eSIM

An eSIM is a downloadable operator profile stored on an embedded chip, not a plastic card. Consumer devices use SGP.22 and IoT devices use SGP.32.

Definitions only — a term explained here is not a service we sell.

An eSIM is a profile stored on the eUICC inside a device, not the chip itself. The profile downloads from an SM-DP+ server once the device validates an activation code.

SGP.02 modules cannot move to SGP.32 over the air; the hardware cycle decides.

From device to subscription

  1. Device
  2. eUICC
  3. Profile
  4. Subscription
Four layers from device to subscription; the subscription is highlighted.
Text description

The four layers run from the device through the eUICC and the profile to the subscription. The eUICC is the secure element that stores the profile. The profile carries an operator's credentials. The subscription is the highlighted layer.

How a profile arrives

The device validates an activation code and contacts an SM-DP+ server to download the profile. A discovery service (SM-DS) can also signal that a profile is waiting. What is eSIM covers the full path.

Consumer and IoT split

Consumer devices follow SGP.22 and use an app. IoT devices follow SGP.32, which adds an eIM that manages profiles without a user interface. Confirm the specification family the device implements, whether it is GSMA-certified and whether a local profile assistant is present.

FAQ

Is an eSIM the same as a virtual SIM?

No. An eSIM is a downloadable profile on a hardware eUICC; a virtual SIM or number is a service abstraction with no secure element.

Can an eSIM profile move to another device?

Usually not by copying it. The profile is bound to the eUICC, so a new device needs a new download, subject to the operator's rules.

Which specification should an IoT fleet use?

SGP.32, when devices are constrained and need remote management without a person at the device.

Learn more

Sources

  1. GSMA: eSIM technology, consumer, M2M and IoT specifications
  2. GSMA SGP.32: eSIM IoT technical specification