eIM Integration
IoT.live integrates directly with eSIM vendor eIM APIs to provide unified orchestration of:
- eSIM lifecycle management
- Connectivity lifecycle management
- Fleet-scale operational workflows
- Remote SIM Provisioning (RSP)
The platform implements eIM integrations as part of its broader eSIM orchestration framework.
[IMAGE PLACEHOLDER: eIM integration architecture]
What is an eIM?
An eIM (eSIM IoT Manager) is responsible for managing Remote SIM Provisioning workflows within IoT eSIM deployments.
The eIM layer interfaces with:
- eSIM devices
- RSP workflows
- SMDP+ platforms
- Carrier systems
- Enterprise orchestration platforms
IoT.live integrates with eIM APIs to:
- Coordinate lifecycle operations
- Align connectivity and provisioning
- Execute fleet-scale orchestration workflows
Supported standards
The platform documentation references support for:
- GSMA SGP.22
- GSMA SGP.32
Including workflows involving:
- LPAe
- LPAd
- IPAe
- IPAd
These standards enable remote lifecycle management of eSIM profiles across enterprise IoT deployments.
eIM integration model
IoT.live integrates with the eSIM vendor's eIM APIs using dedicated Subscription Manager (SM) integrations.
The documentation describes:
- Each eIM integration as a dedicated SM Type
- Each customer integration having a unique IoT.live pod SM name
- SM names abstracting the underlying eIM implementation from end users
This allows users to interact through:
- The IoT.live UI
- Northbound APIs
- Automation workflows
without directly interacting with vendor-specific eIM implementations.
[IMAGE PLACEHOLDER: eIM abstraction model]
Integration prerequisites
The platform documentation outlines several recommended prerequisites for eIM integration.
Typical requirements include:
- Access to the eIM Fleet Management API
- Technical documentation for the eIM APIs
- API credentials
- A live tenant eIM account
- Sample eSIMs for validation and testing
The documentation also strongly recommends:
- Using profiles managed by CMPs already supported within IoT.live
- Validating carrier compatibility early
- Testing lifecycle alignment carefully
CMP integration alignment
A core IoT.live design principle is:
- Aligning eSIM lifecycle operations with:
- Connectivity lifecycle operations
This includes synchronising:
- Profile enablement
- CMP subscription activation
- Rate plan assignment
- Operational status changes
[IMAGE PLACEHOLDER: CMP and eIM lifecycle alignment]
Supported lifecycle operations
The eIM orchestration framework supports:
- Profile download
- Enable
- Disable
- Delete
- Download and Enable
- Change polling parameters
- Change eIM FQDN
Operations may also trigger:
- CMP activation
- Rate plan assignment
- Subscription state updates
- Batch operational workflows
Multi-vendor orchestration
The platform is designed to support orchestration across:
- Multiple eIM vendors
- Multiple CMPs
- Multiple carriers
- Multiple provisioning systems
This enables:
- Carrier flexibility
- Reduced vendor lock-in
- Unified operational workflows
- Enterprise-scale orchestration
Fleet-scale orchestration
eIM integrations support:
- Batch lifecycle operations
- Campaign management
- Automation workflows
- Async provisioning
- Operational reporting
Typical enterprise use cases include:
- Global IoT rollouts
- Bootstrap profile provisioning
- Multi-carrier orchestration
- Manufacturing onboarding
- Remote profile switching
[IMAGE PLACEHOLDER: Fleet-scale eIM orchestration]
Activation code integration
The platform also supports:
- Activation code management
- Activation code distribution
- Lifecycle tracking
- Reuse prevention
Activation code workflows may integrate directly with:
- eIM provisioning
- CMP onboarding
- Automated deployment operations
Async orchestration workflows
Large-scale provisioning operations may execute asynchronously.
Typical async workflows include:
- Fleet-wide provisioning
- Bulk enablement
- Mass profile migration
- Enterprise deployment campaigns
Recommended monitoring includes:
- Async status tracking
- Audit review
- Failed record exports
- Operational logging
Enterprise onboarding workflow
Typical onboarding process:
- Establish eIM API access
- Configure IoT.live SM integration
- Onboard compatible CMP accounts
- Validate lifecycle orchestration
- Test provisioning workflows
- Execute pilot deployments
- Scale operational automation
[IMAGE PLACEHOLDER: Enterprise onboarding workflow]
Security considerations
eIM integrations may affect:
- Live customer connectivity
- Carrier provisioning state
- Enterprise deployments
- Operational lifecycle management
Recommended controls include:
- Restricting provisioning permissions
- Auditing orchestration operations
- Monitoring async workflows carefully
- Separating testing and production environments
Incorrect lifecycle orchestration may disrupt connectivity or provisioning workflows across large production fleets.
Best practices
Recommended eIM integration practices include:
- Validate carrier and CMP compatibility early
- Test lifecycle alignment thoroughly
- Use staged deployment rollouts
- Monitor async operations fully
- Audit provisioning activity consistently
- Maintain strict operational change controls