RA-SDT

Random Access-based Small Data Transmission

IoT →
Introduced in Rel-17

RA-SDT is a 3GPP NR feature that enables devices to transmit small data packets directly during the Random Access procedure, avoiding a full connection state to reduce signaling and power consumption.

Category
IoT
Introduced
Rel-17
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
RA-SDT Description Purpose Detected Changes Specifications

Description

Random Access-based Small Data Transmission (RA-SDT) is a mechanism defined in 3GPP Release 17 for New Radio (NR) that allows a User Equipment (UE), typically an IoT device, to transmit a limited amount of uplink data while remaining in RRC Inactive state. It leverages the existing Physical Random Access Channel (PRACH) procedure as a carrier for both the access request and the initial data payload. The core idea is to piggyback small data packets on the messages of the random access process, thereby avoiding the extensive signaling exchange required to transition to RRC Connected state, perform service request procedures, and then release the connection back to inactive.

Architecturally, RA-SDT integrates with the 3-step and 4-step contention-based random access procedures defined for NR. In the 3-step approach (MsgA), the UE combines the traditional preamble (Msg1) and connection request (Msg3) into a single transmission. RA-SDT can be implemented by allowing the UE to include a small data payload within this MsgA. The gNB's response (MsgB) then includes not only the contention resolution and uplink grant but also the acknowledgment for the transmitted data. For the 4-step approach, data can be included in Msg3. Key components enabling this are enhancements to the RRC Inactive state context, which is stored in both the UE and the network (last serving gNB and AMF), allowing the gNB to validate and process the data without full RRC setup.

How it works involves pre-configuration and resource allocation. The network broadcasts system information indicating support for RA-SDT and its associated parameters, such as the maximum transport block size for data in MsgA/Msg3. A UE in RRC Inactive state with a small amount of data to send and a valid Inactive state context can initiate an RA-SDT procedure. It selects the appropriate preamble resource configured for SDT and transmits MsgA (or Msg1) including the data. The gNB, recognizing the preamble or the content of MsgA as an SDT attempt, uses the stored UE context to authenticate, decipher the data, and forward it to the UPF via the last serving NG-RAN node. The UE may then return to Inactive state immediately after receiving a successful MsgB (or Msg4), completing the transaction with minimal state transitions.

Purpose & Motivation

RA-SDT was created to address a critical inefficiency in cellular IoT and massive Machine-Type Communication (mMTC) scenarios: the disproportionate signaling overhead and energy consumption associated with transmitting very small, infrequent data packets. Traditional procedures require a full RRC connection setup and release for even a single data packet, which can involve 10-20 signaling messages. This 'signaling storm' congests the network and drains the battery of constrained IoT devices, which are designed for years of operation on a single battery charge.

The motivation stems from the evolution of 5G to support a wider range of use cases, including ultra-reliable low-latency communication (URLLC) and massive IoT. Prior to Rel-17, mechanisms like Early Data Transmission (EDT) in LTE-M and NB-IoT addressed similar issues but were limited to those technologies. RA-SDT brings this optimization to the mainstream NR spectrum, enabling efficient support for a new class of NR-light devices (often called 'RedCap' – Reduced Capability). It solves the problem of network resource wastage and poor device battery life for applications like sensor readings, smart meter updates, or wearable health monitors that generate payloads of only a few bytes periodically.

By allowing data transmission within the RRC Inactive state, RA-SDT directly tackles the limitations of the binary connected/inactive model for sporadic traffic. It reduces latency (by skipping connection setup), minimizes control plane load on the gNB and core network, and significantly extends device battery life by avoiding the high-power operations associated with full connection states. This makes NR a more viable and efficient technology for the scaling Internet of Things.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes

In Release 17, the RA-SDT (Random Access-based Small Data Transmission) function was introduced, allowing a UE to initiate a small data transmission procedure via random access. The release included subsequent corrections to refine the RA-SDT and CG-SDT procedures, as indicated by the Change Request titles. The provided specification text details that a UE can select configured Random Access resources for RA-SDT and uses a specific rsrp-ThresholdSSB during the procedure.

Rel-18 2 changes

In Release 18, the RA-SDT function was enhanced to introduce beam failure recovery procedures specific to small data transmission. This allows a UE to recover from a beam failure during an ongoing RA-SDT procedure. The specifications also addressed configuration details, such as the scenario where an SDT BFR timer is not configured.

  • Introduction of beam failure recovery for SDT in Rel-18 [RA-SDT_BeamFailure] TS 38.321CR1712
  • SDT BFR timer being not configured [RA-SDT_BeamFailure] TS 38.321CR1814

Explore further

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

Defining Specifications

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

SpecificationTitleRelease
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.