SIST EN 300 356-32 V3.0.4:2005

• Abstract:

  Definition of ISUP version 2 tests in order to support interoperability & validation for nodes having implemented basic services.

• Status: Published
• Publication Date: 31-Mar-2005
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Ref Project: ETSI EN 300 356-32 V3.0.4 (2000-09) - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 32: Test Suite Structure and Test Purposes (TSS&TP) specification for basic services

SIST EN 300 356-32 V3.0.4:2005 is the SIST version of ETSI EN 300 356-32 for Integrated Services Digital Network (ISDN) Signalling System No.7 ISDN User Part (ISUP) version 3 on the international interface. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for basic services, so manufacturers, operators and test laboratories can validate exchanges that implement ISUP v3. The document focuses on conformance testing for basic call control and signalling procedures.

What does SIST EN 300 356-32 V3.0.4:2005 specify?

SIST EN 300 356-32 V3.0.4:2005 specifies the validation conformance test specification for ISUP'97 basic call control and signalling procedures defined in ITU-T Recommendation Q.764, as endorsed by EN 300 356-1. It applies to exchanges that have implemented the ISUP v3 protocol specification and is intended for validation testing of the exchange types covered by that protocol.

The scope also points readers to the companion documents that carry the implementation statements and the executable test suite: EN 300 356-31 for the PICS proforma and EN 300 356-33 for the ATS and PIXIT proforma. The compatibility tests are covered by ITU-T Recommendation Q.784.1.

The document is organized into these main parts:

• Clause 1 - Scope
• Clause 2 - References
• Clause 3 - Definitions and abbreviations
• Clause 4 - Implementation under test and test methods
• Clause 5 - Conventions used within the ATS
• Clause 6 - Test Suite Structure (TSS)
• Clause 7 - Test purposes (TP)
• Clause 8 - Test coverage
• Bibliography and History

What are the key requirements of SIST EN 300 356-32 V3.0.4:2005?

SIST EN 300 356-32 V3.0.4:2005 is built around a distributed multiparty test method, with the exchange as the System Under Test (SUT) and its ISUP v3 implementation as the Implementation Under Test (IUT). In practice, this means the test setup must observe both signalling and circuit behavior, not only the message flow.

Test method and exchange roles

Clause 4 distinguishes intermediate exchanges from local exchanges. For intermediate exchanges, the test method uses ISUP links on both sides of the SUT, with Points of Control and Observation on the signalling links and on the circuits; the maintenance function is controlled through MNT. For local exchanges, the access side is also part of the test configuration, because call handling, tones and announcements may need to be observed through the user-network interface.

Clause 4 also explains the roles used by the test suite: Originating Local Exchange, Transit Exchange, Incoming/Gateway Exchange, Outgoing/Gateway Exchange and Destination Local Exchange. This matters because the selected test configuration depends on the exchange role, and some test cases run in reversed direction.

ATS conventions and execution rules

Clause 5 fixes the naming patterns for test suite parameters, variables, constants, timers, operations, aliases and test cases. The ATS uses abstract names such as S_XXX and R_XXX for sent and received ISUP messages, and the timer naming follows a clear TN pattern. For a test laboratory, this makes the ATS readable and helps map results back to the protocol events being exercised.

Clause 5.9 describes the execution model: the Main Test Component controls the IUT, then creates one concurrent slave Parallel Test Component chosen from the PICS and PIXIT information. Clause 5.10 adds special pre-test conditions, such as data that must be arranged in the IUT so that pass-on is possible or impossible, continuity checks are required, fallback occurs, or the route avoids echo control devices.

Test suite structure and test purpose groups

Clause 6 gives the Test Suite Structure for ISUP_v3_Basic_Call. Clause 7 then organizes the test purposes into the main groups CSSV, NCS, NCR, UCS, AS, SCS and BS, plus related groups for congestion and user flow control, echo control, temporary alternate routing, hop counter procedure, call collect request procedure and Nx64k bit connection type. This structure matters in practice because it lets the user trace each test to a call-control function or bearer-service behavior.

The test purposes are grouped by valid, inopportune and syntactically invalid stimulus. Many cases focus on circuit supervision, blocking and unblocking, continuity check, normal call setup and release, timer expiry, fallback, segmentation, dual seizure and unknown parameter handling. For an implementer, these are the behaviors that most often affect interoperability at the international interface.

What terms does SIST EN 300 356-32 V3.0.4:2005 define?

• Abstract Test Case (ATC) - a complete abstract specification of the actions needed to reach one test purpose and end in a stable state.
• Abstract Test Method (ATM) - the abstract description of how the IUT is tested, independent of a specific test tool realization.
• Abstract Test Suite (ATS) - the collection of abstract test cases used for conformance testing.
• Implementation Under Test (IUT) - the protocol implementation being exercised by the tests.
• Means of Testing (MOT) - the equipment and procedures used to derive, select, parameterize, execute and log the tests.
• Point of Control and Observation (PCO) - the location in the test setup where test events are controlled and observed.
• Protocol Implementation Conformance Statement (PICS) - the supplier’s statement of which protocol capabilities are implemented.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the supplier’s testing information needed to run the ATS against the IUT.

Who uses SIST EN 300 356-32 V3.0.4:2005?

SIST EN 300 356-32 V3.0.4:2005 is used by exchange manufacturers, telecom operators, conformance test laboratories and certification teams working with ISDN and SS7 interconnection. It is especially relevant when a team needs to prove that an exchange can handle basic call control, signalling supervision, circuit blocking and release behavior at the international interface.

Quality managers and buyers use it to check that a vendor’s PICS and PIXIT information can be mapped to a real test campaign. Test engineers use it to configure the MTC, PTCs, lower testers and upper tester roles described in the document, and maintenance teams use it where the tests touch maintenance alarms and blocking states.

Which standards are used with SIST EN 300 356-32 V3.0.4:2005?

• EN 300 356-1 - defines the ISUP version 3 basic services procedures that the tests validate.
• EN 300 356-31 - provides the PICS proforma for basic services.
• EN 300 356-33 - provides the ATS and PIXIT proforma for basic services.
• ISO/IEC 9646-1 - gives the conformance testing methodology and framework.
• ISO/IEC 9646-3 - provides the Tree and Tabular Combined Notation (TTCN).
• ISO/IEC 9646-7 - defines Implementation Conformance Statements.
• ITU-T Q.764 - defines the ISUP signalling procedures being tested.
• ITU-T Q.762 and ITU-T Q.763 - provide message functions and format/codes used in the test purposes.
• ITU-T Q.784.1 - provides the basic-call test specification for validation and compatibility.
• EN 300 008-1 and ITU-T Q.707 - provide the Message Transfer Part (MTP) support used by the signalling network.
• ITU-T E.164 - defines the ISDN numbering plan used in the definitions.

What does the SIST EN 300 356-32 V3.0.4:2005 document contain?

The document contains figures for the exchange as SUT and for the intermediate and local exchange test configurations, plus a table of exchange roles. It also includes tables of special pre-test conditions and a structured list of test purposes with selection expressions tied to PICS and exchange role.

Most of the document is the test-purpose catalog. Those tables identify the ISUP'97 reference for each case, the test purpose name, and the conditions under which the case applies, so they can be used directly in design verification, conformance testing and lab execution. Clause 8 then summarizes the coverage of the suite.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 32: Test Suite Structure and Test Purposes (TSS&TP) specification for basic services33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 356-32 Version 3.0.4SIST EN 300 356-32 V3.0.4:2005en01-april-2005SIST EN 300 356-32 V3.0.4:2005SLOVENSKI
STANDARD
ETSIEN300356-32V3.0.4(2000-09)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version3fortheinternationalinterface;Part32:TestSuiteStructureandTestPurposes(TSS&TP)specificationforbasicservicesSIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)2ReferenceREN/SPS-01037-2KeywordsISDN,ISUP,SS7,testing,TSS&TP,basicETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)3ContentsIntellectualPropertyRights.4Foreword.41Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.84Implementationundertestandtestmethods.94.1Identificationofthesystemandimplementationundertest.94.2ATMandtestingconfigurationforISUPv3.104.2.1Intermediateexchanges.114.2.2Localexchanges.124.2.3Master-slaveaspectsinthetestconfiguration.145ConventionsusedwithintheATS.155.1Testsuiteparameters,constantsandvariables.155.2Testcasevariables.155.3ASPconstraints.155.4Timers.155.5Testsuiteoperations.155.6Aliases.155.7Testcaseandstepidentifiers.165.8Constraints.165.9Dynamicbehaviourpart.165.10Pre-testconditions.176TestSuiteStructure(TSS).187Testpurposes(TP).207.1Introduction.207.1.1Testpurpose(TP)namingconvention.207.1.2Sourceoftestpurposedefinition.217.1.3Testpurposestructure.217.2Testpurposesforthebasiccall.227.2.1CSSV:Circuitsupervisionandsignallingsupervision.227.2.2NCS:Normalcallsetupordinaryspeechcalls.557.2.3NCRNormalcallrelease.637.2.4UCS:Unsuccessfulcallsetup.657.2.5AS:Abnormalsituations.667.2.6SCS:Specialcallsetup.697.2.7BS:Bearerservices.767.2.8CUF:Congestionanduserflowcontrol.837.2.9EC:Echocontrol.847.2.10TAR:Temporaryalternaterouting.907.2.11HOP:HopCounterProcedure.917.2.12CALLCOL:CallCollectRequestProcedure.927.2.13Nx64k:Nx64kbitconnectiontype.938Testcoverage.1048.1Generalremarks.104Bibliography.105History.106SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart32ofamulti-partstandardcoveringtheISDNUserPart(ISUP)version3fortheinternationalinterface,asidentifiedbelow:Part1:"Basicservices";Part2:"ISDNsupplementaryservices";Part3:"CallingLineIdentificationPresentation(CLIP)supplementaryservice";Part4:"CallingLineIdentificationRestriction(CLIR)supplementaryservice";Part5:"ConnectedLineIdentificationPresentation(COLP)supplementaryservice";Part6:"ConnectedLineIdentificationRestriction(COLR)supplementaryservice";Part7:"TerminalPortability(TP)supplementaryservice";Part8:"User-to-UserSignalling(UUS)supplementaryservice";Part9:"ClosedUserGroup(CUG)supplementaryservice";Part10:"Subaddressing(SUB)supplementaryservice";Part11:"MaliciousCallIdentification(MCID)supplementaryservice";Part12:"ConferenceCall,add-on(CONF)supplementaryservice";Part14:"ExplicitCallTransfer(ECT)supplementaryservice";Part15:"Diversionsupplementaryservices";Part16:"CallHold(HOLD)supplementaryservice";Part17:"CallWaiting(CW)supplementaryservice";Part18:"CompletionofCallstoBusySubscriber(CCBS)supplementaryservice";Part19:"Threeparty(3PTY)supplementaryservice";Part20:"CompletionofCallsonNoReply(CCNR)supplementaryservice";Part31:"ProtocolImplementationConformanceStatement(PICS)proformaspecificationforbasicservices";Part32:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforbasicservices";SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)5Part33:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforbasicservices";Part34:"ProtocolImplementationConformanceStatement(PICS)proformaspecificationforsupplementaryservices";Part35:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforsupplementaryservices";Part36:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforsupplementaryservices".NOTE:Part13and21to30havenotbeenissued.NationaltranspositiondatesDateofadoptionofthisEN:21July2000DateoflatestannouncementofthisEN(doa):31October2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30April2001DateofwithdrawalofanyconflictingNationalStandard(dow):30April2001SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)61ScopeThepresentdocumentcontainsthevalidation(conformance)testspecificationforISUP'97basiccallcontrolandsignallingproceduresdefinedinITU-TRecommendationQ.764[13]asendorsedbyEN300356-1[2].ThepresentdocumentappliesonlytoexchangeshavingimplementedtheISUPv3protocolspecification.ItisapplicableforvalidationtestingofalltypesofexchangesasdefinedintheISUPv3protocolspecification.NotethatthecompatibilitytestsarecoveredbyITU-TRecommendationQ.784.1[10].Themaintextpartofthepresentdocumentpresentstherequirementsregardingthechosentestmethod,conventionsusedwithintheATS,thetestsuitestructureandthetestpurposes(TSS&TP)forISUPv3basiccallcontrolprocedures.EN300356-31[3]presentstheProtocolImplementationConformanceStatements(PICS)ISUPv3basiccallcontrolproceduresandEN300356-33[4]presentstheactualATS,whichisdeliveredinelectronicformonly,andtheProtocolConformanceTestReport(PCTR).2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300008-1(V1.3):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;MessageTransferPart(MTP)tosupportinternationalinterconnection;Part1:Protocolspecification[ITU-TRecommendationsQ.701,Q.702,Q.703,Q.704,Q.705,Q.706,Q.707andQ.708modified]".[2]ETSIEN300356-1(V3.2):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version3fortheinternationalinterface;Part1:Basicservices[ITU-TRecommendationsQ.761toQ.764(1997),modified]".[3]ETSIEN300356-31(V3.0):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version3fortheinternationalinterface;Part31:ProtocolImplementationConformanceStatement(PICS)proformaspecificationforbasicservices".[4]ETSIEN300356-33(V3.0):"IntegratedServicesDigitalNetwork(ISDN);SignallingSystemNo.7;ISDNUserPart(ISUP)version3fortheinternationalinterface;Part33:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforbasicservices".[5]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[7]ISO/IEC9646-7:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part7:ImplementationConformanceStatements".[8]ITU-TRecommendationE.164:"Theinternationalpublictelecommunicationnumberingplan".[9]ITU-TRecommendationQ.767:"ApplicationoftheISDNuserpartofCCITTsignallingsystemNo.7forinternationalISDNinterconnections".SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)7[10]ITU-TRecommendationQ.784.1:"ISUPbasiccalltestspecification:ValidationandcompatibilityforISUP'92andQ.767protocols".[11]ITU-TRecommendationQ.784.2(1997):"ISUPbasiccalltestspecification:AbstracttestsuiteforISUP'92basiccallcontrolprocedures".[12]ITU-TRecommendationQ.784.3:"ISUP'97Basiccallcontrolprocedures,testsuitestructureandtestpurposes(TSS&TP)".[13]ITU-TRecommendationQ.764:"SignalingSystemNo.7-ISDNuserpartsignalingprocedures".[14]ITU-TRecommendationQ.762:"SignalingSystemNo.7-ISDNuserpartgeneralfunctionsofmessagesandsignals".[15]ITU-TRecommendationQ.707:"Testingandmaintenance".[16]ITU-TRecommendationQ.763:"SignallingSystemNo.7-ISDNuserpartformatandcodes".[17]ITU-TRecommendationQ.724:"SpecificationsofSignallingSystemNo.7-Telephoneuserpart".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:-termsdefinedinISDNUserPart(ISUP)referencespecification;-termsdefinedinISO/IEC9646-1[5],ISO/IEC9646-3[6]andinISO/IEC9646-7[7].Inparticular,thefollowingtermsapply:AbstractTestCase(ATC):completeandindependentspecificationoftheactionsrequiredtoachieveaspecifictestpurpose,definedatthelevelofabstractionofaparticularAbstractTestMethod,startinginastabletestingstateandendinginastabletestingstate(seeISO/IEC9646-1[5],subclause3.3.3)AbstractTestMethod(ATM):descriptionofhowanIUTistobetested,givenatanappropriatelevelofabstractiontomakethedescriptionindependentofanyparticularrealizationofaMeansofTesting,butwithenoughdetailtoenableabstracttestcasestobespecifiedforthismethod(seeISO/IEC9646-1[5],subclause3.3.5)AbstractTestSuite(ATS):testsuitecomposedofabstracttestcases(seeISO/IEC9646-1[5],subclause3.3.6)ImplementationUnderTest(IUT):implementationofoneormoreOSIprotocolsinanadjacentuser/providerrelationship,beingpartofarealopensystemwhichistobestudiedbytesting(seeISO/IEC9646-1[5],subclause3.3.43)ISDNnumber:numberconformingtothenumberingandstructurespecifiedinITU-TRecommendationE.164[8]MeansofTesting(MOT):combinationofequipmentandproceduresthatcanperformthederivation,selection,parameterizationandexecutionoftestcases,inconformancewithareferencestandardizedATS,andcanproduceaconformancelog(seeISO/IEC9646-1[5],subclause3.3.54)PICSproforma:document,intheformofaquestionnaire,whichwhencompletedforanimplementationorsystembecomesthePICSPIXITproforma:document,intheformofaquestionnaire,whichwhencompletedfortheIUTbecomesthePIXITPointofControlandObservation(PCO):pointwithinatestingenvironmentwheretheoccurrenceoftesteventsistobecontrolledandobserved,asdefinedinanAbstractTestMethod(seeISO/IEC9646-1[5],subclause3.3.64)Pre-testcondition:settingorstateintheIUTwhichcannotbeachievedbyprovidingstimulusfromthetestenvironmentSIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)8ProtocolImplementationConformanceStatement(PICS):statementmadebythesupplierofaprotocolclaimedtoconformtoagivenspecification,statingwhichcapabilitieshavebeenimplemented(seeISO/IEC9646-1[5],subclause3.3.39andsubclause3.3.80)ProtocolImplementationeXtraInformationforTesting(PIXIT):statementmadebyasupplierorimplementerofanIUT(protocol)whichcontainsorreferencesalloftheinformationrelatedtotheIUTanditstestingenvironment,whichwillenablethetestlaboratorytorunanappropriatetestsuiteagainsttheIUT(seeISO/IEC9646-1[5],subclause3.3.41andsubclause3.3.81)SystemUnderTest(SUT):realopensysteminwhichtheIUTresides(see[ISO/IEC9646-1[5],subclause3.3.103)User:accessprotocolentityattheUsersideoftheuser-networkinterfacewhereaTreferencepointorcoincidentSandTreferencepointapplies3.2AbbreviationsTheISUPmessageacronymscanbefoundintable2ofITU-TRecommendationQ.762[14]asendorsedbyEN300356-1[2].Forthepurposesofthepresentdocument,thefollowingabbreviationsapply:ACHAccesssignallingPCO-(D-channel)APHAccessphysicalcircuitPCO-(B-channel)ASPAbstractServicePrimitiveATCAbstractTestCaseATMAbstractTestMethodATSAbstractTestSuiteCABPCOforABcircuitsCACPCOforACcircuitsCICCircuitIdentificationCodeCntrlEControllingExchangeDLEDestinationLocalExchangeDSS1DigitalSubscriberSystemNo.1ICSImplementationConformanceStatementIncIEIncomingInternationalExchangeIntermEIntermediateExchangeISCInternationalSwitchingCentreISDNIntegratedServicesDigitalNetworkISUPISDNUserPartIUTImplementationUnderTestITEInternationalTransitExchangeLABPCOforsignallinglinkABLACPCOforsignallinglinkACLAPDLinkAccessProtocolfortheD-channelLTLowerTesterMOTMeansOfTestingMMIManMachineInterfaceMNTMaintenancePCOMTCMainTestComponentMTPMessageTransferPartNNINetwork-networkinterfaceNTENationalTransitExchangeOLEOriginatingLocalExchangeOPROperatorPCOOutIEOutgoingInternationalExchangePCOPointofControlandObservationPCTParallelTestComponentPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingPTCParallelTestComponentSIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)9SCCPSignallingConnectionControlPartSCSSystemConformanceStatementSPSignallingPointSS7SignallingSystemN°7SUTSystemUnderTestTPTestPurposeTypeATypeAexchangeTypeBTypeBexchangeTCPTestCo-ordinationProceduresTSSTestSuiteStructureTSS&TPTestSuiteStructureandTestPurposesTTCNTreeandTabularCombinedNotationUNIUser-networkinterfaceUTUpperTester4Implementationundertestandtestmethods4.1IdentificationofthesystemandimplementationundertestThesystemundertest(SUT)isanexchange.SUTExchangeMMIcapabilitiesandfunctionsISUPAccessISUPISUPv3IUTFigure1:ExchangeasSUTTheimplementationundertest(IUT)istheISUPv3implementationinthisexchange,asshowninfigure1.TheaimoftheISUPimplementationistoassurecapabilitiesandfunctionsforcircuitandsignallingsupervisionononehandandforcallhandlingontheother.CircuitsupervisionisdonemainlythroughtheMMI(manmachineinterface)oftheexchange.TheMMIinterfaceisimplementationdependentandthusnotstandardized.TheeffectsofsignallingproceduresoftheISDNUserPartcanbeobservedontheNNI(network-networkinterface),onthecircuitscontrolledbytheISUP.TheISUPsignallingprotocolcanbeobservedontheSS7linkontheNNI.TheISUPimplementationwillinsomeexchangeshavetointerworkwiththeaccesssignallingsystemontheUNI(user-networkinterface)andinvolvecallhandlinginordertoestablishend-to-endconnections.FromtheISUPreferencestandardseveraltypesofexchanges(orroles)canbeidentifiedaspresentedinfigure2.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)10AccessAccessintermediatelocallocalTransitNTEGatewayOutIETransitITEGatewayIncIEnationalnetworkinternationalnetworknationalnetworkDLEOLEFigure2:RolesofexchangesTheexchangescanbedividedintwomaingroupsaccordingtotheirfunctionality:localexchanges,wherecallsoriginateandterminate,andintermediateexchanges,withtransitfunctionality.Localexchangesarenational,i.e.belongtoanationalnetwork.Intermediateexchangesarenationalorinternational.Theinternationalintermediateexchangeswhichpermitaccesstotheinternationalnetworkarethegatewayexchanges(incomingandoutgoing),alsocalledISCs-internationalswitchingcentres.Therolesoftheexchangesaresummarizedintable1:Table1:RolesofexchangesLocalIntermediateExchangeExchangeNationalInternationalOriginatingLocalExchangeTypeAOLETransitExchangeTypeBNTEITEIncoming/GatewayExchangeTypeAIncIEOutgoing/GatewayExchangeTypeAOutIEDestinationLocalExchangeTypeADLE4.2ATMandtestingconfigurationforISUPv3TheAbstractTestMethod(ATM)chosenfortheISUPv3testingspecificationisthedistributedmultipartytestmethod.TheATMisdefinedatanappropriatelevelofabstractionsothatthetestcasesmaybespecifiedappropriately,withoutaddingrestrictionstotheimplementationundertest.Thetestingarchitecturesaredescribedinthefollowingsubclauses.TheATSiswritteninconcurrentTTCN.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)114.2.1IntermediateexchangesTheconfigurationproposedfortestingintermediateexchangesisshowninfigure3.InordertotesttheprotocolandfunctionalityoftransitandgatewayexchangesoneneedstoconsidertheincomingandoutgoingsideoftheSUT.SPASPBIUTTCPMNTCABLABLTISUPlinkCircuitsTCPLTLTPhysicalaspectsCircuitsISUPlinkSPCCACLACUTMaintenanceNetworkserviceproviderNetworkserviceproviderLTFigure3:ISUPtestmethodforintermediateexchangesTheIUTisobservedandcontrolledfromtwoISUPlinkswithassociatedcircuits.Thepointsofcontrolandobservation(PCO)arelabelledLABandCABononeside,andLACandCAContheother.TheLABandLACPCOsareusedbythelowertesters(LT)forcontrollingtheISUPsignallinglink,whereastheCABandCACPCOsareusedbythelowertestersforobservingcircuitrelatedevents,suchasconnectivity,echocontrolcheck,alertingtone,etc.TheISUPPDUstobesentandobservedontheLABPCOsideallowforPDUconstraintstobespecifiedandcodeddowntothebit-level.TheMNTPCOisusedbytheuppertester(UT)tocontrolandobservethemaintenancefunctionsoftheexchange.TheunderlyingnetworkserviceprovideristheMessageTransferPart(MTP)protocolasspecifiedinEN300008-1[1]andITU-TRecommendationsQ.707[15]asendorsedbyEN300008-1[1].SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)12Figure4showstheactualusedconfigurationforintermediateexchanges,withamaintestingcomponent(MTC),responsiblefortheA-Binterfaceandaslaveparalleltestingcomponent(PTC),responsiblefortheC-Ainterface.ThemaintenancePCO(MNT)andtheoperatorPCO(OPR),neededforalimitednumberoftestcasesareintegratedintheMTC,forsimplifyingreasons.Thetestco-ordinationprocedures(TCP)allowforcommunicationbetweenthetesters.Thetestcomponentsaremostlyimplicitlyco-ordinated(asynchronously);theTCPsareonlyusedwhenitisnecessarytoobtaintheverdictfromtheparalleltestcomponent.TCPPTCMTCMaintenanceoperatorISUPsignalling,circuitsMNTOPRISUPsignalling,circuitsIUTSPCSPBCABLABCACLACSPANetworkserviceproviderNetworkserviceproviderFigure4:ISUPtestconfigurationforintermediateexchanges4.2.2LocalexchangesWhentestingalocalexchangeasspecifiedinthereferencestandard,itisdifficult,ifnotimpossible,toobserveonlyISUPPDUs,iffunctionalitysuchasconnectivity,tonesandannouncementsetc.associatedwithprotocoleventsistobeconsideredandusedtoassignverdicts.Thereferencestandardoftenreferstoactionsoreventsinitiatedbyortobeobservedbythecallingorcalleduser.APointofControlofObservationfromISUP(IUT)totheaccesssideisneeded,e.g.forstimulatingthelocalexchangetooriginateacall(sendanIAM).AnotherPCOisneededtocheckconnectivityortochecktonesgeneratedetc.bythelocalexchange.ThereisnoexposedinterfacefromISUP(theIUT)towardstheaccessside.Forpracticaltestingpurposesthenaturalchoiceistheaccessinterface.Itisthereforereasonabletomakeuseoftheaccessinterface(e.g.theuseraccessinterfaceDSS1)asaPCOandtouseexistingnamingconventionsfortheabstractserviceprimitives(ASPs)tobeusedonthisPCO.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)13Figure5presentsamultipartytestingconfigurationforlocalexchanges.InthisfigureeachtesterhasasinglePCO.ThePCOfortheaccessusestheunderlyingaccessserviceprovider(e.g.LAPD,incaseofDSS1)forobservingaccesseventsandstimulatingtheISUPviatheaccess.TheISUPimplementation(IUT)cannotbetestedwithoutinvolvingtheuser-networkinterface(UNI).SPASPBIUTTCPMNTCABLABTCPACHAccessserviceproviderPhysicalaspectsAPHUNILTAnnouncementstones,etc.UTMaintenanceLTCallhandlingLTCircuitsLTISUPlinkNetworkserviceproviderFigure5:ISUPtestmethodfororiginating/destinationexchangesOntherightsidetherearetwoPCOsasinthetestconfigurationpresentedintheprevioussubclause.TheLABPCOisusedbytheLTcontrollingtheISUPsignallinglink,whereastheCABPCOisusedbyanotherLTcontrollingthetrafficchannels(forobservingcircuitrelatedevents,suchasconnectivity,echocontrolcheck,alertingtone,etc.).TheISUPPDUstobesentandobservedontheLABPCOsideallowforPDUconstraintstobespecifiedandcodeddowntothebitlevel.TheMNTPCOisusedbytheUpperTestertocontrolandobservethemaintenancefunctionsoftheexchange.OntheaccesssidetherearetwoPCOsandtwoLTssimilartotheonesonnetworkside.TheACHPCOisusedtoobserveandcontroltheCallHandlingevents,whereastheAPHisusedtocontrolandobservephysicalaspects(e.g.tonesandannouncements).TheaccessPDUstobesentandobservedontheACHPCOarechosenatanappropriatelevelofabstraction.FortheaccessASPsDSS1-like,primitivenameshavebeenused,whereasaccessPDUconstraintshavenotbeencodedtothebitlevel.Theaccessaspectscannotbeleftoutforlocalexchanges,wideninginthisrespecttosomeextentthescopeoftheISUPtesting.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)14Figure6showstheactualusedconfigurationforlocalexchanges,withamaster-testingcomponent(MTC),responsiblefortheA-Binterfaceandaslaveparalleltestingcomponent(PTC),responsiblefortheUNIaccessinterface.ThemaintenancePCOisintegratedintheMTC,forsimplifyingreasons.CABLABTCPPTCIUTMNTMaintenanceSPBMTCACHCallhandlingAPHUNISPAAccessserviceproviderNetworkserviceproviderISUPsignalling,circuitsFigure6:ISUPtestconfigurationforlocalexchanges4.2.3Master-slaveaspectsinthetestconfigurationFigures4and6showthelogicaltestcomponentsoftheadoptedtestconfiguration.ThemaintestcomponentislocatedontherightsideoftheIUT,whereasontheleftsidetherearedifferentparalleltestcomponents:ISUP(seefigure4)andaccess(seefigure6).TheATSiswrittensothattheappropriateconfigurationischosendependingontheexchange'sroletobetested.TherightsidemaintestcomponentmaybeinternationalornationalISUPandisconfigurablesothatanytwoofthesemayberunbasedontheanswersgiventoPIXITquestions.Theleftsideparalleltestcomponentmaybeofanykind:itmaybeinternationalornationalISUP,anaccesssignallingsystemoranon-ISUPUserpart.AttestexecutionexactlyoneoftheseconfigurationswillbechosenbasedontheinformationprovidedinthePICSandPIXIT.ForthegatewayexchangesitisassumedbydefaultthatthecallissetupfromtheleftPTCtotherightMTC.Insometestcasesthecallsetupisdoneinthereversedirection.ThesetestcasesaremarkedintheATSwiththeconfigurationfieldsetto"reversed".TheyhavetobeexecutedwithadifferentsetofPIXITsettings.Themessageflowinthetestcasesisdesignedinsuchawaythattheverdictisassignedbasedonobservingthebehaviourontherightside.Theleftsidewillinthiscasemainlyactasaslavestimulus/acceptor.Thereare,however,testcaseswheretheexpectedbehaviourofbothsidesisneededtoassigntheverdict.AnexampleofsuchatestcaseisthereleaseonbothsidesafterT7(waitingforACM)expiry,wherethefinalverdicthastobebasedontheverdictsassignedonboththeABandtheACinterfaces.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)155ConventionsusedwithintheATSAbbreviationsforISUPmessagesandparametersareusedconsistentlythroughoutthedocument.AbbreviationsforthesignallinginformationofISUPasdefinedinITU-TRecommendationQ.762[14]asendorsedinEN300356-1[2]areconsistentlyusedwithintheATSandareusefulforunderstandingand/ormaintainingthecodingdetaillevel.5.1Testsuiteparameters,constantsandvariablesMosttestsuiteparametersarenamedusingthepattern:TSP_Xxx.Mosttestsuitevariablesarenamedusingthepattern:TSV_Xxx.Alltestsuiteconstantsarenamedusingthepattern:TSC_Xxx.5.2TestcasevariablesMosttestcasevariablesarenamedusingthepattern:TCV_Xxx.5.3ASPconstraintsThenamingschemeforASPconstraintsis:PDU_XY_more_specific.WherePDUindicatesthePDUtypeincluded,XYindicatesthedirectionandmorespecific(ifany)describestheconstraintwithabbreviatednamingconvention.EXAMPLE:IAM_BA_PDCindicatesanIAMsentfromSPBtoSPA,withapropagationdelaycounter.5.4TimersAlltimersarenamedusingthepattern:TN[_minor_max].EXAMPLE:T7,T7_min,T7_max.5.5TestsuiteoperationsMostnamesfortestsuiteoperationsfollowthescheme:TSO_TestSuiteOperationName.TheTSOfunctionsarespecifiedusingthesyntaxofCprogramminglanguage.5.6AliasesAliasesareextensivelyusedinsteadofcumbersomenamesforASPprimitives(likeMTPTRANSFER_IND).Theyarenamedusingthescheme:S_XXXforthesendingofanISUPmessageXXXwhichresolvestotheMTPTRANSFER_REQprimitive.R_XXXforthereceiptofanISUPmessageXXXwhichisresolvedtotheMTPTRANSFER_INDprimitive.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)165.7TestcaseandstepidentifiersThegeneralnamingconventionforthetestcasesis:ISB_{X}_n_n_n._{a}_{n_a}.WhereXiseither:V-validstimulus,I-inopportunestimulusorS-syntacticallyinvalidstimulus;nisaoneortwodigittestcasenumberalignedwithITU-TRecommendationQ.784.1[10]andaisalowercaselettertodistinguishbetweentestsincaseofvariants.Thelastnumberpluslowercaseletterissometimesusedtofurtherdistinguishbetweentestcases.Thegeneralnamingconventionforthedispatcherteststepsis:S_n_n_n.Wherethen-sarethesameasthetestcasetowhichtheyrelate.Thedispatched"slaves"arenamedasfollows:ISUPslave:I_n_n_n.accessslave:A_n_n_n.non-ISUPslave:T_n_n_n.Somegenericstepswithappropriatenames,e.g.tocompletethecall-setup(+S_ACM_etc_BA,+R_ACM_etc_AC)arealsoused.5.8ConstraintsTheconstraintsvisibleonthetestcaselevelareallASPconstraints.TheASPsarechainedtoPDUconstraintseverytimeanISUPmessageisinvolved.ThisallowsforahigherlevelofabstractiononthetestcaselevelandhidestheinformationintheASPconstraintpart.InthecaseofaccessPDUs,nofurtherPDUconstraintsaredefined.GenerallyderivedPDUconstraintsareavoidedforsimplicityreasons.5.9DynamicbehaviourpartThegeneralschemeofrunningatestcasecanbedescribedbrieflyasfollows:Firstly,thecontrolisgiventothemaintestcomponent,whichstartsexecuting.ThismaintestcomponentcontrolsandobservestheIUTontheABsignallinglink.Secondlyafterpossiblyinitializingsomedatathemaintestcomponentcreatesthecorrespondingparalleltestcomponent.Thiscomponentistheslaveprocessanditislocatedinaseparateteststep.Itisdispatchedusingaparameterderivedfromtheroleoftheexchangetobetested.Foreachtestcaseexactlyoneconcurrent"slave"paralleltestcomponent,eitherISUP,oraccess,ornon-ISUPiscreated.ForexampleifthetestconfigurationrequiresanISUPtesterontheleftside,thentheISUPparalleltestcomponentiscreated,andsoon.Themain(right)andtheparallel(left)testcomponentswillthenco-operate,mostofthetimeasynchronouslydrivenbythereceivedmessages,untilthetestpurposeisachievedandtheverdictisset.Thebehaviourdescriptioniskeptonanabstractlevel,hidingwheneveritispossibleprogrammingdetailsintheunderlyingteststeps.Teststepsareusedwheneverthissavescodewithoutdecreasingthereadabilityofthetestcase.Oftenfunctionallyrelatedteststepsaregroupedtogetherusinglocaltrees.Thecommentfieldsareextensivelyused.Themessagesequencechartforthechosentestingconfigurationisprovidedattestcaseleveltoquicklygiveanoverviewoftheexpectedbehaviour.Foroptimalreadabilityanon-proportionalfontisusedforprintingthearrowdiagrams.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)175.10Pre-testconditionsForeachtestitisassumedthatthecircuitsareunblockedfrombothsidesandidle.Someparticulartestcasesneedspecialpre-testconditions.Thesearepresentedintable2.Table2:Specialpre-testconditionsPre-testconditionTestcaseArrangethedataintheIUTsuchthatpassonisnotpossible.IBC_V_1_7_1_4IBC_V_1_7_1_5IBC_V_1_7_2_5IBC_V_1_7_2_6_aIBC_V_1_7_2_6_bIBC_V_1_7_2_7_aIBC_V_1_7_2_7_bArrangethedataintheIUTsuchthattheunknownparameterwillbepassedonbytheIUT.IBC_I_1_7_2_9_aArrangethedataintheIUTsuchthattheunknownparameterwillbediscardedbytheIUT.IBC_I_1_7_2_9_bArrangethedataintheIUTsuchthatthecallisswitchedviasatelliteconnection.IBC_V_2_3_4_aIBC_V_2_3_4_bIBC_V_2_3_4_cArrangethedataintheIUTsuchthatanetworkinitiatedSuspendmessagecanbetriggeredbysignallingpointC(SPC).IBC_V_3_5_bArrangethedataintheIUTsuchthatitisunabletoreturnthecircuittotheidleconditioninresponsetoareleasemessage.IBC_V_5_1ArrangethedataintheIUTsuchthatacontinuitycheckisrequiredontheoutgoingcircuit.IBC_V_6_1_1_aArrangethedataintheIUTsuchthatacontinuitycheckisappliedonthiscall.IBC_V_6_1_3_aArrangethedataintheIUTsuchthatacontinuitycheckisrequiredontheoutgoingcircuit.IBC_V_6_1_4_aIBC_V_6_1_5IBC_V_6_2_4ArrangethedataintheIUTsuchthatfallbackoccursintheIUT.IBC_V_6_6_3_aIBC_V_6_6_3_bArrangethedataintheIUTsuchthatthereareenoughcircuitsavailableforthecall.IBC_V_7_3_7IBC_V_7_3_8IBC_V_7_3_9ArrangethedataintheIUTsuchthattheISDNUserPartofsignallingpointB(SPB)becomesunavailableintheIUT.IBC_V_8_2_2IBC_V_8_2_3ArrangethedataintheIUTsuchthatthecallisroutedoveraroutenotrequiringechocontroldevices.IBC_V_9_1_2SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)186TestSuiteStructure(TSS)ISUP_v3_Basic_Call:CSSVCSRCBCCCTCCGBURUSIMCBURUMSPANCSPVBWCSFDCASBDSCSRMNCRPDDPUCSASTRCDCIneveryleaf:SCSCCCVARAIDSSSAOSGMFBBSUNRAUDMCTCUFACCIACECSITARENHOPCALLNx64kFigure7:TestsuitestructureSIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)19Thetestsuitestructurenamingconventionsare:CSSVCircuitsupervisionandsignallingsupervisionCSCircuitsupervisionRCResetofcircuitsBCBlockingofcircuitsCGBUCircuitgroupblockingunblockingCBUCircuitblockingunblockingCCTCContinuitychecktestcallRUSIMReceiptofunreasonablesignallinginformationmessagesRUReceiptofunknownMSMessagesPAParametersPVParametervaluesFDIntheforwarddirectionBDInthebackwarddirectionRMInthereleasemessageNCSNormalcallsetupordinaryspeechcallsBWCSBothwaycircuitselectionCASCalledaddresssendingSCSSuccessfulcallsetupPDDPPropagationdelaydeterminationprocedureNCRNormalcallreleaseUCSUnsuccessfulcallsetupASAbnormalsituationsTTimersRCDCResetofcircuitduringacallSCSSpecialcallsetupCCCContinuitycheckcallARAAutomaticrepeatattemptDSDualseizureSAOSemi-automaticoperationSGMSimplesegmentationFBFallbackBSBearerservicesUNR64kbit/sunrestrictedconnectiontypesSIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)20AUD3,1kHzaudioconnectiontypeMCTMultirateconnectiontypesCUFCongestionanduserflowcontrolACCAutomaticcongestioncontrolIACISUPavailabilitycontrolECEchocontrolSISimpleechocontrolENEnhancedechocontrolTARTemporaryalternateroutingHOPHopCounterProcedureCALLCOLCallCollectRequestProcedureNx64kNx64kbitconnectiontypeVValidbehaviourstimulusIInopportunestimulusSSyntacticallyincorrectstimulus(e.g.outsiderange,useofsparevalues)7Testpurposes(TP)7.1IntroductionForeachtestrequirementaTestPurpose(TP)isdefined.7.1.1Testpurpose(TP)namingconventionTestpurposesarenumbered,followingtheschemeofITU-TRecommendationQ.784.1[10],withineachgroup.Groupsareorganizedaccordingtothetestsuitestructure(TSS)downtothelastbutonelevel.TheclassificationintheV/I/SgroupsisdonebytheinclusionofV,IorSinthetestcasename.Additionalqualifiers,intheformoflowercaseletters,areaddedtoidentifyvariantswithinonegenerictestcasefromITU-TRecommendationQ.784.1[10],seetable3.AdditionallydefinedtestcasesarenumberedsucceedingtheonesusedinITU-TRecommendationQ.784.1[10].SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)21Table3:TPidentifiernamingconventionschemeIdentifier:IBC___._IBC=ISUPv3BasicCall=group:onecharacterfieldrepresentingthegroupreferenceaccordingtoTSSV:ValidstimulusI:InopportunestimulusS:Syntacticallyinvalidstimulus=CorrespondingreferencenumbersinITU-TRecommendationQ.784.1[10](ifany)=LowercasecharacterdistinguishingtestswithsamereferencenumberInthesubgroupsofCSSV/RU/PV/(FD,BD,RM)somespecialnamingconventionsapply.TheparagraphnumberoftheparametercodingdescriptioninITU-TRecommendationQ.763[16]asendorsedbyEN300356-1[2]hasbeenincludedinthetestcasenametodifferentiatethevarioustestsofparametervalues.7.1.2SourceoftestpurposedefinitionThetestpurposeshavebeendevelopedbasedonITU-TRecommendationQ.784.1[10].Someadditionalvalidationtestcasesaredefined.7.1.3TestpurposestructureAllofthefollowingtestpurposesbelongtothemaingroupISUP_v3_Basic_Call.Eachtestpurposeispresentedinaseparatetable.Thefirstrowofthetablecontainsthefollowingitems:TSSIdentifierinthetestsuitestructure(testgroup/subgroupidentifier).TPIdentifierofthetestpurpose.ISUP'97referenceThereferencetotherequirementintheISUP'97standards,whichledtothetestpurpose.SelectionexpressionSelectioncriterionforthetestpurposetakingintoaccounttheexchange'sroleandtheanswerstothespecifiedPICSquestions.N/AmeansthattheTPisvalidforallrolesofexchanges.Thetestpurposestructureisaccordingtothetestsuitestructure(TSS).TestpurposesthattestnormalbehaviourhavebeengroupedintheV-validbehaviourgroup.TestpurposesthattesttheIUTbehaviourinsituationsthatarenotnormaloperationhavebeengroupedintheI-Inopportunestimulusgroup.TestpurposesthattesttheIUTbehaviouronsparevaluesorvaluesoutofrangehavebeengroupedintheS-Syntacticallyincorrectstimulusgroup.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)227.2TestpurposesforthebasiccallAllofthefollowingtestpurposesbelongtothemaingroupISUP_v3_Basic_Call.7.2.1CSSV:CircuitsupervisionandsignallingsupervisionTSSCSSV/CS/TPIBC_I_1_1ISUP'97referenceN/ASelectionexpressionN/AQ.784.1[10]reference1.1TestpurposeNon-allocatedcircuitsToverifythatonthereceiptofaCICrelatingtoacircuitwhichdoesnotexist,theIUTwilldiscardthemessageandalertthemaintenancesystem.TSSCSSV/RC/TPIBC_V_1_2_1ISUP'97reference2.9.3.1b)/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.1TestpurposeRSCreceivedonanidlecircuitToverifythatonreceiptofaResetcircuitmessagetheIUTwillrespondbysendingaReleasecompletemessage.TSSCSSV/RC/TPIBC_V_1_2_2ISUP'97reference2.9.3.1/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.2TestpurposeRSCsentonanidlecircuitToverifythattheIUTisabletogenerateaResetcircuitmessage.TSSCSSV/RC/TPIBC_V_1_2_3ISUP'97reference2.9.3.1c)/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.3TestpurposeRSCreceivedonalocallyblockedcircuitToverifythatonreceiptofaResetcircuitmessagewhileinitslocallyblockedstate,theIUTwillrespondbysendingaBlockingmessageandaReleasecompletemessage.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)23TSSCSSV/RC/TPIBC_V_1_2_4ISUP'97reference2.9.3.1d)/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.4TestpurposeRSCreceivedonaremotelyblockedcircuitToverifythattheIUTisabletoreacttoaResetcircuitmessageforaremotelyblockedcircuit.TSSCSSV/RC/TPIBC_V_1_2_5_aISUP'97reference2.9.3.2/Q.764[13]SelectionexpressionPICSA.13/8Q.784.1[10]reference1.2.5TestpurposeCircuitgroupresetreceivedToverifythatonreceiptofoneCircuitgroupresetmessagetheIUTwillrespondbysendingaCircuitgroupresetacknowledgemessage.TSSCSSV/RC/TPIBC_S_1_2_5_bISUP'97reference2.9.3.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.5TestpurposeCircuitgroupresetreceivedToverifythataCircuitgroupresetmessageisdiscardedbytheIUTiftherearenocircuitsaffectedbythemessage.TSSCSSV/RC/TPIBC_S_1_2_5_cISUP'97reference2.9.3.2/Q.764[13]2.9.3.3i)/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.5TestpurposeCircuitgroupresetreceivedToverifythataCircuitgroupresetmessageisdiscardedbytheIUTiftherearemorethan32circuitsaffectedbythemessage.TSSCSSV/RC/TPIBC_V_1_2_6ISUP'97reference2.9.3.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.6TestpurposeCircuitgroupresetsentToverifythattheIUTisabletogenerateaCircuitgroupresetmessage.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)24TSSCSSV/RC/TPIBC_V_1_2_7ISUP'97reference2.9.3.2.d)/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.2.7TestpurposeCircuitgroupresetreceivedonremotelyblockedcircuitsToverifythattheIUTisabletoreacttoaCircuitgroupresetmessagecorrectlyforremotelyblockedcircuits.TSSCSSV/BC/CGBU/TPIBC_V_1_3_1_1_aISUP'97reference2.8.2/Q.764[13]2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.1TestpurposeCGBandCGUreceived(maintenanceoriented)ToverifythattheCircuitgroupblockingfeature(maintenanceoriented)canbecorrectlyinitiated.TSSCSSV/BC/CGBU/TPIBC_S_1_3_1_1_bISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.1TestpurposeCGBfor0circuitsreceived(maintenanceoriented)ToverifythataCircuitgroupblockingmessage(maintenanceoriented)isdiscardedbytheIUTiftherearenocircuitsaffectedbythemessage.TSSCSSV/BC/CGBU/TPIBC_S_1_3_1_1_cISUP'97reference2.8.2.3ix)/Q.764[13]SelectionexpressionPICSA.13/14Q.784.1[10]reference1.3.1.1TestpurposeCGBformorethan32circuitsreceived(maintenanceoriented)ToverifythataCircuitgroupblockingmessage(maintenanceoriented)isdiscardedbytheIUTiftherearemorethan32circuitsaffectedbythemessage.SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)25TSSCSSV/BC/CGBU/TPIBC_V_1_3_1_1_dISUP'97reference2.8.2/Q.764[13]2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.1TestpurposeCGBandCGUreceived(hardwarefailureoriented)ToverifythattheCircuitgroupblockingfeature(hardwarefailureoriented)canbecorrectlyinitiated.TSSCSSV/BC/CGBU/TPIBC_S_1_3_1_1_eISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.1TestpurposeCGBfor0circuitsreceived(hardwarefailureoriented)ToverifythataCircuitgroupblockingmessage(hardwarefailureoriented)isdiscardedbytheIUTiftherearenocircuitsaffectedbythemessage.TSSCSSV/BC/CGBU/TPIBC_S_1_3_1_1_fISUP'97reference2.8.2.3ix)/Q.764[13]SelectionexpressionPICSA.13/14Q.784.1[10]reference1.3.1.1TestpurposeCGBformorethan32circuitsreceived(hardwarefailureoriented)ToverifythataCircuitgroupblockingmessage(hardwarefailureoriented)isdiscardedbytheIUTiftherearemorethan32circuitsaffectedbythemessage.TSSCSSV/BC/CGBU/TPIBC_V_1_3_1_2_aISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.2TestpurposeCGBandCGUsentToverifythattheIUTisabletogenerateaCircuitgroupblockingmessageandaCircuitgroupunblockingmessage(bothmaintenanceoriented).SIST EN 300 356-32 V3.0.4:2005

ETSIETSIEN300356-32V3.0.4(2000-09)26TSSCSSV/BC/CGBU/TPIBC_V_1_3_1_2_bISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]reference1.3.1.2TestpurposeCGBandCGUsentToverifythattheIUTisabletogenerateaCircuitgroupblockingmessageandaCircuitgroupunblockingmessage(bothhardwarefailureoriented).TSSCSSV/BC/CGBU/TPIBC_V_1_3_1_3ISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]referenceTestpurposeBlockingwithCBG(maintenanceoriented);unblockingwithUBLToverifythatacircuitwhichisblockedbyamaintenanceorientedCircuitgroupblockingmessagecanbeunblockedbyanUnblockingmessage.TSSCSSV/BC/CGBU/TPIBC_I_1_3_1_4ISUP'97reference2.8.2.2/Q.764[13]SelectionexpressionN/AQ.784.1[10]referenceTestpurposeUBLafterCGB(hardwarefailureoriented)Toverifythatahard
...