Modern cars are infused with software.Adobe Stock / Catsby_Art
The evolution of operating systems for cars is driven by safety, connectivity, and faster OTA updates. Our overview explains the complexity of the various development levels on the way to the operating system of the future.
Open the door, sit down, buckle up, start the engine, drive off. For decades, this was the usual procedure when a driver wanted to start their journey. But since Apple and Google began to target the cockpit, another step has been added for many drivers: connecting the smartphone. Anyone who has already had their own experiences with Android Auto or Apple Carplay appreciates the advantages of integrating the familiar operating system. Nevertheless, car manufacturers do not want to leave the field to the tech giants and are developing their own operating systems.
This is, of course, because the topic is not just about pure infotainment. Automotive operating systems also control safety-critical applications and automated driving. In general, however, the term operating system is not used uniformly and is not clearly defined, says Jan Becker, CEO of Apex.AI. While some manufacturers rely on customized, proprietary solutions, others pursue an open-source approach that offers flexibility and customization options. But where do car manufacturers stand today, and what trends are emerging?
The current landscape of vehicle operating systems is diverse and complex. Many OEMs rely on complete solutions that are flexibly designed for a variety of control units found in a vehicle architecture, explains Martin Schleicher, Head of Software Strategy at Continental. Such operating systems allow manufacturers to develop specific functions and a tailored user experience that meet the requirements of the respective brand.
Advertisement
However, open-source systems like Android Automotive and Automotive Grade Linux (AGL) are also gaining more acceptance. "This adaptability is becoming increasingly attractive to more OEM customers," says Christian Kaiser, Partner at Berylls by AlixPartners. Becker further distinguishes between these two systems. "AGL is a classic operating system based on the open-source Linux kernel, primarily targeting infotainment systems." In contrast, Android Automotive is not a classic operating system but a software development kit adapted from Android for smartphones. Underneath lies a classic operating system that enables cross-manufacturer implementation of infotainment software. Prominent manufacturers that rely on Android Automotive include Volvo, Renault, and GM.
The Role of Safety-Critical Systems
While open-source platforms have primarily gained a foothold in the infotainment sector, systems like BlackBerry QNX continue to dominate in safety-critical applications. This is because they provide high stability and real-time capabilities required in ADAS systems and autonomous driving functions. In this context, Schleicher categorizes QNX as a commercial operating system. In contrast, Linux and Autosar are considered standard operating systems, with Autosar being an automotive-specific standard that encompasses more than just an operating system. "However, not every one of these standard, commercial, or open-source solutions is suitable for every type of control unit," says Schleicher. Operating systems like Linux, QNX, and Android require a system with a microprocessor, while Autosar Classic can also run on simpler and more cost-effective microcontrollers used by many control units in the vehicle, emphasizes Schleicher.
What is behind ISO 26262
ISO 26262 is an international standard that focuses on the functional safety of electrical and electronic systems in road vehicles. A central concept of this standard is the classification of safety requirements through Automotive Safety Integrity Levels (ASIL). These levels help assess the risk of failures in safety-critical systems and take appropriate measures to minimize risk. The ASIL classification ranges from A (low risk) to D (highest risk) and is used to determine the necessary diligence and rigor in the development of vehicle components. Infotainment systems are usually ASIL B systems, while autonomous driving functions are typically ASIL D. “The safety requirements are four to six orders of magnitude higher, and so are the efforts in testing, verification, validation, safeguarding, and approval," explains Jan Becker from Apex.AI.
Collaboration with Technology Companies
Another crucial factor in the development of modern vehicle operating systems is the collaboration between automotive manufacturers and technology companies. "In such partnerships, OEMs typically adopt operating system solutions that have been pre-configured and partially developed by tech companies," emphasizes Kaiser. The close collaboration between semiconductor manufacturers, operating system providers, and automotive manufacturers is therefore not only sensible but necessary to meet the increasingly complex requirements of vehicle architectures, according to Martin Schleicher. These collaborations extend beyond the vehicle and increasingly include cloud-based solutions that enable seamless integration of online services and over-the-air updates (OTA).
Over-the-Air Updates: The Next Challenge
Which brings us to the next point that is on everyone's lips, but still does not work as well as users are accustomed to with their smartphones. The biggest obstacles in implementing over-the-air updates for operating systems in vehicles, according to Kaiser, are the "lack of competence of OEMs to implement functions across domains." The lack of architectural preparation of existing vehicle architectures is also problematic. If multiple control units in the vehicle are to be updated, there are additional challenges, Schleicher also emphasizes. Large amounts of data can accumulate, the transmission takes a certain amount of time, and appropriate communication channels are needed, according to the Conti man.
The status quo of operating systems in cars suggests that there will be a coexistence of proprietary and open-source solutions for the foreseeable future. "The automotive industry is still at the beginning of working together on open-source solutions. We see opportunities here to reduce development efforts through collaboration," says Schleicher. Kaiser also sees an increasing spread of open-source systems, complemented by proprietary security certifications and support.
As mentioned at the beginning, the integration of well-known smartphone systems remains important for the end user. In fact, many customers assess their user experience by the quality and speed of the connection to Android Auto or Apple Carplay, emphasizes Berryls partner Kaiser. However, the fast software update cycles of the new economy can only be represented if all user-relevant software is in the hands of the OEM, or at least accessible in the source code. "In this respect, an open-source solution could bridge the gap between synergy and full access."
