Insights

Physical SIM vs eSIM for IoT: a deployment decision framework

Quanqiu IoT ·

Rugged generic IoT enclosure with a physical SIM tray and an abstract embedded eSIM circuit view on a laptop
Conceptual physical SIM versus eSIM integration scene; not a specific product or customer laboratory.

Start with the device and installation reality

For a physical SIM, confirm the form factor, access after installation, environmental protection, replacement method and whether the device can be opened without invalidating the installation process. For eSIM, confirm the actual eUICC, supported profile operations, device-side software and the remote manager relationship. Do not infer eSIM capability from a product page that only says cellular or dual-SIM.

The GSMA index shows that eSIM IoT specifications and test versions have status and version distinctions. Record the exact device and specification claims that the vendor can substantiate before treating eSIM as a deployment feature.

[1] [2]

Side-by-side comparison

The table summarizes what each delivery model requires, based on the ETSI card standards and GSMA eSIM descriptions. Use it to structure the pilot, not as proof that a specific device or service supports a capability.

Removable physical SIM versus eSIM (eUICC) for IoT deployments
AspectRemovable physical SIMeSIM (eUICC)
How the subscription reaches the deviceA card in a standard format (plug-in, mini-UICC or 4FF) is shipped and insertedAn operator profile is downloaded into a secure element embedded in the device
Device prerequisiteA slot or holder for the chosen card formatAn eUICC plus support for the applicable GSMA eSIM specification, such as SGP.32 for IoT devices
Changing the subscription laterPhysical access to replace the cardA remote profile operation, only if the device, eUICC and service support it
Environmental ratingAsk for the ETSI TS 102 671 environmental class stringThe same question applies to the embedded package, for example MFF2
Pilot evidence to collectInsertion, registration, data session and a card replacementProfile download, activation, a profile change if in scope and recovery after an interrupted operation

[4] [5] [6] [1] [2]

Assign provisioning and lifecycle ownership

Ask who requests a profile, authorizes installation, changes or disables it, monitors state and handles a device that is offline. Define the handover between OEM, integrator, connectivity supplier, operator and end customer. A CMP may provide useful lifecycle visibility, but its actual permissions, API and alert behavior must be confirmed for the proposed service.

For remote or sealed devices, eSIM may reduce physical intervention, but it does not remove the need for identity, authorization, rollback and support procedures. NIST's catalog is useful for turning those risks into device and access questions.

[2] [3]

Use a pilot to test the full path

Test activation or profile installation, first registration, APN and data session, application reachability, profile change or replacement if in scope, and recovery after a failed or interrupted operation. Run the cases on the intended country, hardware revision and firmware. Keep a physical-SIM path in the comparison when field replacement is important.

Bring quantities, countries, device models, installation life, expected traffic, eSIM requirements and pilot evidence to the buying discussion. Catalog pricing can be a starting point; request a project quote when provisioning ownership, device variants or lifecycle coordination are material to the outcome.

[1] [3]

Frequently asked questions

Is eSIM always better than a physical SIM for IoT?

No. The better choice depends on device design, field access, profile workflow, ownership, lifecycle requirements and verified compatibility.

Does eSIM automatically provide multi-network or multi-operator service?

No. Profile capability, commercial arrangement, device support and network policy must be confirmed separately.

What should an eSIM inquiry include?

Include eUICC/device details, countries, quantities, profile or provisioning needs, owners of lifecycle actions, traffic, pilot cases and required CMP or API scope.

Official references

  1. GSMA eSIM Consumer and IoT Specifications
  2. GSMA SGP.32 v1.2 overview
  3. NIST IoT Cybersecurity Capabilities Catalog
  4. ETSI TS 102 221 V18.0.0 (2023-05) Smart Cards; UICC-Terminal interface; Physical and logical characteristics
  5. ETSI TS 102 671 V16.0.0 (2022-11) Smart Cards; Machine to Machine UICC; Physical and logical characteristics
  6. GSMA: What is an eSIM? Guide to eSIM technology and use cases

Related reading

More insights

Share your device design, deployment countries and provisioning requirements with Quanqiu IoT to compare physical SIM and eSIM paths.

Discuss your project