Ask ten hardware teams what they need and most will say "eSIM." Ask what they mean, and the answers split three ways: a soldered chip, remote profile management, or SIM functionality baked into the processor itself. Those are three different decisions with three different bills of materials, three different security evaluation paths, and three different answers to a question that matters more than any datasheet spec — how many times can this device change carriers over a ten-year life?
CSL's April 2026 technical guide covering eSIM, eUICC and iSIM, including the SGP.32 baseline and the emerging in-factory provisioning model, is a useful corrective. Here's the practical version for anyone specifying, sourcing, or manufacturing connected hardware.

Three Packages, Three Different Promises
eSIM describes where the chip sits
An eSIM is a form factor: the SIM chip soldered directly onto the device motherboard, replacing the removable tray. The standard MFF2 package measures 5mm × 6mm × 0.9mm. The benefits are physical — no tray to lose or pry out, a smaller board footprint, fewer mechanical failure points.
eUICC describes what the chip can do
An eUICC is the capability inside the secure element: remote download, activation, disable, delete, and storage of multiple operator profiles at once. This is what actually delivers remote SIM provisioning. It conforms to GSMA's consumer specs (SGP.21/22) or the IoT specs (SGP.31/32).
The assumption almost everyone gets wrong
Form factor and capability are independent. An eUICC can ship in a removable plug-in package and still support full remote provisioning — SGP.32 explicitly addresses removable eSIMs. So the widespread shorthand that "eSIM means you can't swap the card" is a packaging assumption, not a technical rule. If your product needs field-serviceability, that's still available.
iSIM pushes the secure element into the processor
iSIM integrates the SIM function directly into the device's system-on-chip, housed in an Integrated Tamper-Resistant Element (TRE). No separate package, no discrete eUICC component. The GSMA certification framing sits in SGP.08 (PP-0084 path) and SGP.18 (PP-0117 path).
What Actually Changes Between Them
The differences worth putting in a comparison table: removability, remote provisioning support, multi-profile support, where the secure hardware lives, and power profile. Traditional removable SIM: single profile, no remote provisioning, discrete security chip. eUICC: multi-profile, remote provisioning, discrete secure element. iSIM: integrated into silicon, potentially lower power overhead.
The security distinction that decides certification
This is where procurement conversations go wrong. A TEE — a trusted execution environment inside the main processor — provides logical isolation. A TRE is a hardened enclave with a physical boundary, resistant to fault injection, side-channel analysis and memory probing. GSMA integrated-eUICC compliance requires a certified TRE under SGP.08 or SGP.18. TEE-based designs exist in the wider market, but they are not the GSMA certification route for integrated eUICC. If a supplier markets a TEE implementation as "certified integrated eSIM," ask which protection profile and which evaluation path, in writing.
A live example of profile-side risk
GSMA's application note AN-2025-07, published 25 June 2025, addresses malicious Java Card application installation on test profiles that ship with publicly known RAM keys. Its requirements are unglamorous and specific: keep RAM keys confidential regardless of profile class, never mix test certificate issuers with live certificates on end-user devices, and enforce bytecode verification on all Java Card applications. SGP.24 v3.2.1 folded this attestation into the eUICC compliance declaration. For a card or module manufacturer, that means test and production credential handling needs to be a process control, not a footnote.

The Standards You're Actually Choosing Between
Consumer RSP — SGP.21/22
User-initiated profile management through the device UI. Introduces the Local Profile Assistant. Interfaces ES9+ and ES10, with multi-profile enablement support from v3.0 onward.
Legacy M2M — SGP.01/02
Automated, server-initiated provisioning through SM-DP and SM-SR, with profile delivery relying partly on SMS. That SMS dependency is precisely why it struggles on NB-IoT and LTE-M. It still runs millions of devices and does not need a forced migration — but it is not where new designs should go.
IoT RSP — SGP.31/32
The current baseline: SGP.32 v1.2, published 27 June 2024. The architecture adds an IoT Profile Assistant on the device and an eSIM IoT Remote Manager on the platform side, moving provisioning onto IP transport — HTTP/TLS for gateways, CoAP/DTLS for constrained links. It also defines fallback profiles, emergency profiles, rollback on failed installs, and test profiles for certification.
In-factory provisioning — SGP.41, with SGP.42 still pending
SGP.41 v1.0 (February 2025) defines the architecture for loading bound profile packages during manufacturing, so devices ship ready to attach on first power-up instead of downloading over the air. The technical specification, SGP.42, has not appeared in the current GSMA released set; industry sources describe it as under development. Pre-standard vendor implementations exist. Plan against what's published, not against a roadmap slide.
The Numbers, and How to Read Them
Operator support: 441+ operators offered eSIM services by mid-2024, with more than two-thirds of MNOs now providing eSIM smartphone connectivity. Shipments: roughly 9 billion eSIM/iSIM-capable devices projected by 2030, around 70% of cellular devices. IoT: 800 million eUICC/RSP-capable connections in 2025, forecast to 2.36 billion by 2032. iSIM: about 10 million devices projected in 2026 and 210 million connections by 2028 — still early-stage.
One caution the guide states plainly and worth repeating: these figures come from different analyst methodologies and measurement frames. Connections, shipments and operator counts are not additive and should not be treated as interchangeable.
Where iSIM Genuinely Makes Sense
Footprint, power, and long battery life
Compact wearables, medical devices, remote industrial sensors, and products chasing 10–15 year battery life are the natural first adopters. Eliminating a discrete package reduces component count and board area.
The constraints that decide timing
Only a limited set of chipsets support iSIM today, some early implementations are single-profile due to SoC constraints, toolchains need adaptation, and many operators have not enabled iSIM-specific provisioning flows. Integration and certification effort has to be justified by the application, not by the trend.
What This Means If You Build Hardware
Choose the provisioning model from deployment context
Devices configured through managed installer channels, operating under a single operator, or sitting in an estate with established connectivity workflows may see limited near-term value from a full OTA provisioning stack. Remote provisioning earns its keep where zero-touch deployment, dynamic operator switching, or single-SKU global logistics are real operational requirements.
Design SGP.32-compatible today, even if you ship M2M this quarter
Compatibility is cheaper to design in than to retrofit. New greenfield designs should target SGP.32 v1.2 as the forward baseline while existing estates keep running.
Budget for compliance as four layers, not one badge
Functional conformance (SGP.23 for consumer, SGP.33-1/-2/-3 for IoT roles), product security evaluation (SGP.25 plus PP-0084/PP-0117, or SGP.08/SGP.18 for integrated parts), the eSA assurance route, and site security accreditation (SAS-UP for production, SAS-SM for subscription management sites). Compliance status depends on all four, not on any single certificate.
For card and module makers specifically
Profile packaging, EID assignment under SGP.29, and strict separation of test versus live certificate infrastructure are now part of the product, not back-office detail. Get those wrong and the failure surfaces several time zones away, in a customer's field deployment.
Specifying embedded connectivity for a new product line and want the form factor, provisioning model, and certification path aligned before tooling is cut? Talk to us about card, module and credential hardware built for the full device lifecycle.

