Method and device for troubleshooting of low-performance cell, electronic equipment and storage medium

Abstract

The application provides a problem troubleshooting method and device for a low-efficiency cell, electronic equipment and a computer readable storage medium, and relates to the technical field of network performance evaluation. The problem troubleshooting method comprises the following steps: collecting service volume index data of all cells in a network, and obtaining a list of low-efficiency cells according to the service volume index data and corresponding index thresholds, wherein the service volume index comprises daily average traffic and at least one of the following: daily average number of users and daily average PRB utilization rate; determining whether a target low-efficiency cell in the list has a network configuration problem; and in response to the target low-efficiency cell not having a network configuration problem, performing on-site troubleshooting on the target low-efficiency cell. The method at least solves the problems in the related art that resource efficiency is not focused on improving, software and hardware resources in the existing network are not activated, a target low-efficiency cell cannot be quickly and accurately locked, and network resources and human resources are wasted. The method is suitable for network performance detection and optimization scenarios.

Description

Technical Field

[0001] This invention relates to the field of network performance evaluation technology, and in particular to a method, apparatus, electronic device, and computer-readable storage medium for troubleshooting inefficient cells. Background Technology

[0002] In the traditional 4G (4th generation mobile communication technology) era, as the number of users gradually increased, 4G networks evolved from single-carrier to multi-carrier or even fully configured. However, when dealing with inefficient cells, due to a lack of experience and unfamiliarity with professional skills, the traditional method for network optimization staff was to check fault alarms and interference. If no problems were found, they would go directly to the site to investigate.

[0003] Therefore, network optimization staff focus more on performance indicators such as call connection rate and call drop rate, rather than on improving resource efficiency and making full use of the existing network's hardware and software resources. They are unable to quickly and accurately identify target low-efficiency cells, which can easily lead to a waste of network and human resources and reduce user experience. Consequently, the handling of low-efficiency cells results in a large workload, long time, low efficiency, and unsatisfactory results. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to address the above-mentioned shortcomings of the prior art by providing a method, apparatus, electronic device and computer-readable storage medium for troubleshooting inefficient cells. This method can achieve rapid and accurate location of target inefficient cells, thereby improving the efficiency of troubleshooting and handling of target inefficient cells, reducing the waste of network resources and human resources, improving network quality and efficiency, avoiding the risk of inefficient operation and improving user experience.

[0005] In a first aspect, the present invention provides a method for troubleshooting inefficient cells, comprising: collecting traffic volume indicator data of all cells in the network, and obtaining a list of inefficient cells based on the traffic volume indicator data and corresponding indicator thresholds, wherein the traffic volume indicators include average daily traffic and at least one of the following: average daily number of users, average daily PRB utilization rate; determining whether there are network configuration problems in the target inefficient cells in the list; and, in response to the determination that there are no network configuration problems in the target inefficient cells, conducting on-site troubleshooting of the target inefficient cells.

[0006] Preferably, determining whether a target low-performance cell in the list has a network configuration problem specifically includes: determining whether the target low-performance cell is a single-layer network cell; in response to the target low-performance cell being a multi-layer network cell, determining whether other cells in the same sector are low-performance cells; in response to the target low-performance cell being a single-layer network cell, or other cells in the same sector being low-performance cells, determining whether the number of fault alarms, duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions; in response to the number of fault alarms, duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meeting preset conditions, determining that the target low-performance cell does not have a network configuration problem.

[0007] Optionally, after determining whether other cells in the same sector are inefficient cells in response to the target inefficient cell being a multi-layer network cell, the problem-solving method for inefficient cells further includes: in response to the other cells in the same sector not being inefficient cells, performing service balancing optimization on all cells in the network. The determination of whether the number of fault alarms, duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions specifically includes: determining whether the number of fault alarms is greater than a first preset value; determining whether the duration is greater than or equal to a second preset value; determining whether the idle noise floor is... If the number of fault alarms is less than or equal to the third preset value; determine if the cell power is greater than or equal to the fourth preset value; determine if the minimum access threshold is greater than or equal to the fifth preset value; determine if the neighbor cell configuration is missing; in response to the following conditions: the number of fault alarms is less than or equal to the first preset value, the duration is less than the second preset value, the idle noise floor is greater than the third preset value, the cell power is less than the fourth preset value, the minimum access threshold is less than the fifth preset value, and the neighbor cell configuration is fully configured, determine that the number of fault alarms, the duration, the idle noise floor, the cell power, the minimum access threshold, and the neighbor cell configuration all meet the preset conditions.

[0008] Optionally, after determining whether there is a network configuration problem in the target low-performance cell in the list, and before conducting on-site investigation of the target low-performance cell in response to the absence of a network configuration problem, the problem investigation method for low-performance cells further includes: optimizing the network configuration problem in response to the presence of a network configuration problem in the target low-performance cell.

[0009] Preferably, the response to a network configuration problem in the target inefficient cell, and the optimization of the network configuration problem, specifically includes: responding to a fault alarm number greater than a first preset value, performing fault alarm processing; responding to a duration greater than or equal to a second preset value, continuing observation; responding to an idle noise floor less than or equal to a third preset value, performing interference investigation; responding to a cell power greater than or equal to a fourth preset value, performing power increase; responding to a minimum access threshold greater than or equal to a fifth preset value, adjusting the minimum access threshold; and responding to a missing neighbor cell configuration, adding neighbor cells.

[0010] Preferably, in response to the absence of network configuration problems in the target low-efficiency cell, an on-site inspection of the target low-efficiency cell is conducted, specifically including: determining whether the target low-efficiency cell is an indoor distributed antenna system (DAS) cell or a macro base station cell; in response to the target low-efficiency cell being an indoor DAS cell, determining whether the indoor DAS system has been damaged; in response to the indoor DAS system being damaged, performing system repair; and in response to the indoor DAS system not being damaged, reusing and dismantling existing equipment in the target low-efficiency cell.

[0011] Preferably, the step of conducting on-site investigation of the target low-efficiency cell in response to the absence of network configuration problems further includes: determining whether there is coverage demand on-site if the target low-efficiency cell is a macro cell; reusing existing equipment in the target low-efficiency cell if there is no coverage demand on-site; determining whether RF optimization can be performed if there is coverage demand on-site; performing RF optimization if it can be performed; determining whether construction rectification can be carried out if it cannot be performed; performing construction rectification if it can be performed; and reusing existing equipment in the target low-efficiency cell if construction rectification cannot be performed.

[0012] Secondly, the present invention also provides a problem-solving device for inefficient cells, comprising: an acquisition module, a judgment module, and an on-site investigation module. The acquisition module is used to collect traffic volume indicator data of all cells in the network and obtain a list of inefficient cells based on the traffic volume indicator data and corresponding indicator thresholds. The traffic volume indicators include average daily traffic and at least one of the following: average daily number of users and average daily PRB utilization rate. The judgment module is connected to the acquisition module and is used to determine whether there is a network configuration problem in the target inefficient cell in the list. The on-site investigation module is connected to the judgment module and is used to perform on-site investigation of the target inefficient cell in response to the determination that there is no network configuration problem in the target inefficient cell.

[0013] Thirdly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the problem-solving method for inefficient cells provided in the first aspect above.

[0014] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the problem-solving method for inefficient cells provided in the first aspect.

[0015] This invention provides a method, apparatus, electronic device, and computer-readable storage medium for troubleshooting inefficient cells. By conducting lifecycle and performance verification analysis on all cells in the network, a list of inefficient cells is compiled. Then, network configuration problems are investigated and addressed in target inefficient cells on the list. Inefficient cells without network configuration problems are investigated on-site. Therefore, this invention enables rapid and accurate location of target inefficient cells, thereby improving the efficiency of troubleshooting and handling, reducing network and human resource waste, improving network quality and efficiency, mitigating the risks of inefficient operation, and enhancing user experience. Attached Figure Description

[0016] Figure 1 This is a flowchart of a problem-solving method for inefficient cells according to Embodiment 1 of the present invention;

[0017] Figure 2 This is a flowchart of a method for determining an inefficient cell according to Embodiment 1 of the present invention;

[0018] Figure 3 This is a flowchart of a method for troubleshooting network configuration problems in an inefficient cell according to Embodiment 1 of the present invention;

[0019] Figure 4 This is a flowchart of an on-site investigation method for inefficient residential communities according to Embodiment 1 of the present invention;

[0020] Figure 5 This is a schematic diagram of a problem-finding device for inefficient residential communities according to Embodiment 2 of the present invention;

[0021] Figure 6 This is a schematic diagram of a problem-finding device for inefficient residential communities according to Embodiment 3 of the present invention. Detailed Implementation

[0022] To enable those skilled in the art to better understand the technical solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0023] It is understood that the specific embodiments and accompanying drawings described herein are merely for explaining the invention and are not intended to limit the invention.

[0024] It is understood that, without conflict, the various embodiments and features in the embodiments of the present invention can be combined with each other.

[0025] It is understood that, for ease of description, only the parts related to the present invention are shown in the accompanying drawings, while the parts unrelated to the present invention are not shown in the drawings.

[0026] It is understood that each unit or module involved in the embodiments of the present invention may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple units or modules may be integrated into one entity structure.

[0027] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this invention may occur in a different order than that marked in the accompanying drawings.

[0028] It is understood that the flowcharts and block diagrams of this invention illustrate the possible architecture, functions, and operations of systems, apparatuses, devices, and methods according to various embodiments of this invention. Each block in the flowchart or block diagram may represent a unit, module, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagram and flowchart can be implemented using a hardware-based system to achieve the specified function, or using a combination of hardware and computer instructions.

[0029] It is understood that the units and modules involved in the embodiments of the present invention can be implemented by software or by hardware. For example, the units and modules can be located in a processor.

[0030] Example 1:

[0031] like Figure 1 As shown in the figure, this embodiment provides a method for troubleshooting problems in inefficient cells.

[0032] Methods for identifying problems in inefficient residential communities include:

[0033] Step S101: Collect service volume indicator data of all cells in the network, and obtain a list of inefficient cells based on the service volume indicator data and the corresponding indicator thresholds. The service volume indicators include average daily traffic and at least one of the following: average daily number of users and average daily PRB utilization rate.

[0034] In this embodiment, as Figure 2 As shown in one method for identifying inefficient cells, an inefficient cell is... Figure 2This implementation identifies low-performing cells by monitoring and collecting traffic data from all cells in the network. It filters data based on daily average traffic, daily average number of users, and daily average PRB (Physical Resource Block) utilization rate. Based on these traffic data and corresponding threshold values, it identifies inefficient cells and outputs a list of them. In this example, a threshold of 500MB for daily average traffic, 8 users for daily average users, and 5% for daily average PRB utilization rate is used. If a target cell's daily average traffic is below 500MB, its daily average number of users is below 8, or its daily average PRB utilization rate is below 5%, then the target cell is considered inefficient. This implementation performs lifecycle and performance verification analysis on all cells in the network, using algorithms to statistically determine target inefficient cells. This enables rapid and accurate identification of inefficient cells across the network, helping to pinpoint the root cause of problems and identify the specific reasons for inefficiency.

[0035] Step S102: Determine whether there are network configuration problems in the target low-efficiency cells in the list.

[0036] Specifically, step S102: Determine whether there are network configuration problems in the target low-efficiency cells in the list, including steps S1021-S1024:

[0037] S1021, determine whether the target low-efficiency cell is a single-layer network cell.

[0038] S1022, in response to the target low-efficiency cell being a multi-layer network cell, determine whether the other cells in the same sector are low-efficiency cells.

[0039] S1023, in response to the target inefficient cell being a single-layer network cell, or the other cells in the same sector being inefficient cells, determine whether the number of fault alarms, duration days, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet the preset conditions.

[0040] S1024, in response to the fact that the number of fault alarms, duration of days, idle noise floor, cell power, minimum access threshold and neighbor cell configuration all meet the preset conditions, it is determined that there is no network configuration problem in the target low-performance cell.

[0041] Optionally, in S1022: after determining whether other cells in the same sector are inefficient cells in response to the target inefficient cell being a multi-layer network cell, the problem investigation method for inefficient cells may also include: in response to the fact that other cells in the same sector are not inefficient cells, performing service balancing optimization on all cells in the network.

[0042] Specifically, the system determines whether the number of fault alarms, duration of duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions, including: determining whether the number of fault alarms is greater than a first preset value; determining whether the duration of duration is greater than or equal to a second preset value; determining whether the idle noise floor is less than or equal to a third preset value; determining whether the cell power is greater than or equal to a fourth preset value; determining whether the minimum access threshold is greater than or equal to a fifth preset value; and determining whether the neighbor cell configuration is missing. In response to the condition that the number of fault alarms is less than or equal to the first preset value, the duration of duration is less than the second preset value, the idle noise floor is greater than the third preset value, the cell power is less than the fourth preset value, the minimum access threshold is less than the fifth preset value, and the neighbor cell configuration is fully configured, the system determines that the number of fault alarms, duration of duration of duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meet the preset conditions.

[0043] In this embodiment, as Figure 3 As shown in this method for troubleshooting network configuration problems in inefficient cells, the output list of inefficient cells is analyzed for network configuration issues. First, it's determined whether the target inefficient cell is a single-layer network cell or a multi-layer network cell. If it's a multi-layer network cell, it's determined whether other cells in the same sector are also inefficient. If the target inefficient cell is a single-layer network cell or other cells in the same sector are also inefficient, then inefficiency caused by occasional events and inefficiency caused by network configuration problems is ruled out. If it's determined that all the output inefficient cells are not due to network configuration problems, then the output inefficient cells cannot be verified or optimized through the network management backend. This embodiment primarily uses six key data points—number of fault alarms, duration of operation, idle noise floor, cell power, minimum access threshold, and whether neighbor cells are missing—to determine if a target low-performance cell has network configuration problems. Specifically, it checks whether the number of fault alarms, duration of operation, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions. These preset conditions include: number of fault alarms less than or equal to a first preset value, duration of operation less than a second preset value, idle noise floor greater than a third preset value, cell power less than a fourth preset value, minimum access threshold less than a fifth preset value, and neighbor cell configuration at full capacity. In this embodiment, the first preset value is 0, the second preset value is 7 days, the third preset value is -95dBm, the fourth preset value is 20W, and the fifth preset value is -116dBm.

[0044] It should be noted that, Figure 3This example illustrates an optimized method for troubleshooting network configuration problems in inefficient cells. Optionally, in steps S1023 and S1024, it is possible to determine whether the number of fault alarms, and / or the duration in days, and / or the idle noise floor, and / or the cell power, and / or the minimum access threshold, and / or the neighbor cell configuration meet preset conditions. In response to the fact that the number of fault alarms, and / or the duration in days, and / or the idle noise floor, and / or the cell power, and / or the minimum access threshold, and / or the neighbor cell configuration meet the preset conditions, it is determined that the target inefficient cell does not have a network configuration problem. The preset conditions include: the number of fault alarms is less than or equal to a first preset value, and / or the duration in days is less than a second preset value, and / or the idle noise floor is greater than a third preset value, and / or the cell power is less than a fourth preset value, and / or the minimum access threshold is less than a fifth preset value, and / or the neighbor cell configuration is fully configured.

[0045] Optionally, after determining whether there is a network configuration problem in the target low-efficiency cell in the list in S102, and before conducting on-site investigation of the target low-efficiency cell in S103 in response to the absence of a network configuration problem in the target low-efficiency cell, the problem investigation method for low-efficiency cells further includes: optimizing the network configuration problem in response to the presence of a network configuration problem in the target low-efficiency cell.

[0046] Specifically, in response to network configuration issues in the target low-performance cell, the network configuration issues are optimized, including: handling fault alarms when the number of fault alarms exceeds a first preset value; continuing observation when the duration is greater than or equal to a second preset value; investigating interference when the idle noise floor is less than or equal to a third preset value; increasing the cell power when it is greater than or equal to a fourth preset value; adjusting the minimum access threshold when it is greater than or equal to a fifth preset value; and adding neighboring cells when neighboring cell configuration is missing.

[0047] In this embodiment, after determining whether a target low-performance cell has a network configuration problem by using six key data points—fault alarms, duration of operation, idle noise floor, cell power, minimum access threshold, and whether neighbor cells are missing—optimization processing is performed if a network configuration problem is found. This optimization processing includes: fault alarm handling, continued observation, interference troubleshooting, power enhancement, minimum threshold adjustment, and adding neighbor cells. Specifically, determining whether a target low-performance cell has a network configuration problem by using these six key data points involves: ① Fault alarms are the most important cause of cell inefficiency. Therefore, by determining whether the number of fault alarms is 0, it is determined whether the inefficiency of the target low-performance cell is caused by fault alarms. If the number of fault alarms is 0, it means that the inefficiency is not caused by fault alarms, and proceed to step ②. If the number of fault alarms is not 0, fault alarm processing is performed first. Step ② is to exclude the low performance of the coverage cell caused by the venue being inactive or other occasional factors. By determining whether the number of consecutive days is not less than 7 days, it is determined whether the inefficiency of the target low-performance cell is caused by the venue being inactive or other occasional factors. If the number of consecutive days is less than 7 days, it means that the inefficiency is not caused by the venue being inactive or other occasional factors, and proceed to step ③. If the number of consecutive days is not less than 7 days, the service situation is observed again. Step ③ is that when the noise floor of the cell is higher than -95dBm during off-peak hours, it is considered strong interference, making it difficult for users to access the network, thus affecting the cell's service volume. Therefore, by judging whether the idle noise floor value is not lower than -95dBm, if the idle noise floor value is not lower than -95dBm, proceed to ④, and conduct interference troubleshooting; ④ Due to factors such as equipment power limitations or poor quality cell processing actively reducing power, the power values ​​of some cells in the current network are set relatively low. According to the product recommendations provided by the equipment manufacturer, the cell power needs to be higher than 20W. Therefore, it is necessary to determine whether the cell power setting value is not lower than the threshold of 20W. If the cell power is not lower than 20W, proceed to ⑤; if the cell power is lower than 20W, perform power adjustment; ⑤ The setting of the access threshold can affect the coverage conditions under which users access the network. Taking L operator's LTE (Long-Term Evolution) as an example, the minimum access threshold set for the entire network is -116dBm. Therefore, it is necessary to verify whether the minimum access threshold setting of the cell is lower than -116dBm. If the minimum access threshold is not lower than -116dBm, adjust the minimum access threshold of the cell and continue to observe. If the minimum access threshold is lower than -116dBm, proceed to step ⑥. ⑥ Missing neighbor cell configurations can prevent users from switching to the current cell, creating an island effect. Therefore, it is necessary to check whether neighbor cells are missing configurations and whether the ANR (Application Not Responding) function is enabled. If neighbor cells are missing configurations, plan neighbor cells and add them again. If all neighbor cells are configured, output a list of inefficient cells not caused by network configuration issues for on-site investigation.This embodiment combines network management backend data to systematically investigate and handle network configuration problems in target low-performance cells, enabling rapid location of network configuration issues in low-performance cells. This allows for targeted adjustment of network parameter configurations, optimization of target low-performance cell performance, improvement of network coverage and quality, enhancement of user experience and satisfaction, and timely detection and resolution of network configuration problems, reducing network failure rates and decreasing the workload and costs for maintenance personnel.

[0048] Step S103: In response to the fact that there is no network configuration problem in the target low-performance cell, conduct on-site investigation of the target low-performance cell.

[0049] Specifically, step S103: In response to the absence of network configuration problems in the target inefficient cell, an on-site investigation of the target inefficient cell is conducted, including steps S1031-S1034:

[0050] Step S1031: Determine whether the target low-efficiency cell is an indoor distributed cell or a macro cell.

[0051] Step S1032: In response to the target low-efficiency cell being an indoor distributed antenna system (DAS) cell, determine whether the indoor DAS system has been damaged.

[0052] Step S1033: In response to the damage to the indoor distribution system, system repair is performed.

[0053] Step S1034: In response to the fact that the indoor distribution system has not been damaged, the equipment in the target low-efficiency cell is dismantled and reused.

[0054] Optionally, step S103: In response to the absence of network configuration problems in the target inefficient cell, the on-site investigation of the target inefficient cell further includes steps S1035-S1041:

[0055] Step S1035: In response to the target low-efficiency cell being a macro cell, determine whether there is coverage requirement on site.

[0056] Step S1036: In response to the lack of coverage on site, dismantle and reuse existing equipment in the target low-efficiency cell.

[0057] Step S1037: In response to the need for coverage on site, determine whether radio frequency (RF) optimization can be performed.

[0058] Step S1038: In response to the ability to perform RF optimization, RF optimization is performed.

[0059] Step S1039: In response to the inability to perform RF optimization, determine whether construction rectification can be carried out.

[0060] Step S1040: In response to the ability to carry out construction rectification, construction rectification is carried out.

[0061] Step S1041: In response to the inability to carry out construction and rectification, the equipment in the target low-efficiency community is dismantled and reused.

[0062] In this embodiment, as Figure 4 As shown in the on-site troubleshooting method for inefficient cells, an on-site investigation is conducted on a list of inefficient cells not caused by network configuration issues. The on-site investigation needs to combine the station type (indoor / outdoor), engineering parameters (mounting height / tilt angle / azimuth angle), and coverage scenario to output processing suggestions. Determine whether the target low-efficiency cell is an indoor distributed antenna system (DAS) cell or a macro base station cell. If it is an indoor DAS cell, check if the DAS system is damaged. If so, repair it. After repair, re-enter the service monitoring process in step S101 to obtain the latest list of low-efficiency cells. If the DAS system is normal, there is no coverage requirement in the current indoor area, and the equipment can be reused. If the target low-efficiency cell is a macro base station cell, determine whether there is a coverage requirement in the current area based on the on-site coverage environment. If there is no coverage requirement, the equipment can be reused. If the coverage is found to be unreasonable, i.e., there is a coverage requirement, RF (Radio Frequency) optimization can be performed. After optimization, re-enter the service monitoring process in step S101 to obtain the latest list of low-efficiency cells. If RF optimization cannot be performed, determine whether construction and rectification are possible, such as insufficient mounting height or obstructions. If construction and rectification are not possible, there is no coverage requirement in the current area, and the equipment can be reused. In this embodiment, the dismantling and reuse of equipment includes the following two situations: (1) Dismantling old versions of equipment in inefficient cells to reduce network operating costs and improve network performance and efficiency. The old versions of equipment include: old-model base station equipment, i.e., outdated base station equipment, antennas, transmission equipment, etc.; old-version core network equipment, such as outdated core network equipment, routers, switches, etc.; old-version transmission equipment, such as outdated fiber optic transmission equipment, microwave transmission equipment, etc.; old-version auxiliary equipment, such as power supply equipment, air conditioning equipment, etc. (2) Dismantling new versions of equipment that have generated inefficient cells due to unreasonable planning or other reasons, such as indoor distribution equipment after the closure and relocation of enterprises or factories, and inefficient small cell equipment caused by the construction of macro base stations in the surrounding area. The equipment may be new versions, but it has not truly played the role of absorbing services. It can be dismantled and then moved to hotspot areas. This embodiment combines on-site investigation and processing methods to investigate and solve the problem of the target inefficient cell, directly handles the problem, shortens the fault investigation time, speeds up the problem resolution, and improves network recovery efficiency.

[0063] This embodiment provides a method for troubleshooting inefficient cells. By conducting lifecycle and performance verification analysis on all cells in the network, a list of inefficient cells is compiled. Then, network configuration issues are investigated and addressed in target inefficient cells on the list. Inefficient cells without network configuration problems are investigated on-site. Therefore, this invention enables rapid and accurate location of target inefficient cells, thereby improving the efficiency of troubleshooting and handling, reducing network and human resource waste, improving network quality and efficiency, mitigating the risks of inefficient operation, and enhancing user experience. Furthermore, by conducting lifecycle and performance verification analysis on all cells in the network and using algorithms to statistically identify target inefficient cells, rapid and accurate identification of inefficient cells across the entire network is achieved, helping to locate the root cause of the problem and find the specific reasons for inefficiency. By combining network management backend data, the system systematically investigates and addresses network configuration issues in target low-performance cells. This enables rapid location of network configuration problems in low-performance cells, allowing for targeted adjustments to network parameter configurations, optimizing cell performance, improving network coverage and quality, enhancing user experience and satisfaction, and promptly identifying and resolving network configuration issues. This reduces network failure rates and decreases the workload and costs for maintenance personnel. Furthermore, by combining on-site troubleshooting methods, problems in target low-performance cells are identified and resolved directly, shortening troubleshooting time, accelerating problem resolution, and improving network recovery efficiency.

[0064] Example 2:

[0065] like Figure 5 As shown, this embodiment provides a troubleshooting device for inefficient cells. The troubleshooting device for inefficient cells includes: a service monitoring module, a network analysis module, and a field troubleshooting assistance module.

[0066] The service monitoring module is used to monitor and collect service volume data of all cells in the network. It filters service volume indicator data such as average daily traffic, average daily number of users, and average daily PRB (Physical Resource Block) utilization rate by name, and identifies inefficient cells based on service volume indicator data and corresponding indicator thresholds, and outputs a list of inefficient cells.

[0067] In this embodiment, the threshold values ​​for the daily average traffic are 500MB, the daily average number of users are 8, and the daily average PRB utilization rate is 5%. For example, if the target cell's daily average traffic is below 500MB, the daily average number of users is below 8, or the daily average PRB utilization rate is below 5%, then the target cell is considered an inefficient cell. This embodiment performs lifecycle and performance verification analysis on all cells in the network, and uses algorithms to statistically identify target inefficient cells, achieving rapid and accurate identification of inefficient cells across the entire network. This helps in subsequently locating the root cause of the problem and identifying the specific reasons for inefficiency.

[0068] The network analysis module analyzes the output list of inefficient cells to identify network configuration issues. First, it determines whether the target inefficient cell is a single-layer or multi-layer network cell. If it's a multi-layer network cell, it checks if other cells in the same sector are also inefficient. If the target inefficient cell is a single-layer network cell or if other cells in the same sector are also inefficient, it then excludes inefficiencies caused by isolated events or network configuration problems. If all output inefficient cells are determined to be inefficient due to reasons other than network configuration issues (i.e., no network configuration problems exist), then these inefficient cells cannot be verified or optimized through the network management backend. This embodiment primarily uses six key data points—number of fault alarms, duration in days, idle noise floor, cell power, minimum access threshold, and whether neighbor cell configurations are missing—to determine if the target inefficient cell has network configuration problems. Specifically, it checks whether the number of fault alarms, duration in days, idle noise floor, cell power, minimum access threshold, and neighbor cell configurations meet preset conditions.

[0069] In this embodiment, the preset conditions include: the number of fault alarms is less than or equal to a first preset value, the duration is less than a second preset value, the idle noise level is greater than a third preset value, the cell power is less than a fourth preset value, the minimum access threshold is less than a fifth preset value, and the neighboring cell configuration is fully configured. In this embodiment, the first preset value is 0, the second preset value is 7 days, the third preset value is -95dBm, the fourth preset value is 20W, and the fifth preset value is -116dBm.

[0070] After determining whether a target low-performance cell has network configuration problems by using six key data points—fault alarms, duration of operation, idle noise floor, cell power, minimum access threshold, and whether neighbor cells are missing—optimization is performed if network configuration problems are found. This optimization includes: fault alarm handling, continued observation, interference troubleshooting, power enhancement, minimum threshold adjustment, and adding neighbor cells. Specifically: ① Fault alarms are the most important cause of cell inefficiency. Therefore, checking if the number of fault alarms is 0 determines whether the low performance of the target low-performance cell is caused by fault alarms. If the number of fault alarms is 0, it indicates that the low performance is not caused by fault alarms, and proceed to ②. If the number of fault alarms is not 0, fault alarm handling is performed first. ② Duration of operation excludes low performance caused by venues being inactive or other occasional factors. The process involves determining whether the inefficiency of a target cell is caused by the venue being inactive or other unforeseen factors by checking if the duration of inefficiency is not less than 7 days. If the duration is less than 7 days, it indicates that the inefficiency is not caused by the venue being inactive or other unforeseen factors, and the process proceeds to step ③. If the duration is not less than 7 days, the service situation continues to be observed. Step ③ indicates strong interference when the cell's idle noise floor is higher than -95dBm, making it difficult for users to access the network and affecting the cell's service volume. Therefore, the process involves checking if the idle noise floor is not lower than -95dBm. If the idle noise floor is not lower than -95dBm, the process proceeds to step ④, where interference is investigated. Step ④ indicates that due to equipment power limitations or factors such as actively reducing power in poor-quality cells, the power values ​​of some cells in the current network are set relatively low. According to the product recommendations provided by the equipment manufacturer, the cell power should be higher than 20W. Therefore, it is necessary to determine whether the cell power setting is not lower than the threshold of 20W. If the cell power is not lower than 20W, proceed to step ⑤; if the cell power is lower than 20W, power adjustment is required. ⑤ The access threshold setting can affect the coverage conditions under which users access the network. Taking L operator's LTE (Long-Term Evolution) as an example, the minimum access threshold set for the entire network is -116dBm. Therefore, it is necessary to verify whether the minimum access threshold setting of the cell is lower than -116dBm. If the minimum access threshold is not lower than -116dBm, adjust the minimum access threshold of the cell and continue to observe. If the minimum access threshold is lower than -116dBm, proceed to step ⑥. ⑥ Missing neighbor cell configurations can prevent users from switching to the current cell, creating an island effect. Therefore, it is necessary to check whether neighbor cells are missing configurations and whether the ANR (Application Not Responding) function is enabled. If neighbor cells are missing configurations, plan neighbor cells and add them again. If all neighbor cells are configured, output a list of inefficient cells not caused by network configuration issues for on-site investigation.This embodiment combines network management backend data to systematically investigate and handle network configuration problems in target low-performance cells, enabling rapid location of network configuration issues in low-performance cells. This allows for targeted adjustment of network parameter configurations, optimization of target low-performance cell performance, improvement of network coverage and quality, enhancement of user experience and satisfaction, and timely detection and resolution of network configuration problems, reducing network failure rates and decreasing the workload and costs for maintenance personnel.

[0071] The on-site troubleshooting module is used to conduct on-site investigations of the list of inefficient cells that are not caused by network configuration issues. On-site troubleshooting needs to combine the station type (indoor / outdoor), engineering parameters (mounting height / tilt angle / azimuth angle), and coverage scenario to output processing suggestions.

[0072] In this embodiment, it is determined whether the target low-efficiency cell is an indoor distributed antenna system (DAS) cell or a macro base station cell. If the target low-efficiency cell is an indoor DAS cell, it is checked whether the DAS system is damaged. If the DAS system is damaged, it is repaired. After repair, the process re-enters step S101, the service monitoring process, to obtain the latest list of low-efficiency cells. If the DAS system is normal, there is no coverage requirement in the current indoor area, and the equipment can be reused. If the target low-efficiency cell is a macro base station cell, it is determined whether there is a coverage requirement in the current area based on the on-site coverage environment. If there is no coverage requirement, the equipment can be reused. If the coverage is found to be unreasonable, i.e., there is a coverage requirement, RF (Radio Frequency) optimization can be performed. After optimization, the process re-enters step S101, the service monitoring process, to obtain the latest list of low-efficiency cells. If RF optimization cannot be performed, it is determined whether construction and rectification can be carried out, such as insufficient mounting height or obstruction. If construction and rectification cannot be carried out, there is no coverage requirement in the current area, and the equipment can be reused.

[0073] This embodiment provides a device for troubleshooting inefficient cells. By conducting lifecycle and performance verification analysis on all cells in the network, a list of inefficient cells is compiled. Then, network configuration problems are investigated and addressed in target inefficient cells on the list. Inefficient cells without network configuration problems are investigated on-site. Therefore, this invention can quickly and accurately locate target inefficient cells, thereby improving the efficiency of troubleshooting and handling, reducing network and human resource waste, improving network quality and efficiency, mitigating the risks of inefficient operation, and enhancing user experience. Furthermore, by conducting lifecycle and performance verification analysis on all cells in the network and using algorithms to statistically determine target inefficient cells, rapid and accurate identification of inefficient cells across the entire network is achieved, helping to locate the root cause of the problem and identify the specific reasons for inefficiency. By combining network management backend data, the system systematically investigates and addresses network configuration issues in target low-performance cells. This enables rapid location of network configuration problems in low-performance cells, allowing for targeted adjustments to network parameter configurations, optimizing cell performance, improving network coverage and quality, enhancing user experience and satisfaction, and promptly identifying and resolving network configuration issues. This reduces network failure rates and decreases the workload and costs for maintenance personnel. Furthermore, by combining on-site troubleshooting methods, problems in target low-performance cells are identified and resolved directly, shortening troubleshooting time, accelerating problem resolution, and improving network recovery efficiency.

[0074] Example 3:

[0075] like Figure 6 As shown, this embodiment provides a device for troubleshooting inefficient cells, including: an acquisition module 61, a judgment module 62, and an on-site investigation module 63. The acquisition module 61 is used to collect traffic volume indicator data of all cells in the network and obtain a list of inefficient cells based on the traffic volume indicator data and the corresponding indicator thresholds. The traffic volume indicators include average daily traffic and at least one of the following: average daily number of users and average daily PRB utilization. The judgment module 62 is connected to the acquisition module 61 and is used to determine whether there is a network configuration problem in the target inefficient cell in the list. The on-site investigation module 63 is connected to the judgment module 62 and is used to perform on-site investigation of the target inefficient cell in response to the absence of a network configuration problem in the target inefficient cell.

[0076] Specifically, the judgment module 62 includes: a first judgment unit 621, a second judgment unit 622, a third judgment unit 623, and a determination unit 624. The first judgment unit 621 is used to determine whether the target inefficient cell is a single-layer network cell. The second judgment unit 622 is used to determine whether other cells in the same sector are inefficient cells in response to the target inefficient cell being a multi-layer network cell. The third judgment unit 623 is used to determine whether the number of fault alarms, duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions in response to the target inefficient cell being a single-layer network cell or other cells in the same sector being inefficient cells. The determination unit 624 is used to determine that the target inefficient cell does not have a network configuration problem in response to the fact that the number of fault alarms, duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meet preset conditions.

[0077] Optionally, the judgment module 62 further includes: a balance optimization unit 625, used to perform service balance optimization on all cells in the network in response to the fact that other cells in the same sector are not inefficient cells.

[0078] Specifically, the third judgment unit 623 includes: a first judgment subunit, a second judgment subunit, a third judgment subunit, a fourth judgment subunit, a fifth judgment subunit, a sixth judgment subunit, and a determination subunit. The first judgment subunit is used to determine whether the number of fault alarms is greater than a first preset value; the second judgment subunit is used to determine whether the duration of the fault alarms is greater than a second preset value; the third judgment subunit is used to determine whether the idle noise floor is less than or equal to a third preset value; the fourth judgment subunit is used to determine whether the cell power is greater than or equal to a fourth preset value; the fifth judgment subunit is used to determine whether the minimum access threshold is greater than or equal to a fifth preset value; the sixth judgment subunit is used to determine whether the neighbor cell configuration is missing; and the determination subunit is used to determine that the number of fault alarms, duration of the fault alarms, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meet the preset conditions in response to the following conditions: the number of fault alarms is less than or equal to the first preset value, the duration of the fault alarms is less than or equal to the second preset value, the idle noise floor is greater than the third preset value, the cell power is less than the fourth preset value, the minimum access threshold is less than the fifth preset value, and the neighbor cell configuration is fully configured.

[0079] Optionally, the problem-solving device for inefficient cells also includes an optimization module 64, used to optimize the network configuration problem in response to the presence of a network configuration problem in the target inefficient cell.

[0080] Specifically, the optimization module 64 includes: a first optimization unit 641, a second optimization unit 642, a third optimization unit 643, a fourth optimization unit 644, a fifth optimization unit 645, and a sixth optimization unit 646. The first optimization unit 641 is used to process fault alarms when the number of fault alarms exceeds a first preset value. The second optimization unit 642 is used to continue observation when the number of consecutive days exceeds a second preset value. The third optimization unit 643 is used to investigate interference when the idle noise floor is less than or equal to a third preset value. The fourth optimization unit 644 is used to increase the power when the cell power is greater than or equal to a fourth preset value. The fifth optimization unit 645 is used to adjust the minimum access threshold when the minimum access threshold is greater than or equal to a fifth preset value. The sixth optimization unit 646 is used to add neighboring cells when the neighboring cell configuration is missing.

[0081] Specifically, the on-site inspection module 63 includes: a fourth judgment unit 631, a fifth judgment unit 632, a repair unit 633, and a dismantling and reuse unit 634. The fourth judgment unit 631 is used to determine whether the target low-efficiency cell is an indoor distributed antenna system (DAS) cell or a macro base station cell. The fifth judgment unit 632 is used to determine whether the indoor DAS system has been damaged in response to the target low-efficiency cell being an indoor DAS cell. The repair unit 633 is used to repair the system in response to the damage to the indoor DAS system. The dismantling and reuse unit 634 is used to dismantle and reuse the equipment in the target low-efficiency cell in response to the fact that the indoor DAS system has not been damaged.

[0082] Optionally, the on-site inspection module 63 further includes: a sixth judgment unit 635, a seventh judgment unit 636, an RF optimization unit 637, an eighth judgment unit 638, and a construction rectification unit 639. The sixth judgment unit 635 is used to determine whether there is a coverage requirement on-site in response to the target low-efficiency cell being a macro base station cell. The dismantling and reuse unit 634 is also used to dismantle and reuse equipment in the target low-efficiency cell in response to the absence of coverage requirement on-site. The seventh judgment unit 636 is used to determine whether RF optimization can be performed in response to the presence of coverage requirement on-site. The RF optimization unit 637 is used to perform RF optimization in response to the possibility of RF optimization. The eighth judgment unit 638 is used to determine whether construction rectification can be performed in response to the inability to perform RF optimization. The construction rectification unit 639 is used to perform construction rectification in response to the possibility of construction rectification. The dismantling and reuse unit 634 is also used to dismantle and reuse equipment in the target low-efficiency cell in response to the inability to perform construction rectification.

[0083] Understandably, the problem-solving device for inefficient cells provided above is used to execute the method corresponding to Embodiment 1 provided above. Therefore, the beneficial effects it can achieve can be referred to the beneficial effects of the method in Embodiment 1 above and the corresponding scheme in the detailed implementation below, which will not be repeated here.

[0084] Example 4:

[0085] This embodiment also provides an electronic device, including a memory and a processor. The memory stores a computer program, and the processor is configured to run the computer program to implement the problem investigation method for low-efficiency cells in Embodiment 1 above.

[0086] Example 5:

[0087] This embodiment also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the problem-solving method for inefficient cells described in Embodiment 1 above.

[0088] It is understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present invention, and the present invention is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method for troubleshooting inefficient residential communities, characterized in that, include: Collect traffic volume data from all cells in the network, and obtain a list of inefficient cells based on the traffic volume data and the corresponding threshold values. The traffic volume data includes average daily traffic and at least one of the following: average daily number of users and average daily PRB utilization rate. Determine whether the target inefficient cells in the list have network configuration problems; Since there were no network configuration issues in the target low-performance cell, an on-site investigation was conducted on the target low-performance cell. Determining whether the target inefficient cells in the list have network configuration problems specifically includes: Determine whether the target inefficient cell is a single-layer network cell; In response to the fact that the target low-efficiency cell is a multi-layer network cell, determine whether the other cells in the same sector are low-efficiency cells; In response to the target inefficient cell being a single-layer network cell, or other cells in the same sector being inefficient cells, determine whether the number of fault alarms, duration days, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet the preset conditions. If the number of fault alarms, duration of duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meet the preset conditions, and the inefficiency caused by occasional events and network configuration problems is excluded, it is determined that the target inefficient cell does not have network configuration problems.

2. The method for troubleshooting inefficient residential communities according to claim 1, characterized in that, After determining whether other cells in the same sector are inefficient cells in response to the target inefficient cell being a multi-layer network cell, the method further includes: In response to the assumption that other cells in the same sector are not inefficient cells, a service balance optimization is performed on all cells in the network. The determination of whether the number of fault alarms, duration in days, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet preset conditions specifically includes: Determine if the number of fault alarms is greater than the first preset value; Determine if the duration of the period is greater than or equal to the second preset value; Determine whether the background noise during idle hours is less than or equal to the third preset value; Determine if the cell power is greater than or equal to the fourth preset value; Determine whether the minimum access threshold is greater than or equal to the fifth preset value; Determine if the neighboring cell configuration is missing; In response to the following conditions: the number of fault alarms is less than or equal to the first preset value, the duration is less than the second preset value, the idle noise floor is greater than the third preset value, the cell power is less than the fourth preset value, the minimum access threshold is less than the fifth preset value, and the neighbor cell configuration is fully configured, it is determined that the number of fault alarms, the duration, the idle noise floor, the cell power, the minimum access threshold, and the neighbor cell configuration all meet the preset conditions.

3. The method for troubleshooting inefficient residential communities according to claim 1, characterized in that, After determining whether there are network configuration problems in the target inefficient cells in the list, and before conducting on-site investigation of the target inefficient cells in response to the determination that there are no network configuration problems, the method further includes: In response to the network configuration issues found in the target low-performance cell, the network configuration issues are optimized.

4. The method for troubleshooting inefficient residential communities according to claim 3, characterized in that, The response to the network configuration problem in the target inefficient cell involves optimizing the network configuration, specifically including: In response to the number of fault alarms exceeding a first preset value, fault alarm processing is performed; If the duration of the event is greater than or equal to the second preset value, continue observation; When the background noise during idle hours is less than or equal to the third preset value, interference is investigated. In response to the cell power being greater than or equal to the fourth preset value, power is increased; In response to the minimum access threshold being greater than or equal to the fifth preset value, the minimum access threshold is adjusted. In response to a missing neighbor cell configuration, add a neighbor cell.

5. The method for troubleshooting inefficient residential communities according to claim 1, characterized in that, In response to the assumption that there are no network configuration problems in the target low-performance cell, an on-site investigation of the target low-performance cell is conducted, specifically including: Determine whether the target low-efficiency community is an indoor distributed antenna system (DAS) community or a macro base station community; In response to the fact that the target inefficient cell is an indoor distributed antenna system (DAS) cell, determine whether the indoor DAS system has been damaged; In response to damage to the indoor distribution system, system repair is performed; In response to the fact that the indoor distribution system has not been damaged, the equipment in the target low-efficiency cell is dismantled and reused.

6. The method for troubleshooting inefficient residential communities according to claim 5, characterized in that, The response that there is no network configuration problem in the target inefficient cell, and the on-site investigation of the target inefficient cell, also includes: In response to the fact that the target low-efficiency cell is a macro base station cell, determine whether there is a coverage requirement on site; In response to the lack of coverage on-site, the equipment in the target low-efficiency communities is dismantled and reused; In response to the on-site coverage requirements, determine whether radio frequency (RF) optimization can be performed; In response to the ability to perform RF optimization, RF optimization is performed. In response to the inability to perform RF optimization, determine whether construction rectification can be carried out; In response to the need for construction rectification, construction rectification was carried out. In response to the inability to carry out construction and renovation, the equipment in the target low-efficiency community is dismantled and reused.

7. A problem-solving device for inefficient residential communities, characterized in that, include: The module includes an acquisition module, a judgment module, and an on-site investigation module. The acquisition module is used to collect traffic volume indicator data from all cells in the network and obtain a list of inefficient cells based on the traffic volume indicator data and corresponding indicator thresholds. The traffic volume indicators include average daily traffic and at least one of the following: average daily number of users, average daily PRB utilization rate. The judgment module, connected to the acquisition module, is used to determine whether there are network configuration problems in the target inefficient cells in the list. The on-site investigation module, connected to the judgment module, is used to conduct on-site investigations of the target low-performance cell in response to the absence of network configuration problems. Determining whether the target inefficient cells in the list have network configuration problems specifically includes: Determine whether the target inefficient cell is a single-layer network cell; In response to the fact that the target low-efficiency cell is a multi-layer network cell, determine whether the other cells in the same sector are low-efficiency cells; In response to the target inefficient cell being a single-layer network cell, or other cells in the same sector being inefficient cells, determine whether the number of fault alarms, duration days, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration meet the preset conditions. If the number of fault alarms, duration of duration, idle noise floor, cell power, minimum access threshold, and neighbor cell configuration all meet the preset conditions, and the inefficiency caused by occasional events and network configuration problems is excluded, it is determined that the target inefficient cell does not have network configuration problems.

8. An electronic device, characterized in that, The device includes a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to implement a problem-solving method for inefficient cells as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements a problem-solving method for inefficient cells as described in any one of claims 1 to 6.

Images