4.5 Common notifications

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

4.5.1 Alarm notifications

This subclause presents a list of notifications, defined in [11], that IRPManager can receive. The notification header attribute objectClass/objectInstance, defined in [7], would capture the DN of an instance of an IOC defined in this IRP specification.

Name

Qualifier

Notes

notifyAckStateChanged

See Alarm IRP (3GPP TS 32.111-2 [11])

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])

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])

4.5.2 Configuration notifications

This subclause presents a list of notifications, defined in [10], that IRPManager can receive. The notification header attribute objectClass/objectInstance, defined in [7], would capture the DN of an instance of an IOC defined in this IRP specification.

Name

Qualifier

Notes

notifyAttributeValueChange

O

notifyObjectCreation

O

notifyObjectDeletion

O

Annex A (informative):
RET Control Architecture

The Itf-N provides an abstraction of resources to allow the monitor and control of physical resource from the network level management systems. For RET, the antenna tilt is controlled via a control unit which is located within the NodeB (from a management perspective). The control unit sends commands to actuators located at the tower top, in order to read, and to adjust antenna tilt values.

The AntennaFunction class will report failures and malfunctions of either the control unit, or the tilt.

There are several configurations of antennae. Some support the transmission of several frequencies from a single radome while others are deployed as an array in order to provide effective coverage.

Hence in the UTRAN model there is an N:M relationship between the UtranCell class and the AntennaFunction class, permitting the model to support all possibilities. The figure B.1 below illustrates the RET architecture.

Figure B.1: Overall RET architecture

Annex B (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Cat

Old

New

2013-03

SA#59

SP-130057

001

1

CR R11 28.652 Addition of missing Network Sharing support for MDT

F

11.0.0

11.1.0

2013-09

SA#61

SP-130433

002

1

UTRAN NRM Correction of wrong import references

F

11.1.0

11.2.0

2014-06

SA#64

SP-140332

003

2

Correction of operationalState attribute definitions

F

11.2.0

11.3.0

004

1

Correct synCase attribute description and usage of BITSTRING(32) data type

F

SP-140359

005

remove the feature support statements

F

2014-09

Correction of editorial issues(MCC)

11.3.0

11.3.1

2014-09

Upgrade to Rel-12 (MCC)

11.3.1

12.0.0

2014-12

SA#66

SP-140800

008

2

Add support for sharing of UTRAN

B

12.0.0

12.1.0

2015-06

SA#68

SP-150316

011

Add missing IOC notification support

A

12.1.0

12.2.0

013

Correct IsNullable properties for power attributes

A

2015-12

SA#70

SP-150691

014

1

Align id attribute definitions

A

12.2.0

12.3.0

2016-01

SA#70

Upgrade to Rel-13(MCC)

12.3.0

13.0.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2017-03

SA#75

Promotion to Release 14 without technical change

14.0.0

2018-06

Update to Rel-15 version (MCC)

15.0.0

2020-07

Update to Rel-16 version (MCC)

16.0.0

2022-03

Update to Rel-17 version (MCC)

17.0.0