Description
The UE Aggregate Maximum Bit Rate (UE-AMBR) is a Quality of Service (QoS) parameter defined in the EPS and 5GS architectures to control the aggregate bandwidth consumption of a User Equipment (UE). Specifically, it applies to the sum of the data rates of all Non-Guaranteed Bit Rate (Non-GBR) bearers or QoS Flows associated with that UE. Non-GBR bearers are used for best-effort traffic like web browsing or video streaming, where the network does not guarantee a minimum bit rate. The UE-AMBR acts as a ceiling for this aggregate traffic, ensuring fair sharing of radio resources among multiple UEs in a cell.
The UE-AMBR is subscribed in the user's profile in the Home Subscriber Server (HSS) or Unified Data Management (UDM) and is downloaded to the Mobility Management Entity (MME) or Access and Mobility Management Function (AMF) during UE attachment. The MME/AMF then signals the subscribed UE-AMBR value to the base station—the eNodeB (eNB) in LTE or the gNodeB (gNB) in 5G NR. The enforcement of the UE-AMBR is performed solely by the base station in both the uplink and downlink directions. The base station uses scheduling algorithms to ensure that the aggregate data rate for a UE's Non-GBR bearers does not exceed the UE-AMBR limit, while still attempting to meet the QoS requirements of individual bearers.
It is crucial to distinguish UE-AMBR from per-bearer QoS parameters like the Aggregate Maximum Bit Rate (APN-AMBR) and the Guaranteed Bit Rate (GBR). The APN-AMBR limits traffic per Access Point Name (APN) and is enforced by the Packet Gateway (PGW/UPF), while the GBR is a committed rate for dedicated bearers. The UE-AMBR, in contrast, is a radio-level enforcement point. It does not apply to GBR bearers, which have their own dedicated resource reservations. This hierarchical QoS control allows operators to manage network capacity efficiently: APN-AMBR controls core network resource usage per PDN connection, and UE-AMBR controls the radio interface usage per subscriber device.
Purpose & Motivation
UE-AMBR was introduced in 3GPP Release 8 with the Evolved Packet System (EPS) to address the need for subscriber-level radio resource policing in all-IP networks. Prior QoS mechanisms in 2G/3G often focused on per-bearer or per-PDP context guarantees but lacked an efficient way to cap the total radio resource consumption of a single device, especially with the rise of flat-rate data plans and bandwidth-hungry applications. Without UE-AMBR, a single UE with multiple active best-effort sessions (e.g., simultaneous downloads and video streams) could potentially consume a disproportionate share of a cell's capacity, degrading service for other users.
The primary problem UE-AMBR solves is ensuring radio resource fairness and preventing congestion at the air interface. It allows mobile operators to offer tiered data plans by associating different UE-AMBR values with different subscription tiers (e.g., premium vs. basic). It also provides a tool for traffic management, ensuring that the shared nature of the radio medium is respected. Its enforcement at the base station is critical because the radio scheduler has the most accurate and real-time view of resource availability and UE channel conditions, enabling dynamic and efficient application of the limit.
What changed in its specifications
The latest release-to-release comparison of specifications that define UE-AMBR. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →Rel-19 brings only minor changes to TS 29.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 29.060 →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
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 7 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.
UE-AMBR is specified for the first time: the MME sets it from the subscribed value and APN-AMBRs, signals it to the eNB over S1AP, and the E-UTRAN enforces it for Non-GBR bearers.
- “The UE‑AMBR limits the aggregate bit rate that can be expected to be provided across all Non‑GBR bearers of a UE” TS 23.401 v8.18.0
- “the eNB shall use the received UE Aggregate Maximum Bit Rate for non-GBR Bearers for the concerned UE.” TS 36.413 v8.10.0
- “DL bearer level rate enforcement based on UE-AMBR;” TS 23.401 v8.18.0
UE-AMBR handling was extended: MME uses a local UE-AMBR for Gn/Gp SGSN handover, determines it for emergency attach, and recalculates and signals it on bearer changes, with UE-AMBR also added to 23.060 SGSN/RNC signalling.
- “If explicit APN-AMBR values are not received by the MME, a local UE-AMBR shall be included in the 'EPS Bearers be setup list ' IE.” TS 23.401 v9.16.0
- “For emergency attach the MME determines the UE-AMBR to be used by the eNodeB from the APN AMBR received from the S-GW.” TS 23.401 v9.16.0
- “Receiving both the UE Aggregate Maximum Bit Rate Downlink IE and the UE Aggregate Maximum Bit Rate Uplink IE equal to value zero shall be considered as a logical error by the eNB.” TS 36.413 v9.10.0
UE-AMBR and APN-AMBR handling was corrected for CIoT EPS optimisation, and UE-AMBR is now excluded from Control Plane CIoT PDN connections where the S1-AP NAS transport message is used instead.
- “Correction of UE-AMBR and APN-AMBR handling for CIoT EPS optimisation” TS 23.401 v13.14.0
- Correct the storage of Used UE-AMBR TS 23.008CR0495
UE-AMBR handling was corrected for NB-IoT UEs using Control Plane CIoT EPS Optimisation: UE-AMBR was removed from Inter-UE QoS for such UEs, and S1AP and 23.401 handling were corrected.
- “Removal of UE-AMBR from Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS Optimisation” TS 23.401 v14.11.0
- Correction of UE-AMBR and APN-AMBR handling for CIoT EPS Optimisation TS 23.401CR3122
- Correction on UE-AMBR for NB-IoT UE using CP solution TS 36.413CR1517
In Rel-15, S1AP gains Extended UE-AMBR IEs that override the UE-AMBR IEs when present, and F1AP specifies a gNB-DU UE-AMBR Uplink that the gNB-DU stores, enforces and applies to non-GBR bearers.
- “If the Extended UE Aggregate Maximum Bit Rate Downlink IE is included, the UE Aggregate Maximum Bit Rate Downlink IE shall be ignored.” TS 36.413 v15.11.0
- “The gNB-DU shall store the received gNB-DU UE Aggregate Maximum Bit Rate Uplink and use it for non-GBR Bearers for the concerned UE.” TS 38.473 v15.18.0
- “The gNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the gNB-DU.” TS 38.473 v15.18.0
UE-AMBR handling changed: for RLOS attach as well as emergency attach the MME determines UE-AMBR from the APN AMBR, and CRs add serving PLMN UE-AMBR control.
- “For emergency attach or RLOS attach the MME determines the UE-AMBR to be used by the eNodeB from the APN AMBR received from the S-GW.” TS 23.401 v16.14.0
- Serving PLMN UE-AMBR control TS 23.501CR1367
Defining Specifications
3GPP specifications that define or reference UE-AMBR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |