Your SlideShare is downloading. ×
A SOA for the car - 01/2009
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

A SOA for the car - 01/2009

151

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
151
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. A SOA for the carRoland Tritsch, Solutions Architect, IONA Technologies
  • 2. 2Agenda• Introduction – Sharing observations – Motivate the problem• Discuss a possible solution – Service Oriented Architectures – WebServices Definition Language – Shortcomings• Summary – Q&A
  • 3. 3Embedded SWE: Quo vadis?• The conventional way of embedded SWE has reached its limits – Informatik-Spectrum, Broy Mechatronic• Mechatronic alone is probably not able to fix it• But combining it with already proven concepts, Embedded Application standards and tools from SWE SWE the application SWE domain might lead to the required quantum leap in productivity
  • 4. 4
  • 5. 5Current situation
  • 6. 6Current situation ! ! " "# ! "$ %& " ! " " !$ ! " ! " ! "$ Effort
  • 7. 7Resulting challenges• Development – Software Quality • Testing – Reuse• Production – Update/Upgrade • Versioning – Configuration • UPNP – Diagnoses
  • 8. 8The solution ! ! " "# ! "$ ??? %& " ! " " !$ ! " ! " ! "$
  • 9. 9What’s missing?• Abstraction ! ! " "# ! "$ – A way to define abstract interfaces between the services ???• Standards %& " ! " " !$ – Standards to describe these interfaces ! " ! " ! "$
  • 10. Objects, components and services Scope Services Components Objects Granularity
  • 11. 11SOA Primer Registry 2. Lookup Repository 1. Register C C o o n (Virtual) Bus n Requester t t Provider r r a 3. Interact a c c t t
  • 12. 12A SOA for the car ECU S S ECU ECU S Contract Contract Contract ( ) " ! ! " " ! " Contract Contract Contract ECU S ECU S ECU S
  • 13. 13What do you need?• A way to access T&P independent the services• A way to define Service Access the services• A virtual bus – ESB, EMI, … Service Definition• Transport and protocol independence• Based on Service Bus (open) standards
  • 14. 14What do you need?• A way to access T&P independent the services• A way to define the services (W)SIF Service Access• A virtual bus – ESB, EMI, … (W)SDL Service Definition• Transport and protocol independence• Based on CAN, MOST,Bus Service FLEX, … (open) standards
  • 15. 15(W)SDL might be a good canditate % # $ " ! !
  • 16. 16 The Service Definition Language• WSDL is/got famous for its SOAP over HTTP binding• But WSDL is Open and Extensible – Extensibility allows non-SOAP bindings (see below) – Extensibility allows service policies to be defined in contracts too• Already existing non-SOAP/HTTP bindings – Transports • MQ, Tuxedo, Tibco, CORBA, IIOP, HTTP/S – Protocols • XML, Fixed Format, FML (Tuxedo), TibRvMsg, G2++• Service Policies – Routing, Failover, Security, Transactions, etc.
  • 17. 17WSDL Extensors !"" # # "$ "$ " ! !""$$$ $% "& "()* "()* # !*+,- ./0 !"" # # " # " " ! # !"" # # "$ " # " ! # 12 !"" # # # " # " # 12 ! !"" # # "1 " ! !"" # " ! !"" # " # /# # !"" # "
  • 18. 18“Und was ist mit ECUs?”• ECUs send and receive messages as % # $ telegrams "• Every telegram is fixed ! in size and format• Means we need something like a fixed binding !• We also need a transport (e.g. CAN bus)
  • 19. 19WSDL Extensors !"" # # "$ " ! !""$$$ $% "& "()* # !*+,- ./0 !"" # # " # " " ! # !"" # # "$ " # " ! # 12 !"" # # # " # " # 12 ! !"" # # "1 " ! !"" # " ! !"" # " # /# # !"" # "
  • 20. 20Fixed Format Binding1 # 32 4# # 3 5 ! 32 1 4# # 5 !1 " # # ! # # # 6 " 2 !1 5 ! # # 6 7# 2 1 + 5 2 " ! # # 8 & " ! # # 8 & " " !1 5 " 2 " #"1
  • 21. 21CAN Port Extensor # 32 4# # * # 32 4# # - 1 ! 32 1 4# # 3 # 12 ! # 2 1 &9 2 # 9 # 7 2# 2 9" ""
  • 22. 22 Summary• Integrating an increasing number of ECUs will become one of the major challenges for the automotive industry• Applying concepts, standards and tools from the application SWE domain might help – E.g. Middleware, CORBA, WebServices• WSDL might be a good candiate as a universal service description language to describe the services in a car – But there are also (still) a lot of shortcomings• WSIF is complementary to WSDL and provides a means to access the services in a uniform way
  • 23. 23Thank You &Questions

×