When evaluating IoT connectivity options, you’ll encounter three distinct types of providers: Mobile Network Operators (MNOs), Mobile Virtual Network Operators (MVNOs), and IoT connectivity providers (a broader category that can include both). Understanding the structural differences between these models—and why those differences matter for your deployment—is essential for making an informed decision.
The terminology confusion is real: not all “IoT connectivity providers” are created equal. Some own and operate core network infrastructure (MNOs), while others resell capacity from those who do (MVNOs). A third category sits somewhere in between, layering management platforms on top of wholesale connectivity agreements.
This guide breaks down the actual technical, operational, and commercial differences between these models—and explains when each might (or might not) be the right choice for your IoT deployment.
What Is an MNO? (Mobile Network Operator)
An MNO (Mobile Network Operator) is a telecommunications company that owns, operates, and maintains its own core network infrastructure, radio access network (RAN), and spectrum licenses, allowing it to provide cellular connectivity services directly without relying on third-party networks.
What MNOs Own and Control:
- Core Network Infrastructure
- Home Location Register (HLR) / Home Subscriber Server (HSS)
- Packet Core (EPC for LTE, 5GC for 5G)
- Authentication and billing systems
- Gateway GPRS Support Nodes (GGSN) / Packet Data Network Gateways (PDN-GW)
- Radio Access Network (RAN)
- Cell towers and base stations
- Radio equipment (eNodeBs for LTE, gNodeBs for 5G)
- Backhaul infrastructure
- Spectrum Licenses
- Licensed frequency bands from government regulators
- Exclusive right to use specific radio frequencies
- Interconnection Agreements
- Direct peering with other MNOs globally
- Control over roaming agreements and pricing
- Internet backbone connections
Key Characteristics of MNOs:
- ✅ Direct network control — Full visibility and control over network performance, traffic prioritization, and troubleshooting
- ✅ Own SLA accountability — Not dependent on third parties for uptime commitments
- ✅ Network optimization capability — Can tune network parameters specifically for IoT traffic patterns
- ✅ Long-term infrastructure investment — Incentivized to maintain and upgrade network for 10-20+ year IoT device lifecycles
- ✅ Direct support— Technical issues resolved internally, not escalated to another organization
Examples of MNOs:
- Traditional telcos: Vodafone, AT&T, T-Mobile, Orange, Telefónica (operate in specific countries/regions)
- IoT-focused MNOs: OV (global IoT MNO with owned infrastructure across 180+ countries)
OV’s MNO status: OV owns and operates core network infrastructure globally, with direct interconnections to 600+ networks across 180+ countries. This means when you deploy an OV SIM, you’re connecting to OV’s own network—not roaming on a third party’s infrastructure.
What Is an MVNO? (Mobile Virtual Network Operator)
An MVNO (Mobile Virtual Network Operator) is a wireless communications provider that does not own its own radio spectrum or core network infrastructure, instead purchasing wholesale cellular access from one or more MNOs and reselling it to end customers—often with added value-added services like custom billing, platforms, or support.
What MVNOs Do NOT Own:
- ❌ Core network infrastructure
- ❌ Radio access network (cell towers, base stations)
- ❌ Spectrum licenses
- ❌ Direct control over network performance or prioritization
What MVNOs Do Control:
- ✅ Customer relationship and billing
- ✅ Value-added platforms (connectivity management, analytics)
- ✅ Customer support and account management
- ✅ SIM provisioning and lifecycle management
- ✅ Commercial agreements with multiple host MNOs (in some cases)
MVNO Business Models:
There are different levels of MVNO integration:
- Thick MVNO
- Operates some core network elements (HLR, AuC, sometimes packet core)
- More control over services and customer experience
- Higher investment and operational complexity
- Thin MVNO
- Minimal infrastructure ownership
- Relies heavily on host MNO for network functions
- Lower capex, but less differentiation capability
- MVNE-Enabled MVNO
- Uses Mobile Virtual Network Enabler (MVNE) as intermediary
- MVNE provides platform and integration to host MNO
- Lightest-weight model
Key Characteristics of MVNOs:
- ✅ Lower infrastructure costs — No need to build/maintain network
- ✅ Faster market entry — Can launch services without spectrum licenses or RAN deployment
- ✅ Specialization potential — Can focus on specific verticals or customer segments
- ❌ Dependent on host MNO — Limited control over network performance, coverage, or prioritization
- ❌ Indirect troubleshooting — Network issues require escalation to host MNO
- ❌ Potential SLA limitations — Can only offer SLAs as strong as host MNO provides
- ❌ Commercial constraints — Pricing and coverage determined by wholesale agreements
Examples of IoT MVNOs:
- Wireless Logic (UK-based, resells capacity from multiple MNOs)
- Pelion (IoT connectivity platform layer on top of wholesale agreements)
- 1NCE (MVNO with fixed-lifetime pricing model)
Important distinction: Many IoT “connectivity providers” are actually MVNOs—they provide excellent platforms and services, but they’re reselling connectivity from underlying MNOs rather than operating their own networks.
IoT Connectivity Provider: The Broader Category
“IoT connectivity provider” is a catch-all term that can include:
- MNOs offering IoT connectivity (e.g., OV, Vodafone IoT)
- IoT-focused MVNOs (e.g., Wireless Logic, Hologram)
- Platform providers (companies offering connectivity management but sourcing from multiple underlying MNOs/MVNOs)
- Hybrid models (MNOs with MVNO relationships in some markets, owned infrastructure in others)
When evaluating an “IoT connectivity provider,” the critical question is: What is their relationship to the underlying network infrastructure?
MNO vs MVNO: Technical Comparison
When MNO vs MVNO Differences Actually Matter
Scenario 1: Mission-Critical Applications
Use Case: Payment terminals (POS), healthcare devices, lone worker safety, telecare
Why MNO Matters:
- Direct SLA accountability — If network fails, the MNO owns the entire stack and can troubleshoot without third-party dependencies
- Network prioritization— MNOs can ensure IoT traffic gets priority during network congestion
- Redundancy and failover — True multi-network redundancy requires direct interconnections, not daisy-chained roaming agreements
Example: A payment terminal processing £10,000 in daily transactions cannot afford connectivity failures due to MVNO-host MNO relationship issues or delayed troubleshooting escalations.
OV’s approach: As an MNO, OV provides 99.9% uptime SLAs backed by owned infrastructure. When an issue occurs, our technical team has direct access to core network logs and can resolve problems without escalating to a third party.
Scenario 2: Global Deployments
Use Case: Asset tracking, fleet management, international logistics
Why MNO Matters:
- Direct peering agreements — MNOs establish direct interconnections with networks globally, avoiding multi-hop roaming complexity
- Multi-IMSI architecture — True MNOs can provision SIMs with multiple network profiles they directly own/operate
- Local presence — MNOs often have infrastructure and support teams in deployment regions
Example: A shipping company tracking containers from Shanghai to Rotterdam needs connectivity that works seamlessly across Asia, Europe, and transit routes—without relying on cascading roaming agreements that introduce latency, cost unpredictability, or coverage gaps.
MVNO limitation: MVNOs rely on their host MNO’s roaming agreements. If the host MNO has poor agreements in a specific region, the MVNO’s customers are affected—even if other networks in that region would provide better coverage.
Scenario 3: Long-Lifecycle Devices
Use Case: Smart meters, infrastructure sensors, industrial equipment (10-15 year deployments)
Why MNO Matters:
- Infrastructure longevity — MNOs have long-term incentive to maintain networks (they own the assets)
- Network evolution support — MNOs control migration paths from 2G/3G sunset to LTE/5G
- Commercial stability — MVNO-host MNO relationships can change; if a host MNO exits a market or changes terms, MVNOs (and their customers) are impacted
Example: A utility deploying 100,000 smart meters with a 15-year expected lifespan needs confidence that the connectivity provider will still exist—and still support those devices—in 2040.
MVNO risk: If the MVNO’s commercial agreement with its host MNO changes (pricing increase, coverage reduction, relationship termination), the MVNO’s customers are forced to migrate SIMs or accept degraded service.
Scenario 4: High-Volume, Price-Sensitive Deployments
Use Case: Consumer IoT, low-cost trackers, mass-market connected devices
When MVNO Might Be Sufficient:
- Applications where occasional connectivity loss is acceptable
- Devices with short lifecycles (2-3 years)
- Deployments focused in single countries with strong MVNO-host MNO relationships
MVNO advantage: Lower infrastructure overhead can sometimes translate to competitive pricing for specific use cases.
However: For global, long-lifecycle, or mission-critical deployments, the total cost of ownership (including downtime risk, migration costs, and troubleshooting delays) often favors MNO providers despite potentially higher per-MB pricing.
The “Multi-Network” Claim: MNO vs MVNO Reality
Marketing claim: “We offer multi-network IoT SIMs with global coverage.”
The reality depends on provider type:
MNO Multi-Network Implementation:
How it works:
- MNO establishes direct interconnection agreements with multiple networks globally
- MNO provisions Multi-IMSI SIMs with profiles from networks they have direct relationships with
- Device automatically selects strongest available network from SIM’s stored profiles
- All networks in the Multi-IMSI SIM are “first-hop” connections (no roaming overhead)
Key advantage: True network redundancy. If one network fails, device switches to a different network the MNO directly interconnects with.
OV example: OV’s Multi-IMSI SIMs contain profiles from 600+ networks across 180+ countries. These are direct interconnections, not roaming agreements—meaning lower latency, better reliability, and OV’s own SLA coverage across all networks.
MVNO Multi-Network Implementation:
How it works (typical):
- MVNO purchases wholesale access from one or more host MNOs
- MVNO provisions SIMs that roam on the host MNO’s partner networks
- Device connects via host MNO’s roaming agreements (not direct to alternative networks)
Key limitation: Multi-hop dependency. MVNO → Host MNO → Roaming Partner Network. If the host MNO’s roaming agreement with a network has issues, the MVNO’s customers are affected.
Example scenario:
- MVNO partners with Host MNO A
- Host MNO A has roaming agreement with Network B in Country X
- Device in Country X connects: Device → MVNO (SIM) → Host MNO A → Network B
- If Host MNO A and Network B have a commercial dispute and the roaming agreement terminates, the MVNO’s devices in Country X lose connectivity—even if the MVNO has no direct involvement in the dispute.
Contrast with MNO: An MNO can establish a direct interconnection with Network B, eliminating the multi-hop dependency.
Questions to Ask When Evaluating Providers
1. “Are you an MNO or MVNO?”
Why it matters: Determines who owns the network infrastructure and controls SLAs.
Red flag answers:
- “We’re a connectivity platform provider” (vague—doesn’t answer the question)
- “We partner with leading networks globally” (likely MVNO)
- “We have agreements with multiple carriers” (MVNO reselling roaming)
Clear answers:
- “We are an MNO with owned core network infrastructure in [regions]”
- “We are an MVNO reselling capacity from [host MNO names]”
2. “Do you own your core network infrastructure?”
What to listen for:
- MNO: “Yes, we operate our own HLR/HSS, packet core, and gateway infrastructure”
- MVNO: “We use [host MNO]’s core network” or “We operate a platform layer on top of wholesale connectivity”
3. “What happens if I have a network connectivity issue at 2am on a Sunday?”
Why it matters: Reveals troubleshooting and support structure.
MNO answer: “Our 24/7 NOC has direct access to network logs and core infrastructure. We can diagnose and resolve issues without third-party dependencies.”
MVNO answer: “We’ll escalate to our host MNO’s support team” or “We’ll open a ticket with the underlying carrier.”
Impact: For mission-critical applications, third-party escalation delays can be unacceptable.
4. “How do you implement ‘multi-network’ connectivity?”
Why it matters: Determines if you’re getting true redundancy or cascading roaming agreements.
MNO answer: “We have direct interconnections with [X] networks globally. Our Multi-IMSI SIMs contain profiles we provision directly from those networks.”
MVNO answer: “We use roaming agreements through our host MNO partners” or “We source connectivity from multiple wholesale providers.”
5. “What is your relationship with the networks my devices will connect to?”
Why it matters: Commercial relationship stability affects long-term service continuity.
MNO answer: “We own the infrastructure” or “We have direct bilateral agreements with network operators”
MVNO answer: “We purchase capacity from [Host MNO], who provides access to their roaming partner networks”
OV’s MNO Positioning: What It Means for You
OV is a global IoT MNO — not an MVNO, not a platform reseller, not a roaming aggregator.
What this means in practice:
- Owned Infrastructure
- OV operates core network infrastructure globally
- Direct interconnections to 600+ networks across 180+ countries
- Not dependent on third-party host MNOs
- True Multi-Network Architecture
- Multi-IMSI SIMs with profiles OV provisions directly
- Automatic network selection based on signal strength and availability
- No cascading roaming agreements or multi-hop dependencies
- Direct SLA Accountability
- 9% uptime commitments backed by owned infrastructure
- 24/7 Network Operations Center (NOC) with full network visibility
- No third-party escalation required for troubleshooting
- Long-Term Viability
- Infrastructure ownership means OV is invested in 10-20+ year device lifecycles
- Direct control over network evolution (2G/3G sunset → LTE/5G migration)
- Commercial relationships with networks are direct bilateral agreements, not intermediated through host MNOs
- Mission-Critical Reliability
- Network prioritization for IoT traffic during congestion
- Redundant core infrastructure and failover paths
- Proven uptime for payment terminals, healthcare devices, and lone worker safety applications
When MVNO Models Can Work
To be clear: MVNOs are not inherently “bad”—they serve specific use cases well:
Good MVNO Fits:
- Single-country deployments** where the MVNO has strong host MNO relationships and coverage
- Short-lifecycle devices (2-3 years) where long-term provider viability is less critical
- Non-critical applications where occasional connectivity loss is acceptable
- Price-sensitive projects where lowest per-MB cost is the primary decision factor
MVNO Advantages:
- Lower infrastructure overhead can enable competitive pricing in specific markets
- Specialization in niche verticals or customer segments
- Faster service launch (no need to build network infrastructure)
The key is understanding the trade-offs and selecting a provider model that aligns with your deployment’s criticality, scale, and longevity requirements.
Conclusion: Why Provider Type Matters
The difference between MNO and MVNO isn’t just technical trivia—it has real operational and commercial implications:
Choose an MNO when:
- ✅ Deploying mission-critical devices (payment, healthcare, safety)
- ✅ Long device lifecycles (10-15 years)
- ✅ Global or multi-region deployments
- ✅ Uptime and reliability are paramount
- ✅ You need direct SLA accountability and troubleshooting
Consider an MVNO when:
- Single-country deployment with strong MVNO-host MNO relationship
- Short device lifecycles (2-3 years)
- Non-critical applications where occasional outages are acceptable
- Lowest per-MB cost is primary selection criterion
Key takeaway: Not all “IoT connectivity providers” are created equal. Understanding whether you’re working with an MNO (owns infrastructure) or MVNO (resells connectivity) helps you assess reliability, control, long-term viability, and true multi-network redundancy capabilities.
When evaluating providers, ask direct questions:
- Do you own your core network infrastructure?
- How do you implement multi-network connectivity?
- What happens when there’s a network issue at 2am?
- What is your relationship with the networks my devices will connect to?
The answers will reveal whether you’re getting true MNO-backed reliability—or an MVNO reselling access through third-party agreements.
Ready to Deploy with a True IoT MNO?
OV provides global IoT connectivity backed by owned MNO infrastructure:
- 600+ direct network interconnections across 180+ countries
- Multi-IMSI SIMs with true multi-network redundancy (not cascading roaming)
- 99.9% uptime SLAs backed by owned infrastructure
- 24/7 NOC with direct network access (no third-party escalation)
- 10-15 year device lifecycle support (infrastructure ownership = long-term commitment)
Book a technical consultation to discuss your specific deployment requirements and learn how OV’s MNO infrastructure can support your mission-critical IoT applications.
About the Author:
Josh Price, Pre Sales and Product Manager at OV.
Related Articles:
- What Is an IoT SIM Card and How Does It Work? – World OV
- Multi-Network SIM vs Single Network: Why Redundancy Matters
- How to Choose an IoT Connectivity Provider
