Connected vehicle systems depend on more than a link between a car and a cellular network. C-V2X, or cellular vehicle-to-everything communication, describes a set of communication paths that can connect vehicles to one another, pedestrians, networks and road infrastructure. The technology’s evolution from Release 14/15 toward Release 16 5G NR was designed to extend established safety messaging to more demanding applications, including sensor sharing and coordinated driving.
For industrial automation professionals, the broader significance is a shift toward distributed intelligence. Vehicles, roadside units (RSUs), communications networks and cloud services can contribute information to a shared understanding of road conditions. The practical value depends on how reliably and promptly those systems exchange relevant data.
C-V2X: Four communication paths
C-V2X covers several complementary forms of communication. Each supports a different relationship between a vehicle and its surroundings:
- Vehicle-to-vehicle (V2V): Vehicles exchange information, supporting applications such as collision-avoidance safety systems.
- Vehicle-to-pedestrian (V2P): Communications can deliver safety alerts to pedestrians and bicyclists.
- Vehicle-to-infrastructure (V2I): Vehicles communicate with road equipment, such as traffic signals or roadside units.
- Vehicle-to-network (V2N): Connectivity to networks can support services such as traffic and route information, cloud access and telematics.
The Release 14/15 C-V2X standards established a foundation focused on safety. In the 2019 roadmap described in the whitepaper, Release 16 5G NR C-V2X was positioned as a complementary development for advanced use cases. The intended approach retained support for earlier safety communications while adding capabilities for richer direct communication.
Why 5G NR C-V2X expands the use-case conversation
Basic safety messages and advanced cooperative applications place different demands on a communications system. Applications that exchange sensor information or driving intentions may need to carry more data, deliver it with low latency and provide reliable reception among relevant vehicles. The Release 16 design described in the source was intended to address these requirements through a more flexible direct communication link.
Potential applications include:
- Real-time infrastructure updates: An RSU could share information such as a 3D high-definition map update that reflects a lane closure or road hazard.
- Sensor sharing: Vehicles could communicate information about their perception of nearby conditions, extending situational awareness beyond what another vehicle’s own sensors detect.
- Intention sharing: Vehicles could exchange information about planned actions, such as a requested lane change, to support more predictable coordinated maneuvers.
- Increased situational awareness: Vehicle-specific information, such as a door-open warning, could be shared with nearby vehicles and infrastructure.
These examples rely on more than radio connectivity alone. Applications must interpret incoming information, determine whether it is relevant, and connect it to vehicle or infrastructure functions. Edge computing, artificial intelligence, sensor fusion and precise positioning are presented as parts of this wider connected transportation environment.
How connected vehicles and infrastructure work together
A smart vehicle can combine inputs from cameras, radar, lidar and localization systems to build a view of its surroundings. An RSU equipped with sensing and computing capabilities can contribute another perspective, for example by detecting a pedestrian or a hazard. With infrastructure-to-vehicle communication, that information can be sent to approaching vehicles; direct V2P communication is another possible route for a pedestrian alert.
Similarly, an RSU could distribute an updated map indicating that construction has changed the lane layout. A vehicle approaching the work zone could use that update alongside its onboard sensing. This illustrates the role of connectivity as an augmentation to perception—not a replacement for vehicle sensors or the systems that make driving decisions.
Connectivity to a wider network can support different needs. V2N can provide access to cloud-based services and traffic information, while roadside communications can connect road sensors and cameras. The source describes this as a unified connectivity fabric: multiple links serving applications that range from immediate local safety messages to broader transportation services.
Communication design for advanced applications
The Release 16 approach described in the whitepaper builds on earlier C-V2X foundations while introducing design elements intended for advanced direct communication. These include flexible slot-based operation, an OFDM-based air interface, and communication methods such as multicast. The design also emphasizes application awareness, so communication can be tailored to the needs and relevance of a particular use case.
One example is forming connectionless, distance-based groups “on the fly.” Vehicles approaching the same intersection could form a group for a coordinated application, then stop participating once the maneuver is complete. Another is distance-aware messaging: a receiving vehicle need only respond to information relevant to its application and location.
The whitepaper also describes multicast with feedback as a way to improve reliability. In the stated approach, receivers that cannot decode a transmission can send a negative acknowledgment (NACK). This differs from broadcast without feedback, where the sender does not receive that indication. The aim is to support more reliable delivery while limiting unnecessary responses from vehicles for which a message is not relevant.
Interoperability and deployment considerations
Advanced applications require agreement on the messages vehicles exchange, their minimum requirements and how systems from different manufacturers interpret them. The source points to work in regional higher-layer protocol standards, including SAE and ETSI ITS, as part of enabling interoperability.
Backward compatibility is also central to the described evolution. Release 16 vehicles were expected to support Release 14/15 for safety, allowing the newer capabilities to build on established communication profiles rather than displacing them. The source further notes that sensor sharing and infrastructure deployments could provide benefits during early rollout, including situations where some vehicles do not have C-V2X. For example, a connected vehicle could detect a non-C-V2X vehicle with its onboard sensors and share the resulting object information.
Practical implications for automation and transportation
C-V2X’s evolution shows how connected transportation can extend beyond point-to-point data exchange. As vehicles and roadside systems share more timely, application-relevant information, they can support improved awareness of hazards, road changes and other vehicles’ intentions. The proposed outcomes include safer driving, more coordinated maneuvers and potential improvements in travel and energy efficiency.
Realizing those outcomes requires coordination across communications, sensing, computing, infrastructure and standards. For engineers and decision-makers, the key takeaway is to view C-V2X as one layer in a distributed transportation system. Its contribution depends on interoperable messages, suitable communications performance and integration with the perception and control capabilities that act on the information.