Access Official Technical PDF

Share Summary:LinkedInEmail

Cellular vehicle-to-everything (C-V2X) is not simply a radio link between cars. It is part of a broader connected-mobility system that brings together vehicles, mobile networks, roadside infrastructure, devices and software. For industrial automation professionals, its development offers a useful example of how cross-industry standards, system integration and field testing shape complex, safety-related applications.

The 5G Automotive Association (5GAA), established to connect automotive and telecommunications companies, described this work as an effort to develop end-to-end solutions for future mobility and transportation services. Its scope included technical, business and regulatory challenges, reflecting a central reality of connected transport: no single supplier or network layer can deliver the complete system alone.

Why C-V2X depends on a connected ecosystem

Vehicle connectivity involves several layers of technology and organizations. Automotive companies contribute vehicle platforms, hardware and software. Telecommunications companies bring connectivity, network systems and devices. Other participants include semiconductor and wireless-radio suppliers, automotive tiers, mobile network operators, test and verification organizations, public bodies, testbeds and researchers.

This range of stakeholders matters because vehicle-to-everything (V2X) services must work across equipment and networks from different providers. A vehicle communicating with another vehicle, a network or a road user’s device depends on compatible interfaces and coordinated system behavior. Interoperability is therefore a design and deployment requirement, not an optional feature to address after development.

5GAA organized its work around five areas: use cases and technical requirements; system architecture and solution development; evaluation, testbeds and pilots; standards and spectrum; and business models and go-to-market strategies. This structure highlights the lifecycle involved in bringing a communication technology into practical use—from defining what a service must do through validating it and planning its deployment.

C-V2X use cases define different system demands

Requirements for next-generation V2X communications vary with the application. The use cases identified in the 3GPP requirements discussed by 5GAA included platooning, advanced driving, extended sensors and remote driving. Each places a different emphasis on the information exchanged and the communication conditions needed.

  • Platooning: Vehicles dynamically form and travel together as a group, making timely communication between vehicles important.
  • Advanced driving: Connectivity supports semi-automated or fully automated driving functions.
  • Extended sensors: Vehicles exchange raw or processed information from local sensors, or live video, to provide a wider view of road conditions.
  • Remote driving: A remote driver or V2X application operates a vehicle from another location.

The technical targets summarized in the material illustrate why use-case definition must come before network design. Examples included message rates of 50 per second, latency targets ranging from 20 milliseconds for lower automation levels to 10 milliseconds for higher levels, and a 5-millisecond Uu target for remote driving. The requirements also described differing payload sizes, data rates, ranges and reliability levels. These figures are tied to particular use cases and requirement assumptions; they should not be treated as a single performance profile applicable to every deployment.

Testing turns requirements into deployable systems

Because V2X combines communications, vehicles and applications, evaluation must look beyond an individual radio or device. 5GAA work included architecture assessments, alignment between regional upper-layer specifications and 3GPP cellular access layers, sensor-data-sharing analysis, and end-to-end evaluation of V2X use cases. Its testing activities also addressed device-to-device communication, system performance, interoperability and conformance.

Trials and testbeds provide a way to assess technology in different contexts. The organization’s 2018 materials listed C-V2X activity across Europe, North America and Asia, including demonstrations, performance testing, pilots and city-scale projects. Such activity helps stakeholders examine how components behave together and identify issues that cannot be resolved by reviewing a specification in isolation.

For system integrators and operations teams, the practical lesson is to treat validation as an end-to-end task. Testing should reflect the intended application, communication path and participating equipment. Standards alignment, spectrum considerations and cross-network compatibility all affect whether a service can operate consistently beyond a single test setup.

Safety applications and deployment choices

Safety was a major motivation in the work described by 5GAA. A study summarized in its materials compared LTE-PC5, LTE-Uu and 802.11p for cooperative intelligent transport system communications, focusing on red-signal violation and intersection safety, as well as vulnerable road user protection. The study reported its largest modeled impact for LTE-Uu, while also noting that combined PC5 and Uu deployment was considered likely. It reported a lower impact for 802.11p in part because vulnerable-road-user protection was considered less likely to be supported through smartphones.

These findings are specific to the study’s methods and assumptions; they are not a guarantee of outcomes in every deployment. They do, however, show why technology comparisons need to account for the service being delivered, the communication route and the devices available to road users. Safety applications may depend on a combination of direct communication and network-based connectivity rather than one approach serving every need.

How 5G fits into the evolution of V2X

The strategy presented by 5GAA connected LTE-V2X deployment with longer-term development of 5G-V2X based on 5G New Radio. It also emphasized expanding vehicle-to-network applications, building a shared car-smartphone-home ecosystem, supporting communication across vehicle manufacturers and network operators, and considering mobile edge computing as part of connected mobility.

These priorities point to a phased, ecosystem-wide effort. Existing V2X services, future radio technologies, network-based applications and edge computing must be considered in relation to one another. The goal is not connectivity for its own sake, but support for defined mobility services with requirements that can be tested and agreed across stakeholders.

Conclusion: Plan around services, integration and validation

C-V2X development demonstrates that connected mobility is a system-engineering challenge as much as a communications challenge. Automotive and telecommunications organizations must align use cases, architecture, standards, testing and deployment plans. For technical decision-makers, the practical starting point is to define the service and its requirements, then assess the full communication chain, interoperability needs and validation approach. That discipline provides a clearer foundation for evaluating how LTE-V2X and its evolution toward 5G can support cooperative transportation services.

Access Official Technical PDF

About The Author