[RL60]
Module 02
KPI Overview
X
Retainability:
RRC Drop Rate Mobility:
E-RAB Drop Rate Intra eNodeB HO
Success Rate
Inter eNodeB HO
5 © Nokia 2014 - RA47042EN60GLA0
Success Rate
General Measurement Overview (RL60)
The KPI describes the setup success ratio of the elementary E-RAB setup
procedure used to setup the E-RAB between MME and UE.
It indicates the E-UTRAN contribution to network accessibility for the end-
user, not the whole end-to-end service accessibility.
Summarisation
Logical formula formula (PI ID) Summarisation formula (Abbreviation)
E-RAB SSR=(E-RAB 100*sum([M8006C1]) / 100*sum([EPS_BEARER_SETUP_COMPLETIONS])
setup successes / E- sum([M8006C0]) / sum([EPS_BEARER_SETUP_ATTEMPTS])
RAB setup
attempts)*100%
This KPI describes the ratio of normally released E-RABs from user
perspective. This KPI is corresponding to a Connection Completion Ratio.
Summarisation
Logical formula formula (PI ID) Summarisation formula (Abbreviation)
E-RAB NRR 100*sum([M8006C6]+[ 100*sum([EPC_EPS_BEARER_REL_REQ_NORM]
UP=(normal E-RAB M8006C7]+[M8006C15] +[EPC_EPS_BEARER_REL_REQ_DETACH]
releases user + [M8006C10] +
perspective / all E-RAB [M8006C174] + +[ENB_EPS_BEAR_REL_REQ_RNL_REDIR
releases)*100% [M8006C175]) / ]+[ENB_EPS_BEARER_REL_REQ_NORM]
sum([M8006C6]+[M800
6C7]+[M8006C8]+ + [PRE_EMPT_GBR_BEARER] +
[M8006C9] + [PRE_EMPT_NON_GBR_BEARER]) /
[M8006C15]+ sum([EPC_EPS_BEARER_REL_REQ_NORM]
[M8006C10] + +[EPC_EPS_BEARER_REL_REQ_DETACH]
[M8006C12] +[EPC_EPS_BEARER_REL_REQ_RNL]
+[M8006C14] +[EPC_EPS_BEARER_REL_REQ_OTH]
+[M8006C13] + +[ENB_EPSBEAR_REL_REQ_RNL_REDIR]
[M8006C174] + +[ENB_EPS_BEARER_REL_REQ_NORM]
[M8006C175]) +[ENB_EPS_BEARER_REL_REQ_RNL]
+[ENB_EPS_BEARER_REL_REQ_TNL]
+[PRE_EMPT_GBR_BEARER]
+ [PRE_EMPT_NON_GBR_BEARER])
9 © Nokia 2014 - RA47042EN60GLA0
Mobility
This KPI describes the success ratio for the handover execution phase,
when the source eNB receives information that the UE successfully is
connected to the target cell within own eNB.
This KPI describes the success ratio for the inter eNB X2 based handover
execution phase, when the source eNB receives information that the UE
successfully is connected to the target cell within target eNB.
•With Attach, the mobile terminal registers at the LTE network. At the end of the procedure
the UE is authenticated, and a default (nGBR) bearer is established.
•The Attach Time is the interval between the connection request and the acknowledgement
of the positive response by the UE.
•With an explicit Detach request the UE informs the LTE network that it does
not want to access the EPS any longer. At the end of the procedure all EPS
bearers of the UE are released.
•The Detach Time is the interval between the Detach Request and the
reception of a Detach Accept message by the UE. No Detach Accept is sent
by the network if the cause for Detach is switching the UE off.
•The Attach Success Rate is defined as the ratio between the number of successful
registrations and the number of all requests. This is the probability that a user can attach to
the LTE network at any moment of time.
•The calculated success ratio figure excludes attach requests, which are rejected by
authentication failures. On the other hand, network attach requests which are terminated by
timer expiry (due to the unavailability of some LTE resource) are considered as
unsuccessful registrations.
•If the success rate is calculated on the eNB by counting incoming RRC requests, RRC
CONNECTION REQUEST retries are to be excluded, since they would increase the overall
number of establishment attempts, and thus reduce the success ratio.
•Formula:
number _ of _ successful l _ attach
LTENwAttSR 100 %
number _ of _ attach _ attempt
•It is the time taken by the LTE network to setup an EPS bearer on request by the UE. The EPS bearer
can be new (dedicated), or an existing one (e.g. the default EPS bearer). The latter is needed to reassign
Uu radio and S1 bearer resources to the existing EPS bearer of a previously Idle UE.
•The EPS bearer has to be created or activated before IP packets can be exchanged, i.e. the Service
Request creates the IP link dynamically over the mobile access (LTE) network.
•The UE Initiated EPS Bearer Setup Time is the interval between the submission of the message RRC
CONNECTION REQUEST (see References 26. [3GPP36.331]) carrying a NAS: Service Request
message in its body, and the reception of the RRC CONNECTION RECONFIGURATION response by
the UE. The Bearer Setup procedure is based on the Service Request procedure, see References 3.
[3GPP23.401] and 20. [3GPP36.300].
•It is the time taken by the LTE network to set up an EPS bearer on request by the P-GW.
The EPS bearer has to be created before IP packets can be sent (DL) to the UE if the UE
has no proper EPS bearer for the given IP packet flow. The network initiated Service
Request
•Time includes a Paging Time (ref. to Paging Time) if the UE is idle. The EPS Bearer Setup
procedure is based on the Paging and Service Request procedures according to
References 26. [3GPP36.331] and 3.[3GPP23.401].
•Mean value and 95% from all measured samples
•Formula: Service Request Time [s] = tRRC_Reconfig – tRRC_Request
•This KPI is defined as the ratio between successfully established EPS bearers compared
to the overall number of EPS bearer establishment attempts. It corresponds to the
probability that a user or the LTE network can establish an EPS bearer at any moment in
time.
•Requests that are terminated by timer expiry (due to the non-accessibility of some LTE
resource) are considered as unsuccessful attempts. Authentication errors (requests
rejected by the MME) are included in the total number of failures.
•Only the first RRC CONNECTION REQUEST is to be considered, since counting retries of
the same message would increase the overall number of bearer establishment attempts,
and thus reduce the success ratio.
•Formula:
number_of (RRC_CONN_ RECONFIGUR ATION_COMP LETE)
EPSSR 100 %
number_of (RRC_CONNE CTION_REQU EST)
•It is the ratio between abnormally released bearers and the overall
number of established EPS bearers. An abnormal release is defined as
any EPS bearer termination that was not triggered by the mobile user
(from UE side). Thus, it reflects the probability that an established bearer
is aborted due to insufficient network resources.
•Dropping the bearer becomes visible to the end-user if an application
service is actively using it. If the application automatically re-establishes
the bearer, it remains unnoticed by the user.
•Formula:
number_of (dropped_c alls)
EPSBearerD R 100 %
number_of (successfu ll_calls)
• Target:
• Few selected KPIs that can be post-processed automatically from drive test logs.
• Network wide drive testing executable with one drive (=one test case/script) per
cluster.
•
13:56:34.369 DCCH Downlink UECapabilityEnquiry
Example script 13:56:34.390
13:56:34.410
DCCH
DCCH
Uplink
Downlink
UECapabilityInformation
RRCConnectionReconfiguration
13:56:34.414 DCCH Uplink RRCConnectionReconfigurationComplete
• Attach 13:56:34.416 Downlink ATTACH_ACCEPT
13:56:34.416 Downlink ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST
• Detach 13:56:57.142
13:56:57.142
BCCH_BCH Downlink
BCCH Downlink
SYSTEM_INFORMATION_BCH
MASTER_INFORMATION_BLOCK
• Example script
• FTP DL (5MB)
• FTP UL (3MB)
• HTTP page DL (x5)
• Ping 32-1024B (x10)
KPIs 1 2 3 Comment
Attach SR x Attach request -> Attach complete
Attach time x Attach request -> Attach complete
Session setup SR from Deregistetered x RRCC request -> ULinformation transfer (Attach complete)
Session setup time from Deregistered x RRCC request -> ULinformation transfer (Attach complete)
Session setup time from RRC idle x RRCC request -> RRCC reconf. Complete
Session setup SR from RRC idle x RRCC request -> RRCC reconf. Complete
LTE intra freq HO SR x x x
LTE inter freq HO SR x x x
Call/Session drop rate x x
# drops/minute x x x
Re-establishment success rate x x x
FTP/HTTP/PING SR x x x
RTT PING x x x
FTP DL throughput x x x
FTP UL throughput x x x
HTTP page download time x x x