AUTOSAR

Automotive Open System

ARchitecture
Challenges and Achievements 2005

Dr. Thomas Scharnhorst, AUTOSAR Spokesperson

Management summary

2 Friday, 06 July 2007

AUTOSAR aims to improve complexity management of integrated E/E architectures
through increased reuse and exchangeability of SW modules.

OEM n
OEM 1

Platform m.1
Platform m.2
Platform 1.1 Platform m.n
Platform 1.2
Platform 1.n

Supplier A Supplier B
¾ Chassis ¾ Chassis Transferability
Transferability ¾ Safety ¾ Safety between suppliers
¾ Body/Comfort ¾ Telematics
between manufactureres ¾ Multimedia
¾ Multimedia
OEM m
OEM 2
Supplier C
¾ Body/Comfort
¾ Powertrain
¾ Telematics
¾ Multimedia

Platform m.1
Platform m.2
Platform 2.1 Platform m.n
Platform 2.2
Platform 2.n
Transferability
between vehicle platforms
3 Friday, 06 July 2007
AUTOSAR integrates existing and emerging industry electronics standards.

MSR
Manufacturer-Supplier Relationship

OSEK/VDX

ASAM ODX 2002

ASAM/ODX
Media Orientated AUTomotive Open
System Transport System ARchitecture

Hersteller Initiative Software

FlexRayHIS

Local interconnect network

2001 2006

4 Friday, 06 July 2007

Worldwide, OEMs and suppliers participate in AUTOSAR. Development
Status: June 9th, 2005 Members

10 Core Partner Attendees

15 Associate
Members
45 Premium Members

General Generic Semi-

Software Tools
OEM Tier 1 conductors
5 Friday, 06 July 2007
The AUTOSAR core partners manage the project and maintain organizational
control.
Project Organization
Support Functions

Executive Board

Spokes-
Steering Committee Technical Manager
person
Project Control
Office
Administration

PL Team

System Team Technical Office

Basic SW
Architecture Team

Working Groups

6 Friday, 06 July 2007

To achieve the objectives, AUTOSAR has to address the main topics:
software integration, basic software, and functional APIs.

Project Objectives Topics

„ Consideration of availability and safety requirements

„ Redundancy activation
„ Scalability to different vehicle and platform variants „ Methods of Software
Integration
„ Implementation and standardization of basic system
functions as an OEM wide “Standard Core“ solution
„ Transferability of functions throughout network „ Basic Software
„ Integration of functional modules from multiple
suppliers „ Functional APIs
„ Maintainability throughout the whole “Product Life Cycle“
„ Increased use of “Commercial off the shelf hardware“
„ Software updates and upgrades over vehicle lifetime

7 Friday, 06 July 2007

The AUTOSAR ECU software architecture comprises the layers Application,
AUTOSAR Run Time Environment (RTE), and Basic Software.
AUTOSAR
Application Actuator Sensor Application
Software
Component Software Software Software AUTOSAR Software
Component Component Component Component
Software
Different
Kinds of
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
.............. AUTOSAR
Interface
Interfaces

ECU
AUTOSAR Runtime Environment (RTE)
Firmware
Standardized
Standardized Standardized AUTOSAR AUTOSAR
Standard AUTOSAR
Interface Interface Interface Interface
Software Interface
ECU
API 2 Services Communication
Abstraction
Standardized

VFB & RTE

Standardized Standardized Standardized
Interface

relevant
Interface Interface Interface
API 1 Operating
Complex
RTE relevant System
Device
Standardized Drivers
API 0 Interface
Basic Software Microcontroller
API 3 Private
Interfaces inside
Abstraction
Basic Software
possible ECU-Hardware
8 Friday, 06 July 2007
Basic Software Architecture: The layered architecture is finalized

AUTOSAR
Application Actuator Sensor Application
Software
Component Software Software Software AUTOSAR Software
Component Component Component Component
Software
Different
Kinds of
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
.............. AUTOSAR
Interface
Interfaces

ECU
AUTOSAR Runtime Environment (RTE)
Firmware
Standardized
Standardized Standardized AUTOSAR AUTOSAR
Standard AUTOSAR
Interface Interface Interface Interface
Software Interface Services Layer
ECU
API 2 Services Communication
Abstraction
Standardized

VFB & RTE

Standardized Standardized Standardized
Interface

relevant Complex
InterfaceECU Abstraction
Interface Interface
Operating Layer Drivers
API 1 Complex
RTE relevant System
Device
Standardized Drivers
API 0 Interface
Basic Software
Microcontroller Abstraction Layer
Microcontroller
API 3 Private
Interfaces inside
Abstraction
Basic Software
possible ECU-Hardware
9 Friday, 06 July 2007
 Ko
Basic Software Architecture: The layered architecture is split up in morenzthan
ept 80
fol
different modules ie

AUTOSAR
Application Actuator Sensor Application
Software
Component Software Software Software AUTOSAR Software
Component Component Component Component
Software
Different
Kinds of
AUTOSAR
Interface
AUTOSAR
Interface
AUTOSAR
Interface
.............. AUTOSAR
Interface
Weitere Detaillierung der Layered
Interfaces
Architecture
ECU
AUTOSAR Runtime Environment (RTE)
Firmware
Standardized
Standardized Standardized AUTOSAR AUTOSAR
Standard AUTOSAR
Interface Interface Interface Interface
Software Interface Services Layer
ECU
API 2 Services Communication
Abstraction
Standardized

VFB & RTE

Standardized Standardized Standardized
Interface

relevant Complex
InterfaceECU Abstraction
Interface Interface
Operating Layer Drivers
API 1 Complex
RTE relevant System
Device
Standardized Drivers
API 0 Interface
Basic Software
Microcontroller Abstraction Layer
Microcontroller
API 3 Private
Interfaces inside
Abstraction
Basic Software
possible ECU-Hardware
10 Friday, 06 July 2007
Service Layer – Flow through the layer

Memory Services

NVRAM
Manager

EepIf_Read()
EepIf_Write()
ECU
Memory Hardware Abstraction
device device
EEPROM Interface #1 #2

External µC
EEPROM Driver

Spi_Read()
Spi_Write()
driver #1 driver #2
SPI Handler IF µC I/O driver

COM Drivers Memory Drivers

Internal
SPI Driver
EEPROM Driver

SPI µC EEPROM

External
EEPROM

11 Friday, 06 July 2007

Following the AUTOSAR Method, the E/E architecture is derived from the formal
description of software and hardware components.

Using „Software Component

Descriptions“ as input, the „Virtual
Functional Bus“ validates the
interaction of all components and
interfaces before actual software
implementation.

The AUTOSAR Method supports

the generation of an E/E
architecture.

12 Friday, 06 July 2007

 Ko
Description of Topology nze
pt f
oli
e
Net of ECUs Net of Software Components

SwitchEval

ECU Resource ECU Resource SW-Component Description

ECU Resource
Descr. Descr. Descr.

BlinkInputModule
SwitchEval
SW-Component Description

BlinkInputModule
System-
Constraint BlinkMaster
BlinkMaster
Description SW-Component Description

LightActuatorsControl

SMLS LightActuatorsControl
LightSourceSetting
SW-Component Description

BC-V BC-H
LightSourceSetting
BodyFlexRay
SW-Component Description
LIGHTCAN

13 LM-
Friday, 06 July 2007

L LM-R
 Ko
Description of Mapping nze
pt f
oli
e
SW-C to ECUs Interface Connections to Bus Signals

System-Constraint Description
SWCMappingDefs DataMappingDefs

switchStatus

SwitchEval Blink
Switch
Eval Input
Module
BlinkInputModule

BlinkMaster
Comm.Matrix for BodyFlexRay

LightActuatorsControl
FrameInstance
… BlinkSwitch
LightSourceSetting SignalBS1SignalBS2 SignalBS3

14 Friday, 06 July 2007

Unified functional interfaces are been standardized to ensure the interoperability of
functional Software-Components (applications) from different sources

¾ Body/Comfort domain
¾ Powertrain domain ¾ Exterior Light ready for approval
¾ Chassis domain ¾ Interior Light ready for approval
Body Comfort ¾ Central Locking 60%
¾ Safety domain ¾ Anti Theft 60%
¾ Wiper Washer ready for approval
¾ Multimedia and HMI domain

¾ Driver Request 95%

Powertrain ¾ Functional Architecture 50%
¾ System Functionalities 50%

¾ ACC 91%
Chassis
¾ External ESP Interfaces just started

15 Friday, 06 July 2007

 Ko
The AUTOSAR standard will be completed and available to OEM productnzept
f oli
development in 2006. e
actual
timeline

Specification of Templates, BSW and RTE Update BSW and RTE Specifications via CCB

Implementation
and Integration

Phases
Test & Validation

Milestones
30.9.2004 30.4.2005 30.9.2005 15.12.2005 31.5.2006 15.12.2006

Concept Spec R1.0 Spec R2.0 Methodology Integration Validation

- Autosar concept - Autosar BSW - Autosar BSW and - methodology and - BSW and RTE - All documents
finalized specifications for RTE templates prototype formally released, Status
Release 1 are specifications for finalized implementations specifications
finalized Release 2 are and integrations verified on an
finalized completed, test application
specification demonstrator,
completed proof of concept
demonstrated

2H 2004 1H 2005 2H 2005 1H 2006 2H 2006

16 Friday, 06 July 2007
Migration scenarios allow concurrent deployment of AUTOSAR modules and
existing proprietary components to one ECU.

Today Transition period Future – AUTOSAR Life

Time

AUTOSAR-development

MS 1 MS 2 MS 2’

OEM infrastructure

Incorporation of all available

AUTOSAR specifications
Partly proprietary solutions

Implantation of components
not available from AUTOSAR
Proprietary Basic SW Core

17 Friday, 06 July 2007

 Ko
Conclusion nze
pt f
oli
e

Fast growth of the complexity of automotive E/E architectures is a major

1
challenge with respect to product quality.

Through interconnection of subsystems, new system properties emerge

2 which have to be understood and controlled.

Systems Engineering is an integrated approach which covers the

3 development process and the complete product life cycle.

AUTOSAR enables management of the growing E/E complexity with respect

4 to technology and economics.

AUTOSAR pushes the paradigm shift from an ECU based to a function

5 based approach in automotive software development.

18 Friday, 06 July 2007

How to get in contact with AUTOSAR …

http://www.autosar.org

request@autosar.org
19 Friday, 06 July 2007
Thank you for your attention!

http://www.autosar.org

request@autosar.org
20 Friday, 06 July 2007
Backup

21 Friday, 06 July 2007

Heading
Sub-Heading

Level 1
¾ Level 2
ƒ Level 3
– Level 4
– Level 5

22 Friday, 06 July 2007

Document information and change history

Document Owner Dr. Thomas Scharnhorst

Document Responsibility SC
Document Title <AUTOAR_VDI_BadenBadenPresentation.ppt>
Document Version 0.1
Document Status <Draft | Ready for Approval | Final>

Document Change History

Date Version Changed by Change Description
07.06.2005 0.1 Gabriel Schwab Document creation

23 Friday, 06 July 2007

 Ko
The AUTOSAR standard will be completed and available to OEM productnzept
f oli
development in 2006. e
05/03 09/04 11/05 08/06
12/03 06/05 02/06 Mile-
stones

Initiation of Structure & Basis Standardization

Implementation of the Test- & Integration-
Partnership Specification AUTOSAR
SW-Components
architecture process Phases

AUTOSAR
Project plan AUTOSAR Concept and first AUTOSAR compatibility of selected
specifications are
created specification are created and SW modules is approved. First
tested and verified
and agreed executability is approved tools and generators are available
on an application

AUTOSAR concept (specification Realization of Run Time

Evaluated test and integration
and preparation of a de-facto Environment feasible and on
process (product oriented)
standard) is feasible and in plan track

WP10 / WP20
24 Friday, 06 July 2007
Colors

25 Friday, 06 July 2007