Netflix’s 3 Body Problem has put an old bit of physics back into everyday conversation. Two bodies pulling on each other settle into a neat, predictable orbit. Add a third and there’s no tidy general solution: the system swings between calm stretches and chaos. The more time I spend on SGP.32, the more it looks like the same problem, and I think that explains most of what’s happening in IoT eSIM right now.
This is the last part of our four-part series. We’ve covered eSIM vs eUICC, what an eUICC is and what an eIM is. This one pulls it together: where SGP.32 stands in November 2026, who’s doing what, why one standard has produced so many different answers, the other terms you need, and a first look at why it matters for OT security.
The short version. SGP.32 is the GSMA’s eSIM standard for IoT devices with no user. Three parties have to line up for it to work: whoever controls the chip, whoever runs the eIM, and whoever supplies the operator profiles. When one company owns all three, it works smoothly and you’re locked in. When three different companies own them, you get the freedom SGP.32 promised, plus the integration work. Most of the market today sits somewhere in between.
The three bodies of SGP.32
Strip out the acronyms and every SGP.32 deployment has three centres of gravity, with your device caught in the middle.
- The chip is the eUICC, its operating system and the bootstrap profile loaded at the factory so the device can connect out of the box. Whoever owns that bootstrap profile decides how your device first gets online.
- The control is the eIM, which decides which profiles a device holds and which is enabled, and signs the instructions.
- The networks are the operator profiles, prepared on each operator’s SM-DP+. A profile only exists for your chip if an operator has agreed to supply one.
The standard describes how the three talk to each other. It doesn’t say who should own them. That gap is where every commercial model in this market lives.
Where SGP.32 stands in November 2026
| When | What happened | Why it matters |
|---|---|---|
| May 2023 | GSMA publishes the first version of SGP.32 | IoT gets its own eSIM standard, separate from M2M and consumer |
| June 2024 | SGP.32 v1.2 published | Still the version the certification tests are built around |
| October 2024 | Kigen launches what it calls the first market-ready SGP.32 v1.2 eIM | The control layer becomes something you can buy |
| February 2025 | SGP.41 v1.0 published, the architecture for in-factory profile provisioning | A second route: load the operator profile on the production line |
| March 2026 | IDEMIA Secure Transactions, Tele2 IoT and Cisco launch an end-to-end SGP.32 service | Chip, network and platform players start packaging it together |
| April 2026 | Telenor IoT starts commercial delivery of SGP.32 SIMs; Eseye adds SGP.32 to its platform | Operators and specialists move from pilots to products |
| May 2026 | SGP.31 and SGP.32 v1.3 published | The standard keeps moving while test specs stay on v1.2 |
| September 2026 | Onomondo launches an eIM it says works without its own connectivity | The control layer starts separating from the network |
| Still open | SGP.42 (in-factory technical spec) in development; device-side certification still catching up | The middle of the chain is where the work is left |
For the device side of that story, see the SGP.32 readiness chain, and for the UK and European picture earlier in the year, SGP.32 in mid-2026.
Five ways the industry is tackling it
Give the same three-body problem to different companies and each settles on the orbit that suits its business. Here’s how I’d group what’s on offer.
| Approach | Typical players | What you get | Where the lock sits |
|---|---|---|---|
| Chip-led | eUICC and SIM OS vendors running their own eIM and services | A tightly tested stack from silicon up | In the chip OS and whoever owns the bootstrap |
| Connectivity-led | Operators and IoT connectivity specialists with their own eIM and bootstrap | One supplier, one contract, one support desk | In the eIM and the commercial relationship |
| Separate eIM | eIMs sold independently of connectivity, open-source implementations, enterprise-run eIMs | The most freedom to mix networks and change suppliers | Moves to you: more integration and responsibility |
| Control layer on top | Orchestration platforms working across several eIMs and operators | One view across a mixed estate | In the orchestration platform |
| In the factory | In-factory provisioning under SGP.41, with SGP.42 to follow | Devices leave the line already on the right operator | In the production-line decision; you still need SGP.32 for later changes |
There’s also a sixth answer, which is to sidestep the problem. A multi-network IoT SIM that roams across many networks on a single profile already does the job for a lot of UK fleets, and some providers sell both. As I said in part two, not every device needs an eUICC.
Why one standard gives so many answers
People sometimes ask how a single GSMA standard can lead to such different products. I think there are five reasons.
- It defines roles, not owners. SGP.32 says what an eIM, an IPA and an SM-DP+ must do. It doesn’t say who runs them, and that’s a commercial decision.
- It has options. The IPA can live on the chip or on the device. Profiles can be downloaded directly by the device or indirectly through the eIM. Messages can travel over HTTPS or CoAP. Two compliant products can make different choices and still not work together out of the box.
- It has versions. v1.0, v1.2 and v1.3 aren’t fully interchangeable, and some early implementations were built to versions that never reached production.
- Certification isn’t finished. The eUICC and the eIM can be certified today. The device in the middle is still catching up.
- Profiles need contracts. The standard can deliver any operator’s profile to any certified chip. Whether that operator will supply one for your device is down to agreements, not technology.
The other SGP.32 terms you need to know
You can follow most conversations about IoT eSIM with the three terms from this series: eSIM, eUICC and eIM. These are the rest.
| Term | What it means |
|---|---|
| SGP.31 / SGP.32 | The GSMA’s IoT eSIM architecture (SGP.31) and technical specification (SGP.32) |
| SGP.02 / SGP.22 | The earlier M2M and consumer eSIM standards |
| SGP.33 | The test specifications used to certify SGP.32 products |
| SGP.41 / SGP.42 | In-factory profile provisioning (IFPP): architecture and technical spec |
| EID | The eUICC’s permanent identity number, which stays the same whatever profiles it holds |
| ICCID | The identity of each individual profile on the chip |
| Bootstrap profile | A profile loaded at the factory so the device can connect and fetch its proper profile |
| Operational profile | An operator profile used for normal service |
| Fallback | A profile marked to take over if a switch leaves the device without service |
| IPA (IPAe / IPAd) | IoT Profile Assistant, the go-between on the eUICC (IPAe) or on the device (IPAd) |
| SM-DP+ | The operator-side server that prepares and encrypts profiles for a specific chip |
| SM-DS | A discovery server a device can check for pending profile downloads |
| PSMO | Profile state management operation: enable, disable or delete a profile |
| eCO | eIM configuration operation: add, update, delete or list the eIMs a chip trusts |
| eUICC package | A signed bundle of PSMOs or eCOs from the eIM, checked by the chip before it acts |
| ESipa | The interface between the eIM and the IPA |
| BIP | Bearer Independent Protocol, which lets an IPAe ask the modem to open a data connection |
| LPA / SM-SR | The consumer profile assistant (SGP.22) and the M2M subscription manager (SGP.02) |
| eSA | The GSMA’s eUICC Security Assurance scheme |
| iSIM / ieUICC | A SIM built into the modem chipset rather than a separate chip |
For the definitions in more depth, our sister sites sgp32.co.uk and euicc.co.uk go term by term, and our IoT eSIM glossary entry is a good place to start.
My take: where we are now
In the novel, the people living with three suns go through long stable eras and sudden chaotic ones, and they never quite manage to predict which is coming. I think IoT eSIM is in one of its in-between periods. The standard works. Devices have been moved between providers over the air in live tests and early commercial services. But most fleets still get their stability the old way, by letting one supplier own all three bodies.
That’s not a disaster. For plenty of businesses it’s the right call: one contract, one throat to choke, and a product that works. The mistake is buying that package while believing you’ve bought freedom. If one company owns the chip’s bootstrap, the eIM and the profiles, you have a well-run lock-in with an SGP.32 badge on it.
The next stable era will come when the device side is certified routinely, when eIM handovers between competitors are something people have done rather than something they promise, and when adding an operator profile is a menu choice rather than a project. My guess is that we’re two or three years away from that being normal, and the vendors who make handover easy will win more business than the ones who make it hard.
Coming next: SGP.32 and OT security, help or risk?
Over the coming month we’re running a series on cellular OT security: the routers, SIMs and connections sitting in cabinets at pumping stations, substations, solar farms and car parks. SGP.32 will be part of it, because it cuts both ways.
| Where SGP.32 can help | Where it adds risk |
|---|---|
| Identity held in a certified, tamper-resistant chip | The eIM is a new control plane with authority over every connection in the fleet |
| A soldered eUICC can’t be pocketed from a cabinet and used elsewhere | One compromised console could disable profiles across thousands of sites at once |
| A fleet can be moved off a failed or compromised network without site visits | A profile switch can change IP addressing and APN, breaking firewall rules, VPNs and private APN isolation |
| Fallback profiles reduce the risk of stranding a device after a change | An IPA on the device is more code that needs patching for the life of the product |
| Local profiles can keep data in-country | Unclear approval: who is allowed to change a site’s connectivity, and is it logged? |
None of that is speculative. The GSMA’s own SGP.31 architecture includes a threat annex covering a compromised IoT device, a compromised eIM and a malicious eIM. A formal security analysis of SGP.32 provisioning has also appeared on the IACR preprint server under the title “Removing the Human, Keeping the Doors Unlocked”, which tells you where the researchers’ attention went. I’ll go through both properly in the series.
One thing to do now. If you run, or are planning, SGP.32 devices on an OT network, find out who can send a profile change to them, how that person logs in, and whether anyone would notice if a site switched network at three in the morning. If nobody can answer, that’s your first finding.
In the meantime, who secures the router in the cabinet? and our OT security audit guide set the scene.
SGP.32: quick answers
What is SGP.32?
SGP.32 is the GSMA’s eSIM technical specification for IoT devices without a user interface. It lets operator profiles be downloaded, enabled, disabled and deleted remotely, under the control of an eSIM IoT Remote Manager (eIM).
What is the latest version of SGP.32?
SGP.32 v1.3 was published in May 2026, alongside SGP.31 v1.3. The certification test specifications are still aligned to v1.2.
Who provides SGP.32 services?
eUICC vendors, mobile operators, IoT connectivity specialists and independent platforms all offer SGP.32 services. Some bundle the chip, eIM and connectivity together; others sell the eIM separately so you can mix networks and suppliers.
Does SGP.32 remove vendor lock-in?
It removes the technical barrier to changing operator, but not the commercial one. Lock-in can move to whoever owns the bootstrap profile or the eIM, so check how a handover to another eIM works before you buy.
Is SGP.32 a security risk for OT?
It can help OT security through chip-based identity and remote recovery, but it also introduces the eIM as a powerful control plane. Protect who can change profiles, test what a switch does to IP addressing and firewall rules, and log every change.
Sources: GSMA, eSIM specifications status table; GSMA, SGP.32 v1.3 and SGP.31 v1.3 (May 2026), including SGP.31 Annex A, threats and risks; GSMA, SGP.41 IFPP Architecture and Requirements v1.0 (February 2025); CSL, eSIM, eUICC and iSIM technical guide (SGP.42 status); Alertify, SGP.32 in 2026 (Kigen eIM, Telenor); TelecomDrive via Pulse, IDEMIA, Tele2 IoT and Cisco; Eseye, April 2026 announcement; Onomondo, eIM product update (September 2026); IACR ePrint 2026/2020. Diagram by IoTPortal.
The eSIM explained series: Part 1: eSIM vs eUICC · Part 2: What is an eUICC? · Part 3: What is an eIM? · Part 4: SGP.32’s three-body problem (you are here)



