Description
The Paging Transmission Window (PTW) is a fundamental concept in 3GPP's power saving mechanisms, specifically defined for eMTC (enhanced Machine-Type Communication) and NB-IoT (Narrowband IoT) devices. It operates within the broader framework of the extended Discontinuous Reception (eDRX) cycle. The core principle is to concentrate the network's paging transmissions for a specific UE into a predictable, bounded time window, rather than scattering them across the entire, potentially very long, eDRX cycle. This allows the UE to power down its radio receiver for the vast majority of the cycle, waking up only during its assigned PTW to check for incoming pages.
Architecturally, the PTW is configured by the network via Non-Access Stratum (NAS) signaling. The parameters include the PTW length and its relationship to the eDRX cycle. The UE calculates the exact timing of its PTW based on its unique identifier (like the IMSI), system information, and the configured parameters. During the PTW, the UE monitors its assigned paging occasions (POs) according to the legacy paging procedure rules, but these POs are now constrained to fall within the PTW's duration. The network, aware of the UE's PTW schedule, will only attempt to page the UE during this window.
From a procedural standpoint, when a downlink data packet or signaling message arrives for a UE in RRC_IDLE or RRC_INACTIVE state, the core network triggers a paging procedure. The Access Stratum in the RAN schedules the paging message for transmission in a specific PO. For a UE using PTW, the RAN ensures this PO is scheduled within the UE's active PTW. If the UE successfully receives a paging message addressed to it, it initiates the random access procedure to transition to RRC_CONNECTED state. If no page is received by the end of the PTW, the UE returns to a deep sleep state until the next PTW begins.
The role of PTW is critical in balancing network reachability with device power consumption. For IoT and MTC applications where devices report infrequently and must operate on batteries for years, the ability to extend sleep periods from seconds (with normal DRX) to minutes, hours, or even days (with eDRX+PTW) is transformative. It directly enables the long battery life targets of 10+ years for many massive IoT use cases. The PTW provides a deterministic 'on' window, simplifying both UE implementation and network scheduling compared to purely probabilistic long sleep schemes.
Purpose & Motivation
The PTW was introduced to address the stringent power consumption requirements of massive Machine-Type Communication (mMTC) and Internet of Things (IoT) devices defined in 3GPP Release 13 and beyond. Prior to eDRX and PTW, UEs used standard Discontinuous Reception (DRX) cycles, which were limited to a maximum of a few seconds. For sensors or meters that send data only a few times per day, waking up every few seconds to check for paging was a massive and wasteful drain on battery life, making cellular connectivity impractical for long-lived battery-operated devices.
The primary problem PTW solves is extending sleep periods while maintaining manageable latency for mobile-terminated services. Simply extending the DRX cycle without a PTW would mean the UE's paging occasions are spread thinly over a very long period. This would force the network to repeatedly send paging messages over many subframes to ensure coverage, wasting radio resources, and could complicate UE implementation. The PTW provides a concentrated 'active listening' period, making the paging process efficient for both the network and the UE.
Historically, the motivation came from industry verticals like utilities, asset tracking, and smart cities, which required cellular-grade connectivity but with battery life measured in years, not days. The PTW, combined with the eDRX cycle, became a cornerstone 3GPP solution to meet these demands, enabling LTE-M and NB-IoT to compete with non-cellular LPWAN technologies. It represents a fundamental shift from 'always-ready' connectivity to 'predictably reachable' connectivity, optimizing for energy efficiency over instantaneous response.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (34 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the PTW (Paging Transmission Window) function was enhanced to support group paging for Multicast Broadcast Service (MBS) session activation towards UEs in CM-IDLE and RRC_INACTIVE states. The AMF was specified to restrict the paging area within the MBS service area and to include UEs using power saving functions in the group paging procedure. Furthermore, the NG-RAN was enabled to indicate that MBS session data is allowed to be received directly in the RRC_INACTIVE state upon receiving such a group paging request.
- Clarification on when UL data transmission in EDT is not considered successful TS 36.300CR1201
- Paging Monitoring in Camped Normally state and Camped on Any Cell state TS 36.304CR0747
- Small correction to paging with wake up signal TS 36.304CR0741
- Correction on paging for LTE connected to 5GC TS 36.304CR0750
- CR on missing descprition of transmission pool sharing TS 36.304CR0764
- Paging Mechanisms TS 38.300CR0012
+ 9 more changes
In Release 16, the enhancements for the PTW (Paging Transmission Window) function specifically introduced support for **group paging at multicast session activation** towards UEs in RRC_INACTIVE state. Furthermore, the NG-RAN was enabled to indicate **that the MBS session data is allowed to be received in RRC_INACTIVE state** when performing this group paging. These changes were complemented by the handling of **UE Radio Capability for Paging** for UEs in this state, including for NB-IoT and eMTC.
- Clarifications on paging DRX cycle TS 36.304CR0830
- Correction on paging resource determination for eMTC UE in RRC_INACTIVE TS 36.304CR0832
- Correction on uplink transmission allowed without TA TS 38.300CR0343
- Transmissions to the source that continue upon DAPS UL switching TS 38.300CR0353
- Supporting use of UE Radio Capability for Paging in RRC_INACTIVE TS 38.300CR0380
- Handling of UE Radio Capability for Paging in NB-IoT and eMTC TS 36.300CR1263
In Release 17, the enhancements for the Paging Transmission Window (PTW) function primarily involved new paging strategy handling for multicast MBS sessions, including support for group paging at session activation for UEs in CM-IDLE and RRC_INACTIVE states. The updates also introduced corrections for coverage-based paging and paging with PEI, alongside aligning DRX for paging with RRC procedures for SDT. Furthermore, the release specified that the AMF must consider the MBS service area to restrict the paging area and may apply paging differentiation based on received ARP and 5QI.
- Paging strategy handling for multicast MBS session TS 23.247CR0085
- Correction to coverage based paging TS 36.304CR0850
- Small corrections on coverage-based paging TS 36.304CR0860
- Corrections for IIoT on simultaneous PUCCH and PUSCH transmission TS 38.300CR0477
- Correction of Paging with PEI TS 38.300CR0747
- Alignment of DRX for Paging with RRC for SDT TS 38.304CR0251
In Release 18, the PTW function was enhanced to support **Group Paging for Multicast MBS session data reception in RRC_INACTIVE state**. Specifically, when the AMF triggers a Multicast Group paging request, the NG-RAN can now indicate that the MBS session data is allowed to be received by UEs in the RRC_INACTIVE state, as detailed in the paging procedures. This extends paging strategy handling to efficiently activate multicast sessions for UEs in inactive connections.
- Group Paging for Multicast MBS session data reception in RRC_INACTIVE state TS 23.247CR0280
- Clarification on data transmission for EDT TS 36.300CR1422
- Correction of Redcap RAN Paging Request TS 38.300CR0821
- Corrections related to indicating failure of establishing MBS broadcast transmission resources TS 23.247CR0262
- Correction in TS 38.300 to support Simultaneous PUSCH and PUCCH transmissions of same priority on different inter-band cells [SimultaneousPUSCH-PUCCH] TS 38.300CR0773
In Release 19, the PTW (Paging Transmission Window) function was enhanced to address a paging loss issue and to correct UE transmission behavior during Cell DRX. The updates specifically refined the group paging procedure for multicast session activation toward UEs in CM-IDLE and RRC_INACTIVE states, ensuring reliable paging even for UEs using power saving functions. These corrections aimed to improve the reliability of paging delivery within the MBS service area during the PTW.
Explore further
Broader topics and technologies where PTW plays a role.
Defining Specifications
3GPP specifications that define or reference PTW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.247 vj30 | 5G Multicast/Broadcast Service Architecture | Rel-19 |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.304 vj00 | UE Idle Mode Procedures in E-UTRA | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.304 vj00 | UE RRC_IDLE and RRC_INACTIVE Procedures | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |
| TR 38.869 vi00 | Study on low-power wake up signal and receiver for NR | Rel-18 |