TLDR
- A BSS in telecom runs an operator’s customer and revenue side; the OSS (operations support system) runs the network.
- Seven components share the work, from the first customer record to the invoice.
- TM Forum, the telecom industry association, publishes Open APIs (application programming interfaces) that standardize how these components connect. TMF620 is the one for the product catalog.
- The BSS rarely touches network equipment itself. Usage arrives as AAA (authentication, authorization, and accounting) records, and plan rules leave through policy control, which enforces them on live sessions.
Definition
A telecom BSS (business support system) is the set of systems an operator uses to run the customer side of the business. Its components are CRM (customer relationship management), product catalog, order management, charging, billing, mediation, and self-care. Together, they turn a plan into an order, an order into an active service, and network usage into a bill.
What a telecom BSS does?
A telecom BSS keeps four records in step for every subscriber: who they are, what they bought, what they used, and what they owe. Let those records drift and customers can end up billed for plans they never activated.
Separating business systems from network systems isn’t a new idea. ITU-T, the International Telecommunication Union’s standards arm, set out an early form of it in Recommendation M.3010 (clause 9.5), which layers business and service management above network and element management. Today’s BSS architecture still follows roughly the same line.
TM Forum’s Open Digital Architecture (ODA) takes the same idea into software, breaking the stack into reusable components that each expose Open APIs.
Figure 1. The telecom BSS stack: seven components with their TM Forum Open APIs, and the network functions below them
In live deployments, the BSS faults we run into rarely sit inside one component. They sit at the seams. A plan that’s in the catalog but missing from charging, say, or an order that completes while billing never starts.
The seven BSS components
Each of the seven telecom BSS modules owns one stage of the customer lifecycle and shares its data through a TM Forum Open API.
| Component | What it does | TM Forum Open API |
| CRM | Holds customer records and account history | TMF629 Customer Management |
| Product catalog | Defines what is sold and at what price | TMF620 Product Catalog Management |
| Order management | Turns a purchase into tracked fulfillment tasks | TMF622 Product Ordering Management |
| Charging | Prices usage against plans and balances, in real time if needed | TMF654 Prepay Balance Management |
| Billing | Turns charges and payments into invoices | TMF678 Customer Bill Management |
| Mediation | Collects and cleans raw network usage records | TMF635 Usage Management |
| Self-care | Lets customers manage their own accounts | Calls TMF620, TMF622, TMF629, and TMF678 |
1. CRM
Every other component asks CRM who the customer is. CRM keeps identity, account, and consent records, along with the history of every sales or support contact, and where regulators require identity checks at signup, mobile operators store those records here too.
2. Product catalog
If a plan isn’t in the catalog, nothing downstream can sell it, charge for it, or bill it. Every plan, add-on, bundle, and price lives in the product catalog, together with the rules on who’s allowed to buy them. That’s why the web shop and the retail stores show the same offers: they read the same catalog.
3. Order management
Order management checks each purchase against the catalog, then breaks it into tasks like activating the line and shipping the router. It follows every task through to completion. If a step fails, the order can be rolled back, so nothing is left half-done.
4. Charging
Charging rates usage (telecom shorthand for putting a price on it). An online charging system (OCS) approves usage before it happens, which is what prepaid plans need; offline charging prices it afterward. Both are defined by the 3rd Generation Partnership Project (3GPP) in Technical Specification (TS) 32.240, clauses 4.1.2 and 4.1.1.
5. Billing
For postpaid customers, billing gathers each cycle’s fees, rated usage, discounts, and taxes into a single invoice. Collections sit here too, from the first payment reminder to service limits on overdue accounts. There’s more detail in our guide to telecom billing systems.
6. Mediation
Raw usage records often reach the BSS duplicated and in mixed formats, so mediation cleans them up and converts them into the single format that charging and billing can read. TS 32.240 (clause 4.1.1) names the billing mediation device as one of the systems that receive offline charging records.
7. Self-care
Self-care is the web portal or app where customers buy plans, pay bills, and check usage. It doesn’t hold much data of its own; it reads from the other components through their APIs. And top-ups or plan changes made there don’t need a call to the contact center.
How BSS connects to the network
In most stacks, the BSS doesn’t configure routers or gateways itself. BSS and AAA integration runs both ways: usage flows up from AAA accounting into mediation and charging, and plan rules flow down from the BSS to policy control.
The AAA server authenticates each subscriber as they connect, then logs the session’s start, periodic updates on the time and data used, and finally the session’s end using RADIUS accounting messages (RFC 2866).
When an allowance runs out or a customer switches plans, the BSS tells policy control. On RADIUS-based fixed and Wi-Fi sessions, policy control then sends a CoA-Request (RFC 5176) that changes speed or access without forcing a reconnect.
Picture one fiber signup at a regional internet service provider (ISP), viewed from the BSS side. For the network side, start with the difference between OSS and BSS.
- The customer picks a plan in self-care, which pulls the price from the product catalog.
- CRM sets up the customer and billing accounts, and records consent.
- Order management splits the order into tasks: activate the line through the OSS, ship the router, create the AAA subscriber profile.
- Charging sets up the plan’s data allowance.
- Once the router connects and the AAA server authenticates it, accounting records start flowing to the BSS.
- Mediation cleans those records and charging rates them; billing then adds the charges to the first invoice.
- When the allowance runs out, charging tells policy control to slow the session, and self-care offers a top-up.
Full suite or prebuilt BSS
A full suite and a prebuilt BSS cover the same core functions; the difference is who builds them and who runs them. The full suite suits operators with lots of services, complex pricing, and an in-house team that wants control over every rule.
Alepo Digital BSS is the full-suite telecom BSS platform for ISPs, fiber operators, mobile virtual network operators (MVNOs), and mid-size mobile operators. It pairs convergent charging and billing (prepaid and postpaid on one platform) with configurable products and TM Forum Open APIs. It can run on premises or in the cloud.
BSS Now, Alepo’s prebuilt BSS, is a cloud BSS for MVNOs and ISPs. It’s the same Digital BSS platform, delivered as a pre-integrated service, so there’s less for your team to build and run.
If your pricing is standard and getting to market fast matters most, start with prebuilt. Where the BSS itself is how you compete, the full suite is the better fit.
Conclusion
Whichever Digital BSS approach you choose, the goal remains the same: take every customer seamlessly from plan selection to the first invoice, with every component working in sync.
The biggest challenges often lie not within individual systems, but at the handoffs between them. Start by asking two critical questions: Does every plan in your catalog exist in charging? And does every completed order automatically trigger billing? These connections are essential to delivering a seamless customer journey and ensuring revenue flows as expected.
Planning your Digital BSS transformation? See how Alepo brings catalog, order management, charging, and billing together on one integrated platform.
Book a demo to explore how Alepo can help you simplify operations, streamline service activation, and ensure a smoother path from order to invoice.
FAQs
Q1. What is BSS in telecom?
BSS is the commercial side of an operator’s systems: anything a customer sees about prices, orders, or bills comes from it.
Q2. What are the components of a BSS?
The core seven are CRM, product catalog, order management, charging, billing, mediation, and self-care. Bigger operators often add partner settlement and analytics on top.
Q3. How is BSS different from OSS?
The BSS handles customers and revenue, while the OSS runs network resources and service activation. They meet at order management, which is where a commercial order turns into a technical one.
Q4. What is a digital BSS?
A digital BSS is built from modular components that your team configures, so changes don’t need new code. It reaches customers through apps and web self-care as well as through stores and call centers.
Q5. Do small ISPs need a full BSS?
Any ISP that bills customers is already doing BSS work, even if it all lives in spreadsheets. Small operators often don’t need a custom-built suite; a prebuilt BSS for ISPs and MVNOs covers the core components without an integration team.
Q6. How does a BSS get usage data from the network?
Fixed and Wi-Fi networks usually report usage as AAA accounting records, whereas mobile networks send charging events defined by 3GPP. Offline records go through mediation first; online events go straight to charging.
Q7. What are TM Forum Open APIs?
They’re standard web APIs that TM Forum publishes for passing data between BSS and OSS components. Each one has a TMF number (TMF678, for instance, handles customer bills), and together they’re part of TM Forum’s Open Digital Architecture.
