SGP.32 is the GSMA specification for IoT eSIM. Unlike SGP.22 (designed for consumer devices with reliable connectivity), SGP.32 is designed for constrained IoT devices that may have intermittent connectivity, low power budgets, and minimal processing capability. It introduces asynchronous profile management and the eIM (eSIM IoT Manager) as the central management entity – making it the natural integration point for platforms like Teltonika RMS.
| Feature | SGP.22 (Consumer) | SGP.32 (IoT) |
|---|---|---|
| Profile management | LPA on device, user-initiated | eIM server-initiated, remote |
| Connectivity assumption | Always-on, reliable | Intermittent, constrained |
| Operation model | Synchronous (device waits for server) | Asynchronous (server queues commands) |
| LPA requirement | Full LPA on device | Lightweight eIM client (IoT LPA) |
| Bootstrap SIM | Not specified | Defined bootstrap profile workflow |
| IoT platform integration | Limited | Native – eIM interfaces with IoT management platforms |
SGP.32 introduces the eIM (eSIM IoT Manager) as the central management entity for IoT eSIM. The eIM manages profile downloads, activations, deletions, and updates across a fleet of SGP.32-compliant devices. It communicates with the SM-DP+ (profile preparation server) and with devices via an IoT-optimised protocol.
The significance for RMS: the eIM is the natural integration point for an IoT device management platform. Teltonika RMS, as the device management platform, can integrate with an eIM to provide unified device and SIM management from a single control plane. Device configuration changes and SIM profile changes become coordinated operations rather than separate workflows.
SGP.32 defines a bootstrap profile workflow – a minimal SIM profile that allows a device to connect to the network sufficiently to receive its operational SIM profile from the SM-DP+, then switch to the operational profile. This is critical for zero-touch deployment: a device ships from the factory with a bootstrap profile, connects to the network, downloads its operational profile from the eIM/SM-DP+, and begins normal operation – all without manual SIM card provisioning. See Bootstrap SIM and RMS for the full workflow.