An eUICC (Embedded Universal Integrated Circuit Card) is a tamper-resistant secure element that can download, store and switch between several mobile operator profiles without any physical card swap. In the SIM & eSIM area of telecommunications, the eUICC is the hardware and security foundation of what consumers call an eSIM: the eSIM is the service experience, while the eUICC is the chip and its operating system that make remote provisioning possible.
Unlike a classic UICC, whose subscription data is written once at the card factory, an eUICC ships with no fixed operator identity. Profiles arrive later over the air through GSMA remote SIM provisioning, and each profile behaves on the network exactly like a traditional SIM card, with its own IMSI, keys and applets.
How an eUICC is built and isolated
An eUICC combines a secure microcontroller, a card operating system based on Java Card and GlobalPlatform, and a set of security domains defined by the GSMA specifications. The domains separate who controls what, so that one operator can never read or alter another operator’s profile on the same chip.
Each chip carries a unique EID (eUICC Identifier), a 32-digit number that identifies the eUICC itself, not the subscription. The ICCID, by contrast, belongs to each individual profile, so one eUICC with three profiles exposes one EID and three ICCIDs.
The table below lists the main internal components and their roles in the consumer architecture.
| Component | Role | Controlled by |
|---|---|---|
| ISD-R | Root security domain that creates, enables and deletes profiles | eUICC manufacturer |
| ISD-P | Container that holds one operator profile in isolation | Profile owner via SM-DP+ |
| ECASA | Holds certificates and keys for mutual authentication | eUICC manufacturer and GSMA CI |
| MNO-SD | Operator domain inside a profile for applets and OTA updates | Mobile network operator |
| Profile policy rules | Restrict actions such as disabling or deletion | Profile owner |
Trust rests on a public key infrastructure. A GSMA-approved Certificate Issuer signs the certificates of eUICC manufacturers and provisioning servers, and every download begins with mutual authentication between the chip and the server before any profile data moves.
GSMA architectures and eUICC variants
The GSMA defines three remote provisioning architectures, and an eUICC is built and certified for one of them. Choosing the wrong variant is a frequent design error in connected-device projects, because the management model differs fundamentally between them.
| Specification | Target devices | Management model | Key server roles |
|---|---|---|---|
| SGP.02 (M2M) | Meters, vehicles, industrial modules | Server push, no user interface | SM-DP and SM-SR |
| SGP.22 (consumer) | Phones, tablets, watches, laptops | User or device pulls profiles | SM-DP+ and SM-DS |
| SGP.32 (IoT) | Constrained IoT devices | Remote manager without a screen | SM-DP+ and eIM |
In the consumer model, a software component called the Local Profile Assistant (LPA) runs on the device and talks to the SM-DP+ to fetch profiles, usually after the user scans a QR activation code or an operator app triggers the download. In the older M2M model, an SM-SR server holds the management keys and pushes changes without user involvement. The newer SGP.32 architecture brings consumer-style flexibility to headless IoT devices through an eSIM IoT Manager (eIM).
Physical packaging is a separate choice from the architecture. The following table compares the common form factors.
| Form factor | Description | Typical use |
|---|---|---|
| MFF2 chip | Soldered package of about 5 x 6 mm | Smartphones, wearables, vehicles |
| Removable eUICC | Standard plug-in card with eUICC software | Retrofit IoT, legacy devices |
| Integrated (iSIM) | Secure enclave inside the main SoC | Very small or low-cost devices |
eUICC compared with related concepts
The terms eUICC, eSIM, eSIM profile and iSIM are often used interchangeably, but they describe different layers of the same system. Keeping them apart avoids errors in procurement contracts and technical specifications.
| Term | What it refers to | Relationship to the eUICC |
|---|---|---|
| eUICC | Secure chip and operating system | The hardware and software platform |
| eSIM | Commercial name for the whole capability | Service built on an eUICC |
| eSIM profile | Downloadable subscription package | Content stored inside an ISD-P |
| Classic UICC | Single-profile card written at the factory | Predecessor without remote provisioning |
| iSIM | eUICC function integrated into a SoC | Different packaging of the same concept |
A practical way to remember the distinction is that the EID stays with the device for its whole life, while profiles and their ICCIDs come and go. An operator activating service therefore needs the EID only when it binds a profile to a specific chip in advance.
Capacity, security certification and lifecycle
An eUICC can store multiple profiles, typically between five and ten or more, depending on available secure memory and profile size. Most consumer devices historically allowed only one enabled profile at a time; the Multiple Enabled Profiles (MEP) feature introduced in later SGP.22 versions allows two profiles to be active simultaneously on one chip, which supports dual SIM operation without a second physical card.
Security assurance is mandatory. Chips are evaluated under a Common Criteria protection profile at EAL4+ augmented, and production sites need GSMA SAS-UP accreditation for handling personalization data. Provisioning servers in turn require SAS-SM accreditation. These controls protect the long-term network keys (Ki and OPc) that authenticate the subscriber.
- Manufacturing: the chip receives its EID, certificates and the ISD-R, but no operator profile.
- Provisioning: a profile is downloaded, installed in a new ISD-P and enabled.
- Operation: the enabled profile attaches to the network like a conventional SIM.
- Switching: the ISD-R disables one profile and enables another on command.
- Deletion or reset: profiles are removed; a memory reset wipes all operational profiles.
Limitations and common mistakes
The eUICC removes the plastic card but not every constraint. Device locks, operator policies and certification gaps still determine whether a profile can actually be used, and several problems appear repeatedly in deployments.
| Symptom | Likely cause | Remedy |
|---|---|---|
| Profile download fails | Server certificate not trusted by the chip | Use an SM-DP+ under a supported Certificate Issuer |
| Profile cannot be deleted | Profile policy rules forbid deletion | Request release from the profile owner |
| IoT fleet locked to one carrier | SGP.02 chip bound to one SM-SR | Plan SM-SR migration or choose SGP.32 parts |
| Profiles lost after repair | eUICC memory reset during service | Reissue activation codes before servicing |
| Device refuses foreign profile | Carrier device lock in the LPA | Request an unlock from the selling operator |
A further misconception is that an eUICC makes SIM swap fraud impossible. Remote provisioning moves the attack surface to account recovery and activation code issuance, so operators still need strong identity checks before releasing a new profile.
In everyday language
An eUICC is a tiny, permanent SIM chip built into a phone, watch or car. Instead of holding one fixed mobile subscription, it works like a small secure wallet that can hold several subscriptions and switch between them.
When you buy a new plan, the operator sends the subscription to that chip over the internet, and nobody has to open a card tray. The key takeaway is simple: the eUICC is the hardware, and the eSIM is what you experience when you use it.
Seen in the real world
A logistics company operates 4,000 refrigerated trailers across several European countries, each fitted with a telematics unit that reports temperature and location. The units contain soldered MFF2 eUICC chips, because a plastic SIM card would loosen under constant vibration and temperature swings between minus 25 and plus 40 degrees Celsius.
When a new carrier offers better coverage on eastern routes at a lower price, the fleet team does not send technicians to the trailers. Through its remote management platform, it downloads the new carrier profile to every eUICC, tests it on a pilot group of 200 units, and then switches the rest in batches overnight.
The outcome is a carrier change completed in two weeks without a single site visit, while the previous profile stays stored on each chip as a fallback in case of outages.