Towards End-to-end Data Exchange in the IoT Georgios Bouloukakis - - PowerPoint PPT Presentation

towards end to end data exchange in the iot
SMART_READER_LITE
LIVE PREVIEW

Towards End-to-end Data Exchange in the IoT Georgios Bouloukakis - - PowerPoint PPT Presentation

Donald Bren School of Information & Computer Sciences Towards End-to-end Data Exchange in the IoT Georgios Bouloukakis Joint work with Nikolaos Georgantas, Valerie Issarny, Pierre-Guillaume Raverdy, Patient Ntumba, Andrew Chio & Nalini


slide-1
SLIDE 1

CPS & IoT seminar @ USC, Sept 2019

Towards End-to-end Data Exchange in the IoT

Georgios Bouloukakis

Joint work with Nikolaos Georgantas, Valerie Issarny, Pierre-Guillaume Raverdy, Patient Ntumba, Andrew Chio & Nalini Venkatasubramanian

Donald Bren School of Information & Computer Sciences

UC Irvine, Computer Science Department, USA

slide-2
SLIDE 2

Enabling Data Exchange in IoT Smart Spaces

2

Dynamic Heterogeneous

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

“what is the occupancy of the room 2065? “decrease the temperature of those rooms with occupancy above 50% of their capacity?”

slide-3
SLIDE 3

Most recent research

3 Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

IoT application Handling heterogeneity at the middleware-layer

Functional semantics DeXMS Mediators

Handling heterogeneity at the application-layer

Data model

  • Dev. Code

Wrappers/ Virtual Sensors

Automated placement of artifacts at the Edge

IoT Space Model Interaction Constraints Optimized Placement

Enabling a semantic vision of IoT spaces

User Requests Translation Execution Plans

  • Perf. evaluation of heterogeneous interactions

QoS Semancis Analytical models Statistical Analysis Simulated models

Enabling Efficient Event Prioritization over SDN

Situational Awareness SDN Prioritization

  • Band. Allocation

QoS analysis

slide-4
SLIDE 4

IoT heterogeneity at multiple layers

4

CoAP

Physical layer Data Link layer (MAC & LLC) Network layer Transport Layer Middleware layer Application layer Physical layer Data Link layer (MAC & LLC) Network layer Transport Layer Middleware layer Application layer

IP

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-5
SLIDE 5

Middleware protocols in the mobile IoT

5

DPWS CoAP MQTT ZeroMQ WebSockets …. Client-server Pub/sub Streaming ….

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-6
SLIDE 6

Heterogeneous interconnections in the mobile IoT

6

Protocol X Protocol Y

Yannis

 How to enable interconnections in the mobile IoT ?

Bridging middleware protocols Convergence to a single protocol Convergence to a single protocol Relying on a service bus Providing common API abstractions Providing common API abstractions

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

Bluetooth beacon

slide-7
SLIDE 7

Our proposed solution

7

Protocol Y Protocol X

systematic solution to interoperability systematic solution to deployment

Yannis

  • push-based
  • resource
  • pub/sub
  • topic

functional semantics e.g. CoAP server e.g. MQTT subscriber

Automated synthesis of interoperability artifacts:

  • enables functional middleware-layer interoperability

Automated placement and deployment at the Edge:

  • enables the deployment of interoperability artifacts at the Edge

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

Bluetooth beacon

slide-8
SLIDE 8

Models for core interaction paradigms

8

Client–Service (CS)

  • Tight Time & Space Coupling

Publish-Subscribe (PS)

  • Time & Space Decoupling

client server subscriber broker publisher subscriber

Data Streaming (DS)

  • Tight Time & Space Coupling

Tuple Space (TS)

  • Time & Space Decoupling

consumer producer reader tspace writer taker

  • ne-way

two-way sync or async

  • ne-way

two-way stream two-way stream two-way sync

  • ne-way

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-9
SLIDE 9

Data eXchange (DeX) connector model

9

  • Our generic connector defines 4 basic interaction types:
  • ne-way

two-way async two-way sync two-way stream

each interaction is represented as combination of post and get primitives post and get primitives abstract CS, PS, DS and TS primitives

We rely on the DeX abstraction to introduce

  • ur middleware protocol interoperability solution

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-10
SLIDE 10

common protocol

Our middleware protocol interoperability solution

10

  • Data eXchange Mediator Synthesizer (DeXMS)1,2

bluetooth beacon PS Protocol X DS Protocol Y

ACCEPT data PUBLISH event

Mediator 1 Mediator 2

 Mediator architecture: relies on DeX for automated Mediator synthesis  Primitives & data conversion between the common protocol and the Things’ protocols  A universal way to describe the Things’ I/O required

Protocol X Protocol Y

DeX connector A DeX connector C DeX connector B

common protocol

Convertion logic Convertion logic

mobile app

1 G. Bouloukakis et al., FGCS, 2019 2 G. Bouloukakis et al., ICSOC, 2016

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-11
SLIDE 11

Automated Mediator synthesis

11

  • Generic Interface Description Language (DeXIDL) & Generic Mediator

"protocol": “MQTT”, "operations": { "operation_1": { "type": "stream", "role": “consumer", “interaction_type”:”one_way” "scope": “get_occupancy", "input_data" : “capacity,room" } }

Mediator synthesizer

Generic Mediator

Generic

  • ne-way

logic xmget

  • n_get

post

DeX connector X DeX connector Y

DeX API

<< Protocol Pool >>

MQTT CoAP DPWS

… Concrete Mediator

Data conversion logic receive publish REST MQTT

1 2 3 4

REST (common protocol)

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-12
SLIDE 12

The Where and How Problem

12 Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

  • Where to place mediators: Cloud, Edge, and Fog Computing
  • Obvious solution: The Edge and Fog
  • Things push data to the cloud to be analyzed (e.g., 4k camera)
  • Use artifacts at the Edge/Fog to filter these data
  • Timeliness, data privacy, etc

IoT Edge Cloud

  • Work in progress:
  • Systematic solution to automate the deployment of mediators at the Edge
  • Utilize this solution to deploy mediators and other artifacts in the I3 platform
slide-13
SLIDE 13

Mediators at the Edge

13 Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

DeXMS

  • Delivers software in packages

called containers.

  • DeXMS provides mediators as

Dockerfiles.

  • A Dockerfile produces a Docker

image.

Docker Ansible Ansible Kubernetes

  • Automation tool to perform

installation, maintenance, or monitoring operations.

  • Used to automate the installation
  • f the smart space infrastructure

as well the DeXMS service.

  • Triggers the DeXMS service to

generate the required Mediator containers.

  • Can be used to monitor nerworks

and services.

  • Container-orchestration system

for automated deployment, scaling, and management.

  • Supports the automated

deployment of mediators.

slide-14
SLIDE 14

The How Problem

14 Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

  • How to place mediators?
  • Related Problem: Operator Placement
  • Compute a “cost space”1 to represent Things and Physical Nodes
  • E.g., a smart building with heterogeneous Things
  • Place mediators in an optimized manner

N N N T T T T T T T T T M

1 P. Pietzuch et al., ICDE, 2006

M

Criteria: distance, energy, bandwidth, latency, availability, etc Optimization techniques2,3: constraint programming solvers, heuristics, linear programing, genetic programming, etc.

2 V. Issarny et al., ICDCS, 2019 3 A. Chio et al., ARM, 2019

slide-15
SLIDE 15

DeXMS novelty

15

MQTT Camera CoAP WiFi AP REST Mediator

MQTT CoAP

Mediator

CoAP REST

  • Lightweight architecture
  • Mediators employed only when necessary
  • Any common protocol
  • Support for any protocol classified under CS, PS, DS & TS
  • Evolution support
  • Automated Mediator synthesis
  • 75-96 % person-hours reduction when using DeXMS
  • Work in progress: enabling application-layer data exchange1

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

1 R. Yus et al., Buildsys, 2019

Bluetooth beacon

MQTT

slide-16
SLIDE 16

Software artifacts and adoption

16

  • DeXMS is part of the zefxis1 platform (https://gitlab.inria.fr/zefxis):
  • Mediator generator: https://gitlab.inria.fr/zefxis/DeXMS
  • Eclipse plugin for defining Things’ DeXIDLs: https://gitlab.inria.fr/zefxis/DeX-IDL
  • Web console: https://gitlab.inria.fr/zefxis/IoT-web-console
  • Demos:
  • Mediator generation: https://youtu.be/UgfM3810RS8 (ICSOC 2016)
  • Web console installation: https://youtu.be/IGjZ5u3QYOw (ICWE 2018)
  • Fire Detection scenario: https://youtu.be/SJeiqJkBhls (ICWE 2018)
  • DeXMS is used as a core component in H2020 CHOReVOLUTION, UCI

TIPPERS and Inria/UCI MINES projects.

1zefxis in ancient Greek (ζεῦξις) means connection or coupling

slide-17
SLIDE 17

Publications

17

  • G. Bouloukakis, N. Georgantas, P. Ntumba, V. Issarny, "Automated Synthesis of

Mediators for Middleware-layer Protocol Interoperability in the IoT", FGCS Journal, 2019.

  • R. Yus, G. Bouloukakis, S. Mehrotra, N. Venkatasubramanian, “Abstracting

Interactions with IoT Devices Towards a Semantic Vision of Smart Spaces”, ACM Buildsys, November 2019, New York, USA

  • V. Issarny, B. Billet, G. Bouloukakis, D. Florescu, C. Toma, “LATTICE: A Framework for

Optimizing IoT System Configurations at the Edge”, ICDCS 2019, July 2019, Dallas, Texas, USA

  • A. Chio, G. Bouloukakis, C.H. Hsu, S. Mehrotra, N. Venkatasubramanian. “Adaptive

Mediation for Data Exchange in IoT Systems”, 18th ARM Workshop 2019, Davis, CA, USA

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis

slide-18
SLIDE 18

Thank you!

Towards End-to-end Data Exchange in the IoT – Georgios Bouloukakis