In telecom, OSS means Operations Support Systems and BSS means Business Support Systems. If you were looking for open source software, that is a different OSS. This page covers the telecom meaning.
You have used both today. Choosing a phone plan, paying for it and getting a bill all ran through a BSS. Your SIM activating, your phone finding signal and an engineer fixing a faulty cell site before you noticed all ran through an OSS. One side takes the order. The other makes the network deliver it.
This guide also traces one eSIM order from checkout to first data session. Then it maps who owns each function when a brand launches an MVNO: a mobile virtual network operator, which sells service on another company’s network.
What are OSS and BSS?
OSS (Operations Support Systems) is the software a telecom operator uses to provision, monitor and maintain its network. BSS (Business Support Systems) is the software that manages customers, products, orders, charging and billing. BSS takes the order and bills for it; OSS makes the network deliver it. Together they run every mobile, broadband and IoT service.
They meet twice on every order: when the BSS sends it to the OSS for activation, and when usage flows back so the BSS can charge for it.
What does OSS stand for in telecom?
OSS stands for Operations Support System, usually used in the plural as Operations Support Systems. You will also see Operational Support System. In GSM architecture documents, OSS meant the Operation and Support Subsystem, the part of a GSM network that monitored and controlled the other elements. All three names point to the same job: running the network.
What does BSS stand for in telecom?
In telecom, BSS stands for Business Support System, the software for customers, products, orders and billing. The same letters mean Base Station Subsystem in GSM radio networks and Basic Service Set in Wi-Fi. Our guide to the other meanings of BSS explains those.
OSS vs BSS: the differences at a glance
Use this table to place a system, a team or a KPI on the right side of the line.
| OSS (Operations Support Systems) | BSS (Business Support Systems) | |
|---|---|---|
| Faces | The network and its equipment | The customer and the money |
| Core question | Is the service working? | Who bought what, and have they paid? |
| Main functions | Provisioning and activation, inventory, fault and performance management, network management | Product catalogue, CRM, order management, charging, billing, revenue assurance |
| Main users | Network engineers, network operations centre (NOC), field operations | Sales, customer care, marketing, finance |
| Typical buyer | CTO and network operations | CIO, CFO and chief revenue officer |
| KPIs | Uptime, mean time to repair (MTTR), activation success rate, latency | ARPU, churn, billing accuracy, customer satisfaction |
| Failure looks like | Outages, failed activations, dropped sessions | Wrong invoices, stalled orders, revenue leakage |
Order-to-activation time belongs to both: it starts in the BSS when the customer pays and ends in the OSS when the line goes live. Track it across the boundary.
Is billing part of OSS or BSS?
Billing is BSS. The confusion comes from FCAPS, the ITU-T model of network management functions, which includes “accounting”: measuring how much of the network each subscriber uses and producing usage records. That measurement happens on the network side. Rating those records against a price plan, applying discounts and producing an invoice is BSS work.
In 5G, 3GPP places real-time charging in a Charging Function (CHF) within its converged charging architecture, defined in 3GPP TS 32.240 and TS 32.290. The industry usually counts that charging system as BSS. It matters most if you plan to sell 5G Standalone services with usage-based pricing.
One eSIM order, traced from checkout to first data session
Here is one order for an eSIM data plan sold by an MVNO, followed through every system it touches. The last column shows the usual split in a light MVNO, where an MVNE runs the platforms and a host operator runs the network.
| # | What happens | System | Side | Usual owner (light MVNO) |
|---|---|---|---|---|
| 1 | Customer picks a 10 GB plan. The store checks that the phone supports eSIM. | Product catalogue, eligibility check | BSS | MVNE platform, MVNO’s catalogue |
| 2 | Customer pays. An account and an order are created. | CRM, order management, payments | BSS | MVNE platform |
| 3 | The order is split into service and resource requests and sent to the OSS, often over TM Forum Open APIs such as TMF622 Product Ordering. | Order orchestration | BSS to OSS | MVNE platform |
| 4 | A SIM identity (ICCID and IMSI) and a phone number are reserved. | Resource inventory | OSS | MVNE, from host or MVNO ranges |
| 5 | The subscriber profile and data policy are written to the host network’s subscriber database (HSS in 4G, UDM in 5G). | Service activation | OSS | MVNE, through host interfaces |
| 6 | An eSIM profile is prepared on the SM-DP+ server and the customer gets a QR code or in-app activation. | eSIM provisioning (GSMA SGP.22) | OSS | MVNE |
| 7 | The phone downloads the profile, attaches to the network and opens a data session. | Radio and core network | Network | Host MNO |
| 8 | Usage is reported to the charging system and rated against the 10 GB allowance in real time. | Charging and rating | BSS | MVNE platform |
| 9 | The customer sees usage in the app, gets a top-up offer near the limit and receives a renewal or invoice. | Self-care, billing | BSS | MVNO brand on MVNE tools |
| 10 | If the phone cannot connect, support checks line status and network alarms and opens a ticket. | Assurance, CRM case | OSS and BSS | MVNE tools; host for network faults |
Two handoffs decide whether this feels instant or broken. At step 3, a BSS that cannot see activation status will tell the customer the order is complete while the network is still working on it. At step 8, a charging system that only receives usage files overnight cannot stop a line at its allowance or offer a top-up before the customer runs out.
Devices without a screen follow the same path with a different provisioning standard. IoT eSIMs use GSMA SGP.32, which our comparison of SGP.22 vs SGP.32 eSIM standards explains. For step 6 in more depth, see how remote SIM provisioning works.
Who owns OSS and BSS in an MVNO?
Four kinds of company share the work. A mobile network operator (MNO) owns spectrum and towers. A mobile virtual network operator (MVNO) sells mobile service under its own brand on an MNO’s network. A mobile virtual network enabler (MVNE) supplies the OSS, BSS and host integration so the MVNO does not have to build them. A mobile virtual network aggregator (MVNA) buys wholesale capacity and resells it to MVNOs. Our guide to MNO, MVNO, MVNE and MVNA roles covers the commercial side.
Who runs each function depends on the MVNO model. A branded reseller owns little more than the brand. A full MVNO runs its own core network and SIM ranges. Most new launches sit in between, as light MVNOs.
| Function | Branded reseller | Light MVNO | Full MVNO |
|---|---|---|---|
| Radio network and towers | Host MNO | Host MNO | Host MNO |
| Core network and subscriber database (HSS or UDM) | Host MNO | Host MNO | MVNO |
| SIM and eSIM profiles, IMSI ranges | Host MNO | Host MNO or MVNE | MVNO (own IMSI range) |
| Provisioning and activation (OSS) | Host MNO | MVNE, through host interfaces | MVNO |
| Network monitoring and faults (OSS) | Host MNO | Host MNO for the network; MVNE for line status | MVNO for its core; host for radio |
| Product catalogue and pricing (BSS) | Reseller sets retail price on host plans | MVNO decides; MVNE platform runs it | MVNO |
| Charging, rating and billing (BSS) | Host or aggregator | MVNE platform; MVNO owns pricing and invoices | MVNO |
| CRM, self-care and support (BSS) | Reseller, often with host support | MVNO, on MVNE tools | MVNO |
| Wholesale settlement with the host | Host or aggregator | MVNE or MVNO | MVNO |
| Brand, marketing and sales | Reseller | MVNO | MVNO |
Contracts vary, so treat this as a starting map and confirm each row with your host operator and MVNE. The rows that cause disputes later are SIM ownership, number ranges and customer data, because they decide how hard it is to change suppliers. IoT fleets on several networks add a layer, covered in multi-IMSI vs eUICC.
For the full commercial picture, start with how MVNO business models work and what an MVNO launch costs.
Choosing an MVNE? Our OSS/BSS checklist: 10 questions before you sign an MVNE turns this table into questions for a vendor call, from data ownership to real-time charging.
What an OSS does
An OSS system (Operations Support System) is a collection of software tools that telecom providers use to manage, monitor and maintain their network infrastructure. Most operators run OSS products from several vendors, grouped around four jobs.
Service fulfilment: provisioning and activation
Fulfilment turns a sold product into a working service. The OSS works out what has to change in the network, sends the configuration to the right elements and confirms the result. For a mobile line that means the subscriber profile, the SIM or eSIM profile, and the data policy and allowance.
Network and service inventory
Inventory records what exists and how it connects: physical equipment, logical resources such as IP addresses, IMSI and ICCID ranges and phone numbers, and the CRM Services help providers understand customer needs, personalize experiences, and reduce churn. When inventory is wrong, fulfilment allocates resources that are already in use, and assurance cannot tell which customers an alarm affects.
Service assurance: faults and performance
Assurance covers everything after activation. Fault management collects alarms, removes duplicates, links them to a probable cause and opens a trouble ticket. Performance management collects counters such as throughput, latency and dropped sessions and compares them with thresholds. For an IoT fleet, the same function shows up as per-SIM usage and connection status.
Network and element management (NMS and EMS)
An element management system (EMS) manages one vendor’s equipment. A network management system (NMS) sits above several EMSs and gives a single cross-vendor view. The split comes from the layered model in ITU-T Recommendation M.3010, the Telecommunications Management Network (TMN) standard.
The FCAPS model
FCAPS names the five management functional areas set out in ITU-T Recommendation M.3400: fault, configuration, accounting, performance and security. OSS requests for proposal still use it to group requirements.
| Area | What it covers | Example in a mobile network |
|---|---|---|
| Fault | Detect, isolate, fix and log faults | A cell site raises an alarm; the OSS links it to related alarms and opens a ticket |
| Configuration | Record and change element settings and service paths | Pushing a new data policy to every line in an IoT fleet |
| Accounting | Measure resource use and produce usage records | Usage records per SIM, which the BSS then rates and bills |
| Performance | Track throughput, latency, loss and utilisation against thresholds | Latency on one cell breaches its threshold during peak hours |
| Security | Control and audit access to network assets | Logging every administrator change to the subscriber database |
What a BSS does
A BSS (Business Support System) is the software that manages the customer-facing and commercial side of a telecom business. Its functions follow the customer from the first offer to the final payment.
| Function | What it does | Example in an MVNO |
|---|---|---|
| Product catalogue | Defines plans, prices, bundles, eligibility rules and regional availability in one place | A 2 GB watch plan priced differently for retail and enterprise customers |
| CRM | Holds accounts, contacts, active services, cases and consent | A support agent sees the customer’s lines, plan and last ticket |
| Order management | Captures, validates and orchestrates orders, including the handoff to the OSS | A plan change triggers a new data policy on the network |
| Charging and rating | Prices usage against the plan in real time (online) or after the event (offline) | A line reaches its allowance and is slowed or offered a top-up |
| Billing and payments | Produces invoices, takes payments, handles collections and taxes | A monthly invoice with usage, discounts and tax lines |
| Revenue assurance and fraud | Checks that everything the network carried was billed, and flags abuse | Finding lines that used data the BSS never rated |
| Partner settlement | Reconciles host operator invoices and bills or pays resellers | Matching the host’s wholesale invoice to your own usage records |
| Self-care and digital sales | Portals, apps and checkout where customers buy and manage service | eSIM purchase and activation in a branded app |
For an MVNO, charging and partner settlement decide the margin. Our comparison of MVNO billing platforms covers how to test both before you sign.
The standards behind OSS and BSS
Vendor brochures reuse the same handful of standards. This table shows what each one defines and why a buyer should ask about it.
| Standard | Published by | What it defines | Why it matters when you buy |
|---|---|---|---|
| TMN, M.3010 | ITU-T | Layered management model: business, service, network and element management above the network elements | Explains the EMS and NMS split in OSS products |
| FCAPS, M.3400 | ITU-T | Five management functional areas | Common way to group OSS requirements |
| eTOM) (Business Process Framework) | TM Forum | Map of telecom business processes, including fulfilment, assurance and billing | Lets you check which processes a product covers |
| SID (Information Framework) | TM Forum | Shared data model for customers, products, services and resources | Keeps BSS and OSS records consistent |
| ODA and Open APIs | TM Forum | Component architecture and standard REST APIs such as TMF620 Product Catalog and TMF622 Product Ordering | Lets you replace one component without rebuilding every integration |
| 5G converged charging, TS 32.240 and TS 32.290 | 3GPP | Charging architecture and the Charging Function (CHF) in the 5G core | Decides whether charging can rate 5G usage in real time |
| SGP.22 and SGP.32 | GSMA | Remote eSIM provisioning for consumer devices (SGP.22) and IoT (SGP.32) | Decides how profiles reach phones, watches and sensors |
What is changing in OSS and BSS, and what is not
Operators are replacing large suites with components that expose standard APIs. TM Forum’s Open Digital Architecture defines those components and their Open APIs. Its ODA Component Conformance Certification became generally available in June 2025, by which time nearly 100 companies had certified more than 1,700 Open API implementations. For a buyer, that makes “open” something you can check: ask which of a vendor’s APIs are certified.
Network operations are moving from alarms that wait for a person to closed loops that diagnose and fix problems on their own. TM Forum grades this on six levels, from Level 0 (manual) to Level 5 (fully autonomous). In its survey of 80 operators, 20 percent expected to reach Level 4 or above by 2027, and 81 percent were targeting it by 2030. Automation needs accurate inventory and real-time events, so a siloed OSS and BSS slows it down.
Smaller operators and brands also buy OSS and BSS as a service instead of licensing software, a model covered in our guide to Telecom-as-a-Service (TaaS).
The split itself has stayed put. Someone still takes the order and someone still makes the network deliver it. Cloud-native stacks move that boundary into APIs, and the boundary still decides where orders stall.
Where Spenza fits: OSS and BSS for MVNOs without building the stack
Spenza is an MVNE platform for MVNOs, MSPs and resellers, device makers and IoT teams. It covers the MVNE column in the ownership table above, in parts that share one data model and one API.
| OSS or BSS function | What Spenza does | Product |
|---|---|---|
| Provisioning, activation and connectivity management (OSS) | Operator access in 180+ countries, SIM and eSIM provisioning, and routing across operators through one API | TelecomHub |
| Catalogue, charging, billing and settlement (BSS) | Custom prepaid, postpaid and pay-as-you-go plans, rating, parent-child billing for each reseller tier, and automatic plan step-ups | ControlHub |
| Self-care and digital sales (BSS) | Branded subscriber portal, checkout, and a Shopify app that sells plans and devices together | UXHub |
| Operations automation | AI agents for plan, finance and compliance workflows, and an MCP server with 79 tools mapped to the Partner API | AgentHub and the Spenza MCP server |
That last row changes the order trace above. An AI assistant connected to the MCP server can call list_sims to find lines near their allowance and get_sim_usage to check each one. It can then call provision_esim to issue a new profile, within the approval rules you set.
Customer results so far: Butlr cut the time to launch connectivity in a new region from 60 days to 7 and reduced connectivity management costs by 40 percent. MSP-A cut reseller onboarding from weeks to a few days. RocketPhone launched a branded business mobile service without building its own telecom stack.
Spenza does not manage radio or core network equipment. A full MVNO that runs its own core keeps network-facing assurance tools for those elements and can use Spenza for provisioning, plans, billing and self-care on top.
Conclusion
OSS and BSS split telecom software along one line: the commercial side that sells and bills, and the operational side that delivers and repairs. Customers rarely see either system. They see the handoffs, when an order waits for activation or a usage alert arrives a day late.
If you run a network, you need both, and the standards above help you buy them in parts. If you are launching an MVNO, the useful question is which functions you want to own. Map them with the ownership table, test vendors with the OSS/BSS checklist, and keep the customer relationship in your own hands.
FAQs
What is the difference between OSS and BSS?
OSS (Operations Support Systems) manages the network: provisioning, inventory, fault and performance management. BSS (Business Support Systems) manages the business: products, customers, orders, charging and billing. BSS takes the order and bills for it. OSS makes the network deliver the service and keeps it working.
What does OSS stand for in telecom?
OSS stands for Operations Support System, also written Operational Support System. It is the software an operator uses to provision services, track network resources, detect faults and monitor performance. Older GSM documents use OSS for the Operation and Support Subsystem, the part of a GSM network that monitored and controlled the other elements.
Is billing part of OSS or BSS?
Billing is part of BSS. The network side measures usage and produces usage records, which the FCAPS model calls accounting. The BSS rates those records against the customer’s plan, applies discounts and taxes, and issues the invoice. Real-time charging, including the 5G Charging Function, is usually counted as BSS.
How do OSS and BSS work together?
They exchange data at two points. When a customer orders, the BSS validates the order and sends service and resource requests to the OSS, which activates the service and reports back. When the customer uses the service, the network reports usage to the BSS charging system, which rates it and bills for it.
Does an MVNO need its own OSS and BSS?
An MVNO needs OSS and BSS functions, but most do not build them. A light MVNO uses an MVNE platform for provisioning, charging, billing and self-care, while the host operator runs the network. A full MVNO that operates its own core network usually runs more of the stack itself.
What are examples of OSS and BSS systems?
OSS examples include network inventory, service activation, fault management, performance monitoring, and element or network management systems. BSS examples include the product catalogue, CRM, order management, online charging, billing and revenue assurance. Large suppliers to mobile operators include Amdocs, Ericsson, Netcracker, Nokia and Oracle. MVNOs usually get these functions from an MVNE instead.
What is FCAPS in telecom?
FCAPS stands for fault, configuration, accounting, performance and security: the five management functional areas in ITU-T Recommendation M.3400. Operators and vendors use it to group network management requirements. In FCAPS, accounting means measuring usage. Turning that usage into an invoice is a BSS job.
What is replacing legacy OSS/BSS systems?
Cloud-native components connected through standard APIs are replacing monolithic suites, guided by TM Forum’s Open Digital Architecture (ODA) and Open APIs. Many MVNOs skip the software purchase and use OSS and BSS functions as a managed MVNE platform.
