Glossary term · Protocol

SDAP

Service Data Adaptation Protocol

Protocol →

SDAP is a 5G NR protocol layer that manages QoS flows by mapping them to data radio bearers and marking packets with QoS Flow Identifiers for service differentiation and network slicing support.

Introduced
Rel-15
Specifications
8 specs
Category
Protocol
Introduced
Rel-15
Specifications
8 specs
SDAP Description Purpose Related Classification Detected Changes Specifications

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

Part ofPDCP
Related approachesQFI

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 4 changes
  • Miscellaneous corrections for SDAP TS 37.324CR0006
  • Support of ongoing re-mapping on source side during SDAP mobility TS 38.300CR0160
  • Support of ongoing re-mapping on source side during SDAP mobility TS 38.463CR0023
  • Miscellaneous corrections to SDAP TS 37.324CR0007
Rel-16 2 changes
  • Capture latest agreements on SDAP TS 37.324CR0016
  • Correction of PQFI terminology in SDAP TS 37.324CR0020

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.

SpecificationTitleRelease
TS 26.114 vk00 Multimedia Telephony Service for IMS Rel-20
TS 26.804 vk00 5G Media Streaming Architecture Extensions Rel-20
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19
TS 37.324 vj00 Service Data Adaptation Protocol (SDAP) Rel-19
TS 37.483 vj30 E1 Application Protocol (E1AP) Specification Rel-19
TS 38.300 vj30 NR and NG-RAN Overall Description Rel-19
TS 38.306 vj30 NR UE Radio Access Capability Parameters Rel-19
TS 38.463 vj00 E1 Application Protocol (E1AP) Rel-19