4 System overview

32.106-23GPPConfiguration Management (CM)Part 2: Notification Integration Reference Point (IRP): Information Service (IS)Telecommunication managementTS

4.1 System context for Notification

Figure 1 and Figure 2 identify System contexts of Notification IRP in terms of implementations called IRPAgent and IRPManager.

“IRPManager” depicts a process that interacts with IRPAgent for the purpose of receiving network Notifications via this IRP. IRPAgent detects network events. IRPAgent sends IRPManagers notifications carrying the events. Examples of IRPManagers can be a process running supporting network Notification logging device or supporting network Notification viewing devices (such as a local craft terminal) or a process running within a Network Manager (NM) as shown in Figure 1 and Figure 2. IRPAgent implements and supports this IRP. IRPAgent can run within one Element Manager (EM) with one or more NEs (see Figure 1) or run within one NE (see Figure 2). In the former case, the interfaces (represented by a thick dotted line) between the EM and the NEs are not subject of this IRP. Whether EM and NE share the same hardware system is not relevant to this IRP either. By observing the interaction across the IRP, one cannot deduce if EM and NE are integrated in a single system or if they run in separate systems.

NEs

Itf-N

EM

IRPAgent

IRPManager

NM

Notification IRP

Figure 1: System Context A

Itf-N

NE

IRPAgent

IRPManager

NM

Notification IRP

Figure 2: System Context B

This interface supports the following implementation strategies.

  • One IRPAgent supports emission of different categories of Notifications, such as alarms (as specified in 3GPP TS 32.111-2 [1]) and others.
  • One IRPAgent supports emission of one specific category of Notification. For example, one IRPAgent implementation only emits alarms specified in 3GPP TS 32.111-2 [1]. Another IRPAgent implementation emits configuration status change notifications.
  • IRPManager can specify the categories of notifications it wants to receive using subscribe operation. In the case IRPManager does not specify the notification category in subscribe, IRPAgent will then emit all categories of notifications that IRPAgent handles. This implementation is SS dependent.
  • IRPManager can query the categories of notification supported by IRPAgent. This implementation is Solution Set (SS) dependent.

The Notification IRP defines attributes, carried in notifications that are common in all categories of notifications.

Attributes specific to a particular category of notification shall be specified in corresponding IRP (such as Alarm IRP IS – see 3GPP TS 32.111-2 [1]) using the Notification IRP. Those IRP also define the protocol interaction via which IRPManager receives the notifications.