SIST ETS 300 402-6:1998

• Abstract:

  TSS&TP for user&network

• Status: Published
• Publication Date: 31-May-1998
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• ICS: 35.100.20 - Data link layer
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jun-1998
• Due Date: 01-Jun-1998
• Completion Date: 01-Jun-1998
• Mandate: T-234A
• Ref Project: ETSI ETS 300 402-6 ed.1 (1997-01) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 6: Test Suite Structure and Test Purposes (TSS&TP) specification for the general protocol

SIST ETS 300 402-6:1998 is a SIST version of an ETSI European Telecommunications Standard for testing the ISDN DSS1 data link layer general protocol. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for user and network implementations at the T reference point, or the coincident S and T reference point. In practice, it tells test developers what behaviors to verify and how to organize those tests.

What does SIST ETS 300 402-6:1998 specify?

SIST ETS 300 402-6:1998 specifies the TSS&TP for conformance testing of the DSS1 data link layer general protocol for pan-European ISDN. The scope is limited to implementations at the T reference point or the coincident S and T reference point, and it supports both the user side and the network side.

The document is organized into these main parts:

• Clause 1 sets the scope.
• Clause 2 lists normative references.
• Clause 3 gives definitions.
• Clause 4 gives abbreviations.
• Clause 5 shows the Test Suite Structure (TSS).
• Clause 6 defines the Test Purposes (TPs).
• Clause 7 covers compliance.
• Clause 8 gives requirements for a comprehensive testing service.

Figure 1 presents the test suite structure, and the structure divides the tests into Layer management and Data control, each further split by data link state and behavior type.

What are the key requirements of SIST ETS 300 402-6:1998?

The key content is the set of test purposes in clause 6. SIST ETS 300 402-6:1998 turns the base protocol requirements into named test objectives that a tester can execute against an Implementation Under Test (IUT). That matters because it gives a repeatable way to check conformance state by state.

Test-purpose structure and naming

Clause 6.1 defines a naming convention that encodes the suite, side, category, state, group, and sequence number. Clause 6.1.3 also standardizes each TP into header, stimulus, reaction, and message-structure parts. In practice, this helps labs match a test to the exact protocol behavior being checked.

Test method and source

Clause 6.1.2 states that the TPs are based on ETS 300 402-2, and clause 6.1.4 says the analysis was done from the T reference point viewpoint. It also says the tests use Protocol Data Units (PDUs) rather than primitives. For implementers, that means the tests are framed in actual exchanged frames and messages.

Layer management tests

Clause 6.2.1 covers TEI management procedures for both user and network roles. The tests exercise Identity request, Identity check request, Identity assigned, Identity denied, Identity remove, and Identity verify handling across several data link states. In practice, this checks that TEI assignment, verification, and removal behave correctly when a terminal or network side receives valid or unexpected management frames.

Data control tests

Clause 6.2.2 covers establishment, release, and transfer behavior for the data link. It checks reactions to SABME, DISC, DM, UA, RR, REJ, RNR, FRMR, I frames, and UI frames in states such as 4, 5.0, 5.1, 6.0, 7.0, 7.1, 7.4, and 8.0. For a buyer or test engineer, this is the core of verifying link setup, release, acknowledgements, retransmission, and error recovery.

Invalid and exceptional behavior

Across both layer management and data control, the TPs cover valid behavior, inopportune behavior, syntactically invalid frames, timer expiry, and counter limits. This includes checks for frame check errors, wrong bit settings, unsupported SAPIs, overlength information fields, and undefined frames. That matters because interoperability depends not only on normal exchanges but also on predictable handling of bad input.

Timers and counters

Clause 6 includes timer-based and counter-based cases such as T200, T201, and T202, plus counts such as N200, N201, N202, and k. These tests show whether retransmission and retry limits are handled as expected. In practice, they verify the implementation’s persistence and its stop conditions during repeated failures.

What terms does SIST ETS 300 402-6:1998 define?

• Abstract Test Suite (ATS) - The set of abstract test cases derived for conformance testing.
• Abstract Test Method (ATM) - The testing method used to structure how the tests are applied.
• Implementation Under Test (IUT) - The device or protocol entity being checked.
• Protocol Implementation Conformance Statement (PICS) - The supplier’s statement of which features are implemented.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Extra implementation details needed to run the tests.
• Test Purpose (TP) - A single stated behavior or response that the test must verify.
• Point of control and observation - The point where the tester controls stimuli and observes responses.
• lower tester - The test component defined by the OSI testing framework for lower-layer control.

Who uses SIST ETS 300 402-6:1998?

SIST ETS 300 402-6:1998 is used by conformance test engineers, telecom equipment manufacturers, and test laboratories that validate ISDN DSS1 layer 2 behavior. Quality managers and certification teams use it to select relevant tests from a PICS and to check whether a user-side or network-side implementation follows the expected state transitions. It is also relevant to buyers and integrators who need evidence that a product has been tested against the DSS1 data link layer test purposes.

Which standards are used with SIST ETS 300 402-6:1998?

• ETS 300 402-2 - Provides the general protocol specification that the test purposes are based on.
• ETS 300 402-4 - Provides the PICS proforma used to decide which tests apply.
• ISO/IEC 9646-1 - Gives the general conformance testing concepts, including ATS and IUT.
• ISO/IEC 9646-2 - Gives the abstract test suite specification framework.
• ISO/IEC 9646-3 - Gives the Tree and Tabular Combined Notation used in the test language.
• ITU-T Recommendation I.112 - Supplies ISDN vocabulary definitions.
• ITU-T Recommendation I.411 - Defines the ISDN user-network reference configurations used for the reference points in scope.

What does the SIST ETS 300 402-6:1998 document contain?

The document contains a structured test suite description, a TP naming scheme, and a standard TP template. Table 1 defines how TP identifiers are built, and Table 2 shows the parts of a single TP, including stimulus, reaction, and message structure. Figure 1 lays out the test suite tree for layer management and data control.

It then lists many state-based test purposes for user and network roles, grouped by data link state and by valid, inopportune, syntactically invalid, timer, and counter cases. The clauses use concrete frame types and message names so that test cases can be derived directly from the protocol behavior.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SURWRNROIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 6: Test Suite Structure and Test Purposes (TSS&TP) specification for the general protocol35.100.20Podatkovni povezovalni slojData link layer33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 402-6 Edition 1SIST ETS 300 402-6:1998en01-junij-1998SIST ETS 300 402-6:1998SLOVENSKI
STANDARD
EUROPEANETS 300 402-6TELECOMMUNICATIONJanuary 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05087ICS:33.020Key words:ISDN, DSS1, layer 2, D-channel, LAPD, testing, TSS&TPIntegrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Data link layer;Part 6: Test Suite Structure and Test Purposes (TSS&TP)specification for the general protocolETSIEuropean 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 402-6:1998

Page 2ETS 300 402-6: January 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 402-6:1998

Page 3ETS 300 402-6: January 1997ContentsForeword.51Scope.72Normative references.73Definitions.73.1Definitions related to conformance testing.73.2Definitions related to ETS 300 402-2.84Abbreviations.85Test Suite Structure (TSS).96Test purposes (TP).116.1Introduction.116.1.1Test purpose naming convention.116.1.2Source of TP definition.116.1.3TP structure.126.1.4Test strategy.126.2TPs for DSS1 layer 2.136.2.1Layer Management.136.2.1.1User.136.2.1.1.1DL state 1.136.2.1.1.2DL state 3.156.2.1.1.3DL state 4.196.2.1.1.4DL state 5.0.236.2.1.1.5DL state 6.0.246.2.1.1.6DL state 7.0.266.2.1.1.7DL state 8.0.276.2.1.2Network.296.2.1.2.1DL state 1.296.2.1.2.2DL state 4.316.2.1.2.3DL state 5.0.356.2.1.2.4DL state 6.0.356.2.1.2.5DL state 7.0.366.2.1.2.6DL state 8.0.366.2.2Data control.376.2.2.1DL state 4.376.2.2.1.1Valid behaviour.376.2.2.1.2Inopportune behaviour.376.2.2.1.3Syntactically invalid.386.2.2.2DL state 5.0.396.2.2.2.1Valid behaviour.396.2.2.2.2Inopportune behaviour.396.2.2.2.3Syntactically invalid.406.2.2.2.4Timers.416.2.2.3DL state 5.1.416.2.2.3.1Valid behaviour.416.2.2.4DL state 6.0.416.2.2.4.1Valid behaviour.416.2.2.4.2Inopportune behaviour.426.2.2.4.3Syntactically invalid.436.2.2.4.4Timers.43SIST ETS 300 402-6:1998

Page 4ETS 300 402-6: January 19976.2.2.5DL state 7.0.436.2.2.5.1Valid behaviour.436.2.2.5.2Inopportune behaviour.456.2.2.5.3Syntactically invalid.476.2.2.6DL state 7.0 with outstanding I frames.486.2.2.6.1Valid behaviour.486.2.2.6.2Inopportune behaviour.496.2.2.6.3Timers.506.2.2.7DL state 7.1.516.2.2.7.1Valid behaviour.516.2.2.7.2Inopportune behaviour.516.2.2.8DL state 7.4.516.2.2.8.1Valid behaviour.516.2.2.8.2Inopportune behaviour.526.2.2.8.3Syntactically invalid.546.2.2.9DL state 7.4 with outstanding I frames.556.2.2.9.1Valid behaviour.556.2.2.9.2Inopportune behaviour.566.2.2.9.3Timers.566.2.2.10DL state 7.5.586.2.2.10.1Valid behaviour.586.2.2.10.2Inopportune behaviour.586.2.2.11DL state 8.0.586.2.2.11.1Valid behaviour.586.2.2.11.2Inopportune behaviour.596.2.2.11.3Syntactically invalid.616.2.2.12DL state 8.0 with outstanding I frames.626.2.2.12.1Valid behaviour.626.2.2.12.2Inopportune behaviour.626.2.2.12.3Timers.626.2.2.12.4Counters.626.2.2.13DL state 8.1.636.2.2.13.1Valid behaviour.636.2.2.13.2Inopportune behaviour.636.2.2.14DL state 8.4.636.2.2.14.1Valid behaviour.636.2.2.14.2Inopportune behaviour.636.2.2.14.3Syntactically invalid.666.2.2.15DL state 8.4 with outstanding I frames.666.2.2.15.1Valid behaviour.666.2.2.15.2Inopportune behaviour.676.2.2.15.3Timers.676.2.2.15.4Counters.676.2.2.16DL state 8.5.676.2.2.16.1Valid behaviour.676.2.2.16.2Inopportune behaviour.677Compliance.688Requirements for a comprehensive testing service.68History.69SIST ETS 300 402-6:1998

Page 5ETS 300 402-6: January 1997ForewordThis 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 6 of a multi-part standard covering the Integrated Services Digital Network (ISDN) DigitalSubscriber Signalling System No. one (DSS1) data link layer specification as described below:Part 1:"General aspects [ITU-T Recommendation Q.920 (1993), modified]";Part 2:"General protocol specification [ITU-T Recommendation Q.921 (1993), modified]";Part 3:"Frame relay protocol specification";Part 4:"Protocol Implementation Conformance Statement (PICS) proforma specification for thegeneral protocol";Part 5:"PICS proforma specification for the frame relay protocol";Part 6:"Test Suite Structure and Test Purposes (TSS&TP) specification for the generalprotocol";Part 7:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the general protocol".Transposition datesDate of adoption:20 December 1996Date of latest announcement of this ETS (doa):30 April 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 October 1997Date of withdrawal of any conflicting National Standard (dow):31 October 1997SIST ETS 300 402-6:1998

Page 6ETS 300 402-6: January 1997Blank pageSIST ETS 300 402-6:1998

Page 7ETS 300 402-6: January 19971ScopeThis sixth part of ETS 300 402 specifies the Test Suite Structure and Test Purposes (TSS&TP) at theT reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) ofimplementations conforming to the standard for the general data link layer protocol of Digital SubscriberSignalling System No. one (DSS1) for the pan-European Integrated Services Digital Network (ISDN),ETS 300 402-2 [1].A further part of this ETS specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on this ETS.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 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]".[2]ETS 300 402-4 (1996): "Integrated Services Digital Network (ISDN); DigitalSubscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 4:Protocol Implementation Conformance statement (PICS) proforma for thegeneral protocol".[3]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[4]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".[5]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[6]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[7]ITU-T Recommendation I.411 (1993): "ISDN user network interfaces - referenceconfigurations".3DefinitionsFor the purposes of this ETS, the following definitions apply, in addition to those given inETS 300 402-2 [1]:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].SIST ETS 300 402-6:1998

Page 8ETS 300 402-6: January 1997implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to ETS 300 402-2Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [6], definition 308.network: The DSS1 protocol entity at the Network side of the user-network interface where a T referencepoint or coincident S and T reference point applies.network (S/T): The DSS1 protocol entity at the Network side of the user-network interface where acoincident S and T reference point applies.network (T): The DSS1 protocol entity at the Network side of the user-network interface where aT reference point applies (user is the private ISDN).user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point orcoincident S and T reference point applies.user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincidentS and T reference point applies.user (T): The DSS1 protocol entity at the User side of the user-network interface where a T referencepoint applies (User is the private ISDN).4AbbreviationsFor the purposes of this ETS, the following abbreviations apply, in addition to those given inETS 300 402-2 [1]:ATMAbstract Test MethodATSAbstract Test SuiteDSS1Digital Subscriber Signalling System No. oneISDNIntegrated Services Digital NetworkIUTImplementation Under TestPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureSIST ETS 300 402-6:1998

Page 9ETS 300 402-6: January 19975Test Suite Structure (TSS)·
Layer management·
User·
DL state 1·
Valid behaviour·
Syntactically invalid·
DL state 3·
Valid behaviour·
Syntactically invalid·
Timers·
Counters·
DL state 4·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
Timers·
DL state 5.0·
Valid behaviour·
Inopportune behaviour·
Counters·
DL state 6.0·
Valid behaviour·
Inopportune behaviour·
Counters·
DL state 7.0·
Valid behaviour·
Inopportune behaviour·
DL state 8.0·
Valid behaviour·
Inopportune behaviour·
Network·
DL state 1·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
DL state 4·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
Timers·
DL state 5.0·
Inopportune behaviour·
Counters·
DL state 6.0·
Inopportune behaviour·
Counters·
DL state 7.0·
Inopportune behaviour·
DL state 8.0·
Inopportune behaviour·
Data control·
DL state 1·
Valid behaviour·
DL state 3·
Valid behaviour·
DL state 4·
Valid behaviour·
Inopportune behaviour·
Syntactically invalidFigure 1 (sheet 1 of 2): Test suite structureSIST ETS 300 402-6:1998

Page 10ETS 300 402-6: January 1997·
DL state 5.0·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
Timers·
DL state 5.1·
Valid behaviour·
DL state 6.0·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
Timers·
DL state 7.0·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
DL state 7.0 with outstanding I frames·
Valid behaviour·
Inopportune behaviour·
Timers·
DL state 7.1·
Valid behaviour·
Inopportune behaviour·
DL state 7.4·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
DL state 7.4 with outstanding I frames·
Valid behaviour·
Inopportune behaviour·
Timers·
DL state 7.5·
Valid behaviour·
Inopportune behaviour·
DL state 8.0·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
DL state 8.0 with outstanding I frames·
Valid behaviour·
Inopportune behaviour·
Timers·
Counters·
DL state 8.1·
Valid behaviour·
Inopportune behaviour·
DL state 8.4·
Valid behaviour·
Inopportune behaviour·
Syntactically invalid·
DL state 8.4 with outstanding I frames·
Valid behaviour·
Inopportune behaviour·
Timers·
Counters·
DL state 8.5·
Valid behaviour·
Inopportune behaviourFigure 1 (sheet 2 of 2): Test suite structureSIST ETS 300 402-6:1998

Page 11ETS 300 402-6: January 19976Test Purposes (TP)6.1IntroductionFor each test requirement, a TP is defined.6.1.1Test purpose naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS.Additional references are added to identify the actual test suite and whether it applies to the network or theuser (see table 1).Table 1: TP identifier naming convention schemeIdentifier:___=suiteL2 = layer 2=sideU = userN = networkC = combined (user and network)=procedure categoryLLayer managementDData control=data link entity statee.g.:70, 4, 81, etc.=groupone character representing group reference according to TSS:V:Valid stimulusI:Inopportune stimulusS:Syntactically stimulusT:timersC:counters=sequential number(1-99)6.1.2Source of TP definitionThe TPs are based on ETS 300 402-2 [1].SIST ETS 300 402-6:1998

Page 12ETS 300 402-6: January 19976.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is tomake the TPs more readable and checkable. A particular structure has been used which is illustrated intable 2. This table should be read in conjunction with any TP, i.e. please use a TP as an example tofacilitate the full comprehension of table 2.Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1 tabsubclause 5.3.1 [opt.]table D.1/2-1 (see note 2) or new TCTC11001 (see note 3)StimulusEnsure that the IUT in the

(see note 4) see below for message structurereceiving a XXXX frameor to request a .Reactiontransmits, does, etc.if the action is sending
see below for frame structure, etc.and enters stateand/or and remains in the same state(s)or and enters state Messagestructureframe containing aUI, I, SABME, etc.a) field with and back to a)TEI, C/R, INFO, P/F, N(R), etc.NOTE 1:Text in italics will not appear in TPs and text between <> is filled in for each TP and maydiffer from one TP to the next.NOTE 2:All references to state transition tables are to annex D of ITU Recommendation Q.921 asmodified by ETS 300 402-2 [1] (e.g. "Table D.1/2-3" refers to the state transition table D.1,sheet 2, line 3).NOTE 3:These references to I-ETS 300 313 helped in developing this ETS and are of a purelyinformative nature.NOTE 4:The DL entity state by the start of the test case is the one corresponding to the test group.(e.g. in group L70, all the test cases shall be executed from the state 7.0).6.1.4Test strategyAs the base standard ETS 300 402-2 [1] contains no explicit requirements for testing, the TPs weregenerated as a result of an analysis of the base standard and the PICS specification ETS 300 402-4 [2].The criteria applied include the following:-only the requirements from the point of view of the T or coincident S and T reference point areconsidered;-whether or not a test case can be built from the TP is not considered;-as a consequence of the test method used, all information units shall be expressed in term ofProtocol Data Units (PDUs). The use of primitives is considered to be not acceptable.SIST ETS 300 402-6:1998

Page 13ETS 300 402-6: January 19976.2TPs for DSS1 layer 2All PICS items referred to in this subclause are as specified in ETS 300 402-4 [2] unless indicatedotherwise by another numbered reference.6.2.1Layer ManagementSelection:IUT supports TEI management procedures. PICS: MCu 3.6.2.1.1UserSelection:IUT supports the user role. PICS: R 2.16.2.1.1.1DL state 16.2.1.1.1.1Valid behaviourL2U_L10_V_1subclause 5.3.2, table D.1/1-1TC11004Ensure that the IUT, in the state 1, having been requested to establish the data link,transmits an UI frame with an Identity request message and enters the state 3.Selection: IUT supports the automatic TEI assignment procedures. PICS: MCu 3.1.1.L2U_L10_V_2subclause 5.3.3.2TC11001Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity check requestmessage with Ai = 127,transmits no frame and remains in the same state.L2U_L10_V_3subclause 5.3.3.2TC11002Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity check requestmessage with Ai = automatic TEI value,transmits no frame and remains in the same state.NOTE 1:A random function can be used to generate the Ai value between 64 and 126.L2U_L10_V_4subclause 5.3.3.2TC11003Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity check requestmessage with Ai = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 2:A random function can be used to generate the Ai value between 0 and 63.L2U_L10_V_5subclause 5.3.4TC11005Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity remove message withAi = 127,transmits no frame and remains in the same state.L2U_L10_V_6subclause 5.3.4TC11006Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity remove message withAi = automatic TEI value,transmits no frame and remains in the same state.NOTE 3:A random function can be used to generate the Ai value between 64 and 126.L2U_L10_V_7subclause 5.3.4TC11007Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity remove message withAi = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 4:A random function can be used to generate the Ai value between 0 and 63.L2U_L10_V_8subclause 5.3.2TC11008Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity assigned message withAi = automatic TEI value,transmits no frame and remains in the same state.NOTE 5:A random function can be used to generate the Ai value between 64 and 126.SIST ETS 300 402-6:1998

Page 14ETS 300 402-6: January 1997L2U_L10_V_9subclause 5.3.2TC11010Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity denied message withAi = 127,transmits no frame and remains in the same state.L2U_L10_V_10subclause 5.3.2TC11011Ensure that the IUT, in the state 1, on receipt of an UI frame containing an Identity denied message withAi = automatic TEI value,transmits no frame and remains in the same state.NOTE 6:A random function can be used to generate the Ai value between 64 and 126.6.2.1.1.1.2Inopportune behaviourL2U_L10_I_1subclause 3.3TC11013Ensure that the IUT, in the state 1, on receipt of an UI frame with a TEI value ¹ 127, containing a layer 3message requesting a response,transmits no frame and remains in the same state.NOTE 1:A random function can be used to generate the Ai value between 64 and 126.L2U_L10_I_2subclause 3.3TC11014Ensure that the IUT, in the state 1, on receipt of a SABME frame with P = 1,transmits no frame and remains in the same state.NOTE 2:A random function can be used to generate the TEI value between 0 and 126.L2U_L10_I_3subclause 3.3TC11015Ensure that the IUT, in the state 1, on receipt of a DISC frame with P = 1,transmits no frame and remains in the same state.NOTE 3:A random function can be used to generate the TEI value between 0 and 126.L2U_L10_I_4subclause 3.3TC11016Ensure that the IUT, in the state 1, on receipt of a DM frame with F = 1,transmits no frame and remains in the same state.NOTE 4:A random function can be used to generate the TEI value between 0 and 126.L2U_L10_I_5subclause 3.3TC11017Ensure that the IUT, in the state 1, on receipt of an UA frame with F = 1,transmits no frame and remains in the same state.NOTE 5:A random function can be used to generate the TEI value between 0 and 126.L2U_L10_I_6subclause 3.3TC11018Ensure that the IUT, in the state 1, on receipt of a RR command frame with P = 1,transmits no frame and remains in the same state.NOTE 6:A random function can be used to generate the TEI value between 0 and 126.L2U_L10_I_7subclause 3.3TC11022Ensure that the IUT, in the state 1, on receipt of an I frame with P = 1, containing a layer 3 message,transmits no frame and remains in the same state.NOTE 7:A random function can be used to generate the TEI value between 0 and 126.6.2.1.1.1.3Syntactically invalid behaviourL2U_L10_S_1subclause 2.9 a)new TCEnsure that the IUT, in the state 1, on receipt of an UI frame containing a layer 3 message requesting aresponse, with a TEI value = 127, and without closing flag,transmits no frame and remains in the same state.L2U_L10_S_2subclause 2.9 b)new TCEnsure that the IUT, in the state 1, on receipt of a frame containing 4 octets between flags (without controlfield octet),transmits no frame and remains in the same state.SIST ETS 300 402-6:1998

Page 15ETS 300 402-6: January 1997L2U_L10_S_3subclause 2.9 b)new TCEnsure that the IUT, in the state 1, on receipt of a RR frame containing 5 octets between flags (without thesecond control field octet),transmits no frame and remains in the same state.L2U_L10_S_4subclause 2.9 c)new TCEnsure that the IUT, in the state 1, on receipt of an UI frame containing a layer 3 message requesting aresponse, with a TEI value = 127 and which does not consist of an integral number of octets,transmits no frame and remains in the same state.L2U_L10_S_5subclause 2.9 d)TC11026Ensure that the IUT, in the state 1, on receipt of an UI frame
containing a layer 3 message requesting aresponse, with a TEI value = 127 and with a FCS error,transmits no frame and remains in the same state.L2U_L10_S_6subclause 2.9 e)new TCEnsure that the IUT, in the state 1, on receipt of an UI frame with a single octet address field, , containinga layer 3 message requesting a response,transmits no frame and remains in the same state.L2U_L10_S_7subclause 2.9 f)new TCEnsure that the IUT, in the state 1, on receipt of an UI frame containing a layer 3 message requesting aresponse, with a SAPI value not supported and a TEI value = 127,transmits no frame and remains in the same state.L2U_L10_S_8subclause 3.3.2TC11027Ensure that the IUT, in the state 1, on receipt of an UI frame containing , a layer 3 message requesting aresponse, with a TEI value = 127 and with an erroneous C/R bit value,transmits no frame and remains in the same state.L2U_L10_S_9subclause 3.3.1TC11028Ensure that the IUT, in the state 1, on receipt of an UI frame containing a layer 3 message requesting aresponse, with a TEI value = 127 and with an erroneous EA bit value in the first address field octet,transmits no frame and remains in the same state.L2U_L10_S_10subclause 3.3.1TC11029Ensure that the IUT, in the state 1, on receipt of an UI frame containing a layer 3 message requesting aresponse, with a TEI value = 127 and with an erroneous EA bit value in the second address field octet,transmits no frame and remains in the same state.L2U_L10_S_11subclauses 3.6.1, 5.8.5TC11024Ensure that the IUT, in the state 1, on receipt of an undefined frame,transmits no frame and remains in the same state.L2U_L10_S_12subclauses 5.8.5, 5.9.3new TCEnsure that the IUT, in the state 1, on receipt of an UI frame with a TEI value = 127, containing a layer 3message requesting a response with a length exceeding N201,transmits no frame and remains in the same state.6.2.1.1.2DL state 3Selection:IUT supports the automatic TEI assignment procedures. PICS: MCu 3.1.1.6.2.1.1.2.1Valid behaviourL2U_L30_V_1subclause 5.3.2, table D.1/1-8TC13007Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withRi = own Ri value and Ai = automatic TEI value,transmits a SABME frame with P = 1 and enters the state 5.0.NOTE 1:A random function can be used to generate the Ai value between 64 and 126.SIST ETS 300 402-6:1998

Page 16ETS 300 402-6: January 1997L2U_L30_V_2subclause 5.3.2new TCEnsure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withRi = other Ri value and Ai = automatic TEI value,transmits no frame and remains in the same state.L2U_L30_V_3subclause 5.3.2, table D.1/1-10TC13008Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity denied message withRi = own Ri value and with Ai = 127,transmits no frame and enters the state 1.L2U_L30_V_4subclause 5.3.2new TCEnsure that the IUT, in the state 3, on receipt of an UI frame containing an Identity denied message withRi = other Ri value and with Ai = automatic TEI value,transmits no frame and remains in the same state.NOTE 2:A random function can be used to generate the Ai value between 64 and 126.L2U_L30_V_5subclause 5.3.3.2TC13001Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity check requestmessage with Ai = 127,transmits no frame and remains in the same state.L2U_L30_V_6subclause 5.3.3.2TC13002Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity check requestmessage with Ai = automatic TEI value,transmits no frame and remains in the same state.NOTE 3:A random function can be used to generate the Ai value between 64 and 126.L2U_L30_V_7subclause 5.3.3.2TC13003Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity check requestmessage with Ai = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 4:A random function can be used to generate the Ai value between 0 and 63.L2U_L30_V_8subclause 5.3.4TC13004Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity remove message withAi = 127,transmits no frame and remains in the same state.L2U_L30_V_9subclause 5.3.4TC13005Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity remove message withAi = automatic TEI value,transmits no frame and remains in the same state.NOTE 5:A random function can be used to generate the Ai value between 64 and 126.L2U_L30_V_10subclause 5.3.4TC13006Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity remove message withAi = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 6:A random function can be used to generate the Ai value between 0 and 63.6.2.1.1.1.2Inopportune behaviourL2U_L30_I_1subclause 3.3TC13011Ensure that the IUT, in the state 3, on receipt of an UI frame with a TEI value ¹ 127, containing a layer 3message requesting a response,transmits no frame and remains in the same state.NOTE 1:A random function can be used to generate the TEI value between 0 and 126.L2U_L30_I_2subclause 3.3TC13017Ensure that the IUT, in the state 3, on receipt of a SABME frame with P = 1,transmits no frame and remains in the same state.NOTE 2:A random function can be used to generate the TEI value between 0 and 126.SIST ETS 300 402-6:1998

Page 17ETS 300 402-6: January 1997L2U_L30_I_3subclause 3.3TC13018Ensure that the IUT, in the state 3, on receipt of a DISC frame with P = 1,transmits no frame and remains in the same state.NOTE 3:A random function can be used to generate the TEI value between 0 and 126.L2U_L30_I_4subclause 3.3TC13019Ensure that the IUT, in the state 3, on receipt of a DM frame with F = 1,transmits no frame and remains in the same state.NOTE 4:A random function can be used to generate the TEI value between 0 and 126.L2U_L30_I_5subclause 3.3TC13020Ensure that the IUT, in the state 3, on receipt of an UA frame with F = 1,transmits no frame and remains in the same state.NOTE 5:A random function can be used to generate the TEI value between 0 and 126.L2U_L30_I_6subclause 3.3TC13021Ensure that the IUT, in the state 3, on receipt of a RR command frame with P = 1,transmits no frame and remains in the same state.NOTE 6:A random function can be used to generate the TEI value between 0 and 126.L2U_L30_I_7subclause 3.3TC13025Ensure that the IUT, in the state 3, on receipt of an I frame with P = 1, containing a layer 3 message,transmits no frame and remains in the same state.NOTE 7:A random function can be used to generate the TEI value between 0 and 126.6.2.1.1.2.3Syntactically invalid behaviourL2U_L30_S_1subclause 5.3.2new TCEnsure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withRi = own Ri value and Ai = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 1:A non-automatic TEI value is not allowed in the Ai field of an Identity assignedmessage.L2U_L30_S_2subclause 5.3.2new TCEnsure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withRi = own Ri value and Ai = 127,transmits no frame and remains in the same state.NOTE 2:127 is not allowed in the Ai field of an Identity assigned message.L2U_L30_S_3subclause 5.3.2new TCEnsure that the IUT, in the state 3, on receipt of an UI frame containing an Identity denied message withRi = own Ri value and Ai = non-automatic TEI value,transmits no frame and remains in the same state.NOTE 3:A non-automatic TEI value is not allowed in the Ai field of an Identity denied message.L2U_L30_S_4subclause 2.9 a)new TCEnsure that the IUT, in the state 3, on receipt of
an UI frame, containing an Identity assigned messagewith Ai = automatic TEI value, without closing flag,transmits no frame and remains in the same state.L2U_L30_S_5subclause 2.9 b)new TCEnsure that the IUT, in the state 3, on receipt of a frame containing 4 octets between flags (without controlfield octet),transmits no frame and remains in the same state.L2U_L30_S_6subclause 2.9 b)new TCEnsure that the IUT, in the state 3, on receipt of a RR frame containing 5 octets between flags (without thesecond control field octet),transmits no frame and remains in the same state.SIST ETS 300 402-6:1998

Page 18ETS 300 402-6: January 1997L2U_L30_S_7subclause 2.9 c)new TCEnsure that the IUT, in the state 3, on receipt of an UI frame, containing an Identity assigned messagewith Ai = automatic TEI value, which does not consist of an integral number of octets,transmits no frame and remains in the same state.L2U_L30_S_8subclause 2.9 d)TC13029Ensure that the IUT, in the state 3, on receipt of an UI frame, containing an Identity assigned messagewith Ai = automatic TEI value, with a FCS error,transmits no frame and remains in the same state.L2U_L30_S_9subclause 2.9 e)new TCEnsure that the IUT, in the state 3, on receipt of an UI frame with a single octet address field, containingan Identity assigned message with Ai = automatic TEI value,transmits no frame and remains in the same state.L2U_L30_S_10subclause 2.9 f)new TCEnsure that the IUT, in the state 3, on receipt of an UI frame, containing an Identity assigned messagewith Ai = automatic TEI value, with a SAPI not supported,transmits no frame and remains in the same state.L2U_L30_S_11subclause 3.3.2TC13033Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withAi = automatic TEI value with an erroneous C/R bit value,transmits no frame and remains in the same state.L2U_L30_S_12subclause 3.3.1TC13034Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withAi = automatic TEI value with an erroneous EA bit value in the first address field octet,transmits no frame and remains in the same state.L2U_L30_S_13subclause 3.3.1TC13035Ensure that the IUT, in the state 3, on receipt of an UI frame containing an Identity assigned message withAi = automatic TEI value with an erroneous EA bit value in the second address field octet,transmits no frame and remains in the same state.L2U_L30_S_14subclauses 3.6.1, 5.8.5new TCEnsure that the IUT, in the state 3, on receipt of an undefined frame,transmits no frame and remains in the same state.L2U_L30_S_15subclauses 5.8.5, 5.9.3new TCEnsure that the IUT, in the state 3, on receipt of an UI frame with a TEI value = 127, containing aninformation field with a length exceeding N201,transmits no frame and remains in the same state.6.2.1.1.2.3TimersL2U_L30_T_1subclause 5.3.2.1new TCEnsure that the IUT, in the state 3, on expiry of the timer T202,transmits an UI frame with an Identity request message with a new Ri value and remains in thesame state.6.2.1.1.2.4CountersL2U_L30_C_1subclause 5.3.2.1new TCEnsure that the IUT, in the state 3, having transmitted N202 time an UI frame with an Identity requestmessage, on expiry of the timer T202,transmits no frame and enters the state 1.SIST ETS 300 402-6:1998

Page 19ETS 300 402-6: January 19976.2.1.1.3DL state 46.2.1.1.3.1Valid behaviourL2U_L40_V_1subclause 5.3.2TC14015Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity assigned message withAi = other automatic TEI value,transmits no frame and remains in the same state.L2U_L40_V_2subclause 5.3.2TC14016Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity denied message withAi = 127,transmits no frame and remains in the same state.L2U_L40_V_3subclause 5.3.2TC14018Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity denied message withAi = other automatic TEI value,transmits no frame and remains in the same state.L2U_L40_V_4subclause 5.3.3.1TC14001Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity check requestmessage with Ai = 127,transmits an UI frame containing an Identity check response message with Ai = own TEI value andremains in the same state.L2U_L40_V_5subclause 5.3.3.2TC14002Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity check requestmessage with Ai = own TEI value,transmits an UI frame containing an Identity check response message with Ai = own TEI value andremains in the same state.L2U_L40_V_6subclause 5.3.3.2TC14003Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity check requestmessage with Ai = other TEI value,transmits no frame and remains in the same state.L2U_L40_V_7subclause 5.3.4TC14004Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity remove message withAi = 127,transmits an UI frame containing an Identity request message and enters the state 1.Selection:IUT supports the automatic TEI assignment procedures. MCu 3.1.1.L2U_L40_V_8subclause 5.3.4TC14004Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity remove message withAi = 127,transmits no frame and enters the state 1.Selection:IUT supports the non-automatic TEI assignment procedures. PICS: MCu 3.1.2.L2U_L40_V_9subclause 5.3.4TC14005Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity remove message withAi = own TEI value,transmits an UI frame containing an Identity request message and enters the state 1.Selection:IUT supports the automatic TEI assignment procedures. PICS: MCu 3.1.1.L2U_L40_V_10subclause 5.3.4TC14005Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity remove message withAi = own TEI value,transmits no frame and enters the state 1.Selection:IUT supports the non-automatic TEI assignment procedures. PICS: MCu 3.1.2.SIST ETS 300 402-6:1998

Page 20ETS 300 402-6: January 1997L2U_L40_V_11subclause 5.3.4TC14010Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity remove message withAi = other TEI value,transmits no frame and remains in the same state.6.2.1.1.3.2Inopportune behaviourL2U_L40_I_1subclauses 5.3.2, 5.3.4TC14011, TC14014Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity assigned message withAi = own TEI value,transmits an UI frame containing an Identity request message and enters the state 1;ortransmits an UI frame containing an Identity verify message with own TEI value and remains in thesame state.Selection:SCu 1.2 AND MCu 3.1.1.NOTE 1:The Identity assigned message will provoke a TEI removal procedure (duplicate TEIvalue assignment).L2U_L40_I_2subclauses 5.3.4, 5.5.4, 5.8.8, table II.1, table D.1/2-7TC24007Ensure that the IUT, in the state 4, on receipt of an unsolicited UA frame with F = 1 (MDL error C),transmits an UI frame containing an Identity request message and enters the state 1;ortransmits an UI frame containing an Identity verify message with own TEI value and remains in thesame state.Selection:IUT supports the automatic TEI assignment procedures. PICS: MCu 3.1.1.NOTE 2:The unsolicited UA frame will provoke a TEI removal procedure (duplicate TEI valueassignment).`L2U_L40_I_3subclauses 5.3.4, 5.5.4, 5.8.8, table II.1, table D.1/2-7TC24007Ensure that the IUT, in the state 4, on receipt of an unsolicited UA frame with F = 1 (MDL error C),transmits no frame and enters the state 1;ortransmits an UI frame containing an Identity verify message with own TEI value and remains in thesame state.Selection:IUT supports the non-automatic TEI assignment procedures. PICS: MCu 3.1.2.NOTE 3:The unsolicited UA frame will provoke a TEI removal procedure (duplicate TEI valueassignment).L2U_L40_I_4subclauses 5.3.4, 5.5.4, 5.8.8, table II.1, table D.1/2-9TC24008Ensure that the IUT, in the state 4, on receipt of an unsolicited UA frame with F = 0 (MDL error D),transmits an UI frame containing an Identity request message and enters the state 1;ortransmits an UI frame containing an Identity verify message with own TEI value and remains in thesame state.Selection:IUT supports the automatic TEI assignment procedures. PICS: MCu 3.1.1.NOTE 4:The unsolicited UA frame will provoke a TEI removal procedure (duplicate TEI valueassignment).L2U_L40_I_5subclauses 5.3.4, 5.5.4, 5.8.8, table II.1, table D.1/2-9TC24008Ensure that the IUT, in the state 4, on receipt of an unsolicited UA frame with F = 0 (MDL error D),transmits no frame and enters the state 1;ortransmits an UI frame containing an Identity verify message with own TEI value and remains in thesame state.Selection:IUT supports the non-automatic TEI assignment procedures. PICS: MCu 3.1.2.NOTE 5:The unsolicited UA frame will provoke a TEI removal procedure (duplicate TEI valueassignment).L2U_L40_I_6subclause 5.3.2TC14017Ensure that the IUT, in the state 4, on receipt of an UI frame containing an Identity denied message withAi = own TEI value,transmits no frame and remains in the same state.SIST ETS 300 402-6:1998

Page 21ETS 300 402-6: January 1997L2U_L40_I_7subclause 3.3.4TC14025Ensure that the IUT, in the state 4, on receipt of an UI frame, with a TEI value not currently assigned,containing a layer 3 message requesting a response,transmi
...