Sunteți pe pagina 1din 11

LTE KPI Related Colume Header Gloze

Accessibility
1.

Initial E-RAB Establishment Success Rate

This KPI measures the impact on the end user.


The following equation gives the accessibility success rate for end-user services
that are carried by E-RABs included in the Initial UE Context setup procedure. The
counters are on cell level.

Equation 2

Initial E-RAB Establishment Success Rate

Note:
The impact of multiple E-RABs in the Initial context setup procedure is
ignored in the RRC and S1 signalling part contribution.

Pay attention
In this section, the Colume 2, 3, 4 are the part of the Colume 1, the Colume
2(RRC Connection Setup Sucess (%)) equals to the pmRrcConnEstabSucc/
[pmRrcConnEstabAtt-pmZtemporary9], the Colume 3(E-RAB Success
Rate(%)) equals to the pmErabEstabSuccInit/pmErabEstabAttInit; the
Colume 4(S1SigEstabSuccRate (%)) equals to the pmS1SigConnEstabSucc/
pmS1SigConnEstabAtt;

5.

pmRrcConnEstabAtt
The total number of RRC Connection Request attempts.
Condition: Stepped at reception of RRC message RRC Connection Request.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

6.

pmRrcConnEstabSucc
The total number of successful RRC Connection Establishments.
Condition: Stepped at reception of RRC message RRC Connection Setup
Complete.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

7.

pmRRCConnEstReAtt
Please consult the 5.pmRrcConnEstabAtt;

8.

pmErabEstabAttInit
The total number of initial E-RAB Establishment attempts. Initial E-RABs
are all E-RABs present in the S1 message Initial Context Setup Request.
Condition: Stepped for each E-RAB received in the S1 message Initial
Context Setup Request.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

9.

pmErabEstabSuccInit
The total number of successful initial E-RAB Establishments. Initial E-RABs
are all E-RABs present in the S1 message Initial Context Setup Request.
Condition: Stepped for each initial E-RAB that is successfully established.
Counter is reset after measurement period: Yes
Counter type: PEG

Scanner: Primary
Unit: -

Retainability
1.

E-RAB Retainability

This KPI measures the impact on the end user.


The Retainability rate for E-RAB is given by the following equation. The counters
are on cell level.

Equation 6

E-RAB Retainability

Note:
Since the KPI measures the impact of the network on the end user, it
also includes releases initiated by the MME. To observe the impact of
the RBS only, remove the pmErabRelMmeAct from the formula.
To achieve the number of minutes per drop, the multiplicative inverse
of the E-RAB Retainability together with unit transformation from
seconds to minutes can be used.
Pay attention
In the retainability section, Colume 2 &Colume 3 are part of the Colume 1, just
as the equation shown, the Colume 2 ( E-RAB Retainability Abnormal (%))
equals to the pmErabRelAbnormalEnbAct/pmSessionTimeUe, and Colume 3
( E-RAB Retainability MME (%)) equals to the pmErabRelMmeAct
/pmSessionTime-Ue.

4.

pmErabRelAbnormalEnb

The total number of abnormal E-RAB Releases initiated by the RBS. The
counter is stepped regardless of whether data was or was not lost in UL/DL
buffers.
Condition: Stepped at reception of S1 message E-RAB Release Command
or UE Context Release Command when internal cause codes considered
abnormal (Radio Connection with UE is lost; Handover failure for the UE;
Non admitted E-RABs by target cell at successful handover for the UE)
when the RBS initiated the release. It can also be stepped at transmission
of Reset message by the RBS, or when a cell owned by that RBS is
disabled (and that leads to internal RBS UE Context Release).
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

5.

pmErabRelMmeAct
The total number of E-RAB Releases initiated by the MME and that there
was data in either the UL or DL buffer (i.e. active).
Condition: If there was data in the buffer at the time of release, then
stepped at reception of S1 message E-RAB Release Command or UE
Context Release Command. The release must also have been MME
initiated.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

6.

pmErabRelAbnormalEnbAct
The total number of abnormal E-RAB Releases initiated by the RBS and
that there was data in either the UL or DL buffer (i.e. active).
Condition: If there was data in the buffer at the time of release, then
stepped at reception of S1 message E-RAB Release Command or UE
Context Release Command when internal cause codes considered
abnormal (Radio Connection with UE is lost; Handover failure for the UE;
Non admitted E-RABs by target cell at successful handover for the UE)
when the RBS initiated the release. It can also be stepped at transmission
of Reset message by the RBS, or when a cell owned by that RBS is
disabled (and that leads to internal RBS UE Context Release).
Counter is reset after measurement period: Yes
Counter type: PEG

Scanner: Primary
Unit: -

7.

pmErabRelNormalEnb
The total number of normal E-RAB Releases triggered by RBS. The counter
is stepped regardless of whether data was or was not lost in UL/DL
buffers.
Condition: Stepped at reception of S1 message E-RAB Release Command
or UE Context Release Command when internal cause codes considered
normal (User Inactivity, Inter-RAT redirection, CS Fallback Triggered) when
the RBS initiated the release.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

8.

pmErabRelAbnormalEnbActHo
The total number of abnormal E-RAB releases by the RBS due to handover
execution failure and that there was data in either the UL or DL buffer (i.e.
active).
Condition: If there was data in the buffer at the time of release, and the
release is due to that executed handover fails and the UE is considered
dropped.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

9.

pmErabRelAbnormalEnbActUeLost
The total number of abnormal E-RAB releases by the RBS due that the
radio connection with the UE is lost and that there was data in either the
UL or DL buffer (i.e. active).
Condition: If there was data in the buffer at the time of release and if
there was a release of an UE due to that the radio connection towards the
UE is lost (i.e. UE unreachable by the RBS).
Counter is reset after measurement period: Yes
Counter type: PEG

Scanner: Not included in any predefined scanner


Unit: -

10. pmErabRelAbnormalEnbActTnFail
The total number of abnormal E-RAB releases initiated by the RBS due to
S1 interface down and that there was data in either the UL or DL buffer
(i.e. active).
Condition: If there was data in the buffer at the time of release of an ERAB and due to that the S1 interface is lost.
Counter is reset after measurement period: Yes
Counter type: PEG
Sampling rate: Scanner: Not included in any predefined scanner
Unit: -

11. pmErabRelAbnormalEnbActCdt
The total number of abnormal ERAB releases by the RBS due to cell down
time (manual intervention) when data was in either the UL or DL buffer
(i.e. active).
Condition: Stepped for each ERAB that is lost due to cell down time
(manual intervention) when data was in either the UL or DL buffer.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

12. pmErabRelAbnormalEnbActHpr
The total number of abnormal E-RAB releases by the RBS due to handover
preparation and that there was data in either the UL or DL buffer (i.e.
active).
Condition: If there was data in the buffer at the time of release of an ERAB, due to that an executed handover excludes the E-RAB (admission
reject in target)
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

13. pmErabRelMme
The total number of E-RAB Releases initiated by the MME. The counter is
stepped regardless of whether data was or was not lost in UL/DL buffers.
Condition: Stepped at reception of S1 message E-RAB Release Command
or UE Context Release Command. The release must also have been MME
initiated.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Not included in any predefined scanner
Unit: -

14. pmErabRelNormalMme
Please consult the 13.pmErabRelMme;

Integrity
1.

Downlink Latency

This KPI measures the impact on the end user.


DL latency for the UE is given by the following equation. The counters are on cell
level.

Equation 7

2.

Average UE DL Latency

Uplink Throughput

This KPI measures the impact on the end user.


UL throughput for the UE is given by the following equation. The counters are on
cell level.

Equation 10

3.

Average UE UL Throughput

Downlink Throughput

This KPI measures the impact on the end user.


DL throughput for the UE is given by the following equation. The counters are on
cell level.

Equation 9

4.

Average UE DL Throughput

Uplink Packet Loss Rate

This KPI measures the impact on the end user.


UL packet loss rate for the UE is given by the following equation. The counters are
on cell level.

Equation 12

5.

Average UE UL Packet Loss Rate

Downlink Packet Error Loss Rate

This KPI measures the impact on the end user.

DL packet error loss rate for the UE is given by the following equation. The
counters are all on cell level, except pmPdcpPktDiscDlEth which is on RBS level.

Equation 11

Average UE DL Packet Error Loss Rate, from a cell perspective

where

Availability
1.

Partial Cell Availability (node restarts excluded)

This KPI measures system performance. Since the KPI is measured by the RBS, it
does not include time when the RBS is down, i.e. node restart time is excluded.
The length of time in seconds that a cell is available for service is defined as cell
availability. Cell availability for a cluster of M number of cells during N reporting
periods can be calculated using the following formula. The counters are on cell
level.

Equation 14

Cell Availability

Note:
The manual blocking time of a cell is included in this KPI to show the
overall availability of the cell. To remove the manual intervention
impact on cell availability, remove the PM counter pmCellDowntimeMan

from the numerator and subtract the value of the PM counter


pmCellDowntimeMan from the denominator.
Note:
If the files with the PM counters are missing, the time that those files
represent in "NxMx900" shall be excluded from Cell Availability result.

Mobility
1.

Mobility Success Rate

According to the related parameters, the Mobility Success Rate equals to


the pmHoExeSuccLteIntraF /pmHoPreAttLteintraF;

2.

pmHoPrepAttLteIntraF
The number of attempts to start intra LTE intra frequency handover
preparation.
Condition: A better LTE cell is reported by the UE.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

3.

pmHoPrepSuccLteIntraF
The number of successful intra LTE intra frequency handover preparations.
Condition: HANDOVER COMMAND message is received by the source
eNodeB from the MME (S1 handover)
or
HANDOVER REQUEST ACKNOWLEDGE message is received by the source
eNodeB from the target eNodeB (X2 handover)
or
Internal eNodeB trigger (corresponding to HANDOVER REQUEST
ACKNOWLEDGE) received when target cell informs source cell that UE
resources has been reserved (intra eNodeB handover)
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

4.

pmHoExeAttLteIntraF
The number of intra LTE intra frequency handover execution attempts.
Condition: RRC CONNCECTION RECONFIGURATION including the
mobilityControlInformation is sent to the UE from the source cell.
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

5.

pmHoExeSuccLteIntraF
The number of successful intra LTE intra frequency handovers.
Condition: UE CONTEXT RELEASE COMMAND received in the source
eNodeB from the MME with the cause Handover Triggered (S1 handover)
or
UE CONTEXT RELEASE received in the source eNodeB from the target
eNodeB (X2 handover)
or
Internal eNodeB trigger (corresponding to UE CONTEXT RELEASE) received
when the UE has changed cell during a intra eNodeB handover
Counter is reset after measurement period: Yes
Counter type: PEG
Scanner: Primary
Unit: -

S-ar putea să vă placă și