Description
Discontinuous Reception (DRX) is a fundamental power-saving technique employed in 3GPP radio access networks, including UTRAN, E-UTRAN (LTE), and NG-RAN (5G NR). The core principle allows the User Equipment (UE) to deactivate its radio receiver circuitry for predefined periods, entering a low-power 'sleep' state, and only waking up at specific intervals to check for potential downlink data scheduling assignments from the network on the Physical Downlink Control Channel (PDCCH). This cycle is governed by timers and parameters configured by the network via Radio Resource Control (RRC) signaling. The DRX operation is tightly integrated with the UE's Radio Resource Management (RRM) and mobility procedures, such as cell reselection and handover.
The architecture of DRX involves several key timers and cycles. The basic structure includes an 'On Duration' timer, during which the UE must monitor the PDCCH. If data is scheduled, the UE stays awake and starts an 'Inactivity Timer,' which resets with each new scheduling assignment. Once this timer expires, the UE enters a 'DRX cycle,' alternating between short sleep periods and brief listening periods. For more aggressive power saving, a longer 'Long DRX Cycle' can be configured. The network has precise knowledge of the UE's DRX pattern, allowing it to buffer downlink data and schedule transmissions only during the UE's active listening windows, ensuring no data is lost. In Connected Mode, this is known as C-DRX, which balances latency and power consumption. In Idle Mode, a similar concept applies via Paging Discontinuous Reception, where the UE only wakes up at specific Paging Occasions within a Paging Frame to check for paging messages.
From a physical layer perspective, DRX impacts the UE's demodulation and decoding schedule. The UE must synchronize its wake-up periods with the network's transmission time intervals (TTIs). Advanced features introduced over releases include DRX alignment with measurement gaps and enhanced support for features like Carrier Aggregation and Dual Connectivity, where DRX patterns may be coordinated across multiple component carriers or cell groups. In 5G NR, DRX principles are extended with more flexible parameter sets to support diverse service requirements, from ultra-reliable low-latency communications (URLLC) to massive IoT, allowing for very short cycles for critical data or extremely long cycles for background sensor traffic.
Purpose & Motivation
DRX was created to address the paramount challenge of UE battery consumption in cellular networks. Continuously monitoring control channels for potential data assignments is extremely power-intensive. Before DRX, a UE in dedicated channel states would drain its battery rapidly even during periods of inactivity. The primary purpose of DRX is to dramatically extend the operational battery life of mobile devices, which is a critical factor for user experience and device adoption. It solves the problem of inefficient power usage during idle or semi-active states by allowing the device to enter a low-power state without losing network connectivity or the ability to receive incoming data with acceptable latency.
The evolution of DRX mirrors the evolution of mobile services. In early 3G (Release 99), basic DRX was introduced for idle mode. As always-on packet data services became common, Connected Mode DRX (C-DRX) was developed for HSPA and later refined in LTE, enabling smartphones to maintain IP connectivity for push notifications and background sync while conserving power. Each new release introduced optimizations: shorter setup times, alignment with other procedures like measurements, and adaptation to new network architectures like carrier aggregation. The motivation has consistently been to balance the conflicting demands of low latency (requiring frequent listening) and long battery life (requiring long sleep periods), tailoring the mechanism to diverse use cases from voice calls to always-connected cloud applications.
Key Features
- Configurable DRX cycles (short and long) to trade off between latency and power saving.
- Inactivity Timer to extend active time dynamically when data is being transmitted.
- On Duration Timer defining the mandatory listening window at the start of each cycle.
- Support for both Idle Mode DRX (for paging) and Connected Mode DRX (C-DRX).
- Alignment with measurement gaps, handovers, and other RRM procedures to avoid conflicts.
- Flexible parameterization in 5G NR to support diverse service requirements (eMBB, URLLC, mMTC).
Evolution Across Releases
Introduced basic Discontinuous Reception for idle mode in UMTS. Defined the initial concept where the UE periodically monitors the Paging Indicator Channel (PICH) and the associated Paging Channel (PCH) according to a DRX cycle length derived from the IMSI, allowing significant battery savings when not in a connected state.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.272 | 3GPP TS 23.272 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.468 | 3GPP TS 23.468 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 23.720 | 3GPP TS 23.720 |
| TS 23.776 | 3GPP TS 23.776 |
| TS 23.799 | 3GPP TS 23.799 |
| TS 25.123 | 3GPP TS 25.123 |
| TS 25.133 | 3GPP TS 25.133 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.304 | 3GPP TS 25.304 |
| TS 25.324 | 3GPP TS 25.324 |
| TS 25.367 | 3GPP TS 25.367 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.824 | 3GPP TS 25.824 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.913 | 3GPP TS 25.913 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.114 | 3GPP TS 26.114 |
| TS 26.910 | 3GPP TS 26.910 |
| TS 26.926 | 3GPP TS 26.926 |
| TS 26.998 | 3GPP TS 26.998 |
| TS 32.451 | 3GPP TR 32.451 |
| TS 36.111 | 3GPP TR 36.111 |
| TS 36.112 | 3GPP TR 36.112 |
| TS 36.133 | 3GPP TR 36.133 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.304 | 3GPP TR 36.304 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.763 | 3GPP TR 36.763 |
| TS 36.791 | 3GPP TR 36.791 |
| TS 36.855 | 3GPP TR 36.855 |
| TS 36.878 | 3GPP TR 36.878 |
| TS 36.902 | 3GPP TR 36.902 |
| TS 36.976 | 3GPP TR 36.976 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 37.911 | 3GPP TR 37.911 |
| TS 37.985 | 3GPP TR 37.985 |
| TS 38.124 | 3GPP TR 38.124 |
| TS 38.133 | 3GPP TR 38.133 |
| TS 38.174 | 3GPP TR 38.174 |
| TS 38.176 | 3GPP TR 38.176 |
| TS 38.214 | 3GPP TR 38.214 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.304 | 3GPP TR 38.304 |
| TS 38.305 | 3GPP TR 38.305 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.410 | 3GPP TR 38.410 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.869 | 3GPP TR 38.869 |
| TS 38.913 | 3GPP TR 38.913 |
| TS 43.068 | 3GPP TR 43.068 |