Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · IoT

MICO

Mobile Initiated Connection Only

IoT →

MICO is a UE power-saving mode for IoT devices where the network cannot page the device, so it only becomes reachable for mobile-terminated services when it initiates communication itself.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
8 specs
MICO Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define MICO. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (39 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 8 changes
  • MICO and interworking with EPC TS 23.501CR0110
  • Local deactivate MICO for emergency service TS 23.501CR0297
  • Clarifications on MICO indication TS 24.501CR0008
  • Removal of redundant MICO statement TS 24.501CR0064
  • Clarification on MICO indication and LADN information via generic UE configuration update procedure TS 24.501CR0351
  • Enabling use of and disabling use of MICO mode TS 24.501CR0528

+ 2 more changes

Rel-16 17 changes
  • Use of NWDAF analytics for decision of MICO mode parameters TS 23.501CR0837
  • Corrections to MICO mode with Active Time TS 23.501CR1250
  • Active Time for MICO mode TS 24.501CR1019
  • Strictly periodic registration timer indication for MICO mode TS 24.501CR1030
  • MICO mode and Periodic Registration Timer Control TS 23.501CR1047
  • Clarification on MICO and eDRX during CN node changes TS 23.501CR1075

+ 11 more changes

Rel-17 3 changes
  • Clarification on the SPRTI bit of the MICO indication IE TS 24.501CR2643
  • Correction on MICO indication IE TS 24.501CR2918
  • Correction for enabling use of MICO mode TS 24.501CR4041
Rel-18 8 changes
  • Supporting multicast MBS session for UE in MICO mode TS 24.501CR5318
  • Deactivate MICO mode at the broadcast start time/activation times of a broadcast MBS session TS 24.501CR5814
  • MBS operation with eDRX MICO TS 38.304CR0399
  • Correction to timers handling in MICO mode TS 24.501CR6129
  • Tsense timer handling for MICO mode TS 24.501CR6166
  • The UE handling on the MICO mode TS 24.501CR6160

+ 2 more changes

Rel-19 3 changes
  • PSAP emergency callback interaction with MICO mode TS 23.501CR6413
  • Correcting handling NAS timers in MICO mode and unavailability TS 24.501CR6536
  • PSAP emergency callback interaction with MICO mode TS 24.501CR7016

Defining Specifications

3GPP specifications that define or reference MICO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 32.256 vk10 5G Connection and Mobility Charging Rel-20 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read