V2X allows a connected vehicle to share or receive useful information beyond what its onboard cameras, radar or LiDAR can directly see. Depending on the system, that information may come from another vehicle, a traffic signal, a pedestrian device or a mobile network.
The main types of V2X
V2X is not one single connection. It is a family of communication paths. The most common terms are V2V, V2I, V2P and V2N.
V2V — Vehicle-to-Vehicle
Vehicles exchange information such as position, speed, heading or warnings. A practical use could be alerting one vehicle to another approaching an intersection even when buildings or other traffic block direct line of sight.
V2I — Vehicle-to-Infrastructure
The vehicle communicates with roadside infrastructure such as traffic signals, road-side units or traffic-management systems. This can support intersection warnings, signal information, road-hazard alerts and traffic coordination.
V2P — Vehicle-to-Pedestrian
This category covers communication involving vulnerable road users such as pedestrians or cyclists, typically through compatible devices or infrastructure that can help make their presence known to equipped vehicles.
V2N — Vehicle-to-Network
The vehicle communicates through a cellular network with cloud or backend services. V2N can carry traffic information, connected services and other data that does not need to come directly from a nearby road user.
How does V2X work?
Different V2X systems can use different radio technologies and network architectures. A major modern approach is C-V2X, or Cellular Vehicle-to-Everything.
5GAA describes C-V2X as the umbrella for 3GPP-based V2X technologies. It combines two broad communication modes:
- Direct communication (PC5): nearby vehicles, infrastructure or road-user devices can communicate directly, without needing the message to travel through the cellular network.
- Network communication (Uu): the vehicle uses the mobile network to reach cloud or backend services, enabling V2N applications and wider-area information exchange.
LTE-V2X was standardized in 3GPP Release 14, while 5G/NR-V2X work arrived in Release 16 to support more advanced connected and automated-driving use cases.
V2X vs C-V2X: what is the difference?
V2X is the broad concept. C-V2X is a specific family of V2X technologies based on 3GPP cellular standards.
| Term | Meaning | What it describes |
|---|---|---|
| V2X | Vehicle-to-Everything | The overall connected-vehicle communication concept. |
| C-V2X | Cellular Vehicle-to-Everything | 3GPP cellular-based V2X, covering direct and network communication. |
| 5G / NR-V2X | 5G New Radio V2X | Later-generation V2X capabilities designed for more demanding connected and automated-driving use cases. |
| V2N2X | Vehicle-to-Network-to-Everything | A network/backend architecture where the mobile network helps connect vehicles to other vehicles, infrastructure or services. |
What is V2N2X?
V2N2X means vehicle-to-network-to-everything. Instead of relying only on a short-range direct connection, the mobile network and backend systems become part of the information path.
This newer terminology matters because many future connected-vehicle services may combine direct PC5 messages with network-based Uu communication rather than choosing only one method. 5GAA's 2026 dynamic-V2X work specifically examines how direct and network-based communication can complement one another in safety use cases.
Why does V2X matter?
A vehicle's cameras, radar and LiDAR are powerful, but they are still limited by line of sight, range and environmental conditions. V2X can add information from beyond the vehicle's own sensors.
Is V2X the same as autonomous driving?
No. V2X is a communication technology, not an autonomous-driving level.
A vehicle can use V2X without being self-driving, and an automated-driving system can operate using onboard sensors without depending on V2X. In practice, V2X can complement cameras, radar, LiDAR and vehicle software by providing information those sensors may not yet be able to observe directly. For the difference between connectivity and driverless operation, see Level 4 autonomous driving and robotaxis.
What are the limitations of V2X?
- Deployment coverage: benefits vary depending on how many vehicles and roads are equipped.
- Interoperability: vehicles and infrastructure need compatible standards and message formats.
- Security and trust: safety-related messages need reliable authentication and protection against malicious or incorrect data.
- Privacy: connected systems must handle location and mobility data carefully.
- Data quality: receiving a message is not enough; the system also needs confidence that the information is timely and accurate.
Where is V2X heading in 2026?
V2X is moving beyond basic vehicle-awareness messages toward more dynamic and cooperative use cases. In July 2026, 5GAA published work covering intersection safety, vulnerable road users, soft intersections and high-speed rear-end collision scenarios, with direct PC5 and network-based Uu communication working together.
The U.S. Department of Transportation also has a national V2X deployment plan focused on accelerating connected-vehicle deployment for safety, mobility and efficiency. This means V2X is increasingly moving from standards and trials toward broader real-world deployment.
Get notified about important V2X updates
We follow vehicle-to-everything technology as it develops. Get occasional updates when important V2X standards, deployments or safety applications change.
V2X standards, deployments and major technology updates. Unsubscribe anytime.
Occasional editorial emails only, after review. No automatic newsletters. For removal requests: editor@carglossary.com.
Manage / unsubscribeV2X mapping, data platforms and future product brands
As V2X moves from standards and pilots into deployed infrastructure, new products will need to map coverage, visualize roadside units, exchange V2X data and expose connected-mobility services through software. Two useful naming directions are V2X mapping and V2X data / I/O platforms. The examples below show how those ideas can translate into product names without presenting them as formal industry standards.
V2XIO / V2X I/O
V2XIO reads naturally as “V2X I/O” — vehicle-to-everything input/output. That makes it a flexible name for a V2X software platform, API layer, middleware company, message broker, data exchange, edge gateway or developer infrastructure product.
- Strength: broad enough to support software, data and infrastructure rather than one narrow application.
- Brand signal: technical, developer-friendly and infrastructure-oriented.
- Possible future positioning: “the I/O layer for connected mobility.”
V2XMap.com
V2XMap is more descriptive. It could fit a company or product that maps V2X infrastructure, roadside units, coverage, intersections, connected corridors, message activity or deployment readiness.
- Strength: the use case is easy to understand from the name alone.
- Brand signal: geospatial, deployment-planning and visualization focused.
- Possible future positioning: “the map layer for V2X infrastructure.”
V2XIO is the broader brand if the business could expand across APIs, edge software, data exchange and V2X infrastructure. V2XMap is clearer for a mapping, deployment-intelligence or infrastructure-visualization product. Neither name guarantees commercial success; product fit, trademark clearance and market execution matter more than the domain alone.
Disclosure: V2XIO.com and V2XMap.com are publisher-owned domains shown here as real naming examples. This section is branding analysis, not an industry standard or a claim that these names are affiliated with V2X standards bodies.
Related terms
V2X terminology is still evolving. We distinguish broad concepts from specific standards and update this page as deployments and standards change.
Real-world V2X examples: what messages can a connected car exchange?
V2X is a broad category, not a single radio or app. The usefulness of each feature depends on compatible equipment, software, security credentials, infrastructure and local deployment.
- V2V: a nearby equipped vehicle can broadcast position or motion information to support awareness beyond direct line of sight.
- V2I: compatible roadside infrastructure may share signal-phase information, road warnings or roadworks notices.
- V2P: compatible systems may support warnings involving vulnerable road users, but availability is not universal and must not replace driver attention.
- V2N: network services can deliver cloud data, navigation updates and wider-area information; this is not the same communication path as direct short-range V2X.
Start with C-V2X for the cellular standards family, 5G NR-V2X for newer direct-communication capabilities, and ADAS to understand why receiving safety messages is not the same as automated control.
V2X for students and researchers: project ideas and study tools
V2X is also a useful research topic in wireless communications, transport engineering, cybersecurity and automated mobility. Research goes beyond asking whether vehicles can exchange messages: it tests when those messages arrive, whether they can be trusted, and whether they improve a real road-safety scenario.
V2X research questions worth investigating
- Intersection safety: How do warning timing and missed alerts change when an approaching vehicle is hidden from direct view?
- Direct vs network communication: How do packet delivery and delay vary between direct C-V2X PC5 and network-assisted Uu paths under different traffic and coverage assumptions?
- Mixed vehicle fleets: What happens to a warning application's effectiveness when only some vehicles or roadside units support V2X?
- Security and privacy: How should an application handle stale, spoofed or contradictory messages without exposing unnecessary location history?
A manageable student simulation project
Start with an intersection collision-warning scenario. Model vehicles approaching a junction, then compare a baseline with no cooperative messages against one where compatible vehicles exchange warnings. Vary traffic density, the share of equipped vehicles, message loss and network delay. Record packet delivery ratio, message latency, warning lead time and missed or false warnings. State your assumptions clearly: a simulation is not evidence that a feature is deployed or proven safe on public roads.
Standards, technical reports and simulation tools
- 3GPP TR 38.885 — a technical study of NR-V2X, useful for standards terminology and communication assumptions.
- 5GAA dynamic V2X use cases (July 2026) — intersection safety, vulnerable road users and complementary PC5/Uu communication evaluated with models, simulations and real-world data.
- Eclipse SUMO V2X documentation — guidance on coupling a road-traffic simulator to communication-network simulators.
- Eclipse MOSAIC getting-started tutorial — a practical route to combined traffic and V2X-message simulation.
For a strong report, separate communication metrics (such as delivery and latency) from traffic or safety outcomes (such as warning lead time), and document the scenario, software versions and limitations so another student can reproduce your experiment.