2 VoLTE Signaling Flow ISSUE 1.00

VoLTE Signaling & Proc
edures
www.huawei.com
Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
 VoLTE signaling & procedures include:
 Registration
 Service setup
 Anchoring
 SRVCC/eSRVCC

Page3
Objectives
 Upon completion of this course, you will be able to:
 Describe the VoLTE network topology and functions of ke
y elements
 Understand the basic knowledge of VoLTE signaling & pro
cedures (including SIP messages, bearer, QoS and etc)
 Describe the important signaling & procedures of VoLTE
(registration / deregistration, call setup, anchoring,
handover) with the network element involved

Page4
Contents
1. Fundamental of VoLTE
2. VoLTE Key Services Signaling & Procedures

Page5
Contents
1.1 VoLTE Network Topology & Key Element Function
1.2 Fundamental of IMS
1.3 LTE Bearer & QoS

Page6
VoLTE Network Topology SCC AS/MMTel AS
Control Plane
User
Plane HSS
S6a Cx
PCRF MGCF
I-CSCF S-CSCF
MME Mw
Rx
Gx MSC
S1-C Mw
2/3G
MGW
S1-U S5 SGi
Uu
eNodeB S-GW /Gi P-CSCF/SBC IM-
PDN-GW
MGW
E-UTRAN EPC IMS Interwork

with 2G/3G

Functions of EPC Elements
 MME: Access control, mobility management, call management
, network element selection, user bearer information stora
ge
 SGW: Call management, router selection and data forwarding
, Qos control, charging & information storage
 PGW: IP address allocation, call management, PCRF selectio
n, router selection and data forwarding, Qos control, char
ging, policy & charging implantation
 PCRF (Policy and Charging Rules Function): Policy control
& decision and charging control
 HLR / HSS: User subscription data management, user locatio
n management, mobility management and call access restrict
Page8
ion
Functions of CSCF (Call Session Co
ntrol Function)
 CSCF includes P-CSCF, S-CSCF and I-CSCF
Network Function during

Function during Call
Element Registration
Contact point for user
MO: First IMSI access point for
registration
MO UE
P-CSCF Located on the visited
MT: Forward message to MT-UE
networks as first contact
via MT-P-CSCF
point for roaming user
Involved in both MO & MT UEs,
Authenticate user, download
S-CSCF control service triggering, call
user data
control
Assign an S-CSCF for Only for MT UE, as the first
I-CSCF
subscriber registration access point in MT-network

Page9
Other IMS Element & Functions
 ENUM: Domain name query by telephone number
 For example: Send +8675528780808 to ENUMB server for enqu
iry, the corresponding domain name will be return (

hwguy@huawei.com)
 DNS: IP address query by domain name
 For example: Send www.facebook.com to DNS for enquiry, th
e corresponding IP address (for example 189.17.2.123) wil

l be returned
 SBC: IP address conversation between public & private networ
k, media forwarding and network security assurance
 MMTel AS: Provides multimedia telephony & value-added servic
e

Page10
Other IMS Element & Functions (Con
t.)
 MGCF: Media Gateway Control Function
 Realizes interworking between an IMS domain and PSTN/PL
MN
 Control MGW providing audio media channels for real-tim
e conversion of TDM bearer and IP bearer (PSTN/PLMN and

IMS)
 ATCF: Access Transfer Control Function
 Acts as an anchor point for the signaling plane before and aft
er handover
 ATGW: Access Transfer Gateway
 Acts as an anchor point for VoIP media plane before and after
handover

Page11
Contents
1.2.1 IMS-related Identities
1.2.2 VoIP-related SIP Messages

Page12
IMS-related Identity
User Network Public Service

Identity ： Nodes Identity ：
• IMPI Identity ： • SIP URI
NAI • SIP URI • TEL URI
• IMPU • IP Address
 SIP URI
 TEL URI

Page13
Types of Identifier in IMS
SIP URI Tel URI
 SIP Uniform Resource  Tel Uniform Resource
Identifier Identifier
 Uniquely identifies a SIP  Identifies a phone number
user  Begins with "tel:" and may
 SIP URI includes a user contain a global number or a
name and a domain name, local number
or other parameters. It  Encoded using E.164 in the
begins with "sip:" or "sips:" format of tel:Phone number
 User name can be E.164 tel  For instance tel: ＋
number, followed by 867552220001
standardized domain name
 For instance SIP:
+867552220001@ims.sz.cn
Page14
IMS User Identity - IMPI
 IMPI - IP Multimedia Private Identity
 A globally unique number to identify a subscriber on an
IMS network. It is used for registration, authenticatio
n, encryption and charging of IMS subscribers on an IM
S network. It is not used for paging and routing
 Encoded in the network access identifier (NAI) format,
namely User name+@+Domain name
IMPI of User A
1 +867552220001@ims.sz.cn

Page15
IMS User Identity - IMPU
 IMPU - IP Multimedia Public Identity
 A public identity, and used by any user for requestin
g communications to other users
 Used for SIP messages routing
 One IMS user could be assigned one or more IMPUs. IMPU
has two formats: SIP URI and tel URI, with binding betw
een two formats
 IMPU has to be registered before being used to initiate
a call or to be mobile-terminated user
IMPU of User A
User SIP URI Tel URI (E.164)

1 sip:+867552220001@ tel:+867552220001
ims.sz.cn

Page16
Mapping between IMPI & IMPU
 It could be one IMPI with multiple IMPUs or one IMPU
with multiple IMPIs
 Different IMPUs are allowed to share the same service
profile
IMPU
IMPI
sip:zhangsan@aaa.cn
IMS zhangsan_private@aaa.cn Service
Contract Profile 1
tel:+86-139-1234-5678

Page17
Network Nodes Address & Identity
 Network Nodes Identity
 SIP routing processing nodes (such as CSCF, HSS) requires SIP
URI for identification
 The SIP URI of each node with the mapping IP address recorded
in DNS server
 During registration and basic call signaling, terminal and eac
h processing node need to acquire the IP address of the next n
ode from DNS server
sip:scscf1.sx.com
HSS S-CSCF
I-CSCF
sip:icscf1.sx.com
P-CSCF sip:pcscf1.huawei.com

Page18
Public Service Identity - PSI
 Public Service Identity
 A SIP URI that refers to a service instead of a user
 Created in AS (Application Server) to identify the serv
ices provided
 Two formats: SIP URI or tel URI
message service AS AS conference service
p: messaging@ims.huawei.com sip: meeting@ims.huawei.com

Page19
Contents
1.2.1 IMS-related Identities
1.2.2 VoIP-related SIP Messages

Page20
VoLTE Procedures & Signaling
Basic Request Extended Request
 INVITE: Initiate a session  401: Unauthorized, user fault
 ACK: Final acknowledgement for Invite  200: Positive
 REGISTER: Register with address acknowledgement Request
binding has been accepted &

processed successfully
 OPTIONS: Query proxy server for its
capabilities  183: Session Progress.
Request of a call (not
 UPDATE: Update parameters of a
otherwise classified) has been
session during a call
accepted, and currently under
 PRACK: Ack for provisional responses
processing
 CANCEL: Cancel an invite
 BYE: Hang up a session

Page21
SIP Messages during Registration
UE SBC
Registe
r
401
unauthorized
Register
200 OK

Page23
SIP Key Messages - Register
 Initiates registration, authentication and renew registration reque
st with registrar, to record the mapping between user current IP ad
dress and public user identifier (SIP URI)
REGISTER sip:s15.huawei.com SIP/2.0
Via: SIP/2.0/UDP 164.129.32.80:10009;branch=z9hG4……
From::sip:+8675552371010@s15.huawei.com;user=phone>;tag=55d......
To:sip:+8675552371010@s15.huawei.com;user=phone
Cseq:62270 REGISTER
Authorization:Digest username="+8675552371010@s15.huawei.com",
realm="s15.huawei.com",uri="sip:s15.huawei.com", ……
Contact:<sip:44510000@191.169.1.116:5061>
Max-Forwards:70
……
Path:<sip:term@pcscf.s15.huawei.com;lr;ssn;TYPE=V4;IP=164.129.32.80;...
...
P-Visited-Network-ID:"pcscf.s15.huawei.com"
P-Charging-Vector:icid-value="a096f529……
User-agent:Flexit-IMS softphone V1.2D301SP03
……

Page24
Signaling & Procedure of IMS Call
UE1/P-CSCF1 S-CSCF1/AS1 I-CSCF2 S-CSCF2/AS2 P-CSCF2/UE2
INVITE
INVITE INVITE INVITE IMS UE
183 183 performing
183 183 media
PRACK PRACK negotiation
PRACK
, confirm
200 OK(PRACK)
200 OK(PRACK) media IP
200 OK(PRACK)
address,
UPDATE UPDATE
UPDATE media
200 OK (UPDATE) 200 OK (UPDATE) 200 OK (UPDATE) stream type
and
180 Ringing 180 Ringing 180 Ringing 180 Ringing
appropriate
PRACK PRACK PRACK codec
200 OK 200 OK 200 OK
200 OK (INVITE) 200 OK (INVITE) 200 OK (INVITE)
200 OK (INVITE)
ACK ACK
ACK
Call Ongoing

Page25
Signaling & Procedure of Media Neg
otiation
Calling UE Called UE
INVITE (Offer: Preferred media type & codec)
183 on-going (Answer: Supported media type & codec)
UPDATE (Update: Negotiated media type & codec)
200 OK (Answer: Confirmation on negotiated media type &

codec)

Page26
SIP Message - INVITE
 Invite another UA participating in a session. The description o
f the session is included in the message body
INVITE sip:66500002@191.169.1.110 SIP/2.0
From:<sip:44510000@191.169.1.116>;tag=1ccb6df3
To:<sip:66500002@191.169.1.110>
Cseq:1 INVITE
Call-ID: 20973e49f7c52937fc6be224f9e52543@sx3000
Via: SIP/2.0/UDP server9.example.com;branch=z9hG4kb77ef4c23
Via: SIP/2.0/UDP 191.169.1.116:5061;branch=z9hG4bkbc427dad6
Record-Route:<sip:server9.example.com.lr>
Route:<sip:server10.example.com.lr>
Contact:<sip:44510000@191.169.1.116:5061>
Supported:100rel,
Max-Forwards:70
User-agent: Flexit-IMS softphone V1.2D301SP03
Expires:120
Content-Length:230
Content-Type: application/sdp

Page27
SIP Message - UPDATE
 Initiate update request, usually used for media type updat
eUPDATE sip:+8675552371020@s15.huawei.com SIP/2.0 Via:SIP/2.0/UDP
191.138.100.8:5060;branch=z9hG4bKm8ln79nnz91w91kjl09yxj779;Role=3;D
pt=7884_16;TRC=34c5-ffffffff,SIP/2.0/UDP
191.138.100.8:5060;branch=z9hG4bKzx99y991zlz7lkz1kyiw8jjyn;Role=3;Dpt
=7884_16;TRC=34c5-ffffffff,SIP/2.0/UDP
191.138.100.10:5061;branch=z9hG4bKufg544r4w5g1vrurxgi5fiqvq Route:
<sip:191.138.100.10:5060;lr>,<sip:191.138.100.8;lr;ORGDLGID=6511-
3;Dpt=7884_6;TRC=34c5-ffffffff> Call-ID:
hsfou1wwwuiih15r4vuwv4fioxs1vgrq@ATS.ats.s15.huawei.com.22 From:
<sip:+8675552371010@s15.huawei.com;user=phone>;tag=s4yv4hyo-CC-
22-TRC-5650 To: <sip:+8675552371020@s15.huawei.com;user=phone>
CSeq: 1 UPDATE Contact: <sip:
+8675552371010@s15.huawei.com;user=phone> Max-Forwards: 69 P-
Charging-Vector: icid-
value="a096f52912767f6b1d56de9ec4708248.3517286331.242497.53";orig-
ioi=scscf.home1.com;term-ioi=scscf.home1.com Session-Expires: 600
Supported: timer Min-SE: 600 Content-Length: 202 Content-Type:
application/sdp v=0 o=HuaweiATS9900 1360 1361 IN IP4 191.138.100.10
s=Sip Call c=IN IP4 191.138.100.8 t=0 0 m=audio 10788 RTP/AVP 0 8 121
Copyright © 2016
101Huawei Technologies
a=rtpmap:121 Co., Ltd.
AMR/8000 All rights reserved.
a=rtpmap:101 telephone-event/8000
Page28
SIP Message – 183
 183 is used to convey information about the progress of th
e call that is not otherwise classified
SIP/2.0 183 Session Progress

From: +8613625278924 <tel:13625278924;...>
To:"13776014047"<sip:13776014047;....>
…
Contact: <sip:460006012766385@...3gpp-service.ims.icsi.mmtel";...
Cseq: 1 INVITE
Record-Route: <sip:[2409:8015:800:1::7]:9900;...
Via: SIP/2.0/UDP [2409:8015:800:1::7]:9900;...
Content-Type: application/sdp
Content-Length: 529

Page29
SIP Message - PRACK
 Acknowledgement on provisional responses, verify the recip
ient of the provisional 1xx codes. Generally used to ackno
wledge code 183 during session setup, providing the second
time of SDP for media negotiation
PRACK sip: 191.138.100.10:5060 SIP/2.0

Via: SIP/2.0/UDP 10.10.1.196 :5060;branch=8uetb
Route: <sip:scscf2.home2.hu;lr>
Call-Id: sdgweituoweruoiweur
From: <sip:tom@home1.com>;tag=veli
To: <sip:ice@home2.hu SIP/2.0
Cseq: 27971 INVITE
Max-Forwards: 70
RAck: 1 27970 INVITE
Content-Length: 0
Contact: <sip:tom@10.10.1.196:5060

Page30
SIP Message - BYE
 To end the current session. Current dialog terminated once
Bye request received
BYE sip:191.138.100.10:5060 SIP/2.0

Via: SIP/2.0/UDP 164.129.32.80:10009;branch=z9hG4
Route: <sip:191.138.100.5;lr;Dpt=7882_136;Role=3;CxtId=3;spln=PS;X-
HwB2bUaCookie=16024;TRC=34c5-ffffffff>
Call-ID: sbcb070c05c72f4c786fbd9db1f36b0ce78
From: <sip:+8675552371010@s15.huawei.com;user=phone>;tag=b070c
To: <sip:+8675552371020@s15.huawei.com;user=phone>;tag=qo1uy
CSeq: 27973 BYE Max-Forwards: 70 Content-Length: 0

Page31
SIP Message – 180
 The UA receiving INVITE is trying to alert the user. This
response may be used to initiate local ringback
……
From: <sip:
+8613907552122@ims.mnc020.mcc460.3gppnetwork.org>;tag=HTecb
Uu
To: "13907552189"<tel:13907552189>;tag=mnejljfn
……
v=0
o=- 136 136 IN IP6 2002:0000:0000:0000:0000:0000:0000:0004
s=SBC call
c=IN IP6 2002:0000:0000:0000:0000:0000:0000:0004
……
m=audio 12076 RTP/AVP 108 101
a=rtpmap:108 AMR-WB/16000/1
a=fmtp:108 mode-change-capability=2;max-red=0
……

Page32
Contents

Page33
EPS Bearer
 An EPS bearer is used to transmit all the service flows associated w
ith the same QoS policy between a UE and an P-GW. All the service fl
ows transmitted on the same EPS bearer are subject to the same data
transmission treatment related to scheduling, queue management, tran
smission rate restrictions, and RLC configurations

Page34
EPS Bearer (Cont.)
 EPS bearers can also be classified into default and dedicated bear
ers
 Default bearer is set up and remains established throughout the PDN co
nnection in order to provide the UE with always-on IP
 Default bearer has to be non-GBR bearer, with the QoS subscribed in
HSS
 Dedicated bearer includes all EPS bearer connected to the same PDN exc
ept the default bearer
 Dedicated bearer setup or modification can be triggered by network
only
 Dedicated bearer can be non-GBR or GBR, with the QoS subscribed in
PCRF
During registration, VoLTE user setup one default bearer, each f
or PS and IMS, a dedicated bearer (QCI1) during VoLTE service es
tablishment

Page35
EPS QoS Structure

Page36
QoS Parameters: QCI
 Each EPS bearer is defined with a QCI
 The QCI determines how an IP packet on a bearer is
processed on the user plane
Packet Packet
Resour Priorit Delay Error
QCI Example Service
ce Type y Budget Loss
(ms) Rate
1 GBR 2 100 10-2 Conversational voice
2 GBR 4 150 10-3 Conversational video
3 GBR 3 50 10-3 Realtime gaming
Non-conversational
4 GBR 5 300 10-6
voice
Non-
5 1 100 10-6 IMS signaling
GBR
Non-
6 6 300 10-6 TCP-based video
GBR
Non- Voice, video, and
7 7 100 10-3
GBR interactive gaming
Non-
8 8 300 10-6 TCP-based video
Copyright © 2016 GBR
Huawei Technologies Co., Ltd. All rights reserved.
Page37
Non-
QoS Parameters: ARP
 Allocation/Retention Priority (ARP)
 The ARP of a bearer is used to decide whether the requested bear
er can be established or modified and whether such a request is
rejected when network resources are limited.
 The following IEs are related to ARP:
 Priority Level
– Used for this decision to ensure that the request of the bearer w
ith the higher priority level is preferred.
 Pre-emption Capability
– Defines whether a bearer with a lower ARP priority level should b
e dropped to free up the required resource.
 Pre-emption Vulnerability
– Defines whether a bearer is applicable for such dropping by a pr
e-emption capable bearer with a higher ARP priority value.

Page38
QoS Parameters: GBR & Non-GBR
 GBR bearer
 For a GBR bearer, a fixed amount of bandwidth resources is prese
rved, regardless of whether the resources are used or not
 QCI, ARP, GBR, MBR
 Non-GBR bearer
 For a non-GBR bearer, no fixed amount of bandwidth resources is
preserved, and therefore traffic is not ensured
 QCI, ARP, AMBR

Page39
QoS Parameters: AMBR
 Aggregate Maximum Bit Rate (AMBR)
 The AMBR is applicable only to non-GBR bearers
 APN-AMBR (uplink and downlink)
 The APN-AMBR limits the aggregate bit rate that can be provid
ed across all non-GBR bearers related to all PDN connections
on the same APN
 The APN-AMBR is provided by the P-GW which E-UTRAN doesn’t n
eed
 UE-AMBR (uplink and downlink)
 The UE-AMBR is the aggregate maximum bit rate that is expecte
d on all the non-GBR bearers related to a UE
 The UE-AMBR is provided on the eNodeB

Page40
Contents
2.1 Registration / Deregistration
2.2 VoLTE Call
2.3 Anchoring
2.4 Handover

Page42
VoLTE Registration / Deregistratio
n
 There are two stages involved in UE VoLTE network reg
istration:
1. EPS attach procedure
2. IMS attach and third-party attach procedure
 There are two types of VoLTE deregistration:
 UE-initiated: 1. UE detach from IMS 2. UE detach from E
PC
 Network-initiated: 1. HSS initiated 2. UE detach from E
PC

Page43
VoLTE Registration Procedure
Default Bearer
Dedicated HSS
Bearer
PCRF
MME
eNodeB
S-GW PDN-GW
Default bear1: data P-CSCF/SBC I/S-CSCF

Default bear2: ims signaling
voice （ QCI1 ）
Dedicated bear:
E-UTRAN EPC IMS

Page44
VoLTE Registration Procedure – E
PC Attach

Page45
VoLTE Registration Signaling – EPC
Attach
UE eNB MME S/PGW PCRF HLR/HS
1.RRC CONN Req S
2.RRC CONN Setup
3.RRC CONN Setup
Complete 4.Initial UE Msg 5.AIR
(Attach Req) 6.AIA
7.DL NAS Transport
8.DL Info Transfer
(Auth Req)
9.UL Info Transfer
10.UL NAS 11.ULR
Transport 12.ULA
(Auth Rsp) 13.Create Session 14.CCR
Req
16.Create Session 15.CCA
(apn1:data)
17.Initial ContextRsp
Setup
Req
18.RRC CONN (Attach
RECFG Accept)
19.RRC CONN RECFG
Complete 20.Initial Context Setup
Rsp
Page46
VoLTE Registration Signaling – EP
C Attach (Cont.)
UE eNB MME S/PGW PCRF HLR/HS
21.UL Info Transfer S
22.UL NAS
Transport 23.Modify Bearer Req
(Attach Complete)
24.Modify Bearer Rsp
25.UL Info Transfer
(PDN CONN Req) 26.UL NAS 27.Create Session
Transport Req 28.CCR
(apn2:ims) 29.CCA
30.Create Session
31.eRAB Setup Req
Rsp
32.RRC CONN RECFG
33.RRC CONN RECFG
Complete
34.eRAB Setup Rsp
35.UL Info Transfer
36.UL NAS 37.Modify Bearer Req
Transport
38.Modify Bearer Rsp

Page48
Analysis of Key Messages – Attach
Request
 Key elements related to VoLTE in Attach Request:
 Attach Type: specifies the attach flow type: EPS attach, comb
ined EPS/IMSI attach, or emergency attach
 Protocol Configuration Options (PCO): contains the 0002H pa
rameter, indicating a request to establish a default bearer fo
r IMS signaling, and the 000CH parameter, indicating a request
for the P-CSCF address
 PDN Type: specifies the IP address type of the UE: IPv4, IPv6
, or IPv4v6
 MS Network Capability: carries the SRVCC to GERAN/UTRAN capa
bility IE, indicating that the UE supports the SRVCC capabilit
y
 Voice domain preference and UE's usage setting: specifies
whether the UE supports CS Fallback / SMS over SGs, IMS voice,
or both

Page49
Analysis of Key Messages – Attach
Accept
 The element related to VoLTE in Attach Accept message
:
UE IP Address
DNS IP Address

Page51
VoLTE Registration Procedure – IM
S Registration

Page52
VoLTE Registration Signaling – IM
S Registration
UE HLR/HSS P-CSCF I/S-CSCF ATS
39.REGISTER
40.REGISTER
41.UAR
The UE 42.UAA
authenticat 43.MAR
es the 44.MAA
network 46.401 45.401
47.REGISTER 48.REGISTER
49.UAR The
50.UAR network
51.SAR authenticat
52.SAA es the UE
53.200 iFC triggers
analysis
55.UDR 54.REGISTER
56.UDA
57.200

Page53
VoLTE Deregistration Procedure
 Deregistration applies when a subscriber's registration ha
s expired and the subscriber has not initiated a new regis
tration request, or the subscriber wants to deregister fro
m the network
 Deregistration is initiated by UEs or the S-CSCF:
 UE-initiated deregistration:
 UE detach from IMS
 UE detach from EPC
 Network-initiated deregistration:
 IMS-HSS initiated deregistration
 UE detach from EPC

Page55
VoLTE Deregistration Procedure (Co
nts.)

Page56
VoLTE Deregistration Procedure (Co
nts.)

Page57
VoLTE Deregistration Signaling
UE eNB MM S/PG PCRF HLR/HS P- I/S- ATS
E1.REGISTERW S CSCF CSCF
2.REGISTER
3.UAR
4.UAA
5.SAR
7.200 6.SAA
8.REGISTER
10.UL Info Transfer 9.200
11.UL NAS
Transport 12.Delete Session Req
(Detach Req) 13.CCR
14.CCA
15.Delete Session Rsp
16.DL NAS
Transport
17.DL Info Transfer
(Detach Accept) RELEASE
18.UE CONTEXT
REQUEST
19.UE CONTEXT RELEASE
COMMAND
20.RRC Connection
Release 21.UE CONTEXT RELEASE
COMPLETE
Page58
Contents
2.2 VoLTE Call
2.3 Anchoring
2.4 Handover

Page60
VoLTE Call Scenario - Radio
 VoLTE call can be categorized into the following scenarios ac
cording to the UE condition:
 RRC-Connected Call:
 MO: UE initiates call request to IMS, MME triggers dedicated b
earer setup
 MT: IMS sends INVITE message to UE, S/P-GW triggers MME to set
up dedicated bearer
 RRC-Idle Call:
 MO: UE initiates service request, default bearer resumed, proc
eed with IMS call request, MME dedicated bearer setup

 MT: MME triggers paging, default bearer resumed via service re
quest, to receive & acknowledge INVITE message from IMS, and t

hen to setup dedicated bearer

Page61
LTE Subscriber Calling Another LTE
Subscriber

Page63
LTE Call Signaling
I/S- I/S-
UE MM S/PGW PCRF P-CSCF MM HLR/HS
CSCF CSCF
A EA A A A tel AS S
A B
Default Bearer Setup Procedure

1.INVITE Originator
2.AAR Call
Procedure
3.AAA 4.INVITE
5.INVITE
6.INVITE
7.ENUM/DNS
QUERY
8.ENUM/DNS Rsp
9.INVITE

Page64
LTE Call Signaling (Cont.)
I/S-
HLR/HS MM P-CSCF PCRF MME
S
CSCF UE B
tel AS B B B
A
10.LIR Terminated
Call
11.LIA
Procedure
12.INVITE (with T-
13.UDR ADS)
14.IDR
15.IDA
16.UDA 17.INVITE18.INVITE 19.AAR
20.AAA
21.INVITE

Page65
LTE Call Signaling (Cont.)
P-CSCF PCRF S/PGW MME eNB UE
B B B B B B
22. 180
23.AAR Terminated
24.RAR Call Bearer
26.AAA 25.RAA 27.CB Setup
Req 28.eRAB setup
Req 29.RRC CONN
ReCFG
30.RRC CONN ReCFG
31.eRABcomplete
setup
32.CB
Rsp
Rsp
33.CCR
35.AAR 34.CCA
36.AAA

Page66
LTE Call Signaling – Originator D
edicated Bearer Setup
P-
UE eNB MM S/PGW PCRF P-CSCF HLR/HS CSCF
A A EA A A A S
37.180(RingingB
39.RAR 38.AAR )
40.RAA 41.AAA
42.CB Req
43.eRAB setup Req
44.RRC CONN ReCFG
45.RRC CONN ReCFG
complete
46.eRAB setup Rsp
47.UL Info transfer
48.UL NAS
transport 49.CB Rsp 50.CCR
51.CCA 52.RAR
54.180(SDP 53.RAA
,Ringing ）

Page68
LTE Call Signaling – Originator Ded
icated Bearer Setup (Cont.)
MM Tel
UE MM Tel UE
CCF AS/
A AS A
SCC AS B B
55.PRACK
56.200 (PRACK)
57.200 (INVITE)
58.ACR
59.ACA
60.200 (INVITE)
61.ACR
62.ACA
63.200 (INVITE)
64.ACK

Page70
LTE Call Signaling – Session Relea
se Flow
UE MM Tel CCF MM TEL AS/ P-CSCF PCRF S/PGW MM E UE
A AS A SCC AS B B B B B B
65.BYE 66.ACR
(Stop)
67.ACA
68.BYE
69.ACR( (St
op)
70.ACA 71.BYE
72.200
(BYE)
73.STR 74.RAR
Terminat
76.STA 75.RAA 77.DB Req
ed Call
Bearer
79.CCR 78.DB Rsp
Release
80.CCA

Page71
LTE Call Signaling – Session Release
Flow (Cont.)
UE MME S/PGW PCR P-CSCF P-CSCF
eNB A
A A A F A B
A 81.200
83.RAR 82.STR (BYE)
86.DB Req 84.RAA 85.STA
87.eRAB Release
CMD
88.RRC CONN
ReCFG
89.RRC CONN ReCFG
Complete
90.eRAB Release
Rsp
91.DB Rsp
92.CCR
93.CCA
94.200 （ BY
E）

Page72
Contents
2.2 VoLTE Call
2.3 Anchoring
2.4 Handover

Page73
What is Anchoring?
 Anchoring is a process in which calls are anchored from a c
ircuit switched (CS) network to an IMS network for service
processing
 Two anchoring modes: IMRN anchoring prefix & IMRN anchoring
prefix
 The anchor AS performs anchoring in following scenarios:
 An LTE subscriber accesses a CS network and has subscribed to IM
S services. When the LTE subscriber makes a call, the call is an
chored to an IMS network for MO services
 An LTE subscriber accesses an LTE or CS network. When a CS subsc
riber calls the LTE subscriber, the call anchored to an IMS netw
ork for MT services
 Scenario number 2 is more common in live network, with IMRN anch
oring prefix used
Page74
Anchoring Signaling
Anchor
V/GMS MGCF IM- HLR/HS SCC AS I/S-
C MGW S CSCF
Mobile Originating Call Procedure (CS Domain)
1.MAP_SEND_ROUTING_INFORMATION_
REQ Anchoring
2.MAP_SEND_ROUTING_INFORMATION_ Procedure
CNF
3. IDP (Initial Detection Point)
4.CONNECT(IMRN)
5.IAM 6.ADD
REQ
7.ADD
REPLY
8.ADD
REQ
9.ADD
REPLY 10.INVITE

Page75
Anchoring Signaling (Cont.)
HSS MM tel Anchor / I/S-CSCF P-CSCF PCRF MME UE2
AS SCC AS
11.LIR
12.LIA Mobile
13.INVITE Terminated
14.INVITE Call Procedure
(with Domain
16.UDR 15.INVITE
Selection)
17.IDR
18.IDA
19.UDA 20.INVITE 21.INVITE 22.AAR
23.AAA 24.INVITE
25.183
Mobile Terminated Bearer Setup Procedure

Mobile Originated Bearer Modification Procedure
Call End Session Release Procedure

Page77
Contents
2.2 VoLTE Call
2.3 Anchoring
2.4 Handover

Page79
SRVCC/eSRVCC Principle
 ATCF: Access Transfer Control Functionality
 ATGW: Access Transfer Gateway
 SRVCC: Single-Radio Voice Call Continuity
 eSRVCC: enhancement SRVCC

Page80
VoLTE Handover Types
 There are two types of VoLTE handover:
 Intra-EPS Handover: PS domain handover, the procedure is s
imilar with PS service handover

 Considering different handover strategy could be required for
different service, Huawei supports cell-level handover strateg
y per defined QCI, which means different QCI could be configur
ed with different DRX, SRI and handover parameters
 EPS-2G/3G Handover: Implemented by SRVCC / eSRVCC
 For handover decision in radio, the algorithm is similar with
IRAT handover
 For handover procedure, interworking with EPC & IMS is require
d

Page81
Intra-EPS Handover – Inter-eNB X2
Handover Procedure (1/2)
UE Source Target MME SGW
eNB eNB
Measurement CFG
GTP-U:UL &DL Data
1.Measurement
Report
2.Handover Req
3.Handover Req
4.RRC CONN ReCFG ACK
GTP-U:DL Data
5.SN Status
Transfer
GTP-U:Data
Forwarding

Page82
Intra-EPS Handover – Inter-eNB X2
Handover Procedure (2/2)
UE Source Target MME SGW
eNB eNB
6.1RA Preamble
6.2RA response
7.RRC CONN ReCFG Complete
GTP-U:DL Data
8.Path Switch Req
9.Modify Bear Req
10.Modify Bear Rsp
GTP-U:DL Data
GTP-U:end
GTP-U:end marker marker
11.Path Switch Req ACK
GTP-U:UL Data
12.UE Context
Release
TAU Procedure
Page83
Intra-EPS Handover – Inter-eNB S1
Handover Procedure SGW
UE Source Target MME
eNB
Measurement CFG eNB
GTP-U:UL &DL Data
1.Measurement
2.Handover
Report
Required 3.Handover Req
4.Create Indirect
3a.Handover Req Data Forwarding
ACK Tunnel ReqIndirect
4a.Create
6.RRC CONN ReCFG 5.Handover Data Forwarding
7.eNB
CommandStatus
Tunnel Rsp
Transfer 7a.MME Status
Transfer
9.RRC CONN ReCFG Complete
GTP-U:DL Data
GTP-U:UL Data
10.Handover 11.Modify Bear Req
Notify 11a.Modify Bear Rsp
GTP-U:UL & DL Data
TAU Procedure
12.UE Context Release
12a.UE
CommandContext Release
Complete
Page84
EPS-2G/3G Handover - SRVCC/eSRVCC
 SRVCC enables VoIP services of LTE user to be handove
r and carried in the circuit switched (CS) domain of
2G/3G network, ensuring voice service continuity
 There are two handover solution:
 SRVCC: Ensure voice service continuity
 eSRVCC: Enhancement on top of existing SRVCC solution
Note: eSRVCC is commonly used in present live network

Page85
Difference between SRVCC & eSRVCC
 SRVCC Architecture

Page86
Difference between SRVCC & eSRVCC
(Cont.)
 eSRVCC Architecture

Page87
eSRVCC Procedure
SRVC
MSC IM-MGW C-IWF UE1 eNB MME
1.RRC CONN
ReCFG
2.RRC CONN ReCFG
Complete
3.MR 4.HO
6.MAP PREPARE HO Required
5.SRVCC PS to CS Req
Uu and
ReqA/Iu
Interface
7.MAP PREPARE HO
Resource CS Bearer
CNF
Allocation 8.ADD REQ Establishmen
9.ADD REPLY t Procedure
10.IAM
Assign Termination
Resource
11.ACM
12.ADD REQ
13.ADD REPLY 14.SRVCC PS to CS Rsp
15.HO CMD
16.Mobility from EUTRAN

CMD
Page88
eSRVCC Procedure (Cont.) P-
SRVCC- CSCF MM tel
MSC IM-MGW UE1 MME /ATCF /SCC AS HS
IWF
/ATGW S
17.INVITE ATCF
18.200 Termination
19.ACK Establishmen
20.ADD REQ
21.ADD REPLY t Procedure
22.NTFY REQ
23.NTFY REPLY
CS Location Update
Access 24.INVITE
Domain 25.200
Modification 26.ACK
Procedure
Original Call 27.BYE
Release 29.BYE 28.200 (BYE)
Procedure 30.200 (BYE)

Page90
eSRVCC Procedure (Cont.)
 Remarks:

Page91
Key Message Analysis – Handover Requ
ired
 handoverType:
 “ltetoutran” indicates hand
over from LTE from UTRAN
 targetID: Indicates the targe
t RNC location and RNC ID

Page92
Key Message Analysis– PS to CS Reque
st
 Imsi: UE IMSI
 c-msisdn: UE subscribed C-MSIS
DN
 stn-sr: STN-SR assigned by ATC
F to UE during registration
 target-rnc-id: handover target
RNC ID with cell number

Page93
Question:
 Please elaborate the changes in network architecture with
the introduction of VoLTE, including the new network eleme
nt added.
 Please explain what is service anchoring, and domain selec
tion?
 Please elaborate VoLTE user registration procedure.
 What is the difference between SRVCC and eSRVCC?

Page94
Thank you
www.huawei.com

2 VoLTE Signaling Flow ISSUE 1.00

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

2 VoLTE Signaling Flow ISSUE 1.00

Caricato da

Copyright:

Formati disponibili

VoLTE Signaling & Proc

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

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

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

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

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

E-UTRAN EPC IMS Interwork

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

Network Function during

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

iry, the corresponding domain name will be return (

e corresponding IP address (for example 189.17.2.123) wil

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

e conversion of TDM bearer and IP bearer (PSTN/PLMN and

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

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

User Network Public Service

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

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

User SIP URI Tel URI (E.164)

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

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

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

message service AS AS conference service

p: messaging@ims.huawei.com sip: meeting@ims.huawei.com

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

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

binding has been accepted &

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

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

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

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

INVITE (Offer: Preferred media type & codec)

183 on-going (Answer: Supported media type & codec)

UPDATE (Update: Negotiated media type & codec)

200 OK (Answer: Confirmation on negotiated media type &

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

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

SIP/2.0 183 Session Progress

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

PRACK sip: 191.138.100.10:5060 SIP/2.0

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

BYE sip:191.138.100.10:5060 SIP/2.0

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

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

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

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

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

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

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

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

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

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

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

Default bear1: data P-CSCF/SBC I/S-CSCF

E-UTRAN EPC IMS

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

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

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

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

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

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

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

 UE detach from EPC