Description
A Support IOC (Information Object Class) is a concept in 3GPP management specifications, specifically defined in TS 32.102 and TS 32.150. It refers to an IOC that represents a particular capability introduced to model a management service. In the context of 3GPP management architecture, IOCs are used to define the information model for management interfaces, such as the Integration Reference Point (IRP). Support IOCs are those that are not directly related to the managed network resources but are necessary to support the management service itself. For example, in the Alarm IRP Information Service, the AlarmInformation and AlarmList IOCs are Support IOCs because they provide the structure for managing alarms, rather than representing the network elements that generate alarms.
The 3GPP management framework is based on the concept of IRPs, which define the interfaces for managing network elements. Each IRP has an Information Service that specifies the information model using IOCs. These IOCs are categorized into different types, such as Managed Object IOCs, which represent network resources, and Support IOCs, which represent auxiliary capabilities needed for the management service. Support IOCs often include data structures for lists, notifications, and other administrative information.
In TS 32.150, the Integration Reference Point (IRP) concept is further elaborated, and Support IOCs are defined as part of the IRP information model. The definition in TS 32.102 states: 'IOC that represents a particular capability, introduced to model a management service.' This definition has been stable since Rel-8, although in Rel-11 the definition was shortened to 'defined in TS 32.150 [5].' This change indicates a shift to referencing the detailed specification rather than providing an inline definition.
Support IOCs are essential for the operation of management services. They enable the modeling of complex management functions, such as alarm management, performance management, and configuration management. For instance, in alarm management, the AlarmInformation IOC holds details about an alarm, while the AlarmList IOC manages a list of active alarms. These IOCs are not managed resources themselves but are used by the management system to organize and present information.
The concept of Support IOC is part of the broader 3GPP management architecture, which aims to provide a standardized way to manage multi-vendor networks. By defining Support IOCs, 3GPP ensures that management interfaces are consistent and interoperable. The evolution of the definition from a descriptive sentence to a reference to TS 32.150 reflects the maturation of the specifications, where details are consolidated in a single document.
Overall, Support IOCs are a fundamental building block of 3GPP management information models. They allow management services to be modeled in a structured way, separating the managed resources from the supporting data structures. This separation enhances clarity and reusability across different management services.
Purpose & Motivation
Support IOCs exist to provide a structured way to model auxiliary capabilities within 3GPP management services. In the management architecture, it is necessary to represent not only the network resources being managed (e.g., base stations, cells) but also the information structures that support the management functions themselves. For example, when managing alarms, the system needs to represent individual alarms and lists of alarms. These are not network resources but are essential for the alarm management service. Support IOCs fill this gap by defining such supporting information objects.
Before the formalization of Support IOCs, management information models might have mixed resource-related and support-related information, leading to confusion and redundancy. By categorizing IOCs into Managed Object IOCs and Support IOCs, 3GPP provides a clear separation of concerns. This makes the information models easier to understand, implement, and extend. It also promotes reuse of Support IOCs across different management services.
The introduction of Support IOCs in Rel-8 coincided with the ongoing development of the 3GPP management framework, which was evolving to support more complex networks. As networks grew in size and complexity, the need for standardized management interfaces became critical. Support IOCs help ensure that management services are interoperable and can be implemented consistently by different vendors. The change in Rel-11 to reference TS 32.150 rather than providing an inline definition reflects the consolidation of management specifications and the desire to maintain a single source of truth.
What changed in its specifications
The latest release-to-release comparison of specifications that define Support IOC. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 32.102: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 32.102 →Rel-10 added definitions for Managed Object and Managed Object Class and instance, and refined Solution Set definition text.
Full comparison in TS 32.150 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Support IOC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.150 vj00 | IRP Concept and Definitions | Rel-19 read |