6 Information Object Classes
32.6523GPPConfiguration Management (CM)GERAN network resources Integration Reference Point (IRP)Network Resource Model (NRM)Release 12Telecommunication managementTS
6.1 Imported information entities and local labels
Label reference | Local label |
3GPP TS 32.622 [16], information object class, ManagedElement | ManagedElement |
3GPP TS 32.622 [16], information object class, ManagedFunction | ManagedFunction |
3GPP TS 32.622 [16], information object class, SubNetwork | SubNetwork |
3GPP TS 32.622 [16], information object class, Top | Top |
3GPP TS 32.622 [16], information object class, VsDataContainer | VsDataContainer |
3GPP TS 32.642 [19], information object class, UtranRelation | UtranRelation |
3GPP TS 32.762 [22], information object class, EUtranRelation | EUtranRelation |
6.2 Class diagram
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 figures below show the containment/naming hierarchy and the associations of the GERAN NRM.
NOTE 1: The listed cardinality numbers represent transient as well as steady-state numbers, and reflect all managed object creation and deletion scenarios.
NOTE 2: Void.
NOTE 3: The ExternalBssFunction is used in the Core Network NRM.
Figure 6.1: GERAN NRM Containment/Naming and Association diagram
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 an IOC representing a cell could have a format like:
SubNetwork =Sweden,MeContext =MEC-Gbg-1, ManagedElement =RNC-Gbg-1, BssFunction=BSS1.
NOTE 1: The listed cardinality numbers represent transient as well as steady-state numbers, and reflect all managed object creation and deletion scenarios.
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: GERAN NRM Containment/Naming and Association diagram
The VsDataContainer is only used for the Bulk CM IRP.
6.2.2 Inheritance
This clause depicts the inheritance relationships that exist between IOCs.
Figure 6.3 shows the inheritance hierarchy for the GERAN NRM.
Figure 6.3: GERAN NRM Inheritance Hierarchy
6.3 Information object class definitions
6.3.1 BssFunction
6.3.1.1 Definition
This IOC represents BSS functionality. For more information about the BSS, see Ref 3GPP TS 23.002 [20].
6.3.1.2 Attributes
Table 6.1: Attributes of BssFunction
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
6.3.2 BtsSiteMgr
6.3.2.1 Definition
This IOC contains site specific information for a BTS site.
6.3.2.2 Attributes
Table 6.3a: Attributes of BtsSiteMgr
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
latitude | O | M | M |
longitude | O | M | M |
Table 6.3b: Additional attributes of BtsSiteMgr for the support of the State Management IRP
Attribute Name | Support Qualifier | READ | WRITE |
operationalState | O | M | — |
NOTE: No state propagation shall be implied. | |||
6.3.3 GsmCell
6.3.3.1 Definition
This IOC represents the GSM radio cell. The applicability of instantiation of this class is depending on the ME type. It may only be instantiated under ME of type BSC.
6.3.3.2 Attributes
Table 6.5: Attributes of GsmCell
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
cellIdentity | M | M | M |
cellAllocation | M | M | M |
ncc | M | M | M |
bcc | M | M | M |
lac | M | M | M |
mcc | M | M | M |
mnc | M | M | M |
rac | CM | M | M |
racc | CM | M | M |
tsc | CM | M | M |
rxLevAccessMin | M | M | M |
msTxPwrMaxCCH | M | M | M |
rfHoppingEnabled | M | M | M |
hoppingSequenceList | M | M | M |
plmnPermitted | M | M | M |
6.3.3.3 Attribute constraints
Name | Definition |
rac CM support qualifier | GPRS is supported in the cell. |
racc CM support qualifier | GPRS is supported in the cell. |
tsc CM support qualifier | RET and TMA etc. are not modelled according to Ref 3GPP TS 32.792 [21]. |
6.3.4 GsmRelation
6.3.4.1 Definition
This IOC contains a Neighbour cell Relation (NR) from a source cell to a target cell, where the target cell is a GsmCell or ExternalGsmCell instance.
NOTE: In handover relation terms, the cell containing the GsmRelation object is the source cell for the handover. The cell referred to in the GsmRelation object is the target cell for the handover. This defines a one-way handover relation where the direction is from source cell to target cell.
The source cell can be a GsmCell instance. This is the case for an Intra-GERAN NR.
The source cell can be an UtranGenericCell instance. This is the case for Inter-RAT NR from UTRAN to GERAN. See 3GPP TS 32.642 [19].
The source cell can be an EUtranGenericCell instance. This is the case for Inter-RAT NR from E-UTRAN to GERAN. See 3GPP TS 32.762 [22].
6.3.4.2 Attributes
Table 6.7: Attributes of GsmRelation
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
adjacentCell | M | M | M |
bcchFrequency | CM | M | – |
ncc | CM | M | – |
bcc | CM | M | – |
lac | CM | M | – |
isHOAllowed | CM | M | M |
isRemoveAllowed | CM | M | M |
isESCoveredBy | CM | M | M |
6.3.4.3 Attribute constraints
Name | Definition |
bcchFrequency CM support qualifier | The EM does not guarantee consistency between the cell definition and what is broadcasted on system information and RET, TMA etc. are not modelled according to Ref 3GPP TS 32.792 [21]. |
ncc CM support qualifier | The EM does not guarantee consistency between the cell definition and what is broadcasted on system information. |
bcc CM support qualifier | The EM does not guarantee consistency between the cell definition and what is broadcasted on system information. |
lac CM support qualifier | The EM does not guarantee consistency between the cell definition and what is broadcasted on system information. |
isRemoveAllowed Support Qualifier | The condition is "Inter-RAT ANR function is supported in the source cell, and the source cell is an EUtranGenericCell or an UtranGenericCell ". |
isHOAllowed Support Qualifier | The condition is "Inter-RAT ANR function is supported in the source cell, and the source cell is an EUtranGenericCell or an UtranGenericCell ". |
isESCoveredBy support qualifier | The condition is "The source cell is an E-UTRAN or UTRAN cell which supports Inter-RAT Energy Saving". |
6.3.5 ExternalGsmCell
6.3.5.1 Definition
This IOC represents a radio cell controlled by another IRPAgent. This IOC has necessary attributes for inter-system handover. It contains a subset of the attributes of related IOCs controlled by another IRPAgent. To maintain the consistency between the attribute values of these two IOCs is outside the scope of this document.
6.3.5.2 Attributes
Table 6.9: Attributes of ExternalGsmCell
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
cellIdentity | M | M | M |
bcchFrequency | M | M | M |
ncc | M | M | M |
bcc | M | M | M |
lac | M | M | M |
mcc | M | M | M |
mnc | M | M | M |
rac | CM | M | M |
racc | CM | M | M |
6.3.5.3 Attribute constraints
Name | Definition |
rac CM support qualifier | GPRS is supported in the cell. |
racc CM support qualifier | GPRS is supported in the cell. |
6.3.6 ExternalBssFunction
6.3.6.1 Definition
This IOC represents a BssFunction controlled by another IRPAgent. It contains a subset of the attributes of related IOCs controlled by another IRPAgent. To maintain the consistency between the attribute values of these two IOCs is outside the scope of the present document.
6.3.6.2 Attributes
Table 6.11: Attributes of ExternalBssFunction
Attribute name | Support Qualifier | Read Qualifier | Write Qualifier |
id | M | M | – |
6.3.6.3 Attribute constraints
None.
6.4 Information relationship definitions
6.4.1 ExternalGsmNeighbourCellRelation (M)
6.4.1.1 Definition
This represents a unidirectional relation from GsmRelation to the ExternalGsmCell. The role of the relation shall be mapped to a reference attribute, named adjacentCell, of the IOC.
6.4.1.2 Roles
Table 6.11: Roles of the relation ExternalGsmNeighbourCellRelation
Name | Definition |
gsmRelation-externalGsmNeighbourCell | This role (when present) represents GsmRelation capability to identify one ExternalGsmCell. When this role is present, the GsmRelation.adjacentCell shall contain one ExternalGsmCell DN. |
6.4.1.3 Constraints
Name | Definition |
external_neighbour_cell_relation | The role gsmRelation-externalGsmNeighbourCell is only present if the target cell is managed by another IRPAgent than the serving cell. |
6.4.2 GsmNeighbourCellRelation (M)
6.4.2.1 Definition
This represents the unidirectional relation from the GsmRelation to GsmCell. The role of the relation shall be mapped to a reference attribute, named adjacentCell, of the IOC.
6.4.2.2 Roles
Table 6.12: Roles of the relation GsmNeighbourCellRelation
Name | Definition |
gsmRelation-gsmNeighbourCell | This role (when present) represents GsmRelation capability to identify one GsmCell. When this role is present, the GsmRelation.adjacentCell shall contain one GsmCell DN. |
6.4.2.3 Constraints
This role (for a particular GsmRelation) shall be present if the ExternalGsmNeighbourCellRelation of this particular GsmRelation is absent. This role shall be absent if the ExternalGsmNeighbourCellRelation of this particular GsmRelation is present.
Name | Definition |
internal_neighbour_cell_relation | The role gsmRelation-gsmNeighbourCell is only present if the target cell is managed by the same IRPAgent as the serving cell. |
6.5 Information attribute definitions
6.5.1 Definition and legal values
Table 6.13 defines the attributes that are present in several information object classes of the present document.
Table 6.13: Attributes
Attribute Name | Definition | Legal Values |
|---|---|---|
adjacentCell | Pointer to GsmCell or ExternalGsmCell. Distinguished Name of the corresponding object. | |
bcc | IOCs GsmCell and ExternalGsmCell: Base station colour code, BCC (part of BSIC). Ref 3GPP TS 44.018 [4]. IOC GsmRelation: Base station colour code, BCC (part of BSIC. Ref 3GPP TS 44.018 [4]) for another GSM cell or the external GSM cell, that is broadcast in System Information in the Cell. | See Ref 3GPP TS 44.018 [4]. |
bcchFrequency | IOC ExternalGsmCell: This attribute contains the absolute radio frequency channel number of the BCCH channel of the GSM cell. IOC GsmRelation: This attribute contains the absolute radio frequency channel number of the BCCH channel of another GSM cell or the external GSM cell, which is broadcast in System Information in the Cell. | |
cellAllocation | This attribute defines the set of radio frequencies allocated and available to a cell, the first element sets the BCCH frequency, Ref 3GPP TS 44.018 [4]. | See Ref 3GPP TS 44.018 [4]. |
cellIdentity | Cell Identity (Ref 3GPP TS 24.008 [3]). | See Ref 3GPP TS 24.008 [3]. |
hoppingSequenceList | A list of hopping sequence, which is a structure including MA (see 44.018[4]) and HSN (see 45.002[6]). | See Ref 3GPP TS 44.018 [4]. |
isESCoveredBy | The value of the attribute is configured by the IRPManager and is not changed by the IRPAgent. It indicates whether the adjacentCell according to this planning provides no, partial or full Inter-RAT coverage for the cell which name-contains the GsmRelation instance. Adjacent cells with this attribute equal to “yes” are recommended to be considered as candidate cells to take over the coverage when the original cell is about to be transferred to energySaving state. The entirety of adjacent cells with this property equal to “partial” are recommended to be considered as entirety of candidate cells to take over the coverage when the original cell is about to be transferred to energySaving state. | No, partial, yes |
lac | IOCs GsmCell and ExternalGsmCell: Location Area Code, LAC. Ref 3GPP TS 24.008 [3]. IOC GsmRelation: Location Area Code, LAC (Ref 3GPP TS 24.008 [3]) for another GSM cell or the external GSM cell, which is broadcast in System Information in the Cell. | See Ref 3GPP TS 24.008 [3]. |
latitude | Used for geographical positioning of the sitemanager | |
longitude | Used for geographical positioning of the sitemanager | |
mcc | Mobile Country Code, MCC (part of the PLMN Id, Ref. 3GPP TS 23.003 [8]). | See Ref 3GPP TS 24.008 [3]. |
mnc | Mobile Network Code, MNC (part of the PLMN Id, Ref. 3GPP TS 23.003 [8]). | See Ref 3GPP TS 24.008 [3]. |
msTxPwrMaxCCH | Maximum Transmission Power for a Mobile Station on a CCH. Attribute description Ref 3GPP TS 45.008 [5] (MS_TXPWR_MAX_CCH) | See Ref 3GPP TS 45.008 [5]. |
ncc | IOCs GsmCell and ExternalGsmCell: Network Colour Code, NCC (part of BSIC). Ref 3GPP TS 44.018 [4]. IOC GsmRelation: Network Colour Code, NCC (part of BSIC. Ref 3GPP TS 44.018 [4]) for another GSM cell or the external GSM cell, that is broadcast in System Information in the Cell. | See Ref 3GPP TS 44.018 [4]. |
plmnPermitted | Network Colour Code Permitted. Attribute description reference 3GPP TS 45.008 [5] (NCC_PERMITTED) | See Ref 3GPP TS 45.008 [5]. |
rac | Routing Area Code, RAC. Ref 3GPP TS 44.018 [4]. | See Ref 3GPP TS 44.018 [4]. |
racc | Routing Area Colour Code, RACC. Ref 3GPP TS 44.018 [4]. | See Ref 3GPP TS 44.018 [4]. |
rfHoppingEnabled | Indicates if frequency hopping is enabled. | Boolean values 0 represents “disabled”, 1 represents “enabled”. |
rxLevAccessMin | Minimum Access Level. Attribute description Ref 3GPP TS 45.008 [5] (RXLEV_ACCESS_MIN) | See Ref 3GPP TS 45.008 [5]. |
tsc | Training Sequence Code, an attribute of the class channel in Ref 3GPP TS 44.018 [4] | See Ref 3GPP TS 44.018 [4]. |
isHOAllowed | This indicates if HO is allowed or prohibited. If ‘yes’, handover is allowed from source cell to target cell. The source cell is identified by the name-containing UtranGenericCell or EUtranGenericCell of the GsmRelation that has the isHOAllowed. The target cell is referenced by the GsmRelation that has this isHOAllowed. If ‘no’, handover shall not be allowed. | yes, no |
isRemoveAllowed | This indicates if the subject GsmRelation can be removed (deleted) or not. If ‘yes’, the subject GsmRelation instance can be removed (deleted). If ‘no’, the subject GsmRelation instance shall not be removed (deleted) by any entity but an IRPManager. | yes, no |
6.5.2 Constraints
Name | Definition |
– | – |
6.6 Common Notifications
The following notifications apply to the following IOCs:
- BssFunction;
- BtsSiteMgr;
- GsmCell.
Name | Qualifier | Notes |
|---|---|---|
notifyAckStateChanged | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyAttributeValueChange | O | |
notifyChangedAlarm | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyClearedAlarm | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyNewAlarm | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyObjectCreation | O | |
notifyObjectDeletion | O | |
notifyComments | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyAlarmListRebuilt | See Alarm IRP (3GPP TS 32.111-2 [11]) | |
notifyPotentialFaultyAlarmList | See Alarm IRP (3GPP TS 32.111-2 [11]) |
The following notifications apply to the following IOCs:
- GsmRelation;
- ExternalGsmCell;
- ExternalBssFunction.
Name | Qualifier | Notes |
|---|---|---|
notifyAttributeValueChange | O | |
notifyObjectCreation | O | |
notifyObjectDeletion | O |
6.7 Void
Annex A (informative):
Change history
Change history | ||||||||
Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
Jun 2001 | SA_12 | SP-010283 | — | — | Approved at TSG SA #12 and placed under Change Control | 2.0.0 | 4.0.0 | |
Sep 2001 | SA_13 | SP-010477 | 0001 | — | Addition of mcc and mnc in the object model of GERAN | F | 4.0.0 | 4.1.0 |
Dec 2001 | SA_14 | SP-010650 | 0002 | — | Correction of references | F | 4.1.0 | 4.2.0 |
Jun 2002 | SA_16 | SP-020305 | 0003 | — | Addition of the attributes mcc and mnc in the object model of GERAN | F | 4.2.0 | 4.3.0 |
Jun 2002 | SA_16 | SP-020305 | 0004 | — | Correction of attribute descriptions in the Managed Object Class (MOC) GsmRelation of 32.652 (GERAN network resources IRP: NRM) | F | 4.2.0 | 4.3.0 |
Jun 2002 | SA_16 | SP-020304 | 0005 | — | Correction of supported IRP in system context | F | 4.2.0 | 4.3.0 |
Sep 2002 | SA_17 | SP-020494 | 0006 | — | UML corrections | F | 4.3.0 | 4.4.0 |
Sep 2002 | SA_17 | SP-020496 | 0007 | — | Add State Management | B | 4.4.0 | 5.0.0 |
Dec 2002 | — | — | — | — | Cosmetics | — | 5.0.0 | 5.0.1 |
Jun 2003 | SA_20 | SP-030282 | 0010 | — | Include notification tables | A | 5.0.1 | 5.1.0 |
Jun 2003 | SA_20 | SP-030282 | 0012 | — | Correction of UML diagram vsDataContainer Containment/Naming and Association in GERAN NRM | A | 5.0.1 | 5.1.0 |
Jun 2003 | SA_20 | SP-030283 | 0014 | — | Deletion of GERAN attribute relationType | A | 5.0.1 | 5.1.0 |
Sep 2003 | SA_21 | SP-030418 | 0015 | — | Inclusion of External BSS Function in GERAN NRM – Alignment with 32.632 | F | 5.1.0 | 5.2.0 |
Dec 2003 | SA_22 | SP-030641 | 0016 | — | Add missing notification notifyPotentialFaultyAlarmlist | F | 5.2.0 | 5.3.0 |
Dec 2003 | SA_22 | SP-030643 | 0017 | — | VsDataContainer Containment UML – Now covered by 32.622 | F | 5.2.0 | 5.3.0 |
Sep 2004 | SA_25 | SP-040584 | 0018 | Add support for the state change notification in GERAN network resources IRP NRM | B | 5.3.0 | 6.0.0 | |
Mar 2005 | — | — | — | — | Title corrected (changed Release 5 to Release 6) | — | 6.0.0 | 6.0.1 |
Jun 2005 | SA_28 | SP-050298 | 0019 | — | Correction of System Context and Compliance rules | F | 6.0.1 | 6.1.0 |
Dec 2005 | SA_30 | SP-050713 | 0020 | — | Correct relationships for External IOCs | F | 6.1.0 | 6.2.0 |
Dec 2005 | SA_30 | SP-050723 | 0021 | — | Apply IS Template and the UML Repertoire – Align with 32.151 and 32.152 | F | 6.1.0 | 6.2.0 |
Jan 2006 | — | — | — | — | Editorial correction to change history table. | — | 6.2.0 | 6.2.1 |
Jun 2007 | SA_36 | — | — | — | Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. | — | 6.2.1 | 7.0.0 |
Dec 2008 | SA_42 | — | — | — | Upgrade to Release 8 | — | 7.0.0 | 8.0.0 |
Dec 2009 | SA_46 | SP-090719 | 0022 | — | Correction of imported IOC UtranCell and ExternalUtranCell from 32.642 | F | 8.0.0 | 9.0.0 |
Jan 2009 | — | — | — | — | Removal of track changes | — | 9.0.0 | 9.0.1 |
Sep 2010 | SA_49 | SP-100488 | 0024 | — | Corrections of attribute hoppingSequenceNumber in GsmCell IOC | F | 9.0.1 | 9.1.0 |
Sep 2010 | SA_49 | SP-100489 | 0023 | — | Add attribute rfHoppingEnabled in GsmCell IOC | B | 9.1.0 | 10.0.0 |
Mar 2011 | SA-51 | SP-110095 | 0025 | — | Methodology clean-up of Configuration Management; GERAN network resources IRP; Network Resource Model | F | 10.0.0 | 10.1.0 |
Mar 2011 | SA-51 | SP-110096 | 0026 | — | Correcting the support qualifier of attributes tsc and bcchFrequency | F | 10.0.0 | 10.1.0 |
May 2011 | SA-52 | SP-110285 | 0028 | – | Correct attribute constraints | F | 10.1.0 | 10.2.0 |
Dec 2011 | SA-54 | SP-110704 | 0031 | 2 | Add Neighbour cell Relation from GERAN towards E-UTRAN | A | 10.2.0 | 10.3.0 |
Dec 2011 | SA-54 | SP-110704 | 0034 | 2 | Add management of IRAT ANR from E-UTRAN to GERAN | A | 10.2.0 | 10.3.0 |
Dec 2011 | SA-54 | SP-110719 | 0035 | 2 | Add management of IRAT ANR from UTRAN to GERAN and from E-UTRAN to GERAN | B | 10.3.0 | 11.0.0 |
Mar 2012 | SA-55 | SP-120057 | 0036 | — | Add management of IRAT ANR from UTRAN to GERAN | F | 11.0.0 | 11.1.0 |
Sep-2012 | SA-57 | SP-120573 | 0038 | 1 | Add support for Inter-RAT Energy Saving Management | B | 11.1.0 | 11.2.0 |
Sep-2013 | Editorial changes: misspellings,wrong capital letters,wrong abbreviations | 11.2.0 | 11.2.1 | |||||
2014-10 | – | – | – | – | Update to Rel-12 version (MCC) | 11.2.1 | 12.0.0 | |