5 Modelling approach

32.106-53GPPConfiguration Management (CM)Part 5: Basic CM Integration Reference Point (IRP): Information model (including Network Resource Model (NRM)Telecommunication managementTS

This clause identifies the modelling approach adopted and used in this IRP.

As previously described, the IRP is structured in:

  1. an IRP Information Model (the subject document) that specifies the interface in a protocol neutral manner, and
  2. a number of IRP Solution Sets that provide the actual realization of the operations and notifications defined in the IRP Information Model for each protocol environment.

Figure 4 shows the structure of the Basic CM IRP (including a number of possible Solution Sets).

Basic Configuration Management IRP: Information model

IRP Information Service – operations and notifications visible over the IRP.

Network Resource Model (NRM) with MO classes (in UML)

Protocol independent

Protocol specific

SNMP Solution Set

LDAP Solution Set

WBEM Solution Set

CORBA Solution Set

CMIP Solution Set

Figure 4: Basic CM IRP Structure with example Solution Sets

As shown in Figure 4, the IRP Information Model consists of two main parts:

  1. The IRP Information Service
    This is a specification of the operations and notifications that are visible over the IRP. These operations are generic in the sense that they do not specify the Managed Objects that are retrieved/manipulated over the interface.
  2. The Network Resource Model (NRM)
    This is a protocol-independent model that specifies a number of Managed Object classes (with attributes, operations and associations), which are relevant in the context of the subject IRP. Each Solution Set shall provide an implementation of this resource model with:
  3. references to standard models that are applicable for the corresponding protocol environment, and
  4. extensions to these standard models for the parts of the NRM that are not covered.

The modelling approaches for these two aspects of the IRP are somewhat different and are described separately in the next two subclauses.

5.1 IRP Information Service modelling approach

The IRP Information Service of the subject IRP specifies a number of protocol-independent operations and notifications that are needed by an IRPManager to retrieve CM information from an IRPAgent.

The operations and notifications of the IRP Information Service are mainly based on the principles of the Common Management Information Service (CMIS) defined in ITU-T X.710 [7] and ITU-T X.721 [8] (M-GET etc.). Note however, that the Information Service of the subject IRP is focused on the operations and notifications needed for basic CM purposes and thus only covers a subset of the operations/notifications defined in ITU-T X.710 [7]/ITU-T X.721 [8].

It is expected that most Solution Sets will implement the operations and notifications by mapping them to standard operations (and possibly standard notifications) that are applicable in the corresponding protocol environment.
The CMIP Solution Set should for instance map the operations to the more generic operations defined in CMIS, an SNMP Solution Set should map the operations to applicable SNMP operations, and the CORBA Solution Set should map the operations to applicable OMG/CORBA services.

5.2 Network Resource Modelling approach

The NRM defined in the subject IRP bases its design mainly on work captured in ITU-T M.3100 [4], [5], [6]. However, as described in the Scope of the present document (clause 1): The model is highly simplified for the purpose of the NM, based on the assumption that all of the detailed CM actions, including fault correction after one or more alarms, are performed by an Element Manager which knows the vendor-specific NRM and configuration, and which is launched by the NM when necessary.

Moreover, the classes defined herein are very basic, only for the necessary support of Fault Management (FM) and Performance Management (PM), which means that they contain very few attributes – basically only for naming.

In addition, also some basic associations between some of the classes are defined.

The NRM is split into a generic and an UMTS-specific part.

Detailed mapping to the actual standard model is described in each Solution Set. It is important to note that if one selects a specific management protocol, one should also as base use existing de-facto conventions and standard resource models that are applicable to that protocol environment. Examples:

  • SNMP Solution Sets (SMI-specifications) should be consistent with existing standard SNMP MIB-modules in order to function in an SNMP environment.
  • CMIP Solution Sets (GDMO-specifications) should be based on standard models like ITU-T X.721 [8] and ITU-T M.3100 [4], [5], [6] in order to function in an OSI/TMN environment.
  • WBEM Solution Sets (MOF/XML-specifications) should be based on CIM to function in a WBEM environment.

NOTE: CORBA Solution Sets are special in the sense that no such corresponding de-facto standard models exist, and CORBA/IDL is transparent to any model. Thus, one has full freedom to choose the same model for the CORBA Solution Set to this IRP, as the IRP Information Model defined herein.

Finally, all solution sets shall of course be consistent with the IRP Information Model defined herein.