SIST EN 300 347-6 V3.1.1:2005

• Abstract:

  Update the test specifications to be in line with the 3rd edition of the base protocol standard.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.30 - Switching and signalling systems
• 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
• Ref Project: ETSI EN 300 347-6 V3.1.1 (2001-03) - V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (LE side)

Overview

SIST EN 300 347-6 V3.1.1:2005 is a Slovenian national standard identical to EN 300 347-6, published by the European Telecommunications Standards Institute (ETSI). This standard defines the specifications and guidelines for the V interfaces at digital Local Exchange (LE) using the V5.2 interface, specifically focusing on the support of Access Networks (AN) and the creation of testing environments for the network layer on the LE side. Part 6 of this series centers on the Abstract Test Suite (ATS) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for comprehensive network layer conformance testing. The document updates the test specifications to align with the third edition of the base protocol standard, ensuring improved interoperability and compliance.

Key Topics

• V5.2 Interface for LE and AN: Establishes a standard interface allowing different access technologies to connect to the local exchange, boosting flexibility in network deployments.
• Abstract Test Suite (ATS): Provides a structured set of test cases designed to check conformance and interoperability of the network layer implementations according to the V5.2 protocol specifications.
• Partial PIXIT Proforma: Details extra protocol implementation information required for effective testing, covering specific system parameters and variations.
• Network Layer Testing Methodologies: Describes the testing approach based on the Tree and Tabular Combined Notation (TTCN) and follows the principles of ISO/IEC 9646 for open systems conformance testing.
• Test Naming and Structure Conventions: Specifies consistent conventions for test case naming, constraints, dynamic parts, and protocol data units to facilitate test suite maintenance and evolution.
• Address and Parameter Management: Outlines the management of network addresses and key parameters essential for targeted and effective protocol testing.

Applications

SIST EN 300 347-6 V3.1.1:2005 serves as a critical framework for:

• Conformance Testing: Used by vendors and testing laboratories to validate that local exchange network layer implementations comply with the V5.2 protocol standard.
• Equipment Interoperability: Ensures that equipment from various manufacturers can reliably interact via standardized V5.2 interfaces, reducing integration issues in public switched telephone networks (PSTN) and Integrated Services Digital Networks (ISDN).
• Protocol Implementation Verification: Supports network operators, developers, and system integrators in verifying that their protocol implementations meet required specifications before deployment.
• Network Modernization Projects: Aids telecom service providers in upgrading or integrating access network technologies without compromising interoperability or compliance.
• Test Tool Development: Provides a blueprint for designing automated test tools using ATS and PIXIT forms, supporting robust and repeatable network layer protocol testing.

Related Standards

• EN 300 347-1: V5.2 interface specification, the foundational protocol document for the interface.
• EN 300 347-2: Protocol Implementation Conformance Statement (PICS) proforma for V5.2.
• EN 300 347-5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer, LE side.
• EN 300 324 Series: Covers V5.1 interface standards for similar network applications.
• ISO/IEC 9646 Series: International standards for conformance testing methodology in open systems interconnection environments.
• ETSI ETS 300 406: Defines methodologies for protocol and profile conformance testing.

Key terms: V5.2 interface, Local Exchange (LE), Access Network (AN), network layer, Abstract Test Suite (ATS), protocol testing, PIXIT, conformance, interoperability, protocol implementation, ETSI, SIST.

By adhering to SIST EN 300 347-6 V3.1.1:2005, the telecommunications industry can ensure reliable, testable, and standards-compliant communication infrastructures that support a range of access technologies and network evolution requirements.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.2 za podporo dostopovnemu omrežju (AN) – 6. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežno plast na strani krajevne centrale (LE)V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (LE side)33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:EN 300 347-6 Version 3.1.1SIST EN 300 347-6 V3.1.1:2005en01-januar-2005SIST EN 300 347-6 V3.1.1:2005SLOVENSKI
STANDARD
ETSIEN300347-6V3.1.1(2001-03)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(LEside)SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)2ReferenceREN/SPAN-09102-6KeywordsAN,ATS,LE,PIXIT,testing,Vinterface,V5interfaceETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.74Abstracttestmethod.84.1ATM.84.2NWKlayerprotocoltesting.84.3Datalinkaddresses.94.4ExecutionofTCs.94.4.1Handlingoferrorindication.94.4.2TCexecutionsequence.95Untestabletestpurposes.105.1Controlprotocol.105.2PSTNprotocol.105.3Linkcontrolprotocol.115.4BCCProtocol.115.5Protectionprotocol.126Abstracttestsuiteconventions.126.1Namingconventions.126.1.1Declarationpart.126.1.2Constraintpart.136.1.3Dynamicpart.136.1.3.1Testcases.136.1.3.2Teststeps.146.1.3.3Generalaspects.146.1.4ATSabbreviations.146.2Implementationconventions.156.2.1Declarationpart.156.2.2Constraintpart.156.2.3Dynamicpart.156.2.4Documentation.16AnnexA(normative):AbstracttestsuiteforNWKtesting.17A.1TheTTCNGraphicalform(TTCN.GR).17A.2TheTTCNMachineProcessableform(TTCN.MP).17AnnexB(normative):PartialPIXITproforma.18B.1Introduction.18B.2PIXITproforma.18B.2.1Identificationsummary.18B.2.2Abstracttestsuitesummary.18B.2.3Testlaboratory.18B.2.4Client.19B.2.5SUT.19B.2.6Protocollayerinformation.20B.2.6.1Protocolidentification.20B.2.6.2IUTinformation.20SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)4History.27SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart6ofamulti-partdeliverablecoveringtheVinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN),asdescribedbelow:Part1:"V5.2interfacespecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(ANside)";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(ANside)";Part5:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(LEside)";Part6:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(LEside)";Part7:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforthedatalinklayer";Part8:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthedatalinklayer";Part9:"Testspecificationforthephysicallayer".NationaltranspositiondatesDateofadoptionofthisEN:23March2001DateoflatestannouncementofthisEN(doa):30June2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31December2001DateofwithdrawalofanyconflictingNationalStandard(dow):31December2001SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)61ScopeThepresentdocumentcontainstheAbstractTestSuite(ATS)aswellastheAbstractTestMethod(ATM)andthepartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworklayer(NWK)oftheV5.2interfaceandpartsofthesystemmanagementoftheLocalExchange(LE)sideofaV5.2interface.TheobjectiveofthepresentdocumentistoprovideanATScontainingconformancetestswhichgiveahighprobabilityofinter-operabilityofanAccessNetwork(AN)andaLEfromdifferentmanufacturersovertheV5.2interface.ISO/IEC9646-1[7]andISO/IEC9646-2[8]areusedasthebasisforthetestmethodology.TheATSisdefinedusingtheTreeandTabularCombinedNotation(TTCN)accordingtoISO/IEC9646-3[9].TheATSinannexAdescribesasetofTestCases(TCs)whicharebasedontheTestPurposes(TPs)specifiedinETS300347-5[6](whichisanextensionofETS300324-5[2]).TheTCsprovidetheimplementationoftheTPsandcanbeconvertedintoanexecutabletestsuitebyusingavailableTTCNtranslatorsandthecorrespondingtools.AnnexBprovidesthepartialPIXITproforma.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300324-1(V1.2.3):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part1:V5.1interfacespecification".[2]ETSIETS300324-5(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(LEside)".[3]ETSIETS300324-6(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part6:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(LEside)".[4]ETSIEN300347-1(V2.2.2):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part1:V5.2interfacespecification".[5]ETSIEN300347-2(V2.1.3):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[6]ETSIETS300347-5(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(LEside)".[7]ISO/IEC9646-1:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[8]ISO/IEC9646-2:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)7[9]ISO/IEC9646-3:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[10]ISO/IEC9646-5:"InformationTechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".[11]ETSIETS300406:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".[12]ETSIETR141:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;TheTreeandTabularCombinedNotation(TTCN)styleguide".[13]ETSIEN300324-2(V1.2.3):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,alltermsanddefinitionsgiveninETS300324-6[3]apply.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ANAccessNetworkASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBCCBearerChannelConnectionBIInvalidBehaviourBOInopportuneBehaviourBVValidBehaviourCACApabilitytestCTRLControlDSAPDatalinkSAPFEFunctionElementFSMFiniteStateMachineIEInformationElementISDNIntegratedServicesDigitalNetworkISDN-BAISDN-BasicAccessITbasicInterconnectionTestIUTImplementationUnderTestL3addrLayer3addressLCLineCircuitLT1LowerTester1MPHManagementPhysicallayerNWKNetworkLayerPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingREQRequestSAPServiceAccessPointSUTSystemUnderTestTPTestPurposesTSSTestSuiteStructureSIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)8TTCNTreeandTabularCombinedNotationULUpperLayerUTUpperTesterV5DLaddrV5DataLinkaddress4AbstracttestmethodThisclausedescribestheAbstractTestMethod(ATM)andthePointofControlandObservation(PCO)usedtotesttheNWKoftheV5.2protocolfortheLEcomponents.4.1ATMPrincipally,theremotetestmethodisusedforV5.2LENWKconformancetesting.CertainV5.2LENWKTPsneedalsopartoftheserviceandnationalfunctions.Therefore,theembeddedvariantoftheremotetestmethodisapplied.ThenationaldependentinformationisdefinedinthePIXIT.4.2NWKlayerprotocoltestingTheV5.2implementationsdonotofferadirectaccesstotheupperserviceboundary.Theremotetestmethodwaschosenbecauseanyco-ordinationprocedurescanonlybeexpressedinaninformalway.SUTV5NWKPDUsServiceProviderDLL&PHLlayersLT1PCO/DSAPDLconnectionendpointsV5TestSystemIUTV5NWKDL-DATAUTBCC,Control,Linkcontrol,PSTNandProtectionprotocolFigure1:RemotetestmethodappliedtotheV5.2NWKlayertestingLT1:ALowerTester(LT1)islocatedinaremoteV5.2testsystem.ItcontrolsandobservesthebehavioursoftheIUT.DSAP:AuniqueDatalinkServiceAccessPoint(DSAP)isdefinedattheV5.2interfaceandcommonlyusedforexchangingservicedataofthedifferentnetworklayerprotocolfunctionalentities:PSTN,Controlprotocols.PCO:ThePCOsforNWKtestingarelocatedontheDSAP,PSAP,PSTN_ACCESSandPCM_ACCESSinterfaces.AlltesteventsattheDSAParespecifiedintermsofdatalinklayerAbstractServicePrimitives(ASPs)andnetworklayerPDUs.AlltesteventsatthePSAParespecifiedintermsofphysicallayerASPs.AlltesteventsatPSTN_ACCESSandPCM_ACCESSaredefinedasASPs.SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)9UT:NoexplicitUpperTester(UT)existsinthetestsystem.However,theSUTneedstocarryoutsomeULfunctionstoachievesomeeffectsoftestco-ordinationprocedures.DesigningATS,thecapabilityofthesystemmanagementfunctions,suchascontrolsoftheIUT,itsinteractionswiththeQinterfacemaybetakenintoaccount.ThecontrolsoftheIUTwillbeimpliedorinformallyexpressedintheATS,butnoassumptionshallbemaderegardingtheirfeasibilityorrealization.ExamplesofsuchcontrolscouldbetoprovokerestartingIUTorblocking/unblockingproceduresthroughQinterface.4.3DatalinkaddressesWithintheDSAP,differentV5DLaddrareusedtoidentifyeachcorrespondingdatalinkconnection.Eachnetworklayerprotocolfunctionalentitycanhaveonlyonedatalinkconnection,e.g.allPSTNsignallinginformationshareonedatalinkconnection.Table1showstheallocatedV5DLaddrusedbytheprotocolfunctionentities.Table1:V5DLaddrProtocolPSTNControlBCCProtectionLinkControlV5DLaddr817681778178817981804.4ExecutionofTCs4.4.1HandlingoferrorindicationDuringtheexecutionoftheNWKATSmanyerrorindicationswillbesenttothesystemmanagementduetotheinvalidandtheinopportuneTCs.ItisuptotheIUTsuppliertotakethenecessaryprecautionstoavoidanyimpactonthetestresult.4.4.2TCexecutionsequenceThefollowingtestsequenceshallbeapplied:TheTCcontainingthestart-upprocedureshallalwaysbethefirstTCexecuted.AlsoinanycasewheretheIUThastoberestartedthisTCshallbefirstexecuted.Protocolgroups:CTRLLINKPROTECTIONBCCPSTN.Testgroups:ITCATIBVBOBI.Interactionsbetweenthedifferenttestgroupsarenotconsidered.ItisuptotheIUTsuppliertotakethenecessaryprecautionstoavoidanyimpactonthetestresult.SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)105UntestabletestpurposesThisclausecontainsalistofTPswhicharenotcoveredbyintheATSduetothechosenATMorotherrestrictions.5.1ControlprotocolTable2listsTPswhicharenotcoveredbytheATSduetounknownreactionoftheIUTaftertestingtheTPsorduetothefacttheyhavethesamepurposeofTCalreadyimplemented.Table2:UntestableTPsTestPurposeIDTP1311S1_01TP1313S0_01TP1313SM_06TP1313SM_07TP1313SM_08TP1313SM_09TP1321S1_01TP1324S1001TP1324SM_05TP1324SM_11TP1325S1001TP1325S2013TP1325SM_11TP1325SM_24TP1326S1001TP1326SM_06TP1326SM_115.2PSTNprotocolThetestpurposeslistedintable3arenotimplementedintheATSduetounknownreactionoftheIUTaftertestingtheTPsorduetothefacttheyhavethesamepurposeofTCalreadyimplemented.Table3:UntestableTPsTestPurposeIDTP23__S1_04TP23__S1_06TP23__S2_08TP23__S2_09TP23__S4_07TP23__S5_10TP23__S6_01TP26__S4_01SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)115.3LinkcontrolprotocolTable4listsTPswhicharenotcoveredbytheATSduetoexistingoptionalprocedureswhichmayormaynotbeappliedbytheIUT.Table4:UntestableTPsTestPurposeIDTP31__SM_01TP33_1S1_01TP33_1SM_03TP33_7S1002TP33_7S1103TP33_7S1112TP33_7S1113TP33_7S2001TP33_7S2105TP33_7S2134TP33_7S2135TP33_7S2204TP33_7S2228TP33_7S2229TP33_7S2244TP33_7SM_11TP33_7SM_18TP33_7SM_405.4BCCProtocolTable5listsTPswhicharenotcoveredbytheATSbecauseitisnotpossibletofixtheIUTre-provisioningFiniteStateMachine(FSM)instateLE1.Table5:UntestableTPsTestPurposeIDTP41__SM_01TP42__SM_02TP42__SM_03TP42__SM_04TP42__SM_05TP43__SM_23TP43__SM_24TP43__SM_25SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)125.5ProtectionprotocolTable6listsTPswhicharenotcoveredbytheATSbecauseitisnotpossibletoprovokethegenerationofthenecessaryMPHsfromsystemmanagement.Table6:UntestableTPsTestPurposeIDTP51__SM_01TP53__S1_13TP53__SM_04TP53__SM_05TP53__SM_15TP56__S0_02TP56__S1_04TP56__S1_06TP56__S1_076AbstracttestsuiteconventionsTheATSconventionsareintendedtogiveabetterunderstandingoftheATSbuttheydescribealsotheconventionsmadeforthedevelopmentoftheATS,thusforanylatermaintenancepurposesorfurtherdevelopmentoftheATStheconventionsdescribedinthisclauseshallbeconsidered.TheATSconventionscontaintwoclauses,thenamingconventionsandtheimplementationconventions.ThenamingconventionsdescribethestructureofthenamingofallATSelements.TheimplementationconventionsdescribethefunctionalstructureoftheATS.NOTE:TodefinetheATS,theguidelinesgiveninETS300406[11]andETR141[12]wereconsidered.6.1Namingconventions6.1.1DeclarationpartTheIDnamesofthefollowingdefinitionsarewritteninlowercase:-structuredtypedefinitions;-ASPtypedefinitions;-PDUtypedefinitions.TheIDnamesofthefollowingdefinitionsarewritteninuppercase:-TestSuiteParameterDeclarations;-TestCaseSelectionExpressionDefinitions;-TestSuiteConstantDeclarations;-TestCaseVariableDeclarations.IDnamesofPDUsandstructuredtypescommencewithaprotocolidentifiertodefinewhichprotocoltheyarebelongingto.Thefollowingidentifiersareused:-controlprotocol:ctrle.g.crtl_common_control_ack;-PSTNsignalling:pstne.g.pstn_signal_ack.SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)13IDnamesofPDUsandstructuredtypeswhichareusedforinvalidtestscommencewith"bi".EXAMPLE1:bi_com_ctrl_two_mety.CompletenamesasdefinedinthespecificationsareusedforIDnamesofdeclarations.EXAMPLE2:ctrl_control_function_element.TestsuiteparameterIDnamescommencewithTSP:-PICSareidentifiedbyaddingtheletter"C":TSPC_.(e.g.:TSPC_PSTN);-PIXITareidentifiedbyaddingtheletter"X":TSPX_.(e.g.:TSPX_PORT_ADDRESS).Ifatestsuiteparameterisrepresentingasystemparameterorvalue,onlytheparameternameisused.EXAMPLE3:MR(receivesequencenumberinsignalmessage).TestsuiteoperationscommencewithTSO.EXAMPLE4:TSO_INTEGER_TO_OCTETSTRING.TestsuiteconstantIDnamescommencewithTSC.EXAMPLE5:TSC_CFE_FE201_2_UNBL.Iftheconstantisrepresentingasystemparameterorvalue,onlytheparameternameisused.EXAMPLE6:N01.IDnamesofTimerscommencewithT.Thesamenamesasinthespecificationareused.EXAMPLE7:T01.6.1.2ConstraintpartConstraintnamescommencewithuppercase.TheremainingpartoftheIDnameiswritteninlowercase.IDnamesofelementsconcerningthesamesubjecthaveequivalentnamesinthedeclarationandtheconstraintpart:Declarationpart:ctrl_control_function_element;Constraintpart:Ctrl_control_function_element.Thenameofthemodifiedconstraintdescribestheparticularityofthemodifiedconstraint.EXAMPLE:Ctrl_cc_mand_only(commoncontrolmessagewhichcontainsonlythemandatoryIEs).Ifformalparameterlistsareused,thevariablenamesarewritteninlowercase.Thevariablenameisthesameasthenameoftheelementitisrepresenting.6.1.3Dynamicpart6.1.3.1TestcasesTheidentifieroftheTCsisconstructedinthesamewayasfortheTPsdescribedinETS300347-5[6],clause5.1.1,withtheexceptionthat"TP"isreplacedby"TC".TPidentifier:TP1324S1106;TCidentifier:TC1324S1106.SIST EN 300 347-6 V3.1.1:2005

ETSIETSIEN300347-6V3.1.1(2001-03)146.1.3.2TeststepsInTCs,teststepsaswellaslocaltreesareused.Toallowaneasydistinction,thefollowingnamingisapplied:localtree:LTS_[local_tree_name];teststep:STEP_[test-step_name].6.1.3.3GeneralaspectsAllverdictassignmentsarelabelled.Toallowanexactidentificationinwhichtabletheverdictwasassigned,thefollowingnameconventionisapplied:BtestBodyCSstatusverificationteststeps(CheckStatus)DDefaultEErrorhandlingteststepsPOPOstamblePRPReambleStestStepCombinationsoflabelsarealsopossible.EXAMPLE:DPR-->labelwhichisusedinadefaultforpreambles.6.1.4ATSabbreviationsTheseabbreviationsareusedtoshortenidentifiernames:addraddressactactivateaccaccessackacknowledgementallocallocationcaucausecccommoncontrolcfecontrolfunctionelementcficontrolfunctionidentifierchanchannelcomcommoncplcompletectrlcontroldl
...