ETSI ETS 300 806-2 ed.1 (1998-02)

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

DE/ECMA-00110-2

Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Generični funkcijski protokol za podporo dopolnilnim storitvam - 2. del: Abstraktni preskušalni niz (ATS) - Specifikacija

General Information

• Status: Published
• Publication Date: 09-Feb-1998
• Technical Committee: Ecma - Standardizing information and communications systems
• Current Stage: 12 - Completion
• Due Date: 13-Feb-1998
• Completion Date: 10-Feb-1998
• Mandate: IT-74
• Mandate: T-245
• Ref Project: SIST ETS 300 806-2 E1:2005 - 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

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 806-2 E1:2005
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
SIST ETS 300 806-2 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 806-2 E1:2005

---------------------- Page: 2 ----------------------

SIST ETS 300 806-2 E1:2005
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: [e-mail]
Tel.: [phone] - Fax: [phone]
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: 3 ----------------------

SIST ETS 300 806-2 E1:2005
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: 4 ----------------------

SIST ETS 300 806-2 E1:2005
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: 5 ----------------------

SIST ETS 300 806-2 E1:2005
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: 6 ----------------------

SIST ETS 300 806-2 E1:2005
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: 7 ----------------------

SIST ETS 300 806-2 E1:2005
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: 8 ----------------------

SIST ETS 300 806-2 E1:2005
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: 9 ----------------------

SIST ETS 300 806-2 E1:2005
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: 10 ----------------------

SIST ETS 300 806-2 E1:2005
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: 11 ----------------------

SIST ETS 300 806-2 E1:2005
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: 12 ----------------------

SIST ETS 300 806-2 E1:2005
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: 13 ----------------------

SIST ETS 300 806-2 E1:2005
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: 14 ----------------------

SIST ETS 300 806-2 E1:2005
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: 15 ----------------------

SIST ETS 300 806-2 E1:2005
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 Abbrev
...