OMG

Object Management Group

Management →
Introduced in Rel-8

OMG is a consortium whose standards, like the Unified Modeling Language, are referenced by 3GPP for defining architecture and data formats in telecom management system design.

Category
Management
Introduced
Rel-8
Where
Management
Specifications
95 specs
OMG Description Purpose Related Classification Detected Changes Specifications

Description

Within the context of 3GPP specifications, the term "OMG" refers to the external standards consortium, the Object Management Group. 3GPP does not define the OMG but extensively references its technical standards, most notably the Unified Modeling Language (UML), as a normative part of its own specification methodology. UML is used as the primary modeling language for describing the architecture, information models, and procedures of 3GPP systems, especially in the domain of network management (e.g., 32-series specifications).

The use of OMG standards, primarily UML, provides a formal, graphical, and object-oriented way to specify complex systems. In 3GPP, UML class diagrams are used to define the managed objects, their attributes, and relationships within the Information Model for network management. Sequence diagrams are used to specify the message flows and interactions between different network functions or between management systems and network elements. This formal modeling approach reduces ambiguity, improves the precision of specifications, and aids in the development of consistent software implementations and test suites.

The extensive list of 3GPP specs referencing OMG (over 100 in the provided data, mostly from the 28.x, 32.x, and 52.x series) underscores its critical role. These specifications cover areas like Management and Orchestration (MANO) for NFV, Performance Management (PM), Fault Management (FM), Configuration Management (CM), and the overall architecture of the Telecommunication Management Network (TMN) and its evolution. By leveraging OMG's UML, 3GPP achieves a level of design rigor and interoperability that is essential for multi-vendor global telecommunications ecosystems.

Purpose & Motivation

3GPP adopted OMG's UML to solve a fundamental problem in large-scale, multi-party technical standardization: the ambiguity and inconsistency of natural language descriptions. Prior to the widespread use of formal modeling, system specifications were described in text and informal diagrams, which were prone to misinterpretation by different implementers, leading to interoperability issues.

The adoption of OMG's UML, starting prominently in the 2000s (around 3GPP Release 5/6 for management specs), provided a standardized, vendor-neutral, and precise visual language. This allowed 3GPP working groups to define complex management interfaces, data models, and system behaviors in an unambiguous way. The object-oriented nature of UML was a good fit for modeling telecom networks composed of managed objects like network elements, connections, and services.

This move was motivated by the increasing complexity of 3G and later 4G/5G networks, the push for automated management and orchestration, and the critical need for flawless interoperability between equipment from hundreds of suppliers. Using an internationally recognized standard like UML from OMG also facilitated the alignment of 3GPP work with ITU-T and other bodies that also use modeling languages, improving consistency across the broader telecom standards landscape.

Classification

Part ofTMN
Specific typesUMLSAS

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 5 changes

In Release 15, the OMG function was updated to support new management capabilities, including Self-Organizing Network (SON) functionalities for Active Antenna System (AAS) deployment management and the management of ng-eNBs. The updates also extended support for EN-DC and 4G/5G interworking within the EPC definitions. Furthermore, the State management data definition Solution Set was enhanced to support JSON.

  • Add SON for AAS management attributes TS 28.629CR0014
  • Adding attribute of IOC EUtranGenericCell to support SON for AAS deployment management TS 28.659CR0021
  • Update E-UTRAN SS definitions to support ng-eNB management TS 28.659CR0025
  • Update EPC SS definitions to support management of EN-DC and 4G/5G interworking TS 28.709CR0010
  • Update State management data definition Solution Set to support JSON TS 28.626CR0007
Rel-16 3 changes

In Release 16, the OMG function was updated to introduce an Information Object Class (IOC) for managing non-collocated LTE-WLAN Aggregation (LWA) configurations. It also enhanced the existing ENBFunction definitions to support the management of LTE WLAN Radio Level Integration with IPsec Tunnel (LWIP). Furthermore, the specification removed an outdated administrative reference to a temporary joint working group.

  • Add IOC for supporting management of non-collocated LWA TS 28.659CR0026
  • Enhance ENBFunction for LWIP management TS 28.659CR0033
  • Removal of reference to a temporary joint working group TS 32.156CR0023
Rel-18 2 changes

In Release 18, the OMG (Object Management Group) function was updated to include new NRM solution set definitions specifically for the management of IOT-NTN (Internet of Things over Non-Terrestrial Networks). This release also addressed a gap by adding a missing definition for the object tree structure within the management framework. These enhancements provide a more complete specification for managing these advanced network capabilities.

  • Add NRM solution set definitions for IOT-NTN management TS 28.659CR0041
  • Rel-18 CR 32.156 Add missing definition of object tree TS 32.156CR0092

Explore further

Broader topics and technologies where OMG plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 28.303 vj00 LSA Controller IRP Solution Set Definitions Rel-19
TS 28.606 vc10 CN and non-3GPP interworking NRM IRP Solution Sets Rel-12
TS 28.616 vj00 EPC and non-3GPP access NRM IRP SS definitions Rel-19
TS 28.625 vj00 State Management Data Definition IRP Information Service Rel-19
TS 28.626 vj00 State Management Data Definition IRP Solution Set Rel-19
TS 28.629 vj00 SON Policy NRM IRP Solution Set Definitions Rel-19
TS 28.653 vj00 UTRAN NRM IRP Solution Set Definition Rel-19
TS 28.656 vj00 GERAN NRM IRP Solution Set Definitions Rel-19
TS 28.659 vj00 E-UTRAN NRM IRP Solution Set Definitions Rel-19
TS 28.663 vj00 Generic RAN NRM IRP Solution Set Definitions Rel-19
TS 28.673 vj00 HNS NRM IRP Solution Set Definitions Rel-19
TS 28.676 vj00 HeNS NRM IRP Solution Set Definitions Rel-19
TS 28.701 vj00 Core Network NRM IRP Requirements Rel-19
TS 28.703 vj00 Core Network NRM IRP Solution Set Definitions Rel-19
TS 28.706 vj00 IMS NRM IRP Solution Set definitions Rel-19
TS 28.709 vj00 EPC NRM IRP Solution Set Definitions Rel-19
TS 28.733 vj00 TN NRM IRP Solution Set Definitions Rel-19
TS 28.736 vj00 STN Interface NRM IRP Solution Set Definitions Rel-19
TS 28.820 vc00 Umbrella Operation Model for Fixed Mobile Convergence Rel-12
TS 28.821 vd00 UML Model Repertoire for FMC Management Rel-13
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TS 32.111 vj00 Fault Management Requirements Rel-19
TS 32.150 vj00 IRP Concept and Definitions Rel-19
TS 32.151 ve00 IRP Information Service Template Specification Rel-14
TS 32.152 ve10 IRP Information Service UML Repertoire Rel-14
TS 32.153 vj00 IRP Technology-Specific Templates Specification Rel-19
TS 32.156 vk00 UML Modeling for Network Management Systems Rel-20
TS 32.157 vj00 IRP Information Service Template for Converged Management Rel-19
TS 32.301 vj00 Notification IRP Requirements Rel-19
TS 32.302 vj00 Notification IRP Information Service Rel-19
TS 32.303 v900 Notification IRP CORBA Solution Set Rel-9
TS 32.306 vj00 Configuration Management Notification IRP Solution Set Rel-19
TS 32.312 vj00 Generic IRP Management Information Service Rel-19
TS 32.313 v900 Generic IRP CORBA Solution Set Rel-9
TS 32.316 vj00 Generic IRP Management Solution Set Definitions Rel-19
TS 32.323 v900 Test Management IRP CORBA SS Rel-9
TS 32.326 vj00 Test Management IRP Solution Set Definitions Rel-19
TS 32.333 v900 Notification Log IRP CORBA Solution Set Rel-9
TS 32.336 vj00 Notification Log IRP Solution Set Definitions Rel-19
TS 32.343 v1900 File Transfer IRP CORBA Solution Set Rel-9
TS 32.346 vj00 File Transfer IRP Solution Set Definitions Rel-19
TS 32.373 v1900 IRP Security Services CORBA Solution Rel-9
TS 32.375 v1900 Security Services for IRP: File Integrity Rel-9
TS 32.376 vj00 Security services for IRP Solution Set Rel-19
TS 32.413 v900 PM IRP: CORBA Solution Set (SS) Rel-9
TS 32.416 vj00 PM IRP Solution Set Definitions Rel-19
TS 32.442 vj00 Trace Management IRP: Information Service Rel-19
TS 32.443 v910 Trace Management IRP CORBA Solution Set Rel-9
TS 32.446 vj00 Trace Management IRP Solution Set Definitions Rel-19
TS 32.523 v930 SON Policy NRM IRP CORBA Solution Set Rel-9
TS 32.526 vb70 SON Policy NRM IRP Solution Set definitions Rel-11
TS 32.600 vj00 3GPP Configuration Management Specification Rel-19
TS 32.601 vj00 Basic Configuration Management IRP Requirements Rel-19
TS 32.603 v910 Basic CM IRP CORBA Solution Set Rel-9
TS 32.606 vj00 Basic CM IRP Solution Set for CORBA/SOAP Rel-19
TS 32.607 v1910 CM IRP SOAP Solution Set Mapping Rel-9
TS 32.611 vj00 Bulk CM IRP Requirements Rel-19
TS 32.613 v1910 Bulk CM IRP CORBA Solution Set Rel-9
TS 32.616 vj00 Bulk CM IRP Solution Set Definitions Rel-19
TS 32.621 vb00 Generic Network Resources IRP Requirements Rel-11
TS 32.623 v900 Generic NRM CORBA Solution Set Rel-9
TS 32.626 vb20 Generic Network Resources IRP Solution Set Definitions Rel-11
TS 32.631 vb00 Core Network Resources IRP Requirements Rel-11
TS 32.633 v1920 Core Network Resources IRP CORBA Mapping Rel-9
TS 32.636 vb00 CM Core Network Resources IRP Solution Set Rel-11
TS 32.643 v930 UTRAN Network Resources IRP: CORBA Solution Set Rel-9
TS 32.646 vc00 UTRAN NRM IRP Solution Set Definitions Rel-12
TS 32.656 vc00 GERAN NRM IRP Solution Set Definitions Rel-12
TS 32.661 vj00 Kernel Configuration Management IRP Requirements Rel-19
TS 32.663 v1900 Kernel CM IRP CORBA Mapping Rel-9
TS 32.666 vj00 Kernel CM IRP Solution Set Definitions Rel-19
TS 32.672 vb00 State Management IRP Information Service Rel-11
TS 32.673 v900 State Management IRP CORBA Solution Set Rel-9
TS 32.676 vc00 3GPP TS 32.676: State Management IRP Solution Set Rel-12
TS 32.690 vj00 Inventory Management IRP Requirements Rel-19
TS 32.691 vb00 Inventory Management IRP Requirements Rel-11
TS 32.711 vb00 TN Interface NRM IRP Requirements Rel-11
TS 32.713 v900 TN Interface NRM IRP: CORBA Solution Set Rel-9
TS 32.716 vb00 TN NRM IRP Solution Set Definitions Rel-11
TS 32.723 v900 Repeater NRM CORBA Solution Set Rel-9
TS 32.726 vb00 Repeater NRM IRP Solution Set Definitions Rel-11
TS 32.733 v910 IMS NRM IRP CORBA Solution Set Rel-9
TS 32.736 vb00 IMS NRM IRP Solution Set Definitions Rel-11
TS 32.743 v1900 CORBA Solution Set for STN IRP Rel-9
TS 32.746 vb00 STN NRM IRP Solution Set Definitions Rel-11
TS 32.753 v920 EPC NRM IRP CORBA Solution Set Rel-9
TS 32.756 vb00 EPC NRM IRP Solution Set Definitions Rel-11
TS 32.763 v1950 E-UTRAN NRM IRP CORBA Solution Set Rel-9
TS 32.766 vb90 E-UTRAN NRM IRP Solution Set Definitions Rel-11
TS 32.773 v900 HNS NRM IRP CORBA Solution Set Rel-9
TS 32.776 vb00 HNS NRM IRP Solution Set Definitions Rel-11
TS 32.783 v1900 HeNS NRM IRP CORBA Solution Set Rel-9
TS 32.786 vb00 3GPP TS 32.786: HeNS NRM IRP Solution Set Rel-11
TS 32.796 vc00 Generic RAN NRM IRP Solution Set Definitions Rel-12
TS 32.824 v900 SOA and IRP Gap Analysis Rel-9