TS 32.106-2
Telecommunication Management –
Configuration Management (CM);
Part 2: Notification Integration Reference Point (IRP):
Information Service (IS)
V3.3.0 (PDF)
2001/04 19 p.
- Rapporteur:
- Mr. Tovinger, Thomas
full Table of Contents for TS 32.106-2 Word version: 3.3.0
0 Introduction p. 4
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality Of Service (QOS). The CM actions are initiated either as a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs.
The Itf-N interface for Configuration Management (CM) 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 TS 32.101 and TS 32.102. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other specifications for Telecom Management produced by 3GPP. All these are included in 3GPP TS 32.106 from Part 2 and onwards.
The present document is Part 2 of 3GPP TS 32.106 (TS 32.106-2) - Notification IRP Information Service.
1 Scope p. 5
Network Elements (NEs) under management generate events to inform event receivers about occurrences within the network that may be of interest to event receivers. There are a number of categories of events. Alarm, as specified in Alarm IRP: Information Service TS 32.111-2, is one member of this category.
The purpose of Notification IRP is to define an interface through which an IRPManager (typically a network management system) can subscribe to IRPAgent (typically an Element Manager (EM) or a NE) for receiving network events. It also specifies attributes carried in the network events. These attributes are common among all event categories. Attributes that are specific to a particular event category are not part of the present document. For example, perceivedSeverity is an attribute specific for alarm event category. This attribute is not defined the present document but in Alarm IRP TS 32.111-2.
2 References p. 5
3 Definitions and abbreviations p. 6
3.1 Definitions p. 6
3.2 Abbreviations p. 6
4 System overview p. 7
5 Modelling approach p. 8
6 IRP Information Service p. 8
6.1 Interfaces p. 8
6.1.1 NotificationIRPOperation Interface p. 9
6.1.1.1 Operation subscribe (M) p. 9
6.1.1.2 Operation unsubscribe (M) p. 10
6.1.1.3 Operation getNotificationIRPVersion (M) p. 10
6.1.1.4 Operation getSubscriptionStatus (O) p. 11
6.1.1.5 Operation getSubscriptionIds (O) p. 11
6.1.1.6 Operation changeSubscriptionFilter (O) p. 12
6.1.1.7 Operation suspendSubscription (O) p. 12
6.1.1.8 Operation resumeSubscription (O) p. 12
6.1.1.9 Operation getNotificationCategories (O) p. 12
6.1.2 NotificationIRPNotification Interface p. 13
6.1.3 Behaviour p. 15
$ Change history p. 17
