# MVNO enablement — specifications

> Technical specifications: BSS integration with TM Forum Open APIs; MVNO models: who owns what.

Source: https://www.siltatel.net/mvno/specs/ · Service page: https://www.siltatel.net/mvno/

Launch and run a mobile brand on a host network — from a light reseller model to a full MVNO with its own core.

- Host operator selection
- Core and subscriber management
- Number portability, billing, BSS
- Operations and customer care


### BSS integration with TM Forum Open APIs

*TM Forum Open APIs · ODA*

An MVNO is as fast as its order flow. Channels, BSS and network are connected through TM Forum Open APIs, so a sale becomes an active SIM or eSIM without manual steps — and partners plug in their own systems through the same interfaces.

Figure: FIG. 1 — Order-to-activation flow. Order flow through TM Forum Open APIs: channels, BSS (TMF620, 622, 629, 635, 678) and OSS (TMF641, 640, 638) to network and SM-DP+

1. Product catalog (TMF620) and product ordering (TMF622): tariffs and bundles are defined once and sold in every channel.
2. Service ordering (TMF641) and activation (TMF640) turn an order into network actions: HLR/HSS subscription, policy, and the eSIM download order on the SM-DP+ (GSMA ES2+).
3. Service inventory (TMF638) keeps SIMs, numbers and services in one view.
4. Usage (TMF635) and customer bill (TMF678) close the loop from network records to invoices.
5. Processes and data follow TM Forum eTOM (GB921) and SID (GB922); components fit the Open Digital Architecture (ODA).

Standards and references:
- TM Forum TMF620 — Product Catalog Management API
- TM Forum TMF622 — Product Ordering API
- TM Forum TMF629 — Customer Management API
- TM Forum TMF635 — Usage Management API
- TM Forum TMF638 — Service Inventory API
- TM Forum TMF640 — Service Activation and Configuration API
- TM Forum TMF641 — Service Ordering API
- TM Forum TMF678 — Customer Bill Management API
- TM Forum GB921 · GB922 — eTOM business process framework · SID information framework
- TM Forum ODA — Open Digital Architecture

### MVNO models: who owns what

*Operating models*

MVNO models differ in how much of the stack the brand runs itself. The more it owns, the more control it has over roaming, eSIM, pricing and service features — and the more it has to operate.

Figure: FIG. 2 — Ownership of the stack by MVNO model. MVNO models: reseller owns brand and care; light MVNO also billing; full MVNO also SIM/IMSI and core; radio stays with the host operator

**Q: Light MVNO or full MVNO?**

A light MVNO owns the brand, tariffs and billing but uses the host's core network and SIMs. A full MVNO runs its own core (HLR/HSS, policy) and issues its own SIMs and IMSI range, which gives control over roaming, eSIM and service features.

**Q: Can an operator host MVNOs with this platform?**

Yes — we provide the platform and processes to onboard and run MVNO partners on a host network.

Glossary:
- **Host operator** — The network operator whose radio access the MVNO uses.
- **MVNE** — Mobile virtual network enabler: provides the platform an MVNO runs on.
- **IMSI range** — Block of subscriber identities assigned to a network (E.212).