4.7 System context for Interface IRPs

32.1503GPPIntegration Reference Point (IRP) Concept and definitionsRelease 17Telecommunication managementTS

Every Interface IRP on a management interface (e.g. Alarm IRP, Notification IRP, Basic CM IRP, Bulk CM IRP) is subject to a System Context as described in this subclause (also consistent with 3GPP TS 32.102 [2] clause 8).

Figure 4.7.1 and 4.7.2 identify system contexts of the Interface IRP in terms of its implementation, called IRPAgent, and the user of the IRPAgent, called IRPManager.

Each IRPAgent implements and supports one or more IRPs. The set of IRPs that is related to each Interface IRP is defined by the System Context subclause in each individual Interface IRP IS specification, e.g. subclause 4.2 in the Alarm IRP IS [7].

An NE can be managed via System Context A or B. The criterion for choosing System Context A or B to manage a particular NE is implementation dependent. An IRPAgent shall support one of the two System Contexts. By observing the interaction across the management interface, an IRPManager cannot deduce if the EM and NE are integrated in a single system or if they run in separate systems.

Figure 4.7.1: System Context A

Figure 4.7.2: System Context B

An entity can play the consumer role for some operations/notifications and the producer role for other operations/notifications of the same Interface IRP. A diagram shall contain the direction of the operations and notifications per operation and notification.

Examples of when the entities can play the role of both consumer and producer are depicted in Figures 4.7.3.

Figure 4.7.3: Example for entities that can have several roles