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

Glossary term · QoS

APN-AMBR

Access Point Name Aggregate Maximum Bit Rate

QoS →

APN-AMBR is a QoS parameter that limits the total maximum bit rate across all non-GBR bearers associated with a specific Access Point Name for a user equipment.

Introduced
Rel-8
Where
Core Network › Legacy Core
Specifications
3 specs
APN-AMBR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

APN-AMBR (Access Point Name Aggregate Maximum Bit Rate) is a fundamental Quality of Service (QoS) parameter within the 3GPP Evolved Packet System (EPS) architecture that governs the aggregate data throughput for all non-Guaranteed Bit Rate (non-GBR) bearers associated with a specific Access Point Name (APN) for a User Equipment (UE). Unlike per-bearer QoS parameters like QCI (QoS Class Identifier) and ARP (Allocation and Retention Priority), APN-AMBR operates at the APN level, applying a cumulative limit across multiple Packet Data Network (PDN) connections or bearers that share the same APN context. This aggregate approach is essential because a single UE can establish multiple simultaneous data sessions (e.g., internet browsing, video streaming, and corporate VPN) through the same APN, each potentially on separate EPS bearers.

The parameter is enforced at two key network nodes: the User Plane Function (UPF) in 5G Core or the Packet Gateway (PGW) in EPC, and the gNodeB in 5G or eNodeB in LTE. The core network node (UPF/PGW) performs the primary enforcement, ensuring that the aggregate uplink and downlink traffic for all non-GBR bearers belonging to the APN does not exceed the subscribed APN-AMBR values. Simultaneously, the radio access network (RAN) node applies the APN-AMBR limit over the air interface, but it may further restrict the rate based on available radio resources and scheduling algorithms. This dual enforcement ensures consistent traffic shaping across both the core and radio segments.

APN-AMBR is defined by two distinct values: the uplink APN-AMBR and the downlink APN-AMBR, which are configured independently. These values are typically part of the user's subscription profile stored in the Unified Data Management (UDM) or Home Subscriber Server (HSS) and are communicated to the Session Management Function (SMF) or PGW during session establishment. The SMF/PGW then forwards these limits to the UPF/PGW for enforcement and to the Access and Mobility Management Function (AMF) or Mobility Management Entity (MME), which subsequently informs the RAN. Importantly, APN-AMBR applies only to non-GBR bearers; GBR bearers have their dedicated guaranteed bit rates and are excluded from this aggregate limit.

From a technical implementation perspective, APN-AMBR enforcement involves token bucket or leaky bucket algorithms at the UPF/PGW to monitor and shape the aggregate traffic flow. When the aggregate traffic rate approaches the APN-AMBR limit, packets may be buffered, delayed, or dropped according to the network's congestion management policies. This mechanism prevents any single APN from consuming disproportionate network resources, thereby protecting network stability and ensuring equitable service delivery to all users. In multi-APN scenarios (where a UE connects to different APNs like 'internet' and 'IMS'), each APN has its own independent APN-AMBR, allowing for differentiated service controls based on the application or service type.

Purpose & Motivation

APN-AMBR was introduced in 3GPP Release 8 alongside the EPS to address the limitations of earlier 3GPP architectures in managing aggregate user data consumption. Prior to LTE/EPC, QoS mechanisms in 2G/3G networks primarily operated at the PDP (Packet Data Protocol) context level without robust aggregate controls across multiple data sessions. As smartphones and mobile applications evolved, users began simultaneously running multiple data-intensive services (e.g., video streaming, social media, and cloud synchronization) through a single network access point. Without an aggregate limit, these concurrent flows could collectively overwhelm network resources, leading to congestion, degraded performance for other users, and unpredictable billing scenarios.

The primary problem APN-AMBR solves is the need for granular, subscription-based bandwidth management that aligns with both user service plans and network capacity planning. By imposing an aggregate cap per APN, operators can enforce fair usage policies, prevent network abuse, and implement tiered service offerings (e.g., differentiating between premium and standard data plans). For example, a user with a basic subscription might have a lower APN-AMBR than a user with a premium plan, even if both are using the same applications. This capability is crucial for monetization and service differentiation.

Furthermore, APN-AMBR enables more efficient radio and core network resource utilization. By controlling the aggregate throughput per APN, the network can better manage scheduling priorities, reduce congestion, and maintain overall system stability. It also provides a mechanism to implement service-aware policies; for instance, an operator might set a higher APN-AMBR for a dedicated 'video streaming' APN compared to a general 'internet' APN. This historical evolution from per-bearer QoS to include aggregate APN-level controls reflects the industry's shift toward more sophisticated traffic management in the face of exploding mobile data demand and diverse service requirements.

What changed in its specifications

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

TS 23.060Rel-18 → Rel-19

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 →
TS 24.301Rel-18 → Rel-19

Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.

Full comparison in TS 24.301 →

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
  • APN-AMBR counterpart in another generation: Session-AMBR
    “the Session AMBR contains the APN-AMBR” 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 10 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-8 introduced

APN-AMBR is specified for the first time as a QoS parameter limiting aggregate Non-GBR bit rate per APN, enforced by P-GW and UE, with NAS and GTPv2 IE coding.

  • “It limits the aggregate bit rate that can be expected to be provided across all Non‑GBR bearers and across all PDN connections of the same APN” TS 23.401 v8.18.0
  • “The purpose of the APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR when the UE establishes a PDN connection” TS 24.301 v8.10.0
  • “This IE represents the APN-AMBR. It shall be included for an E-UTRAN initial attach, UE requested PDN connectivity” TS 29.274 v8.12.0
Rel-9 specification text

Rel-9 TS 23.401 adds APN-AMBR handling for multiple PDN connections of an APN, with PGW explicit signalling per connection to update the value, plus MME UE-AMBR update when APN-AMBR changes.

Rel-10 specification text

APN-AMBR handling was extended: GTPv2 IE inclusion now covers S2b procedures and ePDG, and the SGSN sends max MBR/APN-AMBR in the enhanced SRNS relocation Update PDP Context Request.

  • “It shall be included on the S4/S11, S5/S8 and S2b interfaces for an E-UTRAN initial attach, UE requested PDN connectivity” TS 29.274 v10.15.0
  • “RAT type, MS Info Change Reporting support indication, NRSN, DTI, max MBR/APN-AMBR) to the GGSNs concerned” TS 23.060 v10.14.0
  • “Enforcement of APN-AMBR / UE-AMBR is independent of whether the MBR of a particular GBR bearer has been set larger than the GBR” TS 23.401 v10.13.0
Rel-11 1 CR

APN-AMBR handling changed in Rel-11: the MME may downgrade APN-AMBR received over S8, the Update Bearer Request carries APN-AMBR, and the Modify Bearer Response gets a presence condition for it.

  • “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
  • “If both the PCO and the TFT are absent and the APN-AMBR has not been modified, the MME shall skip the following steps 4-7.” TS 23.401 v11.11.0
  • Presence condition of APN-AMBR in the Modify Bearer Response message TS 29.274CR1221
Rel-12 1 CR

APN-AMBR handling changed: GTPv2 APN-AMBR IE now covers TAU/RAU/handover from Gn/Gp SGSN with rounding rules, and APN-AMBR is removed from Modify Bearer Response.

  • “If such conversions result in fractions, then the value of APN-AMBR for uplink and the APN-AMBR for downlink shall be rounded upwards.” TS 29.274 v12.15.0
  • Removing APN-AMBR from Modify Bearer Response TS 29.274CR1392
  • “TAU/RAU/Handover from the Gn/Gp SGSN to the S4 SGSN/MME procedures, Attach with GTP on S2b” TS 29.274 v12.15.0
Rel-13 1 CR

APN-AMBR behaviour changed: the MME or PDN GW may now modify the subscribed APN-AMBR (e.g. for NB-IoT) by local policy, and the GTP-C APN-AMBR IE applies to more procedures such as handovers from non-3GPP access.

  • “applies as APN-AMBR unless the APN-AMBR is modified by the MME (e.g in roaming scenarios and/or for usage of NB-IoT) or the PDN GW” TS 23.401 v13.14.0
  • “Correction of UE-AMBR and APN-AMBR handling for CIoT EPS optimisation” TS 23.401 v13.14.0
  • Time conditioned APN-AMBR handling TS 29.212CR1406
Rel-14 1 CR

APN-AMBR handling was corrected for CIoT EPS Optimisation, and APN-AMBR is now included in the Update Bearer Request sent to the Serving GW in a TFT-only bearer update.

  • Correction of UE-AMBR and APN-AMBR handling for CIoT EPS Optimisation TS 23.401CR3122
  • “The PDN GW then sends the Update Bearer Request (PTI, EPS Bearer Identity, APN-AMBR, TFT, Retrieve Location) message to the Serving GW.” TS 23.401 v14.11.0
Rel-15 1 CR

Extended APN-AMBR support was added in NAS signalling: values above 65280 Mbps are now encoded in a new extended APN aggregate maximum bit rate IE, used on PDN connection establishment and on network-initiated changes.

  • “to indicate the initial subscribed APN-AMBR with a value higher than 65280 Mbps when the UE establishes a PDN connection” TS 24.301 v15.8.0
  • Handling of extended EPS quality of service IE and extended APN-AMBR IE TS 24.301CR2919
Rel-16 1 CR

APN-AMBR handling was updated in Rel-16: the paragraphs were reworded, and a CR assigned information element identifiers (IEIs) for the APN-AMBR IE in 24.244.

  • IEIs assignment for Bearer level QoS IE and APN-AMBR IE TS 24.244CR0057
Rel-17 1 CR

The APN-AMBR encoding in TS 24.301 was corrected (typo in minimum range of extended-2 APN-AMBR), and TS 23.401 now lets the MME downgrade APN-AMBR received over S8 for roaming.

  • Fix typo in the minimum range of APN-AMBR for downlink or uplink (extended-2) TS 24.301CR3525
  • “the MME, based on local policies, can downgrade the ARP priority level, ARP pre-emption capability, ARP pre-emption vulnerability, APN-AMBR or MBR (for GBR bearers) parameters received over S8” TS 23.401 v17.11.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19 read