AUTOSAR Introduction

July 2018
AUTOSAR Web Team

© AUTOSAR
Topics

AUTOSAR Introduction

Approaches and standards

Developing the Adaptive Platform

© AUTOSAR
Achievements, plans, organization

Introduction July 18 2
Topics

AUTOSAR Introduction

Approaches and standards

Developing the Adaptive Platform

© AUTOSAR
Achievements, plans, organization

Introduction July 18 3
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.
Exchangeability
between suppliers’
Platform solutions Platform
a.1, a.2, a.n b.1, b.2, b.n

Supplier A Supplier B Supplier C

Platform • Chassis • Chassis • Body/Comfort Platform
f.1, f.2, f.n • Safety • Safety • Powertrain c.1, c.2, c.n
• Body/Comfort • Telematics • Telematics

Exchangeability

© AUTOSAR
Exchangeability between vehicle
between manufacturers’ Platform Platform
platforms
applications e.1, e.2, e.n d.1, d.2, d.n

Introduction July 18 4
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 AUTOSAR • Hardware and software –

widely independent of each
other.

Standardized
Methodology
Software Application • Development can be de-
Software coupled by horizontal layers,
reducing development time
and costs.

HW-specific
(ECUs)

© AUTOSAR
• Reuse of software
Hardware Hardware enhances quality and
Hardware
Hardware efficiency

Introduction July 18 5
Exploitation of the standard provides significant benefits

• Establish development distribution among

suppliers
• Compete on innovative functions with increased
OEM design flexibility
• Simplify software and system integration
• Reduce overall software development costs
Supplier

Tool provider
An industry
standard is

© AUTOSAR
New market
established. entrant

Introduction July 18 6
Exploitation of the standard provides significant benefits

OEM
• Enable more efficent variant handling
• Reuse software modules across OEMs
Supplier
• Increase efficiency of application development
• Invent new business models
Tool provider
An industry
standard is

© AUTOSAR
New market
established. entrant

Introduction July 18 7
Exploitation of the standard provides significant benefits

OEM

Supplier

• Interface with development processes

Tool provider
• Embed tools into an overall tool environment
An industry
standard is

© AUTOSAR
New market
established. entrant

Introduction July 18 8
Exploitation of the standard provides significant benefits

OEM

Supplier

Tool provider
An industry
standard is • Enable new business models by means of

© AUTOSAR
New market standardized interfaces
established. entrant
• Easily understand how automotive software is
developed

Introduction July 18 9
AUTOSAR – Core Partners and Partners

9 Core Partners 53 Premium Partners 38 Development Partners

General OEM

Generic Tier 1

Standard Software

Tools and Services

© AUTOSAR
127 Associate Partners
Semiconductors 21 Attendees

Introduction July 18 10
Top-level goals of AUTOSAR – 9 Project Objectives

PO 1 PO 4 PO 7
Transferability of software Definition of an open Collaboration between
architecture for automotive various partners
PO 2 software PO 8
PO 5
Scalability to different Standardization of basic
vehicle and platform Development of software functionality of
variants dependable systems automotive ECUs
PO 3 PO 6 PO 9
Broad variety of functional Sustainable utilization of Support of applicable

© AUTOSAR
domains natural resources international automotive
standards and
technologies
Introduction July 18 11
Main working topics

Architecture

Acceptance
Methodology
Tests

Application
Interfaces

© AUTOSAR
Introduction July 18 12
Main working topics

Architecture

Software architectures including a complete basic

Acceptance software stack for ECUs – the so called
Methodology
Tests AUTOSAR Basic Software – as an integration
platform for hardware independent software
applications.
Application
Interfaces

© AUTOSAR
Introduction July 18 13
Main working topics

Architecture

Defines exchange formats and description

templates to enable a seamless configuration
Acceptance
Methodology process of the basic software stack and the
Tests
integration of application software in ECUs. It
includes even the methodology how to use this
framework.
Application
Interfaces

© AUTOSAR
Introduction July 18 14
Main working topics

Architecture

Specification of interfaces of typical automotive

Acceptance
Methodology applications from all domains in terms of syntax
Tests
and semantics, which should serve as a standard
for application software.
Application
Interfaces

© AUTOSAR
Introduction July 18 15
Main working topics

Architecture

Specification of test cases intending to validate the

Acceptance
Methodology behavior of an AUTOSAR implementation with
Tests
AUTOSAR application software components or
within one vehicle network.
Application
Interfaces

© AUTOSAR
Introduction July 18 16
Topics

AUTOSAR Introduction

Approaches and standards

Developing the Adaptive Platform

© AUTOSAR
Achievements, plans, organization

Introduction July 18 17
AUTOSAR standardizes two software platforms –
Classic and Adaptive

Application Layer Application Layer Application Layer Applications Applications

RTE RTE

AUTOSAR Non- Non-

Adaptive AUTOSAR AUTOSAR
AUTOSAR AUTOSAR Platform Basic Basic
Classic Classic Software Software
Platform Platform

© AUTOSAR
e.g. SOME / IP BUS

Common Bus Interface Specification

Introduction July 18 18
AUTOSAR Classic Platform is worldwide on the road

Application Layer Application Layer Application Layer Applications Applications

First choice for deeply embedded
ECUs with high demands
RTE RTE regarding safety and deterministic
execution. Non- Non-
AUTOSAR
Adaptive AUTOSAR AUTOSAR
AUTOSAR AUTOSAR Platform Targets small Basic Basic
Classic Classic
and medium sized
Software Software
Platform Platform microcontrollers.

© AUTOSAR
e.g. SOME / IP BUS

Common Bus Interface Specification

Introduction July 18 19
Software architecture of AUTOSAR Classic Platform

Application Actuator Sensor Application

Software Software Software AUTOSAR Software
Component Component Component Software Component

Runtime Environment
AUTOSAR
Interface
Services Communication
Complex Device Standardized
Drivers AUTOSAR
Operating ECU Abstraction Interface
System
Standardized
Interface

© AUTOSAR
Basic Software Microcontroller Abstraction

ECU-Hardware

Introduction July 18 20
Basic approach

Virtual Integration Introduction of HW ECU Configuration

Attributes

© AUTOSAR
Introduction July 18 21
Basic approach

Virtual Integration >

Independent of hardware

SW-C Application
Descriptions SW- SW- SW- SW- Layer
C1 C2 C3 Cn
... Virtual
Functional Bus

© AUTOSAR
Introduction July 18 22
Basic approach

> Introduction of HW Attributes >

Holistic view of the entire system, both software and hardware

Tools supporting development of

software components

ECU System
Descriptions Constraint

© AUTOSAR
Description
ECU
Descriptions

Introduction July 18 23
Basic approach

> ECU Configuration

• Run-Time Environment
• Separation of system into its ECU plus common infrastructure

System ECU I ECU II ECU n

Descriptions SW-C 1 SW-C 2 SW-C 3 SW-C n

RTE RTE … RTE

BSW BSW BSW

© AUTOSAR
Gateway
Flex Ray CAN

Introduction July 18 24
AUTOSAR Classic Platform
Layered Software Architecture

Application Layer
HW and SW
Runtime Environment applications are
decoupled from
Services Layer each other.
Complex
ECU Abstraction Layer Drivers

Microcontroller Abstraction Layer

Microcontroller

© AUTOSAR
Introduction July 18 25
AUTOSAR Classic Platform
Acceptance Test Architecture

Acceptance Tests at Application Level, RTE and Services

Software
under Test

© AUTOSAR
Acceptance Tests at Bus Level

Introduction July 18 26
Game changer for AUTOSAR – selected main drivers

Main drivers for new automotive software systems have been determined.

© AUTOSAR
Highly automated driving

Introduction July 18 27
Game changer for AUTOSAR – selected main drivers

Main drivers for new automotive software systems have been determined.

© AUTOSAR
Car-2-X applications
Internet of Things and cloud services

Introduction July 18 28
Game changer for AUTOSAR – selected main drivers

Main drivers for new automotive software systems have been determined.

© AUTOSAR
Increasing data rates

Introduction July 18 29
Game changer for AUTOSAR – selected main drivers

Main drivers for new automotive software systems have been determined.

© AUTOSAR
New processor technologies

Introduction July 18 30
AUTOSAR Adaptive Platform for realizing future drivers

Application Layer Application Layer Application Layer Applications Applications

RTE RTE Supports the simple distribution

of adaptive applications within
AUTOSAR Non- Non-
Adaptive
AUTOSAR Platform instances
AUTOSAR
Adaptive
AUTOSAR AUTOSAR Platform Basic with Classic Platform
Interacts Basic
Classic Classic Software Software
and non-AUTOSAR systems.
Platform Platform

© AUTOSAR
e.g. SOME / IP BUS

Common Bus Interface Specification

Introduction July 18 31
 Legend
AUTOSAR Adaptive Platform SERVICE
Non-PF Service
SERVICE
Func. Cluster
API
Func. Cluster

Logical view
Adaptive Adaptive Adaptive Adaptive ASW::XYZ ASW::XYZ
Application Application Application Application Non-PF Service Non-PF Service
User Applications

ara::com ara::rest ara::time ara::state service ara::diag service ara::adi service

Communication Mgnt. RESTful Time Synchronization State Diagnostics Automated Driving
Management Interfaces
SOME/IP

(local)
DDS

IPC

ara::per ara::phm
Persistency Platform Health Mgnt.
ara::s2s service ara::nm service
ara::core ara::exec ara::iam ara::log Signal to Service Network
Core Types Execution Mgnt. Identity Access Mgnt. Logging & Tracing Mapping Management

POSIX PSE51 / C++ STL ara::crypto ara::ucm service

Operating System Cryptography Update and Configuration Management

AUTOSAR Runtime for Adaptive Applications (ARA)

© AUTOSAR
(Virtual) Machine / Container / Hardware

Introduction July 18 32
Classic Platform vs. Adaptive Platform
Technical characteristics

Based on OSEK Based on POSIX

Execution of code directly from ROM App. is loaded from persistent memory into RAM

Same address space for all applications
(MPU support for safety)
Optimized for signal-based communication
(CAN, FlexRay)
Fixed task configuration
Each application has its own (virtual) address
space (MMU support)
Service-oriented communication
Support of multiple (dynamic) scheduling

© AUTOSAR
strategies
Specification Specification and code

Introduction July 18 33
The platforms are organized by 5 AUTOSAR standards

Acceptance Application
Test Interfaces

Classic Platform Adaptive Platform

Foundation

© AUTOSAR
Common documents and
specifications for all
standards

Introduction July 18 34
Topics

AUTOSAR Introduction

Approaches and standards

Developing the Adaptive Platform

© AUTOSAR
Achievements, plans, organization

Introduction July 18 35
AUTOSAR Adaptive Platform: Success factors

Market driven feature

Frontloading of validation
development

Precision and quality of the Early availability of

standard exemplary implementation

Interoperability and
Short development cycles

© AUTOSAR
increased quality

Introduction July 18 36
Key factors to make AUTOSAR Adaptive Platform
a success

Collaboration between other standardization

bodies

Joint development of specifications and

© AUTOSAR
exemplary software implementations

Introduction July 18 37
Joint development of AUTOSAR specifications and
exemplary software implementations for the AUTOSAR
Adaptive Platform

Development in AUTOSAR Work Packages

validate

AUTOSAR AUTOSAR Software

Specifications Implementations
improve Providing for product
Licensing for exploitation
development

© AUTOSAR
Usage by AUTOSAR partners

Introduction July 18 38
Cooperation with other standards

Open to connect with others

Identifying / monitoring open source
projects

© AUTOSAR
Introduction July 18 39
Topics

AUTOSAR Introduction

Approaches and standards

Developing the Adaptive Platform

© AUTOSAR
Achievements, plans, organization

Introduction July 18 40
AUTOSAR Achievements and Outlook (1/2)
Milestones, just to name a few

First release Basic SW complete Feature enrichment Release 4.1.1

• Multicore support • Timing analysis
• Functional safety • Diagnostics
• Ethernet • Acceptance testing
•… •…

AUTOSAR Derived New development

© AUTOSAR
founded applications methods

2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

Introduction July 18 41
AUTOSAR Achievements and Outlook (2/2)
Milestones, just to name a few
Release 4.3.0 Release 4.3.1 Release 4.4.
• Hardware Test • Quality • Remote Event Communication Manager
Management on • Interface Module for • Harmonization of Physcial Units for ASW
Startup and Ethernet and IP testing and BSW Based on ASAM
Shutdown • Macro Encapsulation • Security Policy Manager Module
• Crypto Interface Of Library Calls • AUTOSAR Real Time Interface
• V2X Support • Error Detection and • RTE Implementation Plug-Ins
• Extended Buffer Correction for • LIN-Support for LIN slave
Release 4.2.1
Access for Rapid Communication
• Large data communication via • Ethernet Wake on data line
Prototyping
Ethernet and CAN FD • Formal Model Query and Blueprint
• SOME/IP Transport
• Integration of non-AUTOSAR systems Derivation Mechanisms
Protocol
•… Decentralized • Bus-Mirroring
Configuration • Extended Serialization for Data Structures
10 years of AUTOSAR in SOME/IP with tag/length/value encoding

© AUTOSAR
6th OC Nov 13

2013 2014 2015 2016 2017 2018

Introduction July 18 42
 AUTOSAR Platform Roadmap
R1.2.0 Review of open RFCs
Acceptance
Tests ✓

Adaptive R17-03 R17-10 R18-03 R18-10

Platform
✓ ✓

R4.3.0 R4.3.1 R4.4.0

Classic
Platform
✓

R1.1.0 R1.2.0
Foundation
✓ ✓

© AUTOSAR
✓
new contracts Q1/17 Q2/17 Q3/17 Q4/17 Q1/18 Q2/18 Q3/18 Q4/18
✓ released planned on demand Life Cycle development evolution maintenance

Introduction July 18 43
 AUTOSAR Adaptive Platform Roadmap

• Diagnostic Extract • Methodology Extensions • Methodology Extensions • Maintenance and

METHODOLOGY
• Manifests for Adaptive for Adaptive Improvements
• Methodology Extensions • Service to signal • Service to signal • Common System Model
for Adaptive modeling modeling
• Predefined Data Types

EXECUTION • Integration of • Resource Management • Resource Management • Maintenance and

MANAGEMENT Applications onto • Recovery action • Parallel Processing by Improvements
Platform framework HWA
• Start and Stop of • Machine State handling • Recovery action
Applications framework

POSIX
OPERATING • OS Application Interface
SYSTEM (PSE51 & C++STL)
R17-03 R17-10 R18-03 R18-10

✓ ✓

© AUTOSAR
Q1/17 Q2/17 Q3/17 Q4/17 Q1/18 Q2/18 Q3/18 Q4/18
✓ released planned on demand Life Cycle development evolution maintenance

Introduction July 18 44
 AUTOSAR Adaptive Platform Roadmap

DIAGNOSTICS • DTC Management • ISO 13400 / ISO 14229 • Maintenance and • Diagnostic Client
• ISO 14229 / ISO 13400 completion Improvements • Maintenance and
• Handling of SW Clusters Improvements

• Service-Discovery and • Time Synchronization • Signal-based • Vehicle API

COMMUNICATION
Service-based • Support of RESTful Communication • Further Language-
Communication • Network Management • Support of RESTful Bindings
• Events, Fields and Ethernet • Network Management • LIN Support
Methods Ethernet • Support of CAN and
• Language-Binding: C++ CAN-FD
• Inter-Process-
Communication
• Bus-Binding: SOME/IP

R17-03 R17-10 R18-03 R18-10

✓ ✓

© AUTOSAR
Q1/17 Q2/17 Q3/17 Q4/17 Q1/18 Q2/18 Q3/18 Q4/18
✓ released planned on demand Life Cycle development evolution maintenance

Introduction July 18 45
 AUTOSAR Adaptive Platform Roadmap
LOGGING / • Logging and Tracing • Maintenance and • Maintenance and
TRACING Improvements Improvements

SAFETY • C++14 Coding • C++14 Coding • Platform Health • Maintenance and

Guideline Guideline Management Improvements
• E2E Communication • E2E for periodic • Safety concept for AP • Redundancy
Integrity communication • E2E Communication Mechanisms
Integrity

PERSISTENCY • Data Storage • Data Storage • Maintenance and • Maintenance and

• Safe Data Storage Improvements Improvements
• Persistent Data
Encryption

R17-03 R17-10 R18-03 R18-10

✓ ✓

© AUTOSAR
Q1/17 Q2/17 Q3/17 Q4/17 Q1/18 Q2/18 Q3/18 Q4/18
✓ released planned on demand Life Cycle development evolution maintenance

Introduction July 18 46
 AUTOSAR Adaptive Platform Roadmap
SECURITY • Crypto API
• Authentication &
Certificates
• Key Management
• Secure Communication
• Crypto API
• Authentication &
Certificates
• Key Management
• Secure Communication
• Support of trusted
platform
• Crypto API
• Authentication &
Certificates
• Key Management
• Secure Communication
• Support of trusted
platform

• Package Management • Container Support?

SOFTWARE
• Installation routine • Package Download over
CONFIG. MGNT the air
• Package Management
• Installation routine
• Diagnostic Client

R17-03 R17-10 R18-03 R18-10

✓ ✓

© AUTOSAR
Q1/17 Q2/17 Q3/17 Q4/17 Q1/18 Q2/18 Q3/18 Q4/18
✓ released planned on demand Life Cycle development evolution maintenance

Introduction July 18 47
Field of Applications

Automotive applications Derived application Ultra-hazardous activities

Use-cases related to engine Use-cases that are neither an Aerospace and aviation, nuclear
powered, land-based, non-railed Automotive Application nor in a field power, chemical and/ or biological
vehicles, such vehicles intended for of use of products or service that reactors, petrochemical, or military
primary transportation purposes. falls into the categories of ultra- (except for military marine

© AUTOSAR
hazardous activities. transportation vessels).

Original target Extended Excluded

Introduction July 18 48
How do we do that?
Evolution of AUTOSAR’s Organizational Structure
Project Organization Project Management
Executive Board Technical Management

Quality Management

Support Functions
Steering
Administration

Committee Specification Management

Change Management

Release Management
Project Leader Communication
Legal Team
Team Team Quality Assurance

Requirements Mgnt

OSS-CB CF-CCB CCB Work Feature User Engineering

Open Source Consensus Finding
CB CCB
Change Control Board Packages Teams Groups
Technical Office

© AUTOSAR
SW Dev. Engineering

Legend Core Partner, Premium and All partners including

Core Partner Subcontractor
Development Partner Associate Partners

Introduction July 18 49
Work Group Structure Legend: Lead Work Package

Work Package

Feature Team
Project Leader Team

WP-A WP-M WP-I FT-CM FT-SAF WP-X-SEC

Software Methodology and Application Communication Mgmt. Safety Security
architecture Templates Interface .
FT-EMO FT-SEC WP-X-SAF
WP-A-LIB WP-M-METH WP-I-BODY Execution Mgmt. Security Functional Safety
Libraries Methodology Body and Comfort .
FT-DIAG FT-DI WP-X-VAL
WP-A-MCBD WP-M-GST WP-I-ENGINE Demonstrator Validation
Adaptive Diagnostics
Multicore BSW Distr. Generic Structure Powertrain Engine Integration
Template Cross-standard
WP-I-TRSM FT-MM
WP-A1 WP-M-SWCT Powertrain Methodology & Manifests FT-ST concerns
VFB and RTE Software Component Transmission System Tests
Template
WP-I-CHASSIS FT-PER
WP-M-SYST Chassis Control
Persistency FT-ADI
WP-A2 Automated Driving
COM Stack System Template
ECU Configuration WP-I-OCSAFE FT-UCM Interfaces
Occupant and Update & Conf

© AUTOSAR
WP-A4 WP-M-TIMEX Pedestrian Safety Management
Diagnostics Timing Extensions

WP-A5 WP-M1
MCAL Timing Analysis

Introduction July 18 50
User Group Structure

User Groups

UG-IN UG-CN UG-NA UG-IE

India China North America Improved Exploitation

• Interoperability of exchange
artifacts
• Demonstrator development • Common Training: OEM-Tier1 • 6 thesis on optimizing the use
• System design with 3 Workflows/ Security of AUTOSAR
AUTOSAR ECUs • Safety • Establishment of Adaptive
• BSW integration, • Ethernet Platform
documentation and project
closure planned for E2016

© AUTOSAR
Introduction July 18 51
Further information on AUTOSAR

For more information on AUTOSAR:

• Working results
• User Experiences
• Exploitation

You are welcome to have a look at

AUTOSAR’s publications available at the
AUTOSAR website www.autosar.org.

© AUTOSAR
Introduction July 18 52
11th AUTOSAR
Open Conference and Networking Reception

Networking Reception Conference

Tuesday, Wednesday,
November 6th, 2018 + November 7th, 2018
7:00 pm – 10:00 pm All-day

Venue:

© AUTOSAR
The Portman Ritz-Carlton Shanghai
1376 Nanjing Xi Lu, Shanghai 2000-40, China Further information:
https://www.autosar.org/news-events/

Introduction July 18 53
© 2018 by AUTOSAR
All rights reserved.
Confidential and proprietary document.

This document and all information contained herein is the sole property of AUTOSAR. No
intellectual property rights are granted by the delivery of this document or the disclosure of its
content. This document shall not be reproduced or disclosed to a third party without the
express written consent of AUTOSAR. This document and its content shall not be used for
any purpose other than that for which it is supplied.

The statements made herein do not constitute an offer. They are based on the mentioned

© AUTOSAR
assumptions and are expressed in good faith. Where the supporting grounds for these
statements are not shown, AUTOSAR will be pleased to explain the basis thereof.

Picture Credits – iStock

Introduction July 18 54