A SOA for the car - 01/2009Presentation Transcript
A SOA for the carRoland Tritsch, Solutions Architect, IONA Technologies
2Agenda• Introduction – Sharing observations – Motivate the problem• Discuss a possible solution – Service Oriented Architectures – WebServices Definition Language – Shortcomings• Summary – Q&A
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
9What’s missing?• Abstraction ! ! " "# ! "$ – A way to define abstract interfaces between the services ???• Standards %& " ! " " !$ – Standards to describe these interfaces ! " ! " ! "$
Objects, components and services Scope Services Components Objects Granularity
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
12A SOA for the car ECU S S ECU ECU S Contract Contract Contract ( ) " ! ! " " ! " Contract Contract Contract ECU S ECU S ECU S
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
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(W)SDL might be a good canditate % # $ " ! !
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.
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)
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