Retainbility

Content

Retainability
 RRC Connection Release
 E-RAB Release
 UE Context Release
 Procedure
 Release Causes
 Drop Rate
RRC Connection Release (Procedure)
EPC initiated Release MME

UE in Connected Mode
UE Context Release Command

RRC Connection Release (SRB1, DCCH)

See 3GPP 36.413
RRC Connection Release Complete section 8.3.3.2
Release radio Release UE
resources and
See 3GPP 36.331
section 5.3.8.1 associated radio
enter RRC_IDLE resources
UE Context Release Complete
Sampling Point:
• The EUTRAN sends the RRC
CONNECTION RELEASE message
to the UE.
RRC Connection Release (Causes)

According 3GPP 36.331 section 6.2.2 there are the following release causes only
• LoadBalancingTAUrequired
• cs-FallbackHighPriority
• other

To get information about call drops and their causes, according 3GPP the E-RAB
or UE context must be considered

In practise specific analysis for RRC connection release hardly needed

With release of UE context simultaneously RRC connection released as well
E-RAB Release (eNodeB Triggered)
eNodeB initiated release
(not all E-RAB released) MME

UE in Connected Mode
E-RAB Release Indication

E-RAB to be released list

E-RAB Release Command
Release corresponding
local resources See 3GPP 36.413
section 8.2.3.2
RRC Connection Reconfiguration
Procedure E-RAB Release Response
E-RAB released list
E-RAB failed to release list

➢ The E-RAB Release function provides the ability to release one or several E-RABs for one UE
➢ The release of E-RABs can be initiated by the eNodeB
E-RAB Release (MME Triggered)
MME initiated E-RAB release
(not all E-RAB released)

MME
E-RAB Release Command
E-RAB to be released list
Release corresponding
local resources
See 3GPP 36.413
RRC Connection Reconfiguration section 8.2.3.2
Procedure
E-RAB Release Response
E-RAB release list
E-RAB failed to release list

➢ The E-RAB Release can also be initiated by the MME to release

one or several E-RABs for one UE
Sampling Points (not all E-RAB released)

MME initiated
E-RAB Release MME • The EUTRAN receives the E-RAB
Command 1: RELEASE COMMAND message
1 from the MME.

• The EUTRAN sends the E-RAB

RRC Connection 2:
RELEASE RESPONSE message
Reconfiguration E-RAB Release to the MME, indicating that the E-
Procedure Response RAB Release has been successful.
2

See 3GPP 36.413

section 8.2.3.2

eNB initiated

MME
• The EUTRAN sends the E-RAB
RRC Connection
3: RELEASE Indication message to
E-RAB Release Indication the MME.
Reconfiguration 3
Procedure
Sampling Points (all E-RAB released)
eNB initiated
MME
• The EUTRAN sends the UE
4: Context Release Request
UE context rel. request message to the MME.
4
See 3GPP 36.413
section 8.3.2 and 8.3.3
MME initiated
• The EUTRAN receives the UE
5: Context Release Command
UE context rel. command message from the MME.
5
See 3GPP 36.413
See 3GPP 36.413 section 8.7.2.2
section 8.7.1.2
MME initiated MME detected
error MME
reset MME
Error Indication
Reset 7
6
Reset acknowledge
Sampling Points (UE Context / E-RAB Release)

1 2 3 1 2 3 1 2 1
MME

MME
E-RAB Release Indication
E-RAB id = 3
E-RAB Release Indication
E-RAB id = 2
MME
If not all existing E-RABs shall be released
UE context rel. request
→ just E-RAB release procedure
UE context rel. command

If all existing E-RABs shall be released

→ UE context release procedure
Release Causes (Overall Scenarios)

Normal release and total drop indicated

Per QCI class
Specifically during outgoing HO
Excellent resolution of failure per 3GPP category
Analogue set of counters for all ERAB and for VoLTE

counters
1526727547 L.E-RAB.NormRel All eNodeB initiated normal releases
1526727546 L.E-RAB.AbnormRel All eNodeB initiated abnormal releases
1526727547 L.E-RAB.Rel.MME All MME initiated normal + abnormal releases
1526728292 L.E-RAB.AbnormRel.MME All MME initiated abnormal releases
1526728246 L.E-RAB.NormRel.HOOut All normal releases during HO
1526728247 L.E-RAB.AbnormRel.Hoout All abnormal releases during HO
1526728827 L.E-RAB.Rel.S1Reset.eNodeB eNodeB initiated S1 reset (neither normal / abnormal)
1526728837 L.E-RAB.Rel.S1Reset.MME MME initiated S1 reset (neither normal / abnormal)
Release Causes (Overall Scenarios)

counters
1526726687 L.E-RAB.NormRel.QCI.1
1526726689 L.E-RAB.NormRel.QCI.2
1526726691 L.E-RAB.NormRel.QCI.3
1526726693 L.E-RAB.NormRel.QCI.4
1526726695 L.E-RAB.NormRel.QCI.5
1526726697 L.E-RAB.NormRel.QCI.6 Normal releases within whole cell
1526726699 L.E-RAB.NormRel.QCI.7 per QCI (QCI 67 and 68 missing)
1526726701 L.E-RAB.NormRel.QCI.8 eNodeB + MME initiated
1526726703 L.E-RAB.NormRel.QCI.9
1526741993 L.E-RAB.NormRel.QCI.65
1526741994 L.E-RAB.NormRel.QCI.66
1526741995 L.E-RAB.NormRel.QCI.69
1526741996 L.E-RAB.NormRel.QCI.70
Release Causes (Overall Scenarios)

counters
1526726686 L.E-RAB.AbnormRel.QCI.1
1526726688 L.E-RAB.AbnormRel.QCI.2
1526726690 L.E-RAB.AbnormRel.QCI.3
1526726692 L.E-RAB.AbnormRel.QCI.4
1526726694 L.E-RAB.AbnormRel.QCI.5
1526726696 L.E-RAB.AbnormRel.QCI.6 Abnormal releases within whole cell
1526726698 L.E-RAB.AbnormRel.QCI.7 per QCI (QCI 67 and 68 missing)
1526726700 L.E-RAB.AbnormRel.QCI.8 eNodeB + MME initiated
1526726702 L.E-RAB.AbnormRel.QCI.9
1526741989 L.E-RAB.AbnormRel.QCI.65
1526741990 L.E-RAB.AbnormRel.QCI.66
1526741991 L.E-RAB.AbnormRel.QCI.69
1526741992 L.E-RAB.AbnormRel.QCI.70
Release Causes (Overall Scenarios)

counters
1526727317 L.E-RAB.NormRel.HOOut.QCI.1
1526727318 L.E-RAB.NormRel.HOOut.QCI.2
1526727319 L.E-RAB.NormRel.HOOut.QCI.3
1526727320 L.E-RAB.NormRel.HOOut.QCI.4
1526727321 L.E-RAB.NormRel.HOOut.QCI.5
1526727322 L.E-RAB.NormRel.HOOut.QCI.6 Normal releases during HO per
1526727323 L.E-RAB.NormRel.HOOut.QCI.7 QCI (QCI 67 and 68 missing)
1526727324 L.E-RAB.NormRel.HOOut.QCI.8 eNodeB + MME initiated
1526727325 L.E-RAB.NormRel.HOOut.QCI.9
1526742026 L.E-RAB.NormRel.HOOut.QCI.65
1526742027 L.E-RAB.NormRel.HOOut.QCI.66
1526742028 L.E-RAB.NormRel.HOOut.QCI.69
1526742029 L.E-RAB.NormRel.HOOut.QCI.70
Release Causes (Overall Scenarios)

counters
1526727326 L.E-RAB.AbnormRel.HOOut.QCI.1
1526727327 L.E-RAB.AbnormRel.HOOut.QCI.2
1526727328 L.E-RAB.AbnormRel.HOOut.QCI.3
1526727329 L.E-RAB.AbnormRel.HOOut.QCI.4
1526727330 L.E-RAB.AbnormRel.HOOut.QCI.5
1526727331 L.E-RAB.AbnormRel.HOOut.QCI.6 Abnormal releases during HO
1526727332 L.E-RAB.AbnormRel.HOOut.QCI.7 per QCI (QCI 67 and 68 missing)
1526727333 L.E-RAB.AbnormRel.HOOut.QCI.8 eNodeB + MME initiated
1526727334 L.E-RAB.AbnormRel.HOOut.QCI.9
1526742030 L.E-RAB.AbnormRel.HOOut.QCI.65
1526742031 L.E-RAB.AbnormRel.HOOut.QCI.66
1526742032 L.E-RAB.AbnormRel.HOOut.QCI.69
1526742033 L.E-RAB.AbnormRel.HOOut.QCI.70
Release Causes (Detail Analysis)

causes normal release

1526737848 L.E-RAB.Rel.eNodeB.Userinact User inactivity

For following normal release 3GPP causes no counters yet

Normal release
UE not available for PS service
Detach
Successful HO
OaM intervention

The following normal release 3GPP causes are discussed in next chapter
Inter-RAT redirection triggered
CSFB triggered
Release Causes (Detail Analysis)

causes drop
1526728282 L.E-RAB.AbnormRel.Radio All radio network layer failures
1526729549 L.E-RAB.AbnormRel.Radio.SRBReset RLC retransmission timeout for SRB
1526729550 L.E-RAB.AbnormRel.Radio.DRBReset RLC retransmission timeout for DRB
1526729551 L.E-RAB.AbnormRel.Radio.UlSyncFail UL synchronization failure
1526729552 L.E-RAB.AbnormRel.Radio.UuNoReply No feedback from UE
1526732940 L.E-RAB.AbnormRel.Radio.Other Other RNL failures

1526728291 L.E-RAB.AbnormRel.HOFailure HO failure (NOT included in RNL failures)

1526728284 L.E-RAB.AbnormRel.Cong RNL congestion (NOT included in RNL failures)

1526729912 L.E-RAB.AbnormRel.Cong.PreEmp Radio resource triggered preemption
1526729913 L.E-RAB.AbnormRel.Cong.Load Radio resource overload
1526732944 L.E-RAB.AbnormRel.Cong.Other Other RNL congestion problem
Release Causes (Detail Analysis)

causes drop
1526728283 L.E-RAB.AbnormRel.TNL All transport network layer failures
1526729914 L.E-RAB.AbnormRel.TNL.PreEmp Transport resource triggered preemption
1526729915 L.E-RAB.AbnormRel.TNL.Load Transport resource overload
1526732942 L.E-RAB.AbnormRel.TNL.Other Other TNL failures

1526732938 L.E-RAB.AbnormRel.Other Other eNodeB detected failure

1526729911 L.E-RAB.AbnormRel.MMEEUtranGen MME detected EUTRAN generated reason

Release Causes (Detail Analysis)

causes drop VoLTE

1526729921 L.E-RAB.AbnormRel.Radio.VoIP All radio network layer failures
1526729917 L.E-RAB.AbnormRel.Radio.SRBReset.VoIP RLC retransmission timeout for SRB
1526729919 L.E-RAB.AbnormRel.Radio.UlSyncFail.VoIP UL synchronization failure
1526729918 L.E-RAB.AbnormRel.Radio.UuNoReply.VoIP No feedback from UE
1526732941 L.E-RAB.AbnormRel.Radio.Other.VoIP Other RNL failures

1526730862 L.E-RAB.AbnormRel.UlWeak.VoIP Weak UL coverage (NOT in RNL failures)

1526729922 L.E-RAB.AbnormRel.HOFailure.VoIP HO failure (NOT in RNL failures)

1526729923 L.E-RAB.AbnormRel.Cong.VoIP RNL congestion (NOT in RNL failures)

1526729926 L.E-RAB.AbnormRel.Cong.PreEmp.VoIP Radio resource triggered preemption
1526729927 L.E-RAB.AbnormRel.Cong.Load.VoIP Radio resource overload
1526732945 L.E-RAB.AbnormRel.Cong.Other.VoIP Other RNL congestion problem
Release Causes (Detail Analysis)

causes drop VoLTE

1526729925 L.E-RAB.AbnormRel.TNL.VoIP All transport network layer failures
1526729928 L.E-RAB.AbnormRel.TNL.PreEmp.VoIP Transport resource triggered preemption
1526729929 L.E-RAB.AbnormRel.TNL.Load.VoIP Transport resource overload
1526732943 L.E-RAB.AbnormRel.TNL.Other.VoIP Other TNL failures

1526732939 L.E-RAB.AbnormRel.Other.VoIP Other eNodeB detected failure

1526729920 L.E-RAB.AbnormRel.MMEEUtranGen.VoIP MME detected EUTRAN generated reason

Call Drop Rate
General definition
CDR = Number of abnormal release
Number of normal releases + number of abnormal releases

One might distinguish further on between drops from user and network view
Drops from user view = all drops
Drops from network view = drops due to faulty network behavior

Following procedures are compatible with correct network behavior, but cause drop
from user view
Redirection → service is released (e.g. due to poor coverage) and must be reestablished within
target layer to which UE is redirected (vendors / 3GPP consider redirection as
normal cause)
Preemption → service is released because incoming service of higher priority wants to enter
heavily loaded cell (vendors / 3GPP consider preemption as abnormal cause)

Number of abnormal release – redirections – preemptions

CDR net = Number of normal releases + number of abnormal releases
Call Drop Rate (Example)

Number of cells versus ERAB drop rate

[%] from user view
Most cells have call drop rate < 10 %

Number of cells versus ERAB drop rate

[%] from network view
Most cells have call drop rate < 2 %
Call Drop Rate (Example)

All call drops due

to redirection

Half the call drops

due to redirection

CDR user view due to redirection [%] versus total CDR user view [%]
Each point = 1 cell
Most ERAB drops due to redirection
Call Drop Rate (Example)

All call drops due to

radio link failure

Half the call drops due

to radio link failure

CDR user view due to radio link failure [%] versus total CDR user view [%]
Each point = 1 cell
Radio link failure significant root cause for call drop as well
Content
Retainability
 RRC Connection Release
 E-RAB Release
 UE Context Release
 Procedure
 Release Causes
 Drop Rate
UE Context Release (eNodeB Triggered)

eNodeB initiated release

MME

UE in Connected Mode

eNodeB decides to request UE-

associated S1-connection release

UE Context Release Request

UE Context Release Command

RRC Conn. Release (SRB1, DCCH)
eNode B releases UE associated
RRC Connection Release Complete local resources
Release radio resources UE Context Release Response
and enter RRC_IDLE
See 3GPP 36.413
section 8.2.3.2
UE Context Release (MME Triggered)

MME initiated release MME

UE in Connected Mode
UE Context Release Command

RRC Connection Release Procedure

eNode B releases UE
associated local resources
UE Context Release Complete

See 3GPP 36.413

section 8.2.3.2
Causes (Main Procedure)

According 3GPP 36.413 section 9.2.1.3 UE context release failures

classified according the same categories as UE context setup failure
Radio network layer Transport layer NAS
Protocol Miscellaneous

For each category again there are the same detail causes
Release Causes (Overall Scenarios)

Much lower resolution of root causes in comparison to ERAB drop

counters
1526728228 L.UECNTX.NormRel All normal releases
1526728227 L.UECNTX.AbnormRel All abnormal releases
1526728856 L.UECNTX.Rel.eNodeB All eNodeB initiated releases
1526728861 L.UECNTX.Rel.MME All MME initiated releases
1526739720 L.UECNTX.Rel.MME.AbnormRel MME initiated abnormal releases
1526728838 L.UECNTX.Rel.S1Reset.eNodeB eNodeB initiated S1 reset (neither normal / abnormal)
1526728839 L.UECNTX.Rel.S1Reset.MME MME initiated S1 reset (neither normal / abnormal)
Release Causes (Detail Analysis)

causes normal release

1526728862 L.UECNTX.Rel.MME.Normalrel Normal release
1526728858 L.UECNTX.Rel.eNodeB.Userinact User inactivity
1526728440 L.UECNTX.Release.HighSpeed High UE mobility

For other normal release 3GPP causes no counters yet

UE not available for PS service
Detach
Time critical HO
HO cancelled
OaM intervention

The following normal release 3GPP causes are discussed in next chapter
Inter-RAT redirection triggered
CSFB triggered
Release Causes (Detail Analysis)

causes drop
1526728857 L.UECNTX.Rel.eNodeB.Rnl All RNL failures
1526728859 L.UECNTX.Rel.eNodeB.UeLost Radio connection with UE lost
1526728860 L.UECNTX.Rel.eNodeB.HOFailure HO failure

1526730863 L.UECNTX.AbnormRel.UlWeak Weak UL coverage (NOT in RNL failures)

1526737847 L.UECNTX.Rel.eNodeB.InitAttEst.MMENoReply Expiration of initial context setup request

1526742148 L.UECNTX.Rel.eNodeB.CallMute UL mute call

Call Drop Rate (Example)

Number of cells versus UE context drop rate [%] from network view
Much higher than ERAB drop rate
Few cells better than 5%, many even worse than 10%
Call Drop Rate (Example)

All call drops due to

radio link failure

Half the call drops due

to radio link failure

CDR network view due to radio link failure [%] versus total CDR network view [%]
Each point = 1 cell
Radio link failure here plays a minor role only
Call Drop Rate (Example)

All call drops due

to EPC failure

Half the call drops

due to EPC failure

CDR network view due to EPC failure [%] versus total CDR network view [%]
Each point = 1 cell
Most UE context drops due to EPC failure, not due to air interface
Solution to Service-Drop-related KPIs Improvement

Cause for Service Symptom Improvement Measure

Drop

Transmission fault L.E-RAB.AbnormRel.TNL > 0 Check for transmission alarms

Handover fault L.E-RAB.AbnormRel.HOFailure > 0 Handover failur

The value of L.UL.Interference.Avg is

Uplink interference significantly greater than the normal in Troubleshoot uplink interference.
idle mode.
 Solution to Service-Drop-related KPIs Improvement
The failure can be gradually rectified as follows:
⚫ Optimize RF settings to enhance indoor coverage.
⚫ Adjust the QRxLevMin parameter value. The adjusted value must meet the
requirements for cell edge coverage on live networks.
⚫ Increase the number of downlink RLC retransmissions (indicated by
eNodeBMaxRetxThreshold) to enhance the downlink transmission reliability.
⚫ Increase the value of TimeAlignmentTimer to reduce uplink timing errors and
achieve better uplink time alignment performance.
Air interface fault L.E-RAB.AbnormRel.Radio > 0 ⚫ Increase the value of the TrafficRelDelay parameter for a higher probability of UE
reestablishments.
⚫ Increase the value of WaitRrcConnSetupCmpTimer to increase tolerance duration.
For details, see Connection Management Feature Parameter Description.
⚫ Select the SrbProbeSchSwitch option. For details, see Scheduling Feature
Parameter Description.
⚫ Enable the ANR feature to solve problems caused by missing neighboring cells. For
details, see ANR Feature Parameter Description.
⚫ Enable the PCI conflict detection feature to solve PCI conflicts. For details, see PCI
Conflict Detection and Self-Optimization Feature Parameter Description.

Network congestion L.E-RAB.AbnormRel.Cong > 0 Expand the capacity of sites whose resources are congested.
Decrease the value of the UeInactiveTimer parameter to increase the number of normal
A small sum of normal releases The sum of the L.E-RAB.NormRel is significantly small. UE releases and avoid false high service drop rate caused by small number of normal
releases.
The failure can be rectified as follows:
RRC connection reestablishment
L.RRC.ReEstFail.NoCntx > 0 Select the RrcReestOptSwitch option to increase the reestablishment success rate and
failure
reduce service drop rate.
Service-related Parameter Optimization
MO Parameter ID Parameter Name Parameter Description Adjustment

The value of the downlink RSRP below -122 dBm

Reduces the number of UE shows that an area is poorly covered. You are
CellSel/CellResel QRxLevMin Minimum Required RX Level accesses in poorly covered advised to set the parameter to -122 dBm. If
areas. further adjustment is needed, you are advised to
increase its value by 2 dB at a time.
Results in a larger number of
MaxRetxThreshold for You are advised to set it to the maximum value of
SrbRlcPdcpCfg/RlcPdcpParaGroup eNodeBMaxRetxThreshold retransmissions to enhance the
eNodeB 32.
downlink transmission reliability.
You are advised to set this timer to INFINITY. At
Enhances the uplink timing
the same time, select the
TimeAlignmentTimer TimeAlignmentTimer Uplink time alignment timer reliability and reduces the out-of-
TimingAdvCmdOptSwitch option, and set the
synchronization probabilities.
TACmdSendPeriod parameter to SF928.
A longer waiting duration leads
to higher rate of RRC You are advised to set this parameter to 30s, or
CellStandardQci TrafficRelDelay Traffic Release Delay
connection reestablishment and at least not less than 15s.
lower service drop rate.
If further adjustment is needed, you are advised
A longer waiting duration leads to increase its value by 2s at a time. It is
ENodeBConnStateTimer UuMessageWaitingTimer UU Message Waiting Timer
to lower service drop rate. recommended that the value of the timer be less
than or equal to 35s.
If further adjustment is needed, you are advised
A longer waiting duration leads to increase its value by 2s at a time. It is
ENodeBConnStateTimer S1MessageWaitingTimer S1 Message Waiting Timer
to lower service drop rate. recommended that the value of the timer be less
than or equal to 20s.
If further adjustment is needed, you are advised
A longer waiting duration leads to increase its value by 2s at a time. It is
ENodeBConnStateTimer X2MessageWaitingTimer X2 Message Waiting Timer
to lower service drop rate. recommended that the value of the timer be less
than or equal to 20s.
A smaller value of this
parameter results in more RRC
connection releases for UEs to You are advised to set this parameter to 10s, not
RrcConnStateTimer UeInactiveTimer UE Inactivity Timer
prevent worse service drop rate more than 20s and less than 5s.
due to fewer normal RRC
connection releases.
Retainability KPI
Retainability KPI

Category Name Formula Associated Counters

Service_CDR = Service Drop Rate (All) = [L.E-RAB.AbnormRel/(L.E-

Retainability
Service Drop Rate (ERABAbnormalRelease/ERABRel RAB.AbnormRel + L.E-RAB.NormRel + L.E-
KPIs
ease) x 100% RAB.NormRel.IRatHOOut)] x 100%

Minutes Per Service Drop = Minutes Per Service Drop = (L.E-

Retainability
Minutes Per Service Drop TimeOfTranmission/ERABAbnormal RAB.SessionTime.HighPrecision/L.E-RAB.AbnormRel) x
KPIs
Release 100/1000/60
Case Study
Case 1 : LTE Call Drop Rate Improvement Post Connected Mode DRX Activation for Data User

• In X Network Y country, with increase in LTE users post LTE launch there was significant increase in LTE call drop rate due to major reasoning of
AbnormRel.Radio.SRBReset/AbnormRel.Radio.DRBReset. Network level drop rate rising in exponential trend which was very critical for network user and
customer perception.

Cause Analysis：
When DRX is OFF, the RLC Polling timer is 50ms, the RLC RESET Time is ENodeBMaxRetxThreshold * ENodeBPollRetransmitTimer = 32
* 50ms*=1.6s. So when switch on the DRX, RLC Reset Time will always be greater than 1.6 sec and in extreme scenario it can be
10.112 Sec. In normal scenario it will always be greater than 1.6 sec and smaller than 10.112s , Call drops due to DRB & SRB Reset will
be reduced due to increase in Max Reset timer after DRX is switched on.
Handling Process：
• Upon troubleshooting, below items were checked at the initial stage, but non of the issues were observed.
• If there was any top UE issue, secure mode e-RAB setup failures were observed but there were not any increments in secure mode failure If there was any
fluctuations in network availability rate If any activity was conducted from core network end Tilts were checked if they are setup abnormally through RET
audit but no major issues observed of zero electrical and mechanical tilts Then top site BRD logs were collected alongside signaling traces (S1/X2)
interfaces, then below understanding was developed from XML configuration parameters. When DRX was switched off and no consideration was taken into
account about RLC Reset Time which will always be greater than 1.6 sec. When calculated with RLC Polling timer is 50ms, RLC RESET Time =
ENodeBMaxRetxThreshold * ENodeBPollRetransmitTimer = 32 * 50ms*=1.6s which is very less and normally Max Reset timer will always be greater than
1.6s and less than 10.11s however in ideal scenario its always around 3.16s.

•However, When DRX is switched ON, the downlink data cannot be scheduled in sleep state, it must wait for next On duration cycle. So suppose if some data
needs to be re transmitted, it has to wait for the next on duration cycle and If every RLC retransmission waits for next On duration cycle, the RLC RESET max
time will increase. In extreme scenario where every retransmission has to wait to be transmitted in the on duration cycle, the RLC RESET Time will be
calculated as follows.
= (Long DRX Cycle(subframe) – On Duration Timer(subframe) * ENodeBMaxRetxThreshold = (320 - 4)*32 = 10.112s
SCENARIO
Cause RLC MAX RESET Time is always lower when DRX not activated which impact call drop rate due to increase in DRB RESET reasoning

Always keep connected mode DRX activated and in case there are issues in increasing trend of DRB & SRB RESET always double check DRX
Solution
Activated or not.
DRX Activation not only save UE battery but also improve call drop rate in cases where overall number of LTE sites are less and coverage is not that
Suggestions much good.
and summary： DRX Settings:
DRX (EnodeB Level)

DRX switch
Current Proposed

ON
OFF
DRXPARAGROUP (Cell Level)

DRX Inactivity Long DRX Short DRX

*DRX parameter DRX Short
On Duration Timer(subframe) Timer(subframe Cycle(subfram Cycle(subfram
group ID Cycle Timer
) e) e)

3 PSF4 PSF60 SF320 SF80 2

3 PSF4 PSF60 SF320 SF80 2
3 PSF4 PSF60 SF320 SF80 2
Case 2: • Impact of the Issue
• KPI’s indicate HOFailure high on Local Cell ID 0

30
20
10
0

L.E-RAB.AbnormRel.Cong
•HO out counter of 93396A11 L.E-RAB.AbnormRel.HOFailure
L.E-RAB.AbnormRel.MME
L.E-RAB.AbnormRel.Radio
L.E-RAB.AbnormRel.TNL

Data
Sum of Sum of
NCELL_I L.HHO.NCell.ExecAttOut L.HHO.NCell.ExecSuccOut
nfo (times) (times)
13061_0 0 0
13061_1 42 42
13061_2 0 0
13068_0 0 0
13068_1 0 0
13068_2 0 0
13069_0 16 16
13644_2 79 3
Grand
Total 137 61
• The reason of X2 handover out failure was that target eNodeB 93178 didn’t receive “UE_CONN_RECFG CMP” signaling (see below
picture)

Serving eNodeB 93396 signaling trace

X2 Handover signaling flow

•The RSRP of 93396 and 93178 were very weak less than -122dBm (RRC_MEAS_RPRT), at the same time, 3G 93396A1’s RSCP
was also weak less than -104dBm and can’t trigger the Redirection.
• Conclusion
• Call drop rate increase some times caused from Handover Failures , to solve this issue need to know the reason of the handover
failure , if it coverage issue so it is needed to check the target site level and physically optimize it.
Case 3: LTE Service Drop Rate Improvement by Parameters Optimization

• In "XX" country and "YY" NPM project customer requested to improve LTE Service Drop rate of 1 region and to make it <0.5% in busy hours with the help of
Optimization. Parameters changes suggested after analysis & audit of parameters and observed good improvement in SDR after implementation.

• Handling Process
• Following actions performed in order to troubleshoot the issue:
• Alarm information-no major service affecting alarms found on sites.
• Site availability-No major degradation.
• No major Tx issues found
Below parameter changes suggested in order to improve call drop rate and meets
customer requirement:

• After the implementation all the other KPIs

must be checked to cross verify any impact
of this parameter modification.
Case 4: LTE Service Drop Rate improvement by optimizing the value of UE Inactivity timer

Problem Description
InXX country and YY project customer requested to improve E-RAB drop rate for the whole network level and to make it <0.1% with the help of
Optimization. After analysis & parameter audit it has been observed thatUE Inactivity timer value was in some towns was set as 20 sec and for other
towns value is setat 10 sec.

Handling
Process
• Checked Alarms and transmission issues as well- No issuefound.
• Checked Neighbor relations- found ok.
• In the parameter audit, it was found that the UE inactivity timer was set to 20s for some towns which were having high drop rate. The parameter
description and its impact was shared with the customer.
• Description: Indicates the length of the UE inactivity timer. Ifthe eNodeB detects that a UE has neither received nor sent data for a duration
exceeding the value of this parameter, the eNodeB releases the RRC connection for the UE. If this parameter is set to 0, the UE inactivity timer is not
used .If this parameter is modified, the modified value applies only to UEs that access the network later.

Root Cause
• In the parameter audit, it was found that the UE inactivity timer for the network was set to 20s. Recommended to change value of
UE Inactivity Timer to 10 in order to improve Service drop rate.
• Changed value of UE inactivity timer from 20 sec to 10 sec in issue towns.

• Impact on Radio Network Performance : A smaller value of this parameter results in earlier RRC connection releases for UEs without performing services, more
frequent RRC connection setup requests, and better KPIs such as the service drop rate due to more normal RRC connection releases. A larger value of this
parameter results in later RRC connection releases for UEs without performing services, longer online duration in which radio resources are occupied, and
worse KPIs such as the service drop rate due to fewer normal RRC connection releases.

Parameter Current Value Recommended Value

UE Inactivity Timer (S) 20 10

Activation
Recommended
MML Command Parameter ID Default Value
Value
MOD RRCCONNSTATETIMER:
UeInactiveTimer 20 10
UeInactiveTimer=10;
• Optimization of UE inactivity timer can be an option to improve Service drop rate. Keeping UE inactivity timer to a smaller value will cause more
signaling resources due to more frequent RRC connection establishments but can help in improving the service drop rate due to more normal
disconnections.
THANK
YOU