Description
Short Data Services (SDS) is a 3GPP service capability designed for the efficient transfer of small, sporadic data payloads, typically associated with Internet of Things (IoT) and Machine-Type Communication (MTC) applications. It provides mechanisms to send and receive data packets that are small in size (often a few tens to hundreds of bytes) and transmitted infrequently. The architecture supports SDS over both control plane and user plane, with a strong focus on minimizing signaling overhead and device power consumption.
How SDS works involves optimized procedures for data transfer. In control plane solutions, small data packets can be transported via Non-Access Stratum (NAS) signaling messages, allowing data transfer without establishing a full data radio bearer, which reduces signaling latency and overhead. For user plane, solutions like early data transmission (EDT) in LTE-M and NB-IoT allow data to be sent during the random-access procedure. Key network components include the MTC-IWF (for control plane SDS) and the core network functions (AMF, SMF, UPF) that handle the routing and policy for these small data packets. The service is tightly integrated with features like Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX) to maximize device battery life.
Its role is to serve as the underlying transport enabler for a vast array of IoT use cases, such as smart meters, asset trackers, and environmental sensors. By providing a network-native, optimized path for small data, SDS prevents the network from being overloaded with excessive signaling that would occur if these devices used standard data session procedures designed for smartphones. It allows the network to efficiently support a massive number of devices, making large-scale IoT deployments economically and technically feasible.
Purpose & Motivation
SDS was created to address the fundamental mismatch between traditional mobile broadband protocols and the requirements of IoT/MTC devices. Standard cellular data procedures involve significant signaling (e.g., service request, bearer setup) relative to the tiny payloads of IoT data, leading to inefficient network resource usage and high device power consumption. This made traditional cellular technology impractical for battery-operated sensors needing a decade-long lifespan.
The primary problem SDS solves is enabling efficient, network-friendly communication for devices that send small, bursty data. It was motivated by the explosive growth of the IoT market and the need to connect billions of low-cost, low-power devices to cellular networks. Historical context includes its introduction alongside other Cellular IoT (CIoT) features like NB-IoT and LTE-M in 3GPP Releases 13 and 14, which collectively aimed to make LTE networks IoT-ready.
It addresses the limitations of using SMS or full IP data sessions for IoT traffic. SMS can be expensive and lacks acknowledged delivery guarantees suitable for some applications, while full IP sessions are too signaling-heavy. SDS provides a standardized, optimized, and cost-effective middle ground, allowing operators to offer tailored IoT connectivity services. Its evolution is driven by the need to support more complex IoT scenarios, integrate with 5G core, and further enhance efficiency for massive machine-type communication (mMTC).
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (29 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Short Data Services (SDS) function was enhanced with the introduction of specific application type identifiers, a standardized location field, and fixes for the Interworking Function (IWF). It also established a payload size limit for standalone SDS over the signalling control plane and resolved a duplicated procedure name for MCData Group SDS.
- Introduction of SDS application type identifiers TS 23.282CR0079
- SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3 TS 23.282CR0087
- IWF SDS fix TS 23.283CR0017
- IWF SDS fix TS 23.783CR0017
- Payload size limit for standalone SDS over signalling control plane TS 23.282CR0102
- Duplicated procedure name for MCData Group SDS TS 23.282CR0107
In Release 16, the Short Data Service (SDS) function for Mission Critical Data (MCData) was enhanced with new capabilities including functional alias support, the addition of location information to SDS messages, and support for emergency and imminent peril scenarios for one-to-one, group, and off-network SDS sessions. It also introduced specific procedures for off-network SDS using the MCData message store and added interworking between MCData SDS and GSM-R SMS.
- Add interworking between MCData SDS and GSM-R SMS TS 22.282CR0027
- Generic SDS procedure with MCData message store TS 23.282CR0127
- Off-network SDS with MCData message store TS 23.282CR0136
- Functional alias support for Short Data Service (SDS) TS 23.282CR0147
- Emergency support for one-to-one SDS TS 23.282CR0171
- Emergency and imminent peril support for group SDS TS 23.282CR0172
+ 5 more changes
In Release 17, the Short Data Service (SDS) for Mission Critical Data saw specific enhancements, including the introduction of SDS addressing based on functional alias and the addition of application priority capabilities for on-network data requests. The release also finalized corrections and enhancements for one-to-one and group SDS information elements, off-network SDS procedures, and the functional model for IP connectivity. Furthermore, it formally added and specified the required interworking support between MCData SDS and GSM-R SMS.
- SDS addressing based on functional alias TS 23.282CR0163
- Enhancing SDS data requests with application priority capabilities in on-network mode TS 23.282CR0191
- Add enhancements for interworking of MCData SDS with GSM-R SMS TS 23.283CR0050
- Add enhancements for interworking of MCData SDS with GSM-R SMS TS 23.783CR0050
- Corrections to the one-to-one SDS information elements TS 23.282CR0216
- Corrections to the one-to-one SDS and FD communication upgrade flows TS 23.282CR0218
+ 5 more changes
In Release 18, the SDS function was enhanced to support **ad hoc group data communication** for SDS and file distribution services within MCData, as defined by new information flows and procedures. This builds upon the existing SDS capabilities for conveying limited-size, variable-content messages with features like read receipts, location fields, and message threading. The release also formally added support for interworking between MCData SDS and GSM-R SMS.
- Information flows and procedures for the ad hoc group data communication for SDS and FD services of MCData TS 23.282CR0304
Explore further
Broader topics and technologies where SDS plays a role.
Defining Specifications
3GPP specifications that define or reference SDS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.282 vj00 | Mission Critical Data Service Requirements | Rel-19 |
| TS 23.282 vk00 | MCData Functional Architecture & Info Flows | Rel-20 |
| TS 23.283 vk00 | Mission Critical Communication Interworking | Rel-20 |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 |
| TS 23.784 vg00 | Discreet Listening for Mission Critical Services | Rel-16 |
| TR 23.799 ve00 | Study on Next Generation System Architecture | Rel-14 |
| TS 24.582 vj00 | MCData Media Plane Control Protocols | Rel-19 |
| TS 24.883 vg00 | MCPTT Interworking with LMR Systems | Rel-16 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.880 vf10 | Security Study for Enhanced Mission Critical Services | Rel-15 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |
