V2X case studies — how it was actually deployed.
There is a large body of standards work describing what could be built, and a large body of press coverage describing what was announced. There is very little that says, with sources, what was actually fitted to which cars and how the message really travelled.
This section is that record. Seven implementation studies and one global audit, each classified by architecture rather than by marketing term, each carrying its evidence and its review date. They are studies of other organisations' deployments — Ambimat built none of them.
Industry implementation studies, not customer stories.
These are studies of other organisations' deployments, assembled from public evidence. Ambimat did not build, supply, integrate or advise on any of the systems described in this section, and nothing on these pages should be read as a customer relationship, a partnership or an endorsement. Where a manufacturer, supplier or agency is named, it is named because the public record names it.
The reason to write them is that the V2X literature has a gap in the middle. There is a large body of standards work describing what could be built, and a large body of press coverage describing what was announced. There is very little that says, with sources: this manufacturer put this radio in these cars in these markets, the message goes along this exact path, and this is what happened to it afterwards.
Each study answers the same questions in the same order, so that two implementations can be compared rather than merely described: what was deployed, whether it is genuinely vehicle-to-vehicle, when and where, the full communication path, the radio and spectrum, the message standards, what is publicly known about security, the suppliers where confirmed, the use cases, the interoperability boundary, the scale, what happened next, and the engineering lesson.
Six categories, because “V2X” is not one architecture.
Every system in this section carries one of these labels, and the label is the first thing each study states. The boundary that does the most work is between the first two.
| Label | What it means |
|---|---|
| Direct production V2V | Customer vehicles with a local radio link — ITS-G5, DSRC, C-V2X PC5 or a national ITS band. No network operator in the path. |
| Cloud-mediated production | The vehicle originates the hazard, but it travels over the mobile network through a manufacturer backend to reach other vehicles. |
| Infrastructure or fleet V2X | The hazard originates from an emergency vehicle, a work zone, a road operator or a signal controller rather than from a passenger car. |
| Historical production | A genuine production system that has since been discontinued, superseded or withdrawn. Kept, because the reasons are the most transferable part of the record. |
| Pilot only | Field trials, demonstrations and announced fitment. Never presented as deployment, whatever the scale. |
| No production evidence found | Investigated against the same sources; the evidence does not substantiate a deployment. Recorded rather than omitted. |
The global audit.
One page covering every manufacturer investigated, the comparison matrix, the regional analysis, the negative findings, and the reasoning behind each classification. The individual studies below go deeper on the implementations where the evidence supports it.
Which manufacturers actually deployed V2V
A global architecture audit: four manufacturers with direct production V2V, the cloud-mediated systems that are frequently mistaken for it, the historical deployments, the pilots, and the manufacturers where nothing could be verified.
The V2X market landscape
The commercial companion: who ships, who quietly stopped, the Tier 1 and silicon layer, and the alliances. Market view rather than architecture view.
Seven implementations with enough public evidence to be worth the depth.
Volkswagen Car2X
Direct production V2V. Europe, from 2019. More than two million vehicles produced, 5.9 GHz, no mobile network in the warning path.
Toyota ITS Connect
Direct production V2V. Japan, from 2015, on the 760 MHz national ITS band — and unusable anywhere else because of it.
Cadillac V2V
Historical production. The only DSRC vehicle sold in the United States, model years 2017 to 2019, and the regulatory sequence that ended it.
Mercedes-Benz Car-to-X
Cloud-mediated production. Standard with navigation since 2016, over the mobile network through the manufacturer's backend.
Volvo Connected Safety
Cloud-mediated production. Hazard Light Alert and Slippery Road Alert, from 2016, and a public invitation to pool the data.
Stellantis and HAAS Alert
Infrastructure and fleet V2X. About 1.8 million vehicles receiving emergency-fleet alerts. None of them transmits anything.
Audi Traffic Light Information
Infrastructure V2X over cellular. Signal data since 2016 — and a service bulletin recording what happens when the backend outlives the car.
What had to be true before anything was written down.
- Manufacturer, regulator and standards-body material first. Then government transport agencies, consortium and public-project documentation, peer-reviewed work, and finally reputable technical press. Social posts can start an investigation; they never finish one.
- A supplier naming a customer is a supplier claim. It is recorded with its source and marked as such, not converted into a manufacturer statement.
- A capable modem is not a service. Silicon that supports a radio does not put that radio into use, and no manufacturer is credited with a deployment on that basis.
- Where the record stops, the page says so. Chipsets, certificate architectures, ranges and latencies appear only where somebody with standing published them. Not publicly disclosed is used deliberately and often.
- Standards do not evidence implementations. That a specification requires message signing is a fact about the specification. Whether a given manufacturer implemented it that way is a separate question with a separate answer, and the two are kept apart.
Each study carries its own review date. Where evidence conflicts, the conflict is described rather than resolved in favour of the more interesting reading.
Where this fits.
V2V
The message set, the nine specified applications, and why value scales with the square of fitment.
DSRC vs C-V2X
The two radio families behind every direct deployment in this section, compared properly.
Tesla and the sensor-first argument
The case for building a vehicle that needs nobody else, stated fairly and then answered.
India regulation
A framework being assembled before any fitment exists — the inverse of every case in this section.
V2X PKI
Why a direct system needs a receiver that can judge an anonymous message offline, in milliseconds.
V2X use cases
The standards catalogue behind the functions these deployments actually shipped.
Questions this page answers.
Are these Ambimat customer case studies?
No. They are industry implementation studies assembled from public sources. Ambimat did not build, supply, integrate or advise on any of the systems described, and nothing in this section should be read as a customer relationship, a partnership or an endorsement. Where a manufacturer or supplier is named, it is named because the public record names it.
How is a deployment classified?
Into one of six categories: direct production V2V, where customer vehicles carry a local radio link with no network operator in the path; cloud-mediated production, where the vehicle originates a hazard but it travels over the mobile network through a manufacturer backend; infrastructure or fleet V2X, where the hazard comes from an emergency vehicle, work zone or signal controller rather than a passenger car; historical production, for systems since discontinued; pilot only; and no production evidence found.
Why does the difference between direct and cloud-mediated V2X matter?
Because the two architectures fail differently, scale differently and cost differently. Direct radio delivers tens of milliseconds of latency, works with no network coverage and interoperates across manufacturers by construction, but delivers almost nothing until a large fraction of the fleet is equipped. A cloud path has unlimited range and delivers value from the first equipped car, but cannot support crash-imminent warnings, stops working without mobile coverage, and reaches other manufacturers only by commercial agreement.
Which manufacturers have genuine direct vehicle-to-vehicle communication in production?
Volkswagen Group in Europe at volume, Toyota and Lexus in Japan on the 760 MHz national ITS band, BMW on one China-market model, Ford on China-market models, and roughly thirty models across Chinese manufacturers. General Motors did it in the United States between model years 2017 and 2019 and stopped. Everything else frequently described as V2V is cloud-mediated cooperative safety, infrastructure-sourced alerting, or onboard sensing.
What evidence standard do these studies use?
Manufacturer, regulator and standards-body material first, then government transport agencies, consortium and public-project documentation, peer-reviewed work and reputable technical press. A supplier naming a customer is recorded as a supplier claim rather than restated as fact. A V2X-capable modem is never treated as a V2X service. Where the public record stops, the page states that it is not publicly disclosed rather than inferring.
Last updated 2026-09-08 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: neel.shah@ambimat.com