eSIM architecture

Which eSIM model actually fits what you're building.

A phone with a screen, a machine with no interface, and a fleet of meters in the ground each need a different remote provisioning model. SGP.02, SGP.22 and SGP.32 are not interchangeable, and picking wrong is expensive to undo. Advice, architecture and review. Not a provisioning platform.

Quiz

Which architecture fits this deployment?

Four questions. A starting point at the end, then we refine it with you.

FAQ

eSIM questions

What is the difference between SGP.02, SGP.22 and SGP.32?

They are GSMA eSIM architectures for changing operator profiles without swapping a physical SIM. SGP.22 is consumer eSIM (phones, tablets). SGP.02 is classic M2M remote provisioning. SGP.32 is the IoT evolution: more standardised remote control, less lock-in to a single SIM vendor at manufacture, activation code or QR style flows, and no hard dependency on SMS as the only bearer.

Who controls the eSIM profile — LPA or eIM?

SGP.22: the device, through an LPA (Local Profile Assistant) — typically the user or device UI. SGP.32: an eIM (eSIM IoT Remote Manager) drives an IPA (IoT Profile Assistant). The IPA may sit on the device (IPAd) or inside the eUICC (IPAe). Same family of ideas as consumer QR/activation codes, different who is in charge.

What do people mean by “SGP.22” vs “SGP.32” in practice?

SGP.22 usually means the downloadable consumer profile — often installed with a QR. SGP.32 may mean the static part (chip + OS + IPA) or the downloadable profile. The profile payloads themselves are similar; the chip OS and control path are where the architectures diverge.

Can you use an SGP.22 profile QR on an SGP.32 chip?

Often yes in practice, because the profile formats are close — but confirm with the chip vendor and the exact OS build. Compatibility is about the OS and IPA path, not only the QR string.

After an eSIM profile is active, how does day-to-day OTA work?

The card behaves like a normal SIM for campaign OTA: SCP80 / SCP81, RFM, RAM. MoreOTA sits on that layer. It does not download eSIM profiles; choosing SGP.02 / .22 / .32 is a separate architecture track.

Contact

Tell me what you need to change.

Architecture selection, vendor evaluation, RFP wording, chip/OS compatibility.