What V2X is — and what it is not.
V2X lets vehicles and road infrastructure talk to each other.
A car equipped with it broadcasts a short message about ten times a second saying, in effect: here I am, this is how fast I am going, this is the direction I am pointed in, and I have just braked hard. Every other equipped vehicle nearby hears it. Traffic signals broadcast too — this light turns red in 2.4 seconds. So do roadworks, emergency vehicles, and in time the phone in a pedestrian's pocket.
The point is not convenience. It is that radio goes where a driver's eyes and a car's cameras cannot: around the corner, through the fog, behind the truck, over the crest of the hill. A vehicle can be warned about something it has no way of seeing.
The name is a family, not one thing. V2X — vehicle-to-everything — covers vehicles talking to other vehicles (V2V), to roadside infrastructure like traffic signals (V2I), to the mobile network (V2N), and to pedestrians and cyclists (V2P). The “X” is just a placeholder for whatever is at the other end.
In one sentence: V2X is a shared language that lets vehicles and roads warn each other about things nobody can see yet.
Standardised messages, not a data pipe.
V2X is the wireless exchange of standardised, structured messages between a vehicle and everything around it. Not a data pipe, not telemetry, not “the connected car” as a marketing category. A specific set of message formats, sent at specific rates, carrying specific fields, signed with a specific certificate type, so that a receiver built by one company can act on a message sent by a device built by another.
The reason it exists is narrow and physical: every sensor on a vehicle is a line-of-sight sensor, and most crashes involve something the driver could not see.
Cameras, radar and lidar cannot see around corners.
A forward camera has a useful range of roughly 100 to 150 metres. Automotive radar reaches 200 to 250 metres. Lidar is in the same territory. All three degrade in fog, heavy rain, snow, glare and darkness, and all three stop entirely at an occlusion. No camera sees through a truck. No lidar sees around a building.
That matters because occlusion is where crashes happen: the urban intersection with a blind approach, the stopped vehicle beyond a crest, the pedestrian stepping out between parked cars, the queue that begins just past a curve.
Radio at 5.9 GHz diffracts around corners and propagates through and around structures well enough to deliver a message where an optical sensor has zero information. In the field testing 5GAA conducted against the FCC record, C-V2X achieved 1,050 metres line-of-sight range against DSRC's 625 metres, and 600 to 800 metres at 90% reliability in a non-line-of-sight intersection scenario where DSRC managed 90 to 400 metres. Both figures are far beyond any onboard sensor. Those are 5GAA's own measurements, submitted into a regulatory proceeding; they are attributed rather than neutral. The full comparison.
V2X carries data that cannot be observed at all.
Range is only half of it. A Basic Safety Message contains fields that no external sensor can infer:
- brake system status, including whether ABS, traction control or stability control is currently engaged
- a hard-braking event flag
- exterior light and wiper state
- path history — where the vehicle has actually been over the last several seconds
- path prediction — the radius the vehicle is currently tracking
- steering wheel angle
- vehicle size, so a receiver knows whether it is dealing with a scooter or an articulated truck
An infrastructure message goes further. A Signal Phase and Timing message does not describe the light as it is; it describes the light as it will be, with a countdown. There is no optical way to know that. The message sets in detail.
Six that matter for ITS, three more that are about electricity.
| Mode | Between | Carried by | Typical messages |
|---|---|---|---|
| V2V | Vehicle and vehicle | PC5 sidelink or ITS-G5, direct | BSM (US) · CAM, DENM (EU) |
| V2I | Vehicle and roadside unit | PC5 sidelink or ITS-G5, direct | SPaT, MAP, TIM, RSA, SRM/SSM · SPATEM, MAPEM, IVIM, SREM/SSEM |
| V2N | Vehicle and cellular network | Uu, the conventional cellular interface | Hazard feeds, HD map tiles, MEC-assisted services, OTA |
| V2P | Vehicle and a vulnerable road user's device | PC5 sidelink | PSM (US, per SAE J2945/9) · VAM (EU, per ETSI TS 103 300-3) |
| V2D | Vehicle and an arbitrary personal or peripheral device | Usually Bluetooth or Wi-Fi | No standardised safety message set |
| V2C | Vehicle and an OEM cloud back end | Uu | Proprietary, plus SAE probe messages (PVD, PDM) |
| V2G | EV and the electrical grid | The charging cable — not 5.9 GHz | ISO 15118-20 |
| V2H | EV and a home electrical panel | The charging cable | ISO 15118-20, CHAdeMO |
| V2L | EV and a plugged-in appliance | On-board inverter, no protocol | None |
The distinction in the last three rows is not pedantry. V2G, V2H and V2L share the “V2” prefix and nothing else. They run over powerline communication on the charging cable, use a completely different standards family, and have no relationship to the 5.9 GHz ITS radio, the ITS station architecture or V2X PKI. Conflating them is the single most common error in V2X writing. The energy modes, and why they are not ITS →
V2D and V2C are industry terms, not standards terms. Neither appears as a defined mode in any SAE or ETSI deliverable. They are useful descriptive shorthand and should be read as such.
One hundred milliseconds for Day 1. Three for what comes after.
Day-1 safety messaging targets an end-to-end latency budget of 100 ms. Measured mean end-to-end latency for a 193-byte packet on a clean channel is 14 to 15 ms for C-V2X and 16 to 17 ms for DSRC — comfortably inside it. The difference shows up under congestion, where C-V2X stays inside the budget and DSRC's latency tail grows, because C-V2X allocates resources by sensing and semi-persistent scheduling rather than by contention.
3GPP TS 22.186 sets far harder targets for the advanced use cases:
| Use case | Latency | Reliability | Payload / rate |
|---|---|---|---|
| Platooning, highest automation | 10 ms | 99.99% | 50–1,200 B at 30 msg/s, 80 m range |
| Cooperative collision avoidance | 10 ms | 99.99% | 2,000 B at 100 msg/s, 10 Mbit/s |
| Emergency trajectory alignment | 30 ms | 99.999% | 2,000 B, 500 m range |
| Extended sensors, highest automation | 3 ms | 99.999% | 50 Mbit/s, 200 m range |
| Remote driving | 5 ms | 99.999% | 25 Mbit/s uplink, up to 250 km/h |
Those numbers are why NR-V2X exists, and why a 30 MHz spectrum allocation is widely argued to be insufficient in the long run. Spectrum, jurisdiction by jurisdiction.
Four things it is routinely confused with.
- It is not telematics. A connected truck reporting its location to a fleet back office over LTE is V2N or V2C at best. It carries no standardised safety message, participates in no ITS PKI and is invisible to other road users. Volvo Trucks' one million connected trucks, announced September 2025, is a telematics figure, not a V2X figure.
- It is not autonomous driving. V2X is an input to a perception stack. It makes no driving decision, and nothing in the standards requires the vehicle to act on a received message.
- It is not a cloud service. Volvo Cars' Hazard Light Alert and Slippery Road Alert, and Audi's Traffic Light Information, are genuine, useful, deployed cooperative services — delivered over cellular, through an OEM back end, with latency measured in seconds. They solve a different problem from direct PC5 messaging, and they solve it today at scale. But a cloud round trip cannot support intersection movement assist.
- It is not bidirectional charging. See above.
The sensor-first counter-argument — that a manufacturer should build a vehicle that needs nobody else — is a serious one, and it is stated as strongly as it can be on the sensor-first argument page.
Where this fits in the bigger picture.
How V2X works
Six steps, a blind-intersection example, and the four parts inside an on-board unit.
What V2X is for
Safety, traffic efficiency and emissions, with the field-versus-simulation distinction kept.
V2V
The largest safety case, and the hardest deployment problem.
V2I
The mode that pays back first, because value accrues linearly.
C-V2X
PC5 and Uu, and the 3GPP release history behind them.
AmbiSecure connected mobility
Why V2X infrastructure demands hardware-backed identity, from the security business unit.
Working out where V2X fits in your product?
Bring the constraint that is actually binding — BOM cost, thermal envelope, certification timeline, or the PKI you have to interoperate with. We will bring an architecture sketch.
Questions this page answers.
What is the difference between V2X and C-V2X?
V2X describes what is communicated — the applications and message sets. C-V2X describes how, over a 3GPP-defined cellular sidelink. The alternative radio is DSRC, based on IEEE 802.11p and called ITS-G5 in Europe. The same ETSI message, byte for byte, can ride either radio; the access layer is deliberately separable from the facilities layer.
What is the difference between V2X and V2V?
V2V is one mode of V2X — vehicle to vehicle. V2X is the umbrella covering V2V, V2I, V2N, V2P and the rest.
How far does V2X reach?
In 5GAA field testing, C-V2X achieved 1,050 metres in line-of-sight conditions and 600 to 800 metres at 90% reliability in a non-line-of-sight urban intersection scenario. Real-world range depends on antenna placement, transmit power, terrain and channel load, and safety applications are typically engineered around a few hundred metres rather than the maximum achievable.
Does V2X work without a mobile network?
Yes, for the safety modes. V2V, V2I and V2P run over the PC5 sidelink, which is a direct device-to-device link with no base station in the path. It works with no SIM, no subscription and no coverage. C-V2X does require GNSS time synchronisation for the radio, which is a genuine deployment consideration in tunnels and urban canyons — though a device can synchronise from a neighbouring device acting as a reference.
How much does a V2X on-board unit cost?
Indian press coverage of the MoRTH draft cited an estimate of ₹5,000 to ₹7,000 per vehicle (roughly US$60 to US$85). That figure comes from secondary trade coverage of the draft, not from the notification itself, and it is a significant fraction of the cost of an entry-level two-wheeler. Expect it to be contested in the consultation.
Is V2X secure?
Every V2X message in a compliant deployment is cryptographically signed, and every receiver verifies the signature before acting. The security model is well specified — IEEE 1609.2 in North America, ETSI TS 103 097 and TS 102 941 in Europe. The hard parts are not the cryptography. They are key custody in a device an attacker can physically hold, verification throughput under load, and revocation at national scale. V2X security.
What are the main V2X use cases?
The specified Day-1 set is: forward collision warning, emergency electronic brake light, blind spot and lane change warning, intersection movement assist, do-not-pass warning, control loss warning, emergency vehicle alert, wrong-way driving alert, and on the infrastructure side signal phase and timing, green-light optimal speed advisory, red-light violation warning, work-zone warning, and signal priority for transit and emergency vehicles. Day 2 adds collective perception and vulnerable-road-user awareness; Day 3 adds manoeuvre coordination and platooning.
Is V2X the same as ADAS?
No. ADAS is the set of driver-assistance functions a vehicle runs on its own sensors — automatic emergency braking, lane keeping, adaptive cruise. V2X is an additional information source those functions can consume. In practice V2X data feeds the same perception and decision layer that camera and radar data feeds; it does not replace it and it does not constitute a driving function by itself.
What is the difference between V2X and telematics?
Telematics is a vehicle reporting data to a back office over a cellular network — location, diagnostics, driver behaviour — for the benefit of whoever operates that back office. V2X is a vehicle exchanging standardised safety messages with other road users and infrastructure, in a common format any compliant device can act on, usually over a direct radio link with no network involved. A connected fleet is not a V2X fleet.