2026-06-18 👁️ — views

AV V2X Communication — How Vehicles Talk to Infrastructure, Each Other and Pedestrians

V2X lets AVs share data with traffic signals, other vehicles, and pedestrians — extending perception beyond sensor range with predictive wireless communication.

Article 58 in the Physical AI Benchmark Series — The Wireless Perception Layer

Every camera, LIDAR, and radar onboard an autonomous vehicle shares one fundamental limitation: physics. Sensors can only perceive what is within range and in line of sight. An AV approaching an intersection at 45 mph cannot see the delivery truck that ran a red light one block over — until it is already too late to react comfortably. V2X (Vehicle-to-Everything) is the wireless communication layer designed to solve exactly this problem. Instead of waiting for a sensor to detect a hazard, a V2X-equipped vehicle receives a broadcast from the hazard itself, or from infrastructure that already knows the hazard exists.

This article maps what V2X enables, how the two competing wireless standards differ, and how Tesla and Waymo have approached infrastructure connectivity in fundamentally different ways.

Section 1 — What V2X Enables That Sensors Cannot

Onboard sensors (cameras, LIDAR, radar) only see what is within range and line-of-sight. V2X extends perception beyond the sensor horizon by making the environment itself a data source.

The critical advantage is temporal: V2X is predictive (know what will happen) while sensors are reactive (respond to what you see). At highway speeds, a 200 ms earlier warning translates to approximately 4 meters of additional stopping distance — the difference between a comfortable deceleration and an emergency brake.

The V2X stack is further divided by communication mode:

• PC5 sidelink (direct mode): Vehicle-to-vehicle and vehicle-to-infrastructure communication without any network infrastructure, operating at low latency over the 5.9 GHz band. Works in tunnels, rural roads, and any location without cellular coverage.
• Uu mode (network-assisted): Communication routed through cellular base stations, enabling longer range and connection to cloud services (V2N). Requires network coverage.

The two modes are complementary: PC5 handles safety-critical low-latency use cases; Uu handles map updates, traffic management, and fleet coordination.

Section 2 — The Two Standards: C-V2X vs DSRC

The V2X industry has spent a decade divided between two competing wireless standards. The resolution of that competition has significant consequences for which cities and vehicles will be V2X-compatible.

The decisive US event was the FCC’s November 2020 order reallocating the upper 30 MHz of the 5.9 GHz band — the portion DSRC relied on most — to unlicensed WiFi. The lower 30 MHz was retained for C-V2X. This effectively ended the US DSRC investment case and cleared the regulatory path for C-V2X as the dominant standard in North America.

In practice, a city that deployed DSRC RSUs in the 2015–2020 wave (Tampa, Columbus, parts of Detroit) now faces a hardware replacement decision. C-V2X RSUs are not backward-compatible with DSRC vehicle receivers without a software bridge, though some equipment vendors offer dual-mode hardware.

Section 3 — Tesla’s Connectivity Approach

Tesla has not publicly committed to deploying V2X hardware as of mid-2026 (est.). The current Tesla connectivity model reflects its foundational philosophy: autonomous driving should be achievable with onboard sensors and neural networks, without dependence on roadside infrastructure.

The Tesla philosophy has a coherent internal logic: V2X requires infrastructure investment that is outside Tesla’s control, and building a system that depends on that infrastructure creates a deployment constraint. An AV that works everywhere without roadside equipment is more commercially flexible than one that only works optimally in V2X-equipped corridors.

The counter-argument is that V2X handles scenarios that even a perfect sensor suite cannot — a vehicle broadcasting an emergency stop from around a blind corner is information that no camera or LIDAR in the trailing vehicle can generate independently.

Section 4 — Waymo’s Infrastructure Connectivity

Waymo’s approach reflects a different philosophy: a robotaxi operator that partners with cities has both the incentive and the mechanism to integrate with city-controlled infrastructure data.

The SPaT integration is worth emphasis. SPaT (Signal Phase and Timing) is part of the BSM/MAP/SPaT message set standardized by SAE J2735 — the same message format used by both DSRC and C-V2X systems. A Waymo vehicle receiving SPaT data from a city traffic management system knows not just that a light is green, but exactly how many seconds remain until it turns yellow. This enables smoother speed profiles, more comfortable passenger experience, and reduced energy consumption — benefits that compound across a dense urban fleet.

The Waymo model requires active city partnerships and data-sharing agreements, which varies by city and political administration. Tampa and Columbus have been the most active US testbeds; San Francisco’s dense signal grid makes it a high-value integration target.

Section 5 — The Infrastructure Investment Gap

V2X’s full safety potential requires roadside infrastructure: RSUs (Roadside Units) at intersections that broadcast signal timing, hazard data, and receive vehicle broadcasts. The infrastructure gap is the primary constraint on V2X deployment.

The economic case for RSU deployment is real but requires coordination across multiple stakeholders: city transportation departments (who own the signals), state DOTs (who fund major corridors), federal highway programs (who set standards and provide grants), vehicle OEMs (who decide what hardware ships at the factory), and cellular carriers (who provide the network layer for Uu-mode V2X). No single stakeholder controls the full chain.

China has resolved this coordination problem through central policy mandate: the government simultaneously required RSU deployment on national highways and required C-V2X hardware in domestically sold vehicles above a certain category. The result is the world’s most extensive V2X infrastructure network, even if the connected vehicle market it serves is primarily domestic.

The investor signal from V2X infrastructure deployment is worth tracking. Cities that deploy C-V2X RSUs at intersections are building the data layer that reduces AV operating costs — fewer edge-case failures at signalized intersections, better speed optimization reducing energy consumption, and earlier hazard detection reducing safety-critical events. The Waymo city-partnership model may prove more durable than a sensor-only approach if C-V2X becomes the baseline expectation for urban AV deployment. Conversely, if V2X remains fragmented and sparse, Tesla’s infrastructure-independent architecture avoids the deployment dependency entirely.

Sources: FCC 5.9 GHz spectrum reallocation order — fcc.gov (November 2020); USDOT V2X deployment program — transportation.gov/av/v2x; Qualcomm C-V2X technology overview — qualcomm.com/products/automotive/connected-car/c-v2x; Waymo blog and technology overview — waymo.com/blog/. All figures marked (est.) are estimates derived from public company materials, industry reporting, and analyst research. They have not been independently verified and should be treated as directional. This article does not constitute investment advice.

Sources

• FCC 5.9 GHz spectrum reallocation — FCC ↗
• USDOT V2X deployment program — US DOT ↗
• Qualcomm C-V2X technology overview — Qualcomm ↗
• Waymo SPaT signal integration — Waymo blog ↗

Tags