Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 21

VoLTE Call Drop Analysis

©2013 Nokia Solutions and Networks. All rights reserved.


Summary
1.There are 3 different scenarios found, which cause QCI1 deactivated.
2.1 RTP drop – bye
2.2 Drop (LTE RRCConReestReq-Handover Failure)  without real RRC signalling
2.3 HO Failure with RRCConReestReq Reject
2.All VoLTE drop cases found during drive test seem not to trigger our PM counter as
drop for QCI1 (details message show in slides).
-Case2.1 & 2.2  eNB didn’t send UEContextRelRequest with either “RNL” or “other”
cause to EPC, and vice versa.
-Case2.3  Unclear why source eNB wait 1.4 sec without sending either
message “HO Cancel” or “UEContextReleaseRequest” with cause
“Tx2RelocOverall Expire”.
3.Unclear the main reason, why QCI1 was requested to be activated in Case2.1&2.2.
Key information cannot be decoded by emil.
4.Unclear about user experience, why these 3 scenarios will really consider as VoLTE
drop from user point of view or not. Does customer require to make VoLTE again
manually with these above scenarios ?
For internal use Document ID / Version number / Life cycle status / Department / Author
2 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Related Counter for QCI1 Drop Case

Should it be S1AP:E-RAB Release Request or


For internal use Document ID / Version number / Life cycle statusS1AP :UE Context
/ Department Release Request instead ??
/ Author
3 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#1
RTP Drop – Bye

Note: Suddenly message “RTP Drop-Bye” show without any radio link failure
issue, then QCI1 was requested to deactivated. Don’t know what exactly
reason (Emil can’t decoded) sent from UE to eNB toward EPC before got
“ERAB-ReleaseCommand” with normal release !!!

For internal use Document ID / Version number / Life cycle status / Department / Author
4 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#1
RTP Drop - Bye

CRNTI: 16869

For internal use Document ID / Version number / Life cycle status / Department / Author
5 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#1
RTP Drop - Bye

QCI1 activated

RTP Drop - Bye

For internal use Document ID / Version number / Life cycle status / Department / Author
6 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#1
RTP Drop - Bye

QCI1 deactivated

For internal use Document ID / Version number / Life cycle status / Department / Author
7 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#1
RTP Drop – Bye (Emil Trace)

EPC S1AP: ERAB Release Command

For internal use Document ID / Version number / Life cycle status / Department / Author
8 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
UE sent some info to eNB, then QCI1 was requested to deactivated
Can’t decode S1AP: UplinkNASTransport

F:\CA Workshop\
Mon_00C7_1990(RTP Drop - B

Not properly decoded

For internal use Document ID / Version number / Life cycle status / Department / Author
9 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#2
Drop(LTE RrcConReEstReq-Handover Failure)
without real RRC Signalling message

Note: Suddenly message “Drop(LTE RrcConReEstReq-Handover Failure)”


show without any radio link failure issue, no real RRC message happen for
RRC-ConnectionReEstRequest show in UE log.

For internal use Document ID / Version number / Life cycle status / Department / Author
10 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#2 (XCAL)
QCI1 drop without RRC message related AMR-WB traffic still OK, when it was message “Drop (LTE
RRCCon.Reest.Req-handover Failure” show in Uu interface.

Don’t know why suddenly


traffic became Rx direction
with different SN number

QCI1 deactivated

For internal use Document ID / Version number / Life cycle status / Department / Author
11 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#2 (Emil Trace)
QCI1 drop without RRC message related

F:\CA Workshop\
VoLTE_UE_Logs\Drop Call Te

Suspect ENB sent same message as first case to


EPC, then EPC sent back E-RABReleasecommand
with “normal release” to eNB for deactivated QCI1.

For internal use Document ID / Version number / Life cycle status / Department / Author
12 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Case#2 (Wireshark Trace)
No SIP message informed IMS during it’s show RTP-Drop

No sip message informed about RTP drop


sent to IMS before UE sent “BYE” with
“user- triggered” cause.

Still normal AMR-WB traffic during problem


period

For internal use Document ID / Version number / Life cycle status / Department / Author
13 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#3
RRC Drop due to failed HO, and rrcConReEstab-Reject

Note: Handover failure with consequence of RRC-ConnectionReEstab Reject


at target eNB, then QCI1 was deactivated

For internal use Document ID / Version number / Life cycle status / Department / Author
14 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#3
SIP message: Invite message

Voice Traffic Start

SIP signaling message


- Invite message

For internal use Document ID / Version number / Life cycle status / Department / Author
15 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#3
Call Drop due to Handover Failure @ PCI180

Call Drop
C-RNTI: 2425

Failed HO to NLB_SungnamBaekgoongA6(no Emil trace), then continue with rrcConnectionReEstablishment Reject

For internal use Document ID / Version number / Life cycle status / Department / Author
16 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#3
F:\CA Workshop\
Emil Trace @PCI180 (NL_SungnamCholimA2) Mon_0979_10027(Reestablish

!!! EPC sent “UEContextReleaseCommand” to source ENB with


cause “normal release” !!!

Don’t know why eNB don’t sent “UeContextReleaseRequest” with


cause “Tx2Relocoverall Expired” after 500ms or “HO Cancel”
message ??? It’s wait until 1.4sec ???
For internal use Document ID / Version number / Life cycle status / Department / Author
17 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Drop Call Case#3
Deactivate EPS Bearer Context Request
QCI-1 would be deactivated every time after call
drop and come back to service again.

For internal use Document ID / Version number / Life cycle status / Department / Author
18 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
Normal VoLTE Call Drop

Note: Normal VoLTE found in Emil Trace (not UE used for tested)

For internal use Document ID / Version number / Life cycle status / Department / Author
19 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
VoLTE Drop Case # 1
tx2relocoverall-expiry
QCI1,5,8

For internal use Document ID / Version number / Life cycle status / Department / Author
20 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24
VoLTE Drop Case # 2
HO Cancel with cause “unspecified” QCI1,5,8

For internal use Document ID / Version number / Life cycle status / Department / Author
21 Feb 27, 20 ©2013 Nokia Solutions and Networks. All rights reserved.
24

You might also like