SIST ETS 300 402-7:1999

SLOVENSKI STANDARD
SIST ETS 300 402-7:1999
01-maj-1999
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'663RGDWNRYQDSRYH]RYDOQDSODVWGHO$EVWUDNWQL
SUHVNXãDOQLQL]$76LQGHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHL]YHGEH
SURWRNROD3,;,73URIRUPDVSHFLILNDFLMH]DJHQHULþQLSURWRNRO
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Data link layer; Part 7: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma specification for the
general protocol
Ta slovenski standard je istoveten z: ETS 300 402-7 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.100.20 Podatkovni povezovalni sloj Data link layer
SIST ETS 300 402-7:1999 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 402-7:1999

---------------------- Page: 2 ----------------------

SIST ETS 300 402-7:1999
EUROPEAN ETS 300 402-7
TELECOMMUNICATION September 1997
STANDARD
Source: SPS Reference: DE/SPS-05088
ICS: 33.020
Key words: ATS, D-channel, DSS1, ISDN, layer 2, LAPD, network, PIXIT, testing, user
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Data link layer;
Part 7: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the general protocol
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1997. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 402-7:1999
Page 2
ETS 300 402-7: September 1997
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 Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 402-7:1999
Page 3
ETS 300 402-7: September 1997
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).9
5 Untestable test purposes.9
6 ATS conventions .9
6.1 Declarations part.9
6.1.1 Type definitions .9
6.1.1.1 Simple type definitions.9
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.9
6.1.1.3.1 TTCN ASP type definitions .9
6.1.1.3.2 ASN.1 ASP type definitions .10
6.1.1.4 PDU type definitions .10
6.1.1.4.1 TTCN PDU type definitions.10
6.1.1.4.2 ASN.1 PDU type definitions .10
6.1.2 Test suite constants .10
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.11
6.2 Constraints part.11
6.2.1 Structured type constraint declaration.11
6.2.2 ASN.1 type constraint declaration .11
6.2.3 ASP type constraint declaration .12
6.2.3.1 ASN.1 ASP type constraint declaration .12
6.2.3.2 TTCN ASP type constraint declaration.12
6.2.4 PDU type constraint declaration.12
6.2.4.1 ASN.1 PDU type constraint declaration.12
6.2.4.2 TTCN PDU type constraint declaration .12
6.2.5 Derived constraints.12
6.2.6 Parameterized constraints.12
6.2.7 Value assignment.12
6.2.7.1 Specific values.12
6.2.7.2 Matching values.13
6.3 Dynamic part.13
6.3.1 Test cases.13
6.3.2 Test steps.13
6.3.3 Defaults .13
7 ATS to TP map.13
8 PCTR conformance.13

---------------------- Page: 5 ----------------------

SIST ETS 300 402-7:1999
Page 4
ETS 300 402-7: September 1997
9 PIXIT conformance. 14
10 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. 16
A.5 Static conformance review report . 17
A.6 Test campaign report. 17
A.7 Observations. 31
Annex B (normative): Partial PIXIT proforma . 32
B.1 Identification summary. 32
B.2 Abstract test suite summary . 32
B.3 Test laboratory. 32
B.4 Client (of the test laboratory) . 33
B.5 System Under Test (SUT) . 33
B.6 Protocol information. 34
B.6.1 Protocol identification . 34
B.6.2 Configuration to be tested .34
B.6.3 Configuration options . 34
B.6.4 Test management timers . 35
B.6.5 Sending of messages by IUT . 35
B.6.6 Parameter values . 35
Annex C (normative): Abstract Test Suite (ATS). 36
C.1 The TTCN Graphical form (TTCN.GR) .36
C.2 The TTCN Machine Processable form (TTCN.MP) . 36
Annex D (informative): General structure of ATS. 37
History. 38

---------------------- Page: 6 ----------------------

SIST ETS 300 402-7:1999
Page 5
ETS 300 402-7: September 1997
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 7 of a multi-part standard covering the Integrated Services Digital Network (ISDN) Digital
Subscriber Signalling System No. one (DSS1) data link layer specification as described below:
Part 1: "General aspects [ITU-T Recommendation Q.920 (1993), modified]";
Part 2: "General protocol specification [ITU-T Recommendation Q.921 (1993), modified]";
Part 3: "Frame relay protocol specification";
Part 4: "Protocol Implementation Conformance Statement (PICS) proforma specification for the
general protocol";
Part 5: "PICS proforma specification for the frame relay protocol";
Part 6: "Test Suite Structure and Test Purposes (TSS&TP) specification for the general protocol";
Part 7: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the general protocol".
Transposition dates
Date of adoption: 5 September 1997
Date of latest announcement of this ETS (doa): 31 December 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1998
Date of withdrawal of any conflicting National Standard (dow): 30 June 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 402-7:1999
Page 6
ETS 300 402-7: September 1997
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 402-7:1999
Page 7
ETS 300 402-7: September 1997
1 Scope
This seventh part of ETS 300 402 specifies the Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma for the user-network interface data link
layer at the T reference point or coincident S and T reference point (as defined in ITU-T Recommendation
I.411 [9]) of implementations conforming to the standard for the general data link layer protocol for the
pan-European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber Signalling
System No. one (DSS1) protocol, ETS 300 402-2 [1].
ETS 300 402-6 [3] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS
and partial PIXIT proforma specification.
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 402-2: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Data link layer; Part 1: General
protocol specification [ITU-T Recommendation Q.921 (1993), modified]".
[2] ETS 300 402-4: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Data link layer; Part 4: Protocol
Implementation Conformance statement (PICS) proforma specification for the
general protocol".
[3] ETS 300 402-6: "Integrated Services Digital Network (ISDN); Digital Subscriber
Signalling System No. one (DSS1) protocol; Data link layer; Part 6: Test Suite
Structure and Test Purposes (TSS&TP) specification for the general protocol".
[4] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[5] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[6] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[7] ISO/IEC 9646-4: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[8] ISO/IEC 9646-5: "Information Technology - OSI 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 -
Reference configurations".
[10] CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1)".

---------------------- Page: 9 ----------------------

SIST ETS 300 402-7:1999
Page 8
ETS 300 402-7: September 1997
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [4].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [4].
Lower Tester (LT): See ISO/IEC 9646-1 [4].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [4].
Protocol Conformance Test Report (PCTR): 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].
Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [4].
PIXIT proforma: See ISO/IEC 9646-1 [4].
System Under Test (SUT): See ISO/IEC 9646-1 [4].
Upper Tester (UT): See ISO/IEC 9646-1 [4].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
CES Connection Endpoint Suffix
CM Co-ordination Message
ExTS Executable Test Suite
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
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester

---------------------- Page: 10 ----------------------

SIST ETS 300 402-7:1999
Page 9
ETS 300 402-7: September 1997
4 Abstract Test Method (ATM)
The remote test method is applied for this ATS. The Point of Control and Observation (PCO) resides at
the service access point between layers 1 and 2. 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.
LT SUT
Layer 2 IUT
PCO
Layer 1 Layer 1
Service provider
Figure 1: Remote test method
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 this ETS.
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.
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.
6.1.1.2.2 ASN.1 structured type definitions
There are no ASN.1 structured type definitions in the ATS.
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.

---------------------- Page: 11 ----------------------

SIST ETS 300 402-7:1999
Page 10
ETS 300 402-7: September 1997
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used for
requesting or receiving service from the lower layer.
Table 1: TTCN ASP type definition PH_ACT_IN
TTCN ASP Type Definition
ASP NAME : PH_ACT_IN(PH_Activate_Indication)
PCO Type : PSAP
Comments :
Parameter Name           |   Parameter Type    |    Comments
Detailed Comments :
Table 2 shows an example of a parameterized ASP, PH_DATA_RQ, which is an ASP to be sent and
contains a PDU and a Priority Indicator.
Table 2: TTCN ASP type definition PH_DATA_RQ
TTCN ASP Type Definition
ASP NAME : PH_DATA_RQ(PH_DATA_Request)
PCO Type : PSAP
Comments :
Parameter Name           |   Parameter Type    |    Comments
PI (Priority Indicator)      |INTEGER          |
MU (MessageUnit)          |PDU            |Data Link Layer peer to peer
                  |             |message
Detailed Comments :
Table 3 shows an example of a parameterized ASP, PH_DATA_IN, which is an ASP to be received and
contains a PDU and no Priority Indicator.
Table 3: TTCN ASP type definition PH_DATA_IN
TTCN ASP Type Definition
ASP NAME : PH_DATA_IN(PH_DATA_Indication)
PCO Type : PSAP
Comments :
Parameter Name           |   Parameter Type    |    Comments
MU (MessageUnit)          |PDU            |Data Link Layer peer to peer
                  |             |message
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
Each test suite constant is defined in terms of a predefined type or a referenced type. The values given in
the value column will remain unchanged throughout the test suite.

---------------------- Page: 12 ----------------------

SIST ETS 300 402-7:1999
Page 11
ETS 300 402-7: September 1997
6.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type.
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.
Where test case variables are used in constraints, they are passed as formal parameters.
6.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or a procedural
definition.
Table 4: Test suite operation definition using natural language
Test Suite Operation Definition
Operation Name : RANDOM (low:INTEGER; high:INTEGER)
Result Type  : INTEGER
Comments    :
Description
The return value represents a random value between "low" and "high" values.
This operation is useful to provide the RI value during TEI management.
Detailed comments :
Table 5: Test suite operation definition using a procedural definition
Test Suite Operation Definition
Operation Name : CR_CMD (S_R, IUT_TYPE:BOOLEAN)
Result Type  : BITSTRING
Comments    : Calculate the C/R bitstring for a command frame according to the given
         condition (send or receive, user or network).
Description
/* S_R: parameter to indicate if the send is to be sent or received. */
/* S_R = 1 -> send, */
/* S_R = 0 -> receive. */
IF IUT_TYPE THEN   /* IUT has the user role \*/
  IF S_R THEN   /* frame to be sent \*/
    RETURNVALUE '1'B
  ELSE       /* frame to be received \*/
    RETURNVALUE '0'B
  ENDIF
ELSE        /* IUT has the network role *
  IF S_R THEN   /* frame to be sent \*/
    RETURNVALUE '0'B
  ELSE       /* frame to be received \*/
    RETURNVALUE '1'B
  ENDIF
ENDIF
Detailed comments :
6.2 Constraints part
6.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraints.
6.2.2 ASN.1 type constraint declaration
There are no ASN.1 type constraint declarations in the ATS.

---------------------- Page: 13 ----------------------

SIST ETS 300 402-7:1999
Page 12
ETS 300 402-7: September 1997
6.2.3 ASP type constraint declaration
6.2.3.1 ASN.1 ASP type constraint declaration
There are no ASN.1 ASP type constraint declarations in the ATS.
6.2.3.2 TTCN ASP type constraint declaration
The PDUs to be sent or received are passed to the TTCN ASP constraint declarations Ms and Mr as
parameters of meta type PDU. Only if values inside a specific PDU have to be referenced, the use of the
meta type PDU is not allowed according to ISO/IEC 9646-3 [6]. In such cases, different TTCN ASP
constraint declarations are used which are defined to carry only a specific type of PDU (e.g. SETUP).
Tables 6 and 7 show examples of such TTCN ASP constraint declarations.
Table 6: TTCN ASP constraint declaration Fs
TTCN ASP Constraint Declaration
Constraint Name : Fs(PAR:PDU)
ASP Type    : PH_DATA_RQ
Derivation Path :
Comments    : This constraint is used to send PDUs.
Parameter Name           |   Parameter Value    |    Comments
PI                 |1             |High priority value for SAPI 0
MU                 |PAR            |
Detailed Comments :
Table 7: TTCN ASP constraint declaration Fr
TTCN ASP Constraint Declaration
Constraint Name : Fr(PAR:PDU)
ASP Type    : PH_DATA_IN
Derivation Path :
Comments    : This constraint is used to receive PDUs.
Parameter Name           |   Parameter Value    |    Comments
MU                 |PAR            |
Detailed Comments :
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
There are no ASN.1 PDU type constraint declarations in the 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 Derived constraints
Derived constraints are used in this ATS for some PDUs.
6.2.6 Parameterized constraints
Parameterized constraints are used in this ATS.
6.2.7 Value assignment
6.2.7.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.

---------------------- Page: 14 ----------------------

SIST ETS 300 402-7:1999
Page 13
ETS 300 402-7: September 1997
6.2.7.2 Matching values
As matching values the following mechanisms are used:
Instead of Value:
AnyOrOmit "*"
AnyValue "?"
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
6.3 Dynamic part
6.3.1 Test cases
Each test case contains the test purpose text from ETS 300 402-6 [3]. 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.
6.3.3 Defaults
Note the use of the RETURN statement which is defined in DAM1 of ISO/IEC 9646-3 [6]. 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 [8], to produce a PCTR conformant with the PCTR template given in annex B of
ISO/IEC 9646-5 [8].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when
requested by a client to produce a PCTR, is required to produce a PCTR conformant with the PCTR
proforma contained in annex A of this ETS.
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.

---------------------- Page: 15 ----------------------

SIST ETS 300 402-7:1999
Page 14
ETS 300 402-7: September 1997
9 PIXIT conformance
A test realizer, producing an Executable Test Suite (ExTS) for the ATS specification contained in annex C,
is required, as specified in ISO/IEC 9646-4 [7], 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 testin
...