Contents

Services Analysis ( RAN & EPC )

• Drive logs
• VoLTE RAN Optimization • UETR ( X2, S1,RRC)
• VoLTE Border Optimization • MOS scores
• VoLTE Parameter and Configuration Audit • S11
• VoLTE E2E Analysis • Rx & Gx
• SGi
• SIP signaling
• EPC traces

Tools: Accomplishments:

• TEMS Discovery • Optimized 8000+ sites for AT&T and 1700+ sites
• ITK for SingTel
• Business Object • SRVCC Border optimization
• ERTT • MT RRC re-establishment Feature workaround
• VoLTE E2E Analyzer & NEO • DL ICIC feature testing performed
• WIRESHARK • Wining DFW KPI improvement challenge
• ECO • E2E Problem identification
 TEMS Discovery Drive data ( 3rd Party tool) ECO/ERA

• Analyze layer 3 • Identify POOR MOS • Used for automatic

messages calls/clips tilt analysis /
• Analyze poor MOS • Fetch HOIT info recommendations
• Analyze VoLTE • Fetch NCM/Scanner using drive data RF
setup failures & data conditions as input
drop calls • Fetch Network type • PCI confusion
info • Parameter Audit

VoLTE End-2-End Analyzer/

ERTT ITK / BO
Wireshark
• Fetch OSS parameters • Analyze UETRs & Cell • Used to fetch counter
• Perform Audit traces based statistics for
• Analyze EPC traces analysis and provide
• Analyze IMS traces supporting stats for
recommendations.
List of case studies

1. VoLTE Drop without RRC drop

2. RRC drop without VoLTE drop
3. QCI 1 Profile not defined resulting in VoLTE setup failure
4. MT RRC Work around to reduce VoLTE/LTE Drop
5. Incorrect MCS assignment Causing VoLTE Drop
6. Improvement in Retainability with DL ICIC feature activation & MT RRC Work around
7. Improvement in Retainability and SRVCC SR with change in parameter
“b2threshold2rscpUtraoffset”.
 2 3
1

5
 UE

1 1 1

2 2 4

Cell Z did not have RLC - UM feature for VoLTE bearer ( QCI 1) activated
• RLC mode mismatch in source & target cell
• PDCP SN length for QCI 1 mismatch in source & target cell
• RLC SN length for QCI 1 mismatch in source & target cell
• RoHC feature must be activated on both source & target cell

› In some cases it was observed that RLC mode /PDCP / RLC SN length mismatch was observed in
configured value & value found in layer 3 messages
SOLUTION:
– Site should be locked & unlocked after the parameter changes to take in effect.
 There is time offset of 6Hrs b/t drive logs & UETR

1 1
1

2 2

3
3
 New Old
Cell Cell

4
6

4 4.

7 5.

6.

7.
• RLF can be UE detected or ENB detected

• If the RLF is UE detected & if UE performs a successful RRC connection

before MME releases the UE context then VOLTE call will continue

• If the RLF is ENB detected then ENB will request MME to release the
bearers resulting in VoLTE drop.

It is important to note that RRC drop alone do not

conclude that the VoLTE call has dropped.
Further analysis on bearer level needs to be performed
to ascertain if VoLTE call dropped.
 1
1
1

1
2
2
3

1.
2.
3.

CAUSE: QCI-1 Profile was not activated in the site.

1.
2.
3.

4.
5.
 4
1

2 1
PENDING
5
3 4
4

1.

2. This will always result in VOLTE DROP

UE dropped on first carrier & latched on to second carrier cell
3.

4.
›
›

›
›
›
›
›

Parameter Value

connectedModeMobilityPrio -1
voicePrio -1
a5Threshold1Rsrp (cell level) -112
a5Threshold2Rsrp (cell level) -112
a5Threshold1RsrpAnrDelta (cell level) 10
a5Threshold2RsrpAnrDelta (cell level) 1
IsRemove Allowed FALSE
 1
1

3
2
4

1.
2.
3.

4.
›

L13B EP 14 Software rollout

Green CL
drive stopped.

Solution:
ENB software was upgraded to L13B EP14 which
fixed this issue
›

•
•
•

›
›
 LTE Retainability pm MARKET TREND LTE Re-establishment
data pm data

VoLTE Retainability LTE Throughput pm

pm data data

Observation:
Improvement in LTE retainability~0.02 , VoLTE~1. No. of radio link failures reduced significantly, No significant degradation
in throughput.
MARKET TREND – DRIVE DATA
›

›
Observation: Counter Based

Retainability shows slight improvement after the changes . SRVCC attempt reduced as expected and SRVCC success
rate improved when compared to same amount of attempts before.
1. Normal RRC connection release need not necessarily mean not end to VoLTE call. Mismatch in the below
parameters will lead to bearer drop.
 rlcMode
 rlcSnLength
 pdcpSnLength
 rohcEnabled

2. It is important to note that RRC drop alone do not conclude that the VoLTE call has dropped. Further
analysis on bearer level needs to be performed to ascertain if VoLTE call dropped.
3. QCI 1 profile must be defined to enable VoLTE services.
4. Multi Target RRC Connection re-establishment will not be successful (L13B) if neighbors are not defined in
both the directions. The problem could be more severe when layering strategy does not allow handover
from one carrier to other(IFHO). A work around is possible to reduce the impact of the limitation.
5. Incorrect MCS assigned by ENB to Rel 8 UE was causing the VoLTE drops in poor SINRs, this was a eNB
software bug and was rectified by EP14 rollout. A significant improvement in retainability was observed.
6. DL ICIC feature shows good improvement in VoLTE Retainability.
7. QCI 1 specific “b2Threshold2RscpUtraOffset” helps to improve VoLTE retainability as well as SRVCC
performance. Offset value of 10dB showed good results.