ELEG 467/667

1. ELEG 467/667 Sensor Networks Spring 2006

2. Before anything happens • Add / drop • Does anyone know of anyone who is dropping? • A few people can add! (Don’t tell anyone) • Meeting time

3. Basics • Instructor: Stephan Bohacek • TA: none, but Vinay Sridhara will help with Lab stuff. • Web page: http://www.eecis.udel/~bohacek • But nothing is there yet. • Textbook: none. A reader will be available soon.

4. Course Focus • Comprehensive introduction to sensor networks. • Network protocols at various layers. • MAC, routing, transport. (there is cross-over here with wired and other wireless) • Application issues. • Data fusion, localization • Analytical methods in networks • Optimization (routing, and power control) • Modeling (analysis of MAC) • Unique issues: energy efficiency, self managing, data driven, arbitrarily large scale, etc. • And everything

5. Prerequisites • Basic networking • For example, you know • what the transport layer does • what exponential back-off is • at least one MAC protocol • what flooding is and how it works • Programming • For example, you can implement flooding.

6. Format of class • Seminar / project oriented • Lectures • The first couple of months and some others. • Reading • Assigned reading with in class discussion • Homework • Projects • Many small/moderate projects and a large one • Presentations • Grad students must give half-hour talks on a topic. • The talk should be on a paper related to the lecture the week before. • The talk should be fairly short and should add to the prior week’s discussion. • Project discussions • Group talk about project. The talk covers: • The problem to be solved • The related papers (if the project is base on a paper, then the talk MUST include discussion from both the paper that the project is based on, and some related papers) • Key challenges • Schedule • Final project presentation • Final project write-up

7. Projects • Moderate and final projects will be group projects. Groups should have 2 grad and 2 under grads. • Project selection and presentation (by 3/30) • Projects may be related to grad student lecture topic • Project progress report (4/20) • Project presentation (5/18 and 5/25)

8. Grading • Class discussion/reading (10%) • Small/moderate projects (30%) • Homework (10%) • Presentations (20%) • Final project (30%)

9. Reading material • Reader available from the web site and papers listed on web site. • Also: • Wireless sensor networks. Editors: Ragavendra, Sivalingam, and Znati • Wireless sensor networks. Feng Zhao and Leonidas Guibas • Protocols and Architecture for Wireless Sensor Networks. Karl and Willig\ • Wireless Sensor Networks. Bulusu and Jha • Topology control in wireless ad hoc and sensor networks. Santi • Handbook of sensor networks: algorithms and architectures. Ed. Stojmenovic • Ad Hoc wireless networks. Murthy and Manoj. • Wireless Sensor Networks. Edgar and Callaway • Handbook of sensor networks. Editors: Ilyas and Mahgoub

10. Overview – today Propagation of wireless signals Energy MAC protocols Routing Transport Applications Localization Tracking Time synchronization Data Gathering Processing Compression Fusion Architecture Topics (approximate)

11. Today: Introduction • Sensor networks. • Definition, motivation, examples • Challenges. • Architecture and design Issues.

12. What are sensor networks? • Networks of devices that are able to sense the environment, perform on-board computation, (and communicate) • Why? Because we can: Technology • Circuit integration. • Ability to integrate more functions into chip with lower energy • Wireless communication. • Better communication theory • Better devices • Bit-rates are slowly increasing • Transmission power is decreasing • Sensor technology

13. Result: sensing nodes PC-104+ UCLA TAG UCB Mote

14. Embedded Networked Sensing • Micro-sensors, • on-board processing, • wireless interfaces • small scale and low cost => large numbers of sensor fields can be deployed • monitor phenomena “up close”. • Enables spatially and temporally dense monitoring. • Nyquist Sampling – you must sample often enough (in time or space) • Inverse problems are very difficult, e.g., by sensing the temperature at a few places, determine the temperature everywhere (numerically unstable, i.e., errors are amplified). Instead, directly sense the temperature everywhere. • Wireless interface allow little infrastructure – easy deployment • Wireless interface allow cooperation and distributed computing

15. Instability of an inverse problem Contaminate sources Wind direction Air sensors Objective: use the sensors to determine the source of the contaminate. for T=1:.25:10 G=zeros(21,21); for i=-10:10 G(i+11,:) = normpdf([-10:10]-i,0,T); end u0=sin([-10:10]/10*pi)'; %rand(21,1); u2=G*u0; u0hat = inv(G)*u2; u0NoiseEst = inv(G)*(u2+rand(size(u2))*.01); figure(1) clf plot(u0) hold on plot(u2,'g') plot(u0hat,'r') legend('original','observed','inverse') axis([0,21,-1,1]); title(sprintf('Inverse problem at %.2f ',T)) T pause end x Assume that the density at (x,y) is y where U is the flow into the environment at the source Solution: put the sensor near to the source

16. Vision Embed numerous sensing nodes to monitor and interact with physical world Network these devices so that they can execute more complex tasks. Note that these two problems are very different. Different scales and different requirements. It is difficult to lump them into a single “sensors” group.

17. Sensor networks applications…

18. Vision: “Embed the World” • Buildings self-detect and self-correct from structural faults (e.g., weld cracks). • Schools detect airborne toxins at low concentrations, trace contaminant transport to source. • Buoys alert swimmers to dangerous bacterial levels (or an excellent set of waves coming, brah). • Earthquake-rubbled building infiltrated with robots and sensors: locate survivors, evaluate structural damage. • Ecosystems infused with chemical, physical, acoustic, image sensors to track global change parameters. • More??

19. Buoys along the east coast

20. Sensor to assist surfers!

21. Sensors are not always small… • For example, Umass’s CASA (Collaborative Adaptive Sensing of the Atmosphere). Network of meteorological radars to observe, detect, and predict atmospheric phenomena.

22. Deployments • Ecological Habitat Monitoring • UCB/Intel Berkeley: Great Duck Island • UCLA-CENS: James Reserve • Princeton: ZebraNet in Kenya • Structural Monitoring • UCLA-CENS: Factor Building • USC: Networked SHM • UCB/Intel Berkeley: SF Golden Gate Bridge • UD • Biomedical Applications • Artificial retina • “Bio-monitors” • Industrial and Commercial Apps • Ember Corp: Thermal Process Control, Shipment Tracking • CCM

23. Environmental monitoring • Petrel habitat on Great Duck Island in Maine. • Questions to answer: • Usage pattern of nesting burrows over the 24-72 hour cycle. • Changes in the burrow and surface environmental parameters. • Differences in the micro-environments with and without large numbers of nesting petrels.

24. Hierarchical deployment

25. Sensors • Mica platform • Atmel AVR w/ 512kB Flash • 916MHz 40kbps RFM Radio • Range: max 100 ft • Affected by obstacles, RF propogation • 2 AA Batteries, boost converter • Mica weather board – “one size fits all” • Digital Sensor Interface to Mica • Onboard ADC sampling analog photo, humidity and passive IR sensors • Digital temperature and pressure sensors • Designed for Low Power Operation • Individual digital switch for each sensor • Designed to Coexist with Other Sensor Boards • Hardware “enable” protocol to obtain exclusive access to connector resources • Packaging • Conformal sealant + acrylic tube • Placement • Place above ground and in burrows (propagation?)

26. Gateway • Communicate with sensor and base station. • Solar powered (sensors are just battery powered). • Directional antenna pointed toward base station.

27. Base station • Laptops • In lighthouse keepers house. • Log all data and transmit via satellite to D.C. and then on to the Internet.

28. Smart Dust • Design goals • Cubic millimeter. • Very low energy. • Result: sensor package containing: • Sensors • Optical transmitter (passive and active) and receiver • Signal processing • Solar power source

29. Smart dust applications • Environmental monitoring. • Insects. • Meteorological phenomena. • Special operations.

30. Smart dust components

31. ModulatedDownlinkDataor BeamforUplink BeamforUplink Smart dust: passive transmission UnmodulatedInterrogation Lens Photo- detector Downlink Laser Downlink DataIn DataOut Uplink Signal Selection and Processing DataIn CCD Corner-Cube Image Lens Retroreflector ModulatedReflected Sensor Array DustMote Uplink Uplink ... Data Data High power laser emitted from BS for downlink and uplink communication. Out Out 1 N Base-StationTransceiver

32. Passive transmissions • Reflect illuminating beam (from BS) back encoding data. • BS decodes data by reading the “on” and “off” reflections. • Rates of up to 1 kbps over 150m. • Low power sensor power • But, uninterrupted LoS with BS. • A single CCD can decode multiple communications at the same time. • Each CCD element can “see” a small region of space. Each element can decode one communication. • Spatial multiplexing.

33. RFID • RFID uses backscatter - Another passive transmission technique. • RADAR • Send a beam and receive reflections. • Physical radar • Put my hand out and hit what is there. • Instead of DC, I could use AC and move my hand back and forth. I could sense things just the same. However, if what I am hitting resonates at the frequency my hand moves, then the thing I am hitting will start oscillating. • A receiving antenna is not just a receiver. If current is moving along the antenna, then it is transmitting as well. • If the circuit that the antenna is attached to has resonates at the carrier frequency, then this circuit will oscillate. These oscillation will cause RF transmissions. • The RFID can switch the circuit to modulate the transmission.

34. Biomedical applications • Health monitors. • Glucose level. • Digestive system. • Vascular system, etc. • Artificial retina.

35. Sensors for vision

36. Today: Introduction • Sensor networks. • Definition, motivation, examples • Challenges. • Architecture and design Issues.

37. Challenges • Energy • Self-configuring/adapting • Data processing • Scalability

38. Energy • Sensors may require long life times • Great Duck Island required 9 months • If embedded in highways, 10 years is required • Pacemaker (not just a sensor!) last 5-10 years • (supervisory control and data acquisition (SCADA))

39. Energy • Sensors may require long life times • Great Duck Island required 9 months • If embedded in highways, 10 years is required • Pacemaker (not just a sensor!) last 5-10 years • (supervisory control and data acquisition (SCADA)) • Approaches • Low duty cycle systems. • Sleep: deep sleep (everything off), listening but not transmitting, periodic listening • Increases delay => impacts QoS • Nodes must be synchronized • Requires good clocks (which require more power) • As battery power drops, clocks may experience severe drift, reducing effective lifetime

40. Energy • Sensors may require long life times • Great Duck Island required 9 months • If embedded in highways, 10 years is required • Pacemaker (not just a sensor!) last 5-10 years • (supervisory control and data acquisition (SCADA)) • Approaches • Low duty cycle systems. • Sleep: deep sleep (everything off), listening but not transmitting, periodic listening • Increases delay => impacts QoS • Nodes must by synchronized • Requires good clocks (which require more power) • As battery power drops, clocks may experience severe drift, reducing effective lifetime • Low bit-rate • Low power transmissions require low bit-rate

41. Energy • Sensors may require long life times • Great Duck Island required 9 months • If embedded in highways, 10 years is required • Pacemaker (not just a sensor!) last 5-10 years • (supervisory control and data acquisition (SCADA)) • Approaches • Low duty cycle systems. • Sleep: deep sleep (everything off), listening but not transmitting, periodic listening • Increases delay => impacts QoS • Nodes must by synchronized • Requires good clocks (which require more power) • As battery power drops, clocks may experience severe drift, reducing effective lifetime • Low bit-rate • Low power transmissions require low bit-rate • Complicated communication schemes • Nodes can cooperate to transmit far with low power. • Advanced data compression • However, CPU uses power as well. But CPU power usage is decreasing as technology advances.

42. Energy • Sensors may require long life times • Great Duck Island required 9 months • If embedded in highways, 10 years is required • Pacemaker (not just a sensor!) last 5-10 years • (supervisory control and data acquisition (SCADA)) • Approaches • Low duty cycle systems. • Sleep: deep sleep (everything off), listening but not transmitting, periodic listening • Increases delay => impacts QoS • Nodes must by synchronized • Requires good clocks (which require more power) • As battery power drops, clocks may experience severe drift, reducing effective lifetime • Low bit-rate • Low power transmissions require low bit-rate • Complicated communication schemes • Nodes can cooperate to transmit far with low power. • Advanced data compression • However, CPU uses power as well. But CPU power usage is decreasing as technology advances. • Efficient protocols • Avoid retransmissions • Avoid end-to-end retransmission with link layer retransmissions and data caching • Avoid contention • FDM • TDM

43. Energy • Approaches • Renewable power/scavenging. • Solar energy. • Mechanical vibrations (sneakers) • Radio-Frequency inductance (RFID) • Infrared inductance (passive optical)

44. Self-configuring/adapting • Ad hoc deployment; inaccessible areas; • E.g, dropped from airplane • Adapt to unpredictable environment. • E.g., nodes break, crash, run out of power (consider a deployment where each node will last only a week, but nodes come out of hibernation at random times so the network has a lifetime of several months (see HW on next page)) • Unattended, untethered • There is no one to reboot … • Fault tolerant and robust • approaches • Each sensor operate autonomously from neighbors. • Overlapped services area. • No single point of failure.

45. Homework • Suppose that there are N sensor. • Each sensor turns on at time t where t is a random variable that is uniformly distributed between 0 and T. • Once on, the sensor will remain on for  seconds. • Find N (as a function of T and ) such that at time T/2, the average number of on sensors is M. • Hint: • What is the probability that a particular sensor will be on at time T/2? • Use binomial distribution

46. Challenges for embedded biomedical sensors: • Limited capabilities: power, processing, storage, and communication. • Continuous operation. • Robustness and fault tolerance. • Scalabilty. • Self-configuring, self-managing, self-healing. • Data-related issues.

47. Application-specific issues • Material Constraints. • Bio-Compatibility. • Inconspicuous. • Imitative of the environment. • Detect-proof: e.g. stealth flight. • Security. • Privacy. • Interference. • Regulatory issues • Such as FDA requirements.

48. Data processing • Cooperation • Exploit computation near data to reduce communication. • Collaborative signal processing • E.g., nearby images are combined to determine the exact location of an object. The position of the object is the data sent to the base station, not the images. • Data aggregation/compression • If data is spatially correlated, then data can be aggregated and compressed, taking advantage of correlation

49. Data processing • Cooperation • Exploit computation near data to reduce communication. • Collaborative signal processing • E.g., nearby images are combined to determine the exact location of an object. The position of the object is the data sent to the base station, not the images. • Data aggregation/compression • If data is spatially correlated, then data can be aggregated and compressed, taking advantage of correlation • Limited computation and storage capabilities • Error propagation – decrease fault tolerance • The more sensors a process uses, the lower the robustness but more efficient. • Complicated cooperation may require intensive communication. • Heterogeneous power dissipation and lifetime • Nodes closer to base station must carry more data and are also in a better position to aggregate data. But these will expend energy. • Trade-off between latency and energy

50. Data processing • Distributed representation/storage • Data Centric Protocols, in-network processing: • Interpretation of spatially distributed data (Per-node processing alone is not enough). • Network performs in-network processing based on distribution of data. • Queries automatically directed towards nodes that maintain relevant/matching data. • Pattern-triggered data collection • Multi-resolution data storage and retrieval. • E.g., many nodes hold general information, thus it is easy to get. • More detailed information requires contacting more nodes • Highly detailed information requires commutation with a large number of nodes. • If mostly low resolution data is required, then such a scheme is very useful • low resolution = the enemy is crossing the border • Medium resolution = the enemy is in the north • High resolution = there is a enemy truck at the corner of Delaware and S. Chapel st. • Distributed edge/feature detection. • Index data for easy temporal and spatial searching. • Finding global statistics (e.g., distribution).