5 Mapping

32.3033GPPCommon Object Request Broker Architecture (CORBA) Solution Set (SS)Configuration Management (CM)Notification Integration Reference Point (IRP)Telecommunication managementTS

5.1 Operation mapping

Notification IRP: IS (3GPP TS 32.302 [5]) defines semantics of operations visible across this IRP. These operations are the operations of the IOCs defined in 3GPP TS 32.302 [5].

Table 1 maps the operations defined in Notification IRP: IS (3GPP TS 32.302 [5]) to their equivalents (methods) in this Solution Set (SS). Specifically, the table 1 maps the operations of the IOCs defined in 3GPP TS 32.302 [5] to their equivalents in this SS. Since one of the IOCs, the NotificationIRP IOC, inherits from the ManagedGenericIRP IOC [4], the table 1 also maps the operations of ManagedGenericIRP IOC to their equivalents (methods) in this SS.

Table 1 also qualifies if a method is Mandatory (M) or Optional (O).

Table 1: Mapping from IS Operation to SS Equivalents

IS Operations in 3GPP TS 32.302 [5]

SS Methods

Qualifier

subscribe

attach_push, attach_push_b, attach_pull

M, O, O

unsubscribe

detach

M

getIRPVersion (see note.)

get_notification_irp_versions

M

getSubscriptionStatus

get_subscription_status

O

getSubscriptionIds

get_subscription_ids

O

changeSubscriptionFilter

If subscription is established using attach_push method, the SS equivalent shall be change_subscription_filter. The IDL specification of this method is included in annex A. This method is Optional (O).

If subscription is established using attach_push_b method, the SS equivalent shall be modify_constraints. The method is defined in OMG Notification Service Filter Interface (OMG TC Document telecom [2]). The IDL specification of this method is not included in annex A. If IRPAgent supports the optional attach_push_b method, it shall support this method as mandatory.

If subscription is established using attach_pull method, the SS equivalent shall be modify_constraints. The method is defined by OMG Notification Service Filter Interface (OMG TC Document telecom [2]). The IDL specification of this method is not included in annex A. If IRPAgent supports the optional attach_pull method, it shall support this method as mandatory.

See box on the left.

suspendSubscription

If subscription is established using attach_push, there is no SS equivalent. In other words, IRPManager cannot suspend subscription.

If subscription is established using attach_push_b, the SS equivalent shall be suspend_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]). The IDL specification of this method is not included in annex A. If IRPAgent supports the optional attach_push_b method, it shall support this method as mandatory.

If subscription is established using attach_pull, there is no SS equivalent.

See box on the left.

resumeSubscription

If subscription is established using attach_push, there is no SS equivalent. In other words, IRPManager cannot resume subscription.

If subscription is established using attach_push_b, the SS equivalent shall be resume_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]). The IDL specification of this method is not included in annex A. If IRPAgent supports the optional attach_push_b method, it shall support this method as mandatory.

If subscription is established using attach_pull, there is no SS equivalent.

See box on the left.

getNotificationCategories

get_notification_categories

O

getOperationProfile (see note.)

get_notification_irp_operations_profile

O

getNotificationProfile (see note.)

get_notification_irp_notification_profile

O

NOTE: These 3 operations are operations of ManagedGenericIRP IOC specified in 3GPP TS 32.312 [4]. The NotificationIRP IOC of 3GPP TS 32.302 [5] inherits from it.

5.2 Operation parameter mapping

3GPP TS 32.302 [5] defines semantics of parameters carried in operations across the Notification IRP. Table 2 through table 14 indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.

Table 2: Mapping from IS subscribe parameters to SS attach_push equivalents

IS Operation parameter

SS Method parameter

Qualifier

managerReference

string manager_reference (see note 1)

M

timeTick

ManagedGenericIRPConstDefs::UnsignedLongOpt time_tick

O

notificationCategories

NotificationIRPConstDefs::NotificationCategorySetOpt notification_categories

O

filter

ManagedGenericIRPConstDefs::StringOpt filter (see note 2)

O

subscriptionId

Return value of type NotificationIRPConstDefs::SubscriptionId

M

status

Attach, ManagedGenericIRPSystem::ParameterNotSupported, ManagedGenericIRPSystem::InvalidParameter, AlreadySubscribed, AtLeastOneNotificationCategoryNotSupported

M

NOTE 1: IRPManager creates a CosNotifyComm::SequencePushConsumer object and invokes CORBA::ORB::object_to_string to obtain the stringified IOR, say s1. IRPManager stores the s1. IRPManager sends s1 as input parameter of attach_push to IRPAgent. IRPAgent receives s1, performs CORBA::ORB::string_to_object to obtain the IRPManager’s IOR and uses it for its future methods. IRPAgent also stores the s1 for future comparisons. IRPManager later calls detach with s1. IRPAgent receives the stringified IOR s1, compares it with those stored stringified IORs (e.g. s1), finds a match, and performs the detach process. IRPAgent pushes sequence of Structured Events towards IRPManager via the CosNotifyComm::SequencePushConsumer object push_structured_events method, depending on the supplied notification categories and filter.

NOTE 2: The grammar of the filter string is extended_TCL defined by OMG Notification Service (OMG TC Document telecom [2]). This SS and the Alarm IRP: CORBA SS [10] shall use this grammar only.

Table 3: Mapping from IS subscribe parameters to SS attach_push_b equivalents

IS Operation parameter

SS Method parameter

Qualifier

managerReference

string manager_reference (see note 1)

M

timeTick

ManagedGenericIRPConstDefs::UnsignedLongOpt time_tick

O

notificationCategories

NotificationIRPConstDefs::NotificationCategorySetOpt notification_categories

O

filter

ManagedGenericIRPConstDefs::StringOpt filter (see note 2)

O

subscriptionId

Return value of type NotificationIRPConstDefs::SubscriptionId

M

Not specified in IS.

CosNotifyChannelAdmin::SequenceProxyPushSupplier system_reference (see note 3)

M

status

Attach, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::ParameterNotSupported, ManagedGenericIRPSystem::InvalidParameter, AlreadySubscribed, AtLeastOneNotificationCategoryNotSupported

M

NOTE 1: IRPManager creates a CosNotifyComm::SequencePushConsumer object and invokes CORBA::ORB::object_to_string to obtain the stringified IOR, say s1. IRPManager stores the s1. IRPManager sends s1 as input parameter of attach_push_b to IRPAgent. IRPAgent receives s1 and stores the s1 for future comparisons. IRPManager later calls detach with s1. IRPAgent receives the stringified IOR s1, compares it with those stored stringified IORs (e.g. s1), finds a match, and performs the detach process.

NOTE 2: The grammar of the filter string is extended_TCL defined by OMG Notification Service (OMG TC Document telecom [2]). This SS and the Alarm IRP: CORBA SS [10] shall use this grammar only.

NOTE 3: IRPAgent provides this reference to which IRPManager can invoke methods to manage the subscription. Valid methods are not defined in this IRP. OMG CORBA Notification Service defines these methods. Read interface CosNotifyChannelAdmin::SequenceProxyPushSupplier and CosNotifyComm::SequencePushConsumer. IRPManager is expected to invoke connect_sequence_push_consumer method of this interface to connect its own cosNotifyComm::SequencePushConsummer with this reference. After successful connection, IRPAgent pushes sequence of Structured Events towards IRPManager.

Table 4: Mapping from IS subscribe parameters to SS attach_pull equivalents

IS Operation parameter

SS Method parameter

Qualifier

managerReference

string manager_reference (see note 1)

M

timeTick

ManagedGenericIRPConstDefs::UnsignedLongOpt time_tick

O

notificationCategories

NotificationIRPConstDefs::NotificationCategorySetOpt notification_categories

O

filter

ManagedGenericIRPConstDefs::StringOpt filter (see note 2)

O

subscriptionId

Return value of type NotificationIRPConstDefs::SubscriptionId

M

Not specified in IS.

CosNotifyChannelAdmin::SequenceProxyPullSupplier system_reference (see note 3)

M

status

Attach, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::ParameterNotSupported, ManagedGenericIRPSystem::InvalidParameter, AlreadySubscribed, AtLeastOneNotificationCategoryNotSupported

M

NOTE 1: IRPManager creates a CosNotifyComm::SequencePullConsumer object and invokes CORBA::ORB::object_to_string to obtain the stringified IOR, say s1. IRPManager stores the s1. IRPManager sends s1 as input parameter of attach_pull to IRPAgent. IRPAgent receives s1 and stores the s1 for future comparisons. IRPManager later calls detach with s1. IRPAgent receives the stringified IOR s1, compares it with those stored stringified IORs (e.g. s1), finds a match, and performs the detach process.

NOTE 2: The grammar of the filter string is extended_TCL defined by OMG Notification Service (OMG TC Document telecom [2]). This SS and the Alarm IRP: CORBA SS [10] shall use this grammar only.

NOTE 3: IRPAgent provides this reference to which IRPManager can invoke methods to manage the subscription. Valid methods are not defined in this IRP. OMG CORBA Notification Service defines these methods. Read interface CosNotifyChannelAdmin::SequenceProxyPullSupplier and CosNotifyComm::SequencePullConsumer. IRPManager is expected to invoke connect_sequence_pull_consumer method of this interface to connect its own CosNotifyComm::SequencePullConsummer with this reference. After successful connection, IRPManager pulls sequence of Structured Events from IRPAgent.

Table 5: Mapping from IS unsubscribe parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

managerReference

string manager_reference

M

subscriptionId

NotificationIRPConstDefs::SubscriptionIdOpt subscription_id

O

status

DetachException, ManagedGenericIRPSystem::ParameterNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

Table 6: Mapping from IS getIRPVersion parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

versionNumberSet

Return value of type ManagedGenericIRPConstDefs::VersionNumberSet

M

status

GetNotificationIRPVersions

M

Table 7: Mapping from IS getSubscriptionStatus parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

subscriptionId

NotificationIRPConstDefs::SubscriptionId subscription_id

M

notificationCategorySet

Return value of type NotificationIRPConstDefs::NotificationCategorySet

M

filterInEffect

ManagedGenericIRPConstDefs::StringOpt filter_in_effect

O

subscriptionState

NotificationIRPConstDef::SubscriptionStateOpt subscription_state

O

timeTick

ManagedGenericIRPConstDefs::UnsignedLongOpt time_tick

O

status

GetSubscriptionStatus, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

Table 8: Mapping from IS getSubscriptionIds parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

managerReference

string manager_reference

M

subscriptionIdSet

Return value of type NotificationIRPConstDefs::SubscriptionIdSet

M

status

GetSubscriptionIds, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

Table 9: Mapping from IS changeSubscriptionFilter parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

subscriptionId

NotificationIRPConstDefs::SubscriptionId subscription_id

M

filter

string filter

M

status

ChangeSubscriptionFilter, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

Table 10: Mapping from IS suspendSubscription parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

subscriptionId

If subscription is established using attach_push, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_push_b, the SS equivalent method is suspend_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]) and requires no parameter. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_pull, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

M

status

If subscription is established using attach_push, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_push_b, the SS equivalent method is suspend_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]) and it returns a void. Therefore, there is no SS equivalent for this IS parameter. This suspend_connection method can raise OMG Notification Service (OMG TC Document telecom [2]) defined exception called ConnectionAlreadyInactive.

If subscription is established using attach_pull, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

M

Table 11: Mapping from IS resumeSubscription parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

subscriptionId

If subscription is established using attach_push, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_push_b, the SS equivalent method is resume_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]) and requires no parameter. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_pull, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

M

status

If subscription is established using attach_push, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

If subscription is established using attach_push_b, the SS equivalent method is resume_connection. This method is defined by OMG Notification Service (OMG TC Document telecom [2]) and returns a void. Therefore, there is no SS equivalent for this IS parameter. This resume_connection method can raise OMG Notification Service (OMG TC Document telecom [2]) defined exception called ConnectionAlreadyActive.

If subscription is established using attach_pull, there is no SS equivalent method. Therefore, there is no SS equivalent for this IS parameter.

M

Table 12: Mapping from IS getNotificationCategories parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

notificationCategoryList

Return value of type NotificationIRPConstDefs::NotificationCategorySet

M

Not specified in IS.

NotificationIRPConstDefs::NotificationTypesSetOpt notification_type_list

O

status

GetNotificationCategories, ManagedGenericIRPSystem::OperationNotSupported

M

Table 13: Mapping from IS getOperationProfile parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

iRPVersion

ManagedGenericIRPConstDefs::VersionNumber notification_irp_version

M

operationNameProfile, operationParameterProfile

Return of type ManagedGenericIRPConstDefs::MethodList

M

status

GetNotificationIRPOperationsProfile, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

Table 14: Mapping from IS getNotificationProfile parameters to SS equivalents

IS Operation parameter

SS Method parameter

Qualifier

iRPVersion

ManagedGenericIRPConstDefs::VersionNumber notification_irp_version

M

notificationNameProfile, notificationParameterProfile

Return value of type ManagedGenericIRPConstDefs::MethodList

M

status

GetNotificationIRPNotificationProfile, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter

M

5.3 Notification parameter mapping

Notification IRP: IS (3GPP TS 32.302 [5]) defines the semantics of common attributes carried in notifications. This SS does not provide the mapping of these attributes to their CORBA SS equivalents. Other IRPs such as Alarm IRP: IS (3GPP TS 32.111-2 [6]) identify and qualify these common attributes for use in their environment. Their corresponding SS documents define the mapping of these attributes to their SS equivalents.