Supported MNOs & MVNOs
IoT.live supports orchestration and operational management across a broad ecosystem of:
- Mobile Network Operators (MNOs)
- Mobile Virtual Network Operators (MVNOs)
- Regional carriers
- Global connectivity providers
This multi-carrier support enables enterprises to build flexible, scalable, and globally distributed IoT deployments.
[IMAGE PLACEHOLDER: Global MNO and MVNO ecosystem]
Multi-carrier support overview
The platform documentation references support for carriers across:
- Europe
- North America
- Latin America
- Asia-Pacific
- Middle East
- Africa
Supported environments include carriers operating on:
- Cisco Jasper
- Ericsson DCP / Aeris IoTA
- Vodafone GDSP
- Verizon ThingSpace
- Telefonica Kite
- Deutsche Telekom TMSP
This enables unified operational management across diverse carrier ecosystems.
Global carrier coverage
The documentation references support for carriers including:
Europe
- Vodafone UK
- O2 UK
- Three UK
- Deutsche Telekom
- Telefonica
- Tele2
- Telia
- Swisscom
- Sunrise
- Telenor
North America
- AT&T
- Verizon
- T-Mobile
- Rogers
- Bell
- Telus
Asia-Pacific
- NTT Docomo
- Softbank
- KDDI
- Singtel
- Telstra
- Optus
- China Mobile
- China Telecom
- China Unicom
Middle East & Africa
- STC
- Ooredoo
- Etisalat
- du
- MTN
[IMAGE PLACEHOLDER: Global carrier coverage map]
Multi-CMP carrier environments
Many carriers operate using different Connectivity Management Platforms (CMPs).
Examples from the documentation include:
- Cisco Jasper deployments
- Ericsson DCP deployments
- Vodafone GDSP environments
- Hybrid operational platforms
This means operational capabilities may vary depending on:
- Carrier implementation
- CMP platform
- API support
- Regional deployment model
Carrier orchestration benefits
Supporting multiple carriers enables enterprises to:
- Avoid vendor lock-in
- Expand regional coverage
- Improve resiliency
- Optimise operational flexibility
- Support bootstrap provisioning workflows
- Enable multi-carrier eSIM orchestration
This is particularly valuable for:
- Global IoT fleets
- Roaming-sensitive deployments
- Regulatory-driven deployments
- Enterprise resilience strategies
Regional deployment flexibility
The supported carrier ecosystem enables:
- Regional connectivity optimisation
- Carrier-specific provisioning
- Multi-country deployments
- Cross-border operational management
Typical deployment examples include:
- European fleet management
- North American logistics deployments
- APAC manufacturing deployments
- Global telematics infrastructure
[IMAGE PLACEHOLDER: Regional orchestration workflow]
MVNO support considerations
The platform may support MVNO environments where:
- API integrations are available
- CMP compatibility exists
- Operational onboarding requirements are met
MVNO support may depend on:
- Underlying CMP architecture
- Carrier integration capability
- API access availability
- Operational compatibility
eSIM orchestration across carriers
The multi-carrier architecture enables:
- Remote profile switching
- Bootstrap connectivity models
- Carrier migration workflows
- Global provisioning strategies
- Multi-operator orchestration
This supports:
- SGP.22 workflows
- SGP.32 orchestration
- eIM integration models
- Fleet-scale lifecycle management
Carrier onboarding considerations
Successful carrier onboarding may require:
- CMP compatibility validation
- API credential provisioning
- Operational testing
- Lifecycle workflow validation
- Reporting integration verification
Recommended onboarding approach:
- Validate supported CMP compatibility
- Configure API integration access
- Test lifecycle workflows
- Validate reporting visibility
- Execute pilot deployments
Operational capability differences
Operational capabilities may vary between carriers depending on:
- CMP implementation
- API maturity
- Regional support models
- Reporting availability
- Lifecycle management support
Examples of variable capabilities may include:
- Batch operations
- Real-time lifecycle updates
- Usage reporting granularity
- eSIM lifecycle alignment
- Provisioning automation
Multi-carrier governance
Enterprises operating across multiple carriers should implement:
- Standardised operational workflows
- Unified lifecycle governance
- Inventory segmentation
- Audit tracking
- Async monitoring
- Carrier-specific validation processes
[IMAGE PLACEHOLDER: Multi-carrier governance model]
Security considerations
Carrier integrations may expose:
- Operational lifecycle controls
- Provisioning systems
- Usage reporting
- Customer inventory
- Billing-related workflows
Recommended controls include:
- Restricting carrier integration access
- Auditing operational activity
- Monitoring provisioning workflows carefully
- Segregating production and testing environments
Carrier integrations may directly impact live production connectivity services across large enterprise fleets.
Best practices
Recommended multi-carrier operational practices include:
- Validate carrier compatibility early
- Standardise lifecycle workflows where possible
- Test provisioning behaviour carefully
- Monitor async orchestration workflows fully
- Segment fleets logically across carriers
- Maintain carrier-specific operational documentation