Core Networking · Study deck

Wide-Area Access: LPWAN and Cellular

Picture a soil probe that sends four small readings each day.

Packet Pete is your guide for this deck.

networkphysicallpwan

After studying this chapter

Learning objectives

You will be able to:

Explain: LoRaWAN and Sigfox use shared, unlicensed spectrum, but that does not mean either service is automatically privately deployable: LoRaWAN can use owner-operated gateways, whereas Sigfox service normally depends on its operator network.
Explain: This chapter does not provide one universal range, data-rate, or current-draw number for every candidate, and a datasheet range or transmit-current figure would not prove the installed service anyway.
Explain: Figure: The selection record should preserve the workload is a record to be filled in, so read each block for the evidence it demands rather than the topic it names.

Major section

Start With Reach Before Speed

It sits far from the farm office and must run for years.

A fast link may waste power.
A long-range link may fit if it can carry the small job with clear support.
A payload is the useful data carried in a message: Latency means the time from sending work to receiving the needed result.

Major section

Start With Reach Before Speed (continued)

A gateway is a device or service that joins the field radio path to a wider network.

LoRaWAN is a low-power wide-area network in which gateways forward radio messages to a network service.
Long reach does not mean endless reach.
Under the Hood covers link budget, air-time limits, mobile service, and power states.

Major section

Start With Reach Before Speed (continued)

Those details can overturn a paper choice.

LPWAN and cellular choices begin with reach, ownership, power, and service model before raw throughput.
A tiny sensor that reports once an hour and a mobile gateway that streams diagnostics do not need the same wide-area network.
The right technology is the one whose constraints match that record.

Major section

Overview: Wide-Area IoT Trades Bandwidth For Reach

LPWAN and cellular IoT links are chosen when sensors must reach beyond a building, campus, or Wi-Fi cell while using small batteries.

The first design question is not which radio is newest.
Neither family is automatically better.
The practical distinction is therefore not only range.

Wireless selection starts from a bounded workload and compares the same range, data-rate, and power evidence before a radio is chosen.

Major section

Overview: Wide-Area IoT Trades Bandwidth For Reach (continued)

A private LoRaWAN deployment may let the owner place gateways where the sensors actually are, but it also makes gateway siting, network-server operation, shared-spectrum behavior, and regional airtime limits part of the design.

A link that is excellent for four tiny readings per day can be wrong for streaming diagnostics or interactive control, even if both use the phrase "wide area.".
The comparison at Figure: Wireless selection starts from a bounded workload and turns the selection step into an evidence check.
The empty cells in Figure: Wireless selection starts from a bounded workload and are deliberate.

Major section

Overview: Wide-Area IoT Trades Bandwidth For Reach (continued)

This chapter does not provide one universal range, data-rate, or current-draw number for every candidate, and a datasheet range or transmit-current figure would not prove the installed service anyway.

The worked LoRaWAN values are tied to the chapter's named model assumptions; the other cells preserve the evidence boundary instead of inventing comparable-looking numbers.
Until those are recorded, a wide-area choice is a preference rather than a design.
The rate row runs from about 100 b/s at one end to roughly 1 Mb/s at the other.

Major section

Overview: Wide-Area IoT Trades Bandwidth For Reach (continued)

LoRaWAN and Sigfox use shared, unlicensed spectrum, but that does not mean either service is automatically privately deployable: LoRaWAN can use owner-operated gateways, whereas Sigfox service normally depends on its operator network.

NB-IoT and LTE-M use licensed cellular spectrum and generally require an operator agreement.
The panel's distinguishing strengths, including mobility, downlink, and service ownership, decide which option fits; check site coverage and the device power cycle too.
Unlicensed LPWANLoRaWAN and similar systems can support private or community infrastructure, but must live within shared-spectrum rules and duty-cycle or airtime limits.

LPWAN and cellular IoT options separate along spectrum ownership, throughput, mobility, downlink, and power-management boundaries.

Major section

Practitioner: Build A Coverage And Cadence Record

Land, walls, antenna height, gateway spacing, and fades decide how fast that budget is spent.

Include the best, typical, and worst install locations; the normal message; the largest exceptional message; the expected acknowledgement pattern; and the fallback when a report is missed.
For battery devices, keep one measured current trace that includes wake, attach or join, transmit, receive-window behavior, retry, and return to sleep.
The spare margin must cover doubt and the service goal.

Long range is earned through link budget, antenna placement, path loss, gateway density, and margin, not through a data-sheet range number alone.

Major section

Practitioner: Build A Coverage And Cadence Record (continued)

Payload size, reporting interval, burst behavior, downlink need, firmware-update expectation.

For managed networks, keep the provisioning path, owner, renewal date, and support route beside the radio evidence.
Maximum coupling loss is the total loss the link can bear; it is not a distance.
RSSI/SNR or cellular signal reports at real install points.

Major section

Practitioner: Build A Coverage And Cadence Record (continued)

Failure It Prevents.

Figure: The selection record should preserve the workload is a record to be filled in, so read each block for the evidence it demands rather than the topic it names.
The four blocks of Figure: The selection record should preserve the workload run in the order the evidence has to be gathered.
The fourth names who owns the network and when the arrangement expires.

The selection record should preserve the workload, coverage, power, and ownership assumptions that made a wide-area technology acceptable.

Major section

Under The Hood: Radio Physics Meets Service Model

Wide-area IoT is a stack of constraints.

The radio layer controls link budget, airtime, interference, and energy per message.
The service layer controls network ownership, SIM or device provisioning, roaming, downlink timing, firmware-update path, and long-term continuity.
The radio side starts with a link budget, not with an advertised range number.

The IEEE 802.15.4 stack places Zigbee or Thread applications above transport, network, MAC and PHY layers, including 6LoWPAN or Zigbee networking choices and 2.4 GHz or sub-GHz radios.

Major section

Under The Hood: Radio Physics Meets Service Model (continued)

Transmit power, antenna gain, receiver sensitivity, path loss, building loss, terrain, foliage, interference, and fade margin decide whether a packet can be heard at the gateway or base station.

Lower data rates can improve sensitivity, but they keep the transmitter on air for longer.
That longer airtime can consume battery, reduce channel capacity, increase collision exposure, and run into regional duty-cycle or fair-use limits.
The service side is just as technical.

Major section

Under The Hood: Radio Physics Meets Service Model (continued)

The last card holds the 5G categories for dense and reduced-capability devices.

A design that looks efficient for one sensor can fail when thousands of devices wake near the same reporting window.
Provisioning also becomes part of the system: keys, SIM profiles, roaming permissions, operator coverage, gateway backhaul, and network-server ownership decide whether the radio path remains usable after rollout.
Airtime PressureLow data rate increases time on air.

5G service categories separate massive low-rate devices, low-latency control, and high-bandwidth broadband workloads.

Major section

Under The Hood: Radio Physics Meets Service Model (continued)

A wide-area design needs radio and service evidence tied to real sites, payload schedules, and support owners.

An IP-based Thread stack can use 6LoWPAN, IPv6, and UDP for application traffic; Zigbee uses its own network and application layers.
Local mesh or scheduled access still needs a separate wide-area path when the application requires one.
The first is early machine traffic on 2G and 3G: devices reused ordinary mobile modems, so coverage was wide but energy demand and sunset risk were high.
The footer under Figure: Cellular IoT moved from repurposed mobile data toward is the line to keep.

Cellular IoT moved from repurposed mobile data toward purpose-built low-power and service-category options.

Deck summary

Key takeaways

It sits far from the farm office and must run for years.

A gateway is a device or service that joins the field radio path to a wider network.
Those details can overturn a paper choice.
LPWAN and cellular IoT links are chosen when sensors must reach beyond a building, campus, or Wi-Fi cell while using small batteries.
A private LoRaWAN deployment may let the owner place gateways where the sensors actually are, but it also makes gateway siting, network-server operation, shared-spectrum behavior, and regional airtime limits part of the design.

Retrieval practice

Recall check 1 of 4

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

Q1A field sensor sends a small soil-moisture reading four times per day and must run for years on a battery. Which first question best narrows the access choice?

AWhich product page claims the longest range for outdoor battery sensors?

BWhich module advertises the newest cellular label for this class of sensor?

CWhat coverage, cadence, payload, battery, ownership, and downlink needs must it meet?

DWhich plan offers the largest data allowance for a four-reading-per-day device?

Show answer

Answer: C LPWAN and cellular choices are workload decisions: payload, cadence, range, power, coverage, ownership, mobility, and downlink requirements drive the shortlist.

Retrieval practice

Recall check 2 of 4

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

Q2A water-meter pilot works beside the office gateway but fails in several basement meter rooms. What should stop the rollout?

AThe LPWAN label guarantees usable coverage in every basement room.

BA small meter payload removes the need to check retries and coverage.

CLong sleep intervals guarantee reachable downlink at the site.

DOffice-gateway success lacks basement coverage and margin evidence.

Show answer

Answer: D A pilot must prove coverage, link margin, retry behavior, and power behavior at representative install points before rollout.

Retrieval practice

Recall check 3 of 4

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

Q3Which review finding should fail an LPWAN or cellular IoT design before procurement?

AThe design assumes one vendor range number and one lab transmit test are enough for all buildings, terrain, operators, and battery targets.

BThe design records payload cadence, field coverage evidence, power profile, provisioning process, and fallback behavior.

CThe design chooses private LPWAN because the owner can place gateways and validate link margin for the actual terrain.

DThe design selects cellular IoT after confirming operator coverage, subscription terms, device provisioning, and power-mode behavior.

Show answer

Answer: A Wide-area IoT decisions fail when they rely on generic range claims instead of tested coverage, link margin, power, provisioning, and lifecycle evidence.

Retrieval practice

Recall check 4 of 4

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

Q4A remote meter sends tiny payloads, yet its battery fails early at weak-signal sites. Which evidence should the team collect?

AUse clean-lab payload bytes alone as an explanation for field battery drain.

BMeasure radio-on time, retries, wake cycles and current at weak-signal sites.

CUse provider coverage maps alone rather than installed-meter current traces.

DUse cloud dashboard refresh rate alone to explain device radio energy.

Show answer

Answer: B A small payload can still cost energy when radio time and retries grow.

Print reference

Answers

Answer key.

C · LPWAN and cellular choices are workload decisions: payload, cadence, range, power, coverage, ownership, mobility, and downlink requirements drive the shortlist.
D · A pilot must prove coverage, link margin, retry behavior, and power behavior at representative install points before rollout.
A · Wide-area IoT decisions fail when they rely on generic range claims instead of tested coverage, link margin, power, provisioning, and lifecycle evidence.
B · A small payload can still cost energy when radio time and retries grow.