SGP.32 eSIM
and Platform Solution

Yes. Eseye has integrated SGP.32 into its proven AnyNet+ eSIM and Infinity Connectivity Management Platform, giving enterprises unified control and choice across all RSP models (SGP.02, SGP.22, and SGP.32) from a single interface for simpler global IoT logistics.

Unlike many SGP.32 implementations that rely on a single operator profile, Eseye combines SGP.32 with its AnyNet+ multi-IMSI architecture to deliver resilient global connectivity.

SGP.32 requires a new SIM and is not backward compatible with earlier standards. Migration from existing deployments typically occurs during device refresh cycles and requires a physical SIM swap, rather than through a simple over-the-air upgrade.

Here are some of the things enterprises need to consider:

• Ensure your hardware / devices support eUICC and required protocols (e.g. remote profile download, BIP or similar over-the-air management).
• Validate that your current modems/firmware can handle OTA profile switching.
• Plan for updating device firmware if needed.
• Map out which operators / networks you’ll need in each region and is a SGP.32 profile available to support connectivity there.
• Consider how fallback / bootstrap profiles will work.
• Work with Eseye’s experts / technical support to get guidance and help. Eseye offers services such as a free device assessment to test readiness.

1. Is your device SGP.32 ready within your device and application environment?
2. Are there enough profiles available? A sufficient number of Mobile Network Operators (MNOs) must have IoT profiles available for localisation, enabling practical deployment at scale.
3. In most cases, SGP.32 requires a new SIM (eUICC). However, if your existing device already contains an SGP.32-capable eUICC, migration may be possible without replacing the hardware and you may be able to migrate without hardware changes (refer to one of Eseye’s IoT Specialists for more information).

However, devices that only support older SIM standards or that lack remote profile management, hardware
replacement or upgrade will be required.

Eseye’s Infinity Platform supports managed switching across many mobile networks (800+ networks in 190+ countries) using eSIM orchestration. The infrastructure is designed to allow automatic / remote switching to maintain connectivity, even if a primary operator profile fails. This minimizes downtime for globally deployed IoT devices.

Some of the key benefits that SGP.32 offers are:

• Ship one SKU globally (no multiple region-specific SIM types)
• Lower logistics and manufacturing complexity
• Remote profile management: add/remove/switch operator profiles without physical intervention
• Bring Your Own Carrier (BYOC) if you have an existing arrangement and access to a profile
• Improved flexibility and faster deployment in new regions
• Better resilience through fallback / bootstrap profiles.

Yes, potential constraints include:

• Device modems / firmware must support eUICC and remote profile management protocols.
• Some existing older devices may not be upgradable to full SGP.32 compatibility.
• You may need to test OTA functionality, firmware behaviour, and edge cases (e.g. network transitions, roaming, profile switching) in your own deployment scenario.
• Your device must use a global APN, not one tied to a specific operator. If not, you must be able to remotely update the APN on the device. Eseye solves this by offering a global APN that works across all its partner networks in the AnyNet Federation.

Eseye offers a managed service to simplify everything to do with connectivity. We will work with you to ensure the correct carrier and fallback options are selected. If you have an existing carrier profile and agreement that you would like to use in addition, this can be explored with one of our IoT Specialists.

This depends on your provider and plan terms. Whichever profile you’re using is highly likely to incur an additional cost.

We recommend getting in touch to discuss your particular use case.

To provide help with SGP.32 migration, Eseye offers:

• SGP.32 ready SIMs.
• Free device assessments to test your hardware readiness.
• Technical documentation and guidance.
• Whitepapers and resources: “Adopting SGP.32: What Enterprises Need to Know” for planning.
• Customer support and expert consultations.

No. SGP.32 enables profiles to be downloaded remotely, but connectivity still depends on the underlying network and roaming agreements. Many implementations rely on a single operator profile at a time, which can introduce coverage limitations.

Eseye addresses this by combining SGP.32 with multi-IMSI connectivity, enabling access to multiple networks for greater resilience.

No. SGP.32 defines how profiles are delivered to a SIM, but it does not address the full complexity of global IoT connectivity. Enterprises must still manage operator relationships, billing, compliance, and device behaviour.

For this reason, SGP.32 is typically used as part of a broader orchestration and managed connectivity solution.

In many SGP.32 implementations, connectivity depends on a single operator profile. If that network experiences issues, the device may lose connectivity until a new profile is deployed. Eseye mitigates this risk by combining SGP.32 with its AnyNet+ multi-IMSI architecture, enabling devices to maintain connectivity across multiple networks and automatically recover from outages.

SGP.32 enables remote profile management, while multi-IMSI provides real-time access to multiple network identities. Combining both allows enterprises to benefit from flexible profile provisioning and resilient connectivity.

This approach ensures devices remain connected even in complex or changing network conditions.

SGP.32 can simplify certain aspects of profile delivery, particularly for constrained devices. However, it does not remove the need to manage connectivity operations such as billing, configuration, and compliance.

Without orchestration, SGP.32 can introduce additional operational complexity. This is why many organisations adopt it as part of a managed service.