SIST EN 300 403-7 V2.1.2:2005
(Main)Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 7: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network
General Information
- Abstract
To handle comments and incorporate appropriate corrections into the ATS.
- Status
- Published
- Publication Date
- 31-Dec-2004
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Jan-2005
- Due Date
- 01-Jan-2005
- Completion Date
- 01-Jan-2005
Overview
SIST EN 300 403-7 V2.1.2:2005 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for network implementations of the Digital Subscriber Signalling System No. one (DSS1) protocol. DSS1 supports the signalling network layer for circuit-mode basic call control in the Integrated Services Digital Network (ISDN).
This Slovenian standard, identical to the European Standard EN 300 403-7, ensures conformity and interoperability of network-side DSS1 implementations by providing a rigorous testing framework. The standard is part of a multi-part specification for ISDN signalling and focuses specifically on the validation and conformance assessment of the network layer, enabling robust and reliable communications within pan-European ISDN services.
Key Topics
- Abstract Test Suite (ATS): Defines a comprehensive set of abstract test cases to verify the conformance of network-side DSS1 protocol implementations. The ATS is based primarily on multi-party test methods, closely mirroring real-world network test environments.
- PIXIT Proforma: Provides a structured template for gathering additional protocol implementation information needed for effective testing. This helps tailor test suites to specific configurations or implementation details.
- Testing Methodology: Utilizes standardized testing approaches, including clear conventions for test case structuring, test step sequencing, and outcome verdicts, all based on established ISO/IEC conformance testing frameworks.
- Network Layer Conformance: The focus is on the network side of the T reference point as described in ITU-T Recommendation I.411, ensuring all implementations adhere to key ISDN signalling requirements for circuit-mode calls.
- Protocol Conformance Test Report (PCTR): Outlines the format for documentation and reporting of test results to ensure transparency, reproducibility, and compliance.
Applications
- ISDN Network Equipment Vendors: Provides guidelines and test cases for validating conformity of network-side products implementing DSS1 call control protocols.
- Test Laboratories: Offers a repeatable and standardized approach for setting up test environments, executing abstract test cases, and reporting results using the PCTR and PIXIT proformas.
- Certification Bodies: Facilitates product conformance assessment against EN 300 403-7, serving as a key reference in the product certification process.
- Network Operators: Ensures that network-side signalling implementations are interoperable and robust by requiring suppliers to demonstrate compliance with validated ATS and PIXIT processes.
Practical benefits include clear definitions of test roles, accurate mapping from test purposes to test cases, and guidance for handling special configurations such as point-to-multipoint networks. This translates to reduced risk of interoperability issues and helps maintain consistent service quality across ISDN platforms.
Related Standards
The following standards are closely linked to SIST EN 300 403-7 V2.1.2:2005 and together form the comprehensive ISDN DSS1 protocol testing and specification suite:
- EN 300 403-1: Protocol specification for DSS1 network layer (incorporating ITU-T Q.931).
- ETS 300 403-2: Specification and Description Language (SDL) diagrams for DSS1.
- ETS 300 403-3: Protocol Implementation Conformance Statement (PICS) proforma for DSS1 implementations.
- EN 300 403-6: Test Suite Structure and Test Purposes (TSS&TP) for the network side.
- ISO/IEC 9646 Series: International framework for OSI conformance testing, covering methodology, abstract test suite specification, TTCN notation, test realization, and requirements for test laboratories.
- ITU-T Recommendation I.411: Defines ISDN user-network interfaces and reference configurations.
By adhering to SIST EN 300 403-7 and its related standards, organizations are better equipped to ensure the quality, compatibility, and regulatory compliance of ISDN network solutions-promoting seamless digital communications across Europe.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
ANCE
Mexican certification and testing association.
Sponsored listings
Frequently Asked Questions
SIST EN 300 403-7 V2.1.2:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 7: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network". This standard covers: To handle comments and incorporate appropriate corrections into the ATS.
To handle comments and incorporate appropriate corrections into the ATS.
SIST EN 300 403-7 V2.1.2:2005 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN); 35.100.30 - Network layer. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 403-7 V2.1.2: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.RPUHåMHIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 7: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network35.100.30Omrežni slojNetwork layer33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 300 403-7 Version 2.1.2SIST EN 300 403-7 V2.1.2:2005en01-januar-2005SIST EN 300 403-7 V2.1.2:2005SLOVENSKI
STANDARD
ETSIEN300403-7V2.1.2(2000-02)EuropeanStandard(Telecommunicationsseries)IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part7:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworkSIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)2ReferenceREN/SPAN-05157-7KeywordsATS,basic,DSS1,ISDN,layer3,network,PIXITETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88Internetsecretariat@etsi.frIndividualcopiesofthisETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frImportantnoticeThisETSIdeliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74AbstractTestMethod(ATM).84.1DescriptionofATMused.84.2ConventionsfortestcomponentsandPCOs.84.3Conventionsforpoint-to-multipointconfigurations.95Untestabletestpurposes.106ATSconventions.116.1Declarationspart.116.1.1Typedefinitions.116.1.1.1Simpletypedefinitions.116.1.1.2Structuredtypedefinitions.116.1.1.2.1TTCNstructuredtypedefinitions.116.1.1.2.2ASN.1structuredtypedefinitions.116.1.1.3ASPtypedefinitions.116.1.1.3.1TTCNASPtypedefinitions.116.1.1.3.2ASN.1ASPtypedefinitions.126.1.1.4PDUtypedefinitions.126.1.1.4.1TTCNPDUtypedefinitions.126.1.1.4.2ASN.1PDUtypedefinitions.126.1.2Testsuiteconstants.126.1.3Testsuiteparameters.126.1.4Variables.126.1.4.1Testsuitevariables.126.1.4.2Testcasevariables.136.1.5Testsuiteoperationdefinitions.136.2Constraintspart.136.2.1Structuredtypeconstraintdeclaration.136.2.2ASN.1typeconstraintdeclaration.136.2.3ASPtypeconstraintdeclaration.146.2.3.1ASN.1ASPtypeconstraintdeclaration.146.2.3.2TTCNASPtypeconstraintdeclaration.146.2.4PDUtypeconstraintdeclaration.146.2.4.1ASN.1PDUtypeconstraintdeclaration.146.2.4.2TTCNPDUtypeconstraintdeclaration.146.2.5Derivedconstraints.146.2.6Parameterizedconstraints.146.2.7Valueassignment.146.2.7.1Specificvalues.146.2.7.2Matchingvalues.156.3Dynamicpart.156.3.1Testcases.156.3.2Teststeps.156.3.3Defaults.15SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)47ATStoTPmap.158PCTRconformance.159PIXITconformance.1610ATSconformance.16AnnexA(normative):ProtocolConformanceTestReport(PCTR)proforma.17A.1Identificationsummary.17A.1.1Protocolconformancetestreport.17A.1.2IUTidentification.17A.1.3Testingenvironment.17A.1.4Limitsandreservations.18A.1.5Comments.18A.2IUTconformancestatus.18A.3Staticconformancesummary.18A.4Dynamicconformancesummary.18A.5Staticconformancereviewreport.19A.6Testcampaignreport.20A.7Observations.36AnnexB(normative):PartialPIXITproforma.37B.1Identificationsummary.37B.2Abstracttestsuitesummary.37B.3Testlaboratory.37B.4Client(ofthetestlaboratory).38B.5SystemUnderTest(SUT).38B.6Protocolinformation.39B.6.1Protocolidentification.39B.6.2Configurationtobetested.40B.6.3Configurationoptions.40B.6.4Testmanagementtimers.41B.6.5SendingofmessagesbyIUT.41B.6.6Parametervalues.42AnnexC(normative):AbstractTestSuite(ATS).44C.1TheTTCNGraphicalform(TTCN.GR).44C.2TheTTCNMachineProcessableform(TTCN.MP).44AnnexD(informative):GeneralstructureofATS.45History.46SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart7ofamulti-partENcoveringtheIntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol,asidentifiedbelow:Part1:"Protocolspecification[ITU-TRecommendationQ.931(1993),modified]";Part2:"SpecificationandDescriptionLanguage(SDL)diagram";Part3:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part4:"TestSuiteStructureandTestPurposes(TSS&TP)specificationfortheuser";Part5:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationfortheuser";Part6:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork";Part7:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetwork".NationaltranspositiondatesDateofadoptionofthisEN:28January2000DateoflatestannouncementofthisEN(doa):30April2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2000DateofwithdrawalofanyconflictingNationalStandard(dow):31October2000SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)61ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworksideoftheTreferencepointorcoincidentSandTreferencepoint(asdefinedinITU-TRecommendationI.411[10])ofimplementationsconformingtothestandardsforthesignallingnetworklayerforcircuit-modebasiccallcontroloftheDigitalSubscriberSignallingSystemNo.one(DSS1)protocolforthepan-EuropeanIntegratedServicesDigitalNetwork(ISDN),EN300403-1[1]andETS300403-2[2].EN300403-6[4]specifiestheTestSuiteStructureandTestPurposes(TSS&TP)relatedtothisATSandpartialPIXITproformaspecification.OtherpartsspecifytheTSS&TPandtheATSandpartialPIXITproformafortheUsersideoftheTreferencepointorcoincidentSandTreferencepointofimplementationsconformingtoEN300403-1[1]andETS300403-2[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]ETS300403-2(1995):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part2:SpecificationandDescriptionLanguage(SDL)diagrams".[3]ETS300403-3(1996):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part3:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[4]EN300403-6(V1.2):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Signallingnetworklayerforcircuit-modebasiccallcontrol;Part6:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetwork".[5]ISO/IEC9646-1(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-2(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuitespecification".[7]ISO/IEC9646-3(1998):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[8]ISO/IEC9646-4(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part4:Testrealization".[9]ISO/IEC9646-5(1994):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[10]ITU-TRecommendationI.411(1993):"ISDNuser-networkinterfaces-Referenceconfigurations".SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)73Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):seeISO/IEC9646-1[5].ImplementationUnderTest(IUT):seeISO/IEC9646-1[5].LowerTester(LT):seeISO/IEC9646-1[5].PointofControlandObservation(PCO):seeISO/IEC9646-1[5].ProtocolImplementationConformanceStatement(PICS):seeISO/IEC9646-1[5].PICSproforma:seeISO/IEC9646-1[5].ProtocolImplementationeXtraInformationforTesting(PIXIT):seeISO/IEC9646-1[5].PIXITproforma:seeISO/IEC9646-1[5].SystemUnderTest(SUT):seeISO/IEC9646-1[5].UpperTester(UT):seeISO/IEC9646-1[5].3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBABasicAccessCESConnectionEndpointSuffixCMCo-ordinationMessageExTSExecutableTestSuiteIUTImplementationUnderTestLTLowerTesterMOTMeansOfTestingMTCMainTestComponentPCOPointofControlandObservationPCTRProtocolConformanceTestReportPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingPRAPrimaryRateAccessPTCParallelTestComponentSUTSystemUnderTestTPTestPurposeTTCNTreeandTabularCombinedNotationUTUpperTesterSIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)84AbstractTestMethod(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.2ConventionsfortestcomponentsandPCOsMasterpartSlavepartMTCAPTC2CPA2PTC1CPA1L0PCOL1PCOL2PCOIUTNETWORKFigure1:Multi-partytestmethodSIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)9Inamaster/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,2Layer3Layer2Layer1L0IUTL1,2Layer3Layer2Layer1ServiceproviderFigure2:Combinationoftheremoteandmulti-partytestmethodsTheMTCPCOisnamed"L0"("L"forLower).TheL0PCOisusedtocontrolandobservethebehaviouroftheIUTandtestcaseverdictsareassigneddependingonthebehaviourobservedatthisPCO.ThePTCsPTC1,PTC2etc.usePCOsL1,L2etc.ThesePCOsareusedtocontroland,inalimitedway,observethebehaviourofthenetworkequipmentatinterfacesotherthantheoneundertest.NoverdictsareassignedatthesePCOs.Asstatedinapreviousparagraph,thenon-receiptofnetworkgeneratedmessagesatL0,whicharestimulatedbyeventsattheL1,L2etc.,willresultinINCONCLUSIVEratherthanFAILverdictsbeingassigned.PTC2isonlyactivatedinasmallsetoftestcasesthattestthehandlingoftwocallsatonetime.IntestcaseswhichverifythattheIUTrejectsinvalidorunacceptableSETUPmessages,noPTCisactivatedatall,astheserejectionproceduresareconsideredlocaltotheaccessbetweenIUTandMTC.ThecapabilityoftheIUTtosendINFORMATIONandPROGRESSmessagesistestedindifferentcallstates.Implicitsendeventshavetobeusedinthissmallsetoftestcases,asthesendingofthosemessagescannotbetriggeredviaaPTC.SeparatePIXITquestionsareaskedforeachcallstate,ifandhowitispossibleforthetestoperatortocausethesendingofthemessages.4.3Conventionsforpoint-to-multipointconfigurationsForthisgroup,PTC3isconnectedtothesamebasicaccessastheMTC.ThusmessagesthataresenttotheMTCviathebroadcastdatalinkwillbereceivedatPTC3viaPCOL3aswell.BoththeMTCandPTC3willsendmessagesonthesameaccessusingthesamecallreferencevalue.AdistinctionbetweenthetwomessageflowsrelatedtothePCOsL0andL3canstillbemade,astheyusedifferentdatalinkentities.Thisapproach,representingaslightmodificationinthetestmethod,isillustratedinfigure3.ThisshowsthatthepartofthenetworkconsideredtobetheIUTisconnectedtoboththeMTCandPTC3.PTC2isnotusedinthatconfiguration.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)10MasterpartSlavepartMTCAPTC1CPA1CPA3PTC3L0PCOL3PCOCES1CES2L1PCOIUTBasicaccesspoint-to-multipointNETWORKFigure3:Multi-partytestmethod-modifiedforpoint-to-multipointconfigurations5UntestabletestpurposesInsometestpurposes,anESTABLISH-INDICATIONistobereceivedbytheIUT.Thislayer2primitivewillonlybetransmittedbythelayer2oftheIUTonreceiptofaSABMEframeandonlyifV(S)<>V(A).Thisconditioncannotbereachedconsideringthetestmethodused.Sothistestpurposesarenottestable:L3N_N00_I_013,L3N_N02_I_010,L3N_N03_I_009,L3N_N04_I_009,L3N_N06_008,L3N_N07_I_018,L3N_N09_I_017,L3N_N10I_I_009,L3N_N10O_I_010,L3N_N12I_I_007,L3N_N12O_I_008,L3N_N19I_I_006,L3N_N19O_I_007,L3N_U25_I_016,L3N_U25_I_016,L3N_SEG_I_004.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)116ATSconventionsThisclauseisstructuredsimilarlytothestructureofaTTCNATS.However,thenamesofthesubclausesarearrangedinawaymoresuitabletothepresentdocument.6.1Declarationspart6.1.1Typedefinitions6.1.1.1SimpletypedefinitionsWhereappropriate,simpletypeshavealength,avaluelistorarangerestrictionattached.Simpletypesdefinedasbeingofsomestringtype(e.g.BITSTRING,OCTETSTRING),havealengthrestrictionoravaluelistattached.Simpletypes,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.1structuredtypedefinitionsTherearenoASN.1structuredtypedefinitionsintheATS.6.1.1.3ASPtypedefinitions6.1.1.3.1TTCNASPtypedefinitionsTTCNASPtypedefinitionsonlycontainonePDUornoPDUatall.AllTTCNASPtypedefinitionsareprovidedwithafullidentifier.SomeASPsarenotparameterizedasshownintheexampleintable1.SuchASPsareonlyusedforrequestingorreceivingservicefromthelowerlayer.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)12Table1:TTCNASPtypedefinitionDL_REL_INTTCNASPTypeDefinitionASPNAME:DL_REL_IN(DL_RELEASE_INDICATION)PCOType:SAPComments:ParameterName|ParameterType|CommentsDetailedComments:Table2showsanexampleofaparameterizedASP.AllASPscontainingPDUscontainonlythatPDUandnootherparameters.Table2:TTCNASPtypedefinitionDL_DATA_RQTTCNASPTypeDefinitionASPNAME:DL_DATA_RQ(DL_DATA_REQUEST)PCOType:SAPComments:ParameterName|ParameterType|Commentsmun(MessageUnit)|PDU|DetailedComments:6.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.2TestsuiteconstantsEachtestsuiteconstantisdefinedintermsofapredefinedtypeorareferencedtype.Thevaluesgiveninthevaluecolumnwillremainunchangedthroughoutthetestsuite.6.1.3TestsuiteparametersEachtestsuiteparameterisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestsuiteparametertable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.6.1.4Variables6.1.4.1TestsuitevariablesNotestsuitevariablesareusedordefinedinthisATS.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)136.1.4.2TestcasevariablesEachtestcasevariableisdefinedintermsofapredefinedtypeorareferencedtype.Areferencedtypeisusedwhenitisnecessarytoattachrestrictionstothesetypedefinitions(itisnotallowedtoincluderestrictionsdirectlyinthetestcasevariabletable).Thereferencedtypecanhavealengthorvaluerestrictionattachedtoitinitsdeclarationtable.Wheretestcasevariablesareusedinconstraints,theyarepassedasformalparameters.6.1.5TestsuiteoperationdefinitionsThedescriptionpartofatestsuiteoperationdefinitionuseseithernaturallanguageormetaC.Table3:TestsuiteoperationdefinitionASSIGN_CHITestSuiteOperationDefinitionOperationName:ASSIGN_CHI(basic,primary:CHI;basic_flag:BOOLEAN)ResultType:CHIComments:ThisoperationisusedtoassignacorrectChannelidentificationinformationelementtoPDUsdependentonthetypeofaccessthatistested.DescriptionCHIASSIGN_CHI(basic,primary,basic_flag)Ifthevalueofthebasic_flagissettoTRUE,theresultoftheoperationASSIGN_CHIwillbethevaluerepresentedbytheparameterbasicwhichisoftypeCHI.Elsetheoperationresultsinthevaluerepresentedbytheparameterprimary.Examples:ASSIGN_CHI(CHI1b_R1,CHI1p_R1,TRUE)=CHI1b_R1ASSIGN_CHI(CHI1b_R1,CHI1p_R1,FALSE)=CHI1p_R1Detailedcomments:Thetestsuiteoperationdefinitionshownintable3isusedintheconstraintspartwhenassigninganelementoftypeCHIavalue.TheCHItypecanbedefinedintwowaysdependingonwhethertheATSistestingbasicorprimaryrateaccess.ToavoidduplicatetypesandtherebyduplicatetestcasesthisoperationisusedtoassignavaluetoanelementofCHItype.Ittakesthreeparameters:ThisoperationreturnsthecorrectconstraintaccordingtotheBooleanflagbasic_flag.ThatconstraintwillthenbeassignedtothespecificelementoftypeCHI.6.2Constraintspart6.2.1StructuredtypeconstraintdeclarationForeverystructuredtypedefinitionthereexistsoneormorestructuredtypeconstraint.6.2.2ASN.1typeconstraintdeclarationTherearenoASN.1typeconstraintdeclarationsintheATS.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)146.2.3ASPtypeconstraintdeclaration6.2.3.1ASN.1ASPtypeconstraintdeclarationTherearenoASN.1ASPtypeconstraintdeclarationsintheATS.6.2.3.2TTCNASPtypeconstraintdeclarationThePDUstobesentorreceivedarepassedtotheTTCNASPconstraintdeclarationsMsandMrasparametersofmetatypePDU.OnlyifvaluesinsideaspecificPDUhavetobereferenced,theuseofthemetatypePDUisnotallowedaccordingtoISO/IEC9646-3[7].InsuchcasesdifferentTTCNASPconstraintdeclarationsareused,thataredefinedtocarryonlyaspecifictypeofPDU(e.g.SETUP).Table4showsanexampleofsuchaTTCNASPconstraintdeclaration.Table4:TTCNASPconstraintdeclarationSrTTCNASPConstraintDeclarationConstraintName:Sr(PARAM:SETUP_PDU)ASPType:DL_DAT_IN_SETUPDerivationPath:Comments:ASPtoindicatethereceiptofSETUPmessages.ParameterName|ParameterValue|Commentsmun|PARAM|DetailedComments:AllASPconstraintshaveaspecificvalueforitsparameter.NomatchingsymbolsareusedinASPs.6.2.4PDUtypeconstraintdeclaration6.2.4.1ASN.1PDUtypeconstraintdeclarationTherearenoASN.1PDUtypeconstraintdeclarationsintheATS.6.2.4.2TTCNPDUtypeconstraintdeclarationPDUconstraintsareusedforassigningvaluesorpatternstothedatabeingsentorreceived.6.2.5DerivedconstraintsDerivedconstraintsareusedinthisATSonlyforSETUPandERRORPDUs.6.2.6ParameterizedconstraintsParameterizedconstraintsareusedinthisATS.6.2.7Valueassignment6.2.7.1SpecificvaluesForspecificvalueassignmentbothexplicitvaluesandreferencestoexplicitvaluesareused.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)156.2.7.2MatchingvaluesAsmatchingvaluesthefollowingmechanismsareused:InsteadofValue:AnyOrOmit"*"AnyValue"?"Omit"-"Insidevalue:AnyOne"?"AnyOrNone"*"6.3Dynamicpart6.3.1TestcasesEachtestcasecontainsthetestpurposetextfromEN300403-6[4].Tobeabletoreadandunderstandthetestcasedynamicbehaviouritisrecommendedthattheteststepsareunderstoodfirst.6.3.2TeststepsMuchusehasbeenmadeofteststepstoavoidneedlessrepetitionofdynamicbehaviour.6.3.3DefaultsNotetheuseoftheRETURNstatementwhichisdefinedinDAM1ofISO/IEC9646-3[7].Thisallowsvalidbackgroundbehaviourtobehandledinthedefaulttreewithapossibilitytoreturntotheoriginalsetofalternativesinthetestcase.7ATStoTPmapTheidentifiersusedfortheTPsarereusedastestcasenames.Thusthereisastraightforwardone-to-onemapping.8PCTRconformanceAtestlaboratory,whenrequestedbyaclienttoproduceaPCTR,isrequired,asspecifiedinISO/IEC9646-5[9],toproduceaPCTRconformantwiththePCTRtemplategiveninannexBofISO/IEC9646-5[9].Furthermore,atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,whenrequestedbyaclienttoproduceaPCTR,isrequiredtoproduceaPCTRconformantwiththePCTRproformacontainedinannexAofthepresentdocument.APCTRwhichconformstothisPCTRproformaspecificationshallpreservethecontentandorderingoftheclausescontainedinannexA.ClauseA.6ofthePCTRmaycontainadditionalcolumns.Ifincluded,theseshallbeplacedtotherightoftheexistingcolumns.Textinitalicsmayberetainedbythetestlaboratory.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)169PIXITconformanceAtestrealizer,producinganExecutableTestSuite(ExTS)fortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-4[8],toproduceanaugmentedpartialPIXITproformaconformantwiththispartialPIXITproformaspecification.AnaugmentedpartialPIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.TheaugmentedpartialPIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparetheMeansOfTesting(MOT)foraparticularIUT.Atestlaboratory,offeringtestingfortheATSspecificationcontainedinannexC,isrequired,asspecifiedinISO/IEC9646-5[9],tofurtheraugmenttheaugmentedpartialPIXITproformatoproduceaPIXITproformaconformantwiththispartialPIXITproformaspecification.APIXITproformawhichconformstothispartialPIXITproformaspecificationshall,asaminimum,havecontentswhicharetechnicallyequivalenttoannexB.ThePIXITproformamaycontainadditionalquestionsthatneedtobeansweredinordertopreparethetestlaboratoryforaparticularIUT.10ATSconformanceThetestrealizer,producingMOTandExTSforthisATSspecification,shallcomplywiththerequirementsofISO/IEC9646-4[8].Inparticular,theseconcerntherealizationofanExTSbasedoneachATS.ThetestrealizershallprovideastatementofconformanceoftheMOTtothisATSspecification.AnExTSwhichconformstothisATSspecificationshallcontaintestgroupsandtestcaseswhicharetechnicallyequivalenttothosecontainedintheATSinannexC.Allsequencesoftesteventscomprisinganabstracttestcaseshallbecapableofbeingrealizedintheexecutabletestcase.AnyfurthercheckingwhichthetestsystemmightbecapableofperformingisoutsidethescopeofthisATSspecificationandshallnotcontributetotheverdictassignmentforeachtestcase.TestlaboratoriesrunningconformancetestservicesusingthisATSshallcomplywithISO/IEC9646-5[9].AtestlaboratorywhichclaimstoconformtothisATSspecificationshalluseanMOTwhichconformstothisATS.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)17AnnexA(normative):ProtocolConformanceTestReport(PCTR)proformaNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePCTRproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPCTR.A.1IdentificationsummaryA.1.1ProtocolconformancetestreportPCTRnumber:PCTRdate:CorrespondingSCTRnumber:CorrespondingSCTRdate:Testlaboratoryidentification:Testlaboratorymanager:Signature:A.1.2IUTidentificationName:Version:Protocolspecification:EN300403-1PICS:PreviousPCTRs(ifany):A.1.3TestingenvironmentPIXITreferencenumber:ATSspecification:ETS300403-7Abstracttestmethod:Multi-partytestmethod(seeISO/IEC9646-2)Meansoftestingidentification:Datesoftesting:Conformancelogreference(s):Retentiondateforlogreference(s):SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)18A.1.4LimitsandreservationsAdditionalinformationrelevanttothetechnicalcontentsorfurtheruseofthetestreport,ortotherightsandobligationsofthetestlaboratoryandtheclient,maybegivenhere.Suchinformationmayincluderestrictiononthepublicationofthereport.A.1.5CommentsAdditionalcommentsmaybegivenbyeithertheclientorthetestlaboratoryonanyofthecontentsofthePCTR,forexample,tonotedisagreementbetweenthetwoparties.A.2IUTconformancestatusThisIUThas/hasnotbeenshownbyconformanceassessmenttobenon-conformingtothespecifiedprotocolspecification.Striketheappropriatewordsinthissentence.IfthePICSforthisIUTisconsistentwiththestaticconformancerequirements(asspecifiedinclauseA.3ofthisreport)andthereareno"FAIL"verdictstoberecorded(inclauseA.6)striketheword"has",otherwisestrikethewords"hasnot".A.3StaticconformancesummaryThePICSforthisIUTis/isnotconsistentwiththestaticconformancerequirementsinthespecifiedprotocol.Striketheappropriatewordsinthissentence.A.4DynamicconformancesummaryThetestcampaigndid/didnotrevealerrorsintheIUT.Striketheappropriatewordsinthissentence.Ifthereareno"FAIL"verdictstoberecorded(inclauseA.6ofthisreport)striketheword"did",otherwisestrikethewords"didnot".Summaryoftheresultsofgroupsoftests:.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)19A.5StaticconformancereviewreportIfclauseA.3indicatesnon-conformance,thisclauseitemizesthemismatchesbetweenthePICSandthestaticconformancerequirementsofthespecifiedprotocolspecification.SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)20A.6TestcampaignreportCallstateN00ATSreferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsL3N_N00_V_001L3N_N00_V_002L3N_N00_V_003L3N_N00_V_004L3N_N00_V_005L3N_N00_V_006L3N_N00_V_007L3N_N00_V_008L3N_N00_V_009L3N_N00_V_010L3N_N00_V_011L3N_N00_V_012L3N_N00_V_013L3N_N00_V_014L3N_N00_V_015L3N_N00_V_016L3N_N00_V_017L3N_N00_V_018L3N_N00_V_019L3N_N00_V_020L3N_N00_V_021L3N_N00_V_022L3N_N00_V_023L3N_N00_V_024L3N_N00_V_025L3N_N00_V_026L3N_N00_V_027L3N_N00_V_028L3N_N00_V_029L3N_N00_V_030L3N_N00_V_031L3N_N00_V_032L3N_N00_V_033L3N_N00_V_034L3N_N00_V_035L3N_N00_V_036L3N_N00_V_037L3N_N00_V_038L3N_N00_V_039L3N_N00_V_040L3N_N00_V_041L3N_N00_V_042L3N_N00_V_043L3N_N00_V_044L3N_N00_V_045L3N_N00_V_046L3N_N00_V_047L3N_N00_V_048L3N_N00_V_049L3N_N00_V_050L3N_N00_V_051L3N_N00_V_052L3N_N00_V_053L3N_N00_V_054L3N_N00_V_055L3N_N00_V_056L3N_N00_V_057L3N_N00_I_001L3N_N00_I_002SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)21CallstateN00ATSreferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsL3N_N00_I_003L3N_N00_I_004L3N_N00_I_005L3N_N00_I_006L3N_N00_I_007L3N_N00_I_008L3N_N00_I_009L3N_N00_I_010L3N_N00_I_011L3N_N00_I_012L3N_N00_S_001L3N_N00_S_002L3N_N00_S_003L3N_N00_S_004L3N_N00_S_005L3N_N00_S_006L3N_N00_S_007L3N_N00_S_008L3N_N00_S_009L3N_N00_S_010L3N_N00_S_011L3N_N00_S_012CallstateN02ATSreferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsL3N_N02_V_001L3N_N02_V_002L3N_N02_V_003L3N_N02_V_004L3N_N02_V_005L3N_N02_V_006L3N_N02_V_007L3N_N02_V_008L3N_N02_V_009L3N_N02_V_010L3N_N02_V_011L3N_N02_V_012L3N_N02_V_013L3N_N02_I_001L3N_N02_I_002L3N_N02_I_003L3N_N02_I_004L3N_N02_I_005L3N_N02_I_006L3N_N02_I_007L3N_N02_I_008L3N_N02_I_009L3N_N02_I_011L3N_N02_S_001L3N_N02_S_002L3N_N02_S_003L3N_N02_S_004L3N_N02_S_005L3N_N02_S_006L3N_N02_S_007L3N_N02_S_008L3N_N02_S_009L3N_N02_S_010SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)22CallstateN03ATSreferenceSelected?(Y/N)Run?(Y/N)VerdictObservationsL3N_N03_V_001L3N_N03_V_002L3N_N03_V_003L3N_N03_V_004L3N_N03_V_005L3N_N03_V_006L3N_N03_V_007L3N_N03_V_008L3N_N03_V_009L3N_N03_V_010L3N_N03_V_011L3N_N03_I_001L3N_N03_I_002L3N_N03_I_003L3N_N03_I_004L3N_N03_I_005L3N_N03_I_006L3N_N03_I_007L3N_N03_I_008L3N_N03_I_010L3N_N03_S_001L3N_N03_S_002L3N_N03_S_003L3N_N03_S_004L3N_N03_S_005L3N_N03_S_006L3N_N03_S_007L3N_N03_S_008L3N_N03_S_009L3N_N03_S_010SIST EN 300 403-7 V2.1.2:2005
ETSIETSIEN300403-7V2.1.2(2000-02)23CallstateN04ATSreferenceSelected?(Y/N
...