Vehicle-to-vehicle — the mode with the largest safety case and the hardest deployment problem.
V2V is the original V2X. Every equipped vehicle broadcasts its own state ten times a second, in the clear, to anything in range; every equipped vehicle listens to everything it receives, verifies the signature, and hands the result to its safety applications. There is no infrastructure, no network and no negotiation. It is the simplest architecture in the whole field and the one that has proved hardest to actually deploy.
One message, ten times a second, roughly 300 bytes.
In North America the message is the Basic Safety Message, SAE J2735 message ID 20, with on-board system requirements set by SAE J2945/1 for DSRC and SAE J3161/1 for LTE-V2X. It has two parts.
Part I is mandatory and present in every transmission: temporary ID, sub-second timestamp, latitude, longitude, elevation and a positional accuracy set, transmission state, speed, heading, steering wheel angle, a three-axis acceleration set, brake system status, and vehicle size.
Part II is optional and mostly event-driven: the vehicle safety extension carrying event flags (hard braking, ABS, traction control, stability control, hazard lights, wipers), path history, path prediction, RTCM corrections, and supplemental vehicle extensions.
A signed BSM over the air is typically 200 to 400 bytes; the 5GAA performance testing used a 193-byte payload.
In Europe the equivalent is the Cooperative Awareness Message, originally ETSI EN 302 637-2 and now carried into Release 2 as ETSI TS 103 900, currently at V2.3.1 (May 2026). Where the BSM is a fixed 10 Hz, the CAM is adaptive between 1 and 10 Hz, triggered by a 4 metre position change, a 4 degree heading change, a 0.5 m/s speed change, or a one-second timer. Event-driven hazards are carried separately as DENM (EN 302 637-3, Release 2 as TS 103 831). The message sets in full →
Nine that the standards bodies have actually specified.
| Application | What it does |
|---|---|
| Forward Collision Warning | Warns of an impending rear-end collision with a vehicle ahead in the same lane |
| Emergency Electronic Brake Light | Propagates a hard-braking event from a vehicle the driver cannot see |
| Blind Spot / Lane Change Warning | Warns of a vehicle in the adjacent lane blind spot during a lane change |
| Intersection Movement Assist | Warns when it is unsafe to enter an intersection because of a high collision probability |
| Do Not Pass Warning | Warns against overtaking into oncoming traffic |
| Control Loss Warning | Broadcasts a loss-of-control event to surrounding vehicles |
| Emergency Vehicle Alert | Announces an approaching emergency vehicle beyond siren range |
| Wrong-Way Driving Alert | Warns of a vehicle travelling against the direction of traffic |
| Platooning / cooperative lane change | Coordinated multi-vehicle manoeuvres, Day 2 and beyond |
India's draft AIS-230 specifies four to begin with: Emergency Brake Alert, Forward Collision Warning, Wrong-Way Driving Alert and Emergency Vehicle Alert. India's V2X framework →
V2V value scales with the square of fitment. This is the whole story.
For a V2V safety application to fire, two equipped vehicles must be in the same conflict at the same time. If a fraction p of the fleet is equipped, the fraction of conflicts in which both parties are equipped is roughly p². At 5% fitment, that is a quarter of one percent of encounters — effectively no benefit, for 100% of the cost.
Compare V2I: a single equipped intersection delivers benefit to every equipped vehicle that passes it. Value accrues linearly in vehicle penetration and begins immediately.
This asymmetry explains almost everything about the deployment record. The V2X services that actually exist in the field are V2I-flavoured — traffic-light information, signal priority, work-zone warnings. The V2V safety case, the one carrying the large fatality-reduction estimates, has never bootstrapped anywhere except where a regulator or a single high-volume OEM forced it. Volkswagen has crossed the threshold in Europe by fitting Car2X as standard or as a cheap option: more than two million Volkswagen models produced with Car2X for Europe, announced 27 October 2025. India's proposed approach is the other lever — mandate the whole fleet at once.
The p² argument is structural. No authoritative published fitment threshold exists, and the ITS America 2024 report explicitly declines to establish one, so no percentage is stated here.
Where this fits.
V2I
Linear returns, and why the deployed services are infrastructure-flavoured.
Message sets
The BSM field list, the CAM triggers, and the DENM split.
C-V2X
The radio these messages ride, and the congestion control around them.
The OEM landscape
Who has crossed the fitment threshold and who has stopped trying.
AmbiOBU
The on-board unit development platform, and the partner we are looking for.
Pseudonymity and privacy
How a 10 Hz broadcast avoids becoming a tracking beacon.
Questions this page answers.
What does V2V mean?
Vehicle-to-vehicle. Direct wireless exchange of safety-relevant state between vehicles, with no infrastructure or network involved.
How often does a vehicle send a V2V message?
In North America, the Basic Safety Message is sent at a nominal 10 Hz — ten times a second — with a congestion-control algorithm in SAE J2945/1 that adapts rate and power as vehicle density and channel load rise. In Europe the Cooperative Awareness Message is adaptive between 1 and 10 Hz, driven by how much the vehicle's state has changed since the last transmission.
Can V2V messages be faked?
Only by an attacker holding a valid, unrevoked private key and its certificate. That is exactly why the standards require the key to be generated and held inside tamper-resistant hardware — a device with an extractable signing key can be cloned into an unlimited number of validly-signed ghost vehicles, and the PKI cannot detect it, because the messages are genuinely valid. Threats and attacks.
Does V2V identify the vehicle?
No. Messages are signed with short-lived pseudonymous certificates that carry no registration number, VIN, IMEI or persistent identifier, and are rotated on a schedule — typically at a random interval between 10 and 30 minutes in the European profile, alongside a synchronised change of every identifier at every layer of the stack. Pseudonymity and privacy.