Mobile Terminated Small Data Transmission

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.

Key Features

• Enables downlink data delivery to UEs in RRC_INACTIVE state without full RRC connection resume
• Reduces signaling overhead and UE power consumption for infrequent network-initiated traffic
• Utilizes existing RRCResume procedure with piggybacked user data
• Supports both CP (Control Plane) and UP (User Plane) based small data transmission models
• Integrates with 5GC Network Triggered Service Request and RAN-based notification area paging
• Maintains AS security using the stored security context from the previous RRC_CONNECTED state

Evolution Across Releases

Defining Specifications