RBC

Radio Bearer Control

Radio Access Network →
Introduced in R99 Also in: Radio Access Network

RBC is the Radio Resource Management function responsible for establishing, maintaining, configuring, and releasing radio bearers with appropriate QoS to carry user data and signaling.

Category
Radio Access Network
Introduced
R99
Where
Services
Also touches
1 segments
Specifications
7 specs
RBC Description Purpose Detected Changes Specifications

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.

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 5 changes

In Release 15, the Radio Bearer Control (RBC) function was updated to introduce support for the New Radio Access Technology, fundamentally expanding its scope beyond E-UTRAN. This included enhancements for connection re-establishment procedures in the control plane and the introduction of specific mechanisms for UE contention resolution in NB-IoT without requiring an RRC response message. Additionally, improvements were made to enable Multimedia Broadcast Multicast Service (MBMS) bearer event notifications and to manage UE radio access capability size reduction.

  • Introduction of New Radio Access Technology in TS 36.300 TS 36.300CR0998
  • Enabling MBMS Bearer Event Notification TS 36.300CR1138
  • Missing description of RRC Connection Re-establishment for the Control plane TS 36.300CR1094
  • Introduction of support for MAC PDU containing UE contention resolution identity MAC control element without RRC response message in NB-IoT TS 36.300CR1102
  • UE Radio Access Capability Size Reduction TS 36.300CR1162
Rel-16 2 changes

In Release 16, the RBC function was enhanced by introducing the UE Radio Capability Mapping procedure for EN-DC. Additionally, it specified the handling of UE Radio Capability for Paging in NB-IoT and eMTC technologies.

  • Introducing UE Radio Capability Mapping procedure for EN-DC TS 36.300CR1314
  • Handling of UE Radio Capability for Paging in NB-IoT and eMTC TS 36.300CR1263
Rel-18 1 change

In Release 18, the Radio Bearer Control (RBC) function was enhanced to support a multiuser talker control use case. This specifically introduced support for a configurable initial talker permission, allowing the network to manage which user equipment (UE) is initially granted bearer resources for uplink transmission in a session. This update provided more flexible control over the connection-oriented bearer service establishment within the 3GPP system.

  • Changes to Critical Support Applications Multiuser talker control use case to support configurable initial talker permission TS 22.989CR0006
Rel-19 2 changes

In Release 19, the Radio Bearer Control (RBC) function was enhanced to support Multiuser talker control use cases, extending its management of active communications and logical associations. This was informed by an updated gap analysis for railway emergency alert, multi-talker control, authorization, and arbitration, refining RBC's procedures for connection-oriented bearer services and admission control within the 3GPP system.

  • Enhancement of Multiuser talker control related use cases TS 22.989CR0020
  • Update of gap analysis of railway emergency alert, multi-talker control, authorisation of communication, arbitration use cases TS 22.989CR0029
Rel-20 1 change

In Release 20, the RBC function was enhanced to support a new use case involving the merging of two multi-train voice communications by a Train Controller, a ground-based FRMCS user. This introduced specific procedures for bearer control to manage the simultaneous active communications and their associated bearers during such a merge event. The update ensured these new operational scenarios were supported within the 3GPP system's connection-oriented bearer service framework.

  • New use cases: Merging of two multi-train voice communications by Train Controller (Ground FRMCS user) TS 22.989CR0033

Explore further

Broader topics and technologies where RBC plays a role.

Defining Specifications

3GPP specifications that define or reference RBC, 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
TR 22.889 vh40 FRMCS Study; Stage 1 Rel-17
TR 22.989 vk30 FRMCS Analysis and Requirements Rel-20
TS 23.050 v1100 UMTS Network Principles and Architecture R99
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19