VOLTE Introduction

Commercial LTE Voice Solutions

Page2
CSFB Definition
• The circuit switched fallback (CSFB) service enables calls to fall back to the CS domain. The
LTE network provides only data services. When a voice call is initiated or answered, it falls
back to the CS domain for processing. Therefore, carriers only need to upgrade the MSC
server without deploying the IMS network.
• Advantage: Voice services can be provided quickly with little change on the live
network.
• Disadvantage: When subscribers use voice services, data services carried on the LTE
network are interrupted, handed over, or suspended, and voice calls are connected
slowly. This affects user experience.

• Application scenario:
• CSFB is a transition solution before the IMS network deployment.
• If the IMS network is not deployed on the visited network, CSFB can provide voice
services for roaming LTE subscribers.

Page3
 CSFB Definition (Cont.)
⚫ Terminating side
MSC server MME  The MSC server sends a paging request to the
MME over the SGs interface.
CS SGs EPC  The MME forwards the paging request
instructing the UE to fall back to the 2G or 3G
network.
3
1  The UE falls back to the 2G or 3G network.
 The UE sends a paging response to the MSC
server and answers the call based on the
2G/3G LTE normal terminating flow.
2

Fallback MSC server 1 MME

• Originating side CS EPC

SGs
• The UE sends a voice call request to the
MME. The MME then instructs the UE to
fall back to the 2G or 3G network. 4 2
• The UE falls back to the 2G or 3G network.
• The UE initiates a call based on the
normal originating flow on the 2G or 3G
network. 2G/3G 3 LTE
Fallback

Page4
 SVLTE Definition
• In the simultaneous voice and LTE (SVLTE) solution, dual-mode mobile phones work on the
LTE network and the CS network simultaneously. The LTE network provides data services,
while the CS network provides voice services.
• Advantage: SVLTE is a solution for mobile phones without requirements for the network.

• Disadvantage: The cost and power consumption of dual-mode mobile phones are high.

MSC server
MME

CS EPC

Voice service Data service

2G/3G LTE

Page5
OTT Definition
• Over-the-top (OTT) is a solution that uses APPs, such as the Skype, to provide voice
services for LTE subscribers.
• Advantage:
• Only the OTT server needs to be deployed to the live network and slight change is
required. The OTT can enhance user experience by offering rich multimedia services.
• Disadvantages:
• The OTT solution is not carrier-class-based and has low reliability.
• The OTT solution cannot provide E2E QoS guarantee.
• The OTT solution is hard to provide common services, such as emergency calls and
interception, and services that are used only by regulatory bodies.
• Roaming and interconnection are hard to be implemented due to lack of standards.

Page6
 VoLTE Definition
Voice over long term evolution (VoLTE) is an IMS-based voice solution defined
by 3GPP. By deploying the IMS network, operators not only migrate traditional
voice and short message services on live networks but also integrate voice
services with various enhanced functions to diversify services.

VoLTE advantages

⚫ The VoLTE solution inherits all services provided by the CS network, including common services, such as
emergency calls and interception, and services that are used only by regulatory bodies.
⚫ The VoLTE solution can implement E2E QoS control and guarantee voice call quality.
⚫ In the VoLTE solution, voice services are carried on IP networks. Therefore, subscribers can enjoy richer
multimedia services through the IMS network, compete with OTT.
⚫ Subscriber identities (such as the MSISDN) are reserved, which maximizes carriers' resource usage and
facilitates service profit gain.
⚫ The IMS architecture, supported by mature 3GPP standards and specifications, is considered to be the
next generation core network by the communications industry. The IMS architecture ensures roaming
services and network interworking.

Page7
 Three Forces to Drive VoLTE/RCS driving force
investigation result

VoLTE Development (159 participants in the IMS summit

in April 2011)

1. Competing with OTT 2. User experience 3. Unifying the network and reducing TCO
(real driving force) 33.33% (permanent driving force) 30.19% (long-term driving force) 26.42%

• The LTE network features high • HD voice •The spectral efficiency of LTE voice
bandwidth, low delay, all IP, and always • HD video session services increases over four times
online, which facilitates OTT
application development. • Faster call connection compared with that of CS voice
• IMS-based multimedia voice services • Rich multimedia communication services.
and RCS serve as carriers' main experience (IM/Presence •Number of voice channels per sector
competitive sources. service/enhanced address book) •Source: Qualcomm
• VoLTE provided by carriers outperforms
OTT in the following aspects:
• Telecommunication subscriber ID
and authentication
• Interconnection and interworking
• QoS guarantee
• Handover and roaming to 2G and 3G
networks
• Fee package bound to mobile
broadband
The time for setting up a VoLTE call is
• Fault troubleshooting and customer
half that for setting up a 3G call.
care

.
Better communication Faster connection rate Richer Higher spectral
quality services efficiency

Page8
Advantage of VoLTE – Better and Faster
Better Faster connection Richer Higher spectral
communication rate services efficiency
quality

⚫ VoLTE can significantly reduce the call establish delay, provide high-
definition audio and video calls, greatly enhance the user experience

⚫ Fast connection:
 CS call establish duration is around 4-5s，
VoLTE is 0.8 -1.5s.

⚫ HD video:
 VoLTE typical video definition is 480*640
（VGA）, HD 720P and full HD 1080P is
possible（H.264/H.265）

 3G typical video definition is 176*144 SD and HD video size

compare
（QCIF）
Advantage of VoLTE -- HD Voice Quality
Common ear listening range (CD/MP3 range)

HD voice (AMR-WB) The frequency range of human speech

Audio
range
20 50 80 7000
3400 12k Hz 20k Hz
Hz Hz Hz 300 CS Hz
Hz （AMR-NB) Hz

HD voice: (Twice frequency range the AMR-NB)

• VoCS voice: AMR-NB 300~3400 Hz, sampling frequency 8kHz, 12.2Kbps。
• VoLTE HD voice: AMR-WB (G.722.2 ) : 50~7000 Hz, same as the G.711 in PSTN, sampling frequency
16kHz, 23.85Kbps.
• CD music: 20~20K Hz, sampling frequency 44.1K.
Advantage of VoLTE -- QoS
Best effort for OTT services

LTE

Dedicate bearer for VoLTE

QCI Resource Pri. Delay Error rate service
2 GBR 4 150ms 10-6 VoLTE video

6 Non-GBR 6 300ms 10-3 OTT video

QCI: QoS class identifier GBR: guaranteed bit rate

 Advantage of VoLTE –VoLTE with Native RCS

Convergent
communication

VoLTE HD voice and video RCS embedded

contact Multimedia
message
 Comparison Among CSFB, SVLTE, VoLTE and OTT
Deployment
Solution Feature Advantage Disadvantage
Suggestion
The IMS and LTE
networks provide voice Rich multimedia
services. The handover services. The IMS network Large-scale LTE
VoLTE
between the LTE HD voice/video. needs to be deployed. coverage
network and 2G/3G E2E QoS
network is supported.
Voice calls are not
Voice services are Slight change is reliable.
OTT implemented by APPs required on live Roaming and -
of OTT carriers. networks. interworking are hard
to be implemented.
UEs attach to the LTE Slight change is
Initial phase of
network. When a UE required on live The call delay is long.
the LTE network
CSFB initiates or receives a networks. User experience is
(transition
call, the UE falls back to New NEs do not need affected.
solution)
the CS network. to be deployed.
Terminals attach to both Costs of mobile
Initial phase of
the CS and LTE phones are high.
The live network does the LTE network
SVLTE networks. The CS Advantages of the
not need to be adjusted. (transition
network provides voice LTE network cannot
solution)
services. be used.

Page13
Key Technologies Involved in VoLTE
• Voice based on IMS
• VoLTE voice services are IMS-based.

• SRVCC/eSRVCC
• If VoLTE voice services need to be handed over the GSM or RAN network, SRVCC or
eSRVCC is used.

• ICS for VoLTE

• To ensure that subscribers have consistent user experiences on the LTE and CS
networks, ICS is used.

Page14
IMS-based Voice Services MME
PCRF

EPC
E-UTRAN IMS Core
S-GW/P-
GW SBC I/S-CSCF
Handset /P-CSCF
Default bearer: IMS signaling streams
Dedicated bearer: Voice media streams
SIP signaling streams
Voice media streams

• A default bearer is set up for IMS signaling streams when the UE attaches to the network.
• After the UE initiates a call, SIP signaling streams for call connection is transmitted over the
default bearer through the P-GW to the IMS Core.
• A dedicated bearer for IMS voice media streams is set up during call connection.
• Voice media streams of the calling and called parties are transmitted over the dedicated bearer.
• The PCRF assigns and delivers QoS rules for signaling and media streams during the setup of
default and dedicated bearers. This ensures quality of signaling and media streams.

Page15
 VoLTE Basic
Call
• A dedicated
bearer for IMS
voice media
streams is set up
during call
connection

Page16
 SRVCC Definition

• Single radio voice call continuity (SRVCC) is an IMS-based VoLTE.

• VCC describes how a voice call can be continued when a UE moves between the target CS domain and the
LTE domain supporting VoIP services.

• SRVCC describes how a voice call can be continued when a Single Radio UE moves between LTE/Pre-LTE and
2G/3G networks, that is, when a Single Radio UE switches an call session between IMS/LTE and CS.

Page17
 SRVCC Definition (Cont.)
• Calls are set up in the LTE over VoIP / VoIMS.
• When a subscriber moves to an area uncovered by the LTE network while holding a call,
the call is switched to the CS domain. SRVCC interprets a switchover process.

⚫ SRVCC solution: The media

handover point is a peer
device. Such as a peer UE.
⚫ E2E signaling and bearer are
re-established.
⚫ The IMS network sends the
updated media information to
the remote network, and a
session is interrupted around
1s.

Page18
 eSRVCC Definition
• Target: The handover delay is less than 300 ms

• Policy: The remote session update process is optimized. The media handover point is
near to the local side.

⚫ Method: Media and signaling

planes are anchored at the
ATCF or ATGW to avoid the
IMS session transfer process.
When an eSRVCC handover is
performed, only the bearer
between the UE and the
ATGW needs to be set up.
⚫ The original bearer is reused to
transmit media streams
between the peer device and
the ATGW.

Page19
eSRVCC Vs SRVCC
before
SRVCC eSRVCC
E2E media re-establish after
Local media establish

LTE IMS/SBC
IMS/SBC LTE
RAN （ATCF & ATGW） RAN

G/U G/U
Remote RAN RAN
Remote
side side

> 1.5s ~ 0s < 230ms

First eSRVCC testing (Vienna 201210)

LTE to GSM HO time ~ 230ms (Beijing 201404)

ICS Definition
• IMS centralized services (ICS) describe how services of subscribers who access the CS domain or IP-CAN
using different terminals are managed on the IMS network in centralized mode.

• With the ICS feature, all services are centralized to IMS. Therefore, subscribers can have consistent user
experiences on the LTE and CS networks.

• By deploying an MSC server that supports the ICS feature on a network, ICS subscribers can use services
provided by IMS during the initial phase of LTE in the following scenarios:
• CS subscribers who have subscribed to the ICS feature wish to use IMS services without changing their numbers.
• VoLTE subscribers who roam to or experience an SRVCC handover to a CS network wish to continue to use the IMS
services.

Page21
 ICS Definition (Cont.) ICS Architecture
• The ICS solution becomes the
best choice for evolution from the Service layer AS AS AS

mobile softswitch to IMS. The

Centralized service
eMSC server functions as a SIP UA trigger point
IMS Core
and connects subscribers to the
IMS Core.

• MSC server enhancements for ICS,

the MSC server that supports the Access layer

ICS feature, is called mobile MSC server

mAGCF
xPON and
access gateway control function FBB
(mAGCF). In this document, the MGW

MSC server enhancements for ICS

is called eMSC server. 2G/3G
LTE

LTE subscriber
CS subscriber

Page22
 VoLTE Phase-based Deployment
Policy
Phase 1: Phase 2: Phase 3:
Hot spot LTE coverage Continuous LTE coverage Full LTE coverage

LTE LTE
LTE LTE
2G/3G 2G/3G 2G/3G

Pre-VoLTE Initial commercial use Large-scale commercial

deployment
⚫ Terminals: ⚫ Terminals: ⚫ Terminals:
 Initial smartphone  Smartphone
 Smartphone

 LTE data card and LTE CPE  LTE data card and LTE CPE
 LTE data card and LTE

⚫ Deployment suggestions:
 CSFB
 CPEs subscribe to IMS-
CPE
⚫ Deployment suggestions:
 IMS-based VoLTE voice
⚫ Deployment suggestions:
services  The LTE network becomes

based VoIP voice services.  eSRVCC

the mainstream.
 Soft clients subscribe to rich  Convergent database
 ICS

media RCS services. SingleSDB  IMS roaming and

 LTE-based rich media RCS
interworking
services
 Network Evolution Solution

Page24
Evolution to IMS/SRVCC/ICS
The live network
solution evolves to ICS
in the following ways:
Live network MSC servers • Evolution from
Deploy the SRVCC IWF/MGCF. deployment of the
overlay eMSC server
to ICS
• Direct Evolution to
MSC servers
ICS

Enhanced with the mAGCF/SRVCC IWF

Page25
Evolution from CSFB to ICS
The live network solution evolves from CSFB to ICS in the following ways:
• Evolution from the standard CSFB to ICS
• Evolution from the CSFB proxy to ICS

MSC servers

Enhanced with CSFB

MSC servers VoLTE (overlay eMSC server)

MSC servers MSC s ervers

Deploy MSC servers to serve as CSFB proxies. Enhanced with the SRVCC IWF/MGCF
VoLTE Network Architecture
Operation Support Layer and Service Layer
⚫ Operation support layer
Operation support layer  Functions: This layer provides various functions,
such as network management, subscription data
storage, unified operations on the web portal,
charging, and equipment management.
 NEs: DMS, SPG, CCF, and EMS

Service layer
⚫ Service layer
 Functions: This layer consists of different
ATS application servers and resource servers to provide
(MMtel AS/SCC AS/IP-SM-
GW/IM-SSF/Anchor AS)
services, such as instant messaging, conferences,
games, as well as service capabilities, such as group
and media resource capabilities.
 NEs: ATS and RCS

Page28
 Core Layer
⚫ The core layer is divided into the following three
Core layer
parts:
 IMS domain : NEs in the IMS domain implement
such functions for LTE subscribers as registration,
authentication, session path control, service trigger,
route selection, resource control, inter-domain
interworking, and access resource control.
 CS domain : NEs in the CS domain implement such
functions for LTE subscribers as mobility
management and voice services, including
handovers and CSFB.
 SingleSDB: The SingleSDB provides the functions of
the USCDB, HLR, IMS-HSS, SAE-HSS, PCRF,
DNS/ENUM for centralized storage of VoLTE
subscribers' service data. The data can be used by
the CS, IMS, and EPC domains.

Page29
Access Layer
⚫ Access layer
Access layer  Functions:
 The access layer controls LTE subscriber access
and provides mobility management for LTE
subscribers.
 When an LTE subscriber is in the LTE coverage, the
subscriber can access an IMS network through the
EPC.
 When a subscriber moves out of the LTE coverage,
the subscriber can access an IMS network through
a 2G/3G network using ICS.
 If the 2G/3G network does not support ICS, a
subscriber accesses a legacy CS network.
 NEs: eMSC server (mAGCF), S-GW, P-GW, and MME

Page30
Terminal Layer
⚫ Terminal layer
Terminal layer  LTE terminals are classified into VoLTE terminals
and non-VoLTE terminals.
 VoLTE terminals are those that rely on an IMS or
LTE network to use voice services. They include
Single Radio terminals, LTE data cards, and
CPEs.
 Non-VoLTE terminals are those that rely on a CS
network to use voice services and that connect
to an LTE network to use data services. They
include Dual Radio and CSFB terminals.
 Types: Single Radio terminals (SRVCC terminals),
LTE data cards, CPEs, Dual Radio terminals (SVLTE
terminals), and CSFB terminals

Page31
NEs at the Operation Support Layer
NE Name Function

Provides a unified service provisioning interface and the web portal

SPG and sends the service provisioning commands received from the
BSS to the HSS, ENUM, and AS.

Collects ACR messages from IMS charging NEs, such as the CSCF,
CCF ATS, and MGCF, processes the ARC messages to generate CDRs,
and sends the CDRs to a BC specified by carriers.

EMS Interworks with the BSS to manage NEs in a centralized manner.

Page32
 NEs at the Service Layer
NE Name Function
⚫ MMTel AS: provides basic and supplementary multimedia
telephony services.
⚫ SCC AS: interworks with the SRVCC IWF and ATCF/ATGW to
provide the eSRVCC function, and provides the T-ADS function
to select a domain for the called party.
Common ⚫ IP-SM-GW: provides short message interworking between IMS
telephony and CS domains.
application ⚫ IM-SSF: triggers IN services in the CS domain based on the
server subscription information provided by the S-CSCF and the local
(ATS) configuration on the IM-SSF.
• Anchor AS: Routes VoLTE subscribers' calls to the IMS
domain to trigger convergent services by IN-based number
redirection of the anchor AS, when the VoLTE subscribers
originate or receive a call in the CS domain.
Provides the Open Mobile Alliance Instant Message (OMA IM),
Presence, XML document management server (XDMS), and data
RCS AS
synchronization (DS) functions to implement the IM, Presence, and
Network Address Book services.

Page33
 NEs at the Service Layer - ATS
3GPP Mobile TISPAN Business
MMTel special PSTN service
• The ATS provides traditional service service service
mobile services and
multimedia services.

ATS
(MMTel + SCC AS + IP-SM-GW + IM-
SSF + anchor AS)

IMS network

MBB FBB PSTN

Mobile terminal Soft SIP
CPE
phone terminal

POTS POTS

⚫ The ATS integrates the functions of the MMTel AS, IM-SSF, SCC AS, Anchor AS, and IP-SM-
GW to reduce the number of attempts to trigger iFC during calls and realize service
resources sharing.

Page34
NEs at the Service Layer - SCC AS (ATS)
⚫ The service centralization and continuity application server SCC AS
(SCC AS) implements handovers in the IMS domain and ISC
updates the media information about the remote UE. In
IMS Core
details, the SCC AS does the following:

▪ Analyzes information
eMSC server
required by a handover. CS (SRVCC IWF) EPC

▪ Associates handover
requests and anchors Call signaling anchor point
Media connection 1
sessions. LTE
Called connection 3
▪ Implements handovers Handover
Calling SCC AS
connection 1 Called party
between the LTE network Calling access
and the UMTS network. connection 2
GERAN
UMTS Media connection 2

Page35
NEs at the Service Layer - T-ADS (SCC AS)
• T-ADS
• As defined in 3GPP specifications, domain selection by the network is implemented by the terminating access
domain selection (T-ADS).

• The T-ADS function is integrated with the SCC AS. The SCC AS queries the convergent HLR/HSS for the UE type and
access domain information and implements domain selection based on the carrier policies. Based on the T-ADS
information, the SCC AS determines whether the current call is routed to the IMS or CS network.

Page36
NEs at the Service Layer - IP-SM-GW (ATS)
⚫ The IP short message gateway (IP-SM-GW)
provides short message interworking between OCS CGF/CDF
IMS and CS domains.
Ro Rf
2 Translates instant messages to short messages.
•SMS-GMSC/ Sh
•SMS-IWMSC
IP-SM-GW HSS
E/Gd
ISC

SMSC IMS Core

3 Sends short
messages to UEs. 1 SIP message
SME UE

⚫ After the UE sends a SIP message, the IP-SM-GW converts the instant message (SIP
message) to a text message. When the UE registers with IMS, the IP-SM-GW downloads
the SMSC address to a local directory.

Page37
 NEs at the Service Layer - Anchor AS
(ATS)
AS
The anchor AS anchors calls from the CS
network to the IMS network as follows: IMS
Anchor AS
⚫ Routes VoLTE subscribers' calls to the CS MSC server
IMS domain to trigger convergent
services by IN-based number redirection
of the anchor AS, when the VoLTE VoLTE subscriber
subscribers originate or receive a call in
the CS domain.
IMS
⚫ Routes VoLTE subscribers' calls to the Anchor AS

IMS domain by IN-based number CS MSC server

redirection of the anchor AS, when the
VoLTE subscribers receive calls from CS LTE

subscribers. VoLTE
subscriber

Page38
NEs at the Service Layer - RCS AS
• The RCS AS provides the OMA IM, Presence, XDMS, and DS functions to
implement the IM, Presence, and Network Address Book services.

Image/Video share + Voice

File transfer
RCS-e Offline storage and forwarding
IM (1-1 and 1-M)
Capability discovery

Presence
RCS NAB/CAB
VoLTE integration

Page39
NEs at the Core Layer
NE Name Function
Controls subscriber roaming and stores the following information about a subscriber
IMS-HSS
in the IMS network: subscriber IDs, authentication data, service data, access
(FE)
parameters, service trigger information, and roaming information.
Stores service-related data of subscribers, manages subscription information and
SAE- location information, and combines the following NEs:
HSS/HLR • HSS in the EPC network
(FE) • HLR in CS and PS domains in the core network of the mobile telecommunication
system
USCDB Stores subscriber data and implements the functions of adding, deleting, updating,
(BE) and querying data at the request of the FE.
DNS/ENUM Implements functions provided by the DNS and the ENUM server.
eMSC Combines the following NEs:
server • SRVCC IWF: provides eSRVCC to ensure call continuity when terminals move
(SRVCC from an LTE network to a 2G/3G network.
IWF/CSFB • CSFB proxy: moves LTE subscribers to a CS domain to provide voice services for
proxy) them.
Realizes interworking between an IMS network and a PSTN or PLMN network.
If fixed network optimization is required or the live network provides a lot of fixed
MGCF
network services, the UGC3200 is used as the MGCF. In other scenarios, the
MSOFTX3000 is used as the MGCF.

Page40
NEs at the Core Layer (Cont.)
NE Name Function
Provides resources for announcement playing and digit collection, voice conferences,
MRFP
SD video conferences.
Combines the following NEs to provide call control, service triggering, and routing
functions:
• I-CSCF: As the entrance to the IMS home network, the I-CSCF assigns or queries
the HSS to select an appropriate S-CSCF to serve subscribers.
• S-CSCF: The S-CSCF is located on the home network as the central IMS node. It
I-CSCF/S-
implements subscription, authentication, session, routes, and service triggering.
CSCF/BGCF
• BGCF: The BGCF is located on the home network to select an MGCF for calls
/MRFC
between an IMS network and a PSTN or PLMN network. It is integrated into the S-
CSCF to reduce the need for standalone BGCFs. Therefore, call connection delay
is shorten and the reliability is enhanced.
• MRFC: The MRFC controls the MRFP to play announcements and collect digits,
and provide resources for voice conferences and SD video conferences.

Page41
NEs at the Core Layer (Cont.)
NE Name Function

• P-CSCF: located on the visited network as the first contact point for
subscribers within an IMS domain. The P-CSCF forwards SIP signaling
between SIP subscribers and their home networks.
• SBC: provides the core border gateway function (C-BGF) and interconnection
P-
border gateway function (I-BGF). The C-BGF is deployed at the edge of an
CSCF/SBC/ATC
access network to provide attack protection and NAT traversal. The I-BGF
F/ATGW
provides media channels for an IMS network to interwork with other networks
that use SIP or H.323 signaling.
• ATCF/ATGW: located between the P-CSCF and I-CSCF/S-CSCF and
interworks with the SCC AS to provide eSRVCC.

Provides audio media channels for interworking between an IMS network and a
MGW/IM-MGW
PSTN or PLMN network.

Page42
 NEs at the Core Layer - SRVCC IWF
⚫ The SRVCC IWF ensures call continuity when terminals move
from an LTE network to a 2G/3G network. When receiving the
location update request from a UE, the SRVCC IWF changes the
SCC AS
UE access location from the MME to the MSC server based on
the target cell ID contained in the location update request.
IMS Core

⚫ The SRVCC IWF is collocated

with an MSC server or deployed eMSC server
CS (SRVCC IWF) Sv EPC
as a standalone entity. If the
SRVCC IWF is deployed as a
standalone entity, it functions
as a proxy of the MSC server
MSC 2 Selects target MSC
and performs conversion for
MSC
signaling messages between SRVCC IWF MME UE
MSC
the MSC server, SBC, and MME.
MSC
1 Handover request

Page43
NEs at the Core Layer - ATCF/ATGW
⚫ The ATCF/ATGW is located between the P-CSCF and I-CSCF/S-CSCF and
interworks with the SCC AS to provide eSRVCC.
• During a call, the ATCF or ATGW determines whether to anchor a call on the media
plane based on carriers' policies and terminal capabilities.
• During an eSRVCC handover, the ATCF or ATGW correlates a handover request
initiated by the SRVCC IWF with the anchored session, updates session bearer
information, and initiates a handover request to the SCC AS.

2G/3G SRVCC
CS
IWF SCC AS Remote UE
IMS Core
Handover
ATCF
LTE
PS ATGW SBC

Local handover duration: < 300 ms Change is not required.

Signaling before a Bearer before a Signaling after a Bearer after a
handover handover handover handover

Page44
NEs at the Access Layer
NE Name Function

eMSC server Helps ICS subscribers in a CS domain to register with an IMS domain
(mAGCF) and provides basic and supplementary services for them.

• S-GW in an EPC domain: serves as an anchor point for the user

plane between access networks in 3GPP. The S-GW is used as an
interface to screen different access networks in 3GPP.
S-GW/P-GW • P-GW in an EPC domain: serves as an anchor point between a
3GPP access network and non-3GPP access network. It provides
an interface for interworking between a 3GPP access network and
external PDN.

Implements mobility management for LTE subscribers, including

MME subscriber context and mobility status management, and temporary
identity distribution.

Page45
Interfaces in the IMS and CS domains and
Interworking

Page46
Interfaces for Accessing

Page47
Interfaces and Protocols on the VoLTE
Network Protocol
SIP
Purpose
SIP is used to control calls between IMS or CS NEs.
Diameter is used to exchange the subscription and authentication information
Diameter between the CSCF, the MME, and HSS. It is also used to exchange charging
information between the CCF/OCS and IMS NEs.
H.248 is used to exchange messages between the media gateway controller
H.248 (such as the MSC server, MGCF, and MRFC) and the media gateway (such as
MGW, IM-MGW, and MRFP).
MAP defines a means of information exchange among NEs to realize the
MAP
roaming function and SMS of UEs.
CAP is used between the SSP/IM-SSF and SCP to allow CS or IMS subscribers
CAP
to use traditional IN services.
ISUP is used for signaling interworking between MSC servers, and between the
ISUP
MSC server/anchor AS and the MGCF.
GTP-C is used to exchange messages between the MME, SRVCC-IWF, and S-
GTP-C
GW.
SGsAP is used to perform mobility management and paging processes of short
SGsAP
message services between an EPC domain and a CS domain.
HTTP HTTP is used to exchange messages between terminals and DMSs.

Page48
Interfaces and Protocols on the VoLTE
Network - SIP
Interface Location and Function Protocol
Located between the P-CSCF, I-CSCF, and S-CSCF, the Mw interface
is used for message exchange between CSCFs during IMS registration
Mw and session processes and also functions as a proxy. SIP
Located between the ATCF and S-CSCF/SRVCC-IWF, the Mw interface
is used to control eSRVCC.
The Mr interface is located between the CSCF and the MRFC. By using
the Mr interface, the S-CSCF obtains network resource-related services
Mr SIP
from the MRFC, including announcement playing, digit collection,
conference bridges, and video streams.
The Mi interface is located between the S-CSCF and the BGCF. When
the S-CSCF discovers that a session needs to be routed to the CS
Mi SIP
domain, it uses the Mi interface to forward the session to the BGCF so
that the BGCF can select an appropriate breakout to the CS domain.
The Mj interface is located between the BGCF and the MGCF. When
the BGCF receives session control signaling over the Mi interface, it
Mj selects an appropriate breakout to the CS domain. If the selected SIP
breakout is in the same network as the BGCF, the BGCF uses the Mj
interface to forward the session control signaling to the MGCF.

Page49
Interfaces and Protocols on the VoLTE
Network - SIP (Cont.)
Interface Location and Function
Protoco
l
The Mg interface is located between the I-CSCF and the MGCF. The
MGCF uses the Mg interface to forward session control signaling from
Mg SIP
the CS domain to the I-CSCF so that the CS domain can interwork with
the IMS domain.
The Mk interface is located between BGCFs. This interface is used to
forward session control signaling from the BGCF that resides in the
Mk SIP
same network as the originating S-CSCF to the BGCF that resides in
the same network as the MGCF.

The Mm interface is located between the CSCF and other IP networks.

Mm SIP
This interface supports IPv4 and IPv6 addresses.

The ISC interface is located between the S-CSCF and the AS. Based
on the iFC template data obtained from the HSS and SIP service
requests sent from an IMS UE, the S-CSCF determines whether to
ISC SIP
trigger a service. If the service needs to be triggered, the S-CSCF
routes the session request over the ISC interface to a specific AS for
final processing.

Page50
Interfaces and Protocols on the VoLTE
Network - SIP (Cont.)
Interface Location and Function Protocol
The Nc interface is located between the MSC server/anchor AS and
the MGCF and between MSC servers. The main functions of this
interface are as follows:
Nc ISUP/SIP
•Manages mobility and handover and provides interworking for CS
subscribers.
•Allows CS subscribers to be anchored in an IMS network.
The I2 interface is located between the mAGCF and the ATCF/I-
CSCF/S-CSCF. This interface is used between a CS network and an
I2 IMS network to allow CS subscribers to access an IMS network. This SIP
interface is also used to convert messages sent from the A/Iu-CS
interface to IMS SIP signaling messages.
The Gm interface is located between an IMS UE and the P-CSCF for
Gm SIP
registration and session control for IMS subscribers.

Page51
Interfaces and Protocols on the VoLTE
Network - Diameter
Interfac
e
Location and Function Protocol

The Cx interface is located between the CSCF and the IMS-HSS. The
CSCF and the IMS-HSS use the Cx interface to perform the following
operations:
• The I-CSCF queries the IMS-HSS for information required for selecting
an S-CSCF.
Cx • The CSCF queries the IMS-HSS for routing information. Diameter
• The CSCF queries the IMS-HSS for roaming authorization information.
• The CSCF downloads from the IMS-HSS security parameters required
for IMS subscriber authentication.
• The IMS-HSS sends iFC data associated with the IMS session to the
CSCF.
The Dx interface is located between the CSCF and the SLF. If multiple
HSSs are deployed on an IMS network, the CSCF uses the Dx interface
Dx Diameter
to query the SLF for the HSS that stores subscription data of a subscriber.
The Dx interface is not required when only one HSS is deployed.
The Sh interface is located between the IMS-HSS and the SIP AS. The
Sh SIP AS uses the Sh interface to query the IMS-HSS for value-added Diameter
service data and to synchronize data to the IMS-HSS.

Page52
Interfaces and Protocols on the VoLTE
Network - Diameter (Cont.)
Interface Location and Function Protocol

The Dh interface is located between the SLF and the SIP AS. The AS
Dh uses the Dh interface to identify the HSS that stores subscriber data Diameter
based on the subscriber identity and home domain information.

The Rf interface is located between the CCF and other entities such as
Rf the CSCF, MRFC, BGCF, and AS. This interface is used for session- Diameter
related offline charging.
The Ro interface is located between the OCS and other entities such as
Ro the AS, MRFC, and OCG. This interface is used for session-related Diameter
online charging.
The Rx interface is located between the PCRF and the application entity
such as the P-CSCF. The Rx interface is used for session information
exchange at the application layer. Based on the session information, the
Rx Diameter
PCRF determines the policies and charging control schemes to be used.
The PCRF exchanges the decided policies and charging control
schemes with the PCEF.

Page53
Interfaces and Protocols on the VoLTE
Network - Diameter (Cont.)
Interface Location and Function Protocol
The Gx interface is located between the PCRF and the PCEF (such as
the P-GW). The PCRF uses the Gx interface to deliver charging policies
Gx Diameter
to the PCEF, and the PCEF uses the Gx interface to report bearer events
to the PCRF.
The S6a interface is located between the MME and the SAE-HSS. This
S6a interface is used to transmit subscription and authentication data for Diameter
authorized subscribers to access the EPC network.

Page54
Interfaces and Protocols on the VoLTE
Network - H.248
Interface Location and Function Protocol

The Mp interface is located between the MRFC and the MRFP. The
Mp MRFC uses the interface to control the MRFP for announcement H.248
playing, conferences, and DTMF digit collection.

The Mn interface is located between the MGCF and the IM-MGW. The
Mn MGCF uses the Mn interface to control media streams transmitted on H.248
the IM-MGW and allocation of special resources.

The Mc interface is located between the MSC server and the MGW. The
Mc MSC server uses the Mc interface to control media streams transmitted H.248
on the MGW and allocation of special resources.

Page55
Interfaces and Protocols on the VoLTE
Network - MAP
Interface Location and Function Protocol
The E/Gd interface is located between the IP-SM-GW and the SMSC for
E/Gd MAP
SMS interworking between an IMS network and a CS domain.
The E interface is located between the MSC server and the SMSC for
E MAP
SMS interworking.
The Si interface is located between the IM-SSF and the HLR and is used
Si MAP
to obtain IN service information about subscribers.
The J interface is located between the IP-SM-GW and the HLR and is
J MAP
used to obtain the routing information about short messages.

The C/D interface is located between the MSC server/MGCF/SMSC and

the HLR. The MSC server/SMSC and the HLR use the C/D interface to
perform the following operations:
• The MSC server and SMSC query the HLR for routing information.
C/D • The MSC server sends a location update request to the HLR. MAP
• The MSC server and the MGCF query the HLR for the roaming
numbers and subscription information about subscribers.
• In the convergent HLR/HSS anchoring solution, the HLR uses this
interface to obtain the IMRN from the MGCF.

Page56
Interfaces and Protocols on the VoLTE
Network - GTP-C
Interface Location and Function Protocol

The S11 interface is located between the MME and the S-GW. The MME
and S-GW use the S11 interface to transmit bearer setup, update, and
S11 GTP-C
deletion messages. When a UE is in the ECM-IDLE state, the S-GW
instructs the MME to page the UE to restore the S1 bearer.

The Sv interface is located between the MME and the SRVCC IWF to
Sv GTP-C
control the eSRVCC handover.

Page57
Interfaces and Protocols on the VoLTE
Network - CAP/HTTP/SGsAP
Interface Location and Function Protocol

The CAP interface is located between the MSC server/IM-SSF/anchor

AS and the SCP. The CAP interface allows CS or IMS subscribers to use
CAP CAP
traditional IN services and CS subscribers to be anchored in an IMS
network.

The HTTP interface is located between a UE and the DMS. The terminal
HTTP uses the HTTP interface to perform self-help upgrade and fault HTTP
diagnosis.

The SOAP interface is located between the SPG and the AS/HSS. The
SOAP SPG uses the SOAP interface to deliver commands that are run on the HTTP
SPG2800 web portal to the AS or HSS.

The SGs interface is located between the MME and the CSFB MSC
server/CSFB proxy. The SGs interface is used to perform mobility
SGs SGsAP
management and paging procedures between an EPC domain and a CS
domain in the CSFB scenario.

Page58