Inter-APN Routing Policy

Description

The Inter-APN Routing Policy (IARP) is a network management and traffic steering mechanism defined in 3GPP standards, specifically within the context of ANDSF (Access Network Discovery and Selection Function) and later enhancements. It consists of policies configured by the network operator and provisioned to the User Equipment (UE) to intelligently route IP traffic flows across multiple simultaneous Packet Data Network (PDN) connections, each associated with a different Access Point Name (APN). An APN defines the gateway to a specific external network (e.g., the internet, an IMS network, or a corporate intranet). Without IARP, a UE typically uses a default APN for all traffic or relies on static configuration, which is inefficient for modern devices running multiple applications with diverse requirements.

Architecturally, IARP policies are part of the broader ANDSF framework, which provides the UE with network discovery information and inter-system mobility policies (ISMP) or routing policies (ISRP). IARP falls under the category of inter-system routing policies when dealing with routing across different 3GPP and non-3GPP accesses, but it specifically governs routing *between* APNs over the same 3GPP access. The policies are defined in an XML format (Managed Object) and are delivered from the ANDSF server to the UE via the S14 reference point. The UE's operating system or connection management software interprets these policies and applies them to route outgoing IP packets. The policy rules can be based on multiple criteria, including the destination IP address or domain, the application (identified by factors like OS application ID or possibly port number), the requested QoS, or the radio access technology in use.

How IARP works involves the UE evaluating its active PDN connections and the characteristics of each outgoing data flow against the provisioned policy rules. For example, a rule might state that all traffic destined for a corporate VPN server domain should be routed via the 'corporate' APN, while general web browsing traffic uses the 'internet' APN. Another rule could steer high-priority video streaming traffic to an APN configured for guaranteed bitrate QoS. The UE makes these routing decisions at the IP layer, effectively binding specific sockets or flows to specific network interfaces (each corresponding to a PDN connection). This enables simultaneous use of multiple APNs, allowing for traffic segregation, optimized charging (e.g., separating metered and unmetered traffic), and improved performance by matching application needs with network slice or APN capabilities.

Purpose & Motivation

IARP was created to address the limitations of single-APN connectivity in an era of increasingly sophisticated mobile devices and diverse service offerings. Early mobile data systems typically assigned one default APN to a UE for all internet traffic. This monolithic approach became inefficient as operators introduced specialized APNs for services like IMS (for VoLTE), carrier-branded messaging apps, or partnerships with content providers. Without a dynamic routing mechanism, users had to manually switch APNs or devices could only use one service at a time, leading to poor user experience and an inability to leverage network optimizations.

The primary problem IARP solves is intelligent traffic steering and network resource optimization. It allows operators to implement service-aware routing, directing traffic to the most appropriate network gateway based on the service type. This enables several benefits: offloading certain traffic (e.g., video streaming) to a content-delivery-network-optimized APN to reduce core network load, ensuring mission-critical enterprise traffic uses a secure and QoS-guaranteed APN, and separating charging by routing 'sponsored' content through a zero-rated APN. It provides a standardized, policy-driven alternative to complex and non-scalable solutions like deep packet inspection (DPI) in the network or reliance on device-specific, proprietary APIs for connection management.

Introduced in 3GPP Release 12, IARP's development was motivated by the need for more granular traffic management as part of the broader ANDSF enhancements for seamless Wi-Fi offloading and multi-access coordination. It represented a shift towards user-plane intelligence at the device, guided by network policies, aligning with the trend of software-defined networking (SDN) and network function virtualization (NFV). By empowering the UE to make routing decisions, IARP reduces signaling load on the network core compared to network-controlled steering and allows for faster, more application-responsive traffic management, paving the way for later concepts like multi-access edge computing (MEC) and 5G network slicing where traffic routing is paramount.

Key Features

• Operator-defined XML-based policies provisioned to UE via ANDSF
• Routes IP traffic flows between multiple simultaneous PDN connections (APNs)
• Policy rules based on criteria like destination IP/domain, application ID, or QoS requirements
• Enables service-aware traffic steering for optimization and offloading
• Supports traffic segregation for security, charging, and performance isolation
• UE-based enforcement reduces core network signaling overhead

Evolution Across Releases

Defining Specifications