ETSI ETS 300 138-6 ed.1 (1997-05)

Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

DE/SPS-05061-H-6

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: zaprta skupina uporabnikov (CUG) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 6. del: Niz abstraktnih preskusov (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proformna specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 26-May-1997
• Technical Committee: SPS 5 - Digital access signalling
• Current Stage: 12 - Completion
• Due Date: 30-May-1997
• Completion Date: 27-May-1997
• Ref Project: SIST ETS 300 138-6:1997 - Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 138-6:1997
01-december-1997
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY]DSUWD
VNXSLQDXSRUDEQLNRY&8*3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW
'66GHO1L]DEVWUDNWQLKSUHVNXVRY$76LQGHOQDGRGDWQDLQIRUPDFLMD]D
SUHVNXãDQMHL]YHGEHSURWRNROD3,;,73URIRUPQDVSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary
service; Digital Subscriber Signalling System No. one (DSS1) protocol; 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: ETS 300 138-6 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 138-6:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 138-6:1997

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

SIST ETS 300 138-6:1997
EUROPEAN ETS 300 138-6
TELECOMMUNICATION May 1997
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-H-6
ICS: 33.020
Key words: ISDN, DSS1, supplementary service, CUG, testing, ATS, PIXIT, network
Integrated Services Digital Network (ISDN);
Closed User Group (CUG) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 6: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network
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: [e-mail]
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 1997. All rights reserved.

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

SIST ETS 300 138-6:1997
Page 2
ETS 300 138-6: May 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 138-6:1997
Page 3
ETS 300 138-6: May 1997
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Abstract Test Method (ATM).11
4.1 Description of ATM used .11
4.1.1 Conventions for test components and PCOs.11
4.1.2 Conventions for variables and parameters .12
4.2 Alternative ATM .13
5 Untestable test purposes.13
6 ATS conventions .14
6.1 Declarations part.14
6.1.1 Type definitions .14
6.1.1.1 Simple type definitions.14
6.1.1.2 Structured type definitions .14
6.1.1.2.1 TTCN structured type definitions .14
6.1.1.2.2 ASN.1 structured type definitions.14
6.1.1.3 ASP type definitions.15
6.1.1.3.1 TTCN ASP type definitions .15
6.1.1.3.2 ASN.1 ASP type definitions .16
6.1.1.4 PDU type definitions .16
6.1.1.4.1 TTCN PDU type definitions.16
6.1.1.4.2 ASN.1 PDU type definitions .16
6.1.2 Test suite constants .16
6.1.3 Test suite parameters .16
6.1.4 Variables .16
6.1.4.1 Test suite variables.16
6.1.4.2 Test case variables.16
6.1.5 Test suite operation definitions.17
6.2 Constraints part.17
6.2.1 Structured type constraint declaration.17
6.2.2 ASN.1 type constraint declaration .17
6.2.2.1 Specification of encoding rules.17
6.2.3 ASP type constraint declaration .17
6.2.3.1 ASN.1 ASP type constraint declaration .17
6.2.3.2 TTCN ASP type constraint declaration.18
6.2.4 PDU type constraint declaration.18
6.2.4.1 ASN.1 PDU type constraint declaration.18
6.2.4.2 TTCN PDU type constraint declaration .18
6.2.5 Chaining of constraints.18
6.2.5.1 Static chaining .18
6.2.5.2 Dynamic chaining .18
6.2.6 Derived constraints.18
6.2.7 Parameterized constraints.18
6.2.8 Value assignment.19
6.2.8.1 Specific values.19
6.2.8.2 Matching values.19

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

SIST ETS 300 138-6:1997
Page 4
ETS 300 138-6: May 1997
6.3 Dynamic part . 19
6.3.1 Test cases . 19
6.3.2 Test steps . 19
6.3.2.1 PTC1_IN . 19
6.3.2.2 PTC1_OUT . 19
6.3.3 Defaults. 19
7 ATS to TP map . 19
8 PCTR conformance. 20
9 PIXIT conformance. 20
10 ATS conformance. 20
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 21
A.1 Identification summary. 21
A.1.1 Protocol conformance test report. 21
A.1.2 IUT identification. 21
A.1.3 Testing environment. 21
A.1.4 Limits and reservations . 22
A.1.5 Comments. 22
A.2 IUT conformance status . 22
A.3 Static conformance summary. 22
A.4 Dynamic conformance summary. 22
A.5 Static conformance review report . 23
A.6 Test campaign report. 23
A.7 Observations. 25
Annex B (normative): Partial PIXIT proforma . 26
B.1 Identification summary. 26
B.2 Abstract test suite summary . 26
B.3 Test laboratory. 26
B.4 Client (of the test laboratory) . 27
B.5 System Under Test (SUT) . 27
B.6 Protocol information. 28
B.6.1 Protocol identification . 28
B.6.2 Parameter values . 28
B.6.3 Configuration of IUT . 30
B.6.4 Parameter values - information element codings. 30
B.6.5 Parameter values - information elements received from IUT . 30
B.6.6 CUG features . 30
B.6.7 Timer values. 31
B.7 Basic call PIXIT items. 31
B.7.1 Parameter values - information element codings. 31

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

SIST ETS 300 138-6:1997
Page 5
ETS 300 138-6: May 1997
Annex C (normative): Abstract Test Suite (ATS).32
C.1 The TTCN Graphical form (TTCN.GR) .32
C.2 The TTCN Machine Processable form (TTCN.MP) .32
Annex D (informative): General structure of ATS.33
History.34

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

SIST ETS 300 138-6:1997
Page 6
ETS 300 138-6: May 1997
Blank page

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

SIST ETS 300 138-6:1997
Page 7
ETS 300 138-6: May 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Closed User Group
(CUG) supplementary service, 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: "TSS&TP specification for the network";
Part 6: "ATS and partial PIXIT proforma specification for the network".
Transposition dates
Date of adoption: 23 May 1997
Date of latest announcement of this ETS (doa): 31 August 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 28 February 1998
Date of withdrawal of any conflicting National Standard (dow): 28 February 1998

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

SIST ETS 300 138-6:1997
Page 8
ETS 300 138-6: May 1997
Blank page

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

SIST ETS 300 138-6:1997
Page 9
ETS 300 138-6: May 1997
1 Scope
This sixth part of ETS 300 138 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma for the Network 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 Closed User Group (CUG) supplementary service for the pan-
European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber Signalling
System No. one (DSS1) protocol, ETS 300 138-1 [2].
ETS 300 138-5 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS
and partial PIXIT proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT
proforma for the User side of the T reference point or coincident S and T reference point of
implementations conforming to ETS 300 138-1 [2].
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 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[2] ETS 300 138-1 (1992): "Integrated Services Digital Network (ISDN); Closed
User Group (CUG) supplementary service; Digital Subscriber Signalling System
No. one (DSS1) protocol; Part 1: Protocol specification".
[3] ETS 300 138-2 (1995): "Integrated Services Digital Network (ISDN); Closed
User Group (CUG) supplementary service; Digital Subscriber Signalling System
No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification".
[4] ETS 300 138-5: "Integrated Services Digital Network (ISDN); Closed User
Group (CUG) supplementary service; Digital Subscriber Signalling System No.
one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP)
specification for the network".
[5] ETS 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 - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[7] ISO/IEC 9646-2: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[8] ISO/IEC 9646-3: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[9] ISO/IEC 9646-4: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[10] 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".
[11] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".

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

SIST ETS 300 138-6:1997
Page 10
ETS 300 138-6: May 1997
[12] CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1)".
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 [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].
Upper Tester (UT): See ISO/IEC 9646-1 [6].
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
CM Co-ordination Message
CP Co-ordination Point
CUG Closed User Group
ExTS Executable Test Suite
IA Incoming Access
ICB Incoming Calls Barred
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
MTC Main Test Component
OA Outgoing Access
OCB Outgoing Calls Barred
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
PTC Parallel Test Component
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UDI Unrestricted Digital Information
UT Upper Tester

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

SIST ETS 300 138-6:1997
Page 11
ETS 300 138-6: May 1997
4 Abstract Test Method (ATM)
4.1 Description of ATM used
The requirement for testing the network IUT is to focus on the behaviour of the network IUT at the user-
network interface where a T reference point or coincident S and T reference point applies. Thus the IUT is
the network DSS1 protocol entity at a particular user-network interface and is not the whole network.
It is possible to specify an ATS based on a Single party (remote) test method for such an IUT. However, it
is considered that an ATS based on such an approach is of limited use as the only way to specify IUT
generated PDUs is to use the "implicit send" statement. Many users of such an ATS would replace the
"implicit send" statements with descriptions of the behaviour at other interfaces.
An ATS based on a multi-party test method is considered to be more useful in that it is closer to how a
real test suite would be constructed. Such a test method specifies behaviour at multiple network
interfaces. One very important limitation here is that tests are focused on one particular interface. Thus
the test system is made up one Main Test Component (MTC) and one or more Parallel Test Components
(PTC), see figure 1.
4.1.1 Conventions for test components and PCOs
Master part Slave part
MTCA
PTC1
CPA1
L0 PCO L1 PCO
IUT
NETWORK
Figure 1: Multi-party test method
In a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves.
The "slave" testers are only an explicit description of how to deal with the "other" interfaces during the
testing process, i.e. "how to make the IUT send the required message".

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

SIST ETS 300 138-6:1997
Page 12
ETS 300 138-6: May 1997
This means, in particular, that the verdict will only be assigned from the protocol aspects observed on the
interface under test (i.e. by the "master" tester), as it would be observed by a terminal connected to this
interface. A failure in the correlation between the protocol at the different interfaces to which the different
testers are connected, i.e. in the mechanism of the functional service itself, will not cause a FAIL verdict.
For instance, if the IUT fails to send a message on the tested interface after another interface has
received the proper stimulus, the verdict will be INCONCLUSIVE.
The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling the
one or more PTCs. Thus it is responsible for starting the PTCs and afterwards co-ordinates activities by
exchanging Co-ordination Messages (CM) with the PTCs. Secondly it is responsible for the behaviour of
the Lower Tester (LT) at PCO L0.
A combination of the remote and multi-party test methods is applied. As can be seen from figure 1,
several PCOs are used. All PCOs reside at the service access points between layers 2 and 3.
MTC SUT PTC1
Layer 3 IUT Layer 3
 L0      L1 
Layer 2 Layer 2
 
        
Layer 1 Layer 1
Service provider
Figure 2: Combination of the remote and multi-party test methods
The MTC PCO is named "L0" ("L" for Lower). PCO L0 is used to control and observe the behaviour of the
IUT and test case verdicts are assigned depending on the behaviour observed at this PCO. The PTC
PTC1 uses PCO L1. This PCO is used to control and, in a limited way, observe the behaviour of the
network equipment at interfaces other than the one under test. No verdicts are assigned at this PCO.
As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are
stimulated by events at the L1, will result in INCONCLUSIVE rather than FAIL verdicts being assigned.
4.1.2 Conventions for variables and parameters
MTCA
call reference CREF1
B channel (basic) bch_num1 (to PTC1)
channel nr (primary) CH_NUM1
PCO L0 IPN0, LIPN0
PTC1
call reference P1CREF
B channel (basic) P1_bch_num
channel nr (primary) P1_CH_NUM
PCO L1 IPN1, LIPN1

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

SIST ETS 300 138-6:1997
Page 13
ETS 300 138-6: May 1997
4.2 Alternative ATM
As stated in subclause 4.1, an ATS based on a single-party (remote) ATM is possible. Such an ATS may
be generated from the one specified in this ETS. The following general steps should be taken:
1) remove all PTC behaviour;
2) remove all CREATE statements;
3) replace CMs which are used to provoke PDUs at the MTC, with implicit send statements.
An example, showing the difference between the multi-party ATM and single-party ATM for a single test
case, is given in tables 1 and 2.
Table 1: Test case dynamic behaviour table using multi-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration CONFIG1
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |CREATE ( PTC1: PTC1_IN_servedUser) | | |
2 | | +PR31002 | | |preamble N10
3 | | CPA1!CP_M START TWAIT |S_HL | |
4 | |  L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
5 | |  +CS59901(10,1) | | |check N10
6 | |  ?TIMEOUT TWAIT | |(I)|
7 | |  +PO49901(1) | | |postamble N0
DETAILED COMMENTS:
Table 2: Test case dynamic behaviour table using single-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |+PR31002 | | |preamble N10
2 | | |NO20(CREF1,hold_NID) | |
3 | | L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
4 | |  +CS59901(10,1) | | |check N10
5 | | ?TIMEOUT TWAIT | |(I)|
6 | |  +PO49901(1) | | |postamble N0
DETAILED COMMENTS:
5 Untestable test purposes
There are no untestable test cases associated with this ATS and ATM.

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

SIST ETS 300 138-6:1997
Page 14
ETS 300 138-6: May 1997
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.
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 two 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.
The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose of
achieving type-compatibility.
In table 3 the ASN.1 type BIT7OR15 is defined as being of type BIT STRING with a size constraint
attached to it. The size is determined by the value of CR_LENGTH, a test suite parameter. It can have the
value of either 7 or 15. The type BIT7OR15 is used in the struc
...