Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 1; Test specification

Definition of the tests of the ISUP in order to support compatibility and validation procedures for nodes having implemented T/S 43-14

Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija št. 7 - Prva različica ISDN-uporabniškega dela (ISUP) - Preskuševalna specifikacija

General Information

Status
Published
Publication Date
30-Apr-1997
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-May-1997
Due Date
01-May-1997
Completion Date
01-May-1997

Buy Standard

Standard
P ETS 300 335:1997
English language
122 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day
Standard
ETS 300 335:1997
English language
122 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.DFLMDIntegrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 1; Test specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 335 E13SIST ETS 300 335:1997en01-MDQXDU19973SIST ETS 300 335:1997SLOVENSKI
STANDARD



SIST ETS 300 335:1997



EUROPEANETS 300 335TELECOMMUNICATIONJuly 1994STANDARDSource: ETSI TC-SPSReference: DE/SPS-6004ICS:33.080Key words:ISDN, SS7, ISUP, testingIntegrated Services Digital Network (ISDN);Signalling System No.7ISDN User Part (ISUP) version 1Test specificationETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1994. All rights reserved.SIST ETS 300 335:1997New presentation - see History box



Page 2ETS 300 335: July 1994Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 335:1997



Page 3ETS 300 335: July 1994ContentsForeword.51Scope.72Normative references.73Abbreviations.74Requirements.84.1General principles of validation and compatibility testing.84.2Message Transfer Part (MTP) compatibility testing.84.3Text of CCITT Recommendation Q.784.84.4Exceptions to CCITT Recommendation Q.784.84.5Text of CCITT Recommendation Q.785.84.6Exceptions to CCITT Recommendation Q.785.8Annex A (informative):TTCN version of CCITT Recommendation Q.784.9A.1Scope.9A.2Abbreviations.9A.3Test methodology.9A.4Explanation to the test specification.10A.4.1Test suite overview.10A.4.2TTCN declarations.10A.4.3TTCN constraints.11A.4.4TTCN dynamic part.12A.4.5Application of TTCN version for validation test and compatibility test.12A.5ISUP test list.13A.6Test suite overview.15A.7Declarations part.20A.8Constraints part.23A.9Dynamic part.28A.9.1Test case dynamic behaviour.28A.9.2Test step dynamic behaviour.88A.9.3Default dynamic behaviour.120Annex B (informative):Bibliography.121History.122SIST ETS 300 335:1997



Page 4ETS 300 335: July 1994Blank pageSIST ETS 300 335:1997



Page 5ETS 300 335: July 1994ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).The text of this ETS is almost identical to that contained in CCITT Recommendations Q.784 (1991) andQ.785 (1991). It has therefore been decided to endorse the text of CCITT RecommendationsQ.784 (1991) and Q.785 (1991), and to specify the exceptions to those Recommendations in this ETS.A Tree and Tabular Combined Notation (TTCN) version of the tests contained in CCITT RecommendationQ.784 (1991) is included as an informative annex to this ETS.SIST ETS 300 335:1997



Page 6ETS 300 335: July 1994Blank pageSIST ETS 300 335:1997



Page 7ETS 300 335: July 19941ScopeThis European Telecommunication Standard (ETS) specifies a detailed set of validation and compatibilitytests that validate the protocol specified in ETS 300 121 [4]. The tests confirm that the Signalling SystemNo.7 Integrated Services Digital Network (ISDN) User Part (ISUP) protocol supported by any givenimplementation on the international interface has the ability to correctly convey the necessary signallinginformation to support the supplementary services specified in ETS 300 121 [4].The requirements of this ETS are almost identical to those contained in CCITT RecommendationsQ.784 [2] and Q.785 [3]. This ETS endorses the text of CCITT Recommendations Q.784 [2] andQ.785 [3]. It specifies the exceptions to those Recommendations, and some additional requirements.A TTCN version of the tests contained in CCITT Recommendation Q.784 [2] is included as an informativeannex to this ETS.2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]CCITT Recommendation Q.780 (1988): "Signalling system No.7 testspecification general description".[2]CCITT Recommendation Q.784 (1991): "ISUP basic call test specification".[3]CCITT Recommendation Q.785 (1991): "ISUP protocol test specification forsupplementary services".[4]ETS 300 121 (1992): "Integrated Services Digital Network (ISDN); Application ofthe ISDN User Part (ISUP) of CCITT Signalling System No.7 for internationalISDN interconnections (ISUP version 1)".[5]ETS 300 336: "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; Message Transfer Part (MTP); Test specification".3AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ISDNIntegrated Services Digital NetworkISUPISDN User PartMTPMessage Transfer PartTTCNTree and Tabular Combined NotationSIST ETS 300 335:1997



Page 8ETS 300 335: July 19944Requirements4.1General principles of validation and compatibility testingFor the general principles of validation and compatibility testing, CCITT Recommendation Q.780 [1] shallapply.4.2Message Transfer Part (MTP) compatibility testingFor compatibility testing, this ETS requires that the Message Transfer Part (MTP) of Signalling SystemNo.7 shall have been tested to ETS 300 336 [5].4.3Text of CCITT Recommendation Q.784The text of CCITT Recommendation Q.784 [2] shall apply, with the exceptions identified in subclause 4.4of this ETS.4.4Exceptions to CCITT Recommendation Q.784The following test numbers in § 6 of CCITT Recommendation Q.784 [2] are not applicable for the basiccall procedures in ETS 300 121 [4]:-test number 1.5.4; and-test number 8.With respect to the tests covering the circuit group blocking and unblocking procedures, the followingapplies:The valid range value indicated in the group blocking/unblocking messages may be up to 255, but thenumber of status bits set to "1" (identifying the affected circuits) shall be 32 or less (as indicated in CCITTRecommendation Q.767 § C.3.27b).4.5Text of CCITT Recommendation Q.785The text of CCITT Recommendation Q.785 [3] shall apply, with the exceptions identified in subclause 4.6of this ETS.4.6Exceptions to CCITT Recommendation Q.785The following test numbers in § 5 of CCITT Recommendation Q.785 [3] are not applicable for thesupplementary services supported by ETS 300 121 [4]:-test number 3.5.1;-test number 3.5.2;-test number 3.6.1;-test number 3.6.2;-test number 3.6.3; and-test number 3.6.4.SIST ETS 300 335:1997



Page 9ETS 300 335: July 1994Annex A (informative):TTCN version of CCITT Recommendation Q.784A.1ScopeThis annex provides the test specification for the basic call procedures of Signalling System No.7 ISUP(CCITT Recommendations Q.761 to Q.764 and Q.767) based on CCITT Recommendation X.292(ISO/IEC 9646). This test specification makes use of the Tree and Tabular Combined Notation (TTCN)and reflects the content of the test specification described in CCITT Recommendation Q.784 [2]. In allcases of conflict between the text of CCITT Recommendation Q.784 [2] and this TTCN annex, thenCCITT Recommendation Q.784 [2] takes precedence.A.2AbbreviationsFor the purposes of this annex, the following abbreviations apply:ASPAbstract Service PrimitiveATSAbstract Test SuiteCABCircuit PCO between service provider and signalling point BCPTCompatibility TestIUTImplementation Under TestLABLower Tester PCO between service provider and signalling point BLTLower TesterPCOPoint of Control and ObservationPDUProtocol Data UnitTTCNTree and Tabular Combined NotationVATValidation TestUTUpper TesterUTAUpper Tester PCO at signalling point AA.3Test methodologyThis test specification in TTCN makes use of the abstract test methodology as described below.The test methodology used for ISUP testing is called the distributed test method (see figure 1). With thistest method an abstract configuration for testing is established, which does not constrain theimplementation of test machines. The configuration consists of the Implementation Under Test (IUT) andthe tester. The main functionalities of the tester are separated into a Lower Tester (LT) and an UpperTester (UT).Figure 1: ISUP test methodSIST ETS 300 335:1997



Page 10ETS 300 335: July 1994In principle, the lower tester has the capabilities to control and observe the IUT at its lower boundary viathe underlying service provider. The upper tester has the capabilities to control and observe the IUT at itsupper boundary.For ISUP testing in particular, the lower tester controls and observes the IUT from the signalling point ofview via the underlying service provider MTP and from the connection point of view via a predefinednumber of circuits. The upper tester controls and observes the IUT by handling calls. In addition the uppertester should control the MML-interface and should observe the indications for maintenance purposes.A.4Explanation to the test specificationAn Abstract Test Suite (ATS) specification written in TTCN needs to contain the following four parts:a)the overview, giving the structure of the test suite, for general information and understanding;b)the declaration part, giving all the objects, e.g. constants, variables, Points of Control andObservation (PCOs), timers, Protocol Data Unit types (PDU types) and Abstract Service Primitivetypes (ASP types);c)the constraints part, giving the actual values for Protocol Data Units (PDUs) and Abstract ServicePrimitives (ASPs);d)the dynamic part, describing each test case behaviour.A.4.1Test suite overviewThe test suite overview is a sort of directory. It provides an index to the test suite and can be used fordocumentation and reference. The overview indicates the name of the test suite; references to therelevant protocol standards; information on the abstract test method and a test suite structure, an index tothe test cases, test steps and defaults contained in the dynamic part. The relation between the test list ofCCITT Recommendation Q.784 [2] and the TTCN test groups and test case names is indicated in the testsuite structure and test case index tables.The test suite overview for this ISUP test specification is given in Clause A.6.A.4.2TTCN declarationsThe declaration part should mention all the objects used in the dynamic part. The TTCN notation providesa particular format for all sorts of objects to be declared. The declarations for ISUP are given in ClauseA.7.Clause A.7 identifies:-test suite parameters and test suite constants. These are introduced to enable test case selectionprocedures;-test suite variables. These are declared for use in test cases, e.g. RSC_Received in test caseISUPB50203;-three PCOs. These are used in the ISUP test suite:LAB:lower tester PCO between service provider and signalling point B. By means of this PCOISUP signalling information is exchanged between the lower tester and the IUT;SIST ETS 300 335:1997



Page 11ETS 300 335: July 1994CAB:circuit PCO between service provider and signalling point B. By means of this PCO circuitcontrol procedures, e.g. connectivity check and echo control check, are accomplished;UTA:upper tester PCO at signalling point A. Some kind of stimulus operations to generate andclear calls, to activate circuit supervision procedures, etc., are assumed;-all timer identifiers and the corresponding duration;-the ASP types which is an incomplete TTCN declaration. A TTCN ASP declaration consists of theASP type identifier, the PCO type identifier and the ASP structure. The last part of this declaration isomitted, in order to create the same level of abstraction as described in the CCITTRecommendation Q.784 [2] test specification using the CCITT Recommendation Q.780 [1]methodology;-the PDU types for which the same approach described previously is applied.A.4.3TTCN constraintsThe ASPs given in combination with the send and receive events in the dynamic part are references toinstances of ASP types. Every instance of an ASP type, called ASP constraint, specifies an actual ASPvalue. An ASP constraint may carry a PDU constraint. All ASP and PDU constraints are grouped in theTTCN constraints part. The constraints part for ISUP are given in Clause A.8.Due to the high level of abstraction which is required, only the ASP constraint identifier and its ASP typeidentifier are described in this test suite. The actual values of the constraints are not envisaged.The ASPs used in this test suite are grouped into:user ASPs:these ASPs are stimuli to establish a call, to release a call, to suspend a call,to resume a call and to check the provision of tones and announcements;maintenance ASPs:one maintenance ASP is declared to represent a maintenance indicationfrom the IUT;mml ASPs:several mml ASPs are described to enable the activation of circuitsupervision procedures within ISUP;circuit ASPs: this category ASPs are exchanged by some functionality which enablescircuit control procedures, e.g. connectivity check;call setup ASPs: the call setup ASPs represent the corresponding call setup PDUs in ISUP;call release ASPs: the call release ASPs represent the corresponding call release PDUs inISUP;circuit supervision ASPs:the circuit supervision ASPs represent the corresponding circuit supervisionPDUs in ISUP.SIST ETS 300 335:1997



Page 12ETS 300 335: July 1994A.4.4TTCN dynamic partThe TTCN dynamic part contains the main body of the test suite, i.e.:-the test cases grouped into test groups: each test case represents one test purpose. SubclauseA.9.1 contains the test cases representing the purposes as mentioned in the ISUP test list (seeClause A.5);-the test steps grouped into the test step library: a test step can be called by all test cases defined inthe test suite. A test step can be represented as a procedure call or subroutine as defined in aprogramming language. The ISUP test suite does use this TTCN construct e.g. to achieve pre-testconditions and to check specific circuit operations. The required test steps for the ISUP test suiteare specified in subclause A.9.2.-the default groups: if a test case or a test step refers to a default tree, then the content of the defaulttree covers additional alternatives to receive events specified in that test case or test step. In thatcase any received behaviour other than the expected behaviour as specified in the test case or teststep will be handled by the default tree. A very generic default tree for this ISUP test specification isspecified in subclause A.9.3.The test specification is based on the test methodology described above. By means of well chosenidentifiers for PCOs and ASPs the used test methodology is expressed.The identifications of the ASPs are self explaining. Although, the TTCN constraints part should clarify thecontents of the ASPs, this is not done in order to create the same level of abstraction as described in theCCITT Recommendation Q.784 [2] test specification using the CCITT Recommendation Q.780 [1]methodology (the actual message content is not specified).In this test specification only the method of "explicit final verdict" is used (i.e. in each leaf of the behaviourtree an entry occurs in the verdict column of the dynamic behaviour tables). If the leaf is an ATTACHconstruct (i.e. test step reference), this verdict has the following meaning: the verdict applies to each leafof the behaviour tree of the test step.A.4.5Application of TTCN version for validation test and compatibility testThis TTCN version of CCITT Recommendation Q.784 [2] is applicable for both Validation Test (VAT) andCompatibility Test (CPT). It is a conceptual description of the test process which in no way implies anyimplementation of the test system. This means that in case of VAT the LT could be a test box or a realexchange with other supporting equipment. In case of CPT the LT is a real exchange (SP B) withsupporting equipment.SIST ETS 300 335:1997



Page 13ETS 300 335: July 1994A.5ISUP test list1Circuit supervision1.1Non allocated circuits1.2Reset of circuits1.2.1RSC received on an idle circuit1.2.2RSC sent on an idle circuit1.2.3RSC received on a locally blocked circuit1.2.4RSC received on a remotely blocked circuit1.2.5Circuit group reset received1.2.6Circuit group reset sent1.2.7Circuit group reset received on remotely blocked circuits1.3Blocking of circuits1.3.1Circuit group blocking unblocking1.3.1.1
CGB and CGU received1.3.1.2
CGB and CGU sent1.3.2Circuit blocking unblocking1.3.2.1
BLO received1.3.2.2
BLO sent1.3.2.3
Blocking from both ends removal of blocking from one end1.3.2.4
IAM received on a remotely blocked circuit1.4Continuity check test call1.4.1CCR received successful1.4.2CCR sent successful1.4.3CCR received unsuccessful1.4.4CCR sent unsuccessful1.4.5CCR received unsuccessful verify T27 timer1.5Receipt of unreasonable signalling information messages1.5.1Receipt of unexpected messages1.5.2Receipt of unexpected messages during call setup1.5.3Receipt of unexpected messages during a call1.5.4Confusion procedures For further study2Normal call setup - ordinary speech calls2.1Both way circuit selection2.1.1IAM sent by controlling SP2.1.2IAM sent by non controlling SP2.2Called address sending2.2.1En bloc operation2.2.2Overlap operation with SAM2.3Successful call setup2.3.1Ordinary call with various indications in ACM2.3.2Ordinary call with ACM CPG and ANM2.3.3Ordinary call with various indications in CON2.3.4Call switched via a satellite2.3.5Echo control procedure for call setup2.3.6Blocking and unblocking during a call initiated2.3.7Blocking and unblocking during a call received3Normal call release3.1Calling party clears before address complete3.2Calling party clears before answer3.3Calling party clears after answer3.4Called party clears after answer3.5Suspend initiated by the network3.6Suspend and resume initiated by a calling party3.7Suspend and resume initiated by a called party3.8Collision of REL messagesSIST ETS 300 335:1997



Page 14ETS 300 335: July 19944Unsuccessful call setup4.1Validate a set of known causes for release5Abnormal situation during a call5.1Inability to release in response to a REL after ANM5.2Timers5.2.1T7 waiting for ACM or CON5.2.2T9 waiting for an answer message5.2.3T1 and T5 failure to receive a RLC5.2.4T6 waiting for RES Network message5.2.5T8 waiting for COT message if applicable5.2.6T12 and T13 failure to receive a BLA5.2.7T14 and T15 failure to receive a UBA5.2.8T16 and T17 failure to receive a RLC5.2.9T18 and T19 failure to receive a CGBA5.2.10T20 and T21 failure to receive a CGUA5.2.11T22 and T23 failure to receive a GRA5.3Reset of circuits during a call5.3.1Of an outgoing circuit5.3.2Of an incoming circuit6Special call setup6.1Continuity check call6.1.1Continuity check required6.1.2COT applied on previous circuit6.1.3Calling party clears during COT6.1.4Delay of through connect6.1.5COT unsuccessful6.2Automatic repeat attempt6.2.1Dual seizure for non controlling SP6.2.2Blocking of a circuit6.2.3Circuit reset6.2.4Continuity check failure6.2.5Reception of unreasonable signalling information6.3Dual seizure6.3.1Dual seizure for controlling SP6.4Semi-automatic operation6.4.1FOT sent following a call to a subscriber6.4.2FOT received following a call to a subscriber6.4.3FOT sent following a call via codes 11 and 126.4.4FOT received following a call via codes 11 and 127Bearer services7.164 kbit/s unrestricted7.1.1Successful call setup7.1.2Unsuccessful call setup7.1.3Dual seizure7.23,1 kHz audio7.2.1Successful call setup8Congestion control and user flow controlFor further study.SIST ETS 300 335:1997



Page 15ETS 300 335: July 1994A.6Test suite overviewTest Suite StructureSuite Name:TTCN version of the CCITT Recommendation Q.784Standards ref:CCITT Recommendation Q.764PICS ref:For further studyPIXIT ref:For further studyTest Method(s):DSE (Distributed Single-layer Embedded test method)Comments:The structure of the test suite aligns with the contents of CCITT RecommendationQ.784Test Group ReferenceTest Group ObjectivePage NoISUPB/ISUP Basic Call 28ISUPB/CS/ 1 Circuit supervision28ISUPB/CS/Non_alloc_circuits/
1.1 Non allocated circuits28ISUPB/CS/Reset/
1.2 Reset of circuits28ISUPB/CS/Blocking/
1.3 Blocking of circuits31ISUPB/CS/Blocking/Circuit_group/
1.3.1 Circuit group blocking unblocking31ISUPB/CS/Blocking/Circuit/
1.3.2 Circuit blocking unblocking32ISUPB/CS/Cont_check_test_call/
1.4 Continuity check test call34ISUPB/CS/Rec_UNREAS/
1.5 Receipt of unreasonable signalling information
messages37ISUPB/NCS/ 2 Normal call setup Ordinary speech40ISUPB/NCS/Both_way_select/
2.1 Both way circuit selection40ISUPB/NCS/Cld_addr_send/
2.2 Called address sending41ISUPB/NCS/Succ_setup/
2.3 Successful call setup43ISUPB/NCR/ 3 Normal call release49ISUPB/UCS/ 4 Unsuccessful call setup55ISUPB/ABN/ 5 Abnormal situation during a call56ISUPB/ABN/Inabl_to_rel/
5.1 Inability to release in respons to a REL after ANM56ISUPB/ABN/Timers/
5.2 Timers57ISUPB/ABN/Reset/
5.3 Reset
of circuits during a call68ISUPB/SPCS/ 6 Special call setup69ISUPB/SPCS/Cont_check_call/
6.1 Continuity check call69ISUPB/SPCS/Autom_rep_attempt/
6.2 Automatic repeat attempt74ISUPB/SPCS/Dual_seiz/
6.3 Dual seizure79ISUPB/SPCS/Semi_autom_oper/
6.4 Semi-automatic operation80ISUPB/BSERV/ 7 Bearer services84ISUPB/BSERV/64kbps_unres/
7.1 64 kbit/s unrestricted84ISUPB/BSERV/3.1kHz_audio/
7.2 3,1 kHz audio87ISUPB/Congestion_and_user_flow/ 8 Congestion control and user flow controlffsSIST ETS 300 335:1997



Page 16ETS 300 335: July 1994Test Case IndexTest Group NameTest Case DescriptionPage NoISUPB/CS/ Non_alloc_circuits/ISUPB101011.1 Non allocated circuits28 Reset/ISUPB102011.2.1 RSC received on an idle circuit28ISUPB102021.2.2 RSC sent on an idle circuit29ISUPB102031.2.3 RSC received on a locally blocked circuit29ISUPB102041.2.4 RSC received on a remotely blocked circuit30ISUPB102051.2.5 Circuit group reset received30ISUPB102061.2.6 Circuit group reset sent30ISUPB102071.2.7 Circuit group reset received on remotely blocked
circuits31 Blocking/
Circuit_group/ISUPB103111.3.1.1 Circuit_group/CGB and CGU received31ISUPB103121.3.1.2 CGB and CGU sent32
Circuit/ISUPB103211.3.2.1 BLO received32ISUPB103221.3.2.2 BLO sent33ISUPB103231.3.2.3 Blocking from both ends removal of blocking from
one end33ISUPB103241.3.2.4 IAM received on a remotely blocked circuit34 Cont_check_test_call/ISUPB104011.4.1 CCR received successful34ISUPB104021.4.2 CCR sent successful35ISUPB104031.4.3 CCR received unsuccessful35ISUPB104041.4.4 CCR sent unsuccessful36ISUPB104051.4.5 CCR received unsuccessful verify T27 timer36 Rec_UNREAS/ISUPB105011.5.1 Receipt of unexpected messages37ISUPB105021.5.2 Receipt of unexpected messages during call setup 38ISUPB105031.5.3 Receipt of unexpected messages during a call39ISUPB/NCS/ Both_way_select/ISUPB201012.1.1 IAM sent by controlling SP40ISUPB201022.1.2 IAM sent by non controlling SP40 Cld_addr_send/ISUPB202012.2.1 En bloc operation41ISUPB202022.2.2 Overlap operation with SAM42 Succ_setup/ISUPB203012.3.1 Ordinary call with various indications in ACM43ISUPB203022.3.2 Ordinary call with ACM CPG and ANM43ISUPB203032.3.3 Ordinary call with various indications in CON44ISUPB203042.3.4 Call switched via a satellite45ISUPB203052.3.5 Echo control procedure for call setup46ISUPB203062.3.6 Blocking and unblocking during a call initiated47ISUPB203072.3.7 Blocking and unblocking during a call received48ISUPB/NCR/ISUPB301013.1 Calling party clears before any backward message49ISUPB302013.2 Calling party clears before answer49ISUPB303013.3 Calling party clears after answer50ISUPB304013.4 Called party clears after answer51ISUPB305013.5 Suspend initiated by the network52ISUPB306013.6 Suspend and resume initiated by a calling party53ISUPB307013.7 Suspend and resume initiated by a called party54ISUPB308013.8 Collision of REL messages55ISUPB/UCS/ISUPB401014.1 Validate a set of known causes for release55ISUPB/ABN/ Inabl_to_rel/ISUPB501015.1 Inability to release in response to a REL after ANM56 Timers/ISUPB502015.2.1 T7 waiting for ACM or CON57ISUPB502025.2.2 T9 waiting for an answer message58ISUPB502035.2.3 T1 and T5 failure to receive a RLC59ISUPB502045.2.4 T6 waiting for RES Network message60ISUPB502055.2.5 T8 waiting for COT message if applicable61ISUPB502065.2.6 T12 and T13 failure to receive a BLA62(continued)SIST ETS 300 335:1997



Page 17ETS 300 335: July 1994Test Case Index (concluded)Test Group NameTest Case DescriptionPage NoISUPB502075.2.7 T14 and T15 failure to receive a UBA63ISUPB502085.2.8 T16 and T17 failure to receive a RLC64ISUPB502095.2.9 T18 and T19 failure to receive a CGBA65ISUPB502105.2.10 T20 and T21 failure to receive a CGUA66ISUPB502115.2.11 T22 and T23 failure to receive a GRA67 Reset/ISUPB503015.3.1 Of an outgoing circuit68ISUPB503025.3.2 Of an incoming circuit68ISUPB/SPCS/Cont_check_call/ISUPB601016.1.1 Continuity check required69ISUPB601026.1.2 COT applied on a previous circuit70ISUPB601036.1.3 Calling party clears during a COT71ISUPB601046.1.4 Delay of through connect72ISUPB601056.1.5 COT unsuccessful73 Autom_rep_attempt/ISUPB602016.2.1 Dual seizure for non-controlling SP74ISUPB602026.2.2 Blocking of a circuit75ISUPB602036.2.3 Circuit reset76ISUPB602046.2.4 Continuity check failure77ISUPB602056.2.5 Reception of unreasonable signalling information78 Dual_seiz/ISUPB603016.3.1 Dual seizure for controlling SP79 Semi_autom_oper/ISUPB604016.4.1 FOT sent following a call to a subscriber80ISUPB604026.4.2 FOT received following a call to a subscriber81ISUPB604036.4.3 FOT sent following a call via codes 11 and 1282ISUPB604046.4.4 FOT received following a call via codes 11 and 1283ISUPB/BSERV/ 64kbps_unres/ISUPB701017.1.1 Successful call setup84ISUPB701027.1.2 Unsuccessful call setup85ISUPB701037.1.3 Dual seizure86 3.1kHz_audio/ISUPB702017.2.1 Successful call setup87SIST ETS 300 335:1997



Page 18ETS 300 335: July 1994Test Step IndexTest Step Group Test Step NamePage NoISUPB/TEST_S
...

SLOVENSKI STANDARD
SIST ETS 300 335:1997
01-maj-1997
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 6LJQDOL]DFLMDãW3UYD
UD]OLþLFD,6'1XSRUDEQLãNHJDGHOD ,683 3UHVNXãHYDOQDVSHFLILNDFLMD
Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part
(ISUP) version 1; Test specification
Ta slovenski standard je istoveten z: ETS 300 335 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 335:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 335:1997

---------------------- Page: 2 ----------------------

SIST ETS 300 335:1997
EUROPEAN ETS 300 335
TELECOMMUNICATION July 1994
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-6004
ICS: 33.080
ISDN, SS7, ISUP, testing
Key words:
Integrated Services Digital Network (ISDN);
Signalling System No.7
ISDN User Part (ISUP) version 1
Test specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1994. All rights reserved.
New presentation - see History box

---------------------- Page: 3 ----------------------

SIST ETS 300 335:1997
Page 2
ETS 300 335: July 1994
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 335:1997
Page 3
ETS 300 335: July 1994
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Abbreviations.7
4 Requirements.8
4.1 General principles of validation and compatibility testing .8
4.2 Message Transfer Part (MTP) compatibility testing.8
4.3 Text of CCITT Recommendation Q.784.8
4.4 Exceptions to CCITT Recommendation Q.784 .8
4.5 Text of CCITT Recommendation Q.785.8
4.6 Exceptions to CCITT Recommendation Q.785 .8
Annex A (informative): TTCN version of CCITT Recommendation Q.784 .9
A.1 Scope .9
A.2 Abbreviations.9
A.3 Test methodology.9
A.4 Explanation to the test specification.10
A.4.1 Test suite overview .10
A.4.2 TTCN declarations.10
A.4.3 TTCN constraints.11
A.4.4 TTCN dynamic part.12
A.4.5 Application of TTCN version for validation test and compatibility test .12
A.5 ISUP test list.13
A.6 Test suite overview.15
A.7 Declarations part .20
A.8 Constraints part.23
A.9 Dynamic part .28
A.9.1 Test case dynamic behaviour .28
A.9.2 Test step dynamic behaviour.88
A.9.3 Default dynamic behaviour .120
Annex B (informative): Bibliography.121
History.122

---------------------- Page: 5 ----------------------

SIST ETS 300 335:1997
Page 4
ETS 300 335: July 1994
Blank page

---------------------- Page: 6 ----------------------

SIST ETS 300 335:1997
Page 5
ETS 300 335: July 1994
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
The text of this ETS is almost identical to that contained in CCITT Recommendations Q.784 (1991) and
Q.785 (1991). It has therefore been decided to endorse the text of CCITT Recommendations
Q.784 (1991) and Q.785 (1991), and to specify the exceptions to those Recommendations in this ETS.
A Tree and Tabular Combined Notation (TTCN) version of the tests contained in CCITT Recommendation
Q.784 (1991) is included as an informative annex to this ETS.

---------------------- Page: 7 ----------------------

SIST ETS 300 335:1997
Page 6
ETS 300 335: July 1994
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 335:1997
Page 7
ETS 300 335: July 1994
1 Scope
This European Telecommunication Standard (ETS) specifies a detailed set of validation and compatibility
tests that validate the protocol specified in ETS 300 121 [4]. The tests confirm that the Signalling System
No.7 Integrated Services Digital Network (ISDN) User Part (ISUP) protocol supported by any given
implementation on the international interface has the ability to correctly convey the necessary signalling
information to support the supplementary services specified in ETS 300 121 [4].
The requirements of this ETS are almost identical to those contained in CCITT Recommendations
Q.784 [2] and Q.785 [3]. This ETS endorses the text of CCITT Recommendations Q.784 [2] and
Q.785 [3]. It specifies the exceptions to those Recommendations, and some additional requirements.
A TTCN version of the tests contained in CCITT Recommendation Q.784 [2] is included as an informative
annex to this ETS.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] CCITT Recommendation Q.780 (1988): "Signalling system No.7 test
specification general description".
[2] CCITT Recommendation Q.784 (1991): "ISUP basic call test specification".
[3] CCITT Recommendation Q.785 (1991): "ISUP protocol test specification for
supplementary services".
[4] ETS 300 121 (1992): "Integrated Services Digital Network (ISDN); Application of
the ISDN User Part (ISUP) of CCITT Signalling System No.7 for international
ISDN interconnections (ISUP version 1)".
[5] ETS 300 336: "Integrated Services Digital Network (ISDN); Signalling System
No.7; Message Transfer Part (MTP); Test specification".
3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ISDN Integrated Services Digital Network
ISUP ISDN User Part
MTP Message Transfer Part
TTCN Tree and Tabular Combined Notation

---------------------- Page: 9 ----------------------

SIST ETS 300 335:1997
Page 8
ETS 300 335: July 1994
4 Requirements
4.1 General principles of validation and compatibility testing
For the general principles of validation and compatibility testing, CCITT Recommendation Q.780 [1] shall
apply.
4.2 Message Transfer Part (MTP) compatibility testing
For compatibility testing, this ETS requires that the Message Transfer Part (MTP) of Signalling System
No.7 shall have been tested to ETS 300 336 [5].
4.3 Text of CCITT Recommendation Q.784
The text of CCITT Recommendation Q.784 [2] shall apply, with the exceptions identified in subclause 4.4
of this ETS.
4.4 Exceptions to CCITT Recommendation Q.784
The following test numbers in § 6 of CCITT Recommendation Q.784 [2] are not applicable for the basic
call procedures in ETS 300 121 [4]:
- test number 1.5.4; and
- test number 8.
With respect to the tests covering the circuit group blocking and unblocking procedures, the following
applies:
The valid range value indicated in the group blocking/unblocking messages may be up to 255, but the
number of status bits set to "1" (identifying the affected circuits) shall be 32 or less (as indicated in CCITT
Recommendation Q.767 § C.3.27b).
4.5 Text of CCITT Recommendation Q.785
The text of CCITT Recommendation Q.785 [3] shall apply, with the exceptions identified in subclause 4.6
of this ETS.
4.6 Exceptions to CCITT Recommendation Q.785
The following test numbers in § 5 of CCITT Recommendation Q.785 [3] are not applicable for the
supplementary services supported by ETS 300 121 [4]:
- test number 3.5.1;
- test number 3.5.2;
- test number 3.6.1;
- test number 3.6.2;
- test number 3.6.3; and
- test number 3.6.4.

---------------------- Page: 10 ----------------------

SIST ETS 300 335:1997
Page 9
ETS 300 335: July 1994
Annex A (informative): TTCN version of CCITT Recommendation Q.784
A.1 Scope
This annex provides the test specification for the basic call procedures of Signalling System No.7 ISUP
(CCITT Recommendations Q.761 to Q.764 and Q.767) based on CCITT Recommendation X.292
(ISO/IEC 9646). This test specification makes use of the Tree and Tabular Combined Notation (TTCN)
and reflects the content of the test specification described in CCITT Recommendation Q.784 [2]. In all
cases of conflict between the text of CCITT Recommendation Q.784 [2] and this TTCN annex, then
CCITT Recommendation Q.784 [2] takes precedence.
A.2 Abbreviations
For the purposes of this annex, the following abbreviations apply:
ASP Abstract Service Primitive
ATS Abstract Test Suite
CAB Circuit PCO between service provider and signalling point B
CPT Compatibility Test
IUT Implementation Under Test
LAB Lower Tester PCO between service provider and signalling point B
LT Lower Tester
PCO Point of Control and Observation
PDU Protocol Data Unit
TTCN Tree and Tabular Combined Notation
VAT Validation Test
UT Upper Tester
UTA Upper Tester PCO at signalling point A
A.3 Test methodology
This test specification in TTCN makes use of the abstract test methodology as described below.
The test methodology used for ISUP testing is called the distributed test method (see figure 1). With this
test method an abstract configuration for testing is established, which does not constrain the
implementation of test machines. The configuration consists of the Implementation Under Test (IUT) and
the tester. The main functionalities of the tester are separated into a Lower Tester (LT) and an Upper
Tester (UT).
Figure 1: ISUP test method

---------------------- Page: 11 ----------------------

SIST ETS 300 335:1997
Page 10
ETS 300 335: July 1994
In principle, the lower tester has the capabilities to control and observe the IUT at its lower boundary via
the underlying service provider. The upper tester has the capabilities to control and observe the IUT at its
upper boundary.
For ISUP testing in particular, the lower tester controls and observes the IUT from the signalling point of
view via the underlying service provider MTP and from the connection point of view via a predefined
number of circuits. The upper tester controls and observes the IUT by handling calls. In addition the upper
tester should control the MML-interface and should observe the indications for maintenance purposes.
A.4 Explanation to the test specification
An Abstract Test Suite (ATS) specification written in TTCN needs to contain the following four parts:
a) the overview, giving the structure of the test suite, for general information and understanding;
b) the declaration part, giving all the objects, e.g. constants, variables, Points of Control and
Observation (PCOs), timers, Protocol Data Unit types (PDU types) and Abstract Service Primitive
types (ASP types);
c) the constraints part, giving the actual values for Protocol Data Units (PDUs) and Abstract Service
Primitives (ASPs);
d) the dynamic part, describing each test case behaviour.
A.4.1 Test suite overview
The test suite overview is a sort of directory. It provides an index to the test suite and can be used for
documentation and reference. The overview indicates the name of the test suite; references to the
relevant protocol standards; information on the abstract test method and a test suite structure, an index to
the test cases, test steps and defaults contained in the dynamic part. The relation between the test list of
CCITT Recommendation Q.784 [2] and the TTCN test groups and test case names is indicated in the test
suite structure and test case index tables.
The test suite overview for this ISUP test specification is given in Clause A.6.
A.4.2 TTCN declarations
The declaration part should mention all the objects used in the dynamic part. The TTCN notation provides
a particular format for all sorts of objects to be declared. The declarations for ISUP are given in Clause
A.7.
Clause A.7 identifies:
- test suite parameters and test suite constants. These are introduced to enable test case selection
procedures;
- test suite variables. These are declared for use in test cases, e.g. RSC_Received in test case
ISUPB50203;
- three PCOs. These are used in the ISUP test suite:
LAB: lower tester PCO between service provider and signalling point B. By means of this PCO
ISUP signalling information is exchanged between the lower tester and the IUT;

---------------------- Page: 12 ----------------------

SIST ETS 300 335:1997
Page 11
ETS 300 335: July 1994
CAB: circuit PCO between service provider and signalling point B. By means of this PCO circuit
control procedures, e.g. connectivity check and echo control check, are accomplished;
UTA: upper tester PCO at signalling point A. Some kind of stimulus operations to generate and
clear calls, to activate circuit supervision procedures, etc., are assumed;
- all timer identifiers and the corresponding duration;
- the ASP types which is an incomplete TTCN declaration. A TTCN ASP declaration consists of the
ASP type identifier, the PCO type identifier and the ASP structure. The last part of this declaration is
omitted, in order to create the same level of abstraction as described in the CCITT
Recommendation Q.784 [2] test specification using the CCITT Recommendation Q.780 [1]
methodology;
- the PDU types for which the same approach described previously is applied.
A.4.3 TTCN constraints
The ASPs given in combination with the send and receive events in the dynamic part are references to
instances of ASP types. Every instance of an ASP type, called ASP constraint, specifies an actual ASP
value. An ASP constraint may carry a PDU constraint. All ASP and PDU constraints are grouped in the
TTCN constraints part. The constraints part for ISUP are given in Clause A.8.
Due to the high level of abstraction which is required, only the ASP constraint identifier and its ASP type
identifier are described in this test suite. The actual values of the constraints are not envisaged.
The ASPs used in this test suite are grouped into:
user ASPs: these ASPs are stimuli to establish a call, to release a call, to suspend a call,
to resume a call and to check the provision of tones and announcements;
maintenance ASPs: one maintenance ASP is declared to represent a maintenance indication
from the IUT;
mml ASPs: several mml ASPs are described to enable the activation of circuit
supervision procedures within ISUP;
circuit ASPs: this category ASPs are exchanged by some functionality which enables
circuit control procedures, e.g. connectivity check;
call setup ASPs: the call setup ASPs represent the corresponding call setup PDUs in ISUP;
call release ASPs: the call release ASPs represent the corresponding call release PDUs in
ISUP;
circuit supervision ASPs: the circuit supervision ASPs represent the corresponding circuit supervision
PDUs in ISUP.

---------------------- Page: 13 ----------------------

SIST ETS 300 335:1997
Page 12
ETS 300 335: July 1994
A.4.4 TTCN dynamic part
The TTCN dynamic part contains the main body of the test suite, i.e.:
- the test cases grouped into test groups: each test case represents one test purpose. Subclause
A.9.1 contains the test cases representing the purposes as mentioned in the ISUP test list (see
Clause A.5);
- the test steps grouped into the test step library: a test step can be called by all test cases defined in
the test suite. A test step can be represented as a procedure call or subroutine as defined in a
programming language. The ISUP test suite does use this TTCN construct e.g. to achieve pre-test
conditions and to check specific circuit operations. The required test steps for the ISUP test suite
are specified in subclause A.9.2.
- the default groups: if a test case or a test step refers to a default tree, then the content of the default
tree covers additional alternatives to receive events specified in that test case or test step. In that
case any received behaviour other than the expected behaviour as specified in the test case or test
step will be handled by the default tree. A very generic default tree for this ISUP test specification is
specified in subclause A.9.3.
The test specification is based on the test methodology described above. By means of well chosen
identifiers for PCOs and ASPs the used test methodology is expressed.
The identifications of the ASPs are self explaining. Although, the TTCN constraints part should clarify the
contents of the ASPs, this is not done in order to create the same level of abstraction as described in the
CCITT Recommendation Q.784 [2] test specification using the CCITT Recommendation Q.780 [1]
methodology (the actual message content is not specified).
In this test specification only the method of "explicit final verdict" is used (i.e. in each leaf of the behaviour
tree an entry occurs in the verdict column of the dynamic behaviour tables). If the leaf is an ATTACH
construct (i.e. test step reference), this verdict has the following meaning: the verdict applies to each leaf
of the behaviour tree of the test step.
A.4.5 Application of TTCN version for validation test and compatibility test
This TTCN version of CCITT Recommendation Q.784 [2] is applicable for both Validation Test (VAT) and
Compatibility Test (CPT). It is a conceptual description of the test process which in no way implies any
implementation of the test system. This means that in case of VAT the LT could be a test box or a real
exchange with other supporting equipment. In case of CPT the LT is a real exchange (SP B) with
supporting equipment.

---------------------- Page: 14 ----------------------

SIST ETS 300 335:1997
Page 13
ETS 300 335: July 1994
A.5 ISUP test list
1 Circuit supervision
1.1 Non allocated circuits
1.2 Reset of circuits
1.2.1 RSC received on an idle circuit
1.2.2 RSC sent on an idle circuit
1.2.3 RSC received on a locally blocked circuit
1.2.4 RSC received on a remotely blocked circuit
1.2.5 Circuit group reset received
1.2.6 Circuit group reset sent
1.2.7 Circuit group reset received on remotely blocked circuits
1.3 Blocking of circuits
1.3.1 Circuit group blocking unblocking
1.3.1.1  CGB and CGU received
1.3.1.2  CGB and CGU sent
1.3.2 Circuit blocking unblocking
1.3.2.1  BLO received
1.3.2.2  BLO sent
1.3.2.3  Blocking from both ends removal of blocking from one end
1.3.2.4  IAM received on a remotely blocked circuit
1.4 Continuity check test call
1.4.1 CCR received successful
1.4.2 CCR sent successful
1.4.3 CCR received unsuccessful
1.4.4 CCR sent unsuccessful
1.4.5 CCR received unsuccessful verify T27 timer
1.5 Receipt of unreasonable signalling information messages
1.5.1 Receipt of unexpected messages
1.5.2 Receipt of unexpected messages during call setup
1.5.3 Receipt of unexpected messages during a call
1.5.4 Confusion procedures For further study
2 Normal call setup - ordinary speech calls
2.1 Both way circuit selection
2.1.1 IAM sent by controlling SP
2.1.2 IAM sent by non controlling SP
2.2 Called address sending
2.2.1 En bloc operation
2.2.2 Overlap operation with SAM
2.3 Successful call setup
2.3.1 Ordinary call with various indications in ACM
2.3.2 Ordinary call with ACM CPG and ANM
2.3.3 Ordinary call with various indications in CON
2.3.4 Call switched via a satellite
2.3.5 Echo control procedure for call setup
2.3.6 Blocking and unblocking during a call initiated
2.3.7 Blocking and unblocking during a call received
3 Normal call release
3.1 Calling party clears before address complete
3.2 Calling party clears before answer
3.3 Calling party clears after answer
3.4 Called party clears after answer
3.5 Suspend initiated by the network
3.6 Suspend and resume initiated by a calling party
3.7 Suspend and resume initiated by a called party
3.8 Collision of REL messages

---------------------- Page: 15 ----------------------

SIST ETS 300 335:1997
Page 14
ETS 300 335: July 1994
4 Unsuccessful call setup
4.1 Validate a set of known causes for release
5 Abnormal situation during a call
5.1 Inability to release in response to a REL after ANM
5.2 Timers
5.2.1 T7 waiting for ACM or CON
5.2.2 T9 waiting for an answer message
5.2.3 T1 and T5 failure to receive a RLC
5.2.4 T6 waiting for RES Network message
5.2.5 T8 waiting for COT message if applicable
5.2.6 T12 and T13 failure to receive a BLA
5.2.7 T14 and T15 failure to receive a UBA
5.2.8 T16 and T17 failure to receive a RLC
5.2.9 T18 and T19 failure to receive a CGBA
5.2.10 T20 and T21 failure to receive a CGUA
5.2.11 T22 and T23 failure to receive a GRA
5.3 Reset of circuits during a call
5.3.1 Of an outgoing circuit
5.3.2 Of an incoming circuit
6 Special call setup
6.1 Continuity check call
6.1.1 Continuity check required
6.1.2 COT applied on previous circuit
6.1.3 Calling party clears during COT
6.1.4 Delay of through connect
6.1.5 COT unsuccessful
6.2 Automatic repeat attempt
6.2.1 Dual seizure for non controlling SP
6.2.2 Blocking of a circuit
6.2.3 Circuit reset
6.2.4 Continuity check failure
6.2.5 Reception of unreasonable signalling information
6.3 Dual seizure
6.3.1 Dual seizure for controlling SP
6.4 Semi-automatic operation
6.4.1 FOT sent following a call to a subscriber
6.4.2 FOT received following a call to a subscriber
6.4.3 FOT sent following a call via codes 11 and 12
6.4.4 FOT received following a call via codes 11 and 12
7 Bearer services
7.1 64 kbit/s unrestricted
7.1.1 Successful call setup
7.1.2 Unsuccessful call setup
7.1.3 Dual seizure
7.2 3,1 kHz audio
7.2.1 Successful call setup
8 Congestion control and user flow control
For further study.

---------------------- Page: 16 ----------------------

SIST ETS 300 335:1997
Page 15
ETS 300 335: July 1994
A.6 Test suite overview
Test Suite Structure
Suite Name
: TTCN version of the CCITT Recommendation Q.784
Standards ref
: CCITT Recommendation Q.764
PICS ref
: For further study
PIXIT ref
: For further study
Test Method(s)
: DSE (Distributed Single-layer Embedded test method)
Comments
: The structure of the test suite aligns with the contents of CCITT Recommendation
Q.784
Test Group Reference Test Group Objective Page No
ISUPB/ ISUP Basic Call 28
ISUPB/CS/ 1 Circuit supervision 28
ISUPB/CS/Non_alloc_circuits/  1.1 Non allocated circuits 28
ISUPB/CS/Reset/  1.2 Reset of circuits 28
ISUPB/CS/Blocking/  1.3 Blocking of circuits 31
ISUPB/CS/Blocking/Circuit_group/  1.3.1 Circuit group blocking unblocking 31
ISUPB/CS/Blocking/Circuit/  1.3.2 Circuit blocking unblocking 32
ISUPB/CS/Cont_check_test_call/  1.4 Continuity check test call 34
ISUPB/CS/Rec_UNREAS/  1.5 Receipt of unreasonable signalling information
     messages 37
ISUPB/NCS/ 2 Normal call setup Ordinary speech 40
ISUPB/NCS/Both_way_select/  2.1 Both way circuit selection 40
ISUPB/NCS/Cld_addr_send/  2.2 Called address sending 41
ISUPB/NCS/Succ_setup/  2.3 Successful call setup 43
ISUPB/NCR/ 3 Normal call release 49
ISUPB/UCS/ 4 Unsuccessful call setup 55
ISUPB/ABN/ 5 Abnormal situation during a call 56
ISUPB/ABN/Inabl_to_rel/  5.1 Inability to release in respons to a REL after ANM 56
ISUPB/ABN/Timers/  5.2 Timers 57
ISUPB/ABN/Reset/  5.3 Reset of circuits during a call 68
ISUPB/SPCS/ 6 Special call setup 69
ISUPB/SPCS/Cont_check_call/  6.1 Continuity check call 69
ISUPB/SPCS/Autom_rep_attempt/  6.2 Automatic repeat attempt 74
ISUPB/SPCS/Dual_seiz/  6.3 Dual seizure 79
ISUPB/SPCS/Semi_autom_oper/  6.4 Semi-automatic operation 80
ISUPB/BSERV/ 7 Bearer services 84
ISUPB/BSERV/64kbps_unres/  7.1 64 kbit/s unrestricted 84
ISUPB/BSERV/3.1kHz_audio/  7.2 3,1 kHz audio 87
ISUPB/Congestion_and_user_flow/ 8 Congestion control and user flow control ffs

---------------------- Page: 17 ----------------------

SIST ETS 300 335:1997
Page 16
ETS 300 335: July 1994
Test Case Index
Test Group Name Test Case Description Page No
ISUPB/CS/
Non_alloc_circuits/
ISUPB10101 1.1 Non allocated circuits 28
Reset/ ISUPB10201 1.2.1 RSC received on an idle circuit 28
ISUPB10202 1.2.2 RSC sent on an idle circuit 29
ISUPB10203 1.2.3 RSC received on a locally blocked circuit 29
ISUPB10204 1.2.4 RSC received on a remotely blocked circuit 30
ISUPB10205 1.2.5 Circuit group reset received 30
ISUPB10206 1.2.6 Circuit group reset sent 30
ISUPB10207 1.2.7 Circuit group reset received on remotely blocked
     circuits 31
Blocking/
 Circuit_group/ ISUPB10311 1.3.1.1 Circuit_group/CGB and CGU received 31
ISUPB10312 1.3.1.2 CGB and CGU sent 32
 Circuit/ ISUPB10321 1.3.2.1 BLO received 32
ISUPB10322 1.3.2.2 BLO sent 33
ISUPB10323 1.3.2.3 Blocking from both ends removal of blocking from
      one end 33
ISUPB10324 1.3.2.4 IAM received on a remotely blocked circuit 34
Cont_check_test_call/ ISUPB10401 1.4.1 CCR received successful 34
ISUPB10402 1.4.2 CCR sent successful 35
ISUPB10403 1.4.3 CCR received unsuccessful 35
ISUPB10404 1.4.4 CCR sent unsuccessful 36
ISUPB10405 1.4.5 CCR received unsuccessful verify T27 timer 36
Rec_UNREAS/ ISUPB10501 1.5.1 Receipt of unexpected messages 37
ISUPB10502 1.5.2 Receipt of unexpected messages during call setup 38
ISUPB10503 1.5.3 Receipt of unexpected messages during a call 39
ISUPB/NCS/
Both_way_select/ ISUPB20101 2.1.1 IAM sent by controlling SP 40
ISUPB20102 2.1.2 IAM sent by non controlling SP 40
Cld_addr_send/ ISUPB20201 2.2.1 En bloc operation 41
ISUPB20202 2.2.2 Overlap operation with SAM 42
Succ_setup/ ISUPB20301 2.3.1 Ordinary call with various indications in ACM 43
ISUPB20302 2.3.2 Ordinary call with ACM CPG and ANM 43
ISUPB20303 2.3.3 Ordinary call with various indications in CON 44
ISUPB20304 2.3.4 Call switched via a satellite 45
ISUPB20305 2.3.5 Echo control procedure for call setup 46
ISUPB20306 2.3.6 Blocking and unblocking during a call initiated 47
ISUPB20307 2.3.7 Blocking and unblocking during a call received 48
ISUPB/NCR/ ISUPB30101 3.1 Calling party clears before any backward message 49
ISUPB30201 3.2 Calling party clears before answer 49
ISUPB30301 3.3 Calling party clears after answer 50
ISUPB30401 3.4 Called party clears after answer 51
ISUPB30501 3.5 Suspend initiated by the network 52
ISUPB30601 3.6 Suspend and resume initiated by a calling party 53
ISUPB30701 3.7 Suspend and resume initiated by a called party 54
ISUPB30801 3.8 Collision of REL messages 55
ISUPB/UCS/ ISUPB40101 4.1 Val
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.