Remote SIM Provisioning (RSP) enables devices to download and manage SIM profiles digitally instead of relying on physical SIM cards. It allows seamless activation, switching, and lifecycle management through secure over-the-air (OTA) systems. 

In the consumer ecosystem, RSP follows the GSMA SGP.22 architecture, used in: 

• Smartphones (iOS, Android) 
• Tablets 
• Laptops 
• Smartwatches 
• Connected consumer electronics 

RSP was created to solve three main problems: 

1. Removing the need for physical SIM swapping 
2. Simplifying the customer activation experience 
3. Supporting small device formats (e.g., smartwatches) 

It also enables: 

• Digital onboarding 
• Operator portability 
• Better user experience 
• Multi-profile storage inside the eUICC 
• Global device scalability 

1. Operator or service provider prepares a digital SIM profile on an SM-DP+. 
2. A device requests or receives instructions to download a profile. 
3. The device’s LPA (Local Profile Assistant) establishes a secure channel. 
4. The profile is downloaded, installed, and activated. 
5. The device connects to the operator’s network using the new credentials. 

SGP.22 defines three major components: 

A secure backend system that: 

• Stores encrypted eSIM profiles 
• Delivers profiles to devices 
• Manages profile lifecycle events (enable/disable/delete) 
• Authenticates device requests 

The SM-DP+ is the heart of Consumer RSP. 

A directory-like service that: 

• Notifies devices that a profile is available 
• Allows devices to discover the SM-DP+ address 
• Supports “push” activations (no QR required) 
• Enables “operator app activation” flows 

The component inside the device that: 

• Manages user interaction 
• Displays QR code activation 
• Manages profile installation and switching 
• Communicates with SM-DP+ and SM-DS 
• Stores profile metadata 

On iOS, the LPA is system-managed.
On Android, the LPA may be: 

• System-provided (standard Android LPA) 
• OEM-customized 
• Carrier app-based (in specific architectures) 

Consumer eSIM activation can occur through different mechanisms depending on device type, operator preference, and channel (retail, web, app). 

Customer scans a QR code containing: 

• SM-DP+ address 
• Activation code 
• Profile identifier (optional) 

Steps: 

1. User scans QR code 
2. Device contacts SM-DP+ 
3. Profile is downloaded 
4. LPA prompts user to enable the profile 
5. Device registers on network 

Advantages: 

• Widely supported 
• Simple retail flow 
• Easy to distribute 

Limitations: 

• Requires camera 
• Not available on watches or some laptops

Operators may embed activation logic inside their mobile app using: 

• LPA APIs 
• Deep linking 
• SM-DS discovery 

Typical flow: 

1. User logs into operator app 
2. App authenticates the user 
3. App initiates activation via device APIs 
4. Device downloads profile silently 

Advantages: 

• Seamless UX 
• Works without QR codes 
• Allows business logic (KYC, plan selection) 

User selects:
Settings → Mobile Network → Add eSIM / Add Mobile Plan 

The device: 

1. Queries the SM-DS 
2. Retrieves available profiles 
3. Downloads and installs profile 

Used by: 

• Apple “Add Cellular Plan” 
• Android “Add eSIM” 

Advantages: 

• Completely QR-free 
• Ideal for prepaid/postpaid operator apps

Profile availability is automatically “pushed” to the device via SM-DS. 

Used when: 

• Device IMEI/EID is pre-registered 
• Operator pushes profile silently 
• Some IoT-like consumer devices (connected PCs, wearables) 

Used for: 

• Smartwatches 
• Companion devices 

Entitlement Server validates: 

• User eligibility 
• Device compatibility 
• Subscription rights 

Profile is downloaded automatically. 

Profiles undergo several lifecycle stages defined by GSMA. 

1. Download

Profile is delivered from SM-DP+ to device via secure channel. 

2. Installation

Profile is decrypted and written into eUICC. 

3. Enable

Profile becomes active; device attaches to the network. 

4. Disable

Profile is kept on device but cannot connect. 

5. Delete

Profile is permanently removed from eUICC. 

6. Reactivate

Disabled profiles can be re-enabled without re-downloading. 

Multi-Profile Behavior 

Modern smartphones support: 

• Multiple installed profiles 
• One active profile per SIM slot 
• Dual SIM via eSIM + eSIM (some devices) 
• Some modern smartphones support DSDA (Dual SIM Dual Active), enabling simultaneous voice/data on two profiles; behavior varies by OEM. 

This is one of the most important aspects for operators. 

Different device manufacturers behave differently in activation, storage, and LPA logic. 

Characteristics: 

• Most mature eSIM implementation 
• Highly stable activation flows 
• Supports QR, app-based, SM-DS, and push activations 
• Excellent lifecycle management 
• Supports full entitlement flows (watch pairing) 

Apple-Specific Behavior: 

• iPhones can convert physical SIM → eSIM 
• eSIM to eSIM transfer is automated between iPhones 
• Strong dependency on Entitlement Server for wearables 

Characteristics: 

• Widely used globally 
• Some firmware fragmentation 
• Supports LPA, SM-DS, QR flows 
• May require carrier configuration files 

Limitations: 

• Older firmware may not support eSIM transfer 
• Some models do not support eSIM

Characteristics: 

• Cleanest Android implementation 
• Excellent interoperability 
• Supports most activation flows 

Characteristics: 

• Limited LPA capabilities 
• Some laptops require operator app activation 
• SM-DS reliability varies 

Below is a fully written troubleshooting section operators and OEMs can use. 

Possible causes: 

• Low-quality print 
• Damaged code 
• Wrong QR format 
• Unsupported camera permissions 

Resolution: 

• Reprint or resend QR 
• Ensure SM-DP+ URL is correct 
• Clean camera lens 
• Try manual entry 

Causes: 

• SM-DP+ unreachable 
• Incorrect SM-DP+ address 
• Firewall blocking ports 
• Device time/date mismatch 

Resolution: 

• Validate network connection 
• Confirm Wi-Fi or mobile data 
• Verify SM-DP+ domain is reachable 
• Restart device 

Common root causes: 

• Corrupt activation code 
• Device not certified 
• Incomplete firmware updates 

Resolution: 

• Update OS 
• Reset network settings 
• Re-issue activation code

Causes: 

• Weak signal 
• Wi-Fi drop 
• Incorrect profile format 
• SM-DP+ timeout 

Resolution: 

• Switch to stronger Wi-Fi 
• Retry profile download 
• Restart device 

Causes: 

• Old device not updated 
• Profiles locked 
• Operator restrictions 

Resolution: 

• Perform full erase on old device 
• Request re-issuance 
• Install via QR 

Symptoms: 

• eSIM downloads but cannot attach to network 
• Activation errors 

Resolution: 

• Unlock device through operator 
• Check IMEI status 

Causes: 

• Operator provisioning incomplete 
• APN not configured 
• Region-specific restrictions 

Resolution: 

• Update APN 
• Confirm provisioning status 
• Re-enable profile