SIST EN 301 454-2 V1.3.1:2003

• Abstract:

  Update of ATS PIXIT for CTM location registration.

• Status: Published
• Publication Date: 31-Mar-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: RES - Radio equipment and systems
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2003
• Due Date: 01-Apr-2003
• Completion Date: 01-Apr-2003
• Mandate: T-326
• Ref Project: ETSI EN 301 454-2 V1.3.1 (2002-01) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Location Registration (CTLR) supplementary service; ECMA-QSIG-CTLR; Part 2: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification

SIST EN 301 454-2 V1.3.1:2003 is the ETSI conformance-testing standard for the Private Integrated Services Network (PISN) Cordless Terminal Location Registration (CTLR) supplementary service. It defines the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for implementations at the VPN "b" reference point. Test laboratories and test-realization teams use it to prepare, run, and report protocol conformance testing.

What does SIST EN 301 454-2 V1.3.1:2003 specify?

SIST EN 301 454-2 V1.3.1:2003 specifies how to test implementations that conform to the CTLR supplementary service described in ETS 300 693. Clause 1 states that it covers the ATS and partial PIXIT proforma, and that EN 301 454-1 provides the related Test Suite Structure and Test Purposes (TSS&TP).

The document is organized as follows:

• Clauses 2 to 10 cover references, definitions and abbreviations, the abstract test method, untestable test purposes, ATS conventions, the ATS to TP map, and conformance rules.
• Annex A gives the Protocol Conformance Test Report (PCTR) proforma.
• Annex B gives the partial PIXIT proforma.
• Annex C contains the ATS.
• Annex D records changes.
• Annex E lists bibliography items.

Annex	What it covers
A	PCTR proforma for reporting conformance test results
B	Partial PIXIT proforma for test setup and parameter values
C	ATS in TTCN graphical and machine-processable forms
D	Informative changes to the test specification
E	Bibliography

What are the key requirements of SIST EN 301 454-2 V1.3.1:2003?

SIST EN 301 454-2 V1.3.1:2003 is built around a multi-party test method, fixed test conventions, and conformance rules for test reports, test suites, and test equipment. In practice, these clauses tell a laboratory how to observe the implementation under test, what to record, and what an executable test suite must preserve from the abstract suite.

Clause 4 - abstract test method

The standard uses a multi-party test method with PCOs named L0, L1, and an operator PCO O. This matters because different test groups use different test components depending on whether the implementation under test is in Originating or Home configuration.

Clause 5 - untestable test purposes

The standard states that there are no untestable test cases associated with this ATS and ATM. For a test program, that means the suite is intended to be fully executable within the defined method.

Clause 6 - ATS conventions

The ATS uses the TTCN version defined in TR 101 101 and combines TTCN with ASN.1. The document also sets encoding rules: BER is used only where specifically indicated, while the default encoding for ASN.1 constraints is the ISDN "Direct Encoding" variation.

Clause 7 - ATS to TP map

The identifiers of the test purposes are reused as test case names, giving a one-to-one mapping. That helps users trace each executable test directly back to its stated purpose.

Clauses 8 to 10 - conformance

The conformance clauses define what a conforming PCTR, PIXIT proforma, MOT, and ETS must contain. A key practical point is that any extra checking performed by a test system must not affect verdict assignment for the ATS test case.

Annex A and Annex B content

Annex A structures the PCTR around identification, IUT status, static and dynamic conformance summaries, campaign results, and observations. Annex B structures the partial PIXIT around laboratory details, SUT details, protocol information, parameter values, timers, information parameter values, and basic call PIXIT items.

What terms does SIST EN 301 454-2 V1.3.1:2003 define?

• Abstract Test Suite (ATS) - the set of abstract test cases and supporting material that define the conformance tests.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the implementation-specific information needed to prepare the test environment and interpret results.
• Protocol Conformance Test Report (PCTR) - the report used to record the outcome of a conformance test campaign.
• Implementation Under Test (IUT) - the protocol implementation being assessed.
• System Under Test (SUT) - the complete system or platform that contains the IUT and the test-relevant environment.
• Point of Control and Observation (PCO) - the place where the tester controls and observes protocol behavior.
• Main Test Component (MTC) and Parallel Test Component (PTC) - the coordinated test components used in the multi-party method.

Who uses SIST EN 301 454-2 V1.3.1:2003?

SIST EN 301 454-2 V1.3.1:2003 is used by test laboratories that run conformance services for CTLR implementations. It is also used by test realizers who build an Executable Test Suite (ETS) and by clients who need a PCTR or PIXIT for a specific IUT.

In practice, users rely on it to:

• configure the Means Of Testing (MOT)
• prepare parameter values and timers for the SUT
• execute the ATS from Annex C
• document conformance results in the PCTR format from Annex A

What changed in SIST EN 301 454-2 V1.3.1:2003 from the previous edition?

Annex D records three change items from 4TD 175 clause 1.2. One introduces a synchronization step in all dual configurations, one replaces unclear test messages to the dummy PTC with test constants and clearer operator instructions, and one states that no changes were made to the PIXIT tables for address parameters.

The document history also shows the earlier V1.2.2 publication and the later V1.3.1 publication.

Which standards are used with SIST EN 301 454-2 V1.3.1:2003?

Clause 2 cites these related standards and documents:

• EN 301 454-1 - provides the Test Suite Structure and Test Purposes that match this ATS.
• ISO/IEC 9646 (all parts) - gives the conformance testing methodology and framework used throughout the document.
• TR 101 101 - defines the TTCN version used here.
• ISO/IEC 8825-1 - defines BER, CER, and DER encoding rules for ASN.1.
• ETS 300 693 - defines the CTLR supplementary service that this ATS tests.

What does the SIST EN 301 454-2 V1.3.1:2003 document contain?

Annex C contains the ATS in both TTCN.GR and TTCN.MP form, and the standard notes that the two published forms are equivalent. Annex A contains the report structure used to document test campaigns, including the test case list in clause A.6. Annex B contains the PIXIT questions and parameter tables needed before testing starts, including timer values and information-element coding items.

The document also includes Figure 1 for the multi-party test configuration and Table 1 for ASN.1 encoding variation, both of which support test realization rather than user operation. Annex D and Annex E add change notes and bibliography for traceability.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VLJQDOL]DFLMVNLãHYDOQHJDPrivate Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Location Registration (CTLR) supplementary service; ECMA-QSIG-CTLR; Part 2: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 454-2 Version 1.3.1SIST EN 301 454-2 V1.3.1:2003en01-april-2003SIST EN 301 454-2 V1.3.1:2003SLOVENSKI
STANDARD
ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 2
Reference REN/SPAN-130291-2 Keywords ATS, CTM, mobility, PISN, PIXIT, QSIG, supplementary service, testing, VPN 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://portal.etsi.org/tb/status/status.asp 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 2002. All rights reserved.
ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 3 Contents Intellectual Property Rights.5 Foreword.5 1 Scope.6 2 References.6 3 Definitions and abbreviations.6 3.1 Definitions.6 3.2 Abbreviations.6 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.8 7 ATS to TP map.9 8 PCTR conformance.9 9 PIXIT conformance.9 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.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 SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 4 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 Annex D (informative): Changes.20 D.1 Comment 1 of 4TD 175 clause 1.2.20 D.2 Comment 3 of 4TD 175 clause 1.2.22 D.3 Comment 4 of 4TD 175 clause 1.2.22 Annex E (informative): Bibliography.23 History.24
ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 5 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://webapp.etsi.org/IPR/home.asp). 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 Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Location Registration (CTLR) supplementary service; ECMA-QSIG-CTLR, 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 specification".
National transposition dates Date of adoption of this EN: 18 January 2002 Date of latest announcement of this EN (doa): 30 April 2002 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
31 October 2002 Date of withdrawal of any conflicting National Standard (dow): 31 October 2002
ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 6 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 Location Registration supplementary service (SS-CTLR) as described in ETS 300 693 (see bibliography). EN 301 454-1 [1] 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, subsequent revisions do apply. [1] ETSI EN 301 454-1 (V1.1.4): "Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless Terminal Location Registration (CTLR) supplementary service; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification". [2] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework". [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: "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). 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [2] apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ANF Additional Network Feature 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 SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 7 PCTR Protocol Conformance Test Report PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component 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.
PTC2
CPA2
MTC
PTC1
CPA1
PCO L0
PCO
L1
Informal test co-ordination by operator
PCO
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 Originating 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 is not used. The PTC2 and PCO O are used to specify control above the IUT. • When the IUT is in the Home 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 PTC2 is not used. SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 8 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. 6.2.2 Specification of encoding rules There is a variation in the encoding rules applied to ASN.1 types and constraints specified in this ATS and therefore a mechanism is needed to differentiate the encoding rules. However the mechanism specified in ISO/IEC 9646-3/AM2 [2] 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/AM2 [2] in which comment fields have been used as a means of encoding rules. For ASN.1 used in this ATS, 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" is used. In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER. SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 9 Table 1: ASN.1 type constraint declaration showing use of encoding variation ASN.1 Type Constraint Declaration Constraint Name : locUpdate_inv_R (USR_NUM: PartyNumber; PINX_NUM: PartyNumber) ASN.1 Type
: Component Derivation Path
: Encoding Variation : Comments
: ASN1_Encoding: BER
Receive Component: LocUpdate invoke component, with type of Basic Service. Description locUpdate_Comp
locUpdate_InvokeComp
{ invokeID
?,
-- The invoke identifier
operation_value
localValue
50,
-- The value for operation
argument
{pisnNumber
USR_NUM,
basicService
?,
visitPINX
PINX_NUM}
} 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. 8 PCTR conformance A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [2], to produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [2]. 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 [2], 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 [2], 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. SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 10 10 ATS conformance The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of ISO/IEC 9646-4 [2]. 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 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 this ATS shall comply with ISO/IEC 9646-5 [2]. A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS. SIST EN 301 454-2 V1.3.1:2003

ETSI ETSI EN 301 454-2 V1.3.1 (2002-01) 11 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 693 PICS:
Previous PCTRs (if any):
A.1.3 Testing environment PIXIT reference number:
ATS specification: EN 301 454-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 ETSI EN 301 454-2 V1.3.1 (2002-01) 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. . . . .
...