Fault detection method, device, system, equipment and medium
By sending multiple connectivity detection requests to the boundary equipment and counting the response status, the problem of fast and accurate detection of boundary equipment fault detection is solved, and efficient fault detection and misjudgment are achieved.
Patent Information
- Application Number
- CN202311798754.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-25
- Publication Date
- 2025-06-27
AI Technical Summary
How to quickly and accurately detect whether a boundary device has failed, especially when the boundary device communicates with external devices.
By sending at least two connectivity detection requests to the boundary device, carrying the identification of different target external devices, counting the proportion of target external devices in the connected state, and determining whether the boundary device has a failure based on the set threshold.
It realizes rapid and accurate detection of boundary equipment failures, minimizes misjudgments, and ensures the accuracy and safety of detection results.
Smart Images
Figure CN120223577A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of fault detection, and in particular, to a fault detection method, device, system, equipment and medium. Background Art
[0002] A typical information system consists of boundary devices (also known as boundary systems) and service devices (also known as service systems). The information system is usually deployed in the internal network area (hereinafter referred to as the intranet for short); external devices (also known as external systems), as the users of the information system, are usually deployed in the external network area (hereinafter referred to as the extranet for short).
[0003] As the communication hub between external devices and service devices, the boundary device is responsible for forwarding service requests between service devices and external network devices, and is an important link in the communication link of the information system. If the boundary device fails, even if the service device and the external device are both operating normally, the service device and the external device cannot communicate. Therefore, it is very necessary to monitor the health status of the boundary device so that operation and maintenance can be promptly handled when the boundary device fails. Among them, how to quickly and accurately detect whether the boundary device has failed is a technical problem that needs to be solved urgently at present. Summary of the Invention
[0004] This application provides a fault detection method, device, system, equipment and medium for quickly and accurately detecting whether the boundary device has failed.
[0005] In a first aspect, this application provides a fault detection method, which is applied to a health detection device. The method includes:
[0006] Sending at least two connectivity detection requests to the boundary device, where the target external device identifiers carried in at least two connectivity detection requests are different from each other, so that when the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request, and when each target external device receives any connectivity detection request, it feeds back response information to the boundary device, and when the boundary device receives the response information fed back by any target external device, it sends the response information to the health detection device;
[0007] For any target external device, based on the response information feedback data of the target external device, determining whether the target external device is in a connected state;
[0008] Counting the first proportion of the target external devices in a connected state among all target external devices, and determining whether the boundary device has failed according to the first proportion and a first set proportion threshold.
[0009] In a possible implementation, determining whether the boundary device has a fault according to the first proportion and the first set proportion threshold includes:
[0010] If the first proportion is not less than the first set proportion threshold, it is determined that the boundary device has no fault;
[0011] If the first proportion is less than the first set proportion threshold, it is determined that the boundary device has a fault.
[0012] In a possible implementation, determining whether the target external device is in a connected state based on the response information feedback data of the target external device includes:
[0013] Count the second proportion of the number of times the target external device feeds back response information in the total number of connectivity detection requests carrying the identifier of the target external device, and determine whether the target external device is in a connected state according to the second proportion and the second set proportion threshold.
[0014] In a possible implementation, determining whether the target external device is in a connected state according to the second proportion and the second set proportion threshold includes:
[0015] If the second proportion is not less than the second set proportion threshold, it is determined that the target external device is in a connected state;
[0016] If the second proportion is less than the second set proportion threshold, it is determined that the target external device is in a disconnected state.
[0017] In a possible implementation, after sending at least two connectivity detection requests to the boundary device and before determining whether the target external device is in a connected state based on the response information feedback data of the target external device for any target external device, the method further includes:
[0018] For any connectivity detection request carrying the identifier of any target external device sent to the boundary device, if the response information carrying the identifier of the target external device forwarded by the boundary device is received within the set time period, it is determined that the target external device has fed back response information for this connectivity detection request; if the response information carrying the identifier of the target external device forwarded by the boundary device is not received within the set time period, it is determined that the target external device has not fed back response information for this connectivity detection request.
[0019] In a possible implementation, the health detection device is configured in the internal network, and the internal network includes a network area not connected to the Internet.
[0020] In a possible implementation, before sending at least two connectivity detection requests to the boundary device, the method further includes:
[0021] Obtain the operation metrics of multiple candidate external devices, and select each of the target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
[0022] In a second aspect, the present application provides a fault detection device, and the device includes:
[0023] A sending module, configured to send at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in at least two connectivity detection requests are different from each other, so that when the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request, and so that when each target external device receives any connectivity detection request, it feeds back response information to the boundary device, and so that when the boundary device receives the response information fed back by any target external device, it sends the response information to a health detection device;
[0024] A judgment module, configured to, for any target external device, judge whether the target external device is in a connected state based on the response information feedback data of the target external device;
[0025] A detection module, configured to count the first proportion of the target external devices in a connected state among all target external devices, and judge whether the boundary device has a fault according to the first proportion and a first set proportion threshold.
[0026] In a possible implementation, the detection module is specifically configured to:
[0027] If the first proportion is not less than the first set proportion threshold, it is determined that the boundary device has no fault;
[0028] If the first proportion is less than the first set proportion threshold, it is determined that the boundary device has a fault.
[0029] In a possible implementation, the judgment module is specifically configured to:
[0030] Count the second proportion of the number of times the target external device feeds back response information in the total number of connectivity detection requests carrying the target external device identifier, and judge whether the target external device is in a connected state according to the second proportion and a second set proportion threshold.
[0031] In a possible implementation, the judgment module is specifically configured to:
[0032] If the second ratio is not less than the second set ratio threshold, it is determined that the target external device is in a connected state;
[0033] If the second ratio is less than the second set ratio threshold, it is determined that the target external device is in a disconnected state.
[0034] In a possible implementation manner, the determination module is further configured to:
[0035] For any connectivity detection request carrying any target external device identifier sent to the boundary device, if the response information carrying the target external device identifier forwarded by the boundary device is received within the set duration, it is determined that the target external device has fed back the response information for the connectivity detection request; if the response information carrying the target external device identifier forwarded by the boundary device is not received within the set duration, it is determined that the target external device has not fed back the response information for the connectivity detection request.
[0036] In a possible implementation manner, the health detection device is configured in the internal network, and the internal network includes a network area not connected to the Internet.
[0037] In a possible implementation manner, the sending module is further configured to:
[0038] Obtain the operation metrics of multiple candidate external devices, and select the target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
[0039] In a third aspect, the present application provides a fault detection system, and the system includes:
[0040] A health detection device, configured to send at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other;
[0041] The boundary device is configured to, for each received connectivity detection request, send the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request;
[0042] Each target external device is configured to, if any connectivity detection request is received, feed back response information to the boundary device;
[0043] The boundary device is further configured to, if the response information fed back by any target external device is received, send the response information to the health detection device;
[0044] The health detection device is further configured to, for any target external device, determine whether the target external device is in a connected state based on the response information feedback data of the target external device; count a first proportion of the target external devices in a connected state among all target external devices, and determine whether the boundary device has a fault according to the first proportion and a first set proportion threshold.
[0045] In a fourth aspect, the present application provides an electronic device, which at least includes a processor and a memory. When the processor executes a computer program stored in the memory, the steps of the method according to any one of the first aspects are implemented.
[0046] In a fifth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method according to any one of the first aspects are implemented.
[0047] Since the health detection device of the present application can send connectivity detection requests to multiple target external devices through the boundary device, it can determine whether the boundary device responsible for forwarding information (connectivity detection requests) has a fault based on the feedback response information of the multiple target external devices, which can maximally eliminate misjudgments such as misjudging that the boundary device fails to forward information due to a fault of an individual external device that cannot feedback response information, and can maximally ensure the purpose of quickly and accurately detecting whether the boundary device has a fault. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] In order to more clearly illustrate the embodiments of the present application or the implementation manners in the related art, the following will briefly introduce the drawings required for use in the description of the embodiments or the related art. Obviously, the following drawings are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings.
[0049] Figure 1 FIG. 1 shows a schematic diagram of a first fault detection process provided by some embodiments of the present application;
[0050] Figure 2 FIG. 2 shows a schematic diagram of a second fault detection process provided by some embodiments of the present application;
[0051] Figure 3 FIG. 3 shows a schematic diagram of a third fault detection process provided by some embodiments of the present application;
[0052] Figure 4 FIG. 4 shows a schematic diagram of a fault detection device provided by some embodiments of the present application;
[0053] Figure 5Shows a schematic diagram of a fault detection system provided by some embodiments of the present application;
[0054] Figure 6 Shows a schematic diagram of the structure of an electronic device provided by some embodiments of the present application. Detailed implementation manners
[0055] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. Obviously, the embodiments described in the present application are only some of the embodiments of the present application, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.
[0056] It should be noted that the brief description of the terms in the present application is only for facilitating the understanding of the subsequent described embodiments, rather than intending to limit the embodiments of the present application. Unless otherwise specified, these terms should be understood in their ordinary and general meanings.
[0057] The terms "first", "second", "third", etc. in the specification, claims and the above-mentioned drawings of the present application are used to distinguish similar or like objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that such terms can be interchanged under appropriate circumstances.
[0058] The terms "comprising" and "having" and any variations thereof are intended to cover but not exclude inclusion. For example, a product or device comprising a series of components does not necessarily have to be limited to all the components clearly listed, but may include other components not clearly listed or inherent to these products or devices.
[0059] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic or a combination of hardware or / and software code that can perform functions related to that element.
[0060] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.
[0061] In order to quickly and accurately detect whether a boundary device has a fault, the present application provides a fault detection method, device, system, equipment and medium.
[0062] The preferred embodiments of the present application will be described below in conjunction with the accompanying drawings of the specification. It should be understood that the preferred embodiments described herein are only for explaining and illustrating the present application, and are not used to limit the present application. And without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.
[0063] Embodiment 1:
[0064] Figure 1 FIG. 1 shows a schematic diagram of the first fault detection process provided by some embodiments of the present application. As Figure 1 shown, the process includes the following steps:
[0065] S101: Send at least two connectivity detection requests to the boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other. When the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request. And when each target external device receives any one of the connectivity detection requests, it feeds back response information to the boundary device. And when the boundary device receives the response information fed back by any one of the target external devices, it sends the response information to the health detection device.
[0066] The fault detection method provided by the embodiments of the present application is applied to a health detection device. Among them, the health detection device can be an electronic device such as a PC or a mobile terminal, or an electronic device such as a server.
[0067] In a possible implementation manner, in order to quickly and accurately detect whether the boundary device fails, for any statistical period (detection period), the health detection device can send at least two (multiple) connectivity detection requests to the boundary device. For example, the health detection device can send multiple connectivity detection requests to the boundary device simultaneously in parallel, or can send multiple connectivity detection requests to the boundary device separately one after another. The present application does not make specific limitations on the specific manner of sending the connectivity detection requests.
[0068] Each connectivity detection request sent by the health detection device to the boundary device can carry a target external device identifier respectively. For each connectivity detection request, when the boundary device receives the connectivity detection request, it can identify the target external device identifier carried in the connectivity detection request, and according to the target external device identifier, send the connectivity detection request to the target external device corresponding to the target external device identifier.
[0069] Among them, in order to accurately detect whether a boundary device fails, in the embodiment of this application, the health detection device can send connectivity detection requests to multiple target external devices through the boundary device, and based on the situation of the multiple target external devices feedbacking response information, accurately determine whether the boundary device responsible for forwarding the connectivity detection request fails. Specifically, in order to send connectivity detection requests to multiple target external devices, among the multiple connectivity detection requests sent by the health detection device to the boundary device, at least two of the connectivity detection requests carry different target external device identifiers, so as to ensure that connectivity detection requests can be sent to multiple (at least two) target external devices through the boundary device.
[0070] Optionally, considering that the intranet usually refers to an internal local area network, which is generally used for communication between computers (devices) within the local area network and does not communicate with the external network, that is, the intranet is usually a network area not connected to the Internet, while the extranet is usually a network area connected to the Internet. The security of the intranet environment is usually higher than that of the extranet environment. If the health detection device is configured in the extranet environment, the health detection device may be subject to security attacks, affecting the accuracy of the fault detection result of the boundary device. In order to safely and accurately detect whether the boundary device fails, the health detection device can be configured (deployed) in the intranet (internal network area) like the boundary device. That is to say, this application can deploy the health detection device in the intranet with higher security, and the health detection device located in the intranet actively initiates a connectivity detection request for the boundary device to detect the fault (health status) of the boundary device, which can maximize the accuracy of the detection result and the security and controllability of the entire detection process.
[0071] In a possible implementation manner, for each target external device, when the target external device receives the connectivity detection request sent by the boundary device, it can feedback a response information to the boundary device. Optionally, the response information can carry the identifier of the target external device (target external device identifier). Among them, this application does not specifically limit the target external device identifier, and it can be flexibly set according to requirements. When the boundary device receives the response information feedback by any target external device, it can send the response information to the health detection device.
[0072] Optionally, the health detection device and the service device (service system) can be two independent devices (also referred to as systems), or can be integrated into one device (system). This application does not make specific limitations on this, and can be flexibly set according to requirements. The connectivity detection request sent by the health detection device to the boundary device can be a lightweight network connectivity test request or a service connectivity test request. The process of the boundary device receiving the connectivity detection request and forwarding it to the external device is similar to the process in the related art where the boundary device receives service request information sent by the service device and forwards the information to the external device. It does not involve changes to the business logic of the boundary device, does not involve additional development support for the boundary device or the external device, has low intrusion on the boundary device and the external device, and can quickly, accurately, and at low cost detect whether the boundary device has failed.
[0073] S102: For any target external device, based on the response information feedback data, determine whether the target external device is in a connected state.
[0074] In a possible implementation manner, for each target external device, the health detection device can count the feedback situation of the target external device to the response information to obtain the response information feedback data. Exemplarily, for each target external device, it can be counted how many connectivity detection requests have been sent to the target external device through the boundary device during the current detection period (that is, count the total number of connectivity detection requests carrying the identifier of the target external device), and it can also be counted which of the connectivity detection requests the target external device has feedback response information to, the number of times the target external device has feedback response information, etc. Based on these response information feedback data of the target external device, it can be determined whether the target external device is in a connected state.
[0075] Optionally, to improve efficiency, when determining whether to receive the response information feedback by a certain target external device, for each connectivity detection request carrying the identifier of the target external device (target external device identifier), after the health detection device sends the connectivity detection request to the boundary device, it is determined whether the response information carrying the identifier of the target external device forwarded by the boundary device is received within the set time period. If received, it can be considered (determined) that the target external device has feedback the response information to the connectivity detection request. Otherwise, if the response information carrying the identifier of the target external device forwarded by the boundary device is not received within the set time period, it can be determined that the target external device has not feedback the response information to the connectivity detection request.
[0076] Optionally, when the health detection device determines whether the target external device is in a connected state based on the response information feedback data of the target external device, for each target external device, it can calculate (count) the proportion of the number of times the target external device feedbacks response information in the total number of connectivity detection requests sent to the target external device through the boundary device (that is, the total number of connectivity detection requests carrying the identifier of the target external device) (for convenience of description, referred to as the second proportion). It can determine whether the target external device is in a connected state according to the size relationship between the second proportion and the second set proportion threshold. For example, for each target external device, when the second proportion corresponding to the target external device is not less than (greater than or equal to) the second proportion threshold, it is considered that the target external device is in a connected state. On the contrary, when the second proportion corresponding to the target external device is less than the second proportion threshold, it is considered that the target external device is in a disconnected state (not in a connected state). Among them, the second proportion threshold can be 100%, or a positive number less than 100%, etc. The confidence level of whether the target external device is in a connected state can be adjusted accordingly by adjusting the second proportion threshold. For example, the larger the second proportion threshold, the higher the confidence level of the judgment result of whether the target external device is in a connected state, and thus the higher the confidence level of the judgment result of whether the boundary device fails. This application does not make specific limitations on this and can be flexibly set according to requirements.
[0077] S103: Statistically calculate the first proportion of the target external devices in a connected state among all target external devices, and determine whether the boundary device fails according to the first proportion and the first set proportion threshold.
[0078] In a possible implementation manner, the number of target external devices in a connected state can be statistically calculated (for convenience of description, referred to as the first number), and the total number of target external devices for which the health detection device has sent connectivity detection requests through the boundary device can be statistically calculated. For example, after fusing and de-duplicating the target external device identifiers carried in each connectivity detection request, the total number of target external devices for which the health detection device has sent connectivity detection requests through the boundary device can be obtained (for convenience of description, referred to as the second number). Optionally, the proportion of the number of target external devices in a connected state among all target external devices can be statistically calculated (for convenience of description, referred to as the first proportion). That is to say, the ratio of the first number to the second number can be determined as the first proportion.
[0079] Optionally, it is possible to determine whether the boundary device has a fault based on the magnitude relationship between the first proportion and the first set proportion threshold. For example, when the first proportion is not less than the first set proportion threshold, it can be considered that most or even all of the target external devices are in a connected state. At this time, it can be considered (determined) that the boundary device can forward information normally and the boundary device has no fault. Even if there are individual target external devices that are not in a connected state (in a disconnected state), it can be considered that these individual target external devices have their own faults that cause them to be in a disconnected state.
[0080] If the first proportion is less than the first set proportion threshold, it can be considered that most or even all of the target external devices are in a disconnected state. At this time, it can be considered that it is very likely that the boundary device has a fault and fails to forward the connectivity detection request normally, resulting in most or even all of the target external devices being in a disconnected state. At this time, the boundary device can be determined to have a fault. Among them, the first proportion threshold can be 100%, or a positive number less than 100%, etc. The confidence level of whether the target external device is in a connected state can be adjusted accordingly by adjusting the first proportion threshold. For example, the larger the first proportion threshold, the higher the confidence level of the judgment result of whether the boundary device has a fault. This application does not make specific limitations on this and can be flexibly set according to requirements.
[0081] Since the health detection device of this application can send connectivity detection requests to multiple target external devices through the boundary device, it is possible to determine whether the boundary device responsible for forwarding information (connectivity detection requests) has a fault based on the situation of the feedback response information of multiple target external devices, which can maximize the exclusion of misjudgment situations such as actually misjudging that the boundary device fails to forward information due to a fault of an individual external device that cannot feedback response information, and can maximize the purpose of quickly and accurately detecting whether the boundary device has a fault.
[0082] Embodiment 2:
[0083] In order to accurately detect whether the boundary device has a fault, based on the above embodiment, in the embodiment of this application, before sending at least two connectivity detection requests to the boundary device, the method further includes:
[0084] Obtain the operation metrics of multiple candidate external devices, and select the respective target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
[0085] In a possible implementation manner, in order to improve the accuracy of the judgment result (detection result) on whether a boundary device fails, an external device with relatively high operation quality can be selected as the detection object (target external device). Specifically, when selecting the target external device, the operation indexes such as the service processing volume, service processing success rate, and processing time consumption of multiple candidate external devices can be obtained first, and then it is judged whether the operation indexes of each candidate external device meet the set index requirements, and each target external device is selected from the candidate external devices whose operation indexes meet the set index requirements.
[0086] For ease of understanding, the following uses a specific embodiment to explain the fault detection process provided by this application. Refer to Figure 2 , Figure 2 FIG. shows a schematic diagram of a second fault detection process provided by some embodiments of this application, and this process includes the following steps:
[0087] A health detection device (health detection system) located in the internal network sends multiple connectivity detection requests (referred to as detection request initiation in the figure) to a boundary device (boundary system). For example, it sends connectivity detection requests carrying the identifiers of external device 1 (external system 1), connectivity detection requests carrying the identifiers of external device 2 (external system 2), connectivity detection requests carrying the identifiers of external device 3 (external system 3),..., multiple connectivity detection requests carrying the identifiers of external device n (external system n). When the boundary device receives each connectivity detection request, for each connectivity detection request, it can send (forward) the connectivity detection request to the corresponding target external device (referred to as detection request forwarding in the figure), such as forwarding the connectivity detection requests to external system 1, external system 2,..., external system n in the figure respectively. When each target external device receives the connectivity detection request, it feeds back response information (not shown in the figure) to the boundary device, and the response information carries the identifier of the corresponding target external device. When the boundary device receives the response information fed back by any target external device, it sends the response information to the health detection device. For any target external device, a decision module (referred to as a health decision system in the figure) in the health detection device can count detection data such as the time of sending the connectivity detection request (detection time), the identifier of the target external device carried in the connectivity detection request, and whether it has received the response information of each target external device, and persistently store the detection data (detection result) at a set location (detection data storage). The decision module in the health detection device can, for each target external device, based on the response information feedback data of the target external device, determine whether the target external device is in a connected state, and can count the first proportion of the target external devices in a connected state among all target external devices. According to the size relationship between the first proportion and the first set proportion threshold, it determines whether the boundary device has a fault (referred to as health status calculation in the figure), and can output the determination result (health status output) to an operation and maintenance disposal device (operation and maintenance disposal system), so as to perform fault disposal in a timely manner when the boundary device has a fault, etc. This application does not make specific limitations on this.
[0088] For ease of understanding, the following uses a specific embodiment to explain the fault detection process provided by this application. Refer to Figure 3 , Figure 3 FIG. shows a schematic diagram of a third fault detection process provided by some embodiments of this application, and this process includes the following steps:
[0089] S301: A health detection device located in the internal network obtains the operation metrics of multiple candidate external devices, and selects each target external device from the candidate external devices whose operation metrics meet the set metric requirements.
[0090] S302: The health detection device located in the internal network sends multiple connectivity detection requests to the boundary device, where the target external device identifiers carried in at least two of the connectivity detection requests are different from each other.
[0091] S303: When the boundary device receives any connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request.
[0092] S304: When each target external device receives any connectivity detection request, it feeds back response information to the boundary device, and the response information carries the identifier of the target external device.
[0093] S305: When the boundary device receives the response information fed back by any target external device, it sends the response information to the health detection device.
[0094] S306: For any target external device, the health detection device determines whether the target external device is in a connected state based on the response information feedback data of the target external device, and counts the first proportion of the target external devices in a connected state among all target external devices. According to the first proportion and the first set proportion threshold, it determines whether the boundary device has a fault.
[0095] Embodiment 3:
[0096] Based on the same technical concept, the present application provides a fault detection device. Refer to Figure 4 , Figure 4 which shows a schematic diagram of a fault detection device provided in some embodiments of the present application. The device includes:
[0097] A sending module 41, configured to send at least two connectivity detection requests to the boundary device, where the target external device identifiers carried in at least two of the connectivity detection requests are different from each other, so that when the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request, and so that when each target external device receives any connectivity detection request, it feeds back response information to the boundary device, and so that when the boundary device receives the response information fed back by any target external device, it sends the response information to the health detection device;
[0098] A judging module 42, configured to determine whether any target external device is in a connected state based on the response information feedback data of the target external device;
[0099] The detection module 43 is used to count the first proportion of the target external devices in the connected state among all target external devices, and determine whether the boundary device has a fault according to the first proportion and the first set proportion threshold.
[0100] In a possible implementation manner, the detection module 43 is specifically configured to:
[0101] If the first proportion is not less than the first set proportion threshold, it is determined that the boundary device has no fault;
[0102] If the first proportion is less than the first set proportion threshold, it is determined that the boundary device has a fault.
[0103] In a possible implementation manner, the judgment module 42 is specifically configured to:
[0104] Count the second proportion of the number of times the target external device feeds back response information in the total number of connectivity detection requests carrying the identifier of the target external device, and determine whether the target external device is in a connected state according to the second proportion and the second set proportion threshold.
[0105] In a possible implementation manner, the judgment module 42 is specifically configured to:
[0106] If the second proportion is not less than the second set proportion threshold, it is determined that the target external device is in a connected state;
[0107] If the second proportion is less than the second set proportion threshold, it is determined that the target external device is in a disconnected state.
[0108] In a possible implementation manner, the judgment module 42 is further configured to:
[0109] For any connectivity detection request carrying the identifier of any target external device sent to the boundary device, if the response information carrying the identifier of the target external device is received from the boundary device within the set time period, it is determined that the target external device has fed back response information for this connectivity detection request; if the response information carrying the identifier of the target external device is not received from the boundary device within the set time period, it is determined that the target external device has not fed back response information for this connectivity detection request.
[0110] In a possible implementation manner, the health detection device is configured in the internal network, and the internal network includes a network area that is not connected to the Internet.
[0111] In a possible implementation manner, the sending module 41 is further configured to:
[0112] Obtain the operation metrics of multiple candidate external devices, and select each of the target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
[0113] Embodiment 4:
[0114] Based on the same technical concept, the present application provides a fault detection system. Refer to Figure 5 , Figure 5 which shows a schematic diagram of a fault detection system provided by some embodiments of the present application. The system includes:
[0115] A health detection device 51, configured to send at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other;
[0116] The boundary device 52 is configured to, for each received connectivity detection request, send the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request;
[0117] Each target external device 53 is configured to, if any connectivity detection request is received, feedback response information to the boundary device;
[0118] The boundary device 52 is further configured to, if response information feedback by any target external device is received, send the response information to the health detection device;
[0119] The health detection device 51 is further configured to, for any target external device, based on the response information feedback data of the target external device, determine whether the target external device is in a connected state; count the first proportion of the target external devices in a connected state among all target external devices, and determine whether the boundary device has a fault according to the first proportion and a first set proportion threshold.
[0120] In a possible implementation manner, the health detection device 51 is specifically configured to:
[0121] If the first proportion is not less than the first set proportion threshold, it is determined that the boundary device has no fault;
[0122] If the first proportion is less than the first set proportion threshold, it is determined that the boundary device has a fault.
[0123] In a possible implementation manner, the health detection device 51 is specifically configured to:
[0124] Calculate the second proportion of the number of times the feedback response information of the target external device is in the total number of connectivity detection requests carrying the identifier of the target external device, and determine whether the target external device is in a connected state according to the second proportion and the second set proportion threshold.
[0125] In a possible implementation manner, the health detection device 51 is specifically configured to:
[0126] If the second proportion is not less than the second set proportion threshold, determine that the target external device is in a connected state;
[0127] If the second proportion is less than the second set proportion threshold, determine that the target external device is in a disconnected state.
[0128] In a possible implementation manner, the health detection device 51 is further configured to:
[0129] For any connectivity detection request carrying the identifier of any target external device sent to the boundary device, if the response information carrying the identifier of the target external device is received from the boundary device within the set time period, it is determined that the target external device has feedback the response information for the connectivity detection request; if the response information carrying the identifier of the target external device is not received from the boundary device within the set time period, it is determined that the target external device has not feedback the response information for the connectivity detection request.
[0130] In a possible implementation manner, the health detection device 51 is configured in the internal network, and the internal network includes a network area that is not connected to the Internet.
[0131] In a possible implementation manner, the health detection device 51 is further configured to:
[0132] Obtain the operation metrics of multiple candidate external devices, and select the target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
[0133] Embodiment 5:
[0134] Based on the same technical concept, the present application also provides an electronic device, Figure 6 shows a schematic structural diagram of an electronic device provided by some embodiments of the present application, as Figure 6 shown, the electronic device includes: a processor 61, a communication interface 62, a memory 63, and a communication bus 64, wherein the processor 61, the communication interface 62, and the memory 63 complete communication with each other through the communication bus 64;
[0135] A computer program is stored in the memory 63. When the program is executed by the processor 61, the processor 61 is caused to execute the steps of the fault detection method described in any of the above embodiments, which will not be elaborated here.
[0136] The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
[0137] The communication interface 62 is used for communication between the above electronic device and other devices.
[0138] The memory may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far from the aforementioned processor.
[0139] The above processor may be a general-purpose processor, including a central processor, a Network Processor (NP), etc.; it may also be a Digital Signal Processing (DSP), an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0140] Embodiment 6:
[0141] Based on the same technical concept, an embodiment of the present application provides a computer-readable storage medium. A computer program executable by an electronic device is stored in the computer-readable storage medium. When the program runs on the electronic device, the electronic device is caused to execute the steps of the fault detection method described in any of the above embodiments, which will not be elaborated here.
[0142] The above computer-readable storage medium may be any available medium or data storage device accessible by the processor in the electronic device, including but not limited to magnetic memories such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc., optical memories such as CDs, DVDs, BDs, HVDs, etc., and semiconductor memories such as ROM, EPROM, EEPROM, Non-Volatile Memory (NANDFLASH), Solid State Drives (SSD), etc.
[0143] Based on the same inventive concept, the present application provides a computer program product, which includes computer program code that, when running on a computer, enables the computer to execute the method described in any of the above-described embodiments of the fault detection method applied to an electronic device.
[0144] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof, and can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
[0145] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0146] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.
[0147] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing devices to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.
[0148] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, so that a series of operation steps are executed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions for implementing the steps specified in one process or a plurality of processes and / or blocks Figure 1 one process or a plurality of processes and / or blocks Figure 1 steps for the functions specified in one block or a plurality of blocks.
[0149] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.
Claims
1. A fault detection method, characterized in that, The method is applied to a health detection device, and the method includes: Sending at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other, so that when the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request, and so that each target external device, when receiving any connectivity detection request, feeds back response information to the boundary device, and so that when the boundary device receives the response information fed back by any target external device, it sends the response information to the health detection device; For any target external device, based on the response information feedback data of the target external device, determining whether the target external device is in a connected state; Counting a first proportion of the target external devices in a connected state among all target external devices, and based on the first proportion and a first set proportion threshold, determining whether the boundary device has a fault.
2. The method according to claim 1, wherein The determining whether the boundary device has a fault based on the first proportion and the first set proportion threshold includes: If the first proportion is not less than the first set proportion threshold, determining that the boundary device has no fault; If the first proportion is less than the first set proportion threshold, determining that the boundary device has a fault.
3. The method according to claim 1, characterized in that, The determining whether the target external device is in a connected state based on the response information feedback data of the target external device includes: Counting a second proportion of the number of times the target external device feeds back response information in the total number of connectivity detection requests carrying the target external device identifier, and based on the second proportion and a second set proportion threshold, determining whether the target external device is in a connected state.
4. The method according to claim 3, wherein The determining whether the target external device is in a connected state based on the second proportion and the second set proportion threshold includes: If the second proportion is not less than the second set proportion threshold, determining that the target external device is in a connected state; If the second proportion is less than the second set proportion threshold, determining that the target external device is in a disconnected state.
5. The method according to claim 1, characterized in that After sending at least two connectivity detection requests to the boundary device and before, for any target external device, determining whether the target external device is in a connected state based on the response information feedback data of the target external device, the method further includes: For any connectivity detection request carrying any target external device identifier sent to the boundary device, if the response information carrying the target external device identifier forwarded by the boundary device is received within a set time period, determining that the target external device has fed back response information for the connectivity detection request; if the response information carrying the target external device identifier forwarded by the boundary device is not received within the set time period, determining that the target external device has not fed back response information for the connectivity detection request.
6. The method according to any one of claims 1-5, characterized in that, The health detection device is configured in an internal network, and the internal network includes a network area not connected to the Internet.
7. The method according to any one of claims 1-5, characterized in that, Before sending at least two connectivity detection requests to the boundary device, the method further includes: Obtain the operation metrics of multiple candidate external devices, and select each of the target external devices from the candidate external devices whose operation metrics meet the set metric requirements.
8. A fault detection device, characterized in that, The device includes: A sending module, configured to send at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other, so that when the boundary device receives each connectivity detection request, it sends the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request, and so that when each target external device receives any connectivity detection request, it feeds back response information to the boundary device, and so that when the boundary device receives the response information fed back by any target external device, it sends the response information to a health detection device; A judgment module, configured to, for any target external device, judge whether the target external device is in a connected state based on the response information feedback data of the target external device; A detection module, configured to count the first proportion of the target external devices in a connected state among all the target external devices, and judge whether the boundary device has a fault according to the first proportion and a first set proportion threshold.
9. A fault detection system, characterized in that, The system includes: A health detection device, configured to send at least two connectivity detection requests to a boundary device, where the target external device identifiers carried in the at least two connectivity detection requests are different from each other; The boundary device, configured to, for each received connectivity detection request, send the connectivity detection request to the target external device corresponding to the target external device identifier carried in the connectivity detection request; Each target external device, configured to, if it receives any connectivity detection request, feed back response information to the boundary device; The boundary device, further configured to, if it receives the response information fed back by any target external device, send the response information to the health detection device; The health detection device, further configured to, for any target external device, judge whether the target external device is in a connected state based on the response information feedback data of the target external device; count the first proportion of the target external devices in a connected state among all the target external devices, and judge whether the boundary device has a fault according to the first proportion and a first set proportion threshold.
10. An electronic device, characterized in that, The electronic device includes at least a processor and a memory, and the processor is configured to implement the steps of the method according to any one of claims 1-7 when executing the computer program stored in the memory.