Data Radio Bearer

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.

Key Features

• Logical transport channel for user plane data over the Uu interface
• Configured via RRC signaling with specific PDCP, RLC, and MAC parameters
• Maps one or more QoS Flows (5G) or SDFs (LTE) with similar QoS requirements
• Associated with a 5QI (5G) or QCI (LTE) defining scheduling priority and packet treatment
• Supports dynamic setup, modification, and release based on service demand and mobility
• Enables radio-level enforcement of QoS and network slicing performance isolation

Evolution Across Releases

Defining Specifications