Method for tracking and utilizing operational run time of a network element

• US 9,451,482 B2
• Filed: 12/10/2013
• Issued: 09/20/2016
• Est. Priority Date: 03/15/2013
• Status: Expired due to Fees

• Current Assignee: Nokia Solutions and Networks US LLC (Nokia Corporation)
• Original Assignee: Nokia Solutions and Networks US LLC (Nokia Corporation)
• Inventors: Ryan, David James, Gormley, Eamonn
• Primary Examiner(s): Ngo, Ricky
• Assistant Examiner(s): Ng, Christine
• Application Number:
  US14/102,317
• Publication Number:
  US 20140269382A1
• Time in Patent Office: 1,015 Days
• Field of Search: 370/252, 370/328, 370/338, 370/401
• US Class Current: 1/1
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition

Abstract

Techniques for normalizing a performance metric in a wireless communication network include collecting operation data of a network element over a plurality of data collection time periods, determining operational run time of the network element based on the operation data, calculating a normalization value based on the operational run time, and normalizing the performance metric for the network element using the normalization value.

Claims

1. A system for normalizing a performance metric in a wireless communication network, the system comprising:

a memory;

a processor; and

a non-transitory computer readable medium associated with the processor, the computer readable medium having computer executable instructions stored thereon which, when executed by the processor, perform the following steps;

collecting operation data of a network element over a plurality of data collection time periods;

determining operational run time of the network element based on the operation data, the operational run time corresponding to an amount of time the network element is operational;

calculating a normalization value based on the operational run time; and

normalizing the performance metric for the network element using the normalization value,

wherein the normalized performance metric is used as a performance metric for the network element in an automated network optimization process.

2. The system of claim 1, wherein the operation data is chosen from performance data and configuration data.

3. The system of claim 2, wherein the performance data is chosen from a connection activity metric and a data throughput metric.

4. The system of claim 2, wherein the configuration data is collected from a configuration management system, an alarm management system, or both.

5. The system of claim 1, wherein the instructions executed by the processor further include aligning first operation data with second operation data in time.

6. The system of claim 5, wherein aligning the first operation data with the second operation data in time includes interpolation or decimation to match a periodicity of the first operation data to a periodicity of the second operation data.

7. The system of claim 1, wherein determining operational run time of the network element includes determining an operational status for each data collection time period in the plurality of data collection time periods.

8. The system of claim 7, wherein determining operational status for each data collection period includes:

receiving data indicating a locked state or an unlocked state for each collection time period from a configuration management system;

designating a first collection time period as non-operational when the data for the first collection time period indicates a locked state; and

designating a second collection time period as operational when the data for the first collection time period indicates an unlocked state.

9. The system of claim 7, wherein determining operational status for each data collection period includes:

receiving performance data values for the plurality of data collection time periods;

comparing each performance data value to a threshold value;

when a compared performance data value is less than the threshold value, designating a time period associated with the compared performance metric data as non-operational; and

when the compared performance data value is more than the threshold value, designating the time period associated with the compared performance metric data as operational.

10. The system of claim 1, wherein the instructions executed by the processor further include weighting the normalized performance metric according to a weighting factor based on at least the time of day in which the operational run time was determined.

11. The system of claim 1, wherein the instructions executed by the processor further include:

determining whether the network element was introduced during a reporting interval with a duration exceeding a threshold value;

when the network element is introduced during the reporting interval with a duration exceeding the threshold value, reporting the normalized performance metric for the network element during the reporting interval exceeding the threshold value.

12. A method for normalizing a performance metric in a wireless communication network, the method comprising:

collecting operation data of a network element over a plurality of data collection time periods;

determining operational run time of the network element based on the operation data, the operational run time corresponding to an amount of time the network element is operational;

calculating a normalization value based on the operational run time; and

normalizing the performance metric for the network element using the normalization value; and

using the normalized performance metric as a performance metric for the network element in an automated network optimization process.

13. The method of claim 12, wherein the operation data is chosen from performance data and configuration data,

the performance data is chosen from a connection activity metric and a data throughput metric, and

the configuration data is collected from a configuration management system, an alarm management system, or both.

14. The method of claim 12, wherein the instructions executed by the processor further include aligning first operation data with second operation data in time, and

wherein aligning the first operation data with the second operation data in time includes interpolation or decimation to match a periodicity of the first operation data to a periodicity of the second operation data.

15. The method of claim 12, wherein determining operational run time of the network element includes determining an operational status for each data collection time period in the plurality of data collection time periods, and wherein determining operational status for each data collection period includes:

receiving data indicating a locked state or an unlocked state for each collection time period from a configuration management system;

designating a first collection time period as non-operational when the data for the first collection time period indicates a locked state; and

designating a second collection time period as operational when the data for the first collection time period indicates an unlocked state.

16. The method of claim 12, wherein determining operational run time of the network element includes determining an operational status for each data collection time period in the plurality of data collection time periods, and wherein determining operational status for each data collection period includes:

receiving performance data values for the plurality of data collection time periods;

comparing each performance data value to a threshold value;

when a compared performance data value is less than the threshold value, designating a time period associated with the compared performance metric data as non-operational; and

when the compared performance data value is more than the threshold value, designating the time period associated with the compared performance metric data as operational.

17. The method of claim 12, wherein the instructions executed by the processor further include weighting the normalized performance metric according to a weighting factor based on at least the time of day in which the operational run time was determined.

18. The method of claim 12, wherein the instructions executed by the processor further include:

determining whether the network element was introduced during a reporting interval with a duration of at least six hours;

when the network element is introduced during the reporting interval with a duration of at least six hours, reporting the normalized performance metric for the network element during the reporting interval of at least six hours.

19. The method of claim 12, wherein collecting the operation data includes at least one of receiving a plurality of first signals indicating performance data from a performance reporting system, and receiving a plurality of second signals indicating a configuration status from a configuration management system.

20. A non-transitory computer readable medium with computer executable instructions stored thereon which, when executed by a processor, perform the following steps:

collecting operation data of a network element over a plurality of data collection time periods;

determining operational run time of the network element based on the operation data, the operational run time corresponding to an amount of time the network element is operational;

calculating a normalization value based on the operational run time; and

normalizing the performance metric for the network element using the normalization value,

wherein the normalized performance metric is used as a performance metric for the network element in an automated network optimization process.