07 adaptive autosar ?c extending the scope of autosar ... · v0.1 | 2017-08-04 vector congress...

V0.1 | 2017-08-04

Vector Congress 2017, September 6th – 7th, Shanghai China

Adaptive AUTOSAR –Extending the Scope of AUTOSAR-based Embedded Software

2

Use Cases for Adaptive AUTOSAR

Introduction

� 2D/3D accel. support in POSIX systems

� Video Codecs, Streaming support, multi-media library, etc…

Infotainment

� Image- and preprocessing of Camera/Radar/LIDAR

� Sensor Fusion and Machine Learning

Highly Automated Driving

Connectivity

� “App-Store” for automotive applications

� Installation and update over the air

Dynamic Software Platform

� Car-2-X (LTE, WiFi, GPS, etc.)

� Multimedia (USB, SD-Card, NFC, etc.)

source: fotolia

3

� New use cases bring new requirements

� Incremental Deployment> Allow download of individual applications

> Allow dynamic initialization and scheduling of applications

> Allow dynamic initialization of service needs (e.g. communication)

� High performance computing> Support of faster CPU architectures

(e.g. 64 Bit ARM and Intel architectures)

> Support of hardware accelerators (e.g. GPUs)

> Efficient multicore exploitation

Requirements for Adaptive AUTOSAR

Introduction

Foundation(FO)

common requirements

Classic Platform(CP)

Adaptive Platform

(AP)

� Efficient software development> Object-orientation and use of dynamic memory

> Integration of existing software (e.g. GUI-toolkits)

AUTOSAR decided to rearrange and extend the standard

� Both standards must be compatible with each other

� Each standard targets different ECU types

4

2

Classic AUTOSAR

Adaptive AUTOSAR

1

3 Conclusion

5

� We’ve come a long way with AUTOSAR classic

� It supported many use cases right from the start> Communication (CAN, LIN, FlexRay)

> NV memory

> diagnostics

> network management

Introduction

Classic AUTOSAR

� Over time several features were added

6

SOAD



> NV memory

> diagnostics


Ethernet Support

Classic AUTOSAR

ETHIF

ETHSM

TCPIP

IPv4, ARP, ICMPv4IPv6, NDP, ICMPv6

UDP, TCP, DHCPv4, DHCPv6

COMMSD

BSWM

LDCOMCOM

PDUR

UDPNM

TLS

RTE

SWCSWC SWC

SOMEIPXF

� Over time several features were added> Ethernet

ETHTRCVETHETHSWT

Hardware

7

Hardware



> NV memory

> diagnostics


Multicore Support

Classic AUTOSAR

MIC

RO

SAR D

IAG

Core 1 Core 2

MICROS. SYS X

CP

MIC

RO

SAR M

EM

MIC

RO

SAR C

OM

MU

NIC

ATIO

N

MIC

RO

SAR I

O

Com

ple

x D

rivers

MICROSAR CALMICROSAR

EXTCore Test

ECU State Manager

Satellite

Com

ple

x D

rivers

Watchdog Manager

Satellite

ECU State Manager

Watchdog Manager

Multicore RTE

SWCSWC SWC

MIC

RO

SAR O

SM

ulti-

Core

SWC


> Multicore

8



> NV memory

> diagnostics


Safety Features

Classic AUTOSAR

Safe RTE

SWCSWC c SWC SWC

SafeOS

SafeBSW

Safe

WD

G

MCAL

Hardware

E2E

ASIL QM


> Multicore

> Safety

9

RTE

SWCSWC SWC



> NV memory

> diagnostics


Security Features

Classic AUTOSAR

Hardware

CRYDRV(HSM)

CRYDRV(SHE)

CRYDRV(SW)

CRYIF

CSM

SHE HSM

Channel SH

E

Channel H

W-R

SA

CSM queuing &

prioritization

AES AES RSA


> Multicore

> Safety

> Security

10



> NV memory

> diagnostics


POSIX Support (Vector-proprietary)

Classic AUTOSAR


> Multicore

> Safety

> Security

> POSIX (Vector-proprietary)

Ethernet CAN

Guest OS

RTE

SWCSWC SWC

POSIX OS

PDUR

Diagnostics COM

MIC

RO

SAR M

EM

MIC

RO

SAR S

YS

CAN SocketBSD Socket

POSIX Process

Hardware

11

� Feature-rich

� Stable

� Real-time capable

� Scalable

� Resource efficient

� Still improving

We’ve ended up with a platform that is



> NV memory

> diagnostics


Conclusion

Classic AUTOSAR


> Multicore

> Safety

> Security

> POSIX (Vector-proprietary)

> V2G (Vector-proprietary)

> Time synchronization

> …

12

2

Classic AUTOSAR

Adaptive AUTOSAR

1

3 Conclusion

13

Architecture

Adaptive AUTOSAR

Applications

Platform

POSIX OS

SCM Service

App1

POSIX Process

PersistencyEM (Execution

Manager)

ara::com ara::em ara::pers


Diagnostic Service


Middlewareara::com SOMEIPd

Service Discovery

App2

POSIX Process


ara::em

…

BSD Socket BSD Socket for DoIP

14

Applications

Adaptive AUTOSAR

Manifest

InstanceConfiguration

� Application

> Multi-threaded

> Execution states

> Manifest contains platform related information (recovery action, dependencies to services or libraries)

> Instance config contains application specific static information (variant, options, …)

� Interfaces

> ara::com for communication with adaptive services (basic services and user applications)

> PSE51 is the usable OS API subset

> The Adaptive AUTOSAR Foundation clusters (Execution Management, Persistency, etc.) are available via direct APIs

App1

POSIX Process

INIT:

RUN:

SHUTDOWN:

Thre

ad

Thre

ad

Thre

ad

Adaptive AUTOSAR Services

Adaptive AUTOSAR

Foundation

ara::com Direct APIPSE51

C++ Stdlib

POSIX OS

15

Overview ara::com

Adaptive AUTOSAR

� Service-oriented communication

� Location-transparent

� Supports multiple communication bindings

� AUTOSAR model defines available bindings for each service provider and consumer

� Explicit support for optimized shared memory implementations Services

APP 1 APP 2

ara::com

� Applications connected at runtime (Service Discovery)

� Find service instances dynamically without hardwiring in model

� Connection between proxies and skeletons can be recovered

� Real-time support: Developers’ choice of polling or event-driven processing of communication

16

Application CodeService Description (ARXML)

Tools and Workflow

Adaptive AUTOSAR

libara

libsomeip

Logic

SOME/IP Config

AppSWCTypes

Port

Auth

oring T

ool

Soft

ware

Configura

tion M

anagem

ent

ServiceInterfaceServiceInterfaceServiceInterface

Vehicle

SOMEIPd

ComServer

Diag

EM

Installed APP

Application Manifest (JSON)

BIN

InstanceManifest(s)

(JSON)

Installed APP

Application Manifest (JSON)

BIN

Instance Manifest(s)

(JSON)

POSIX IPC

BSD Sock

Deploy Package

/opt/myApp/

Application Manifest

./etc/MANIFEST.arxml

BIN

./bin/myApp

Instance Manifest(s)

./etc/instance1.arxml

./etc/instance2.arxml

Genera

tors

PortPort

Static

Proxies / Skeletons

SOME/IP Serializer

E2ESerializer

POSIX IPC

Generated

Com

piler

17

Hypervisor combines Safety and Linux

Adaptive AUTOSAR

SafePOSIX(e.g. PikeOS)

Linux

Hypervisor (e.g. PikeOS)

Barrier: Safe and Secure

QM Application

QM Adaptive AUTOSAR

Safe Application

Safe Adaptive AUTOSAR

µController

18

2

Classic AUTOSAR

Adaptive AUTOSAR

1

3 Conclusion

19

AUTOSAR Classic Platform - CP

Technical Comparison of Both Standards

Conclusion

AUTOSAR Adaptive Platform - AP

Real Time Requirements

Computing Power

Safety Critical

� Executed in place (ROM)

� Developed in C

� Whole stack compiled and linked in one piece

� All applications share one address space (MPU-based)

� All modules completely specified

� Focus on signal-oriented communication (AUTOSAR COM)

� Loaded at startup (RAM)

� Developed in C++

� Software components as loadable POSIX processes

� Each process has its own address space (MMU-based)

� Less modules, only APIs specified

� Focus on service oriented communication (SOME/IP)

20

Powertrain / Chassis

Central Computing

Cluster

A Possible E/E-Architecture

Conclusion

BodyInfotainmentADAS & Safety

EMS Radar

Camera

Camera

Connectivity

ESP

Airbag

Smart Charging

3G/LTEWiFiCar2X

CAN | LIN | Ethernet

Switch Switch

Connectivity Control

Off-BoardTester

Switch

Switch

Classic Platform(CP)

Adaptive Platform(AP)

21

Conclusion

Conclusion

� The new Adaptive Platform complements

the existing Classic Platform

� The Classic Platform will host deep

embedded functions

� The Adaptive Platform will host resource

intensive, high-order functions

� Vector will continue to contribute to AUTOSAR

and provide implementations and tools for

both Classic and Adaptive AUTOSAR

� For more information:

� https://vector.com

� https://www.youtube.com/user/vectorchannel

� Contact your local sales agent for

> Evaluation Bundle, Prototype, Training

22 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2017-08-04

For more information about Vectorand our products please visit

www.vector.com

Author:Dr. Bastian ZimmerVector Germany

07 adaptive autosar ?c extending the scope of autosar ... · v0.1 | 2017-08-04 vector congress...

Documents