Description
The Vehicle-to-Everything Application Server (V2X AS) is a critical network entity within the 3GPP service-based architecture, specifically designed to support V2X communication services. It operates within the core network's application layer, interfacing with other network functions like the Unified Data Management (UDM), Network Exposure Function (NEF), and the V2X Control Function. The V2X AS hosts the application logic for various V2X services, such as Cooperative Awareness Messages (CAM), Decentralized Environmental Notification Messages (DENM), and other V2X application-specific functionalities. It is responsible for service authorization, configuration management for UEs engaged in V2X communication, and potentially for application-layer message routing or processing, especially for network-assisted V2X communication modes.
Architecturally, the V2X AS can support different V2X communication modes defined by 3GPP: direct communication (PC5 interface) and network-based communication (Uu interface). For PC5-based communication, the V2X AS, often in conjunction with the V2X Control Function, provides necessary parameters to the UE, such as authorization policies, ProSe Per-Packet Priority (PPPP), and configuration for the sidelink radio interface. For Uu-based communication, it can act as an application server that communicates with UEs via the network, enabling wider dissemination of messages or access to cloud-based V2X services. The V2X AS interfaces with the UDM to retrieve subscription data for V2X service authorization and with the Policy Control Function (PCF) for policy enforcement related to V2X services.
Its role extends to managing the V2X service area, which defines the geographical region where a UE is authorized to perform V2X communications. The V2X AS may also interact with external V2X application providers or the V2X Control Function to translate service requirements into network policies. In later releases, its functionality evolved to support more advanced services, including collective perception of the environment and coordinated driving maneuvers, requiring more sophisticated data aggregation, processing, and low-latency distribution capabilities. The V2X AS is therefore not just a simple server but a key orchestrator that bridges V2X application requirements with the capabilities of the 3GPP network, ensuring secure, reliable, and efficient service delivery for connected vehicles.
Purpose & Motivation
The V2X AS was created to provide a standardized, network-based platform for hosting and managing V2X applications within the cellular ecosystem. Prior to its specification, V2X communication was primarily based on dedicated short-range communication (DSRC) standards like IEEE 802.11p, which lacked seamless integration with wide-area cellular networks for service management, security, and scalability. The integration of V2X services into the 3GPP architecture, starting in Release 14, was motivated by the automotive industry's need for a global, future-proof solution that leverages ubiquitous cellular coverage, network security frameworks, and evolving 5G capabilities for advanced automated driving.
The V2X AS solves the problem of how to efficiently authorize, configure, and manage a massive number of vehicular UEs (V-UEs) and their V2X services. It provides a centralized point for service logic and policy enforcement, which is crucial for safety-critical applications. Without such a network function, managing service parameters, security credentials, and geographic service areas for millions of vehicles would be highly inefficient and insecure. The V2X AS enables network operators and service providers to offer differentiated V2X services, ensures that UEs only operate where authorized, and paves the way for network-assisted and network-scheduled V2X communication, which improves reliability and resource utilization compared to purely distributed ad-hoc approaches.
Key Features
- Hosts application logic for V2X services (e.g., CAM, DENM)
- Provides V2X service authorization and configuration management for UEs
- Manages V2X service areas and associated parameters
- Interfaces with core network functions (UDM, PCF, NEF) for policy and subscription
- Supports both direct (PC5) and network-based (Uu) V2X communication modes
- May facilitate message routing and aggregation for network-assisted V2X
Evolution Across Releases
Introduced the V2X AS as part of the initial 3GPP LTE-based V2X architecture. It provided basic support for V2X service authorization, UE parameter provisioning for PC5-based communication, and definition of V2X service areas. It laid the foundation for integrating V2X into the cellular network.
Enhanced the architecture to support 5G system integration. The V2X AS's interactions within the 5G core network's service-based architecture were defined, including interfaces with the NEF and UDM. Support for NR-based V2X sidelink communication began.
Introduced enhanced V2X (eV2X) services with more demanding requirements. The V2X AS's role expanded to support advanced use cases like vehicle platooning, extended sensors, and remote driving, requiring more sophisticated service management and QoS handling.
Further enhancements for sidelink and NR V2X, including support for sidelink relay and improvements for operation in higher frequency ranges (e.g., 52.6 GHz - 71 GHz). The V2X AS's capabilities were refined to support these new radio features and associated service requirements.
Continued evolution within the 5G-Advanced framework, focusing on system efficiency and support for expanded use cases. Work likely included enhancements for reduced capability (RedCap) V2X devices, improved power efficiency, and tighter integration with network slicing for V2X.
Ongoing development within 5G-Advanced, expected to include further optimizations for autonomous driving, AI/ML integration for V2X services, and support for more complex collaborative automated driving applications, impacting the data processing and distribution functions of the V2X AS.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.786 | 3GPP TS 23.786 |
| TS 36.101 | 3GPP TR 36.101 |
| TS 36.785 | 3GPP TR 36.785 |
| TS 36.786 | 3GPP TR 36.786 |
| TS 36.787 | 3GPP TR 36.787 |
| TS 36.788 | 3GPP TR 36.788 |
| TS 38.304 | 3GPP TR 38.304 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.785 | 3GPP TR 38.785 |
| TS 38.786 | 3GPP TR 38.786 |
| TS 38.787 | 3GPP TR 38.787 |
| TS 38.807 | 3GPP TR 38.807 |
| TS 38.808 | 3GPP TR 38.808 |
| TS 38.846 | 3GPP TR 38.846 |
| TS 38.859 | 3GPP TR 38.859 |
| TS 38.868 | 3GPP TR 38.868 |
| TS 38.886 | 3GPP TR 38.886 |
| TS 38.913 | 3GPP TR 38.913 |