Professional Documents
Culture Documents
KPIs
Challenges of implementation
Introduction to VOLTE
LTE is a packet only architecture designed to improve data performance. It does not support CS
voice or video call.
In order to accommodate voice on LTE, two approaches were taken i.e. CSFB(Circuit Switch Fall
Back) and Volte.
GSMA Voice over LTE has evolved as the preferred standard for telephony solution in LTE that
has been accepted by the operator community.
GSMA has defined Voice over LTE (Volte) in describing minimum set of requirements for delivering
voice in an all IP environment based on existing 3GPP IMS based
multimedia
telephony
. by LTE
IMS/SRVCC(Voice
Solution
Provided bysolution
IMS and Data
Voice and Data Services
Provided
By the LTE Network
LTE
LTE
Initial smartphone
LTE data card and LTE
CPE(Customer premises
equipment (CPE)
Deployment suggestions:
CSFB
CPEs subscribe to IMS-based VoIP
voice services.
Soft clients subscribe to rich media
RCS services(Rich
Communication
Services) program is a GSM
Association (GSMA) .
2G/3G
2G/3G
Pre-VoLTE
Terminals:
LTE
LTE
2G/3G
Phase 3:
Full LTE coverage
Phase 2:
Continuous LTE coverage
Phase 1:
Hot spot LTE
coverage
Terminals:
Smartphone
LTE data card and LTE
CPE(Customer premises
equipment (CPE))
Deployment suggestions:
Large-scale commercial
deployment
Terminals:
Smartphone
LTE data card and LTE
CPE(Customer premises
equipment (CPE))
Deployment suggestions:
MME
Traces
collected
1) TI-Logs are Terminal Logs or UE Logs Collected during drive test and Analyses Using
Tems Discovery Like RRC Failure Analysis and L3 Message Analysis
2) 2)As a Part of Enode B Performance Analysis Wireshark Logs Collected at MME on S1
AP,X2 AP to analyse the Performance issues happening on SIP protocols to identify
UE and ENodeB Performance issues
Analyze UE Layer 3
RF
Correlation
Found?
YES
Evaluate in detail
RAN
ISSUE
NO
Evaluate SIP Log
IMS
Correlation
Found?
YES
Evaluate in detail
NO
Potential MME/EPC
Issue?
CORE
ISSUE
Trouble Shooting to Improve Volte Performance are done Via Drive Test Logs an Logs
Collected at MME
Access ability and Retain ability are two main KPIs for LTE Layer 3 Analysis. Tems
Discovery Volte report also provides LTE RRC KPIs like RRC Setup Failure Rate, RRC Setup
Attempts, RRC Setup Complete, RRC Drop Rate, RRC Calls Successfully Completed, RRC
Drops, etc.
5
I
Copyright 2016 Tech Mahindra. All rights reserved.
The Above Snap shows the analysis of Packet Capture for SIP Messages done on ENodeB to MME S1 AP
Interface analysis done using wireshark.The Log shows the UE is Registered in Volte Domain(registered
with IMS) and IMS AKA-Authentication(Authentication and Key Agreement) has been Completed by
Core
Network
andMahindra.
UE isAllReady
to make Volte Calls
I
Copyright
2016 Tech
rights reserved.
The Above Snap shows the analysis of UE logs collected during drive test and analyzed using Tems
discovery, the L3 analysis above shows that the UE is started reading the System Information messages
and ready for registration to LTE network
7
KPI Target
>99%
> 99 %
> 98.5 %
< 1%
> 11
>5
> 98.5 %
VOLTE Drive KPI
VOLTE MO
Accessibility
VOLTE Retainability
VOLTE MO
Retainability
VOLTE MT
KPIs
Retainability
VOLTE MO Voice
Setup Time
VOLTE MT Voice
Setup Time
% of Samples with
MOS>2.1
% of call stayed on
VOLTE
KPI Target
>99%
% Retainability
QCI 1
> 99 %
% HOSR
QCI1
> 98.5 %
> 98.5 %
VOLTE Drive Scenario
MS1
LTE_Scanner
Long Call DL (DO
MS2
only)
Long Call UL (DO
MS3
only)
MS4
MO CSFB Call
MS5
MT CSFB Call
MS6
VOLTE MO UE
MS7
VOLTE MT UE
Yes
HW Fault /Down
Time?
NO
Tx Fault?
Yes
NO
is Accessibility
fail to Due o
High/LOW RSSI
Yes
NO
Is Fails due to
Poor RF
Yes
NO
Fails due to
Other Reasons?
Yes
END
10
NO
As Fails due to
Congestion?
Yes
Yes
HW Fault /Down
Time?
NO
Tx Fault?
Yes
NO
Is Drop due to
HO Fail Or High
UL RSSI?
Yes
NO
Is Drop due to
Poor RF
Yes
NO
Drops due to
Other Reasons?
Yes
END
11
NO
Is Drop due to
Congestion?
Yes
NO
Poor HO Preparation
Yes
NO
Incorrect Parameter
setting in Target
Yes
NO
Yes
NOO
Yes
NO
Overshooting
Yes
NO
Collectogs on X2 and S1
AP
END
12
2
3
Description
Troubleshooting
Solution
If Both the Tx branches of Antenna or
It can we verified with scanner Tx1 & Tx2
RRU are not dominant in same
Inform customer so that the tower
RSRP plot in Tems discovery to see that the
TX Imbalance direction, it is refered as Tx Imbalance,
crew can be sent to site for
difference between TX1 and TX2 rsrp should
(Difference between two TX branches <
rectification.
not exceed 10db.
10db).
Feeder cables are physically
PCI plot need to be checked on Tems
Inform customer so that the tower
Feeder Swap incorrectly connected between the
discovery to see if the sectors are radiating in crew can be sent to site for
RRU and Antenna.
the expected direction.
rectification.
PCI distribution need to be check in PCI Plot. Inform customer so that the tower
If existing orientation of antenna are
Azimuth Issue
PCIs are shifted either clockwise or anti
crew can be sent to site for
different from the designed azimuth.
clockwise with respect to the azimuths
verification.
Need to Check PCI collision. Check for UL
RSSI, Check for coverage, check for Alarm, Fix the problem after implementation
Accessibility
Poor Accessibility observed during
check for License capacity. Check for SIP
of recommendation on the basis of
Issue
Drive Test
call flow, there can be several reason
analysis.
observed from SIP messages.
Check for coverage, Check for PCI collision,
check for UL RSSI, check for handover
Fix the problem after implementation
Retainability
Poor Retainability observed during
parameters. Check for SIP call flow. If there of recommendation on the basis of
Issue
drive test
is no RTP packet for 10 sec then it will
analysis.
pegged a drop.
Need to check the neighbor definition and
During the mobilty test when UE tries
Fix the problem after implementation
check for ANR parameters as well.
HO Failure
to Handover from one PCI to another
of recommendation on the basis of
Need to check the basic Handover
PCI and it got failed.
analysis.
Parameters.
MOS Score
Issue
13
Problem
VOLTE
15