The move to software-defined vehicles is driven by the rapid growth of software-intensive functions—ADAS/AD, electrification control, and connected services—which require continuous updates, data-driven improvement, and faster feature velocity than hardware-centric architectures can support. As high-performance computing (HPC) capabilities advance, more vehicle functions can be consolidated onto fewer computing platforms. This architectural compression supports migrating edge-based software to centralized HPCs, enabling a more efficient, scalable in-vehicle network design that can support new capabilities for years to come.
Domain vs zonal architecture in the modern in-vehicle network
Two dominant architectural approaches have emerged. Domain Master architectures assign dedicated HPCs to individual technical domains, such as powertrain, body and chassis, and driver-assistance systems. This architecture is often effective for today's systems.However the cabling and networking of a pure Domain Master architecture cause concerns for its scalability as software complexity and data traffic grow.
Zonal architectures distribute HPCs throughout the vehicle’s geography, with each zone controller managing software from multiple technical domains. Individual sensors or subordinate ECUs need only to connect to the closest zonal controller. This not only reduces cable weight and complexity but also improves fault isolation and scalability as vehicle platforms evolve. These architectural changes increase the demands placed on the in-vehicle network, requiring higher bandwidth, deterministic communication, and more flexible software orchestration across multiple vehicle zones.
Automotive Ethernet and Ethernet TSN enabling real-time vehicle systems
A core enabler of these scalable architectures is automotive Ethernet. Unlike legacy CAN or LIN networks, automotive Ethernet offers much higher bandwidth, enabling it to handle the immense data generated by sensors, cameras, and compute platforms in real time. Ethernet makes use of IP(Internet Protocol) addressing, enabling cloud resources to connect to the devices in the vehicle. This facilitates over-the-air software updates across all HPCs and virtual machines, an essential requirement as vehicles become more software-defined. Additionally, it also supports diagnostic and monitoring capabilities, which are necessary for maintaining system integrity, ensuring uptime, and enabling predictive maintenance.
However automotive control and safety systems require deterministic behaviour and ethernet is typically not deterministic in regards to time. To meet the stringent demands of safety-critical and autonomous driving applications, Ethernet Time-Sensitive Networking (TSN) extends standard Ethernet by adding deterministic communication features. TSN enables guaranteed latency and bandwidth for time-critical data flows, such as those required for real-time control of braking, steering, and sensor fusion. It also introduces redundancy mechanisms to ensure fail safe operational behavior—vital in any safety function.
Together, automotive Ethernet and TSN provide the bandwidth, determinism, scalability, and robustness required for next-generation vehicle architectures. By supporting software-defined functionality, redundancy, diagnostics, and real-time communication, these technologies form the backbone of in-vehicle networks that can meet the future demands of software defined vehicles
Explore how Excelfore enables scalable in vehicle network architectures using automotive Ethernet and Ethernet TSN technologies for next-generation vehicle platforms.
Learn more about Excelfore automotive networking tools →
https://excelfore.com/automotive-networking-test-tools#mini-test-tool-avb-tsn.
Leave a Comment