Description
Mobile Initiated Connection Only (MICO) is a power-saving feature defined in 3GPP standards, primarily for IoT and other battery-constrained devices. It fundamentally alters the traditional reachability model. In a standard 3GPP connection, the network can page a UE at any time during its registered state to deliver mobile-terminated data or signaling, requiring the UE to periodically listen for paging messages. MICO mode disables this network-side paging capability. When a UE registers with the network and indicates support for MICO, the network allocates it a MICO-specific Allowed NSSAI and configures the Access and Mobility Management Function (AMF) accordingly. After successful registration, the UE enters a deep sleep state. The AMF will reject any mobile-terminated requests (like Session Management or Data Notification messages from the SMF/UPF) with a cause indicating the UE is unreachable. The network may buffer or discard this downlink data based on policy. Reachability is restored only when the UE itself initiates a Service Request procedure, typically triggered by its own uplink data or periodic Registration Update timer expiry. This procedure moves the UE to a connected state, allowing any buffered downlink data to be delivered. The UE's Radio Resource Control (RRC) state in MICO mode is typically RRC_IDLE, but with the crucial difference that it does not monitor the paging channel, leading to substantial power savings. The feature is negotiated during the Registration procedure via the MICO indication in the UE's Registration Request and the network's MICO indication in the Registration Accept. Network parameters like the Active Time and Periodic Registration Timer are also configured to manage the UE's sleep cycles and mandatory check-ins.
Purpose & Motivation
MICO was created to address the critical challenge of battery life for massive Machine-Type Communication (mMTC) devices in 5G and beyond. Traditional cellular devices, even in idle mode, must wake up frequently to listen for paging messages, which consumes significant energy over time. For IoT sensors, meters, or trackers that send data infrequently (e.g., once per day) but are expected to operate for years on a single battery, this constant readiness for downlink traffic is wasteful and impractical. MICO solves this by shifting to a purely mobile-originated communication model, aligning the network's behavior with the typical traffic pattern of many IoT applications. It was motivated by the need to make 5G networks viable for ultra-low-power, wide-area IoT deployments, competing with and surpassing the energy efficiency of non-cellular LPWAN technologies like LoRaWAN or Sigfox. By eliminating the power drain from paging reception, MICO enables decade-long battery life, which is a key requirement for many industrial and smart city IoT use cases. It represents a paradigm shift from 'always reachable' to 'reachable on device terms,' optimizing the network for asymmetric, device-triggered traffic.
Key Features
- Disables network-initiated paging for the UE
- Negotiated during the Registration procedure via NAS signaling
- UE reachable only when it initiates a Service Request
- AMF rejects mobile-terminated sessions with an explicit 'UE unreachable' cause
- Supports extended discontinuous reception (eDRX) cycles for further power saving
- Network may apply specific policies for handling buffered downlink data
Evolution Across Releases
Introduced as a core 5G feature for power saving. Defined the basic NAS signaling for MICO indication in Registration messages, the behavior of the AMF to reject MT sessions, and the association with Network Slicing (Allowed NSSAI). Established the fundamental architectural principle of mobile-initiated-only reachability.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.501 | 3GPP TS 23.501 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.890 | 3GPP TS 24.890 |
| TS 29.503 | 3GPP TS 29.503 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 32.256 | 3GPP TR 32.256 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.304 | 3GPP TR 38.304 |