SIST EN 301 490-2 V1.1.1:2005

SLOVENSKI STANDARD
SIST EN 301 490-2 V1.1.1:2005
01-april-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,61±6LJQDOL]DFLMVNLSURWRNROPHG
FHQWUDODPL±'RSROQLOQDVWRULWHYSUHGDMDNOLFD]DYVWRSQRWRþNR931EVWRULWYH±
GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMH
GHOQHL]YHGEHSURWRNROD3,;,7±3URIRUPD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call
transfer supplementary service for the VPN b service entry point; Part 2: Abstract Test
Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification
Ta slovenski standard je istoveten z: EN 301 490-2 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 301 490-2 V1.1.1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 301 490-2 V1.1.1:2005

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

SIST EN 301 490-2 V1.1.1:2005
ETSI EN 301 490-2 V1.1.1 (2000-12)
European Standard (Telecommunications series)
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Call transfer supplementary service
for the VPN "b" service entry point;
Part 2: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma


---------------------- Page: 3 ----------------------

SIST EN 301 490-2 V1.1.1:2005
2 ETSI EN 301 490-2 V1.1.1 (2000-12)
Reference
DEN/SPAN-05190-3
Keywords
PISN, VPN, PSS1, CT, SS-CT, testing, TSS&TP,
ATS, CCS, PIXIT, QSIG, stage 3, supplementary
service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33492 94 4200 Fax: +33493 65 4716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI

---------------------- Page: 4 ----------------------

SIST EN 301 490-2 V1.1.1:2005
3 ETSI EN 301 490-2 V1.1.1 (2000-12)
Contents
Intellectual Property Rights .5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.7
3.1 Definitions . 7
3.2 Abbreviations. 7
4 Abstract Test Method (ATM).7
4.1 Description of ATM used . 7
5 Untestable test purposes.8
6 ATS conventions .8
6.1 Version of TTCN used . 8
6.2 Use of ASN.1. 8
6.2.1 Situations where ASN.1 is used. 8
6.2.2 Specification of encoding rules. 9
7 ATS to TP map.9
8 PCTR conformance .10
9 PIXIT conformance .10
10 ATS conformance.10
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma .11
A.1 Identification summary .11
A.1.1 Protocol conformance test report. 11
A.1.2 IUT identification. 11
A.1.3 Testing environment. 11
A.1.4 Limits and reservations. 12
A.1.5 Comments. 12
A.2 IUT conformance status.12
A.3 Static conformance summary .12
A.4 Dynamic conformance summary.12
A.5 Static conformance review report.13
A.6 Test campaign report .13
A.7 Observations.15
Annex B (normative): Partial PIXIT proforma.16
B.1 Identification summary .16
B.2 Abstract test suite summary .16
B.3 Test laboratory.16
B.4 Client (of the test laboratory) .17
B.5 System Under Test (SUT).17
B.6 Protocol information.18
B.6.1 Protocol identification . 18
ETSI

---------------------- Page: 5 ----------------------

SIST EN 301 490-2 V1.1.1:2005
4 ETSI EN 301 490-2 V1.1.1 (2000-12)
B.6.2 IUT information . 18
B.6.2.1 Parameter values. 18
B.6.2.2 Timer values. 18
B.6.2.3 Information parameter values . 19
B.7 Basic call PIXIT items .20
B.7.1 Parameter values - information element coding. 20
Annex C (normative): Abstract Test Suite (ATS).21
C.1 The TTCN Graphical form (TTCN.GR).21
C.2 The TTCN Machine Processable form (TTCN.MP) .21
Bibliography.22
History .23
ETSI

---------------------- Page: 6 ----------------------

SIST EN 301 490-2 V1.1.1:2005
5 ETSI EN 301 490-2 V1.1.1 (2000-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 2 for a multi-part deliverable covering the Inter-exchange signalling protocol for Call
Transfer supplementary service for the VPN "b" service entry point, as described below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 2: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma".
National transposition dates
Date of adoption of this EN: 15 December 2000
Date of latest announcement of this EN (doa): 31 March 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 2001
Date of withdrawal of any conflicting National Standard (dow): 30 September 2001
ETSI

---------------------- Page: 7 ----------------------

SIST EN 301 490-2 V1.1.1:2005
6 ETSI EN 301 490-2 V1.1.1 (2000-12)
1 Scope
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma for the VPN "b" reference point of implementations conforming to the standard for the
Call Transfer supplementary service (SS-CT) as described in ETS 300 261 [1].
EN 301 490-1 [5] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXIT
proforma specification.
2 References
The following documents contain provisions, which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI ETS 300 261 (1995): "Private Integrated Services Network (PISN); Inter-exchange
signalling protocol; Call transfer supplementary service [ISO/IEC 13869 (1995) modified]".
[2] ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 2: Abstract test suite specification".
[3] ETSI TR 101 101 (V1.1.1): "Methods for Testing and Specification (MTS); TTCN interim version
including ASN.1 1994 support [ISO/IEC 9646-3] (Second Edition Mock-up for JTC1/SC21
Review)".
[4] ISO/IEC 8825-1 (1994): "Information technology - Encoding Rules for Abstract Syntax Notation
One (ASN.1) - Part 1: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules
(CER) and Distinguished Encoding Rules (DER)". (See also ITU-T Recommendation X.690).
[5] ETSI EN 301 490-1: "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Call transfer supplementary service for the VPN "b" service entry point; Part 1: Test
Suite Structure and Test Purposes (TSS&TP) specification".
[6] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework".
[7] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[8] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment".
[9] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
ETSI

---------------------- Page: 8 ----------------------

SIST EN 301 490-2 V1.1.1:2005
7 ETSI EN 301 490-2 V1.1.1 (2000-12)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [6] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
ETS Executable Test Suite
IUT Implementation Under Test
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SS-CT Call Transfer Supplementary Service
SUT System Under Test
TP Test Purpose
TTCN Tree and Tabular Combined Notation
VPN Virtual Private Network
4 Abstract Test Method (ATM)
4.1 Description of ATM used
The multi-party test method is applied for testing the IUT. The general configuration used is shown in figure 1.
A Point of Control and Observation (PCO) resides at the service access point between layers 2 and 3 in the test system.
The PCO used by the MTC is named "L0" (for Lower) and the PCO used by the PTC is named "L1". These PCOs are
used to control and observe the behaviour of the Implementation Under Test (IUT) and test case verdicts are assigned
depending on the behaviour observed at these PCOs.
A third "informal" PCO, called "O" (for Operator) is used to specify control but not observation above the IUT; events
at this PCO are never used to generate test case verdicts. Messages sent by the tester at this PCO explicitly indicate to
the operator actions, which are to be performed on the SUT. This is regarded as a preferred alternative to the use of the
implicit send event.
ETSI

---------------------- Page: 9 ----------------------

SIST EN 301 490-2 V1.1.1:2005
8 ETSI EN 301 490-2 V1.1.1 (2000-12)
PTC_D
CPA_D
MTC
PTC1
CPA1
Informal test
PCO PCO PCO
co-ordination by
operator
L0 L1 O
IUT
Figure 1: Multi-party test method
Not all components are used in every test case and the relationship between the IUT and the tester depends on the test
group:
• when the IUT is in the Authentication configuration, the IUT is only connected to the MTC. The verdict depends
only on the behaviour observed at the PCO between the IUT and the MTC. The PTC1 and PTC_D are not used.
• when the IUT is in the Home and Visitor configuration, the PTC1 and the MTC are both used. The verdict is
assigned by the MTC or the PTC1 depending on the test purpose. The PTC_D and PCO O are used to specify
control above the IUT.
5 Untestable test purposes
There are no untestable test cases associated with this ATS and ATM.
6 ATS conventions
6.1 Version of TTCN used
The version of TTCN used is that defined in TR 101 101 [3].
6.2 Use of ASN.1
6.2.1 Situations where ASN.1 is used
ASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that "pure" TTCN
cannot. For instance, data structures modelling ordered or unordered sequences of data are preferably defined in ASN.1.
Second, ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions. Third, it is
necessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the base
standards in ASN.1.
The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.
ETSI

---------------------- Page: 10 ----------------------

SIST EN 301 490-2 V1.1.1:2005
9 ETSI EN 301 490-2 V1.1.1 (2000-12)
6.2.2 Specification of encoding rules
There is a variation in the encoding rules applied to ASN.1 types and constraints specified in the present document and
therefore a mechanism is needed to differentiate the encoding rules. However the mechanism specified in
ISO/IEC 9646-3 [7] and in TR 101 101 [3] does not facilitate definition of the encoding rules as needed for this ATS. A
solution is therefore used which is broadly in the spirit of ISO/IEC 9646-3 [7] in which comment fields have been used
as a means of encoding rules.
For ASN.1 used in the present document, two variations of encoding rules are used. One is the commonly known Basic
Encoding Rules (BER) as specified in ISO/IEC 8825-1 [4]. In the second case the encoding is according to ISDN,
i.e. the ASN.1 data types are a representation of structures contained within the ISDN specification (basic call, Generic
functional protocol or individual supplementary service). For example, if octets of an information element are specified
in ASN.1 as a SEQUENCE then this should be encoded in an Executable Test Suite (ETS) as any other ISDN
information element specified using tabular TTCN. This ISDN encoding variation is the default encoding rule for this
ATS. This means that all ASN.1 constraint tables are encoded using ISDN (non-BER) encoding unless stated otherwise.
BER encoding should never be applied to an ASN.1 constraint where BER encoding has not been specified. This
encoding rule is sometimes named "Direct Encoding".
For BER encoding, an indication is given in the comments field of the table header. For this ATS such indications
appear in the ASN.1 type constraint declaration tables only. In the first line of the table header comment field, the
notation "ASN1_Encoding: BER"isused.
In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.
Table 1: ASN.1 type constraint declaration showing use of encoding variation
ASN.1 Type Constraint Declaration
Constraint Name : CallTransferComplete_inv_S1 (INV_ID: InvokeIDType
ASN.1 Type : Component
Derivation Path :
Encoding Variation :
Comments : ASN1_Encoding: BER
Description
callTransferComplete_Comp
callTransferComplete_InvokeComp {
invokeID INV_ID,
operation_value localValue 12,
argument {
endDesignation primaryEnd,
callStatus answered }}
Detailed comments :
7 ATS to TP map
The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.
ETSI

---------------------- Page: 11 ----------------------

SIST EN 301 490-2 V1.1.1:2005
10 ETSI EN 301 490-2 V1.1.1 (2000-12)
8 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [8], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [8].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a
client to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A.
A PCTR, which conforms to this PCTR proforma specification, shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
9 PIXIT conformance
A test realizer, producing an executable test suite for the ATS specification contained in annex C, is required, as
specified in ISO/IEC 9646-4 [9], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT
proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a
minimum, have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may
contain additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular
IUT.
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [8], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma
conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents
which are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be
answered in order to prepare the test laboratory for a particular IUT.
10 ATS conformance
The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of
ISO/IEC 9646-4 [9]. In particular, these concern the realization of an ETS based on each ATS. The test realizer shall
provide a statement of conformance of the MOT to this ATS specification.
An EN/ETS, which conforms to this ATS specification, shall contain test groups and test cases, which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall
be capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each test
case.
Test laboratories running conformance test services using the present document shall comply with ISO/IEC 9646-5 [8].
A test laboratory, which claims to conform to this ATS specification, shall use a MOT which conforms to the present
document.
ETSI

---------------------- Page: 12 ----------------------

SIST EN 301 490-2 V1.1.1:2005
11 ETSI EN 301 490-2 V1.1.1 (2000-12)
Annex A (normative):
Protocol Conformance Test Report (PCTR) proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PCTR.
A.1 Identification summary
A.1.1 Protocol conformance test report
PCTR number:
PCTR date:
Corresponding SCTR number:
Corresponding SCTR date:
Test laboratory identification:
Test laboratory manager:
Signature:
A.1.2 IUT identification
Name:
Version:
Protocol specification: ETS 300 261
PICS:
Previous PCTRs (if any):
A.1.3 Testing environment
PIXIT reference number:
ATS specification: EN 301 490-2
Abstract test method: Multi-party test method (see ISO/IEC 9646-2)
Means of testing identification:
Dates of testing:
Conformance log reference(s):
Retention date for log reference(s):
ETSI

---------------------- Page: 13 ----------------------

SIST EN 301 490-2 V1.1.1:2005
12 ETSI EN 301 490-2 V1.1.1 (2000-12)
A.1.4 Limits and reservations
Additional information relevant to the technical contents or further use of the test report, or to the rights and
obligations of the test laboratory and the client, may be given here. Such information may include restriction on the
publication of the report.
................................................................................................................................................................................
................................................................................................................................................................................
................................................................................................................................................................................
................................................................................................................................................................................
A.1.5 Comments
Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for
example, to note disagreement between the two parties.
................................................................................................................................................................................
................................................................................................................................................................................
................................................................................................................................................................................
................................................................................................................................................................................
A.2 IUT conformance status
This IUT has / has not been shown by conformance assessment to be non-conforming to the specified protocol
specification.
Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance
requirements (as specified in clause A.3 of the present document and there are no "FAIL" verdicts to be recorded (in
clause A.6) strike the words "has", otherwise strike the words "has not".
A.3 Static conformance summary
The PICS for this IUT is / is not consistent with the static conformance requirements in the specified protocol.
Strike the appropriate words in this sentence.
A.4 Dynamic conformance summary
The test campaign did / did not reveal errors in the IUT.
Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause A.6 of the
present document) strike the word "did"; otherwise strike the words "did not".
Summary of the results of groups of tests:
................................................................................................................................................................................
................................................................................................................................................................................
................................................................................................................................................................................
ETSI

---------------------- Page: 14 ----------------------

SIST EN 301 490-2 V1.1.1:2005
13 ETSI EN 301 490-2 V1.1.1 (2000-12)
A.5 Static conformance review report
If clause A.3 indicates non-conformance, this clause itemizes the mismatches between the PICS and the static
conformance requirements of the specified protocol specification.
................................................................................................................................................................................
.............
...