IoT Connectivity: ThingSpace Across LTE-M, NB-IoT and 5G RedCap

The Three IoT Profiles and What They Carry

Snapshot: IoT connectivity splits cleanly across three radio profiles. NB-IoT for the smallest messages at lowest power; LTE-M for moderate telemetry at broader coverage; 5G RedCap for mid-tier throughput at lower power than consumer 5G.

NB-IoT (Narrowband IoT) is the narrowest and lowest-power profile. Throughput runs in the 30 to 60 kbps range. The target devices are stationary and send small messages infrequently — a smart electric meter reporting kWh hourly, an environmental sensor reporting temperature every ten minutes, a parking-space sensor reporting occupancy on each state change. NB-IoT's deep-building penetration is a meaningful feature for basement meter rooms, underground parking structures and sub-grade utility vaults where other profiles struggle with signal. Battery lifetimes on NB-IoT devices routinely run five to ten years.

LTE-M (Long-Term Evolution for Machines) sits between NB-IoT and consumer LTE in the capability stack. Throughput runs up to approximately 1 Mbps. Cell handover is supported, which lets devices move between cells without dropping the session — this is the feature that differentiates LTE-M from NB-IoT for mobile applications. Target devices include asset trackers following shipments across distances, wearable health-monitoring devices that follow the wearer, fleet-tracking units on lighter vehicles, and point-of-sale terminals at pop-up events. LTE-M supports both power-saving modes and always-on connectivity depending on the profile the customer chooses.

5G RedCap (Reduced Capability) is the mid-tier throughput profile introduced with the 5G generation. Throughput runs 80 to 220 Mbps with lower power consumption than consumer 5G but materially higher than LTE-M. Target devices include point-of-sale terminals that serve rich video or high-resolution product imagery, kiosks with full-screen touch interaction, digital signage that rotates video content, industrial telemetry bridges that aggregate local sensor traffic and stream upstream, and mid-tier asset trackers that require faster update rates than LTE-M provides. RedCap is the newest of the three profiles and deployment is expanding alongside the 5G Ultra Wideband footprint — see 5G Business for the broader 5G layer context.

Profile, Throughput and Typical Use Case

Snapshot: the profile ladder breaks cleanly by throughput, mobility support and target device class. A customer with a mixed fleet can run all three on the same ThingSpace master.

ThingSpace Platform and SIM Lifecycle

Snapshot: ThingSpace is the managed platform that makes an IoT SIM fleet manageable at scale. Activation, profile change, rate-plan swap, usage monitoring and retirement all run through one admin console and one REST API.

Without a management layer, operating an IoT SIM fleet means tracking SIMs individually across the manufacturing, provisioning, deployment, operating and retirement phases. ThingSpace collapses this into a single lifecycle view. A SIM enters the admin inventory at shipment from the Verizon fulfilment centre. The admin activates it on the chosen profile — NB-IoT, LTE-M or RedCap — and binds it to a device identifier (IMEI or manufacturer serial number). The SIM enters the operating phase on its initial rate plan. Usage, errors and connection quality report up to the dashboard. When the SIM is nearing retirement, the admin can transition it between profiles over the air without a physical SIM swap, or can deactivate it entirely.

Rate plans on ThingSpace split by expected usage profile. Small-message plans are optimised for NB-IoT devices reporting kilobytes per day. Moderate-telemetry plans serve LTE-M fleets. Higher-throughput plans serve RedCap deployments. Pooled rate plans across a customer's fleet work similarly to Verizon Wireless Business pooled data — aggregate allowance across many SIMs flatten spiky usage patterns without triggering overage on individual lines.

Bulk activation is the primitive most customers with sizable fleets run daily. A CSV or Excel manifest lists the ICCIDs of SIMs to activate, their device identifiers, the chosen profile and the initial rate plan. ThingSpace validates the manifest, runs activation, and returns a result file. Properly formatted manifests of several thousand SIMs complete in minutes. The API-driven equivalent lets a manufacturer integrate activation into their production line — the SIM activates automatically when the assembled device passes a specific test-point on the factory floor. Regulatory posture for M2M services aligns with FCC Title II common-carrier framework under industry practice published by the CTIA.

Device Profiles and Pre-Provisioned Modules

Snapshot: IoT devices ship with radio modules that support one or more of the three profiles. Profile selection at activation pins the SIM to the radio profile the module supports.

An IoT device's radio module determines the profiles it supports. A device built around a cellular module that supports only NB-IoT will never operate on LTE-M or RedCap — the admin must pin the SIM to NB-IoT at activation. A multi-profile module that supports LTE-M plus NB-IoT lets the admin choose at activation time and transition over the air later if the traffic profile evolves. A RedCap-capable module typically supports fallback to LTE-M where RedCap coverage has not reached, keeping the device operational outside the Ultra Wideband footprint. Verizon publishes a certified-module list to help device designers select the right radio.

Pre-provisioned modules skip the activation step entirely. The manufacturer embeds a SIM at manufacture, and the module arrives at the customer with the SIM already tied to the customer's ThingSpace master. Deployment is plug-and-power. This pattern is common in fleet-tracker and asset-tracker market where the device-maker and the customer coordinate on the SIM provisioning at the factory rather than post-shipment.

Integration and Reporting

Snapshot: ThingSpace exports into customer analytics, fleet-management and billing systems through a REST API and SCIM-compatible usage reports.

The ThingSpace REST API exposes the primitives a customer's back-office systems want. SIM-activation endpoints let device onboarding workflows trigger activation directly. Profile-change endpoints let usage-monitoring systems up-tier or down-tier a device based on observed traffic. Usage endpoints pull per-device consumption for downstream billing or capacity planning. The authentication model uses OAuth 2.0 bearer tokens tied to role-scoped credentials so an automated workflow cannot accidentally perform an action outside its scope. The broader master-account admin console integrates with the wireless fleet through the My Verizon administrator portal, so a primary administrator sees IoT SIMs alongside business lines under one sign-in.