1. 1 Global Sensor Networks A Platform for the Internet of Things Ali Salehi, Prof. Karl Aberer

2. 2 What are Sensor Networks ? ActuatorsSensors Interconnected! and Actuators, Sensors,

3. 3 Properties of existing solutions Expensive To Modify Time consuming Hire Expert(s) People don't benefit from sensor networks.

4. 4 Motivation, ? ?

5. 5 Question : What is common ? 1. Stream of Data. 2. Structure can be defined. 3. Common Requirements. Virtual Sensor

6. 6 WHAT DOES ALL THIS MEAN Internet of Things.

7. 7 Hardware independent, any new hardware (sensors and actuators) should be integratable. Application independent. Light & Scalable (internet scale ; peer to peer) Modifications MUST be very cheap and simple. Modifications MUST be applied while system is running. Solution, Restarting the internet ?!!! A Software :

8. 8 Design, Global Sensor Networks Common data processing, management and interfacing requirements, off the shelf. GSN = implementation of the virtual sensor concept and the all the listed requirements. Multi layered architecture to be deployable on resource constrained devices.

9. 9 Simplicity, Simplicity, Simplicity (1) Email to MMS Service (swisscom) A ) Select Image from Camera B ) Select Temperate from MoteA Select Camera.Image from A[window 1],B[window 10min] where avg(temperature) >30 Application description

10. 10 Control Engineers Automatic Control Laboratory,ETHZ Requirements: Simplicity, Unified Abstraction. Matlab Controller Light & Temperature Electric blinds GSN

11. 11 Stream Services Develop sensor network applications :  Virtual sensors.  Might produce a stream of data (service). Buy a stream source :  Hardware and/or Service (E.g., Lausanne temperature ). Stream Sources GSN Virtual Sensors

12. 12 Simplicity, Simplicity, Simplicity (2) Self identifying devices (IEEE 1451). TEDS and Virtual TEDS. Zero-programming deployment. Template Virtual Sensor TEDS New Virtual Sensor + =

13. 13 High Level View of The GSN * Uniform API for developing Sensor Network Applications. * Declarative Requirement Management. * Uniform API for exporting sensor data to the GSN. * Various protocols (interfaces) for accessing data.

14. 14 Resource Discovery Addressing the virtual sensors : Static (e.g., socket address). Dynamic using a set of predicates : Using a Directory Service: 46.3423 temperature Distributed Directory Service (DDS)*: Based on P-Grid infrastructure. Each node acts as a peer in DDS. * Not implemented yet.

15. 15 Resource Constrained Devices Resources are allocated on demand. Resource sharing as much as possible. 20 virtual sensors, 10% > CPU, 64MB RAM, 500 Mhz. Requirements (e.g., Nokia 770),  32-bit processor.  64 MB Memory and/or Swap Option.  25 MB Storage.

16. 16 Wrappers, as of Today Bridge between the sensors/actuators and the GSN. WrappersActuators TinyOS 1.xSMS Service. TinyOS 2.xEmail Service. Wise NodesPages Service. TI RFID Readers (20cm) Alien Tech. Readers (20m) Fax Service. Wired CamerasEPuck Robots. Networked CamerasSpeaker Output (AT&T) Generic Bluetooth Protocol IEEE 1451 Compatibility Generic Serial Generic UDP

17. 17 Outcome as of today. Successful Open Source Project. More than 20 sensors/actuators supported. 7 Releases of the engine (Stable). 30K visitors, 600 downloads. Users Community GNU GPL License

18. 18 WHAT DOES ALL THIS MEAN GSN, Middleware for Internet of Things. Q/A