Leveraging Multi Domain Links via the Internet of Things Towards horizontal integration of vertical pilots A. Andrushevich, B. Copigneaux, R. Kistler, A. Kurbatski, F. Le Gall, A. Klapproth rusmart 2013, 28.08.2013, St. Petersburg, Russia
Agenda Introduction Defined horizontal scenario Security and privacy considerations Development objectives Validation targets IoT system overview IoT application example Conclusion 2
Introduction Recent automation resulted in numerous specialized ICT solutions and systems in different domains Internet of Things (IoT) vision targets interdisciplinary system scalable to all areas of human activity Differences in logic processes and standards imped compatibility and interoperability BUTLER offers a context aware 24/7 information endusers support solution based on IoT integrated Home, Transport, Health and Shopping scenarios 3
Introduction: domain centric ICT solutions SmartTransport SmartShopping - Monitoring and controlling - Promoting carpooling - Managing sparkdeals - Saving energy comfortably - Minimizing taxi delays - Getting advice on buying goods - Interacting with appliances - Avoiding traffic jams! - Retrieving discount SmartHome - SmartHealth - Monitoring medicine intake - Personalized diabetes assistance - Providing training tips - - SmartCity - - Managing parking space - Lighting up a city efficiently - Monitoring Air Quality - 4
Daisy and Donald: Smart Life scenario personas Donald is 51 years old, works at a bank and is married with Daisy. They have 2 children. They live in a nice house in the suburbs and also own a chalet in the mountains. Donald enjoys eating out, despite his food allergies and he is interested in energy efficiency. Daisy is 45 years old, a housewife, part time shop assistant. She is married to Donald, has 2 children. Daisy suffers from diabetes, tries to do fitness regularly and likes shopping with her friends. She is glad that machines support her in her household tasks. They are about to go skiing for a long weekend. BUTLER supports them in managing it. 5
BUTLER Smart Life horizontal scenario Presents the horizontal context aware and secure vision Horizontality is a complementary data exchange between application domains generating the added value through availability of the non core information. Horizontal scenario is a conceptual target and a basis for Proof of Concepts, Field Trials and Business Cases 6
From domain centric apps to Smart Life scenario Smart Mobility Transport Smart Health Wellness Smart Home Office Smart Shopping Smart City Vertical UCs Vertical UCs Vertical UCs Vertical UCs Vertical UCs Aggregate results from Verticals Smart Live Concept: Horizontal Story Line incl. Personas Business Requirements IoT Butler 7
BUTLER Smart Life horizontal scenario 8
BUTLER Smart Life horizontal scenario solutions SmartLife 9
Security and privacy considerations in IoT 1. Main objective: user controls/manages its profile Static and Dynamic Distributed User Profile 2. Applications use/update Application 1 Application 2 10
Security and privacy considerations in IoT Horizontal IoT services are based on personal behavioral data causing the following security and privacy concerns: Sensibility of user data: IoT applications gather lots of data revealing daily behavior if analyzed on a large scale Security of user data: IoT communication complexity / number of to be protected links grows exponentially User data storage and management by service provider Ownership and sharing of data control and revenue Data captivity: what happens if user leaves the service Availability / quality of information and presentation 11
Security and privacy considerations in IoT Ethical concerns lead to the Privacy Paradox trading off between personalized services vs. identifying user profile. Privacy by Design treats privacy as ethics of knowledge: Transparency data usage: explicit user consent Adequate, relevant and not excessive collected data Collector shall use data for explicit purpose Collector shall protect data at communication level Collector shall protect collected data at data storage Collector shall let user access / remove personal data 12
Development objectives Horizontal cross domain exploitation of the IoT enabled applications consists of the following activities: Creating enabling technologies of secure, pervasive, context aware IoT where smart environments are monitored, learned, adjusted to user needs in real time Integrating / developing a new flexible 6LoWPAN / IPv6 / RESTful network architecture when devices function in 3roles: smart Object (sensors, actuators, gateways), smart Mobile (user s personal device) and smart Server (providers of contents and services) Building a series of field trials(home, Transport, Health) 13
Development objectives: methodology BUTLER IoT horizontality methodology starts from evaluating and validating the requirements of different applications not based on a similar architecture/platform: Smart Home energy awareness, LBS multimedia; Smart Health personalized assistive users lifestyle Smart City public parking reservation / management Smart Shopping dynamic context aware pricing, deals Smart Transport improved safety in public transport and continues with integration and cross domain exploitation of IoT enabling technologies between domains 14
Validation targets (1) Validation target Values Description Technical feasibility Feasible now Feasible in less than 3 years Feasible in more than 3 years Not feasible until 2020 Field Trial aims to validate if the proposed IoT solution, service or application can be technically implemented using a state of the art technology set today or within the next years to come Technology integration Open for integration Open data formats only Standard communication protocols only Integration hardly possible Field Trial aims to validate if the proposed IoT solution, service or application is ready for integration into the IoT ecosystem including data formats and communication protocols Deploymen t efforts Low Remote automatic Feasible Remote semiautomatic Considerable Onsite semiautomatic High Onsite manual Field Trial aims to validate if the proposed IoT solution, service or application can be easily deployed Maintenan ce efforts Low Remote automatic Feasible Remote semiautomatic Considerable Onsite semiautomatic High Onsite manual Field Trial aims to validate if the proposed IoT solution, service or application can be easily maintained 15
Validation targets (2) Validation target Values Description Scalability > 1 000 000 connected nodes 100 000 1 000 000 connected nodes 10 000 100 000 connected nodes 1 000 10 000 connected nodes < 1 000 connected nodes Field Trial aims to validate if the proposed IoT solution, service or application can be scaled to a large amount of nodes User experience / comfort / perception User friendly, simple, secure, reliable, privacy driven User affine Any three properties Limited Any two properties Very limited Any property Field Trial aims to validate if the proposed IoT solution, service or application attracts with a welldesigned user experience User acceptance High Daily usage Considerable Weekly usage Borderline Monthly usage Low Less than monthly usage Field Trial aims to validate if the proposed IoT solution, service or application is widely accepted 16
IoT system overview 17
IoT system overview: Communications Application 1 Application 2 Application N Application/Data Layer OneM2M/ETSI M2M Service Layer HTTP CoAP SEP 2.0 Transport Layer ZigBee TCP TCP/UDP Network Layer RPL 6LoWPAN IPv6 Data Link Layer Physical Layer IEEE 802.15.4 Bluetooth 4.0 Low Energy RFID/NFC Wi Fi 3GPP 18
BUTLER IoT applications methodology The BUTLER story Proof of Concepts 3 x Vertical Proof of Concepts (M12) 1st Horizontal Proof of Concepts (M24) 2nd Horizontal Proof of Concepts (M36) Trials 3 x Vertical Trials (M12 M24) 1 x Horizontal Trial (M24 M36) 19
IoT application example 20
IoT application example: GUI 21
Conclusion IoT will integrate / interconnect isolated specific domains like Smart Transport, Smart Health, Smart Shopping, Smart Home and Smart City. Goal: added value generation in the context aware 24 / 7 information support for end users through availability of the non core information. Contributions: Validation and measurement methodology for IoT pilots. Architectural system overview of technological enablers / security and privacy concerns within IoT. Concrete IoT application example in Smart Home. 22
Connect with BUTLER www.iot butler.eu: Learn about BUTLER Follow progresses Partnerships BUTLER on social networks: Twitter: https://twitter.com/#!/iotbutler LinkedIn: http://www.linkedin.com/groups/butler 4205902 23
ihomelab: Location For Project Reviews 24
Thank you! Alexey.Andrushevich@iHomeLab.ch 25
Butler keeps Donald informed about the energy consumption according to the weather and other conditions and gives him advice what is the best to do.
SmartHome: Energy Awareness ihomelab, STMicro, Ericsson, Telecom Italia 27
...the news continues exactly at the point where Donald stopped watching them in the living room. 28
SmartHome Media everywhere The multimedia follows the user in the house 29
Daisy checks her blood sugar level, she also takes a look at the measurement history of the last week and the data of her step counter (fit bit). BUTLER suggests more sports and fewer sweets
SmartHealth: Diabetes Diary KU Leuven, ihomelab 31
Technical Achievement 32
Technical Achievement Efficiency and effectivenesstrade off analysis Recognition accuracy, computational complexity, communication overhead and latency, power consumption, storage, 33
Daisy is notified by Butler that the boots she has long looked for are available at a very good price. She decides to pick them up, because Butler can help her find and reserve a parking place near the shop.
Street Perspective 35
SmartCity Smart Parking TST,TIL 36
Donald s tablet suddenly buzzes. Someone stands at the door of his home back in the city. Donald shortly opens the door and lets postman enter the home with the packet. Later he sees him leaving the house and BUTLER notifies door locked again.
Das verknüpfte Bild kann nicht angezeigt werden. Möglicherweise wurde die Datei verschoben, umbenannt oder gelöscht. Stellen Sie sicher, dass die Verknüpfung auf die korrekte Datei und den korrekten Speicherort zeigt. Das Bild kann zurzeit nicht angezeigt werden. SmartTransport ZigPos, JUB 38