SGP.22 & SGP.32 Support
IoT.live supports enterprise eSIM orchestration workflows aligned with:
- GSMA SGP.22
- GSMA SGP.32
The platform is designed to support Remote SIM Provisioning (RSP) operations across multiple eSIM vendors, carriers, and Connectivity Management Platforms (CMPs).
[IMAGE PLACEHOLDER: SGP.22 and SGP.32 architecture overview]
GSMA eSIM standards overview
The GSMA specifications define standardised approaches for Remote SIM Provisioning (RSP).
IoT.live documentation references support for:
- SGP.22
- SGP.32
Including:
- LPAe
- LPAd
- IPAe
- IPAd
These standards enable remote lifecycle management of eSIM profiles across IoT deployments.
SGP.22 support
SGP.22 is commonly associated with:
- eSIM profile download workflows
- LPA-based device management
- Enterprise-driven provisioning
- Remote lifecycle operations
The platform supports orchestration workflows involving:
- Profile download
- Enable
- Disable
- Delete
- Lifecycle alignment with CMP operations
[IMAGE PLACEHOLDER: SGP.22 workflow]
SGP.32 support
SGP.32 extends eSIM orchestration capabilities for IoT-focused deployments.
The platform documentation references:
- IPAe
- IPAd
- eIM integration workflows
- Fleet-scale orchestration
- Automated provisioning operations
SGP.32 workflows are designed to support:
- Large-scale IoT deployments
- Automated provisioning
- Enterprise orchestration
- Zero-touch onboarding models
[IMAGE PLACEHOLDER: SGP.32 workflow]
eIM integration model
The platform integrates with:
- eIM APIs
- CMP APIs
- RSP operational workflows
This creates a unified orchestration layer between:
- Connectivity management
- eSIM lifecycle management
- Carrier provisioning systems
The platform documentation describes this as:
- A unified connectivity and eSIM management framework
- A single-pane operational model
- Fleet-scale orchestration
[IMAGE PLACEHOLDER: eIM orchestration architecture]
Supported lifecycle operations
Supported eSIM lifecycle operations include:
- Download
- Enable
- Download and Enable
- Disable
- Delete
- Change polling parameters
- Change eIM FQDN
These operations may be combined with:
- CMP subscription activation
- Rate plan assignment
- Batch operations
- Campaign processing
Lifecycle alignment with CMPs
A key operational challenge in eSIM deployments is ensuring that:
- eSIM profile state
- Connectivity lifecycle state
remain synchronised.
Example scenarios include:
- Activating a profile while also enabling the CMP subscription
- Assigning the correct rate plan after profile enablement
- Preventing fallback profile activation
- Coordinating provisioning across multiple systems
[IMAGE PLACEHOLDER: CMP and eSIM lifecycle alignment]
Multi-vendor orchestration
The platform is designed to support orchestration across:
- Multiple eIM vendors
- Multiple CMP types
- Multiple carriers
- Multiple RSP environments
This enables enterprises to:
- Avoid vendor lock-in
- Expand carrier flexibility
- Standardise operational workflows
- Centralise orchestration
Zero-touch provisioning goals
The documentation describes a goal of:
- End-to-end zero-touch eSIM operations
- Reduced supply chain friction
- Automated lifecycle alignment
- Self-onboarding workflows
Typical operational workflows may include:
- Manufacturing onboarding
- Bootstrap provisioning
- Automated carrier activation
- Fleet-wide orchestration
[IMAGE PLACEHOLDER: Zero-touch provisioning workflow]
Operational orchestration workflows
Compound orchestration workflows may include:
- Download profile
- Enable profile
- Activate subscription on CMP
- Assign rate plan
- Update operational state
- Execute reporting and audit tracking
These workflows may be:
- Automated
- Scheduled
- Batched
- Executed asynchronously
Enterprise deployment benefits
SGP.22 and SGP.32 orchestration support provides:
- Carrier flexibility
- Remote lifecycle control
- Reduced operational complexity
- Fleet-scale automation
- Improved provisioning efficiency
- Centralised operational visibility
Security considerations
Remote SIM provisioning operations may affect:
- Live production connectivity
- Carrier provisioning state
- Enterprise deployments
- Operational availability
Recommended controls include:
- Restricting provisioning permissions
- Auditing orchestration workflows
- Monitoring async lifecycle operations
- Validating operational sequencing carefully
Incorrect lifecycle alignment between eSIM state and CMP state may disrupt production connectivity services.
Best practices
Recommended SGP.22 and SGP.32 operational practices include:
- Validate CMP compatibility early
- Test orchestration workflows carefully
- Monitor async operations fully
- Align lifecycle and connectivity operations together
- Use staged rollout strategies for large deployments
- Audit provisioning operations consistently