Description
Aircraft-to-Everything Policy (A2XP) is a comprehensive policy control framework standardized by 3GPP to govern communication services involving aircraft. It operates within the 5G core network's Policy Control Function (PCF), extending policy management to the unique requirements of aerial vehicles. The framework handles scenarios where the User Equipment (UE) is located on an aircraft, which could be the aircraft itself (as an aerial UE) or passenger devices connecting via an onboard access network. A2XP policies are distinct because they must account for the aircraft's mobility in three dimensions, high velocity, and the specific service requirements for both operational/crew communications (A2A, A2G) and passenger connectivity.
The architecture integrates with existing 5G policy and charging control (PCC) architecture. Key network functions involved include the PCF, which is the central entity for A2XP policy decisions; the Access and Mobility Management Function (AMF) and Session Management Function (SMF), which enforce policies related to access, mobility, and session management; and the Unified Data Management (UDM), which stores subscriber and policy data. For A2XP, the PCF consumes specific input such as the aircraft's identity, flight status, location, altitude, and the type of service (e.g., safety-critical telemetry vs. passenger broadband) to derive appropriate policy rules. These rules are then provided to the SMF and AMF as Policy and Charging Control (PCC) rules or Access and Mobility Policy (AMP) rules.
A2XP policies cover several critical dimensions. They manage Quality of Service (QoS) by assigning specific 5QI (5G QoS Identifier) values tailored for aviation services, ensuring low latency for command and control or guaranteed bandwidth for cockpit communications. Mobility policies are crucial, dictating handover strategies between ground base stations and potentially satellite or airborne network nodes (Non-Terrestrial Networks - NTN) as the aircraft traverses different flight phases and jurisdictions. Security policies are enhanced to protect against threats specific to aerial connectivity, including secure authentication of the aircraft and isolation of critical operational traffic from passenger traffic. Furthermore, A2XP enables network slicing for aviation, allowing the creation of dedicated slices for airline operations, air traffic management, or inflight entertainment, each with its own isolated resources and performance guarantees.
The framework's operation is dynamic and context-aware. For instance, during takeoff and landing, policies might prioritize ultra-reliable low-latency communication (URLLC) slices for telemetry and restrict bandwidth-heavy passenger services. During cruise, policies could enable high-throughput broadband slices for passengers while maintaining a separate, secure slice for operational data. Charging policies under A2XP can also be specialized, supporting models like flat-rate for the duration of a flight or volume-based charging for specific service types. By centralizing this logic in the PCF, A2XP provides a standardized, scalable way for mobile network operators and aviation service providers to offer managed, billable, and secure connectivity services to the aviation industry.
Purpose & Motivation
A2XP was created to address the lack of a standardized policy framework for integrating aircraft communications into 5G mobile networks. Prior to 3GPP's work, connectivity for aircraft relied on proprietary systems (e.g., for Air-to-Ground communications) or satellite links, which were often expensive, offered limited bandwidth, and lacked seamless integration with terrestrial mobile networks. The proliferation of consumer devices on aircraft and the aviation industry's need for digitalization—including real-time aircraft health monitoring, optimized flight paths, and enhanced passenger experience—created a demand for cost-effective, high-performance, and globally interoperable connectivity solutions.
The primary problem A2XP solves is the policy management gap for aerial User Equipment (UE). A ground-based UE's policy is based on factors like subscriber profile and location. An aircraft, however, introduces new dimensions: three-dimensional location (including altitude), high-speed mobility across multiple network and national borders, and the co-existence of critical flight operations with commercial passenger services on the same platform. Without A2XP, network operators would have to use generic policies or develop non-standard extensions, leading to fragmentation, security vulnerabilities, and an inability to guarantee service-level agreements (SLAs) for aviation-specific applications like low-latency drone control or in-flight emergency communications.
Historically, the motivation stems from 3GPP's broader initiative to support Vertical and LAN Services, including the '5G for Aviation' work item. The creation of A2XP in Release-18 was driven by the need to provide a unified policy control plane that understands aviation context. It enables the commercial and technical feasibility of using 5G as a primary or complementary access technology for aviation, paving the way for new business models for Mobile Network Operators (MNOs), airlines, and air traffic management authorities. It addresses limitations of previous non-integrated approaches by ensuring aviation traffic receives appropriate network resources, security treatment, and mobility support directly within the standardized 5G core network architecture.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the standardization work focused on correcting and clarifying the technical implementation of the Aircraft-to-Everything Policy (A2XP) function. This included resolving encoding issues for A2XP-related UE policies and correcting the procedures for A2XP determination and provisioning to the UE. Furthermore, the specifications were updated to fix references to the correct clauses detailing how A2XP provides configuration parameters for A2X communication over PC5 or Uu interfaces.
Explore further
Broader topics and technologies where A2XP plays a role.
Defining Specifications
3GPP specifications that define or reference A2XP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.503 vk00 | 5G Policy and Charging Control Framework | Rel-20 |
| TS 24.526 vj30 | UE Policies for 5GS; Stage 3 | Rel-19 |
| TS 24.577 vj10 | A2X Services in 5GS | Rel-19 |
| TS 24.578 vj00 | UE policies for A2X services in 5GS | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |