Internal · Sales & Engineering

Telecom Industry Primer

Understanding the three parallel business models in telecom, how they interact, and where Signal Telecom Suite fits. Required reading for all sales and engineering team members.

1. The Three Business Models

Carriers and ISPs are parallel infrastructure owners. MVNOs sit above them as an abstraction layer — consuming infrastructure from both and presenting a unified service to the end customer.

MVNO

Abstraction layer — owns nothing physical
Buys mobile capacity from carrier + internet transit from ISP
Customer sees one brand, one bill, one app

▲ Abstraction — customer doesn’t see what’s below ▲

↑

Mobile capacity

↑

Internet transit

Carrier (MNO)

Owns spectrum license
Owns BTS towers
Owns core network (EPC/5GC)

ISP

Owns fiber/wireless infra
Owns routers, APs, OLTs
Owns backbone network

▼ Parallel infrastructure owners ▼

Downstream ISP

Buys wholesale from ISP
Resells under own brand

Hybrid ISP + MVNO

Owns fiber (ISP layer)
Buys mobile from a host carrier (MVNO layer)
Sells wholesale to downstream ISPs

Entity	Owns	Buys From	Sells To	Examples
Carrier (MNO)	Spectrum, towers, core	—	Mobile subscribers, MVNOs	Airtel, MTN, Safaricom, Jio, AT&T
ISP	Fiber, routers, APs, OLTs	Upstream transit	Internet subscribers, downstream ISPs	Comcast, ACT Fibernet, regional fibre operators
MVNO	Nothing physical	Mobile capacity from carrier	Mobile subscribers	Google Fi, Lycamobile, AeroVoyce
Downstream ISP	Minimal (CPE only)	Wholesale bandwidth from ISP	Local subscribers	Small regional ISPs

Key insight: Some companies operate in multiple models simultaneously. Jio is both a carrier AND an ISP (JioFiber). A regional ISP may also want to become an MVNO on a Tier-1 host. The platform supports both tracks side by side so a hybrid operator doesn't run two separate BSS stacks.

2. What Each Model Needs from Our Platform

ISP Needs

Capability	Our Module	What It Does
Customer management	SIG-ID	CRM, KYC, lifecycle
Service plans & subscriptions	SIG-PROV	Broadband plans with speed/data caps
Subscriber authentication	SIG-RAD	RADIUS AAA for WiFi/broadband access
Router/switch configuration	SIG-NET	NETCONF/YANG to Juniper, Cisco, etc.
CPE provisioning	SIG-CPE	REST APIs to Cambium, MikroTik, Ubiquiti, etc.
Usage metering	SIG-RATE	RADIUS accounting → usage records
Billing	SIG-BILL	Invoices with PDF generation
WiFi hotspot login	Captive Portal	Splash page for hotel/airport WiFi

MVNO Needs

Capability	Our Module	What It Does
Customer management	SIG-ID	Same CRM — shared with ISP
Mobile plans	SIG-PROV	Data/voice/SMS plans
SIM lifecycle	SIG-SIM	ICCID, IMSI, Ki/OPc, activation
HSS/HLR integration	SIG-SIM	AKA key sync to carrier HSS
Carrier interconnect	SIG-ICX	CDR settlement, wholesale rates
CDR processing	SIG-RATE	Carrier CDR → rated charges
Billing	SIG-BILL	Subscriber invoices
Enterprise bulk SIM	SIG-SIM + Enterprise	500+ SIMs, departments, cost centers

Notice: An MVNO does NOT need SIG-RAD, SIG-NET, or SIG-CPE. The carrier owns the radio network and RADIUS. The MVNO only manages SIMs, billing, and customer relationships.

Wholesale ISP (B.Carried) Needs

Capability	Our Module	What It Does
Tenant management	Tenant System	Each downstream ISP = separate tenant
Schema isolation	Database	PostgreSQL schema-per-tenant
White-label portals	Portal System	Each ISP gets own branded dashboard
Wholesale billing	SIG-BILL	Bill downstream ISPs for bandwidth
Cross-tenant views	Ops Portal	Infrastructure owner sees all tenants

3. Hardware at Each Layer

Our OSS needs to talk to different device types, each speaking a different protocol:

Device Type	Purpose	Protocol	Vendors	Who Owns It
Core Router	Backbone routing	NETCONF/YANG	Juniper MX, Cisco ASR	ISP
Edge Router	Customer gateway	NETCONF/YANG	Juniper SRX, Cisco ISR	ISP
Switch	LAN / data center	NETCONF / SNMP	Juniper EX, Arista	ISP
WiFi AP	Wireless access	Vendor REST API	Cambium, Ubiquiti, HFCL	ISP
OLT	Fiber to the home	SNMP / REST	Calix, DZS, STL, ADTRAN	ISP
CPE / ONT	Customer premises	REST API	MikroTik, Grandstream	ISP (managed)
Microwave	Tower backhaul	SNMP / REST	Ceragon, RADWIN	ISP
BTS / eNodeB	Cellular radio	Vendor NMS	C-DOT, Nokia, Ericsson	Carrier (MNO)
Small Cell	Indoor cellular	REST API	Baicells, Lekha, ip.access	Carrier / Enterprise
RADIUS Server	Auth / accounting	RADIUS protocol	FreeRADIUS	ISP
HSS / HLR	Mobile subscriber auth	Diameter / S6a	Open5GS	Carrier or Full MVNO

Key insight for sales: An MVNO does not need to talk to any physical network device. The carrier's BSS/OSS handles that. The MVNO only talks to the carrier's HSS (for SIM auth) and receives CDRs (for billing). Our SIG-NET, SIG-CPE, and SIG-RAD modules are ISP-only.

4. Integration Approach

We don't connect to each device individually. Where possible, we connect to vendor management platforms:

We Talk To	Covers	Protocol
Junos Space / Paragon	All Juniper devices	REST API
cnMaestro	All Cambium devices	REST API
UniFi Controller	All Ubiquiti devices	REST API
Calix Cloud	All Calix OLTs/ONTs	REST API
Direct NETCONF	Cisco, Nokia, Huawei	NETCONF/YANG
Direct SNMP	Legacy / no NMS	SNMP v2c/v3
FreeRADIUS	Subscriber auth	RADIUS protocol
Open5GS	MVNO mobile core	Diameter/S6a

5. The Hybrid Operator Archetype

A common shape we see across regional operators in emerging markets: a fibre/FWA ISP today, with an ambition to add mobile (MVNO on a host carrier) and a wholesale layer (downstream ISPs riding their backbone). This archetype is the one that benefits most from a single platform — they otherwise end up running three separate billing stacks.

Hybrid ISP → MVNO → wholesale operator

Today (data-only ISP):

Sells data only over its own infrastructure (fibre, fixed-wireless, WiFi)
No voice, no SIM cards, no spectrum, no carrier relationship yet
Enterprise- and SME-led; consumer subscriber base just starting
Equipment mix typically Cambium, Ubiquiti, Tejas, FreeRADIUS, vendor NMS platforms
Billing is fragmented — invoicing in an ERP (Odoo or similar), provisioning in an older ISP-billing tool, manual reconciliation in between

Where this archetype wants to go:

Consumer broadband + hotspots — residential and roaming-voucher tiers on the same fibre/WiFi footprint
MVNO — buy wholesale mobile capacity from a host carrier to offer voice + data under their own brand
Wholesale — resell backbone capacity to downstream ISPs, each running their own customers and billing
Digital services — agritech, healthtech, edtech bundles under one customer ID
Physical retail attached to connectivity — agri inputs, solar kits, devices invoiced alongside the connectivity bill

Why no spectrum is needed for the ISP layer: data over WiFi/fibre doesn't require a spectrum licence. Only mobile cellular (4G/5G) needs spectrum, which only carriers hold. When this archetype adds an MVNO line, they buy capacity from a host carrier — they don't need their own spectrum.

Typical network: protected fibre rings, redundant upstream feeds, zero-contention or low-contention model, 24/7 NOC.

How the platform maps to this archetype

Business Line	Platform Track	Modules Used
Residential + SME broadband	ISP Track	SIG-ID, SIG-PROV, SIG-RAD, SIG-NET, SIG-CPE, SIG-RATE, SIG-BILL
MVNO (individual)	MVNO Track	SIG-ID, SIG-PROV, SIG-SIM, SIG-ICX, SIG-RATE, SIG-BILL
MVNO (enterprise)	Enterprise Extension	Above + Enterprise Accounts, bulk SIM, cost-centre billing
Wholesale to downstream ISPs	Tenant Management	Tenant system, schema isolation, ops portal, white-label

The platform pitch: most OSS/BSS stacks make a hybrid operator choose — ISP or MVNO or wholesale. Sigtel supports all three tracks in one platform, with a downstream ISP onboarded as a fully isolated tenant on the same infrastructure. One platform, three (or more) business lines.

6. Common Misconceptions

Misconception	Reality
MVNOs are parallel to ISPs	No. Carriers and ISPs are the parallel entities — both are infrastructure owners. MVNOs sit above them as an abstraction layer, consuming from both and presenting a unified service to the end customer.
You need one device type per adapter	Vendor NMS platforms (cnMaestro, Junos Space) manage all of a vendor's devices through one API.
Carrier and ISP are always separate	Some companies do both (Jio is carrier + ISP, many regional fibre operators add an MVNO line on a host carrier).
An MVNO needs routers and RADIUS	No. The carrier handles radio/auth. MVNO only needs SIM lifecycle, CDR processing, and billing.
Enterprise = big individual customer	Enterprise customers need their own infrastructure (dedicated hardware, SIM pools, cost center billing). They're not just "bigger" consumers.

Related Resources

Visual Glossary → MVNO Architecture & AKA → Integration Guide →

Signal AI Labs · Internal · Sales & Engineering Reference