Description
A Radio Access Bearer (RAB) is a fundamental concept in UMTS and the early phases of LTE, representing a service provided by the Radio Access Network (UTRAN or E-UTRAN) for the transfer of user data between the User Equipment (UE) and the Core Network (CN). It is not a physical channel but a logical association that defines a set of quality of service (QoS) parameters for a specific data flow. The RAB is essentially the concatenation of a Radio Bearer (RB) over the Uu (air) interface and an Iu Bearer (for UMTS) or S1 Bearer (for LTE) over the respective RAN-CN interface.
The establishment, modification, and release of a RAB are controlled by the Core Network, specifically the Serving GPRS Support Node (SGSN) in UMTS or the Mobility Management Entity (MME) in LTE, via the RANAP (Iu interface) or S1-AP (S1 interface) protocols. When a PDP Context (UMTS) or EPS Bearer (LTE) is activated in the CN, it triggers the setup of a corresponding RAB. The CN signals the desired QoS profile (e.g., traffic class, guaranteed bit rate, maximum bit rate, transfer delay) to the RAN. The RAN's Radio Resource Management (RRM) function, specifically Radio Admission Control (RAC), then determines if sufficient radio resources are available to support the requested profile. If admitted, the RAN configures the appropriate transport channels and physical channels to realize the Radio Bearer part of the RAB.
A single UE can have multiple RABs simultaneously, each supporting a different service with its own QoS requirements. For instance, one RAB could be for a conversational voice call (high priority, low delay), while another is for background email traffic (low priority). The RAB sublayer in the protocol stack is responsible for mapping higher-layer data packets onto the configured transport channels while respecting the QoS attributes. This includes functions like traffic policing, scheduling priority, and handling transparent vs. non-transparent data transfer modes. The RAB is therefore the key entity that enables the UMTS/LTE network to offer differentiated services over the shared radio medium.
Purpose & Motivation
The RAB was created to provide a standardized, QoS-aware mechanism for transporting user data across the radio access network, which was a significant evolution from the primarily best-effort nature of 2G GPRS. It solved the problem of how to efficiently support diverse services (voice, video streaming, web browsing) with vastly different requirements on a single, packet-switched infrastructure. The RAB concept allows the network to treat different data flows from the same user with appropriate priority and resource allocation.
Historically, circuit-switched networks dedicated a physical channel (a timeslot) to a voice call, guaranteeing quality but wasting resources during silence. Packet-switched 2.5G introduced mobility but lacked sophisticated QoS. The RAB, introduced with UMTS, was a cornerstone of the All-IP vision, enabling true multimedia convergence. It provides the contractual interface between the Core Network, which knows the subscriber's service profile, and the Radio Access Network, which manages the scarce and variable radio resources. By defining clear QoS parameters, it allows for efficient radio admission control, scheduling, and handover procedures that maintain service continuity. Its evolution into the EPS Bearer model in LTE/EPC refined this concept further with stricter binding to IP flows.
Key Features
- Logical channel with a defined QoS profile (Traffic Class, Bit Rates, Delay, BER).
- Established, modified, and released by Core Network signaling (RANAP/S1-AP).
- Comprises a Radio Bearer (over Uu) and an Iu/S1 Bearer (over RAN-CN interface).
- Supports multiple simultaneous instances per UE for multi-service operation.
- Enables Radio Admission Control (RAC) and radio resource scheduling based on QoS.
- Fundamental to service differentiation and guaranteed performance over the air interface.
Evolution Across Releases
Introduced as the core QoS mechanism for UMTS. Defined four Traffic Classes: Conversational, Streaming, Interactive, and Background. Established the RAB setup procedure via RANAP between the RNC and SGSN, linking a PDP Context to specific radio resources.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.153 | 3GPP TS 23.153 |
| TS 23.205 | 3GPP TS 23.205 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.815 | 3GPP TS 23.815 |
| TS 23.910 | 3GPP TS 23.910 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.410 | 3GPP TS 25.410 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.415 | 3GPP TS 25.415 |
| TS 25.914 | 3GPP TS 25.914 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 25.993 | 3GPP TS 25.993 |
| TS 26.102 | 3GPP TS 26.102 |
| TS 26.202 | 3GPP TS 26.202 |
| TS 26.233 | 3GPP TS 26.233 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 29.212 | 3GPP TS 29.212 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.404 | 3GPP TR 32.404 |
| TS 32.405 | 3GPP TR 32.405 |
| TS 32.410 | 3GPP TR 32.410 |
| TS 32.863 | 3GPP TR 32.863 |
| TS 34.109 | 3GPP TR 34.109 |
| TS 34.114 | 3GPP TR 34.114 |
| TS 36.509 | 3GPP TR 36.509 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.544 | 3GPP TR 37.544 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 37.902 | 3GPP TR 37.902 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 43.129 | 3GPP TR 43.129 |
| TS 44.060 | 3GPP TR 44.060 |