MT-SDT

Mobile Terminated Small Data Transmission

IoT →
Introduced in Rel-18

MT-SDT is a 5G NR feature that enables efficient network-initiated delivery of small data packets to IoT devices in RRC Inactive state, reducing signaling and power consumption.

Category
IoT
Introduced
Rel-18
Where
Radio Access Network › NG-RAN (5G)
Specifications
10 specs
MT-SDT Description Purpose Related Classification Detected Changes Specifications

Description

Mobile Terminated Small Data Transmission (MT-SDT) is a 3GPP feature standardized in Release 18 for 5G New Radio (NR). It is a counterpart to Mobile Originated Small Data Transmission (MO-SDT) and is designed for IoT and mMTC (massive Machine-Type Communications) scenarios. The core principle is to allow the network to deliver a small amount of downlink data to a User Equipment (UE) that is in the RRC_INACTIVE state, without transitioning the UE to the RRC_CONNECTED state. This is crucial for battery-constrained IoT devices that only sporadically receive small commands, updates, or acknowledgements from network servers.

Architecturally, MT-SDT leverages the existing 5G core network (5GC) and NG-RAN architecture. When downlink data arrives at the UPF (User Plane Function) for a UE in RRC_INACTIVE, the 5GC, specifically the AMF (Access and Mobility Management Function), triggers a Network Triggered Service Request procedure. The RAN, which maintains the UE context in the RRC_INACTIVE state (stored in the last serving gNB and potentially in a RAN-based Notification Area), pages the UE. Upon receiving the paging message, the UE initiates a Random Access procedure. However, instead of performing a conventional Service Request leading to RRC_CONNECTED, the UE can indicate its capability and intent to use MT-SDT during the Random Access process, typically via a specific preamble or message.

The key technical enabler is the transmission of the downlink user data within the initial signaling messages of the RRC procedure that resumes the suspended RRC connection. Specifically, the gNB can include the downlink data payload within the RRCResume message or a subsequent downlink RRC message before the RRC connection is fully resumed to the CONNECTED state. This data is transmitted using the stored AS security context and the same protocol layers (PDCP, RLC, MAC) as a normal data transmission, but the signaling procedure is truncated. After successfully delivering the data, the UE can return to RRC_INACTIVE without completing the full resume procedure, or the network may decide to move the UE to RRC_CONNECTED if more data is pending. This mechanism significantly reduces control plane signaling between UE and network and minimizes the time the UE's radio transceiver is active, directly extending battery life.

MT-SDT is defined across multiple 3GPP specification groups. TS 38.300 provides the overall NR system description, while TS 38.331 (RRC) and TS 38.321 (MAC) detail the signaling procedures and MAC enhancements. TS 38.423 (XnAP) and TS 38.473 (NGAP) cover the relevant RAN interface signaling for context fetching and paging coordination. TS 29.244 specifies the 5GC User Plane protocol. TS 37.480 and 37.483 cover performance requirements and test specifications for UE and network, ensuring interoperability and reliable operation. Its role is integral to 5G's support for massive-scale, low-power IoT deployments, making network-initiated communication as efficient as device-originated communication.

Purpose & Motivation

MT-SDT was created to solve a critical inefficiency in cellular IoT: the high cost of establishing a full RRC connection for delivering tiny downlink packets. Prior to MT-SDT, if an IoT device in a power-saving state (like RRC_IDLE or RRC_INACTIVE) needed to receive data, the network had to page it, the device would perform a full RRC Connection Resume or Setup procedure, transition to RRC_CONNECTED, receive the data, and then go through another procedure to release the connection and return to idle/inactive. This entire cycle consumes significant signaling resources on the radio interface and in the core network, and more importantly, drains the device's battery for what could be a payload of just a few bytes.

The historical context lies in the evolution of cellular IoT from 2G/3G to LTE-M and NB-IoT, and now into 5G NR. While MO-SDT (for uplink) was introduced earlier, the downlink path remained inefficient. The motivation for MT-SDT in Rel-18 was to achieve symmetry and complete the "small data" optimization paradigm for 5G. It addresses the limitations of previous approaches where any downlink data, regardless of size, triggered a full connection establishment. This was a major barrier for applications like remote sensor actuation, firmware updates, or command-and-control for millions of devices, where network signaling load and device energy consumption are primary constraints.

By enabling MT-SDT, 3GPP allows network operators to support a vast number of IoT devices with infrequent downlink traffic in a scalable and sustainable manner. It reduces latency for downlink commands and optimizes radio resource utilization. This feature is a cornerstone for enabling truly massive Machine-Type Communications (mMTC) in 5G Advanced, supporting use cases in smart cities, industrial IoT, and asset tracking where devices are predominantly passive but occasionally need to be instructed or updated by the network.

Classification

Related approachesMO-SDT

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 9 changes

In Release 15, the MT-SDT (Mobile Terminated Small Data Transmission) function was newly introduced, allowing a UPF that supports the feature to report downlink data packet sizes per QoS flow. Specifically, based on local policy or an AMF indication, the SMF can provide Mobile Terminated Small Data Transmission Control Information in a BAR to request this reporting from the UPF when sending a Downlink Data Report.

  • CR to clarify non-codebook based PUSCH transmission TS 38.306CR0123
  • Flush HARQ buffer upon skipping a UL transmission TS 38.321CR0153
  • Correction to SIB1 transmission during handover TS 38.331CR0847
  • Small Corrections for System Information TS 38.331CR1124
  • Correction for SN terminated DRB To Be Setup in SN Addition Response TS 38.423CR0099
  • XnAP Correction of PDU Session Resource Setup Response Info – MN terminated TS 38.423CR0112

+ 3 more changes

Rel-16 30 changes

In Release 16, the MT-SDT (Mobile Terminated Small Data Transmission) function was newly introduced, allowing the SMF to provide Mobile Terminated Small Data Transmission Control Information to a supporting UPF to request reports on downlink data packet sizes. This enables efficient handling of small downlink data transmissions, such as those for IoT devices, based on local policy or an indication from the AMF. The feature integrates with the existing PFCP session management framework for data reporting.

  • Implementing confirmation of code block group based transmission TS 38.331CR1717
  • Correction on uplink transmission allowed without TA TS 38.300CR0343
  • Transmissions to the source that continue upon DAPS UL switching TS 38.300CR0353
  • Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability TS 38.306CR0501
  • CR on the Capability of PUCCH Transmissions for HARQ-ACK-38306 TS 38.306CR0521
  • Correction on Capability of two PUCCH transmission TS 38.306CR0542

+ 24 more changes

Rel-17 25 changes

In Release 17, the MT-SDT (Mobile Terminated Small Data Transmission) function was introduced, enabling a UPF that supports the feature to report downlink data packet sizes per QoS flow. Specifically, based on local policy or an AMF indication, the SMF can provide MT-SDT Control Information in a BAR to request this reporting from the UPF, facilitating efficient data handling for mobile-terminated small data sessions.

  • Introduction of Small Data Transmission for MAC spec TS 38.321CR1198
  • Parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA [NC-PRACH-SimulTx] TS 38.331CR3577
  • Missing transmission bandwidth configurations in XnAP [NR_FR1_35MHz_45MHz_BW] TS 38.423CR1021
  • Missing transmission bandwidth configurations in F1AP TS 38.473CR1124
  • Traffic usage reporting on Redundant Transmission at transport layer TS 29.244CR0591
  • Corrections for IIoT on simultaneous PUCCH and PUSCH transmission TS 38.300CR0477

+ 19 more changes

Rel-18 49 changes

In Release 18, the MT-SDT (Mobile Terminated Small Data Transmission) function was newly introduced, enabling the UPF to report downlink data packet sizes to support its activation. Specifically, if the UPF indicates support for the MT-SDT feature, the SMF can provide MD-SDT Control Information in a BAR to request the UPF to report the sum of DL Data Packets Size per QoS flow when sending a Downlink Data Report. This introduction was accompanied by enhancements to the triggering conditions and corrections to capability and data size reporting for the feature.

  • Introduction on MT-SDT TS 37.480CR0003
  • Introduction of MT-SDT TS 37.483CR0054
  • Introduction of MT-SDT in Stage-2 TS 38.300CR0711
  • Introduction of Mobile IAB TS 38.300CR0727
  • Introduction on MT-SDT TS 38.300CR0751
  • Introduction of MT-SDT and CG-SDT enhancement for MAC spec [CG-SDT-enh] TS 38.321CR1699

+ 43 more changes

Rel-19 4 changes

In Release 19, the MT-SDT (Mobile Terminated Small Data Transmission) function was enhanced by enabling the SMF to provide specific control information to a supporting UPF. Based on the grounding context, if the UPF indicates support for the MT-SDT feature, the SMF may provide the MD-SDT Control Information IE in a BAR to request the UPF to report the sum of DL Data Packets Size per QoS flow. This allows for more granular reporting and control of downlink small data traffic.

  • Correction on UE transmissions during Cell DRX TS 38.300CR1044
  • Clarification on simultaneous transmission capabilities in inter-band CA TS 38.306CR1403
  • Clarification on NR uplink transmission duty cycle TS 38.306CR1407
  • Correction on UE transmissions during Cell DRX TS 38.321CR2129

Explore further

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

Defining Specifications

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

SpecificationTitleRelease
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 37.480 vj00 E1 Interface General Aspects and Principles Rel-19
TS 37.483 vj10 E1 Application Protocol (E1AP) Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19