4 Basic aspects

32.106-43GPPCommon Management Information Protocol (CMIP) Solution Set (SS)Configuration Management (CM)Part 4: Notification Integration Reference Point (IRP)Telecommunication managementTS

The present document defines all the GDMO and ASN.1 definitions necessary to implement the Notification IRP Information Service for the CMIP interface. The definitions provided in the present document are the base to implement any other IRP that includes event reporting and/or management of event reporting.

The terms “manager/agent” are applied in the present document to mean “IRP Manager/IRP Agent” introduced in 3GPP TS 32.106-2 [3].

4.1 Architectural aspects

This CMIP Notification IRP is based, as much as possible, on the ITU-T TMN architecture, as defined through the ITU-T X.700 Recommendations series.

4.1.1 Notifications

The Notifications messages are sent from the Agent to the Manager using the CMISE service M-EVENT-REPORT, defined in ITU-T Recommendation X.710 [5] and ITU-T Recommendation X.711 [6].

Any object of the Agent that sends a specific notification to the Manager needs to have, in its Managed Object Class (MOC) Definition, the GDMO definition of that specific “Notification” and the supporting ASN.1 syntax definition. The present document does not define any specific Notification. The specific Notifications are defined in other “CMIP IRP Solution Sets”, as necessary (e.g. the alarm notifications are defined in CMIP Alarm IRP Solution Set).

4.1.2 Event reporting management

In the higher level (protocol independent) description of the Notification IRP Information Service, the event reporting is managed (by the Manager) by means of several operations: subscribe, unsubscribe, suspend, resume subscription, change filter, etc. Most of these operations require the “subscription identifier” parameter to easy the handling of multiple subscriptions.

In the ITU-T TMN architecture the event reporting is managed by means of the MOC Event Forwarding Discriminator (EFD), which is instantiated on the Agent and is controlled by the Manager, by means of CMISE services (M-CREATE, M-SET, etc.). There is no attribute in the EFD that corresponds to the “subscription identifier”.

The mapping between the operations defined in the Notification IRP Information Service and the CMISE services applicable to the EFD is not one-to-one, therefore a mediation function is necessary. This mediation function can be located on the Manager or on the Agent. In the first case, the Manager should translate the subscription-related operations in a sequence of one or more CMISE services, it should assign a subscription identifier and it should handle the mapping between the subscription identifier and the EFDs.

In the second case this mediation is performed by the Agent and is based on the following points:

  • A new MOC (i.e. notificationControl) is defined to be instantiated on the IRP Agent. This MOC has the purpose to implement the operations defined in Notification IRP Information Service and to interact with the local EFD(s). The operations are implemented as Actions. There is a one-to-one mapping between the operations and the Actions.
  • The EFD defined in ITU-T Recommendation X.734 [10] and ITU-T Recommendation X.721 [7] is used for event reporting, however this EFD shall be controlled by the agent. In other words, it shall be created/deleted and its attributes shall be managed by the Agent, via notificationControl MOI.
  • The Manager shall interact with notificationControl MOI located on the IRP Agent to execute the subscription related Actions. It is responsibility of the notificationControl MOI to assign the “subscription identifier” and to handle the correspondence between the subscription identifiers, the EFDs and the discriminatorConstruct associated to each subscription.
    It is not required that the Manager controls directly the EFD by means of CMISE services.

The second alternative is chosen. The rest of this Solution Set (SS) is based on this choice.

4.1.3 Subscription related operations

The operation that allows the Manager to receive notifications from the Agent is subscribe.

The IRP concept foresees in different operations a parameter subscriptionId, which is generated by the Agent as response to a subscribe request and unambiguously identifies a Manager subscription in the scope of the whole Agent. Therefore the Agent is required to maintain at any time a table of correspondence between every subscription and the related EFD instance.

When the forwarding of some notifications is not needed any more, the Manager may invoke an unsubscribe operation. In this case one or all subscriptions available for this Manager are cancelled, e.g. the Agent may implicitly delete also the related EFD instance(s).

The creation and deletion of EFD instances on the Manager-Agent interface is therefore "encapsulated", i.e. in the CMIP Solution Set the standardised M-CREATE and M-DELETE services (defined in ITU-T Recommendation X.710 [5] and ITU-T Recommendation X.711 [6]) are not directly used for the EFD management.

Note that only the mandatory EFD attributes (destination and filter, according to ITU-T Recommendation X.721 [7]) are supported by the subscribe operation.

To suspend/resume the forwarding of the notification towards a manager, the subscribed Manager shall use the suspendSubscription/resumeSubscription actions of notificationControl. These actions result in locking/unlocking the administrative state of the related EFD.

To change the filtering constraints associated to a subscription, the subscribed Manager shall use the changeSbscriptionFilter action of notificationControl. This action results in a change of the discriminatorConstruct of the related EFD.

4.2 Mapping

The semantics of the Notification IRP is defined in 3GPP TS 32.106-2 [3]. The definitions of the management information defined there are independent of any implementation technology and protocol. This clause maps these protocol independent definitions onto the equivalencies of the CMIP solution set of Notification IRP.

4.2.1 Mapping of Operations

Table 1 maps the operations defined in the Notification IRP Information Service onto the equivalent Actions of the CMIP Solution Set. The CMIP Actions are qualified as Mandatory (M) or Optional (O).

The CMIP Actions are based on he M-ACTION service of CMISE, defined in ITU-T Recommendation X.710 [5] and ITU-T Recommendation X.711 [6]).

Table 1: Mapping of Operations

Operations of Information Services of the Notification IRP

Equivalent GDMO Actions of the CMIP solution set for the Notification IRP

Qualifier

changeSubscriptionFilter

changeSubscriptionFilter

O

getNotificationCategories

getNotificationCategories

O

getNotificationIRPVersion

getNotificationIRPVersion

M

getSubscriptionIds

getSubscriptionIds

O

getSubscriptionStatus

getSubscriptionStatus

O

resumeSubscription

resumeSubscription

O
Implemented if ‘suspend-Subscription’ is implemented.

subscribe

subscribe

M

suspendSubscription

suspendSubscription

O
Implemented if ‘resume-Subscription’ is implemented.

unsubscribe

unsubscribe

M

4.2.2 Mapping of operation parameters

The tables in the following subclauses shows the parameters of each operations defined in the Information Service described in TS 32.106-2 and their equivalence in the CMIP solution set of the Notification IRP.

The input parameters of the operations defined in TS 32.106-2 are mapped into “Action information” (see GDMO and ASN.1 definitions for more details).

The output parameters of the operations defined in TS 32.106-2 are mapped into “Action response” (see GDMO and ASN.1 definitions for more details).

4.2.2.1 Mapping of Parameters of ‘subscribe’

Table 2: Mapping of Parameters of ‘subscribe’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

managerReference

managerReference

M

timeTick

timeTick

O

notificationCategories

notificationCatagoryList

O

filter

filter

O

subscriptionId

subscriptionId

M

status

status

M

no equivalence

destination

This information indicates a manager application which is designated to receive the concerned event reports issued by the related agent and is used to create the required EFD in the agent. It can be mapped onto the interface “notify” defined in the Information Service of the Notification IRP.

M

4.2.2.2 Mapping of Parameters of ‘unsubscribe’

Table 3: Mapping of Parameters of ‘unsubscribe’

Operation parameters of the Information Services.

CMIP Solution Set equivalencies

Qualifier

managerReference

managerReference

M

subscriptionId

subscriptionId

M

status

status

M

4.2.2.3 Mapping of Parameters of ‘getNotificationIRPVersion’

Table 4: Mapping of Parameters of ‘getNotificationIRPVersion’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

versionNumberList

versionNumberList

M

status

status

M

4.2.2.4 Mapping of Parameters of ‘getSubscriptionStatus’

Table 5: Mapping of Parameters of ‘getSubscriptionStatus’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

subscriptionId

subscriptionId

M

notificationCategoryList

notificationCategoryList

M

filterInEffect

filterInEffect

M

subscriptionStatus

subscriptionStatus

O

timeTick

timeTick

O

status

status

M

4.2.2.5 Mapping of Parameters of ‘changeSubscriptionFilter’

Table 6: Mapping of Parameters of ‘changeSubscriptionFilter’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

subscriptionId

subscriptionId

M

filter

filter

M

status

status

M

4.2.2.6 Mapping of Parameters of ‘suspendSubscription’

Table 7: Mapping of Parameters of ‘suspendSubscription’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

subscriptionId

subscriptionId

M

status

status

M

4.2.2.7 Mapping of Parameters of ‘resumeSubscription’

Table 8: Mapping of Parameters of ‘resumeSubscription’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

subscriptionId

subscriptionId

M

status

status

M

4.2.2.8 Mapping of Parameters of ‘getNotificationCategories’

Table 9: Mapping of Parameters of ‘getNotificationCategories’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

notificationCategoryList

notificationCategoryList

M

extendedEventTypeList

there is no equivalence in the CMIP solution set!

status

status

M

4.2.2.9 Mapping of Parameters of ‘getSubscriptionIds’

Table 10: Mapping of Parameters of ‘getSubscriptionIds’

Operation parameters of the Information Services.

CMIP Solution Set equivalences

Qualifier

managerReference

managerReference

M

subscriptionIdList

subscriptionIdList

M

status

status

M

4.3 Mapping of common notification parameters

The following table gives the mapping between the common parameters of TS 32.106-2 onto the common parameters of M-EVENT-REPORT

Table 11: Mapping of common notification parameters

Common Parameters

M-EVENT-REPORT Parameters

Qualifier

(see NOTE 1)

Invoke identifier

M

ManagedObjectClass

Managed object class

M

ManagedObjectInstance

Managed object instance

M

NotificationId

(see NOTE 2)

EventType

Event type (see NOTE 3)

M

ExtendedEventType

EventTime

Event time

M

SystemDN

(see NOTE 4)

NOTE 1: There is no common parameter in IRP Notification that corresponds to Invoke Identifier defined in [5].

NOTE 2: The common parameter NotificationId is mapped onto notificationIdentifier ([7] [9]) which is not part of the M-EVENT-REPORT header, indeed it is one of the parameters of the event information.

NOTE 3: The common parameters EventType and ExtendedEventType are condensed in one parameter (Event type) of the M-EVENT-REPORT header.

NOTE 4: The common parameter SystemDN is conditional in TS 32.106-2 and is not used on the CMIP interfaces.