What is SGP.32 and what changed in 2026?
The GSMA publishes the eSIM specifications used across the mobile industry. Two of them cover IoT devices such as routers, sensors, trackers and cameras:
| Specification | Purpose | Versions listed by the GSMA |
|---|---|---|
| SGP.31 | eSIM IoT architecture and requirements | V1.0 (April 2022) to V1.3 (22 May 2026) |
| SGP.32 | eSIM IoT technical specification | V1.0.1 (4 July 2023), V1.1 and V1.2 (2024), V1.3 (22 May 2026) |
| SGP.22 | Consumer eSIM, as used in phones and wearables | Several active versions, most recently V2.7 (April 2026) |
SGP.31 defines the requirements for remote provisioning and management of eSIMs in IoT devices that are network constrained, with limited bandwidth or protocol options, or user interface constrained, with little or no screen for managing profiles. The GSMA lists versions 1.2 and 1.3 of both IoT specifications as active, which means they can be used to implement or test products.
The practical point for event and temporary site planners is that the standard now has several published revisions, and industry reporting in 2025 described certified platforms and devices starting to reach the market, with broader adoption expected through 2026.
How does eSIM for IoT work?
An eSIM is a secure chip in the device, called an eUICC, that can hold one or more mobile network profiles. The IoT specification adds two roles that suit devices without a screen:
- eSIM IoT Remote Manager (eIM): the system responsible for profile state operations on a single device or a whole fleet, such as enabling, disabling or deleting a profile.
- IoT Profile Assistant (IPA): the function in the device or in the eSIM that handles profile downloads, discovery and notifications.
A profile is downloaded from the provisioning server and installed in a disabled state. When the remote manager sends a signed request to enable a different profile, the eSIM checks that the request comes from its associated manager, then disables the current profile and enables the new one.
SGP.31 also describes an optional fallback mechanism. If the enabled profile loses network connectivity, the eSIM can enable a profile marked as the fallback profile. A device can hold at most one fallback profile, and only where the profile owner allows it.
Why does this matter for event routers, terminals and cameras?
Temporary networks rely heavily on mobile data. A 4G or 5G router might serve a market, a marquee or a site office for a weekend, then move to a different suburb the following week. Remote provisioning helps in several ways:
- Fewer SIM swaps on site: changing networks no longer requires opening a router, terminal or camera housing, which is useful for sealed outdoor enclosures and cameras mounted on poles.
- Matching the network to the site: if a pre-event survey shows one network is weak at a particular venue, a profile can be switched before the equipment ships rather than swapping physical SIMs.
- Fleet management: one manager can see and change profiles across many devices, which suits equipment that rotates between events.
- A last-resort path: where configured, the fallback profile gives a device a way back online after its main network fails.
These benefits apply to the equipment we use for 4G and 5G router hire and temporary CCTV installation, as well as card terminals with built-in mobile data.
What does eSIM for IoT not solve?
Remote profile switching is a management improvement, not a reliability fix on its own. Planners should keep these limits in mind:
- One connection at a time: enabling a new profile disables the current one, so a single eSIM module switches between networks rather than using two at once. Expect a short interruption while the device reconnects.
- Fallback reacts after a failure: it starts once connectivity is lost, so payments or a live stream on that device may still drop for a period.
- Coverage still decides performance: a profile on a network with poor signal at the venue does not perform better because it was delivered remotely. A site survey is still the starting point.
- Device support varies: older devices may use earlier machine-to-machine or consumer approaches. Check whether a device supports the IoT specification before relying on it.
- Profiles depend on agreements: which networks can be loaded depends on the arrangements behind the remote manager, not only on the standard.
For payments and live streams, true resilience still means two independent paths, such as two separate mobile connections in different devices, or a wired service plus mobile. Our backup internet page explains how we set this up.
How should event and site planners use it?
- Ask what the devices support. For routers, terminals and cameras, ask whether they use a removable SIM, a consumer eSIM or an IoT eSIM, and who manages the profiles.
- Survey before choosing a network. Test signal and upload at the actual positions where equipment will sit, at a similar time of day to the event. Our site survey and coverage planning service covers this.
- Switch profiles before the event, not during it. Plan any change during bump-in so the interruption does not affect trading or a stream.
- Keep critical services on two paths. Use eSIM flexibility as one layer of resilience, not the only one.
- Document the setup. Record which profile each device uses, the fallback arrangement and who can change it on the day.
Our guide to temporary internet options in Australia compares mobile, fixed and other connection types for short-term sites.
How can we help plan mobile connectivity for temporary sites?
We plan and supply temporary internet for events, markets, construction sites and pop-up offices across Sydney, combining mobile connections with separate networks for payments, streaming, staff and guests. We choose connections based on testing at the site rather than coverage maps.
If you are planning an event or temporary site, send us the address, the dates and the list of devices that need to connect through our contact page, and we will suggest a connection and backup plan. You can also read about our temporary internet service.
Questions people ask
What is SGP.32?
SGP.32 is the GSMA eSIM IoT technical specification. It works with the SGP.31 architecture to let a remote manager download, enable and switch mobile network profiles on IoT devices that have limited networks or no user interface.
When was the latest version of SGP.32 published?
The GSMA eSIM specification page lists SGP.32 version 1.3, dated 22 May 2026, alongside SGP.31 version 1.3 from the same date. Version 1.2 from June 2024 is also listed as active.
Can an eSIM router use two mobile networks at once?
A single eSIM module enables one profile at a time. Enabling a new profile disables the current one, so for simultaneous connections you need two separate modules, devices or links.
Does eSIM for IoT remove the need for a site survey?
No. Remote provisioning changes how a network is selected, not how well it performs at the venue. Signal and upload still need to be tested at the actual equipment positions.
What is the eSIM fallback profile?
It is an optional feature in SGP.31. If the enabled profile loses connectivity, the eSIM can enable a designated fallback profile. A device can hold at most one, and only with the profile owner's permission.
Sources
- GSMA: eSIM specifications (SGP.22, SGP.31, SGP.32 versions)
- GSMA: SGP.31 v1.3 eSIM IoT Architecture and Requirements Specification
- GSMA: IoT RSP, enabling the growth of massive IoT
- RCR Wireless: A new era for cellular IoT eSIM (June 2025)
Event dates, prices and product details can change. Check the organiser or manufacturer before you plan around them. Planning figures are starting points; every network is confirmed against the actual site.