A remote maintenance method for monitoring system operation state

Abstract

The application relates to the field of remote operation and maintenance of a video monitoring system, and discloses a monitoring system operation state remote maintenance method; the method establishes a video monitoring channel link model comprising a camera end, a streaming media forwarding end, a video recording storage end and a playing end; different node state data are collected and video link state fingerprints are generated; the state fingerprints of different nodes of the same channel are compared for consistency to determine an abnormal link; a remote maintenance action package is generated according to the abnormal link. When the maintenance action can cause short-time interruption of a main code stream, a shadow verification channel is established based on an auxiliary code stream and pre-verification is carried out; when the pre-verification is passed and a key monitoring area is covered by an adjacent blind supplement channel, the remote maintenance action package is executed; after the maintenance, verification is carried out in combination with real-time preview, video playback and playing end decoding state, and rollback is executed when the verification is not passed. The application can realize video link abnormality positioning and controlled remote maintenance.

Description

Technical Field

[0001] This invention relates to the field of remote operation and maintenance of video surveillance systems, and specifically to a method for remotely maintaining the operational status of a surveillance system. Background Technology

[0002] Video surveillance systems typically consist of front-end cameras, streaming media forwarding servers, video storage devices, client playback terminals, and corresponding management platforms. The video stream undergoes multiple stages, including acquisition and encoding, network transmission, streaming media forwarding, recording and writing, index generation, and playback decoding, before real-time preview and playback can be achieved. As the number of monitoring points increases, the maintenance of video surveillance system operations is gradually shifting from manual inspection to remote inspection. Current technologies often detect anomalies through online device testing, network connectivity testing, video quality testing, black screen detection, stuttering detection, and missing recording detection, and then handle these anomalies through alarms, work orders, or remote restarts.

[0003] However, in actual operation, when anomalies such as black screens, stuttering, missing recordings, or playback failures occur on the same video surveillance channel, the causes may stem from encoding errors at the camera end, streaming media forwarding errors, recording storage indexing errors, or decoding errors at the playback end. Existing remote maintenance methods often focus on determining whether the video image is abnormal or whether the device is online, making it difficult to accurately pinpoint the abnormal link based on the state differences of the same video stream in each stage of acquisition, forwarding, storage, and playback. When the source of the anomaly cannot be distinguished, it is easy to resort to crude maintenance actions such as directly restarting the camera, switching forwarding nodes, or refreshing the storage service, leading to a reliance on experience in troubleshooting and the possibility of misoperation or repeated operations.

[0004] Furthermore, video surveillance systems typically undertake continuous monitoring tasks, especially in critical areas such as entrances and exits, passageways, equipment rooms, and warehouses. During remote maintenance, directly performing operations such as restarting, switching forwarding, or refreshing storage on the main stream channel may cause short-term monitoring interruptions or recording gaps. While existing technologies can detect some video anomalies and handle them remotely, they lack a closed-loop control mechanism to verify auxiliary streams, the coverage status of adjacent filler channels, and the real-time preview, recording playback, and decoding status after maintenance. Therefore, accurately locating the abnormal link when a video surveillance system malfunctions and performing remote maintenance without affecting the continuous coverage of critical monitoring areas is a pressing technical problem that needs to be solved in this field. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a remote maintenance method for monitoring the operational status of a system, thereby resolving the technical problems existing in the prior art.

[0006] The above-mentioned technical objective of the present invention is achieved through the following technical solution: A method for remote maintenance of a monitoring system's operational status includes the following steps: S1. Establish a link model for the video surveillance channel. The link model includes the camera end, streaming media forwarding end, video recording storage end, and playback end. Record the main stream address, secondary stream address, key monitoring area, and adjacent blind spot filling channels corresponding to the video surveillance channel. S2. Collect status data of different nodes in the link model of the same video surveillance channel, and generate video link status fingerprints of the corresponding nodes based on the status data; S3. Perform consistency comparison of video link status fingerprints at different nodes of the same video surveillance channel, and determine the abnormal links based on the comparison results; S4. Generate a remote maintenance action package based on the abnormal process. The remote maintenance action package includes maintenance actions and corresponding verification conditions. S5. When the remote maintenance action package contains maintenance actions that will cause a short interruption of the main stream, a shadow verification channel is established based on the secondary stream address, and a pre-verification operation corresponding to the maintenance action is performed on the shadow verification channel. S6. After the shadow verification channel meets the verification conditions, determine whether the key monitoring area is covered by the adjacent blind-filling channel whose video link status fingerprint meets the normal conditions; if the coverage conditions are met, execute the remote maintenance action package for the video monitoring channel corresponding to the main stream; if the coverage conditions are not met, execute the non-interrupted recovery action or delay the execution of the maintenance action that will cause a short interruption of the main stream. S7. After the remote maintenance action package is executed, the video link status fingerprint of the video monitoring channel is collected again, and the remote maintenance action package is judged to meet the verification conditions in combination with the real-time preview status, recording playback status and playback terminal decoding status; if the verification conditions are not met, the rollback operation is executed.

[0007] Preferably, in S1, the link model is established according to the video surveillance channel number; The link model also records the device identifier, encoding parameters, and access address of the camera end; the forwarding node identifier, streaming protocol, and forwarding address of the streaming media forwarding end; the recording plan, recording file storage path, and recording index address of the recording storage end; and the client identifier, decoding method, and playback request address of the playback end.

[0008] Preferably, in S2, status data of at least three nodes of the same video surveillance channel are collected at the camera end, streaming media forwarding end, video recording storage end, and playback end; The status data includes the timestamp of the encoded frame, keyframe interval, output bitrate and frame sequence number output by the camera end, the sequence number of the transmission packet received by the streaming media forwarding end, the first frame response time and forwarding bitrate, the start and end time of the video segment generated by the video storage end, the length of the video file and the video index identifier, and the timestamp of the decoded frame, the first frame display time, the decoding error code and the playback interruption record generated by the playback end.

[0009] Preferably, in S2, the video link status fingerprint includes key frame timestamp sequence, bit rate fluctuation value, transmission sequence continuity, inter-frame content features, recording index continuity, and playback end decoding status. When generating video link status fingerprints, the status data collected by the same video surveillance channel within the same sampling time period are normalized according to the node position, and the normalized status data is bound to the corresponding video surveillance channel number, node position and sampling time period.

[0010] Preferably, in S3, the abnormal process includes a data acquisition and encoding process, a transmission and forwarding process, a video recording and storage process, and a playback and decoding process; When the video link status fingerprint at the camera end is abnormal, and the video link status fingerprints at the streaming media forwarding end, video recording storage end, and playback end are also abnormal synchronously with the camera end, the abnormal link is identified as the acquisition and encoding link. When the video link status fingerprint at the camera end is normal, but the video link status fingerprint at the streaming media forwarding end is abnormal, the abnormal link is identified as the transmission and forwarding link. When the video link status fingerprints at the camera end and the streaming media forwarding end are normal, but the video link status fingerprint at the recording storage end is abnormal, the abnormal link is identified as the recording storage link. When the video link status fingerprints at the camera end, streaming media forwarding end, and video recording storage end are normal, but the video link status fingerprint at the playback end is abnormal, the abnormal link is identified as the playback decoding link.

[0011] Preferably, when determining that the video link status fingerprint is abnormal, the key frame timestamp sequence, bit rate fluctuation value, transmission sequence continuity, recording index continuity, and playback end decoding status are judged respectively. When any of the following situations occur, such as missing keyframe timestamp sequences, bitrate fluctuations exceeding the preset bitrate range, breaks in transmission sequence continuity, missing recording index continuity, or decoding status at the playback end containing decoding error codes indicating decoding failure, the video link status fingerprint of the corresponding node is determined to be abnormal.

[0012] Preferably, in S4, the remote maintenance action package further includes action object, action type, execution order, preconditions, and rollback conditions; When the abnormal step is the acquisition and encoding step, the action types include rollback of encoding parameters, switching of auxiliary bitstream, and camera soft restart; When the abnormal link is the transmission and forwarding link, the action types include refreshing the streaming session, switching the streaming media forwarding node, and rebuilding the forwarding cache; When the abnormal process is the video recording storage process, the action types include verifying video segments, rebuilding the video recording index, and refreshing the storage mount. When the abnormal process is the playback decoding process, the action types include resetting the playback session, clearing the decoding cache, and switching decoding parameters.

[0013] Preferably, in S5, when establishing the shadow verification channel, a streaming request corresponding to the current sampling time period of the main stream is initiated to the camera end according to the auxiliary stream address. The auxiliary stream is connected to the streaming media verification node to form a verification forwarding stream, the verification forwarding stream is connected to the recording verification node to form a verification recording segment, and the verification forwarding stream is connected to the playback verification node to form a verification playback stream. The streaming media verification node, recording verification node, and playback verification node are independent of the streaming media forwarding end, recording storage end, and playback end corresponding to the main stream, respectively.

[0014] Preferably, in S6, when determining whether the key monitoring area is covered by an adjacent blind-filling channel whose video link status fingerprint meets the normal conditions, the area identifier and adjacent blind-filling channel number corresponding to the key monitoring area are read, and the video link status fingerprint of the adjacent blind-filling channel in the current sampling time period is obtained. When the video link status fingerprint of the adjacent blind spot filling channel meets the normal conditions, and the monitoring area identifier of the adjacent blind spot filling channel contains the area identifier of the key monitoring area, the coverage condition is determined to be met.

[0015] Preferably, in S7, after the remote maintenance action package is executed, the video link status fingerprint of the real-time preview stream, the video link status fingerprint of the recording playback stream, and the video link status fingerprint of the playback end are obtained respectively. When the video link status fingerprints of the real-time preview stream, video playback stream, and playback terminal after maintenance all match the historical normal fingerprints of the corresponding nodes, and the start and end times of the recording segments in the video playback status are continuous with the execution time of the remote maintenance action package, it is determined that the remote maintenance action package has passed verification. If the above conditions are not met, it is determined that the remote maintenance action package verification has failed, and the rollback operation is performed according to the rollback conditions in the remote maintenance action package.

[0016] In summary, the present invention has the following main beneficial effects: By establishing a link model for the same video surveillance channel, including the camera end, streaming media forwarding end, video storage end, and playback end, and generating video link status fingerprints after collecting status data at different link nodes, the remote maintenance platform can compare the status differences of the same video stream during acquisition, forwarding, storage, and playback based on link status such as key frame timestamp sequence, bitrate fluctuation, transmission sequence continuity, video index continuity, and playback end decoding status. This achieves the effect of further locating apparent anomalies such as black screen, stuttering, missing recordings, and playback failures to the acquisition encoding stage, transmission forwarding stage, video storage stage, or playback decoding stage, avoiding the problem of inaccurate fault identification caused by general alarms based solely on picture quality or equipment online status.

[0017] By generating remote maintenance action packages based on abnormal processes, including action objects, action types, execution order, preconditions, verification conditions, and rollback conditions, and when maintenance actions may cause a short-term interruption of the main stream, a shadow verification channel is first established based on the secondary stream address. This allows the corresponding maintenance actions to be applied first to the verification forwarding stream, verification recording segment, and verification playback stream, which are independent of the main stream service. This achieves the effect of pre-verifying whether the maintenance actions can restore the video link status to normal without directly affecting the real-time preview and recording storage of the main stream. This avoids the risk that the monitoring service will be interrupted and cannot be recovered after directly restarting the camera, switching the forwarding node, or refreshing the storage mount.

[0018] After the shadow verification channel meets the verification conditions, it is then determined whether the key monitoring area is covered by an adjacent blind-filling channel whose video link status fingerprint meets the normal conditions. Only when the coverage conditions are met is the remote maintenance action package executed on the video monitoring channel corresponding to the main stream executed. At the same time, after the maintenance is completed, a closed-loop verification is performed by combining the real-time preview status, video playback status, and playback terminal decoding status. This achieves the effect of balancing fault recovery and the continuity of monitoring of key areas during remote maintenance. When the real-time preview, video playback, or playback terminal decoding status does not meet the verification conditions after maintenance, the encoding parameters, forwarding nodes, decoding parameters, or storage status before maintenance can be restored according to the rollback conditions, thereby avoiding the expansion of the original abnormal scope by the remote maintenance action. Attached Figure Description

[0019] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] Example 1 refer to Figure 1 A remote maintenance method for monitoring the operating status of a system includes the following steps: S1. Establish a link model for the video surveillance channel. The link model includes the camera end, streaming media forwarding end, video recording storage end, and playback end. Record the main stream address, secondary stream address, key monitoring area, and adjacent blind spot filling channels corresponding to the video surveillance channel. S2. Collect status data of different nodes in the link model of the same video surveillance channel, and generate video link status fingerprints of the corresponding nodes based on the status data; S3. Perform consistency comparison of video link status fingerprints at different nodes of the same video surveillance channel, and determine the abnormal links based on the comparison results; S4. Generate a remote maintenance action package based on the abnormal process. The remote maintenance action package includes maintenance actions and corresponding verification conditions. S5. When the remote maintenance action package contains maintenance actions that will cause a short interruption of the main stream, a shadow verification channel is established based on the secondary stream address, and a pre-verification operation corresponding to the maintenance action is performed on the shadow verification channel. S6. After the shadow verification channel meets the verification conditions, determine whether the key monitoring area is covered by the adjacent blind-filling channel whose video link status fingerprint meets the normal conditions; if the coverage conditions are met, execute the remote maintenance action package for the video monitoring channel corresponding to the main stream; if the coverage conditions are not met, execute the non-interrupted recovery action or delay the execution of the maintenance action that will cause a short interruption of the main stream. S7. After the remote maintenance action package is executed, the video link status fingerprint of the video monitoring channel is collected again, and the remote maintenance action package is judged to meet the verification conditions in combination with the real-time preview status, recording playback status and playback terminal decoding status; if the verification conditions are not met, the rollback operation is executed.

[0022] This application applies to video surveillance systems including camera terminals, streaming media forwarding terminals, video recording storage terminals, playback terminals, and remote maintenance platforms. The camera terminal outputs the main and secondary streams; the streaming media forwarding terminal receives and forwards the video stream; the video recording storage terminal stores the video stream according to the recording plan and generates a recording index; the playback terminal initiates real-time preview requests or video playback requests and performs decoding and display; the remote maintenance platform establishes a link model, collects status data, generates video link status fingerprints, locates abnormal links, generates remote maintenance action packages, establishes shadow verification channels, determines the coverage conditions of adjacent blind spot filling channels, and performs verification and rollback after the maintenance actions are executed.

[0023] In this embodiment, the video surveillance channel refers to a monitoring service link formed by the video stream output from a single camera sequentially passing through a streaming media forwarding end, a video recording storage end, and a playback end. The same camera is configured with a primary stream address and a secondary stream address. The primary stream is used for normal real-time preview and video recording storage, while the secondary stream is used to establish a shadow verification channel or temporarily carry preview requests without interrupting recovery operations.

[0024] The remote maintenance platform establishes a link model for each video surveillance channel. The link model uses the video surveillance channel number as an index to record the correspondence between the camera end, streaming media forwarding end, video storage end, and playback end.

[0025] The link model records the camera's device identifier, device IP address, access port, main stream address, secondary stream address, encoding format, resolution, frame rate, keyframe interval, and bitrate configuration; it records the streaming media forwarding end's forwarding node identifier, streaming protocol, forwarding address, forwarding session identifier, main stream forwarding path, and secondary stream forwarding path; it records the video storage end's recording plan, video file storage path, video file naming rules, video segment duration, video index address, and video playback interface address; and it records the playback end's client identifier, playback request address, decoding method, playback session identifier, and playback end status feedback interface.

[0026] The link model also records the key monitoring areas and adjacent blind-spot fill channels corresponding to the video surveillance channels. Key monitoring areas refer to areas configured to maintain surveillance coverage during video surveillance system deployment, such as entrances / exits, equipment room doors, platform boundaries, passageway intersections, warehouse passageways, or checkout areas. Adjacent blind-spot fill channels are video surveillance channels whose monitoring areas have a pre-configured coverage relationship with the key monitoring areas. This coverage relationship can be determined based on camera installation location, field of view, monitoring area identifier, area coordinate range, or manually calibrated area mapping relationships, and is stored in the link model of the remote maintenance platform.

[0027] During operation, the remote maintenance platform directly calls the region mapping relationship in the link model to determine whether the blind spot coverage conditions are met, without recalculating the camera's field of view during operation. This avoids relying on temporary image recognition results for blind spot channel determination and ensures that the source of adjacent blind spot channels is clear.

[0028] The remote maintenance platform collects status data from video surveillance channels according to the inspection cycle. The inspection cycle is configured by the video surveillance system based on the monitoring level, system scale, network bandwidth, and equipment performance. Key video surveillance channels are configured with shorter inspection cycles, while ordinary video surveillance channels are configured with longer inspection cycles. The specific cycle is configured according to the actual monitoring scenario during system deployment.

[0029] Within an inspection cycle, the remote maintenance platform collects status data from at least three nodes of the same video surveillance channel: the camera end, the streaming media forwarding end, the video recording storage end, and the playback end. Collecting data from at least three nodes is essential to establish a link-level comparison relationship, enabling the remote maintenance platform to distinguish whether an anomaly occurred during the acquisition and encoding stage, the transmission and forwarding stage, the video recording storage stage, or the playback and decoding stage.

[0030] Camera-side status data includes encoded frame timestamps, keyframe intervals, output bitrate, frame sequence number, main stream output status, and secondary stream output status. This data can be obtained through the camera SDK, ONVIF interface, GB / T28181 device status reporting information, or collected by the edge gateway.

[0031] Streaming media forwarding endpoint status data includes packet sequence number, first frame response time, forwarding bitrate, forwarding session status, forwarding buffer status, and forwarding endpoint error codes. This data can be obtained from the streaming media server's session logs, RTP sequence statistics, forwarding service interface, or streaming media proxy components.

[0032] The video storage status data includes the start and end times of the video segments, the length of the video file, the video index identifier, the video file write status, the continuity of the video index, and the playback interface response status. This data can be provided by a video storage server, network video recorder, centralized video storage device, cloud storage platform, or video index database.

[0033] Playback client status data includes decoding frame timestamps, first frame display time, playback interruption records, decoding error codes, playback client buffer status, and records of playback client black screens or freezes. This data can be collected by the client player SDK, web player status interface, decoding component logs, or playback service proxy components.

[0034] The above status data all originate from the encoding, transmission, storage, and playback data generated during the operation of the video surveillance system. It does not require changes to the camera hardware structure, nor does it rely on a general image quality scoring model.

[0035] The remote maintenance platform normalizes the status data collected from different nodes of the same video surveillance channel within the same sampling time period and generates a video link status fingerprint for the corresponding node. The sampling time period refers to the time window used to collect status data during an inspection process, and this time window corresponds to the status acquisition process of the main stream and the auxiliary stream.

[0036] Video link status fingerprints are used to characterize the link status of the same video surveillance channel at a single node location. To enable consistent comparisons between different nodes, the remote maintenance platform converts the status data collected from different nodes into a fingerprint structure containing fields of the same category.

[0037] In this embodiment, the video link status fingerprint includes at least the key frame timestamp sequence, bit rate fluctuation value, transmission sequence continuity, inter-frame content features, recording index continuity, and playback end decoding status.

[0038] The keyframe timestamp sequence is formed by arranging the timestamps corresponding to each keyframe within the sampling time period in chronological order. It is used to determine whether there are missing keyframes in the video stream. The keyframe timestamp sequence corresponds to the keyframe interval configured in the camera's encoding parameters. When the keyframe timestamps and keyframe intervals within the sampling time period are inconsistent, and this is not a brief jitter allowed by the protocol, the remote maintenance platform will determine the keyframe timestamp sequence as abnormal.

[0039] The bitrate fluctuation value is obtained by comparing the actual bitrate within the sampling period with the historical normal bitrate of the corresponding node of the video surveillance channel. The historical normal bitrate is derived from the historical sampling period of the video surveillance channel when there were no device offline alarms, no streaming failure alarms, no recording loss alarms, no playback decoding failure alarms, and no remote maintenance actions were performed. The bitrate fluctuation value is not determined using a uniform fixed value, but rather by combining the video surveillance channel's own encoding configuration and historical normal operation data.

[0040] Transmission sequence continuity is determined by RTP sequence number, video frame sequence number, or forwarding packet sequence number. When there are no non-protocol-allowed breakpoints between adjacent sequence numbers within the sampling time period, the transmission sequence continuity is recorded as continuous; when there is packet loss, duplicate packets, or sequence breakage, the transmission sequence continuity is recorded as abnormal.

[0041] Inter-frame content features are obtained by extracting one of the following from keyframes or interval frames within the sampling time period: grayscale histogram, edge distribution, or perceptual hash. These inter-frame content features are not used to identify specific targets in the image, nor are they used to evaluate image quality levels. Instead, they are used to determine whether the video content of the same video surveillance channel remains consistent across different link nodes. For example, within the same sampling time period, the inter-frame content features corresponding to the camera end, streaming media forwarding end, and playback end should be consistent. If the content features at the camera end are normal, but the corresponding features at the playback end remain unchanged for a long period, the decoding status of the playback end can be combined to determine whether the playback end is frozen.

[0042] Video index continuity is used to characterize whether the video storage end generates video segments and video indexes corresponding to the video stream time within the sampling period. For non-recording nodes, this field is not used as a basis for judging the node's own anomalies; when judging the video storage link, the video index continuity of the video storage end is used as the basis.

[0043] The playback device's decoding status is used to characterize whether there are decoding failures, first frame timeouts, playback interruptions, persistent black screens, or persistent frozen frames. The playback device's decoding status is jointly determined by the playback device's error codes, decoding logs, and playback device display status. Only error codes indicating decoding failures, decoding timeouts, or playback interruptions are considered as exceptions.

[0044] When generating a video link status fingerprint, the remote maintenance platform binds the above fields with the corresponding video surveillance channel number, node location, and sampling time period. This binding relationship determines which video surveillance channel, which link node, and which sampling time period a given video link status fingerprint belongs to.

[0045] The remote maintenance platform establishes historical normal fingerprint sets based on the video surveillance channel number and node location. These sets are formed from sampling periods during which the video surveillance channels were in normal operating condition. Normal operating condition means that no device offline alarms, streaming failure alarms, missing recording alarms, or playback decoding failure alarms were generated during that sampling period, and no remote maintenance actions were performed during that period.

[0046] The remote maintenance platform writes the video link status fingerprints corresponding to multiple sampling time periods that meet the above conditions into the historical normal fingerprint set. When an abnormal alarm occurs or a remote maintenance action is performed in a subsequent sampling time period, the video link status fingerprint corresponding to that sampling time period is not written into the historical normal fingerprint set. The historical normal fingerprint set can be updated on a rolling basis according to the system operation cycle. During the update, sampling time periods in which abnormal events occurred are removed to prevent abnormal data from entering the normal range.

[0047] In this embodiment, the normal conditions for the video link status fingerprint are as follows: the key frame timestamp sequence does not contain any missing key frames that are inconsistent with the encoding parameters of the video monitoring channel; the bit rate fluctuation value does not exceed the bit rate fluctuation threshold determined by the historical normal fingerprint set; the transmission sequence continuity does not contain any sequence breaks that are not allowed by the protocol; the recording index continuity can cover the sampling time period and support the recording playback interface access; and the decoding status of the playback end does not contain error codes indicating decoding failure, first frame display timeout, or playback interruption.

[0048] For nodes that do not contain video storage or playback fields, the default fields are not used as the basis for anomaly determination when judging the node's own status; when judging the video storage or playback decoding stages, the corresponding fields of the video storage or playback stages are called for judgment.

[0049] The preset bitrate range is determined jointly by the target bitrate range configured at the camera end and the historical normal fingerprint set. For video surveillance channels with fixed bitrate encoding, the preset bitrate range is based on the target bitrate and allowable fluctuation range in the camera-end encoding parameters, and is corrected by combining historical normal operation data. For video surveillance channels with variable bitrate encoding, the preset bitrate range is determined by the bitrate distribution range of the video surveillance channel at the corresponding node in the historical normal fingerprint set. The above preset bitrate range is generated by the remote maintenance platform based on the equipment configuration and historical normal operation data of the same video surveillance channel, and does not use fixed empirical values ​​unrelated to the channel.

[0050] The remote maintenance platform performs consistency comparisons on the video link status fingerprints of the same video surveillance channel at different nodes, and identifies abnormal links based on the comparison results. Abnormal links include the acquisition and encoding link, the transmission and forwarding link, the recording and storage link, and the playback and decoding link.

[0051] When the video link status fingerprint at the camera end is abnormal, and the video link status fingerprints at the streaming media forwarding end, video storage end, and playback end are also abnormal synchronously with the camera end, the remote maintenance platform identifies the abnormal link as the acquisition and encoding stage. For example, if the camera end has already shown missing key frame timestamp sequences or abnormal bitrate fluctuations, and subsequently the streaming media forwarding end, video storage end, and playback end show corresponding transmission sequence breaks, missing video segments, or playback end freezes, it indicates that the source of the abnormality is located in the camera end output stage.

[0052] In this embodiment, "camera-end synchronization anomaly" refers to a situation where, after the camera experiences a missing keyframe timestamp sequence, abnormal bitrate fluctuation, or abnormal inter-frame content characteristics during the current sampling time period, the streaming media forwarding end, video storage end, or playback end experiences a transmission sequence breakpoint, missing video segment, playback end freeze, or decoding failure corresponding to the camera-end anomaly within the same sampling time period, or within an adjacent sampling time period after considering video buffer latency. The video buffer latency is determined by the streaming media buffer configuration and playback end buffer configuration of the video surveillance system and stored in the link model.

[0053] When the video link status fingerprint at the camera end meets the normal conditions, but the video link status fingerprint at the streaming media forwarding end is abnormal, the remote maintenance platform identifies the abnormal link as the transmission and forwarding link. For example, if the main stream output at the camera end is normal and the key frame timestamp sequence is continuous, but the streaming media forwarding end experiences a transmission sequence break, abnormal first frame response time, or forwarding session error code, then the abnormality occurs in the transmission and forwarding link.

[0054] When the video link status fingerprints at both the camera and streaming media forwarding ends meet normal conditions, but the video link status fingerprint at the recording storage end is abnormal, the remote maintenance platform identifies the abnormal link as the recording storage link. For example, if the real-time preview stream can be forwarded normally, but the recording storage end fails to generate recording segments covering the sampling time period, or if the recording index is missing, causing the playback interface to be inaccessible, then the abnormality occurs in the recording storage link.

[0055] When the video link status fingerprints at the camera, streaming media forwarding end, and video storage end all meet the normal conditions, but the video link status fingerprint at the playback end is abnormal, the remote maintenance platform identifies the abnormal link as the playback decoding link. For example, if the camera output is normal, the streaming media forwarding end forwards normally, and the recorded segments and recording indexes are normal, but the playback end displays an error code indicating decoding failure, a first frame display timeout, or a continuous black screen, then the abnormality occurs in the playback decoding link.

[0056] The above-mentioned anomaly location method is based on the state differences of the same video surveillance channel in multiple link nodes, rather than solely on the blurry image, black screen, abnormal brightness, or offline status of the device to issue alarms.

[0057] The remote maintenance platform generates remote maintenance action packages based on abnormal situations. Each remote maintenance action package includes maintenance actions, action objects, action types, execution order, preconditions, verification conditions, verification windows, and rollback conditions.

[0058] When the anomaly occurs during the acquisition and encoding stage, the action targets are the camera or edge access gateway. Action types include rolling back encoding parameters, switching the secondary bitstream, and performing a camera soft restart. The execution order is: first roll back the encoding parameters, then switch the secondary bitstream, and finally perform the camera soft restart. The camera soft restart is a maintenance action that will cause a short-term interruption to the main bitstream and requires entering the shadow verification and blind spot coverage judgment process.

[0059] When the abnormal process occurs in the transmission and forwarding stage, the action target is the streaming media forwarding end, and the action types include refreshing the streaming session, switching the streaming media forwarding node, and rebuilding the forwarding cache. The execution order is: first refresh the streaming session, then switch the streaming media forwarding node, and finally rebuild the forwarding cache. Switching the streaming media forwarding node and rebuilding the forwarding cache may cause a short-term interruption of the main stream, which requires pre-verification.

[0060] When the anomaly occurs in the video recording storage stage, the action target is the video recording storage end, and the action types include verifying video segments, rebuilding the video recording index, and refreshing the storage mount. The execution order is: first verify the video segments, then rebuild the video recording index, and finally refresh the storage mount. Refreshing the storage mount may affect video writing, requiring the initiation of an overwrite check and video continuity verification process.

[0061] When the abnormal process occurs during playback decoding, the action target is the playback client or playback service proxy node. Action types include resetting the playback session, clearing the decoding buffer, and switching decoding parameters. These actions do not disable the main stream output on the camera end, and the real-time preview status and playback client decoding status still need to be verified after execution.

[0062] The prerequisites for the remote maintenance action package include: the action object is consistent with the abnormal link; the action object is in a connectable state; the same action has not exceeded the preset number of executions in the current abnormal event; for maintenance actions that will cause a short interruption of the main code stream, the shadow verification channel meets the verification conditions, and the adjacent blind-filling channel meets the coverage conditions.

[0063] The preset number of execution attempts is stored in the action policy table of the remote maintenance platform and corresponds to the action type and device type. For example, refreshing the streaming session can be configured to attempt multiple times, while a camera soft restart can be configured to attempt only once. The specific number of attempts depends on the device manufacturer's interface capabilities, maintenance security policies, and on-site monitoring level.

[0064] The verification conditions in the remote maintenance action package include: the video link status fingerprint of the target node meets the normal conditions after maintenance; the real-time preview status is restored; the recorded playback status covers the maintenance action execution time; and the decoding status on the playback end does not show any error codes indicating decoding failure. Rollback conditions include: the above verification conditions are not met within the verification window, or a new node anomaly is introduced after the maintenance action is executed.

[0065] When the remote maintenance action package contains maintenance actions that will cause a short interruption of the main stream, the remote maintenance platform does not directly execute the maintenance action on the video monitoring channel corresponding to the main stream. Instead, it first establishes a shadow verification channel based on the secondary stream address.

[0066] When establishing the shadow verification channel, the remote maintenance platform initiates a stream retrieval request to the camera terminal based on the secondary stream address, corresponding to the current sampling time period of the main stream. The secondary stream is then connected to the streaming media verification node to form a verification forwarding stream; the verification forwarding stream is connected to the recording verification node to form a verification recording segment; and the verification forwarding stream is connected to the playback verification node to form a verification playback stream. The streaming media verification node, recording verification node, and playback verification node are independent of the streaming media forwarding end, recording storage end, and playback end corresponding to the main stream, respectively.

[0067] Mutual independence does not require that the verification node and the main stream node be physically completely different servers. Rather, it means that the shadow verification channel does not reuse the forwarding sessions, recording indexes, and playback sessions currently being used by the main stream. During shadow verification, even if the pre-verification operation fails, it will not directly disrupt the real-time preview and recording services being provided by the main stream.

[0068] The pre-verification operations correspond to the maintenance actions in the remote maintenance action package. For example, if the main stream intends to switch the streaming media forwarding node, the shadow verification channel first performs the corresponding forwarding node switch on the secondary stream and collects the verification forwarding stream status fingerprint after the switch; if the main stream intends to rebuild the recording index, the shadow verification channel first performs index reconstruction on the verification recording segment and checks whether the verification recording segment can be played back normally; if the main stream intends to switch decoding parameters, the shadow verification channel first performs decoding parameter switching on the playback verification node and collects the decoding status of the playback end of the verification playback stream.

[0069] The shadow verification channel meets the verification conditions if, after the pre-verification operation, the video link status fingerprints corresponding to the verification forwarding stream, verification recording segment, and verification playback stream all meet the normal conditions, and no new transmission sequence breakpoints, missing recording indexes, or decoding failure error codes appear. Only after the shadow verification passes will the remote maintenance platform continue to perform the adjacent blind spot filling channel coverage judgment.

[0070] The shadow verification channel differs from ordinary backup stream playback. It is not simply used for temporary playback, but rather to verify the impact of remote maintenance actions on various nodes in the video link without affecting the main stream service.

[0071] After the shadow verification channel meets the verification conditions, the remote maintenance platform determines whether the key monitoring area is covered by the adjacent blind spot filling channel whose video link status fingerprint meets the normal conditions.

[0072] Specifically, the remote maintenance platform reads the area identifier and adjacent blind spot channel number corresponding to the key monitoring area recorded in the link model; collects the video link status fingerprint of the adjacent blind spot channel within the current sampling time period; determines whether the video link status fingerprint of the adjacent blind spot channel meets the normal conditions, and determines whether the monitoring area identifier of the adjacent blind spot channel includes the area identifier of the key monitoring area.

[0073] Specifically, the inclusion of the critical monitoring area's area identifier in the monitoring area identifier of adjacent blind spot replacement channels means that, in the area mapping table, the set of coverage areas of adjacent blind spot replacement channels contains the area identifier of the critical monitoring area, or that adjacent blind spot replacement channels and the critical monitoring area have a pre-defined coverage relationship. This inclusion relationship does not refer to a literal name inclusion, but rather to the area coverage mapping relationship established during the deployment of the video surveillance system.

[0074] When the video link status fingerprint of an adjacent blind spot filler channel meets the normal conditions, and the monitoring area identifier of the adjacent blind spot filler channel includes the area identifier of the critical monitoring area, the remote maintenance platform determines that the coverage conditions are met. At this time, even if the main stream experiences a short-term interruption during maintenance operations, the critical monitoring area can still be monitored by the adjacent blind spot filler channel.

[0075] When the video link status fingerprint of an adjacent blind spot coverage channel does not meet the normal conditions, or the monitoring area identifier of an adjacent blind spot coverage channel does not include the area identifier of a critical monitoring area, the remote maintenance platform determines that the coverage conditions are not met. In this case, the remote maintenance platform will perform a non-interrupted recovery action, or a maintenance action that would cause a short-term interruption of the main stream will be delayed.

[0076] Uninterrupted recovery actions refer to maintenance actions that do not shut down the main stream, restart the camera, or pause the main stream recording. These actions include refreshing the playback session, refreshing the streaming session, switching playback decoding parameters, switching the secondary stream temporary preview, and clearing the playback cache. Delayed execution means that the remote maintenance platform retains the remote maintenance action package and re-evaluates the coverage conditions of the shadow verification channel and adjacent blind spot filling channels during subsequent sampling periods.

[0077] In this embodiment, the adjacent blind spot compensation channel is not used to determine whether the camera is faulty, but rather as a permission condition for remote maintenance actions that will cause a short interruption of the main stream.

[0078] When the shadow verification channel meets the verification conditions and the adjacent blind spot filling channel meets the coverage conditions, the remote maintenance platform executes a remote maintenance action package on the video monitoring channel corresponding to the main stream.

[0079] During execution, the remote maintenance platform calls the control interfaces of the corresponding nodes sequentially according to the execution order in the remote maintenance action package. For abnormalities in the transmission and forwarding process, the remote maintenance platform first calls the streaming media forwarding interface to refresh the streaming session; if the main stream video link status fingerprint still does not meet the normal conditions after refreshing, it calls the backup streaming media forwarding node interface to switch the forwarding node; if the problem persists after switching, it rebuilds the forwarding cache.

[0080] In case of anomalies in the video storage process, the remote maintenance platform first verifies the video segments corresponding to the sampling time period through the video storage terminal interface; when the video file exists but the index is missing, it calls the video index reconstruction interface to rebuild the video index; when the video file write path is unavailable, it calls the storage mount refresh interface to refresh the storage mount, and then re-collects the continuity of the video index after the refresh.

[0081] If an anomaly occurs during the acquisition and encoding process, the remote maintenance platform first calls the camera's interface to revert the encoding parameters to the historical normal configuration. If the main stream is still abnormal after the reversion, the auxiliary stream is called for temporary support. If the camera's output status still has not recovered, a soft restart of the camera is performed, provided that both shadow verification and blind spot coverage conditions are met.

[0082] Before executing each action, the remote maintenance platform records the action object, action start time, action end time, action interface return status, and node status fingerprint after action execution. These records are used for subsequent verification and rollback judgment.

[0083] After the remote maintenance action package is executed, the remote maintenance platform re-collects the video link status fingerprint of the video surveillance channel within the verification window. The verification window is determined by the remote maintenance platform based on the maintenance action type, recording segment generation cycle, playback buffer time, and device interface response time.

[0084] For actions such as refreshing the streaming session, resetting the playback session, and clearing the decoding cache, the verification window is based on the first frame display time on the playback end and the session recovery time on the forwarding end. For actions such as rebuilding the recording index and refreshing the storage mount, the verification window is based on the recording segment generation cycle and the recording index refresh cycle. For camera soft restart actions, the verification window is based on the camera's re-on time, the main stream's output recovery time, and the first frame display time on the playback end. The verification window is generated along with the action package as a field of the remote maintenance action package.

[0085] Within the verification window, the remote maintenance platform acquires the video link status fingerprints of the real-time preview stream, the video playback stream, and the playback device after maintenance. The video link status fingerprint of the real-time preview stream is used to confirm whether the main stream has returned to normal at the camera and streaming media forwarding ends; the video link status fingerprint of the video playback stream is used to confirm whether the video storage end has generated a recording segment covering the maintenance action execution time and can be played back normally through the recording index; the video link status fingerprint of the playback device is used to confirm whether the playback device has resumed decoding and display.

[0086] When the video link status fingerprints of the real-time preview stream, video playback stream, and playback terminal after maintenance all match the historical normal fingerprints of the corresponding nodes, and the start and end times of the recording segments in the video playback status cover the execution time of the remote maintenance action package, the remote maintenance platform determines that the remote maintenance action package has been verified.

[0087] The start and end times of the video clips covering the execution time of the remote maintenance action package mean that the start and end times of the remote maintenance action package are covered by the start and end times of one or more video clips generated by the video storage terminal, and there are no time gaps between adjacent video clips that exceed the video clip segmentation interval. If a gap exists in the main stream video clip due to a permissible short-term interruption during maintenance of the video surveillance channel, the remote maintenance platform reads the video clips of the adjacent gap-filling channel that meet the coverage conditions within the same time period, and associates the video clips of the gap-filling channel with the maintenance record of the original video surveillance channel as supplementary evidence for verifying the continuity of recording during maintenance.

[0088] When the real-time preview stream is not restored, the video playback stream has missing indexes, the start and end times of the video clips cannot cover the execution time of the remote maintenance action package, the playback terminal still has error codes indicating decoding failure, or new node anomalies occur after maintenance, the remote maintenance platform determines that the remote maintenance action package verification has failed and executes the rollback operation according to the rollback conditions in the remote maintenance action package.

[0089] The rollback operation includes one or more of the following: restoring the encoding parameters before maintenance, restoring the original streaming media forwarding node, restoring the original playback decoding parameters, canceling the incomplete video index reconstruction task, and restoring the original storage mounting state. After the rollback operation is executed, the remote maintenance platform collects the video link status fingerprint again and reserves the abnormal links as pending manual verification to avoid repeatedly executing maintenance actions that would cause a short-term interruption of the main stream in the same abnormal event.

[0090] Taking the video surveillance channel C01 at the park entrance as an example, this channel includes the camera terminal CAM01, the streaming media forwarding terminal SMS01, the video storage terminal VSS01, and the playback terminal APP01. The link model records the main stream address and the secondary stream address of CAM01, and records the entrance area A01 as the key monitoring area, and the adjacent blind spot channel C02 also covers area A01.

[0091] During a routine inspection, the remote maintenance platform collected status data for C01 at the camera, streaming media forwarding, video storage, and playback ends. The data showed that the keyframe timestamp sequence at the camera was continuous, and the bitrate fluctuation was within the historical normal range; the streaming media forwarding end exhibited a break in the transmission sequence continuity, with abnormal first-frame response time; the video storage end showed intermittent missing video segments; and the playback end recorded playback interruptions. Based on its anomaly location rules, the remote maintenance platform determined that the source of the anomaly was in the transmission forwarding stage.

[0092] The remote maintenance platform generates remote maintenance action packages for the transmission and forwarding process. Action types include refreshing the streaming session, switching streaming media forwarding nodes, and rebuilding the forwarding buffer. Since switching streaming media forwarding nodes may cause a short-term interruption of the main stream, the remote maintenance platform first establishes a shadow verification channel based on the secondary stream address of CAM01. The secondary stream is then connected to the streaming media verification node, the recording verification node, and the playback verification node. Forwarding node switching is then performed within the shadow verification channel. After pre-verification, the continuity of the transmission sequence of the verification forwarded stream is restored, the continuity of the recording segment index is verified, and no decoding failure error codes appear in the playback stream. The remote maintenance platform then determines that the shadow verification channel meets the verification conditions.

[0093] Subsequently, the remote maintenance platform collected the video link status fingerprint of the adjacent blind spot channel C02. The key frame timestamp sequence of C02 was continuous, the bitrate fluctuation was within the normal range, the transmission sequence continuity showed no breaks, the recording index was continuous, and no decoding errors occurred at the playback end. Furthermore, the monitoring area identifier of C02 included area A01 in the area mapping table. The remote maintenance platform determined that the critical monitoring area A01 was covered by a normally functioning adjacent blind spot channel, and therefore performed a remote maintenance action to switch the streaming media forwarding node for the video monitoring channel corresponding to the main stream of C01.

[0094] After the action was executed, the remote maintenance platform re-collected the real-time preview stream, video playback stream, and video link status fingerprint of the playback end within the verification window. The verification results showed that the real-time preview stream transmission sequence was continuous, the video playback stream could replay recording segments covering the time of the maintenance action execution, and no decoding failure error codes appeared at the playback end. The remote maintenance platform confirmed that the remote maintenance action package had passed verification.

[0095] In the above embodiments, the remote maintenance platform does not only generate alarms based on phenomena such as black screen, blurry image, or offline status, nor does it simply dispatch maintenance tasks to maintenance personnel. Instead, it first identifies abnormal links through multi-node video link status fingerprints, then verifies the impact of maintenance actions on the video link through the shadow verification channel, and then controls the execution of main stream maintenance actions in combination with the coverage conditions of adjacent blind spot filling channels. After execution, it performs closed-loop verification through real-time preview, video playback, and decoding status at the playback end.

[0096] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for remote maintenance of the operating status of a monitoring system, characterized in that, Includes the following steps: S1. Establish a link model for the video surveillance channel. The link model includes the camera end, streaming media forwarding end, video recording storage end, and playback end. Record the main stream address, secondary stream address, key monitoring area, and adjacent blind spot filling channels corresponding to the video surveillance channel. S2. Collect status data of different nodes in the link model of the same video surveillance channel, and generate video link status fingerprints of the corresponding nodes based on the status data; S3. Perform consistency comparison of video link status fingerprints at different nodes of the same video surveillance channel, and determine the abnormal links based on the comparison results; S4. Generate a remote maintenance action package based on the abnormal process. The remote maintenance action package includes maintenance actions and corresponding verification conditions. S5. When the remote maintenance action package contains maintenance actions that will cause a short interruption of the main stream, a shadow verification channel is established based on the secondary stream address, and a pre-verification operation corresponding to the maintenance action is performed on the shadow verification channel. S6. After the shadow verification channel meets the verification conditions, determine whether the key monitoring area is covered by the adjacent blind-filling channel whose video link status fingerprint meets the normal conditions. If the coverage conditions are met, a remote maintenance action package will be executed on the video surveillance channel corresponding to the main stream. If the coverage conditions are not met, perform a non-interrupted recovery action or a maintenance action that will cause a short interruption of the main stream by delaying the execution; S7. After the remote maintenance action package is executed, the video link status fingerprint of the video monitoring channel is collected again, and the real-time preview status, recording playback status and playback terminal decoding status are combined to determine whether the remote maintenance action package meets the verification conditions. If the verification conditions are not met, a rollback operation is performed.

2. The remote maintenance method for monitoring the operating status of a system according to claim 1, characterized in that, In S1, the link model is established according to the video surveillance channel number; The link model also records the device identifier, encoding parameters, and access address of the camera end; the forwarding node identifier, streaming protocol, and forwarding address of the streaming media forwarding end; the recording plan, recording file storage path, and recording index address of the recording storage end; and the client identifier, decoding method, and playback request address of the playback end.

3. The remote maintenance method for monitoring the operating status of a system according to claim 2, characterized in that, In S2, status data of at least three nodes of the same video surveillance channel are collected from the camera end, streaming media forwarding end, video storage end and playback end. The status data includes the timestamp of the encoded frame, keyframe interval, output bitrate and frame sequence number output by the camera end, the sequence number of the transmission packet received by the streaming media forwarding end, the first frame response time and forwarding bitrate, the start and end time of the video segment generated by the video storage end, the length of the video file and the video index identifier, and the timestamp of the decoded frame, the first frame display time, the decoding error code and the playback interruption record generated by the playback end.

4. The remote maintenance method for monitoring the operating status of a system according to claim 3, characterized in that, In S2, the video link status fingerprint includes key frame timestamp sequence, bit rate fluctuation value, transmission sequence continuity, inter-frame content features, recording index continuity, and playback end decoding status. When generating video link status fingerprints, the status data collected by the same video surveillance channel within the same sampling time period are normalized according to the node position, and the normalized status data is bound to the corresponding video surveillance channel number, node position and sampling time period.

5. A remote maintenance method for monitoring the operating status of a system according to claim 4, characterized in that, In S3, the abnormal process includes the acquisition and encoding process, the transmission and forwarding process, the video recording and storage process, and the playback and decoding process; When the video link status fingerprint at the camera end is abnormal, and the video link status fingerprints at the streaming media forwarding end, video recording storage end, and playback end are also abnormal synchronously with the camera end, the abnormal link is identified as the acquisition and encoding link. When the video link status fingerprint at the camera end is normal, but the video link status fingerprint at the streaming media forwarding end is abnormal, the abnormal link is identified as the transmission and forwarding link. When the video link status fingerprints at the camera end and the streaming media forwarding end are normal, but the video link status fingerprint at the recording storage end is abnormal, the abnormal link is identified as the recording storage link. When the video link status fingerprints at the camera end, streaming media forwarding end, and video recording storage end are normal, but the video link status fingerprint at the playback end is abnormal, the abnormal link is identified as the playback decoding link.

6. The remote maintenance method for monitoring the operating status of a system according to claim 5, characterized in that, When judging the video link status fingerprint anomaly, the key frame timestamp sequence, bit rate fluctuation value, transmission sequence continuity, recording index continuity, and playback decoding status are judged separately. When any of the following situations occur, such as missing keyframe timestamp sequences, bitrate fluctuations exceeding the preset bitrate range, breaks in transmission sequence continuity, missing recording index continuity, or decoding status at the playback end containing decoding error codes indicating decoding failure, the video link status fingerprint of the corresponding node is determined to be abnormal.

7. A remote maintenance method for the operating status of a monitoring system according to claim 6, characterized in that, In S4, the remote maintenance action package also includes action object, action type, execution order, preconditions and rollback conditions; When the abnormal step is the acquisition and encoding step, the action types include rollback of encoding parameters, switching of auxiliary bitstream, and camera soft restart; When the abnormal link is the transmission and forwarding link, the action types include refreshing the streaming session, switching the streaming media forwarding node, and rebuilding the forwarding cache; When the abnormal process is the video recording storage process, the action types include verifying video segments, rebuilding the video recording index, and refreshing the storage mount. When the abnormal process is the playback decoding process, the action types include resetting the playback session, clearing the decoding cache, and switching decoding parameters.

8. A remote maintenance method for the operating status of a monitoring system according to claim 7, characterized in that, In S5, when establishing the shadow verification channel, a streaming request corresponding to the current sampling time period of the main stream is initiated to the camera end based on the secondary stream address. The secondary stream is connected to the streaming media verification node to form a verification forwarding stream, the verification forwarding stream is connected to the recording verification node to form a verification recording segment, and the verification forwarding stream is connected to the playback verification node to form a verification playback stream. The streaming media verification node, recording verification node, and playback verification node are independent of the streaming media forwarding end, recording storage end, and playback end corresponding to the main stream, respectively.

9. A remote maintenance method for the operating status of a monitoring system according to claim 8, characterized in that, In S6, when determining whether the key monitoring area is covered by an adjacent blind-filling channel whose video link status fingerprint meets the normal conditions, the area identifier and adjacent blind-filling channel number corresponding to the key monitoring area are read, and the video link status fingerprint of the adjacent blind-filling channel in the current sampling time period is obtained. When the video link status fingerprint of the adjacent blind spot filling channel meets the normal conditions, and the monitoring area identifier of the adjacent blind spot filling channel contains the area identifier of the key monitoring area, the coverage condition is determined to be met.

10. A remote maintenance method for the operating status of a monitoring system according to claim 9, characterized in that, In S7, after the remote maintenance action package is executed, the video link status fingerprint of the real-time preview stream, the video link status fingerprint of the recording playback stream, and the video link status fingerprint of the playback end are obtained respectively. When the video link status fingerprints of the real-time preview stream, video playback stream, and playback terminal after maintenance all match the historical normal fingerprints of the corresponding nodes, and the start and end times of the recording segments in the video playback status are continuous with the execution time of the remote maintenance action package, it is determined that the remote maintenance action package has passed verification. If the above conditions are not met, it is determined that the remote maintenance action package verification has failed, and the rollback operation is performed according to the rollback conditions in the remote maintenance action package.

Images