Description
The Paging Indicator (PI) is a fundamental mechanism within the 3GPP radio access network, specifically in the context of paging procedures for User Equipment (UE) in idle or inactive states. It operates as a calculated value derived from higher-layer parameters, such as the UE's International Mobile Subscriber Identity (IMSI) and system frame numbers, to determine the precise paging occasions when a UE must wake up and listen for paging messages on the Paging Channel (PCH). The PI is used to map UEs to specific Paging Indicator Channels (PICH) in UMTS or Paging Occasions (PO) and Paging Frames (PF) in LTE and NR, ensuring that paging messages are broadcast only at predetermined intervals, thereby organizing network paging traffic efficiently.
Architecturally, the PI is generated by the network's Radio Resource Control (RRC) layer or higher, based on algorithms defined in 3GPP specifications. In UMTS, the PI is associated with the PICH, a physical channel that carries paging indicators to alert UEs. The UE calculates its own PI using the same algorithm and monitors the corresponding PICH subframe. If the indicator is set, the UE then decodes the associated PCH for the actual paging message. In LTE and 5G NR, the concept evolves into Paging Occasions and Paging Frames, where the PI-like calculation determines the specific subframe and frame for paging, integrating with Discontinuous Reception (DRX) cycles to further optimize power saving.
The role of the PI is critical for mobility management and connection establishment. It allows the network to reach UEs for incoming calls, SMS, or data sessions without requiring the UE to continuously monitor channels, thus conserving battery life. The PI calculation ensures a uniform distribution of UEs across paging resources, preventing congestion and enabling scalable paging in large networks. Its implementation is standardized across releases, with enhancements in later versions to support new states like RRC_INACTIVE in 5G, where paging mechanisms are extended for efficient state transitions and network efficiency.
Purpose & Motivation
The Paging Indicator was introduced to address the challenge of efficiently notifying idle UEs of incoming communications while minimizing their power consumption. In early cellular systems, UEs had to frequently listen for paging signals, leading to high battery drain. The PI mechanism, introduced in 3GPP R99, provided a structured way to determine specific paging instances, enabling UEs to sleep most of the time and wake only at calculated intervals. This solved the problem of excessive energy use in mobile devices, which was a key limitation in prior approaches like constant monitoring or simple periodic paging.
Historically, as networks evolved from 2G to 3G with UMTS, the need for more sophisticated paging grew due to increased user density and data services. The PI allowed for deterministic paging occasions based on UE identity, reducing collision risks and improving network capacity. It also facilitated the implementation of Discontinuous Reception (DRX), a power-saving feature that relies on precise paging timing. Without the PI, networks would struggle with inefficient signaling, higher latency in reaching UEs, and reduced battery life, impacting user experience and network scalability in the era of mobile broadband and IoT deployments.
In later releases, the PI concept underpinned enhancements for LTE and 5G NR, where paging efficiency became even more critical with massive IoT and low-power devices. It addressed limitations of earlier paging methods by providing a standardized, scalable solution that integrates with advanced RRC states and network slicing, ensuring backward compatibility and forward flexibility for evolving telecommunications standards.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (13 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, no new technical details for the Paging Indicator (PI) function are introduced in the provided grounding context. The context describes existing paging concepts like the paging DRX cycle, paging occasion, and initial paging information, but does not specify any changes or additions specific to Release 15. The associated Change Request title also pertains to interworking for a different parameter and does not relate to the PI function.
- Correction of the Backward call indicators parameter interworking TS 29.163CR1031
In Release 16, the paging (PI) function was enhanced by introducing new measurement capabilities. Specifically, the release added the ability to perform "measurement of paging" to monitor and assess paging performance. This provided a clearer view of the performance indicators related to the paging process.
In Release 17, the enhancements to the Paging Indicator (PI) function focused on improving measurement accuracy and completeness. Specifically, corrections were made to paging measurements, and missing procedures for paging discard measurements were added. These updates ensure more reliable monitoring during the paging occasion within the UE's paging DRX cycle.
In Release 18, the paging indicator (PI) function was enhanced through new network management capabilities. Specifically, the release introduced standardized measurements for NG-RAN Initiated paging sent by the gNB-CU, allowing for improved monitoring and optimization of the paging procedure. This provides operators with greater visibility into the performance of the core paging mechanism where the network seeks a User Equipment.
In Release 19, the paging indicator (PI) function was enhanced primarily in the network management domain with new performance monitoring capabilities. Specifically, the release introduced new measurements to monitor paging load in Non-Terrestrial Network deployments and added multicast group paging records for Multimedia Broadcast Service (MBS) measurements. These updates, along with a correction on paging record measurement, expanded the operational visibility for paging in new network topologies and services.
- Rel-19 CR TS 28.552 New measurements to monitor Paging Load in Non-Terrestrial Network deployments TS 28.552CR0585
- Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement TS 28.552CR0690
- Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement TS 28.552CR0722
- Rel-19 CR 28.552 Introduce missing definition of term “Key Performance Indicator (KPI)” TS 28.552CR0673
- Rel-19 CR TS 28.552 correction on paging record measurement TS 28.552CR0698
Explore further
Broader topics and technologies where PI plays a role.
Defining Specifications
3GPP specifications that define or reference PI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.333 vj00 | MRFC-MRFP Mp Interface Requirements | Rel-19 |
| TS 23.334 vj00 | IMS-ALG to IMS-AGW Interface (Iq) Stage 2 | Rel-19 |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 |
| TS 25.202 vj00 | 7.68Mcps TDD Option Technical Specification | Rel-19 |
| TS 25.211 vj00 | UTRA FDD Layer 1: Transport & Physical Channels | Rel-19 |
| TS 25.214 vj00 | UTRA FDD Physical Layer Procedures | Rel-19 |
| TS 25.221 vj00 | UTRA TDD Physical Layer Specification | Rel-19 |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 |
| TS 25.304 vj00 | UTRA Idle Mode Procedures Specification | Rel-19 |
| TS 25.367 vj00 | Home NodeB Mobility Procedures | Rel-19 |
| TS 25.705 vd00 | UMTS Small Data Transmission Enhancements Study | Rel-13 |
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TS 26.253 vj00 | IVAS Codec Algorithmic Description | Rel-19 |
| TS 28.552 vk10 | 5G Performance Management Measurements | Rel-20 |
| TR 28.832 vi01 | Technical Report on URLLC Management | Rel-18 |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 |
| TS 33.831 vc00 | Study on Spoofed Call Detection & Prevention | Rel-12 |
| TS 37.462 vj00 | Iuant Interface Data Link Layer for RETAP/TMAAP | Rel-19 |