SGP.31/.32: New GSMA Standards for Massive Deployments
As the number of devices connected to the internet, like sensors and trackers, is growing, common standards are also changing. The initial communication standards didn't intend to handle the sheer number and variety of these 'Internet of Things' (IoT) devices. Organizations like GSMA are working on the creation of new standards that address the specific challenges of IoT, e.g., remote monitoring of the large numbers of devices, enabling access to different networks, and optimizing them for limited-power devices. The GSMA (Global System for Mobile Communications Association) has introduced key specifications, SGP.31 and SGP.32 to address these requirements in the context of eSIM. The standards provide a specific framework for the RSP (remote SIM provisioning) in IoT devices and aim to improve large-scale IoT deployments.
Short Overview of SGP.31/SGP.32
SGP.31 describes the architecture and specifications for the remote provisioning of embedded universal circuit cards, or eUICCs, in Internet of Things devices. It helps to overcome the challenges of eSIM deployment in devices with resource constraints or limited user interfaces, which are common for many IoT use cases.
On the other side, SGP.32 provides the technical implementation of SGP.31, detailing the procedures and protocols for managing eSIMs in different IoT environments. SGP.32 defines how to implement remote provisioning and the use of eSIM-enabled IoT devices to achieve broader scalability and flexibility in deployments.
SGP.31 requires coordination with SGP.21 (the broader eSIM specification) to ensure complete remote provisioning, while SGP.32 operationalizes the framework set out by SGP.31 through specific implementation guidelines. Learn more about:
From eSIM M2M to new eSIM IoT Specification: Key Benefits
The distinct requirements of connected devices in long-term applications are driving the transition from older machine-to-machine (M2M) eSIM standards to the most recent IoT specifications, such as SGP.31/32.
Unlike consumer electronics with short lifespans, many industrial IoT devices, such as those in energy or logistics, are expected to operate for a decade or even two. This longevity requires a more flexible solution. The older M2M specifications require SMS or HTTPS for profile delivery, which is difficult for memory-restricted LPWAN devices. Profile delivery refers to the process of remotely installing and managing SIM profiles (operator credentials) on an eUICC. Furthermore, managing worldwide deployments is made more complex by the interaction between SM-SR (Subscription Manager-Secure Routing, responsible for securely delivering profiles) and SM-DP (Subscription Manager-Data Preparation, responsible for encrypting and preparing profiles for download) and the requirement that SM-SR must be pre-configured at the eUICC manufacturing stage.
The major improvement in the new specifications is the introduction of a simplified IoT Profile Assistant, or IPA. It is designed to manage local profiles and comes in two forms: one directly on the eUICC, and the other within the IoT device itself. Regardless of its location, the IPA interacts seamlessly with the remote management systems, which enables more efficient profile switching.
"The introduction of the IoT Profile Assistant and eSIM IoT Manager marks a turning point for massive IoT. We’re no longer forcing outdated M2M workflows onto low-power devices; instead, we’re enabling smarter, more flexible provisioning for the cellular IoT era." - shares Fabian Kochem, Director of Product Strategy at 1NCE.
At the same time, eSIM IoT Manager (eIM), which standardizes provisioning and remote management of eSIM-enabled IoT devices. The eIM eliminates pre-negotiation between components, allowing seamless communication with any IoT device or SM-DP+. Unlike SM-DP, which is used in M2M environments and requires pre-configured settings, SM-DP+ is designed for consumer and IoT use cases, enabling dynamic profile downloads without prior coordination. It also supports flexible configuration at any stage, from manufacturing to deployment, ensuring adaptability to regulatory requirements.
Another improvement directly addresses a common challenge faced by manufacturers. Traditionally, MNOs would issue eSIM profiles without knowing the precise location or intended use of the device. However, with the new remote management capabilities with provisioning techniques, they can now customize eSIM profiles in the moment they are linked to the device. This ensures the correct connectivity settings for the device deployment.
Now OEMs can launch one single version of their devices and remotely set it for versatile networks, reducing production and logistics costs, and simplifying supply chains. SGP.32 further improves connectivity for resource-constrained devices, such as sensors, trackers, and smart meters, supporting lightweight protocols like CoAP/UDP and WiFi/Bluetooth profile downloads. Furthermore, the convergence of industrial and consumer IoT provisioning mechanisms allows traditionally industrial devices to adopt connectivity features which used to be limited to consumer applications, such as multi-IMSI roaming for better overall integration and scalability.
Feature | Description | eSIM M2M | eSIM IoT |
eUICC | The physical integrated circuit within devices that enables remote SIM provisioning. The handling of eUICC profiles varies for M2M and IoT applications. | + | + |
RSP | Functionality to provision SIM cards remotely. | + | + |
SM-SR | Manages the secure handling of eUICC profiles through encrypted communication. | + |
|
IPA | Facilitates profile switching and connects device or eUICC communications with management systems. |
| + |
eIM | Manages profile status across a single IoT device or a group of devices. |
| + |
Difference between SGP.21/22 and SGP.31/32
SGP.21/22 and SGP.31/32 are two sets of GSMA specifications related to eSIM (embedded SIM) technology; nevertheless, they have distinct functions and pertain to distinct kinds of devices. They are in fact complimentary, with SGP.31/32 increasing the scope of SGP.21/22's application to the larger Internet of Things (IoT) ecosystem and building upon its foundation. Below is a summary of their main distinctions:
Standards | SGP.21/22 | SGP.31/32 |
Hardware | Consumer devices (e.g., wearables) and advanced M2M/IoT devices (e.g., connected cars) | IoT devices with limited resources (e.g., sensors and trackers) |
Resource Requirements | Higher resource availability (memory, processing power, user interface) | Resource-constrained devices (low power, no UI, limited memory) |
Coverage | Primarily aimed at regional SIM solutions | Aimed at global deployments with multi-IMSI support |
Connectivity | Devices with stable network connections, often with constant or high bandwidth | Network-constrained devices, including those with low-bandwidth connections |
Protocols | HTTP, TCP, TLS for higher-capacity devices | CoAP/UDP, DTLS for LPWAN for low-power and resource-constrained use cases |
Use Cases | Consumer IoT, industrial IoT, M2M | Large-scale IoT deployments, including smart cities, fleet management, utilities, and industrial IoT |
Provisioning | eSIM provisioning for consumer and high-end M2M devices with more complex connectivity options (e.g., broadband, user interfaces). | Remote provisioning for mass deployments of IoT devices with minimal resources and flexible connectivity |
Coverage | Primarily aimed at regional SIM solutions | Aimed at global deployments with multi-IMSI support |
Remote Management | Less emphasis on large-scale remote management | eSIM IoT Remote Manager (eIM) for managing large numbers of devices remotely |
Impact of SGP.31/32 on Industries
The potential impact of SGP.31 and SGP.32 extends across multiple sectors:
Industry | Impact of SGP.31/.32 |
Smart Cities | Simplifies eSIM provisioning for resource-constrained devices like smart streetlights and sensors across large urban projects. |
Logistics | Fleet management systems can remotely configure devices like GPS trackers and telematics, reducing the need for region-specific SIMs and supporting global roaming. |
Utilities | Allows utilities to manage devices remotely, improving operational efficiency by handling large-scale deployments across diverse geographical areas. |
Industrial IoT & Manufacturing | Reduces integration complexity, making it easier to scale systems like predictive maintenance sensors and factory monitoring systems in industries such as automotive and electronics. |
Consumer IoT | Facilitated connectivity and multi-IMSI roaming, which is critical for products like smartwatches, which require seamless connectivity across different regions. |
Summing up
The GSMA's SGP.31 and SGP.32 specifications represent a significant leap forward in addressing the unique challenges of large-scale IoT deployments. The introduction of the IoT Profile Assistant (IPA) and the eSIM IoT Manager (eIM) streamlines operations, while broader protocol support and global compatibility help manufacturers to deploy large scale projects across diverse networks. SGP.31/32 not only bridge the gap between industrial and consumer IoT but also pave the way for more scalable, adaptable, and cost-effective IoT solutions across various industries, from smart cities and logistics to utilities and manufacturing.