1 WSN Summer Project Demo Scenario Skövde 2008

2 Shows features (legend) Real-time (RT) Fusion (Fus) Database, Replication (DB) Scalability, ViFuR (VF)

3 Fire fighting scenario or Battlefield game? The scenario described can be mapped to alternative real scenarios – ”imagine!”

4 Scenario features Persons move in a watch area. They are light-sensed as ’red’ or ’blue’ people. Their locations are reported into a database, from where their tracks can be extracted and also predicted by using fusion (e.g. Kalman filters). Multiple red people may be separated by their expected track (assumed being not too close). Persons act in the environment by clapping (single/double clap signature), and those events are reported, with signatures, to the connected database node. Disjoint sensor sub nets report their area to separate database nodes. People tracking and event localization is done at a fusion node, where database replication provides data for the entire area. Tracks and actions are visualized at multiple client nodes, which have replicas of the visualization data (segment) of the database.

5 Features of the Scenario Sensors: Tracking by using visual features (color), event detection and localization by using acoustic features (sound signatures) Events are localized by using sound timestamps from multiple sensors (RT, Fus) Action signatures by single or double claps. This emulates processing for signatures (RT, Fus) Tracks + localized events are visualized on multiple displays (DB, Rep) Tracking by using the logged visual trace, short term database time series, multiple red people may be distinguished by their physical move limitations (DB, Fus) Data from regions of sensors (can’t communicate in between) are replicated (VF, DB)

6 Sensor setup Acoustic: Room has 5 MICAz+MTS310, using the microphone (sound level) Visual: Multiple TelosB, using the light sensors with ”directed sight” (tube) and colored light sensing (filter) (or distinct gray scale differences). ”Colored jackets” worn by people? ”Colored jackets” worn by people?

7 Sensor placement SS SS S L LL L LL L LL L LL LL S = Colored light sensor= Sound sensor

8 Technical needs Move-events + classification from sensors Action-events + signature from sensors Feed of sensor data + (re-)configuration. Support request for 1) - single sensor input 2) - periodic sensor input 3) - sensor input (single or periodic) in response to event (including timer), all sensor input includes a vector of all sensor readings in the sensor node (should we prepare for the possibility of requesting a subset, or adding additional sensors?) (should we prepare for the need to buffer multiple readings and send as single message to save bandwidth clutter?) Database replication, single master, but extendable for PRiDe

9 Scenario, decision on Friday 11th Consider alternative scenario descriptions Using the same technical features to describe alternative scenarios: Map application to demo: ”Imagine!”

10 Impl:Mote communication 1.Tmote Connect approach 2.TelosB gateway  Tablet USB 3.Tinymote gateway  Tablet SD slot 4.Bluetooth gateway  Tablet (port?)

11 Impl:Database 1.Store sensor data in local BDB database 2.Visualize sensor data 3.Replicate sensor data to other nodes 4.Visualization sensor data at other DB node