SIST EN 301 455-2 V1.3.1:2005

SLOVENSKI STANDARD
SIST EN 301 455-2 V1.3.1:2005
01-april-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,61±6LJQDOL]DFLMVNLSURWRNROPHG
FHQWUDODPL±0RELOQRVWEUH]YUYLþQHJDWHUPLQDOD&70±'RGDWQDODVWQRVWRPUHåMD
]DRGKRGQLNOLFEUH]YUYLþQHJDWHUPLQDOD]DYVWRSQRWRþNR931EVWRULWYH±

GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQH

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Cordless

Terminal Mobility (CTM); Incoming call additional network feature for the VPN b service

entry point; Part 2: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

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/

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 ................................................................................................................................9

6.1 Version of TTCN used ................................................................................................................................ 9

6.2 Use of ASN.1.............................................................................................................................................. 9

6.2.1 Situations where ASN.1 is used.............................................................................................................. 9

6.2.2 Specification of encoding rules............................................................................................................... 9

7 ATS to TP map.................................................................................................................................10

8 PCTR conformance ..........................................................................................................................10

9 PIXIT conformance ..........................................................................................................................11

10 ATS conformance.............................................................................................................................11

Annex A (normative): Protocol Conformance Test Report (PCTR) proforma ............................12

A.1 Identification summary .....................................................................................................................12

A.1.1 Protocol conformance test report................................................................................................................ 12

A.1.2 IUT identification...................................................................................................................................... 12

A.1.3 Testing environment.................................................................................................................................. 13

A.1.4 Limits and reservations.............................................................................................................................. 13

A.1.5 Comments................................................................................................................................................. 13

A.2 IUT conformance status....................................................................................................................13

A.3 Static conformance summary ............................................................................................................13

A.4 Dynamic conformance summary.......................................................................................................14

A.5 Static conformance review report......................................................................................................14

A.6 Test campaign report ........................................................................................................................14

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

B.6.2 IUT information ........................................................................................................................................ 18

B.6.2.1 Parameter values.................................................................................................................................. 18

B.6.2.2 Configuration of IUT ........................................................................................................................... 18

B.6.2.3 Timer values........................................................................................................................................ 19

B.6.2.4 Information parameter values ............................................................................................................... 19

B.7 Basic call PIXIT items ......................................................................................................................20

B.7.1 Parameter values - information element codings......................................................................................... 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

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

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

This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and

The present document is part 2 for a multi-part delivrable covering the Inter-exchange signalling protocol; Cordless

Terminal Mobility (CTM); Incoming call additional network feature for the VPN "b" service entry point, as described

Part 2: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for

This second part of EN 301 455 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 Incoming Call Additional Network Feature (ANF-CTMI).

EN 301 455-1 [5] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXIT

The following documents contain provisions which, through reference in this text, constitute provisions of the present

• References are either specific (identified by date of publication, edition number, version number, etc.) or

• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same

[1] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance

[2] 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

[3] ISO/IEC 8825-1: "Information technology - ASN.1 encoding rules: Specification of Basic

Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules

[4] ETSI ETS 300 696 (1996): "Private Integrated Services Network (PISN); Inter-exchange

signalling protocol; Cordless Terminal Incoming Call additional network feature".

[5] ETSI EN 301 455-1 (V1.1.4): "Private Integrated Services Network (PISN); Inter-exchange

signalling protocol; Cordless Terminal Incoming Call additional network feature (ANF-CTMI) for

the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP)

For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [1] apply.

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), the PCO used by the PTC1 is named "L1", and the PCO used by

the PTC2 is named "L2". 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 fourth "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

Not all components are used in every test case and the relationship between the IUT and the tester depends on the test

• when the IUT is in the Home, Visitor or Detect (with Home functionality) configuration, the IUT is connected to

the MTC. The verdict depends only on the behaviour observed at the PCO between the IUT and the MTC. The

• when the IUT is in the Rerouting or Detect 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 PCO O is used to specify control above

• when the IUT is the Detect configuration providing Rerouting functionality, PTC1, PTC2 and the MTC are used.

The verdict is assigned by the MTC or the PTCs depending on the test purpose. The PCO O is used to specify

The Test Purpose CTMI_Visitor01_001 is untestable because the receive event by the operator (by the CTM User)

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

The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.

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 [1] and in TR 101 101 [2] 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 ISOIEC 9646-3/AM2 [1] in which comment fields

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 [3]. 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

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

In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.

The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.

A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [1], to

produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [1].

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.

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 [1], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT

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

A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in

ISO/IEC 9646-5 [1], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma

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

The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of

ISO/IEC 9646-4 [1]. In particular, these concern the realization of an ETS based on each ATS. The test realizer shall

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

Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [1].

A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.

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

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

................................................................................................................................................................................

................................................................................................................................................................................

................................................................................................................................................................................

................................................................................................................................................................................

Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for

................................................................................................................................................................................

................................................................................................................................................................................

................................................................................................................................................................................

................................................................................................................................................................................

This IUT has / has not been shown by conformance assessment to be non-conforming to the specified protocol

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 this report) and there are no "FAIL" verdicts to be recorded (in clause A.6)

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. If there are no "FAIL" verdicts to be recorded (in clause A.6 of this

................................................................................................................................................................................

................................................................................................................................................................................

................................................................................................................................................................................