SIST EN 300 286-4 V1.3.3:2005

• Abstract:

  To handle comments and incorporate appropriate corrections into the ATS of DSS1 L2

• Status: Published
• Publication Date: 31-Mar-2005
• 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-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Ref Project: ETSI EN 300 286-4 V1.3.3 (2000-05) - Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

SIST EN 300 286-4 V1.3.3:2005 is the SIST adoption of ETSI EN 300 286-4 Version 1.3.3 for the Integrated Services Digital Network (ISDN) User-to-User Signalling (UUS) supplementary service over the Digital Subscriber Signalling System No. one (DSS1) protocol. It specifies the Abstract Test Suite (ATS) and a partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the user side. Engineers, test laboratories, and suppliers use it to prepare, run, and document conformance tests for user-side UUS implementations.

What does SIST EN 300 286-4 V1.3.3:2005 specify?

SIST EN 300 286-4 V1.3.3:2005 specifies the user-side ATS and partial PIXIT proforma for implementations that conform to EN 300 286-1 on the T reference point or coincident S and T reference point. It is the fourth part of the EN 300 286 series and it belongs with the protocol specification and the test purpose documents for the user side.

The document is organized into clauses on scope, references, definitions and abbreviations, the abstract test method, untestable test purposes, ATS conventions, ATS to Test Purpose mapping, and conformance for PCTR, PIXIT, and ATS. The annexes then provide the forms and the ATS itself.

Annex	What it covers
Annex A	Protocol Conformance Test Report (PCTR) proforma
Annex B	Partial PIXIT proforma
Annex C	Abstract Test Suite (ATS)
Annex D	General structure of ATS
Annex E	Change record

What are the key requirements of SIST EN 300 286-4 V1.3.3:2005?

SIST EN 300 286-4 V1.3.3:2005 is primarily a conformance-testing document. Its key requirements are about how the ATS is structured, how tests are executed, how results are reported, and how the supporting PIXIT and PCTR forms are completed.

Test method and observation points

Clause 4 applies the remote test method. The Point of Control and Observation (PCO) is placed at the service access point between layers 2 and 3 and is called L. Verdicts depend on what is observed at that PCO, while a second informal PCO called O is used only to describe operator actions and test co-ordination. In practice, this means the test system must be arranged so that layer-2 and layer-3 behavior can be stimulated and observed from the outside.

Test purposes and ATS structure

Clause 5 states that there are no untestable test purposes associated with the ATS. Clause 6 then defines how the ATS is written, including type definitions, constraints, and dynamic behavior. This matters because the ATS is intended to be turned into a working executable test suite with predictable structure.

The ATS uses TTCN and ASN.1 together. Clause 6 explains that structured types, ASPs, and PDUs are declared with a one-to-one relationship where needed, and that test suite parameters and test case variables are used where restrictions must be carried through the test specification. For a reader, this means the test cases are meant to be machine-realizable rather than descriptive only.

Constraint handling and matching behavior

Clause 6 also shows how send and receive constraints are written for ASN.1 types such as the Facility Information Element (FIE). Send constraints fix a specific component, while receive constraints may accept a superset of components using the SUPERSET mechanism. In practice, this lets the same ATS validate both exact message construction and tolerant message reception.

The document also defines matching symbols such as AnyOrOmit, AnyValue, SuperSet, Omit, AnyOne, and AnyOrNone. These are important because they control how test equipment matches received protocol data without over-specifying values that may vary.

Encoding rules

Clause 6 specifies that the default encoding for ASN.1 constraints in this ATS is ISDN encoding, not Basic Encoding Rules (BER), unless BER is explicitly indicated in the table header. When BER is used, the ATS expects different length forms to be exercised during a test campaign, including indefinite, short definite, and long definite forms. In practice, test realizers need to configure encoding carefully so they do not send BER where the ATS does not allow it.

Mapping from test purposes to test cases

Clause 7 maps Test Purposes (TPs) directly to test case names on a one-to-one basis. That makes it easier to trace a test result back to the original purpose from EN 300 286-3. For users of the standard, this supports traceability during implementation, execution, and audit.

Conformance reporting and proformas

Clauses 8 to 10 define conformance requirements for PCTR, PIXIT, and ATS realizations. Annex A gives the PCTR proforma that a test laboratory uses to report results. Annex B gives the partial PIXIT proforma that the laboratory or client completes for a specific System Under Test (SUT). Annex C contains the ATS in TTCN form. In practice, these clauses tell each party what documentation must accompany a conformance test campaign.

What terms does SIST EN 300 286-4 V1.3.3:2005 define?

SIST EN 300 286-4 V1.3.3:2005 uses the standard conformance-testing terms from ISO/IEC 9646-1.

• Abstract Test Suite (ATS) - the set of abstract test cases, test steps, and related declarations used to test conformance.
• Implementation Under Test (IUT) - the implementation being assessed against the protocol specification.
• Point of Control and Observation (PCO) - the point where the tester controls and observes protocol behavior.
• Protocol Implementation Conformance Statement (PICS) - the statement that records which protocol options the implementation supports.
• Protocol Implementation eXtra Information for Testing (PIXIT) - the extra implementation-specific information needed to run tests.
• System Under Test (SUT) - the complete system, including the IUT and its test environment context.
• Tree and Tabular Combined Notation (TTCN) - the notation used to write the ATS.
• User-to-User Signalling (UUS) - the supplementary service covered by the standard.

Who uses SIST EN 300 286-4 V1.3.3:2005?

SIST EN 300 286-4 V1.3.3:2005 is used by conformance test laboratories, protocol implementers, and equipment vendors working with ISDN DSS1 user-side UUS. It is also relevant to test realizer teams that build executable test suites from the ATS.

In practice, users apply it to these tasks:

• preparing a PIXIT for a specific product or system
• realizing an Executable Test Suite (ExTS) from the ATS
• running remote conformance tests against the user-side interface
• completing PCTR reports for customers or audits
• checking whether an implementation matches the required PICS and test purposes

What changed in SIST EN 300 286-4 V1.3.3:2005 from the previous edition?

SIST EN 300 286-4 V1.3.3:2005 incorporates a revised ATS. The change record also notes conversion to EN layout, replacement of references to ETS 300 102 with EN 300 403, and substitution of non-specific references to basic standards so they point to the latest version.

Which standards are used with SIST EN 300 286-4 V1.3.3:2005?

SIST EN 300 286-4 V1.3.3:2005 is used together with the standards listed in its references and the other parts of EN 300 286.

Reference	What it contributes
EN 300 286-1	The protocol specification for UUS over DSS1
EN 300 286-2	The PICS proforma specification
EN 300 286-3	The user-side Test Suite Structure and Test Purposes (TSS&TP)
EN 300 286-5	The network-side TSS&TP
EN 300 286-6	The network-side ATS and partial PIXIT proforma
EN 300 403-1	DSS1 signalling network layer for circuit-mode basic call control
EN 300 196-1	Generic functional protocol for supplementary services support
ISO/IEC 9646-1 to 5	Conformance testing concepts, ATS writing, TTCN, test realization, and laboratory/client requirements
ITU-T I.411	ISDN user-network reference configurations
CCITT X.209	Basic Encoding Rules for ASN.1
ETS 300 102	Earlier basic call control reference named in the change record

What does the SIST EN 300 286-4 V1.3.3:2005 document contain?

SIST EN 300 286-4 V1.3.3:2005 contains a TTCN-based ATS, the partial PIXIT proforma, and a PCTR proforma. It also includes a remote test method figure, conformance rules, and detailed conventions for declarations, constraints, and dynamic behavior.

The annexes provide the practical test material. Annex A gives the report form for recording static and dynamic conformance results, Annex B asks for implementation-specific parameters such as call reference length, message behavior, and timer values, and Annex C contains the ATS in both graphical and machine-processable TTCN forms.

Clause 6 includes representative type and constraint examples, including ASN.1 definitions for information elements and TTCN ASP and PDU handling. Those examples show how the ATS expects testers to model protocol data, parameterized values, and message matching during conformance testing.

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY
PHGXSRUDEQLãNDVLJQDOL]DFLMD8863URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMH
ãW'66GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]D
LMD]DSUHVNXãDQMHGHOQHL]YHGEHSURWRNROD3,;,73URIRUPDVSHFLILNDF
XSRUDEQLND
Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma specification for the user
Ta slovenski standard je istoveten z: EN 300 286-4 Version 1.3.3
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);
User-to-User Signalling (UUS) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user


2 ETSI EN 300 286-4 V1.3.3 (2000-05)
Reference
REN/SPS-05168-4
Keywords
ATS, DSS1, ISDN, PIXIT, supplementary service,
user, UUS
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 300 286-4 V1.3.3 (2000-05)
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) .8
5 Untestable test purposes.8
6 ATS conventions.8
6.1 Declarations part .8
6.1.1 Type definitions .8
6.1.1.1 Simple type definitions.8
6.1.1.2 Structured type definitions .9
6.1.1.2.1 TTCN structured type definitions.9
6.1.1.2.2 ASN.1 structured type definitions.9
6.1.1.3 ASP type definitions.10
6.1.1.3.1 TTCN ASP type definitions.10
6.1.1.3.2 ASN.1 ASP type definitions .11
6.1.1.4 PDU type definitions.11
6.1.1.4.1 TTCN PDU type definitions.11
6.1.1.4.2 ASN.1 PDU type definitions .11
6.1.2 Test suite constants .11
6.1.3 Test suite parameters .11
6.1.4 Variables.11
6.1.4.1 Test suite variables.11
6.1.4.2 Test case variables .11
6.1.5 Test suite operation definitions.12
6.2 Constraints part.12
6.2.1 Structured type constraint declaration.12
6.2.2 ASN.1 type constraint declaration .12
6.2.2.1 Specification of encoding rules .13
6.2.3 ASP type constraint declaration.14
6.2.3.1 ASN.1 ASP type constraint declaration .14
6.2.3.2 TTCN ASP type constraint declaration.14
6.2.4 PDU type constraint declaration .14
6.2.4.1 ASN.1 PDU type constraint declaration.14
6.2.4.2 TTCN PDU type constraint declaration .14
6.2.5 Chaining of constraints .14
6.2.5.1 Static chaining.14
6.2.5.2 Dynamic chaining.15
6.2.6 Derived constraints .15
6.2.7 Parameterized constraints .15
6.2.8 Value assignment.15
6.2.8.1 Specific values .15
6.2.8.2 Matching values .15
6.3 Dynamic part .16
6.3.1 Test cases.16
6.3.2 Test steps .16
6.3.3 Defaults.16
ETSI
4 ETSI EN 300 286-4 V1.3.3 (2000-05)
7 ATS to TP map.16
8 PCTR conformance.16
9 PIXIT conformance.16
10 ATS conformance .17
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma.18
A.1 Identification summary .18
A.1.1 Protocol conformance test report.18
A.1.2 IUT identification.18
A.1.3 Testing environment.18
A.1.4 Limits and reservations.19
A.1.5 Comments.19
A.2 IUT Conformance status .19
A.3 Static conformance summary.19
A.4 Dynamic conformance summary.20
A.5 Static conformance review report .20
A.6 Test campaign report.21
A.7 Observations.23
Annex B (normative): Partial PIXIT proforma.24
B.1 Identification summary .24
B.2 Abstract test suite summary .24
B.3 Test laboratory .24
B.4 Client (of the test laboratory).25
B.5 System Under Test (SUT).25
B.6 Protocol information .26
B.6.1 Protocol identification .26
B.6.2 Parameter values.26
B.6.3 User-user information element values .26
B.6.4 Sending of messages by IUT .27
B.6.5 Timer values.28
Annex C (normative): Abstract Test Suite (ATS).29
C.1 The TTCN Graphical form (TTCN.GR).29
C.2 The TTCN Machine Processable form (TTCN.MP) .29
Annex D (informative): General structure of ATS.30
Annex E (informative): Change record.31
E.1 Changes between EN 300 286-4 V1.2 and 1.3 .31
E.2 Changes between ETS 300 286-4 and EN 300 286-4 V1.2 .31
History.32
ETSI
5 ETSI EN 300 286-4 V1.3.3 (2000-05)
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 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 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 4 of a multi-part standard covering the Integrated Services Digital Network (ISDN); User-
to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol, as
described 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: 5 May 2000
Date of latest announcement of this EN (doa): 31 August 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2001
Date of withdrawal of any conflicting National Standard (dow): 28 February 2001
ETSI
6 ETSI EN 300 286-4 V1.3.3 (2000-05)
1 Scope
This fourth part of EN 300 286 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma for the user side of the T reference point or coincident S and T reference
point (as defined in ITU-T Recommendation I.411 [11]) of implementations conforming to the stage three standard for
the User-to-User Signalling (UUS) supplementary service for the pan-European Integrated Services Digital Network
(ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 286-1 [2].
EN 300 286-3 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXIT
proforma. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the network side of the T
reference point or coincident S and T reference point of implementations conforming to EN 300 286-1 [2].
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 EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;
Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".
[2] ETSI EN 300 286-1 (V1.2): "Integrated Services Digital Network (ISDN); User-to-User Signalling
(UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 1: Protocol specification".
[3] ETSI EN 300 286-2 (V1.2): "Integrated Services Digital Network (ISDN); User-to-User Signalling
(UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".
[4] ETSI EN 300 286-3 (V1.2): "Integrated Services Digital Network (ISDN); User-to-User Signalling
(UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user".
[5] ETSI EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for
the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 1: Protocol specification".
[6] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[7] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract Test Suite specification".
[8] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".
[9] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
ETSI
7 ETSI EN 300 286-4 V1.3.3 (2000-05)
[10] 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".
[11] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[12] CCITT Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract Syntax
Notation One (ASN.1)".
[13] ETSI ETS 300 102 (all parts): "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Abstract Test Suite (ATS): see ISO/IEC 9646-1 [6].
Implementation Under Test (IUT): see ISO/IEC 9646-1 [6].
Lower Tester (LT): see ISO/IEC 9646-1 [6].
Point of Control and Observation (PCO): see ISO/IEC 9646-1 [6].
Protocol Implementation Conformance Statement (PICS): see ISO/IEC 9646-1 [6].
PICS proforma: see ISO/IEC 9646-1 [6].
Protocol Implementation eXtra Information for Testing (PIXIT): see ISO/IEC 9646-1 [6].
PIXIT proforma: see ISO/IEC 9646-1 [6].
System Under Test (SUT): see ISO/IEC 9646-1 [6].
UpperTester(UT): see ISO/IEC 9646-1 [6].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
ExTS Executable Test Suite
FIE Facility Information Element
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
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
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
ETSI
8 ETSI EN 300 286-4 V1.3.3 (2000-05)
TTCN Tree and Tabular Combined Notation
UT Upper Tester
UUS User-to-User Signalling
4 Abstract Test Method (ATM)
The remote test method is applied for the AOC user ATS. The Point of Control and Observation (PCO) resides at the
service access point between layers 2 and 3. 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.
Tester SUT
LT IUT
PCO
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 1: Remote test method
ISO/IEC 9646-2 [7] allows the informal expression of Test Co-ordination Procedures (TCP) between the System Under
Test (SUT) upper layer(s) and the Lower Tester (LT). In the ATS contained in annex C, TCP is achieved by use of a
second "informal" PCO, called "O" (for Operator). This PCO is used to specify control but not observation above the
IUT and consequently, events at this PCO are never used to generate test case verdicts. The use of this O PCO is
regarded as a preferred alternative to the use of the implicit send event, in that it allows the ATS to specify in a clear and
meaningful way what actions are required to be performed on the IUT.
5 Untestable test purposes
There are no untestable test purposes associated with this ATS.
6 ATS conventions
This clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses are arranged
in a way more suitable to the present document.
6.1 Declarations part
6.1.1 Type definitions
6.1.1.1 Simple type definitions
Where appropriate, simple types have a length, a value list or a range restriction attached.
Simple types defined as being of some string type (e.g. BIT STRING, OCTET STRING), have a length restriction or a
value list attached.
Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.
ETSI
9 ETSI EN 300 286-4 V1.3.3 (2000-05)
6.1.1.2 Structured type definitions
6.1.1.2.1 TTCN structured type definitions
All structured type definitions are provided with a full name.
All elements in every structured type definition, defined as being of some string type (e.g. BIT STRING,
OCTET STRING), have a length restriction attached.
If an element in a structured type definition is defined as being of a referenced type, the (possible) restriction is defined
in that referenced type.
For information elements the identifier, which is unique for each element, has its type defined as a simple type where the
value list is restricted to the single value which is the identifier itself. This has the advantage that it allows a test system
derived from this ATS to easily identify information elements embedded in messages. An ATS where information
element identifiers are represented as unrestricted types can present difficulties for a derived test system in the case
where it needs to find one information element embedded in a number of others and the constraints for the other
elements have the any-or-omit value. In such a case the test system cannot easily find the beginning of each information
element.
6.1.1.2.2 ASN.1 structured type definitions
ASN.1 has been used for three major reasons:
1) 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;
2) ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions;
3) it is necessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the
base standards.
The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose of achieving
type-compatibility.
Tables 1 and 2 show the typical use of ASN.1. The FIE type in table 1 is written in ASN.1 to permit the use of the SET
OF construction in the components field. Constraints of the FIE type can therefore be written using the SUPERSET
function which allows to match a single component which may be delivered together with a set of other components.
Table 2 shows the reject component type which is defined following the ASN.1 declaration in EN 300 196-1 [5].
Table 1: ASN.1 type definition FIE
ASN.1 Type Definition
Type Name : FIE
Comments : Facility information element taken from EN 300 196; 11.2.2.1.
Specified here for both send & receive event.
Type Definition
SEQUENCE {
informationElementIdentifier FIE_I,
length FIE_LengthType,
extBit BIT STRING (SIZE (1)),
spareBits BIT STRING (SIZE (2)),
protocolProfile BIT STRING (SIZE (5)),
components SET OF Component }
ETSI
10 ETSI EN 300 286-4 V1.3.3 (2000-05)
Table 2: ASN.1 type definition RejectComponent
ASN.1 Type Definition
Type Name : RejectComponent
Comments : Reject Component is not specific to any particular operation. The invokeID may be
used to identify a specific operation.
Type Definition
SEQUENCE {
invokedID CHOICE {
invokeID InvokeIDType,
null NULL },
problem CHOICE {
generalProblem [0] IMPLICIT GeneralProblem,
invokeProblem [1] IMPLICIT InvokeProblem,
returnResultProblem [2] IMPLICIT ReturnResultProblem,
returnErrorProblem [3] IMPLICIT ReturnErrorProblem } }
Table 3 shows an example of how ASN.1 can be used to model unordered sequences.
Table 3: ASN.1 type definition FIES
ASN.1 Type Definition
Type Name : FIES
Comments :
Type Definition
SET OF FIE
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.1.1.3 ASP type definitions
6.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all. The relationship between an ASP type and a PDU
type is one-to-one. That is, there exists one ASP type definition for each PDU type definition (if that ASP type contains
a PDU).
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 4. Such ASPs are only used for requesting or
receiving service from the lower layer.
Table 4: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME : DL_REL_IN
(DL_RELEASE_INDICATION)
PCO Type : SAP
Comments :
Parameter Name | Parameter Type | Comments
Detailed Comments :
ETSI
11 ETSI EN 300 286-4 V1.3.3 (2000-05)
Table 5 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no other
parameters.
Table 5: TTCN ASP type definition DL_DATA_RQ_ALERT
TTCN ASP Type Definition
ASP NAME : DL_DATA_RQ_ALERT
(DL_DATA_REQUEST)
PCO Type : SAP
Comments :
Parameter Name | Parameter Type | Comments
mun (MessageUnit) |ALERT_PDU |
Detailed Comments :
6.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
6.1.1.4 PDU type definitions
6.1.1.4.1 TTCN PDU type definitions
The TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded in ASPs.
If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element has a restriction
attached to it.
6.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
6.1.2 Test suite constants
No test suite constants are used or defined in this ATS.
6.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type or a referenced type. A referenced type is used when it
is necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test
suite parameter table). The referenced type can have a length or value restriction attached to it in its declaration table.
6.1.4 Variables
6.1.4.1 Test suite variables
No test suite variables are used or defined in this ATS.
6.1.4.2 Test case variables
Each test case variable is defined in terms of a predefined type or a referenced type. A referenced type is used when it is
necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test case
variable table). The referenced type can have a length or value restriction attached to it in its declaration table.
Where test case variables are used in constraints, they are passed as formal parameters.
ETSI
12 ETSI EN 300 286-4 V1.3.3 (2000-05)
6.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 6: Test suite operation definition ASSIGN_CHI
Test Suite Operation Definition
Operation Name : ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)
Result Type : CHI
Comments : This operation is used to assign a correct Channel identification information
element to PDUs dependent on the type of access that is tested.
Description
{
if(basic_flag)
return basic;
else
return primary
}
Detailed comments :
The test suite operation definition shown in table 6 is used in the constraints part when assigning an element of type CHI
a value. As previously described, the CHI type can be defined in two ways depending on whether the ATS is testing
basic or primary rate access. This operation is used to assign a value to an element of CHI type. It takes three
parameters:
primary: a constraint of type CHI valid for primary rate access;
basic: a constraint of type CHI valid for basic access;
basic_flag: a Boolean value: TRUE if basic access is applicable, FALSE otherwise.
This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will then be
assigned to the specific element of type CHI.
6.2 Constraints part
6.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
6.2.2 ASN.1 type constraint declaration
Constraints of this type are used to assign the corresponding type a specific value. These constraints are used for the
purpose of modelling unordered data or specific types that cannot be expressed in TTCN.
A value assigned to an element of type SET OF differs depending on whether it is a send or receive constraint.
Table 7: ASN.1 type constraint declaration fIEs (send constraint)
ASN.1 Type Constraint Declaration
Constraint Name : fIEs(comp : Component)
ASN.1 Type : FIE
Derivation Path :
Comments : Send FIE which will contain one component "comp".
Description
{
informationElementIdentifier '00011100'B,
length CALC_FIE_LENGTH(comp),
extBit '1'B,
spareBits '00'B,
protocolProfile '10001'B,
components {comp}
}
Detailed comments :
NOTE 1: The last element in the constraint, components,isoftype SET OF Component where Component is
structured data of some type.
ETSI
13 ETSI EN 300 286-4 V1.3.3 (2000-05)
If the constraint is a send constraint (see table 7) the value for the component element is stated as "{comp}" where comp
is an argument received as a parameter. The "{" and "}" turns the value into a SET OF value which is correct according
to that element's type definition.
Table 8: ASN.1 type constraint declaration fIEr (receive constraint)
ASN.1 Type Constraint Declaration
Constraint Name : fIEr(comp : Component)
ASN.1 Type : FIE
Derivation Path :
Comments : A received FIE which can contain several components, but which contains at
least "comp".
Description
{
informationElementIdentifier '00011100'B,
length '????????'B,
extBit '1'B,
spareBits '00'B,
protocolProfile '10001'B,
components SUPERSET({comp})
}
Detailed comments :
NOTE 2: The last element in the constraint, components,isoftype SET OF Component where Component is
structured data of some type.
If the constraint is a receive constraint (as in table 8) the corresponding matching value is assigned by using
SUPERSET. The keyword SUPERSET has an argument that is type compatible with the type definition of that field. In
table 8, the element named components is defined as "SET OF Component" and this implies that the argument to
SUPERSET should be of type SET OF Component. This is achieved the same way as for send constraints, enclosing the
value in curly brackets.
The semantic of SUPERSET is stated in ISO/IEC 9646-3 [8], subclause 11.6.4.7. In short it defines the semantic as
follows: "A value that uses SUPERSET matches the incoming value if, and only if, the incoming value contains at least
all of the elements defined within the SUPERSET, and may contain more elements." This is exactly the semantic
definition used in this ATS.
6.2.2.1 Specification of encoding rules
At the time of specifying this ATS the mechanisms related to encoding of ASN.1 types, specified in DAM-2 of
ISO/IEC 9646-3 [8], were not yet stable. Nevertheless as there is a variation in the encoding rules as applied to ASN.1
types and constraints specified in this ATS, a mechanism is used to differentiate the different encoding rules. Given the
non-finalized status of DAM-2, a solution which is broadly in the spirit of DAM-2 has been created. Comment fields
have been used as a means of including the 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 CCITT Recommendation X.209 [12]. 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 (ExTS) 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.
For BER encoding, an indication is given in the comments field of the table header. For this ATS such indications
appear in the ASN.1 type constraint declaration tables only. In the first line of the table header comment field, the
notation "ASN1_Encoding: BER"isused.
Note that within BER, there are a number of variations for the encoding of lengths of fields. According to
EN 300 196-1 [5], 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 [5] gives guidelines but makes no restrictions on the length forms within
BER which an IUT may apply.
ETSI
14 ETSI EN 300 286-4 V1.3.3 (2000-05)
In relation to components sent by the tester to the IUT, implementors of this ATS shall use a variety of length forms
such that at least one of each of the length forms is sent to the IUT during a test campaign. The variations of length
forms to be used are indefinite, short definite and long definite.
In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.
Table 9: ASN.1 type constraint declaration showing use of encoding variation
ASN.1 Type Constraint Declaration
Constraint Name : Beg3PTYinv
ASN.1 Type : Component
Derivation Path :
Comments : ASN1_Encoding: BER
Receive component: Begin3PTY invoke component
Description
begin3PTY_Components
begin3PTY_InvokeComp
{ invokeID ? ,
operation_value localValue 4}
Detailed comments :
6.2.3 ASP type constraint declaration
6.2.3.1 ASN.1 ASP type constraint declaration
No ASN.1 ASP type constraint declaration exists in this ATS.
6.2.3.2 TTCN ASP type constraint declaration
For TTCN ASP constraint declarations there is a one-to-one relationship between its type and the constraint. That is,
there is only one constraint for each TTCN ASP Type Declaration. The reason for this is that the ASPs are used only for
carrying a specific PDU value. The many ASP constraints (and types) could have been avoided by using the meta type
PDU, but that was not suitable as values inside a specific PDU have to be referenced. To reference elements inside a
valueofmetatype PDU is not allowed according to ISO/IEC 9646-3 [8], so each ASP has to be defined as having a
parameter of a specific PDU type.
In all ASP constraints the embedded PDU constraint is either chained static or "semi-dynamic". That is, the PDU
constraint is always fixed to a specific ASP constraint but it (the PDU) may be parameterized.
All ASP constraints have a specific value for its parameter. No matching symbols are used in ASPs.
6.2.4 PDU type constraint declaration
6.2.4.1 ASN.1 PDU type constraint declaration
No ASN.1 PDU type constraint declaration exists in this ATS.
6.2.4.2 TTCN PDU type constraint declaration
PDU constraints are used for assigning values or patterns to the data being sent or received.
6.2.5 Chaining of constraints
6.2.5.1 Static chaining
Static chaining, that is a fixed reference to a specific constraint, is used in this ATS. The static chaining is used for static
binding of both variables and sub-structures.
ETSI
15 ETSI EN 300 286-4 V1.3.3 (2000-05)
6.2.5.2 Dynamic chaining
Dynamic chaining is achieved when having a reference to a value which is unknown. The only thing known (before run-
time) is the type of that reference. The reference is passed as a parameter. Strict dynamic chaining is not used in this
ATS. What is used is something that is called "semi-dynamic chaining". The definition of semi-dynamic chaining is that
the fixed reference is parameterized with an unknown value. That value is received as a parameter.
Table 10: TTCN ASP constraint declaration A_RST1
TTCN ASP Constraint Declaration
Constraint Name : A_RST1(FLAG : INTEGER)
ASN.1 Type : DL_DAT_IN_RESTARTr
Derivation Path :
Comments :
Parameter Name Parameter Value Comments
mun RST1(FLAG) RST1(FLAG)
Detailed comments :
Table 10 is an example of semi-dynamic chaining. The TTCN ASP constraint is parameterized with an INTEGER value
named FLAG. That value is passed further down in the structure as a parameter to a static named PDU constraint
reference.
6.2.6 Derived constraints
No derivation of any constraints is used. All constraints are considered to be base constraints.
6.2.7 Parameterized constraints
Parameterized constraints are used in this ATS.
6.2.8 Value assignment
6.2.8.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.
6.2.8.2 Matching values
As matching values the following mechanisms are used:
Instead of Value:
AnyOrOmit "*"
AnyValue "?"
SuperSet SUPERSET
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
ETSI
16 ETSI EN 300 286-4 V1.3.3 (2000-05)
6.3 Dynamic part
6.3.1 Test cases
Each test case contains the test purpose text from EN 300 286-3 [4]. To be able to read and understand the test case
dynamic behaviour it is recommended that the test steps are understood first.
6.3.2 Test steps
Much use has been made of test steps to avoid needless repetition of dynamic behaviour. Many test steps are based on
those used for the ISDN basic call ATS.
6.3.3 Defaults
Note the use of the RETURN statement which is defined in DAM1 of ISO/IEC 9646-3 [8]. This allows valid
background behaviour to be handled in the default tree with a possibility to return to the original set of alternatives in the
test case.
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 [10], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [10].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a
client to
...