RRC Setup Success Rate (Service)

Description

According to 3GPP TS 36.331, the RRC connection setup procedure is triggered by different causes, which are identified in the "establishmentCause" field in an RRC Connection Request message as emergency, highPriorityAccess, mt-Access, mo-Signaling, mo-Data, or delayTolerantAccess-v1020. The UE sets the establishmentCause in accordance with the information it receives from upper layers. The mo-signaling cause is a signaling-related cause. All other causes are service-related causes. The accessibility KPI evaluates the RRC setup success rate using service-related causes in a cell or radio network.
The RRC Setup Success Rate (Service) KPI is calculated based on the counters measured at the eNodeB when the eNodeB receives an RRC Connection Request message from the UE, as shown in Figure 1. The number of RRC connection attempts is collected by the eNodeB at measurement point A, and the number of successful RRC connections is counted at measurement point C.

Figure 1 Measurement points for RRC connection setup

Definition

The RRC Setup Success Rate (Service) KPI is defined in Table 1. Note that the number of RRC connection setup attempts (service) and the number of successful RRC setup connections (service) are collected based on the description in Description.

Table 1 RRC Setup Success Rate (Service)

Name	RRC Setup Success Rate (Service)
Object	Cell or radio network
Formula	RRCS_SRservice = (RRCConnectionSuccessservice/RRCConnectionAttemptservice) x 100%
Associated Counters	RRC Setup Success Rate (Service) =((L.RRC.ConnReq.Succ.Emc + L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.Mt + L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.DelayTol)/(L.RRC.ConnReq.Att.Emc + L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.Mt + L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.DelayTol)) x 100%
Unit/Range	Percentage (%)
Note	None