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

Glossary term · QoS

MFBR

Maximum Flow Bit Rate

QoS →

MFBR is a QoS parameter that defines the maximum sustained bit rate allowed for a data flow within a PDU session for traffic policing and resource allocation.

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

Description

The Maximum Flow Bit Rate (MFBR) is a Quality of Service (QoS) parameter defined in the 5G QoS model. It applies to individual QoS Flows within a Protocol Data Unit (PDU) Session. A QoS Flow is the finest granularity for QoS differentiation in the 5G system, and each flow is associated with a QoS profile containing parameters like the 5G QoS Identifier (5QI), Guaranteed Flow Bit Rate (GFBR), and the MFBR. The MFBR specifies the peak bit rate that the network should not exceed for that particular QoS Flow. It represents an upper limit on the sustained data rate.

In operation, the MFBR is used by the network's User Plane functions, particularly the UPF (User Plane Function), to perform traffic policing. When user data packets for a specific QoS Flow arrive, the UPF measures the flow's bit rate. If the flow's rate attempts to exceed the configured MFBR, the UPF will typically drop or mark (e.g., using Explicit Congestion Notification) the excess packets to enforce the limit. This prevents a single QoS Flow from consuming disproportionate network resources, which is crucial for maintaining service quality for other flows and users. The MFBR is enforced on a per-flow basis, allowing for granular control.

The MFBR is signaled during PDU Session establishment or modification procedures. The SMF (Session Management Function) is responsible for deriving the QoS parameters, including MFBR, based on subscriber policies from the PCF (Policy Control Function) and the requested service. The SMF then provides these parameters to the UPF for enforcement and to the RAN (via the AMF) for potential radio resource consideration. While the RAN primarily uses the Aggregate Maximum Bit Rate (AMBR) for non-GBR flows, the per-flow MFBR is essential in the core network for precise traffic management. Its value is typically expressed in kilobits per second (kbps) or megabits per second (Mbps) and is a critical component in realizing network slicing, as different slices can have vastly different MFBR limits tailored to their service requirements (e.g., enhanced Mobile Broadband vs. IoT).

Purpose & Motivation

The MFBR exists to provide a mechanism for precise traffic policing and resource management at the granularity of a QoS Flow. In the absence of such a parameter, data flows could potentially consume unlimited bandwidth, leading to network congestion, unfair resource allocation, and degradation of service for other users. It is a fundamental tool for implementing service-level agreements (SLAs) and differentiated charging models, where users or services are granted specific maximum bandwidth entitlements.

Historically, similar concepts existed in earlier systems (like Maximum Bit Rate in EPS), but the 5G QoS model refines it within a more flexible, flow-based architecture. The motivation for MFBR in 5G is heightened by the diverse range of services, from ultra-high-definition video (requiring high MFBR) to massive IoT (requiring very low MFBR). It allows network operators to efficiently package and sell tiered data services, enforce fair use policies, and ensure that critical services (with guaranteed bit rates) are not starved by best-effort traffic attempting to use excessive bandwidth. It is a key enabler for network efficiency and monetization in 5G.

What changed in its specifications

The latest release-to-release comparison of specifications that define MFBR. 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

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

MFBR is defined for the first time as a GBR QoS Flow parameter for UL and DL, signalled to RAN and UE, enforced in UPF and RAN, and encoded in NAS QoS parameters.

  • “The MFBR is enforced in the UPF in the Downlink for GBR QoS Flows.” TS 23.501 v15.13.0
  • “The MFBR limits the bit rate to the highest bit rate that is expected by the QoS Flow” TS 23.501 v15.13.0
  • “When the parameter identifier indicates "MFBR uplink", the parameter contents field contains the one octet indicating the unit” TS 24.501 v15.7.0
Rel-16 2 CRs

MFBR became a mandatory parameter of GBR QoS flows in UE-side handling, with a syntactical error when both MFBR uplink and downlink are zero, and MFBR is also signalled to the UE after notification control or alternative QoS profile use.

  • Add MFBR as mandatory parameter in GBR QoS flow TS 24.501CR2120
  • Declare syntactical error when both MFBR uplink and MFBR downlink equal zero TS 24.501CR1804
  • “the SMF shall use NAS signalling (that is sent transparently through the RAN) to inform the UE about the QoS parameters (i.e. 5QI, GFBR, MFBR)” TS 23.501 v16.20.0
Rel-17 1 CR

UE handling of MFBR changed: subscribed MFBR indication for uplink/downlink omits the MFBR parameter, and GBR QoS flow descriptions lacking MFBR are treated as errors; MFBR is also specified for PC5 QoS flows.

  • “When the UE indicates subscribed MFBR for uplink, the "MFBR uplink" parameter is not included in the "Parameters list".” TS 24.501 v17.18.1
  • Clarifications on indicating subscribed MFBR/GFBR uplink/downlink TS 24.501CR2675
  • “When the parameter identifier indicates "MFBR ", the parameter contents field contains the one octet indicating the unit of the maximum flow bit rate” TS 24.554 v17.10.0
Rel-18 specification text

MFBR is now signalled within N3QAI for each QoS flow to the PEGC, with its own uplink/downlink parameter contents format, and the TSN Maximum Flow Bitrate is calculated over StreamGateAdminCycleTime.

  • “N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate.” TS 23.501 v18.12.0
  • “the format of the N3QAI parameter contents follows the table 9.11.4.12.1 of clause 9.11.4.12 of this specification.” TS 24.501 v18.14.0
Rel-19 specification text

Rel-19 adds rules that the available bitrate can never exceed MFBR, and that MFBR from the SMF is set as the end-to-end MFBR for PC5 GBR QoS flows.

  • “The available bitrate can be larger than the GFBR but can never exceed the MFBR.” TS 23.501 v19.9.0

Defining Specifications

3GPP specifications that define or reference MFBR, 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
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 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 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read