Volte - Rcs Roaming and Interconnection Guidelines 19 May 2015
Volte - Rcs Roaming and Interconnection Guidelines 19 May 2015
Volte - Rcs Roaming and Interconnection Guidelines 19 May 2015
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Copyright Notice
Copyright 2015 GSM Association
Disclaimer
The GSM Association (Association) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept
any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document.
The information contained in this document may be subject to change without prior notice.
Antitrust Notice
The information contain herein is in full compliance with the GSM Associations antitrust compliance policy.
V1.0
Page 1 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Table of Contents
1
Introduction
1.1 Purpose
1.2 Scope
1.3 Definition of Terms
1.4 Document Cross-References
Reference Architecture
2.1 Overview
2.2 IMS Roaming Architecture Options
2.2.1
Local Breakout Architecture
2.2.2
Home Routed Architecture
2.3 Recommendation
Technical Requirements and Recommendations
3.1 Roaming Interfaces
3.1.1
S8 Interface
3.1.2
S6a Interface
3.1.3
S9 Interface
3.2 IP Interworking
3.2.1
Overview
3.2.2
Interworking Form for IMS Services
3.2.3
Inter-PLMN IP Backbone
3.3 IPX Interconnection
3.3.1
Overview
Other Technical Requirements and Recommendations
4.1 Addressing and Routing
4.2 QoS Support
4.2.1
Overview
4.2.2
Options
4.2.3
Recommendations
4.3 Policy and Charging Support
4.3.1
Overview
4.3.2
Options
4.3.3
Recommendations
4.4 Security
4.5 Emergency Services
4.6 Lawful Interception
4.6.1
Overview
4.6.2
Options
4.6.3
Recommendations
VoLTE Roaming and Interconnection
5
5
5
5
7
10
10
11
11
13
15
16
16
16
16
16
16
16
17
17
17
17
17
17
17
17
18
18
18
18
18
19
19
19
19
19
19
20
20
5.1 Connectivity
5.1.1
Overview
5.2 Codec Interworking
20
20
20
V0.1
Page 2 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
5.2.1
Overview
5.2.2
Recommendations
5.3 IPX Interconnection
5.4 Addressing and Routing
5.5 QoS Support
5.5.1
Overview
5.5.2
Recommendations
5.6 Policy and Charging Support
5.6.1
Overview
5.6.2
Recommendations
5.7 Security
5.8 Emergency Services
5.8.1
Overview
5.8.2
Recommendations
5.9 Supplementary Services
5.9.1
Overview
5.9.2
Configuration Options for Supplementary Services
5.9.3
Recommendations
ViLTE Roaming and Interconnection
6.1 Connectivity
6.1.1
Overview
6.1.2
Recommendations
6.2 IPX Interconnection
6.3 Addressing and Routing
6.4 QoS Support
6.4.2
Options
6.4.3
Recommendations
6.5 Policy and Charging Support
6.5.1
Overview
6.5.2
Recommendations
6.6 Security
6.7 Emergency Services
6.7.1
Overview
6.7.2
Recommendations
SMS over IP Roaming and Interconnection
7.1 Connectivity
7.1.1
Overview
7.1.2
Options
7.1.3
Recommendations
7.2 IPX Interconnection
7.3 Addressing and Routing
7.4 QoS Support
7.5 Policy and Charging Support
7.6 Security
V0.1
20
20
21
21
21
21
21
21
21
21
21
21
21
21
22
22
22
22
22
22
22
22
22
22
22
23
23
23
23
23
23
23
23
23
23
23
23
24
25
25
25
25
25
26
Page 3 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
26
26
8.1 Connectivity
8.1.1
Overview
8.1.2
Options
8.1.3
Recommendations
8.2 IPX Interconnection
8.3 Addressing and Routing
8.4 QoS Support
8.4.1
Overview
8.4.2
Recommendations
8.5 Policy and Charging Support
8.5.1
Overview
8.5.2
Recommendations
8.6 Security
8.7 Emergency Services
8.7.1
Overview
8.7.2
Recommendations
9 IMS Centralization Services (SrVCC/TADS/SCC AS)
10 Trials and Testing Lessons learned
10.1 Testing Framework
10.1.1 Roaming Testing
10.1.2 Inter-IMS NNI Testing
Annex A
Specific service requirements in certain regions
26
26
26
26
26
26
26
26
26
26
26
27
27
27
27
27
27
27
27
27
28
29
Annex B
30
V0.1
Document Management
Page 4 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
1 Introduction
Purpose
Next generation multimedia services such as VoLTE and RCS using IMS have long been
endorsed by the GSMA community. However, deployment of such services has been slow
due to the challenges posed by the various implementation options and the diverse
changing industry needs, specifically the impact on Roaming and Interworking scenarios.
Various documents have been written and continue to be tweaked by 3GPP and the GSMA.
The purpose of this document is not to replace or restate the information mentioned in those
documents, but to provide guidance on various implementation options and
recommendations associated with VoLTE-RCS Roaming & Interconnection. GSMA
specifications PRDs IR.92 [1], IR.94 [2], IR.65 [3], IR 88 [4], IR.90 [5], and RCC.07 [6] serve
as the basis for broader requirements on the subject matter.
Scope
This document defines guidelines for IMS service roaming in an Inter-Service Provider
environment, and targets existing IMS service deployments. It aims to complement
interworking procedures specified in GSMA PRDs RCC.54 [7] and IR.90 [5]. As such, it
elaborates on roaming aspects of the service interchange, taking into consideration
interconnection guidelines defined in GSMA PRD RCC.54 [7] and reference to the
Interworking Form for IMS Based Services, published as Annex B of GSMA PRD IR.90 [5].
Definition of Terms
Term
Description
AF
Application Function
APN
AS
Application Server
CDMA
CDR
CPM
Converged IP Messaging
CS
Circuit Switched
DSCP
DM
Device Management
DNS
ENUM
EPC
EPS
E-UTRAN
GBR
GRX
V0.1
Page 5 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Term
Description
GSM
GTP
HPMN
HSS
HTTP(S)
IBCF
II-NNI
IM
Instant Messaging
IMS
IP
Internet Protocol
IP-CAN
IPX
IR
International Roaming
LBO
Local Breakout
LI
Lawful Interception
LNP
LTE
MME
MMS
MMTel
MultiMedia Telephony
MNO
MSRP
NNI
Network-Network Interface
OCS
OMA
PCC
PCRF
PCEF
P-CSCF
PDN
P-GW
PLMN
PRD
PS
Packet Switched
PSAP
QCI
QoS
Quality of Service
V0.1
Page 6 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Term
Description
RCS
RTCP
RTP
SCC
SDP
S-GW
Signalling Gateway
SIMPLE
Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions
SIP
SLA
SMS
SMS-MO
SMS-MT
SMSoIP
SMS over IP
SR-VCC
TADS
TAP
TCP
TrGW
Transition Gateway
TRF
UDP
UE
User Equipment
UNI
ViLTE
VoLTE
VPMN
XCAP
XML
Document Cross-References
Ref
Doc Number
Title
[1]
IMS Profile for Voice and SMS, Version 8.0, 22 April 2014
[2]
[3]
[4]
[5]
[6]
GSMA PRD
RCC.07
V0.1
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Ref
Doc Number
[7]
GSMA PRD
RCC.54
[8]
[9]
[10]
[11]
GSMA PRD
AA.80
[12]
[13]
GSMA PRD
TD.41
[14]
GSMA PRD
TD.50
TAP Test Cases (TTC) for VoLTE Roaming Testing, Version 1.0, 06
May 2014.
[15]
GSMA PRD
TD.51
TAP Test Cases (TTC) for LTE and EPC Roaming Testing, Version
1.0, 15 May 2014.
[16]
[17]
[18]
[19]
[20]
3GPP TS 29.165
[21]
3GPP TS 23.228
[22]
3GPP TS 24.229
[23]
3GPP TS 26.114
[24]
3GPP TS 23.203
[25]
3GPP TS 33.106
[26]
3GPP TS 33.107
[27]
3GPP TS 33.108
[28]
3GPP TS 32.251
[29]
3GPP TS 32.299
[30]
OMA DM
[31]
[32]
ATIS-0700005
Lawfully Authorized Electronic Surveillance (LAES) for 3GPP IMSbased VoIP and other Multimedia Services
V0.1
Title
RCS Interconnection Guidelines, Version 1.0, 30 January 2014
Page 8 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Ref
[33]
V0.1
Doc Number
ATIS-1000678
Title
Lawfully Authorized Electronic Surveillance (LAES) for Voice over
Packet Technologies in Wireline Telecommunications Networks,
Version 2
Page 9 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
2 Reference Architecture
This section provides the reference architecture and introduces the components. Only a
high level description is provided as the idea is not to replicate what other documents
already provide.
Overview
The reference architecture of VoLTE-RCS including roaming and interworking is depicted in
the following figure. The architecture and procedures used for IMS-based services are
based on 3GPP specifications such as TS 23.228 [21] and TS 24.229 [22].
IMS
Core
AS
SCSCF
Control plane
IBCF
PCSCF
User plane
P-GW
EPS Core
S-GW
UE C
LTE MNO C
Non-Roaming
SCSCF
IMS Core
IBCF
PCSCF
AS
PCSCF
IMS
Core
IBCF
Roaming
IPX
P-GW
S-GW
P-GW
S-GW
UE A2
EPS Core
UE A1
EPS Core
Page 10 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
a) Due to security concerns, all AS(s) configuration servers are not accessible via
public Internet.
D iam eter
IP traffic
IMS
Services
PCC Infrastructure
HSS
hPCRF
HPMN
S6a
S9
OCS
Gy
VPMN
vPCRF
Gxc
MME
SGW
BBERF
Rx
Gx
P-CSCF
Visited
PDN-Gw
E-UTRAN
V0.1
Page 11 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
V0.1
Page 12 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
V0.1
ViLTE calling where the PCRF in HPMN requests the setup of a QCI=1 bearer and in
addition either a setup of a QCI-2 GBR bearer or of a non-GBR QCI bearer in the PGW in HPMN (per GSMA PRD IR.94 [2]). Bearer management support required in
the VPMN EPC and E-UTRAN is described in Sections 7.1.1 and 7.1.2 of GSMA
PRD IR.88 [4].
Anti Bill Shock where the PCRF or the OCS can ask the P-GW in the HPMN to
terminate the PDN connection once a threshold is reached per HPMN policy.
Page 13 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Figure 5 below based on but extending Figure 7.1-1 in GSMA PRD IR.88 [4] shows the
architecture diagram for this option.
V0.1
Page 14 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Recommendation
LBO Roaming Architecture as described in Section 2.2.1 is recommended if IMS (VoLTE)
Roaming is agreed between HPMN and VPMN.
Home Routed Architecture as described in Section 2.2.2 is left as an option if LTE Data
Roaming is agreed between HPMN and VPMN (with enforcement of QoS as described in
section 7.1.3 of GSMA PRD IR.88 [4]).
Note 1: The roaming architecture for handling Emergency Services is done
independently of the above architecture choices because of the nature of the
Emergency service requirements. This is described in section 4.5. Emergency Services
must be provided to normal attached UEs and, depending on local regulations, these
services can be extended to UEs in limited service state (e.g. UICC-less, no
V0.1
Page 15 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
subscription). However, the basic IMS architecture can be leveraged with Emergency
Services functionalities (e.g. E-CSCF and location support functions).
S6a Interface
Section 3.1.3 in GSMA PRD IR.88 [4] applies.
S9 Interface
Section 3.1.3 in GSMA PRD IR.88 [4] applies.
If the service requires dynamic policy and charging control from the HPMN, Section 3.3.1 in
GSMA PRD IR.88 [4] recommends the use of the S9 interface.
Note 1: VPMN and HPMN can exchange dynamic PCC rules over S9.
Note 2: VPMN and HPMN can exchange pre-configured PCC rules over S9; e.g. PCC
rules are provisioned directly to the VPMN PCEF but activated by the Home
PCRF.
Note 3: If S9 is not deployed, the Rating Groups and Service Identifiers used over Gy
are coordinated between HPMN and VPMN (see Section 2.2.1). The
assignment of Rating Groups and Service Identifiers is done as part of the PCC
rules provisioned in the PCEF of the Visited PGW. The Visited PCRF will use
locally configured policies according to the roaming agreement with the HPMN
as input for PPC rule generation (see note 2 in 3GPP TS 23.203 [24] Section
6.2.1.3.1).
IP Interworking
Overview
Sections 2, 3, 5 and 6 in GSMA PRD RCC.54 [7] provide guidelines for interconnection
between Service Providers for the purposes of interchanging VoLTE, ViLTE and RCS traffic
originating from and terminating to the respective Service Providers network.
V0.1
Page 16 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Inter-PLMN IP Backbone
IP Addressing Recommendation
Section 3.4.2 in GSMA PRD RCC.54 [7] allows use of IPv4, IPv6, or both for Service
Provider Interconnections.
Use of IPv6 is recommended to facilitate IMS interworking across North America IMS
deployments.
IPX Interconnection
Overview
Section 4 in GSMA PRD RCC.54 [7] provides the applicable portions of GSMA PRD IR.34
[8] that are used to provide guidelines on how Service Providers interconnect via an InterService Provider IP Backbone (IPX) network.
Note 1: Specific guidance for IPX Providers is not provided in the current version of GSMA
PRD RCC.54 [7].
If one or more Route headers are present, these will take precedence over the Request
URI.
QoS Support
Overview
Section 6A.1 in GSMA PRD IR.88 [4] specifies functionality needed in the VPMN and in the
HPMN to support QoS for LTE roaming. QoS support is required for setting up the default
V0.1
Page 17 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
bearer when a roaming UE registers with the VPMN. According to GSMA PRD IR.88 [4]
QoS support is subject to the roaming agreement between operators, and to be enforced by
the VPMN.
Options
In order to comply with agreed QoS policies the VPMN verifies the subscription information
associated with the roamer against the supported QoS parameter values defined in the
roaming agreement with the HPMN. If the roamers subscription information is outside of the
agreed parameter values, the VPMN would apply the QoS parameters specified in the
roaming agreement for the set up of a PDN connection requested by the roamer, rather
than using the parameters specified in the roamer subscription. In such cases, the HPMN
will accept the QoS parameter values provided by the VPMN.
Recommendations
Both VPMN and HPMN have to agree on the support of QoS policies defined in their
roaming agreement as specified in GSMA PRD IR.88 [4].
Options
According to 3GPP TS 23.203 [24] QoS authorization information may be dynamically
provisioned in PCC functional elements or pre-configured PCC rules can be statically
provisioned in those PCC elements.
In case PCC rules are dynamically provisioned, authorized QoS information is provided for
the setup of the requested bearer resources. If PCC rules are pre-configured, the
authorized QoS information is effective as soon as these are activated.
Regardless if the PCC rules are dynamically provided or pre-configured, the PCRF needs to
ensure that the PCC rules are within the limitations given by the subscription and operator
policies. In an LBO roaming scenario in Figure 2 the roaming partners may implement the
V0.1
Page 18 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Recommendations
Both VPMN and HPMN have to agree on the exchange authorized QoS information either
applying dynamic or pre-configured PCC rules for the synchronization of policy control
functions in the respective networks, and as specified in GSMA PRD IR.88 [4].
Security
Section 6.1 in GSMA PRD IR.88 [4] and section 4.3 in GSMA PRD IR.65 [3] indicate certain
requirements and procedures that Service Providers should take into account to guarantee
a proper level of operational security.
Emergency Services
Emergency services are supported by the serving network (which is the visited network
when roaming or the home network when not roaming). A P-GW within the serving network
is selected based on a specific emergency APN and which is not the IMS APN (refer to
GSMA PRD IR.88 [4] section 6.4). This provides for the following basic functionalities:
o Identifying the emergency session and setup of emergency bearers
o Routing the emergency session request to the appropriate PSAP
o Support of UE location determination with the location accuracy required
(per regulatory requirements)
o Support of PSAP call back.
Emergency Services are described in the corresponding sections of the IMS based services
for roaming and interconnection.
Note 1: Additional technical requirements associated with emerging IMS based
services, such as RCS are to be considered in the future.
Lawful Interception
Overview
Lawful interception (LI) requirements for 3GPP IMS-based VoIP and other 3GPP IMS-based
multimedia services are specified in 3GPP TS 33.106 [25].
Options
The lawful interception capabilities are specified in 3GPP standards TS 33.107 [26] and TS
33.108 [27].
V0.1
Page 19 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Note 1: The CS domain functionality as referring to CSFB is not in the scope of this
document.
Recommendations
Refer to 3GPP TS 33.106 [25] for global requirements for LI and Annex A for specific
regional requirements for LI.
Recommendations
Depending on an inter-PLMN roaming agreement or SLA being in place, routing of media
for VoLTE should follow VPMN Routing considerations. Otherwise, Home Routing will be
applied.
Codec Interworking
Overview
GSMA PRD RCC.54 [7] Section 7.3.2.1 recommends that AMR, AMR wideband and G.711
mu-law speech codecs will be supported across the NNI. Moreover, it states that Service
Providers will mutually agree as to the specific codec mode sets to be required and to be
optionally supported across the NNI, and indicate this information in the IP Voice Call
codec field of the IR.90 Interworking Form.
3GPP TS 26.114 [23] Table 6.3 on the handling of the AMR-NB and AMR-WB SDP
parameters in the SDP offer/answer states that the preferred mode-set for AMR-NB is {12.2,
7.4, 5.9, 4.75} and for AMR-WB it is {12.65, 8.85 and 6.60} unless the MTSI client in
terminal is configured with a preferred mode set.
Recommendations
GSMA PRD IR.36 [16] recommends WB-Set 0 as the recommended configuration for voice
transmission in all 3GPP mobile networks (that is 2G, 3G and Voice over LTE (VoLTE).
Refer to 3GPP TS 26.114 [23] for complementing NB mode-set recommendations.
V0.1
Page 20 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
IPX Interconnection
Refer to section 3.3 of this document.
QoS Support
Overview
Section 4.3.2 in GSMA PRD IR.92 [1] describes the bearer considerations for Voice calls in
E-UTRAN.
Recommendations
Refer to GSMA PRD IR.92 [1] and section 4.2 in this document.
Recommendations
Refer to GSMA PRD IR.88 [4] and section 4.3 in this document.
Security
Refer to section 4.4 of this document.
Emergency Services
Overview
Section 5.2 in GSMA PRD IR.92 [1] identifies specific requirements for the support of
Emergency Services in IMS based services such as for VoLTE service.
Recommendations
Refer to GSMA PRD IR.92 [1] and section 4.5 in this document.
V0.1
Page 21 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Supplementary Services
Overview
Support for VoLTE supplementary services is described in section 2.3 of GSMA PRD IR.92
[1]. The configuration of these services is described in section 2.3.2 of GSMA PRD IR.92
[1].
Recommendations
GSMA PRD IR.92 [1] requires the use of Ut interface for management of MMTEL
supplementary services.
Recommendations
Refer to GSMA PRDs IR.94 [2] and IR.65 [3].
IPX Interconnection
Refer to section 3.3 of this document.
QoS Support
6.1.1
Overview
Section 4.2.1 in GSMA PRD IR.94 [2] describes the bearer considerations for Video calls in
E-UTRAN.
V0.1
Page 22 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Options
Section 4.2.1 in GSMA PRD IR.94 [2] allows for use of the following options:
a) Video bearer using GBR (QCI 2)
b) Video bearer using non-GBR
Recommendations
GSMA PRD IR.94 [2] recommends the use of QCI 2 or a non-GBR bearer. Based on mutual
agreement between two mobile network operators, a non-GBR QCI may be used for video
bearer.
Note 1: QCI 7 or other non-GBR QCIs as defined in 3GPP TS 23.203 [24] may be used
as a non-GBR bearer for video
Recommendations
Refer to GSMA PRD IR.88 [4] and section 4.3 of this document.
Security
Refer to section 4.4 of this document.
Emergency Services
Overview
Annex B in GSMA PRD IR.94 [2] refers to GSMA PRD IR.92 [1] for specific requirements for
the support of IMS emergency services and how video capability may be applied.
Recommendations
Refer to GSMA PRDs IR.94 [2], IR.92 [1] and section 4.5 in this document
Page 23 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Note 3: Other GSMA PRDs refer to SMSoIP functionality using different terminology;
e.g., it is referred to as SMS over IMS in GSMA PRD IR.25 [10].
If a VPMN supports LTE data services but does not provide an IMS service to visiting
subscribers, then the VPMN must support SMS over SGs as described in GSMA PRD IR.88
[4] Sections 2.3.1 and 5.1.
Options
Note 1: GSMA PRDs IR.65 [3] and IR.88 [4] currently have no specification on SMSoIP
interworking in both the roaming and non-roaming aspects.
Section 2.4 in GSMA PRD IR.25 [10] describes the test SMS-MO and SMS-MT scenarios
needed to support SMS over IP (SMSoIP) roaming.
Note 2: Information on testing details for SMSoIP interworking pending in Section 2.4.1
in GSMA PRD IR.25 [10].
SMSoIP Roaming SMS-MO Scenario
Section 2.4.2.1 in GSMA PRD IR.25 [10] describes the SMS-MO over IMS while roaming.
This is shown in Figure 6 below (referencing Figure 2 in GSMA PRD IR.25 [10]).
V0.1
Page 24 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Recommendations
SMSoIP interworking considering both the roaming and non-roaming aspects is
recommended, although not currently specified in GSMA PRDs IR.65 [3] and IR.88 [4].
IPX Interconnection
Refer to section 3.3 of this document.
QoS Support
Not applicable.
Page 25 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Security
Refer to section 4.4 of this document.
Emergency Services
Refer to section 4.5 of this document.
Options
Interworking aspects of RCS are identified in GSMA PRD IR.90 [5].
Recommendations
Refer to GSMA PRDs RCC.54 [7], IR.90 [5] and IR.65 [3].
IPX Interconnection
Refer to section 3.3 of this document.
QoS Support
Overview
GSMA PRD RCC.54 [7] provides some guidance for QoS support in Section 4.6, but does
not specify the assignment of QCI within a Service Providers network as out of scope for
RCS Interconnection. However, according to section 2.9.1.3 in GSMA PRD RCC.07 [6] if a
device is in VoLTE mode, either QCI 8 or 9 may assigned for MSRP traffic.
Recommendations
Refer to GSMA PRDs RCC.54 [7] and RCC.07 [6].
V0.1
Page 26 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Recommendations
Refer to GSMA PRD IR.88 [4] and section 4.3 of this document.
Security
Refer to section 4.4 of this document.
Emergency Services
Overview
Section 2.16 in GSMA PRD RCC.07 [6] specifies requirements for the support IMS
Multimedia Emergency Services, further indicating that only the 1-to-1 Chat feature supports
the applicable procedures.
Recommendations
Refer to GSMA PRD RCC.07 [6] and section 4.5 of this document.
Testing Framework
Roaming Testing
Annex A in GSMA PRD IR.88 [4] provides references to GSMA PRDs IR.23 [18] and IR.35
[19] for LTE data roaming test cases.
Note 1: GSMA PRD IR.88 [4] currently does not include a reference to GSMA PRD
IR.38 [12].
LTE and EPC Roaming testing is described in GSMA PRD IR.38 [12]. The objective, as
stated in Section 1.2, is to confirm the capability of LTE data/CS Fallback/SMS over SGs
services which users will receive when roaming. The test procedures, which are restricted to
top-level capability testing, are described in Section 2.
Note 2: Section 1.1 in GSMA PRD IR.38 [12] listed the following as out of scope of the
PRD:
VoLTE and SMSoIP roaming testing is described in GSMA PRD IR.25 [10].
V0.1
Page 27 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Note 3: GSMA PRD IR.25 [10] does not include ViLTE and RCS 5.1 roaming test cases.
GSMA PRD TD.50 [14] specifies the TAP Test Cases for VoLTE service testing in
accordance to the TAP Testing Procedures in GSMA PRD TD.41 [13].
GSMA PRD TD.51 [15] specifies the TAP Test Cases for LTE and EPC service testing in
accordance to the TAP Testing Procedures in GSMA PRD TD.41 [13].
V0.1
Page 28 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Annex A
A.1
Lawful Interception
Lawful interception (LI) capabilities specified in this section are applicable for service
implementations in the United States. LI requirements in other regions also supporting
3GPP standards TS 33.106 [25], TS 33.107 [26], and TS 33.108 [27] should be considered
in the Annex in the future.
ATIS-0700005 [32] specifies the LI capabilities for 3GPP IMS-based VoIP and other 3GPP
IMS-based multimedia services and applicable for service implementations in the United
States. This ATIS Standard was published in 2007, and the second version is currently in
development by the ATIS WTSC-LI Subcommittee.
Note 1: ATIS-0700005 [32] covers requirements for IMS-based VoIP, which includes
VoLTE. This ATIS Standard identifies specific United States requirements for LI.
ATIS-0700005 [32] is provided for the purposes of a safe harbour as specified in Section
107 of the Communication Assistance for Law Enforcement Act (CALEA).
ATIS-0700005 [32] defines an interface between a Telecommunications Service Provider
and a Law Enforcement Agency for the reporting of lawfully authorized electronic
surveillance (LAES) for 3GPP IMS-based VoIP and 3GPP IMS-based multimedia
services.
The main purpose of ATIS-0700005 [32] is to provide capabilities for support of LAES for
VoIP. In addition, the scope also includes other IMS-based multimedia services because the
media type may change in mid-session (e.g., audio to video, video to audio). This ATIS
Standard provides for the mapping of SIP messages to ATIS-1000678 [33] LAES messages.
These LAES messages represent events in the processing of the VoIP call, and must take
place from the beginning of a session because of the potential for a change in the VoIP call
in the middle of the session.
V1.0
Page 29 of 30
GSM Association
Non-confidential
Official Document NG.103 - VoLTE RCS Roaming and Interconnection Guidelines
Annex B
B.1
Document Management
Document History
Version
Date
0.1
31/03/2015
B.2
Approval
Authority
GSMA PSMC
Editor
Company
Narayanan
Haran United
States Cellular
Corporation
Other Information
Type
Description
Document Owner
GSMA NG
Editor / Company
It is our intention to provide a quality product for your use. If you find any errors or omissions,
please contact us with your comments. You may notify us at [email protected]
V1.0
Page 30 of 30