4.2 Class diagrams

28.6523GPPInformation Service (IS)Release 17Telecommunication managementTSUniversal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP)

4.2.1 Relationships

This clause depicts the set of classes (e.g. IOCs) that encapsulates information relevant for this IRP. This subclause provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these 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.

Figure 4.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 AntennaFunction instances (referenced by a role-attribute of IOC CellReferences inherited by UTRANGenericCell) is required when supporting RET. For a description and clarification of RET, please refer to Annex A.

NOTE 3: The AntennaFunction Instances can be associated with a particular NodeBFunction instance (via IubLink and UTRANGenericCell). These AntennaFunction instances and NodeBFunction instance must be contained by the same ManagedElement instance.

NOTE 4: The TmaFunction Instances can be associated with a particular NodeBFunction instance (via IubLink and UTRANGenericCell). These TmaFunction Instances and NodeBFunction instance must be contained by the same ManagedElement instance.

NOTE 5: Please see TS 28.662 [17] for the definitions of the five associations between a) UtranGenericCell and AntennaFunction b) between UtranGenericCell and SectorEquipmentFunction c) between UtranGenericCell and TmaFunction d) between SectorEquipmentFunction and AntennaFunction and e) between SectorEquipmentFunction and TmaFunction.

Figure 4.2.1-1: Transport view UTRAN NRM Containment/Naming and Association diagram

NOTE 6: 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 7: 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 8: The UtranRelation and GsmRelation can be name-contained under IOCs defined in other NRMs.

NOTE 9: ExternalUTRANGenericCell is contained under SubNetwork or ExternalRncFunction.

Figure 4.2.1-2: Cell view UTRAN NRM Containment/Naming and Association diagram

NOTE 10: 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 11: Each instance of the VsDataContainer shall only be contained under one IOC.
The VsDataContainer can be contained under IOCs defined in other NRMs.

Figure 4.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 4.2.1-4: UTRAN Transport Network NRM Containment/Naming and Association diagram

The VsDataContainer is only used for the Bulk CM IRP.

Each IOC instance 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 4.2.1-5: Association diagram of EP_Iur, EP_IuCS and EP_IuPS

4.2.2 Inheritance

This clause depicts the inheritance relationships that exist between IOCs.

Figure 4.2.2.1 shows the inheritance hierarchy for the UTRAN NRM.

Figure 4.2.2.1: UTRAN NRM Inheritance Hierarchy