NB-IoT fit
Stationary meters, bins, valves, and environmental sensors with small payloads, long sleep intervals, and deep coverage needs.
12 Matching Apps to Cellular Tech
cellular-iot
Overview: Match The Application Before Choosing The Modem
Cellular IoT is strongest when devices are spread across wide areas, move between coverage regions, or need a managed network without site-owned gateways. The choice still has to be proven with application evidence: mobility, payload size, coverage, reachability, power budget, SIM lifecycle, and recurring operations cost.
Make the first pass a risk sort. A fixed meter, a mobile tracker, a camera gateway, and a private plant-floor controller may all use cellular service, but each puts pressure on a different part of the record. The application owner should name the hardest condition before the modem is chosen: deepest cabinet, longest route, largest update, strictest command window, weakest service region, or most expensive truck roll. That hardest condition becomes the pilot target.
Keep rejected options visible too. If LTE-M is rejected for a meter, note that mobility and fast downlink were not required. If NB-IoT is rejected for a tracker, note the route, reachability, and maintenance evidence. Those short rejection notes prevent later procurement or support teams from reopening the same question with only a coverage map or a plan price.
LTE-M fit
Moving assets, wearables, fleet devices, and equipment that need connected-mode mobility, more responsive downlinks, or larger updates.
Broadband fit
Video, high-rate telemetry, industrial gateways, or maintenance devices where power and data plans can support larger traffic.
Private 5G fit
Sites that need local policy control, operational isolation, predictable coverage ownership, or integration with industrial systems.
Selection Contract
A cellular application decision is reviewable when it records the device requirement, selected radio profile, operator coverage evidence, SIM or eSIM lifecycle, power mode, payload pattern, application owner, cost model, and retest trigger.
Practitioner: Review Use Cases As Evidence Patterns
Use cases are not marketing categories. Each one implies a different combination of mobility, payload cadence, downlink reachability, antenna placement, battery service, and operator contract. The examples below show what to prove before selecting a cellular category.
Write each pattern in the same evidence shape so the review can compare them. Start with the service promise, then record the installed location, traffic pattern, battery assumption, connectivity lifecycle, failure owner, and retest trigger. A table of use cases is useful only when every row can point to the evidence that would approve, reject, or segment that use case.
| Application | Likely Fit | Evidence That Decides |
|---|---|---|
| Asset tracking | LTE-M, multi-mode LTE, or broadband for image/video exceptions. | Movement pattern, location cadence, roaming policy, antenna placement, and battery impact from GNSS and attach retries. |
| Smart metering | NB-IoT for small scheduled readings; LTE-M where faster control or larger updates are required. | Meter location survey, deep indoor margin, reporting interval, power mode, certification, and backend data-retention needs. |
| Fleet telematics | LTE-M, LTE Cat-1, or broadband depending on diagnostics and media needs. | Vehicle power, update frequency, handoff behavior, OBD or CAN data volume, and exception media policy. |
| Agricultural sensors | NB-IoT or LTE-M where operator coverage is validated; private LPWAN when cellular is weak or uneconomic. | Rural coverage test, antenna height, service visit cost, reporting interval, battery and solar assumptions, and seasonal change. |
Worked Review: Water Meter Fleet
A utility wants scheduled readings from meters in basements and outdoor pits. The reviewer asks for meter-location survey data, operator NB-IoT profile support, reporting interval, PSM timer behavior, battery measurement, backend retention, and owner response for failed reads before accepting the technology fit.
Under The Hood: Keep The Operations Evidence Visible
The modem is only one part of the decision. A cellular IoT release also depends on operator configuration, SIM or eSIM lifecycle, private APN or internet egress, sleep and reachability behavior, firmware update path, certification, and the support model after deployment.
Keep the record cross-functional. Firmware owns modem state, retry limits, and update behavior; network operations owns APN, routing, and operator escalation; product operations owns provisioning, decommissioning, and support response. When those owners are not named, a small field failure can move between teams without resolution. Under-the-hood review therefore asks which log or record each owner will use when a device attaches, fails to deliver, drains its battery, roams unexpectedly, or misses a queued command.
| Evidence Area | What To Record | Retest Trigger |
|---|---|---|
| Coverage and antenna | Installed signal evidence, indoor or mobile cases, antenna placement, and coverage exceptions. | New site type, enclosure, antenna, operator, band, or installation method. |
| Power and reachability | PSM/eDRX or connected behavior, measured current profile, downlink expectations, and recovery after missed contact. | Reporting interval, firmware update policy, alarm latency, or battery target changes. |
| Identity and service | SIM/eSIM ownership, activation flow, roaming rules, APN or egress path, suspension, and decommissioning. | Carrier, MVNO, region, ownership, or procurement model changes. |
| Cost and support | Five-year TCO assumptions, field service model, plan tier, diagnostics, and owner response to failures. | Device count, payload volume, service-level promise, or support contract changes. |
Release Gate
Do not accept a cellular application decision until the record explains why the chosen category is sufficient and what would force a revisit. Good records reject one-size-fits-all answers: a sparse utility fleet, a moving asset tracker, and a private industrial site have different evidence boundaries.
12.1 Start With the Story
Every cellular IoT application has a rhythm. A utility meter, asset tracker, industrial gateway, and safety monitor each send different payloads, tolerate different delays, and need different support when the link fails.
Start simple: name the application’s reporting rhythm and consequence of silence before mapping it to a cellular technology.
Phoebe’s Field Notes: Antenna Gain vs. Repetition Count in a Basement Meter
Phoebe’s Why
Coverage in a shielded basement is fought on two fronts that both spend the same currency: margin in decibels. An antenna with more gain does not add power – it reshapes a fixed total of radiated power into a narrower cone pointed where it is needed, which is exactly what a dBi rating describes. NB-IoT’s coverage-enhancement mode pays with the same currency by a different route: it repeats the same message and lets the receiver combine the copies, and every doubling of repeats buys roughly another 3 dB of effective sensitivity. The difference is cost. The antenna’s decibels are free after installation. The repetition-count decibels are billed on every single uplink, in extra transmit time and extra battery current, for the life of the meter.
The Derivation
EIRP folds transmit power and antenna gain into one budget number:
\[\mathrm{EIRP}_{\mathrm{dBm}} = P_{t,\mathrm{dBm}} + G_{\mathrm{dBi}}\]
with effective aperture \(A_e = G\lambda^2/4\pi\) describing the same gain on receive.
Repeating a message \(R\) times and combining the copies buys an idealized combining gain:
\[\Delta S \approx 10\log_{10}(R)\]
(an energy-combining upper bound; real non-coherent NB-IoT combining gains less). A fixed decibel shortfall can therefore be closed by antenna gain \(G_{\mathrm{dBi}}\) or by \(10\log_{10}(R)\) of repetition – the same margin, two different bills.
Worked Numbers: Closing the Basement Margin
- Built-in vs. external antenna (catalog-typical): compact NB-IoT module antenna \(\approx 0\) dBi; external panel/Yagi routed to a wall penetration point \(\approx 8.00\) dBi, so \(\Delta G = 8.00\) dB of EIRP
- Repetition-doubling gain: \(10\log_{10}(2) = 3.01\) dB per doubling
- Doublings equivalent to 8.00 dB: \(8.00/3.01 = 2.66 \to 2^{2.66} = 6.31\times\)
- If the basement link needs \(R_0 = 128\) repeats (NB-IoT CE Level 2 max, catalog-typical) to close margin without the antenna, the 8.00 dB is worth cutting that to \(128/6.31 = 20.3\), i.e. the next standard repetition step down, \(R' = 16\) – a \(128/16 = 8.00\times\) reduction
- Battery tie: at fixed per-repetition TX current and duration, transmit energy per uplink scales linearly with repetition count, so cutting repeats from 128 to 16 cuts radio energy per uplink by the same \(8.00\times\) – directly stretching the radio-dominated share of the meter’s battery life by roughly that factor
12.2 Summary
Cellular IoT application selection starts from the application promise, not from a modem category. NB-IoT, LTE-M, broadband cellular, and private 5G each fit different mixes of mobility, payload, coverage, power, reachability, and operations ownership.
The strongest decisions record installed coverage, payload cadence, power mode, SIM lifecycle, cost model, support owner, and retest trigger before scaling the deployment.
12.3 Key Takeaway
Choose cellular IoT by matching the application evidence to the radio and service profile; do not treat coverage maps, phone tests, or generic cellular branding as release evidence.
12.4 See Also
- Cellular IoT Overview introduces the cellular IoT family and its main deployment boundaries.
- NB-IoT vs LTE-M Comparison compares the two main LPWAN cellular categories.
- Cellular IoT Deployment Planning expands coverage, operator, rollout, and support evidence.
- Cellular IoT Power Optimization explains PSM, eDRX, reporting cadence, and measured current profiles.