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.
Key Features
- Operates mobile services without owning licensed spectrum or RAN infrastructure
- Utilizes wholesale network access agreements with one or more host MNOs
- Can range from light (reseller) to full (own core network) operational models
- Manages its own customer relationships, branding, billing, and tariff plans
- Identified by its own unique Mobile Network Code (MNC) within subscriber IMSIs
- Interconnects with MNO network via standardized 3GPP interfaces (e.g., S8, N9) and GRX/IPX
Evolution Across Releases
Initial 3GPP considerations for network sharing and MVNO concepts. Laid the groundwork by standardizing core network architecture that could logically separate the serving network from the home network, a prerequisite for MVNO models.
5G System architecture fully embraced network slicing, providing a native and powerful technical framework for MVNOs. An MVNO can be allocated its own network slice(s) with specific characteristics, managed via the 5G service-based architecture.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.240 | 3GPP TS 22.240 |
| TS 22.261 | 3GPP TS 22.261 |
| TS 26.941 | 3GPP TS 26.941 |
| TS 28.843 | 3GPP TS 28.843 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.296 | 3GPP TR 32.296 |
| TS 43.901 | 3GPP TR 43.901 |