Description
Early Data Transmission (EDT) is a feature introduced in 3GPP Release 15 for LTE-based IoT technologies, specifically for narrowband IoT (NB-IoT) and enhanced machine-type communication (eMTC). It enables a device to transmit a small amount of uplink data during the random access procedure, without establishing a full radio resource control (RRC) connection. This is particularly beneficial for IoT devices that need to send infrequent small data packets, as it reduces signalling overhead and power consumption.
The EDT procedure works by allowing the UE to include user data in the random access message (Msg3) or in a dedicated message following the random access response. There are two variants: Control Plane EDT (CP-EDT) and User Plane EDT (UP-EDT). In CP-EDT, the data is carried in the control plane signalling, typically using the NAS message, and the S1 connection is established or resumed upon reception of the uplink data. In UP-EDT, the data is carried over the user plane, and the S1 connection is established or resumed, with the possibility of releasing or suspending the connection along with the downlink data transmission. The feature is specified in 3GPP TS 36.321 (MAC protocol) and TS 36.331 (RRC protocol).
From an architectural perspective, EDT involves the UE, the eNB, the MME (for CP-EDT) or S-GW/P-GW (for UP-EDT), and the core network. The eNB allocates resources for the EDT transmission based on the random access preamble and the indicated data size. The UE indicates its intention to use EDT via a specific preamble or a MAC control element. The eNB then provides an uplink grant in the random access response, and the UE transmits its data in Msg3. For CP-EDT, the data is encapsulated in a NAS message and forwarded to the MME, which then forwards it to the SCEF or the application server. For UP-EDT, the data is sent over the user plane, and the S1 connection is established or resumed to carry the data.
EDT significantly reduces the signalling overhead associated with connection setup and release. In traditional IoT communication, a device must perform a full random access procedure, establish an RRC connection, perform security activation, and then send data. This involves multiple round trips and consumes significant power. EDT allows the data to be sent earlier, reducing the number of messages and the time the device needs to stay awake. This is crucial for battery-powered IoT devices that are expected to operate for years on a single battery.
The feature also supports downlink data transmission following the uplink data. After the uplink data is sent, the network may send downlink data to the UE, either in the same random access procedure or in a subsequent message. The S1 connection may be released or suspended after the downlink data transmission, allowing the device to return to idle mode quickly. This makes EDT suitable for applications such as smart metering, sensor readings, and other infrequent small data transmissions.
In Release 19, the definition was updated to include the CB-Msg3-EDT procedure, which refers to contention-based Msg3 EDT. This indicates that the feature continues to evolve to support new procedures and optimizations. Overall, EDT is a key enabler for massive machine-type communication (mMTC) and IoT, providing efficient small data transmission with minimal signalling and power consumption.
Purpose & Motivation
Early Data Transmission was created to address the inefficiencies of traditional connection setup for IoT devices. IoT devices often need to send small amounts of data infrequently, but the conventional procedure requires a full random access and RRC connection establishment, which involves multiple signalling messages and consumes significant power. This is particularly problematic for battery-powered devices that are expected to operate for years without maintenance.
The motivation was to reduce signalling overhead, latency, and power consumption for small data transmissions. By allowing data to be sent during the random access procedure, EDT eliminates the need for a full connection setup, reducing the number of messages exchanged and the time the device needs to be active. This directly extends battery life and improves network efficiency by reducing signalling load.
Historically, IoT devices using LTE-M and NB-IoT were designed for low power and low cost, but the connection setup overhead was a significant burden. EDT, introduced in Release 15, was a direct response to this challenge, building on earlier work on small data transmission and control plane optimizations. It has since become a fundamental feature for IoT deployments, and its evolution continues with enhancements like CB-Msg3-EDT in Release 19.
What changed in its specifications
The latest release-to-release comparison of specifications that define Early Data Transmission. Each summary describes the whole specification, not only this term.
Rel-19 adds to TS 36.321 a contention-based Msg3 early data transmission (CB-Msg3-EDT) procedure, along with new definitions and abbreviations. This is the only feature overview provided, so no other additions can be named.
Full comparison in TS 36.321 →Rel-19 adds NTN-for-IoT Phase 3 and inter-RAT mobility from E-UTRAN to NR NTN, plus LTE-based 5G Broadcast Phase 2 changes. It also adds IMS disaster-roaming access barring, NTN-for-NR Phase 3 fields, and NR RRM Phase 5 items.
Full comparison in TS 36.331 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Early Data Transmission, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.321 vj30 | E-UTRA MAC Protocol Specification | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |