benefit
play

benefit Architectures for the future of notifications in the IoT - PowerPoint PPT Presentation

In collaboration with IoT Notifications: from disruption to benefit Architectures for the future of notifications in the IoT Supervisor(s) Presenter Fulvio Corno Teodoro Montanaro Pino Castrogiovanni Research GOAL Investigate the


  1. In collaboration with IoT Notifications: from disruption to benefit Architectures for the future of notifications in the IoT Supervisor(s) Presenter Fulvio Corno Teodoro Montanaro Pino Castrogiovanni

  2. Research GOAL Investigate the intelligence component in Internet of Things (IoT) architectures and applications: study, define, and prototype intelligent distributed architectures that may extract additional value and intelligent behaviors to some significant sample problems, representative of future IoT scenarios. The distribution and customization of notifications in the IoT domain has been treated as an example of possible future IoT scenarios. 2

  3. Notification Context: sample scenario Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 3

  4. Notification Context: sample scenario Date : 9 th September 2018 Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 4

  5. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 5

  6. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 5 people: Mum : is preparing the washing machine Dad : is reading a newspaper Clara : is using her pc on her bedroom John : is working on his PC Frank : is working out on the tapis roulant Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 6

  7. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 5 people: Mum Dad Clara John Frank Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 7

  8. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 Various IoT 5 people: devices Mum Dad Clara John Frank Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 8

  9. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 Various IoT 5 people: devices Mum Dad Events: Clara 1. Cleaning John robot battery Frank is low 2. Frank stops to play sport Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 9

  10. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 Various IoT 5 people: devices Mum Notifications Dad Events: Clara 1. Cleaning John robot battery Frank is low 2. Frank stops to play sport Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 10

  11. Notification Context: sample scenario Date : 9 th September 2018 Time : 19.00 Various IoT 5 people: devices Mum Dad Clara John Frank https://me.me/ Source: https://iot.do/windstream-research-future-connected-home-community-2015-04 11

  12. Main problem Notifications could be disruptive: • Wrong moment • Wrong device on which the notification is shown • Wrong modality (e.g., vibration instead of sound) • Wrong person (s) • Repetitive notifications • Too many simultaneous notifications • … 12

  13. Notification Context: sample scenario Simplified version (used as a reference) Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services

  14. Main Research GOAL Design and develop new IoT architectures to a) enhance the effect of IoT notifications on users experience b) allow developers to effectively exploit the notifications improving their services, tools and applications. Notifications 14

  15. Proposed solutions Two different approaches are possible 1. At the distribution level : notifications are intercepted as soon as they arrive on the IoT devices and then systems decide if, when, and how to show them. Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services 15

  16. Proposed solutions Two different approaches are possible 1. At the distribution level : notifications are intercepted as soon as they arrive on the IoT devices and then systems decide if, when, and how to show them. Solution: Smart Notification System (SNS) SNS Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services 16

  17. Proposed solutions Two different approaches are possible 2. At the design level : notifications are designed with the aim of reducing user disruption. Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services 17

  18. Proposed solutions Two different approaches are possible 2. At the design level : notifications are designed with the aim of reducing user disruption. Solution : XDN (Cross Device Notifications) framework XDN XDN Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services 18

  19. Smart Notification System (SNS) 19

  20. SNS Smart Notification System (SNS): a modular architecture to deal with notifications at the distribution level. It uses machine learning algorithms to manage incoming notifications according to context awareness and users habits . Our contributions: 1. Architecture design 2. Prototypes implementation of different architectural components SNS Notification Generator Notifications Notifications IoT Sensors / Dervices / Notified Cloud Services People Services 20

  21. SNS: Architecture Overview: Online Services IoT IoT (e.g., Twitter) notifications notifications SMART NOTIFICATION NOTIFICATION SYSTEM COLLECTOR Environment User Context Context Converted information information Notifications USER (IN) ENVIRONMENT USER HABITS CONTEXT CONTEXT COLLECTORS COLLECTORS User DECISION MAKER context Environment context ENVIRONMENT USER Converted CONTEXT CONTEXT Notifications ANALYSIS ANALYSIS + LABELS (OUT) DISPATCHER 21

  22. SNS: Architecture 22

  23. SNS: Architecture A modular architecture aware of 23

  24. SNS: Architecture A modular architecture aware of Environment status (e.g., weather information, current date and time) 24

  25. SNS: Architecture A modular architecture aware of Environment status User context (e.g., (e.g., weather location, status, information, current current activity), date and time) 25

  26. SNS: Architecture A modular architecture aware of Environment status User context (e.g., (e.g., weather location, status, User habits information, current current activity), (e.g., usual lunch time) date and time) 26

  27. SNS: Architecture A modular architecture aware of Environment status User context (e.g., (e.g., weather location, status, User habits information, current current activity), (e.g., usual lunch time) date and time) Decision maker: makes decisions on who should receive the notification, best moment, best devices and best modalities (including actuation) to present notifications. 27

  28. SNS: Architecture How can we map our use case? 28

  29. SNS: Architecture How can we map our use case? 29

  30. SNS: Prototypes 1. The Decision Maker contribution: 3. The Context Analysis group of contributions a) Decision maker prototype a) Location Estimator 2. The Collectors group of contributions: a) IoT Collector server b) Mobile Collector c) SmartHome Collector d) SmartCity Collector 30

  31. SNS: Prototypes 1. The Decision Maker contribution: 3. The Context Analysis group of contributions a) Decision maker prototype a) Location Estimator 2. The Collectors group of contributions: a) IoT Collector server b) Mobile Collector c) SmartHome Collector d) SmartCity Collector 31

  32. SNS: 1. Decision Maker Prototype Objective : demonstrate that Machine Learning algorithms can be adopted to the IoT notifications domain Contribution : Preliminary version of the Decision maker module Context Information to be used by the ML algorithm: Notification information to be used by the ML algorithm: 32

  33. SNS: 1. Decision Maker Prototype Objective : demonstrate that Machine Learning algorithms can be adopted to the IoT notifications domain Contribution : Preliminary version of the Decision maker module Context Information to be used by the ML algorithm: Used dataset Synthetic information Notification information to be used by the ML algorithm: 33

  34. SNS: 1. Decision Maker Prototype Objective : demonstrate that Machine Learning algorithms can be adopted to the IoT notifications domain Contribution : Preliminary version of the Decision maker module Tests: 3 different machine learning algorithms adopted over an existing dataset • (MIT): Support Vector Machine, Gaussian Naïve Bayes and Decision Trees . Used dataset Synthetic information Used tools 34

  35. SNS: 1. Decision Maker Prototype Objective : demonstrate that Machine Learning algorithms can be adopted to the IoT notifications domain Contribution : Preliminary version of the Decision maker module Tests: Main outcome 3 different machine learning algorithms adopted over an existing dataset • (MIT): Support Vector Machine, Gaussian Naïve Bayes and Decision Trees . - The three algorithms behave as expected : Used dataset DT works better than the others due to the • programmatic approach used to generate synthetic information Synthetic Almost all the algorithms obtain an high level of • information accuracy, precision and recall - ML is promising technique to enhance the effect of IoT Used tools notifications on users experience 35

Recommend


More recommend