SGP.32 and eSIM Switching: The Control Layer Explained

What is eSIM Switching?

eSIM switching is the ability to remotely change a device mobile network profile without physically replacing the SIM card. A device running on Vodafone today can be moved to EE tomorrow – without a site visit, without a SIM swap, without any physical intervention at the device location. The change happens over the air, initiated from a management platform, executed on the eUICC chip inside the device.

That is the simple version. The important version is what this makes possible at scale: a fleet of 10,000 industrial sensors, utility meters, or vehicle trackers where the network relationship can be managed, adapted, and optimised from a single dashboard, throughout a device lifetime that may span 15 or 20 years.

Why “eSIM Switching” Is a New Category

The term eSIM switching does not appear prominently in GSMA specification documents. SGP.32 describes remote SIM provisioning, profile lifecycle management, and server-initiated profile control. What it does not describe is the enterprise-facing layer that makes all of this operationally accessible.

That layer is the eSIM switching platform. It is the interface, the dashboard, the policy engine, and the API that sits above the GSMA infrastructure and allows a connectivity manager, an IT director, or an operations engineer to actually control which network their devices use without understanding SM-DP+ endpoints or eIM authentication chains.

eSIM switching is the commercial translation of what SGP.32 enables technically. It is the language the market will use as the standard matures. And it is, right now, a category without a dominant owner.

The Old World vs the New World

Static Connectivity (the old world)

Most IoT devices currently in the field operate on static connectivity. The SIM is provisioned at deployment with a single operator relationship. If coverage deteriorates, if the operator raises prices, if regulations require a local profile, if the operator exits the market – the answer is a site visit. Send someone to the device. Swap the SIM. Leave.

At small scale this is manageable. At 500 devices across 50 sites it is expensive. At 50,000 devices across multiple countries it is operationally untenable.

Dynamic Connectivity (the new world)

Dynamic connectivity means the network relationship is managed in software rather than hardware. The device ships with an eUICC capable of holding multiple profiles. The appropriate profile is loaded remotely. When conditions change, the profile changes. When a better commercial arrangement is available, the profile changes. When regulations require a local operator, the profile changes. No engineer. No van. No downtime.

This is what eSIM switching delivers. SGP.32 is the standard that makes it reliable, interoperable, and scalable. The eSIM switching platform is the interface that makes it accessible.

What an eSIM Switching Platform Does

An eSIM switching platform provides five core capabilities that sit above the GSMA infrastructure:

1. Unified Device Dashboard

A single view of every device in the estate: current network, signal strength, active profile, last switch event, status. Not individual SIM management through separate operator portals – one place where the entire fleet is visible.

2. Remote Profile Switching

The ability to instruct a device or group of devices to switch from one operator profile to another. The platform sends the instruction to the eIM, the eIM pushes to the device, the device downloads and activates the new profile. The administrator sees the status change in real time.

3. Policy Engine

Rules that automate switching decisions without human intervention. If signal strength drops below a threshold, switch to the next available profile. If data cost exceeds a budget, move to a cheaper operator. If a device enters a country where permanent roaming is restricted, automatically activate the local profile. The policy engine is where eSIM switching becomes genuinely autonomous.

4. Provider Abstraction

A catalogue of available operator profiles – UK, European, global – accessible through a single interface rather than through separate operator portals and commercial agreements. The platform handles the relationships so the enterprise manages connectivity as a software decision.

5. API Access

Programmatic control of all switching operations, integrated into existing device management, monitoring, and operational toolchains. A router that detects poor signal quality can trigger a profile switch through the eSIM switching API without human involvement.

How SGP.32 Enables eSIM Switching at Scale

Earlier eSIM standards made switching possible but not practical at IoT scale. SGP.02 required heavy SM-SR infrastructure and created operator lock-in. SGP.22 required a user at the device to initiate profile changes. Neither was designed for fleets of headless, low-power devices in remote locations.

SGP.32 changes three things that matter specifically for eSIM switching:

• Server-initiated management – the eIM pushes profile changes from the server side. No user required at the device.
• CoAP transport – profile operations work over NB-IoT and LTE-M, not just HTTPS. Constrained devices on kilobyte data budgets can receive and execute switching instructions.
• Asynchronous operation – devices in deep sleep receive switching instructions when they next wake. A battery-powered sensor that reports twice a day can still be managed by the eSIM switching platform.

These three capabilities are what make eSIM switching a viable operational model rather than a theoretical one. SGP.32 is the infrastructure. The eSIM switching platform is the interface.

The Switching Stack

The eSIM switching architecture maps cleanly to five layers:

The Commercial Opportunity

The market for eSIM switching platforms does not yet exist as a named category. The underlying infrastructure (SGP.32, eUICC, eIM) is maturing. The hardware is arriving (Robustel/Kigen, Quectel, Thales). The operator relationships are developing (Wireless Logic, Eseye, Tele2 IoT).

What is missing is the enterprise-facing control layer – the platform that takes the complexity of the GSMA architecture and makes it accessible as a business tool. That is the gap that eSIM switching platforms will fill.

The GSMA projects 195 million SGP.32 profile downloads by 2029. Every one of those represents a device that will need switching management over its lifetime. The addressable market for eSIM switching platforms is not theoretical – it is the entire commercial layer above the standard.

For the technical standard that underpins eSIM switching, see What is SGP.32?. For the architecture that makes server-initiated switching possible, see SGP.32 Architecture. For hardware that implements eSIM switching capability, see the eSIM Hardware Guide.