SIST EN 300 188-6 V1.3.4:2003

• Abstract:

  To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI EN 300 188-6 V1.3.4 (1999-11) - Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

SIST EN 300 188-6 V1.3.4:2003 is the Slovenian adoption of ETSI EN 300 188-6 Version 1.3.4. It defines the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network side of the Integrated Services Digital Network (ISDN) Three-Party (3PTY) supplementary service using the Digital Subscriber Signalling System No. one (DSS1) protocol. It is used by test laboratories and test realizers to check conformance of network implementations at the T reference point, or a coincident S and T reference point, against the 3PTY protocol specification.

What does SIST EN 300 188-6 V1.3.4:2003 specify?

SIST EN 300 188-6 V1.3.4:2003 specifies the network-side ATS and partial PIXIT proforma for 3PTY conformance testing over DSS1. The focus is the network DSS1 protocol entity at the user-network interface, not the whole network.

Clause 1 sets the scope and points to the related network test purpose specification in Part 5. Clause 2 lists the references used by the document, Clause 3 gives the main definitions and abbreviations, and Clauses 4 to 10 cover the test method, ATS conventions, mapping to test purposes, and conformance statements. Annexes A to C are normative and provide the PCTR proforma, partial PIXIT proforma, and ATS; Annexes D and E are informative.

Annex	What it covers
A	Protocol Conformance Test Report (PCTR) proforma
B	Partial PIXIT proforma
C	Abstract Test Suite (ATS)
D	General structure of ATS
E	Change record

What are the key requirements of SIST EN 300 188-6 V1.3.4:2003?

Clause 4 requires a combined remote and multi-party Abstract Test Method (ATM). In practice, that means the test system uses one Main Test Component (MTC) and one or more Parallel Test Components (PTCs), with verdicts assigned from what is observed on the interface under test.

Clause 4 also distinguishes the roles of the MTC and the PTCs. The MTC controls the test and assigns verdicts, while the PTCs stimulate and observe the other interfaces so the network can be driven into the required state; this matters because a failure at a non-tested interface does not automatically become a FAIL verdict.

Clause 4.1.3 gives the remote-user convention used in the ATS. PTC1 is connected to the IUT on the remote-user side, while the MTC stays on the served-user side and receives Coordination Messages (CM); this allows reuse of test steps while keeping verdict control at the MTC.

Clause 5 states that there are no untestable test cases associated with this ATS and ATM. That means the suite is intended to cover all its specified test purposes in a realizable way.

Clause 6 explains how TTCN and ASN.1 are used in the ATS. It defines rules for simple and structured types, ASPs, PDUs, constraints, chaining, and value matching, which matters because implementers need these conventions to build a consistent executable test suite.

Clause 6.2.2 sets the encoding approach for ASN.1 constraints. The default is ISDN encoding for ASN.1 constraint tables, while BER is used only where explicitly indicated; for BER-encoded components, the document requires a variety of length forms during a test campaign.

Clause 7 maps ATS test case identifiers directly to the corresponding test purposes. In practice, that gives a one-to-one trace from the abstract test purpose to the test case name.

Clauses 8 to 10 define conformance expectations for the PCTR, PIXIT, and ATS. Test laboratories and test realizers must preserve the structure of the annexed proformas and produce technically equivalent results.

What terms does SIST EN 300 188-6 V1.3.4:2003 define?

• Abstract Test Suite (ATS) - the abstract set of test cases and behavior descriptions used to assess conformance.
• Implementation Under Test (IUT) - the network implementation being evaluated.
• Main Test Component (MTC) - the test component that controls the test and assigns verdicts.
• Parallel Test Component (PTC) - a supporting test component used to drive or observe other interfaces.
• Point of Control and Observation (PCO) - the point where the test system controls and observes protocol behavior.
• Protocol Implementation Conformance Statement (PICS) - the statement describing what a protocol implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - additional implementation information needed to prepare and run tests.
• System Under Test (SUT) - the complete system that contains the IUT in the testing setup.

Who uses SIST EN 300 188-6 V1.3.4:2003?

SIST EN 300 188-6 V1.3.4:2003 is used by conformance test laboratories, test realizers, and suppliers of ISDN network equipment. It is also relevant to engineers and quality teams preparing a network implementation for 3PTY testing, because the PIXIT items ask for practical details such as access type, call reference length, timer values, and how to stimulate specific network behavior.

The document is especially relevant when preparing an executable test suite, a Means Of Testing (MOT), or a conformance report. Buyers or assessors can use it to understand what information a vendor must provide before network-side 3PTY testing can start.

What changed in SIST EN 300 188-6 V1.3.4:2003 from the previous edition?

The change record states that this version updates the ATS to correct errors. It also records conversion to the EN layout, replacement of references to ETS 300102 with EN 300 403-1, and substitution of non-specific references to the basic standards where the intention is to refer to the latest version.

Which standards are used with SIST EN 300 188-6 V1.3.4:2003?

• EN 300 403-1 - the basic call control protocol specification used as a reference for DSS1 network layer behavior.
• EN 300 188-1 - the main 3PTY protocol specification that this ATS supports.
• EN 300 188-2 - the PICS proforma for the 3PTY service.
• EN 300 188-5 - the network TSS & TP specification linked to this ATS.
• EN 300 196-1 - the generic functional protocol for supplementary services, used for ASN.1 and related data structures.
• ISO/IEC 9646-1 to 9646-5 - the conformance testing framework, including ATS specification, TTCN, test realization, and laboratory requirements.
• ITU-T Recommendation I.411 - the reference configurations for ISDN user-network interfaces.
• CCITT Recommendation X.209 - the Basic Encoding Rules (BER) reference.

What does the SIST EN 300 188-6 V1.3.4:2003 document contain?

The document contains the ATS written in Tree and Tabular Combined Notation (TTCN), with both graphical and machine-processable forms identified in Annex C. It also contains the partial PIXIT proforma and the PCTR proforma used for real test campaigns.

Clause 6 includes declarations for types, parameters, variables, constraints, test suite operations, and test case behavior. The annexes and tables support test development, test execution, and reporting rather than product design, so the document is mainly a test specification and conformance tool.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 188-6 Version 1.3.4SIST EN 300 188-6 V1.3.4:2003en01-december-2003SIST EN 300 188-6 V1.3.4:2003SLOVENSKI
STANDARD
ETSIEN300188-6V1.3.4(1999-11)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);ThreeParty(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworkSIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)2ReferenceREN/SPS-05167-6(1qpi0j2o.PDF)KeywordsISDN,DSS1,supplementaryservice,3PTY,ATS,PIXIT,networkETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/[e-mail]ETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]Ideliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshouldbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute1999.Allrightsreserved.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.84AbstractTestMethod(ATM).94.1DescriptionofATMused.94.1.1ConventionsfortestcomponentsandPCOs.94.1.2Conventionsforvariablesandparameters.114.1.3Conventionsfortheremoteusergroup.114.2AlternativeATM.125Untestabletestpurposes.136ATSconventions.136.1Declarationspart.136.1.1Typedefinitions.136.1.1.1Simpletypedefinitions.136.1.1.2Structuredtypedefinitions.146.1.1.2.1TTCNstructuredtypedefinitions.146.1.1.2.2ASN.1structuredtypedefinitions.146.1.1.3ASPtypedefinitions.156.1.1.3.1TTCNASPtypedefinitions.156.1.1.3.2ASN.1ASPtypedefinitions.166.1.1.4PDUtypedefinitions.166.1.1.4.1TTCNPDUtypedefinitions.166.1.1.4.2ASN.1PDUtypedefinitions.166.1.2Testsuiteconstants.166.1.3Testsuiteparameters.166.1.4Variables.166.1.4.1Testsuitevariables.166.1.4.2Testcasevariables.166.1.5Testsuiteoperationdefinitions.166.2Constraintspart.176.2.1Structuredtypeconstraintdeclaration.176.2.2ASN.1typeconstraintdeclaration.176.2.2.1Specificationofencodingrules.186.2.3ASPtypeconstraintdeclaration.196.2.3.1ASN.1ASPtypeconstraintdeclaration.196.2.3.2TTCNASPtypeconstraintdeclaration.196.2.4PDUtypeconstraintdeclaration.196.2.4.1ASN.1PDUtypeconstraintdeclaration.196.2.4.2TTCNPDUtypeconstraintdeclaration.196.2.5Chainingofconstraints.196.2.5.1Staticchaining.196.2.5.2Dynamicchaining.196.2.6Derivedconstraints.206.2.7Parameterizedconstraints.206.2.8Valueassignment.206.2.8.1Specificvalues.206.2.8.2Matchingvalues.206.3Dynamicpart.21SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)46.3.1Testcases.216.3.2Teststeps.216.3.2.1PTC1_IN.216.3.2.2PTC1_OUT.216.3.3Defaults.217ATStoTPmap.218PCTRconformance.219PIXITconformance.2210ATSconformance.22AnnexA(normative):ProtocolConformanceTestReport(PCTR)proforma.23A.1Identificationsummary.23A.1.1Protocolconformancetestreport.23A.1.2IUTidentification.23A.1.3Testingenvironment.23A.1.4Limitsandreservations.24A.1.5Comments.24A.2IUTconformancestatus.24A.3Staticconformancesummary.24A.4Dynamicconformancesummary.24A.5Staticconformancereviewreport.25A.6Testcampaignreport.25A.7Observations.26AnnexB(normative):PartialPIXITproforma.27B.1Identificationsummary.27B.2Abstracttestsuitesummary.27B.3Testlaboratory.27B.4Client(ofthetestlaboratory).28B.5SystemUnderTest(SUT).28B.6Protocolinformation.29B.6.1Protocolidentification.29B.6.2Parametervalues.29B.6.3ActionsrequiredtostimulateIUT.29B.6.4ConfigurationofIUT.30B.6.5Timervalues.30B.7BasiccallPIXITitems.31B.7.1Parametervalues-informationelementcodings.31SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)5AnnexC(normative):AbstractTestSuite(ATS).32C.1TheTTCNGraphicalform(TTCN.GR).32C.2TheTTCNMachineProcessableform(TTCN.MP).32AnnexD(informative):GeneralstructureofATS.33AnnexE(informative):Changerecord.34E.1ChangeswithrespecttoEN300188-6(V1.2).34E.2ChangeswithrespecttoETS300188-6(Ed.1).34History.35SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeSignallingProtocolsandSwitching(SPS).Thepresentdocumentispart6ofamulti-partstandardcoveringtheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolspecificationfortheIntegratedServicesDigitalNetwork(ISDN)ThreeParty(3PTY)supplementaryservice,asdescribedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part5:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part6:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".Thepresentversionupdatesthereferencestothebasiccallspecifications.NationaltranspositiondatesDateofadoptionofthisEN:5November1999DateoflatestannouncementofthisEN(doa):29February2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2000DateofwithdrawalofanyconflictingNationalStandard(dow):31August2000SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)71ScopeThissixthpartofEN300188specifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[11])ofimplementationsconformingtothestagethreestandardfortheThreeParty(3PTY)supplementaryserviceforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN)bymeansoftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocol,EN300188-1[2].EN300188-5[4]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproformaspecification.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300188-1[2].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]EN300403-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part1:Protocolspecification[ITU-TRecommendationQ.931(1993),modified]".[2]EN300188-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[3]EN300188-2(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[4]EN300188-5(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Three-Party(3PTY)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".[5]EN300196-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[6]ISO/IEC9646-1:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[7]ISO/IEC9646-2:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[8]ISO/IEC9646-3:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[9]ISO/IEC9646-4:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)8[10]ISO/IEC9646-5:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[11]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referencesconfigurations".[12]CCITTRecommendationX.209(1988):"SpecificationofbasicencodingrulesforAbstractSyntaxNotationOne(ASN.1)".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[6]ImplementationUnderTest(IUT):seeISO/IEC9646-1[6]LowerTester(LT):seeISO/IEC9646-1[6]PointofControlandObservation(PCO):seeISO/IEC9646-1[6]ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[6]PICSproforma:seeISO/IEC9646-1[6]ProtocolImplementationeXtraInformationforTesting(PIXIT):seeISO/IEC9646-1[6]PIXITproforma:seeISO/IEC9646-1[6]SystemUnderTest(SUT):seeISO/IEC9646-1[6]UpperTester(UT):seeISO/IEC9646-1[6]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:3PTYThreePartyASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBERBasicEncodingRulesCMCo-ordinationMessageCPCo-ordinationPointExTSExecutableTestSuiteIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingMTCMainTestComponentPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingPTCParallelTestComponentSUTSystemUnderTestSIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)9TPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTester4AbstractTestMethod(ATM)4.1DescriptionofATMusedTherequirementfortestingthenetworkIUTistofocusonthebehaviourofthenetworkIUTattheuser-networkinterfacewhereaTreferencepointorcoincidentSandTreferencepointapplies.ThustheIUTisthenetworkDSS1protocolentityataparticularuser-networkinterfaceandisnotthewholenetwork.ItispossibletospecifyanATSbasedonaSingleparty(remote)testmethodforsuchanIUT.However,itisconsideredthatanATSbasedonsuchanapproachisoflimiteduseastheonlywaytospecifyIUTgeneratedPDUsistousethe"implicitsend"statement.ManyusersofsuchanATSwouldreplacethe"implicitsend"statementswithdescriptionsofthebehaviouratotherinterfaces.AnATSbasedonamulti-partytestmethodisconsideredtobemoreusefulinthatitisclosertohowarealtestsuitewouldbeconstructed.Suchatestmethodspecifiesbehaviouratmultiplenetworkinterfaces.Oneveryimportantlimitationhereisthattestsarefocusedononeparticularinterface.ThusthetestsystemismadeuponeMainTestComponent(MTC)andoneormoreParallelTestComponents(PTC),seefigure1.4.1.1ConventionsfortestcomponentsandPCOsMasterpartSlavepartMTCAPTC2CPA2PTC1CPA1L0PCOL1PCOL2PCOIUTNETWORKFigure1:Multi-partytestmethodSIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)10Inamaster/slavearrangement,theMTCisconsideredtobethemasterwhilethePTCsaretheslaves.The"slave"testersareonlyanexplicitdescriptionofhowtodealwiththe"other"interfacesduringthetestingprocess,i.e."howtomaketheIUTsendtherequiredmessage".Thismeans,inparticular,thattheverdictwillonlybeassignedfromtheprotocolaspectsobservedontheinterfaceundertest(i.e.bythe"master"tester),asitwouldbeobservedbyaterminalconnectedtothisinterface.Afailureinthecorrelationbetweentheprotocolatthedifferentinterfacestowhichthedifferenttestersareconnected,i.e.inthemechanismofthefunctionalserviceitself,willnotcauseaFAILverdict.Forinstance,iftheIUTfailstosendamessageonthetestedinterfaceafteranotherinterfacehasreceivedtheproperstimulus,theverdictwillbeINCONCLUSIVE.TheMTCMTCAhastwofunctionsinthisconfiguration.Firstly,ithastheMTCfunctionofcontrollingtheoneormorePTCs.ThusitisresponsibleforstartingthePTCsandafterwardsco-ordinatesactivitiesbyexchangingCo-ordinationMessages(CM)withthePTCs.SecondlyitisresponsibleforthebehaviouroftheLowerTester(LT)atPCOL0.Acombinationoftheremoteandmulti-partytestmethodsisapplied.Ascanbeseenfromfigure1,severalPCOsareused.AllPCOsresideattheserviceaccesspointsbetweenlayers2and3.MTCSUTPTC1,2Layer3Layer2Layer1L0IUTL1,2Layer3Layer2Layer1ServiceproviderFigure2:Combinationoftheremoteandmulti-partytestmethodsTheMTCPCOisnamed"L0"("L"forLower).TheL0PCOisusedtocontrolandobservethebehaviouroftheIUTandtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.ThePTCsPTC1,PTC2etc.usePCOsL1,L2etc.ThesePCOsareusedtocontroland,inalimitedway,observethebehaviourofthenetworkequipmentatinterfacesotherthantheoneundertest.NoverdictsareassignedatthesePCOs.Asstatedinapreviousparagraph,thenon-receiptofnetworkgeneratedmessagesatL0,whicharestimulatedbyeventsattheL1,L2etc.,willresultinINCONCLUSIVEratherthanFAILverdictsbeingassigned.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)114.1.2ConventionsforvariablesandparametersMTCAcallreferenceCREF1Bchannel(basic)bch_num1(toPTC1)channelnr(primary)CH_NUM1callreferenceCREF2Bchannel(basic)bch_num2(toPTC2)channelnr(primary)CH_NUM2PCOL0IPN0,LIPN0PTC1callreferenceP1CREFBchannel(basic)P1_bch_numchannelnr(primary)P1_CH_NUMPCOL1IPN1,LIPN1PTC2callreferenceP2CREFBchannel(basic)P2_bch_numchannelnr(primary)P2_CH_NUMPCOL2IPN2,LIPN24.1.3ConventionsfortheremoteusergroupForthisgroup,thesideofthenetworkwhichisbeingtestediswheretheconferenceremoteuserisconnected.ThemostconvenientapproachhereistoconnectPTC1totheIUT.TheMTCis,asfortheservedusergrouptestcases,connectedattheservedusersideofthenetwork.Thisapproachallowsthereuseofteststepsdevelopedfortheservedusergrouptests.Thisapproach,representingaslightmodificationinthetestmethod,isillustratedinfigure3.ThisshowsthatthepartofthenetworkconsideredtobetheIUTisconnectedtoPTC1ratherthanMTC1.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)12MasterpartSlavepartMTCAPTC2CPA2PTC1CPA1L0PCOL1PCOL2PCOIUTNETWORKFigure3:Multi-partytestmethod-modifiedforremoteusertestsThePTC1isusedtoobservethenotificationssentbythenetwork.TheteststepPTC1_remoteUser_CR1isusedtocheckthereceiptofthenotificationanddependingontheresultsendsaCMbacktotheMTC.TheMTCthenissuesaverdictdependingontheCMreceivedfromthePTC1.ThisisdoneinordertomaintaintheconventionthattheMTCisonlyallowedtoissueverdicts.However,oneconsequenceofthisisthatanybehaviourattheservedusersidewhichisnon-conformingwillresultinaFailverdictbeingissuedeventhoughthefocusofthetestsisattheremoteuserside.Thisconstraintisviewedasacceptablegiventhefactthatinanycasethenetworkshallprovideaconformingserveduserinterfaceaswellasoneormoreconformingremoteuserinterfaces.4.2AlternativeATMAsstatedinsubclause4.1,anATSbasedonasingle-party(remote)ATMispossible.SuchanATSmaybegeneratedfromtheonespecifiedinthepresentdocument.Thefollowinggeneralstepsshouldbetaken:1)removeallPTCbehaviour;2)removeallCREATEstatements;3)replaceCMswhichareusedtoprovokePDUsattheMTC,withimplicitsendstatements.Anexample,showingthedifferencebetweenthemulti-partyATMandsingle-partyATMforasingletestcase,isgivenintables1and2.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)13Table1:Testcasedynamicbehaviourtableusingmulti-partyATMTESTCASEDYNAMICBEHAVIOURTestCaseNameHOLD_N04_001GroupRemoteUser_ST_OR_T/Holding/PurposeEnsurethattheIUT,whileintheActivecallstateN10,tonotifythenon-serveduserthatthecallisheldsendsaNOTIFYmessagewithanotificationindicatorcodedas"remotehold"touserBandremainsintheActivecallstate.DefaultDF69901(1)ConfigurationCONFIG1Comments9.2.1validoptionalNr|Label|BEHAVIOURDESCRIPTION|CREF|V|COMMENTS1||CREATE(PTC1:PTC1_IN_servedUser)|||2||+PR31002|||preambleN103||CPA1!CP_MSTARTTWAIT|S_HL||4||L0?NOTIFYr|A_NO20(CREF1,hold_NID)|(P)|5||+CS59901(10,1)|||checkN106||?TIMEOUTTWAIT||(I)|7||+PO49901(1)|||postambleN0DETAILEDCOMMENTS:Table2:Testcasedynamicbehaviourtableusingsingle-partyATMTESTCASEDYNAMICBEHAVIOURTestCaseNameHOLD_N04_001GroupRemoteUser_ST_OR_T/Holding/PurposeEnsurethattheIUT,whileintheActivecallstateN10,tonotifythenon-serveduserthatthecallisheldsendsaNOTIFYmessagewithanotificationindicatorcodedas"remotehold"touserBandremainsintheActivecallstate.DefaultDF69901(1)ConfigurationComments9.2.1validoptionalNr|Label|BEHAVIOURDESCRIPTION|CREF|V|COMMENTS1||+PR31002|||preambleN102|||NO20(CREF1,hold_NID)||3||L0?NOTIFYr|A_NO20(CREF1,hold_NID)|(P)|4||+CS59901(10,1)|||checkN105||?TIMEOUTTWAIT||(I)|6||+PO49901(1)|||postambleN0DETAILEDCOMMENTS:5UntestabletestpurposesTherearenountestabletestcasesassociatedwiththisATSandATM.6ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.However,thenamesofthesubclausesarearrangedinawaymoresuitabletothepresentdocument.6.1Declarationspart6.1.1Typedefinitions6.1.1.1SimpletypedefinitionsWhereappropriate,simpletypeshavealength,avaluelistorarangerestrictionattached.Simpletypesdefinedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionoravaluelistattached.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)14Simpletypes,definedasbeingofINTEGERtype,haveavaluelistorarangerestrictionattached.6.1.1.2Structuredtypedefinitions6.1.1.2.1TTCNstructuredtypedefinitionsAllstructuredtypedefinitionsareprovidedwithafullname.Allelementsineverystructuredtypedefinition,definedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionattached.Ifanelementinastructuredtypedefinitionisdefinedasbeingofareferencedtype,the(possible)restrictionisdefinedinthatreferencedtype.Forinformationelementstheidentifier,whichisuniqueforeachelement,hasitstypedefinedasasimpletypewherethevaluelistisrestrictedtothesinglevaluewhichistheidentifieritself.ThishastheadvantagethatitallowsatestsystemderivedfromthisATStoeasilyidentifyinformationelementsembeddedinmessages.AnATSwhereinformationelementidentifiersarerepresentedasunrestrictedtypescanpresentdifficultiesforaderivedtestsysteminthecasewhereitneedstofindoneinformationelementembeddedinanumberofothersandtheconstraintsfortheotherelementshavetheany-or-omitvalue.Insuchacasethetestsystemcannoteasilyfindthebeginningofeachinformationelement.6.1.1.2.2ASN.1structuredtypedefinitionsASN.1hasbeenusedforthreemajorreasons.First,typesdefinedinASN.1canmodelproblemsthat"pure"TTCNcannot.Forinstance,datastructuresmodellingorderedorunorderedsequencesofdataarepreferablydefinedinASN.1.Second,ASN.1providesabetterrestrictionmechanismfortypedefinitionsbyusingsub-typedefinitions.Third,itisnecessarytouseASN.1toreproducethetypedefinitionsforremoteoperationcomponentsasspecifiedinthebasestandards.ThefactthatASN.1providesabetterrestrictionmechanismfortypedefinitionsisusedforthepurposeofachievingtype-compatibility.Tables3and4showthetypicaluseofASN.1.TheFIEtypeintable3iswritteninASN.1topermittheuseoftheSETOFconstructioninthecomponentsfield.ConstraintsoftheFIEtypecanthereforebewrittenusingtheSUPERSETfunctionwhichallowstomatchasinglecomponentwhichmaybedeliveredtogetherwithasetofothercomponents.Table4showstherejectcomponenttypewhichisdefinedfollowingtheASN.1declarationinEN300196-1[5].Table3:ASN.1typedefinitionFIEASN.1TypeDefinitionTypeName:FIEComments:FacilityinformationelementtakenfromEN300196-1;11.2.2.1.Specifiedhereforbothsend&receiveevent.TypeDefinitionSEQUENCE{informationElementIdentifierFIE_I,lengthFIE_LengthType,extBitBITSTRING(SIZE(1)),spareBitsBITSTRING(SIZE(2)),protocolProfileBITSTRING(SIZE(5)),componentsSETOFComponent}SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)15Table4:ASN.1typedefinitionRejectComponentASN.1TypeDefinitionTypeName:RejectComponentComments:RejectComponentisnotspecifictoanyparticularoperation.TheinvokeIDmaybeusedtoidentifyaspecificoperation.TypeDefinitionSEQUENCE{invokedIDCHOICE{invokeIDInvokeIDType,nullNULL},problemCHOICE{generalProblem[0]IMPLICITGeneralProblem,invokeProblem[1]IMPLICITInvokeProblem,returnResultProblem[2]IMPLICITReturnResultProblem,returnErrorProblem[3]IMPLICITReturnErrorProblem}}Table5showsanexampleofhowASN.1canbeusedtomodelunorderedsequences.Table5:ASN.1typedefinitionFIESASN.1TypeDefinitionTypeName:FIESComments:TypeDefinitionSETOFFIEThepossibilitytouseTTCNandASN.1incombinationisused,i.e.referringtoanASN.1typefromaTTCNtype.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.TherelationshipbetweenanASPtypeandaPDUtypeisone-to-one.Thatis,thereexistsoneASPtypedefinitionforeachPDUtypedefinition(ifthatASPtypecontainsaPDU).AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SomeASPsarenotparameterizedasshownintheexampleintable6.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.Table6:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:Table7showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table7:TTCNASPtypedefinitionDL_DATA_RQ_ALERTTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ_ALERT(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|ALERT_PDU|DetailedComments:SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)166.1.1.3.2ASN.1ASPtypedefinitionsTherearenoASN.1ASPtypedefinitionsintheATS.6.1.1.4PDUtypedefinitions6.1.1.4.1TTCNPDUtypedefinitionsTheTTCNPDUtypereflectstheactualdatabeingtransferredorreceived.AllPDUsareembeddedinASPs.IfaspecificPDUtypedefinitioncontainselementsdefinedintermsofapre-definedtype,thatelementhasarestrictionattachedtoit.6.1.1.4.2ASN.1PDUtypedefinitionsTherearenoASN.1PDUtypedefinitionsintheATS.6.1.2TestsuiteconstantsNotestsuiteconstantsareusedordefinedinthisATS.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.6.1.4Variables6.1.4.1TestsuitevariablesNotestsuitevariablesareusedordefinedinthisATS.6.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.6.1.5TestsuiteoperationdefinitionsThedescriptionpartofatestsuiteoperationdefinitionuseseithernaturallanguageormetaC.Table8:TestsuiteoperationdefinitionASSIGN_CHITestSuiteOperationDefinitionOperationName:ASSIGN_CHI(basic,primary:CHI;basic_flag:BOOLEAN)ResultType:CHIComments:ThisoperationisusedtoassignacorrectChannelidentificationinformationelementtoPDUsdependentonthetypeofaccessthatistested.Description{if(basic_flag)returnbasic;elsereturnprimary}Detailedcomments:SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)17Thetestsuiteoperationdefinitionshownintable8isusedintheconstraintspartwhenassigninganelementoftypeCHIavalue.Aspreviouslydescribed,theCHItypecanbedefinedintwowaysdependingonwhethertheATSistestingbasicorprimaryrateaccess.ThisoperationisusedtoassignavaluetoanelementofCHItype.Ittakesthreeparameters:ThisoperationreturnsthecorrectconstraintaccordingtotheBooleanflagbasic_flag.ThatconstraintwillthenbeassignedtothespecificelementoftypeCHI.6.2Constraintspart6.2.1StructuredtypeconstraintdeclarationForeverystructuredtypedefinitionthereexistsoneormorestructuredtypeconstraint.6.2.2ASN.1typeconstraintdeclarationConstraintsofthistypeareusedtoassignthecorrespondingtypeaspecificvalue.TheseconstraintsareusedforthepurposeofmodellingunordereddataorspecifictypesthatcannotbeexpressedinTTCN.AvalueassignedtoanelementoftypeSETOFdiffersdependingonwhetheritisasendorreceiveconstraint.Table9:ASN.1typeconstraintdeclarationfIEs(sendconstraint)ASN.1TypeConstraintDeclarationConstraintName:fIEs(comp:Component)ASN.1Type:FIEDerivationPath:Comments:SendFIEwhichwillcontainonecomponent"comp".Description{informationElementIdentifier'00011100'B,lengthCALC_FIE_LENGTH(comp),extBit'1'B,spareBits'00'B,protocolProfile'10001'B,components{comp}}Detailedcomments:NOTE1:Thelastelementintheconstraint,components,isoftypeSETOFComponentwhereComponentisstructureddataofsometype.Iftheconstraintisasendconstraint(asintable9)thevalueforthecomponentelementisstatedas"{comp}"wherecompisanargumentreceivedasaparameter.The"{"and"}"turnsthevalueintoaSETOFvaluewhichiscorrectaccordingtothatelement'stypedefinition.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)18Table10:ASN.1typeconstraintdeclarationfIEr(receiveconstraint)ASN.1TypeConstraintDeclarationConstraintName:fIEr(comp:Component)ASN.1Type:FIEDerivationPath:Comments:AreceivedFIEwhichcancontainseveralcomponents,butwhichcontainsatleast"comp".Description{informationElementIdentifier'00011100'B,length'????????'B,extBit'1'B,spareBits'00'B,protocolProfile'10001'B,componentsSUPERSET({comp})}Detailedcomments:NOTE2:Thelastelementintheconstraint,components,isoftypeSETOFComponentwhereComponentisstructureddataofsometype.Iftheconstraintisareceiveconstraint(asintable10)thecorrespondingmatchingvalueisassignedbyusingSUPERSET.Thekey-wordSUPERSEThasanargumentthatistypecompatiblewiththetypedefinitionofthatfield.Intable10,theelementnamedcomponentsisdefinedas"SETOFComponent"andthisimpliesthattheargumenttoSUPERSETshouldbeoftypeSETOFComponent.Thisisachievedthesamewayasforsendconstraints,enclosingthevalueincurlybrackets.ThesemanticofSUPERSETisstatedinISO/IEC9646-3[8],subclause11.6.4.7.Inshortitdefinesthesemanticasfollows:"AvaluethatusesSUPERSETmatchestheincomingvalueif,andonlyif,theincomingvaluecontainsatleastalloftheelementsdefinedwithintheSUPERSET,andmaycontainmoreelements."ThisisexactlythesemanticdefinitionusedinthisATS.6.2.2.1SpecificationofencodingrulesAtthetimeofspecifyingthisATSthemechanismsrelatedtoencodingofASN.1types,specifiedinDAM-2ofISO/IEC9646-3[8],werenotyetstable.NeverthelessasthereisavariationintheencodingrulesasappliedtoASN.1typesandconstraintsspecifiedinthisATS,amechanismisusedtodifferentiatethedifferentencodingrules.Giventhenon-finalizedstatusofDAM-2,asolutionwhichisbroadlyinthespiritofDAM-2hasbeencreated.Commentfieldshavebeenusedasameansofincludingtheencodingrules.ForASN.1usedinthisATS,twovariationsofencodingrulesareused.OneisthecommonlyknownBasicEncodingRules(BER)asspecifiedinCCITTRecommendationX.209[12].InthesecondcasetheencodingisaccordingtoISDN,i.e.theASN.1datatypesarearepresentationofstructurescontainedwithintheISDNspecification(basiccall,Genericfunctionalprotocolorindividualsupplementaryservice).Forexample,ifoctetsofaninformationelementarespecifiedinASN.1asaSEQUENCEthenthisshouldbeencodedinanExecutableTestSuite(ExTS)asanyotherISDNinformationelementspecifiedusingtabularTTCN.ThisISDNencodingvariationisthedefaultencodingruleforthisATS.ThismeansthatallASN.1constrainttablesareencodedusingISDN(non-BER)encodingunlessstatedotherwise.BERencodingshouldneverbeappliedtoanASN.1constraintwhereBERencodinghasnotbeenspecified.ForBERencoding,anindicationisgiveninthecommentsfieldofthetableheader.ForthisATSsuchindicationsappearintheASN.1typeconstraintdeclarationtablesonly.Inthefirstlineofthetableheadercommentfield,thenotation"ASN1_Encoding:BER"isused.NotethatwithinBER,thereareanumberofvariationsfortheencodingoflengthsoffields.AccordingtoEN300196-1[5],anIUTshouldbeabletointerpretalllengthformswithinBERforreceivedPDUs.WhensendingPDUscontainingBERencoding,EN300196-1[5]givesguidelinesbutmakesnorestrictionsonthelengthformswithinBERwhichanIUTmayapply.InrelationtocomponentssentbythetestertotheIUT,implementorsofthisATSshalluseavarietyoflengthformssuchthatatleastoneofeachofthelengthformsissenttotheIUTduringatestcampaign.Thevariationsoflengthformstobeusedareindefinite,shortdefiniteandlongdefinite.InthisparticularATSallASN.1typeconstraintswhichareoftype"Component"aretobeencodedusingBER.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)19Table11:ASN.1typeconstraintdeclarationshowinguseofencodingvariationASN.1TypeConstraintDeclarationConstraintName:Beg3PTYinvASN.1Type:ComponentDerivationPath:Comments:ASN1_Encoding:BERReceivecomponent:Begin3PTYinvokecomponentDescriptionbegin3PTY_Componentsbegin3PTY_InvokeComp{invokeID?,operation_valuelocalValue4}Detailedcomments:6.2.3ASPtypeconstraintdeclaration6.2.3.1ASN.1ASPtypeconstraintdeclarationNoASN.1ASPtypeconstraintdeclarationexistsinthisATS.6.2.3.2TTCNASPtypeconstraintdeclarationForTTCNASPconstraintdeclarationsthereisaone-to-onerelationshipbetweenitstypeandtheconstraint.Thatis,thereisonlyoneconstraintforeachTTCNASPTypeDeclaration.ThereasonforthisisthattheASPsareusedonlyforcarryingaspecificPDUvalue.ThemanyASPconstraints(andtypes)couldhavebeenavoidedbyusingthemetatypePDU,butthatwasnotsuitableasvaluesinsideaspecificPDUhavetobereferenced.ToreferenceelementsinsideavalueofmetatypePDUisnotallowedaccordingtoISO/IEC9646-3[8],soeachASPhastobedefinedashavingaparameterofaspecificPDUtype.InallASPconstraintstheembeddedPDUconstraintiseitherchainedstaticor"semi-dynamic".Thatis,thePDUconstraintisalwaysfixedtoaspecificASPconstraintbutit(thePDU)maybeparameterized.AllASPconstraintshaveaspecificvalueforitsparameter.NomatchingsymbolsareusedinASPs.6.2.4PDUtypeconstraintdeclaration6.2.4.1ASN.1PDUtypeconstraintdeclarationNoASN.1PDUtypeconstraintdeclarationexistsinthisATS.6.2.4.2TTCNPDUtypeconstraintdeclarationPDUconstraintsareusedforassigningvaluesorpatternstothedatabeingsentorreceived.6.2.5Chainingofconstraints6.2.5.1StaticchainingStaticchaining,thatisafixedreferencetoaspecificconstraint,isusedinthisATS.Thestaticchainingisusedforstaticbindingofbothvariablesandsub-structures.6.2.5.2DynamicchainingDynamicchainingisachievedwhenhavingareferencetoavaluewhichisunknown.Theonlythingknown(beforerun-time)isthetypeofthatreference.Thereferenceispassedasaparameter.StrictdynamicchainingisnotusedinthisATS.Whatisusedissomethingthatiscalled"semi-dynamicchaining".Thedefinitionofsemi-dynamicchainingisthatthefixedreferenceisparameterizedwithanunknownvalue.Thatvalueisreceivedasaparameter.SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)20Table12:TTCNASPconstraintdeclarationA_RST1TTCNASPConstraintDeclarationConstraintName:A_RST1(FLAG:INTEGER)ASN.1Type:DL_DAT_IN_RESTARTrDerivationPath:Comments:ParameterNameParameterValueCommentsmunRST1(FLAG)RST1(FLAG)Detailedcomments:Table12isanexampleofsemi-dynamicchaining.TheTTCNASPconstraintisparameterizedwithanINTEGERvaluenamedFLAG.ThatvalueispassedfurtherdowninthestructureasaparametertoastaticnamedPDUconstraintreference.6.2.6DerivedconstraintsNoderivationofanyconstraintisused.Allconstraintsareconsideredtobebaseconstraints.6.2.7ParameterizedconstraintsParameterizedconstraintsareusedinthisATS.6.2.8Valueassignment6.2.8.1SpecificvaluesForspecificvalueassignmentbothexplicitvaluesandreferencestoexplicitvaluesareused.6.2.8.2MatchingvaluesAsmatchingvaluesthefollowingmechanismsareused:InsteadofValue:AnyOrOmit"*"AnyValue"?"Omit"-"Insidevalue:AnyOne"?"AnyOrNone"*"SIST EN 300 188-6 V1.3.4:2003

ETSIETSIEN300188-6V1.3.4(1999-11)216.3Dynamicpart6.3.1TestcasesEachtestcasecontainsthetestpurposetextfromEN300188-5[4].Tobeabletoreadandunderstandthetestcasedynamicbehaviouritisrecommendedthattheteststepsareunderstoodfirst.6.3.2Teststeps6.3.2.1PTC1_INThisteststepdescribesthebehaviourofthePTC1forsupportofanincomingcallattheMTC(serveduserside).ThusPTC1istheoriginatorofthecall.ThePTC1receivesaCMfromtheMTCinordertosendtheSETUPmessagewhichbeginsthecallestablishment.TheteststepisterminatedbyreceiptofaRELEASEmessageorbyapprop
...