7 Sensor Node Characteristics

iot

wireless-sensor-networks

sensor-nodes

Keywords

WSN sensor node characteristics, wireless sensor node architecture, sensor node review, WSN node roles, sensor node diagnostics, WSN embedded systems

7.1 Start With the Field Story

Start with a single sensor node as a field worker with a job, limits, and proof obligations. It must sense, process, store, communicate, sleep, wake, diagnose itself, and survive service conditions well enough for the monitoring claim it supports.

Phoebe’s Field Notes: What a Directional Gateway Antenna Buys a Leaf Node

Phoebe the physics guide

Phoebe’s Why

An antenna cannot create power out of nothing – gain is focus, not amplification. Feed a fixed amount of radio power into an isotropic radiator and it spreads evenly over every direction, like a bare bulb. Feed the same power into a directional element and it bunches that same total into a narrower cone, so the intensity in the favoured direction rises exactly as much as the intensity elsewhere falls. That is why gain in dBi is always measured against the imaginary isotropic radiator: it tells you how much brighter one direction got, not how much extra power arrived. A WSN gateway pointed at a cluster of leaf nodes can trade that unused backside coverage for real range, or, just as usefully, for a lower transmit setting and a longer battery life on the far end.

The Derivation

Directivity compares peak intensity to the isotropic average \(U_0 = P_t/4\pi\):

\[D = \frac{U_{\max}}{U_0}, \qquad G = \eta D\]

EIRP folds transmit power and antenna gain into one budget number:

\[\mathrm{EIRP}_{\mathrm{dBm}} = P_{t,\mathrm{dBm}} + G_{\mathrm{dBi}}\]

Effective aperture links gain back to wavelength:

\[A_e = \frac{G\lambda^2}{4\pi}\]

In free space, received power falls as \(1/d^2\), so doubling range costs \(20\log_{10}2 = 6.02\) dB; a gain change of \(\Delta G\) dB buys a range multiplier of \(10^{\Delta G/20}\).

Worked Numbers: Gain Spent on Range vs. Battery

Omni leaf-node antenna (half-wave dipole, catalog): \(G_{\mathrm{omni}} = 2.15\) dBi
Directional gateway antenna (small patch/Yagi, catalog-typical): \(G_{\mathrm{dir}} = 9.15\) dBi, so \(\Delta G = 7.00\) dB
Spent on range (same EIRP): \(10^{7.00/20} = 2.24\times\) farther reach in free space
Spent on TX power instead (same EIRP, so drop \(P_t\) by 7.00 dB): from 10.0 dBm (10.0 mW) to 3.00 dBm \(= 10^{0.3} = 1.995 \approx 2.00\) mW
PA current at 3.3 V, 35% efficiency (catalog-typical low-power sub-GHz PA): \(I = P_{\mathrm{RF}}/(\eta V)\) gives \(8.66\) mA at 10.0 mW and \(1.73\) mA at 2.00 mW
Battery tie, 1000 mAh cell, 1% TX duty cycle, 5 \(\mu\)A sleep (catalog-typical mote sleep current): \(I_{\mathrm{avg,omni}} = 8.66(0.01)+0.005(0.99) = 0.0915\) mA \(\to\) 455 days; \(I_{\mathrm{avg,dir}} = 1.73(0.01)+0.005(0.99) = 0.0223\) mA \(\to\) 5.13 years – the same 7.00 dB of antenna gain, spent on lower transmit power instead of extra range, is a \(4.11\times\) runtime extension

7.2 Sensor Node as Field Role

A WSN sensor node is the field system that turns a physical condition into usable evidence. It includes the sensor element, processing, radio, storage, power source, enclosure, firmware, identity, diagnostics, calibration path, and service plan. A part list is only a starting point.

The same rule applies to very small motes such as Michigan Micro Mote-style boards: miniaturization is interesting only after the review ties sensing, radio, storage, power, firmware, and service behavior to a field role.

The first review question is the role the node must prove. A quiet leaf node, relay, cluster head, mobile node, reference node, actuator-adjacent node, and gateway-adjacent node can use similar electronics but need different evidence. The acceptable design is the one that supports the stated role in the field conditions where the monitoring claim will be used.

Use the sensor-node route as a review path: start with the field role, then check the sensing path, processing, radio behavior, power and storage, diagnostics, evidence record, decision boundary, retest trigger, and service loop as one connected claim.

The practical mistake is to review those pieces one by one and forget the handoff between them. A temperature node that senses correctly can still fail its role if the enclosure traps heat, the firmware hides stale readings, the radio retries drain the battery, or the owner has no visible trigger for recalibration. A strong node review asks whether the whole route still supports the field claim.

If you only need the intuition, this layer is enough: approve a sensor node for one written role claim. Name what it senses, how it reports, what power and service limits apply, what failure becomes visible, and what change forces a retest.

Physical Evidence

Placement, calibration, warm-up, drift, saturation, environmental exposure, and reference checks show whether the node can observe the condition it claims to observe.

Network Evidence

Radio reach, retries, receive windows, routing burden, queue behavior, time labels, and gateway handoff show whether readings can leave the node with their meaning intact.

Service Evidence

Battery threshold, enclosure access, firmware version, update behavior, diagnostics, identity, and maintenance ownership show whether the node can remain trustworthy after installation.

7.3 Sensor-Node Evidence Record

A useful record separates node subsystems from the claim they support. The goal is not to document every component detail. The goal is to preserve enough evidence that another reviewer can see why the node is acceptable, what it cannot prove, and who owns the next action when evidence weakens.

Subsystem

Evidence to Keep

Common Weak Point

Retest Trigger

Sensing path

Placement, calibration, sample timing, warm-up, drift, saturation, and quality flags.

The sensor part is trusted even though mounting or environment changed the measurement.

Sensor model, placement, calibration method, sampling interval, enclosure, or reference condition changes.

Processing and storage

Filtering, thresholds, timestamps, queues, logs, replay order, duplicate handling, and visible loss state.

Firmware hides missing, stale, filtered, or replayed data as if it were fresh evidence.

Firmware update, configuration change, outage behavior, queue pressure, storage wear, or new event threshold appears.

Radio and role load

Link behavior, retries, receive windows, routing burden, forwarded traffic, security state, and diagnostics.

A leaf-node test is reused after the node becomes a relay, cluster head, mobile node, or gateway-adjacent node.

Topology, gateway, antenna, route policy, channel condition, traffic mix, or node role changes.

Power and service

Sleep states, active current, brownout behavior, update window, service threshold, enclosure, identity, and owner.

The node can work in theory but cannot be reached, diagnosed, recalibrated, powered, or replaced safely in the field.

Battery chemistry, harvest source, duty cycle, enclosure, installation access, maintenance interval, or ownership changes.

Role changes deserve explicit review. A relay node receives and forwards other nodes’ traffic. A cluster head schedules or aggregates. A gateway-adjacent node may carry concentrated traffic and command exposure. A mobile node changes contact, location meaning, and custody. None of those burdens is proven by a leaf-node sensing test.

Sensor-node record template Role claim: what this node must sense, forward, store, decide, or protect. Accepted evidence: sensing path, processing path, radio path, storage path, power path, enclosure, identity, and diagnostics. Known limit: the claim that is not approved, such as safety alarm, fast control, public warning, or new relay burden. Owner: who maintains calibration, firmware, keys, battery, enclosure, and replacement state. Retest trigger: the exact sensor, firmware, antenna, gateway, traffic, enclosure, power, service, or application change that reopens review.

7.4 Why Node Evidence Fails

Most weak sensor-node decisions fail at a boundary. The value may be measured correctly but timestamped badly. The packet may be sent but not acknowledged. The buffer may preserve data but replay it out of order. The firmware may recover but lose calibration state. The enclosure may protect the electronics but detune the antenna. The node may look healthy because diagnostics are missing.

Measurement Boundary

Sensor output becomes evidence only after placement, calibration, timing, range, noise, drift, and quality flags are reviewed against the monitoring claim.

Custody Boundary

Once data enters firmware, queues, radio, routing, and gateway handoff, the record needs freshness, duplicate, missing-data, replay, and ownership evidence.

Control Boundary

Remote commands, firmware updates, threshold changes, and actuator-adjacent decisions need stronger identity, authorization, rollback, and failure-state evidence.

Brownout is a useful example because it crosses several boundaries. A weak battery can corrupt timekeeping, reset firmware, shorten radio range, drop queue writes, or make diagnostics disappear. A resilient node review states how brownout is detected, how the node labels recovery, what data is discarded or preserved, and when service must act.

Diagnostics are the bridge between hidden device behavior and an operator decision. A good node exposes enough status to distinguish no event from no sample, no route from no power, no queue space from no gateway, and old calibration from a fresh observation. Without those labels, the backend may display a clean value while the node is actually outside its approved boundary.

That is why the evidence record should include negative states as well as successful measurements. Missing packets, low battery, stale timestamps, saturation, replacement, firmware rollback, and failed update attempts are not side notes. They are part of the proof that the node can tell the rest of the WSN when its own claim is no longer reliable.

The under-the-hood rule is to avoid accepting silent assumptions. If a node decision depends on calibration, time, state, route, queue, key, battery, enclosure, or owner, that dependency should appear in the evidence record with a known limit and retest trigger.

7.5 Summary

A WSN sensor node is a field role with sensing, processing, radio, storage, power, enclosure, firmware, identity, diagnostics, calibration, and service behavior.
Node approval should start with a written role claim: leaf, relay, cluster head, mobile node, reference node, actuator-adjacent node, or gateway-adjacent node.
Sensing evidence covers placement, calibration, sample timing, warm-up, drift, saturation, and visible quality flags.
Processing, storage, and radio evidence must preserve freshness, ordering, replay, duplicate, loss, route, security, and diagnostic state.
Power, enclosure, and service evidence determine whether the node can remain trustworthy after deployment.
A changed sensor, firmware, antenna, gateway, topology, traffic load, enclosure, power source, service plan, or application claim should reopen the node review.

7.6 Key Takeaway

Approve sensor nodes by role and evidence boundary, not by board label. The reviewed claim must tie measurement, firmware, radio, storage, power, diagnostics, service owner, known limit, and retest trigger together.