4 Architectural Features

32.111-33GPPFault ManagementPart 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)Release 7Telecommunication managementTS

The overall architectural feature of Alarm IRP is specified in 3G TS 32.111-2 [6]. This clause specifies features that are specific to the CORBA SS.

4.1 Notification Services

In implementations of CORBA SS, IRPAgent conveys Alarm Information to IRPManager via OMG Notification Service (OMG Notification Service [1]).

OMG Event Service [2] provides event routing and distribution capabilities. OMG Notification Service provides, in addition to Event Service, event filtering and Quality Of Service (QOS) as well.

A necessary and sufficient sub set of OMG Notification Services shall be used to support AlarmIRPNotifications notifications as specified in 3G TS 32.111-2 [6].

4.2 Push and Pull Style

OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRPAgent pushes notifications to IRPManager as soon as they are available. The other is called pull style. In this style, IRPAgent keeps the notifications till IRPManager requests for them.

This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O).

4.3 Support multiple notifications in one push operation

For efficiency reasons, IRPAgent may send multiple notifications using one single push operation. To pack multiple notifications into one push operation, IRPAgent may wait and not invoke the push operation as soon as notifications are available. To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent shall implement an IRPAgent wide timer configurable by administrator. On expiration of this timer, IRPAgent shall invoke push if there is at least one notification to be conveyed to IRPManager. This timer is re-started after each push invocation.

4.4 Filter

IRPAgent shall optionally support alarm filtering based on IRPManager’s supplied alarm filter constraints (e.g. as parameter in subscribe() of 3G TS 32.302 [4]. Alarm filtering can be applied in the following cases:

– It is applicable to alarms emitted by IRPAgent via AlarmIRPNotifications. IRPManager supplies alarm filter constraint via the subscribe method. This filter is effective during the period of subscription.

– It is applicable to alarms returned by IRPAgent via the out parameter of get_alarm_list method. IRPManager supplies alarm filter constraint via the get_alarm_list method. This filter is effective only for this method invocation.

– It is applicable to the calculation of alarm counts returned by IRPAgent via the out parameters of get_alarm_count method. IRPManager supplies alarm filter constraint via the get_alarm_count method. This filter is effective only for this method invocation.

This SS shall use of filter constraint grammar specified by reference OMG Notification Service [1]. The name of the grammar is called "EXTENDED_TCL". See clause 2.4, Default Filter Constraint Language in OMG Notification Service [1]. This SS shall use this grammar only.