Question 1

What is an eUICC SIM card and how does it work?

Accepted Answer

Basically, there is no such thing as “the one eUICC SIM card.” eUICC is a software component provided on an M2M SIM card. It allows users to manage a network operator profile remotely (Remote SIM Provisioning, RSP). This includes activating, deactivating, or deleting it.

In theory, this software can be deployed on any type of M2M SIM—whether on physical SIM cards or on an eSIM, a SIM chip soldered directly into the device that eliminates the need for a physical plastic SIM card. However, it cannot be loaded onto an M2M SIM card after the fact. The new eUICC standard SGP.32 is particularly interesting for IoT applications with permanently embedded SIM chips or eSIMs.

Question 2

How do I manage my SIM profile(s) on the eUICC?

Accepted Answer

To manage eUICC profiles on a SIM card, users need an online portal or an API. In the past, every mobile network operator whose SIM profiles were to be used had to be connected to and integrated with this portal or API. Because of this significant effort, the cost of eUICC SIM cards was very high in the past.

With current and future eUICC standards, managing mobile network profiles for IoT applications is becoming increasingly simple and flexible. As a result, companies benefit from more efficient device management and can design their IoT deployments for the long term, independent of individual network operators.

The specific features and capabilities depend on the eUICC solution used and the supported standards.

‍

Question 3

What costs are associated with eUICC IoT SIM cards?

Accepted Answer

The cost of eUICC IoT SIM cards consists of several components. These include the SIM card or eSIM itself, the provision and management of mobile network profiles, and the ongoing costs for the data plans used.

Compared to traditional IoT SIM cards, eUICC solutions may involve additional costs, depending on the use case. At the same time, however, they offer significantly more flexibility, as mobile network profiles can be managed remotely and changed as needed.

The actual costs depend on factors such as the number of units, the application area, the selected network operator, the pricing model, and the required management functions. We would be happy to provide a customized quote for your project.

Question 4

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

Accepted Answer

SGP.22 is the eSIM standard for consumer devices such as smartphones. It is based on user interaction (e.g. QR code scanning), relies on a simplified architecture model (SM-DP+) and was developed for devices with a display. SGP.32, on the other hand, addresses the special requirements of IoT: there is no longer any dependency on SMS, profiles can be downloaded via both push and pull, and new roles have been introduced with eIM and IPA, which enable flexible, scalable operation of IoT fleets.

Question 5

Is SGP.32 backwards compatible?

Accepted Answer

No, SGP.32 is not backwards compatible. Devices with SGP.02 (M2M) or SGP.22 (consumer) cannot be upgraded to SGP.32 via a software update, as the architecture and roles are different. For existing fleets, this means that they continue to run with the standard for which they were built. It is better to plan new IoT projects with the new eSIM IoT standard SGP.32 from the outset in order to be future-proof.

Question 6

How secure is the new eSIM standard?

Accepted Answer

SGP.32 offers a higher level of security than its predecessors. All profile operations (e.g. activation, deactivation, deletion) run as so-called Profile State Management Operations (PSMO) and are cryptographically secured. This means that only authorized eIMs can make changes. In addition, standardization ensures interoperability between manufacturers and providers, which prevents security gaps caused by proprietary special solutions.

Question 7

When is it worth switching to SGP.32?

Accepted Answer

For all new IoT deployments where it is clear from the outset that a SIM swap will be necessary, SGP.32 is the clear recommendation. The standard eliminates lock-ins, enables easy integration of local profiles (important in countries with regulatory requirements), and allows for flexible switching between providers. Existing projects using SGP.02 or SGP.22 do not need to be replaced immediately, but should migrate to SGP.32 when upgrading hardware to avoid long-term costs and dependencies.

eUICC M2M SIM: Change SIM profiles remotely

What is an eUICC SIM card?

Advantages & features

Profile change from a distance

Extended storage capacity

No physical SIM exchange

Freedom to Leave

Optimize prices

Local SIM profiles

Compatibility

The three eUICC standards at a glance

loT Standard
GSMA SGP.32

Consumer Standard GSMA SGP.22

m2m (automotive) Standard
GSMA SGP.02

eSIM, embedded SIM and eUICC for IoT projects

Frequently Asked Questions

Bring your devices online - everywhere - with WhereverSIM