AUTOSAR proofs to be THE automotive software

platform for intelligent mobility

Dr.-Ing. Thomas Scharnhorst
AUTOSAR Spokesperson
Simon Fürst, BMW AG Tony Jaux, PSA Peugeot Citroën
Stefan Rathgeber, Continental Corporation Thomas Rüping, Robert Bosch GmbH
Lorenz Slansky, Daimler AG Kenji Nishikawa, Toyota Motor Company
Frank Kirschke-Biller, Ford Motor Company Dr. Carsten Krömke, Volkswagen AG
Rick Flores, General Motors

ELIV, Bonn Germany

October 18th -19th 2017
Overview

➢ Introduction
 Overview and achievements

➢ New challenges and use cases

➢ The Adaptive Platform

 Overview
 1st release of the Adaptive Platform 17-03
 Roadmap

➢ New cooperation model

 Agile development
 Collaboration with other standardization bodies

➢ Summary

2 19-October-2017 ELIV VDI Congress Bonn 2017

E/E innovations in vehicle development are increasing

90% of all
innovations
All major
innovations
Linked are driven
Networks by E/E

Infotainment Vehicles are

connected to
Electronic
the back-end
Mechanics Support

1970 1980 1990 2000 2010 2020

3 19-October-2017 ELIV VDI Congress Bonn 2017

AUTOSAR – Core Partners and Partners (June 2017)
29 Development Partners
9 Core Partners

44 Premium Partners
91 Associate Partners
19 Attendees

General Generic Standard Tools and Semi-

OEM Tier 1 Software Services conductors

4 19-October-2017 ELIV VDI Congress Bonn 2017

AUTOSAR vision
AUTOSAR aims to improve complexity management of integrated E/E architectures through
increased reuse and exchangeability of SW modules between OEMs and suppliers.
OEM b
Exchangeability
between
suppliers’ OEM c
OEM a Platform b.1 solutions
Platform b.2
Platform b.n

Supplier A Supplier B Platform c.1

Platform c.2
Platform a.1 ➢ Chassis ➢ Chassis Platform c.n
Platform a.2
Platform a.n ➢ Safety ➢ Safety
➢ Body/ ➢ Telematics
Exchangeability Comfort OEM d
between
Supplier C
manufacturers’ ➢ Body/Comfort
applications ➢ Powertrain

OEM f ➢ Telematics
Platform d.1
Platform d.2
Platform d.n
OEM e
Exchangeability
Platform f.1
between vehicle
Platform f.2 platforms
Platform f.n
Platform e.1
Platform e.2
Platform e.n

5 19-October-2017 ELIV VDI Congress Bonn 2017

Aims and benefits of using AUTOSAR
AUTOSAR aims to standardize the software architecture of Electronic Control Units (ECUs).
AUTOSAR paves the way for innovative electronic systems that further improve
performance, safety and environmental friendliness.

Yesterday AUTOSAR
Customer needs

Standardized
Methodology
▪ Adaptive Cruise Control
▪ Lane Departure Warning
Application ▪ Advanced Front Lighting
Software Software System
▪ …

Using standards

HW-specific
▪ Communication Stack

(ECUs)
▪ OSEK
Hardware Hardware ▪ Diagnostics
Hardware ▪ CAN, FlexRay
Hardware

➢ Hardware and software will be widely independent of each other.

➢ Development can be de-coupled by horizontal layers, reducing development time and costs.
➢ The reuse of software increases at OEM as well as at suppliers. This enhances quality and
efficiency during development.

6 19-October-2017 ELIV VDI Congress Bonn 2017

Overview

➢ Introduction
 Overview and achievements

➢ New challenges and use cases

➢ The Adaptive Platform

 Overview
 1st release of the Adaptive Platform 17-03
 Roadmap

➢ New cooperation model

 Agile development
 Collaboration with other standardization bodies

➢ Summary

7 19-October-2017 ELIV VDI Congress Bonn 2017

Motivation
Main drivers to develop the Adaptive Platform

Highly automated driving Car-2-X applications

Open and secure access to vehicle Increased Connectivity

8 19-October-2017 ELIV VDI Congress Bonn 2017

Selected main drivers for new automotive software systems (1/4)

Highly automated driving will be on the road.

➢ Driver temporarily/partially passes responsibility for driving task to vehicle

➢ Support of communication with traffic lights
Use cases
➢ Support of high-performance micro-controllers and computing
➢ Support of high quality map data

9 19-October-2017 ELIV VDI Congress Bonn 2017

Selected main drivers for new automotive software systems (2/4)

Car-2-X applications will require the interaction of vehicles and off-board systems.

➢ Secure on-board communication

➢ Support of cross domain computing platforms
Use cases
➢ Smartphone integration
➢ Integration of non-AUTOSAR systems

10 19-October-2017 ELIV VDI Congress Bonn 2017

Selected main drivers for new automotive software systems (3/4)

Open and secure access will require dedicated means for security

➢ Support secure cloud interaction

➢ Support of emergency vehicle preemption
Use cases
➢ Remote diagnostics and In-field flashing
➢ Support of distributed services e.g. repair and exchange handling

11 19-October-2017 ELIV VDI Congress Bonn 2017

Selected main drivers for new automotive software systems (4/4)

Upcoming use cases will lead to a stronger interaction of automotive software systems.

ECU1 SW-C2

SW-C1 SW-C5
SW-C6
ECU4 ECU2 ECU3
Server
SW-C3 SW-C4

Statically deployed Dynamically

deployed application Off Board application
application

➢ Consideration of non-AUTOSAR systems within methodology

Use cases ➢ Dynamic deployment of software components
➢ Interaction with non-AUTOSAR and off-board systems

12 19-October-2017 ELIV VDI Congress Bonn 2017

Technology Drivers

Ethernet
➢ High bandwidth
➢ Communication system is no longer a limiting aspect
➢ Switched network
➢ Efficient point-to-point communication
➢ Efficient transfer of long messages

Processors
➢ Switch from microcontroller to processors with external
memory (and maybe filesystems)
➢ Many core processors
➢ Parallel computing
➢ „Cheap“ availability of computing power

Heterogeneous architectures
➢ Special purpose processors

13 19-October-2017 ELIV VDI Congress Bonn 2017

Overview

➢ Introduction
 Overview and achievements

➢ New challenges and use cases

➢ The Adaptive Platform

 Overview
 1st release of the Adaptive Platform 17-03
 Roadmap

➢ New cooperation model

 Agile development
 Collaboration with other standardization bodies

➢ Summary

14 19-October-2017 ELIV VDI Congress Bonn 2017

AUTOSAR Adaptive Platform – emerging from deeply embedded systems

Application framework
SHFrontLeft: PM:
▪ Support for run-time configuration SeatHeatingContr Power
▪ Service-oriented communication olAndDrivers Management
▪ Partial update

Formats for design data

▪ Planning of dynamic behavior (e.g. constraints
Ethernet
for scheduling and communication)
▪ Consider automotive specific cooperation
scenarios Planning of
dynamic
▪ Support integration with existing systems
communication
(Classic Platform)

Reference architecture
▪ Reuse existing (non-automotive) standards
▪ Ease software development
▪ Support automotive use-cases and protocols
▪ Reference Implementation

… and many more

15 19-October-2017 ELIV VDI Congress Bonn 2017

Architectural Overview
Functional Clusters

AUTOSAR Runtime for Adaptive Application (ARA)

API API API Service Service Service

Software
Time Execution Security
Configuration Diagnostics
Management Management Management
Operating Management
system
(*)
API API Adaptive Platform Services

Platform API API API

Health Persistency
Hardware
Bootloader Management Logging and Tracing Communications
Acceleration

Adaptive Platform Foundation

(Virtual) Machine / Hardware

AUTOSAR Runtime for Adaptive Applications = Σ of all Functional Cluster APIs / Services
API Programming language specific API for a Functional Cluster as specified in SWS
Service Service Interface of a Functional Cluster. API is generated according to ara::com specification
Functional Behavioral specification of Functional Cluster
Cluster
(*) POSIX OS, not separately standardized

16 19-October-2017 ELIV VDI Congress Bonn 2017 639_9020

Address space virtualization

Each application lives in its own protected

Each application lives in its own address space
address space

Access to platform
Application 1 Application 2
functionality via
libraries API(libc) API API API(libc) API API

Service Service Service

Communication via Software
impl. spec. IPC Time Execution Security
Configuration Diagnostics
Management Management Management
Management

Adaptive AUTOSAR Services

Persistency
Operating
System (*)

Platform
Logging and Hardware Communication
Health
Tracing Acceleration Management
Bootloader Management
Adaptive AUTOSAR Foundation

(Virtual) Machine / Hardware

(*) POSIX OS, not separately standardized

17 19-October-2017 ELIV VDI Congress Bonn 2017

Service-oriented communication (1/2)
Dynamic establishing of communication path

ECU I ECU II ECU n

Brake assistance Application 2 Application 3 Application n

ServiceFind()

...
P1 P2 P3 Skeleton Skeleton Skeleton

Communication Communication
Communication Management Management Management
Middleware Middleware Middleware

Ethernet
➢ Service Discovery finds all local and remote Service Instances in the System.
➢ Available Service Instances are represented by Proxies (P1 … P3) to the Application.
➢ Application can choose which Service Instance(s) to use.

18 19-October-2017 ELIV VDI Congress Bonn 2017

Service-oriented Ethernet communication (2/2)

Service Interface
Definition
Service Service
Consumer Implementation
Application

API(libc) Communication API Proxy Skeleton

Provided Interface
Events
Methods
Communication
Management
Fields

SOME/IP-Serialization
Operating E2E Protection
system (*)

SOME/IP

SOME/IP Service
Bootloader Discovery
Adaptive AUTOSAR Foundation

(Virtual) Machine / Hardware

(*) POSIX OS, not separately standardized

19 19-October-2017 ELIV VDI Congress Bonn 2017

Execution model

Classic Platform vs. Adaptive Platform

ECU ECU
SWC Application

Software specifies
Component Runnables
Manifest Callbacks Threads
Description

creates creates
executes

executes void main()

RTE
Influences
generated executes
code
Communication Execution
Management Management

configures

20 19-October-2017 ELIV VDI Congress Bonn 2017

1st Release finalized March 2017

AUTOSAR Runtime for Adaptive Application

Adaptive AUTOSAR Services

API API

Execution Service
Service Service
Service Service
Management
Software
Software
Security
Security
Configuration
Configuration Diagnostics
Management
Management
Operating API Management
Management
System (*)
Persistency

API API API

API API

Platform Health Logging and Hardware

Hardware
Tracing Communications
Bootloader Management Acceleration
Acceleration

Adaptive AUTOSAR Foundation

(Virtual) Machine / Hardware

(*) POSIX OS, not separately standardized

The Adaptive Platform is developed iteratively – the functionality grows with each release

21 19-October-2017 ELIV VDI Congress Bonn 2017

AUTOSAR Adaptive Platform Feature Roadmap
Safety
• Platform Health Management
• C++14 Coding Guideline
• E2E Communication Integrity
Logging / Tracing
• Logging and Tracing
Methodology
• Diagnostic Extract
• Manifests
• Methodology Extensions for
Adaptive
Persistency
• Data Storage
Diagnostics
• DTC Management
• ISO 14229 / ISO 13400
Communication
• Service-Discovery and
Service-based Communication
• Events, Fields and Methods
• Language-Binding: C++
• Inter-Process-Communication
• Bus-Binding: SOME/IP
Execution Management
• Integration of Applications onto
Platform
• Start and Stop of Applications
POSIX Operating System
• OS Application Interface
(PSE51 & C++STL)
AP R17-03
22 19-October-2017
Security
Security • Crypto API
• Crypto API • Authentication & Certificates
• Authentication & Certificates • Key Management
• Key Management • Secure Communication
• Support of trusted platform
• Secure Communication
Security • Support of trusted platform Safety
• Crypto API • Maintenance and
• Authentication & Certificates Safety
Improvements
• Key Management • Platform Health Management
• Redundancy Mechanisms
• Secure Communication • Safety concept for AP
• E2E Communication Integrity Logging / Tracing
Safety • Maintenance and
• Platform Health Management Logging / Tracing Improvements
• C++ 14 Coding Guideline • Maintenance and
Improvements SW-Configuration Mgnt
Logging / Tracing • Container Support?
• Logging and Tracing SW-Configuration Mgnt • Package Download over the
• Package Management air
Methodology • Installation routine • Package Management
• Methodology Extensions for • Diagnostic Client • Installation routine
Adaptive • Diagnostic Client
• Service to signal modeling Methodology
• Predefined Data Types • Methodology Extensions for Methodology
Adaptive • Maintenance and Improvements
Persistency • Service to signal modeling
• Data Storage • Common System Model
• Safe Data Storage Persistency Persistency
• Persistent Data Encryption • Maintenance and • Maintenance and
Improvements
Diagnostics Improvements
• ISO 13400 / ISO 14229 Diagnostic Diagnostic
completion • Maintenance and • Maintenance and
• Handling of SW Clusters Improvements Improvements
Communication Communication Communication
• Time Synchronization • Signal-based Communication • Vehicle API
• Support of RESTful • Support of RESTful • Further Language-Bindings
• Network Management Ethernet • LIN Support
Execution Management
• Resource Management Execution Management • Support of CAN and CAN-FD
• Parallel Processing by HWA • Resource Management Execution Management
• Recovery action framework • Parallel Processing by HWA • Maintenance and
• Machine State handling • Recovery action framework Improvements
AP R17-10 AP R18-03 AP R18-10
ELIV VDI Congress Bonn 2017
The Challenge: Integration of Different Platforms

Classic Classic Non- Non-

Adaptive Adaptive
Application Application AUTOSAR AUTOSAR
Application Application
SW-C SW-C Application Application

Runtime Environment Runtime Environment Adaptive AUTOSAR API

(ARA)
Service Layer Service Layer Adaptive AUTOSAR
ECU Abstraction C C Services
ECU Abstraction
Layer D Layer D
Microcontroller Microcontroller
Abstraction Layer Abstraction Layer AUTOSAR Foundation
Non-AUTOSAR
Microcontroller Microcontroller (Virtual) Machine / Hardware
Non-AUTOSAR Offboard
AUTOSAR Classic Platform AUTOSAR Classic Platform AUTOSAR Adaptive Platform Basic Software System

e.g. SOME/IP

Software Abstraction Common Bus Interface Specification

23 19-October-2017 ELIV VDI Congress Bonn 2017

Overview

➢ Introduction
 Overview and achievements

➢ New challenges and use cases

➢ The Adaptive Platform

 Overview
 1st release of the Adaptive Platform 17-03
 Roadmap

➢ New cooperation model

 Agile development
 Collaboration with other standardization bodies

➢ Summary

24 19-October-2017 ELIV VDI Congress Bonn 2017

The first release 17-03 already provides specifications and software

Development in AUTOSAR Feature Teams

validate

AUTOSAR Specifications AUTOSAR Software

Implementations
Licensing for

Licensing for
exploitation

exploitation
improve

Exploitation of released Specifications and exemplary Software

Implementation by AUTOSAR partners

25 19-October-2017 ELIV VDI Congress Bonn 2017

Organization of development of the Adaptive Platform
Work mode and contributions

Joint expert Joint expert Joint expert

group meeting group meeting
group meeting group meeting
Run Release
3–4
3 4 months
months
approx. twice a year

Sprint Continuous development

according to Scrum
Sprint planning meetings
per feature team defined by FBO 2-5
Days

4 Weeks

Feature Sprint Scrum Deliverable

Backlog Backlog Meetings Increment

refinement sprint sprint sprint sprint

planning monitoring review retrospective

26 19-October-2017 ELIV VDI Congress Bonn 2017

Releases and revisions of AUTOSAR

2016 2017 2018

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Classic Platform

R4.3.0 R4.3.1 R4.4.0

Release 1.0.0
Foundation

R 1.0.0 R 1.1.0 R 1.2.0 R 1.X.Y

Synchronized
Release

Release R 17-03
Adaptive Platform

R 17-03 R 17-10 R 18-03 R 18-10

Development Evolution Maintenance Issue Notice

27 19-October-2017 ELIV VDI Congress Bonn 2017

Overview

➢ Introduction
 Overview and achievements

➢ New challenges and use cases

➢ The Adaptive Platform

 Overview
 1st release of the Adaptive Platform 17-03
 Roadmap

➢ New cooperation model

 Agile development
 Collaboration with other standardization bodies

➢ Summary

28 19-October-2017 ELIV VDI Congress Bonn 2017

Architectural Overview
Classic Platform vs. Adaptive Platform
Based on OSEK
Execution of code directly from ROM
Same address space for all
applications (MPU support for safety)
Optimized for signal-based
communication (CAN, FlexRay)
Fixed task configuration
Specification
30 19-October-2017 ELIV VDI Congress Bonn 2017
Based on POSIX (PSE51)
Application is loaded from persistent
memory into RAM
Each application has its own (virtual)
address space (MMU support)
Service-oriented communication
Support of multiple (dynamic)
scheduling strategies
Standard is defined by specification
Code as reference implementation
Summary

Achievements
➢ Established a worldwide software standard focusing on
automotive applications
➢ Classic Platform is massively used in series production

AUTOSAR
➢ Already launched: AUTOSAR Classic Platform, AUTOSAR
Standards
Foundation and AUTOSAR Acceptance Tests
➢ First release of AUTOSAR Adaptive Platform 17-03 launched
➢ Reference Implementation available for partners

Future of
➢ Improvement and stabilization of existing standard
AUTOSAR
➢ Anticipate the future by providing the next generation of
platform software
➢ Creation of new eco-systems by new collaboration models

AUTOSAR will continue to be THE creator of automotive software standards.

31 19-October-2017 ELIV VDI Congress Bonn 2017

More information available online
More information about
AUTOSAR:
http://www.autosar.org

Become a partner and

get exploitation rights for
the AUTOSAR standard
admin@autosar.org

For information only

(see disclaimer)
Published Releases

32 19-October-2017 ELIV VDI Congress Bonn 2017