Slide 1

Slide 1 text

Semantic Tuple Spaces for Constrained Devices: A Web-compliant Vision Aitor Gómez Goiri gomezgoiri.net June 16, 2014

Slide 2

Slide 2 text

Outline 1. Introduction 2. Hypothesis 3. Space model 4. Search architecture 5. Actuation 6. Conclusions

Slide 3

Slide 3 text

Introduction

Slide 4

Slide 4 text

Background Introduction

Slide 5

Slide 5 text

Background Introduction

Slide 6

Slide 6 text

Background Introduction

Slide 7

Slide 7 text

Background Introduction

Slide 8

Slide 8 text

Background Introduction

Slide 9

Slide 9 text

Background: UbiComp Introduction

Slide 10

Slide 10 text

Background: UbiComp Introduction

Slide 11

Slide 11 text

UbiComp, challenge 1: dynamism Introduction

Slide 12

Slide 12 text

UbiComp, challenge 1: dynamism Introduction

Slide 13

Slide 13 text

UbiComp, challenge 1: dynamism Introduction

Slide 14

Slide 14 text

UbiComp, challenge 1: dynamism Introduction

Slide 15

Slide 15 text

UbiComp, challenge 1: proposed solution Introduction

Slide 16

Slide 16 text

UbiComp, challenge 2: heterogeneity Introduction

Slide 17

Slide 17 text

UbiComp, challenge 2: heterogeneity Introduction The IEEE defines interoperability as The ability of two or more systems or components to exchange information and to use the information that has been exchanged.

Slide 18

Slide 18 text

UbiComp, challenge 2: heterogeneity Introduction The IEEE defines interoperability as The ability of two or more systems or components to exchange information and to use the information that has been exchanged.

Slide 19

Slide 19 text

UbiComp, challenge 2a: use info Introduction

Slide 20

Slide 20 text

UbiComp, challenge 2a: proposed solution Introduction

Slide 21

Slide 21 text

UbiComp, challenge 2b: exchange info Introduction The IEEE defines interoperability as The ability of two or more systems or components to exchange information and to use the information that has been exchanged.

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

Why the Web? Introduction > UbiComp, challenge 2b: exchange info

Slide 24

Slide 24 text

Why the Web? Introduction > UbiComp, challenge 2b: exchange info

Slide 25

Slide 25 text

UbiComp, challenge 2b: exchange info Introduction

Slide 26

Slide 26 text

Summary: Solutions for UbiComp challenges Introduction

Slide 27

Slide 27 text

State-of-the-art Motivation

Slide 28

Slide 28 text

Common design: delegate semantic provision Motivation

Slide 29

Slide 29 text

Common design: delegate semantic provision Motivation

Slide 30

Slide 30 text

Common design: delegate semantic provision Motivation

Slide 31

Slide 31 text

"Short" or "limited" are relative adjectives Motivation

Slide 32

Slide 32 text

Delegation of semantic provision: Problem 1 Motivation

Slide 33

Slide 33 text

Delegation of semantic provision: Problem 1 Motivation

Slide 34

Slide 34 text

Delegation of semantic provision: Problem 1 Motivation

Slide 35

Slide 35 text

Delegation of semantic provision: Problem 1 Motivation

Slide 36

Slide 36 text

Delegation of semantic provision: Problem 1 Motivation

Slide 37

Slide 37 text

Delegation of semantic provision: Problem 1 Motivation

Slide 38

Slide 38 text

Delegation of semantic provision: Problem 2 Motivation

Slide 39

Slide 39 text

Delegation of semantic provision: Problem 2 Motivation

Slide 40

Slide 40 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 41

Slide 41 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 42

Slide 42 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 43

Slide 43 text

Goals 1. Space model 2. Search architecture 3. Actuation mechanism

Slide 44

Slide 44 text

Outline 1- Introduction 2- Hypothesis 3 - Space model 4- Search architecture 5- Actuation 6- Conclusions

Slide 45

Slide 45 text

Space model [CHB2014] Lightweight semantic framework for interoperable ambient intelligence applications [WoT2012] RESTful Triple Spaces of Things [IEEESensors2011] Collaboration of Sensors and Actuators through Triple Spaces. [WoT2011] On the complementarity of Triple Spaces and the Web of Things.

Slide 46

Slide 46 text

Space model s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . TSC HTTP API s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . asteroid 1 s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . asteroid N OSAPI Outer space Coordination space OSAPI ... coordinator Analysis: Networking properties Coordination properties Is it for limited devices?

Slide 47

Slide 47 text

Networking properties Space model

Slide 48

Slide 48 text

Networking properties Space model

Slide 49

Slide 49 text

Networking properties Space model

Slide 50

Slide 50 text

Networking properties Space model

Slide 51

Slide 51 text

Networking properties Space model

Slide 52

Slide 52 text

Networking properties Space model REST-like APIs Scalability Simplicity User perceived performance Efficiency Evolvability

Slide 53

Slide 53 text

Time uncoupling Coordination properties Space model Space uncoupling

Slide 54

Slide 54 text

Time uncoupling Coordination space ✔ ✔ Coordination properties Space model Space uncoupling

Slide 55

Slide 55 text

Time uncoupling Coordination space ✔ ✔ Outer space ✔ Coordination properties Space model Space uncoupling

Slide 56

Slide 56 text

Time uncoupling Coordination space ✔ ✔ Outer space ✔ X Coordination properties Space model Space uncoupling

Slide 57

Slide 57 text

Properties for UbiComp Space model

Slide 58

Slide 58 text

Properties for UbiComp Space model

Slide 59

Slide 59 text

Outline 1- Introduction 2- Hypothesis 3 - Space model 4- Search architecture 5- Actuation 6- Conclusions

Slide 60

Slide 60 text

Energy-aware search architecture [IJWGS2014] Energy-aware architecture for information search in the semantic web of things. [IMIS2012] Assessing data dissemination strategies within triple spaces on the web of things.

Slide 61

Slide 61 text

Problem: in the context of this PhD Energy-aware search architecture How to search in the outer space? s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . TSC HTTP API s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . asteroid 1 s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . s1 p1 o1 . s2 p2 o2 . s3 p3 o3 . asteroid N OSAPI Outer space Coordination space OSAPI ... coordinator

Slide 62

Slide 62 text

Problem: a generalization Energy-aware search architecture

Slide 63

Slide 63 text

Problem: a generalization Energy-aware search architecture

Slide 64

Slide 64 text

Energy consumption: an example Energy-aware search architecture Platform FoxG20 RAM Memory 64 MB CPU 400 MHz Atmel ARM9

Slide 65

Slide 65 text

Energy consumption: an example Energy-aware search architecture

Slide 66

Slide 66 text

Roles Energy-aware search architecture

Slide 67

Slide 67 text

Roles Energy-aware search architecture

Slide 68

Slide 68 text

Roles Energy-aware search architecture

Slide 69

Slide 69 text

Roles Energy-aware search architecture

Slide 70

Slide 70 text

Roles Energy-aware search architecture

Slide 71

Slide 71 text

Roles Energy-aware search architecture

Slide 72

Slide 72 text

Clues Energy-aware search architecture

Slide 73

Slide 73 text

Clues Energy-aware search architecture

Slide 74

Slide 74 text

Clues Energy-aware search architecture

Slide 75

Slide 75 text

Clues Energy-aware search architecture

Slide 76

Slide 76 text

Clues Energy-aware search architecture

Slide 77

Slide 77 text

Clues Energy-aware search architecture

Slide 78

Slide 78 text

Clues Energy-aware search architecture

Slide 79

Slide 79 text

Clues Energy-aware search architecture

Slide 80

Slide 80 text

Clue content Energy-aware search architecture

Slide 81

Slide 81 text

Clue content Energy-aware search architecture

Slide 82

Slide 82 text

Clue content Energy-aware search architecture

Slide 83

Slide 83 text

Clue content Energy-aware search architecture

Slide 84

Slide 84 text

Clue content Energy-aware search architecture

Slide 85

Slide 85 text

Discovery Energy-aware search architecture Using a discovery mechanism each node shares: 1. the Spaces it belongs to, 2. whether it is White Page (+ its setup version) 3. information for the White Page selection process

Slide 86

Slide 86 text

White page selection Energy-aware search architecture

Slide 87

Slide 87 text

White page selection Energy-aware search architecture

Slide 88

Slide 88 text

White page selection Energy-aware search architecture

Slide 89

Slide 89 text

White page selection Energy-aware search architecture

Slide 90

Slide 90 text

White page selection Energy-aware search architecture

Slide 91

Slide 91 text

White page selection Energy-aware search architecture

Slide 92

Slide 92 text

White page selection Energy-aware search architecture

Slide 93

Slide 93 text

Experimental environment: simulation inputs Energy-aware search architecture

Slide 94

Slide 94 text

Experimental environment: simulation inputs Energy-aware search architecture AEMET metereological dataset University of Luebeck Wisebed Sensor Readings Kno.e.sis Linked Sensor Data Bizkaisense

Slide 95

Slide 95 text

Compared strategies Energy-aware search architecture

Slide 96

Slide 96 text

Evaluation: Network activity Energy-aware search architecture

Slide 97

Slide 97 text

Evaluation: Network activity (by device type) Energy-aware search architecture seconds seconds

Slide 98

Slide 98 text

Evaluation: Network activity (high dynamism) Energy-aware search architecture

Slide 99

Slide 99 text

Summary Energy-aware search architecture The presented search architecture cares about computation (C) and energy (E), because: Management tasks are delegated to the most powerful devices in the space (C+E) The search is improved avoiding many unnecessary requests (C+E) If the Provider cannot process the aggregated clue, it can delegate it on the WP (C) The WP selection process prioritizes cases where less providers are forced to resend their last clue version (E).

Slide 100

Slide 100 text

Summary Energy-aware search architecture

Slide 101

Slide 101 text

Outline 1- Introduction 2- Hypothesis 3 - Space model 4- Search architecture 5- Actuation 6- Conclusions

Slide 102

Slide 102 text

Actuation [esIoT2014] Reusing web-enabled actuators from a semantic space-based perspective.

Slide 103

Slide 103 text

Patterns for Tuple Spaces Actuation

Slide 104

Slide 104 text

Patterns for Tuple Spaces Actuation

Slide 105

Slide 105 text

Patterns for Tuple Spaces Actuation

Slide 106

Slide 106 text

Patterns for Tuple Spaces Actuation

Slide 107

Slide 107 text

Patterns for Tuple Spaces Actuation

Slide 108

Slide 108 text

Patterns for Tuple Spaces Actuation

Slide 109

Slide 109 text

Patterns for Tuple Spaces Actuation

Slide 110

Slide 110 text

Patterns for Tuple Spaces Actuation

Slide 111

Slide 111 text

Patterns for Tuple Spaces Actuation

Slide 112

Slide 112 text

Patterns for Tuple Spaces Actuation

Slide 113

Slide 113 text

Patterns for Tuple Spaces in UbiComp Actuation

Slide 114

Slide 114 text

Patterns for Tuple Spaces in UbiComp Actuation

Slide 115

Slide 115 text

Patterns for Tuple Spaces in UbiComp Actuation

Slide 116

Slide 116 text

Patterns for Tuple Spaces in UbiComp Actuation

Slide 117

Slide 117 text

HTTP API Actuation P O S T / b l a d e s H T T P / 1 . 1 H o s t : s m a r t f a n . e u t r u e

Slide 118

Slide 118 text

HTTP API Actuation

Slide 119

Slide 119 text

HTTP API Actuation

Slide 120

Slide 120 text

RESTdesc Actuation

Slide 121

Slide 121 text

RESTdesc Actuation

Slide 122

Slide 122 text

RESTdesc Actuation

Slide 123

Slide 123 text

RESTdesc Actuation

Slide 124

Slide 124 text

RESTdesc Actuation O P T I O N S / d e u s t o t e c h / l i g h t s H T T P / 1 . 1 H o s t : d e u s t o . e u H T T P / 1 . 0 2 0 0 O K D a t e : S a t , 1 4 J u n 2 0 1 4 2 1 : 2 2 : 0 1 G M T C o n t e n t - t y p e : t e x t / n 3 ; c h a r s e t = U T F - 8 C o n t e n t - L e n g t h : 5 1 2 { a c t u a t o r s : l i g h t s s n : m a d e O b s e r v a t i o n ? l i g h t _ o b s . } = > { _ : r e q u e s t h t t p : m e t h o d N a m e " G E T " ; h t t p : r e q u e s t U R I ? l i g h t _ o b s ; h t t p : r e s p [ h t t p : b o d y ? l i g h t _ o b s ] . ? l i g h t _ o b s a s s n : O b s e r v a t i o n ; s s n : o b s e r v e d P r o p e r t y s w e e t : L i g h t ; . . .

Slide 125

Slide 125 text

RESTdesc Actuation

Slide 126

Slide 126 text

RESTdesc Actuation

Slide 127

Slide 127 text

RESTdesc Actuation

Slide 128

Slide 128 text

RESTdesc Actuation

Slide 129

Slide 129 text

RESTdesc Actuation

Slide 130

Slide 130 text

Motivation Actuation

Slide 131

Slide 131 text

Comparison Actuation Actuation Communication style Benefits Required features Space-based Indirect Decoupling Subscriptions REST-based Direct Reuse Rule-based reasoning

Slide 132

Slide 132 text

Comparison Actuation Actuation Communication style Benefits Required features Space-based Indirect Decoupling Subscriptions REST-based Direct Reuse Rule-based reasoning

Slide 133

Slide 133 text

Comparison Actuation Actuation Communication style Benefits Required features Space-based Indirect Decoupling Subscriptions REST-based Direct Reuse Rule-based reasoning

Slide 134

Slide 134 text

Driving scenario Actuation

Slide 135

Slide 135 text

Comparison Actuation

Slide 136

Slide 136 text

Comparison Actuation Platform Raspberry Pi (model B) RAM Memory 512 MB CPU 700 MHz Low Power ARM1176JZ-F Applications Processor

Slide 137

Slide 137 text

Comparison Actuation seconds

Slide 138

Slide 138 text

Comparison Actuation Actuation Perspective Activity Networking Computation Space-based Provider Proactive, limited Limited Consumer Proactive, limited Limited Space Reactive, high Varies REST-based Provider Reactive, limited Limited Consumer Proactive, high Demanding

Slide 139

Slide 139 text

Comparison Actuation Actuation Perspective Activity Networking Computation Space-based Provider Proactive, limited Limited Consumer Proactive, limited Limited Space Reactive, high Varies REST-based Provider Reactive,limited Limited Consumer Proactive, high Demanding

Slide 140

Slide 140 text

Comparison Actuation Actuation Perspective Activity Networking Computation Space-based Provider Proactive, limited Limited Consumer Proactive, limited Limited Space Reactive, high Varies REST-based Provider Reactive, limited Limited Consumer Proactive, high Demanding

Slide 141

Slide 141 text

Interoperation Actuation

Slide 142

Slide 142 text

Interoperation Actuation

Slide 143

Slide 143 text

Interoperation Actuation

Slide 144

Slide 144 text

Interoperation: how? Actuation

Slide 145

Slide 145 text

Interoperation: how? Actuation

Slide 146

Slide 146 text

Interoperation: how? Actuation

Slide 147

Slide 147 text

Discussion Actuation Further investigation with more complex scenarios is needed: Is the translation between the subscriptions and the goal always possible? If the plan has 2 or more paths to achieve a goal, which one should we chose? What if two different actuators from space-based and rest-based actuation can be activated?

Slide 148

Slide 148 text

Outline 1- Introduction 2- Hypothesis 3 - Space model 4- Search architecture 5- Actuation 6- Conclusions

Slide 149

Slide 149 text

Conclusion

Slide 150

Slide 150 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 151

Slide 151 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 152

Slide 152 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 153

Slide 153 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 154

Slide 154 text

Hypothesis The alignment of the TSC paradigm with the web's principles together with the consideration of its energy and computational impact, leads to UbiComp environments where heterogeneous devices communicate autonomously in an uncoupled and interoperable fashion.

Slide 155

Slide 155 text

Scientific contributions: space model [CHB2014] Lightweight semantic framework for interoperable ambient intelligence applications [WoT2012] RESTful Triple Spaces of Things [IEEESensors2011] Collaboration of Sensors and Actuators through Triple Spaces. [WoT2011] On the complementarity of Triple Spaces and the Web of Things.

Slide 156

Slide 156 text

Scientific contributions: search architecture [IJWGS2014] Energy-aware architecture for information search in the semantic web of things. [IMIS2012] Assessing data dissemination strategies within triple spaces on the web of things.

Slide 157

Slide 157 text

Scientific contributions: actuation [esIoT2014] Reusing web-enabled actuators from a semantic space- based perspective.

Slide 158

Slide 158 text

Scientific contributions: related Lightweight user access control for limited devices. [JUCS2013] Enabling user access control in energy-constrained wireless smart environments. [CISIS2013] Extending a user access control proposal for wireless network services with hierarchical user credentials. [UCAmI2012] Lightweight user access control in energy- constrained wireless network services.

Slide 159

Slide 159 text

Scientific contributions: related Use of TSC middleware in a number of different domains: [IWAAL2011] Easing the mobility of disabled people in supermarkets using a distributed solution. In Ambient Assisted Living, n. 6693 in LNCS, pp. 41–48, January 2011. [Robot2011] Distributed semantic middleware for social robotic services [IWAAL2011] Distributed tracking system for patients with cognitive impairments.

Slide 160

Slide 160 text

Technical contributions As a result of my PhD, I have open-sourced the following software: A parametrizable simulation environment https://github.com/gomezgoiri/Semantic-WoT-Environment-Simulation The three different implementations of the same basic actuation scenario presented before https://github.com/gomezgoiri/reusingWebActuatorsFromSemanticSpace A TSC-based middleware: Otsopack https://github.com/gomezgoiri/otsopack

Slide 161

Slide 161 text

Technical contributions Otsopack has been used in the following research projects: THOFU (CEN-20101019), funded by the Spanish Centro para el Desarrollo Tecnológico Industrial (CDTI) and supported by the the Spanish Ministry of Science and Innovation. ACROSS (TSI-020301-2009-27), funded by the Spanish Ministerio de Industria, Turismo y Comercio. TALIS+ENGINE (TIN2010-20510-C04-03), funded by the Spanish Ministry of Science and Innovation. ISMED (PC2008-28), funded by the Department of Education, Universities and Research of the Basque Government for the period 2008-10.

Slide 162

Slide 162 text

Technical contributions These projects used it in different domains... Residences Hospitals Supermarkets Hotels and homes environments.

Slide 163

Slide 163 text

Future work Are limited devices just dumb devices unable to manage semantic annotations? Do we really need the Semantic Web? Will true-REST-architectures ever prevail?

Slide 164

Slide 164 text

Questions? Aitor Gómez Goiri aitor.gomez (at) deusto (dot) es

Slide 165

Slide 165 text

All rights of images are reserved by the original owners*, the rest of the content is licensed under a Creative Commons by-sa 3.0 license. * leogg, rduris, williamtheaker and cibo00.