V2.0 | 2017-09-21
Vector GB Conference 2017
Enabling Connectivity with Service Oriented Architectures
2
u Different Perspectives on Connectivity
From Signal Oriented to Service Oriented Architectures
Future E/E Architectures
Service Oriented Architectures with AUTOSAR Classic
Service Oriented Architectures with AUTOSAR Adaptive
Summary and Outlook
Agenda
3
New Vehicle Functions and Services with Connectivity
Different Perspectives on Connectivity
© Ricky Hudi, Audi AG: Die Automobilindustrie im (radikalen) Umbruch, 20. Intern. Fachkongress Fortschritte in der Automobilelektronik, June 14-15,2016, Ludwigsburg
u The IT Backend Perspective
u The Vehicle Perspective
u The Business Perspective
u The Technical Perspective
4
Different Perspectives on Connectivity
u From Signal Oriented to Service Oriented Architectures
Future E/E Architectures
Service Oriented Architectures with AUTOSAR Classic
Service Oriented Architectures with AUTOSAR Adaptive
Summary and Outlook
Agenda
5 © 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
From Signal Oriented to Service Oriented Architectures
AUTOSAR Classic ECU/System
SWC1 SWC3
SWC2 Data Element
Sender
Receiver
u Distributed systems with signal-based communication
u Between SW components and
u Between ECUs
u Many decisions are done at design time:
u Binding of SW components
u Communication design: Signal, PDU, Frame and Schedule Design
u The complete system is known and considered at design time ("Closed static distributed system")
u Distributed SW architecture is based on SW Components with sender/receiver communication
u AUTOSAR Classic is a mature, widely-accepted and used implementation platform
u Implementation in C
Basic Software (BSW)
RTE
AUTOSAR Classic ECU
SWC1 SWC2
Signal
Basic Software (BSW)
RTE
AUTOSAR Classic ECU
SWC3
Design-Time Run-Time
Signal Oriented Architectures
6
Design Workflow for Signal Oriented Architectures in AUTOSAR Classic
From Signal Oriented to Service Oriented Architectures
Software Architecture
Hardware Architecture
7
Signal Oriented Architectures - Summary
From Signal Oriented to Service Oriented Architectures
u Strengths
u The complete system is known
u The system behaviour is predictable at design time (real-time behaviour
and memory resources)
u Optimisations regarding resources are possible at design time
(message-based routing, bus scheduling,…)
u Weaknesses
u Low flexibility at run-time. The system cannot be easily extended after design-time
u High design and test efforts > For communication (Signals, PDUs, Frames and Schedules)
> For start-up and shut-down behaviour of the distributed system (network management, …)
u No support for more complex SW architectures (SW components with only Sender/Receiver Interfaces are used)
u Customer Benefits
u Predictability of distributed embedded real-time systems
u Cost-optimised implementation with low resources for microcontrollers and communication technologies
Design-Time Run-Time
Signal Oriented Architectures
8
Characteristics of Service Oriented Architectures
From Signal Oriented to Service Oriented Architectures
u Distributed systems with service-based communication
u Between SW components and
u Between ECUs
u Important decisions are done at run-time, not at design-time!
u Binding (by service discovery)
u Communication is dynamic (e.g. dynamic PDU content transmitted using serialisation and deserialisation)
u "Open system": Services can be added at run-time (e.g. outside the vehicle)
u The SW Architecture is designed with SW components with service interfaces
u AUTOSAR Adaptive as implementation platform currently in specification
u Implementation in C++ AUTOSAR Adaptive ECU/System
SWC1 SWC3
SWC2 Service Interface
Service Provider
Service Consumer
Switch
u … but AUTOSAR Classic can also be used as an 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
9
What is a Service?
From Signal Oriented to Service Oriented Architectures
AUTOSAR Adaptive ECU/System
SWC1 SWC3
SWC2 Service Provider
Service Consumer
Switch Serialisation/Deserialisation Ethernet
Service Discovery
Technology Mapping
Technology Mapping
Service Participant
3
Service Participant
2
Service Contract
Service Interface
Method
Fire&Forget Method
Property
Event
Service Provider Port
Service Consumer
Port Technology Mapping
Receiver, Sender, Server, Client Ports
AUTOSAR Classic ECU/System
SWC1 SWC3
SWC2
Switch Serialisation/Deserialisation Ethernet
Service Discovery
Sender, Receiver, Client, Server Ports
Technology Mapping
10
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
Service Provider Port
Service Consumer
Port
SOA Diagram in PREEvision 8.0
11
Service Interface and Technology Mapping to AUTOSAR Classic
From Signal Oriented to Service Oriented Architectures
Application SW Component (Service Provider)
Client Server Interface
Sender Receiver Interface
Client Server Interface with GET_ and SET_ operation
Sender Receiver Interface change notification
Sender Receiver Interface
1: Fire and Forget Method = Method without return
2: Property = Field = Attribute
Service Interface
Methods
F&F Methods 1
Properties 2
Events
Event Groups
Service Participant
3
Service Participant
2
Service Contract
Service Interface
Method
Fire&Forget Method
Property
Event
Service Provider Port
Service Consumer
Port Technology Mapping
AUTOSAR Classic ECU/System
SWC1 SWC3
SWC2
Switch Serialization/Deserialization Ethernet
Service Discovery
Technology Mapping
12
Design Workflow for Service Oriented Architectures in AUTOSAR Classic
From Signal Oriented to Service Oriented Architectures
Workflow Folie und ECU-Beispiel (neu)
13
Service Oriented Architectures: Summary
From Signal Oriented to Service Oriented Architectures
u Strengths
u Higher flexibility at run-time
u Services inside and outside the vehicle can be linked
u Extensions and updates of services are possible
u Simplified communication design
u Simplified start-up and shut-down design
u Implementation of complex and open SW architectures (Complex Interfaces, Layers, Remote Procedure Calls, …) possible
u Maintenance and extensions of SW architectures are easier
u Weaknesses
u Predictability of system behaviour (different results of service discovery possible)
u Higher resources for implementation needed (microcontrollers and communication technologies)
u Many different, dynamic system configurations have to be tested
u Customer Benefits
u Flexible, open and dynamic distributed embedded systems
Design-Time Run-Time
Service Oriented Architectures
14
Service Oriented Architectures are Enablers …
u … for Connectivity
u Completely new functions by flexible integration of services in the IT backend
u … for Autonomous Driving
u Communication from the vehicle to the IT backend and vice versa
u Creation of precise maps
u Predictive assistance based on precise maps
u Routing for vehicle fleets in the IT backend
u …
u … for SW Update, SW Upgrade and Service
for Vehicles in the Field
u SW update of single services
u SW update and upgrade for vehicles
in the field Over The Air
u Remote diagnostics
u …
u … for Variant and Building Set Strategies
u 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. Fachkongress Fortschritte in der Automobilelektronik, June 14-15,2016, Ludwigsburg
15
Different Perspectives on Connectivity
From Signal Oriented to Service Oriented Architectures
u Future E/E Architectures
Service Oriented Architectures with AUTOSAR Classic
Service Oriented Architectures with AUTOSAR Adaptive
Summary and Outlook
Agenda
16
Signal Oriented versus Service Oriented Architectures
u Strengths of Service Oriented Architectures
u Higher flexibility at run-time
u Services inside and outside the vehicle can be linked
u Extensions and update of services are possible
u Simplified communication design
u Simplified start up and shut down design
u Implementation of complex and open SW architectures (Complex Interfaces, Layers, Remote Procedure Calls, …) is possible
u Maintenance and extensions of SW architectures are possible
u Customer Benefits
u Flexible, open and dynamic distributed embedded systems
u Strengths of Signal Oriented Architectures
u The complete system is known
u The system behavior is predictable at design time (real time behavior and memory ressources)
u Optimisations regarding resources are possible at design time
(message-based routing, bus scheduling,…)
u Many years of experience
u Many mature components exist
u Customer Benefits
u Predictability of distributed embedded real time systems
u Cost optimised implementation with low resources for microcontrollers and communication technologies
Future E/E Architectures
17
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
u Future E/E architectures will combine the strengths of both:
u Signal Orientation and Service Orientation
u "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
18
© 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
u "Hybrid ECUs" are expected
19
Different Perspectives on Connectivity
From Signal Oriented to Service Oriented Architectures
Future E/E Architectures
u Service Oriented Architectures with AUTOSAR Classic
Service Oriented Architectures with AUTOSAR Adaptive
Summary and Outlook
Agenda
20
SOA Use Cases
Service Oriented Architectures with AUTOSAR Classic
u Introduction of Service Oriented Architectures
u Migration from Signal to Service Oriented Architectures
u Design of Hybrid Architectures in AUTOSAR Classic
Software/Service Architecture
Service Oriented Architecture
SWC Instances
AUTOSAR Classic
SW Library
AUTOSAR Classic
Import
Export
1 2
3
21
SOA Design Workflow
Service Oriented Architectures with AUTOSAR Classic
Software/Service Architecture
Service Oriented Architecture
SWC Instances
AUTOSAR Classic
SW Library
22
Migration from Signal to Service Orientation
Service Oriented Architectures with AUTOSAR Classic
From Signal Orientation … Signals: • WheelSpeed_FR (Signal) • WheelSpeed_FL (Signal) • WheelSpeed_RR (Signal) • WheelSpeed_RL (Signal)
… to Service Orientation: Services: • WheelSpeeds (Service Interface)
• WheelSpeed_FR (Event) • WheelSpeed_FL (Event) • WheelSpeed_RR (Event) • WheelSpeed_RL (Event)
23
Migration from Signal to Service Orientation
Service Oriented Architectures with AUTOSAR Classic
© Dr. Matthias Traub, BMW: Mitten im Umbruch zur Digitalisierung.
Presentation on the 8. Vector Congress, Nov. 29.-30,2016, Stuttgart
24
The complete Vector AUTOSAR Tool Chain
Basic Software (BSW)
RTE
Application Software Development
PREEvision
DaVinci Developer
SWC Design
vVIRTUALtarget pro
SWC Execution and Test
ECU SW Integration
DaVinci Configurator Pro
vVIRTUALtarget basic
BSW/RTE Configuration
Virtual Integration
Application Software Verification
CANoe & VT System
vVIRTUALtarget pro
SWC Verification in Virtual Environment
SWC Verification within Real ECU
AUTOSAR ECU/System
AUTOSAR ECU/System
AUTOSAR ECU
System Design
PREEvision
CANdelaStudio
Architecture and Communication Design
Diagnostics Design
SWC1 SWC3
SWC2
SWC1 SWC3
SWC2
SWC1 SWC2 ECU SW Verification
CANoe.AMD
ECU Monitoring and Debugging
System Verification
CANape
ECU Calibration
CANoe & CANoe.DiVa
Verification of Network Communication and Diagnostic Behavior
Service Oriented Architectures with AUTOSAR Classic
25
AUTOSAR at the System Level
Service Oriented Architectures with AUTOSAR Classic
AUTOSAR Workflow Support
26
Different Perspectives on Connectivity
From Signal Oriented to Service Oriented Architectures
Future E/E Architectures
Service Oriented Architectures with AUTOSAR Classic
u Service Oriented Architectures with AUTOSAR Adaptive
Summary and Outlook
Agenda
27
Manifest
Software/Service Architecture
AUTOSAR Adaptive Support
Service Oriented Architectures with AUTOSAR Adaptive
Service Oriented Architecture
SWC Instances
AUTOSAR Adaptive
SW Library
AUTOSAR Adaptive
Import
Export
1 2
3b
SWC Instances
AUTOSAR Classic
AUTOSAR Classic
Import
Export
3a
Manifest Manifest
28
UML Diagrams
Service Oriented Architectures with AUTOSAR Adaptive
Needed UML Diagrams:
u Use Case Diagram
u SOA Diagram
u Class Diagram
u Sequence Diagram
u State Diagram
VehicleSpeedInterface (Service Interface)
VehicleSpeed (Event)
WheelState (Method)
WheelInterface (Service Interface)
WheelSpeed (Event)
WheelPressure (Method)
SWC Service
Consumer Port
Service Provider Port
AUTOSAR Adaptive Platform
WheelSpeed (Receiver Port)
VehicleSpeed (Sender Port)
WheelPressure (Client Port)
WheelState (Server Port)
AUTOSAR Classic Platform
SWC
Software/Service Architecture
Service Oriented Architecture
SWC Instances
AUTOSAR Classic
SWC Instances
AUTOSAR Adaptive
SW Library
1 2
3a 3b
Service Interface (Class)
Property (Attribute)
Method (Operation())
Method Fire&Forget (Operation())
Event (Operation())
29
Different Perspectives on Connectivity
From Signal Oriented to Service Oriented Architectures
Future E/E Architectures
Service Oriented Architectures with AUTOSAR Classic
Service Oriented Architectures with AUTOSAR Adaptive
u Summary and Outlook
Agenda
30
Enabling Connectivity with Service Oriented Architectures
Summary 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, Stuttgart
31
Enabling Connectivity with Service Oriented Architectures
Summary and Outlook
u Service Oriented Architectures (SOAs) provide flexible, open and dynamic distributed systems
u They are enablers for
u Connectivity and Autonomous Driving
u SW Update, SW Upgrade and Vehicle Service in the field
u New Building Set Strategies and Handling of Variants
u Future E/E Architectures will combine the strengths of Signal Oriented and Service Oriented Architectures
u AUTOSAR Adaptive and AUTOSAR Classic will be deployed in the same vehicle, even in the same ECU
u The introduction of SOAs, the migration to SOAs and their implementation in AUTOSAR Classic are the first steps
u The next steps are:
u Implementation in AUTOSAR Adaptive,
u Hybrid applications of AUTOSAR Adaptive and AUTOSAR Classic, and
u SOA Design with UML Class, Sequence, and State Diagrams
32 © 2017. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V2.0 | 2017-09-21
Your questions are welcome!
Author: Jörg Schäuffele & Iain Cunningham Vector Germany
Top Related