10 th AUTOSAR Open Conference

Transcription

1 10 th AUTOSAR Open Conference Dr. Günther Heling Vector Informatik AUTOSAR Adaptive Platform Now it s Time to get on Board AUTOSAR Nov-2017

2 Introduction At the first glance Adaptive and Classic don t have too much in common A I A D P T V E C L S S C A second glance reveals even more differences: Classic harmonize terminology, functions, and interfaces optimize development methodology Adaptive utilize existing IT methods and solutions connect vehicles to the internet Nevertheless: it s worth to have a look at Classic 2

3 Adaptive now it s time to get on board 1 What can we learn from Classic? 2 Where to use Adaptive? 3 How to benefit best? 3

4 1. What can we learn from Classic? AUTOSAR grows continuously but full exploitation takes a while 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% non AUTOSAR BSW AUTOSAR Classic BSW 63% 0% % 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% AUTOSAR Share Europe North America Asia % Source: Vector s evaluation based on number of projects

5 1. What can we learn from Classic? Development methods change slower than technology Usage of the AUTOSAR methodology can be derived from usage of RTE 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% RTE Share of AUTOSAR Classic Projects 0% %... and from usage of ARXML System Description: 1/3 of our OEM programs use ARXLM To benefit from a new technology it takes 1. a good reason, 2. a good opportunity and 3. the will to change 5 Source: Vector s evaluation based on number of projects

6 1. What can we learn from Classic? AUTOSAR Classic - many variants for many OEMs 6 Program AUTOSAR version Configuration Bus System Legacy LDF + DBC + Fibex CAN, LIN, FlexRay AUTOSAR SD CAN, LIN, FlexRay x Legacy LDF + DBC CAN, LIN x Legacy Fibex CAN, LIN, FlexRay x Legacy LDF + DBC CAN, LIN 6 3.x Legacy LDF, DBC + Fibex CAN, LIN, FlexRay 7 3.x Legacy LDF, Fibex CAN, LIN, FlexRay 8 3.X Legacy LDF + DBC CAN, LIN 9 3.X Legacy LDF + DBC CAN, LIN, J Legacy DBC CAN, LIN success requires adaptation to specific needs RFCs AUTOSAR SD, Fibex CAN, LIN, FlexRay, Eth RFCs Legacy LDF + DBC CAN, LIN RFCs / AUTOSAR SD CAN, LIN, FlexRay, Eth RFCs / AUTOSAR SD CAN, LIN, Eth , (Eth) AUTOSAR SD CAN, LIN, Eth SD CAN, CAN-FD, LIN, FlexRay, Eth AUTOSAR SD + DEXT CAN, LIN, FlexRay, Eth AUTOSAR SD CAN, LIN Legacy LDF + DBC CAN, LIN, Eth, J features AUTOSAR SD + DEXT CAN, CAN-FD, FlexRay, Eth, LIN features AUTOSAR SD + DEXT CAN, CAN-FD, FlexRay, Eth x Legacy LDF + DBC CAN, LIN, Eth 23 4.X Legacy LDF + DBC CAN, LIN 24 4.X Legacy LDF + DBC CAN, LIN, Eth 25 4.X Legacy LDF + DBC CAN, LIN 26 4.X Legacy LDF + DBC CAN, LIN 27 4.x Legacy LDF + DBC, ARXML CAN, LIN

7 1. What can we learn from Classic? AUTOSAR Classic many versions with growing functionality Specification: success requires extension of functionality Changes in Ethernet - traffic shaping - queue optimization - SOMEIP-TP Security - new crypto interfaces - SecOC freshness handling - secured TP/diagnostics V2X - introduced Diagnostics - DEXT: J1939, OBD, FIM - DEM: multiclient - virtual ECUs 7 Implementation: AUTOSAR 3 AUTOSAR 4 Number of BSW Modules Lines of Code 100% 271%

8 1. What can we learn from Classic? What else can we learn? keep! - use the power of the AUTOSAR community - support automotive specifics diagnostics; workflows - benefit from competition in implementation improve! - one solution for one problem - use the complete methodology incl. integration to Classic - be open for new business models drop! - specification of all details - focus on minimum footprint 8

9 Adaptive now it s time to get on board 1 What can we learn from Classic? 2 Where to use Adaptive? 3 How to benefit best? 9

10 2. Where to use Adaptive? Automotive goes IT Automotive IT AUTOSAR Adaptive started 2015 AUTOSAR first release of AUTOSAR Classic REST published 1995 JAVA published first SOP with CAN first WWW browser CAN published Ethernet becomes ISO standard 10

11 2. Where to use Adaptive? Adaptive best of two worlds Cloud / Backend support of high performance processors high bandwidth service based architectures open source dynamic and updatable internet Embedded Systems AUTOSAR Classic safe secure embedded integration and debugging automotive supply chain automotive communication protocols automotive diagnostics 11

12 2. Where to use Adaptive? Adaptive best of two worlds Cloud / Backend system and mobility strategies deep learning support Adaptive of high performance AUTOSARprocessors high bandwidth service based architectures open source dynamic and updatable internet On board HP Computing multipurpose computing servers connectivity, gateways, HMI automated driving embedded integration and debugging AUTOSAR Adaptive safe automotive supply chain secure Embedded Systems automotive communication protocols embedded integration and debugging intelligent sensors and actuators automotive diagnostics basic functions automotive supply chain fallback computing automotive communication protocols AUTOSAR Classic safe secure automotive diagnostics 12

13 2. Where to use Adaptive? Adaptive best of two worlds Cloud / Backend system and mobility strategies deep learning On board HP Computing multipurpose computing servers connectivity, gateways, HMI automated driving AUTOSAR Adaptive Embedded Systems intelligent sensors and actuators basic functions fallback computing Adaptive AUTOSAR support of high performance processors high bandwidth service based architectures open source dynamic and updatable internet safe secure embedded integration and debugging automotive supply chain automotive communication protocols automotive diagnostics AUTOSAR Classic 13

14 2. Where to use Adaptive? There are more reasons to use Adaptive! Let s have a look at the development process: Classic AUTOSAR AUTOSAR Adaptive static dynamic monolithic / top-down modular / parallel model-based model-based and software-based configuration at compile time configuration at runtime maximal efficiency quick local changes not supported maximal flexibility quick local changes well supported Good software design is more important than small footprint good fit to AUTOSAR Adaptive Software is developed by computer scientist good fit to AUTOSAR Adaptive AUTOSAR Adaptive may be the right choice even for smaller ECUs 14

15 2. Where to use Adaptive? There are more reasons to use Adaptive! Seamless link between on-board and off-board computing Parts of a safety related function can be calculated off-board Flexible mapping of functions on-board and off-board even at runtime vehicle becomes a part of IoT What about using Adaptive for non-automotive applications? 15

16 Adaptive now it s time to get on board 1 What can we learn from Classic? 2 Where to use Adaptive? 3 How to benefit best? 16

17 3. What should you do to benefit best? Now it s time to get on board AR Release R17-03: > Execution Management > Communication/ Middleware > DLT > Diagnostics > Persistency AR Release R17-10: > Platform Health Management > RESTful Services > Signal based communication > Security Features > Time Synchronization > E2E Protection (Draft) > Package Management (Draft) AR Release R18-03: > Container Support > Package Management > E2E Protection > SW-Lockstep > Crypto Hardware > Network Management AR Release R18-10: > tbd There are still parts left to specify but core features are specified 1. Implementations let s define one have powerful not yet standard reached production level but Contribute projects can to already the specification be started 2. gain experience early Start evaluation projects now 3. combination of automotive embedded & IT is challenging Care for skilled staff 17

18 10 th AUTOSAR Open Conference Thank you for your attention! Dr. Günther Heling Vector Informatik GmbH Ingersheimer Str Stuttgart Germany - AUTOSAR page 18