Content for TS 32.301 Word version: 16.0.0
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements.
32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS).
32.306: Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions.
The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101
and TS 32.102
Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service , is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service  is another possible kind of event.
Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to IRPAgent for receiving notifications.
This IRP bases its design on work captured in ITU-T Recommendation X.734 , OMG Notification Service . The central design ideas are:
Separation of notification Consumers (IRPManagers) from Producers (IRPAgents);
Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications.
Common characteristics related to notifications in all other IRPs are gathered in one IRP.
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Requirements" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
: "Telecommunication management; Principles and high level requirements".
: "Telecommunication management; Architecture".
: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
ITU-T Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function".
OMG: "OMG Notification Service".
For the purposes of the present document, the following terms and definitions apply:
Element Manager (EM):
Network Manager (NM):
For the purposes of the present document, the following abbreviations apply:
Common Object Request Broker Architecture
Integration Reference Point
International Telecommunication Union - Telecommunication
Management Information Base
Object Management Group
Universal Mobile Telecommunications System
The IRPAgent shall provide IRPManagers with the capabilities to subscribe and unsubscribe to the notification mechanism. An IRPManager shall be able to specify the types of notifications IRPAgent should emit to IRPManager during subscription, to specify filtering criteria that shall be applied by the notification mechanism. An IRPManager shall be able to subscribe several times in order to include in a subscription different types of notifications. An IRPManager shall also be able to request multiple subscriptions, which is equivalent, from the IRPAgent perspective, to multiple IRPManagers each providing one subscription.
The IRPAgent may provide to IRPManagers capabilities to control its subscriptions. An IRPManager may then be able to check whether its subscription is still active or not, to know the details of a particular subscription and to know the list of all subscriptions it has opened.
In principle, notifications are forwarded to the IRPManagers as soon as they are available. The real-time forwarding of these notifications occurs via appropriate filtering mechanisms ("discriminators" on CMIP interfaces, "subscription" on CORBA interfaces) in accordance with ITU-T Recommendation X.734  or OMG event/notification service. Any IRPManager may be able to set and change filter criteria applicable during the life-cycle of one if its subscriptions in order to ensure that only the notifications which fulfil pre-defined criteria are sent. An IRPManager may also be able to enable and disable the emission of notifications corresponding to its subscriptions.
The IRPAgent may provide IRPManagers with a capability to discover the IRPs supported by the IRPAgent that are capable of sending notifications through the notification IRP. Those IRPs shall be identified with their version.
Notifications are emitted by the notification IRP. Those notifications can be defined in any other IRP (e.g. a notification for a new alarm as specified in TS 32.111-2
Alarm IRP: Information Service). It is required that all notifications emitted by the notification IRP support the same header that contains enough information to identify the type of notification, the resource at the origin of the notification and the time of the notification.