You are on page 1of 9

Notice on Precaution for Possible VoLTE Performance Deterioration

When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

Notice on Precaution for Possible VoLTE Performance


Deterioration When Some VoLTE Parameters Are Not Set to
Recommended Values

Sub-Product Line LTE FDD Product Family LTE FDD

Model DBS3900 LTE Release Time 2017-05-17


BTS3900 LTE
BTS3900L LTE
BTS3900A LTE
BTS3900AL LTE
LampSite eNodeB
BTS3202E
BTS3203E
BTS3911E
Severity Major Urgency Urgent

Involved Versions All versions that support VoLTE


(This problem is related to parameter settings rather than product
versions.)
Involved Device eNodeB

Application Scope Global

Operation Type Precaution

Class ID
Operation Set related VoLTE parameters to their recommended values.
Requirement

Completion Time N/A


Manpower Input N/A
Contact Person Service Contact Person Jiang Haoran (00408557; NTD)

R&D Contact Person Wang Hongbo (00385937)

Sub-regional Contact N/A


Person

Rep Office Contact N/A


Person

2021-08-11 Page 1 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

Keywords:
VoLTE, one-way audio, delay, call setup failure

Abstract:
Some VoLTE parameters are not set to their recommended values, which may cause the
following VoLTE problems in elevators, tunnels, or in other areas with weak coverage,
strong interference, or heavy traffic:
 Call setup failures
 Long call setup delay
 One-way audio
There have been user complaints due to inappropriate VoLTE parameter settings on the
live network.

[Problem Description]
Problem 1:
The PDCP SN Size and RLC SN Size parameters are set to inappropriate values for
QCI 1 bearers. As a result, one-way audio occurs in VoLTE services in either of the
following scenarios:
 A UE moves into an elevator or a tunnel where there is no LTE coverage.
 The network traffic is heavy.
Triggering conditions:
The PDCP SN Size and RLC SN Size parameters are respectively set to 7 and 5 for
QCI 1 bearers.
Fault symptom:
When a UE processing an ongoing VoLTE call moves into an elevator or tunnel with no
LTE coverage for more than 2.56s or when the network traffic is heavy, there is a low
probability that the eNodeB will retransmit packets after a long delay. If this occurs,
inconsistent hyper frame numbers (HFNs) on the eNodeB and UE sides cause PDCP
decryption to fail, resulting in one-way audio.
Identification method:
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network.
 In versions earlier than eRAN11.1, run the following command and
obtain the value of RLC PDCP parameter group ID from the command output:
LST STANDARDQCI: Qci=QCI1;
 In eRAN11.1 and later versions, run the LST
GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.
- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=1;

2021-08-11 Page 2 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI1;

Step 2 Run the following command to query the values of parameters related to PDCP/RLC
SN size:
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
In the command output, check whether the values of UM PDCP-SN size(bit), Uplink
RLC-Sn size(bit), and Downlink RLC-SN size(bit) are respectively 7, 5, and 5.
If they are, the triggering conditions are met.
----End

Problem 2:
The PDCP discard timer for QCI 5 bearers is set to an inappropriate value. As a result,
VoLTE call setup fails in weak coverage scenarios.
Triggering conditions:
The PDCP discard timer for QCI 5 bearers is set to an excessively small value (for
example, less than 300 ms).
Fault symptom:
Possible symptom in the downlink:
QCI 5 packets are received by the eNodeB during the DRX sleeping period (the default
DRX period for QCI 5 is 320 ms). They are not sent promptly and therefore are
discarded by the eNodeB.
Possible symptom in the uplink:
The UE is in a weak-coverage area, and QCI 5 packets are fragmented into too many
pieces. These packets are not sent before the PDCP discard timer expires and are
discarded.
Identification method:
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network by
running related MML commands.
 In versions earlier than eRAN11.1, run the following command:
LST STANDARDQCI: Qci=QCI5;

 In eRAN11.1 and later versions, run the LST


GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.
- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=5;

2021-08-11 Page 3 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI5;

Step 3 Run the following command to query the value of Discard timer(ms):
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
In the command output, check whether the value of Discard timer(ms) is infinity.
If it is not, the triggering conditions are met.
----End

Problem 3:
Parameters related to the maximum number of RLC retransmission times for QCI 5
bearers are set to inappropriate values. As a result, VoLTE call setup fails in areas with
weak coverage or strong interference.
Triggering conditions:
Parameters related to the maximum number of RLC retransmission times for QCI 5
bearers are set to an excessively small value (for example, 4).
Fault symptom:
In areas with weak coverage or strong interference, QCI 5 packets may be retransmitted
for the maximum number of retransmission times, causing VoLTE call setup failures.
Identification method:
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network by
running related MML commands.
 In versions earlier than eRAN11.1, run the following command:
LST STANDARDQCI: Qci=QCI5;

 In eRAN11.1 and later versions, run the LST


GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.
- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=5;

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI5;

Step 4 Run the following command to query the values of parameters related to the maximum
number of RLC retransmission times:
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.

2021-08-11 Page 4 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

In the command output, check whether the values of MaxretxThreshold for UE and
MaxRetxThreshold for eNodeB are both 32.
If they are not, the triggering conditions are met.
----End

Problem 4:
The uplink compensation scheduling switch for VoLTE services is turned off, causing
poor voice quality in strong interference scenarios.
Triggering conditions:
The uplink compensation scheduling switch for VoLTE services is turned off.
Fault symptom:
When there is strong interference in the uplink, the eNodeB may skip some scheduling
requests (SRs) sent by UEs. If this occurs, the eNodeB cannot schedule uplink voice
packets promptly and packet loss may occur in the uplink, affecting voice quality.
Identification method:
Run the LST CELLULSCHALGO command. In the command output, check whether
the value of UlVoipSchOptSwitch in the Uplink Enhanced VoIP Schedule Switch
parameter is On.
If they are not, the triggering conditions are met.
Problem 5:
Parameters related to the scheduling request indicator (SRI)-based gap optimization
switch are turned off. As a result, there is a low probability of one-way audio occurring
in VoLTE services when network traffic is heavy.
Triggering conditions:
Parameters related to the SRI-based gap optimization switch are turned off.
Fault symptom:
When network traffic is heavy, the UE SR period expands to 40 ms. If the UE uses the
gap for inter-frequency measurement, SRs may be generated during the gap period, and
the UE will be unable to report them. In this scenario, there are very few scheduling
chances, and packet loss is extensive, or there is even one-way audio.
Identification method:
Run the LST ENODEBALGOSWITCH command. In the command output, check
whether the values of BasedSriGapOptSwitch and DrxBasedSriGapOptSwitch in the
Handover Common Optimized Switch parameter are both On.
If they are not, the triggering conditions are met.

[Root Cause]
 For Problem 1

2021-08-11 Page 5 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

When a UE processing an ongoing VoLTE call moves into an elevator or tunnel


with no LTE coverage for more than 2.56s or when the network traffic is heavy,
there is a low probability that the eNodeB will retransmit packets after a long
delay. If this occurs, PDCP decryption fails due to inconsistent HFNs on the
eNodeB and UE sides, causing one-way audio.
 For Problem 2
Possible cause in the downlink:
QCI 5 packets are received by the eNodeB during the DRX sleeping period (the
default DRX period for QCI 5 is 320 ms). They are not sent promptly and therefore
are discarded by the eNodeB.
Possible cause in the uplink:
The UE is in a weak-coverage area, QCI 5 packets are fragmented into too many
pieces. These packets are not sent before the PDCP discard timer expires and are
discarded.
 For Problem 3
In areas with weak coverage or strong interference, QCI 5 packets may be
retransmitted for the maximum number of retransmission times, causing VoLTE
call setup failures.
 For Problem 4
When there is strong interference in the uplink, the eNodeB may skip some SRs
sent by UEs. If this occurs, the eNodeB cannot schedule uplink voice packets
promptly and packet loss may occur in the uplink, affecting voice quality.
 For Problem 5
When network traffic is heavy, the UE SR period expands to 40 ms. If the UE uses
the gap for inter-frequency measurement, SRs may be generated during the gap
period, and the UE will be unable to report them. In this scenario, there are very
few scheduling chances, and packet loss is extensive, or there is even one-way
audio.

[Impact and Risk]


If VoLTE parameters are not set to their recommended values, there is a low probability
that there will be VoLTE call setup failures, long call delay, or one-way audio on the
network. These problems may trigger user complaints.

[Measures and Solutions]


Recovery measures:
N/A
Workarounds:
For Problem 1:
Set PDCP SN Size and RLC SN Size respectively to 12 and 10 for QCI 1 bearers.
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network.
 In versions earlier than eRAN11.1, run the following command:
LST STANDARDQCI: Qci=QCI1;

2021-08-11 Page 6 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

 In eRAN11.1 and later versions, run the LST


GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.
- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=1;

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI1;

Step 5 Run the following command to query the values of parameters related to PDCP/RLC
SN size:
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
Step 6 If the values of UM PDCP-SN size(bit), Uplink RLC-Sn size(bit), and Downlink
RLC-SN size(bit) are respectively 7, 5, and 5 in the command output, run the following
command to change the parameter values:
MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X, RlcMode=RlcMode_UM,
PdcpSnSize=PdcpSnsize_12bits, UlRlcSnSize=RlcSnSize_size10,
DlRlcSnSize=RlcSnSize_size10;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
Step 7 To prevent any UE incompatibility issues due to inconsistent settings of parameters
related to PDCP/RLC SN size for QCI 1 bearers on the entire network, turn on the RLC
SN size switch.
 In versions earlier than eRAN11.1, run the following command to turn
on the switch (a reserved parameter):
MOD ENBRSVDPARA: RsvdSwPara1=RsvdSwPara1_bit24-1;

 In eRAN11.1 and later versions, run the following command to turn on


the switch (an official parameter):
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=HoRlcSnSizeSwitch-1;

----End

For Problem 2:
Set the PDCP discard timer to infinity for QCI 5 bearers.
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network by
running related MML commands.
 In versions earlier than eRAN11.1, run the following command:
LST STANDARDQCI: Qci=QCI5;

 In eRAN11.1 and later versions, run the LST


GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.

2021-08-11 Page 7 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=5;

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI5;

Step 8 Run the following command to query the value of Discard timer(ms):
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
Step 9 If the value of Discard timer(ms) is not infinity in the command output, run the
following command to change the parameter value to DiscardTimer_Infinity:
MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X,
DiscardTimer=DiscardTimer_Infinity;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
----End

For Problem 3:
Set parameters related to the maximum number of RLC retransmission times for QCI 5
bearers to 32.
Step 1 Query the RLC PDCP parameter group ID for QCI 1 bearers on the live network by
running related MML commands.
 In versions earlier than eRAN11.1, run the following command:
LST STANDARDQCI: Qci=QCI5;

 In eRAN11.1 and later versions, run the LST


GLOBALPROCSWITCH command to query the value of QCI Parameter
Effect Flag.
- If the value is ON, run the following command to query the RLC PDCP
parameter group ID:
LST QCIPARA: Qci=5;

- If the value is OFF, run the following command to query the RLC PDCP
parameter group ID:
LST STANDARDQCI: Qci=QCI5;

Step 10 Run the following command to query the values of parameters related to the maximum
number of RLC retransmission times:
LST RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
Step 11 If the values of MaxretxThreshold for UE and MaxRetxThreshold for eNodeB are
not 32 in the command output, run the following command to change them to 32:

2021-08-11 Page 8 of 9
Notice on Precaution for Possible VoLTE Performance Deterioration
When Some VoLTE Parameters Are Not Set to Recommended Values INTERNAL

MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X, RlcMode=RlcMode_AM,


UeMaxRetxThreshold=Maxretx_Threshold_t32,
ENodeBMaxRetxThreshold=Maxretx_Threshold_t32;

In this step, set RLC PDCP parameter group ID to the value queried in step 1.
----End

For Problem 4:
Run the following command to turn on the uplink compensation scheduling switch for
VoLTE services:
MOD CELLULSCHALGO: UlEnhencedVoipSchSw=UlVoipSchOptSwitch-1;

For Problem 5:
Run the following command with both BasedSriGapOptSwitch and
DrxBasedSriGapOptSwitch in the Handover Common Optimized Switch parameter
set to On so that the gap and SRI do not conflict:
MOD ENODEBALGOSWITCH: HoCommOptSwitch=BasedSriGapOptSwitch-
1&DrxBasedSriGapOptSwitch-1;

Solutions:
Set the VoLTE parameters to their recommended values.
Changing the parameter values has no impact on live-network KPIs.

2021-08-11 Page 9 of 9

You might also like