3 LPWAN Link Budget and Range

Overview: Link Budget Is Signal Accounting

An LPWAN link budget is a review record, not a range promise. It adds the useful signal contributions, subtracts losses, compares the expected received signal with receiver sensitivity, and keeps margin for fading, clutter, antenna placement, enclosure loss, and measurement uncertainty.

The result is not "this device reaches ten kilometers." The result is a bounded statement: under these assumptions, this link has enough or not enough remaining margin to justify a pilot.

Suppose a farm water-monitoring project wants one gateway to cover hill tanks, buried meter pits, and a shed-mounted pressure sensor. The radio ledger may begin with a healthy raw budget, but the buried pits need enclosure and ground-level penalties, the shed sensor needs wall-loss allowance, and the hill tanks need wind-driven antenna alignment checks. If the raw budget is 149 dB and the review reserves 10 dB for fading, 12 dB for obstruction, and 4 dB for installation uncertainty, only 123 dB remains for path loss. A model estimate of 118 dB is a pilot candidate; an estimate of 128 dB is not a "maybe" range claim. It is a design gap unless the team changes antenna placement, gateway density, radio settings, or the device location.

The overview record should therefore state the acceptance rule before field work starts. A pass might mean every representative location keeps at least the reserved margin while using an allowed data rate and legal transmit setting. A conditional pass might allow the hill tanks but require a second gateway for buried pits. A fail should name the design change, not leave a vague note that the range was shorter than expected.

The claim that A defensible range claim starts with a ledger and ends with field evidence needs “settings” as a concrete check beside “Gains”. Inspect Figure 3.1 before continuing the “settings”–“gains” decision, especially “settings” beside “Gains”.

+

Trace the review path across Figure 3.1 from “settings” to “Gains”. From “antennas”, it arrives at “Losses”. That path is evidence for A defensible range claim starts with a ledger and ends with field evidence; retain it when revisiting the “settings”–“gains” decision.

Practitioner: Turn the Ledger into a Margin Decision

Start by calculating raw link budget, then remove the margins and allowances that should not be spent by normal path loss. What remains is maximum allowable path loss. That value can be compared with a model estimate or measured field result.

Inspect Figure 3.2 to ask whether the planned path meets receiver sensitivity and still preserves the required safety margin.

+

Read Figure 3.2 from the +14 dBm transmitter through antenna gain and path losses to the −111 dBm expected signal. Receiver sensitivity sets the minimum usable level, while the separate safety target reserves room for changes the simple model cannot predict. The figure reports 12 dB of total margin against a 10 dB requirement, leaving 12 dB − 10 dB = 2 dB of extra reserve. That is not a range guarantee. It is a reviewable ledger whose antenna, cable, obstruction, and installation assumptions must be checked at the actual site before the link can support a release decision.

To ground the “healthy”–“pilot” decision through “Redesign” in visible evidence about “Healthy”, inspect Figure 3.3. Its named elements “Healthy” and “Pilot” frame the claim that The margin gate turns a calculation into an engineering decision.

+

Read Figure 3.3 with “Healthy” as the anchor; treat “Pilot” as the first comparison. Then connect “Redesign” with “Unsuitable”. Those labels make The margin gate turns a calculation into an engineering decision a traceable part of the “healthy”–“pilot” decision, not an unsupported assertion.

The practitioner decision should also name the evidence owner. If the gateway is moved from a mast to a building wall, the link-budget owner must rerun the allowance, not simply reuse the earlier pass result. If a product team adds confirmed messages or a larger payload, the margin gate should be reopened because retry behavior and airtime can turn a coverage pass into an operations failure. The ledger is strongest when it records both the numeric answer and the condition that would make that answer stale.

Under the Hood: Models Need Field Evidence

Path-loss models translate distance and environment assumptions into estimated loss. A free-space estimate is a clean baseline, while log-distance and clutter-aware models add assumptions about terrain, buildings, foliage, antenna height, and indoor penetration. The model is useful only when its assumptions are documented and tested.

Start the evidence review for the “+14 dBm”–“antenna gain” decision: inspect Figure 3.4. Start at +14 dBm transmit power. Add the device and gateway antenna gains, subtract cable and connector losses, then reserve fade, obstruction, and installation margins before comparing the remaining allowance with measured path loss.

+

Treat every model output as a hypothesis to challenge. If the model assumes antennas several metres above ground but the real device is bolted inside a metal cabinet, the path-loss estimate is optimistic even when the arithmetic is correct. If the model assumes clear outdoor terrain but the deployment has wet foliage, reinforced concrete, or a service vehicle parked beside the enclosure, the field record must either measure those conditions or reserve enough margin to survive them. Gateway density is the same kind of under-the-hood question. One gateway may satisfy a coverage model yet still create weak receive diversity, high channel load, poor downlink opportunity, or fragile incident response. The release evidence should connect path-loss samples, gateway count, traffic pattern, and retest triggers into one decision.

Make the acceptance threshold explicit in the same record. For a rollout gate, the team might require each representative device class to keep reserved margin, join without repeated retries, avoid spending most traffic at the slowest data rate, and show at least one retest trigger for seasonal or installation change. Those criteria keep the model, the measurement, and the release decision tied together.

Numeric headroom in Figure 3.5 sits alongside gaps in gateway field measurements.

+

The chart subtracts a 26 dB reserve from a 149 dB raw budget, leaving 123 dB allowable path loss. A path at 118 dB has 5 dB headroom; one at 125 dB misses the limit by 2 dB. The lower panel asks for noise margin and data-rate distributions at the same hard locations with one, two, and three gateways. It supplies no measured series for those counts. A second gateway might hear a weak packet, but the diagram does not prove that benefit. Log signal, retries, join behavior, rate, and gateway identity in the field before keeping a gateway count or claiming better service.

A field team should therefore test the awkward cases on purpose. Put one device in the lowest meter pit, one behind the metal shed wall, one at the edge of the service area, and one near the busiest reporting cluster. Record received signal, noise margin, spreading factor or data-rate distribution, retries, join behavior, gateway identity, and whether a second gateway also heard the packet. If every easy point passes but the low pit consumes all reserved margin, the correct result is not "range proven"; it is "coverage depends on installation constraints." If many edge devices pass only at the slowest rate, the team should also check airtime and downlink pressure before approving the gateway count.

Inspect Figure 3.6 to ask which field cases are most likely to break the modeled link budget.

+

Read Figure 3.6 from deliberately different locations: open, indoor, edge, and obstructed cases reveal losses that an easy line-of-sight point will hide. At each one, record received signal and noise margin together rather than treating signal strength alone as quality. Then compare the data-rate distribution and retry rate, which expose links that pass only by consuming more airtime. Gateway load and the identity of the hearing gateway tie radio evidence to capacity. End with a pass, fail, or constrained result and the installation change that reopens it. The field record tests the assumptions most likely to fail, not merely the most convenient locations.