Even when there is no active traffic flowing back and forth between the network and the User Equipment (UE), the UE normally has to continuously listen to the network. At the very least, the UE must remain prepared to decode the Physical Downlink Control Channel (PDCCH). This operational requirement means the UE must remain in an “ON” state all the time, which inherently creates a constant and significant drain on the battery. One cannot simply force the UE to shut down into a deep sleep mode whenever there is a lull in traffic, because the network might independently attempt to send data while the UE is sleeping, causing the UE to completely miss the transmission.
The engineering solution to balancing battery conservation and reliable data reception is Discontinuous Reception (DRX). DRX establishes a mechanism where the UE enters a sleep mode for a specific period of time, wakes up to actively check for incoming network data, and then returns to sleep if no data is present, repeating this cycle continuously. To prevent the worst-case scenario—where the network sends data while the UE is asleep and cannot receive it—both the UE and the Network follow a strictly defined synchronization agreement that outlines exact sleep and wake schedules.
The Key DRX Parameters
The network dynamically controls these sleep and wake schedules by configuring specific parameters sent to the UE via RRC Connection Reconfiguration or RRC Connection Setup messages. The primary parameters governing this behavior include the following:
- DRX Cycle: This value represents the total duration of one complete “ON time” combined with one subsequent “OFF time”.
- onDurationTimer: This explicitly specifies the duration of the “ON time” that occurs within a single DRX cycle.
- drx-InactivityTimer: This critical timer dictates precisely how long the UE must remain “ON” after it successfully receives a PDCCH transmission. While this timer remains active, the UE stays in the ON state, which can effectively extend the UE’s ON period deep into the time block that would normally be designated as the “OFF” period.
- drx-RetransmissionTimer: This defines the maximum number of consecutive PDCCH subframes the UE is required to stay active to wait for an incoming retransmission after the earliest available retransmission time.
- shortDRX-Cycle: This establishes a shorter, secondary DRX cycle that can be implemented exclusively within the broader “OFF” period of a standard long DRX Cycle.
- drxShortCycleTimer: This represents the consecutive number of subframes that the UE must strictly adhere to the short DRX cycle immediately after the DRX Inactivity Timer has expired.