Table of Contents
As IoT deployments expand across transportation, industrial monitoring, smart metering, and connected equipment, businesses need ways to manage mobile subscriptions without physically replacing SIM cards. The GSMA SGP.32 specification defines a remote SIM provisioning architecture for IoT devices, including equipment with limited user interfaces or constrained network connectivity. Within this architecture, eIM and SM-DP+ perform different but complementary functions, working with the device-side IPA and eUICC to support remote profile provisioning and management.
The Responsibilities of eIM and SM-DP+ in SGP.32
The eIM, or eSIM IoT Remote Manager, coordinates remote eSIM management operations. It communicates with the device-side IoT Profile Assistant (IPA) and coordinates supported profile operations, including profile downloads and lifecycle management. For businesses managing large numbers of connected devices, an esim iot remote manager provides a management layer for coordinating these operations across a distributed fleet.
SM-DP+, short for Subscription Manager Data Preparation Plus, has a different responsibility. It prepares operator subscription profiles and protects them for secure delivery to the eUICC. The mobile operator supplies the subscription-related information required for profile preparation, while SM-DP+ handles the relevant profile preparation and delivery functions.
The two components therefore serve distinct roles. The eIM coordinates remote management, while SM-DP+ prepares and securely delivers the subscription profile. Their interaction allows the provisioning process to take place through standardized interfaces rather than depending on physical SIM replacement. SGP.32 defines how these components interact with other elements in the remote provisioning architecture.
How IPA and eUICC Support Device-Side Remote Provisioning
On the device side, the IPA and eUICC enable the remote provisioning process. The IPA, or IoT Profile Assistant, facilitates communication between the remote management infrastructure and the eUICC. Depending on the device implementation, it can operate as IPAd within the IoT device or as IPAe within the eUICC.
The eUICC is the secure element that stores and manages operator subscription profiles. When a new profile is provisioned, the eUICC processes the profile through the applicable secure procedures. This allows compatible IoT devices to receive and manage subscription profiles remotely instead of requiring a technician to replace a physical SIM.
The division of responsibilities is important: the eIM coordinates management operations, the IPA facilitates device-side communication, and the eUICC handles the profile within its secure environment. Together, these components connect remote provisioning instructions with the operations performed on the device.
From Profile Preparation to Download and Device Enablement
A typical SGP.32 provisioning process begins when a mobile operator arranges for a subscription profile to be prepared by SM-DP+. The profile is prepared and protected for delivery through the specified provisioning process.
The eIM then coordinates the required remote operation with the device-side IPA and the relevant profile infrastructure. Through the defined interfaces, the profile can be downloaded to the target eUICC. The IPA facilitates communication, while the eUICC processes and installs the profile according to the applicable security and provisioning procedures.
After installation, the profile may be enabled through an authorized operation. Once enabled, it can provide the subscription credentials needed for the device to access the associated mobile network, subject to operator service and network availability. Profile download and profile enablement are separate operations, and the exact workflow depends on the implementation and deployment requirements.
This process allows supported IoT devices to receive subscription profiles remotely. It also reduces dependence on physical SIM handling when connectivity requirements change during a device’s service life.
How These Components Support IoT eSIM Remote Provisioning
The eIM, SM-DP+, IPA, and eUICC work together as parts of a coordinated architecture. SM-DP+ prepares the subscription profile; the eIM coordinates remote management; the IPA facilitates communication with the device; and the eUICC securely installs and manages the profile. SGP.32 defines the interfaces and procedures that allow these elements to cooperate within a compatible implementation.
For IoT service providers, device manufacturers, and mobile operators, this architecture supports remote profile management across distributed fleets. It can help simplify connectivity administration for applications such as smart meters, industrial sensors, transportation equipment, and connected vehicles, where physical access to each device may be difficult or costly.
Through its eSIM IoT manager platform, BHDC supports SGP.32-based IoT eSIM remote management and integration with compatible profile servers. Understanding how eIM, SM-DP+, IPA, and eUICC divide their responsibilities helps organizations assess the components and interfaces needed for their provisioning projects.
Remote IoT eSIM provisioning depends on the coordinated operation of these components rather than on a single platform alone. When the relevant systems and devices are compatible, the architecture provides a standardized foundation for downloading, enabling, and managing subscription profiles across IoT deployments.
For businesses planning IoT connectivity projects, BHDC provides a starting point for exploring its connectivity solutions and assessing how eSIM management capabilities may fit their deployment requirements.
