Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

MVNO

Mobile Virtual Network Operator

Management →

MVNO is a mobile service provider that does not own radio spectrum or infrastructure but purchases wholesale network capacity from an MNO to brand and sell retail services to end-users.

Introduced
R99
Where
Services › Codecs
Specifications
8 specs
Also in
Management
MVNO Description Purpose What changed Neighbours Detected Changes Specifications

Description

A Mobile Virtual Network Operator (MVNO) is a business entity that provides mobile communication services to customers without owning the underlying radio access network (RAN) or licensed spectrum. Technically, an MVNO relies on a commercial agreement with one or more host Mobile Network Operators (MNOs) to obtain access to network resources. The degree of technical independence varies significantly based on the MVNO model. A full MVNO operates its own core network elements, such as the Home Subscriber Server (HSS), Mobile Switching Center (MSC), or in 5G, the Unified Data Management (UDM) and Session Management Function (SMF). It connects these to the MNO's RAN via standardized interfaces. This model provides the MVNO with greater control over services, provisioning, and customer data.

A light MVNO or service provider MVNO, on the other hand, may only operate a billing system, customer care, and marketing, while relying entirely on the MNO's core network and simply reselling its services. The key technical interface between an MVNO and an MNO is often the GRX/IPX (GPRS Roaming eXchange/IP eXchange) network for connectivity, and specific reference points like the S8 interface in 4G (between the MVNO's PGW and the MNO's SGW) or the N9 interface in 5G. The MVNO's subscribers are identified by their own Mobile Network Code (MNC), which is part of their IMSI, allowing the MNO's network to route signaling and traffic to the MVNO's network elements for authentication and service handling.

Architecturally, the MVNO model introduces a logical separation between the infrastructure layer (owned by the MNO) and the service layer (operated by the MVNO). This requires robust business support systems (BSS) and operational support systems (OSS) interfaces for provisioning, billing, and fault management. The MVNO's role is to innovate at the service and marketing level, targeting niche markets (e.g., low-cost, specific ethnic groups, IoT verticals) without the massive capital expenditure of building a physical network. The network sees the MVNO's traffic as wholesale roaming traffic, applying agreed-upon QoS and policy controls based on the service level agreement (SLA).

Purpose & Motivation

The MVNO concept emerged to increase competition and innovation in the mobile telecommunications market without requiring new entrants to acquire scarce and expensive spectrum licenses and build duplicate nationwide infrastructure. Prior to MVNOs, market entry barriers were prohibitively high, limiting consumer choice. MVNOs solve this by leveraging the excess capacity of established MNOs, allowing them to monetize their network investments further while enabling new players to offer tailored services.

MVNOs address specific market segments that large MNOs may underserve. For example, they can offer low-cost, prepaid plans, international calling packages, or specialized IoT connectivity plans. Their creation was motivated by regulatory pushes in some regions to foster competition, as well as by pure business opportunities. From a technical standpoint, 3GPP standardization of MVNO architectures (beginning in Release 99) was crucial to ensure interoperability between different MNO and MVNO equipment, enabling scalable and secure wholesale access models. This has allowed for a vibrant ecosystem of service providers, driving down prices and increasing service variety for end-users.

What changed in its specifications

The latest release-to-release comparison of specifications that define MVNO. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 22.261Rel-18 → Rel-19

Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.

Full comparison in TS 22.261 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-19 2 changes
  • Add MVNO charging which provides satellite service TS 32.240CR0518
  • Rel-19 CR 32.240 Correction on N107 and N108 for MVNO Charging TS 32.240CR0502

Defining Specifications

3GPP specifications that define or reference MVNO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.240 vj00 3GPP Generic User Profile Requirements Rel-19 read
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read
TS 26.941 vk00 5GMS Network Slicing Study Rel-20 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read