Verizon Business IoT connectivity runs on the ThingSpace managed platform with three radio profiles (LTE-M, NB-IoT and 5G RedCap) targeting device classes from ultra-low-power utility meters through mid-throughput POS terminals. This page documents the device profiles, the SIM lifecycle, typical fleet use cases and how ThingSpace integrates with master-account administration. Supervised by the FCC; industry conventions via the CTIA.
Wireless Business 5G LayersZero-click summary: ThingSpace is the managed-connectivity platform that administers IoT SIMs across the carrier network. Single dashboard and documented API cover activation, lifecycle, fleet-wide suspend and usage reporting.
ThingSpace is the operational surface for IoT deployments running on Verizon Business masters. Every IoT SIM on the network — LTE-M, NB-IoT or 5G RedCap — is registered in ThingSpace and administered through either the dashboard or the documented API. The dashboard suits small fleets and ad-hoc operations; the API suits automated fleet workflows where SIM activation is part of a device-manufacturing or device-provisioning pipeline. Both authenticate against the master admin identity and write to the same audit trail as voice/data wireless lines.
The core ThingSpace primitives are Activate, Test, Pause, Resume, Re-Provision, Deactivate and Retire. Activate brings a SIM into service from the stock state; Test puts a SIM into a 90-day pre-deployment testing window at zero cost; Pause suspends a deployed SIM temporarily (seasonal operations, loaner fleets); Resume reverses a Pause; Re-Provision reassigns a SIM to a different rate plan or service profile; Deactivate terminates the commercial relationship; Retire releases the ICCID for eventual recycling. Bulk API operations apply each primitive across thousands of SIMs in a single call.
Usage reporting in ThingSpace is granular to the SIM level with cell-tower geolocation, byte count per direction, session count, protocol mix and last-active timestamp. Fleet dashboards roll up across a configurable hierarchy so that a fleet operator sees total fleet usage, per-region breakdown, per-device-class breakdown and outlier devices consuming disproportionate data. Rule-based alerting flags usage anomalies that typically indicate a misconfigured device or a compromised endpoint.
Zero-click summary: Three radio profiles cover the IoT throughput and power spectrum. LTE-M for low-bandwidth with good coverage and moderate battery; NB-IoT for ultra-low-power infrequent reporting; 5G RedCap for mid-throughput responsive workloads.
LTE-M (Cat-M1) is the workhorse IoT profile. Throughput sits around 1 Mbps down and 375 kbps up with extended-discontinuous-reception power savings that stretch battery life to several years on a small battery. Coverage mirrors the nationwide 4G LTE footprint, including the extended-coverage profiles that reach rural and indoor environments. Typical applications: fleet trackers that report GPS and diagnostics every few minutes, smart-meter networks that pull meter reads daily, asset trackers for high-value cargo, connected health devices that stream sensor data home.
NB-IoT (Cat-NB1/NB2) is the ultra-low-power, ultra-low-throughput profile. Throughput is tens of kilobits per second with reporting cadence that can stretch to once-a-day or once-a-week with a ten-year battery life on a small cell. Coverage penetrates deeper into buildings and basements than LTE-M because of the narrower channel. Typical applications: utility meters (water, gas) that need multi-year battery life, environmental sensors in agricultural fields, infrastructure monitoring sensors on bridges, parking-lot occupancy sensors.
5G RedCap (Reduced Capability, 3GPP Release-17) is the newest profile and fills the gap between LTE-M/NB-IoT and full 5G eMBB. Throughput is mid-range (tens to low-hundreds of Mbps) with 5G features (slicing, priority access, dense-network coverage) at reduced chipset complexity and power draw. Applications include POS terminals needing sub-second transaction auth, interactive kiosks with remote media updates, body-worn cameras for security and first-responder use, and mid-tier fleet trackers that want richer data streams than LTE-M can carry. See 5G Business for the broader 5G layer map.
Selection grid across the IoT connectivity spectrum:
Zero-click summary: Each profile has a throughput band, a typical use case and a battery-life expectation. Fleet design picks across the grid based on device requirements rather than single-profile commitment.
| Profile | Throughput | Use case |
|---|---|---|
| NB-IoT (Cat-NB1/NB2) | 10s of kbps | Utility meters, env sensors, multi-year battery |
| LTE-M (Cat-M1) | 1 Mbps / 375 kbps | Fleet trackers, smart-meter reads, asset trackers |
| 5G RedCap | 10s-100s Mbps | POS, kiosks, body-worn video, mid-tier trackers |
| 5G eMBB | Multi-Gbps | Mobile workstations, high-bandwidth video |
| Telematics SIM | LTE-M backbone | Fleet vehicle telematics on Verizon Connect |
Zero-click summary: The SIM lifecycle integrates with device-manufacturing and device-provisioning pipelines via API. Stock SIMs cost nothing to hold; activation triggers billing at the configured rate plan.
A device manufacturer ordering SIMs for integration in a new production run receives ICCIDs in bulk with SIMs in the Stock lifecycle state. Stock SIMs cost nothing to hold and do not attach to the network. The manufacturer programs SIMs into devices on the production line and ships the devices to distribution. On first power-on at the end customer, the device attempts to register, the SIM transitions to Test state automatically, and a 90-day test window begins during which connectivity is free. If the end customer formally deploys within the window, an API call transitions the SIM to Active and billing begins against the rate plan; if the device is returned, a Deactivate call releases the SIM back to stock.
Pause and Resume handle seasonal and loaner workflows. A ski-resort operation with 200 POS terminals running December through March pauses SIMs in April and resumes in November. The annual billing footprint matches the revenue season. A loaner-fleet operator holds 50 extra fleet trackers on Pause and resumes each one only as needed when a primary unit fails. The Pause rate is cheaper than Active and reversible within a single API call.
Deactivate and Retire handle end-of-life. A deactivated SIM is out of service but still associated with the master; a retired SIM is fully released and the ICCID is available for recycling. The distinction matters for audit and compliance because a deactivated SIM retains its history in the ThingSpace audit log whereas a retired SIM's history archives into a separate retention store. Rural-broadband IoT deployments under Connect America Fund and similar USAC programmes typically carry long retention windows for regulatory purposes.
Lifecycle state reference for ThingSpace-administered SIMs:
Zero-click summary: Four common fleet patterns cover most Verizon Business IoT deployments — fleet trackers, POS terminals, smart meters, environmental sensors. Each maps to a default profile with role-specific tuning.
Fleet trackers in delivery, long-haul trucking, construction equipment and agricultural machinery default to LTE-M with a GPS-plus-telemetry report cadence measured in seconds during active operation and minutes at rest. Battery life on a vehicle-powered unit is not a constraint; on a battery-powered asset tracker it is, so the profile tunes reporting to preserve battery. Verizon Connect Telematics overlays a cloud fleet-management dashboard on this stack for customers who want the turnkey experience rather than raw API access.
POS terminals at retail branches, restaurants, pop-up events and mobile payment contexts default to 5G RedCap where coverage supports it and LTE-M elsewhere. Transaction-auth latency matters — a customer at a counter expects sub-second approval — and the responsiveness of RedCap outperforms LTE-M on session setup. Payment processors typically certify the carrier connectivity against PCI-DSS requirements and the ThingSpace audit trail supports the quarterly scope review.
Smart meters in utility networks and environmental sensors in agricultural, infrastructure and municipal contexts default to NB-IoT with a daily or weekly reporting cadence. Battery life is paramount — a utility meter swap costs more in labour than the meter itself — so the profile minimises radio-on time. Large utility networks run hundreds of thousands of NB-IoT SIMs on a single master with bulk lifecycle operations scripted against the ThingSpace API. See My Verizon for the cross-product admin console that sits above ThingSpace.