Remote SIM provisioning (RSP) is the standardized method of delivering operator subscriptions over the air to an embedded SIM, so a device can receive, enable, switch or delete mobile network profiles without anyone inserting a physical card. Within the SIM & eSIM topic of telecommunications, RSP is the system that turns the eUICC chip from a blank secure element into a working subscriber identity.
The architecture is defined by the GSMA in its SGP specifications, which describe the servers, the device software, the security certificates and the message flows. Every eSIM activation, from a smartphone scanning a QR code to a smart meter joining a network in the field, relies on one of the RSP variants described below.
How remote SIM provisioning delivers a profile
RSP works by moving an encrypted eSIM profile from an operator-controlled server to the eUICC through a chain of mutually authenticated sessions. The operator first orders a profile from its SM-DP+ (Subscription Manager Data Preparation), which personalizes the profile with the IMSI, the authentication key Ki and network parameters, then binds it to one specific chip.
On the device side, the Local Profile Assistant (LPA) contacts the SM-DP+, and the eUICC and the server prove their identities to each other with certificates issued under the GSMA Certificate Issuer root. Only after this handshake does the server send a Bound Profile Package, which is encrypted with session keys that only the target eUICC can derive. The chip decrypts and installs the package internally, so the secret keys never appear in plain form on the phone operating system.
The following table lists the main components and the role each one plays in the process.
| Component | Location | Role in provisioning |
|---|---|---|
| SM-DP+ | Operator or vendor data center | Prepares, encrypts and delivers profiles |
| SM-DS | Shared discovery service | Tells devices that a profile is waiting |
| LPA | Device software or eUICC | Downloads profiles and handles user consent |
| eUICC | Secure chip in the device | Stores and runs one or more profiles |
| Certificate Issuer | GSMA-accredited root | Anchors trust between all parties |
| EUM | Chip manufacturer | Signs each eUICC certificate at production |
The three RSP architectures
The GSMA has published three distinct RSP architectures, because consumer phones, industrial modules and constrained sensors have very different user interfaces and connectivity. Choosing the wrong one is a common design error in connected product projects.
The M2M architecture (SGP.02) is server-driven: an SM-SR (Subscription Manager Secure Routing) pushes commands to the chip, usually via SMS, and the device owner has no menu to manage profiles. The consumer architecture (SGP.22) is device-driven: the user or the device app triggers downloads through the LPA. The newer IoT architecture (SGP.32) keeps the device-driven logic but moves control to a remote eSIM IoT Manager (eIM), so fleets without screens can be managed in bulk.
| Specification | Control model | Typical devices | Main drawback |
|---|---|---|---|
| SGP.02 (M2M) | Push from SM-SR | Meters, vehicles, industrial modules | Complex operator integration and lock-in |
| SGP.22 (consumer) | Pull via LPA and user | Phones, tablets, watches, laptops | Needs a user interface for consent |
| SGP.32 (IoT) | Pull via remote eIM | Low-power sensors, trackers, gateways | Newer, with a smaller ecosystem |
Consumer RSP has gone through several versions, and SGP.22 version 3 added support for multiple enabled profiles, which lets a single eUICC run two subscriptions at the same time for Dual SIM use.
Activation codes, discovery and interfaces
A device learns where to fetch its profile through an activation code, a discovery service or a carrier app. The activation code is a short string, often printed as a QR code, in the format LPA:1$smdp.example.com$MATCHING-ID, which combines the SM-DP+ address with a matching ID that points to the reserved profile.
The SM-DS serves devices that should receive a profile without manual input, for example a watch paired to a phone plan. Devices with default SM-DP+ addresses burned into the eUICC can also poll a preset server on first boot. Each link in these flows uses a named interface, and engineers troubleshoot failures by identifying which interface broke.
| Interface | Between | Purpose |
|---|---|---|
| ES2+ | Operator and SM-DP+ | Ordering, confirming and releasing profiles |
| ES9+ | LPA and SM-DP+ | Authentication and profile download |
| ES8+ | SM-DP+ and eUICC | End-to-end encrypted profile installation |
| ES10 | LPA and eUICC | Local profile management commands |
| ES11 and ES12 | LPA, SM-DP+ and SM-DS | Event registration and discovery |
Remote SIM provisioning compared with physical SIM distribution
RSP replaces the logistics of plastic cards with a software process, which changes cost, speed and security for operators and device makers. A traditional SIM card carries a single fixed identity, which is personalized at a factory and shipped through retail, while an RSP profile is generated on demand and can be replaced remotely during the device lifetime.
| Aspect | Physical SIM card | Remote SIM provisioning |
|---|---|---|
| Time to activate | Days, including shipping | Usually under two minutes |
| Changing operator | New card must be inserted | New profile is downloaded |
| Profiles per chip | One | Several, limited by eUICC memory |
| Theft or loss of identity | Card can be removed | Profile stays inside the device |
| Main fraud vector | Stolen or cloned cards | Social engineering for profile transfer |
The removal of physical swapping does not remove SIM swap fraud. Attackers now target the operator process that issues a new activation code, so identity checks before profile reissue remain the critical control.
Operational limits and common mistakes
RSP is mature, yet deployments still fail for predictable reasons. Most problems come from operator integration, device policy or network access during download, rather than from the cryptography itself.
- Single-use activation codes: a profile that was downloaded once cannot be fetched again with the same code, so deleting it by mistake usually requires a new order.
- No connectivity for the first download: the device needs Wi-Fi or another active profile, which is a problem for IoT units without a bootstrap profile.
- Device or carrier locks: an eUICC can accept only profiles that match eligibility rules set by the manufacturer or a subsidizing operator.
- Memory limits: a typical eUICC stores roughly five to ten profiles, depending on profile size and chip capacity.
- Mixing architectures: an SGP.02 chip cannot be managed by a consumer LPA, and migrating a deployed fleet is costly.
Regulators also watch RSP closely, because profile transfer between devices and operator switching affect consumer choice. Some markets require operators to support eSIM activation on equal terms with physical cards.
Stripped to the essentials
A SIM tells the mobile network who you are and which plan you pay for. In the past, that identity lived on a small plastic card that the shop handed over. Remote SIM provisioning sends the same identity over the internet and stores it on a chip that is already built into the phone.
Think of it as downloading a sealed key instead of collecting it at a counter. The phone fetches it from the operator, checks that the sender is genuine, and unlocks it inside a protected chip. The result is a working mobile plan within minutes, with no card to post, lose or swap.
Where it is applied
A logistics company equips 12,000 refrigerated containers with cellular trackers that report temperature and location. The modules ship from the factory with an SGP.32 eUICC and a small bootstrap profile that works in many countries but at a high per-megabyte price.
When a container is assigned to routes in South America, the company eSIM IoT Manager instructs each tracker to download a regional operator profile through the SM-DP+ of that operator. The trackers install the new profile, switch to it and keep the bootstrap profile as a fallback. Nobody opens a sealed unit or travels to a port.
The outcome is lower data cost per device and a single manufacturing variant for every market. When a contract with one operator ends, the fleet moves to the next provider with a remote campaign that takes days instead of the months a card replacement would require.