4.introduction To The VoLTE Solution ISSUE7.02

Introduction to the
VoLTE Solution
www.huawei.com
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

Reference
 VoLTE Product Documentation
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page1
Objectives
 Upon completion of this course, you will be able to

understand:
 VoLTE solution basic concepts
 VoLTE solution architecture
 VoLTE evolution trend
 Huawei VoLTE solution products and deployment principles
Contents
1. VoLTE Solution Basic Concepts
2. VoLTE Network Evolution
3. Huawei VoLTE Solution Architecture
4. Huawei VoLTE Solution Products
Contents
1.1 Commercial LTE Voice Solutions
1.2 Advantages of VoLTE
1.3 Key Technologies Involved in VoLTE
Commercial LTE Voice Solutions
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.
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
2G/3G 2
LTE the normal terminating flow.
Fallback MSC server 1 MME
 Originating side CS SGs EPC

 The UE sends a voice call request to the
4 2
MME. The MME then instructs the UE to
fall back to the 2G or 3G network.
 The UE falls back to the 2G or 3G network. 2G/3G LTE
3
 The UE initiates a call based on the normal Fallback
originating flow on the 2G or 3G network.
Page7
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
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.
Contents
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.
Three Forces to Drive VoLTE/RCS driving force
investigation result
(159 participants in the IMS
VoLTE Development summit in April 2011)
1. Competing with OTT 2. User experience 3. Unifying the network and

(real driving force) 33.33% (permanent driving force) 30.19% reducing TCO
(long-term driving force) 26.42%
• The LTE network features high • HD voice •The spectral efficiency of LTE
bandwidth, low delay, all IP, and • HD video session voice services increases over four
always online, which facilitates OTT
application development. • Faster call connection times compared with that of CS
• IMS-based multimedia voice • Rich multimedia communication voice services.
services and RCS serve as carriers' experience (IM/Presence •Number of voice channels per
main competitive sources. service/enhanced address book) sector
• VoLTE provided by carriers •Source: Qualcomm
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
The time for setting up a VoLTE call
broadband
is half that for setting up a 3G call.
• Fault troubleshooting and
customer care
.
Better communication Faster connection Richer Higher spectral
quality rate services efficiency
Advantage of VoLTE – Better and Faster
Better Faster Richer Higher
communication connection rate services spectral
quality efficiency
 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.
Contents

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.
IMS-based Voice Services
PCRF
MME
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.
VoLTE Basic
Call
 A dedicated
bearer for IMS
voice media
streams is set
up during call
connection
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.
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.
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.
eSRVCC Vs SRVCC
before
SRVCC eSRVCC
E2E media re-establish after
Local media establish
LTE IMS/SBC
IMS/SBC LTE
RAN （ATCF & RAN
ATGW）
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.
ICS Definition (Cont.)
ICS Architecture
 The ICS solution becomes the
best choice for evolution from Service layer AS AS AS
the mobile softswitch to IMS.
Centralized service
The eMSC server functions as trigger point
IMS Core
a SIP UA and connects
subscribers to the IMS Core.
 MSC server enhancements for
ICS, the MSC server that Access layer
supports the ICS feature, is MSC server
mAGCF
xPON
called mobile access gateway and FBB
control function (mAGCF). In MGW
this document, the MSC
server enhancements for ICS 2G/3G
LTE
is called eMSC server.
LTE subscriber
CS subscriber
Contents
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
CPE
 Deployment suggestions:  Deployment suggestions:
 CSFB  IMS-based VoLTE voice
 Deployment suggestions:
 CPEs subscribe to IMS-
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
Evolution to IMS/SRVCC/ICS
The live network

solution evolves to
ICS in the following
Live network MSC servers
ways:
Deploy the SRVCC IWF/MGCF. • Evolution from
deployment of the
overlay eMSC
server to ICS
MSC servers
• Direct Evolution to
ICS
Enhanced with the mAGCF/SRVCC IWF
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 servers
Deploy MSC servers to serve as CSFB proxies. Enhanced with the SRVCC IWF/MGCF

Contents
Contents

3.1 VoLTE Layered Network Architecture
3.2 VoLTE Key NE Functions
3.3 VoLTE Interface and Protocol
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
(MMtel AS/SCC AS/IP-
SM-GW/IM-SSF/Anchor provide services, such as instant messaging,
AS) conferences, games, as well as service
capabilities, such as group and media resource
capabilities.
 NEs: ATS and RCS
Core Layer
 The core layer is divided into the following
Core layer
three 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.
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
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
Contents

3.2 VoLTE Key NE Functions
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.
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.
NEs at the Service Layer - ATS
3GPP Mobile TISPAN Business
MMTel special PSTN service
 The ATS provides service service service
traditional mobile services
and multimedia services.
ATS
(MMTel + SCC AS + IP-SM-GW
+ IM-SSF + anchor AS)
IMS network
MBB FBB PSTN

Mobile Soft SIP
CPE
terminal 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.
NEs at the Service Layer - SCC AS
(ATS)
 The service centralization and continuity application SCC AS
server (SCC AS) implements handovers in the IMS ISC
domain and updates the media information about the
IMS Core
remote UE. In 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 Calling access
network and the UMTS connection 2
GERAN
network. UMTS Media connection 2
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.
NEs at the Service Layer - IP-SM-GW
(ATS)
 The IP short message gateway (IP-SM-
GW) provides short message OCS CGF/CDF
interworking between IMS and CS
Ro Rf
domains. 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 1 SIP message
UEs.
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.
NEs at the Service Layer - Anchor AS
(ATS)
AS
The anchor AS anchors calls from the
CS network to the IMS network as IMS
Anchor AS
follows:
CS MSC server
 Routes VoLTE subscribers' calls to
the IMS domain to trigger convergent
services by IN-based number VoLTE subscriber
redirection of the anchor AS, when
the VoLTE subscribers originate or
receive a call in the CS domain. IMS
Anchor AS
 Routes VoLTE subscribers' calls to
CS MSC server
the IMS domain by IN-based number
redirection of the anchor AS, when
LTE
the VoLTE subscribers receive calls
VoLTE
from CS subscribers. subscriber
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
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.
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.
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.
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
SCC AS
SRVCC IWF changes the 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 eMSC server
CS (SRVCC IWF) Sv EPC
server or deployed as a
standalone entity. If the
SRVCC IWF is deployed as
a standalone entity, it
MSC 2 Selects target MSC
functions as a proxy of the
MSC
MSC server and performs SRVCC IWF MME UE
MSC
conversion for signaling
MSC
messages between the 1 Handover request
MSC server, SBC, and MME.
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
IMS Core SCC AS Remote UE
Handover
ATCF
LTE
PS ATGW SBC
Local handover duration: < 300 ms Change is not required.

Signaling before a Bearer before a Signaling after Bearer after a
handover handover a handover handover
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.
Contents

3.2 VoLTE NE Functions
Interfaces in the IMS and CS domains
and Interworking
Interfaces for Accessing
Interfaces and Protocols on the
VoLTE
Protocol
Network
Purpose
SIP 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.
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.
VoLTE Network - SIP (Cont.)
Protoco
Interface Location and Function
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.
VoLTE Network - SIP (Cont.)
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.
VoLTE Network - Diameter
Interfac
Location and Function Protocol
e
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.
VoLTE Network - Diameter (Cont.)
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.
VoLTE Network - Diameter (Cont.)
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.
VoLTE Network - H.248
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.
VoLTE Network - MAP
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.
VoLTE Network - GTP-C
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.
VoLTE Network - CAP/HTTP/SGsAP
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.
Contents
Huawei VoLTE Solution
Application server Legacy service
O&M
ATS
Presence/IM/DS/XDMS
(MMTel AS/SCC AS/IP-SM-GW/Anchor AS/IM
RCS9880 SCP
SSF)
EMS Convergent SDB ATS9900
IMS Core
iManager
Legacy
M2000
network
MGCF
I-CSCF/S- MSOFTX3000
Provisioning HLR/IMS-HSS/SAE-HSS CSCF/MRFC
MRFP IM-MGW
GW /ENUM /DNS CSC3300
MRP6600 UMG8900
SPG2800
SBC
CS
CCF (P-CSCF/A-BCF/A-BGF/ATCF/ATGW/E-CSCF)
iCG9815 eMSC server SE2600/SE2900
(SRVCC-IWF/CSFB proxy)
MSOFTX3000 EPC
DMS
TMS9950 MGW MME S-GW/P-GW PCRF
UMG8900 USN9810 UGW9811 UPCC
2G/3G 2G/3G LTE LTE
Terminal LTE handset LTE CPE LTE data card + software client
Huawei VoLTE Solution Products
Layer NE Product
DMS TMS9950
Operation SPG SPG2800

support layer CCF iCG9815
EMS M2000/U2000
ATS ATS9900
Service layer IM-SSF ATS9900
RCS AS RCS9880
(Cont.)
Layer NE Product
Convergent HLR/HSS HSS9860
DNS/ENUM HSS9860
eMSC server (SRVCC IWF/CSFB
MSOFTX3000
proxy)
MGCF MSOFTX3000
Core layer Anchor AS ATS9900
MRFP MRP6600
I/S-CSCF/BGCF/MRFC CSC3300
P-CSCF/SBC/ATCF/ATGW SE2900
MGW/IM-MGW UMG8900
(Cont.)
Layer NE Product
eMSC server (mAGCF) MSOFTX3000
Access
S-GW/P-GW UGW9811
layer
MME USN9810
High Integration
SE2900
Unified Network Management
 The M2000/U2000 is deployed to manage all NEs in IMS, CS, and EPC networks in a unified
manner. The M2000/U2000 functions include monitoring alarms and collecting NE performance
data. With the M2000, operators can monitor, configure, and maintain the entire network
conveniently.
SPG for Unified Service Provisioning
 Service provisioning through the
BSS:
 The BSS sends service requests
over the northbound interface on
the SPG2800.
 The SPG2800 performs ACL
and user authentication and
checks message services.
 After the authentication and
check are successful, the
SPG2800 forwards commands
to the associated NEs for
processing.
 After the processing, the
SPG2800 returns responses to
the BSS.
Typical VoLTE Network Deployment Scenario
VoLTE Commercial Deployment key
Points
 Major network upgrade/re-construction point:
 Convergent HSS (EPC HSS/IMS HSS/HLR) deployment
 Core network(IMS/CS/EPC) upgrade/new deployment
 4G PCC (PCRF) upgrade/new deployment
 IP bearer network/service platform
 Diameter signaling network(DRA) deployment
 BSS/EMS upgrade
Convergent HSS Construction
Scenarios
Database Construction Solution Card Type Policy
The newly deployed convergent HSS\HLR coexists with the HLR on
New card and new
the live network. VoLTE subscribers use new cards and new USIM card
number segment
number segments.
New card and old
SIM card
number
The convergent HSS\HLR replaces the HLR on the live network.
Old card and old
USIM card
number segment
New card and old

The newly deployed convergent HSS\HLR coexists with the HLR on SIM card
number segment
the live network. VoLTE and 2G/3G subscribers use the same
Old card and old
number segments. The STP provides the FNR function. USIM card
number segment
The newly deployed convergent HSS\HLR coexists with the HLR on New card and old
SIM card
the live network. VoLTE and 2G/3G subscribers use the same number segment
number segments. The convergent HSS\HLR provides the FNR Old card and old
USIM card
function. number segment
Solution 1: The Newly Deployed Convergent HSS\HLR
Coexists with the HLR, and VoLTE Subscribers Use
New Cards and New Number Segments
 Solution description
BSS  Carriers allocate new IMSI and
MSISDN number segments to VoLTE
Stores data of only VoLTE
Stores data of only subscribers.
subscribers who use new
2G/3G subscribers.
IMSIs and MSISDNs.  The newly deployed convergent
Convergent
HLR HLR/HSS HLR/HSS stores data of subscribers
using new number segments. A
subscriber from the IMS, CS, and PS
domains can access an LTE
subscriber's data.
MSC server SGSN MME IMS Core  GTs for new IMSI/MSISDN number
segments are configured on the MSC
server and SGSN. Messages are
routed to the newly deployed
HLR/HSS.

Replaces the HLR on the Live Network
BSS  The newly deployed HLR/HSS stores
data of 2G, 3G, 4G subscribers. A
Stores data of all subscriber from the IMS, PS, and CS
subscribers. domain can access the data.
Existing Reconstruction Convergent HLR/HSS Subscriber data stored on the HLR
HLR
on the live network is migrated to the
newly deployed convergent
HLR/HSS. Huawei HLR V900R006
or later can be upgraded to the
MSC server SGSN MME IMS Core convergent HLR/HSS.
 The MSC and SGSN on the live
In this solution, only SIM cards need to be changed. network update all routes and store
them in the convergent HLR/HSS.
Coexists with the HLR, and VoLTE and 2G/3G
Subscribers Use the Same Number Segments
BSS
 The newly deployed convergent HLR/HSS
Stores data of only Stores data of only manages 4G subscriber data. New VoLTE
2G/3G subscribers. Adds migration VoLTE subscribers.
information
subscribers can be defined on the
about VoLTE convergent HLR/HSS. Data of 2G/3G
HLR subscribers.
Convergent HLR/HSS subscribers who have subscribed to 4G
services is migrated from the HLR to the
STP/SRF convergent HLR/HSS. If 2G/3G subscribers
do not subscribe to 4G services, their data
is still stored in the HLR.
 Routing data for IMSIs and MSISDNs are
MSC server SGSN MME
configured on the STP and SRF. If
IMS Core
subscribers have subscribed to 4G services,
messages are routed to the convergent
In this solution, only SIM cards need to be changed. HLR/HSS. If subscribers do not subscribe
to 4G services, messages are routed to the
old HLR.
Summary
 This course describes:
 VoLTE solution basic concepts
 VoLTE network evolution
 Huawei VoLTE solution architecture and NE functions
 Huawei VoLTE solution products and deployment solutions
Acronyms
VoLTE voice over long term evolution
CSFB circuit switched fallback
SVLTE simultaneous voice and LTE
OTT over-the-top
CTAS common telecom application server
T-ADS terminating access domain selection
EPC evolved packet core
MO mobile originating
MT mobile terminating
LTE Long Term Evolution
IMS IP multimedia subsystem
SAE system architecture evolution
SMS short message service
UE user equipment
RCS Rich Communication Suite
IM instant message
ICS IMS centralized service
SRVCC single radio voice call continuity
eSRVCC enhanced single radio voice call continuity
SCC AS Service Centralization and Continuity Application Server
HSS home subscriber server
Acronyms (Cont.)
MME mobility management entity
PS packet switched
CS circuit switched
ATCF access transfer control function
ATGW access transfer gateway
mAGCF mobile access gateway control function
AGCF access gateway control function
CSCF call session control function
S-CSCF serving-call session control function
P-CSCF proxy-call session control function
I-CSCF interrogating-call session control function
MRFC multimedia resource function controller
MFFP multimedia resource function processor
MGCF media gateway control function
AS application server
BGCF breakout gateway control function
NAB Network Address Book
CAB Convergent Address Book
Thank you
www.huawei.com

4.introduction To The VoLTE Solution ISSUE7.02

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

4.introduction To The VoLTE Solution ISSUE7.02

Hochgeladen von

Copyright:

Verfügbare Formate

Introduction to the

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be able to

 VoLTE solution architecture

 VoLTE evolution trend

 Huawei VoLTE solution products and deployment principles

2. VoLTE Network Evolution

3. Huawei VoLTE Solution Architecture

4. Huawei VoLTE Solution Products

1.1 Commercial LTE Voice Solutions

1.2 Advantages of VoLTE

1.3 Key Technologies Involved in VoLTE

Fallback MSC server 1 MME

 Originating side CS SGs EPC

Voice service Data service

 The OTT solution cannot provide E2E QoS guarantee.

 Roaming and interconnection are hard to be implemented due to lack of standards.

1.1 Commercial LTE Voice Solutions

1.2 Advantages of VoLTE

1.3 Key Technologies Involved in VoLTE

1. Competing with OTT 2. User experience 3. Unifying the network and

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

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

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

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

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

Dedicate bearer for VoLTE

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

QCI: QoS class identifier GBR: guaranteed bit rate

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

VoLTE HD voice and video RCS embedded

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

1. VoLTE Solution Basic Concepts

1.2 Advantages of VoLTE

1.3 Key Technologies Involved in VoLTE

 ICS for VoLTE

 Method: Media and signaling

First eSRVCC testing (Vienna 201210)

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

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

2. VoLTE Network Evolution

3. Huawei VoLTE Solution Architecture

4. Huawei VoLTE Solution Products

Pre-VoLTE Initial commercial use Large-scale commercial

based VoIP voice services.  eSRVCC

media RCS services. SingleSDB  IMS roaming and

 LTE-based rich media RCS

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

The live network

Enhanced with the mAGCF/SRVCC IWF

Enhanced with CSFB

MSC servers VoLTE (overlay eMSC server)

MSC servers MSC servers

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

2. VoLTE Network Evolution

3. Huawei VoLTE Solution Architecture

4. Huawei VoLTE Solution Products

3. Huawei VoLTE Solution Architecture

3.2 VoLTE Key NE Functions

3.3 VoLTE Interface and Protocol

3. Huawei VoLTE Solution Architecture

3.2 VoLTE Key NE Functions

3.3 VoLTE Interface and Protocol