V2X and Connected Vehicle Technology, a Decade After the First Pilots

Vehicle-to-everything communication is older than the robotaxi industry it was supposed to support.

V2X lets a vehicle exchange data directly with other vehicles and with infrastructure, traffic signals, road sensors, rather than relying only on what its own cameras and radar can see. The pitch was straightforward: a car could know a traffic light is about to change, or that a vehicle three cars ahead just braked hard, before its own sensors had any way to detect it. None of that requires the vehicle to see the light or the other car directly; the information arrives ahead of what onboard perception could ever pick up on its own.

What actually slowed things down was a standards fight. Two competing technical approaches, DSRC and C-V2X, split early deployment efforts for years, with different regulators, automakers and suppliers backing one or the other and neither side gaining enough ground to force a unified rollout. The timing cost the industry years. Infrastructure built around one standard doesn't help a vehicle equipped for the other, so the split effectively meant two smaller, incompatible rollouts instead of one large one, and a piece of roadside equipment installed for the wrong protocol was, for practical purposes, invisible to half the vehicles that might have used it.

Retrofitting existing intersections adds another layer of friction on top of the standards question. Equipping a traffic signal for V2X isn't a software update; it typically means new hardware at the intersection itself, and a city has to decide which intersections get it first, a slow-moving budget and planning exercise that has little to do with how good the underlying technology actually is.

Underneath the standards fight is a more basic network-effect problem. V2X only delivers value once enough vehicles and enough infrastructure both have it installed, and neither side has much incentive to move first. An automaker equipping a handful of models with V2X hardware gains little if the traffic signals those vehicles pass are still unequipped, and a city investing in V2X-capable signals gains little if the vehicles on its roads mostly can't talk to them. That's a familiar problem with any technology that only works as a network rather than as a standalone feature, and it's harder to solve through incremental adoption than most standalone vehicle features are, because early movers on either side see comparatively little payoff for going first.

Closed fleets illustrate the same network-effect problem in reverse. A transit agency or a logistics operator that controls both the vehicles and the relevant infrastructure can roll out V2X without waiting for anyone else to move first, precisely because it doesn't have to coordinate with an outside party on either end. That's a meaningfully smaller version of the deployment problem than the passenger-vehicle market as a whole faces, which is one reason V2X's more concrete successes tend to cluster in fleet and transit contexts rather than in general consumer vehicles.

Regulatory decisions have also reshaped the picture over time, not just the industry's own choices. The radio spectrum originally set aside for one of the two competing standards has since been reallocated in part for other uses, which changed the practical footing under a technology that was already struggling to gain traction. A standard losing dedicated spectrum after years of being positioned as the future of connected roads is a setback that's hard to recover momentum from, regardless of how sound the underlying technical case for V2X still is.

The result, a decade on, is that most deployed automated-driving systems rely primarily on onboard perception, the same sensor mix described in the rundown of lidar, radar and camera-only approaches, rather than on V2X. That's not necessarily permanent. But for now V2X functions as a complement to onboard sensing rather than something an automated-driving stack actually depends on to operate.