Core Networking · Study deck

Link Budget and Coverage Planning

A gateway hears a field sensor reliably, but configuration commands rarely return.

Packet Pete is your guide for this deck.

proplinkbudget

Packet Pete, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

Follow this chapter path with evidence at each boundary.

Name the system boundary.
Record the evidence needed there.
Keep the next decision tied to the source.

Build one radio gain-and-loss ledger. Compare received power with the selected sensitivity and reserve. Check uplink and return path with field evidence.

Major section

Start With the Margin You Need to Trust

A gateway means the device or service that joins the local radio network to another system.

This proves one path and set of conditions, not every season or site; the deeper sections derive the budget and examine fade, uncertainty, and release limits.
A link budget is the story of a signal from transmitter to receiver with every gain and loss written down.
For IoT, the budget becomes a release gate.

Major section

Overview: A Link Budget Turns Range Into A Checkable Record

Each step adds one line to the record.

Antenna gains at both ends are added, then path, cable and wall losses are subtracted.
The running total is compared with receiver sensitivity, which is where a design first looks either promising or short.
A calculated pass still needs field validation.

The decision is a chain: radio settings create launched power, deployment losses reduce it, and the remaining margin decides whether the link is ready for field validation.

Major section

Practitioner: Build The Budget As A Deployment Ledger

Maximum coupling loss is the total loss that the pair can bear, not a range claim.

The link still needs margin for fades, model error, weather, antenna angle, and age.
The record should name each source, site type, receiver setting, spare margin, and field test that backs or changes the model.

LPWAN coverage planning depends on a ledger of radio terms, path assumptions, installation losses, and the margin required for reliable reporting.

Major section

Practitioner: Build The Budget As A Deployment Ledger (continued)

The example signal starts at 14 dBm of transmit power and gains 2 dBi from the antenna.

Cable loss takes 1 dB back, which looks trivial.
The fade margin, typically 10 to 20 dB, is held back after it, not before.
The final box asks whether what remains still sits above receiver sensitivity.

Major section

Under The Hood: Margin Is Where Assumptions Become Risk

Stage two compares that with a receiver sensitivity of -118 dBm, and the gap is 23 dB.

Stage three is the one a review must not skip.
The remaining value, not the raw gap, supports release.
Field percentiles and outage behaviour must still confirm that the chosen reserve covers the required service condition.

The calculation is additive in dB units: add gains, subtract losses, then compare the result with receiver sensitivity.

Major section

Under The Hood: Margin Is Where Assumptions Become Risk (continued)

The urban path in the illustration adds buildings, lower antennas, reflections, interference, and penetration loss, consuming link budget quickly.

The rural path offers clearer geometry and fewer obstructions, so the same transmitter, receiver, and settings can cover roughly five to fifteen times the distance in this illustration.
That ratio is an observed class, not a conversion rule for every site.
Gateway height, terrain, foliage, indoor placement, and traffic load still change coverage.

The same radio can behave very differently in dense urban, indoor, and open rural paths because the environment changes the loss terms.

Major section

Check Both Directions before Calling the Site Covered

Separate illustrative waterfall: 14+2−1−105=−90 dBm.

Name the system boundary.
Record the evidence needed there.
Keep the next decision tied to the source.

A waterfall view helps review every gain and loss in order, especially when a design looks good on path loss alone but weak after installation losses are included.

Uplink ledger: 14+2−96−15=−95 dBm; 23−10=13 dB.

Major section

Check Both Directions before Calling the Site Covered (continued)

Its coverage calculation changes even if no hardware moves.

If its selected mode requires −110 dBm, the nominal margin is only 9 dB.
Sensitivity belongs to a particular receiver and setting; it is not a universal property of the site.
A radio acknowledgement alone need not prove the requested configuration was applied.

Deck summary

Key takeaways

A gateway means the device or service that joins the local radio network to another system.

Each step adds one line to the record.
Maximum coupling loss is the total loss that the pair can bear, not a range claim.
The example signal starts at 14 dBm of transmit power and gains 2 dBi from the antenna.
Stage two compares that with a receiver sensitivity of -118 dBm, and the gap is 23 dB.

Retrieval practice

Recall check 1 of 3

Packet Pete says: answer from memory, then check your reasoning.

Q1What is the main decision a link budget should support before an IoT wireless deployment?

AWhether a vendor brochure advertises a long maximum range.

BWhether received power clears sensitivity after losses and reserve.

CWhether transmit power stays below the regulatory ceiling.

DWhether the selected antenna has a published gain figure.

Show answer

Answer: B The useful decision is whether the link has enough margin after gains, losses, and reserve assumptions are recorded.

Retrieval practice

Recall check 2 of 3

Packet Pete says: answer from memory, then check your reasoning.

Q2A gateway move adds a longer antenna cable and places the antenna behind a parapet. What should happen to the link-budget record?

ALeave the budget unchanged because the same radio protocol is still being used.

BRemove receiver sensitivity from the record because the gateway location changed.

CRecord the new cable and obstruction losses, then recheck field margin.

DIncrease the advertised range value and skip field validation.

Show answer

Answer: C The physical installation changed, so the budget needs new loss terms and validation against measured signal quality.

Retrieval practice

Recall check 3 of 3

Packet Pete says: answer from memory, then check your reasoning.

Q3Why is a positive nominal link margin still not enough for release in a real IoT deployment?

ABecause receiver sensitivity is unrelated to whether a link works.

BBecause free-space models must be replaced with an indoor model.

CBecause datasheet antenna gain should be removed from the budget.

DBecause reserve may miss fading, site loss, and measurement uncertainty.

Show answer

Answer: D A nominal pass is only useful when the reserve terms and field validation show the link can survive real deployment variation.

Print reference

Answers

Answer key.

B · The useful decision is whether the link has enough margin after gains, losses, and reserve assumptions are recorded.
C · The physical installation changed, so the budget needs new loss terms and validation against measured signal quality.
D · A nominal pass is only useful when the reserve terms and field validation show the link can survive real deployment variation.

B · Compare received power with sensitivity after losses and reserve. C · Recalculate cable and obstruction losses after a move. D · Validate reserve against site variation.