Home›Telecom›Deep dives›Multi-Tenant BSS: MVNO, MVNE & Enterprise← All deep dives
Deep dive

Multi-Tenant BSS: MVNO, MVNE & Enterprise

Running many brands, partners and large business customers on one BSS: tenant separation, wholesale models and account hierarchies.

Business unitsMVNO / MVNEAccount hierarchiesClosed user groupsShared plans
1 platformMany brands and partners
StrictData and configuration separation per tenant
DeepEnterprise hierarchies with many levels

Why multi-tenancy matters

Operators increasingly host other brands on their platform: sub-brands, mobile virtual network operators (MVNOs) and enablers (MVNEs) who serve several MVNOs. Each needs its own products, prices, bills and customer care, while sharing the same network and BSS to keep costs down.

The same capabilities serve large enterprise customers, who need account hierarchies, cost centres, shared allowances and consolidated invoices across thousands of lines.

MVNO models

How much an MVNO runs itself.

ModelMVNO runsHost provides
Branded resellerBrand and marketingEverything else
Light MVNOBrand, sales, careBSS, network, often billing
Service-provider MVNOBSS, pricing, billingNetwork and core
Full MVNOBSS and its own core networkRadio access only

Building blocks

Business units

Each tenant is a business unit with its own catalog, tariffs, bill cycles, documents and users.

Data isolation

Tenant identifiers on every record, access rules in every API and separate encryption keys where required.

Wholesale billing

The host rates the tenant's usage at wholesale prices and invoices the tenant, alongside the tenant's own retail billing.

Account hierarchies

Parent and child accounts, cost centres and invoice responsibility at any level.

Closed user groups

Virtual private networks with on-net pricing, short-code dialling and group-level discounts.

Shared and family plans

Pooled allowances and balances shared across lines, with per-member limits.

AI opportunity

Where AI helps

Tenant growth insight

Benchmark tenant performance, churn and usage to support partner management.

Enterprise churn risk

Predict which business accounts are at risk from usage and ticket trends.

Bill explanation

Generate plain-language explanations of complex enterprise invoices for care agents.

Design tips

Standards & references

TMF666Account Management API
TMF632Party Management API
TM Forum SIDInformation model for party, account and product

Related pages

This page describes generic industry practice and public standards. It is not based on, and does not describe, any particular vendor's product or operator's systems.