Access Point Name Network Identifier

Description

The Access Point Name Network Identifier (APN-NI) is a fundamental component of the APN structure defined in 3GPP specifications. An APN is a Fully Qualified Domain Name (FQDN) used by the network to select the Packet Data Network Gateway (PGW) for a UE's Packet Data Protocol (PDP) context or PDN connection. The APN itself is composed of two parts: the APN Network Identifier (APN-NI) and the APN Operator Identifier (APN-OI). The APN-NI is the mandatory part that identifies the external packet data network (PDN) the UE wishes to communicate with, such as 'internet', 'ims', or a corporate domain like 'company.mnc012.mcc345.gprs'. The APN-OI, which is optional, defines the network operator's domain (e.g., .mnc<MNC>.mcc<MCC>.gprs) and is often appended by the network.

Architecturally, the APN-NI is used during the session establishment procedures, primarily in the Packet Data Protocol (PDP) context activation in GPRS/UMTS or the PDN connectivity request in LTE/5G. When a UE initiates a data session, it includes a requested APN, which contains the APN-NI, in signaling messages sent to the network. The Serving GPRS Support Node (SGSN) in 2G/3G or the Mobility Management Entity (MME)/Access and Mobility Management Function (AMF) in 4G/5G receives this request. The network node then uses the APN-NI, along with subscriber profile information from the Home Subscriber Server (HSS) or Unified Data Management (UDM), to resolve the appropriate PGW or User Plane Function (UPF) that provides connectivity to the desired external network.

The resolution process involves a Domain Name System (DNS) query. The network constructs a full APN FQDN by potentially combining the UE-provided APN-NI with the operator's APN-OI. This FQDN is then queried in the DNS to obtain the IP address(es) of the suitable PGW(s). The selection is based on factors like PGW capabilities, load, and topological proximity. The APN-NI is thus the key that unlocks the mapping to the specific gateway and the external data network. It enables network segmentation, allowing operators to offer distinct services (e.g., internet access, IMS for VoLTE, enterprise VPNs) over the same physical infrastructure by using different APN-NIs.

In the core network architecture, the APN-NI is tightly integrated with policy control. The Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) can be informed of the APN in use. This allows the application of specific Quality of Service (QoS) profiles, charging rules, and access control policies tailored to that particular APN-NI. For example, traffic on an 'ims' APN-NI might be given higher priority and different charging than traffic on a general 'internet' APN-NI. The APN-NI therefore acts not just as a routing label, but also as a policy anchor point within the 3GPP system.

Purpose & Motivation

The APN-NI was created to solve the fundamental problem of identifying and connecting to diverse external packet data networks from within a mobile operator's core network. In early 2G GPRS networks, as operators began offering data services beyond simple internet access, a mechanism was needed to direct user traffic to the correct destination network, such as a wireless application protocol (WAP) gateway, a corporate intranet, or later, the IP Multimedia Subsystem (IMS). Without a standardized identifier like the APN-NI, networks would lack the ability to support multiple concurrent data services for a single subscriber or to offer specialized network slices for different applications.

Historically, before the formalization of the APN structure, data connectivity was often monolithic or required proprietary configurations. The introduction of the APN, with the APN-NI as its core identifier, provided a standardized, flexible, and scalable method for service differentiation. It addressed the limitation of having a one-size-fits-all data path by enabling the network to select different gateways (GGSNs/PGWs) based on the service requested. This was crucial for the commercialization of mobile data, allowing for the creation of service-specific APNs with tailored bandwidth, security, and billing characteristics.

The APN-NI's purpose extends to enabling mobile virtual network operators (MVNOs) and facilitating roaming. An MVNO can use its own APN-NI to route traffic through its own network infrastructure even while using the host operator's radio access. For roaming subscribers, the visited network uses the APN-NI, often in conjunction with the home operator's APN-OI, to establish a connection back to the home network's PGW (home-routed traffic) or to a local PGW (local breakout), as defined by the APN configuration. Thus, the APN-NI is a cornerstone for service innovation, multi-tenancy, and global interoperability in mobile packet-switched networks.

Key Features

• Identifies the external packet data network (PDN) for UE connectivity
• Mandatory component of the Access Point Name (APN) FQDN
• Used by network nodes (SGSN/MME/AMF) to select the appropriate PGW/UPF via DNS resolution
• Enables service differentiation and network segmentation (e.g., internet, IMS, enterprise VPN)
• Serves as a key for applying service-specific QoS and charging policies via PCRF/PCF
• Supports roaming scenarios by facilitating home-routed or local breakout traffic steering

Evolution Across Releases

Defining Specifications