| |NOVEMBER 20219Control, Central Timing Module, Body Control, Infotainment and more. Each of these modules are operated by Electron-ic Control Units (ECU) ­ which is an integrated unit of HW & SW. A typical premium car will have hundreds of ECUs. The ECUs communicate with each other through their own communication channel and together operate the car. If new features are added to the car specially related to ADAS, it will also add another ECU with its own power unit, own components, own connectivity, and its own process-ing. This increases weight, cost and complexity of the car. Instead, if we have a Centralized Architecture, it will reduce the need of discreet control units. Secondly, today, consum-ers are increasingly looking for more software features in the car like driver assistance, innovative infotainment and intelligent connectivity. This increases the need for more software applications inside the car. Also, while for all intel-ligent devices, software is updated remotely through OTA. However, for an Automotive today, we still need to go to a dealer for software upgrade. We still depend on the dealer to monitoring and tuning of core functional capabilities of the vehicle, such as power train and vehicle dynamics.The idea behind SDV is to simplify vehicle E/E architec-ture and consolidate hundreds of ECUs into domain/zonal controllers and vehicle computers, have separation of soft-ware from hardware, and move all the SW controller logic to vehicle computers, thereby managing the vehicle, rather than managing individual ECUs. It also enables updating vehicle software over-the-air, either feature-by-feature, domain-by-domain, or even full-vehicle update.· Physical connections of sensors to vehicle computers and/or zonal controllers shall be abstracted out, with redundancies by design· Zonal/domain controllers separates various I/O from the vehicle controllers· Mechatronics ECU will provide a abstraction layer· The vehicle computers will have virtualized applica-tions running on them.The SDV architecture is based on simplified design, cen-tralizes computing power and optimized electrical/elec-tronic content, components, and functionality. In SDV Archi-tecture, we have two key components - Domain Controller and Vehicle Compute. The Domain Controllers deliver power and data connections to the sensors and other devices, with just a backbone connection to the Vehicle Compute. All pe-ripheral sensors and devices are connected to Domain/Zone controllers. Vehicle Computes are essentially Central Com-puting Units ­ they will host Applications & Services (ECU functionalities are converted into containerized Micros-ervices) and these services provided by multiple Central Computing units communicate among each other and ex-change the data using Service Bus Architecture. As the I/O is separated from the compute, the computing resources in
< Page 8 | Page 10 >