Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · QoS

GFBR

Guaranteed Flow Bit Rate

QoS →

GFBR is the minimum bit rate guaranteed for a Quality of Service flow in 5G networks, ensuring critical services like VoNR receive at least a specified data rate.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
11 specs
Also in
Services, Radio Access Network
GFBR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Guaranteed Flow Bit Rate (GFBR) is a key QoS parameter introduced in 5G System (5GS) specifications, particularly in TS 23.501 (System Architecture for the 5G System) and TS 24.501 (Non-Access-Stratum protocol for 5GS). GFBR defines the bit rate that is guaranteed to be provided to a QoS flow by the network. It is applicable to Guaranteed Bit Rate (GBR) QoS flows, which are used for services that require dedicated bandwidth, such as Voice over NR (VoNR), real-time gaming, and mission-critical communications. GFBR is negotiated between the UE and the network during PDU session establishment or modification, and it represents the minimum guaranteed data rate for the flow.

In the 5G QoS framework, each QoS flow is associated with a QoS profile that includes parameters like 5QI (5G QoS Identifier), Allocation and Retention Priority (ARP), and for GBR flows, GFBR and Maximum Flow Bit Rate (MFBR). GFBR is enforced by the network through admission control, resource reservation, and scheduling. The Session Management Function (SMF) is responsible for authorizing the requested GFBR based on subscription data and policy control (PCF). The User Plane Function (UPF) and the Radio Access Network (RAN) ensure that the flow receives at least the GFBR by allocating sufficient radio resources and prioritizing the flow's packets.

GFBR can be set per QoS flow and can be different for uplink and downlink. It is typically expressed in bits per second. The network uses GFBR to determine whether a new GBR flow can be admitted without compromising existing guarantees. If resources are insufficient, the network may reject the establishment of the flow or modify its QoS parameters. GFBR is also used in handover procedures to ensure that the target cell can support the required bit rate before admitting the UE.

The 3GPP specifications define GFBR in various contexts, including network slicing, where each slice may have its own GFBR guarantees, and in interworking with 4G LTE, where GFBR maps to the Guaranteed Bit Rate (GBR) of EPS bearers. In TS 38.300 (NR overall description) and TS 38.835 (Study on enhancement for data collection for NR and EN-DC), GFBR is discussed in the context of RAN QoS management and performance measurements.

Overall, GFBR is a fundamental QoS parameter that enables deterministic service quality in 5G networks, supporting a wide range of applications from enhanced mobile broadband to ultra-reliable low-latency communications.

Purpose & Motivation

GFBR exists to provide a guaranteed minimum bit rate for specific QoS flows in 5G networks, addressing the need for deterministic quality of service for real-time and mission-critical applications. In earlier generations like 4G LTE, the concept of Guaranteed Bit Rate (GBR) was introduced for EPS bearers, but 5G introduced a more granular flow-based QoS model where GFBR applies per QoS flow. This allows operators to offer differentiated services with strict performance guarantees, such as voice calls, video conferencing, and industrial automation.

The motivation for GFBR stems from the limitations of best-effort and non-GBR services, which cannot assure consistent data rates under network congestion. By defining GFBR, 3GPP enables admission control and resource reservation mechanisms that ensure the required bandwidth is available throughout the lifetime of the flow, even during handovers or network load variations. This is essential for services that are sensitive to packet loss and delay, where falling below a certain bit rate would degrade the user experience.

Furthermore, GFBR supports network slicing and multi-operator scenarios by allowing each slice or tenant to specify their guaranteed bit rate requirements. It also facilitates interworking with 4G, where GFBR maps to GBR, ensuring continuity of QoS guarantees during mobility between generations. As 5G evolves towards Rel-20 and beyond, GFBR remains a cornerstone for QoS enforcement in diverse deployment scenarios.

What changed in its specifications

The latest release-to-release comparison of specifications that define GFBR. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Technology family

Sessions, bearers and QoS · Core Network

  1. R96 PDP context
  2. R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
  3. Rel-7 IP-CAN bearer, IP-CAN session, QCI
  4. Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
  5. Rel-9 Evolved ARP
  6. Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
  7. Rel-16 MA PDU Session
  • GFBR counterpart in another generation: GBR
    “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 sources

Documented changes in 5 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.

Rel-15 introduced

GFBR is specified for the first time in Rel-15: a UL/DL QoS parameter for GBR QoS Flows, with NG-RAN notification when it can no longer (or can again) be guaranteed, PCF reporting and UE signalling.

  • “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
  • “When the parameter identifier indicates "GFBR uplink", the parameter contents field contains one octet indicating the unit of the guaranteed flow bit rate for uplink” TS 24.501 v15.7.0
  • “For GBR QoS Flows, the SMF should set the GFBR to the sum of the GBRs of all PCC rules that are active” TS 23.503 v15.10.0
Rel-16 specification text

Rel-16 extends GFBR notification handling with Alternative QoS Profiles (GFBR/PDB/PER combinations), changes handover and notification behaviour, and makes GFBR and MFBR both mandatory for GBR QoS flows in UE signalling.

  • “the NG-RAN shall check whether the GFBR, the PDB and the PER that the NG-RAN currently fulfils match any of the Alternative QoS Profile(s)” TS 23.501 v16.20.0
  • “An Alternative QoS Profile represents a combination of QoS parameters PDB, PER and GFBR to which the application traffic is able to adapt.” TS 23.501 v16.20.0
  • “GBR QoS flows, if the QoS flow includes a GFBR uplink parameter, a GFBR downlink parameter, a MFBR uplink parameter and a MFBR downlink parameter” TS 24.501 v16.15.0
Rel-17 specification text

GFBR gained new roles in Rel-17: NG-RAN admission control must respect UE-Slice-MBR while guaranteeing each GBR flow's GFBR, UE handling of subscribed GFBR was clarified, and GFBR was specified for 5G ProSe PC5 flows.

  • “while always guaranteeing the GFBR of every GBR QoS Flow of those PDU Sessions as described in clause 5.7.2.5” TS 23.501 v17.15.0
  • “When the UE indicates subscribed GFBR for uplink, the "GFBR uplink" parameter is not included in the "Parameters list".” TS 24.501 v17.18.1
  • “the parameter contents field contains one octet indicating the unit of the guaranteed flow bit rate followed by two octets containing the value” TS 24.554 v17.10.0
Rel-18 specification text

NG-RAN notification control for GFBR was extended: notifications now cover PDB or PER not being fulfilled, report the current situation including Alternative QoS Profiles, and carry a BAT offset with the GFBR notification.

  • “notifications of "GFBR can no longer (or can again) be guaranteed" are requested when the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled” TS 23.501 v18.12.0
  • “The BAT offset is provided from NG-RAN to the SMF when sending the notification towards the SMF that the "GFBR can no longer be guaranteed"” TS 23.501 v18.12.0
  • “the NG-RAN shall also apply the value of the optional QoS parameter present in an Alternative QoS Profile instead of the corresponding QoS parameter's value” TS 23.501 v18.12.0
Rel-19 specification text

NG-RAN must now indicate the impacted direction when GFBR, PDB or PER cannot be fulfilled in only one direction, and "GFBR can again be guaranteed" requires fulfilment in both UL and DL.

  • “the NG-RAN shall also indicate the impacted direction when notifying that "GFBR can no longer be guaranteed"” TS 23.501 v19.9.0
  • “"GFBR can again be guaranteed" can only be sent when all of the GFBR, the PDB and the PER of the QoS profile are fulfilled in UL” TS 23.501 v19.9.0

Defining Specifications

3GPP specifications that define or reference GFBR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.554 vk10 5G ProSe Protocols and Procedures Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 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 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TR 38.835 vi01 Technical Report on XR Enhancements for NR Rel-18 read