SIST ETS 300 806-2 E1:2005

SLOVENSKI STANDARD
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,610HGFHQWUDOQLVLJQDOL]DFLMVNL
SURWRNRO*HQHULþQLIXQNFLMVNLSURWRNRO]DSRGSRURGRSROQLOQLPVWRULWYDPGHO
$EVWUDNWQLSUHVNXãDOQLQL]$766SHFLILNDFLMD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Generic
functional protocol for the support of supplementary services; Part 2: Abstract Test Suite
(ATS) specification
Ta slovenski standard je istoveten z: ETS 300 806-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 806-2
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA-00110-2
ICS: 33.020
Key words: ATS, layer 3, PINX, PISN, QSIG, supplementary service, testing
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Generic functional protocol for the
support of supplementary services;
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 806-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 806-2: February 1998
Contents
Foreword .5
1 Scope .6
2 Normative references.6
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Abstract Test Method (ATM).8
4.1 Choice of the ATM .8
4.1.1 Functional subsets .8
4.1.2 PINX Role and Test Component Configuration considerations .9
4.2 Single PCO testing.9
4.2.1 Testing of End PINX and Transit PINX (single Transit interface active) .9
4.3 Multiple PCO testing .10
4.3.1 Testing of transit PINX (dual transit interfaces active) .10
4.4 Test configurations and use of concurrent TTCN.11
5 Untestable Test Purposes.12
6 Conformance clause .13
7 ATS Conventions .14
7.1 Short names and abbreviations .14
7.2 Test suite type, Abstract Service Primitive type (ASP), PDU and alias identifiers.15
7.2.1 ASP type identifiers .15
7.2.2 PDU type identifiers.15
7.2.3 Test Suite Type identifiers (IEs) .15
7.2.4 ASN.1 types.16
7.2.5 Aliases.16
7.3 Identifiers concerning test configuration .16
7.3.1 Test components.16
7.3.2 Test component configurations.17
7.3.3 Points of Control and Observations (PCOs) .17
7.3.4 Co-ordination Points (CPs).17
7.3.5 Co-ordination Message types.17
7.4 Test Suite Parameter and Selection Expression identifiers.17
7.4.1 Test suite parameters .17
7.4.2 PICS parameters.18
7.4.3 PIXIT parameters .18
7.4.4 Test Case Selection Expressions .18
7.4.5 Abbreviations used in PIXIT parameters and Test Case Selection
Expressions.18
7.5 Miscellaneous identifiers.19
7.5.1 Test suite operations.19
7.5.2 Test suite constants .19
7.5.3 Test suite variables .19
7.5.4 Test case variables .20
7.5.5 Timers .20
7.6 Constraints.20
7.6.1 TTCN Test suite type constraints.20
7.6.2 ASN.1 type constraints.20
7.6.3 ASP constraints.20
7.6.4 PDU constraints .21
7.6.5 CM constraints .21

Page 4
ETS 300 806-2: February 1998
7.7 Dynamic part . 21
7.7.1 Test Case identifiers. 21
7.7.2 Test Step identifier. 21
7.7.3 Default identifier. 22
7.8 Notation. 22
8 Test case and test purpose mapping . 22
Annex A (normative): Partial PIXIT proforma . 23
A.1 Identification summary. 23
A.2 ATS summary. 23
A.3 Test laboratory. 23
A.4 Client identification. 23
A.5 SUT. 23
A.6 Protocol layer information. 24
A.6.1 Protocol identification . 24
A.6.2 IUT information. 24
A.6.2.1 Call Independent Signalling Connection (CISC). 24
A.6.2.2 Call Related Signalling. 27
Annex B (normative): Protocol Conformance Test Report (PCTR) Proforma for GFP . 28
B.1 Identification summary. 28
B.1.1 Protocol conformance test report. 28
B.1.2 IUT identification. 28
B.1.3 Testing environment. 28
B.1.4 Limits and reservation . 29
B.1.5 Comments. 29
B.2 IUT Conformance status. 29
B.3 Static conformance summary. 29
B.4 Dynamic conformance summary. 29
B.5 Static conformance review report . 30
B.6 Test campaign report. 30
B.7 Observations. 34
Annex C (normative): Abstract Test Suite (ATS) for GFP . 35
C.1 The TTCN Graphical form (TTCN.GR) .35
C.2 The TTCN Machine Processable form (TTCN.MP) . 35
History. 36

Page 5
ETS 300 806-2: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the standardizing Information
and Communication Systems Association (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; Generic Functional Protocol (GFP) for the support of supplementary
services". The title of each part is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS & TP)";
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 6
ETS 300 806-2: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) specification
for the core part of the Generic Functional Protocol (GFP) for the support of supplementary services of the
Inter-exchange signalling protocol, for Private Integrated Services Networks (PISN).
The core part of the GFP excludes the connectionless Application Packet Data Unit (APDU) transport
mechanism, the Data Service Element (DSE) protocol, the Application Control Service Element (ACSE)
protocol, procedures for carrying manufacturer specific information and requirements only relevant to
Originating PINXs for calls and Call Independent Signalling Connections (CISCs) or source PINXs for
APDUs and notifications.
The objective of this ETS is to provide conformance tests which give a high probability of inter-operability.
This ETS covers the core part of the procedures described in ETS 300 239 [1].
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6]
and ISO/IEC 9646-3 [7] including Amendment 1 [8]) is used as basis for the test methodology.
This ETS is applicable to implementations which support either a Basic Rate (BR) or a Primary Rate
Access (PRA) interface, or both, operating over a leased line. It is applicable to PINXs acting as both
transit or end PINXs for calls and Call Related Signalling Connections (CRSC), however it does not
include test cases applicable to end PINXs acting as source or originating PINXs.
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 239 (1995): "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Generic functional protocol for the support of
supplementary services".
[2] ETS 300 172 (1995): "Private Integrated Services Network (PISN);
Inter-exchange Signalling protocol; Circuit Mode Basic Services".
[3] ETS 300 806-1 (1996): "Private Integrated Services Networks (PISN);
Inter-exchange signalling protocol; Generic Functional Protocol for the support
of supplementary services; Test Suite Structure and Test Purposes (TSS&TP)".
[4] ETS 300 805-2 (1996): "Private Integrated Services Networks (PISN);
Inter-exchange signalling protocol; Circuit Mode Basic Services; Network Layer
(NL); Abstract Test Suite Specification (ATS)".
[5] ISO/IEC 9646-1 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 1:
General Concepts".
[6] ISO/IEC 9646-2 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 2:
Abstract Test Suite Specification".

Page 7
ETS 300 806-2: February 1998
[7] ISO/IEC 9646-3 (1992): "Information Technology - Opens 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).
[8] ISO/IEC 9646-3 AM2 (1997): "Amendment 1 to ISO/IEC 9646-3: 1992 Further
extensions" .
[9] ISO/IEC 9646-4 (1994): "Information Technology - Open Systems
Interconnection - Conformance Testing Methodology and Framework - Part 4:
Test Realization".
[10] 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".
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 [5].
application layer: For the purposes of this ETS, this refers to the procedures described as such in
ETS 300 239 [1], subclause 6.2.
Implementation Under Test (IUT): See ISO/IEC 9646-1 [5].
Lower Tester (LT): See ISO/IEC 9646-1 [5].
Network Layer: For the purposes of this ETS, this refers to the procedures described as such in
ETS 300 239 [1] subclause 6.2.
originating PINX: See ETS 300 239 [1].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5].
PICS proforma: See ISO/IEC 9646-1 [5].
Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [5].
PIXIT proforma: See ISO/IEC 9646-1 [5].
Signalling Carriage Mechanism (SCM): See ETS 300 172 [2].
super test purpose: See ETS 300 806-1 [3].
System Under Test (SUT): See ISO/IEC 9646-1 [5].
terminating PINX: See ETS 300 239 [1].
transit PINX: See ETS 300 239 [1].
Upper Tester (UT): See ISO/IEC 9646-1 [5].

Page 8
ETS 300 806-2: February 1998
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ACSE Application Control Service Element
APDU Application Packet Data Unit
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
CF Co-ordination Function
CISC Call Independent Signalling Connection
CM Co-ordination Message
CP Co-ordination Point
CTP Combined Test Purpose
DSE Data Service Element
ETS Executable Test Suite
GFP Generic Functional Protocol
GFTC Generic Functional Transport Control
IUT Implementation Under Test
LT Lower Tester
MTC Master Test Component
PC Protocol Control
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PINX Private Integrated Services Network Exchange
PISN Private Integrated Services Network
PIXIT Protocol Implementation eXtra Information for Testing
PSS1 Private Integrated Signalling System No.1
PTC Parallel Test Component
ROSE Remote Operation Service Element
RTM Response Test Method
SS Switching System
SUT System Under Test
TC Test Case
TP Test Purpose
TTCN Tree and Tabular Combined Notation
4 Abstract Test Method (ATM)
This clause describes the different ATMs used for testing the GFP. Two methods are applied; the Remote
test method, and the Multi-Party test method.
4.1 Choice of the ATM
4.1.1 Functional subsets
The GFP is divided into a number of entities as shown in figure 1. This ATS is principally concerned with
the testing of the Protocol Control (PC) and Generic Functional Transport Control (GFTC) entities,
however it also contains Test Cases (TCs) concerning some error handling functions of the Co-ordination
and ROSE entities.
NOTE: Valid behaviour of the application layer is supplementary service specific and its testing
is specified in test specifications for individual supplementary services (if any). DSE
requirements are excluded from the scope of this ETS.
The testing of all these layers is performed using a PCO at the SCM/Network layer boundary.

Page 9
ETS 300 806-2: February 1998
SS
ROSE DSE ACSE
Application
Control
Layer
Coordination
Function
GFP
Generic Functional
Network Transport Control
Layer
Protocol Control
Layer 2
SCM
Layer 1
NOTE: Grey shading indicates entities not part of the GFP.
Figure 1: GFP functional subsets
4.1.2 PINX Role and Test Component Configuration considerations
A PINX may act either in the role of an End PINX or in the role of a Transit PINX in the context of each
Basic Call or CISC. A particular PINX may be capable of acting in one or both roles. Whereas the Generic
Functional Transport Control (GFTC) requirements generally depend on which role is involved, the
Protocol Control (PC) requirements do not.
Depending on the role of the PINX, it may be necessary to use different procedures in the preambles to
achieve the pre-condition in some TPs concerned with PC requirements. For these cases, which will
require different test component configurations, there may be two separate Test Cases (TCs), one for
each role, generated from each relevant TP.
4.2 Single PCO testing
Single PCO testing applies to all aspects of the testing of the IUT as an End PINX. It is also used for those
tests as a Transit PINX when events at the outgoing side are not required to be tested and when no
activity is expected at the outgoing side, i.e. only one interface is reacting.
4.2.1 Testing of End PINX and Transit PINX (single Transit interface active)
As shown in figure 2, the ROSE, Co-ordination Function (CF), GFTC and Protocol Control (PC) part, is
considered to be the IUT, and 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 LX, is located between the ROSE, Co-ordination Function, Generic Functional
Transport Control and Protocol Control part, and the segmentation part. Only unsegmented Protocol Data
Units (PDUs) are exchanged.
Page 10
ETS 300 806-2: February 1998
TEST SYSTEM SUT
IUT
LT
ROSE, DSE, ACSE ROSE, DSE, ACSE
Application
Coordination Coordination
Unsegmented
Layer
Function, Function,
PDUs
Generic Functional Generic Functional
Transport Control, Transport Control,
Protocol Control Protocol Control
PCO : LX Network Layer
Segmentation
Segmentation
P. D. Filter
P. D. Filter
SCM
Figure 2: Remote single layer test method for testing of end PINX and transit PINX (single transit
interface active)
4.3 Multiple PCO testing
Multiple PCO testing applies to the testing of the IUT as a transit PINX, except for tests were no events on
the outgoing side are expected. The two interfaces are active.
4.3.1 Testing of transit PINX (dual transit interfaces active)
As shown in figure 3, the ROSE, CF, GFTC and PC part is considered to be the IUT, and 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, located between the ROSE, CF
and PCl part, and the segmentation part. The PDUs exchanged are only unsegmented PDUs.

Page 11
ETS 300 806-2: February 1998
TEST SYSTEM
LOWER TESTER CONTROL FUNCTION
TCP
TCP
SUT (RELAY-SYSTEM)
LT1 LT2
IUT
ROSE, DSE, ACSE ROSE, DSE, ACSE
ROSE, DSE, ACSE
-
Coordination Coordination
Coordination
Unsegmented Unsegmented
Function, Function,
Function,
PDUs
PDUs
Generic Functional Generic Functional
Generic Functional
Transport Control, Transport Control,
Transport Control,
Protocol Control Protocol Control
Protocol Control
Network
PCO : LX
PCO : LY
Layer
Segmentation Segmentation
Segmentation Segmentation
P. D. Filter P. D. Filter
P. D. Filter P. D. Filter
SCM
SCM
Figure 3: multi-party test method for testing of transit PINX (dual transit interfaces active)
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 figure 4 and 5.
The mono configuration is used in case of single-party testing, i.e. for the following:
- ROSE testing;
- CF testing;
- GFTC testing;
- PC testing,
for End PINX and Transit PINX (single Transit interface active).
Only one test component, which is the Master Test Component MTC_MONO, connected to the IUT via
the PCO LX, is needed in this case.

Page 12
ETS 300 806-2: February 1998
MTC_MONO
LX
IUT
Figure 4: Mono configuration
The transit configuration is used in case of multi-party testing, i.e. for the following:
- ROSE testing;
- CF testing;
- GFTC testing;
- PC testing,
for transit PINX (dual transit interfaces active).
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 Master Test
Component 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_TRANSIT
CPY
CPX
PTC_Y
PTC_X
LX LY
IUT
Figure 5: Transit configuration
5 Untestable Test Purposes
Due to the ATMs chosen in this ATS or other restrictions, the following test purposes have been identified
as being untestable, and therefore have not been derived into test cases.

Page 13
ETS 300 806-2: February 1998
The following TPs are applicable to both Transit and End PINX roles and are untestable for both:
TP2042
TP2073
TP2139
TP2140
TP2210
TP2213
TP2217
TP2218
TP2249
TP2251
TP2254
The following TPs are applicable to both Transit and End PINX roles and are untestable for End PINX
only:
TP2014
TP2016
TP2017
TP2049
TP2057
TP2058
TP2076
TP2077
TP2085
TP2167
TP2168
TP2170
TP2171
TP2172
TP2174
TP2177
TP2178
TP2181
TP2182
TP2183
TP2184
TP2185
TP2191
TP2253
The following TPs are applicable to End PINX only and are untestable:
TP2164
TP2195
6 Conformance clause
This ETS is applicable to implementations which support either a BRA or a PRA interface, or both,
operating over a leased line. A means of test may offer one or both access types.
The test realiser shall comply with the requirements of ISO/IEC 9646-4 [9]; in particular, these concern the
realization of an ETS based on each ATS.
Test laboratories running conformance test services using this ATS shall comply with
ISO/IEC 9646-5 [10].
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.
Page 14
ETS 300 806-2: February 1998
7 ATS Conventions
This clause describes the conventions adopted in this ATS and gives the naming conventions chosen for
the different ATS elements. In general if a name is used, both in this ETS and also in ETS 300 805-2 [4],
the name will refer to the same thing, even though the definitions may not be identical. For example,
additional IEs, corresponding to differences between ETS 300 239 [1] and ETS 300 172 [2], may be
permitted in the definition in this ETS .
7.1 Short names and abbreviations
Throughout the ATS short names and abbreviations for PDUs and ASPs are used, also abbreviations for
IEs 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_PDU 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.
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-CONFIRM DL_REL_CON DRCO

Page 15
ETS 300 806-2: February 1998
Table 3: Abbreviations for IE
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, Abstract Service Primitive type (ASP), PDU 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 (IEs)
The identifier of a test suite type describing a single information element is the abbreviation for the IE with
the suffix "_TYP".
EXAMPLE 1: FIE_TYP is the facility IE type.
The identifier for a set or sequence of IEs of the same type is the abbreviation for the IE with the suffix
"s_TYP".
EXAMPLE 2: FIEs_TYP is a type for a set of one or more Facility IEs.
The identifier for a type describing an invalid variant of an IE is the abbreviation for the IE with the suffix
"_TYP_BAD".
Page 16
ETS 300 806-2: February 1998
EXAMPLE 3: FIE_TYP_BAD is a type for an invalid Facility IE.
The element (field) names used within structured types which describing 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 4: FIE_protprof is the Protocol Profile field of the Facility IE.
7.2.4 ASN.1 types
ASN.1 types corresponding to IEs, have identifiers according to subclause 7.2.3. Other ASN.1 types taken
from ETS 300 239 [1] have, whenever possible, the same identifier names as the ASN.1 type names used
in those standards. In some cases it is necessary to replace a hyphen character ("-") with an underscore
character ("_") to satisfy the TTCN syntax. Where an ASN.1 type is used to replace an ASN.1 macro, the
identifier is the name of the macro with the first letter in upper case and the remainder of the name in
lower case (the macro name is specified with all upper case characters).
In other cases the identifier consists of one or more words, with the first letter of each word in upper case,
and the remaining letters in the word, in lower case.
EXAMPLE 1: PrivateTypeOfNumber is the ASN.1 PrivateTypeOfNumber type from
ETS 300 239 [1].
EXAMPLE 2: Operation is the ASN.1 type replacing the OPERATION macro.
The identifier of an ASN.1 named type (i.e. the name of a field within a type defined in ASN.1), the
identifier of an ASN.1 named number or the identifier of a value of an ASN.1 enumerated type is
composed of a string of concatenated words, all but the first word (which begins with a lower case letter),
beginning with an uppercase letter, with the remainder of the word in lower case. Where these named
types, named numbers or values of enumerated types are taken from ETS 300 239 [1] the same
identifiers have been used as in those standards, subject to the same restrictions as for type identifiers.
EXAMPLE 3: sourceEntity is the identifier of the ASN.1 named type sourceEntity in the
ASN.1 NetworkFacilityExtension type from ETS 300 239 [1].
EXAMPLE 4: discardAnyUnrecognizedInvokePdu is the identifier of one named number of
the ASN.1 InterpretationAPDU enumerated type from ETS 300 239 [1].
NOTE: Due to the TTCN static semantics, it has been necessary to define new intermediate
ASN.1 types (e.g. RoseErrors), consisting of some named numbers from INTEGER
types or values of ENUMERATED types, in order to avoid multiple definitions of items
with the same name.
7.2.5 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 an Master Test Component (MTC) is composed of the prefix "MTC_", followed by a string in
upper case identifying the function of the MTC.

Page 17
ETS 300 806-2: February 1998
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 PTC 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 PCO identifiers are composed of "L" (for Lower tester) followed by an upper case letter indicating the
interface that the PCO is connected to.
EXAMPLE: LX is the PCO on interface X in the LT.
7.3.4 Co-ordination Points (CPs)
The CP identifiers are composed "CP" followed by an upper case letter indicating the PTC the CP
communicates with. (All CPs used are between the MTC and one PTC)
EXAMPLE: CPX is a Co-ordination Point between the MTC_TRANSIT component and the
PTC_X component.
7.3.5 Co-ordination Message types
The identifier of a CM 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.

Page 18
ETS 300 806-2: February 1998
7.4.2 PICS parameters
The identifiers of PICS parameters start with the prefix "PC_" followed by "BC_" or "GFP_" to indicate
whether the parameters is from the basic call PICS (ETS 300 172 [2], annex A) or the GFP PICS
(ETS 300 239 [1], annex A). This is followed by the reference of the item in the relevant PICS.
EXAMPLE 1: PC_GFP_ C1 relates to item C1 in the GFP PICS "Does the PINX support
connection-oriented APDU transport?".
EXAMPLE 2: PC_BC_B3 relates to item B3 in the basic ball PICS "Is the implementation
capable of functioning as a Transit PINX?".
NOTE: The corresponding PICS parameters for Basic Call in the basic call ATS
(ETS 300 805-2 [4]) does not include the "BC_" in the identifier.
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_CISC_T303 is a parameter meaning "Does the IUT support timer T303 for a
CISC".
EXAMPLE 2: tsp_OpValue is a parameter meaning "Operation value which the IUT can
understand".
The identifiers of PIXIT parameters in the boolean configuration category are as the corresponding value
with the prefix "CO_" replacing "tsp_".
EXAMPLE 3: CO_OpValue is a parameter meaning "Is an operation value which the IUT can
understand available".
The identifiers for PIXIT parameters do not depend on whether the parameter is derived from the GFP
PIXIT (annex A of this ETS) or the Basic Call PIXIT (ETS 300 805-2 [4], annex A).
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: CISC_TR_S8_T313 is a selection expression meaning when true "The IUT can
enter state 8 for CISCs as a transit PINX and supports T313 in that situation.
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.

Page 19
ETS 300 806-2: February 1998
Table 4: Abbreviations used in PIXIT parameters and Test Case Selection Expressions
Abbreviation Meaning
CISC Call Independent Signalling Connection
TR Transit PINX
TE Terminating PINX
EN End PINX
TE_ONLY IUT can only act as a terminating PINX (not transit)
EN_ONLY IUT can only act as an End PINX (not transit)
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)
T303 etc. Timer T303 etc. implemented
REL etc. IUT can sent RELEASE message etc. (Message abbreviations
are as defined in table 1
iREL etc. Implicit send of RELEASE possible
iCLEAR Implicit clearing possible
STx IUT sends STATUS or STATUS ENQUIRY message
imp Feature is implemented
OpValue Operation Value which the IUT understands
OpArgument Argument for use with OpValue
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
Bcap Bearer Capability IE
Echnum Valid channel number
CISCnum Number for CISCs
NFEnum PINX address (for use in NFE)
INVnum Invalid number
NRnum Insufficient number for routing
Fnum Complete number (whether or not IUT can determine it to be
complete)
Cnum Number the IUT can determine to be complete
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 (ITC) 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 20
ETS 300 806-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 239 [1] or
ETS 300 172 [2] 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 errone
...