1 / 11

Low Power Design for Wireless Sensor Networks

Low Power Design for Wireless Sensor Networks. Aki Happonen. Table of Contents. Introduction Digital Design RF Design Conclusions. Many cases wireless sensors are deployed to remote location without capability to replace battery.

butlerc
Download Presentation

Low Power Design for Wireless Sensor Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Low Power Design for Wireless Sensor Networks Aki Happonen

  2. Table of Contents • Introduction • Digital Design • RF Design • Conclusions

  3. Many cases wireless sensors are deployed to remote location without capability to replace battery. One of the key elements for distributed sensors is long lifetime covering both reliability and energy efficiency. This presentation covers low power design methods – focus on digital design Introduction source:http://bwrc.eecs.berkeley.edu/People/Faculty/jan/presentations/hotchips1.pdf

  4. One key element in digital design is energy-flexibility trade-off The most efficient solution is Application Specific IC while the worst energy efficiency is in synthesizable processors Digital Design - Efficiency [J. M. Rabaey 2000]

  5. Digital Design – Asynchronous • Operating voltage is the key element in energy consumption – lower the voltage lower the power consumption • Asynchronous design is one method to adopt lower operating voltage and lower clock frequency • Two methods for data path: single rail and dual rail

  6. In single-rail design controller generates initial request signal. Request signal goes through delay that is matched to processing delay and it is also latching signal for output. Acknowledge is generated by delaying request signal by the time latching the output takes An advantage of single rail design is that synchronous designs’ blocks could be used so data paths have good area constraints. Digital Design – Single Rail

  7. In dual-rail design data is encoded using two wires for each bit. Codes “01” and “10” present “1” and “0” data values and code “00” represents spacer or idle state. This is robust method that guarantees correct operation with arbitrary delays in the circuit or logic. A disadvantage of dual-rail logic is larger area due the two wires per bit encoding Digital Design – Dual Rail

  8. DVS allows the processor operating voltage, and frequency to be reduced when workload levels are low Challenge: How to get the optimum voltage? Huge power saving potential: 53% savings [Sinha A. et al] Current consumption is not dependent on code – only voltage and clock frequency matters Dynamic Voltage Scaling (DVS)

  9. One important issue in power management is to minimize processing activity variation. Battery lifetime decreases as a function of increase in workload variance even if the average workload remains fixed. Processing Load

  10. Power amplifier dominates total power budged if the transmission range is more than 10 meters But short-range communication having gigahertz carrier frequency the radio the frequency synthesizer dominates power rather than the actual transmit power In packet based communication the start-up time of radios start to dominate in energy consumption Table shows low power design examples for BT RF Design

  11. Conclusions • The most attractive technology to reduce power consumption is dynamic voltage scaling. • In digital design energy per operation scales with technology but communication energy per transmitted bit does not scale at the same rate. • Compute do not communicate. • In the end implementation selections will be minor issue if the system level constraints are wrong.

More Related