SR5667066 Root Cause Analysis For KPI Changed After VoLTE Enable in Zain Kuwait

SR5667066 Root Cause Analysis for
KPI changed after VoLTE enable in

Zain Kuwait
Issue 01
Date 2016-01-23
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Issue 01 (2016-01-23) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co.,
Ltd
Trademarks and Permissions
And other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either expressed or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Web site: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2016-01-23) Huawei Proprietary and Confidential ii

Ltd
SR5667066 Root Cause Analysis for KPI changed after
VoLTE enable in Zain Kuwait Contents
1 About This Document
Trouble Ticket Information
Trouble Ticket 5667066

Number
Prepared by Wangzhijian 00167848
Approved by Zhangjun 00152386
Approval Date 2016-1-24
Revision History
This chapter is optional.
Issue Date Author Change Description
01 2016-01-23 Wangzhijian This is the first issue
Issue 01 (2016-01-23) Huawei Proprietary and Confidential iii

Ltd
VoLTE enable in Zain Kuwait Contents
2 Contents
About This Document...................................................................................................................iii

1 Basic Information.......................................................................................................................1-1
2 Problem Description..................................................................................................................2-1
3 Problem Analysis.......................................................................................................................3-1
3.1 Operation Confirm PUSCHDTX cause KPI changed....................................................................................3-1
3.1.1 Operation influence analysis.................................................................................................................3-1
3.1.2 Live network trial confirm PUSCHDTX caused KPI changed.............................................................3-3
3.2 Call Drop Aanalysis........................................................................................................................................3-4
3.2.1 DRBReset and other reason cause call drop increase...........................................................................3-4
3.2.2 Top type UE caused other reason call drop...........................................................................................3-5
3.2.3 DTX Error detections cause Call drop..................................................................................................3-6
3.3 Uplink Ibler changed analysis........................................................................................................................3-8
3.4 Clarification document for PUSCHDTX.......................................................................................................3-9
4 Root Cause...................................................................................................................................4-1
5 Corrective Action........................................................................................................................5-1
5.1 Workaround....................................................................................................................................................5-1
5.2 Solution...........................................................................................................................................................5-1
6 Preventive Action.......................................................................................................................6-1
Issue 01 (2016-01-23) Huawei Proprietary and Confidential iv

Ltd
VoLTE enable in Zain Kuwait 3 Problem Analysis
3 Basic Information
Product Name Version
BTS3900 V100R010C10SPC190
Issue 01 (2016-01-23) Huawei Proprietary and Confidential 1

Ltd
4 Problem Description
ZAIN Kuwait, V100R010C10SPC190, live network active VoLTE at January 11th, but after
enable VoLTE, some KPI changed, including call drop, uplink packet loss, uplink Ibler.
Figure1 Call drop rate deteriorate

Ltd
Figure2 Uplink IBLER increase

Ltd
5 Problem Analysis
5.1 Operation Confirm PUSCHDTX cause KPI changed

From the operation log for VoLTE enable, there are just four command will influence the PS
data service, and other command just influence the voice service. But from the counter, the no
voice user in the live network, so it can confirm that just one or more command in this four
commands caused KPI changed. The four commends are:
5.1.1 Operation influence analysis

1. Changed the B1 threshold from -103 to -95;
Figure3 Operation log shows B1 threshold changed
Influence analysis in theory:
B1 changed from -103 to -95, it means UE need better coverage for UMTS when UE move to
UTRAN. This caused many UE can’t move to UTRAN because of B1 threshold not meet.
And more UE locate weak coverage, it may cause call drop, demodulation fail and so on.
2. Enable UlLast2RetransSchOptSwitch and DlRetxTbsIndexAdjOptSwitch

Ltd
Figure4 Enable retransmission optimization

This two switch used for retransmission optimization, when data packet transmission fail, for
last two retransmission, eNodeB will select lower MCS, which will increase the transmission
success rate. It just has benefit.
3. Power control switch
Figure5 Power control switch

It changed may influence the interference level and eNodeB’s PUCCH demodulation. So, it
also may cause many abnormal.
4. PUSCH DTX Detection Switch
Figure6 PUSCH DTX Detection Switch
Influence analysis in theory (See the figure below):

Ltd
PUSCH DTX OFF: While DCI0 on PDCCH miss detection, there is no data transmission on
PUSCH. The eNB sends a NACK and wait for the retransmission on PUSCH, which leads to
a waste for the PUSCH RB.
PUSCHDTX ON: eNB can detect it as PUSCH DTX. If DTX is detected, New Transmission
is performed. While NACK detected, retransmission is performed thus resource is wasted.
Pros: This could save PUSCH RB and improve UL throughput.

Cons: PUSCH DTX may have error detections, which results in PDCCH UL grant waste and
retransmission gain loss.
Figure7 DTX detection switch theory
Above all, B1, power control and PUSCH DTX switch may cause KPI changed. Next step,
we should find which one is main reason.
5.1.2 Live network trial confirm PUSCHDTX caused KPI changed

1. For B1 threshold
See the figure below, the B1 roll back at Jan 13th, the call drop rate become well, but not
returns the original level. So, B1 threshold setting is one of the reasons for Call drop. But it is
not the main reason.

Ltd
2. for power control
These parameter bad been executed at December 14th. And for Jan 11th, the parameters are the
same as Dec 14th. It can exclude the power control influence.
So, the KPI changed must be influenced by PUSCH DTX Detection switch.
5.2 Call Drop Aanalysis

5.2.1 DRBReset and other reason cause call drop increase
This figure shows the reasons for call drop. It is obvious that L.E-RAB.Abnormal. Radio
reason increased, which caused call drop rate deteriorated.

Ltd
Figure8 Call Drop Reason Analysis
Analysis the sub-reason for L.E-RAB.Abnormal.Radio, as figure 8 shows, DRBReset and

other reason increase obviously.
Figure9 Sub reason analysis for Radio reason
5.2.2 Top type UE caused other reason call drop

This figure shows the internal call drop reason in CHR, it is shows the main reason for call
drop is “UEM_UECNT_REL_PDCP_INTEG_CHECK_FAIL _IND”, which means PDCP
check the integrality fail.
Figure10 Call Drop reason in internal
Check the UE type, it shows 146 times “UEM_UECNT_REL_PDCP_INTEG_CHECK_FAIL

_IND” caused by one type UE and the UE feature capability is:
“0x24;FFCFFEB8;0000000900DF;00000093;0560”. This sentence means this UE is Release
10 and Category 4; the FGI is FFCFFEB8; the UE support LTE Band is

Ltd
band1/2/3/4/5/7/8/17/20; the UE support UTRAN band is Band1/2/3/7/9; the UE support

GSM band is 1900,1800,900E,900P,750.
Figure11 Top type UE cause “UEM_UECNT_REL_PDCP_INTEG_CHECK_FAIL _IND”
It is clear, top type UE caused call drop, which also found in other operator like: Saudi Arabia
ZAIN, The United Arab Emirates DU, and Malaysia. And for this issue need get the UE log
and ask UE manufacturer for help.
5.2.3 DTX Error detections cause DRBReset Call drop

Counter definition:
L.E-RAB.AbnormRel.Radio.DRBReset counter is incremented each time the E-RABs are

released because the RLC PDU for a DRB has been retransmitted for the maximum number of
times.
According to this counter definition, check the downlink schedule. It shows that before the
RLC reach maximum retransmission, all downlink PDU’s HARQ feedback is ACK in
PUCCH. And no PDU with 4 times HARQ re-transmission. By this confirm that downlink is
OK, and RLC status report not received.

Ltd
Figure12 Downlink transmit HARQ Feedback is OK
RLC status report is transmitted through PUSCH, so next step need to check uplink schedule
and confirm why RLC status report not received. Check the uplink schedule trace, it shows
before call drop, many DTX had been detected, but air-condition is not bad.
Figure13 Uplink shows many schedule detected as DTX by eNodeB
Next step, should check why DTX be detected by eNodeB. Check the baseband trace, it
shows this UE signal fluctuates (EquSinr and Rsrp column) obviously. And sometimes this
UE have big the noise and interference (NP column) which leads to eNodeB detects DTX.

Ltd
Figure14 Air condition fluctuate or interference
Because of the DTX detection mechanism, when eNodeB detect the DTX, eNodeB just
trigger one times adaptive re-transmission, compare with the DTX off (MAC layer have 4
times re-transmission), it lost HARQ re-transmission chance and easier to call drop.
5.3 Uplink Ibler changed analysis

As said in chapter 3.1.1, PUSCH DTX Detection switch changed the schedule mechanism.
When eNodeB detect the DTX, if adaptive retransmission enabled, one more re-transmission
triggered else it will not trigger HARQ retransmission and wait the next times initial
transmission.
By this mechanism, UE lost the retransmission benefit. For example (see the figure below),
one packet transmits fail, and after 3 times re-transmission gets success. When DTX detection
disabled, can trigger HARQ retransmission and get success after one initial transmission. But
if DTX detection enabled, this packet need more 3 times initial transmission, which the first
two initial transmissions is fail, then IBLER increased.

Ltd
Figure15 One example for Uplink Ibler
5.4 Clarification document for PUSCHDTX

For PUSCH DTX detection algorithm, there are two clarification document for explain the
PUSCH DTX detection theory.

Ltd
6 Root Cause
For Call drop increase is caused by TOP UE after PUSCH DTX detection switch which also
found in other operator.
For IBLER increase and call drop increase are caused by re-transmission benefit lost after
PUSCH DTX detection enabled and eNodeB detect DTX.

Ltd
7 Corrective Action
7.1 Workaround
NA
7.2 Solution
Roll back the switch "PUSCHDTXSWITCH” and the MML is:
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=PuschDtxSwitch-0;
Influence:
Roll back this switch will return the KPI to before PUSCH DTX swtich enable. And this
switch is not the necessary parameter for VOIP enable.

Ltd
8 Preventive Action
NA

Ltd

SR5667066 Root Cause Analysis For KPI Changed After VoLTE Enable in Zain Kuwait

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SR5667066 Root Cause Analysis For KPI Changed After VoLTE Enable in Zain Kuwait

Uploaded by

Copyright:

Available Formats

SR5667066 Root Cause Analysis for

KPI changed after VoLTE enable in

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.

Issue 01 (2016-01-23) Huawei Proprietary and Confidential i

Huawei Technologies Co., Ltd.

Web site: http://www.huawei.com

Issue 01 (2016-01-23) Huawei Proprietary and Confidential ii

1 About This Document

Trouble Ticket Information

Trouble Ticket 5667066

Prepared by Wangzhijian 00167848

Approved by Zhangjun 00152386

Approval Date 2016-1-24

Issue Date Author Change Description

01 2016-01-23 Wangzhijian This is the first issue

Issue 01 (2016-01-23) Huawei Proprietary and Confidential iii

About This Document...................................................................................................................iii

Issue 01 (2016-01-23) Huawei Proprietary and Confidential iv

Product Name Version

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 1

Figure1 Call drop rate deteriorate

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 1

Figure2 Uplink IBLER increase

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 2

5.1 Operation Confirm PUSCHDTX cause KPI changed

5.1.1 Operation influence analysis

Figure3 Operation log shows B1 threshold changed

Influence analysis in theory:

2. Enable UlLast2RetransSchOptSwitch and DlRetxTbsIndexAdjOptSwitch

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 1

Figure4 Enable retransmission optimization

Influence analysis in theory:

3. Power control switch

Figure5 Power control switch

Influence analysis in theory:

4. PUSCH DTX Detection Switch

Figure6 PUSCH DTX Detection Switch

Influence analysis in theory (See the figure below):

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 2

Pros: This could save PUSCH RB and improve UL throughput.

Figure7 DTX detection switch theory

5.1.2 Live network trial confirm PUSCHDTX caused KPI changed

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 3

2. for power control

5.2 Call Drop Aanalysis

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 4

Figure8 Call Drop Reason Analysis

Analysis the sub-reason for L.E-RAB.Abnormal.Radio, as figure 8 shows, DRBReset and

Figure9 Sub reason analysis for Radio reason

5.2.2 Top type UE caused other reason call drop

Figure10 Call Drop reason in internal

Check the UE type, it shows 146 times “UEM_UECNT_REL_PDCP_INTEG_CHECK_FAIL

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 5

band1/2/3/4/5/7/8/17/20; the UE support UTRAN band is Band1/2/3/7/9; the UE support

Figure11 Top type UE cause “UEM_UECNT_REL_PDCP_INTEG_CHECK_FAIL _IND”

5.2.3 DTX Error detections cause DRBReset Call drop

L.E-RAB.AbnormRel.Radio.DRBReset counter is incremented each time the E-RABs are

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 6

Figure12 Downlink transmit HARQ Feedback is OK

Figure13 Uplink shows many schedule detected as DTX by eNodeB

Issue 01 (2016-01-23) Huawei Proprietary and Confidential 7

Figure14 Air condition fluctuate or interference