Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

SDS

Short Data Services

Services →

SDS is a service that enables efficient transmission of small, infrequent data packets for IoT devices, optimizing network signaling and power consumption for long battery life.

Introduced
Rel-14
Where
Services › IMS
Specifications
11 specs
SDS Description Purpose What changed Neighbours Detected Changes Specifications

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).

What changed in its specifications

The latest release-to-release comparison of specifications that define SDS. Each summary describes the whole specification, not only this term.

TS 22.282Rel-16 → Rel-17

Rel-17 brings only minor changes to TS 22.282: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 22.282 →
TS 23.282Rel-18 → Rel-19

Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.

Full comparison in TS 23.282 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-15 6 changes
  • 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
Rel-16 11 changes
  • 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

Rel-17 11 changes
  • 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

Rel-18 1 change
  • Information flows and procedures for the ad hoc group data communication for SDS and FD services of MCData TS 23.282CR0304

Defining Specifications

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

SpecificationTitleRelease
TS 22.282 vj00 Mission Critical Data Service Requirements Rel-19 read
TS 23.282 vk31 Mission Critical Data Architecture Rel-20 read
TS 23.283 vk10 Mission Critical Communication Interworking Rel-20 read
TR 23.783 vi00 Technical Report on Mission Critical Services over 5GS Rel-18 read
TS 23.784 vg00 Discreet Listening for Mission Critical Services Rel-16 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 read
TS 24.582 vj00 MCData Media Plane Control Protocols Rel-19 read
TS 24.883 vg00 MCPTT Interworking with LMR Systems Rel-16 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read