Description
Idle mode is one of the two fundamental RRC states in which a User Equipment (UE) can operate in a 3GPP network, the other being connected mode (RRC_CONNECTED). In idle mode, the UE has no dedicated radio resources allocated by the network and no Radio Resource Control (RRC) connection with the Radio Access Network (RAN). Despite the absence of an active connection, the UE is not passive: it performs a well-defined set of autonomous tasks that keep it reachable and prepared to initiate communication.
When a UE is powered on, it first performs a cell search procedure to find a suitable cell of a Public Land Mobile Network (PLMN). Once a suitable cell is found, the UE "camps" on that cell. Camping means the UE monitors the cell's broadcast channels — in LTE, the Master Information Block (MIB) on PBCH and System Information Blocks (SIBs) on PDSCH — to acquire parameters such as PLMN identity, cell selection/reselection thresholds, paging configuration, and access barring parameters. The UE then registers with the network through a Non-Access Stratum (NAS) procedure (Attach or Registration) if it is not already registered, so that the core network knows its location at the Tracking Area (TA) level.
While camped in idle mode, the UE continuously evaluates neighbouring cells and performs cell reselection according to rules broadcast in system information. It also monitors the paging channel (PCH) during specific paging occasions determined by the UE's International Mobile Subscriber Identity (IMSI) or 5G-S-TMSI and the DRX cycle configured by the network. Paging allows the network to alert the UE to incoming mobile-terminated calls, downlink data, or system information changes. Because the network only knows the UE's Tracking Area, paging is broadcast across all cells in the Tracking Area list, and the UE performs a Tracking Area Update (TAU) when it moves outside its registered list.
Idle mode is central to power efficiency and network scalability. The UE can enter deep sleep between paging occasions, dramatically reducing battery consumption compared to connected mode. For the network, idle mode means no per-UE context is maintained in the RAN — radio resources are only allocated when the UE transitions to connected mode via an RRC connection establishment procedure (triggered by paging, uplink data, or NAS signalling). This on-demand resource allocation is what allows a single cell to serve thousands of devices that are mostly dormant.
In 5G NR, the equivalent state is RRC_IDLE, complemented by RRC_INACTIVE (introduced in Rel-15), which retains some UE context in the RAN to enable faster transition. Idle mode remains the lowest-energy, lowest-overhead state and is the default state for UEs that are not actively communicating. The concept has been stable since early 3GPP releases, with the definition text itself essentially unchanged since Rel-8, reflecting the maturity and fundamental nature of the state model.
Purpose & Motivation
Idle mode exists to reconcile two competing requirements: the network must be able to reach a UE at any time (for incoming calls or data), yet it cannot afford to dedicate radio and processing resources to every UE continuously. Idle mode solves this by decoupling reachability from resource allocation. The UE autonomously maintains its presence in the network by camping on a cell and monitoring paging, while the network tracks the UE only at the granularity of a Tracking Area rather than at the cell level.
Before idle mode was formalised, early cellular systems had similar concepts, but 3GPP standardised the state model to enable interoperability and consistent UE behaviour across vendors. The introduction of explicit idle and connected states allowed the RAN to scale to millions of subscribers per network without a proportional increase in signalling and hardware. It also enabled significant battery savings, which became critical as mobile devices evolved from voice-only handsets to always-on smartphones and, later, to battery-constrained IoT devices.
The definition of idle mode has proven remarkably durable. From Rel-4 through Rel-19, the meaning has remained the same: a switched-on UE with no established RRC connection. The only notable textual revision occurred in Rel-8, when the wording was refined to explicitly name "User Equipment (UE)" and "Radio Resource Control (RRC)" rather than the more generic phrasing used earlier. This stability reflects that idle mode is a foundational architectural concept rather than a feature subject to frequent change.
What changed in its specifications
The latest release-to-release comparison of specifications that define Idle mode. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-13 brings only minor changes to TS 34.124: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 34.124 →Technology family
RRC states and connection modes · Radio Access Network
- R97 GPRS IDLE, GPRS READY, GPRS STANDBY
- R99 CELL_DCH, CELL_FACH, CELL_PCH, PMM-CONNECTED, PMM-IDLE, URA_PCH, UTRA Idle mode
- Rel-8 RRC_CONNECTED, RRC_IDLE
- Rel-15 RRC_INACTIVE
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 7 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in R99 (release dating of the term; no individual change cited).
Rel-13 introduced extended Idle mode DRX for idle UEs in LTE and Gb mode, and specified the MME's Modify Bearer Request content for UEs in Idle mode during Network Triggered Service Request.
- Introducing extended Idle mode DRX feature to LTE TS 23.401CR2889
- Introduction of support for extended Idle mode DRX for Gb mode TS 23.060CR1982
- “the MME shall include only the existing Bearer Contexts (not the new Bearer Contexts just created)” TS 29.274 v13.13.0
Rel-15 specifies Idle mode mobility between 5GS and EPS over N26, adding Context Request, identification and authentication handling plus related flags for the idle-mode procedures.
- “The new MME shall send the Context Request message to the old AMF on N26 interface as a part of an 5GS to EPS Idle mode Mobility” TS 29.274 v15.9.0
- Perform authentication before Context Acknowledgement during 5GS to EPS Idle mode mobility using N26 interface TS 23.502CR0249
- “This flag shall also be set to 1 by the new AMF/new MME during the Idle mode Mobility between 5GS and EPS using N26 interface.” TS 29.274 v15.9.0
Rel-16 added Idle mode mobility procedures between 5GS and EPS over N26 with data forwarding, plus I-SMF removal/insertion variants, and Idle mode handling in NR test cases.
- “4.11.1.3.2A 5GS to EPS Idle mode mobility using N26 interface with data forwarding” TS 23.502 v16.19.0
- “4.11.1.3.3A EPS to 5GS Idle mode mobility using N26 interface with data forwarding” TS 23.502 v16.19.0
- Enhance Idle mode mobility using N26 interface procedure to support NAS-SM data transfer via SCEF+NEF TS 23.502CR0928
Rel-17 added new NR idle mode test cases (6.1.1.4a, 6.1.2.15a) and the specification handles idle mode differently for UEs with different E-UTRA RAC in TN and NTN.
- Idle mode handling for UEs with different E-UTRA RAC in TN and NTN TS 23.401CR3719
- “Addition of new Idle mode TC 6.1.1.4a” TS 38.523-1 v17.9.0
- “Addition of new Idle mode TC to test the intraFreqReselection in MIB message is set to not allowed” TS 38.523-1 v17.9.0
Rel-18 38.523-1 adds 2Rx XR Idle mode test cases (serving cell barred, intra-frequency reselection not allowed, access not allowed) and corrects several existing Idle mode test cases.
- “Addition of 2Rx XR Idle mode test case for Serving cell becomes barred” TS 38.523-1 v18.4.0
- “Addition of 2Rx XR Idle mode test case for Intra frequency reselection not allowed” TS 38.523-1 v18.4.0
- Correction to Idle mode test case 6.1.2.4 TS 38.523-1CR4752
Rel-19 adds new Idle mode test cases such as LP-WUS monitoring and corrects Idle mode procedures, including EMM TRANSPORT handling in Idle mode with suspend indication.
- Introduction of RRC Idle mode LP-WUS monitoring test cases TS 38.523-1CR5461
- EMM TRANSPORT handling in Idle mode with suspend indication TS 24.301CR4595
- Update to Idle mode TC for NR channel BW less than 5MHz for FR1 TS 38.523-1CR5034
Defining Specifications
3GPP specifications that define or reference Idle mode, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 34.124 vj00 | EMC Requirements for 3G UTRA Terminals | Rel-19 read |
| TR 34.926 vj00 | EMC Requirements for Mobile Terminals | Rel-19 read |
| TS 36.124 vj00 | EMC for E-UTRA User Equipment | Rel-19 read |
| TS 38.124 vj00 | NR UE EMC Requirements | Rel-19 read |