E2E Volte optimization- Offerings & Capabilities

1 Planning & implementation

2 Testing & Tools

3 KPIs

4 Challenges of implementation

1 I Copyright © 2016 Tech Mahindra. All rights reserved.

 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 solution.

IMS/SRVCC(Voice Solution Provided by IMS and Data by LTE

Voice and Data Services EPC.LTE Subscribers can Roam on 2G/3G network by SRVCC
Provided
By the LTE Network Voice Services are Provided by OTT(Over the Top Content
Delivery of Audio and Video Over Internet with help of ISP)
LTE Voice Solutions Carrier

Data Services Provided Voice Services Provided by CSFB (Subscribers Fall back to

By the LTE Network and Traditional 2G/3G Networks)

Voice Services Provided

By the CS Network
SVLTE: Dual Radio Terminals are required ,the 2G/3G
Network Provides Voice services and LTE Provides data

2 I Copyright © 2016 Tech Mahindra. All rights reserved.

VoLTE Phase-based Deployment Policy(Planning)

Phase 1: Phase 2: Phase 3:

Hot spot LTE Continuous LTE coverage Full LTE coverage
coverage
LTE LTE
LTE LTE
2G/3G 2G/3G 2G/3G

Pre-VoLTE Initial commercial use Large-scale commercial

deployment
 Terminals:  Terminals:  Terminals:
 Initial smartphone  Smartphone  Smartphone
 LTE data card and LTE  LTE data card and LTE  LTE data card and LTE
CPE(Customer premises CPE(Customer premises CPE(Customer premises
equipment (CPE) equipment (CPE)) equipment (CPE))
 Deployment suggestions:  Deployment suggestions:  Deployment suggestions:
 CSFB  IMS-based VoLTE voice services  The LTE network becomes the
 CPEs subscribe to IMS-based VoIP  eSRVCC mainstream.
voice services.  Convergent database SingleSDB  ICS(IMS Centralized Services)
 Soft clients subscribe to rich media  LTE-based rich media RCS  IMS roaming and interworking
RCS services(Rich services
Communication
Services) program is a GSM
Association (GSMA) .

3 I Copyright © 2016 Tech Mahindra. All rights reserved.

Overview of the Data collection Using Wireshark and
TEMS Discovery

TI
Logs

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
4 I Copyright © 2016 Tech Mahindra. All rights reserved.
High level Troubleshooting Guide For Performance
Analysis Collect Data

Analyze UE Layer 3

RF YES RAN
Correlation Correlate with Traces Evaluate in detail
Found? ISSUE

NO
IMS YES
Evaluate SIP Log Correlation Evaluate in detail
Found?

NO
Potential MME/EPC CORE
Cascade to E2E Team
Issue? 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.
 Wireshark Logs an Helps to Find out NON-RF issues like SIP Protocols Issues, Core Network Issues
5 I Copyright © 2016 Tech Mahindra. All rights reserved.
VOLTE Log Analysis Using Wireshark(SIP Messages)
UE Registration with IMS

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 and UE is Ready to make Volte Calls
6 I Copyright © 2016 Tech Mahindra. All rights reserved.
RRC(L3) Analysis Procedure from Tems Discovery

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 I Copyright © 2016 Tech Mahindra. All rights reserved.

LTE/VOLTE COUNTER KPI’S & THRESHOLD
LTE OSS KPI’s Volte OSS KPI’s

LTE Counter KPI'S for 10 MHz KPI Target VOLTE Counter KPI'S KPI Target
% Accessibility >99% % Accessibility >99%
% Retainability > 99 % QCI1
% HOSR % Retainability
> 98.5 % > 99 %
QCI 1
% IRAT Rate < 1%
DL Throughput (Mbps) > 11 % HOSR
> 98.5 %
QCI1
UL Throughput (Mbps) >5
CSFB Succ Rate > 98.5 % %SRVCC Succ Rate > 98.5 %
VOLTE Drive KPI KPI Threshold VOLTE Drive Scenario
VOLTE MO Accessibility >99% MS1 LTE_Scanner
VOLTE Retainability >99% MS2 Long Call DL (DO only)
MS3 Long Call UL (DO only)
VOLTE MO Retainability >99%
MS4 MO CSFB Call
Volte Drive Test KPI’s VOLTE MT Retainability >99% MS5 MT CSFB Call
MS6 VOLTE MO UE
VOLTE MO Voice Setup <8.5 sec MS7 VOLTE MT UE
Time
VOLTE MT Voice Setup <3.5 sec
Time
% of Samples with > 98 %
MOS>2.1
% of call stayed on VOLTE >96%

8 I Copyright © 2016 Tech Mahindra. All rights reserved.

 VOLTE OPTIMIZATION(Drive Test and OSS Statistics)
 Volte Performance can Analysed by Drive Test data and OSS Statistics
 The purpose of VOLTE drive test is to evaluate the coverage and performance of a network for voice call services. The Major VOLTE
drive test parameters are as RSRP, SINR, DL RSSI, MOS Score, RSRQ, UE TX Power etc.
 Techmahindra has to perform few basic checks with drive logs and parameter audit sheets like : Site are not radiating or radiating
with poor footprint, Antenna Swap, MIMO Swap, PCI Collision, Alarms, UL RSSI, VSWR, Cell Status, eNodeB Power and check for
Parameter.
 Session setup success (Accessibility), session completion failure (Retainability) and SRVCC success rate are two main KPI’s for analysis
from Drive Test data and OSS Stats
 With the help of drive test data and OSS Stats, Techmahindra can check below points:
– Coverage footprint of sites
– Accessibility
– Retain ability
– Mobility
– Quality
– MOS Score
– SRVCC
 If Any degradation in any drive KPI, then has to find out RCA and has to provide solution as per specific problems. Please find some
basic troubleshooting and recommendation for improvement of drive KPI in next slide:
 SRVCC - SRVCC is the Main KPI which needs to be Optimized when there is no Volte Coverage When the handset leaves the LTE
coverage area, then VOLTE connection can be handed over to a CS connection in a legacy network. This procedure is called SRVCC
(Single Radio Voice Call Continuity). If LTE coverage is extensive, then SRVCC probability is Low. It is beneficial to have a low SRVCC
probability to gain full benefit of VOLTE.
If SRVCC issue observed, need to check for A2 and B2 thresholds of QCI 1. Check for neighbor relations for SRVCC with legacy
network
9 I Copyright © 2016 Tech Mahindra. All rights reserved.
VOLTE OPTIMIZATION(Flow Chart for Accessibility)
START

Call Access Failure? Check Hardware Fault (RRU, Neighbor Cell fault or down),
Yes
Check current alarm, History & Activity logs
HW Fault /Down Time?

NO
Yes Check Media, S1 continuity, Tempoint status.
Tx Fault?
NO
Check PCI Collision, Interference (UL RSSI), overshooting and Hardware
Yes
is Accessibility fail to
Due o High/LOW RSSI

NO Identify Poor RF Coverage, Check CQI & Power Limitation. Recommend Physical
Optimization of cells or Propose New Coverage sites. Check for faulty antenna, High
Yes VSWR, damaged cables or connectors.
Is Fails due to Poor RF

NO Try to offload Cell/Site, Apply Layer management strategy if multicarrier carriers

Yes available, Apply Hi Cap settings & Do possible Physical Optimization.
As Fails due to
Congestion?

NO Check for any Non RF Ready Or Pre launch sites nearby, Check layer management
strategy for Multicarrier sites, need to check core Network issues by UE traces or
Fails due to Other Yes MME traces analyzed using Wireshark.
Reasons?

END

10 I Copyright © 2016 Tech Mahindra. All rights reserved.

VOLTE OPTIMIZATION(Flow Chart for Retainability)
START
No
Call Drop? Check Hardware Fault (RRU, Neighbor Cell fault or down),
Yes
Check current alarm, History & Activity logs
HW Fault /Down Time?

NO
Yes Check Media, S1 continuity, Tempoint status.
Tx Fault?
NO
Check PCI Collision, Interference (UL RSSI) on target cell, overshooting Check UL RSSI
Yes
Is Drop due to HO Fail on cell. High Interference cause drops.
Or High UL RSSI?

NO Identify Poor RF Coverage, Check CQI & Power Limitation. Recommend Physical
Optimization of cells or Propose New Coverage sites. Check for faulty antenna, High
Yes VSWR, damaged cables or connectors.
Is Drop due to Poor RF

NO Try to offload Cell/Site, Apply Layer management strategy if multicarrier carriers

Yes available, Apply Hi Cap settings & Do possible Physical Optimization.
Is Drop due to
Congestion?

NO Check for any Non RF Ready Or Pre launch sites nearby, Check layer management
strategy for Multicarrier sites, need to check core Network issues by UE traces or
Drops due to Other Yes MME traces analyzed using Wireshark.
Reasons?

END

11 I Copyright © 2016 Tech Mahindra. All rights reserved.

VOLTE OPTIMIZATION(Flow Chart for Mobility )
START NO

Term point to MME missing on target cells. Check if all MME link is working if MME is
Poor HO Preparation
in Pool.
Yes

Incorrect Parameter
NO setting in
Target
Handover preparation may fail because the target eNodeB cannot provide the
Yes necessary resources for the handover during congestion or cannot interpret the
contents of the handover request message. Check Ho Parameters and Call traces
NO with log analysis to check the incorrect parameter

Yes
Target cell might be loaded

NOO Yes Check for X2Failure alarm or S1 Failure alarm in

Alarm in the target
NO The target cell

NO
Check for Overshooting cells with drive plots/Prach Report ,Recommend Physical
Optimization of these cells and parameter optimization to restrict the Cell
Yes
Overshooting footprint. Propose Coverage optimization for sites having coverage holes.

NO
Analyse using Wireshark and check for the Cause
Collectogs on X2 and S1
AP

END

12 I Copyright © 2016 Tech Mahindra. All rights reserved.

VOLTE OPTIMIZATION CASE STUDIES during Drive Test

S. N Problem Description Troubleshooting Solution

If Both the Tx branches of Antenna or
RRU are not dominant in same
1 TX Imbalance direction, it is refered as Tx Imbalance,
(Difference between two TX branches
< 10db).
Feeder cables are physically
2 Feeder Swap incorrectly connected between the
RRU and Antenna.
If existing orientation of antenna are
3 Azimuth Issue
different from the designed azimuth.
Accessibility Poor Accessibility observed during
4 check for License capacity. Check for SIP
Issue Drive Test
Retainability Poor Retainability observed during
5 parameters. Check for SIP call flow. If there of recommendation on the basis of
Issue drive test
During the mobilty test when UE tries
6 HO Failure to Handover from one PCI to another
PCI and it got failed.
It can we verified with scanner Tx1 & Tx2
Inform customer so that the tower
RSRP plot in Tems discovery to see that the
crew can be sent to site for
difference between TX1 and TX2 rsrp should
rectification.
not exceed 10db.
PCI plot need to be checked on Tems Inform customer so that the tower
discovery to see if the sectors are radiating in crew can be sent to site for
the expected direction. rectification.
PCI distribution need to be check in PCI Plot. Inform customer so that the tower
PCIs are shifted either clockwise or anti crew can be sent to site for
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
of recommendation on the basis of
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
is no RTP packet for 10 sec then it will analysis.
pegged a drop.
Need to check the neighbor definition and
Fix the problem after implementation
check for ANR parameters as well.
of recommendation on the basis of
Need to check the basic Handover
analysis.
Parameters.

Need to check RF conditions. Check for UL

Fix the problem after implementation
MOS Score RSSI, Alarms, VSWR and verify for codec
7 Poor MOS Score (<2.1) of recommendation on the basis of
Issue rate etc.
analysis.
.

13 I Copyright © 2016 Tech Mahindra. All rights reserved.

 Challenges To Deploying VoLTE
The “flipside” of being able to deliver voice and data over one network is that those networks must now be optimized for both voice
and data. Delivering high-quality voice is more challenging, and doing so in the form of data packets even more so.
Aside from the sheer novelty of this undertaking, VoLTE involves lots of new moving pieces, unproven technologies, and
interdependencies. Major challenges to ensuring successful
Deployments out of the gate include:
 Validating New Devices and Configurations
By 2016, ARC Chart expects the installed base of Volte-enabled handsets to top 74 million. Such devices are already available in Korea and other
countries leading adoption. Expects to see many more devices available in many more countries by the end of 2014, and
all of these new devices need to be evaluated for performance, interoperability, and reliability.
 Interoperability in Increasingly Multi-vendor Environments
the interfaces involved in Volte are also prone to customization by vendors, including critical Diameter protocols used in the EPC core, and Session
Initiation Protocol (SIP) implementations within IMS.
 Signaling
Spikes in hard-to-predict signaling traffic are already occurring due to smartphones generating up to 20x the signaling traffic of traditional phones.
Signaling volumes may actually overwhelm infrastructures, leading to costly and embarrassing outages.
 Fallback
Volte is not a forklift upgrade; it’s a whole new deal. Until every mobile phone in use supports it, operators will need to support legacy air-links and
provide seamless fallback to 2G/3G networks where LTE is unavailable.
 Ensuring Quality of Experience (QoE)
For Volte to be worth the formidable investment, it not only has to deliver better quality than what OTT players provide, but exceed what 2G/3G
networks deliver as well. Early indicators
 Impact on value-added services
What impact will increased complexity have on features like Call Waiting, forwarding, voicemail, and conferencing? In migrating voice to LTE,
operators need to be sure subscribers’ satisfaction with the features they’ve come to rely on won’t be compromised
 Stress / Scalability
Does voice get prioritized effectively as the network become stressed? Where are the new bottlenecks and congestion points? What happens when
failovers occur? QoS and reliability must be assessed under realistic load and high-stress conditions to ensure satisfaction and bring high-risk surprises to
light before they do damage.
14 I Copyright © 2016 Tech Mahindra. All rights reserved.
VOLTE – Key Optimization CHALLENGES

15 I Copyright © 2016 Tech Mahindra. All rights reserved.