SIST ETS 300 324-5 E2:2003

SLOVENSKI STANDARD
01-december-2003
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 5. del: Zgradba preskušalnega niza in nameni
preskušanja (TSS&TP) – Specifikacija za omrežno plast na strani krajevne centrale
(LE)
V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for
the network layer (LE side)
Ta slovenski standard je istoveten z: ETS 300 324-5 Edition 2
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 324-5
TELECOMMUNICATION April 1999
STANDARD Second Edition
Source: SPS Reference: RE/SPS-09055-5
ICS: 33.020
Key words: V interface, V5 interface, PSTN, ISDN, LE, TSS&TP, testing, layer 3, AN
V interfaces at the digital Local Exchange (LE);
V5.1 interface for the support of Access Network (AN);
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network layer (LE side)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1999. All rights reserved.

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

Page 3
ETS 300 324-5: April 1999
Contents
Foreword . 7
1 Scope. 9
2 Normative references . 9
3 Definitions and abbreviations. 10
3.1 Definitions. 10
3.2 Abbreviations. 11
4 Test Suite Structure (TSS). 12
4.1 TSS overview . 12
4.2 Test groups . 13
4.2.1 Protocol groups. 13
4.2.1.1 Control protocol. 13
4.2.1.2 PSTN protocol. 14
4.2.2 Main test groups . 14
4.2.2.1 Basic Interconnection (IT) tests. 14
4.2.2.2 Capability (CA) tests. 14
4.2.2.3 Valid Behaviour (BV) tests . 14
4.2.2.4 Inopportune Behaviour (BO) tests. 14
4.2.2.5 Invalid Behaviour (BI) tests . 14
4.2.2.6 Timer (TI) expiry and counter mismatch tests. 14
4.2.2.6.1 Timer expiry and counters of the
Control protocol . 15
4.2.2.6.2 Timer expiry and counters of the
PSTN protocol . 15
4.2.2.6.3 Timer expiry and counters of the LE
system management. 15
4.3 Test step structure. 15
4.3.1 State transitions . 15
4.3.1.1 Startup of V5.1 interface . 16
4.3.1.2 Common control Protocol (system management). 17
4.3.1.3 Control protocol (PSTN port FSM) . 17
4.3.1.4 Control protocol (ISDN-BA port FSM) . 17
4.3.1.5 PSTN protocol. 17
4.3.2 Preambles. 18
4.3.3 Postambles . 18
4.3.4 Status verification. 18
4.3.4.1 PSTN protocol. 18
4.3.4.2 Port control protocol . 19
4.3.4.3 Common control protocol. 19
4.3.5 Common test steps. 19
4.4 Defaults . 20
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs) . 20
4.5.1 ASPs . 20
4.5.2 PDUs. 20
4.5.2.1 Common control protocol. 20
4.5.2.2 Port control protocol . 20
4.5.2.3 PSTN protocol. 20
4.5.3 Information elements . 20
4.5.3.1 Variable length information elements. 20
4.5.3.1.1 Control protocol . 20
4.5.3.1.2 PSTN protocol . 20
4.5.3.2 Single octet information elements. 21
4.5.3.2.1 Control protocol . 21
4.5.3.2.2 PSTN protocol . 21

Page 4
ETS 300 324-5: April 1999
4.6 Timers and counters of the Abstract Test Suite (ATS).21
5 Test Purposes (TPs) .22
5.1 Introduction .22
5.1.1 TP naming convention.22
5.1.2 Source of TP definition.23
5.1.3 Test strategy.23
5.1.4 Requirements not covered by TPs.23
5.1.5 Initial state .24
5.1.6 Test and data configuration requirements.24
5.2 Control protocol.24
5.2.1 Basic interconnection tests (V5NWKLE/CTRL/IT).24
5.2.2 Capability tests (V5NWKLE/CTRL/CA).24
5.2.3 Valid behaviour tests (V5NWKLE/CTRL/BV).25
5.2.3.1 V5NWKLE/CTRL/BV/COM.25
5.2.3.1.1 V5NWKLE/CTRL/BV/COM/TRANS.25
5.2.3.1.2 V5NWKLE/CTRL/BV/COM/REST .25
5.2.3.1.3 V5NWKLE/CTRL/BV/COM/REVY .26
5.2.3.2 V5NWKLE/CTRL/BV/PORT .28
5.2.3.2.1 V5NWKLE/CTRL/BV/PORT/TRANS.28
5.2.3.2.2 V5NWKLE/CTRL/BV/PORT/PSTN.29
5.2.3.2.3 V5NWKLE/CTRL/BV/PORT/ISDNBA.31
5.2.4 Inopportune behaviour tests (V5NWKLE/CTRL/BO) .36
5.2.4.1 V5NWKLE/CTRL/BO/COM .36
5.2.4.1.1 V5NWKLE/CTRL/BO/COM/TRANS .36
5.2.4.1.2 V5NWKLE/CTRL/BO/COM/REVY.36
5.2.4.2 V5NWKLE/CTRL/BO/PORT.36
5.2.4.2.1 V5NWKLE/CTRL/BO/PORT/TRANS.36
5.2.4.2.2 V5NWKLE/CTRL/BO/PORT/ISDNBA .36
5.2.5 Invalid behaviour tests (V5NWKLE/CTRL/BI).38
5.2.5.1 V5NWKLE/CTRL/BI/COM .38
5.2.5.1.1 V5NWKLE/CTRL/BI/COM/TRANS.38
5.2.5.2 V5NWKLE/CTRL/BI/PORT .39
5.2.5.2.1 V5NWKLE/CTRL/BI/PORT/TRANS .39
5.2.6 Timer expiry and counter mismatch tests (V5NWKLE/CTRL/TI).40
5.2.6.1 V5NWKLE/CTRL/TI/COM .40
5.2.6.1.1 V5NWKLE/CTRL/TI/COM/TRANS .40
5.2.6.2 V5NWKLE/CTRL/TI/PORT.40
5.2.6.2.1 V5NWKLE/CTRL/TI/PORT/TRANS .40
5.3 PSTN Protocol .41
5.3.1 Basic interconnection tests (V5NWKLE/PSTN/IT).41
5.3.2 Capability tests (V5NWKLE/PSTN/CA).41
5.3.3 Valid behaviour tests (V5NWKLE/PSTN/BV).42
5.3.3.1 V5NWKLE/PSTN/BV/0.42
5.3.3.2 V5NWKLE/PSTN/BV/1.42
5.3.3.3 V5NWKLE/PSTN/BV/2.43
5.3.3.4 V5NWKLE/PSTN/BV/4.44
5.3.3.5 V5NWKLE/PSTN/BV/5.45
5.3.3.6 V5NWKLE/PSTN/BV/6.46
5.3.4 Inopportune behaviour tests (V5NWKLE/PSTN/BO) .46
5.3.4.1 V5NWKLE/PSTN/BO/0.46
5.3.4.2 V5NWKLE/PSTN/BO/1.48
5.3.4.3 V5NWKLE/PSTN/BO/2.49
5.3.4.4 V5NWKLE/PSTN/BO/4.50
5.3.4.5 V5NWKLE/PSTN/BO/6.52
5.3.5 Invalid behaviour tests (V5NWKLE/PSTN/BI).53
5.3.5.1 V5NWKLE/PSTN/BI/1 .53
5.3.5.2 V5NWKLE/PSTN/BI/4 .54
5.3.6 Timer expiry and counter mismatch tests (V5NWKLE/PSTN/TI).55
5.3.6.1 V5NWKLE/PSTN/TI/0 .55
5.3.6.2 V5NWKLE/PSTN/TI/1 .55
5.3.6.3 V5NWKLE/PSTN/TI/2 .56
5.3.6.4 V5NWKLE/PSTN/TI/4 .56

Page 5
ETS 300 324-5: April 1999
5.3.6.5 V5NWKLE/PSTN/TI/5 . 57
5.3.6.6 V5NWKLE/PSTN/TI/6 . 58
Annex A (informative): Bibliography. 59
History . 60

Page 6
ETS 300 324-5: April 1999
Blank page
Page 7
ETS 300 324-5: April 1999
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 5 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: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer
(LE side)";
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 link layer";
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 dates
Date of adoption of this ETS: 26 March 1999
Date of latest announcement of this ETS (doa): 30 June 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1999
Date of withdrawal of any conflicting National Standard (dow): 31 December 1999

Page 8
ETS 300 324-5: April 1999
Blank page
Page 9
ETS 300 324-5: April 1999
1 Scope
This fifth part of ETS 300 324 contains the Test Suite Structure (TSS) and Test Purposes (TPs) for the
Network layer (NWK) and parts of the system management of the Local Exchange (LE) side of a V5.1
interface.
The objective of this ETS is to provide conformance tests giving a high probability of inter-operability of an
Access Network (AN) and a LE from different manufacturers over the V5.1 interface. This ETS covers the
procedures described in ETS 300 324-1 [1] only.
ISO/IEC 9646-1 [4] is used as the basis for the methodology of conformance testing.
Concerning the Public Switched Telephone Network (PSTN) protocol testing, only the procedures defined
in ETS 300 324-1 [1] are covered by the tests defined in this ETS. An Implementation Under Test (IUT),
however, will have implemented a national PSTN protocol part as well. This requires that the tester
generates messages containing the national PSTN protocol specific optional Information Elements (IEs),
otherwise the IUT would not act on messages according to the PSTN protocol procedure definition.
However, this does not provide a comprehensive test of the national PSTN protocol mapping
specification, which is outside the scope of this ETS.
As the tests use PSTN messages containing optional IEs according to national specifications, the test
result is only valid for the implemented national mapping of the V5.1 PSTN protocol.
This ETS does not cover tests related to functions of the bearer channel. Those functions should be
tested in conjunction with testing the national PSTN protocol mapping specification.
This ETS contains no requirements concerning NWK tests for Integrated Services Digital Network Basic
Access (ISDN-BA).
Annex A lists the bibliography.
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) including amendment A1: "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): "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] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference Model".
[4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".

Page 10
ETS 300 324-5: April 1999
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 case: Refer to ISO/IEC 9646-1 [4]
abstract test suite: Refer to ISO/IEC 9646-1 [4]
current provisioning variant: Identifier for the presently active data set
data link layer: Refer to ISO 7498 [3]
implementation under test: Refer to ISO/IEC 9646-1 [4]
incorrect information element: Specified information element carrying information types not defined in
ETS 300 324-1 [1]
invalid PSTN information element: PSTN information element not according to national specific
requirements
invalid protocol data unit: PDU which contains an incorrect message format
invalid PSTN message: PSTN message carrying information elements not according to national specific
requirements
lower tester: Refer to ISO/IEC 9646-1 [4]
network layer: Refer to ISO 7498 [3]
new provisioning variant: Identifier for the data set which was announced to the IUT to become the next
active data set through reprovisioning
physical layer: Refer to ISO 7498 [3]
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [4]
PICS proforma: Refer to ISO/IEC 9646-1 [4]
specified information element: Information element identifier defined in ETS 300 324-1 [1]
system under test: Refer to ISO/IEC 9646-1 [4]
test purpose: Refer to ISO/IEC 9646-1 [4]
unknown provisioning variant: Identifier for a non-available data set
unspecified information element: Information element identifier not defined in ETS 300 324-1 [1]
valid information element: PSTN information element according to national specific requirements
valid PSTN message: PSTN message carrying information elements according to national specific
requirements
Page 11
ETS 300 324-5: April 1999
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATC Abstract Test Case
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability
COM Common control protocol
CTRL Control
FE Function Element
FSM Finite State Machine
ID Identifier
IE Information Element
ISDN Integrated Services Digital Network
ISDN-BA ISDN-Basic Access
IT Basic Interconnection
IUT Implementation Under Test
L3addr Layer 3 address
LE Local Exchange
LT Lower Tester
MDU Management Data Unit
MPH Management Physical Layer
NWK Network Layer
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statements
PSTN Public Switched Telephone Network
REST Restart
REVY Verify and Reprovisioning
SUT System Under Test
TI Timer
TP Test Purpose
TSS Test Suite Structure
Page 12
ETS 300 324-5: April 1999
4 Test Suite Structure (TSS)
4.1 TSS overview
Figure 1 shows the structure of the V5.1 LE side NWK test suite.
V5NW KLE CTRL IT
CA
BV
COM
TRANS/PROTOCOL
SYS_MAN/ RES T
SYS_MAN/ REV Y
PORT
TRANS/PROTOCOL
PS TN
IS DN-BA
BO COM TRANS/PROTOCOL
SYS_M AN/ REVY
PORT
TRANS/PROTOCOL
ISDN-BA
BI
COM TRANS/PROTOCOL
PORT
TR ANS/PROTOCOL
TI
COM TRANS/PROTOCOL
PORT TRANS/PROTOCOL
PS TN IT
CA
BV STATE
BO
STATE
BI
STATE
TI
STATE
Figure 1: NWK LE TSS
Page 13
ETS 300 324-5: April 1999
4.2 Test groups
Figure 2 gives an overview of the various protocol entities of a V5.1 interface. Table 1 maps each protocol
entity on tested protocol groups.
national
FE
DL-DATA
LE_PSTN_DL LE_PSTN
PSTN
protocol
MDU-CTRL
PH
MDL
MPH
V5
LE_PSTN_port_FSM
PH-DATA
MPH
MPH
LE_V5_FSM
LE_SM
MPH
PH-DATA
LE_ISDN_port_FSM
MDL
PH
ISDN
MDU-CTRL
L2
DL-DATA
FE
LE_CTRL_DL management
LE_CTRL
MPH
Figure 2: Network Layer LE - protocol entity overview
Table 1: Names used in figure 2 that correspond to ETS 300 324-1 [1]
NWK protocol entities Protocol entities defined in Protocol group references
ETS 300 324-1 [1]
LE_PSTN_port_FSM LE_PSTN_user_port_FSM 4.2.1.1
LE_ISDN_port_FSM LE_ISDN-BA_user_port_FSM 4.2.1.1
LE_CTRL LE_control_protocol 4.2.1.1
LE_SYS LE_system_management 4.2.1.1
LE_PSTN LE_PSTN_protocol 4.2.1.2
4.2.1 Protocol groups
4.2.1.1 Control protocol
All tests in the Control protocol (V5NWKLE/CTRL) test group are intended to verify as thoroughly as
possible the various procedures of the LE_control_protocol entity. Depending on provisioning the following
configurations are covered:
LE_system_management: the startup, restart, re-provisioning and verification procedures for normal
operation of the LE_system_management (V5NWKLE/CTRL/BV/COM/REST, V5NWKLE/CTRL/
BV/COM/REVY and V5NWKLE/CTRL/BO/COM/REVY) are tested.
LE_control_protocol: the normal and exceptional procedures of the LE_control_protocol are verified in
the test groups V5NWKLE/CTRL/BV/COM/TRANS, V5NWKLE/CTRL/BO/COM/TRANS,
V5NWKLE/CTRL/TI/COM/TRANS, V5NWKLE/CTRL/BV/PORT/TRANS, V5NWKLE/CTRL/BO/
PORT/TRANS and V5NWKLE/CTRL/TI/PORT/TRANS. Contents of the LE_control_protocol values
are not verified (e.g. the control function ID). The error handling procedures are verified in test
groups V5NWLKE/CTRL/BI/COM/TRANS and V5NWLKE/CTRL/BI/PORT/TRANS.
LE_PSTN_user_port: the blocking, blocking request and co-ordinated unblocking procedures of the
LE_PSTN_user_port_FSM are verified in the test group V5NWKLE/CTRL/BV/PORT/PSTN. The
interworking of the LE_PSTN_user_port_FSM and the LE_PSTN protocol entity is tested via the
LE_system_management.
Page 14
ETS 300 324-5: April 1999
LE_ISDN-BA_user_port: the blocking, blocking request, co-ordinated unblocking and activation/
deactivation procedures of the LE_ISDN-BA_user_port_FSM are verified in the test groups
V5NWKLE/CTRL/BV/PORT/ISDNBA and V5NWKLE/CTRL/BO/PORT/ISDNBA.
4.2.1.2 PSTN protocol
All tests in the PSTN protocol (V5NWKLE/PSTN) test group are intended to verify as thoroughly as
possible the various procedures of the LE_PSTN protocol entity.
The following PSTN procedures are covered:
- all path related normal operation procedures;
- significant path related exceptional procedures;
- the status enquiry procedure;
- the layer 3 error detection procedure;
- the error handling procedures;
- the port blocking procedure;
- the restart procedure.
4.2.2 Main test groups
4.2.2.1 Basic Interconnection (IT) tests
The IT test subgroup contains a basic set of TPs which assures that there is a sufficient conformance for
interconnection and that the chosen parameters are valid for the configuration.
4.2.2.2 Capability (CA) tests
Capability testing provides a limited testing to ascertain the capabilities stated in the PICS can be
observed.
4.2.2.3 Valid Behaviour (BV) tests
Predefined state transitions are considered as valid. The TPs in the BV test subgroup cover as far as
reasonable the verification of the normal and exceptional procedures of the various Finite State Machines
(FSMs).
A valid test is a test where the message sequence and the message contents is considered as valid (no
error indication shall be indicated).
4.2.2.4 Inopportune Behaviour (BO) tests
This test group is intended to verify that the IUT is able to react properly in the case an inopportune
protocol event occurring. Such an event is syntactically correct but occurs when it is not expected and an
error indication is caused.
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). An invalid PDU is defined as a syntactically incorrect message and therefore an
error indication is caused.
4.2.2.6 Timer (TI) expiry and counter mismatch tests
Different timers and counters are defined to supervise the various state transitions. This test group is
intended to verify that the FSM is reacting properly to an expiry of one of the timers or counter mismatch.

Page 15
ETS 300 324-5: April 1999
4.2.2.6.1 Timer expiry and counters of the Control protocol
Refer to ETS 300 324-1 [1], table 58.
T01 PORT CONTROL message sent
T02 COMMON CONTROL message sent
4.2.2.6.2 Timer expiry and counters of the PSTN protocol
Refer to ETS 300 324-1 [1], table 28.
T1 ESTABLISH sent
T3 DISCONNECT sent
T4 STATUS ENQUIRY sent
Tr SIGNAL received
Tt SIGNAL or PROTOCOL PARAMETER sent
Refer to ETS 300 324-1 [1], subclause 13.5.5.
S(S) Sequence number of the next message to be sent
S(A) Sequence number of the last acknowledged message
S(R) Sequence number of the last received message
M(S) Send sequence number in SIGNAL or PROTOCOL PARAMETER messages
M(R) Receive sequence number in SIGNAL ACK messages
4.2.2.6.3 Timer expiry and counters of the LE system management
Refer to ETS 300 324-1 [1], annex C, table C.1.
TR1 MDU-CTRL(restart request) to all PSTN protocol FSMs
TR2 MDU-CTRL(restart request) to CTRL protocol
TC1 CONTROL-DL establishment requested
TC2 CONTROL-DL establishment requested
TC3 PSTN-DL establishment requested
4.3 Test step structure
General dynamic behaviours are described in test steps which can be called from all ATCs within the
ATS:
state transitions (refer to subclause 4.3.1)
preambles (refer to subclause 4.3.2)
postambles (refer to subclause 4.3.3)
status checks (refer to subclause 4.3.4)
common behaviours (refer to subclause 4.3.5)
4.3.1 State transitions
The following subclauses identify the test steps used in the ATS. In general, each test step represents a
state transition. For example in the PSTN protocol, PSTN_LE1_2 is the test step which brings the LE
PSTN protocol FSM from PSTN_path_state LE1 to PSTN_path_state LE2. The state transitions are
declared in the parenthesis (originating state - destination state) which follow the test step names.
Three groups of state transitions are defined:
STARTUP startup the V5.1 interface and put the IUT into the initial state as defined in
subclause 5.1.5.
CTRL state transitions used to preamble and postamble the Control protocol before a TP can
be performed.
Page 16
ETS 300 324-5: April 1999
PSTN state transitions used to preamble and postamble the PSTN protocol before a TP can
be performed.
To test the V5.1 interface certain sequences (i.e. preamble) shall be executed to reach the state which is
the subject for the TPs.
4.3.1.1 Startup of V5.1 interface
The startup procedure for a V5.1 interface depends on the provisioned data configuration. Therefore, the
two PICS items M1 and M2 (refer to subclause 6.5.1 of ETS 300 324-2 [2]) are used to define the
implemented configuration of the IUT.
NOTE 1: ETS 300 324-2 [2] requires at least one of the two PICS items to be set to "Yes".
PICS item description:
M1: ISDN-BA ports supported;
M2: PSTN ports supported.
NOTE 2: One port of each supported type shall be provisioned in a way that the IUT tries to
enter the operational state for these ports after system startup (see subclause 5.1.6).
Depending on the setting of the PICS items, the startup procedure is described in figure 3. This flow
diagram describes the test step called STARTUP_LE.
PICS M1 = YES
PICS M1 = NO PICS M1 = YES
PICS M2 = YES PICS M2 = YES
PICS M2 = NO
LE LT1
Variant & Interface ID
req var and interf ID req var and interf ID req var and interf ID
(note 1)
var and interf ID var and interf ID var and interf ID
Restart
restart req restart req
(note 2)
restart complete restart complete
restart complete
restart complete
PSTN port FSM
unblock req
unblock req
(note 3)
block cmd
block cmd
ISDN port FSM
(note 4)
unblock req
unblock req
block cmd block cmd
NOTE 1: A test of the IUT's capability of receiving a request for the variant and interface ID is covered in
subclause 5.2.3.1.1.
NOTE 2: LT1 shall wait for the receipt of restart complete from the IUT before sending restart complete.
NOTE 3: To reach the initial state of the IUT PSTN user port FSM as defined in subclause 5.1.5, the
IUT's unblocking request is rejected by LT1. Before rejecting the unblock request, it shall be
verified that the IUT PSTN protocol has entered the PSTN_path_state LE6 (Port blocked).
NOTE 4: To reach the initial state of the IUT ISDN-BA user port FSM as defined in subclause 5.1.5, the
IUT's unblocking request is rejected by LT1.
Figure 3: STARTUP_LE flow diagram

Page 17
ETS 300 324-5: April 1999
4.3.1.2 Common control Protocol (system management)
Refer to ETS 300 324-1 [1], table 62 and annex C.
CTRL_COM_LE0_1
On LE system startup (reset or initialization) the LE_CONTROL_DL shall be established between LE and
LT1 and the common and port control protocol shall enter the In Service state LE1.
4.3.1.3 Control protocol (PSTN port FSM)
Refer to ETS 300 324-1 [1], table 41.
CTRL_PSTN_LE20_10
On receipt of a PORT CONTROL message containing the control_function_element IE FE204
(block_cmd) the IUT PSTN user port FSM shall enter state LE1.0.
NOTE 1: This results in a state transition of the PSTN protocol as well. The PSTN protocol of
the affected port is forced to enter the PSTN_path_state LE6.
CTRL_PSTN_LE10_20
On receipt of a PORT CONTROL message containing the control_function_element IE FE202
(unblock_req) the IUT shall respond with the PORT CONTROL message containing the
control_function_element IE FE201 (unblock_ack) and then enter state LE2.0.
NOTE 2: This results in a state transition of the PSTN protocol as well. The PSTN protocol of
the affected port is forced to enter the PSTN_path_state LE1.
4.3.1.4 Control protocol (ISDN-BA port FSM)
Refer to ETS 300 324-1 [1], table 36.
CTRL_ISDNBA_LE20_10
On receipt of a PORT CONTROL message containing the control_function_element IE FE204
(block_cmd) the IUT ISDN-BA user port FSM shall enter state LE1.0.
CTRL_ISDNBA_LE10_20
On receipt of a PORT CONTROL message containing the control_function_element IE FE202
(unblock_req) the IUT shall respond with the PORT CONTROL message containing the
control_function_element IE FE201 (unblock_ack) and the IUT ISDN-BA user port FSM shall then enter
state LE2.0.
CTRL_ISDNBA_LE20_22
On receipt of a PORT CONTROL message containing the control_function_element IE FE104
(access_activated) the IUT ISDN-BA user port FSM shall enter state LE2.2.
4.3.1.5 PSTN protocol
Refer to ETS 300 324-1 [1], table 30.
All messages sent within the test steps shall be valid PSTN messages.
PSTN_LEx_6” CTRL_PSTN_LE20_10 (refer to subclause 4.3.1.3)
On receipt of a PORT CONTROL message containing the control_function_element IE FE204
(block_cmd) the IUT PSTN protocol shall enter PSTN_path_state LE6.
PSTN_LE6_1” CTRL_PSTN_LE10_20 (refer to subclause 4.3.1.3)
On receipt of a PORT CONTROL message containing the control_function_element IE FE202
(unblock_req) the IUT PSTN protocol shall enter PSTN_path_state LE1.
PSTN_LE1_0
On receipt of a COMMON CONTROL message containing the control_function_ID "restart req" the IUT
PSTN protocol shall enter PSTN_path_state LE0.

Page 18
ETS 300 324-5: April 1999
PSTN_LE0_1
On receipt of a COMMON CONTROL message containing the control_function_ID "restart complete" the
IUT PSTN protocol shall enter PSTN_path_state LE1.
PSTN_LE1_2
On receipt of a terminating call request (FE-establish_request) the IUT PSTN protocol shall send an
ESTABLISH message and enter PSTN_path_state LE2.
PSTN_LE4_5
On receipt of a SIGNAL message containing a faulty sequence number the IUT PSTN protocol shall send
a DISCONNECT message and enter PSTN_path_state LE5.
4.3.2 Preambles
The preamble test step group contains test steps needed for initialization of the IUT before testing the
particular TP. All combinations of the test steps defined in subclauses 4.3.1.2 to 4.3.1.5 can be used to
create preambles. Each preamble shall start from the IUT initial state as defined in subclause 5.1.5.
4.3.3 Postambles
After each ATC the IUT shall be brought back to the initial state as defined in subclause 5.1.5. All
combinations of the test steps defined in subclauses 4.3.1.2 to 4.3.1.5 can be used to create postambles.
4.3.4 Status verification
4.3.4.1 PSTN protocol
Based on ETS 300 324-1 [1], table 30, it is possible to identify the state of the IUT PSTN protocol FSM. All
messages sent within the test steps shall be valid PSTN messages.
PSTN_CHECK_STATE_0 (Out of Service)
Run test step CTRL_PSTN_LE10_20.
On receipt of a DISCONNECT COMPLETE message the IUT PSTN protocol shall send a STATUS
ENQUIRY message ⇒ the IUT PSTN protocol is not in one of the PSTN_path_states LE1 up to LE6.
Complete this test step by sending a STATUS message containing the state IE AN0.
PSTN_CHECK_STATE_1 (Null)
On receipt of an ESTABLISH ACK message the IUT PSTN protocol shall send a STATUS ENQUIRY
message ⇒ the IUT PSTN protocol is not in one of the PSTN_path_states LE2 and LE5.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN1" the IUT PSTN protocol shall not send a DISCONNECT message ⇒ the IUT PSTN protocol is not in
one of the PSTN_path_states LE3 and LE4.
On receipt of an ESTABLISH ACK message the IUT PSTN protocol shall send again a STATUS
ENQUIRY message.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN5" the IUT PSTN protocol shall send a DISCONNECT message ⇒ the IUT PSTN protocol is not in
one of the PSTN_path_states LE0 and LE6.
Complete this test step by sending a DISCONNECT COMPLETE message (IUT PSTN protocol enters the
PSTN_path_state LE1).
Page 19
ETS 300 324-5: April 1999
PSTN_CHECK_STATE_2 (Path initiated by LE)
On receipt of a SIGNAL message the IUT PSTN protocol shall send a STATUS ENQUIRY message ⇒
the IUT PSTN protocol is not in one of the PSTN_path_states LE4 and LE5.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN1" the IUT PSTN protocol shall not send a DISCONNECT message ⇒ the IUT PSTN protocol is not in
the PSTN_path_state LE3.
On receipt of a SIGNAL message the IUT PSTN protocol shall send again a STATUS ENQUIRY
message.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN3" the IUT PSTN protocol shall send a DISCONNECT message ⇒ the IUT PSTN protocol is not in
one of the PSTN_path_states LE0, LE1 and LE6.
Complete this test step by sending a DISCONNECT COMPLETE message (IUT PSTN protocol enters the
PSTN_path_state LE1).
PSTN_CHECK_STATE_4 (Path active)
On receipt of an ESTABLISH message the IUT PSTN protocol shall send a STATUS ENQUIRY message
⇒ the IUT PSTN protocol is not in one of the PSTN_path_states LE1, LE2, LE3 and LE5.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN2" the IUT PSTN protocol shall send a DISCONNECT message ⇒ the IUT PSTN protocol is not in
one of the PSTN_path_states LE0 and LE6.
Complete this test step by sending a DISCONNECT COMPLETE message (IUT PSTN protocol enters the
PSTN_path_state LE1).
PSTN_CHECK_STATE_5 (Path disconnect request)
On receipt of a DISCONNECT message the IUT PSTN protocol shall send no DISCONNECT
COMPLETE and no STATUS ENQUIRY message ⇒ the IUT PSTN protocol is not in one of the
PSTN_path_states LE0, LE1, LE2, LE3, LE4 and LE6.
PSTN_CHECK_STATE_6 (Port blocked)
On receipt of a DISCONNECT message the IUT PSTN protocol shall send a STATUS ENQUIRY
message ⇒ the IUT PSTN protocol is not in one of the PSTN_path_states LE1 up to LE5.
On receipt of a STATUS message containing the cause_type "response to status enquiry" and the state IE
"AN6" the IUT PSTN protocol shall not send a DISCONNECT message.
Run test step CTRL_PSTN_LE10_20.
On receipt of a DISCONNECT COMPLETE message the IUT PSTN protocol shall not send a STATUS
ENQUIRY message ⇒ the IUT PSTN protocol is not in the PSTN_path_state LE0.
4.3.4.2 Port control protocol
CHECK_PC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5 interface.
Afterwards teststep CTRL_PSTN_LE10_20 (refer to subclause 4.3.1.3) or CTRL_ISDNBA_LE10_20
(refer to subclause 4.3.1.4), depending on the affected port type is applied.
4.3.4.3 Common control protocol
CHECK_CC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5 interface.
On receipt of a COMMON CONTROL message containing the control_function_id IE "request variant &
interface ID" the IUT shall send a COMMON CONTROL ACK message and a COMMON CONTROL
message containing the control_function_id IE "variant & interface ID".
Complete this teststep by sending a COMMON CONTROL ACK message.
4.3.5 Common test steps
This test step group contains procedures which are used in more than one ATC.

Page 20
ETS 300 324-5: April 1999
4.4 Defaults
The default section describes the behaviour in case of an unexpected test event.
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)
4.5.1 ASPs
The format of the two used ASPs is defined as described in ETS 300 324-1 [1], subclause 13.4.
dl_data_req
dl_data_ind
4.5.2 PDUs
4.5.2.1 Common control protocol
ctrl_common_control
ctrl_common_control_ack
4.5.2.2 Port control protocol
ctrl_port_control
ctrl_port_control_ack
4.5.2.3 PSTN protocol
pstn_establish
pstn_establish_ack
pstn_signal
pstn_signal_ack
pstn_disconnect
pstn_disconnect_complete
pstn_status_enquiry
pstn_status
pstn_protocol_parameter
4.5.3 Information elements
4.5.3.1 Variable length information elements
4.5.3.1.1 Control protocol
ctrl_control_function_element
ctrl_control_function_id
ctrl_variant
ctrl_interface_id
4.5.3.1.2 PSTN protocol
pstn_sequence_number
pstn_cadenced_ringing
pstn_pulsed_signal
pstn_steady_signal
pstn_digit_signal
pstn_recognition_time
pstn_enable_autonomous_ack
pstn_disable_autonomous_ack
pstn_cause
pstn_resource_unavailable
Page 21
ETS 300 324-5: April 1999
4.5.3.2 Single octet information elements
4.5.3.2.1 Control protocol
ctrl_performance_grading
ctrl_rejection_cause
4.5.3.2.2 PSTN protocol
pstn_line_infomation
pstn_state
pstn_autonomous_signalling_sequence
pstn_sequence_response
pstn_pulse_notification
4.6 Timers and counters of the Abstract Test Suite (ATS)
This subclause describes the timers and counters used in the ATS. The min and max indications define if
the timer value represents the minimum or maximum limit of a timer. The timer values contain some
additional tolerances for delays caused by test simulators. Therefore, a bigger timer tolerance is given
than defined in ETS 300 324-1 [1]:
Minimum value of ATS timer = ETS timer - ETS tolerance;
Maximum value of ATS timer = ETS timer + 2 x ETS tolerance.
The repetition of messages by the IUT shall be tested in the following way: the message has to be
repeated within the time period T_min < T < T_max. This testing procedure applies to the tests in the TI
test group only.
NOTE: Maximum values of some ATS timers are defined as test suite parameters.
Timers used in the ATS are given in Timer Declarations part of the ATS.
Table 2 gives the identified protocol counters used in the ATS and the references to ETS 300 324-1 [1].
Table 2: Protocol counter values and references to ETS 300 324-1 [1]
ATS counter ATS counter Explanation Reference to
name value ETS 300 324-1 [1]
N01 1 Allowed number of repetitions of the PORT clause 14, table 61
CONTROL message
N02 1 Allowed number of repetitions of the COMMON clause 14, table 62
CONTROL message
N1 1 Allowed number of repetitions of the clause 13, table 28
ESTABLISH message
N3 2 Allowed number of repetitions of the clause 13, table 28
DISCONNECT message
N4 2 Allowed number of repetitions of the STATUS clause 13, table 28
ENQUIRY message
Page 22
ETS 300 324-5: April 1999
5 Test Purposes (TPs)
5.1 Introduction
For each test requirement, a TP is defined.
This subclause details the TPs for the LE side of NWK of the V5.1 interface for each test group and
references to the corresponding ATC.
At the beginning of each test subgroup the initial state (refer to subclause 5.1.5), the preambles (refer to
subclause 4.3.2) and the postambles (refer to subclause 4.3.3) are listed.
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 Control protocol
(test group) 2 PSTN protocol
= 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 Expiry and Counter Mismatch
= group level 1: 1 Common control
2 Port control
_ (underscore) not relevant
= group level 2: 1 Transport
2 System management procedure Restart
3 System management procedure
Re-provisioning & Verification
4 PSTN
5 ISDN BA
_ (underscore) not relevant
= test purpose type: S Single
_ (underscore) not relevant
= state: (0-9)
M Multiple state transition
_ (underscore) not relevant
= substate: (0-9)
_ (underscore) not relevant
= sequential number: (01-99)

Page 23
ETS 300 324-5: April 1999
5.1.2 Source of TP definition
The TPs were developed based on ETS 300 324-1 [1], clauses 13 and 14, and annex C.
5.1.3 Test strategy
To achieve a maximum of test coverage with an appropriate number of TPs the following selection criteria
have been applied:
a) only the first up to the third value of the PSTN sequence number variables S(S), S(A), S(R), M(S),
M(R) is covered;
b) the error handling procedures of the Control and PSTN protocol are not exhaustively tested. Not all
possible combinations of protocol errors in all protocol st
...