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 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
- GBR counterpart in another generation: GFBR
“ARP, GBR and MBR of the EPS Bearer is set to the ARP, GFBR and MFBR of the corresponding QoS Flow, respectively.” TS 23.502
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 12 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in R99 (release dating of the term; no individual change cited).
TS 23.401 v8i0 defines GBR for the first time, as a bearer-level QoS parameter: GBR bearers get permanently allocated dedicated resources, while Non-GBR bearers do not.
- “An EPS bearer is referred to as a GBR bearer if dedicated network resources related to a Guaranteed Bit Rate (GBR) value” TS 23.401 v8.18.0
- “The GBR denotes the bit rate that can be expected to be provided by a GBR bearer.” TS 23.401 v8.18.0
- “Each GBR bearer is additionally associated with the following bearer level QoS parameters:” TS 23.401 v8.18.0
In Rel-9 the MME's handling of GBR bearers on S1 release changed: bearers are preserved for User Inactivity and Inter-RAT Redirection, and CS Fallback is handled per TS 23.272; other causes trigger dedicated bearer deactivation.
- “If the cause of S1 release is because of User Inactivity, Inter-RAT Redirection, the MME shall preserve the GBR bearers.” TS 23.401 v9.16.0
- “the PDN GW provides to the PCRF the content of the TAD and, if applicable, the GBR change (increase or decrease)” TS 23.401 v9.16.0
MBR of a GBR bearer may now be set larger than the GBR, replacing the earlier requirement that MBR equal GBR, and enforcement of AMBR is independent of this.
- “The MBR of a particular GBR bearer may be set larger than the GBR.” TS 23.401 v10.13.0
- “The MBR of a particular GBR bearer shall be set equal to the GBR.” TS 23.401 v10.13.0
MME GBR bearer handling on S1 release changed: GBR bearers are now deactivated when S1 signalling is lost or the eNodeB fails, and the UE GBR modification request now requires existing packet filter identifiers.
- “Otherwise, e.g. Radio Connection With UE Lost, S1 signalling connection lost, eNodeB failure the MME shall trigger the MME Initiated Dedicated Bearer Deactivation procedure” TS 23.401 v11.11.0
- “When only requesting for a modification of GBR (i.e. decrease or increase), the TAD shall include the existing packet filter identifier(s)” TS 23.401 v11.11.0
- “The MME, based on local policies, can downgrade the ARP pre-emption capability, APN-AMBR or MBR (for GBR bearers) parameters received over S8” TS 23.401 v11.11.0
GBR bearers are declared unsupported in NB-IoT, with the PDN GW using RAT Type to keep them inactive, and the MME may defer GBR bearer deactivation for a short period.
- “GBR bearers are not supported by NB-IoT. The PDN GW uses the RAT Type to ensure that GBR bearers are not active” TS 23.401 v13.14.0
- “The MME can defer the deactivation of GBR bearers for a short period (in the order of seconds)” TS 23.401 v13.14.0
- Deferring GBR bearers deactivation upon S1 Reset or S1AP path failure TS 23.007CR0317r1
The 5G system specifications first define GBR QoS Flows in Rel-15, with GFBR/MFBR parameters, notification control, and PCC handling of GBR rules and resource sharing.
- “A QoS Flow using the GBR resource type or the Delay-critical GBR resource type and requiring guaranteed flow bit rate.” TS 23.501 v15.13.0
- “For each GBR QoS Flow only, the QoS profile shall also include the QoS parameters:” TS 23.501 v15.13.0
- “If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN determines that the GFBR can no longer be guaranteed” TS 23.501 v15.13.0
GBR QoS Flow handling was extended with Alternative QoS Profiles, GFBR notification control behaviour in NG-RAN, and GBR traffic handling for MA PDU sessions.
- “NG-RAN shall send a notification towards SMF that the "GFBR can no longer be guaranteed".” TS 23.501 v16.20.0
- “the SMF shall release the resources for the GBR QoS flow and report to the PCF about the removal of the PCC rule” TS 29.512 v16.23.0
- Steering modes for GBR traffic TS 23.501CR2153
Rel-17 adds GBR QoS flow handling for network slice data rate control (UE-Slice-MBR admission control, PCF slice rate deduction) and TSC-derived GBR, plus GBR default QoS flow corrections.
- “the NG-RAN admission control shall ensure that the sum of the GFBR values of the admitted GBR QoS Flows is not exceeding the UE-Slice-MBR” TS 23.501 v17.15.0
- “the PCF derives the MBR using the Requested Maximum Bitrate provided by the AF and sets the GBR equal to the MBR” TS 23.503 v17.11.0
- Correction to the GBR type of default QoS flow TS 29.512CR0716
In Rel-18 GBR QoS Flows gained support for the Redundant steering mode, with the SMF providing the QoS profile to both accesses and handling resource allocation failures.
- “If the PCC rule allows a GBR QoS Flow in both accesses and the Steering Mode is Redundant, the SMF provides the QoS profile for the GBR QoS Flow to both access networks.” TS 23.501 v18.12.0
- “for a GBR QoS Flow using the Delay-critical resource type” TS 23.501 v18.12.0
- Handling of GBR traffic using the Redundant steering mode TS 29.244CR0799
Rel-19 adds QoS monitoring and reporting of UL/DL available bitrate for GBR QoS Flows, with NG-RAN reporting via GTP-U and PCF/AF subscription thresholds, plus a new GBR streaming slice type.
- “For a GBR QoS Flow, based on the PCC rule from PCF, the SMF requests the NG-RAN to report the UL and/or DL available bitrate.” TS 23.501 v19.9.0
- “The QoS Monitoring for available bitrate allows the measurement and reporting of the UL and/or DL available bitrate for a GBR QoS Flow” TS 23.501 v19.9.0
- Activation of QoS monitoring for the GBR service data flow TS 23.503CR1550
GBR bearers, previously unsupported in NB-IoT, are now supported for NB-IoT (GEO) when IMS voice is supported, with the PDN GW restricting GBR bearers by RAT type otherwise.
- “For NB-IoT (GEO), when IMS voice is supported (see clause 4.13.12) then GBR bearers are supported.” TS 23.401 v20.1.0
- “Except for the case of IMS Voice over NB-IoT(GEO), GBR bearers are not supported by NB-IoT.” TS 23.401 v20.1.0
- Dedicated bearer and GBR bearer support for IMS Voice over NB-IoT(GEO) TS 23.401CR4002
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 |