CMP Integration Types
IoT.live supports multiple Connectivity Management Platform (CMP) integration models to accommodate:
- Different carrier technologies
- Legacy operational systems
- Modern REST-based platforms
- Reporting-driven integrations
- Hybrid operational environments
This flexibility allows enterprises to unify operations across diverse carrier ecosystems and provisioning platforms.
[IMAGE PLACEHOLDER: CMP integration type overview]
Integration model overview
The platform documentation references several integration approaches including:
- Pure SOAP API integrations
- Pure REST API integrations
- Hybrid API integrations
- API and reporting feed combinations
- CMP-specific operational connectors
These integration types enable IoT.live to support:
- Multi-carrier orchestration
- Unified inventory visibility
- Lifecycle management
- Usage reporting
- eSIM orchestration workflows
Pure SOAP API integrations
Some CMP environments are integrated using:
- SOAP APIs
- XML-based workflows
- Legacy operational service models
The documentation references SOAP integrations for platforms including:
- Cisco Jasper
- Vodafone GDSP
- Ericsson DCP environments
SOAP integrations may support:
- Inventory operations
- Lifecycle management
- Usage retrieval
- Provisioning workflows
- Operational reporting
[IMAGE PLACEHOLDER: SOAP integration workflow]
Pure REST API integrations
Modern CMP integrations may use:
- REST APIs
- JSON payloads
- HTTPS operational workflows
The documentation references REST integrations for:
- Cisco Jasper
- Verizon ThingSpace
- Deutsche Telekom TMSP
- T-Mobile NetCracker
REST integrations may provide:
- Improved operational responsiveness
- Simplified automation
- Modern orchestration workflows
- Enhanced API scalability
Hybrid API integrations
Some carrier environments use:
- Hybrid SOAP and REST integrations
- Combined operational interfaces
- Mixed lifecycle management models
Hybrid integrations may exist where:
- Carrier platforms evolved over time
- Operational systems remain partially legacy-based
- Reporting and lifecycle operations use different interfaces
This allows IoT.live to support:
- Complex carrier ecosystems
- Transitional operational models
- Mixed provisioning architectures
[IMAGE PLACEHOLDER: Hybrid integration architecture]
API and reporting feed integrations
Some CMP integrations combine:
- API operations with:
- Reporting or export feeds
The documentation references hybrid models using:
- APIs for lifecycle management
- Reporting feeds for operational visibility
- Export-driven synchronisation workflows
These integrations may improve:
- Historical reporting
- Usage analysis
- Inventory reconciliation
- Operational auditing
Carrier-specific integration models
Different carriers may expose:
- Different operational APIs
- Different lifecycle capabilities
- Different provisioning models
- Different reporting mechanisms
As a result:
- Operational behaviour may vary
- Lifecycle capabilities may differ
- Async workflows may behave differently
- Reporting granularity may vary
Recommended practice:
- Validate operational behaviour during onboarding
- Test lifecycle workflows carefully
- Confirm reporting capabilities early
CMP aggregation framework
IoT.live uses a CMP aggregation model to abstract:
- Carrier-specific APIs
- Operational differences
- Lifecycle inconsistencies
- Reporting variations
This creates:
- Unified operational workflows
- Standardised orchestration logic
- Centralised inventory visibility
- Simplified enterprise automation
[IMAGE PLACEHOLDER: CMP aggregation framework]
eSIM orchestration alignment
CMP integrations are also aligned with:
- eIM integrations
- Remote SIM Provisioning workflows
- eSIM lifecycle orchestration
- SGP.22 and SGP.32 operational models
This enables:
- Unified lifecycle management
- Connectivity and eSIM synchronisation
- Automated orchestration workflows
- Fleet-scale provisioning
Operational capability considerations
Supported operational capabilities may include:
- Inventory retrieval
- Status updates
- Rate plan management
- Batch operations
- Usage reporting
- Async provisioning
- eSIM lifecycle alignment
Capability availability depends on:
- Carrier implementation
- CMP API maturity
- Integration type
- Regional deployment model
Enterprise onboarding considerations
When onboarding new CMP integrations, enterprises should validate:
- API availability
- Authentication requirements
- Lifecycle support
- Batch operation support
- Reporting capabilities
- Async operational behaviour
Recommended onboarding workflow:
- Validate CMP compatibility
- Configure API credentials
- Test lifecycle operations
- Validate reporting visibility
- Test orchestration workflows
- Execute pilot deployments
Integration architecture benefits
Supporting multiple integration models provides:
- Carrier flexibility
- Reduced operational friction
- Legacy system compatibility
- Simplified enterprise onboarding
- Broader global carrier support
This is especially valuable for:
- Global deployments
- Multi-carrier orchestration
- Enterprise migration projects
- eSIM fleet management
Security considerations
CMP integrations may expose:
- Provisioning workflows
- Subscription lifecycle controls
- Usage reporting
- Operational inventory
- Customer deployment data
Recommended controls include:
- Restricting integration access
- Auditing operational workflows
- Monitoring async processing carefully
- Segregating testing and production environments
CMP integrations may directly affect live production subscriptions and provisioning workflows.
Best practices
Recommended CMP integration practices include:
- Validate carrier behaviour carefully
- Test lifecycle operations thoroughly
- Standardise orchestration workflows where possible
- Monitor async operations fully
- Maintain integration-specific operational documentation
- Align CMP lifecycle management with eSIM orchestration workflows