1. Developing Complex Services in an IoT Ecosystem Charilaos Akasiadis, Grigorios Tzortzis, Evaggelos Spyrou, and Constantine Spyropoulos Institute of Informatics and Telecommunications N.C.S.R. “Demokritos”, Athens, Greece

2. Introduction Internet of things - Web of things ◦Integration of physical objects with the world wide web ◦New business models (fulfill varying customer needs at real-time, personalized offers) ◦Certain advantages (monitoring, effective management, human-robot collaborations) ◦Most probably: IoT is the technology that will drive the future Developing Complex Applications in an IoT Ecosystem 2

3. Introduction We examine how to: ◦Easily develop and deploy complex applications/services ◦Using already existing, simpler services ◦Utilizing an Internet of Things platform ◦Show case: Person counting module for smart rooms Developing Complex Applications in an IoT Ecosystem 3

4. Outline  SYNAISTHISI IoT Platform  Smart meeting room ontology  Discovery, Interconnection, Delivery  Use case: Person counting module from simpler services Developing Complex Applications in an IoT Ecosystem 4

5. The SYNAISTHISI Platform Developing Complex Applications in an IoT Ecosystem 5

6. The SYNAISTHISI Platform  Everything is a Service :  (S)ensing Services  Temperature sensors  Cameras  Consumption meters  …  (A)ctuating Services  Speakers  Plug Switches  Motors  … Developing Complex Applications in an IoT Ecosystem 6  (P)rocessing Services  Audio Analyzers  Image Processors  Decision Makers  … CO, CO 2 levels Anomaly Detectio n Activate Alarm S P A

7. The SYNAISTHISI Platform Developing Complex Applications in an IoT Ecosystem 7 o Layered Architecture o Bidirectional communication among layers o Seamless interconnection between heterogeneous modules

8. Smart Meeting Room Ontology Domain specific ontology, built by combining and extending IoT-A, SSN, QU, and QUDT Resource Model (excerpt) Developing Complex Applications in an IoT Ecosystem 8

9. Smart Meeting Room Ontology Domain specific ontology, built by combining and extending IoT-A, SSN, QU, and QUDT Service Model (excerpt) Developing Complex Applications in an IoT Ecosystem 9

10. Discovery, Interconnection, Delivery Developing Complex Applications in an IoT Ecosystem 10

11. Discovery, Interconnection, Delivery  Given the user’s application blueprint  Query the system registry for available services of the requested type  Type refers to location and functionality  SPA piping process  Define an identifier for each service  Describe data flows between services Developing Complex Applications in an IoT Ecosystem 11 SELECT ?motiondetect_res ?motiondetect_serv WHERE { ?motiondetect_res rdf:type MotionDetectionResource. ?motiondetect_res isExposedThroughService ?motiondetect_serv. ?motiondetect_serv hasServiceArea Area1. ?motiondetect_serv hasServiceOutput ?motiondetect_out. ?motiondetect_out rdf:type MotionDetection.

12. Developing Complex Applications in an IoT Ecosystem 12 Use Case: Person Counting App

13. Data flows and interconnection Developing Complex Applications in an IoT Ecosystem 13

14. SPARQL Queries for SPA discovery Developing Complex Applications in an IoT Ecosystem 14 Use Case: Person Counting App RGB-D Cameras, S-type Services Person Counting Module, P-type Service

15. Energy monitoring and management Safety and surveillance Healthcare Smart rooms/buildings/cities Traffic management systems Developing Complex Applications in an IoT Ecosystem 15 Lots More Use-Cases

16. Conclusions  IoT and WoT technologies can be used for complex applications development  Construction is made easy by using integrated, less complex services  No additional expertise required from the developer’s side  New business models arise FUTURE WORK: ◦Automatic complex service composition approaches ◦Customizable, user friendly GUIs, secure protocols ◦NLP approaches to make service discoverability and piping even easier Developing Complex Applications in an IoT Ecosystem 16

17. Conclusions  IoT and WoT technologies can be used for complex applications development  Construction is made easy by using integrated, less complex services  No additional expertise required from the developer’s side  New business models arise FUTURE WORK: ◦Automatic complex service composition approaches ◦Customizable, user friendly GUIs, secure protocols ◦NLP approaches to make service discoverability and piping even easier Developing Complex Applications in an IoT Ecosystem 17 Thank you! …questions?