4 System overview

32.106-83GPPConfiguration Management (CM)Part 8: Name convention for Managed ObjectsRelease 1999Telecommunication managementTS

4.1 System context

Situations under which MO (representing network resource) names are used are as follows:

a) MO names cross various Integration Reference Points (IRPs).

EXAMPLE 1: In the context of Alarm IRP 3G TS 32.111-2 [8], IRPAgent notifies IRPManager of the alarm condition of a network resource. The DN of the MO, representing alarmed network resource, encoded as specified in the present document, is carried in the Managed Object Instance parameter of the notification.

EXAMPLE 2: In the context of Basic CM IRP 3G TS 32.106-5 [9], IRPAgent notifies IRPManager of the creation of new object. The DN of the newly created object, encoded as specified in the present document, is carried in the notification.

EXAMPLE 3: In the context of Basic CM IRP 3G TS 32.106-5 [9], IRPManager requests IRPAgent to search for a particular object by specifying the start point of the search. The DN of the base object, upon which the search begins downward hierarchically, is carried in the request.

b) Co-operating management applications need to exchange information that includes MO
(representing network resource) names.

EXAMPLE 1: A Fault Management (FM) application may request a trouble ticket system to open a new trouble ticket reporting the alarmed condition of a network resource by specifying, among other things, the MO name representing the alarmed network resource. The DN of the MO, encoded as specified in the present document, is included in the request.

EXAMPLE 2: A Performance Management (PM) system that produces reports on performance of network resources. The DNs of the MOs, representing the reported network resources, encoded as specified in the present document, are printed on the report.