SGP.22
The consumer eSIM specification: the user starts a profile download with a QR code or an app.
Definitions only — a term explained here is not a service we sell.
SGP.22 standardizes consumer eSIM provisioning. The user pulls a profile with a QR code or an app, and the device installs it after confirmation, so the flow assumes a screen and a human in the loop.
Unattended IoT fleets use SGP.32 instead. SGP.22 covers the download, installation, enabling and deletion of a profile, not the commercial plan behind it.
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 and scans the QR code; the device downloads and enables it. In SGP.32, an eIM selects the profile and the device downloads it with no person present.
Roles and limits
The SM-DP+ prepares the profile and the discovery service tells the device where to fetch it. Check the profile limit, deletion behavior and lock policy, and test a re-download after a reset. The SGP.22 vs SGP.32 comparison covers the IoT alternative.