2SkyMobile

IoT Global SIM Guide: Choosing Connectivity for Deployments

2T

2SkyMobile Team

Sep 10, 2026

IoT Global SIM Guide: Choosing Connectivity for Deployments

How to choose IoT SIM connectivity: LTE-M vs NB-IoT vs 5G, eSIM vs physical SIM, Multi-IMSI coverage, data sizing and management platform requirements for global deployments.

Choosing the wrong SIM connectivity for an IoT deployment is an expensive mistake. Unlike consumer mobile, IoT devices are deployed at scale, often in inaccessible locations, with multi-year operational lifespans. A connectivity decision made at the prototype stage locks in cost structure, coverage limitations, and management complexity for the entire deployment lifecycle. Getting it right requires understanding five variables: network type, SIM form factor, coverage architecture, data consumption model, and management platform.

This guide covers each variable in depth and gives you a decision framework for selecting IoT SIM connectivity that scales — from a small single-country rollout to a large global fleet.


The IoT Connectivity Landscape in 2026

IoT devices use multiple connectivity technologies. Cellular SIM is one of several options, and the right choice depends on your deployment requirements:

Cellular (SIM-based) — LPWA cellular standards (LTE-M, NB-IoT) and standard LTE/5G. Best for: mobile assets, wide-area coverage, devices in locations without fixed infrastructure, applications requiring two-way communication or firmware OTA updates. Range: unlimited (wherever cellular coverage exists). Cost: varies widely with data volume, geography and commercial terms.

WiFi — best for: stationary devices in controlled indoor environments with existing network infrastructure. Not suitable for: mobile assets, outdoor deployments, locations without managed WiFi. Cost: near-zero marginal cost per device once infrastructure exists.

LoRaWAN / Sigfox — ultra-low-power wide-area networks for very low data rate applications. Best for: simple sensor reporting (temperature, humidity, door state) with very long battery life requirements. Not well suited to: applications that need frequent or larger payloads, or regular firmware OTA updates.

Bluetooth Low Energy (BLE) — best for: short-range applications with gateway infrastructure. Common in retail, healthcare, and smart building deployments.

This guide focuses on cellular SIM connectivity — the right choice when you need wide-area coverage, mobile asset tracking, significant data throughput, or remote device management capabilities.


Step 1: Choose the Right Cellular Network Type

The cellular network type determines battery life, data throughput, latency, and device mobility. IoT deployments typically choose between three cellular options:

LTE-M (Cat-M1)

LTE-M is a 4G LTE standard optimized for IoT devices requiring mobility, moderate data rates, and low power consumption. Key specifications:

  • Data rates: around 300 kbps downlink and 380 kbps uplink peak (half-duplex Cat-M1), with typical field averages of roughly 100–150 kbps (GSMA)
  • Latency: around 100–150 ms in normal coverage, higher in extended coverage modes (GSMA)
  • Power consumption: low-power design using power saving mode (PSM) and extended discontinuous reception (eDRX)
  • Battery life: multi-year operation is achievable, depending on reporting frequency, coverage conditions and battery capacity
  • Mobility: Full handover support — device moves between cells without dropping connection
  • Voice: Supports VoLTE (Voice over LTE)
  • Coverage: Availability depends on the operator and country — confirm LTE-M support in each deployment market

Best use cases for LTE-M: Fleet tracking and telematics (vehicles, trucks, shipping containers), wearables and personal emergency response devices, smart metering with high-frequency reads, industrial asset monitoring with firmware OTA update requirements, point-of-sale terminals in mobile environments.

NB-IoT (Cat-NB1/NB2)

NB-IoT is designed for stationary, low-power, low-data-rate applications where very long battery life is the primary design constraint.

  • Data rates: peak of 26 kbps downlink and 66 kbps uplink (multi-tone) for NB1, dropping to a few kbps in extended coverage (GSMA); later releases (Cat-NB2) raise peak rates
  • Latency: around 1 second in normal coverage, rising to several seconds in extended coverage (GSMA) — not suitable for real-time applications
  • Power consumption: very low idle current when using power saving mode (PSM) and eDRX
  • Battery life: designed for very long battery life with infrequent reporting; actual life depends on traffic profile, coverage and battery capacity
  • Mobility: No connected-mode handover — best suited to stationary or slow-moving devices
  • Coverage: Designed for coverage enhancement, including deep indoor and underground locations

Best use cases for NB-IoT: Smart meters (electricity, gas, water), environmental sensors (weather stations, air quality monitors), smart parking sensors, agricultural soil monitors, building management sensors, waste bin fill-level monitors.

5G for IoT

5G is relevant for IoT deployments requiring high bandwidth or ultra-low latency. Two 5G modes matter for IoT:

5G NR (New Radio) — standard 5G, offering much higher throughput and lower latency than LTE-based IoT technologies. Relevant for: industrial automation with real-time control loops, HD video surveillance, connected vehicles requiring V2X (vehicle-to-everything) communication.

RedCap (Reduced Capability 5G) — a reduced-capability NR device category introduced in 3GPP Release 17 for mid-tier IoT, offering a middle ground between LTE-M/NB-IoT and full 5G NR in throughput, device complexity and power consumption. Availability depends on operator 5G rollouts and module support in each market.

Decision rule: Use LTE-M for mobile or data-intensive IoT. Use NB-IoT for stationary low-power sensors. Use 5G NR only if your application genuinely requires throughput or latency beyond what LTE-M can deliver — otherwise the device cost and power premium is not justified.


Step 2: Select the Right SIM Form Factor

IoT deployments choose between removable, soldered and embedded SIM options. The choice depends on the physical deployment environment and management requirements:

Standard / Nano SIM (Removable)

The consumer SIM form factors (2FF Standard, 3FF Micro, 4FF Nano) are appropriate for IoT devices where the SIM may need to be physically swapped — for example, devices that change owners or markets between deployments. Not recommended for harsh environments due to connector reliability issues over repeated insertions and vibration sensitivity.

Use when: Device is in a controlled indoor environment. SIM may need physical replacement. Cost is a primary constraint (removable SIMs are typically the lowest-cost option per unit).

MFF2 (Machine Form Factor 2) — Soldered

MFF2 is an industrial SIM permanently soldered to the PCB. It is the common choice for deployments with environmental stress requirements: industrial-grade MFF2 parts are typically specified for wider temperature ranges and better resistance to vibration, shock and humidity than a removable SIM in a slot. Exact ratings vary by manufacturer and grade — check the datasheet of the specific part.

MFF2 is strongly recommended for: automotive and transportation (engine bay, exterior mounting), industrial machinery, outdoor infrastructure, marine deployments, and any application where SIM slot reliability over a multi-year lifespan is critical.

Important: MFF2 is a form factor, not a SIM type. MFF2 chips can contain standard SIM OS, multi-IMSI SIM OS, or eSIM/eUICC — the form factor and the connectivity architecture are independent choices.

eSIM / eUICC (Embedded SIM with Remote Provisioning)

eSIM combines the physical permanence of MFF2 with the ability to change carrier profiles over the air. The eSIM chip is permanently soldered (available in both consumer and MFF2 form factors), but the carrier relationship is software-defined and remotely manageable.

For IoT specifically, eSIM follows the GSMA SGP.02 (M2M) architecture or the newer GSMA SGP.32 eSIM IoT Technical Specification. These standards define a machine-to-machine remote provisioning protocol — no QR code scanning or user interaction required. Profiles are delivered remotely — via SM-DP and SM-SR under SGP.02, or via SM-DP+ orchestrated by an eSIM IoT Remote Manager (eIM) under SGP.32.

eSIM is the right choice when:

  • Deploying across multiple countries (one SKU, local carrier activation on arrival)
  • Devices will be in the field for many years (carrier relationships need to evolve)
  • Remote carrier switching is needed without device access
  • Deployment scale justifies platform management overhead (typically 500+ devices)

Step 3: Determine Your Coverage Architecture

Coverage architecture — single-carrier vs Multi-IMSI — is the most commercially significant decision for global IoT deployments.

Single-Carrier Coverage

A single-carrier IoT SIM is tied to one carrier's network and roams internationally through that carrier's bilateral agreements. This is the simplest setup and appropriate for:

  • Single-country deployments
  • Deployments where all devices are in one region covered by one strong carrier
  • Small-scale deployments where management simplicity outweighs cost optimization

Single-carrier limitations at scale: Roaming rates in countries not covered by strong bilateral agreements can be significantly higher than local wholesale rates. Coverage gaps where the carrier's roaming partner has limited infrastructure. No automatic failover if the primary carrier has an outage. No ability to optimize cost as carrier rates change over a multi-year deployment.

Multi-IMSI Coverage

Multi-IMSI stores multiple carrier IMSIs on the SIM or eSIM, covering different regions. The steering logic automatically selects the best carrier profile for each location based on coverage, latency, and cost rules. For a deeper explanation, see What is Multi-IMSI.

For global IoT deployments, Multi-IMSI is typically chosen because it delivers:

Cost predictability at scale. Using local or preferred-partner IMSIs in key markets reduces reliance on permanent roaming and its higher rates. At fleet scale, even a small per-MB difference compounds across every device and every month, so model each architecture with your own traffic profile and quoted rates.

Coverage completeness. In markets where your primary carrier's roaming partner has limited coverage, Multi-IMSI provides a secondary carrier option. This matters most in markets where roaming coverage is inconsistent.

Operational resilience. When a carrier has an outage or maintenance window, Multi-IMSI devices automatically switch to the next available carrier profile. Single-carrier deployments without a fallback can go offline until the carrier resolves the issue.

Carrier relationship flexibility. As your deployment scales, you negotiate better rates with carriers. With eSIM remote provisioning, or a multi-IMSI applet that supports OTA updates, new carrier profiles can be added to deployed devices remotely as new agreements are signed — without physical access.


Step 4: Calculate Your Data Requirements

IoT data consumption varies by several orders of magnitude depending on the application. Miscalculating leads to either overprovisioning (paying for unused data) or underprovisioning (hitting caps mid-month and paying overage rates).

Data Consumption by Use Case

The ranges below are illustrative planning estimates, not benchmarks — actual consumption depends on payload design, protocol and reporting frequency, so validate them in a pilot.

ApplicationTypical Data/Device/MonthNotes
Simple sensor (temp, humidity)1–5 MBReporting every 15 min, small payload
Asset tracking (1 update/hour)5–15 MBGPS coordinates + status
Asset tracking (1 update/minute)20–50 MBHigh-frequency fleet tracking
Smart meter2–10 MBDaily reads + billing data
Industrial monitor (vibration, pressure)10–50 MBMulti-sensor, frequent sampling
Remote camera (JPEG snapshot/hour)200–800 MBImage upload at moderate resolution
Video surveillance (continuous HD)Very high; depends on bitrateContinuous streaming is usually better served by fixed or unmetered links
Firmware OTA update10–500 MBOne-time, depends on firmware size

Calculating Total Deployment Data

Start with your base consumption figure, then apply planning allowances such as the examples below (adjust them to your protocol stack and coverage conditions):

  • Protocol overhead: Add 15–20% for cellular protocol headers, TCP/IP overhead, and TLS encryption
  • Retransmission allowance: Add 10% for packet loss retransmissions in areas with marginal coverage
  • OTA updates: Calculate separately — a 50MB firmware update for 10,000 devices = 500GB of additional data during the update window
  • Diagnostic telemetry: Add 5% if your platform sends device health data

Round up to the nearest plan tier and add a 25% buffer. IoT data consumption tends to increase over deployment lifetime as new features are added and reporting frequency increases.


Step 5: Evaluate the Management Platform

The SIM hardware and carrier connectivity are necessary but not sufficient. The management platform — the software layer above the SIM — determines your operational efficiency at scale.

Core Platform Requirements

Real-time usage dashboard. You need per-device visibility into data consumption, carrier in use, signal strength, and last-seen timestamp. Batch reporting (monthly CSV exports) is operationally inadequate for large fleets. Issues surface weeks after they occur and are much more expensive to resolve.

Automated alerts. The platform must alert you when a device exceeds a usage threshold (potential malfunction or SIM cloning), when a device goes offline for longer than expected, or when carrier switching occurs at unusual frequency (potential coverage issue in a deployment location).

Bulk operations API. Managing thousands of devices manually is impractical. The platform must support API-driven bulk operations: suspend/resume groups of SIMs, change plan tier for a device group, force carrier selection for all devices in a region, push new IMSI profiles to a subset of your fleet.

Webhook and event streaming. Real-time event notifications (device online/offline, carrier switch, usage threshold exceeded) enable integration with your device management platform, alerting systems, and business logic. Polling-based integrations have unacceptable latency for operational IoT management.

Integration with IoT platforms. Check how the SIM management platform integrates with the device management system you use — cloud IoT services or industry-specific platforms — whether through native connectors, webhooks or event streams, and what you would need to build yourself.

Cost Management Features

Usage-based billing. Fixed monthly plan billing is appropriate for predictable, uniform devices. For mixed fleets with variable consumption, usage-based billing (per MB or per KB) prevents overprovisioning costs.

Automatic suspension rules. Configure rules to automatically suspend SIMs that exceed consumption thresholds. This prevents runaway costs from malfunctioning devices consuming gigabytes of data and eliminates the need for manual monitoring of individual device consumption.

Rate ceilings. For Multi-IMSI deployments, the platform should enforce maximum per-GB rate rules — automatically routing away from any carrier that exceeds your configured rate ceiling, regardless of coverage.


Global IoT Connectivity: Choosing a Provider

Evaluating wholesale IoT SIM providers requires assessing five dimensions:

Coverage

Ask for coverage documentation by country with specific carrier names and network generations (2G/3G/4G/5G). A headline country count is a marketing claim — verify it. Request a test SIM and run speed tests in your deployment locations before committing to a production contract.

For global deployments, look for at least two carrier options in each of your priority markets. A roaming product that technically covers many countries but relies on legacy 2G/3G networks in a significant share of them — networks that are being shut down in many markets — is not a viable global product.

Platform Maturity

Request API documentation before signing a contract. A mature IoT platform has: a public API reference (OpenAPI spec), a sandbox environment for integration testing, documented webhook schemas, and client libraries for at least Python and Node.js. If the provider's API documentation is a PDF sent by email, their platform is not production-ready.

SLA and Support

IoT deployments are operational infrastructure. The connectivity SLA must include: a contractually defined uptime commitment, incident response time targets by severity level, and compensation mechanisms for outages. Ask specifically about the support model for production incidents outside business hours — 24/7 support is non-negotiable for mission-critical deployments.

Commercial Terms

IoT connectivity pricing varies significantly between providers. Key commercial factors: minimum monthly commitment (can be waived for pilot programs), overage pricing (what happens when a device exceeds its plan), data rollover policy (do unused MB carry over?), and contract length (longer contracts can offer better rates but require confidence in the deployment scale). For initial deployments, negotiate a time-limited pilot at slightly higher per-unit costs with the option to lock in volume pricing once deployment scale is confirmed.

Compliance and Certification

For regulated IoT applications (healthcare, automotive, financial services), ask for evidence relevant to your scope: independent security attestations, ISO/IEC 27001 (information security management) and, for eSIM subscription management, GSMA SAS-SM accreditation of the provisioning sites. For devices deployed in the EU, GDPR compliance documentation including data processing agreements is required. For automotive applications, OEMs commonly require AEC-Q100-qualified SIM hardware.


Decision Framework: Choosing the Right IoT SIM

Answer these questions to identify the right connectivity architecture. Device-count thresholds below are rules of thumb, not hard limits:

Single country or multi-country deployment? → Single country, < 500 devices: Standard SIM, single carrier, simple management platform → Single country, > 500 devices: eSIM with single carrier, platform management → Multi-country, any scale: eSIM with Multi-IMSI, platform management required

Mobile asset or stationary sensor? → Mobile (vehicle, tracked asset, wearable): LTE-M → Stationary, low data rate, battery-critical: NB-IoT → High bandwidth or ultra-low latency: 5G NR

Deployment environment? → Controlled indoor environment: Standard removable SIM acceptable → Outdoor, vehicle, industrial, or harsh environment: MFF2 form factor required

Deployment lifespan? → < 2 years: Physical SIM with current carrier may be sufficient → > 2 years: eSIM with remote provisioning to future-proof carrier relationships

Device count at full scale? → < 200 devices: Manual management acceptable, standard SIM → 200–2,000 devices: Platform management required, eSIM preferred → > 2,000 devices: Multi-IMSI eSIM with full API management mandatory


Frequently Asked Questions

What is the difference between LTE-M and NB-IoT?

LTE-M and NB-IoT are both low-power wide-area cellular standards designed for IoT, optimized for different use cases. LTE-M offers higher data rates (around 300 kbps downlink and 380 kbps uplink peak, per GSMA), handles device mobility with cell handover and supports voice (VoLTE) — suitable for mobile assets like fleet trackers, wearables, and emergency response devices. NB-IoT has lower peak rates (26 kbps downlink and 66 kbps uplink for NB1, per GSMA), no connected-mode handover (devices should be stationary or slow-moving), is designed for very long battery life with infrequent reporting, and has enhanced indoor and underground coverage penetration — ideal for smart meters, environmental sensors, and building management systems.

Should I use eSIM or physical SIM for my IoT deployment?

For new deployments at scale (500+ devices) in multiple countries, eSIM with Multi-IMSI is almost always the better choice: one SKU for global deployment, remote provisioning and carrier switching without physical access, and GSMA SGP.32 standard for automated device management. Physical SIM remains appropriate for: single-country deployments under 500 devices, legacy hardware without eSIM support, markets where carrier eSIM infrastructure is not yet deployed, and budget-constrained projects where the eSIM platform management overhead is not justified by scale.

How do I calculate data requirements for my IoT deployment?

Start with your reporting frequency and payload size. Simple sensor reporting every 15 minutes with a 50-byte payload: 50 bytes × 4/hour × 24 hours × 30 days = 144,000 bytes = 144KB/month. Asset tracking with 1-minute GPS updates (100 bytes per update): 100 bytes × 60/hour × 24 × 30 = 4.3MB/month. Add example allowances (e.g. 20% for protocol overhead and 10% for retransmissions), and calculate OTA update data separately. Then add a 25% buffer and select the plan tier above your calculated requirement. Always verify your calculations against actual device consumption in a 30-day pilot before committing to a production deployment volume.

What is an MFF2 SIM and when do I need one?

MFF2 (Machine Form Factor 2) is an industrial SIM permanently soldered onto a PCB rather than inserted in a SIM slot. Industrial-grade MFF2 SIMs are typically specified for wider operating temperature ranges and better vibration and humidity resistance than standard SIM cards; exact ratings vary by part, so check the datasheet. You need MFF2 when deploying in automotive or transportation (engine bay temperatures, vibration), industrial machinery (factory floor conditions), outdoor infrastructure (temperature extremes), marine environments, or any application where SIM slot reliability over a multi-year lifespan is critical. MFF2 is compatible with standard SIM OS, Multi-IMSI SIM, and eSIM/eUICC profiles.

How do I manage SIM connectivity for a fleet of thousands of IoT devices?

Enterprise IoT connectivity management requires: a centralized dashboard with per-device connectivity status, data consumption, and carrier information; a REST API for programmatic bulk operations (suspend, resume, change plan, force carrier, push IMSI profiles); automated alerts for unusual consumption patterns and device offline events; usage-based billing to prevent overprovisioning costs; and integration with your existing IoT device management platform via webhooks and event streaming. Confirm each of these capabilities with any provider you evaluate — ideally in a sandbox before signing.


Conclusion

IoT SIM selection is an infrastructure decision with multi-year consequences. The wrong network type wastes battery life or limits data throughput. The wrong form factor fails in the deployment environment. The wrong coverage architecture creates unmanageable cost structures at scale. The wrong management platform leaves your operations team blind to connectivity issues until they become customer-facing problems.

The framework is straightforward: match LTE-M or NB-IoT to your application's mobility and data requirements, use MFF2 form factor for any non-controlled environment, choose eSIM with Multi-IMSI for any deployment exceeding 500 devices or spanning multiple countries, and insist on a management platform with real-time visibility and full API control before signing a production contract.

2SkyMobile provides wholesale mobile data connectivity via API, delivered through licensed third-party operators, with terms agreed per engagement, and develops custom telecom software such as billing platforms, portals and integrations for teams that need their own tooling. Contact 2SkyMobile to discuss your connectivity requirements.

Key facts

mff2
Soldered industrial SIM form factor for harsh environments; ratings vary by part
lte m speed
Around 300 kbps downlink / 380 kbps uplink peak (half-duplex), field averages about 100–150 kbps (GSMA)
nb iot speed
26 kbps downlink / 66 kbps uplink peak for NB1 multi-tone (GSMA)
esim iot spec
GSMA SGP.32 eSIM IoT Technical Specification (eIM, IPA, SM-DP+)
iot standards
["GSMA SGP.02 M2M","GSMA SGP.32 IoT","3GPP LTE-M","3GPP NB-IoT","3GPP NR RedCap (Release 17)"]
lte m latency
Around 100–150 ms in normal coverage (GSMA)
esim threshold
Rule of thumb: 500+ devices or multi-country deployment
nb iot latency
Around 1 second in normal coverage, several seconds in extended coverage (GSMA)
nb iot mobility
No connected-mode handover; for stationary or slow-moving devices
multi imsi benefit
Local or preferred-partner IMSIs reduce reliance on permanent roaming and add carrier redundancy

FAQ

What is the difference between LTE-M and NB-IoT?
LTE-M and NB-IoT are both low-power wide-area cellular standards designed for IoT, optimized for different use cases. LTE-M offers higher data rates (around 300 kbps downlink and 380 kbps uplink peak, per GSMA), handles device mobility with cell handover and supports voice (VoLTE) — suitable for mobile assets like fleet trackers, wearables, and emergency response devices. NB-IoT has lower peak rates (26 kbps downlink and 66 kbps uplink for NB1, per GSMA), no connected-mode handover, is designed for very long battery life with infrequent reporting, and has enhanced indoor and underground coverage — ideal for smart meters, environmental sensors, and building management systems.
Should I use eSIM or physical SIM for my IoT deployment?
For new deployments at scale (500+ devices) in multiple countries, eSIM with Multi-IMSI is almost always the better choice: one SKU for global deployment, remote provisioning and carrier switching without physical access, and GSMA SGP.32 standard for automated device management. Physical SIM remains appropriate for single-country deployments under 500 devices, legacy hardware without eSIM support, markets where carrier eSIM infrastructure is not yet deployed, and budget-constrained projects where the platform management overhead is not justified by scale.
How do I calculate data requirements for my IoT deployment?
Start with your reporting frequency and payload size. Simple sensor reporting every 15 minutes with a 50-byte payload: approximately 144KB/month. Asset tracking with 1-minute GPS updates (100 bytes): approximately 4.3MB/month. Add example allowances (e.g. 20% for protocol overhead and 10% for retransmissions), and calculate OTA update data separately. Then add a 25% buffer and select the plan tier above your calculated requirement. Always verify calculations against actual device consumption in a 30-day pilot before committing to production deployment volume.
What is an MFF2 SIM and when do I need one?
MFF2 (Machine Form Factor 2) is an industrial SIM permanently soldered onto a PCB rather than inserted in a SIM slot. Industrial-grade MFF2 SIMs are typically specified for wider operating temperature ranges and better vibration and humidity resistance than standard SIM cards; exact ratings vary by part, so check the datasheet. You need MFF2 for: automotive and transportation, industrial machinery, outdoor infrastructure, marine environments, or any application where SIM slot reliability over a multi-year lifespan is critical. MFF2 is compatible with standard SIM OS, Multi-IMSI SIM, and eSIM/eUICC profiles.
How do I manage SIM connectivity for a fleet of thousands of IoT devices?
Enterprise IoT connectivity management requires: a centralized dashboard with per-device connectivity status and data consumption; a REST API for programmatic bulk operations (suspend, resume, change plan, force carrier, push IMSI profiles); automated alerts for unusual consumption and device offline events; usage-based billing to prevent overprovisioning; and integration with your IoT device management platform via webhooks and event streaming. Confirm each of these capabilities with any provider you evaluate — ideally in a sandbox before signing.