Introduction

32.3833GPPCommon Object Request Broker Architecture (CORBA) Solution Set (SS)Partial Suspension of Itf-N Integration Reference Point (IRP)Telecommunication managementTS

The present document is part 3 of a multi-part TS covering the 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication Management; Partial Suspension of Itf-N Integration Reference Point (IRP), as identified below:

32.381: "Partial Suspension of Itf-N Integration Reference Point (IRP); Requirements".

32.382: "Partial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS)".

32.383: "Partial Suspension of Itf-N Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)".

32.385: Partial Suspension of Itf-N Integration Reference Point (IRP); eXtensible Markup Language (XML) 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 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].

Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications (see 3GPP TS 32.302 [3]. IRPManager (typically a network management system) receives notifications. In certain scenarios floods of unwanted notifications including alarms will be sent to the IRP manager by network object instances. Thereby the interface and the management systems bear unnecessary load. Even worse: The operator’s awareness is drawn away from really urgent events.