SIST ETS 300 324-3 E2:2003
(Main)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)
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)
TSSTP
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo dostopovnemu omrežju (AN) – 3. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) – Specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 324-3 E2:
01-RNWREHU-
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 3. del: Zgradba preskušalnega niza in nameni
preskušanja (TSS&TP) – Specifikacija za omrežno plast na strani dostopovnega
omrežja (AN)
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)
Ta slovenski standard je istoveten z: ETS 300 324-3 E2
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
SIST ETS 300 324-3 E2: en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
DRAFT
EUROPEAN pr ETS 300 324-3
TELECOMMUNICATION December 1997
STANDARD Second Edition
Source: SPS Reference: RE/SPS-03055-3
ICS: 33.020
Key words: V interface, V5 interface, AN, ISDN, layer 3, LE, PSTN, testing, TSS&TP
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)
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
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 1997. All rights reserved.
Page 2
Draft prETS 300 324-3: December 1997
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
Draft prETS 300 324-3: December 1997
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 AN 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 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 Port control protocol.19
4.3.5.3 Common control protocol .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
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 .20
4.5.3.2.1 Control protocol .20
4.5.3.2.2 PSTN protocol .20
4.6 Timers and counters of the Abstract Test Suite (ATS).20
Page 4
Draft prETS 300 324-3: December 1997
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 (V5NWKAN/CTRL/IT). 24
5.2.2 Capability tests (V5NWKAN/CTRL/CA). 24
5.2.3 Valid behaviour tests (V5NWKAN/CTRL/BV). 24
5.2.3.1 V5NWKAN/CTRL/BV/COM . 24
5.2.3.1.1 V5NWKAN/CTRL/BV/COM/TRANS . 24
5.2.3.1.2 V5NWKAN/CTRL/BV/COM/REST. 25
5.2.3.1.3 V5NWKAN/CTRL/BV/COM/REVY. 25
5.2.3.2 V5NWKAN/CTRL/BV/PORT. 27
5.2.3.2.1 V5NWKAN/CTRL/BV/PORT/TRANS. 27
5.2.3.2.2 V5NWKAN/CTRL/BV/PORT/PSTN . 27
5.2.3.2.3 V5NWKAN/CTRL/BV/PORT/ISDNBA . 29
5.2.4 Inopportune behaviour tests (V5NWKAN/CTRL/BO) . 32
5.2.4.1 V5NWKAN/CTRL/BO/COM . 32
5.2.4.1.1 V5NWKAN/CTRL/BO/COM/TRANS. 32
5.2.4.1.2 V5NWKAN/CTRL/BO/COM/REVY . 32
5.2.4.2 V5NWKAN/CTRL/BO/PORT . 33
5.2.4.2.1 V5NWKAN/CTRL/BO/PORT/TRANS . 33
5.2.4.2.2 V5NWKAN/CTRL/BO/PORT/PSTN. 33
5.2.4.2.3 V5NWKAN/CTRL/BO/PORT/ISDNBA. 33
5.2.5 Invalid behaviour tests (V5NWKAN/CTRL/BI). 34
5.2.5.1 V5NWKAN/CTRL/BI/COM. 34
5.2.5.1.1 V5NWKAN/CTRL/BI/COM/TRANS. 34
5.2.5.2 V5NWKAN/CTRL/BI/PORT . 35
5.2.5.2.1 V5NWKAN/CTRL/BI/PORT/TRANS. 35
5.2.6 Timer expiry and counter mismatch tests (V5NWKAN/CTRL/TI). 36
5.2.6.1 V5NWKAN/CTRL/TI/COM. 36
5.2.6.1.1 V5NWKAN/CTRL/TI/COM/TRANS. 36
5.2.6.2 V5NWKAN/CTRL/TI/PORT . 36
5.2.6.2.1 V5NWKAN/CTRL/TI/PORT/TRANS . 36
5.3 PSTN protocol. 37
5.3.1 Basic interconnection tests (V5NWKAN/PSTN/IT). 37
5.3.2 Capability tests (V5NWKAN/PSTN/CA) . 37
5.3.3 Valid behaviour tests (V5NWKAN/PSTN/BV). 37
5.3.3.1 V5NWKAN/PSTN/BV/0. 38
5.3.3.2 V5NWKAN/PSTN/BV/1. 38
5.3.3.3 V5NWKAN/PSTN/BV/2. 39
5.3.3.4 V5NWKAN/PSTN/BV/3. 40
5.3.3.5 V5NWKAN/PSTN/BV/4. 41
5.3.3.6 V5NWKAN/PSTN/BV/5. 42
5.3.3.7 V5NWKAN/PSTN/BV/6. 43
5.3.3.8 V5NWKAN/PSTN/BV/7. 44
5.3.4 Inopportune behaviour tests (V5NWKAN/PSTN/BO). 45
5.3.4.1 V5NWKAN/PSTN/BO/0 . 45
5.3.4.2 V5NWKAN/PSTN/BO/1 . 46
5.3.4.3 V5NWKAN/PSTN/BO/2 . 46
5.3.4.4 V5NWKAN/PSTN/BO/3 . 47
5.3.4.5 V5NWKAN/PSTN/BO/4 . 47
5.3.4.6 V5NWKAN/PSTN/BO/5 . 48
5.3.4.7 V5NWKAN/PSTN/BO/6 . 48
5.3.4.8 V5NWKAN/PSTN/BO/7 . 49
5.3.5 Invalid behaviour tests (V5NWKAN/PSTN/BI). 49
5.3.5.1 V5NWKAN/PSTN/BI/1 . 49
5.3.5.2 V5NWKAN/PSTN/BI/5 . 51
Page 5
Draft prETS 300 324-3: December 1997
5.3.6 Timer expiry and counter mismatch tests (V5NWKAN/PSTN/TI).52
5.3.6.1 V5NWKAN/PSTN/TI/2.52
5.3.6.2 V5NWKAN/PSTN/TI/3.52
5.3.6.3 V5NWKAN/PSTN/TI/4.52
5.3.6.4 V5NWKAN/PSTN/TI/5.53
5.3.6.5 V5NWKAN/PSTN/TI/7.53
Annex A (informative): Bibliography.54
History.55
Page 6
Draft prETS 300 324-3: December 1997
Blank page
Page 7
Draft prETS 300 324-3: December 1997
Foreword
This draft second edition European Telecommunication Standard (ETS) has been produced by the
Signalling Protocols and Switching (SPS) Technical Committee of the European Telecommunications
Standards Institute (ETSI), and is now submitted for the Public Enquiry phase of the ETSI standards
approval procedure.
This ETS is part 3 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".
Proposed transposition dates
Date of latest announcement of this ETS (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
Page 8
Draft prETS 300 324-3: December 1997
Blank page
Page 9
Draft prETS 300 324-3: December 1997
1 Scope
This third 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 Access Network (AN) 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
AN and a Local Exchange (LE) from different manufacturers over the V5.1 interface. This ETS covers only
the procedures described in ETS 300 324-1 [1].
ISO/IEC 9646-1 [5] 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 of 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 (1996): "Signalling Protocols
and Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 1: V5.1 interface
specification".
[2] ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS)
proforma".
[3] ETS 300 297 (1995): "Integrated Services Digital Network (ISDN); Access digital
section for ISDN basic access".
[4] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference Model".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
Page 10
Draft prETS 300 324-3: December 1997
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 (ATC): Refer to ISO/IEC 9646-1 [5].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].
current provisioning variant: Identifier for the presently active data set.
data link layer: Refer to ISO 7498 [4].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5].
incorrect IE: Specified IE carrying IE types not defined in ETS 300 324-1 [1].
invalid PSTN IE: PSTN IE not according to national specific requirements.
invalid Protocol Data Unit (PDU): PDU which contains incorrect message format.
invalid PSTN message: PSTN message carrying IEs not according to national specific requirements.
Lower Tester (LT): Refer to ISO/IEC 9646-1 [5].
Network Layer (NWK): Refer to ISO 7498 [4].
Network Termination (NT): An equipment providing the network side at the ISDN user-network interface
for the basic access.
NOTE: This term is used in this ETS to indicate network-terminating aspects of NT1 and NT2.
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 [4].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].
PICS proforma: Refer to ISO/IEC 9646-1 [5].
specified IE: IE identifier defined in ETS 300 324-1 [1].
System Under Test (SUT): Refer to ISO/IEC 9646-1 [5].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
unknown provisioning variant: Identifier for a non-available data set.
unspecified IE: IE identifier not defined in ETS 300 324-1 [1].
valid IE: PSTN IE according to national specific requirements.
valid PSTN message: PSTN message carrying IEs according to national specific requirements.
Page 11
Draft prETS 300 324-3: December 1997
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
DSAP Data link Service Access Point
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
NT Network Termination
NWK Network layer
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PL Permanent Line
PSTN Public Switched Telephone Network
REST Restart
REVY Verify and Reprovisioning
SUT System Under Test
TE Terminal Equipment (ISDN or PSTN)
TI Timer
TP Test Purpose
TSS Test Suite Structure
UNI User Network Interface
Page 12
Draft prETS 300 324-3: December 1997
4 Test Suite Structure (TSS)
4.1 TSS overview
Figure 1 shows the structure of the V5.1 AN side NWK test suite.
V5NW KAN CTRL IT
CA
BV
COM TRANS/PROTOCOL
S YS_MAN/ RES T
SYS_MAN REVY
PORT
TRANS/PROTOCOL
PSTN
IS D N -B A
BO
COM TRANS/PROTOCOL
SYS_MAN REVY
PORT
TRANS/PROTOCOL
PSTN
ISDN-BA
BI
COM TRANS/PROTOCOL
PORT
TRANS/PROTOCOL
TI
COM TRANS/PROTOCOL
PORT
TRANS/PROTOCOL
PSTN
IT
CA
BV
STATE
BO
STATE
BI
STATE
TI
STATE
Figure 1: NWK AN TSS
Page 13
Draft prETS 300 324-3: December 1997
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.
UNI
FE
DL-DATA
AN_PSTN_DL
AN_PSTN
AN_PSTN_UP
MDU-CTRL
MDL PH-DATA
MPH
V5
AN_PSTN_port_FSM
MPH
AN_V5_FSM
AN_SM
MPH
AN_ISDN_port_FSM
MDL
PH-DATA
PH
MDU-CTRL
DL-DATA
FE
AN_CTRL_DL
AN_CTRL
AN_ISDN_UP
Figure 2: Network Layer AN - protocol entity overview
Table 1: Names used in figure 2 that correspond to ETS 300 324-1
NWK protocol entities Protocol entities defined in Protocol group reference
ETS 300 324-1 [1]
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_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
4.2.1 Protocol groups
4.2.1.1 Control protocol
All tests in the Control protocol (V5NWKAN/CTRL) test group are intended to verify as thoroughly as
possible the various procedures of the AN_control_protocol entity. Depending on provisioning the
following configurations are covered:
AN_system_management: the startup, restart, re-provisioning and verification procedures of
normal operation of the AN_system_management (V5NWKAN/CTRL/BV/COM/REST, V5NWKAN/
CTRL/BV/COM/REVY) and V5NWKAN/CTRL/BO/COM/REVY) are tested.
AN_control_protocol: the normal and exceptional procedures of the AN_control_protocol are
verified in the test groups V5NWKAN/CTRL/BV/COM/TRANS, V5NWKAN/CTRL/BO/COM/TRANS,
V5NWKAN/CTRL/TI/COM/TRANS, V5NWKAN/CTRL/BV/PORT/TRANS, V5NWKAN/CTRL/BO/
PORT/TRANS and V5NWKAN/CTRL/TI/PORT/TRANS. Contents of the AN_control_protocol
values are not verified (e.g. the control function ID). The error handling procedures are verified in
test groups V5NWKAN/CTRL/BI/COM/TRANS and V5NWKAN/CTRL/BI/PORT/TRANS.
Page 14
Draft prETS 300 324-3: December 1997
AN_PSTN_user_port: the blocking, blocking request and co-ordinated unblocking procedures of
the AN_PSTN_user_port_FSM are verified in the test group V5NWKAN/CTRL/BV/PORT/PSTN.
The interworking of the AN_PSTN_user_port_FSM and the AN_PSTN_protocol entity is tested via
the AN_system_management.
AN_ISDN-BA_user_port: the blocking, blocking request, co-ordinated unblocking and activation/
deactivation procedures of the AN_ISDN-BA_user_port_FSM are verified in the test group
V5NWKAN/CTRL/BV/PORT/ISDNBA and V5NWKAN/CTRL/BO/PORT/ISDNBA.
4.2.1.2 PSTN protocol
All tests in the PSTN protocol (V5NWKAN/PSTN) test group are intended to verify as thoroughly as
possible the various procedures of the AN_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 error handling procedures;
- the layer 3 error detection procedure;
- 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 test purpose in the valid behaviour test subgroup
cover as far as reasonable the verification of the normal and exceptional procedures of the various 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 subgroup is intended to verify that the IUT is able to react properly in the case of 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
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 subgroup is
intended to verify that the Finite State Machine (FSM) is reacting properly to an expiry of one of the timers
or counter mismatch.
Page 15
Draft prETS 300 324-3: December 1997
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 Subscriber seizure/Line information ESTABLISH sent;
T2 Time out T1 or T2;
T3 DISCONNECT sent;
Tr SIGNAL or PROTOCOL PARAMETER received;
Tt SIGNAL sent.
Refer to ETS 300 324-1 [1], subclause 13.5.5.
S(S) Sequence number to be sent/transmitted in next message;
S(A) Sequence number on the last acknowledged message;
S(R) Sequence number to be received in next message;
M(S) Sequence number of transmitted message;
M(R) Sequence number of next received message.
4.2.2.6.3 Timer expiry and counters of the AN 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);
preconditions (refer to subclause 4.3.2);
preambles (refer to subclause 4.3.3);
postambles (refer to subclause 4.3.4);
status checks (refer to subclause 4.3.5);
common behaviours (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.
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 test
purpose can be performed.
Page 16
Draft prETS 300 324-3: December 1997
PSTN state transitions used to preamble and postamble the PSTN protocol before a test
purpose 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 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 to be set to "Yes".
PICS 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, the startup procedure is described in figure 2. This flow diagram
describes the test step called STARTUP_AN.
PICS M1 = Yes M1 = Yes M1 = No
PICS M2 = Yes M2= No M2 = Yes
AN 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
restart complete restart complete
(note 2)
restart complete restart complete
PSTN port FSM
unblock req unblock req
(note 3)
block cmd block cmd
ISDN port FSM
unblock req unblock req
(note 4)
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 AN6 (Port blocked).
NOTE 4: To reach the initial state of the ISDN-BA user port FSM as defined in subclause 5.1.5, the IUT's
unblocking request is rejected by LT1.
Figure 2: STARTUP_AN flow diagram
Page 17
Draft prETS 300 324-3: December 1997
4.3.1.2 Common control protocol (system management)
Refer to ETS 300 324-1 [1], table 60 and annex C.
CTRL_COM_AN0_1
On AN system startup (reset or initialization) the AN_CONTROL_DL is established between AN and LT1
and the Common and Port control protocol enter the In Service state AN1.
4.3.1.3 Control protocol (PSTN port FSM)
Refer to ETS 300 324-1 [1], table 40.
CTRL_PSTN_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.
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 AN6.
CTRL_PSTN_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.
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 AN1.
4.3.1.4 Control protocol (ISDN-BA port FSM)
Refer to ETS 300 324-1 [1], table 35.
CTRL_ISDNBA_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_ISDNBA_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.
CTRL_ISDNBA_AN20_22
On receipt of a PORT CONTROL message containing the control_function_element IE FE101
(activate_access_req) the IUT shall enter state AN2.2 (access activated) when UNI reach successful
activation and respond with a PORT CONTROL message containing the control_function_element IE
FE104 (access_activated_ind).
CTRL_ISDNBA_AN22_20
On receipt of a PORT CONTROL message containing the control_function_element IE FE105
(deactivate_access_req) the IUT shall enter state AN2.0 (operational deactivated) when UNI reach
successful deactivation and respond with a PORT CONTROL message containing the
control_function_element IE FE106 (access_deactivated_ind).
4.3.1.5 PSTN protocol
Refer to ETS 300 324-1 [1], table 29.
All messages sent within the test steps shall be valid PSTN messages.
PSTN_ANx_6 ≡ CTRL_PSTN_AN20_10 (refer to subclause 4.3.1.3)
On receipt of a PORT CONTROL message containing the control_function_element IE FE203
(block_cmd) the PSTN protocol FSM shall enter the PSTN_path_state AN6.
Page 18
Draft prETS 300 324-3: December 1997
PSTN_AN1_0
On receipt of a MDU_CTRL (restart_req) message the IUT shall send a COMMON CONTROL message
containing the control_function_id IE "restart req". The IUT shall send a COMMON CONTROL message
containing the control_function_id IE "restart complete".
PSTN_AN6_1 ≡ CTRL_PSTN_AN10_20 (refer to subclause 4.3.1.3)
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 the PSTN protocol shall enter the
PSTN_path_state AN1. The subscriber line shall be monitored for a subscriber seizure or line information
condition. If this condition exists the IUT shall send an ESTABLISH message. (refer to ETS 300 324-1 [1],
subclause 13.5.4.2).
PSTN_AN1_2
On receipt of an originating call attempt (FE-subscriber_seizure) the IUT shall send the message
ESTABLISH and enter the PSTN_path_state AN2 (Path initiated by AN).
PSTN_AN2_3
On receipt of a FE-subscriber_release, the IUT shall enter the PSTN_path_state AN3.
PSTN_AN1_4
On receipt of the event FE-line_information, the IUT shall send the ESTABLISH message and enter the
PSTN_path_state AN4.
PSTN_AN1_5
On receipt of the ESTABLISH message the IUT shall send the message ESTABLISH ACK and enter the
PSTN_path_state AN5 (Path active).
PSTN_AN5_7
On receipt of a SIGNAL message containing a faulty sequence number the IUT PSTN protocol shall send
a DISCONNECT message and enter the PSTN_path_state AN7.
4.3.2 Preconditions
The precondition step of a test group applies at the UP via the user interface as a Permanent Line (PL)
condition. This line condition shall be permanent during all tests in that test group.
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.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.4 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.5 Status verification
4.3.5.1 PSTN protocol
Based on ETS 300 324-1 [1], table 29, it is possible to identify the state of the IUT PSTN protocol FSM
with valid PSTN messages.
On receipt of a STATUS ENQUIRY message the IUT shall send a STATUS message and remain the
same state.
Page 19
Draft prETS 300 324-3: December 1997
4.3.5.2 Port control protocol
CHECK_PC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5.1 interface.
Afterwards teststep CTRL_PSTN_AN10_20 (refer to subclause 4.3.1.3) or CTRL_ISDNBA_AN10_20
(refer to subclause 4.3.1.4), depending on the affected port type is applied.
4.3.5.3 Common control protocol
CHECK_CC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5.1 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.6 Common test steps
This test step group shall contain procedures which are used in more than one ATC.
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.
The ASP shall transfer the V5DLaddr to the Data link Service Access Point (DSAP).
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.
Page 20
Draft prETS 300 324-3: December 1997
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.
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_pulse_notification;
pstn_line_infomation;
pstn_state;
pstn_autonomous_signalling_sequence;
pstn_sequence_response.
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.
Page 21
Draft prETS 300 324-3: December 1997
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 repetition of the PORT clause 14, table 59
CONTROL message
N02 1 Allowed number of repetition of the COMMON clause 14, table 60
CONTROL message
N1 1 Number of repetitions of the ESTABLISH clause 13, table 28
message before starting T2
N2 3 Maximum number of tested repetitions of the clause 13, table 28
ESTABLISH message
N3 2 Allowed number of repetitions of the clause 13, table 28
DISCONNECT message
Page 22
Draft prETS 300 324-3: December 1997
5 Test Purposes (TPs)
5.1 Introduction
For each test requirement, a TP is defined.
This subclause details the TPs for the AN side of NWK of the V5.1 interface for each test group and
references to the corresponding ATCs.
At the beginning of each test subgroup the initial state (refer to subclause 5.1.5), the preambles (refer to
subclause 4.3.3) and the postambles (refer to subclause 4.3.4) 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
Draft prETS 300 324-3: December 1997
5.1.2 Source of TP definition
The source for the TPs is 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 abstract test cases 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 states are covered. The TPs cover o
...
SLOVENSKI STANDARD
01-december-2003
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnemu omrežju (AN) – 3. del: Zgradba preskušalnega niza in nameni
preskušanja (TSS&TP) – Specifikacija za omrežno plast na strani dostopovnega
omrežja (AN)
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)
Ta slovenski standard je istoveten z: ETS 300 324-3 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-3
TELECOMMUNICATION April 1999
STANDARD Second Edition
Source: SPS Reference: RE/SPS-09055-3
ICS: 33.020
Key words: V interface, V5 interface, PSTN, ISDN, AN, TSS&TP, testing, layer 3, LE
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)
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-3: 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-3: April 1999
Contents
Foreword . 7
1 Scope. 9
2 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. 15
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 AN
system management. 15
4.3 Test step structure. 15
4.3.1 State transitions . 16
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) . 18
4.3.1.5 PSTN protocol. 18
4.3.2 Preconditions . 19
4.3.3 Preambles. 19
4.3.4 Postambles . 19
4.3.5 Status verification. 19
4.3.5.1 PSTN protocol. 19
4.3.5.2 Port control protocol . 19
4.3.5.3 Common control protocol. 19
4.3.6 Common test steps. 20
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 . 21
4.5.3.2 Single octet information elements. 21
4.5.3.2.1 Control protocol . 21
Page 4
ETS 300 324-3: April 1999
4.5.3.2.2 PSTN protocol .21
4.6 Timers and counters of the Abstract Test Suite (ATS).22
5 Test Purposes (TPs) .23
5.1 Introduction .23
5.1.1 TP naming convention.23
5.1.2 Source of TP definition.24
5.1.3 Test strategy.24
5.1.4 Requirements not covered by TPs.24
5.1.5 Initial state .25
5.1.6 Test and data configuration requirements.25
5.2 Control protocol.25
5.2.1 Basic interconnection tests (V5NWKAN/CTRL/IT) .25
5.2.2 Capability tests (V5NWKAN/CTRL/CA) .25
5.2.3 Valid behaviour tests (V5NWKAN/CTRL/BV) .26
5.2.3.1 V5NWKAN/CTRL/BV/COM .26
5.2.3.1.1 V5NWKAN/CTRL/BV/COM/TRANS.26
5.2.3.1.2 V5NWKAN/CTRL/BV/COM/REST.26
5.2.3.1.3 V5NWKAN/CTRL/BV/COM/REVY.27
5.2.3.2 V5NWKAN/CTRL/BV/PORT .28
5.2.3.2.1 V5NWKAN/CTRL/BV/PORT/TRANS .28
5.2.3.2.2 V5NWKAN/CTRL/BV/PORT/PSTN.29
5.2.3.2.3 V5NWKAN/CTRL/BV/PORT/ISDNBA .31
5.2.4 Inopportune behaviour tests (V5NWKAN/CTRL/BO).34
5.2.4.1 V5NWKAN/CTRL/BO/COM.34
5.2.4.1.1 V5NWKAN/CTRL/BO/COM/TRANS.34
5.2.4.1.2 V5NWKAN/CTRL/BO/COM/REVY .34
5.2.4.2 V5NWKAN/CTRL/BO/PORT.34
5.2.4.2.1 V5NWKAN/CTRL/BO/PORT/TRANS.34
5.2.4.2.2 V5NWKAN/CTRL/BO/PORT/PSTN.34
5.2.4.2.3 V5NWKAN/CTRL/BO/PORT/ISDNBA.35
5.2.5 Invalid behaviour tests (V5NWKAN/CTRL/BI) .35
5.2.5.1 V5NWKAN/CTRL/BI/COM .35
5.2.5.1.1 V5NWKAN/CTRL/BI/COM/TRANS .35
5.2.5.2 V5NWKAN/CTRL/BI/PORT.36
5.2.5.2.1 V5NWKAN/CTRL/BI/PORT/TRANS.36
5.2.6 Timer expiry and counter mismatch tests (V5NWKAN/CTRL/TI) .37
5.2.6.1 V5NWKAN/CTRL/TI/COM.37
5.2.6.1.1 V5NWKAN/CTRL/TI/COM/TRANS.37
5.2.6.2 V5NWKAN/CTRL/TI/PORT.38
5.2.6.2.1 V5NWKAN/CTRL/TI/PORT/TRANS.38
5.3 PSTN protocol.38
5.3.1 Basic interconnection tests (V5NWKAN/PSTN/IT) .38
5.3.2 Capability tests (V5NWKAN/PSTN/CA) .39
5.3.3 Valid behaviour tests (V5NWKAN/PSTN/BV) .39
5.3.3.1 V5NWKAN/PSTN/BV/0 .39
5.3.3.2 V5NWKAN/PSTN/BV/1 .40
5.3.3.3 V5NWKAN/PSTN/BV/2 .41
5.3.3.4 V5NWKAN/PSTN/BV/3 .42
5.3.3.5 V5NWKAN/PSTN/BV/4 .43
5.3.3.6 V5NWKAN/PSTN/BV/5 .44
5.3.3.7 V5NWKAN/PSTN/BV/6 .45
5.3.3.8 V5NWKAN/PSTN/BV/7 .45
5.3.4 Inopportune behaviour tests (V5NWKAN/PSTN/BO).47
5.3.4.1 V5NWKAN/PSTN/BO/0.47
5.3.4.2 V5NWKAN/PSTN/BO/1.47
5.3.4.3 V5NWKAN/PSTN/BO/2.48
5.3.4.4 V5NWKAN/PSTN/BO/3.48
5.3.4.5 V5NWKAN/PSTN/BO/4.49
5.3.4.6 V5NWKAN/PSTN/BO/5.49
5.3.4.7 V5NWKAN/PSTN/BO/6.50
5.3.4.8 V5NWKAN/PSTN/BO/7.51
5.3.5 Invalid behaviour tests (V5NWKAN/PSTN/BI) .51
Page 5
ETS 300 324-3: April 1999
5.3.5.1 V5NWKAN/PSTN/BI/1 . 51
5.3.5.2 V5NWKAN/PSTN/BI/5 . 52
5.3.6 Timer expiry and counter mismatch tests (V5NWKAN/PSTN/TI). 53
5.3.6.1 V5NWKAN/PSTN/TI/2 . 53
5.3.6.2 V5NWKAN/PSTN/TI/3 . 53
5.3.6.3 V5NWKAN/PSTN/TI/4 . 53
5.3.6.4 V5NWKAN/PSTN/TI/5 . 54
5.3.6.5 V5NWKAN/PSTN/TI/7 . 54
Annex A (informative): Bibliography. 55
History . 56
Page 6
ETS 300 324-3: April 1999
Blank page
Page 7
ETS 300 324-3: 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 3 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-3: April 1999
Blank page
Page 9
ETS 300 324-3: April 1999
1 Scope
This third 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 Access Network (AN) 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
AN and a Local Exchange (LE) from different manufacturers over the V5.1 interface. This ETS covers only
the procedures described in ETS 300 324-1 [1].
ISO/IEC 9646-1 [5] 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 of the national PSTN protocol mapping specification.
This ETS contains no requirements concerning NWK tests for Integrated Services Digital Network Basic
Access (ISDN-BA).
2 References
This ETS incorporates by dated and undated reference, provisions from other publications. These
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] ETS 300 297 (1995): "Integrated Services Digital Network (ISDN); Access
Digital Section for ISDN basic rate".
[4] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference Model".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
Page 10
ETS 300 324-3: 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 (ATC): Refer to ISO/IEC 9646-1 [5]
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]
current provisioning variant: Identifier for the presently active data set
data link layer: Refer to ISO 7498 [4]
implementation under test: Refer to ISO/IEC 9646-1 [5]
incorrect information element: Specified information element carrying information element 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 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 [5]
network layer: Refer to ISO 7498 [4]
network termination: Equipment providing the network side at the ISDN user-network interface for the
basic access
NOTE: This term is used in this ETS to indicate network-terminating aspects of NT1 and NT2.
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 [4]
Protocol Implementation Conformance Statement: Refer to ISO/IEC 9646-1 [5]
PICS proforma: Refer to ISO/IEC 9646-1 [5]
specified information element: Information element identifier defined in ETS 300 324-1 [1]
System Under Test (SUT): Refer to ISO/IEC 9646-1 [5]
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5]
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-3: 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
DSAP Data link Service Access Point
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
NT Network Termination
NWK Network layer
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statements
PL Permanent Line
PSTN Public Switched Telephone Network
REST Restart
REVY Verify and Reprovisioning
SUT System Under Test
TE Terminal Equipment (ISDN or PSTN)
TI Timer
TP Test Purpose
TSS Test Suite Structure
UNI User Network Interface
Page 12
ETS 300 324-3: April 1999
4 Test Suite Structure (TSS)
4.1 TSS overview
Figure 1 shows the structure of the V5.1 AN side NWK test suite.
V5NW KAN CTRL IT
CA
BV
COM TRANS/PROTOCOL
S YS_MAN/ RES T
SYS_MAN REVY
PORT
TRANS/PROTOCOL
PSTN
IS D N -B A
BO
COM TRANS/PROTOCOL
SYS_MAN REVY
PORT
TRANS/PROTOCOL
PSTN
ISDN-BA
BI
COM TRANS/PROTOCOL
PORT
TRANS/PROTOCOL
TI
COM TRANS/PROTOCOL
PORT
TRANS/PROTOCOL
PSTN
IT
CA
BV
STATE
BO
STATE
BI
STATE
TI
STATE
Figure 1: NWK AN TSS
Page 13
ETS 300 324-3: 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.
UNI
FE
DL-DATA
AN_PSTN_DL
AN_PSTN
AN_PSTN_UP
MDU-CTRL
MDL PH-DATA
MPH
V5
AN_PSTN_port_FSM
MPH
AN_V5_FSM
AN_SM
MPH
AN_ISDN_port_FSM
MDL
PH-DATA
PH
MDU-CTRL
DL-DATA
FE
AN_CTRL_DL
AN_CTRL
AN_ISDN_UP
Figure 2: Network Layer AN - 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 reference
ETS 300 324-1 [1]
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_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
4.2.1 Protocol groups
4.2.1.1 Control protocol
All tests in the Control protocol (V5NWKAN/CTRL) test group are intended to verify as thoroughly as
possible the various procedures of the AN_control_protocol entity. Depending on provisioning the
following configurations are covered:
AN_system_management: the startup, restart, re-provisioning and verification procedures of normal
operation of the AN_system_management (V5NWKAN/CTRL/BV/COM/REST,
V5NWKAN/ CTRL/BV/COM/REVY) and V5NWKAN/CTRL/BO/COM/REVY) are tested.
AN_control_protocol: the normal and exceptional procedures of the AN_control_protocol are verified in
the test groups V5NWKAN/CTRL/BV/COM/TRANS, V5NWKAN/CTRL/BO/COM/TRANS,
V5NWKAN/CTRL/TI/COM/TRANS, V5NWKAN/CTRL/BV/PORT/TRANS,
V5NWKAN/CTRL/BO/ PORT/TRANS and V5NWKAN/CTRL/TI/PORT/TRANS. Contents of the
AN_control_protocol values are not verified (e.g. the control function ID). The error handling
procedures are verified in test groups V5NWKAN/CTRL/BI/COM/TRANS and
V5NWKAN/CTRL/BI/PORT/TRANS.
Page 14
ETS 300 324-3: April 1999
AN_PSTN_user_port: the blocking, blocking request and co-ordinated unblocking procedures of the
AN_PSTN_user_port_FSM are verified in the test group V5NWKAN/CTRL/BV/PORT/PSTN. The
interworking of the AN_PSTN_user_port_FSM and the AN_PSTN_protocol entity is tested via the
AN_system_management.
AN_ISDN-BA_user_port: the blocking, blocking request, co-ordinated unblocking and
activation/deactivation procedures of the AN_ISDN-BA_user_port_FSM are verified in the test
group V5NWKAN/CTRL/BV/PORT/ISDNBA and V5NWKAN/CTRL/BO/PORT/ISDNBA.
4.2.1.2 PSTN protocol
All tests in the PSTN protocol (V5NWKAN/PSTN) test group are intended to verify as thoroughly as
possible the various procedures of the AN_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 error handling procedures;
- the layer 3 error detection procedure;
- 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 test purpose in the valid behaviour test subgroup
cover as far as reasonable the verification of the normal and exceptional procedures of the various 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 subgroup 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
PDU. An invalid PDU is defined as a syntactically incorrect message and therefore an error indication is
caused.
Page 15
ETS 300 324-3: April 1999
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 subgroup is
intended to verify that the Finite State Machine (FSM) is reacting properly to an expiry of one of the timers
or counter mismatch.
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 Subscriber seizure/Line information ESTABLISH sent
T2 Time out T1 or T2
T3 DISCONNECT sent
Tr SIGNAL or PROTOCOL PARAMETER received
Tt SIGNAL sent
Refer to ETS 300 324-1 [1], subclause 13.5.5.
S(S) Sequence number to be sent/transmitted in next message
S(A) Sequence number on the last acknowledged message
S(R) Sequence number to be received in next message
M(S) Sequence number of transmitted message
M(R) Sequence number of next received message
4.2.2.6.3 Timer expiry and counters of the AN 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)
preconditions (refer to subclause 4.3.2)
preambles (refer to subclause 4.3.3)
postambles (refer to subclause 4.3.4)
status checks (refer to subclause 4.3.5)
common behaviours (refer to subclause 4.3.6)
Page 16
ETS 300 324-3: April 1999
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.
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 test
purpose can be performed.
PSTN state transitions used to preamble and postamble the PSTN protocol before a test
purpose 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 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 to be set to "Yes".
PICS 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, the startup procedure is described in figure 2. This flow diagram
describes the test step called STARTUP_AN.
Page 17
ETS 300 324-3: April 1999
PICS M1 = Yes M1 = Yes M1 = No
PICS M2 = Yes M2= No M2 = Yes
AN 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
restart complete restart complete
(note 2)
restart complete restart complete
PSTN port FSM
unblock req unblock req
(note 3)
block cmd block cmd
ISDN port FSM
unblock req unblock req
(note 4)
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 AN6 (Port blocked).
NOTE 4: To reach the initial state of the ISDN-BA 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
4.3.1.2 Common control protocol (system management)
Refer to ETS 300 324-1 [1], table 60 and annex C.
CTRL_COM_AN0_1
On AN system startup (reset or initialization) the AN_CONTROL_DL is established between AN and LT1
and the Common and Port control protocol enter the In Service state AN1.
4.3.1.3 Control protocol (PSTN port FSM)
Refer to ETS 300 324-1 [1], table 40.
CTRL_PSTN_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.
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 AN6.
Page 18
ETS 300 324-3: April 1999
CTRL_PSTN_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.
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 AN1.
4.3.1.4 Control protocol (ISDN-BA port FSM)
Refer to ETS 300 324-1 [1], table 35.
CTRL_ISDNBA_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_ISDNBA_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.
CTRL_ISDNBA_AN20_22
On receipt of a PORT CONTROL message containing the control_function_element IE FE101
(activate_access_req) the IUT shall enter state AN2.2 (access activated) when UNI reach successful
activation and respond with a PORT CONTROL message containing the control_function_element IE
FE104 (access_activated_ind).
CTRL_ISDNBA_AN22_20
On receipt of a PORT CONTROL message containing the control_function_element IE FE105
(deactivate_access_req) the IUT shall enter state AN2.0 (operational deactivated) when UNI reach
successful deactivation and respond with a PORT CONTROL message containing the
control_function_element IE FE106 (access_deactivated_ind).
4.3.1.5 PSTN protocol
Refer to ETS 300 324-1 [1], table 29.
All messages sent within the test steps shall be valid PSTN messages.
PSTN_ANx_6” CTRL_PSTN_AN20_10 (refer to subclause 4.3.1.3)
On receipt of a PORT CONTROL message containing the control_function_element IE FE203
(block_cmd) the PSTN protocol FSM shall enter the PSTN_path_state AN6.
PSTN_AN1_0
On receipt of a MDU_CTRL (restart_req) message the IUT shall send a COMMON CONTROL message
containing the control_function_id IE "restart req".
The IUT shall send a COMMON CONTROL message containing the control_function_id IE "restart
complete".
PSTN_AN6_1” CTRL_PSTN_AN10_20 (refer to subclause 4.3.1.3)
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 the PSTN protocol shall enter the
PSTN_path_state AN1. The subscriber line shall be monitored for a subscriber seizure or line information
condition. If this condition exists the IUT shall send an ESTABLISH message. (refer to ETS 300 324-1 [1],
subclause 13.5.4.2).
PSTN_AN1_2
On receipt of an originating call attempt (FE-subscriber_seizure) the IUT shall send the message
ESTABLISH and enter the PSTN_path_state AN2 (Path initiated by AN).
Page 19
ETS 300 324-3: April 1999
PSTN_AN2_3
On receipt of a FE-subscriber_release, the IUT shall enter the PSTN_path_state AN3.
PSTN_AN1_4
On receipt of the event FE-line_information, the IUT shall send the ESTABLISH message and enter the
PSTN_path_state AN4.
PSTN_AN1_5
On receipt of the ESTABLISH message the IUT shall send the message ESTABLISH ACK and enter the
PSTN_path_state AN5 (Path active).
PSTN_AN5_7
On receipt of a SIGNAL message containing a faulty sequence number the IUT PSTN protocol shall send
a DISCONNECT message and enter the PSTN_path_state AN7.
4.3.2 Preconditions
The precondition step of a test group applies at the UP via the user interface as a Permanent Line (PL)
condition. This line condition shall be permanent during all tests in that test group.
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.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.4 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.5 Status verification
4.3.5.1 PSTN protocol
Based on ETS 300 324-1 [1], table 29, it is possible to identify the state of the IUT PSTN protocol FSM
with valid PSTN messages.
On receipt of a STATUS ENQUIRY message the IUT shall send a STATUS message and remain the
same state.
4.3.5.2 Port control protocol
CHECK_PC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5.1 interface.
Afterwards teststep CTRL_PSTN_AN10_20 (refer to subclause 4.3.1.3) or CTRL_ISDNBA_AN10_20
(refer to subclause 4.3.1.4), depending on the affected port type is applied.
4.3.5.3 Common control protocol
CHECK_CC_DISCARD
Until time-out of timer T_NOAC no message shall appear on the V5.1 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.
Page 20
ETS 300 324-3: April 1999
4.3.6 Common test steps
This test step group shall contain procedures which are used in more than one ATC.
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
The ASP shall transfer the V5DLaddr to the Data link Service Access Point (DSAP).
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
Page 21
ETS 300 324-3: April 1999
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
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_pulse_notification
pstn_line_infomation
pstn_state
pstn_autonomous_signalling_sequence
pstn_sequence_response
Page 22
ETS 300 324-3: April 1999
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 repetition of the PORT clause 14, table 59
CONTROL message
N02 1 Allowed number of repetition of the COMMON clause 14, table 60
CONTROL message
N1 1 Number of repetitions of the ESTABLISH clause 13, table 28
message before starting T2
N2 3 Maximum number of tested repetitions of the clause 13, table 28
ESTABLISH message
N3 2 Allowed number of repetitions of the clause 13, table 28
DISCONNECT message
Page 23
ETS 300 324-3: April 1999
5 Test Purposes (TPs)
5.1 Introduction
For each test requirement, a TP is defined.
This subclause details the TPs for the AN side of NWK of the V5.1 interface for each test group and
references to the corresponding ATCs.
At the beginning of each test subgroup the initial state (refer to subclause 5.1.5), the preambles (refer to
subclause 4.3.3) and the postambles (refer to subclause 4.3.4) are listed.
5.1.1 TP naming convention
The identifier of the TP is constructed according to the scheme in table 4.
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 24
ETS 300 324-3: April 1999
5.1.2 Source of TP definition
The source for the TPs is 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 abstract test cases 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 states are covered. The TPs cover only
examples for each error handling procedure:
1) for the PSTN protocol applications the error handling procedures are tested in
PSTN_path_state AN1. To easily perform some of the test cases, some procedures are
tested in PSTN_path_state AN5;
2) for the Control protocol applications the error handling procedures are tested in state AN1 of
the Common and Port control protocol. During these tests the PSTN and ISDN-BA user port
FSMs stay in state AN1.0.
The procedure for unexpected events of the PSTN protocol is exhaustively tested (all unexpected
events in all PSTN_path_states are covered);
c) for several TPs some activities by the testing person are requested (invoking of certain procedures
by the System Under Test (SUT)). These TPs are marked with (*);
d) the Port control protocol, the Common control protocol (COM), the ISDN user p
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...