Patent Grant
9113353
Some embodiments described herein relate generally to optimizing wireless networks, and in particular, to methods and apparatus for improving coverage and capacity in wireless networks by automatically reconfiguring transmit power and antenna tilt of multiple network elements.
Some known wireless networks implement an automated system for network optimization, which adjust radio resources and network parameters to improve the overall network performance. Such systems, however, typically are not designed to continuously optimize coverage and capacity within the wireless network by automatically reconfiguring transmit power and antenna tilt of multiple network elements while limiting any decrease in network performance (e.g., due to interference between two antenna cells). Further, some known network optimization systems fail to suitably react and readjust to differences between planned coverage and capacity and actual (in use) coverage and capacity.
Accordingly, a need exists for methods and apparatus for automatically reconfiguring transmit power and antenna tilt of one or more network elements to improve the overall network performance of the wireless network.
A non-transitory processor-readable medium stores code to cause a processor to receive, at a first time, a value associated with each key performance indicator from a set of key performance indicators associated with a wireless network. In some instances, a key performance indicator can be associated with, for example, a drop call rate. The code stored in the medium includes code to cause the processor to identify, based on the value associated with each key performance indicator from the set of key performance indicators, a geographic area having a network performance problem at the first time. The code stored in the medium includes code to cause the processor to send, in response to identifying the network performance problem and to a down cell detection module, an inactive cell request to identify inactive antenna cells from a set of antenna cells associated with the geographic area. The code stored in the medium includes code to cause the processor to receive in response to the inactive cell request an indication that each antenna cell from the set of antenna cells is active. The code stored in the medium includes code to cause the processor to send, in response to the geographic area having the network performance problem at the first time, a neighbor relation update request for each antenna cell from the set of antenna cells to update at a second time after the first time a neighbor list associated with that antenna cell. The code stored in the medium includes code to cause the processor to classify the network performance problem as a coverage hole in response to identifying the network performance problem at a third time. The third time is a predetermined time after the second time.
a)-3(d) illustrate antenna coverage maps with coverage holes having varying bases of identification for a wireless network, according to an embodiment.
a) and 6(b) illustrate a process for using timers when implementing coverage and capacity optimization for cells without automatic neighbor relation (ANR) updating, and cells with ANR updating, respectively, according to an embodiment.
In some embodiments, an apparatus includes a coverage hole detection module implemented in at least one of a memory or a processing device. The coverage hole detection module is configured to receive, at a first time, a value associated with each key performance indicator from a set of key performance indicators associated with a wireless network. In some instances, a key performance indicator can be associated with, for example, a drop call rate, an indication of received signal power at a set of user devices, an estimate of propagation time between the set of user devices and an access point associated with an antenna cell from the plurality of antenna cells, available resources at a set of user devices, a radio resource utilization rate at an antenna cell, and/or an indication of devices changing technology within the geographic area The coverage hole detection module is configured to identify, based on the value associated with each key performance indicator from the set of key performance indicators, a geographic area having a network performance problem at the first time. The coverage hole detection module is configured to send, in response to identifying the network performance problem and to a down cell detection module, an inactive cell request to identify inactive antenna cells from a set of antenna cells associated with the geographic area. The coverage hole detection module is configured to receive, from the down cell detection module and in response to the inactive cell request, an indication that each antenna cell from the set of antenna cells is active. The coverage hole detection module is configured to send, in response to the geographic area having the network performance problem at the first time and to a neighbor relation module, a neighbor relation update request for each antenna cell from the set of antenna cells to update at a second time after the first time a neighbor list associated with that antenna cell. The coverage hole detection module is configured to classify the network performance problem as a coverage hole in response to the coverage hole detection module identifying the network performance problem at a third time. The third time is a predetermined time after the second time.
In some embodiments, an apparatus includes a coverage hole mitigation module implemented in at least one of a memory or a processing device. The coverage hole mitigation module is configured to receive an indication of a coverage hole within a geographic area and associated with multiple antenna cells associated with an antenna. The coverage hole mitigation module is configured to identify a first antenna cell (1) from the multiple antenna cells and (2) to use to mitigate the coverage hole. The coverage hole mitigation module is configured to send a signal to change a tilt of the antenna from a first position to a second position at a first time. The coverage hole mitigation module is configured to send, at a second time after the first time, a signal to increase power of the first antenna cell from a first power level to a second power level in response to at least one of (1) an adverse effect on a coverage area associated with a second antenna cell from the multiple antenna cells and during a predetermined time period after the first time, or (2) a limit associated with the tilt of the antenna.
The code stored in the medium includes code to cause the processor to further analyze, periodically and upon expiration of a detection timer for a wireless network, a first value of each key performance indicator from a set of key performance indicators for the wireless network. The code stored in the medium includes code to cause the processor to identify, based on the first value associated with at least one key performance indicator from the set of key performance indicators, a geographic area having a network performance problem at a time. The code stored in the medium includes code to cause the processor to send, in response to the geographic area having the coverage network performance problem at the time, a neighbor relation request to update a neighbor list associated with at least one antenna cell from a set of antenna cells associated with the geographic area. The code stored in the medium includes code to cause the processor to initiate a neighbor relation timer associated with the at least one antenna cell based on sending the neighbor relation request. The code stored in the medium includes code to cause the processor to, upon expiration of the neighbor relation timer, identify the network performance problem as a coverage hole if a second value associated with the at least one key performance indicator does not meet a predetermined criterion. The code stored in the medium includes code to cause the processor to send, in response to identifying the network performance problem as a coverage hole, a signal to modify at least one of a power associated with the at least one antenna cell from the set of antenna cells or a tilt of an antenna including the at least one antenna cell from the set of antenna cells. The code stored in the medium includes code to cause the processor to initiate a monitor timer and an action timer for the antenna in relation to the signal to modify at least one of the power or the antenna tilt. The code stored in the medium includes code to cause the processor to, upon expiration of the monitor timer, receive a third value of each key performance indicator from the set of key performance indicators and determine improvement or decrease in performance associated with the antenna based on the third value of the at least one key performance indicator from the set of key performance indicators. The code stored in the medium includes code to cause the processor to, upon expiration of the action timer, send a signal to further modify at least one of the power associated with the at least one antenna cell from the set of antenna cells or the tilt of the antenna if a fourth value of the at least one key performance indicator from the set of key performance indicators meets a predetermined criterion.
As used herein, an antenna can be any device or component that can radiate, transmit, and/or receive signals (e.g., electromagnetic and/or radio waves). For example, an antenna can include an element or device for transmitting and/or receiving radio frequency signals within a communications network.
As used herein, an antenna cell can be a portion of an antenna, associated circuitry and/or associated component(s) that defines a coverage area for a particular frequency, technology (3rd Generation (3G)), geographic area, and/or power level. A perimeter of the coverage area can be defined at least in part by the antenna cell. Further, the antenna cell can define at least in part an effective operating range for transmitting and receiving signals. In some embodiments, an antenna cell, and its associated circuitry and/or components, can be associated with a particular radio frequency, a particular technology (Long Term Evolution (LTE)), and/or a particular provider of such services. In some embodiments, multiple antenna cells can be associated with a common antenna. An antenna cell can also be referred to as an antenna portion.
As used herein, a coverage area can be an area defined by an effective operating range of a transmitter and/or antenna cell. Outside of the coverage area, for example, can be an ineffective operation range of the transmitter and/or the antenna cell associated with the coverage area. Each coverage area can be associated with a particular antenna cell. Further, a coverage area, or a perimeter thereof, can be modified by modifying configuration parameters of the antenna cell associated with that coverage area (e.g., by modifying tilt and/or power).
As used herein, an antenna sector can be multiple antenna cells associated with a common antenna. For example, an antenna sector can include a first antenna cell (e.g., associated with a first technology or frequency) and a second antenna cell (e.g., associated with a second technology or frequency). For example, each antenna cell of an antenna can be within a common antenna sector.
As used herein, a module can be, for example, any assembly and/or set of operatively-coupled electrical components associated with performing a specific function, and can include, for example, a memory, a processor, electrical traces, optical connectors, software (executing in hardware) and/or the like. As used herein, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, the term “a coverage hole detection module” is intended to mean a single module or a combination of modules configured to perform coverage hole detection functions.
Specifically, the wireless network 100 can be any network that enables wireless communication devices (e.g., cellular phones, Wi-Fi enabled laptops, Bluetooth devices, mobile devices, etc.) to communicate with each other. In some embodiments, the wireless network 100 can be implemented and administered using wireless transmission such as radio frequency (RF) waves. For example, the wireless network 100 can be a cellular network that enables two cellular phones to communicate with each other. For another example, the wireless network 100 can be a Wi-Fi network that enables multiple Wi-Fi enabled laptops to be operatively connected. In some embodiments, the wireless network 100 can be at least a portion of, for example, a wireless local area network (WLAN), a wireless mesh network, a wireless metropolitan area network (MAN), a wireless wide area network (WAN), a mobile device network (e.g., a global system for mobile communications (GSM) network, a personal communications service (PCS) network), a radio access network (RAN), a long term evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS) network, and/or the like.
As shown in
The network optimization device 101 is operatively coupled to the network database 120. The network optimization device 101 is also operatively coupled to and configured to manage the one or more controllers (e.g., controllers 112, 114 and 116). Each controller (e.g., the controller 114) is operatively coupled to and configured to manage one or more network elements (e.g., base stations 142, 144 and 146). A controller can be any device that is capable of sending control signals (e.g., commands, instructions, requests, etc.) to the network element(s) controlled by that controller, thus managing operations of the network element(s). In some embodiments, a controller can be, for example, a server or similar computer device. In some embodiments, a controller can also be considered a network element of the wireless network 100.
A network element (e.g., the base station 142, 144 or 146) controlled by a controller (e.g., the controller 114) can be any device, component, subsystem, or infrastructure that can be wirelessly coupled to and communicate with one or more wireless communication devices (e.g., communication devices of subscribers to the wireless network 100). In some embodiments, such a network element (e.g., the base station 146) can be equipped with and configured to control one or more antennas (e.g., the antennas 152 and 154 and/or antenna cell(s) of each antenna), which can be used to support data communications (e.g., transmit data to and/or receive data from) between that network element and the wireless communication devices (not shown in
In some embodiments, the connections between the network optimization device 101 and the one or more controllers (e.g., the controllers 112, 114 and 116) and the network database 120 can include, for example, a wireless connection, a wired connection, and/or a combination of wireless and wired connections. Similarly, the connections between each controller (e.g., the controller 114) and its associated network element(s) (e.g., the base stations 142, 144 and 146) can include, for example, a wireless connection, a wired connection and/or a combination of wireless and wired connections.
The network database 120 can be implemented in a memory or other storage device that is part of the network optimization device 101 or another device operatively coupled to the network optimization device 101. The network database 120 can be configured to receive and store information and/or data associated with the wireless network 100, such as network statistics, current network configurations, and performance indicators of the wireless network 100. Furthermore, the network database 120 can be configured to provide or send the stored information and/or data to the network optimization device 101. The information and/or data can be used at the network optimization device 101 to monitor, optimize or improve network performance of the wireless network 100, as described in detail with respect to
The network optimization device 101 can be any device configured to control, monitor, coordinate and/or execute one or more optimization processes (e.g., hardware processes and/or software processes executed in hardware) for performing optimization of network parameters (e.g., coverage, capacity, interference, etc.) in the wireless network 100. In some embodiments, the network optimization device 101 can be, for example, a compute device, a server device, an application server, a mobile device, a workstation, and/or the like. As shown in
In some embodiments, the process for improving and/or optimizing coverage and capacity in the wireless network 100 can be executed at a processor of the network optimization device 101.
As shown in
As shown in
As will be discussed in further detail herein, the coverage hole detection module 222, the down cell detection module 224, the neighbor relation module 226 and the coverage hole mitigate module 228 can cooperatively function to identify coverage holes from network performance problems, mitigate the coverage holes while reducing and/or minimizing potential detriment or interference within the wireless network resulting from such mitigation, and monitor actual performance during and after mitigation.
a)-3(d) illustrate antenna coverage maps with coverage holes having varying bases of identification and degrees of insufficient coverage and capacity. First,
b) illustrates an antenna coverage map with a coverage hole CHb identifiable based at least in part on a drop call rate. As shown, coverage hole CHb is located between a first coverage area 362b established by a first antenna cell (not shown), and a second coverage area 364b established by a second antenna cell (not shown). In operation, as subscriber devices move into or are otherwise disposed within the coverage hole CHb, drop call rates associated with coverage area 362b and/or coverage area 364b will be present, or increase, thereby indicating the possibility of a coverage hole.
c) illustrates an antenna coverage map with an “isolated island” coverage hole CHc identifiable based at least in part on a drop call rate or a lower than expected use rate. As shown, coverage hole CHc is defined in part by an expected or designed coverage area 364c, that surrounds an actual coverage area 362c. Similarly stated, the actual coverage area 362c is smaller than the expected or designed coverage area 36c, thereby defining the coverage hole CHc therebetween. Here, subscriber devices (not shown) moving from actual coverage area 362c to designed coverage area 364c will experience interruption in service (e.g., a dropped call). In some instances, a usage rate associated with the actual coverage area 362c can be lower than an expected usage rate based on or associated with the designed coverage area 364c
d) illustrates an antenna coverage map experiencing overshooting, and thus potential interference issues and/or capacity issues with neighbor antennas and/or antenna cells. As shown, the wireless system includes an actual coverage area 362d surrounding or overflowing a planned coverage area 364d. Such overflow OF can be identified based on interference by or to neighbor antenna cells. In addition, such overflow can result in overcrowding of a coverage area 362d. Overcrowding by subscriber devices (not shown) of a coverage area, in some instances, can result in capacity challenges. Similarly stated, a number of subscriber devices (not shown) may seek to communicate with an antenna—that number being greater than a designed capacity of that antenna/service.
Referring back to
Before classifying or identifying a network performance problem as a coverage hole, and subsequently taking action to mitigate the coverage hole, in some embodiments, it can be desirable to eliminate or rule-out potential causes of the network performance problem. One potential cause of or contributor to a network performance problem can be an inactive antenna cell associated with the geographic area experiencing the network performance problem. For example, if a network performance problem is caused by an inactive cell, the network performance problem may be mitigated by fixing the antenna cell associated with that inactive cell. Similarly stated, if the network performance problem is caused by an inactive cell, the network performance problem will not be classified as a coverage hole. If, however, the network performance problem is not caused by an inactive cell, the network performance problem can potentially be classified as a coverage hole.
To diagnose, in some instances, the coverage hole detection module 222 can send to the down cell detection module 224 an inactive cell request to identify any inactive antenna cells associated with that geographic area. In response to the request, the down cell detection module 224 can determine and/or identify any such inactive or insufficiently functioning antenna or antenna cell(s). For example, the down cell detection module 224 can access a list of current inactive cells, and/or query one or more antenna cells, or associated components, to identify any such inactive cells. The down cell detection module 224 can then send to the coverage hole detection module a signal representing its determination or identification. Similarly stated, the coverage hole detection module 222 can receive from the down cell detection module 224 and in response to the inactive cell request, a status indication of one or more antenna or antenna cells.
Further, another potential cause of or contributor to a network performance problem is an inaccurate (or outdated) neighbor relation list. For example, if a neighbor list is not up-to-date, neighbor antenna cells, or subscriber devices in communication (or desirous of communication) therewith, may experience handover issues. Thus, in some embodiments, it can be desirable to determine whether the network performance problem is caused by or related to an inaccurate neighbor relation list. If the network performance problem is caused by an inaccurate neighbor relation list, an update to the list may improve or eliminate the network performance problem. As such, a network performance problem caused any an inaccurate neighbor relation list will not be classified as a coverage hole.
To diagnose, in some instances, the coverage hole detection module 222 can send to the neighbor relation module 226 a neighbor relation update request for one or more antenna cells in a geographic area associated with an indication of a network performance problem to update a neighbor list associated with that antenna cell. In instances in which the coverage hole detection module 222 identifies the network performance problem upon expiration of a predetermined time period after sending a neighbor relation update request, it can be assumed that the network performance problem is not caused by or related to an inaccurate neighbor list or associated handover issues. As such, in some embodiments, the coverage hole detection module 222 can classify a network performance problem as a coverage hole when each antenna cell within a particular geographic area associated with the network performance problem is active, and a neighbor list associated with each antenna cell within the geographic area is up-to-date and/or accurate.
In some instances, the coverage hole detection module 222 can receive, from the down cell detection module 224 (e.g., in response to identifying a network performance problem within a geographic area), an indication that each antenna cell associated with that geographic area is active. In response to receiving the indication, in some instances, the coverage hole detection module 222 can send to the neighbor relation module 226 a neighbor relation update request for each antenna cell within that geographic area to update a neighbor list. If the coverage hole detection module 222 subsequently (e.g., at a pre-determined time or after expiration of a pre-determined time period) identifies the network performance problem, the coverage hole detection module 222 can classify that network performance problem as a coverage hole.
Once a network performance problem has been classified as a coverage hole, the coverage hole mitigation module 228 of the network optimization device 201 can improve and/or optimize the wireless network by mitigating the coverage hole. In some embodiments, for example, the coverage hole mitigation module 228 can receive from the coverage hole detection module 222 an indication of a coverage hole within a geographic area. The indication can include an association between the coverage hole and multiple antenna cells associated with an antenna. Based upon such an indication, the coverage hole mitigation module 228 can send a signal to antennas (or associated components or devices) within the network to modify a power and/or an antenna tilt associated with one or more antenna cells.
In some instances, the coverage hole mitigation module 228 can identify (e.g., based on KPI's associated with a geographic area having a network performance problem; and/or based on a ranking (as discussed in further detail herein) associated with the antenna cell(s)) a first antenna cell (1) from the multiple antenna cells and (2) to use to mitigate the coverage hole. In some instances, it can be desirable to modify the tilt of an antenna rather than a power of the antenna to maintain or optimize balanced uplink and downlink communications between the antenna and associated subscriber devices. As such, in some instances, upon identifying the first antenna cell to use to mitigate the coverage hole, the mitigation module 228 can send a signal to the antenna (or a controller operably coupled thereto) associated with the first antenna cell to change a tilt of its associated antenna from a first position to a second position. In some instances, the tilt change can mitigate the coverage hole. Further, in some cases, (e.g., if the initial tilt change only partially mitigated the coverage hole), the coverage mitigation module 228 can send a signal to change the tilt of the antenna from the second position to a third position to further mitigate the coverage hole. In some instances, however, based on a tilt limit of the antenna (e.g., the antenna cannot change from the second position to the third position), tilt modification may not be sufficient for mitigating a coverage hole. In such instances, the coverage hole mitigation module 228 can send a signal to change a power level of the antenna cell to further mitigate the coverage hole. In this manner, tilt and power modifications can collectively mitigate the coverage hole.
In other instances, however, such a tilt change may result in no significant change or may result in an adverse effect on a coverage area associated with a second antenna cell from the multiple antenna cells. In such cases, in response to the adverse effect (e.g., identified based on one or more KPIs) on the coverage area associated with the second antenna cell during a predetermined time period after the coverage hole mitigation module 228 sent the signal to change the tilt, the coverage hole mitigation module 228 can send a signal to re-adjust the tilt of the first antenna (e.g., revert the tilt to a different configuration, or a prior configuration (from the second position to the first position)).
Upon reversion or re-adjustment of the first antenna tilt, the coverage hole mitigation module 228 can send a signal to adjust the power of the first antenna cell from a first power level to a second power level. In desirable instances, sending the signal to adjust the power of the first antenna cell from the first power level to the second power level can result in an improvement in a value of one or more KPIs. In such instances, the coverage hole mitigation module 228 can send a signal to increase the power of the first antenna cell from the second power level to a third power level. In this manner, the coverage hole mitigation module 228 can incrementally optimize the coverage and capacity within that geographic area, while continually monitoring (e.g., via KPIs) the network performance.
In other instances, however, sending the signal to adjust the power from the first power level to the second power level can produce an undesirable result or change within the wireless network 200, e.g., an indication of devices changing technology within the geographic area, interference issues, capacity issues, etc. In some instances, based on identification of such an adverse effect on one or more of the antenna cells, the coverage hole mitigation module 228 can send a signal to change the power of the first antenna cell from the second power level to the first power level (i.e., revert back to the initial power level). In such instances, it can be desirable to revert back expediently to mitigate the adverse effect. In some embodiments, for example, a time period to change the power of the first antenna cell from the second power level to the first power level (e.g., based on identification of an adverse effect on one or more antenna cells) is less than a time period to further increase the power of the first antenna cell from the second power level to the third power level (e.g., based on the improvement of one or more antenna cells).
In some instances, the first antenna cell can meet a capacity limit after its power is increased (e.g., from the first power level to the second power level). In such instances, the coverage hole mitigation module 228 can send a signal to change the power of the first antenna cell from the second power level to the first power level, or to a power level there between suitable to address any capacity limit issues.
In some instances, the antenna can meet a capacity limit during or after its tilt increase (e.g., from the first tilt position to the second tilt position). In such instances, the coverage hole mitigation module 228 can send a signal to change the tilt of the antenna from the second tilt position to the first tilt position, or to a tilt position there between suitable to address any capacity limit issues.
Modifications to the power level and/or the tilt of an antenna selected to mitigate a coverage hole can incremental, and can be triggered in any suitable order. Such incremental modifications can allow for better monitoring, control and reaction to effects on network performance.
Before, after, or while modifying a power level and/or tilt of an antenna cell to modify a coverage hole within a wireless network, potential interference to the antenna cell's neighbors can be monitored, reduced and/or minimized. (also referred to herein as potential victims).
Potential victim antenna cells can be identified and/or selected for interference management based on, for example, a value associated with handovers, an azimuth angle, a beamwidth, and/or a distance estimated by an estimate of propagation time and/or geographic information, such as, latitude and longitude data.
As shown by the coverage areas established from each candidate antenna cell, the three candidate antenna cells A, B, and C, are available to mitigate the coverage hole CH (e.g., by adjustment in antenna power level and/or tilt). Notwithstanding neighbor interference issues (i.e., disregarding potential victim antenna cells D, E), in some embodiments, a candidate antenna cell from the three candidate antenna cells can be selected to mitigate the coverage hole CH based on a predefined ranking, for example, a cost-based ranking (e.g., a cost value to modify a configuration of a given antenna cell). A cost value can be based on, for example, a value associated with dropped calls, a value associated with handovers, a value associated with other user devices likely to be affected by a mitigation action, distances from tilt or power limits, and/or proximity to the coverage hole. Further, antenna cells, and/or in some instances potential victim antenna cells, can be selected for mitigation action based on, for example, an azimuth angle, a beamwidth, and/or a distance estimated by an estimate of propagation time and/or geographic information, such as, latitude and longitude data.
As a further example, capacity of the antenna cells can serve as an additional or alternative factor for determining ranking. For example, if candidate antenna cell A can handle a first number of subscriber devices, and candidate antenna cell B can handle a second number of subscriber devices larger than the first number of subscriber devices, candidate antenna cell B may be more suitable than candidate antenna cell A for mitigating certain coverage holes requiring a certain capacity.
As yet an additional or alternative factor for ranking purposes, a candidate antenna cell can be selected to use to at least partially mitigate the coverage hole CH based on a portion of the coverage hole CH associated with that antenna cell being greater than a portion of the coverage hole associated with each remaining candidate antenna cells. As an example, if candidate antenna cell A can be reconfigured to mitigate 50% of coverage hole CH, and candidate antenna cell B can be reconfigured to mitigate only 20% of coverage hole CH, candidate antenna cell A will be ranked higher than candidate antenna cell B. Further to this example, in some instances, based on a cost value associated with modifying a configuration of antenna cell A being significantly higher than a cost value associated with modifying a configuration of antenna cell B, candidate antenna cell B may have a ranking higher than candidate antenna cell A, in some instances, even when the candidate antenna cell A can be reconfigured to mitigate a larger portion of the coverage hole CH than the candidate antenna cell B. Assuming for discussion purposes that candidate antenna cell A is ranked higher than candidate antenna cell B, and the candidate antenna cell B is ranked higher than the candidate antenna cell C, when the coverage hole CH is detected, candidate antenna cell A is initially selected based on its ranking to mitigate the coverage hole CH.
Candidate antenna cell A and candidate antenna cell B can share a common potential victim antenna cell (i.e., potential victim antenna cell D) within their established cells. Similarly stated, if both candidate antenna cell A and candidate antenna cell B were to collectively or substantially simultaneously adjust their power levels or tilt settings to mitigate the coverage hole CH, potential victim antenna cell D may experience interference issues due to being within the coverage areas established by candidate antenna cell A and candidate antenna cell B. To minimize or avoid such interference issues, in this example, the configurations of candidate antenna cell A and candidate antenna cell B are not collectively or substantially simultaneously modified to mitigate the coverage hole CH.
Turning to the next best antenna cell to help mitigate the coverage hole CH, i.e., candidate antenna cell C, as shown in
Referring back to
As discussed with respect to
Capacity and coverage optimization (CCO) of the wireless network can be an iterative process based on many factors, and can include detecting, managing, reconfiguring and monitoring many network elements and components, as discussed above. As such, in some embodiments, various timers can be employed to detect, manage and/or monitor performance changes in the wireless network.
For ease of illustration, the timers can be divided into two categories, i.e., identification timers and mitigation timers. The detection timer (Time_Det) and the neighbor relation timer (Time_ANR) are classified as identification timers, and can specify time periods in which to detect network performance problems and identify when such problems should be classified as coverage holes. The action timer (Time-Act) and monitor timer (Time-Mon) are classified as mitigation timers.
As shown in
Upon identification of a network performance problem, the antenna cell(s) associated with the network performance problem (e.g., antenna cell F) proceeds from following the detection timer (e.g., the detection timer can be associated with all antenna cells in the network) to following the neighbor relation timer specific to cell F, which is triggered upon expiration of the detection timer and based on the identification of the network performance problem. In other words, antenna cell F (also referred to herein as a problem cell) can transfer from the global timer detection process to a cell specific identification/mitigation process.
Because antenna cell F does not use an ANR function, as illustrated in
In addition, as discussed in further detail herein, a down cell detection process can be executed to determine any inactive cells associated with the geographic area of the network performance problem. This process can include, for example, accessing a list of current inactive cells, and/or querying one or more antenna cells, or associated components, to identify any inactive cells.
Upon expiration of the neighbor relation timer and after updating the neighbor list, the KPI's associated with that timer (i.e., the “Missing Neighbor Verification Time Interval”) are analyzed to determine if the network performance problem still exists. In some embodiments, the KPI's associated with the neighbor relation timer can be compared with the KPI's associated with the detection timer. If the network performance problem still exists after the down cell detection process results in no inactive cells identified, and neighbor list is updated, the network performance problem can be classified as a coverage hole.
In response to identifying the network performance problem as a coverage hole upon expiration of the neighbor relation timer (
In other embodiments, as shown in
At this time, a signal is sent to modify (1) a power associated with one or more antenna cells that are associated with the problem cell (e.g., antenna cell F), and/or (2) a tilt of an antenna of one or more antenna cells that are associated with the problem cell (e.g., antenna cell F). In other words, suitable antenna cells are modified (also referred to herein as a “CCO Action Change”) to mitigate the coverage hole in the problem cell.
During a duration associated with the action timer (the “CCO Action Change Time Interval”) and a duration associated with the monitor timer (the “Monitoring Time Interval”), the KPI's (or average of the KPI's) associated with one or both of those durations are analyzed to determine network performance and/or a change thereto. For example, a set of KPIs can be monitored during each monitor period (defined by the monitoring time interval(s)). Upon expiration of each monitor timer, the KPI's collected and/or monitored during that time period can be analyzed for status of and/or changes to status of network performance. Further, upon expiration up each action timer, based on the assessment of the data (e.g., KPI's) monitored during the associated monitoring time interval, progressive action/mitigation can occur. When an action (e.g., power or tilt) is executed, monitoring according to the appropriate monitor timer (and associated interval) will occur to assess the results of the action(s) on network performance. Similarly stated, correlative results between the action change (power or tilt) and the network performance, based on KPI's, can be monitored, defined, analyzed, acted upon, and re-acted upon.
In some embodiments, a duration associated with the monitor timer can be less than a duration associated with the action timer. This is illustrated in
In this manner, effects on network performance by CCO action changes can be monitored periodically or in substantially real-time such that any undesirable effects can be sensibly and relatively quickly mitigated. For example, consider the case where a CCO action change includes three power steps/modifications, then two tilt position changes, and then one more power modification. A monitor timer can be employed and reset multiple times (e.g., 6 times) before the above action changes are implemented. As such, a decrease in performance associated with the antenna receiving the CCO action change can be identified relatively quickly and appropriate action (e.g., revert to a prior configuration) can be taken. Accordingly, adverse effects can be identified and mitigated within a shorter time period than taking additional progressive action to mitigate a coverage hole.
In some embodiments, CCO can be applied to antenna cells at a single antenna or antenna sector.
As an example, in use, a network performance problem can be detected in cell A.1 during the CCO Detection Time Interval. In this example, similar to
As shown in
At 702, the network optimization device can receive, at a first time, a value associated with each key performance indicator from a set of key performance indicators associated with a wireless network. The set of key performance indicators can include, for example, a drop call rate, an indication of received signal power at a set of user devices, an estimate of propagation time between the set of user devices and an access point (e.g., a base station similar to base station 146 in
At 706, the network optimization device can send, in response to identifying the network performance problem, an inactive cell request to identify inactive antenna cells from a set of antenna cells associated with the geographic area. The inactive cell request, for example, can be sent to a down cell detection module. At 708, the network optimization device can receive, in response to the inactive cell request, an indication that each antenna cell from the set of antenna cells is active. As such, the network performance problem can be identified as not an inactive cell problem.
At 710, the network optimization device can send, in response to the geographic area having the network performance problem at the first time a neighbor relation update request for each antenna cell from the set of antenna cells to update at a second time after the first time a neighbor list associated with that antenna cell. In some instances, the network optimization device can send the neighbor relation request in response to receiving the indication that each antenna cell from the set of antenna cells is active. If the network performance problem is identified after a predetermined time at the second time, the network performance problem can be identified as not a handoff/neighbor relation problem.
At 712, the network optimization device can classify the network performance problem as a coverage hole in response to the identifying the network performance problem at a third time. The third time is a predetermined time after the second time. Similarly stated, based on the results from the inactive cell request and the neighbor relation update request, and identifying the network performance at the third time (i.e., after the inactive cell and inaccurate neighbor lists are identified as not the problem), the network performance problem can be classified as a coverage hole.
In some embodiments, method 700 can include step 714 in which the network optimization device can send a signal to modify at least one of a power or an antenna tilt associated with at least one antenna cell from the set of antenna cells based on the classifying the network performance problem as a coverage hole. In some instances, the network optimization device can, for each antenna cell from the set of antenna cells, detect a set of potential victim antenna cells within an area covered by that antenna cell from the set of antenna cells if that antenna cell from the set of antenna cells were used to mitigate the coverage hole. The network optimization device can select a first antenna cell from the set of antenna cells to use to mitigate the coverage hole, and send a signal to modify a configuration associated with the first antenna cell to at least partially mitigate the coverage hole. In some instances, the network optimization device does not use a second antenna cell from the set of antenna cells to mitigate the coverage hole based on an antenna cell from the set of potential victim antenna cells within the area covered by the second antenna cell being within the set of potential victim antenna cells within the area covered by the first antenna cell.
In some instances, the network optimization device can, for each antenna cell from the set of antenna cells, detect a set of potential victim antenna cells within an area covered by that antenna cell from the set of antenna cells if that antenna cell from the set of antenna cells were used to mitigate the coverage hole. The network optimization device can select a first antenna cell from the set of antenna cells to use to mitigate the coverage hole, and can send a signal to modify a configuration associated with the first antenna cell to at least partially mitigate the coverage hole. The network optimization device can be configured to send a signal to modify a configuration associated with a second antenna cell from the set of antenna cells based on each antenna cell from the set of potential victim antenna cells within the area covered by the second antenna cell not being within the set of potential victim antenna cells within the area covered by the first antenna cell.
In some instances, the network optimization device can rank the set of antenna cells based on a cost value to modify a configuration of each antenna cell from the set of antenna cells, and at a fourth time after the third time, send a signal to change a configuration associated with a first antenna cell from the set of antenna cells to mitigate the coverage hole based on the first antenna cell having a rank meeting a first predetermined criterion. The network optimization device can, at a fifth time after the fourth time, send a signal to change a configuration associated with a second antenna cell from the set of antenna cells to mitigate the coverage hole based on (1) the second antenna cell from the set of antenna cells having a rank meeting a second predetermined criterion (e.g., has the next lowest cost) and (2) the first antenna cell from the set of antenna cells not meeting a third predetermined criterion (e.g., would cause interference).
In some instances, the network optimization device can select an antenna cell from the set of antenna cells to use to at least partially mitigate the coverage hole based on a portion of the coverage hole associated with the antenna cell from the set of antenna cells being greater than a portion of the coverage hole associated with each remaining antenna cell from the set of antenna cells.
When optimizing the capacity and coverage of a wireless network, a tradeoff can exist between such coverage and capacity. For example, in some cases, an expansion in coverage may lead to a decrease in capacity.
As shown by the “Coverage Measure plot of
While shown in
Some embodiments described herein relate to a computer storage product with a non-transitory computer-readable medium (also can be referred to as a non-transitory processor-readable medium) having instructions or computer code thereon for performing various computer-implemented operations. The computer-readable medium (or processor-readable medium) is non-transitory in the sense that it does not include transitory propagating signals per se (e.g., a propagating electromagnetic wave carrying information on a transmission medium such as space or a cable). The media and computer code (also can be referred to as code) may be those designed and constructed for the specific purpose or purposes. Examples of non-transitory computer-readable media include, but are not limited to: magnetic storage media such as hard disks, floppy disks, and magnetic tape; optical storage media such as Compact Disc/Digital Video Discs (CD/DVDs), Compact Disc-Read Only Memories (CD-ROMs), and holographic devices; magneto-optical storage media such as optical disks; carrier wave signal processing modules; and hardware devices that are specially configured to store and execute program code, such as Application-Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), Read-Only Memory (ROM) and Random-Access Memory (RAM) devices. Other embodiments described herein relate to a computer program product, which can include, for example, the instructions and/or computer code discussed herein.
Examples of computer code include, but are not limited to, micro-code or micro-instructions, machine instructions, such as produced by a compiler, code used to produce a web service, and files containing higher-level instructions that are executed by a computer using an interpreter. For example, embodiments may be implemented using Java, C++, or other programming languages (e.g., object-oriented programming languages) and development tools. Additional examples of computer code include, but are not limited to, control signals, encrypted code, and compressed code.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, not limitation, and various changes in form and details may be made. Where methods described above indicate certain events occurring in certain order, the ordering of certain events may be modified. Additionally, certain of the events may be performed concurrently in a parallel process when possible, as well as performed sequentially as described above. Any portion of the apparatus and/or methods described herein may be combined in any combination, except mutually exclusive combinations. The embodiments described herein can include various combinations and/or sub-combinations of the functions, components and/or features of the different embodiments described.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5425051 | Mahany | Jun 1995 | A |
| 5796722 | Kotzin et al. | Aug 1998 | A |
| 5802144 | Laird et al. | Sep 1998 | A |
| 5859839 | Ahlenius et al. | Jan 1999 | A |
| 5873040 | Dunn et al. | Feb 1999 | A |
| 6051408 | Bartsch et al. | Apr 2000 | A |
| 6069871 | Sharma et al. | May 2000 | A |
| 6115393 | Engel et al. | Sep 2000 | A |
| 6138016 | Kulkarni et al. | Oct 2000 | A |
| 6141565 | Feuerstein et al. | Oct 2000 | A |
| 6253077 | Burt et al. | Jun 2001 | B1 |
| 6304556 | Haas | Oct 2001 | B1 |
| 6400335 | Weaver et al. | Jun 2002 | B1 |
| 6400355 | Pin-Chien | Jun 2002 | B1 |
| 6545690 | Hernandez | Apr 2003 | B1 |
| 6549529 | Drabeck et al. | Apr 2003 | B1 |
| 6574477 | Rathunde | Jun 2003 | B1 |
| 6729929 | Sayers et al. | May 2004 | B1 |
| 6829491 | Yea et al. | Dec 2004 | B1 |
| 6842431 | Clarkson et al. | Jan 2005 | B2 |
| 6937863 | Gordon et al. | Aug 2005 | B1 |
| 6985704 | Yang et al. | Jan 2006 | B2 |
| 6999766 | Padovani | Feb 2006 | B1 |
| 7006805 | Sorrells et al. | Feb 2006 | B1 |
| 7016685 | Cain et al. | Mar 2006 | B1 |
| 7149478 | Hawe | Dec 2006 | B2 |
| 7221928 | Laird et al. | May 2007 | B2 |
| 7260415 | Oh | Aug 2007 | B1 |
| 7313402 | Rahman | Dec 2007 | B1 |
| 7323945 | Cyr et al. | Jan 2008 | B2 |
| 7349765 | Reaume et al. | Mar 2008 | B2 |
| 7353160 | Voigt | Apr 2008 | B2 |
| 7385503 | Wells et al. | Jun 2008 | B1 |
| 7461037 | Hätönen et al. | Dec 2008 | B2 |
| 7477920 | Scheinert et al. | Jan 2009 | B2 |
| 7505010 | Franzon et al. | Mar 2009 | B2 |
| 7519860 | Hätönen et al. | Apr 2009 | B2 |
| 7529215 | Osterling | May 2009 | B2 |
| 7561876 | Chiou et al. | Jul 2009 | B2 |
| 7567822 | Hart et al. | Jul 2009 | B2 |
| 7577103 | Diaz et al. | Aug 2009 | B2 |
| 7590589 | Hoffberg | Sep 2009 | B2 |
| 7606287 | Mahany | Oct 2009 | B2 |
| 7609747 | Mahany | Oct 2009 | B2 |
| 7623455 | Hilla et al. | Nov 2009 | B2 |
| 7653407 | Backes et al. | Jan 2010 | B2 |
| 7663555 | Caimi et al. | Feb 2010 | B2 |
| 7747712 | Petersen et al. | Jun 2010 | B2 |
| 7757103 | Savransky et al. | Jul 2010 | B2 |
| 7768968 | Plehn et al. | Aug 2010 | B2 |
| 7827268 | Monier et al. | Nov 2010 | B2 |
| 7839882 | Soliman | Nov 2010 | B2 |
| 7877095 | Hubner et al. | Jan 2011 | B2 |
| 7877108 | Wengerter et al. | Jan 2011 | B2 |
| 7899890 | Petersen et al. | Mar 2011 | B2 |
| 7904080 | Atkins et al. | Mar 2011 | B2 |
| 7941136 | Reed et al. | May 2011 | B2 |
| 7969896 | Sheinfeld et al. | Jun 2011 | B2 |
| 8010469 | Kapoor et al. | Aug 2011 | B2 |
| 8018925 | Noriega | Sep 2011 | B2 |
| 8023529 | Oh et al. | Sep 2011 | B2 |
| 8032131 | Dobson et al. | Oct 2011 | B2 |
| 8045996 | Brunner et al. | Oct 2011 | B2 |
| 8050191 | Tirpak et al. | Nov 2011 | B2 |
| 8117294 | Pollakowski et al. | Feb 2012 | B2 |
| 8144619 | Hoffberg | Mar 2012 | B2 |
| 8159932 | Hart et al. | Apr 2012 | B1 |
| 8185124 | Antic et al. | May 2012 | B2 |
| 8208924 | Han et al. | Jun 2012 | B2 |
| 8295877 | Hui et al. | Oct 2012 | B2 |
| 8320850 | Khlat | Nov 2012 | B1 |
| 8355728 | Jung et al. | Jan 2013 | B2 |
| 8385900 | Trigui | Feb 2013 | B2 |
| 8509762 | Li et al. | Aug 2013 | B2 |
| 8626075 | Turk et al. | Jan 2014 | B2 |
| 8665835 | Hussein et al. | Mar 2014 | B2 |
| 20020056066 | Gesbert et al. | May 2002 | A1 |
| 20030100344 | Garmonev et al. | May 2003 | A1 |
| 20030191856 | Lewis et al. | Oct 2003 | A1 |
| 20030228857 | Maeki | Dec 2003 | A1 |
| 20030229478 | Rappaport et al. | Dec 2003 | A1 |
| 20040018839 | Andric et al. | Jan 2004 | A1 |
| 20040042473 | Park et al. | Mar 2004 | A1 |
| 20040117226 | Laiho et al. | Jun 2004 | A1 |
| 20040196834 | Ofek et al. | Oct 2004 | A1 |
| 20040229621 | Misra | Nov 2004 | A1 |
| 20040248589 | Gwon et al. | Dec 2004 | A1 |
| 20040266442 | Flanagan et al. | Dec 2004 | A1 |
| 20050009531 | Lindquist et al. | Jan 2005 | A1 |
| 20050054339 | Merritt | Mar 2005 | A1 |
| 20050064844 | McAvoy | Mar 2005 | A1 |
| 20050111630 | Potorny et al. | May 2005 | A1 |
| 20050176440 | Sang et al. | Aug 2005 | A1 |
| 20050243723 | Randriamsay | Nov 2005 | A1 |
| 20050259571 | Battou | Nov 2005 | A1 |
| 20050267677 | Poykko et al. | Dec 2005 | A1 |
| 20050272444 | Heffield et al. | Dec 2005 | A1 |
| 20050277444 | Rensburg et al. | Dec 2005 | A1 |
| 20060083170 | Silva et al. | Apr 2006 | A1 |
| 20060221886 | Rao | Oct 2006 | A1 |
| 20060239224 | Borst et al. | Oct 2006 | A1 |
| 20060246844 | Kroboth et al. | Nov 2006 | A1 |
| 20070002765 | Kadaba et al. | Jan 2007 | A1 |
| 20070021151 | Mori et al. | Jan 2007 | A1 |
| 20070066298 | Hurst | Mar 2007 | A1 |
| 20070087756 | Hoffberg | Apr 2007 | A1 |
| 20070094729 | Hoefelmeyer et al. | Apr 2007 | A1 |
| 20070123271 | Dickinson | May 2007 | A1 |
| 20070129086 | Toone | Jun 2007 | A1 |
| 20070147297 | Diaz et al. | Jun 2007 | A1 |
| 20070195721 | Backes et al. | Aug 2007 | A1 |
| 20070197215 | Ben-Yehuda et al. | Aug 2007 | A1 |
| 20070218862 | Tatman et al. | Sep 2007 | A1 |
| 20070248039 | Backes et al. | Oct 2007 | A1 |
| 20080004078 | Barratt et al. | Jan 2008 | A1 |
| 20080016198 | Johnston-Watt et al. | Jan 2008 | A1 |
| 20080020801 | Fesas et al. | Jan 2008 | A1 |
| 20080039089 | Berkman et al. | Feb 2008 | A1 |
| 20080096566 | Brunner et al. | Apr 2008 | A1 |
| 20080125142 | Chang-Hung | May 2008 | A1 |
| 20080130790 | Forenza et al. | Jun 2008 | A1 |
| 20080207195 | Ranta et al. | Aug 2008 | A1 |
| 20080225714 | Denis | Sep 2008 | A1 |
| 20080261622 | Lee et al. | Oct 2008 | A1 |
| 20080268833 | Huang et al. | Oct 2008 | A1 |
| 20080311924 | Lucidarme | Dec 2008 | A1 |
| 20090003236 | Aoyama et al. | Jan 2009 | A1 |
| 20090003312 | Velazquez et al. | Jan 2009 | A1 |
| 20090023477 | Staudte | Jan 2009 | A1 |
| 20090036116 | Kim et al. | Feb 2009 | A1 |
| 20090047968 | Gunnarsson et al. | Feb 2009 | A1 |
| 20090075648 | Reed et al. | Mar 2009 | A1 |
| 20090075655 | Dobson et al. | Mar 2009 | A1 |
| 20090112932 | Skierkowski et al. | Apr 2009 | A1 |
| 20090131038 | MacNaughtan et al. | May 2009 | A1 |
| 20090163223 | Casey | Jun 2009 | A1 |
| 20090221297 | Wengerter et al. | Sep 2009 | A1 |
| 20090227261 | Tiirola et al. | Sep 2009 | A1 |
| 20090233625 | Ferguson | Sep 2009 | A1 |
| 20090257353 | Song et al. | Oct 2009 | A1 |
| 20090264130 | Catovic et al. | Oct 2009 | A1 |
| 20090312022 | Viorel et al. | Dec 2009 | A1 |
| 20090315736 | Reichl et al. | Dec 2009 | A1 |
| 20090323530 | Trigui et al. | Dec 2009 | A1 |
| 20100002603 | Gupta et al. | Jan 2010 | A1 |
| 20100008293 | Gupta et al. | Jan 2010 | A1 |
| 20100029282 | Stamoulis et al. | Feb 2010 | A1 |
| 20100046369 | Zhao et al. | Feb 2010 | A1 |
| 20100075682 | del Rio-Romero | Mar 2010 | A1 |
| 20100103911 | Ji | Apr 2010 | A1 |
| 20100111013 | Chou | May 2010 | A1 |
| 20100111047 | Yang et al. | May 2010 | A1 |
| 20100124934 | Mach | May 2010 | A1 |
| 20100130194 | Dickey | May 2010 | A1 |
| 20100149984 | Kapoor et al. | Jun 2010 | A1 |
| 20100159936 | Brisebois et al. | Jun 2010 | A1 |
| 20100169934 | Kennedy | Jul 2010 | A1 |
| 20100190488 | Jung et al. | Jul 2010 | A1 |
| 20100203881 | del Rio Romero et al. | Aug 2010 | A1 |
| 20100214939 | Ryan | Aug 2010 | A1 |
| 20100216453 | Kallin et al. | Aug 2010 | A1 |
| 20100216467 | Ryan et al. | Aug 2010 | A1 |
| 20100216477 | Ryan | Aug 2010 | A1 |
| 20100232318 | Sarkar | Sep 2010 | A1 |
| 20100235285 | Hoffberg | Sep 2010 | A1 |
| 20100254344 | Wei et al. | Oct 2010 | A1 |
| 20100267397 | Shen et al. | Oct 2010 | A1 |
| 20100278161 | Ore et al. | Nov 2010 | A1 |
| 20100284303 | Catovic et al. | Nov 2010 | A1 |
| 20100299419 | Ramankutty et al. | Nov 2010 | A1 |
| 20100303174 | Oh et al. | Dec 2010 | A1 |
| 20100309799 | Nunzi et al. | Dec 2010 | A1 |
| 20100311415 | Hamabe et al. | Dec 2010 | A1 |
| 20100311421 | Mach | Dec 2010 | A1 |
| 20100325267 | Mishra et al. | Dec 2010 | A1 |
| 20100327766 | Recker et al. | Dec 2010 | A1 |
| 20110009105 | Lee et al. | Jan 2011 | A1 |
| 20110014925 | Antic et al. | Jan 2011 | A1 |
| 20110028144 | Catovic et al. | Feb 2011 | A1 |
| 20110034179 | David et al. | Feb 2011 | A1 |
| 20110044165 | Ni et al. | Feb 2011 | A1 |
| 20110045865 | Viering et al. | Feb 2011 | A1 |
| 20110059744 | Won et al. | Mar 2011 | A1 |
| 20110090820 | Hussein et al. | Apr 2011 | A1 |
| 20110092195 | Hussein et al. | Apr 2011 | A1 |
| 20110096687 | Dottling et al. | Apr 2011 | A1 |
| 20110096688 | Sachs et al. | Apr 2011 | A1 |
| 20110105139 | On | May 2011 | A1 |
| 20110111700 | Hackett | May 2011 | A1 |
| 20110130135 | Trigui | Jun 2011 | A1 |
| 20110130146 | Trigui | Jun 2011 | A1 |
| 20110136478 | Trigui | Jun 2011 | A1 |
| 20110141972 | Oh et al. | Jun 2011 | A1 |
| 20110151881 | Chou et al. | Jun 2011 | A1 |
| 20110190016 | Hamabe et al. | Aug 2011 | A1 |
| 20110199985 | Cai et al. | Aug 2011 | A1 |
| 20110230222 | Reudink | Sep 2011 | A1 |
| 20110252477 | Sridhar et al. | Oct 2011 | A1 |
| 20110280157 | Suerbaum | Nov 2011 | A1 |
| 20110294527 | Brueck et al. | Dec 2011 | A1 |
| 20110312335 | Liu et al. | Dec 2011 | A1 |
| 20120009912 | Wang et al. | Jan 2012 | A1 |
| 20120009938 | Liu et al. | Jan 2012 | A1 |
| 20120009948 | Powers et al. | Jan 2012 | A1 |
| 20120026918 | Won et al. | Feb 2012 | A1 |
| 20120026941 | Ahmad et al. | Feb 2012 | A1 |
| 20120028584 | Zhang et al. | Feb 2012 | A1 |
| 20120028664 | Zhang et al. | Feb 2012 | A1 |
| 20120034919 | Nakata et al. | Feb 2012 | A1 |
| 20120066377 | Li et al. | Mar 2012 | A1 |
| 20120087257 | Larsson et al. | Apr 2012 | A1 |
| 20120087269 | Hussein et al. | Apr 2012 | A1 |
| 20120147765 | Wigren | Jun 2012 | A1 |
| 20120147828 | Wigren | Jun 2012 | A1 |
| 20120170478 | Doettling et al. | Jul 2012 | A1 |
| 20120182874 | Siomina et al. | Jul 2012 | A1 |
| 20120252479 | Morita et al. | Oct 2012 | A1 |
| 20120264470 | Bajj et al. | Oct 2012 | A1 |
| 20120270536 | Ratasuk et al. | Oct 2012 | A1 |
| 20120295609 | Li et al. | Nov 2012 | A1 |
| 20120327797 | Siomina et al. | Dec 2012 | A1 |
| 20130028107 | Ho et al. | Jan 2013 | A1 |
| 20130114464 | Tarraf et al. | May 2013 | A1 |
| 20130196650 | Futaki | Aug 2013 | A1 |
| 20130217435 | Tarraf et al. | Aug 2013 | A1 |
| 20130229914 | Suerbaum | Sep 2013 | A1 |
| 20130242736 | Tarraf et al. | Sep 2013 | A1 |
| 20130322395 | Kazmi et al. | Dec 2013 | A1 |
| 20150011197 | Tarraf et al. | Jan 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2129175 | Dec 2010 | EP |
| 1952657 | Aug 2011 | EP |
| WO 2007063426 | Jun 2007 | WO |
| WO 2012072445 | Jun 2012 | WO |
| Entry |
|---|
| Amirijoo et al., “Cell Outage Management in LTE Networks,” COST 2100 TD(9)941, Vienna, Austria, Sep. 28-30, 2009. |
| Blume et al., “Energy Savings in Mobile Networks Based on Adaptation to Traffic Statistics,” Bell Labs Technical Journal 15(2):77-94 (2010) © 2010 Alcatel-Lucent. |
| Lehtimaki et al., “A SOM Based Approach for Visualization of GSM Network Performance Data,” Helsinki University of Technology (2005). |
| Mueller et al., “A Cell Outage Detection Algorithm Using Neighbor Cell List Reports,” Springer-Verlag Berlin Heidelberg (2008). |
| “Self-Optimizing Networks: The Benefits of SON in LTE,” 4G Americas (Jul. 2011). |
