Arrowhead Protocol Translation

Transcription

1 1 Arrowhead Protocol Translation IPSO Protocol committee March 10 th 2016 Webex lhasan Derhamy lluleå tekniska universitet

2 Overview of presentation Briefly introduce Arrowhead project and framework Introduce the topic of protocol interoperability, our perspective. Arrowhead Protocol Translation Service Translation?

3 Introducing Arrowhead Four year Artemis Innovation Project from Now in final year Pilot demonstrations at IECON2016 in Florence More Information at Arrowhead website 81 partners including Schneider Electric, Airbus, AVL, Ford, Infineon, NXP, ST, Thales, and many more industry and academic institutions. Pilot areas in Production, Electro-mobility, Virtual Market of Energy, Smart Buildings and Infrastructure, Energy Production and End Users Services.

4 Introducing Arrowhead Service Oriented Architecture based framework for integrating multi-vendor applications

5 Motivation??? JSON JSON HTTP XML XMPP EXI IPSO SenML IPSO BSON SenML XML HTTP XML HTTP JSON MQTT XML MQTT Broker BSON MQTT EXI MQTT

6 Middleware? More and more Internet based applications Service Oriented Architecture is promising Centralized software buses or static protocol adaptors/bridges used in closed systems.

7 Gateway or proxy? Sit at edge of network Forced to segregate total network into sub-networks Gateway HTTP HTTP Still acting similar to middleware Overhead in network setup, configuration and change

8 Recap what interoperability in Arrowhead means! Service contract = specific set of documents System P Service A Service A Contract System C A CP A SD A IDD A SP

9 Arrowhead Service Contract Interoperability Service A contract using HTTP Service A* contract using System P Service A Service A Contract A CP A SD A IDD A SP Contract Miss-match!! Service A* Service A* Contract A* CP A SD A* IDD A SP System C

10 Arrowhead Service Contract Interoperability Arrowhead translator can help to bridge the contract miss-match! System P Service A Service A Contract A CP A SD A IDD A SP Translator Service A* Service A* Contract A* CP A SD A* IDD A SP System C

11 Transparency!! Use Orchestration to make translation transparent! Zero-Configuration!! Orchestration System System Consumer 4 Translator 5 System Producer

12 Arrowhead Translator Arrowhead Core Service Registry Orchestration - Authorization HTTP Translator HTTP HTTP Translator XMPP

13 Arrowhead Translation Architecture

14 Message API - Initialization Users: Orchestrator to setup the translator and receive the fully defined service endpoint. <translatorsetup> <serviceproviderdnssdrecord> </serviceproviderdnssdrecord> <serviceconsumertype> </serviceconsumertype> </translatorsetup>

15 Message API Initialization Possible future Make use of a Service Inventory which will hold much more detail regarding the Service Contract [ServiceDescription/ InterfaceDesignDescription/ CommunicationProfile/ SemanticProfile] <translatorsetup> <serviceproviderdnssdrecord> </serviceproviderdnssdrecord> <serviceconsumertype> </serviceconsumertype> <serviceinventoryreferences> <provider> </provider> <consumer> </consumer> </serviceinventoryreferences> </translatorsetup>

16 Message API - Usage Users: Service consumer systems Can interact with this API as the original Service Contract

17 Arrowhead Translation Architecture

18 Architecture cont. Translator Service Hub 1 Hub 2 Hub N

19 Intermediary Format Key unique identifier assigned by Hub Payload UTF-8 payload to be sent (no translation of payload) Payload type To be passed onto the translated payload Method HTTP method enumeration Object This can be URL path, topic, or chat room Error Intermediate error codes

20 Conclusion and future work This work has delivered: 1) Defined a concept for increasing Service Interoperability without middleware 2) Produced an open-source prototype with design documentation Future work: 1) Implement an Orchestrator which can utilize the Translation System 2) Implement capability for XMPP Spoke 3) Any pilots would like to integrate with other pilots running a different communication protocol??

21 Thank you for your time! Hasan Derhamy Doktorand EISLAB LTU