Description
The V2X Application Specific Server (VASS) is an application-layer entity in the 3GPP V2X architecture that provides vehicle-to-everything services to UEs (vehicles, roadside units, and pedestrian devices). It was introduced in Release 18 as part of the V2X service evolution and is specified in TR 23.700 and TS 29.486. The VASS sits above the 5G core and interacts with the V2X control function, the UDR, and the network exposure function to deliver application-specific services. Unlike generic application servers, the VASS is aware of V2X-specific requirements such as low latency, high reliability, and location-based service discovery.
Architecturally, the VASS communicates with the 5GC through the N6 reference point or via the NEF for exposure of capabilities. It may host multiple V2X applications, each identified by a V2X Application ID and associated with a set of service requirements. The VASS registers with the V2X control function (e.g., the V2X Application Server (VAS) or the 5G V2X control function) and provides service information that the network uses for UE configuration. When a UE requests V2X service, the network can direct it to the appropriate VASS based on location, application ID, and policy.
The VASS plays a key role in PC5 and Uu-based V2X communication. For Uu-based communication, the VASS provides the application server endpoint for V2X messages, and the 5GC establishes the necessary PDU sessions with appropriate QoS. For PC5-based communication, the VASS may provide configuration information such as the V2X service parameters, radio resource pools, and security credentials that the UE uses for direct sidelink communication. The VASS also supports service continuity when vehicles move across different network slices or PLMNs.
Key components of the VASS include the application hosting environment, the service registration and discovery function, the QoS mapping function, and the interface to the V2X control function. The VASS uses the Service Based Architecture (SBA) principles of 5G, exposing its capabilities via APIs defined in TS 29.486. These APIs allow the network to query VASS capabilities, subscribe to service events, and configure V2X service parameters. The VASS also interacts with the UDM/UDR for subscriber-specific V2X authorization and with the PCF for policy control.
VASS is important because it decouples V2X application logic from the underlying network, allowing third-party service providers to deploy V2X services without deep integration into the operator's core. It enables use cases such as cooperative lane change, intersection collision warning, and platooning by providing a standardized way for vehicles to discover and access application servers. The Release 18 specification builds on earlier V2X work (Releases 14-17) by introducing a more flexible, service-based architecture for V2X application servers.
Purpose & Motivation
VASS was created to provide a standardized, service-based architecture for hosting V2X applications in 5G networks. Earlier V2X deployments in Releases 14-17 relied on a monolithic V2X Application Server (VAS) that combined control and application functions, making it difficult for third-party providers to deploy services and for operators to manage multiple V2X applications. The VASS separates application-specific logic from network control, enabling a more modular and scalable ecosystem.
The motivation also comes from the diverse requirements of V2X services. Different applications (e.g., platooning, sensor sharing, remote driving) have different latency, reliability, and throughput needs. A generic application server cannot efficiently handle these variations. The VASS allows each application to define its own QoS requirements and service parameters, which the 5GC can then enforce through network slicing and policy control.
Another key driver is interoperability and multi-vendor deployment. By defining standardized APIs in TS 29.486, the VASS enables operators to integrate V2X servers from different vendors and allows service providers to offer V2X services across multiple networks. This is essential for automotive use cases where vehicles roam across regions and need consistent service. Introduced in Release 18, VASS is part of the broader 5G V2X evolution toward automated driving and intelligent transportation systems.
What changed in its specifications
The latest release-to-release comparison of specifications that define VASS. Each summary describes the whole specification, not only this term.
Adding Individual Message Delivery Subscription creation, a subscriptionId parameter, a reception report request flag, and feature negotiation. Also adding NotifyReceptionReport and Downlink Message Delivery Reception Reporting.
Full comparison in TS 29.486 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference VASS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 29.486 vj40 | V2X Application Enabler (VAE) Protocol; Stage 3 | Rel-19 read |