Carrier Compatibility
IoT.live is designed to support enterprise IoT deployments across a broad range of:
- Carriers
- Connectivity Management Platforms (CMPs)
- eSIM vendors
- Provisioning environments
Carrier compatibility depends on:
- CMP support
- API availability
- Operational capabilities
- eSIM lifecycle support
- Reporting integration availability
[IMAGE PLACEHOLDER: Carrier compatibility overview]
Compatibility model overview
The platform documentation references compatibility across carriers using:
- Cisco Jasper
- Ericsson DCP / Aeris IoTA
- Vodafone GDSP
- Verizon ThingSpace
- Telefonica Kite
- Deutsche Telekom TMSP
- NetCracker environments
Compatibility is enabled through:
- API integrations
- Reporting integrations
- CMP aggregation
- Lifecycle orchestration frameworks
Compatibility validation requirements
Before onboarding a carrier environment, enterprises should validate:
- CMP compatibility
- API access availability
- Lifecycle management support
- Usage reporting support
- Batch operation capability
- eSIM orchestration compatibility
Recommended onboarding process:
- Confirm CMP support
- Validate API access
- Test inventory retrieval
- Validate lifecycle operations
- Test orchestration workflows
- Validate reporting behaviour
[IMAGE PLACEHOLDER: Carrier validation workflow]
Supported CMP ecosystems
The documentation references compatibility with CMP ecosystems including:
- Cisco Jasper
- Ericsson DCP
- Vodafone GDSP
- Verizon ThingSpace
- Telefonica Kite
- Deutsche Telekom TMSP
Each CMP ecosystem may expose:
- Different operational APIs
- Different provisioning capabilities
- Different lifecycle workflows
- Different reporting models
As a result, operational behaviour may vary between carriers.
eSIM compatibility considerations
eSIM compatibility may depend on:
- eIM API support
- SGP.22 support
- SGP.32 support
- Activation code workflows
- Profile lifecycle orchestration
- CMP lifecycle alignment
The documentation strongly recommends:
- Using CMPs already supported within IoT.live
- Validating eSIM orchestration behaviour early
- Testing lifecycle alignment workflows thoroughly
Multi-carrier operational alignment
The platform is designed to harmonise operational management across:
- Multiple carriers
- Multiple CMPs
- Multiple eIM vendors
- Multiple provisioning systems
This enables:
- Unified operational workflows
- Standardised lifecycle orchestration
- Centralised inventory visibility
- Fleet-scale automation
[IMAGE PLACEHOLDER: Multi-carrier orchestration model]
Operational capability differences
Operational capabilities may vary between carriers depending on:
- CMP implementation
- API maturity
- Regional deployment architecture
- Reporting support
- Provisioning integration availability
Capability differences may affect:
- Batch operations
- Async workflows
- Usage reporting
- Lifecycle updates
- eSIM orchestration support
Recommended practice:
- Validate workflows directly against target environments
- Avoid assuming identical behaviour across carriers
Reporting compatibility
Some carrier integrations support:
- Real-time API reporting
- Export-driven reporting
- Hybrid reporting models
- Historical operational feeds
Reporting capability differences may impact:
- Inventory synchronisation
- Usage visibility
- Operational monitoring
- Billing reconciliation
- Audit workflows
Enterprise deployment considerations
Large enterprise deployments should validate:
- Regional carrier support
- Roaming behaviour
- Provisioning workflows
- Lifecycle sequencing
- Operational automation compatibility
This is especially important for:
- Global IoT fleets
- Bootstrap provisioning models
- Multi-region deployments
- eSIM orchestration workflows
Carrier onboarding strategy
Recommended onboarding strategy:
- Validate carrier and CMP compatibility
- Configure API integration access
- Test lifecycle workflows
- Validate usage reporting
- Execute pilot deployment
- Expand deployment gradually
This staged approach reduces:
- Operational risk
- Provisioning conflicts
- Lifecycle inconsistencies
- Carrier-specific integration issues
[IMAGE PLACEHOLDER: Carrier onboarding lifecycle]
Compatibility benefits
Broad carrier compatibility enables:
- Reduced vendor lock-in
- Improved deployment flexibility
- Multi-carrier resiliency
- Regional optimisation
- Simplified global scaling
- Unified enterprise operations
This is particularly valuable for:
- Enterprise IoT deployments
- Global logistics
- Automotive telematics
- Smart infrastructure
- Industrial IoT
Security considerations
Carrier integrations may expose:
- Operational lifecycle controls
- Provisioning workflows
- Usage reporting
- Customer inventory
- Connectivity management systems
Recommended controls include:
- Restricting carrier integration access
- Auditing operational workflows
- Monitoring provisioning activity carefully
- Segregating testing and production environments
Carrier compatibility validation should always be completed before executing production orchestration workflows.
Best practices
Recommended carrier compatibility practices include:
- Validate compatibility early
- Test lifecycle orchestration thoroughly
- Confirm reporting behaviour carefully
- Monitor async operations fully
- Maintain carrier-specific operational documentation
- Use phased deployment rollouts for new carrier integrations