V2.0 | 2018-08-31

Low Carbon Vehicle Show, Millbrook, 2018-09-13

Enabling Connectivity with Service Oriented Architectures

New Vehicle Functions and Services with Connectivity

The IT Backend Perspective

The Vehicle Perspective

The Business Perspective

The Technical Perspective

Different Perspectives on Connectivity

© Ricky Hudi, Audi AG: Die Automobilindustrie im (radikalen) Umbruch, 20. Intern. FachkongressFortschritte in der Automobilelektronik, June 14-15, 2016, Ludwigsburg2

© Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles, Presentation on the 8. Vector Congress, Nov. 29.-30, 2016, Stuttgart

Characteristics of Signal Oriented Architectures

Distributed systems with signal-based communication … between SW components and … between ECUs.

Many decisions are done at design time: Binding of SW components Communication design: Signal, PDU, Frame and Schedule Design

The complete system is known and considered at design time (“Closed static distributed system”).

Distributed SW architecture is based on SW Components with sender/receiver communication.

AUTOSAR Classic is a mature, widely accepted and used implementation platform.

Implementation is done in C.

From Signal Oriented to Service Oriented Architectures

Design Time Run Time

Signal Oriented Architectures

AUTOSAR Classic ECU/System

SWC1 SWC3

SWC2 Data ElementSender

Receiver

Basic Software (BSW)

RTE

AUTOSAR Classic ECU

SWC1 SWC2

Signal

Basic Software (BSW)

RTE

AUTOSAR Classic ECU

SWC3

3

Signal Oriented Architectures – Summary

Strengths The complete system is known. The system behavior is predictable at design time (real time behavior

and memory resources). Optimisations regarding resources are possible at design time

(message copies, bus scheduling,…).

Weaknesses Low flexibility at run time. The system cannot be extended after design time. High design and test efforts

> for communication (Signals, PDUs, Frames and Schedules).> for start up and shut down behavior of the distributed system (network management, …).

No support for more complex SW architectures (SW components with only Sender/Receiver Interfaces are used).

Customer Benefits Predictability of distributed embedded real time systems. Cost optimized implementation with low resources for microcontrollers and communication

technologies.

From Signal Oriented to Service Oriented Architectures

Design Time Run Time

Signal Oriented Architectures

4

Characteristics of Service Oriented Architectures

Distributed systems with service-based communication … between SW components and … between ECUs.

Important decisions are made at run time, not at design time! Binding (by service discovery) Communication is dynamic (e.g. dynamic PDU content transmitted using serialisation and

deserialisation)

“Open system”: Services can be added at run time (e.g. outside the vehicle).

The SW Architecture is designed with SW components with service interfaces.

AUTOSAR Adaptive as implementation platform.

Implementation in C++

From Signal Oriented to Service Oriented Architectures

AUTOSAR Adaptive ECU/System

SWC1 SWC3

SWC2 Service InterfaceService Provider

Service Consumer

Switch

… but AUTOSAR Classic can also be used as implementation platform for Service Oriented Architectures.

© Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles, Presentation on the 8. Vector Congress, Nov. 29.-30, 2016, Stuttgart

Design Time Run Time

Service Oriented Architectures

5

What is a Service?From Signal Oriented to Service Oriented Architectures

Service Participant

3

Service Participant

2

Service Contract

Service Interface

Method

Fire&Forget Method

Property

Event

ServiceProviderPort

ServiceConsumer

Port

SOA Diagram in PREEvision

6

Service Oriented Architectures: Summary

Strengths Higher flexibility at run time. Services inside and outside the vehicle can be linked. Extensions and updates of services are possible. Simplified communication design. Simplified start up and shut down design. Implementation of complex and open SW architectures (Complex Interfaces, Layers, Remote

Procedure Calls, …) possible. Maintenance and extensions of SW architectures are easier.

Weaknesses Predictability of system behavior (different results of service discovery possible). Higher resources for implementation needed (microcontrollers and communication technologies). Many different, dynamic system configurations have to be tested.

Customer Benefits Flexible, open and dynamic distributed embedded systems.

From Signal Oriented to Service Oriented Architectures

Design Time Run Time

Service Oriented Architectures

7

Service Oriented Architectures are Enablers …

… for Connectivity Completely new functions by flexible integration of services in the IT backend

… for Autonomous Driving Communication from the vehicle to the IT backend and vice-versa Creation of precise maps Predictive assistants based on precise maps Routing for vehicle fleets in the IT backend …

… for SW Update, SW Upgrade and Service for Vehicles in the Field

SW update of single services SW update and upgrade for vehicles in the

field ‘Over the Air’ Remote diagnostics …

… for Variant and Building Set Strategies SW options can be implemented as services

(base service … premium service)

From Signal Oriented to Service Oriented Architectures

© Ricky Hudi, Audi AG: Die Automobilindustrie im (radikalen) Umbruch, 20. Intern. FachkongressFortschritte in der Automobilelektronik, June 14-15,2016, Ludwigsburg8

Strengths of Signal Oriented Architectures The complete system is known. The system behavior is predictable at design

time (real time behavior and memory resources).

Optimisations regarding resources are possible at design time (message copies, bus scheduling,…).

Many years of experience Many mature components exist

Customer Benefits Predictability of distributed embedded real

time systems. Cost optimized implementation with low

resources for microcontrollers and communication technologies.

Strengths of Service Oriented Architectures Higher flexibility at run time. Services inside and outside the vehicle can be

linked. Extensions and update of services are

possible. Simplified communication design. Simplified start up and shut down design. Implementation of complex and open SW

architectures (Complex Interfaces, Layers, Remote Procedure Calls, …) is possible.

Maintenance and extensions of SW architectures are possible.

Customer Benefits Flexible, open and dynamic distributed

embedded systems.

Signal Oriented versus Service Oriented ArchitecturesFuture E/E Architectures

9

Signal Oriented or Service Oriented Architectures?Future E/E Architectures

Either … or … ?

Service Oriented Architecture

Signal Oriented Architecture

… as well as … !

Service Oriented Architecture

Signal Oriented Architecture

Future E/E architectures will combine the strengths of both:

Signal Orientation and Service Orientation

“Hybrid architectures” are expected.

© Ricky Hudi, Audi AG: Die Automobilindustrie im (radikalen) Umbruch, 20. Intern. Fachkongress Fortschritte in der Automobilelektronik, June 14-15,2016, Ludwigsburg

Vehicle ECU 13 ECU 15

ECU1

ECU 3

ECU 6

ECU 4

ECU 2

ECU 5

Service Oriented Architecture

Signal Oriented Architecture

ECU7

ECU 9

ECU 12

ECU 10

ECU 8

ECU 11

IT Backend

ECU 14

10

© Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles, Presentation on the 8. Vector Congress, Nov. 29.-30,2016, Stuttgart

Signal Oriented or Service Oriented Architectures?Future E/E Architectures

Also “Hybrid ECUs” are expected.

11

Enabling Connectivity with Service Oriented ArchitecturesSummary and Outlook

Software/Service Architecture

Service Oriented Architecture

SWC Instances

AUTOSAR Classic

SWC Instances

AUTOSAR Adaptive

SW Library

1 2

3a 3b

© Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Autonomous Vehicles, Presentation on the 8. Vector Congress, Nov. 29.-30, 2016, Stuttgart12

Enabling Connectivity with Service Oriented Architectures

Service Oriented Architectures (SOAs) provide flexible, open and dynamic distributed systems.

They are enablers for: Connectivity and Autonomous Driving SW Update, SW Upgrade and Vehicle Service in the field New Building Set Strategies and Handling of Variants.

Future E/E Architectures will combine the strengths of Signal Oriented and Service Oriented Architectures.

The AUTOSAR Adaptive and AUTOSAR Classic Platforms will be deployed in the same vehicle, even in the same ECU.

The introduction of SOAs, the migration to SOAs and their implementation in AUTOSAR Classic are underway right now!

Talk with us to learn more about how you can: Implement SOA in AUTOSAR Adaptive Platform, Have hybrid applications of AUTOSAR Adaptive and AUTOSAR Classic, and Design SOAs with UML and SysML Diagrams and thereby configure AUTOSAR ECUs.

Summary and Outlook

13

Please visit us at C3 410Want to know more?

14

© 2017. Vector GB Limited. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V2.0 | 2018-08-31

Author:Iain CunninghamVector UK

Your questions are welcome!