2 WSN Introduction and History
wireless sensor networks, WSN introduction, WSN history, sensor node roles, distributed sensing, WSN design evidence
2.1 Start With the Field Story
Begin with one simple claim: small devices in the field need to notice something and report it often enough to matter. The rest of a WSN review checks whether node roles, radio paths, gateways, energy budgets, and maintenance plans can keep that claim true after the first demonstration.
Phoebe’s Why
A datasheet’s mAh number counts charge – how many electrons the cell can push through the circuit – not the energy those electrons deliver, because energy also depends on the voltage each electron is pushed at, and that voltage is not constant. Every real cell has internal resistance, so the terminal voltage sags under load, and the nameplate charge itself erodes quietly from self-discharge even when the node is asleep. A WSN battery budget that multiplies nameplate mAh by nominal voltage and stops there is already optimistic before a single packet is sent – and every retry this chapter’s route-repair evidence records is a real draw against that same optimistic budget, whatever radio path caused the retry.
The Derivation
Energy is the integral of voltage times current, not charge times a constant:
\[E = \int V(t)\,I(t)\,dt\]
Internal resistance \(R_{int}\) sags the terminal voltage under load (Ohm’s law applied to the cell itself):
\[V_{term} = V_{oc} - I\,R_{int}\]
Only when \(V\) is treated as constant does charge become a stand-in for energy:
\[E(\mathrm{Wh}) \approx Q(\mathrm{Ah}) \times V\]
Self-discharge removes usable charge even at rest, and a design margin (derating) further discounts the nameplate value to a safe usable capacity \(Q_{usable} = f_{derate} \times Q_{nominal}\).
Worked Numbers: A Typical WSN Leaf Node
Using a standard/typical lithium primary cell (3.6 V nominal, 2000 mAh, since this chapter names no specific battery):
- Nameplate energy: \(E = 2.000\ \text{Ah} \times 3.6\ \text{V} = 7.20\) Wh
- Sag during a radio TX pulse (\(I = 30\) mA, typical 802.15.4-class active current, \(R_{int} = 3\ \Omega\) typical): \(\Delta V = I R_{int} = 0.030 \times 3 = 0.0900\) V, terminal voltage drops to \(3.51\) V during transmit
- Derated usable capacity at 80% (standard design margin covering sag, temperature, and self-discharge): \(0.80 \times 2000 = 1600\) mAh, or \(0.80 \times 7.20 = 5.76\) Wh
- At a 50 \(\mu\)A average duty-cycle current: life \(= 1600\ \text{mAh} / 0.050\ \text{mA} = 32{,}000\) h \(= 32{,}000/8760 = 3.65\) years
That 3.65-year figure assumes a clean radio path. A reflected or diffracted signal path (wave optics) forces the retries this chapter’s route-repair evidence flags; every retry redraws the 30 mA active current above, so a site with poor Fresnel clearance or heavy multipath eats directly into the 3.65-year budget, not just into packet-success percentage.
2.2 What a WSN Claim Means
A wireless sensor network, or WSN, is a distributed sensing system. Many small nodes measure physical conditions, perform limited local work, and move readings toward a sink, gateway, or application service. The useful claim is not “we have wireless nodes.” The useful claim is that a named sensing objective can be observed, transmitted, interpreted, and maintained under defined field conditions.
WSN history matters because it explains the recurring pressures: constrained energy, lossy links, placement-sensitive measurements, topology changes, gateway boundaries, and maintenance ownership. Early research proved that many constrained nodes can create useful system evidence. Field deployments proved that lab connectivity is only one part of the review.
The review map keeps the introduction grounded in evidence. A sensor field starts with a physical condition and a decision that uses that condition. The node roles then explain who senses, relays, aggregates, or bridges. The site evidence explains whether placement, enclosure, and link conditions match the claim. Energy evidence explains whether the duty cycle and role burden can last. Path evidence explains how readings move through relays, sinks, gateways, and services.
That order prevents a common beginner mistake: treating the network diagram as the whole system. A WSN can look connected while the sensing point is misplaced, the relay carries too much traffic, the gateway loses meaning during recovery, or the support owner has no retest rule. The introduction should therefore approve only the part of the system that has matching field evidence.
If you only need the intuition, this layer is enough: approve a WSN from the sensing claim, node roles, topology, power evidence, data path, operations owner, and retest trigger. A successful packet in a lab does not prove field sensing quality.
2.2.1 The Five Evidence Boundaries
Sensing purpose
The review starts with what condition is measured, where it is measured, at what interval, and which decision uses the data.
Node behavior
Sensor, processor, radio, storage, sleep state, retry behavior, calibration, enclosure, mounting, and battery assumptions define each node claim.
Network behavior
Star, cluster, mesh, relay, sink, gateway, routing, aggregation, loss, recovery, and stale-data behavior define the communication claim.
Operations behavior
Battery replacement, calibration, firmware, keys, gateway health, alert ownership, data quality, and retest triggers decide whether the deployment remains trustworthy.
2.2.2 Beginner Examples
- A gateway ping proves only a narrow communication fact. It does not prove sensing placement, power life, route recovery, or missing-data detection.
- A mesh diagram is not proof of route resilience. Relay load, parent choice, loss, recovery, and battery impact need field evidence.
- A sensor reading is not useful unless it is placed, calibrated, timestamped, delivered, and interpreted for a decision.
- A WSN can be the wrong tool when wired sensing, manual sampling, a powered gateway, or fewer high-quality instruments provide better evidence.
2.2.3 Overview Knowledge Check
2.3 WSN Review Record
A practical WSN review record should let another engineer repeat the decision. It states the sensing objective, node role model, topology, power budget, data path, gateway boundary, failure behavior, owner, and change that reopens the decision.
Early design may record assumptions. A release review should replace assumptions with representative evidence from field placement, enclosure, calibration, interference, traffic, route behavior, battery profile, gateway outage behavior, missing-data handling, and support procedures.
2.3.1 Worked Review: Greenhouse Monitoring
A greenhouse team wants temperature and humidity readings from several growing zones. The review should start with the control decision and acceptable latency, then record sensor placement, enclosure behavior near wet areas, calibration, gateway reachability, reporting interval, missing-node alerts, and battery replacement ownership.
The safe approval statement is narrow: under the reviewed placement and reporting interval, this sensor field supports these zone-level decisions. It does not prove every crop layout, gateway location, enclosure, battery, or future alert threshold.
2.3.2 Bridge Vibration Monitoring
A bridge monitoring deployment needs vibration evidence at selected structural points. The review should separate measurement quality from radio connectivity: mounting validation, feature preservation, sample or summary behavior, buffering, relay load, gateway outage behavior, weather exposure, and retest triggers after maintenance or firmware changes.
The approval should not say that low-power wireless generally solves structural monitoring. It should say which sensing features, node positions, network route, and operations procedure were observed.
2.3.3 Practitioner Knowledge Check
2.4 Layer Handoffs and Failures
WSN failures are often misdiagnosed because several layers appear as one missing reading. A measurement can be wrong before it is transmitted. A good measurement can be buffered and delayed. A packet can reach a relay but not a gateway. A gateway can store data while the dashboard interprets it with stale thresholds. A working route can still be operationally unsafe if nobody owns batteries, calibration, or keys.
The review should preserve the handoff from physical observation to node behavior, network delivery, gateway and backend interpretation, and operations. That separation keeps a narrow lab result from becoming a broad deployment claim.
2.4.1 Diagnosis Pattern
- Name the failing boundary. Separate bad measurement, missing packet, stale reading, duplicate reading, gateway outage, alert error, and maintenance failure.
- Check the closest lower proof. If the dashboard is wrong, inspect gateway and backend mapping before moving nodes. If the reading is noisy, inspect placement and calibration before changing routing.
- Change one variable at a time. Sensor placement, reporting interval, retry policy, route behavior, gateway location, and alert threshold can each change the evidence trail.
- Write the unsupported claim. If the pilot covered one room, one topology, one season, or one battery profile, keep the approval limited to that boundary.
2.4.2 Under-the-Hood Knowledge Check
2.5 Summary
- WSN approval starts with a bounded sensing claim, not with a wireless label or a lab packet.
- Node roles, topology, routing, power, gateway behavior, data quality, and operations ownership need separate evidence.
- Sensing quality depends on placement, calibration, enclosure, interval, and the decision that uses the data.
- Energy review must include sensing, processing, transmit, receive, retries, listening windows, joins, downlinks, and maintenance traffic.
- Network review must cover topology, role burden, link quality, route repair, gateway recovery, and stale-data behavior.
- Operations evidence names owners for batteries, calibration, firmware, keys, gateway health, alert thresholds, and retest triggers.
Approve a WSN only when the reviewed behavior is tied to sensing purpose, node roles, topology, routing, energy evidence, gateway behavior, owner, and retest boundary.
2.6 See Also
WSN Architecture and Applications
Review node, sink, gateway, backend, topology, application-fit, and operations boundaries.
Connect sensing, processing, radio, storage, enclosure, mounting, and power evidence to node behavior.
Review message flow, aggregation, link behavior, loss, retry, and gateway handoffs in WSN communication.
Separate duty cycle, sleep, receive windows, retries, maintenance traffic, and replacement evidence.