SGP.32
SGP.32 is the GSMA eSIM specification for IoT fleets: an eIM orders profile downloads and enables or deletes profiles without a person at the device.
Definitions only — a term explained here is not a service we sell.
SGP.32 is the eSIM specification for IoT devices. An eSIM IoT manager (eIM) orders profile downloads and enables or deletes profiles across a fleet, with no person at the device.
The device needs a connection to receive a command, or the command waits until it next attaches. Fallback rules decide what happens when a download fails, and they are the part most often left unspecified.
What replaces the user
SGP.32 keeps the profile preparation and discovery roles of the consumer architecture and moves the trigger to the fleet platform. An IoT profile assistant, in the eUICC or in the module, passes manager commands to the secure element, and enabling a new profile usually disables the old one. The SGP.22 vs SGP.32 comparison sets out both flows.
Profile lifecycle
SGP.22 (consumer)
- 1 Order
- 2 Scan the QR code
- 3 Profile downloads Current step
- 4 Enable on the device
SGP.32 (IoT)
- 1 Order
- 2 eIM selects a profile
- 3 Profile downloads Current step
- 4 No person at the device
Text description
In SGP.22 the user orders a profile, scans a QR code, the device downloads it and the user enables it. In SGP.32 the fleet platform orders a profile, the eIM selects it, the device downloads it, and no person is needed at the device.
What to check
Confirm the module and the eUICC are certified for SGP.32, and that the manager supports the operations you need. Ask who can issue commands, how the manager authenticates, and what audit trail exists.