SIST EN 300 324-3 V3.1.1:2005
(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)
Update the test specifications to be in line with the 3rd edition of the base protocol standard.
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 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
Standards Content (Sample)
SLOVENSKI STANDARD
01-januar-2005
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 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)
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: EN 300 324-3 Version 3.1.1
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 Standard (Telecommunications series)
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 ETSI EN 300 324-3 V3.1.1 (2001-03)
Reference
REN/SPAN-09101-3
Keywords
AN, LE, testing, TSS&TP, V interface
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33492 94 4200 Fax: +33493 65 4716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
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 2001.
All rights reserved.
ETSI
3 ETSI EN 300 324-3 V3.1.1 (2001-03)
Contents
Intellectual Property Rights .6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.8
3.1 Definitions . 8
3.2 Abbreviations. 9
4 Test Suite Structure (TSS) .10
4.1 TSS overview. 10
4.2 Test groups . 11
4.2.1 Protocol groups. 11
4.2.1.1 Control protocol . 11
4.2.1.2 PSTN protocol. 12
4.2.2 Main test groups . 12
4.2.2.1 Basic Interconnection (IT) tests. 12
4.2.2.2 Capability (CA) tests . 12
4.2.2.3 Valid Behaviour (BV) tests. 12
4.2.2.4 Inopportune Behaviour (BO) tests. 12
4.2.2.5 Invalid Behaviour (BI) tests . 12
4.2.2.6 Timer (TI) expiry and counter mismatch tests. 13
4.2.2.6.1 Timer expiry and counters of the Control protocol . 13
4.2.2.6.2 Timer expiry and counters of the PSTN protocol. 13
4.2.2.6.3 Timer expiry and counters of the AN system management . 13
4.3 Test step structure. 14
4.3.1 State transitions. 14
4.3.1.1 Startup of V5.1 interface. 14
4.3.1.2 Common control protocol (system management). 15
4.3.1.3 Control protocol (PSTN port FSM). 16
4.3.1.4 Control protocol (ISDN-BA port FSM). 16
4.3.1.5 PSTN protocol. 16
4.3.2 Preconditions. 17
4.3.3 Preambles . 17
4.3.4 Postambles. 17
4.3.5 Status verification . 17
4.3.5.1 PSTN protocol. 17
4.3.5.2 Port control protocol. 18
4.3.5.3 Common control protocol . 18
4.3.6 Common test steps. 18
4.4 Defaults . 18
4.5 Abstract Service Primitives (ASPs) and Protocol Data Units (PDUs). 18
4.5.1 ASPs . 18
4.5.2 PDUs. 18
4.5.2.1 Common control protocol . 18
4.5.2.2 Port control protocol. 18
4.5.2.3 PSTN protocol. 19
4.5.3 Information elements . 19
4.5.3.1 Variable length information elements. 19
4.5.3.1.1 Control protocol . 19
4.5.3.1.2 PSTN protocol . 19
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
ETSI
4 ETSI EN 300 324-3 V3.1.1 (2001-03)
5 Test Purposes (TPs).21
5.1 Introduction. 21
5.1.1 TP naming convention . 21
5.1.2 Source of TP definition . 21
5.1.3 Test strategy . 22
5.1.4 Requirements not covered by TPs. 22
5.1.5 Initial state. 23
5.1.6 Test and data configuration requirements. 23
5.2 Control protocol . 23
5.2.1 Basic interconnection tests (V5NWKAN/CTRL/IT) . 23
5.2.2 Capability tests (V5NWKAN/CTRL/CA). 23
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. 24
5.2.3.1.3 V5NWKAN/CTRL/BV/COM/REVY. 25
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 . 28
5.2.4 Inopportune behaviour tests (V5NWKAN/CTRL/BO). 31
5.2.4.1 V5NWKAN/CTRL/BO/COM. 31
5.2.4.1.1 V5NWKAN/CTRL/BO/COM/TRANS. 31
5.2.4.1.2 V5NWKAN/CTRL/BO/COM/REVY. 31
5.2.4.2 V5NWKAN/CTRL/BO/PORT. 31
5.2.4.2.1 V5NWKAN/CTRL/BO/PORT/TRANS. 31
5.2.4.2.2 V5NWKAN/CTRL/BO/PORT/PSTN. 32
5.2.4.2.3 V5NWKAN/CTRL/BO/PORT/ISDNBA . 32
5.2.5 Invalid behaviour tests (V5NWKAN/CTRL/BI) . 33
5.2.5.1 V5NWKAN/CTRL/BI/COM . 33
5.2.5.1.1 V5NWKAN/CTRL/BI/COM/TRANS . 33
5.2.5.2 V5NWKAN/CTRL/BI/PORT . 34
5.2.5.2.1 V5NWKAN/CTRL/BI/PORT/TRANS . 34
5.2.6 Timer expiry and counter mismatch tests (V5NWKAN/CTRL/TI). 35
5.2.6.1 V5NWKAN/CTRL/TI/COM . 35
5.2.6.1.1 V5NWKAN/CTRL/TI/COM/TRANS. 35
5.2.6.2 V5NWKAN/CTRL/TI/PORT . 36
5.2.6.2.1 V5NWKAN/CTRL/TI/PORT/TRANS . 36
5.3 PSTN protocol . 36
5.3.1 Basic interconnection tests (V5NWKAN/PSTN/IT). 36
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. 37
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 . 50
ETSI
5 ETSI EN 300 324-3 V3.1.1 (2001-03)
5.3.6 Timer expiry and counter mismatch tests (V5NWKAN/PSTN/TI) . 51
5.3.6.1 V5NWKAN/PSTN/TI/2. 51
5.3.6.2 V5NWKAN/PSTN/TI/3. 51
5.3.6.3 V5NWKAN/PSTN/TI/4. 52
5.3.6.4 V5NWKAN/PSTN/TI/5. 52
5.3.6.5 V5NWKAN/PSTN/TI/7. 52
Bibliography.53
History .54
ETSI
6 ETSI EN 300 324-3 V3.1.1 (2001-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 3 of a multi-part deliverable, covering the V5.1 interface at the digital Local Exchange
(LE); V5.1 interface for the support of Access Network (AN), as described below:
Part 1: "V5.1 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
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".
National transposition dates
Date of adoption of this EN: 16 March 2001
Date of latest announcement of this EN (doa): 30 June 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 December 2001
Date of withdrawal of any conflicting National Standard (dow): 31 December 2001
ETSI
7 ETSI EN 300 324-3 V3.1.1 (2001-03)
1 Scope
The present document 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 the present document 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. The present document covers
only the procedures described in EN 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
EN 300 324-1 [1] are covered by the tests defined in the present document. 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 the present document.
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.
The present document 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.
The present document contains no requirements concerning NWK tests for Integrated Services Digital Network Basic
Access (ISDN-BA).
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI EN 300 324-1 (V2.1.1): "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] ETSI EN 300 324-2: "V interface at the digital Local Exchange (LE); V5.1 interface for the
support of Access Network (AN); Part 2: Protocol Implementation Conformance Statement (PICS)
proforma specification".
[3] ETSI ETS 300 297 (1995): "Integrated Services Digital Network (ISDN); Access digital section
for ISDN basic access".
[4] ISO 7498-2: "Information processing systems - Open Systems Interconnection - Basic Reference
Model - Part 2: Security Architecture".
[5] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
ETSI
8 ETSI EN 300 324-3 V3.1.1 (2001-03)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply, together with those given in
EN 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-2 [4]
implementation under test: refer to ISO/IEC 9646-1 [5]
incorrect information element: specified information element carrying information element types not defined in
EN300 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-2 [4]
network termination: equipment providing the network side at the ISDN user-network interface for the basic access
NOTE: This term is used in the present document 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-2 [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 EN 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 EN 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
ETSI
9 ETSI EN 300 324-3 V3.1.1 (2001-03)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATC AbstractTestCase
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
ETSI
10 ETSI EN 300 324-3 V3.1.1 (2001-03)
4 Test Suite Structure (TSS)
4.1 TSS overview
Figure 1 shows the structure of the V5.1 AN side NWK test suite.
CTRL IT
V5NWKAN
CA
BV
COM TRANS/PROTOCOL
SYS_MAN/ REST
SYS_MAN REVY
PORT
TRANS/PROTOCOL
PSTN
ISDN-BA
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
Figure1:NWKANTSS
ETSI
11 ETSI EN 300 324-3 V3.1.1 (2001-03)
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 EN 300 324-1 [1]
NWK protocol entities Protocol entities defined in Protocol group reference
EN 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 start-up, 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.
ETSI
12 ETSI EN 300 324-3 V3.1.1 (2001-03)
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.
ETSI
13 ETSI EN 300 324-3 V3.1.1 (2001-03)
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 EN 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 EN 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 EN 300 324-1 [1], clause 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 EN 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 or from CTRL protocol
TC1 MDL-RELEASE-INDICATION from CONTROL-DL
TC2 Expiry of TC1
TC3 MDL-RELEASE-INDICATION from PSTN-DL
TC8 Expiry of TC2
TC9 Cold restart of V5 interface
TV1 MDU-CTRL(request variant & interface ID) to CTRL protocol
ETSI
14 ETSI EN 300 324-3 V3.1.1 (2001-03)
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 clause 4.3.1)
preconditions (refer to clause 4.3.2)
preambles (refer to clause 4.3.3)
postambles (refer to clause 4.3.4)
status checks (refer to clause 4.3.5)
common behaviours (refer to clause 4.3.6)
4.3.1 State transitions
The following clauses 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 clause 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 clause 6.5.1 of EN 300 324-2 [2]) are used to define the implemented configuration of the IUT.
NOTE 1: EN 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 clause 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.
ETSI
15 ETSI EN 300 324-3 V3.1.1 (2001-03)
PICS M1 = Yes M1 = Yes M1 = No
PICS M2 = Yes M2= No M2 = Yes
AN LT1
wait for TC9 wait for TC9 wait for TC9
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
PSTN port FSM
unblock req unblock req
(note 2)
block cmd block cmd
ISDN port FSM
unblock req unblock req
(note 3)
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
clause 5.2.3.1.1.
NOTE 2: To reach the initial state of the IUT PSTN user port FSM as defined in clause 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 3: To reach the initial state of the ISDN-BA user port FSM as defined in clause 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 EN 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.
ETSI
16 ETSI EN 300 324-3 V3.1.1 (2001-03)
4.3.1.3 Control protocol (PSTN port FSM)
Refer to EN 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 EN 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 EN 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 clause 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".
ETSI
17 ETSI EN 300 324-3 V3.1.1 (2001-03)
PSTN_AN6_1 ≡ CTRL_PSTN_AN10_20 (refer to clause 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
EN 300 324-1 [1], clause 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 clause 4.3.1.2 to clause 4.3.1.5 can be used to create preambles.
Each preamble shall start from the IUT initial state as defined in clause 5.1.5.
4.3.4 Postambles
After each ATC the IUT shall be brought back to the initial state as defined in clause 5.1.5. All combinations of the test
steps defined in clauses 4.3.1.2 to 4.3.1.5 can be used to create posta
...
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...