Access Point Name

Description

The Access Point Name (APN) is a critical configuration parameter in 3GPP packet-switched networks, acting as a reference point to a Packet Data Network (PDN). Structurally, an APN is a Fully Qualified Domain Name (FQDN) composed of two parts: the APN Network Identifier (mandatory), which specifies the external PDN, and the APN Operator Identifier (optional), which identifies the operator's network. When a User Equipment (UE) initiates a Packet Data Protocol (PDP) Context activation in 3G/UMTS or a PDN Connection in 4G/5G, it includes the APN. The network uses this APN to select the appropriate Gateway GPRS Support Node (GGSN) in UMTS or the Packet Data Network Gateway (PGW) in EPS/5GC, which serves as the anchor point to the external network.

Upon receiving an activation request with an APN, the Serving GPRS Support Node (SGSN) in UMTS or the Mobility Management Entity (MME)/Session Management Function (SMF) in EPS/5GC performs a DNS query. This query resolves the APN FQDN to the IP address(es) of the suitable gateway (GGSN/PGW). The selection process considers subscriber profiles, network policies, and load balancing. The chosen gateway then establishes the data session, allocates an IP address to the UE (often via DHCP), and sets up the user plane bearers for data traffic. The APN thus directly dictates the routing path, the external network reachable, and the Quality of Service (QoS) profile applied to the connection.

The APN's role extends beyond simple connectivity. It is intrinsically linked to policy and charging control. The APN value is used by the Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) to determine which policy and charging rules apply to the subscriber's data session. This enables operators to offer differentiated services—such as dedicated APNs for Internet, MMS, IMS, or enterprise VPNs—each with distinct bandwidth limits, security settings, and billing models. In 5G, the concept evolves with the Data Network Name (DNN), which is functionally equivalent to the APN, providing connectivity to a specific data network while integrating with network slicing and enhanced policy frameworks.

Purpose & Motivation

The APN was introduced to solve the fundamental problem of connecting mobile subscribers to multiple, distinct packet data networks beyond the mobile operator's core. In early GPRS, without such an identifier, all data traffic would be homogeneously routed to a single external network (like the public internet), preventing service differentiation, secure corporate access, and specialized services like WAP or MMS. The APN provides the necessary logical separation, allowing the network to select different gateways and apply specific policies based on the intended service.

Historically, before standardized APNs, value-added data services were difficult to implement and manage. The APN mechanism created a scalable, subscriber-configurable way to direct sessions. It addressed limitations in routing, billing, and service quality by enabling the network to identify the destination PDN during session establishment. This was crucial for the commercial success of mobile data, as it allowed operators to offer tiered service plans, partner with content providers, and support secure enterprise connectivity through dedicated APNs with private addressing.

Furthermore, the APN is central to policy enforcement and charging. By associating a session with a specific APN, operators can deploy distinct policy rules for traffic shaping, access control, and quality of service. It enables accurate billing—for example, charging data used on a 'internet' APN differently from data on a 'mms' APN. This flexibility motivated its creation and sustained evolution, forming the basis for the more advanced DNN parameter in 5G systems, which continues this role within network slicing and service-based architectures.

Key Features

• Identifies the external Packet Data Network (PDN) for session routing
• Used by the network to select the appropriate gateway (GGSN/PGW)
• Determines the IP address allocation method for the UE
• Triggers specific Policy and Charging Control (PCC) rules
• Enables differentiated services, QoS, and billing per data service
• Configured on the UE and validated against subscriber profile in HSS/UDM

Evolution Across Releases

Defining Specifications