Enabling Connectivity with Service Oriented Architectures

Transcription

1 Enabling Connectivity with Service Oriented Architectres Vector GB Conference 2017 V

2 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 2

3 Different Perspectives on Connectivity New Vehicle Fnctions and Services with Connectivity The IT Backend Perspective The Vehicle Perspective The Bsiness Perspective The Technical Perspective 3 Ricky Hdi, Adi AG: Die Atomobilindstrie im (radikalen) Umbrch, 20. Intern. Fachkongress Fortschritte in der Atomobilelektronik, Jne 14-15,2016, Ldwigsbrg

4 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 4

5 From Signal Oriented to Service Oriented Architectres Characteristics of Signal Oriented Architectres Distribted systems with signal-based commnication Between SW components and Signal Oriented Architectres Between ECUs Many decisions are done at design time: Design-Time Rn-Time Binding of SW components Commnication design: Signal, PDU, Frame and Schedle Design The complete system is known and considered at design time ("Closed static distribted system") Distribted SW architectre is based on SW Components with sender/receiver commnication AUTOSAR Classic is a matre, widely-accepted and sed implementation platform Implementation in C AUTOSAR Classic ECU/System AUTOSAR Classic ECU AUTOSAR Classic ECU SWC2 Sender Data Element Receiver SWC1 SWC2 RTE SWC3 RTE SWC1 SWC3 Basic Software (BSW) Basic Software (BSW) Signal 5 Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Atonomos Vehicles, Presentation on the 8. Vector Congress, Nov , 2016, Stttgart

6 From Signal Oriented to Service Oriented Architectres Design Workflow for Signal Oriented Architectres in AUTOSAR Classic Software Architectre Hardware Architectre 6

7 From Signal Oriented to Service Oriented Architectres Signal Oriented Architectres - Smmary Strengths The complete system is known The system behavior is predictable at design time (real-time behavior and memory resorces) Optimisations regarding resorces are possible at design time (message-based roting, bs schedling, ) Weaknesses Low flexibility at rn-time. The system cannot be easily extended after design-time High design and test efforts > For commnication (Signals, PDUs, Frames and Schedles) > For start-p and sht-down behavior of the distribted system (network management, ) No spport for more complex SW architectres (SW components with only Sender/Receiver Interfaces are sed) Cstomer Benefits Predictability of distribted embedded real-time systems Cost-optimised implementation with low resorces for microcontrollers and commnication technologies Signal Oriented Architectres Design-Time Rn-Time 7

8 From Signal Oriented to Service Oriented Architectres Characteristics of Service Oriented Architectres Distribted systems with service-based commnication Between SW components and Service Oriented Architectres Between ECUs Important decisions are done at rn-time, not at design-time! Design-Time Rn-Time Binding (by service discovery) Commnication is dynamic (e.g. dynamic PDU content transmitted sing serialisation and deserialisation) "Open system": Services can be added at rn-time (e.g. otside the vehicle) The SW Architectre is designed with SW components with service interfaces AUTOSAR Adaptive as implementation platform crrently in specification Implementation in C++ AUTOSAR Adaptive ECU/System SWC2 Service Provider Service Interface Service Consmer bt AUTOSAR Classic can also be sed as an implementation platform for Service Oriented Architectres SWC1 SWC3 8 Switch Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Atonomos Vehicles, Presentation on the 8. Vector Congress, Nov , 2016, Stttgart

9 From Signal Oriented to Service Oriented Architectres What is a Service? Service Interface Method Fire&Forget Method Property Event Technology Mapping Service Participant 2 Service Provider Port Service Contract Service Consmer Port Service Participant 3 Technology Mapping SWC1 AUTOSAR Adaptive ECU/System SWC2 Service Provider Service Consmer SWC3 Technology Mapping Technology Mapping SWC1 AUTOSAR Classic ECU/System SWC2 Sender, Receiver, Client, Server Ports Receiver, Sender, Server, Client Ports SWC3 9 Service Discovery Serialisation/Deserialisation Switch Ethernet Service Discovery Serialisation/Deserialisation Switch Ethernet

10 From Signal Oriented to Service Oriented Architectres What is a Service? Service Interface Method Fire&Forget Method Property Event SOA Diagram in PREEvision 8.0 Service Participant 2 Service Provider Port Service Contract Service Consmer Port Service Participant 3 10

11 From Signal Oriented to Service Oriented Architectres Service Interface and Technology Mapping to AUTOSAR Classic Service Participant 2 Service Interface Service Provider Port Method Fire&Forget Method Property Event Service Contract Service Consmer Port Technology Mapping SWC1 Service Participant 3 Service Discovery Serialization/Deserialization Technology Mapping AUTOSAR Classic ECU/System SWC2 Switch SWC3 Ethernet Service Interface Methods F&F Methods 1 Properties 2 Events Event Grops 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 11 1: Fire and Forget Method = Method withot retrn 2: Property = Field = Attribte

12 From Signal Oriented to Service Oriented Architectres Design Workflow for Service Oriented Architectres in AUTOSAR Classic Workflow Folie nd ECU-Beispiel (ne) 12

13 From Signal Oriented to Service Oriented Architectres Service Oriented Architectres: Smmary Strengths Higher flexibility at rn-time Services inside and otside the vehicle can be linked Extensions and pdates of services are possible Simplified commnication design Simplified start-p and sht-down design Implementation of complex and open SW architectres (Complex Interfaces, Layers, Remote Procedre Calls, ) possible Maintenance and extensions of SW architectres are easier Design-Time Service Oriented Architectres Rn-Time Weaknesses Predictability of system behavior (different reslts of service discovery possible) Higher resorces for implementation needed (microcontrollers and commnication technologies) Many different, dynamic system configrations have to be tested Cstomer Benefits Flexible, open and dynamic distribted embedded systems 13

14 From Signal Oriented to Service Oriented Architectres Service Oriented Architectres are Enablers for Connectivity Completely new fnctions by flexible integration of services in the IT backend for Atonomos Driving Commnication from the vehicle to the IT backend and vice versa Creation of precise maps Predictive assistance based on precise maps Roting for vehicle fleets in the IT backend for SW Update, SW Upgrade and Service for Vehicles in the Field SW pdate of single services SW pdate and pgrade for vehicles in the field Over The Air Remote diagnostics 14 for Variant and Bilding Set Strategies SW options can be implemented as services (base service premim service) Ricky Hdi, Adi AG: Die Atomobilindstrie im (radikalen) Umbrch, 20. Intern. Fachkongress Fortschritte in der Atomobilelektronik, Jne 14-15,2016, Ldwigsbrg

15 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 15

16 Ftre E/E Architectres Signal Oriented verss Service Oriented Architectres Strengths of Service Oriented Architectres Strengths of Signal Oriented Architectres Higher flexibility at rn-time The complete system is known Services inside and otside the vehicle can be linked Extensions and pdate of services are possible Simplified commnication design Simplified start p and sht down design Implementation of complex and open SW architectres (Complex Interfaces, Layers, Remote Procedre Calls, ) is possible The system behavior is predictable at design time (real time behavior and memory ressorces) Optimisations regarding resorces are possible at design time (message-based roting, bs schedling, ) Many years of experience Many matre components exist Maintenance and extensions of SW architectres are possible Cstomer Benefits Cstomer Benefits Flexible, open and dynamic distribted embedded systems Predictability of distribted embedded real time systems Cost optimised implementation with low resorces for microcontrollers and commnication technologies 16

17 Ftre E/E Architectres Signal Oriented or Service Oriented Architectres? Signal Oriented Architectre Service Oriented Architectre Either or? Signal Oriented Architectre Service Oriented Architectre as well as! Ftre E/E architectres will combine the strengths of both: Signal Orientation and Service Orientation Ricky Hdi, Adi AG: Die Atomobilindstrie im (radikalen) Umbrch, 20. Intern. Fachkongress Fortschritte in der Atomobilelektronik, Jne 14-15,2016, Ldwigsbrg Service Oriented Architectre IT Backend Vehicle ECU 13 ECU 14 ECU 15 "Hybrid architectres" are expected ECU 1 ECU 2 ECU 7 ECU 8 ECU 3 ECU 4 ECU 9 ECU ECU 5 ECU 6 ECU 11 Signal Oriented Architectre ECU 12

18 Ftre E/E Architectres Signal Oriented or Service Oriented Architectres? "Hybrid ECUs" are expected 18 Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Atonomos Vehicles, Presentation on the 8. Vector Congress, Nov ,2016, Stttgart

19 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 19

20 Service Oriented Architectres with AUTOSAR Classic SOA Use Cases Introdction of Service Oriented Architectres Migration from Signal to Service Oriented Architectres Design of Hybrid Architectres in AUTOSAR Classic Software/Service Architectre Service Oriented Architectre SW Library 1 2 SWC Instances AUTOSAR Classic 3 Import Export AUTOSAR Classic 20

21 Service Oriented Architectres with AUTOSAR Classic SOA Design Workflow Software/Service Architectre Service Oriented Architectre SW Library SWC Instances AUTOSAR Classic 21

22 Service Oriented Architectres with AUTOSAR Classic Migration from Signal to Service Orientation 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) 22

23 Service Oriented Architectres with AUTOSAR Classic Migration from Signal to Service Orientation 23 Dr. Matthias Trab, BMW: Mitten im Umbrch zr Digitalisierng. Presentation on the 8. Vector Congress, Nov ,2016, Stttgart

24 Service Oriented Architectres with AUTOSAR Classic The complete Vector AUTOSAR Tool Chain System Design Architectre and Commnication Design Diagnostics Design PREEvision CANdelaStdio AUTOSAR ECU/System SWC2 SWC1 SWC3 ECU Calibration System Verification CANape Verification of Network Commnication and Diagnostic Behavior CANoe & CANoe.DiVa Application Software Development AUTOSAR ECU/System Application Software Verification SWC Design PREEvision DaVinci Developer SWC1 SWC2 SWC3 SWC Verification within Real ECU CANoe & VT System SWC Exection and Test BSW/RTE Configration Virtal Integration vvirtualtarget pro ECU SW Integration DaVinci Configrator Pro vvirtualtarget basic AUTOSAR ECU SWC1 SWC2 RTE Basic Software (BSW) SWC Verification in Virtal Environment vvirtualtarget pro ECU SW Verification ECU Monitoring and Debgging CANoe.AMD 24

25 Service Oriented Architectres with AUTOSAR Classic AUTOSAR at the System Level AUTOSAR Workflow Spport 25

26 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 26

27 Service Oriented Architectres with AUTOSAR Adaptive AUTOSAR Adaptive Spport Software/Service Architectre Service Oriented Architectre SW Library 1 2 SWC Instances SWC Instances AUTOSAR Classic 3a AUTOSAR Adaptive 3b Import Export Import Export AUTOSAR Classic AUTOSAR Adaptive Manifest Manifest Manifest 27

28 Service Oriented Architectres with AUTOSAR Adaptive UML Diagrams AUTOSAR Classic Platform WheelSpeed (Receiver Port) WheelPressre (Client Port) SWC VehicleSpeed (Sender Port) WheelState (Server Port) Needed UML Diagrams: Use Case Diagram SOA Diagram Class Diagram Seqence Diagram Software/Service Architectre Service Oriented Architectre SWC Instances AUTOSAR Classic SW Library 1 2 3a SWC Instances AUTOSAR Adaptive 3b AUTOSAR Adaptive Platform State Diagram Service Consmer Port SWC Service Provider Port WheelInterface (Service Interface) WheelSpeed (Event) WheelPressre (Method) VehicleSpeedInterface (Service Interface) VehicleSpeed (Event) WheelState (Method) 28 Service Interface Property Method Method Fire&Forget Event (Class) (Attribte) (Operation()) (Operation()) (Operation())

29 Agenda Different Perspectives on Connectivity From Signal Oriented to Service Oriented Architectres Ftre E/E Architectres Service Oriented Architectres with AUTOSAR Classic Service Oriented Architectres with AUTOSAR Adaptive Smmary and Otlook 29

30 Smmary and Otlook Enabling Connectivity with Service Oriented Architectres Software/Service Architectre Service Oriented Architectre SW Library 1 2 SWC Instances AUTOSAR Classic 3a SWC Instances AUTOSAR Adaptive 3b 30 Simon Fürst, AUTOSAR Steering Committee: The AUTOSAR Adaptive Platform for Connected and Atonomos Vehicles, Presentation on the 8. Vector Congress, Nov , 2016, Stttgart

31 Smmary and Otlook Enabling Connectivity with Service Oriented Architectres Service Oriented Architectres (SOAs) provide flexible, open and dynamic distribted systems They are enablers for Connectivity and Atonomos Driving SW Update, SW Upgrade and Vehicle Service in the field New Bilding Set Strategies and Handling of Variants Ftre E/E Architectres will combine the strengths of Signal Oriented and Service Oriented Architectres AUTOSAR Adaptive and AUTOSAR Classic will be deployed in the same vehicle, even in the same ECU The introdction of SOAs, the migration to SOAs and their implementation in AUTOSAR Classic are the first steps The next steps are: Implementation in AUTOSAR Adaptive, Hybrid applications of AUTOSAR Adaptive and AUTOSAR Classic, and SOA Design with UML Class, Seqence, and State Diagrams 31

32 Yor qestions are welcome! Athor: Jörg Schäffele & Iain Cnningham Vector Germany Vector Informatik GmbH. All rights reserved. Any distribtion or copying is sbject to prior written approval by Vector. V