Mobile Originated Early Data Transmission

Description

Mobile Originated Early Data Transmission (MO-EDT) is an optimization mechanism defined for Cellular IoT (CIoT) technologies, specifically NB-IoT and LTE-M (eMTC). It enables a UE to send a limited payload of uplink user data embedded within the Msg3 of the Random Access Channel (RACH) procedure in LTE, or within the RRC Early Data Request message in NR, before the Radio Resource Control (RRC) connection transitions to the RRC_CONNECTED state. This process bypasses the full connection setup, which involves multiple signaling messages for security activation and data radio bearer establishment.

The procedure is initiated when a CIoT UE in RRC_IDLE or RRC_INACTIVE state has a small amount of data to send (up to a few hundred bytes, as defined by the network). The UE indicates its capability and intent to use EDT in the Random Access Preamble (Msg1) or RRC Connection Request (Msg3). The network, if it supports EDT, responds with a message (e.g., RAR for Msg2 or RRC Connection Setup for EDT) that grants resources and parameters for the uplink data transmission. The UE then transmits its data along with the RRC message (e.g., RRC Early Data Request) in the granted uplink resources.

Key components involved include the UE's CIoT stack, the eNodeB/gNodeB which must support EDT processing, and the core network (MME for LTE, AMF for 5GC). The core network node receives the data via the S1-AP or NG-AP Initial UE Message, which carries the user data payload. After successful reception, the network can release the RRC connection immediately without moving the UE to RRC_CONNECTED, sending a release message (e.g., RRC Connection Release) that may include a small downlink response if needed. This entire exchange is contained within the random access and initial connection signaling phases.

The role of MO-EDT in the network is to minimize the signaling overhead and energy consumption associated with infrequent small data transmissions, which are characteristic of many IoT applications like sensor readings or status updates. By reducing the number of messages exchanged and the time the radio is active, it extends battery life for devices that may be deployed for years. It is a critical enabler for massive Machine-Type Communication (mMTC) use cases within 5G, improving network efficiency by reducing control plane congestion.

Purpose & Motivation

MO-EDT was created to address the significant inefficiency of using traditional LTE connection establishment procedures for IoT devices that only need to send very small, infrequent data packets. The standard LTE RRC connection setup involves several message exchanges (RRC Connection Request, Setup, Complete, Security Mode Command, etc.), each requiring device energy and network resources. For a sensor sending a few bytes of data, this signaling overhead could be orders of magnitude larger than the data payload itself, leading to poor battery life and unnecessary network load.

The technology solves the problem of optimizing network architecture for massive-scale, low-power, low-data-rate IoT deployments. It was motivated by the requirements of 3GPP's Cellular IoT work item, which aimed to enable battery lifetimes of over 10 years for devices. Previous approaches, like Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX), helped with power saving in idle mode but did not reduce the signaling cost per transmission.

MO-EDT, introduced in Release 15/16, directly tackles this by allowing data transmission during the initial access, effectively collapsing the data transmission into the connection request phase. This reduces latency, signaling messages, and radio-on time, directly translating to lower power consumption. It represents a shift in design philosophy, treating small data as an integral part of the control procedure rather than a separate user-plane activity.

Key Features

• Uplink Data in Msg3/RRC Request: Transmits user data payload within the RRC Connection Request or Early Data Request message during random access.
• No Full RRC Connection: Avoids transition to RRC_CONNECTED state, skipping security activation and data radio bearer setup for the transmission.
• Fast Release: Network can immediately release the connection after data reception with an RRC Connection Release message.
• Limited Payload Size: Supports transmission of small data packets (size defined by network, typically up to ~1000 bytes for LTE-M, less for NB-IoT).
• Support for Downlink Response: Allows the network to include a small downlink data response within the connection release message.
• Operation in IDLE/INACTIVE: Can be initiated from both RRC_IDLE (LTE) and RRC_INACTIVE (5G NR) states, aligning with IoT power-saving states.

Evolution Across Releases

Defining Specifications