You are on page 1of 3

LTE KPI: ERAB Succ Rate Optimization

RRC + NAS message

eRAB Succ Rate (%) = eRAB Succ Att


eRAB Tot Att

Some Ue do not support


when these two messages
are bundled together.
LTE KPI: ERAB Succ Rate Optimization

T304

Could be brought about by


bad radio condition.

“Security Mode Complete”


message from Ue not
received by eNB.

RRC Reestablishment Request (T301) is initiated


because “Security Mode Command” was
received by Ue. Else, if RLF happened before
“Security Mode Command”, Ue will transition to
RRC_IDLE, then initiate RRC Connection Request
(T300).
LTE KPI: ERAB Succ Rate Optimization

RLF happened before receiving


these two messages.

PAGING message came before


RRC Connection Reconfiguration
message, thus, creating a 2nd
eRAB establishment and
eventually the confusion.

MO: PCCHCFG, ParamId: DefaultPagingCycle (rf128, radio frames)


Range: rf32, rf64, rf128, rf256

The values of this parameter and the NB parameter determine the number of paging occasions, that is, the number of paging groups. A larger value
of this parameter may lead to a longer delay in paging a UE but help reduce the power consumption of the UE. A smaller value of this parameter may
lead to a shorter delay in paging a UE but cause more power consumption of the UE. If the EPC specifies a DRX period for a UE, the UE uses the
smaller value between the period and the parameter value as its DRX period.

You might also like