Browse Prior Art Database

Autonomic Network Performance Management System providing Efficient Data Collection Disclosure Number: IPCOM000192206D
Original Publication Date: 2010-Jan-20
Included in the Prior Art Database: 2010-Jan-20
Document File: 4 page(s) / 102K

Publishing Venue



A method and apparatus for network management is described. In one embodiment, a method comprises collecting performance data having accompanying meta data including information defining the performance management data and information indicating operations to be performed on the performance management data, and generating output data for display using collected performance management data according to the information indicating the operations to be performed on the performance management data.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 37% of the total text.

Page 1 of 4

Autonomic Network Performance Management System providing Efficient Data Collection

Network Terminology used:

Southbound: incoming performance data
Southbound Interface: Sub-component of the Performance Management application responsible for collecting performance data
Northbound: outgoing performance data, for example in the form of a user report (for example, a table or a chart displayed on a computer screen), automated report, or export from the performance management system to an external system (for example Service Quality Management, Network Optimisation Management). Downstream system: System providing performance data to the Performance Management application, i.e. to its southbound interface
KPI: Key Performance Indicator. Each network equipment (node, link, ...) can expose many of them. For wireless networks, such KPIs include "traffic", "connection attempts", "dropped calls", ...

Data Collection Rate (or interval): Rate at which each KPI is collected, i.e. if "dropped calls" is collected every 15 minutes, the data collection rate (or interval) for this KPI is 15 minutes.

OSS: Operations Support System
EMS: Element Management System
Network Entity: An device or network apparatus observed from a performance perspective

    As computer networks and network elements have become more complex over the years, their management has also become extremely complex.

    Nowadays, it is not sufficient to state if a network element or link between elements is "up" as opposed to "down". The performance of each network element and link between elements needs to be assessed in order to provide a complete view of the network. In order to assess performance, KPIs (Key Performance Indicators) are used.

    KPIs can include items such as "equipment temperature" to "traffic" and "dropped calls". In Wireless networks, it is very common for a single element to offer several thousand such KPIs. As many different network elements can constitute the complete network, the total domain of available KPIs can very quickly reach tens of thousand to hundreds of thousand KPIs, each collected per network element and for each time interval (in general, every 5 to 15 minutes).

    Network Performance Management applications collect all these KPIs for each monitored network element on a periodical basis (e.g. every hour, every 15 minutes etc.).

    This collection can very quickly lead to billions of KPIs to monitor, on a daily basis.

    The multiplication of KPIs can therefore mean that a very large computer will be needed in order to collect, store, manage and report on this amount of data.

    The importance of this problem is highlighted by the existence of several patents in this domain. However, none of these patents address the fact that most of the collected data will actually never be reported on, exported or otherwise used, thereby increasing the solution total...