1. Juan Alapin 324507516 Alon Shahaf 039785431

2. Traditional WSN “Sensor Clould” Other stuff??!?

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

4. Drawbacks: One application per sensor network Time Resources

6. 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

7. 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

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

9. 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.

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

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

13. Divided into three layers:

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

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

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

18. Multi-tiered client-server architecture:

19. 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)

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

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

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

23. Combination of requests from users. Data is stored in the database.

24. The Sensor Cloud.. Takes the burden away from the users Sensing as a service