Basics

Driven by the advent of innovative vehicle applications, contemporary automotive E/E architecture has reached a level of complexity which requires a technological breakthrough in order to manage it satisfactorily and fulfill the heightened passenger and legal requirements. This need is particularly acute for vehicle manufacturers and their leading Tier 1 suppliers who are faced with often conflicting requirements from:

∙ Legal enforcement – key items include environmental aspects and safety requirements

∙ Passenger convenience and service requirements from the comfort and entertainment functional domains

∙ Driver assistance and dynamic drive aspects – key items include detection and suppression of critical dynamic vehicle states and navigation in high density traffic surroundings

Leading OEMs and Tier 1 suppliers, having recognized this to be an industry-wide challenge, decided to work together to meet the challenge. Their common objective is to create a development base for industry collaboration on basic functions while providing a platform which continues to encourage competition on innovative functions. To this end a development partnership called Automotive Open System Architecture (AUTOSAR) has been formed with the goals of:

∙ Standardization of basic software functionality of automotive ECUs

∙ Scalability to different vehicle and platform variants

∙ Transferability of software

∙ Support of different functional domains

∙ Definition of an open architecture

∙ Collaboration between various partners

∙ Development of highly dependable systems

∙ Support of applicable automotive international standards and state-of-the-art technologies

The AUTOSAR scope includes all vehicle domains.

The AUTOSAR standard will serve as a platform upon which future vehicle applications will be implemented and will also serve to minimize the current barriers between functional domains. It will, therefore, be possible to map functions and functional networks to different control nodes in the system, almost independently from the associated hardware.

Motivation & Goals

Motivation

∙ Management of E/E complexity associated with growth in functional scope

∙ Flexibility for product modification, upgrade and update

∙ Scalability of solutions within and across product lines

∙ Improved quality and reliability of E/E systems

Goals

∙ Fulfillment of future vehicle requirements, such as, availability and safety, SW upgrades/ updates and maintainability

∙ Increased scalability and flexibility to integrate and transfer functions

∙ Higher penetration of "Commercial off the Shelf" SW and HW components across product lines

∙ Improved containment of product and process complexity and risk

∙ Cost optimization of scalable systems

Key Features

Modularity and configurability

∙ Definition of a layered basic software architecture for automotive electronic control units in order to encapsulate the HW dependencies

∙ Consideration of HW dependent and HW independent SW modules

∙ Enable the integration of basic SW modules provided by different suppliers to increase the functional reuse

∙ Enable the transferability of functional SW-components within a particular E/E-system at least at the final software linking process

∙ Resource optimized configuration of the SW infrastructure of each ECU depending on the function deployment

∙ Scalability of the E/E-system across the entire range of vehicle product lines

Standardized interfaces

∙ Standardization of different APIs to separate the AUTOSAR SW layers

∙ Facilitate encapsulation of functional SW-components

∙ Definition of the data types of SW-components

∙ Standardization of interfaces of basic SW modules of the SW infrastructure

Runtime Environment (RTE)

∙ Provision of inter- and intra-ECU communication across all nodes of a vehicle network

∙ Located between the functional SW-components and the basic SW-modules

∙ All entities connected to the AUTOSAR RTE must comply with the AUTOSAR specification

∙ Enables the easy integration of customer specific functional SW-modules

Acceptance Tests

∙ Standardization of test case specifications to test a basic software and RTE implementation at application and bus level

Technical Overview

To achieve the technical goals modularity, scalability, transferability and re-usability of functions AUTOSAR provides a common software infrastructure for automotive systems of all vehicle domains based on standardized interfaces for the different layers as shown in the top right image.

AUTOSAR enables configuration process optimization (e.g. partitioning and resource usage) and where necessary, to allow local optimization if required to meet the runtime requirements of specific devices and hardware constraints.

Modularity

Modularity of automotive software elements enables tailoring of software according to the individual requirements of electronic control units and their tasks.

Scalability

Scalability of functions ensures the adaptability of common software modules to different vehicle platforms to prohibit proliferation of software with similar functionality.

Transferability

Transferability of functions optimizes the use of resources available throughout a vehicle´s electronic architecture.

Re-usability

Re-usability of functions helps to improve product quality and reliability and to reinforce corporate brand image across product lines.

Standardized interfaces

Standardization of functional interfaces across manufacturers and suppliers and standardization of the interfaces between the different software layers is seen as a basis for achieving the technical goals of AUTOSAR.

The figure on the right hand side shows a very condensed view of the AUTOSAR approach. The basic concept is the AUTOSAR Software Component (SW-C).

The AUTOSAR Software Components encapsulate an application which runs on the AUTOSAR infrastructure. The AUTOSAR Software Components have well-defined interfaces, which are described using a standardized exchange format defined in AUTOSAR.

Software Component Description

For the interfaces as well as other aspects needed for the integration of the AUTOSAR Software Components, AUTOSAR provides a standard description format, i.e. the Software Component Description.

Virtual Functional Bus (VFB)

The VFB is the sum of all communication mechanisms and essential interfaces to the basic software provided by AUTOSAR on an abstract, i.e. technology independent, level. When the connections between AUTOSAR Software Components for a concrete system are defined, the VFB will allow a virtual integration of them in an early development phase.

System Constraint and ECU Descriptions

In order to integrate AUTOSAR Software Components into a network of ECUs, AUTOSAR provides description formats for the complete system as well as for the resources and configuration of the single ECUs. These descriptions are kept independent of the Software Component Descriptions.

Mapping on ECUs

AUTOSAR defines the methodology and tool support needed to bring the information of the various description elements together in order to build a concrete system of ECUs. This includes especially the configuration and generation of the Runtime Environment and the Basic Software on each ECU.

Runtime Environment (RTE)

From the viewpoint of the AUTOSAR Software Component, the RTE implements the VFB functionality on a specific ECU. The RTE can however delegate this task to the Basic Software as far as possible.

Basic Software

The Basic Software provides the infrastructural functionality on an ECU.

AUTOSAR资料From官网