Method and device for improving maintainability of video monitoring system and electronic equipment

Abstract

The embodiment of the invention discloses a maintainability improving method and device of a video monitoring system and electronic equipment. The method comprises the following steps: obtaining a service evaluation index corresponding to service equipment, determining service state information based on a multi-level index judgment method, determining that the service state information is abnormal in response to the service state information, maintaining the service equipment according to a hierarchical service keeping strategy, and determining a recovery state of the service equipment. And further, in response to the recovery state, determining that the recovery state is a recovery fault, determining a target recovery instruction according to the fault classification recovery strategy, and executing the target recovery instruction. The state and fault hidden dangers of the system can be comprehensively detected and mastered through multiple layers of service evaluation indexes, anomaly detection is more timely, the fault detection isolation time is shortened, unnecessary repair time is saved through a service maintenance strategy and a fault classification repair strategy, the maintainability of the video monitoring system is improved, and the fault detection efficiency is improved. And the use requirement of a high-maintainability scene is met.

Description

A method, apparatus, and electronic device for improving the maintainability of a video surveillance system. Technical Field

[0001] This specification relates to the field of system maintenance technology, and in particular to a method for improving the maintainability of a video surveillance system. Background Technology

[0002] System maintainability refers to the ability of a system to maintain or restore its required functional state under given conditions when its equipment is maintained using prescribed procedures and resources. In certain video surveillance applications, the ability to maintain or quickly restore a system to its required functional state over extended periods is required. Therefore, improving the maintainability of video surveillance systems is necessary. However, currently used intelligent video operation and maintenance platforms often focus only on fault diagnosis and recovery of front-end devices, with limited attention to the operation and maintenance of back-end services. This results in an inability to comprehensively detect and understand the system's status and potential faults, leading to insufficient timeliness in anomaly detection and excessively long fault repair times, failing to meet the needs of high maintainability scenarios. Summary of the Invention

[0003] This specification provides a method, apparatus, and electronic device for improving the maintainability of a video surveillance system, the technical solution of which is as follows:

[0004] Firstly, embodiments of this specification provide a method for improving the maintainability of a video surveillance system, the method comprising:

[0005] For any service device in the video surveillance system, obtain the service evaluation index corresponding to the service device. The service device includes management device, media device, storage device and processing device. The service evaluation index includes device performance index, operating environment index, business service index and user experience index.

[0006] The service status information corresponding to the service evaluation indicators is determined based on a multi-level indicator judgment method.

[0007] In response to the service status information being determined to be abnormal, the service device is maintained according to the tiered service maintenance strategy, and the recovery status of the service device is determined.

[0008] In response to the recovery status being determined to be a recovery failure, the target repair instruction corresponding to the failure event is determined according to the failure classification and repair strategy, and the target repair instruction is executed.

[0009] Secondly, a maintainability improvement device for a video surveillance system is provided, the device comprising:

[0010] The acquisition module is used to acquire service evaluation indicators corresponding to any service device in the video surveillance system. The service devices include management devices, media devices, storage devices, and processing devices. The service evaluation indicators include device performance indicators, operating environment indicators, business service indicators, and user experience indicators.

[0011] The determination module is used to determine the service status information corresponding to the service evaluation indicators based on a multi-level indicator judgment method.

[0012] The maintenance module is used to maintain the service device according to the tiered service maintenance strategy in response to the service status information being determined to be abnormal, and to determine the recovery status of the service device.

[0013] The repair module is used to respond to the recovery status being determined to be a recovery fault, determine the target repair instruction corresponding to the fault event according to the fault classification repair strategy, and execute the target repair instruction.

[0014] Thirdly, an electronic device is provided, including a device processor and a memory;

[0015] The device processor is connected to the memory;

[0016] The memory is used to store executable program code;

[0017] The device processor runs a program corresponding to the executable program code stored in the memory to perform the steps of the method provided as in the first aspect or any possible implementation thereof.

[0018] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, the computer-readable storage medium storing instructions that, when executed on a computer or device processor, cause the computer or device processor to perform the method provided as in the first aspect or any possible implementation thereof.

[0019] The beneficial effects of the technical solutions provided in some embodiments of this specification include at least the following:

[0020] In one or more embodiments of this specification, service evaluation indicators corresponding to the service equipment are obtained, and then service status information corresponding to the service evaluation indicators is determined based on a multi-level indicator judgment method. In response to the service status information being determined to be abnormal, the service equipment is maintained according to a layered service maintenance strategy, and the recovery status of the service equipment is determined. Further, in response to the recovery status being determined to be a recovery fault, the target repair instruction corresponding to the fault event is determined according to a fault classification and repair strategy, and the target repair instruction is executed. The multi-level service evaluation indicators enable comprehensive detection and understanding of the system's status and potential faults, making anomaly detection more timely, reducing fault detection and isolation time, and saving unnecessary repair time through service maintenance and fault classification and repair strategies. This improves the maintainability of the video surveillance system and meets the usage requirements of high maintainability scenarios. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 is a flowchart of a method for improving the maintainability of a video surveillance system provided in an embodiment of this specification;

[0023] Figure 2 is a structural schematic diagram of a maintainability improvement device for a video surveillance system provided in an embodiment of this specification.

[0024] Figure 3 is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification. Detailed Implementation

[0025] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0026] The terms "first," "second," "third," etc., in the description, claims, and accompanying drawings are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0027] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the described elements without departing from the scope of this specification. Various processes or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0028] Please refer to Figure 1, which shows an overall flowchart of a method for improving the maintainability of a video surveillance system provided in an embodiment of this specification.

[0029] As shown in Figure 1, the method for improving the maintainability of this video surveillance system may include at least the following steps:

[0030] Step 101: For any service device in the video surveillance system, obtain the service evaluation index corresponding to the service device.

[0031] The service equipment includes management equipment, media equipment, storage equipment, and processing equipment, and the service evaluation indicators include equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators.

[0032] In the embodiments of this specification, system maintainability refers to the system's ability to maintain or restore its required functional state when its equipment is maintained using prescribed procedures and resources under given conditions. A video surveillance system may include multiple service devices such as management devices, media devices, storage devices, and processing devices. Each service device has a certain probability of malfunctioning or shutting down. The key to improving the maintainability of a video surveillance system lies in its ability to recover from faults and be put back into use in the shortest possible time, which can be achieved by reducing fault detection and isolation time and mean time to repair (MTBT). Therefore, to reduce fault detection and isolation time, a multi-level maintainability evaluation index and its monitoring mechanism can be established to comprehensively detect and understand the system's status within a video surveillance service index system. Specifically, after the video surveillance system is started, for any service device in the system, it is necessary to first obtain the corresponding service evaluation index for each service device. Optionally, the service evaluation index includes equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators.

[0033] Among them, device performance indicators may include CPU utilization, memory utilization, storage I / O performance, etc.; operating environment indicators may include network performance, service process status, database performance, etc.; business service indicators may include device management performance, media service performance, video storage performance, video processing performance, display and control device performance, etc.; and user experience indicators may include data and control latency, user response time, video picture quality, etc.

[0034] Step 103: Determine the service status information corresponding to the service evaluation indicators based on the multi-level indicator judgment method.

[0035] In the embodiments of this specification, for any service device in the video surveillance system, after obtaining the service evaluation index corresponding to that service device, since the service evaluation index includes equipment performance index, operating environment index, business service index, and user experience index, in order to comprehensively detect the service status of the video surveillance system and achieve rapid fault detection, a multi-level index judgment method can be used to comprehensively analyze all the obtained service evaluation indices to obtain their corresponding service status information. Specifically, when using the multi-level index judgment method, each service evaluation index can be compared with a threshold individually before determining the service status information, or judgment weights can be pre-assigned, and the weights of each service evaluation index can be fused to obtain a comprehensive index before determining the service status information.

[0036] In one possible implementation, determining the service status information corresponding to the service evaluation indicator based on a multi-level indicator judgment method includes:

[0037] Determine the threshold values ​​for the equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators, respectively.

[0038] The indicator values ​​corresponding to the device performance indicators, operating environment indicators, business service indicators, and user experience indicators are compared with the threshold values ​​of each indicator to obtain the comparison results.

[0039] The service status information corresponding to the service evaluation indicators is determined based on the comparison results.

[0040] In the embodiments of this specification, the service status information corresponding to the service evaluation indicators is determined based on a multi-level indicator judgment method. First, based on the improvement instructions issued by the target user, the threshold values ​​corresponding to the equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators are determined respectively. Then, the difference between the indicator values ​​corresponding to the equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators and their corresponding threshold values ​​is calculated and compared to obtain the comparison results. Finally, based on the improvement requirements in the improvement instructions and the comparison results, the service status information corresponding to the service evaluation indicators is determined. Specifically, priority weights can be set for each comparison result. If a high-priority comparison result indicates that the indicator threshold range is not met, the overall corresponding service status information can be determined as abnormal. Optionally, it can also be set that if any comparison result indicates that the indicator threshold range is not met, the overall corresponding service status information is determined as abnormal.

[0041] In one possible implementation, determining the service status information corresponding to the service evaluation index based on each of the comparison results includes:

[0042] In response to the existence of at least one of the comparison results indicating that the indicator value is greater than the indicator threshold, the service status information is determined to be abnormal.

[0043] In response to each of the comparison results indicating that the index value is not greater than the index threshold, the service status information is determined to be normal.

[0044] In the embodiments of this specification, when the improvement command issued by the target user has a high improvement requirement, that is, the sensitivity requirement of the corresponding fault detection is high, as long as one comparison result indicates that the indicator value corresponding to the acquired indicator is greater than the indicator threshold, the service status information needs to be determined as abnormal. If all comparison results indicate that the indicator value corresponding to the acquired indicator is not greater than the indicator threshold, the service status information is determined as normal.

[0045] Step 105: In response to the service status information being determined to be abnormal, maintain the service device according to the tiered service maintenance strategy and determine the recovery status of the service device.

[0046] In the embodiments of this specification, after determining the service status information of the service device, if the service status information is determined to be normal, the monitoring state continues, that is, service evaluation indicators are continuously acquired to determine the service status information. If the service status information is determined to be abnormal, the service device is maintained or downgraded according to the tiered service maintenance strategy. That is, the corresponding maintenance measures are determined according to the type of service anomaly, such as actively reducing new service requests to restore the service status to normal as quickly as possible, so as to avoid unnecessary repair time caused by restarting the service device every time an anomaly occurs. Therefore, after maintaining the service device, it is necessary to further determine the recovery status of the service device to determine whether it is necessary to initiate a rapid fault repair procedure for the service device.

[0047] In one possible implementation, the step of maintaining the service device according to a tiered service maintenance strategy in response to the service status information being determined to be abnormal includes:

[0048] In response to the service status information being determined to be abnormal, the type of service abnormality in the service status information is determined.

[0049] The target maintenance instruction is determined based on the type of service anomaly, and the service equipment is maintained according to the target maintenance instruction.

[0050] In the embodiments of this specification, when the service status information is determined to be abnormal, and maintenance is performed on the service device according to the tiered service maintenance strategy, different types of service abnormalities correspond to different maintenance measures. Therefore, it is necessary to first determine the type of service abnormality in the service status information. Then, the target maintenance instruction corresponding to the type of service abnormality is determined according to a preset maintenance instruction database or maintenance instruction model. Finally, the service device is maintained according to the target maintenance instruction.

[0051] If multiple service evaluation metrics are abnormal simultaneously, the service devices need to be maintained in order of priority. For example, when all service anomalies are present—device performance, operating environment, business services, and user experience—the maintenance should proceed as follows: first, maintain device performance; then, maintain the operating environment; next, maintain the business services; and finally, maintain the user experience.

[0052] In one possible implementation, determining the target maintenance instruction based on the type of service anomaly includes:

[0053] In response to the service anomaly being identified as a device performance anomaly, the target maintenance instruction is identified as a first maintenance instruction, which is used to terminate redundant processes and discard cached data.

[0054] In response to the service exception type being determined to be an operating environment exception, the target maintenance instruction is determined to be a second maintenance instruction, which is used to execute the rejection of network connection requests and connection pool connection requests;

[0055] In response to the service exception type being determined to be a business service exception, the target maintenance instruction is determined to be a third maintenance instruction, which is used to execute a rejection of the video stream establishment request and service request;

[0056] In response to the service exception being identified as a user experience exception, the target maintenance instruction is identified as the fourth maintenance instruction, which is used to execute a denial-of-service session establishment request.

[0057] In the embodiments of this specification, when determining the target maintenance instruction based on the type of service anomaly, if the type of service anomaly is characterized as device performance anomaly, the target maintenance instruction needs to be determined as the first maintenance instruction, that is, to terminate redundant processes and discard cached data. Specifically, resource-intensive, non-critical processes can be terminated or restarted, and basic services can be maintained by discarding business data or temporarily interrupting services to avoid service crashes.

[0058] When the service exception is determined to be an operational environment exception, the target maintenance instruction needs to be designated as the second maintenance instruction, which means rejecting network connection requests and connection pool connection requests. Specifically, network connections and connection pool connections can be restricted. By rejecting new connection requests, the system load can be reduced, service crashes can be prevented, self-recovery time can be provided, and self-protection can be achieved. Furthermore, by prioritizing the quality of core services or existing connections and proactively discarding non-critical or new requests, service degradation can be achieved.

[0059] When the service exception type is determined to be a business service exception, the target maintenance instruction needs to be designated as the third maintenance instruction, which means rejecting video stream establishment requests and service requests. Specifically, this can involve limiting the number of concurrent streaming media connections and request frequency, prioritizing basic video surveillance services, abandoning non-real-time functions such as data analysis and report generation, ensuring ongoing business and high-priority services, rejecting new access, and prioritizing the restriction of low-priority traffic.

[0060] When the service exception type is determined to be a user experience exception, the target maintenance instruction needs to be set to the fourth maintenance instruction, which is to execute a denial-of-service session establishment request. Specifically, the establishment of some new sessions can be proactively rejected, thereby protecting the user experience of existing sessions and avoiding impacting the experience of all users.

[0061] In one possible implementation, determining the recovery status of the service device includes:

[0062] The service equipment is subjected to service heartbeat detection, and the number of detection rounds is counted.

[0063] In response to the detection polling number exceeding the preset maximum polling number, the recovery status of the service device is determined to be a recovery failure.

[0064] In the embodiments of this specification, after the service status information is determined to be abnormal and maintenance is performed on the service device, it is necessary to determine the recovery status of the service device. Specifically, service heartbeat detection can be performed on the service device. First, the detection initialization settings are performed, that is, the detection frequency and the preset maximum number of polling attempts are determined. Then, service heartbeat detection is continuously performed and the number of polling attempts is counted in real time. When the detection is successful and the corresponding number of polling attempts does not exceed the preset maximum number of polling attempts, the recovery status of the service device can be determined as successful recovery. When the counted number of polling attempts exceeds the preset maximum number of polling attempts and the detection still fails, the recovery status of the service device is determined as recovery failure, and the failure needs to be repaired immediately.

[0065] Step 107: In response to the recovery status being determined as a recovery fault, determine the target repair instruction corresponding to the fault event according to the fault classification and repair strategy, and execute the target repair instruction.

[0066] In the embodiments of this specification, when the recovery status is determined to be a recovery failure, immediate fault repair is required. However, different fault repair methods will result in different average repair times. Specifically, restarting software takes less time than restarting the device, and restarting a single piece of software takes less time than restarting multiple pieces of software. Therefore, it is necessary to determine the target repair instruction corresponding to the fault time that occurred at this time based on the fault classification and repair strategy. Subsequently, only the target repair instruction needs to be executed to minimize the average repair time, thereby improving the maintainability of the video surveillance system. The fault classification and repair strategy can query the fault event based on a pre-built preset fault repair database, or it can directly generate the target repair instruction corresponding to the fault event based on a pre-built classification and repair model. This classification and repair model is trained using a large amount of historical repair record data.

[0067] In one possible implementation, in response to the recovery state being determined as a recovery fault, determining the target repair instruction corresponding to the fault event according to a fault classification and repair strategy includes:

[0068] In response to the recovery status being determined as a recovery failure, the failure event is matched with the list of failure types in the preset failure repair database to obtain the target failure type corresponding to the maximum similarity.

[0069] Based on the preset fault repair database, the target fault type is queried to obtain the target repair instruction.

[0070] In the embodiments of this specification, when the recovery status is determined to be a recovery failure, the failure event can be matched with the list of failure types in the preset failure repair database to obtain various similarity values. The maximum similarity is then determined using the extreme value method, and the target failure type corresponding to the maximum similarity is identified. The preset failure repair database is obtained by statistically analyzing a large amount of historical repair record data. Each failure type corresponds to a repair instruction; therefore, the target failure type can be queried in the preset failure repair database to obtain its corresponding target repair instruction.

[0071] As an example, when the target fault type is a connection and session failure, the repair instruction is connection reset; when the target fault type is a device software failure, the repair instruction is device fault diagnosis and isolation and restarting the device software; when the target fault type is a device failure, the repair instruction is restarting the device; and when the target fault type is a device reset failure, the repair instruction is primary / backup switchover and backup and recovery of the device.

[0072] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0073] Please refer to Figure 2 next. Figure 2 shows a schematic diagram of the structure of a maintainability improvement device for a video surveillance system provided in an embodiment of this specification. It should be noted that the maintainability improvement device for the video surveillance system shown in Figure 2 is used to perform the method of the embodiment shown in Figure 1 of this application. For ease of explanation, only the parts related to the embodiment of this application are shown. For specific technical details not disclosed, please refer to the embodiment shown in Figure 1 of this application.

[0074] As shown in Figure 2, the maintainability improvement device for this video surveillance system may include at least:

[0075] The acquisition module 201 is used to acquire service evaluation indicators corresponding to any service device in the video surveillance system. The service devices include management devices, media devices, storage devices, and processing devices. The service evaluation indicators include device performance indicators, operating environment indicators, business service indicators, and user experience indicators.

[0076] The determination module 202 is used to determine the service status information corresponding to the service evaluation indicators based on the multi-level indicator judgment method;

[0077] The maintenance module 203 is used to perform maintenance on the service device according to the layered service maintenance strategy in response to the service status information being determined to be abnormal, and to determine the recovery status of the service device.

[0078] The repair module 204 is used to respond to the recovery status being determined to be a recovery fault, determine the target repair instruction corresponding to the fault event according to the fault classification repair strategy, and execute the target repair instruction.

[0079] In one possible implementation, the determining module 202 is specifically used for:

[0080] Determine the threshold values ​​for the equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators, respectively.

[0081] The indicator values ​​corresponding to the device performance indicators, operating environment indicators, business service indicators, and user experience indicators are compared with the threshold values ​​of each indicator to obtain the comparison results.

[0082] The service status information corresponding to the service evaluation indicators is determined based on the comparison results.

[0083] In one possible implementation, the determining module 202 is further configured to:

[0084] In response to the existence of at least one of the comparison results indicating that the indicator value is greater than the indicator threshold, the service status information is determined to be abnormal.

[0085] In response to each of the comparison results indicating that the index value is not greater than the index threshold, the service status information is determined to be normal.

[0086] In one possible implementation, the maintenance module 203 is specifically used for:

[0087] In response to the service status information being determined to be abnormal, the type of service abnormality in the service status information is determined.

[0088] The target maintenance instruction is determined based on the type of service anomaly, and the service equipment is maintained according to the target maintenance instruction.

[0089] In one possible implementation, the maintenance module 203 is further configured to:

[0090] In response to the service anomaly being identified as a device performance anomaly, the target maintenance instruction is identified as a first maintenance instruction, which is used to terminate redundant processes and discard cached data.

[0091] In response to the service exception type being determined to be an operating environment exception, the target maintenance instruction is determined to be a second maintenance instruction, which is used to execute the rejection of network connection requests and connection pool connection requests;

[0092] In response to the service exception type being determined to be a business service exception, the target maintenance instruction is determined to be a third maintenance instruction, which is used to execute a rejection of the video stream establishment request and service request;

[0093] In response to the service exception being identified as a user experience exception, the target maintenance instruction is identified as the fourth maintenance instruction, which is used to execute a denial-of-service session establishment request.

[0094] In one possible implementation, the maintenance module 203 is further configured to:

[0095] The service equipment is subjected to service heartbeat detection, and the number of detection rounds is counted.

[0096] In response to the detection polling number exceeding the preset maximum polling number, the recovery status of the service device is determined to be a recovery failure.

[0097] In one possible implementation, the repair module 204 is specifically used for:

[0098] In response to the recovery status being determined as a recovery failure, the failure event is matched with the list of failure types in the preset failure repair database to obtain the target failure type corresponding to the maximum similarity.

[0099] Based on the preset fault repair database, the target fault type is queried to obtain the target repair instruction.

[0100] Those skilled in the art will clearly understand that the technical solutions of the embodiments of this application can be implemented by means of software and / or hardware. In this specification, "unit" and "module" refer to software and / or hardware that can independently complete or cooperate with other components to complete a specific function, wherein the hardware may be, for example, a field-programmable gate array (FPGA), an integrated circuit (IC), etc.

[0101] Each processing unit and / or module in the embodiments of this application can be implemented by an analog circuit that implements the functions described in the embodiments of this application, or by software that executes the functions described in the embodiments of this application.

[0102] Please refer to Figure 3 next, which shows a schematic diagram of the structure of an electronic device provided in an embodiment of this specification.

[0103] As shown in Figure 3, the electronic device 300 may include at least one device processor 301, at least one network interface 304, user interface 303, memory 305, and at least one communication bus 302.

[0104] The communication bus 302 can be used to realize the connection and communication of the above components.

[0105] The user interface 303 may include buttons, and the optional user interface may also include a standard wired interface or a wireless interface.

[0106] The network interface 304 may include, but is not limited to, Bluetooth modules, NFC modules, Wi-Fi modules, etc.

[0107] The device processor 301 may include one or more processing cores. The device processor 301 connects to various parts within the electronic device 300 using various interfaces and lines. It executes various functions and processes data of the electronic device 300 by running or executing instructions, programs, code sets, or instruction sets stored in the memory 305, and by calling data stored in the memory 305. Optionally, the device processor 301 may be implemented using at least one hardware form of DSP, FPGA, or PLA. The device processor 301 may integrate one or more of the following: CPU, GPU, and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required for display; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the device processor 301 and may be implemented as a separate chip.

[0108] The memory 305 may include RAM or ROM. Optionally, the memory 305 may include a non-transitory computer-readable medium. The memory 305 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 305 may also be at least one storage device located remotely from the aforementioned device processor 301. As shown in FIG3, the memory 305, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and program instructions.

[0109] Specifically, the device processor 301 can be used to call the video surveillance system maintainability improvement application stored in the memory 305, and specifically perform the following operations:

[0110] For any service device in the video surveillance system, obtain the service evaluation index corresponding to the service device. The service device includes management device, media device, storage device and processing device. The service evaluation index includes device performance index, operating environment index, business service index and user experience index.

[0111] The service status information corresponding to the service evaluation indicators is determined based on a multi-level indicator judgment method.

[0112] In response to the service status information being determined to be abnormal, the service device is maintained according to the tiered service maintenance strategy, and the recovery status of the service device is determined.

[0113] In response to the recovery status being determined to be a recovery failure, the target repair instruction corresponding to the failure event is determined according to the failure classification and repair strategy, and the target repair instruction is executed.

[0114] As an optional embodiment of this specification, the step of determining the service status information corresponding to the service evaluation index based on the multi-level index judgment method includes:

[0115] Determine the threshold values ​​for the equipment performance indicators, operating environment indicators, business service indicators, and user experience indicators, respectively.

[0116] The indicator values ​​corresponding to the device performance indicators, operating environment indicators, business service indicators, and user experience indicators are compared with the threshold values ​​of each indicator to obtain the comparison results.

[0117] The service status information corresponding to the service evaluation indicators is determined based on the comparison results.

[0118] As an optional embodiment of this specification, determining the service status information corresponding to the service evaluation index based on each comparison result includes:

[0119] In response to the existence of at least one of the comparison results indicating that the indicator value is greater than the indicator threshold, the service status information is determined to be abnormal.

[0120] In response to each of the comparison results indicating that the index value is not greater than the index threshold, the service status information is determined to be normal.

[0121] As an optional embodiment of this specification, the step of maintaining the service device according to the tiered service maintenance strategy in response to the service status information being determined to be abnormal includes:

[0122] In response to the service status information being determined to be abnormal, the type of service abnormality in the service status information is determined.

[0123] The target maintenance instruction is determined based on the type of service anomaly, and the service equipment is maintained according to the target maintenance instruction.

[0124] As an optional embodiment of this specification, the step of determining the target maintenance instruction based on the type of service anomaly includes:

[0125] In response to the service anomaly being identified as a device performance anomaly, the target maintenance instruction is identified as a first maintenance instruction, which is used to terminate redundant processes and discard cached data.

[0126] In response to the service exception type being determined to be an operating environment exception, the target maintenance instruction is determined to be a second maintenance instruction, which is used to execute the rejection of network connection requests and connection pool connection requests;

[0127] In response to the service exception type being determined to be a business service exception, the target maintenance instruction is determined to be a third maintenance instruction, which is used to execute a rejection of the video stream establishment request and service request;

[0128] In response to the service exception being identified as a user experience exception, the target maintenance instruction is identified as the fourth maintenance instruction, which is used to execute a denial-of-service session establishment request.

[0129] As an optional embodiment of this specification, determining the recovery status of the service device includes:

[0130] The service equipment is subjected to service heartbeat detection, and the number of detection rounds is counted.

[0131] In response to the detection polling number exceeding the preset maximum polling number, the recovery status of the service device is determined to be a recovery failure.

[0132] As an optional embodiment of this specification, the step of determining the target repair instruction corresponding to the fault event according to the fault classification and repair strategy in response to the recovery state being determined as a recovery fault includes:

[0133] In response to the recovery status being determined as a recovery failure, the failure event is matched with the list of failure types in the preset failure repair database to obtain the target failure type corresponding to the maximum similarity.

[0134] Based on the preset fault repair database, the target fault type is queried to obtain the target repair instruction.

[0135] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.

[0136] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0137] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0138] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.

[0139] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0140] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0141] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0142] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0143] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

Claims

1. A method for improving the maintainability of a video surveillance system, characterized in that, The method includes: for any service device in the video surveillance system, acquiring service evaluation indicators corresponding to the service device, wherein the service device includes management devices, media devices, storage devices, and processing devices, and the service evaluation indicators include device performance indicators, operating environment indicators, business service indicators, and user experience indicators; determining service status information corresponding to the service evaluation indicators based on a multi-level indicator judgment method; in response to the service status information being determined to be abnormal, maintaining the service device according to a layered service maintenance strategy, and determining the recovery status of the service device; in response to the recovery status being determined to be a recovery failure, determining the target repair instruction corresponding to the failure event according to a failure classification and repair strategy, and executing the target repair instruction.

2. The method according to claim 1, characterized in that, The method of determining the service status information corresponding to the service evaluation index based on the multi-level index judgment method includes: determining the index thresholds corresponding to the equipment performance index, operating environment index, business service index and user experience index respectively; comparing the index values ​​corresponding to the equipment performance index, operating environment index, business service index and user experience index with each index threshold respectively to obtain each comparison result; and determining the service status information corresponding to the service evaluation index based on each comparison result.

3. The method according to claim 2, characterized in that, The step of determining the service status information corresponding to the service evaluation index based on each of the comparison results includes: in response to at least one of the comparison results indicating that the index value is greater than the index threshold, determining the service status information as abnormal; and in response to each of the comparison results indicating that the index value is not greater than the index threshold, determining the service status information as normal.

4. The method according to claim 1, characterized in that, The step of responding to the service status information being determined to be abnormal and maintaining the service device according to the tiered service maintenance strategy includes: responding to the service status information being determined to be abnormal, determining the type of service abnormality in the service status information; determining a target maintenance instruction based on the type of service abnormality, and maintaining the service device according to the target maintenance instruction.

5. The method according to claim 4, characterized in that, The step of determining the target maintenance instruction based on the service anomaly type includes: in response to the service anomaly type being determined to be a device performance anomaly, determining the target maintenance instruction as a first maintenance instruction, the first maintenance instruction being used to terminate redundant processes and discard cached data; in response to the service anomaly type being determined to be an operating environment anomaly, determining the target maintenance instruction as a second maintenance instruction, the second maintenance instruction being used to reject network connection requests and connection pool connection requests; in response to the service anomaly type being determined to be a business service anomaly, determining the target maintenance instruction as a third maintenance instruction, the third maintenance instruction being used to reject video stream establishment requests and service requests; and in response to the service anomaly type being determined to be a user experience anomaly, determining the target maintenance instruction as a fourth maintenance instruction, the fourth maintenance instruction being used to reject service session establishment requests.

6. The method according to claim 1, characterized in that, Determining the recovery status of the service device includes: performing service heartbeat detection on the service device and counting the number of detection rounds; in response to the number of detection rounds exceeding a preset maximum number of rounds, determining the recovery status of the service device as a recovery failure.

7. The method according to claim 1, characterized in that, The step of determining the target repair instruction corresponding to the fault event based on the fault classification and repair strategy in response to the recovery state being determined as a recovery fault includes: matching the fault event with a list of fault types in a preset fault repair database to obtain the target fault type corresponding to the maximum similarity; and querying the target fault type based on the preset fault repair database to obtain the target repair instruction.

8. A maintainability improvement device for a video surveillance system, characterized in that, The device includes: an acquisition module, configured to acquire service evaluation indicators corresponding to any service device in the video surveillance system, wherein the service device includes management devices, media devices, storage devices, and processing devices, and the service evaluation indicators include device performance indicators, operating environment indicators, business service indicators, and user experience indicators; a determination module, configured to determine service status information corresponding to the service evaluation indicators based on a multi-level indicator judgment method; a maintenance module, configured to maintain the service device according to a layered service maintenance strategy in response to the service status information being determined to be abnormal, and determine the recovery status of the service device; and a repair module, configured to determine the target repair instruction corresponding to the fault event according to a fault classification repair strategy in response to the recovery status being determined to be a recovery fault, and execute the target repair instruction.

9. 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, it implements the steps of the method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer or processor, cause the computer or processor to perform the steps of the method as described in any one of claims 1-7.

Images