vector congress 2016: the autosar adaptive platform for ... · pdf filethe autosar adaptive...
TRANSCRIPT
The AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
Simon Fürst, AUTOSAR Steering Committee 8th Vector Congress 29-Nov-2016, Alte Stuttgarter Reithalle, Stuttgart, Germany
Overview
Game changers New challenges and use-cases New functions
Future of AUTOSAR – AUTOSAR Adaptive Platform Architecture Key functions
Framework of the AUTOSAR Adaptive Platform Novelties from 1 January 2017 onwards Timeline
Summary
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 3
Starting Point: selected main drivers
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 4
Main drivers for new automotive software systems have been determined.
Highly automated driving Car-2-X applications
Vehicle in the cloud Increased connectivity
Influence by new players
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 5
Open to cooperate with others
Define standardized
interfaces to …
Cooperation with other standards
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 6
Open to connect with others
Identifying / monitoring open source projects
Overview
Game changers New challenges and use-cases New functions
Future of AUTOSAR – AUTOSAR Adaptive Platform Architecture Key functions
Framework of the AUTOSAR Adaptive Platform Novelties from 1 January 2017 onwards Timeline
Summary
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 7
Another platform for different applications
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 8
Safety relevance
Real time requirements
Computing power
Classic Platform
Microcontroller
Runtime Environment
CD
Microcontroller Abstraction Layer
Service Layer
ECU Abstraction Layer
Infotainment Platform supporting „Planned dynamics“
Security
AUTOSAR Classic Platform
AUTOSAR Adaptive Platform
non - AUTOSAR Basic Platform
Application SW - C
Adaptive Application
SW - C
SW - C Non AR
RTE
Adaptive Application
SW - C
BUS
AUTOSAR Classic Platform
Application SW - C
RTE non - AUTOSAR Offboard System
SW - C Non AR
SOME / IP
A new AUTOSAR standard: The AUTOSAR Adaptive Platform
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 9
The new platform will close the gap. It will support adaptive deployment, complex micro-controllers and interaction with non AUTOSAR systems.
Common Bus Interface Specification
SW system
description
ECU description
Classic Platform vs. Adaptive Platform Technical characteristics
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 10
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-based communication (CAN, FlexRay)
Service-oriented communication
Fixed task configuration Support of multiple (dynamic) scheduling strategies
AUTOSAR runtime for adaptive applications - functional clusters
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 11
AUTOSAR Runtime for Adaptive Applications
Adaptive AUTOSAR Foundation
(Virtual) Machine / Hardware
Adaptive AUTOSAR Services
Software Configuration Management
Service
Security Management
Service
Diagnostics
Service
Bootloader
Operating system
API
Execution Management
API
Persistency
API
Platform Health
Management
API
Logging and Tracing
API
Hardware Acceleration
API Communicati
on Management
API
Time Management
API
Application
Language specific APIs as part of ARA
Services provided via Communication ARA API
APIs and services exposed to applications by functional clusters
Application Application Application Application
API Programming language specific API for a Functional Cluster as specified in SWS
Software Configuration Management
Behavioral specification of Functional Cluster
Service Service Interface of a Functional Cluster. API is generated according to ara::com specification
(Virtual) Machine / Hardware
Communications
Adaptive Platform – technical architecture (communication)
29-Nov-2016 12
Adaptive Application
Ethernet Driver
TCP/IP
SOME/IP Transport
IPC Transport
IPC
Dispatching and Discovery
normative interface informative interface private interface
Public Interface Part of the adaptive AUTOSAR API and specified in the SWS. Protected Interface Interaction between functional clusters. Informative. Private Interface Interaction between elements within a functional cluster. Informative.
Technical architecture Shows standardized and non-standardized
interfaces of the Adaptive platform Give informative example for SW
architecture of a platform implementation
C++11 Language Binding
ARA API
network
Execution Management
API
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
Adaptive AUTOSAR Foundation
Adaptive AUTOSAR Services
Intrinsic safety - freedom from interference
29-Nov-2016 13
(Virtual) Machine / Hardware
Application 1
API(libc) API API
Software Configuration Management
Service
Security Management
Service
Diagnostics
Service
Bootloader
Operating system
Execution Management
Persistency
Platform Health
Management
Logging and Tracing
Hardware Acceleration
Communication Management
Time Management
Application 2 Access to platform functionality via libraries API(libc) API API
Communication via implementation specific IPC
Each application lives in its own protected address space Each application lives in its own address space
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
ara::com – Service-oriented communication
29-Nov-2016 14
Adaptive AUTOSAR Foundation
(Virtual) Machine / Hardware
Application
API(libc) Communication API
Bootloader
Operating system
Communication Management
Proxy Skeleton
Provided Interface Events Methods Files
Service Implementation
Service Consumer
SOME/IP
SOME/IP Service Discovery
SOME/IP-Serialization E2E Protection
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
Service Interface Definition
Service-oriented communication Dynamic establishing of communication path
15 29-Nov-2016 AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
ECU n
...
Ethernet
ECU II ECU I
Communication Management Middleware
Communication Management Middleware
Communication Managment Middleware
Application n Application 3 Application 2 Application 1
Skeleton Skeleton Skeleton P1 P2 P3
ServiceFind()
ServiceDiscovery finds all local and remote ServiceInstances in the System. Available ServiceInstances are represented by Proxies (P1 … P3) to the Application. Application can choose which ServiceInstance(s) to use.
ECU ECU
Execution model
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 16
SWC
RTE
Runnables
Software Component Description
specifies
Influences generated
code
executes
Application
Communication Management
Callbacks Manifest
configures
executes
Threads
void main()
executes
creates
Execution Management
Classic Platform Adaptive Platform vs.
creates
Architecture – machine level
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 17
Mem IntC I/O Core Core
MCU MCU MCU …
ECU
Adaptive AUTOSAR Classic AUTOSAR
Core Mem
Hypervisor
Core Mem IntC I/O Core Mem IntC
Physical Machine
IntC I/O Core
Adaptive AUTOSAR
Mem Physical Machine
Virtual Machines
Software Platform
Instances
One Machine is generally occupied exclusively by one Software Platform Instance
MCU …
ECU may contain multiple MCUs
Overview
Game changers New challenges and use-cases New functions
Future of AUTOSAR – AUTOSAR Adaptive Platform Architecture Key functions
Framework of the AUTOSAR Adaptive Platform Novelties from 1 January 2017 onwards Timeline
Summary
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 18
What are the mayor novelties from 1 January 2017 onwards?
AUTOSAR Software Implementation • Joint development of
exemplary software
Collaboration • Collaboration and joint
use of specifications with third parties by sublicensing
Derived Applications • Revised definition
29-Nov-2016 AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 19
New from 1 January 2017 onwards: Joint development of exemplary software implementations for the AUTOSAR Adaptive Platform
Development in AUTOSAR Work Packages
AUTOSAR Specifications AUTOSAR Software Implementations
Exploitation of released Specifications and exemplary Software Implementation by AUTOSAR partners
validate
improve
Lice
nsin
g fo
r ex
ploi
tatio
n
Lice
nsin
g fo
r ex
ploi
tatio
n
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 20
Standardization process and specification validation
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 21
Specifications will be validated in parallel with the standardization.
Standardization
Feedback Agile
development
Prototyping
Input
Feedback Feedback
Operating system definition based on POSIX Middleware technologies for the implementation of service
oriented communication, e.g. SOME/IP Definition of execution model(s) to support the different use
cases of access freedom, e.g. full access, sandboxing Use of package format and managers for application
deployment
Ongoing feasibility studies
Work mode and how-to contribute
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 22
Joint expert group meeting
Joint expert group meeting
Joint expert group meeting
Sprint planning meetings per feature team defined by FBO
Continuous development according to Scrum
Run 3 – 4 months
Sprint 4 weeks*
Active members
Active and passive members
Timeline
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 23
Saf
ety
Sec
urity
C
omm
unic
atio
n B
ase
syst
em
R17-03 R17-10 R18-03 R18-10
Ethernet
Diagnostics
Operating System
Persistent storage of data
E2E Protection
DLT
Execution Management
HW Acceleration (OpenCL)
Software installation
Platform Health Mgmt.
File Encryption
Signal based comm.
CAN support
User management
Resource management
New from 1 January 2017 onwards: Definition of Derived Applications
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 24
Derived applications Ultra-hazardous activities
Use-cases that are neither an Automotive Application nor in a field of use of products or services that falls into the categories of ultra-hazardous activities.
Aerospace and aviation, nuclear power, chemical and/ or biological reactors, petrochemical, or military (except for military marine transportation vessels).
Use-cases related to engine powered, land-based, non-railed vehicles, such vehicles intended for primary transportation purposes.
Automotive applications
NO
Original target Extended Excluded
Overview
Game changers New challenges and use-cases New functions
Future of AUTOSAR – AUTOSAR Adaptive Platform Architecture Key functions
Framework of the AUTOSAR Adaptive Platform Novelties from 1 January 2017 onwards Timeline
Summary
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 25
Summary
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 26
Achievements
Game changers
Established a worldwide software standard focusing on automotive applications
Classic Platform is massively used in series production
New use-cases such as autonomous driving, Car-2-X applications, vehicle in the cloud etc.
New players in the market Cooperation with other standardization bodies required
Future of AUTOSAR
AUTOSAR Adaptive Platform designed to meet new use cases
Development of exemplary software New Development Agreement to form the legal baseline
AUTOSAR will continue to be THE creator of automotive software standards.
More information available online
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 27
More information about AUTOSAR:
http://www.autosar.org
Become a partner and get exploitation rights for the AUTOSAR standards
For information only (see disclaimer)
Published Releases
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles
AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles 29-Nov-2016 28
Thank you for your attention!
Do you have questions?