SGP.32: the new eSIM standard for scalable IoT connectivity

The rise of eSIM (eUICC) technology has fundamentally changed the way IoT connectivity is deployed. Physical SIM cards still need to be replaced per location, whereas SGP.32 makes it possible to remotely install an eProfile on the eSIM (eUICC).

With the introduction of SGP.32, the GSMA delivers a new standard that is a true game changer. It combines flexibility in profile management with scalability and control, making it easier to connect devices worldwide in a compliant manner.

What is SGP.32 and how does it differ from earlier eSIM standards?

SGP.02, introduced in 2014, enabled operators to push profiles to IoT devices but offered limited control to end users. SGP.22 (2016) introduced the pull model, allowing end users to download profiles themselves. This approach was primarily suited for consumer devices such as smartphones and wearables.

SGP.32 combines the best of both worlds: it is designed for the enterprise market, supports both push and pull models, and introduces the eIM (eUICC IoT Manager) as an intermediary layer for provisioning and management. As a result, organizations gain greater autonomy over eProfile provisioning.

Why is this relevant for large-scale IoT deployments?

For organizations managing thousands of devices worldwide, manually swapping SIM cards is highly impractical. SGP.32 enables organizations to:

• remotely activate or switch profiles without physical access to the device;
• comply with local regulations, such as restrictions on permanent roaming;
• quickly switch eProfiles (operators) in response to price changes or service disruptions;
• build scalable network infrastructures independent of individual operator contracts.

What are the technical and operational considerations?

While SGP.32 is promising, it requires a careful implementation strategy. Key considerations include:

• Interoperability: not all MNOs and MVNOs support SGP.32 at market introduction.
• Security & compliance: the standard provides strong authentication and encryption, but compliance with local data storage and identification laws remains the responsibility of the end customer.
• Backend integration: SGP.32 requires integration with existing systems such as provisioning platforms and APN configurations.
• Cost structure: profile hosting and switching may incur additional costs, such as monthly fees for access to eProfiles.

In which scenarios does SGP.32 add value?

SGP.32 is particularly suited for organizations with international or dynamic connectivity requirements, such as:

• OEMs deploying devices across multiple countries with diverse network requirements;
• manufacturing environments where devices are preconfigured during production (for example in China) but only become operational at a later stage.

What is the right approach?

Migrating to SGP.32 requires a phased approach. We recommend starting with:

• IoT readiness assessment: determine which devices already support eUICC and which modems need to be replaced or upgraded.
• Pilot project: test SGP.32 in a limited environment, focusing on provisioning, eProfile switching, and network stability.
• Integration and tooling: ensure management systems are prepared for dynamically adding and switching profiles via eIM and SM-DP+.
• Operational guidelines: define clear procedures for eProfile management, roaming control, and incident handling.

SGP.32 offers clear advantages—but only when embedded within a well-organized connectivity management architecture.

More information

Would you like to know what SGP.32 can mean for your IoT strategy? Thingsdata supports organizations in the preparation, integration, and implementation of eSIM technology based on the latest GSMA standards.

Contact us at +31-85-0443500 or email info@thingsdata.com. We are happy to help you realize scalable, flexible, and future-proof IoT connectivity.