ETSI TS 186 005-3 V1.1.1 (2008-09)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification

DTS/TISPAN-06019-3-NGN-R1

General Information

• Status: Published
• Publication Date: 04-Sep-2008
• Technical Committee: TISPAN 6 - TISPAN Testing
• Current Stage: 12 - Completion
• Due Date: 08-Aug-2008
• Completion Date: 05-Sep-2008

Standards Content (Sample)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Terminating Identification Presentation (TIP) and
Terminating Identification Restriction (TIR);
Part 3: Abstract Test Suite (ATS) and partial
Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification
�
2 ETSI TS 186 005-3 V1.1.1 (2008-09)

Reference
DTS/TISPAN-06019-3-NGN-R1
Keywords
ATS, SIP, ISUP, testing, TTCN, PIXIT, TIP, TIR
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 2008.
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.
ETSI
3 ETSI TS 186 005-3 V1.1.1 (2008-09)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
2.1 Normative references.6
2.2 Informative references.7
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.10
4.3 Test architecture.10
4.3.1 Interconnection of TS and SUT .10
4.3.2 Test system architecture.11
4.3.2.1 General.11
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.18
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 .19
5.3 ATS specification framework.20
5.3.1 ATS Library.20
5.3.2 Use of TTCN-3.21
5.3.2.1 General.21
5.3.2.2 TTCN-3 naming conventions.22
5.4 ATS archive.23
Annex A (normative): Partial PIXIT proforma .24
A.1 Introduction.24
A.2 PIXIT items.24
A.2.1 SIP-related PIXIT.24
A.2.2 ISUP/BICC-related PIXIT.27
Annex B (informative): TTCN-3 library modules.31
B.1 Electronic annex, zip file with TTCN-3 code .31
Annex C (informative): Bibliography.32
History .33

ETSI
4 ETSI TS 186 005-3 V1.1.1 (2008-09)
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 3 of a multi-part deliverable covering Terminating Identification Presentation (TIP) and
Terminating Identification Restriction (TIR), as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification".
ETSI
5 ETSI TS 186 005-3 V1.1.1 (2008-09)
1 Scope
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma based on the Test suite Structure and Test purposes defined in TS 186 005-2 [22].
The TSS&TP have been developed to test the Terminating Identification Presentation (TIP) and Terminating
Identification Restriction (TIR) PSTN/ISDN simulation services.
The test notation used in the ATS is TTCN-3 (ES 201 873-1 [5]).
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.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
ETSI
6 ETSI TS 186 005-3 V1.1.1 (2008-09)
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 186 002-4: "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 4: Abstract Test
Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) for
Profile A and B".
[2] 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]".
[3] 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".
[4] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol
Testing (IPT); IPv6 Testing: Methodology and Framework".
[5] 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".
[6] 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)".
[7] 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)".
[8] ISO/IEC 9646-1 (1992): "Information Technology - Open Systems Interconnection - Conformance
Testing Methodology and Framework - Part 1: General concepts".
[9] ISO/IEC 9646-7 (1994): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 7: Implementation Conformance Statements".
[10] ITU-T Recommendation Q.1912.5 (2004): "Interworking between Session Initiation Protocol
(SIP) and Bearer Independent Call Control protocol or ISDN User Part".
[11] ITU-T Recommendation Q.2150.1 (2001): "Signalling Transport Converter on MTP3 and
MTP3b".
[12] ITU-T Recommendation E.164 (2005): "The international public telecommunication numbering
plan".
[13] ITU-T Recommendation Q.761 (2000): "Signalling System No. 7 - ISDN User Part functional
description".
[14] ITU-T Recommendation Q.762 (2000): "Signalling System No. 7 - ISDN User Part general
functions of messages and signals".
[15] ITU-T Recommendation Q.763 (2000): "Signalling System No. 7 - ISDN User Part formats and
codes".
[16] ITU-T Recommendation Q.764 (2000): "Signalling System No. 7 - ISDN User Part signalling
procedures".
[17] ITU-T Recommendation Q.9: "Vocabulary of switching and signalling terms".
[18] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol".
[19] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax".
ETSI
7 ETSI TS 186 005-3 V1.1.1 (2008-09)
[20] IETF RFC 2617 (1999): "HTTP Authentication: Basic and Digest Access Authentication".
[21] IETF RFC 2806 (2000): "URLs for Telephone Calls".
[22] ETSI TS 186 005-2: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating
Identification Restriction (TIR); Part 2: Test Suite Structure and Test Purposes (TSS&TP)".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions from the following list of documents apply:
- terms defined in SIP/ISUP interworking reference specification [2],
- terms defined in ISDN User Part (ISUP) reference specification [13] to [16],
- terms defined in ISO/IEC 9646-1 [8] and ISO/IEC 9646-7 [9], and
- terms defined in ES 201 873-1 [5] (TTCN-3).
In particular, the following terms 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
address identity: See ITU-T Recommendation E.164 [12] or/and RFC 2806 [21].
call: See ITU-T Recommendation Q.9 [17], definition 2201.
call state: state as defined in clause 2.1 of the present document, for either the user side or network side as appropriate
NOTE: A call state may exist for each call reference value (and at the network side for each additional responding
CEI in the incoming call states).
identity information: includes all the information (RFC 2806 [21]/RFC 2396 [19]/ITU-T Recommendation
E.164 [12]) identifying a user, including trusted (network generated) and/or untrusted (user generated) addresses
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 [12]
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
ETSI
8 ETSI TS 186 005-3 V1.1.1 (2008-09)
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
supplementary service: service that modifies or supplements a basic Telecommunication service
System Under Test (SUT): real open system in which the IUT resides
trusted identity: network generated user address information
untrusted identity: user generated user address information
voice session: existing voice connection between two terminal equipments
EXAMPLE: Via RTP.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in table 2/Q.762 of ITU-T Recommendation
Q.762 [14] (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).
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
CN Core Network
CS Circuit Switched
DSS1 Digital Subscriber System No. 1
FCI Forward Call Indicators
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
IETF Internet Engineering Task Force
IM IP Multimedia
IP Internet Protocol
ISDN Integrated Services Digital Network
ISUP ISDN User Part
IUT Implementation Under Test
IWU Interworking Unit
LLC Low Layer Compatibility
LT Lower Tester
MOT Means Of Testing
ETSI
9 ETSI TS 186 005-3 V1.1.1 (2008-09)
MTC Main Test Component
MTP Message Transfer Part
NCI Nature of Connection Indicators
NGN Next Generation Network
NNI Network-network interface
PCO Point of Control and Observation
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PSTN Public Switch Telephone Network
PTC Parallel Test Component
SDP Session Description Protocol
SIP Session Initiation Protocol
SN Signalling Node
STC Signalling Transport Converter
NOTE According to ITU-T Recommendation Q.2150.1 [11].
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
TMR Transmission Medium Requirement
TP Test Purpose
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
UE User Equipment
4 Abstract Test Method (ATM)
4.1 Network architecture
Two different network configurations have been assumed in the scope of the test purpose description defined in
TS 186 005-2 [22], SIP-SIP and SIP-ISUP. The test purposes from the latter configuration are also covered in
TS 186 002-4 [1]; they have been adopted and integrated to the present document and its related TTCN-3 test code
specification.
Figures 1 and 2 show the network architecture for SIP-SIP and SIP-ISUP configuration.
Figure 1 shows the network architecture for SIP-SIP UE Interworking.

SIP SIP
<-----------------------------------------> IMS <------------------------------------------>

Figure 1: Interworking between two SIP UEs
Figure 2 shows the network architecture for SIP-ISUP Interworking.
ETSI
10 ETSI TS 186 005-3 V1.1.1 (2008-09)

SIP ISUP
<-----------------------------------------> IMS/IWU <------------------------------------------>

Figure 2: Interworking between SIP and ISUP
4.2 Protocol architecture
Figures 1 and 2 show that there are two configurations of the SUT (representing the SUT in the testing environment
described in the present document): a SIP UE interface and either a second SIP UE or an ISUP interface 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).
Figure 3 shows the protocol architecture regarding the two interfaces.
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 and ISUP interfaces
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.
ETSI
11 ETSI TS 186 005-3 V1.1.1 (2008-09)

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.
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 [6].
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 [6], whereas the specification and implementation of the TCI is in ES 201 873-6 [7].
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.
ETSI
12 ETSI TS 186 005-3 V1.1.1 (2008-09)
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 [3].
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.
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.
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 takes from the ASP, depending on the value of parameter 'isupBiccSelection', either the ordered combination of
'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), puts it in front of
encoded parameter 'iSUP_BICC_MSG', and sends the so constructed message at the ISUP or BICC interface
respectively.
ETSI
13 ETSI TS 186 005-3 V1.1.1 (2008-09)
Table 3: ISUP_BICC_MSG_ind ASP structure
ASP Name: ISUP_BICC_MSG_ind
Port: sysPort
Direction: SA->TE
Description: ASP used to receive 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 TE only if
ISUP has been selected in 'isupBiccSelection'.
routingLabel RoutingLabel The contents of this ASP parameter is evaluated in TE only if
ISUP has been selected in 'isupBiccSelection'.
circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is evaluated in TE only if
ISUP has been selected in 'isupBiccSelection'.
callInstanceCode CallInstanceCode The contents of this ASP parameter is evaluated in TE 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 receive matching.
Comments:
The SA takes from the received message, depending on the value of parameter 'isupBiccSelection', either the ordered
combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), and
puts it into the associated ASP parameters. The complementary ASP parameters 'callInstanceCode' (ISUP) and
combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (BICC) are filled by the SA with '0'-bits
according to the lengths of their types.
The TE does not evaluate the contents of the complementary parameters (but needs the correct lengths to identify the
start of 'iSUP_BICC_MSG').
The received message (body) is put by the SA into parameter 'iSUP_BICC_MSG' and is matched in the ATS with an
according receive template.
ETSI
14 ETSI TS 186 005-3 V1.1.1 (2008-09)
Table 4: InitializeIsupBicc_req ASP structure
ASP Name: InitializeIsupBicc_req
Port: IsupBiccPort
Direction: TE->SA
Description: Initialize ISUP/BICC part of the test system.
Parameter Type Description
isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing.
'00000000'B means 'ISUP' and any other value means 'BICC'.
ts_pointCode Bit14 Signalling point code of the TS (ISUP).
sut_pointCode Bit14 Signalling point code of the SUT (ISUP).
ts_address_sip octetstring Address (e.g. IP) of the TS (SIP side). The use of this address
is to enable the TS to communicate with the SUT at the SIP
side to establish and maintain the lower layer connections.
ts_address_isup_bicc octetstring Address (e.g. IP) of the TS (ISUP/BICC side). The use of this
address is to enable the TS to communicate with the SUT at
the ISUP/BICC side to establish and maintain the lower layer
connections.
sut_address_isup_bicc octetstring Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this
address is to enable the TS to communicate with the SUT at
the ISUP/BICC side to establish and maintain the lower layer
connections.
Comments:
This ASP is used at the beginning of each test case to initiate the necessary initialization of the test system, particularly
the interfaces to the SUT.
If parameter isupBiccSelection indicates 'bicc', the values of parameters 'ts_pointCode' and 'sut_pointCode' shall
be ignored by the SA.
If parameter isupBiccSelection indicates 'isup', the values of parameters 'ts_address_isup_bicc' and
'sut_address_isup_bicc' may be ignored, if they are not necessary.
Among the initializing actions there shall be:
a) Verification that the ISUP/BICC link is operable between SUT and TS.
b) Verification that the TS is ready to send and receive SIP messages.
NOTE: It is a matter of TS implementation whether the TS, upon this request, sets up and initializes lower layer
connections, if these are not setup.
Other initialization actions may be TS-specific.

Table 5: InitializeIsupBicc_cnf ASP STRUCTURE
ASP Name: InitializeIsupBicc_cnf
Port: sysPort
Direction: LT->TTCN
Description: Answer whether all necessary ISUP/BICC test system initializations have been successfully
performed.
The result can be positive or negative.
The result will be positive only if the TS is able to send and receive messages at the
ISUP/BICC-interface of the SUT.
Parameter Type Description
result boolean Indicating success or non-success of the whole initialization.
Comments:
Table 6: BearerSetup_req ASP structure
ASP Name: BearerSetup_req
Port: IsupBiccPort
Direction: TE->SA
Description: For BICC: request TS to setup the bearer connection between TS and SUT.
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
Comments:
ETSI
15 ETSI TS 186 005-3 V1.1.1 (2008-09)
Table 7: BearerSetup_acc ASP structure
ASP Name: BearerSetup_acc
Port: IsupBiccPort
Direction: SA->TE
Description: For BICC: answer to BearerSetup_req.
The answer can be positive (bearer connection setup successful) or negative (bearer connection setup
failed).
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
result boolean The answer is positive when the bearer connection setup was
successful and negative when the bearer connection setup
failed.
Comments:
Table 8: BearerSetup_ind ASP structure
ASP Name: BearerSetup_ind
Port: IsupBiccPort
Direction: SA->TE
Description: For BICC: indication that the bearer has been setup.
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
Comments:
Table 9: BearerRelease_req ASP structure
ASP Name: BearerRelease_req
Port: bcPort
Direction: TE->SA
Description: For BICC: request to release the established bearer connection.
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
Comments:
Table 10: BearerRelease_cnf ASP structure
ASP Name: BearerRelease_cnf
Port: bcPort
Direction: SA->TE
Description: For BICC: confirmation that the requested bearer is released.
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
result boolean Indication of whether the bearer is successfully released.
Comments:
At release collision the result is still 'true'.

Table 11: BearerRelease_ind ASP structure
ASP Name: BearerRelease_ind
Port: bcPort
Direction: SA->TE
Description: For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued
before).
Parameter Type Description
cic CallInstanceCode Call Instance Code identifying the bearer connection.
Comments:
ETSI
16 ETSI TS 186 005-3 V1.1.1 (2008-09)
Table 12: s_IsupBicc_conversation ASP structure
ASP Name: s_IsupBicc_conversation
Port: operatorPort_IsupBicc
Direction: SA-<>TE
Description: Check that conversation is possible on the through-connected bearer.
Parameter Type Description
text charstring Request operator to check the conversation.
answer boolean Check result entered by the operator.
Comments:
This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter.

Table 13: s_IsupBicc_ringing ASP structure
ASP Name: s_IsupBicc_ringing
Port: operatorPort_IsupBicc
Direction: SA-<>TE
Description: Check that ringing occurs on the through-connected bearer.
Parameter Type Description
text charstring Request operator to check the ringing.
answer boolean Check result entered by the operator.
Comments:
This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter.

4.3.2.3.2 Sending and receiving SIP and ISUP/BICC messages
4.3.2.3.2.1 General
Before starting a test case, the SA shall be prepared to provide the transport of SIP and ISUP/BICC messages by
establishing appropriate connections on the lower layers (see figure 3).
4.3.2.3.2.2 Encoding/Decoding System requirements
4.3.2.3.2.2.1 Encoding/Decoding System requirements for SIP
The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, shall comply with the conventions
defined in clause 6.1 of TS 102 027-3 [3].
4.3.2.3.2.2.2 Encoding/Decoding System requirements for ISUP/BICC
4.3.2.3.2.2.2.1 General
ISUP/BICC messages are sent and received in the test suite by embedding them in ASPs ISUP_BICC_MSG_req and
ISUP_BICC_MSG_ind respectively.
The ASPs contain all information to route the ISUP/BICC messages to/from the SUT.
ISUP messages and parameters are structured by using tables (see ITU-T Recommendation Q.763 [15]).
NOTE: The term 'parameter' is used as defined in the ISUP protocol context. It corresponds e.g. to the term
'Information Element' in other protocols.
All structure elements are bitstrings, hexstrings or octetstrings.
For ISUP message/parameter elements a specific way is defined to extend bitstring or hexstring elements over octet
boundaries. This is known as 'LowToHigh encoding', as shown in the following example.
EXAMPLE 1: Coding of element 'Circuit Identity Code' (CIC), consisting of 12 bits.
ETSI
17 ETSI TS 186 005-3 V1.1.1 (2008-09)
Octet # Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1
Octet 1
CIC (LSB)
Octet 2 spare CIC (MSB)
Figure 6: Bit field structure of the 'CIC' parameter
The 8 least significant bits of the CIC value fill octet 1 (the least significant bit of CIC is assigned to bit 1 of octet 1),
and the 4 most significant bits of the CIC value fill the lower 4 bits of octet 2.
NOTE: When a bitstring (hexstring) is presented as a sequence of bits (semi-octets) from left to right, the leftmost
bit (semi-octet) is the most significant and the rightmost bit (semi-octet) is the least significant.
EXAMPLE 2: Address digits.
Several ISUP parameters have an element 'Address digits', where the individual digits are BCD-encoded (e.g. digit
'0' is encoded as '0000'B, digit '9' is encoded as '1001'B.
When an address string is given as a sequence of ASCII digits, as a user would type them in, e.g. "0123456789", the
encoded value is as shown on figure 7.
Octet # Bits 8 7 6 5 Bits 4 3 2 1
Octet 1 0001 0000
Octet 2 0011 0010
Octet 3 0101 0100
Octet 4 0111 0110
Octet 5 1001 1000
Figure 7: Hex (BCD) field structure of an 'address digits' element
This also corresponds to a 'LowToHigh' encoding. In this particular case however, for the sake of ATS user
convenience, a conversion function is used in the ATS in the following way:
• All module parameters containing address digits have type 'charstring' (resp. IA5String), which means that the
user enters digits as ASCII characters '1', '2' and so on.
• Inside the address parameter templates the conversion function converts the ASCII string into a BCD-coded
octetstring, taking also care of:
- 'sending complete' digit (only applicable to the Called Party Number);
- filler (final semi-octet, if the number of coded digits is odd).
The encoding of octetstrings however is not LowToHigh, as shown in the following example.
EXAMPLE 3: octetstring value.
The octetstring value '01234ABCDE'O is encoded as shown on figure 8.
Octet # Bits 8 7 6 5 Bits 4 3 2 1
Octet 1 0000 0001
Octet 2 0010 0011
Octet 3 0100 1010
Octet 4 1011 1100
Octet 5 1101 1110
Figure 8: Octetstring field encoding
4.3.2.3.2.2.2.2 Decoding of parameters containing strings of variable length
Typical fields addressed here are e.g. the 'address digits' field in the 'Called Party Number' parameter, or the
'diagnostics' field in the 'Cause Indicators' parameter.
The above mentioned strings of variable length are the last elements of the related parameter, which has a preceding
length field. A 'real' decoder deduces the length (and thereby the value) of such fields from the value of the 'length' field
of the parameter and the position of the decoder where the field starts.
ETSI
18 ETSI TS 186 005-3 V1.1.1 (2008-09)
The decoder of the test system shall also be able to decode such fields when the value of the template is '?' or '*'.
In order to support this encoding the relevant types have a trailing "with { encode ." statement, like in the following
example (Called Party Number):
EXAMPLE 4:
....
with { encode (paramLen) "tag=""CDN_paramLen"";";
encode (addressSignals) "length=valueOf(getTag(""CDN_paramLen"")).toInt()-2;"; }

End EXAMPLE 4
4.3.2.3.2.2.2.3 Decoding of parameters containing extension bits
Some parameters transport IEs from the DSS1 protocol (Q.931), such as the Bearer Capability IE:
• IEs of this kind contain extension bits specifying the presence of succeeding octets.
The decoder shall be able to evaluate the extension bits to deduce the presence of optional octets in case wildcards '?' or
'*' are specified in templates of such IEs.
4.3.2.3.2.2.2.4 Receipt of unknown ISUP/BICC messages
Unknown messages in this context are messages not defined in the dated version of [15] referred to in the present
document.
Unknown messages shall not be passed to TE by the test system.
4.3.2.3.2.2.2.5 Receipt of unknown ISUP/BICC parameters
Unknown parameters in this context are parameters not defined in the dated version of ITU-T Recommendation
Q.763 [15] referred to in the present document, or defined parameters not being assigned in ITU-T Recommendation
Q.763 [15] to the particular received message carrying this parameter.
Unknown parameters shall not be passed to TE by the test system (i.e. they shall be removed from the carrying known
message before passing this message to TE).
4.3.2.3.2.2.2.6
...