MT-EDT

Mobile Terminated Early Data Transmission

IoT →
Introduced in Rel-16

MT-EDT is an NB-IoT and LTE-M feature that allows efficient, network-initiated downlink data transmission during the random access procedure to reduce signaling and power consumption for small packets.

Category
IoT
Introduced
Rel-16
Where
Core Network › Evolved Packet Core
Specifications
7 specs
MT-EDT Description Purpose Related Classification Detected Changes Specifications

Description

Mobile Terminated Early Data Transmission (MT-EDT) is an enhancement for Cellular IoT (CIoT) technologies, specifically Narrowband IoT (NB-IoT) and LTE for Machine-Type Communications (LTE-M). It optimizes the procedure for delivering a small downlink data packet from the network to a User Equipment (UE) that is in a power-saving state (e.g., Idle or Inactive). Traditionally, a mobile-terminated data delivery requires a full Service Request procedure, involving paging, random access, RRC connection establishment, and data bearer setup, which is signaling-intensive and consumes significant energy for the UE. MT-EDT allows the downlink data to be piggybacked on the message used to respond to the UE's random access preamble during the contention-based random access procedure. The process is triggered when the network receives downlink data for a UE in RRC Idle or RRC Inactive state. The network pages the UE with an indication that MT-EDT is supported. The UE, upon receiving the page, initiates a random access procedure using a specific preamble allocated for EDT. In the Random Access Response (RAR) message, the network includes not only the usual timing advance and uplink grant but also the downlink data payload itself (or an indication of it). The UE can then receive the data directly in this early message exchange, often completing the transaction without transitioning to RRC Connected state. This significantly reduces the number of signaling messages exchanged between the UE and the network (eNodeB/gNB). The feature is tightly coupled with Control Plane CIoT EPS Optimization and User Plane CIoT EPS Optimization. It is governed by specific thresholds for data size to ensure efficiency. Key specifications define the RRC procedures, NAS signaling adaptations, and core network impacts, particularly in the MME and Serving Gateway (SGW).

Purpose & Motivation

MT-EDT was created to address the critical challenge of power consumption and network signaling overhead for IoT devices that primarily receive small, infrequent downlink packets (e.g., configuration updates, remote commands, or firmware patches). Prior to EDT, every mobile-terminated data transaction, no matter how small, required a full RRC connection setup, involving multiple round-trip signaling messages. This was inefficient for battery-constrained IoT devices that spend most of their time in deep sleep. The motivation stemmed from the need to extend IoT device battery life to years while maintaining reliable downlink reachability. MT-EDT solves this by minimizing the active radio time and the number of transmitted/received messages required for a downlink transaction. It builds upon the foundation of Uplink EDT (introduced earlier), extending the early data transmission concept to the downlink direction. This optimization is a key enabler for massive IoT deployments where network capacity and device longevity are paramount. It addresses the limitations of previous paging and service request procedures, which were designed for human-centric traffic with different latency and power profiles.

Classification

Part ofEDT

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 7 changes

In Release 15, MT-EDT for Control Plane CIoT EPS optimization was newly introduced, enabling mobile terminated data transport. This function involves the buffering of mobile terminated data at the Serving GW or MME to handle communication with potentially unreachable UEs. The release also clarified procedures for when uplink data transmission in EDT is not considered successful.

  • Introducing Early Data Transmission for Control Plane CIoT EPS optimization TS 23.401CR3436
  • EPS mobile identity and UE status in the ATTACH REQUEST message TS 24.301CR3028
  • Correction on transmission failure of IDENTITY RESPONSE message TS 24.301CR3078
  • Delay the transmission of kseaf after home network verifies the RES TS 33.501CR0280
  • Acknowledging possibility of early calculation of EMSK TS 33.501CR0401
  • Clarification on when UL data transmission in EDT is not considered successful TS 36.300CR1201

+ 1 more changes

Rel-16 18 changes

In Release 16, the new Mobile Terminated Early Data Transmission (MT-EDT) function was introduced, enabling mobile terminated services for UEs using Control Plane CIoT EPS Optimisation. This release added specific support indications for MT-EDT and included provisions for early security re-activation during the RRC Connection Resume procedure. These enhancements allowed for more efficient handling of downlink data to idle-mode devices within the existing reachability and congestion control frameworks.

  • Introduction of MT-EDT TS 23.401CR3542
  • Addition of MT-EDT support indication TS 24.301CR3332
  • Early security re-activation at RRC Connection Resume TS 36.306CR1723
  • SMS transmission in Communication pattern parameters TS 23.401CR3552
  • MT-EDT related update TS 23.401CR3589
  • 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario TS 36.300CR1347

+ 12 more changes

Rel-17 2 changes

In Release 17, the MT-EDT function was enhanced to improve reliability for mobile terminated services during network congestion. Specifically, the update ensured that mobile terminated services remained excepted from NAS-level congestion control measures, aligning with the handling of other high-priority access scenarios. This built upon existing rules where UEs were already allowed to respond to paging for mobile terminated events without being restricted by the Service Gap timer.

  • EPS MUSIM SR transmission failure TS 24.301CR3611
  • Traffic usage reporting on Redundant Transmission at transport layer TS 29.244CR0591
Rel-18 2 changes

In Release 18, enhancements to Mobile Terminated Early Data Transmission (MT-EDT) included specific clarifications on the rules for data transmission during EDT procedures. Furthermore, the release provided a correction to the determination of the periodic timer and the mobile reachable timer based on the user plane and its start, refining reachability management for UEs. These updates aimed to improve the reliability and control of mobile terminated services for IoT devices using Control Plane CIoT EPS Optimisation.

  • Correction to determination of periodic timer, mobile reachable timer based on UP and start of UP TS 24.301CR3996
  • Clarification on data transmission for EDT TS 36.300CR1422
Rel-19 2 changes

In Release 19, the enhancements for MT-EDT involved adjustments to the mobile reachable timer and the implicit detach timer to improve network efficiency during congestion control. Specifically, the MME was given the capability to adjust these timers when applying General NAS level Mobility Management Congestion Control to a UE. This refinement ensures more reliable mobile terminated service reachability, including for MT-EDT, during controlled overload conditions.

  • The adjustment of mobile reachable timer or the implicit detach timer TS 24.301CR4343
  • Correction to the mobile reachable timer TS 24.301CR4656

Explore further

Broader topics and technologies where MT-EDT plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vj50 Evolved Packet System (EPS) Stage 2 Description Rel-19
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.274 vj50 GTPv2-C Control Plane Protocol Specification Rel-19
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19