KPI

Key Performance Indicators

Management →
Introduced in Rel-8 Also in: Management, Radio Access Network

KPI is a set of quantifiable metrics used to evaluate the performance, health, and quality of a mobile network and its services for planning, optimization, and ensuring service quality.

Category
Management
Introduced
Rel-8
Where
Services › Codecs
Also touches
2 segments
Specifications
36 specs
KPI Description Purpose Related Classification Detected Changes Specifications

Description

Key Performance Indicators (KPIs) in 3GPP are standardized, measurable values that demonstrate how effectively a network, network slice, or service is achieving key operational and business objectives. They are derived from measurements collected by various network elements (NEs), management systems, and probes. The architecture for KPI management involves a hierarchical data collection and processing chain: Performance Measurement (PM) data is generated by NEs (e.g., gNB, AMF, UPF) as raw counters, events, and gauges. This data is then collected by Network Management (NM) or Element Management (EM) systems via standardized interfaces (e.g., Itf-N). The management systems then apply defined formulas—often specified in 3GPP documents—to aggregate and compute the KPIs from the raw PM data.

How KPIs work is a continuous cycle of measurement, collection, computation, and analysis. For example, a fundamental Radio Access Network (RAN) KPI like the LTE Radio Resource Control (RRC) Setup Success Rate is computed by an EM system. It collects the raw counter "AttConnEstabAtt" (number of RRC connection establishment attempts) and "AttConnEstabSucc" (number of successful attempts) from the eNodeB over a defined measurement period (e.g., 15 minutes). The KPI is then calculated as (Successful Attempts / Total Attempts) * 100%. This computed KPI value is then stored, visualized, and compared against target thresholds to assess performance. KPIs span all network domains: Accessibility (e.g., call setup success rate), Retainability (e.g., drop call rate), Integrity (e.g., throughput, latency), Availability (e.g., node uptime), and Mobility (e.g., handover success rate).

Key components in the KPI ecosystem include the Performance Measurement Jobs configured in network elements, the Management Data Analytics (MDA) functions that can process KPIs for automation, and the standardized definitions and formulas provided in 3GPP Technical Specifications (TS) and Technical Reports (TR). Their role is multifaceted: for engineers, they are diagnostic tools for root cause analysis; for planners, they guide capacity expansion; for operators, they ensure Service Level Agreement (SLA) compliance, especially for network slicing where slice-specific KPIs are crucial. The description and calculation methods for hundreds of KPIs are detailed across numerous 3GPP specs, including service requirements (22-series), management (28-series, 32-series), and performance aspects (38.8xx series for NR).

Purpose & Motivation

KPIs exist to provide an objective, quantitative basis for assessing network performance and service quality. The fundamental problem they solve is the need to move from subjective, anecdotal assessments of network health to data-driven decision making. In the early days of mobile networks, operators lacked standardized metrics, making benchmarking and interoperability difficult. KPIs provide a common language for defining what "good performance" means for aspects like voice call quality, data speed, and network reliability.

The creation and continuous evolution of KPIs in 3GPP are motivated by several factors: the introduction of new technologies (e.g., 5G NR, network slicing), new services (e.g., Ultra-Reliable Low Latency Communication - URLLC), and the need for automated network management. Each new release introduces capabilities that require new KPIs to measure them effectively. For instance, 5G introduced KPIs for beam management, network slice performance, and energy efficiency. They address the limitations of previous approaches by providing increasingly granular, service-aware, and real-time capable metrics. This allows operators to not only monitor the network's technical performance but also to correlate it with the end-user's Quality of Experience (QoE), enabling proactive optimization and efficient resource utilization.

Classification

Part ofPM
Related approachesSONQoEMDA

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the specification introduced a formal framework for Energy Efficiency Key Performance Indicators (EE KPIs) at the network, equipment, and site levels. It defined a self-managed Energy Efficiency Control and Coordination function, which uses embedded metering to collect EE KPI statistics and execute operator-defined EE policies. Furthermore, the release streamlined KPI measurement by removing the requirement for redundant end-to-end latency KPI measurement.

  • Remove the redundant measurement of end-to-end latency KPI TS 28.552CR0002
Rel-16 1 change

In Release 16, the KPI function was enhanced to support configurable KPI control via the NRM. This introduced a self-managed and automated Energy Efficiency control process, which uses operators' defined EE KPI targets to coordinate power saving operations across the network, equipment, and site levels.

  • Add configurable KPI control NRM TS 28.622CR0069
Rel-17 2 changes

In Release 17, the KPI function was enhanced with new work on Energy Efficiency (EE) KPIs for 5G, converting a draft specification into a formal work item. The release also included an update to the requirements for Network and Customer Experience Insight Service (NCIS) KPIs, focusing on the self-managed control functions that use EE KPIs and QoS statistics to automate power-saving operations across the network.

  • CR for WI ePM_KPI_5G converted from draftCR S5-211355 TS 28.552CR0288
  • Update of NCIS KPI requirements TS 22.261CR0413
Rel-18 1 change

In Release 18, the KPI function was updated to provide a clarification for the AMMT use case within the service requirements. The release introduced more detailed considerations for calculating Energy Efficiency (EE) KPIs, specifically addressing the complexity added by spatial and temporal variations in network load. Furthermore, it defined the role of EE KPIs within automated control and coordination functions, linking them to policy management and optimization operations that monitor energy consumption against predefined thresholds.

  • Clarification of KPI in TS22.261 clause 7.10 for AMMT use case TS 22.261CR0633
Rel-19 5 changes

In Release 19, the KPI function was enhanced by formally introducing missing definitions for the terms "Key Performance Indicator (KPI)" and "performance metric" into the specifications. The release also addressed specific KPI requirements for new scenarios, including UE-to-UE relay operations and corrections for AI/ML KPIs in direct network connections. These updates provide a clearer foundational framework for defining and assessing KPIs, such as Energy Efficiency (EE) KPIs, across network, equipment, and site levels.

  • KPI Requirements for UE to UE Relay TS 22.261CR0738
  • Correction of AI/ML KPI requirements for direct network connection TS 22.261CR0761
  • Rel-19 CR 28.552 Introduce missing definition of term “Key Performance Indicator (KPI)” TS 28.552CR0673
  • Rel-19 CR 28.622 Introduce missing definition of terms “Key Performance Indicator (KPI)” and “performance metric” TS 28.622CR0535
  • Rel-19 CR 32.401 Introduce missing definition of terms “Key Performance Indicator (KPI)” and “performance metrics” TS 32.401CR0043

Explore further

Broader topics and technologies where KPI plays a role.

Defining Specifications

3GPP specifications that define or reference KPI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.866 vf00 Study on Energy Efficiency in 3GPP Standards Rel-15
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 21.915 vf00 Release 15 Description: Summary of Rel-15 Work Items Rel-15
TR 21.916 vg20 Rel-16 Description Summary Rel-16
TR 21.917 vh01 Rel-17 Work Items Summary Rel-17
TR 21.918 vi00 Release 18 Feature Summaries Rel-18
TS 22.179 vk00 MCPTT Service Requirements Rel-20
TS 22.261 vk30 5G System Service Requirements Rel-20
TS 22.830 vg10 Business Role Models for Network Slicing Rel-16
TS 23.435 vj30 Network Slice Capability Exposure Procedures Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.758 vh00 Study on Edge Application Architecture Rel-17
TS 26.179 vj00 Codecs and Media Handling for MCPTT Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TR 26.857 vi00 Technical Report on Media Service Enablers Rel-18
TR 26.909 vj00 QoE Enhancement for Streaming Services Rel-19
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19
TR 26.942 vj00 Study on Media Energy Consumption Exposure & Evaluation Rel-19
TR 26.956 vj01 Beyond 2D Video Formats & Codecs Study Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TS 28.535 vj00 Closed Control Loop Assurance Management Rel-19
TS 28.552 vk10 5G Performance Management Measurements Rel-20
TS 28.622 vk20 Telecommunication Management; Generic NRM Information Service Rel-20
TS 32.401 vj00 Performance Management Concept & Requirements Rel-19
TS 32.410 vj00 3GPP TS 32.410: Key Performance Indicators (KPI) Rel-19
TS 32.450 vj00 E-UTRAN Key Performance Indicators (KPI) Definitions Rel-19
TS 32.451 vj00 KPI Requirements for E-UTRAN Rel-19
TS 32.454 vj00 IMS Key Performance Indicators (KPIs) Rel-19
TS 32.835 vc00 HetNet Management Information Selection Rel-12
TS 32.863 vd00 PM Measurement Metadata Definition Rel-13
TR 32.972 vj00 Energy Efficiency Study for 5G Networks Rel-19
TS 38.811 vf40 Study on NR Support for Non-Terrestrial Networks Rel-15
TS 38.843 vj00 Study on AI/ML for NR Air Interface Rel-19
TR 38.859 vi10 Technical Report Rel-18
TR 38.913 vj00 Next Gen Access Tech Scenarios & Requirements Rel-19
TS 43.868 vc10 GERAN Improvements for MTC Feasibility Study Rel-12
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.