LTE RRC Succ Rate Optimization
LTE RRC Succ Rate Optimization
LTE RRC Succ Rate Optimization
Probability of failure is
higher for RRC
containing signaling
messages.
RRC Connection Setup Complete message from Ue didn’t reach eNB due to uplink imbalance.
Recommend:
Antenna down-tilt or re-orientation !!!
LTE KPI: RRC Succ Rate Optimization
Other Causes of RRC Failures:
Interference due to high traffic load (high success rate is observed during low traffic period).
Recommend:
a) Antenna down-tilt or re-orientation.
b) Improve layering strategy (mobility) or load balancing.
c) Activate MRC/IRC (Max Ratio Combining/UL Interference Rejection Combining) Feature:
MrcIrcAdptSwitch - Indicates whether to apply MRC/IRC adaptation to the PUSCH. If this option is selected, MRC/IRC adaptation is applied to the PUSCH. If
this option is deselected, the MRC algorithm is applied to the PUSCH. This option applies only to LTE FDD and LTE TDD.
SmartIrcSwitch - Indicates whether to apply the smart IRC algorithm to the PUSCH. If this option is selected, the smart IRC algorithm is applied to the PUSCH.
If this option is deselected, the smart IRC algorithm is not applied to the PUSCH. This option applies only to LTE TDD.
MrcIrcAdaptivefor2R - Indicates whether to apply MRC/IRC adaptation to the PUSCH in 2R scenarios. This option takes effect only when the
MrcIrcAdptSwitch option is selected. If this option is selected, MRC/IRC adaptation is applied to the PUSCH in 2R scenarios. If this option is deselected, the
MRC algorithm is applied to the PUSCH. This option applies only to LTE FDD and LTE TDD.
NoIntrfSmartIRCEnhSwitch - Indicates whether to apply the enhanced interference cancellation algorithm to the PUSCH. If this option is selected, the
enhanced interference cancellation algorithm is applied to the PUSCH. If this option is deselected, the enhanced interference cancellation algorithm is not
applied to the PUSCH. This option applies only to LTE TDD. For 2R cells established on LBBPc boards, if the MrcIrcAdptSwitch option is selected, the IRC
algorithm is applied to the PUSCH. If the MrcIrcAdptSwitch option is deselected, the MRC algorithm is applied to the PUSCH. For 2R cells established on LBBPd
boards, the setting of the MrcIrcAdaptivefor2R option takes effect only when the MrcIrcAdptSwitch option is selected. If the MrcIrcAdptSwitch and
MrcIrcAdaptivefor2R options are selected, MRC/IRC adaptation is applied to the PUSCH. If the MrcIrcAdptSwitch option is selected and the
MrcIrcAdaptivefor2R option is deselected, the IRC algorithm is applied to the PUSCH. If the MrcIrcAdptSwitch option is deselected, the MRC algorithm is
applied to the PUSCH. For 2R cells established on UBBP boards, if the MrcIrcAdptSwitch option is selected, IRC/MRC adaptation is applied to the PUSCH. If the
MrcIrcAdptSwitch option is deselected, the MRC algorithm is applied to the PUSCH. For 4R cells established on LBBPc, LBBPd, or UBBP boards, if the
MrcIrcAdptSwitch option is selected, IRC/MRC adaptation is applied to the PUSCH. If the MrcIrcAdptSwitch option is deselected, the MRC algorithm is applied
to the PUSCH.
LTE KPI: RRC Succ Rate Optimization
Other Causes of RRC Failures (Cont.):
Interference caused by external sources (low success rate during busy and low traffic hours).
Recommend:
a) Conduct external check by spectrum analyzer.
b) Check if interfered band is wide band or part of the band only.
Incompatible Ue
Ue is not able to support the channel configuration re'qd. by eNB during "RRC Connection Setup" thus Ue is not able to send "RRC Connection Setup
Complete". Investigate by tracing the RRC layer for a specific Ue TMSI having multiple attempts of "RRC Connection Request" messages to eNB.
RRC rejection due to CAC (Call Admission Control process) where RRC capacity is exhausted.
Recommend:
a) Antenna down-tilt or re-orientation.
b) Improve layering strategy (mobility) or load balancing.
c) Optimize T302 and Ue Inactivity Timer:
MO: RRCCONNSTATETIMER, ParamId: T302 (16 sec)
Range: 1 ~ 16 sec
T302 specifies the time during which a UE whose RRC connection request is rejected has to wait before the UE can initiate a request again. This timer starts
when the UE receives an RRCConnectionReject message and stops when the UE enters the RRC_CONNECTED mode or performs cell reselection. This
parameter applies only to LTE FDD and LTE TDD. If this parameter is set to a small value, the eNodeB rejects access of the UE again for the same reason. If this
parameter is set to a large value, the UE cannot access the network for a long period of time, which affects user experience.
MO: QCIPARA, ParamId: UeInactiveTimerForQci (20 sec)
MO: QCIPARA, ParamId: CiotUeInactiveTimer (20 sec)
MO: QCIPARA, ParamId: UeInactivityTimerDynDrxQci (200 sec)
Range: 0 ~ 3600 sec
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. If the UE Inactivity Timer is set to a smaller value,
the number of times UEs near a cell center access the cell becomes larger, resulting in smaller values of the L.RRC.ConnSetup.TimeAvg and L.E-
RAB.Est.TimeAvg counters.
CiotUeInactiveTimer indicates the UE inactivity timer for MTC UEs, eMTC UEs, and UEs with the RRC connection setup cause delayToleran. If the eNodeB
detects that such a UE has neither received nor sent data for a period exceeding the value of this parameter, the eNodeB releases the RRC connection for the
UE. If this parameter is set to 0, the timer length is infinite. This parameter takes effect only for UEs that will access the network after the parameter is set. If a
UE has bearers of several QCIs, the eNodeB selects the longest UE inactivity timer of bearers with the highest QCI-specific priority specified by the
UeInactiveTimerPri parameter as the UE inactivity timer for the UE. This parameter applies only to LTE FDD and LTE TDD.
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.
UeInactivityTimerDynDrxQci indicates the length of the UE inactivity timer for UEs that have entered DRX mode and have bearers of the QCI when dynamic
DRX is enabled. If the eNodeB detects that a UE has neither received nor sent data for a period exceeding the value of this parameter, the eNodeB releases
the RRC connection for this UE. If this parameter is set to a large value, the amount of signaling is reduced but UE power consumption increases. You are
advised to set this parameter to a value greater than that of UlSynTimerDynDrx. In power saving mode, you are advised to set this parameter significantly
different to the value of the UlSynTimerDynDrx parameter, for example a gap of 10 seconds, to avoid power consumption increase due to the increase of
signaling. If a UE has bearers of several QCIs, the eNodeB selects the longest UE Inactivity Timer of bearers with the highest QCI-specific priority specified by
the UeInactiveTimerPri parameter as the UE inactivity timer for the UE. This parameter applies only to LTE FDD and LTE TDD.
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.
UeInactiveTimerPri indicates the priority of the QCI-specific UE Inactivity Timer. A larger value of this parameter indicates a higher priority. The eNodeB
selects the longest UE Inactivity Timer with the highest QCI-specific priority as the UE Inactivity Timer for UEs running services with the specific QCI. The UE
Inactivity Timer for QCI 69 is taken as the UE Inactivity Timer for the MCPTT UEs. This parameter applies only to LTE FDD and LTE TDD.
A smaller value of this parameter indicates a lower priority for the UE Inactivity Timer for the QCI and a lower probability that this timer is selected for a UE. A
larger value of this parameter results in the opposite effects.