Transforma Insights has released its free Transition Topic Position Paper, sponsored by Eseye, titled ‘Key considerations for Enterprises looking to adopt SGP.32’. The SGP.32 (IoT) standard for Remote SIM Provisioning, introduced in May 2023, aims to provide a more efficient and user-friendly way for enterprises to manage connectivity on their cellular devices.
However, as outlined in the report, it is not a simple solution for providing seamless access to every network. The reality is more complex.
The main findings of the report are:
- SGP.32 as a standard will be widely adopted: As an evolution of the previous SGP.02 (“M2M”) and SGP.22 (“Consumer”) standards, SGP.32 (“IoT”) addresses many technical limitations, particularly in supporting constrained devices and simplifying the switch-over of connections between operators. However, this is only part of the picture
- True SGP.32 capability will be available from 2025: Current SGP.32 solutions are not based on fully interoperable standards, and pre-standard versions will have limited appeal due to the lack of universal support
- SGP.32 does not resolve all challenges of deploying multi-country IoT connectivity: Commercial contracts must still be negotiated with network operators, and back-end processes and settings must be updated to reflect a change of connectivity provider. It is not as simple as switching from operator A to operator B
- SGP.32 will generally need to be offered as a managed service: Few enterprise customers will manage SGP.32 functionality themselves. Thus, it will likely be accessed via an orchestration layer provided by connectivity providers, and offered as part of a range of options including roaming, multi-IMSI, and SGP.02
- A roadmap to SGP.32 is required for implementation today: Since the technology will not be available for deployment until 2025, potential users will need to use alternatives (such as SGP.02) and rely on a connectivity provider for a seamless migration
Commenting on the report, author Matt Hatton said: “The SGP.32 standard has a lot to recommend it. It irons out many of the creases from the prior standards. However, there is a very significant risk with SGP.32 that the real (and perceived) benefits will blind enterprises to the realities of the intricacies of managing the overall IoT solution deployment and the requirements for a migration path to get there.”
“Enterprises still have a lot of key considerations to make before deciding how and when to adopt SGP.32. The transition will take time and there are many factors to take into account to deliver 100 percent global connectivity,” added Nick Earle, CEO of Eseye. “With Eseye’s deep understanding of the RSP landscape, we know how important it is, as underlined in Matt’s report, to offer customers a choice of SGP.02 as well as SGP.32. Plus a managed service to help with the transition, orchestration, and MNO management as soon as the GSMA ratifies the SGP.32 standard.”
There’s plenty of other editorial on our sister site, Electronic Specifier! Or you can always join in the conversation by commenting below or visiting our LinkedIn page.
