5 Interface IRPs
32.1033GPPIntegration Reference Point (IRP) overview and usage guideRelease 17Telecommunication managementTS
5.1 Interface IRP Overview
Figure 5.1-1: 3GPP Interface IRPs
5.2 Generic/Common Interface IRPs
Notification IRP – 32.300 [25], 32.301 [68], 32.302 [69], 32.306 [70]
The purpose of the Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications, manage these subscriptions, and optionally set filters.
Generic IRP – 32.311 [71], 32.312 [72], 32.316 [73]
This IRP defines common services supported by all IRPs such as AlarmIRP. With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP.
5.3 FM related interface IRPs
Alarm IRP – 32.111-1 [22], 32.111-2 [63], 32.111-6 [64]
The Alarm (IRP) addresses the alarm surveillance aspects of Fault Management (FM), applied to Itf-N. It defines alarm semantics & syntax as well as alarm management related operations and notifications.
Advanced Alarm Management IRP – 32.121 [65], 32.122 [66], 32.126 [67]
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system’s client and it also specifies the semantics of the interactions used to carry this information.
Test management IRP – 32.321 [74], 32.322 [75], 32.326 [76]
The purpose of the Test management IRP is to define an interface through which an IRPManager can manage and monitor tests in NE’s, as well as methods to receive test results.
5.4 CM related interface IRPs
Basic CM IRP – 32.600 [32], 32.601 [7], 32.602 [8], 32.603 [9], 32.606 [124]
Using this IRP, an IRPAgent can communicate basic Configuration Management related information to one or several IRPManagers. The function of this Basic CM IRP Information Service is to define an interface for the retrieval and modification of Configuration Management Information.
Bulk CM IRP – 32.611 [125], 32.612 [126], 32.616 [127]
Using the Bulk CM IRP an IRPAgent can communicate CM related information to one or several IRPManagers using bulk data transfer mehods.
– BulkCM SimpleUpload, enabling upload of resource information by the IRPManager without explicit session control
– BulkCM Controlled Upload, enabling a session controlled upload of resource information by the IRPManager
– BulkCM Controlled Upload & Provisioning, enabling a session controlled upload and provisioning of resource information by the IRPManager
Kernel CM IRP – 32.661 [134], 32.662 [135], 32.666 [136]
The function of this Kernel CM IRP Information Service is to define an interface that provides essential CM notification services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capabilities, the Kernel CM IRP is expected to provide the common supporting CM notifications required for other CM IRPs such as the Basic CM IRP or the Bulk CM IRP, each of which require the Kernel CM IRP.
5.5 PM file format/collection & Trace related Interface IRPs
Performance Management IRP – 32.410 [100], 32.411 [101], 32.412 [102], 32.416 [103]
The Performance Management IRP defines an interface through which an IRPManager can manage measurement jobs as well threshold values.
Performance Measurement collection – 32.432 [107], 32.435 [108], 32.406 [109]
The Performance Measurement collection specifications describe the general semantics of performance measurement result and collection. They define the report file format, report file conventions and the file transfer procedure.
Trace Management IRP – 32.441 [38], 32.442 [110], 32.446 [111]
The Trace Management IRP is defines an interface through which an IRPManager can activate and manage equipment and subscriber trace jobs.
5.6 Special-purpose related Interface IRPs
Notification Log IRP – 32.331 [77], 32.332 [78], 32.336 [79]
The purpose of the Notification Log IRP is to define an interface through which an IRPManager can manage a Notification Log, as well as methods for retrieval of logged notifications.
File Transfer IRP – 32.341 [80], 32.342 [81], 32.346 [82]
The purpose of the File Transfer IRP is to define a generic tools set supporting the management of file transfers between IRPManager and IRPAgent. Curently the following management data types are supported by this IRP:
– performance data files
– configuration & inventory files
– test result files
– call trace files
– notification log files
– charging files
Communication Surveillance IRP – 32.351 [83], 32.352 [84], 32.356 [85]
The purpose of the Communication Surveillance IRP is to provide an IRPManager with the capability to monitor the health of the communications link towards an IRPAgent.
Entry Point IRP – 32.361 [86], 32.362 [87], 32.366 [88]
The purpose of the Entry Point IRP is to provide an IRPManager with discovery and entry point capabilities towards an IRPAgent and its supported IRPs.
Partial Suspension of Itf-N IRP – 32.381 [89], 32.382 [90], 32.386 [91]
The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
Delta synchronization IRP – 32.391 [92], 32.392 [93], 32.396 [94]
The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data that have changed (i.e. changed, were created or deleted) from a synchronization point onwards.
5.7 SON related Interface IRPs
Self-Configuration IRP – 32.500 [27], 32.501 [36], 32.502 [117], 32.506 [118]
The Self-Configuration provides methods to allow automatic configuration of eNBs, which are brought newly into a network.
Software Management IRP – 32.531 [121], 32.532 [122], 32.536 [123]
The Software Management IRP provides an IRPManager with capabilities to automate software management via Itf-N.