Description
Mobile Originated Small Data Transmission (MO-SDT) is a feature standardized in 3GPP Release 18, designed to efficiently handle sporadic, small data transmissions from IoT and other devices. It operates by allowing a User Equipment (UE) to send a limited amount of uplink data while remaining in the RRC_INACTIVE or RRC_IDLE state, thereby avoiding the signaling overhead and latency associated with transitioning to the RRC_CONNECTED state. This is achieved by encapsulating the data within specific signaling messages, such as a modified RRC Resume Request or a new small data transmission message, which are processed by the network without fully re-activating all user plane bearers.
The architecture involves coordination between the Radio Access Network (RAN) and the Core Network (CN). When a UE in RRC_INACTIVE has data to send, it can initiate MO-SDT if the data size and other conditions (like configured thresholds) are met. The UE includes the data payload in the initial access message sent to the gNB. The gNB, upon receiving this, can forward the data to the UPF via the last serving NG-RAN node's context or a new path, depending on the implementation. The Core Network, specifically the AMF and SMF, supports this by allowing the user plane to be briefly established or by using a pre-configured small data transmission resource.
Key components include the UE, which must support the MO-SDT procedures as per 3GPP specifications; the gNB, which handles the reception of the small data and its forwarding; and the Core Network functions (AMF, SMF, UPF) that manage the context and data routing. The procedure leverages stored UE context in the RAN (for INACTIVE state) to minimize signaling. MO-SDT's role is to reduce latency, signaling load, and power consumption for devices that primarily send small, infrequent data bursts, making it a cornerstone for efficient massive Machine-Type Communication (mMTC) in 5G and beyond.
Purpose & Motivation
MO-SDT was created to address the inefficiencies of traditional connection establishment for IoT and M2M devices that generate small, sporadic data packets. Prior to its introduction, a UE needing to send data had to perform a full RRC connection setup, involving multiple signaling exchanges, even for a few bytes of data. This process consumed significant battery power and network resources, which is unsustainable for massive-scale IoT deployments with billions of devices. The limitations of previous approaches, like always keeping devices in connected state or using inefficient signaling, led to high overhead and reduced network capacity.
The motivation stems from the growth of IoT applications, such as sensors, smart meters, and wearables, which require energy-efficient and network-friendly communication. 3GPP Release 18 introduced MO-SDT as part of broader enhancements for reduced capability (RedCap) devices and IoT optimization. It solves the problem of signaling storms and battery drain by enabling data transmission without state transitions, aligning with 5G goals of supporting diverse services with varying requirements. Historically, early IoT solutions in LTE used techniques like Power Saving Mode (PSM) or extended Discontinuous Reception (eDRX), but these still incurred overhead during data transmission; MO-SDT provides a more integrated and efficient solution within the 5G NR framework.
Key Features
- Enables uplink data transmission from RRC_INACTIVE or RRC_IDLE states
- Reduces signaling overhead by avoiding full RRC connection establishment
- Supports small data packets with size limits defined by network configuration
- Leverages stored UE context in RAN for fast processing
- Integrates with 5G Core Network for efficient data routing
- Enhances battery life for IoT devices by minimizing radio activity
Evolution Across Releases
Introduced MO-SDT with initial architecture allowing data transmission in inactive state using RRC signaling. Defined procedures in specs like 38.300 and 38.331, supporting basic small data transmission with network-controlled parameters and thresholds.
Defining Specifications
| Specification | Title |
|---|---|
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.306 | 3GPP TR 38.306 |
| TS 38.321 | 3GPP TR 38.321 |
| TS 38.331 | 3GPP TR 38.331 |