9 Infrastructure-Denied IoT: Radio Options

wsn

infrastructure

denied

connectivity

9.1 Overview

This first route frames the disconnected mission and compares radio and contact options against its constraints.

This is part 1 of 2. Continue with Infrastructure-Denied IoT: Field Architecture for the second focused route.

9.2 In 60 Seconds

Picture a flood sensor deep in a valley with no phone signal or mains power. It still needs to send a small warning. A protocol is a set of rules for exchanging messages. LoRaWAN is a long-range radio protocol for small, infrequent messages. A gateway is a local bridge from that radio link to a wider network. Telemetry means readings sent from a remote device. A duty cycle is the share of time a device stays awake or transmits.

First write the warning size, distance, deadline, and battery target. Then test the route in the actual terrain. Check what happens when trees are wet, a gateway fails, or several nodes report together. Save unsent records and make gaps visible. A cheap link is not useful if it hides the event that matters.

Prove the smallest useful message first. Send one dated warning across the hardest part of the route. Repeat at different times. Count success, delay, and battery cost. Turn off the receiver. Check that the node saves the warning. Restore contact. Confirm that old and new warnings remain distinct. This small test gives the wider design an honest starting point.

Use a field-first link record. Mark the sensor and receiver on a map. Measure height and distance. Walk the route. Note hills, trees, water, and safe access. Test in bad weather when possible. Save signal and loss results. Set the message rate. Keep airtime within local rules. Count sleep, listen, and send energy. Reserve storage for an outage. Mark old records after recovery.

Plan a second path only when it can be supported. A satellite, mobile collector, or extra relay also needs power, ownership, and a failure plan. Recheck the route after seasons or site access change.

This opening cannot predict every valley, antenna, season, or emergency. The Practitioner section compares link choices and field evidence. Under the Hood explains radio budgets, energy limits, and recovery models.

Some IoT deployments fail before data analysis begins because there is no practical communication path. Remote forests, mountains, disaster zones, offshore sites, and protected ecological areas may have no cellular coverage, no mains power, no safe access routes, dense vegetation, and limited maintenance windows. In these settings, the engineering problem is not “which cloud platform should receive the data?” but “can a tiny, battery-powered node send a few reliable bits from a hostile radio environment without a permanent infrastructure footprint?”

9.3 Minimum Viable Understanding

Connectivity is an environmental constraint, not just a protocol choice: A technology that works on a farm field or city street can fail in dense canopy, valleys, tunnels, or disaster-damaged areas because radio links depend on frequency, antenna placement, terrain, foliage, interference, and gateway access. Low-data telemetry changes the design space: If the application only needs status, alarms, location, battery level, or compact sensor summaries, very low data rates can be acceptable when they buy range, robustness, and battery life. The right design starts with a link and power budget: Before selecting LoRaWAN, cellular, satellite, mesh, or HF radio, engineers must estimate path loss, receiver sensitivity, antenna gain, fade margin, duty cycle, average current, battery life, and gateway constraints. Infrastructure-denied does not mean impossible: It means the system may need store-and-forward operation, local gateways, private LPWAN, delay tolerance, energy harvesting, rugged enclosures, careful antenna design, or unusual radio paths such as skywave propagation. HF/NVIS is a specialist option, not the default answer: Near-Vertical Incidence Skywave belongs in the course as background for rare regional, low-rate, infrastructure-denied links. Most IoT deployments should still start by checking simpler options such as private LPWAN, cellular IoT, satellite IoT, or mobile collection.

9.4 For Beginners: Why Remote IoT Is Hard

Imagine placing sensors in a place where phones show “no service”, there is no mains electricity, trees block the sky, heavy rain damages connectors, and technicians can only visit every few months. The sensor still needs to wake up, measure something, send a message, and go back to sleep.

That is infrastructure-denied IoT. The device is not just a sensor. It is also a tiny energy system, a radio station, a data logger, and a fault-tolerant computer.

9.5 Learning Objectives

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

Explain why conventional wireless technologies fail in some remote IoT environments
Compare connectivity options for infrastructure-denied sensing, including private LPWAN, cellular IoT, satellite IoT, multi-hop mesh, and HF/NVIS radio
Apply link-budget reasoning to estimate whether a communication path has enough margin
Describe how frequency, wavelength, antenna size, and bandwidth shape remote sensor-network design
Design compact telemetry payloads for low-data, low-power deployments
Evaluate energy trade-offs between sensing, processing, transmitting, sleeping, and gateway operation
Plan a field validation strategy using reliability, SNR, power level, location, time of day, and failure-mode evidence

Chapter Roadmap

This chapter moves through the problem in four passes:

First define the environment and the smallest useful message.
Then compare radio options against link budget, terrain, foliage, and antenna limits.
Next connect weak-signal telemetry to power, gateway, and architecture choices.
Finally prove custody and choose the design an organisation can sustain.

Checkpoints recap the design decisions as you go; deeper tables and formulas are support material for field choices.

9.6 Infrastructure-Denied Connectivity

9.7 Prerequisites

Prerequisites: WSN Communication Patterns | WSN Deployment and Sizing | LPWAN Link Budget and Range

Part of: Wireless Sensor Networks

This enables: WSN Energy Management | LPWAN Technology Selection

9.8 What “Infrastructure-Denied” Means

An infrastructure-denied IoT environment is a deployment area where normal assumptions about connectivity, power, maintenance, and access are weak or false.

The problem is common in:

Remote ecological monitoring
Wildlife and habitat protection
Disaster response after communication towers are damaged
Mountain, glacier, desert, and rainforest sensing
Offshore and riverine monitoring
Border, defence, and emergency-service telemetry
Rural infrastructure monitoring beyond reliable cellular coverage

The defining constraints are not just distance. The harder issue is the combination of distance, obstruction, low power, low maintenance, and uncertain radio conditions.

9.8.1 Typical Constraints

Constraint	Practical effect	Design implication
No cellular coverage	LTE-M, NB-IoT, and 4G/5G cannot attach to a network	Use private infrastructure, satellite, store-and-forward, or non-cellular radio
Dense vegetation	Sub-GHz and GHz links lose margin through foliage and wet canopy	Use conservative link budgets, gateway elevation, lower frequencies, or alternate paths
No clear sky view	Satellite modems may fail or need long acquisition times	Avoid satellite, elevate antenna, or use sparse scheduled transmissions
No mains power	Gateways and repeaters become difficult to sustain	Use low-power nodes, solar, batteries, local buffering, or fewer powered infrastructure points
Limited maintenance	Battery replacement and connector repairs are expensive	Use long-life chemistry, rugged enclosures, remote diagnostics, and large reliability margins
Safety/access limits	Field teams cannot freely visit all sites	Design for remote commissioning, health telemetry, and graceful degradation
Regulatory limits	Spectrum, duty cycle, encryption, and licensing may constrain operation	Check legal operation before building the physical design

9.9 Start With the Communication Requirement

Remote IoT projects often begin with the wrong question: “Which wireless technology should we use?”

The better first question is: what exactly must the remote node communicate, and how quickly?

9.9.1 Requirement Model

Define the communication requirement in six dimensions:

Dimension	Questions to answer
Payload	How many bytes per message? Is it a reading, event flag, GPS coordinate, image, or waveform?
Frequency	How often are messages sent? Every minute, hour, day, or only on events?
Latency	Is a message useful after 10 seconds, 10 minutes, 1 hour, or 1 day?
Reliability	Is occasional loss acceptable, or must every alarm arrive?
Direction	Uplink only, downlink commands, acknowledgements, firmware updates, or two-way control?
Lifetime	How long must the node operate without human service?

These answers determine whether the system needs broadband networking or only robust telemetry.

9.9.2 Telemetry Classes

Classify telemetry by the decision it must support before choosing a bearer. Start with payload size and reporting frequency, then add the latest useful arrival time, loss tolerance, direction, and storage or replay needs. Move down the table from compact status and event records toward bulk and continuous media to see how quickly throughput and energy demands grow. This comparison connects application evidence to connectivity: the class constrains which links are plausible, but measured coverage and service evidence still determine acceptance.

Class	Payload	Latency	Examples	Connectivity implications
Status beacon	1-20 bytes	Minutes to hours	Alive signal, battery, mode	Very low rate; strong candidate for ultra-narrow or weak-signal links
Event alert	5-50 bytes	Seconds to minutes	Door open, flood threshold, equipment fault	Needs reliability and retry strategy more than high throughput
Sensor summary	10-200 bytes	Minutes to hours	Mean, max, min, trend, compressed feature	Local preprocessing reduces radio cost
Trajectory point	20-100 bytes	Minutes to hours	GPS/GNSS fix, timestamp, speed	Compact but needs careful encoding
Bulk data	Kilobytes to megabytes	Hours to days	Audio clips, images, logs	May require local storage plus occasional high-rate retrieval
Real-time media	Megabytes per minute	Seconds	Video, continuous audio	Usually incompatible with ultra-low-power remote links

The less data you need, the more connectivity options become possible.

Checkpoint: Requirement First

You now know:

Infrastructure-denied design starts with payload, frequency, latency, reliability, direction, and lifetime.
Tiny messages such as 1-20 byte beacons, 5-50 byte alerts, and 10-200 byte summaries can trade throughput for range and battery life.
Broadband assumptions only make sense after the required decision and delay have been defined.

9.10 Technology Landscape

No single radio technology dominates infrastructure-denied IoT. Each option carries a different compromise among range, power, bandwidth, infrastructure, cost, and operational risk.

9.10.1 Common Options

Option	Best fit	Strengths	Weak points
BLE	Wearables and short-range collection	Very low power, cheap hardware	Short range, phone/gateway needed nearby
Zigbee/Thread	Local mesh networks	Mature mesh, low power	Multi-hop maintenance burden, limited wide-area range
Wi-Fi	High data rate near infrastructure	Cheap, IP-native, high bandwidth	High power, short range, poor for multi-year batteries
LoRa/LoRaWAN	Rural low-rate telemetry with gateway access	Long range, low power, private network possible	Gateway placement, foliage/terrain loss, duty-cycle and capacity limits
Sigfox-style UNB	Tiny messages in covered regions	Simple device model, long battery life	Operator dependency, payload and message limits
NB-IoT/LTE-M	Managed wide-area service where coverage exists	Licensed spectrum, operator network, mobility support	Requires cellular coverage and subscriptions
Satellite IoT	Remote areas with clear sky	Wide geographic reach	Sky view, cost, power, antenna orientation, subscriptions
Multi-hop mesh	Local areas with many nodes	Can route around obstacles	Relay nodes consume energy; topology maintenance is hard
HF/NVIS radio	Low-rate telemetry where ground infrastructure and line-of-sight are unavailable	Can cover regional areas without towers or clear line-of-sight	Low data rate, larger antennas, variable propagation, regulatory complexity

9.11 Where NVIS Belongs in This Course

NVIS should be taught here, inside infrastructure-denied WSN design, rather than as a separate top-level IoT networking part. It only makes sense after students understand payload size, link budget, antenna size, gateway power, regulation, field validation, and operational ownership.

Primary location: this chapter, because it compares NVIS directly against LPWAN, cellular IoT, satellite IoT, mesh, and store-and-forward designs. Supporting locations: LPWAN selection chapters should mention it only as a contrast case; energy-management chapters should mention the power and duty-cycle implications; application chapters should mention it in disaster, defence, rural, or environmental monitoring scenarios. When to create a separate chapter: only if the course later adds full HF telemetry labs, antenna construction guidance, propagation planning exercises, regulatory workflows, or detailed field case studies.

9.12 Remote Is More Than Distance

A 20 km open rural link and a 2 km link through wet vegetation can be completely different problems. Range claims are usually measured in favourable conditions. In infrastructure-denied environments, the design must budget for foliage, terrain, antenna height, human installation error, connector loss, fading, weather, and seasonal change.

9.13 Radio Fundamentals for Remote IoT

Radio communication is governed by physics before it is governed by protocols. Four ideas matter most: frequency, wavelength, bandwidth, and signal-to-noise ratio.

9.13.1 Frequency and Wavelength

Wavelength is the physical length of one radio wave cycle:

\lambda = \frac{c}{f}

where:

$\lambda$ is wavelength in metres
$c$ is the speed of light, approximately $3 \times 10^8$ m/s
$f$ is frequency in Hz

Approximate examples:

Frequency	Wavelength	Typical IoT relevance
5 MHz	60 m	HF regional radio, large antennas, low data rate
433 MHz	69 cm	Sub-GHz telemetry in some regions
868/915 MHz	35/33 cm	LoRaWAN and other LPWAN deployments
2.4 GHz	12.5 cm	Wi-Fi, BLE, Zigbee, Thread
1.5 GHz	20 cm	GNSS receive bands

Lower frequencies generally diffract around obstacles better and can be less sensitive to foliage than GHz signals. But they require larger antennas and normally provide less bandwidth. Higher frequencies support compact antennas and higher data rates, but are more line-of-sight sensitive and can be blocked by vegetation, walls, terrain, and the human body.

9.13.2 Bandwidth and Sensitivity

Receiver sensitivity improves when the receiver listens over a narrower bandwidth and when the modulation/coding scheme can recover weak signals.

Thermal noise power is approximately:

N = -174 \text{ dBm/Hz} + 10\log_{10}(B) + NF

where:

$B$ is receiver bandwidth in Hz
$NF$ is receiver noise figure in dB

Narrow bandwidth reduces noise. That is why low-rate systems can often hear weaker signals than high-rate systems. The trade-off is payload speed.

9.13.3 Link Budget

A link budget checks whether received signal strength stays above receiver sensitivity after losses:

P_{rx} = P_{tx} + G_{tx} + G_{rx} - L_{path} - L_{cable} - L_{misc}

The link works only if:

P_{rx} - S_{rx} \geq M

Interpret the equation from the transmitter toward the receiver. Begin with transmit power $P_{tx}$ , add the transmit and receive antenna gains $G_{tx}$ and $G_{rx}$ , then subtract path loss $L_{path}$ together with cable and miscellaneous losses. The result is received power $P_{rx}$ . Compare that result with receiver sensitivity $S_{rx}$ ; the difference must still meet the required fade margin $M$ . This order keeps antenna gain, propagation loss, hardware loss, and acceptance margin as separate quantities that can be measured or justified.

For field systems, margin is not optional. A link that works with 1 dB margin during installation may fail after rain, vegetation growth, battery voltage drop, antenna movement, or a season change.

Phoebe’s Field Notes: Why Antenna Gain Buys Range by Spending Coverage

The mathematical gist. At 868 MHz, wavelength is 0.346 m and a 20 km free-space path costs about 117 dB; the same path at 2.4 GHz costs about 126 dB, an 8.83 dB penalty. An ideal 6.02 dB directional gain doubles free-space range by concentrating power fourfold, shrinking ideal beam coverage from $4\pi$ to about $\pi$ steradians before cable, foliage, terrain, and installation losses.

Checkpoint: Radio Margin

You now know:

A 20 km open rural link and a 2 km wet-vegetation link can be different engineering problems.
Frequency sets wavelength: 5 MHz is about 60 m, while 2.4 GHz is about 12.5 cm.
A link budget is not complete until fade margin survives weather, battery, antenna, and installation changes.

9.14 Dense Natural Environments

Remote ecological and environmental deployments are hard because the radio channel changes in ways that are hard to model.

9.14.1 Foliage and Moisture

Vegetation affects radio links through:

Absorption by water in leaves and trunks. Scattering from branches and layered canopy. Multipath caused by uneven terrain and vegetation structure. Seasonal changes in leaf density and moisture. Additional attenuation after rain.

The effect depends on frequency. Sub-GHz links often perform better than 2.4 GHz, but can still degrade strongly in dense wet vegetation.

9.14.2 Terrain and Fresnel Clearance

Long-range radio is not just about a straight line between antennas. The Fresnel zone around the path must also be clear enough. Hills, ridges, buildings, trees, and ground curvature can reduce link margin even when a map suggests that the endpoints are close.

9.14.3 Noise Floor

Receiver sensitivity is only useful when the environment is quiet enough. Practical noise sources include:

Switching power supplies
Solar charge controllers
Motors and pumps
Lightning and atmospheric noise
Nearby transmitters
Poor grounding or water-damaged connectors

In low-signal systems, local noise can matter as much as path loss.

9.15 Continue to Part 2

Continue with Infrastructure-Denied IoT: Field Architecture.