SIST ETS 300 324-7 E2:2003

V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 7: Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer

Scope not communicated (nd)

Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo dostopovnemu omrežju (AN) – 7. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• Withdrawal Date: 30-Sep-1998
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: BC-T-340
• Ref Project: ETSI ETS 300 324-7 ed.2 (1999-04) - V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 7: Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer

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.1 za podporo dostopovnemu omrežju (AN) – 7. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežjeV interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 7: Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 324-7 E2SIST ETS 300 324-7 E2:en01-RNWREHU-SIST ETS 300 324-7 E2:SLOVENSKI
STANDARD



SIST ETS 300 324-7 E2:2003



DRAFTEUROPEANprETS 300 324-7TELECOMMUNICATIONDecember 1997STANDARDSecond EditionSource: SPSReference: RE/SPS-03055-7ICS:33.020Key words:V interface, V5 interface, AN, ISDN, layer 2, LE, PSTN, testing, TSS&TPSignalling Protocols and Switching (SPS);V interfaces at the digital Local Exchange (LE);V5.1 interface for the support of Access Network (AN);Part 7: Test Suite Structure and Test Purposes (TSS&TP)specification for the data link layerETSIEuropean 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: [e-mail].: [phone] - Fax: [phone]Copyright 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 1997. All rights reserved.SIST ETS 300 324-7 E2:2003



Page 2Draft prETS 300 324-7: December 1997Whilst 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 324-7 E2:2003



Page 3Draft prETS 300 324-7: December 1997ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84Test Suite Structure (TSS).94.1TSS overview.94.2Test groups.94.2.1Protocol groups.94.2.1.1Link Access Protocol for V5 interface - Envelope Functionsublayer (LAPV5-EF).94.2.1.2Link Access Protocol for V5 interface - Data Link sublayer(LAPV5-DL).94.2.2Main test groups.94.2.2.1Basic Interconnection (IT) tests.94.2.2.2Capability (CA) tests.104.2.2.3Valid Behaviour (BV) tests.104.2.2.4Inopportune Behaviour (BO) tests.104.2.2.5Invalid Behaviour (BI) tests.104.2.2.6Timer (TI).104.3Test step structure.104.3.1State transitions.104.3.1.1V5 interface start-up.104.3.1.2LAPV5-DL state transitions.114.3.2Preambles.124.3.3Postambles.124.3.4Status verification.124.3.5Common test steps.124.4Defaults.124.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs).134.5.1ASPs.134.5.2PDUs.134.6Timers and counters of the Abstract Test Suite (ATS).135Test Purposes (TP).145.1Introduction.145.1.1TP naming convention.145.1.2Source of TP definition.145.1.3Test strategy.155.1.4Procedures for which no TPs are defined.155.1.5Initial state.155.1.6Data configuration for AN and LE testing.155.2LAPV5-EF.165.2.1Basic interconnection tests.165.2.2Valid behaviour tests.165.2.3Invalid behaviour tests.165.3LAPV5-DL.175.3.1Basic interconnection tests.175.3.2Capability tests.17SIST ETS 300 324-7 E2:2003



Page 4Draft prETS 300 324-7: December 19975.3.3Valid behaviour.175.3.3.1State 9: link not established.175.3.3.2State 5: awaiting establishment.175.3.3.2.1State 5.0: establish.175.3.3.2.2State 5.1: re-establish.185.3.3.3State 7: multiple frame established.195.3.3.3.1State 7.0: TX: normal, RX: normal.195.3.3.3.2State 7.1: TX: normal, RX: REJ recovery.195.3.3.3.3State 7.4: TX: peer rec busy, RX: normal.205.3.3.3.4State 7.5: TX: peer rec busy, RX: REJ recovery.205.3.3.4State 8: timer recovery.215.3.3.4.1State 8.0: TX: normal, RX: normal.215.3.3.4.2State 8.1: TX: normal, RX: REJ recovery.215.3.3.4.3State 8.4: TX: peer rec busy, RX: normal.225.3.3.4.4State 8.5: TX: peer rec busy, RX: REJ recovery.225.3.4Inopportune behaviour.225.3.4.1State 7: multiple frame established.225.3.4.1.1State 7.0: TX: normal, RX: normal.225.3.4.1.2State 7.1: TX: normal, RX: REJ recovery.235.3.4.1.3State 7.4: TX: peer rec busy, RX: normal.235.3.4.2State 8: timer recovery.235.3.4.2.1State 8.0: TX: normal, RX: normal.235.3.5Invalid behaviour.235.3.5.1State 7: multiple frame established.235.3.5.1.1State 7.0: TX: normal, RX: normal.235.3.5.1.2State 7.1: TX: normal, RX: REJ recovery.245.3.5.1.3State 7.4: TX: peer rec busy, RX: normal.245.3.5.2State 8: timer recovery.255.3.5.2.1State 8.0: TX: normal, RX: normal.255.3.5.2.2State 8.1: TX: normal, RX: REJ recovery.255.3.5.2.3State 8.4: TX: peer rec busy, RX: normal.255.3.6Timer.255.3.6.1State 5: awaiting establishment.255.3.6.1.1State 5.0: establish.255.3.6.1.2State 5.1: re-establish.265.3.6.2State 7: multiple frame established.265.3.6.2.1State 7.0: TX: normal, RX: normal.265.3.6.2.2State 7.4: TX: peer rec. busy, RX: normal.265.3.6.3State 8: timer recovery.265.3.6.3.1State 8.0: TX: normal, RX: normal.265.3.6.3.2State 8.4: TX: peer rec. busy, RX: normal.26Annex A (informative):Bibliography.27History.28SIST ETS 300 324-7 E2:2003



Page 5Draft prETS 300 324-7: December 1997ForewordThis draft second edition European Telecommunication Standard (ETS) has been produced by theSignalling Protocols and Switching (SPS) Technical Committee of the European TelecommunicationsStandards Institute (ETSI), and is now submitted for the Public Enquiry phase of the ETSI standardsapproval procedure.This ETS is part 7 of a multi-part standard covering the V5.1 interface as described below:Part 1:"V5.1 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:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LEside)";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the network layer (LE side)";Part 7:"Test Suite Structure and Test Purposes (TSS&TP) specification for the data linklayer";Part 8:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the data link layer";Part 9:"Test specification for the physical layer".Proposed transposition datesDate of latest announcement of this ETS (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this ETS (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaSIST ETS 300 324-7 E2:2003



Page 6Draft prETS 300 324-7: December 1997Blank pageSIST ETS 300 324-7 E2:2003



Page 7Draft prETS 300 324-7: December 19971ScopeThis seventh part of ETS 300 324 contains the Test Suite Structure (TSS) and Test Purposes (TPs) forthe Data Link Layer (DLL) of the V5.1 interface.The conformance tests in this ETS provide a high probability of inter-operability of the DLL between anAccess Network (AN) and a Local Exchange (LE) infrastructure. This ETS covers only the proceduresdescribed in ETS 300 324-1 [1] which are based upon ETS 300 125 [3].ISO/IEC 9646-1 [5] is used as the basis for the methodology of conformance testing.ETS 300 324-1 [1] defines the sublayers of the DLL, i.e. Link Access Protocol for V5 interface (LAPV5)Data Link sublayer (LAPV5-DL), LAPV5 Envelope Function sublayer (LAPV5-EF) and the mappingfunction (refer to ETS 300 324-1 [1], figure 6 which illustrates this approach). Regarding the conformancetesting these sublayer functions are not tested separately. The test purposes defined in clause 5 covertesting of the LAPV5-DL (control protocol only), LAPV5-EF and the mapping function. The AN frame relayfunction is tested in co-operation with a generic test of an Integrated Services Digital Network (ISDN)D-channel.The limitation of the DLL test to the Control DL is based on the assumption that the Public SwitchedTelephone Network (PSTN) DL implementation is identical with the Control DL implementation. Thisneeds to be declared by the Implementation Under Test (IUT) supplier. Otherwise, the TPs defined for theControl DL may be used for the PSTN DL as well.2Normative referencesThis ETS incorporates by dated or 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-1 (1994) including amendment A1 (1996): "Signalling Protocolsand Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.1interface for the support of Access Network (AN); Part 1: V5.1 interfacespecification".[2]ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.1 interface for the support of AccessNetwork (AN); Part 2: Protocol Implementation Conformance Statement (PICS)proforma".[3]ETS 300 125 (1991): "Integrated Services Digital Network (ISDN); User-networkinterface data link layer specification; Application of CCITT RecommendationsQ.920/I.440 and Q.921/I.441".[4]ISO 7498: "Information Processing Systems - Open Systems Interconnection -Basic Reference Model".[5]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".SIST ETS 300 324-7 E2:2003



Page 8Draft prETS 300 324-7: December 19973Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply, together with those given inETS 300 324-1 [1]:Abstract Test Suite (ATS): See ISO/IEC 9646-1 [5].Data Link Layer (DLL): See ISO 7498 [4].Implementation Under Test (IUT): See ISO/IEC 9646-1 [5].Lower Tester (LT): See ISO/IEC 9646-1 [5].Network Layer (NWK): See ISO 7498 [4].Notional Upper Tester (UT): The upper layers of the System Under Test (SUT) are used to realize thefunctions of the UT, without any additional mechanism being installed.Physical Layer (PHL): See ISO 7498 [4].Point of Control and Observation (PCO): See ISO/IEC 9646-1 [5].Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5].PICS proforma: See ISO/IEC 9646-1 [5].Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [5].PIXIT proforma: See ISO/IEC 9646-1 [5].System Under Test (SUT): See ISO/IEC 9646-1 [5].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANAccess NetworkASPAbstract Service PrimitiveATSAbstract Test SuiteBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapabilityDLLData Link LayerEFaddrEnvelope Function addressFCSFrame Check SequenceFSMFinite State MachineIDIdentifierISDNIntegrated Services Digital NetworkITBasic InterconnectionIUTImplementation Under TestLAPDLink Access Protocol for the ISDN D-channelLAPV5Link Access Protocol for V5 interfaceLAPV5-DLLAPV5 Data Link sublayerLAPV5-EFLAPV5 Envelope Function sublayerLELocal ExchangeLTLower TesterNWKNetwork LayerPCOPoint of Control and ObservationSIST ETS 300 324-7 E2:2003



Page 9Draft prETS 300 324-7: December 1997PDUProtocol Data UnitPHLPhysical LayerPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPSTNPublic Switched Telephone NetworkRXReceiver conditionSAPIService Access Point IdentifierSUTSystem Under TestTEITerminal Endpoint IdentifierTITimerTPTest PurposeTSSTest Suite StructureTXTransmitter conditionUTUpper Tester4Test Suite Structure (TSS)4.1TSS overviewFigure 1 shows the structure of the V5.1 DLL test suite.V5DLLLAPV5_EFLAPV5_DLITCABIBVBOTIITBVBISTATESTATESTATESTATEFigure 1: DLL TSS4.2Test groups4.2.1Protocol groups4.2.1.1Link Access Protocol for V5 interface - Envelope Function sublayer (LAPV5-EF)The defined test purposes cover the LAPV5-EF procedures including the mapping function and the ANrelay function (see ETS 300 324-1 [1], figure 6).4.2.1.2Link Access Protocol for V5 interface - Data Link sublayer (LAPV5-DL)The defined test purposes cover the LAPV5-DL (control protocol only) procedures (seeETS 300 324-1 [1], figure 6).4.2.2Main test groups4.2.2.1Basic Interconnection (IT) testsThe IT test subgroup contains a basic set of test purposes which assures that there is a sufficientconformance for inter connection and that the chosen parameters are valid for the configuration.SIST ETS 300 324-7 E2:2003



Page 10Draft prETS 300 324-7: December 19974.2.2.2Capability (CA) testsCapability testing provides a limited testing to ascertain the main capabilities stated in the ProtocolImplementation Conformance Statements (PICSs) can be observed.4.2.2.3Valid Behaviour (BV) testsA valid test is a test where the message sequence and the message content is considered as valid (noMDL_ERR_IND is caused in the Finite State Machine (FSM) of the DLL entity).4.2.2.4Inopportune Behaviour (BO) testsThis test subgroup is intended to verify that the IUT is able to react properly, in case an inopportuneprotocol event occurs. Such an event is syntactically correct but it occurs when it is not expected (aMDL_ERR_IND is caused in the FSM of the DLL entity).4.2.2.5Invalid Behaviour (BI) testsThis test subgroup is intended to verify that the IUT is able to react properly having received an invalidProtocol Data Unit (PDU). Invalid PDU here means a syntactically invalid PDU and, therefore, aMDL_ERR_IND might be caused in the FSM of the DLL entity.4.2.2.6Timer (TI)The TI test group contains tests related to the system timers T200 and T203.4.3Test step structureGeneral dynamic behaviours should be described in test steps. The main test steps to apply the TPsdescribed in this ETS are described in this subclause.4.3.1State transitionsTwo groups of state transitions are defined:V5 interface start-up: this group contains the test steps to initialize the V5 interface.LAPV5-DL state transitions: this group contains test steps which describe state transitions of theLAPV5-DL implementation used in different preambles.4.3.1.1V5 interface start-upThe start-up procedure of a V5.1 IUT (AN or LE) depends on the configuration which is provisioned (referto subclause 5.1.6). The PICS items M1 and M2 (refer to ETS 300 324-2 [2], subclauses 6.5.1 and 6.6.1),further called TSPC_PSTN and TSPC_ISDNBA, are used to define the implemented configuration of theIUT.NOTE:ETS 300 324-2 [2] requires at least one of two the PICS items to be set to "Yes".PICS description:TSPC_PSTN:PSTN ports supported;TSPC_ISDNBA:ISDN-BA user ports supported.SIST ETS 300 324-7 E2:2003



Page 11Draft prETS 300 324-7: December 1997Figure 2 describes the start-up procedure.TSPC_ISDNBATSPC_PSTNTSPC_PSTNTSPC_ISDNBAIUTLT1Control-DLControl-DLControl-DLPSTN-DLSABMESABMEUAUAVariant and Interface ID reqVariant and Interface IDrestart reqrestart completerestart completeControl-DLSABMEUAControl-DLSABMEUAControl-DLVariant and Interface ID reqVariant and Interface IDControl-DLVariant and Interface ID reqVariant and Interface IDPSTN-DLSABMEUAControl-DLrestart reqrestart completerestart completeIUTLT1IUTLT1(note)(note)NOTE:Only valid if TSPC_PSTN is set.Figure 2: Start-up4.3.1.2LAPV5-DL state transitionsThe following test steps allow to reach any IUT state necessary for DLL testing:LAPV5_DL_51_9:state transition from state 5.1 to 9.On receipt of a DM response (F=1) the IUT enters state 9.LAPV5_DL_70_51:state transition from state 7.0 to 5.1.On receipt of a DM response (F=0) the IUT sends a SABME frame (P=1) and enters state 5.1.LAPV5_DL_70_71:state transition from state 7.0 to 7.1.On receipt of an I-frame (P=0) whose sequence number N(S) > V(R) the IUT sends a REJ response (F=0)and enters state 7.1.LAPV5_DL_70_74:state transition from state 7.0 to 7.4.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 7.4.LAPV5_DL_70_80:state transition from state 7.0. to 8.0.On T203 expiry the IUT sends a RR command (P=1) and enters state 8.0.LAPV5_DL_71_75:state transition from state 7.1 to 7.5.On receipt of a RNR command (P=1) the IUT sends a RR response and enters state 7.5.LAPV5_DL_80_81:state transition from state 8.0 to 8.1.On receipt of an I-frame (P=1) whose sequence number N(S) > V(R) the IUT sends a REJ response (F=1)and enters state 8.1.LAPV5_DL_80_84:state transition from state 8.0 to 8.4.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 8.4.SIST ETS 300 324-7 E2:2003



Page 12Draft prETS 300 324-7: December 1997LAPV5_DL_81_85:state transition from state 8.1 to 8.5.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 8.5.LAPV5_DL_9_50:state transition from state 9 to 5.0.On receipt of a DM response (F=0) the IUT sends a SABME frame (P=1) and enters state 5.0.4.3.2PreamblesThe preamble test group contains the preamble test steps needed for initialization of the IUT beforetesting the particular test purpose. The preambles are based on the state transition described insubclause 4.3.1.4.3.3PostamblesAfter each test, the IUT is brought back to the initial state.4.3.4Status verificationBased on the modifications to tables D-1 to D-3 of ETS 300 125 [3] as specified in ETS 300 324-1 [1],subclause 10.4.11.2, it is possible to identify the status of the IUT, if the IUT is in state 7 (multiple frameestablished). States 7.2, 7.3, 7.6 and 7.7 are not distinguished as it is not possible to bring the IUT intothis state (except under load condition).CHECK_STATE_70The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a REJ response (F=1) Þ different tostate 7.1.CHECK_STATE_71The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a RR response (F=1) Þ different tostate 7.0.CHECK_STATE_74No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) Þ the IUT is notin state 7.0, 7.1 or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a REJ response (F=1) Þ different tostate 7.5.CHECK_STATE_75No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) Þ the IUT is notin state 7.0, 7.1 or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a RR response (F=1) Þ different tostate 7.4.4.3.5Common test stepsThis test step group contains test steps which describe procedures which are used in more than one testcase, e.g. receive procedures of common acknowledgement messages.4.4DefaultsThe default section describes the behaviour in case of an unexpected test event.SIST ETS 300 324-7 E2:2003



Page 13Draft prETS 300 324-7: December 19974.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)4.5.1ASPsTwo ASPs are defined:-ph_data_req;-ph_data_ind.The PH-data information shall be defined as described in ETS 300 324-1 [1], figure 7. For the purpose ofDLL testing, only the Envelope Function address (EFaddr) and the Frame Check Sequence (FCS) arerelevant.The value of the flag sequence and the FCS are usually supplied by the V5.1 tester, but for testing of theLAPV5-EF functions it is necessary to corrupt the FCS value.4.5.2PDUsThe PDUs used on the V5.1 interface have to be split into two parts:1)PDUs sent to the LAPV5-DL level (refer to ETS 300 324-1 [1], clause 10):sabme_cmdSABME-command;ua_rspUA-response;dm_rspDM-response;rr_cmdRR-command;rr_rspRR-response;rnr_cmdRNR-command;rnr_rspRNR-response;rej_cmdREJ-command;rej_rspREJ-response;i_cmdI-command.2)PDUs sent to an ISDN-BA terminal via an ISDN-BA user port:refer to ETS 300 125 [3], table 5.4.6Timers and counters of the Abstract Test Suite (ATS)This subclause describes the timer and counters which shall be applied when implementing the TPs in aATS. The min and max indications define that the timer value represents the minimum or maximumtolerance of a timer. The timer values contain some additional tolerances for delays caused by testers.Timers used in the ATS are given in Timer Declarations part of the ATS.Counters used in the ATS are given in table 2.Table 2: ATS countersATS counternameATS countervalueCommentsReference toETS 300 324-1 [1]N2003Corresponding counter variable: RCsubclause 10.4.9N201260Maximum number of octets in an informationfieldsubclause 10.4.9SIST ETS 300 324-7 E2:2003



Page 14Draft prETS 300 324-7: December 19975Test Purposes (TP)5.1IntroductionClause 5 contains the TPs for V5.1 DLL testing. This subclause describes the test strategy of the TPs, thetest environment for which the TPs apply and the V5.1 procedures for which no TPs are defined.5.1.1TP naming conventionThe identifier of the TP is constructed according to the scheme in table 3.Table 3: TP identifier naming convention schemeIdentifier:TP=type of protocol:1LAPV5-EF(test group)2LAPV5-DL=category:1IT, Basic Interconnection Tests(test subgroup)2CA, Capability Tests3BV, Valid Behaviour Tests4BO, Inopportune Behaviour Tests5BI, Invalid Behaviour Tests6TI, Timertest purpose typeSSingle TP (not combined TP)=state(0-9)_(underscore) not relevant=substate(0-9)_(underscore) not relevant=sequential number(00-99)5.1.2Source of TP definitionThe test purposes have been based on the state tables D-1, D-2 and D-3 of ETS 300 125 [3] as modifiedby subclause 10.4.11.2 of ETS 300 324-1 [1]. To eliminate redundancy, the SDL diagrams B-1 to B-9 ofETS 300 125 [3] have been applied according to ETS 300 324-1 [1].Whenever in the TPs reference is made to ETS 300 125 [3], the restrictions imposed inETS 300 324-1 [1], subclause 10.4.11.2, shall apply.SIST ETS 300 324-7 E2:2003



Page 15Draft prETS 300 324-7: December 19975.1.3Test strategya)the following selection criteria have been applied to cover a maximum of test events with anappropriate number of test cases:-in tables D-1 to D-3 of ETS 300 125 [3], state actions which are identified by the characters"|" or "/" are not covered. These states are "impossible" by the definition of the DLL service orby the definition of the peer-to-peer data link procedures;b)in relation to the SDL diagrams B-1 to B-9 of ETS 300 125 [3], the testing is limited:-if parameter variation (P/F and C/R bit) is not considered in a SDL diagram path, only oneparameter value is tested;-if the SDL diagram paths are the same for different states, only one state is explicitly tested;c)to test the protocol error handling (BI test cases), more extensive testing is necessary even thoughsome tests are testing the same SDL diagram paths as others;d)the AN frame relay function is tested in co-operation with a generic test of an ISDN D-channel.5.1.4Procedures for which no TPs are defineda)only the Control DL is tested. The limitation of the DLL tests to the Control DL is based on theassumption that the PSTN DL implementation is identical with the Control DL implementation. Thisshall be dec
...

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.1 za podporo dostopovnemu omrežju (AN) – 7. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežjeV interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 7: Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 324-7 Edition 2SIST ETS 300 324-7 E2:2003en01-december-2003SIST ETS 300 324-7 E2:2003SLOVENSKI
STANDARD



SIST ETS 300 324-7 E2:2003



EUROPEANETS 300 324-7TELECOMMUNICATIONApril 1999STANDARDSecond EditionSource: SPSReference: RE/SPS-09055-7ICS:33.020Key words:AN, ISDN, layer 2, LE, PSTN, testing, TSS&TP, V interface, V5 interfaceV interfaces at the digital Local Exchange (LE);V5.1 interface for the support of Access Network (AN);Part 7: Test Suite Structure and Test Purposes (TSS&TP)specification for the data link layerETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: [e-mail] - http://www.etsi.orgTel.: [phone] - Fax: [phone]Copyright 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 1999. All rights reserved.SIST ETS 300 324-7 E2:2003



Page 2ETS 300 324-7: April 1999Whilst 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 Standards Making Support Dept." at the address shown on the title page.SIST ETS 300 324-7 E2:2003



Page 3ETS 300 324-7: April 1999ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84Test Suite Structure (TSS).94.1TSS overview.94.2Test groups.94.2.1Protocol groups.94.2.1.1Link Access Protocol for V5 interface - Envelope Functionsublayer (LAPV5-EF).94.2.1.2Link Access Protocol for V5 interface - Data Link sublayer(LAPV5-DL).94.2.2Main test groups.94.2.2.1Basic Interconnection (IT) tests.94.2.2.2Capability (CA) tests.104.2.2.3Valid Behaviour (BV) tests.104.2.2.4Inopportune Behaviour (BO) tests.104.2.2.5Invalid Behaviour (BI) tests.104.2.2.6Timer (TI).104.3Test step structure.104.3.1State transitions.104.3.1.1V5 interface start-up.104.3.1.2LAPV5-DL state transitions.114.3.2Preambles.124.3.3Postambles.124.3.4Status verification.124.3.5Common test steps.124.4Defaults.124.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs).134.5.1ASPs.134.5.2PDUs.134.6Timers and counters of the Abstract Test Suite (ATS).135Test Purposes (TP).145.1Introduction.145.1.1TP naming convention.145.1.2Source of TP definition.145.1.3Test strategy.145.1.4Procedures for which no TPs are defined.155.1.5Initial state.155.1.6Data configuration for AN and LE testing.155.2LAPV5-EF.165.2.1Basic interconnection tests.165.2.2Valid behaviour tests.165.2.3Invalid behaviour tests.165.3LAPV5-DL.175.3.1Basic interconnection tests.175.3.2Capability tests.175.3.3Valid behaviour.175.3.3.1State 9: link not established.175.3.3.2State 5: awaiting establishment.17SIST ETS 300 324-7 E2:2003



Page 4ETS 300 324-7: April 19995.3.3.2.1State 5.0: establish.175.3.3.2.2State 5.1: re-establish.185.3.3.3State 7: multiple frame established.195.3.3.3.1State 7.0: TX: normal, RX: normal.195.3.3.3.2State 7.1: TX: normal, RX: REJrecovery.195.3.3.3.3State 7.4: TX: peer rec busy, RX:normal.205.3.3.3.4State 7.5: TX: peer rec busy, RX: REJrecovery.205.3.3.4State 8: timer recovery.205.3.3.4.1State 8.0: TX: normal, RX: normal.205.3.3.4.2State 8.1: TX: normal, RX: REJrecovery.215.3.3.4.3State 8.4: TX: peer rec busy, RX:normal.215.3.3.4.4State 8.5: TX: peer rec busy, RX: REJrecovery.215.3.4Inopportune behaviour.225.3.4.1State 7: multiple frame established.225.3.4.1.1State 7.0: TX: normal, RX: normal.225.3.4.1.2State 7.1: TX: normal, RX: REJrecovery.225.3.4.1.3State 7.4: TX: peer rec busy, RX:normal.225.3.4.2State 8: timer recovery.225.3.4.2.1State 8.0: TX: normal, RX: normal.225.3.5Invalid behaviour.225.3.5.1State 7: multiple frame established.225.3.5.1.1State 7.0: TX: normal, RX: normal.225.3.5.1.2State 7.1: TX: normal, RX: REJrecovery.245.3.5.1.3State 7.4: TX: peer rec busy, RX:normal.245.3.5.2State 8: timer recovery.245.3.5.2.1State 8.0: TX: normal, RX: normal.245.3.5.2.2State 8.1: TX: normal, RX: REJrecovery.255.3.5.2.3State 8.4: TX: peer rec busy, RX:normal.255.3.6Timer.255.3.6.1State 5: awaiting establishment.255.3.6.1.1State 5.0: establish.255.3.6.1.2State 5.1: re-establish.255.3.6.2State 7: multiple frame established.255.3.6.2.1State 7.0: TX: normal, RX: normal.255.3.6.2.2State 7.4: TX: peer rec. busy, RX:normal.265.3.6.3State 8: timer recovery.265.3.6.3.1State 8.0: TX: normal, RX: normal.265.3.6.3.2State 8.4: TX: peer rec. busy, RX:normal.26Annex A (informative):Bibliography.27History.28SIST ETS 300 324-7 E2:2003



Page 5ETS 300 324-7: April 1999ForewordThis 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 7 of a multi-part standard covering the V5.1 interface as described below:Part 1:"V5.1 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:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LEside)";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the network layer (LE side)";Part 7:"Test Suite Structure and Test Purposes (TSS&TP) specification for the data linklayer";Part 8:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the data link layer";Part 9:"Test specification for the physical layer".Transposition datesDate of adoption of this ETS:26 March 1999Date of latest announcement of this ETS (doa):30 June 1999Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 December 1999Date of withdrawal of any conflicting National Standard (dow):31 December 1999SIST ETS 300 324-7 E2:2003



Page 6ETS 300 324-7: April 1999Blank pageSIST ETS 300 324-7 E2:2003



Page 7ETS 300 324-7: April 19991ScopeThis seventh part of ETS 300 324 contains the Test Suite Structure (TSS) and Test Purposes (TPs) forthe Data Link Layer (DLL) of the V5.1 interface.The conformance tests in this ETS provide a high probability of inter-operability of the DLL between anAccess Network (AN) and a Local Exchange (LE) infrastructure. This ETS covers only the proceduresdescribed in ETS 300 324-1 [1] which are based upon ETS 300 402-2 [3].ISO/IEC 9646-1 [5] is used as the basis for the methodology of conformance testing.ETS 300 324-1 [1] defines the sublayers of the DLL, i.e. Link Access Protocol for V5 interface (LAPV5)Data Link sublayer (LAPV5-DL), LAPV5 Envelope Function sublayer (LAPV5-EF) and the mappingfunction (refer to ETS 300 324-1 [1], figure 6 which illustrates this approach). Regarding the conformancetesting these sublayer functions are not tested separately. The test purposes defined in clause 5 covertesting of the LAPV5-DL (control protocol only), LAPV5-EF and the mapping function. The AN frame relayfunction is tested in co-operation with a generic test of an Integrated Services Digital Network (ISDN)D-channel.The limitation of the DLL test to the Control DL is based on the assumption that the Public SwitchedTelephone Network (PSTN) DL implementation is identical with the Control DL implementation. Thisneeds to be declared by the Implementation Under Test (IUT) supplier. Otherwise, the TPs defined for theControl DL may be used for the PSTN DL as well.2Normative referencesThis ETS incorporates by dated or 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-1 (1994) including amendment A1: "V interfaces at the digitalLocal Exchange (LE); V5.1 interface for the support of Access Network (AN);Part 1: V5.1 interface specification".[2]ETS 300 324-2 (1994): "V interfaces at the digital Local Exchange (LE); V5.1interface for the support of Access Network (AN); Part 2: ProtocolImplementation Conformance Statement (PICS) proforma".[3]ETS 300 402-2 (1995): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2:General protocol specification [ITU-T Recommendation Q.921 (1993),modified]".[4]ISO 7498: "Information processing systems - Open Systems Interconnection -Basic Reference Model".[5]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".SIST ETS 300 324-7 E2:2003



Page 8ETS 300 324-7: April 19993Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply, together with those given inETS 300 324-1 [1]:abstract test suite: See ISO/IEC 9646-1 [5]data link layer: See ISO 7498 [4]implementation under test: See ISO/IEC 9646-1 [5]lower tester: See ISO/IEC 9646-1 [5]network layer: See ISO 7498 [4]notional upper tester: The upper layers of the System Under Test (SUT) are used to realize thefunctions of the UT, without any additional mechanism being installedphysical layer: See ISO 7498 [4]point of control and observation: See ISO/IEC 9646-1 [5]Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5]PICS proforma: See ISO/IEC 9646-1 [5]Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [5]PIXIT proforma: See ISO/IEC 9646-1 [5]system under test: See ISO/IEC 9646-1 [5]3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANAccess NetworkASPAbstract Service PrimitiveATSAbstract Test SuiteBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapabilityDLLData Link LayerEFaddrEnvelope Function addressFCSFrame Check SequenceFSMFinite State MachineIDIdentifierISDNIntegrated Services Digital NetworkITBasic InterconnectionIUTImplementation Under TestLAPDLink Access Protocol for the ISDN D-channelLAPV5Link Access Protocol for V5 interfaceLAPV5-DLLAPV5 Data Link sublayerLAPV5-EFLAPV5 Envelope Function sublayerLELocal ExchangeLTLower TesterNWKNetwork (Layer)PCOPoint of Control and ObservationSIST ETS 300 324-7 E2:2003



Page 9ETS 300 324-7: April 1999PDUProtocol Data UnitPHLPhysical LayerPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPSTNPublic Switched Telephone NetworkRXReceiver conditionSAPIService Access Point IdentifierSUTSystem Under TestTEITerminal Endpoint IdentifierTITimerTPTest PurposeTSSTest Suite StructureTXTransmitter conditionUTUpper Tester4Test Suite Structure (TSS)4.1TSS overviewFigure 1 shows the structure of the V5.1 DLL test suite.V5DLLLAPV5_EFLAPV5_DLITCABIBVBOTIITBVBISTATESTATESTATESTATEFigure 1: DLL TSS4.2Test groups4.2.1Protocol groups4.2.1.1Link Access Protocol for V5 interface - Envelope Function sublayer (LAPV5-EF)The defined test purposes cover the LAPV5-EF procedures including the mapping function and the ANrelay function (see ETS 300 324-1 [1], figure 6).4.2.1.2Link Access Protocol for V5 interface - Data Link sublayer (LAPV5-DL)The defined test purposes cover the LAPV5-DL (control protocol only) procedures (seeETS 300 324-1 [1], figure 6).4.2.2Main test groups4.2.2.1Basic Interconnection (IT) testsThe IT test subgroup contains a basic set of test purposes which assures that there is a sufficientconformance for inter connection and that the chosen parameters are valid for the configuration.SIST ETS 300 324-7 E2:2003



Page 10ETS 300 324-7: April 19994.2.2.2Capability (CA) testsCapability testing provides a limited testing to ascertain the main capabilities stated in the ProtocolImplementation Conformance Statements (PICSs) can be observed.4.2.2.3Valid Behaviour (BV) testsA valid test is a test where the message sequence and the message content is considered as valid (noMDL_ERR_IND is caused in the Finite State Machine (FSM) of the DLL entity).4.2.2.4Inopportune Behaviour (BO) testsThis test subgroup is intended to verify that the IUT is able to react properly, in case an inopportuneprotocol event occurs. Such an event is syntactically correct but it occurs when it is not expected (aMDL_ERR_IND is caused in the FSM of the DLL entity).4.2.2.5Invalid Behaviour (BI) testsThis test subgroup is intended to verify that the IUT is able to react properly having received an invalidProtocol Data Unit (PDU). Invalid PDU here means a syntactically invalid PDU and, therefore, aMDL_ERR_IND might be caused in the FSM of the DLL entity.4.2.2.6Timer (TI)The TI test group contains tests related to the system timers T200 and T203.4.3Test step structureGeneral dynamic behaviours should be described in test steps. The main test steps to apply the TPsdescribed in this ETS are described in this subclause.4.3.1State transitionsTwo groups of state transitions are defined:-V5 interface start-up: this group contains the test steps to initialize the V5 interface.-LAPV5-DL state transitions: this group contains test steps which describe state transitions of theLAPV5-DL implementation used in different preambles.4.3.1.1V5 interface start-upThe start-up procedure of a V5.1 IUT (AN or LE) depends on the configuration which is provisioned (referto subclause 5.1.6). The PICS items M1 and M2 (refer to ETS 300 324-2 [2], subclauses 6.5.1 and 6.6.1),further called TSPC_PSTN and TSPC_ISDNBA, are used to define the implemented configuration of theIUT.NOTE:ETS 300 324-2 [2] requires at least one of two the PICS items to be set to "Yes".PICS description:TSPC_PSTN:PSTN ports supported;TSPC_ISDNBA:ISDN-BA user ports supported.SIST ETS 300 324-7 E2:2003



Page 11ETS 300 324-7: April 1999Figure 2 describes the start-up procedure.TSPC_ISDNBATSPC_PSTNTSPC_PSTNTSPC_ISDNBAIUTLT1Control-DLControl-DLControl-DLPSTN-DLSABMESABMEUAUAVariant and Interface ID reqVariant and Interface IDrestart reqrestart completerestart completeControl-DLSABMEUAControl-DLSABMEUAControl-DLVariant and Interface ID reqVariant and Interface IDControl-DLVariant and Interface ID reqVariant and Interface IDPSTN-DLSABMEUAControl-DLrestart reqrestart completerestart completeIUTLT1IUTLT1(note)(note)NOTE:Only valid if TSPC_PSTN is set.Figure 2: Start-up4.3.1.2LAPV5-DL state transitionsThe following test steps allow to reach any IUT state necessary for DLL testing:LAPV5_DL_51_9:state transition from state 5.1 to 9.On receipt of a DM response (F=1) the IUT enters state 9.LAPV5_DL_70_51:state transition from state 7.0 to 5.1.On receipt of a DM response (F=0) the IUT sends a SABME frame (P=1) and enters state 5.1.LAPV5_DL_70_71:state transition from state 7.0 to 7.1.On receipt of an I-frame (P=0) whose sequence number N(S) > V(R) the IUT sends a REJ response (F=0)and enters state 7.1.LAPV5_DL_70_74:state transition from state 7.0 to 7.4.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 7.4.LAPV5_DL_70_80:state transition from state 7.0. to 8.0.On T203 expiry the IUT sends a RR command (P=1) and enters state 8.0.LAPV5_DL_71_75:state transition from state 7.1 to 7.5.On receipt of a RNR command (P=1) the IUT sends a RR response and enters state 7.5.LAPV5_DL_80_81:state transition from state 8.0 to 8.1.On receipt of an I-frame (P=1) whose sequence number N(S) > V(R) the IUT sends a REJ response (F=1)and enters state 8.1.LAPV5_DL_80_84:state transition from state 8.0 to 8.4.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 8.4.SIST ETS 300 324-7 E2:2003



Page 12ETS 300 324-7: April 1999LAPV5_DL_81_85:state transition from state 8.1 to 8.5.On receipt of a RNR command (P=1) the IUT sends a RR response (F=1) and enters state 8.5.LAPV5_DL_9_50:state transition from state 9 to 5.0.On receipt of a DM response (F=0) the IUT sends a SABME frame (P=1) and enters state 5.0.4.3.2PreamblesThe preamble test group contains the preamble test steps needed for initialization of the IUT beforetesting the particular test purpose. The preambles are based on the state transition described insubclause 4.3.1.4.3.3PostamblesAfter each test, the IUT is brought back to the initial state.4.3.4Status verificationBased on the modifications to tables D-1 to D-3 of ETS 300 402-2 [3] as specified in ETS 300 324-1 [1],subclause 10.4.11.2, it is possible to identify the status of the IUT, if the IUT is in state 7 (multiple frameestablished). States 7.2, 7.3, 7.6 and 7.7 are not distinguished as it is not possible to bring the IUT intothis state (except under load condition).CHECK_STATE_70The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a REJ response (F=1) Þ different tostate 7.1.CHECK_STATE_71The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a RR response (F=1) Þ different tostate 7.0.CHECK_STATE_74No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) Þ the IUT is notin state 7.0, 7.1 or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a REJ response (F=1) Þ different tostate 7.5.CHECK_STATE_75No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) Þ the IUT is notin state 7.0, 7.1 or 8.x.On receipt of an I-frame (P=1) with N(S) ¹ V(R), the IUT shall send a RR response (F=1) Þ different tostate 7.4.4.3.5Common test stepsThis test step group contains test steps which describe procedures which are used in more than one testcase, e.g. receive procedures of common acknowledgement messages.4.4DefaultsThe default section describes the behaviour in case of an unexpected test event.SIST ETS 300 324-7 E2:2003



Page 13ETS 300 324-7: April 19994.5Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)4.5.1ASPsTwo ASPs are defined:-ph_data_req;-ph_data_ind.The PH-data information shall be defined as described in ETS 300 324-1 [1], figure 7. For the purpose ofDLL testing, only the Envelope Function address (EFaddr) and the Frame Check Sequence (FCS) arerelevant.The value of the flag sequence and the FCS are usually supplied by the V5.1 tester, but for testing of theLAPV5-EF functions it is necessary to corrupt the FCS value.4.5.2PDUsThe PDUs used on the V5.1 interface have to be split into two parts:1)PDUs sent to the LAPV5-DL level (refer to ETS 300 324-1 [1], clause 10):sabme_cmdSABME-command;ua_rspUA-response;dm_rspDM-response;rr_cmdRR-command;rr_rspRR-response;rnr_cmdRNR-command;rnr_rspRNR-response;rej_cmdREJ-command;rej_rspREJ-response;i_cmdI-command.2)PDUs sent to an ISDN-BA terminal via an ISDN-BA user port:refer to ETS 300 402-2 [3], table 5.4.6Timers and counters of the Abstract Test Suite (ATS)This subclause describes the timer and counters which shall be applied when implementing the TPs in aATS. The min and max indications define that the timer value represents the minimum or maximumtolerance of a timer. The timer values contain some additional tolerances for delays caused by testers.Timers used in the ATS are given in Timer Declarations part of the ATS.Counters used in the ATS are given in table 1.Table 1: ATS countersATS counternameATS countervalueCommentsReference toETS 300 324-1 [1]N2003Corresponding counter variable: RCsubclause 10.4.9N201260Maximum number of octets in an informationfieldsubclause 10.4.9SIST ETS 300 324-7 E2:2003



Page 14ETS 300 324-7: April 19995Test Purposes (TP)5.1IntroductionClause 5 contains the TPs for V5.1 DLL testing. This subclause describes the test strategy of the TPs, thetest environment for which the TPs apply and the V5.1 procedures for which no TPs are defined.5.1.1TP naming conventionThe identifier of the TP is constructed according to the scheme in table 2.Table 2: TP identifier naming convention schemeIdentifier:TP=type of protocol:1LAPV5-EF(test group)2LAPV5-DL=category:1IT, Basic Interconnection Tests(test subgroup)2CA, Capability Tests3BV, Valid Behaviour Tests4BO, Inopportune Behaviour Tests5BI, Invalid Behaviour Tests6TI, Timertest purpose typeSSingle TP (not combined TP)=state(0-9)_(underscore) not relevant=substate(0-9)_(underscore) not relevant=sequential number(00-99)5.1.2Source of TP definitionThe test purposes have been based on the state tables D-1, D-2 and D-3 of ETS 300 402-2 [3] asmodified by subclause 10.4.11.2 of ETS 300 324-1 [1]. To eliminate redundancy, the SDL diagrams B-1 toB-9 of ETS 300 402-2 [3] have been applied according to ETS 300 324-1 [1].Whenever in the TPs reference is made to ETS 300 402-2 [3], the restrictions imposed inETS 300 324-1 [1], subclause 10.4.11.2, shall apply.5.1.3Test strategya)The following selection criteria have been applied to cover a maximum of test events with anappropriate number of test cases:-in tables D-1 to D-3 of ETS 300 402-2 [3], state actions which are identified by the characters"|" or "/" are not covered. These states are "impossible" by the definition of the DLL service orby the definition of the peer-to-peer data link procedures;b)In relation to the SDL diagrams B-1 to B-9 of ETS 300 402-2 [3], the testing is limited:-if parameter variation (P/F and C/R bit) is not considered in a SDL diagram path, only oneparameter value is tested;-if the SDL diagram paths are the same for different states, only one state is explicitly tested;SIST ETS 300 324-7 E2:2003



Page 15ETS 300 324-7: April 1999c)To test the protocol error handling (BI test cases), more extensive testing is necessary even thoughsome tests are testing the same SDL diagram paths as others.d)The AN frame relay function is tested in co-operation with a generic test of an ISDN D-channel.5.1.4Procedures for which no TPs are defineda)Only the Control DL is tested. The limitation of the DLL tests to the Control DL is based on theassumption that the PSTN DL implementation is identical with the Control DL implementation. Thisshall be declared by the IUT supplier in a Protocol Implementation eXtra Information for Testing(PIXIT). Otherwise the TPs defined for the Control DL can be used for the PSTN DL as well.b)To test the IUT status (marked in TPs as new/remain in state), the test steps defined insubclause 4.3.4 shall be applied. States 9, 5.0, 5.1 and 8.x cannot be checked, therefore no statuscheck is defined if the IUT is supposed to be in one of those states. In general, the sta
...