13 Communication Paradigms
Minimum Viable Understanding
- WSNs use an N-to-1 convergecast pattern – the opposite of broadcast: While TV broadcasting sends data from 1 source to N receivers (1-to-N), sensor networks send data from N distributed sensors to 1 central sink (N-to-1) – this unique pattern creates specific challenges like sink bottleneck and hotspot problems but enables powerful in-network data aggregation.
- Data aggregation reduces transmissions by 85-95%: Instead of 200 sensors each sending raw 8-byte readings (154 KB/day), hierarchical aggregation through 20 cluster heads computing averages reduces total data to 23 KB/day (85% reduction), extending network lifetime from 3 months to 18+ months because each bit transmitted costs 1000x more energy than computing locally.
- IoT uniquely combines all three communication paradigms: Sensing uses N-to-1 (sensors to cloud), control uses 1-to-N (firmware updates to all devices), and user interaction uses 1-to-1 (phone to smart lock) – understanding which paradigm applies to each data flow enables optimal protocol selection.
Sensor Squad: The Message Relay Race
Sammy the sound sensor is explaining how messages travel in their network. “Think of us like a river system!” he says.
Lila the light sensor is a mountain spring – she produces a tiny trickle of data (her light readings). Max the motion sensor is another spring nearby. Both trickles flow into Bella the bio sensor, who is like a stream – she combines their readings and passes them on.
“All our data flows together, getting bigger and bigger, until it reaches the gateway – that’s like the ocean where all rivers end up!” explains Sammy. “This is called convergecast – many sources, one destination!”
But here’s the clever part: Bella does not just pass on EVERY reading from Lila and Max. She calculates the AVERAGE and sends just ONE number instead of two. That saves half the messages!
“So we’re like a relay race where runners can combine their batons!” Max exclaims. “Instead of 100 runners each running to the finish line, 10 team captains collect 10 batons each and run just once!”
That is exactly how sensor networks save energy through data aggregation – combining data along the way so fewer messages need to be sent over the expensive radio.
For Beginners: Three Ways to Communicate
Communication networks use three basic patterns – and sensor networks introduced a new one to the world:
- Telephony (1-to-1): Like a phone call – one person talks to one other person
- Broadcast (1-to-N): Like a TV station – one source sends to many receivers
- Sensor Networks (N-to-1): Like tax returns – many people send forms to one tax office
| Pattern | Direction | Example | Key Feature |
|---|---|---|---|
| 1-to-1 | Bidirectional | Phone call | Equal peers |
| 1-to-N | Source to many | TV broadcast | Passive receivers |
| N-to-1 | Many to one | Sensor network | Many sources, one collector |
Why this matters: The N-to-1 pattern was new to networking when WSNs emerged. It creates unique challenges (all traffic converges at one point, causing bottlenecks) but also unique opportunities (data can be combined along the way, saving huge amounts of energy). Understanding which pattern your application follows helps you choose the right architecture and protocols.
13.1 Learning Objectives
By the end of this chapter, you will be able to:
- Differentiate the N-to-1 convergecast pattern: Contrast WSN data flow with traditional networking paradigms
- Compare communication paradigms: Distinguish between telephony (1-to-1), broadcast (1-to-N), and sensor networks (N-to-1) with concrete examples
- Calculate data aggregation savings: Derive bandwidth and energy reductions from in-network aggregation at cluster heads
- Map IoT paradigm integration: Illustrate how IoT combines all three communication paradigms in bidirectional architectures
- Diagnose design implications: Solve sink bottleneck, hotspot problem, and scalability challenges with multiple sinks and clustering
- Relate WSN-IoT evolution: Trace how WSNs evolved into and complement modern IoT systems
13.2 Relationship Between Sensor Networks and IoT
Key Concepts
- Core Concept: Fundamental principle underlying Communication Paradigms — understanding this enables all downstream design decisions
- Key Metric: Primary quantitative measure for evaluating Communication Paradigms performance in real deployments
- Trade-off: Central tension in Communication Paradigms design — optimizing one parameter typically degrades another
- Protocol/Algorithm: Standard approach or algorithm most commonly used in Communication Paradigms implementations
- Deployment Consideration: Practical factor that must be addressed when deploying Communication Paradigms in production
- Common Pattern: Recurring design pattern in Communication Paradigms that solves the most frequent implementation challenges
- Performance Benchmark: Reference values for Communication Paradigms performance metrics that indicate healthy vs. problematic operation
Wireless Sensor Networks and the Internet of Things are intimately related yet distinct concepts with significant overlap and complementary characteristics.
13.2.1 Historical Relationship
WSN as IoT Precursor: WSNs emerged before the modern IoT concept, establishing foundational principles: - Networked embedded devices - Autonomous operation - Data-driven decision making - Wireless communication among resource-constrained devices
IoT Evolution: IoT expanded beyond WSNs to encompass: - Broader device types (smartphones, wearables, vehicles, appliances) - Direct internet connectivity - Cloud-centric architectures - Rich user interfaces and applications - Commercial and consumer focus
13.2.2 Commonalities
Distributed Sensing and Actuation: Both involve networks of physically distributed devices monitoring and affecting the environment.
Wireless Communication: Both rely heavily on wireless technologies for connectivity and data exchange.
Data-Driven Operation: Both collect and analyze data to extract insights and drive intelligent actions.
Resource Optimization: Both face challenges in energy efficiency, bandwidth usage, and computational limitations.
Autonomy and Self-Organization: Both require devices to operate autonomously with minimal human intervention.
13.2.3 Distinctions
Connectivity:
- WSN: Often operates as isolated network; indirect internet connectivity through gateways
- IoT: Devices typically have direct or one-hop internet connectivity
Device Diversity:
- WSN: Homogeneous nodes optimized for specific sensing tasks
- IoT: Heterogeneous devices with varying capabilities, purposes, and manufacturers
Scale:
- WSN: Dozens to thousands of nodes in localized deployment
- IoT: Billions of devices globally distributed
Application Focus:
- WSN: Specialized monitoring and control (environment, infrastructure, industrial)
- IoT: Broad consumer, commercial, industrial, and smart city applications
Protocol Stack:
- WSN: Specialized protocols optimized for low-power, multi-hop networks (802.15.4, RPL, 6LoWPAN)
- IoT: Internet protocols (IP, HTTP, MQTT, CoAP) with various physical layers
Cloud Integration:
- WSN: Traditional architectures focused on local base stations and servers
- IoT: Cloud-centric with edge computing support
13.2.4 WSN as IoT Component
Complementary Integration: Modern IoT systems often incorporate WSNs as essential components:
Edge Sensing Layer: WSNs provide distributed sensing capabilities at the network edge, feeding data to IoT platforms.
Example: Agricultural IoT system uses WSN for soil moisture monitoring, gateway for data aggregation, and cloud platform for analytics and farmer interfaces.
Specialized IoT Networks: Certain IoT applications are essentially evolved WSNs with internet connectivity.
Example: Smart building environmental monitoring using wireless sensors connected through IoT gateways to cloud-based building management systems.
Hybrid Architectures: Combining WSN principles (energy efficiency, multi-hop routing) with IoT capabilities (cloud connectivity, rich applications).
Example: Smart city infrastructure monitoring uses energy-efficient WSN protocols for sensor communication while providing cloud-based dashboards and APIs.
13.2.5 Convergence Trends
IP-Enabled WSNs: Standards like 6LoWPAN enable IP connectivity in resource-constrained sensor networks, blurring WSN-IoT boundaries.
Edge Computing: Bringing computation closer to sensors aligns with WSN distributed processing principles while supporting IoT scalability.
LPWAN Technologies: Low-Power Wide-Area Networks (LoRaWAN, NB-IoT, Sigfox) combine WSN energy efficiency with IoT wide-area connectivity.
Standardization: Common protocols (MQTT, CoAP) and platforms enable interoperability between WSN and broader IoT ecosystems.
13.3 WSN Communication Paradigm: The N-to-1 Pattern
Understanding wireless sensor networks requires recognizing their fundamental communication paradigm. Unlike traditional networking models, WSNs implement a distinctive N-to-1 (many-to-one) data flow pattern that fundamentally shapes their architecture, protocols, and optimization strategies.
13.3.1 The Three Communication Paradigms
Communication networks can be categorized into three fundamental paradigms based on their data flow patterns:
| Paradigm | Pattern | Direction | Examples | Key Characteristic |
|---|---|---|---|---|
| Telephony | 1-to-1 | Bidirectional | Phone calls, video chat, VoIP | Equal peer relationship |
| Broadcast | 1-to-N | Unidirectional (source→receivers) | TV, radio, multicast streaming | Single source, passive receivers |
| Sensor Networks | N-to-1 | Unidirectional (sources→sink) | WSN, IoT monitoring, telemetry | Many sources, single collector |
13.3.2 The N-to-1 Convergecast Pattern
The convergecast (or many-to-one) pattern is the defining characteristic of sensor network communication:
Definition: Data flows from N distributed sensor nodes through multi-hop paths to 1 central sink (gateway or base station).
Key Properties of N-to-1 Communication:
- Asymmetric Traffic: Most data flows inbound (sensor→sink); minimal outbound traffic (commands, queries)
- Multi-hop Necessity: Sensors often beyond single-hop range of sink, requiring relay through intermediate nodes
- Aggregation Opportunity: Intermediate nodes can combine data, reducing total transmissions
- Sink Bottleneck: All traffic converges at sink, creating potential congestion and energy hotspot
- Tree-like Topology: Natural formation of routing trees rooted at sink
13.3.3 Data Aggregation: The Power of N-to-1
The N-to-1 pattern enables in-network data aggregation—one of WSN’s most powerful energy-saving techniques.
Why Aggregation Matters
Without aggregation: 100 sensors each sending 100 bytes → 10,000 bytes total transmission With aggregation: 100 sensors → 10 aggregators each sending 50 bytes → 500 bytes total (95% reduction!)
Each bit transmitted costs ~1000× more energy than computing locally. Aggregation exploits this ratio.
Common Aggregation Functions:
| Function | Description | Use Case | Compression Ratio |
|---|---|---|---|
| Average | Mean of N readings | Temperature monitoring | N:1 |
| Min/Max | Extreme values only | Threshold alerts | N:1 |
| Count | Number of events | Intrusion detection | N:1 |
| Median | Middle value (outlier-resistant) | Environmental sensing | N:1 |
| Sum | Total accumulation | Energy consumption | N:1 |
| Concatenation | Combine readings | Debugging, raw data | N:N (no reduction) |
Putting Numbers to It
Aggregation compression ratio determines energy savings:
\[\text{Energy Savings} = 1 - \frac{1}{N} = \frac{N-1}{N}\]
where \(N\) is the number of readings aggregated.
Worked example: A cluster head aggregates 10 temperature readings (8 bytes each) into one average (8 bytes): - Without aggregation: 10 × 8 bytes = 80 bytes transmitted - With aggregation: 1 × 8 bytes = 8 bytes transmitted - Compression: 80/8 = 10:1 ratio - Energy savings: \((10-1)/10 = 90\%\) reduction in transmission energy
Try It: Data Aggregation Savings Calculator
Adjust parameters to see how in-network aggregation reduces transmission volume and energy.
13.3.4 Practical Example: Smart Agriculture Monitoring
Consider a precision agriculture deployment monitoring soil moisture across a 50-hectare vineyard:
Deployment Parameters:
- 200 soil moisture sensors deployed in grid pattern
- 1 gateway (sink) at field edge connected to cellular/Wi-Fi
- Sensors sample every 15 minutes
- Each reading: 4 bytes (moisture %) + 4 bytes (timestamp) = 8 bytes
Without Aggregation (Naive Approach):
200 sensors × 8 bytes × 4 samples/hour × 24 hours = 153,600 bytes/day
= ~154 KB/dayWith Hierarchical Aggregation:
Tier 1: 200 sensors → 20 cluster heads (10 sensors each)
Each cluster computes: avg, min, max = 12 bytes
20 clusters × 12 bytes × 4/hour × 24 = 23,040 bytes/day
Tier 2: 20 cluster heads → 1 sink
Already aggregated, minimal additional processing
Total: ~23 KB/day (85% reduction)Energy Impact:
| Metric | Without Aggregation | With Aggregation | Improvement |
|---|---|---|---|
| Daily Transmissions | 19,200 | 1,920 | 10× fewer |
| Network Lifetime | 3 months | 18+ months | 6× longer |
| Bandwidth Usage | 154 KB/day | 23 KB/day | 85% reduction |
| Gateway Load | High (all raw data) | Low (summaries only) | Reduced congestion |
13.3.5 IoT as the Integration of All Three Patterns
Modern IoT systems uniquely combine all three communication paradigms into unified architectures:
How IoT Combines the Paradigms:
| Direction | Paradigm | IoT Function | Example |
|---|---|---|---|
| Uplink | N-to-1 (WSN) | Sensor data collection | 1000 sensors → 1 cloud platform |
| Downlink | 1-to-N (Broadcast) | Firmware updates, commands | 1 cloud → all devices simultaneously |
| Lateral | 1-to-1 (Telephony) | Device-to-device control | Phone → smart lock direct unlock |
| Hybrid | All combined | Complete smart home | Sensors report (N-to-1), phone controls (1-to-1), alerts broadcast (1-to-N) |
The IoT Paradigm Insight
WSNs introduced the N-to-1 pattern to networking. Before sensor networks, networks were dominated by 1-to-1 (telephony/internet) and 1-to-N (broadcast) patterns. WSNs revealed that many real-world sensing applications follow the opposite pattern: many distributed sources feeding into centralized collection points.
IoT’s innovation is seamlessly integrating all three patterns: - Sensing uses N-to-1 (convergecast) - Control uses 1-to-N (broadcast commands) or 1-to-1 (targeted actuation) - User interaction uses 1-to-1 (phone to device)
Understanding which paradigm applies to each data flow enables optimal protocol selection and architecture design.
13.3.6 Design Implications of N-to-1
The N-to-1 pattern creates unique design challenges and opportunities:
Challenges:
- Sink Bottleneck: All traffic converges at sink—congestion, energy depletion, single point of failure
- Hotspot Problem: Nodes near sink relay all traffic, depleting 10-100× faster
- Scalability Limits: Adding sensors increases sink load linearly
- Latency Accumulation: Multi-hop paths add delay at each hop
Solutions:
| Challenge | Solution | Implementation |
|---|---|---|
| Sink bottleneck | Multiple sinks | Deploy 3-5 sinks across large deployments |
| Hotspot problem | Mobile sinks | Sink moves periodically to distribute load |
| Scalability | Hierarchical clustering | LEACH, HEED protocols with rotating cluster heads |
| Latency | Geographic routing | GPSR, greedy forwarding toward sink location |
| Energy balance | Aggregation trees | TAG (Tiny AGgregation) protocol |
Worked Example: Calculating Aggregation Savings
Scenario: Environmental monitoring network with 500 sensors, each producing 16-byte readings every 10 seconds.
Without Aggregation: \[\text{Data Rate} = 500 \times 16 \text{ bytes} \times 6/\text{min} = 48,000 \text{ bytes/min} = 2.88 \text{ MB/hour}\]
With 2-Level Aggregation (50 clusters of 10 sensors each):
Level 1: Each cluster head receives 10 readings (160 bytes), computes average (4 bytes) + min (4 bytes) + max (4 bytes) + count (2 bytes) = 14 bytes output
\[\text{Cluster Output} = 50 \times 14 \text{ bytes} \times 6/\text{min} = 4,200 \text{ bytes/min}\]
Level 2: Sink receives from 50 cluster heads
\[\text{Sink Input} = 4,200 \text{ bytes/min} = 252 \text{ KB/hour}\]
Compression Ratio: \(\frac{2.88 \text{ MB}}{252 \text{ KB}} = 11.4:1\) (91% reduction)
Energy Savings: At 50 nJ/bit transmission energy: - Without: \(2.88 \text{ MB} \times 8 \times 50 \text{ nJ} = 1.15 \text{ J/hour}\) - With: \(252 \text{ KB} \times 8 \times 50 \text{ nJ} = 0.10 \text{ J/hour}\) - Savings: 1.05 J/hour = 91% energy reduction in transmission
13.4 Knowledge Check
Test Your Understanding
Question 1: What communication paradigm is unique to wireless sensor networks?
- 1-to-1 (telephony pattern)
- 1-to-N (broadcast pattern)
- N-to-1 (convergecast pattern)
- N-to-N (peer-to-peer pattern)
Answer
c) N-to-1 (convergecast pattern)
The N-to-1 convergecast pattern is the defining characteristic of sensor network communication. Data flows from N distributed sensor nodes through multi-hop paths to 1 central sink (gateway or base station). Before WSNs, networks were dominated by 1-to-1 (telephony/internet) and 1-to-N (broadcast) patterns. WSNs revealed that many real-world sensing applications follow the opposite pattern: many distributed sources feeding into centralized collection points. This pattern creates specific challenges (sink bottleneck, hotspot problem) but enables powerful optimizations like in-network data aggregation.
Test Your Understanding
Question 2: A vineyard has 200 soil moisture sensors, each sending 8-byte readings every 15 minutes. With hierarchical aggregation through 20 cluster heads, what is the approximate daily data reduction?
- 50% reduction (77 KB/day)
- 70% reduction (46 KB/day)
- 85% reduction (23 KB/day)
- 95% reduction (8 KB/day)
Answer
c) 85% reduction (23 KB/day)
Without aggregation: 200 sensors x 8 bytes x 4 samples/hour x 24 hours = 153,600 bytes/day (~154 KB/day). With hierarchical aggregation: 20 cluster heads each compute average, min, max = 12 bytes per cluster per sample. 20 clusters x 12 bytes x 4/hour x 24 hours = 23,040 bytes/day (~23 KB/day). This is an 85% reduction (from 154 KB to 23 KB). The energy impact is even more dramatic: network lifetime extends from 3 months to 18+ months because each bit transmitted costs approximately 1000x more energy than computing locally.
Test Your Understanding
Question 3: What is the “hotspot problem” in WSN convergecast, and what is its primary cause?
- Sensors near heat sources generate false readings
- Nodes near the sink relay all network traffic, depleting batteries 10-100x faster than edge nodes
- The gateway overheats from processing too much data
- Sensors in direct sunlight lose accuracy
Answer
b) Nodes near the sink relay all network traffic, depleting batteries 10-100x faster than edge nodes
In the N-to-1 convergecast pattern, ALL data from the network must pass through nodes closest to the sink. Like a river system where all upstream water flows through the river mouth, these “hotspot” nodes relay traffic from the entire network in addition to their own data. They deplete 10-100x faster than edge nodes. When hotspot nodes die, the entire network becomes disconnected even though most nodes still have plenty of battery. Solutions include: deploying multiple sinks to distribute load, using mobile sink nodes that relocate periodically, implementing energy-aware routing, or overprovisioning hotspot zones with extra nodes or mains-powered relays.
Decision Framework: Selecting Communication Paradigm and Aggregation Strategy
| Application Type | Communication Pattern | Aggregation Function | Energy Savings | Latency Impact |
|---|---|---|---|---|
| Temperature monitoring | N-to-1 (periodic reports) | Average | 85-90% | Low (minutes OK) |
| Intrusion detection | N-to-1 (event-driven) | MAX (first alert) | 60-70% | Critical (<1s) |
| Soil moisture monitoring | N-to-1 (slow-changing) | Delta encoding | 70-85% | Low (hours OK) |
| Structural health (vibration) | N-to-1 (continuous) | Median + outliers | 50-70% | Medium (<10s) |
| Firmware updates | 1-to-N (broadcast) | None (all receive same) | N/A | Low (minutes OK) |
| Point-to-point control | 1-to-1 (direct) | None | N/A | Critical (<100ms) |
Decision steps:
- Identify data flow direction:
- Many sensors → one sink? Use N-to-1 with hierarchical clustering
- One command → all devices? Use 1-to-N broadcast
- Device ↔︎ device direct? Use 1-to-1 direct links
- Select aggregation function:
- Average/Sum: When all values equally important (temperature, humidity)
- Min/Max: When extremes matter (threshold detection, alerts)
- Median: When outlier resistance needed (noisy environments)
- Delta encoding: When values change slowly (soil moisture, pressure)
- None: When every reading required (regulatory compliance, debugging)
- Calculate energy/latency trade-off:
- High aggregation = Low energy, High latency
- Low aggregation = High energy, Low latency
- Match to application criticality
- Verify hotspot mitigation:
- Single sink? Deploy multiple sinks or rotate cluster heads
- Static routing? Implement energy-aware path selection
Common Mistake: Ignoring the Hotspot Problem in N-to-1 Networks
Misconception: “If we deploy enough sensors with good coverage, the network will last as long as the weakest battery.”
Reality: Nodes near the sink relay ALL network traffic and deplete 10-100× faster than edge nodes. When hotspot nodes die, the entire network becomes disconnected even though 90%+ of nodes still have full batteries.
Real-world example: A 2020 forest monitoring deployment with 200 temperature sensors arranged in 5-hop topology from sink: - Edge nodes (hop 5): 95% battery remaining after 6 months - Middle nodes (hop 3): 60% battery remaining - Hotspot nodes (hop 1): 8% battery remaining, 3 already failed - Network disconnected at 6 months despite avg 75% battery across fleet
Solutions:
- Multiple sinks: Distribute relay load across 3-5 sinks positioned throughout network
- Mobile sink: Sink moves periodically (daily/weekly) to different positions, rotating hotspot
- Rotating cluster heads: LEACH protocol rotates CH role every 10-60 minutes, distributing burden
- Mains-powered relays: Deploy AC-powered relay nodes in hotspot zones
- Energy-aware routing: Route traffic around low-battery nodes to extend overall lifetime
Rule of thumb: For N-to-1 networks with >50 nodes, plan for 3× over-provisioning near sink OR implement rotation/mobile strategies from day 1. Never assume uniform battery depletion in convergecast topologies.
Common Pitfalls
1. Prioritizing Theory Over Measurement in Communication Paradigms
Relying on theoretical models without profiling actual behavior leads to designs that miss performance targets by 2-10×. Always measure the dominant bottleneck in your specific deployment environment — hardware variability, interference, and load patterns routinely differ from textbook assumptions.
2. Ignoring System-Level Trade-offs
Optimizing one parameter in isolation (latency, throughput, energy) without considering impact on others creates systems that excel on benchmarks but fail in production. Document the top three trade-offs before finalizing any design decision and verify with realistic workloads.
3. Skipping Failure Mode Analysis
Most field failures come from edge cases that work in the lab: intermittent connectivity, partial node failure, clock drift, and buffer overflow under peak load. Explicitly design and test failure handling before deployment — retrofitting error recovery after deployment costs 5-10× more than building it in.
13.5 Summary
This chapter covered WSN communication paradigms and their relationship to IoT:
- Three Paradigms: Telephony (1-to-1), Broadcast (1-to-N), and Sensor Networks (N-to-1) represent fundamentally different data flow patterns
- N-to-1 Convergecast: WSN’s defining pattern where many sensors send data to a single sink, enabling unique optimizations
- Data Aggregation: In-network processing reduces transmissions by 85-95%, exploiting the 1000× cost difference between transmission and computation
- IoT Integration: Modern IoT combines all three paradigms—N-to-1 for sensing, 1-to-N for control, 1-to-1 for user interaction
- WSN-IoT Relationship: WSNs pioneered energy-efficient sensing; IoT added cloud connectivity, diverse devices, and richer applications
- Design Challenges: Sink bottleneck, hotspot problem, and scalability require multiple sinks, mobile collection, and hierarchical clustering
13.6 Concept Relationships
| Primary Concept | Builds On | Enables | Contrasts With | Related Pattern |
|---|---|---|---|---|
| N-to-1 Convergecast | Multi-hop routing, tree topology | In-network aggregation, data fusion | Broadcast (1-to-N), unicast (1-to-1) | Upstream data flow, collection tree |
| Data Aggregation | Convergecast pattern, cluster heads | 85-95% traffic reduction | Raw data forwarding | Data fusion, compression |
| Hotspot Problem | Convergecast, multi-hop relaying | Energy-aware routing, multiple sinks | Uniform energy distribution | Energy hole, relay burden |
| IoT Paradigm Integration | WSN (N-to-1), telephony (1-to-1), broadcast (1-to-N) | Bidirectional IoT systems | WSN-only unidirectional sensing | Command-and-control, full-duplex |
| Sink Bottleneck | Single collection point, convergecast | Multiple sinks, mobile collectors | Distributed collection | Congestion, single point of failure |
13.7 What’s Next
| Topic | Chapter | Description |
|---|---|---|
| Energy Management | WSN Energy Management | Implement duty cycling and LEACH protocol for energy-efficient data collection |
| Routing Protocols | WSN Routing | Compare tree-based routing and gradient forwarding for convergecast |
| MQTT Protocol | MQTT Fundamentals | Apply publish-subscribe for bidirectional IoT communication |
| Clustering Protocols | WSN Deployment Sizing | Design LEACH and hierarchical clustering for scalable deployments |
13.8 Concept Check
13.9 Try It Yourself
Hands-On Aggregation Calculation Exercise
Scenario: Environmental monitoring WSN with 200 sensors measuring temperature and humidity every 10 minutes.
Given:
- Each sensor sends: 4 bytes (temp) + 4 bytes (humidity) + 4 bytes (timestamp) = 12 bytes
- Network organized into 20 clusters of 10 sensors each
- Aggregation function: send average, min, max for each metric
Tasks:
- Calculate total daily transmission volume WITHOUT aggregation (all raw data to sink)
- Calculate volume WITH two-tier aggregation (sensors → cluster heads → sink)
- Determine energy savings factor if transmitting 1 byte costs 50 nJ
Step-by-Step:
Without Aggregation:
- 200 sensors × 12 bytes × 6 samples/hour × 24 hours = ? bytes/day
- Convert to MB/day
With Aggregation:
- Cluster heads each receive 10 × 12 bytes = 120 bytes
- Each cluster head computes: avg(temp), min(temp), max(temp), avg(humidity), min(humidity), max(humidity) = 6 values × 4 bytes = 24 bytes per cluster
- 20 clusters × 24 bytes × 6 samples/hour × 24 hours = ? bytes/day
What to Observe: The dramatic reduction in long-range transmissions (to sink). Short-range intra-cluster communication adds overhead but is cheap compared to long-range sink transmission.
Extension: How much does compression ratio change if you only report when temperature/humidity changes by >1% (delta encoding)?
13.10 Knowledge Check
13.11 What’s Next
Continue to Energy Management and Duty Cycling to explore the critical techniques for extending WSN battery life, including synchronous and asynchronous duty cycling protocols, energy harvesting, and performance trade-offs.