Operation and maintenance data reporting method and device, storage medium and electronic device

Abstract

The application discloses a kind of operation and maintenance data reporting method and device, storage medium and electronic device, which comprises: receiving data reporting request, wherein data reporting request is used to indicate network device to the network management equipment connected to network device and report the operation and maintenance data of network device;According to the first data and the second data, the network fault information of network device is detected, wherein the first data is used to indicate the service execution state when network device executes network coverage service, and the second data is used to indicate the network coverage quality of terminal equipment detected by network device accessing network device;From the first data and the second data, the target data with the associated relationship with network fault information is screened out;Target data is reported to network management equipment, wherein network management equipment is used to adjust the service execution state when network device executes network coverage service according to target data, and the above technical solution solves the waste of bandwidth resources in the operation and maintenance data reporting process in the related art.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for reporting operation and maintenance data, a storage medium, and an electronic device. Background Technology

[0002] Modern communication network operation and maintenance heavily relies on two types of fundamental data: data indicating the service execution status of network devices when performing network coverage services, and data indicating the network coverage quality detected by terminal devices accessing the network devices. These two types of data are typically reported separately to the network management device in full, which can lead to a significant waste of bandwidth resources between the network devices and the network management device.

[0003] There is still no effective solution to the problem of wasted bandwidth resources during the reporting of operation and maintenance data in related technologies. Summary of the Invention

[0004] This application provides a method and apparatus for reporting operation and maintenance data, a storage medium, and an electronic device to at least solve the problem of wasted bandwidth resources during the operation and maintenance data reporting process in related technologies.

[0005] According to one embodiment of this application, a method for reporting operation and maintenance data is provided, comprising: receiving a data reporting request, wherein the data reporting request is used to instruct a network device to report operation and maintenance data of the network device to a connected network management device; detecting network fault information of the network device based on first data and second data, wherein the first data is used to indicate the service execution status of the network device when performing network coverage services, and the second data is used to indicate the network coverage quality of the network device detected by a terminal device accessing the network device; filtering target data that is correlated with network fault information from the first data and the second data; and reporting the target data to the network management device, wherein the network management device is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0006] In an exemplary embodiment, detecting network fault information of a network device based on first data and second data includes: detecting the periodic fault state of the network device in the current period based on the first data and second data to obtain the current fault state, wherein the periodic fault state is the implementation state of the network device in implementing network coverage function within the corresponding periodic time period, and the implementation state includes abnormal state and normal state; detecting operation and maintenance requirement information based on the current fault state and historical fault states, wherein the historical fault state is the periodic fault state of the network device in historical periods before the current period, and the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of the network device, and the network fault information includes operation and maintenance requirement information.

[0007] In one exemplary embodiment, detecting maintenance requirement information based on the current fault state and historical fault states includes: when the current fault state is an abnormal state and the historical fault state is a normal state, determining that the maintenance requirement information indicates an importance level greater than a first importance threshold; when the current fault state is a normal state and the historical fault state is a normal state, determining that the maintenance requirement information indicates an importance level less than or equal to the first importance threshold, and greater than a second importance threshold; when the current fault state is an abnormal state and the historical fault state is an abnormal state, determining that the maintenance requirement information indicates an importance level less than or equal to the second importance threshold; and when the current fault state is a normal state and the historical fault state is an abnormal state, determining that the maintenance requirement information indicates an importance level greater than the first importance threshold.

[0008] In an exemplary embodiment, detecting the periodic fault state of the network device in the current period based on first data and second data to obtain the current fault state includes: detecting whether each first sub-data in the first data falls within a first target range corresponding to each first sub-data, and detecting whether the second sub-data falls within a second target range corresponding to the second sub-data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; if the target sub-data does not fall within the first target range corresponding to the target sub-data, and / or the second sub-data does not fall within the second target range, determining the current fault state as an abnormal state, wherein the target sub-data is any one of the first sub-data; if all the first sub-data falls within the first target range corresponding to each first sub-data, and the second sub-data falls within the second target range, determining the current fault state as a normal state.

[0009] In one exemplary embodiment, filtering target data that is associated with network fault information from first data and second data includes: detecting coverage information of the second data over the first data, wherein the coverage information is used to indicate the degree of overlap between the second collection time period of the second data and the first collection time period of the first data; filtering target data from the first data and second data based on the coverage information and operation and maintenance requirement information, wherein the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of network devices, and the network fault information includes the operation and maintenance requirement information.

[0010] In one exemplary embodiment, selecting target data from first data and second data based on coverage information and operation and maintenance requirement information includes: determining the first data and second data as target data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree greater than a first importance threshold; determining the first data and second sub-data as target data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to the first importance threshold but greater than a second importance threshold, wherein the second sub-data indicates the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; and determining the first data and second sub-data as target data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to the second importance threshold. The system detects whether the time for abnormal reporting of operation and maintenance data has been reached. If the time for abnormal reporting has been reached, the first data and the second sub-data are determined as target data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data. If the time for abnormal reporting has not been reached, the first data is determined as target data. If the coverage information is used to indicate that the degree of overlap is less than the overlap threshold, and the operation and maintenance requirement information is used to indicate that the importance is less than or equal to the first importance threshold, the first data is determined as target data. If the coverage information is used to indicate that the degree of overlap is less than the overlap threshold, and the operation and maintenance requirement information is used to indicate that the importance is greater than the first importance threshold, target data is selected from the first data and the second data based on reference sub-data, wherein the reference sub-data is used to indicate the signaling performance of the network device, and the first data includes the reference sub-data.

[0011] In one exemplary embodiment, selecting target data from first data and second data based on reference sub-data includes: detecting whether the reference sub-data falls within a first reference range corresponding to the reference sub-data; if the reference sub-data falls within the first reference range, determining the first data as target data; if the reference sub-data does not fall within the first reference range, determining the first data and second data as target data.

[0012] According to another embodiment of the present application, a device for reporting operation and maintenance data is also provided, comprising: a receiving module for receiving a data reporting request, wherein the data reporting request is used to instruct a network device to report operation and maintenance data of the network device to a connected network management device; a detection module for detecting network fault information of the network device based on first data and second data, wherein the first data is used to indicate the service execution status of the network device when performing network coverage services, and the second data is used to indicate the network coverage quality of the network device detected by a terminal device accessing the network device; a filtering module for filtering target data that is associated with network fault information from the first data and the second data; and a reporting module for reporting the target data to the network management device, wherein the network management device is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0013] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described method for reporting operation and maintenance data when it is run.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above-mentioned method for reporting maintenance data through the computer program.

[0015] In this embodiment, a data reporting request is received, instructing the network device to report network device operation and maintenance data to the connected network management device. Based on first data indicating the service execution status of the network device when performing network coverage services and second data indicating the network coverage quality detected by the terminal device accessing the network device, network fault information of the network device is detected. Target data correlated with the network fault information is filtered from the first and second data and reported to the network management device. That is, the reported operation and maintenance data is associated with the current network fault information of the network device, avoiding the blind full reporting of the first and second data and preventing waste of bandwidth resources. By adopting the above technical solution, the problem of wasted bandwidth resources during operation and maintenance data reporting in related technologies is solved, achieving the technical effect of saving bandwidth resources during operation and maintenance data reporting. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the hardware environment for a method of reporting operation and maintenance data according to an embodiment of this application.

[0019] Figure 2 This is a flowchart of a method for reporting operation and maintenance data according to an embodiment of this application;

[0020] Figure 3 This is a flowchart of a reporting and management scheme for operation and maintenance data according to an embodiment of this application;

[0021] Figure 4 This is a structural block diagram of a maintenance data reporting device according to an embodiment of this application. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] The methods and embodiments provided in this application can be executed on a computer terminal, device terminal, or similar computing device. Taking running on a computer terminal as an example, Figure 1 This is a schematic diagram of the hardware environment for a method of reporting operation and maintenance data according to an embodiment of this application. For example... Figure 1As shown, a computer terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. In one exemplary embodiment, the computer terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 1 The more or fewer components shown, or having the same Figure 1 Equivalent functions or ratios shown Figure 1 The functions shown have more different configurations.

[0025] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the operation and maintenance data reporting method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0026] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0027] This embodiment provides a method for reporting operation and maintenance data, applied to the aforementioned computer terminal. Figure 2 This is a flowchart of a method for reporting operation and maintenance data according to an embodiment of this application. The process includes the following steps:

[0028] Step S202: Receive a data reporting request, wherein the data reporting request is used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device;

[0029] Step S204: Detect network fault information of network devices based on first data and second data, wherein the first data is used to indicate the service execution status of network devices when performing network coverage services, and the second data is used to indicate the network coverage quality of network devices detected by terminal devices accessing network devices.

[0030] Step S206: Filter out target data that is related to network fault information from the first data and the second data;

[0031] Step S208: Report the target data to the network management device, wherein the network management device is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0032] Through the above steps, a data reporting request is received, instructing the network device to report network device operation and maintenance data to the connected network management device. Based on first data indicating the service execution status of the network device when performing network coverage services and second data indicating the network coverage quality detected by the terminal device accessing the network device, network fault information of the network device is detected. Target data related to the network fault information is filtered from the first and second data and reported to the network management device. That is, the reported operation and maintenance data is associated with the current network fault information of the network device, avoiding the blind full reporting of the first and second data and preventing the waste of bandwidth resources. This technical solution solves the problem of bandwidth resource waste during operation and maintenance data reporting in related technologies, achieving the technical effect of saving bandwidth resources during operation and maintenance data reporting.

[0033] In the technical solution provided in step S202 above, network equipment may refer to, but is not limited to, the basic components for building a communication network. Network equipment may be used for data transmission, processing, and management, enabling the network to operate and provide services. Network equipment may include, but is not limited to, routers, switches, firewalls, wireless access points, baseband units (BBU), remote radio units (RRU), base stations (such as eNodeB in 4G and gNodeB in 5G), small base stations, core network elements (such as SGW, PGW, AMF, SMF, etc.), and transmission nodes.

[0034] Optionally, in this embodiment, network management equipment may refer to, but is not limited to, a platform used to monitor and manage network devices and their related services to ensure normal network operation and improve network service quality. Network management equipment can collect operational data in real time, analyze network conditions, adjust network configurations, and perform fault diagnosis and prevention. Network management equipment may include, but is not limited to, network management servers, virtualized network management systems, cloud network management platforms, and integrated service management platforms.

[0035] Optionally, in this embodiment, operation and maintenance data may refer to, but is not limited to, information generated during the operation of network devices for monitoring device status, performance, and quality of service. This data is crucial for network operation and maintenance, and may, but is not limited to, help identify network faults, optimize network performance, and improve user experience. Operation and maintenance data may, but is not limited to, include: performance counters and measurement reports (MRs). Performance counters may, but are not limited to, be generated in real-time by network protocol stack modules and are used to characterize key performance indicators (KPIs) of network service quality, such as connection establishment success rate, number of handover failures, and call drop rate, and are characterized by low frequency, structure, and result-oriented features. Measurement reports may, but are not limited to, be reported by terminal devices under event triggering or periodic configuration conditions, and may, but are not limited to, include wireless measurement information of the serving cell and neighboring cells (such as RSRP, RSRQ, SINR, PCI, frequency points, etc.), and are characterized by high frequency, semi-structured features, and process-oriented features.

[0036] Optionally, in this embodiment, data reporting requests may be received in the following ways, but not limited to: triggering a data reporting request when the data reporting period arrives; or receiving a data reporting request issued by the network management device; or triggering a data reporting request when a network device is detected to have a device failure or a significant degradation in the device performance.

[0037] In the technical solution provided in step S204 above, the first data may, but is not limited to, refer to the service execution status data statistically collected by the network device itself when performing network coverage services. The first data may, but is not limited to, include performance counters, and such data may, but is not limited to, be result-oriented, reflecting the overall operating status of the device and the quality of network services.

[0038] Optionally, in this embodiment, the first data may include, but is not limited to, the following: connection establishment success rate (the number of successful connection establishments divided by the total number of connection attempts, used to measure the performance of the access network), handover success rate (the number of successful handovers divided by the number of handovers initiated, reflecting the effectiveness of mobility management), average downlink throughput (the average of the total downlink data transmission volume of all users within a certain time window), etc.

[0039] Optionally, in this embodiment, the second data may, but is not limited to, refer to measurement data about network coverage quality detected and reported by terminal devices (such as mobile phones and IoT devices) to network devices. This type of data is process-oriented, provides real-time feedback on network conditions, and helps with refined management and problem localization.

[0040] Optionally, in this embodiment, the amount of the second data can be, but is not limited to, extremely large; for example, a single cell can generate tens of thousands of records per hour.

[0041] Optionally, in this embodiment, to ensure that the reported operation and maintenance data is strictly aligned with the standard time window (e.g., whole 5 / 15 / 60 minutes) and to avoid errors in KPI aggregation of network management devices due to deviations in the triggering time of the processing module (OM), the processing module (OM) can be configured not to rely on the time difference between "the last read" and "now", but to calculate the standard cycle boundary based on UTC to achieve absolute time alignment. This ensures that no matter when the OM is scheduled to execute, the data processed by the OM (including the first data and the second data) strictly adheres to the mechanism of "belonging to the previous cycle".

[0042] Optionally, the algorithm for calculating the standard period boundary may include, but is not limited to, the following: If the current system time of the network device is T_now (unit: milliseconds, format: UTC) and the user-configured period is P (unit: seconds), the period may be converted to milliseconds first, P_ms = P × 1000; then, the period in which the current time falls is calculated by rounding down, T_end = |T_now / P_ms| × P_ms; then, the start time of this period is calculated, T_prev = T_end – P_ms; then, data in the intermediate cache that meets the time requirements is filtered, T_prev <= record <= T_end, that is, the time when the data collection / generation time falls within this period is filtered. For example, converting the current period to milliseconds: P = 15 minutes = 900 seconds, then P_ms = 900,000 milliseconds; calculating the period end time: T_now = 10:15:23.456, converted to milliseconds = [10 × 3600 + 15 × 60 + 23] seconds × 1000 + 456 = 36,923,456 ms; calculating how many periods the current time has spanned: 36,923,456 / 900,000 ≈ 41.026, rounded to 41; calculating the period end time: T_end = 41 × 900,000 = 3,690,000 0ms, converted to time 36900000ms = 36900 seconds = 10 hours 15 minutes 0 seconds, i.e. 10:15:00.000; Calculation cycle start time: T_prev = T_end - P_ms = 36900000 - 900000 = 36000000ms = 10:00:00.000; Data filtering: Data between 10:00:00.000 and 10:15:00.000 is the data that may be reported to the network management device this time, i.e., the first and second data needed this time.

[0043] By accurately calculating the cycle boundary, even if the network device restarts or there is a delay in the OM scheduling in the network device, the data can still be guaranteed to fall into the correct cycle, and the network management device can aggregate data without ambiguity.

[0044] Optionally, in this embodiment, the first and second data can be collected and parsed simultaneously on the network device according to the parsing logic of the first data and the parsing logic of the second data, respectively, and then jointly analyzed. The results of the joint analysis are then sent to the network management device. Alternatively, the storage and parsing methods of the first and second data can be integrated in the following ways to solve the problem of difficulty in joint analysis on the network management device side at a unified time window, caused by the first and second data belonging to different cache queues, requiring the maintenance of two sets of parsing logics, and having different reporting paths or file naming rules. Specifically, the problems of inconsistent time bases, inconsistent formats, and scattered parsing logic of the two types of heterogeneous data can be solved by combining unified timestamp marking and standardized cache record structure. Optionally, before the first and second data are written to the intermediate cache, the acquisition module (bottom layer) of the network device can forcibly encapsulate the first and second data into a unified metadata header + payload structure, so that the processing module (OM) of the network device can parse and process them uniformly without distinguishing the data source. Table 1 is an exemplary cache record structure.

[0045] Table 1

[0046]

[0047] Optionally, in this embodiment, after achieving single-pipeline processing through pre-standardized encapsulation and significantly reducing code complexity and memory overhead, a lock-free cache read / write mechanism based on atomic pointers can be designed, but is not limited to. This can include, but is not limited to, maintaining two 64-bit global offset pointers in the system: a write pointer (WP): atomically incremented by the acquisition module after successfully writing a record, accumulating the total number of bytes (never wrapping around, capable of continuous operation for >1 million years); and a read pointer (RP): atomically updated by the processing module to the latest processed position after successfully processing a batch of data.

[0048] The following decision logic can be set, but is not limited to: if WP > RP, it indicates that there is unprocessed data; if WP == RP, it indicates that the cache is empty. Optionally, but not limited to, in the event of a write failure, the failed data can be discarded directly. Optionally, if the CRC check fails during a read operation, the read request can be skipped and other requests can continue to be executed, ensuring that WP ≥ RP always holds true, in order to avoid complex reset logic.

[0049] Optionally, in this embodiment, Table 2 is a read / write operation example of a lock-free cache read / write mechanism based on atomic pointers according to an embodiment of this application.

[0050] Table 2

[0051]

[0052] Optionally, in this embodiment, network fault information may refer to, but is not limited to, any signs and detailed descriptions of problems that occur during network operation that affect network performance, stability, and quality of service (e.g., the type of fault, the degree of impact of the fault, etc.), or the importance of current operation and maintenance control of network devices determined based on these signs and detailed descriptions.

[0053] Optionally, in this embodiment, network fault information of network devices can be detected based on the first data and the second data in the following ways, but not limited to: monitoring key service execution status indicators in the first data (such as connection establishment success rate, number of successful handovers, service call drop rate, etc.). When a certain indicator is found to suddenly drop or exceed a preset threshold, it is determined that the network device may have a fault or performance degradation. For example, if the connection establishment success rate is consistently below 90%, the current network fault information is determined to be that the network device may have a hardware problem, a software bug, or a high load on the network device.

[0054] Optionally, in this embodiment, network fault information of network devices can also be detected by, but not limited to, the following methods: analyzing second data to determine the current network fault information. For example, analyzing wireless measurement information reported by terminal devices (such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), etc.) to detect network coverage quality and wireless link status. When multiple terminals frequently report low-quality signals (such as RSRP below -110dBm), the current network fault information is determined to be a fault in the antenna feeder system of the network device or the presence of external interference.

[0055] Optionally, in this embodiment, network fault information of network devices can also be detected by combining the first data and the second data simultaneously.

[0056] In the technical solution provided in step S206 above, the network fault information may include, but is not limited to, different types of network faults, and may include, but is not limited to, data related to the type of network fault represented by the detected network fault information as target data, selected from the first data and the second data.

[0057] Optionally, in this embodiment, network fault information may also represent different levels of importance of operation and maintenance needs. It may also select target data from the first data and the second data that matches the level of importance for operation and maintenance needs of different levels of importance. That is, the greater the importance, the more data the target data has.

[0058] In one exemplary embodiment, target data correlated with network fault information can be filtered from the first data and the second data in the following manner, but not limited to: by analyzing the correlation between the service status in the first data and the terminal measurement results in the second data, data directly related to the fault information can be filtered out. For example, if a decrease in handover success rate is detected, and MR shows abnormal fluctuations in neighboring cell signal strength, then these two types of data become target data because they both point to an interference source or network configuration error.

[0059] In one exemplary embodiment, target data related to network fault information can be filtered from the first and second data in the following ways, but not limited to: setting thresholds for various performance indicators and measurement results, as well as data priorities, and prioritizing the filtering of critical data that exceeds the thresholds. Furthermore, the data filtering strategy is dynamically adjusted according to the urgency of the network fault, prioritizing the reporting of data that may have a significant impact. For example, if the cell load is too high and the average throughput per person is extremely low, this will be marked as the highest priority and all data will be reported, while minor anomalies (such as occasional handover failures) will only be reported as summary information.

[0060] In one exemplary embodiment, network fault information of a network device can be detected based on first data and second data in the following ways, but not limited to: detecting the periodic fault state of the network device in the current period based on the first data and second data to obtain the current fault state, wherein the periodic fault state is the implementation state of the network device in implementing network coverage function within the corresponding periodic time period, and the implementation state includes abnormal state and normal state; detecting operation and maintenance requirement information based on the current fault state and historical fault state, wherein the historical fault state is the periodic fault state of the network device in the historical periods before the current period, and the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of the network device, and the network fault information includes operation and maintenance requirement information.

[0061] Optionally, in this embodiment, the periodic fault state may refer to, but is not limited to, the overall operating status and service execution status of the network device within a specific period during which the network device performs network coverage services. This state is a comprehensive evaluation of the network device's performance and behavior throughout the entire period, and can be divided into abnormal and normal states. An abnormal state means that during this period, the network device's performance indicators deviate from the standard or threshold for normal operation, which may be caused by various factors, such as hardware failure, software defects, configuration errors, external interference, etc. A normal state, on the other hand, indicates that all performance indicators of the network device during this period are within acceptable ranges, and no problems affecting service quality and stability have been detected.

[0062] Optionally, in this embodiment, the periodic fault status may be, but is not limited to, a comprehensive evaluation output. The periodic fault status may be, but is not limited to, the analysis results based on the first data and the second data, representing the operating status of the network device within a certain period, i.e., whether it has encountered a fault that affects the quality of service.

[0063] By combining the first and second data within a single cyclical framework for analysis, rather than viewing each type of data in isolation, we can more comprehensively assess the operational status of network devices, accurately identify faults, and reduce the possibility of false alarms and missed alarms.

[0064] Optionally, in this embodiment, the importance of current network device operation and maintenance control can be analyzed by combining the current fault status of the current cycle with the historical fault status of historical cycles. By dynamically adjusting the importance of operation and maintenance requirement information based on the changes in the periodic fault status and the comparison with historical status, high-level operation and maintenance responses can be triggered in a timely manner when a fault first occurs and during fault recovery. When the fault persists or the network device continues to operate normally, lower-level control measures can be taken, thereby avoiding excessive intervention or slow response.

[0065] In one exemplary embodiment, maintenance requirement information can be detected based on the current fault state and historical fault states in the following ways, but not limited to: when the current fault state is an abnormal state and the historical fault state is a normal state, determining that the maintenance requirement information indicates an importance greater than a first importance threshold; when the current fault state is a normal state and the historical fault state is a normal state, determining that the maintenance requirement information indicates an importance less than or equal to the first importance threshold, and greater than a second importance threshold; when the current fault state is an abnormal state and the historical fault state is an abnormal state, determining that the maintenance requirement information indicates an importance less than or equal to the second importance threshold; when the current fault state is a normal state and the historical fault state is an abnormal state, determining that the maintenance requirement information indicates an importance greater than the first importance threshold.

[0066] Optionally, in this embodiment, when the periodic fault state of a network device changes from a normal state to an abnormal state, it is necessary to obtain a large amount of complete data to better analyze the reasons for the network device turning to an abnormal state. Therefore, it is possible, but not limited to, to determine the importance of the current operation and maintenance requirements as the highest level of importance, that is, to determine the operation and maintenance requirements information to indicate that the importance is greater than the first importance threshold.

[0067] Optionally, in this embodiment, when the periodic fault state of the network device changes from an abnormal state to a normal state, it is also necessary to obtain a large amount of complete data to verify the effect of the adjustment operation taken by the network management device on the fault repair of the network device. Therefore, it is possible, but not limited to, and necessary to determine the importance of the current operation and maintenance needs as the highest level of importance, that is, to determine the operation and maintenance needs information to indicate that the importance is greater than the first importance threshold.

[0068] Optionally, in this embodiment, when the periodic fault state of the network device continues to remain in the normal state, it may be necessary, but is not limited to, to obtain some information to further determine the fault state of the network device. Therefore, it may be necessary, but is not limited to, to determine the importance of the current operation and maintenance requirement as an intermediate level of importance, that is, to determine the operation and maintenance requirement information to indicate that the importance is less than or equal to the first importance threshold and greater than the second importance threshold.

[0069] Optionally, in this embodiment, if the periodic fault state of the network device continues to remain in an abnormal state, the operation and maintenance data corresponding to the abnormal state has already been reported when the abnormal state first appears. The operation and maintenance personnel are likely to know that the problem exists. Therefore, it is not very valuable to report the operation and maintenance data again. Therefore, it is possible, but not limited to, to determine the importance of the current operation and maintenance needs as a lower level of importance, that is, to determine the operation and maintenance needs information to indicate that the importance is less than or equal to the second importance threshold.

[0070] Optionally, in this embodiment, target data can be filtered according to the level of importance, but not limited to. For example, if the level of importance is the highest, the first data and the second data can be determined as target data; if the level of importance is intermediate, the first data and the second sub-data obtained by lightweighting the second data (for example, the second sub-data can be used to indicate the average network quality collected by the terminal device) can be determined as target data; if the level of importance is low, the first data can be determined as target data.

[0071] In one exemplary embodiment, the current fault state can be obtained by detecting the periodic fault state of the network device in the current period based on the first data and the second data in the following manner, but not limited to: detecting whether each first sub-data in the first data falls within the first target range corresponding to each first sub-data, and detecting whether the second sub-data falls within the second target range corresponding to the second sub-data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; if the target sub-data does not fall within the first target range corresponding to the target sub-data, and / or the second sub-data does not fall within the second target range, the current fault state is determined to be an abnormal state, wherein the target sub-data is any one of the first sub-data; if each first sub-data falls within the first target range corresponding to each first sub-data, and the second sub-data falls within the second target range, the current fault state is determined to be a normal state.

[0072] Optionally, in this embodiment, the first data may refer to, but is not limited to, a set of performance counters for network devices. For example, in a typical 5G base station, the first data may include, but is not limited to, the following first sub-data: rrc_setup_success_rate (RRC establishment success rate), handover_attempted (number of handover attempts), handover_succeeded (number of successful handovers), call_drop_rate (call drop rate), avg_dl_throughput (average downlink throughput), etc.

[0073] Optionally, in this embodiment, the second sub-data may be, but is not limited to, the average network quality calculated from the measurement reports uploaded by the terminal device, such as avg_sinr (average SINR, i.e., signal-to-noise ratio plus interference). This value may be, but is not limited to, obtained by statistically averaging the SINR values ​​from multiple MR reports, and is used to evaluate the quality of the wireless link. A higher SINR value means better signal quality and less interference.

[0074] By monitoring the first and second data points, the current periodic fault status of network devices is determined, improving the sensitivity and accuracy of fault detection. By setting a first target range for each first sub-data point and a second target range for each second sub-data point, it is possible to accurately determine whether the network device's operation has deviated from its normal service level.

[0075] In one exemplary embodiment, target data that is associated with network fault information can be filtered from first data and second data in the following ways, but not limited to: detecting coverage information of the second data over the first data, wherein the coverage information is used to indicate the degree of overlap between the second collection time period of the second data and the first collection time period of the first data; filtering target data from the first data and second data based on the coverage information and operation and maintenance requirement information, wherein the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of network devices, and the network fault information includes the operation and maintenance requirement information.

[0076] Optionally, in this embodiment, the target data to be reported is accurately located by detecting the coverage information of the second data (network quality data detected by the terminal device) over the first data (service execution status data of the network device), that is, by assessing the degree of overlap between the collection time windows of the two. The core advantage of this mechanism is that it can dynamically adjust the reporting strategy according to the time relevance of the data and the importance of the operation and maintenance requirements, ensuring that the operation and maintenance data received by the network management device is not only closely related to the current network fault information, but also reflects the full picture and depth of the fault, thereby greatly improving the efficiency of fault diagnosis and network optimization.

[0077] In one exemplary embodiment, target data can be selected from first data and second data based on coverage information and operation and maintenance requirement information in the following ways, but not limited to: When the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree greater than a first importance threshold, the first data and second data are determined as target data; when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to a first importance threshold and greater than a second importance threshold, the first data and second sub-data are determined as target data, wherein the second sub-data indicates the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to a second importance threshold... Under the threshold condition, the system detects whether the abnormal reporting opportunity for operation and maintenance data has been reached. If the abnormal reporting opportunity has been reached, the first data and the second sub-data are determined as target data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data. If the abnormal reporting opportunity has not been reached, the first data is determined as target data. If the coverage information is used to indicate that the overlap degree is less than the overlap degree threshold, and the operation and maintenance requirement information is used to indicate that the importance is less than or equal to the first importance threshold, the first data is determined as target data. If the coverage information is used to indicate that the overlap degree is less than the overlap degree threshold, and the operation and maintenance requirement information is used to indicate that the importance is greater than the first importance threshold, target data is selected from the first data and the second data based on reference sub-data, wherein the reference sub-data is used to indicate the signaling performance of the network device, and the first data includes the reference sub-data.

[0078] Optionally, in this embodiment, a data reporting strategy can be set after an abnormal state is detected, i.e., how to decide when to report abnormal data in a continuous abnormal cycle. The abnormal reporting timing here can be understood as selecting to report all abnormal data at one or more specific time points during a continuous abnormal state, rather than reporting it in every cycle. This mechanism is particularly suitable when network devices are in an abnormal state for a long time, avoiding repeated reporting of the same problem, reducing the amount of data exchange between the network management system and network devices, and also avoiding the fatigue of maintenance personnel dealing with repetitive and unresolved information.

[0079] Optionally, in this embodiment, when the overlap between the second collection time period indicated by the coverage information and the first collection time period is poor (i.e., the overlap is less than the overlap threshold), the second data may be avoided as much as possible, because the second data that can be obtained at this time is not good at explaining the first data, and the value of reporting the second data is not great. However, in some special cases, there may be a need to upload the second data with poor coverage. For example, when the data is of high importance but has a low overlap, it is necessary to further determine the target data based on the current signaling performance of the network device.

[0080] Optionally, in this embodiment, the reference sub-data may refer to, but is not limited to, a specific subset of data used to evaluate the signaling plane performance and health status of network devices. The reference sub-data may include, but is not limited to, handover request counts, channel establishment failure rate, signaling latency, and signaling congestion rate, etc. The reference sub-data may be, but is not limited to, one type of data in the first data set.

[0081] In one exemplary embodiment, target data may be selected from first data and second data based on reference sub-data in the following manner, but not limited to: detecting whether the reference sub-data falls within a first reference range corresponding to the reference sub-data; if the reference sub-data falls within the first reference range, determining the first data as target data; if the reference sub-data does not fall within the first reference range, determining the first data and second data as target data.

[0082] Optionally, in this embodiment, even if the network device performs poorly in terms of network coverage and signaling, all maintenance data will help in analyzing network device malfunctions. Therefore, even if the overlap indicated by the coverage information is small (i.e. less than the overlap threshold), the second data still needs to be reported in full.

[0083] Optionally, in this embodiment, when the reference sub-data is data in the first data, the first reference range is larger than the first target range.

[0084] As an optional implementation, this application provides an operation and maintenance data reporting management scheme that combines a unified timestamp marker and a standardized cache record structure, a lock-free cache read and write mechanism based on atomic pointers, precise data truncation based on standard time, and intelligent control of MR reporting based on performance counters. Figure 3 This is a flowchart of a reporting and management scheme for operation and maintenance data according to an embodiment of this application. Figure 3The scheme combining unified timestamp marking with standardized cache record structure, lock-free cache read / write mechanism based on atomic pointers, and precise data truncation based on standard time has already been explained and will not be repeated here. Figure 3 As shown, this application proposes a scheme that uses a performance counter as a health monitoring anchor point, and only reports the complete original MR when an anomaly is detected, while only uploading a lightweight aggregated summary MR (i.e., second data) when normal.

[0085] Specifically, multi-dimensional performance monitoring tasks can be automatically established, but are not limited to, monitoring whether the following indicators (i.e., each first sub-data point) exceed reasonable thresholds: whether rrc_setup_success_rate (RRC setup success rate, number of successful RRC requests / number of RRC requests) is lower than 98%; whether call_drop_rate (call drop rate, number of dropped calls / total number of successfully established connections) is greater than 2%; whether handover_success_rate (handover success rate, number of successful handovers / total number of handover attempts) is less than 95%; whether avg_dl_throughput_per_ue (average downlink throughput per user, total downlink traffic (bits) / (number of active users × period duration)) is lower than 500 kbps under 4G; whether avg_dl_throughput_per_ue is lower than 2000 kbps under 5G; and whether low_throughput_ue_ratio (percentage of users with low throughput, (throughput < 300 kbps) is lower than 2000 kbps. The following parameters are considered: whether the percentage of active UEs (number of active UEs per kbps) / total number of active UEs is greater than 60%; whether dl_prb_utilization (number of used PRBs / total number of available PRBs) is greater than 90% and the average throughput per user is less than 300 kbps; and whether the month-on-month decrease in dl_data_volume_mb (total downlink traffic of the cell, the sum of downlink data volume of all UEs within the period) is greater than 70%. Simultaneously, lightweight aggregation is performed on MR to calculate avg_sinr (average signal-to-interference-plus-noise ratio) (i.e., the second sub-data).

[0086] Furthermore, collaborative time alignment is performed using the performance counter (i.e., the first data) as the anchor point. Specifically, it can, but is not limited to, detecting the status of MR. When the MR fully covers the performance counter, the MR is normally aggregated or reported completely. When the MR partially or does not cover the performance counter, the coverage rate is calculated. Only when the coverage rate is greater than or equal to 50% (i.e., the overlap threshold) is it used for abnormal reporting. In other cases, the MR is not extracted. If the performance is abnormal, only the alarm flag is reported.

[0087] For data storage, performance counter data is processed, written to a local file, and then uploaded to the network management system (i.e., the network management device). For MR data, when performance monitoring is abnormal: the original MR data is extracted, parsed, and then written in full to a local file, uploaded to the network management system, and immediately deleted after upload; when performance monitoring is normal: the original MR data is not retained, only a lightweight aggregation record is generated, written to a local file, and only the UTC time (start and end times), site ID, and calculated avg_sinr are reported, and then immediately deleted after upload.

[0088] Optionally, in this embodiment, the state determination (i.e., the detection cycle fault state) can be performed according to, but is not limited to, the following logic:

[0089] If conditions A and B are met simultaneously, the current state is considered normal: A. Context valid: The current time period is a low-traffic scenario (0:00~6:00) or, although it is a low-traffic period, all indicators meet expectations. B. All indicators that meet the validity conditions have not exceeded the threshold.

[0090] An abnormal state is determined when any of the following conditions are met: A. There is a valid and excessive performance indicator, such as avg_sinr < 0dB and MR coverage ≥ 50%. B. Zero call traffic occurs during the valid business period (e.g., weekdays 8:00–22:00), and there is usually call traffic during the same period in history. C. MR coverage < 50% but the signaling plane KPI (i.e., reference sub-data) is significantly degraded (e.g., call drop rate > 5%).

[0091] Furthermore, a state machine can be used, but is not limited to, to control the reporting frequency and avoid redundant reporting. Table 3 is a correspondence table between the states of a state machine and their corresponding operations according to an embodiment of this application. The state machine can determine how to report MR based on the correspondence shown in Table 3, but is not limited to.

[0092] Table 3

[0093]

[0094] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software and necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0095] Figure 4 This is a structural block diagram of a maintenance data reporting device according to an embodiment of this application; as shown below. Figure 4 As shown, the device includes:

[0096] The receiving module 402 is used to receive data reporting requests, wherein the data reporting requests are used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device;

[0097] The detection module 404 is used to detect network fault information of the network device based on the first data and the second data. The first data is used to indicate the service execution status of the network device when performing network coverage services, and the second data is used to indicate the network coverage quality of the network device detected by the terminal device accessing the network device.

[0098] The filtering module 406 is used to filter out target data that is related to network fault information from the first data and the second data.

[0099] The reporting module 408 is used to report target data to the network management device, which is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0100] Through the above embodiments, a data reporting request is received, instructing the network device to report network device operation and maintenance data to the connected network management device. Based on first data indicating the service execution status of the network device when performing network coverage services and second data indicating the network coverage quality detected by the terminal device accessing the network device, network fault information of the network device is detected. Target data related to the network fault information is filtered from the first and second data and reported to the network management device. That is, the reported operation and maintenance data is associated with the current network fault information of the network device, avoiding the blind full reporting of the first and second data and preventing the waste of bandwidth resources. By adopting the above technical solution, the problem of bandwidth resource waste during operation and maintenance data reporting in related technologies is solved, achieving the technical effect of saving bandwidth resources during operation and maintenance data reporting.

[0101] In an exemplary embodiment, the detection module includes: a first detection unit, configured to detect the periodic fault state of a network device in the current period based on first data and second data, to obtain the current fault state, wherein the periodic fault state is the implementation state of the network device in implementing network coverage function within the corresponding periodic time period, and the implementation state includes an abnormal state and a normal state; and a second detection unit, configured to detect operation and maintenance requirement information based on the current fault state and historical fault states, wherein the historical fault states are the periodic fault states of the network device in historical periods prior to the current period, and the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of the network device, and the network fault information includes the operation and maintenance requirement information.

[0102] In one exemplary embodiment, the second detection unit is further configured to: determine that the importance of the maintenance requirement information is greater than a first importance threshold when the current fault state is an abnormal state and the historical fault state is a normal state; determine that the importance of the maintenance requirement information is less than or equal to the first importance threshold and greater than a second importance threshold when the current fault state is a normal state and the historical fault state is a normal state; determine that the importance of the maintenance requirement information is less than or equal to the second importance threshold when the current fault state is an abnormal state and the historical fault state is an abnormal state; and determine that the importance of the maintenance requirement information is greater than the first importance threshold when the current fault state is a normal state and the historical fault state is an abnormal state.

[0103] In an exemplary embodiment, the first detection unit is further configured to: detect whether each first sub-data in the first data falls within the first target range corresponding to each first sub-data, and detect whether the second sub-data falls within the second target range corresponding to the second sub-data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; if the target sub-data does not fall within the first target range corresponding to the target sub-data, and / or the second sub-data does not fall within the second target range, determine the current fault state as an abnormal state, wherein the target sub-data is any one of the first sub-data; if all the first sub-data falls within the first target range corresponding to each first sub-data, and the second sub-data falls within the second target range, determine the current fault state as a normal state.

[0104] In one exemplary embodiment, the filtering module includes: a third detection unit, configured to detect coverage information of the second data over the first data, wherein the coverage information is used to indicate the degree of overlap between the second collection time period of the second data and the first collection time period of the first data; and a filtering unit, configured to filter target data from the first data and the second data based on the coverage information and operation and maintenance requirement information, wherein the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of network devices, and network fault information includes the operation and maintenance requirement information.

[0105] In one exemplary embodiment, the filtering unit is further configured to: determine the first data and the second data as target data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree greater than a first importance threshold; determine the first data and the second sub-data as target data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to the first importance threshold and greater than a second importance threshold, wherein the second sub-data indicates the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; and detect abnormal reporting of operation and maintenance data when the coverage information indicates an overlap degree greater than or equal to an overlap degree threshold, and the operation and maintenance requirement information indicates an importance degree less than or equal to the second importance threshold. Whether the timing has been reached; if the timing for an anomaly reporting has been reached, the first data and the second sub-data are determined as target data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data; if the timing for anomaly reporting has not been reached, the first data is determined as target data; if the coverage information is used to indicate that the overlap degree is less than the overlap degree threshold, and the operation and maintenance requirement information is used to indicate that the importance is less than or equal to the first importance threshold, the first data is determined as target data; if the coverage information is used to indicate that the overlap degree is less than the overlap degree threshold, and the operation and maintenance requirement information is used to indicate that the importance is greater than the first importance threshold, target data is selected from the first data and the second data based on reference sub-data, wherein the reference sub-data is used to indicate the signaling performance of the network device, and the first data includes the reference sub-data.

[0106] In an exemplary embodiment, the filtering unit is further configured to: detect whether the reference sub-data falls within the first reference range corresponding to the reference sub-data; if the reference sub-data falls within the first reference range, determine the first data as target data; if the reference sub-data does not fall within the first reference range, determine the first data and the second data as target data.

[0107] Embodiments of this application also provide a storage medium, which includes a stored program, wherein the program executes any of the above-mentioned methods for reporting maintenance data when it runs.

[0108] Optionally, in this embodiment, the storage medium may be configured to store program code for performing the following steps:

[0109] S1, Receive data reporting request, wherein the data reporting request is used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device;

[0110] S2, Detect network fault information of network devices based on first data and second data, wherein the first data is used to indicate the service execution status of network devices when performing network coverage services, and the second data is used to indicate the network coverage quality of network devices detected by terminal devices accessing network devices;

[0111] S3, Filter out target data that is related to network fault information from the first data and the second data;

[0112] S4 reports the target data to the network management device, which is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0113] Embodiments of this application also provide 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 perform the steps in any of the above embodiments of the method for reporting maintenance data.

[0114] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0115] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0116] S1, Receive data reporting request, wherein the data reporting request is used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device;

[0117] S2, Detect network fault information of network devices based on first data and second data, wherein the first data is used to indicate the service execution status of network devices when performing network coverage services, and the second data is used to indicate the network coverage quality of network devices detected by terminal devices accessing network devices;

[0118] S3, Filter out target data that is related to network fault information from the first data and the second data;

[0119] S4 reports the target data to the network management device, which is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

[0120] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0121] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0122] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above embodiments of the operation and maintenance data reporting method.

[0123] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above embodiments of the operation and maintenance data reporting method.

[0124] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0125] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for reporting operation and maintenance data, characterized in that, include: Receive a data reporting request, wherein the data reporting request is used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device; The network fault information of the network device is detected based on the first data and the second data, wherein the first data is used to indicate the service execution status of the network device when performing network coverage services, and the second data is used to indicate the network coverage quality of the network device detected by the terminal device accessing the network device. Target data that is correlated with the network fault information is selected from the first data and the second data; The target data is reported to the network management device, wherein the network management device is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

2. The method according to claim 1, characterized in that, The step of detecting network fault information of the network device based on the first data and the second data includes: The network device is detected in the current period based on the first data and the second data to obtain the current fault state. The periodic fault state is the implementation state of the network device when implementing the network coverage function within the corresponding periodic time period. The implementation state includes abnormal state and normal state. Operation and maintenance requirement information is detected based on the current fault status and historical fault status, wherein the historical fault status is the periodic fault status of the network device in the historical period before the current period, and the operation and maintenance requirement information is used to indicate the importance of operation and maintenance control of the network device, and the network fault information includes the operation and maintenance requirement information.

3. The method according to claim 2, characterized in that, The step of detecting maintenance requirements based on the current fault status and historical fault status includes: If the current fault state is the abnormal state and the historical fault state is the normal state, the operation and maintenance requirement information is determined to indicate that the importance level is greater than the first importance threshold. When the current fault state is the normal state and the historical fault state is the normal state, the operation and maintenance requirement information is determined to indicate that the importance is less than or equal to the first importance threshold and greater than the second importance threshold. If the current fault state is the abnormal state and the historical fault state is the abnormal state, the operation and maintenance requirement information is determined to indicate that the importance is less than or equal to the second importance threshold. When the current fault state is the normal state and the historical fault state is the abnormal state, the operation and maintenance requirement information is determined to indicate that the importance level is greater than the first importance threshold.

4. The method according to claim 2, characterized in that, The step of detecting the periodic fault state of the network device in the current period based on the first data and the second data, and obtaining the current fault state, includes: The system detects whether each first sub-data in the first data falls within the first target range corresponding to each first sub-data, and detects whether the second sub-data falls within the second target range corresponding to the second sub-data. The second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more second data. If the target sub-data does not fall within the first target range corresponding to the target sub-data, and / or the second sub-data does not fall within the second target range, the current fault state is determined to be the abnormal state, wherein the target sub-data is any one of the first sub-data; If each of the first sub-data points falls within the first target range corresponding to each of the first sub-data points, and the second sub-data point falls within the second target range, then the current fault state is determined to be the normal state.

5. The method according to claim 1, characterized in that, The step of filtering target data that is related to the network fault information from the first data and the second data includes: Detect the coverage information of the second data over the first data, wherein the coverage information is used to indicate the degree of overlap between the second collection time period of the second data and the first collection time period of the first data; The target data is selected from the first data and the second data based on the coverage information and the operation and maintenance requirements information, wherein the operation and maintenance requirements information is used to indicate the importance of operation and maintenance control of the network device, and the network fault information includes the operation and maintenance requirements information.

6. The method according to claim 5, characterized in that, The step of filtering the target data from the first data and the second data based on the coverage information and operation and maintenance requirements information includes: When the coverage information indicates that the degree of overlap is greater than or equal to the degree of overlap threshold, and the maintenance requirement information indicates that the degree of importance is greater than the first importance threshold, the first data and the second data are determined as the target data; When the coverage information indicates that the degree of overlap is greater than or equal to the degree of overlap threshold, and the maintenance requirement information indicates that the degree of importance is less than or equal to the first importance threshold and greater than the second importance threshold, the first data and the second sub-data are determined as the target data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more of the second data; When the coverage information indicates that the overlap is greater than or equal to the overlap threshold, and the maintenance requirement information indicates that the importance is less than or equal to the second importance threshold, it is detected whether the abnormal reporting opportunity for the maintenance data has been reached; if the abnormal reporting opportunity has been reached, the first data and the second sub-data are determined as the target data, wherein the second sub-data is used to indicate the average network quality collected by the terminal device, and the second sub-data is calculated based on one or more of the second data; if the abnormal reporting opportunity has not been reached, the first data is determined as the target data. When the coverage information indicates that the degree of overlap is less than the overlap threshold, and the maintenance requirement information indicates that the degree of importance is less than or equal to a first importance threshold, the first data is determined as the target data; When the coverage information indicates that the degree of overlap is less than the overlap threshold, and the operation and maintenance requirement information indicates that the degree of importance is greater than the first importance threshold, the target data is filtered from the first data and the second data according to the reference sub-data, wherein the reference sub-data is used to indicate the signaling performance of the network device, and the first data includes the reference sub-data.

7. The method according to claim 6, characterized in that, The step of filtering the target data from the first data and the second data based on reference sub-data includes: Detect whether the reference sub-data falls within the first reference range corresponding to the reference sub-data; If the reference sub-data falls within the first reference range, the first data is determined as the target data; If the reference sub-data does not fall within the first reference range, the first data and the second data are determined as the target data.

8. A device for reporting operation and maintenance data, characterized in that, include: A receiving module is used to receive data reporting requests, wherein the data reporting requests are used to instruct the network device to report the operation and maintenance data of the network device to the connected network management device; The detection module is used to detect network fault information of the network device based on first data and second data, wherein the first data is used to indicate the service execution status of the network device when performing network coverage services, and the second data is used to indicate the network coverage quality of the network device detected by the terminal device accessing the network device; A filtering module is used to filter out target data that is related to the network fault information from the first data and the second data; The reporting module is used to report the target data to the network management device, wherein the network management device is used to adjust the service execution status of the network device when performing network coverage services based on the target data.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method of any one of claims 1 to 7.

10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 7 through the computer program.

Images