You are on page 1of 25

Juan Alapin 324507516

Alon Shahaf 039785431


Traditional WSN
Sensor Clould
Other stuff??!?

The users responsibilities:
Own a WSN
Program the sensors
Deployment
Maintenance


Drawbacks:
One application per sensor network
Time
Resources



Combined WSNs in a wide geographical area.
Virtualization of the sensors. (sensor = service)
Affordable!
Dynamic/Adaptive to the needs of the users applications
Better sensors management (use and control)
Sharing among users (reduces redundancy, increases
efficiency)
Transparent to users in low level details



Emulation of a physical sensor
Contains information of both the physical sensor and the
users holding it.
Overcomes hardware limitations
Implemented in four configurations:
One-to-many
Many-to-one
Many-to-many
Derived



One-to-Many
One physical sensor corresponds to many virtual sensors.
Shared between many users.
Dynamic sampling duration and frequency (No. of users)



Many-to-One
The geographical area is divided into regions, with one or
more physical sensors & sensors networks.
User has access to all WSNs in the region with specific
phenomena.
Fault tolerance.
Adaptive to changes in topology.



Many-to-Many
Combination of one-to-many & many-to-one.
Physical sensor -> many virtual sensors
Physical sensor -> part of a region (network)



Derived
Combination of multiple physical sensors.
Virtual sensor communicates with multiple sensor types!
Enables sense complex phenomenon's and substitute not
deployed sensors.



Divided into three layers:


Client-centric layer:
Acts as a gateway between users and sensors.
User Interface
Session management
Membership management
Repository management




Middleware layer:
Connects client requests with sensors data
Provision management
Image life-cycle management
Billing management




Sensor-centric layer:
Commincation with the physical sensors.
WSN Registration
WSN Maintenance
Data collection






Multi-tiered client-server architecture:


Developing sensor cloud:
System side
Client-centric & Middleware layers
Manage physical resources
Sensor side
Sensor-centric layer
Synchronization
Fault tolerance
Security
Sensor specific constraints ( Low power,bandwidth,energy resources)





Two levels of QoS:
Sensor-centric
Responding to node failures
Network partioning
Packet losses
Virtual sensors
Reliability
Data accuracy
Coverage




Back-End servers platform: Linux
Web application & Back-End servers application: JAVA
Communication: Sockets & RMI
Wireless sensors: TelosB motes






Back-End servers platform: Linux
Web application & Back-End servers application: JAVA
Communication: Sockets & RMI
Wireless sensors: TelosB motes

Combination of requests from users.
Data is stored in the database.
The Sensor Cloud ..
Takes the burden away from the users
Sensing as a service