IoT Knowledge Base
Learn the key concepts you need to know. Without the technical jargon.
IoT Reports & Guides
In-depth research, white-papers and guides from Pelion.
Blog Articles & News
The latest insights on industry trends, best practices, and Pelion announcements.
Events & Webinars
Upcoming events, online sessions, and expert-led webinars
About Us
Our mission, values, team, and the solutions we offer in the IoT space.
The Team
Meet our team behind Pelion's effortless connectivity.
Careers
Job opportunities, company culture, and the benefits of joining our team.
Sustainability
Our commitment to environmentally responsible practices.
SGP.22 is a technical specification from the GSMA that defines how eSIMs are provisioned and managed remotely for machine-to-machine (M2M) use cases. It’s part of the broader GSMA eSIM architecture and plays a crucial role in how connected devices securely receive and switch between mobile operator profiles without needing a physical SIM swap.
SGP.22 focuses specifically on the remote SIM provisioning (RSP) process for M2M deployments — meaning devices like smart meters, asset trackers, connected vehicles, and industrial IoT sensors that usually run headless and unattended in the field.
IoT devices are often deployed at scale, across geographies, and in environments where physical access is difficult or expensive. Managing connectivity for those devices using removable SIM cards isn't practical.
That’s where SGP.22 steps in. It allows remote provisioning of eSIMs embedded in the device. This means you can update or switch a device’s mobile network operator (MNO) profile over-the-air, even years after deployment.
This makes SGP.22 a foundational standard for M2M eSIM deployments, giving businesses control and flexibility over connectivity without needing to physically access devices.
The benefits of SGP.22 for IoT deployments
With SGP.22, you can remotely manage operator profiles on your eSIM-enabled devices. Whether you need to switch to a local operator to avoid roaming charges or migrate to a more cost-effective MNO, it's all possible from your backend system.
Think about servicing a device buried in a pipeline, mounted on a utility pole, or shipped globally. Traditional SIM swaps would mean high labour costs and downtime. SGP.22 removes the need for truck rolls or manual SIM handling.
IoT devices are often critical infrastructure. If a network goes down or fails to meet SLAs, SGP.22 allows you to push a new operator profile and restore connectivity quickly.
You can manufacture your devices with a single stock-keeping unit (SKU), preload a bootstrap profile, and then provision the final operator profile depending on where the device ends up. This simplifies manufacturing, logistics, and inventory.
The GSMA's SGP.22 standard ensures a secure architecture using certificates and encrypted communications. It aligns with telecom security frameworks and provides safeguards for remote operations.
At its core, SGP.22 defines the procedures and interfaces for managing operator profiles on an eSIM remotely. It works in coordination with the SGP.21 specification, which outlines the architecture and entities involved. Here’s a simplified view of how it all comes together.
eUICC: The embedded Universal Integrated Circuit Card. It’s the secure element in the device that stores operator profiles.
Subscription Manager - Data Preparation (SM-DP): Prepares and encrypts operator profiles.
Subscription Manager - Secure Routing (SM-SR): Handles secure transmission and installation of profiles on the eUICC.
MNO: The mobile network operator whose profile is being provisioned.
Device Controller / M2M Platform: Initiates profile management operations.
Bootstrap profile: The device comes with a default operator profile (bootstrap) that provides basic connectivity.
Provisioning request: The M2M platform sends a command to download a new operator profile.
Profile download: The SM-DP prepares the profile. The SM-SR sends it securely to the device.
Activation: The new profile is installed and activated. The old profile can be disabled or removed.
All this happens remotely and securely, without any local intervention.
To use SGP.22, you need more than just an IoT eSIM. You need:
eUICC-compatible hardware: The device must support embedded SIM functionality and comply with SGP.22.
An operator or platform with SGP.22 integration: Not all MNOs support full M2M eSIM RSP. Look for providers (like Pelion) who offer carrier-grade infrastructure and interoperability.
Access to Subscription Managers (SM-DP and SM-SR): These are often managed by the MNO or an independent eSIM service provider.
When choosing an IoT eSIM provider, check:
Do they provide bootstrap profiles and secure profile switching?
Is their SM-SR interoperable with multiple eUICC vendors?
Do they support global deployments and local operator integration?
Are they compliant with GSMA SGP.22 specifications?
While SGP.22 is designed for M2M deployments, SGP.32 is targeted at IoT devices that are user-managed or semi-autonomous — like wearables, consumer devices, or enterprise devices with UIs.
SGP.22 assumes that the device can't interact with the user, so all provisioning happens remotely via backend systems.
SGP.32, by contrast, allows devices to download and manage profiles themselves via Local Profile Assistant (LPA), typically through a UI.
If you're deploying rugged industrial sensors or connected utility devices, SGP.22 is the right standard. If you're shipping a connected smartwatch, SGP.32 is probably a better fit.
Smart meters using SGP.22 can switch to a different mobile network if signal strength drops, without anyone needing to visit the premises.
Vehicles with embedded eSIMs can stay connected across borders by remotely updating operator profiles, reducing roaming costs and improving reliability.
Devices on construction sites, in factories, or remote locations can be updated, secured, and switched to different networks without downtime.
Pelion is a trusted provider of global IoT connectivity, with a platform built to support GSMA SGP.22 specifications. We make it easy to manage eSIMs at scale for M2M use cases. Our solution supports secure remote provisioning, multi-operator integrations, and full visibility over your deployed base.
We work with OEMs, enterprise IoT teams, and systems integrators to make eSIM simple. Whether you’re just getting started with SGP.22 or scaling a global fleet, we’ve got the expertise and tools to help.