AUTOSAR System and Software Design with …...> Short theoretical introduction of the process > Tool demo > Improvements in Communication tooling Questions will be answered at the

V0.0 | 2020-05-19

PREEvision 9.5

AUTOSAR System and Software Design with PREEvision

RELEASED

2

To my person:> Claudia Gettkandt

> Product Manager for PREEvision

> AUTOSAR, Communication, Diagnostics

> At Vector since 2017

Goals and Focus of todays Webinar:> Focus on Communication design in AUTOSAR Classic

> Short theoretical introduction of the process

> Tool demo

> Improvements in Communication tooling

Questions will be answered at the end of the Webinar, please use the Q&A Window

Introduction

3

u AUTOSAR System and Software Design with PREEvision

Tool Demo

Communication Tooling in PREEvision

PREEvision 9.5 – Communication Improvements

Agenda

4

OVERVIEW


5

Overview


AUTOSAR in PREEvision

Software Architecture

Network Topology Communication

6

Overview


7

Overview


u Multi user support

u Lock concept on artifact level to prevent access conflicts

u All users have always access to up-to-date information

u Version and configuration management

8

AUTOSAR


9

AUTOSAR Workflow (theory)


VFB

Virtual Function Bus

SWC1

SWC2 SWC3

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

Extract of System Description*ECU ConfigurationDescription (ECUC)*

Software Component Description*

*

SWC1 SWC2

Basic Software (BSW)

RTE

Complete SW functionality of the vehicle is defined as a system of SWCs...

..and distributed to ECUs

An extract is created for each ECU...

The ECU is configured based on the ECU Extract.

ECU1

SWC1

SWC2

10

u Virtual function bus design

u Topology design

u Software/Hardware mapping

u Data mapping and signal routing

u CAN, CAN FD, LIN, FlexRay design

AUTOSAR System Design Workflow


12

Format Use Case AUTOSAR version

SystemDescription

ImportExportUpdate

3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

ECU Extract Export 3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

ECU System Description

Export 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

Software Component(and other custom extracts)

ImportExportUpdate

3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

AUTOSAR Import


* Limited support

14

Software Design


u Graphical diagrams to model SW architecture

u Library to define SW components, interfaces, data types, etc.

u TPI (Type-Prototype-Instance) concept

u Engineering tools to merge/split/move SW Components, automatic connection of ports, propagation of port interfaces

u Dedicated editors and views for ports, connections, interfaces, etc.

15

Hardware Network Design


u Graphical diagrams to model HW architecture

u Reuse of HW components

u Engineering tools to change type of HW components, change type of bus, …

16

SW Component Mapping


u Mapping of SW Components to HW Components

u Mappings are objects and support variant management

u Graphical visualization of mappings in diagrams

u Mapping editor

17

Data Mapping and Signal Routing


u Signal router to automatically create signals, data mappings and signal routes (including gateways entries)

u Various routing options and delta routing

18

Network Communication Design


u Frame/PDU/Signal layout editor

u Protocol specific bus editors for CAN, CAN FD, LIN and FlexRay

u Dedicated editors for Frames, Signals, etc.

u Support of legacy formats (LDF, DBC, FIBEX)

19

AUTOSAR Export (Supplier Integration)


u Consistency checks

u Generation of specification documents

u Export / Import of AUTOSAR System Description, System Extract, ECU System Description, ECU Extract, SW Component.

u Update of several formats

* Limited support

Format Use Case AUTOSAR version

SystemDescription

ImportExportUpdate

3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

ECU Extract Export 3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

ECU System Description

Export 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

Software Component(and other custom extracts)

ImportExportUpdate

3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0

20

WORKFLOW


21

Vector AUTOSAR Tool Chain


System Description

SW Component Description

AUTOSAR

System Design

PREEvision

System Description

ECUExtract

ECUSystem

Description



RTE ConfigurationBSW Configuration

DaVinciConfigurator Pro

SWC Detailed Design

(RTE Configuration)

DaVinci Developer

ECUC

ECU Extract

System scope

ECU scope

Soft

ware

Inte

gra

tion P

ackage

Bus simulation

CANoe

Implementation

Model based impl. tool

Up

date

Ch

an

ge

man

ag

em

en

t

CustomExtract

23

> Tool demo

Tool Demo

24


Tool Demo

u Communication Tooling in PREEvision


Agenda

25

u There are a lot of artifacts….

Overview

Communication Tooling in PREEvision

Interface

DE1 Signal1M Signaltransmission1

Channel Communication

ECU Interfaces

Signal GW Rout. Entry

Gateway

IPDU

Frame

Assign-ment

PDUtransmission

Frametransmission

PDU GW Rout. Entry

Frame GW Rout. Entry

Manual steps

Signal Router

Frame Synthesis

26

Unified Communication Modeling for Mixed Systems


MM

PDU

Signal (serialized)SOME/IP header

Tx Rx

u On the Software Layer, Adaptive and Classic software components can be connected with the new Port Adapter.

u The software components are mapped to machines and ECUs.

u The Signal Router creates a SOME/IP representation of the Service Interface on the bus (Ethernet).

u The SOME/IP representation consists of PDUs with serialized Signals containing the data of methods or events.

u For Classic ECUs, this information is taken into the ECU Extract.

u For Adaptive Machines, this information is used to check the consistency of the model and will be ignored on export.

Signal Router checks the system consistency and synthesizes the communication

27

Configuration Support for Secured Onboard Communication (SecOC)


u Additional Artifacts for Specification of AUTOSAR SecOC Configuration:

u Secure Communication Freshness Configuration

u Secure Communication Authentication Configuration

u SecOC Crypto Service Configuration including> Crypto Service Key

> Crypto Service Primitive

Legend: New in PREEvision 9.5

The SecOC Configuration artifacts are linked tothe Secured IPDU and the PDU Transmission:

28

Configuration Support for Transport Layer Security (TLS)


u Additional Artifacts for Specification of AUTOSAR Transport Layer Security (TLS):

u TLS Crypto Cipher Suite including> Crypto Service Certificates

> Crypto Service Primitives

> Crypto Service Keys

u TLS Key Assignment

u TLS is the Successor of SSL

u Supported in AUTOSAR 4.4.0 ff

u Use cases are DoIP and Smart Charging

Legend: New in PREEvision 9.5

The TLS artifacts are linked to theApplication End Point:

29 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.0 | 2020-05-19

Author:Jörg Schäuffele, Marcelino Varas, Markus Helmling, Claudia GettkandtVector Germany

For more information about Vectorand our products please visit

www.vector.com

http://www.vector.com/

Documents

AUTOSAR System and Software Design with …...> Short theoretical introduction of the process > Tool demo > Improvements in Communication tooling Questions will be answered at the