370  Energy Management and Duty Cycling

370.1 Learning Objectives

By the end of this chapter, you will be able to:

  • Analyze energy consumption profiles: Quantify power draw across radio, sensing, processing, and sleep states
  • Apply conservation strategies: Implement duty cycling, data reduction, and topology control techniques
  • Compare MAC protocols: Evaluate S-MAC (synchronous) vs B-MAC/X-MAC (asynchronous) duty cycling
  • Design energy-aware systems: Balance trade-offs between energy, latency, reliability, and throughput
  • Calculate network lifetime: Use FND, HND, and LND metrics for deployment planning
  • Evaluate energy harvesting: Determine when harvesting outperforms battery-only solutions

370.2 Characteristics of Sensor Systems

⏱️ ~10 min | ⭐⭐ Intermediate | 📋 P05.C31.U04

Sensor systems encompass the complete stack from physical sensing to data interpretation, with characteristics that determine their effectiveness and applicability.

370.2.1 System-Level Characteristics

Scalability: Ability to function effectively as network size grows from tens to thousands of nodes.

Challenges: - Routing complexity increases with node count - Data aggregation and processing load - Network management and configuration - Address space and identifier management

Solutions: - Hierarchical architectures (clustering) - Scalable routing protocols (geographic, hierarchical) - Distributed data aggregation - Self-organizing capabilities

Reliability: Ensuring consistent operation despite node failures, communication errors, and environmental challenges.

Approaches: - Redundancy: Multiple sensors measuring same phenomenon - Multi-path routing: Alternative communication paths - Fault detection and recovery mechanisms - Data validation and error correction

Robustness: Operating effectively under varying conditions, interference, and unexpected events.

Techniques: - Adaptive protocols adjusting to conditions - Interference mitigation - Environmental calibration - Graceful degradation under stress

Latency: Time between event occurrence and system response or user notification.

Factors: - Sensing frequency and processing time - Multi-hop routing delays - Gateway processing and cloud transmission - Application-specific requirements (real-time vs. batch)

Accuracy and Precision: Quality of measurements and consistency of readings.

Considerations: - Sensor calibration and drift - Environmental interference - Data fusion from multiple sensors - Trade-offs with power consumption

370.2.2 Network Characteristics

Topology: Physical and logical arrangement of nodes.

Common Topologies: - Star: Nodes communicate directly with central gateway - Tree/Hierarchical: Multi-level structure with cluster heads - Mesh: Nodes form multi-hop network with multiple paths - Hybrid: Combining topologies for optimization

Density: Number of nodes per unit area.

Implications: - High density: Better coverage, redundancy, but increased interference and complexity - Low density: Energy efficient, but coverage gaps and reduced reliability

Connectivity: Degree to which nodes can communicate directly or through multi-hop paths.

Metrics: - Average node degree (number of neighbors) - Network diameter (maximum hops between nodes) - Connectivity probability

Coverage: Extent to which monitored area is sensed by nodes.

Types: - Area Coverage: Every point in region monitored by at least k sensors - Barrier Coverage: Detecting intrusions crossing monitored boundary - Point Coverage: Monitoring specific locations or targets

TipDesign for Hotspot Avoidance from Day One

In multi-hop WSNs, nodes near the sink (gateway) become “hotspots” that relay traffic from all other nodes, depleting their batteries 10-100x faster than edge nodes. When hotspot nodes die, the entire network becomes disconnected despite most nodes having plenty of battery remaining. Prevent this by deploying multiple sinks to distribute load, use mobile sink nodes that relocate periodically, implement energy-aware routing that avoids low-battery nodes, or overprovision hotspot zones with more nodes or mains-powered relays. A 100-node agricultural WSN avoided complete failure by deploying 3 sinks instead of 1, extending network lifetime from 3 months to over 2 years.

370.2.3 Data Characteristics

Data Rates: Volume of data generated and transmitted per time unit.

Variation: - Event-driven: High rates during events, idle otherwise - Periodic: Constant sampling intervals - Query-driven: On-demand measurements

Data Aggregation: Combining data from multiple sources to reduce transmission volume and extract insights.

Techniques: - Compression: Reducing data size before transmission - Fusion: Combining readings from multiple sensors - Summarization: Statistical summaries (average, min, max, variance) - Filtering: Removing redundant or outlier data

Data Quality: Accuracy, completeness, consistency, and timeliness of collected data.

Quality Factors: - Sensor calibration and accuracy - Missing data handling - Outlier detection and correction - Timestamp synchronization

370.2.4 Security Characteristics

Threats: - Eavesdropping on wireless communications - Node capture and tampering - Denial of service attacks - False data injection - Routing attacks

Security Requirements: - Confidentiality: Protecting data from unauthorized access - Integrity: Ensuring data authenticity and preventing tampering - Authentication: Verifying node and user identities - Availability: Ensuring network remains operational

Security Mechanisms: - Encryption (AES, lightweight ciphers) - Message authentication codes (MAC) - Secure key management and distribution - Intrusion detection systems - Physical tamper resistance


370.3 Energy Management

⏱️ ~15 min | ⭐⭐⭐ Advanced | 📋 P05.C31.U05

Energy is the most critical resource in battery-powered WSNs, fundamentally limiting network lifetime and capabilities. Effective energy management is essential for practical deployments.

370.3.1 Energy Consumption Profile

Radio Communication (Dominant Consumer): - Transmission: 10-50 mW typical - Reception: 10-40 mW (often comparable to transmission) - Idle listening: 1-20 mW (significant waste in low-traffic networks)

Sensing: - Simple sensors (temperature): < 1 mW - Complex sensors (camera, GPS): 10-100+ mW - Sensor activation and stabilization time

Processing: - Active computation: 1-10 mW - Sleep mode: 1-100 μW - Deep sleep: < 1 μW

Memory Access: - Flash write operations: High energy cost - RAM access: Relatively low cost

370.3.2 Energy Conservation Strategies

Duty Cycling: Alternating between active and sleep periods to reduce average power consumption.

Approaches: - Time-based: Fixed sleep/wake schedules - Event-driven: Wake on external interrupts (sensors, messages) - Demand-driven: Wake based on predicted activity or queries

Challenges: - Latency increase due to sleep periods - Synchronization for communication - Balancing energy savings vs. responsiveness

Data Reduction: Minimizing amount of data transmitted to reduce communication energy.

Techniques: - Local processing and filtering - Data compression - In-network aggregation - Adaptive sampling rates - Threshold-based reporting (only significant changes)

Topology Control: Managing network topology to optimize energy consumption.

Methods: - Transmission power adjustment - Reducing node degree (number of neighbors) - Clustering and hierarchy formation - Sleep scheduling coordination

Routing Optimization: Selecting energy-efficient paths for data delivery.

Strategies: - Minimum energy routing - Load balancing to avoid hotspots - Geographic routing to minimize hops - Multi-path routing for reliability

Energy Harvesting: Supplementing battery power with ambient energy sources.

Geometric illustration of energy harvesting options for wireless sensor nodes showing solar panels, piezoelectric vibration harvesters, thermoelectric generators, and RF energy collection circuits, with arrows indicating energy flow to battery and power management circuits for sustainable node operation.

WSN Energy Harvesting
Figure 370.1: Energy harvesting options for WSN nodes enabling extended or perpetual operation through ambient energy capture.

Sources: - Solar (outdoor deployments) - Vibration (machinery, bridges) - Thermal (temperature gradients) - RF energy harvesting - Wind or water flow

Challenges: - Intermittent availability - Energy storage requirements - Harvester efficiency - Cost and size constraints

WarningMesh Networks Aren’t Always the Answer

Developers often default to mesh topologies assuming “more paths = better reliability,” but mesh networks introduce significant energy and complexity costs. Each node must maintain routing tables, handle relayed traffic from neighbors (consuming energy), and suffer from the broadcast storm problem where route discovery floods propagate through the network. For many applications, simpler star or tree topologies with strategic gateway placement provide 90% of mesh benefits at 10% of the energy cost and complexity. Use mesh only when deployment area genuinely requires multi-hop communication beyond gateway range, or when mobility and dynamic topology changes are frequent. Consider hybrid approaches: mesh backbone with star clusters, providing scalability without universal mesh overhead.

370.3.3 Network Lifetime Metrics

First Node Death (FND): Time until first node exhausts energy. Critical for applications requiring full coverage.

Half Nodes Dead (HND): Time until 50% of nodes depleted. Indicates significant degradation.

Last Node Death (LND): Complete network cessation. Less relevant for redundant deployments.

Network Coverage Lifetime: Duration maintaining required coverage and connectivity, accounting for node failures.

370.3.4 Energy-Aware Protocols

LEACH protocol overview
Figure 370.2: LEACH (Low-Energy Adaptive Clustering Hierarchy) protocol overview - distributed cluster-based routing
LEACH protocol operation
Figure 370.3: LEACH protocol operation showing cluster head selection and data aggregation
LEACH protocol rounds
Figure 370.4: LEACH protocol rounds showing setup phase and steady-state data transmission phases
Multi-hop routing path
Figure 370.5: Multi-hop routing path in WSN showing data forwarding from source to sink through intermediate nodes

MAC Protocols: Coordinating medium access to minimize idle listening and collisions.

Examples: - S-MAC (Sensor-MAC): Coordinated sleep schedules - B-MAC (Berkeley MAC): Low-power listening with preambles - RI-MAC: Receiver-initiated communication - IEEE 802.15.4: CSMA/CA with optional beacon mode

Routing Protocols: Energy-aware path selection and load distribution.

Examples: - LEACH (Low-Energy Adaptive Clustering Hierarchy): Randomized cluster head rotation - PEGASIS (Power-Efficient GAthering in Sensor Information Systems): Chain-based routing - TEEN (Threshold sensitive Energy Efficient sensor Network): Event-driven reporting - Geographic routing: Position-based forwarding

Cambridge lecture slide explaining LEACH (Low-Energy Adaptive Clustering Hierarchy) protocol where sensor nodes self-organize into clusters with rotating cluster heads that aggregate data from member nodes and transmit to base station, distributing energy consumption to extend network lifetime

LEACH clustering protocol showing cluster head selection and rotation for energy-balanced WSN operation

Source: University of Cambridge, Mobile and Sensor Systems Course (Prof. Cecilia Mascolo)


370.4 Radio Duty Cycling

⏱️ ~12 min | ⭐⭐⭐ Advanced | 📋 P05.C31.U06

Radio duty cycling is one of the most effective energy conservation techniques in WSNs, reducing the time transceivers spend in energy-consuming states.

370.4.1 Duty Cycling Fundamentals

Duty Cycle Definition: The fraction of time a node’s radio is active (transmitting, receiving, or listening).

\[\text{Duty Cycle} = \frac{\text{Active Time}}{\text{Total Time}}\]

Example: A node awake 10ms every 100ms has a 10% duty cycle.

Impact: Reducing duty cycle from 100% to 1% can extend battery lifetime by 10-100x, depending on the relative power consumption of radio vs. other components.

Cambridge lecture slide on dynamic duty cycling explaining how refined strategies allow sensors with more packets to stay awake longer while others sleep more, comparing synchronized protocols like S-MAC that negotiate schedules versus asynchronous protocols like B-MAC and X-MAC that use preamble sampling

Dynamic duty cycling overview showing two main approaches: Synchronized protocols (e.g., S-MAC) that negotiate schedules among neighboring nodes, and Asynchronous protocols (e.g., B-MAC, X-MAC) that rely on preamble sampling to connect transmitters to receivers

Source: University of Cambridge - Mobile and Sensor Systems (Prof. Cecilia Mascolo)

370.4.2 Duty Cycling Approaches

Synchronous Duty Cycling: Nodes coordinate wake/sleep schedules to ensure communication opportunities.

Characteristics: - Nodes wake up simultaneously - Requires clock synchronization - Lower latency for multi-hop communication - Examples: S-MAC, T-MAC

S-MAC duty cycling protocol
Figure 370.6: S-MAC protocol - synchronous duty cycling with coordinated sleep schedules for WSN energy conservation

Cambridge lecture slide showing S-MAC protocol architecture with timeline diagram illustrating wakeup periods, sleep periods, and the active period subdivided into SYNCH, RTS, and CTS phases for coordinated duty cycling in wireless sensor networks

S-MAC (Sensor-MAC) protocol showing the rendez-vous concept where neighboring nodes turn on simultaneously during active periods for packet exchange, with wakeup period containing sleep periods and active phases divided into SYNCH, RTS, and CTS phases

Source: University of Cambridge - Mobile and Sensor Systems (Prof. Cecilia Mascolo)

370.5 S-MAC Protocol: Visual Operation

S-MAC (Sensor MAC) coordinates sleep schedules for energy efficiency.

370.5.1 The S-MAC Cycle

%% fig-cap: "S-MAC Frame Structure showing synchronized duty cycling"
%% fig-alt: "Gantt chart showing S-MAC frame structure with Node A and Node B synchronized through SYNC, RTS/CTS, DATA, and SLEEP phases"
%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#2C3E50', 'primaryTextColor': '#fff', 'primaryBorderColor': '#1a252f', 'lineColor': '#16A085', 'secondaryColor': '#16A085', 'tertiaryColor': '#E67E22'}}}%%
gantt
    title S-MAC Frame Structure
    dateFormat X
    axisFormat %s

    section Node A
    SYNC     :a1, 0, 1
    RTS/CTS  :a2, 1, 2
    DATA     :a3, 2, 4
    SLEEP    :a4, 4, 10

    section Node B
    SYNC     :b1, 0, 1
    RTS/CTS  :b2, 1, 2
    DATA     :b3, 2, 4
    SLEEP    :b4, 4, 10

Figure 370.7: Gantt chart showing S-MAC frame structure with Node A and Node B synchronized through SYNC, RTS/CTS, DATA, and SLEEP phases

370.5.2 Step-by-Step Operation

%% fig-cap: "S-MAC step-by-step operation cycle"
%% fig-alt: "Flowchart showing S-MAC three-phase operation: synchronization with SYNC packets, listen period with RTS/CTS/DATA/ACK exchange, and sleep period with radio off"
%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#2C3E50', 'primaryTextColor': '#fff', 'primaryBorderColor': '#1a252f', 'lineColor': '#16A085', 'secondaryColor': '#16A085', 'tertiaryColor': '#E67E22'}}}%%
flowchart TD
    subgraph sync["1. Synchronization"]
        S1["Nodes exchange SYNC packets"]
        S2["Agree on common schedule"]
    end

    subgraph listen["2. Listen Period"]
        L1["RTS: Request to Send"]
        L2["CTS: Clear to Send"]
        L3["DATA transmission"]
        L4["ACK receipt"]
    end

    subgraph sleep["3. Sleep Period"]
        Z1["Radio OFF"]
        Z2["Timer running"]
    end

    sync --> listen
    listen --> sleep
    sleep -->|"Timer expires"| sync

    style sync fill:#2C3E50,color:#fff
    style listen fill:#16A085,color:#fff
    style sleep fill:#7F8C8D,color:#fff

Figure 370.8: Flowchart showing S-MAC three-phase operation: synchronization with SYNC packets, listen period with RTS/CTS/DATA/ACK exchange, and sleep period with radio off.

370.5.3 Energy Savings

Duty Cycle Listen Time Sleep Time Power Reduction
100% 100% 0% 0% (baseline)
10% 10% 90% ~90%
1% 1% 99% ~99%

370.5.4 Key Insight

Nodes that hear the same SYNC adopt the same schedule, forming virtual clusters that can communicate efficiently.

Preamble sampling duty cycling
Figure 370.9: Preamble sampling mechanism for asynchronous duty cycling - sender transmits long preamble until receiver wakes

Advantages: - Predictable communication windows - Efficient for scheduled traffic - Coordinated network operation

Challenges: - Synchronization overhead and drift - Global schedule may not suit all nodes - Less flexibility for event-driven traffic

Asynchronous Duty Cycling: Nodes operate on independent schedules without global synchronization.

Characteristics: - No synchronization required - Senders must account for receiver schedules - Examples: B-MAC, X-MAC, RI-MAC

X-MAC duty cycling protocol
Figure 370.10: X-MAC protocol - asynchronous duty cycling with short preambles and early acknowledgment for energy efficiency

Cambridge lecture slide explaining X-MAC protocol improvements over B-MAC including short preambles for reduced latency and energy, target addressing in preambles to minimize overhearing by non-destination nodes, and inter-preamble wait times for faster communication when receiver wakes early

X-MAC protocol key innovations: short preamble to reduce latency and energy consumption, target address in preamble to minimize overhearing problem, and wait time between preambles to reduce latency when destination is awake before preamble completes

Source: University of Cambridge - Mobile and Sensor Systems (Prof. Cecilia Mascolo)

Mechanisms: - Preamble sampling: Sender transmits long preamble until receiver wakes - Wake-up beacons: Receivers announce availability - Receiver-initiated: Receivers poll for pending messages

Advantages: - No synchronization overhead - Flexible and adaptive - Supports mobile and heterogeneous networks

Challenges: - Potential latency increase - Energy cost of preambles or polling - Variable message delivery time

Hybrid Approaches: Combining synchronous and asynchronous techniques.

Examples: - Local synchronization within clusters, asynchronous between clusters - Schedule-based for regular traffic, on-demand for events - Adaptive switching based on traffic patterns

370.5.5 Advanced Duty Cycling Techniques

Adaptive Duty Cycling: Dynamically adjusting duty cycle based on conditions.

Parameters: - Traffic load (increase cycle during high activity) - Residual energy (reduce cycle when battery low) - Time of day (circadian patterns in environmental monitoring) - Event detection (increase sampling rate during events)

Predictive Duty Cycling: Using historical data and prediction models to optimize schedules.

Approaches: - Machine learning to predict traffic patterns - Correlation-based sensing (sensors with correlated readings coordinate) - Event prediction to pre-activate relevant nodes

Hierarchical Duty Cycling: Different duty cycles for different node roles.

Structure: - Cluster heads: Higher duty cycle for availability - Regular nodes: Lower duty cycle for energy conservation - Gateway nodes: Always-on or high duty cycle

Wake-on-Radio: Special low-power radio listens continuously, waking main radio when messages arrive.

Characteristics: - Main radio sleeps indefinitely - Wake-up radio consumes micro-watts - Triggered wake-up for main radio - Ultra-low average power consumption

Technologies: - Dedicated wake-up receivers - Ultra-low-power always-on circuits - RF energy harvesting for wake-up

370.5.6 Performance Trade-offs

Energy vs. Latency: Lower duty cycles save energy but increase message delivery latency.

Mitigation: - Multi-hop forwarding during wake periods - Predictive wake-up for urgent messages - Adaptive cycles based on message priority

Energy vs. Reliability: Sleeping nodes may miss messages or events.

Solutions: - Redundant sensing coverage - Message retransmission mechanisms - Acknowledgment-based reliability - Wake-up on event detection

Energy vs. Throughput: Limited active time constrains data transmission capacity.

Balancing: - Efficient data aggregation and compression - Adaptive duty cycle during high-traffic periods - Buffering and batch transmission - Priority-based scheduling


370.6 Knowledge Check

Test your understanding of WSN fundamental concepts with these questions covering architecture, sensor nodes, and network topologies.

Question: Which of the following best describes the three-tier architecture of a Wireless Sensor Network?

Question: Which option best describes the classic three-tier WSN architecture?

Explanation: C. Sensors feed a gateway/sink (aggregation + protocol bridging), which then connects to backend systems for storage/analytics.

Correct Answer: C) Sensor Nodes → Gateway/Sink → Backend Systems

Explanation: The three-tier WSN architecture consists of:

  1. Tier 1 - Sensor Nodes: Collect environmental data, perform local processing and filtering, and transmit data to nearby nodes or gateways. These are typically battery-powered with limited resources.

  2. Tier 2 - Gateway/Sink Nodes: Aggregate data from multiple sensor nodes, provide protocol translation (e.g., 802.15.4 to Wi-Fi/Ethernet), perform edge processing and data fusion, and connect the sensor network to external networks.

  3. Tier 3 - Backend Systems: Cloud or on-premise servers that store and analyze large-scale data, provide user interfaces and applications, and enable remote management and configuration.

This architecture enables efficient data collection from distributed sensors while managing the resource constraints (energy, bandwidth, processing) at each tier appropriately.

Question: A sensor node’s communication subsystem (radio transceiver) typically consumes what fraction of total power compared to sensing and processing combined?

Question: How much power does the radio typically consume vs sensing + processing combined?

Explanation: C. Radio transmission is usually the dominant energy cost, which is why WSNs minimize airtime.

Correct Answer: C) 3-30 times more (3:1 to 30:1 ratio)

Explanation: The communication subsystem is the dominant energy consumer in sensor nodes:

Subsystem Typical Power Draw
Sensing Unit 1-10 mW
Processing Unit (MCU) 10-100 mW
Communication Unit (Radio) 50-300 mW

The radio transceiver typically consumes 3-30× more power than sensing and processing combined. This fundamental asymmetry drives nearly all WSN protocol design decisions:

  • Duty cycling: Sleep the radio as much as possible
  • Data aggregation: Process locally to reduce transmissions
  • In-network processing: Compute at nodes rather than transmit raw data
  • Transmission power control: Use minimum power needed

This is why the design principle “minimize radio usage” is paramount in WSN design. Every bit transmitted costs approximately 1000× more energy than computing locally.

Question: In a WSN deployment, you need to monitor a large agricultural field. Which topology would provide the best combination of energy efficiency, scalability, and fault tolerance?

Question: Which topology best balances energy efficiency, scalability, and fault tolerance for a large agricultural WSN?

Explanation: C. Clustering reduces hotspot load via aggregation and can rotate energy-heavy roles across nodes.

Correct Answer: C) Cluster/Hierarchical topology - nodes grouped into clusters with rotating cluster heads

Explanation: For large agricultural deployments, cluster/hierarchical topology offers the best balance:

Topology Pros Cons
Star Simple, low latency Limited range, gateway bottleneck, single point of failure
Mesh Redundant paths, fault tolerant High overhead, routing complexity, energy-intensive
Cluster Scalable, energy-efficient, reduces hotspots Moderate complexity, cluster head burden
Linear Simple for narrow areas Poor fault tolerance, high latency

Why Cluster topology wins for agriculture:

  1. Energy Efficiency: Only cluster heads perform long-range transmission to the gateway; regular nodes use short-range communication to their cluster head
  2. Scalability: Can add clusters without affecting existing network structure
  3. Load Balancing: Rotating cluster head roles (like LEACH protocol) distributes energy consumption evenly
  4. Data Aggregation: Cluster heads aggregate data from members, reducing total transmissions by 70-90%
  5. Fault Tolerance: If a cluster head fails, a new one can be elected from remaining members

For a 50-hectare vineyard with 200 sensors, hierarchical clustering with 10 clusters of 20 nodes each would reduce gateway traffic by 90% compared to flat routing.

Question: Why does multi-hop routing typically save energy compared to direct transmission in WSNs, even though it requires more total transmissions?

Question: Why can multi-hop save energy vs a single long transmission?

Explanation: B. Path loss grows superlinearly with distance, so splitting a long link into shorter hops can reduce total transmit energy (at the cost of relaying overhead).

Correct Answer: B) Radio transmission power scales with distance^n (where n=2-4), making multiple short hops more efficient

Explanation: Radio transmission follows the path loss model:

\[P_{tx} \propto d^n\]

where \(d\) is distance and \(n\) is the path loss exponent (typically 2-4 for wireless propagation).

Energy Comparison Example (100m to sink):

Approach Calculation (n=4) Relative Energy
Direct: 1 hop × 100m \(100^4 = 100,000,000\) Baseline
Multi-hop: 10 hops × 10m \(10 × 10^4 = 100,000\) 1000× savings!

Key insight: Breaking a long transmission into multiple short hops dramatically reduces total energy because of the exponential relationship between distance and power.

However, multi-hop introduces trade-offs: - Higher latency: Each hop adds 10-50ms delay - Hotspot problem: Nodes near the sink relay all traffic, depleting faster - Routing overhead: Maintaining routes consumes energy and bandwidth - Reliability: More hops = more potential failure points

Design guideline: Use multi-hop strategically when nodes are beyond single-hop range, but avoid unnecessary hops. Deploy multiple sinks to keep average path length under 5 hops.

Question: A WSN deployment in a forest fire detection system uses 500 nodes across 100 km². Network lifetime is defined as “time until first node dies” (FND). After 6 months, the first node fails and the network becomes disconnected. What does this scenario illustrate?

Question: What does this scenario illustrate about WSN lifetime metrics?

Explanation: D. If full coverage/connectivity is required, the first node failure (or partition) can be a system-level failure even if most nodes still have energy.

Correct Answer: D) FND metric is critical for coverage-dependent applications; alternative metrics may miss failures

Explanation: This illustrates why choosing appropriate lifetime metrics is critical.

Network lifetime metrics:

Metric Definition Best For
First Node Death (FND) Time until ANY node dies Full coverage required (fire detection, security)
Half Nodes Dead (HND) Time until 50% nodes die Applications tolerating graceful degradation
Last Node Death (LND) Time until ALL nodes die Less useful - network often dysfunctional before this
Network Partition Time (NPT) Time until network splits Connectivity-dependent applications

For fire detection: FND is appropriate because a single dead node creates a blind spot where fires could start undetected.

Solutions to extend network lifetime: - Deploy redundant node coverage (2-3 nodes per area) - Use mobile nodes to fill gaps when nodes fail - Implement scheduled node replacement before battery exhaustion - Add energy harvesting (solar) in accessible locations - Use energy-aware routing to balance load across all nodes

Key insight: Metric choice affects design. Optimizing for FND requires balanced energy consumption across ALL nodes (avoid hotspots), while HND allows some nodes to die early.

370.7 Summary

This chapter covered energy management and duty cycling in wireless sensor networks:

  • Energy Consumption Profile: Radio communication dominates (50-300 mW), followed by processing (10-100 mW) and sensing (1-10 mW)
  • Conservation Strategies: Duty cycling, data reduction, topology control, routing optimization, and energy harvesting
  • Network Lifetime Metrics: FND (first node death), HND (half nodes dead), LND (last node death) for different application requirements
  • Synchronous Duty Cycling: S-MAC coordinates sleep schedules through SYNC packets, enabling predictable communication windows
  • Asynchronous Duty Cycling: B-MAC and X-MAC use preamble sampling, avoiding synchronization overhead but with variable latency
  • Advanced Techniques: Adaptive, predictive, and hierarchical duty cycling; wake-on-radio for ultra-low power
  • Trade-offs: Energy vs latency (sleeping increases delay), energy vs reliability (missed messages), energy vs throughput (limited active time)

370.8 What’s Next

Return to the WSN Overview: Fundamentals index page to review all chapters in this series, or continue to related topics: