Network fault detection method, device, equipment, medium and program product

Abstract

The invention provides a network fault detection method, device and equipment, a medium and a program product, which can be applied to the technical field of network security. The method comprises the following steps: in response to a network log file representing that a network has a fault, determining a fault moment when the network has the fault; determining a first detection result based on the signal intensity value of the network connection signal; under the condition that the first detection result represents that the network connection signal is normal, determining a re-detection moment based on the fault moment and the detection time interval; determining a second detection result based on the connection condition of the network at the re-detection moment; comparing the hardware configuration information of the Internet of Things hardware with file configuration information set in the configuration file of the network to determine a third detection result; determining a fourth detection result based on a data record in an interface log file of the network communication interface; and determining a fault detection result of the network based on the first detection result, the second detection result, the third detection result and the fourth detection result.

Description

Technical Field

[0001] This disclosure relates to the field of network security technology, and specifically to a network fault detection method, apparatus, device, medium, and program product. Background Technology

[0002] With the development of IoT technology, controlling IoT hardware through networks and detecting and analyzing its operating status can improve the control efficiency of IoT hardware. The IoT connection of escalators and elevators includes the connection between the gateway and the escalator controller, as well as the connection between the gateway and the cloud. By analyzing the data transmitted in real time by the escalator controller, the control efficiency of the escalator can be improved and the probability of escalator failure can be reduced.

[0003] In the process of implementing this disclosure, the inventors discovered that the prior art has at least the following problems: when the network or IoT hardware fails, the cloud will be unable to receive the data transmitted in real time by the escalator controller. Therefore, it is impossible to locate the fault location by simply analyzing the cloud's data reception. Manual inspection of the operation of the network and IoT hardware is required, resulting in high labor costs and low detection efficiency. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a network fault detection method, apparatus, device, medium and program product.

[0005] According to a first aspect of this disclosure, a network fault detection method is provided, comprising: determining the fault time of the network fault in response to a network log file indicating a network fault; determining a first detection result based on the signal strength value of the network connection signal; determining a re-detection time based on the fault time and a detection time interval if the first detection result indicates that the network connection signal is normal; determining a second detection result based on the network connection status and signal strength value at the re-detection time; determining a third detection result by comparing the hardware configuration information of IoT hardware with the file configuration information set in the network configuration file; determining a fourth detection result based on data records in the interface log file of the network communication interface; and determining a network fault detection result based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0006] According to embodiments of this disclosure, determining a fourth detection result based on data records in the interface log file of a network communication interface includes: parsing multiple data records in the interface log file, determining the interaction type of each of the multiple data records, wherein the interaction type includes sending data and reading data; and determining that the fourth detection result characterizes a network interface communication anomaly when the multiple interaction types corresponding to the multiple data records do not include reading data.

[0007] According to embodiments of this disclosure, determining a first detection result based on the signal strength value of a network connection signal includes: acquiring the signal strength value of the network connection signal within a detection time interval; determining a calculated value of the network connection signal within the detection time interval based on the acquired signal strength value, wherein the calculated value includes an upper limit, a lower limit, and a mean signal; determining a signal comparison result by comparing the calculated value with a signal threshold, wherein the signal threshold includes an upper limit threshold, a lower limit threshold, and a mean threshold, and the signal comparison result includes multiple sub-results, a first sub-result representing the comparison result between the upper limit and the upper limit threshold, a second sub-result representing the comparison result between the lower limit and the lower limit threshold, a third sub-result representing the comparison result between the mean signal and the mean threshold; and determining that the first detection result represents an abnormal network connection signal when there is a sub-result in the signal comparison result representing a calculated value lower than the signal threshold.

[0008] According to embodiments of this disclosure, a third detection result is determined by comparing the hardware configuration information of IoT hardware with the file configuration information set in the network configuration file. This includes: determining the hardware configuration information of the IoT hardware, wherein the hardware configuration information includes the device number of the IoT hardware and the group number of the group to which the IoT hardware belongs; determining the file configuration information set in the configuration file, wherein the file configuration information includes the device numbers of the multiple IoT hardware devices controlled by the network and the group number of the group formed by the multiple IoT hardware devices; comparing the hardware configuration information of the IoT hardware with the file configuration information set in the configuration file to determine the comparison result; and if the comparison result indicates that the file configuration information does not include the device number of the IoT hardware or the group number of the IoT hardware group, determining that the third detection result indicates that the configuration file is incorrect.

[0009] According to embodiments of this disclosure, a second detection result is determined based on the network's connectivity status and signal strength value at a re-detection time, including: determining the network's connectivity status and signal strength value at the re-detection time; and determining that the second detection result indicates an abnormal network connectivity process when the connectivity status indicates a network anomaly and the signal strength value indicates a normal signal strength.

[0010] According to embodiments of this disclosure, determining network fault detection results based on first detection results, second detection results, third detection results, and fourth detection results includes: determining fault type and fault location in the network based on first detection results, second detection results, third detection results, and fourth detection results; and determining network fault detection results based on fault type and fault cause.

[0011] According to embodiments of this disclosure, the network fault detection method further includes: determining network repair methods based on the network fault type; determining network repair targets based on network fault location; determining network repair schemes based on the repair methods and repair targets; and repairing the network based on the repair schemes.

[0012] A second aspect of this disclosure provides a network fault detection device, comprising:

[0013] The fault determination module is used to determine the time of the network failure in response to the network log file indicating a network failure.

[0014] The first detection module is used to determine the first detection result based on the signal strength value of the network connection signal.

[0015] The timing determination module is used to determine the re-detection time based on the fault time and the detection time interval, when the first detection result indicates that the network connection signal is normal.

[0016] The second detection module is used to determine the second detection result based on the network's connectivity and signal strength value at the re-detection time.

[0017] The third detection module is used to compare the hardware configuration information of the IoT hardware with the file configuration information set in the network configuration file to determine the third detection result.

[0018] The fourth detection module is used to determine the fourth detection result based on data records in the interface log file of the network communication interface; and

[0019] The result determination module is used to determine the network fault detection result based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0020] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0021] A fourth aspect of this disclosure also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0022] The fifth aspect of this disclosure also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0023] According to embodiments of this disclosure, when network log files indicate a network failure, a first detection result, a second detection result, a third detection result, and a fourth detection result are determined by means of detecting network connection signals, re-detecting the network, hardware configuration information, and interface log files, thereby determining the fault detection result for the network status. Determining the overall network fault detection result through multiple means and multiple detection results ensures more comprehensive network fault detection, more accurate fault location, and improves the efficiency and accuracy of network fault detection. Attached Figure Description

[0024] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0025] Figure 1 The illustration schematically depicts application scenarios of network fault detection methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0026] Figure 2 A flowchart illustrating a network fault detection method according to an embodiment of the present disclosure is shown schematically.

[0027] Figure 3 A flowchart illustrating a network fault detection method according to another embodiment of the present disclosure is shown schematically;

[0028] Figure 4 A schematic diagram illustrating the structure of a network fault detection apparatus according to an embodiment of the present disclosure is shown; and

[0029] Figure 5 A block diagram of an electronic device suitable for implementing a network fault detection method according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0030] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0031] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0032] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0033] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0034] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0035] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this disclosure all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

[0036] Embodiments of this disclosure provide a network fault detection method, comprising: determining the fault time of the network fault in response to a network log file indicating a network fault; determining a first detection result based on the signal strength value of the network connection signal; determining a re-detection time based on the fault time and a detection time interval if the first detection result indicates that the network connection signal is normal; determining a second detection result based on the network connection status and signal strength value at the re-detection time; determining a third detection result by comparing the hardware configuration information of IoT hardware with the file configuration information set in the network configuration file; determining a fourth detection result based on data records in the interface log file of the network communication interface; and determining a network fault detection result based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0037] Figure 1 The illustration shows an application scenario of a network fault detection method, apparatus, device, medium, and program product according to embodiments of the present disclosure.

[0038] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, a server 105, and IoT hardware 106. The network 104 serves as a medium for providing communication links between the first terminal device 101, the second terminal device 102, the third terminal device 103, the network 104, the server 105, and the IoT hardware 106. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0039] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 and the IoT hardware 106 via the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103 to send and receive messages from the IoT hardware 106.

[0040] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0041] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0042] The IoT hardware 106 may include various sensors, actuators, communication modules, and other hardware that can interact with the first terminal device 101, the second terminal device 102, the third terminal device 103, the network 104, and the server 105 via the network 104.

[0043] It should be noted that the network fault detection method provided in this embodiment can generally be executed by server 105. Correspondingly, the network fault detection device provided in this embodiment can generally be located in server 105. The network fault detection method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105 and / or IoT hardware 106. Correspondingly, the network fault detection device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105 and / or IoT hardware 106.

[0044] It should be understood that Figure 1 The number of terminal devices, networks, servers, and IoT hardware shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, servers, and IoT hardware can be included.

[0045] The following will be based on Figure 1 The described scene, through Figures 2-3 The network fault detection method according to the embodiments of this disclosure will be described in detail.

[0046] Figure 2 A flowchart illustrating a network fault detection method according to an embodiment of the present disclosure is shown schematically.

[0047] like Figure 2 As shown, the network fault detection method of this embodiment includes operations S210 to S270.

[0048] In operation S210, in response to the network log file indicating a network failure, the timing of the network failure is determined.

[0049] According to embodiments of this disclosure, potential network fault types include physical network connection failures, network connection program failures, connection binding mismatches of IoT hardware, and network signal failures. The IoT hardware may include escalators, elevators, and other similar devices. When the network log file includes error logs, the network log file indicates a network fault, and the time of the fault can be determined based on the timestamps in the error logs.

[0050] According to embodiments of this disclosure, the network fault detection method can be triggered in response to a network log file indicating a network fault, or a detection period can be set and triggered after the detection period. Preferably, the detection period can be one hour.

[0051] In operation S220, the first detection result is determined based on the signal strength value of the network connection signal.

[0052] According to embodiments of this disclosure, the signal strength value of the network connection signal at the time of the fault is determined from the network log file, thereby determining a first detection result, wherein the first detection result is used to characterize whether the signal strength of the network connection signal is sufficient to support the network connection.

[0053] In operation S230, if the first detection result indicates that the network connection signal is normal, the re-detection time is determined based on the fault time and the detection time interval.

[0054] According to embodiments of this disclosure, the re-detection time can be determined by adding a detection time interval to the fault time, wherein the detection time interval is pre-configured, and preferably, the detection time interval can be 5 minutes.

[0055] In operation S240, the second detection result is determined based on the network's connectivity and signal strength at the re-detection time.

[0056] According to embodiments of this disclosure, the network connectivity is detected at a re-detection time, and a second detection result is determined based on the network connectivity and signal strength value at the re-detection time. The second detection result can be used to characterize whether there is a fault in the network's communication process.

[0057] When operating the S250, the hardware configuration information of the IoT hardware is compared with the file configuration information set in the network configuration file to determine the third detection result.

[0058] According to embodiments of this disclosure, hardware configuration information of IoT hardware is determined, and the hardware configuration information is compared with file configuration information set in the network's configuration file to determine a third detection result. The third detection result can be used to characterize whether the IoT hardware matches the IoT hardware information set in the network's configuration file.

[0059] During operation S260, the fourth detection result is determined based on the data recorded in the interface log file of the network communication interface.

[0060] According to embodiments of this disclosure, data records in the interface log file of the network communication interface are determined, and the attributes of each data record are determined. The attributes of the data record include the interaction attributes represented by the data record. The interaction attributes are used to represent the way the network communication interface processes data, such as sending data and reading data.

[0061] In operation S270, the fault detection results of the network are determined based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0062] According to embodiments of this disclosure, based on the first detection result, the second detection result, the third detection result, and the fourth detection result, information such as the type of fault existing in the network, the cause of the fault, and the location of the network fault is determined, thereby determining the fault result of the network.

[0063] According to embodiments of this disclosure, when network log files indicate a network failure, a first detection result, a second detection result, a third detection result, and a fourth detection result are determined by means of detecting network connection signals, re-detecting the network, hardware configuration information, and interface log files, thereby determining the fault detection result for the network status. Determining the overall network fault detection result through multiple means and multiple detection results ensures more comprehensive network fault detection, more accurate fault location, and improves the efficiency and accuracy of network fault detection.

[0064] According to embodiments of this disclosure, determining a fourth detection result based on data records in the interface log file of a network communication interface includes: parsing multiple data records in the interface log file, determining the interaction type of each of the multiple data records, wherein the interaction type includes sending data and reading data; and determining that the fourth detection result characterizes a network interface communication anomaly when the multiple interaction types corresponding to the multiple data records do not include reading data.

[0065] According to embodiments of this disclosure, an interface log file is obtained, and multiple data records in the interface log file are parsed to determine the interaction type of each of the multiple data records. The interaction type is used to characterize the information interaction type between the network communication interface and other hardware such as IoT devices, including sending data and reading data. Sending data characterizes the network communication interface sending data to other hardware through the network, and reading data characterizes the network communication interface reading data sent by other hardware through the network.

[0066] According to embodiments of this disclosure, after the network communication interface performs a data transmission action, the interface log file adds a corresponding data record with the interaction type of "sending data" and waits for a response from the IoT device. Only after the network communication interface receives the response data will the interface log file add a corresponding data record with the interaction type of "reading data". However, in the event of a network interface communication anomaly, the network communication interface can still transmit data normally, but the data cannot reach the target IoT hardware, and the network communication interface also cannot receive response data from the IoT hardware. Therefore, when multiple data records correspond to multiple interaction types of "sending data" and do not include "reading data", it indicates that the network communication interface only transmitted data and did not read data, thus confirming that the fourth detection result indicates a network interface communication anomaly.

[0067] According to embodiments of this disclosure, based on multiple data records in the interface log file, the interaction type of each data record is determined, and based on whether the interaction type includes reading data, it is determined whether there is a communication anomaly in the network interface. This allows for accurate judgment of the network interface's communication status based on the characteristics of data transmission and reception, improving the accuracy of network fault detection.

[0068] According to embodiments of this disclosure, determining a first detection result based on the signal strength value of a network connection signal includes: acquiring the signal strength value of the network connection signal within a detection time interval; determining a calculated value of the network connection signal within the detection time interval based on the acquired signal strength value, wherein the calculated value includes an upper limit, a lower limit, and a mean signal; determining a signal comparison result by comparing the calculated value with a signal threshold, wherein the signal threshold includes an upper limit threshold, a lower limit threshold, and a mean threshold, and the signal comparison result includes multiple sub-results, a first sub-result representing the comparison result between the upper limit and the upper limit threshold, a second sub-result representing the comparison result between the lower limit and the lower limit threshold, a third sub-result representing the comparison result between the mean signal and the mean threshold; and determining that the first detection result represents an abnormal network connection signal when there is a sub-result in the signal comparison result representing a calculated value lower than the signal threshold.

[0069] According to embodiments of this disclosure, multiple signal strength values ​​of a network connection signal are collected within a detection time interval, and based on the multiple signal strength values, an upper limit, a lower limit, and a mean signal value of the network connection signal within the detection time interval are determined. The upper limit is the maximum value among the multiple signal strength values, the lower limit is the minimum value among the multiple signal strength values, and the mean signal value is determined based on the multiple signal strength values ​​and the number of multiple signal strength values.

[0070] According to embodiments of this disclosure, the upper limit of the signal is compared with an upper limit threshold to determine a first sub-result; the lower limit of the signal is compared with a lower limit threshold to determine a second sub-result; and the average value of the signal is compared with an average threshold to determine a third sub-result. If any of the first, second, or third sub-results indicates a calculated value lower than the signal threshold, the first detection result is determined to indicate an abnormal connection signal. If all three sub-results indicate a calculated value higher than the signal threshold, the first detection result is determined to indicate a normal connection signal.

[0071] According to embodiments of this disclosure, by collecting multiple signal strength values ​​of network connection signals within a detection time interval, the calculated value of the network connection signal is determined, and the multiple calculated values ​​are compared with the corresponding signal thresholds to determine the signal comparison results, thereby determining whether there is an anomaly in the network connection signal. This increases the causes of network fault detection and improves detection efficiency and accuracy.

[0072] According to embodiments of this disclosure, a third detection result is determined by comparing the hardware configuration information of IoT hardware with the file configuration information set in the network configuration file. This includes: determining the hardware configuration information of the IoT hardware, wherein the hardware configuration information includes the device number of the IoT hardware and the group number of the group to which the IoT hardware belongs; determining the file configuration information set in the configuration file, wherein the file configuration information includes the device numbers of the multiple IoT hardware devices controlled by the network and the group number of the group formed by the multiple IoT hardware devices; comparing the hardware configuration information of the IoT hardware with the file configuration information set in the configuration file to determine the comparison result; and if the comparison result indicates that the file configuration information does not include the device number of the IoT hardware or the group number of the IoT hardware group, determining that the third detection result indicates that the configuration file is incorrect.

[0073] According to embodiments of this disclosure, hardware configuration information is determined based on the hardware attributes of the IoT hardware. The hardware configuration information includes the device number of the IoT hardware and the group number of the group to which the IoT hardware belongs. The group includes multiple IoT hardware devices, and the group number represents the number of the IoT hardware device among the multiple IoT hardware devices in the group.

[0074] According to embodiments of this disclosure, a network-based gateway determines file configuration information set in a configuration file. The configuration file may be a gateway configuration file. The file configuration information includes the device number of each of the multiple IoT hardware devices controlled by the network and the group number of the group formed by the multiple IoT hardware devices. The multiple IoT hardware devices controlled by the network may belong to the same group or different groups.

[0075] According to embodiments of this disclosure, the hardware configuration information of the IoT hardware is compared with the file configuration information set in the configuration file. Specifically, the device number of the IoT hardware is compared with the device number of the network-controlled IoT hardware, and the group number of the group to which the IoT hardware belongs is compared with the group number of the group formed by the network-controlled IoT hardware, thereby determining the comparison result.

[0076] According to embodiments of this disclosure, if the device number of the IoT hardware or the group number of the IoT hardware group is not included in the configuration information of the comparison result characterization file, it indicates that the multiple IoT hardware controlled by the network does not include the IoT hardware. Therefore, the third detection result can be used to characterize that the configuration file of the gateway is set incorrectly.

[0077] According to embodiments of this disclosure, the hardware configuration information of the IoT hardware is determined, and the file configuration information of the gateway is determined. By comparing the hardware configuration information and the file configuration information, it is determined whether the IoT hardware is correctly configured in the gateway's configuration file, thereby determining whether the configuration file is incorrect, and further improving the accuracy of network fault detection.

[0078] According to embodiments of this disclosure, a second detection result is determined based on the network's connectivity status and signal strength value at a re-detection time, including: determining the network's connectivity status and signal strength value at the re-detection time; and determining that the second detection result indicates an abnormal network connectivity process when the connectivity status indicates a network anomaly and the signal strength value indicates a normal signal strength.

[0079] According to embodiments of this disclosure, the network connectivity and signal strength values ​​can be determined at the re-detection time by means of methods such as pinging a cloud server.

[0080] According to embodiments of this disclosure, when the connection status indicates a network anomaly and the signal strength value indicates a normal signal strength, it can be determined that the network signal strength is normal, but the network has a fault. Therefore, it can be determined that the second detection result is used to characterize the network connection process anomaly. In particular, when determining the network connection status by pinging the cloud server, if no response is received from the cloud server, it can be determined that the connection status indicates a network anomaly.

[0081] According to embodiments of this disclosure, the network connection status and signal strength value are determined at the re-detection time. The network connection status determines whether the network is normal, and the signal strength value determines whether the signal strength is normal. In the case of network abnormality but normal signal strength, the network connection procedure is determined to be abnormal. Based on the principle of network connection, the network connection procedure status can be determined by elimination method, thereby improving the accuracy and efficiency of network fault detection.

[0082] According to embodiments of this disclosure, determining network fault detection results based on first detection results, second detection results, third detection results, and fourth detection results includes: determining fault type and fault location in the network based on first detection results, second detection results, third detection results, and fourth detection results; and determining network fault detection results based on fault type and fault cause.

[0083] According to embodiments of this disclosure, based on a first detection result, a second detection result, a third detection result, and a fourth detection result, the fault type and fault location in the network are determined. The fault location in the network includes the location where the network fault occurs, such as the physical location of a network connection fault, the physical location of a network antenna fault, etc. Based on the fault type and fault cause, the network fault detection result can be determined.

[0084] According to embodiments of this disclosure, after determining the network fault detection results, an alarm can be sent to the IoT hardware administrator. The alarm includes the fault type and fault cause, so that the IoT hardware administrator can conduct further troubleshooting and repair based on the fault type and fault cause.

[0085] According to embodiments of this disclosure, network fault detection results are determined based on first detection results, second detection results, third detection results, and fourth detection results, thereby ensuring that the fault detection results include more comprehensive network faults and improving the accuracy of network fault detection.

[0086] Figure 3 A flowchart illustrating a network fault detection method according to another embodiment of the present disclosure is shown.

[0087] like Figure 3 As shown, the network fault detection method of this embodiment includes operations S301 to S311.

[0088] In operation S301, determine if the network log file indicates a network fault, or determine if a preset detection cycle has been reached, triggering network fault detection. In operation S302, determine the time of the fault and the signal strength value of the network connection signal at that time. In operation S303, determine the first detection result based on the signal strength value. In operation S304, based on the first detection result, determine if the signal strength value is normal; if the signal strength value is normal, execute operation S305. In operation S305, based on the time of the fault, determine the re-detection time and determine the network connection status and signal strength value of the network connection signal at the re-detection time. In operation S306, based on the network connection status and signal strength value at the re-detection time, determine the second detection result. In operation S307, determine if the hardware configuration information of the IoT hardware matches the file configuration information of the gateway configuration file. In operation S308, determine the third detection result. In operation S309, determine the data records in the interface log file. In operation S310, based on the interaction type of the data records, determine the fourth detection result. In operation S311, the fault detection results of the network are determined based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0089] According to embodiments of this disclosure, the network fault detection method further includes: determining network repair methods based on the network fault type; determining network repair targets based on network fault location; determining network repair schemes based on the repair methods and repair targets; and repairing the network based on the repair schemes.

[0090] According to embodiments of this disclosure, the repair methods for the network are determined based on the type of network fault. For example, if the fault type is a network connection program fault, the repair methods may be debugging the connection program or restarting the connection program. If the fault is a network physical connection fault, the repair methods may be reconnecting or strengthening the physical connection.

[0091] According to embodiments of this disclosure, a network repair target is determined based on network fault location. For example, if the fault location is the physical location where the network antenna fault occurs, the repair target is the network antenna at that physical location.

[0092] According to embodiments of this disclosure, a network repair scheme is determined based on repair methods and repair targets, and the network is repaired based on the repair scheme, wherein the repair scheme includes repairing the repair targets using repair methods.

[0093] According to embodiments of this disclosure, based on the network fault type and fault location, the network repair methods and repair targets are determined respectively, thereby determining the network repair plan. Based on the repair plan, the repair methods are used to accurately repair the network repair targets, thereby improving the efficiency of network fault detection and network repair, and improving network stability.

[0094] Based on the above-described network fault detection method, this disclosure also provides a network fault detection device. The following will be combined with... Figure 4 The device is described in detail.

[0095] Figure 4 A schematic block diagram of a network fault detection device according to an embodiment of the present disclosure is shown.

[0096] like Figure 4 As shown, the network fault detection device 400 of this embodiment includes a fault determination module 410, a first detection module 420, a time determination module 430, a second detection module 440, a third detection module 450, a fourth detection module 460, and a result determination module 470.

[0097] The fault determination module 410 is used to determine the time of the network failure in response to the network log file indicating a network failure. In one embodiment, the fault determination module 410 can be used to perform the operation S210 described above, which will not be repeated here.

[0098] The first detection module 420 is used to determine a first detection result based on the signal strength value of the network connection signal. In one embodiment, the first detection module 420 can be used to perform the operation S220 described above, which will not be repeated here.

[0099] The timing determination module 430 is used to determine the re-detection time based on the fault time and the detection time interval when the first detection result indicates that the network connection signal is normal. In one embodiment, the timing determination module 430 can be used to perform the operation S230 described above, which will not be repeated here.

[0100] The second detection module 440 is used to determine the second detection result based on the network's connectivity and signal strength value at the re-detection time. In one embodiment, the second detection module 440 can be used to perform the operation S240 described above, which will not be repeated here.

[0101] The third detection module 450 is used to compare the hardware configuration information of the IoT hardware with the file configuration information set in the network configuration file to determine the third detection result. In one embodiment, the third detection module 450 can be used to perform the operation S250 described above, which will not be repeated here.

[0102] The fourth detection module 460 is used to determine the fourth detection result based on data recording in the interface log file of the network communication interface. In one embodiment, the fourth detection module 460 can be used to perform the operation S260 described above, which will not be repeated here.

[0103] The result determination module 470 is used to determine the network fault detection result based on the first detection result, the second detection result, the third detection result, and the fourth detection result. In one embodiment, the result determination module 470 can be used to perform the operation S270 described above, which will not be repeated here.

[0104] According to embodiments of this disclosure, the fourth detection module 460 includes a record parsing submodule and a fourth anomaly determination submodule.

[0105] The record parsing submodule is used to parse multiple data records in the interface log file and determine the interaction type of each data record. The interaction type includes sending data and reading data.

[0106] The fourth anomaly determination submodule is used to determine the fourth detection result to characterize network interface communication anomalies when multiple interaction types corresponding to multiple data records do not include reading data.

[0107] According to embodiments of this disclosure, the first detection module 420 includes an intensity value determination submodule, a calculated value determination submodule, a first comparison result determination module, and a first anomaly determination submodule.

[0108] The intensity value determination submodule is used to collect the signal strength value of the network connection signal within the detection time interval.

[0109] The calculated value determination submodule is used to determine the calculated value of the network connection signal within the detection time interval based on the signal strength values ​​collected within the detection time interval. The calculated value includes the upper limit of the signal, the lower limit of the signal, and the average signal value.

[0110] The first comparison result determination module is used to compare the signal threshold with the calculated value to determine the signal comparison result. The signal threshold includes an upper limit threshold, a lower limit threshold, and a mean threshold. The signal comparison result includes multiple sub-results. The first sub-result is used to characterize the comparison result between the upper limit of the signal and the upper limit threshold. The second sub-result is used to characterize the comparison result between the lower limit of the signal and the lower limit threshold. The third sub-result is used to characterize the comparison result between the mean of the signal and the mean threshold.

[0111] The first anomaly determination submodule is used to determine that the first detection result represents an anomaly in the network connection signal when there is a sub-result in the signal comparison result where the calculated value is lower than the signal threshold.

[0112] According to embodiments of this disclosure, the third detection module 450 includes a hardware determination submodule, a file determination submodule, a second comparison result determination submodule, and a third anomaly determination submodule.

[0113] The hardware determination submodule is used to determine the hardware configuration information of the IoT hardware, which includes the device number of the IoT hardware and the group number of the group to which the IoT hardware belongs.

[0114] The file determination submodule is used to determine the file configuration information set in the configuration file. The file configuration information includes the device number of each of the multiple IoT hardware devices controlled by the network and the group number of the group formed by the multiple IoT hardware devices.

[0115] The second comparison result determination submodule is used to compare the hardware configuration information of the IoT hardware with the file configuration information set in the configuration file to determine the comparison result.

[0116] The third anomaly determination submodule is used to determine that the third detection result characterization configuration file is incorrect if the device number of the IoT hardware or the group number of the IoT hardware group is not included in the configuration information of the comparison result characterization file.

[0117] According to an embodiment of this disclosure, the second detection module 440 includes a connection determination submodule and a second anomaly determination submodule.

[0118] The connection determination submodule is used to determine the network connectivity and signal strength values ​​during re-detection.

[0119] The second anomaly determination submodule is used to determine, when the connection status indicates a network anomaly and the signal strength value indicates a normal signal strength, that the second detection result indicates a network connection procedure anomaly.

[0120] According to embodiments of this disclosure, the result determination module 470 includes a fault determination submodule and a result determination submodule.

[0121] The fault determination submodule is used to determine the fault type and fault location in the network based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

[0122] The result determination submodule is used to determine the network fault detection results based on the fault type and fault cause.

[0123] According to embodiments of this disclosure, the network fault detection device 400 further includes a means determination module, a target determination module, a scheme determination module, and a network repair module.

[0124] The method determination module is used to determine the repair methods for the network based on the type of network fault.

[0125] The target determination module is used for network-based fault location to determine the network repair targets.

[0126] The solution determination module is used to determine the network repair solution based on the repair methods and repair objectives.

[0127] The network repair module is used to repair the network based on the repair plan.

[0128] According to embodiments of this disclosure, any plurality of modules among the fault determination module 410, the first detection module 420, the timing determination module 430, the second detection module 440, the third detection module 450, the fourth detection module 460, and the result determination module 470 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the fault determination module 410, the first detection module 420, the timing determination module 430, the second detection module 440, the third detection module 450, the fourth detection module 460, and the result determination module 470 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the fault determination module 410, the first detection module 420, the time determination module 430, the second detection module 440, the third detection module 450, the fourth detection module 460, and the result determination module 470 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0129] Figure 5 A block diagram of an electronic device suitable for implementing a network fault detection method according to an embodiment of the present disclosure is shown schematically.

[0130] like Figure 5As shown, an electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage portion 508 into a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0131] RAM 503 stores various programs and data required for the operation of electronic device 500. Processor 501, ROM 502, and RAM 503 are interconnected via bus 504. Processor 501 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 502 and / or RAM 503. It should be noted that the programs may also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0132] According to embodiments of this disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to a bus 504. The electronic device 500 may also include one or more of the following components connected to the input / output (I / O) interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the input / output (I / O) interface 505 as needed. A removable medium 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 510 as needed so that computer programs read from it can be installed into the storage section 508 as needed.

[0133] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0134] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 502 and / or RAM 503 and / or one or more memories other than ROM 502 and RAM 503 described above.

[0135] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0136] When the computer program is executed by the processor 501, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0137] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 509, and / or installed from a removable medium 511. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0138] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by processor 501, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0139] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0140] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0141] Those skilled in the art will understand that the features described in the various embodiments of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0142] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A network fault detection method, characterized in that, The method includes: In response to the network log file indicating a network failure, the timing of the network failure is determined. The first detection result is determined based on the signal strength value of the network connection signal. If the first detection result indicates that the network connection signal is normal, the re-detection time is determined based on the fault time and the detection time interval; The second detection result is determined based on the network's connectivity and signal strength at the re-detection time. The third detection result is determined by comparing the hardware configuration information of the IoT hardware with the file configuration information set in the network's configuration file. The fourth detection result is determined based on data records in the interface log file of the network communication interface; and Based on the first detection result, the second detection result, the third detection result, and the fourth detection result, the fault detection result of the network is determined.

2. The method according to claim 1, characterized in that, The data records in the interface log file based on the network communication interface are used to determine the fourth detection result, including: Parse multiple data records in the interface log file to determine the interaction type of each data record, wherein the interaction type includes sending data and reading data; and If the read data is not included in the multiple interaction types corresponding to the multiple data records, the fourth detection result is determined to indicate that the network interface communication is abnormal.

3. The method according to claim 1, characterized in that, The determination of the first detection result based on the signal strength value of the network connection signal includes: The signal strength value of the network connection signal is collected within the detection time interval; Based on the signal strength values ​​collected within the detection time interval, the calculated value of the network connection signal within the detection time interval is determined, wherein the calculated value includes the upper limit of the signal, the lower limit of the signal, and the average signal value; A signal comparison result is determined by comparing the signal threshold with the calculated value. The signal threshold includes an upper limit threshold, a lower limit threshold, and a mean threshold. The signal comparison result includes multiple sub-results: a first sub-result characterizes the comparison result between the upper limit and the upper limit threshold; a second sub-result characterizes the comparison result between the lower limit and the lower limit threshold; and a third sub-result characterizes the comparison result between the mean and the mean threshold. If there is a sub-result in the signal comparison results that indicates that the calculated value is lower than the signal threshold, the first detection result is determined to indicate that the network connection signal is abnormal.

4. The method according to claim 1, characterized in that, The comparison of the hardware configuration information of the IoT hardware with the file configuration information set in the network's configuration file to determine the third detection result includes: Determine the hardware configuration information of the IoT hardware, wherein the hardware configuration information includes the device number of the IoT hardware and the group number of the group to which the IoT hardware belongs; The file configuration information set in the configuration file is determined, wherein the file configuration information includes the device number of each of the multiple IoT hardware devices controlled by the network and the group number of the group formed by the multiple IoT hardware devices; The hardware configuration information of the IoT hardware is compared with the file configuration information set in the configuration file to determine the comparison result; and If the comparison result indicates that the configuration file does not contain the device number of the IoT hardware or the group number of the IoT hardware group, then the third detection result indicates that the configuration file is incorrect.

5. The method according to claim 1, characterized in that, The determination of the second detection result based on the network's connectivity and signal strength at the re-detection time includes: At the re-detection time, the network connectivity and the signal strength value are determined; and If the connection status indicates a network anomaly, and the signal strength value indicates a normal signal strength, then the second detection result indicates a network connection procedure anomaly.

6. The method according to any one of claims 1 to 5, characterized in that, Determining the network fault detection result based on the first detection result, the second detection result, the third detection result, and the fourth detection result includes: Based on the first detection result, the second detection result, the third detection result, and the fourth detection result, the fault type and fault location in the network are determined; and Based on the fault type and the fault cause, the fault detection result of the network is determined.

7. The method according to claim 6, characterized in that, The method further includes: Based on the fault type of the network, determine the repair methods for the network; Based on the fault location of the network, the repair target of the network is determined; Based on the aforementioned repair methods and repair objectives, a repair scheme for the network is determined; and The network is repaired based on the aforementioned repair scheme.

8. A network fault detection device, characterized in that, The device includes: The fault determination module is used to determine the time of the network failure in response to the network log file indicating that the network has failed. The first detection module is used to determine the first detection result based on the signal strength value of the network connection signal. The timing determination module is used to determine the re-detection time based on the fault time and the detection time interval when the first detection result indicates that the network connection signal is normal. The second detection module is used to determine the second detection result based on the network's connectivity and signal strength value at the re-detection time. The third detection module is used to compare the hardware configuration information of the IoT hardware with the file configuration information set in the network configuration file to determine the third detection result. The fourth detection module is used to determine the fourth detection result based on data records in the interface log file of the network communication interface; and The result determination module is used to determine the fault detection result of the network based on the first detection result, the second detection result, the third detection result, and the fourth detection result.

9. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images