eSIM RSP Knowledge Base

Comprehensive technical knowledge base covering 12 GSMA eSIM specifications. 84+ articles on Remote SIM Provisioning — SGP.02, SGP.22, SGP.32, SGP.41, SGP.29, SGP.23, SGP.25, SGP.26 and more.

Project maintained by AlexsCodingAgent Hosted on GitHub Pages — Theme by mattgraham

Testing the Phone’s Assistant 📱🦸

Imagine…

You hire a personal assistant to manage your house keys. This assistant needs to:

Find where keys are stored
Pick up new keys from the locksmith
Hand you the right key when you need it
Throw away old keys you don’t use anymore
Label each key so you know what door it opens

Now imagine testing that assistant before you trust them with your actual house. You’d give them fake keys, pretend doors, and watch every move they make. That’s exactly what LPA testing does in the eSIM world: it makes sure the phone’s built-in assistant knows how to handle digital keys perfectly.

The LPA Has Three Jobs 🎯

The Local Profile Assistant on your phone is actually three helpers in one:

Helper	Name	Real Job
🔍 LDS	Discovery Service	Checks the Post Office for waiting deliveries
⬇️ LPD	Download Service	Runs the whole key-download pipeline
👆 LUI	User Interface	Shows you buttons to manage your profiles

Each one talks to the eUICC chip using its own special interface: ES10a for discovery, ES10b for downloading, and ES10c for managing.

ES10a: Finding Where the Keys Are 🔍

Two simple functions get tested:

GetEuiccConfiguredAddresses : “Hey chip, which Post Office should we check for deliveries?” The chip replies with addresses of any SM-DS or SM-DP+ it knows about.
SetDefaultDpAddress : “Remember this Key Maker’s address as the default.” The test verifies that the address sticks even after restarting.

ES10b: The Download Pipeline ⬇️

This is the big one: 12 different functions that form the key-download chain:

GetEUICCInfo : “Show me your ID badge and capabilities”
GetEUICCChallenge : “Give me a fresh random number to prove you’re really you”
AuthenticateServer : “Check the Key Maker’s ID badge and sign the handshake”
PrepareDownload : “Get ready: a key is coming!”
LoadBoundProfilePackage : “Here’s the encrypted key: please store it safely”

The chip is tested for all the edge cases: what if the certificate is expired? What if the matching ID is wrong? What if someone tampers with the key package? A good chip rejects all of these.

ES10c: Managing the Keychain 👆

Eight functions let you manage profiles like apps on your phone:

Function	What It Does	Real-Life Analogy
GetProfilesInfo	Lists all your profiles	Opening your key drawer
EnableProfile	Makes a profile active	Putting a key on your keyring
DisableProfile	Puts a profile to sleep	Taking a key off but keeping it
DeleteProfile	Removes a profile forever	Throwing away an old key
SetNickname	Labels a profile	Sticking a label on a key
GetEID	Shows your chip’s unique ID	Reading the serial number on your vault
eUICCMemoryReset	Factory reset: wipes everything	Emptying every drawer at once

Testing the Whole Device 📲

When testing the actual phone (not just the chip), the test flips around. Now the phone is real, and the chip and servers are simulated:

A test eUICC chip (already certified) sits inside the phone
Simulated servers (S_SM-DP+, S_SM-DS) pretend to be the Key Maker and Post Office
S_EndUser simulator taps buttons on the screen
Every complete workflow: Add Profile, Enable, Disable, Delete: is tested from start to finish

The profile download pipeline is the most heavily tested sequence in all of SGP.23. The four-function chain (GetEUICCChallenge → AuthenticateServer → PrepareDownload → LoadBoundProfilePackage) has dozens of test variations, including wrong certificates, expired credentials, tampered keys, and retry scenarios: because if ANY step fails, the key never gets delivered.

Kid-friendly version of GSMA SGP.23, Sections 4.2 (eUICC Interfaces), 4.4 (LPAd Interfaces), 5.4 (Device Procedures)

← Back to Kids Articles