Description
The Service Data Adaptation Protocol (SDAP) is a sublayer within the 5G New Radio (NR) user plane protocol stack, residing above the Packet Data Convergence Protocol (PDCP) and below the application layer. It operates transparently between the gNB (Next Generation NodeB) and the User Equipment (UE). Its primary architectural role is to act as an adaptation layer for the QoS framework defined for the 5G System (5GS). Unlike in LTE, where QoS was tied to EPS bearers, 5G introduces a more flexible QoS model based on QoS Flows. The SDAP entity is configured per Protocol Data Unit (PDU) Session and per data radio bearer (DRB).
SDAP works by processing downlink packets from the core network's User Plane Function (UPF) and uplink packets from the UE's higher layers. Each IP packet is associated with a specific QoS Flow Identifier (QFI). The core function of SDAP is to map these QoS flows onto the appropriate data radio bearers. A single DRB can carry packets from multiple QoS flows if they share similar QoS characteristics, a process known as QoS flow aggregation. Conversely, a QoS flow with stringent requirements might be mapped to a dedicated DRB. The SDAP entity in the gNB performs this mapping in the downlink, while the UE's SDAP entity performs the reverse mapping in the uplink based on rules received from the network.
A key operational mechanism is the marking of packets with QFI headers. In the downlink, the gNB's SDAP layer adds a small SDAP header to the packet, which includes the QFI and potentially an RQI (Reflective QoS Indicator) and/or an RDI (Reflective QoS Indication for Delay Critical GBR). This header allows the UE to identify the QoS flow to which the packet belongs for proper uplink treatment. For reflective QoS, the RQI bit instructs the UE to create a mirroring QoS rule for the uplink based on the observed downlink traffic, reducing signaling overhead. The SDAP layer is also responsible for handling the establishment, modification, and release of SDAP entities and their associated mappings via RRC signaling.
Purpose & Motivation
SDAP was created to support the revolutionary QoS model of the 5G System, which was designed to cater to an unprecedented variety of services—from enhanced mobile broadband (eMBB) to ultra-reliable low-latency communications (URLLC) and massive IoT (mIoT). The previous 4G EPS bearer model was relatively rigid, binding QoS parameters to a bearer tunnel end-to-end. This made dynamic service creation and fine-grained traffic differentiation cumbersome. The 5G QoS model decouples the QoS flow (a service-level concept) from the data radio bearer (a transport-level concept), enabling greater flexibility and efficiency.
The protocol exists to solve the problem of efficiently mapping these abstract QoS flows onto the physical radio resources (DRBs) while maintaining the integrity of QoS enforcement. It allows the network to optimize radio resource usage by aggregating multiple similar flows onto one bearer or isolating critical flows on dedicated bearers without requiring core network involvement for every adjustment. Furthermore, SDAP enables network slicing by providing a clear demarcation point where slice-specific QoS policies, received from the core network, can be applied to the radio bearer mapping. Its introduction was motivated by the need for a protocol mechanism that could realize the advanced 5G QoS framework, ensuring that diverse latency, reliability, and bandwidth promises could be technically enforced on the air interface.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (32 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the SDAP (Service Data Adaptation Protocol) was newly introduced as a standalone protocol specification, TS 37.324, to handle the mapping of QoS flows to data radio bearers in the 5G NR user plane. The release included foundational support for SDAP mobility procedures, specifically enabling ongoing QoS flow re-mapping on the source network side during handover. Additionally, this initial specification underwent several miscellaneous corrections to solidify the protocol's functionality.
- Delay budget report and MAC CE adaptation for NR for TS 38.300 TS 38.300CR0042
- Delay budget report and MAC CE adaptation for NR for TS 38.306 TS 38.306CR0013
- Miscellaneous corrections for SDAP TS 37.324CR0006
- Correction to description of bandwidth adaptation TS 38.300CR0051
- Clarification of PDCP functionality TS 38.300CR0053
- Correction of BWP adaptation TS 38.300CR0107
+ 8 more changes
In Release 16, the SDAP specification saw refinements including clarifications on PDCP duplication procedures for features like Industrial IoT and interactions with the E1AP interface. The release also introduced corrections to specific terminologies, such as PQFI, and provided updates to ensure proper handling during RRC reconfiguration and bandwidth adaptation. These changes built upon the foundational role of SDAP in managing QoS flows and mapping for the 5G user-plane protocol stack.
- Capture latest agreements on SDAP TS 37.324CR0016
- Correction of PQFI terminology in SDAP TS 37.324CR0020
- Stage-2 CR for clarifications of Rel-16 PDCP Duplication TS 38.300CR0263
- PDCP SN issue for EPC to 5GC handover TS 38.300CR0347
- Correction on Industrial IOT Rel-16 PDCP duplication for E1AP TS 38.463CR0566
- Clarification on pdcp-Duplication at RRC Reconfiguration TS 38.300CR0222
+ 3 more changes
In Release 17, the SDAP function was updated to introduce support of User Plane IP for EPC connected architectures using NR PDCP. Additionally, enhancements were made to extend the PDCP Discard Timer over the E1 interface and to implement PDCP COUNT reset in the CU-UP for inter-gNB-DU Handover scenarios.
In Release 18, the SDAP function was updated to define the protocol stack for an MTSI UE, which notably excludes 3GPP Layer 2 protocols when using fixed access. The release also introduced IANA registration procedures for data channel sub-protocols used within the SDAP context. Furthermore, corrections and clarifications were made regarding PDCP duplication handling for specific multi-connectivity and relay scenarios.
- Protocol Stack for MTSI UE TS 26.114CR0529
- IANA registration for data channel sub-protocols TS 26.114CR0537
- Support of PDCP SN Gap Report TS 37.483CR0135
- Correction to PDCP duplication description for L2 MP using SL relay or N3C indirect path TS 38.300CR0989
- Correction on pdcp-DuplicationSRB for NR-DC TS 38.306CR1303
In Release 19, the key update for the Service Data Adaptation Protocol (SDAP) was its introduction to support the new NR Femto Architecture, as detailed in the corresponding protocol aspects. This integration extends SDAP's role in managing QoS flows and marking packets to the femto cell deployment scenario. The specification TS 37.324 remains the defining document for the SDAP protocol within the 3GPP system architecture.
- Introduction of NR Femto Architecture and Protocol Aspects TS 38.300CR1035
Explore further
Broader topics and technologies where SDAP plays a role.
Defining Specifications
3GPP specifications that define or reference SDAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 37.324 vj00 | Service Data Adaptation Protocol (SDAP) | Rel-19 |
| TS 37.483 vj10 | E1 Application Protocol (E1AP) | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.463 vj00 | E1 Application Protocol (E1AP) | Rel-19 |