You are on page 1of 22

Analysis - Handover Interruption Time < 100ms

Handover Interruption Time < 100ms 95% Actual value 81.58%

- DL : 12 times, UL : 8 times, VoM: 18 times (Of the 42 delayed times, only 38 are visible in XCAP)
- Total 38 times of the handover Interruption Time were occurred due to HO RACH fail as below.
But it could be happened because of live network. There are no RF issues, and all identified time delays
are seen as Core issues.

202ms

‘rrcConnectionConfigurationComplet
e' to send the message it took more
than 100ms

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 1


Handover Interruption Time < 100ms
Most of
Handover
delaying are due
to RACH fail
regardless RF
issue.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 2


Handover Interruption time < 100ms

186m
s

Total 7 tilmes of the handover interruption time were occurred due to HO RACH fail as
above
But it could be happened because of live network and
DL : 0 times, UL : 2 times, VoM : 5 times

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 3


Analysis - VoLTE Setup Time < 1.5 ms
VoLTE Setup Time < 1.5ms 95% Actual value 90.2%

Case# : Core Issue

More than 3.4s

In this case is 100 trying delay where the delayed location RF condition also
not bad as shown above figure.
Despite the good RF, the VoLTE setup time delay failed due to core issues.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 4


VoLTE Setup Time < 1.5s
Total VoLTE Setup time

More

UL Interference and Backhaul should be cleared

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 5


VoLTE Setup Time - Analysis

VoLTE Setup Time was delayed, due to UE received 100Trying message 3.1s later regardless RF Condition. IMS Server Issue.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 6


VoLTE Setup Time < 1.5s

1 time(2.521s) of the Volte setup time delay.


Time were occurred due to Rx Invite/100 Trying
takes long time after Tx invite request as above
snapshot.
At time downlink is not bad. It could be happened
because of live network
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 7
Justification for VoLTE setup time
Analysis

Received
Ack
after 0.9s

After UE sent Invite msg, ack was received after about 0.9s and it caused KPI
fail
Since this is not RF issue, KPI fail has to be justified
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 8
VoLTE Setup Time < 1.5s

It took long time until get the 100Trying for IVITE from system regardless RF issue.
Total 1 time out of 18 times of VOLTE Setup delaying happened due to same reason.
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 9
VoLTE Setup Time < 1.5s

VoLTE Setup Time was delayed due to UE received 100Trying message 1.6s later regardless RF Condition.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 10


Analysis
VoLTE setup delay. Case #1 (In most case,RF environment is good, but it is caused by the 100 Trying .)

Delayed Dedicated 100 Trying 1.0s

100 Trying Activation Delay by IMS


- 100 Trying was activated too late

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 11


Exceptional case analysis
VoLTE Setup Time Analysis (87.5%)

Most of VoLTE Setup time fail


location is nor RF condition
More than 1s delay ack message for invite message from upper layer area as shown left figure

Most fail reason is lately

3. 927s
response ack message for
INVITE message from upper
layer even the location that late
volte setup of RF condition was
very good (RSRP -70 / SINR 10)

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 12


VoLTE Latency < 100 ms

When VoLTE Latency delayed, UL Data Arrival happened continuously regardless RF environment
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 13
VoLTE Latency < 100 ms

VoLTE Latency Delayed even though not


bad RF environment
At that time UE used full power (23dBm),
it suspected due to Uplink Interference

And, when UE send MR message for A2


and A1, Latency delayed

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 14


Analysis

- VoLTE Latency time delay. Case #1 Mostly Delayed VoLTE Latency is occurred during the Radio Link failure as seen snap-shot below snapshot

In most case, RF environment is good need to check GTP Loss from LSM-R & UL Uplink RSSI Check.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 15


Analysis
VoLTE Latency time delay. Case #1 Mostly Delayed VoLTE Latency is occurred during the Radio Link failure as seen snap-shot be

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 16


VoLTE Latency < 100ms

VoLTE Latency also related with GTP Loss, need to check and update GTP
Loss status from India © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
17
Justification for VoLTE Latency
Analysis

Delayed VoLTE Latency is occurred during the Failure at MSG4 due to CT timer expired. RF environment is good.
VoLTE Latency ©>=100ms was occurring
Samsung Electronics. in Reserved.
All Rights every points. Needand
Confidential toProprietary.
check from core end 18
Analysis

- VoLTE Latency time delay. Case #1 Mostly Delayed VoLTE Latency is occurred during the Failure at MSG4 due to CT timer expired as seen snap-shot below
In most case, RF environment is good Need to check core

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 19


VoLTE RTP Packet Loss Rate

VoLTE - Site Issue


Need to check UL Interference and Backhau

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 20


VoLTE RTP Packet Loss Rate

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 21


VoLTE RTP Packet loss rate Analysis[Exception]

All RF parameters are good.RACH failed . suddenly RTP Packet loss occurred after PM12:00 as shown below chart so need to
check from core end.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 22

You might also like