DEEKSHA TECH GROUP

Module 15

VoLTE Architecture
 Agenda
Introduction to VOLTE .
VOLTE Radio Bearers.
VOLTE Architecture.
IMS/SIP Signaling.
Different VoLTE Call Flows
INTRODUCTION TO VOLTE
LTE is a packet only architecture designed to improve data
performance . It does not support CS voice or Video call.
In order to accommodate voice on LTE , two approach were
taken i.e. CSFB (Circuit Switch Fall Back) and VOLTE (Voice
over LTE)
GSMA voice over LTE has evolved as a preferred standard for
a telephony solution in LTE that has been accepted by the
operator community .
GSMA has defined Voice over LTE (VOLTE) in PRD IR.92;
describing minimum set of requirements for delivering voice
in an all IP environment based on existing 3GPP IMS based
Multimedia telephony solution.
VOlTE Brief
First VoLTE Aug 2012 in South Korea
First HD voice and video calling in 2013 at china
VoLTE is simple and reliable
VoLTE provides better voice quality than other mobile
communication
VoLTE reduces operator OPEX
Voice-carried over LTE NW
QoS Better QoS over the VoIP
QoS Wide band codec
Capacity One of the issues with voice over IP type calls is the
overhead resulting from the IP header
Capacity VoLTE supports Robust Header Compression (ROHC) of
RTP header
Capacity less signaling overhead
VOLTE END-TO-END (SIMPLIFIED VIEW)

Mobile Originator : A Mobile Terminator: B

VOLTE RADIO BEARER SETUP
VoLTE Architecture
VoLTE Evolution
VoLTE introduction with SR-VCC and
ICS
 SRVCC
Single Radio Voice Call Continuity SR-VCC according to 3GPP TS
23.216 [6] provides IMS voice call continuity for the conversational
QCI1 VoIP bearer from E-UTRAN to CS access in UTRAN or GERAN.
Additionally, SR-VCC coordinates the handling of the voice session
and possible parallel ongoing PS sessions.
SR-VCC introduces the Sv interfaces between MME and anchor
MSC. The new SCC-AS in the IMS network is linked into every IMS
voice call (based on triggers in HSS). In case of SR-VCC HO, the MME
coordinates the HO for
voice using the Sv towards the anchor MSC and for other PS bearers
over S3 or Gn towards SGSN.
The anchor MSC/MGCF serves as SIP user agent for the UE when
the UE is in the CS domain. It coordinated the session transfer in
IMS over the Mg interface and the CS HO towards the UTRAN or
GERAN.
SRVCC
 ICS (IMS Centralized Services)
IMS Centralized Services (ICS) provides mechanisms to support the
use of CS media bearer for IMS sessions. With ICS, IMS sessions
using CS media are treated as standard IMS sessions for the
purpose of service control and service continuity.
In short, ICS is about centralization of voice and SMS services in a
homogenous network, where VoLTE will have less coverage than
CS network (2G/3G).
Two underlying drivers for IMS Centralized Services:
Homogeneous service experience in a Heterogeneous
network, where VoIP will have less coverage than CS access.
Service interaction and service enhancement easier to do in
a single service engine, providing consistent service experience
to end users.
 CSFB
Emergency Call fallback to CS for early VoLTE deployments
Voice Network Architecture 2G Vs. VoLTE
 IMS Network Architecture Voice, Video & Messaging Services

MNP Porting Traffic

MNP GW MNP DB

Subs Provisioning
Provisioning HSS
Signaling Traffic
Other
IMS MGCF Operator
s

E1
SBC MGW Interconnect
Charging Traffic ( VVMS) ( ISUP)

Billing LIS
Charging Traffic (HSI) EPC LCS
(For Location
information)
EPC- Evolved packet core
IMS- IP multimedia system
SBC- Session Boarder controller Access Network
MGCF- Media GW controller Signaling Traffic
MGW- Media Gateway eNB Bearer Traffic
LIM Lawful interception System
HSS Home subscriber system
LCS- Location system Reliance Jio Infocomm Limited
BEARER MANAGEMENT FOR QOS
Each QCI (QoS Class Identifier) is related to
certain transport characteristics .
Out of 256 possible QCIs , 9 of them have been
standardizes
 IMS to IMS VoLTE Call Flow
P-CSCF/SAE- S-CSCF TAS I-CSCF S-CSCF TAS P-CSCF/SAE- UE -
UE-A HSS GW(A)
GW(A) (A) (A) (A) (B) (B) B
INVITE

MNP

INVITE
Location
Retrieval

INVITE

183
(SDP)

PRACK
200 OK(PRACK)

180 Ringing

200 OK

200 OK ACK is not shown

Call is answered, RTP session setup between UE-A and UE-B

RTP RTP RTP

 IMS to CS Core MO Call Flow
P-CSCF/SAE- TAS I- MGCF/ PSTN
UE-A GW(A) S-CSCF BGCF
(A) CSCF GMSC (B)
INVITE

MNP
Based on LRN BGCF
selects MGCF. S-
CSCF and BGCF are INVITE
collocated in actual
deployment. IAM
183
(SDP)
ACM
180 Ringing

200 OK ANM

ACK

Call is answered, RTP session setup between UE-A and UE-B

TAS I- BGC MG PST

UE-A UAG S-CSCF
(A) CSCF F W N (B)

RTP RTP TDM

 CS Core to IMS MT Call Flow
UE-B P-CSCF/SAE- S-CSCF TAS I- MGC MSC
HSS
GW(A) (B) (B) CSCF F (A)
IAM (MSISDN)

MNP MGCF performs

MNP dip for
screening & based
on LRN, decides to
INVITE(MSISDN) route to RJIO IMS
or another network
Location
Retrieval
INVITE(MSISDN)

INVITE

183 Session Progress (SDP) Default RBT by

MGCF
PRACK

200 OK (PRACK)

180 Ringing ACM

200 OK (INVITE) ANM

ACK (200
OK)
Call is answered, RTP session setup between UE-A and UE-B

UE-A TAS I- BGC MG PST

UAG S-CSCF
(A) CSCF F W N (B)

RTP RTP TDM

IMS to CS Core MO SMS Flow
IMS to CS Core MT SMS Flow
VoLTE Roaming Architecture
Inter Circle Roaming Scenario
Emergency Call Flow
Thank you