Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

V2V Service

Vehicle-to-Vehicle Service

Services →

V2V Service is a V2X service in which both communicating parties are UEs equipped on different vehicles, underpinning cooperative safety applications such as collision avoidance, platooning and cooperative awareness.

Introduced
Rel-14
Where
Services › Codecs
Specifications
3 specs
V2V Service Description Purpose Neighbours Specifications

Description

V2V (Vehicle-to-Vehicle) Service is one of the core V2X service types defined by 3GPP, describing communication in which both parties are UEs installed on different vehicles. It is the most prominent V2X service type because many cooperative intelligent transport system (C-ITS) safety applications — forward collision warnings, emergency electronic brake lights, cooperative adaptive cruise control and platooning — depend on low-latency, high-reliability exchange of status and intent information directly between vehicles.

V2V is defined at the service level in TS 22.885 and its architecture is specified in TS 23.785 for LTE-based V2X and in TS 23.287 for 5G V2X. The service can be realized over two transport paths. The first is direct communication over the PC5 sidelink, where vehicle UEs exchange V2X messages without traversing the network infrastructure; this is essential for low latency and for operation outside network coverage. The second is network-based communication over the Uu interface, where V2X messages are sent to and distributed by the network, for example via a V2X application server or the V2X Control Function. 3GPP supports both modes and allows a UE to use them in combination.

In the direct mode, the radio layer provides the necessary enablers: sidelink resource allocation (Mode 3/4 in LTE, Mode 1/2 in NR), synchronization, and QoS handling for V2X messages. The V2X Control Function provides authorization and provisioning — it tells the UE whether it is authorized to use V2V services, what radio parameters to use, and how to map V2X service types to QoS. Security for V2X is handled through the V2X security framework, which provides confidentiality and integrity protection for V2X messages, with credentials managed via the V2X Control Function and the security infrastructure defined in the relevant specifications.

V2V messages are V2X messages carrying V2X application layer information, typically cooperative awareness messages (CAM) or decentralized environmental notification messages (DENM) in the European ITS profile, or basic safety messages (BSM) in other profiles. 3GPP does not define the application payloads but specifies the transport, QoS, authorization and radio mechanisms that carry them. Performance requirements for V2V are stringent: TS 22.885 sets targets for latency (on the order of tens of milliseconds), reliability and range that reflect the safety-critical nature of the applications.

With 5G NR sidelink in Rel-16 and beyond, V2V gains improved capabilities: unicast, groupcast and broadcast communication, more flexible and reliable resource allocation, and better support for high-density scenarios. These enhancements make V2V better suited to advanced use cases such as platooning and cooperative maneuvering, where vehicles must exchange information with high reliability and low latency. V2V is thus a foundational service concept for connected and automated driving.

Purpose & Motivation

V2V Service exists to provide a standardized cellular framework for direct and network-assisted communication between vehicles. Before Rel-14, vehicle safety communication was addressed by dedicated short-range communication (DSRC) technologies outside the 3GPP ecosystem, which had limited integration with cellular networks, no unified QoS and authorization framework, and no path to wide-area network assistance. 3GPP introduced V2V in Rel-14 as part of LTE-based V2X to bring vehicle communication into the cellular system, leveraging licensed spectrum, operator management and a common architecture.

The concept solves the problem of enabling low-latency, high-reliability exchange of safety information between vehicles in a standardized way. By defining V2V as a service type and specifying PC5 sidelink transport, 3GPP enabled vehicles to communicate directly without infrastructure round-trips, which is essential for collision avoidance where latency budgets are tight. At the same time, the network-based path allows operators to provide coverage extension, message distribution and management functions.

Historically, V2V was motivated by the vision of cooperative intelligent transport systems and by regulatory interest in vehicle safety. The Rel-14 definition focused on the physical relationship — UEs on different vehicles — while Rel-15 reworded it to focus on the application type used by both parties, reflecting a maturation of the service concept from a device-placement description to an application-centric one. The subsequent evolution through NR sidelink has extended V2V toward more demanding automated driving use cases.

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.

Rel-14 Initial

V2V Service was introduced as a type of V2X Service where both parties of the communication are UEs equipped on different vehicles. This established the initial LTE-based V2X architecture with PC5 sidelink (Mode 3/4) and Uu transport options, plus V2X Control Function authorization.

The definition wording was revised to: 'A type of V2X Service, where both parties of the communication are UEs using V2V application.' The change moved the definition from a device-placement description (UEs on different vehicles) to an application-centric one (UEs using V2V application), paralleling the V2P rewording.

The Rel-15 wording ('both parties of the communication are UEs using V2V application') carried over unchanged, while NR sidelink introduced unicast, groupcast and broadcast capabilities that significantly enhanced V2V transport.

The definition remained unchanged from Rel-15/Rel-16; the term carried over as-is while Rel-17 sidelink enhancements continued to develop the surrounding capabilities.

The definition text was unchanged from previous releases; V2V continued to be referenced within the evolving V2X and sidelink framework.

The definition remained unchanged; the term carried over into Rel-19 without textual modification.

Defining Specifications

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

SpecificationTitleRelease
TS 22.885 ve00 LTE Support for V2X Services Rel-14 read
TR 23.785 ve00 Architecture enhancements for LTE V2X services Rel-14 read
TR 26.985 vj00 Media Handling for Advanced V2X Services Rel-19 read