At the very heart of the “software defined vehicle” is the Automotive OS, enabling the user-visible functionality that the applications provide, which run on different ECUs. Consequently, the Automotive OS is not an operating system in the classical sense. Instead, it has the following three properties: 1. The Automotive OS abstracts the complex vehicle network of ECUs as a single device. 2. The Automotive OS manages, supervises and updates this device. 3. The Automotive OS enables an ecosystem by harmonizing the APIs against which functions are developed. These properties have implications on the vehicle's E/E architecture, software lifecycle and overall safety and security architecture. The paper presents how the abstraction of the vehicle network can be achieved by setting up a service-oriented architecture using automotive standards like AUTOSAR, thereby enabling the “single device” view postulated by the Automotive OS. We discuss the resulting requirements on the software lifecycle of the Automotive OS platform and the applications in order to keep the software ecosystem thriving across car platforms and generations. This talk also shows how safety and security can be addressed in this environment.
Session: E/E ARCHITECTURE | | 17:00 - 17:30