SIST EN 300 347-5 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-5 V3.1.1 (2001-03) - V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LE side)

SIST EN 300 347-5 V3.1.1:2005 is the ETSI test specification for the V5.2 interface at the digital Local Exchange (LE), focused on the network layer on the LE side. It defines the Test Suite Structure and Test Purposes (TSS&TP) used to check conformance between an Access Network (AN) and an LE, with the aim of supporting interoperability between equipment from different manufacturers.

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

SIST EN 300 347-5 V3.1.1:2005 specifies the TSS&TP for the NWK layer and parts of system management for the LE side of a V5.2 interface. It is organized as a test-suite structure in Clause 4 and test purposes in Clause 5, with supporting definitions, abbreviations, references and a bibliography.

The document is part of a multi-part V5.2 deliverable. The foreword lists companion parts for the interface specification, PICS proformas, ATS/PIXIT proformas, data-link layer testing, and physical layer testing.

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

Clause 4 says the test suite is built around protocol groups and main test groups. In practice, that means a tester can target control, PSTN, link control, BCC and protection behavior separately, while still checking how they interact.

• Clause 4.2.1 covers the protocol groups. The Control protocol, PSTN protocol, Link control protocol, BCC protocol and Protection protocol each have dedicated coverage. This matters because a fault in one protocol can affect another, especially link control, BCC and protection.
• Clause 4.2.2 defines the main test groups: IT, CA, BV, BO, BI and TI. These groups separate basic connection checks, capability checks, normal behavior, out-of-sequence behavior, invalid messages, and timer or counter handling.
• Clause 4.3 defines reusable test steps, including state transitions, preambles, postambles, status verification and common test steps. This helps test authors build repeatable test cases and helps implementers see how a conformance test drives the interface.
• Clause 4.3.1.1 uses PICS items N11, N12, M2, N9 and R5.4 to select the startup path and the supported port and link configuration. In practice, the implementation’s declared feature set determines which startup and alignment procedures are exercised.
• Clause 4.3.1.7 and 4.3.1.9 show that link blocking and protection switching are tied together. For a reader, this means link control tests can trigger protection behavior, so link provisioning and protection group setup must match the declared configuration.
• Clause 4.4 and Clause 4.6 define defaults, ATS timers and counters. The ATS uses timer tolerances and repetition limits, so the test system must respect the specified timing windows rather than only message content.
• Clause 5 structures the Test Purposes by protocol and category. It includes coverage for common control, port control, PSTN, link control, BCC and protection behavior, with explicit preconditions, messages and expected responses.
• Clauses 5.4 and 5.5 show that link control and BCC are tested with real operational sequences such as blocking, unblocking, identification, allocation, de-allocation, audit and fault handling. That means these are not abstract checks only - they are interaction tests across the V5.2 interface.

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

• Access Network (AN) - the network side that connects to the LE over the V5.2 interface.
• Local Exchange (LE) - the digital exchange side that is under test in this document.
• Test Suite Structure and Test Purposes (TSS&TP) - the organization of the test suite and the intended purpose of each test.
• Abstract Test Suite (ATS) - the abstract test framework used to express the tests and their timing.
• Protocol Implementation Conformance Statement (PICS) - the declared feature set used to choose which tests and configurations apply.
• Bearer Channel Connection (BCC) - the protocol area that allocates, de-allocates and audits bearer channels.
• Public Switched Telephone Network (PSTN) - the telephony side whose call control behavior is included in the test coverage.

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

SIST EN 300 347-5 V3.1.1:2005 is used by conformance test engineers, laboratory staff, vendors, system integrators, quality managers and buyers who need to verify V5.2 LE implementations. It is especially relevant when checking interoperability between AN and LE equipment, when building ATS test cases, and when validating declared PICS configurations.

What changed in SIST EN 300 347-5 V3.1.1:2005 from the previous edition?

SIST EN 300 347-5 V3.1.1:2005 updates the test specifications to be in line with the 3rd edition of the base protocol standard.

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

• ETSI EN 300 347-1 - the base V5.2 interface specification that defines the protocol behavior and many referenced tables and clauses.
• ETSI EN 300 347-2 - the PICS proforma used to declare which features and configurations are implemented.
• ISO/IEC 9646-1 - the general conformance testing methodology and framework used as part of the test basis.
• ISO/IEC 9646-2 - the abstract test suite specification methodology used for the ATS structure.
• ETSI EN 300 324-5 - the V5.1 part 5 test specification used for several clauses and test groups that are identical or directly referenced.
• ETSI ETS 300 347-7 - the data-link layer TSS&TP specification, referenced for link-related behavior outside this part.

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

The document contains the test suite structure, test-step structure, protocol data units, information elements, timer and counter declarations, and a long list of test purposes for Control protocol, Link control protocol, BCC and Protection protocol. It also includes figures for the NWK LE test-suite structure and the startup flow, plus tables that map protocol entities and define timer and counter values.

For implementation and test execution, the most useful parts are the preambles and postambles, the state-transition steps, and the protocol-specific expected messages. For engineering work, the document gives the exact points where an LE is expected to allocate channels, block or unblock ports and links, respond to fault conditions, or trigger protection switching.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vmesniki V pri digitalnih krajevnih telefonskih centralah (LE) – Vmesnik V5.2 za podporo dostopovnemu omrežju (AN) – 5. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – 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 5: Test Suite Structure and Test Purposes (TSS&TP) 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-5 Version 3.1.1SIST EN 300 347-5 V3.1.1:2005en01-januar-2005SIST EN 300 347-5 V3.1.1:2005SLOVENSKI
STANDARD
ETSIEN300347-5V3.1.1(2001-03)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(LEside)SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)2ReferenceREN/SPAN-09102-5KeywordsAN,LE,testing,TSS&TP,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-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.84TestSuiteStructure(TSS).94.1Overview.94.2Testgroups.104.2.1Protocolgroups.114.2.1.1Controlprotocol.114.2.1.2PublicSwitchedTelephoneNetwork(PSTN)protocol.114.2.1.3Linkcontrolprotocol.114.2.1.4BearerChannelConnection(BCC)protocol.114.2.1.5Protectionprotocol.114.2.2Maintestgroups.124.2.2.1Basicinterconnectiontests(IT).124.2.2.2Capabilitytests(CA).124.2.2.3Validbehaviourtests(BV).124.2.2.4Inopportunebehaviourtests(BO).124.2.2.5Invalidbehaviourtests(BI).124.2.2.6Timerexpiryandcountermismatchtests(TI).124.2.2.6.1TimersandcountersoftheControlprotocol.124.2.2.6.2TimersandcountersofthePSTNprotocol.134.2.2.6.3TimersandcountersoftheLinkcontrolprotocol.134.2.2.6.4TimersandcountersoftheBCCprotocol.134.2.2.6.5TimersandcountersoftheProtectionprotocol.134.2.2.6.6TimersandcountersoftheLEsystemmanagement.134.3Teststepstructure.144.3.1Statetransitions.144.3.1.1Start-upofV5.2interface.144.3.1.2Commoncontrolprotocol(systemmanagement).164.3.1.3Controlprotocol(PSTNportFSM).164.3.1.4Controlprotocol(ISDN-BAportFSM).164.3.1.5Controlprotocol(ISDN-PRAportFSM).164.3.1.6PSTNprotocol.174.3.1.7Linkcontrolprotocol.174.3.1.8BCCprotocol.174.3.1.9Protectionprotocol.184.3.2Preambles.184.3.3Postambles.184.3.4Statusverification.194.3.4.1PSTNprotocol.194.3.4.2LinkcontrolFSM.194.3.5Commonteststeps.194.4Defaults.194.5AbstractServicePrimitives(ASPs)andProtocolDataUnits(PDUs).204.5.1ASPs.204.5.2PDUs.204.5.2.1Commoncontrolprotocol.204.5.2.2Portcontrolprotocol.204.5.2.3PSTNprotocol.204.5.2.4Linkcontrolprotocol.20SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)44.5.2.5BCCprotocol.204.5.2.6Protectionprotocol.214.5.3Informationelements.214.5.3.1Variablelengthinformationelements.214.5.3.1.1Controlprotocol.214.5.3.1.2PSTNprotocol.214.5.3.1.3Linkcontrolprotocol.214.5.3.1.4BCCprotocol.214.5.3.1.5Protectionprotocol.214.5.3.2Singleoctetinformationelements.224.5.3.2.1Controlprotocol.224.5.3.2.2PSTNprotocol.224.5.3.2.3Linkcontrolprotocol.224.5.3.2.4BCCprotocol.224.5.3.2.5Protectionprotocol.224.6TimersandcountersoftheAbstractTestSuite(ATS).225TestPurposes(TPs).235.1Introduction.235.1.1Testpurposenamingconvention.235.1.2Sourceoftestpurposedefinition.245.1.3Teststrategy.245.1.3.1Commoncontrolprotocol.245.1.3.2Portcontrolprotocol.245.1.3.3PSTNprotocol.245.1.3.4Linkcontrolprotocol.255.1.3.5BCCprotocol.255.1.3.6Protectionprotocol.255.1.4Requirementsnotcoveredbytestpurposes.265.1.5Initialstates.265.1.6Testanddataconfigurationrequirements.275.2Controlprotocol.275.2.1Basicinterconnectiontests(V5NWKLE/CTRL/IT).275.2.2Capabilitytests(V5NWKLE/CTRL/CA).275.2.3Validbehaviourtests(V5NWKLE/CTRL/BV).275.2.3.1V5NWKLE/CTRL/BV/COM.275.2.3.1.1V5NWKLE/CTRL/BV/COM/TRANS.275.2.3.1.2V5NWKLE/CTRL/BV/COM/REST.275.2.3.1.3V5NWKLE/CTRL/BV/COM/REVY.285.2.3.1.4V5NWKLE/CTRL/BV/COM/ACCALGT.285.2.3.2V5NWKLE/CTRL/BV/PORT.295.2.3.2.1V5NWKLE/CTRL/BV/PORT/TRANS.295.2.3.2.2V5NWKLE/CTRL/BV/PORT/PSTN.295.2.3.2.3V5NWKLE/CTRL/BV/PORT/ISDNBA.295.2.3.2.4V5NWKLE/CTRL/BV/PORT/ISDNPRA.305.2.4Inopportunebehaviourtests(V5NWKLE/CTRL/BO).325.2.4.1V5NWKLE/CTRL/BO/COM.325.2.4.2V5NWKLE/CTRL/BO/PORT.325.2.4.2.1V5NWKLE/CTRL/BO/PORT/TRANS.325.2.4.2.2V5NWKLE/CTRL/BO/PORT/ISDNBA.325.2.4.2.3V5NWKLE/CTRL/BO/PORT/ISDNPRA.325.2.5Invalidbehaviourtests(V5NWKLE/CTRL/BI).325.2.6Timerexpiryandcountermismatchtests(V5NWKLE/CTRL/TI).335.3PSTNprotocol.335.4Linkcontrolprotocol.335.4.1Basicinterconnectiontests(V5NWKLE/LINK/IT).335.4.2Capabilitytests(V5NWKLE/LINK/CA).335.4.3Validbehaviourtests(V5NWKLE/LINK/BV).335.4.3.1V5NWKLE/LINK/BV/TRANS.335.4.3.2V5NWKLE/LINK/BV/LINK.345.4.4Inopportunebehaviourtests(V5NWKLE/LINK/BO).455.4.4.1V5NWKLE/LINK/BO/TRANS.45SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)55.4.4.2V5NWKLE/LINK/BO/LINK.455.4.5Invalidbehaviourtests(V5NWKLE/LINK/BI).475.4.5.1V5NWKLE/LINK/BI/TRANS.475.4.6Timerexpiryandcountermismatchtests(V5NWKLE/LINK/TI).485.4.6.1V5NWKLE/LINK/TI/TRANS.485.5BCCprotocol.485.5.1Basicinterconnectiontests(V5NWKLE/BCC/IT).495.5.2Capabilitytests(V5NWKLE/BCC/CA).495.5.3Validbehaviourtests(V5NWKLE/BCC/BV).505.5.4Inopportunebehaviourtests(V5NWKLE/BCC/BO).535.5.5Invalidbehaviourtests(V5NWKLE/BCC/BI).565.5.6Timerexpiryandcountermismatchtests(V5NWKLE/BCC/TI).585.6Protectionprotocol.585.6.1Basicinterconnectiontests(V5NWKLE/PROTECT/IT).595.6.2Capabilitytests(V5NWKLE/PROTECT/CA).595.6.3Validbehaviourtests(V5NWKLE/PROTECT/BV).595.6.4Invalidbehaviourtests(V5NWKLE/PROTECT/BI).635.6.5Timerexpiryandcountermismatchtests(V5NWKLE/PROTECT/TI).64Bibliography.66History.67SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart5ofamulti-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-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)71ScopeThepresentdocumentcontainstheTestSuiteStructureandTestPurposes(TSS&TP)fortheNetWorKlayer(NWK)andpartsofthesystemmanagementoftheLocalExchange(LE)sideofaV5.2interface.Theobjectiveofthepresentdocumentistoprovideconformancetestsgivingahighprobabilityofinter-operabilityofanAccessNetwork(AN)andaLEfromdifferentmanufacturersovertheV5.2interface.ThepresentdocumentcoversonlytheproceduresdescribedinEN300347-1[2].ISO/IEC9646-1[4]andISO/IEC9646-2[5]areusedasthebasisforthetestmethodology.ThepresentdocumentneedstobereadinconjunctionwithEN300324-5[1].ThetwodocumentsshareacommonformatandclauseswithinEN300324-5[1]aredirectlyreferenced.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300324-5(V3.1.1):"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part5:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthenetworklayer(LEside)".[2]ETSIEN300347-1(V2.2.2):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part1:V5.2interfacespecification".[3]ETSIEN300347-2(V2.1.3):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[4]ISO/IEC9646-1(1995):"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[5]ISO/IEC9646-2(1995):"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[6]ETSIETS300347-7(1999):"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part7:TestSuiteStructureandTestPurposes(TSS&TP)specificationforthedatalinklayer".SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)83Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninEN300324-5[1],EN300347-1[2]andthefollowingapply.specifiedinformationelement:informationelementidentifierasdefinedinEN300347-1[2]unspecifiedinformationelement:informationelementidentifierwhichisnotdefinedinEN300347-1[2]incorrectinformationelement:specifiedinformationelementcarryinginformationelementtypeswhicharenotdefinedinEN300347-1[2]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AISAlarmIndicationSignalANAccessNetworkASPAbstractServicePrimitiveATSAbstractTestSuiteBCCBearerChannelConnectionBIInvalidBehaviourBOInopportuneBehaviourBVValidBehaviourCACapabilityCOMCommoncontrolprotocolCTRLControlFEFunctionElementFSMFiniteStateMachineIDIdentifierIEInformationElementISDNIntegratedServicesDigitalNetworkISDN-BAISDNBasicAccessISDN-PRAISDNPrimaryRateAccessITBasicInterconnectionIUTImplementationUnderTestL3addrLayer3addressLELocalExchangeLT1LowerTester1MDUManagementDataUnitMPHManagementPhysicallayerNWKNetworklayerPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPSTNPublicSwitchedTelephoneNetworkRAIRemoteAlarmIndicationREQRequestSNSequenceNumberSUTSystemUnderTestTETerminalEquipment(ISDNorPSTN)TITimerTPTestPurposeTSTimeSlotTSSTestSuiteStructureUPUserPortSIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)94TestSuiteStructure(TSS)4.1OverviewFigure1showsthestructureoftheV5.2NWKtestsuite.V5NWKLEITCABVCTRLCOMTRANS/PROTOCOLSYS_MAN/RESTSYS_MANREVYTRANS/PROTOCOLPORTPSTNISDN-BAISDN-PRACOMTRANS/PROTOCOLBITRANS/PROTOCOLPORTCOMTRANS/PROTOCOLTRANS/PROTOCOLPORTTIITCABVPSTNSTATESTATESTATESTATEBOBITIITCABVTRANS/PROTOCOLLINKLINKCTRLTRANS/PROTOCOLTITRANS/PROTOCOLBIITBVBCCCAITBVPROTECTTIBICABOCOMTRANS/PROTOCOLPORTTRANS/PROTOCOLSYS_MANREVYISDN-BAISDN-PRATRANS/PROTOCOLLINKCTRLBOBOBITIFigure1:NWKLEtestsuitestructureSIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)104.2TestgroupsFigure2givesanoverviewofthevariousprotocolentitiesofaV5.2interface.Table1mapseachprotocolentityontestedprotocolgroups.LE_PSTN_port_FSMLE_ISDN_port_FSMLE_PSTNLE_SYSLE_DLLE_CTRLLE_V5_FSMFEDL-DATAMPHPHDL-DATAFEMDUPH-DATAMDUMPHV5(ANI)MDULE_RMLE_LINKLE_PROTMDLMDUMDUDL-DATADL-DATANWK_LEDL-DATALE_LINK_CTRL_FSMFEMDUnationalPSTNprotocolISDNlayer2managementMPHLE_BCCFigure2:NWKLE-protocolentityoverviewTable1:Namesusedinfigure2thatcorrespondtoEN300347-1[2]NetworklayerprotocolentitiesProtocolentitiesdefinedinEN300347-1[2]ProtocolgroupreferencesLE_PSTN_port_FSMLE_PSTN_user_port_FSM4.2.1.1LE_ISDN_port_FSMLE_ISDN-BA_user_port_FSMLE_ISDN-PRA_user_port_FSM4.2.1.1LE_CTRLLE_control_protocol4.2.1.1LE_SYSLE_system_management4.2.1.1LE_PSTNLE_PSTN_protocol4.2.1.2LE_LINKLE_link_control_protocol4.2.1.3LE_LINK_CTRL_FSMLE_link_control_FSM4.2.1.3LE_RMLE_resource_management4.2.1.4LE_BCCLE_BCC_protocol4.2.1.4LE_PROTLE_protection_protocol4.2.1.5SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)114.2.1Protocolgroups4.2.1.1ControlprotocolThecontentsofthisclauseareidenticaltoclause4.2.1.1ofEN300324-5[1]withthefollowingadditionsfortheISDN-PRAuserportFiniteStateMachine(FSM).Dependingonprovisioningthefollowingconfigurationistested:LE_ISDN-PRA_user_port:Theblocking,blockingrequestandco-ordinatedunblockingproceduresoftheLE_ISDN-PRA_user_port_FSMareverifiedinthetestgroupsV5NWKLE/CTRL/BV/PORT/ISDNPRAandV5NWKLE/CTRL/BO/PORT/ISDNPRA.4.2.1.2PublicSwitchedTelephoneNetwork(PSTN)protocolThecontentsofthisclauseareidenticaltoclause4.2.1.2ofEN300324-5[1].4.2.1.3LinkcontrolprotocolAlltestsintheLinkcontrolprotocol(V5NWKLE/LINK)testgroupareintendedtoverifyasthoroughlyaspossiblethevariousproceduresoftheLE_link_control_protocolentity.Dependingonprovisioningthefollowingconfigurationsarecovered:LE_link_control_protocol:ThenormalandexceptionalproceduresoftheLE_link_control_protocolareverifiedinthetestgroupsV5NWKLE/LINK/BV/TRANS,V5NWKLE/LINK/BO/TRANSandV5NWKLE/LINK/TI/TRANS.TheerrorhandlingproceduresareverifiedinthetestgroupV5NWKLE/LINK/BI/TRANS.LE_link_control_FSM:Thelinkfailure,linkblocking,linkblockingrequest,co-ordinatedlinkunblockingandlinkidentificationproceduresoftheLE_link_control_FSMareverifiedinthetestgroupV5NWKLE/LINK/BV/LINKandV5NWKLE/LINK/BO/LINK.4.2.1.4BearerChannelConnection(BCC)protocolAlltestsintheBCCprotocol(V5NWKLE/BCC)testgroupareintendedtoverifyasthoroughlyaspossiblethevariousproceduresoftheLE_BCCprotocolentity.ThefollowingBCCproceduresarecovered:-normalandexceptionalbearerchannelallocationprocedure;-normalandexceptionalbearerchannelde-allocationprocedure;-auditprocedure;-ANinternalfailurenotificationprocedure;-errorhandlingprocedures.4.2.1.5ProtectionprotocolAlltestsintheProtectionprotocol(V5NWKLE/PROTECT)testgroupareintendedtoverifyasthoroughlyaspossiblethevariousproceduresoftheLEProtectionprotocolentity.ThefollowingProtectionprotocolproceduresarecovered:-transmissionofProtectionprotocolmessages;-normalandexceptionalsequencenumberresetprocedure;SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)12-normalandexceptionalstandardprotectionswitch-overprocedureinitiatedbyLEside;-normalandexceptionaldedicatedprotectionswitch-overprocedureinitiatedbyOSLE;-normalandexceptionalswitch-overprocedurerequestedbyANside;-errorhandlingprocedures.4.2.2Maintestgroups4.2.2.1Basicinterconnectiontests(IT)Thecontentsofthisclauseareidenticaltoclause4.2.2.1ofEN300324-5[1].4.2.2.2Capabilitytests(CA)Thecontentsofthisclauseareidenticaltoclause4.2.2.2ofEN300324-5[1].4.2.2.3Validbehaviourtests(BV)Thecontentsofthisclauseareidenticaltoclause4.2.2.3ofEN300324-5[1].4.2.2.4Inopportunebehaviourtests(BO)Thecontentsofthisclauseareidenticaltoclause4.2.2.4ofEN300324-5[1].4.2.2.5Invalidbehaviourtests(BI)Thecontentsofthisclauseareidenticaltoclause4.2.2.5ofEN300324-5[1].4.2.2.6Timerexpiryandcountermismatchtests(TI)Differenttimersandcountersaredefinedtosupervisethevariousstatetransitions.ThistestgroupisintendedtoverifythattheFSMisreactingproperlytoanexpireofoneofthetimersorcountermismatch.4.2.2.6.1TimersandcountersoftheControlprotocolThecontentsofthisclauseareidenticaltoclause4.2.2.6.1ofEN300324-5[1]withadditionsfortheacceleratedalignmentprocedure.ThistimersaregiveninEN300347-1[2],annexC,tableC.1.TU1AMDU-CTRL(UNBLOCKALLRELEVANTPSTNANDISDNPORTSREQUEST)sent;TU2AMDU-CTRL(UNBLOCKALLRELEVANTPSTNANDISDNPORTSCOMPLETE)sent;TU1BMDU-CTRL(UNBLOCKALLRELEVANTPSTNPORTSREQUEST)sent;TU2BMDU-CTRL(UNBLOCKALLRELEVANTPSTNPORTSCOMPLETE)sent;TU1CMDU-CTRL(UNBLOCKALLRELEVANTISDNPORTSREQUEST)sent;TU2CMDU-CTRL(UNBLOCKALLRELEVANTISDNPORTSCOMPLETE)sent;TU1DMDU-CTRL(BLOCKALLPSTNPORTSREQUEST)sent;TU2DMDU-CTRL(BLOCKALLPSTNPORTSCOMPLETE)sent;TU1EMDU-CTRL(BLOCKALLISDNPORTSREQUEST)sent;TU2EMDU-CTRL(BLOCKALLISDNPORTSCOMPLETE)sent.SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)134.2.2.6.2TimersandcountersofthePSTNprotocolThecontentsofthisclauseareidenticaltoclause4.2.2.6.2ofEN300324-5[1].4.2.2.6.3TimersandcountersoftheLinkcontrolprotocolRefertoEN300347-1[2],table23.-LCTO1LINKCONTROLmessagesent.4.2.2.6.4TimersandcountersoftheBCCprotocolRefertoEN300347-1[2],table46.-TBCC1ALLOCATIONsent;-TBCC2DE-ALLOCATIONsent;-TBCC3DE-ALLOCATIONsent;-TBCC4AUDITsent.4.2.2.6.5TimersandcountersoftheProtectionprotocolRefertoEN300347-1[2],table64.-TSO1SWITCH-OVERCOMsent;-TSO2OS-SWITCH-OVERCOMsent;-TSO4RESETSNCOMsent;-TSO5RESETSNCOMreceived.RefertoEN300347-1[2],clause18.6.2.-VP(S)SendStateVariable;-VP(R)ReceiveStateVariable.4.2.2.6.6TimersandcountersoftheLEsystemmanagement-TC4MDL-RELEASE-INDICATIONfromLINK-CONTROL-DL;-TC5ExpiryTC4;-TC6MDL-RELEASE-INDICATIONfromBCC-DL;-TC7ExpiryTC6;-TC10MDL-ESTABLISH-CONFIRMorMDL-ESTABLISH-INDICATEreceivedfromthefirstofallV5.2Datalinksinstart-up.Otherwisethecontentsofthisclauseareidenticaltoclause4.2.6.3ofEN300324-5[1].SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)144.3TeststepstructureGeneraldynamicbehavioursaredescribedinteststepswhichcanbecalledfromalltestcaseswithintheAbstractTestSuite(ATS):-statetransitions(refertoclause4.3.1);-preambles(refertoclause4.3.2);-postambles(refertoclause4.3.3);-statusverification(refertoclause4.3.4);-commonteststeps(refertoclause4.3.5).4.3.1StatetransitionsThefollowingclausesidentifytheteststepsusedintheATS.Ingeneral,eachteststeprepresentsastatetransition.ForexampleinthePSTNprotocol,PSTN_LE1_2istheteststepwhichbringstheLEPSTNprotocolFSMfromPSTN_path_stateLE1toPSTN_path_stateLE2.Thestatetransitionsaredeclaredintheparenthesis(originatingstate-destinationstate)whichfollowtheteststepnames.Sixgroupsofstatetransitionsaredefined:STARTUPstartuptheV5interfaceandputtheIUTintotheinitialstateasdefinedinclause5.1.5;CTRLstatetransitionsusedtopreambleandpostambletheControlprotocolbeforeatestpurposecanbeperformed;PSTNstatetransitionsusedtopreambleandpostamblethePSTNprotocolbeforeatestpurposecanbeperformed;LINKstatetransitionsusedtopreambleandpostambletheLinkcontrolprotocolbeforeatestpurposecanbeperformed;BCCstatetransitionsusedtopreambleandpostambletheBCCprotocolbeforeatestpurposecanbeperformed;PROTECTstatetransitionsusedtopreambleandpostambletheProtectionprotocolbeforeatestpurposecanbeperformed.TotesttheV5.2interfacecertainsequences(i.e.preamble)shallbeexecutedtoreachthestatewhichisthesubjectforthetestpurposes.4.3.1.1Start-upofV5.2interfaceThestart-upprocedureforaV5.2interfacedependsontheprovisioneddataconfiguration.Therefore,thethreePICSitemsN11,N12,M2andN9(seeclause6.5.1ofEN300347-2[3])areusedtodefinetheimplementedconfigurationoftheIUT.NOTE1:EN300347-2[3]requiresthatatleastoneofthethreePICSitemsN11,N12andM2shallbeset.NOTE2:PICSitemN9definestheconfigurationofIUTwithmultipleoronesingle2048kbit/sdigitallinksasaV5.2interface.Asingle2048kbit/sdigitallinkhavenoprotectionfunctionsimplemented.SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)15PICSN11orN12=YESPICSN11orN12=YESPICSN11andN12=NOPICSM2=YESPICSM2=YESPICSM2=NOLELT1Variant&interfaceIDreqvarandinterfaceIDreqvarandinterfaceIDreqvarandinterfaceIDvarandinterfaceIDvarandinterfaceIDvarandinterfaceIDLinkidentificationLinkidentificationreqLinkidentificationreqLinkidentificationreqLinkidentificationackLinkidentificationackLinkidentificationackLinkidentificationrelLinkidentificationrelLinkidentificationrelRestartRestartReqRestartReqRestartCompleteRestartCompleteRestartCompleteRestartCompletePSTNportFSMUnblockreqUnblockreqUnblockreqUnblockreqBlockcmdBlockcmdBlockcmdBlockcmdISDNportFSMNote1Note2Note3Note4Note5NOTE1:AtestoftheIUT'scapabilityofreceivingacommandtoresetsequencenumberiscoveredinclause5.6.2NOTE2:AtestoftheIUT'scapabilityofreceivingarequestforthevariantandinterfaceIDiscoveredinclause5.2.3.1.NOTE3:Thenumberofappearancesofthisoptionalpartofthesystemstart-upproceduredependsontheconfigurationoftheIUT.AtestoftheIUT'scapabilityofreceivingalinkidentificationrequestiscoveredinclause5.4.3.2.NOTE4:ToreachtheinitialstateoftheIUTPSTNuserportFSMasdefinedinclause5.1.5,theIUT'sunblockingrequestisrejectedbyLT1.Beforerejectingtheunblockrequest,itshallbeverifiedthattheIUTPSTNprotocolhasenteredthePSTN_path_stateAN6(PortBlocked).NOTE5:IfthePICSitemsN11andN12aresettoYES,thispartofthesystemstart-upprocedureappearstwice,oncefortheISDN-BAportandoncefortheISDN-PRAport.ToreachtheinitialstateoftheIUTISDN-BAuserportFSMand/ortheISDN-PRAuserportFSMasdefinedinclause5.1.5,theIUT'sunblockingrequestisrejectedbyLT1.Figure3:STARTUP_LEflowdiagramSIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)16PICSitemdescription:-N11:ISDN-BAportssupported;-N12:ISDN-PRAportssupported;-M2:PSTNportssupported;-N9:MultiplelinkV5.2interface.NOTE3:OneportofeachsupportedtypeshallbeprovisionedinawaythattheIUTtriestoentertheoperationalstatefortheseportsaftersystemstart-up(refertoclause5.1.6).NOTE4:AtSTARTUPtheLT1willrejectallrequestonacceleratedportstatealignmentbyrespondwiththecontrolmessageUBA-rejected(seeclause5.1.6).DependingonthesettingofthePICSitems,thestart-upprocedureisdescribedinfigure3.ThisflowdiagramdescribestheteststepcalledSTARTUP_LE.4.3.1.2Commoncontrolprotocol(systemmanagement)Thecontentsofthisclauseareidenticaltoclause4.3.1.2ofEN300324-5[1].4.3.1.3Controlprotocol(PSTNportFSM)Thecontentsofthisclauseareidenticaltoclause4.3.1.3ofEN300324-5[1]withthefollowingreplacements:CTRL_PSTN_LE20_10:OnreceiptofaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE204(blockcmd)theIUTPSTNuserportFSMshallenterstateLE1.0.IfthereisanyV5.2timeslotallocatedtotheaffectedport,theIUTshallsendaDE-ALLOCATIONmessage.InthatcasethisteststepiscompletedbysendingaDE-ALLOCATIONCOMPLETEmessage.NOTE:ThisresultsinastatetransitionofthePSTNprotocolaswell.ThePSTNprotocoloftheaffectedportisforcedtoenterthePSTN_path_stateLE6.4.3.1.4Controlprotocol(ISDN-BAportFSM)Thecontentsofthisclauseareidenticaltoclause4.3.1.4ofEN300324-5[1]withthefollowingreplacements:CTRL_ISDNBA_LE20_10:OnreceiptofaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE204(block_cmd)theIUTISDN-BAuserportFSMshallenterstateLE1.0.IfthereisanyV5.2timeslotallocatedtotheaffectedport,theIUTshallsendaDE-ALLOCATIONmessage.InthatcasethisteststepiscompletedbysendingaDE-ALLOCATIONCOMPLETEmessage.4.3.1.5Controlprotocol(ISDN-PRAportFSM)RefertoEN300347-1[2],table8.CTRL_ISDNPRA_LE20_10:OnreceiptofaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE204(block_cmd)theIUTISDN-PRAportFSMshallenterstateLE1.0.CompletethisteststepbysendingaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE209(TE_out_of_service).IfthereisanyV5.2timeslotallocatedtotheaffectedport,theIUTshallsendaDE-ALLOCATIONmessage.InthatcasethisteststepiscompletedbysendingaDE-ALLOCATIONCOMPLETEmessage.CTRL_ISDNPRA_LE10_20:OnreceiptofaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE202(unblockreq)theIUTshallrespondwiththePORTCONTROLmessagecontainingthecontrol_function_elementIEFE201(unblock_ack)andtheIUTISDN-PRAportFSMshallthenenterstateLE2.0.SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)174.3.1.6PSTNprotocolThecontentsofthisclauseareidenticaltoclause4.3.1.5ofEN300324-5[1]withthefollowingreplacements:PSTN_LEx_6:OnreceiptofaPORTCONTROLmessagecontainingthecontrol_function_elementIEFE204(blockcmd)theIUTPSTNprotocolshallenterPSTN_path_stateLE6.IfthereisanyV5.2timeslotallocatedtotheaffectedport,theIUTshallsendaDE-ALLOCATIONmessage.InthatcasethisteststepiscompletedbysendingaDE-ALLOCATIONCOMPLETEmessage.PSTN_LE1_2:Onreceiptofaterminatingcallrequest(FE-establish_request)theIUTprotocolshallsendanALLOCATIONmessage.OnreceiptofaDE-ALLOCATIONmessagetheIUTshallsendanESTABLISHmessageandenterPSTN_path_stateLE2.PSTN_LE4_5:OnreceiptofaSIGNALmessagecontainingafaultysequencenumbertheIUTPSTNprotocolshallsendaDISCONNECTmessageandenterPSTN_path_stateLE5.IfthereisanyV5.2timeslotallocatedtotheaffectedport,theIUTshallsendaDE-ALLOCATIONmessage.InthatcasethisteststepiscompletedbysendingaDE-ALLOCATIONCOMPLETEmessage.4.3.1.7LinkcontrolprotocolRefertoEN300347-1[2],table16.LINK_LE20_10:OnreceiptofaLINKCONTROLmessagecontainingthelink_control_functionIEFE304(link_block_cmd)theIUTlinkcontrolFSMshallenterstateLE1.0.NOTE:TheblockingofaV5.2linkresultsinaprotectionswitching(ifpossible)ofallC-pathscarriedbythatlink.LINK_LE10_20:OnreceiptofaLINKCONTROLmessagecontainingthelink_control_functionIEFE302(link_unblock_req)theIUTshallrespondwiththeLINKCONTROLmessagecontainingthelink_control_functionIEFE301(link_unblock_ack)andthenenterstateLE2.0.4.3.1.8BCCprotocolRefertoEN300347-1[2],clause17.5,table48.BCC_NULL:ThepurposeofthisteststepistogettheIUTtostateLEBcc0(Bccnull).BCC_ALLOC_WAIT:ThepurposeofthisteststepistogettheIUTtostateLEBcc1(Bccwaitingallocation).Onreceiptofanoriginating/terminatingcallattempt,theIUTshallsendanALLOCATIONmessagecontainingtheoriginatingUPreferencedintheUP_IDIE.BCC_CONN:ThepurposeofthisteststepistoallocateatimeslotinV5.2interface.Onreceiptofanoriginatingcallattempt,theIUTshallsendanALLOCATIONmessagecontainingtheoriginatingUPreferencedintheUP_IDIE.CompletetheteststepbysendinganALLOCATIONCOMPLETEmessage.BCC_DEALLOC_WAIT:ThepurposeofthisteststepistogettheIUTtostateLEBcc3(Bccwaitingde-allocation).Onreceiptofanoriginatingcallattempt,theIUTshallsendanALLOCATIONmessagecontainingtheoriginatingUPreferencedintheUP_IDIE.OnreceiptofanALLOCATIONCOMPLETEmessage,theIUTshallrespondtotheoriginatingcallattempt.Onreceiptofauserreleaserequest,theIUTshallsendaDE-ALLOCATIONmessagecontainingtheoriginatingUPreferencedintheIEUP_IDIEandtheallocatedV5TSreferencedintheV5_TS_IDIE.SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)18BCC_ALLOC_ABORT:ThepurposeofthisteststepistogettheIUTtostateLEBcc2(Bccallocationabort).OnreceiptofMDU-BCC(Allocationrequest),theIUTshallsendanALLOCATIONmessagecontainingtheterminatingUPreferencedintheUP_IDIE.OnreceiptofMDU-BCC(De-allocationrequest),theIUTshallsendaDE-ALLOCATIONmessagecontainingtheterminatingUPreferencedintheUP_IDIEandtheallocatedV5TSreferencedintheV5_TS_IDIE.BCC_AUDIT_WAIT:ThepurposeofthisteststepistogettheIUTtostateLEBcc4(Bccwaitingabort).TheIUTshallsendanAUDITmessage.ItisimplementationdependenthowtheAUDITprocedureisinitiated.BCC_DEALLOC:Thepurposeofthisteststepistode-allocateatimeslotinV5.2interface.4.3.1.9ProtectionprotocolRefertoEN300347-1[2],clause18.6,table65.PROTECT_SOLEx_0:OnreceiptofaRESETSNCOMmessage,theIUTshallsendaRESETSNACKmessage(IUTprotectionFSMentersstateSOLE0).CompletethisteststepbywaitingfortheexpirationoftimerTSO5.PROTECT_BACK_TO_INIT1:OnreceiptofaSWITCH-OVERREQmessagecontainingthelogical_C-channel_IDIE"logicalC-channel1"andthephysical_C-channel_IDIE"TS16ofprimarylink",theIUTshallsendaSWITCH-OVERCOMmessagecontainingthesamedata.CompletetheteststepbysendingaSWITCH-OVERACKmessagecontainingthesamedata.PROTECT_BACK_TO_INIT2:OnreceiptofaSWITCH-OVERREQmessagecontainingthelogical_C-channel_IDIE"logicalC-channel2"andthephysical_C-channel_IDIE"TS15ofprimarylink",theIUTshallsendaSWITCH-OVERCOMmessagecontainingthesamedata.CompletetheteststepbysendingaSWITCH-OVERACKmessagecontainingthesamedata.PROTECT_BACK_TO_INIT3:OnreceiptofaSWITCH-OVERREQmessagecontainingthelogical_C-channel_IDIE"logicalC-channel3"andthephysical_C-channel_IDIE"TS31ofprimarylink",theIUTshallsendaSWITCH-OVERCOMmessagecontainingthesamedata.CompletetheteststepbysendingaSWITCH-OVERACKmessagecontainingthesamedata.4.3.2PreamblesThepreambletestgroupcontainsthepreambleteststepsneededforinitializationoftheIUTbeforetestingtheparticulartestpurpose.Allcombinationsoftheteststepsdefinedinclauses4.3.1.2to4.3.1.9canbeusedtocreatepreambles.EachpreambleshallstartfromtheIUTinitialstateasdefinedinclause5.1.5.4.3.3PostamblesAftereachtestcasetheIUTshallbebroughtbacktotheinitialstateasdefinedinclause5.1.5.Allcombinationsoftheteststepsdefinedinclauses4.3.1.2to4.3.1.9canbeusedtocreatepostambles.SIST EN 300 347-5 V3.1.1:2005

ETSIETSIEN300347-5V3.1.1(2001-03)194.3.4Statusverification4.3.4.1PSTNprotocolThecontentsofthisclauseareidenticaltoclause4.3.4ofEN300324-5[1]withthefollowingreplacements.PSTN_CHECK_STATE_2(PathinitiatedbyLE)OnreceiptofaSIGNALmessagetheIUTPSTNprotocolshallsendaSTATUSENQUIRYmessagetheIUTPSTNprotocolisnotinoneofthePSTN_path_statesLE4andLE5.OnreceiptofaSTATUSmessagecontainingthecause_type"responsetostatusenquiry"andthestateIE"AN1"theIUTPSTNprotocolshallnotsendaDISCONNECTmessagetheIUTPSTNprotocolisnotinthePSTN_path_stateLE3.OnreceiptofaSIGNALmessage,theIUTPSTNprotocolshallsendagainaSTATUSENQUIRYmessage.OnreceiptofaSTATUSmessagecontainingthecause_type"responsetostatusenquiry"andthesta
...