Information Object Class

Description

Information Object Class (IOC) is a fundamental construct in 3GPP's network management framework, particularly within the Fault, Configuration, Accounting, Performance, and Security (FCAPS) model. An IOC serves as a template or schema that defines the structure and semantics of managed objects, which are software abstractions representing physical or logical network resources, such as network elements, functions, or services. Each IOC specifies a set of attributes (properties), actions (operations that can be invoked), notifications (events emitted), and behavior (rules governing the object). Managed objects are instances of IOCs, populated with specific values, and they reside in a Management Information Base (MIB) accessible via management interfaces like the Itf-N or OAM interfaces.

The architecture of IOC-based management involves hierarchical class inheritance, where IOCs can be derived from parent classes, inheriting and extending their definitions. This object-oriented approach promotes reusability and consistency. Key components include the IOC definition in specification documents (e.g., 3GPP TS 28.xxx and 32.xxx series), the supporting management protocols (e.g., SNMP, CORBA, or RESTful APIs in newer releases), and the agent-manager paradigm where managed objects are implemented by network elements and accessed by management systems. IOCs cover a wide range of entities, from physical equipment like base stations to logical functions like network slices or QoS flows.

In operation, IOCs enable standardized management operations such as monitoring performance counters, configuring parameters, receiving fault alarms, and auditing usage. For example, an IOC for a gNB would define attributes for cell ID, transmit power, and connection statistics, actions for reset or software update, and notifications for link failure. By adhering to IOC definitions, vendors ensure interoperability, allowing network operators to manage multi-vendor deployments seamlessly. IOCs are central to 3GPP's Self-Organizing Networks (SON), network slicing management, and 5G service assurance, providing a unified information model for the entire network lifecycle.

Purpose & Motivation

IOC was developed to address the challenges of managing complex, multi-vendor telecommunications networks. Prior to standardization, each vendor used proprietary information models, making integration and unified management difficult and costly. The IOC concept, rooted in ITU-T's TMN and OSI systems management, provides a common language for describing network resources, enabling interoperability and reducing operational expenses.

The primary problems solved include fragmentation in management data representation and lack of consistency across different network domains. IOCs facilitate automated management, essential for scaling 5G networks with massive numbers of devices and dynamic services. They support FCAPS functions by ensuring that all managed entities expose a consistent set of attributes and behaviors. Historically, as networks evolved from 2G to 5G, the scope of IOCs expanded from basic network element management to encompass virtualized network functions, end-to-end service management, and network slicing. This evolution was motivated by the need for agile, software-driven networks where management must be as flexible and scalable as the services themselves.

Key Features

• Object-oriented template for managed objects with inheritance
• Standardized attributes, actions, and notifications for network resources
• Support for multi-vendor interoperability in OAM
• Integration with management protocols (e.g., SNMP, RESTCONF)
• Foundation for SON automation and policy-based management
• Comprehensive coverage from physical to virtualized network functions

Evolution Across Releases

Defining Specifications