What is SGP.32?
SGP.32 is the GSMA IoT eUICC specification (Release 3.1+), designed specifically for constrained IoT devices that cannot support the full SGP.02 M2M or SGP.22 consumer eSIM architectures. SGP.32 introduces the IoT Profile Assistant (IPA) — a lightweight agent that runs on the device or on a companion SIM — and the eIM (IoT eUICC Manager) for remote profile management without the device needing to initiate a full TLS session to the SM-DP server.
SGP.32 architecture
SGP.32 replaces the LPA (Local Profile Assistant) used in consumer SGP.22 eSIM with two new components:
- IPA (IoT Profile Assistant): A lightweight agent running on the device (IPA Device) or on a SIM or companion chip (IPA eUICC). Handles profile download and management commands from the eIM.
- eIM (IoT eUICC Manager): The server-side management entity that initiates and coordinates profile operations. Equivalent to SM-SR in SGP.02 but with a simplified, IoT-optimised protocol.
SGP.32 vs SGP.02 vs SGP.22
| SGP.02 (M2M) | SGP.22 (Consumer) | SGP.32 (IoT) | |
|---|---|---|---|
| Target devices | Industrial M2M | Smartphones, wearables | Constrained IoT |
| Profile initiation | Server push (SM-SR) | Device pull (LPA) | Server push via eIM/IPA |
| Device requirements | Full TLS capable | Display + user interaction | Low power, minimal resources |
| NB-IoT/RedCap compatible | Limited | No | Yes (designed for) |
| PSM/eDRX compatible | Limited | No | Yes |
SGP.32 is particularly relevant for NB-IoT and 5G RedCap deployments where devices operate in deep sleep modes (PSM) for extended periods and cannot maintain a persistent connection to an SM-DP server. The eIM can queue profile management operations and deliver them when the device wakes.