MNO, MVNO, Full MVNO, MVNA, MVNE: what each model actually commits you to

Mobile network architecture: Core Network ownership and the real cost of operator dependencies

By Benoit Mathian, CTO at Halys

MNO, Branded Reseller, Thin MVNO, Medium MVNO, Full MVNO, MVNA, MVNE — these acronyms describe fundamentally different network architectures, with very different levels of dependency that shape every mobile operator project for years to come.

Launching an MVNO or evolving a mobile architecture isn’t just a matter of picking a model. It’s a structural commitment — one that’s often hard to undo — that determines whether you can switch host operators, expand internationally, or maintain real control over your subscribers.

This article doesn’t define these models. It looks at what they actually imply once you’re in production.

Comparing the 7 mobile operator models at a glance

Before diving into each model, the table below maps which layers each one controls. It’s the reference point for everything that follows.

Three things stand out immediately:

• Core Network control and subscriber management are the primary drivers of real operational independence

• IMSI ownership determines whether you can switch MNOs without a costly, high-risk migration

• the fastest models to launch create the deepest long-term dependencies

These models each represent a different position on four dimensions:

• how dependent you are on an MNO or third party

• how much control you have over your subscribers and services

• how much flexibility you have to evolve your architecture

• the cost structure, balancing upfront investment against ongoing operational dependency

These dimensions move together. More layers controlled means more autonomy — but higher technical, organisational and financial requirements. Lighter models mean faster, cheaper launches — at the cost of deeper dependency and less room to evolve.

 To understand these differences in operational terms, you need to start with the structure of a mobile network.

The layers of a mobile network: how to read operator models

Every mobile network is built around the same set of functional layers:

• RAN (Radio Access Network) — antennas, radio spectrum, physical radio infrastructure

• SIM / eSIM — the physical or digital carriers of subscriber identities (IMSI/SUPI)

• Core Network — EPC in 4G or 5GC in 5G; handles subscriber authentication (HSS/UDM) and routing of voice and data

• Service platforms — voice, messaging and value-added services (IMS, VAS)

• BSS / CRM — billing, activation, operations and customer management

• Roaming — inter-operator agreements and interconnection platforms that keep subscribers connected outside the home network

What sets each model apart isn’t size or commercial ambition. It’s which of these layers it actually owns — and which ones it hands off to a third party.

 Every handoff has a technical cost: a constraint, a dependency or a limitation that stays invisible until it matters — during a migration, a traffic surge, or an operator switch.

MNO: the baseline, no dependencies

The MNO (Mobile Network Operator) owns and operates all six layers. It holds its own spectrum licences, runs its own RAN, and operates a complete Core Network spanning every generation in production — from legacy 2G/3G through 4G and 5G. It runs its own BSS/OSS systems and manages the customer relationship end to end.

Full control, full complexity. The MNO depends on no third party to operate, innovate or evolve its services. It can run 5G network slicing, offer differentiated SLAs to enterprise customers, negotiate bilateral roaming agreements directly with operators worldwide, and host other operators — generating wholesale revenue alongside its retail business.

Every other model is defined in relation to this one — by progressively giving up layers of control, and accepting the constraints that come with each trade-off.

Branded Reseller: maximum speed, zero technical ownership

The Branded Reseller sells mobile services under its own brand but owns nothing underneath. No RAN, no Core Network, no BSS — not even the SIMs or IMSIs of its own subscribers. Everything belongs to the host MNO. Its only proprietary assets are its brand, distribution channels and existing customer base.

The practical implication is near-total structural dependency. A Branded Reseller controls no network parameters, can’t differentiate its offering beyond what the host MNO allows, and doesn’t own its subscribers’ data in any network sense. If the host MNO relationship ends, so does the mobile business — with no technical assets to carry forward.

It’s a fast-entry model built for testing the market with minimal investment. That works as a starting point. As a permanent position, the dependency makes it structurally fragile.

Thin MVNO: real commercial autonomy, a hidden structural constraint

The Thin MVNO — or Service Provider MVNO — crosses a meaningful threshold. It has its own SIMs, CRM and BSS, which gives it ownership of the customer relationship, independent billing and genuine pricing flexibility. It’s the most common MVNO model in Europe, accounting for the majority of active virtual operators on the continent.

There’s a significant blind spot, though — one that’s easy to overlook at launch. The IMSIs still belong to the host MNO. The IMSI (International Mobile Subscriber Identity) is the fundamental network identifier of each subscriber, anchored to the host MNO’s Core Network (HSS/UDM). Without controlling those functions, the Thin MVNO can’t retrieve its IMSIs — and remains structurally dependent on its host operator.

Switching host MNO means physically migrating every SIM in circulation — an operation that grows heavier, costlier and riskier as the subscriber base scales.

Early on, this constraint is largely invisible. It becomes critical during a renegotiation or operator change — precisely when the subscriber base makes migration hardest.

Medium MVNO: real subscriber control, growing independence

The Medium MVNO — or Enhanced Service Provider — solves the Thin MVNO’s core problem by bringing subscriber management functions (HSS/UDM) in-house. This is the most structurally significant technical step in the MVNO progression — and probably the least well understood from the outside.

Owning these functions means controlling subscriber management in the network sense: the SIM lifecycle, the MSISDN — the phone number tied to each subscriber. On IMSIs, the picture is more nuanced: a Medium MVNO can access its own IMSI blocks, but control remains partial and depends on what was negotiated with the host MNO.

It’s growing autonomy, not yet complete — full autonomy is what the Full MVNO achieves. But it’s also the threshold at which obtaining your own Mobile Network Code (MNC) becomes possible, marking a new level of independent network identity.

The Medium MVNO also runs its own VAS platforms, enabling differentiation that goes well beyond pricing.

In practice, this model becomes relevant when subscriber base ownership, the ability to switch operators, or preparing for an upgrade start to matter strategically.

Full MVNO: maximum autonomy through Core Network ownership

The Full MVNO is as independent as a mobile operator can get without owning spectrum. It runs its own Core Network — EPC in 4G or 5GC in 5G, including subscriber authentication (HSS/UDM) — plus its own service platforms for voice, messaging and VAS. It owns its SIMs and IMSIs, controls its BSS/CRM, and can negotiate roaming agreements directly with operators worldwide. Some functions — international roaming in particular — may still be partially handled through interconnection platforms or specialist partners. The only layer it doesn’t own is the RAN.

Running a full Core infrastructure requires real internal expertise, rigorous dimensioning and ongoing maintenance. That’s the trade-off. The returns are significant: end-to-end QoS control, 5G network slicing, substantially better terms on international roaming, and full sovereignty over subscriber data. This level of control becomes essential in contexts where regulatory constraints, data governance or service quality requirements can’t be outsourced — particularly in industrial, financial and mission-critical sectors.

It’s also the model that enables an operator to position itself as an MVNE or MVNA for others — opening up new B2B revenue streams.

MVNA: wholesale network access for MVNOs

The MVNA (Mobile Virtual Network Aggregator) isn’t an operator in the retail sense. It buys network capacity in bulk from one or more MNOs and resells it to MVNOs that can’t negotiate directly — because they don’t have the volume to secure acceptable terms on their own.

 By aggregating multiple MVNOs, the MVNA achieves pricing no individual MVNO could reach. Its role is strictly defined: it doesn’t provide an operational platform — no BSS, no CRM, no billing. It structures network access, nothing more. An MVNO working with an MVNA still needs to build or source its own operational platform.

That distinction — between network access and operational enablement — directly shapes the architecture and autonomy of any MVNO model.

MVNE: the operational backbone for MVNOs

The MVNE (Mobile Virtual Network Enabler) operates at a different level: it provides the full operational platform an MVNO needs to launch without building its own systems — BSS, CRM, billing, SIM provisioning, customer portal, reporting, and in some cases network interconnection components.

The core value proposition is speed. An MVNE can cut time-to-market from months to weeks. That’s real. The trade-off is structural outsourcing: subscriber data, billing processes and technical integrations sit with a third party. That dependency rarely causes problems immediately. It tends to surface during evolution phases — model changes, scaling, specific integration needs — when the platform becomes a bottleneck rather than an enabler.

In some cases, dependency can be partially reduced — particularly when the MVNO retains control of critical components or manages its own interfaces. But it remains a long-term structural factor.

Mobile network architecture: understanding operator dependencies — and where Halys comes in

Across all these models — MNO, Thin/Medium/Full MVNO, MVNA, MVNE — the same principle holds: architecture decisions, particularly around the Core Network and subscriber management, directly determine how much control you have and how much flexibility you retain. Those decisions determine whether you can switch host operators, expand into new markets, launch new services, or absorb traffic growth without being constrained by your initial architecture.

IMSI portability, HSS/UDM ownership, data sovereignty, MVNE platform lock-in — these are never theoretical concerns. They show up in concrete situations: an operator renegotiation, a fast-growing subscriber base, or a service integration that the current architecture wasn’t built for.

This is exactly where Halys has built its expertise. Our teams design and deploy telecom platforms for MNOs, MVNOs, carriers and integrators, in both national and international operator environments — projects where reliability, scale and interoperability aren’t optional.

In practice, that covers:

• 4G/5G core network components, in cloud-native, modular and sovereign architectures;

• operator interconnection and roaming functions — SS7 Hub, Diameter Gateway, GTP Hub, multi-operator traffic management;

• operator messaging platforms — SMSC, SMS Hub, MMSC, Welcome SMS.

Our platforms support millions of connections every day in live operator environments.

Designing or evolving an operator architecture? Our teams can help you work through the technical implications — whether you’re launching an MVNO, migrating a Core Network, or building a multi-operator interconnection architecture.

Talk to our team

Frequently asked questions about mobile operator models

What’s the difference between an MVNO and an MNO?

An MNO (Mobile Network Operator) owns and operates its entire network infrastructure — from the radio spectrum to the Core Network. An MVNO (Mobile Virtual Network Operator) relies on a host MNO for some or all of those layers. The distinction between MVNO types — Thin, Medium, Full — comes down to how much of the critical infrastructure, particularly the Core Network and subscriber management, the MVNO controls directly.

What is a Branded Reseller?

A Branded Reseller sells mobile services under its own brand but owns no technical infrastructure whatsoever. Connectivity, subscriber management and back-office systems are all operated by the host MNO. It’s a fast route to market, but it comes with no technical control and no operational independence.

What’s the difference between an MVNA and an MVNE?

An MVNA (Mobile Virtual Network Aggregator) and an MVNE (Mobile Virtual Network Enabler) operate at different levels of the MVNO stack. The MVNA focuses on network access: it negotiates wholesale capacity from MNOs and packages it for MVNOs that don’t have the volume to negotiate directly. The MVNE focuses on operations: it provides the technical platform an MVNO needs to run its service — BSS, CRM, billing, SIM provisioning.

The two roles are complementary: one handles network access, the other enables the service to run. An MVNO may rely on one, the other, or both.

Why does subscriber management (HSS/UDM) matter so much?

HSS/UDM functions handle subscriber authentication and identity management (IMSI/SUPI). Owning them means controlling the full subscriber lifecycle and avoiding structural dependency on your host MNO. Without that control, any major architecture change — especially switching operators — requires a heavy SIM migration.

When should you bring subscriber management (HSS/UDM) in-house?

When your dependency on the host MNO starts limiting your ability to evolve. In practice, that usually means one of three things: your subscriber base has reached a size where SIM migration becomes genuinely complex; you’re planning an operator switch or international expansion; or data control has become a strategic requirement. This transition typically marks the move from Thin to Medium MVNO.

What is a Full MVNO?

A Full MVNO runs its own Core Network (EPC in 4G or 5GC in 5G), controls its own subscriber management (HSS/UDM), owns its SIMs and IMSIs, and manages operator roaming agreements directly. The only thing it leases from its host MNO is the RAN. It’s the highest-control MVNO model — well suited to IoT deployments, B2B operators, and any environment where operational sovereignty over subscribers, services and data is non-negotiable.

Which MVNO model works best for IoT or private network projects?

The Full MVNO is generally the right fit for industrial IoT and private 5G deployments: it gives you Core Network control (EPC/5GC), subscriber management, data sovereignty, 5G network slicing, and the ability to negotiate direct roaming agreements — including across multiple countries. For more targeted deployments, specific 4G/5G core components can be deployed in hybrid architectures, balancing technical control against cost.

Mobile network technical glossary

5GC — 5G Core

The 5G equivalent of the EPC, built on a cloud-native, service-based architecture. It introduces capabilities including network slicing — dividing the network into virtual segments dedicated to specific use cases.

EPC — Evolved Packet Core

The 4G LTE core network, responsible for data routing, subscriber authentication and mobility management. In Full MVNO architectures, the EPC is operated in-house.

HLR / HSS / UDM — Core Network subscriber management functions

The HLR (Home Location Register), HSS (Home Subscriber Server) and UDM (Unified Data Management) are the core network functions that manage subscriber identities and profiles. HLR is the 2G/3G function, HSS covers 4G, and UDM handles 5G in a service-based architecture. Owning these functions in-house — and therefore controlling subscriber identities (IMSI/SUPI) — is the technical threshold that separates Medium MVNOs from Thin MVNOs, and determines how freely an operator can evolve its architecture or switch host operators.

IMSI — International Mobile Subscriber Identity

The unique network identifier stored on each SIM, used to identify and authenticate a subscriber. The IMSI is managed by subscriber management functions (HSS/UDM). Without controlling those functions, an MVNO’s IMSIs remain tied to the host MNO — with significant portability constraints as a result.

In 5G, the permanent subscriber identifier is the SUPI (Subscription Permanent Identifier), managed by the equivalent core functions.

MNC — Mobile Network Code

The two or three-digit code that identifies a mobile operator within a country. Getting your own MNC is a key step towards an independent network identity, and becomes accessible at the Medium MVNO level.

MSISDN — Mobile Station Integrated Services Digital Number

The phone number associated with a SIM, as it appears for calls and SMS. Managed by subscriber management functions (HLR/HSS/UDM) and linked to the subscriber’s network identity.

RAN — Radio Access Network

The physical radio infrastructure of the mobile network: antennas, base stations and radio spectrum management. It’s the layer that connects devices to the core network. In every MVNO model, the RAN is leased from the host MNO.

SMSC — Short Message Service Centre

The Core Network component responsible for SMS routing and delivery. Running your own SMSC is one of the hallmarks of a Full MVNO. Halys provides SMSC and SMS Hub platforms for mobile operators.

SUPI — Subscription Permanent Identifier

The unique subscriber identifier in 5G networks — the functional equivalent of the IMSI in earlier generations. Used by the 5G core network to identify and authenticate subscribers, with stronger privacy protections built into the architecture.

QoS — Quality of Service

The set of technical mechanisms that guarantee network performance — throughput, latency, availability — for a given service or user. QoS control is directly tied to how much of the Core Network you own.

VAS — Value-Added Services

Services delivered on top of basic network connectivity — messaging, advanced voice, application services. In MVNO architectures, owning your VAS stack enables differentiation beyond pricing and direct control over the customer experience.