SIST EN 300 356-32 V3.0.4:2005
(Main)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
General Information
- 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
- 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
Overview
SIST EN 300 356-32 V3.0.4:2005 is a Slovenian national adoption of a European standard developed by ETSI, focusing on the Integrated Services Digital Network (ISDN) and, more specifically, the Signalling System No.7 (SS7) ISDN User Part (ISUP) version 3. This standard specifies the Test Suite Structure and Test Purposes (TSS&TP) for basic call services at the international interface level. Its main goal is to provide a common framework for testing and validating ISUP implementations, ensuring compliance, interoperability, and reliability between network nodes.
The conformance and validation test specifications outlined in this document are essential for network operators, equipment manufacturers, and testing laboratories to verify that ISUP protocol implementations correctly support basic call control and signaling procedures as defined in related ITU-T and ETSI recommendations.
Key Topics
The standard covers core aspects necessary for structured testing of ISUP version 3, including:
- Test Suite Structure (TSS): Establishes the organization of test cases for ISUP v3, focusing on areas such as circuit supervision, call setup, call release, unsuccessful call attempts, abnormal situations, special call handling, bearer services, user flow control, echo control, and temporary alternative routing.
- Test Purposes (TP): Defines and classifies the objectives for each test, ensuring all expected, exceptional, and invalid behaviors of the ISUP node under test are validated.
- Testing Methodology: Details the configuration and approach for validating different types of exchanges (such as local, intermediate, and gateway exchanges) using abstract test methods, mainly distributed multiparty testing.
- Naming Conventions & Structure: Uses consistent identifiers and naming schemes for test parameters, cases, constraints, and steps to facilitate clarity and maintain test integrity.
- Pre-test Conditions: Specifies initial state requirements or particular data arrangements needed for certain tests to be valid.
- Abstraction and Reusability: Employs abstract test cases and operations to promote reusability and easier adaptation to various ISUP implementations.
Applications
This standard has practical applicability in a variety of scenarios, including:
- Equipment Certification: Ensures telecommunication switches and network nodes conform to ISUP v3 standards, minimizing integration issues across international interfaces.
- Interoperability Testing: Provides a reliable test framework for manufacturers and service providers needing to demonstrate interoperability between multi-vendor ISUP implementations.
- Network Evolution and Upgrades: Assists network operators when upgrading or migrating legacy ISDN infrastructure by verifying that new equipment supports basic ISUP call procedures as required by international standards.
- Conformance Assessment: Used by testing laboratories and quality assurance teams as a reference to systematically validate ISUP implementations, reducing error rates in deployment and service.
- Protocol Development: Supports protocol engineers in implementing and debugging ISUP functionalities by outlining specific test cases for normal and abnormal signaling behaviors.
Related Standards
Understanding SIST EN 300 356-32 V3.0.4:2005 is often complemented by familiarity with related standards and frameworks, including:
- EN 300 356-1: ISUP v3 basic services specification (reference for call control procedures)
- EN 300 356-31: Protocol Implementation Conformance Statement (PICS) for ISUP v3
- EN 300 356-33: ISUP v3 Abstract Test Suite (ATS) and PIXIT proforma for basic services
- EN 300 008-1: Message Transfer Part (MTP) protocol for international interconnection
- ITU-T Recommendations (e.g., Q.764, Q.762, Q.763, Q.784.1): International framework and guidance for ISUP signaling, test methods, and protocol validation
- ISO/IEC 9646 series: General methodology for OSI conformance testing
Summary
SIST EN 300 356-32 V3.0.4:2005 is a vital standard for the telecommunications sector, providing a robust and internationally aligned framework for ISUP v3 protocol validation. By defining rigorous test structures and precise test purposes, it ensures basic ISDN call services operate consistently and reliably across diverse network environments, supporting global interoperability and service quality.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 356-32 V3.0.4:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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". This standard covers: Definition of ISUP version 2 tests in order to support interoperability & validation for nodes having implemented basic services.
Definition of ISUP version 2 tests in order to support interoperability & validation for nodes having implemented basic services.
SIST EN 300 356-32 V3.0.4:2005 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 356-32 V3.0.4:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
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.:+33492944200Fax:+33493654716SiretN°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:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.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
...