Video uploading method, video reviewing method, device, equipment and storage medium

Abstract

The application provides a video uploading method, a video review method, a device, equipment and a storage medium, and belongs to the technical field of data storage. The method comprises the following steps: in response to a live broadcast wake-up event, transmitting a live broadcast video code stream in a first transmission period of a live broadcast wake-up time window, and sending local storage video data to a cloud storage end in a second transmission period of the live broadcast wake-up time window; the local storage video data is video data collected and saved to a video shooting device in response to other wake-up events except the live broadcast wake-up event. According to the application, the second transmission period is opened to supplement the local storage video data to the cloud storage end in the gap of transmitting the live broadcast video code stream in response to the live broadcast wake-up event starting the live broadcast wake-up time window, a video uploading scheme for reducing unnecessary response wake-up, avoiding redundant data and uploading data in order is realized, and the power consumption of the video shooting device is further reduced and the endurance time is prolonged.

Description

Technical Field

[0001] This invention relates to the field of data storage technology, and in particular to a video uploading method, a video playback method, an apparatus, a device, and a storage medium. Background Technology

[0002] Always-On Video (AOV) technology is a core solution for low-power video shooting equipment, and video shooting equipment using AOV technology is also known as AOV equipment. Generally speaking, battery-powered AOV equipment solves the problem that traditional event-triggered recording cannot cover 24 hours a day by using a hybrid working mode of "low frame rate recording during sleep + high frame rate recording when triggered by events".

[0003] However, because AOV devices need to respond to multiple wake-up events in hybrid working mode, such as live broadcast wake-up events, playback wake-up events, and memory full wake-up events, each wake-up requires switching from a low-power sleep state to a high-power wake-up state, switching from collecting low-frame-rate audio and video data to collecting high-frame-rate audio and video data, and simultaneously transferring some or all of the high-frame-rate data to the cloud storage. Meanwhile, other high-frame-rate data not stored in the cloud and low-frame-rate data collected in the sleep state are stored locally on the AOV device. This leads to unnecessary wake-ups and collection of redundant data, causing a surge in AOV device power consumption, as well as the problem of disordered data collection and uploading, which increases the power consumption of the AOV device.

[0004] For example, in the playback wake-up event response where there is no need to collect data at a high frame rate, the AOV device needs to be woken up by acquiring data stored locally on the device. As a result, the AOV device will continue to collect static scene data at a high frame rate after being woken up, which will increase the power consumption of the AOV device.

[0005] Furthermore, these static scene data and the high frame rate data that are necessary to collect in the response to motion wake-up events and live wake-up events are generally uploaded to the cloud in the order of collection time. However, due to the need to transmit static scene data, the high frame rate data collected later in response to motion wake-up events and live wake-up events may not be uploaded to the cloud in time. This requires additional waking of the AOV device for data transmission, resulting in a significant increase in the power consumption of the AOV device and a shorter battery life. Summary of the Invention

[0006] This invention provides a video uploading method, a video playback method, an apparatus, a device, and a storage medium to solve the defects in the prior art, such as unnecessary waking up of AOV devices, collection of redundant data, disordered data uploading, and transmission conflicts, which lead to increased power consumption and shorter battery life of AOV devices.

[0007] This invention provides a video uploading method, applied to a video shooting device, comprising: In response to a live stream wake-up event, the live video stream is transmitted during the first transmission period of the live stream wake-up time window, and the locally stored video data is sent to the cloud storage terminal during the second transmission period of the live stream wake-up time window. The locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live broadcast wake-up event.

[0008] According to a video uploading method provided by the present invention, the transmission of a live video stream includes: sending the live video stream to a live streaming server; the live streaming server being used to send the live video stream to a user terminal that triggers the live wake-up event; the live streaming server being further used to generate a live video slice in cloud storage format based on the live video stream, and to send the live video slice to the cloud storage terminal.

[0009] According to a video uploading method provided by the present invention, the locally stored video data includes at least one of first event video data and second event video data; when the locally stored video data includes the first event video data, before responding to a live broadcast wake-up event, the method further includes: in response to a first wake-up event, acquiring the first event video data at a first frame rate and storing the first event video data in the storage module of the video shooting device; the first wake-up event is triggered when the rate of change of the image within the field of view of the video shooting device is greater than or equal to a preset rate of change threshold; when the locally stored video data includes the second event video data, before responding to a live broadcast wake-up event, the method further includes: in response to a second wake-up event, writing the continuously acquired second event video data at a second frame rate from the memory of the video shooting device to the storage module; wherein, the first frame rate is greater than the second frame rate.

[0010] According to a video uploading method provided by the present invention, when the locally stored video data includes first event video data and second event video data, the step of sending the locally stored video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window includes: sending the first event video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window; and continuing to send the second event video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window after all the first event video data has been sent to the cloud storage terminal.

[0011] According to a video uploading method provided by the present invention, the second wake-up event is any one of a memory full wake-up event, a timed wake-up event, and a playback wake-up event.

[0012] According to a video uploading method provided by the present invention, after transmitting the live video stream during a first transmission period of the live wake-up time window in response to a live wake-up event, and sending locally stored video data to the cloud storage terminal during a second transmission period of the live wake-up time window, the method further includes: if not all of the locally stored video data is sent to the cloud storage terminal during the second transmission period of the live wake-up time window, then, if the network status of the video shooting device is idle, sending the unsent locally stored video data to the cloud storage terminal.

[0013] The present invention also provides a video playback method, applied to a user terminal, comprising: Send a video playback request to the cloud storage terminal; the video playback request includes the video playback time and wake-up event tag; The system receives a video playback file sent by the cloud storage terminal; the video playback file is determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes the live video stream and locally stored video data. The live video stream and the locally stored video data are transmitted based on any of the video upload methods described above.

[0014] The present invention also provides a video uploading device, deployed on a video shooting device, comprising: The dual transmission module is used to respond to a live wake-up event by transmitting the live video stream during the first transmission period of the live wake-up time window and sending the locally stored video data to the cloud storage terminal during the second transmission period of the live wake-up time window. The locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live broadcast wake-up event.

[0015] The present invention also provides a video playback device, deployed on a user terminal, comprising: The sending module is used to send video playback requests to the cloud storage terminal; the video playback request includes video playback time and wake-up event tags; A receiving module is used to receive video playback files sent by the cloud storage terminal; the video playback files are determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes live video streams and locally stored video data; The live video stream and the locally stored video data are transmitted using the video upload device described above.

[0016] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement any of the video uploading methods or video playback methods described above.

[0017] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the video uploading methods or video playback methods described above.

[0018] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements any of the video uploading methods or video playback methods described above.

[0019] The video uploading method, video playback method, apparatus, device, and storage medium provided by this invention, by storing video data collected in response to wake-up events other than live wake-up events as local storage video data on the video shooting device, and then, during the interval between the live wake-up time window in response to a live wake-up event to transmit the live video stream, opening a second transmission period to supplement the local storage video data to the cloud storage, this enables the video shooting device to upload local storage video data of other wake-up events to the cloud storage during live wake-up, avoiding additional unnecessary wake-ups to the video shooting device when uploading local storage video data; furthermore, by separating the live wake-up time window into two different transmission periods to transmit the live video stream and the locally stored video data separately, this invention achieves video playback functionality. The orderly uploading of video data avoids conflicts during video transmission that could cause live stream interruptions and necessitate additional device wake-ups for data retransmission, ensuring smooth live streaming. Simultaneously, by completing the transmission and cloud storage of the live video stream and locally stored video data during the live stream wake-up period, user terminals only need to retrieve the video playback file from the cloud storage when watching the video, eliminating the need to wake up the video recording device. This prevents the video recording device from entering a high-power state of high frame rate video capture in response to playback wake-up events. Furthermore, by avoiding redundant data generated in response to playback wake-up events, the number of times the video recording device responds to full storage wake-up events is reduced. Ultimately, this achieves a video upload solution that reduces unnecessary wake-up responses, avoids redundant data generation, and ensures orderly data upload, further reducing the power consumption of video recording devices and extending battery life. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a flowchart illustrating the video uploading method provided by the present invention.

[0022] Figure 2 This is a schematic diagram of the video uploading and playback system provided by the present invention.

[0023] Figure 3 This is a flowchart illustrating the video playback method provided by the present invention.

[0024] Figure 4 This is a schematic diagram of the video uploading device provided by the present invention.

[0025] Figure 5 This is a schematic diagram of the video playback device provided by the present invention.

[0026] Figure 6 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0028] It should be noted that, in the description of this invention, the term "comprising" or any other variations thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Those skilled in the art will understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0029] The terms "first," "second," etc., used in this invention are used to distinguish similar objects, not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0030] The following is combined Figures 1-6This invention describes the video uploading method, video playback method, apparatus, device, and storage medium provided by the present invention.

[0031] AOV technology is a core solution for low-power video shooting equipment. It generally solves the problem that traditional "event-triggered recording" (such as PIR infrared triggering) of video shooting equipment cannot cover 24 hours a day by using a hybrid mode of "low frame rate (such as 1-2 frames / second) recording during sleep + high frame rate (such as 15-30 frames / second) recording when triggered by events".

[0032] Video recording equipment based on AOV technology, also known as AOV equipment, typically includes an acquisition module, a processing module, a storage module, a communication module, and a power management module. The acquisition module can be a camera that supports dynamic frame rate adjustment, the processing module can be an embedded chip responsible for encoding and event judgment, the storage module can be a local memory such as eMMC or SD card, the communication module can be a Wi-Fi module or Bluetooth module responsible for data transmission, and the power management module can be used to control sleep state and wake-up state (active state).

[0033] The core application logic of AOV devices is "low-power standby + on-demand wake-up". In sleep mode, only low-power acquisition function is retained. The AOV device only acquires data at a low frame rate and temporarily caches it in memory. When the wake-up event is triggered, the AOV device switches from sleep mode to wake-up mode and performs high frame rate acquisition, data transmission and storage operations.

[0034] Low-power AOV equipment typically uses batteries or solar panels for auxiliary power. Its power consumption level directly determines the equipment's endurance. For example, if the battery capacity of an AOV equipment is fixed, reducing power consumption by 50% can double the endurance. Therefore, reducing the power consumption throughout the equipment's life cycle has become the core technical requirement for low-power AOV equipment.

[0035] To extend the battery life of low-power AOV devices as much as possible, we have explored AOV device application solutions in areas such as video capture and local storage, cloud storage and upload mechanisms, live streaming and playback, and upload scheduling logic.

[0036] Regarding video capture and local storage, the AOV device employs a low-power mode in sleep mode, capturing video data at a low frame rate (e.g., 1 frame / second) and temporarily caching it in the device's memory. The device's memory capacity is designed for a maximum cache of 30 minutes to avoid frequent wake-ups. When a wake-up event is triggered, the AOV device switches from sleep mode to wake mode and captures audio and video data at a high frame rate (e.g., 15-30 frames / second), while simultaneously writing the cached data in memory to the AOV device's storage module (e.g., eMMC / SD card). After completing local storage, the device enters sleep mode from wake mode.

[0037] Among them, wake-up events include, but are not limited to, any one of the following: live broadcast wake-up event, motion wake-up event, memory full wake-up event, timed wake-up event, and playback wake-up event.

[0038] For example, when the memory full wake-up event is triggered, it indicates that the memory cache of the AOV device has reached a threshold, such as accumulating 30 minutes of low frame rate data in the cache. The AOV device is then woken up, and it enters the wake-up state from the sleep state. The low frame rate data in memory is stored in the storage module until all the low frame rate data in memory is stored in the storage module, and then the AOV device enters the sleep period.

[0039] For example, when a timed wake-up event is triggered, such as when the AOV device has been in a sleep state for a full hour, the AOV device is woken up. The AOV device enters the wake-up state from the sleep state, collects audio and video data at a high frame rate, and stores the low frame rate data in memory into the storage module.

[0040] Regarding the cloud storage upload mechanism, when a critical wake-up event is triggered, the AOV device encodes the high-frame-rate audio and video segments captured locally into cloud storage segments and uploads them to the cloud storage terminal (referred to as cloud storage) via the network. Low-frame-rate data captured during non-critical wake-up events or when there is no wake-up event will be stored in the device's local memory or storage module and will not be uploaded to the cloud storage terminal.

[0041] For example, when a motion wake-up event is triggered, the AOV device enters the wake-up state from the sleep state, collects audio and video data at a high frame rate, encodes the high frame rate audio and video data into cloud storage segments, and uploads them to the cloud storage terminal.

[0042] Regarding live streaming and replay, when a live streaming wake-up event is triggered, the AOV device enters a wake-up state from sleep mode, acquires audio and video data at a high frame rate, and generates two high frame rate streams. One stream is pushed live for viewing to ensure the real-time nature of the live stream, while the other stream is delayed, sliced, and uploaded to cloud storage. When a replay wake-up event is triggered, the AOV device acquires audio and video data at a high frame rate and transmits the low frame rate data stored locally on the device to the user terminal. After the live stream or replay ends, the AOV device enters a sleep period and resumes acquiring audio and video data at a low frame rate.

[0043] Regarding the upload scheduling logic, the uploading of audio and video data collected by the AOV device to cloud storage depends on event triggering or users watching live streams. When the AOV device is uploading audio and video data, it is in a wake-up state, collecting audio and video data at a high frame rate. Furthermore, if a single transmission fails, the device will typically be woken up again to retry the transmission after a certain interval (e.g., 5 minutes), which will also wake up the AOV device.

[0044] Compared to collecting audio and video data at a high frame rate 24 hours a day, the exploration of AOV equipment applications in video acquisition and local storage, cloud storage and upload mechanisms, live streaming and playback, and upload scheduling logic has reduced the power consumption of AOV equipment. However, various wake-up events can still cause a surge in the power consumption of AOV equipment. Furthermore, high frame rate acquisition is performed in unnecessary scenarios where only low frame rate data needs to be collected, resulting in redundant data. In addition, the disordered upload of collected data may conflict with the live stream, causing live stream stuttering.

[0045] In playback wake-up events, existing cloud storage typically serves only as "critical event backup," such as backing up only high-frame-rate audio and video data captured in response to live streaming and motion wake-up events. It doesn't cover all historical data, with the remaining data stored locally on the AOV device. This means playback operations still rely on the AOV device's local storage. Each time a user performs a playback, the device needs to be woken up, transitioning from sleep to active mode and reading local data for transmission, resulting in a 10-20 fold increase in power consumption. Under these circumstances, even frequent short playbacks (e.g., 5 times a day, 30 seconds each time) will lead to additional power consumption, significantly shortening battery life. For example, the battery life of a battery-powered AOV device might drop from 30 days to 20 days. Furthermore, when a playback wake-up event is triggered, even if only low-frame-rate data is needed, the woken AOV device lacks priority for wake-up events and will still capture data at a high frame rate, generating a large amount of redundant data in this unnecessary scenario, further increasing energy consumption during data transmission and storage.

[0046] During live stream wake-up events, AOV devices need to simultaneously capture the "live stream bitrate" and generate "cloud storage fragments," transmitting two data streams. This significantly increases the device's power consumption, resulting in shorter battery life for battery-powered AOV devices. Furthermore, AOV devices often lack priority management during data transmission. The live stream bitrate, high-frame-rate data (critical data) captured in response to motion wake-up events, and low-frame-rate data captured in sleep mode are all uploaded out of order. This can easily lead to delays in the transmission of live stream data or critical data due to bandwidth occupation, ultimately causing live stream stuttering and potentially requiring additional device wake-ups for retransmission.

[0047] In view of this, the present invention provides a video uploading method, a video playback method, an apparatus, a device, and a storage medium to solve at least one of the aforementioned problems of power consumption surge caused by playback wake-up, energy waste caused by redundant data acquisition and transmission, and inefficient upload scheduling.

[0048] Figure 1 This is a flowchart illustrating the video upload method provided by the present invention, as shown below. Figure 1As shown, the video uploading method is applied to a video shooting device, including but not limited to step 101.

[0049] It is understood that the video shooting device has the necessary functions such as acquisition, processing, storage, communication and power management to realize the acquisition, processing, storage and uploading of live video streams and locally stored video data.

[0050] Optionally, the video recording device is an AOV device.

[0051] Alternatively, the video shooting device is battery powered; or, the video shooting device is primarily battery powered and supplemented by solar panels.

[0052] For example, AOV (Automated Optical Video) devices whose video recording equipment is powered by batteries.

[0053] Step 101: In response to the live broadcast wake-up event, transmit the live video stream during the first transmission period of the live broadcast wake-up time window, and send the locally stored video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window.

[0054] Locally stored video data refers to video data collected and saved to the video shooting device in response to wake-up events other than live broadcast wake-up events.

[0055] The live streaming wake-up event is an activation event that triggers the video shooting device to switch from a low-power sleep state to an active live streaming processing state and start live streaming processing. The live streaming processing state indicates that the video shooting device needs to collect high frame rate video data streams and transmit them in real time so that the user's APP can receive the live video stream in a timely manner.

[0056] The live video stream is a high-frame-rate video data stream that is captured in real time by the video shooting device in response to a live wake-up event; the locally stored video data is the video data that is captured and saved to the video shooting device in response to other wake-up events besides the live wake-up event before the live wake-up event; among them, other wake-up events include, but are not limited to, any one of the following wake-up events: motion wake-up event, memory full wake-up event, timed wake-up event, and playback wake-up event.

[0057] The priority of the live wake-up event is higher than that of other wake-up events. For live video streams captured in real time in response to the highest priority live wake-up event, real-time transmission will be performed. For video data captured in response to other wake-up events of other priorities, real-time transmission is not required. Instead, the data is first stored locally in the storage module of the video shooting device or cached in memory as local storage video data. Then, when the live wake-up event is triggered, the locally stored video data will be sent to the cloud storage.

[0058] Live broadcast wake-up events can be any of the following: a user actively initiates a live broadcast viewing request through the APP, the preset live broadcast reservation time is reached, or a reconnection request used for abnormal recovery after a live broadcast transmission interruption.

[0059] The live stream wake-up time window is a structured, finite time interval opened by the video recording device in response to a live stream wake-up event, used for transmitting the live video stream. It typically consists of multiple first transmission periods and multiple second transmission periods. The first transmission period is the time interval within the live stream wake-up time window used for transmitting the live video stream; the second transmission period is the time interval within the live stream wake-up time window used for transmitting locally stored video data. The durations of the first transmission periods can be the same or different; the durations of the second transmission periods can also be the same or different.

[0060] Optionally, each first transmission period and each second transmission period in the live broadcast wake-up time window are set alternately.

[0061] The cloud storage terminal is a cloud server used to store all video data (including live video streams and locally stored video data) captured by video shooting equipment, and to return the target playback video data to the user terminal in response to a video playback request initiated by the user terminal.

[0062] Specifically, the live streaming wake-up event is triggered when a user initiates a live streaming viewing request through the APP or when the preset live streaming reservation time is reached. In response to the live streaming wake-up event, the video shooting device enters an active state of high power consumption and high frame rate video acquisition from a low power sleep state, opens the live streaming wake-up time window and acquires high frame rate live video streams in real time.

[0063] On the one hand, during the first transmission period of the live broadcast wake-up time window, the video capturing device transmits the live video stream so that the user terminal and the cloud storage terminal can receive the live video stream. This includes sending the live video stream directly to the user terminal, or transmitting the live video stream in segments to the cloud storage terminal, or transmitting the live video stream to the live broadcast server first, and then forwarding it to the cloud storage terminal and the user terminal by the live broadcast server. On the other hand, during the second transmission period of the live broadcast wake-up time window, the video capturing device sends the locally stored video data previously collected in response to other wake-up events to the cloud storage terminal so that the cloud storage terminal stores all the video data collected by the video capturing device. Ultimately, after responding to the video playback request sent by the user terminal, the cloud storage terminal can determine the video playback file from the complete live video stream stored in the cloud storage terminal and the locally stored video data and return it to the user terminal.

[0064] For example, the first transmission period is set to 3 seconds and the second transmission period is set to 500 ms. When the video shooting device is woken up in response to the live wake-up event, the live wake-up time window is opened. Locally stored video data is transmitted during the intervals between the transmission of the live video stream. First, the 3-second live video stream is transmitted, then the 500-ms local stored video data is transmitted, then the 3-second live video stream is transmitted again, and so on, until the live wake-up time window is closed and the data transmission is terminated, or the local stored video data transmission is terminated after the data transmission is completed.

[0065] Optionally, if all locally stored video data is not transmitted within a single live stream wake-up time window, the breakpoint is recorded, and the transmission of locally stored video data continues from the breakpoint before the next live stream wake-up event response, thus avoiding duplicate transmission.

[0066] Optionally, each first transmission period is longer than any second transmission period in order to prioritize the transmission of high frame rate real-time captured live video streams, ensuring that the live video streams are transmitted completely and guaranteeing that users enjoy a smooth live streaming experience.

[0067] Optionally, each first transmission period is longer than any second transmission period, and the throughput of each second transmission period is greater than that of any first transmission period. This allows for the transmission of locally stored video data with a larger throughput within a shorter second transmission period. This ensures that even when the amount of locally stored video data is large, all locally stored video data can be transmitted to the cloud storage terminal within the live broadcast wake-up time window, thus achieving full data storage on the cloud storage terminal.

[0068] In relevant AOV device video upload solutions, the AOV device needs to respond to a storage full wake-up event, enter an active state of high frame rate video capture, and then upload the locally stored video data captured at high frame rate to the cloud storage. At the same time, the AOV device will save the low frame rate video locally, and needs to enter an active state of high frame rate video capture in response to a playback wake-up event before returning the low frame rate video locally to the user terminal. This results in a surge in the AOV device's power consumption and a shortened battery life.

[0069] The video uploading method provided by this invention stores video data collected in response to wake-up events other than the live wake-up event as local storage video data on the video shooting device. Then, during the interval between the live wake-up time window that initiates the live wake-up event to transmit the live video stream, a second transmission period is established to supplement the local storage video data to the cloud storage. This enables the video shooting device to upload local storage video data for other wake-up events to the cloud storage during the live wake-up period, avoiding unnecessary additional wake-ups to the video shooting device when uploading local storage video data. Furthermore, by separating the live wake-up time window into two different transmission periods to transmit the live video stream and local storage video data separately, orderly uploading of video data is achieved, avoiding... This solution avoids conflicts during video transmission that could cause live stream interruptions or require additional device wake-ups to retransmit data, ensuring smooth live streaming. Simultaneously, by completing the transmission and cloud storage of the live video stream and locally stored video data during the live stream wake-up period, user terminals only need to retrieve the video playback file from the cloud storage when watching the video, eliminating the need to wake up the video recording device. This prevents the video recording device from entering a high-power state of high frame rate video capture in response to playback wake-up events. Furthermore, by avoiding redundant data generated from playback wake-up events, the number of times the video recording device responds to full storage wake-up events is reduced. Ultimately, this achieves a video upload solution that reduces unnecessary wake-up responses, avoids redundant data, and ensures orderly data upload, further reducing the power consumption of video recording devices and extending battery life.

[0070] Based on the above embodiments, as an optional embodiment, the transmission of the live video stream includes: Send the live video stream to the live streaming server; The live streaming server is used to send the live video stream to the user terminal that triggered the live streaming wake-up event; The live streaming server is also used to generate live video slices in cloud storage format based on the live video bitstream, and send the live video slices to the cloud storage terminal.

[0071] Among them, the live streaming server is a cloud server or hardware server that is independent of the video shooting equipment.

[0072] Cloud storage format is a video data structure optimized for cloud storage environments. It converts the original live video stream into a structured slice format that adapts to the characteristics of cloud storage.

[0073] Specifically, Figure 2 This is a schematic diagram of the video uploading and playback system provided by the present invention, as shown below. Figure 2As shown, in response to the live stream wake-up event, the video capture device transitions from sleep mode to an active state of high-power, high-frame-rate video capture, and opens the live stream wake-up time window. At this time, the video capture device only captures and generates one live video stream in real-time, such as TS (Transport Stream) format. It does not perform separate cloud storage fragmentation on the live video stream; instead, during the first transmission period of the live stream wake-up time window, it directly transmits the high-frame-rate live video stream to the live stream server.

[0074] Upon receiving the live video stream in real time, the live streaming server forwards the stream to the user terminal that triggered the live wake-up event of the video shooting device for viewing on the user terminal's app. Simultaneously, the live streaming server segments the stream at preset time intervals (e.g., 5 seconds, 10 seconds, 20 seconds) to generate cloud-store format live video segments. These segments are then sent to the cloud storage terminal via a transfer interface, where they are assembled into a complete historical record for storage.

[0075] Optionally, the transfer interface is an API interface provided by the Object Storage Service (OSS) platform.

[0076] In the relevant AOV device video upload solution, after the AOV device responds to the live broadcast wake-up event, it generates two high frame rate live video streams. One stream is pushed to the user terminal in real time so that the user can watch the live broadcast, and the other stream is uploaded to the cloud storage after being delayed and sliced.

[0077] The video uploading method provided by this invention directly transmits a single live video stream captured in real time from a video shooting device to a live streaming server independent of the video shooting device. The independent live streaming server performs the transfer and storage processing of the live video stream, including user terminal forwarding processing and cloud storage segment transmission and storage processing. This avoids generating, processing, and transmitting two live video streams locally on the video shooting device, eliminates the need for the video shooting device to generate storage segments, and saves the power consumption of uploading cloud storage segments separately through the transfer interface provided by the video shooting device through OSS platform, etc., further reducing the power consumption of the video shooting device and increasing its battery life.

[0078] Based on the above embodiments, as an optional embodiment, the locally stored video data includes at least one of first event video data and second event video data; If the locally stored video data includes the first event video data, the method further includes, prior to responding to the live stream wake-up event: In response to a first wake-up event, video data of the first event is acquired at a first frame rate and stored in the storage module of the video shooting device; the first wake-up event is triggered when the rate of change of the image within the field of view of the video shooting device is greater than or equal to a preset rate of change threshold. If the locally stored video data includes the second event video data, the method further includes, prior to responding to the live stream wake-up event: In response to the second wake-up event, the second event video data at the second frame rate that is continuously collected is written from the memory of the video shooting device to the storage module; Wherein, the first frame rate is greater than the second frame rate.

[0079] The first wake-up event, also known as the motion wake-up event, is a wake-up event triggered within a preset time range (such as 1 second or 0.5 seconds) when the rate of change of the image within the field of view of the video recording device is greater than or equal to a preset rate of change threshold. For example, when a moving pedestrian or animal appears within the field of view of the video recording device, the rate of change of the image within the field of view is greater than or equal to the preset rate of change threshold, thus triggering the motion wake-up event.

[0080] It is understood that the preset rate of change threshold can be determined in advance based on factors such as the size of the field of view of the video shooting device, the setting position of the video shooting device, and historical motion video data, and this invention does not limit this.

[0081] The motion trigger event is an activation event that triggers the video capturing device to switch from a low-power sleep state to an active state of motion processing and to perform motion acquisition and processing. The motion processing state indicates that the video capturing device needs to acquire high frame rate video data, but does not need to transmit the acquired high frame rate video data in real time. Instead, the high frame rate video data can be transmitted to the device.

[0082] The second wake-up event, also known as the static scene wake-up event, is triggered when the rate of change of the image within the field of view of the video capturing device is less than a preset rate of change threshold. This is a wake-up event other than the first wake-up event and the live streaming wake-up event. In this case, the video capturing device maintains a low frame rate, including but not limited to any of the static scene wake-up events such as memory full wake-up event, timed wake-up event, and playback wake-up event. The first frame rate is the frame rate at which the video data for the first event is captured; the second frame rate is the frame rate at which the video data for the second event is captured.

[0083] The video data captured by the video shooting device under the first and second wake-up events will be stored locally on the device (in memory or SD card) as local storage video data, so that it can be uploaded to the cloud storage in subsequent live wake-up events.

[0084] Among them, the memory full wake-up event is triggered when the memory is full (i.e., the available memory capacity reaches a preset threshold or is completely full), which triggers the video shooting device to enter the memory migration state from the low-power sleep state, write the low frame rate video data cached in memory to the storage module (such as SD card), and maintain the low frame rate video capture. The timed wake-up event is triggered at preset time intervals (such as 30 minutes, 1 hour, etc.) to trigger the video shooting device to routinely write the low frame rate video data cached in memory to the storage module for data synchronization. The playback wake-up event is triggered when the cloud storage terminal returns the video playback file to the user.

[0085] Generally, a live stream wake-up event indicates that the user needs to watch the captured content in real time, thus requiring high frame rate and high definition video capture and transmission in real time, and has the highest priority. A motion wake-up event indicates that a critical event has occurred within the market range of the video capture equipment, requiring detailed recording at high frame rate and high definition, but not real-time transmission, and has the second highest priority. A static scene wake-up event indicates that the video capture equipment does not need to capture or transmit data at a high frame rate, only low frame rate video capture is required, and has the lowest priority. Therefore, the first frame rate should be equal to or less than the capture frame rate of the live video stream; the first frame rate should be greater than the second frame rate to reduce the amount of invalid high frame rate data captured under static scene wake-up events.

[0086] For example, the first frame rate and the capture frame rate of the live video stream are both 15~30 frames / second to meet the video capture needs of users for live streaming, sports recording, etc. The second frame rate is 1~2 frames / second to maintain the minimum frame rate limit for video data capture and not to capture high frame rate video data.

[0087] Specifically, before the video shooting device responds to the live wake-up event, opens the live wake-up time window, and transmits the locally stored video data to the cloud storage terminal during the second transmission period, it is ensured that the storage module of the video shooting device contains the high frame rate first event video data collected in response to the first wake-up event, and / or the low frame rate second event video data collected in response to the second wake-up event.

[0088] When the rate of change of the image within the field of view of the video shooting device is greater than or equal to a preset rate of change threshold, the first wake-up event is triggered. In response to the first wake-up event, the video shooting device switches from a low-power sleep state to a high-power active state, acquires the first event video data at a higher first frame rate, and directly stores the first event video data in the storage module such as the SD card of the video shooting device, so that the first event video data becomes the local storage video data to be retransmitted during the live broadcast response.

[0089] If the live broadcast wake-up event and the first wake-up event are not triggered, and any one of the following conditions is met, such as full memory, routine synchronization, or playback wake-up, the second wake-up event is triggered. The second event video data that is continuously collected and temporarily cached in memory is written to the storage module so that the second event video data becomes the local storage video data to be transmitted during the live broadcast response.

[0090] In other words, in this embodiment, the high frame rate first event video data is directly stored in the storage module after acquisition, and the memory of the video shooting device only caches the continuously acquired low frame rate second event video data, so as to reduce the number of times the video shooting device responds to the memory full wake-up event.

[0091] The video uploading method provided by this invention utilizes contextualized data generation and transmission scheduling to store video data generated in response to first and second wake-up events (excluding live wake-up events) in a storage module. This data serves as local storage for the video shooting device, awaiting subsequent responses to live wake-up events. The data is then transmitted to cloud storage during a second transmission period within the live wake-up time window. Furthermore, by directly storing high-frame-rate first event video data captured in motion scenarios in the storage module, while continuously captured low-frame-rate second event video data is first stored in memory and written to the storage module upon triggering the second wake-up event, the number of wake-up events triggered by full memory is reduced. This overall optimization of the video shooting device's wake-up mechanism, through a priority and frame rate control mechanism among live wake-up events, motion wake-up events, and other wake-up events, ensures that high-frame-rate capture is enabled only in preset high-priority live wake-up and motion wake-up events. This further reduces unnecessary wake-up-induced invalid and redundant data, thereby reducing the power consumption of the video shooting device.

[0092] Based on the above embodiments, as an optional embodiment, the second wake-up event is any one of a memory full wake-up event, a timed wake-up event, and a lookback wake-up event.

[0093] Based on the above embodiments, as an optional embodiment, when the locally stored video data includes first event video data and second event video data, the step of sending the locally stored video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window includes: During the second transmission period of the live broadcast wake-up time window, the first event video data is sent to the cloud storage terminal; If all the video data of the first event is sent to the cloud storage terminal, the video data of the second event will continue to be sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window.

[0094] Specifically, when the locally stored video data includes both first event video data and second event video data collected and stored due to wake-up events in both moving and static scenes, data will be transmitted in descending order of transmission queue priority after the video shooting device responds to the live broadcast wake-up time window.

[0095] First, the live video stream has the highest transmission queue priority. Therefore, the first transmission period (which is longer than the second transmission period) in the live wake-up time window is dedicated to transmitting the real-time captured, high-frame-rate live video stream to ensure smooth live viewing.

[0096] Secondly, the first event video data in motion scenarios has the second highest transmission queue priority, only lower than the live video bitrate. Therefore, during the second transmission period of the live wake-up time window, the first event video data is sent to the cloud storage terminal first to ensure priority backup of critical data.

[0097] Furthermore, the transmission queue of the second event video data in static scenes has the lowest priority. Therefore, if the first event video data stored in the storage module of the video shooting device has been sent to the cloud storage terminal and the live broadcast wake-up time window has not yet closed (i.e., the user has not yet finished watching the live broadcast), the second event video data stored in the video shooting device will be sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window in order to delay the storage of non-critical data.

[0098] Furthermore, during the process of sending the second event video data to the cloud storage, the second event video data stored in the storage module is first sent to the cloud storage. After all the second event video data in the storage module has been sent to the cloud storage, if the live broadcast wake-up time window has not yet closed, then the second event video data in memory is sent to the cloud storage. This avoids the video shooting device being forced to wake up due to the local storage full wake-up event. Unlike the memory full wake-up event, when the local storage full wake-up event is triggered, the video shooting device must specifically enter a high-power active state from a low-power sleep state to transfer the locally stored video data in the storage module to the cloud storage. However, when the memory full wake-up event is triggered, the video shooting device can write the video data in memory to the storage module with relatively low power consumption.

[0099] Optionally, when transmitting the live video stream and locally stored video data, the live video stream and its corresponding video capture time and wake-up event tag are transmitted together, and the locally stored video data and its corresponding video capture time and wake-up event tag are sent together to the cloud storage terminal to facilitate subsequent transmission scheduling by the cloud storage terminal; wherein, the video capture time is also the video playback time, which refers to the time when the video requested by the user terminal for playback is captured; and, the wake-up event tag of the live video stream is the live event tag, the wake-up event tag of the first event video data is the motion event tag, the wake-up event tag of the memory full wake-up event is the memory full event tag, the wake-up event tag of the timed wake-up event is the timed event tag, and the wake-up event tag of the playback wake-up event is the playback event tag.

[0100] Optionally, when transmitting the live video stream and locally stored video data, the live video stream, its corresponding video capture time, wake-up event tag, and video capture frame rate are transmitted together to facilitate subsequent transmission scheduling on the cloud storage side. For example, "motion event tag - high frame rate" and "memory full event tag - low frame rate".

[0101] The video upload method provided by this invention transmits first event video data and second event video data sequentially according to priority during the second transmission period of the live broadcast wake-up time window. This achieves full cloud storage of data based on data transmission priority and live broadcast wake-up time window reuse rules. It reduces unnecessary response wake-ups such as playback wake-ups and storage full wake-ups, avoids redundant data, and ensures orderly data upload. In the event that the local storage video data cannot be fully transmitted within the live broadcast wake-up time window, it prioritizes the transmission of key data in motion scenarios, reducing the number of times the video shooting device is woken up by low-priority data, further reducing the power consumption of the video shooting device during transmission retries, and increasing battery life.

[0102] Based on the above embodiments, as an optional embodiment, after transmitting the live video stream during the first transmission period of the live wake-up time window in response to the live wake-up event, and sending the locally stored video data to the cloud storage terminal during the second transmission period of the live wake-up time window, the method further includes: If not all the locally stored video data is sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window, then if the network status of the video shooting device is idle, the unsent locally stored video data will be sent to the cloud storage terminal.

[0103] Specifically, when transmitting locally stored video data during the second transmission period of the live stream wake-up window, if the amount of locally stored video data is large and the user's live stream viewing time is short, it's possible that the locally stored video data hasn't been fully transmitted to the cloud storage when the live stream wake-up window closes. In this case, the breakpoint in the locally stored video data transmission is recorded, and transmission resumes from that breakpoint at the start of the next live stream wake-up window. Alternatively, an idle-time transmission strategy can be adopted. When the network status of the video recording device is idle, the communication module is activated, transitioning from sleep mode to active mode, and the unsent locally stored video data is sent to the cloud storage from the breakpoint. The device immediately returns to sleep mode after transmission is complete. If the network status becomes busy during idle-time transmission (e.g., the gateway detects other devices starting to download), the video recording device pauses transmission and records the breakpoint, resuming transmission during the next idle period.

[0104] Optionally, when the video shooting device is a 4G low-power camera, the network status of the video shooting device is determined based on the platform's heartbeat mode. Specifically, this includes: the video shooting device periodically (e.g., every 5 minutes) sends a very small heartbeat packet (e.g., less than 50 bytes) to the cloud storage terminal while in sleep mode. The heartbeat packet includes basic information such as the device ID and the current timestamp, and the power consumption is controlled within 1mA·s. The cloud storage terminal calculates the suggested upload time period based on the network load in the area where the video shooting device is located (e.g., base station load, historical upload success rate analysis, etc.) and the historical behavior of the video shooting device (e.g., upload success rate, number of retries, etc.), and attaches network status information (e.g., "suggested upload time period is 2:00~5:00", "current network is busy, please try again later") in the heartbeat response and returns it to the video shooting device. After receiving the heartbeat response returned by the cloud storage terminal, the video shooting device determines whether the network status of the video shooting device is idle by combining the locally recorded upload success rate and / or upload latency. When the network status is idle, the communication module is started to send the unsent locally stored video data to the cloud storage terminal.

[0105] Optionally, when the video shooting device has a gateway, the network status of the video shooting device is determined based on the gateway linkage mode. Specifically, this includes: using smart home gateway protocols (such as MQTT, CoAP, etc.), the video shooting device establishes a low-power connection with the gateway via Wi-Fi / BLE. The gateway monitors the home network status in real time (such as bandwidth utilization and the number of concurrent traffic devices) and pushes this information to the video shooting device via the protocol. The video shooting device obtains detailed network status information (such as bandwidth utilization <20% and no other high-traffic devices transmitting) through the gateway and, combined with its own upload strategy (such as prioritizing uploads of high-priority events), activates the communication module to send unsent locally stored video data to the cloud storage when it detects that the network status is idle.

[0106] Optionally, when the video shooting device has multiple network connection methods (such as simultaneously supporting 4G and Wi-Fi), the network status of the video shooting device is determined based on a dual-network combination mode. Specifically, when the video shooting device is in a Wi-Fi environment, the gateway linkage mode is used first to obtain detailed network status; if the Wi-Fi signal is weak or unavailable, it automatically switches to 4G mode, relying on the platform heartbeat to obtain simplified network status information to determine if the video shooting device's network is idle. When the network is idle, the communication module is activated to send any unsent locally stored video data to the cloud storage. Through this dual-network combination mode, the platform heartbeat mechanism is also retained as a backup in the gateway linkage mode, ensuring that basic network status information can still be obtained in the event of network anomalies.

[0107] The video upload method provided by this invention reduces the transmission failure rate by obtaining network status from cloud storage or home gateways and transmitting low-priority data during idle periods. By considering network conditions during video upload, it improves the upload success rate of full data storage on cloud storage.

[0108] Figure 3 This is a flowchart illustrating the video playback method provided by the present invention, as shown below. Figure 3 As shown, the video playback method is applied to a user terminal, including but not limited to steps 301 and 302.

[0109] It should be noted that the execution subject of the video playback method provided by the present invention can be a server, computer device, such as a mobile phone, tablet computer, laptop computer, handheld computer, vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0110] Step 301: Send a video playback request to the cloud storage.

[0111] The video playback request includes the video playback time and the wake-up event tag.

[0112] Step 302: Receive the video playback file sent by the cloud storage terminal.

[0113] The video playback file is determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes the live video stream and locally stored video data.

[0114] The live video stream and the locally stored video data are transmitted based on the video upload method described in any of the above embodiments.

[0115] A video playback request is a request sent by the user terminal to the cloud storage terminal to obtain the video playback time and the video playback file corresponding to the wake-up event tag.

[0116] Video playback time is the time when the video requested for playback by the user terminal is captured; wake-up event tag is a tag based on the type of wake-up event that the video requested for playback was captured and stored, including but not limited to any one of the following: live event tag, motion event tag, memory full event tag, timed event tag, and playback event tag.

[0117] Specifically, in combination Figure 3 and Figure 2 As shown, when a video shooting device uploads live video streams and locally stored video data to the cloud storage terminal, it will synchronously transmit the video capture time and wake-up event tags to the cloud storage terminal. This enables the cloud storage terminal to establish a mapping index of "video capture time - wake-up event tag - video data address". For example, motion event tags and live event tags correspond to high frame rate segment addresses, while wake-up event tags in static scenes correspond to low frame rate segment addresses.

[0118] The user terminal sends a video playback request, including the video playback time and wake-up event tag, to the cloud storage terminal. After receiving the video playback request, the cloud storage terminal determines the video playback file requested by the user from all the live video streams received from the cloud storage terminal and the locally stored video data based on the video playback time and wake-up event tag in the video playback request, and returns the video playback file to the user terminal. This allows the user to directly access the video playback through the index during playback. The entire process only requires interaction with the cloud storage terminal and does not require the video shooting device to participate, thus avoiding waking up the video shooting device and increasing its power consumption.

[0119] It should be noted that the video playback method provided by the present invention can be referenced and used interchangeably with the video upload method described in any of the above embodiments during actual operation, and this embodiment will not elaborate on this.

[0120] The video playback method provided by this invention, during the interval between transmitting the live video stream in response to a live wake-up event and the start of the live wake-up time window, opens a second transmission period to supplement the locally stored video data collected and stored on the video shooting device in response to other wake-up events and transmit it to the cloud storage. The storage and retrieval of both high-frame-rate and low-frame-rate video data collected by the video shooting device are transferred from the video shooting device to the cloud storage. Cloud storage replaces local storage as the dominant method in playback operations, eliminating the need to wake up the video shooting device in playback scenarios. This allows the user terminal to retrieve the video playback file from the cloud storage without waking up the video shooting device, avoiding the high-power state of the video shooting device entering high-frame-rate video capture due to the wake-up event. Finally, this achieves a video playback solution that reduces the power consumption of the video shooting device and increases its battery life.

[0121] To better illustrate the video upload and video playback methods provided by this invention, the following detailed explanation will be based on a user's home with a video shooting device (such as a wireless security camera or other AOV device) that supports the video upload method provided by this invention.

[0122] During the day, the video recording device is in a low-power sleep state for most of the time, capturing video data of the second event at a low frame rate of 1 frame / second and temporarily caching it in the memory of the video recording device. When the memory is full and the wake-up event is triggered, the video data of the second event is written to the storage module of the video recording device.

[0123] When a user initiates a live stream viewing request while commuting to work, triggering a live stream wake-up event, the video recording device is awakened from sleep mode. A live stream wake-up time window is opened, and a single TS format live video stream with a frame rate of 15-30 frames per second is captured and generated. This stream is then transmitted to the live streaming server during the first transmission period of the wake-up time window. The live streaming server receives the stream and uses it for live viewing while simultaneously generating live video segments at 10-second intervals and transferring them to cloud storage. If the video recording device still contains locally stored video data captured during the previous wake-up event response, it is retransmitted during the second transmission period of the wake-up time window. Priority is given to transmitting the high-frame-rate cloud storage data from motion-activated wake-up events before transmitting the low-frame-rate data captured and stored from static scenes.

[0124] If the video capture device detects that the rate of change of the image within the field of view is greater than or equal to the preset rate of change threshold, it indicates that a motion event has occurred. The video capture device is also awakened from the sleep state, and the acquisition frame rate is increased to 15-30 frames / second for acquisition. The video data of the first event is marked as a "motion event tag", which enjoys higher priority when transmitted in the second transmission period.

[0125] When the network is idle at night, the video shooting device can detect that the network status is good through platform heartbeat or gateway linkage. If there is any unuploaded locally stored video data, it will only start the communication module to upload this data to the cloud storage terminal. After the upload is completed, it will quickly enter the sleep state.

[0126] When users want to watch videos from a specific time period during the day after returning home in the evening, they can directly access the cloud storage terminal. Through the "video capture time - wake-up event tag - video data address" mapping index established by the cloud storage terminal, the corresponding video data can be quickly obtained without waking up the video shooting device.

[0127] Overall, this application proposes a low-power cloud storage upload and playback method and system for AOV devices based on wake-up event priority scheduling. Regarding playback power consumption, related technologies require waking up the AOV device for each playback, while this application's solution directly accesses the cloud storage terminal, eliminating the need to wake up the AOV device and reducing daily power consumption by approximately 30%. In terms of data generation efficiency, related technologies generate high frame rate data for all wake-up scenarios, while this application's solution only generates high frame rate data for high-priority live streaming wake-up events and playback wake-up events, reducing the amount of invalid data. This application reduces data transmission volume by approximately 40%. Regarding wake-up frequency, related technologies require separate wake-ups for low-priority data; this application reuses existing wake-up windows, reducing wake-up frequency and energy consumption by approximately 60%. In terms of transmission failure rate, related technologies have a failure rate >30% during network congestion, while this application has a failure rate <5% during idle periods, reducing retry energy consumption and lowering transmission-related energy consumption by approximately 25%. Regarding live streaming and cloud storage collaboration, related technologies require transmitting two live streams; this application uses a single stream multiplexed for both live streaming and data transfer, reducing device transmission energy consumption. Finally, through triple optimization of "cloud-based replacement of local storage," "dynamic scene adaptation," and "intelligent transmission scheduling," this application reduces the overall power consumption of AOV devices by 30%-50%, extending the battery life of AOV devices from 30 days to 45-60 days. Cloud backup enhances data security, and the ability to review content without waiting for device wake-up improves user experience.

[0128] Figure 4 This is a schematic diagram of the video uploading device provided by the present invention, as shown below. Figure 4 As shown, the video uploading device is deployed on the video shooting equipment, including but not limited to the dual transmission module 401.

[0129] The dual transmission module 401 is used to respond to a live broadcast wake-up event by transmitting the live video stream during the first transmission period of the live broadcast wake-up time window and sending the locally stored video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window.

[0130] The locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live broadcast wake-up event.

[0131] It should be noted that the video uploading device provided by the present invention can execute the video uploading method described in any of the above embodiments during specific operation, and this embodiment will not elaborate on this.

[0132] The video uploading device provided by this invention stores video data collected in response to wake-up events other than live wake-up events as local storage video data on the video shooting device. Then, during the interval between the live wake-up time window that initiates the live wake-up event to transmit the live video stream, a second transmission period is created to supplement the locally stored video data to the cloud storage. This enables the video shooting device to upload locally stored video data from other wake-up events to the cloud storage during live wake-up, avoiding unnecessary additional wake-ups to the video shooting device when uploading locally stored video data. Furthermore, by separating the live wake-up time window into two different transmission periods to transmit the live video stream and locally stored video data separately, orderly uploading of video data is achieved, avoiding... This solution avoids conflicts during video transmission that could cause live stream interruptions or require additional device wake-ups to retransmit data, ensuring smooth live streaming. Simultaneously, by completing the transmission and cloud storage of the live video stream and locally stored video data during the live stream wake-up period, user terminals only need to retrieve the video playback file from the cloud storage when watching the video, eliminating the need to wake up the video recording device. This prevents the video recording device from entering a high-power state of high frame rate video capture in response to playback wake-up events. Furthermore, by avoiding redundant data generated from playback wake-up events, the number of times the video recording device responds to full storage wake-up events is reduced. Ultimately, this achieves a video upload solution that reduces unnecessary wake-up responses, avoids redundant data, and ensures orderly data upload, further reducing the power consumption of video recording devices and extending battery life.

[0133] As an optional embodiment, the dual transmission module includes: a first transmission module for transmitting a live video stream, including sending the live video stream to a live server; the live server for sending the live video stream to a user terminal that triggers the live wake-up event; the live server is also used to generate a live video slice in cloud storage format based on the live video stream, and send the live video slice to the cloud storage terminal.

[0134] As an optional embodiment, the video uploading device further includes: a first data storage module and a second data storage module; The first data storage module is used to respond to the first wake-up event, collect the video data of the first event at a first frame rate, and store the video data of the first event to the storage module of the video shooting device; the first wake-up event is triggered when the rate of change of the image within the field of view of the video shooting device is greater than or equal to a preset rate of change threshold. The second data storage module is used to write the continuously collected second event video data at a second frame rate from the memory of the video shooting device to the storage module in response to a second wake-up event; wherein the first frame rate is greater than the second frame rate.

[0135] As an optional embodiment, the dual transmission module further includes: a second transmission module, configured to send the first event video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window; and, if all the first event video data has been sent to the cloud storage terminal, to continue sending the second event video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window.

[0136] As an optional embodiment, the video uploading device further includes: an idle transmission module, configured to send the unsent local stored video data to the cloud storage terminal if all the locally stored video data is not sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window, when the network status of the video shooting device is idle.

[0137] Figure 5 This is a structural schematic diagram of the video playback device provided by the present invention, as shown below. Figure 5 As shown, the video playback device is deployed on the user terminal and includes, but is not limited to, a sending module 501 and a receiving module 502.

[0138] The sending module 501 is used to send a video playback request to the cloud storage terminal; the video playback request includes the video playback time and the wake-up event tag.

[0139] The receiving module 502 is used to receive the video playback file sent by the cloud storage terminal; the video playback file is determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes the live video stream and locally stored video data.

[0140] The live video stream and the locally stored video data are transmitted using the video upload device described in any of the above embodiments.

[0141] It should be noted that the video playback device provided by the present invention can execute the video playback method described in any of the above embodiments during specific operation, and this embodiment will not elaborate on this.

[0142] The video playback device provided by this invention, during the intervals between transmitting the live video stream in response to a live wake-up event and the activation of the live wake-up time window, opens a second transmission period to supplement the locally stored video data collected and stored on the video shooting device in response to other wake-up events and transmits it to the cloud storage end. The storage and retrieval of both high-frame-rate and low-frame-rate video data collected by the video shooting device are transferred from the video shooting device to the cloud storage end. Cloud storage replaces local storage as the dominant method in playback operations, eliminating the need to wake up the video shooting device in playback scenarios. This allows the user terminal to retrieve the video playback file from the cloud storage end without waking up the video shooting device, avoiding the high-power state of the video shooting device entering high-frame-rate video capture due to the wake-up event. Finally, this invention provides a video playback solution that reduces the power consumption of the video shooting device and increases its battery life.

[0143] Figure 6 This is a schematic diagram of the structure of the electronic device provided by the present invention, such as... Figure 6 As shown, the electronic device may include: a processor 610, a communications interface 620, a memory 630, and a communication bus 640, wherein the processor 610, the communications interface 620, and the memory 630 communicate with each other through the communication bus 640. The processor 610 can call logical instructions in the memory 630 to execute the video uploading method provided in any of the above embodiments. The video uploading method includes, but is not limited to, the following steps: in response to a live wake-up event, transmitting a live video stream during a first transmission period of the live wake-up time window, and sending locally stored video data to a cloud storage terminal during a second transmission period of the live wake-up time window; the locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live wake-up event. Alternatively, the video playback method provided in any of the above embodiments can be executed, wherein the video playback method includes, but is not limited to, the following steps: sending a video playback request to a cloud storage terminal; the video playback request including a video playback time and a wake-up event tag; receiving a video playback file sent by the cloud storage terminal; the video playback file being determined from complete video data based on the video playback time and the wake-up event tag; the complete video data including a live video stream and locally stored video data; the live video stream and the locally stored video data being transmitted by the video upload method described in any of the above embodiments.

[0144] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a 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.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. 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.

[0145] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the video uploading method provided in any of the above embodiments. The video uploading method includes, but is not limited to, the following steps: in response to a live wake-up event, transmitting a live video stream during a first transmission period of the live wake-up time window, and sending locally stored video data to a cloud storage terminal during a second transmission period of the live wake-up time window; the locally stored video data is video data collected and saved to the video shooting device in response to other wake-up events besides the live wake-up event. Alternatively, the video playback method provided in any of the above embodiments can be executed, wherein the video playback method includes, but is not limited to, the following steps: sending a video playback request to a cloud storage terminal; the video playback request including a video playback time and a wake-up event tag; receiving a video playback file sent by the cloud storage terminal; the video playback file being determined from complete video data based on the video playback time and the wake-up event tag; the complete video data including a live video stream and locally stored video data; the live video stream and the locally stored video data being transmitted by the video upload method described in any of the above embodiments.

[0146] In another aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the video uploading method provided in any of the above embodiments. The video uploading method includes, but is not limited to, the following steps: in response to a live wake-up event, transmitting a live video stream during a first transmission period of a live wake-up time window, and sending locally stored video data to a cloud storage terminal during a second transmission period of the live wake-up time window; the locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live wake-up event. Alternatively, the video playback method provided in any of the above embodiments can be executed, wherein the video playback method includes, but is not limited to, the following steps: sending a video playback request to a cloud storage terminal; the video playback request including a video playback time and a wake-up event tag; receiving a video playback file sent by the cloud storage terminal; the video playback file being determined from complete video data based on the video playback time and the wake-up event tag; the complete video data including a live video stream and locally stored video data; the live video stream and the locally stored video data being transmitted by the video upload method described in any of the above embodiments.

[0147] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0148] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0149] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A video uploading method, characterized in that, Used in video shooting equipment, including: In response to a live stream wake-up event, the live video stream is transmitted during the first transmission period of the live stream wake-up time window, and the locally stored video data is sent to the cloud storage terminal during the second transmission period of the live stream wake-up time window. The locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live broadcast wake-up event.

2. The video uploading method according to claim 1, characterized in that, The transmission of the live video stream includes: Send the live video stream to the live streaming server; The live streaming server is used to send the live video stream to the user terminal that triggered the live streaming wake-up event; The live streaming server is also used to generate live video slices in cloud storage format based on the live video bitstream, and send the live video slices to the cloud storage terminal.

3. The video uploading method according to claim 1, characterized in that, The locally stored video data includes at least one of the first event video data and the second event video data; If the locally stored video data includes the first event video data, the method further includes, prior to responding to the live stream wake-up event: In response to a first wake-up event, video data of the first event is acquired at a first frame rate and stored in the storage module of the video shooting device; the first wake-up event is triggered when the rate of change of the image within the field of view of the video shooting device is greater than or equal to a preset rate of change threshold. If the locally stored video data includes the second event video data, the method further includes, prior to responding to the live stream wake-up event: In response to the second wake-up event, the second event video data at the second frame rate that is continuously collected is written from the memory of the video shooting device to the storage module; Wherein, the first frame rate is greater than the second frame rate.

4. The video uploading method according to claim 3, characterized in that, When the locally stored video data includes first event video data and second event video data, sending the locally stored video data to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window includes: During the second transmission period of the live broadcast wake-up time window, the first event video data is sent to the cloud storage terminal; If all the video data of the first event is sent to the cloud storage terminal, the video data of the second event will continue to be sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window.

5. The video uploading method according to claim 3, characterized in that, The second wake-up event is any one of the following: memory full wake-up event, timed wake-up event, and lookback wake-up event.

6. The video uploading method according to claim 1, characterized in that, After transmitting the live video stream during the first transmission period of the live wake-up time window in response to the live wake-up event, and sending the locally stored video data to the cloud storage terminal during the second transmission period of the live wake-up time window, the method further includes: If not all the locally stored video data is sent to the cloud storage terminal during the second transmission period of the live broadcast wake-up time window, then if the network status of the video shooting device is idle, the unsent locally stored video data will be sent to the cloud storage terminal.

7. A video playback method, characterized in that, Applied to user terminals, including: Send a video playback request to the cloud storage terminal; the video playback request includes the video playback time and wake-up event tag; The system receives a video playback file sent by the cloud storage terminal; the video playback file is determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes the live video stream and locally stored video data. The live video stream and the locally stored video data are transmitted based on the video upload method as described in any one of claims 1 to 6.

8. A video uploading device, characterized in that, Deployed on video shooting equipment, including: The dual transmission module is used to respond to a live wake-up event by transmitting the live video stream during the first transmission period of the live wake-up time window and sending the locally stored video data to the cloud storage terminal during the second transmission period of the live wake-up time window. The locally stored video data is video data collected and saved to the video shooting device in response to wake-up events other than the live broadcast wake-up event.

9. A video playback device, characterized in that, Deployed on user terminals, including: The sending module is used to send video playback requests to the cloud storage terminal; the video playback request includes video playback time and wake-up event tags; A receiving module is used to receive video playback files sent by the cloud storage terminal; the video playback files are determined from the complete video data based on the video playback time and the wake-up event tag; the complete video data includes live video streams and locally stored video data; The live video stream and the locally stored video data are transmitted based on the video upload device as described in claim 8.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the video uploading method as described in any one of claims 1 to 6 or the video playback method as described in claim 8.

11. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the video uploading method as described in any one of claims 1 to 6 or the video playback method as described in claim 8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the video uploading method as described in any one of claims 1 to 6 or the video playback method as described in claim 8.

Images