Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

OSS

Operations and Supervisory System

Management →

OSS is a management system for network operations that enables service providers to monitor, control, and optimize network elements and services.

Introduced
R99
Where
Management
Specifications
18 specs
Also in
Core Network, Services, Security
OSS Description Purpose What changed Neighbours Specifications

Description

The Operations and Supervisory System (OSS) is a comprehensive suite of applications and platforms that form the operational backbone of a telecommunications network. It is responsible for the management of network elements (NEs) and the services they provide, adhering to the FCAPS model (Fault, Configuration, Accounting, Performance, Security). Architecturally, OSS typically resides in the network management layer, interfacing with network elements via standardized interfaces like the Itf-N (Interface-Northbound) or using protocols such as SNMP, CORBA, or NETCONF/YANG in more modern implementations. It collects data from the network, processes it, and presents it to network operators through a management interface, enabling centralized control.

At its core, OSS functions through several key subsystems. The Fault Management system continuously monitors the network for alarms and events, performing root cause analysis and triggering corrective actions or trouble tickets. Configuration Management handles the provisioning and lifecycle management of network resources, including software updates and parameter changes. Performance Management collects and analyzes key performance indicators (KPIs) and quality of service (QoS) metrics to assess network health and capacity. Accounting Management tracks resource usage for billing and charging purposes, while Security Management enforces policies, monitors for threats, and manages access controls.

In the 3GPP ecosystem, OSS interacts with various network domains, including the Core Network (CN) and Radio Access Network (RAN). It manages entities like the Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW) in 4G, and their 5G counterparts (AMF, SMF, UPF). For the RAN, it manages NodeBs, eNodeBs, and gNBs. The OSS plays a critical role in service assurance, enabling operators to maintain service level agreements (SLAs), plan network expansions, and automate routine operational tasks, thereby reducing operational expenditure (OPEX) and minimizing downtime.

Purpose & Motivation

The OSS was created to address the growing complexity of telecommunications networks, which became unmanageable through manual, element-by-element operations. Prior to standardized OSS, operators relied on proprietary, vendor-specific management tools that led to operational silos, high integration costs, and inefficient processes. The proliferation of network technologies (2G, 3G, 4G, 5G) and the increasing demand for diverse services necessitated a unified, standardized approach to network operations.

3GPP standardized the OSS to provide a common framework for multi-vendor, multi-technology network management. This standardization solves critical problems like interoperability between management systems and network elements from different suppliers. It enables automated service provisioning, centralized fault monitoring, and holistic performance analysis across the entire network. The motivation was to reduce operational costs, improve service quality and reliability, and accelerate the deployment of new services by providing operators with the tools to efficiently manage their increasingly complex and scalable network infrastructures.

What changed in its specifications

The latest release-to-release comparison of specifications that define OSS. Each summary describes the whole specification, not only this term.

TS 23.078Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.078: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.078 →
TS 23.218Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.218: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.218 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced the foundational OSS architecture for 3GPP networks, focusing on managing the new 3G UMTS network elements. It established basic FCAPS functions and interfaces for the Circuit Switched (CS) and Packet Switched (PS) core domains and the UTRAN radio access network.

Defining Specifications

3GPP specifications that define or reference OSS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.031 vj00 Fraud Information Gathering System (FIGS) - Stage 2 Rel-19 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TS 23.845 va00 UDC Evolution Study Rel-10 read
TR 26.933 vj00 Study on Diverse Audio Capturing System Rel-19 read
TS 28.500 vj00 Management of Virtualized Network Functions Rel-19 read
TR 28.834 vi01 Technical Report Rel-18 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19 read
TS 32.816 v800 E-UTRAN and EPC Management Principles Rel-8 read
TS 32.826 va00 Study on Energy Savings Management in LTE/SAE Networks Rel-10 read
TS 32.842 vd10 Management of Virtualized 3GPP Core Networks Rel-13 read
TS 32.854 vb10 FMC Federated Network Information Model Rel-11 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TR 33.848 vi00 Technical Report on Virtualisation Security Rel-18 read