MVNE

Also known as: Mobile virtual network enabler

On this page 7

An MVNE (mobile virtual network enabler) is a company that provides the technical infrastructure and operational services a mobile virtual network operator needs to run a mobile service, without owning radio spectrum or holding the retail customer relationship itself. Among mobile operators, the MVNE sits between the host network and the virtual brand, turning raw wholesale network access into a ready-to-sell product.

A typical MVNE supplies core network elements, real-time charging, billing, provisioning and SIM management as a shared platform. This allows a retailer, bank, sports club or cable company to launch mobile plans in months rather than years, and with far lower upfront investment than building its own systems.

Where the MVNE fits in the mobile value chain

The mobile value chain has distinct layers: the MNO owns spectrum and radio access, the MVNE provides the systems that make service sellable, and the MVNO owns the brand, pricing and customer. Some markets add a fourth layer, the MVNA (mobile virtual network aggregator), which buys wholesale capacity in bulk and resells it to smaller virtual operators.

The table below separates these roles, because contracts and regulatory obligations attach to each one differently.

RoleMain assetCustomer of the roleTypical revenue
MNOSpectrum licenses and radio networkMVNOs, MVNAs, end usersWholesale and retail fees
MVNABulk wholesale agreementSmall MVNOsMargin on resold capacity
MVNECore, charging and IT platformMVNOsSetup fees and per-subscriber fees
MVNOBrand, distribution, customer baseEnd usersRetail subscriptions
Roles in the virtual operator ecosystem

One company may combine several roles. An MVNA-MVNE hybrid bundles wholesale access with the platform, and some MNOs operate an in-house MVNE unit to attract virtual brands onto their network.

Services an MVNE typically provides

The scope of an MVNE varies by contract, but the services fall into network, business support and operational layers. The MVNO selects only the components it does not want to build or run itself.

LayerComponentsWhat they enable
Core networkHSS/HLR, packet core, IMS, SMS centerOwn subscriber identities and routing
ChargingOnline charging system, policy controlReal-time prepaid and data limits
BSSBilling, rating, CRM, product catalogPlans, invoices and customer accounts
SIM and eSIMCard profiles, SM-DP+ access, logisticsPhysical and digital activation
OperationsNumber porting, interconnect, lawful interceptRegulatory compliance and portability
Common MVNE service components

Modern MVNEs increasingly deliver these components as cloud-native, multi-tenant platforms with open APIs. Each MVNO runs as a separate tenant with its own catalog and branding, while the MVNE shares hardware, software licenses and operations staff across all tenants, which is the source of its economies of scale.

MVNO models and the depth of MVNE involvement

How much an MVNO relies on an MVNE depends on its operating model. The industry usually distinguishes branded resellers, light MVNOs and full MVNOs, and the MVNE share of the technical stack shrinks as the MVNO takes on more control.

MVNO modelWhat the MVNO ownsWhat the MVNE or host providesControl over products
Branded resellerBrand and sales channelAlmost everythingVery limited
Light (thin) MVNOBrand, pricing, customer careCore, charging, billing, SIMsModerate
Full MVNOOwn core, IMSI range, often billingSelected BSS or operationsHigh
MVNO models and the role of the MVNE

A full MVNO with its own core network and mobile network code can switch host networks more easily, because its subscriber identities do not belong to the MNO. A light MVNO is faster to launch but remains more dependent on the host and the MVNE for every new feature, such as 5G standalone access or Wi-Fi calling.

Choosing and contracting an MVNE

Selecting an MVNE is a long-term architectural decision, because migrating subscribers to another platform later is costly and risky. Buyers should evaluate commercial terms and technical capability together.

  • Host network integrations: which MNOs the MVNE is already connected to, and in which countries.
  • Pricing structure: setup fee, monthly minimums and the per-active-subscriber fee, which dominates long-term cost.
  • Feature roadmap: support for eSIM, VoLTE, 5G, roaming and IoT connectivity.
  • Data ownership: whether the MVNO can export customer and usage data in full.
  • Exit terms: notice periods, migration assistance and IMSI portability.

Service level agreements deserve close reading. Availability targets of 99.9 to 99.99 percent are common for charging and provisioning systems, and the gap between them translates into hours of potential outage per year, during which customers may be unable to top up or activate service.

Risks, limitations and common mistakes

Outsourcing technology to an MVNE reduces cost and time to market, but it creates dependency and shared-platform risks that new virtual operators often underestimate.

ProblemCauseMitigation
Slow product changesShared catalog with fixed release cyclesNegotiate configuration rights in the contract
Costly migrationVendor lock-in on IMSIs and BSS dataSecure data export and IMSI ownership upfront
Margins squeezed at scalePer-subscriber fees grow linearlyAgree volume tiers or a path to a full MVNO
Outage affects many brandsMulti-tenant platform failureRequire redundancy and service credits
Unclear compliance dutiesSplit responsibility for lawful intercept and data retentionMap obligations per party in writing
Typical MVNE pitfalls

A frequent strategic mistake is treating the MVNE as a pure supplier rather than a critical partner. When the MVNE itself is acquired or exits the market, its MVNO tenants can face forced migrations, so financial stability belongs on the evaluation list.

Understanding it simply

Imagine a company that wants to sell its own mobile phone plans but has no cell towers and no technical team. The towers can be rented from a big network operator, but someone still has to connect customers, count their minutes and data, and send them bills.

That someone is the MVNE. It works like a behind-the-scenes kitchen that cooks for many restaurant brands at once: each brand has its own menu and name on the door, while the same kitchen prepares the food. The key idea is that an MVNE lets new mobile brands launch without building complex systems themselves.

Applied in practice

A national supermarket chain with six million loyalty card members decides to offer prepaid mobile plans that reward customers with shopping points. It has no telecom engineers, so it signs a contract with an MVNE that already runs a light MVNO platform on one of the country’s three host networks.

The MVNE configures a new tenant with the supermarket’s brand, connects the plans to the loyalty system through its APIs, and supplies physical SIM cards and eSIM activation for sale at checkout. The supermarket handles marketing, pricing and in-store customer support only.

The service launches five months after contract signature, and the chain pays a per-subscriber monthly fee instead of a large upfront investment. After reaching 400,000 active lines, it renegotiates volume pricing and evaluates whether moving to a full MVNO model would improve its margins.