tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 32.302 (SA5)
Configuration Management (CM) – Notification IRP – Information Service (IS)

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    29 p.
(P) V13.0.0    2016/01    29 p.
(P) V12.0.0    2014/10    29 p.
(P) V11.1.0    2012/12    29 p.
(P) V10.0.0    2010/10    29 p.
(P) V9.0.0    2009/12    29 p.
(P) V8.0.0    2008/12    29 p.
(P) V7.0.0    2007/06    29 p.
(P) V6.3.0    2006/03    27 p.
(P) V5.2.0    2005/01    27 p.
(P) V4.2.0    2003/06    26 p.

Rapporteur:  Mr. Tse, Edwin
See also:  –

The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This TS is the "Information Service" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.

An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Service) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).

Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".

Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.

This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in this TS but in Alarm IRP: Information Service.

How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of this TS.


Here          Top



1   Scope   PDF-p. 7
2   References
3   Definitions and abbreviations   PDF-p. 8
4   System overview   PDF-p. 9
5   Information Object Classes   PDF-p. 10
6   Interface Definition   PDF-p. 15
6.1   Class diagram representing interfaces
6.2   Generic rules
6.3   notificationIRPManagement Interface (M)   PDF-p. 16
6.4   subscriberManagement Interface (O)
6.5   subscriptionStatusOperations Interface (O)      Up
6.6   subscriptionFilterOperations Interface (O)
6.7   subscriptionSuspendOperations Interface (O)
6.8   IRPManagementOperations Interface (O)   PDF-p. 24
6.9   NotificationIRPNotification Interface   PDF-p. 25
A   Change history   PDF-p. 27      Up

Up          Top