Until recently, the involvement of tech companies inside the cabin was limited to managing maps and music, through interfaces to connect to a smartphone or operating systems embedded in multimedia displays.
Google has, however, decided to take a further step, presenting a new version of its software designed to interface with the deeper systems of vehicles: Android Automotive OS for Software Defined Vehicles, abbreviated as AAOS SDV. This expansion will bring the operating system to manage much more than the simple car radio.
Android Automotive OS is transforming, Google wants control over (almost) the entire car
Until today, Android Automotive OS has offered automakers a high-level interface to govern entertainment functionalities, while at the same time lowering development costs.
The new SDV iteration extends the software’s reach far beyond the central display. In practical terms, the California-based company provides an open infrastructure capable of handling all those vehicle components that do not concern active or passive safety.
Onboard voice assistants, for example, will be able to interact natively with the air conditioning controls, manage the door unlocking, communicate with the digital keys and offer proactive maintenance alerts by reading the vehicle telemetry data.
It is important to note that Google will maintain a clear demarcation: AAOS SDV will have no access or control over critical systems such as emergency braking or lane keeping, which will remain the exclusive competence of automakers.
Code discipline and savings for manufacturers
Currently, software integration in cars represents a complex challenge. Manufacturers often have to assemble modules from dozens of different suppliers, creating a fragmented, closed, and costly-to-maintain mosaic.
Building and continually updating the underlying infrastructure drains valuable resources from creating the functionalities that allow a brand to stand out in the market.
The approach proposed by Google provides a common and reliable foundation. By using a standardized architecture for managing secondary services, automakers can focus solely on the end-user experience.
This translates into a drastic reduction in development times and a greater stability of the entire onboard system.
Ongoing updates and open-source release
An additional advantage of this architecture lies in update management. Adopting the AAOS SDV system will greatly facilitate the release of Over-The-Air packages, allowing vehicles to receive new features and improvements exactly as today with smartphones.
The end user will benefit from an extremely cohesive interface and a vehicle capable of getting better over time.
Google is not moving alone in this initiative: companies such as Renault Group and Qualcomm are already actively working on development and hardware integration of the system.
The source code of Android Automotive OS for Software Defined Vehicles will be released in open-source format by the end of the year, enabling any industry manufacturer to study, experiment with and implement this infrastructure freely in models under design.
