8 ::: {style=“overflow-x: auto;”}

title: “WSN Node ID & Applications” difficulty: intermediate —

In 60 Seconds

WSN node identification uses 16-bit or hierarchical addressing to scale networks to 65,000+ nodes, while MAC protocols (TDMA, CSMA/CA) prevent packet collisions that waste up to 30% of transmitted energy. WSN applications span environmental monitoring (wildfire detection with 30-second alerts), industrial process control (vibration sensing at 1kHz), precision agriculture (soil moisture at 10cm resolution), and smart cities (traffic flow with 95% detection accuracy).

Prerequisites: WSN Fundamentals and Topologies | WSN Energy and Architecture

Part of: WSN Overview series

This enables: WSN Tracking | WSN Coverage | WSN Clustering

8.1 Learning Objectives

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

Design Node Identification Schemes: Implement addressing mechanisms supporting networks with 65,000+ nodes
Implement Collision Avoidance: Apply TDMA, CSMA/CA, and hybrid strategies to prevent packet collisions
Calculate Collision Impact: Quantify packet loss rates and energy impact of different MAC protocols
Apply WSN to Real Domains: Match WSN capabilities to environmental, industrial, agricultural, and smart city applications
Evaluate Application Requirements: Assess sensing frequency, latency, and coverage needs for specific use cases

MVU: Minimum Viable Understanding

If you only have 5 minutes, understand these essentials:

Node addressing allows networks to scale to 65,000+ nodes using 16-bit or hierarchical addressing schemes
Collision avoidance (TDMA, CSMA/CA, or hybrid) is essential once networks exceed 50 nodes – without it, 20-30% of packets are lost
Application domains range from slow environmental monitoring (hourly readings, 5-year batteries) to industrial safety (sub-100ms latency, real-time alerts)

Every WSN application must match its MAC protocol and addressing scheme to its specific data rate, latency, and scale requirements.

Sensor Squad: Talking Without Interrupting!

Sammy the Sensor has a problem – all his friends want to talk at the same time!

Imagine a classroom where everyone shouts their answer at once. Nobody can hear anything! That is what happens when sensors all transmit together – it is called a collision.

Lila says: “We need rules! Like raising your hand in class!”

Here are three ways the Sensor Squad avoids talking over each other:

TDMA (Taking Turns): The teacher gives everyone a specific time to speak. Max speaks at 10:00, Bella at 10:01, Sammy at 10:02. Nobody interrupts! But if Sammy has nothing to say, his time slot is wasted.
CSMA/CA (Listen First): Before speaking, listen to check if anyone else is talking. If quiet, go ahead! If someone is talking, wait a random amount of time and try again. Like politely waiting for a pause in conversation.
Hybrid (Best of Both): Use taking-turns for regular reports, but allow “listen first” for emergencies. If Max detects a fire, he does not wait for his turn – he shouts immediately!

Fun Fact: A factory with 500 sensors lost 23% of their messages before using these rules. After switching to hybrid mode, they only lost 0.3%!

For Beginners: Node Identification Basics

What is this chapter about? When you have hundreds or thousands of sensors in a network, how do they avoid “talking over each other”? This chapter explains addressing and collision avoidance.

Key Terms:

Term	Meaning
MAC Address	Unique hardware identifier for each node
TDMA	Time slots assigned to each node (no collisions)
CSMA/CA	Listen before transmitting to avoid collisions
Backoff	Waiting random time before retrying transmission

Why This Matters:

Without collision avoidance, 20-30% of packets can be lost
Collisions waste energy (transmission + retransmission)
Proper MAC protocols enable scaling to 1000s of nodes

Simple Analogy: Imagine a classroom where everyone wants to speak at once. TDMA is like raising hands and waiting for your turn (teacher assigns time slots). CSMA/CA is like waiting for silence before speaking (if someone else is talking, wait). Both prevent the chaos of everyone talking simultaneously.

8.2 Node Identification and Collision Avoidance

In large-scale WSN deployments with hundreds or thousands of nodes, node identification and collision avoidance become critical challenges. When multiple sensors attempt to transmit simultaneously on shared radio channels, packet collisions corrupt data.

8.2.1 Addressing and Identification

Mechanism	Description	Capacity	Protocol Example
16-bit Short Address	Unique node identifier assigned during network join	65,536 nodes	Zigbee, 802.15.4
64-bit Extended Address	Globally unique MAC address (factory-assigned)	18.4 quintillion devices	IEEE 802.15.4 EUI-64
Cluster-Tree Addressing	Hierarchical addressing (cluster ID + node ID)	65K clusters x 256 nodes/cluster	Zigbee cluster-tree routing

8.2.2 Collision Avoidance Strategies

Diagram comparing three WSN collision avoidance strategies side by side: TDMA (Time Division Multiple Access) assigns fixed numbered time slots to each sensor node in a round-robin schedule - all nodes take turns with zero collisions but unused slots waste channel capacity; CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) shows nodes listening before transmitting with backoff timer when channel is busy - efficient but collisions possible under high load; Hybrid combines a periodic TDMA frame for regular sensor data with a contention window where CSMA/CA allows urgent alerts to break in - achieving near-zero collisions while supporting event-driven transmissions. — Figure 8.1: Three collision avoidance strategies: TDMA assigns fixed time slots (no collisions, deterministic), CSMA/CA listens before transmitting (efficient utilization, possible collisions), Hybrid combines scheduled slots for regular data with CSMA windows for urgent alerts.

1. TDMA (Time Division Multiple Access):

Gateway assigns dedicated time slots to each sensor
Example: 100-node network with 10ms slots - each sensor transmits every 1 second (100 x 10ms)
Advantage: Zero collisions (deterministic)
Disadvantage: Fixed slot waste (if sensor has no data, slot unused)

2. CSMA/CA (Carrier Sense Multiple Access / Collision Avoidance):

Sensor listens to channel before transmitting (carrier sense)
If channel busy, waits random backoff time (collision avoidance)
Advantage: Efficient channel utilization (no wasted slots)
Disadvantage: Collisions possible during high traffic

Putting Numbers to It

CSMA/CA Collision Probability in High-Density WSN

Consider a 100-node WSN where all nodes attempt transmission with Poisson arrival:

Channel parameters:

Transmission time per packet: $T_{pkt} = 5$ ms (100-byte packet at 160 kbps)
Carrier sense duration: $T_{cs} = 0.5$ ms
Average arrival rate: $\lambda = 20$ packets/sec (all nodes combined)

Collision probability using Poisson model: During the vulnerable period (carrier sense time), if another node starts transmitting, collision occurs.

Vulnerable window: $T_{vuln} = T_{cs} = 0.5$ ms

Expected number of arrivals during vulnerable period: \[N_{arrivals} = \lambda \times T_{vuln} = 20 \times 0.0005 = 0.01 \text{ packets}\]

Collision probability (at least 1 other node transmits): \[P_{collision} = 1 - e^{-\lambda T_{vuln}} = 1 - e^{-0.01} \approx 0.01 = 1\%\]

At higher load ($\lambda = 100$ packets/sec): \[P_{collision} = 1 - e^{-100 \times 0.0005} = 1 - e^{-0.05} \approx 4.9\%\]

Energy waste: Each collision wastes transmit energy ($20$ mJ) + requires retransmission. With 4.9% collision rate and 100 transmissions/sec: $4.9 \times 20 = 98$ mJ/sec wasted. Over 24 hours: $98 \times 86,400 = 8,467$ J = enough to power 2 sensor nodes for a full year.

TDMA comparison: Zero collisions, but 40% unused slots (nodes with no data). Trade-off: CSMA/CA better for low traffic (≤50% utilization), TDMA better for predictable high traffic.

8.2.3 Interactive: CSMA/CA Collision Probability Calculator

Show code

{
  const tVuln = csTime / 1000; // convert ms to seconds
  const pCollision = 1 - Math.exp(-arrivalRate * tVuln);
  const collisionsPerSec = pCollision * arrivalRate;
  const energyWastedPerSec = collisionsPerSec * txEnergy;
  const energyWastedPerDay = energyWastedPerSec * 86400 / 1000; // in J

  const color = pCollision < 0.02 ? '#16A085' : pCollision < 0.10 ? '#E67E22' : '#E74C3C';

  return html`<div style="background: var(--bs-light, #f8f9fa); padding: 1rem; border-radius: 8px; border-left: 4px solid ${color}; margin-top: 0.5rem;">
    <p><strong>Collision Probability:</strong> <span style="color:${color}; font-size:1.2em; font-weight:bold">${(pCollision * 100).toFixed(2)}%</span></p>
    <p><strong>Collisions per Second:</strong> ${collisionsPerSec.toFixed(2)}</p>
    <p><strong>Energy Wasted per Second:</strong> ${energyWastedPerSec.toFixed(1)} mJ</p>
    <p><strong>Energy Wasted per Day:</strong> ${energyWastedPerDay.toFixed(1)} J</p>
    <p style="font-size:0.85em; color:#666;">Formula: P<sub>collision</sub> = 1 − e<sup>−λ × T<sub>vuln</sub></sup></p>
  </div>`;
}

3. Hybrid TDMA + CSMA/CA:

TDMA for scheduled high-priority data (e.g., cluster head aggregation)
CSMA/CA for unscheduled event-driven alerts (e.g., motion detection)
Used in industrial WSN standards like WirelessHART and ISA100.11a

8.2.4 Real-World Example: Factory Floor WSN

Problem: 500 vibration sensors monitoring motors transmit 1 reading/second. Without collision management, simultaneous transmissions corrupt 23% of packets (measured in pilot deployment).

Solution: Hybrid TDMA + prioritized CSMA/CA - Regular monitoring: 500 TDMA slots x 2ms/slot = 1-second cycle (no collisions) - Emergency alerts: CSMA/CA with priority queues (vibration spike detected - immediate channel access) - Result: Packet loss reduced from 23% to 0.3% (only during rare simultaneous emergencies)

Energy Impact:

CSMA/CA idle listening: 20-30% of sensor energy budget (radio on, waiting for clear channel)
TDMA sleep scheduling: Sensor sleeps 99% of cycle (wakes only for assigned 2ms slot)
Battery life improvement: 6 months (CSMA/CA) to 2.5 years (TDMA) for same duty cycle

This collision management layer is transparent to higher network layers but critical for WSN scalability beyond 50-100 nodes.

8.2.5 Protocol Comparison

Factor	TDMA	CSMA/CA	Hybrid
Collision Rate	0%	5-30% (load dependent)	<1%
Channel Utilization	40-60% (wasted slots)	70-90% (dynamic)	75-85%
Energy Efficiency	Excellent (scheduled sleep)	Poor (idle listening)	Good
Latency	Fixed (wait for slot)	Variable (0-100ms)	Mixed
Complexity	High (synchronization)	Low	Medium
Best For	Regular periodic data	Bursty event data	Mixed workloads

8.3 Application Domains

WSNs enable diverse applications across multiple industries. Each domain has unique requirements for sensing frequency, coverage, latency, and reliability.

8.3.1 Environmental Monitoring

Use Cases:

Climate and weather monitoring
Pollution detection (air, water, soil)
Forest fire detection
Flood and landslide warning systems
Wildlife habitat monitoring

Example Deployment: Volcano monitoring networks use temperature, seismic, and gas sensors to predict eruptions. The US Geological Survey deploys WSNs on active volcanoes that operate autonomously for 2+ years, transmitting data every 10 minutes via LoRaWAN to satellite uplinks.

8.3.2 Industrial Applications

Use Cases:

Structural health monitoring (bridges, buildings, dams)
Machine condition monitoring (predictive maintenance)
Supply chain and inventory tracking
Quality control and process optimization
Hazardous gas detection in industrial facilities

Example Deployment: Oil refineries deploy 5,000+ wireless sensors for equipment monitoring, leak detection, and environmental compliance. WirelessHART protocol provides deterministic latency (<10ms) for safety-critical gas detection while supporting 100+ sensors per access point.

8.3.3 Smart Agriculture

Use Cases:

Precision irrigation management
Soil moisture and nutrient monitoring
Crop health assessment
Livestock tracking and health monitoring
Greenhouse climate control

Example Deployment: California almond orchards deploy soil moisture sensors every 100m (400 sensors for 1000 hectares), reducing water usage by 25% through precision irrigation. Zigbee mesh networks provide 3-year battery life with 15-minute readings.

8.3.4 Healthcare

Use Cases:

Patient vital signs monitoring
Fall detection for elderly care
Hospital asset tracking
Environmental monitoring in medical facilities
Pandemic and disease outbreak detection

Example Deployment: Elderly care facilities deploy wearable fall detection sensors using BLE beacons for room-level location. Alert latency <3 seconds enables rapid response, while 5-day battery life minimizes resident disruption.

8.3.5 Smart Cities

Use Cases:

Traffic monitoring and management
Smart parking systems
Waste management optimization
Street lighting control
Noise level monitoring

Example Deployment: Barcelona’s smart parking network deploys 30,000 ground-embedded sensors using LoRaWAN, guiding drivers to available spots via mobile app. 10-year battery life (one reading per minute) eliminates maintenance for municipal infrastructure.

8.3.6 Military and Defense

Use Cases:

Battlefield surveillance
Intrusion detection
Target tracking
Chemical/biological threat detection
Equipment and personnel monitoring

Example Deployment: Border security uses seismic and acoustic sensors buried along perimeters, forming mesh networks that detect and classify vehicles vs. personnel. Event-triggered operation provides 6-month unattended operation with <1 second alert latency.

Quick Check: Collision Avoidance

A WSN factory deployment uses 500 sensors transmitting once per second. Without any MAC protocol, 23% of packets are lost. Which approach eliminates collisions for regular periodic data?

Increase transmission power
TDMA with assigned time slots
Reduce the number of sensors
Use larger packet sizes

Answer

b) TDMA with assigned time slots. TDMA assigns each sensor a dedicated time slot, achieving zero collisions for scheduled periodic data. With 500 sensors and 2ms slots, each sensor transmits once per second with no overlap. Increasing power does not prevent simultaneous transmissions from colliding.

Test Yourself: Match MAC Protocols to Characteristics

Test Yourself: Steps to Select a WSN Application Protocol

8.4 Application Selection Guide

Four-quadrant matrix chart for WSN application technology selection with axes of latency requirement (low to high on vertical) and data rate requirement (low to high on horizontal). Industrial monitoring (upper-right quadrant, high data rate and low latency) is labeled WirelessHART or wired sensors. Healthcare wearables (upper-left, low data rate but low latency) is labeled BLE or Zigbee. Environmental monitoring (lower-right, high data rate but high latency tolerance) is labeled LoRaWAN. Smart city parking (lower-left, low data rate and high latency tolerance) is labeled LPWAN. Each quadrant contains example applications and recommended protocols. — Figure 8.2: **Application Requirements Matrix**: This quadrant chart helps select appropriate WSN technology based on application needs. Upper-right (Industrial) requires high data rates AND low latency - use WirelessHART or wired sensors. Upper-left (Healthcare) needs low latency but moderate data rates - BLE or Zigbee. Lower-right (Environmental) has high latency tolerance but low data rates - perfect for LoRaWAN. Lower-left (Smart City) tolerates both high latency and low data rates - ideal for ultra-low-power LPWAN.

Key Concepts

Node Identification: Unique addressing schemes (16-bit, 64-bit, hierarchical) enabling networks with 65,000+ nodes
TDMA: Time Division Multiple Access assigns fixed transmission slots, eliminating collisions but potentially wasting channel capacity
CSMA/CA: Carrier Sense Multiple Access with Collision Avoidance listens before transmitting, efficient for bursty traffic
Collision Rate: Percentage of packets corrupted due to simultaneous transmissions, 5-30% without proper MAC protocol
Application Domain: Specific industry or use case with unique requirements for sensing frequency, latency, and coverage

8.5 WSN Deployment Cost Benchmarks by Application Domain

Understanding typical deployment costs helps project managers budget accurately and avoid the common mistake of underestimating installation labor and ongoing maintenance.

Application Domain	Nodes per km²	Node Cost (each)	Installation Cost (per node)	Annual Maintenance (per node)	Network Lifetime Target	Total 5-Year Cost (100 nodes)
Precision agriculture	5-20	$30-$80	$15 (stake in ground)	$10 (battery swap)	3-5 years	$15,500
Structural health (bridges)	50-200	$200-$500	$300 (trained technician, drilling)	$50 (inspection + calibration)	10-20 years	$75,000
Forest fire detection	1-5	$80-$150	$100 (tree mounting, remote access)	$25 (battery, weatherproofing)	2-5 years	$30,500
Smart building (HVAC)	100-500	$40-$80	$25 (ceiling mount, commissioning)	$8 (firmware update, battery)	5-10 years	$13,300
Industrial vibration	200-1,000	$150-$400	$200 (machine mounting, calibration)	$75 (recalibration, harsh environment)	5-10 years	$80,000
Pipeline monitoring	10-50 (per km)	$100-$250	$150 (buried/attached, weatherproof)	$40 (site visit, battery)	3-7 years	$49,000

:::

Why Installation Cost Often Exceeds Hardware Cost

A common budgeting mistake in WSN projects is allocating 80% of budget to hardware and 20% to deployment. Real-world data shows the opposite pattern for specialized applications:

Example – Structural Health Monitoring of a Highway Bridge (US DOT study, I-35W replacement bridge, Minneapolis):

323 sensors deployed across the bridge deck and piers
Sensor hardware: $500 x 323 = $161,500 (24% of total)
Installation labor (ironworkers + electricians): $280,000 (42%)
Gateway infrastructure + solar panels: $85,000 (13%)
Commissioning + baseline calibration: $68,000 (10%)
Project management + engineering: $72,000 (11%)
Total: $666,500 – hardware was less than 1/4 of total cost

Contrast with Precision Agriculture (Decagon Devices deployment, Washington State):

80 soil moisture sensors across 40 hectares
Sensor hardware: $60 x 80 = $4,800 (53% of total)
Installation labor (farm workers with stakes): $1,200 (13%)
Gateway + cellular modem: $800 (9%)
Commissioning: $400 (4%)
Annual subscription (cloud dashboard): $1,800/year (21%)
Total first year: $9,000 – hardware dominates because installation is trivial

Rule of Thumb: If deploying sensors requires a licensed technician (electrician, ironworker, certified inspector), installation costs will exceed hardware 2-3x. If sensors can be deployed by unskilled labor (push into soil, stick on wall), hardware costs dominate.

Common Pitfalls

1. Prioritizing Theory Over Measurement in WSN Node ID & Applications

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.

🏷️ Label the Diagram

Code Challenge

8.6 Summary

This chapter covered node identification, collision avoidance, and WSN application domains:

Node addressing supports networks from 256 to 65,000+ nodes using hierarchical schemes
TDMA provides zero collisions but wastes channel capacity; CSMA/CA is efficient but collision-prone
Hybrid protocols combine scheduled slots with contention windows for optimal performance
Application domains range from slow environmental sensing (5-year batteries, hourly readings) to industrial monitoring (real-time, sub-100ms latency)
Choosing the right protocol depends on data rate, latency requirements, and network scale

This completes the WSN Overview series, providing foundational understanding for deeper exploration of specific WSN topics.

8.7 Test Your Understanding

Test Your Understanding

Question 1: A factory floor WSN uses 500 vibration sensors transmitting once per second. Without collision management, 23% of packets are corrupted. Which MAC approach would best handle both regular monitoring AND emergency alerts?

Pure TDMA – all sensors get fixed time slots
Pure CSMA/CA – all sensors listen before transmitting
Hybrid TDMA + prioritized CSMA/CA
Increase transmission power to overcome collisions

Answer

c) Hybrid TDMA + prioritized CSMA/CA. Regular periodic monitoring fits TDMA perfectly (no collisions with scheduled slots), while emergency vibration spike alerts need immediate channel access via prioritized CSMA/CA. Pure TDMA cannot handle urgent unscheduled events. Pure CSMA/CA wastes energy on idle listening. Increasing power does not prevent collisions.

Question 2: An environmental monitoring WSN requires 3-10 year battery life with sensing every 5-60 minutes. Which application domain best matches these requirements?

Industrial machine monitoring (1-1000 Hz sensing, <100ms latency)
Healthcare patient monitoring (continuous sensing, <1s latency)
Climate and pollution monitoring (slow environmental changes)
Military battlefield surveillance (event-triggered, <100ms latency)

Answer

c) Climate and pollution monitoring. Environmental monitoring applications have slow-changing phenomena (temperature, air quality, water quality), requiring infrequent sensing (every 5-60 minutes) and tolerating minutes-to-hours latency. This matches the 3-10 year battery requirement. Industrial and military need much lower latency, and healthcare needs continuous or near-continuous sensing.

Question 3: Barcelona deployed 30,000 ground-embedded parking sensors using LoRaWAN with 10-year battery life. What characteristic of this application made LoRaWAN ideal?

High data rate requirements for video streaming
Low data rate (one reading per minute), long range, and ultra-low power
Sub-millisecond latency for real-time parking guidance
High node mobility as cars move through the city

Answer

b) Low data rate (one reading per minute), long range, and ultra-low power. Smart parking sensors transmit tiny binary readings (occupied/vacant) infrequently. LoRaWAN provides 10-15 km range with ultra-low power, enabling 10-year battery life and zero recurring connectivity fees – making it economically viable for 30,000 sensors.

8.8 Worked Example: WSN Application Comparison – Environmental vs Structural Monitoring

Worked Example: Designing Two WSNs With Opposite Requirements

Scenario: Compare designing a WSN for (A) forest temperature monitoring (low rate, energy-critical) vs (B) bridge vibration monitoring (high rate, latency-critical). Both need 50 sensor nodes and 5-year lifetime.

Application A: Forest Temperature Monitoring

Parameter	Value	Design Implication
Sampling rate	1 reading / 10 min (0.0017 Hz)	Ultra-low duty cycle possible
Data per reading	4 bytes (temperature + humidity)	Minimal bandwidth
Latency tolerance	Hours (daily batch OK)	Store-and-forward, sleep aggressively
Network data rate	50 nodes x 4 B x 6/hr = 1.2 KB/hr	Any low-power radio works
Power source	2x AA batteries (no solar under canopy)	Must last 5 years on 6,000 mAh
Energy budget	6,000 mAh / 43,800 hrs = 0.137 mA avg	0.1% duty cycle with 0.001 mA sleep radio
Node cost	$18 (low-power MCU + LoRa + temp sensor)
Total deployment	$900 + $200 gateway = $1,100

Application B: Bridge Vibration Monitoring

Parameter	Value	Design Implication
Sampling rate	1,000 Hz (Nyquist for 500 Hz vibrations)	Continuous high-rate ADC
Data per reading	2 bytes (16-bit accelerometer)	2 KB/sec per node
Latency tolerance	<100 ms (real-time structural alert)	Cannot use store-and-forward
Network data rate	50 nodes x 2 KB/sec = 100 KB/sec = 800 kbps	Exceeds Zigbee capacity (250 kbps)
Power source	Solar panel + supercapacitor (bridge surface)	Energy harvesting enables continuous operation
Processing requirement	Local FFT to extract frequency peaks	MCU with DSP (e.g., STM32F4)
Node cost	$85 (DSP MCU + MEMS accelerometer + solar + Wi-Fi)
Total deployment	$4,250 + $500 gateway = $4,750

Key Architecture Differences:

Decision	Forest (App A)	Bridge (App B)
Radio	LoRa (long range, low power, low rate)	Wi-Fi or 802.15.4g (high throughput)
Topology	Star (single gateway, 2 km range)	Mesh (bridge is 500 m, need multi-hop for reliability)
Data processing	None at node (raw temp reading)	FFT at node (reduce 2 KB/sec to 20 bytes of frequency peaks)
Routing protocol	Simple beacon (no multi-hop needed)	RPL with ETX metric (reliability over shortest path)
Failure mode	Graceful degradation (1 dead node = 1 blind spot, not critical)	Safety-critical (1 dead node could miss a structural crack)

Result: Two 50-node WSNs with 100x different data rates, 1000x different latency requirements, and 4x different costs. The forest WSN optimizes for energy (5 years on batteries). The bridge WSN optimizes for throughput and reliability (real-time safety). Choosing the wrong architecture for either application would result in failure: a bridge WSN built with LoRa would miss 99.9% of vibration data; a forest WSN built with Wi-Fi would drain batteries in 3 days.

8.9 Knowledge Check

Quiz: WSN Node ID & Applications

8.10 What’s Next?

Topic	Chapter	Description
Sensor Nodes	WSN Sensor Nodes	Sensor node hardware, capabilities, and resource constraints
IoT Integration	WSN IoT Relationship	How WSNs integrate with broader IoT architectures
Energy Management	WSN Energy Management	Advanced energy conservation strategies and duty cycling
Deployment Sizing	WSN Deployment Sizing	Plan WSN deployments with sizing calculations
Common Mistakes	WSN Common Mistakes	Avoid costly pitfalls in WSN deployment