SGP.32

SGP.32 is the GSMA technical specification for eSIM in IoT devices. It lets a remote manager — the eIM — download and switch operator profiles on devices that have no screen or user, using the same SM-DP+ infrastructure as consumer eSIM. It implements the architecture and requirements set out in SGP.31.

SGP.32 architecture

Element	Role
eUICC	Stores profiles; verifies and executes signed operations
IPA	Profile assistant in the device (IPAd) or in the eUICC (IPAe)
eIM	Triggers downloads and manages profile state remotely
SM-DP+	Prepares and delivers profiles; reused from SGP.22
SM-DS	Optional discovery of pending downloads

Key interfaces include ESipa (eIM to IPA), ESep (end to end, eIM to eUICC), ES9+ (SM-DP+ to IPA) and ES9+’ (SM-DP+ to eIM). ESipa can run over HTTPS or over CoAP with DTLS, and the specification includes annexes for LwM2M and MQTT.

Versions and adoption

• v1.0.1 was published in May 2023.
• v1.2 followed in 2024; the SGP.33 test specifications published in January 2025 apply to it, enabling certification.
• First certification: Giesecke+Devrient’s IoT eUICC was the first to achieve GSMA compliance and certification for SGP.32, in April 2025.
• Commercial SIMs: operators have started selling SGP.32 SIMs; Telenor IoT, for example, made them orderable in February 2026 with shipments from April 2026.

How SGP.32 differs from SGP.02 and SGP.22

SGP.32 is not backward compatible with the M2M specification SGP.02: there is no SM-SR, and the eIM can be run by the device owner rather than being fixed at manufacture. Compared with SGP.22, it removes the need for user interaction and supports constrained devices on NB-IoT and LTE-M.

Why it matters for testing

SGP.32 adds new moving parts — eIM, IPA, eUICC Packages — on top of the usual network risks. Teams need to verify download, enable, fallback and attach on real eUICCs and live networks before shipping fleets. SimCheck.ai supports SGP.32 profile installation through a cloud eIM on real modems — see SGP.32 IoT eSIM testing.