Description
The V2X service identifier is a fundamental naming construct in the 3GPP V2X ecosystem. It is an identifier of a V2X service, for example a Provider Service Identifier (PSID), an Intelligent Transport Systems Application Identifier (ITS-AID), or an Application Identifier (AID) of the V2X application. These identifier forms originate from external V2X standards bodies — PSIDs from IEEE 1609 / SAE J2735, ITS-AIDs from ISO/ETSI ITS station architecture, and AIDs from ETSI — and 3GPP reuses them so that cellular V2X can interoperate with existing intelligent transport systems. The term V2X service identifier used in the 24.3xx service aspects specifications corresponds to the term V2X service type defined in 3GPP TS 23.287, which is the architecture specification for 5G V2X services.
Architecturally, the V2X service identifier sits at the boundary between the application layer and the 3GPP network. A V2X application on the UE (e.g., a cooperative awareness or platooning application) is associated with one or more V2X service identifiers. When the UE requests V2X communication, it signals the relevant identifiers to the network — for example in the PC5 policy provisioning procedures defined in TS 24.386 (V2X over LTE), TS 24.486 (V2X over 5G), and TS 24.587 (5G V2X, later releases). The network uses these identifiers to authorize the UE for specific services, to select the appropriate V2X configuration (radio parameters, QoS, spectrum), and to apply charging and policy rules.
In the PC5 sidelink path, the V2X service identifier is mapped to a destination Layer-2 ID and to a PC5 QoS flow. The UE's V2X configuration (provisioned via the V1 reference point, i.e., the V2X control function or PCF) contains a mapping between V2X service identifiers and the parameters needed to transmit: destination L2 ID, V2X frequency, Tx profile, and PC5 5QI. This mapping is what allows a UE to autonomously select radio resources for a given application without per-packet signalling to the network.
In the Uu path, the V2X service identifier is used during PDU session establishment or modification to indicate the V2X service being requested, so that the SMF/PCF can authorize the service and the UPF can apply the correct traffic handling. The identifier also appears in the V2X application server discovery and in the service authorization procedures, ensuring that only UEs entitled to a given V2X service can transmit or receive it.
The identifier is therefore a cross-layer key: it binds an application to a QoS treatment, a radio configuration, and an authorization decision. Because it is defined by external standards, it also enables a single V2X service to be delivered over multiple access technologies (LTE PC5, NR PC5, Uu) while retaining a consistent identity.
Purpose & Motivation
The V2X service identifier exists to give a stable, globally meaningful name to each V2X application so that the 3GPP network can treat it correctly. Without such an identifier, the network would have no way to know which application a UE's traffic belongs to, and therefore no way to authorize it, apply the right QoS, or select the right radio configuration. By reusing PSID, ITS-AID, and AID from the ITS standards world, 3GPP avoids inventing a parallel namespace and ensures that a vehicle's cooperative awareness message means the same thing whether it travels over cellular sidelink or over a non-3GPP ITS link.
The identifier also solves the authorization and charging problem. Operators need to know which V2X services a subscriber is entitled to and how to bill for them; the V2X service identifier provides the granularity for both. It further enables policy-based provisioning: the network can push a configuration that maps each identifier to a destination L2 ID and QoS profile, letting the UE operate autonomously in out-of-coverage or resource-selection modes.
Historically, the concept was introduced in Release 14 alongside LTE V2X (TS 23.285) and the V2X service aspects in TS 24.386. Release 16 extended it to 5G V2X with the AID form and aligned the terminology with TS 23.287, reflecting the broader 5G V2X architecture that supports advanced services such as vehicle platooning, extended sensors, and remote driving.
What changed in its specifications
The latest release-to-release comparison of specifications that define V2X service identifier. Each summary describes the whole specification, not only this term.
Added NR-PC5 configuration parameters, new 5G V2X spec references, extended PC5 QoS profiles, UDP/TCP port configuration, and updated V2X server address discovery over LTE-Uu.
Full comparison in TS 24.386 →Rel-18 adds VRU zone monitoring and management procedures, V2P schedule configuration/update, new terms and XML elements, plus expanded application layer support for V2X services.
Full comparison in TS 24.486 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference V2X service identifier, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.386 vj00 | V2X Communication Protocols and Procedures | Rel-19 read |
| TS 24.486 vj00 | V2X Application Enabler (VAE) Protocol Spec | Rel-19 read |
| TS 24.587 vj30 | V2X Services Protocols for 5G System | Rel-19 read |