6 Use of OMG Notification StructuredEvent

32.106-33GPPCommon Object Request Broker Architecture (CORBA) Solution Set (SS)Configuration Management (CM)Part 3: Notification Integration Reference Point (IRP)Telecommunication managementTS

Notification IRP: IS (3GPP TS 32.106-2 [5]) defines attributes that are commonly present in notifications of all notification categories such as notifications emitted from Alarm IRP IRPAgent.

In CORBA SS, OMG defined StructuredEvent (OMG TC Document telecom [2]) is used to carry notification. This clause identifies the OMG defined StructuredEvent attributes that carry the common attributes defined in 3GPP TS 32.106-2 [5].

The composition of OMG StructuredEvent is:

Header

Fixed Header

Domain_name

Type_name

Event_name

Variable Header

Body

Filterable_body_fields

Remaining_body

Table 13 shows the OMG Structured Event attributes (middle column) that are used to carry the common notification attributes defined in Notification IRP: IS (3GPP TS 32.106-2 [5]).

Table 13: Attributes of StructuredEvent

Common attributes defined in Notification IRP: IS (3GPP TS 32.106-2 [5])

Attribute defined by OMG Structured Event

Comment

There is no corresponding SS attribute.

domain_name

It indicates that the StructuredEvent, carried in the Notification, is defined by a specific 3GPP IRP such as Alarm IRP, as opposed to OMG specified Telecommunication, healthcare, utility, finance, etc. It indicates the CORBA SS version number as well.

It is a string. Legal values are defined in module.

For Alarm IRP version 1:1, the value is ALARM_IRP_VERSION_1_1.

eventType

type_name

It indicates event types of this notification. The semantics of the event type is defined by ITU-T TMN Recommendations. Each IRP, such as Alarm IRP IS version 1, shall identify the ITU-T defined event types for their use. Each such IRP document shall define the values of the identified event Types as well.

Dependent on the notification category, possible legal values are:

COMMUNICATIONS_ALARM (clause 8.1.1 of ITU-T Recommendation X.736 [8]),

QUALITY_OF_SERVICE_ALARM (clause 8.1.1 of ITU-T Recommendation X.736 [8]),

PROCESSING_ERROR_ALARM (clause 8.1.1 of ITU-T Recommendation X.736 [8]),

EQUIPMENT_ALARM (clause 8.1.1 of ITU-T Recommendation X.736 [8]),

ENVIRONMENTAL_ALARM (clause 8.1.1 of ITU-T Recommendation X.736 [8]),

PHYSICAL_VIOLATION (ITU-T Recommendation X.736 [1]),

INTEGRITY_VIOLATION (ITU-T Recommendation X.736 [1]),

SECURITY_VIOLATION (ITU-T Recommendation X.736 [1]),

TIME_DOMAIN_VIOLATION (ITU-T Recommendation X.736 [1]),

OPERATIONAL_VIOLATION (ITU-T Recommendation X.736 [1]).

The bracketed number of each type indicates the reference where the semantics of the type is specified.

It is a string. See each individual CORBA SS IDL module for each IRP using the Notification IRP, for legal values used by that IRP version.

Since each IRP except Notification IRP specifies its own set of event type, the values specified by each IRP are only unique within one IRP. For uniqueness among all IRPs’ specifications, the values of event type shall be coupled with the notification category, the value carried in domain_name of the same notification.

extended EventType

event_name

The legal values carried in this attribute are specified by the IRP using the notification. For example, Alarm IRP: CORBA SS (3GPP TS 32.111-3 [7]) defines and uses the following values:

NOTIFY_FM_NEW_ALARM,

NOTIFY_FM_CHANGED_ALARM,

NOTIFY_FM_ACK_STATE_CHANGED,

NOTIFY_FM_CLEARED_ALARM and

NOTIFY_FM_ALARM_LIST_REBUILT.

It is a string. See each individual CORBA SS IDL module for each IRP using the Notification IRP, for legal values used by that IRP version.

Since each IRP except Notification IRP specifies its own set of extended event type, the values specified by each IRP are only unique within one IRP. For uniqueness among all IRPs’ specification, the values of extended event type shall be coupled with the notification category, the value carried in domain_name of the same notification.

There is no corresponding SS attribute.

variable Header

managed Object Class, managed Object Instance

One NV (name-value) pair of filterable_ body_fields

Name of NV pair is a string, NV_MANAGED_OBJECT_INSTANCE.

Value of NV pair is a string. Syntax and semantics of this string conform to the Managed Object string representation specified in (3GPP TS 32.106-8 [4]). Note that two SS attributes are carried in this one NV pair since the string representation specified in 3GPP TS 32.106-8 [4] can convey the semantics of managedObjectClass and managedObjectInstance in one string.

notificationId

One NV pair of filterable_ body_fields

Name of NV pair is a string, NV_NOTIFICATION_ID.

Value of NV pair is a long.

eventTime

One NV pair of filterable_ body_fields

Name of NV pair is a string, NV_EVENT_TIME.

Value of NV pair is an IRPTime.

systemDN

One NV pair of filterable_ body_fields

Name of NV pair is a string, NV_SYSTEM_DN.

Value of NV pair is a string. Syntax and semantics of this string conforms to the Managed Object string representation specified in 3GPP TS 32.106-8 [4].

There is no corresponding SS attribute.

remaining_ Body