4 - Call Flow PDF

Call Flow
4 rth February 2015
2015 Samsung Electronics
Table of contents
Network Elements
Network Overview
Scenarios
VoLTE Basics
VoLTE Call Flow
Network Architecture
ENB Interface and Protocol

The Protocols that run between UE and
eNB are called Access Stratum Protocols or
AS Protocols
The Protocols that run between UE and
Core Network are called as NAS Protocols
or Non Access Stratum Protocols
MME Interface and Protocol
MME Interface and Protocol
SAE GW Interface and Protocol
SAE GW Interface and Protocol
IP Packet is tunneled between P GW and UE using GPRS Tunneling Protocol GTP

Each Bearer has associated QCI
Each QCI has GBR/ Non GBR, Priority, packet delay , Packet Error Rate defined
PCRF decides the Bearer Type
P GW performs the DHCP functionality = allocates IP addresses to each UE
VoLTE Logical Architecture

ENUM Electronic Number Mapping System
To translate a telephone number into IP address
VoLTE Logical Architecture
10
RJIL Network Overview
11
LTE reference model

NODE
DESCRIPTIONS
eNB
Radio interfaces and radio resource management.

Radio bearer control/radio admission control/scheduling of uplink & downlink/
IP header compression and encryption of the user plane data/eNB handover(X2)/pooling
between MMEs and eNBs(S1, many-to-many relations)
MME
LTE related control plane signaling

Mobility and security functions for devices attaching over the LTE RAN/Management of all the
terminals in idle mode including Tracking Area management and paging.
S-GW
Anchoring point for intra-LTE and between GSM/GPRS, WCDMA/HSPA and LTE/ Accounting
functions for inter-operator charging and billing settlements.
P-GW
Interconnection point to external IP networks. IP address allocation/charging/packet

filtering/policy-based control of user-specific IP flows
PCRF
Policy and Charging Rules Function Flow based charging, including e.g., online credit control and
policy control including service authorization and QoS management.
OCS/OFCS
Online Charging System / Offline Charging System
Samsung Confidential and Proprietary Information. All Contents Copyright 2011 Samsung Electronics Co., Ltd.
12
RJIL Network Architecture(LTE)
SAE-GW = S-GW + P-GW
13
Regional Sites (8 Super Core) Setup
14
14
Child Circle Parenting with Regional Sites

Haryana Circle EPC Nodes connecting to Delhi Super Core Nodes and its Geo Mate Kolkata
Super Core Nodes.
Similarly, Assam Circle EPC Nodes connecting to Kolkata Super Core Nodes and its Geo Mate
Delhi Super Core Nodes.
Child Circle
Local Circle
15
15
Basic VoLTE Network Architecture

IP
Network
LTE Network
HSS
EPC Network
PCRF
eNB
PSTN
PLMN
MME
S-GW
HSS
SGW
ENUM
MNP
MGCF
CSCF
VCC
MRF
TAS
MGW
P-GW
SBC
ePDG
IP-SMGW
IMS Network
eNB
WiFi AP
EPC
IMS (Minimum Set for VoLTE)
IMS
SBC : Session Border Controller

CSCF : Call Session Control Function
VCC : Voice Call Continuity
TAS : Telephony Application Server
IP-SM-GW : IP-Short Message-Gateway
MGCF : Media Gateway Control Function
MGW : Media GateWay
SGW : Signaling GateWay
MRF : Media Resource Function
HSS : Home Subscriber Server
MNP : Mobile Number Portability
16
RJIL Network Architecture(IMS)
17
PDN Connectivity & Attach

PDN connectivity a type of IP connection including QoS, charging, mobility, security, policy control
aspects, as such it is differentiated from the mere IP connection.
APN(Access Point Name): a character string that contains a reference to the PDN where the desired
services are available. The corresponding PGW is selected by the network based on the given APN.
18
QCI table
Dedicate
d
bearer
Persistent
Dedicated
bearer
Default
bearer
19
NW Architecture - Voice/Video Call over LTE

IMS
Network
LTE/EPC
Network
Dedicated bearer
for media
MME
CSCF
SIP Signaling
Voice (QCI 1)
UE
PCRF
TAS
QoS control
(Voice/Video service
info)
eNB
Video (QCI 2)
SAE
GW
RTP
Voice/Video
BGW
Bearer
Use the same architecture/procedure/protocol with VoLTE
Traffic
SIP for Signaling using default bearer with QCI-5
Difference with VoLTE

Usage of two dedicated bearers
One for voice (QCI-1) and the other for video (QCI-2)
Codec used for video : H.264 (H.263 also used in normal commercial network)
20
Network Identities
21
Identities Used in LTE - GUTI

GUTI Globally Unique Temporary UE Identity - is assigned only by the MME during
initial attach of a UE to the E-UTRAN masks the true identity of the subscriber
GUTI provides an unambiguous identification of the UE that does not revel the UEs
permanent identity. It also allows identification of the MME and Network to which
UE attaches
GUTI has to main components - GUMMEI Globally Unique Mobility management
Entity Identifier and the M TMSI that uniquely identifies the UE within the MME
For paging, the mobile is paged with the S-TMSI which is a shorter version of GUTI
On the S1 Interface, the IMSI is typically not seen just like the GUTI. Exceptions are
initial attach when no old GUTI is stored on the USIM card or in paging procedure
22
Identities Used in LTE - RNTI

RNTI Radio Network Temporary Identifier
RNTI is signaled in the MAC Layer. When MAC uses the PDCCH to indicate radio
resource allocation, the RNTI is mapped on the PDCCH depends on the logical channel
type C- RNTI : Temporary Cell Radio Network Temporary Identifier for Dedicated Control Channel
(DCCH and DTCH). It defines which data sent in DL belongs to a particular subscriber all RRC
messages are marked with same C RNTI for a subscriber
P- RNTI : Paging Radio Network Temporary Identifier for Paging Control Channel (PCCH) is
derived from IMSI. It does not refer to a particular UE but to a group of UEs.
RA- RNTI : Random Access Radio Network Temporary Identifier for Random Access Response
(RAR) on DL-SCH assigned to particular UE and is contained in the response from eNode B
for PRACH. The UE then uses this RA- RNTI to send RRC Connection Request
Temporary C-RNTI for Common Control Channel (CCCH) during random access procedure
SI- RNTI : System Information Radio Network Temporary Identifier for Broadcast Control
Channel (BCCH) sent on PDCCH - it signals to all UEs where SIBs are found on PDSCH
RNTI Values
23
LTE Identities
24
Bearers
25
LTE Identifiers
26
UE Temporary IDs at different interfaces
27
S1AP Interface
In between eNB and MME, the User can be identified using the S1AP IDs.
eNB-UE-S1AP ID is the S1AP ID terminating at the eNB side
MME-UE-S1AP ID is the S1AP ID terminating at the MME Side.
28
GTP Teids
GTP-C Teids (S11 MME GTPC Teid and S11/S4 SGW GTPC Teid) are used as the control
plane teids at MME and GW respectively.
GTP-U Teids(S1-U eNB GTPU Teid and S1-U SGW GTPU Teid) are used as the user
plane teids at eNB and GW respectively.
29
Diameter Session ID
Gx Diameter Session Id can be used to identify the diameter packets related to a
particular subscriber session.
Gx diameter session Id will be created when the session is created for the subscriber
and will stay till the session is available.
30
Scenarios
31
Packet Data Flow in LTE
32
IMS (Schematic Architecture)
33
3G UMTS Interworking
S3 : MME to SGSN
S4: SGW to SGSN
1. LTE natively supports VoIP only using IMS services

2. LTE also supports CSFB Circuit Switched Fallback mechanism which allows CS voice calls
to be handled via legacy RAT (Radio Access Technology) for UEs that are camped on LTE
3. This is supported by SGs interface between MME and MSC. This allows the UE to attach
to the MSC and register for CS services while still in LTE. It also carries paging messages
from the MSC so that UE can be paged over LTE
4. The Network may choose a handover, cell change order or redirection procedure to
move UE to the legacy RAT
5. The UE moves to CS services on initiating a CS voice call
34
CSFB and SRVCC

CSFB is a solution for networks that do not have support for IMS VoIP.
The Voice Calls are handled by the CS domain and the UE is handed over at the time of a
voice call. The MME maps the Tracking Area to the Location Area.
Challenge is Call Set Up delay
SRVCC is a solution for converting and handing over an IMS VoIP call to a CS voice call
without interrupting the call when coverage of LTE is not there with handover interruption
time of less than 300 ms
SRVCC is a one way handover from LTE to UTRAN/GERAN and the UE may return to LTE
when reaching idle state
The solution relies on running only one radio at a time i.e. the UE may not communicate
with both the Networks.
In this solution the MME is connected to the MSC via a Sv interface which is used for
control signaling in the SRVCC handover
SVLTE Simultaneous Voice and LTE handset works simultaneously in LTE and circuit
switched mode LTE provides data services and circuit switched mode providing voice
services the mobile phone has high power consumption as two radios run together
One additional approach not initiated by operators is usage of OTT services Over the Top
Content Services like Skype / Google Talk
Additional Interfaces required for
2015interworking
Samsung Electronics with Legacy CS Networks
35
OTT and VoLTE

Over the Top (OTT) communication solutions such as Skype
cannot provide fully satisfactory user experience as there are no QoS measures in place
There is no handover mechanism to circuit switched network
No wide spread interoperability of services between different OTT services and devices
No guaranteed emergency support or security measures
Cannot provide services like HD Voice
VoLTE has the following advantages Operators can make use of wider capabilities of IP based networks to deliver high capacity
and inter operable communication services
Can provide HD Voice, Video calling, HD conferencing, IP messaging and contact
management
Can provide guaranteed end to end QoS, support for emergency services and regulatory
services, global interoperability and mobility, interconnect and international roaming
Can have fallback options to circuit switched networks
36
Message Flow for CSFB Call
Figure shows message flow for a CSFB call from LTE to UMTS including paging from the
MSC via the SGs interface and MME for UE terminated calls and the sending of an
Extended Service Request NAS message from the UE to the MME to trigger either a
handover or redirection to the target RAT for UE originated call.
37
CSFB
38
SRVCC
39
E UTRAN Connections
Connections after handover to

UTRAN/GERAN
Connections via E-UTRAN
Figure also shows the reference points for inter RAT handover between E-UTRAN,
UTRAN and GERAN
40
SRVCC Single Radio Voice Call Continuity

If ubiquitous coverage of LTE is not available, it is possible that a UE involved in VoIP call
over LTE might then move out of LTE coverage to enter legacy RAT which offers CS voice
services
The SRVCC is designed for handover of a PS Packet Switched VoIP Call over LTE to a CS
voice call involving the transfer of a PS bearer into a CS bearer
The eNode B detects UE is moving out of LTE coverage and triggers a handover
SRVCC is used for handover from PS VoIP Call to CS Voice Call
41
E-UTRAN with roaming
42
VoLGA
VoLGA Voice over LTE via Generic Access Standards
Most Operators preferred VOLTE
The lack of software support in initial LTE devices as well as core network devices led to a
number of carriers promoting VoLGA as an interim solution

The idea was to use same principles as GAN Generic Access Network also known as UMA
or unlicensed mobile access which defines the protocols through which a mobile handset
can perform voice calls over a customers private internet connection usually over
wireless LAN
VoLGA however never gained much support because VoLTE promises much more flexible
services
43
WiFi Calling
WiFi Calling needs to be enabled both in the device and in the network
New integrated functionality in the EPC with the ePDG Evolved Packet Data Gateway
in needed to allow untrusted non-3GPP accesses to interwork with the EPC and
connect to the IMS Network
The ePDG provides security mechanism such as IPsec tunneling of connections
44
Video Calls over LTE

Video Calling
45
SMS Over LTE

There are two options to deliver SMS services over LTE via the existing Short Message
Service Center SMS-C
SMS over SGs the device sends and retrieves circuit switched based SMS messages - uses
SGs interface between MSC and MME. The device will not fall back to GSM/WCDMA while
sending or receiving messages. For SMs over SGs the existing roaming/interconnect
agreements may be reused.
SMS over IP - the device sends and retrieves SIP packet switched SMS messages - the
solution requires an SMS client that uses IMS and SIP stack , an IP Short Message Gateway
(IP SM-GW)
SMS over IP
SMS is encapsulated & routed via IMS
SMS over SGs
46
IPsec
The IP version can be IPv4 or IPv6
In case of VPN traffic IPsec will be used
The applications on top of IP in the user plane stack are all protocols of the TCP/IP
suite such as File Transfer Protocol FTP, HTTP (web browsing), POP3/SMTP (for e-mail)
and Real Time Transport Protocol RTP and SIP for real time services like VoIP
While IPsec is used decoding of TCP/UDP frames is not possible due to ciphering used
by IPsec
47
47
VoLTE Basics
48
IMS Connectivity
49
On Net Call
SCFX
PCFX
50
Off Net Voice Call
51
Emergency Call Flow
52
On Net SMS
53
Off Net SMS
54
VoLTE Requirements
55
VoLTE Ecosystem Requirements
56
VoLTE Ecosystem Requirements (Contd)
57
VoLTE Requirements
58
User Identities in IMS Network
59
Bearer Mapping
60
61
62
63
SIP Cause Codes
64
SIP Cause Codes (Contd)
65
SIP Cause Codes (Contd)
66
67
68
Attach Procedure
T300
starts
T300
stops
69
Attach Procedure
70
RACH
71
RACH Trigger (Two Examples)
72
RRC Connection Request (UpLink) (Two Examples)
73
RRC Connection Setup (Down Link)
74
RRC Connection Setup Complete (Uplink)

Attach Request
75

Attach Request
76

Attach Request
77
78

Attach Request
79

Attach Request
80
81
82
83
84
85
Codec
Selection
Dedicated
Bearer
86
87
QoS Negotiation
88
VoLTE Call Flow
89
RJIL Initial Attach Request (APN=jionet)

UE
eNB
SAE GW
MME
S-GW
P-GW
HSS
SPR
PCRF
OCS
Power on
RRC Connection Setup
1. Attach Request(PDN Connectivity Request)
IMSI, Initial Request, APN=jionet
LTE Authentication
NAS Security Setup
Location Update
2. Create Session Request
IMSI, MSISDN, APN=jionet, PCO, Bearer Context (Bearer ID, Bearer QoS QCI:9, GBR: 0, MBR: 0)
3. UE IP allocation
4. CCR(Indication of IP-CAN Session establishment)

Initial Request, Subscription-Id(e.g., IMSI), UE-IP, APN, EventReport, QoS Info(APN-AMBR(UL/DL)), EPS Bearer QoS(QCI, ARP)
5. Profile Request
6. Profile Response
User Profile = internet
7. Policy Decision
8. CCA(Acknowledge of IP-CAN Session Establishment)
9. Policy Enforcement
PCC Rule for Default bearer(QCI=9, ARP=1, APN9.1 CCR (Indication of Session, APN=JioNet)
AMBR(UL/DL)=50Mbps/100Mbps, Offline, TFT(UL/DL))
10. Create Session Response

UE-IP, Default bearer QoS(QCI=9, ARP=1, APN-AMBR(UL)=50Mbps, TFT(UL)=(UE IP, *, SIP, *, UDP)
9.2 CCA (Ack of session, APN=JioNet)
11. Attach Accept(Activate Default EPS bearer Context Request)

APN=jionet, UE-IP, Default Bearer QoS(QCI=9, ARP=1, UE-AMBR(ULAPNAMBR(UL)=50Mbps, TFT(UL)=(UE IP, *, SIP, *, UDP), PCO, GUTI, TAI-list
12. Policy Enforcement

13. Attach Complete(Activate Default Bearer Context Accept)
14. Modify Bearer Request Bearer ID
15. Modify Bearer Response
Default Bearer(QCI=9)
90
RJIL PDN Connectivity Request (APN=ims)

OCS
PCRF
PCO option is used

by UE during PDP
context activation
to request for
P_CSCF address,
DNS server details
etc
4.1 CCR & CCA to/from PCRF, APN=ims)

4.2 CCR & CCA to/from OCS, APN=ims)
PCO : Protocol
Configuration Option is
used to allocate the PCSCF
domain name /IP address
DNS : Domain Name
Server translates
hostname into IP address
91
RJIL Device view after IMS registration(S-4 mini)
The Jio Join client resides on a 2G/3G/4G LTE Only handsets

92
VoLTE - UE Attachment and IMS Registration message
RACH, Attach, Authentication and Default Bearer

Creation QCI 9 and Dedicated Bearer QCI 5 using Jionet
APN and IMS APN both bearers shown (detailed
messages already discussed)
CCR Credit Control Request
CCA Credit Control Answer
Part 1 of 2
93
VoLTE - UE Attachment and IMS Registration message
Auth Challenge
UAR : User Authorization Request, UAA : User Authorization Answer

MAR : Multimedia Authorization Request, MAA : Multimedia Authorization Answer
UDR : Update Data Request, UDA : Update Data Answer
SAR : Server Authorization Request, SAA : Server Authorization Answer
Part 2 of 2
94
RJIL VoLTE Call Flow (UE to UE SIP Msgs)

UE
IMS
UE
INVITE (SDP offer)

100 Trying
INVITE (SDP offer)

100 Trying
183 Session Progress (SDP answer)

PRACK
Used only when

network based
ringback is used
183 Session Progress (SDP answer)
200 Ok_PRACK
PRACK
200 Ok_PRACK
180 Ringing
180 Ringing
UPDATE (SDP offer)

200 Ok_UPDATE (SDP answer)
183 Session Progress
200 Ok_INVITE
UPDATE (SDP offer)

200 Ok_UPDATE (SDP answer)
200 Ok_INVITE
Ack
User
alerting
Hook off
Ack
RTP/RTCP
BYE
BYE
200 Ok_INVITE
200 Ok_INVITE
95
Case Study : M to M VoLTE call(1)

Both Devices are in Idle Mode
96
97
98
99
100
IMS to PSTN/PLMN call flow
101
VoLTE - UE to UE Call establishment (Originating Side)
RAR : Reauthorization Request, AAR : Authentication Authorization Request, SDP : Session Description
Protocol
102
VoLTE - UE to UE Call establishment (Terminating Side)
103
VoLTE - UE to UE Call clearing (Initiated message)
104
VoLTE - UE to UE Call clearing (Received message )
105
VoLTE - VoLTE UE to CS call establishment (Originating Side )
106
VoLTE - VoLTE UE to CS call establishment (Originating Side )
107
VoLTE - VoLTE UE to CS call establishment (Terminating
Side )
108
VoLTE - VoLTE UE to CS call Clearing (Initiated )
109
VoLTE - VoLTE UE to CS call Clearing (Received )
110
MOCN Trial set up
12th Jan 2016
111
MOCN Trial set up Schematic

Internet
ALU
7750SR
SGi
SGi
S1 - U
SAEGW
SGi
OAM
Gx
PCRF
OAM
S11
SGs
MME
Gx
Gx
Gy/Ga
Shared eNB
CCR
( 1+1 )
S6a/ S13
S1 - MME
OAM
HP
Switch
( 1+1 )
Gy/Ga
Gy/Gz
Juniper
M120
SGs
CAG
( 1+1 )
S6a/ S13
OCS / OFCS
SGs
MSC / IWF
S6a/ S13
HSS / EIR
OAM
OSS
Interfaces ready for Data call
Interfaces WIP for voice call
DCN NW
Not mandatory for first call
Internet data call successfully tested

Voice call testing readiness is in progress
112
Copyright and Confidentiality

Copyright 2015, SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to the specifications of
the products detailed in this document at any time without notice and obligation to notify any person of such changes. Information
in this document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained here may be copied, translated,
transcribed or duplicated by any form without the prior written consent of SAMSUNG Electronics.
113

4 - Call Flow PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4 - Call Flow PDF

Uploaded by

Copyright:

Available Formats

Call Flow

4 rth February 2015

2015 Samsung Electronics

2015 Samsung Electronics

2015 Samsung Electronics

ENB Interface and Protocol

2015 Samsung Electronics

MME Interface and Protocol

2015 Samsung Electronics

MME Interface and Protocol

2015 Samsung Electronics

SAE GW Interface and Protocol

2015 Samsung Electronics

SAE GW Interface and Protocol

IP Packet is tunneled between P GW and UE using GPRS Tunneling Protocol GTP

2015 Samsung Electronics

VoLTE Logical Architecture

2015 Samsung Electronics

VoLTE Logical Architecture

2015 Samsung Electronics

RJIL Network Overview

2015 Samsung Electronics

LTE reference model

Radio interfaces and radio resource management.

LTE related control plane signaling

Interconnection point to external IP networks. IP address allocation/charging/packet

Online Charging System / Offline Charging System

RJIL Network Architecture(LTE)

SAE-GW = S-GW + P-GW

Regional Sites (8 Super Core) Setup

Child Circle Parenting with Regional Sites

Basic VoLTE Network Architecture

SBC : Session Border Controller

RJIL Network Architecture(IMS)

PDN Connectivity & Attach

NW Architecture - Voice/Video Call over LTE

Use the same architecture/procedure/protocol with VoLTE

SIP for Signaling using default bearer with QCI-5

Difference with VoLTE

2015 Samsung Electronics

Identities Used in LTE - GUTI

2015 Samsung Electronics

Identities Used in LTE - RNTI

2015 Samsung Electronics

2015 Samsung Electronics

2015 Samsung Electronics

2015 Samsung Electronics

UE Temporary IDs at different interfaces

2014 Samsung Electronics

2014 Samsung Electronics

2014 Samsung Electronics

2014 Samsung Electronics

2015 Samsung Electronics

Packet Data Flow in LTE

2015 Samsung Electronics

IMS (Schematic Architecture)

2015 Samsung Electronics

1. LTE natively supports VoIP only using IMS services

2015 Samsung Electronics

CSFB and SRVCC

OTT and VoLTE

2015 Samsung Electronics