What Is GSMA SGP.32?

Understand how SGP.32 enables remote SIM provisioning for IoT connectivity and how it differs from earlier eSIM standards.

Last updated: May 2026

In a world of connected devices, reliable and flexible connectivity is essential. As IoT adoption grows, from industrial sensors to smart home products, there’s a clear need for a simpler, more scalable way to manage connectivity. GSMA SGP.32 is the latest eSIM standard, developed specifically to address the challenges of IoT. On this page, we explain what SGP.32 is, how it works, and how it differs from earlier standards like SGP.22.

GSMA SGP.32 at a Glance

Standard: GSMA SGP.32 (IoT eSIM / RSP)
Designed for: IoT devices, especially without a user interface
Core capability: Remote SIM provisioning and profile management at scale
Replaces / complements: SGP.02 for M2M use cases and complements SGP.22 for consumer eSIM
Commercial status: Available to order; delivery started 17 April 2026

What Is SGP.32?

SGP.32 is a global, next-generation eSIM standard by GSMA for remote SIM provisioning in IoT devices, especially those with no user interface. It enables large-scale, hands-off management of eSIM profiles, making it easier to deploy and operate IoT devices without physical access.

Video

SGP.32 Explained in Under 3 Minutes

Why SGP.32 Matters for IoT

For global IoT deployments, connectivity is no longer just a question of getting devices online. The bigger challenge is keeping them connected, adaptable, and able to meet changing market and regulatory requirements throughout their lifecycle.

SGP.32, the GSMA’s IoT eSIM standard, helps address this shift by making IoT connectivity more flexible. Instead of treating the SIM profile as a fixed decision made at production, enterprises can design devices to support remote profile management over time. This makes it easier to adapt when coverage needs, market conditions, regulations, or commercial agreements change.

The value is especially clear for long-life IoT devices, such as connected vehicles, smart meters, industrial equipment, and logistics trackers. These devices may remain in the field for years, often across multiple markets, where connectivity requirements can change after deployment.

SGP.32 reduces technical lock-in and supports more flexible global deployment models. But flexibility is not the same as simplicity. To get the full value, enterprises still need to manage global roaming, local profile access, device readiness, regulatory requirements, and operational support.

When Should Enterprises Use SGP.32 for IoT?

Enterprises should consider SGP.32 when IoT devices need to remain flexible after deployment, especially across global markets, long product lifecycles, or changing connectivity requirements.

Use SGP.32 for IoT When...	SGP.32 May Be Less Urgent When...
IoT devices need long-term flexibility after deployment	The selected connectivity setup is expected to remain suitable throughout the product lifecycle
Devices are difficult, expensive, or impractical to access physically	Physical SIM replacement is realistic for the deployment
Future connectivity profile changes may be needed	The same connectivity profile or operator setup is expected to meet the deployment’s needs over time
Market dynamics, roaming rules, or local access requirements may change	The deployment operates in a stable and well-defined market environment
A Single SKU strategy is important and hardware alignment allows it	Regional hardware or SIM variants are already required and manageable
The business wants to reduce technical lock-in to one connectivity setup or provider	The selected connectivity model is expected to remain suitable over time
Global roaming is useful for launch, but future local profile access may be needed	Global roaming continues to meet operational, commercial, and regulatory needs

SGP.32 does not need to replace every existing connectivity model. For many global IoT deployments, the strongest approach is to use global roaming for immediate scale while keeping devices SGP.32-ready for future profile changes, local profile access, or changing market requirements.

Quick Primer: What Is an eSIM?

An eSIM (Embedded SIM) is a SIM card with built-in eUICC software that allows network profiles to be remotely updated over the air, without needing to replace the SIM. This makes it easier to manage connectivity and enables truly global IoT products with a single SKU that can be configured when deployed. eSIM technology can be used in plastic and solderable SIMs.

Want to understand the bigger picture? Read our introduction to IoT SIM cards.

How eSIM Standards Have Evolved

The GSMA, the industry body responsible for mobile communication standards, has played a pivotal role in shaping eSIM technology. Early M2M eSIM standards (SGP.02) relied on server-driven provisioning, often using SMS for communication. Later, consumer eSIM standards (SGP.22) were introduced to support devices with a user interface, allowing users to manage SIM profiles directly. However, neither approach fully addressed IoT-specific challenges:

M2M standards (SGP.02) were complex and heavily dependent on SMS or TCP/IP, making them unsuitable for devices with limited power or no SMS capability.
Consumer eSIM models (SGP.22) required user interaction, which is impractical for many IoT deployments where devices are remote or inaccessible.

To bridge this gap, GSMA SGP.32 was developed, combining the best aspects of both models while introducing new capabilities tailored for IoT. Unlike SGP.22, which is designed for consumer devices with a user interface, SGP.32 is specifically designed for IoT deployments where devices operate without user interaction. The GSMA maintains a comprehensive list of published eSIM specifications.

Comparing eSIM Standards: SGP.02 vs. SGP.22 vs. SGP.32

Feature	SGP.02 (eSIM M2M)	SGP.22 (Consumer eSIM)	SGP.32 (eSIM IoT)
Use Case	M2M devices	Consumer electronics	IoT deployments
Profile Management	Server-driven (typically via SMS or IP)	User-initiated using a Local Profile Assistant	Remote, bulk profile switching via an IoT Profile Assistant (IPA) controlled by an eSIM IoT Remote Manager (eIM)
User Interaction	Limited; managed by the server	Requires manual interaction	No user interaction needed
SMS Dependency	Commonly required	Not typically needed once activated	Not required (optional in rare cases)
Protocols	Primarily TCP/IP	TCP/IP and SMS for initial provisioning	Lightweight protocols such as CoAP, UDP, and DTLS
Power Efficiency	Less optimised for low-power devices	Suited for devices with richer user interfaces	Optimised with a light profile template for low-power devices

Key Benefits of SGP.32 for IoT

SGP.32 was designed from the ground up to meet the specific demands of IoT deployments. Its main benefits include:

Scalability

Managing connectivity for a handful of devices is one thing, but what about tens of thousands of sensors, meters, or trackers spread across the globe? SGP.32’s remote provisioning capabilities allow for bulk profile management, meaning changes can be applied quickly across an entire fleet without physical access to each device.

Efficiency for Low-Power Devices

SGP.32 is optimised for devices with limited power or memory. By using lightweight profile templates and offloading processing to the network-based eSIM IoT Remote Manager (eIM), it minimises device resource consumption and extends device lifespan.

Simplified Remote Management

In many IoT scenarios, devices are deployed in hard-to-reach or remote locations, think environmental sensors in the wild or industrial sensors in hazardous areas. SGP.32 enables centralised control of these devices, eliminating the need for local user interaction. Profile downloads, switches, and modifications are handled remotely via the eIM, reducing operational costs and simplifying large-scale deployments.

No Need for SMS or Legacy Protocols

Unlike older M2M SIM models that depend on SMS or TCP/IP to issue commands, SGP.32 enables seamless communication using modern, lightweight protocols, ideal for devices that don’t support SMS.

Enhanced Security & Compliance

Security is a critical concern for IoT deployments. SGP.32 incorporates robust safeguards for provisioning and managing network profiles, helping ensure compliance with global regulations and protection against unauthorized access.

Future-Proof Design

Built on a global GSMA standard, SGP.32 ensures long-term compatibility with new networks, devices, and emerging technologies, safeguarding your IoT investment.

For those interested in the technical specifications behind this innovation, the GSMA provides detailed documentation on the SGP.32 standard (published June 2024).

A fully standardised SGP.32 implementation, combined with Telenor IoT’s global roaming portfolio, enables the delivery of a comprehensive, future-proof connectivity solution.

Mårten Ulvsbäck Product Manager Telenor IoT

What SGP.32 Does and Does Not Solve

SGP.32 gives enterprises more flexibility in how IoT connectivity profiles are managed over time. But it is important to separate what the standard enables technically from what still needs to be managed commercially, operationally, and regionally.

SGP.32 can help enterprises:

manage SIM profiles remotely across IoT devices;
reduce technical lock-in to one fixed SIM profile or connectivity setup;
support future profile changes without physical SIM swaps;
address permanent roaming challenges by enabling profile switching;
support a Single SKU strategy where hardware alignment allows.

SGP.32 does not automatically solve:

local telecom regulations, commercial access rights, or regional licensing requirements;
device, module, or eUICC readiness across an existing fleet;
radio frequency support, regional certification, or hardware constraints;
the operational work of managing profiles, support, billing, fallback logic, and service continuity.

In short, SGP.32 is a technical standard, not a complete operating model. Its value is strongest when combined with global roaming, local profile access, device readiness, and managed connectivity orchestration.

SGP.32 Availability

Telenor IoT now offers a fully standardised SGP.32 eSIM solution. SGP.32 SIM cards can be ordered and are available for delivery.

The standardised implementation ensures seamless interoperability, simplified integration, and consistent security across networks and devices. Unlike non-standardised alternatives, it eliminates compatibility issues and reduces the risk of vendor lock-in, ensuring long-term flexibility and reliability.

Testing is available through Telenor IoT Test SIMs and pilot deployments, enabling evaluation of SGP.32 prior to large-scale rollout.

SGP.32 in Practice

See how Axentia enables global connectivity using SGP.32.

Read the case study

Optimised IoT SIM Cards for Reliable IoT Connectivity

With global coverage, versatile form factors, and adherence to established GSMA and 3GPP standards, we are committed to providing the best possible SIM solutions for your IoT needs. Connect your IoT devices with ease and confidence with Telenor IoT.

Building Future-Ready IoT Connectivity With SGP.32

SGP.32 is a major step forward for IoT connectivity, especially at scale. It eliminates manual SIM management, supports low-power devices, and simplifies operations for global fleets.

Whether you're deploying connected products today or planning for the future, understanding SGP.32 is key to building flexible, secure, and scalable IoT solutions.

SGP.32 is still a relatively new standard. While it is now commercially available, broader ecosystem support across device vendors and profile providers continues to mature. Organisations exploring SGP.32 should evaluate compatibility and readiness across their value chain. We’re here to help you with that!

Co-authored by Our Expert

Mårten Ulvsbäck, Product Manager Telenor IoT, drives innovation in eSIM technology. With deep expertise in eUICC and SGP.32, he’s shaping the future of global IoT connectivity. Catch his insights at our SGP.32 webinar, where he explores SGP.32’s impact for enterprises.

Webinar: Your Guide to the New SGP.32 Standard

On demand

Watch the webinar on SGP.32

Frequently Asked Questions

What does SGP stand for?

SGP stands for SIM Group Permanent. It refers to a series of GSMA initiatives aimed at developing and standardising the next generation of SIM technologies, including those designed for IoT.

What is Remote SIM Provisioning (RSP)?

Remote SIM Provisioning is the process of updating, activating, or switching a device’s SIM profile over the air—without needing to physically swap SIM cards. It allows operators and IoT solution providers to manage connectivity for devices at scale, enabling them to deploy updates, change networks, or add new services without manual intervention.

What is eUICC (Embedded Universal Integrated Circuit Card)

eUICC is a type of SIM technology that enables remote SIM provisioning, allowing multiple mobile network operator (MNO) profiles to be stored and switched over-the-air. Unlike traditional SIM cards, eUICCs support dynamic profile changes without physical replacement, making them ideal for IoT and enterprise deployments.

What is the difference between SGP.32 and SGP.22?

SGP.22 was developed primarily for consumer devices—think smartphones, tablets, and smartwatches. In these devices, users interact directly with the device to manage their eSIM profiles (for example, scanning a QR code or using a dedicated app). The SGP.22 standard supports multiple profiles and the ability to switch between them, but it is very much designed with a user interface in mind.

SGP.32, on the other hand, is designed specifically for IoT. Many IoT devices operate in environments where there is no human to initiate or manage profile changes. SGP.32 allows network profile management to be conducted entirely remotely, without any need for user intervention. This capability is crucial when dealing with thousands of devices in remote or hard-to-access locations.

The key differences, therefore, lie in the mode of operation and target application:

User Interaction: SGP.22 is user-driven; SGP.32 is server- or cloud-driven.
Protocol Support: SGP.32 eliminates reliance on SMS, making it suitable for devices with limited capabilities.

Scalability: SGP.32 is built to handle large-scale deployments and offers bulk management functionalities that SGP.22 does not emphasise.

Does SGP.32 replace global roaming?

Not necessarily. For many global IoT deployments, roaming remains the fastest and most practical way to launch across markets. SGP.32 adds flexibility by making it possible to manage and change connectivity profiles remotely over time. In practice, SGP.32 and global roaming can work together: roaming can support immediate deployment, while SGP.32 helps prepare devices for future profile changes or local profile access where needed.

Can SGP.32 help with permanent roaming restrictions?

Yes, SGP.32 can help address permanent roaming challenges by enabling IoT devices to switch connectivity profiles remotely. However, SGP.32 is not a regulatory shortcut. Local market rules, operator agreements, licensing requirements, and commercial access rights still need to be managed. The standard enables profile switching technically, but the wider regulatory and commercial model still matters.

Is SGP.32 enough to make IoT devices locally compliant?

No. SGP.32 is a technical standard for remote SIM provisioning and profile management. It can support compliance strategies by making local or alternative profiles easier to manage, but it does not automatically make a device compliant in every market. Enterprises still need to consider local telecom rules, data requirements, device certification, security obligations, and commercial agreements.

Can SGP.32 support a Single SKU strategy?

Yes, SGP.32 can support a Single SKU strategy by reducing the SIM profile as a source of regional variation. However, it does not remove every hardware or regulatory constraint. A true Single SKU approach still depends on factors such as module frequency-band support, radio certification, regional requirements, and device design. SGP.32 helps with connectivity profile flexibility, but hardware alignment still matters.

Do existing IoT devices support SGP.32?

It depends on the device, module, eUICC, firmware, and connectivity setup. SGP.32 requires a standardized SGP.32-capable eUICC, so existing deployments may not be able to use SGP.32 without hardware or software changes. Enterprises planning new IoT products should check SGP.32 support early in the module and eUICC selection process, especially for devices with long lifecycles or global deployment requirements.

What should enterprises check before adopting SGP.32?

Enterprises should check device and module readiness, eUICC support, firmware requirements, profile management processes, fallback behavior, roaming needs, local profile access, and regulatory requirements in target markets. They should also clarify who manages profile orchestration, support, billing, commercial agreements, and service continuity across the device lifecycle.

Talk to Our Experts

Want to know how SGP.32 fits into your IoT strategy?

Get in touch