The automotive industry is being reshaped by the Software-Defined Vehicle (SDV), a car whose functions and value are defined by software and continuously expanded even after sale through over-the-air (OTA) updates, much as a smartphone gains features after purchase. Delivering those updates forces a rethink of the in-vehicle electrical/electronic (E/E) architecture where computing must be consolidated into a small number of high-performance platforms so that hardware and software can be developed and evolved independently.
The conventional distributed architecture includes anywhere from tens to more than a hundred function-specific ECUs, each running a different supplier’s software which makes consistent, vehicle-wide updates difficult. A second force here is sensor fusion. As ADAS and autonomous driving mature, cameras, radar, LiDAR and ultrasonic sensors increasingly stream RAW or lightly-processed data to a central platform for integrated processing, rather than each reporting only its own local decisions. Both trends demand more bandwidth and more centralized computing, turning the modern car into a “data center on wheels.” This two-part series maps that evolution, from Distributed to Domain to Zonal architectures, tracking sensor, data format, SoC and network changes along the way while showing how SerDes and Ethernet get applied and eventually converge.