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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the MVNO function was enhanced through the update of the 5G LAN - virtual network (5G LAN-VN) capability. This introduced more sophisticated support for enterprise and localized service areas by leveraging the core network's ability to offer specific services within an operator-defined group of cells. The update further enabled the flexible provisioning of services to end-users independent of the access technology, aligning with Fixed Mobile Convergence principles.
- Update of 5G LAN - virtual network (5G LAN-VN). TS 22.261CR0336
In Release 17, the MVNO function was enhanced by introducing operator-provided end-to-end security for factory networks, a new capability enabling secure service delivery in enterprise environments. This builds upon existing core network operator and PLMN selection frameworks, allowing MVNOs to offer localized service areas with specific access conditions. The enhancement leverages the established architecture where services can be provided by operator-specific nodes, ensuring the PLMN operator or a delegated organization can manage these secure, specialized network slices.
- Operator provided end-to-end security for factory networks TS 22.261CR0430
In Release 19, the MVNO function was enhanced to specifically support charging for satellite services, introducing a new MVNO charging capability for this access type. This required corrections to the associated charging interfaces, namely N107 and N108, to ensure proper functionality. These updates formalize the charging procedures for MVNOs providing services via satellite networks.
Explore further
Broader topics and technologies where MVNO plays a role.
Defining Specifications
3GPP specifications that define or reference MVNO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.240 vj00 | 3GPP Generic User Profile Requirements | Rel-19 |
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TR 26.941 vj01 | 5G Media Slicing Extensions | Rel-19 |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |