Network Computing Laboratory Sentire: A Framework for Building Middleware for Sensor and Actuator Networks Joel W. Branch*, John Davis, Daby Sow, and Chatschik

Network Computing Laboratory

Sentire: A Framework for Building Middleware for Sensor and Actuator

Networks

Joel W. Branch*, John Davis, Daby Sow, and Chatschik BisdikianRensselaer Polytechnic Institute – Troy, NY*, IBM T.J. Watson Research Center –

Hawthorne, NY

IEEE PerCom 2005 – PerSeNS WorkshopKauai Island, Hawaii March 8-12, 2005

Network Computing Laboratory | 2

Korea Advanced Institute of Science and Technology

Agenda

One-line comment Background

Sensor-Actuator Network

Motivation Solution approach

Overview Managers messages

Demonstration Collaborating sensing

Critique



One-line comments

This paper, Sentire (latin, to sense), describes a framework for developing extensible middleware for sensor and actuator networks (SANETs)



SANET

BackgroundSensor-actuator networks

Sensor-actuator network Sensor

Unreliable resource-constrained network

Actuator Control-oriented application

Middleware Application

Example Building control: Heating, ventilation

and air conditioning (HVAC) Sensors Actuators Controller A set of preferred temperature level

(user policy)

SANET middleware

Application(s)



MotivationScaling up SANET-related systems

1-1000 1000-10M >10MNumber of embedded devices

Co

ntr

ol d

istr

ibu

tio

nC

entr

aliz

ed

Dec

entr

aliz

ed

Today

Tomorrow

Autos

Security systems

Smartbuildings

Adaptive trafficcontrol

Automatedfactories

Assettracking

Networked cities

Instrumentedfarm

Plant processcontrol

Habitatmonitoring

* Figure reproduced from [Zhao2004]

Trend points to increasing number of devices and decentralization

??



Motivation“Reaching tomorrow” – Research motivation

SANET middlewaredevelopment standard

- Supports large scale development- Supports extensibility, reusability, and

interoperability- Supports SANET integration

SANET requirements- Resource management- Network management

- Data management

SANET applicationdevelopment

- Shield applicationdevelopers from writing complex andcustom code for multiple platforms



The Sentire approachOverview

Objectives Introduce general software development framework for extensible SANET

middleware development Different from middleware instantiations

Easy applications’ usage of integrated, heterogeneous sensor and actuator-enabled systems

Partition middleware development into logically related sub-tasks Share a common plug-in infrastructure



The Sentire approachOverview

Current components Centralized component-

interaction model Managers Messages

Current assumptions Direct-transmission (1-hop)

networks Middleware residing on edge-

servers, stargates, etc.

Interface manager

Query results,Admit/reject decisions

Sensor dataQueries, Device instructions

Sensor manager

Resource manager

Resource data

Admit/rejectdecisions

Data manager Actuator manager

Query results

Queries,Device instructions

Sentireframework

Queries

Sensor and actuator network(s)


SANET application(s)

Deviceinstructions

Device instr.

Queries



The Sentire approachManagers

Interface manager Funnels application queries and instructions to appropriate managers Provides initial layer of query/instruction filtering via developer-defined admit/reject

policies Assign unique IDs to the queries and instructions

Sensor and actuator managers Controls sensor and actuator device behavior

Influences both the quality of sensed information and adjustments to the environment Request authorization

Resource manager Implements service registration of SANETs Tracks SANET resource usage (e.g., energy, bandwidth) Supports other managers in their policy-based decisions

Authorization and confirmation Adjusts resource usage

Data manager Embodies develop-defined data processing routines (e.g., event detection, data

cleaning, etc.) Interact with the sensor and actuator managers to Instantiate more complex sensing

and actuation



The Sentire approachMessages

Sentire queries Interaction with external user application Header: Query’s ID, Priority, Data type, QoI requirement, and Query type

(e.g., single query, subscription, event notification) Sentire messages

“Publish-subscribe” used for inter-manager communication Structure for inter-manager communication Header: Priority, timestamp, sending manager

Data messages Response to queries Header: Corresponding query ID, Data type

Customizable XML payload structures Promotes flexible message attributes and data payloads Extensible inter-component interaction Simple “plug-in” environment



SANET

Sentire demonstrationCollaborative sensing

Demonstration Scenario

Motion SensorActuator

Sentire middleware

If (car exist & head light is on) then turn on a streetlamp

Light Sensor

Oh, it’s too dark!!

Is there any light?

Sensingresponse instruction




Implemented using Sentire and LEGO® MindstormsTM hardware [LEGO]

The motion detector monitors for vehicle movement in 2 zones

Upon detected movement in a zone, re-bind to the zone’s respective light sensor

If light is detected, the zone’s respective LED powers on.

Zone 1

Zone 2

SANETmiddleware

SANETgateway

Low-energymotion detector

High-energylight sensor

Target

RCXbrick

Legacynetwork

LED




Sentire operation details

Interface manager Registry event notification

Sensor manager Decompose request Check permission

Data manager Receive and verify events Route events to sensor and

actuator manager Resource manager

Check battery charge Suppress instruction

Zone 1

Zone 2

SANETmiddleware

SANETgateway

Low-energymotion detector

High-energylight sensor

Target

RCXbrick

Legacynetwork

LED

Interface manager



Sensor manager

Resource manager

Resource data



Query results


Sentireframework

Queries




Deviceinstructions

Device instr.

Queries



ConclusionResearch progress

Current progress Middleware methodology for facilitating applications’

interaction with integrated sense-and-respond system

Research timelinePerSeNS 2005

Future work Extend methodology for “closed-loop” sensor-

actuator interaction Distribute Sentire functionality

Coordinate multiple edge-servers, etc. Distribute framework to the device level



Critique

Strong point Framework for developing middleware for SANET Integrate heterogeneous SANET Lesson of Sentire comparing to SCANET

Thinking of core part Fast development Simple and Practical experiment

Weak point Dim management classification

Ambiguous role distribution between manager Anyway, we must develop a “specific” middleware for each system

using sentire Sentire just help a development of middleware



New idea

Modify message to remove ambiguous role Missing part of global query

handler Developer concentrate on data

manager develop-defined data processing

routines Query handling routines

Other manager can be shared

Interface manager



Sensor manager

Resource manager

Resource data



Query results


Sentireframework

Sensor and actuator network(s )



Device instr.

Queries

QueriesDeviceinstructions



New idea

Merging Sentire with MASDAQ

Interface manager



Sensor manager

Resource manager

Resource data



Query results


Sentireframework




Device instr.

Queries

QueriesDeviceinstructions

Application

Sensors

PSC: Probabilistic Sample Collector

QSO: QoI-aware Sampling Optimizer



Backup slides



Signal landscape

SANET

The Sentire approachFramework

Sentire middleware

Application 1

Priority=1, Data_type=Movement, Query_Type=1_time

Location=North_walkway, Object=people, Metric=Quantity, Quality=low

Query_ID=1_1234, Priority=1, Data_type=Audio, Query_Type=1_time

Location=N_h, Object=P, Metric=Quantity, Sensors=1,3

From sensor manager

SANET

Documents

Network Computing Laboratory Sentire: A Framework for Building Middleware for Sensor and Actuator Networks Joel W. Branch*, John Davis, Daby Sow, and Chatschik