V2XP

Vehicle-to-Everything Policy

Management →
Introduced in Rel-16 Also in: User Equipment

V2XP is a framework for defining and enforcing rules that govern V2X communication sessions, determining how network resources are allocated and managed based on service parameters to ensure safety-critical messages receive necessary treatment.

Category
Management
Introduced
Rel-16
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
8 specs
V2XP Description Purpose Detected Changes Specifications

Description

Vehicle-to-Everything Policy (V2XP) refers to the set of rules and parameters that govern the behavior and resource allocation for V2X communication within a 3GPP network. It is a specialized subset of the broader Policy and Charging Control (PCC) framework, tailored specifically for the unique requirements of V2X services, which often involve low latency, high reliability, and dynamic geographic constraints. The V2XP framework is implemented and enforced by the Policy Control Function (PCF) in the 5G core network. The PCF generates V2XP rules based on input from the V2X Application Server (V2X AS), network operator configurations, and subscriber information from the Unified Data Management (UDM).

These policies are then delivered to the relevant network functions and the User Equipment (UE). For network-based communication (Uu), V2XP rules are provided to the Session Management Function (SMF) and Access and Mobility Management Function (AMF) to influence QoS flows, packet forwarding, and session management. For direct communication over the PC5 sidelink, V2XP rules are provided to the UE to govern its behavior on the sidelink interface. Key parameters within a V2XP rule include the ProSe Per-Packet Priority (PPPP), ProSe Per-Packet Reliability (PPPR), allowed V2X service areas, maximum transmission power, and resource allocation modes (scheduled vs. autonomous). The PCF may also provide V2X-specific Policy and Charging Control (PCC) rules that include parameters for charging and QoS enforcement.

The operation of V2XP involves dynamic policy decisions. For instance, when a UE initiates a V2X service, the V2X AS may request a specific policy from the PCF based on the service type (e.g., basic safety vs. advanced teleoperation). The PCF evaluates this request against the user's subscription and network conditions to formulate the appropriate V2XP. This policy is then activated and enforced for the duration of the V2X session. V2XP is crucial for managing radio congestion, especially in dense vehicular scenarios, by prioritizing safety messages and efficiently allocating sidelink resources. It provides a standardized mechanism for the network to control and optimize V2X communication, ensuring that the diverse and stringent requirements of different V2X applications are met consistently across the network.

Purpose & Motivation

V2XP was created to address the need for granular, dynamic, and service-aware control over V2X communications within the 3GPP policy framework. Early V2X implementations, including the initial Release 14 specifications, had policy mechanisms but the formalized V2XP framework, emphasized from Release 16 onwards, was driven by the introduction of more advanced and diverse eV2X services. These new services (e.g., platooning, remote driving) have vastly different requirements in terms of latency, reliability, data rate, and communication range compared to basic safety messages. A one-size-fits-all policy approach was insufficient.

The V2XP framework solves the problem of how to efficiently map diverse V2X application requirements onto network and radio resources. It allows the network operator and service provider to define policies that dictate, for example, that a collision-avoidance message must have higher priority and lower latency than an infotainment-related V2X update. This is critical for managing limited radio spectrum, preventing congestion, and ensuring that safety-of-life messages are never delayed due to network resource contention. V2XP also enables service differentiation and monetization, as operators can offer tiered V2X service levels with corresponding policy guarantees. By integrating V2X policy into the core PCC architecture, 3GPP ensured that V2X communication could be managed with the same robustness, security, and scalability as traditional cellular services.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 3 changes

In Release 16, the V2X Policy (V2XP) function was formally introduced to provide configuration parameters for Vehicle-to-Everything communication over both PC5 and Uu reference points. The release included corrections and refinements to the V2XP UE policy definitions and its information contents, integrating them into the overall policy framework. Furthermore, it specified procedures for UE-triggered V2X policy provisioning from the PCF and defined the methods for configuring this policy to the UE, including pre-configuration and provisioning priorities.

  • Corrections in V2XP UE policy part TS 24.588CR0014
  • Correction of V2XP statement TS 24.588CR0017
  • Include V2XP info contents into policy section TS 29.525CR0098
Rel-17 4 changes

In Release 17, the enhancements for the V2X Policy (V2XP) function included refining the procedures for how and when the policy is requested by the UE. Specifically, changes were made to allow the request of V2XP during the NAS Transport procedure, while also enabling the removal of the request for V2XP during the initial registration process. Furthermore, work was done on the selection of the Policy Control Function (PCF) responsible for providing the V2XP.

  • PCF selection for V2XP and ProSe TS 29.513CR0374
  • Removal of the request of V2XP and/or ProSeP during registration TS 29.525CR0223
  • Request of V2XP/ProSeP during NAS Transport procedure TS 29.513CR0371
  • Request of ProSeP/V2XP during NAS Transport procedure TS 29.525CR0211
Rel-18 1 change

In Release 18, a key update for the V2X Policy (V2XP) function was the removal of the V2XP and ProSe Policy (ProSeP) during the UE registration procedure. This change streamlined the initial registration process by not including these specific policy provisions at that stage, though the UE can still request V2XP from the Policy Control Function (PCF) via a separate UE-triggered provisioning procedure afterwards.

  • Removal of V2XP/ProSeP during registration TS 29.513CR0425
Rel-19 1 change

In Release 19, the key enhancement for the V2X Policy (V2XP) function was the introduction of a standardized method for the storage of its configuration information alongside other policies like ProSeP and A2XP within the Access Network Discovery and Selection Policy (ANDSP) framework. This allows for the pre-configuration of V2XP parameters to the UE, which are applied only when the same policy type is not received dynamically from the Policy Control Function (PCF). The update formalizes the integration of V2XP into the broader UE policy management architecture, utilizing existing Npcf and Namf service operations for provisioning.

  • Storage of UPSI(s) for ProSeP, V2XP, A2XP, RSLPP, and N3AN node configuration information of ANDSP TS 24.501CR6665

Explore further

Broader topics and technologies where V2XP plays a role.

Defining Specifications

3GPP specifications that define or reference V2XP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.503 vk00 5G Policy and Charging Control Framework Rel-20
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.526 vj30 UE Policies for 5GS; Stage 3 Rel-19
TS 24.587 vj30 V2X Services Protocols for 5G System Rel-19
TS 24.588 vj00 UE Policies for V2X Services in 5GS Rel-19
TR 26.941 vj01 5G Media Slicing Extensions 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
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.