Some embodiments described herein relate generally to Self Optimizing Networks (SON), and, in particular, to methods and apparatus for managing simultaneous SON processes in a wireless network using a SON manager.
Some known wireless networks implement manual network optimization that typically consumes a large amount of human resources. As a lengthy process, the manual network optimization is typically performed only when needed or periodically with a long duration between actual implementations. As a result, the network or parts of the network will typically be non-optimized for relatively long periods of time. Thus, the network resource usage is typically not maximized, and the unused available network resources can result in significant revenue loss. Additionally, the quality of service is typically degraded, which affects the end users' overall satisfaction.
Accordingly, a need exists for methods and apparatus for implementing a SON manager that can automatically coordinate the work between different SON products or processes, to improve or maximize the overall network performance for the wireless networks.
In some embodiments, an apparatus includes a management module implemented in at least one of a memory or a processing device. The management module is configured to receive a signal associated with a value of a performance indicator that a first process module is configured to optimize using a metric. The management module is configured to optimize a value associated with the metric based at least in part on the value of the performance indicator that the first process module is configured to optimize and a value of a performance indicator that a second process module is configured to optimize using the metric. The management module is configured to send a signal to the first process module such that the first process module modifies a value of the metric based on the value associated with the metric.
In some embodiments, an apparatus includes a management module implemented in a memory or a processing device. The management module is configured to receive a signal associated with a value of a performance indicator that a first process module is configured to optimize using a first metric. The management module is configured to optimize a first value associated with the first metric based on the value of the performance indicator that the first process module is configured to optimize, and a first value of a performance indicator that a second process module is configured to optimize using the first metric. In some embodiments, the management module can be configured to optimize the first value associated with the first metric based on the value of the performance indicator that the first process module is configured to optimize, the first value of the performance indicator that the second process module is configured to optimize using the first metric, and a value of a second metric used to optimize the performance indicator that the first process module is configured to optimize. Furthermore, the management module is configured to send a signal to the first process module such that the first process module modifies a value of the first metric based on the first value associated with the first metric.
In some instances, the first value associated with the first metric can be a value to which to change the value of the first metric. The first metric or the second metric can be, for example, associated with a tilt of an antenna, or can be a number of cycles associated with the first process module. For other examples, the first process module or the second process module can be an antenna-based SON process module, a parameter-based SON process module, a load balancing SON process module or an interference reduction SON module.
As used herein, a module can be, for example, any assembly and/or set of operatively-coupled electrical components, 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 network optimization apparatus” is intended to mean a single physical device or a combination of physical devices.
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 a wireless transmission system 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
A base station 142, 144, 146 can be any device or infrastructure that can be wirelessly coupled to and communicate with one or more wireless communication devices (e.g., subscribers to the wireless network 100). Specifically, each base station 142, 144, 146 can be equipped with and configured to control one or more antennas (e.g., the antennas 152 and 154), which can be used to support data communications (e.g., transmit data to and/or receive data from) between the base station and the wireless communication devices that are distributed throughout a coverage area (i.e., sector) associated with that antenna. For example, the antenna 152 is used to support data communications between the base station 146 and wireless communication devices distributed within the coverage area 162; the antenna 154 is used to support data communications between a base station where the antenna 154 is located and wireless communication devices distributed within the coverage area 164. In some embodiments, a base station can be, for example, a cell site. In such embodiments, the coverage area associated with an antenna of that base station can be referred to as a cell.
In some embodiments, the connections between the network optimization apparatus 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 base station(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 apparatus 101 or another device operatively coupled to the network optimization apparatus 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 and current network configurations of the wireless network 100. Furthermore, the network database 120 can be configured to provide the stored information and/or data to the network optimization apparatus 101. The information and/or data can be used at the network optimization apparatus 101 to assist in monitoring and optimizing SON processes operated in the wireless network 100, as described in details with respect to
The network statistics and configurations provided from the network database 120 to the network optimization apparatus 101 can include a set of values and/or indicators that can be used to determine the performance of the wireless network 100 in various aspects. The set of values and/or indicators can include, for example, Key Performance Indicators (KPIs), mobile level measurements, cell level measurements, system level measurements, network metrics, configuration metrics (e.g., system configuration metrics, device configuration metrics), power indicators, indications of a network alarm, and/or the like.
In some embodiments, the KPIs provided from the network database 120 to the network optimization apparatus 101 can include, for example, a dropped call rate (i.e., the ratio between failed calls and a total number of calls requested), a transmitted radio power, traffic statistical values associated with a cell, total average transmitted power (e.g., in dBm), uplink total noise (e.g., in dBm), downlink/uplink load factor (e.g., in percentage), uplink interference noise rise (e.g., in dB), number of downlink/uplink radio links used, connection success rate (e.g., in percentage), average number of attempted users, average number of connected users, average number of used codes, ratio of handoff (e.g., in percentage), connection success, downlink/uplink throughput (e.g., in kbps), etc. In some embodiments, the KPIs can include cell level KPIs (e.g., statistics associated with handover and neighbor list as listed above), user equipment level KPIs (e.g., a signal strength indicator for a wireless communication device), as well as system level KPIs (e.g., number of connected users across the network).
In some embodiments, the set of values and/or indicators can include a network statistic representing the capacity of the wireless network 100. In some embodiments, such a capacity can be measured, for example, by a total number of calls, an amount of delivered data in bits and/or a throughput (e.g., overall data rate) in case of data calls.
In some embodiments, the set of values and/or indicators can include a number of handovers of end-user equipments (i.e., wireless communication devices) that are transitioning between different serving sectors (i.e., coverage areas). Specifically, each active user equipment is associated with one or more serving sectors. As the user equipment moves between the coverage areas of different antennas, the serving sectors associated with the user equipment can potentially change due to, for example, a new serving sector having a better signal quality than an existing serving sector associated with the user equipment. Particularly, in a soft handover, the user equipment can be associated with more than one serving sector at the same time because the signal quality of the different serving sectors is similar. In some embodiments, the number of handovers between different serving sectors can be used as an indicator of how close those serving sectors are to each other, and/or an indicator of the dependency between those different serving sectors.
In some embodiments, the set of values and/or indicators can include a neighbor list, which includes a list of potential neighbors (i.e., neighbor serving sectors) for a user equipment (i.e., wireless communication device) in a given serving sector, and/or neighbor priorities of those potential neighbors. A potential neighbor for a user equipment can be a neighbor serving sector that can potentially provide services to that user equipment as part of a handover operation when the user equipment is traveling between different coverage areas. Each potential neighbor for a user equipment can be associated with a neighbor priority that indicates the priority (or likelihood) of the corresponding neighbor serving sector being selected to provide services to the user equipment. In some embodiments, such a neighbor priority can be determined based on, for example, a measurement (e.g., signal strength, distance to a base station) associated with the quality of the services that can be potentially provided to the user equipment if the corresponding neighbor serving sector is selected. In some embodiments, multiple neighbor lists of the serving sectors that are currently serving the user equipment can be combined to define a single neighbor list to be sent to the user equipment. In such embodiments, the user equipment can use this combined list to search for additional potential neighbors for handover operations.
The network optimization apparatus 101 can be any device configured to control and/or coordinate SON processes operated in the wireless network 100 by executing, for example, a SON manager. For example, in a highly congested network that is to be optimized in multiple aspects (e.g., load balancing, co-channel interference, neighbor list, handovers, self-healing, etc.), multiple SON processes and/or other optimization processes can be operated across the wireless network 100 at the same time. Many dependencies exist between different SON processes. Dependencies can also exist between metrics that are used in the different SON processes, and between configurations of network devices that operate the SON processes. In such embodiments, a SON manager can be executed (e.g., at a network optimization apparatus) to manage the simultaneous SON processes, as described in further details with respect to
In some embodiments, the network optimization apparatus 101 can be, for example, a computer device, a server device, an application server, a mobile device, a workstation, and/or the like. As shown in
In some embodiments, the SON manager for managing the SON processes operated in the wireless network 100 can be executed at a processor of the network optimization apparatus 101.
Each module in the processor 200 can be any combination of hardware-based module (e.g., a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), a digital signal processor (DSP)) and/or software-based module (e.g., a module of computer code stored in memory and/or executed at the processor 200) capable of performing one or more specific functions associated with that module. The processor 200 can be any suitable processor configured to run and/or execute those modules.
Each of the SON process modules in the processor 200 (e.g., the SON process modules 202 and 204) can be configured to execute one or more SON processes in the wireless network 100. In some embodiments, each SON process module in the processor 200 can be configured to execute, for example, an antenna-based SON process, a parameter-based SON process, and/or the like. In some embodiments, the combination of the SON process modules 202 and 204 can be, for example, a combination of a load balancing SON process module and an interference reduction SON process module, a combination of a load balancing SON process module and a neighbor list SON process module, a combination of a load balancing SON process module and a handover SON process module, a combination of a self-healing SON process module and an interference reduction SON process module, or any suitable combination of SON process modules. Furthermore, as shown in
Specifically, the SON manager module 206 can be configured to schedule different SON process modules by taking various actions. For example, the SON manager module 206 can be configured to start (e.g., initiate) and/or stop different SON processes. That is, the SON manager module 206 can decide or accept the starting of a SON process, and decide when to stop a SON process. For another example, the SON manager module 206 can be configured to pause and/or resume different SON processes. In some embodiments, the SON manager module 206 can pause a SON process until certain conditions are met; and after the conditions are met, the SON manager module 206 can resume that SON process. Additionally, the SON manager module 206 can be configured to choose to execute multiple SON processes in serial or parallel; prioritize different SON processes; determine a running time for a SON process; and/or the like.
In some embodiments, the SON manager module 206 can be configured to transfer data and/or control signals (e.g., KPIs, messages, commands, etc.) between different SON process modules. In some embodiments, the SON manager module 206 can be configured to apply rules and/or policies to make modifications on the SON process modules, thus to control the corresponding SON processes.
In some embodiments, the SON manager module 206 can be configured to coordinate with different SON processes to harmonize modifications, which are generated during those SON processes, on network devices (e.g., base stations) operating the SON processes. Signals representing the harmonized modifications are then sent to the associated base stations for implementation. As such, the SON manager module 206 can be configured to check if any potential conflict exists between the modifications from the different SON processes before sending the signals to the associated base stations. If any potential conflict is determined, the SON manager module 206 can be configured to, for example, accept one of the modifications and suppress the others; send signals representing the potential conflict to the SON processes that are involved in the conflict and instruct the SON processes to recalculate their modification inputs; send signals representing the modification inputs of the other parties (e.g., the other SON processes) to the SON processes that are involved in the potential conflict and receive responses from the SON processes about the acceptability of the modification inputs of the other parties; and/or act as a communication link between the SON processes to enable the SON processes to send signals between each other.
While shown in
Returning to
The SON manager module 206 can then be configured to send each optimized value of the metrics to each corresponding SON process module (e.g., the SON process module 202, 204 in
As a centralized controller over the multiple SON processes operating in the wireless network 100, the SON manager module 206 can be configured to manage the multiple SON processes in a cooperative manner such that conflicts between the multiple SON processes can be avoided, minimized or reduced. In some embodiments, for example, the SON manager module 206 can be configured to manage two SON processes (e.g., a load balancing SON process and an interference reduction SON process) operating in the wireless network 100, each of which can potentially modify a common metric (e.g., an antenna tilt). The SON manager module 206 can control the modifications on the common metric from the two SON processes such that a modification on the common metric from one of the two SON processes is not contradictory, or does not negatively affect, a modification on the common metric from the other of the two SON processes. For example, if the SON manager module 206 instructs one SON process to increase the metric value from an original value to a new value, the SON manager module 206 will not instruct the other SON process to decrease the metric value from the new value back to the original value. In such a manner, the SON manager module 206 can eliminate a ping-pong effect between the two SON processes attempting to modify a common metric. Thus, the centralized control pattern implemented at the SON manager module 206 can avoid, minimize or reduce contradictive operations by SON processes.
In some embodiments, a SON manager can be configured to simultaneously manage various types of SON processes, including antenna-based SON processes and parameter-based SON processes to optimize values of various dependent metrics for solving one problem or achieving an optimization objective. Herein parameter-based SON processes are referred to as parameter-based SON processes that are not associated with antennas, that is, metrics modified by parameter-based SON processes are non-antenna metrics.
As shown in
In some instances, the actions of the SON manager 310 can depend on which SON processes are currently running, as well as the relations and/or dependencies between the different SON processes. For example, if two SON processes operating in a wireless network (e.g., the wireless network 100 in
At 402, the SON manager can be configured to execute the antenna-based SON process to modify antenna metric values to resolve the problem (e.g., load balancing). The antenna metric values can be associated with, for example, the antenna tilts. After one or a predetermined number of cycles of executing the antenna-based SON process (e.g., modify each antenna metric value to a new value) are completed, at 404, the SON manager can check whether the problem has been resolved or not. If the problem has been resolved, at 410, the SON manager can terminate the optimization process. Otherwise, if the problem has not been resolved, at 406, the SON manager can pause the antenna-based SON process and execute the parameter-based SON process (e.g., a handover (HO) parameter-based load balancing SON process) to modify other metric values that are not associated with the antenna. After one or a predetermined number of cycles of executing the parameter-based SON process (e.g., modify each of the other metric values to a new value) are completed, at 408, the SON manager can check whether the problem has been resolved or not. If the problem has been resolved, at 412, the SON manager can terminate the optimization process. Otherwise, if the problem has not been resolved, the SON manger can iterate the optimization process by repeating the steps 402-408 as illustrated in
In the optimization process illustrated in
At 502, the SON manager can execute the antenna-based load balancing SON process to optimize load balancing by modifying antenna metric values (e.g., antenna tilts). After one or a predetermined number of cycles of executing the antenna-based load balancing SON process are completed, at 504, the SON manager can check whether the problem (i.e., optimization of load balancing) has been resolved or not. If the problem has been resolved, at 506, the SON manager can terminate the optimization process. Otherwise, if the problem has not been resolved, at 508, the SON manager can check whether a tilt constraint associated with the antenna has been reached or not. If the tilt constraint has not been reached, the SON manager can continue executing the antenna-based load balancing SON process by repeating the steps 502-508. Otherwise, if the tilt constraint has been reached, at 510, the SON manager can stop the antenna-based load balancing SON process and execute the handover-based load balancing SON process to optimize load balancing by modifying handover metric values, until the optimization of load balancing is completed.
Similar to the example illustrated in
At 602, the SON manager can execute the antenna-based self-healing SON process to achieve self-healing by modifying antenna metric values (e.g., antenna tilts). After one or a predetermined number of cycles of executing the antenna-based self-healing SON process are completed, at 604, the SON manager can check whether the problem has been resolved (i.e., the outage has been recovered) or not. If the problem has been resolved, at 610, the SON manager can check whether the outage has been recovered, and if the outage has been recovered, corresponding metrics of the wireless network (e.g., antenna tilts, metric values associated with modulation and/or coding schemes) can be reset at 612. Otherwise, if the problem has not been resolved, at 606, the SON manager can check whether a tilt constraint associated with the antenna has been reached or not. If the tilt constraint has not been reached, the SON manager can continue executing the antenna-based self-healing SON process by repeating the steps 602-606. Otherwise, if the tilt constraint has been reached, at 608, the SON manager can stop the antenna-based self-healing SON process and execute the parameter-based SON process for adjusting modulation and/or coding schemes. Specifically, the SON manager can be configured to execute the parameter-based SON process to achieve self-healing by modifying metric values associated with modulation and/or coding schemes. When the parameter-based SON process is executed, at 610, the SON manger can regularly check whether the outage has been recovered, and if the outage has been recovered, the self-healing process is completed and corresponding metrics of the wireless network can be reset at 612.
In the examples of
In some embodiments, a SON manager can be configured to coordinate multiple SON processes with different optimization objectives (e.g., load balancing, self-healing, interference reduction, neighbor relations, etc.), where the multiple SON processes are associated with a common set of metrics (e.g., antenna tilts, non-antenna metrics). Execution of those multiple SON processes can depend on the set of metrics (e.g., use part or all of the metrics as an input to the execution), and/or affect the set of metrics (e.g., modify part or all of the metrics as a result of the execution). Thus, the SON manager coordinate the execution of the multiple SON processes such that execution of one SON process will not adversely affect execution of another SON process.
For example, three SON processes operated in a wireless network with different optimization objectives as load balancing, self-healing or interference reduction can all use antenna tilts as a metric to adjust the antennas to meet their corresponding optimization objectives. Because tilt changes made to meet one of the three optimization objectives may be contrary to the other optimization objectives, the three SON processes can be coordinated by the SON manager. In addition, tilt changes made to meet these collective optimization objectives may negatively affect cell neighbor relations, which in turn can negatively affect, for example, the handover performance of the wireless network. Hence, the SON manager also can coordinate the optimization objectives with an Automatic Neighbor Relations (ANR) update.
At 702, the SON manager can be configured to execute the antenna-based load balancing SON process to optimize load balancing by modifying antenna metric values (e.g., antenna tilts). After one or a predetermined number of cycles of executing the antenna-based load balancing SON process are completed, at 704, the SON manager can be configured to execute the ANR SON process to adjust any neighbor relation that is affected by the changes (e.g., tilt changes) made in the previous step 702. After one or a predetermined number of cycles of executing the ANR SON process are completed, at 706, the SON manager can check whether the problem (i.e., optimization of load balancing and/or neighbor relations) has been resolved or not. If the problem has been resolved, at 708, the SON manager can stop the ANR SON process. Otherwise, if the problem has not been resolved, the SON manager can continue executing the antenna-based load balancing SON process and the ANR SON process by repeating the steps 702-706, as illustrated in
Similar to the example of
At 802, the SON manager can be configured to execute the antenna-based load balancing SON process to optimize load balancing by modifying antenna metric values (e.g., antenna tilts). After one or a predetermined number of cycles of executing the antenna-based load balancing SON process are completed, at 804, the SON manager can check whether the problem (i.e., load balancing) has been resolved or not. If the problem has not been resolved, the SON manager can continue executing the antenna-based load balancing SON process by repeating the step 802, as illustrated in
In some embodiments, the SON processes operated in the example of
In some embodiments, a SON manager can be configured to manage which elements (e.g., metrics) each SON process should handle. As an example,
In some embodiments, a SON manager can be configured to manage multiple SON processes with different granularities. As an example,
In
In
Specifically, during a period 1021, the SON manager can execute a first phase of the load balancing SON process based on, for example, one or more KPIs received from other devices of the wireless network (e.g., during a previous observation period not shown in
After the first phase of the neighbor list SON process is completed and any modified metric value is stored, the SON manager can be configured to observe the effects of the first phase of the neighbor list SON process on the wireless network in a second observation period 1024. After the second observation period 1024, the SON manager can execute a second phase of the load balancing SON process during a period 1025. Particularly, the SON manager can execute the second phase of the load balancing SON process based on, for example, one or more KPIs received from other devices of the wireless network and/or one or more metric values stored in the network database during the second observation period 1024 and the period 1023. As a result, one or more KPIs and/or metric values used by the second phase of the load balancing SON process executed during the period 1025 can be updated or modified by the first phase of the neighbor list SON process executed during the period 1023. Similarly, a third observation period 1026 and a second phase of the neighbor list SON process during a period 1027 can be sequentially executed. In such an iterative manner, the SON manager can manage different interleaved SON processes to incrementally optimize the wireless network in terms of multiple optimization objectives.
Compared to the method with the relatively lower granularity illustrated in
At 1102, the SON manager can be configured to receive a signal associated with a value of a performance indicator that a first process module is configured to optimize using a first metric. In some embodiments, the first process module can be, for example, a load balancing SON process module, a self-healing SON process module, an interference reduction SON process module, an ANL SON process module, and/or the like. In some embodiments, the performance indicator can be, for example, a KPI.
In some embodiments, the first process module can be an antenna-based SON process module. In such embodiments, the first metric can be a metric associated with an antenna, such as a tilt of an antenna. In other embodiments, the first process module can be a parameter-based (i.e., non-antenna) SON process module. In such embodiments, the first metric can be a non-antenna metric such as a number of cycles associated with the first process module.
At 1104, the SON manager can be configured to optimize a value associated with the first metric based on the value of the performance indicator that the first process module is configured to optimize, a value of a performance indicator that a second process module is configured to optimize using the first metric, and/or a value of a second metric used to optimize the performance indicator that the first process module is configured to optimize. Similar to the first process module, the second process module can be an antenna-based SON process module or a parameter-based SON process module. The second process module can be, for example, a load balancing SON process module, a self-healing SON process module, an interference reduction SON process module, an ANL SON process module, and/or the like. In some embodiments, the value associated with the first metric can be a value to which to change the value of the first metric.
At 1106, the SON manager can send a signal to the first process module including the value associated with the first metric such that the first process module modifies a value of the first metric based on the value associated with the first metric. In some embodiments, the signal can include the value of the second metric.
Furthermore, in some embodiments, the SON manager can receive a signal associated with a second value of the performance indicator that the second process module is configured to optimize. In response to the signal, the SON manager can optimize a second value associated with the first metric based on the value of the performance indicator that the first process module is configured to optimize, and the second value of the performance indicator that the second process module is configured to optimize. The SON manager can further send a signal to the second process module such that the second process module modifies the value of the first metric based on the second value associated with the first metric.
At 1202, the SON manager can be configured to receive a signal associated with a value of a performance indicator that a first process module is configured to optimize using a first metric and a second process module is configured to optimize using a second metric. The first process module and the second process module can be an antenna-based SON process module and/or a parameter-based SON process module. In some embodiments, the first process module and the second process module can be, for example, a load balancing SON process module, a self-healing SON process module, an interference reduction SON process module, an ANL SON process module, and/or the like.
At 1204, the SON manager can be configured to optimize a value associated with the first metric and a value associated with the second metric based on the value of the performance indicator. In some embodiments, the value associated with the first metric or the second metric can be a value to which to change the value of the first metric or the second metric.
At 1206, the SON manager can be configured to send a signal to the first process module such that the first process module modifies a value of the first metric based on the value associated with the first metric. Meanwhile, in some embodiments, the SON manager can be configured to send the value of the second metric to the first process module, such that the first process module modifies the value of the first metric based on the value of the second metric as well.
At 1208, similar to the step 1207, the SON manager can send a signal to the second process module such that the second process module modifies a value of the second metric based on the value associated with the second metric. In some embodiments, the SON manager can send the signals to the first process module and the second process module at substantially the same time. In other embodiments, the SON manager can send the signals to the first process module and the second process module at different times.
In some embodiments, the value of the performance indicator is a value of the performance indicator at a first time. The SON manager can send the signal to the first process module at a second time after the first time. The SON manager can then be configured to receive a signal associated with a second value of the performance indicator at a third time after the second time. As a result, the SON manager can be configured to optimize the value associated with the second metric based on the value of the performance indicator at the first time and the value of the performance indicator at the third time.
While shown and described herein as the SON manager being implemented in a wireless network, in other embodiments, a SON manager can also be implemented in other types of networks such as a wired network or a hybrid wireless-wired network. In such embodiments, the SON manager does not necessarily manage antenna-based SON processes or coordinate between antenna-based SON processes and parameter-based SON processes. Instead, the SON manager may manage and coordinate between different types of parameter-based SON processes in a similar method as described herein.
While shown and described herein as a SON process module being an antenna-based SON process module or a parameter-based SON process module, in other embodiments, a SON process module can be a combined antenna- and parameter-based SON process module. Such a combined SON process module can control a SON process where both antenna metric values (e.g., antenna tilts) and non-antenna metric values (e.g., parameters in a modulation scheme) can be modified.
While shown and described with respect to
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.
This application claims priority to and the benefit of U.S. Provisional Patent Application No. 61/532,850, filed Sep. 9, 2011, and entitled “Self Optimizing-Organizing Network Manager,” which is incorporated herein by reference in its entirety.
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 |
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 |
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 |
7929457 | Healy et al. | Apr 2011 | B2 |
7941136 | Reed | 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 | 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 |
8971302 | Lee | Mar 2015 | 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 | 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 |
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-Yahuda 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 |
20080032677 | Catovic | Feb 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 |
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 | 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 |
20090227251 | Lei | 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 | 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 |
20100151850 | Majmundar | 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 |
20100302954 | Tirpak et al. | Dec 2010 | A1 |
20100303174 | Oh et al. | Dec 2010 | A1 |
20100309799 | Nunzi | Dec 2010 | A1 |
20100311415 | Hamabe et al. | Dec 2010 | A1 |
20100311421 | Mach | Dec 2010 | A1 |
20100325267 | Mishra | Dec 2010 | A1 |
20100327766 | Recker et al. | Dec 2010 | A1 |
20110009105 | Lee | 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 | 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 |
20110249558 | Raaf | Oct 2011 | A1 |
20110252477 | Sridhar | 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 |
20120214477 | Wieslawa | Aug 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 |
20130003548 | Sridhar | Jan 2013 | A1 |
20130005297 | Sanders | Jan 2013 | A1 |
20130028107 | Ho | Jan 2013 | A1 |
20130114464 | Tarraf et al. | May 2013 | A1 |
20130189991 | Rose | Jul 2013 | A1 |
20130217435 | Tarraf et al. | Aug 2013 | A1 |
20130229914 | Suerbaum | 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 2010121251 | Oct 2010 | WO |
WO 2010132884 | Nov 2010 | WO |
WO 2011005524 | Jan 2011 | WO |
WO 2011046705 | Apr 2011 | WO |
WO 2012072445 | Jun 2012 | WO |
WO 2012162070 | Nov 2012 | WO |
WO 2013036793 | Mar 2013 | WO |
WO 2013070900 | May 2013 | WO |
Entry |
---|
International Search Report and Written Opinion mailed Jun. 18, 2010 for PCT Application No. PCT/US2010/31603. |
U.S. Office Action mailed Oct. 13, 2010 for U.S. Appl. No. 12/385,752, filed Apr. 17, 2009. |
U.S. Office Action mailed May 5, 2011 for U.S. Appl. No. 12/385,752, filed Apr. 17, 2009. |
International Search Report and Written Opinion mailed Nov. 24, 2010 for PCT Application No. PCT/US2010/050627. |
International Search Report and Written Opinion mailed Nov. 15, 2010 for PCT Application No. PCT/US2010/048929. |
U.S. Office Action mailed Dec. 22, 2011 for U.S. Appl. No. 12/718,189, filed Mar. 5, 2010. |
U.S. Office Action mailed Dec. 29, 2011 for U.S. Appl. No. 12/634,057, filed Dec. 9, 2009. |
International Search Report and Written Opinion mailed Nov. 3, 2010 for PCT Application No. PCT/US2010/048927. |
Amirijoo et al., “Cell Outage Management in LTE Networks,” Cost 2100 TD(9)941, Vienna, Austria, Sep. 28-30, 2009. |
Mueller et al., “A Cell Outage Detection Algorithm Using Neighbor Cell List Reports” 2008. |
U.S. Office Action mailed Feb. 27, 2012 for U.S. Appl. No. 12/385,752, filed Apr. 17, 2009. |
U.S. Office Action mailed Jun. 6, 2012 for U.S. Appl. No. 12/634,057, filed Dec. 9, 2009. |
U.S. Final Office Action mailed Jul. 13, 2012 for U.S. Appl. No. 12/385,752, filed Apr. 17, 2009. |
U.S. Final Office Action mailed Aug. 29, 2012 for U.S. Appl. No. 12/718,189, filed Mar. 5, 2010. |
International Search Report and Written Opinion mailed Nov. 5, 2012 for PCT Application No. PCT/US2012/054204. |
“Self-Optimizing Networks: The Benefits of SON in LTE,” 4G americas, Jul. 2011. |
International Search Report and Written Opinion mailed Feb. 5, 2013 for PCT Application No. PCT/US2012/064131. |
U.S. Office Action mailed Mar. 18, 2013 for U.S. Appl. No. 12/580,604, filed Oct. 16, 2009. |
Lehtimaki et al., “A SOM Based Approach for Visualization of GSM Network Performance Data,” Helsinki University of Technology, 2005. |
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. |
International Search Report and Written Opinion for International Application No. PCT/US2012/038243, mailed Aug. 17, 2012. |
Office Action for U.S. Appl. No. 13/670,830, mailed Jan. 5, 2015. |
International Search Report and Written Opinion for International Application No. PCT/US2013/026102, mailed Apr. 29, 2013. |
Office Action for U.S. Appl. No. 13/273,354, mailed Apr. 16, 2013. |
Office Action for U.S. Appl. No. 12/718,189, mailed Jan. 16, 2014. |
Office Action for U.S. Appl. No. 12/718,189, mailed Jul. 31, 2014. |
Office Action for U.S. Appl. No. 12/580,604, mailed Dec. 3, 2012. |
Extended European Search Report for European Patent Application No. 12829986.4, mailed Jun. 2, 2015. |
Sater, et al., “Self-Optimizing Networks: The Benefits of SON in LTE.” (Jul. 2011). 4G Americas. |
Feng, Sujuan, and Eiko Seidel. “Self-organizing networks (SON) in 3GPP long term evolution.” Nomor Research GmbH, Munich, Germany (2008). |
Number | Date | Country | |
---|---|---|---|
20130242736 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
61532850 | Sep 2011 | US |