global automotive e/e standard - or manager …...2014/11/02 · 24 october 22, 2014 7th autosar...

Global Automotive E/E Standard

Rick Flores, General Motors, AUTOSAR Steering CommitteeOpen Architecture SummitWashington, D.C. November 4, 2014

90% of all innovations

Linked networks

Infotainment

Electronic supportMechanics

E/E innovations in vehicle development increases

AUTOSAR – The Global Automotive E/E Standard23rd October, 20132

Major innovations

are fully based on

E/E

1970 1980 1990 2000 2010 2020

2003 – 10 companies found AUTOSAR

23rd October, 2013 AUTOSAR – The Global Automotive E/E Standard3

AUTOSAR has Become a Global Standard

October 22, 20144

Europe:91 Partners

America:27 Partners Asia:

67 Partners

Africa:1 Partner

7th AUTOSAR Open Conference

AUTOSAROrganization and

Processes

AUTOSARMotivation and

Partnership

AUTOSAROutlook

AUTOSARWorldwide and other Standards

Overview

AUTOSAR Guided Tour (Part 1)2013-085

1 2 3 4


Processes


Partnership

AUTOSAROutlook


Overview

AUTOSAR Guided Tour (Part 1)Motivation and Principles

2013-086

Vision and Objectives

Cooperation and Partner Status

1 2 3 4

Methodology:Defines exchange formats and description templates to enable a seamless configuration process of the basic software stack and the integration of application software in ECUs. It includes even the methodology how to use this framework.

Application Interfaces:Specification of interfaces of typical automotive applications from all domains in terms of syntax and semantics, which should serve as a standard for application software.

Architecture:Software architecture including a complete basic software stack for ECUs – the so called AUTOSAR Basic Software – as an integration platform for hardware independent software applications.

AUTOSAR Main Working Topics

ApplicationInterfacesMethodology

Architecture

Methodology

Architecture

ApplicationInterfacesMethodology

Architecture

2013-087 AUTOSAR Guided Tour (Part 1)Motivation and Principles

ApplicationInterfaces

Running the AUTOSAR partnership: Three tier partnership structure


Premium Partners

Leadership of Working Groups

Involvement in Working Groups

Development Partners

Dedicate expertise contributions

Involvement in Working Groups

Core Partners

Organizational control Administrative control

Associate Partners

Users of the AUTOSAR standard

Up-to-date status see: http://www.autosar.org

AUTOSAR Partners (March 2014)

AUTOSAR Guided Tour (Part 1)Motivation and Principles

2013-089

AUTOSAR VisionAUTOSAR aims to improve complexity management of integrated E/E architectures through increased reuse and exchangeability of SW modules between OEMs and suppliers.

25.-26. June 2014, Munich10 The Future of AUTOSAR

Cooperate on standards, compete on implementation.

The Principles of the Development Cooperation

Core-, Premium- and Development Partners jointly develop a common automotive standard

AUTOSAR Partners grant each other a non-exclusive, non-transferable license under its essential intellectual property rights

AUTOSAR Partners do not assert against each other when commercially exploiting the AUTOSAR standard

As part of their exploitation of AUTOSAR, AUTOSAR Partners developed AUTOSAR compliant products

AUTOSAR Partners commit for product conformance to AUTOSAR specifications to ensure interoperability

Product conformance

2013-0811 AUTOSAR Guided Tour (Part 1)Motivation and Principles

Running the AUTOSAR partnership: Exploitation license valid for automotive applications

“Automotive Applications

means applications related to engine powered,

land-based, non-railed vehicles, such vehicles

intended for primary transportation purposes.”

23rd October, 201312 AUTOSAR – The Global Automotive E/E Standard

Running the AUTOSAR partnership: Exploitation license valid for derived applications

Civil machineries Ultra hazardous activities

23rd October, 2013 AUTOSAR – The Global Automotive E/E Standard13

Marine including military marine transportation vessels, railway powertrain, agriculture and forest machinery, construction and mining machinery, compressors and pumps, or power generators.

aerospace and aviation, nuclear power, chemical and/or biological reactors, petrochemical, or military (except for military marine transportation vessels).

AUTOSARProcesses and Organization


Partnership

AUTOSAROutlook


Overview

Life cycle model and concept handling process

Release Phases

AUTOSAR Guided Tour (Part 1)Organization and Processes

2013-0814

Management boards and work packages

1 2 3 4

Today


2013-0815

AUTOSAR Release Phases

StabilizationSelective Enhancements

Maintenance and support of the exploitation

Development ofArchitecture and Methodology

2014

Phase II Phase III

20102007 2008 2009 2011 2012 2013 2015

Rel. 3.2

Rel. 3.1.5 (LoKI*)

*Loki = List of known issues

Rel. 3.1

Rel. 4.2 Rel. 4.1Rel. 4.0Rel. 4.0

Rel. 2.x (LoKI*)

Development Evolution Maintenance Issue Notice

AUTOSAR Continuation

DMS2DMS1 DMS3bDMS3a

MS2MS1 MS3a MS3b MS4


2013-0816

AUTOSAR Release Management:Decoupled Concept Development Process

Evaluate concept (initial technical assessment, dependencies to other concepts) Agree on use cases and features Refine concept request

Agree on refined use cases and features, concept elements and concept parts Identify affected specifications, new specifications to be created Investigate different solutions, and select the most suitable Prepare project plan and propose validation strategy

Prepare “copy-and-paste” ready solution based on expert discussions Agree on final technical solution with owner of affected documents

Prove maturity of concept Identify inconsistencies & incompleteness

Add technical solution to theAUTOSAR documents

Part 1

MS0

Part 2

Part 1

Part 2

Concept Assessment

Concept Elaboration

Detailing

Validation

IncorporationPart … Part …

October 22, 201417

Achievements – new concepts in release 4.2.1

7th AUTOSAR Open Conference

For the AUTOSAR Basic Software and Methodology Release 4.2.1 new concepts were developed and integrated:

Communication Enhanced Ethernet Support

Switch Configuration Sender Receiver Serialization

CAN FD

Safety & Security E2E Extension ASIL QM Protection Secure On Board Communication

Basic Software NV Data Handling RTE EcuM Fixed MC

Methodology Safety Extensions Decentralized Configuration

AUTOSAR OrganizationOverview

2013-0818 AUTOSAR Guided Tour (Part 1)Organization and Processes

Core Partner Lead WP and WP

Subcontractor Regional WPs

Supp

ort F

unct

ions

Project Organization

Adm

inis

trat

ion

Technical Manager

Quality Manager

Change Manager

Release Manager

Technical Office

Quality AssuranceLegal TeamCommunication Team

Executive Board

…

Project Leader Team

Work Packages

Steering Committee

Work Package structure from 2015 on

7th AUTOSAR Open ConferenceOctober 22, 201419

Cross-product concerns

Functional Safety

WP-A3

VFB and RTE

WP-A1

COM Stack

WP-A2

Timing Analysis

WP-M1

Diagnostics

WP-A4

MCAL

WP-A5

ApplicationInterfaces

WP-I

WP-I-BODYBody and ComfortWP-I-ENGINEPowertrain EngineWP-I-TRSMPowertrain TransmissionWP-I-CHASSIS Chassis ControlWP-I-OCSAFEOccupant and Pedestrian Safety

SoftwareArchitecture

WP-A

WP-A-LIBLibraries

WP-A-PRODERRProduction Errors

Methodology and Templates

WP-M

WP-M-METHMethodologyWP-M-GSTGeneric Structure TemplateWP-M-SWCTSoftware Component TemplateWP-M-SYSTSystem TemplateECU ConfigurationWP-M-TIMEXTiming Extensions

Legend:

Lead WorkPackage

Work PackageWP-x.y

Subgroups

Validation

WP-X-VAL

Security

WP-X-SEC

Project Leader Team

Acceptance Test

WP-T

Japan

WP-R-JP

Subgroups


Processes


Partnership

AUTOSARAchievements and Outlook


Overview

AUTOSAR Guided Tour (Part 1)Worldwide and other Standards

2013-0820

Globalization - motivation and activities

Regional co-operations

Other Standards

1 2 3 4


2013-0821

Motivation to Globalize the AUTOSAR Organization

Foster AUTOSAR as a global standard

Make the participation for partners in the regions China, India, Japan and US more attractive. That means: Make F2F-Meetings easier Cover local / regional requirements (e.g. provide specific configuration, translations …) Motivate our regional partners to join and support the standardization process

Avoid the creation of variants of the standard in the regions

AUTOSAR started to introduce regional work packages and user groups

AUTOSAR Worldwide: Open to Connect Others …


2013-0822

First activities startedAt least to be considered …


Processes


Partnership

AUTOSAROutlook


Overview

AUTOSAR Guided Tour (Part 1)Achievements and Outlook

2013-0823

Future of AUTOSAR

1 2 3 4

Future of AUTOSAR – objectives and challenges


Maintain stability and compatibility of existing standard.

Main directions of the Future of AUTOSAR: Reflect new use cases of today’s and future market

needs. Adapt to upcoming market needs. Support new technologies.

2014 2020

Anticipate the future – identification oftechnological trends, key features and next challenges for AUTOSAR

Stabilize the standard – maintain the standard, reduce complexity and increase usability, improve job sharing

Starting point – selected main drivers


Main drivers for new automotive software systems have been determined.

Highly automated driving Car-2-X applications

Open access to vehicle Stronger interaction

Summary

26 The Future of AUTOSAR

Challenges of a living standard: Improve stability and keep compatibility with existing releases Reflect new use cases of todays and future market needs

Main directions of the Future of AUTOSAR: Improve existing standard Adapt to upcoming market needs Support new technologies: Car2X, enhanced security, dynamic

architectures, …

25.-26. June 2014, Munich

Thank you for your attention!

2013-0827 AUTOSAR Guided Tour (Part 1)Achievements and Outlook

More Information about AUTOSAR:

http://www.autosar.org

Become a partner and get exploitation rights for the AUTOSAR standard

[email protected] information only (see disclaimer)

Published Releases

Backup

AUTOSAR and AUTOSAR and Trends in Automotive Software11/12/201428

GM SYSTEM/ SOFTWARE PRODUCT LINES BACKUP

2 9

GM NEXT GENERATION TOOLS

PROBLEM STATEMENT

How do we create a tool set that allows:• Full explicit traceability across the development lifecycle in a high reuse, multi-

deployment Product Line

• Modern Architecture Management Methods

• Information hiding, component based software engineering, generated

middleware, …

• Global large scale multi-user collaboration (~3000 users)

• Ease of use

• Minimization of CM version conflict (avoid merges)

30

WHAT IS A PRODUCT LINE

A Product Line is a set of systems sharing a common, managed set of features

that are developed from a common set of core assets in a prescribed way

Why Product Line over Products – Our Experience

• As much as an 85% reduction in effort for a second application

• As much as a 70% reduction in field claims

Functional Architecture Implementation Architecture Deployment Architecture

Electrical Hierarchy

Domain Hierarchy

FE FE

Software, Algorithm Models & Parameter Definition

Mechanizations

SW Hierarchy System Design Model

•SWC•HWC•Networks

ECU

ECU ECU

1…n Networks

ECU Extracts

Allocate Components to ECUs

Integration Platform (Based on OSLC)Change\ CM

DiagnosticDesign

NetworkDesign

Core ArchDesign

ControllerDevelopment

Logical View

Vehicle Application Architecture

System Data

•Hardware Connectivity •Power & Ground•Merge with 3D data for wiring •Service Documentation

•Archite

cture

Requ

iremen

ts•

PLE Mod

els

SYSTEM ENGINEERING DEVELOPMENT LIFECYCLE ‐ ELECTRICAL

Product Line Engineering

SYSCFunctional Packaging

Structural Packaging

Allocate SYSCs to ECUs

Subsystems

Functions

Domain

System Hierarchy

HW Hierarchy

Hardware Elements

Allocate FEs to HW/SW

•Re

quire

men

ts•

PLE Mod

els

FE

32

AN EFFICIENT MEANS OF PRODUCTION FOR

SYSTEMS AND SOFTWARE PRODUCT LINES

THE SPL LIFECYCLE FRAMEWORK

SYNCHRONOUS CONCERNS IN A SPL SOLUTION

• Multi-product. Feature-based variation management and automated production line

• Multi-phase. Product line lifecycle assets, architecture and traceability

• Multi-baseline. Product line change management and baseline management

PLE LIFECYCLE BASED ON A CONFIGURABLE BILL OF FEATURES

Stakeholder Requirements

System Requirements

HardwareSubsystemRequirements

SoftwareSubsystemRequirements

HardwareSubsystem

Design

SoftwareSubsystem

Design

HardwareComponentImplementation

SoftwareComponent

Implementation

User Acceptance Test

System Integration Test

SubsystemIntegration

Hardware Test

SubsystemIntegration

Software Test

HardwareSubsystem

Internal Test

SoftwareSubsystem

Wht Box Test

HardwareComponent

Test

SoftwareUnit

Test

Bill of Features

ECU Allocation

Vehicle Layout

Yesterday Today

Application Software

HardwareHardware

Software

Exploring AUTOSAR: Hardware independent architecture


Customized

Standardized

ComplexDrivers

Microcontroller Drivers

Memory Drivers I/O Drivers

I/O Hardware Abstraction

Memory Hardware

Abstraction

Memory ServicesSystem Services

Onboard Device Abstraction

Communication Drivers

Communication Hardware

Abstraction

Communication Services

Microcontroller

Application Layer

Runtime Environment

SWComponents

Exploring AUTOSAR: Software architecture


Basic Software

ECU Resources

Middle Ware

Exploring AUTOSAR: Basic Software Abstraction inside the Infrastructure Architecture

ComplexDrivers

Microcontroller

AUTOSAR Runtime Environment (RTE)

Microcontroller Drivers Memory Drivers I/O Drivers


Memory Hardware Abstraction


Onboard DeviceAbstraction

CommunicationDrivers

CommunicationHardware Abstraction

CommunicationServices

Application Layer

I/O Drivers



Communication Hardware Abstraction

CAN Driver

Driver for ext.CAN ASIC

SPIHandlerDriver

Diagnostic

Com

.M

anagerAUTOSAR COM

CAN NM

µC SPI CAN

External CAN Controller

CAN Transceiver Driver

DIO Driver

Generic NM Interface

CANState ManagerPDU Router

CAN Interface

Debugging

IPD

U

Multiplexer

J1939 Transport Protocol

CAN Transport Protocol

Example: Communication Stack – CAN


ComplexDrivers

Microcontroller Drivers

Memory Drivers I/O Drivers


Memory Hardware

Abstraction


Onboard Device Abstraction


Communication Hardware

Abstraction


Microcontroller

Application Layer

Runtime Environment

SWComponents

Exploring AUTOSAR: Application interfaces


ActuatorSoftware

Component

SensorSoftware

Component

ApplicationSoftware

ComponentAUTOSARInterface

AUTOSARInterface

AUTOSARInterface

ApplicationSoftware

ComponentAUTOSARInterface

Ports implement the interface according to the communication paradigm.

Ports are the interaction points of software components.

The communication is channeled via the RTE.

The communication layer in the basic software is not visible at the application layer.

PowertrainOccupant Safety

Exploring AUTOSAR: Application interfaces – Example engine speed

41

Seat Belt Reminder

Combustion Engine

Data type „N1“ [rpm]:Uint16 value with resolution 0.5

Port „Engine Speed“

The actual rotationalspeed of the enginecrankshaft.

Interface „Engine Speed 1“

Connection to transfera rotational speed of type N1.

41 23rd October, 2013 AUTOSAR – The Global Automotive E/E Standard

Exploring AUTOSAR: Methodology – Basic approach


System Constraint Description

ECU Descriptions

Tools supporting development of software components

ECU Description

...

Gateway

ECU nSW-C n

RTE

BSW

Flex Ray CANSystem Description

ECU IISW-C 3

RTE

BSW

ECU ISW-C 2

RTE

BSW

SW-C 1

Virtual Integration

Introduction of HW Attributes

ECU Configuration

Application Layer

Virtual Functional Bus

SW-C 1 ... SW-C nSW-C 3SW-C 2

SW-CDescriptions

ECU n

Exploring AUTOSAR: Methodology – AUTOSAR description templates


...

GatewayFlex Ray CAN

ECU IIECU I

RTE

Basic Software

RTE

Basic Software

RTEBasic

Software

SW-C nSW-C 3SW-C 2SW-C 1

Application Layer

Virtual Functional Bus

...

AUTOSAR description templates SWC description:

application software

ECU description:ECU characteristics and configuration

System description: network and assignment of SWCs to ECUs

Tool-based deployment of SWCs to ECUs

enable

SW-C 1 SW-C nSW-C 3SW-C 2SW-C 1 SW-C nSW-C 3SW-C 2

global automotive e/e standard - or manager …...2014/11/02 · 24 october 22, 2014 7th autosar...

Documents