Description
Disconnected Mode (DM) is a fundamental frame type and operational state defined across numerous 3GPP specifications, primarily within the context of data link layer protocols. It represents a state where a logical connection between two peer entities (e.g., a User Equipment and the network, or between network nodes) is maintained, but the active transfer of user data is suspended. The physical resources associated with the connection may be released, but the context and configuration parameters are preserved by both ends. This state is distinct from a full connection release or an idle state, as it allows for a faster resumption of data transfer when needed, avoiding the full signaling overhead of a fresh connection establishment.
Architecturally, DM is implemented within protocol layers like the Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP) in the radio interface, and similar concepts exist in core network signaling protocols. The mode is typically entered through an explicit control procedure, such as a Suspend or Inactivity procedure, triggered by a lack of data activity for a configured timer. While in DM, the device or network node may power down relevant radio components or processing units to conserve energy, while periodically monitoring for paging or trigger messages that indicate the need to resume the connection.
Key components enabling DM include the state management logic within the protocol state machines, the timers governing inactivity detection and state transitions, and the context preservation mechanisms. The preserved context includes security keys, bearer configurations, IP addresses, and Quality of Service (QoS) profiles. The role of DM in the network is multifaceted: it is a cornerstone for device power saving, especially for battery-powered User Equipment, and it is critical for efficient radio resource management. By allowing the network to quickly reclaim physical resources (like time-frequency blocks or channelization codes) while keeping a logical handle on the connection, overall system capacity is improved. Resumption from DM to active data transfer involves a reactivation procedure, which is significantly lighter in signaling than a full setup from an idle state, thus reducing latency for bursty data applications.
Purpose & Motivation
The primary purpose of Disconnected Mode is to optimize network resource utilization and extend device battery life. In early mobile systems, a device was either fully connected (consuming radio resources and power) or completely idle (requiring a lengthy setup procedure to resume). This binary approach was inefficient for applications with intermittent, bursty data patterns, such as web browsing, instant messaging, or push email. DM was introduced to create an intermediate, low-overhead state that balances the trade-off between fast connection resumption and resource conservation.
Historically, the motivation stemmed from the need to improve the user experience for packet-switched services in 3G (UMTS) and evolved systems. Without DM, devices would either drain their batteries quickly by staying in a continuously connected state or suffer from high latency when transitioning from idle to active. DM solves this by allowing the network to suspend the connection during periods of inactivity while retaining the necessary session context. This addressed the limitations of previous approaches that lacked such a graceful, context-preserving suspend/resume mechanism.
Furthermore, DM enables more sophisticated network-controlled mobility and state management. It allows the network to manage a large population of devices in a resource-efficient manner, which became increasingly important with the rise of always-on applications and, later, Internet of Things (IoT) devices. By standardizing the DM frame type and associated procedures across multiple specifications, 3GPP ensured interoperability and consistent behavior for power saving and fast connection reactivation across different generations of technology, from 3G to 5G.
Key Features
- Context preservation of security, QoS, and bearer parameters during suspension
- Explicit control procedures for entering and exiting the mode (e.g., Suspend/Resume)
- Timer-based triggering for automatic transition to DM upon inactivity
- Reduced signaling overhead for connection reactivation compared to full setup
- Enables significant power saving for User Equipment by allowing radio component deactivation
- Allows network to re-allocate physical layer resources while maintaining logical session
Evolution Across Releases
Introduced as a fundamental frame type and state within various protocol specifications, primarily for UMTS. Established the basic architecture for suspending a packet data protocol (PDP) context or RRC connection while preserving the context at the Serving GPRS Support Node (SGSN) and User Equipment. Enabled efficient handling of bursty data traffic in early 3G networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.022 | 3GPP TS 24.022 |
| TS 24.141 | 3GPP TS 24.141 |
| TS 24.166 | 3GPP TS 24.166 |
| TS 24.167 | 3GPP TS 24.167 |
| TS 24.216 | 3GPP TS 24.216 |
| TS 24.235 | 3GPP TS 24.235 |
| TS 24.247 | 3GPP TS 24.247 |
| TS 24.275 | 3GPP TS 24.275 |
| TS 24.285 | 3GPP TS 24.285 |
| TS 24.286 | 3GPP TS 24.286 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 24.305 | 3GPP TS 24.305 |
| TS 24.312 | 3GPP TS 24.312 |
| TS 24.323 | 3GPP TS 24.323 |
| TS 24.368 | 3GPP TS 24.368 |
| TS 24.391 | 3GPP TS 24.391 |
| TS 24.417 | 3GPP TS 24.417 |
| TS 24.424 | 3GPP TS 24.424 |
| TS 24.483 | 3GPP TS 24.483 |
| TS 24.484 | 3GPP TS 24.484 |
| TS 24.841 | 3GPP TS 24.841 |
| TS 26.247 | 3GPP TS 26.247 |
| TS 27.010 | 3GPP TS 27.010 |
| TS 28.405 | 3GPP TS 28.405 |
| TS 28.620 | 3GPP TS 28.620 |
| TS 29.864 | 3GPP TS 29.864 |
| TS 31.113 | 3GPP TR 31.113 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.130 | 3GPP TR 32.130 |
| TS 32.571 | 3GPP TR 32.571 |
| TS 32.582 | 3GPP TR 32.582 |
| TS 32.584 | 3GPP TR 32.584 |
| TS 32.592 | 3GPP TR 32.592 |
| TS 32.594 | 3GPP TR 32.594 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.816 | 3GPP TR 32.816 |
| TS 32.821 | 3GPP TR 32.821 |
| TS 32.827 | 3GPP TR 32.827 |
| TS 32.851 | 3GPP TR 32.851 |
| TS 32.972 | 3GPP TR 32.972 |
| TS 33.812 | 3GPP TR 33.812 |
| TS 37.462 | 3GPP TR 37.462 |
| TS 44.064 | 3GPP TR 44.064 |