Telecom OSS Glossary
Purpose: A comprehensive reference of Telecom OSS terms, acronyms, and concepts. Use this glossary to quickly look up definitions while studying or working with OSS systems. Click "Learn More" links to explore detailed topic pages.
A
Accounting Management
FCAPSFCAPS area focused on tracking network resource usage for billing, capacity planning, and cost allocation. OSS provides usage data to BSS for rating and invoicing.
AIOps (Artificial Intelligence for IT Operations)
Modern OSSUses machine learning to analyze telemetry, detect anomalies, predict failures, and recommend remediation actions.
Alarm
FMSAn actionable abnormal condition requiring operator attention. Has severity (critical, major, minor) and state (raised, updated, cleared). Differs from a raw event.
Alarm Correlation
FMSProcess of grouping related alarms to identify a single root cause. Reduces alarm storms by 90-95% in real networks.
Alarm Storm
FMSThousands of alarms generated from a single fault when correlation is poor. Overwhelms NOC operators and hides the root cause.
API-First Architecture
Modern OSSArchitecture approach where systems are designed around reusable APIs instead of tightly coupled integrations. Foundation of TM Forum ODA and modern OSS/BSS systems.
B
Batch Processing
Data processing at scheduled intervals (daily, hourly, 15-min). Used for PM counters, billing files, and historical reporting. Contrast with streaming.
BSS (Business Support Systems)
BusinessSystems that manage customers, products, orders, billing, and revenue. CRM, order management, rating, and invoicing. Integrates with OSS via TMF APIs.
C
Canonical Model
ArchitectureInternal, vendor-neutral data representation that normalizes information from multiple sources. Decouples OSS applications from vendor-specific formats.
CI/CD (Continuous Integration / Continuous Delivery)
Cloud-NativeAutomated software delivery pipeline: code commit → build → test → deploy → validate. Enables frequent OSS feature updates.
Closed-Loop Automation
OrchestrationObserve → Analyse → Decide → Act → Verify cycle without human intervention. Enables self-healing networks.
Cloud-Native OSS
Modern OSSOSS built using microservices, containers (Docker), Kubernetes orchestration, and CI/CD. Enables scalability, resilience, and faster feature delivery.
CNF (Cloud-Native Network Function)
Cloud-NativeContainerized network function running on Kubernetes instead of traditional VNFs on virtual machines.
Configuration Management
FCAPSFCAPS area managing device configurations, software versions, compliance, and resource discovery.
Correlation
FMSGrouping related events and alarms to identify root cause and reduce noise.
CRM (Customer Relationship Management)
BSSBSS system managing customer data, interactions, sales, and support. Integrates with OSS for service status and fault notifications.
D
Day-0 / Day-1 / Day-2 Operations
OrchestrationDay-0: Planning and onboarding. Day-1: Initial provisioning and activation. Day-2: Ongoing operations (scaling, healing, optimization).
Digital Twin
Modern OSSVirtual replica of a physical network, fed by streaming telemetry. Used for simulation, what-if analysis, and predictive maintenance.
Docker
Cloud-NativeContainer platform that packages OSS services and dependencies into lightweight, portable containers.
E
East-West Interface
ArchitecturePeer-to-peer communication between OSS domains, orchestration platforms, and domain controllers at the same architectural level.
EMS (Element Management System)
Network MgmtVendor-focused management platform for a network technology family. Handles element-level configuration, software upgrades, telemetry, and fault collection.
eTOM (Enhanced Telecom Operations Map)
TM ForumTM Forum business process framework. Organizes telecom operations into Fulfilment, Assurance, and Billing (FAB) verticals.
ETSI NFV MANO
StandardsManagement and Orchestration framework for NFV – orchestrating VNFs and CNFs across NFV infrastructure.
Event
FMSRaw occurrence or state change in the network. Massive volume. Not all events become alarms – only actionable ones.
F
FAB (Fulfilment, Assurance, Billing)
eTOMThe three vertical process areas in eTOM: Fulfilment (order to activation), Assurance (service monitoring), Billing (usage to invoicing).
Fault
FMSUnderlying problem that caused alarms. Root cause. One fault can generate hundreds of alarms.
FCAPS
FrameworkISO standard framework for network management: Fault, Configuration, Accounting, Performance, Security.
FMS (Fault Management System)
OSSOSS component that detects failures, correlates alarms, suppresses noise, creates tickets, and tracks resolution.
G
GitOps
Cloud-NativeInfrastructure and OSS configurations managed declaratively through Git repositories with automated deployment pipelines.
gNB (5G Base Station)
5GNext-generation Node B – the 5G base station. Generates alarms, performance counters, and telemetry.
gNMI (gRPC Network Management Interface)
TelemetryModern streaming telemetry protocol for configuration and real-time data collection. Uses gRPC and YANG models.
gRPC
ProtocolHigh-performance RPC framework used by gNMI for streaming telemetry and microservice communication.
I
Intent-Based Networking (IBN)
OrchestrationDeclaring business intent (what to achieve) rather than low-level configurations. Orchestration translates intent into automated actions.
Inventory Drift
InventoryWhen network changes are made without updating the inventory system. Causes provisioning failures and incorrect service impact analysis.
Inventory Reconciliation
InventoryPeriodic audit process that compares OSS inventory records against actual network state to detect and correct inventory drift.
IRP (Integration Reference Point)
3GPP SA5Standardized interfaces between network elements, EMS, and OSS for FM, PM, and CM defined by 3GPP SA5.
K
Kafka
StreamingDistributed event streaming platform used for real-time telemetry, alarm distribution, and event-driven OSS architectures.
KPI (Key Performance Indicator)
PMMeasurable value indicating network/service performance: throughput, latency, availability, PRB utilization.
Kubernetes (K8s)
Cloud-NativeContainer orchestration platform that automates deployment, scaling, and management of containerized OSS microservices.
M
Mediation
IntegrationLayer that normalizes, enriches, filters, and routes data between network systems and OSS/BSS applications. Critical for multi-vendor environments.
Microservices
Cloud-NativeSmall, independent, deployable services that form an OSS application. Each service has its own API and data store.
MTBF (Mean Time Between Failures)
SLASLA metric measuring average time between service outages. Higher is better.
MTTR (Mean Time To Repair)
SLASLA metric measuring average time to restore service after failure. Lower is better.
N
Netconf
ProtocolNetwork configuration protocol using XML/YANG. Used for device configuration management.
Network Slice
5GEnd-to-end logical network with specific SLA characteristics (low latency, high bandwidth) created for enterprise customers or use cases.
NMS (Network Management System)
Network MgmtCentralized system providing end-to-end network visibility across domains and vendors. Aggregates alarms, topology, and performance.
NOC (Network Operations Center)
OperationsCentralized operations team responsible for monitoring network health, alarms, SLA compliance, outages, and operational incidents.
Normalization
IntegrationTransforming vendor-specific alarms, telemetry, and inventory data into standardized OSS formats and canonical models.
Northbound Interface
ArchitectureOSS to higher-level systems (BSS, analytics, portals). OSS exposes services upward toward BSS, analytics, and customer portals. Protocols: REST, TMF APIs, Kafka, event buses.
NRM (Network Resource Model)
3GPP SA5Standardized information models for 5G network functions (gNB, UPF, AMF, SMF). Used by OSS for inventory and configuration.
O
Observability
Cloud-NativeThree pillars: metrics, logs, and traces. Monitoring tells operators when something is wrong. Observability helps explain why.
OCS (Online Charging System)
BSSReal-time charging system in BSS for prepaid services, quota management, and balance updates.
ODA (Open Digital Architecture)
TM ForumTM Forum's cloud-native, API-first, event-driven architecture blueprint for OSS/BSS modernization.
OFCS (Offline Charging System)
BSSPost-paid charging system in BSS for batch processing of usage records.
ONAP (Open Network Automation Platform)
OrchestrationOpen-source orchestration platform for end-to-end service orchestration, policy control, analytics, and closed-loop automation.
OpenConfig
TelemetryVendor-neutral YANG models for network device configuration and telemetry. Standardizes multi-vendor management.
Orchestration
OSSCoordinating multiple automated tasks across domains to achieve a business outcome. Provisioning a 5G slice across RAN, transport, and core.
O-RAN (Open RAN)
StandardsOpen Radio Access Network architecture. Includes SMO (Service Management and Orchestration) and RIC (RAN Intelligent Controller).
OSS (Operational Support Systems)
CoreSystems that monitor, manage, automate, and operate telecom networks. Includes fault, performance, inventory, provisioning, and orchestration.
P
Party
SIDSID entity representing individuals or organizations. Includes customers, partners, employees.
Performance Management (PM)
FCAPSMeasures and reports network KPIs: throughput, latency, packet loss, PRB utilization. Enables SLA monitoring and capacity planning.
PM (Performance Management)
OSSOSS component that collects and analyzes network performance metrics for SLA tracking and capacity planning.
PRB (Physical Resource Block)
5GBasic unit of radio spectrum in 4G/5G. PRB utilisation indicates radio capacity consumption in a cell.
Proactive Assurance
AssuranceDetecting issues before customer impact using predictive analytics, synthetic monitoring, and anomaly detection.
Product
SIDSID entity representing commercial offerings, catalog items, and product specifications.
Provisioning
OSSProcess of configuring network devices and resources to deliver customer services. Triggered by BSS orders and executed by OSS orchestration.
Q
QoE (Quality of Experience)
AssuranceCustomer-perceived service quality. Good SLA metrics do not guarantee good QoE.
R
RCA (Root Cause Analysis)
FMSProcess of identifying the underlying fault that generated alarms. Essential for effective resolution.
Resource
SIDSID entity representing physical and virtual network assets: routers, ports, IP addresses, antennas, licenses.
Resource Inventory
OSSTMF639 – standard API for managing physical and virtual network resources. Single source of truth for what exists in the network.
REST API
IntegrationArchitectural style for APIs. TMF Open APIs are REST-based and JSON-driven.
Root Cause Alarm
FMSPrimary alarm representing the underlying fault. Correlated alarms are linked to this root cause via the correlatedAlarms field.
RRC (Radio Resource Control)
4G/5GProtocol managing connection between phone and cell tower. RRC failures and drops are common alarms.
S
Security Management
FCAPSFCAPS area covering access control (RBAC), authentication, audit logging, encryption, and compliance.
Service
SIDSID entity representing logical services: VPN, VoLTE, broadband. Maps customer-facing products to underlying resources.
Service Assurance
OSSCustomer-centric monitoring focusing on SLA compliance, customer impact analysis, and proactive issue detection.
Service Fulfilment
eTOMeTOM vertical covering order management, provisioning, activation, and service delivery to customers.
Service Inventory
OSSTMF638 – standard API for managing service records and service state. Tracks relationships between services and resources.
Service Mesh (Istio, Linkerd)
Cloud-NativeManages microservice communication – provides observability, traffic control, security, and resilience.
SID (Shared Information/Data Model)
TM ForumTM Forum standard data dictionary. Core domains: Party, Product, Service, Resource. Enables semantic interoperability.
SLA (Service Level Agreement)
BSS/OSSContractual service quality commitments: availability, latency, packet loss, MTTR. Failures trigger financial credits.
SNMP (Simple Network Management Protocol)
ProtocolLegacy telemetry protocol. Uses polling (request-response) and traps (alarms). Still widely deployed, being supplemented by gNMI.
Southbound Interface
ArchitectureOSS communicates downward toward network devices and EMS. Protocols: SNMP, Netconf, gNMI, CLI, RESTCONF.
Streaming Telemetry
TelemetryPush model where devices continuously send data to OSS without waiting for requests (gNMI, gRPC, Kafka).
Synthetic Monitoring
AssuranceProactive testing using synthetic probes or simulated transactions to measure service quality and detect issues before customers are impacted.
T
TCA (Threshold Crossing Alert)
PMAlert triggered when a performance metric exceeds a configured threshold (e.g., PRB utilisation > 85%).
Telemetry
Data CollectionOperational data collected from network devices and systems including metrics, counters, logs, events, and traces.
Ticketing (Trouble Ticket)
NOCRecord created by OSS to track fault resolution, escalation, and SLA timers. Integrated with NOC workflows and field dispatch systems.
TMF Open APIs
TM ForumStandardized REST APIs for OSS/BSS integration. Examples: TMF639 (Resource Inventory), TMF638 (Service Inventory), TMF642 (Alarm Management), TMF641 (Service Order).
TM Forum
StandardsIndustry association developing OSS/BSS standards: eTOM (process), SID (data), Open APIs (integration), ODA (architecture).
TMF639 (Resource Inventory Management API)
Open APIQuery and manage physical and virtual network resources.
TMF638 (Service Inventory Management API)
Open APICreate, retrieve, and manage service records.
TMF642 (Alarm Management API)
Open APIStandard REST API for exposing and managing alarms.
TMF641 (Service Ordering API)
Open APIBSS to OSS order handoff for service provisioning.
Topology
ArchitectureRepresentation of network connectivity and relationships between devices, links, services, and dependencies. Used for impact analysis and root-cause correlation.
U
UPF (User Plane Function)
5G Core5G core network function handling user data traffic forwarding, QoS, and usage reporting.
V
VNF (Virtualized Network Function)
NFVNetwork function (router, firewall, UPF) running on virtual machines instead of physical hardware.
Y
YANG (Yet Another Next Generation)
Data ModelingData modelling language defining telemetry data structures. Used by gNMI and NETCONF. OpenConfig YANG standardizes multi-vendor telemetry.
How to Use This Glossary
- Use the alphabetical navigation to jump to specific letters.
- Use the search bar to quickly find terms by keyword.
- Terms are categorized with badges (FCAPS, TM Forum, Cloud-Native, etc.) for easy filtering.
- Click "Learn More" links to explore detailed topic pages.
- Refer back to this glossary while studying other topics or preparing for interviews.
- Bookmark this page for quick reference during OSS integration projects.