Mobile Network Operators are the foundational layer of cellular IoT. They build and operate the radio access network infrastructure that IoT devices connect to, manage the licensed spectrum those networks run on, and maintain the core network systems that authenticate devices, assign IP addresses, route traffic, and handle billing. Without MNO infrastructure, there is no cellular IoT. Every SIM card provisioned for an IoT device ultimately connects through an MNO’s network, whether the SIM was purchased directly from that MNO, from an MVNO reselling the MNO’s capacity, or from an enterprise IoT connectivity provider with direct carrier relationships.

Understanding what MNOs do, and equally what they do not do, is essential context for enterprise IoT architects evaluating connectivity options. The MNO’s role in IoT is substantial but bounded. The infrastructure they provide is necessary but not sufficient for enterprise-grade IoT deployments at scale. And the gap between what MNO connectivity provides and what enterprise IoT deployments require is where most of the hard connectivity work happens.

The Infrastructure MNOs Provide

MNOs invest in several layers of infrastructure that form the foundation of cellular IoT connectivity.

Radio Access Network infrastructure is the most visible layer: the cell towers, distributed antenna systems, small cells, and associated radio equipment that establish the cellular coverage footprint in a given geography. MNOs manage the radio resource allocation across this infrastructure, balancing spectrum usage between consumer mobile subscribers, fixed wireless access customers, and IoT device populations that have different usage patterns and different traffic characteristics.

The IoT-relevant radio technologies that MNOs deploy vary by carrier and by market maturity:

• LTE-M (Cat-M1) deployment requires software and hardware upgrades to existing LTE infrastructure to enable the specific 3GPP Release 13 features that define the technology. Not every LTE base station in an MNO’s network has been upgraded to support LTE-M, and coverage maps for LTE-M are meaningfully different from general LTE coverage maps in many markets.
• NB-IoT deployment similarly requires feature activation on LTE base stations, and NB-IoT coverage has been rolled out unevenly across carrier networks and geographic markets.
• 5G NR for IoT requires new radio hardware in addition to software configuration, and the IoT-specific 5G NR features including RedCap (3GPP Release 17) are at early stages of deployment relative to general 5G coverage.

Core network infrastructure handles everything that happens after the radio connection is established. The Evolved Packet Core in LTE networks, and the 5G Core in 5G networks, manages device authentication via the Home Subscriber Server or Unified Data Management, handles IP address assignment and routing, enforces quality of service policies, connects the device to the internet or to enterprise private networks via APN configuration, and generates the data records that billing is based on.

Spectrum licenses give MNOs the legal right to operate their networks in specific frequency bands within their licensed geographic territories. Licensed spectrum is the asset that defines an MNO’s network boundaries: an MNO cannot extend its network infrastructure beyond its licensed territory without acquiring spectrum licenses in additional markets, which is why MNO networks are fundamentally regional or national in scope.

Roaming agreements allow MNOs to extend the coverage of their network by allowing their subscribers to connect to partner MNOs’ networks when traveling outside the home network’s territory. Roaming is the mechanism that gives a single-carrier SIM access to cellular coverage in countries where the home carrier has no infrastructure. The commercial and technical characteristics of roaming, including the latency penalty from routing traffic through the home carrier’s core, the cost variability of inter-operator tariff agreements, and the fair use restrictions that visited networks apply to roaming traffic, are the trade-offs that enterprise IoT deployments on standard roaming SIMs carry.

How MNOs Serve IoT Customers Directly

When enterprise IoT deployments purchase connectivity directly from an MNO, the commercial and operational relationship has several characteristics that are important to understand.

IoT-specific rate plans from MNOs are structured differently from consumer mobile plans, with data pooling across device fleets, volume-tiered pricing, and in some cases dedicated IoT APNs that separate IoT device traffic from consumer mobile traffic on the MNO’s network. The availability and terms of IoT-specific rate plans vary significantly across MNOs and are typically negotiated rather than listed, with pricing structures that reflect the enterprise’s aggregate data consumption, device count, and contract term commitment.

Private APN provisioning is available from MNOs for enterprise customers requiring that IoT device traffic route directly to the enterprise’s network infrastructure without traversal of the public internet. Private APN configuration is standard practice for enterprise IoT deployments with data security, compliance, or latency requirements, and MNOs with established enterprise IoT businesses can provision private APNs as part of the commercial arrangement.

IoT connectivity management portals are provided by most major MNOs for enterprise IoT customers, allowing visibility into device connectivity status, data usage per SIM, and basic SIM lifecycle operations such as activation, suspension, and deactivation. The sophistication of these portals varies across MNOs, and the API accessibility of connectivity management functions varies as well.

Technical support for IoT deployments from MNOs is usually structured around the commercial relationship scale. Large enterprise customers with significant committed revenue receive dedicated technical account management. Smaller deployments may be managed through standard business support channels with longer resolution timelines for connectivity issues.

The Boundaries of What MNOs Provide

The MNO’s role in IoT is defined by network infrastructure. The boundaries of that role are equally important to understand, because they define where enterprise IoT deployments need additional capabilities beyond what the MNO provides directly.

Geographic coverage is limited to licensed territory. An MNO’s own network infrastructure stops at its licensed spectrum boundaries, which are typically national. An enterprise deploying IoT devices across multiple countries cannot rely on a single MNO’s infrastructure for all markets. Either the enterprise establishes separate commercial relationships with MNOs in each target market, or they rely on roaming agreements, or they work with a connectivity provider that maintains direct carrier relationships across multiple markets and provides a unified commercial and management interface across all of them.

Network technology coverage within territory is not uniform. As noted above, IoT-specific network technologies including LTE-M and NB-IoT have been deployed unevenly within carrier networks. An MNO that has strong LTE coverage in a given geography may have limited or no LTE-M or NB-IoT coverage in specific areas within that geography, particularly in rural regions or markets where the IoT-specific feature rollout is incomplete.

Multi-carrier resilience is not available in a single-MNO relationship. A device provisioned on a single MNO’s SIM has no automatic path to an alternative carrier’s network when the primary carrier has an outage or coverage gap. Multi-carrier resilience, where the device can connect to whichever carrier provides the strongest available signal, requires either a multi-SIM device architecture or a multi-IMSI or eUICC SIM solution that is provided by a connectivity provider rather than by a single MNO.

Connectivity management sophistication for large device estates varies. The IoT connectivity management portals provided by MNOs are designed for managing SIM estates on that MNO’s network. Enterprises managing devices across multiple carriers, multiple countries, and multiple network technologies need a connectivity management platform that provides unified visibility and control across all of those dimensions, which a single-MNO portal cannot provide by definition.

Device logistics and hardware are outside the MNO’s core business. MNOs provide connectivity. They do not typically provide device selection guidance, hardware procurement, device configuration and staging, field logistics for device deployment, or the forward and reverse logistics of managing a large IoT device estate across its operational lifecycle. These capabilities, which are essential for enterprise IoT deployments at scale, require either internal enterprise capability or a connectivity partner with an integrated device and logistics offering.

MVNOs and IoT Connectivity Aggregators as the Intermediary Layer

Between the MNO infrastructure layer and the enterprise IoT deployment sits a range of intermediary providers that build on MNO relationships to offer capabilities that individual MNOs do not provide.

Mobile Virtual Network Operators purchase connectivity capacity from MNOs and resell it to enterprise customers, typically offering simplified commercial terms, multi-carrier SIM options, and connectivity management platforms that aggregate the underlying MNO relationships into a unified interface. MVNOs vary widely in sophistication, from simple SIM resellers with minimal management capabilities to full-service IoT connectivity providers with extensive operational infrastructure.

The main distinction within the MVNO and connectivity aggregator category is the depth of the underlying carrier relationships and the architecture of the multi-network connectivity they provide. Standard roaming, where devices connect to visited networks as roaming visitors from a home network, provides geographic coverage extension but preserves the latency, cost variability, and performance limitations of the roaming model. Localized multi-network connectivity, where devices authenticate as local subscribers on networks in each target market via multi-IMSI or eUICC technology, provides local-grade performance and cost predictability that standard roaming cannot.

KORE occupies a distinct position in this landscape. As an enterprise IoT connectivity infrastructure provider with 40+ direct carrier partnerships across 200+ countries, KORE is not simply reselling MNO capacity through roaming agreements. The OmniSIM architecture provides localized connectivity on 500 networks across 195 countries. The ConnectivityPro platform provides unified connectivity management across all carriers and all markets. The four global logistics hubs support device deployment at the scale that enterprise IoT programs require. With 21M+ active SIMs deployed since 2003 across connected health, fleet, industrial, and utilities verticals, the operational depth reflects a track record that neither single-MNO relationships nor basic MVNO resellers can match.

What the MNO Layer Means for Enterprise IoT Architecture

The practical implication of understanding the MNO’s role is that enterprise IoT connectivity architecture decisions need to account for both the MNO layer and the connectivity management layer above it.

For deployments that operate in a single geography with strong coverage from a single MNO and modest device management requirements, a direct MNO relationship may be the most straightforward option. The commercial relationship is simple, the connectivity management portal may be sufficient for the device count, and the coverage requirements are met by the MNO’s domestic network.

For deployments that span multiple geographies, require multi-carrier resilience, have large device estates requiring sophisticated lifecycle management, or operate in verticals with specific compliance and data routing requirements, a direct MNO relationship in each market is operationally complex and commercially inefficient. The enterprise ends up managing multiple carrier relationships, multiple management portals, multiple billing relationships, and multiple support escalation paths. The connectivity management overhead scales with the number of carrier relationships rather than declining.

The connectivity provider layer that sits above MNO infrastructure, when it provides genuine multi-network architecture rather than simple roaming resale, unified connectivity management across all carriers, and the device and logistics capability that enterprise deployments require, is the infrastructure layer that makes large-scale, geographically diverse IoT deployments operationally tractable.

MNOs build the radio networks that cellular IoT depends on. The connectivity infrastructure that makes enterprise IoT deployments work at scale is built on top of those networks, not within them.

If you are evaluating the connectivity architecture for an enterprise IoT deployment and determining how to structure the MNO layer and the connectivity management layer above it, talk to a KORE connectivity architect about the infrastructure requirements your deployment scale and geographic scope demand.

Originally published July 2, 2026