Physicalnet cross network applications for multi user sensor and actuator networks
This presentation is the property of its rightful owner.
Sponsored Links
1 / 10

Physicalnet: Cross-network Applications for Multi-user Sensor and Actuator Networks PowerPoint PPT Presentation


  • 48 Views
  • Uploaded on
  • Presentation posted in: General

Physicalnet: Cross-network Applications for Multi-user Sensor and Actuator Networks. Pascal A. Vicaire ([email protected]) John A. Stankovic ([email protected]) University of Virginia. Goals. Programming sensor network applications from any PC connected to the Internet

Download Presentation

Physicalnet: Cross-network Applications for Multi-user Sensor and Actuator Networks

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Physicalnet cross network applications for multi user sensor and actuator networks

Physicalnet: Cross-network Applications forMulti-user Sensor and Actuator Networks

Pascal A. Vicaire ([email protected])

John A. Stankovic ([email protected])

University of Virginia


Goals

Goals

  • Programming sensor network applications from any PC connected to the Internet

    • Global / cross-network applications

      => Access rights

    • Multi-user

      => Conflict resolution

    • Ease of programming

      => Discovery and manipulation of large sets of nodes

      => Heterogeneity

      => Mobility

      => Compatibility


Physicalnet

Global accessibilty

Physicalnet is a Service Oriented Architecture

Each node has a unique global identifier

Nodes are not tied to a particular geographical location

Physicalnet

Users

Negotiators

Gateways

Service Providers


Physicalnet1

Access rights

All Physicalnet services are composed of states and events

For each service:

Localization rights

For each state:

Reading rights

Writing rights

Priority

For each event:

Idem

Physicalnet

Temperature Sensor Access Right Table

| Priority | Location | Sensor | Rate

John | 1 | L | RW | RW

Mike | 2 | L | RW | R-

Peter | 3 | - | RW | RW

Tom | 4 | - | -- | --


Physicalnet2

Conflict resolution

Service specific resolvers to manage conflicts between user requirements

Examples:

First come first serve

OR, AND operators

Highest priority

Minimum

Access to actual state value within application

Physicalnet

Users

Negotiator

Requirement Table

App. Service State/Event Args

A1 temp1 samplingPeriod 10s

A2 temp1 samplingPeriod 15s

A3 temp1 samplingPeriod 20s

Resolver

Service State/Event Args

temp1 samplingPeriod 10s

Towards Service Providers

(Sensors / Actuators)


Physicalnet3

Programming API

Large sets

Cross networks

Dynamic sets

heterogeneous sets

Mobility

Compatibility

Physicalnet


Preliminary results

FireAlarm Application:

Code Size:~80 lines of code

Installation time:~15s for 36 nodes distributed across 2 remote networks

Average responsiveness: ~3s

Preliminary Results:


Conclusion

Conclusion

  • Our goal is to create a framework to facilitate the programming of cross-network applications of multi-user sensor and actuator networks.

  • Our solution uses a service oriented architecture that supports node heterogeneity, node mobility, access rights, conflict resolution mechanisms.

  • It provides a high level java API to specify programs using dynamic logical sets of nodes.


Physicalnet cross network applications for multi user sensor and actuator networks

Thank You!

Questions?

Pascal A. Vicaire ([email protected])

John A. Stankovic ([email protected])


Why is it difficult

Global accessibility

=> Access rights

Resolution?

Specification?

Mechanisms?

Multiple users

=> Conflict resolution

Resolution?

Specification?

Mechanisms?

Ease of programming

=> Discovery and manipulation of large sets of nodes

=> Sets that span multiple networks

=> Heterogeneous sets of nodes

=> Mobility

=> Compatibility with other service oriented architectures

Why is it Difficult?


  • Login