3 Definitions and abbreviations

32.6023GPPBasic CM Integration Reference Point (IRP)Configuration Management (CM)Information Service (IS)Release 17Telecommunication managementTS

3.1 Definitions

For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [17], 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [6] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [17], 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [6].

Association: Association used to model relationships between Managed Objects.

NOTE 1: Associations can be implemented in several ways, such as:

a) name bindings,

b) reference attributes, and

c) association objects.

This IRP stipulates that containment associations shall be expressed through name bindings, but it does not stipulate the implementation for other types of associations as a general rule. These are specified as separate entities in the object models (UML diagrams). Currently however, all (non-containment) associations are modelled by means of reference attributes of the participating MOs.

Managed Object (MO): software object that encapsulates the manageable characteristics and behaviour of a particular network resource.

NOTE 2: The MO is instance of a MO class defined in a MIM/NRM. An MO class has attributes that provide information used to characterize the objects that belong to the class. Furthermore, an MO class can have operations that represent the behaviour relevant for that class. An MO class may support notifications that provide information about an event occurrence within a network resource.

Management Information Base (MIB): A MIB is an instance of an NRM and has some values on the defined attributes and associations specific for that instance.

NOTE 3: In the context of the present document, an MIB consists of:

a) a Name space (describing the MO containment hierarchy in the MIB through Distinguished Names),

b) a number of Managed Objects with their attributes and

c) a number of Associations between these MOs. Also note that TMN (ITU-T Recommendation X.710 [7]) defines a concept of a Management Information Tree (also known as a Naming Tree) that corresponds to the name space (containment hierarchy) portion of this MIB definition. Figure 3.1 depicts the relationships between a Name space and a number of participating MOs (the shown association is of a non-containment type)

Figure 3.1: Relationships between a Name space and a number of participating MOs

Name space: A name space is a collection of names. The IRP name convention (see 3GPP TS 32.300 [5]) restricts the name space to a hierarchical containment structure, including its simplest form – the one-level, flat name space.
All Managed Objects in a MIB shall be included in the corresponding name space and the MIB/name space shall only support a strict hierarchical containment structure (with one root object). A Managed Object that contains another is said to be the superior (parent); the contained Managed Object is referred to as the subordinate (child). The parent of all MOs in a single name space is called a Local Root. The ultimate parent of all MOs of all managed systems is called the Global Root.

Network resource: See definition in 3GPP TS 28.622 [16].

Network Resource Model (NRM): See definition in 3GPP TS 28.622 [16].

3.2 Abbreviations

For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [17] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [17].

DN Distinguished Name (see 3GPP TS 32.300 [5])

MO Managed Object

RDN Relative Distinguished Name (see 3GPP TS 32.300 [5])

SS Solution Set