SIST ETS 300 012-6 E2:2003

• Abstract:

  This second edition of ETS 300 012 will incorporate the test suite specification and referenced material from ITU-T I.430

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 012-6 ed.2 (1998-10) - Integrated Services Digital Network (ISDN); Basic User-Network Interface (UNI); Part 6: Abstract Test Suite (ATS) specification for interface IA

SIST ETS 300 012-6 E2:2003 is the Slovenian adoption of ETS 300 012-6 Edition 2, an ETSI standard for the Integrated Services Digital Network (ISDN) Basic User-Network Interface (UNI). It specifies an Abstract Test Suite (ATS) for the user side of the T reference point, or the coincident S and T reference point, in pan-European ISDN basic access implementations conforming to ETS 300 012-1. In practice, it is the document to use when you need the abstract conformance test definition for that layer 1 interface.

What does SIST ETS 300 012-6 E2:2003 specify?

SIST ETS 300 012-6 E2:2003 specifies the ATS for testing ISDN basic access implementations at the user side of the T reference point, or the coincident S and T reference point. It is part 6 of ETS 300 012 and is linked to the layer 1 specification in ETS 300 012-1.

The document is organized into:

• scope and normative references
• definitions and abbreviations
• the Abstract Test Method (ATM)
• untestable test purposes
• ATS conventions
• the ATS to Test Purpose (TP) map
• conformance rules for the Protocol Conformance Test Report (PCTR) and the ATS
• normative annexes for the PCTR proforma and the ATS itself
• an informative annex showing the general ATS structure

Annex	What it covers
Annex A	Normative PCTR proforma, including identification, conformance status, summaries, and the test campaign report
Annex B	Normative ATS, with TTCN.GR and TTCN.MP forms for basic access
Annex C	Informative general structure of the ATS

What are the key requirements of SIST ETS 300 012-6 E2:2003?

SIST ETS 300 012-6 E2:2003 is built as a TTCN-based conformance test specification. The practical requirement is that the ATS, the resulting executable tests, and the test reports all line up with the ISO/IEC conformance testing framework.

Abstract test method and observation points

Clause 4 states that the remote test method is used. The Points of Control and Observation (PCOs) are at the service access point between the physical connection and layer 1, and they are named L, Ld, and Lp. In practice, this means the tester observes behavior only at those points, rather than directly inside the lower protocol layers.

Clause 4 also says that only PDUs received from the IUT over the physical connection are directly accessible to the tester. The ATS checks response to stimuli, timer duration, and state transitions. That matters because the test verdicts depend on externally visible behavior, not internal implementation details.

Physical layer test behavior

Clause 4.1 explains that silence in the physical layer is treated as sending Info 0, and that when tester action is not specified, the last specified Info is considered to continue. It also notes the use of an operation to fill D-Bit positions inside Info 4. For implementers and test labs, this tells you how to interpret “no action” and how to handle repeated physical-layer signaling in the ATS.

ATS structure and TTCN conventions

Clause 6 sets the conventions for the ATS. It covers:

• simple and structured type definitions
• ASP and PDU type definitions
• test suite constants, parameters, and variables
• test suite operation definitions
• constraints and constraint chaining
• dynamic test cases, test steps, and defaults

This matters because it tells a test realizer how the ATS is written and how to derive an executable test suite from it. The document uses TTCN structured types and TTCN ASP/PDU definitions, and the dynamic part is organized around test cases and reusable test steps.

Constraints and matching

Clause 6.1.2 says the ATS uses structured type constraints, TTCN ASP constraints, TTCN PDU constraints, static chaining, and semi-dynamic chaining. It also defines matching symbols such as AnyOrOmit, AnyValue, Omit, AnyOne, and AnyOrNone. In practice, these are the mechanisms that let the ATS describe exact values where needed and flexible patterns where the test allows variation.

Mapping and conformance reporting

Clause 7 says the TP identifiers are reused as test case names, so the ATS has a one-to-one mapping to the Test Purpose set. Clause 8 requires a PCTR that conforms to the proforma in Annex A when the lab is asked to produce one. Clause 9 requires any Means Of Testing (MOT) and Executable Test Suite (ExTS) derived from the ATS to comply with ISO/IEC 9646-4, and it requires the ExTS to be technically equivalent to the ATS in Annex B.

For a buyer, quality manager, or test lab, this is the key practical point: the document is not just a theory description. It also defines how conformance results are reported and what it means for an executable realization to claim conformance.

What terms does SIST ETS 300 012-6 E2:2003 define?

The document uses the conformance-testing vocabulary of ISO/IEC 9646-1 and adds its own abbreviations.

• Implementation Under Test (IUT) - the implementation being checked for conformance.
• System Under Test (SUT) - the broader system that contains or includes the IUT during testing.
• Abstract Test Suite (ATS) - the abstract set of tests and verdict logic defined before executable realization.
• Lower Tester (LT) - the tester component that interacts with the system at the lower interface.
• Upper Tester (UT) - the tester component that interacts with the system above the IUT where applicable.
• Point of Control and Observation (PCO) - the point where the tester controls and observes behavior.
• Protocol Conformance Test Report (PCTR) - the report format used to record conformance test results.

Who uses SIST ETS 300 012-6 E2:2003?

SIST ETS 300 012-6 E2:2003 is used by test laboratories, test realizers, and organizations that need to verify ISDN basic access implementations against ETS 300 012-1. It is also relevant to engineers designing layer 1 equipment, quality teams preparing conformance evidence, and buyers who need to specify a conformance test basis in procurement or acceptance work.

In practice, the main tasks are:

• deriving an executable test suite from the ATS
• running conformance tests on an Implementation Under Test
• producing a PCTR using the required proforma
• checking that an implementation’s PICS matches the static requirements
• assessing whether the implementation behaves correctly under dynamic test cases

What changed in SIST ETS 300 012-6 E2:2003 from the previous edition?

This second edition incorporates the test suite specification and referenced material from ITU-T I.430. The history section identifies it as the second edition, following the first edition of April 1992 and the later publication cycle that led to the October 1998 ETS.

Which standards are used with SIST ETS 300 012-6 E2:2003?

The document relies on the following referenced standards and recommendations:

• ETS 300 012-1 - provides the layer 1 specification that the ATS tests against.
• ETS 300 012-2 and ETS 300 012-3 - provide the ICS and IXIT specifications named in the normative references.
• ISO/IEC 9646-1 to ISO/IEC 9646-5 - provide the conformance testing framework, ATS specification method, TTCN, test realization, and laboratory/client requirements.
• ITU-T Recommendation I.411 - defines the ISDN reference configurations used for the reference point terminology.
• ITU-T Recommendation I.112 - provides ISDN vocabulary.
• CCITT Recommendation E.164 - provides numbering plan context for the ISDN era.
• ITU-T Recommendation I.430 - provides the basic user-network interface layer 1 specification that this ATS is based on.

What does the SIST ETS 300 012-6 E2:2003 document contain?

The document contains a TTCN-based ATS, a remote test method description, and the rules for conformance reporting. Annex A gives the PCTR proforma, including identification data, IUT status, static and dynamic summaries, and the test campaign report table used to record verdicts.

Annex B contains the ATS itself in TTCN.GR and TTCN.MP forms for basic access. The text says the graphical representation is in a PDF file and the machine-processable form is in an ASCII file that accompany the standard. Annex C gives the general structure of the ATS, which helps readers navigate the declaration part, constraints part, and dynamic part.

The main body also explains how test cases, test steps, defaults, type definitions, constraints, and chaining are organized. For a test lab, that is the practical working material needed to build, run, and report a conformance test system for ISDN basic access.

SLOVENSKI STANDARD
01-december-2003
Digitalno omrežje z integriranimi storitvami (ISDN) – Osnovni vmesnik uporabnik-
omrežje (UNI) – 6. del: Specifikacija za abstraktni preskušalni niz (ATS) za vmesnik
IA
Integrated Services Digital Network (ISDN); Basic User-Network Interface (UNI); Part 6:
Abstract Test Suite (ATS) specification for interface IA
Ta slovenski standard je istoveten z: ETS 300 012-6 Edition 2
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 ETS 300 012-6
TELECOMMUNICATION October 1998
STANDARD Second Edition
Source: TM Reference: RE/TM-03038-6
ICS: 33.020
Key words: ATS, basic, ISDN, layer 1, testing, transmission, UNI
Integrated Services Digital Network (ISDN);
Basic User Network Interface (UNI);
Part 6: Abstract Test Suite (ATS) specification for interface I
A
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.fr - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
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 1998. All rights reserved.

Page 2
ETS 300 012-6: October 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 012-6: October 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 Abstract Test Method (ATM).8
4.1 Particularities of the physical layer.9
5 Untestable test purposes.9
6 ATS conventions .9
6.1 General design issues .9
6.1.1 Declarations part .10
6.1.1.1 Type definitions.10
6.1.1.1.1 Simple type definitions.10
6.1.1.1.2 Structured type definitions .10
6.1.1.1.3 Abstract Service Primitive (ASP) type
definitions.10
6.1.1.1.4 PDU type definitions .11
6.1.1.2 Test suite constants.11
6.1.1.3 Test suite parameters.11
6.1.1.4 Variables.11
6.1.1.4.1 Test suite variables.11
6.1.1.4.2 Test case variables.11
6.1.1.5 Test suite operation definitions.11
6.1.1.6 Alias definitions.11
6.1.2 Constraint part.12
6.1.2.1 Structured type constraint declaration .12
6.1.2.2 ASN.1 type constraint declaration .12
6.1.2.3 ASP type constraint declaration.12
6.1.2.3.1 ASN.1 ASP type constraint declaration 12
6.1.2.3.2 TTCN ASP type constraint declaration .12
6.1.2.4 PDU type constraint declaration .12
6.1.2.4.1 ASN.1 PDU type constraint
declaration .12
6.1.2.4.2 TTCN PDU type constraint declaration.12
6.1.2.5 Chaining of constraints .12
6.1.2.5.1 Static chaining.12
6.1.2.5.2 Dynamic chaining.12
6.1.2.6 Derived constraint.12
6.1.2.7 Parameterized constraints.12
6.1.2.8 Value assignment .13
6.1.2.8.1 Specific values.13
6.1.2.8.2 Matching values.13
6.1.3 Dynamic part .13
6.1.3.1 Test cases .13
6.1.3.2 Test steps .13
6.1.3.3 Defaults.13
7 ATS to Test Purpose (TP) map.13

Page 4
ETS 300 012-6: October 1998
8 Protocol Conformance Test Report (PCTR) conformance. 13
9 ATS conformance. 14
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 15
A.1 Identification summary. 15
A.1.1 Protocol conformance test report. 15
A.1.2 IUT identification. 15
A.1.3 Testing environment. 15
A.1.4 Limits and reservations . 16
A.1.5 Comments. 16
A.2 IUT conformance status . 16
A.3 Static conformance summary. 16
A.4 Dynamic conformance summary. 17
A.5 Static conformance review report . 17
A.6 Test campaign report. 17
A.7 Observations. 20
Annex B (normative): Abstract Test Suite (ATS). 21
B.1 The TTCN Graphical form (TTCN.GR) for basic access . 21
B.2 The TTCN Machine Processable form (TTCN.MP) for basic access . 21
Annex C (informative): General structure of ATS. 22
History. 23

Page 5
ETS 300 012-6: October 1998
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the ETSI
Technical Committee Transmission and Multiplexing (TM).
This ETS concerns the basic User Network Interface (UNI) for the Integrated Services Digital Network
(ISDN) and consists of 7 parts as follows:
Part 1: "Layer 1 specification";
Part 2: "Implementation Conformance Statement (ICS) and Implementation eXtra Information for
Testing (IXIT) specification for interface I ";
A
Part 3: "Implementation Conformance Statement (ICS) and Implementation eXtra Information for
Testing (IXIT) specification for interface I ";
B
Part 4: "Conformance test specification for interface I ";
A
Part 5: "Conformance test specification for interface I ";
B
Part 6: "Abstract Test Suite (ATS) specification for interface I ";
A
Part 7: "Abstract Test Suite (ATS) specification for interface I ";
B
and is based on ITU-T Recommendation I.430 [12].
Transposition dates
Date of adoption of this ETS: 18 September 1998
Date of latest announcement of this ETS (doa): 31 January 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1999
Date of withdrawal of any conflicting National Standard (dow): 31 July 1999

Page 6
ETS 300 012-6: October 1998
Blank page
Page 7
ETS 300 012-6: October 1998
1 Scope
This part 6 of ETS 300 012 specifies the Abstract Test Suite (ATS) for the user side of the T reference
point or coincident S and T reference point (as defined in CCITT Recommendation I.411 [9]) of
implementations conforming to ETS 300 012-1 [1] for the pan-European Integrated Services Digital
Network (ISDN).
A further part of this ETS specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this
ATS.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 012-1 (1998): "Integrated Services Digital Network (ISDN); Basic User
Network Interface (UNI); Part 1: Layer 1 specification".
[2] ETS 300 012-2 (1998): "Integrated Services Digital Network (ISDN); Basic User
Network Interface (UNI); Part 2: Implementation Conformance Statement (ICS)
and Implementation eXtra Information for Testing (IXIT) specification for
interface I ".
A
[3] ETS 300 012-3 (1998): "Integrated Services Digital Network (ISDN); Basic User
Network Interface (UNI); Part 3: Implementation Conformance Statement (ICS)
and Implementation eXtra Information for Testing (IXIT) specification for
interface I ".
B
[4] ISO/IEC 9646-1 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 1:
General concepts".
[5] ISO/IEC 9646-2 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 2:
Abstract test suite specification".
[6] ISO/IEC 9646-3 (1992): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 3: The
Tree and Tabular Combined Notation (TTCN)".
[7] ISO/IEC 9646-4 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 4: Test
realization".
[8] ISO/IEC 9646-5 (1994): "Information technology; Open Systems
Interconnection; Conformance Testing Methodology and Framework; Part 5:
Requirements on test laboratories and clients for the conformance assessment
process".
[9] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces;
references configurations".
[10] ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".
[11] CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".
[12] ITU-T Recommendation I.430 (1995): "Basic user-network interface; Layer 1
specification".
Page 8
ETS 300 012-6: October 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Implementation Under Test (IUT): See ISO/IEC 9646-1 [4].
System Under Test (SUT): See ISO/IEC 9646-1 [4].
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [4].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [4].
PICS proforma: See ISO/IEC 9646-1 [4].
Lower Tester (LT): See ISO/IEC 9646-1 [4].
Upper Tester (UT): See ISO/IEC 9646-1 [4].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [4].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply, in addition to those given in
ETS 300 012-1 [1]:
ASN.1 Abstract Syntax Notation one
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
ExTS Executable Test Suite
ISO International Organization for Standardization
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
System Conformance Test Report
SCTR
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TSS&TP Test Suite Structure and Test Purposes
TTCN Tree and Tabular Combined Notation
4 Abstract Test Method (ATM)
The remote test method is applied for this ATS. The boundary between layer 1 and layer 2 is supposed to
be inaccessible. This means that the correct interaction between the Implementation Under Test (IUT)
and its upper layer on the one hand, and the management entity on the other hand, is not directly testable.
The Points of Control and Observation (PCOs) reside at the service access point between the physical
connection and "layer1". These PCOs are named "L" (for Lower), Ld for D-channel, Lp for power status.
The L PCOs are used to control and observe the behaviour of the IUT and test case verdicts are assigned
depending on the behaviour observed at these PCOs.

Page 9
ETS 300 012-6: October 1998
Tester SUT
Layer 2 Layer 2
Layer 1 IUT
L, Ld, Lp
PCOs
Service provider
Figure 1: Remote test method
Actions by the IUT are caused by either of the following events:
- with layer 1 Protocol Data Units (PDUs) delivered to the IUT via the physical connection;
- with external actions on the IUT. These events are described with Tree and Tabular Combined
Notation (TTCN) "implicit send events" whose practical execution is strictly related to the IUT
features.
Only PDUs received from the IUT via the physical connection are directly accessible to the tester. By
means of the PDUs received the following is tested for conformance:
- correct response of the IUT to a stimulus from the tester;
- correct timer duration of the implement timers;
- state transition.
Both "normal" and provocative testing are considered according to the tester behaviour.
4.1 Particularities of the physical layer
In upper layers, the tester and the IUT do not always send something, but in physical layer to send nothing
means to send Info 0. Then we shall consider in the dynamic part that when the tester action is not
specified, that means that it is still sending the last specified Info.
It is quite long to specify every Info 4 emitted by the tester to try to establish data link layer. Then an
operation is used to continuously fill in D-Bit positions inside Info 4.
5 Untestable test purposes
There are no untestable test purposes associated with this ATS.
6 ATS conventions
6.1 General design issues
Clause 6 is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses
are arranged in a way more suitable to this ETS.

Page 10
ETS 300 012-6: October 1998
6.1.1 Declarations part
6.1.1.1 Type definitions
6.1.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. BITSTRING, OCTETSTRING, IA5Sting), 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.
6.1.1.1.2 Structured type definitions
6.1.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. BITSTRING,
OCTETSTRING), 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
...