Access Point Name Aggregate Maximum Bit Rate

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.

Key Features

• Aggregate bandwidth limiting across all non-GBR bearers for a specific APN
• Independent uplink and downlink maximum bit rate enforcement
• Dual enforcement at both core network (UPF/PGW) and radio access network (RAN) nodes
• Subscription-based parameter stored in UDM/HSS and applied during session establishment
• Exclusion of GBR bearers from the aggregate limit to preserve guaranteed service flows
• Support for multiple concurrent APNs per UE with independent APN-AMBR values per APN

Evolution Across Releases

Defining Specifications