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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Use of NWDAF analytics for decision of MICO mode parameters TS 23.501CR0837
- Corrections to MICO mode with Active Time TS 23.501CR1250
- MICO mode and Periodic Registration Timer Control TS 23.501CR1047
- Clarification on MICO and eDRX during CN node changes TS 23.501CR1075
- Interaction between MICO mode with active time and eDRX TS 23.501CR1283
- Corrections to analytics used by AMF for MICO mode and SMF for UPF selection TS 23.501CR1405
+ 2 more changes
Explore further
Broader topics and technologies where MICO plays a role.
Defining Specifications
3GPP specifications that define or reference MICO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk20 | 5G System Architecture Stage 2 | Rel-20 |
| TS 24.501 vk00 | 5G System (5GS) Non-Access Stratum (NAS) Protocol | Rel-20 |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 |
| TS 29.503 vk00 | UDM Service Based Interface Stage 3 | Rel-20 |
| TS 31.102 vj50 | USIM Application for 3GPP Telecom Networks | Rel-19 |
| TS 32.256 vk00 | 5G Connection and Mobility Charging | Rel-20 |
| TS 38.300 vj30 | NR and NG-RAN Overall Description | Rel-19 |
| TS 38.304 vj30 | NR UE Idle and Inactive State Procedures | Rel-19 |