Skip to main content
IoT Glossary

What is SGP.32 eSIM?

SGP.32 marks a major evolution in eSIM technology. Designed with IoT in mind, it promises to simplify connectivity, enhance security and unlock global scalability. But what makes this new GSMA standard so transformative? Let’s explore what’s behind SGP.32. 

What is SGP.32 eSIM?

SGP.32 is the GSMA’s latest remote SIM provisioning (RSP) standard which promises to unify and optimise the GSMA standards for RSP and drive mass adoption of eSIM and iSIM technologies.   

Unlike SGP.02 and SGP.22 standards, SGP.32 is specially tailored for IoT (Internet of Things) devices - especially those with minimal user interface or constrained connectivity – and it optimises secure, large-scale, over-the-air management of eSIM profiles across device fleets.

 

Why SGP.32 matters

  • Built for constrained IoT environments: Unlike earlier standards, SGP.32 is optimised for devices with limited memory, intermittent connectivity and no user interface
  • Modern, modular infrastructure: It introduces two new components — IPA (IoT Profile Assistant) on the device and eIM (eSIM IoT Remote Manager) in the backend, enabling lightweight, scalable provisioning
  • IP-based, SMS-free operation: SGP.32 replaces cumbersome SMS-driven approaches with efficient IP protocols like CoAP and DTLS — boosting reliability and performance
  • Global scalability and flexibility: Enables enterprises to deploy and manage IoT devices worldwide. It make connectivity and carrier switching easier and more seamless. 
why-sgp32-matters

SGP.32 vs. SGP.02 and SGP.22

With SGP.32 the trigger point for profile interactions can be the device or the cloud/server. In other words it supports a push and a pull model which was not the case with SGP.02 (push only) and SGP.22 (pull only). 

Some vendors claimed that the SGP.22 “pull” model gave consumers the ultimate flexibility and removed enterprise and operator control but this is largely inaccurate. Operators and enterprises retain full control over which profiles are downloaded and activated on IoT devices and for good reason. It helps maintain quality of service and security.  

This same is true for SGP.32, only pre-approved and contracted profiles can be downloaded and activated meaning operator relationships remain key although in the vast majority of cases an IoT service provider (or MVNO) will manage this for you.  

 

Standard 

Use Case 

Device Constraints 

Provisioning Mechanism 

Scalability & Flexibility 

SGP.02 (M2M) 

Automotive/industrial/M2M devices 

Headless, resource-heavy devices 

Pushbased, SMS-centric 

Limited; not designed for wide-scale IoT sensors 

SGP.22 (Consumer) 

Smartphones, consumer gadgets 

UI-enabled, interactive 

Pullbased via user interaction (QR, app) 

High for consumer 

SGP.32 (IoT) 

Low-power, headless IoT devices 

UI-constrained, network-limited 

Push/pull with IPA + eIM, IPbased 

Optimised for global, scalable IoT rollouts 

 

Key differences

sgp32-differences
  • SGP.02 relies on SMS and lacks agility for modern IoT - making it more complex and less flexible 
  • SGP.22 is designed for consumer devices and depends on user-driven provisioning - it doesn't suit unmanned or remote IoT equipment 
  • SGP.32 merges the best of both, delivering secure, automated provisioning tailored for IoT environments - with components like eIM and IPA built for scale and resilience. 

Note that Wireless Logic orchestrates the sourcing, deployment and management of virtual eSIM profiles using all three RSP standards and removes the majority of the shortcomings mentioned above. 

sgp32-features-1

Key features of SGP.32

Remote SIM provisioning (RSP)

IoT devices can receive, enable, disable or delete SIM profiles over the air - no physical SIM changes are needed.

IoT friendly architecture

  • eIM:  Manages profile orchestration transactions

  • IPA: Device-side agent that interfaces with the eSIM

  • SM-DP+: The secure backend system that stores and delivers eSIM profiles

  • Enables robust, scalable deployments.

The eIM itself will most commonly operate under the control of a higher layer management function, commonly referred to as eSIM Orchestrator (eSO).

sgp32-features-2

Secure & efficient connectivity 

  • IP-based protocols (e.g., CoAP, DTLS) replace SMS for faster, lightweight provisioning
  • Supports low-bandwidth and discontinuous networks where devices might be in sleep-more for periods of time.  

Global deployment support 

  • Reduces dependencies on operators and roaming
  • Enables mass rollout and autonomy across regions and networks
  • Lowers operational costs and simplifies compliance.

When to use SGP.32

SGP.32 is ideal for the vast majority of IoT applications but especially those which include: 

  • Devices with no UI or deployed in remote locations 
  • Need for remote, automated provisioning of SIM profiles 
  • Global or large-scale deployments requiring flexibility, security and cost-efficiency 
  • Devices which are operate in the field for multiple years and might experiences to commercial, performance on regulatory changes. 
when-to-use-sgp32

Further reading

Wireless Logic orchestrates the sourcing, deployment and management of virtual eSIM profiles using all three RSP standards. 

Click below to read more about remote SIM provisioning (RSP).

IoT. It's not complicated with Wireless Logic.

Design and deploy a future-proof IoT solution that scales with your business.