IoT Explained
13 March 2025
Reading Time: 5 mins
Eseye
IoT Hardware and Connectivity Specialists
LinkedInThe GSMA’s eSIM for IoT Technical Specification, otherwise known as SGP.32, is expected to become a reality as early as 2025. As the next evolution in eSIM technology designed to enhance remote SIM provisioning and management across diverse IoT ecosystems, enterprises and mobile network operators (MNOs) see SGP.32 as a panacea for deploying and managing IoT devices at scale with greater flexibility, security, and efficiency.
Understanding the SGP.32 eSIM standard
Large scale IoT deployments require more advanced management platforms and eSIM solutions that facilitate seamless integration of devices, networks and applications.
The GSMA’s SGP.32 specification, now expected to be deployment-ready later this year (2025), significantly reduces the complexity of switching between profiles on eSIM and introduces highly scalable Remote SIM Provisioning (RSP) for IoT.
This boost to interoperability – making it easier to choose and switch IoT connectivity providers – paves the way for the activation of billions of new IoT connections globally over the next four years, according to analysts at Omdia.
IoT has special requirements that differ from consumer cellular services, and there has been a gradual shift from the use of generic networking platforms and consumer-focused SIMs to purpose-built and specialist solutions for IoT.
The SGP.32 standard was originally unveiled by the GSMA in 2023, to deliver exactly this – a more streamlined and effective mechanism to manage IoT connectivity. The stable version, SGP.32v1.2, was published in June 2024.
SGP.32 is an evolution on the SGP.02 standard intended for M2M, and the SGP.22 consumer-focused standard, and represents several steps forward for IoT estate management, resolving many of the technical limitations on supporting constrained devices and offering a simplified mechanism for handling switch-over of connections between operators.
Remote SIM Provisioning (RSP) explained
Before the development of RSP, the only ways to change the network operator profile associated with a SIM was by having physical access to the device and swapping the hardware SIM card; or for multi-IMSI (International Mobile Subscriber Identity) SIMs, to switch to an alternative pre-loaded SIM profile.
Neither of these options are particularly useful in the case of IoT deployments, which could see tens or hundreds of thousands of connected devices in unreachable locations and needed intensive logistical management.
As a result, the GSMA’s releases of standards for global specifications for eSIM, including capabilities for RSP OTA, have specifically addressed the requirements for M2M and IoT devices with evolutions through to SGP.32.
How SGP.32 enhances IoT connectivity for MNOs
- Remote UI: The remote user interface (UI) in SGP.32 is a feature that allows remote control of the IoT Profile Assistant (IPA). This is achieved by making the role of the Local Profile Assistant (LPA) partially on the device as the IPA and partially hosted by the network operator or third party management system in the form of the eSIM IoT remote Manager (eIM). This allows for the remote control of the IPA.
The LPA is a software interface on devices using eSIM that facilitates the downloading, installation, and management of eSIM profiles. LPA can be used to switch carriers or activate a new eSIM profile. - Support for lightweight protocols: Such as CoAP-based Lightweight M2M (LwM2M) to manage profile downloads and other operations while overcoming constraints on latency and bandwidth which are common with some IoT connectivity technologies.
- No requirement for SMS: SMS was required for SGP.22 but isn’t widely used by many NB-IoT devices.
- A small footprint: Because much of the functionality of the LPA has been moved into the eIM it reduces the memory and processing requirements on the device itself.
SGP.32 solves many of the problems with earlier standards that prevented IoT devices being effectively managed remotely.
Much of this is due to the adoption of IPA. Instead of an LPA which the connectivity manager would use directly to initiate profile changes, it incorporates an IPA sitting on the device that is controlled by an eIM which is hosted by a network operator or other third party such as an IoT connectivity specialist like Eseye.
Using this eIM, the manager of the IoT estate would be able to pull a profile from any MNO/MVNO to the device. The big change with SGP.32 is that it allows the device’s profile to be changed without requirement for integration between donor and recipient platforms/networks or the agreement of the current provider.
Adoption of SGP.32
Analysts at Transforma Insights expect SGP.32 to ultimately become the dominant Remote SIM Provisioning technology, with over 2.3 billion cellular connections expected to be eUICC/RSP capable in 2032.
But the journey might not be so easy as many claim or expect, especially when it comes to solving all the challenges of deploying multi-country and multi-operator connectivity.
Even with commercial relationships with multiple network operators in place, it’s not simply a case of switching between providers seamlessly. The way in which connections are supported will vary from network to network with many settings not specified by the standard that will not automatically carry over from one network to another.
There will also be a requirement for back-end integration with management platforms for process changes to things like APN settings, setting the polling frequency for new eSIM profiles, and device security.
Finally, because SGP.32 is not actually available today and likely won’t be until later 2025, any business looking to deploy IoT imminently will need an alternative solution with a migration path for when the time comes.
Expertise in SGP.32 implementation
Transforma Insights recommends that rather than trying to deploy SGP.32, or any IoT connectivity solution yourself, it makes more sense to work with established connectivity providers able to provide the transition, orchestration, and MNO management functions required.
A specialist third party, such as Eseye, will be able to handle the heavy lifting of negotiating contracts and managing connectivity as well as orchestration of the whole SIM lifecycle management. And, notably, will likely be in a better position to negotiate favourable rates for that connectivity.
Eseye has designed its Integra eSIM orchestration (eSO) platform to enable you to take control of your customer accounts by providing the ability to deploy and manage IoT without limitations. Integra supports remote SIM provisioning (RSP) for SGP.02, SGP.22 and SGP.32 standards.
As well as the eSIM management function, Eseye can offer the orchestration of all the other elements of supporting the user’s IoT connections, including managing data flows, device middleware, security, and compliance.
Finally, just because SGP.32 is the latest does not mean it is the greatest. A specialist partner like Eseye will help you understand what is best for the device and the application, rather than what is ‘the best connectivity technology’.
For some companies, SGP.32 may be the correct answer, but it won’t be for others. The optimum approach is to select a provider that can offer it as part of a broader portfolio of offerings.
Eseye
IoT Hardware and Connectivity Specialists
LinkedInEseye brings decades of end-to-end expertise to integrate and optimise IoT connectivity delivering near 100% uptime. From idea to implementation and beyond, we deliver lasting value from IoT. Nobody does IoT better.
In this article
Be Ready for SGP.32
There is no magic wand to adopt and seamlessly migrate your IoT to SGP.32. Get expert advice, practical steps and the strategic recommendations you need to transition.
Download whitepaper