Developing intelligent connected vehicles is not simply a matter of adding sensors, software or wireless links to a conventional vehicle. It requires coordinated decisions across vehicle architecture, power systems, communications, cybersecurity and validation. The SAE 2019 New Energy & Intelligent Connected Vehicle Technical Conference program reflected this breadth, bringing together topics that ranged from battery management and electric drives to C-V2X, high-definition mapping and autonomous vehicle testing.
For automotive engineers, system integrators and technical decision-makers, the program offers a useful view of the connected challenges behind vehicle automation. Its central lesson is that vehicle capabilities depend on how well technologies and development processes work together—not on any one component in isolation.
Intelligent connected vehicles need an integrated architecture
As vehicles combine advanced driver-assistance systems, connectivity and automated driving functions, their hardware and software architecture becomes a critical design consideration. Conference sessions examined topics including central computing, vehicle networks, sensor fusion and software platforms. These systems must support the growth of vehicle functions while accounting for the different requirements associated with automated driving.
That architectural perspective also connects to functional safety and cybersecurity. A vehicle’s sensors, computing resources, communications and control functions form an interdependent system. Engineering teams therefore need to consider how information moves through that system, how functions rely on one another, and how the design can be assessed for safe and secure operation.
Connectivity also changes the scope of system design. Rather than treating the vehicle as an isolated product, development may involve the vehicle, road infrastructure and cloud platforms. The conference’s “Chip-Road-Cloud” discussions focused on the roles different stakeholders and technologies could play in cooperative vehicle-infrastructure systems. The program also raised practical questions about deployment paths and business models, underscoring that technical integration and industry coordination are linked.
Vehicle-road collaboration extends the sensing environment
Vehicle-road collaboration is intended to connect vehicles with information and services beyond the vehicle itself. Sessions on C-V2X and intelligent transportation systems addressed potential roles in traffic management, traffic efficiency and safety, as well as support for assisted and autonomous driving. The program also covered 5G-based vehicle-road applications and edge computing as elements of cooperative systems.
For engineering teams, this approach introduces interfaces and dependencies that must be considered alongside onboard systems. A connected-vehicle function relies not only on vehicle equipment but also on communications and the surrounding infrastructure. The conference agenda’s focus on pilot-zone deployments, intelligent highways and collaborative applications illustrates the range of environments in which such systems may need to operate.
Vehicle-road cooperation was presented as a complement to vehicle-only intelligence, particularly in discussions of challenging driving situations and cost control. It does not remove the need for capable onboard sensing, decision-making and control. Instead, it raises a systems question: how should information from the vehicle, road and cloud be coordinated, and how should the resulting functions be tested?
Cybersecurity and validation belong in the development process
As connected and automated functions expand, cybersecurity becomes part of product development and system assurance. The conference program addressed cybersecurity engineering, emerging regulations and standards, and security testing for intelligent connected vehicles. It also highlighted the need to evaluate a vehicle’s overall security protections rather than viewing individual components in isolation.
These topics have direct implications for development planning. Security requirements affect architecture, software, communications and assessment activities. The program’s emphasis on standards and testing points to the importance of defining how protection will be evaluated as systems are designed and integrated.
Validation presents a related challenge. Testing approaches developed for traditional embedded control functions may not, by themselves, address the distinct characteristics of intelligent connected vehicle software. Conference sessions considered testing strategies for autonomous driving, including how to verify software and hardware and how to adapt established automotive validation processes.
The program also distinguished among vehicle intelligence, automation and connectivity as different areas for assessment. Proposed approaches included evaluating intelligence, using scenarios to assess autonomous performance and applying functional tests to connectivity. This distinction can help teams choose tests that match the function under review rather than relying on a single broad measure of vehicle capability.
Electric powertrain engineering remains part of the picture
Connected and automated features develop alongside changes in vehicle propulsion. The conference covered battery technology, battery management systems, thermal management, electric motors, drive systems and fuel cells. These areas bring their own design and integration demands, including measurement accuracy, operating conditions, power-system thermal management and the coordination of fuel-cell and battery systems.
For example, battery-management discussions addressed monitoring, communication and safety mechanisms, while thermal-management sessions focused on the importance of managing heat in batteries and power modules. Electric-drive presentations covered motor design and integrated propulsion components. Taken together, these topics show why vehicle-level planning must account for both digital functions and the systems that provide and manage propulsion.
Practical priorities for engineering teams
The conference program points to several priorities for teams developing intelligent connected vehicles:
- Design across system boundaries. Consider how onboard computing, sensors, vehicle networks and external infrastructure interact.
- Address cybersecurity early. Connect security requirements with architecture, development and testing activities.
- Match validation to the function. Use testing approaches suited to automation, connectivity and intelligent features, including scenario-based evaluation where appropriate.
- Integrate power-system considerations. Coordinate battery, thermal-management and electric-drive requirements with vehicle-level development.
- Plan for collaboration. Vehicle-road systems depend on multiple technologies and stakeholders, making interfaces and deployment conditions important engineering questions.
Conclusion
Intelligent connected vehicle development spans more than autonomous-driving software or wireless communication. It combines vehicle architecture, infrastructure connectivity, cybersecurity, testing and electrified power systems. For technical decision-makers, the practical implication is to manage these as connected engineering disciplines: define their interfaces, build security and validation into development, and assess vehicle functions in the context where they will operate. That systems-level approach is essential to turning individual technologies into coherent vehicle capabilities.