SIST EN 300 324-4 V3.1.1:2005

• Abstract:

  Update the test specifications to be in line with the 3rd edition of the base protocol standard.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI EN 300 324-4 V3.1.1 (2001-03) - V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)

SIST EN 300 324-4 V3.1.1:2005 is the Slovenian adoption of ETSI EN 300 324-4 Version 3.1.1 for the V5.1 interface at the digital Local Exchange (LE). It specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network layer on the Access Network (AN) side. In practice, it gives test laboratories and suppliers a common basis for checking conformance and interoperability between AN and LE implementations over V5.1.

What does SIST EN 300 324-4 V3.1.1:2005 specify?

SIST EN 300 324-4 V3.1.1:2005 specifies how to test the AN-side network layer of the V5.1 interface, using an ATS and a partial PIXIT proforma. The document is organized as a test specification: clauses 1 to 6 cover scope, references, definitions, the abstract test method, untestable test purposes, and ATS conventions, followed by two normative annexes.

Annex	What it covers
Annex A	The normative Abstract Test Suite for NWK testing, including TTCN.GR and TTCN.MP representations
Annex B	The normative partial PIXIT proforma for the V5.1 AN network layer

The scope also says the test specifications are updated to align with the 3rd edition of the base protocol standard. That matters because the test cases and PIXIT items are meant to match the protocol behaviour defined for the current base specification.

What are the key requirements of SIST EN 300 324-4 V3.1.1:2005?

The test method is remote, with an embedded variant for some cases

SIST EN 300 324-4 V3.1.1:2005 uses the remote test method for V5.1 AN NWK conformance testing, and applies the embedded variant where national and service functions are involved. The practical point is that testing is done from outside the implementation, but some test coordination depends on how the AN system is provisioned and managed.

Clause 4 states that there is no explicit Upper Tester (UT), so some control actions are implied or expressed informally in the ATS. It also notes that a simulator shall be attached to the relevant User Port when PSTN and ISDN-BA protocols are tested.

The Point of Control and Observation is on the DSAP

Clause 4 places the PCO for NWK testing on the DSAP, and test events at that point are described using data link Abstract Service Primitives (ASPs) and network layer PDUs. In practice, this tells the implementer what the test system watches and sends, so the test boundary is at the data link service access point rather than inside the protocol stack.

The same clause explains that different V5DLaddr values are used to identify the data link connection for each network layer protocol functional entity. That matters because the ATS keeps Control and PSTN signalling separated at the addressing level.

Test case execution has a fixed order

Clause 4.4 requires the startup test case TC11__SM_01 to be executed first, including after any restart of the IUT. It also sets the protocol group order as CTRL then PSTN, and the test group order as IT, CA, TI, BV, BO, BI.

In practice, that means the test campaign is not free-form. The order helps keep provisioning state, restart behaviour, and shared resources under control so that later test cases are not affected by earlier ones.

Some test purposes are intentionally not implemented in the ATS

Clause 5 lists Test Purposes (TPs) that are not implemented in the ATS. The reasons given are the chosen abstract test method, unknown reaction of the IUT after certain tests, or overlap with an already implemented test case.

For a reader, this means the ATS is a selected executable subset of the full test purpose set from the companion TSS&TP specification. When planning coverage, you need to look at the ATS together with the test purpose list from Part 3.

The ATS follows strict naming and implementation conventions

Clause 6 defines naming conventions for declaration, constraint, and dynamic parts of TTCN. It also defines how test steps, local trees, verdict labels, and common abbreviations are named.

This matters in practice because the ATS is meant to be maintainable and tool-convertible. A laboratory or tool vendor using the suite needs to preserve these conventions to keep the test logic readable and traceable.

The PIXIT proforma captures the data needed to run the tests

Annex B defines the partial PIXIT proforma from the testing viewpoint. It collects identification data, lab data, SUT data, protocol-layer information, addresses, timer values, procedural information, optional PSTN information, implicit send events, and PICS information.

This is the information that lets a test lab adapt the generic ATS to a specific IUT. Without it, the test cases cannot be fully parameterized for the implementation under test.

What terms does SIST EN 300 324-4 V3.1.1:2005 define?

• Abstract Test Suite (ATS) - The set of abstract test cases and related test material used to test protocol conformance.
• Abstract Test Method (ATM) - The test setup and control approach used to apply the ATS to the implementation under test.
• Protocol Implementation eXtra Information For Testing (PIXIT) - Implementation-specific information needed to run the tests correctly.
• Implementation Under Test (IUT) - The implementation being checked by the test suite.
• Point Of Control And Observation (PCO) - The point where the tester controls and observes protocol behaviour.
• Data link Service Access Point (DSAP) - The access point used here as the PCO for NWK testing.
• V5DLaddr - The V5 data link address used to identify the data link connection for a protocol functional entity.

Who uses SIST EN 300 324-4 V3.1.1:2005?

SIST EN 300 324-4 V3.1.1:2005 is used by test laboratories, equipment manufacturers, and suppliers of AN and LE implementations that need to verify V5.1 network layer behaviour. It is also used by clients who prepare or witness conformance assessment, because Annex B is a PIXIT proforma based on ISO/IEC 9646-5.

In practice, the main users are people who need to:

• set up conformance tests for V5.1 AN network layer equipment,
• complete PIXIT information for a specific SUT or IUT,
• map protocol behaviour to TTCN test cases,
• and document what the implementation supports, including Control and PSTN-related items.

What changed in SIST EN 300 324-4 V3.1.1:2005 from the previous edition?

SIST EN 300 324-4 V3.1.1:2005 updates the test specifications to be in line with the 3rd edition of the base protocol standard.

Which standards are used with SIST EN 300 324-4 V3.1.1:2005?

Standard	What it contributes
ETSI EN 300 324-1	The V5.1 interface specification that defines the protocol behaviour being tested
ETSI EN 300 324-2	The PICS proforma used to state implementation capabilities
ETSI EN 300 324-3	The TSS&TP specification that supplies the test purposes implemented by the ATS
ISO 7498	The reference model used for terms such as NWK, DLL, and PHL
ISO/IEC 9646-1	General conformance testing concepts, including ATS, IUT, PCO, and PIXIT
ISO/IEC 9646-2	Abstract test suite specification and ATM concepts
ISO/IEC 9646-3	TTCN notation used to define the ATS
ISO/IEC 9646-5	Requirements for test laboratories and clients in the conformance assessment process

What does the SIST EN 300 324-4 V3.1.1:2005 document contain?

The document contains the ATS for NWK testing, including TTCN conventions, test case structure, and execution rules. Annex A provides the TTCN.GR and TTCN.MP forms of the ATS, so the suite can be handled in graphical and machine-processable form.

Annex B provides the partial PIXIT proforma with fields for identification, test-lab details, SUT details, protocol layer information, addresses, parameter values, timer values, procedural information, optional PSTN data, implicit send events, and PICS information. In practice, this is the part that a supplier or laboratory fills in before running the test suite.

The body of the document also describes the abstract test method, the DSAP-based PCO, the handling of error indications, and the conventions used to name TTCN elements and verdict labels. That makes the standard useful both as a test specification and as an implementation guide for turning the ATS into executable tests.

SLOVENSKI STANDARD
01-januar-2005
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.1 za podporo
dostopovnega omrežja (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna
dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma
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 4: Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN
side)
Ta slovenski standard je istoveten z: EN 300 324-4 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 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network layer (AN side)

2 ETSI EN 300 324-4 V3.1.1 (2001-03)
Reference
REN/SPAN-09101-4
Keywords
AN,ATS,LE,PIXIT,Vinterface,V5interface
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
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:
[e-mail]
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-4 V3.1.1 (2001-03)
Contents
Intellectual Property Rights .5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.7
3.1 Definitions . 7
3.2 Abbreviations. 8
4 Abstract test method .9
4.1 ATM. 9
4.2 NWK protocol testing. 9
4.3 Data link addresses. 10
4.4 Execution of TCs. 10
4.4.1 Handling of error indication . 10
4.4.2 TC execution sequence. 10
5 Untestable test purposes.11
5.1 Control protocol . 11
5.2 PSTN protocol . 12
6 Abstract test suite conventions .12
6.1 Naming conventions. 12
6.1.1 Declaration part . 12
6.1.2 Constraint part . 13
6.1.3 Dynamic part . 14
6.1.3.1 TC. 14
6.1.3.2 Test steps. 14
6.1.3.3 General aspects. 14
6.1.4 ATS abbreviations . 14
6.2 Implementation conventions. 15
6.2.1 Declaration part . 15
6.2.2 Constraint part . 15
6.2.3 Dynamic part . 16
6.2.4 Documentation. 17
Annex A (normative): Abstract test suite for NWK testing .18
A.1 The TTCN Graphical form (TTCN.GR).18
A.2 The TTCN Machine Processable form (TTCN.MP) .18
Annex B (normative): Partial PIXIT proforma.19
B.1 Introduction.19
B.2 PIXIT proforma.19
B.2.1 Identification summary. 19
B.2.2 Abstract test suite summary. 19
B.2.3 Test laboratory . 19
B.2.4 Client. 20
B.2.5 SUT . 20
B.2.6 Protocol layer information . 21
B.2.6.1 Protocol identification. 21
B.2.6.2 IUT information. 21
ETSI
4 ETSI EN 300 324-4 V3.1.1 (2001-03)
Bibliography.27
History .28
ETSI
5 ETSI EN 300 324-4 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 4 of a multi-part deliverable covering the V5.1 interface for the support of Access
Network (AN); 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
6 ETSI EN 300 324-4 V3.1.1 (2001-03)
1 Scope
The present document contains the Abstract Test Suite (ATS) as well as the Abstract Test Method (ATM) and the
partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the Network layer (NWK) of the
V5.1 interface 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 an ATS containing conformance tests which give a high probability
of inter-operability of an AN and a Local Exchange (LE) from different manufacturers over the V5.1 interface.
ISO/IEC 9646-1 [5] and ISO/IEC 9646-2 [6] are used as the basis for the test methodology. The ATS is defined using
the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [7].
The ATS in annex A describes a set of Test Cases (TCs) which are based on the Test Purposes (TPs) specified in
EN 300 324-3 [3]. The TCs provide the implementation of the TPs and can be converted into an executable test suite by
using available TTCN translators and the corresponding tools.
Annex B provides the partial PIXIT proforma.
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 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 specification".
[3] ETSI EN 300 324-3: "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)".
[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".
[6] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract test suite specification".
[7] ISO/IEC 9646-3: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[8] ISO/IEC 9646-5: "Information Technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
ETSI
7 ETSI EN 300 324-4 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]
NOTE: In the present document, the commonly used term TC is applied in the same way as ATC.
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [5]
current provisioning variant: ID for the presently active data set
Data Link Layer (DLL): refer to ISO 7498 [4]
embedded variant: refer to ISO/IEC 9646-2 [6]
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [5]
incorrect information element: specified IE carrying IE types not defined in EN 300 324-1 [1]
invalid PSTN information element: PSTN IE not according to national specific requirements
invalid protocol data unit: protocol Data Unit (PDU) which contains an incorrect message format
invalid PSTN message: PSTN message carrying IEs not according to national specific requirements
LowerTester(LT): refer to ISO/IEC 9646-1 [5]
Network Layer (NWK): refer to ISO 7498 [4]
new provisioning variant: ID for the data set which was announced to the IUT to become the next active data set
through re-provisioning
Physical Layer (PHL): refer to ISO 7498 [4]
PICS proforma: refer to ISO/IEC 9646-1 [5]
PIXIT proforma: refer to ISO/IEC 9646-1 [5]
Point Of Control And Observation (PCO): refer to ISO/IEC 9646-1 [5]
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [5]
Protocol Implementation eXtra Information For Testing (PIXIT): refer to ISO/IEC 9646-1 [5]
remote test method: refer to ISO/IEC 9646-2 [6]
specified information element: IE ID 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: ID for a non-available data set
unspecified information element: IE ID not defined in EN 300 324-1 [1]
valid information element: PSTN IE according to national specific requirements
valid PSTN message: PSTN message carrying IEs according to national specific requirements
ETSI
8 ETSI EN 300 324-4 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
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA CApability test
CTRL Control
DLL Data Link Layer
DSAP Data link SAP
FE Function Element
FSM Finite State Machine
ID Identifier
IE Information Element
IEI Information Element Identifier
ISDN Integrated Services Digital Network
ISDN-BA ISDN-Basic Access
IT basic Interconnection Test
IUT Implementation Under Test
L3addr Layer 3 address
LE Local Exchange
LT1 Lower Tester 1
PCO Point of Control and Observation
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PSTN Public Switched Telephone Network
SAP Service Access Point
SUT System Under Test
TC Test Case, the same definition as for ATC applies
TP Test Purposes
TTCN Tree and Tabular Combined Notation
UL Upper Layer
UT Upper Tester
V5DLaddr V5 Data Link address
ETSI
9 ETSI EN 300 324-4 V3.1.1 (2001-03)
4 Abstract test method
This clause describes the Abstract Test Method (ATM) and the Point of Control and Observation (PCO) used to test the
NWK of the V5.1 protocol for the AN components.
4.1 ATM
Principally, the remote test method is used for V5.1 AN NWK conformance testing. Certain V5.1 AN NWK TPs need
also part of the service and national functions. Therefore, the embedded variant of the remote test method is applied.
The national dependant information is defined in the PIXIT.
NOTE: The multi-party testing ATM (MPyT) (ISO/IEC 9646-2 [6], clause 12.7, was also considered for this
ATS. But as the interfaces on the user port side may be implemented on national specific standards the
MPyT ATM was not applicable for this ATS. To solve this need for operations on the user port interfaces,
terminals will be connected to the user ports. All necessary functions which would have been provided by
a lower tester connected to the user ports can be achieved by manual operations on the connected
terminal.
4.2 NWK protocol testing
The V5.1 implementations do not offer a direct access to the upper service boundary. The remote test method was
chosen because any co-ordination procedures can only be expressed in an informal way.
SUT V5 Test System
UT
LT1
V5 NWK PDUs
IUT
PCO/DSAP
V5-NWK
DL-DATA
Control,BCC, LINK,
Service Provider
Protection and PSTN
DLL & PHL layers
DL connection endpoints
Figure 1: Remote single layer test method applied to the V5.1 NWK testing
LT1: A Lower Tester (LT1) is located in a remote V5.1 test system. It controls and observes the
behaviours of the IUT.
DSAP: A unique Data link Service Access Point (DSAP) is defined at the V5.1 interface and commonly
used for exchanging service data of the different Network layer protocol functional entities: PSTN,
Control protocols.
PCO: The PCO for NWK testing is located on the DSAP. All test events at the PCO are specified in
terms of data link Abstract Service Primitives (ASPs) and network layer PDUs.
ETSI
10 ETSI EN 300 324-4 V3.1.1 (2001-03)
UT: No explicit Upper Tester (UT) exists in the test system. However, the SUT needs to carry out some
UL functions to achieve some effects of test co-ordination procedures. Designing ATS, the
capability of the system management functions, such as controls of the IUT, its interactions with
the Q interface may be taken into account. The controls of the IUT will be implied or informally
expressed in the ATS, but no assumption shall be made regarding their feasibility or realization.
An example of such controls could be to provoke restarting of the IUT through the Q interface.
V5-NWK: To test the PSTN and ISDN-BA protocols, a simulator shall be attached to relevant User Port
(UP).
4.3 Data link addresses
Within the DSAP, different V5DLaddr are used to identify each corresponding data link connection. Each network
layer protocol functional entity can have only one data link connection, e.g. all PSTN signalling information shares one
data link connection.
Table 1 shows the allocated V5DLaddr used by protocol function entities.
Table 1: V5DLaddr
Protocol PSTN Control
V5DLaddr 8 176 8 177
4.4 Execution of TCs
4.4.1 Handling of error indication
During the execution of the NWK ATS many error indications will be sent to the system management due to the invalid
and the inopportune TCs. It is up to the IUT supplier to take the necessary precautions to avoid any impact on the test
result.
4.4.2 TC execution sequence
The following test sequence shall be applied:
The TC containing the start-up procedure (TC11__SM_01) shall always be the first TC executed. Also in any case
where the IUT has to be restarted this TC shall be first executed.
Protocol groups: CTRL ⇒ PSTN.
Test groups: IT ⇒ CA ⇒ TI ⇒ BV ⇒ BO ⇒ BI.
Interactions between the different test groups are not considered. It is up to the IUT supplier to take the necessary
precautions to avoid any impact on the test result.
NOTE: This applies in particular to PORT CONTROL messages from ISDN ports while testing PSTN-related
protocols and vice versa.
ETSI
11 ETSI EN 300 324-4 V3.1.1 (2001-03)
5 Untestable test purposes
This clause gives a list of TPs which are not implemented in the ATS due to the chosen abstract test method or other
restrictions.
5.1 Control protocol
The test purposes listed in table 2 are not implemented in the ATS due to unknown reaction of the IUT after testing the
TPs or due to the fact they have the same purpose of TC already implemented.
Table 2: Untestable TPs
Test Purpose
TP1311S1_01
TP1313S0_01
TP1321S2_01
TP1324S1001
TP1324S1002
TP1324SM_06
TP1324SM_07
TP1325SM_03
TP1325S2207
TP1325S2208
TP1325S2209
TP1424S1101
TP1425SM_01
TP1521S1-01
ETSI
12 ETSI EN 300 324-4 V3.1.1 (2001-03)
5.2 PSTN protocol
The test purposes listed in table 3 are not implemented in the ATS due to unknown reaction of the IUT after testing the
TPs.
Table 3: Untestable TPs
Test Purpose
TP23__S0_04
TP23__S0_06
TP23__S0_07
TP23__S1_08
TP23__S1_09
TP23__S2_11
TP23__S3_10
TP23__S3_11
TP23__S4_06
TP23__S4_09
TP23__S4_10
TP23__S6_05
TP23__S7_11
TP24__S2_03
TP24__S2_04
TP24__S3_04
TP24__S3_05
TP24__S4_05
TP24__S5_04
TP24__S5_05
TP24__S5_06
TP24__S7_02
TP26__S5_01
6 Abstract test suite conventions
The ATS conventions are intended to give a better understanding of the ATS but they describe also the conventions
made for the development of the ATS, thus for any later maintenance purposes or further development of the ATS the
conventions described in this clause shall be considered.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming
conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the
functional structure of the ATS.
NOTE: To define the ATS, the guidelines given in EN 300 406 and ETR 141 were considered.
6.1 Naming conventions
6.1.1 Declaration part
The ID names of the following definitions are written in lowercase:
- structured type definitions;
- ASP type definitions;
- PDU type definitions.
ETSI
13 ETSI EN 300 324-4 V3.1.1 (2001-03)
The ID names of the following definitions are written in uppercase:
- Test Suite Parameter Declarations;
- Test Case Selection Expression Definitions;
- Test Suite Constant Declarations;
- Test Case Variable Declarations.
ID names of PDUs and structured types commence with a protocol identifier to define which protocol they are
belonging to. The following identifiers are used:
- control protocol: ctrle.g. crtl_common_control_ack;
- PSTN signalling: pstn e.g. pstn_signal_ack.
ID names of PDUs and structured types which are used for invalid tests commence with "bi".
EXAMPLE 1: bi_com_ctrl_two_mety.
Complete names as defined in the specifications are used for ID names of declarations.
EXAMPLE 2: ctrl_control_function_element.
Test suite parameter ID names commence with TSP:
- PICS are identified by adding the letter "C": TSPC_. (e.g.: TSPC_PSTN);
- PIXIT are identified by adding the letter "X": TSPX_. (e.g.: TSPX_PORT_ADDRESS).
If the test suite parameter is representing a system parameter or value, only the parameter name is used.
EXAMPLE 3: MR (receive sequence number in signal message).
Test suite operations commence with TSO.
EXAMPLE 4: TSO_INTEGER_TO_O_1.
Test suite constant ID names commence with TSC.
EXAMPLE 5: TSC_CFE_FE201_2_UNBL.
If the constant is representing a system parameter or value, only the parameter name is used.
EXAMPLE 6: N01.
ID names of timers commence with T. The same names as in the specification are used.
EXAMPLE 7: T01.
6.1.2 Constraint part
Constraint names commence with uppercase. The remaining part of the ID name is written in lowercase.
ID names of elements concerning the same subject have equivalent names in the declaration and the constraint part:
Declaration part: ctrl_control_function_element;
Constraint part: Ctrl_control_function_element.
The name of the modified constraint describes the particularity of the modified constraint.
EXAMPLE: Ctrl_cc_mand_only (common control message which contains only the mandatory IEs).
If formal parameter lists are used, the variable names are written in lowercase. The variable name is the same as the
name of the
...