autosar introduction...wg -ap di demonstrator integration st system tests lead working group working...

Presenter

Occasion (Meeting, Conference, etc.)

27 October

2020

AUTOSAR Introduction

Location @ Host

The vision, the partnership and current features in a nutshell

Agenda

27 October

2020AUTOSAR Introduction

Introduction of the AUTOSAR Partnership

Challenges in the automotive industry

Architecture and recent features

Smart solutions based on AUTOSAR

Processes and quality

Outlook

3 of 65

Agenda

27 October







Outlook

4 of 65

AUTOSAR Introduction

(AUTomotive Open System ARchitecture)

is a worldwide development partnership of car manufacturers, suppliers and other

companies from the electronics, semiconductor and software industry.

AUTOSAR Introduction27 October

20205 of 65

AUTOSAR Vision

27 October


AUTOSAR aims to improve complexity management of integrated E/E architectures through

increased reuse and exchangeability of SW modules between OEMs and suppliers.

Exchangeability

between manufacturers’

applications

Exchangeability

between suppliers’

solutions

Exchangeability

between vehicle

platforms

Supplier A

• Chassis

• Safety

• Body/Comfort

Supplier B

• Chassis

• Safety

• Telematics

Supplier C

• Body/Comfort

• Powertrain

• Telematics

Platform a.1, a.2, a.n

Platform b.1, b.2, b.n

Platform c.1, c.2, c.n

Platform d.1, d.2, d.n

Platform e.1, e.2, e.n

Platform f.1, f.2, f.n

6 of 65

Aims and benefits of using AUTOSAR

27 October

2020AUTOSAR Introduction 7 of 65

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

• Hardware and software –

widely independent of each

other.

• Development can be de-

coupled (through abstraction)

by horizontal layers, reducing

development time and costs.

• Reuse of software

enhances quality and

efficiency

Proprietary

Application Software

Standardized Basic Software

StandardizedMethodology

HW-specific(ECUs)

Standardized Middleware

Hardware

Hardware specific

Hardware

Basic

Software

Application

Software

Exploitation of the standard provides significant benefits

27 October


• Establish development distribution among

suppliers

• Compete on innovative functions with

increased design flexibility

• Simplify software and system integration

• Reduce overall software development costs

An industry

standard is

established.

Supplier

Tool provider

New marketentrant

OEM

8 of 65


27 October


• Enable more efficent variant handling

• Reuse software modules across OEMs

• Increase efficiency of application development

• Invent new business models

An industry

standard is

established.

Supplier

Tool provider

New marketentrant

OEM

9 of 65


27 October


• Interface with development processes

• Embed tools into an overall tool environmentAn industry

standard is

established.

Supplier

Tool provider

New marketentrant

OEM

10 of 65


27 October


• Enable new business models by means of

standardized interfaces

• Easily understand how automotive software is

developed

An industry

standard is

established.

OEM

Supplier

Tool provider

New marketentrant

11 of 65

More Than 280 AUTOSAR Partners

27 October


9 Core Partners

2 Strategic Partners56 Premium Partners

51 Development Partners

+ 144 Associate

Partners

+ 24 Attendees

27 October


History and current state – Total: 284

Geographical distribution of partners(last update 02.09.2020)

Europe: 137Core: 6

Strategic: 0

Premium: 27

Development: 29

Associate: 55

Attendee: 20

Africa: 2Core: 0

Strategic: 0

Premium: 0

Development: 2

Associate: 0

Attendee: 0

Asia: 112Core: 1

Strategic: 2

Premium: 23

Development: 16

Associate: 66

Attendee: 4

North America: 35Core: 2

Strategic: 0

Premium: 6

Development: 4

Associate: 23

Attendee: 0

Partner Status27 October

202014 of 65

Legal Team

AUTOSAR Organization

AUTOSAR Introduction 15 of 65

Core and Strategic PartnerCore, Strategic, Premium and

Development Partner

Off

icia

l A

UT

OS

AR

ro

les

Legend

Executive Board

Steering Committee

Project Leader Team

Working Groups

OSS-CBOpen Source CB

CCBChange Control Board

CF-CCBConsensus Finding CCB

Core Partner

27 October

2020

Governance

Strategic Management

Technical Steering

Standardization

Communication Team

Project Leader Team

Classic Platform Working Groups (CP) Adaptive Platform Working Groups (AP)

Cross-standard Working Groups (for FO, CP, AP)

Working Groups


WG-A Architecture Team

WG-CP-RTERuntime Environment

WG-AP-DIDemonstrator Integration

WG-AP-STSystem Tests

Lead Working Group

Working Group

Legend:

WG-AP-EMOExecution Man. & OS

WG-UCMUpdate & Conf. Management

WG-CP-MCLMCAL and NVRAM

WG-AP-PERPersistency

WG-CP-LIBLibraries

WG-CP-MCBDMulticore BSW Distr.

WG-MT Methodology and Templates

WG-SEC Automotive Security

WG-SAFFunctional Safety

WG-AP-CCTCentral Coding Team

27 October

2020

WG-AP-CLDCloud Services

WG-RESResources

WG-DIADiagnostics

WG-V2XVehicle to X

WG-AIFApplication Interfaces

WG-IVCIn-Vehicle COM

WG-TSYTime Synchronization

User Group Structure


User Groups

UG-IEImproved Exploitation

• 6 thesis on optimizing the use

of AUTOSAR

• Establishment of Adaptive

Platform

UG-NANorth America

UG-CNChina

• Common Training: OEM-Tier1

Workflows/ Security

• Safety

• Ethernet

• Demonstrator development

• BSW integration

27 October

2020

Groups, Boards and Task Forces

18 of 65

Group Type Initiated by Main Tasks Coaching Contact person Reporting to

Lead WG Permanent PL Team - Technical supervision of WGs and

concept groups

- Harmonization of technical content

- Assignment of concepts to WGs

PL Coach WG Speaker PL Team

WG Permanent PL Team - Expert statements

- Responsibility for documents and code

development

- Assessment of concepts

PL Coach WG Speaker PL Team

Subgroup Permanent WG WG substructure for a dedicated branch of

WG content

- Subgroup Speaker WG

Control Board Permanent PL Team Controlling task within AUTOSAR

processes (e.g. CM, QM, SDE or RM) such

as CCB, CF-CCB and OSS-CB

PL Team CM, QM or RM CM, QM or RM

Concept Group On demand

(project-based)

CP/SP/PP/DP Creation and processing of a concept or a

set of concepts according to concept

process

Responsibility for concept validation

- Concept Owner(s) Lead WG, WG, PL

Team; cf. concept

handling process

Task Force On demand

(project-based)

WG or

PL Team

Dedicated task with defined due date - TF Speaker WG or PL Team

AUTOSAR Introduction27 October

202018 of 65

AUTOSAR Deliverables

27 October


Common documents and

specifications for all

standards

Foundation

Acceptance

Test

Application

Interfaces

Adaptive PlatformClassic Platform

Sensor

Interfaces

Legend

A B

Released as an own standard

Released as part of the standard it is extending

A extends B

A planned to extend BA B

19 of 65

Agenda

27 October







Outlook

20 of 65

Challenges – selected main drivers

27 October


Highly automated driving

21 of 65


27 October


Car-2-X applications

Internet of Things and cloud services

22 of 65


27 October


Increasing data rates

23 of 65


27 October


New processor technologies

24 of 65


27 October


Trust

25 of 65

Challenges – Driving changes in E/E Architectures

New types of in vehicle computers are required to

fulfill the needs of

• performance,

• flexibility and

• connectivity

But

• backwards compatibility with existing

solutions,

• fulfillment of increasing requirements for safety

and security

is a must as well.

27 October

2020

90% of all

innovations

Linked

NetworksInfotain-

ment

Electronic

SupportMechanics

All major

innovations

are driven

by E/E

Vehicles are

connected

to the back-

end

1970 1980 1990 2000 2010 2020

Modular

Integration

Centralization

Domain Fusion

Vehicle Computer

Vehicle / Domain Controller

Deeply Embedded ECUs

Obsolete ECUs

Intelligent Actuators / Sensors

Integration process

26 of 65AUTOSAR Introduction

AUTOSAR’s answer to the upcoming challenges

Real time

Requirements

High,

in the range of micro-sec

Mid,

in the range of milli-sec

Low,

in the range of sec

Safety

Criticality

High,

up to ASIL-D

High,

at least ASIL-B

Low,

QM

Computing

power

Low,

~ 1000 DMIPs

High,

> 20.000 DMIPs

High,

~ 10.000 DMIPs

Infotainment

AUTOSAR

Classic Platform

27 October


?AUTOSAR

Adaptive Platform

27 of 65

… are the prerequisite for ADAS applications

AUTOSAR Adaptive PlatformThe 3 Pillars of the Adaptive Platform …

27 October


Service-Oriented Communication

Cloud

Cloud

DTLS

IPsec

external

communication

process

separation

process-sys

separation

SecOC

crypto

IAM

Platform

failure

handling

exception-less

APIs

E2E for

SOA

safe data

storage

super-

vision

resource

budgeting

New

New

New

New

New

in-vehicle

communication

I – Safe & Secure II – Connected III – Dynamic & Updateable

Software

Package

Executable

Manifest

App Development

Manifest

28 of 65

… to form the standard solution for today´s automobiles

AUTOSAR Classic PlatformThe 4 Pillars of the Classic Platform…

27 October


I – Functional Safety II – Efficiency III – Field Proven IV – Performance

▪ Mature safety features

(e.g. watchdog, E2E

communication

protection,…)

▪ Scalable from QM up to

ASIL D

▪ AUTOSAR stacks from

different vendors

▪ Cost effective by

supporting a wide range

of µControllers

▪ Flexibility due to CDD

▪ Mature by many years

of application

▪ High quality due to

widespread

implementations

▪ Established

development processes

▪ Hard real time

capabilities

▪ Event triggered

applications

▪ Flexible by supporting a

wide range of protocols

and networks

▪ Scalability by

configuration

!

29 of 65

Strengthen and Extend Pillars of AUTOSARAUTOSAR USP

Strengthen Safety & Security

➔ Support standard failure and attack scenarios

➔ Extend test and verification

➔ Improve processes

Strengthen connectivity

➔ Extend standard cloud services

➔ Think about AUTOSAR App store

➔ Enable connectivity to smart phones and zone

ECUs

Develop flexible updates during life time

➔ Improve modularity e.g. define cluster interfaces

➔ Provide means for system description

27 October


Safety & Security

Connectivity

Updateability

4,6

Methodology

Tests

Architecture

Application

Interfaces

30 of 65

Agenda

27 October







Outlook

31 of 65

Applications

Non-

AUTOSAR

Basic

Software

Application Layer

AUTOSAR

Adaptive

Platform

Application Layer

AUTOSAR

Classic

Platform

RTE

Applications

Non-

AUTOSAR

Basic

Software

AUTOSAR in a Vehicle Network

27 October


Common Bus Interface Specification

e.g. SOME / IP BUS

Application Layer

AUTOSAR

Classic

Platform

RTE

32 of 65

AUTOSAR FoundationCommon Features

The Foundation assures compatibility of the different

AUTOSAR standards and therefore contains all

common artifacts such as …

27 October


AUTOSAR FoundationThe Methodology, derived out of the Meta Model, …

27 October


… provides means to describe the AUTOSAR

architecture with all its interfaces

… defines exchange formats and description

templates (e.g. manifest) to enable

• a seamless integration of the complete

vehicle E/E architecture,

• the automatized configuration of the µC- and

µP-software stacks and

• the seamless integration of application

software

… supports means to ensure safety and security

of the system

… provides templates to document the standard

Meta Model

Methodology

TestsApplication

InterfacesArchitecture

µC µP

Doc

level

of

ab

str

acti

on

Legend

B

A

A implements B

Co

nfi

gu

rati

on

34 of 65

AUTOSAR Classic Platform Layered Software Architecture (1/2)

The layered architecture of the classic

platform basically supports

• Hardware abstraction

• Scheduling of runnables and tasks (OS)

• Communication between applications

on the same hardware and over the

network

• Diagnosis and diagnostic services

• Safety- and

• Security Services

27 October


Microcontroller

Microcontroller Abstraction Layer

ECU Abstraction Layer

Services Layer

Runtime Environment

Application Layer

Complex

Drivers

35 of 65

AUTOSAR Classic Platform Layered Software Architecture (2/2)

27 October


Microcontroller

System

Services

Runtime Environment

Application Layer

Complex

Drivers

Memory

Services

Off-board

Communication

Services

I/O HW

Abstraction

Communication

Services

Crypto

Services

Memory

Drivers

Wireless

Communication

Drivers

I/O DriversCommunication

Services

Crypto

Drivers

Microcontroller

Drivers

Memory

HW Abstraction

Wireless

Communication

HW Abstraction

Communication

HW Abstraction

Crypto

HW Abstraction

Onboard

Device

Abstraction

AUTOSAR Runtime for Adaptive Applications (ARA)

AUTOSAR Adaptive PlatformLogical view

27 October

2020

(Virtual) Machine / Container / Hardware

ara::exec

Execution Mgnt.

ara::com

Communication Mgnt.ara::rest

RESTful

ara::per

PersistencySO

ME

/IP

ara::crypto

Cryptography

ara::phm

Platform Health Mgnt.

ara::time

Time Synchronization

ara::log

Logging & Tracing

ara::state service

State

Management

ara::diag service

Diagnostics

User Applications

Adaptive

Application

Adaptive

Application

Adaptive

Application

ASW::XYZ

Non-PF Service

API

Func. ClusterSERVICE

Func. ClusterSERVICE

Non-PF Service

Legend

IPC

(local)

DD

S

ara::s2s service

Signal to Service

Mapping

ara::nm service

Network

Management

ara::ucm service

Update and Configuration Management

POSIX / C++ STL

Operating System

ara::core

Core Types

ara::iam

Identity Access Mgnt.

Adaptive

Application

ara::adi service

Automated Driving

Interfaces

ASW::XYZ

Non-PF Service

39 of 65AUTOSAR Introduction

AUTOSAR AP and CP Features

27 October


Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

2018 2019 2020

Release R18-10 Release R19-03 Release R19-11 Release R20-11

26 Nov 29 Mar 29 Nov 27 Mar 27 Nov

Stabilization

released planned optional

Demo Release R19-11

Agenda

27 October







Outlook

48 of 65

AUTOSAR RTE

AUTOSAR Interface

Headlight

AUTOSAR Interface

Front-Light Manager

AUTOSAR Interface

LightRequest

AUTOSAR Interface

SwitchEvent

Software Architecture – AUTOSAR Defined InterfacesUse Case ‘Front Light Management’: Exchange Type of Front Light

27 October


ECU-Hardware

StandardizedInterface

OperatingSystem

Integrator Supplier B OEM Supplier A

Sil

ico

n V

en

do

r A

Inte

gra

tor

ComplexDrivers

AUTOSARInterface

Standardized Interface

Microcontroller Abstraction

DIO CAN DriverPWM

ECU Abstraction

AUTOSARInterface

Std. InterfaceSta

nd

ard

ize

dIn

terfa

ce


Communication

Std. Interface

Std. AUTOSARInterface

Services

Std. Interface

request_light (type, mode)

request_light (type, mode)switch event (event)

Switch_event (event)

check_switch ()

set_light (type, mode)


get_keyposition()set_current (…)

set_dboard(type, mode)

50 of 65

AUTOSAR RTE

AUTOSAR Interface

Headlight

AUTOSAR Interface

Front-Light Manager

AUTOSAR Interface

LightRequest

AUTOSAR Interface

SwitchEvent

Software Architecture – AUTOSAR Defined InterfacesUse Case ‘Front Light Management’: Exchange Type of Front Light

27 October


ECU-Hardware


OperatingSystem

Integrator Supplier B OEM Supplier A

Sil

ico

n V

en

do

r A

Inte

gra

tor

ComplexDrivers

AUTOSARInterface



DIO CAN DriverPWM

ECU Abstraction

AUTOSARInterface

Std. InterfaceSta

nd

ard

ize

dIn

terfa

ce


Communication

Std. Interface


Services

Std. Interface

request_light (type, mode)

request_light (type, mode)switch event (event)

Switch_event (event)

check_switch ()



get_keyposition()set_current (…)

set_dboard(type, mode)

AUTOSAR Interface

Xenonlight

set_light(type, mode)

set_current (…)

DIO

51 of 65

AUTOSAR Interface

Xenonlight

set_current (…)


AUTOSAR Interface

Front-Light Manager

get_keyposition()


AUTOSAR Interface

Front-Light Manager

request_light(type, mode)


AUTOSAR Interface

LightRequest

AUTOSAR Interface

LightRequest

switch_event(event)

request_light

(type, mode)

AUTOSAR Int.

SwitchEventcheck_switch ()

AUTOSAR Int.

SwitchEvent

switch_event

(event)

27 October


Distribution ECUs

52 of 65

AUTOSAR Interface

Xenonlight


set_current (…)

AUTOSAR Interface

Front-Light Manager

get_keyposition()request_light(type, mode)


AUTOSAR Interface

LightRequest

switch_event(event)

request_light

(type, mode)AUTOSAR Int.

SwitchEventcheck_switch ()

switch_event

(event)

27 October


CAN Bus

ECU-Hardware

AUTOSAR RTE



ECU Abstraction

AUTOSARInterface

Std. Interface


Communication

Std. Interface

CAN Driver PWM

ECU-Hardware

AUTOSAR RTE




Services

Std. Interface

ECU Abstraction

AUTOSARInterface

Std. Interface


Communication

Std. Interface

DIO




Communication

Std. Interface

CAN Driver

ECU-Hardware

AUTOSAR RTE

CAN Driver

639_0323

AUTOSAR Interface

Xenonlight


set_current (…)

AUTOSAR Interface

Xenonlight

AUTOSAR Interface

Xenonlight


set_current (…)

AUTOSAR Interface

Front-Light Manager

get_keyposition()



AUTOSAR Interface

Front-Light Manager

AUTOSAR Interface

Front-Light Manager

get_keyposition()



AUTOSAR Interface

LightRequest

switch_event(event)

request_light

(type, mode)

AUTOSAR Interface

LightRequest

AUTOSAR Interface

LightRequest

switch_event(event)

request_light

(type, mode)

Distribution on ECUs – ‘Front-Light Management’

53 of 65

AUTOSAR Platform ApplicationContinuous improvement cycle for ADAS systems

27 October


Perception

Scene

Understanding

Mission and

Trajectory Planning

Plan Execution,

Motion Control

On Board Off Board

Sensor Fusion

ara:adi ara:com✓

Secure data

exchange on top of

DDS

SOME/IPor

REST

Labeling of

trained data

Evolution by

training

Simulation and

sign-off

54 of 65

ENGINE

START

STOP

27 October


User Applications

Vehicle

Manager

HMI

Distance

Radar

>> Run Execution Manager

…

…

…

…

ara:: exec > start { Vehicle Manager }

The operation completed successfully

ara:: exec > start { HMI }


ara:: exec > start { Distance Radar }


AUTOSAR Platform Application

27 October


HMIDistance

Radar

Vehicle

Manager

New

User Application ?

27 October


Adaptive Cruise Control

(ACC) install

User Applications

HMI Distance

Radar

Download

Vehicle

Manager

App

Store

Adaptive Cruise Control

>> Run Persistency

…

…

…

ara:: per > install new application software

from ara:: ucm service { ACC }

Ara:: per > deploy persistent data to

Key-Value Database:

> Vehicle Manager

> HMI

> Distance Radar

> ACC

ACC

ENGINE

START

STOP

27 October


User Applications

Vehicle

Manager

HMI

Distance

Radar

>> Run Execution Manager

…

…

…

ara:: exec > start { Vehicle Manager }


ara:: exec > start { HMI }


ara:: exec > start { Distance Radar }


ara:: exec > start { ACC}


ACC

27 October


HMIDistance

Radar

Vehicle

ManagerACC

ACC

Agenda

27 October







Outlook

62 of 65

Best tradeoff between commercial cooperation & compatibility between different vendors

Specification DemonstrationImplementation

AUTOSAR Adaptive Platform development approach

27 October


Gain speed:

1) Spec validation

2) Reduce room for spec interpretation

3) Training / dissemination of AP

Attracting environment for coders:

• Appealing technology (C++, Yocto, Git, …)

• Modern use case (ADAS EBA)

• Handy documentation (Wiki)

• Peer programming sessions

Identify needs & use-cases:

1) Concepts

2) Features

3) Requirements

Gain trust:

1) Advertises the progress

2) Highlights some specific features

Quality:

• TF-ARC approval

• Cross team review

• Lifecycle :

preliminary → draft → valid

Show AUTOSAR interoperability

• of classic and adaptive platforms

• but also with others

RS

Documents

SWS

Documents

Code

System

Tests

Test

Specification

Module

Tests

Ethernet

Classic

Platform

Adaptive

Platform

Others

63 of 65

Agenda

27 October







Outlook

64 of 65

27 October


Timeline to full automationAUTOSAR – a faithful ADAS companion

© BMW2019 2020 2021 2022 2023 2024 2025 20262018

Automated Driving

Level 4:

highly automated driving

Automated Driving

Level 5:

full automation

Automated Driving

Level 3:

Conditional automation

✓

R18-10

✓

R19-11 R20-11 R21-11

✓

…

R19-03, Stabilisation

R17-10

R18-03

✓ ✓

65 of 65