ETSI EN 300 369-6 V1.4.2 (2000-01)

Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) 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

REN/SPS-05116-6

Digitalno omrežje z integriranimi storitvami (ISDN) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – Dopolnilna storitev: nedvoumna predaja klica (ECT) – 6. del: Abstraktni preskušalni niz (ATS) in dodatna informacija za preskušanje delne izvedbe protokola (PIXIT) – Proforma specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 03-Jan-2000
• Technical Committee: SPS 5 3 - Conformance Testing
• Current Stage: 12 - Completion
• Due Date: 31-Dec-1999
• Completion Date: 04-Jan-2000
• Ref Project: SIST EN 300 369-6 V1.4.2:2005 - Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) 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 EN 300 369-6 V1.4.2:2005
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±3URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66±'RSROQLOQDVWRULWHYQHGYRXPQDSUHGDMDNOLFD(&7±
GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQH
L]YHGEHSURWRNROD3,;,7±3URIRUPDVSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) 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: EN 300 369-6 Version 1.4.2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST EN 300 369-6 V1.4.2:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 300 369-6 V1.4.2:2005

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

SIST EN 300 369-6 V1.4.2:2005
ETSI EN 300 369-6 V1.4.2 (2000-01)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Explicit Call Transfer (ECT) 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
�

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

SIST EN 300 369-6 V1.4.2:2005
2 ETSI EN 300 369-6 V1.4.2 (2000-01)
Reference
REN/SPS-05116-6
Keywords
ATS, DSS1, ECT, ISDN, network, PIXIT,
supplementary service
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - 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
Internet
[e-mail]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [e-mail]
Important notice
This ETSI deliverable 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.
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

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

SIST EN 300 369-6 V1.4.2:2005
3 ETSI EN 300 369-6 V1.4.2 (2000-01)
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) .7
4.1 Description of ATM used.7
4.2 Served user test cases .8
4.3 Remote user test cases .8
5 Untestable test purposes.8
6 ATS conventions.9
6.1 Version of TTCN used .9
6.2 Use of ASN.1 .9
6.2.1 Situations where ASN.1 is used .9
6.2.2 Specification of encoding rules.9
6.3 Conventions for variables and parameters.10
7 ATS to TP map.11
8 PCTR conformance.11
9 PIXIT conformance.11
10 ATS conformance .11
11 Configurations required in testing.12
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma.13
A.1 Identification summary .13
A.1.1 Protocol conformance test report.13
A.1.2 IUT identification.13
A.1.3 Testing environment.13
A.1.4 Limits and reservations.14
A.1.5 Comments.14
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
4 ETSI EN 300 369-6 V1.4.2 (2000-01)
A.2 IUT conformance status .14
A.3 Static conformance summary.14
A.4 Dynamic conformance summary.14
A.5 Static conformance review report .15
A.6 Test campaign report.15
A.7 Observations.18
Annex B (normative): Partial PIXIT proforma.19
B.1 Identification summary .19
B.2 Abstract test suite summary .19
B.3 Test laboratory .19
B.4 Client (of the test laboratory).20
B.5 System Under Test (SUT).20
B.6 Protocol information .21
B.6.1 Protocol identification .21
B.6.2 IUT information .21
B.6.2.1 Parameter values.21
B.6.2.2 Configuration of IUT .22
B.6.2.3 Timer values .22
B.7 Basic call PIXIT items .23
B.7.1 Parameter values - information element codings.23
Annex C (normative): Abstract Test Suite (ATS).24
C.1 The TTCN Graphical form (TTCN.GR).24
C.2 The TTCN Machine Processable form (TTCN.MP) .24
Bibliography.25
History.26
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
5 ETSI EN 300 369-6 V1.4.2 (2000-01)
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)
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocol and Switching (SPS).
The present document 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) Explicit Call Transfer (ECT)
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: "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: 17 December 1999
Date of latest announcement of this EN (doa): 31 March 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 2000
Date of withdrawal of any conflicting National Standard (dow): 30 September 2000
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
6 ETSI EN 300 369-6 V1.4.2 (2000-01)
1 Scope
The present document 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 of
implementations conforming to the stage three standard for the Explicit Call Transfer (ECT) 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 369-1 [1].
EN 300 369-5 [3] 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 EN 300 369-1 [1].
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] EN 300 369-1 (V1.2): "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:
Protocol specification".
[2] EN 300 369-2 (V1.2): "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2:
Protocol Implementation Conformance Statement (PICS) proforma specification".
[3] EN 300 369-5 (V1.2): "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test
Suite Structure and Test Purposes (TSS&TP) specification for the network".
[4] 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".
[5] TR 101 101 (V1.1): "Methods for Testing and Specification (MTS); TTCN interim version
including ASN.1 1994 support [ISO/IEC 9646-3] (Second Edition Mock-up for JTC1/SC21
Review)".
[6] ISO/IEC 9646: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework" (all parts).
[7] ISO/IEC 8825-1 (1994): "Information technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)" (see also ITU-T Recommendation X.690: 1994).
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
7 ETSI EN 300 369-6 V1.4.2 (2000-01)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [6] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
CM Co-ordination Message
ECT Explicit Call Transfer
ETS Executable Test Suite
IUT Implementation Under Test
MOT Means Of Testing
MTC Main Test Component
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
TP Test Purpose
TTCN Tree and Tabular Combined Notation
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.
In practice the behaviour at a single user-network interface does not occur in isolation, but depends on the activity at
other user-network interfaces. Therefore a multi-party test method is used.
The general configuration used is shown in figure 1. In this ATS the PTCs act as slaves to the MTC; all active behaviour
at the PTCs is initiated by CMs sent by the MTC and all verdicts are assigned by the MTC (using information sent in
CMs by the PTCs where appropriate). Not all components are used in every test case and the relationship between the
IUT and the tester depends on the test group.
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
8 ETSI EN 300 369-6 V1.4.2 (2000-01)
MTC PTC3
CPA3
PTC2
CPA2
PTC1
CPA1
PCO PCO PCO PCO
L0 L1 L2 L3
Interface to Interface to Interface to Interface to
Served User Remote User 1 Remote User 2 Remote User 3
Network
Figure 1: Multi-party test method
4.2 Served user test cases
For these test cases the IUT is connected to the MTC. Depending on the test case zero to three PTCs are used. The
verdict depends only on the behaviour observed at the PCO between the IUT and the MTC. The PTC(s) are used only to
provoke the IUT to send messages to the MTC or to handle behaviour at the remote user interface(s) as a result of
activity at the IUT interface.
In general the correlation of messages between the served and remote user interfaces (which is part of the functionality
of the supplementary service rather than the protocol) is not tested. If a message is expected at the MTC as a result of an
action at a remote user and is not received this usually leads to an inconclusive verdict.
PTC3 is only used in certain test cases for the explicit linkage procedures.
4.3 Remote user test cases
For these test cases the IUT is the protocol entity connected to either PTC1 or PTC2. The verdict is assigned by the
MTC on the basis of behaviour reported in a CM by the PTC connected to the IUT and the behaviour of the served user
attached to the MTC. A consequence of this is that incorrect behaviour by the served user can lead to a Fail verdict.
PTC3 is never used in the remote user test cases.
5 Untestable test purposes
There are no untestable test cases (see EN 300 369-5 [3]) associated with this ATS and ATM.
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
9 ETSI EN 300 369-6 V1.4.2 (2000-01)
6 ATS conventions
6.1 Version of TTCN used
The version of TTCN used is that defined in TR 101 101 [5].
6.2 Use of ASN.1
6.2.1 Situations where ASN.1 is used
ASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that "pure" TTCN
cannot. For instance, data structures modelling ordered or unordered sequences of data are preferably defined in ASN.1.
Second, ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions. Third, it is
necessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the base
standards in ASN.1.
The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.
6.2.2 Specification of encoding rules
There is a variation in the encoding rules applied to ASN.1 types and constraints specified in this ATS and therefore a
mechanism is needed to differentiate the encoding rules. However the mechanism specified in ISO/IEC 9646-3/AM2 [6]
and in TR 101 101 [5] does not facilitate definition of the encoding rules as needed for this ATS. A solution is therefore
used which is broadly in the spirit of ISO/IEC 9646-3/AM2 [6] in which comment fields have been used as a means of
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 ISO/IEC 8825-1 [7]. 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 (ETS) 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 shall
not be applied to an ASN.1 constraint where BER encoding has not been specified. This encoding rule is sometimes
named "Direct Encoding".
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 [4], 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 [4] gives guidelines but makes no restrictions on the length forms within
BER which an IUT may apply.
In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
10 ETSI EN 300 369-6 V1.4.2 (2000-01)
Table 1a: 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.3 Conventions for variables and parameters
Table 1b
MTCA
call reference CREF1
B channel (basic) bch_num1 (to PTC1)
channel nr (primary) CH_NUM1
call reference CREF2
B channel (basic) bch_num2 (to PTC2)
channel nr (primary) CH_NUM2
call reference CREF3
B channel (basic) bch_num3 (to PTC3)
channel nr (primary) CH_NUM3
PCO L0 IPN0, LIPN0
PTC1
call reference P1CREF
B channel (basic) P1_bch_num
channel nr (primary) P1_CH_NUM
PCO L1 IPN1, LIPN1
PTC2
call reference P2CREF
B channel (basic) P2_bch_num
channel nr (primary) P2_CH_NUM
PCO L2 IPN2, LIPN2
PTC3
call reference P3CREF
B channel (basic) P3_bch_num
channel nr (primary) P3_CH_NUM
PCO L3 IPN3, LIPN3
NOTE: In most TCs the calls identified by CREF1, CREF2 and CREF3
correspond to those identified by CR1, CR2 and CR3 respectively in the
TP. In a small number of TCs CREF1 refers to CR2 and CREF2 refers
to CR1.
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
11 ETSI EN 300 369-6 V1.4.2 (2000-01)
7 ATS to TP map
The identifiers used for the TPs (see EN 300 369-5 [3]) 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 [6], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [6].
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.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
9 PIXIT conformance
A test realizer, producing an executable test suite for the ATS specification contained in annex C, is required, as
specified in ISO/IEC 9646-4 [6], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT
proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum,
have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may contain
additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular IUT.
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [6], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma
conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents
which are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be
answered in order to prepare the test laboratory for a particular IUT.
10 ATS conformance
The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of
ISO/IEC 9646-4 [6]. In particular, these concern the realization of an ETS based on each ATS. The test realizer shall
provide a statement of conformance of the MOT to this ATS specification.
An ETS which conforms to this ATS specification shall contain test groups and test cases which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall
be capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each
test case.
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [6].
A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.
ETSI

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

SIST EN 300 369-6 V1.4.2:2005
12 ETSI EN 300 369-6 V1.4.2 (2000-01)
11 Configurations required in testing
For some test cases it is necessary to configure the SUT in specific ways, this is described in table 2 below. In this table
L0, L1 and L2 refer to the network interfaces connected to PCOs L0, L1 and L2 respectively. Except where specified
otherwise the following configurations apply:
- for S/T reference point test cases (Groups ECT_N01, ECT_N02 and ECT_N03):
- L0 configured as S/T reference point;
- L1 and L2 configured as S/T reference point for remote user tests (group ECT_N03);
- ECT subscribed at L0 as served user;
- HOLDsubscribedatL0asserveduser;and
- L1 and L2 supporting ECT and HOLD as remote users.
- for T reference point test cases (Groups ECT_N04, ECT_N05 and ECT_N06):
- L0 configured as T reference point;
- L1 and L2 configured as T reference point for remote user tests (group ECT_N06);
- ECT subscribed at L0 as served user; and
- L1 and L2 supporting ECT as remote users.
Table 2: SUT configurations for specific test cases
Test case Special configuration PIXIT
reference
ECT_N01_004 - 006 L0 shall not be subscribed to the ECT service. 2.1
ECT_N02_025 - 030
ECT_N05_013 - 015
ECT_N01_007 - 009 It shall not be possible to transfer the calls L0-L1 and L0-L1 2.2
ECT_N02_031 - 036 because of a looping condition.
ECT_N05_016 - 018
ECT_N01_049 - 051 It shall not be possible to transfer the calls L0-L1 and L0-L1 2.3
ECT_N02_065 - 070 because of supplementary service interactions.
ECT_N05_039 - 041
ECT_N02_013 - 018 It shall not be possible to assign a LinkID for the call L0-L2. 2.4
ECT_N05_007 - 009
ECT_N
...