Video management method and device, and storage medium

Abstract

The invention discloses a video management method and device and a storage medium, the method is applied to an image acquisition device, a first communication connection exists between the image acquisition device and a cloud server, and the method comprises the following steps: in response to detection of triggering of a first target event, performing local video processing on the first target event to obtain a first local video; according to first local video information of the first local video and equipment state information of the image acquisition equipment, determining a currently uploaded video and a video to be retransmitted in the first local video; uploading the currently uploaded video to a cloud server; and in response to a received video additional transmission request sent by the cloud server for the first local video, uploading the video to be subjected to additional transmission to the cloud server. According to the scheme, the video management efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a video recording management method, device, and storage medium. Background Technology

[0002] With the rapid development of IoT technology, a wide variety of IoT devices have been developed and applied to modern life.

[0003] Among them, IoT-based image acquisition devices have become mainstream products in smart home scenarios. Image acquisition devices can capture images and / or videos, and their typical working mode is usually "event-triggered recording," that is, video recording is started only after a target event is detected in the current scene, and the video data is synchronously saved to local storage media for local recording, and saved to a cloud server for cloud recording.

[0004] However, image acquisition devices need to log into the cloud platform before recording cloud video after detecting an event. Continuously uploading data to ensure the integrity of cloud recordings consumes a lot of device power; however, reducing uploads to save power sacrifices user experience. Therefore, existing solutions lack granular recording power consumption management, making it difficult to effectively achieve end-to-cloud collaboration and reducing recording management efficiency. Summary of the Invention

[0005] This application provides at least one video recording management method, apparatus, device, and computer-readable storage medium.

[0006] This application provides a video recording management method, applied to an image acquisition device, wherein the image acquisition device has a first communication connection with a cloud server, comprising: in response to detecting the triggering of a first target event, performing local video recording processing on the first target event to obtain a first local video recording; determining the currently uploaded video recording and the video recording to be re-uploaded in the first local video recording based on the first local video recording information and the device status information of the image acquisition device; uploading the currently uploaded video recording to the cloud server; and in response to receiving a video re-upload request sent by the cloud server for the first local video recording, uploading the video recording to be re-uploaded to the cloud server.

[0007] In one embodiment, determining the currently uploaded video and the video to be re-uploaded in the first local video based on the first local video recording information and the device status information of the image acquisition device includes: determining the current upload duration based on the first local video recording information and the device status information of the image acquisition device; and dividing the first local video into the currently uploaded video and the video to be re-uploaded based on the current upload duration.

[0008] In one embodiment, the first local recording information includes a first local recording duration, and the device status information includes a device sleep countdown, remaining device battery power, and recording upload power consumption. Determining the current upload duration based on the first local recording information and the device status information of the image acquisition device includes: determining the remaining upload time based on the remaining device battery power and the recording upload power consumption; and determining the minimum value among the first local recording duration, the device sleep countdown, and the remaining upload time as the current upload duration.

[0009] In one embodiment, uploading the currently uploaded video to the cloud server includes: in response to detecting the triggering of a second target event, pausing or stopping the uploading of the currently uploaded video to the cloud server, and obtaining the first video metadata of the first local video and uploading it to the cloud server; performing local recording processing on the second target event to obtain a second local video; and uploading a portion of the video in the second local video to the cloud server.

[0010] In one embodiment, before uploading the video to be re-uploaded to the cloud server, the method further includes: in response to receiving a video re-upload request sent by the cloud server for the first local video, determining whether the first local video exists in the local video list of the image acquisition device; if not, notifying the cloud server that the first local video has been lost.

[0011] In one embodiment, the cloud server and the client have a second communication connection; the video re-upload request is generated by the client based on the prediction of the user's viewing intention for the first local video and sent to the cloud server.

[0012] In one embodiment, after uploading the currently uploaded video to the cloud server, the method further includes: obtaining the local video storage period and the cloud video storage period; in response to the local video storage period being less than the cloud video storage period, determining a pre-upload time based on the local video storage period; and in response to no video re-upload request being received before the pre-upload time, uploading the video to be re-uploaded to the cloud server within the pre-upload time.

[0013] In one embodiment, the method further includes: obtaining a local video recording list in the image acquisition device and local video recording metadata of each local video recording in the local video recording list; and periodically synchronizing the local video recording list and the local video recording metadata to the cloud server.

[0014] A second aspect of this application provides a video recording management device, which is applied to an image acquisition device and has a first communication connection with a cloud server. The device includes: a local recording module, configured to perform local recording processing on the first target event in response to the detection of a first target event to obtain a first local recording; a re-transmission determination module, configured to determine the currently uploaded recording and the recording to be re-transmitted in the first local recording based on the first local recording information of the first local recording and the device status information of the image acquisition device; a current uploading module, configured to determine the currently uploaded recording and the recording to be re-transmitted in the first local recording based on the first local recording information of the first local recording and the device status information of the image acquisition device; and a video re-transmission module, configured to upload the recording to be re-transmitted to the cloud server in response to receiving a video re-transmission request sent by the cloud server for the first local recording.

[0015] A third aspect of this application provides an electronic device, including a memory and a processor, wherein the processor is used to execute program instructions stored in the memory to implement the above-described video recording management method.

[0016] The fourth aspect of this application provides a computer-readable storage medium having program instructions stored thereon, which, when executed by a processor, implement the above-described video recording management method.

[0017] The above scheme, upon detecting the triggering of a first target event, obtains a first local video recording by performing local recording processing on the first target event. The local video recording is stored on a local storage medium and needs to be uploaded to a cloud server to obtain a cloud video recording. In this application, during the process of uploading the local video recording to the cloud server, the local recording information and the device status information of the image acquisition device are comprehensively considered to determine which currently uploaded video recording needs to be uploaded first and which recordings awaiting subsequent upload are to be supplemented. The currently uploaded video recording is uploaded to the cloud server first. The segmented upload method allows for prioritizing the upload of some recordings when the network is poor, or actively segmenting uploads to save power under normal network conditions. If a recording supplementation request is received from the cloud server for the first local video recording, the recording to be supplemented is then uploaded to the cloud server. The subsequent supplementation method ensures the consistency of data between the end and the cloud. This allows for reasonable and efficient video recording management.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description

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

[0020] Figure 1 This is a flowchart illustrating an exemplary embodiment of the video recording management method of this application; Figure 2 This is a schematic diagram illustrating an exemplary application scenario of the video recording management method in this application; Figure 3 This is an exemplary playback interface diagram of the video recording management method of this application; Figure 4 This is a block diagram illustrating a video recording management device in an exemplary embodiment of this application; Figure 5 This is a schematic diagram of the structure of an embodiment of the electronic device of this application; Figure 6 This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium of this application. Detailed Implementation

[0021] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0022] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.

[0023] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0024] To facilitate understanding, one of the applicable scenarios of this application will be illustrated by example.

[0025] With the rapid development of IoT technology, a wide variety of IoT devices have been developed and applied to modern life.

[0026] Among them, IoT-based image acquisition devices have become mainstream products in smart home scenarios. Image acquisition devices can capture images and / or videos, and their typical working mode is usually "event-triggered recording," that is, video recording is started only after a target event is detected in the current scene, and the video data is synchronously saved to local storage media for local recording, and saved to a cloud server for cloud recording.

[0027] However, existing video recording management methods still have several problems that urgently need to be addressed, such as: 1. Inconsistency between cloud recording and local recording: After an image acquisition device is triggered by a target event, it usually needs to log in to the cloud platform first. However, if the network connection of the image acquisition device is poor, the login delay can cause the cloud recording cache on the device to fill up, resulting in the discarding of recordings from the initial stage of the event. Therefore, if the network is allowed to recover before uploading data from the cloud recording cache to the cloud server, the cloud recording duration may be shorter than the local recording duration, and the start time of recording the target event in the cloud recording may also be later than the start time of recording the target event in the local recording.

[0028] 2. Balancing power consumption and user experience: Low-power cameras are widely used, and the continuous uploading of data to ensure complete cloud recording consumes a significant amount of battery power. However, reducing uploading to save power sacrifices the user experience. Therefore, common solutions lack sophisticated energy management for low-power cameras.

[0029] In summary, common technical solutions lack refined video recording energy consumption management, making it difficult to effectively achieve end-to-cloud collaboration and reducing video recording management efficiency.

[0030] Please see Figure 1 , Figure 1 This is a flowchart illustrating an exemplary embodiment of the video recording management method of this application. The method of this application is mainly applied to the image acquisition device in the video recording management system, which may also be referred to as the device end below. The video recording management system may also include a cloud server, and a first communication connection exists between the image acquisition device and the cloud server. Specifically, it may include the following steps: Step S110: In response to the detection of the first target event being triggered, local recording processing is performed on the first target event to obtain the first local recording.

[0031] The first target event can be of various types. For example, detecting a target object can be a target event, or detecting a target behavior can be a target event. It can also be some preset detection rules such as tripwire detection, area intrusion, etc., which will not be elaborated here.

[0032] For example, there are multiple methods to determine whether the first target event has been triggered. For instance, it can be determined by analyzing the video image data acquired by the image acquisition device (refer to image processing or neural network models, etc., which will not be elaborated here); or it can be determined by the detection results of detection devices that have other communication connections with the image acquisition device (such as radar, radio frequency sensors, photoelectric sensors, etc., which will not be elaborated here).

[0033] Once the image acquisition device determines that the first target event has been triggered, the recording module can be activated to record the event. This recording process can include local recording and cloud recording. Typically, local recording is performed first, and then the local recording is uploaded to the cloud server for cloud recording.

[0034] It should be noted that there may be multiple target events in the application scenarios of this application. The trigger time, duration and end time of different target events may be the same or different, and no limitation is made here.

[0035] For ease of explanation, the local recording corresponding to the triggering of the first target event is defined as the first local recording. Similarly, if a second target event is subsequently triggered, the local recording corresponding to the triggering of the second target event is defined as the second local recording. Essentially, both the first and second local recordings are local recordings. Therefore, the processing methods for the first local recording can be applied to the second local recording in the same way, which will not be elaborated here.

[0036] Step S120: Determine the currently uploaded video and the video to be uploaded in the first local video based on the first local video information and the device status information of the image acquisition device.

[0037] The first local video recording information refers to information related to the first local video recording, such as the total recording duration and the amount of video data.

[0038] Device status information refers to information related to the device status of an image acquisition device, such as the network status, battery status, and sleep countdown of the image acquisition device.

[0039] For example, when preparing to upload cloud video recordings, this application first divides the currently uploaded video recordings that need to be uploaded first and the video recordings that need to be uploaded later into those that need to be uploaded later, based on the local video recording information and device status information.

[0040] Specifically, the methods for dividing the currently uploaded video and the video to be uploaded in the local recording may include, but are not limited to, dividing by time or by data volume.

[0041] The currently uploaded recordings refer to a portion of the recordings selected from the local recordings during the cloud recording process to achieve fast uploading and timely data synchronization.

[0042] Correspondingly, the videos to be uploaded refer to the remaining videos in the local recordings besides the currently uploaded videos. Videos to be uploaded need to wait for an upload opportunity (some upload trigger conditions can be set) before the upload process is performed (uploading them to the cloud server).

[0043] The conditions for retransmission may include, but are not limited to: receiving a video retransmission request and then performing the retransmission process; or performing the retransmission process periodically, etc., which will not be elaborated here.

[0044] Therefore, the method of this application can ensure that the core content of local recordings is uploaded quickly, and the remaining parts are uploaded as needed, thus comprehensively guaranteeing device energy efficiency and user experience.

[0045] Step S130: Upload the currently uploaded video to the cloud server.

[0046] Based on the steps described above, after determining the currently uploaded video in the local recording, the currently uploaded video can be transferred to the cloud server first to obtain a partial cloud recording of the first target event.

[0047] Furthermore, after the video upload is completed, if there is a client with a second communication connection to the cloud server, the client can view the relevant information corresponding to the first target event and part of its cloud video recording content.

[0048] Understandably, the client here needs to have the security conditions such as the ability to access the cloud server and the ability to view the cloud recordings of the first target event, which will not be elaborated here.

[0049] Step S140: In response to receiving the video re-upload request sent by the cloud server for the first local video recording, upload the video to be re-uploaded to the cloud server.

[0050] A video re-upload request refers to an upload request for a video recording that needs to be re-uploaded from a specific target event (a local video recording). For example, a video re-upload request for the first local video recording is used to instruct the upload of the video recording that needs to be re-uploaded from the first local video recording.

[0051] For example, the video retransmission request can be sent by the user to the cloud server through the client, and then sent by the cloud server to the image acquisition device; or it can be generated by the cloud server and sent to the image acquisition device; or it can be generated locally by the image acquisition device, which is not limited here.

[0052] Specifically, when the device receives a video re-upload request from the first local video recording, it can find the video recording to be re-uploaded corresponding to the first local video recording in the local storage medium according to the video re-upload request, and then upload the video recording to be re-uploaded to the cloud server, thereby realizing the complete upload of the first local video recording and obtaining the complete cloud recording of the first local video recording.

[0053] Furthermore, after obtaining the complete cloud recording of the first local video on the cloud server, it can be synchronously displayed on the client, which means that the client can view the complete cloud recording content of the first local video.

[0054] As can be seen, when the first target event is detected, this application performs local recording processing on the first target event to obtain the first local recording. The local recording is stored on a local storage medium and needs to be uploaded to a cloud server to obtain cloud recordings. In this application, during the process of uploading the local recording to the cloud server, the local recording information and the device status information of the image acquisition device are comprehensively considered to determine which recordings need to be uploaded first and which need to be supplemented later. The currently uploaded recording is uploaded to the cloud server first. The segmented upload method allows for the priority upload of some recordings when the network is poor, or proactive segmented upload to save power under normal network conditions. If a supplementary recording request is received from the cloud server for the first local recording, the supplementary recording is then uploaded to the cloud server. The subsequent supplementary upload method ensures the consistency of data between the end and the cloud. This allows for reasonable and efficient recording management.

[0055] Based on the above embodiments, this embodiment provides an exemplary description of a video recording management system for the application scenario of this application. On one hand, in an example application scenario, the video recording management system of this application may include at least an image acquisition device and a cloud server. On the other hand, references can be made to... Figure 2 As shown, Figure 2 This is a schematic diagram illustrating an exemplary application scenario of the video recording management method of this application. In this example application scenario, the video recording management system of this application may include at least an image acquisition device, a cloud server, and a client.

[0056] It should be noted that when uploading video files to the cloud server (including full or partial uploads), the video metadata should be uploaded to the cloud server first. Metadata is data used to describe data; here, video metadata refers to data describing the video file, similar to an archive file for the video. Examples include recording duration, video data size, video thumbnails, and recording summaries, which will not be elaborated upon here.

[0057] This could involve the image acquisition device prioritizing the uploading of segmented recordings only when it detects poor network conditions (such as network anomalies or low network speeds preventing real-time uploads); conversely, when the network is detected as normal, it could choose to upload all recordings. Alternatively, the image acquisition device could disregard network conditions and consistently prioritize uploading segmented recordings. This approach is not limited to a single method.

[0058] Therefore, after receiving the video recording metadata, the cloud server can still display the complete video recording information corresponding to that portion of the cloud recording on the client, even if only a portion of the recording has been uploaded. For example, a 3-minute local recording might have 1 minute of that portion uploaded as a cloud recording. Although the user can only view 1 minute of the cloud recording on the client by accessing the cloud server, the client's display shows the complete 3-minute duration of the recording (including the 2 minutes of recording to be uploaded).

[0059] Among them, you can refer to, such as Figure 3 As shown, Figure 3 This is a schematic diagram of an exemplary playback interface in the video recording management method of this application.

[0060] Specifically, for cloud recordings uploaded to the cloud server in segments, the progress bar on the client's playback interface can be displayed using a differentiated visual scheme. For example, when a user views a cloud recording on the client, the progress bar for the portion of the cloud recordings that have been successfully uploaded to the cloud server can be displayed in solid or dark color (referred to as the first display method). The progress bar for recordings that have not been successfully uploaded and are still stored locally on the device, awaiting re-upload, can be displayed using a dashed line, semi-transparent material, or a contrasting color (referred to as the second display method). The first and second display methods differ (e.g., different colors and / or shapes). Optionally, clear text descriptions and first-time user guides can be added to the client interface to intuitively explain its advantages of power saving and on-demand loading.

[0061] Furthermore, to improve user experience, this application also provides an intelligent preloading method for partial cloud recordings during playback on the client side of the video recording management system. When a user plays a partial cloud recording of a target event on the client side, the client implements a predictive preloading strategy. When the client predicts that the user intends to continue watching the currently playing partial cloud recording, it generates a recording re-upload request for the target event and notifies the corresponding device side through the cloud server to re-upload the recording of the target event.

[0062] For example, when a client plays a portion of a cloud recording of a target event, the system predicts the user's intention to continue watching that portion of the cloud recording based on their behavior. If there is an intention to continue watching that portion of the cloud recording, the re-upload process is triggered in advance (generating a re-upload request and sending it to the device via the cloud server), allowing for a certain buffer time for the re-upload.

[0063] There are various ways to predict viewing intent, and no specific method is limited here. For example, prediction methods may include, but are not limited to: 1. Determining that the user will continue watching when the playback progress of a portion of the cloud recording reaches a specific percentage (e.g., 50%) of the total duration of that portion of the cloud recording. 2. Determining that the user will continue watching when the playback progress of a portion of the cloud recording reaches a specific percentage (e.g., 50%) of the total duration of the complete cloud recording. 3. Determining that the user intends to continue watching when they pause or rewind during the playback of a portion of the cloud recording.

[0064] Specifically, after the client generates a video re-upload request, it is forwarded to the device for execution via the cloud server. Optionally, while waiting for the video re-upload, the client's playback interface can display a user-friendly loading animation and status prompts (such as "Loading the complete video from the device...") to effectively manage user expectations and eliminate user confusion caused by silent waiting.

[0065] In addition, the triggering mechanism for video re-upload can include the client predicting the user's intention to continue watching, or the client receiving a re-upload request actively issued by the user (e.g., the user dragging the playback progress bar to the progress area of ​​the video to be re-uploaded), or the cloud server actively issuing a video re-upload request (e.g., setting up periodic re-upload tasks to achieve regular synchronization between local and cloud recordings, or the cloud server detecting that the network status changes from abnormal to normal), etc., which are not limited here.

[0066] Using the methods described in the foregoing embodiments, even if the cloud server only stores a portion of the cloud recording of the target event, the video management system of this application can still achieve seamless and smooth playback when the client plays a portion of the cloud recording through pre-upload of the recording.

[0067] Based on the above embodiments, this embodiment describes step S120. Specifically, the method for determining the currently uploaded video and the video to be re-uploaded in the first local video based on the first local video information and the device status information of the image acquisition device in step S120 includes steps S121 to S122.

[0068] Step S121: Determine the current upload duration based on the first local video recording information and the device status information of the image acquisition device.

[0069] Referring to the foregoing embodiments, this application can divide the first local video recording into a currently uploaded video and a video to be uploaded, thereby achieving the effect of segmented video uploading. The method for segmenting the video can be based on time or data volume, etc.

[0070] For example, taking the division of video segments based on time as an example, in this embodiment, a current upload duration can be determined by the first local video recording information and device status information. The current upload duration is equivalent to a suitable uploadable video duration for the current scenario, which is determined by comprehensively considering the local video recording information and device status information.

[0071] Step S122: Divide the first local video recording into the currently uploaded video recording and the video recording to be uploaded according to the current upload duration.

[0072] Based on the steps described above, after obtaining the current upload duration, the first local recording can be divided into the currently uploaded recording and the recording to be uploaded.

[0073] For example, there are many ways to divide the first local video recording into the currently uploaded video recording and the video recording to be uploaded based on the current upload duration, and no specific method is limited here.

[0074] For example, you can select a portion of the local video recordings that is the same length as the current upload recording as the current upload recording, and then select the remaining portion of the local video recordings as the recordings to be uploaded later. Alternatively, you can select a portion of the local video recordings that is shorter than the current upload recording as the current upload recording, and then select the remaining portion of the local video recordings as the recordings to be uploaded later.

[0075] For example, the start time of the local video recording can be used as the starting point for the current uploaded video, and a video segment of the same time period can be selected as the current uploaded video based on the current upload duration. Alternatively, any video segment with a duration equal to the current upload duration can be selected from the local video as the current uploaded video. Another approach is to install a lightweight object detection model in the image acquisition device. The image acquisition device can analyze the local video using a pre-trained object detection model to identify segments of interest (ROI) and use these ROI segments as the current uploaded video. Specific methods for identifying ROI segments (or high-attention segments, high-popularity segments, etc.) in a video can be found in various feasible approaches within this technical field, and will not be elaborated upon here.

[0076] It's important to note that during the process of identifying segments of interest and designating them as the current upload recording, since local recordings are triggered by the target event, there may be many segments of interest. Therefore, you can either first identify segments of interest with a duration less than or equal to the current upload duration, and then randomly select one of these segments as the current upload recording, or sort them by degree of interest and then select the segment with the highest degree of interest as the current upload recording.

[0077] Alternatively, one could first determine the segments of interest and their number. If there is only one segment of interest, then determine whether the duration of that segment is less than or equal to the current upload duration. If so, then directly use it as the currently uploaded recording. If not, then trim the segment of interest according to the current upload duration to obtain the trimmed segment of interest, and use that as the currently uploaded recording. If there are multiple segments of interest, they can first be sorted according to their degree of interest. After determining the segment of interest with the highest degree of interest, then determine whether its duration exceeds the current upload duration. The same logic applies to subsequent segments, which will not be elaborated here.

[0078] For example, when determining the current upload video, the local video can first be divided into several sub-video segments (which can be divided equally or unevenly according to duration; this is not limited here). After sorting the respective video segments by priority, multiple target sub-video segments can be selected as the current upload video. The sum of the recording durations of the multiple target sub-video segments must be less than or equal to the current upload duration.

[0079] The method of prioritizing can refer to the relevant methods in this technical field, such as including but not limited to: sorting according to the degree of interest of each sub-video segment as in the aforementioned example, or finding the corresponding sub-event priority according to the sub-events that occur in each sub-video segment, or sorting according to the amount of dynamic change in each sub-video segment (for example, the more drastic the pixel change, the more intense the current video content is, which may be a moving scene; while the less drastic the pixel change, the more stable the current video content is, which may be a still scene).

[0080] Based on the above embodiments, this embodiment describes step S121. Specifically, the method for determining the current upload duration in step S121 based on the first local recording information of the first local recording and the device status information of the image acquisition device includes steps S1211 to S1212.

[0081] Step S1211: Determine the remaining upload time based on the device's remaining battery power and the energy consumption for video upload.

[0082] The video upload energy consumption refers to the energy (power) consumed by the image acquisition device when uploading a certain duration or a certain amount of data; or, in other words, the upload duration or amount of video data that can be uploaded for each certain amount of power consumed. For example, 10 seconds of video can be uploaded for every 1% of power. The specific value can be determined through multiple experiments and is a constant, so it will not be elaborated upon here.

[0083] Therefore, by considering the remaining battery power of the image acquisition device and the energy consumption for uploading video recordings, we can determine the remaining time or the remaining amount of data that the image acquisition device can support for uploading video recordings.

[0084] Step S1212: Determine the minimum value among the first local recording duration, the device sleep countdown, and the remaining upload time as the current upload duration.

[0085] Based on the steps described above, after knowing the remaining upload time of the video recording supported by the current remaining battery power of the image acquisition device, the local recording duration can be compared with the remaining upload time.

[0086] On one hand, if the local recording duration is less than the remaining upload time, the local recording duration can be set as the current upload duration, and the entire local recording can be uploaded to the cloud server. On the other hand, if the local recording duration is greater than the remaining upload time, to ensure successful upload, only the remaining upload time can be set as the current upload duration, and only a portion of the local recording can be uploaded to the cloud server. If the local recording duration is equal to the remaining upload time, either option can be chosen as the current upload duration.

[0087] On the other hand, considering application scenarios where the image acquisition device is a low-power device, low-power devices usually have a preset sleep time. After the device has been in operation for the sleep time, it will enter a sleep state to ensure power consumption control.

[0088] Therefore, when determining the current upload duration, the sleep time can also be taken into account. The device sleep countdown refers to the countdown (remaining sleep time) from the device's current normal video recording state to entering sleep mode.

[0089] To address this, when determining the current upload duration, this application uses the minimum value among the first local recording duration, the device sleep countdown, and the remaining upload time as the current upload duration, Safe_Upload_Duration. That is, Safe_Upload_Duration = Min(local recording duration, device sleep countdown, remaining upload time). This avoids the device being unable to enter sleep mode due to recording upload tasks.

[0090] Optionally, when determining the current upload duration, a time buffer constant (e.g., 5 seconds) can be set on top of the device's sleep countdown to ensure the device can safely go to sleep after the recording is uploaded. That is, Safe_Upload_Duration = Min(local recording duration, device sleep countdown - time buffer constant, remaining upload time). This means the recording upload needs to be completed before the time buffer constant before the device enters sleep mode.

[0091] On the other hand, the currently uploaded recording can be determined from the local recordings based on the amount of data that can be uploaded. For example, by obtaining the current network bandwidth (Network_Bandwidth, which can be in MB / s), and based on the remaining battery power and the energy consumption of uploading the recording, the current upload duration supported by the remaining battery power can be determined. Then, based on the current upload duration and the current network bandwidth, the amount of video data that can be uploaded can be determined, and then a portion of the recordings corresponding to that amount of data (i.e., the currently uploaded recording) can be determined from the local recordings.

[0092] Similarly, using the method described in the previous example, after determining the local recording duration and the device sleep countdown (or device sleep countdown minus the time buffer constant) as the current upload duration, multiplying them by the current network bandwidth will determine the amount of video data that can be uploaded. Then, based on this amount of video data, a portion of the recordings corresponding to this amount is determined from the local recordings; the specific details will not be elaborated further.

[0093] It is understandable that video images may be captured in multiple modes (such as multiple resolutions) during the operation of an image acquisition device. That is, although different video files may have the same duration, their data size may differ. Consequently, even when transmitting video files of the same duration, inconsistencies in transmission time and power consumption may still occur. Therefore, this application proposes determining the currently uploaded video in the local recording based on the data volume dimension, which can more accurately determine the power consumption of the image acquisition device and enable the image acquisition device to enter a normal sleep state.

[0094] Based on the above embodiments, this embodiment describes step S130. Specifically, the method of uploading the currently uploaded video to the cloud server in step S130 includes steps S131 to S133.

[0095] Step S131: In response to the detection of the second target event, pause or stop uploading the currently uploaded video to the cloud server, and obtain the first video metadata of the first local video and upload it to the cloud server.

[0096] In conjunction with the foregoing embodiments, in some application scenarios, for the same image acquisition device, if a new event is detected before the local recording of an old event has been uploaded, the image acquisition device will record and upload the new event.

[0097] In traditional methods, the upload tasks for old and new events are arranged together in the upload queue. When there are multiple incomplete uploads, the traditional queue-based upload may exhaust the limited upload time allocated to new events due to processing the upload tasks for old events, causing the device to be unable to go into sleep mode in time; or the videos of new events may not be uploaded or viewed in time.

[0098] This embodiment proposes a video upload method based on cross-event task scheduling and metadata prioritization to address this type of problem. Specifically, the triggering sequence of the second target event is later than that of the first target event. This means the first target event is an older event, while the second target event is a newer event.

[0099] For example, if a second target event is detected during the process of uploading the currently uploaded video to the cloud server, the uploading of the currently uploaded video of the first target event to the cloud server is paused or stopped. First, the complete metadata of the first local video is obtained and uploaded to the cloud server.

[0100] Therefore, by uploading metadata first, the cloud server ensures the complete display of the recording entries for the first target event (such as displaying the correct recording duration). In other words, as mentioned in the previous example, although the user may only see a portion of the recording content on the client, the cloud server can still display the complete information of the target event to the client because of the complete metadata.

[0101] Step S132: Perform local recording processing on the second target event to obtain the second local recording.

[0102] In conjunction with the preceding steps, steps S131 and S132 can be executed in parallel or sequentially, and no limitation is made here.

[0103] For example, uploading the first video metadata and recording the second local video can be done simultaneously, or the first video metadata can be uploaded first, and the second local video can be recorded after the metadata upload is complete. The methods, recording specifications, and other parameters for local recording processing of the second target event can be the same as or different from those for local recording processing of the first target event; this is not limited here.

[0104] Step S133: Upload a portion of the video recording from the second local recording to the cloud server.

[0105] Based on the steps described above, after obtaining the second local video recording, you can refer to the example method described above to determine the currently uploaded video (partial video recording) from the second local video recording and upload it to the cloud server. This will not be elaborated on here.

[0106] In summary, in the method provided in this embodiment, when a new event (the second target event) is triggered, the complete metadata of the old event (such as the total recording duration of 60 seconds, recording summary, thumbnails, etc.) is uploaded to the cloud server first. This ensures that the "archive" of the cloud recording of the old event is complete and of the correct duration on the cloud server. We only need to wait for the local recording of the old event to be re-uploaded via a subsequent recording re-upload request, which will not be elaborated upon here.

[0107] For example, as can be seen from the previous example, after a new event is triggered, the system first uploads the complete metadata of the incomplete old event (such as total duration, thumbnail, etc.), then determines the current upload duration (safe duration) based on multi-dimensional perception of the recording information and device status, and uploads the portion of the recording corresponding to the current upload duration in the recording of the new event.

[0108] When there is a conflict between the retransmission processing and the recording upload of new events, the business logic of new events can be prioritized. Based on the deadline of the sleep task (such as the sleep countdown), the low-priority tasks in the pending tasks can be suspended to prevent the devices from being stuck due to the competition for resources among the tasks (such as the device being unable to enter the low-power sleep state due to the processing of the recording upload task of the old event (such as the long video retransmission), resulting in the power being quickly exhausted or the new event being missed).

[0109] To address this, this application can also introduce task prioritization and preemption mechanisms. "Device timely hibernation" is set as the highest priority task. The system sets a "latest hibernation deadline." When this deadline is reached, regardless of whether any current tasks are completed, the image acquisition device is forced into hibernation, and unfinished tasks are suspended. This ensures deterministic power consumption control, preventing the device from continuously operating at high power consumption due to processing low-priority tasks, thus avoiding problems such as energy depletion or system response delays.

[0110] Based on the above embodiments, this embodiment describes step S140. Specifically, step S140 may include steps S141 to S142 before uploading the video to be re-uploaded to the cloud server.

[0111] Step S141: In response to receiving a video retransmission request from the cloud server for the first local video recording, determine whether the first local video recording exists in the local video recording list of the image acquisition device.

[0112] The local video recording list in the image acquisition device can represent the video recording files still stored in the image acquisition device.

[0113] It should be noted that since the retention periods of cloud recordings and local recordings may differ, when a recording retransmission request is received, the requested local recording may or may not exist on the local storage medium; this is not a limitation here.

[0114] Therefore, whenever a video retransmission request is received for a certain local video (such as the first local video), it is necessary to determine whether the local video list in the image acquisition device still contains a local video (such as the first local video).

[0115] Step S142: If not, notify the cloud server that the first local recording has been lost.

[0116] To illustrate the steps outlined above, if the local video recording corresponding to the requested re-upload request does not exist in the local video recording list of the image acquisition device, a corresponding prompt message needs to be generated to notify the cloud server that "the local video recording corresponding to this re-upload request has been lost." For example, the device can return some pre-defined error codes to the cloud server, which can then update the status of the cloud video recording corresponding to the re-upload request to "source file lost" and display the corresponding prompt to the user on the client, thereby avoiding playback logic errors and improving system robustness.

[0117] Based on the above embodiments, this embodiment describes a method that can be selectively executed after step S140. Specifically, steps S150 to S170 may also be included after step S140.

[0118] Step S150: Obtain the local video recording storage period and the cloud video recording storage period.

[0119] The local video recording storage period refers to the time that the image acquisition device retains the local video recording.

[0120] The cloud video recording storage period refers to the time that the cloud server retains the cloud video recordings.

[0121] The local video recording storage period and the cloud video recording storage period can be the same or different; there is no limitation here.

[0122] Step S160: In response to the fact that the local video recording storage period is less than the cloud video recording storage period, determine the pre-upload time based on the local video recording storage period.

[0123] In some application scenarios, the local video recording storage period may be shorter than the cloud video recording storage period. Therefore, this application can also implement a pre-upload method for videos to be re-uploaded by analyzing the difference in storage periods between the local and cloud recordings.

[0124] For example, if the local video recording storage period is detected to be shorter than the cloud video recording storage period, the pre-upload time is determined based on the local video recording storage period.

[0125] The pre-upload time refers to the time during which the video to be re-uploaded must be completed. It's essentially another re-upload processing condition besides receiving a video re-upload request. This can be achieved by setting the local video storage period as the pre-upload time, or by setting a pre-upload time threshold. When the time difference between the current time and the local video storage period (end time) is less than the pre-upload time threshold (indicating that the local video is about to expire), the corresponding pre-upload processing is triggered.

[0126] For example, before local video recording data is about to be overwritten (such as on the Nth day before the local video recording storage period expires), the image acquisition device can automatically start a background pre-upload task to upload the video clips that still need to be retained on the cloud server but are about to be lost in the device's local storage to the cloud server.

[0127] In step S170, in response to the fact that no video re-upload request was received before the pre-upload time, the video to be re-uploaded is uploaded to the cloud server within the pre-upload time.

[0128] Based on the steps described above, in a specific application scenario, if no video re-upload request is received before the pre-upload time, the video to be re-uploaded will be uploaded to the cloud server within the pre-upload time.

[0129] If a video re-upload request is received before the pre-upload time, the re-uploaded video segments can be marked, and the pre-upload task in this embodiment can be cancelled subsequently.

[0130] Based on the above embodiments, this embodiment further explains the pre-upload mechanism in the aforementioned embodiments.

[0131] To address the additional write / erase burden that the pre-upload mechanism places on the device's storage chip, the device firmware can employ wear leveling algorithms (such as FTL-based block mapping strategies) and integrate them into the pre-upload process to optimize the write distribution of the storage medium.

[0132] For example, the pre-upload mechanism involves reading data from a storage medium (such as a memory card) and uploading it. Pre-upload itself does not add extra writes, but normal video recording and storage will continue to write to the memory card after the device is woken up. To cope with the write burden on the memory card from daily video recording and storage, the device firmware uses a preset wear leveling algorithm to distribute write operations across physical blocks, thereby significantly extending the lifespan of the memory card and improving the long-term reliability of the product.

[0133] Based on the above embodiments, this embodiment describes a method for end-to-cloud data synchronization between the image acquisition device and the cloud server in a video recording management system. The method includes steps S210 to S220.

[0134] Step S210: Obtain the local video recording list in the image acquisition device and the local video recording metadata of each local video recording in the local video recording list.

[0135] The local video recording list refers to the list of videos still stored on the device's local storage medium.

[0136] The interpretation of metadata can be found in the examples described in the foregoing embodiments, and will not be repeated here.

[0137] Step S220: Periodically synchronize the local video recording list and local video recording metadata to the cloud server.

[0138] To ensure consistency between the device and cloud states, the video recording management system in this application may introduce a state synchronization and conflict resolution protocol. Specifically, the device can periodically synchronize its list of valid locally recorded files and their recording metadata to the cloud server.

[0139] Therefore, the cloud server can update the status of each video file in a timely manner and accurately display it to the user through the client.

[0140] Based on the above embodiments, this embodiment illustrates the communication methods in the overall application scenario of this application.

[0141] For example, predictive connection management and efficient communication protocols can be set up in the overall application scenario of this application.

[0142] Specifically, the device can learn user behavior patterns through lightweight AI, thereby determining the high-probability and low-probability periods for triggering target events. During the predicted high-probability periods, the heartbeat interval between the device and the cloud server is shortened to ensure rapid connection response between the two. Similarly, the heartbeat interval can be lengthened during low-probability periods to control power consumption (saving electricity).

[0143] The method for adjusting the heartbeat interval can refer to the heartbeat mechanism in this technical field, and will not be elaborated here.

[0144] In addition, to reduce communication overhead and further lower power consumption and transmission latency, a simplified binary communication protocol can be used between the device and the cloud server. Here, "simplified" refers to optimization for low-power scenarios, which differs somewhat from ordinary binary protocols. Examples include reducing packet header size and compressing signaling, which will not be elaborated upon here.

[0145] In this embodiment, a custom binary protocol is adopted. By optimizing the packet header structure and compressing data fields, communication overhead can be reduced, enabling data exchange to be completed more efficiently within a short wake-up window.

[0146] It should be further noted that the entity executing the video recording management method can be a video recording management device. For example, the video recording management method can be executed by a terminal device, a server, or other processing devices. The terminal device can be a user equipment (UE), computer, mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, the video recording management method can be implemented by a processor calling computer-readable instructions stored in memory.

[0147] Figure 4 This is a block diagram illustrating a video recording management device according to an exemplary embodiment of this application. The device is applied to an image acquisition device, and a first communication connection exists between the image acquisition device and a cloud server. Figure 4 As shown, the exemplary video recording management device 300 includes: a local recording module 310, a re-transmission determination module 320, a current upload module 330, and a video re-transmission module 340. Specifically: The local recording module 310 is used to perform local recording processing on the first target event in response to the detection of the first target event, so as to obtain the first local recording.

[0148] The retransmission determination module 320 is used to determine the currently uploaded video and the video to be retransmitted in the first local video based on the first local video information and the device status information of the image acquisition device.

[0149] The current upload module 330 is used to determine the currently uploaded video and the video to be uploaded in the first local video based on the first local video recording information and the device status information of the image acquisition device.

[0150] The video re-transmission module 340 is used to respond to the video re-transmission request sent by the cloud server for the first local video recording and upload the video to be re-transmitted to the cloud server.

[0151] In this exemplary video recording management device, when a first target event is detected, a first local video is obtained by performing local recording processing on the first target event. The local video is stored on a local storage medium and needs to be uploaded to a cloud server to obtain a cloud video. In this application, during the process of uploading the local video to the cloud server, the local recording information and the device status information of the image acquisition device are comprehensively considered to determine which currently uploaded video needs to be uploaded first and which video awaits subsequent upload. The currently uploaded video is uploaded to the cloud server first. The segmented upload method allows for the priority upload of some videos when the network is poor, or proactive segmented upload to save power under normal network conditions. If a video re-upload request is received from the cloud server for the first local video, the video awaiting re-upload is then uploaded to the cloud server. The subsequent re-upload method ensures the consistency of data between the end and the cloud. This enables reasonable and efficient video management.

[0152] It should be noted that the apparatus and method provided in the above embodiments belong to the same concept, and the specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the apparatus provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the apparatus can be divided into different functional modules to complete all or part of the functions described above, and this is not a limitation.

[0153] The functions of each module can be found in the video recording management method implementation example, and will not be repeated here.

[0154] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of an embodiment of the electronic device of this application. The electronic device 100 includes a memory 101 and a processor 102. The processor 102 is used to execute program instructions stored in the memory 101 to implement the steps in any of the above-described video recording management method embodiments. In a specific implementation scenario, the electronic device 100 may include, but is not limited to, a microcomputer or a server. In addition, the electronic device 100 may also include mobile devices such as laptops and tablets, which are not limited here.

[0155] Specifically, processor 102 controls itself and memory 101 to implement the steps in any of the above-described video recording management method embodiments. Processor 102 can also be referred to as a CPU (Central Processing Unit). Processor 102 may be an integrated circuit chip with signal processing capabilities. Processor 102 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. Furthermore, processor 102 can be implemented using integrated circuit chips.

[0156] In this exemplary electronic device, upon detecting the triggering of a first target event, a first local video recording is obtained by performing local recording processing on the first target event. The local video recording is stored on a local storage medium and needs to be uploaded to a cloud server to obtain a cloud video recording. In this application, during the process of uploading the local video recording to the cloud server, the local recording information and the device status information of the image acquisition device are comprehensively considered to determine which currently uploaded video recording needs to be uploaded first and which recordings awaiting subsequent upload. The currently uploaded video recording is uploaded to the cloud server first. The segmented upload method allows for the priority upload of some recordings when the network is poor, or proactive segmented upload to save power under normal network conditions. If a recording re-upload request is received from the cloud server for the first local video recording, the recording to be re-uploaded is then uploaded to the cloud server. The subsequent re-upload method ensures the consistency of data between the end and the cloud. This enables reasonable and efficient video recording management.

[0157] Please see Figure 6 , Figure 6 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 110 stores program instructions 111 that can be executed by a processor. The program instructions 111 are used to implement the steps in any of the above-described video recording management method embodiments.

[0158] In this exemplary storage medium, by running the program instructions in the storage medium, when a first target event is detected, the first target event is locally recorded to obtain a first local video recording. The local video recording is stored in the local storage medium and needs to be uploaded to a cloud server to obtain a cloud video recording. In this application, during the process of uploading the local video recording to the cloud server, the local recording information and the device status information of the image acquisition device are comprehensively considered to determine which currently uploaded video recording needs to be uploaded first and which recordings awaiting subsequent upload. The currently uploaded video recording is uploaded to the cloud server first. The segmented upload method allows for prioritizing the upload of some recordings when the network is poor, or actively segmenting uploads to save power under normal network conditions. If a recording re-upload request is received from the cloud server for the first local video recording, the recording to be re-uploaded is then uploaded to the cloud server. The subsequent re-upload method ensures the consistency of data between the end and the cloud. This allows for reasonable and efficient video recording management.

[0159] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0160] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

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

[0162] 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. 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 medium. 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 storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A video recording management method, characterized in that, The method is applied to an image acquisition device, wherein the image acquisition device has a first communication connection with a cloud server, and the method includes: In response to the detection of a first target event, local recording processing is performed on the first target event to obtain a first local recording; Based on the first local recording information of the first local recording and the device status information of the image acquisition device, determine the currently uploaded recording and the recording to be re-uploaded in the first local recording; Upload the currently uploaded video to the cloud server; In response to receiving a video re-upload request from the cloud server for the first local video recording, the video recording to be re-uploaded is uploaded to the cloud server.

2. The method according to claim 1, characterized in that, The step of determining the currently uploaded video and the video to be re-uploaded in the first local video based on the first local video recording information and the device status information of the image acquisition device includes: The current upload duration is determined based on the first local recording information of the first local recording and the device status information of the image acquisition device; Based on the current upload duration, the first local video is divided into the currently uploaded video and the video to be uploaded.

3. The method according to claim 2, characterized in that, The first local recording information includes a first local recording duration, and the device status information includes a device sleep countdown, remaining device battery power, and recording upload power consumption. Determining the current upload duration based on the first local recording information and the device status information of the image acquisition device includes: The remaining upload time is determined based on the remaining battery power of the device and the energy consumption of the video upload. The minimum value among the first local recording duration, the device sleep countdown, and the remaining upload time is determined as the current upload duration.

4. The method according to claim 1, characterized in that, Uploading the currently uploaded video to the cloud server includes: In response to the detection of a second target event, the uploading of the currently uploaded video to the cloud server is paused or stopped, and the first video metadata of the first local video is obtained and uploaded to the cloud server. The second target event is processed for local recording to obtain a second local recording; A portion of the recordings from the second local recording is uploaded to the cloud server.

5. The method according to claim 1, characterized in that, Before uploading the video recording to be re-uploaded to the cloud server, the method further includes: In response to receiving a video retransmission request from the cloud server for the first local video recording, determine whether the first local video recording exists in the local video recording list of the image acquisition device; If not, notify the cloud server that the first local recording has been lost.

6. The method according to claim 1, characterized in that, The cloud server and the client have a second communication connection; the video re-upload request is generated by the client based on the prediction of the user's viewing intention for the first local video and sent to the cloud server.

7. The method according to claim 1, characterized in that, After uploading the currently uploaded video to the cloud server, the method further includes: Obtain the local video recording storage period and the cloud video recording storage period; In response to the fact that the local video recording storage period is less than the cloud video recording storage period, the pre-upload time is determined according to the local video recording storage period; If no video re-upload request is received before the pre-upload time, the video to be re-uploaded is uploaded to the cloud server within the pre-upload time.

8. The method according to claim 1, characterized in that, The method further includes: Obtain the local video recording list in the image acquisition device and the local video recording metadata of each local video recording in the local video recording list; The local video recording list and the local video recording metadata are periodically synchronized to the cloud server.

9. An electronic device, characterized in that, The method includes a memory and a processor, the processor being configured to execute program instructions stored in the memory to implement the method according to any one of claims 1 to 8.

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

Images