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.
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.
Explore further
Broader topics and technologies where DM plays a role.
Defining Specifications
3GPP specifications that define or reference DM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.022 vj00 | Radio Link Protocol (RLP) for Circuit Switched Data | Rel-19 |
| TS 24.141 vj00 | Presence Service Protocol Details | Rel-19 |
| TS 24.166 vj00 | IMS Conferencing Management Object | Rel-19 |
| TS 24.167 vj00 | 3GPP IMS Management Object Specification | Rel-19 |
| TS 24.216 vj00 | Communication Continuity Management Object | Rel-19 |
| TS 24.235 vc10 | I-WLAN Interworking Management Object | Rel-12 |
| TS 24.247 vj10 | IMS Messaging Service Protocol Details | Rel-19 |
| TS 24.275 vj00 | MO for MMTEL Basic Communication Part | Rel-19 |
| TS 24.285 vj00 | Allowed CSG List Management Object | Rel-19 |
| TS 24.286 vj00 | 3GPP TS 24.286: ICS Management Object | Rel-19 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 24.305 vj00 | Selective Disabling of 3GPP UE Capabilities | Rel-19 |
| TS 24.312 vj00 | ANDSF Management Objects Specification | Rel-19 |
| TS 24.323 vj00 | IMS Service Level Tracing Management Object | Rel-19 |
| TS 24.368 vj40 | NAS Configuration Management Object | Rel-19 |
| TS 24.391 vj00 | USSD over IMS Management Object Specification | Rel-19 |
| TS 24.417 vj00 | OIP/OIR Management Object Specification | Rel-19 |
| TS 24.424 vj00 | XCAP over Ut for Supplementary Services MO | Rel-19 |
| TS 24.483 vj20 | Mission Critical Services Management Object | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 24.841 v1600 | Presence Service IP Multimedia Subsystem | Rel-6 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 27.010 vj00 | Multiplexing Protocol for UE-TE Interface | Rel-19 |
| TS 28.405 vj40 | QoE Measurement Control & Configuration | Rel-19 |
| TS 28.620 vj20 | FMC Federated Network Information Model (FNIM) UIM | Rel-19 |
| TS 29.864 v801 | Application Server Service Data Definition for IMS Telephony | Rel-8 |
| TS 31.113 v1800 | USAT Interpreter Byte Code Specification | Rel-8 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.130 vj20 | Network Sharing OAM&P Requirements | Rel-19 |
| TS 32.571 vj00 | HNB/HeNB Type 2 Interface Management Concepts | Rel-19 |
| TS 32.582 vj00 | HNB Management Information Model for Type 1 Interface | Rel-19 |
| TS 32.584 vj00 | HNB OAM&P XML Definitions for Type 1 Interface | Rel-19 |
| TS 32.592 vj00 | HeNB OAM&P Information Model | Rel-19 |
| TS 32.594 vj00 | Data definitions for HeNB to HeMS Type 1 interface | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.816 v800 | UMTS Management Reuse for E-UTRAN/EPC | Rel-8 |
| TS 32.821 v1900 | SON OAM Architecture for Home NodeB | Rel-9 |
| TS 32.827 va10 | UE Management over Itf-N for MDT/SON | Rel-10 |
| TS 32.851 vc20 | Network Sharing OAM Requirements | Rel-12 |
| TR 32.972 vj00 | Energy Efficiency Study for 5G Networks | Rel-19 |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 |
| TS 37.462 vj00 | Iuant Interface Data Link Layer for RETAP/TMAAP | Rel-19 |
| TS 44.064 vj00 | GPRS Logical Link Control (LLC) Protocol | Rel-19 |