4.2 Class diagrams

28.6223GPPGeneric Network Resource Model (NRM) Integration Reference Point (IRP)Information Service (IS)Release 18Telecommunication managementTS

4.2.1 Relationships

This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP. This clause 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 figure shows the containment/naming hierarchy and the associations of the classes defined in the present document. See Annex A of a class diagram that combines this figure with Figure 1 of [2], the class diagram of UIM.

NOTE 1: ManagedElement may be contained either

– in a SubNetwork (since SubNetwork inherits from Domain_ and ManagedElement inherits from ManagedElement_ and Domain_ name-contained ManagedElement_ as observed in the figure of Annex A) or

– in a MeContext instance as observed by the above figure or in the figure of Annex A.

This either-or relation cannot be shown by using an {xor} constraint in the above figure.

ManagedElement may also have no parent instance at all.

NOTE 2: Void

NOTE 3: If the configuration contains several instances of SubNetwork, exactly one SubNetwork instance shall directly or indirectly contain all the other SubNetwork instances.

NOTE 4: The SubNetwork instance not contained in any other instance of SubNetwork is referred to as "the root SubNetwork instance".

NOTE 5: ManagementNode shall be contained in the root SubNetwork instance.

NOTE 6: If contained in a SubNetwork instance, MnsAgent shall be contained in the root SubNetwork instance.

NOTE 7: For a clarification on the choice of containment of the IRPAgent (since it has three possible parents), see the definition of MnsAgent.

NOTE 8: The MnsAgent shall be replaced by the IRPAgent in deployments using the IRP framework as defined in TS 32.102 [2].

Figure 4.2.1-1: NRM fragment

Each Managed Object 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 a ManagedElement instance could have a format like:

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

NOTE 8: Void

NOTE 9: Void

Figure 4.2.1-2: Vendor specific data container NRM fragment

Figure 4.2.1-3: PM control NRM fragment

Figure 4.2.1-4: Threshold monitoring control NRM fragment

Figure 4.2.1-5: Notification subscription and heartbeat notification control NRM fragment

Figure 4.2.1-6: FM control NRM fragment

Figure 4.2.1-7: Trace control NRM fragment

Figure 4.2.1-8: MnS Registry NRM fragment

Figure 4.2.1-9: File retrieval NRM fragment

Figure 4.2.1-10: File download NRM fragment

Figure 4.2.1-11: Management data collection NRM fragment

4.2.2 Inheritance

This clause depicts the inheritance relationships.

Figure 4.2.2-1: NRM fragment

Figure 4.2.2-2: PM control NRM fragment

Figure 4.2.2-3: Threshold monitoring control NRM fragment

Figure 4.2.2-4: Notification subscription and heartbeat notification control NRM fragment

Figure 4.2.2-5: FM control NRM fragment

Figure 4.2.2-6: Trace control NRM fragment

Figure 4.2.2-7: MnS Registry NRM fragment

Figure 4.2.2-8: File retrieval NRM fragment

Figure 4.2.2-9: File download NRM fragment

Figure 4.2.2-10: Management data collection NRM fragment