SIST EN 301 144-6 V1.1.1:2005

• Abstract:

  Test specification for DE/SPS-05121-1

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 144-6 V1.1.1 (2000-12) - Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) and Signalling System No.7 (SS7) protocols; Signalling application for the mobility management service on the alpha interface; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

SIST EN 301 144-6 V1.1.1:2005 is the Slovenian standard identical to ETSI EN 301 144-6 Version 1.1.1. It specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the network side of the signalling application for the mobility management service on the alpha interface. In practice, it is the conformance testing document used with EN 301 144-1 for implementations in the ISDN, DSS1 and SS7 environment.

What does SIST EN 301 144-6 V1.1.1:2005 specify?

SIST EN 301 144-6 V1.1.1:2005 specifies the network-side ATS and partial PIXIT proforma for the signalling application for the mobility management service on the alpha interface. It applies to all types of exchanges defined in the reference specification, and it is the network companion to the user-side material in the other parts of EN 301 144.

The document is organized as a test specification rather than a protocol description. Its main clauses cover scope, references, definitions and abbreviations, the abstract test method, untestable test purposes, ATS conventions, the ATS-to-test-purpose map, and the conformance rules for PCTR, PIXIT and ATS use.

Annex	What it covers
Annex A	Partial PCTR proforma for reporting conformance test results
Annex B	Partial PIXIT proforma for configuring the SUT and test environment
Annex C	Abstract Test Suite (ATS) in TTCN.GR and TTCN.MP forms
Annex D	Informative general structure of a typical ATS

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

The test method is remote and uses two points of control

SIST EN 301 144-6 V1.1.1:2005 uses the remote test method. Clause 4 places the main Point of Control and Observation (PCO) at the service access point between layers 2 and 3, and names it L.

That matters because verdicts are based on what the tester observes at PCO L. The same clause also defines an informal PCO O for operator coordination only, so actions sent there guide manual steps but do not themselves decide the test result.

There are no untestable test purposes

SIST EN 301 144-6 V1.1.1:2005 states in clause 5 that there are no untestable test purposes.

For a test lab, that means the ATS is intended to cover the test purposes set for this part without marking any of them as outside test execution. For planning, it signals that the test suite is meant to be directly usable rather than partly descriptive only.

The ATS follows strict TTCN naming and structure rules

SIST EN 301 144-6 V1.1.1:2005 defines naming conventions in clause 6 for the ATS declarations, constraints and dynamic parts. It fixes the TTCN version by reference to ETSI TR 101 101, and it gives naming patterns for test suite operations, parameters, constants, variables, timers, PCOs, ASPs and PDUs.

This is important in practice because tool-generated test suites and manually maintained TTCN need consistent identifiers. If a laboratory or tool vendor builds on this ATS, the naming rules help keep the suite readable and aligned with the document structure.

ASN.1 and BER are used where TTCN alone is not enough

SIST EN 301 144-6 V1.1.1:2005 explains in clause 6.3 that ASN.1 is used for data structures, tighter type restriction, and remote operation component type definitions from the base standards. It also combines TTCN and ASN.1 where needed.

The encoding rules matter as well. The ATS uses direct encoding for protocol data structures taken from the relevant standards and Basic Encoding Rules (BER) for ASN.1 parts. For BER, received PDUs must be decodable in all length forms, while sent data should use the short form of length encoding if possible.

Test purposes map one-to-one to test cases

SIST EN 301 144-6 V1.1.1:2005 says in clause 7 that the identifiers used for the test purposes are reused as test case names.

That makes the relation between the test suite structure and the test purpose list straightforward. For users of the ATS, it reduces ambiguity when tracing a case in the executable suite back to the published test purpose.

Conformance reporting and PIXIT completion are controlled

SIST EN 301 144-6 V1.1.1:2005 sets conformance expectations for three different deliverables. Clause 8 requires a PCTR that follows the proforma in Annex A; clause 9 requires a PIXIT proforma technically equivalent to Annex B, with extra questions allowed if needed to prepare the Means Of Testing (MOT); clause 10 requires an executable ATS and MOT that are technically equivalent to the ATS in Annex C.

In practice, this means a test laboratory cannot change the substance or ordering of the prescribed report and proforma contents. It may add material needed for a specific IUT, but the added material cannot replace the required technical content.

The annexes define the reporting and test data needed for real use

Annex A structures the Protocol Conformance Test Report (PCTR) around identification, IUT status, static and dynamic conformance summaries, review results and the test campaign report. Annex B structures the PIXIT around laboratory, client, SUT and protocol information, plus parameter values, configuration actions, timers and basic call coding items.

That matters because the document is not only a test suite - it also tells the lab what information to collect before testing, what to record during testing, and how to report the outcome afterward.

What terms does SIST EN 301 144-6 V1.1.1:2005 define?

Abstract Test Suite (ATS) - The formal set of abstract test cases and related declarations used to assess protocol conformance.

Protocol Implementation eXtra Information for Testing (PIXIT) - The implementation-specific information needed to prepare and configure a test campaign for a particular IUT or SUT.

Protocol Conformance Test Report (PCTR) - The report format used to record the results and summaries of a conformance test campaign.

Implementation Under Test (IUT) - The protocol implementation being assessed by the test suite.

System Under Test (SUT) - The configured system, including the IUT and its test environment, as described in the PIXIT.

Point of Control and Observation (PCO) - The interface point where the tester controls and observes protocol behaviour.

Tree and Tabular Combined Notation (TTCN) - The notation used to describe the ATS in a structured, test-oriented form.

Basic Encoding Rules (BER) - The ASN.1 encoding rule used here for the ASN.1 parts of the test suite.

Who uses SIST EN 301 144-6 V1.1.1:2005?

SIST EN 301 144-6 V1.1.1:2005 is used by test laboratories, protocol implementers, and test tool developers working on the network side of the mobility management service on the alpha interface. It is also used by test realizers who build executable suites and Means Of Testing (MOT), because clause 10 ties conformance to the ATS in Annex C.

Quality managers and buyers use it to check whether a supplier can support the expected conformance test process, including the PICS, PIXIT and PCTR workflow. Operators who support testing also use the PIXIT items, especially the configuration and timer questions in Annex B.

Which standards are used with SIST EN 301 144-6 V1.1.1:2005?

Standard	What it contributes
ISO/IEC 9646 (all parts)	Conformance testing terminology, framework and the test-reporting basis used throughout the document
ETSI TR 101 101	The TTCN version and interim testing methods used for the ATS
ETSI EN 300 196	The DSS1 functional protocol reference used for related protocol behaviour and BER length handling guidance
ETSI EN 300 175-5	The DECT Common Interface network layer reference used for CTM-related encoding and parameter information
ETSI EN 301 144-1	The protocol specification under test
ETSI EN 301 144-2	The PICS program specification used with this part
ETSI EN 301 144-5	The network TSS&TP companion part used with this part
ISO/IEC 8825-1	Supporting BER encoding rules cited in the bibliography

What does the SIST EN 301 144-6 V1.1.1:2005 document contain?

The document contains the ATS in Annex C, published in both TTCN.GR and TTCN.MP forms, with the note that the two forms are equivalent. It also contains the partial PCTR proforma in Annex A and the partial PIXIT proforma in Annex B, each laid out for practical use in testing and reporting.

Annex A includes the IUT identification, testing environment, conformance summaries and a detailed test campaign report, with test case names listed for CTM and DG groups. Annex B includes tables for protocol information, IUT configuration actions, timer values and information-element coding for basic call, CTM and DECT access to GSM items.

Annex D gives the general structure of a typical ATS, including the overview, indexes, declarations, constraints and dynamic behaviour sections. That helps readers and tool developers navigate the ATS content without reproducing the full TTCN material here.

SLOVENSKI STANDARD
01-januar-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±3URWRNROLGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66LQVLJQDOL]DFLMHãW66±6LJQDOL]DFLMVNDDSOLNDFLMD]D
VWRULWHYXSUDYOMDQMDPRELOQRVWLQDYPHVQLNXDOID±GHO$EVWUDNWQLSUHVNXãDOQL
QL]$76LQGHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHL]YHGEHSURWRNROD3,;,7±
3URIRUPDVSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) and Signalling System No.7 (SS7) protocols; Signalling application for the
mobility management service on the alpha interface; Part 6: Abstract Test Suite (ATS)
and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network
Ta slovenski standard je istoveten z: EN 301 144-6 Version 1.1.1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) and
Signalling System No.7 (SS7) protocols;
Signalling application for the mobility management
service on the alpha interface;
Part 6: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network

2 ETSI EN 301 144-6 V1.1.1 (2000-12)
Reference
DEN/SPAN-05121-6
Keywords
ISDN, DSS1, ATS, PIXIT, network, CTM, SS7
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 144-6 V1.1.1 (2000-12)
Contents
Intellectual Property Rights .5
Foreword.5
1 Scope.6
2 References.6
3 Definitions, symbols and abbreviations .6
3.1 Definitions . 6
3.2 Abbreviations. 7
4 Abstract Test Method.7
5 Untestable test purposes.8
6 ATS conventions .8
6.1 Version of TTCN used . 8
6.2 Naming conventions. 8
6.2.1 Declarations part. 8
6.2.1.1 Simple type, ASN.1 type and structured type definitions . 8
6.2.1.2 Test suite operations definitions. 8
6.2.1.3 Test suite parameter declarations. 8
6.2.1.4 Test case selection expression definitions. 8
6.2.1.5 Test suite constant declarations. 8
6.2.1.6 Test suite variable declarations. 8
6.2.1.7 Test case variable declarations . 8
6.2.1.8 PCO type declarations . 9
6.2.1.9 PCO declarations. 9
6.2.1.10 Timer declarations. 9
6.2.1.11 ASP type definitions. 9
6.2.1.12 PDU type definitions . 9
6.2.2 Constraints part. 9
6.2.2.1 Structured type constraints. 9
6.2.2.2 ASN.1 type constraints . 9
6.2.2.3 ASP constraints . 9
6.2.2.4 PDU constraint. 9
6.2.3 Dynamic part . 9
6.2.3.1 Test case identifiers . 10
6.2.3.2 Test step identifiers. 10
6.3 Use of ASN.1. 10
6.3.1 Situations where ASN.1 is used. 10
6.3.2 Specification of encoding rules. 10
7 ATS to TP map.11
8 PCTR conformance .11
9 PIXIT conformance .11
10 ATS conformance.11
Annex A (normative): Partial 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
ETSI
4 ETSI EN 301 144-6 V1.1.1 (2000-12)
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 .15
A.7 Observations.21
Annex B (normative): Partial PIXIT proforma.22
B.1 Identification summary .22
B.2 Abstract test suite summary .22
B.3 Test laboratory.22
B.4 Client (of the test laboratory) .23
B.5 System Under Test (SUT).23
B.6 Protocol information.24
B.6.1 Protocol identification . 24
B.6.2 IUT information . 24
B.6.2.1 Parameter values. 24
B.6.2.2 Configuration of IUT . 25
B.6.2.3 Timer values. 26
B.7 Basic call PIXIT items .26
B.7.1 Parameter values - information element coding. 26
Annex C (normative): Abstract Test Suite (ATS).28
C.1 The TTCN Graphical form (TTCN.GR).28
C.2 The TTCN Machine Processable form (TTCN.MP) .28
Annex D (informative): General structure of ATS .29
Bibliography.30
History .31
ETSI
5 ETSI EN 301 144-6 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 6 of a multi-part deliverable covering the Digital Subscriber Signalling System No. one
(DSS1) and Signalling System No.7 protocols; Signalling application for the mobility management service on the alpha
interface, as identified below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the network".
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 144-6 V1.1.1 (2000-12)
1 Scope
This sixth part of EN 301 144 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma for the network of the Signalling application for the mobility management
service on the alpha interface. It is applicable to all types of exchanges as defined in the reference specification.
Part 5 of EN 301 144 specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this protocol. Other
parts specify the TSS&TP and the ATS and partial PIXIT proforma for the User side for implementations conforming
to part 1 of EN 301 144 [5].
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.
• 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 EN 300 196: "Integrated Services Digital Network (ISDN); Generic functional protocol for
the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol".
[2] ISO/IEC 9646 (all parts): "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework".
[3] ETSI TR 101 101 (V1.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] ETSI EN 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT); Common
Interface (CI); Part 5: Network (NWK) Layer".
[5] ETSI EN 301 144-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) and Signalling System No.7 (SS7); Signalling application for the mobility
management service on the alpha interface; Part 1: Protocol specification".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [2] apply.
ETSI
7 ETSI EN 301 144-6 V1.1.1 (2000-12)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASP Abstract Service Primitive
ATS Abstract Test Suite
BER Basic Encoding Rules
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method
The remote test method is applied for this ATS.
A Point of Control and Observation (PCO) resides at the service access point between layers 2 and 3 in the test system.
This PCO is named "L" (for Lower). The L PCO is 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 this PCO.
A second "informal" PCO, called "O" (for Operator) is used to specify control but not observation concerning 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.
Tester Informal test co- SUT
ordination by
operator
Upper layer(s)
LT IUT
PCO L
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 1: Remote test method with PCO O for test co-ordination
ETSI
8 ETSI EN 301 144-6 V1.1.1 (2000-12)
5 Untestable test purposes
There are no untestable test purposes.
6 ATS conventions
6.1 Version of TTCN used
The version of TTCN used is that defined in TR 101 101 [3].
6.2 Naming conventions
6.2.1 Declarations part
This subclause describes the naming conventions chosen for the elements of the ATS declarations part.
6.2.1.1 Simple type, ASN.1 type and structured type definitions
The test suite simple type, ASN.1 type and structured type identifiers are written in lowercase starting by an uppercase
letter or completely in upper case letters.
6.2.1.2 Test suite operations definitions
The test suite operation identifiers are composed of strings in uppercase and lowercase letters starting by the string
"TSO_".
EXAMPLE: TSO_CalcFieLength
6.2.1.3 Test suite parameter declarations
The test suite parameter identifiers are composed of strings in uppercase and lowercase letters starting by the uppercase
string "PC_" for a PICS or "PX_" for a PIXIT.
6.2.1.4 Test case selection expression definitions
The naming conventions for the test case selection expression definitions use free text starting with the string: "TCSE_".
The name of the expression shall explain clearly the selection rule. The test case selection expressions are generally
logical combinations of the applied test suite parameter definitions.
6.2.1.5 Test suite constant declarations
The test suite constant identifiers are composed of strings in uppercase and lower letters starting by the uppercase string
"TSC_".
6.2.1.6 Test suite variable declarations
The test suite variable identifiers are composed of string in lowercase letters starting by the lowercase string "tsv_".
6.2.1.7 Test case variable declarations
The test case variable identifiers are composed of strings in lowercase letters starting by the lowercase string "tcv_".
ETSI
9 ETSI EN 301 144-6 V1.1.1 (2000-12)
6.2.1.8 PCO type declarations
The point of control and observation type identifiers consist of two or three capital letters.
6.2.1.9 PCO declarations
The point of control and observation identifiers consist of one capital letter.
6.2.1.10 Timer declarations
The timer names begin with the prefix "T_", followed by a string in lowercase or uppercase letters with each word in
the following string starting with an uppercase letter.
6.2.1.11 ASP type definitions
The ASP types are defined in uppercase letters.
6.2.1.12 PDU type definitions
The type of a PDU is given in uppercase letters, followed by the string "_PDU".
6.2.2 Constraints part
This subclause describes the naming conventions chosen for the elements of the ATS constraints part.
6.2.2.1 Structured type constraints
Structured type constraint identifiers begin with an uppercase letter followed by uppercase and lowercase letters. The
meaning of the identifier represents the contents of the structured type constraint.
6.2.2.2 ASN.1 type constraints
ASN.1 type constraint identifiers begin with an uppercase letter followed by uppercase and lowercase letters. The
meaning of the identifier represents the contents of the ASN.1 type constraint.
6.2.2.3 ASP constraints
ASP constraint identifiers begin with an uppercase letter followed by uppercase and lowercase letters. The meaning of
the identifier represents the contents of the ASP constraint.
6.2.2.4 PDU constraint
Constraint identifiers begin with the type of the PDU meaningfully abbreviated, written in uppercase.
As a suffix a string "_S" or "_R" is appended to indicate if the constraint is sent or received by the tester. This string is
followed by a number allowing to distinguish between different variations of sent or received PDUs.
In case the PDU constraints are specific to the CTM part of the DECT access to GSM part of the ATS the character "C"
respectively "G" immediately follows the undersore character.
6.2.3 Dynamic part
This subclause describes the naming conventions chosen for the elements of the ATS dynamic part.
ETSI
10 ETSI EN 301 144-6 V1.1.1 (2000-12)
6.2.3.1 Test case identifiers
The test case identifiers are built with a string of uppercase letters subdivided by underscore characters distinguishing
between the different groups and subgroups of which the test suite consists. The highest group level allows to make the
difference between the test cases according to "CTM" and those according to "DECT access to GSM", for which
prefixes "CTM" and "DG" are used. The lowest subgroup level divides "valid" and "invalid" test cases, represented by
the character "V" or "I" respectively. Within these subgroups the test case are given individual numbers.
EXAMPLES: CTM_…_…_V_01
DG_…_ …_I_02
This convention is the one applied to identify the test cases in the TSS&TP document.
6.2.3.2 Test step identifiers
The test step identifiers are built with a string of lowercase letters prefixed by a string of capital letters and joined by an
underscore character. The first string indicates the main function of the test step; e.g. PR for preamble, PO for
postamble, ST for a normal step, LTS for a local test step, and DEF for a default test step. The second string indicates
the meaning of the step.
EXAMPLES: PR_Name
PO_Name
ST_Name
LTS_Name
DEF_Name
6.3 Use of ASN.1
6.3.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 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.3.2 Specification of encoding rules
The data types therefore consist of non-ASN.1 and eventually ASN.1 parts, each of which has to be encoded as these
parts require. Consequently two different types of encoding rules are used in this test suite:
• direct Encoding: the data structures fully specified in the relevant protocol standards – in a form sometimes
called tabular - are mapped bitwise onto the transfer data stream;
• basic Encoding Rules defined in the ASN.1 standard.
Note that within BER, there are a number of variations for the encoding of lengths of fields. According to
EN 300 196-1 [1], an IUT should be able to interpret all length forms within BER for received PDUs. When sending
PDUs containing BER encoding, EN 300 196-1 [1] gives guidelines but makes no restrictions on the length forms
within BER which an IUT may apply. This ATS prescribes a BER encoding variation which requests that, if possible,
the short form of length enocding is being used in data being sent, and that the receiving end shall be capable of
decoding any length form.
In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER. In
circumstances where it is irrelevant received components are decoded as if they had been directly encoded, applying a
simplified data structure.
ETSI
11 ETSI EN 301 144-6 V1.1.1 (2000-12)
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 either 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 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 either 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.
10 ATS conformance
The test realizer, producing MOT and executable test suite for this ATS specification, shall comply with the
requirements of ISO/IEC 9646-4 [2]. In particular, these concern the realization of an executable test suite based to this
ATS specification. The test realizer shall provide a statement of conformance of the MOT to this ATS specification.
An executable test suite 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.
ETSI
12 ETSI EN 301 144-6 V1.1.1 (2000-12)
Annex A (normative):
Partial 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: EN 301 144-1
PICS:
Previous PCTR (if any):
ETSI
13 ETSI EN 301 144-6 V1.1.1 (2000-12)
A.1.3 Testing environment
PIXIT Re
...