Camera fault detection method and device

Abstract

The embodiment of the invention provides a camera fault detection method and device. The method comprises the following steps: generating a knowledge base comprising an internet protocol (IP) address of a camera and information of a plurality of transmission nodes to which the camera belongs; receiving a fault detection request for a fault camera, and searching an IP address of the fault camera and information of a transmission node to which the fault camera belongs in the knowledge base; the method comprises the steps of sequentially detecting operation states of transmission nodes according to information of the transmission nodes to which fault cameras belong, determining that the fault reason of the fault cameras is node faults under the condition that the transmission nodes are not accessed to a detection platform, and detecting the operation states of the fault cameras under the condition that the operation states of the transmission nodes are normal. And the fault reason of the fault camera is determined. Through the camera fault detection method and device, the problem that a general camera fault detection method is low in efficiency is solved, and then the effect of accurately and rapidly determining the fault reason of the camera is achieved.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a camera fault detection method and device. Background Art

[0002] With the rapid development of science and technology, intelligent monitoring has been widely used in many occasions such as military, customs, public security, fire protection, forestry, factories, airports, railways, ports, urban transportation, etc., and has also entered thousands of households. The core of intelligent monitoring is the intelligent recognition algorithm, which can identify and judge the behavior or characteristics of people or objects in the scene, and generate alarm prompts to feedback to users or administrators under appropriate conditions. The monitoring terminal-camera is the eye of intelligent monitoring. After an intelligent monitoring system starts to operate, there are many types of fault points that affect normal use, but camera failure is often high-probability and common. For some scenarios, such as intelligent monitoring of factory production lines and intelligent road monitoring of public security departments, the number of cameras is very large, ranging from hundreds to thousands or even tens of thousands. Faced with such a huge number of cameras, and frequent failures. Once a camera fails, it will inevitably affect the intelligent monitoring business and cause losses to users. How to shorten the time when the camera fails and goes offline? This can reduce the losses caused to users to a certain extent.

[0003] When an administrator is informed that a camera has been disconnected, the common analysis and diagnosis method is to first use the ping tool on the operation and maintenance PC to access the camera's management IP address to confirm whether the network is connected. If the network is connected, it means that the camera hardware is faulty; if the network is not connected, it means that the network node or transmission cable is faulty. Then, use tools such as tracert and pathping to track the data packet to determine which network node the data packet is lost at, and then use the telnet tool to log in to the corresponding network node to analyze whether there is a device failure, device overload, power failure, interface blockage, interface cable problem, configuration problem, etc., and then go to the site to confirm whether the cause of the failure analyzed above is accurate, and finally give a specific solution and solve the problem. Aside from the time spent on giving solutions and solving problems, it takes several minutes or even more time to analyze and diagnose the cause of the camera disconnection, which often depends on the complexity of the network and the technical level of the analyst. Summary of the invention

[0004] The embodiments of the present application provide a camera fault detection method and device, which at least solve the problem of low efficiency of general camera fault detection methods.

[0005] According to one embodiment of the present application, a camera fault detection method is provided, including: generating a knowledge base including an Internet Protocol IP address of a camera and information of multiple transmission nodes to which the camera belongs; receiving a fault detection request for a faulty camera, searching the IP address of the faulty camera and the information of the transmission node to which the faulty camera belongs in the knowledge base; detecting the operating status of the transmission nodes in sequence according to the information of the transmission nodes to which the faulty camera belongs, and when the transmission nodes are not connected to a detection platform, determining that the cause of the fault of the faulty camera is a node failure, and when the operating status of the transmission node is normal, detecting the operating status of the faulty camera and determining the cause of the fault of the faulty camera.

[0006] In an exemplary embodiment, the operating status of the transmission nodes to which the faulty camera belongs is detected in sequence according to the information of the transmission nodes, including: detecting whether the first transmission node of the transmission nodes to which the faulty camera belongs is connected to a detection platform; if the first transmission node is not connected to the detection platform, checking the detection platform; if the first transmission node is connected to the detection platform, detecting whether other transmission nodes to which the faulty camera belongs are connected to the detection platform in sequence, wherein the first transmission node is a gateway node; for the first target transmission node among the other transmission nodes that is not connected to the detection platform, accessing the previous transmission node adjacent to the target transmission node and detecting the configuration parameters of the previous transmission node. Check whether the number is correct, and determine according to the detection result that the cause of the fault is a fault in the target transmission node or a fault in the previous transmission node; when all the transmission nodes to which the faulty camera belongs are connected to the detection platform, detect whether the faulty camera is connected to the detection platform; when the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the status of the interface connecting the last transmission node to the faulty camera, and determine according to the access result that the cause of the fault is a camera failure; when the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera, and determine according to the access result that the cause of the fault is a camera failure.

[0007] In an exemplary embodiment, a previous transmission node adjacent to the target transmission node is accessed and configuration parameters of the previous transmission node are detected to determine whether they are correct, and the cause of the fault is determined based on the detection result to be that the target transmission node or the previous transmission node is faulty, including: accessing the previous transmission node and checking routing table information of the previous transmission node, determining whether the routing table information includes the IP address of the previous transmission node, and if the routing table information does not include the IP address of the previous transmission node, determining that the cause of the fault is that the previous transmission node is not configured with a target route; if the routing table information includes the IP address of the previous transmission node , check the status of the downstream cascade interface of the upper transmission node, and when the downstream cascade interface is operating normally, determine that the cause of the fault is a hardware failure or a configuration error of the target transmission node; when the downstream cascade interface is not operating normally, check whether the downstream cascade interface is closed, and when the downstream cascade interface is closed, determine that the cause of the fault is that the downstream cascade interface of the upper transmission node has been closed; when the downstream cascade interface is not closed, determine that the cause of the fault is a hardware failure of the target transmission node or a problem with the cascade line between the target transmission node and the upper transmission node or a power outage of the target transmission node.

[0008] In an exemplary embodiment, when the operating status of the transmission node is normal, the operating status of the faulty camera is detected, including: accessing the last transmission node, checking whether the configuration parameters of the last transmission node are correct, and when the configuration parameters of the last transmission node are correct, restarting the interface connecting the last transmission node and the faulty camera, and when the configuration parameters of the last transmission node are wrong, determining that the cause of the fault is a fault in the camera cable connection, a fault in the camera hardware, or a power outage in the camera.

[0009] In an exemplary embodiment, when the operating status of the transmission node is normal, the operating status of the faulty camera is detected, including: when the IP address of the faulty camera is not successfully accessed, determining that the cause of the fault is a hardware failure of the camera; when the IP address of the faulty camera is successfully accessed, checking whether the port of the faulty camera is normally opened, and when the port is normally opened, determining that the cause of the fault is a suspended state of the main application of the faulty camera; when the port is not normally opened, determining that the cause of the fault is that the main application of the faulty camera is closed.

[0010] In an exemplary embodiment, after restarting the interface connecting the last transmission node to the faulty camera, the method further includes: detecting again whether the faulty camera is connected to the detection platform.

[0011] In an exemplary embodiment, before receiving the fault detection request for the faulty camera, the method further includes: screening the faulty cameras and generating list information of the faulty cameras.

[0012] According to another embodiment of the present application, a camera fault detection device is provided, including: a generation module: used to generate a knowledge base including an Internet Protocol IP address of a camera and information of multiple transmission nodes to which the camera belongs; a search module, used to receive a fault detection request for a faulty camera, and search the IP address of the faulty camera and the information of the transmission node to which the faulty camera belongs in the knowledge base; a determination module, used to detect the operating status of the transmission nodes in sequence according to the information of the transmission nodes to which the faulty camera belongs, and when the transmission nodes are not connected to a detection platform, determine that the cause of the fault of the faulty camera is a node failure, and when the operating status of the transmission node is normal, detect the operating status of the faulty camera and determine the cause of the fault of the faulty camera.

[0013] In an exemplary embodiment, the determination module also includes: a detection unit, which is used to detect whether the first transmission node of the transmission node to which the faulty camera belongs is connected to a detection platform; if the first transmission node is not connected to the detection platform, the detection platform is checked; if the first transmission node is connected to the detection platform, other transmission nodes to which the faulty camera belongs are detected in turn whether they are connected to the detection platform, wherein the first transmission node is a gateway node; a first determination unit, for the first target transmission node among the other transmission nodes that is not connected to the detection platform, is used to access the previous transmission node adjacent to the target transmission node and detect whether the configuration parameters of the previous transmission node are correct, and determine whether the detection result is correct. Determine that the cause of the failure is a failure of the target transmission node or a failure of the previous transmission node; a second determination unit is used to detect whether the faulty camera is connected to the detection platform when all the transmission nodes to which the faulty camera belongs are connected to the detection platform, and if the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the status of the interface connecting the last transmission node to the faulty camera, and determine that the cause of the failure is a camera failure based on the access result, and if the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera, and determine that the cause of the failure is a camera failure based on the access result.

[0014] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.

[0015] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0016] Through the embodiments of the present application, since the IP address of the camera and the information of the transmission node to which the camera belongs are collected and a knowledge base is generated, when it is necessary to perform fault detection on a faulty camera, the IP address of the faulty camera and the information of the transmission node to which the faulty camera belongs can be searched for and used for subsequent detection of the transmission nodes in sequence. When the transmission nodes are operating normally, the operating status of the faulty camera can be detected, and the cause of the fault of the faulty camera can be determined, thereby achieving the effect of accurately and quickly determining the cause of the camera's failure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 is a flow chart of a camera fault detection method according to an embodiment of the present application;

[0020] Figure 2 is a structural block diagram of a camera fault detection device according to an embodiment of the present application;

[0021] Figure 3 is a structural block diagram of a camera fault detection device according to yet another embodiment of the present application;

[0022] Figure 4 is a communication topology diagram according to an embodiment of the present application;

[0023] Figure 5 is a flow chart of a camera fault detection method according to yet another embodiment of the present application;

[0024] Figure 6 It is a flow chart of a camera fault detection method according to another embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or apparatuses.

[0027] The following is a description of relevant terms in the embodiments of the present invention:

[0028] The application used standard network troubleshooting techniques in Internet protocols and the Python programming language, such as ping, telnet / ssh protocols, and display / show, restart interface, and other commands based on transmission nodes. The ping protocol is used to detect network connectivity, but it cannot guarantee whether a certain application service at the head end can be accessed normally; the telnet / ssh protocol can effectively detect whether the application service can be accessed normally, and can also be used to log in to various transmission nodes for remote operation and control; the display / show command is used to check whether the configuration parameters of each transmission node are correct; the restart interface command can achieve a soft restart of the interface, release the interface cache data, and restore the interface to normal working state; the Python programming language is used to implement the programmability of the intelligent analysis and diagnosis system.

[0029] According to one aspect of an embodiment of the present application, a camera fault detection method is provided. Figure 1 is a flow chart of a camera fault detection method according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0030] Step S102, generating a knowledge base including an Internet Protocol IP address of the camera and information of a plurality of transmission nodes to which the camera belongs;

[0031] Step S104, receiving a fault detection request for a faulty camera, and searching the knowledge base for the IP address of the faulty camera and information of the transmission node to which the faulty camera belongs;

[0032] Before step S104 of this embodiment, the process also includes screening faulty cameras and generating list information of the faulty cameras.

[0033] Step S106, detect the operating status of the transmission nodes in turn according to the information of the transmission node to which the faulty camera belongs. When the transmission node is not connected to the detection platform, determine that the fault cause of the faulty camera is a node failure. When the operating status of the transmission node is normal, detect the operating status of the faulty camera and determine the fault cause of the faulty camera.

[0034] In step S106 of this embodiment, it includes detecting whether the first transmission node of the transmission nodes to which the faulty camera belongs is connected to the detection platform. If the first transmission node is not connected to the detection platform, the detection platform is checked. If the first transmission node is connected to the detection platform, other transmission nodes to which the faulty camera belongs are sequentially detected to see whether they are connected to the detection platform, wherein the first transmission node is a gateway node.

[0035] For the first target transmission node among other transmission nodes that is not connected to the detection platform, access the previous transmission node adjacent to the target transmission node and detect whether the configuration parameters of the previous transmission node are correct, and determine according to the detection result that the cause of the failure is a failure of the target transmission node or a failure of the previous transmission node;

[0036] When all the transmission nodes to which the faulty camera belongs are connected to the detection platform, check whether the faulty camera is connected to the detection platform. If the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the status of the interface connecting the last transmission node to the faulty camera. According to the access result, determine that the cause of the fault is a camera failure. When the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera. According to the access result, determine that the cause of the fault is a camera failure.

[0037] In an exemplary embodiment, a previous transmission node adjacent to a target transmission node is accessed and configuration parameters of the previous transmission node are detected to determine whether they are correct, and according to the detection result, determining that the cause of the fault is that the target transmission node is faulty or the previous transmission node is faulty, including: accessing the previous transmission node and checking routing table information of the previous transmission node, determining whether the routing table information includes the IP address of the previous transmission node, and if the routing table information does not include the IP address of the previous transmission node, determining that the cause of the fault is that the previous transmission node is not configured with a target route; if the routing table information includes the IP address of the previous transmission node Next, check the status of the downstream cascade interface of the upper transmission node. When the downstream cascade interface operates normally, determine that the cause of the fault is a hardware failure or configuration error of the target transmission node; when the downstream cascade interface does not operate normally, check whether the downstream cascade interface is closed. When the downstream cascade interface is closed, determine that the cause of the fault is that the downstream cascade interface of the upper transmission node has been closed; when the downstream cascade interface is not closed, determine that the cause of the fault is a hardware failure of the target transmission node or a problem with the cascade line between the target transmission node and the upper transmission node or a power outage of the target transmission node.

[0038] In an exemplary embodiment, when the operating status of the transmission node is normal, the operating status of the faulty camera is detected, including: accessing the last transmission node, checking whether the configuration parameters of the last transmission node are correct; when the configuration parameters of the last transmission node are correct, restarting the interface connecting the last transmission node to the faulty camera; when the configuration parameters of the last transmission node are incorrect, determining that the cause of the fault is a fault in the camera cable connection, a fault in the camera hardware, or a power outage in the camera.

[0039] In an exemplary embodiment, when the operating status of the transmission node is normal, the operating status of the faulty camera is detected, including: when the IP address of the faulty camera is not successfully accessed, determining that the cause of the fault is a hardware failure of the camera; when the IP address of the faulty camera is successfully accessed, checking whether the port of the faulty camera is normally opened, and when the port is normally opened, determining that the cause of the fault is a suspended state of the main application of the faulty camera; when the port is not normally opened, determining that the cause of the fault is that the main application of the faulty camera is closed.

[0040] In an exemplary embodiment, after restarting the interface connecting the last transmission node to the faulty camera, the method further includes: detecting again whether the faulty camera is connected to the detection platform.

[0041] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory / random access memory (ROM / RAM), a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of each embodiment of the present application.

[0042] In this embodiment, a camera fault detection device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" may be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

[0043] Figure 2 is a structural block diagram of a camera fault detection device according to an embodiment of the present application, such as Figure 2 As shown, the device includes a generating module 10 , a searching module 20 and a determining module 30 .

[0044] A generating module 10, for generating a knowledge base including information of an Internet Protocol IP address of a camera and a transmission node to which the camera belongs;

[0045] A search module 20, configured to receive a fault detection request for a faulty camera, and search a knowledge base for the IP address of the faulty camera and information of a transmission node to which the faulty camera belongs;

[0046] The determination module 30 is used to detect the operating status of the transmission nodes in sequence according to the information of the transmission nodes to which the faulty camera belongs. When the transmission nodes are not connected to the detection platform, it is determined that the cause of the failure of the faulty camera is a node failure. When the operating status of the transmission node is normal, the operating status of the faulty camera is detected and the cause of the failure of the faulty camera is determined.

[0047] Figure 3 is a structural block diagram of a camera fault detection device according to another embodiment of the present application, such as Figure 3 As shown, the device includes Figure 2 In addition to all modules shown, the determination module also includes:

[0048] The detection unit 31 is used to detect whether the first transmission node of the transmission nodes to which the faulty camera belongs is connected to the detection platform. If the first transmission node is not connected to the detection platform, the detection platform is checked. If the first transmission node is connected to the detection platform, other transmission nodes to which the faulty camera belongs are sequentially detected to see whether they are connected to the detection platform, wherein the first transmission node is a gateway node.

[0049] The first determining unit 32 is used for accessing the previous transmission node adjacent to the target transmission node and detecting whether the configuration parameters of the previous transmission node are correct, and determining, according to the detection result, that the cause of the failure is a failure of the target transmission node or a failure of the previous transmission node;

[0050] The second determination unit 33 is used to detect whether the faulty camera is connected to the detection platform when all the transmission nodes to which the faulty camera belongs are connected to the detection platform; if the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the state of the interface connecting the last transmission node to the faulty camera, and determine according to the access result that the cause of the fault is a camera failure; if the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera, and determine according to the access result that the cause of the fault is a camera failure.

[0051] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0052] In order to facilitate the understanding of the technical solutions provided by the application embodiments, the embodiments are described below in combination with specific scenarios.

[0053] Figure 4 is a communication topology diagram according to an embodiment of the present application, such as Figure 4 As shown, the camera in the intelligent monitoring is located at the end of the 802.3 wired Ethernet LAN and is a terminal node. In addition, it is equipped with a data center server, a PC operation and maintenance end, and N transmission nodes (N is greater than or equal to 1), where the transmission nodes include various switches, firewalls and other equipment.

[0054] Figure 5 is a flow chart of a camera fault detection method according to another embodiment of the present application. Figure 5 As shown, the following steps are included:

[0055] Step S5001, transmission node parameter setting;

[0056] Specifically, in order to accurately analyze the reasons for the camera failure and disconnection, it is necessary to collect the transmission node information of each camera in advance, such as the management IP address, login username and password, and set the N transmission node information of the camera in the analysis and diagnosis system (fill in from the gateway node to the terminal transmission node in sequence). This parameter setting only needs to be filled in once and saved for permanent use, and does not need to be set again later.

[0057] Step S5002, entering the diagnosis interface;

[0058] Specifically, open the analysis and diagnosis system to enter the diagnosis interface. The analysis and diagnosis system can be made into an application based on Windows or Ubuntu system, or it can be embedded in the camera status interface of the streaming platform. The "diagnosis interface" can be popped up by clicking its unique icon or button with the mouse.

[0059] Step S5003, obtaining the IP address of the camera to be analyzed and diagnosed;

[0060] Specifically, in the "diagnosis interface" popped up in step S5002, the IP address of the camera to be analyzed and diagnosed can be obtained by manual filling or automatic reading. Whether it is a normally operating camera or a faulty offline camera, it can be analyzed and diagnosed.

[0061] Step S5004, start diagnosis;

[0062] Specifically, the analysis and diagnosis can be started by clicking the "Start Analysis and Diagnosis" button with the mouse.

[0063] Step S5005, determine whether pinging the gateway node IP has timed out;

[0064] Specifically, by pinging the first transmission node, i.e., the gateway node IP and returning the ping results, if all the results are timed out, then proceed to step S5006; if all the results are not timed out, it means that the gateway node is operating normally, then proceed to step S5007;

[0065] Step S5006, outputting "check whether the diagnosis platform is connected to the network", and terminating the analysis and diagnosis;

[0066] Step S5007, pinging other transmission node IPs in order to see if timeout occurs;

[0067] Specifically, by pinging the IP addresses of other transmission nodes in sequence and returning the ping results, until the Nth transmission node is pinged, if all the results are timed out, it means that the current pinged transmission node is not running normally, and the process goes to step S5008; if all the ping return results are not timed out, that is, there is no timeout, it means that the transmission node is running normally, and the process goes to step S5016;

[0068] Step S5008, telnet / ssh to a transmission node and execute the display / show route view command;

[0069] Specifically, use the telnet / ssh command to log in to the previous transmission node, and then execute the display / show ip route-table command on the node to view the existing routing table information on the node.

[0070] Step S5009, check whether there is a target route;

[0071] Specifically, if it is determined according to the query content in the system step S5008 whether the IP of the second transmission node exists in the existing routing table, if not, proceed to step S5010; if it is determined to exist in the existing routing table, proceed to step S5011.

[0072] Step S5010, outputting "There is no target route on the previous transmission node (IP information is automatically marked), configuration is required";

[0073] Step S5011, check the status of the downstream cascade interface up / down;

[0074] Specifically, since the last transmission node has been logged in in step S5008, the interface status information can be viewed by executing display / showinterface interface number. If the interface status is up, proceed to step S5012; if the interface status is down, proceed to step S5013.

[0075] Step S5012: Output "this transmission node hardware failure or configuration error";

[0076] Step S5013, checking whether the downstream cascade interface has been manually closed;

[0077] Specifically, since the previous transmission node has been logged in in step S5008, it is possible to check and determine whether the downstream cascade interface is configured with a shutdown command. If the shutdown command is configured under the interface, the interface will be closed. If yes, proceed to step S5014; if not, proceed to step S5015.

[0078] Step S5014, outputting "the downstream cascade interface of the previous transmission node (with automatically labeled IP information) has been manually closed";

[0079] Step S5015, outputting "the hardware of this node is faulty or there is a problem with the cascade line between this node and the previous transmission node (with automatic IP information labeling) or the power of this node is off";

[0080] Step S5016, whether pinging the faulty camera IP times out;

[0081] Specifically, by pinging the IP of the faulty camera and returning the ping results, if the results are not all timed out, that is, there is no timeout, go to step S5017; if the results are all timed out, go to step S5024.

[0082] Step S5017, telnet the faulty camera IP + port 5060 to see if it is successful;

[0083] Specifically, since the protocol port number is a logical interface that is open to the outside world for external access by a specific application, if the port cannot be accessed from the outside, there must be something wrong with the corresponding application. Therefore, you can use the "telnet ip+port" command to test whether a specific application can be connected normally. If it can be connected normally, it means that the application is normal. If it cannot be connected normally, it means that the application is not running normally. This step uses this principle to determine whether the camera port 5060 (port 5060 is the port for external access to a certain brand of camera to obtain the stream, and the port number of different brands may be different) is running normally. If the connection can be successful, go to step S5018; if the connection cannot be successful, go to step S5019.

[0084] Step S5018, outputting "the camera being analyzed and diagnosed is operating normally";

[0085] Step S5019, determine whether the telnet to the faulty camera is successful;

[0086] Specifically, log in to the camera backend through the telnet tool to determine whether the login is successful. If the login cannot be successful, go to step S5020; if the login is successful, go to step S5021.

[0087] Step S5020, outputting "camera hardware failure";

[0088] Step S5021, check whether port 5060 is normally opened;

[0089] Specifically, the camera's operating system is a streamlined Linux-like system, so after logging into the camera backend, you can use the netstat-tunlp command to check whether port 5060 is normal. If the query result shows that port 5060 is normal, go to step S5022; if the result shows that port 5060 is abnormal, go to step S5023 and output "The main application of the camera is unexpectedly closed, and the camera needs to be restarted."

[0090] Step S5022, outputting "the main application of the camera is suspended";

[0091] Step S5023, outputting "The main application of the camera is unexpectedly closed, and the camera needs to be restarted";

[0092] Step S5024, telnet / ssh the Nth transmission node;

[0093] Step S5025, checking the up / down status of the corresponding interface at the Nth transmission node;

[0094] Specifically, the status of the port to which the camera is connected can be checked by using the display / show interface x / x command. If the status is up, proceed to step S5026; if the status is down, proceed to step S5027.

[0095] Step S5026, restarting the access port corresponding to the camera on the Nth transmission node;

[0096] Specifically, restart the access port corresponding to the camera on the Nth transmission node, and the port can be closed and then reopened by command restartinterface x / x, so that the data cached in the port will be released. If the data is blocked due to port blockage or pseudo-death, the problem can be solved by restarting the interface. Therefore, after restarting the port, if it is the first restart, it will enter step S5016; if it is the second restart, it will enter step S5017.

[0097] Step S5027, output "camera cable connection problem or hardware failure or camera power failure".

[0098] Figure 6 is a flow chart of a camera fault detection method according to another embodiment of the present application, such as Figure 6 As shown, the following steps are included:

[0099] Step S602, searching for faulty offline cameras on the streaming media platform;

[0100] Specifically, filter the list of faulty offline cameras in the "National Standard Equipment" list of the streaming platform.

[0101] Step S604, manually click the "Diagnosis" button;

[0102] Specifically, there is a "Diagnosis" button in the "Operation" item on the right side of each offline camera information displayed. Just click the button with the mouse.

[0103] Step S606, a diagnostic interface pops up and automatically obtains the IP address of the offline camera;

[0104] Specifically, after step S604 is completed, a "camera offline analysis and diagnosis" interface will automatically pop up, and the IP address information of the offline camera will be automatically filled in the "camera to be analyzed and diagnosed" column.

[0105] Step S608, click the "Start Analysis and Diagnosis" button;

[0106] Specifically, click the "Start Analysis and Diagnosis" button. There is a "Start Analysis and Diagnosis" button in the "Camera Offline Analysis and Diagnosis" interface. Click the button with the mouse, and the analysis and diagnosis system will start to analyze the camera.

[0107] Step S610: Output diagnosis conclusion

[0108] The diagnosis is complete.

[0109] From the above description, it can be seen that the above embodiment achieves the following technical effects: starting from the link of analyzing and diagnosing the cause of camera failure, it realizes its rapidity, efficiency, intelligence and automation. Compared with the traditional manual troubleshooting analysis, it omits the trouble of manually inputting a large number of commands; at the same time, it also integrates the experience summary of various causes of camera failure, ensuring that the analyzed causes of failure are fast, efficient, comprehensive and accurate. At the same time, with this application, the time spent in analyzing and diagnosing the cause of camera failure will not be affected by factors such as network complexity and the technical level of analysts. It is suitable for camera failure offline in intelligent monitoring and security monitoring applications in various occasions, and can quickly locate the cause of the failure, thereby shortening the camera offline time and reducing the user's loss.

[0110] The embodiments of the present application are a camera fault intelligent analysis and diagnosis system and method applicable to various scenarios. Through this application, rapid and comprehensive intelligent analysis and diagnosis can be achieved, the cause of the camera fault offline can be located, and corresponding solutions can be given. It has the characteristics of simple and convenient operation. There is no need to enter cumbersome commands, no need for very professional diagnostic personnel, and it is not affected by the complexity of the network. Technicians of ordinary levels can get started and can quickly locate the cause of the camera fault offline and give appropriate solutions within minutes, which greatly improves the analysis efficiency of the operation and maintenance personnel, thereby shortening the camera fault offline time and reducing the loss to the user to a certain extent. The present application is particularly suitable for application scenarios with a large number of cameras, and the effect is more prominent, which is convenient for promotion and application in large-scale scenarios.

[0111] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the present application is not limited to any specific combination of hardware and software.

[0112] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A camera fault detection method, characterized in that: include: generating a knowledge base including an Internet Protocol (IP) address of a camera and information of a plurality of transmission nodes to which the camera belongs; receiving a fault detection request for a faulty camera, and searching the knowledge base for the IP address of the faulty camera and the information of the transmission node to which the faulty camera belongs; According to the information of the transmission node to which the faulty camera belongs, the operating status of the transmission node is detected in turn. When the transmission node is not connected to the detection platform, it is determined that the failure cause of the faulty camera is a node failure. When the operating status of the transmission node is normal, the operating status of the faulty camera is detected and the failure cause of the faulty camera is determined.

2. The method according to claim 1, characterized in that Detecting the operating status of the transmission nodes in sequence according to the information of the transmission nodes to which the faulty camera belongs, including: Detect whether the first transmission node of the transmission node to which the faulty camera belongs is connected to the detection platform. If the first transmission node is not connected to the detection platform, check the detection platform. If the first transmission node is connected to the detection platform, detect in turn whether other transmission nodes to which the faulty camera belongs are connected to the detection platform, wherein the first transmission node is a gateway node; For the first target transmission node among the other transmission nodes that is not connected to the detection platform, access the previous transmission node adjacent to the target transmission node and detect whether the configuration parameters of the previous transmission node are correct, and determine according to the detection result that the cause of the failure is that the target transmission node fails or the previous transmission node fails; When all the transmission nodes to which the faulty camera belongs are connected to the detection platform, detect whether the faulty camera is connected to the detection platform; when the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the status of the interface connecting the last transmission node to the faulty camera, and determine according to the access result that the cause of the fault is a camera failure; when the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera, and determine according to the access result that the cause of the fault is a camera failure.

3. The method according to claim 2, characterized in that Accessing a previous transmission node adjacent to the target transmission node and detecting whether configuration parameters of the previous transmission node are correct, and determining, according to the detection result, that the fault cause is a fault of the target transmission node or a fault of the previous transmission node, including: Access the previous transmission node and check the routing table information of the previous transmission node, determine whether the routing table information includes the IP address of the previous transmission node, and if the routing table information does not include the IP address of the previous transmission node, determine that the cause of the fault is that the previous transmission node is not configured with a target route; In a case where the IP address of the previous transmission node is included in the routing table information, checking the status of the downstream cascade interface of the previous transmission node, and in a case where the downstream cascade interface operates normally, determining that the fault cause is a hardware fault or a configuration error of the target transmission node; In the case where the downstream cascade interface is not operating normally, checking whether the downstream cascade interface is closed, and in the case where the downstream cascade interface is closed, determining that the fault cause is that the downstream cascade interface of the upper transmission node has been closed; In the case that the downstream cascade interface is not closed, it is determined that the fault cause is a hardware failure of the target transmission node, or a problem with the cascade line between the target transmission node and the previous transmission node, or a power outage of the target transmission node.

4. The method according to claim 2, characterized in that: When the operation state of the transmission node is normal, detecting the operation state of the faulty camera includes: Access the last transmission node and check whether the configuration parameters of the last transmission node are correct. If the configuration parameters of the last transmission node are correct, restart the interface connecting the last transmission node to the faulty camera. If the configuration parameters of the last transmission node are incorrect, determine that the cause of the fault is a fault in the camera cable connection, a fault in the camera hardware, or a power outage in the camera.

5. The method according to claim 2, characterized in that: When the operation state of the transmission node is normal, detecting the operation state of the faulty camera includes: In the case where the IP address of the faulty camera is not successfully accessed, determining that the fault cause is a hardware failure of the camera; In the case of successfully accessing the IP address of the faulty camera, checking whether the port of the faulty camera is normally opened, and in the case of the port being normally opened, determining that the cause of the fault is that the main application of the faulty camera is suspended; In the case that the port is not opened normally, it is determined that the cause of the failure is that the main application of the faulty camera is closed.

6. The method according to claim 4, characterized in that After restarting the interface connecting the last transmission node to the faulty camera, the method further includes: detecting again whether the faulty camera is connected to the detection platform.

7. The method according to claim 1, characterized in that Before receiving the fault detection request for the fault camera, the method further includes: The faulty cameras are screened and list information of the faulty cameras is generated.

8. A camera fault detection device, characterized in that: include: A generation module: used to generate a knowledge base including an Internet Protocol IP address of a camera and information of a plurality of transmission nodes to which the camera belongs; A search module, configured to receive a fault detection request for a faulty camera, and search the knowledge base for the IP address of the faulty camera and the information of the transmission node to which the faulty camera belongs; A determination module is used to detect the operating status of the transmission node in turn according to the information of the transmission node to which the faulty camera belongs. When the transmission node is not connected to the detection platform, it is determined that the cause of the failure of the faulty camera is a node failure. When the operating status of the transmission node is normal, the operating status of the faulty camera is detected and the cause of the failure of the faulty camera is determined.

9. The device according to claim 8, characterized in that The determination module also includes: a detection unit, configured to detect whether a first transmission node of the transmission nodes to which the faulty camera belongs is connected to a detection platform, and to check the detection platform if the first transmission node is not connected to the detection platform, and to sequentially detect whether other transmission nodes to which the faulty camera belongs are connected to the detection platform if the first transmission node is connected to the detection platform, wherein the first transmission node is a gateway node; A first determining unit, for a first target transmission node among the other transmission nodes that is not connected to the detection platform, is used to access a previous transmission node adjacent to the target transmission node and detect whether a configuration parameter of the previous transmission node is correct, and determine, according to the detection result, that the cause of the failure is a failure of the target transmission node or a failure of the previous transmission node; The second determination unit is used to detect whether the faulty camera is connected to the detection platform when all the transmission nodes to which the faulty camera belongs are connected to the detection platform; if the faulty camera is not connected to the detection platform, access the last transmission node to which the faulty camera belongs and check the state of the interface connecting the last transmission node to the faulty camera, and determine that the cause of the fault is a camera failure according to the access result; and if the faulty camera is connected to the detection platform, access the IP address of the faulty camera and the port of the faulty camera, and determine that the cause of the fault is a camera failure according to the access result.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Images