RACE: A Centralized Platform Computer Based Architecture for Automotive Applications

Abstract

In the last couple of years software functionality of modern cars increased dramatically. This growing functionality leads directly to a higher complexity of development and configuration. Current studies show that the amount of software will continue to grow. Additionally, advanced driver assistance systems (ADAS) and autonomous functionality, such as highly and fully automated driving or parking, will be introduced. Many of these new functions require access to different communication domains within the car, which increases system complexity. AUTOSAR, the software architecture established as a standard in the automotive domain, provides no methodologies to reduce this kind of complexity and to master new challenges. One solution for these evolving systems is developed in the RACE project. Here, a centralized platform computer (CPC) is introduced, which is inspired by the well-established approach used in other domains like avionics and automation. The CPC establishes a generic safety-critical execution environment for applications, providing interfaces for test and verification as well as a reliable communication infrastructure to smart sensors and actuators. A centralized platform also significantly reduces the complexity of integration and verification of new applications, and enables the support for Plug&Play.

Component-based modeling and integration of automotive application architectures

“…They are currently aligned and limit modularity as well as flexibility. At the platform level, a first step is to provide a generic runtime environment like the one proposed in the RACE-Project [6] as a foundation for an integrated system architecture. It also includes an ARINC 653 [7] inspired automotive execution environment.…”

An Automated Electric Vehicle Prototype Showing New Trends in Automotive Architectures

“…Dependent on different Automotive Safety Integrity Levels (ASIL) from QM to ASIL-D and fault tolerance requirements (fail-silent or failoperational), functions can be executed either on one lane of one DCC, on two lanes of one DCC or even redundantly on multiple DCC's [7]. This scalable redundancy provides cost efficient execution tailored to the requirements of the function.…”

“…It supports BroadR-Reach technology using cheap and lightweight single twisted pair cables [7]. Strict priority scheduling is used to separate different kinds of data, like critical and non-critical data.…”

“…Strict priority scheduling is used to separate different kinds of data, like critical and non-critical data. To minimize the influence between network data with mixed criticalities and mixed transmission rates, the preemption mechanism standardized in TSN is used [7]. Multiple Virtual Local Area Networks (VLANs) are used to define disjoint path for critical data and to protect the network rings from circulating packets [8].…”

Adaptive Error and Sensor Management for Autonomous Vehicles: Model-Based Approach and Run-Time System

“…Such architecture is proposed in the Robust and Reliant Automotive Computing Environment for Future eCars (RACE) 4 project [13]. The fail-operational centralized platform (Figure 1) consists of a redundant and reliable communication infrastructure based on a switched Ethernet topology, redundant power supply (blue and red lines in Figure 1) and redundant controllers.…”