SIST ETS 300 324-7:1997

Signalling 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 layer

Abstract Test Suite specification (ATS in TTCN) and protocol implementation extra information for testing (PIXIT) proforma V5.1 interface for support of Access Network; 2048 kBit/s interface without concentration capability within the Access Network

Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih centralah (LE) - Vmesnik V5.1 za podporo dostopovnega omrežja (AN) - 7. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) za podatkovno povezovalno plast

General Information

• Status: Published
• Publication Date: 31-Oct-1997
• ICS: 33.040.30 - Switching and signalling systems
• 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-Nov-1997
• Due Date: 01-Nov-1997
• Completion Date: 01-Nov-1997
• Ref Project: ETSI ETS 300 324-7 ed.1 (1995-10) - 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)

SLOVENSKI STANDARD
SIST ETS 300 324-7:1997
01-november-1997
Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih
centralah (LE) - Vmesnik V5.1 za podporo dostopovnega omrežja (AN) - 7. del:
Zgradba preskušalnega niza in namen preskušanja (TSS&TP) za podatkovno
povezovalno plast
Signalling 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 layer
Ta slovenski standard je istoveten z: ETS 300 324-7 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
35.100.20 Podatkovni povezovalni sloj Data link layer
SIST ETS 300 324-7:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 324-7:1997

---------------------- Page: 2 ----------------------

SIST ETS 300 324-7:1997
EUROPEAN ETS 300 324-7
TELECOMMUNICATION October 1995
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03003.3-3
ICS: 33.020, 33.080, 33.100.20
V interface, V5 interface, PSTN, ISDN, LE, AN, TSS&TP, testing, layer 2
Key words:
Signalling 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 layer
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1995. All rights reserved.
New presentation - see History box

---------------------- Page: 3 ----------------------

SIST ETS 300 324-7:1997
Page 2
ETS 300 324-7: October 1995
Whilst 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.

---------------------- Page: 4 ----------------------

SIST ETS 300 324-7:1997
Page 3
ETS 300 324-7: October 1995
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 Test Suite Structure (TSS) .9
4.1 TSS overview.9
4.2 Test groups.9
4.2.1 Protocol groups .9
4.2.1.1 Link Access Protocol for V5 interface - Envelope Function
sublayer (LAPV5-EF).9
4.2.1.2 Link Access Protocol for V5 interface - Data Link sublayer
(LAPV5-DL) .9
4.2.2 Main test groups.9
4.2.2.1 Basic Interconnection (IT) tests.9
4.2.2.2 Capability (CA) tests .10
4.2.2.3 Valid Behaviour (BV) tests.10
4.2.2.4 Inopportune Behaviour (BO) tests .10
4.2.2.5 Invalid Behaviour (BI) tests.10
4.2.2.6 Timer (TI).10
4.3 Test step structure.10
4.3.1 State transitions.10
4.3.1.1 V5 interface start-up .10
4.3.1.2 LAPV5-DL state transitions.11
4.3.2 Preambles .12
4.3.3 Postambles.12
4.3.4 Status verification .12
4.3.5 Common test steps .12
4.4 Defaults.12
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs).13
4.5.1 ASPs .13
4.5.2 PDUs .13
4.6 Timers and counters of the Abstract Test Suite (ATS).13
5 Test Purposes (TP).14
5.1 Introduction .14
5.1.1 TP naming convention.14
5.1.2 Source of TP definition.14
5.1.3 Test strategy.15
5.1.4 Procedures for which no TPs are defined .15
5.1.5 Initial state .15
5.1.6 Data configuration for AN and LE testing.15
5.2 LAPV5-EF.16
5.2.1 Basic interconnection tests.16
5.2.2 Valid behaviour tests .16
5.2.3 Invalid behaviour tests.16
5.3 LAPV5-DL.17
5.3.1 Basic interconnection tests.17
5.3.2 Capability tests .17
5.3.3 Valid behaviour.17
5.3.3.1 State 9: link not established.17
5.3.3.2 State 5: awaiting establishment.17

---------------------- Page: 5 ----------------------

SIST ETS 300 324-7:1997
Page 4
ETS 300 324-7: October 1995
5.3.3.2.1 State 5.0: establish. 17
5.3.3.2.2 State 5.1: re-establish . 18
5.3.3.3 State 7: multiple frame established. 19
5.3.3.3.1 State 7.0: TX: normal, RX: normal . 19
5.3.3.3.2 State 7.1: TX: normal, RX: REJ
recovery. 19
5.3.3.3.3 State 7.4: TX: peer rec busy, RX:
normal . 20
5.3.3.3.4 State 7.5: TX: peer rec busy, RX: REJ
recovery. 20
5.3.3.4 State 8: timer recovery. 20
5.3.3.4.1 State 8.0: TX: normal, RX: normal . 20
5.3.3.4.2 State 8.1: TX: normal, RX: REJ
recovery. 21
5.3.3.4.3 State 8.4: TX: peer rec busy, RX:
normal . 21
5.3.3.4.4 State 8.5: TX: peer rec busy, RX: REJ
recovery. 22
5.3.4 Inopportune behaviour. 22
5.3.4.1 State 7: multiple frame established. 22
5.3.4.1.1 State 7.0: TX: normal, RX: normal . 22
5.3.4.1.2 State 7.1: TX: normal, RX: REJ
recovery. 22
5.3.4.1.3 State 7.4: TX: peer rec busy, RX:
normal . 22
5.3.4.2 State 8: timer recovery. 22
5.3.4.2.1 State 8.0: TX: normal, RX: normal . 22
5.3.5 Invalid behaviour. 23
5.3.5.1 State 7: multiple frame established. 23
5.3.5.1.1 State 7.0: TX: normal, RX: normal . 23
5.3.5.1.2 State 7.1: TX: normal, RX: REJ
recovery. 24
5.3.5.1.3 State 7.4: TX: peer rec busy, RX:
normal . 24
5.3.5.2 State 8: timer recovery. 24
5.3.5.2.1 State 8.0: TX: normal, RX: normal . 24
5.3.5.2.2 State 8.1: TX: normal, RX: REJ
recovery. 25
5.3.5.2.3 State 8.4: TX: peer rec busy, RX:
normal . 25
5.3.6 Timer. 25
5.3.6.1 State 5: awaiting establishment . 25
5.3.6.1.1 State 5.0: establish. 25
5.3.6.1.2 State 5.1: re-establish . 25
5.3.6.2 State 7: multiple frame established. 25
5.3.6.2.1 State 7.0: TX: normal, RX: normal . 25
5.3.6.2.2 State 7.4: TX: peer rec. busy, RX:
normal . 26
5.3.6.3 State 8: timer recovery. 26
5.3.6.3.1 State 8.0: TX: normal, RX: normal . 26
5.3.6.3.2 State 8.4: TX: peer rec. busy, RX:
normal . 26
Annex A (informative): Bibliography . 27
History. 28

---------------------- Page: 6 ----------------------

SIST ETS 300 324-7:1997
Page 5
ETS 300 324-7: October 1995
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (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 (AN
side)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the network layer (AN side)";
Part 5: "TSS&TP specification for the network layer (LE side)";
Part 6: "ATS and partial PIXIT proforma specification for the network layer (LE side)";
Part 7: "TSS&TP specification for the data link layer";
Part 8: "ATS and partial PIXIT proforma specification for the data link layer";
Part 9: "Test specification for the physical layer".
Transposition dates
Date of adoption of this ETS: 27 October 1995
Date of latest announcement of this ETS (doa): 31 January 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1996
Date of withdrawal of any conflicting National Standard (dow): 31 July 1996

---------------------- Page: 7 ----------------------

SIST ETS 300 324-7:1997
Page 6
ETS 300 324-7: October 1995
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 324-7:1997
Page 7
ETS 300 324-7: October 1995
1 Scope
This seventh part of ETS 300 324 contains the Test Suite Structure (TSS) and Test Purposes (TPs) for
the 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 an
Access Network (AN) and a Local Exchange (LE) infrastructure. This ETS covers only the procedures
described 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 mapping
function (refer to ETS 300 324-1 [1], figure 6 which illustrates this approach). Regarding the conformance
testing these sublayer functions are not tested separately. The test purposes defined in clause 5 cover
testing of the LAPV5-DL (control protocol only), LAPV5-EF and the mapping function. The AN frame relay
function 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 Switched
Telephone Network (PSTN) DL implementation is identical with the Control DL implementation. This
needs to be declared by the Implementation Under Test (IUT) supplier. Otherwise, the TPs defined for the
Control DL may be used for the PSTN DL as well.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 324-1 (1994): "Signalling Protocols and Switching (SPS), V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 1: V5.1 interface specification".
[2] ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS), V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS)
proforma".
[3] ETS 300 125 (1991): "Integrated Services Digital Network (ISDN); User-network
interface data link layer specification; Application of CCITT Recommendations
Q.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".

---------------------- Page: 9 ----------------------

SIST ETS 300 324-7:1997
Page 8
ETS 300 324-7: October 1995
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, together with those given in
ETS 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 the
functions 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.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability
DLL Data Link Layer
EFaddr Envelope Function address
FCS Frame Check Sequence
FSM Finite State Machine
ID Identifier
ISDN Integrated Services Digital Network
IT Basic Interconnection
IUT Implementation Under Test
LAPD Link Access Protocol for the ISDN D-channel
LAPV5 Link Access Protocol for V5 interface
LAPV5-DL LAPV5 Data Link sublayer
LAPV5-EF LAPV5 Envelope Function sublayer
LE Local Exchange
LT Lower Tester
NWK Network Layer
PCO Point of Control and Observation

---------------------- Page: 10 ----------------------

SIST ETS 300 324-7:1997
Page 9
ETS 300 324-7: October 1995
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PSTN Public Switched Telephone Network
RX Receiver condition
SAPI Service Access Point Identifier
SUT System Under Test
TEI Terminal Endpoint Identifier
TI Timer
TP Test Purpose
TSS Test Suite Structure
TX Transmitter condition
UT Upper Tester
4 Test Suite Structure (TSS)
4.1 TSS overview
Figure 1 shows the structure of the V5.1 DLL test suite.
V5DLL LAPV5_EF IT
BV
BI
LAPV5_DL IT
CA
BV STATE
BO STATE
BI STATE
STATE
TI
Figure 1: DLL TSS
4.2 Test groups
4.2.1 Protocol groups
4.2.1.1 Link 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 AN
relay function (see ETS 300 324-1 [1], figure 6).
4.2.1.2 Link Access Protocol for V5 interface - Data Link sublayer (LAPV5-DL)
The defined test purposes cover the LAPV5-DL (control protocol only) procedures (see
ETS 300 324-1 [1], figure 6).
4.2.2 Main test groups
4.2.2.1 Basic Interconnection (IT) tests
The IT test subgroup contains a basic set of test purposes which assures that there is a sufficient
conformance for inter connection and that the chosen parameters are valid for the configuration.

---------------------- Page: 11 ----------------------

SIST ETS 300 324-7:1997
Page 10
ETS 300 324-7: October 1995
4.2.2.2 Capability (CA) tests
Capability testing provides a limited testing to ascertain the main capabilities stated in the Protocol
Implementation Conformance Statements (PICSs) can be observed.
4.2.2.3 Valid Behaviour (BV) tests
A valid test is a test where the message sequence and the message content is considered as valid (no
MDL_ERR_IND is caused in the Finite State Machine (FSM) of the DLL entity).
4.2.2.4 Inopportune Behaviour (BO) tests
This test subgroup is intended to verify that the IUT is able to react properly, in case an inopportune
protocol event occurs. Such an event is syntactically correct but it occurs when it is not expected (a
MDL_ERR_IND is caused in the FSM of the DLL entity).
4.2.2.5 Invalid Behaviour (BI) tests
This test subgroup is intended to verify that the IUT is able to react properly having received an invalid
Protocol Data Unit (PDU). Invalid PDU here means a syntactically invalid PDU and, therefore, a
MDL_ERR_IND might be caused in the FSM of the DLL entity.
4.2.2.6 Timer (TI)
The TI test group contains tests related to the system timers T200 and T203.
4.3 Test step structure
General dynamic behaviours should be described in test steps. The main test steps to apply the TPs
described in this document are described in this subclause.
4.3.1 State transitions
Two 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 the
LAPV5-DL implementation used in different preambles.
4.3.1.1 V5 interface start-up
The start-up procedure of a V5.1 IUT (AN or LE) depends on the configuration which is provisioned (refer
to 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 the
IUT.
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.

---------------------- Page: 12 ----------------------

SIST ETS 300 324-7:1997
Page 11
ETS 300 324-7: October 1995
Figure 2 describes the start-up procedure.
TSPC_ISDNBA
TSPC_PSTN TSPC_ISDNBA
TSPC_PSTN
IU T LT1 IU T LT1
IU T LT1
Control-DL
Control-DL Control-DL
SABM E
SABM E SABM E
UA
UA UA
Control-DL Control-DL
Control-DL
Variant and Interface ID req Variant and Interface ID req
Variant and Interface ID req
Variant and Interface ID Variant and Interface ID
Variant and Interface ID
PSTN-DL PSTN-DL
SABM E SABM E
UA UA (note)
Control-DL
Control-DL
restart req
restart req
restart complete restart complete
restart complete (note)
restart complete
NOTE: Only valid if TSPC_PSTN is set.
Figure 2: Start-up
4.3.1.2 LAPV5-DL state transitions
The 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.

---------------------- Page: 13 ----------------------

SIST ETS 300 324-7:1997
Page 12
ETS 300 324-7: October 1995
LAPV5_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.2 Preambles
The preamble test group contains the preamble test steps needed for initialization of the IUT before
testing the particular test purpose. The preambles are based on the state transition described in
subclause 4.3.1.
4.3.3 Postambles
After each test, the IUT is brought back to the initial state.
4.3.4 Status verification
Based 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 frame
established). States 7.2, 7.3, 7.6 and 7.7 are not distinguished as it is not possible to bring the IUT into
this state (except under load condition).
CHECK_STATE_70
The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5
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 to
state 7.1.
CHECK_STATE_71
The timer T_NOAC (3 s) is started, if no events occur during time T_NOAC the IUT is not in state 7.4, 7.5
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 to
state 7.0.
CHECK_STATE_74
No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) ⇒ the IUT is not
in 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 to
state 7.5.
CHECK_STATE_75
No action is taken from the tester, the IUT shall send N200 times a RR command (P=1) ⇒ the IUT is not
in 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 to
state 7.4.
4.3.5 Common test steps
This test step group contains test steps which describe procedures which are used in more than one test
case, e.g. receive procedures of common acknowledgement messages.
4.4 Defaults
The default section describes the behaviour in case of an unexpected test event.

---------------------- Page: 14 ----------------------

SIST ETS 300 324-7:1997
Page 13
ETS 300 324-7: October 1995
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)
4.5.1 ASPs
Two 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 of
DLL testing, only the Envelope Function address (EFaddr) and the Frame Check Sequence (FCS) are
relevant.
The value of the flag sequence and the FCS are usually supplied by the V5.1 tester, but for testing of the
LAPV5-EF functions it is necessary to corrupt the FCS value.
4.5.2 PDUs
The 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_cmd SABME-command;
ua_rsp UA-response;
dm_rsp DM-response;
rr_cmd RR-command;
rr_rsp RR-response;
rnr_cmd RNR-command;
rnr_rsp RNR-response;
rej_cmd REJ-command;
rej_rsp REJ-response;
i_cmd I-command.
2) PDUs sent to an ISDN-BA terminal via an ISDN-BA user port:
refer to ETS 300 125 [3], table 5.
4.6 Timers and counters of the Abstract Test Suite (ATS)
This subclause describes the timer and counters which shall be applied when implementing the TPs in a
ATS. The min and max indications define that the timer value represents the minimum or maximum
tolerance of a timer. The timer values contain some additional tolerances for delays caused by testers.
Table 1: ATS timers
ATS timer name ATS timer value ETS timer name Reference to
[s] ETS 300 324-1 [1]
T200_min 0,5 T200 subclause 10.4.9
T200_max 1,5
T203_min 1 T203 subclause 10.4.9
T203_max 11
TC2_max TSPX_TC2_max TC2 table C.1
TR2_max 132 TR2 table C.1
T_AC_short 1 Watch dog timer if an immediate ACtion is
expected from the IUT.
T_AC_long 60 Watch dog timer if an ACtion from the IUT
is expected after an undefined time period.
T_NOAC 3 Guard timer if NO ACtion shall appear.

---------------------- Page: 15 ----------------------

SIST ETS 300 324-7:1997
Page 14
ETS 300 324-7: October 1995
Table 2: ATS counters
ATS counter ATS counter Comments Reference to
name value ETS 300 324-1 [1]
N200 3 Corresponding counter variable: RC subclause 10.4.9
N201 260 Maximum number of octets in an information subclause 10.4.9
field
5 Test Purposes (TP)
5.1 Introduction
Clause 5 contains the TPs for V5.1 DLL testing. This subclause describes the test strategy of the TPs, the
test environment for which the TPs apply and the V5.1 procedures for which no TPs are defined.
5.1.1 TP naming convention
The identifier of the TP is constructed according to the scheme in table 3.
Table 3: TP identifier naming convention scheme
Identifier: TP
= type of protocol: 1 LAPV5-EF
(test group) 2 LAPV5-DL
= category: 1 IT, Basic Interconnection Tests
(test subgroup) 2 CA, Capability Tests
3 BV, Valid Behaviour Tests
4 BO, Inopportune Behaviour Tests
5 BI, Invalid Behaviour Tests
6 TI, Timer
test purpose type S Single TP (not combined TP)
= state (0-9)
_ (underscore) not relevant
= substate (0-9)
_ (underscore) not relevant
= sequential number (00-99)
5.1.2 Source of TP definit
...