OSS – Operational Support Systems
Definition: OSS is the operational control layer responsible for monitoring, provisioning, assurance, and network lifecycle management of telecom networks.
What Does OSS Do?
OSS performs several core operational functions, many aligned with FCAPS principles:
- Network Monitoring – Continuously checks health of routers, antennas, fibre cables, and 5G base stations (gNBs). Alerts when thresholds are crossed. Modern OSS increasingly operates in near real-time using streaming telemetry, event buses, and AIOps platforms rather than only scheduled polling systems.
- Fault Management (FMS) – Detects failures, correlates alarms from multiple devices, suppresses duplicate alerts, and creates trouble tickets for field engineers.
- Performance Management (PM) – Collects metrics: traffic volume (bytes), latency (ms), packet loss (%), CPU utilisation (%), PRB utilisation (radio capacity).
- Provisioning & Activation – OSS orchestration or provisioning systems send configuration commands to network devices to deliver customer services.
- Inventory Management – Tracks physical equipment (routers, switches, cables) and logical resources (IP addresses, VLANs, ports).
Northbound vs Southbound Communication
OSS communicates in two directions:
- Southbound: OSS talks to network devices and EMS systems using protocols like SNMP, Netconf, gNMI, or CLI.
- Northbound: OSS exposes processed information to higher systems like BSS, dashboards, analytics, or AIOps platforms using REST APIs, TMF Open APIs, Kafka, or event buses.
Real-World Example
When a customer activates a new 5G SIM card:
- BSS captures customer order and sends to OSS via API (TMF641 Service Order or custom integration APIs).
- OSS orchestration/provisioning systems check inventory for available gNB capacity and IP resources.
- OSS sends configuration commands to the gNB and core network (5GC).
- OSS confirms activation back to BSS with service ID and activation timestamp.
- BSS starts billing and updates CRM.
The customer never sees OSS – but without it, activation would fail.
Real Telecom Challenge: Multi-Vendor Integration
Telecom operators rarely use equipment from only one vendor. OSS must normalize alarms, KPIs, inventory models, and telemetry coming from Nokia, Ericsson, Huawei, Cisco, Juniper, and many others into a unified operational view.
Connection to BSS (For BSS Professionals)
If you come from BSS (CRM, Billing, Order Management), here is how OSS relates:
| BSS handles: | Customers, products, orders, pricing, invoicing, CRM, revenue assurance |
| OSS handles: | Network devices, alarms, performance, inventory, activation, topology |
| Integration point: | BSS sends "activate service" orders → OSS executes → OSS returns "active" status → BSS begins billing |
Why This Matters in Real Telecom Operations
OSS directly impacts customer experience and operator revenue. Poor OSS performance leads to:
- Call drops – Faults not detected or correlated quickly enough
- Broadband outages – Configuration errors during provisioning
- Failed enterprise VPN activation – Inventory data out of sync with actual network
- SLA penalties – Performance monitoring misses degradation before customer reports
- Revenue leakage – Service active on network but BSS not billing due to activation confirmation failure
Industry Examples – OSS Platforms by Vendor
| Vendor | OSS Platform | Key Capabilities |
|---|---|---|
| Nokia | NetAct | Radio network management, SON, performance analytics |
| Ericsson | ENM (Ericsson Network Manager) | Multi-vendor RAN and core management |
| Huawei | U2020 / M2000 | Wireless network management, fault correlation |
| Cisco | Cisco Prime / DNA Center | IP/MPLS network management, assurance |
How OSS Fits in Telecom Architecture
OSS sits between the physical network and business systems (BSS).
Common Interview Questions
Q1. What is the difference between OSS and BSS?
OSS manages network operations (faults, performance, inventory, provisioning). BSS manages business and customer operations (orders, billing, CRM, products). They integrate via APIs for order-to-activation and usage-to-billing flows.
Q2. Why is OSS critical for telecom operators?
OSS enables lifecycle management of network services. Without OSS, operators cannot provision new customers, detect faults, monitor performance, or plan capacity expansions.
Q3. What is the biggest OSS challenge in real networks?
Multi-vendor integration. Normalizing alarms, KPIs, and inventory models across Nokia, Ericsson, Huawei, Cisco, and others into a unified operational view is extremely complex.
Key Terms You Should Know
Takeaways for You
- OSS is the operational control layer for network monitoring, fault management, performance, provisioning, and inventory.
- BSS triggers actions (orders), OSS executes them (activations) and reports back.
- Southbound = OSS talks to network devices. Northbound = OSS exposes data to BSS and analytics.
- Real-world OSS must handle multi-vendor complexity – Nokia, Ericsson, Huawei, Cisco all in one network.
- Poor OSS directly causes customer outages, SLA breaches, and revenue leakage.
Recommended Next Learning Path