Everything worth knowing, nothing that isn't.
Why SGP.32 exists
SGP.02 (the original M2M spec) was built for a world where every device had a dedicated cellular subscription provisioned at the factory. As IoT scaled to billions of devices that move between operators (vehicles, asset trackers, smart meters), the SM-DP/SM-SR architecture became a bottleneck — every profile change required signed file pushes from the operator's SM-SR. SGP.32 splits the SM-DP+ from the eSIM IoT remote SIM provisioning (eIM) and lets devices initiate profile downloads themselves.
Components
Three new entities: the eUICC (the hardware on the device), the IoT Profile Assistant (IPA, sometimes embedded in the eUICC, sometimes in the device OS), and the eIM (eSIM IoT remote Manager, hosted by the connectivity provider or a third party). The eIM talks to SM-DP+ servers operated by the destination mobile operators.
Why messaging buyers care
If you are deploying connected products that need SMS for command-and-control (smart meters reading on-demand, asset trackers reporting motion), SGP.32 simplifies the provisioning experience and cuts roaming cost. BroadNet's TripoSIM product is built on SGP.32 with eIM in our Dubai data centre — global SIM, MENA-anchored signalling, no per-device SM-DP+ contracts.
Adoption state
First commercial SGP.32 devices shipped in late 2024. Most tier-1 operators announced eIM support through 2025. Expect SGP.32 to be the dominant IoT eSIM architecture by 2027, displacing SGP.02 for new deployments while existing M2M fleets stay on SGP.02 for their useful life.