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
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005

Buy Documents

Standard

SIST EN 300 347-6 V3.1.1:2005

English language (27 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 347-6 V3.1.1:2005 is the Slovenian adoption of ETSI EN 300 347-6 V3.1.1, published for V interfaces at the digital Local Exchange (LE) and the V5.2 interface that supports an Access Network (AN). It specifies the Abstract Test Suite (ATS), the Abstract Test Method (ATM), and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network layer (NWK) on the LE side. In practice, it is the document a test lab, manufacturer, or conformance team uses to check LE-side V5.2 network-layer behavior against the ETSI test model.

What does SIST EN 300 347-6 V3.1.1:2005 specify?

SIST EN 300 347-6 V3.1.1:2005 specifies conformance test material for the V5.2 network layer and related parts of system management on the LE side of the interface. The document is built on the ISO/IEC 9646 conformance testing framework, and the ATS is written in Tree and Tabular Combined Notation (TTCN).

The document is organized around six clauses plus two normative annexes:

AnnexWhat it covers
Annex AThe normative Abstract Test Suite for NWK testing, in TTCN.GR and TTCN.MP forms
Annex BThe normative partial PIXIT proforma, including addresses, parameters, timers, procedures, and PICS-related information

Clause 4 describes the abstract test method and the point of control and observation used for testing. Clause 5 lists test purposes that the ATS does not cover. Clause 6 defines the naming and implementation conventions used in the ATS.

What are the key requirements of SIST EN 300 347-6 V3.1.1:2005?

Clause 4 sets out a remote test method for LE-side V5.2 NWK testing, with an embedded variant where needed for service and national functions. That matters because the IUT is tested from a remote V5.2 test system, and some control actions are only represented informally in the ATS.

Clause 4.2 explains that the test system uses a Lower Tester 1 (LT1) and several points of control and observation on the DSAP, PSAP, PSTN_ACCESS, and PCM_ACCESS interfaces. In practice, test events are expressed as data link layer Abstract Service Primitives (ASPs), network layer Protocol Data Units (PDUs), or physical layer ASPs, depending on the point being observed.

Clause 4.3 assigns V5DLaddr values to the protocol entities. Each network-layer protocol functional entity has one data link connection, so the tester must configure the correct address for PSTN, Control, BCC, Protection, and Link control behavior.

Clause 4.4 defines how test cases are executed. The start-up test case must be run first, and it must also be run first after any restart of the IUT. The clause also notes that invalid and inopportune test cases can generate error indications during system management, so those indications must be handled without disturbing the test result.

Clause 5 identifies untestable test purposes for the Control protocol, PSTN protocol, Link control protocol, BCC Protocol, and Protection protocol. The stated reasons include unknown IUT reactions, overlap with already implemented test cases, optional procedures that may not be present, a fixed FSM state requirement, and the inability to provoke certain management messages. This tells the reader which Test Purposes are not expected to appear in the ATS.

Clause 6 gives the ATS conventions. It defines naming rules for declarations, constraints, test cases, test steps, verdict labels, and ATS abbreviations, and it describes how TTCN tables are structured. This matters for implementation, maintenance, and traceability of test results.

What terms does SIST EN 300 347-6 V3.1.1:2005 define?

  • Abstract Test Suite (ATS) - the formal set of conformance test cases defined for the NWK part of the V5.2 interface.
  • Abstract Test Method (ATM) - the test approach used to apply the ATS, here based on remote testing with an embedded variant where needed.
  • partial Protocol Implementation eXtra Information for Testing (PIXIT) - the implementation-specific information that fills in test parameters such as addresses, timers, and optional message content.
  • Implementation Under Test (IUT) - the protocol implementation being tested.
  • System Under Test (SUT) - the broader system that contains the IUT and related testable parts.
  • Point of Control and Observation (PCO) - the interface point where the test system sends stimuli and observes reactions.
  • Tree and Tabular Combined Notation (TTCN) - the notation used to define the ATS in Annex A.

Who uses SIST EN 300 347-6 V3.1.1:2005?

SIST EN 300 347-6 V3.1.1:2005 is used by conformance test laboratories, telecom equipment manufacturers, and acceptance or quality teams working on V5.2 interfaces. It is also relevant to engineers preparing PICS and PIXIT data, because Annex B shows what implementation-specific information the test system needs. Buyers or integrators can use it to understand what kind of formal interoperability testing is available for the LE-side network layer.

Which standards are used with SIST EN 300 347-6 V3.1.1:2005?

  • EN 300 347-1 - supplies the V5.2 interface specification and protocol/message details used by the tests.
  • EN 300 347-2 - provides the PICS proforma referenced for protocol identification and implementation data.
  • EN 300 347-5 - provides the Test Suite Structure and Test Purposes for the LE-side network layer.
  • EN 300 324-1 - is referenced for V5.1 interface details, addresses, timers, and related behavior used in the proforma and test data.
  • EN 300 324-2 - provides earlier PICS references used by some PIXIT items.
  • EN 300 324-5 and ETS 300 324-6 - are earlier V5.1 counterparts for the network-layer TSS&TP and ATS/PIXIT structure.
  • ISO/IEC 9646-1, -2, -3, and -5 - provide the conformance testing framework, ATS specification rules, TTCN notation, and laboratory/client requirements.
  • ETS 300 406 and ETR 141 - provide ETSI testing methodology and TTCN style guidance.

What does the SIST EN 300 347-6 V3.1.1:2005 document contain?

The document contains the ATS in Annex A, including both TTCN.GR and TTCN.MP representations. Annex B contains the partial PIXIT proforma with identification data, test-laboratory details, SUT information, protocol-layer data, addresses, timers, procedural information, implicit send events, and PICS-related items.

It also contains a remote-test-method figure, a V5DL address table, lists of untestable test purposes, and detailed naming and implementation conventions for TTCN tables. Those parts are what a lab uses to configure the test environment, parameterize message content, and interpret verdicts during conformance testing.

Buy Documents

Standard

SIST EN 300 347-6 V3.1.1:2005

English language (27 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 347-6 V3.1.1:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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)". This standard covers: Update the test specifications to be in line with the 3rd edition of the base protocol standard.

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

SIST EN 300 347-6 V3.1.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.30 - Switching and signalling systems. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 347-6 V3.1.1: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.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.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©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
...