Radio Bearer Control

Description

Radio Bearer Control is a core component of the Radio Resource Management (RRM) layer, primarily executed by the Radio Network Controller (RNC) in UMTS and the gNB in LTE and NR. It manages the lifecycle of radio bearers, which are logical connections mapped onto physical radio resources. A radio bearer is characterized by a set of attributes including traffic class, guaranteed bit rate, maximum bit rate, delivery order, and SDU error ratio, which define its QoS profile. RBC functions include bearer establishment, reconfiguration, and release, triggered by events such as session initiation, handover, or changes in network conditions or service requirements.

The process begins when the Core Network, via the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF), requests a bearer with specific QoS parameters for a user session. The RBC function in the RAN evaluates the current radio resource availability, UE capabilities, and the requested QoS to determine if the bearer can be admitted. If admitted, it configures the appropriate Layer 2 protocols (RLC, MAC) and physical layer parameters to realize the bearer. This involves allocating logical channel identifiers, configuring RLC modes (Transparent, Unacknowledged, Acknowledged), and setting up scheduling parameters in the MAC layer.

During an active session, RBC continuously monitors the bearer's performance. It may initiate bearer reconfiguration in response to mobility events (e.g., handover), changes in traffic patterns, or network load conditions. For example, during a handover from one cell to another, RBC re-establishes the bearer in the target cell, ensuring service continuity with minimal interruption. It also handles the release of bearers when a session ends or due to radio link failure. The interaction between RBC and other RRM functions like Admission Control, Packet Scheduling, and Handover Control is critical for efficient radio resource utilization and maintaining end-to-end QoS across the RAN and core network.

Purpose & Motivation

Radio Bearer Control exists to manage the logical transport channels that carry user data and control signaling over the air interface in a resource-constrained and dynamic radio environment. Its primary purpose is to translate service-level QoS requirements, received from the core network, into specific radio resource configurations that can be implemented by the RAN. Without RBC, the network would be unable to guarantee differentiated service qualities for diverse applications like voice calls, video streaming, or web browsing, leading to poor user experience and inefficient use of spectrum.

The concept was introduced in 3G UMTS (Release 99) to address the limitations of 2G GSM, which offered primarily circuit-switched voice with limited data capabilities. GSM lacked a sophisticated, dynamic bearer management system for packet data. RBC provided the necessary framework to support multiple concurrent bearers with different QoS profiles for a single user, enabling true multimedia services. It solved the problem of efficiently multiplexing traffic with varying delay, loss, and throughput requirements onto shared physical channels, a cornerstone for the evolution towards all-IP networks and mobile broadband.

As networks evolved to LTE and 5G NR, the role of RBC remained essential but its implementation became more distributed and integrated with other RAN functions. The move from a centralized RNC in UMTS to a distributed eNB/gNB architecture required RBC functionality to be embedded within the base station, enabling faster decision-making and adaptation to rapid channel variations. This evolution was motivated by the need for lower latency, higher data rates, and support for a vastly expanded set of services and use cases in 4G and 5G.

Key Features

• Bearer Establishment and Configuration: Creates and configures radio bearers with specific QoS attributes like traffic class, bit rates, and error tolerance.
• Bearer Reconfiguration: Dynamically modifies bearer parameters during active sessions in response to handover, traffic changes, or network conditions.
• Bearer Release: Terminates radio bearers upon session completion or radio link failure, freeing up resources.
• QoS Mapping and Enforcement: Translates core network QoS parameters (QCI, 5QI) into RAN-specific configurations for scheduling and link adaptation.
• Interaction with RRM Functions: Coordinates closely with Admission Control, Packet Scheduling, and Handover Control for holistic resource management.
• Support for Multiple Bearers per UE: Manages several dedicated and default bearers simultaneously for a single user equipment to support concurrent services.

Evolution Across Releases

Defining Specifications