Description
Guaranteed Bit Rate (GBR) is a fundamental Quality of Service (QoS) attribute defined in 3GPP standards for EPS (Evolved Packet System) and 5GS (5G System). It applies to dedicated bearers (in EPS) or QoS Flows (in 5GS) that require a minimum level of bandwidth assurance from the network. When a bearer/flow is designated as GBR, the network performs Admission Control during its establishment: it checks if sufficient radio and transport resources are available to honor the requested GBR value. If resources are available, the network commits them, reserving capacity to ensure the bit rate is maintained for the duration of the session, barring exceptional conditions like radio link failure.
The GBR value is coupled with other QoS parameters such as the Maximum Bit Rate (MBR), which caps the peak rate, and the QoS Class Identifier (QCI or 5QI). The network, particularly the eNodeB/gNodeB and the core network's policy control (PCRF/PCF), continuously monitors the resource usage of GBR bearers. In congestion scenarios, resources allocated to GBR bearers are protected, while non-GBR traffic may be throttled. The enforcement of GBR happens primarily at the radio scheduler in the base station, which allocates time-frequency resources to meet the guaranteed rate for each active GBR bearer.
GBR bearers are typically used for real-time conversational services (e.g., Voice over LTE/5G, video calls) and real-time streaming services. The guarantee ensures low latency, jitter, and packet loss, providing a consistent user experience. In contrast, Non-GBR bearers are used for elastic traffic like web browsing or email, where the available bit rate can vary based on network load. The distinction between GBR and Non-GBR is a cornerstone of the 3GPP QoS model, enabling the network to efficiently multiplex traffic with diverse requirements while meeting strict service level agreements.
Purpose & Motivation
GBR was introduced to support real-time, delay-sensitive applications over packet-switched mobile networks. Early mobile data services (e.g., basic GPRS) offered "best-effort" service, which was insufficient for voice, video telephony, or live streaming, as these applications suffer severely from variable throughput and latency.
The creation of GBR as a QoS parameter solved this by enabling the network to provide resource assurance. It allows operators to offer Service Level Agreements (SLAs) for specific applications or user tiers. From a technical perspective, GBR motivates the necessary resource reservation and admission control mechanisms within the RAN and core network. It addresses the limitation of stateless, best-effort IP routing by introducing a stateful, connection-oriented QoS model within the packet core, ensuring that real-time services can coexist with background traffic without degradation. This was crucial for the convergence of all services onto a single IP-based access network, a key goal of EPS and 5GS.
What changed in its specifications
The latest release-to-release comparison of specifications that define GBR. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-8 brings only minor changes to TS 23.202: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.202 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference GBR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 read |
| TS 23.202 vj00 | CS Bearer Services Architecture in UMTS | Rel-19 read |
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.910 v550 | CS Bearer Services in UMTS | Rel-5 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 26.348 vj00 | xMB Interface Specification | Rel-19 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 26.818 vf00 | Audio Media Profiles Test Results for VR Streaming | Rel-15 read |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 read |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 read |
| TR 26.928 vj00 | Study on eXtended Reality (XR) in 5G | Rel-19 read |
| TS 26.940 vk10 | Ultra-Low Bitrate Codec for GEO IMS Voice | Rel-20 read |
| TR 26.981 vj00 | MBMS Provisioning & Content Ingestion Interface Study | Rel-19 read |
| TR 26.998 vj00 | 5G AR/MR Glasses Integration Study | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 read |
| TS 29.212 vk00 | Diameter-Based PCC Reference Points | Rel-20 read |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 read |
| TS 29.507 vk10 | Access and Mobility Policy Control | Rel-20 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 32.130 vj20 | Network Sharing OAM&P Requirements | Rel-19 read |
| TS 32.451 vj00 | KPI Requirements for E-UTRAN | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 36.444 vj00 | M3AP Protocol Specification for M3 Interface | Rel-19 read |
| TR 38.835 vi01 | Technical Report on XR Enhancements for NR | Rel-18 read |