eUICC.co.ukIndependent eUICC, eSIM, SGP.32 and IoT deployment guidance

SGP.32 Explained

SGP.32 is the GSMA remote SIM provisioning standard designed specifically for IoT devices, where smartphone-style eSIM activation does not fit the deployment model.

Quick answer: SGP.32 introduces an IoT-focused provisioning model with the eSIM IoT Remote Manager, usually shortened to eIM. The important shift is that profile management can be controlled remotely at scale without relying on the device user to scan a QR code or operate a local app.

Why SGP.32 exists

Earlier eSIM approaches were built around consumer and machine-to-machine assumptions that do not fit every IoT estate. Consumer eSIM works well when a human owns the device and can authorise or install a profile. Classic M2M eSIM works for some controlled deployments, but it can be heavy, contractual and awkward when organisations want more flexible control across device types and providers.

SGP.32 was created to deal with that gap. It recognises that IoT devices may be constrained, unattended, battery-powered, remote, or deployed in large numbers.

The role of the eIM

The eIM is the control layer that manages the relationship between the eUICC, the device side provisioning components and the remote profile infrastructure. In plain English: it is the orchestration layer that decides what should happen to profiles and helps make it happen securely.

Practical interpretation

For businesses, the eIM is where SGP.32 becomes interesting. It points towards a world where SIM profile control is less tied to one operator portal and more connected to a broader device-management workflow.

What changes for IoT deployments

  • Profile changes can be designed around estate management rather than individual device users.
  • Switching logic can be connected to coverage, commercial or resilience policies.
  • Integrator and enterprise platforms can potentially sit above individual networks.
  • The SIM becomes part of a managed control plane rather than a static component.

Where SGP.32 does not solve everything

SGP.32 is not a substitute for a good router, a good antenna, a resilient management path or clear operational ownership. If the device cannot get online at all, remote provisioning is still constrained by the same physical reality as any other cellular service.

SGP.32 and existing deployments

Many current industrial eSIM router deployments still use SGP.22-style mechanisms combined with vendor cloud platforms. That can deliver useful operational functionality today. SGP.32 should be viewed as the direction of travel for IoT eSIM control, not as a switch that makes every existing deployment obsolete overnight.

SGP.22 vs SGP.32eSIM platformsStandards wiki