WLAN - APN

Description

The WLAN - APN (W-APN) is a specialized Access Point Name used within 3GPP architectures to facilitate packet data connectivity for User Equipment (UE) when it is accessing the network via a non-3GPP Wireless Local Area Network (WLAN), such as Wi-Fi. An APN is a critical identifier in mobile packet core networks; it is essentially a Fully Qualified Domain Name (FQDN) that the network uses to determine the correct Packet Data Network Gateway (PGW in 4G/EPC) or Packet Gateway (PGW-U+PGW-C in 5G) and to select the specific external Packet Data Network (PDN) the user wishes to connect to, like the internet or an IP Multimedia Subsystem (IMS) network. The 'W-' prefix explicitly denotes its application for WLAN access scenarios.

When a UE attaches to the network via WLAN, it includes the W-APN in its connection request. This request is typically handled by a trusted WLAN Access Gateway (TWAG) or, in more recent architectures, a Non-3GPP InterWorking Function (N3IWF). The network element resolves the W-APN to identify the appropriate PGW/SMF+UPF and the associated service profile. The resolution process involves querying the Domain Name System (DNS) of the core network. The selected gateway then establishes a GTP or PMIP-based tunnel (such as S2a or N3IWF-UPF tunnel) for the user's data traffic, applying the specific policies, charging rules, and QoS parameters associated with that W-APN.

The W-APN is central to policy enforcement and service differentiation. It allows operators to offer different service tiers or dedicated service networks (e.g., a 'VoWiFi' APN for IMS-based voice over Wi-Fi) over WLAN access. It works in conjunction with authentication mechanisms like EAP-AKA or EAP-AKA' to ensure secure access. The management of W-APN configurations is part of the UE's subscription data stored in the Home Subscriber Server (HSS) or Unified Data Management (UDM), ensuring that users are authorized for the WLAN services they attempt to access. This mechanism provides a standardized way to integrate WLAN into the mobile operator's service framework.

Purpose & Motivation

The W-APN was developed to solve the challenge of integrating unlicensed spectrum WLAN (Wi-Fi) access into the 3GPP mobile network ecosystem in a controlled and service-aware manner. Initially, WLAN was seen as a separate, best-effort internet access technology with no integration with cellular services. This led to a disjointed user experience where services like voice calls or secure enterprise access would drop when moving between cellular and Wi-Fi. The creation of the W-APN, part of the broader 3GPP WLAN Interworking (I-WLAN) and later Trusted WLAN Access (TWAN) standards, provided a standardized identifier to bridge this gap.

Its purpose is to enable the mobile core network to identify and apply the same sophisticated policy control, charging, and service continuity mechanisms to WLAN access as it does to 3GPP radio access. Before W-APN, Wi-Fi traffic was often offloaded directly to the internet without traversing the operator's core, denying the operator visibility and control. By using a W-APN, the operator can route selected traffic through their core network gateways, enabling services like carrier-grade Voice over Wi-Fi (VoWiFi), seamless offload, and access to operator-hosted services (e.g., IMS, IPTV). It addressed the business and technical need for network convergence, allowing operators to use Wi-Fi as a complementary radio access technology while maintaining service quality, security, and monetization capabilities.

Key Features

• Identifies the target PDN and gateway for user data sessions established over WLAN access
• Enables policy and charging control (PCC) for WLAN traffic via the core network
• Supports service differentiation (e.g., separate APNs for internet, IMS, enterprise access) over Wi-Fi
• Integrates with 3GPP authentication and security frameworks (EAP-AKA/AKA')
• Facilitates seamless service continuity and traffic steering between 3GPP and WLAN access
• Configured as part of user subscription data in HSS/UDM

Evolution Across Releases

Defining Specifications