SensorWare: Distributed Services for Sensor Networks

1
SensorWare Distributed Services for Sensor
Networks

• Rockwell Science Center
• and UCLA

2
Distributed Services for Sensor Networks
NEW IDEAS

• Object-oriented API to nodes sensing and
  processing functions
• Scriptable light, run-time environment with
  security and protection
• SensorWare Distributed sensor network
  domain-specific middleware services APIs
• Lightweight, mobile, sensor control scripts for
  tasking and tracking

IMPACT
SCHEDULE

• Facilitate development and plugging in of new
  distributed sensing applications using high level
  of abstractions
• Allow authorized external users and systems, even
  transient ones, to access the collective sensing
  capabilities of sensor networks
• Operate efficiently with limited computation,
  communication and power resources

YEAR 1
YEAR 2
YEAR 3
Requirements Analysis Node Enhancements Runtime
Environment Script Execution Middleware
Services Integration/Demos
Rockwell Science Center Jonathan Agre UCLA
Mani Srivastava
3
SensorWare Target Tracking
User downloads a sensor control script
Scripts coordinate to combine sensor readings and
send periodic updates to the external user
Scripts move to new sensor nodes as the target
moves
4
Current Software Architecture
User Applications
Long Range Radio
Software Development Toolkit
PC HOSTED
User Message/ Command Interface
User Interface Application
Sensor Fusion
ARM HOSTED
Signal Processing Vibration
Signal Processing Microphone
Signal Processing Magnetometer
Network Protocols
System Control
MicroC/OS
DCT Radio Driver
Vibration Driver
Microphone Driver
Magnetometer Driver
External RS232 Driver
HAL
System Bus
RADIO HOSTED
DCT Radio
Vibration
Microphone
Magnetometer
5
SensorWare System Architecture
Transient External User
download
Download migrate
Mobile Scripts
SCRIPT
Applications
APP
Node Kernel APIs
Sensor Middleware
Hardware Abstraction Layer
Sensor Node Hardware
Sensor 1
Sensor 2
6
SensorWare Middleware Services

• Addressing and naming services for info
  dissemination and control
• spatial addressing of nodes
• spatial routing to individual and groups of nodes
• Signal processing services
• sensor value-based and collaborative processing
• Fault management
• exploit overlapping coverage
• Resource Management and Organization
• power aware services
• Timing and synchronization
• support synchronized sensing
• Authentication and security
• detection of spoofing
• User/External System Interfaces
• command/control and situation reporting
• Mobile script execution
• retasking and target tracking

7
SensorWare Near Term Goals

• Requirements definition (6 mo.)
• Choose realtime OS environment (currently
  microC/OS)
• Define low-level OO API for radio, sensors and
  other system components
• Define initial set of distributed middleware
  services
• Enhance existing Rockwell Platform (6 mo.)
• Increase Memory Capacity
• Build 10 units
• Improve debugger
• Interface to SenseIT Architecture
• Plan for demonstration of mobile code for target
  tracking
• Integration with overall architecture

8
SensorWare New Directions, Challenges, Open
Questions

• The definition of set of services that
  accomodates the SenseIT Community
• Not initially an objective, need feedback from
  other PIs
• What basic services can be provided by other
  PIs for consideration?
• Communication services span a wide range of
  needs/desires
• Original emphasis was on spatial addressing
• Can diffusion, which does not require explicit
  addressing, coexist with addressable units?
• How critical is realtime and deterministic
  behavior?
• Integration of mobile script demonstration with
  overall demonstrations
• Integration with architecture proposed by BBN is
  under discussion