SIST ETS 300 347-3:1997

Signalling Protocols and Switching (SPS) - V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN side)

Abstract Test Suite specification (ATS in TTCN) and protocol implementation extra information for testing (PIXIT) proforma V5.2 interface for support of Access Network with up to N interfaces each at 2048 kBit/s with concentration capability within the Access Network

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

General Information

• Status: Published
• Publication Date: 31-Oct-1997
• ICS: 33.040.30 - Switching and signalling systems
• ICS: 35.100.30 - Network 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 347-3 ed.1 (1996-02) - V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN side)

Standards Content (Sample)

SLOVENSKI STANDARD
01-november-1997
Signalizacijski protokoli in komutacija (SPS) - Vmesniki "V" pri digitalnih krajevnih
centralah (LE) - Vmesnik V5.2 za podporo dostopovnega omrežja (AN) - 3. del:
Zgradba preskušalnega niza in namen preskušanja (TSS&TP) za omrežno plast na
strani dostopovnega omrežja (AN)
Signalling Protocols and Switching (SPS) - V interfaces at the digital Local Exchange
(LE); V5.2 interface for the support of Access Network (AN); Part 3: Test Suite Structure
and Test Purposes (TSS&TP) specification for the network layer (AN side)
Ta slovenski standard je istoveten z: ETS 300 347-3 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
35.100.30 Omrežni sloj Network layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 347-3
TELECOMMUNICATION February 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03003.4-1
ICS: 33.020, 33.080, 35.100.30
V interface, V5 interface, PSTN, ISDN, AN, TSS&TP, testing, layer 3
Key words:
Signalling Protocols and Switching (SPS);
V interfaces at the digital Local Exchange (LE);
V5.2 interface for the support of Access Network (AN);
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network layer (AN side)
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 1996. All rights reserved.

Page 2
ETS 300 347-3: February 1996
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 3
ETS 300 347-3: February 1996
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.13
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 .14
4.2.2.6.3 Timers and counters of the Link control protocol .14
4.2.2.6.4 Timers and counters of the BCC protocol .14
4.2.2.6.5 Timers and counters of the Protection protocol.14
4.2.2.6.6 Timers and counters of the AN system management .14
4.3 Test step structure.15
4.3.1 State transitions.15
4.3.1.1 Start-up of V5.2 interface.15
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 Control protocol (ISDN-PRA port FSM).17
4.3.1.6 PSTN protocol .17
4.3.1.7 Link control protocol .17
4.3.1.8 BCC protocol .18
4.3.1.9 Protection protocol.18
4.3.2 Preconditions.18
4.3.3 Preambles .18
4.3.4 Postambles.18
4.3.5 Status verification .18
4.3.5.1 PSTN protocol .18
4.3.5.2 Link control FSM.19
4.3.6 Common test steps .19
4.4 Defaults.19
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs).19
4.5.1 ASPs .19
4.5.2 PDUs .19
4.5.2.1 Common control protocol .19
4.5.2.2 Port control protocol.19
4.5.2.3 PSTN protocol .19

Page 4
ETS 300 347-3: February 1996
4.5.2.4 Link control protocol. 19
4.5.2.5 BCC protocol. 19
4.5.2.6 Protection 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.1.3 Link control protocol. 20
4.5.3.1.4 BCC protocol. 20
4.5.3.1.5 Protection protocol . 20
4.5.3.2 Single octet information elements. 20
4.5.3.2.1 Control protocol. 20
4.5.3.2.2 PSTN protocol. 20
4.5.3.2.3 Link control protocol. 20
4.5.3.2.4 BCC protocol. 20
4.5.3.2.5 Protection protocol . 21
4.6 Timers and counters of the Abstract Test Suite (ATS) . 21
5 Test Purposes (TPs). 22
5.1 Introduction. 22
5.1.1 Test purpose naming convention . 22
5.1.2 Source of test purpose definition . 23
5.1.3 Test strategy . 23
5.1.3.1 Common control protocol. 23
5.1.3.2 Port control protocol. 23
5.1.3.3 PSTN protocol. 23
5.1.3.4 Link control protocol. 24
5.1.3.5 BCC protocol. 24
5.1.3.6 Protection protocol . 24
5.1.4 Requirements not covered by test purposes . 25
5.1.5 Initial states. 25
5.1.6 Test and data configuration requirements. 25
5.2 Control protocol. 26
5.2.1 Basic interconnection tests (V5NWKAN/CTRL/IT). 26
5.2.2 Capability tests (V5NWKAN/CTRL/CA). 26
5.2.3 Valid behaviour tests (V5NWKAN/CTRL/BV). 26
5.2.3.1 V5NWKAN/CTRL/BV/COM . 26
5.2.3.2 V5NWKAN/CTRL/BV/PORT. 26
5.2.3.2.1 V5NWKAN/CTRL/BV/PORT/TRANS. 26
5.2.3.2.2 V5NWKAN/CTRL/BV/PORT/PSTN . 26
5.2.3.2.3 V5NWKAN/CTRL/BV/PORT/ISDNBA . 26
5.2.3.2.4 V5NWKAN/CTRL/BV/PORT/ISDNPRA. 27
5.2.4 Inopportune behaviour tests (V5NWKAN/CTRL/BO) . 28
5.2.4.1 V5NWKAN/CTRL/BO/COM . 28
5.2.4.2 V5NWKAN/CTRL/BO/PORT . 28
5.2.4.2.1 V5NWKAN/CTRL/BO/PORT/TRANS . 28
5.2.4.2.2 V5NWKAN/CTRL/BO/PORT/PSTN. 28
5.2.4.2.3 V5NWKAN/CTRL/BO/PORT/ISDNBA. 28
5.2.4.2.4 V5NWKAN/CTRL/BO/PORT/ISDNPRA . 29
5.2.5 Invalid behaviour tests (V5NWKAN/CTRL/BI). 29
5.2.6 Timer expiry and counter mismatch tests (V5NWKAN/CTRL/TI). 29
5.3 PSTN protocol. 29
5.4 Link control protocol . 29
5.4.1 Basic interconnection tests (V5NWKAN/LINK/IT) . 29
5.4.2 Capability tests (V5NWKAN/LINK/CA) . 29
5.4.3 Valid behaviour tests (V5NWKAN/LINK/BV) . 30
5.4.3.1 V5NWKAN/LINK/BV/TRANS . 30
5.4.3.2 V5NWKAN/LINK/BV/LINK . 30
5.4.4 Inopportune behaviour tests (V5NWKAN/LINK/BO). 40
5.4.4.1 V5NWKAN/LINK/BO/TRANS. 40
5.4.4.2 V5NWKAN/LINK/BO/LINK. 41
5.4.5 Invalid behaviour tests (V5NWKAN/LINK/BI) . 43
5.4.5.1 V5NWKAN/LINK/BI/TRANS. 43

Page 5
ETS 300 347-3: February 1996
5.4.6 Timer expiry and counter mismatch tests (V5NWKAN/LINK/TI).44
5.4.6.1 V5NWKAN/LINK/TI/TRANS .44
5.5 BCC protocol.44
5.5.1 Basic interconnection tests (V5NWKAN/BCC/IT) .45
5.5.2 Capability tests (V5NWKAN/BCC/CA) .45
5.5.3 Valid behaviour tests (V5NWKAN/BCC/BV) .46
5.5.4 Inopportune behaviour tests (V5NWKAN/BCC/BO).49
5.5.5 Invalid behaviour tests (V5NWKAN/BCC/BI) .50
5.5.6 Timer expiry and counter mismatch tests (V5NWKAN/BCC/TI).52
5.6 Protection protocol.52
5.6.1 Basic interconnection tests (V5NWKAN/PROTECT/IT).52
5.6.2 Capability tests (V5NWKAN/PROTECT/CA) .53
5.6.3 Valid behaviour tests (V5NWKAN/PROTECT/BV).53
5.6.4 Inopportune behaviour tests (V5NWKAN/PROTECT/BO).58
5.6.5 Invalid behaviour tests (V5NWKAN/PROTECT/BI).58
5.6.6 Timer expiry and counter mismatch tests (V5NWKAN/PROTECT/TI) .60
Annex A (informative): Bibliography.62
History.63

Page 6
ETS 300 347-3: February 1996
Blank page
Page 7
ETS 300 347-3: February 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunication Standard Institute (ETSI).
This ETS is part 3 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: "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: 1 March 1996
Date of latest announcement of this ETS (doa): 31 May 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1996
Date of withdrawal of any conflicting National Standard (dow): 30 November 1996

Page 8
ETS 300 347-3: February 1996
Blank page
Page 9
ETS 300 347-3: February 1996
1 Scope
This third part of ETS 300 347 contains the Test Suite Structure and Test Purposes (TSS&TP) for the
network layer and parts of the system management of the Access Network (AN) 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
AN and a Local Exchange (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-3 [1]. The two documents share a common
format and clauses within ETS 300 324-3 [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-3 (1995): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network layer (AN side)".
[2] ETS 300 347-1 (1994): "Signalling Protocols and Switching (SPS); 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): "Signalling Protocols and Switching (SPS); 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-3: February 1996
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-3 [1] and 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].
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].
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 Statements
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-3: February 1996
4 Test Suite Structure (TSS)
4.1 Overview
Figure 1 shows the structure of the V5.2 network layer test suite.
V5NW KAN
CTRL IT
CA
BV
COM TRANS/PROTOCOL
SYS_M AN/ REST
SYS_M AN REVY
PO RT
TRANS/PRO TO CO L
PSTN
ISDN-BA
IS D N -P R A
BO COM TRANS/PRO TO CO L
SYS_M AN REVY
PO RT
TRANS/PRO TO CO L
PSTN
IS D N -B A
ISDN-PRA
BI
TRANS/PRO TO CO L
COM
TRANS/PRO TO CO L
PO RT
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
LIN K
IT
CA
BV TRANS/PRO TO CO L
LINK CTRL
BO
TRANS/PRO TO CO L
LINK CTRL
BI
TRANS/PROTOCOL
TI TRANS/PRO TOCOL
BCC
IT
CA
BV
BO
BI
TI
PRO TECT
IT
CA
BV
BO
BI
TI
Figure 1: Network Layer AN test suite structure

Page 12
ETS 300 347-3: February 1996
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_AN
UNI
FE DL-DATA
AN_PSTN
AN_PSTN_UP
AN_RM
MDU
PH-DATA
MDU
MDU
DL-DATA
MPH
AN_BCC
V5
AN_PSTN_port_FSM
MDL
AN_V5_FSM
AN_SYS AN_DL
MDU DL-DATA
AN_PROT
(ANI)
AN_ISDN_port_FSM
MDU DL-DATA
AN_LINK
FE
PH
MDU
FE
DL-DATA
AN_CTRL
AN_ISDN_UP
MPH
AN_LINK_CTRL_FSM
Figure 2: Network layer AN - protocol entity overview
Table 1: Names used in figure 2 that correspond to ETS 300 347-1 [2]
Network layer Protocol entity defined in Protocol group reference
protocol entity ETS 300 347-1 [2]
AN_PSTN_UP AN_PSTN_user_port 4.2.1.1
AN_PSTN_port_FSM AN_PSTN_user_port_FSM 4.2.1.1
AN_ISDN_port_FSM AN_ISDN_BA_user_port_FSM 4.2.1.1
AN_ISDN_PRA_user_port_FSM
AN_ISDN_UP AN_ISDN_BA_user_port 4.2.1.1
AN_ISDN_PRA_user_port
AN_CTRL AN_control_protocol 4.2.1.1
AN_SYS AN_system_management 4.2.1.1
AN_PSTN AN_PSTN_protocol 4.2.1.2
AN_LINK AN_link_control_protocol 4.2.1.3
AN_LINK_CTRL_FSM AN_link_control_FSM 4.2.1.3
AN_RM AN_rescource_manager 4.2.1.4
AN_BCC AN_BCC_protocol 4.2.1.4
AN_PROT AN_protection_protocol 4.2.1.5

Page 13
ETS 300 347-3: February 1996
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-3 [1] with the following
additions for the ISDN-PRA user port Finite State Machine (FSM).
Depending on provisioning the following configuration is tested:
AN_ISDN-PRA_user_port: The blocking, blocking request and co-ordinated unblocking procedures of the
AN_ISDN-PRA_user_port_FSM are verified in the test group V5NWKAN/CTRL/BV/PORT/
ISDNPRA and V5NWKAN/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-3 [1].
4.2.1.3 Link control protocol
All tests in the Link control protocol (V5NWKAN/LINK) test group are intended to verify as thoroughly as
possible the various procedures of the AN_link_control_protocol entity.
Depending on provisioning the following configurations are covered:
AN_link_control_protocol: The normal and exceptional procedures of the AN_link_control_protocol are
verified in the test groups V5NWKAN/LINK/BV/TRANS, V5NWKAN/LINK/BO/TRANS and
V5NWKAN/LINK/TI/TRANS.
The error handling procedures are verified in the test group V5NWKAN/LINK/BI/TRANS.
AN_link_control_FSM: The link blocking, link blocking request, co-ordinated link unblocking and link
identification procedures of the AN_link_control_FSM are verified in the test groups
V5NWKAN/LINK/BV/LINK and V5NWKAN/LINK/BO/LINK.
4.2.1.4 Bearer Channel Connection (BCC) protocol
All tests in the BCC protocol (V5NWKAN/BCC) test group are intended to verify as thoroughly as possible
the various procedures of the AN_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.
4.2.1.5 Protection protocol
All tests in the Protection protocol (V5NWKAN/PROTECT) test group are intended to verify as thoroughly
as possible the various procedures of the AN 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 AN side;
- normal and exceptional dedicated protection switch-over procedure initiated by OS AN;
- normal and exceptional switch-over procedure requested by AN side;
- error handling procedures.
Page 14
ETS 300 347-3: February 1996
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-3 [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-3 [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-3 [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-3 [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-3 [1].
4.2.2.6 Timer expiry and counter mismatch tests (TI)
The contents of this subclause are identical to subclause 4.2.2.6 of ETS 300 324-3 [1].
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-3 [1].
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-3 [1].
4.2.2.6.3 Timers and counters of the Link control protocol
Refer to the 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 the ETS 300 347-1 [2], table 46.
TBCC5 AN fault sent
4.2.2.6.5 Timers and counters of the Protection protocol
Refer to the ETS 300 347-1 [2], table 64.
TSO3 SWITCH-OVER REQ sent
TSO4 RESET SN COM sent
TSO5 RESET SN COM received
Refer to the 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 AN system management
The contents of this subclause are identical to subclause 4.2.2.6.3 of ETS 300 324-3 [1].

Page 15
ETS 300 347-3: February 1996
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);
preconditions (refer to subclause 4.3.2);
preambles (refer to subclause 4.3.3);
postambles (refer to subclause 4.3.4);
status verification (refer to subclause 4.3.5);
common test steps (refer to subclause 4.3.6).
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_AN1_2 is the test step which brings the AN
PSTN protocol FSM from PSTN_path_state AN1 to PSTN_path_state AN2. The state transitions are
declared in the parenthesis (originating state - destination state) which follow the test step names.
Six groups of state transitions are defined:
STARTUP start up the V5 interface and put the Implementation Under Test (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 and N2 (see subclause 6.6.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 shall be set.

Page 16
ETS 300 347-3: February 1996
PICS N11 or N12 = YES PICS N11 and N12 = NO PICS N11 or N12 = YES
PICS N2 = YES PICS N2 = YES PICS N2 = NO
AN LT1
Variant & interface ID
req var and interface ID req v ar and interface ID req var and interface ID
Note 1
v ar 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 identifica tion rel Link identification rel
Restart
Restart Req Restart Req
Restart Complete Restart Com plete
Note 3
Restart Complete Restart Com plete
PSTN port FSM
Unblock req Unblock req
Note 4
Block cm d Block cm d
ISDN port FSM
Unblock req Unblock req
Note 5
Block cm d Block cm d
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_AN flow diagram

Page 17
ETS 300 347-3: February 1996
PICS item description:
N11: ISDN-BA ports supported;
N12: ISDN-PRA ports supported;
N2: 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 start-up procedure is described in figure 3. This flow
diagram describes the test step called STARTUP_AN.
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-3 [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-3 [1].
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-3 [1].
4.3.1.5 Control protocol (ISDN-PRA port FSM)
Refer to the ETS 300 347-1 [2], table 8.
CTRL_ISDNPRA_AN10_10
On receipt of a local unblock_req (MPH-UBR) the IUT shall send a message containing the
control_function_element IE FE202 (unblock_req).
On receipt of a PORT CONTROL message containing the control_function_element IE FE203
(block_cmd) the IUT ISDN-PRA user port FSM shall re-enter state AN1.0.
CTRL_ISDNPRA_AN20_10
On receipt of a PORT CONTROL message containing the control_function_element IE FE203
(block_cmd) the IUT shall enter state AN1.0.
CTRL_ISDNPRA_AN10_20
On receipt of a PORT CONTROL message containing the control_function_element IE FE201
(unblock_req) the IUT shall respond with the PORT CONTROL message containing the
control_function_element IE FE202 (unblock_ack) and then enter state AN2.0.
4.3.1.6 PSTN protocol
The contents of this subclause are identical to subclause 4.3.1.5 of ETS 300 324-3 [1].
4.3.1.7 Link control protocol
LINK_AN20_10
On receipt of a LINK CONTROL message containing the link_control_function IE FE303 (link_block_cmd)
the IUT link control FSM shall enter state AN1.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_AN10_20
On receipt of a LINK CONTROL message containing the link_control_function IE FE301
(link_unblock_req) the IUT shall respond with the LINK CONTROL message containing the
link_control_function IE FE302 (link_unblock_ack) and then enter state AN2.0.

Page 18
ETS 300 347-3: February 1996
4.3.1.8 BCC protocol
BCC_CONN
On receipt of an ALLOCATION message, the IUT shall send an ALLOCATION COMPLETE message.
BCC_REL
On receipt of a DE-ALLOCATION message, the IUT shall send a DE-ALLOCATION COMPLETE
message.
BCC_FAULT
On receipt of an ALLOCATION message, the IUT shall send an ALLOCATION COMPLETE message. On
detection of "AN internal failure" of the allocated connection, the IUT shall send an AN FAULT message
containing the UP_ID IE, the ISDN_port_channel_ID (only for ISDN application) and the V5_TS_ID IE.
4.3.1.9 Protection protocol
PROTECT_SOANx_0
On receipt of a RESET SN COM message, the IUT shall send a RESET SN ACK message (IUT
protection FSM enters state SOAN0).
Complete this teststep by waiting for the expiration of timer TSO5.
PROTECT_BACK_TO_INIT1
On receipt of a SWITCH-OVER COM 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 ACK
message containing the same data.
PROTECT_BACK_TO_INIT2
On receipt of a SWITCH-OVER COM 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 ACK
containing the same data.
PROTECT_BACK_TO_INIT3
On receipt of a SWITCH-OVER COM 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 ACK
containing the same data.
4.3.2 Preconditions
The contents of this subclause are identical to subclause 4.3.2 of ETS 300 324-3 [1].
4.3.3 Preambles
The preamble test step group contains the test steps needed for initialization of the IUT before testing the
particular test purpose. All combinations of the test steps defined in subclause 4.3.1.2 to subclause
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.4 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.
4.3.5 Status verification
4.3.5.1 PSTN protocol
The contents of this subclause are identical to subclause 4.3.5 of ETS 300 324-3 [1].

Page 19
ETS 300 347-3: February 1996
4.3.5.2 Link control FSM
LINK_CHECK_ID (Path active)
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.6 Common test steps
The contents of this subclause are identical to subclause 4.3.6 of ETS 300 324-3 [1].
4.4 Defaults
The contents of this subclause are identical to subclause 4.4 of ETS 300 324-3 [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-3 [1].
4.5.2 PDUs
4.5.2.1 Common control protocol
The contents of this subclause are identical to subclause 4.3.4 of ETS 300 324-3 [1].
4.5.2.2 Port control protocol
The contents of this subclause are identical to subclause 4.3.4 of ETS 300 324-3 [1].
4.5.2.3 PSTN protocol
The contents of this subclause are identical to subclause 4.3.4 of ETS 300 324-3 [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
Page 20
ETS 300 347-3: February 1996
4.5.2.6 Protection protocol
protect_switch_over_req
protect_switch_over_com
protect_os_switch_over_com
protect_switch_over_ack
protect_switch_over_reject
protect_protocol_error
protect_reset_sn_com
protect_reset_sn_ack
4.5.3 Information elements
4.5.3.1 Variable length information elements
4.5.3.1.1 Control protocol
The contents of this subclause are identical to subclause 4.5.3.1.1 of ETS 300 324-3 [1].
4.5.3.1.2 PSTN protocol
The contents of this subclause are identical to subclause 4.5.3.1.2 of ETS 300 324-3 [1].
4.5.3.1.3 Link control protocol
link_control_function
4.5.3.1.4 BCC protocol
bcc_user_port_ident
bcc_ISDN_port_channel_ident
bcc_V5-time_slot_ident
bcc_multi_slot_map
bcc_reject_cause
bcc_protocol_error_cause
bcc_connection_incomplete
4.5.3.1.5 Protection protocol
protect_sequence_number
protect_logical_c_channel_ident
protect_physical_c_channel_ident
protect_rejection_cause
protect_protocol_error_cause
4.5.3.2 Single octet information elements
4.5.3.2.1 Control protocol
The contents of this subclause are identical to subclause 4.5.3.2.1 of ETS 300 324-3 [1].
4.5.3.2.2 PSTN protocol
The contents of this subclause are identical to subclause 4.5.3.2.2 of ETS 300 324-3 [1].
4.5.3.2.3 Link control protocol
There are no single octet information elements defined within the Link control protocol.
4.5.3.2.4 BCC protocol
There are no single octet information elements defined within the BCC protocol.

Page 21
ETS 300 347-3: February 1996
4.5.3.2.5 Protection protocol
There are no single octet information elements defined within the Protection protocol.
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 347-1 [2]:
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.
Table 2 gives the ATS timers which are used in addition to those defined in subclause 4.6 of
ETS 300 324-3 [1].
Table 2: ATS timer values and references to ETS 300 347-1 [2]
ATS timer name ATS timer value ETS timer name Reference to
[s] ETS 300 347-1 [2]
LCTO1_max 1,2 LCTO1 clause 16, table 23
LCTO1_min 0,9
TPERS_max 0,15 - 30 Persistence subclause 16.1.3
TPERS_min 0,05 - 22,5 check timer
TBCC1_max 1,8 TBCC1 clause 17, table 46
TBCC2_max 2,4 TBCC2 clause 17, table 46
TBCC3_max 2,4 TBCC3 clause 17, table 46
TBCC4_max 1,8 TBCC4 clause 17, table 46
TBCC5_max 0,6 - 1,8 TBCC5 clause 17, table 46
TBCC5_min 0,45 - 1,2
TSO1_max 1,8 TSO1 clause 18, table 64
TSO2_max 1,8 TSO2 clause 18, table 64
TSO3_max 1,8 TSO3 clause 18, table 64
TSO3_min 0,45
TSO4_max 24 TSO4 clause 18, table 64
TSO4_min 18
TSO5_max 12 TSO5 clause 18, table 64
TSO5_min 9
Table 3 gives the ATS counters which are used in addition to those defined in subclause 4.6 of
ETS 300 324-3 [1].
Table 3: Protocol counter values and references to ETS 300 347-1 [2]
ATS counter ATS counter Explanation Reference to
name value ETS 300 347-1 [2]
NLCO1 1 Allowed number of repetions of the LINK clause 16, table 23
CONTROL message
NBCC5 1 Allowed number of repetions of the AN FAULT clause 17, table 46
message
NSO3 1 Allowed number of repetions of the SWITCH- clause 18, table 64
OVER REQ message
NSO4 1 Allowed number of repetions of the RESET SN clause 18, table 64
COM message
Page 22
ETS 300 347-3: February 1996
5 Test Purposes (TPs)
5.1 Introduction
The contents of this subclause are identical to subclause 5.1 of ETS 300 324-3 [1] and also valid for the
V5.2 interface.
5.1.1 Test purpose naming convention
The identifier of a test purpose is built according to the scheme described in table 4.
Table 4: Test purpose identifier naming convention scheme
Identifier: TP
= type of protocol: 1 Control protocol
2 PSTN protocol
3 Link control protocol
4 BCC protocol
5 Protection protocol
= category: 1 IT, Basic Interconnection Tests
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
6 ISDN-PRA
7 Link control
_ (underscore) Not relevant
= test purpose type: S Single
C Combined
= state (0-9)
M Multiple state transition
_ (underscore) Not relevant
= substate (0-9)
_ (underscore) Not relevant
= sequential number (01-99)

Page 23
ETS 300 347-3: February 1996
5.1.2 Source of test purpose definition
The TPs were developed based on ETS 300 347-1 [2], clauses 14 to 18 and annexes A to E.
5.1.3 Test strategy
5.1.3.1 Common control protocol
To achieve a maximum of test coverage with an appropriate number of TPs the following se
...