SIST EN 300 347-4 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-4 V3.1.1 (2001-03) - V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)

Overview

SIST EN 300 347-4 V3.1.1:2005 defines the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer of the V5.2 interface, on the Access Network (AN) side. Published by the Slovenski inštitut za standardizacijo (SIST), this standard aligns test specifications with the third edition of the base protocol and supports the conformance and interoperability testing of equipment using the V5.2 interface in digital local exchanges (LE).

The document is relevant for telecommunication professionals, equipment manufacturers, and test laboratories ensuring interoperability between Access Networks (AN) and Local Exchanges (LE) using V5.2 interfaces. It sets out standardized testing and reporting methods to verify protocol implementation and compliance with European telecommunications standards.

Key Topics

• Abstract Test Suite (ATS): Specifies conformance test cases for the V5.2 network layer (AN side) to increase interoperability probability between diverse manufacturers’ equipment.
• Testing Methodology: Based on ISO/IEC 9646 series for Open Systems Interconnection (OSI) conformance testing, using the Tree and Tabular Combined Notation (TTCN).
• Protocol Implementation eXtra Information for Testing (PIXIT): Provides a proforma for implementers to declare extra information relevant to protocol testing-addressing system specifics required during conformance evaluations.
• Test Execution and Reporting: Outlines conventions for naming, structuring, and documenting test cases, constraints, and test steps.
• Scope of Applicability: Covers the network layer and parts of system management for the Access Network side of a V5.2 interface.
• Untestable Test Purposes: Lists scenarios excluded from the ATS due to methodological or practical test limitations.
• Update Conformance: Brings testing requirements into line with the 3rd edition of the base V5.2 protocol standard for consistency across Europe.

Applications

This standard is vital for:

• Telecommunications Equipment Manufacturers: Ensuring their Access Network components and Local Exchanges are V5.2-conformant and interoperable with other vendors’ products.
• Testing Laboratories: Implementing standardized methodologies and using the provided ATS for rigorous, repeatable conformance tests.
• Network Operators: Verifying that network components from diverse suppliers function correctly in a multi-vendor environment.
• Certification Bodies: Facilitating formal certification processes for access and switching equipment using harmonized test protocols.

The test suite helps reduce market fragmentation, minimizes integration issues, and accelerates the deployment of reliable telecommunications networks. The PIXIT proforma ensures that specific implementation details-like address types and protocol options-are transparently declared and factored into evaluation procedures.

Related Standards

For comprehensive coverage and compatibility, consider referencing these related standards:

• EN 300 347-1: V5.2 interface specification (base protocol)
• EN 300 347-2: Protocol Implementation Conformance Statement (PICS) proforma
• EN 300 347-3: Test Suite Structure and Test Purposes (TSS&TP) for network layer (AN side)
• EN 300 347-5/6: Test structures and ATS for the LE side
• EN 300 347-7/8: Test suites for data link and physical layers of V5.2
• ISO/IEC 9646: Conformance testing methodology for OSI systems

By implementing SIST EN 300 347-4 V3.1.1:2005 together with these harmonized standards, organizations can ensure complete and recognized interoperability testing coverage for V interfaces in digital local exchanges.

---

Keywords: V5.2 interface, network layer, conformance testing, ATS, PIXIT, Access Network, Local Exchange, interoperability, telecommunications standard, TTCN, protocol implementation.

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) – 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežno plast na strani dostopovnega omrežja (AN)V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:EN 300 347-4 Version 3.1.1SIST EN 300 347-4 V3.1.1:2005en01-januar-2005SIST EN 300 347-4 V3.1.1:2005SLOVENSKI
STANDARD
ETSIEN300347-4V3.1.1(2001-03)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(ANside)SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)2ReferenceREN/SPAN-09102-4KeywordsAN,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-4 V3.1.1:2005

ETSIETSIEN300347-4V3.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.115.3Linkcontrolprotocol.115.4BCCProtocol.125.5Protectionprotocol.126Abstracttestsuiteconventions.126.1Namingconventions.126.1.1Declarationpart.126.1.2Constraintpart.136.1.3Dynamicpart.146.1.3.1Testcases.146.1.3.2Teststeps.146.1.3.3Generalaspects.146.1.4ATSabbreviations.146.2Implementationconventions.156.2.1Declarationpart.156.2.2Constraintpart.156.2.3Dynamicpart.166.2.4Documentation.17AnnexA(normative):AbstracttestsuiteforNWKtesting.18A.1TheTTCNGraphicalform(TTCN.GR).18A.2TheTTCNMachineProcessableform(TTCN.MP).18AnnexB(normative):PartialPIXITproforma.19B.1Introduction.19B.2PIXITproforma.19B.2.1Identificationsummary.19B.2.2Abstracttestsuitesummary.19B.2.3Testlaboratory.19B.2.4Client.20B.2.5SUT.20B.2.6Protocollayerinformation.21B.2.6.1Protocolidentification.21B.2.6.2IUTinformation.21SIST EN 300 347-4 V3.1.1:2005

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

ETSIETSIEN300347-4V3.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).Thepresentdocumentispart4ofamulti-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-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)61ScopeThepresentdocumentcontainstheAbstractTestSuite(ATS)aswellastheAbstractTestMethod(ATM)andthepartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortheNetworklayer(NWK)oftheV5.2interfaceandpartsofthesystemmanagementoftheAccessNetwork(AN)sideofaV5.2interface.TheobjectiveofthepresentdocumentistoprovideanATScontainingconformancetestswhichgiveahighprobabilityofinter-operabilityofanANandaLocalExchange(LE)fromdifferentmanufacturersovertheV5.2interface.ISO/IEC9646-1[7]andISO/IEC9646-2[8]areusedasthebasisforthetestmethodology.TheATSisdefinedusingtheTreeandTabularCombinedNotation(TTCN)accordingtoISO/IEC9646-3[9].TheATSinannexAdescribesasetofTestCases(TCs)whicharebasedontheTestPurposes(TPs)specifiedinEN300347-3[6](whichisanextensionofETS300324-3[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-3(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(ANside)".[3]ETSIETS300324-4(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationforthenetworklayer(ANside)".[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]ETSIEN300347-3:"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(ANside)".[7]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[8]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.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]ETSIEN300377-1:"Q3interfaceattheLocalExchange(LE)forconfigurationmanagementofV5interfacesandassociatedcustomerprofiles;Part1:Q3interfacespecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninETS300324-4[3]apply.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ANAccessNetworkASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteBCCBearerChannelConnectionBIInvalidBehaviourBOInopportuneBehaviourBVValidBehaviourCACApabilitytestCTRLControlDLLDataLinkLayerDSAPDatalinkSAPFEFunctionElementIEInformationElementIEIInformationElementIdentifierISDNIntegratedServicesDigitalNetworkISDN-BAISDN-BasicAccessITbasicInterconnectionTestIUTImplementationUnderTestL3addrLayer3addressLCLineCircuitLT1LowerTester1MPHManagementPhysicallayerNWKNetworkLayerPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingREQRequestSAPServiceAccessPointSUTSystemUnderTestTPTestPurposesTSSTestSuiteStructureSIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)8TTCNTreeandTabularCombinedNotationULUpperLayerUTUpperTesterV5DLaddrV5DataLinkaddress4AbstracttestmethodThisclausedescribestheAbstractTestMethod(ATM)andthePointofControlandObservation(PCO)usedtotesttheNWKoftheV5.2protocolfortheANcomponents.4.1ATMPrincipally,theremotetestmethodisusedforV5.2ANNWKconformancetesting.CertainV5.2ANNWKTPsneedalsopartoftheserviceandnationalfunctions.Therefore,theembeddedvariantoftheremotetestmethodisapplied.ThenationaldependantinformationisdefinedinthePIXIT.4.2NWKlayerprotocoltestingTheV5.2implementationsdonotofferadirectaccesstotheupperserviceboundary.Theremotetestmethodwaschosenbecauseanyco-ordinationprocedurescanonlybeexpressedinaninformalway.SUTV5NWKPDUsServiceProviderDLL&PHLlayersLT1Control,BCC,LINK,ProtectionandPSTNDLconnectionendpointsV5TestSystemIUTV5-NWKDL-DATAPCO/DSAPUTFigure1:RemotesinglelayertestmethodappliedtotheV5.2NWKlayertestingLT1:ALowerTester(LT1)islocatedinaremoteV5.2testsystem.ItcontrolsandobservesthebehavioursoftheIUT.DSAP:AuniqueDatalinkServiceAccessPoint(DSAP)isdefinedattheV5.2interfaceandcommonlyusedforexchangingservicedataofthedifferentnetworklayerprotocolfunctionalentities.PCO:ThePCOsforNWKtestingarelocatedontheDSAP,PSAP,PSTN_ACCESSandPCM_ACCESSinterfaces.AlltesteventsattheDSAParespecifiedintermsofDataLinkLayer(DLL)AbstractServicePrimitives(ASPs)andnetworklayerPDUs.AlltesteventsatthePSAParespecifiedintermsofphysicallayerASPs.AlltesteventsatPSTN_ACCESSandPCM_ACCESSaredefinedasASPs.SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)9UT:NoexplicitUpperTester(UT)existsinthetestsystem.However,theSUTneedstocarryoutsomeULfunctionstoachievesomeeffectsoftestco-ordinationprocedures.DesigningATS,thecapabilityofthesystemmanagementfunctions,suchascontrolsoftheIUT,itsinteractionswiththeQinterfacemaybetakenintoaccount.ThecontrolsoftheIUTwillbeimpliedorinformallyexpressedintheATS,butnoassumptionshallbemaderegardingtheirfeasibilityorrealization.ExamplesofsuchcontrolscouldbetoprovokerestartingIUTorblocking/unblockingproceduresthroughQinterface.V5-NWK:TotestthePSTNandISDNprotocols,asimulatorshallbeattachedtorelevantUserPort(UP).4.3DatalinkAddressesWithintheDSAP,differentV5DLaddrareusedtoidentifyeachcorrespondingdatalinkconnection.Eachnetworklayerprotocolfunctionalentitycanhaveonlyonedatalinkconnection,e.g.allPSTNsignallinginformationsharesonedatalinkconnection.Table1showstheallocatedV5DLaddrusedbyprotocolfunctionentities.Table1:V5DLaddrProtocolPSTNControlBCCProtectionLinkControlV5DLaddr817681778178817981804.4ExecutionofTCs4.4.1HandlingoferrorindicationDuringtheexecutionoftheNWKATSmanyerrorindicationswillbesenttothesystemmanagementduetotheinvalidandtheinopportuneTCs.ItisuptotheIUTsuppliertotakethenecessaryprecautionstoavoidanyimpactonthetestresult.4.4.2TCexecutionsequenceThefollowingtestsequenceshallbeapplied:TheTCcontainingthestart-upprocedureshallalwaysbethefirstTCexecuted.AlsoinanycasewheretheIUThastoberestartedthisTCshallbefirstexecuted.-Protocolgroups:CTRLLINKPROTECTIONPSTNBCC.-Testgroups:ITCATIBVBOBI.Interactionsbetweenthedifferenttestgroupsarenotconsidered.ItisuptotheIUTsuppliertotakethenecessaryprecautionstoavoidanyimpactonthetestresult.NOTE:ThisappliesinparticulartoPORTCONTROLmessagesfromISDNportswhiletestingPSTN-relatedprotocolsandviceversa.SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)105UntestabletestpurposesThisclausegivesalistofTPswhicharenotimplementedintheATSduetothechosenabstracttestmethodorotherrestrictions.5.1ControlprotocolTable2listsTPswhicharenotcoveredbytheATSduetounknownreactionoftheIUTaftertestingtheTPsorduetothefacttheyhavethesamepurposeofTCalreadyimplemented.Table2:UntestableTPsTestPurposeTP1311S1_01TP1313S0_01TP1321S2_01TP1324S1001TP1324S1002TP1324SM_06TP1324SM_07TP1325SM_03TP1325S2207TP1325S2208TP1325S2209TP1326SM_07TP1326S2008TP1326S2009TP1326S2010TP1326S2011TP1326S2012TP1424S1101TP1425SM_01TP1426SM_01TP1426SM_02TP1426SM_03TP1521S1-01SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)115.2PSTNprotocolThefollowingtestpurposesarenotimplementedintheATSduetounknownreactionoftheIUTaftertestingtheTPsorduetothefacttheyhavethesamepurposeofTCalreadyimplemented.Table2aTestPurposeTP23__S0_04TP23__S0_06TP23__S0_07TP23__S1_08TP23__S1_09TP23__S2_11TP23__S3_10TP23__S3_11TP23__S4_06TP23__S4_09TP23__S4_10TP23__S6_05TP23__S7_11TP24__S2_03TP24__S2_04TP24__S3_04TP24__S3_05TP24__S4_05TP24__S5_04TP24__S5_05TP24__S5_06TP24__S7_02TP26__S5_015.3LinkcontrolprotocolThefollowingtestpurposesarenotimplementedintheATSduetounknownreactionoftheIUTaftertestingtheTPsorduetothefacttheyhavethesamepurposeofTCalreadyimplemented.Table3:UntestableTPsTestPurposeTP31__SM_01TP32__SM_01TP33_1S1_01TP33_1SM_03TP33_7S1002TP33_7S1103TP33_7S1112TP33_7S1113TP33_7S2001TP33_7S2105TP33_7S2125TP33_7S2126TP33_7S2204TP33_7S2222TP33_7SM_11TP33_7SM_29SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)125.4BCCProtocolTable4listsTPswhicharenotcoveredbytheATS.Table4:UntestableTPsTestPurposeTP41__SM_01TP43__SM_21TP44__S1_02TP44__S1_03TP44__S1_04TP46__S1_01TP46__S1_025.5ProtectionprotocolThefollowingtestpurposesarenotimplementedintheATS.Table5:UntestableTPsTestPurposeTP51__SM_01TP53__SM_05TP53__SM_06TP53__SM_18TP53__SM_20TP56__S0_02TP56__S1_046AbstracttestsuiteconventionsTheATSconventionsareintendedtogiveabetterunderstandingoftheATSbuttheydescribealsotheconventionsmadeforthedevelopmentoftheATS,thusforanylatermaintenancepurposesorfurtherdevelopmentoftheATStheconventionsdescribedinthisclauseshallbeconsidered.TheATSconventionscontaintwoclauses,thenamingconventionsandtheimplementationconventions.ThenamingconventionsdescribethestructureofthenamingofallATSelements.TheimplementationconventionsdescribethefunctionalstructureoftheATS.NOTE:TodefinetheATS,theguidelinesgiveninETS300406[11]andETR141[12]wereconsidered.6.1Namingconventions6.1.1DeclarationpartTheIDnamesofthefollowingdefinitionsarewritteninlowercase:-structuredtypedefinitions;-ASPtypedefinitions;-PDUtypedefinitions.SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)13TheIDnamesofthefollowingdefinitionsarewritteninuppercase:-TestSuiteParameterDeclarations;-TestCaseSelectionExpressionDefinitions;-TestSuiteConstantDeclarations;-TestCaseVariableDeclarations.IDnamesofPDUsandstructuredtypescommencewithaprotocolidentifiertodefinewhichprotocoltheyarebelongingto.Thefollowingidentifiersareused:-controlprotocol:ctrle.g.crtl_common_control_ack;-PSTNsignalling:pstne.g.pstn_signal_ack.IDnamesofPDUsandstructuredtypeswhichareusedforinvalidtestscommencewith"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).Ifthetestsuiteparameterisrepresentingasystemparameterorvalue,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.SIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)146.1.3Dynamicpart6.1.3.1TestcasesTheidentifieroftheTCsisconstructedinthesamewayasfortheTPsdescribedinEN300347-3[6],clause5.1.1,withtheexceptionthat"TP"isreplacedby"TC".-TPidentifier:TP1324S1106;-TCidentifier:TC1324S1106.6.1.3.2TeststepsInTCs,teststepsaswellaslocaltreesareused.Toallowaneasydistinction,thefollowingnamingisapplied:-localtree:LTS_[local_tree_name];-teststep:STEP_[test-step_name].6.1.3.3GeneralaspectsAllverdictassignmentsarelabelled.Toallowanexactidentificationinwhichtabletheverdictwasassigned,thefollowingnameconventionisapplied:BtestBodyCSCheckStateteststepsDDefaultEErrorhandlingteststepsPOPOstamblePRPReambleStestStepCombinationsoflabelsarealsopossible.EXAMPLE:DPR→labelwhichisusedinadefaultforpreambles.6.1.4ATSabbreviationsTheseabbreviationsareusedtoshortenidentifiernames:addraddressactactivateaccaccessackacknowledgementallocallocationcaucausecccommoncontrolcfecontrolfunctionelementcficontrolfunctionidentifierchanchannelcomcommoncplcompletectrlcontroldldatalinkenqenquiryestestablishfuncfunctionindindicationinterfinterfacemandmandatorymetymessagetypemodmodifiedSIST EN 300 347-4 V3.1.1:2005

ETSIETSIEN300347-4V3.1.1(2001-03)15parparameterpcportcontrolpdprotocoldiscriminatorperformperformanceprogprogressprprotectionprotocolprotprotocolprovprovisionedreprore-provisioningreqrequestrestrestartrspresponseupuserportvarvariantverifyverifyingvidvariant&interfaceID6.2Implementationconventions6.2.1DeclarationpartThecommentlineofsingleelementTTCNtables(e.g.testsuiteconstants)isusedtogiveareferencewheretheformatandcontentoftheelementisdescribedintherelevantprotocolspecifications.Anyparticularityoftheelementformatorcontentisdescribedinthecommentline.Thecommentlineintheheaderofmulti-elementTTCNtables(e.g.ASPs)isusedtoreferencetotheprotocolspecification.Thedetailedcommentsareusedtodescribeanyparticularityofthetable.IntheASPandPDUdeclarations,thecommentscolumnisusedtoidentifyifanelementismandatoryoroptional.m:mandatory;o:optional.IntheASPandPDUdeclarationsthecommentscolumnisfurtherusedtogiveinformationabouttheelementvalue,inparticulariftheelementcontainsafixedsparevalue.Intableswherestructuretypesareusedtheinformationelementandtherelevantstructuredtypehavealwaysthesamename,thatallowstohavethesamestructureasintheprotocolstandardsisusedtodocumenttherelationbetweeninformationelementsinatableandtheirspecificdescriptioninanotherclauseoftheprotocolstandard.6.2.2ConstraintpartTheASPsandPDUsaredefinedinawaythatallrelevantelementareparameterized.Thatimprovesthetransparencyoftheconstraintsinthedynamicpart,asallvalueswhicharerelevantforthetestarealwayspresent.Generallythebaseconstraintcontainsallpossibleparametersandtherelevantformalparameterlistwhichgoeswiththebaseconstraint.IncasewhereaspecificmessageIEisnotusedatallintheATS,thebaseconstraintwillnotcontainsuchanIE.ThebaseconstraintsofthePSTNprotocolcontainallmandatoryIEs.TheoptionalIEsaredefinedinoneelementoftypeOCTETSTRING.TheactualvalueandformatoftheoptionalIEhastobedefinedinthePIXITsaccordingtothePSTNspecificationswhichisim
...