6.2 Class diagram

32.6423GPPConfiguration Management (CM)Network Resource Model (NRM)Release 11Telecommunication managementTSUTRAN network resources Integration Reference Point (IRP)

6.2.1 Attributes and relationships

This clause depicts the set of IOCs that encapsulate information relevant for this service. This clause provides the overview of all information object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these information object classes.

The following figures show the containment/naming hierarchy and the associations of the information object classes defined in the present document. They are split in several figures only for a readability purpose.

NOTE 1: The listed cardinality numbers, in particular the use of cardinality number zero, do not represent transient states. The transient state is considered an inherent property of all IOC instances and therefore there is no need to represent them by individual IOC cardinality numbers.

NOTE 2: The IOC AntennaFunction is required when supporting RET. For a description and clarification of RET, please refer to Annex B.

NOTE 3: The instances of the AntennaFunction associated with a particular instance of NodeBFunction shall be contained by the same ManagedElement instance.

NOTE 4: The instances of the TmaFunction associated with a particular instance of NodeBFunction shall be contained by the same ManagedElement instance.

NOTE 5: Please see TS 32.792 [24] for the definitions of the associations EUtranCell-AntennaRelation, EUtranCell-SectorRelation, EUtranCell-TmaRelation, SectorEquipment-AntennaRelation and SectorEquipment-TmaRelation.

Figure 6.2.1.1: Transport view UTRAN NRM Containment/Naming and Association diagram

NOTE 1: The listed cardinality numbers, in particular the use of cardinality number zero, do not represent transient states. The transient state is considered an inherent property of all IOC instances and therefore there is no need to represent them by individual IOC cardinality numbers.

NOTE 2: The relation between GsmRelation and GsmCell is optional. It may be present if both the UtranGenericCell and the GsmCell are managed by the same management node.

NOTE 3: The UtranRelation and GsmRelation can be name-contained under IOCs defined in other NRMs.

NOTE 4: ExternalUtranGenericCell is contained under SubNetwork or ExternalRncFunction.

Figure 6.2.1.2: Cell view UTRAN NRM Containment/Naming and Association diagram

NOTE 1: The listed cardinality numbers, in particular the use of cardinality number zero, do not represent transient states. The transient state is considered an inherent property of all IOC instances and therefore there is no need to represent them by individual IOC cardinality numbers.

NOTE 2: Each instance of the VsDataContainer shall only be contained under one IOC.
The VsDataContainer can be contained under IOCs defined in other NRMs.

Figure 6.2.1.3: VsDataContainer Containment/Naming and Association in UTRAN NRM diagram

NOTE 1: The ATMChannelTerminationPoint is name-contained under IOCs defined in the Transport Network NRM.

NOTE 2: The group of ATMChannelTerminationPoints associated with an IubLink
(the relation AssociatedWith1) represent the RNC end of the ATM Virtual Channel Connections (transport connection) between an RNC and a NodeB.

NOTE 3: An ATMChannelTerminationPoint can be associated with more than one IubLink for the case of AAL2 multiplexing/switching.
I.e. to allow an ATM Channel at the RNC to be connected to multiple NodeBs.

Figure 6.2.1.4: UTRAN Transport Network NRM Containment/Naming and Association diagram

The VsDataContainer is only used for the Bulk CM IRP.

Each IOC is identified with a Distinguished Name (DN) according to 3GPP TS 32.300 [13] that expresses its containment hierarchy. As an example, the DN of an IOC instance representing a cell could have a format like:

SubNetwork=Sweden, MeContext=MEC-Gbg-1,ManagedElement=RNC-Gbg-1, RncFunction=RF-1,UtranCell=Gbg-1.

Figure 6.2.1.5: EP_Iur Containment/Naming and Association diagram

Figure 6.2.1.6: Energy Saving view of UTRAN NRM

6.2.2 Inheritance

This clause depicts the inheritance relationships that exist between IOCs.

Figure 6.2.2.1 shows the inheritance hierarchy for the UTRAN NRM.

Figure 6.2.2.1: UTRAN NRM Inheritance Hierarchy