AUTOSAR proofs to be THE automotive software platform for intelligent mobility

Transcription

1 AUTOSAR proofs to be THE automotive software platform for intelligent mobility Dr.-Ing. Thomas Scharnhorst AUTOSAR Spokesperson 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 ELIV, Bonn Germany October 18 th -19 th 2017

2 Overview Introduction Overview and achievements New challenges and use cases The Adaptive Platform Overview 1 st release of the Adaptive Platform Roadmap New cooperation model Agile development Collaboration with other standardization bodies Summary 2

3 E/E innovations in vehicle development are increasing 90% of all innovations Linked Networks All major innovations are driven by E/E Mechanics Electronic Support Infotainment Vehicles are connected to the back-end

4 AUTOSAR Core Partners and Partners (June 2017) 9 Core Partners 29 Development Partners 44 Premium Partners 91 Associate Partners 19 Attendees General OEM Generic Tier 1 Standard Software Tools and Services Semiconductors 4

5 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 a OEM b Platform b.1 Platform b.2 Platform b.n Exchangeability between suppliers OEM c solutions Platform a.1 Platform a.2 Platform a.n Exchangeability between manufacturers applications OEM f Platform f.1 Platform f.2 Platform f.n Supplier A Chassis Safety Body/ Comfort OEM e Supplier C Platform e.1 Platform e.2 Platform e.n Supplier B Chassis Safety Telematics Body/Comfort Powertrain Telematics Platform c.1 Platform c.2 Platform c.n OEM d Platform d.1 Platform d.2 Platform d.n Exchangeability between vehicle platforms 5

6 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 Software AUTOSAR Application Software Standardized Methodology Customer needs Adaptive Cruise Control Lane Departure Warning Advanced Front Lighting System Hardware Hardware Hardware Hardware HW-specific (ECUs) Using standards Communication Stack OSEK Diagnostics CAN, FlexRay 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

7 Overview Introduction Overview and achievements New challenges and use cases The Adaptive Platform Overview 1 st release of the Adaptive Platform Roadmap New cooperation model Agile development Collaboration with other standardization bodies Summary 7

8 Motivation Main drivers to develop the Adaptive Platform Highly automated driving Car-2-X applications Open and secure access to vehicle Increased Connectivity 8

9 Selected main drivers for new automotive software systems (1/4) Highly automated driving will be on the road. Use cases 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 9

10 Selected main drivers for new automotive software systems (2/4) Car-2-X applications will require the interaction of vehicles and off-board systems. Use cases Secure on-board communication Support of cross domain computing platforms Smartphone integration Integration of non-autosar systems 10

11 Selected main drivers for new automotive software systems (3/4) Open and secure access will require dedicated means for security Use cases 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 11

12 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 ECU4 ECU2 SW-C3 SW-C4 SW-C5 ECU3 SW-C6 Server Statically deployed application Dynamically deployed application Off Board application Use cases Consideration of non-autosar systems within methodology Dynamic deployment of software components Interaction with non-autosar and off-board systems 12

13 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

14 Overview Introduction Overview and achievements New challenges and use cases The Adaptive Platform Overview 1 st release of the Adaptive Platform Roadmap New cooperation model Agile development Collaboration with other standardization bodies Summary 14

15 AUTOSAR Adaptive Platform emerging from deeply embedded systems Application framework Support for run-time configuration Service-oriented communication Partial update SHFrontLeft: SeatHeatingContr olanddrivers PM: Power 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) Ethernet Planning of dynamic communication Reference architecture Reuse existing (non-automotive) standards Ease software development Support automotive use-cases and protocols Reference Implementation and many more 15

16 Architectural Overview Functional Clusters AUTOSAR Runtime for Adaptive Application (ARA) API API API Service Service Service Operating system (*) Time API Execution API Software Configuration Security Diagnostics Adaptive Platform Services Bootloader Platform Health Persistency API API API Logging and Tracing Hardware Acceleration Communications Adaptive Platform Foundation (Virtual) Machine / Hardware AUTOSAR Runtime for Adaptive Applications = Σ of all Functional Cluster APIs / Services API Service Functional Cluster Programming language specific API for a Functional Cluster as specified in SWS Service Interface of a Functional Cluster. API is generated according to ara::com specification Behavioral specification of Functional Cluster (*) POSIX OS, not separately standardized _9020

17 Address space virtualization Each application lives in its own protected Each application lives in its own address space address space Access to platform functionality via Application 1 Application 2 libraries API(libc) API API API(libc) API API Communication via impl. spec. IPC Time Execution Service Software Configuration Service Security Service Diagnostics Operating System (*) Persistency Adaptive AUTOSAR Services Bootloader Platform Health Logging and Tracing Adaptive AUTOSAR Foundation (Virtual) Machine / Hardware Hardware Acceleration Communication (*) POSIX OS, not separately standardized 17

18 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 Middleware Communication Middleware Communication 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 Service-oriented Ethernet communication (2/2) Application Service Consumer Service Implementation Service Interface Definition API(libc) Communication API Communication Proxy Skeleton Provided Interface Events Methods Fields Operating system (*) SOME/IP-Serialization E2E Protection SOME/IP Bootloader Adaptive AUTOSAR Foundation SOME/IP Service Discovery (Virtual) Machine / Hardware (*) POSIX OS, not separately standardized 19

20 Execution model Classic Platform vs. Adaptive Platform ECU ECU SWC Application Software Component Description specifies Runnables Manifest Callbacks Threads executes creates creates Influences generated code RTE executes Communication void main() executes Execution configures 20

21 1 st Release finalized March 2017 AUTOSAR Runtime for Adaptive Application API Operating System (*) API Execution API Persistency Adaptive AUTOSAR Services Service Service Service Software Security Configuration Diagnostics Bootloader API API API API Platform Health Logging and Tracing Hardware Acceleration Communications Adaptive AUTOSAR Foundation (Virtual) Machine / Hardware (*) POSIX OS, not separately standardized The Adaptive Platform is developed iteratively the functionality grows with each release 21

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

23 The Challenge: Integration of Different Platforms Classic Application SW-C Classic Application SW-C Adaptive Application Adaptive Application Non- AUTOSAR Application Non- AUTOSAR Application Runtime Environment Service Layer ECU Abstraction Layer C D Runtime Environment Service Layer ECU Abstraction Layer C D Adaptive AUTOSAR API (ARA) Adaptive AUTOSAR Services Microcontroller Abstraction Layer Microcontroller AUTOSAR Classic Platform Microcontroller Abstraction Layer Microcontroller AUTOSAR Classic Platform AUTOSAR Foundation (Virtual) Machine / Hardware AUTOSAR Adaptive Platform Non-AUTOSAR Basic Software Non-AUTOSAR Offboard System e.g. SOME/IP Software Abstraction Common Bus Interface Specification 23

24 Overview Introduction Overview and achievements New challenges and use cases The Adaptive Platform Overview 1 st release of the Adaptive Platform Roadmap New cooperation model Agile development Collaboration with other standardization bodies Summary 24

25 The first release already provides specifications and software Development in AUTOSAR Feature Teams validate AUTOSAR Specifications AUTOSAR Software Implementations Licensing for exploitation improve Licensing for exploitation Exploitation of released Specifications and exemplary Software Implementation by AUTOSAR partners 25

26 Organization of development of the Adaptive Platform Work mode and contributions Joint expert group meeting Run 3 4 months Joint expert group meeting Release approx. twice a year Joint expert group meeting Sprint planning meetings per feature team defined by FBO Sprint 2-5 Days Continuous development according to Scrum 4 Weeks Feature Backlog Sprint Backlog Scrum Meetings Deliverable Increment refinement sprint planning sprint monitoring sprint review sprint retrospective 26

27 Releases and revisions of AUTOSAR 2016 Q1 Q2 Q3 Q4 Q Q2 Q3 Q4 Q Q2 Q3 Q4 Classic Platform R4.3.0 R4.3.1 R4.4.0 Foundation Release R R R R 1.X.Y Synchronized Release Adaptive Platform Release R R R R R Development Evolution Maintenance Issue Notice 27

28 Overview Introduction Overview and achievements New challenges and use cases The Adaptive Platform Overview 1 st release of the Adaptive Platform Roadmap New cooperation model Agile development Collaboration with other standardization bodies Summary 28

29 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 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 30

30 Summary Achievements Established a worldwide software standard focusing on automotive applications Classic Platform is massively used in series production AUTOSAR Standards Already launched: AUTOSAR Classic Platform, AUTOSAR Foundation and AUTOSAR Acceptance Tests First release of AUTOSAR Adaptive Platform 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. 31

31 More information available online More information about AUTOSAR: Become a partner and get exploitation rights for the AUTOSAR standard admin@autosar.org For information only (see disclaimer) Published Releases 32