SIST EN 301 492-2 V1.1.1:2005

• Abstract:

  ATS PIXIT for CTM authorization.

• Status: Published
• Publication Date: 31-Mar-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Mandate: T-326
• Ref Project: ETSI EN 301 492-2 V1.1.1 (2000-12) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless terminal authentication supplementary services; Part 2: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the VPN b service entry point

SIST EN 301 492-2 V1.1.1:2005 is the Slovenian adoption of ETSI EN 301 492-2 V1.1.1 for Private Integrated Services Network (PISN) inter-exchange signalling. It covers the Cordless terminal authentication supplementary services and, in particular, the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the VPN "b" service entry point. In practice, it is the test specification used to check implementations of CTM authentication against the protocol defined in I-ETS 300 809.

What does SIST EN 301 492-2 V1.1.1:2005 specify?

SIST EN 301 492-2 V1.1.1:2005 specifies the ATS and partial PIXIT proforma for the VPN "b" reference point of implementations that conform to the Cordless Terminal Authentication supplementary service. It is a conformance-testing document: it tells you how the protocol is to be tested, what test data and parameters must be supplied, and how test reports are structured.

The scope is limited to testing material for the authentication supplementary service. EN 301 492-1 provides the Test Suite Structure and Test Purposes (TSS&TP) that correspond to this ATS and partial PIXIT proforma.

The document is organized into clauses 1 to 10 and three normative annexes.

Annex	What it covers
Annex A	Protocol Conformance Test Report (PCTR) proforma
Annex B	Partial PIXIT proforma
Annex C	Abstract Test Suite (ATS)

Clauses 4 to 10 cover the abstract test method, untestable test purposes, ATS conventions, the ATS-to-TP map, and conformance rules for PCTR, PIXIT, and ATS.

What are the key requirements of SIST EN 301 492-2 V1.1.1:2005?

The document is mainly about how conformance testing shall be organized and how test material shall be represented. The most important points are in clauses 4, 6, 7, 8, 9 and 10, plus annexes A to C.

Test method and test setup

Clause 4.1 applies a multi-party test method for the IUT. The tester uses distinct Points of Control and Observation (PCOs) to control and observe behaviour, with verdicts based on what happens at those points.

• L0 is the PCO used by the Main Test Component (MTC).
• L1 is the PCO used by the Parallel Test Component (PTC).
• O is an informal operator PCO used for control only.

In practice, this means the same ATS can exercise different configurations of the IUT. For the Authentication configuration, the IUT is connected only to the MTC. For the Home and Visitor configuration, the MTC and PTC1 are both used, and the operator PCO is used for actions above the IUT.

Test suite conventions and encoding

Clause 6 states that the TTCN version used is the one defined in TR 101 101, and that ASN.1 is used where it helps model data structures, apply subtype restrictions, or reproduce remote operation component types from the base standards.

Clause 6.2 also defines two encoding variations for ASN.1:

• BER for ASN.1 types where the table comments indicate it.
• ISDN/direct encoding as the default for ASN.1 constraint tables unless BER is stated.

This matters because test implementations must encode test data in the same way the ATS expects. If the encoding rule is wrong, a test can fail for the wrong reason.

Mapping test purposes to test cases

Clause 7 says the identifiers used for the Test Purposes (TPs) are reused as test case names. The map is one-to-one. For users of the ATS, this makes it easier to trace a test case back to the intended protocol behaviour and to relate test reports to the test purpose list.

Reporting and conformance obligations

Clause 8 requires a PCTR to follow the ISO/IEC 9646-5 template, and also to conform to the PCTR proforma in Annex A when reporting tests for this ATS. The report must preserve the content and ordering of Annex A, although extra columns may be added in clause A.6.

Clause 9 requires a partial PIXIT proforma to be augmented for a particular IUT and then used as the PIXIT for this ATS. The content must remain technically equivalent to Annex B, but extra questions may be added to prepare the Means Of Testing (MOT) for a specific implementation.

Clause 10 states that the MOT and ETS produced for this ATS shall comply with ISO/IEC 9646-4. An ETS must contain test groups and test cases technically equivalent to those in Annex C, and every abstract test event sequence must be realizable in the executable test case. Additional checks are allowed, but they must not affect the verdict assignment for each test case.

What terms does SIST EN 301 492-2 V1.1.1:2005 define?

• Implementation Under Test (IUT) - the protocol implementation being assessed for conformance.
• System Under Test (SUT) - the full system or platform that contains the IUT in the test environment.
• Point of Control and Observation (PCO) - the interface where the tester controls and observes behaviour during a test.
• Abstract Test Suite (ATS) - the abstract set of test cases and test groups written independently of a specific test tool.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the implementation-specific information needed to run the tests.
• Protocol Conformance Test Report (PCTR) - the standardized report used to record conformance test results.
• Means Of Testing (MOT) - the concrete test means, including the tools and configuration used to execute the ATS.

Who uses SIST EN 301 492-2 V1.1.1:2005?

Test laboratories use this standard to run conformance tests and to prepare a PCTR or PIXIT for a specific implementation. Test realizers use it to build an executable test suite from the ATS in Annex C.

Equipment vendors and protocol implementers use it when developing or validating CTM authentication support for PISN inter-exchange signalling. Clients commissioning tests use it to understand what implementation data must be supplied and what the test report will contain.

It is also relevant to quality managers and technical buyers who need to check whether a product’s CTM authentication behaviour can be verified against the specified conformance material.

Which standards are used with SIST EN 301 492-2 V1.1.1:2005?

Reference	What it contributes
ETSI I-ETS 300 809	The base protocol specification for Cordless terminal authentication supplementary services
ETSI EN 301 492-1	The TSS&TP specification related to this ATS and partial PIXIT
ETSI ETS 300 239	Generic functional protocol for support of supplementary services
ISO/IEC 9646-1	General conformance testing concepts
ISO/IEC 9646-2	Abstract test suite specification framework
ISO/IEC 9646-3	TTCN notation used for the ATS
ISO/IEC 9646-4	Test realization requirements for MOT and ETS
ISO/IEC 9646-5	Requirements on test laboratories and clients
ETSI TR 101 101	TTCN interim version with ASN.1 1994 support
ISO/IEC 8825-1	BER, CER and DER encoding rules for ASN.1

These references supply the protocol basis, the conformance testing methodology, the TTCN notation, and the encoding rules used by the ATS and PIXIT material.

What does the SIST EN 301 492-2 V1.1.1:2005 document contain?

Annex A gives a PCTR proforma with identification, IUT status, static and dynamic conformance summaries, a test campaign report, and observations. Annex B gives a partial PIXIT proforma with protocol identification, laboratory and client data, SUT details, timer values, parameter values, and information element coding items.

Annex C contains the ATS itself in TTCN.GR and TTCN.MP forms. The document states that the graphical and machine-processable forms are equivalent, and that any discrepancy between them must be resolved by correcting the erroneous format.

The main body also includes the abstract test method, the rules for untestable test purposes, the ATS conventions, the ATS-to-TP map, and the formal conformance statements for PCTR, PIXIT, and ATS.

SLOVENSKI STANDARD
01-april-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,61±6LJQDOL]DFLMVNLSURWRNROPHG
FHQWUDODPL±'RSROQLOQDVWRULWHYDYWHQWLNDFLMDEUH]YUYLþQHJDWHUPLQDOD±GHO
$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQH
L]YHGEHSURWRNROD3,;,7±3URIRUPDVSHFLILNDFLMD]DYVWRSQRWRþNR931E
VWRULWYH
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless
terminal authentication supplementary services; Part 2: Abstract Test Suite (ATS) and
partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the
VPN b service entry point
Ta slovenski standard je istoveten z: EN 301 492-2 Version 1.1.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 Standard (Telecommunications series)
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Cordless terminal authentication supplementary services;
Part 2: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma for the VPN "b" service entry point

2 ETSI EN 301 492-2 V1.1.1 (2000-12)
Reference
DEN/SPAN-05196-3
Keywords
CTM, PISN, PSS1, CTAT, CTAN, mobility,
testing, authentication, TSS&TP, ATS, PIXIT,
QSIG, stage 3, supplementary service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI
3 ETSI EN 301 492-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. 12
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.13
A.5 Static conformance review report.13
A.6 Test campaign report .13
A.7 Observations.14
Annex B (normative): Partial PIXIT proforma.15
B.1 Identification summary .15
B.2 Abstract test suite summary .15
B.3 Test laboratory.15
B.4 Client (of the test laboratory) .16
B.5 System Under Test (SUT).16
B.6 Protocol information.17
B.6.1 Protocol identification . 17
ETSI
4 ETSI EN 301 492-2 V1.1.1 (2000-12)
B.6.2 IUT information . 17
B.6.2.1 Parameter values. 17
B.6.2.2 Timer values. 17
B.6.2.3 Information parameter values . 18
B.7 Basic call PIXIT items .18
B.7.1 Parameter values - information element coding. 18
Annex C (normative): Abstract Test Suite (ATS).19
C.1 The TTCN Graphical form (TTCN.GR).19
C.2 The TTCN Machine Processable form (TTCN.MP) .19
Bibliography.20
History .21
ETSI
5 ETSI EN 301 492-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 of a multi-part deliverable covering the Inter-exchange signalling protocol for the
cordless terminal authentication 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 for the VPN "b" service entry point".
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
6 ETSI EN 301 492-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
Cordless Terminal Authentication supplementary service as described in I-ETS 300 809 [2].
EN 301 492-1 [10] 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 239 (1995): "Private Integrated Services Network (PISN); Inter-exchange
signalling protocol; Generic functional protocol for the support of supplementary services
[ISO/IEC 11582 (1995), modified]".
[2] ETSI I-ETS 300 809 (1995): "Private Integrated Services Network (PISN); Cordless Terminal
Mobility (CTM); Inter-exchange signalling protocol; Cordless terminal authentication
supplementary services".
[3] ISO/IEC 9646-2 (1994): "Information technology; Open Systems Interconnection; Conformance
testing methodology and framework; Part 2: Abstract test suite specification".
[4] 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)".
[5] ISO/IEC 8825-1: "Information technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)" (See also ITU-T Recommendation X.690): 1994.
[6] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[8] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[9] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
[10] ETSI EN 301 492-1: "Private Integrated Services Network (PISN); Inter-exchange signalling
protocol; Cordless terminal authentication supplementary services; Part 1: Test Suite Structure and
Test Purposes (TSS&TP) specification for the VPN "b" service entry point".
ETSI
7 ETSI EN 301 492-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
CTM Cordless Terminal Mobility
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-CTAN Supplementary service - Authentication of a PISN
SS-CTAT Supplementary service - Authentication of a CTM user
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
8 ETSI EN 301 492-2 V1.1.1 (2000-12)
PTC_D
CPA_D
MTC
PTC1
CPA1
Informal test
PCO PCO PCO
co-ordination by
L0 L1 operator 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 [4].
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
9 ETSI EN 301 492-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 [4] does not facilitate definition of the encoding rules as needed for the present
document. 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 [5]. 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 the
present document. 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 the present document 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"is used.
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 : authCtmUser_inv_S1 (INV_ID: InvokeIDType; USR_NUM: PartyNumber; CHALLENGE:
AuthChallenge; RESPONSE: AuthResponse)
ASN.1 Type : Component
Derivation Path :
Encoding Variation :
Comments : ASN1_Encoding: BER
Send Component: authCtmUser invoke component, element calcCtatInfo is
included.
Description
authCtmUser_Comp
authCtmUser_InvokeComp
{ invokeID INV_ID, -- The invoke identifier
operation_value localValue 72, -- The value for operation
argument {pisnNumber USR_NUM,
calcCtatInfo {{authChallenge CHALLENGE,
authResponse RESPONSE,
derivedCipherKey OMIT,
calculationParam OMIT}},
dummyExtension OMIT}
}
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
10 ETSI EN 301 492-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 con
...