AUTOSAR proofs to be THE automotive software … proofs to be THE automotive software platform for...

AUTOSAR proofs to be THE automotive software platform for intelligent mobility

Dr.-Ing. Thomas ScharnhorstAUTOSAR Spokesperson

ELIV, Bonn GermanyOctober 18th -19th 2017

Simon Fürst, BMW AG Stefan Rathgeber, Continental Corporation Lorenz Slansky, Daimler AG Frank Kirschke-Biller, Ford Motor Company Rick Flores, General Motors

Tony Jaux, PSA Peugeot Citroën Thomas Rüping, Robert Bosch GmbH Kenji Nishikawa, Toyota Motor Company Dr. Carsten Krömke, Volkswagen AG

2

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

ELIV VDI Congress Bonn 201719-October-2017

90% of all innovations

Linked Networks

Infotainment

Electronic SupportMechanics

E/E innovations in vehicle development are increasing

All major innovations are driven

by E/E

Vehicles are connected to the back-end

1970 1980 1990 2000 2010 2020


AUTOSAR – Core Partners and Partners (June 2017)

91 Associate Partners19 Attendees

9 Core Partners 29 Development Partners

ELIV VDI Congress Bonn 2017

44 Premium Partners

GeneralOEM

StandardSoftware

Semi-conductors

GenericTier 1

Tools andServices

19-October-20174

http://www.avelabs.com/

OEM f

Exchangeabilitybetween suppliers’solutions

Exchangeabilitybetween vehicle platforms

Exchangeabilitybetween manufacturers’applications

Platform d.nPlatform d.2Platform d.1

Platform e.nPlatform e.2Platform e.1

Platform f.nPlatform f.2Platform f.1

Platform c.nPlatform c.2Platform c.1

Platform a.nPlatform a.2Platform a.1

OEM e

OEM aPlatform b.n

Platform b.2Platform b.1

OEM b

OEM d

OEM c

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.

Supplier A➢Chassis➢Safety➢Body/

Comfort

Supplier B➢Chassis➢Safety➢Telematics

Supplier C➢Body/Comfort➢Powertrain➢Telematics


Aims and benefits of using AUTOSAR

➢ 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.

Yesterday

Hardware

Software

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.

Application Software

Hardware

AUTOSAR

HardwareHardware

Customer needs▪ Adaptive Cruise Control▪ Lane Departure Warning▪ Advanced Front Lighting

System▪ …

Using standards▪ Communication Stack▪ OSEK▪ Diagnostics▪ CAN, FlexRay

HW

-spe

cific

(EC

Us)

Stan

dard

ized

Met

hodo

logy


Overview





➢ Summary


Motivation Main drivers to develop the Adaptive Platform


Highly automated driving

Open and secure access to vehicle Increased Connectivity

Car-2-X applications

19-October-20178

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➢ Support of high-performance micro-controllers and computing ➢ Support of high quality map data

Use cases



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

➢ Secure on-board communication➢ Support of cross domain computing platforms➢ Smartphone integration➢ Integration of non-AUTOSAR systems

Use cases



Open and secure access will require dedicated means for security


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

Use cases

19-October-201711


➢ Consideration of non-AUTOSAR systems within methodology➢ Dynamic deployment of software components➢ Interaction with non-AUTOSAR and off-board systems

SW-C2

SW-C3 SW-C4

SW-C5SW-C6

ECU1

ECU2 ECU3Server

SW-C1

ECU4

Use cases

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

Statically deployed application

Dynamically deployed application Off Board application


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

Technology Drivers

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


http://www.shutterstock.com/subscribe.mhtml

Overview





➢ Summary


AUTOSAR Adaptive Platform – emerging from deeply embedded systems

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

Application framework▪ Support for run-time configuration▪ Service-oriented communication▪ Partial update

Formats for design data▪ Planning of dynamic behavior (e.g. constraints

for scheduling and communication)▪ Consider automotive specific cooperation

scenarios▪ Support integration with existing systems

(Classic Platform)

SHFrontLeft: SeatHeatingContr

olAndDrivers

PM: Power

Management

… and many more

Ethernet

Planning of dynamic

communication


Architectural OverviewFunctional Clusters

Adaptive Platform Foundation

(Virtual) Machine / Hardware

Adaptive Platform Services

Operating system

(*)

BootloaderHardware

Acceleration

Platform Health

Management

Execution Management

Software Configuration Management

SecurityManagement Diagnostics

Communications

AUTOSAR Runtime for Adaptive Application (ARA)

Logging and TracingPersistency

API API API

API

API API API

Service Service Service

ELIV VDI Congress Bonn 2017 639_9020

FunctionalCluster

Behavioral specification of Functional Cluster

API Programming language specific API for a Functional Cluster as specified in SWS

TimeManagement

API

AUTOSAR Runtime for Adaptive Applications = Σ of all Functional Cluster APIs / Services

(*) POSIX OS, not separately standardized

Service Service Interface of a Functional Cluster. API is generated according to ara::com specification

19-October-201716

Adaptive AUTOSAR Foundation

Adaptive AUTOSAR Services

Address space virtualization


Application 1

API(libc) APIAPI


Service

Security Management

Service

Diagnostics

Service

Bootloader

Operating System (*)


Persistency

Platform Health

Management

Logging andTracing

Hardware Acceleration

Communication Management

Time Management

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

Communication via impl. spec. IPC

Each application lives in its own protected address spaceEach application lives in its own address space



19-October-201717

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


ECU n

...

Ethernet

ECU IIECU I

Communication ManagementMiddleware



Application nApplication 3Application 2Brake assistance

Skeleton SkeletonSkeletonP1 P2 P3

ServiceFind()

➢ 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.

19-October-201718

Service-oriented Ethernet communication (2/2)



Application

API(libc) Communication API

Bootloader

Operating system (*)


Proxy SkeletonProvided InterfaceEventsMethodsFields

ServiceImplementation

ServiceConsumer

SOME/IP

SOME/IP Service Discovery

SOME/IP-SerializationE2E Protection


Service Interface Definition


19-October-201719

ECUECU

Execution model


SWC

RTE

Runnables

SoftwareComponentDescription

specifies

Influences generated

code

executes

Application


CallbacksManifest

configures

executes

Threads

void main()

executes

creates


Classic Platform Adaptive Platformvs.

creates

19-October-201720

1st Release finalized March 2017


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




Operating System (*)

BootloaderHardware

AccelerationPlatform Health Management

Execution Management Software

Configuration Management

SecurityManagement Diagnostics

Communications

AUTOSAR Runtime for Adaptive Application

Logging and Tracing

Persistency

API API

API

API API API API

Service Service Service


Service

SecurityManagement

Service

Hardware Acceleration

API


19-October-201721

Logging / Tracing• Maintenance and

Improvements

AUTOSAR Adaptive Platform Feature Roadmap


Execution Management• Integration of Applications onto

Platform• Start and Stop of Applications

Communication• Service-Discovery and

Service-based Communication• Events, Fields and Methods• Language-Binding: C++• Inter-Process-Communication• Bus-Binding: SOME/IP

AP R17-03 AP R17-10 AP R18-03 AP R18-10

Persistency• Data Storage

Diagnostics• DTC Management• ISO 14229 / ISO 13400

POSIX Operating System• OS Application Interface

(PSE51 & C++STL)

Methodology• Diagnostic Extract• Manifests• Methodology Extensions for

Adaptive

Execution Management• Resource Management• Parallel Processing by HWA• Recovery action framework

Persistency• Maintenance and

Improvements

SW-Configuration Mgnt• Package Management• Installation routine• Diagnostic Client

Diagnostic• Maintenance and

Improvements

Methodology• Methodology Extensions for

Adaptive• Service to signal modeling

Execution Management• Resource Management• Parallel Processing by HWA• Recovery action framework• Machine State handling

Communication• Time Synchronization• Support of RESTful

Persistency• Data Storage• Safe Data Storage• Persistent Data Encryption

Diagnostics• ISO 13400 / ISO 14229

completion• Handling of SW Clusters

Methodology• Methodology Extensions for

Adaptive• Service to signal modeling• Predefined Data Types

Security• Crypto API• Authentication & Certificates• Key Management• Secure Communication

Safety• Platform Health Management• Safety concept for AP• E2E Communication Integrity

Security• Crypto API• Authentication & Certificates• Key Management• Secure Communication• Support of trusted platform

Execution Management• Maintenance and

Improvements

Persistency• Maintenance and

Improvements

Communication• Vehicle API• Further Language-Bindings• LIN Support• Support of CAN and CAN-FD

SW-Configuration Mgnt• Container Support?• Package Download over the

air• Package Management• Installation routine• Diagnostic Client

Diagnostic• Maintenance and

Improvements

Methodology• Maintenance and Improvements• Common System Model

Safety• Maintenance and

Improvements• Redundancy Mechanisms

Security• Crypto API• Authentication & Certificates• Key Management• Secure Communication• Support of trusted platform

Logging / Tracing• Logging and Tracing

Safety• Platform Health Management• C++14 Coding Guideline• E2E Communication Integrity

Safety• Platform Health Management• C++ 14 Coding Guideline

Logging / Tracing• Logging and Tracing

Logging / Tracing• Maintenance and

Improvements

Communication• Signal-based Communication• Support of RESTful• Network Management Ethernet

19-October-201722

The Challenge: Integration of Different Platforms

Software Abstraction Common Bus Interface Specification

AUTOSAR Adaptive Platform

Adaptive Application

Adaptive Application

Non-AUTOSAR Basic Software

Non-AUTOSAR Application

ClassicApplication

SW-C

Non-AUTOSAR OffboardSystem

Non-AUTOSAR Application

AUTOSAR Classic Platform

Classic Application

SW-C

AUTOSAR Classic Platform

Microcontroller

Runtime Environment

CD

Microcontroller Abstraction Layer

ECU Abstraction Layer

Service Layer

e.g. SOME/IP

AUTOSAR Foundation(Virtual) Machine / Hardware


Adaptive AUTOSAR API (ARA)

Microcontroller

Runtime Environment

CD

Microcontroller Abstraction Layer

ECU Abstraction Layer

Service Layer


Overview





➢ Summary


The first release 17-03 already provides specifications and software

Development in AUTOSAR Feature Teams

AUTOSAR Specifications AUTOSAR Software Implementations

Exploitation of released Specifications and exemplary Software Implementation by AUTOSAR partners

validate

improve

Lice

nsin

g fo

rex

ploi

tatio

n

Lice

nsin

g fo

r ex

ploi

tatio

n


FeatureBacklog

SprintBacklog

ScrumMeetings

DeliverableIncrement

refinement sprintplanning

sprintmonitoring

sprintreview

sprintretrospective

4 Weeks

2-5 Days

Organization of development of the Adaptive PlatformWork mode and contributions


Joint expert group meeting



3 – 4 months

Sprint planning meetingsper feature team defined by FBO

Continuous development according to Scrum

3 – 4 monthsRun

Sprint

group meeting

Releaseapprox. twice a year

19-October-201726

2016

Releases and revisions of AUTOSAR

Development Evolution Maintenance Issue Notice

Q1 Q2 Q3 Q4 Q12017

Q2 Q3 Q4 Q12018

Q2 Q3 Q4

R4.3.0

R 17-03

R4.3.1

Release 1.0.0

Classic Platform

Adaptive PlatformRelease R 17-03

Foundation

R 1.0.0


R 17-10

R4.4.0

R 1.1.0 R 1.2.0

R 18-03 R 18-10

R 1.X.Y

Synchronized Release

19-October-201727

Overview





➢ Summary


Architectural OverviewClassic Platform vs. Adaptive Platform


Based on OSEK Based on POSIX (PSE51)

Execution of code directly from ROM Application is loaded from persistent memory into RAM

Same address space for all applications (MPU support for safety)

Each application has its own (virtual) address space (MMU support)

Optimized for signal-basedcommunication (CAN, FlexRay)

Service-oriented communication

Fixed task configuration Support of multiple (dynamic) scheduling strategies

Specification Standard is defined by specificationCode as reference implementation

19-October-201730

Summary

Achievements

AUTOSAR Standards

➢ Established a worldwide software standard focusing on automotive applications

➢ Classic Platform is massively used in series production

➢ Already launched: AUTOSAR Classic Platform, AUTOSAR Foundation and AUTOSAR Acceptance Tests

➢ First release of AUTOSAR Adaptive Platform 17-03 launched➢ Reference Implementation available for partners

Future of AUTOSAR

➢ Improvement and stabilization of existing standard➢ 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.


More information available onlineMore information about

AUTOSAR:http://www.autosar.org

Become a partner and get exploitation rights for the AUTOSAR standard

[email protected]

For information only (see disclaimer)

Published Releases


http://www.autosar.org/

mailto:[email protected]

http://www.autosar.org/index.php?p=3&

AUTOSAR proofs to be THE automotive software … proofs to be THE automotive software platform for...

Documents

Transcript of AUTOSAR proofs to be THE automotive software … proofs to be THE automotive software platform for...