SGP.02

In IoT deployments, everything revolves around scale, manageability, and flexibility. Especially when devices are deployed globally and remain operational for years. In these environments, eSIM technology plays a key role.

One of the first standards that enabled remote SIM provisioning for machine to machine environments is SGP 02. Although newer standards have been introduced, this one is still widely used in existing IoT deployments.

In this article, you will learn what SGP 02 is, how it works, and when it is still relevant.

Summary

For a quick overview:

• SGP 02 is a GSMA standard for eSIM in M2M environments
• it enables remote simcard management without physical replacement
• it works with central components such as SM DP and SM SR
• it is designed for devices without a user interface
• it is still used, but has limitations compared to newer standards

What SGP 02 is

SGP 02 is a GSMA specification for remote SIM provisioning in machine to machine communication. It defines how eSIM profiles can be managed remotely on an embedded simcard, also known as an eUICC.

The standard was developed at a time when IoT deployments were growing rapidly, but flexibility in connectivity was still limited. With SGP 02, it became possible to:

• download sim profiles remotely
• switch operators without replacing the simcard
• centrally manage connectivity throughout the lifecycle

A key principle is that devices operate autonomously. No user interaction is required to confirm profile actions.

How SGP 02 works in practice

The strength of SGP 02 lies in its architecture. It consists of several components that work together to enable remote provisioning.

Key components within SGP 02

Within the GSMA SGP 02 standard, these elements play a central role:

• eUICC
  The embedded simcard in the device where profiles are stored
• SM DP (Subscription Manager Data Preparation)
  Responsible for preparing and encrypting sim profiles
• SM SR (Subscription Manager Secure Routing)
  Ensures secure delivery and management of profiles on the eUICC
• MNO (Mobile Network Operator)
  The provider that delivers the network profile

These components operate within a relatively closed ecosystem.

How remote SIM provisioning works

A typical SGP 02 provisioning flow looks like this:

1. A device is manufactured with an eUICC
2. An initial profile is installed
3. A new profile is prepared by the SM DP
4. The SM SR securely delivers the profile to the eUICC
5. The profile is activated without physical intervention

This process happens entirely remotely and without user interaction.

Key characteristics and benefits of SGP 02

Although the standard is older, it offers several important benefits.

Remote management without physical simcards

The biggest advantage is that simcards no longer need to be physically replaced. This reduces operational costs and logistics, especially for hard to reach devices.

Designed for devices without a user interface

Many IoT use cases involve devices without screens or controls. SGP 02 is specifically built for these environments.

Proven technology in M2M

The standard has been widely used in sectors such as automotive and smart metering. This makes it a stable and proven solution.

Central control over connectivity

Organizations can centrally manage connectivity, including activation, deactivation, and profile switching.

Use cases for SGP 02

SGP 02 is mainly used in traditional M2M scenarios where stability is more important than flexibility.

Examples include:

• smart metering deployments with long lifecycles
• connected vehicles
• industrial installations
• logistics and asset tracking solutions
• fixed infrastructure such as alarm systems

In these use cases, connectivity requirements typically do not change frequently.

Limitations and challenges of SGP 02

While SGP 02 enables remote provisioning, it also has clear limitations. These limitations led to the development of newer standards.

Limited flexibility for international deployments

Switching profiles is possible, but often complex and dependent on pre established agreements between parties.

Complex infrastructure

The architecture with SM DP and SM SR requires integration between multiple stakeholders. This can make implementation and management more complex.

Limited scalability for modern IoT

For very large deployments with dynamic requirements, SGP 02 can be less efficient than newer standards.

Less suitable for dynamic use cases

Use cases where devices need to frequently switch networks or adapt to changing conditions are harder to support.

SGP 02 versus newer eSIM standards

The introduction of standards such as SGP 32 highlights where SGP 02 falls short.

Key differences include:

• newer standards offer more flexibility in profile selection
• management is more automated
• less reliance on pre configured relationships
• better suited for large scale IoT deployments

That said, SGP 02 is still widely used and does not need to be replaced immediately in existing environments.

When to still choose SGP 02

In new projects, SGP 02 is less commonly selected. However, there are situations where it remains relevant:

• existing infrastructure is already based on this standard
• the use case is stable with limited changes
• devices have long lifecycles and are already deployed
• migration to newer standards would be costly

In these scenarios, continuing with SGP 02 can be a practical choice.

Conclusion

SGP 02 has played a key role in the evolution of eSIM and remote SIM provisioning for M2M and IoT. It enabled remote management of simcards in environments where physical access is difficult or expensive.

At the same time, its capabilities do not always align with the needs of modern IoT deployments. Newer standards offer more flexibility, scalability, and simplicity.

For organizations, the choice depends on context. In existing deployments, SGP 02 remains a stable solution. For new implementations, it is worth considering more modern alternatives.

For more information, please contact us by phone at +31-85-0443500 or by email at info@thingsdata.com.