10th autosar open conference · extended by the functional clusters. autosar runtime for adaptive...
TRANSCRIPT
10th AUTOSAR Open Conference
AUTOSAR Nov-2017
AUTOSAR Adaptive Platform
Rinat AsmusAUTOSAR Project Leader BMW
AUTOSAR Nov-2017 2
New Challenges – One Standard.
Do AUTOSAR Core partners commit to standard use?
Is the implementation of the standard applicable?
Does AUTOSAR provide the functionality my software application requires?
AUTOSAR Nov-2017 3
Adaptive Platform characteristics.
Service Oriented Architecture
Parallel processing
FunctionalSafety (ISO26262)
Automotive Security
Flexible SoftwareConfiguration
Compatibility to existing standards
and norms
One common AUTOSAR
methodology
Based on POSIX Standards
Dynamic memory allocation
AUTOSAR Nov-2017 4
Adaptive Platform – Functional Architecture.
Machine
ARA includesPOSIX profilePSE51. Additional APIs areextended by thefunctional clusters.
AUTOSAR Runtime for Adaptive Applications (ARA)
Signal 2 Service Mapping
Network Management
Logging and Tracing
Time Synchronisation
Persistency
Cryptography REST
Execution Management
Operating System
Not part of AUTOSAR standardization.
Bootloader
Update and Configuration Management
DiagnosticsIdentity Access Management
Communication Management
Platform Health Management
Adaptive Platform Services
Adaptive Platform Foundation
AUTOSAR Nov-2017 5
Service vs. API implementation.
AUTOSAR Runtime for Adaptive Applications (ARA)
Machine
Adaptive Platform Foundation.. provides detached additional features
- implemented as C++ libraries - Communicates over inter process
communication directly
Adaptive Platform Services.. are coupled to ara middleware
implementation
- C++ code is generated through information passed by to ara::com generator
- Onboard communication is managed by ara::com DiagnosticsExecution
Management
… schedules processes and manages the machine states
… to manage software errors andreaction
AUTOSAR Nov-2017 6
AUTOSAR Runtime Environment for Adaptive Applications (ARA)
ARA COM middleware.
Machine
Service interface
Service proxy Service skeletonMiddleware
generates generates
- SoA to intra and inter machine communication- Generates Proxy/Skeleton as defined in Methodology- Supports static (preconfigured) and dynamic (during runtime)
service discovery- Specifies additional data types such as collection types or function
wrappers- Abstracts from network communication protocol layer- ARA API is designed for event-driven and polling approaches- supports a seamless integration of end2end protection
AUTOSAR Nov-2017 7
Features of Adaptive Platform Release 17-03.
• Logging and Tracing
• Service-Discovery and Service-based Communication
• Events and Methods• Language-Binding: C++• Inter-Process-Communication• Bus-Binding: SOME/IP
• Diagnostic Extract• Manifests• Methodology Extensions for
Adaptive
• C++14 Coding Guideline• E2E Communication Integrity
LOGGING / TRACING
SAFETY
• DTC Management• ISO 14229 / ISO 13400
DIAGNOSTICS
COMMUNICATION
• OS Application Interface (PSE51 & C++STL)
• Data Storage
PERSISTENCY
POSIX OS
METHODOLOGY
• Integration of Applications onto Platform
• Start and Stop of Applications
EXECUTION MANAGEMENT
R17-03
AUTOSAR Nov-2017 8
Features of Adaptive Platform Release 17-10.
R17-10
• Time Synchronization• Support of RESTful• Fields
• Methodology Extensions for Adaptive
• Service to signal modeling• Predefined Data Types
• C++14 Coding Guideline• E2E for periodic
communication
SAFETY
COMMUNICATION
METHODOLOGY
• Resource Management• Recovery action framework• Machine State handling
EXECUTION MANAGEMENT
• Crypto API• Authentication & Certificates• Key Management• Secure Communication
SECURITY
• ISO 13400 / ISO 14229 completion
• Handling of SW Clusters
DIAGNOSTICS
AUTOSAR Nov-2017 9
• Data Storage• Safe Data Storage• Persistent Data Encryption
Features of Adaptive Platform Release 18-03.
• Support of RESTful• Network Management Ethernet• Methodology Extensions for
Adaptive• Service to signal modeling
• Platform Health Management• Safety concept for AP• E2E for non periodic
communication
SAFETY
• Maintenance and Improvements
DIAGNOSTICS
COMMUNICATIONMETHODOLOGY
• Crypto API• Authentication & Certificates• Key Management• Secure Communication• Support of trusted platform
SECURITY
• Package Management• Installation routine
PERSISTENCY
• Maintenance and Improvements
LOGGING / TRACINGSW-CONFIGURATION MGNT
• Resource Management• Parallel Processing by HWA• Recovery action framework
R18-03
EXECUTION MANAGEMENT
AUTOSAR Nov-2017 10
Specification and Validation by Implementation.
The Adaptive Platform is validated through an AUTOSAR-internal implementation: The Adaptive Platform Demonstrator
This Demonstrator is available to all the partners and can be a reference to understand the underlying concepts of the Adaptive Platform.
All further development based on the Demonstrator will become the responsibility of the respective partner.
specification
AUTOSAR Nov-2017 11
Join AUTOSAR.
ValidationWP-X-VAL
SecurityWP-X-SEC
Functional SafetyWP-X-SAF
WP-A1 VFB and RTE
WP-A2COMM Stack
WP-M1Timing Analysis
WP-A4Diagnostics
WP-A5MCAL
WP-IApplicationInterfaces
WP-I-BODYBody and ComfortWP-I-ENGINEPowertrain EngineWP-I-TRSMPowertrain TransmissionWP-I-CHASSIS Chassis ControlWP-I-OCSAFEOccupant and Pedestrian Safety
WP-ASoftware
ArchitectureWP-A-LIBLibrariesWP-A-MCBDMulticore BSW Dist
WP-MMethodology and
TemplatesWP-M-METHMethodologyWP-M-GSTGeneric Structure TemplateWP-M-SWCTSoftware Component TemplateWP-M-SYSTSystem TemplateECU ConfigurationWP-M-TIMEXTiming Extensions
FT-SECSecurity
FT-UCMUpdate & ConfManagement
FT-STSystem Tests Legend:
Lead WorkPackage
Work Package
Subgroups
Feature Team
FT-ADIAutomated Driving
Interfaces
FT-PERPersistency
FT-SAFSafety
FT-CMCommunication
Management
FT-EMO Execution
Management
FT-DIAAdaptive
Diagnostics
FT-MMMethodology &
Manifests
FT-DIDemonstrator
Integration
Project Leader Team
New in 2018
10th AUTOSAR Open Conference
Thank you for your attention!
- AUTOSAR - page 12
Hufelandstr. 180937 Munich, GermanyTel: +49-89-382-65843Mail: [email protected]
Rinat Asmus