SCP11 eSIM Management Relay
SCP11/live/ is the consolidated eSIM management relay shell. It uses
platform TLS trust by default, accepts explicit CA bundle overrides, and keeps
a relay-first operator model.
Use it when the workflow runs through an SM-DP+ or an eIM and should behave
the way a shipping LPA/IPA would.
On this page
Underlying concept
Read RSP Architecture first. The LPAd / IPAd split there is what the command surface reflects.
When to use it
DOWNLOAD-PROFILEdriven by an activation codeDISCOVERandDOWNLOADfor IPAd-style pulls- optional local extensions for deployment-specific relay commands
- setting SM-DP+, ES9+, or ES9+ CA parameters for the session
- running notification synchronization around transactional flows
Entry points
python -m SCP11.live
python -m SCP11.live --cmd "DISCOVER; STATUS; EXIT"
yggdrasim-scp11-live
python main/main.py and pick the eSIM Management Relay entry.
Command surface, grouped
Session and diagnostics
| Command | Purpose |
|---|---|
STATUS |
print relay session snapshot |
LIST |
list known SM-DP+, ES9+, and CA entries |
RESET |
reset session state to defaults |
HELP |
print the grouped help surface |
LPAd
| Command | Purpose |
|---|---|
DOWNLOAD-PROFILE <activation> |
run the full activation-code download flow |
IPAd
| Command | Purpose |
|---|---|
DISCOVER |
contact SM-DP+ for pending events |
DOWNLOAD [matchingId] |
pull a specific profile event |
Optional extension commands
| Command | Purpose |
|---|---|
Profile state
| Command | Purpose |
|---|---|
ENABLE-PROFILE |
enable the selected profile |
DISABLE-PROFILE |
disable the selected profile |
DELETE-PROFILE |
delete the selected profile |
Endpoints and trust
| Command | Purpose |
|---|---|
SET-SMDP <host> |
set the SM-DP+ endpoint |
SET-ES9 <host> |
set the ES9+ endpoint |
SET-ES9-TLS <on/off> |
control TLS for ES9+ |
SET-ES9-CA <path> |
pin the CA used by ES9+ |
ES9-CERT-INFO |
inspect the ES9+ certificate chain |
Compatibility probes
| Command | Purpose |
|---|---|
FLOW |
scripted relay flow probe |
EIM-AUTHENTICATE |
relay-side eIM authentication probe |
HIL / diagnostics
| Launcher flag | Purpose |
|---|---|
--dump-keybag <path> |
no-op stub. SCP11c BSP keys are derived inside the eUICC during BPP processing and never reach the host, so they cannot be exported from the relay. The flag prints a clear message pointing at SCP11.local_access (for host-derived BSPs) or SCP03 (for SCP03 session keys), then exits with code 2. |
For actual keybag exports see SCP11 Local Access and SCP03.
Runtime dependencies
- a PC/SC reader with an eUICC, or a relay transport endpoint for the card
- certificate material under
SCP11/and under the writable runtime root - network reachability to the chosen SM-DP+ or eIM
- optional local extension packages under the runtime root
State the shell writes
| Location | Contents |
|---|---|
state/device_inventory.sqlite3 |
per-EID live session settings |
runtime root plugins/ |
optional local extension code and artifacts |
Common recipes
Fast preflight
python -m SCP11.live --cmd "DISCOVER; STATUS; LIST; EXIT"
Download with an activation code
[eSIM Management] > DOWNLOAD-PROFILE LPA:1$example.smdp.example.com$ABCDEF123456
Pitfalls
- An expired or untrusted ES9+ certificate fails at
InitiateAuthenticationwith a clear server-side error. CheckSET-ES9-CAandES9-CERT-INFO. - Notifications left on the card block subsequent transactions. Let the shell synchronize them, or force it via the notification verbs.
DOWNLOAD-PROFILErequires that the card supports the CI PKID that the SM-DP+ advertises. Mismatches fail early with aCI PKID unavailableresponse.- The optional plugin capability is loaded from the active runtime root. If
you are on a frozen build, drop the plugin into the runtime root's
plugins/tree, not the source tree.