SIST ETS 300 805-2 E1:2005

SLOVENSKI STANDARD
01-maj-2005
Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski
protokol - Vodovne osnovne storitve - Omrežna plast (NL) - 2. del: Abstraktni
preskušalni niz (ATS) - Specifikacija
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit
mode basic services; Network Layer (NL); Part 2: Abstract Test Suite (ATS) specification
Ta slovenski standard je istoveten z: ETS 300 805-2 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 805-2
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA-00109-2
ICS: 33.020
Key words: ATS, circuit mode, layer 3, PINX, PISN, QSIG, testing
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Circuit mode basic services;
Network Layer (NL);
Part 2: Abstract Test Suite (ATS) specification
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 1998. All rights reserved.

Page 2
ETS 300 805-2: February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 805-2: February 1998
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Abstract Test Method (ATM).11
4.1 Choice of the ATM .11
4.1.1 Functional subsets .11
4.1.2 Single- and Multi-party testing.12
4.2 Single PCO testing.12
4.2.1 CC testing for non-Transit PINX and PC testing .12
4.2.2 Segmentation and Protocol Discriminator Filter testing .13
4.3 Multiple PCO testing .14
4.3.1 CC testing for a Transit PINX.14
4.4 Test Configurations and use of concurrent TTCN.14
5 Untestable Test Purposes (TPs).15
6 Conformance clause .15
7 ATS Conventions .16
7.1 Short names and abbreviations .16
7.2 Test Suite type, ASP type, PDU type and Alias identifiers.17
7.2.1 ASP type identifiers .17
7.2.2 PDU type identifiers.17
7.2.3 Test Suite type identifiers (Information Elements) .17
7.2.4 Aliases.18
7.3 Identifiers concerning test configuration .18
7.3.1 Test components.18
7.3.2 Test component configurations.18
7.3.3 Points of Control and Observations (PCOs) .18
7.3.4 Co-ordination Points (CPs).18
7.3.5 Co-ordination Message (CM) types.19
7.4 Test Suite Parameter and Selection Expression identifiers.19
7.4.1 Test suite parameters .19
7.4.2 PICS Parameters .19
7.4.3 PIXIT parameters .19
7.4.4 Test case selection expressions .19
7.4.5 Abbreviations used in PIXIT parameters and Test Case Selection
Expressions.20
7.5 Miscellaneous identifiers.21
7.5.1 Test Suite operations .21
7.5.2 Test Suite constants.21
7.5.3 Test Suite variables.21
7.5.4 Test case variables .22
7.5.5 Timers .22
7.6 Constraints.22
7.6.1 TTCN Test Suite type constraints .22
7.6.2 ASP constraints.22
7.6.3 PDU constraints .22
7.6.4 CM constraints .23

Page 4
ETS 300 805-2: February 1998
7.7 Dynamic part . 23
7.7.1 Test Case identifiers. 23
7.7.2 Test step identifier . 24
7.7.3 Default identifier. 24
7.8 Notation. 25
8 Test case and test purpose mapping . 25
Annex A (normative): Partial PIXIT proforma . 26
A.1 Identification summary. 26
A.2 ATS summary. 26
A.3 Test laboratory. 26
A.4 Client identification. 26
A.5 SUT. 27
A.6 Protocol layer information. 27
A.6.1 Protocol identification . 27
A.6.2 IUT information. 27
A.6.2.1 General information . 27
A.6.2.1.1 General configuration. 27
A.6.2.1.2 Addressing . 28
A.6.2.2 Clearing Procedures. 29
A.6.2.3 General Sending of Messages . 29
A.6.2.4 Originating PINX . 31
A.6.2.5 Terminating PINX . 32
A.6.2.6 Incoming Gateway PINX. 33
A.6.2.7 Outgoing Gateway PINX. 33
A.6.2.8 Transit PINX . 34
A.6.2.9 Status Procedure. 34
A.6.2.10 Layer Management. 35
A.6.2.11 Error Handling. 35
A.6.2.12 Segmentation. 35
A.6.2.13 Timers. 36
A.6.3 Called Party Numbers in the PIXIT . 36
Annex B (normative): Protocol Conformance Test Report (PCTR) Proforma for PSS1_BC Layer . 38
B.1 Identification summary. 38
B.1.1 Protocol conformance test report. 38
B.1.2 IUT identification. 38
B.1.3 Testing environment. 38
B.1.4 Limits and reservation . 39
B.1.5 Comments. 39
B.2 IUT Conformance status. 39
B.3 Static conformance summary. 39
B.4 Dynamic conformance summary. 39
B.5 Static conformance review report . 40
B.6 Test campaign report. 41
B.7 Observations. 48

Page 5
ETS 300 805-2: February 1998
Annex C (normative): Abstract Test Suite (ATS) for PSS1_BC .49
C.1 The TTCN Graphical form (TTCN.GR) .49
C.2 The TTCN Machine Processable form (TTCN.MP) .49
History.50

Page 6
ETS 300 805-2: February 1998
Blank page
Page 7
ETS 300 805-2: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the standardizing Information
and Communication Systems (ECMA) on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
This ETS comprises two parts with the generic title "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Network Layer (NL); Circuit mode basic services". The title of each part
is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS & TPs)";
Part 2: "Abstract Test Suite Specification (ATS)".
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

Page 8
ETS 300 805-2: February 1998
Blank page
Page 9
ETS 300 805-2: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) specification
for the Network Layer (NL), Circuit Mode Basic Services (CMBS) of the Inter-exchange signalling protocol,
for Private Integrated Services Networks (PISN).
The objective of this ATS specification is to provide conformance tests which give a high probability of
inter-operability of the NL. The ATS specification covers the procedures described in ETS 300 172 [1].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3],
ISO/IEC 9646-2 [4] and ISO/IEC 9646-3 [5]) is used as basis for the test methodology.
This ATS specification is applicable to implementations which support either a Basic Rate or a Primary
Rate access interface, or both, operating over a leased line. It is applicable to various PINX roles,
i.e. Originating, Terminating, Transit, Incoming/Outgoing Gateway.
Annex A provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma of
this ETS.
Annex B provides the Protocol Conformance Test Report (PCTR) proforma of this ETS.
Annex C provides the Tree and Tabular Combined Notation (TTCN) part of this ETS.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited in the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments or revisions to 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 172 (1995): "Private Integrated Services Network (PISN);
Inter-Exchange Signalling protocol, Circuit Mode Basic Services".
[2] ETS 300 805-1 (1996): "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Circuit mode basic services; Network Layer
(NL); Part 1: Test Suite Structure and Test Purposes (TSS&TP)".
[3] ISO/IEC 9646-1 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 1:
General Concepts".
[4] ISO/IEC 9646-2 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 2:
Abstract Test Suite Specification".
[5] ISO/IEC 9646-3 (1992): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework -Part 3:
The Tree and Tabular Combined Notation (TTCN)" including "Amendment 1 to
ISO/IEC 9646-3:1992 TTCN extensions" (1996).
[6] ISO/IEC 9646-3 AM2 (1997): " Amendment 2 to ISO/IEC 9646-3:1992 Further
extensions".
[7] ISO/IEC 9646-4 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework, Part 4:
Test Realization".
[8] ISO/IEC 9646-5 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 5:
Requirements on test laboratories and clients for the conformance assessment
process".
Page 10
ETS 300 805-2: February 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [3].
final test purpose: See ETS 300 805-1 [2].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [3].
incoming call: See ETS 300 172 [1].
incoming gateway PINX: See ETS 300 172 [1].
Lower Tester (LT): See ISO/IEC 9646-1 [3].
network layer: For the purposes of this ATS the procedures described in ETS 300 172 [1].
originating PINX: See ETS 300 172 [1].
outgoing call: See ETS 300 172 [1].
outgoing gateway PINX: See ETS 300 172 [1].
PICS proforma: See ISO/IEC 9646-1 [3].
PIXIT proforma: See ISO/IEC 9646-1 [3].
Point Of Control And Observation (PCO): See ISO/IEC 9646-1 [3].
preceding PINX: See ETS 300 172 [1].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [3].
Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [3].
segmentation: See ETS 300 805-1 [2].
Signalling Carriage Mechanism (SCM): See ETS 300 172 [1].
subsequent PINX: See ETS 300 172 [1].
super test purpose: See ETS 300 805-1 [2].
System Under Test (SUT): See ISO/IEC 9646-1 [3].
terminating PINX: See ETS 300 172 [1].
transit PINX: See ETS 300 172 [1].
Upper Tester (UT): See ISO/IEC 9646-1 [3].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
Page 11
ETS 300 805-2: February 1998
ATS Abstract Test Suite
CC Call Control
CM Co-ordination Message
CMBS Circuit Mode Basic Services
CP Co-ordination Point
IUT Implementation Under Test
LT Lower Tester
MS Message Segmentation
MTC Master Test Component
NL Network Layer
PC Protocol Control
PCF Protocol Control Function
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDF Protocol Discriminator Filter
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PINX Private INtegrated services eXchange
PISN Private Integrated Services Network
PIXIT Protocol Implementation eXtra Information for Testing
PSS1 Private Integrated Signalling System Number 1
PTC Parallel Test Component
SUT System Under Test
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the different Abstract Test Methods (ATMs) used for testing the Network Layer (NL)
protocol. Two methods are applied; the Remote single layer test method and the Multi-Party test method.
4.1 Choice of the ATM
4.1.1 Functional subsets
The choice of functional subsets is based primarily on the fact that Private Integrated signalling System
Number One (PSS1) is subdivided into two functional entities: Call Control (CC) and Protocol Control
(PC). Each of these two functional entities is tested using different sets of Test Purposes (TPs) and hence
different test cases.
The PC entity is further divided into three sublayers: the Protocol Discriminator Filter (PDF) sublayer, the
Message Segmentation sublayer and the other Protocol Control Functions (PCF) sublayer.
From the viewpoint of this ATS, PSS1 is considered to be divided into two functional subsets, as shown in
figure 1. The first of these functional groups consists of the Protocol Discriminator Filter sublayer and the
Message Segmentation sublayer. The second functional group consists of the other PCF sublayer and the
CC entity. A different Point of Control and Observation (PCO) is used for each of these functional groups
when being tested.
Page 12
ETS 300 805-2: February 1998
Call Control
Call Control
2nd group
Other Protocol
Control Functions
Protocol
PSS1
Control
Segmentation
1st group
P. D. Filter
Layer 2
SCM
Layer 1
NOTE: In the remainder of clause 4, the term "Protocol Control" (PC) refers only to the "Other Protocol
Control Functions" sublayer.
Figure 1: PSS1 functional subsets
4.1.2 Single- and Multi-party testing
For CC, the protocol defines different roles that a private integrated services exchange (PINX) can play: it
can be an end or gateway PINX (Originating, Terminating, Incoming Gateway, Outgoing Gateway), or a
Transit PINX. In the first case, only one interface needs to be tested and in the second case, two
interfaces need to be tested simultaneously.
4.2 Single PCO testing
Single PCO testing applies to the Segmentation and Protocol Discriminator Filter, to the Protocol Control
and to the CC for an Originating, Terminating, Incoming Gateway or Outgoing Gateway PINX.
4.2.1 CC testing for non-Transit PINX and PC testing
As shown in figure 2, the Implementation Under Test (IUT) is the PC and CC part and it is an end-system.
It is not possible to observe and control the upper service boundary of the IUT. Consequently, the test
method chosen is the Remote Test Method, where the co-ordination procedures are expressed in an
informal way. The test system will only contain one Lower Tester (LT) and no Upper Tester (UT). The
PCO, called LX, is located between the PC and CC part and the Segmentation part. Only unsegmented
Protocol Data Units (PDUs) are exchanged.

Page 13
ETS 300 805-2: February 1998
TEST SYSTEM
SUT
LT
IUT
Unsegmented
PDUs
Call Control and Call Control and
Protocol Control
Protocol Control
PCO : LX PSS1
Segmentation Segmentation
P. D. Filter P. D. Filter
SCM
Figure 2: Remote single layer test method for Protocol Control and Call Control
for non-Transit PINX
4.2.2 Segmentation and Protocol Discriminator Filter testing
As shown in figure 3, the IUT is the Segmentation and Protocol Discriminator Filter part and it is an
end-system. It is not possible to observe and control the upper service boundary of the IUT.
Consequently, the test method chosen is the Remote Test Method, where the co-ordination procedures
are expressed in an informal way. The test system will only contain one LT and no UT. The PCO, called
LSEG, is located between the Segmentation and Protocol Discriminator Filter part and the SCM. The
PDUs exchanged are SEGMENT PDUs and unsegmented PDUs.
TEST SYSTEM SUT
LT
Call Control and
Call Control and
Protocol Control
Protocol Control
IUT
SEGMENT PDUs
PSS1
Segmentation
Segmentation
and
unsegmented PDUs
P. D. Filter P. D. Filter
PCO : LSEG
SCM
Figure 3: Remote single layer test method for Segmentation and Protocol
Discriminator Filter
Page 14
ETS 300 805-2: February 1998
4.3 Multiple PCO testing
Multiple PCO testing applies to the PC and the CC for Transit PINX.
4.3.1 CC testing for a Transit PINX
As shown in figure 4, the IUT is the PC and CC part of the Transit PINX and it is an open-relay system.
Consequently, the test method chosen is a Multi-Party Test Method with no UT. The test system will
contain two LTs attached to the IUT via two PCOs, called LX and LY between the PC and CC part and the
Segmentation part. The PDUs exchanged are only unsegmented PDUs.
TEST SYSTEM
LOWER TESTER CONTROL FUNCTION
TCP
TCP
SUT (RELAY-SYSTEM)
LT1 LT2
IUT
Unsegmented
Unsegmented
Call Control  PDUs Call Control
PDUs
Call Control
and and
and
Protocol Control Protocol Control
Protocol Control
PCO : LX PCO : LY
PSS1
Segmentation Segmentation
Segmentation Segmentation
P. D. Filter P. D. Filter P. D. Filter
P. D. Filter
SCM SCM
Figure 4: Multi-party test method for PC and CC for Transit PINX
4.4 Test Configurations and use of concurrent TTCN
As this ATS covers both single-party testing using non-concurrent TTCN and multi-party testing using
concurrent TTCN, the notation chosen for the complete ATS is the concurrent TTCN syntax. Therefore,
test components are defined to describe the two configurations: the "mono" configuration and the "transit"
configuration, as shown in figures 5 and 6.
The mono configuration is used in case of single-party testing, i.e. for the PC testing, the CC testing for
non-transit PINX and the Segmentation and Protocol Discriminator Filter testing. Only one test
component, which is the Master Test Component (MTC) MTC_MONO, connected to the IUT via the
PCOs LX or LSEG, is needed in this case.

Page 15
ETS 300 805-2: February 1998
MTC_MONO
LX or LSEG
IUT
Figure 5: Mono configuration
The transit configuration is used in case of multi-party testing, i.e. for the PC and CC testing for transit
PINX. In this case, three test components are needed, these are the Master Test Component
MTC_TRANSIT and the two Parallel Test Components PTC_X and PTC_Y, which are connected to the
MTC via the two Co-ordination Points CPX and CPY. PTC_X and PTC_Y are further connected to the IUT
via the two PCOs LX and LY.
MTC_TRAN SIT
CPY
CPX
PTC_Y
PTC_X
LX LY
IU T
Figure 6: Transit configuration
5 Untestable Test Purposes (TPs)
Due to the ATMs chosen in this ATS or other restrictions, the following super test purposes have been
identified as being untestable and therefore have not been derived into final test purposes:
SP005, SP006, SP014, SP099, SP159, SP161, SP162, SP163, SP164.
6 Conformance clause
This specification is applicable to implementations which support either a Basic Rate or a Primary Rate
access interface, or both, operating over a leased line. A means of test may offer one or both access
types.
The test realizer shall comply with the requirements of ISO/IEC 9646-4 [7]; in particular, these concern the
realization of an executable Test Suite based on each ATS.

Page 16
ETS 300 805-2: February 1998
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [8].
A means of test conforming to this ATS shall implement at least a subset of test cases which is the
complete subset of test cases selected according to the selection expressions for a particular consistent
set of test suite parameters. Such a subset may include only test cases applicable to Transit PINX or End
PINX testing.
Certain test cases are selected only when the IUT is configured as A or as B. Therefore, in order to cover
all test cases applicable to an implementation, it is necessary to change the configuration and run the
omitted test cases with the appropriate changes to the Test Suite Parameter IUT_A.
7 ATS Conventions
This clause describes the conventions adopted in this ATS and gives the naming conventions used for the
different ATS elements.
7.1 Short names and abbreviations
Throughout the ATS short names and abbreviations for PDUs and Abstract Service Primitives (ASPs) are
used, also abbreviations for Information Elements are used. These are defined in tables 1 to 3.
Table 1: Short names and abbreviations for PDUs
PDU name Short Name Abbreviation
ALERTING ALERTING ALE
CALL PROCEEDING CALL_PROC CPR
CONNECT CONNECT CON
CONNECT ACKNOWLEDGE CONN_ACK COA
DISCONNECT DISCON DIS
FACILITY FACILITY FAC
INFORMATION INFO INF
NOTIFY NOTIFY NOT
PROGRESS PROGRESS PRO
RELEASE RELEASE REL
RELEASE COMPLETE REL_COM RLC
RESTART RESTART RES
RESTART ACKNOWLEDGE REST_ACK RSA
SETUP SETUP SET
SETUP ACKNOWLEDGE SETUP_ACK SUA
STATUS STATUS STA
STATUS ENQUIRY STAT_ENQ STQ
Error PDU (note 1) ERROR ERR
Q931 message (note 2) Q931MSG Q931
Generic message (note 3) GENERIC GEN
NOTE 1 ERROR_PDU is used for incorrectly coded messages sent by the tester which do not have
the correct structure for any valid message type.
NOTE 2: Q931MSG is used to receive any message without examining its contents.
NOTE 3: GENERIC is used for messages received by the tester where the message type may vary
but it is necessary to examine the contents of the message.

Page 17
ETS 300 805-2: February 1998
Table 2: Short names and abbreviations for ASPs
ASP name Short name Abbreviation
DL-DATA-REQUEST DL_DAT_REQ DLRQ
DL-DATA-INDICATION DL_DAT_IND DLIN
DL-ESTABLISH-REQUEST DL_EST_REQ DERQ
DL-ESTABLISH-INDICATION DL_EST_IND DEIN
DL-ESTABLISH-CONFIRM DL_EST_CON DECO
DL-RELEASE-REQUEST DL_REL_REQ DRRQ
DL-RELEASE-INDICATION DL_REL_IND DRIN
DL-RELEASE-CONFIRM DL_REL_CON DRCO
Table 3: Abbreviations for Information Elements
Information Element name Abbreviation
Protocol discriminator PD
Call Reference CR
Message type MT
Sending complete SC
Locking shift (note 1) LS
Bearer capability BCAP
Cause CAU
Called party number CDPN
Called party subaddress CDPS
Calling party number CGPN
Calling party subaddress CGPS
Channel identification CHI
Connected number CNDN
Connected subaddress CNDS
Call state CST
Facility FIE
High layer compatibility HLC
Low layer compatibility LLC
Notification indicator NOT
Party category PC
Progress indicator PI
Restart indicator RI
Transit counter TC
Unspecified IE (note 2) UNSP
NOTE 1: LS4 and LS5 are used as the abbreviations for locking shift to codesets 4 and 5.
NOTE 2: UNSP is used where an IE sent to the IUT does not have the structure of any valid IE.
7.2 Test Suite type, ASP type, PDU type and Alias identifiers
7.2.1 ASP type identifiers
The identifier of an ASP is the short name of the ASP.
EXAMPLE: DL_DAT_REQ is the DL-DATA-REQUEST ASP.
7.2.2 PDU type identifiers
The identifier of a PDU type is the short name of the PDU.
EXAMPLE: DISCON is the DISCONNECT PDU.
7.2.3 Test Suite type identifiers (Information Elements)
The identifier of a test suite type describing a single information element is the abbreviation for the IE with
the suffix "_TYP".
Page 18
ETS 300 805-2: February 1998
EXAMPLE 1: BCAP_TYP is the Bearer capability IE type.
The identifier for a type describing an invalid variant of an IE is the abbreviation for the IE with the suffix
"_TYP_BAD".
EXAMPLE 2: CR_TYP_BAD is a type for an invalid Call Reference IE.
The element (Field) names used within structured types which describing Information Elements (IEs)
consist of the abbreviation for the IE followed by an underscore, followed by, in abbreviated form and in
lower case, the name of the relevant field.
EXAMPLE 3: BCAP_codstd is the Coding Standard Field type of the Bearer Capability IE.
7.2.4 Aliases
Aliases are used in the ATS to show which PDU is being sent or received within an ASP. The identifiers
for aliases consist of the short name of the PDU, with the suffix "rq" used in aliases for DL_DAT_REQ
(PDUs sent by the tester) and the suffix "in" used in the case of aliases for DL_DAT_IND (PDUs received
by the tester).
EXAMPLE: CONN_ACKrq is an alias for DL_DAT_REQ used for sending a CONNECT
ACKNOWLEDGE message.
7.3 Identifiers concerning test configuration
7.3.1 Test components
The name of a MTC is composed of the prefix "MTC_", followed by a string in upper case identifying the
function of the MTC.
EXAMPLE 1: MTC_MONO is the Master Test Component used in the mono configuration.
The name of a Parallel Test Component (PTC) is composed of the prefix "PTC_", followed by an upper
case letter indicating which interface the PTC controls.
EXAMPLE 2: PTC_X is the Parallel Test Component representing the X interface of the IUT.
7.3.2 Test component configurations
The name of a configuration is composed of the prefix "Config_", followed by a name indicating the
function of the configuration. The first letter of this name is in upper case and the remainder in lower case.
EXAMPLE: Config_Transit is used for transit configuration.
The two figures in subclause 4.4 show a logical view of the configurations used.
7.3.3 Points of Control and Observations (PCOs)
The Point of Control and Observation identifiers are composed of "L" (for Lower tester) followed by an
upper case letter indicating the interface to which the PCO is connected.
EXAMPLE: LX is the PCO on interface X in the LT.
7.3.4 Co-ordination Points (CPs)
The Co-ordination Point (CP) identifiers are composed "CP" followed by an upper case letter indicating the
PTC with which the CP communicates. (All CPs used are between the MTC and one PTC)
EXAMPLE: CPX is a Co-ordination Point between the MTC_TRANSIT component and the
PTCX component.
Page 19
ETS 300 805-2: February 1998
7.3.5 Co-ordination Message (CM) types
The identifier of a Co-ordination Message type is a string in upper case.
EXAMPLE: READY is a CM used to request if, or to indicate that, a PTC is ready.
7.4 Test Suite Parameter and Selection Expression identifiers
7.4.1 Test suite parameters
Two categories of test suite parameters can be distinguished as follows;
- PICS category: those derived from the PICS proforma questions
- PIXIT category: those derived from the PIXIT proforma questions
and the latter can be further subdivided into the following parts;
- PIXIT values: parameters concerning the protocol itself
- Configuration parameters: parameters concerning the IUT configuration
- Values: values used within test cases
- Boolean: parameters indicting if the corresponding value is available.
All the PICS parameters and PIXIT parameters of the PIXIT values are boolean. The types of the
configuration values depend on the type of information represented by the parameter.
The identifier of the test suite parameter depends on whether it is a PICS or PIXIT parameter. In each
case it starts with a prefix identifying the category.
7.4.2 PICS Parameters
The identifiers of PICS parameters start with the prefix "PC_" followed by the reference of the item in the
relevant PICS.
EXAMPLE 1: PC_B3 relates to item B3 in the Basic Call PICS "Is the implementation capable
of functioning as a Transit PINX?",
7.4.3 PIXIT parameters
The identifiers of PIXIT parameters in the PIXIT values and configuration values categories start with the
prefix "PX_" or "tsp_" respectively. This is followed by a string of abbreviations, separated by underscores,
describing the meaning of the parameter as described in subclause 7.4.5.
EXAMPLE 1: PX_S0_ISset is a parameter meaning "Does the IUT support implicit sending of
SETUP in state 0".
EXAMPLE 2: tsp_InvNum is a parameter meaning "A number which the IUT can determine to
be invalid".
The identifiers of PIXIT parameters in the boolean configuration category are as the corresponding value
with the prefix "CO_" replacing "tsp_".
EXAMPLE 3: CO_InvNum is a parameter meaning "Is a number which the Iut can determine
to be invalid available".
7.4.4 Test case selection expressions
The identifiers of test case selection expressions consist of a string of abbreviations, separated by
underscores, describing the meaning of the parameter as described in subclause 7.4.5.
EXAMPLE: TR_ENT_TCC5_XS2 is a selection expression meaning when true "The IUT, as
a transit PINX, can enter state TCC5 with interface X in state 2".

Page 20
ETS 300 805-2: February 1998
7.4.5 Abbreviations used in PIXIT parameters and Test Case Selection Expressions
The abbreviations used in the PIXIT parameters and Test Case Selection Expressions are defined in
table 4. While it is possible to see from these abbreviations the approximate meaning of the parameter or
expression it is necessary to refer to the appropriate table in the TTCN ATS or the referenced PIXIT
question to determine the exact meaning.
Table 4
Abbreviation Meaning
OC, Out_Call Outgoing call
IC, In_Call Incoming call
TR Transit PINX
TE Terminating PINX
OI Originating PINX
OG Outgoing Gateway PINX
IG Incoming Gateway PINX
ENT Enters state
UN Unstable
S8 etc. State 8. etc. (If this is the last component it means that the IUT
can enter and is stable in the specified state. If it is followed by a
message it means that the IUT can send the message in the
specified state).
T304etc. Timer T304etc. implemented
no Number
rel Relays
REL etc. IUT can send RELEASE message etc. (Message abbreviations
are as defined in table?).
iREL etc. Implicit send of RELEASE possible etc.
iCLEAR Implicit clearing possible
imp Feature is implemented
retr Retransmits
onUNREC IUT sends message on receiving unrecognized message
onDLestCON IUT sends message on DL_ESTABLISH_CONFORM
TC IUT supports transit counter functions
TCinclude IUT includes transit counter IE
TClimit Limit for Transit Counter value
Ta Tones and Announcements associated with Call Clearing
PI etc. Including Progress Indicator IE etc. (IE abbreviations are as
defined in table 3
pref, excl Preferred, Exclusive (Values of Preferred/Exclusive bit)
unres, speech, audio, udi_ta Unrestricted Digital Info, Speech, 3.1kHz Audio, UDI with Tones
& announcements (Bearer Capabilities)
Bcap Bearer Capability IE
NoCLIR Without the Calling/Connected Line Identification Restriction
supplementary service being invoked.
Echnum, Echnum2 Valid channel numbers
Nechnum Invalid channel number
NoChans Number of channels available
(continued)
Page 21
ETS 300 805-2: February 1998
Table 4 (concluded)
Abbreviation Meaning
Cnum "Complete Number": a number which the IUT can determine to
be complete
Fnum "Full Number": a number which is complete in the numbering
plan implemented in the IUT and which the IUT may, or may not,
determine to be complete.
Inum "Incomplete number" a number which the IUT can to be
incomplete.
Onum "Overlap number": a number which the IUT cannot determine to
be complete (i.e. causes it to use overlap receiving).
Rnum "Routing Number": a number which is sufficient for the IUT to
route the call on a particular inter-PINX link, but is insufficient for
the IUT to determine to be complete
NRnum "Non-Routing Number" is a number is insufficient for the IUT (a
transit PINX) to determine is to be routed on a particular
inter-PINX link, but may, with the addition of further digits, so be
routed.
InvNnum "Invalid Number" : a number which the IUT can determine to be
unassigned in the numbering plan for which it is configured.
Tnum "Timer Number": a number which is complete in the numbering
plan that the IUT is configured for, but which the IUT cannot
determined to be complete (in the absence of Sending
complete) until expiry of T302
sXYnum Supplementary X-Y number (X and Y can be C, R or NR
representing Complete, Routing or non-Routing). This is a
number which when concatenated to the number given as an "X
number" produces a "Y number".
Cnum1 etc. First part of Cnum etc.
Pre Preceding PINX
Tester_NumDigits Number of terminal attached to tester as seen by IUT
Parts Number can be divided in parts
time time (duration)
len Length
7.5 Miscellaneous identifiers
7.5.1 Test Suite operations
The Test Suite operation identifiers are composed of string in lower case separated by underscore
characters ('_').
EXAMPLE: choose_bcap is used for returning the appropriate Information Transfer
Capability field of the Bearer Capability IE.
7.5.2 Test Suite constants
The Test Suite constant identifiers begin with the prefix 'C_', followed by a string identifying the function of
the constant. Where the constant represents the value of the message type for a specific message the
string consists of "MT" (the abbreviation for the Message Type IE) followed by the abbreviation for the
specific message. In other cases the string starts with the abbreviation for the appropriate IE and there is
no restriction in the characters in the remainder of the string.
EXAMPLE: C_MTCOA is the Message Type IE value of a CONNECT ACK message.
7.5.3 Test Suite variables
No Test Suite variables have been used in the ATS.

Page 22
ETS 300 805-2: February 1998
7.5.4 Test case variables
The Test Case Variable identifiers begin with the prefix "CV_", followed by a string with no restriction on
the type of characters.
EXAMPLE: CV_CRVALUE is a Call Reference Value used by one call between the IUT and
the tester.
7.5.5 Timers
The identifier for a test suite timer derived from a protocol timer defined in ETS 300 172 [1], is the name of
the timer from the base standard with the suffix "_max" or "_min" to indicate the minimum or maximum
duration of the timer.
EXAMPLE 1: T313_max is a test suite timer corresponding to the maximum duration of the
protocol timer T313.
The identifiers for other timers (e.g. those used while waiting for a response from the IUT) consist of "T_"
followed by a name in upper case.
EXAMPLE 2: T_REST is a timer for the response of the IUT to a RESTART message.
7.6 Constraints
7.6.1 TTCN Test Suite type constraints
Test suite type constraint identifiers consist of the abbreviation for the IE followed by two digits for a valid
constraint or one upper case letter (X or Y) and one digit for an erroneous constraint.
EXAMPLE 1: CHI01 is a constraint for the Channel Identification IE.
EXAMPLE 2: CAUX1 is a constraint of the Cause test suite type containing an error (reserved
value of location).
7.6.2 ASP constraints
The identifier for an ASP constraint is the abbreviation for the ASP. (There is never more than one
constraint for each ASP).
EXAMPLE 1: DLRQ, is a generic constraint for the DL_DAT_REQ primitive, for sending any
PDU to the IUT.
EXAMPLE 2: DLIN, is a generic constraint for the DL_DAT_IND primitive for receiving any
PDU from the IUT.
7.6.3 PDU constraints
PDU constraint identifiers consist
...