What Does GSMA SGP.32 eSIM Mean?
GSMA SGP.32 eSIM refers to the remote SIM provisioning (RSP) technical specification published by the GSMA that defines how eSIM profiles are managed on Internet of Things (IoT) devices operating with limited network connectivity, restricted power, or no user interface. The specification reuses much of the architecture used in consumer eSIM provisioning but introduces a new server component, allowing a platform called the eSIM IoT remote manager, or eIM, to remotely initiate a profile download, delete, enable, or disable profiles without requiring the end user to trigger the change. This enables zero-touch provisioning of remote devices.
A device is SGP.32 compliant when its eUICC (embedded universal integrated circuit card) and onboard software support remote profile management through the eIM and an on-device component often called the IoT Profile Assistant (IPA), enabling profile changes to be pushed and executed without a person physically present at the device or manually approving each step.
If a device relies solely on the older M2M standard, SGP.02, or the consumer standard, SGP.22, it lacks the specific architecture SGP.32 defines for constrained, unattended IoT operation, even though it may still support remote provisioning in a more limited form.
Why GSMA SGP.32 eSIM Matters
SGP.32 exists because logistical complexity previously prevented widespread eSIM adoption across IoT applications, and legacy standards were too costly and cumbersome to support large fleets of low-power, low-touch devices. The SGP.32 technical specification matters commercially because it changes how device manufacturers build and ship hardware. Rather than building separate SKUs for different markets or carriers, OEMs can build a single device with one SIM and personalize it later, reducing the number of hardware variants and stock-keeping units they need to manage. This has direct implications for asset trackers, industrial sensors, smart meters, connected vehicles, and any device deployed at scale in locations where physical SIM swaps would be impractical or costly.
How GSMA SGP.32 eSIM Works
SGP.32 combines elements of both the M2M and consumer eSIM specifications into a standard built specifically for IoT, relying on two core elements: An eUICC embedded directly into the device, and the ability to switch profiles between network providers remotely and at scale. This "en masse" profile switching capability is the primary innovation the standard introduces over its predecessors.
The architecture depends on several defined roles and components working together:
- eUICC: The embedded secure element on the device that stores and executes SIM profiles, present regardless of form factor.
- eIM (eSIM IoT Remote Manager): A network-based platform that enables remote device management at scale, replacing the need for manual, on-device profile changes.
- IPA (IoT Profile Assistant): An on-device software component that works alongside the eIM to support remote provisioning actions.
- SM-DP+ (Subscription Manager, Data Preparation): The server role, inherited from the consumer eSIM architecture, responsible for preparing and securing profile packages before delivery.
By using lightweight profile templates and offloading processing to the network-based eIM, the standard minimizes on-device resource consumption, which extends battery life and supports devices with limited memory or processing power.
GSMA SGP.32 eSIM vs. Prior eSIM Standards (SGP.02 and SGP.22)
SGP.32 did not emerge in isolation. It was built specifically to resolve limitations in the two eSIM standards that came before it:
- SGP.02 (M2M eSIM): The foundational remote SIM provisioning specification, released between 2014 and 2015 for machine-to-machine use cases such as automotive remote network management, using a server-driven push model dependent on SMS. This approach proved complex and heavily dependent on SMS or TCP/IP connectivity, making it unsuitable for devices with limited power or no SMS capability.
- SGP.22 (Consumer eSIM): Introduced later to support devices with a user interface, allowing individuals to manage SIM profiles directly on smartphones, tablets, and wearables. This model requires user interaction, which is impractical for IoT devices that are unattended, embedded in remote locations, or lack any screen or input method.
- SGP.32 (IoT eSIM): Developed to bridge this gap by combining the strengths of both prior models while adding capabilities tailored specifically to IoT, removing the dependency on user interaction and the inefficiencies of the older SMS-driven push model.
A common misconception is that SGP.32 simply replaces SGP.22. In practice, the two specifications are designed to coexist. SGP.32 is built to integrate with SGP.22, the consumer eSIM specification, and SGP.31, which defines the broader IoT eSIM architecture and requirements that SGP.32 implements.
Related GSMA Specifications
SGP.32 is part of a broader family of GSMA eSIM IoT documentation, including SGP.31, which defines the eSIM IoT architecture and requirements. Related specifications also cover test procedures, security evaluation, and compliance, including SGP.33 for eSIM IoT test specifications and SGP.29 for EID definition and assignment. Because these specifications are periodically revised and reissued in new versions, organizations implementing SGP.32 should confirm they are referencing the current published version directly through the GSMA rather than relying on a fixed version number indefinitely.
Quick-Answer Summary
GSMA SGP.32 eSIM is a remote SIM provisioning specification published by the GSMA for IoT devices with constrained networks, power, or no user interface. It allows a network-based platform called the eIM to remotely download, enable, disable, or delete eSIM profiles at scale, without requiring physical SIM access or user interaction, resolving limitations found in the earlier SGP.02 (M2M) and SGP.22 (consumer) eSIM standards.
Frequently Asked Questions About GSMA SGP.32
When was GSMA SGP.32 released?
GSMA published SGP.32 v1.0 on May 26, 2023, with subsequent updates including v1.1 in 2024 and later revisions refining the specification through 2026. Commercially certified devices did not become widely available immediately, since certified devices were only expected to be commercially available at the earliest by the end of 2025, as the ecosystem needed time to complete related test specifications and compliance programs.
Is GSMA SGP.32 backward compatible with SGP.22?
Yes. SGP.32 is designed to integrate with SGP.22 rather than replace it outright, reusing much of the consumer eSIM architecture while adding the eIM and IPA components needed for unattended IoT operation. Because certified SGP.32 hardware is still scaling, many eSIM-capable IoT devices sold today continue to rely on SGP.22 in the interim.
What devices currently use GSMA SGP.32?
SGP.32 targets constrained, unattended device categories such as smart meters, asset trackers, industrial sensors, connected vehicles, and fleet management hardware. Legacy M2M devices, particularly in automotive and early-generation smart electricity meters, still commonly run on the older SGP.02 standard, and GSMA recommends new devices migrate to SGP.32 as certified hardware becomes available.
Does GSMA SGP.32 require a SIM card slot in the device?
No. SGP.32 relies on an eUICC, an embedded secure element built directly into the device, rather than a removable physical SIM card. This is part of why the standard supports zero-touch deployment models, since there is no physical card to insert, remove, or replace in the field.
How does an eIM decide which network profile a device should use?
The eIM functions as the decision-making platform in the SGP.32 architecture, determining which carrier profile a device should use and when. When a profile change is needed, the eIM requests a profile server, typically an SM-DP+, to prepare the new operator profile, then instructs the device's IPA to securely fetch, install, and enable it on the eUICC.
Can a device switch mobile network operators without physical access under SGP.32?
Yes. This is one of the standard core capabilities. Because the eIM can remotely trigger profile downloads, deletions, and activations, switching network providers no longer requires physical access to the device or manual intervention, making it possible to manage carrier changes across large, geographically distributed device fleets from a central platform.
Is GSMA SGP.32 adoption growing?
Industry forecasts point to significant growth, though from a small current base. Analysts have projected SGP.32 profile downloads to scale from under 3 million in 2025 to well over 100 million within a few years, with some estimates suggesting SGP.32 could represent a majority share of all IoT eSIM activity by the end of the decade. Adoption has been gradual, since certified silicon, eIM platforms, and IPA implementations needed time to mature before broader commercial rollout could occur.
Who certifies a device as GSMA SGP.32 compliant?
Compliance is managed through the GSMA's own certification and security assurance programs. Vendors can pursue GSMA eSIM Compliance certification for functional interoperability, along with adjacent security schemes such as eSA (eUICC Security Assurance) and SAS-SM (Security Accreditation Scheme for Subscription Management), which address hardware and site-level security separately from functional compliance.
Continue Reading About GSMA SGP.32 eSIM