Professional Documents
Culture Documents
Deployment's
Guideline
Boumédiene
BOUKHARI
Document history
2 Interne Orange
Contents
VoLTE Introduction
Voice over LTE Activation
VoLTE Features Overview
Mandatory Features
Recommended Features
Recommended Optimization's
VoLTE Setting & Monitoring
References
3 Interne Orange
Overview
This work was done based on a dedicated workshop on VoLte deployment's feedback form Orange Poland experience, also based on
support during serval month on different MEA affiliate.
The main aim of this document is to share a guide of best practice methodology on the deployment’s of features and optimizations actions
for Huawei/Nokia Vendor.
4 Interne Orange
VoLTE introduction
VoLTE introduction
VoLTE Overview
VoLTE is a voice sessions set up over IP networks initiated by compatible user equipment across IMS.
The activation of the voice services over LTE will permit handling voice services without the need of falling back to UTRAN/GERAN,
also it will offer a lower access delay with a better voice quality and then improve the end user experience.
EUTRAN: Evolved UMTS Terrestrial Radio Access Network GERAN: GSM/EDGE Radio Access Network
6 Interne Orange
MME: Mobility Management Entity HSS : Home Subscriber Server
SGSN: Serving GPRS Support Node PCRF : Policy and Charging Rule Function
UTRAN: Universal Terrestrial Radio Access Network
VoLTE introduction
Qos differentiation- QCI setting
Packet Schedul
Packet Error enforce TTI Schedull Weight
QCI TRANSLATION table Delay Target Delay DSCP maxGbrDL maxGbrUL Prio Qci Qci Supp
Loss Rate Bundling Prio (UE scheduler -
Budget higher value= lower
priority)
QCI Tab 1 −2 -
80 100 ms 10 46 1 256 256 2 1 Enable 5
QCI Tab 5 −6
- 100 ms 10 46 0 - - 1 5 Enable 4 100
It’s allows the MME to dynamically change the following bearer level parameters using the E-RAB modify procedure :
QCI
ARP (including PVI/PCI)
VoLTE bearer :
Downlink GBR/MBR
• QCI1: voice packet - dedicated bearer
7 Interne Orange Uplink GBR/MBR • QCI5: IMS signaling – default bearer
VoLTE introduction
Coverage
As other services, in VoLTE the Uplink is the limiting factor compared to
downlink but thanks to some features as TTI bundling which can improve
it ( ~ 2 dB of gain with ePA channel model).
If we compare voice services between LTE & 2G/3G the highest
difference will be identified until the cell edge and
be visible in the stability if the voice quality offered by
VoLTE but also in the shorter delay.
In VoLTE, the capacity of Cell represented by the maximum of VoLTE users can be limited by different channel depending on carrier
frequency, bandwidth, scheduling mode,…
DS(dynamic scheduling )
Bandwidth Limiting channel
Uniform
5 Mhz 50-62 PDCCH
10 Mhz 120-140 PDCCH
20 Mhz 270-290 PDCCH
several assumptions have been used several assumptions have been used
Please note that the relative low throughput requirements of VoLTE are typically not a threat for shared channel (PDSCH/PUSCH)
capacity.
The impact of the VoLte deployment on the LTE capacity is negligible thanks to existing
solutions as ROHC, …
9 Interne Orange
VoLTE introduction
Codecs
The eNodeB and the EPC are not involved during the codec negotiation phases, its performed firstly when the call is initiated between the
original caller and target receiver. Each UE provide a list of prioritized codec, then a selected one will be common with the highest priority.
10 Interne Orange
VoLTE introduction
Mobility
One of the most important point over the different technologies as GSM/UMTS or LTE is the
mobility and the service continuity.
For the best performances some complementary features are needed to complement the
processing in the case of less dense for LTE or for weak coverage (indoor/rural) depending on
the deployed frequency.
The UE will communicate different information's during the attach request phases as VoLTE
support or UE capability , also on the MME side during the accepting phases serval information's
should be sent to the UEs as :
Emergency service support
Location services support indication
VoLTE supported indication
The concerned feature are :
CS Fallback
Single radio voice call continuity (SRVCC) – Introduced in this Guideline
HUAWEI NOKIA
EUTRANVOIPSUPPORTSWITCH=ON LTE10: EPS Bearers for Conversational Voice
UlschStrategy ~ULSCH_STRATEGY_EPF Perquisite feature :
DlschStrategy~DLSCH_PRI_TYPE_EPF LTE7 : Support of multiple EPS bearer
13 Interne Orange
VoLTE
Features
Overview
VoLTE Features Summary
15 Interne Orange
VoLTE Robustness Enhancements Coverage boosting Coverage
VoLTE Features Summary
16 Interne Orange
VoLTE Robustness Enhancements Coverage boosting Coverage
Mandatory Features
Mandatory Features Recap
Vendor Category Feature ID Feature Name Validation statuts Requirement for VoLTE
18 Interne Orange
Mandatory Features Recap
Vendor Category Feature ID Feature Name Validation statuts Requirement for VoLTE
19 Interne Orange
Mandatory Features T6
RoHC ( Robust header compression )
The aim for compression of RTP/UDP/IP headers is to decrease the VoIP
throughput between terminal and eNodeB
Voice header overhead (IP/UDP/RTP) reduced from 40 or 60 bytes to 5 bytes
for IPv6 and IPv4
Fully transparent compression/decompression between eNB and UE ,Robust to
errors common on cellular links
Handles several consecutive packet losses with maintained compression
efficiency With RoHC and PDCCH optimizations (Frame bundling …), gain is
expected on the cell capacity (max number of simultaneous VoLTE call) and
remaining data capacity
Benefits
Reduction of header overheads & packet loss
Shortens the response time
High robustness
High compression efficiency
TTI Bundling is the most efficient uplink coverage feature for voice, based on 4
systematic and preventive repetitions of the speech frame before positive or
negative acknowledgement from the eNB (allowing
higher energy per bit). TTI bundling is intended mainly for UEs at cell border with
active VoIP (QCI1) services. Bundling of TTIs enhances the uplink coverage. One
transport block is allocated to four TTIs instead of one TTI, that is, the energy per
transmitted bit is increased.
Benefits
Improvements of the uplink coverage
Reduction of latency caused by multiple adaptive HARQ retransmissions.
In case of poor radio condition, it will reduces PDCCH traffic by preventing
from packet segmentation and because of fewer adaptive HARQ retransmissions.
Fewer HARQ retransmissions leads to latency reduction
SRVCC features
Single Radio voice call continuity (SRVCC) feature ( it is both a RAN & Core related feature )
enables VoLTE service to be carried in the circuit switched ( CS) domain to ensure the voice
service continuity.
There are two scenario's of SRVCC deployment’s : CS –Only or CS + PS
In this documents we will focus only on the scenario CS–Only (the must deployed).
For the SRVCC CS-Only :
The MME instruct the MSC to prepare the handover
The PS services resume during RAU procedure on the UTRAN
To support SRVCC, the Sv interface is introduced between MSC server & MME.
Benefits
Need the activation of feature or switch over
Ensure the continuity of the service between the E-UTRAN &
UTRAN/GERAN
UTRAN to ensure the full activation of SRVCC
SRVCC to UTRAN/GERAN requires cell relations to UTRAN external cells
Recommended
Recommended
25 Interne Orange
Recommended Features T6
Smart Admission Control
VoLTE is a GBR (Guaranteed Bit Rate) service impacting overall system capacity and
performance due to the higher priority than regular data services.
The main goal of this functionality is to allow a high resource utilization and that by accepting
radio bearer requests as long as radio resources are available by considering guaranteed
transmission capacity.
Also the task of the admission control (AC) is to admit or reject the establishment requests for
new radio bearers signaling/data radio bearers. It is a feature of enhancement only for GBR
traffic and is required to prevent congestion on “guaranteed” resources.
Benefits
Optimal system and resource availability
The improvement of the admission decisions
HUAWEI NOKIA
LTE497: Smart Admission Control
LBFD-002023 : Admission Control Perquisite feature :
26 Interne Orange LOFD-001029 : Enhanced Admission Control LTE496: EPS bearers with QCI 2, 3 and 4, LTE7: Support of Multiple EPS Bearer
LTE534: ARP based Admission Control
Recommended Features T6
VoLTE UL coverage boosting
Generally the imbalance between UL/DL link budget is around 10 dB and one of the
reason of that is due to the limited transmission power.
It may happen that UE cannot spend enough energy during one TTI to achieve a
successful transmission towards eNondeB and that can increase packet loss rate or call
drops.
The main importance of this functionality is the improvement of UL coverage for UEs
with QCI1 bearer and that over the three below mechanism :
Sensitivity based on UL resource allocation
Reduction of aperiodic CQI reporting Packet Loss
Improvement of the UL receiver
Benefits
UP to 2.5 dB for UEs in TTI bundling mode (1.5 dB for other UEs)
Improvement of call drop and RTP packet loss rate
Improvement on quality mean opinion (MOS)
Improvement on maximum coupling loss (MCL)
HUAWEI NOKIA
LTE2098 : VoLTE Uplink Coverage Boosting
LOFD-120204 : VoLTE Coverage Enhancement Prerequisites features :
27 Interne Orange
“VoLTE Coverage Enhancement Based on Extended Delay Budget” LTE10/LTE11: EPS Bearer for Conversational Voice/ROHC
LTE1034/LTE1495: Extended /Uplink Link Adaptation (E/F-ULA)
Recommended Features T6
DRX
DRX technology enables a UE to turn on its receiver and enter the active
state only when the UE needs to receive downlink (DL) data or signaling.
The UE turns off its receiver and enters the sleep state in other situations
to reduce power consumption.
The UE will monitor the PDCCH in a discontinuous manner which mean
that the UE is aware that the PDCCH does not need to be checked during
period without any transmission and then reduce the battery consumption.
DRX status :
o Active Time: UE turns on its receiver and monitor PDCCH
o Sleep Time : UE turns off its receiver and does not monitor the PDCCH
DRX Cycle: specifies the periodic repetition of the on duration followed by
a possible period of inactivity.
Benefits
DRX Setting for QCI 5 :
Better power consumption of UEs The recommendation is to set the same DRX
Reduces signaling overhead parameters with Data QCI, the Long DRX for
QQCI5 is advised to be =<320ms
DRX Setting for QCI 1 :
HUAWEI NOKIA Long DRX cycle = 40ms
On duration/inactivity timer = 4
LBFD-002017: DRX LTE42 : DRX in RRC connected mode Drx retransmission timer = 4
28 LOFD-00110501:
Interne Orange Dynamic DRX LTE585 : Smart DRX Short DRX cycle to set OFF
Smart Pre-Allocation must be activated
Recommended Features T6
Voice Rate Control
The main aim of the Voice Rate Control feature is to improve quality for voice
connections by an adjustment of the codec rate.
The eNodeB determines whether to adjust the voice coding rate depending on the uplink
channel quality and voice quality. If rate adjustment is needed, either the eNodeB or
session border controller adjusts the voice coding rate of the UE depending on the
parameter settings.
Benefits
Significant decrease of UL packet loss rate
Increases of the MOS by 0.01 to 0.2
Improvement of the voice quality
VoLTE MOS
Increase of
LTE4244 : VoLTE coverage extension by codec rate
LOFD-111207 : Voice Rate Control adaptation
Perquisite feature : Perquisite feature :
LBFD-081103: Terminal Awareness Differentiation LTE10 EPS bearers for conversational voice
LTE2774 Source rate based UL grant assignment for VoLTE
29 Interne Orange
DT ON ZIELONOGÓRSKIE District
Recommended Features T6
VoLTE Robustness Enhancements
VoLTE Robustness Enhancements is a complementary feature with the aim to improve the
VoLTE robustness and it’s realized via three mechanism :
- Proactive Grants for VoLTE Robustness
- Improved mechanism for TTI Bundling activation/de-activation
- Fake DRX Pool license needed
Benefits
Reducing ping pong between regular mode and TTIB mode
Decrease the VoLTE call drops by reduction of TTIB activation/deactivation
handover events (Improved mechanism for entering / leaving TTI Bundling mode)
Improved VoLTE retainability in TTIB mode due to longer OOS detection time
use (Fake DRX mechanism)
NOKIA
LTE3692 : VoLTE Robustness Enhancements
Prerequisites features :
LTE10: EPS Bearerfor ConversationalVoice
30 Interne Orange LTE42: DRX in RRC connected mode
Recommended
Optimization's
Recommended Optimization’s
SRVCC Optimization’s 1/3
Observations :
More conservative thresholds for QCI1 (and QCI5) lead to different mobility behavior
between VoLTE and not volte UE.
The redirection to 3G/2G were triggered earlier for VoLTE UE compare to non-VoLTE UE
Solution:
Same handover Group are assigned to QCI5 and QCI related to Data (QCI 6/8/9)
For the delayed SRVCC problem when CN do not support alerting or pre-alerting, bellow the possible solutions :
SRVCC Measurement Report Delay Timer – LTE3290 SRVCC Trigger Enhancement (FDD-LTE 17) : SRVCC
SRVCCMRDELAYTIMER (timer starts when a VoLTE service is delay timer (delay timer for SRVCC procedure trigger after
successfully set up). establishment of first QCI#1 bearer for UE)
Ringing Message Check Switch – RINGINGMSGCHECKSW
(eNodeB identifies the SIP Ringing message and stops the timer
defined by SrvccMrDelayTimer).
32 Interne Orange
Recommended Optimization’s
SRVCC Optimization’s 2/3
LTE3290 SRVCC Trigger Enhancement SRVCC to UTRAN
The feature introduces a new parameter to control the trigger of the Bellow the Optimization solution when alerting/pre-alerting
single radio voice call continuity (SRVCC) procedure. The SRVCC SRVCC is not supported :
allows a seamless handover procedure between LTE and SRVCC Measurement Report Delay Timer :indicates the length
WCDMA/GSM, but it can be rejected by some IMS implementations of the processing delay timer of SRVCC measurement reports.
if triggered too early. The new, operator-configurable parameter This timer starts when a VoLTE service is successfully set up. It
delays the start of the SRVCC and prevents the procedure from being is used to avoid SRVCC before phones ring or users answer
rejected by the IMS. calls.
Ringing Message Check Switch : indicates whether to check the
SIP Ringing message when the processing delay of SRVCC
measurement reports is enabled. The eNodeB identifies the SIP
Benefits Ringing message and stops the timer defined by
SrvccMrDelayTimer after the identification is successful if this
The IMS no longer rejects the single radio voice call continuity
parameter is set to ON(On). The eNodeB does not identify the
(SRVCC) procedure during the early phase of the VoLTE call setup if
message if this parameter is set to OFF(Off).
the srvccDelayTimer parameter is active.
Parameters Parameters
srvccDelayTimer=1s SRVCCMRDELAYTIMER = 3
RINGINGMSGCHECKSW = ON
33 Interne Orange
Recommended Optimization’s
SRVCC Optimization’s 3/3
Observations :
Failed SRVCC in Nokia RAN due to extended ueCapabilityInformation of Cat18 and
Cat16 UEs.
UE CapInfo is added by Nokia’s eNB to Handover Required message sent to MME.
LTE2324 Network requested UE
Cisco MME before SV 21.4.6 did not support “Source to target transparent container” Radio Capabilities
IE above 2048 bytes. Example of cat.18 mobile phones: Samsung S9/S9+ (6CA),
Sony XZ2 (5CA), Huawei Mate 10 Pro.
This feature ensure end user’s mobile greater flexibility since they support more band
combinations. It impact the RAN system NE external by introducing new information elements to
:
requestedFrequencyBans-r11 in the RRC: UECapabilityEnquiry message
SupportBandCombinationAdd-r11 in the RRC: ueCapabilityInformation message
Parameters
Benefits
Avoid latency from IDLE to active transition Activate Network Requested UE Radio capabilities
User’s flexibility actNwReqUECapa= true
34 Interne Orange
Recommended Optimization’s
Uplink RLC segmentation enhancement
Benefits
Improve voice quality when channel quality is poor Parameters
UlVoipRlcMaxSegNum=23
35 Interne Orange
Note that this parameter is in relationship with UlVoipCrosslayerOptSwitch, if UlVoipCrosslayerOptSwitch is deactivated set UlVoipRlcMaxSegNum=20
Recommended Optimization’s
Voice Characteristic Awareness Scheduling
UL Delayed based Scheduling
Uplink Delay-based Dynamic Scheduling :
for VoLTE services
The activation of this functionality by setting the strategy to VOIP_DELAYSCH
allow the enodeB to prioritize voice packets based on their waiting times.
Sorting scheduling priorities based on delay for voice services brings balanced
scheduling sequence.
Benefits
Improvement of the voice quality for UEs far from center with poor radio
conditions
Increase the user satisfaction ( mostly in scenarios where voice service load is
high)
Parameters
UlDelaySchStrategy=VOIP_DELAYSCH-1
UlVoLTEDataSizeEstSwitch =ON
SriPeriodOptForVoipSW=ON
36 Interne Orange
Recommended Optimization’s
MCS Selection based on TBS Optimization
For VoLTE traffic, the packet number is small, so more padding under some
MCS index ca be observed.
The activation of this parameter allow eNodeB to checks the number of online
VoLTE subscribers and IBLER and then determines whether to apply the
TBS-based MCS selection function to voice services. TBS is short for transport
block size. If the function takes effect on voice services, the eNodeB makes
decisions based on the packet size during a voice call to select a relatively low
MCS while ensuring that the number of RBs remains unchanged.
Benefits
Reduce of HARQ retransmission
Improvement of user delay
Parameters
VoipTbsBasedMcsSelSwitch =1
37 Interne Orange
Recommended Optimization’s
Prevent VoLTE one-way audio, Call setup delay & failures 1/2
Bellow the recommended setting by Huawei to prevent some radio issue (delay, failures,..) :
UlEnhencedVoipSchSw-
UL Compensation Scheduling UlVoipSchOptSwitch
OFF ON
40 Interne Orange
Recommended Features
Uplink VoLTE Continuous Scheduling
During uplink VoLTE continuous scheduling, VoLTE UEs are continuously scheduled in the uplink during talk spurts to reduce the uplink
scheduling delay.
When a UE is in DRX mode, the eNodeB performs SR scheduling or compensation scheduling for all the voice data of the UE at one time if
the UE's power or uplink RBs are insufficient. However, with uplink VoLTE continuous scheduling, the eNodeB does not need to wait for
the UE to report the BSR before triggering the next uplink dynamic scheduling.
When a UE not in the TTI bundling state starts gap-assisted measurement, the eNodeB prevents UL Grant, PUSCH initial transmission,
PHICH feedback for the initial transmission, and initial retransmission from falling into measurement periods. However, uplink VoLTE
continuous scheduling enables the eNodeB to prevent only UL Grant and initial transmission on the PUSCH from falling into measurement
periods.
Benefits
Reduce uplink packet delay
Improvement of voice quality
Parameter HUAWEI
CellUlschAlgo.UlEnhencedVoipSchSw
UlVoLTEContinuousSchSw:Off
41 Interne Orange
VoLTE setting
&
Monitoring
NOKIA Features
43 Interne Orange
Parameters listing Feuille de calcul
Microsoft Excel
Counters listing Feuille de calcul
Microsoft Excel
HUAWEI Features
44 Interne Orange
Parameters listing Feuille de calcul Counters listing Feuille de calcul
Microsoft Excel
Microsoft Excel
Groupe
KPI’s
GROUPE VOLTE KPI’s
Basic KPI’s 1/6
This KPI shows the eNB (radio part) observed probability to set up an end to end
connection for VoLTE. Under the end to end, a connection to be provided with an either
initial or additional E-RAB at request is meant.
100*((SIGN_CONN_ESTAB_COMP)
This KPI consists of four phases: RRC, S1, ERAB QCI_5 (VoLTE default bearer) and
/ (SIGN_CONN_ESTAB_ATT_MO_S +
ERAB QCI_1. Both initial and additional ERAB setup attempts and successes are
SIGN_CONN_ESTAB_ATT_MT +
included in the KPI. RRC and S1 are calculated for all types of services and only ERAB
SIGN_CONN_ESTAB_ATT_MO_D +
parts consider typical QCI’s required by VoLTE.
SIGN_CONN_ESTAB_ATT_DEL_TOL +
It is assumed that statistically RRC SSR and S1 SSR for VoLTE is the same as for any
SIGN_CONN_ESTAB_ATT_HIPRIO +
other type of service. The ERAB component considers initial setups of QCI 5 and QCI1
SIGN_CONN_ESTAB_ATT_EMG +
ERABS, as it is assumed that both are needed to setup a voice over LTE call.
SIGN_CONN_ESTAB_ATT_MO_VOICE +
It also has to be noted that RRC, S1 and ERAB QCI5 need to be established only when
SIGN_CONN_ESTAB_ATT_OTHERS))
Percentage of established calls over *
transition from idle to connected takes place while ERAB QCI1 is usually established
when a new VoLTE call start which may question validity of this approach
the requested ones for VoLTE. (S1_SIGN_CONN_ESTAB_SUCC_UE /
S1_SIGN_CONN_ESTAB_ATT_UE)
4G/LTE Call Setup A call is established when the UE has *
Success Rate – VoLTE established its E-Radio Access [(ERAB_INI_SETUP_SUCC_QCI1+ ERAB_SR=ERAB_QCI1 SR * ERAB_QCI5 SR
ERAB_ADD_SETUP_SUCC_QCI1-
Bearer(s). ERAB_REL_TEMP_QCI1)/
(ERAB_INI_SETUP_ATT_QCI1+
ERAB_ADD_SETUP_ATT_QCI1)]
*
FL17A,18 [(ERAB_INI_SETUP_SUCC_QCI5+
ERAB_ADD_SETUP_SUCC_QCI5)/
(ERAB_INI_SETUP_ATT_QCI5+
ERAB_ADD_SETUP_ATT_QCI5)]
46 Interne Orange
GROUPE VOLTE KPI’s
Basic KPI’s 2/6
This KPI shows the eNB (radio part) observed probability to set up an end to end
connection for VoLTE. Under the end to end, a connection to be provided with an either
CSSR= 100* RRC SR * S1 SR * RAB SR initial or additional E-RAB at request is meant.
This KPI consists of four phases: RRC, S1, ERAB QCI_5 (VoLTE default bearer) and
RRC SR ERAB QCI_1. Both initial and additional ERAB setup attempts and successes are
included in the KPI. RRC and S1 are calculated for all types of services and only ERAB
(L.RRC.ConnReq.Succ.Emc + parts consider typical QCI’s required by VoLTE.
L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt + It is assumed that statistically RRC SSR and S1 SSR for VoLTE is the same as for any
L.RRC.ConnReq.Succ.MoData + other type of service. The ERAB component considers initial setups of QCI 5 and QCI1
L.RRC.ConnReq.Succ.DelayTol+ ERABS, as it is assumed that both are needed to setup a voice over LTE call.
L.RRC.ConnReq.Succ.MoVoiceCall)/
It also has to be noted that RRC, S1 and ERAB QCI5 need to be established only when
Percentage of established calls (L.RRC.ConnReq.Att.Emc + L.RRC.ConnReq.Att.HighPri +
transition from idle to connected takes place while ERAB QCI1 is usually established
L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData +
over the requested ones for L.RRC.ConnReq.Att.DelayTol+ when a new VoLTE call start which may question validity of this approach
4G/LTE Call Setup VoLTE. L.RRC.ConnReq.Att.MoVoiceCall)
S1 SR
Success Rate – VoLTE A call is established when the
ERAB_SR=ERAB_QCI1 SR * ERAB_QCI5 SR
UE has established its E-Radio L.S1Sig.ConnEst.Succ /L.S1Sig.ConnEst.Att)
RAB SR
Access Bearer(s).
( L.E-RAB.SuccEst.QCI.1 / L.E-RAB.AttEst.QCI.1-L.E-
eRAN 6.0&higher RAB.FailEst.X2AP.VoIP)*
(L.E-RAB.SuccEst.QCI.5 / L.E-RAB.AttEst.QCI.5)
Remark:
Counters in green work with feature LOFD-121202
VoLTE User Prior Access. If this feature is not activated
these counters can be removed from the formula
47 Interne Orange
GROUPE VOLTE KPI’s
Basic KPI’s 3/6
This KPI shows the eNB (radio part) observed probability to set up an end to end
connection. Under the end to end, a connection to be provided with an either initial or
additional E-RAB at request is meant.
VoLTE Dedicated 100 * sum([M8006C206] + [M8006C215] -
[M8006C301]) / sum([M8006C188] +
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used
to setup the E-RAB between MME and UE. It indicates the E-UTRAN contribution to
ERAB Setup Success The E-RAB Setup Success Rate [M8006C334] - [M8006C335]) network accessibility for the end-user, not the whole end-to-end servce accessibility. This
(VoIP) KPI indicates the E-RAB [(ERAB_INI_SETUP_SUCC_QCI1+ KPI can be used to evaluate the ERAB setup success rate of the VoIP service in a cell or a
Rate ERAB_ADD_SETUP_SUCC_QCI1 - cluster. This KPI is calculated based on the counters (both the ERAB setup attempts
setup success rate of the voice ERAB_REL_TEMP_QCI1)/ (QCI1) and the successful ERAB setup (QCI1) counters) measured at the eNodeB.
over IP (VoIP) services in a cell or (ERAB_INI_SETUP_ATT_QCI1+ERAB_AD This KPI includes both initial and additional eRAB setups.
FL18A radio network.
D_SETUP_ATT_QCI1_EX_RTR-
ERAB_ADD_SETUP_ATT_QCI1_HO)
This KPI describes the ratio of abnormally released (dropped) E-RABs for
100*(ERAB_REL_HO_PART_QCI1 + VoLTE (QCI1) from user perspective point of view.
ERAB_REL_ENB_QCI1+ERAB_REL_EPC_PATH_S This KPI can be used to evaluate the call drop rate of all services in a cell or
WITCH_QCI1 - ERAB_REL_ENB_RNL_INA_QCI1 - a cluster.
ERAB_REL_ENB_RNL_RED_QCI1 -
Ratio between the number of ERAB_REL_TEMP_QCI1+
EPC_EPS_BEAR_REL_REQ_R_QCI1
4G/LTE Drop Call Rate drop calls over the total + EPC_EPS_BEAR_REL_REQ_O_QCI1)
/
- VoLTE number of connection releases (ERAB_REL_ENB_QCI1 +
ERAB_REL_HO_PART_QCI1-
for VoLTE. ERAB_REL_TEMP_QCI1 +
FL17,17A,18 EPC_EPS_BEAR_REL_REQ_N_QCI1 +
EPC_EPS_BEAR_REL_REQ_D_QCI1 +
EPC_EPS_BEAR_REL_REQ_R_QCI1 +
EPC_EPS_BEAR_REL_REQ_O_QCI1+ERAB_REL_
EPC_PATH_SWITCH_QCI1
+ERAB_REL_SUCC_HO_UTRAN_QCI1 +
ERAB_REL_SUCC_HO_GERAN_QCI1)
48 Interne Orange
GROUPE VOLTE KPI’s
Basic KPI’s 4/6
This KPI shows the eNB (radio part) observed probability to set up an end to end
connection. Under the end to end, a connection to be provided with an either initial or
additional E-RAB at request is meant.
The KPI describes the setup success ratio of the elementary E-RAB setup procedure used
VoLTE Dedicated The E-RAB Setup Success Rate to setup the E-RAB between MME and UE. It indicates the E-UTRAN contribution to
ERAB Setup Success (VoIP) KPI indicates the E- L.E-RAB.SuccEst.QCI.1 / (L.E- network accessibility for the end-user, not the whole end-to-end servce accessibility. This
KPI can be used to evaluate the ERAB setup success rate of the VoIP service in a cell or a
RAB.AttEst.QCI.1- L.E-
Rate RAB setup success rate of the cluster. This KPI is calculated based on the counters (both the ERAB setup attempts
(QCI1) and the successful ERAB setup (QCI1) counters) measured at the eNodeB.
voice over IP (VoIP) services in RAB.FailEst.X2AP.VoIP) This KPI includes both initial and additional eRAB setups.
eRAN 6.0&higher a cell or radio network.
This KPI describes the ratio of abnormally released (dropped) E-RABs for
eRAN 8.1 and earlier VoLTE (QCI1) from user perspective point of view.
This KPI can be used to evaluate the call drop rate of all services in a cell or
4G/LTE Drop Call Rate Ratio between the number of 100*(L.E-RAB.AbnormRel.eNBTot.QCI.1+ L.E- a cluster.
RAB.AbnormRel.MMETot.VoIP) / (L.E-
- VoLTE drop calls over the total RAB.AbnormRel.QCI.1 + L.E-
RAB.NormRel.QCI.1 +
number of connection L.IRATHO.SRVCC.E2W.ExecSuccOut +
L.IRATHO.SRVCC.E2G.ExecSuccOut)
releases for VoLTE.
eRAN 6.0&higher eRAN 11.1 and higher
100*(L.E-RAB.AbnormRel.eNBTot.QCI.1+ L.E-
RAB.AbnormRel.MMETot.VoIP) / (L.E-
RAB.AbnormRel.QCI.1 + L.E-
RAB.NormRel.QCI.1 + L.E-
RAB.NormRel.IRatHOOut.QCI.1)
49 Interne Orange
GROUPE VOLTE KPI’s
Basic KPI’s 5/6
Indicator Name
Definition Formula Calculation rule
RL70
This KPI shows the average VoLTE UE's in connected mode aggregated over
the network.
The average number of UE’s in The number of UE’s in RRC connected mode is sampled and at the end of
RRC connected mode the measurement period the average of these sampling results are used to
calculate this KPI
performing services with QCI1 Optionally:
VoLTE sessions can be understood as sessions with VoIP bearers established.
Average Nb of VoIP
Users L.Traffic.User.VoIP.Avg
100*
ISYS_HO_GERAN_SRVCC_SUCC /
ISYS_HO_GERAN_SRVCC_PREP This KPI describes the success ratio for the inter RAT
handover execution phase for SRVCC, where successes are
INTER-RAT HO This KPI can be used to 100*M8016C34/ M8016C54 considered when the source eNB receives a UE CONTEXT
SUCCESS RATE FOR evaluate the inter-RAT RELEASE COMMAND message from the MME after the
SRVCC (LTE TO GSM) handover success rate from UE is handed over from the E-UTRAN to a GERAN. Both
LTE to GSM in a cell or a preparation and execution phases are included.
cluster for SRVCC 100*
L.IRATHO.SRVCC.E2G.ExecSuccOut/
RL70&higher L.IRATHO.SRVCC.E2G.PrepAttOut
eRAN 6.0&higher
51 Interne Orange
References
References
53 Interne Orange
54
55