SIST ETS 300 347-5 E2:2003

SLOVENSKI STANDARD
01-december-2003
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.2 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.2 interface for the support of Access
Network (AN); Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for
the network layer (LE side)
Ta slovenski standard je istoveten z: ETS 300 347-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 347-5
TELECOMMUNICATION April 1999
STANDARD Second Edition
Source: SPS Reference: RE/SPS-09056-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.2 interface for the support of Access Network (AN);
Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network layer (LE side)
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 347-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 347-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. 10
4 Test Suite Structure (TSS). 11
4.1 Overview. 11
4.2 Test groups . 12
4.2.1 Protocol groups. 13
4.2.1.1 Control protocol. 13
4.2.1.2 Public Switched Telephone Network (PSTN) protocol. 13
4.2.1.3 Link control protocol . 13
4.2.1.4 Bearer Channel Connection (BCC) protocol . 13
4.2.1.5 Protection protocol . 14
4.2.2 Main test groups . 14
4.2.2.1 Basic interconnection tests (IT). 14
4.2.2.2 Capability tests (CA). 14
4.2.2.3 Valid behaviour tests (BV). 14
4.2.2.4 Inopportune behaviour tests (BO) . 14
4.2.2.5 Invalid behaviour tests (BI). 14
4.2.2.6 Timer expiry and counter mismatch tests (TI). 14
4.2.2.6.1 Timers and counters of the Control
protocol. 14
4.2.2.6.2 Timers and counters of the PSTN
protocol. 15
4.2.2.6.3 Timers and counters of the Link
control protocol. 15
4.2.2.6.4 Timers and counters of the BCC
protocol. 15
4.2.2.6.5 Timers and counters of the Protection
protocol. 15
4.2.2.6.6 Timers and counters of the LE system
management . 15
4.3 Test step structure. 15
4.3.1 State transitions . 15
4.3.1.1 Start-up of V5.2 interface . 16
4.3.1.2 Common control protocol (system management). 18
4.3.1.3 Control protocol (PSTN port FSM) . 18
4.3.1.4 Control protocol (ISDN-BA port FSM) . 18
4.3.1.5 Control protocol (ISDN-PRA port FSM) . 18
4.3.1.6 PSTN protocol. 19
4.3.1.7 Link control protocol . 19
4.3.1.8 BCC protocol. 19
4.3.1.9 Protection protocol . 20
4.3.2 Preambles. 20
4.3.3 Postambles . 20
4.3.4 Status verification. 21
4.3.4.1 PSTN protocol. 21
4.3.4.2 Link control FSM . 21
4.3.5 Common test steps. 21
4.4 Defaults . 21
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs) . 21

Page 4
ETS 300 347-5: April 1999
4.5.1 ASPs .21
4.5.2 PDUs .21
4.5.2.1 Common control protocol .21
4.5.2.2 Port control protocol.21
4.5.2.3 PSTN protocol .22
4.5.2.4 Link control protocol .22
4.5.2.5 BCC protocol .22
4.5.2.6 Protection protocol.22
4.5.3 Information elements.22
4.5.3.1 Variable length information elements .22
4.5.3.1.1 Control protocol.22
4.5.3.1.2 PSTN protocol .22
4.5.3.1.3 Link control protocol.22
4.5.3.1.4 BCC protocol.22
4.5.3.1.5 Protection protocol.23
4.5.3.2 Single octet information elements .23
4.5.3.2.1 Control protocol.23
4.5.3.2.2 PSTN protocol .23
4.5.3.2.3 Link control protocol.23
4.5.3.2.4 BCC protocol.23
4.5.3.2.5 Protection protocol.23
4.6 Timers and counters of the Abstract Test Suite (ATS).23
5 Test Purposes (TPs) .25
5.1 Introduction .25
5.1.1 Test purpose naming convention .25
5.1.2 Source of test purpose definition.26
5.1.3 Test strategy.26
5.1.3.1 Common control protocol .26
5.1.3.2 Port control protocol.26
5.1.3.3 PSTN protocol .26
5.1.3.4 Link control protocol .27
5.1.3.5 BCC protocol .27
5.1.3.6 Protection protocol.28
5.1.4 Requirements not covered by test purposes.28
5.1.5 Initial states .28
5.1.6 Test and data configuration requirements.29
5.2 Control protocol.29
5.2.1 Basic interconnection tests (V5NWKLE/CTRL/IT).29
5.2.2 Capability tests (V5NWKLE/CTRL/CA).30
5.2.3 Valid behaviour tests (V5NWKLE/CTRL/BV).30
5.2.3.1 V5NWKLE/CTRL/BV/COM.30
5.2.3.2 V5NWKLE/CTRL/BV/PORT .30
5.2.3.2.1 V5NWKLE/CTRL/BV/PORT/TRANS.30
5.2.3.2.2 V5NWKLE/CTRL/BV/PORT/PSTN.30
5.2.3.2.3 V5NWKLE/CTRL/BV/PORT/ISDNBA.30
5.2.3.2.4
.... V5NWKLE/CTRL/BV/PORT/ISDNPRA30
5.2.4 Inopportune behaviour tests (V5NWKLE/CTRL/BO) .32
5.2.4.1 V5NWKLE/CTRL/BO/COM .32
5.2.4.2 V5NWKLE/CTRL/BO/PORT.32
5.2.4.2.1 V5NWKLE/CTRL/BO/PORT/TRANS.32
5.2.4.2.2 V5NWKLE/CTRL/BO/PORT/ISDNBA .33
5.2.4.2.3
....V5NWKLE/CTRL/BO/PORT/ISDNPRA33
5.2.5 Invalid behaviour tests (V5NWKLE/CTRL/BI).33
5.2.6 Timer expiry and counter mismatch tests (V5NWKLE/CTRL/TI).33
5.3 PSTN protocol.33
5.4 Link control protocol.34
5.4.1 Basic interconnection tests (V5NWKLE/LINK/IT) .34
5.4.2 Capability tests (V5NWKLE/LINK/CA) .34
5.4.3 Valid behaviour tests (V5NWKLE/LINK/BV) .34
5.4.3.1 V5NWKLE/LINK/BV/TRANS .34

Page 5
ETS 300 347-5: April 1999
5.4.3.2 V5NWKLE/LINK/BV/LINK . 35
5.4.4 Inopportune behaviour tests (V5NWKLE/LINK/BO) . 47
5.4.4.1 V5NWKLE/LINK/BO/TRANS. 47
5.4.4.2 V5NWKLE/LINK/BO/LINK. 47
5.4.5 Invalid behaviour tests (V5NWKLE/LINK/BI) . 50
5.4.5.1 V5NWKLE/LINK/BI/TRANS . 50
5.4.6 Timer expiry and counter mismatch tests (V5NWKLE/LINK/TI). 51
5.4.6.1 V5NWKLE/LINK/TI/TRANS . 51
5.5 BCC protocol . 51
5.5.1 Basic interconnection tests (V5NWKLE/BCC/IT) . 51
5.5.2 Capability tests (V5NWKLE/BCC/CA) . 52
5.5.3 Valid behaviour tests (V5NWKLE/BCC/BV) . 53
5.5.4 Inopportune behaviour tests (V5NWKLE/BCC/BO). 57
5.5.5 Invalid behaviour tests (V5NWKLE/BCC/BI) . 60
5.5.6 Timer expiry and counter mismatch tests (V5NWKLE/BCC/TI) . 62
5.6 Protection protocol. 62
5.6.1 Basic interconnection tests (V5NWKLE/PROTECT/IT). 63
5.6.2 Capability tests (V5NWKLE/PROTECT/CA). 63
5.6.3 Valid behaviour tests (V5NWKLE/PROTECT/BV). 63
5.6.4 Invalid behaviour tests (V5NWKLE/PROTECT/BI). 68
5.6.5 Timer expiry and counter mismatch tests (V5NWKLE/PROTECT/TI) . 69
Annex A (informative): Bibliography. 71
History . 72

Page 6
ETS 300 347-5: April 1999
Blank page
Page 7
ETS 300 347-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.2 interface as described below:
Part 1: "V5.2 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (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 347-5: April 1999
Blank page
Page 9
ETS 300 347-5: April 1999
1 Scope
This fifth part of ETS 300 347 contains the Test Suite Structure and Test Purposes (TSS&TP) for the
NetWorK layer (NWK) and parts of the system management of the Local Exchange (LE) side of a V5.2
interface.
The objective of this ETS is to provide conformance tests giving a high probability of inter-operability of an
Access Network (AN) and a LE from different manufacturers over the V5.2 interface. This ETS covers
only the procedures described in ETS 300 347-1 [2].
ISO/IEC 9646-1 [4] and ISO/IEC 9646-2 [5] are used as the basis for the test methodology.
This ETS needs to be read in conjunction with ETS 300 324-5 [1]. The two documents share a common
format and clauses within ETS 300 324-5 [1] are directly referenced.
Annex A lists the bibliography.
2 Normative references
This ETS incorporates by dated and 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-5 (1999): "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)".
[2] ETS 300 347-1 (1994) including amendment A1: "V interfaces at the digital
Local Exchange (LE); V5.2 interface for the support of Access Network (AN);
Part 1: V5.2 interface specification".
[3] ETS 300 347-2 (1994): "V interfaces at the digital Local Exchange (LE); V5.2
interface for the support of Access Network (AN); Part 2: Protocol
Implementation Conformance Statement (PICS) proforma".
[4] ISO/IEC 9646-1 (1995): "Information technology - Open systems
interconnection - Conformance testing methodology and framework -
Part 1: General concepts".
[5] ISO/IEC 9646-2 (1995): "Information technology - Open systems
interconnection - Conformance testing methodology and framework -
Part 2: Abstract test suite specification".

Page 10
ETS 300 347-5: April 1999
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, in addition to those given in
ETS 300 324-5 [1] and ETS 300 347-1 [2]:
specified information element: Information element identifier as defined in ETS 300 347-1 [2]
unspecified information element: Information element identifier which is not defined in
ETS 300 347-1 [2]
incorrect information element: A specified information element carrying information element types
which are not defined in ETS 300 347-1 [2]
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AIS Alarm Indication Signal
AN Access Network
ASP Abstract Service Primitive
ATS Abstract Test Suite
BCC Bearer Channel Connection
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
ISDN-PRA ISDN Primary Rate Access
IT Basic Interconnection
IUT Implementation Under Test
L3addr Layer 3 address
LE Local Exchange
LT1 Lower Tester 1
MDU Management Data Unit
MPH Management Physical layer
NWK Network layer
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PSTN Public Switched Telephone Network
RAI Remote Alarm Indication
REQ Request
SN Sequence Number
SUT System Under Test
TE Terminal Equipment (ISDN or PSTN)
TI Timer
TP Test Purpose
TS Time Slot
TSS Test Suite Structure
UP User Port
Page 11
ETS 300 347-5: April 1999
4 Test Suite Structure (TSS)
4.1 Overview
Figure 1 shows the structure of the V5.2 NWK test suite.
V5NW KLE
CTRL IT
CA
BV
COM TRANS/PRO TOCOL
SYS_M AN/ REST
SYS_M AN REVY
PO RT
TRANS/PRO TO CO L
PSTN
IS D N -B A
ISDN-PRA
BO TRANS/PRO TO CO L
COM
SYS_M AN REVY
PO RT TRANS/PRO TO CO L
ISDN-BA
ISDN-PRA
BI COM TRANS/PRO TO CO L
PO RT TRANS/PRO TO CO L
TI
TRANS/PRO TO CO L
COM
TRANS/PRO TO CO L
PO RT
PSTN IT
CA
BV STATE
BO STATE
BI
STATE
TI STATE
LINK
IT
CA
BV TRANS/PRO TO CO L
LINK CTRL
BO TRANS/PRO TO CO L
LINK CTRL
BI
TR AN S/PRO T O C O L
TI
TR AN S/PR O TO C O L
BCC
IT
CA
BV
BO
BI
TI
PRO TECT
IT
CA
BV
BI
TI
Figure 1: NWK LE test suite structure

Page 12
ETS 300 347-5: April 1999
4.2 Test groups
Figure 2 gives an overview of the various protocol entities of a V5.2 interface. Table 1 maps each protocol
entity on tested protocol groups.
NWK_LE
FE
DL-DATA
LE_PSTN national
PSTN
LE_RM
MDU
PH-DATA
protocol
MDU
MPH
DL-DATA MDU
LE_BCC
V5
LE_PSTN_port_FSM
MDL
LE_V5_FSM
LE_DL
LE_SYS
DL-DATA MDU
LE_PROT
(ANI)
MDU LE_ISDN_port_FSM
DL-DATA
LE_LINK
FE
MDU
PH
FE
ISDN
DL-DATA
LE_CTRL
layer 2
MPH
management
MPH
LE_LINK_CTRL_FSM
Figure 2: NWK LE - protocol entity overview
Table 1: Names used in figure 2 that correspond to ETS 300 347-1 [2]
Network layer Protocol entities defined in Protocol group references
protocol entities ETS 300 347-1 [2]
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_ISDN-PRA_user_port_FSM
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
LE_LINK LE_link_control_protocol 4.2.1.3
LE_LINK_CTRL_FSM LE_link_control_FSM 4.2.1.3
LE_RM LE_resource_management 4.2.1.4
LE_BCC LE_BCC_protocol 4.2.1.4
LE_PROT LE_protection_protocol 4.2.1.5

Page 13
ETS 300 347-5: April 1999
4.2.1 Protocol groups
4.2.1.1 Control protocol
The contents of this subclause are identical to subclause 4.2.1.1 of ETS 300 324-5 [1] with the following
additions for the ISDN-PRA user port Finite State Machine (FSM).
Depending on provisioning the following configuration is tested:
LE_ISDN-PRA_user_port:
The blocking, blocking request and co-ordinated unblocking procedures of the LE_ISDN-
PRA_user_port_FSM are verified in the test groups V5NWKLE/CTRL/BV/PORT/ISDNPRA and
V5NWKLE/CTRL/BO/PORT/ISDNPRA.
4.2.1.2 Public Switched Telephone Network (PSTN) protocol
The contents of this subclause are identical to subclause 4.2.1.2 of ETS 300 324-5 [1].
4.2.1.3 Link control protocol
All tests in the Link control protocol (V5NWKLE/LINK) test group are intended to verify as thoroughly as
possible the various procedures of the LE_link_control_protocol entity. Depending on provisioning the
following configurations are covered:
LE_link_control_protocol:
The normal and exceptional procedures of the LE_link_control_protocol are verified in the test groups
V5NWKLE/LINK/BV/TRANS, V5NWKLE/LINK/BO/TRANS and V5NWKLE/LINK/TI/TRANS.
The error handling procedures are verified in the test group V5NWKLE/LINK/BI/TRANS.
LE_link_control_FSM:
The link failure, link blocking, link blocking request, co-ordinated link unblocking and link identification
procedures of the LE_link_control_FSM are verified in the test group V5NWKLE/LINK/BV/LINK and
V5NWKLE/LINK/BO/LINK.
4.2.1.4 Bearer Channel Connection (BCC) protocol
All tests in the BCC protocol (V5NWKLE/BCC) test group are intended to verify as thoroughly as possible
the various procedures of the LE_BCC protocol entity.
The following BCC procedures are covered:
- normal and exceptional bearer channel allocation procedure;
- normal and exceptional bearer channel de-allocation procedure;
- audit procedure;
- AN internal failure notification procedure;
- error handling procedures.
Page 14
ETS 300 347-5: April 1999
4.2.1.5 Protection protocol
All tests in the Protection protocol (V5NWKLE/PROTECT) test group are intended to verify as thoroughly
as possible the various procedures of the LE Protection protocol entity.
The following Protection protocol procedures are covered:
- transmission of Protection protocol messages;
- normal and exceptional sequence number reset procedure;
- normal and exceptional standard protection switch-over procedure initiated by LE side;
- normal and exceptional dedicated protection switch-over procedure initiated by OS LE;
- normal and exceptional switch-over procedure requested by AN side;
- error handling procedures.
4.2.2 Main test groups
4.2.2.1 Basic interconnection tests (IT)
The contents of this subclause are identical to subclause 4.2.2.1 of ETS 300 324-5 [1].
4.2.2.2 Capability tests (CA)
The contents of this subclause are identical to subclause 4.2.2.2 of ETS 300 324-5 [1].
4.2.2.3 Valid behaviour tests (BV)
The contents of this subclause are identical to subclause 4.2.2.3 of ETS 300 324-5 [1].
4.2.2.4 Inopportune behaviour tests (BO)
The contents of this subclause are identical to subclause 4.2.2.4 of ETS 300 324-5 [1].
4.2.2.5 Invalid behaviour tests (BI)
The contents of this subclause are identical to subclause 4.2.2.5 of ETS 300 324-5 [1].
4.2.2.6 Timer expiry and counter mismatch tests (TI)
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 expire of one of the timers or counter mismatch.
4.2.2.6.1 Timers and counters of the Control protocol
The contents of this subclause are identical to subclause 4.2.2.6.1 of ETS 300 324-5 [1] with additions for
the accelerated alignment procedure. This timers are given in ETS 300 347-1 [2], annex C, table C.1.
TU1 MDU-CTRL(UNBLOCK ALL RELEVANT ACCEPTED) to all PSTN and ISDN user port
FSMs.
TU2 MDU-CTRL(UNBLOCK ALL RELEVANT PORTS REQUEST) to all PSTN and ISDN user
port FSMs.
Page 15
ETS 300 347-5: April 1999
4.2.2.6.2 Timers and counters of the PSTN protocol
The contents of this subclause are identical to subclause 4.2.2.6.2 of ETS 300 324-5 [1].
4.2.2.6.3 Timers and counters of the Link control protocol
Refer to ETS 300 347-1 [2], table 23.
LCTO1 LINK CONTROL message sent
4.2.2.6.4 Timers and counters of the BCC protocol
Refer to ETS 300 347-1 [2], table 46.
TBCC1 ALLOCATION sent
TBCC2 DE-ALLOCATION sent
TBCC3 DE-ALLOCATION sent
TBCC4 AUDIT sent
4.2.2.6.5 Timers and counters of the Protection protocol
Refer to ETS 300 347-1 [2], table 64.
TSO1 SWITCH-OVER COM sent
TSO2 OS-SWITCH-OVER COM sent
TSO4 RESET SN COM sent
TSO5 RESET SN COM received
Refer to ETS 300 347-1 [2], subclause 18.6.2.
VP(S) Send State Variable
VP(R) Receive State Variable
4.2.2.6.6 Timers and counters of the LE system management
The contents of this subclause are identical to subclause 4.2.6.3 of ETS 300 324-5 [1].
4.3 Test step structure
General dynamic behaviours are described in test steps which can be called from all test cases within the
Abstract Test Suite (ATS):
state transitions (refer to subclause 4.3.1);
preambles (refer to subclause 4.3.2);
postambles (refer to subclause 4.3.3);
status verification (refer to subclause 4.3.4);
common test steps (refer to subclause 4.3.5).
4.3.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.

Page 16
ETS 300 347-5: April 1999
Six groups of state transitions are defined:
STARTUP start up the V5 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 test
purpose can be performed.
PSTN state transitions used to preamble and postamble the PSTN protocol before a test
purpose can be performed.
LINK state transitions used to preamble and postamble the Link control protocol before a
test purpose can be performed.
BCC state transitions used to preamble and postamble the BCC protocol before a test
purpose can be performed.
PROTECT state transitions used to preamble and postamble the Protection protocol before a test
purpose can be performed.
To test the V5.2 interface certain sequences (i.e. preamble) shall be executed to reach the state which is
the subject for the test purposes.
4.3.1.1 Start-up of V5.2 interface
The start-up procedure for a V5.2 interface depends on the provisioned data configuration. Therefore, the
three PICS items N11, N12, M2 and N9 (see subclause 6.5.1 of ETS 300 347-2 [3]) are used to define the
implemented configuration of the IUT.
NOTE 1: ETS 300 347-2 [3] requires that at least one of the three PICS items N11, N12 and M2
shall be set.
NOTE 2: PICS item N9 defines the configuration of IUT with multiple or one single 2 048 kbit/s
digital links as a V5.2 interface. A single 2 048 kbit/s digital link have no protection
functions implemented.
Page 17
ETS 300 347-5: April 1999
PICS N11 or N12 = YES PICS N11 and N12 = NO PICS N11 or N12 = YES
PICS M2 = YES PICS M2 = YES PICS M2 = NO
LE LT1
Variant & interface ID
req var and interface ID req var and interface ID req var and interface ID
Note 1
var and interface ID var and interface ID var and interface ID
Link identification
Link identification req Link identification req Link identification req
Note 2
Link identification ack Link identification ack Link identification ack
Link identification rel Link identification rel Link identification rel
Restart
Restart Req Restart Req
Restart Complete Restart Complete
Note 3
Restart Complete Restart Complete
PSTN port FSM
Unblock req Unblock req
Note 4
Block cmd Block cmd
ISDN port FSM
Unblock req Unblock req
Note 5
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.
NOTE 2: The number of appearances of this part of the system start-up procedure depends on the
configuration of the IUT. A test of the IUT's capability of receiving a link identification request is
covered in subclause 5.4.3.2.
NOTE 3: LT1 shall wait for the receipt of restart complete from the IUT before sending restart complete.
NOTE 4: To reach the initial state of the IUT PSTN user port FSM as defined in subclause 5.1.5, 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 AN6 (Port Blocked).
NOTE 5: If the PICS items N11 and N12 are set to YES, this part of the system start-up procedure
appears twice, once for the ISDN-BA port and once for the ISDN-PRA port. To reach the initial
state of the IUT ISDN-BA user port FSM and/or the ISDN-PRA 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 18
ETS 300 347-5: April 1999
PICS item description:
N11: ISDN-BA ports supported;
N12: ISDN-PRA ports supported;
M2: PSTN ports supported;
N9: Multiple link V5.2 interface.
NOTE 3: 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 start-up (refer to
subclause 5.1.6).
NOTE 4: At STARTUP the LT1 will reject all request on accelerated port state alignment by
respond with the control message UBA-rejected (see subclause 5.1.6).
Depending on the setting of the PICS items, the start-up procedure is described in figure 3. This flow
diagram describes the test step called STARTUP_LE.
4.3.1.2 Common control protocol (system management)
The contents of this subclause are identical to subclause 4.3.1.2 of ETS 300 324-5 [1].
4.3.1.3 Control protocol (PSTN port FSM)
The contents of this subclause are identical to subclause 4.3.1.3 of ETS 300 324-5 [1] with the following
replacements:
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.
If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATION
message. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.
NOTE: This results in a state transition of the PSTN protocol as well. The PSTN protocol of
the affected port is forced to enter the PSTN_path_state LE6.
4.3.1.4 Control protocol (ISDN-BA port FSM)
The contents of this subclause are identical to subclause 4.3.1.4 of ETS 300 324-5 [1] with the following
replacements:
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.
If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATION
message. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.
4.3.1.5 Control protocol (ISDN-PRA port FSM)
Refer to ETS 300 347-1 [2], table 8.
CTRL_ISDNPRA_LE20_10:
On receipt of a PORT CONTROL message containing the control_function_element IE FE204
(block_cmd) the IUT ISDN-PRA port FSM shall enter state LE1.0.
Complete this test step by sending a PORT CONTROL message containing the control_function_element
IE FE209 (TE_out_of_service).
If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATION
message. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.
CTRL_ISDNPRA_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-PRA port FSM shall then enter state LE2.0.

Page 19
ETS 300 347-5: April 1999
4.3.1.6 PSTN protocol
The contents of this subclause are identical to subclause 4.3.1.5 of ETS 300 324-5 [1] with the following
replacements:
PSTN_LEx_6:
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.
If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATION
message. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.
PSTN_LE1_2:
On receipt of a terminating call request (FE-establish_request) the IUT protocol shall send an
ALLOCATION message.
On receipt of a DE-ALLOCATION message the IUT 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.
If there is any V5.2 time slot allocated to the affected port, the IUT shall send a DE-ALLOCATION
message. In that case this test step is completed by sending a DE-ALLOCATION COMPLETE message.
4.3.1.7 Link control protocol
LINK_LE20_10:
On receipt of a LINK CONTROL message containing the link_control_function IE FE304 (link_block_cmd)
the IUT link control FSM shall enter state LE1.0.
NOTE: The blocking of a V5.2 link results in a protection switching (if possible) of all C-paths
carried by that link.
LINK_LE10_20:
On receipt of a LINK CONTROL message containing the link_control_function IE FE302
(link_unblock_req) the IUT shall respond with the LINK CONTROL message containing the
link_control_function IE FE301 (link_unblock_ack) and then enter state LE2.0.
4.3.1.8 BCC protocol
BCC_NULL:
The purpose of this test step is to get the IUT to state LEBcc0 (Bcc null).
BCC_ALLOC_WAIT:
The purpose of this test step is to get the IUT to state LEBcc1 (Bcc waiting allocation).
On receipt of an originating/terminating call attempt, the IUT shall send an ALLOCATION message
containing the originating UP referenced in the UP_ID IE.
BCC_CONN:
The purpose of this test step is to allocate a timeslot in V5.2 interface.
On receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing the
originating UP referenced in the UP_ID IE.
Complete the test step by sending an ALLOCATION COMPLETE message.
BCC_DEALLOC_WAIT:
The purpose of this test step is to get the IUT to state LEBcc3 (Bcc waiting de-allocation).
On receipt of an originating call attempt, the IUT shall send an ALLOCATION message containing the
originating UP referenced in the UP_ID IE.
On receipt of an ALLOCATION COMPLETE message, the IUT shall respond to the originating call
attempt.
On receipt of a user release request, the IUT shall send a DE-ALLOCATION message containing the
originating UP referenced in the IE UP_ID IE and the allocated V5 TS referenced in the V5_TS_ID IE.

Page 20
ETS 300 347-5: April 1999
BCC_ALLOC_ABORT:
The purpose of this test step is to get the IUT to state LEBcc2 (Bcc allocation abort).
On receipt of MDU-BCC(Allocation request), the IUT shall send an ALLOCATION message containing the
terminating UP referenced in the UP_ID IE.
On receipt of MDU-BCC(De-allocation request), the IUT shall send a DE-ALLOCATION message
containing the terminating UP referenced in the UP_ID IE and the allocated V5 TS referenced in the
V5_TS_ID IE.
BCC_AUDIT_WAIT:
The purpose of this test step is to get the IUT to state LEBcc4 (Bcc waiting abort).
The IUT shall send an AUDIT message. It is implementation dependent how the AUDIT procedure is
initiated.
BCC_DEALLOC:
The purpose of this test step is to de-allocate a timeslot in V5.2 interface.
4.3.1.9 Protection protocol
PROTECT_SOLEx_0:
On receipt of a RESET SN COM message, the IUT shall send a RESET SN ACK message (IUT
protection FSM enters state SOLE0).
Complete this teststep by waiting for the expiration of timer TSO5.
PROTECT_BACK_TO_INIT1:
On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel
1" and the physical_C-channel_ID IE "TS 16 of primary link", the IUT shall send a SWITCH-OVER COM
message containing the same data.
Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.
PROTECT_BACK_TO_INIT2:
On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel
2" and the physical_C-channel_ID IE "TS 15 of primary link", the IUT shall send a SWITCH-OVER COM
message containing the same data.
Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.
PROTECT_BACK_TO_INIT3:
On receipt of a SWITCH-OVER REQ message containing the logical_C-channel_ID IE "logical C-channel
3" and the physical_C-channel_ID IE "TS 31 of primary link", the IUT shall send a SWITCH-OVER COM
message containing the same data.
Complete the teststep by sending a SWITCH-OVER ACK message containing the same data.
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. All combinations of the test steps defined in subclauses 4.3.1.2 to
4.3.1.9 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 test case 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.9 can be used to create postambles.

Page 21
ETS 300 347-5: April 1999
4.3.4 Status verification
4.3.4.1 PSTN protocol
The contents of this subclause are identical to subclause 4.3.4 of ETS 300 324-5 [1] with the following
replacements:
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 shall send a DISCONNECT and a DE-ALLOCATION 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 and a DE-ALLOCATION 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 shall send a DISCONNECT and a DE-ALLOCATION 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 and a DE-ALLOCATION COMPLETE
message (IUT PSTN protocol enters the PSTN_path_state LE1).
4.3.4.2 Link control FSM
LINK_CHECK_ID:
On receipt of a message containing the link_control_function IE FE-IDReq (link_identification_req) the IUT
shall send a message containing the link_control_function IE FE-IDAck (link_identification_ack) and
frames with S bit set to zero.
a7
On receipt of a message containing the link_control_function IE FE-IDRel (link_identification_rel) the IUT
shall send frames with S bit set to one.
a7
4.3.5 Common test steps
The contents of this subclause are identical to subclause 4.3.5 of ETS 300 324-5 [1].
4.4 Defaults
The contents of this subclause are identical to subclause 4.4 of ETS 300 324-5 [1].
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs)
4.5.1 ASPs
The contents of this subclause are identical to subclause 4.5.1 of ETS 300 324-5 [1].
4.5.2 PDUs
4.5.2.1 Common control protocol
The contents of this subclause are identical to subclause 4.5.2.1 of ETS 300 324-5 [1].
4.5.2.2 Port control protocol
The contents of this subclause are identical to subclause 4.5.2.2 of ETS 300 324-5 [1].

Page 22
ETS 300 347-5: April 1999
4.5.2.3 PSTN protocol
The contents of this subclause are identical to subclause 4.5.2.3 of ETS 300 324-5 [1].
4.5.2.4 Link control protocol
link_ctrl
link_ctrl_ack
4.5.2.5 BCC protocol
bcc_allocation
bcc_allocation_complete
bcc_allocation_reject
bcc_deallocation
bcc_deallocation_complete
bcc_deallocation_reject
bcc_audit
bcc_audit_complete
bcc_an_fault
bcc_an_fault_ack
bcc_protocol_error
4.5.2.6 Protection protocol
protect_switch_over_req
protect_switch_over_
...