eIM

An eIM (eSIM IoT Remote Manager) is the server that manages eSIM profiles on IoT devices in the GSMA SGP.32 architecture. It takes the place of the human user in consumer eSIM: instead of someone scanning a QR code, the eIM tells each device which profile to download and when to enable, disable or delete profiles.

What the eIM does

• Triggers profile downloads: it sends the device an activation code, an instruction to contact the default SM-DP+, or an instruction to query an SM-DS.
• Manages profile state: it signs eUICC Packages containing profile state operations — enable, disable, delete, list profiles — which the eUICC verifies before executing.
• Collects results: it receives signed execution results and notifications, so it knows each device’s actual profile state.
• Optionally proxies downloads: in indirect profile download, the eIM talks to the SM-DP+ itself and relays the encrypted profile to the device, which suits network-constrained devices that should talk to only one server.

How the eIM reaches devices

The eIM communicates with the IPA — the profile assistant in the device (IPAd) or in the eUICC (IPAe) — over the ESipa interface. SGP.32 v1.2 defines bindings over HTTPS and over CoAP with DTLS, with annexes for LwM2M and MQTT. The IPA can retrieve pending packages from the eIM, or the eIM can push them, depending on what both sides support. Separately, the logical ESep interface secures eUICC Packages end to end between eIM and eUICC, so the device in between cannot alter them.

Who runs an eIM

The eIM’s identity and credentials are configured on the eUICC, and an eUICC can be associated with more than one eIM. The eIM can therefore be operated by the device maker, the enterprise that owns the fleet, or a connectivity provider — unlike the SM-SR of SGP.02, which was usually fixed at manufacture.

Why it matters for testing

Each eIM instruction crosses several boundaries: eIM to IPA, IPA to eUICC, and device to SM-DP+ over a live cellular link. A profile that downloads correctly in the lab can still fail in the field because the device cannot reach the eIM over its bootstrap profile. SimCheck.ai can install profiles through a cloud eIM onto real modems and then verify attach and data on the new profile — see SGP.32 IoT eSIM testing.