Patent Application
20230126716
The present application generally relates to automated communication network monitoring.
This section illustrates useful background information without admission of any technique described herein representative of the state of the art.
Cellular communication networks comprise a plurality of cells serving users of the network. When users of the communication network move in the area of the network, connections of the users are seamlessly handed over between cells of the network.
In order to provide good quality of service for users of the network, different parts of the network need to operate as intended. Network operators constantly monitor operation of the network to be able to identify and fix any problems without delay. There are various automatic monitoring methods for this purpose.
Now a new automatic monitoring method is provided.
Various aspects of examples of the invention are set out in the claims. Any devices and/or methods in the description and/or drawings which are not covered by the claims are examples useful for understanding the invention.
According to a first example aspect of the present invention, there is provided a computer implemented method of monitoring operation of a communication network for the purpose of controlling the communication network. The method comprises
In an example embodiment, the data related to failures comprises at least one or more of the following: failure alarms, customer complaints, automatically generated maintenance tickets, information about automatically performed failure corrections, explanatory notes related to maintenance tickets, increased energy consumption, and performance indicator data.
In an example embodiment, identifying the first set of failures is based on comparing failure frequency during a monitored time period to a failure frequency during a reference time period.
In an example embodiment, identifying the first set of failures is based on comparing failure frequency in certain geographical area to a failure frequency in a reference area.
In an example embodiment, detecting that statistically significant number of failures of said first set of failures is associated with at least one common component is based on comparing failure frequency in a first component setup comprising the common component and failure frequency in a reference setup.
In an example embodiment, the common component is a component of a first type.
In an example embodiment, the common component is a jumper.
In an example embodiment, the common component is a component with a first software version.
In an example embodiment, the common component is a component with a first combination of software, firmware and/or hardware.
According to a second example aspect of the present invention, there is provided an apparatus comprising a processor and a memory including computer program code; the memory and the computer program code configured to, with the processor, cause the apparatus to perform the method of the first aspect or any related embodiment.
According to a third example aspect of the present invention, there is provided a computer program comprising computer executable program code which when executed by a processor causes an apparatus to perform the method of the first aspect or any related embodiment.
The computer program of the third aspect may be a computer program product stored on a non-transitory memory medium.
Different non-binding example aspects and embodiments of the present invention have been illustrated in the foregoing. The embodiments in the foregoing are used merely to explain selected aspects or steps that may be utilized in implementations of the present invention. Some embodiments may be presented only with reference to certain example aspects of the invention. It should be appreciated that corresponding embodiments may apply to other example aspects as well.
For a more complete understanding of example embodiments of the present invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:
Example embodiments of the present invention and its potential advantages are understood by referring to
Example embodiments of the invention provide new mechanisms to monitor and analyze operation of communication networks. Certain example embodiments are based on analyzing failures detected in operation of the network with the aim to identify situations where certain equipment or equipment setup may be the root cause of the failures.
It has been noted that automatic network monitoring may repeatedly detect failures in certain cell or base station. Likewise, plurality of similar failures may repeatedly occur in customer complaints or other sources of data relating to failures. In some cases, the repeated failures may lead to repeated replacement of physical equipment or at least repeated visits to base station site by maintenance personnel. The root cause for such repeated failures may be certain component or component setup that does not operate as intended and if the component is changed to another one, the repeated failures may disappear. Simply replacing the component with a new component of exactly same type may appear to be the solution if there is a failure associated with the component, but this does not always solve the problem permanently. Instead, the same problem may reoccur within a short period of time. In such cases, repairing the root cause (i.e. changing the component to another one) is clearly beneficial and likely to provide cost savings and improved user experience. Various embodiments of the invention provide alerts that flag out such potential root cause of problems and based on which the potential root cause may be repaired.
In an embodiment of the invention the scenario of
In phase 13, the automation system 111 analyses the failures and identifies a first set of failures comprising a statistically significant number of substantially similar failures.
In phase 14, it is detected that statistically significant number of failures in the first set of failures is associated with at least one common component. It is to be noted that if statistically significant number of similar failures or a common component are not detected, the process may stop or continue monitoring and analyzing further data relating to failures.
In phase 15, the automation system 111 outputs an alert when at least one common component is detected in the analysis of phase 14. Based on the alert, network operator may make an educated decision about changing one or more components in the network. For example, software or firmware version may be changed, component type may be changed, component vendor may be changed etc.
The analysis of phases 13 and 14 may be repeated for example once a day, every other day, every three days, once a week, every two weeks, once a month, or every two months or after some other period of time. By periodically repeating the analysis, changes performed in the network on the basis of the alerts may result in efficient improvements in the network and help avoiding repeated degradation of quality of service.
The general structure of the apparatus 20 comprises a processor 21, and a memory 22 coupled to the processor 21. The apparatus 20 further comprises software 23 stored in the memory 22 and operable to be loaded into and executed in the processor 21. The software 23 may comprise one or more software modules and can be in the form of a computer program product. Further, the apparatus 20 comprises a communication interface 25 coupled to the processor 21.
The processor 21 may comprise, e.g., a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a graphics processing unit, or the like.
The memory 22 may be for example a non-volatile or a volatile memory, such as a read-only memory (ROM), a programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), a random-access memory (RAM), a flash memory, a data disk, an optical storage, a magnetic storage, a smart card, or the like. The apparatus 20 may comprise a plurality of memories.
The communication interface 25 may comprise communication modules that implement data transmission to and from the apparatus 20. The communication modules may comprise, e.g., a wireless or a wired interface module. The wireless interface may comprise such as a WLAN, Bluetooth, infrared (IR), radio frequency identification (RF ID), GSM/GPRS, CDMA, WCDMA, LTE (Long Term Evolution) or 5G radio module. The wired interface may comprise such as Ethernet or universal serial bus (USB), for example. Further the apparatus 20 may comprise a user interface (not shown) for providing interaction with a user of the apparatus. The user interface may comprise a display and a keyboard, for example. The user interaction may be implemented through the communication interface 25, too.
A skilled person appreciates that in addition to the elements shown in
The method of
Phase 301: Data relating to failures in a communication network is being monitored. The data may be obtained from a plurality of different sources and may comprise at least one or more of the following: failure alarms, customer complaints, automatically generated maintenance tickets, information about automatically performed failure corrections, explanatory notes related to maintenance tickets, increased energy consumption, performance indicator data.
Phase 302: A first set of failures is identified. The first set of failures comprises a statistically significant number of substantially similar failures. For example: failure alarms may repeatedly indicate certain type of failure in certain base stations; customer complaints may indicate repeated problems in certain cells; automatically generated maintenance tickets may be repeatedly generated for certain base stations; automatically performed failure corrections may comprise continuous resets in certain cells during certain time period; explanatory notes related to maintenance tickets may show significant number of component changes; energy consumption in certain base stations may have increased during certain time period, while energy consumption in other base stations remains substantially the same as before; performance indicator data may exceed predefined threshold in plurality of cells. It is to be noted that this is non-exhaustive list and also other data sources and other types of failures may be monitored.
Statistically significant number of failures may be very different in different cases. In some cases, even a small number of failures may be statistically significant and in other cases larger amount of failures is required.
The flow diagram of
In an example embodiment, the substantially similar failures may refer to exactly the same failure occurring multiple times and/or the exactly same failure occurring in multiple places. Alternatively, multiple occurrences of similar failures suffice. For example, customer complaints in certain geographical area may be considered substantially similar even though the content of the complaint may be different. In another example, automatically performed failure corrections occurring the same time of the day may be considered substantially similar even though the failure correction may be different. In yet another example, explanatory notes related to maintenance tickets including certain key work such as “jumper” may be considered substantially similar even though the explanatory notes may be otherwise very different from each other.
The analysis of phase 302 may be performed for data obtained over a period certain of time. The period of time may be for example a week, two weeks, a month, two months or six months or some other period of time. In an example embodiment, there may be short-term evaluation and long-term evaluation that are performed simultaneously or only short-term or long-term evaluation may be chosen to be performed. For example, there may be evaluation over one-week period and evaluation over three-month period. A benefit of long-term evaluation is that sudden disruptions in network operation are ignored do not cause extensive action. Whereas a short-term evaluation provides the benefit of enabling quick reactions to problems in the network.
In an example case where energy consumption is monitored, there may be a short-term evaluation and a long-term evaluation. For example, at least 15% increase on weekly energy consumption or at least 10% increase over a 3-month period may be required for detection of increased energy consumption and identification of a first set of failures. The component setups exhibiting increased energy consumption may be then analysed for finding out whether they (or significant number of them) are associated with a common component that may be the root cause for the increased energy consumption. Substantial increase in energy consumption may be an indication of a malfunctioning component, but normal failure monitoring does not necessarily detect any problem. The embodiment where energy consumption is monitored provides the effect of being able to detect and repair such cases.
Phase 303: Common component associated with statistically significant number of failures in the first set of failures is detected. For example, if at least certain percentage of failures of the identified first set are associated with a component setup that comprises certain component type, then that certain component type may be considered to be the common component in the sense of present disclosure. The common component may be component of a certain type, component of a certain vendor, a combination of a certain component and certain software versions, a combination of a certain component with certain hardware, firmware and/or software. The percentage may be for example 30-70%. As a clarification, it is to be noted that statistically significant number is required twice: first it is required that the first set of statistically significant number of similar failures are identified in phase 302. Then, after identifying the first set of failures, it is required that within the first set of failures, there is a statistically significant number of failures associated with a common component. All failures of the first set need not relate to the common component, though.
It is to be noted that if statistically significant number of similar failures or a common component are not detected, the process may stop or continue monitoring and analyzing further data relating to failures.
Phase 305: An alert associated with the common component is output, when at least one common component is detected in phase 303. Based on the alert, network operator may make an educated decision about changing one or more components in the network. For example, software or firmware version may be changed, component type may be changed, component vendor may be changed etc.
In an example case, there are 100 maintenance visits to a base station site and 30 of these are associated with an explanatory note including the term “jumper”. Now if the 30 cases (or almost all of them) relate to a setup having the same jumper type, the method according to various embodiments results in an alert associated with the identified jumper type.
In another example case, there are 100 automatically performed failure corrections and 75 of these are associated with a setup comprising certain network equipment with certain software version. In such case the method according to various embodiments results in an alert associated with the software version (or combination of the network equipment type and software version).
In an embodiment, detecting e.g. in phase 303 of
In a first example case of
In a second example case of
In a third example case of
Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is ability to detect possible root cause for failures in network. In this way it is possible to improve operation of the network and to provide cost savings in network maintenance actions.
Another technical effect of one or more of the example embodiments disclosed herein is ability improve user experience by reducing failures in the network.
If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the before-described functions may be optional or may be combined.
Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.
It is also noted herein that while the foregoing describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications, which may be made without departing from the scope of the present invention as defined in the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 20205385 | Apr 2020 | FI | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/FI2021/050252 | 4/7/2021 | WO |
