How eSIM Provisioning Works: QR Codes to eUICC

ملخص

Pixel’s announcement explains consumer eSIM provisioning, from the activation code in a QR to profile installation on an eUICC. It covers the roles of the LPA and SM-DP+, mutual authentication, and why a used QR code usually cannot activate a profile on another phone.

DEV Community

How eSIM Provisioning Actually Works: QR Codes, SM-DP+ and the eUICC Explained

If you've ever bought a travel eSIM, you scanned a QR code and a few seconds later your phone had a new mobile line. But what actually happens in those seconds? Here's a developer-friendly walkthrough of how consumer eSIM provisioning works. eSIM = eUICC + a downloadable profile A physical SIM is a UICC: a tiny smart card running a Java Card OS that stores your subscriber identity (IMSI), authentication key (Ki) and operator settings. An eSIM is an eUICC: the same kind of secure element, soldered onto the phone's board, that can hold multiple downloadable profiles. A "profile" is the operator package: IMSI, keys, network settings and apps, encrypted for one specific eUICC. The players (GSMA SGP.22 consumer spec) SM-DP+ (Subscription Manager Data Preparation): the operator's server that prepares and stores encrypted profiles. LPA (Local Profile Assistant): software on the phone (the "Add eSIM" flow in iOS/Android settings). eUICC: the secure element that finally installs the profile. What the QR code contains The QR is just an activation code string, typically: LPA:1$smdp.example.com$MATCHING-ID-123
1 is the format version smdp.example.com is the SM-DP+ address MATCHING-ID tells the server which prepared profile is yours No secret keys are in the QR, which is why it can be emailed, though it should still be treated as single-use and private. The download, step by step The LPA parses the activation code and opens a TLS session to the SM-DP+. Mutual authentication: the eUICC proves it is a genuine GSMA-certified chip; the SM-DP+ proves it is a certified server. The SM-DP+ binds the profile to that eUICC and sends a Bound Profile Package, encrypted so only that chip can decrypt it. The eUICC installs the profile and the LPA shows it as a new line. That's why a used QR code usually fails on a second phone: the profile was already bound to the first eUICC. Why this matters for travellers Because profiles download over the internet, a traveller can install a local-rate data plan before leaving home, keep their home SIM active for calls and OTPs, and switch data to the eSIM on landing. Services like eSIMKite package these plans for 200+ destinations, from a Dubai / UAE eSIM to a Europe multi-country plan. Not sure your device has an eUICC? Most iPhones from XS onward, Pixel 3+ and Galaxy S20+ do; you can check compatibility here. Further reading GSMA SGP.22 (RSP Technical Specification) How to install a travel eSIM on iPhone and Android
How eSIM Provisioning Works: QR Codes to eUICC
Powered by Readybot.io

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …