DRB

Data Radio Bearer

Radio Access Network →
Introduced in Rel-8 Also in: Services, Testing

DRB is a logical channel between a user device and a base station that carries user data traffic with specific quality of service treatment in LTE and 5G networks.

Category
Radio Access Network
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
16 specs
DRB Description Purpose Related Classification Detected Changes Specifications

Description

A Data Radio Bearer (DRB) is a fundamental construct in the radio protocol stack of LTE (E-UTRAN) and 5G NR (NG-RAN). It represents a logical connection or "pipe" over the air interface (Uu) specifically dedicated to transporting user plane data for a particular service or application flow. Each DRB is configured with a specific set of protocol layers and parameters that define how data is processed, protected, and transmitted between the UE and the Radio Access Network (RAN) node—the eNodeB in LTE or the gNB in 5G NR. The DRB is the point where QoS differentiation is physically enforced on the radio link.

The establishment and configuration of a DRB are controlled by the RAN node via RRC (Radio Resource Control) signaling. When a UE initiates a data session (a PDU Session in 5G or an EPS Bearer in LTE), the Core Network (5GC or EPC) requests the setup of a QoS flow (5G) or an EPS bearer with specific QoS characteristics (QCI/5QI, ARP, GBR, etc.). The RAN node translates this request into the configuration of one or more DRBs. A key function is QoS mapping: the RAN maps multiple QoS flows (in 5G) or Service Data Flows (in LTE) that share similar QoS requirements onto a single DRB. Each DRB is associated with a specific 5QI/QCI value, which dictates its treatment in terms of scheduling priority, packet delay budget, and error loss rate.

Technically, a DRB is realized through the configuration of the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) layers. PDCP provides header compression, ciphering, and integrity protection. RLC handles segmentation, concatenation, and error correction through ARQ. MAC performs scheduling, logical channel prioritization, and multiplexing of multiple DRBs (and SRBs) onto the shared transport channels. The physical layer (PHY) then transmits the data over the air. The DRB is identified by a DRB ID, and its lifecycle—setup, modification (e.g., for handover or QoS change), and release—is managed dynamically to match user data activity and mobility events, ensuring efficient use of radio resources while meeting the required service quality.

Purpose & Motivation

The DRB concept was introduced with LTE in 3GPP Release 8 to provide a flexible and efficient mechanism for delivering IP-based services with guaranteed Quality of Service (QoS) over the radio link. It addressed limitations of previous 3G systems where the mapping between core network bearers and radio channels was less flexible. The primary problem it solves is the efficient translation of core network QoS requirements into concrete radio resource allocation and treatment.

In pre-LTE systems, radio bearers were often tied more rigidly to specific services. The DRB, coupled with the QCI (QoS Class Identifier) framework, created a standardized, granular way to apply different packet forwarding behaviors (scheduling, queue management, etc.) based on service type (e.g., voice, video, web browsing). This enables network operators to prioritize latency-sensitive traffic like VoIP over best-effort traffic, improving user experience. Furthermore, the DRB's dynamic nature allows the network to establish bearers on-demand as services are activated, conserving radio resources when not needed. In 5G NR, the purpose evolved to support an even more flexible QoS model with QoS Flows. The DRB acts as the RAN's container for these flows, allowing efficient aggregation and reducing signaling overhead. It is a critical enabler for network slicing at the radio level, as different slices can be supported by different sets of DRBs with distinct QoS profiles, isolating performance between slices.

Classification

Related approachesSRB

Release Timeline

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 3 changes

In Release 15, specific procedures for DRB handling were enhanced, including the delivery of stored PDCP SDUs for UM DRB during PDCP re-establishment. Corrections were also made to the PDCP re-establishment procedure specifically for AM DRB. Furthermore, the release introduced a notification mechanism for the default DRB over the E1 interface.

  • Deliver stored PDCP SDUs for UM DRB at PDCP re-establishment TS 36.323CR0241
  • Correction on the PDCP re-establishment for AM DRB TS 38.323CR0025
  • CR to 38.460 on notification for default DRB over E1 TS 38.460CR0014
Rel-16 3 changes

In Release 16, specific corrections and clarifications were made to DRB handling procedures within the PDCP layer. These included defining the correct behavior for LTE PDCP re-establishment for UM DRBs when the t-Reordering timer is active and specifying the proper receive operation when both EHC (Header Compression) and out-of-order delivery are configured for a DRB. Additionally, a correction was provided for the handling of a suspended AM DRB during PDCP re-establishment.

  • CR on LTE PDCP re-establishment for UM DRB when t-Reordering is used TS 36.323CR0291
  • Correction on receive operation when both EHC and out-of-order delivery are configured for a DRB TS 38.323CR0050
  • Correction on suspended AM DRB in PDCP re-establishment TS 38.323CR0074

Explore further

Broader topics and technologies where DRB plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 26.114 vj10 IMS Multimedia Telephony Media Handling Rel-19
TR 33.853 vh00 Study on User Plane Integrity Protection Rel-17
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.314 vj00 E-UTRA Radio Measurements Specification Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 36.360 vj00 LTE-WLAN Aggregation Adaptation Protocol Rel-19
TS 36.361 vj00 LWIP Encapsulation Protocol Specification Rel-19
TS 36.509 vh40 EPC Special UE Conformance Testing Functions Rel-17
TS 37.470 vj00 W1 Interface Introduction for ng-eNB Rel-19
TS 37.480 vj00 E1 Interface General Aspects and Principles Rel-19
TR 37.901 vf10 UE Application Layer Data Throughput Performance Rel-15
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.460 vj00 E1 Interface General Aspects and Principles Rel-19
TS 38.470 vj10 F1 Interface Introduction 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.