Академический Документы
Профессиональный Документы
Культура Документы
1 KPI Introduction
The traffic measurement data and drive test data are the objective basis of the network
optimization, while the human perception is the subjective basis. It is necessary to trace
and analyze signalling messages to locate problems before these problems are solved. It is
obvious that the traffic measurement data provide a very important method to analyze the
network performance. Especially when there is traffic in the network, the traffic
measurement data provide important references and guide for the network optimization.
The integrity and accuracy of the measurement items and the convenience of operations
will directly affect the efficiency of network optimization. Meanwhile, the quality of
measurement items is also a very important factor to measure the effect of network
optimization.
On the other hand, network operators set much store by the traffic measurement data.
The boss of network operators usually learns and judges the running status of networks
according to the visual data obtained from traffic measurement. These visual traffic
measurement data also provide an important basis for the future network capacity
expansion.
Above figure lists the major KPIs which we may concern in the network
These two counters are measured at the same points as service oriented RRC setup
ERAB includes both the ERAB radio bearer and corresponding S1 bearer. Any abnormal
release on either bearer causes call drop and therefore is counted into the call drop rate.
The abnormal release is identified by the Cause IE (Information Element) defined in
Reference.
As shown in point A in Figure 1, the corresponding counter is incremented each time the
eNodeB receives an E-RAB RELEASE COMMAND message from the MME and the Release
Cause information element is not Normal Release, User Inactivity, Partial Handover, or
Handover triggered. If the E-RAB RELEASE COMMAND message requires multiple E-RAB
releases at the same time, the corresponding counter is incremented repeatedly.
As shown in point A in Figure 2, the corresponding counter is incremented each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME and the
Release Cause information element is not Normal Release, User Inactivity, Partial
Handover, or Handover triggered.
As shown in point A in Figure 3, the corresponding counter is incremented by 1 each time
the eNodeB sends an E-RAB RELEASE INDICATION message to the UE. If the E-RAB
RELEASE INDICATION message requires multiple E-RAB releases at the same time, the
corresponding counter is incremented repeatedly.
As shown in point A in Figure 4, the corresponding counter is incremented each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME and the
Release Cause information element is not Normal Release, User Inactivity, Partial
Handover, or Handover triggered.
As shown in point A in Figure 1, the corresponding counter is incremented each time the
eNodeB receives an E-RAB RELEASE COMMAND message from the MME and the Release
Cause information element is Normal Release, User Inactivity, Partial Handover, or
Handover triggered.
As shown in point A in Figure 2, the corresponding counter is incremented each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME and the
Release Cause information element is Normal Release, User Inactivity, Partial
Handover, or Handover triggered.
During a handover where the source cell and target cell are controlled by the same
eNodeB, as shown in point B, the corresponding counter is incremented by 1 each time
the eNodeB sends an RRC Connection Reconfiguration message to the UE. The counters
are measured as follows:
If the source cell and target cell work at the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and target cell work at different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the eNodeB
receives an RRC Connection Reconfiguration Complete message from the UE and the
subsequent operations are successful. The counters are measured as follows:
If the source cell and target cell are at the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and target cell are at different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1.
During such a handover where the source cell and target cell are controlled by different
eNodeBs, as shown in point B in the figure above, the corresponding counter is
incremented each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE from the target
eNodeB or receiving a HANDOVER COMMAND message from the MME. The counters are
measured as follows:
If the source cell and target cell work at the same frequency, the
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and target cell work at different frequencies, the
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
As shown in point C , the corresponding counter is incremented each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB or a UE
CONTEXT RELEASE COMMAND message from the MME. The counters are measured as
follows:
If the source cell and target cell are at the same frequency, the
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and target cell are at different frequencies, the
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
The available RB for DL/UL is fixed value according to the system bandwidth
Associated counter:
Number of Used Downlink PRBs(L.ChMeas.PRB.DL.Used.Avg):Downlink PRBs in a
cell are occupied by the PDSCH and PDCCH in time division mode. Therefore, the
number of used downlink PRBs mainly refers to the number of PRBs used by the
PDSCH. The counter measures the average number of used downlink PRBs in a cell.
It is used to analyze the usage of downlink PRBs.
Number of Used Uplink PRBs(L.ChMeas.PRB.UL.Used.Avg): The uplink PRBs in a cell
are occupied by the PUSCH,PRACH and PUCCH in frequency division mode, with
those PRBs at both ends being used by the PUCCH and others in the middle being
used for the PUSCH and PRACH. The total number of PRBs used by the
PUCCH,PRACH and PUSCH is the number of used uplink PRBs. The counter
measures the average number of used uplink PRBs in a cell. It is used to analyze the
usage of uplink PRBs.
Relative counters:
L.ChMeas.PRB.DL.Used.Avg: Average number of used downlink PRBs, Downlink
PRBs in a cell are occupied by the PDSCH and PDCCH in time division mode.
Therefore, the number of used downlink PRBs mainly refers to the number of PRBs
used by the PDSCH. The counter measures the average number of used downlink
PRBs in a cell. It is used to analyze the usage of downlink PRBs.
L.ChMeas.PRB.UL.Used.Avg: Average number of used uplink PRBs, The uplink PRBs
in a cell are occupied by the PUSCH,PRACH and PUCCH in frequency division mode,
with those PRBs at both ends being used by the PUCCH and others in the middle
being used for the PUSCH and PRACH. The total number of PRBs used by the
PUCCH,PRACH and PUSCH is the number of used uplink PRBs. The counter
measures the average number of used uplink PRBs in a cell. It is used to analyze the
usage of uplink PRBs.
The counters measure the duration of cell unavailability due to human factors or non-
human factors. Human factors refer to operation maintenance, include the operator
execute the command on LMT(Local Maintenance Terminal): block cells or de-active
cell.Non-human factors refer to other reasons except operation maintenance, mainly
include: board inner fault, The CPRI link is faulty, The baseband processing unit carrying
services is faulty, The transmit/receive channel of the RF unit is faulty, transport resource
for control plane (S1 signaling link) or user plane (IP path) is unavailable, The license
resources are insufficient, The clock resources are unavailable.
The duration of cell unavailability is sampled every five seconds. If a cell is unavailable, the
corresponding counter is incremented by five at each sampling point accordingly. At the
end of a measurement period, the sum of these sampling results is reported.
Associated counters
Number of DRBs in a Cell (L.Traffic.DRB.QCI.x)
Description:
The counters measure the number of DRBs for each service with a specific QCI
ranging from 1 to 9 in a cell, respectively.
Measurement point:
The number of DRBs for each service with a specific QCI ranging from 1 to 9 in a
cell is sampled every five seconds. At the end of a measurement period, the
average of these sampling results is used as the value of the corresponding
counter.
Associated counters:
L.Thrp.bits.UL.QCI.x
Measurement point:
The downlink traffic volume for transmitted PDCP SDUs of each service with a
specific QCI ranging from 1 to 9 is measured in a cell. Only the payload sizes of the
SDUs that are successfully transmitted is accumulated, and the sum is used as the
value of the corresponding counter.
Associated counters:
L.Thrp.bits.UL.QCI.x
Measurement point:
The uplink traffic volume for transmitted PDCP SDUs of each service with a specific
QCI ranging from 1 to 9 is measured in a cell. Only the payload sizes of the SDUs
that are successfully transmitted is accumulated, and the sum is used as the value
of the corresponding counter.
The PRS is a platform used to manage mobile network performance reports and analyze
network performance.