Future Integration Concepts for ADAS

Abstract

The automotive industry is facing the next major evolutionary step. New functions for highly automated driving are entering the vehicles. This is accompanied by increased E/E and mechatronic contents, leading to increased topological complexity. At the same time the system/component and development costs should remain stable, and product quality should be further improved.

A promising strategy to master the complexity of the E/E architecture is the clustering of already intensively networked functional elements either by physical integration or by functional integration into a handful of functional domains. One of these functional domains is the motion domain, which is needed to execute the driving strategy. In recent times there has been a trend toward automation of selected elements of the driving strategy, like driving with a predefined speed or distance in a specific lane.

The main purpose of motion control is to execute the driving strategy by generating and managing the forces at the wheels. Motion control structures and coordinates the access to the actuators. The command flow is hierarchically organized in a three-layer sequence. The standardization of the interfaces of each layer is an important task, which finally has to lead to an extension of the AUTOSAR application interface catalog. A new and challenging requirement for motion control is to provide a tracking control capability to follow a predefined trajectory autonomously.

For a custom-specific realization of motion control, powerful and flexible integration platforms equipped with multi-core microcontrollers are available. The new architecture is highly scalable and fulfills all requirements from ISO26262 ASIL D. The design is fail operational due to additional on-chip diagnosis (1oo2D), i.e., in case of a permanent failure in one channel, a limp-home mode is entered. The AUTOSAR compliant software can be configured to satisfy different customer needs and requirements, e.g., most flexible hardware resource usage or maximum independency between OEM and supplier software (virtual ECU).