VoLTE Overview and Performance

Voice in LTE:
VoLTE & SRVCC

Solution
www.huawei.com
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

LTE Voice Solutions
VoLTE
Voice & SMS services
Voice software such as Skype
CSFB reuses a CS domain
Simultaneous voice and LTE (SVLTE) terminals, also

called Dual Radio terminals, are connected to both LTE
and GSM/UMTS networks
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved. Page2
Evolution of the LTE voice solutions
 IMS/SRVCC is the final solution of voice over LTE.
 CSFB is used as a transitional option for the VoLTE

solution
VoLTE topology
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
1. A default bearer is set up for IMS signaling streams when the UE attaches to the network.
2. 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.
3. A dedicated bearer for IMS voice media streams is set up during call connection.
4. 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.
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved.

QoS Design
QCI Resource Priority Packet Packet Example Services
Type Delay Error Loss
Budget Rate
1 GBR 2 100 ms 10-2 Conversational voice

2 4 150 ms 10-3 Conversational video (live
streaming)
5 Non-GBR 1 100 ms 10-6 IMS signaling
USN Basic Services
 Basic VoLTE services include VoLTE voice, video
conversation, and SMS services.
 Unstructured supplementary service data (USSD) and

location service (LCS) services cannot be provided during a
VoLTE voice service.
 EPC only transfers services but does not control services,

and it cannot differentiate service types.
APN Policy
 According to GSMA IR.92 specifications, an independent APN is used for

VoLTE services, the recommended IMS APN is "IMS.“
Charging Policy
 VoLTE charging is mainly performed on the IMS. The IMS charges

subscribers based on their service usage, such as call duration and number
of short messages.
 When a UE accesses the IMS through the LTE network, PGW records the
UE's traffic volume and generates offline charging data for information
verification. To prevent repeated charging, the billing center deduct VoLTE
service traffic volumes using the IMS APN or RG.
Provides charging verification Charging point for
information for VoLTE services VoLTE services
S-GW P-GW
Billing
center
status in
object type KPI formula KPI name in PRS
PRS
enodeB Accessibility VoLTE ERAB Establishment SR [%] 100*L.E-RAB.AttEst.QCI.1/L.E-RAB.SuccEst.QCI.1 active VoLTE ERAB Establishment SR
enodeB Accessibility VoLTE connections (%) 100*L.E-RAB.AttEst.QCI.1/L.E-RAB.SuccEst active VoLTE connections
100∗((L.E−RAB.FailEst.NoReply.VoIP+L.E−RAB.FailEst.MME.Vo
IP+L.E−RAB.FailEst.SecurModeFail.VoIP)/(L.E−RAB.FailEst.No
enodeB Accessibility ERAB others Fails QCI 1 [%] Reply.VoIP+L.E−RAB.FailEst.MME.VoIP+L.E−RAB.FailEst.Secu active ERAB others Fails QCI1
rModeFail.VoIP+L.E−RAB.FailEst.TNL.VoIP+L.E−RAB.FailEst.R
NL.VoIP+L.E−RAB.FailEst.NoRadioRes.VoIP)
100∗((L.E−RAB.FailEst.TNL.VoIP)/(L.E−RAB.FailEst.NoReply.Vo
IP+L.E−RAB.FailEst.MME.VoIP+L.E−RAB.FailEst.SecurModeFai
enodeB Accessibility ERAB Fails due TNL QCI 1 [%] active ERAB Fails due TNL QCI1
l.VoIP+L.E−RAB.FailEst.TNL.VoIP+L.E−RAB.FailEst.RNL.VoIP+
L.E−RAB.FailEst.NoRadioRes.VoIP))
100∗((L.E−RAB.FailEst.RNL.VoIP)/(L.E−RAB.FailEst.NoReply.V
oIP+L.E−RAB.FailEst.MME.VoIP+L.E−RAB.FailEst.SecurModeF
enodeB Accessibility ERAB Fails due RF QCI 1 [%] active ERAB Fails due RF QCI1
ail.VoIP+L.E−RAB.FailEst.TNL.VoIP+L.E−RAB.FailEst.RNL.VoIP
+L.E−RAB.FailEst.NoRadioRes.VoIP)
100∗((L.E−RAB.FailEst.NoRadioRes.VoIP)/(L.E−RAB.FailEst.No
Reply.VoIP+L.E−RAB.FailEst.MME.VoIP+L.E−RAB.FailEst.Secu
enodeB Accessibility ERAB Fail Lack of resources QCI 1 [%] active ERAB Fail Lack of resources QCI1
rModeFail.VoIP+L.E−RAB.FailEst.TNL.VoIP+L.E−RAB.FailEst.R
NL.VoIP+L.E−RAB.FailEst.NoRadioRes.VoIP))
status in
object Type KPI formula KPI name in PRS
PRS
VoLTE SRVCC Preparation Failure 100 * (1 - （L.IRATHO.SRVCC.E2W.ExecSuccOut /
enodeB Retainability active VoLTE SRVCC Preparation Failure Rate
Rate L.IRATHO.SRVCC.E2W.PrepAttOut)）
100*L.IRATHO.SRVCC.E2W.ExecSuccOut/L.IRATHO.SRVCC.E
enodeB Retainability VoLTE SRVCC Exe Success Rate (%) active VoLTE SRVCC Exe Success Rate
2W.ExecAttOut
100∗(L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP+L.HHO.Intra
enodeB Retainability Intrafreq Ho Execution QCI 1 [%] eNB.IntraFreq.ExecSuccOut.VoIP)/(L.HHO.IntereNB.IntraFreq.E active Intrafreq Ho Execution QCI1
xecAttOut.VoIP+L.HHO.IntraeNB.IntraFreq.ExecAttOut.VoIP)
ERAB drop rate due to s1 down QCI 1 {100}*[L.E-RAB.AbnormRel.TNL.VoIP]/([L.E-
enodeB Retainability active ERAB drop rate due to s1 down QCI1
[%] RAB.AbnormRel.QCI.1]+[L.E-RAB.NormRel.QCI.1])
100∗(1− L.E−RAB.NormRel.VoIP)/(L.E−RAB.AbnormRel.VoIP + formula
enodeB Retainability ERAB drop rate due to other QCI 1 [%]
L.E−RAB.NormRel.VoIP) error
ERAB drop rate due to lost radio 100∗L.E−RAB.AbnormRel.Radio.VoIP/(L.E−RAB.AbnormRel.VoI ERAB drop rate due to lost radio connection
enodeB Retainability active
connection QCI 1 [%] P + L.E−RAB.NormRel.VoIP) QCI1
L.HHO.Pre
p.FailOut.P
ERAB drop rate due to HO prep QCI 1 100∗L.HHO.Prep.FailOut.PrepFailure.VoIP/(L.E−RAB.AbnormRe repFailure.
enodeB Retainability
[%] l.VoIP + L.E−RAB.NormRel.VoIP) VoIP
counter not
exist
ERAB drop rate due to HO exe failure 100∗L.E−RAB.AbnormRel.HOFailure.VoIP/(L.E−RAB.AbnormRel
enodeB Retainability active ERAB drop rate due to HO exe failure QCI1
QCI 1 [%] .VoIP + L.E−RAB.NormRel.VoIP)
L.E−RAB.A
100∗(L.E−RAB.AbnormRel.VoIP)/(L.E−RAB.AbnormRel.VoIP + bnormRel.V
enodeB Retainability ERAB drop Rate due to eNb QCI 1 [%]
L.E−RAB.NormRel.VoIP) oIP counter
not exist
L.E−RAB.A
100∗(L.E−RAB.AbnormRel.VoIP+L.E−L.E−RAB.AbnormRel.MM bnormRel.V
enodeB Retainability ERAB drop Rate due to core QCI 1 [%]
E.VoIP)/(L.E−RAB.AbnormRel.VoIP + L.E−RAB.NormRel.VoIP) oIP counter
not exist
ERAB drop rate due to cell down time 100∗(L.E−RAB.FailEst.NoRadioRes.VoIP)/(L.E−RAB.AbnormRel. formula
enodeB Retainability
QCI 1 [%] VoIP + L.E−RAB.NormRel.VoIP) error
100∗L.E−RAB.AbnormRel.QCI.1/(L.E−RAB.AbnormRel.QCI.1+
enodeB Retainability Call drop Rate VoIP (%) active Call Drop Rate (VoIP)
L.E−RAB.NormRel.QCI.1)
enodeB traffic VoLTE Erlangs L.E-RAB.SessionTime.QCI1 / (ROP (min) x 60) active VoLTE Erlangs
enodeB traffic User TTI Bundling L.Traffic.User.TtiBundling.Avg active User TTI Bundling
enodeB traffic User data in buffer QCI 1 UL (%) L.Traffic.ActiveUser.UL.QCI.1 active User data in buffer QCI1 DL
enodeB traffic User data in buffer QCI 1 DL (%) L.Traffic.ActiveUser.DL.QCI.1 active User data in buffer QCI1 UL
UE eNodeB MME SGW/ PGW HSS
VoLTE signaling flow
Attach Request
Initial UE message(Attach Request(PDNConnectivityRequest))
Authentication Information Request
Authentication Information Answer
Authentication Request
Authentication Response
Security Mode Command
Security Mode Complete
Update Location Request
Update Location Answer
Create Session Request

Internet APN
Create Session Response
Initial Context Setup Request(Attach Accept(ActivateDefaultEPSBearerContextRequest))

RRC Connection Reconfiguration
RRC Connection Reconfiguration Complete
Initial Context Setup Response

Direct Transfer/Attach Complete
Uplink NAS Trasport(Attach Complete(ActivateDefaultEPSBearerContextAccept))
Modify Bearer Request
Modify Bearer Response
Notify Request
Notify Response
Default Bearer Activation Procedure
QCI=5
Dedicated Bearer Activation Procedure
QCI=1 or 2
SRVCC
(Single Radio Voice Call Continuity)
 During the initial deployment phase of the LTE network, only
some areas are under LTE coverage. When a UE moves
from the LTE network to the GSM/UMTS network, carriers
need to deploy the SRVCC solution to switch voice services
to the GSM/UMTS network to ensure that voice services are
not interrupted
 SRVCC aims to ensure voice call continuity in an LTE

network.
 SRVCC is divided into SRVCC Only and SRVCC+PS Handover, and the eNodeB
determines which mode to use.
SRVCC Only:
 When a UE moves from the E-UTRAN to the GERAN/UTRAN, the MME uses the
SRVCC solution to switch voice services to the GERAN/UTRAN to ensure that
voice services are not interrupted.
 Data services will resume in a later RAU or TAU procedure without being
switched.
SRVCC+PS Handover (CS+PS SRVCC):
 Voice services are switched by SRVCC for service continuity and data services
are switched by the PS handover for service continuity. Both services are not
interrupted.
 However, UEs and the GSM network do not support the PS handover from the
LTE network to the GSM network. As a result, SRVCC+PS Handover applies only
to switchover from the LTE network to the UMTS network.
Sv interface
 The Sv interface is an interface between the
mobility management entity (MME) and the
mobile switching center (MSC).
 After deciding to trigger a handover based on

measurement reports sent by the user
equipment (UE), the evolved NodeB (eNodeB)
sends a Handover Request message to the
MME.
 After receiving the request message from the

eNodeB, the MME sends a PS-to-CS handover
request to the MSC over the Sv interface,
requesting to switch the voice bearers to the
MSC.
SRVCC from an LTE network to a GSM network
without DTM support 1. UE sends a measurement report to the eNodeB.
2. eNodeB triggers an SRVCC based on [1].
3. Handover Required: Target ID IE=LAI, SRVCC HO
Indication IE=CS only,
4. To split the voice bearer (QCI 1) from PS bearers.
5. MME selects the SRVCC MSC based on Target ID IE in
[3]. DNS server is used.
6. [6-12] MSC server instructs the target MSC to prepare CS
radio bearer resources. Through Session Transfer

procedure, IMS notifies the peer end of the local CS
access leg and releases the local IMS access leg.
13. MSC server indicates that CS radio bearer resources
have been allocated.
14. Handover Command (Target to Source Transparent
Container) message contains only the voice information
to the eNodeB.
15. To instruct the UE to start the handover.
16. UE accesses the CS domain of the GSM network.
17. Target BSS detects that the UE has accessed the target
cell. UE sends a Handover Complete to the target MSC
through the target BSS.
18. UE cannot access the data service after the handover
because the GSM network or UE does not support
DTM.
19. [19-22] To indicate UE has been handed over.
22. [a] Dedicated bearer deactivation procedure to
deactivate the voice bearer and other GBR bearers and

to suspend the non-GBR bearer.
23. [a,b] If UE has not registered in MSC server.
24.
Copyright © 2017 Huawei Technologies Co., Ltd. All rights Ifreserved.
an emergency call is handed over.
Page17
Accessibility
Retainability
Erlangs
SRVCC improvement after DNS

VoLTE Overview and Performance

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VoLTE Overview and Performance

Transféré par

Droits d'auteur :

Formats disponibles

Voice in LTE:

VoLTE & SRVCC

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

Voice software such as Skype

CSFB reuses a CS domain

Simultaneous voice and LTE (SVLTE) terminals, also

 CSFB is used as a transitional option for the VoLTE

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

1 GBR 2 100 ms 10-2 Conversational voice

 Unstructured supplementary service data (USSD) and

 EPC only transfers services but does not control services,

 According to GSMA IR.92 specifications, an independent APN is used for

 VoLTE charging is mainly performed on the IMS. The IMS charges

Authentication Information Request

Authentication Information Answer

Security Mode Command

Security Mode Complete

Update Location Request

Update Location Answer

Create Session Request

Initial Context Setup Request(Attach Accept(ActivateDefaultEPSBearerContextRequest))

RRC Connection Reconfiguration Complete

Initial Context Setup Response

Modify Bearer Response

 SRVCC aims to ensure voice call continuity in an LTE

SRVCC+PS Handover (CS+PS SRVCC):

 After deciding to trigger a handover based on

 After receiving the request message from the

radio bearer resources. Through Session Transfer

22. [a] Dedicated bearer deactivation procedure to

deactivate the voice bearer and other GBR bearers and

Vous aimerez peut-être aussi