SOM

Service Operations Management

Management →
Introduced in Rel-8

SOM is a 3GPP management framework and set of standards for the operational lifecycle management of telecommunications services, providing principles and architecture for provisioning, configuring, assuring, and billing services.

Category
Management
Introduced
Rel-8
Where
Management
Specifications
1 specs
SOM Description Purpose Specifications

Description

Service Operations Management (SOM) is a comprehensive management framework defined in the 3GPP Technical Specification 32.101. It encompasses the processes, functions, and information models required for managing the operational lifecycle of services within a telecommunications environment. SOM is not a single tool but a standardized reference architecture that guides the implementation of Operations Support Systems (OSS) and Business Support Systems (BSS). It covers the full spectrum from service conception and design through to provisioning, fulfillment, assurance, billing, and eventual decommissioning.

The architecture of SOM is typically described through functional layers. At its core, it involves Service Management Functions that interact with Resource Management Functions (which manage the underlying network elements) and Business Management Functions (which handle customer relationships and billing). Key processes within SOM include Service Configuration Management (setting up service parameters), Service Problem Management (handling faults and degradations affecting a service), Service Quality Management (monitoring and reporting on service level agreements - SLAs), and Service Accounting Management (tracking service usage for billing). These processes rely on standardized information models, such as those defined using UML, to ensure data consistency and interoperability between different management systems from various vendors.

SOM works by defining a logical separation between the service layer and the network resource layer. This abstraction is crucial. A customer-facing service (e.g., '5G Enhanced Mobile Broadband with VoIP') is realized by the orchestration and configuration of multiple underlying network resources (e.g., network slices, PDU sessions, QoS flows). SOM provides the management capabilities to map service requirements to resource configurations, monitor the aggregated health and performance of the service, and take corrective actions if SLAs are violated. Its role is to enable efficient, automated, and customer-centric operations, which is essential for modern complex services like network slicing, IoT, and edge computing.

Purpose & Motivation

SOM was created to address the growing complexity and dynamic nature of telecommunications services. In early mobile networks, services were relatively simple (primarily voice and SMS), and management was often manual and siloed. As networks evolved to offer a vast array of data services, multimedia content, and customized enterprise solutions, a standardized approach to service management became imperative. The lack of standardization led to high operational costs, long time-to-market for new services, difficulty in assuring end-to-end service quality, and challenges in integrating multi-vendor OSS/BSS environments.

The initial specification in Release 8 established the foundational principles, driven by the need for a common framework following the adoption of IP Multimedia Subsystem (IMS) and the proliferation of data services. SOM provides the blueprint for automating service lifecycle operations, which is critical for scaling operations, reducing human error, and improving customer experience. It solves the problem of service-aware management by focusing on the customer service as the managed entity, rather than just individual network elements. This allows operators to efficiently manage bundled offerings, guarantee SLAs, and rapidly deploy new services, which are key competitive advantages in the telecommunications market.

Evolution Across Releases

Rel-8 Initial

SOM was initially defined in TS 32.101, establishing the fundamental principles, reference architecture, and core management processes (Fulfillment, Assurance, Billing) for telecommunications services. This release laid the groundwork for managing the complexity introduced by IMS and early mobile data services, focusing on service-aware management.

Explore further

Broader topics and technologies where SOM plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 32.101 vj00 Management principles and high-level requirements Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.