6.2.1 Attributes and relationships

32.6323GPPConfiguration Management (CM)Core network resources Integration Reference Point (IRP)Network Resource Model (NRM)Release 11Telecommunication managementTS

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 figures below show the containment/naming hierarchy and the associations of the information object classes defined in the present document.

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

Figure 6.2.1.1: CN NRM Containment/Naming relationships 1

Figure 6.2.1.2: CN NRM Containment/Naming relationships 2

Figure 6.2.1.3: Void

CbcFunction

<<InformationObjectClass>>

SgsnFunction

<<InformationObjectClass>>

ManagedElement

(from 32.622)

<<InformationObjectClass>>

0..1

1

0..1

1

<<names>>

0..1

1

0..1

1

<<names>>

CsMgwFunction

<<InformationObjectClass>>

0..n

1

0..n

1

<<names>>

MscServerFunction

<<InformationObjectClass>>

0..1

0..n

0..1

0..n

AssociatedWith3

0..1

1

0..1

1

<<names>>

RncFunction

(from 32.642)

<<InformationObjectClass>>

IucsLink

<<InformationObjectClass>>

0..n

1

0..n

+csMgwFunction-IucsLink

1

ConnectedTo1

0..n

1

1

<<names>>

0..1

0..n

0..1

+connectedRnc

0..n

ConnectedTo3

ExternalRNCFunction (from 32.642)

<<InformationObjectClass>>

0..1

0..n

ConnectedTo2

0..1

0..n

+connectedRnc

IupsLink

<<InformationObjectClass>>

0..n

1

1

<<names>>

0..1

0..n

0..1

+connectedRnc

0..n

ConnectedTo4

IubcLink

<<InformationObjectClass>>

0..n

1

1

<<names>>

0..1

0..n

0..1

+connectedRnc

0..n

ConnectedTo6

ExternalRNCFunction (from 32.642)

<<InformationObjectClass>>

0..1

0..n

0..1

0..n

ConnectedTo5

+connectedRnc

0..1

ConnectedTo7

+connectedRnc

0..1

NOTE: The association between MscServerFunction and CsMgwFunction is optional and is only mandatory when they belong to different ManagedElements.

Figure 6.2.1.4: CN UTRAN NRM Containment/Naming and Association

MscServerFunction

<<InformationObjectClass>>

CsMgwFunction

<<InformationObjectClass>>

0..n

0..1

0..n

0..1

AssociatedWith3

ManagedElement

(from 32.622)

<<InformationObjectClass>>

1

0..1

1

0..1

<<names>>

1

0..n

1

0..n

<<names>>

GsmCell

(from 32.652)

<<InformationObjectClass>>

0..1

0..n

0..1

0..n

AssociatedWith1

ExternalGsmCell

(from 32.652)

<<InformationObjectClass>>

0..n

0..1

0..n

0..1

AssociatedWith2

ALink

<<InformationObjectClass>>

0..n

1

..

1

<<names>>

0..n

0..1

0..n

+csMgwFunction-ALink

0..1

ConnectedTo8

IucsLink

<<InformationObjectClass>>

IupsLink

<<InformationObjectClass>>

SgsnFunction

<<InformationObjectClass>>

0..1

1

0..1

1

<<names>>

0..n

0..1

0..n

0..1

AssociatedWith4

0..n

0..1

0..n

0..1

AssociatedWith5

BssFunction

(from 32.652)

<<InformationObjectClass>>

0..1

0..n

0..1

+connectedBss

ConnectedTo12

0..1

0..n

0..1

+onnectedBss

ConnectedTo11

0..1

0..n

0..1

+connectedBss

ConnectedTo14

ExternalBssFunction

(from 32.652)

<<InformationObjectClass>>

0..1

0..n

0..1

+connectedBss

ConnectedTo9

0..1

0..n

0..1

+connectedBss

ConnectedTo10

0..1

0..1

+connectedBss

0..n

ConnectedTo15

GbLink

<<InformationObjectClass>>

0..n

1

0..n

1

<<names>>

0..1

0..n

0..1

+connectedBss

ConnectedTo13

0..1

0..n

0..1

+connectedBss

ConnectedTo16

NOTE 1: The association between MscServerFunction and CsMgwFunction is optional and is only mandatory when they belong to different ManagedElements.

NOTE 2: The association between MscServerFunction and GsmCell, and SgsnFunction and GsmCell are optional. It may be valid if both the MscServerFunction and GsmCell, or SgsnFunction and GsmCell are managed by the same management node.

Figure 6.2.1.5: CN GERAN NRM Containment/Naming and Association

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 representing a cell could have a format like:

SubNetwork=Sweden, MeContext =MEC-Gbg-1, ManagedElement =MSC-Gbg-1, MscServerFunction=MSC-1.

Figure 6.2.1.6: CN MBMS NRM Containment/Naming and Association

Figure 6.2.1.7: CN CircuitEndPointSubgroup related NRM Containment/Naming and Association

Figure 6.2.1.8: CN MscPool related NRM Containment/Naming and Association

Figure 6.2.1.9: CN SgsnPool related NRM Containment/Naming and Association