Protocol Interconnection in Urban Traffic Coordination use case - PowerPoint PPT Presentation

Protocol Interconnection in Urban Traffic Coordination use case (demo) Georgios Bouloukakis Inria 1 st Review Meeting Brussels, February 11, 2016

Route planning: Choreography diagram Specification Specification sub-choreography diagram raffic Specification raffic Specification 2 afikv affic afikv affic “+” flo “+” “+” “x”): (simplified affic flo affic “+” affic “x”): (simplified affic simplified affic affic defin first “Send Destination”, simplified “Send nation” =” ” ” ” ” ” defin first “Send Destination”, “Send nation” =” ” ” ” ” ”

Route planning: Service coordination ND TRVC DTS-HERE BS-MAP Legend 1. ND 2. BS-MAP 3. DTS-GOOGLE DTS-GOOGLE 4. DTS-HERE DTS-TRV-ACC 5. TRVC 6. DTS-TRV-ACC Web Services calls 3

Route planning: BS-MAP to DTS-GOOGLE DTS GOOGLE BS-MAP GET /directions/{origin}/{destination}  BS-Map interacts using the SOAP protocol  DTS-GOOGLE interacts using the REST protocol  The eVolution Service Bus (VSB) enables the interconnection of services running on different protocols 4

5

VSB Architecture 6

Steps to interconnect BS-MAP and DTS- GOOGLE services (1) (2) The Synthesis Processor interacts to the VSB Manager providing: Service Interface description (3) (4) war artifact 7

BS-MAP to DTS-GOOGLE BC DTS GOOGLE BS-MAP SOAP REST <service name="BindingComponent"> "operation": { requestRoute (origin, dest) “type": " two_way", <soap:address location= "role": “server”, "http://localhost:8888/BindingComponent"/> "scope": ” GET /directions/{origin}/{dest} ” , </service> "get_data ”: “ origin ”, “ destination ” <operation name="routeRequest"> <input …. /> "post_data ": ” Route ” <output …. /> …. </operation> …. 8

Route planning: Service coordination using the BC ND TRVC DTS-HERE BS-MAP BC Legend 1. ND 2. BS-MAP 3. DTS-GOOGLE DTS-GOOGLE 4. DTS-HERE DTS-TRV-ACC 5. TRVC 6. DTS-TRV-ACC Web Services calls 9

10