What Is an eUICC? UICC vs eUICC, and Whether Your IoT Devices Need One

An eUICC is a SIM that can hold several operator profiles and have new ones loaded remotely. Peter Green looks inside the chip, compares UICC vs eUICC, explains what an eUICC can't do, and sets out when your IoT devices actually need one.

What is an eUICC: a SIM chip holding several operator profiles, one enabled
Quick answer: An eUICC is a SIM that can hold several operator profiles and have new ones loaded remotely. Peter Green looks inside the chip, compares UICC vs eUICC, explains what an eUICC can't do, and sets out when your IoT devices actually need one.

What is an eUICC? Most explanations start with a wall of acronyms: ISD-R, ECASD, ISD-P, SM-DP+. I’ll get to those, because they explain a lot. But the question I actually get asked by people buying IoT hardware is simpler. Do I need one, and what am I paying for if I do?

Here’s my answer, built from the inside of the chip outwards.

In one sentence. An eUICC is a SIM that can hold several operator profiles at once, switch between them and download new ones remotely, under rules set by the GSMA. A traditional UICC holds one operator’s identity for life. Whether you need the extra capability depends on how long your device lives, where it goes and how easily you can reach it.

What is an eUICC?

Every modern SIM is a UICC: a small, tamper-resistant computer that runs the USIM application and keeps the secrets your device uses to prove who it is to the network. On a conventional UICC, those secrets belong to one operator. The IMSI, the authentication key, the network lists and the ICCID are written in at personalisation, and that’s that. New operator, new SIM.

An eUICC keeps all of that, but puts each operator’s identity in its own sealed container, called a profile, and adds the machinery to manage those containers from a distance. The chip itself gets a permanent identity of its own, the EID, which stays the same however many profiles come and go. Think of a UICC as a key cut for one lock, and an eUICC as a key safe that a trusted locksmith can restock remotely.

It’s worth saying what an eUICC is not. It isn’t a package. You can buy one as a soldered MFF2 chip, as a normal plastic SIM card or built into the modem chipset. The packaging argument is a separate one, which I cover in eSIM vs eUICC for IoT.

UICC vs eUICC: what’s inside the chip

This is where the acronyms earn their keep. Here’s a simplified view of the two architectures side by side.

UICC vs eUICC architecture On the left, a UICC containing a single fixed operator profile with IMSI, authentication key, ICCID and network lists. On the right, an eUICC with an EID, an ECASD holding the chip’s certificate and keys, an ISD-R managing profiles, and three ISD-P containers: a bootstrap profile, an enabled operational profile and a disabled operational profile. A remote manager connects to the ISD-R. UICC one operator, fixed at the factory Card operating system Operator profile IMSI (subscriber identity) Ki (authentication key) ICCID (card number) Network lists and settings USIM and toolkit applets To change operator: replace the SIM eUICC several profiles, managed remotely Card operating system EID: the chip’s own ID ECASD proves the chip is genuine ISD-R creates and manages profiles ISD-P 1 Bootstrap profile disabled ISD-P 2 Operator A profile ENABLED ISD-P 3 Operator B profile disabled To change operator: enable, download or delete a profile remotely Remote manager and profile server eIM and SM-DP+ under SGP.32 Simplified. Real eUICCs also hold applets, policy rules and, under SGP.32, may host the IoT Profile Assistant.
A UICC carries one operator’s identity for life. An eUICC keeps each operator’s identity in its own sealed container (ISD-P), managed by the ISD-R and vouched for by the ECASD.

In plain English:

  • ECASD holds the chip’s certificate and private keys, put there by the eUICC manufacturer. It’s how a profile server knows it’s talking to a genuine, certified chip before it hands over an operator’s secrets.
  • ISD-R is the root manager. It receives remote instructions, creates new profile containers, and enables, disables or deletes them. It can see each profile’s metadata, but it can’t read the operator’s secrets inside.
  • ISD-P is a sealed container for one profile. Each one is isolated from the others, so operator A can never see operator B’s keys. In a typical IoT eUICC, one profile is enabled at a time.
  • Bootstrap or provisioning profile is the one loaded at the factory so the device can connect out of the box and fetch its proper profile. Who owns that profile matters more than most buyers realise.

If you want the full term-by-term treatment, euicc.co.uk goes deeper, and our IoT eSIM glossary entry links the related terms together.

UICC vs eUICC at a glance

UICCeUICC
Operator profilesOne, fixedSeveral, stored in isolated containers
Changing operatorPhysically swap the SIMDownload, enable or delete a profile remotely
Who can provisionThe issuing operatorAny operator whose profile can be delivered to that chip, under GSMA rules
IdentityICCID per cardA permanent EID for the chip, plus an ICCID per profile
PackagesPlastic, MFF2Plastic, MFF2 and smaller, integrated
AssuranceOperator and SIM vendor testingGSMA compliance and security assurance for the chip and its software
Memory and powerModestMore secure memory needed for multiple profiles. Check the datasheet for power figures on battery devices
Unit costLowestHigher, though the gap keeps narrowing

What an eUICC doesn’t do

I’ve watched eUICCs sold as a cure for everything from poor coverage to a bad tariff. They aren’t. A few things worth being clear about:

  • It doesn’t improve coverage. The enabled profile still connects to one network at a time. If the signal’s poor at the mounting point, a new profile won’t help; an antenna might.
  • It doesn’t guarantee profiles exist. You can only load a profile that an operator has agreed to supply for that chip and that remote manager. The capability is technical; the availability is commercial.
  • It doesn’t work on its own. The modem, its firmware and, under SGP.32, the IoT Profile Assistant all have to cooperate. I covered that in the SGP.32 readiness chain.
  • It isn’t the only way to get multi-network. A multi-network or multi-IMSI IoT SIM can roam across several UK and foreign networks from a single profile today. For many UK estates, that’s the simpler answer.
  • It doesn’t remove lock-in by itself. If one supplier owns the bootstrap profile and the remote manager, you have the chip that could switch and a contract that won’t let it.

Do you need an eUICC for IoT?

This is the bit that matters. My rough rule: the harder it is to reach the device, and the longer it has to last, the more an eUICC is worth. Here’s how that plays out.

Your situationeUICC?Why
Sealed or soldered device expected to last 10 years or moreYesNetworks, tariffs and technologies will change long before the device dies. Without an eUICC, so does the device.
Product built in one place and shipped to many countriesYesOne SKU, with the right local profile loaded after it arrives. Some countries restrict permanent roaming, which a local profile avoids.
Large fleet where a site visit costs more than the deviceUsuallyThe first operator change pays for the chip many times over.
You want leverage at contract renewalUsuallyOnly if you can also move the remote manager and bootstrap profile. Check before you buy.
Mains-powered router in a UK cabinet, removable SIM, five-year lifeProbably notA good multi-network IoT SIM covers it, and a SIM swap is a manageable job. A plastic eUICC remains an option later if the router supports it.
Tiny battery sensor in huge volumeDependsLook closely at chip cost, power draw during provisioning and whether an integrated SIM suits better.
Short trial or temporary deploymentNoKeep it simple. Spend the money on antennas and testing.

My take. I think of an eUICC as an insurance policy. You pay a bit more for the chip on day one so you don’t have to visit every device when something you can’t control changes: a network retires a technology, a supplier is bought, a customer moves the kit abroad. On a device you’ll never see again, that insurance is cheap. On a router you can reach in twenty minutes, it’s optional. The mistake is buying the policy and then signing a contract that won’t let you claim on it.

If you’re weighing up the connectivity side as well as the chip, IoT SIM connectivity after SGP.32 looks at how pricing and suppliers are shifting, and how operators actually deliver SGP.32 explains what’s going on behind the scenes when a profile lands.

What is an eUICC: quick answers

What does eUICC stand for?

Embedded Universal Integrated Circuit Card. Despite the name, an eUICC doesn’t have to be embedded: it is available as a soldered chip, a plastic SIM card or integrated into a modem chipset.

What is the difference between a UICC and an eUICC?

A UICC holds one operator profile, fixed when the SIM is made, so changing operator means changing the SIM. An eUICC can hold several profiles in isolated containers and have them downloaded, enabled or deleted remotely under GSMA specifications.

What are ISD-R, ECASD and ISD-P?

They are security domains inside an eUICC. The ECASD holds the chip’s certificate and keys to prove it is genuine. The ISD-R manages profiles, creating and enabling or deleting them. Each ISD-P is a sealed container holding one operator profile.

Do I need an eUICC for my IoT devices?

You most likely need one if devices are sealed, long-lived, deployed across several countries or expensive to visit. For an accessible router with a removable SIM and a multi-network IoT tariff, an eUICC is often unnecessary.

Can an eUICC connect to more than one network at once?

Usually not. A typical IoT eUICC stores several profiles but has one enabled at a time. For roaming across networks within one profile, a multi-network IoT SIM is the more common approach.

Sources: GSMA, SGP.22 RSP Technical Specification, section 2.4 eUICC architecture (ECASD, ISD-R, ISD-P); GSMA, SGP.31 v1.3 eSIM IoT Architecture and Requirements and SGP.32 v1.3 Technical Specification (May 2026); GSMA, eSIM specifications status table; An Overview of GSMA’s M2M Remote Provisioning Specification (arXiv 1906.02254). Diagram by IoTPortal.

The eSIM explained series: Part 1: eSIM vs eUICC · Part 2: What is an eUICC? (you are here) · Part 3: What is an eIM? · Part 4: SGP.32’s three-body problem