Table of Contents
- Introduction – The Dawn of Seamless Connectivity
- The ‘Before’ Picture – Why a New eSIM Standard Was Needed
- Consumer eSIM (GSMA SGP.21 / SGP.22): The User-Driven Approach
- M2M eSIM (GSMA SGP.01 / SGP.02): The Machine-Centric Approach
- Introducing SGP.32 – The Unified Solution for eSIM Connectivity Management
- How SGP.32 Works (Simplified)
- Key Benefits of the SGP.32 Standard
- For Device Manufacturers (OEMs)
- For Mobile Network Operators (MNOs) & Mobile Virtual Network Operators (MVNOs)
- For Service Providers & Enterprises
- For End-Users
- Spenza – Navigating the Multi-Operator Future with Unified eSIM
- Conclusion – SGP.32: Simplifying Today, Unifying Tomorrow
- FAQs

Introduction: Simplifying Connectivity with SGP.32
Our world thrives on connection, from smartphones and laptops to industrial sensors and tiny trackers. While eSIM technology promised easier connectivity management than traditional SIM cards, its initial rollout created complexity. Different standards emerged for consumer devices (requiring user interaction) and Machine-to-Machine (M2M)/IoT devices (needing remote management), leading to fragmentation.
Presenting the GSMA SGP.32 eSIM standard – the new, unified approach designed to simplify everything. This groundbreaking standard merges the previous consumer and M2M specifications, creating a single, flexible framework for all connected devices. SGP.32 streamlines eSIM connectivity management, making it easier to deploy and manage connections for both personal gadgets and the vast world of IoT eSIM devices. It’s the future-proof eSIM specification built to unlock seamless connectivity for billions of devices worldwide.
The ‘Before’ Picture: Why Was a New eSIM Standard Needed?
To truly appreciate the significance of SGP.32, we must first understand the landscape it aims to simplify. Before its introduction, the eSIM world operated largely on two distinct tracks, each defined by GSMA specifications tailored for different primary use cases:
Consumer eSIM (GSMA SGP.21/SGP.22): The User-Driven Approach
This is the eSIM technology most familiar to consumers. Designed primarily for devices like smartphones, tablets, smartwatches, and laptops, the SGP.21 (Architecture) and SGP.22 (Technical Specification) standards focused on user-centric activation and management.

- Target Devices: User-facing electronics where interaction is expected.
- Mechanism: Relied on a component called the Local Profile Assistant (LPA) residing on the device. Profile downloads from the operator’s SM-DP+ (Subscription Manager – Data Preparation+) were typically initiated by the end-user. This often involved scanning a QR code provided by the operator, using a carrier app, or navigating device settings menus. The user essentially “pulled” the desired profile onto their device.
- Limitations: While effective for consumer devices, this model proved less suitable for scenarios involving large numbers of devices requiring remote provisioning without user intervention, or for “headless” devices (those without screens or input methods) common in IoT. Custom workarounds were often needed for M2M/IoT applications trying to leverage this standard. Furthermore, dependencies on SMS or specific protocols like HTTPS could be challenging for resource-constrained IoT devices.
M2M eSIM (GSMA SGP.01/SGP.02): The Machine-Centric Approach
Developed earlier (around 2013-2014), the SGP.01 (Architecture) and SGP.02 (Technical Specification) standards were purpose-built for Machine-to-Machine (M2M) communication and the burgeoning IoT market.

- Target Devices: Industrial sensors, smart meters, asset trackers, connected cars, and other devices where remote, automated management is paramount.
- Mechanism: Employed a server-driven “push” model. It involved two key network elements: the SM-DP (Subscription Manager – Data Preparation) for creating profiles and the SM-SR (Subscription Manager – Secure Routing) for securely delivering and managing those profiles on the remote device’s eUICC (embedded Universal Integrated Circuit Card – the eSIM chip). This allowed network operators or service providers to remotely push profile updates or switch profiles without needing physical access or user interaction.
- Limitations: While robust and secure, the M2M architecture was often considered more complex and rigid. It required intricate integration between the SM-DP and SM-SR platforms, and often necessitated cooperation between the “donor” and “recipient” operators during a profile switch. This complexity could hinder flexibility and scalability, especially when dealing with diverse global deployments or needing to switch providers easily. It also typically relied on SMS for triggering operations, which isn’t supported by all modern IoT network technologies like NB-IoT.
The Fragmentation Problem
- OEMs faced increased costs and development time managing distinct connectivity stacks.
- MNOs/MVNOs had to maintain separate, complex backend infrastructures.
- Siloed ecosystems hindered seamless integration for hybrid devices.
- The complexity of SGP.02 and user-centricity of SGP.22 hampered scalable IoT deployment.
Clearly, a new eSIM standard was needed – one that could bridge the gap, eliminate fragmentation, and offer a unified eSIM approach fit for the diverse connectivity demands of the modern world.
Introducing SGP.32: The Unified Solution for eSIM Connectivity Management

Recognizing the limitations and fragmentation caused by the separate consumer and M2M tracks, the GSMA embarked on developing a next-generation eSIM specification. The result, officially published with its technical specification (SGP.32) in May/July 2023 and reaching a stable version (v1.2) in June 2024, is the GSMA SGP.32 eSIM standard.
What is GSMA SGP.32?
At its core, SGP.32 is the new eSIM standard designed specifically to provide a single, unified eSIM framework for remotely provisioning and managing eSIM profiles across all types of devices, with a particular focus on addressing the needs of the rapidly expanding IoT eSIM market. It effectively takes the best elements from the previous standards and merges them into a streamlined, flexible, and future-proof architecture.
Core Concept: Unification – One Standard to Rule Them All
The central philosophy behind SGP.32 is unification. Instead of separate approaches for consumer (mobile eSIM) and machine (IoT eSIM) devices, SGP.32 provides a common foundation. This simplifies the entire ecosystem, from chip design and device manufacturing to network infrastructure and service deployment. It aims to be the universal standard for eSIM connectivity management, regardless of whether the device is a powerful smartphone or a low-power sensor.
The Key Innovation: The IoT eSIM Manager (eIM) and IoT Profile Assistant (IPA)
To achieve this unification and address the limitations of previous standards (especially for IoT), SGP.32 introduces a clever evolution of the device-side logic. It effectively splits the functionality of the old Consumer LPA into two distinct, standardized components:

- eIM (eSIM IoT Remote Manager): This is a crucial new element, often residing in the cloud or on a network server. The eIM acts as a standardized remote provisioning tool. Its primary role is to handle the remote management of eSIM profiles – initiating downloads, enabling, disabling, or deleting profiles on potentially vast fleets of devices. It essentially takes the “intent” or command authority away from needing to be solely on the device (like in SGP.22) or locked within complex M2M infrastructure (like SGP.02) and places it in a flexible, remote management entity. The eIM can be operated by the MNO, MVNO, or even potentially the enterprise or OEM managing their device fleet.
- IPA (IoT Profile Assistant): This component acts as the local intermediary on the device, facilitating communication between the remote eIM and the eUICC (the eSIM chip). It receives commands from the eIM and executes the necessary actions on the eUICC, such as managing the profile download process from the SM-DP+. The IPA is designed to be lightweight and efficient. It can be implemented either as software running on the device’s main processor (IPA.d) or embedded directly within the secure eUICC chip itself (IPA.e). Using IPA.e can simplify certification for device makers as the component is pre-certified within the secure chip.
Bridging the Gap
By combining the existing SM-DP+ infrastructure (used in SGP.22) with the new eIM and IPA components, SGP.32 cleverly bridges the gap:
- It retains the flexibility and widely adopted SM-DP+ infrastructure from the consumer world, avoiding the need for the complex SM-SR of the M2M standard.
- It introduces the eIM/IPA mechanism to enable robust, scalable, and standardized remote management, which was the strength of the M2M approach but is now achieved more flexibly.
- It allows profile management to be triggered remotely (like M2M) or potentially by a local application (like Consumer), offering maximum versatility within a single framework.
This unified eSIM architecture is the foundation for simplifying eSIM connectivity management across the board.
How SGP.32 Works (Simplified)
While the underlying technical specifications are detailed, the operational concept of SGP.32 can be understood through its core components and process flow. It’s designed for efficiency, especially for IoT eSIM devices that might be constrained by power, memory, or network bandwidth.
The Architecture Overview:
The key players in an SGP.32 ecosystem are:

- eUICC (Embedded Universal Integrated Circuit Card): The secure chip embedded in the device that stores operator profiles and cryptographic keys. This is the eSIM hardware itself.
- IPA (IoT Profile Assistant): As described above, the lightweight component on the device (IPA.d) or eUICC (IPA.e) that acts as the local agent, communicating with the eIM and managing profile operations on the eUICC.
- eIM (eSIM IoT Remote Manager): The remote, server-based entity responsible for initiating and managing profile operations (download, enable, disable, delete) for one or many devices. It communicates securely with the IPA.
- SM-DP+ (Subscription Manager – Data Preparation+): The operator’s platform responsible for creating, securing, and storing the actual network profiles that will be downloaded to the eUICC. The SGP.32 standard leverages the existing SM-DP+ infrastructure defined for consumer eSIM.
Key Benefits & Advantages of the SGP.32 eSIM Standard
The shift towards the unified eSIM model offered by GSMA SGP.32 delivers tangible advantages across the entire connected device ecosystem. Its focus on simplification, flexibility, and scalability addresses key pain points of the previous fragmented standards.
SGP.32 brings all eSIMs under one simple, flexible system. Instead of juggling different technical setups for phones, wearables, sensors, and more, everyone can use the same basic approach. This cuts costs, speeds up launches, and makes it easy to add connectivity to almost any device.
For Device Makers (OEMs)
- One Design Fits All: You no longer need separate SIM hardware or software for each product line. A single eSIM solution works for both high‑end gadgets and tiny IoT sensors.
- Lower Costs & Fewer Headaches: Less engineering work, simpler testing, and standard parts mean you spend less on R&D and logistics.
- Faster to Market: With one unified integration process, your new products can ship sooner.
- Smarter Devices: Easier connectivity lets you build features that were too costly or complex before.
For Mobile Network Operators (MNOs & MVNOs)
- Use What You Already Have: SGP.32 builds on the common consumer eSIM ecosystem, so you can avoid running separate legacy platforms.
- Simpler Device Onboarding: A single management interface handles phones, cars, industrial sensors, and everything in between.
- Reach More Customers: Easier eSIM adoption across industries means a bigger potential market, especially in IoT.
- New Revenue Streams: Create special data plans and services for smart meters, trackers, medical devices, etc., and let customers switch providers more easily.
For Service Providers & Enterprises
- Centralized Fleet Management: Manage thousands—or even millions—of devices around the world from one dashboard.
- Choice & Control: Switch carriers or negotiate better rates without re-engineering each integration. You can even run your own management server.
- Scale Without Strain: Built for mass deployments, SGP.32 handles bulk activations and updates far more efficiently.
- Lower Operating Expenses: No more manual SIM swaps or site visits—everything is provisioned and updated over the air.
- Future‑Ready: A global standard that keeps pace with 5G, 6G, and whatever comes next.
For End Users
- Hassle‑Free Setup: Activations and updates happen automatically, so your devices just work.
- More Connected Gadgets: Smaller, cheaper, and lower‑power devices can now get online, from smart home sensors to wearable health monitors.
- Reliable Service: Remote troubleshooting and updates mean fewer dropouts and faster fixes
In essence, the SGP.32 eSIM standard acts as a catalyst, reducing friction and enabling innovation across the board, paving the way for a more seamlessly connected future.
Spenza: Navigating the Multi-Operator Future with Unified eSIM
The new SGP.32 standard makes it technically easier to switch your eSIM to different mobile operators. But even with SGP.32, handling multiple plans, bills, and connections from various providers can still be complicated for businesses. That’s where platforms like Spenza come in.
What is Spenza?
Think of Spenza as a helpful control center for business connectivity. It’s a platform that doesn’t favour any single mobile operator (it’s operator-neutral). Spenza offers software and a marketplace where businesses can find, buy, and manage mobile plans from many different providers. The main goal is to make managing wireless services and costs much simpler. Spenza’s services fit perfectly with the benefits of the new SGP.32 standard:
- Handles Multi-Operator Complexity: While SGP.32 allows easier switching, Spenza helps you manage the practical side. It gives you one central place (a “single pane of glass”) to see all your plans, track spending, and handle connections from different operators. No more juggling multiple systems!
- Lets You Use SGP.32’s Flexibility: SGP.32 gives you the freedom to choose providers. Spenza’s marketplace makes it easy to find and select the best plans for your needs – whether you need low data for sensors or high data for video, local plans or global roaming – from many different MNOs and MVNOs.
- Supports IoT Devices: Spenza works well for companies using lots of connected devices, like IoT sensors or even smartwatches. It offers custom plans and helps manage the specific needs of these deployments, like providing multi-operator SIMs/eSIMs to ensure good coverage. Companies like Butlr use it to manage plans in different countries easily.
- Keeps You Ready for the Future: As technology like SGP.32 rolls out, Spenza helps businesses use these new standards effectively. Because it’s neutral and automated, Spenza makes it easier to manage your connections as the industry changes.
In short, SGP.32 provides the technical ability for more flexible eSIM management, and platforms like Spenza provide the practical tools to make managing that flexibility simple and efficient for businesses.
Conclusion: SGP.32 – Simplifying Today, Unifying Tomorrow
The journey of eSIM technology has moved from fragmented standards like SGP.22 (Consumer) and SGP.02 (M2M) to a unified future with the GSMA SGP.32 standard. Designed to solve the complexity of earlier models, SGP.32 introduces a new architecture with the eIM (eSIM IoT Remote Manager) and IPA (IoT Profile Assistant), combining the flexibility of consumer eSIMs with the robust remote management needed for IoT and M2M. It simplifies device design, streamlines operations, and creates a scalable, standardized foundation to manage billions of connected devices more efficiently.
SGP.32 represents more than just a technical upgrade—it brings true simplification, unification, and scalability to eSIM connectivity. By breaking down silos and reducing complexity, it empowers OEMs, operators, enterprises, and end users alike. As adoption continues to grow through 2025 and beyond, SGP.32 is set to unlock new possibilities, lower costs, and bring us closer to a seamless, interconnected world. Understanding SGP.32 is not just about technology—it’s about embracing the future of global connectivity.
FAQs
The GSMA SGP.32 eSIM standard is a technical specification for remote eSIM provisioning (RSP) specifically designed for IoT devices, particularly those with network or user interface constraints.
SGP. 22 is a method of delivering eSIM profiles to consumer devices.
SGP. 02 was developed with the specific goal of supporting remote SIM provisioning (RSP) for M2M applications
SGP.32 combines the best aspects of the older standards. Unlike SGP.02, which focuses on basic machine-to-machine connections, and SGP.22, which caters to consumer devices, SGP.32 is designed for large-scale, remotely managed IoT deployments with enhanced security and efficiency.
SGP.32 offers several key benefits for IoT connectivity, especially in eSIM deployments. It simplifies provisioning and management, enhances security, and provides greater flexibility for global IoT rollouts.
The IPA acts as an intermediary between the eSIM and the eIM and facilitates communication and commands from the eIM to the device
SGP.32 works for both M2M and consumer profiles while SGP.22 was limited to only M2M use.
Is your business ready for the future of connectivity? Book a demo with Spenza today to leverage unified eSIM management and simplify your multi-operator strategy in the SGP.32 era.