Introduction

32.3853GPPPartial Suspension of Itf-N Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definitionTelecommunication managementTS

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.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

32.385: Partial Suspension of Itf-N Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition

The Itf-N interface is built up by a number of 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 [1] and TS 32.102 [2].

Information of an event is carried in a notification. An IRPAgent (typically an EM or a NE) emits notifications (see TS 32.302 [3]. The IRPManager (typically a Network Management System) receives notifications. In certain scenarios floods of unwanted notifications including alarms would 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.