What is a telecom BSS?
A telecom BSS (Business Support System) is the software layer telecom operators use to run the commercial and customer-facing side of the network — product catalogue, ordering, billing, revenue assurance, dunning, self-service, and third-party integrations. It sits alongside the OSS (Operations Support System), which manages network provisioning, inventory, and faults.
What a BSS actually does
A modern telecom BSS covers five core capabilities: (1) product catalogue with rate plans, add-ons, bundles and lifecycle rules; (2) customer and party management, typically modelled as N:N Party Roles per TM Forum SID; (3) order capture, validation, and orchestration into downstream OSS/network systems; (4) charging, invoicing, tax, payment collection and dunning; (5) customer self-service through portals, hosted checkout and support workflows.
On top of those five, most operators need integrations — into ERPs (Bexio, SAP), into wholesale carriers (Swisscom BBCS, PortaONE), into hardware inventory, into eBill/Pingen/Stripe, and into identity verification providers (Veriff). A BSS that ships those as first-party connectors is materially cheaper to run than one where every integration is a custom project.
BSS vs OSS — the practical difference
OSS runs the network: element management, inventory, fault, service assurance, provisioning of physical and logical resources. BSS runs the business: who the customer is, what they bought, what they owe, what they can self-serve.
A well-integrated stack publishes domain events (order.created, subscription.activated, invoice.paid) from BSS into OSS and vice versa, on a shared data model. When BSS and OSS drift into separate models the operator ends up reconciling by hand — the single biggest hidden cost in legacy telco IT.
Modern vs legacy BSS
Legacy BSS is monolithic, on-prem, licensed per subscriber, and typically requires a systems integrator for every change. Modern BSS is cloud-native, API-first, SID-aligned, event-driven, and priced on a SaaS basis. The gap matters most when an operator wants to launch a new brand, MVNO, or bundle quickly — legacy stacks often take 6–18 months per launch, modern stacks target weeks.
METAVSHN is a modern BSS built specifically for ISPs, MVNOs, and telecom resellers. It is Swiss-hosted, TM Forum SID-aligned, ships first-party connectors for the Swiss and European telecom ecosystem, and is designed for operators who need to launch or migrate in weeks, not quarters.
Frequently asked
- What does BSS stand for in telecom?
- BSS stands for Business Support System. It is the software layer telecom operators use for product catalogue, customer management, ordering, billing, revenue assurance, and self-service.
- What is the difference between BSS and OSS?
- BSS runs the commercial side (customers, orders, billing). OSS runs the network side (provisioning, inventory, faults). They share data — orders flow BSS→OSS, service state flows OSS→BSS.
- Do MVNOs need a BSS?
- Yes. Even a small MVNO needs product catalogue, subscription management, billing, and self-service. Modern cloud-native BSS platforms like METAVSHN let MVNOs launch without building any of that from scratch.
- What is TM Forum SID?
- SID (Shared Information/Data model) is the TM Forum standard for how telecom entities like Customer, Product, Service, and Resource are structured. BSS platforms aligned with SID interoperate cleanly with OSS and third-party systems.