SENSEI - CONFIDENTIAL SENSEI system overview RWI discussion material Alex Gluhak – University of Surrey 07. April 2010

SENSEI - CONFIDENTIAL

SENSEI system overview

RWI discussion material

Alex Gluhak – University of Surrey

07. April 2010

SENSEI objectives and roles in the system

SENSEI SENSEI Review Meeting, Bucharest 30.03.2010 2

Resource user:•Business process •Context-aware mobile service •Control and monitoring applications •Network management function, etc.

Resource provider•WSAN island operator, •Processing component provider

Resource:• Sensor• Actuator• Processing component• Management state, etc.

Design the foundations of a framework that enables an open market place for real world information and interaction

Horizontalisation - facilitate the horizontal reuse of sensing, actuation and processing services.

Evolvability - evolvable RWI architecture to withstand technological changes in the eco-system

Heterogeneity - accommodate a variety of sensor and actuator networks with different technology and administrative domains

Continuity - ensure that requested services are provided with adequate quality despite mobility of system entities/users

Privacy and Security - protect the privacy of the users and offer adequate security for participating systems/entities

Accessibility - reduce the complexity of accessing sensing and actuation services

Simplicity of participation - ease the integration of new WSANs and facilitate the deployment

Manageability - permit distributed management of the participating systems and their resources

Scalability - support internetworking of a large number of distributed sensor networks islands

Locality - support local operation of the system

SENSEI -- Confidential 3

SENSEI design goals

Resource user expectations

I want to discover and access resources that I need– Resources that suit my interactions demands

– Resources that satisfy a certain quality of information or actuation

– Resources that provide best value for money

– Best possible resource currently available for the envisioned request

– ...

I want simpler access to resources– I do not care about the resources but I just want the result they provide or

the effect they cause


Resource provider expectations

I want an flexible and easy way for users to – Discover the resources they need

– Access the resources they need

Only authorised users should access my resources

Only authorised users should discover my resources and their capabilities

I want an easy way – to deploy my resources

– to manage my resources

I want my resources to be re-used for different users, possibly at the same time

I would like revenues from the use of resources I offer


EntityDirectory

ResourceDirectory

Real World

sensor

sensor

actuatorsensor

sensor

Entity-based ContextModel models relevantaspects of Real World

SENSEI System

Resourcesmeasure,observe andactuate onReal World

Association of resourcesto modelled entities

Different levels of abstraction


Context Framework

Sensor Framework

Interaction examples from a resource user view (1) Resource level lookup and discovery of resources

– ID based: • I want the resource description of Sensor 1234• I want the resource description of Actuator 9876

– Type based: • I want a list of the resource descriptions of Temperature Sensors

– Tag based:• I want the resource descriptions of resources that have been tagged as

“London”, “Air Quality”

Entity level lookup and discovery of resources– Entity ID / attribute based:

• I want the resource description of actuator resources that allow me to set the Light Level (attribute) of Room 45 (entity ID).

– Entity type / attribute based:• I want the resource descriptions of resources that provide me the Activity

(attribute) of Pubs (entity type) [in downtown Heidelberg]


Interaction examples from a resource user view (2) Resource level access to observations and measurements

– ID based: • I want to query the current measurement of Sensor 1234• I want to subscribe to periodic updates of the measurements of Sensor

1234– Type based:

• I want the current measurements of all Temperature Sensors– Tag based:

• I want to subscribe to updates of the measurements of sensors that have been tagged as “London”, “Air Quality”

Entity level access to context information– Entity ID / attribute based:

• I want a notification for Indoor Temperature (attribute) of Room 45 (entity ID), when ((Indoor Temperature > 25°C) or (Indoor Temperature < 18 °C)).

– Entity type / attribute based:• I want to query the current Activity (attribute) of Pubs (entity type) [in

downtown Heidelberg]


Interaction examples from a resource user view (3) Resource level actuation

– ID based:• I want to set the Light Status of Actuator456 to on.

Entity level actuation– Entity ID / attribute based:

• I want to set the Light Status (attribute) in Room 45 (entity ID) to on.– Entity type / attribute based:

• I want to set the current Light Status (attribute) of Rooms (entity type) to off [on the second floor]


Interaction examples resource provider view Operation and management of WSAN islands

– Configuration of access policies for a resource or an WSAN island• Set access policy X for access group Y for Sensor 1234• Set default access policy for all nodes in WSAN island Y

– Reading statistics from individual sensor nodes• Get “uptime” statistic for Sensor 1234• Get average packet drop rate over past 1h for all nodes in building A

– Setting configuration parameters• Configure network prefix for GW x• Set concurrent query parameter to 3 for sensor 1234

– Re-programming of sensor nodes or entire islands• Distribute firmware code X to all nodes in WSAN island Y of type Z• Restart all nodes with firm ware version X.Y

– Control loops or complex events for advanced O&M• Send an alarm message to network operation centre, if more than 5

sensor nodes become unavailable in Building Z and activate backup


Infrastructure of sensing, actuation, and processing resources

Incoming requests cannot always be achieved by one resource

Complex resources: aggregations built on the fly

Complex resources


Genericheatingcontrol

Temperature Room1

PresenceRoom1

Genericheatingcontrol

Heating control Room1

HeaterRoom1

Weatherservice

Sensei resources

Other features

Plug and play configuration– Automatic discovery and registration of resources in the system– Association management between resources and entities– Automatic update of system state if changes in real world occur

Adaptation of longer lasting interactions– Maintaining a desired quality of information/ actuation level

throughout the duration by substituting or reselecting serving resources or a subset of those

....


High level view

SENSEI 13

Communication Services Layer

Application Layer

Context Aware/Control Applications

Management Applications

SENSEI (Real World) Resource Layer

SE

NS

EI S

cope

SENSEICommunity

Management

SENSEIResources

SENSEISupport Services

Unifying abstraction for sensors, actuators And processing components

• Lookup and discovery • Adaptive composition• Dynamic resource creation • Long term interactions

• Identity management• AAA• Privacy and security

Key architectural entities

SENSEI 14

REP

REP host

Resource

Resource host

Real worldentity

1..*

1

1..*

1

1..*

0 *

0 *

associated with

hosts

accessed through

contains

1

Entity

Spatial Entity

Room

Person

Virtual Entity

...

hasIndoorTemperaturehasLightLevelhasNoisehasOccupanthasSize...

Simple Composite

Physicalsensor, actuator

multi-sensor/ actuator node,

sensor gateway

Virtual

Performancecounters,

configuration parameters

processing component, data

storage

Support services


Resource Directory

Semantic Query Resolver

Execution Manager

lookup, query

lookup

query

query

Entity Directoryquery

publish

query

access

Setup & monitor

access

ResourceUser

Res

ourc

e D

irect

ory

Host

ResourceResource Creation

request


Support Services

Host

Resource Directory

Dynamic Resource Creator


Query Analysis

Task Planning

Resource Deployment

Resource User

Abstract PlanData Base

ComponentData Base

Dynamic ResourceCreation

ResourceData Base

Resource Publication

Execution Manager

Session Monitoring

Resource Lookup

RLI

RLI

RRCI

RLI

R

Request Management

SQI

RAI

Entity Directory

EnitityPublication

Mapping TableEntity Lookup

OntologyELI

ELI

REI

EP

R EPI

R

RPI

ELI

Resource

REP

RP

RAI

RAI

R

RDI


T3.1 – Use cases: Direct interaction with Resource

Host

Resource Directory



Query Analysis

Task Planning

Resource Deployment

Resource User


ComponentData Base


ResourceData Base


Execution Manager

Session Monitoring

Resource Lookup

RLI

RLI

RRCI

RLI

R

Request Management

SQI

RAI

Entity Directory

EnitityPublication


OntologyELI

ELI

REI

EP

R EPI

R

RPI

ELI

Resource

REP

RP

RAI

RAI

R

RDI

Light Temp123 what is your value?

Light Temp123: value=10oC


T3.1 – Use cases: Rendez-vous, Resource Directory

Host

Resource Directory



Query Analysis

Task Planning

Resource Deployment

Resource User


ComponentData Base


ResourceData Base


Execution Manager

Session Monitoring

Resource Lookup

RLI

RLI

RRCI

RLI

R

Request Management

SQI

RAI

Entity Directory

EnitityPublication


OntologyELI

ELI

REI

EP

R EPI

R

RPI

ELI

Resource

REP

RP

RAI

RAI

R

RDI

1.Find Resource, keywords: “temp”, “Stockholm”

2.REP URL: http://sensei.com/Temp123


T3.1 – Use cases: SQR, Entity Directory

Host

Resource Directory



Query Analysis

Task Planning

Resource Deployment

Resource User


ComponentData Base


ResourceData Base


Execution Manager

Session Monitoring

Resource Lookup

RLI

RLI

RRCI

RLI

R

Request Management

SQI

RAI

Entity Directory

EnitityPublication


OntologyELI

ELI

REI

EP

R EPI

R

RPI

ELI

Resource

REP

RP

RAI

RAI

R

RDI

1.Are there any “temp” sensors in “Room45” ?

3.Entity: “Room45” associated with

Resource type: “Temp” ?2.Find if EoI “Room45”

has any resource of type “temp”

5.Entity: “Room45”Resource: Temp123

7.EoI: “Room45”, Temp123 ResDes

4.Entity-Resource Lookup

6.Retrieve Resource Description of Temp123


T3.1 – Use cases: Long term Actuation Loop

Host

Resource Directory



Query Analysis

Task Planning

Resource Deployment

Resource User


ComponentData Base


ResourceData Base


Execution Manager

Session Monitoring

Resource Lookup

RLI

RLI

RRCI

RLI

R

Request Management

SQI

RAI

Entity Directory

EnitityPublication


OntologyELI

ELI

REI

EP

R EPI

R

RPI

ELI

Resource

REP

RP

RAI

RAI

R

RDI

1.If room Galileo is empty for 5 minutes, turn lights offExecute this command for 10 days

2.Find resource providing this service

3.No Resource!

4.Find an abstract task plan that provides this

service

5.Abstract task plan needs resources:

1) a motion sensor2) a light switch

3) Both resources associated with Entity

GalileoRD is queried for needed resources

6.Create resource: emptyGalileo

7.Publish Resource8.Publish Galileo- emptyGalileo association

9.emptyGalileo

Execution Manager setting up Sessions

ResourceUser

ExecutionManager

REP

Session

RAI

RAI

RAI

RAI

RAI

SessionSession

SessionSession

RAI

RAIRAI

RAI RAIREPREP

REPREP

RAI

Subscription Interface:- Subscription Locator- Subscription- RAI Interface (Type)

Notification Interface:- Locator- Subscription ID



Community management services

TokenIssuing

interface

Security TokenService

AAA service

Resource Access ProxyService

Federation interface

AccessControl

interface

Security layerfor RAI

Token Issuing interface

Auditing andBilling Service

Billing Serviceinterface

Security layer for

RAI

Security layer Resource Layer

interfaces

Access ControlledEntity

e.g. Framework Componentor REP

AccessingEntity

e.g. end useror resource

Accessing Entity Access Controlled Entity

End user Resource

End user Resource Description

End user Framework component

Resource Resource Directory

Peering between SENSEI domains

SENSEI 23

RD

SENSEI administrative domain #1

ATS

EDSQR

EM

DRCpeering

RUsRUs

RD

SENSEI administrativedomain #2

ATS

EDSQR

EM

DRC

RUsRUs

ResourceProviders Resource

Providers

Key design goals revisited - design choices

Support the heterogeneity of resources through openness and semantics– Unified resource descriptions not resource access interfaces – Semantic descriptions of resource operations and capabilities

Support horizontalisation across multiple application domains– Rendevous infrastructure enables decoupling of WSANs from applications– Enable multiple context frameworks on top of unifying sensor framework

Accessibility– Uniform resource abstraction– Provide advanced service function, reducing the complexity of discovery and interaction

for services and applications

Simplicity of participating– Plug and play integration of WSAN through easy to use SENSEI wrapper– AAA framework to enable different business models

Continuity– Advanced system functionality to adapt to system dynamics

SENSEI 24

SENSEI 25

Conclusions

SENSEI provides an architecture for integrating heterogeneous resources for real world information and interaction

– Provides a common way of representing resources in the system and ways to access those

– Rendezvous mechanisms to discover resources that can provide necessary context or actuation

– Session support to manage complexity of system dynamics

Documents

SENSEI - CONFIDENTIAL SENSEI system overview RWI discussion material Alex Gluhak – University of Surrey 07. April 2010