6.3 Generic Network Resource Model (NRM)

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

This subclause defines the generic managed object classes supporting the Basic CM IRP. These object classes are protocol environment neutral and the model does not define the syntax or encoding of the operations and parameters.

The model described in this subclause allows for Managed Elements to be defined for management purposes according to the functionality contained within them. As an example, a single implementation of a combined MSC and VLR may be required. However, in the implementation it is required to create a single interface for the management of this element. This is expected to be achieved by instantiating a G3ManagedElement MOC that contains the "mscFunction" MOC, the "vlrFunction" MOC (as in the GSM 12.xx-series of specifications), and other generic or non-UMTS specific MOCs as appropriate to define the manageable capability of that managed element. See also the managedElementType attribute in the G3ManagedElement MOC definition.

It should be noted that, although this model allows for combined managed element functionality as described above, in this subclause only the high-level and generic MOCs are defined. UMTS MOCs modelling more specific managed element functionality are defined in subclause 6.4.

6.3.1 Managed Object Class (MOC) diagrams

6.3.1.1 Inheritance hierarchy

Figure 6 shows the inheritance hierarchy for the generic MO classes defined in this IRP.

Figure 6: Generic NRM Inheritance Hierarchy

6.3.1.2 Containment/Naming and Association diagram

Figure 7 shows the containment/naming hierarchy and the associations of the generic MO classes defined by this IRP.

NOTE: The Managed Object containment/naming relationships are in the diagram(s) below indicated by UML “Aggregation by reference” (“hollow diamonds”).

NOTE 1: G3ManagedElement may be contained in either a G3SubNetwork or an MeContext instance, or have no parent instance at all.

NOTE 2: The listed cardinality numbers represent transient as well as steady-state numbers, and reflect all managed object creation and deletion scenarios.

Figure 7: Generic NRM Containment/Naming and Association diagram

Each Managed Object is identified with a Distinguished Name (DN) according to 3GPP TS 32.106-8 [13] that expresses its containment hierarchy. As an example, the DN of a Managed Element instance could have a format like:

g3SubNetwork=Sweden,meContext=MEC-Gbg-1,g3ManagedElement=RNC-Gbg-1.

Managed Object Class (MOC) definitions

A general note regarding all the notification tables defined for each MOC below: Each MOC may potentially send the notifications listed in the notification table for the MOC. The notifications with qualifier (M) shall be supported by the MOC, and the notifications with qualifier (O) may be supported by the MOC.

For example, if Notification notifyObjectCreation defined in Basic CM IRP has the qualifier (M), then if a MOC is defined such that it emits such a notification, this notification shall be emitted when appropriate (i.e. when a new object is created). If Notification notifyChangedAlarm has the qualifier (O) in Alarm IRP (see 3GPP TS 32.111-2 [11]), then if a MOC is defined such that it emits such a notification, this notification may or may not be emitted when appropriate.

Further, if a notification in the qualifier column (of the MOC notification tables) has a reference to another specification, it means that the qualifier for the notification is specified in the referred specification.

6.3.2.1 MOC G3SubNetwork

This Managed Object Class represents a set of managed entities as seen over the Itf-N.

A G3SubNetwork may have 0…N instances. It shall be present if either a ManagementNode or multiple G3ManagedElements are present (i.e. ManagementNode and multiple G3ManagedElement instances shall have G3SubNetwork as parent). Restriction in R99: N=1.

Table 8: Attributes of G3SubNetwork

Name

Qualifier

Description

g3SubNetworkId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of the G3SubNetwork object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

dnPrefix

READ- ONLY, C

It carries the DN Prefix information as defined in Annex C of 32.106-8 [13]. It shall only be specified if the instance of G3SubNetwork is a local root instance of the MIB. Otherwise the value shall carry the NULL semantics.

userLabel

READ- ONLY, M

A user-friendly (and user assigned) name of the associated object.

Table 9: Notifications of G3SubNetwork

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAttributeValueChange

O

notifyChangedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyClearedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyNewAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyObjectCreation

O

notifyObjectDeletion

O

6.3.2.2 MOC G3ManagedElement

This Managed Object Class represents telecommunications equipment or TMN entities within the telecommunications network that performs Managed Element (ME) functions, i.e. provides support and/or service to the subscriber.
An ME communicates with a manager (directly or indirectly) over one or more interfaces for the purpose of being monitored and/or controlled. MEs may or may not additionally perform element management functionality.
An ME contains equipment that may or may not be geographically distributed. An ME is often referred to as a “Network Element”. This class is similar to the Managed Element class specified in ITU-T M.3100 [4], [5], [6].

A G3ManagedElement may be contained in either a G3SubNetwork or in an MeContext instance. A single G3ManagedElement seen over the Itf-N may also exist stand-alone with no parent at all.

As mentioned in the introduction to subclause 6.3 (the generic model), the G3ManagedElement MOC may be used to represent combined ME functionality (as indicated by the managedElementType attribute and the contained instances of different functional MOCs).

Single function G3ManagedElement managed object instances will have a 1..1 containment relationship to a function Managed Object (in this context a function MO is an MO derived from the ManagedFunction MOC). Multiple function G3ManagedElement managed object instances will have a 1..N containment relationship to function Managed Objects.

It should be noted that although the present document only models UMTS specific functionality with some UTRAN related MOCs, the G3ManagedElement MOC may still be used to represent other ME types than RNC or NodeB, e.g. an MSC or a combined MSC/HLR/VLR.

Table 10: Attributes of G3ManagedElement

Name

Qualifier

Description

g3ManagedElementId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of the G3ManagedElement object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

dnPrefix

READ- ONLY, C

It carries the DN Prefix information as defined in Annex C of 32.106-8 [13]. It shall only be specified if the instance of G3ManagedElement is a local root instance of the MIB. Otherwise the value shall carry the NULL semantics.

managedElementType

READ-ONLY, M

The type of managed element. It is a multi-valued attribute with one or more elements. Thus, it may represent one ME functionality, e.g. an RNC, or a combination of more than one functionality e.g. an MSC/HLR. The allowed members of this attribute are:

RNC, NodeB, MSC, HLR, VLR, AUC, EIR, SMS-IWMSC, SMS-GMSC, GMSC, SGSN, GGSN and BG.

The actual syntax and encoding of this attribute is Solution Set specific.

userLabel

READ-ONLY, M

A user-friendly name of this object.

vendorName

READ-ONLY, M

The name of the G3ManagedElement vendor.

userDefinedState

READ-ONLY, M

An operator defined state for operator specific usage. (See also Note below)

locationName

READ-ONLY, M

The physical location of this entity (e.g. an address).

managedBy

READ-ONLY, M

The value of this attribute shall be the DN of the related managementNode instance. This is a reference attribute modelling the role (of the association MgmtAssociation) that this ME is managed by 0-1 managementNode.

NOTE: In addition to the userDefinedState, state management attributes are expected to be included in the next release.

Table 11: Notifications of G3ManagedElement

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAttributeValueChange

O

notifyChangedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyClearedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyNewAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyObjectCreation

O

notifyObjectDeletion

O

6.3.2.3 MOC MeContext

This Managed Object Class (MOC) is introduced for naming purposes. It may support creation of unique DNs in scenarios when some MEs have the same RDNs due to the fact that they have been manufacturer pre-configured.
If some MEs have the same RDNs (for the above mentioned reason) and they are contained in the same G3SubNetwork instance, some measure shall be taken in order to assure the global uniqueness of DNs for all MOIs under those MEs. One way could be to set different DnPrefixes for those NEs, but that would require either that:

  1. all LDNs or DNs are locally modified using the new DnPrefix for the upper portion of the DNs, or
  2. a mapping (translation) of the old LDNs or DNs to the new DNs every time they are used externally, e.g. in alarm notifications.

As both the two alternatives above may involve unacceptable drawbacks (as the old RDNs for the MEs then would have to be changed or mapped to new values), using MeContext offers a new alternative to resolve the DN creation. Using MeContext as part of the naming tree (and thus the DN) means that the DnPrefix, including a unique MeContext for each ME, may be directly concatenated with the LDNs, without any need to change or map the existing ME RDNs to new values.

MeContext have 0..N instances. It may exist even if no G3SubNetwork exists. Every instance of MeContext contains exactly one G3ManagedElement during steady-state operations.

Table 12: Attributes of MeContext

Name

Qualifier

Description

meContextId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

dnPrefix

READ- ONLY, C

It carries the DN Prefix information as defined in Annex C of 3GPP TS  32.106-8 [13]. It shall only be specified if the instance of MeContext is a local root instance of the MIB. Otherwise the value shall carry the NULL semantics.

Table 13: Notifications of MeContext

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAttributeValueChange

O

notifyChangedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyClearedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyNewAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyObjectCreation

O

notifyObjectDeletion

O

6.3.2.4 MOC ManagementNode

This Managed Object Class represents a telecommunications management system (EM) within the TMN that contains functionality for managing a number of Managed Elements (MEs). The management system communicates with the MEs directly or indirectly over one or more interfaces for the purpose of monitoring and/or controlling these MEs.

This class has similar characteristics as the G3ManagedElement. The main difference between these two classes is that the ManagementNode has a special association to the managed elements that it is responsible for managing.

Table 14: Attributes of ManagementNode

Name

Qualifier

Description

managementNodeId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

userLabel

READ-ONLY, M

A user-friendly name of this object.

vendorName

READ-ONLY, M

The name of the ManagementNode vendor.

userDefinedState

READ-ONLY, M

An operator defined state for operator specific usage.

locationName

READ-ONLY, M

The physical location of this entity (e.g. an address).

manages

READ-ONLY, M

The value of this attribute shall be a list of the DN(s) of the related ManagedElement instance(s). This is a reference attribute modelling the role (of the association MgmtAssociation) that this managementNode is responsible for managing 0-N MEs.

Table 15: Notifications of ManagementNode

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAttributeValueChange

O

notifyChangedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyClearedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyNewAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyObjectCreation

O

notifyObjectDeletion

O

6.3.2.5 MOC ManagedFunction

This Managed Object Class is similar to the class gsmManagedFunction defined in GSM 12.20 [12] and is provided for sub-classing only. It provides the attributes that are common to functional MO classes. Note that a Managed Element may contain several managed functions. The ManagedFunction may be extended in the future if more common characteristics to functional objects are identified.

Table 16: Attributes of ManagedFunction

Name

Qualifier

Description

userLabel

READ-ONLY, M

A user-friendly name of the associated object.

6.3.2.6 MOC IRPAgent

This Managed Object Class represents the functionality of an IRPAgent. It shall be present. For a definition of IRPAgent, see 3GPP TS 32.102 [2].

Restriction in R99: The IRPAgent will be contained under a managed object as follows (only one of the options shall be used):

  1. ManagementNode, if the configuration contains a ManagementNode (see Config #1 and Config #2 in Figure A.1).
  2. G3SubNetwork, if the configuration contains a G3SubNetwork and no ManagementNode (see Config #3 in Figure A.1).
  3. G3ManagedElement, if the configuration contains no ManagementNode or G3SubNetwork (see Config #4 in Figure A.1).

Table 17: Attributes of IRPAgent

Name

Qualifier

Description

irpAgentId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

systemDN

READ-ONLY, C

The Distinguished Name (DN) of IRPAgent. Defined in 3GPP TS 32.106-2 [3].

Table 18: Notifications of IRPAgent

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAlarmListRebuilt

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyAttributeValueChange

O

notifyChangedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyClearedAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyNewAlarm

See Alarm IRP (3GPP TS 32.111-2 [11])

notifyObjectCreation

O

notifyObjectDeletion

O

Note that these notifications are issued based on occurrences on the IRPAgent MOC and not on occurrences on other Basic CM IRP managed objects.

6.3.2.7 MOC NotificationIRP

This Managed Object Class represents the Notification IRP capability associated with each IRPAgent. At least one instance shall be present for every IRPAgent instance. Restriction in R99: Number of instances = 1.

Table 19: Attributes of NotificationIRP

Name

Qualifier

Description

notificationIRPId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

irpVersion

READ-ONLY, M

One or more Notification IRP version entries.

6.3.2.8 MOC AlarmIRP

This Managed Object Class represents the Alarm IRP (see 3GPP TS 32.111-2 [11]) capability associated with each IRPAgent. Restriction in R99: Number of instances = 0..1.

Table 20: Attributes of AlarmIRP

Name

Qualifier

Description

alarmIRPId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

irpVersion

READ-ONLY, M

One or more Alarm IRP (see 3GPP TS 32.111-2 [11]) version entries.

6.3.2.9 MOC BasicCmIRP

This Managed Object Class represents the Basic CM IRP capability associated with each IRPAgent. Restriction in R99: Number of instances = 0..1.

Table 21: Attributes of BasicCmIRP

Name

Qualifier

Description

basicCmIRPId

READ-ONLY, M

An attribute whose ‘name+value’ can be used as an RDN when naming an instance of this object class. This RDN uniquely identifies the object instance within the scope of its containing (parent) object instance.

irpVersion

READ-ONLY, M

One or more Basic CM IRP version entries.

6.3.3 Associations

6.3.3.1 Association MgmtAssociation (M)

This association is used to represent relationships between one or more MEs and the ManagementNode that is responsible for managing the MEs. It has two roles, named Manages and ManagedBy. The role ‘Manages’ models the fact that a ManagementNode is responsible for managing zero or more MEs, and the role ManagedBy models the fact that an ME is managed by zero or one ManagementNode. Each role is in the MOC definition mapped to a reference attribute with the same name.