autosar adaptive in preevision - vector · 2018. 11. 6. · service autosar adaptive in preevision...

V0.2 | 2018-05-24

PREEvision 9.0

AUTOSAR Adaptive in PREEvision

u AUTOSAR Adaptive

AUTOSAR Methodology

AUTOSAR Adaptive in PREEvision

PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive Toolchain

Roadmap

Agenda

2

Motivation

AUTOSAR Adaptive

Automotive trends New requirements

u As a partner of the Automotive industry AUTOSAR saw the necessity to define a new platform

u It was clear that future cars will have heterogenous architectures

u The existing architectures had to be complemented by another one

Adaptive AUTOSAR

3

AUTOSAR Adaptive

u AUTOSAR Methodology

AUTOSAR Adaptive in PREEvision

PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive Toolchain

Roadmap

Agenda

4

AUTOSAR Methodology

Application

Machine Service instance

Operating systemwith deployedapplication

5

AUTOSAR Adaptive

AUTOSAR Methodology

u AUTOSAR Adaptive in PREEvision

PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive Toolchain

Roadmap

Agenda

6

AUTOSAR Adaptive support

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive in PREEvision

Additional applicable layers

7

AUTOSAR Adaptive

AUTOSAR Methodology

AUTOSAR Adaptive in PREEvision

u PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive Toolchain

Roadmap

Agenda

8

Design Workflow for Service-oriented Architectures in AUTOSAR Adaptive

PREEvision 9.0 – AUTOSAR System and Software Design

9

u The AUTOSAR Adaptive Explorer helps at all phases of the workflow with creating the Adaptive AUTOSAR System

u Combined with diagrams, Signal Router and further data synthesis it’s possible to create an Adaptive System from scratch or edit an existing one

AUTOSAR Adaptive Explorer

AUTOSAR Adaptive in PREEvision

10

Service

AUTOSAR Adaptive in PREEvision

u Service is an abstract description for a set of software functionality with the purpose to be available and be reused by several different clients.

u The Service Definition allows describing capabilities of the services as well as their dependencies.

u Additionally the Service ID and the preferred VLAN for a Service can be defined. These settings are considered by the following phases of the top-down design.

u The Service Definition can also be realized using the SOA Architecture Diagram

11

u Service Interface is an artefact describing the capabilities of a Service

u It allows the aggregation of Properties, Methods and Events

u Service Interfaces can be created and modified using the Service Interface Editor

u Additionally can Service Interfaces be graphically created and edited on a Class Diagram

Service Interface (1/4)

AUTOSAR Adaptive in PREEvision

12

u The sub-elements of a Service Interface are characterized by a data type.

u Data types can be assigned using the Service Interface Data Type Editor

u Designing complex data types can also be graphically realized using the Class Diagram

Service Interface (2/4)

AUTOSAR Adaptive in PREEvision

13

u PREEvision supports the SOME/IP protocol for the transport of service data over the network

u SOME/IP identifiers shall be defined for every sub-element transmitting data into the bus.

u A synthesis for the SOME/IP interface deployment is available

u The definition of the SOME/IP identifiers can be realized using the SOME/IP Interface Deployment Editor

Service Interface (3/4)

AUTOSAR Adaptive in PREEvision

14

u The serialization of the Service Interfaces is defined by mean of Transformers.

u For each Service Interface sub-element can be defined a transformation rule of for the whole Service Interface

u That can be done with the Service Interface Transformation Properties Editor

Service Interface (4/4)

AUTOSAR Adaptive in PREEvision

15

u The Software Architecture in AUTOSAR Adaptive is described by means of adaptive software components which can be grouped in composition

u Software Architectures can be created using the known software diagrams: SW Component Type or Instance Diagram and Interface Assignment Diagram

u Alternatively is also possible to work with the Provided Port Connection Editor and Required Port Connection Editor available in the AUTOSAR Adaptive Explorer

Software Architecture

AUTOSAR Adaptive in PREEvision

16

u The AUTOSAR Adaptive Application describes a collection of executables that forms an adaptive application.

u Adaptive applications can contain several executables.

u For an adaptive application can be generally defined the transformation method.

u The creation and editor of AUTOSAR Adaptive Applications can be realized with the Adaptive Application Editor.

Adaptive Application

AUTOSAR Adaptive in PREEvision

17

u For deploying an Adaptive Application is necessary to define the startup dependencies to other applications or to some states of the machine or function groups.

u It is also necessary to configure the startup parameters of the process for the operating system.

u This activity can be realized with the Process Startup Dependency Editor.

u For designing the state machine of an application can be used the State Chart

Application Deployment

AUTOSAR Adaptive in PREEvision

18

u AUTOSAR Adaptive Platform supports Ethernet as communication bus technology

u The design of the network topology can be realized using the Network Topology Diagram

u The topology can be viewed and edited with the Network Topology Editor

Network Design

AUTOSAR Adaptive in PREEvision

19

u To deploy a machine shall be described the available connections and the configuration settings of the Adaptive AUTOSAR Stack that is running on the machine

u For configuring the Machine states and the function groups applications will react on, can be used the Machine Modes Editor

u The state machines can be designed using the State Chart

Machine Deployment (1/2)

AUTOSAR Adaptive in PREEvision

20

u A further aspect to be configured for the machine deployment are the Service Discovery parameters

u IP addresses as well as ports can be configured using the Service Discovery Configuration Editor

Machine Deployment (2/2)

AUTOSAR Adaptive in PREEvision

21

u As in the classic platform, the software components are distriubuted on the available machines

u That can be graphically realized working with diagrams and drag&drop or using the

SW to HW mapping

AUTOSAR Adaptive in PREEvision

22

Service Instances (1/2)

AUTOSAR Adaptive in PREEvision

u A Service Instance makes the functionality of a Service Interface available on the AUTOSAR adaptive platform.

u Service Instances are automatically synthesized based on the information of the SW-HW mapping and the Service Interfaces assigned to the SW Ports.

u With the SOME/IP Service Instance Editor the service instances can be edited

23

u Service Instances contain the needed information for the communication into the Ethernet bus

u Tp/IP configuration as IP address and port and the Service Discovery configuration can be realized using dedicated table editors.

Service Instances (2/2)

AUTOSAR Adaptive in PREEvision

24

AUTOSAR formats and versions

AUTOSAR Adaptive in PREEvision

Import Export

Format Use CaseAUTOSAR version

Service Interface Description

Import/Export17-10

Application Manifest

Machine Manifest

Service Instance Manifest

Application Description

System Description

Custom Export

25

Supported

Service Interface

Adaptive data types (Vector, AssMap, String)

SOME/IP deployment

SOME/IP serialization

Adaptive Application SW Component Type

Adaptive Application

Executable

Process

Startup configuration

Machine

Service Instance

Service discovery

System Design*

Overview supported/not supported concepts

AUTOSAR Adaptive in PREEvision

Not supported

Persistency Interface

Diagnostics

REST

Resources

End to End Protection

Security

Crypto

Platform health

Software Cluster

Signal based communication

* partially supported

26

AUTOSAR Adaptive

AUTOSAR Methodology

AUTOSAR Adaptive in PREEvision

PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

u AUTOSAR Adaptive Toolchain

Roadmap

Agenda

27

AUTOSAR Adaptive Toolchain

AUTOSAR Adaptive Toolchain

Adaptive System Design

PREEvision

Diagnostics

Design

CANdela Studio

System Architecture

Sys Diag Design

App Design

App Diag Design

Service Instance

Machine Manifest

App Manifest

System Design

PlatformService

Deployment

Application Design

Deployment Configuration

Manifest

Application Description

Simulation/Test

CANoe

App.-Code

Application Code

DaVinci Adaptive IDE

SW Platform

AMSR Generators

App.-Code

(Service Impl)

Manifest

28

AUTOSAR Adaptive

AUTOSAR Methodology

AUTOSAR Adaptive in PREEvision

PREEvision 9.0 – AUTOSAR System and Software Design

AUTOSAR Adaptive in PREEvision

AUTOSAR Adaptive Toolchain

u Roadmap

Agenda

29

u PREEvision 9.0 End of July 2018

u PREEvision 9.5 2019

u Candidate features for PREEvision 9.5> AR Ad 18-10 and/or 19-03

> C++ data types

> End to end protection

> Security

> Extensions of support for mixed platform system

> Further UML integration (state charts, activity chart, sequence chart)

> …

PREEvision 9.5

Roadmap

30

© 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.2 | 2018-05-24

Author:Marcelino VarasVector Germany

For more information about Vectorand our products please visit

www.vector.com