SIST ETS 300 347-5:1997

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih telefonskih centralah (LE) - Vmesnik V5.2 za podporo dostopovnega omrežja (AN) - 5. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) za omrežno plast na strani krajevne centrale (LE)Signalling Protocols and Switching (SPS) - 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)35.100.30Omrežni slojNetwork layer33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 347-5 Edition 1SIST ETS 300 347-5:1997en01-november-1997SIST ETS 300 347-5:1997SLOVENSKI
STANDARD
EUROPEANETS 300 347-5TELECOMMUNICATIONFebruary 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-03003.4-2ICS:33.020, 33.080, 35.100.30Key words:V interface, V5 interface, PSTN, ISDN, LE, TSS&TP, testing, layer 3Signalling Protocols and Switching (SPS);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)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 347-5:1997

Page 2ETS 300 347-5: February 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 347-5:1997

Page 3ETS 300 347-5: February 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.104Test Suite Structure (TSS).114.1Overview.114.2Test groups.124.2.1Protocol groups.134.2.1.1Control protocol.134.2.1.2Public Switched Telephone Network (PSTN) protocol.134.2.1.3Link control protocol.134.2.1.4Bearer Channel Connection (BCC) protocol.134.2.1.5Protection protocol.134.2.2Main test groups.144.2.2.1Basic interconnection tests (IT).144.2.2.2Capability tests (CA).144.2.2.3Valid behaviour tests (BV).144.2.2.4Inopportune behaviour tests (BO).144.2.2.5Invalid behaviour tests (BI).144.2.2.6Timer expiry and counter mismatch tests (TI).144.2.2.6.1Timers and counters of the Control protocol.144.2.2.6.2Timers and counters of the PSTN protocol.144.2.2.6.3Timers and counters of the Link control protocol.144.2.2.6.4Timers and counters of the BCC protocol.144.2.2.6.5Timers and counters of the Protection protocol.144.2.2.6.6Timers and counters of the LE system management.154.3Test step structure.154.3.1State transitions.154.3.1.1Start-up of V5.2 interface.154.3.1.2Common control protocol (system management).174.3.1.3Control protocol (PSTN port FSM).174.3.1.4Control protocol (ISDN-BA port FSM).174.3.1.5Control protocol (ISDN-PRA port FSM).174.3.1.6PSTN protocol.184.3.1.7Link control protocol.184.3.1.8BCC protocol.184.3.1.9Protection protocol.194.3.2Preambles.194.3.3Postambles.194.3.4Status verification.204.3.4.1PSTN protocol.204.3.4.2Link control FSM.204.3.5Common test steps.204.4Defaults.204.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs).204.5.1ASPs.204.5.2PDUs.214.5.2.1Common control protocol.214.5.2.2Port control protocol.214.5.2.3PSTN protocol.214.5.2.4Link control protocol.21SIST ETS 300 347-5:1997

Page 4ETS 300 347-5: February 19964.5.2.5BCC protocol.214.5.2.6Protection protocol.214.5.3Information elements.214.5.3.1Variable length information elements.214.5.3.1.1Control protocol.214.5.3.1.2PSTN protocol.214.5.3.1.3Link control protocol.214.5.3.1.4BCC protocol.224.5.3.1.5Protection protocol.224.5.3.2Single octet information elements.224.5.3.2.1Control protocol.224.5.3.2.2PSTN protocol.224.5.3.2.3Link control protocol.224.5.3.2.4BCC protocol.224.5.3.2.5Protection protocol.224.6Timers and counters of the Abstract Test Suite (ATS).225Test Purposes (TPs).245.1Introduction.245.1.1Test purpose naming convention.245.1.2Source of test purpose definition.255.1.3Test strategy.255.1.3.1Common control protocol.255.1.3.2Port control protocol.255.1.3.3PSTN protocol.255.1.3.4Link control protocol.265.1.3.5BCC protocol.265.1.3.6Protection protocol.275.1.4Requirements not covered by test purposes.275.1.5Initial states.275.1.6Test and data configuration requirements.285.2Control protocol.285.2.1Basic interconnection tests (V5NWKLE/CTRL/IT).285.2.2Capability tests (V5NWKLE/CTRL/CA).285.2.3Valid behaviour tests (V5NWKLE/CTRL/BV).285.2.3.1V5NWKLE/CTRL/BV/COM.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.295.2.4Inopportune behaviour tests (V5NWKLE/CTRL/BO).315.2.4.1V5NWKLE/CTRL/BO/COM.315.2.4.2V5NWKLE/CTRL/BO/PORT.315.2.4.2.1V5NWKLE/CTRL/BO/PORT/TRANS.315.2.4.2.2V5NWKLE/CTRL/BO/PORT/ISDNBA.315.2.4.2.3V5NWKLE/CTRL/BO/PORT/ISDNPRA.315.2.5Invalid behaviour tests (V5NWKLE/CTRL/BI).325.2.6Timer expiry and counter mismatch tests (V5NWKLE/CTRL/TI).325.3PSTN protocol.325.4Link control protocol.325.4.1Basic interconnection tests (V5NWKLE/LINK/IT).325.4.2Capability tests (V5NWKLE/LINK/CA).325.4.3Valid behaviour tests (V5NWKLE/LINK/BV).325.4.3.1V5NWKLE/LINK/BV/TRANS.325.4.3.2V5NWKLE/LINK/BV/LINK.335.4.4Inopportune behaviour tests (V5NWKLE/LINK/BO).455.4.4.1V5NWKLE/LINK/BO/TRANS.455.4.4.2V5NWKLE/LINK/BO/LINK.455.4.5Invalid behaviour tests (V5NWKLE/LINK/BI).485.4.5.1V5NWKLE/LINK/BI/TRANS.485.4.6Timer expiry and counter mismatch tests (V5NWKLE/LINK/TI).495.4.6.1V5NWKLE/LINK/TI/TRANS.49SIST ETS 300 347-5:1997

Page 5ETS 300 347-5: February 19965.5BCC protocol.495.5.1Basic interconnection tests (V5NWKLE/BCC/IT).505.5.2Capability tests (V5NWKLE/BCC/CA).505.5.3Valid behaviour tests (V5NWKLE/BCC/BV).515.5.4Inopportune behaviour tests (V5NWKLE/BCC/BO).555.5.5Invalid behaviour tests (V5NWKLE/BCC/BI).575.5.6Timer expiry and counter mismatch tests (V5NWKLE/BCC/TI).595.6Protection protocol.605.6.1Basic interconnection tests (V5NWKLE/PROTECT/IT).615.6.2Capability tests (V5NWKLE/PROTECT/CA).615.6.3Valid behaviour tests (V5NWKLE/PROTECT/BV).615.6.4Invalid behaviour tests (V5NWKLE/PROTECT/BI).665.6.5Timer expiry and counter mismatch tests (V5NWKLE/PROTECT/TI).66Annex A (informative):Bibliography.69History.70SIST ETS 300 347-5:1997

Page 6ETS 300 347-5: February 1996Blank pageSIST ETS 300 347-5:1997

Page 7ETS 300 347-5: February 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 5 of a multi-part standard covering the V5.2 interface as described below:Part 1:"V5.2 interface specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (ANside)";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the network layer (AN side)";Part 5:"TSS&TP specification for the network layer (LE side)";Part 6:"ATS and partial PIXIT proforma specification for the network layer (LE side)";Part 7:"TSS&TP specification for the data link layer";Part 8:"ATS and partial PIXIT proforma specification for the data link layer";Part 9:"Test specification for the physical layer".Transposition datesDate of adoption of this ETS:1 March 1996Date of latest announcement of this ETS (doa):31 May 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 November 1996Date of withdrawal of any conflicting National Standard (dow):30 November 1996SIST ETS 300 347-5:1997

Page 8ETS 300 347-5: February 1996Blank pageSIST ETS 300 347-5:1997

Page 9ETS 300 347-5: February 19961ScopeThis fifth part of ETS 300 347 contains the Test Suite Structure and Test Purposes (TSS&TP) for thenetwork layer and parts of the system management of the Local Exchange (LE) side of a V5.2 interface.The objective of this ETS is to provide conformance tests giving a high probability of inter-operability of anAccess Network (AN) and a LE from different manufacturers over the V5.2 interface. This ETS coversonly the procedures described in ETS 300 347-1 [2].ISO/IEC 9646-1 [4] and ISO/IEC 9646-2 [5] are used as the basis for the test methodology.This ETS needs to be read in conjunction with ETS 300 324-5 [1]. The two documents share a commonformat and clauses within ETS 300 324-5 [1] are directly referenced.Annex A lists the bibliography.2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 324-5 (1995): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.1 interface for the support of AccessNetwork (AN); Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the network layer (LE side)".[2]ETS 300 347-1 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.2 interface for the support of AccessNetwork (AN); Part 1: V5.2 interface specification".[3]ETS 300 347-2 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.2 interface for the support of AccessNetwork (AN); Part 2: Protocol Implementation Conformance Statement (PICS)proforma".[4]ISO/IEC 9646-1 (1995): "Information technology - Open systems interconnection- Conformance testing methodology and framework - Part 1: General concepts".[5]ISO/IEC 9646-2 (1995): "Information technology - Open systems interconnection- Conformance testing methodology and framework - Part 2: Abstract test suitespecification".SIST ETS 300 347-5:1997

Page 10ETS 300 347-5: February 19963Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply, in addition to those given inETS 300 324-5 [1] and ETS 300 347-1 [2]:specified information element: Information element identifier as defined in ETS 300 347-1 [2].unspecified information element: Information element identifier which is not defined inETS 300 347-1 [2].incorrect information element: A specified information element carrying information element typeswhich are not defined in ETS 300 347-1 [2].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:AISAlarm Indication SignalANAccess NetworkASPAbstract Service PrimitiveATSAbstract Test SuiteBCCBearer Channel ConnectionBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapabilityCOMCommon control protocolCTRLControlFEFunction ElementFSMFinite State MachineIDIdentifierIEInformation ElementISDNIntegrated Services Digital NetworkISDN-BAISDN Basic AccessISDN-PRAISDN Primary Rate AccessITBasic InterconnectionIUTImplementation Under TestL3addrLayer 3 addressLELocal ExchangeLT1Lower Tester 1MDUManagement Data UnitMPHManagement Physical layerNWKNetwork layerPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementsPSTNPublic Switched Telephone NetworkRAIRemote Alarm IndicationREQRequestSNSequence NumberSUTSystem Under TestTETerminal Equipment (ISDN or PSTN)TITimerTPTest PurposeTSTime SlotTSSTest Suite StructureUPUser PortSIST ETS 300 347-5:1997

Page 11ETS 300 347-5: February 19964Test Suite Structure (TSS)4.1OverviewFigure 1 shows the structure of the V5.2 network layer test suite.V5NWKLEITCABVCTRLCOMTRANS/PROTOCOLSYS_MAN/ RESTSYS_MAN REVYTRANS/PROTOCOLPORTPSTNISDN-BAISDN-PRACOMTRANS/PROTOCOLBITRANS/PROTOCOLPORTCOMTRANS/PROTOCOLTRANS/PROTOCOLPORTTIITCABVPSTNSTATESTATESTATESTATEBOBITIITCABVTRANS/PROTOCOLLINKLINK CTRLTRANS/PROTOCOLTITRANS/PROTOCOLBIITBV BCCCAITBVPROTECTTIBICABOCOMTRANS/PROTOCOLPORTTRANS/PROTOCOLSYS_MAN REVYISDN-BAISDN-PRATRANS/PROTOCOLLINK CTRLBOBOBITIFigure 1: Network Layer LE test suite structureSIST ETS 300 347-5:1997

Page 12ETS 300 347-5: February 19964.2Test groupsFigure 2 gives an overview of the various protocol entities of a V5.2 interface. Table 1 maps each protocolentity on tested protocol groups.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_FSMFEMDUnationalPSTNprotocolISDNlayer 2managementMPHLE_BCCFigure 2: Network layer LE - protocol entity overviewTable 1: Names used in figure 2 that correspond to ETS 300 347-1 [2]Network layerprotocol entitiesProtocol entities defined inETS 300 347-1 [2]Protocol group referencesLE_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 ETS 300 347-5:1997

Page 13ETS 300 347-5: February 19964.2.1Protocol groups4.2.1.1Control protocolThe contents of this subclause are identical to subclause 4.2.1.1 of ETS 300 324-5 [1] with the followingadditions for the ISDN-PRA user port Finite State Machine (FSM).Depending on provisioning the following configuration is tested:LE_ISDN-PRA_user_port: The blocking, blocking request and co-ordinated unblocking procedures of theLE_ISDN-PRA_user_port_FSM are verified in the test groups V5NWKLE/CTRL/BV/PORT/ISDNPRA and V5NWKLE/CTRL/BO/PORT/ISDNPRA.4.2.1.2Public Switched Telephone Network (PSTN) protocolThe contents of this subclause are identical to subclause 4.2.1.2 of ETS 300 324-5 [1].4.2.1.3Link control protocolAll tests in the Link control protocol (V5NWKLE/LINK) test group are intended to verify as thoroughly aspossible the various procedures of the LE_link_control_protocol entity. Depending on provisioning thefollowing configurations are covered:LE_link_control_protocol: The normal and exceptional procedures of the LE_link_control_protocol areverified in the test groups V5NWKLE/LINK/BV/TRANS, V5NWKLE/LINK/BO/TRANS andV5NWKLE/LINK/TI/TRANS.The error handling procedures are verified in the test group V5NWKLE/LINK/BI/TRANS.LE_link_control_FSM: The link failure, link blocking, link blocking request, co-ordinated link unblockingand link identification procedures of the LE_link_control_FSM are verified in the test groupV5NWKLE/LINK/BV/LINK and V5NWKLE/LINK/BO/LINK.4.2.1.4Bearer Channel Connection (BCC) protocolAll tests in the BCC protocol (V5NWKLE/BCC) test group are intended to verify as thoroughly as possiblethe various procedures of the LE_BCC protocol entity.The following BCC procedures are covered:-normal and exceptional bearer channel allocation procedure;-normal and exceptional bearer channel de-allocation procedure;-audit procedure;-AN internal failure notification procedure;-error handling procedures.4.2.1.5Protection protocolAll tests in the Protection protocol (V5NWKLE/PROTECT) test group are intended to verify as thoroughlyas possible the various procedures of the LE Protection protocol entity.The following Protection protocol procedures are covered:-transmission of Protection protocol messages;-normal and exceptional sequence number reset procedure;-normal and exceptional standard protection switch-over procedure initiated by LE side;-normal and exceptional dedicated protection switch-over procedure initiated by OS LE;-normal and exceptional switch-over procedure requested by AN side;-error handling procedures.SIST ETS 300 347-5:1997

Page 14ETS 300 347-5: February 19964.2.2Main test groups4.2.2.1Basic interconnection tests (IT)The contents of this subclause are identical to subclause 4.2.2.1 of ETS 300 324-5 [1].4.2.2.2Capability tests (CA)The contents of this subclause are identical to subclause 4.2.2.2 of ETS 300 324-5 [1].4.2.2.3Valid behaviour tests (BV)The contents of this subclause are identical to subclause 4.2.2.3 of ETS 300 324-5 [1].4.2.2.4Inopportune behaviour tests (BO)The contents of this subclause are identical to subclause 4.2.2.4 of ETS 300 324-5 [1].4.2.2.5Invalid behaviour tests (BI)The contents of this subclause are identical to subclause 4.2.2.5 of ETS 300 324-5 [1].4.2.2.6Timer expiry and counter mismatch tests (TI)Different timers and counters are defined to supervise the various state transitions. This test group isintended to verify that the FSM is reacting properly to an expire of one of the timers or counter mismatch.4.2.2.6.1Timers and counters of the Control protocolThe contents of this subclause are identical to subclause 4.2.2.6.1 of ETS 300 324-5 [1].4.2.2.6.2Timers and counters of the PSTN protocolThe contents of this subclause are identical to subclause 4.2.2.6.2 of ETS 300 324-5 [1].4.2.2.6.3Timers and counters of the Link control protocolRefer to the ETS 300 347-1 [2], table 23.LCTO1LINK CONTROL message sent4.2.2.6.4Timers and counters of the BCC protocolRefer to the ETS 300 347-1 [2], table 46.TBCC1ALLOCATION sentTBCC2DE-ALLOCATION sentTBCC3DE-ALLOCATION sentTBCC4AUDIT sent4.2.2.6.5Timers and counters of the Protection protocolRefer to the ETS 300 347-1 [2], table 64.TSO1SWITCH-OVER COM sentTSO2OS-SWITCH-OVER COM sentTSO4RESET SN COM sentTSO5RESET SN COM receivedSIST ETS 300 347-5:1997

Page 15ETS 300 347-5: February 1996Refer to the ETS 300 347-1 [2], subclause 18.6.2.VP(S)Send State VariableVP(R)Receive State Variable4.2.2.6.6Timers and counters of the LE system managementThe contents of this subclause are identical to subclause 4.2.6.3 of ETS 300 324-5 [1].4.3Test step structureGeneral dynamic behaviours are described in test steps which can be called from all test cases within theAbstract Test Suite (ATS):state transitions (refer to subclause 4.3.1);preambles(refer to subclause 4.3.2);postambles(refer to subclause 4.3.3);status verification(refer to subclause 4.3.4);common test steps(refer to subclause 4.3.5).4.3.1State transitionsThe following subclauses identify the test steps used in the ATS. In general, each test step represents astate transition. For example in the PSTN protocol, PSTN_LE1_2 is the test step which brings the LEPSTN protocol FSM from PSTN_path_state LE1 to PSTN_path_state LE2. The state transitions aredeclared in the parenthesis (originating state - destination state) which follow the test step names.Six groups of state transitions are defined:STARTUPstart up the V5 interface and put the IUT into the initial state as defined in subclause5.1.5.CTRLstate transitions used to preamble and postamble the Control protocol before a testpurpose can be performed.PSTNstate transitions used to preamble and postamble the PSTN protocol before a testpurpose can be performed.LINKstate transitions used to preamble and postamble the Link control protocol before atest purpose can be performed.BCCstate transitions used to preamble and postamble the BCC protocol before a testpurpose can be performed.PROTECTstate transitions used to preamble and postamble the Protection protocol before a testpurpose can be performed.To test the V5.2 interface certain sequences (i.e. preamble) shall be executed to reach the state which isthe subject for the test purposes.4.3.1.1Start-up of V5.2 interfaceThe start-up procedure for a V5.2 interface depends on the provisioned data configuration. Therefore, thethree PICS items N11, N12 and N2 (see subclause 6.5.1 of ETS 300 347-2 [3]) are used to define theimplemented configuration of the IUT.NOTE 1:ETS 300 347-2 [3] requires that at least one of the three PICS items shall be set.SIST ETS 300 347-5:1997

Page 16ETS 300 347-5: February 1996PICS N11 or N12 = YESPICS N11 or N12 = YESPICS N11 and N12 = NOPICS N2 = YESPICS N2 = YESPICS N2 = NOLELT1Variant & interface IDreq var and interface IDreq var and interface IDreq var and interface IDvar and interface IDvar and interface IDvar and interface IDLink identificationLink identification reqLink identification reqLink identification reqLink identification ackLink identification ackLink identification ackLink identification relLink identification relLink identification relRestartRestart ReqRestart ReqRestart CompleteRestart CompleteRestart CompleteRestart CompletePSTN port FSMUnblock reqUnblock reqUnblock reqUnblock reqBlock cmdBlock cmdBlock cmdBlock cmdISDN port FSMNote 1Note 2Note 3Note 4Note 5NOTE 1:A test of the IUT's capability of receiving a request for the variant and interface ID is covered insubclause 5.2.3.1.NOTE 2:The number of appearances of this part of the system start-up procedure depends on theconfiguration of the IUT. A test of the IUT's capability of receiving a link identification request iscovered in subclause 5.4.3.2.NOTE 3:LT1 shall wait for the receipt of restart complete from the IUT before sending restart complete.NOTE 4:To reach the initial state of the IUT PSTN user port FSM as defined in subclause 5.1.5, theIUT's unblocking request is rejected by LT1. Before rejecting the unblock request, it shall beverified that the IUT PSTN protocol has entered the PSTN_path_state AN6 (Port Blocked).NOTE 5:If the PICS items N11 and N12 are set to YES, this part of the system start-up procedureappears twice, once for the ISDN-BA port and once for the ISDN-PRA port. To reach the initialstate of the IUT ISDN-BA user port FSM and/or the ISDN-PRA user port FSM as defined insubclause 5.1.5, the IUT's unblocking request is rejected by LT1.Figure 3: STARTUP_LE flow diagramSIST ETS 300 347-5:1997

Page 17ETS 300 347-5: February 1996PICS item description:N11:ISDN-BA ports supported;N12:ISDN-PRA ports supported;N2:PSTN ports supported.NOTE 2:One port of each supported type shall be provisioned in a way that the IUT tries toenter the operational state for these ports after system startup (refer to subclause5.1.6).Depending on the setting of the PICS items, the start-up procedure is described in figure 3. This flowdiagram describes the test step called STARTUP_LE.4.3.1.2Common control protocol (system management)The contents of this subclause are identical to subclause 4.3.1.2 of ETS 300 324-5 [1].4.3.1.3Control protocol (PSTN port FSM)The contents of this subclause are identical to subclause 4.3.1.3 of ETS 300 324-5 [1] with the followingreplacements:CTRL_PSTN_LE20_10On receipt of a PORT CONTROL message containing the control_function_element IE FE204 (blockcmd) the IUT PSTN user port FSM shall enter state LE1.0.If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATIONmessage. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.NOTE:This results in a state transition of the PSTN protocol as well. The PSTN protocol ofthe affected port is forced to enter the PSTN_path_state LE6.4.3.1.4Control protocol (ISDN-BA port FSM)The contents of this subclause are identical to subclause 4.3.1.4 of ETS 300 324-5 [1] with the followingreplacements:CTRL_ISDNBA_LE20_10On receipt of a PORT CONTROL message containing the control_function_element IE FE204(block_cmd) the IUT ISDN-BA user port FSM shall enter state LE1.0.If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATIONmessage. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.4.3.1.5Control protocol (ISDN-PRA port FSM)Refer to the ETS 300 347-1 [2], table 8.CTRL_ISDNPRA_LE20_10On receipt of a PORT CONTROL message containing the control_function_element IE FE204(block_cmd) the IUT ISDN-PRA port FSM shall enter state LE1.0.Complete this test step by sending a PORT CONTROL message containing the control_function_elementIE FE209 (TE_out_of_service).If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATIONmessage. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.SIST ETS 300 347-5:1997

Page 18ETS 300 347-5: February 1996CTRL_ISDNPRA_LE10_20On receipt of a PORT CONTROL message containing the control_function_element IE FE202 (unblockreq) the IUT shall respond with the PORT CONTROL message containing the control_function_elementIE FE201 (unblock_ack) and the IUT ISDN-PRA port FSM shall then enter state LE2.0.4.3.1.6PSTN protocolThe contents of this subclause are identical to subclause 4.3.1.5 of ETS 300 324-5 [1] with the followingreplacements:PSTN_LEx_6On receipt of a PORT CONTROL message containing the control_function_element IE FE204 (blockcmd) the IUT PSTN protocol shall enter PSTN_path_state LE6.If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATIONmessage. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.PSTN_LE1_2On receipt of a terminating call request (FE-establish_request) the IUT protocol shall send anALLOCATION message.On receipt of a DE-ALLOCATION message the IUT shall send an ESTABLISH message and enterPSTN_path_state LE2.PSTN_LE4_5On receipt of a SIGNAL message containing a faulty sequence number the IUT PSTN protocol shall senda DISCONNECT message and enter PSTN_path_state LE5.If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATIONmessage. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.PSTN_LE1_3_4On receipt of an ESTABLISH message the IUT shall send an ESTABLISH ACK and an ALLOCATIONmessage and the IUT PSTN protocol shall enter PSTN_path_state LE4.Complete this step by sending an ALLOCATION COMPLETE message.4.3.1.7Link control protocolLINK_LE20_10On receipt of a LINK CONTROL message containing the link_control_function IE FE304 (link_block_cmd)the IUT link control FSM shall enter state LE1.0.NOTE:The blocking of a V5.2 link results in a protection switching (if possible) of all C-pathscarried by that link.LINK_LE10_20On receipt of a LINK CONTROL message containing the link_control_function IE FE302(link_unblock_req) the IUT shall respond with the LINK CONTROL message containing thelink_control_function IE FE301 (link_unblock_ack) and then enter state LE2.0.4.3.1.8BCC protocolBCC_ALLOCOn receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing theoriginating UP referenced in the UP_ID IE.BCC_CONNOn receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing theoriginating UP referenced in the UP_ID IE.Complete the test step by sending an ALLOCATION COMPLETE message.SIST ETS 300 347-5:1997

Page 19ETS 300 347-5: February 1996BCC_DEALLOCOn receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing theoriginating UP referenced in the UP_ID IE.On receipt of an ALLOCATION COMPLETE message, the IUT shall respond to the originating callattempt.On receipt of a user release request, the IUT shall send a DE-ALLOCATION message containing theoriginating UP referenced in the IE UP_ID IE and the allocated V5 TS referenced in the V5_TS_ID IE.BCC_AUDITOn receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing theoriginating UP referenced in the UP_ID IE.On receipt of an ALLOCATION REJECT message containing the reject_cause IE "connection alreadypresent at the UP to a different V5 TS", the IUT shall send an AUDIT message containing only the UP_IDIE.4.3.1.9Protection protocolPROTECT_SOLEx_0On receipt of a RESET SN COM message, the IUT shall send a RESET SN ACK message (IUTprotection FSM enters state SOLE0).Complete this teststep by waiting for the expiration of timer TSO5.PROTECT_BACK_TO_INIT1On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel1" and the physical_C-channel_ID IE "TS 16 of primary link", the IUT shall send a SWITCH-OVER COMmessage containing the same data.Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.PROTECT_BACK_TO_INIT2On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel2" and the physical_C-channel_ID IE "TS 15 of primary link", the IUT shall send a SWITCH-OVER COMmessage containing the same data.Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.PROTECT_BACK_TO_INIT3On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel3" and the physical_C-channel_ID IE "TS 31 of primary link", the IUT shall send a SWITCH-OVER COMmessage containing the same data.Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.4.3.2PreamblesThe preamble test group contains the preamble test steps needed for initialization of the IUT beforetesting the particular test purpose. All combinations of the test steps defined in subclauses 4.3.1.2 to4.3.1.9 can be used to create preambles. Each preamble shall start from the IUT initial state as defined insubclause 5.1.5.4.3.3PostamblesAfter each test case the IUT shall be brought back to the initial state as defined in subclause 5.1.5. Allcombinations of the test steps defined in subclauses 4.3.1.2 to 4.3.1.9 can be used to create postambles.SIST ETS 300 347-5:1997

Page 20ETS 300 347-5: February 19964.3.4Status verification4.3.4.1PSTN protocolThe contents of this subclause are identical to subclause 4.3.4 of ETS 300 324-5 [1] with the followingreplacements:PSTN_CHECK_STATE_2(Path initiated by LE)On receipt of a SIGNAL message the IUT PSTN protocol shall send a STATUS ENQUIRY message Þthe IUT PSTN protocol is not in one of the PSTN_path_states LE4 and LE5.On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE"AN1" the IUT PSTN protocol shall not send a DISCONNECT message Þ the IUT PSTN protocol is not inthe PSTN_path_state LE3.On receipt of a SIGNAL message, the IUT PSTN protocol shall send again a STATUS ENQUIRYmessage.On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE"AN3" the IUT shall send a DISCONNECT and a DE-ALLOCATION message Þ the IUT PSTN protocol isnot in one of the PSTN_path_states LE0, LE1 and LE6.Complete this test step by sending a DISCONNECT COMPLETE and a DE-ALLOCATION COMPLETEmessage (IUT PSTN protocol enters the PSTN_path_state LE1).PSTN_CHECK_STATE_4(Path active)On receipt of an ESTABLISH message the IUT PSTN protocol shall send a STATUS ENQUIRY message Þ the IUT PSTN protocol is not in one of the PSTN_path_states LE1, LE2, LE3 and LE5.On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE"AN2" the IUT shall send a DISCONNECT and a DE-ALLOCATION message Þ the IUT PSTN protocol isnot in one of the PSTN_path_states LE0 and LE6.Complete this test step by sending a DISCONNECT COMPLETE and a DE-ALLOCATION COMPLETEmessage (IUT PSTN protocol enters the PSTN_path_state LE1).4.3.4.2Link control FSMLINK_CHECK_IDOn receipt of a message containing the link_control_function IE FE-IDReq (link_identification_req) the IUTshall send a message containing the link_control_function IE FE-IDAck (link_identification_ack) andframes with Sa7 bit set to zero.On receipt of a message containing the link_control_function IE FE-IDRel (link_identification_rel) the IUTshall send frames with Sa7 bit set to one.4.3.5Common test stepsThe contents of this subclause are identical to subclause 4.3.5 of ETS 300 324-5 [1].4.4DefaultsThe contents of this subclause are identical to subclause 4.4 of ETS 300 324-5 [1].4.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)4.5.1ASPsThe contents of this subclause are identical to subclause 4.5.1 of ETS 300 324-5 [1].SIST ETS 300 347-5:1997

Page 21ETS 300 347-5: February 19964.5.2PDUs4.5.2.1Common control protocolThe contents of this subclause are identical to subclause 4.5.2.1 of ETS 300 324-5 [1].4.5.2.2Port control protocolThe contents of this subclause are identical to subclause 4.5.2.2 of ETS 300 324-5 [1].4.5.2.3PSTN protocolThe contents of this subclause are identical to subclause 4.5.2.3 of ETS 300 324-5 [1].4.5.2.4Link control protocollink_ctrllink_ctrl_ack4.5.2.5BCC protocolbcc_allocationbcc_allocation_completebcc_allocation_rejectbcc_deallocationbcc_deallocation_completebcc_deallocation_rejectbcc_auditbcc_audit_completebcc_an_faultbcc_an_fault_ackbcc_protocol_error4.5.2.6Protection protocolprotect_switch_over_reqprotect_switch_over_comprotect_os_switch_over_comprotect_switch_over_ackprotect_switch_over_rejectprotect_protocol_errorprotect_reset_sn_comprotect_reset_sn_ack4.5.3Information elements4.5.3.1Variable length information elements4.5.3.1.1Control protocolThe contents of this subclause are identical to subclause 4.5.3.1.1 of ETS 300 324-5 [1].4.5.3.1.2PSTN protocolThe contents of this subclause are identical to subclause 4.5.3.1.2 of ETS 300 324-5 [1].4.5.3.1.3Link control protocollink_control_functionSIST ETS 300 347-5:1997

Page 22ETS 300 347-5: February 19964.5.3.1.4BCC protocolbcc_user_port_identbcc_ISDN_port_channel_identbcc_V5-time_slot_identbcc_multi_slot_mapbcc_rejection_causebcc_protocol_error_causebcc_connection-incomplete4.5.3.1.5Protection protocolprotect_sequence_numberprotect_physical_c_channel_identprotect_logical_c_channel_identprotect_rejection_causeprotect_protocol_error_cause4.5.3.2Single octet information elements4.5.3.2.1Control protocolThe contents of this subclause are identical to subclause 4.5.3.2.1 of ETS 300 324-5 [1].4.5.3.2.2PSTN protocolThe contents of this subclause are identical to subclause 4.5.3.2.2 of ETS 300 324-5 [1].4.5.3.2.3Link control protocolThere are no single octet information elements defined within the Link control protocol.4.5.3.2.4BCC protocolThere are no single octet information elements defined within the BCC protocol.4.5.3.2.5Protection protocolThere are no single octet information elements defined within the Protection protocol.4.6Timers and counters of the Abstract Test Suite (ATS)This subclause describes the timers and counters used in the ATS. The min and max indications define ifthe timer value represents the minimum or maximum limit of a timer. The timer values contain someadditional tolerances for delays caused by test simulators. Therefore, a bigger timer tolerance is giventhan defined in ETS 300 347-1 [2]:Minimum value of ATS timer=ETS timer - ETS tolerance;Maximum value of ATS timer=ETS timer + 2 x ETS tolerance.The repetition of messages by the IUT shall be tested in the following way: The message has to berepeated within the time period T_min < T < T_max. This testing procedure applies to the tests in the TI-test group only.Table 2 gives the ATS timers which are used in addition to those defined in subclause 4.6 ofETS 300 324-5 [1].SIST ETS 300 347-5:1997

Page 23ETS 300 347-5: February 1996Table 2: ATS timer values and references to ETS 300 347-1 [2]ATS timer nameATS timer value[s]ETS timer nameReference toETS 300 347-1 [2]LCTO1_max1,2LCTO1clause 16, table 23LCTO1_min0,9TPERS_max0,15- 30Persistencesubclause 16.1.3TPERS_min0,05 - 22,5check timerTBCC1_max0,6 - 1,8TBCC1clause 17, table 46TBCC1_min0,45 - 1,2TBCC2_max2,4TBCC2clause 17, table 46TBCC2_min1,8TBCC3_max2,4TBCC3clause 17, table 46TBCC3_min0,8TBCC4_max0,6 - 1,8TBCC4clause 17, table 46TBCC4_min0,45 - 1,2TBCC5_max1,8TBCC5clause 17, table 46TSO1_max1,8TSO1clause 18, table 64TSO1_min1,2TSO2_max1,8TSO2clause 18, table 64TSO2_min1,2TSO3_max1,8TSO3clause 18, table 64TSO4_max24TSO4clause 18, table 64TSO4_min18TSO5_max12TSO5clause 18, table 64TSO5_min9Table 3 gives the ATS counters which are used in addition to those defined in subclause 4.6 ofETS 300 324-5 [1].Table 3: Protocol counter values and references to ETS 300 347-1 [2]ATS counternameATS countervalueExplanationReference toETS 300 347-1 [2]NLCO11Allowed number of repetitions of the LINKCONTROL messageclause 16, table 23NBCC11Allowed number of repetitions of theALLOCATION messageclause 17, table 46NBCC21Allowed
...