ETSI TS 186 011-2 V2.1.1 (2009-02)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
IMS NNI Interworking Test Specifications;
Part 2: Test Descriptions for IMS NNI Interworking

2 ETSI TS 186 011-2 V2.1.1 (2009-02)

Reference
RTS/TISPAN-06033-2-NGN-R1
Keywords
IMS, interworking, NNI, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 2009.
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
3 ETSI TS 186 011-2 V2.1.1 (2009-02)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
2.1 Normative references.7
2.2 Informative references.8
3 Abbreviations.9
4 IMS NNI Interoperability Test Specification.9
4.1 Introduction.9
4.2 Test Prerequisites.10
4.2.1 IP Version.10
4.2.2 Authentication and Security.10
4.2.3 Registration and Subscription.10
4.2.3.1 SIP Call Flow.10
4.2.3.1.1 Early IMS Registration and Subscription Call Flow .10
4.2.3.1.2 Full IMS Registration and Subscription Call Flow .11
4.2.3.1.3 SIP Digest Registration and Subscription Call Flow.12
4.2.4 Supported Options .12
4.2.4.1 Security.12
4.2.4.2 Signalling Compression.12
4.3 Test Infrastructure.12
4.3.1 Core IMS Nodes .12
4.3.1.1 P-CSCF.13
4.3.1.1.1 Relevant Interfaces.13
4.3.1.1.2 Node Configuration.13
4.3.1.2 S-CSCF.13
4.3.1.2.1 Relevant Interfaces.13
4.3.1.2.2 Node Configuration.13
4.3.1.3 I-CSCF.13
4.3.1.3.1 Relevant Interfaces.13
4.3.1.3.2 Node Configuration.13
4.3.1.4 IBCF.13
4.3.1.4.1 Node Configuration.13
4.3.1.4.2 Relevant Interfaces.14
4.3.1.5 HSS.14
4.3.1.5.1 Relevant Interfaces.14
4.3.1.5.2 Node Configuration.14
4.3.2 External IMS Nodes.14
4.3.2.1 UE.14
4.3.2.1.1 Relevant Interfaces.14
4.3.2.1.2 Node Configuration.14
4.3.2.2 AS.15
4.3.2.2.1 Relevant Interfaces.15
4.3.2.2.2 Node Configuration.15
4.3.3 Supporting IMS Nodes .15
4.3.3.1 DNS.15
4.3.3.1.1 Relevant Interfaces.15
4.3.3.1.2 Node Configuration.15
4.3.4 Test Configurations.15
4.4 Use Cases.20
4.4.1 IMS Registration in a Visited Network.20
4.4.1.1 Description.20
4.4.1.2 UC_01_R: SIP message flow for IMS registration with CF ROAM .21
4.4.2 User-initiated VoIP call setup and release .21
ETSI
4 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.4.2.1 Normal Call.21
4.4.2.1.1 Description.21
4.4.2.1.2 UC_02_I: SIP Call Flow "Normal Call" with CF_INT_CALL.23
4.4.2.1.3 UC_02_R: SIP Call Flow "Normal Call" with CF_ROAM_CALL .24
4.4.3 User-initiated call hold and resume .27
4.4.3.1 User-initiated call hold and resume using reINVITE.27
4.4.3.1.1 Description.27
4.4.3.1.2 UC_03_I: SIP Call Flow "call hold and resume" using reINVITE with CF_INT_CALL.28
4.4.3.1.3 UC_03_R: SIP Call Flow "call hold and resume" using reINVITE with CF_ROAM_CALL.30
4.4.3.2 User-initiated call hold and resume using UPDATE .33
4.4.3.2.1 Description.33
4.4.3.2.2 UC_04_I: SIP Call Flow "call hold and resume" using UPDATE with CF_INT_CALL .34
4.4.3.2.3 UC_04_R: SIP Call Flow "call hold and resume" using UPDATE with CF_ROAM_CALL.35
4.4.4 IMS message exchange between UEs in different networks .37
4.4.4.1 Description.37
4.4.4.2 UC_05_I: SIP Call flow for IMS Message Exchange with CF_INT_CALL.38
4.4.4.3 UC_05_R: SIP Call Flow for IMS Message Exchange with CF_ROAM_CALL .38
4.4.5 Supplementary Service Anonymous Communication Rejection (ACR) .38
4.4.5.1 Description.38
4.4.5.2 UC_06_R: SIP message flow for SS ACR with CF_ROAM_AS.39
4.4.6 Supplementary Service Outgoing Communication Barring (OCB).39
4.4.6.1 Description.39
4.4.6.2 UC_07_R: SIP message flow for SS OCB with CF_ROAM_AS.40
4.4.7 Supplementary Service Originating Identification Presentation (OIP).40
4.4.7.1 Description.40
4.4.7.2 UC_08_R: SIP message flow for SS OIP with CF_ROAM_AS.41
4.4.8 Supplementary Service Originating Identification Restriction (OIR).42
4.4.8.1 Description.42
4.4.8.2 UC_09_R: SIP message flow for SS OIR with CF_ROAM_AS .43
4.4.9 Supplementary Service HOLD.44
4.4.9.1 Description.44
4.4.9.1.1 UC_10_R: SIP Call Flow "call hold and resume with AS tones and/or announcements" using
reINVITE with CF_ROAM_AS.45
4.4.10 Supplementary Service Call Forward Unconditional (CFU) .47
4.4.10.1 Description.47
4.4.10.1.1 UC_11_R: SIP Call Flow "Communication Forwarding unconditional" with CF_ROAM_AS .48
4.5 Test Descriptions.49
4.5.1 General Capabilities.50
4.5.1.1 SIP messages longer than 1 500 bytes.50
4.5.2 Registration and De-registration.51
4.5.2.1 First time registration in a visited IMS network.51
4.5.2.2 Multiple entry points, no response from first entry point on REGISTER.54
4.5.2.3 403 response to REGISTER from an un-trusted domain .56
4.5.2.4 Network initiated deregistration upon receipt of a new registration with new contact information.57
4.5.2.5 Network initiated deregistration by the S-CSCF.59
4.5.2.6 Network initiated re-authentication by the S-CSCF.61
4.5.2.7 First time registration in a visited IMS network requiring Topology Hiding.63
4.5.3 Initial Dialog or Standalone Procedures .65
4.5.3.1 Initial INVITE Dialog Procedures .65
4.5.3.1.1 Initial INVITE Request Procedures - Originating .65
4.5.3.1.2 Dialogue Procedures with Roaming .76
4.5.3.1.3 Subsequent Request Procedures - Originating Network.88
4.5.3.1.4 Subsequent Request Procedures - Terminating Network .98
4.5.3.1.5 Dialogue Procedures - Topology Hiding.100
4.5.4 Messaging.107
4.5.4.1 Messaging with SIP URI public identities .107
4.5.4.2 Messaging with TEL URI identities.109
4.5.4.3 Messaging with DNS/ENUM lookup procedure.111
4.5.4.4 Messaging when roaming.113
4.5.4.5 Messaging with receiving user not registered .114
4.5.4.6 Messaging with receiving user barred.115
4.5.5 Supplementary Services.117
ETSI
5 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.5.5.1 Supplementary Service HOLD with AS .117
History .120

ETSI
6 ETSI TS 186 011-2 V2.1.1 (2009-02)
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 2 of a multi-part deliverable covering the IMS NNI Interworking Test Specifications, as
identified below:
Part 1: "Test Purposes for IMS NNI Interworking";
Part 2: "Test Descriptions for IMS NNI Interworking".
ETSI
7 ETSI TS 186 011-2 V2.1.1 (2009-02)
1 Scope
The present document specifies interoperability Test Descriptions (TDs) for IMS NNI interoperability testing for the IP
Multimedia Call Control Protocol based on Stage 3 Session Initiation Protocol (SIP) and Session Description Protocol
(SDP) standard, TS 124 229 Release 7 [1]. TDs have been specified on the basis of the Test Purposes (TPs) and Test
Suite Structure (TSS) presented in TS 124 229 [1]. TP fragments presented in the present document as part of TDs are
defined using the TPLan notation of ES 202 553 [5]. TDs have been written based on the test specification framework
described in TS 102 351 [3] and the interoperability testing methodology defined in TS 102 237-1 [4],
i.e. interoperability testing with a conformance relation.
For the assessment of IMS core network requirements related to the ISC interface parts of the supplementary services
HOLD (TS 124 410 [10]), CDIV (TS 124 404 [11]), ACR-CB (TS 124 411 [12]) and OIP/OIR (TS 124 407 [13]) have
been used.
The scope of these test descriptions is not to cover all requirements specified in TS 124 229 [1]. TDs have been only
specified for requirements that are observable at the interface between two IMS core network implementations, i.e. IMS
NNI.
NOTE: Requirements pertaining to a UE or an AS implementation or IMS core network requirements that can
only be observed at the interface between UE and IMS CN are explicitly not within the scope of the
present document. The latter requirements have been dealt with from a UE and conformance perspective
in TS 134 229 [6].
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.
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 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 124 229:" Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol
based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
(3GPP TS 24.229 version 7.2.0 Release 7)".
[2] ETSI TS 186 011-1 (V2.1.1): "Telecommunications and Internet converged Services and Protocols
for Advanced Networking (TISPAN); IMS NNI Interworking Test Specifications; Part 1: Test
Purposes for IMS NNI Interworking".
ETSI
8 ETSI TS 186 011-2 V2.1.1 (2009-02)
[3] ETSI TS 102 351: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT);
IPv6 Testing: Methodology and Framework".
[4] ETSI TS 102 237-1: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to
interoperability testing".
[5] ETSI ES 202 553: "Methods for Testing and Specification (MTS); TPLan: A notation for
expressing Test Purposes".
[6] ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP)
multimedia call control protocol based on Session Initiation Protocol (SIP) and Session
Description Protocol (SDP); Part 1: Protocol conformance specification (3GPP TS 34.229-1
version 7.0.0 Release 7)".
[7] ETSI TS 133 203: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); 3G security; Access security for IP-based services
(3GPP TS 33.203 version 6.10.0 Release 6)".
[8] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
[9] IETF RFC 2806: "URLs for Telephone Calls".
[10] ETSI TS 124 410: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol;
Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification
(3GPP TS 24.410 version 7.0.0 Release 7)".
[11] ETSI TS 124 404: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services:
Communication Diversion (CDIV); Protocol specification (3GPP TS 24.404 version 7.0.0
Release 7)".
[12] ETSI TS 124 411: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Anonymous
Communication Rejection (ACR) and Communication Barring (CB); Protocol specification
(3GPP TS 24.411 version 7.0.0 Release 7)".
[13] ETSI TS 124 407: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Originating
Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol
specification (3GPP TS 24.407 version 7.0.0 Release 7)".
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.
[i.1] ETSI TR 133 978: "Universal Mobile Telecommunications System (UMTS); Security aspects of
early IP Multimedia Subsystem (IMS) (3GPP TR 33.978 version 6.6.0 Release 6)".
[i.2] ETSI TR 123 981: "Universal Mobile Telecommunications System (UMTS); Interworking aspects
and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations
(3GPP TR 23.981 version 6.4.0 Release 6)".
ETSI
9 ETSI TS 186 011-2 V2.1.1 (2009-02)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
ACR Anonymous Communication Rejection
AKA Authentication and Key Agreement
AS (IMS) Application Server
CB Call Barring
CDIV Call DIVersion
CF (Test) Configuration
CFW Call Flow
CN Core Network
CSCF Call Session Control Function
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
HOLD Communication HOLD
HSS Home Subscriber Server
IBCF Interconnection Border Control Gateway
I-CSCF Interrogating CSCF
IMS IP Multimedia Subsystem
IOI Inter Operator Identifier
IP Internet Protocol
IPsec Internet Protocol Security
ISC IMS Service Control
NNI Network-to-Network Interface
OIP Originating Identification Presentation
OIR Originating Identification Restriction
PCO Point of Control and Observation
P-CSCF Proxy CSCF
PO Point of Observation
PSTN Public Switched Telephone Network
SA Security Association
S-CSCF Serving CSCF
SDP Session Description Protocol
SIP Session Initiation Protocol
SUT System Under Test
TCP Transmission Control Protocol
TD Test Description
TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking
TP Test Purpose
TPLan Test Purpose Notation
TSS Test Suite Structure
UC Use Case
UE User Equipment
URI Uniform Record Identifier
VoIP Voice over Internet Protocol
XML eXtensible Markup Language
4 IMS NNI Interoperability Test Specification
4.1 Introduction
The IMS NNI Interoperability Test Descriptions (TDs) defined in the following clauses are derived from the Test
Purposes (TPs) specified in TS 186 011-1 [2]. The TDs cover both basic call procedures such as call establishment and
call release and a selection of the most common supplementary services.
ETSI
10 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.2 Test Prerequisites
4.2.1 IP Version
These test specifications are based on the use of IPv4 for SIP message transport throughout all IMS nodes as specified
in TR 123 981 [i.2].
4.2.2 Authentication and Security
The current test specification supports as default full IMS TS 133 203 [7] 3GPP security. Non-compliance with full
IMS security features defined in TS 133 203 [7] is expected to be a problem mainly at the UE side, because of the
potential lack of support of the USIM/ISIM interface (especially in 2G-only devices) and of the potential inability to
support IPsec on some UE platforms. For those reasons, fallback to early IMS TR 133 978 [i.1] and SIP Digest
authentication without key agreement and null authentication may be used to achieve satisfactory test results. Tests
should however be executed with full IMS security if all required IMS nodes support it.
4.2.3 Registration and Subscription
4.2.3.1 SIP Call Flow
This clause describes the registration call flow under the authentication and security scope described in clause 4.2.2.
4.2.3.1.1 Early IMS Registration and Subscription Call Flow
Early IMS security does not allow SIP requests to be protected using an IPsec Security Association (SA) because it does
not perform a key agreement procedure. IPsec security associations are not set up between UE and P-CSCF, as they are
in the full IMS security solution. For early IMS security, the expected registration and subscription sequence is:
Step Direction Message Comment
UE IMS
1  The UE establishes an IP bearer as required by its
specific access network (optional).
2  P-CSCF address discovery using DHCP procedures for
IPv4 (optional).
3 REGISTER The UE sends initial registration for IMS services.
4 200 OK The IMS responds with 200 OK.
5 SUBSCRIBE The UE subscribes to its registration event package.
6 200 OK The IMS responds with 200 OK.

7 NOTIFY The IMS sends initial NOTIFY for registration event
package, containing full registration state information for
the registered public user identity in the XML body.
8 200 OK The UE responds with 200 OK.

ETSI
Unprotected
11 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.2.3.1.2 Full IMS Registration and Subscription Call Flow
For full IMS security, the expected registration and subscription sequence is:
Step Direction Message Comment
UE IMS
1  The UE establishes an IP bearer as required by its
specific access network (optional).
2  P-CSCF address discovery using DHCP
procedures for IPv4 (optional).

3 REGISTER The UE sends initial registration for IMS services.
4 401 Unauthorized The IMS responds with a valid Digest AKA
authentication challenge and a list of integrity and
encryption algorithms supported by the network as
defined in the IMS AKA procedure of
TS 133 203 [7].
5  Upon receipt of 401 Unauthorized, the UE selects
the first integrity and encryption algorithm
combination on the list received from the P-CSCF in
401 Unauthorized which is also supported by the
UE. If the P-CSCF did not include any
confidentiality algorithm in 401 Unauthorized then
the UE shall select the NULL encryption algorithm.
The UE then proceeds to establish two new pairs of
IPSEC security associations (SA1 and SA2).
6 REGISTER The UE sends another REGISTER with
authentication credentials over IPSEC security
association SA1.
7 200 OK The IMS responds with 200 OK over the same
IPSEC security association SA1.
8 SUBSCRIBE The UE subscribes to its registration event package
over the IPSEC security association SA2.
9 200 OK The IMS responds with 200 OK over the IPSEC
security association SA2.
10 NOTIFY The IMS sends initial NOTIFY for registration event
package, containing full registration state
information for the registered public user identity in
the XML body, over the IPSEC security association
SA2.
11 200 OK The UE responds with 200 OK over the IPSEC
security association SA2.
ETSI
Protected by SA2 Protected Unprotected
by SA1
12 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.2.3.1.3 SIP Digest Registration and Subscription Call Flow
For SIP Digest authentication without key agreement and null authentication, the expected registration and subscription
sequence is:
Step Direction Message Comment
UE IMS
1  The UE establishes an IP bearer as required by its
specific access network (optional).

2 P-CSCF address discovery using DHCP
procedures for IPv4 (optional).
3 REGISTER The UE sends initial registration for IMS services.

4 401 Unauthorized The IMS responds with a valid HTTP Digest
authentication challenge as defined in
RFC 2617 [8].
5 REGISTER The UE sends another REGISTER with
authentication credentials.
6 200 OK The IMS responds with 200 OK.
7 SUBSCRIBE The UE subscribes to its registration event
package.
8 200 OK The IMS responds with 200 OK.
9 NOTIFY The IMS sends initial NOTIFY for registration event
package, containing full registration state
information for the registered public user identity in
the XML body.
10 200 OK The UE responds with 200 OK.

4.2.4 Supported Options
4.2.4.1 Security
Support for security agreement is optional in case of Full IMS Reg. It shall only be used in case all IMS nodes support
it.
4.2.4.2 Signalling Compression
"No SigComp" is the default signalling configuration in all test descriptions. Tests may be executed with signalling
compression if the required nodes support it.
4.3 Test Infrastructure
In these clauses we define the involvement of the various IMS nodes specifically as they pertain to NNI testing. The
configuration of the nodes is described. Points of control and observation are identified and static test configurations are
described. The Mw interface or the Ic interface if topology hiding is required is the interface under observation for NNI
interoperability testing.
4.3.1 Core IMS Nodes
Because the current testing scope excludes IMS roaming and border control functionality, P-CSCF, S-CSCF, I-CSCF,
IBCF and HSS are considered to be within a "black box" for testing purposes, i.e. the System Under Test (SUT).
Interfaces within the IMS are considered internal and not observable for testing purposes.
ETSI
Unprotected
13 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.3.1.1 P-CSCF
4.3.1.1.1 Relevant Interfaces
The P-CSCF constitutes the point of entry for UE signalling into the IMS core. The Gm interface between the P-CSCF
and the UE is used as a Point of Control and Observation (PCO) for NNI interoperability testing purposes. In the case of
IMS roaming configurations where no topology hiding is applied the Mw interface of the P-CSCF is exposed at the NNI
and used there as a Point of Observation (PO).
4.3.1.1.2 Node Configuration
The P-CSCF should be configured to support the pre-requisites outlined in clause 4.2.
4.3.1.2 S-CSCF
4.3.1.2.1 Relevant Interfaces
The S-CSCF is the core IMS node delivering IMS services to subscribers. When no topology hiding is applied, the Mw
interface between the S-CSCF and either I- or S-CSCF in another network domain is used as a PO against which NNI
interoperability tests are validated. The Mw interfaces between I- and S-CSCFs within the same network are considered
to be internal IMS interfaces. Although considered as internal and not explicitly involved in all NNI test configurations,
it is recommended that these interface are exposed for troubleshooting purposes.
4.3.1.2.2 Node Configuration
The S-CSCF should be configured to support the pre-requisites outlined in clause 4.2. When applicable based on the
specific configuration, the S-CSCF must be provisioned to support required application servers (AS) as trusted nodes.
4.3.1.3 I-CSCF
4.3.1.3.1 Relevant Interfaces
The I-CSCF is the contact point within an operator's network for all connections destined to a user of that network
operator or a roaming user currently located within that network operator's service area. When no topology hiding is
applied, the Mw interface between the I-CSCF and an S-CSCF in another network domain is used as a PO against
which NNI interoperability tests are validated. The Mw interfaces between I- and S-CSCFs within the same network are
considered to be internal IMS interfaces. Although considered as internal and not explicitly involved in all NNI test
configurations, it is recommended that these interface are exposed for troubleshooting purposes.
4.3.1.3.2 Node Configuration
The I-CSCF should be configured to support the pre-requisites outlined in clause 4.2.
4.3.1.4 IBCF
The IBCF is the core IMS node providing topology hiding. When topology hiding is applied, the Ic interface between
the IBCF and either IBCF or I- or S-CSCF in another network domain is used as a PO against which NNI
interoperability tests are validated. The Mw interfaces between IBCF and I- or S-CSCFs within the same network are
considered to be internal IMS interfaces. Although considered as internal and not explicitly involved in all NNI test
configurations, it is recommended that these interfaces are exposed for troubleshooting purposes.
4.3.1.4.1 Node Configuration
The IBCF should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the IBCF as
part of an IMS core network depends highly on the test description to be executed. In case the requirement to support
topology hiding is not explicitly stated in the pre-conditions of a test description it shall be assumed that the IBCF is not
activated.
ETSI
14 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.3.1.4.2 Relevant Interfaces
4.3.1.5 HSS
4.3.1.5.1 Relevant Interfaces
The HSS constitutes the repository for IMS subscriber information. The Cx interface between the HSS and the S-CSCF
and/or I-CSCF is considered an internal IMS interface.
4.3.1.5.2 Node Configuration
The HSS should be configured within each IMS participating in an interoperability test, i.e. IMS_A as well as IMS_B,
to interact with CSCFs as required using DIAMETER Cx interfaces. Users should be provisioned to match the sample
profiles listed in table 1. In addition, each IMS shall have its own unique domain. Also the phone numbers configured in
the two IMSes participating in an interoperability test shall be unique, i.e. IMS_A and IMS_B shall have no phone
numbers in common. All public identities belong to the same implicitly registered set.
Table 1: HSS sample user profiles
Private Identity Public Identity 1 Public Identity 2 Default Public Filter criteria
(Tel URI) Identity
user_1_priv user_1_pub n.a. 1 na
user_2_priv user_2_pub e.g. tel:0633348273 1 na
user_3_priv user_3_pub e.g. tel:0633348274 2 na
user_4_priv user_4_pub n.a. 1 terminating_unregistered/INVITE/
SESSION_TERMINATED/
as-1.ims-a.net
user_5_priv user_5_pub n.a. 1 TODO
user_6_priv user_6_pub n.a. 1 TODO

Public user identity may take the form of SIP or TEL URIs (RFC 2806 [9]).
EXAMPLE 1: sip:user_1_pub@ims_a.net
EXAMPLE 2: tel: 0633348273@ims_a.net
Private user identity may take the form of- @ims.mnc..mcc.3gppnetwork.org
EXAMPLE 3: 293410100367663@ims.041mnc.293.mcc.3gppnetwork.org
4.3.2 External IMS Nodes
4.3.2.1 UE
4.3.2.1.1 Relevant Interfaces
The UE is considered to act as a stimulus node in this test specification. The Gm interface between the P-CSCF and the
UE is used as a point of control and observation (PCO) for NNI interoperability tests.
4.3.2.1.2 Node Configuration
The UE should be configured to support the pre-requisites outlined in clause 4.2. The test descriptions in the present
document assume that a UE supports basic call and messaging functionality, target refresh based on UPDATE and on
re-INVITE method, message transport via UDP and TCP and the use of at least one of the supplementary services
HOLD (TS 124 410 [10]), CDIV (TS 124 404 [11]), ACR-CB (TS 124 411 [12]) or (TS 124 407 OIP/OIR [13]). In the
case that a UE does not meet one or more of these features, only a selected subset of the test descriptions in the present
document should be used for IMS core network interoperability testing, i.e. test descriptions which do not contain any
pass criteria related to these features.
ETSI
15 ETSI TS 186 011-2 V2.1.1 (2009-02)
4.3.2.2 AS
4.3.2.2.1 Relevant Interfaces
The application server (AS) is considered to act as a stimulus node in this test specification. The ISC interface between
the S-CSCF and the AS is used as a Point of Control and Observation (PCO) for NNI interoperability tests.
4.3.2.2.2 Node Configuration
The AS should be configured to support the pre-requisites outlined in clause 4.2. The test descriptions in the present
document assume that an AS supports the use of at least one of the supplementary services HOLD (TS 124 410 [10]),
CDIV (TS 124 404 [11]), ACR-CB (TS 124 411 [12]) or (TS 124 407 OIP/OIR [13]).
4.3.3 Supporting IMS Nodes
4.3.3.1 DNS
4.3.3.1.1 Relevant Interfaces
The Domain Name Service (DNS) is considered as a supporting entity in this test specification.
4.3.3.1.2 Node Configuration
DNS should be configured for appropriate resource record handling as required to support proper resolution of all SIP
URIs in Request URIs and Route headers. In addition, DNS must support ENUM functionality in order to resolve Tel
URIs into SIP URIs. As an example, a DNS should have an entry to map E.164 number 0633348273 with user
user_2_priv@ims_a.net.
4.3.4 Test Configurations
The following architectural test configurations are referenced in the IMS NNI interoperability TDs in the present
document. They are intended to give a general rather than a specific view of the required IMS SUT(s) connectivity and
associated UE(s), AS(s) and DNS(s).
NOTE: In the following figures observable interfaces are indicated as a solid line, non-observable interfaces
indicated as dashed lines and IBCF assumed to act in a "pass-through" mode if topology hiding is not
required by a test description.
ETSI
16 ETSI TS 186 011-2 V2.1.1 (2009-02)

Figure 1: CF_ROAM_REG
ETSI
17 ETSI TS 186 011-2 V2.1.1 (2009-02)

Figure 2: CF_INT_CALL
ETSI
18 ETSI TS 186 011-2 V2.1.1 (2009-02)

Figure 3: CF_ROAM_CALL
ETSI
19 ETSI TS 186 011-2 V2.1.1 (2009-02)

Figure 4: CF_INT_AS
ETSI
20 ETSI TS 186 011-2 V2.1.1 (2009-02)

Figure 5: CF_ROAM_AS
4.4 Use Cases
Use cases are the basis for interoperability test descriptions. Each use case defines both a generic test sequence, i.e. a set
of user stimuli and observations for any number of involved IM
...