LoRa & LoRaWAN · Study deck

LoRaWAN vs LPWAN Alternatives

A farm's far field sits behind a ridge.

Radio Remi is your guide for this deck.

lpwan

After studying this chapter

Learning objectives

You will be able to:

Explain: A technology is ready only when the operations team can explain how it will detect missing data, diagnose the responsible boundary, and revisit the choice after site, device, payload, policy, or provider changes.
Explain: A managed alternative priced at £12 per device per year would cost 80 × £12 = £960 before any installation or exception fees.
Explain: That small count does not settle the choice: the gateway location may cost more to operate than the data service.
Explain: LoRaWAN can be a good candidate when gateway placement, network-server routing, device profiles, and application ownership are under review.

Major section

Start Simple · Overview: Compare Evidence, Not Labels

A gateway is the unit that receives nearby device messages and passes them to the wider service.

Its site and owner can decide whether the path works.
A rare valve command must also get back to them.
The sites are far apart, mains power is absent, and one field sits behind a hill.

LPWAN comparison review map showing deployment question, hard constraints, evidence request, candidate shortlist, pilot record, and release decision. — LPWAN comparison moves from deployment question to hard constraints, evidence request, shortlist, pilot record, and release decision.

Major section

Practitioner: Shortlist by Hard Constraints

When two candidates survive, do not force a premature winner.

A defensible shortlist separates technology capability from service availability and operations.
LoRaWAN can be a good candidate when gateway placement, network-server routing, device profiles, and application ownership are under review.
Provider service evidence, site survey, module behavior, and operational support boundary.

Boundary evidence separates network ownership, provider dependence, message limits, and hybrid deployment paths.

Major section

Under the Hood: Release Records Beat Generic Rankings

LPWAN comparison becomes risky when a team treats the candidate list as a scoreboard.

The release record should state assumptions, exceptions, pilot limits, unresolved risks, rollback path, and recheck triggers.
The hard part is that many failures look identical at the dashboard.
A generic ranking cannot route that work.

The release record turns a technology comparison into an auditable operations decision.

Major section

Under the Hood: Release Records Beat Generic Rankings (continued)

The release record must say which boundary owns each symptom and which evidence proves that boundary is healthy.

A technology is ready only when the operations team can explain how it will detect missing data, diagnose the responsible boundary, and revisit the choice after site, device, payload, policy, or provider changes.
It also has to protect the future choice.
Without that record, the same shortlist gets reused after its assumptions have expired.

Major section

Compare the Cost of Owning the Hilltop Receiver

That small count does not settle the choice: the gateway location may cost more to operate than the data service.

The private gateway path has £600 of backhaul and power costs, plus two £150 maintenance visits, totalling £900.
A managed alternative priced at £12 per device per year would cost 80 × £12 = £960 before any installation or exception fees.
The £60 gap is too narrow to justify selection without coverage, lifecycle and service evidence.

An evidence matrix keeps each candidate tied to the behaviors the application will actually need.

Major section

Compare the Cost of Owning the Hilltop Receiver (continued)

The gateway and subscription costs here are classroom assumptions, not market prices.

The LoRaWAN candidate needs an installed gateway and a tested return path.
The alternatives need equally concrete service evidence; a coverage map cannot stand in for a message from the far field.
Its lower cost would not cure that hard failure.

Major section

Compare the Cost of Owning the Hilltop Receiver (continued)

This module distinguishes LoRaWAN from the wider LPWAN family because operational ownership changes with the network.

The alternatives should be rejected or assigned only to the delay-tolerant probes.
Combining LoRaWAN with a backup path adds credentials, state and a rule for recognizing duplicate readings.
A useful selection makes that work visible beside payload, energy and timing.

Deck summary

Key takeaways

A gateway is the unit that receives nearby device messages and passes them to the wider service.

When two candidates survive, do not force a premature winner.
LPWAN comparison becomes risky when a team treats the candidate list as a scoreboard.
The release record must say which boundary owns each symptom and which evidence proves that boundary is healthy.
That small count does not settle the choice: the gateway location may cost more to operate than the data service.

Retrieval practice

Recall check 1 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q1A farm operator wants battery soil probes in low fields, pallet trackers that leave the property, and rare valve downlinks. The team says LoRaWAN is best because it is low power and long range. What should the reviewer ask for first?

AApprove one LoRaWAN plan for all groups solely because messages are small.

BUse roadside coverage maps without low-field probe or valve-downlink tests.

CReject hybrid LPWAN before checking which groups need local or provider service.

DCompare payload, mobility, gateway ownership, downlink needs, pilots, and retests by group.

Show answer

Answer: D LPWAN comparison starts with the behavior of each device group, the ownership boundary, and observed evidence from the actual deployment.

Retrieval practice

Recall check 2 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q2A campus can install gateways and wants local coverage logs, routing control, and application integration ownership. Which candidate deserves first review?

AA provider-managed LPWAN path, to reduce the campus team's gateway maintenance workload

BLoRaWAN, with gateway placement, link margin, device class, security, and operations evidence

CThe smallest-payload service, because tiny messages remove operations work

DA broad LPWAN pilot, postponing the shortlist until field coverage results are available

Show answer

Answer: B LoRaWAN is a strong first candidate when local gateway and network evidence are central, but it still needs a pilot record.

Retrieval practice

Recall check 3 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q3When is a hybrid LPWAN design more defensible than forcing every device onto one technology?

AWhen the team wants to avoid separate pilot records for device groups.

BWhen all radio candidates show identical field behavior and ownership.

CWhen distinct device groups have evidenced paths, owners, and release limits.

DWhen one successful uplink proves the route and payload requirements for every planned device location.

Show answer

Answer: C Hybrid LPWAN designs need explicit boundaries, owner decisions, and release evidence for each path.

Retrieval practice

Recall check 4 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q4A team compares private LoRaWAN and cellular service for moving sensors. What belongs in the pilot ledger?

AUse different success rules for LoRaWAN and cellular, omitting common route evidence.

BSkip mobility evidence because both candidates are described as LPWAN services.

CUse the same route, downlink, power, owner and failure fields for both candidates.

DKeep vendor range headlines because published range is enough to predict the installed route and support effort.

Show answer

Answer: C Comparable pilot fields make the shortlist a testable decision.

Retrieval practice

Recall check 5 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q5A chosen LPWAN path fails at one site during an outage. What release rule should already exist?

AMove the entire fleet silently to another service after one site's failed network path.

BName fallback owner and trigger a recheck of the affected site and device group.

CKeep the old release claim unchanged because the original successful site represents the complete rollout.

DAssume a second interface suffices because interface diversity provides recovery when the first path fails.

Show answer

Answer: B The release boundary needs an owner, exception, fallback, and new evidence.

Print reference

Answers

Answer key.

D · LPWAN comparison starts with the behavior of each device group, the ownership boundary, and observed evidence from the actual deployment.
B · LoRaWAN is a strong first candidate when local gateway and network evidence are central, but it still needs a pilot record.
C · Hybrid LPWAN designs need explicit boundaries, owner decisions, and release evidence for each path.
C · Comparable pilot fields make the shortlist a testable decision.
B · The release boundary needs an owner, exception, fallback, and new evidence.