ETSI TS 186 002-5 V1.1.1 (2010-06)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN UserPart (ISUP); Part 5: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) for Profile C

RTS/TISPAN-06059-5-NGN-R1

General Information

• Status: Published
• Publication Date: 16-Jun-2010
• Technical Committee: TISPAN 6 - TISPAN Testing
• Current Stage: 12 - Completion
• Due Date: 18-Jun-2010
• Completion Date: 17-Jun-2010

Standards Content (Sample)

ETSI TS 186 002-5 V1.1.1 (2010-06)
Technical Specification

Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Interworking between Session Initiation Protocol (SIP)
and Bearer Independent Call Control Protocol (BICC) or
ISDN User Part (ISUP);
Part 5: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
for Profile C


�

---------------------- Page: 1 ----------------------
2 ETSI TS 186 002-5 V1.1.1 (2010-06)



Reference
RTS/TISPAN-06059-5-NGN-R1
Keywords
ATS, BICC, interworking, ISUP, PIXIT, SIP,
testing, TTCN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2010.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 186 002-5 V1.1.1 (2010-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Abstract Test Method (ATM) . 9
4.1 Network architecture . 9
4.2 Protocol architecture. 9
4.3 Test architecture . 10
4.3.1 Interconnection of TS and SUT . 10
4.3.2 Test system architecture . 10
4.3.2.1 General . 10
4.3.2.2 Structure . 11
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) . 12
4.3.2.3.1 Control of the SUT Adapter (SA) by using ASPs . 12
4.3.2.3.2 Sending and receiving SIP and ISUP/BICC messages . 16
4.3.2.3.3 Logging conventions . 19
5 The ATS development process . 19
5.1 Requirements and Test Purposes . 19
5.2 ATS structure . 19
5.2.1 Test case grouping . 19
5.2.2 Test case identifiers . 21
5.3 ATS specification framework . 22
5.3.1 ATS Library . 22
5.3.2 Use of TTCN-3 . 23
5.3.2.1 General . 23
5.3.2.2 TTCN-3 naming conventions . 24
5.4 ATS archive . 25
Annex A (normative): Partial PIXIT proforma . 26
A.1 Introduction . 26
A.2 PIXIT items . 26
A.2.1 SIP-related PIXIT . 26
A.2.2 ISUP/BICC-related PIXIT . 28
Annex B (informative): TTCN-3 library modules . 38
B.1 Electronic annex, zip file with TTCN-3 code . 38
Annex C (informative): Bibliography . 39
History . 41

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 186 002-5 V1.1.1 (2010-06)
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 ETSI 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://webapp.etsi.org/IPR/home.asp).
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 ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 5 of a multi-part deliverable covering the Interworking between Session Initiation
Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP) for Profile A and B";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) for Profile C";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for Profile A and B";
Part 5: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) for Profile C".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 186 002-5 V1.1.1 (2010-06)
1 Scope
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma based on the Testsuite Structure and Testpurposes defined in TS 186 002-3 [1].
The TSS&TP have been developed to test the interworking between Session Initiation Protocol (SIP) and Bearer
Independent Call Control Protocol (BICC) or ISDN User Part, Profiles C. The ATS is sometimes referred to in the
present document as 'SIP-ISUP-Interworking ATS'.
The test notation used in the ATS is TTCN-3 (ES 201 873-1 [8]).
The following test specification- and design considerations can be found in the body of the present document:
• the overall test suite structure;
• the testing architecture;
• the test methods and port definitions;
• the test configurations;
• the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator);
• TTCN styles and conventions;
• the partial PIXIT proforma;
• the modules containing the TTCN-3 ATS.
Annex A provides the Partial Implementation Extra Information for Testing (IXIT) Proforma of the ATS.
Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
NOTE: The current version of the document covers test purposes for SIP-I to ISUP and ISUP to SIP-I basic call
and supplementary services only. ATS and PIXIT for ISDN-(ISUP)-SIP-I interworking defined in
annex A of TS 186 002-3 [1] will be added in a later version of the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
NOTE: References have been used both in the present document and in the TTCN-3 library modules (annex B).
[1] ETSI TS 186 002-3: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 3: Test Suite
Structure and Test Purposes (TSS&TP) for Profile C".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 186 002-5 V1.1.1 (2010-06)
[2] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol
Testing (IPT); IPv6 Testing: Methodology and Framework".
[3] ETSI TS 186 002-1 (V1.1.1): "Telecommunications and Internet converged Services and Protocols
for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 1: Protocol
Implementation Conformance Statement (PICS)".
[4] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and
Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T
Recommendation Q.1912.5, modified]".
[5] ITU-T Recommendation .1912.5 (2004): "Interworking between Session Initiation Protocol (SIP)
and Bearer Independent Call Control protocol or ISDN User Part".
[6] ITU-T Recommendation Q.2150.1 (2001): "Signalling Transport Converter on MTP3 and
MTP3b".
[7] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test
Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma".
[8] ETSI ES 201 873-1 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 1: TTCN-3 Core Language".
[9] ETSI ES 201 873-5 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
[10] ETSI ES 201 873-6 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[11] ISO/IEC 9646-1 (1992): "Information Technology - Open Systems Interconnection - Conformance
Testing Methodology and Framework - Part 1: General concepts".
[12] ISO/IEC 9646-7 (1994): "Conformance testing methodology and framework -
Part 7: Implementation Conformance Statement".
[13] ITU-T Recommendation E.164 (2005): "The international public telecommunication numbering
plan".
[14] ITU-T Recommendation Q.761 (2000): "Specifications of Signalling System No.7 ISDN User Part
(ISUP); functional description".
[15] ITU-T Recommendation Q.762 (2000): "Specifications of Signalling System No.7 ISDN User Part
(ISUP); general functions of messages and signals".
[16] ITU-T Recommendation Q.763 (2000): "Specifications of Signalling System No.7 ISDN User Part
(ISUP); formats and codes".
[17] ITU-T Recommendation Q.764 (2000): "Specifications of Signalling System No.7 ISDN User Part
(ISUP); signalling procedures".
[18] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol".
[19] IETF RFC 2617 (1999): "HTTP Authentication: Basic and Digest Access Authentication".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 3398: "Integrated Services Digital Network (ISDN) User Part (ISUP) to Session
Initiation Protocol (SIP) Mapping".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 186 002-5 V1.1.1 (2010-06)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, definitions from the following list of documents apply:
• terms defined in SIP / ISUP interworking reference specification [5];
• terms defined in ISDN User Part (ISUP) reference specification [14] to [17];
• terms defined in ISO/IEC 9646-1 [11] and ISO/IEC 9646-7 [12]; and
• terms defined in ES 201 873-1 [8] (TTCN-3).
In particular, the following terms and definitions apply:
Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test
purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state and
ending in a stable testing state
Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to
make the description independent of any particular realization of a Means of Testing, but with enough detail to enable
abstract test cases to be specified for this method
Abstract Test Suite (ATS): test suite composed of abstract test cases
Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider
relationship, being part of a real open system which is to be studied by testing
SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [13]
Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection,
parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a
conformance log
PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes the PICS
PIXIT proforma: document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT
Point of Control and Observation: point within a testing environment where the occurrence of test events is to be
controlled and observed, as defined in an Abstract Test Method
pre-test condition: setting or state in the IUT which cannot be achieved by providing stimulus from the test
environment
Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to
conform to a given specification, stating which capabilities have been implemented
Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of
an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment,
which will enable the test laboratory to run an appropriate test suite against the IUT
System Under Test (SUT): real open system in which the IUT resides
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 186 002-5 V1.1.1 (2010-06)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations given in Table 2/Q.762 of ITU-T
Recommendation Q.762 [15] (ISUP messages) and the following apply:
NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules
(annex B).
ACM Address Complete Message
ANM Answer Message
ASP Abstract Service Primitive
NOTE: Exchanged between entities inside the TS or between the user of the ATS (operator) and the TS.
ATC Abstract Test Case
ATM Abstract Test Method
ATM Asynchronous Transfer Mode
ATS Abstract Test Suite
BCI Backward Call Indicators
CIC Circuit Identification Code
CON Connect message
CPG Call Progress message
CW Call Waiting
DSS1 Digital Subscriber System No. 1
EDS Encoding/Decoding System
ETS Executable Test Suite
FCI Forward Call Indicators
IAM Initial Address Message
IETF Internet Engineering Task Force
ISDN Integrated Services Digital Network
ISUP ISDN User Part
IUT Implementation Under Test
IWU Interworking Unit
LT Lower Tester
MOT Means Of Testing
MTP Message Transfer Part
NCI Nature of Connection Indicators
NGN Next Generation Network
PA Platform Adapter
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
REL Release message
SA SUT Adapter
SAM Subsequent Address Message
SDP Session Description Protocol
SIP Session Initiation Protocol
SN Signalling Node
STC Signalling Transport Converter
NOTE According to ITU-T Recommendation Q.2150.1 [6].
SUT System Under Test
TC Test Case
TCI TTCN-3 Control Interface
TCP Test Coordination Procedures
TD Test Description
TE Test Equipment
TISPAN ETSI technical body with responsibility for NGN standardization
TL Test Logging
TM Test Management
TMR Transmission Medium Requirement
TP Test Purpose
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 186 002-5 V1.1.1 (2010-06)
TRI TTCN-3 Runtime Interface
TS Test System
TSS Test Suite Structure
TSS&TP Test Suite Structure and Test Purposes
TTCN Tree and Tabular Combined Notation
TTCN-3 Testing and Test Control Notation edition 3
4 Abstract Test Method (ATM)
4.1 Network architecture
Figures 1 and 2 show the network architecture for SIP-ISUP/BICC Interworking Units.
Figure 1 shows the network architecture for SIP-ISUP Interworking.


SIP ISUP
<-----------------------------------------> IWU <------------------------------------------>




Figure 1: Interworking between SIP and ISUP
Figure 2 shows the network architecture for SIP-BICC Interworking.


SIP BICC
<------------------------------------------>
<-----------------------------------------> IWU
<------------------------------------------>
 ATM bearer control



Figure 2: Interworking between SIP and BICC
NOTE: There are 3 profiles defined for IWU: Profile A, Profile B and Profile C. Figures 3 to 7 in clause 4 of
TS 186 002-1 [3] shows the substructures of the IWU for Profiles C in terms of gateways and signalling
nodes. In the ATS the SUT (IWU) represents either a G/W Type 3 or 4.
4.2 Protocol architecture
Figures 1 and 2 above show that there are 2 interfaces of the IWU (representing the SUT in the testing environment
described in the present document):
• a SIP interface; and
• an ISUP- or BICC interface.
Since the ISUP and BICC protocols are very similar (the latter one being derived from ISUP), they are treated here as
one protocol.
NOTE: No signalling is used within the SIP-ISUP-Interworking ATS to control the ATM bearer in case of BICC
(ASPs are used).
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 186 002-5 V1.1.1 (2010-06)
Figure 3 shows the protocol architecture in 2 branches.
SUT



IUT IUT
SIP ISUP BICC

  STC STC
UDP TCP

  MTP 3 MTP 3b


IP MTP Layer 2 AAL


(LAN) G.703/G.704 ATM



Figure 3: Protocol architecture of the SIP-ISUP-Interworking ATS
4.3 Test architecture
4.3.1 Interconnection of TS and SUT
Figure 4 shows the interconnection of TS and SUT in terms of signalling message flows.



SIP ISUP/
SUT
BICC
<------------------------>
<------------------------> IWU
<------------------------>
  ATM bearer control
(only for BICC)



Test

System

Figure 4: Interconnection of TS and SUT
4.3.2 Test system architecture
4.3.2.1 General
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 186 002-5 V1.1.1 (2010-06)
4.3.2.2 Structure
An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 5 and also stated in
ES 201 873-5 [9].
Test Management (TM)
Test Control (TC) Test Logging (TL)

TCI



TTCN-3 Executable (TE)
TTCN-3 Runtime System (T3RTS)
  Executable Test Suite (ETS)
Encoding/Decoding System


TRI



SUT Adapter (SA) Platform Adapter (PA)


Figure 5: Abstract Test System Architecture
A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify
the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and
Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in
ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10].
The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is
shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a
TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the
TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone,
can be decomposed into Test Management (TM), SUT Adapter (SA), and Platform Adapter (PA) entities. In general,
these entities cover a TS user interface, test execution control, test event logging, communication of test data with the
SUT, and timer implementation.
The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol
architecture described in clause 4.2.
The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL)
entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [7].
The part of SA used for ISUP/BICC message transfer shall implement the TRI adaptation as well as the ISUP/BICC
transport protocol architecture described in clause 4.2. For BICC, in addition, the ATM bearer control shall be
implemented.
The Encoding/Decoding System (EDS) entity, as far as applied to ISUP/BICC messages, shall comply with the
conventions and requirements defined in the following clauses.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 186 002-5 V1.1.1 (2010-06)
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
4.3.2.3.1 Control of the SUT Adapter (SA) by using ASPs
Table 1 lists the ASPs used in the SIP-ISUP-Interworking ATS. Detailed descriptions of the ASPs together with their
parameters follow.
Table 1: List of ASPs
ASP Name Short description
InitializeIsupBicc_req Initialize ISUP/BICC part of the test system.
InitializeIsupBicc_cnf Answer whether all necessary ISUP/BICC test system
initializations have been successfully performed.
ISUP_BICC_MSG_req Used to send an ISUP/BICC message.
ISUP_BICC_MSG_ind Used to receive an ISUP/BICC message.
BearerSetup_req For BICC: request TS to setup the bearer connection between
TS and SUT.
BearerSetup_acc For BICC: answer to BearerSetup_req.
BearerSetup_ind For BICC: indication that the bearer has been setup.
BearerRelease_req For BICC: request to release established bearer connection.
BearerRelease_cnf For BICC: confirmation that the requested bearer is released.
BearerRelease_ind For BICC: indication that the bearer has been released (when
no BearerRelease_req has been issued before).
s_IsupBicc_conversation Check that conversation is possible on the bearer.
s_IsupBicc_ringing Check that ringing occurs.

Tables 2 to 13 contain the descriptions of the ASPs used in the present document, including the ASP parameters (if any)
and the types of values these may assume. No ASP parameter is optional.
Table 2: ISUP_BICC_MSG_req ASP structure
ASP Name: ISUP_BICC_MSG_req
Port: sysPort
Direction: TE -> SA
Description: ASP used to send an ISUP/BICC message.
Parameter Type Description
isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing.
'00000000'B means 'ISUP' and any other value means 'BICC'.
serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is evaluated in SA only if
ISUP has been selected in 'isupBiccSelection'.
routingLabel RoutingLabel The contents of this ASP parameter is evaluated in SA only if
ISUP has been selected in 'isupBiccSelection'.
circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is evaluated in SA only if
ISUP has been selected in 'isupBiccSelection'.
callInstanceCode CallInstanceCode The contents of this ASP parameter is evaluated in SA only if
BICC has been selected in 'isupBiccSelection'.
iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message
body types, where a message body starts with the 'message
type' field. This body is common for ISUP and BICC messages.
When using this ASP, a particular message(body) template is
selected from the union for transmission.
Comments:
The SA t
...