A Language-based Approach to Interoperability of IoT Platforms

Transcription

1 COLLECTOR CoAP TEMPERATURE SENSOR HTTP/FTP/SMTP UDP Set Temperature 70 ºF Get Temperature 68 ºF END TO END PATTERN PUBLISH/SUBSCRIBE PATTERN HVAC COLLECTOR TEMPERATURE SENSOR HVAC TCP/UDP TEMPERATURE SENSOR QoS (0,1 or 2) Subscribe Operation Get Temperature Confirmable GET Request Operation Get Temperature QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish 205 Response QoS (0,1 or 2) Subscribe Confirmable POST Request Ack Response Operation Set Temperature Operation Set Temperature QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish QoS (0,1 or 2) Publih A Language-based Approach to Interoperability of IoT Platforms Stefano Pio Zingaro 1

2 2 The challenge JSON XML CoAP MQTT UDP TCP/UDP 6LowPAN IEEE e IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

3 3 The challenge JSON XML CoAP MQTT UDP TCP/UDP 6LowPAN IPv4/IPv6 IEEE e Data Link Layer Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

4 4 The challenge JSON XML CoAP MQTT UDP TCP/UDP 6LowPAN IEEE e Internet Layer Data Link Layer IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

5 5 The challenge JSON XML CoAP MQTT UDP 6LowPAN IEEE e Transport Layer Internet Layer Data Link Layer TCP/UDP IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

6 6 The challenge JSON XML CoAP UDP 6LowPAN IEEE e Application Layer Transport Layer Internet Layer Data Link Layer MQTT TCP/UDP IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

7 7 The challenge JSON CoAP UDP 6LowPAN IEEE e Data Format Application Layer Transport Layer Internet Layer Data Link Layer XML MQTT TCP/UDP IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

8 8 The challenge JSON Data Format XML IoT ISLANDS PROBLEM CoAP Application Layer MQTT UDP 6LowPAN IEEE e Transport Layer Internet Layer Data Link Layer TCP/UDP IPv4/IPv Ethernet Wireless IoT platforms frequently take the shape of vertical solutions that rely on a single communication technology stack.

9 9 Possible solutions To facilitate the development of IoT applications Low Level Abstractions A. Middlewares B. Smart Gateways (Meshlium, etc.) High Level Abstractions (our approach) C. Integration Frameworks (Eclipse IoT) D. APIs (WoT from W3C)

10 10 Possible solutions To facilitate the development of IoT applications Low Level Abstractions NOT A DEDICATED LANGUAGE! A. Middlewares B. Smart Gateways (Meshlium, etc.) High Level Abstractions (our approach) C. Integration Frameworks (Eclipse IoT) D. APIs (WoT from W3C)

11 11 The proposed solution In order to achieve a better integration we propose a programming language: Programmers can easily change the transport and application protocols (even at runtime!) The language can automatically marshal and unmarshal data formats as required (e.g. HTTP/JSON to CoAP/JSON) The complexity of guaranteeing interoperability among protocols is managed by the programming language

12 12 The challenge JSON CoAP UDP 6LowPAN IEEE e Data Format Application Layer Transport Layer Internet Layer Data Link Layer XML MQTT TCP/UDP IPv4/IPv Ethernet Wireless We focus on integration at the transport and application layer.

13 13 An Example of Interoperability Suppose we want to replace the technology used: Static replacement because of the deployment of new, heterogeneous devices in a pre-existing system. Dynamic replacement to support a changing topology of disparate mobile devices.

14 14 Another Example of Interoperability COAP over UDP TEMPERATURE SENSOR Send Temperature COLLECTOR HTTP over TCP TEMPERATURE SENSOR Send Temperature

15 15 Another Example of Interoperability COAP over UDP TEMPERATURE SENSOR HTTP over TCP TEMPERATURE SENSOR Send Temperature Send Temperature COLLECTOR /* * Unique behavior */ main { receivetemperature( data );

16 16 Another Example of Interoperability COAP over UDP TEMPERATURE SENSOR Send Temperature HTTP over TCP /* TEMPERATURE Send Temperature * Deployment for SENSOR HTTP/TCP */ inputport HTTP_Collector { Location: socket://collector.net:8000 Protocol: http OneWay: receivetemperature( string ) COLLECTOR /* * Unique behavior */ main { receivetemperature( data );

17 17 Another Example of Interoperability COAP over UDP /* TEMPERATURE * Deployment for SENSOR CoAP/UDP */ inputport CoAP_Collector { Location: datagram://local.me:5683 Protocol: coap /* OneWay: receivetemperature( string Send Temperature ) HTTP over TCP /* TEMPERATURE Send Temperature * Deployment for SENSOR HTTP/TCP */ inputport HTTP_Collector { Location: socket://collector.net:8000 Protocol: http OneWay: receivetemperature( string ) COLLECTOR * Unique behavior */ main { receivetemperature( data );

18 18 Another Example of Interoperability COAP over UDP /* TEMPERATURE * Deployment for SENSOR CoAP/UDP */ inputport CoAP_Collector { Location: datagram://coap.me:5683 Protocol: Use coap different /* OneWay: receivetemperature( Receive string Temperature ) communication modalities in a HTTP over TCP /* TEMPERATURE Receive Temperature * Deployment uniform SENSOR HTTP/TCP way */ inputport HTTP_Collector { Location: socket://collector.net:8000 Protocol: http OneWay: receivetemperature( string ) COLLECTOR * Unique behavior */ main { receivetemperature( data );

19 19 Another Example of Interoperability COAP over UDP /* TEMPERATURE * Deployment for SENSOR CoAP/UDP */ inputport CoAP_Collector { Location: datagram://coap.me:5683 Protocol: Use coap different /* OneWay: receivetemperature( Receive string Temperature ) communication modalities in a HTTP over TCP /* TEMPERATURE Receive Temperature * Deployment uniform SENSOR HTTP/TCP way */ inputport HTTP_Collector { Location: socket://collector.net:8000 Protocol: http OneWay: receivetemperature( string ) * Unique behavior */ main { COLLECTOR Easily switch between them receivetemperature( data );

20 20 The JIoT Project Main Contribution Integrating IoT related technologies into the Jolie Service Oriented Programming Language: The Publish/Subscribe communication pattern The MQTT Application Layer protocol The UDP Transport Layer protocol The CoAP Application Layer protocol

21 21 MQTT integration in Jolie 1. Publish/Subscribe communication paradigm Adding a generic publish/subscribe meta-channel that bridges between end-to-end style of communications and publish/subscribe interactions. 2. Message Queue Telemetry Transport (MQTT) Encoding/Decoding MQTT messages (Netty based)

22 22 CoAP and UDP integration in Jolie 1. User Datagram Protocol (UDP) Adding Listener and Sender classes based on Netty Extend the semantic to support un-reliable communications 2. Constrained Application Protocol (CoAP) Encoding/Decoding CoAP messages (ncoap based)

23 23 JIoT Interpreter Last Release of the interpreter can be found at: Requires JRE 1.8+ Download jiot jar Open a console and run: java -jar jiot jar

24 24 JIoT Sources JIoT is an open source project developed as an extension to Jolie The sources for the project can be found at:

25 Recap The Service Oriented Paradigm Everything is a service A service is an application that offers functionalities through operations A service can invoke another service by calling one of its operations Slide by Saverio Giallorenzo Stefano Pio Zingaro 25

26 26 Recap What is Jolie? A Service-Oriented Programming Language Service-Oriented Object-Oriented Services Objects Operations Methods Slide by Saverio Giallorenzo

27 27 Deployments Enabling Communications

28 Communication Ports in Deployments Services communicate through Ports Ports give access to an Interface Interface be a set of Operations An Output Port is used to invoke interfaces exposed by other services Stefano Pio Zingaro 28 An Input Port is used to expose an interface Slide by Saverio Giallorenzo

29 29 A closer look on ports - Protocols A protocol defines the format in which the data is sent (encoded) and received (decoded) In Jolie protocols are described by names and possibly some parameters:

30 30 Behaviours Composing Interactions

31 31 Interactions via Operations oneway( req ) Input Operations reqres( req )( res ){ // code block Output Operations oneway@port( req ) reqres@port( req )( res ) Slide by Saverio Giallorenzo

32 32 Case Study Smart Home Example TEMPERATURE SENSOR COLLECTOR Get Temperature 68 ºF Set Temperature 70 ºF HVAC

33 33 Case Study Smart Home Example End to end communication using CoAP over UDP TEMPERATURE SENSOR COLLECTOR HVAC Operation Get Temperature Confirmable GET Request 205 Response Confirmable POST Request Ack Response Operation Set Temperature

34 Case Study Smart Home Example Publish/Subscribe communication using MQTT over TCP COLLECTOR TEMPERATURE SENSOR BROKER HVAC QoS (0,1 or 2) Subscribe QoS (0,1 or 2) Subscribe Operation Get Temperature QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish QoS (0,1 or 2) Publish QoS QoS(0,1 (0,1oror2)2)Subscribe Publih Operation Set Temperature Stefano Pio Zingaro QoS (0,1 or 2) Publih QoS (0,1 or 2) Publish 34

35 Case Study Smart Home Example /* * Lets define a common interface for the * different equipped thermostats, * using the same operations */ interface ThermostatInterface { OneWay: settemp( int ) RequestResponse: gettemp( void )( int ) Stefano Pio Zingaro 35

36 Case Study Smart Home Example /* * The common behaviour */ main { gettemp@thermostat( )( temp ); if ( temp > 81 ) { settemp@thermostat( 75 ) else if ( temp < 59 ) { settemp@thermostat( 72 ) Stefano Pio Zingaro 36

37 37 Case Study Smart Home Example /* REQUEST-RESPONSE pattern * The Outbound final, RequestResponse common behavior communications */ send a message and wait for a reply. main { gettemp@thermostat( )( temp ); if ( temp > 81 ) { settemp@thermostat( 75 ) else if ( temp < 59 ) { settemp@thermostat( 72 )

38 38 Case Study Smart Home Example /* ONE-WAY pattern * The final, common behavior */ Outbound OneWay communications main { send a message asynchronously. gettemp@thermostat( )( temp ); if ( temp > 81 ) { settemp@thermostat( 75 ) else if ( temp < 59 ) { settemp@thermostat( 72 )

39 Case Study Smart Home Example /* * Lets define a common interface for the * different equipped thermostats, * using the same operations */ interface ThermostatInterface { OneWay: settemp( int ) RequestResponse: gettemp( void )( int ) Stefano Pio Zingaro 39

40 40 Case Study Smart Home Example outputport Coap_Thermostat { Location: "datagram://localhost:5683" Protocol: coap {.osc.gettemp << {.contentformat = "text/plain",.alias = "/gettemperature",.messagecode = GET" ;.osc.settemp << {.contentformat = "text/plain",.alias = "/settemperature",.messagecode = "POST" Interfaces: ThermostatInterface

41 Case Study Smart Home Example outputport Mqtt_Thermostat { Location: socket://iot.eclipse.org:1883 Protocol: mqtt {.osc.gettemp << {.alias = "gettemperature",.qos = 2 ;.osc.settemp << {.alias = "settemperature",.qos = 2 Interfaces: ThermostatInterface Stefano Pio Zingaro 41

42 42 A special thanks to the SPACES team Image by Saverio Giallorenzo so long, and thanks for all the fish