eSIM Switching for IoT: Dynamic Connectivity in Practice

The Problem with Static Connectivity at Scale

Every IoT deployment eventually hits the same wall. A device installed in 2021 on Vodafone coverage is now in a location where EE is stronger. Or the Vodafone contract is up and O2 is cheaper. Or regulations in the deployment country now restrict permanent roaming. Or the device has moved across a border and needs a local profile.

With a physical SIM, the answer to every one of these scenarios is the same: send someone to the device. Swap the SIM. Leave. At scale, this is not an operational inconvenience – it is a business model problem. The cost of physical SIM management compounds relentlessly across a growing fleet.

eSIM switching eliminates this. Not by making connectivity free or simple in every dimension, but by removing the physical constraint. The network relationship becomes a software decision, not a hardware event.

Industrial Routers – The Clearest Use Case

Industrial routers are where eSIM switching is most immediately practical today, because manufacturers like Teltonika and Robustel have already built the capability into their management platforms, even if the underlying standard is SGP.22 rather than native SGP.32.

A Teltonika RUT241 on a construction site is running on an O2 profile. Coverage is marginal. The installer uses RMS to switch to EE without visiting the site. Ten minutes, one click, no van. This is eSIM switching in its simplest commercial form, and it works today with SGP.22 hardware.

Where the gap shows up is at scale with constrained hardware. A fleet manager with 2,000 routers across 40 sites can use RMS to manage those devices. A utilities company with 200,000 NB-IoT smart meters cannot – the devices are too constrained, the connections too intermittent, and the data budgets too small for HTTPS-based profile management. That is where native SGP.32 with CoAP transport becomes the requirement.

Smart Meters and Utilities

Utility-scale IoT is the use case that most clearly defines why SGP.32 and eSIM switching matter. Meters have 15 to 20 year operational lifetimes. Over that period, the network landscape will change fundamentally – 2G and 3G have already gone, 4G LTE-M and NB-IoT are the current foundation, and 5G RedCap is emerging as the mid-tier industrial standard.

A meter installed in 2026 needs to remain connected and manageable until 2041 or 2046. The operator relationship established at installation may not survive that period. The ability to switch profiles remotely – to move from one operator to another as coverage, commercial terms, or technology generations shift – is not a convenience feature for utility IoT. It is a fundamental operational requirement.

The eSIM switching scenario for utilities looks like this: a metering platform detects that a cohort of 5,000 meters in a geographic area is experiencing degraded NB-IoT signal on one operator. An automated policy rule triggers a batch profile switch to an alternative operator. The meters receive the switching instruction when they next wake from their reporting cycle, activate the new profile, and continue operating normally. No field intervention. No service disruption.

Logistics and Cross-Border Deployments

Permanent roaming restrictions are a growing operational constraint for logistics IoT. Countries including Brazil, Turkey, and others have introduced or are considering regulations that restrict devices from operating permanently on a foreign network profile. A container tracker that ships globally on a single roaming SIM may become non-compliant as it crosses specific borders.

eSIM switching solves this with what the industry calls just-in-time provisioning. A device ships with a global roaming bootstrap profile. As it arrives in a specific country, a location trigger or manual instruction loads a local operator profile appropriate for that market. The device is now on a local network, compliant with roaming regulations, and likely on better commercial terms than permanent roaming would provide.

The practical version of this today uses SGP.22 with management layers from providers like Eseye or Wireless Logic. The SGP.32 version, when the hardware matures, will enable lower-power, more reliable switching specifically for the constrained asset tracking devices that logistics IoT depends on.

CCTV and Security Systems

Security system connectivity has an unusual requirement: it must be available precisely when it is needed most, which is often during infrastructure failures or deliberate network interference. Single-operator physical SIM deployments are a vulnerability. An attacker or failure event that disrupts one operator creates gaps in coverage that a dual-SIM or eSIM setup can mitigate.

eSIM switching for security applications focuses on automated failover – if the primary operator profile fails the connectivity check, the system immediately switches to a backup profile on a different operator. This is not manual intervention. It is a policy rule: signal below threshold triggers profile switch, no human involvement required.

With Teltonika RUT241 or similar hardware running alongside a physical SIM fallback, this is achievable today. With native SGP.32, the failover logic becomes fully software-defined and eIM-managed, removing the dependency on physical SIM hardware for the backup path.

EV Charging Infrastructure

EV charging networks face a version of the permanent roaming problem combined with a dense deployment challenge. Charge points are installed across geographies, often in locations where coverage varies significantly between operators. The optimal network for a charge point in rural Scotland is different from the optimal network for one in central London.

An eSIM switching platform managing an EV charging fleet can automatically assign the optimal local operator profile to each charge point based on installation location, apply failover rules when the primary operator drops below availability thresholds, and update profiles across the entire fleet when commercial terms change – without any site visits to the charge point hardware.

The Policy Layer – Where Switching Becomes Autonomous

Manual eSIM switching – an engineer clicking a button to move a device to a different operator – is valuable. Automated eSIM switching – a platform applying rules to manage connectivity autonomously – is transformative.

A mature eSIM switching platform would implement rules like these across a live fleet:

• Signal failover – if RSRP drops below -110 dBm, switch to next available profile
• Cost optimisation – if monthly data spend exceeds budget threshold, switch to lower-cost operator profile
• Location compliance – if device enters jurisdiction with roaming restrictions, activate local operator profile automatically
• Network sunset – if operator announces technology shutdown, pre-emptively migrate affected devices to replacement profiles

These rules run without human instruction. The platform monitors, detects, and acts. The fleet manager reviews the audit log, not the individual switching events. This is connectivity managed like software infrastructure, not like hardware logistics.

What is Available Today vs What Requires SGP.32

For a full technical explanation of how SGP.32 enables these capabilities, see What is eSIM Switching? and the SGP.32 Architecture Guide. For the bootstrap and first-connection challenge in switching deployments, see eSIM Bootstrap Issues.