IoT Mashup as a Service: Cloud-based Mashup Service for the Internet of Things By: Benny Bazumnik Lidor Otmazgin Date: 21/05/14

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Mashup  Iot environment provides the human with many useful services.  Mashup, a way to compose new things from existing services, is expected to play an important role in these cases because people have different use cases and preferences.  Mashup in IoT environment is possible if each thing exposes its functionalities as a web service.

Why do we need Mashups  To increase agility by supporting dynamic assembly and configuration of applications.  To speed up the development.  To reduce development costs through lightweight integration, reuse and sharing.  To foster innovation by unlocking and remixing information in ways not originally planned for

Motivation  Large number of devices, and their heterogeneity and availability.  Web services from devices in IoT environment are heterogeneous depending on the function of the service.  Web services may not be available all the time.  Amount of computation resource changes according to data with is produced by things and processing algorithm. Therefore, applying current web mashup technology may not be possible in IoT environment. Challenges

IoT Mashup as a Service  A definition of thing model, software model and computational resource model.  Three components can be customized depending on end users’ preference.  This model relieves heterogeneity of devices, bringing interoperability among devices and mashup service.

IoT Service Cloud  Consists of three components:  Thing configuration  Software component assembly  Allocation of cloud resource.  It is designed to be an ecosystem reflecting business roles of the real world stakeholders.

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

IoT Mashup as a Service Model Platform Independent Model

An Example of instantiated IoTMaaS

SDO – Super Distributed Object Example: IP camera.  sdoID: urn:epc:id:sgtin: (EPC)  sdoType: ipcamera  status: heading direction Device Profile  deviceType: IP camera  manufacturer: LG  model: LW130W  version: 1.0 Service Profile  serviceID  interfaceType: camera, microphone

CCM – CORBA Component Model  Common Object Request Broker Architecture.  A standard designed to facilitate the communication of systems.  CORBA enables collaboration between systems on different operating systems, programming languages, and computing hardware.

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Definitions  Service Planner (SP) – a professional service designer, defines the IoTMaaS Template.  IoTMaaS Instantiation Client (IC) – a non-professional end user client.  Frontend Service (FS)  Service Deployer (SD)

Definitions – cont’d  Thing Profile Service (TPS) – services provided by the thing, it includes serviceID, interfaceType, etc.  Thing Identifier Service (TIDS) – service that provides lookup mechanism for retrieving address of TPS.  IoT Service Instance (SI) – service that collects and processes the data from things to notify the service client.  Thing Cluster Service (TCS) – used for discovery and availability check.

An Architecture to serve IoTMaaS

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Thing Cluster and Discovery Service  Ways to manage things:  Centralized  Distributed  Hierarchical  Each thing has it own controller (TC)  Controllers are registered to the TDS

Thing Metadata Retrieval and Service Composition Static information maintained by the manufacturer and need to be shared:  Product information  Thing service driver (TSD)

Steps to compose IoT Service  The architecture composes the IoT service in 5 stages: Stage 1:  IC defines the IoTMaaS template by the SP  IC specifies the amount of computing resources. Stage 2:  FS checks availability of things Stage 3:  FS sends the composition request to SD SD role:  Prepares the SWCs  Uses the TIDS to prepare the TSD and to retrieve the thing address

Steps to compose IoT Service - cont’d Stage 4:  SD composes IoTMaaS Instance  It generates archive files which include:  Assembly description, TSDs, SWCs, Thing Address, parameters  SD sends deployment command to CCM Stage 5:  IoTMaaS instance starts working  Getting data from things  Process data  Notify UI or actuate the things

Towards an Ecosystem  Each part of the system can charge other parts for it services.  For example: SC can charge IC the usage of the IoTMaaS.

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Implementation IoT Service Cloud Platform

Implementation – cont’d Things:  Three LG IP cameras  Manufacturer didn’t provided TSDs  No GPS internal component Software:  Vacancy Detection software Vacant Room Detection Scenario

IoTMaaS Application Scenario

A prototype Service UI VM configuration Mashup service configuration

Agenda  Introduction  Mashup definition  Motivation  IoT Service Cloud  IoT Mashup as a Service Model  An Architecture to serve IoTMaaS  Services  Implementation  Conclusion

Conclusion  We described a cloud-based mashup service in IoT environment.  A composition of: things, software and computing resource.  The contribution of the model to the heterogeneity of devices.  The platform works as an ecosystem.

Thank you for listening!