SGP.22 vs SGP.32
SGP.22 and SGP.32 both deal with eSIM remote provisioning, but they were designed around different assumptions about devices, users and control.
The short comparison
| Area | SGP.22 | SGP.32 |
|---|---|---|
| Original fit | Consumer eSIM and devices with local user interaction. | IoT devices and remotely managed estates. |
| Control model | Often relies on Local Profile Assistant behaviour on or near the device. | Introduces IoT-specific remote management using eIM concepts. |
| IoT practicality | Can work when wrapped by router or cloud vendor tooling. | Designed to be a cleaner long-term IoT provisioning model. |
| Current market reality | Common in current router and module implementations. | Emerging as the strategic direction for IoT eSIM management. |
Why SGP.22 is still important
SGP.22 is not dead. In fact, a lot of practical industrial eSIM work still depends on it. Router manufacturers and platform providers can add their own management layer around SGP.22 to make it useful in IoT settings. This is why some current deployments feel more advanced than the underlying consumer-style standard might suggest.
How router vendors bridge the gap
Vendors such as Teltonika and Robustel can use their remote management platforms to deliver functionality that feels closer to the SGP.32 ambition, even where the underlying implementation is not a pure SGP.32 architecture. The platform handles device visibility, profile workflows, fallbacks and operational control.
This is the important nuance: SGP.22 can be made operationally useful for IoT when the router vendor wraps it with a proper device-management platform. SGP.32 aims to standardise more of that IoT-specific control model.
Procurement risk
The dangerous phrase is “supports eSIM”. It is too vague. Procurement teams should ask which standard is supported, how profiles are loaded, who controls the profiles, whether bulk deployment is possible, what happens if a switch fails, and whether the router can still be reached during provisioning problems.
Decision guide
Use SGP.22-aware hardware today
Useful when a router vendor provides solid cloud tooling and the deployment need is immediate.
Plan for SGP.32
Important for long-life products, multi-provider orchestration and stronger future control.
Avoid vague claims
Do not buy on the word eSIM alone. Ask how it is actually provisioned and managed.