Share this Post:

PAGE CONTENTS

5 MVNO Types Compared: Characteristics and Use Cases

PAGE CONTENTS

What Are the Main Types of Mobile Virtual Network Operator (MVNO)? 

A mobile virtual network operator (MVNO), is a company that provides mobile communication services without owning the underlying radio access network infrastructure. Instead, MVNOs purchase access to network services in bulk from traditional mobile network operators (MNOs) like AT&T, Verizon, or T-Mobile, and resell to customers under their own brand.

Mobile Virtual Network Operator (MVNO) types vary based on the level of control and services they manage compared to the host Mobile Network Operator (MNO). MVNO types and definitions can also change significantly between countries and regions. However, to provide an introduction to the topic, some common types include:

  • Branded Resellers: These are the most basic type, primarily focusing on marketing and selling mobile services under their brand. They rely heavily on the MNO for all technical operations, including the network, billing, and customer service. 
  • Thin MVNOs: Handle some functions like billing and support, but depend fully on the MNO or MVNE for all technical network operations.
  • Light MVNOs: Manage their own OSS/BSS for billing, customer care, and subscriptions, allowing custom plans and services while relying on the MNO for core network access.
  • Thick MVNOs: These are more self-sufficient, owning some core network elements like a gateway mobile switching center (GMSC) for voice or a gateway GPRS support node (GGSN) for data. They also often have their own billing systems. 
  • Full MVNOs: Full MVNOs have the most control, owning most core network elements like the Home Location Register (HLR) and Mobile Switching Center (MSC). They lease only the radio access network (RAN) from the MNO.

The MVNO business model allows for increased market competition and can introduce innovative pricing or service packages that are not always available from the major MNOs. Many MVNOs focus on serving niche demographics such as budget-conscious users, immigrants needing international calling, or customers looking for flexible, no-contract plans. 

However, because MVNOs do not control the underlying network, they can face challenges related to network access, speed throttling, or prioritization during peak usage times.

This is part of a series of articles about Mobile virtual network operator

Understanding MVNO Types

The following table summarizes the characteristics and use cases of common MVNO types. Keep in mind that MVNO types and definitions can vary between countries and regions. Below we discuss each of these common types in more detail.

MVNO Type Network Infrastructure Owned Control Over OSS/BSS Licensing Requirements Time to Market Typical Use Cases
Branded Reseller None None None Fastest Retail brands adding mobile plans, quick market entry
Thin MVNO None Limited (billing, customer service) None Very Fast Niche pricing models, diaspora calling services
Light MVNO None Moderate (own OSS/BSS) Sometimes, depending on jurisdiction Moderate Custom plans, loyalty programs, niche market targeting
Thick MVNO Partial (e.g., GGSN, gateways) High Often required Slower Advanced data services, technical differentiation
Full MVNO Most core network elements (e.g., HLR, MSC, billing systems) Full Required Slowest Full service customization, enterprise and IoT solutions

1. Branded Reseller MVNO

A branded reseller, also known as a skinny MVNO, represents the most lightweight MVNO model. In this arrangement, the MVNO rebrands and resells existing mobile services that are almost entirely managed and controlled by the host mobile network operator (MNO) or a mobile virtual network enabler (MVNE). 

Responsibilities such as billing, rating, customer support infrastructure, and systems integration are primarily handled by the network provider, enabling a branded reseller to launch quickly and with minimal effort. In many cases, no license is required to operate as a branded reseller (skinny MVNO), but this depends on the region in which the MVNO operates and the local regulations.

Key characteristics:

  • Lowest barriers to entry: Branded (skinny) MVNOs primarily rely on the host MNO for operational processes, significantly lowering startup costs.
  • Fastest time to market: Because the infrastructure is fully managed by the partner MNO or MVNE, a skinny MVNO can go live with minimal lag.
  • Limited customization: Branded resellers are limited by the existing tariffs and features of the host network. If the MNO does not provide a specific data bundle or specialized function, the skinny MVNO cannot include it in its portfolio.

Use cases:

  • Retail chains: Large retail chains, such as supermarkets, can launch a branded reseller MVNO to offer mobile services to their loyal customers at competitive rates.
  • Established brands expanding reach: Businesses looking to quickly enter the telecom market can do so with minimal investment by becoming a branded (skinny) MVNO.

Notable examples of branded resellers include Walmart Family Mobile and ALDI Mobile. These companies capitalize on their strong brand recognition to deliver mobile services to their extensive customer bases.

2. Thin MVNO

Thin MVNOs, also known as service provider MVNOs, share many similarities with branded MVNOs but generally take on slightly more control over customer relationships and service offerings. 

For example, while the core network infrastructure remains under the management of the MNO, a thin MVNO might oversee its customer service operations or have greater flexibility in creating customized bundles. Like branded MVNOs, thin MVNOs often do not require a license to operate, but this depends on local regulations.

Key characteristics:

  • Slightly more control: Thin MVNOs may handle billing and customer service, but they rely wholly on the MNO’s (or MVNE’s) network systems for tasks such as rating, SIM provisioning, and other technical operations.
  • Variable branding options: Because they have more control than branded resellers, these MVNOs can tweak pricing or create specialized promotional campaigns to stand out.
  • Low CAPEX/OPEX: Thin MVNO operations still involve significantly lower costs than deeper, more infrastructure-heavy MVNO types.

Use cases:

  • Market-savvy startups: A small technology startup that wants to launch its phone service but does not want to deal with the complexities of building a billing solution from scratch might choose a thin MVNO approach.
  • Specialized services: Thin MVNOs are popular among those focusing on unique segments, like diaspora communities who need cost-friendly international calling rates.

3. Light MVNO

Light MVNOs, also known as enhanced service providers or mid-tier MVNOs, take on a greater share of business and operational processes compared to thin MVNOs. This includes managing certain aspects of the OSS (operations support system) and BSS (business support system). 

However, they typically do not own significant network infrastructure. Instead, light MVNOs connect to the host MNO’s core network while maintaining direct control over billing systems, branding, and marketing strategies.

Key characteristics:

  • Greater flexibility: Light MVNOs have a higher degree of flexibility in defining rate plans, bundles, and value-added services.
  • Independent OSS/BSS: The light MVNO often manages its own customer care, billing, subscription management platforms, and other technical layers that shape the user experience.
  • Mid-level control: While they rely on the host for core network elements like the radio network and subscriber registry, light MVNOs can craft their branding strategies, define marketing campaigns, and design unique user experiences.

Use cases:

  • Companies seeking differentiation: A light MVNO can effectively incorporate advanced features (such as loyalty programs or data rollover) that may not be offered by MNOs.
  • Niche segment operators: These might include operators focusing on senior citizens, students, or IoT devices, leveraging specialized billing, data usage analytics, or subscription models.

4. Thick MVNO

A thick MVNO or enhanced service provider MVNO expands on the light MVNO model by incorporating or maintaining partial core network components, such as a GGSN, home subscriber server, or specific data gateways. 

By operating certain elements of the MNO’s network architecture, thick MVNOs can offer advanced features like custom data routing, specialized data analytics, or zero-rated applications. However, because they manage partial network infrastructure, thick MVNOs often require additional licenses, which vary based on the country and its regulatory framework.

Key characteristics:

  • Infrastructure ownership: While not a full MVNO, a thick MVNO might negotiate wholesale agreements with MNOs or MVNAs and run certain core network aspects in-house.
  • Better offerings: By owning some network control points, thick MVNOs have the freedom to create advanced value-added services, such as specialized roaming solutions or tailored data usage rules.

Use cases:

  • Operators targeting technical differentiation: Thick MVNOs might build unique data/information services for customers, free social media traffic, or premium data usage analytics.
  • Businesses with more resources: To run a thick MVNO operation, an entity needs bigger investments and stronger technical expertise, making it more suitable for established companies expanding into telecom.

5. Full MVNO

A full MVNO is the most independent and sophisticated type of MVNO. While it does not have access to the radio spectrum (which remains under the control of the MNO), a full MVNO typically owns or manages all critical core network elements, including the home location register (HLR), home subscriber server (HSS), gateway GPRS support node (GGSN), billing and charging engines, and SIM provisioning systems. This level of control provides full MVNOs with maximum flexibility in designing, packaging, and delivering mobile services.

Key characteristics:

  • Full infrastructure control: By owning most core network components, full MVNOs can implement advanced features, customize call flows, manage data usage, and control SIM card issuance.
  • Brand differentiation: Full MVNOs have the ability to fully customize the user experience, including call routing and data management.
  • Larger investments and more complexity: As they manage the core network (excluding physical radio towers), full MVNOs require significant upfront capital, a larger workforce, and advanced technical expertise.

Use cases:

  • Established operators: Telecom companies that are well-versed in network operations might choose to launch a full MVNO to specifically reach separate demographics or expand internationally.

Enterprises with complex needs: Often, businesses that want total autonomy over data flows (such as high-security or specialized IoT projects) might operate as a full MVNO.

Key Considerations for Choosing the Right MVNO Model

Selecting the appropriate MVNO model involves evaluating several strategic, operational, and regulatory factors. The decision impacts time to market, upfront investment, operational complexity, and long-term service flexibility. Here are the primary considerations to assess:

  • Capital investment (CAPEX/OPEX): Branded and thin MVNOs require minimal capital expenditure and are suitable for entities seeking low-risk market entry. Thick and full MVNOs involve higher investment due to infrastructure and licensing requirements.
  • Control over services: The more control an MVNO has over systems like billing, OSS/BSS, and SIM management, the greater its ability to differentiate. Full and thick MVNOs offer deeper customization than branded or thin models.
  • Time to market: Branded and thin MVNOs can launch quickly due to limited infrastructure and integration needs. Full MVNOs, in contrast, face long setup cycles due to complex system deployment.
  • Regulatory compliance: Some MVNO types (especially thick and full) may require specific telecom licenses depending on jurisdiction. Understanding local regulatory frameworks is critical before committing to these models.
  • Target market and differentiation needs: If the MVNO targets a niche with unique needs (e.g., IoT, enterprise mobility, diaspora communities), a light, thick, or full MVNO model may offer the required flexibility to tailor services effectively.
  • Technical expertise: Higher-tier MVNOs need in-house telecom and IT expertise to manage their systems. Entities without this capability may prefer branded or thin models supported by MVNEs.
  • Scalability and long-term strategy: Businesses anticipating growth or service evolution may prefer light or full MVNO models that support long-term differentiation, even if they start as a lower-tier MVNO.

Each model presents a trade-off between control and complexity. The right choice aligns with the MVNO’s business objectives, operational capacity, and market positioning.

IoT Connectivity for MVNOs with floLIVE

Global IoT rollouts often fail on permanent‑roaming bans, latency, and data‑sovereignty rules. The workaround is local connectivity at global scale—using local profiles and local breakout instead of tromboning traffic back to a home network.

How floLIVE helps (regardless of MVNO type)

  • Local breakout & data residency: Route device traffic to nearby packet gateways to cut latency and keep data in‑region (e.g., GDPR). 
  • 40+ local PoPs + IMSI library: A distributed core with 40+ points of presence and a broad IMSI library delivers local behavior in 200+ markets with one provider.

  • Multi‑IMSI + eUICC: Combine multi‑IMSI with eUICC to switch operators or add local profiles OTA—ideal where permanent roaming is restricted.

  • Multi‑cloud resilience: Core deployed across OCI + AWS for redundancy and regional compliance.

Where you fit, by MVNO type

  • Branded/Thin: Launch fast; let floLIVE handle SIM lifecycle, IMSI steering, and regulatory‑friendly routing—no heavy core to build.

  • Light/Thick: Keep your OSS/BSS differentiation and add local profiles + LBO via APIs for performance and sovereignty.

  • Full MVNO: Use floLIVE as your global complement, local egress and profile orchestration where you don’t (or can’t) run local core.

Business outcomes

  • Compliance & reach: Operate in countries with roaming limits (e.g., Brazil, China, turkey) using local profiles instead of workarounds.

  • Performance: Lower latency + deterministic routing vs classic roaming.

  • Simplicity: One console and API for SIMs, IMSIs, policies, and breakouts—across markets.

Related articles

See More