Weeks 11-12 Summary

Notes: 1. WSN Proactive: getting all paths ready for named-data transmissions/routing. 2. WSN Reactive: transmitting/routing named-data when required (i.e. on demand), e.g. when event changes, or when Sink wants some data (query). 3. Flat WSN: all sensor nodes are equal in transmitting data; no clusters nor cluster heads. 4. Data centric routing: transmissions based on whether named data is required (of-interest) from any sensor nodes, i.e. sensor node id is immaterial. Egs: (i) Sink/Base Station broadcasts a request to seek data of interest (e.g. temp > 60C) from any sensor node. (ii) A sensor node broadcasts to its neighbours to see any of them is interested in its named data. 5. Clustered/Hierarchical WSN: sensor nodes are grouped into clusters (one-level or multilevels), with a self-appointed cluster head (cluster heads work in rounds); a cluster head acts as a relay point (much like MPR in OLSR) for transmitting data to-and-forth the Sink/Base Station. Main purpose: to conserve energy by reducing the number of data transmissions (via data fusion/aggregation). 6. SPIN protocol: A sensor node (Source) wants to propagate its data to all other sensor nodes in a proactive manner, using ADV broadcast, then interested neighbours respond with REQ; finally the Source SENDS DATA to the interested neighbours. Subsequently, these neighbours will propagate the Sources data to all other WSN nodes in the same manner: ADV -> REQ -> SEND DATA. 7. Directed Diffusion protocol: Sink/Base Station is looking (querying) for named data from any sensor node when required, i.e. in a reactive manner: Sink propagates/floods interest ->

Initial gradients set up (much like reverse pointers in AODV) -> Data delivery (Sink to-andforth Source) along reinforced path (most optimal path among all the alternate gradients). 8. LEACH protocol: mostly for single-level clusters; clusters are set up in a proactive (periodical) manner with 2 phases: (1) Set-up phase: Self-proclaimed Advert (I am a Cluster Head -CH) -> Cluster Membership Set-up -> CH schedules a timeslot for each of its members to transmit data. (2) Steady-State phase: in a given timeslot, each member transmits data to the CH for relaying the data to the Sink. CHs work in rounds. 9. TEEN protocol: mostly for multi-level clusters; clusters are set up when required (on demand), such as when an event changes. A sensor node transmits data to its CH or a CH transmits data to Sink only when: (1) the data value is greater than a threshold (called Hard Threshold), and (2) the difference between the data value and the previously-transmitted data value is more than a threshold (called Soft Threshold). Data are not transmitted if these 2 conditions are not met hence conserving energy.

(See the lecture slides and the e-book chapter for details of SPIN, Directed Diffusion, LEACH and TEEN routing protocols.)