Cellular IoT · Study deck
Matching Apps to Cellular Tech
A basement water meter may send a daily total yet need to report a broken seal promptly.
Radio Remi is your guide for this deck.

After studying this chapter
Learning objectives
You will be able to:
- Explain: The example load makes cadence visible: a five-minute interval produces 12 × 24 = 288 records/day; at 100 payload bytes each, that is 28,800 payload bytes before protocol overhead.
- Explain: Its labelled evidence shows smart metering architecture with utility meter, MCU, NB-IoT module, cellular network, and utility backend, the distinction that anchors practitioner: review use cases as evidence patterns.
- Explain: In Figure: Fleet management architecture with GPS, the architecture begins with Fleet Telematics Evidence Flow, crosses: Telematics, and depends on: Platform for the next service function.
- Explain: A tamper event adds a 32-byte record.
Major section
Start With the Story
Every cellular Internet of Things (IoT) application has a rhythm.
- A payload is the useful data inside a message.
- A gateway is a device that passes data between different networks.
- A utility meter, asset tracker, industrial gateway, and safety monitor each send different payloads.
- They also tolerate different delays and need different support when a link fails.
Major section
Phoebe's Field Notes: Antenna Gain vs. Repetition Count in a Basement Meter
The mathematical gist: An illustrative 8 dBi installed antenna improvement is a 6.31× ideal combining factor.
- Starting from 128 repeats gives 20.3 ideal repeats.
Major section
Overview: Match The Application Before Choosing The Modem
Small, rare reports from fixed meters point first to NB-IoT.
- The battery row has no fixed winner.
- Sleep time, signal, retries, and downlink use set the full-cycle cost.
- The final note is a rule, not a rank.
Major section
Practitioner: Review Use Cases As Evidence Patterns
Maps, alerts, and APIs are outcomes only when one observed transaction joins those checkpoints.
- The example load makes cadence visible: a five-minute interval produces 12 × 24 = 288 records/day; at 100 payload bytes each, that is 28,800 payload bytes before protocol overhead.

Major section
Practitioner: Review Use Cases As Evidence Patterns (continued)
The field evidence must preserve identity, event time, route conditions, receipt, and service result so delayed positions cannot be presented as current ones.
- Its labelled evidence shows smart metering architecture with utility meter, MCU, NB-IoT module, cellular network, and utility backend, the distinction that anchors practitioner: review use cases as evidence patterns.
- Those labels make smart metering architecture with utility meter, MCU, NB-IoT module, cellular network, and utility backend concrete.
- In Figure: Fleet management architecture with GPS, the architecture begins with Fleet Telematics Evidence Flow, crosses: Telematics, and depends on: Platform for the next service function.
Major section
Separate a Meter Reading from a Tamper Alarm
A tamper event adds a 32-byte record.
- They exclude cellular signalling, security, transport headers and retransmissions, which may dominate a small exchange.
- Six records need 6 × 24 bytes = 144 bytes of local space before metadata.
- When service returns, the oldest reading is already about 6 hours old.
Major section
Separate a Meter Reading from a Tamper Alarm (continued)
A phone showing service outside the building does not demonstrate that a sealed pit provides the same link.
- A daily billing total may tolerate this delay; a tamper workflow may not.
- The battery calculation also changes with the alarm promise.
- The selection record should therefore distinguish stationary coverage evidence from route evidence.
Major section
Separate a Meter Reading from a Tamper Alarm (continued)
A modem that sleeps for long intervals can save energy, but a pending command cannot be assumed to reach it at once.
- The stored meter totals can still be useful after recovery if their timestamps survive.
- The alarm service has already missed its prompt notification target, even if the same bytes eventually arrive.
- The worked byte counts are illustrative; operator support and the modem's measured current profile decide the deployed behaviour.
Deck summary
Key takeaways
Every cellular Internet of Things (IoT) application has a rhythm.
- The mathematical gist: An illustrative 8 dBi installed antenna improvement is a 6.31× ideal combining factor.
- Small, rare reports from fixed meters point first to NB-IoT.
- Maps, alerts, and APIs are outcomes only when one observed transaction joins those checkpoints.
- The field evidence must preserve identity, event time, route conditions, receipt, and service result so delayed positions cannot be presented as current ones.
Retrieval practice
Recall check 1 of 5

Radio Remi says: answer from memory, then check your reasoning.
Q1A city water-meter pilot shows a phone has service near the curb, but the production meters will sit inside cast-metal basement cabinets and send small daily readings. What should the reviewer request first?
Show answer
Answer: A Cellular application selection should be grounded in device and service evidence, not general coverage branding.
Retrieval practice
Recall check 2 of 5

Radio Remi says: answer from memory, then check your reasoning.
Q2A city water-meter project has stationary devices, small scheduled readings, hard-to-access batteries, and many meters in basements. Which evidence best supports the cellular category decision?
Show answer
Answer: A Use-case selection connects the application pattern to coverage, power, payload, operator, and operations evidence.
Retrieval practice
Recall check 3 of 5

Radio Remi says: answer from memory, then check your reasoning.
Q3A tracker works in a lab modem session, but the release plan omits roaming rules, SIM ownership, battery measurement, and recovery after missed contact. What should the reviewer do?
Show answer
Answer: A A cellular IoT release needs operations evidence, not only a modem connection demonstration.
Retrieval practice
Recall check 4 of 5

Radio Remi says: answer from memory, then check your reasoning.
Q4A released tracker changes its enclosure and operator route. What should the release record require?
Show answer
Answer: D Both changes can alter the service evidence behind approval.
Retrieval practice
Recall check 5 of 5

Radio Remi says: answer from memory, then check your reasoning.
Q5A cross-border tracker sends exception reports while moving. Which comparison best supports its radio choice?
Show answer
Answer: C Mobility, traffic, power, operator path, and cost all affect the fit.
Print reference
Answers
Answer key.
- A · Cellular application selection should be grounded in device and service evidence, not general coverage branding.
- A · Use-case selection connects the application pattern to coverage, power, payload, operator, and operations evidence.
- A · A cellular IoT release needs operations evidence, not only a modem connection demonstration.
- D · Both changes can alter the service evidence behind approval.
- C · Mobility, traffic, power, operator path, and cost all affect the fit.