← Back to the chapter · Next detail →
Technical detail · NB-IoT Metering and Telemetry
Coverage, power and reachability evidence
For coverage, collect installed radio indicators, delivery logs, retry counts, antenna and enclosure notes, and the service profile. A coverage map or lab attach cannot prove a basement, cabinet or rural installation. Retest after changes to antenna, enclosure, operator, region, mounting height or site type. Use NB-IoT Coverage Enhancement to examine the radio behavior behind this evidence.
For power state, capture current traces for search, attach, transfer, receive windows, retries, sleep, sensor activity and recovery. Estimating battery life from a modem sleep-current line omits whole-device behavior. Retest when firmware, timer policy, payload cadence, coverage class, battery or sensor duty cycle changes.
For reachability, record command-delay tolerance, wake schedule, acknowledgement policy, maintenance window and failure response. A sleeping endpoint cannot be assumed to behave like an always-reachable controller. Revisit the evidence when command timing, alarm policy or support workflow changes.
For operations, record SIM lifecycle, APN or profile ownership, monitoring fields, escalation, decommissioning and data retention. Without remote diagnosis, every field issue may become a site visit. Recheck after changes to operator contract, fleet size, backend path, ownership or retirement process.
These boundaries explain why generic “low power” or “deep coverage” claims are insufficient. Approval depends on measured behavior for the selected application and deployment.