SGP.22 and SGP.32 are both GSMA remote SIM provisioning specifications, built for different devices. SGP.22 serves consumer eSIMs, where a person scans a QR code or taps through an app and the Local Profile Assistant on the device pulls a profile from an SM-DP+. SGP.32 serves IoT eSIMs, where a server called the eIM tells the device to download, switch or delete a profile, with nobody at the device. Choose by one question: can a person finish the activation?
If yes, SGP.22 is the established route. If the device is a meter, tracker, camera or gateway that nobody will touch again, SGP.32 is the specification designed for it. This guide explains how each works, where the older SGP.02 M2M standard fits, what to check before you buy, and how to run a fleet that holds both. It sits alongside our guides to remote SIM provisioning and eSIM orchestration for global IoT.
Last verified 2 November 2026.
One correction up front. SGP.32 does not merge the consumer and M2M standards into one framework for every device, and it does not replace SGP.22. It adds an IoT-specific management layer on top of the same SM-DP+ that SGP.22 uses. Phones stay on SGP.22; new headless IoT designs target SGP.32.
The GSMA eSIM specifications at a glance
The GSMA publishes the remote provisioning specifications in numbered families. Four numbers matter here:
- SGP.02 is the original machine-to-machine (M2M) specification. It is server driven and relies on an SM-SR (Subscription Manager Secure Routing) to deliver and manage profiles. Industry explainers date it to around 2014.
- SGP.21 and SGP.22 are the consumer architecture and technical specifications. Industry explainers date the consumer model to 2016. The device runs a Local Profile Assistant (LPA) and the user starts the download.
- SGP.31 and SGP.32 are the IoT architecture and technical specifications. SGP.31 defines the architecture and requirements; SGP.32 defines the technical specification that implements it.
- SGP.33 and SGP.24 cover testing and the compliance process for products built to SGP.32.
The dates matter because SGP.32 is still moving. Kigen’s summary of the 2023 release reports the first release, v1.0, in May 2023. The GSMA eSIM specifications page lists v1.2 as dated 27 June 2024 and v1.3 as dated 22 May 2026, with SGP.31 v1.3 carrying the same date. CSL Group’s SGP.32 overview adds that v1.2 introduced an optional fallback mechanism and that v1.3 was published on 28 May 2026. When a vendor says it supports SGP.32, ask which version.
Why IoT outgrew SGP.22 and SGP.02
A physical SIM forces a decision before the device ships. You pick an operator at manufacturing, carry one hardware variant per market, and replace the SIM with a site visit if coverage or commercial terms change. Remote provisioning exists to remove that decision. The two standards the GSMA had for it before SGP.32 each solved half the problem.
SGP.02: capable, but tied to the operator
SGP.02 gives the operator or service provider a central way to push profile changes to a device. The cost is integration. The SM-SR and the SM-DP must be integrated with each other, the SM-SR is fixed at eUICC manufacturing, and moving a device to a new operator can require cooperation from the one it is leaving. Profile management also depends on SMS, which some low-power networks do not carry. In practice that suited large buyers with negotiating power and left smaller IoT builders with little room to switch.
SGP.22: easy to integrate, built for a person
SGP.22 made eSIM simple to adopt: a phone user can add a plan in a minute. It assumes things a headless device lacks. A person decides, a camera or an app captures the activation code, and the LPA talks to the SM-DP+ over HTTPS. Teams that needed IoT scale still used it, by printing QR codes into packaging, writing companion apps that stand in for a human, or shipping a bootstrap profile and sorting out the rest later. These approaches work for pilots. They are fragile at fleet scale because the lifecycle depends on a step that someone must perform for every device.

How SGP.32 works
SGP.32 keeps the profile factory of SGP.22 and changes who gives the orders. The consumer LPA is replaced by two pieces, one in the cloud and one at the device. The eIM can work with any SM-DP+ without a prior agreement between the parties, according to Onomondo’s SGP.32 explainer, which is what lets one enterprise manage profiles from several operators.
The eIM: the remote manager
The eIM (eSIM IoT Remote Manager) is a server-side component. It can trigger profile downloads for a fleet, proxy them, and sign the packages that change profile state. It can download, enable, disable and delete profiles and retrieve profile information. For changes to installed profiles, the eUICC verifies the eIM’s signature before acting, so a command from anyone else is refused.
Who runs the eIM is a commercial choice. An eSIM management provider, a connectivity provider or the enterprise itself can operate one. The eUICC can hold associations with more than one eIM, and a new eIM is added through one that is already associated, with no technical integration between the two. The current eIM must allow the change, and a first eIM that is not configurable can block it. That makes it worth asking any vendor whether its eIM is configurable before you sign. It is the feature that decides whether you can change management provider later.
The IPA: the agent at the device
The IPA (IoT Profile Assistant) carries instructions and profile data between the eIM and the eUICC. It can sit in the device application (IPAd) or inside the eUICC (IPAe). IPAe usually means less development work for the device maker, because the function ships with the secure element; IPAd gives the device more control and suits gateways and routers with a capable processor. The GSMA compliance process assesses the two separately.
The eUICC and the SM-DP+
The eUICC is the secure chip that stores profiles and keys. The SM-DP+ (Subscription Manager Data Preparation+) prepares, protects and delivers profile packages, and it is run by the operator or an authorized subscription management provider. SGP.32 reuses the SM-DP+ from SGP.22, so profiles are still created and protected there.

Download modes and protocols
SGP.32 supports two ways to deliver a profile, and both work without a person at the device and without SMS.
- Direct download. The profile comes straight from the operator’s SM-DP+ server to the device. This suits devices with a full network stack, such as vehicles and cameras.
- Indirect download. The eIM acts as a proxy and relays the profile. This suits devices that cannot or should not reach an SM-DP+ themselves, for example because of a firewall or a constrained link.
The specification does not mandate one eIM-to-IPA protocol. It requires integrity and confidentiality, and suggests HTTP secured with TLS where TCP is available and CoAP secured with DTLS for network-constrained devices, as CSL Group’s SGP.32 overview describes. Onomondo’s SGP.32 explainer adds that SGP.32 has no SMS or TCP/IP dependency. The practical effect for low-power wide-area devices is a lighter exchange than the HTTPS-based consumer flow. How much battery that saves depends on the device and network, so measure it on your hardware instead of relying on a published percentage. For the radio-side trade-offs, see our comparison of NB-IoT, LTE-M and 5G RedCap.
First connectivity
A device must reach the eIM before anything can be managed. Onomondo notes that an IoT eSIM can ship with one or more bootstrapped profiles connected to a chosen network. Treat that initial profile as part of your supplier contract: it decides what the device can do on first boot, and some providers sell out-of-the-box arrangements tied to network configurations that are hard to undo.
SGP.22 vs SGP.32 side by side
| Question | SGP.22 (consumer) | SGP.32 (IoT) |
|---|---|---|
| Who starts a download? | The user or an app on the device | The eIM, on behalf of the enterprise or provider |
| Device-side component | Local Profile Assistant (LPA) | IoT Profile Assistant (IPA), in the device (IPAd) or the eUICC (IPAe) |
| Human at the device? | Assumed: screen, camera or app | Not required |
| Profile source | SM-DP+ | SM-DP+ (reused from SGP.22) |
| Fleet control | Per device, through the user flow | From the eIM, for one device or a whole fleet |
| Typical transport | HTTPS over TCP | HTTP with TLS, or CoAP with DTLS for constrained devices |
| Changing the manager | Not an eIM concept | The eUICC can hold more than one eIM and the manager can be changed if the eIM allows it |
| Typical devices | Phones, tablets, wearables, consumer CPE | Meters, trackers, sensors, gateways, industrial assets, vehicles |
| Ecosystem maturity | Established, with broad device and operator support | Newer, with eUICC, IPA and eIM products still reaching the market |
SGP.02 is not in the table. Like SGP.32 it pushes from a server, but through the SM-SR rather than a portable eIM, it depends on SMS, and SGP.32 is not backward compatible with it. Compare M2M SIMs if you are maintaining an SGP.02 estate.
Strengths and limits
SGP.22 strengths: a mature ecosystem, simple onboarding for products with a screen, and infrastructure many enterprises already integrate with. SGP.22 limits for IoT: no native fleet-level control, a user-centric flow, and a hard path to vendor-neutral multi-carrier operation at scale.
SGP.32 strengths: server-driven provisioning for headless devices, a lighter option for constrained links, a manager you can choose and in principle change, and one orchestrator across operators. SGP.32 limits: it needs SGP.32-capable eUICCs and firmware, it is not backward compatible with SGP.02 hardware, and its ecosystem is still maturing.
Which to choose for your devices
Decide device by device, not company by company. Use these questions in order.
Choose SGP.22 when
- The device has a screen, an app or a person who can finish activation: phones, tablets, wearables with displays, consumer routers.
- The product is sold to individuals, who expect to add a plan themselves.
- Your operator partners currently offer consumer eSIM profiles and not IoT management.
Choose SGP.32 when
- The device is headless and will be installed once and left alone: meters, sensors, trackers, gateways, industrial equipment.
- A site visit to change connectivity is too costly or impossible.
- The fleet crosses countries and you want more than one operator behind it.
- You want rules to drive profile changes, for example by location or by network performance.
- You want to keep the option of changing who manages the devices.
The tie-breaker is the lifecycle, not the headcount. Rules of thumb that tie the choice to a device count have no basis in the GSMA documents. A small fleet of buried sensors can justify SGP.32 sooner than a large product line with a screen.

What to check before you commit to SGP.32
- The version. Ask which SGP.31 and SGP.32 version each product was built and tested against, given v1.2 and v1.3 are both listed.
- The compliance status. A specification is not itself certified. Products follow the SGP.24 process against SGP.33 test specifications, and the eUICC, IPA and eIM are separate product types. A vendor claiming alignment is not claiming a compliance confirmation, so ask which one it holds.
- The IPA location. IPAe or IPAd changes who writes and certifies the code. Decide it with your module and chip suppliers.
- The eIM terms. Is it configurable? Can a second eIM be added? Who holds the keys and the data if you leave?
- The operator side. Confirm that each operator you want will deliver profiles through its SM-DP+ to an eIM-managed device, and on what commercial terms.
- Existing devices. A deployed device supports SGP.32 only if its eUICC and software already implement the required IPA functions. Do not assume a firmware update will add it.
- Interoperability. Components certified separately can still behave unexpectedly together, so test the exact combination you will ship.
Running SGP.22 and SGP.32 devices together
Most companies that sell both consumer and IoT products end up with both standards. A mixed estate needs three decisions.
- Keep an inventory by standard. Record, per device model, whether it is SGP.02, SGP.22 or SGP.32, which eIM or LPA flow manages it, and where the initial profile came from.
- Separate provisioning from operations. The way a profile reaches a device differs by standard. Plans, usage, billing and support do not need to. A single view above both avoids running two operations teams. Our guides to single-pane IoT connectivity management and multi-network eSIM aggregation cover that layer.
- Migrate by product line. Keep current SGP.22 or SGP.02 lines running and launch the next hardware revision with an SGP.32 eUICC, instead of trying to convert devices in the field.
Remote provisioning is also not the only route to multi-network service. Some fleets use multi-IMSI SIMs, and our multi-IMSI versus eUICC guide explains when each fits. For physical form factors and SIM options, see the IoT SIM cards guide, and for a broader introduction to eSIM, what an eSIM is.
Who gains from SGP.32
- Device makers can ship one hardware variant, leave the operator choice until deployment, and cut the SKUs and field replacements that a single-carrier SIM creates. IPAe can reduce the code they own.
- Operators and MVNOs can serve IoT customers through the SM-DP+ they already run for consumer eSIM, adding eIM integration instead of a separate platform. Our guide to implementing eSIM at an MVNO covers the operator side.
- Enterprises and service providers can change profiles over the air, move traffic between operators for coverage or cost, and avoid depending on one network. The risks of staying with one carrier are laid out in single-carrier IoT risks.
Where Spenza fits
A standard decides how a profile reaches a device. It does not decide which plan, which operator, what it costs or who gets the invoice. Spenza is an operator-neutral connectivity management platform for device makers, managed service providers and enterprise IoT teams, covering multi-carrier SIMs and eSIM, billing and customer-facing portals. It works at that operational layer, above whichever provisioning standard a device uses. If you are comparing platforms for it, see our overview of IoT connectivity management platforms. Ask any vendor, including us, for the specific SGP.32 components it supports today and the version they were tested to, instead of accepting a general statement about standards support.
Conclusion
SGP.22 and SGP.32 are not rivals for the same job. SGP.22 puts the decision with a person at the device, which is right for phones and wearables. SGP.32 moves it to an eIM and an IPA so a fleet of headless devices can be provisioned and re-pointed without a visit, using the same SM-DP+ that SGP.22 relies on. SGP.02 estates keep running but do not carry over to SGP.32.
Before you commit, settle four things: which version your suppliers built to, whether your eIM is configurable, which operators will deliver profiles to it, and how plans and billing will run above the standard. Those answers matter more than the acronym on the datasheet.
FAQs
What is the difference between SGP.22 and SGP.32?
SGP.22 is the GSMA specification for consumer eSIMs: a person on the device, usually through a Local Profile Assistant, asks an SM-DP+ for a profile. SGP.32 is the specification for IoT eSIMs: a remote server, the eIM, tells an IoT Profile Assistant to download, enable, disable or delete profiles, with no person at the device. Both draw profiles from an SM-DP+.
Does SGP.32 replace SGP.22?
No. SGP.32 is aimed at new IoT designs, and consumer devices such as phones continue on SGP.22. SGP.32 reuses the SM-DP+ that SGP.22 defines, so the two share the profile delivery side while differing in who triggers the download and how.
What are the eIM and the IPA in SGP.32?
The eIM (eSIM IoT Remote Manager) is the server-side component that triggers profile downloads and signs commands that change profile state. The IPA (IoT Profile Assistant) is the device-side component that passes instructions and profile data between the eIM and the eUICC. It can run in the device (IPAd) or inside the eUICC (IPAe).
Is SGP.32 backward compatible with SGP.02 devices?
No. Industry explainers state that eSIM IoT under SGP.32 is not backward compatible with eSIM M2M under SGP.02. Existing SGP.02 estates keep running, and a deployed device only works with SGP.32 if its eUICC and software already implement the required IPA functions.
Which SGP.32 version is current in 2026?
According to the GSMA specifications page, SGP.32 v1.3 is dated 22 May 2026, with SGP.31 v1.3 on the same date. Version 1.2, dated 27 June 2024, is also listed as active. Check which version your eUICC, IPA and eIM vendors built and tested against before you commit.
Can I run SGP.22 and SGP.32 devices in one fleet?
Yes, but they are managed through different mechanisms: user or app-driven flows for SGP.22 devices and eIM-driven flows for SGP.32 devices. Many teams keep a single place for plans, profiles and billing above both. Plan the device inventory by standard before you plan the platform.
Does SGP.32 remove carrier lock-in?
It removes the structural lock-in of SGP.02, where the SM-SR ties a device to its first operator. It does not remove commercial lock-in by itself. You still need an eIM you can change, profiles from more than one operator, and contracts that let you move.
When should an IoT project still use SGP.22?
When the device has a screen, an app or a person who can finish activation, as consumer products do, or when you must work with an operator who offers only consumer eSIM profiles today. For headless devices that nobody can reach after installation, SGP.32 is the specification built for the job.



