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 usage tracking, operational accounting, capacity planning, and resource utilization reporting.
AIOps (Artificial Intelligence for IT Operations)
Modern OSSUses machine learning to analyze telemetry, detect anomalies, predict failures, and support automated or operator-assisted remediation workflows.
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 probable root-cause relationships and reduce operational noise.
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. A key architectural principle in TM Forum ODA and modern OSS/BSS integration strategies.
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, commercial operations, orders, billing, charging, and revenue management.
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. Helps streamline software delivery, testing, deployment, and operational update workflows.
Closed-Loop Automation
OrchestrationObserve → Analyze → Decide → Act → Verify cycle with varying levels of automation and human oversight. Enables automated or semi-automated remediation workflows.
Cloud-Native OSS
Modern OSSOSS commonly using microservices, containers (Docker), Kubernetes orchestration, CI/CD pipelines, API-first integration, and DevOps practices. Supports scalable deployment models, operational resilience, and modular software evolution.
CNF (Cloud-Native Network Function)
Cloud-NativeContainerized network function running on Kubernetes instead of traditional VNFs on virtual machines. Part of cloud-native telecom evolution.
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. A key function of modern OSS assurance platforms.
CRM (Customer Relationship Management)
BSSBSS system managing customer data, interactions, sales, and support. Integrates with OSS for service status and fault notifications.
D
Data Lake
Data & AnalyticsCentralized repository storing raw telecom telemetry (gNMI streams, PM counters, syslogs, alarms) in native format. Uses three-zone architecture: Raw (original data), Processed (normalized), Curated (business-ready). Enables ML training, root cause analysis, and long-term audits.
Day-0 / Day-1 / Day-2 Operations
OrchestrationDay-0: Planning and onboarding of services, templates, and infrastructure before deployment. Day-1: Initial provisioning, activation, and service deployment across domains. Day-2: Ongoing operations including scaling, healing, optimization, upgrades, and assurance.
Delta Lake
Data & AnalyticsOpen-source storage layer that brings ACID transactions to data lakes. Enables reliable upserts, deletes, and time travel (accessing historical data versions). Commonly used for Curated Zone in telecom data lakes.
Digital Twin
Modern OSSVirtual replica of a physical network, fed by operational telemetry, inventory, topology, and network-state data. Used for simulation, what-if analysis, and predictive maintenance.
Docker
Cloud-NativeContainer platform that packages OSS services and dependencies into lightweight, portable containers. Ensures consistency across environments.
E
East-West Interface
ArchitecturePeer-to-peer communication between OSS domains, orchestration platforms, and domain controllers at the same or adjacent architectural layers. Essential for cross-domain orchestration.
EMS (Element Management System)
Network MgmtVendor-focused management platform for a network technology family. Handles element-level configuration, software upgrades, telemetry, and fault collection. Examples: Nokia NetAct, Ericsson ENM.
eTOM (Enhanced Telecom Operations Map)
TM ForumTM Forum business process framework. Organizes telecom operations into Fulfillment, Assurance, and Billing (FAB) verticals with supporting cross-functional processes.
ETSI NFV MANO
StandardsManagement and Orchestration framework for NFV – orchestrating virtualized network functions and evolving cloud-native deployment environments across NFV infrastructure.
Event
FMSRaw occurrence or state change in the network. Large telecom OSS environments may process extremely high operational event volumes continuously. Not all events become alarms – only actionable ones that require operational attention.
F
FAB (Fulfillment, Assurance, Billing)
eTOMThe three vertical process areas in eTOM: Fulfillment (order to activation), Assurance (service monitoring), Billing (usage to invoicing).
Fault
FMSUnderlying problem that caused alarms. Root cause. One fault may generate many alarms. Fault identification requires correlation across domains.
FCAPS
FrameworkISO standard framework for network management: Fault, Configuration, Accounting, Performance, Security. ISO/IEC 10040 defines the functional areas of network management.
FMS (Fault Management System)
OSSOSS component that detects failures, correlates alarms, suppresses noise, creates tickets, and tracks resolution. Goal is to minimize MTTR/T2R.
G
GitOps
Cloud-NativeInfrastructure and OSS configurations managed declaratively through Git repositories and automated deployment pipelines. Improves auditability, version control, and deployment consistency.
gNB (5G Base Station)
5GNext-generation Node B – the 5G base station. Generates alarms, performance counters, and streaming telemetry via modern telemetry and management interfaces. Managed via SA5 NRM models.
gNMI (gRPC Network Management Interface)
TelemetryModern streaming telemetry protocol widely adopted for cloud-native and 5G networks. Uses gRPC and YANG models for configuration and real-time data collection.
gRPC
ProtocolHigh-performance RPC framework used by gNMI for streaming telemetry and microservice communication.
H
HLR (Home Location Register)
4GCentral database in 4G core networks storing subscriber information, service profiles, and location data. Managed via OSS provisioning and activation workflows.
HSS (Home Subscriber Server)
4G/5GEvolution of HLR in 4G/5G core networks. Manages subscriber authentication, authorization, and service profiles.
I
Intent-Based Networking (IBN)
OrchestrationAdvanced orchestration approach where operators declare business intent (what to achieve) rather than low-level configurations. Orchestration translates intent into policies and automated actions.
Inventory Drift
InventoryWhen network changes are made without updating the inventory system (e.g., CLI changes). Can lead to provisioning inconsistencies, operational errors, and incorrect service-impact analysis. Managed through reconciliation.
Inventory Reconciliation
InventoryPeriodic audit process that compares OSS inventory records against actual network state to detect and correct inventory drift. Essential for provisioning automation accuracy.
IRP (Integration Reference Point)
3GPP SA5Standardized interfaces between network elements, EMS, and OSS for FM, PM, and CM defined by 3GPP SA5. Enables multi-vendor OSS integration. Not mandatory in modern OSS.
J
Jitter
PMVariation in packet delay over time. High jitter affects real-time services like voice and video. Monitored by OSS performance management systems.
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, call drop rate.
Kubernetes (K8s)
Cloud-NativeContainer orchestration platform that automates deployment, scaling, workload recovery, and service management for containerized OSS microservices.
L
L2C (Lead to Cash)
BusinessTime from customer order to first bill. Service Fulfillment time. OSS plays a critical role in L2C through provisioning and activation.
Latency
PMTime for a packet to travel from source to destination. Critical SLA metric for real-time services.
M
Mediation
IntegrationLayer that normalizes, enriches, filters, and routes data between network systems and OSS/BSS applications. Critical for multi-vendor environments and canonical model implementation.
Microservices
Cloud-NativeSmall, independent, deployable services that form an OSS application. Each service has its own API and data store, enabling loose coupling and independent scaling.
MTBF (Mean Time Between Failures)
SLASLA metric measuring average time between service outages. Higher is better. Complementary to MTTR.
MTTR (Mean Time To Repair/Restore)
SLASLA metric measuring average time to restore service after failure. Lower is better. Critical for T2R (Trouble to Resolve).
N
Netconf
ProtocolRPC-based management protocol using XML/YANG. Used for configuration and operational management of network devices.
Network Slice
5GEnd-to-end logical network with specific SLA characteristics (low latency, high bandwidth) created for enterprise customers or use cases. Orchestrated across RAN, transport, and core domains.
NMS (Network Management System)
Network MgmtCentralized system providing end-to-end network visibility across domains and vendors. Aggregates alarms, topology, and performance from multiple EMS systems.
NOC (Network Operations Center)
OperationsCentralized operations team responsible for monitoring network health, alarms, SLA compliance, outages, and operational incidents. Primary users of NMS systems.
Normalization
IntegrationTransforming vendor-specific alarms, telemetry, and inventory data into standardized OSS formats and canonical models. Includes semantic normalization (mapping same meaning across vendor terms).
Northbound Interface
ArchitectureOSS exposes services upward toward BSS platforms, analytics systems, integration layers, and downstream applications. Protocols: REST, TMF Open APIs, Kafka, event buses.
NRM (Network Resource Model)
3GPP SA5Standardized information models for 5G network functions (gNB, UPF, AMF, SMF). Defines what attributes each network function has. Used by OSS for inventory and configuration across vendors.
O
Observability
Cloud-NativeThree pillars: metrics (Prometheus), logs (Elasticsearch/Loki), and traces (Jaeger). Helps diagnose issues across distributed microservices in cloud-native OSS.
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. Builds on eTOM, SID, and Open APIs.
OFCS (Offline Charging System)
BSSPost-paid charging system in BSS for batch processing of usage records and mediation files.
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 across routers, switches, and optical transport.
Orchestration
OSSCoordinating multiple automated tasks across domains to achieve a business outcome. Example: provisioning a 5G slice across RAN, transport, and core with end-to-end validation.
O-RAN (Open RAN)
StandardsOpen Radio Access Network architecture. Includes SMO (Service Management and Orchestration) and RIC (RAN Intelligent Controller) with A1, E2, O1, O2 interfaces.
OSS (Operational Support Systems)
CoreSystems that monitor, manage, automate, and operate telecom networks. Includes fault, performance, inventory, provisioning, and orchestration. Responsible for Service Fulfillment (L2C) and Service Assurance (T2R).
P
Packet Loss
PMPercentage of packets lost during transmission. High packet loss indicates network congestion or quality issues.
Parquet
Data & AnalyticsColumnar storage file format optimized for analytics. Compresses data efficiently and supports high-performance queries. Commonly used for storing processed and curated data in telecom data lakes.
Party
SIDSID entity representing individuals or organizations. Includes customers, partners, employees, and other stakeholders in telecom operations.
Performance Management (PM)
FCAPSFCAPS area focused on collecting network metrics, analyzing trends, and generating threshold crossing alerts for capacity planning and SLA monitoring.
Policy Engine
OrchestrationDefines rules controlling automation decisions, approvals, scaling limits, and remediation actions. Translates business intent into technical actions in orchestration platforms.
Post-Provisioning Validation
OrchestrationConfirms service reachability, KPI baselines, and policy consistency before activation completion. Prevents sending activation confirmation for services that are not actually operational.
PRB (Physical Resource Block)
5GBasic unit of radio spectrum in 4G/5G. PRB utilisation indicates radio capacity consumption in a cell. Key RAN KPI monitored by OSS.
Proactive Assurance
AssuranceDetecting issues before customer impact using predictive analytics, synthetic monitoring, anomaly detection, and AI/ML workflows.
Product
SIDSID entity representing commercial offerings, catalog items, product specifications, and pricing models in BSS product catalog.
Provisioning
OSSProcess of configuring network devices and resources to deliver customer services. Translates customer orders into technical service configurations. 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. Measured through MOS (Mean Opinion Score), surveys, and application-specific metrics.
QoS (Quality of Service)
NetworkNetwork-level performance guarantees including bandwidth, latency, jitter, and packet loss. Managed through QoS policies enforced by OSS configuration and orchestration systems.
R
RAN (Radio Access Network)
NetworkThe radio access network including gNBs (5G) and eNBs (4G). Managed by OSS for configuration, performance, and fault management.
RCA (Root Cause Analysis)
FMSProcess of identifying the underlying fault that generated alarms. Essential for effective resolution and reducing mean time to repair (MTTR).
Resource
SIDSID entity representing physical and virtual network assets: routers, gNBs, ports, IP addresses, antennas, licenses.
Resource Inventory
OSSTMF639 – standard API for managing physical and virtual network resources. Acts as a critical operational reference point for what exists in the network.
REST API
IntegrationArchitectural style for APIs. TMF Open APIs are REST-based and JSON-driven. Used for northbound OSS-BSS integration.
RRC (Radio Resource Control)
4G/5GProtocol managing connection between phone and cell tower. RRC failures and drops are common alarms in RAN fault management.
S
Security Management
FCAPSFCAPS area covering access control (RBAC), authentication, audit logging of user actions, encryption, and compliance with regulatory requirements (GDPR, SOX).
Service
SIDSID entity representing logical services: VPN, VoLTE, broadband, 5G slices. Maps customer-facing products to underlying resources for assurance and billing.
Service Assurance
OSSCustomer-centric monitoring focusing on SLA compliance, customer impact analysis, proactive issue detection, and closed-loop remediation.
Service Fulfillment
eTOMeTOM vertical covering order management, provisioning, activation, and service delivery to customers. L2C (Lead to Cash) process.
Service Inventory
OSSTMF638 – standard API for managing service records and service state. Tracks relationships between services and resources for assurance and billing.
Service Mesh (Istio, Linkerd)
Cloud-NativeManages microservice communication – provides observability, traffic control, security, and resilience without changing service code. Common in cloud-native OSS.
SID (Shared Information/Data Model)
TM ForumTM Forum standard data dictionary. Core domains: Party, Product, Service, Resource. Enables semantic interoperability across OSS/BSS systems.
SLA (Service Level Agreement)
BSS/OSSContractual service quality commitments: availability, latency, packet loss, MTTR. Failures may trigger financial credits based on SLA terms.
SMO (Service Management and Orchestration)
O-RANThe management and orchestration function in O-RAN architecture. SMO manages O-RAN components (O-CU, O-DU, RICs, O-Cloud) and exposes northbound APIs to OSS/BSS.
SNMP (Simple Network Management Protocol)
ProtocolLegacy telemetry protocol. Uses polling (request-response) and traps (alarms). Still widely deployed, being supplemented by gNMI for streaming telemetry.
Southbound Interface
ArchitectureOSS communicates downward toward network devices, EMS platforms, domain controllers, and network elements. Protocols: SNMP, Netconf, gNMI, CLI, RESTCONF.
Streaming Telemetry
TelemetryPush model where devices continuously send data to OSS using continuous or subscription-based telemetry delivery models (gNMI, gRPC, Kafka). Enables near-real-time monitoring with greatly reduced sampling gaps.
Synthetic Monitoring
AssuranceProactive testing using synthetic probes or simulated transactions to measure service quality and detect issues before customers are impacted.
T
T2R (Trouble to Resolve)
SLATime from fault detection to resolution. Critical SLA metric. Equivalent to MTTR (Mean Time To Repair/Restore).
TCA (Threshold Crossing Alert)
PMAlert triggered when a performance metric exceeds a configured threshold (e.g., PRB utilisation > 85%). Can be warnings (soft) or actionable alarms (hard).
Telemetry
Data CollectionOperational data collected from network devices and systems including metrics, counters, logs, events, and traces. Foundation for monitoring and assurance.
Ticketing (Trouble Ticket)
NOCRecord created by OSS to track fault resolution, escalation, and SLA timers. Two types: Customer TT (user-reported) and Network TT (system-generated).
TMF Open APIs
TM ForumStandardized REST APIs for OSS/BSS integration. Examples: TMF639 (Resource Inventory), TMF638 (Service Inventory), TMF642 (Alarm Management), TMF641 (Service Order), TMF628 (Performance Management), TMF649 (Performance Thresholding). Modern implementations commonly use lowercase severity values such as critical, major, minor, warning, and cleared.
TMF628 (Performance Management API)
TM ForumTM Forum Open API for Performance Management. Exposes network KPIs (latency, throughput, availability) to BSS for SLA monitoring, customer dashboards, and capacity planning.
TMF649 (Performance Thresholding API)
TM ForumTM Forum Open API for Performance Threshold Management. Used to create and manage performance thresholds and raise threshold crossing alerts (TCAs). Works with TMF628.
TM Forum
StandardsIndustry association developing OSS/BSS standards: eTOM (process), SID (data), Open APIs (integration), ODA (cloud-native architecture).
TMF639 (Resource Inventory Management API)
Open APITM Forum Open API for querying and managing physical and virtual network resources.
TMF638 (Service Inventory Management API)
Open APITM Forum Open API for creating, retrieving, and managing service records and service state.
TMF642 (Alarm Management API)
Open APITM Forum Open API for exposing and managing alarms. Modern implementations commonly use lowercase severity values.
TMF641 (Service Ordering API)
Open APITM Forum Open API for BSS to OSS order handoff for service provisioning and activation.
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 enforcement, and usage reporting for billing.
V
VNF (Virtualized Network Function)
NFVNetwork function (router, firewall, UPF) running on virtual machines instead of physical hardware. Managed by NFV MANO frameworks.
W
Workflow Engine
OSSMiddleware that orchestrates tasks across OMS, inventory, provisioning, and activation systems. Reduces point-to-point interfaces and provides centralized control and monitoring.
X
xApp
O-RANApplication running on Near-RT RIC (RAN Intelligent Controller) for near-real-time RAN optimization. Managed via O-RAN SMO East-West interfaces.
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.
Z
Zero-Touch Provisioning (ZTP)
AutomationAutomated provisioning of network devices without manual intervention. Devices auto-configure when connected to the network. Enabled by OSS orchestration and inventory systems.
📌 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, Data & Analytics, 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.