12/30/22, 4:18 PM Key Performance Indicators

User Guide 37/1553-LZA 701 6014/1 Uen V

Key Performance Indicators

Contents
Introduction
End-User Performance in LTE
Observability in Ericsson LTE
LTE RAN Performance Observability Model
Aggregation of KPIs
Service Separation of Observability in LTE RAN
Detailed Separation of Observability in LTE RAN with Flexible Counters
Accessibility
Initial E-RAB Establishment Success Rate
Initial E-RAB Establishment Success Rate per QCI 19.Q4 and later
Differentiated Initial E-RAB Establishment Success Rate
Compensated Initial E-RAB Establishment Success Rate
Initial E-RAB Establishment Success Rate for Emergency Calls
Initial E-RAB Establishment Success Rate, No MO Signaling
Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling
Added E-RAB Establishment Success Rate
Differentiated Added E-RAB Establishment Success Rate
Compensated Added E-RAB Establishment Success Rate
Added E-RAB Establishment Success Rate per QCI
Added E-RAB Establishment Success Rate for Emergency Calls
Robust Random Access Success Rate
Random Access MSG1 Success Rate
Robust Random Access Success Rate for Cat-M1 UE devices
Random Access MSG1 Success Rate for Cat-M1 UE devices
eMBMS Establishment Success Rate
Retainability
E-RAB Retainability - Session Time Normalized Loss Rate
E-RAB Retainability - Session Time Normalized Loss Rate the Second
Compensated E-RAB Retainability - Session Time Normalized Loss Rate
Compensated E-RAB Retainability - Session Time Normalized Loss Rate, the Second
E-RAB Retainability - Session Time Normalized per QCI Loss Rate
E-RAB Retainability - Session Time Normalized per QCI Loss Rate, the Second
E-RAB Retainability - Percentage Lost
Differentiated E-RAB Retainability - Percentage Lost
Compensated E-RAB Retainability - Percentage Lost
E-RAB Retainability (eNB) - Percentage Lost
E-RAB Retainability (eNB) - Percentage Lost, the Second
Compensated E-RAB Retainability (eNB) - Percentage Lost
Compensated E-RAB Retainability (eNB) - Percentage Lost, the Second
E-RAB Retainability - Percentage Lost per QCI
E-RAB Retainability - Percentage Lost for Emergency Calls
eMBMS Retainability - Percentage Lost
Integrity
Average DL UE Latency
Compensated Average DL UE Latency
Average DL PDCP DRB LTE Latency per QCI
Average DL PDCP DRB Cat-M Latency per QCI
Average DL UE PDCP DRB Latency per QCI
Average DL MAC DRB Latency per QCI
Differentiated Average DL MAC DRB Latency per QCI
Compensated average DL MAC DRB Latency per QCI
Average DL PDCP UE Throughput
Compensated Average DL PDCP UE Throughput
Total DL PDCP UE Throughput
Average DL PDCP Cell Throughput
Average DL MAC Cell Throughput
Filtered MBB UE DL PDCP Throughput
DL PDCP UE Throughput Distribution
Average DL PDCP UE DRB Throughput per QCI
DL PDCP UE Throughput Distribution for MBB UE
Mean DL PDCP UE Throughput
Mean DL PDCP UE Throughput for MBB UE
Average DL PDCP UE Throughput for Carrier Aggregation
Compensated Average DL PDCP UE Throughput for Carrier Aggregation
Filtered MBB UE UL Throughput
Average UL PDCP UE Throughput
Compensated Average UL PDCP UE Throughput
Average UL PDCP Cell Throughput
Average UL MAC Cell Throughput
Normalized Average UL MAC Cell Throughput Considering Successful PUSCH subframe Only
Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only
Average UL PDCP UE Throughput for Carrier Aggregation
Compensated Average UL PDCP UE Throughput for Carrier Aggregation
Average MAC UE UL THROUGHPUT
Compensated Average MAC UE UL Throughput
UL PDCP UE Throughput Distribution
Mean UL PDCP UE Throughput
Average UL UE Throughput per LCG
Compensated average UL Throughput per LCG
Average DL Packet Error Loss Rate
Average DL Packet Error Loss Rate per QCI
Average eMBMS Packet Loss Rate
Average UL Packet Loss Rate
Average UL Packet Loss Rate per QCI
VoIP Cell Integrity
Compensated VoIP Cell integrity
GTP-U Downlink Packet Loss Rate
GTP-U Downlink Packet Out of Order Rate
DL Scheduled Entities per TTI
UL Scheduled Entities per TTI
Mobility
Mobility Success Rate
Cell Mobility Success Rate
Flexible Intra-Frequency Cell Mobility Success Rate
Handover Success Rate
Handover Execution Success Rate
Cell Handover Success Rate
Cell Handover Execution Success Rate
Differentiated Cell Handover Success Rate
UTRAN SRVCC Success Rate
Availability
Cell Availability

about:blank 1/26
12/30/22, 4:18 PM Key Performance Indicators

1 Introduction
KPIs are used for RAN to measure the quality and system performance observed and perceived by subscribers.

Monitoring the performance of a RAN through KPIs enables the following activities:

– Supervising and optimizing radio network performance to provide better quality or better use of available resources.

– Detecting performance issues in the network to preserve service quality.

– Providing radio network planners with detailed information for dimensioning, optimizing, and configuring the network.

– Troubleshooting on cell clusters of interest.

Performance Management (PM) counters collect performance statistics from measurements on live traffic in the radio network. These measurements do not interfere with user connection and transmission handling. The nodes can sometimes delay data collection and postpone the measurement period due to increased resource use. In this case, the results of the KPI
calculations can be observed as a minor peak in the overall performance statistics.

1.1 End-User Performance in LTE

Key Performance Indicators (KPIs) in LTE networks measure both end-user performance and network performance in the RAN. The performance of end-user applications is measured over a broader area than the RAN. As illustrated on , it covers the entire packet delivery chain.

PGW Packet Data Network Gateway

SGW Serving Gateway

TN Transport Network

UE User Equipment

Figure 1 LTE Packet Delivery Chain

1.2 Observability in Ericsson LTE

Observability covers all functions in LTE RAN that supervise the performance and characteristics of the network. This can be done on various levels with different target groups and requirements. Figure 2 illustrates a model for observability in LTE RAN.

Figure 2 Top-Down Approach in LTE RAN Observability

Table 1 Observability Levels and Purposes

Observability Level Description of Use

The KPI represents the end-user perception of a network on a macro level. Operators use KPI statistics to compare networks against each other, and to detect problems and errors. KPIs
Key Performance Indicator (KPI)
are calculated from PI and PM counters. The reliability, granularity, and accuracy of the data are critical, and the data is collected continuously.
The PI represents system level information that explains the KPI results. Many PIs can be based on PM counters, for example, PM counters for Root Cause Analysis. PIs can also be in the
Performance Indicator (PI)
form of metrics that show specific parts of the system can perform. PIs usually have an impact on KPIs. PIs can be collected on demand.
The RI represents system level information that explains the system capacity and resource use. The RI data can be used for planning and dimensioning. RI data, mostly from PM counters,
RI
can be collected continuously.
The Procedure level represents in-depth troubleshooting, and the measurements of system characteristics. Signalling, procedure, and function levels are included in the measurements.
The purpose of the measurements is to investigate problems detected at higher levels.
Procedure
The measurements are generally user-initiated for a specific purpose or for a specific area. The scope of the measurements are limited with the specified aspects. The source for the data is
mostly the UE trace and the cell trace recording functions.

For more information about UE trace and cell trace, see the document Performance Management (DU node) or Manage Performance (Baseband node).

1.3 LTE RAN Performance Observability Model

The LTE RAN Performance Observability model used by Ericsson combines the general, International Telecommunications Union-Telecommunications (ITU-T) QoS categories with mobility, availability and utilization.
Table 2 Ericsson Observability Model

QoS Categories Description

Accessibility The ability of a service to be obtained, within specified tolerances and other given conditions, when requested by the end user.
Retainability The probability that a service, once obtained, remains provided under given conditions for a given time duration.
Integrity The degree to which a service is provided without excessive impairments, once obtained. Service Integrity represents the quality experienced by the end user during the call or session.
Mobility The ability of the system to allow movement within the LTE RAN.
Availability The ability of an item to be in a state to perform a chosen function at a given instant of time within a given time interval, assuming that the external resources, if necessary, are provided.
Describes the network use by measuring traffic level and capacity resource management, including congestion, admission and load control, and license use. Utilization information is
Utilization
needed as input to network planning. For formulas to calculate utilization, see License and Resource Use Indicators.

In LTE, all sessions are Packet Switched (PS). The LTE network supports multiple simultaneous services per user. ITU-T definitions are used as guidelines for performance measurement.

KPIs are developed for observing the network performance impact on the end user, and for observing the performance of the network itself. Each KPI is defined for observing end-user impact or system performance.

1.4 Aggregation of KPIs

The PM counters can be aggregated in the following ways:

– Over a group of cells

– Over a cluster of cells

– Over one RBS

– Over multiple RBSs

– Over a complete geographic area

– Over time periods (hour, days, week)

Aggregation needs to be considered for maximum calculations in case of some PIs, where the maximum value means the average of maximum or the maximum of average. A distribution function can be created as an alternative for the set of max values, so that the range of values can be preserved and highlighted. In some cases, the data-capture tool and also the user data
can provide some further aggregation.

Many KPIs are basically a ratio of two quantities (for example, between success and failure, or between volume and time). Based on the two quantities, two basic aggregation methodologies are available that can produce different results. The operator needs to consider exactly what is calculated, and also know the advantage and disadvantage of the calculated quantities.

The PM counters can be aggregated over time (for example, hour, day or week) for a specific cell to get a cell-specific, time aggregated PI. The cell PI can be aggregated over cell clusters to get an average over an area. Use both equations for the aggregation.

Example of Aggregation

1. Aggregate the individual PM counter values across the time and geographic area using the equation.

2. Perform the PI equation.

In certain situations, an operator needs to replace the individual pmXyz PM counter in each equation to get a metric over a larger area and longer time, or for both.

1. Calculate the PI equation for the specific metric at the lower time and geographic resolution with the formula.

2. Aggregate across the longer time and larger geographic area using the equation.

Note: When a formula involves the sum of fractions (for example, the sum of PI(Cell&ROP), the result of the formula indicates an invalid result that is invalid for all fractions involved. When the result is invalid for less than all fractions involved in the formula, the invalid fractions (for example, 0 / 0) are ignored. In this case, the value of " N " is to be adjusted.

Result of Aggregation

– Use of aggregated pmXyz can mask individual cells or times when there are not usual results in a specific time or location. This can result in an overall average.

– Use of PI(Cell&ROP) can highlight the impact of individual metrics as each PI is equally weighted. This results in equal amount of weight for cells with minimal traffic and with large traffic. The final result can be biased.

– In cases where the denominator pmRst(Cell&ROP) is a fixed number in the samples (for example, 900 seconds in a ROP), then both methods produce the same result.

– In case of throughput metrics, SUM(all_Volume) / SUM(all_Time), can introduce significant bias. For example, if a few UEs require a long delivery time because of poor RF. This can hide the benefits of features such as Carrier Aggregation and Frequency Selective Scheduling that attempt to maximize individual UE throughput.

– Aggregation of quantities based on time (for example, pmUeThpTimeDl and pmDrbThpTimeDlQci time counters, or uplink and downlink throughput metrics) need special consideration as aggregation when metric occurs simultaneously on same entity. Results can differ significantly from aggregation when there is no simultaneity. In reality, there is often a mixture
of simultaneous and sequential actions which are challenging to interpret. Simultaneity can impact the definition of some PM counters. The pmPdcpVolDlDrbLastTti and SUM(pmPdcpVolDlLastTtiQci) PM Counters can be different depending on the simultaneity (at TTI level) of the individual QCI bursts.

– Same aggregation methodology needs to be used comparing results to avoid any differences triggered by the aggregation.

– SUM function needs to be avoided, if the aggregated quantities are depending on each other. For example, the volume and time metrics related to lastTt.

– The type of aggregation can be decided based on the date capture tool or the context and purpose of use.

Aggregation is indicated in the formulas when in use.

1.5 Service Separation of Observability in LTE RAN

In an LTE system, the service is not directly known to the RAN. If a service is mapped towards a specific Quality of Service Class Indicator (QCI) or Allocation Retention Priority (ARP), then it is possible to determine the observability of the service.
Emergency Calls If it is defined that Emergency (EM) Calls have a specific AR, accessibility for Emergency calls can be determined by using the Initial E-RAB Establishment Success Rate for Emergency Calls formula.
Web sessions If seven is defined as QCI for Web sessions, downlink Throughput for Web sessions can be determined using the DL Throughput per QCI formula.

VoIP If one is defined as QCI for VoIP, Retainability for VoIP can be determined using the E-RAB Retainability - Percentage Lost per QCI formula.

Note: The ARP and QCI values are only examples. More information about the different uses of ARP and QCI can be found in TS 23.203.

For the uplink, the scheduler grants resources based on Logical Channel Groups (LCG) instead of QCI. Some uplink measurement per LCG is preferable than per QCI. For more information about LCG and QCI, see Quality of Service (DU node) or Manage Quality of Service (Baseband node).

1.6 Detailed Separation of Observability in LTE RAN with Flexible Counters

When new UE categories are introduced with different characteristics, for example Cat-M1 UE devices, KPIs can show higher or lower values. The solution can be using the Flexible Counters feature or using PM counters that are related to the specific characteristics.

about:blank 2/26
12/30/22, 4:18 PM Key Performance Indicators

The Flexible Counters feature can be used for the following purposes:

– Replacing the existing PM counters with the use of flexible counters and filters to the related PM counters. For example, if two PLMNs are used and the result for throughput is needed separately. The flexible counters filtered on the two PLMNs replace the legacy PM counters in the corresponding KPI.

– Compensating KPIs with subtracting legacy PM counters of a KPI formula and replacing it with flexible counters filtered on a specific characteristic. For example, Cat-M1 UE part is subtracting from the throughput KPI. The maximum throughput for Cat-M1 UE devices is lower than the average, which results in overall lower average for UE throughput. This can be
compensated by using flexible counters filtered on the Cat-M1 UE category.

Each KPI formula that can be used with flexible counters are indicated with an example.
Note: The Flexible Counters feature is not supported on DUL 20 and Pico RBS.

For list of filters supported by flexible counters, see Flexible Counters.

Note: These figures are only examples of KPIs, and cannot be used for measurement purposes.

about:blank 3/26
12/30/22, 4:18 PM Key Performance Indicators

2 Accessibility
2.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 PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Initial E-RAB Establishment Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Initial E-RAB Establishment Success Rate:

Figure 3 Initial E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmRrcConnEstabSucc

– pmRrcConnEstabAtt

– pmRrcConnEstabAttReatt

– pmRrcConnEstabFailMmeOvlMos

– pmRrcConnEstabFailMmeOvlMod

– pmS1SigConnEstabSucc

– pmS1SigConnEstabAtt

– pmS1SigConnEstabFailMmeOvlMos

– pmErabEstabSuccInit

– pmErabEstabAttInit

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReatt.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected. In such a case PM counter pmRrcConnEstabAtt is pegged, PM counter pmRrcConnEstabAttReAtt is NOT pegged for the reattempt. Double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAtt is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject

– These KPIs are differentiated using flexible counters see Differentiated Initial E-RAB Establishment Success Rate.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated Initial E-RAB Establishment Success Rate.

2.2 Initial E-RAB Establishment Success Rate per QCI 19.Q4 and later
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 PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status PRELIMINARY

Calculate Initial E-RAB Establishment Success Rate per QCI 19.Q4 and later by using the following formula:

The results of the following subformulas are used in the calculation of Initial E-RAB Establishment Success Rate per QCI 19.Q4 and later:

Figure 4 Initial E-RAB Establishment Success Rate per QCI 19.Q4 and later

The following counters are used in the formulas:

– pmRrcConnEstabSuccMod

– pmRrcConnEstabSuccMoVoice

– pmRrcConnEstabSuccMta

– pmRrcConnEstabSuccHpa

– pmRrcConnEstabAttMod

– pmRrcConnEstabAttMoVoice

– pmRrcConnEstabAttMta

– pmRrcConnEstabAttHpa

– pmRrcConnEstabFailMmeOvlMod

– pmRrcConnEstabAttReattMod

– pmRrcConnEstabAttReattMoVoice

– pmRrcConnEstabAttReattMta

– pmRrcConnEstabAttReattHpa

– pmS1SigConnEstabSuccMod

– pmS1SigConnEstabSuccMoVoice

– pmS1SigConnEstabSuccMta

– pmS1SigConnEstabSuccHpa

– pmS1SigConnEstabAttMod

– pmS1SigConnEstabAttMoVoice

– pmS1SigConnEstabAttMta

– pmS1SigConnEstabAttHpa

– pmErabEstabSuccInitQci

– pmErabEstabAttInitQci

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReattMod and pmRrcConnEstabAttReattMta. If the pm...Mod and pm...Mta sub-
components are not available, then the parent PM counters can be used.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected, although pmRrcConnEstabAttxxx are pegged, pmRrcConnEstabAttReAttxxx are NOT pegged for the reattempt. Double counting of the attempt is possible.

– PM counter pmRrcConnEstabAttMod is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receive an RRC connection reject.

– Several of these PM counters are not included in any predefined scanner.

– See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

2.3 Differentiated 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 PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Differentiated Initial E-RAB Establishment Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Differentiated Initial E-RAB Establishment Success Rate:

about:blank 4/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 5 Differentiated Initial E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmRrcConnEstabSucc

– pmRrcConnEstabAtt

– pmRrcConnEstabAttReatt

– pmRrcConnEstabFailMmeOvlMos

– pmRrcConnEstabFailMmeOvlMod

– pmS1SigConnEstabSucc

– pmS1SigConnEstabAtt

– pmS1SigConnEstabFailMmeOvlMos

– pmFlexErabEstabSuccInit

– pmFlexErabEstabAttInit

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReatt.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected. In such a case PM counter pmRrcConnEstabAtt is pegged, PM counter pmRrcConnEstabAttReAtt is NOT pegged for the reattempt. Double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAtt is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject

– These KPIs are differentiated using flexible counters.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated Initial E-RAB Establishment Success Rate.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

2.4 Compensated 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 PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Initial E-RAB Establishment Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Compensated Initial E-RAB Establishment Success Rate:

Figure 6 Compensated Initial E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmRrcConnEstabSucc

– pmRrcConnEstabAtt

– pmRrcConnEstabAttReatt

– pmRrcConnEstabFailMmeOvlMos

– pmRrcConnEstabFailMmeOvlMod

– pmS1SigConnEstabSucc

– pmS1SigConnEstabAtt

– pmS1SigConnEstabFailMmeOvlMos

– pmErabEstabSuccInit

– pmErabEstabAttInit

– pmFlexErabEstabSuccInit

– pmFlexErabEstabAttInit

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReatt.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected. In such a case PM counter pmRrcConnEstabAtt is pegged, PM counter pmRrcConnEstabAttReAtt is NOT pegged for the reattempt. Double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAtt is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject

– These KPIs are differentiated using flexible counters see Differentiated Initial E-RAB Establishment Success Rate.

– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

2.5 Initial E-RAB Establishment Success Rate for Emergency Calls

This KPI measures the impact on the end user.

The following equation gives the accessibility success rate for emergency calls that are carried by E-RABs included in the Initial UE Context setup procedure. The PM counters in this KPI are on cell level and per ARP (hence only include the ARP range that defines Emergency).

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Initial E-RAB Establishment Success Rate for Emergency Calls by using the following formula:

Figure 7 Initial E-RAB Establishment Success Rate for Emergency Calls

The following counters are used in the formulas:

– pmRrcConnEstabSuccEm

– pmRrcConnEstabAttEm

– pmRrcConnEstabAttReattEm

– pmS1SigConnEstabSuccEm

– pmS1SigConnEstabAttEm

– pmErabEstabSuccInitArp

– pmErabEstabAttInitArp

Note:
– If an RRC Connection Establishment reattempt is rejected because of high load or overload, then although pmRrcConnEstabAttEm are pegged, pmRrcConnEstabAttReAttEm are NOT pegged for the reattempt, thus some double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAttEm is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject.

– Several of these PM counters are not included in any predefined scanner

2.6 Initial E-RAB Establishment Success Rate, No MO Signaling

This KPI measures the E-RAB establishment success rate and one can remove all RRC connection requests that are set up for signaling from the first parts of the formula. That would result in the following alternative formula for initial E-RAB establishment success rate, no MO signaling.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Initial E-RAB Establishment Success Rate, No MO Signaling by using the following formula:

The results of the following subformulas are used in the calculation of Initial E-RAB Establishment Success Rate, No MO Signaling:

about:blank 5/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 8 Initial E-RAB Establishment Success Rate, No MO Signaling

The following counters are used in the formulas:

– pmRrcConnEstabSucc

– pmRrcConnEstabSuccMos

– pmRrcConnEstabFailMmeOvlMod

– pmRrcConnEstabAtt

– pmRrcConnEstabAttMos

– pmRrcConnEstabAttReatt

– pmRrcConnEstabAttReattMos

– pmS1SigConnEstabSucc

– pmS1SigConnEstabSuccMos

– pmS1SigConnEstabAtt

– pmS1SigConnEstabAttMos

– pmErabEstabSuccInit

– pmErabEstabAttInit

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReatt.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected. In such a case PM counter pmRrcConnEstabAtt is pegged, PM counter pmRrcConnEstabAttReAtt is NOT pegged for the reattempt. Double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAtt is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject

– These KPIs are differentiated using flexible counters see Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling.

2.7 Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling

This KPI measures the E-RAB establishment success rate and one can remove all RRC connection requests that are set up for signaling from the first parts of the formula. That would result in the following alternative formula for initial E-RAB establishment success rate, no MO signaling.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling by using the following formula:

The results of the following subformulas are used in the calculation of Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling:

Figure 9 Differentiated Initial E-RAB Establishment Success Rate, No MO Signaling

The following counters are used in the formulas:

– pmRrcConnEstabSucc

– pmRrcConnEstabSuccMos

– pmRrcConnEstabFailMmeOvlMod

– pmRrcConnEstabAtt

– pmRrcConnEstabAttMos

– pmRrcConnEstabAttReatt

– pmRrcConnEstabAttReattMos

– pmS1SigConnEstabSucc

– pmS1SigConnEstabSuccMos

– pmS1SigConnEstabAtt

– pmS1SigConnEstabAttMos

– pmFlexErabEstabSuccInit

– pmFlexErabEstabAttInit

Note:
– The impact of multiple E-RABs in the Initial context setup procedure is not considered in the RRC and S1 signaling part contribution. Compared to 3GPP 32.450 definition of the KPI, Ericsson subtract repetitive attempts from the same UE, see definition of pmRrcConnEstabAttReatt.

– During the high load or overload an RRC Connection Establishment reattempt can be rejected. In such a case PM counter pmRrcConnEstabAtt is pegged, PM counter pmRrcConnEstabAttReAtt is NOT pegged for the reattempt. Double counting of the attempt is possible.

– The PM counter pmRrcConnEstabAtt is not stepped when the cell soft lock has started, even though the UE can still try to make RRC Connection Requests until the cell becomes locked and UE receives an RRC connection reject

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

2.8 Added E-RAB Establishment Success Rate

This KPI measures the impact on the end user. Accessibility success rate for end-user services which is carried by E-RABs included in the E-RAB setup procedure is given by the following equation. The PM counters in this KPI are on cell level. The KPI excludes the additional E-RAB setup attempts made during ongoing procedure and setup attempts that lead to CS Fallback.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Added E-RAB Establishment Success Rate by using the following formula:

Figure 10 Added E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmErabEstabSuccAdded

– pmErabEstabAttAdded

– pmErabEstabFailAddedOngoingProc

– pmErabEstabAttAddedCsfb

Note:
– This KPI can be compensated or differentiated by using flexible counters see Compensated added E-RAB Establishment Success Rate and Differentiated added E-RAB Establishment Success Rate.

2.9 Differentiated Added E-RAB Establishment Success Rate

This KPI measures the impact on the end user. Accessibility success rate for end-user services which is carried by E-RABs included in the E-RAB setup procedure is given by the following equation. The PM counters in this KPI are on cell level. The KPI excludes the additional E-RAB setup attempts made during ongoing procedure and setup attempts that lead to CS Fallback.
Formula can be differentiated with different filter counters when the operator configures them as pmFlex.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Differentiated Added E-RAB Establishment Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Differentiated Added E-RAB Establishment Success Rate:

Figure 11 Differentiated Added E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmFlexErabEstabSuccAdded

– pmFlexErabEstabAttAdded

– pmFlexErabEstabFailAddedOngoingProc

– pmFlexErabEstabAttAddedCsfb

about:blank 6/26
12/30/22, 4:18 PM Key Performance Indicators

Note:
– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

2.10 Compensated Added E-RAB Establishment Success Rate

This KPI measures the impact on the end user. Accessibility success rate for end-user services which is carried by E-RABs included in the E-RAB setup procedure is given by the following equation. The PM counters in this KPI are on cell level. The KPI excludes the additional E-RAB setup attempts made during ongoing procedure and setup attempts that lead to CS Fallback.
Formula can be compensated with different filter counters when the operator configures them as pmFlex.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Added E-RAB Establishment Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Compensated Added E-RAB Establishment Success Rate:

Figure 12 Compensated Added E-RAB Establishment Success Rate

The following counters are used in the formulas:

– pmErabEstabAttAdded

– pmFlexErabEstabAttAdded

– pmErabEstabFailAddedOngoingProc

– pmFlexErabEstabFailAddedOngoingProc

– pmErabEstabSuccAdded

– pmFlexErabEstabSuccAdded

– pmErabEstabAttAddedCsfb

– pmFlexErabEstabAttAddedCsfb

Note:
– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

2.11 Added E-RAB Establishment Success Rate per QCI

This KPI measures the impact on the end user.

Accessibility success rate for end-user services which is carried by E-RABs included in the E-RAB setup procedure is given by the following equation. The PM counters in this KPI are on cell level per QCI.

The KPI excludes the additional E-RAB setup attempts made during ongoing handover and setup attempts that lead to CS Fallback.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Added E-RAB Establishment Success Rate per QCI by using the following formula:

Figure 13 Added E-RAB Establishment Success Rate per QCI

The following counters are used in the formulas:

– pmErabEstabSuccAddedQci

– pmErabEstabAttAddedQci

– pmErabEstabAttAddedHoOngoingQci

– pmErabEstabAttAddedCsfbQci

Note:
– Flexible counters can be used to select measurements for particular QCIs see Differentiated Added E-RAB Establishment Success Rate.

2.12 Added E-RAB Establishment Success Rate for Emergency Calls

This KPI measures the impact on the end user.

Accessibility success rate for emergency calls which is carried by E-RABs included in the E-RAB setup procedure is given by the following equation. The PM counters in this KPI are on cell level and per ARP (hence only include the ARP range that defines Emergency).

The KPI excludes the additional E-RAB setup attempts made during ongoing handover and setup attempts that lead to CS Fallback.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Added E-RAB Establishment Success Rate for Emergency Calls by using the following formula:

Figure 14 Added E-RAB Establishment Success Rate for Emergency Calls

The following counters are used in the formulas:

– pmErabEstabSuccAddedArp

– pmErabEstabAttAddedArp

– pmErabEstabAttAddedHoOngoingArp

– pmErabEstabAttAddedCsfbArp

2.13 Robust Random Access Success Rate

This KPI measures the impact on the end user.

Robust Random Access Success Rate describes how often a transmitted RaMsg2 results in a successfully received RaMsg3. The PM counters are on a cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Robust Random Access Success Rate by using the following formula:

Figure 15 Robust Random Access Success Rate

The following counters are used in the formulas:

– pmRaSuccCbra

– pmRaMsg2AttCbra

2.14 Random Access MSG1 Success Rate

Random Access MSG1 Success Rate describes how often a detected preamble results in a successfully allocated RaMsg2 in DL.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Random Access MSG1 Success Rate by using the following formula:

Figure 16 Random Access MSG1 Success Rate

The following counters are used in the formulas:

– pmRaMsg2AttCbra

– pmRaAttCbra

Note:
– The PM counters in the Equation are not included in any predefined scanner.

2.15 Robust Random Access Success Rate for Cat-M1 UE devices

The following KPI is supported for Cat-M1 UE.

about:blank 7/26
12/30/22, 4:18 PM Key Performance Indicators

Robust Random Access Success Rate describes how often a transmitted RaMsg2 results in a successfully received RaMsg3.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Robust Random Access Success Rate for Cat-M1 UE devices by using the following formula:

Figure 17 Robust Random Access Success Rate for Cat-M1 UE devices

The following counters are used in the formulas:

– pmRaSuccCbraBr

– pmRaMsg2AttCbraBr

2.16 Random Access MSG1 Success Rate for Cat-M1 UE devices

The following KPI is supported for Cat-M1 UE.

Random Access MSG1 Success Rate describes how often a detected preamble results in a successfully allocated RaMsg2 in DL.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Random Access MSG1 Success Rate for Cat-M1 UE devices by using the following formula:

Figure 18 Random Access MSG1 Success Rate for Cat-M1 UE devices

The following counters are used in the formulas:

– pmRaMsg2AttCbraBr

– pmRaAttCbraBr

2.17 eMBMS Establishment Success Rate

This KPI measures the impact on the end user.

Accessibility success rate for end-user eMBMS is given by the following equation. The PM counters in this KPI are on RBS level.

Network Function LTE

Level ENodeBFunction

Formula Status CURRENT

Calculate eMBMS Establishment Success Rate by using the following formula:

Figure 19 eMBMS Establishment Success Rate

The following counters are used in the formulas:

– pmMbmsSessionEstabSucc

– pmMbmsSessionEstabAtt

Note:
– The PM counters in the Equation are not included in any predefined scanner.

about:blank 8/26
12/30/22, 4:18 PM Key Performance Indicators

3 Retainability
3.1 E-RAB Retainability - Session Time Normalized Loss Rate
This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for E-RAB is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Session Time Normalized Loss Rate by using the following formula:

Figure 20 E-RAB Retainability - Session Time Normalized Loss Rate

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalMmeAct

– pmSessionTimeUe

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula. The contribution of several components including pmErabRelAbnormalEnbActTnFail and
pmErabRelAbnormalEnbActCdt are not part of the 3GPP 32.450 definition of the KPI. However, Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).

– 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.

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Session Time Normalized Loss Rate.

– Cat-M1 UE devices impact on the PM counters pmErabRelAbnormalEnbAct and pmErabRelAbnormalMmeAct must be compensated for by using flexible counters as Cat-M1 UE devices are not included into the PM counter pmSessionTimeUe.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Session Time Normalized Loss Rate.

3.2 E-RAB Retainability - Session Time Normalized Loss Rate the Second
This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for E-RAB is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Session Time Normalized Loss Rate the Second by using the following formula:

Figure 21 E-RAB Retainability - Session Time Normalized Loss Rate the Second

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmSessionTimeUe

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula. The contribution of several components including pmErabRelAbnormalEnbActTnFail and
pmErabRelAbnormalEnbActCdt are not part of the 3GPP 32.450 definition of the KPI. However, Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).

– 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.

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Session Time Normalized Loss Rate the Second.

– Cat-M1 UE devices impact on the PM counter pmErabRelAbnormalEnbAct must be compensated for by using flexible counters as Cat-M1 UE devices are not included into the PM counter pmSessionTimeUe.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Session Time Normalized Loss Rate the Second.

3.3 Compensated E-RAB Retainability - Session Time Normalized Loss Rate

This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for E-RAB is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated E-RAB Retainability - Session Time Normalized Loss Rate by using the following formula:

The results of the following subformulas are used in the calculation of Compensated E-RAB Retainability - Session Time Normalized Loss Rate:

Figure 22 Compensated E-RAB Retainability - Session Time Normalized Loss Rate

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalMmeAct

– pmSessionTimeUe

– pmFlexErabRelAbnormalEnbAct

– pmFlexErabRelAbnormalMmeAct

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula. The contribution of several components including pmErabRelAbnormalEnbActTnFail and
pmErabRelAbnormalEnbActCdt are not part of the 3GPP 32.450 definition of the KPI. However, Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).

– 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.

– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

3.4 Compensated E-RAB Retainability - Session Time Normalized Loss Rate, the Second
This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for E-RAB is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated E-RAB Retainability - Session Time Normalized Loss Rate, the Second by using the following formula:

Figure 23 Compensated E-RAB Retainability - Session Time Normalized Loss Rate, the Second

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmSessionTimeUe

– pmFlexErabRelAbnormalEnbAct

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula. The contribution of several components including pmErabRelAbnormalEnbActTnFail and
pmErabRelAbnormalEnbActCdt are not part of the 3GPP 32.450 definition of the KPI. However, Ericsson thinks it is important to include these cases even if there is no S1AP messages for these cases (the 32.425 have its triggers built on S1AP triggers).

– 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.

– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

3.5 E-RAB Retainability - Session Time Normalized per QCI Loss Rate
This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for an end-user service that is carried by E-RAB is given by the following equation. The PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Session Time Normalized per QCI Loss Rate by using the following formula:
about:blank 9/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 24 E-RAB Retainability - Session Time Normalized per QCI Loss Rate

The following counters are used in the formulas:

– pmErabRelAbnormalEnbActQci

– pmErabRelAbnormalMmeActQci

– pmSessionTimeDrbQci

Note:
– 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.

– 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 pmErabRelAbnormalMmeActQci in the formula.

– The PM counters in the Equation are not included in any predefined scanner.

– Cat-M1 UE devices impact on the PM counters pmErabRelAbnormalEnbActQci and pmErabRelAbnormalMmeActQci must be compensated for by using flexible counters as Cat-M1 UE devices are not included into the PM counter pmSessionTimeDrbQci see Compensated E-RAB Retainability - Session Time Normalized Loss Rate.

– 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, exclude pmErabRelAbnormalMmeActQci in the formula.

3.6 E-RAB Retainability - Session Time Normalized per QCI Loss Rate, the Second
This KPI measures the impact on the end user with the purpose to reflect the rate of abnormal releases.

The Retainability Loss rate for an end-user service that is carried by E-RAB is given by the following equation. The PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Session Time Normalized per QCI Loss Rate, the Second by using the following formula:

Figure 25 E-RAB Retainability - Session Time Normalized per QCI Loss Rate, the Second

The following counters are used in the formulas:

– pmErabRelAbnormalEnbActQci

– pmSessionTimeDrbQci

Note:
– 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.

– 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 pmErabRelAbnormalMmeActQci in the formula.

– The PM counters in the Equation are not included in any predefined scanner.

– Cat-M1 UE devices impact on the PM counters pmErabRelAbnormalEnbActQci and pmErabRelAbnormalMmeActQci must be compensated for by using flexible counters as Cat-M1 UE devices are not included into the PM counter pmSessionTimeDrbQci see Compensated E-RAB Retainability - Session Time Normalized Loss Rate the Second.

– 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, exclude pmErabRelAbnormalMmeActQci in the formula.

3.7 E-RAB Retainability - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The Retainability Loss rate for E-RAB is given by the following equations. The PM counters in this KPI are on cell level and may be differentiated also per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Percentage Lost by using the following formula:

Figure 26 E-RAB Retainability - Percentage Lost

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalMmeAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

Note:
– Several of these PM counters are not included in any predefined scanner.

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Percentage Lost.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Percentage Lost.

3.8 Differentiated E-RAB Retainability - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The Retainability Loss rate for E-RAB is given by the following equations. The PM counters in this KPI are on cell level and may be differentiated also per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Differentiated E-RAB Retainability - Percentage Lost by using the following formula:

The results of the following subformulas are used in the calculation of Differentiated E-RAB Retainability - Percentage Lost:

Figure 27 Differentiated E-RAB Retainability - Percentage Lost

The following counters are used in the formulas:

– pmFlexErabRelAbnormalEnbAct

– pmFlexErabRelAbnormalMmeAct

– pmFlexErabRelAbnormalEnb

– pmFlexErabRelNormalEnb

– pmFlexErabRelMme

Note:
– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

3.9 Compensated E-RAB Retainability - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The Retainability Loss rate for E-RAB is given by the following equations. The PM counters in this KPI are on cell level and may be differentiated also per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated E-RAB Retainability - Percentage Lost by using the following formula:

The results of the following subformulas are used in the calculation of Compensated E-RAB Retainability - Percentage Lost:

Figure 28 Compensated E-RAB Retainability - Percentage Lost

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

about:blank 10/26
12/30/22, 4:18 PM Key Performance Indicators

– pmErabRelAbnormalMmeAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

– pmFlexErabRelAbnormalEnbAct

– pmFlexErabRelAbnormalMmeAct

– pmFlexErabRelAbnormalEnb

– pmFlexErabRelNormalEnb

– pmFlexErabRelMme

Note:
– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

3.10 E-RAB Retainability (eNB) - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability (eNB) - Percentage Lost by using the following formula:

Figure 29 E-RAB Retainability (eNB) - Percentage Lost

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

– pmErabRelMmeActEutra

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 pmErabRelMmeActEutra in the formula.

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Percentage Lost & Compensated E-RAB Retainability(eNB) - Percentage Lost, the Second

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Percentage Lost & Compensated E-RAB Retainability(eNB) - Percentage Lost, the Second.

– Several of these PM counters are not included in any predefined scanner.

3.11 E-RAB Retainability (eNB) - Percentage Lost, the Second

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability (eNB) - Percentage Lost, the Second by using the following formula:

Figure 30 E-RAB Retainability (eNB) - Percentage Lost, the Second

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

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 pmErabRelMmeActEutra in the formula..

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Percentage Lost & Compensated E-RAB Retainability(eNB) - Percentage Lost, the Second

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Percentage Lost & Compensated E-RAB Retainability(eNB) - Percentage Lost, the Second.

– Several of these PM counters are not included in any predefined scanner.

3.12 Compensated E-RAB Retainability (eNB) - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated E-RAB Retainability (eNB) - Percentage Lost by using the following formula:

The results of the following subformulas are used in the calculation of Compensated E-RAB Retainability (eNB) - Percentage Lost:

Figure 31 Compensated E-RAB Retainability (eNB) - Percentage Lost

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

– pmFlexErabRelAbnormalEnbAct

– pmFlexErabRelAbnormalEnb

– pmFlexErabRelNormalEnb

– pmFlexErabRelMme

– pmErabRelMmeActEutra

– pmFlexErabRelMmeActEutra

Note:
– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

3.13 Compensated E-RAB Retainability (eNB) - Percentage Lost, the Second

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RABs that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

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, exclude pmErabRelAbnormalMmeAct or replace it with pmErabRelMmeActEutra in the formula.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated E-RAB Retainability (eNB) - Percentage Lost, the Second by using the following formula:

The results of the following subformulas are used in the calculation of Compensated E-RAB Retainability (eNB) - Percentage Lost, the Second:

about:blank 11/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 32 Compensated E-RAB Retainability (eNB) - Percentage Lost, the Second

The following counters are used in the formulas:

– pmErabRelAbnormalEnbAct

– pmErabRelAbnormalEnb

– pmErabRelNormalEnb

– pmErabRelMme

– pmFlexErabRelAbnormalEnbAct

– pmFlexErabRelAbnormalEnb

– pmFlexErabRelNormalEnb

– pmFlexErabRelMme

Note:
– Please see Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN on Dependencies and Associated Features for more information. These flexible counters are not included in any predefined scanner.

3.14 E-RAB Retainability - Percentage Lost per QCI

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RAB that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The Retainability rate for an end-user service that is carried by E-RAB is given by the following equations. The PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Percentage Lost per QCI by using the following formula:

Figure 33 E-RAB Retainability - Percentage Lost per QCI

The following counters are used in the formulas:

– pmErabRelAbnormalEnbActQci

– pmErabRelAbnormalMmeActQci

– pmErabRelAbnormalEnbQci

– pmErabRelNormalEnbQci

– pmErabRelMmeQci

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– This KPI can be compensated by using flexible counters see Compensated E-RAB Retainability - Percentage Lost.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available see Compensated E-RAB Retainability - Percentage Lost.

– 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, exclude pmErabRelAbnormalMmeActQci in the formula.

3.15 E-RAB Retainability - Percentage Lost for Emergency Calls

This KPI measures the impact on the end user with the purpose to reflect the percentage of established E-RAB that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The Retainability rate for Emergency Calls that is carried by E-RAB is given by the following equation. The PM counters in this KPI are on cell level and per ARP (hence only include the ARP range that defines Emergency).

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate E-RAB Retainability - Percentage Lost for Emergency Calls by using the following formula:

Figure 34 E-RAB Retainability - Percentage Lost for Emergency Calls

The following counters are used in the formulas:

– pmErabRelAbnormalEnbActArp

– pmErabRelAbnormalMmeActArp

– pmErabRelAbnormalEnbArp

– pmErabRelNormalEnbArp

– pmErabRelMmeArp

Note:
– Several of these PM counters are not included in any predefined scanner.

– 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, exclude pmErabRelAbnormalMmeActArp in the formula.

3.16 eMBMS Retainability - Percentage Lost

This KPI measures the impact on the end user with the purpose to reflect the percentage of established eMBMS sessions that are lost with an abnormal release. Good retainability is shown by a low value metric for example, < 5%.

The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate eMBMS Retainability - Percentage Lost by using the following formula:

The results of the following subformulas are used in the calculation of eMBMS Retainability - Percentage Lost:

Figure 35 eMBMS Retainability - Percentage Lost

The following counters are used in the formulas:

– pmMbmsSessionEnd

– pmMbmsSessionStopAuditTimer

– pmMbmsSessionStopMme

– pmMbmsSessionStopMmeNoSession

Note:
– The PM counters in the Equation are not included in any predefined scanner.

about:blank 12/26
12/30/22, 4:18 PM Key Performance Indicators

4 Integrity
4.1 Average DL UE Latency
This KPI measures the impact on the end user. The latency increases with more instantaneously active UEs and also depends on the scheduling algorithms being used.

DL latency for the UE is given by the following equation. The PM counters in this KPI are on cell level and can be differentiated per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL UE Latency by using the following formula:

Figure 36 Average DL UE Latency

The following counters are used in the formulas:

– pmPdcpLatTimeDl

– pmPdcpLatPktTransDl

Note:
– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– This KPI can be compensated by using flexible counters see Compensated average DL UE Latency definition. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

4.2 Compensated Average DL UE Latency

This KPI measures the impact on the end user. The latency increases with more instantaneously active UEs and also depends on the scheduling algorithms being used.

DL latency for the UE is given by the following equation. The PM counters in this KPI are on cell level and can be differentiated per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average DL UE Latency by using the following formula:

Figure 37 Compensated Average DL UE Latency

The following counters are used in the formulas:

– pmPdcpLatTimeDl

– pmPdcpLatPktTransDl

– pmFlexPdcpLatTimeDl

– pmFlexPdcpLatPktTransDl

4.3 Average DL PDCP DRB LTE Latency per QCI

DL latency for a DRB with a given QCI value for LTE UEs. The PM counters in this KPI are on cell level per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP DRB LTE Latency per QCI by using the following formula:

Figure 38 Average DL PDCP DRB LTE Latency per QCI

The following counters are used in the formulas:

– pmPdcpLatTimeDlDrxNoSyncQci

– pmPdcpLatTimeDlNoDrxSyncQci

– pmPdcpLatTimeDlDrxSyncQci

– pmPdcpLatTimeDlNoDrxNoSyncQci

– pmPdcpLatPktTransDlDrxNoSyncQci

– pmPdcpLatPktTransDlNoDrxSyncQci

– pmPdcpLatPktTransDlDrxSyncQci

– pmPdcpLatPktTransDlNoDrxNoSyncQci

4.4 Average DL PDCP DRB Cat-M Latency per QCI

DL latency for a DRB with a given QCI value for Cat-M UEs. The PM counters in this KPI are on cell level per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP DRB Cat-M Latency per QCI by using the following formula:

Figure 39 Average DL PDCP DRB Cat-M Latency per QCI

The following counters are used in the formulas:

– pmPdcpLatTimeDlCatMDrxNoSyncQci

– pmPdcpLatTimeDlCatMNoDrxSyncQci

– pmPdcpLatTimeDlCatMDrxSyncQci

– pmPdcpLatTimeDlCatMNoDrxNoSyncQci

– pmPdcpLatPktTransDlCatMDrxNoSyncQci

– pmPdcpLatPktTransDlCatMNoDrxSyncQci

– pmPdcpLatPktTransDlCatMDrxSyncQci

– pmPdcpLatPktTransDlCatMNoDrxNoSyncQci

4.5 Average DL UE PDCP DRB Latency per QCI

DL latency for a DRB with a given QCI value is given by the following equation. The PM counters in this KPI are on cell level per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL UE PDCP DRB Latency per QCI by using the following formula:

Figure 40 Average DL UE PDCP DRB Latency per QCI

The following counters are used in the formulas:

– pmPdcpLatTimeDlQci

– pmPdcpLatPktTransDlQci

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The difference in interpretation between this metric and the next metric is shown in Figure Latency Counters.

– DL PDCP DRB latency is counted once for each PDCP active burst. A burst is defined as time from the new data arrives to an empty PDCP buffer until all the data from that buffer is fetched to the HARQ buffers on the MAC layer and the PDCP buffer gets empty again.

– Flexible counters can be used to select PM counters for particular QCIs. Filter parameters can be used for PM counters pmFlexPdcpLatTimeDl_Filter, pmFlexPdcpLatPktTransDl_Filter. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.6 Average DL MAC DRB Latency per QCI

Average DL latency measurement per burst for a DRB with a given QCI value is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L21Q1.1

about:blank 13/26
12/30/22, 4:18 PM Key Performance Indicators

Calculate Average DL MAC DRB Latency per QCI by using the following formula:

Figure 41 Average DL MAC DRB Latency per QCI

The following counters are used in the formulas:

– pmMacLatTimeDlQci

– pmMacTimeDlSampQci

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The pmMacLatTimeDlQci and pmMacTimeDlSampQci PM counters are not available on DUL 20.

– DL MAC DRB latency is counted once for each active burst. A burst is defined as time from the new data arrives to an empty PDCP buffer until all the data from that buffer is successfully transmitted on the MAC layer and both the PDCP buffer and HARQ buffers get empty.

– Different active burst definitions are used for the latency counters pmPdcpLatTimeDlQci and pmMacLatTimeDlQci, (see Figure Latency Counters). This means that if a new PDCP data arrives during the transmission of the last data in the previous PDCP burst, a new burst is considered by pmPdcpLatTimeDlQci calculations but not by pmMacLatTimeDlQci. That
is new values are added to the counters pmPdcpLatTimeDlQci and pmPdcpLatPktTransDlQci but not to the counters pmMacLatTimeDlQci and pmMacTimeDlSampQci. Hence, in general, latency counters pmPdcpLatTimeDlQci and pmMacLatTimeDlQci can count different number of samples, especially when radio environment conditions are bad and number of
HARQ retransmissions is high.

– Flexible counters can be used to select measurements for particular QCIs. Filter parameters can be used for PM counters pmFlexMacLatTimeDl_Filter, pmFlexMacTimeDlSamp_Filter. See Equation Differentiated Average DL MAC DRB Latency.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.7 Differentiated Average DL MAC DRB Latency per QCI

Average Differentiated DL latency measurement per burst for a DRB with a given QCI value is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L21Q1.1

Calculate Differentiated Average DL MAC DRB Latency per QCI by using the following formula:

Figure 42 Differentiated Average DL MAC DRB Latency per QCI

The following counters are used in the formulas:

– pmFlexMacLatTimeDl

– pmFlexMacTimeDlSamp

Note:
– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

4.8 Compensated average DL MAC DRB Latency per QCI

Average Compensated DL latency measurement per burst for a DRB with a given QCI value is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L21Q1.1

Calculate Compensated average DL MAC DRB Latency per QCI by using the following formula:

Figure 43 Compensated average DL MAC DRB Latency per QCI

The following counters are used in the formulas:

– pmMacLatTimeDlQci

– pmMacTimeDlSampQci

– pmFlexMacLatTimeDl

– pmFlexMacTimeDlSamp

Note:
– Filter parameters can be used for flexible counters. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

4.9 Average DL PDCP UE Throughput

DL PDCP throughput for the UE is given by the following equation. The PM counters in this KPI are on cell level..

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP UE Throughput by using the following formula:

Figure 44 Average DL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThpTimeDl

– pmPdcpVolDlDrb

– pmPdcpVolDlDrbLastTTI

Note:
– For cases where pmUeThpTimeDl is small and/or where pmPdcpVolDlDrb is similar magnitude to pmPdcpVolDlDrbLastTtiExceptQci1 (causing a small numerator from two large values), caution need to be used in using the metric as the result can be ill-conditioned.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– This KPI can be compensated by using flexible counters, see Compensated average DL PDCP UE Throughput definition. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

4.10 Compensated Average DL PDCP UE Throughput

DL PDCP throughput for the UE is given by the following equation. The PM counters in this KPI are on cell level and can be differentiated also per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average DL PDCP UE Throughput by using the following formula:

The results of the following subformulas are used in the calculation of Compensated Average DL PDCP UE Throughput:

Figure 45 Compensated Average DL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThpTimeDl

– pmFlexPdcpVolDlDrbLastTTI

– pmPdcpVolDlDrb

– pmPdcpVolDlDrbLastTTI

– pmFlexPdcpVolDlDrb

– pmFlexUeThpTimeDl

Note:
– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

4.11 Total DL PDCP UE Throughput

Total DL PDCP UE throughput is given by following equation which includes the lastTTI, buffer waiting times and volume and transfer times for the last transport blocks in all data bursts and possible HARQ retransmission delays.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L21Q1.1

Calculate Total DL PDCP UE Throughput by using the following formula:

about:blank 14/26
12/30/22, 4:18 PM Key Performance Indicators

The results of the following subformulas are used in the calculation of Total DL PDCP UE Throughput:

Figure 46 Total DL PDCP UE Throughput

The following counters are used in the formulas:

– pmPdcpVolDlDrb

– pmMacUeThpTimeDl

Note:
– pmMacUeThpTimeDl is not included in any predefined scanner

4.12 Average DL PDCP Cell Throughput

These KPIs measure the impact on the end user. DL PDCP throughput for a cell is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP Cell Throughput by using the following formula:

Figure 47 Average DL PDCP Cell Throughput

The following counters are used in the formulas:

– pmSchedActivityCellDl

– pmPdcpVolDlDrb

Note:
– Cell active time PM counter pmSchedActivityCellDl does not include PDCP packet buffer waiting times (latency). The measurement includes the transmission time for the last transport block in each data burst.

– pmSchedActivityCellDl is not included in any predefined scanner.

– For the cells with a large amount of traffic consisting of small data bursts. Giving an example. Web, mobile apps or VoLTE, this throughput formula can not be a good measurement to evaluate performance. For such traffic PDCP packet transfer time may be dominated by buffer waiting times (latency) which is not included into this measurement.

4.13 Average DL MAC Cell Throughput

These KPIs measure the impact on the end user. DL MAC throughput for a cell is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL MAC Cell Throughput by using the following formula:

Figure 48 Average DL MAC Cell Throughput

The following counters are used in the formulas:

– pmSchedActivityCellDl

– pmRadioThpVolDl

Note:
– The volume PM counter pmRadioThpVolDl is at the MAC layer and thus if Carrier Aggregation is active, includes both PCell traffic and also the traffic carried as SCell traffic on behalf on another PCell.

– The PM counters in Equation are not included in any predefined scanner.

– Cat-M1 UE devices impact is removed from the PM counters in this KPI.

4.14 Filtered MBB UE DL PDCP Throughput

The distribution of Filtered MBB UE DL PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average DL PDCP UE Throughput .

Figure 49 Filtered DL PDCP UE Throughput Distribution

Figure 50 Filtered DL PDCP UE Throughput Distribution - deprecated

The PM counter pmUeThpDlMbbFiltered2Distr filters out throughput of devices which volume or time is below configured thresholds of the internal parameters.

The following PM Counters are to measure the number of UEs that are not included in pmUeThpDlMbbFiltered2Distr:

pmUeExclThpDlVolte Number of UE excluded from DL throughput calculation due to VoLTE traffic

pmUeExclThpDlSmallVol2 Number of MBB UE excluded from DL throughput calculation due to small volume

pmUeExclThpDlShortDrb2 Number of MBB UE excluded from DL throughput calculation due to short transport time

Filtered MBB UE DL PDCP Throughput is calculated per percentile (10%tile，20%tile，30%tile，40%tile, 50%tile), and include results of pmUeThpDlMbbFiltered2Distr and pmUeExclThpDlShortDrb2.

Figure 51 Cumulative Distribution Function

Figure 52 Cumulative Distribution Function - deprecated

Note: Throughput can be calculated for each percentile by using liner interpolate within pmUeThpDlMbbFiltered2Distr[Index], where Index is the first value for which CDF[Index] > percentile.

PM counters: pmUeThpDlMbbFiltered2Distr, pmUeExclThpDlShortDrb2

4.15 DL PDCP UE Throughput Distribution

The distribution of UE DL PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average DL PDCP UE Throughput.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate DL PDCP UE Throughput Distribution by using the following formula:

Figure 53 DL PDCP UE Throughput Distribution

The following counters are used in the formulas:

– pmUeThp2DlDistr

4.16 Average DL PDCP UE DRB Throughput per QCI

DL PDCP UE Throughput for both AM and UM for end-user services (defined by QCI) is given by the following equation. The PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP UE DRB Throughput per QCI by using the following formula:

Figure 54 Average DL PDCP UE DRB Throughput per QCI

The following counters are used in the formulas:

– pmDrbThpTimeDlQci

– pmPdcpVolDlDrbLastTTIQci

– pmPdcpVolDlDrbQci

Note:
– For QCI where all bearers have only ROHC traffic the KPI will show zero. This is to filter out VoLTE which volume is measured differently, see. pmUeExclThpDlVolte.

– For cases where pmDrbThpTimeDlQci is small and / or where pmPdcpVolDlDrbQci is similar magnitude to pmPdcpVolDlDrbLastTtiQci (causing a small numerator from two large values), caution is to be used in using the "average" metric as the result may be ill-conditioned.

– The PM counters in the Equation are not included in any predefined scanner.

– This KPI can be compensated by using flexible counters. Filter parameters can be used for PM counter pmFlexDrbThpTimeDl_Filter. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

about:blank 15/26
12/30/22, 4:18 PM Key Performance Indicators

4.17 DL PDCP UE Throughput Distribution for MBB UE

The mean distribution of UE DL PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average DL PDCP UE Throughput. The PM counter filters out throughput of
devices which value or time is below configured thresholds of the respective attributes. filterUeDlThpVolThr and filterUeDlThpTimeThr.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate DL PDCP UE Throughput Distribution for MBB UE by using the following formula:

Figure 55 DL PDCP UE Throughput Distribution for MBB UE

The following counters are used in the formulas:

– pmUeThpDlMbbFilteredDistr

4.18 Mean DL PDCP UE Throughput

The distribution of UE DL PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average DL PDCP UE Throughput. From the pmUeThp2DlDistr PM counter, a mean
UE PDCP throughput (on a per-session basis) can be calculated. The value for MeanBinValue[i] = 0.5 x ( Bin_Upperbound[i] + Bin_LowerBound[i] ). Since the last bin has no static Bin_Upperbound[i] defined, a default of 1500000 is recommended for that (and is default used by reports in OSS, where this default can be adjusted if desired). This value is generally different
from the legacy equation in Average DL PDCP UE Throughput as in this case each session has an equal weight in the averaging. Both are correct, but from different viewpoints.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Mean DL PDCP UE Throughput by using the following formula:

Figure 56 Mean DL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThp2DlDistr

4.19 Mean DL PDCP UE Throughput for MBB UE

The mean distribution of UE DL PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average DL PDCP UE Throughput.

The PM counter pmUeThpDlMbbFilteredDistr filters out throughput of devices which value or time is below configured thresholds of the respective attributes. filterUeDlThpVolThr and filterUeDlThpTimeThr.

The value for MeanBinValue[i] = 0.5 x ( Bin_Upperbound[i] + Bin_LowerBound[i] ). Since the last bin has no static Bin_Upperbound[i] defined, a default of 1000000 is recommended for that (and is default used by reports in OSS, where this default can be adjusted if desired).

This value is generally different from the legacy equation in Average DL PDCP UE Throughput as in this case each session has an equal weight in the averaging. Both are correct, but from different viewpoints.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Mean DL PDCP UE Throughput for MBB UE by using the following formula:

Figure 57 Mean DL PDCP UE Throughput for MBB UE

The following counters are used in the formulas:

– pmUeThpDlMbbFilteredDistr

Note:
– The PM counters are not included in any predefined scanner.

– The following PM Counters are to measure throughput of UEs that were not included in this formula.

– Number of UE excluded from DL throughput calculation due to VoLTE traffic. pmUeExclThpDlVolte.

– Number of UE excluded from DL throughput calculation due to VoLTE traffic but with simultaneous sizable MBB traffic. pmUeExclThpDlVolteMbb.

– Number of MBB UE excluded from DL throughput calculation due to small volume. pmUeExclThpDlSmallVol.

– Number of MBB UE excluded from DL throughput calculation due to short transport time. pmUeExclThpDlShortDrb.

4.20 Average DL PDCP UE Throughput for Carrier Aggregation

For traffic which is using carrier aggregation, different PM counters are provided and can be used for that traffic based on the legacy equation in Average DL PDCP UE Throughput

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL PDCP UE Throughput for Carrier Aggregation by using the following formula:

Figure 58 Average DL PDCP UE Throughput for Carrier Aggregation

The following counters are used in the formulas:

– pmPdcpVolDlDrbCa

– pmPdcpVolDlDrbLastTTICa

– pmUeThpTimeDlCa

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The carrier aggregation configured status per UE is only updated once per second, so for the updating in the pmxxxCa PM counters, there may be a slight inaccuracy for UE CA status changes within a second. Although a UE is configured for carrier aggregation, there is no guarantee that carrier aggregation is actually being used for that UE in that second.

4.21 Compensated Average DL PDCP UE Throughput for Carrier Aggregation

For traffic which is using carrier aggregation, different PM counters are provided and can be used for that traffic based on the legacy equation in Average DL PDCP UE Throughput.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average DL PDCP UE Throughput for Carrier Aggregation by using the following formula:

The results of the following subformulas are used in the calculation of Compensated Average DL PDCP UE Throughput for Carrier Aggregation:

Figure 59 Compensated Average DL PDCP UE Throughput for Carrier Aggregation

The following counters are used in the formulas:

– pmPdcpVolDlDrbLastTTICa

– pmPdcpVolDlDrbCa

– pmUeThpTimeDlCa

– pmFlexPdcpVolDlDrbLastTTIUeCa

– pmFlexPdcpVolDlDrbCa

– pmFlexUeThpTimeDlCa

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The carrier aggregation configured status per UE is only updated once per second, so for the updating in the pmxxxCa PM counters, there may be a slight inaccuracy for UE CA status changes within a second. Although a UE is configured for carrier aggregation, there is no guarantee that carrier aggregation is actually being used for that UE in that second.

– These KPIs are differentiated using flexible counters. See Detailed separation of Observability in LTE RAN for more information.

4.22 Filtered MBB UE UL Throughput

Filtered MBB UE UL Throughput is calculated per percentile (10%tile，20%tile，30%tile，40%tile, 50%tile), and include results of pmMacUeThpUlMbbLowVolDistr, pmUeExclThpUlShortTimeLowVol, pmUeExclThpUlRelativeLowVol or pmMacUeThpUlMbbHighVolDistr, pmUeExclThpUlShortTimeHighVol, pmUeExclThpUlRelativeHighVol.

Figure 60 Cumulative Distribution Function for filtered MBB UE UL Throughput with Lower Volumes

Figure 61 UeExclThpUlLow

Figure 62 Cumulative Distribution Function for filtered MBB UE UL Throughput with Higher Volumes

about:blank 16/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 63 UeExclThpUlHigh

Note: Throughput can be calculated for each percentile by using liner interpolate within pmMacUeThpUlMbbLowVolDistr[Index] or pmMacUeThpUlMbbHighVolDistr[Index], where Index is the first value that satisfy CDF[Index] > percentile.

PM counters: pmMacUeThpUlMbbLowVolDistr, pmUeExclThpUlShortTimeLowVol, pmUeExclThpUlRelativeLowVol, pmMacUeThpUlMbbHighVolDistr, pmUeExclThpUlShortTimeHighVol, pmUeExclThpUlRelativeHighVol

4.23 Average UL PDCP UE Throughput

UL PDCP throughput for the UE is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL PDCP UE Throughput by using the following formula:

Figure 64 Average UL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThpVolUl

– pmUeThpTimeUl

Note:
– For cases where pmUeThpTimeUl is small and / or where pmUeThpVolUl is small, caution is to be used in using the metric as the result may be ill-conditioned.

– For traffic, which uses small SDU (for example, VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in the "LastTti" leaving minimal net volume if any, on the numerator.

– If UL Carrier Aggregation is active this KPI is expected to increase. The PM counters pmUeThpVolUl and pmUeThpTimeUl include cell level data regardless of whether the scheduled data relates to traffic carried on this PCell or received from an SCell. It does not show any traffic received for another PCell, which this cell supports as an SCell.

– This KPI can be compensated by using flexible counters, see Compensated average UL PDCP UE Throughput. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact can be compensated for in this KPI by using flexible counters, see Compensated average UL PDCP UE Throughput definition for an example on how to use flexible counters.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.24 Compensated Average UL PDCP UE Throughput

UL PDCP throughput for the UE is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average UL PDCP UE Throughput by using the following formula:

Figure 65 Compensated Average UL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThpVolUl

– pmUeThpTimeUl

– pmFlexUeThpVolUl

– pmFlexUeThpTimeUl

Note:
– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

4.25 Average UL PDCP Cell Throughput

UL PDCP throughput for a cell is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL PDCP Cell Throughput by using the following formula:

Figure 66 Average UL PDCP Cell Throughput

The following counters are used in the formulas:

– pmPdcpVolUlDrb

– pmSchedActivityCellUl

Note:
– pmSchedActivityCellUl is not included in any predefined scanner.

– The volume PM counter pmPdcpVolUlDrb is measured after any ROHC decompression (for applicable traffic streams).

– If UL Carrier Aggregation is active, the PM counters pmPdcpVolUlDrb and pmSchedActivityCellUl include cell level data regardless of whether the scheduled data relates to traffic carried on this PCell or received from an SCell. It does NOT show any traffic received for another PCell, which this cell supports as an SCell.

– Cat-M1 UE devices impact can be compensated for in this KPI by using flexible counters on pmPdcpVolUlDrb. Filter parameters can be used for counter pmFlexPdcpVolUlDrb. See Detailed separation of Observability in LTE RAN for more information and an example on how to use flexible counters. Cat-M1 UEs are not included into the counter
pmSchedActivityCellUl. These flexible counters are not included in any predefined scanner.

4.26 Average UL MAC Cell Throughput

UL MAC throughput for a cell is given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL MAC Cell Throughput by using the following formula:

Figure 67 Average UL MAC Cell Throughput

The following counters are used in the formulas:

– pmSchedActivityCellUl

– pmRadioThpVolUl

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The volume PM counter pmRadioThpVolUl is at the MAC layer and thus if UL Carrier Aggregation is active, includes both PCell traffic and also the traffic carried as SCell traffic on behalf on another PCell.

– Cat-M1 UE devices impact is removed from the PM counters in this KPI.

4.27 Normalized Average UL MAC Cell Throughput Considering Successful PUSCH subframe Only
Normalized average UL MAC throughput for a cell, based on successfully received SDU on PUSCH. Given by the following equation.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Normalized Average UL MAC Cell Throughput Considering Successful PUSCH subframe Only by using the following formula:

Figure 68 Normalized Average UL MAC Cell Throughput Considering Successful PUSCH subframe Only

The following counters are used in the formulas:

– pmMacVolUl

– pmPuschSchedActivity

Note:
– The PM counters in the equation are not included in any predefined scanner.

– The pmMacVolUl counter is at the MAC layer. If Uplink Carrier Aggregation is active, the counters include volume transmitted on this cell regardless of whether it is used as PCell or SCell and the same for time in pmPuschSchedActivity.

– This KPI is only showing non-Category M traffic.This KPI is recommended when using ESS.

4.28 Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only
This KPI is deprecated and replaced by "Normalized Average UL MAC Cell Throughput Considering Successful PUSCH subframe Only".

Network Function LTE

about:blank 17/26
12/30/22, 4:18 PM Key Performance Indicators

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L20Q4.1

Calculate Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only by using the following formula:

Figure 69 Normalized Average UL MAC Cell Throughput Considering Successful PUSCH Slot Only

The following counters are used in the formulas:

– pmMacVolUl

– pmPuschSchedActivity

Note:
– The PM counters in the equation are not included in any predefined scanner.

– The pmMacVolUl counter is at the MAC layer. If Uplink Carrier Aggregation is active, the counters include volume transmitted on this cell regardless of whether it is used as PCell or SCell and the same for time in pmPuschSchedActivity.

– This KPI is only used for non-Category M traffic.This KPI is recommended when using ESS.

4.29 Average UL PDCP UE Throughput for Carrier Aggregation

For traffic which is in a CA_Configured state, different PM counters are provided and can be used for that traffic based on the legacy equation in Average UL PDCP UE Throughput.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL PDCP UE Throughput for Carrier Aggregation by using the following formula:

Figure 70 Average UL PDCP UE Throughput for Carrier Aggregation

The following counters are used in the formulas:

– pmUeThpVolUlCa

– pmUeThpTimeUlCa

Note:
– This KPI can be compensated by using flexible counters, see Equation Compensated average CA UL PDCP UE Throughput. See Detailed separation of Observability in LTE RAN for more information.

4.30 Compensated Average UL PDCP UE Throughput for Carrier Aggregation

For traffic which is in a CA_Configured state, different PM counters are provided and can be used for that traffic based on the legacy equation in Average UL PDCP UE Throughput.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average UL PDCP UE Throughput for Carrier Aggregation by using the following formula:

Figure 71 Compensated Average UL PDCP UE Throughput for Carrier Aggregation

The following counters are used in the formulas:

– pmUeThpVolUlCa

– pmUeThpTimeUlCa

– pmFlexUeThpVolUlCa

– pmFlexUeThpTimeUlCa

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– The carrier aggregation configured status per UE is only updated once per second, so for the updating in the pmxxxCa counters, there may be a slight inaccuracy for UE CA status changes within a second. Although a UE is configured for carrier aggregation, there is no guarantee that carrier aggregation is actually being used for that UE in that second.

– Flexible counters can be filtered for different UE EN-DC stages. See Detailed separation of Observability in LTE RAN for more information.

4.31 Average MAC UE UL THROUGHPUT

Uplink user throughput for traffic restricted by the air interface. The KPI fulfils "Scheduled IP Throughput" in 3GPP TS 36.314.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average MAC UE UL THROUGHPUT by using the following formula:

Figure 72 Average MAC UE UL THROUGHPUT

The following counters are used in the formulas:

– pmMacVolUlResUe

– pmMacTimeUlResUe

4.32 Compensated Average MAC UE UL Throughput

Overall Uplink user Throughput's volume and time can be compensated by the impact from subset of filtered UE device Uplink Throughput's Volume and time.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated Average MAC UE UL Throughput by using the following formula:

Figure 73 Compensated Average MAC UE UL Throughput

The following counters are used in the formulas:

– pmMacVolUlResUe

– pmFlexMacVolUlResUe

– pmMacTimeUlResUe

– pmFlexMacTimeUlResUe

Note:
– Flexible counters can be filtered by filter parameters in MO PmFlexCounterFilter, Filters as below. PLMN, UE_CATEGORY, SPID, SUBSCRIBER_GROUP, ENDC, UE_POWER_CLASS.

4.33 UL PDCP UE Throughput Distribution

The distribution of UE uplink PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average UL PDCP UE Throughput.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate UL PDCP UE Throughput Distribution by using the following formula:

Figure 74 UL PDCP UE Throughput Distribution

The following counters are used in the formulas:

– pmUeThp2UlDistr

4.34 Mean UL PDCP UE Throughput

The distribution of UE uplink PDCP throughput is reported as an array PM counter. This PM counter is updated based on the UE throughput in each session as each UE session ends (or at ROP-end) and uses the underlying measurements and nominal equation (on a per-session basis) provided in Average UL PDCP UE Throughput.

From the pmUeThp2UlDistr PM counter, a mean UE PDCP throughput (on a per-session basis) can be calculated.

The value for MeanBinValue[i] = 0.5 x ( Bin_Upperbound[i] + Bin_LowerBound[i] ). Since the last bin has no static Bin_Upperbound[i] defined, a default of 200000 is recommended for that and is default used by reports in OSS, where this default can be adjusted if desired.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

about:blank 18/26
12/30/22, 4:18 PM Key Performance Indicators

Calculate Mean UL PDCP UE Throughput by using the following formula:

Figure 75 Mean UL PDCP UE Throughput

The following counters are used in the formulas:

– pmUeThp2UlDistr

Note:
– This value is in general different from the legacy equation in Average UL PDCP UE Throughput as in this case each session has an equal weight in the averaging. Both are correct, but from different viewpoints.

4.35 Average UL UE Throughput per LCG

This KPI measures the impact on the end user. For traffic which use small SDU (for example, VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be excluded from the PM counters.

For the UL, instead of measuring per QCI the measurements are Logical Channel Group (LCG) level. For and the connection between LCG and QCI, see Quality of Service. UL throughput for the UE per LCG is given by the following equation. The PM counters in this KPI are on cell level and per LCG.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL UE Throughput per LCG by using the following formula:

Figure 76 Average UL UE Throughput per LCG

The following counters are used in the formulas:

– pmLcgThpVolUlLcg

– pmLcgThpTimeUlLcg

Note:
– For cases where pmLcgThpTimeUlLcg is small and / or where pmLcgThpVolUlLcg is small, caution is to be used in using the metric as the result may be ill-conditioned.

– For traffic, which uses small SDU (for example, VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be counted in the "LastTti" leaving minimal net volume if any, on the numerator.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

– This KPI can be compensated by using flexible counters, see Equation Compensated average UL Throughput per LCG. See Detailed separation of Observability in LTE RAN for more information. These flexible counters are not included in any predefined scanner.

4.36 Compensated average UL Throughput per LCG

This KPI measures the impact on the end user. For traffic which use small SDU (for example, VoLTE), the throughput may not be a good measurement to evaluate performance, since most of the traffic may only use a single TTI and may be excluded from the PM counters.

For the UL, instead of measuring per QCI the measurements are Logical Channel Group (LCG) level. For and the connection between LCG and QCI, see Quality of Service. UL throughput for the UE per LCG is given by the following equation. The PM counters in this KPI are on cell level and per LCG.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated average UL Throughput per LCG by using the following formula:

Figure 77 Compensated average UL Throughput per LCG

The following counters are used in the formulas:

– pmLcgThpVolUlLcg

– pmLcgThpTimeUlLcg

– pmFlexLcgThpVolUl

– pmFlexLcgThpTimeUl

4.37 Average DL Packet Error Loss Rate

This KPI measures the impact on the end user.

DL packet error loss rate for the UE, from a cell perspective, is given by the following equation. The PM counters in this KPI are on several MO classes.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL Packet Error Loss Rate by using the following formula:

The results of the following subformulas are used in the calculation of Average DL Packet Error Loss Rate:

Figure 78 Average DL Packet Error Loss Rate

The following counters are used in the formulas:

– pmPdcpPktDiscDlHo

– pmPdcpPktReceivedDl

– pmPdcpPktFwdDl

– pmPdcpPktDiscDlPelr

– pmPdcpPktDiscDlPelrUu

– pmPdcpPktDiscDlEth

– pmPdcpPktDiscDlNoUeCtxt

– pmMbmsPktRecSynchPayload

– pmMbmsPktRecSynchCtrl

– pmPdcpPktDiscDlNoMbmsCtxt

Note:
– The term " A " represents packets discarded (pmPdcpPktDiscDlEth, pmPdcpPktDiscDlNoUeCtxt) which cannot be mapped to any specific cell. Therefore an estimate is used, consisting of weighting the total number of these discarded packets with the fraction of packets that went to that cell versus all packets on all cells of the RBS. Term "C" similarly removes a
fraction of the discards apportioned to eMBMS. If eMBMS is inactive, C wil be equal to 1 and pmPdcpPktDiscDlEth will not be reduced.

– Several of these PM counters are not included in any predefined scanner.

– This KPI can be compensated by using flexible counters. The filter parameters can be used for flexible counters, pmFlexPdcpPktDiscDlPelrUu_Filter, pmFlexPdcpPktDiscDlHo_Filter, pmFlexPdcpPktReceivedDl_Filter, pmFlexPdcpPktFwdDl_Filter. See Detailed separation of Observability in LTE RAN for more information and an example on how to use flexible
counters. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.38 Average DL Packet Error Loss Rate per QCI

This KPI measures the impact on the end user.

DL packet error loss rate for the UE is given by the following equation. The PM counters in this KPI are on several MO classes. It is important to aggregate them on a common basis (for example, cell level) to obtain a meaningful metric.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average DL Packet Error Loss Rate per QCI by using the following formula:

The results of the following subformulas are used in the calculation of Average DL Packet Error Loss Rate per QCI:

about:blank 19/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 79 Average DL Packet Error Loss Rate per QCI

The following counters are used in the formulas:

– pmPdcpPktTransDlQci

– pmPdcpPktDiscDlPelrQci

– pmPdcpPktDiscDlPelrUuQci

– pmPdcpPktDiscDlHoQci

– pmPdcpPktDiscDlEth

– pmPdcpPktDiscDlNoUeCtxt

– pmPdcpPktReceivedDlQci

– pmPdcpPktReceivedDl

– pmMbmsPktRecSynchPayload

– pmMbmsPktRecSynchCtrl

– pmPdcpPktDiscDlNoMbmsCtxt

Note:
– The term " B " represents packets discarded (pmPdcpPktDiscDlEth, pmPdcpPktDiscDlNoUeCtxt) which cannot be mapped to any specific cell. Therefore an estimate is used, consisting of weighting the total number of these discarded packets with the fraction of the specific QCI packets that went to that cell versus all packets on all cells of the RBS. Term " C "
similarly removes a fraction of the discards apportioned to eMBMS. If eMBMS is inactive, C wil be equal to 1 and pmPdcpPktDiscDlEth will not be reduced.

– Several of these PM counters are not included in any predefined scanner.

– PM counter pmPdcpPktDiscDlPelrUuQci is estimated from overall average HARQ failure statistics, so its value may be inappropriately assigned to specific QCI

– This KPI can be compensated by using flexible counters. Filter parameters can be used for PM counters pmFlexPdcpPktDiscDlPelr_Filter, pmFlexPdcpPktDiscDlPelrUu_Filter, pmFlexPdcpPktDiscDlHo_Filter, pmFlexPdcpPktReceivedDl_Filter. See Detailed separation of Observability in LTE RAN for more information and an example on how to use flexible
counters. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.39 Average eMBMS Packet Loss Rate

This KPI measures the impact on the end user. The eMBMS packet loss rate for the UE is given by the following equation. The PM counters in this KPI are on the MbmsService MO level.

Network Function LTE

Level ENodeBFunction

Formula Status CURRENT

Calculate Average eMBMS Packet Loss Rate by using the following formula:

The results of the following subformulas are used in the calculation of Average eMBMS Packet Loss Rate:

Figure 80 Average eMBMS Packet Loss Rate

The following counters are used in the formulas:

– pmMbmsPktRecSynchPayload

– pmMbmsPktDiscSynchPayloadMuted

– pmMbmsPktDiscSynchPayloadTooMuch

Note:
– The PM counters in the Equation are not included in any predefined scanner.

4.40 Average UL 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 PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL Packet Loss Rate by using the following formula:

Figure 81 Average UL Packet Loss Rate

The following counters are used in the formulas:

– pmPdcpPktLostUl

– pmPdcpPktReceivedUl

Note:
– This KPI can be compensated by using flexible counters. Filter parameters can be used for PM counters pmFlexPdcpPktLostUl_Filter, pmFlexPdcpPktReceivedUl. See Detailed separation of Observability in LTE RAN for more information and an example on how to use flexible counters. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.41 Average UL Packet Loss Rate per QCI

This KPI measures the impact on the end user. UL packet loss rate for the UE is given by the following equation. The PM counters in this KPI are on cell level and per QCI.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Average UL Packet Loss Rate per QCI by using the following formula:

Figure 82 Average UL Packet Loss Rate per QCI

The following counters are used in the formulas:

– pmPdcpPktLostUlQci

– pmPdcpPktReceivedUlQci

Note:
– The PM counters in the Equation are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

4.42 VoIP Cell Integrity

This KPI measures the integrity impact for VoIP in the RAN. An E-RAB is defined as VoIP based on settings of the QciProfilePredefined / QciProfileOperatorDefined MO attribute ServiceType. Simulations have shown that the UL is usually the limiting factor. VoIP integrity is a measurement that shows how many % of the VoIP users that have 99% of their UL packets within
the packet delay budget. The satisfaction rate for the UE is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate VoIP Cell Integrity by using the following formula:

Figure 83 VoIP Cell Integrity

The following counters are used in the formulas:

– pmVoipQualityRbUlOk

– pmVoipQualityRbUlNok

Note:
– This KPI can be compensated by using flexible counters. See Detailed separation of Observability in LTE RAN for more information and an example on how to use flexible counters.

– The PM counters in the Equation are not included in any predefined scanner.

4.43 Compensated VoIP Cell integrity

This KPI measures the integrity impact for VoIP in the RAN. An E-RAB is defined as VoIP based on settings of the QciProfilePredefined / QciProfileOperatorDefined MO attribute ServiceType. Simulations have shown that the UL is usually the limiting factor. VoIP integrity is a measurement that shows how many % of the VoIP users that have 99% of their UL packets within
the packet delay budget. The satisfaction rate for the UE is given by the following equation. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Compensated VoIP Cell integrity by using the following formula:

The results of the following subformulas are used in the calculation of Compensated VoIP Cell integrity:

about:blank 20/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 84 Compensated VoIP Cell integrity

The following counters are used in the formulas:

– pmVoipQualityRbUlOk

– pmVoipQualityRbUlNok

– pmFlexVoipQualityRbUlOk

– pmFlexVoipQualityRbUlNok

Note:
– The PM counters in the Equation are not included in any predefined scanner.

4.44 GTP-U Downlink Packet Loss Rate

This KPI measures the network performance. PM counters in this KPI are on QCI level.

GTP-U Downlink Packet Loss Rate shows percentage of lost GTP-U user packets in downlink per QCI.

Network Function LTE

Level TermPointToSGW

Formula Status CURRENT

Calculate GTP-U Downlink Packet Loss Rate by using the following formula:

Figure 85 GTP-U Downlink Packet Loss Rate

The following counters are used in the formulas:

– pmS1uPktLostDlQci

– pmS1uPktRecQci

Note:
– For cases where sequence number in received GTP-U packets on S1-U is not present the metric as the result may be ill-conditioned.

4.45 GTP-U Downlink Packet Out of Order Rate

This KPI measures the network performance. PM counters in this KPI are on QCI level.

GTP-U Downlink Packet Out Of Order Rate shows percentage of GTP-U user packets received out of order in downlink per QCI.

Network Function LTE

Level TermPointToSGW

Formula Status CURRENT

Calculate GTP-U Downlink Packet Out of Order Rate by using the following formula:

Figure 86 GTP-U Downlink Packet Out of Order Rate

The following counters are used in the formulas:

– pmS1uPktRecOooQci

– pmS1uPktRecQci

Note:
– For cases where sequence number in received GTP-U packets on S1-U is not present the metric as the result may be ill-conditioned.

4.46 DL Scheduled Entities per TTI

The following KPIs are to measure scheduled entities per TTI in Downlink. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L22Q2.2

Calculate DL Scheduled Entities per TTI by using the following formula:

Figure 87 DL Scheduled Entities per TTI

The following counters are used in the formulas:

– pmSchedActivityUeDl

– pmSchedTtiCellDl

Note:
– These PM Counters are not included in any predefined scanner.

– This KPI is deprecated and replaced by RI "DL Scheduled Entities per TTI", see CPI "License and Resource Use Indicators".

4.47 UL Scheduled Entities per TTI

The following KPIs are to measure scheduled entities per TTI in Uplink. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status DEPRECATED

Deprecated Since L22Q2.2

Calculate UL Scheduled Entities per TTI by using the following formula:

Figure 88 UL Scheduled Entities per TTI

The following counters are used in the formulas:

– pmSchedActivityUeUl

– pmSchedTtiCellUl

Note:
– These PM Counters are not included in any predefined scanner.

– This KPI is deprecated and replaced by RI "DL Scheduled Entities per TTI", see CPI "License and Resource Use Indicators".

about:blank 21/26
12/30/22, 4:18 PM Key Performance Indicators

5 Mobility
5.1 Mobility Success Rate
This KPI measures system performance. Mobility Success rate includes both preparation of target cell resources and move from the source cell to the target cell, as given in the following equation. PM counters in this KPI are on the MO EUtranCellRelation or UtranCellRelation or GeranCellRelation or GutranCellRelation or Cdma2001xRttCellRelation level and must be
aggregated over the various cell pairings for each type of handover.

Network Function LTE

Level EUtranCellRelation

Formula Status CURRENT

Calculate Mobility Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Mobility Success Rate:

Figure 89 Mobility Success Rate

The following counters are used in the formulas:

– pmHoPrepSuccLteIntraF

– pmHoPrepSuccLteInterF

– pmHoPrepSucc

– pmHoPrepSucc1xRttSrvcc

– pmHoPrepSuccNonMob

– pmHoPrepAttLteIntraF

– pmHoPrepAttLteInterF

– pmHoPrepAtt

– pmHoPrepAtt1xRttSrvcc

– pmHoPrepAttNonMob

– pmHoPrepRejOutUlThres

– pmHoExeSuccLteIntraF

– pmHoExeSuccLteInterF

– pmHoExeSucc

– pmHoExeSuccNonMob

– pmHoExeAttLteIntraF

– pmHoExeAttLteInterF

– pmHoExeAtt

– pmHoExeAttNonMob

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– Some of the features (for example features related to load balancing and eMBMS) can trigger handover without any mobility. So PM counters with "NonMob" suffix (pmHoPrepSuccNonMob, pmHoPrepAttNonMob, pmHoExeSuccNonMob, and pmHoExeAttNonMob) remove handovers that are triggered with those non-mobility factors rather than mobility.

– The PM counters pmHoPrepSucc, pmHoPrepAtt1xRttSrvcc, pmHoPrepAtt, pmHoExeSucc, pmHoPrepSucc1xRttSrvcc & pmHoExeAtt refer to handovers to non-LTE systems and are not parents of the corresponding LTE handover counters. PM counters in the equations exist in class UtranCellRelation for WCDMA and TDScdma handovers, in class
GeranCellRelation for GERAN SRVCC handovers (see the SRVCC Handover to GERAN feature), in class GutranCellRelation for NR SA IRAT handover (see the Outgoing NR IRAT Handover feature) and in class Cdma20001xRttCellRelation for SRVCC handover to CDMA 1xRtt (see the SRVCC Handover to CDMA 1X feature).

– Several of these PM counters are not included in any predefined scanner.

5.2 Cell Mobility Success Rate

This KPI measures system performance. Rarely used cell relations are not populated within EUtranCellRelation MO if AnrFunction.cellRelHoAttRateThreshold attribute is greater than 0. Those new relations do not appear in the preceding mobility equation until the handover attempt usage exceeds the new attribute value. PM counters based on EUtranCellFDD or
EUtranCellTDD are cell-based. These new PM counters are pegged whether the CellRelation has been created or not. If AnrFunction.cellRelHoAttRateThreshold is 0 then the new PM counters and the cell-aggregated CellRelation counters are equivalent. These PM counters permit the following Cell Mobility KPI metric.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Cell Mobility Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Cell Mobility Success Rate:

Figure 90 Cell Mobility Success Rate

The following counters are used in the formulas:

– pmCellHoPrepSuccLteIntraF

– pmCellHoPrepSuccLteInterF

– pmHoPrepSucc

– pmHoPrepSucc1xRttSrvcc

– pmHoPrepSuccNonMob

– pmCellHoPrepAttLteIntraF

– pmCellHoPrepAttLteInterF

– pmHoPrepAtt

– pmHoPrepAtt1xRttSrvcc

– pmHoPrepAttNonMob

– pmHoPrepRejOutUlThres

– pmCellHoExeSuccLteIntraF

– pmCellHoExeSuccLteInterF

– pmHoExeSucc

– pmHoExeSuccNonMob

– pmCellHoExeAttLteIntraF

– pmCellHoExeAttLteInterF

– pmHoExeAtt

– pmHoExeAttNonMob

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– Some features can trigger handover without any mobility, for example, features related to load balancing and eMBMS. So, the following PM counters with NonMob suffix remove handovers that are triggered with those non-mobility factors rather than mobility: - pmHoPrepSuccNonMob - pmHoPrepAttNonMob - pmHoExeSuccNonMob - pmHoExeAttNonMob

– The following PM counters refer to handovers to non-LTE systems and are not parents of the corresponding LTE handover counters. - pmHoPrepSucc - pmHoPrepAtt1xRttSrvcc - pmHoPrepAtt - pmHoExeSucc - pmHoPrepSucc1xRttSrvcc - pmHoExeAtt PM counters in the equations exist in the following MO classes. - In the UtranCellRelation MO for WCDMA
and TDScdma handovers. - In the GeranCellRelation MO for GERAN SRVCC handovers. For more information, see the SRVCC Handover to GERAN feature. - In the GutranCellRelation MO for NR SA IRAT handover. For more information, see the Outgoing NR IRAT Handover feature. - In the Cdma20001xRttCellRelation MO for SRVCC handover to CDMA 1xRtt.
For more information, see the SRVCC Handover to CDMA 1X feature.

– Several of these PM counters are not included in any predefined scanner.

– The Lb, GERAN, UTRAN, GUTRAN and 1xRTT PM counters must be aggregated to the cell level for these Cell Mobility equations.

– This KPI can be compensated with the use of flexible counters. See Detailed Separation of Observability in LTE RAN with Flexible Counters for more information and an example of how to use flexible counters. These flexible counters are not included in any predefined scanner

5.3 Flexible Intra-Frequency Cell Mobility Success Rate

This KPI measures system performance. This KPI is a flexible mobility measurement, when used with Cat-M1 filter it is dedicated for Cat-M1 devices. The pmCounters are on cell level. These PM counters permit the following Cell Mobility KPI metric.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Flexible Intra-Frequency Cell Mobility Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Flexible Intra-Frequency Cell Mobility Success Rate:

about:blank 22/26
12/30/22, 4:18 PM Key Performance Indicators

Figure 91 Flexible Intra-Frequency Cell Mobility Success Rate

The following counters are used in the formulas:

– pmFlexCellHoPrepSuccLteIntraF

– pmFlexCellHoPrepAttLteIntraF

– pmFlexCellHoExeSuccLteIntraF

– pmFlexCellHoExeAttLteIntraF

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– This KPI is differentiated with use of flexible counters. See Detailed separation of Observability in LTE RAN for related for more information. For example how to use flexible counters see Detailed separation of Observability in LTE RAN. These flexible counters are not included in any predefined scanner.

– Cat-M1 UE devices impact in this KPI can be compensated and the corresponding Cat-M1 only KPI is also available. See Detailed separation of Observability in LTE RAN for related references to the Feature Description of Category M Access.

5.4 Handover Success Rate

This KPI measures system performance. The Handover Success rate includes both mobility-triggered handovers and handovers that are not triggered with mobility (for example for load balancing). The KPI covers both preparation of target cell resources and move from the source cell to the target cell, as given in the following equation. PM counters in this KPI are on the MO
EUtranCellRelation or UtranCellRelation or GeranCellRelation or GutranCellRelation or Cdma2001xRttCellRelation level and must be aggregated over the various cell pairings for each type of handover.

Network Function LTE

Level EUtranCellRelation

Formula Status CURRENT

Calculate Handover Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Handover Success Rate:

Figure 92 Handover Success Rate

The following counters are used in the formulas:

– pmHoPrepSuccLteIntraF

– pmHoPrepSuccLteInterF

– pmHoPrepSucc

– pmHoPrepSucc1xRttSrvcc

– pmHoPrepAttLteIntraF

– pmHoPrepAttLteInterF

– pmHoPrepAtt

– pmHoPrepAtt1xRttSrvcc

– pmHoPrepRejOutUlThres

– pmHoExeSuccLteIntraF

– pmHoExeSuccLteInterF

– pmHoExeSucc

– pmHoExeAttLteIntraF

– pmHoExeAttLteInterF

– pmHoExeAtt

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– The PM counters pmHoPrepSucc, pmHoPrepAtt1xRttSrvcc, pmHoPrepAtt, pmHoExeSucc, pmHoPrepSucc1xRttSrvcc & pmHoExeAtt refer to handovers to non-LTE systems and are not parents of the corresponding LTE handover counters. PM counters in the equation exist in class UtranCellRelation for WCDMA and TDScdma handovers, in class
GeranCellRelation for GERAN SRVCC handovers (see the SRVCC Handover to GERAN feature), in class GutranCellRelation for NR SA IRAT handover (see the Outgoing NR IRAT Handover feature) and in class Cdma20001xRttCellRelation for SRVCC handover to CDMA 1xRtt (see the SRVCC Handover to CDMA 1X feature).

– Several flexible counters are available to compensate this KPI. See Detailed Separation of Observability in LTE RAN for more information.

– Several of these PM counters are not included in any predefined scanner.

5.5 Handover Execution Success Rate

This KPI measures system performance. The Handover Execution Success rate includes both mobility-triggered handovers and handovers that are not triggered with mobility (for example for load balancing). The KPI covers only the move from the source cell to the target cell, as given in the following equation. PM counters in this KPI are on the MO EUtranCellRelation or
UtranCellRelation or GeranCellRelation or GutranCellRelation or Cdma2001xRttCellRelation level and must be aggregated over the various cell pairings for each type of handover.

Network Function LTE

Level EUtranCellRelation

Formula Status CURRENT

Calculate Handover Execution Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Handover Execution Success Rate:

Figure 93 Handover Execution Success Rate

The following counters are used in the formulas:

– pmHoExeSuccLteIntraF

– pmHoExeSuccLteInterF

– pmHoExeSucc

– pmHoExeAttLteIntraF

– pmHoExeAttLteInterF

– pmHoExeAtt

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– Some features can trigger handover without any mobility, for example, features related to load balancing and eMBMS.

– The PM counters pmHoExeSucc and pmHoExeAtt refer to handovers to non-LTE systems and are not parents of the corresponding LTE handover counters. PM counters in the equations exist in class UtranCellRelation for WCDMA and TDScdma handovers, in class GeranCellRelation for GERAN SRVCC handovers (see the SRVCC Handover to GERAN feature), in
class GutranCellRelation for NR SA IRAT handover (see the Outgoing NR IRAT Handover feature) and in class Cdma20001xRttCellRelation for SRVCC handover to CDMA 1xRtt (see the SRVCC Handover to CDMA 1X feature).

– Several of these PM counters are not included in any predefined scanner.

5.6 Cell Handover Success Rate

This KPI measures system performance. The Handover Success rate includes both mobility-triggered handovers and handovers that are not triggered with mobility (for example for load balancing). The KPI covers both preparation of target cell resources and move from the source cell to the target cell, as given in the following equation. PM counters in this KPI are on the MO
EUtranCellRelation or UtranCellRelation or GeranCellRelation or GutranCellRelation or Cdma2001xRttCellRelation level and must be aggregated over the various cell pairings for each type of handover. Rarely used cell relations are not populated within MO EUtranCellRelation if attribute AnrFunction.nrHONeededToAddCellRelation > 0. Those new relations do not appear in
the preceding mobility equation until the handover attempt usage exceeds the new attribute value. PM counters based on EUtranCellFDD/EUtranCellTDD are cell-based. These new PM counters are pegged whether the CellRelation has been created or not. If AnrFunction.nrHONeededToAddCellRelation = 0, then the new PM counters and the cell-aggregated (CellRelation)
counters are equivalent. These PM counters permit the Cell Handover KPI metric.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Cell Handover Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Cell Handover Success Rate:

Figure 94 Cell Handover Success Rate

The following counters are used in the formulas:

– pmCellHoPrepSuccLteIntraF

about:blank 23/26
12/30/22, 4:18 PM Key Performance Indicators

– pmCellHoPrepSuccLteInterF

– pmHoPrepSucc

– pmHoPrepSucc1xRttSrvcc

– pmCellHoPrepAttLteIntraF

– pmCellHoPrepAttLteInterF

– pmHoPrepAtt

– pmHoPrepAtt1xRttSrvcc

– pmHoPrepRejOutUlThres

– pmCellHoExeSuccLteIntraF

– pmCellHoExeSuccLteInterF

– pmHoExeSucc

– pmCellHoExeAttLteIntraF

– pmCellHoExeAttLteInterF

– pmHoExeAtt

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– The Lb, GERAN, UTRAN, GUTRAN and 1xRTT PM counters must be aggregated to the cell level for these Cell Handover equations.

– Several flexible counters are available to compensate this KPI. See Detailed Separation of Observability in LTE RAN for more information.

– Several of these PM counters are not included in any predefined scanner.

5.7 Cell Handover Execution Success Rate

This KPI measures system performance. The Handover Execution Success rate includes both mobility-triggered handovers and handovers that are not triggered with mobility (for example for load balancing). The KPI covers only the move from the source cell to the target cell, as given in the following equation. PM counters in this KPI are on one of the following MO levels
and must be aggregated over the various cell pairings for each type of handover. - EUtranCellRelation - UtranCellRelation - GeranCellRelation - GutranCellRelation - Cdma2001xRttCellRelation Rarely used cell relations are not populated within EUtranCellRelation MO if the AnrFunction.nrHONeededToAddCellRelation attribute is larger than 0. Those new relations do not
appear in the preceding Handover Execution equation until the handover attempt usage exceeds the new value of the attribute. A set of PM counters based on EUtranCellFDD or EUtranCellTDD is cell-based. These new PM counters are pegged whether the CellRelation has been created or not. If AnrFunction.nrHONeededToAddCellRelation is 0, then the PM counters and the
cell-aggregated (CellRelation) counters are equivalent. These PM counters permit the following Cell Handover Execution KPI metric.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Cell Handover Execution Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Cell Handover Execution Success Rate:

Figure 95 Cell Handover Execution Success Rate

The following counters are used in the formulas:

– pmCellHoExeSuccLteIntraF

– pmCellHoExeSuccLteInterF

– pmHoExeSucc

– pmCellHoExeAttLteIntraF

– pmCellHoExeAttLteInterF

– pmHoExeAtt

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– The Lb, GERAN, UTRAN, GUTRAN and 1xRTT PM counters must be aggregated to the cell level for these Cell Handover Execution equations.

5.8 Differentiated Cell Handover Success Rate

This KPI measures system performance and Cell Handover Success Rate. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Differentiated Cell Handover Success Rate by using the following formula:

The results of the following subformulas are used in the calculation of Differentiated Cell Handover Success Rate:

Figure 96 Differentiated Cell Handover Success Rate

The following counters are used in the formulas:

– pmFlexCellHoExeAttGeran

– pmFlexCellHoExeAttLteInterF

– pmFlexCellHoExeAttLteIntraF

– pmFlexCellHoExeSuccGeran

– pmFlexCellHoExeSuccLteInterF

– pmFlexCellHoExeSuccLteIntraF

– pmFlexCellHoExeSuccNonMobIrat

– pmFlexCellHoExeSuccNonMobLte

– pmFlexCellHoPrepAtt1xRttSrvcc

– pmFlexCellHoPrepAttGeran

– pmFlexCellHoPrepAttLteInterF

– pmFlexCellHoPrepAttLteIntraF

– pmFlexCellHoPrepAttNonMobIrat

– pmFlexCellHoPrepAttNonMobLte

– pmFlexCellHoPrepSucc1xRttSrvcc

– pmFlexCellHoPrepSuccGeran

– pmFlexCellHoPrepSuccLteInterF

– pmFlexCellHoPrepSuccLteIntraF

– pmFlexCellHoPrepSuccNonMobIrat

– pmFlexCellHoPrepSuccNonMobLte

– pmFlexCellHoExeAttNonMobLte

– pmFlexCellHoExeAttNonMobIrat

– pmFlexCellHoPrepSuccUtran

– pmFlexCellHoPrepAttUtran

– pmFlexCellHoExeSuccUtran

– pmFlexCellHoExeAttUtran

– pmFlexCellHoPrepAttNr

– pmFlexCellHoPrepSuccNr

– pmFlexCellHoExeAttNr

– pmFlexCellHoExeSuccNr

Note:
– If handover for a UE fails, but is followed by a successful reestablishment, the handover is still treated as unsuccessful by this KPI.

– The Lb, GERAN, UTRAN, GUTRAN and 1xRTT PM counters must be aggregated to the cell level for these Cell Handover Execution equations.

– Filter parameters can be used for flexible counters. For more information, see the Detailed Separation of Observability in LTE RAN chapter of the Key Performance Indicators User Guide.

– These flexible counters are not included in any predefined scanner.

5.9 UTRAN SRVCC Success Rate

This KPI measures system performance, when SRVCC occurs to an UTRAN system

Network Function LTE

Level UtranCellRelation
about:blank 24/26
12/30/22, 4:18 PM Key Performance Indicators

Formula Status CURRENT

Calculate UTRAN SRVCC Success Rate by using the following formula:

Figure 97 UTRAN SRVCC Success Rate

The following counters are used in the formulas:

– pmHoPrepSuccSrvcc

– pmHoPrepAttSrvcc

– pmHoExeSuccSrvcc

– pmHoExeAttSrvcc

about:blank 25/26
12/30/22, 4:18 PM Key Performance Indicators

6 Availability
6.1 Cell Availability
This KPI measures system performance. Since the KPI is measured by the RBS, it does not include time when the RBS is down, that is, 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 'CELL' number of cells during 'ROP' reporting periods can be calculated using the
following formula. The PM counters in this KPI are on cell level.

Network Function LTE

Level EUtranCell

Formula Status CURRENT

Calculate Cell Availability by using the following formula:

Figure 98 Cell Availability

The following counters are used in the formulas:

– pmCellDowntimeAuto

– pmCellDowntimeMan

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.

– If the files with the PM counters are missing, the time that those files represent in "CELL x ROP x 900" shall be excluded from Cell Availability result.

– A cell restart because of the Advanced Cell Supervision feature increments the PM counter pmCellDowntimeMan.

– The default setting for the delay timer is 0, which does not affect the cell restart time. If the delay timer is set to be larger than 0, cell restart/unlock time duration is extended as a consequence of the number of TX updates taken place during the lock/unlock procedure.

– Downtime because of Cell Sleep mode is not impacting the user perceived availability and therefore pmCellSleepTime is not included in this KPI.

– If Clock is adjusted by more than 300 seconds in order to keep up with the time references, and the PM counters pmCellDowntimeAuto/pmCellDowntimeMan step above 1200, those PM counters are set to blank value in current ROP.

Legal | © Ericsson AB 2021

Copyright © Ericsson AB 2021. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

about:blank 26/26