Video recording method, apparatus and storage medium

Abstract

The application discloses a video recording method, device and storage medium. The video recording method comprises the following steps: in response to receiving a wake-up request in a sleep mode, a video recording device is switched to a wake-up mode, and the trigger type of the wake-up request is determined, wherein the video recording device acquires and stores a video stream at a first frame rate in the sleep mode; when the trigger type is an event trigger type, the video stream is acquired and stored at a second frame rate, wherein the event trigger type indicates that an event is detected from the video stream, and the second frame rate is greater than the first frame rate; when the trigger type is a non-event trigger type, the video stream is acquired and stored at a frame rate within a preset frame rate range, wherein the upper limit value of the preset frame rate range is less than the second frame rate. In the above manner, when the video recording device is woken up due to a non-event, the video can be recorded at a lower frame rate, thereby reducing the storage space occupation.

Description

Technical Field

[0001] This application relates to the field of video processing technology, and in particular to a recording method, apparatus and storage medium. Background Technology

[0002] Currently, AOV (Always-On-Video) cameras record video at a low frame rate in sleep mode (also known as low-power mode). When an event or other non-event behavior is detected, they are woken up and record video at a high frame rate. They then enter sleep mode again after the event or other non-event behavior ends. However, non-event wake-up behaviors are not actually security events. When an AOV camera is woken up by a non-event behavior, it generates a large amount of meaningless high-frame-rate recordings, consuming a significant amount of storage space. Summary of the Invention

[0003] The main technical problem addressed by this application is to provide a recording method, device, and computer-readable storage medium that can record video at a lower frame rate when the recording device is woken up by a non-event, thereby reducing storage space usage.

[0004] To address the aforementioned technical problems, this application provides a recording method applied to a recording device. The method includes: in response to receiving a wake-up request in sleep mode, switching to wake-up mode and determining the trigger type of the wake-up request, wherein the recording device acquires and stores a video stream at a first frame rate in sleep mode; in response to the trigger type being event-triggered, acquiring and storing the video stream at a second frame rate, wherein the event-triggered type indicates that an event has been detected in the video stream, and the second frame rate is greater than the first frame rate; and in response to the trigger type being non-event-triggered, acquiring and storing the video stream at a frame rate within a preset frame rate range, wherein the upper limit of the preset frame rate range is less than the second frame rate.

[0005] In one embodiment, the trigger type is non-event-triggered, and the wake-up request is either a preview request from the user or a service request from the recording device. Acquiring and storing the video stream at a frame rate within a preset frame rate range includes: acquiring and storing the video stream at a first frame rate.

[0006] In one embodiment, the trigger type is non-event-triggered, the wake-up request is a preview request from the user terminal, and the preview period of the user terminal is divided into at least one sub-period during the recording process. Acquiring and storing the video stream at a frame rate within a preset frame rate range includes: acquiring and storing the video stream at a frame rate within a preset frame rate range in each sub-period corresponding to the preview period; wherein, in at least one sub-period, there exists a target sub-period with a frame rate greater than a first frame rate.

[0007] In one embodiment, the target sub-period includes a start sub-period and an end sub-period in at least one sub-period; and / or, the frame rate corresponding to each sub-period other than the target sub-period in at least one sub-period is equal to the first frame rate.

[0008] In one embodiment, at least one of the frame rate corresponding to the target sub-segment and the duration of the target sub-segment is used as the target labeling parameter for the target sub-segment. The step of determining the target labeling parameter includes: determining at least one evaluation factor; wherein the at least one evaluation factor includes at least one of the current battery level of the recording device, the current remaining storage space of the recording device, the current network quality of the recording device, and the frequency of user-initiated previews; and combining the at least one evaluation factor to determine the target labeling parameter.

[0009] In one embodiment, determining a target labeling parameter by integrating at least one evaluation factor includes: determining the evaluation score of each evaluation factor; integrating the evaluation scores of each evaluation factor to obtain a comprehensive score; determining a target score interval corresponding to the comprehensive score; and selecting a labeling parameter corresponding to the target score interval from a first mapping relationship as the target labeling parameter; wherein the first mapping relationship includes several preset score intervals and preset labeling parameters corresponding to each preset score interval. Alternatively, at least one evaluation factor includes current battery power and current remaining storage space. Determining a target labeling parameter by integrating at least one evaluation factor includes: determining a target operating mode of the recording device using the current battery power and current remaining storage space; and selecting a labeling parameter corresponding to the target operating mode from a second mapping relationship as the target labeling parameter; wherein the second mapping relationship includes several preset operating modes and preset labeling parameters corresponding to each preset operating mode.

[0010] In one embodiment, the trigger type is non-event triggered, and the wake-up request is a preview request from the user terminal. The method further includes: in response to receiving a preview marker instruction sent by the user terminal during the preview period, obtaining the trigger time corresponding to the preview marker instruction; using a first video stream within a first duration before the trigger time and a second video stream within a second duration after the trigger time to generate a user-focused segment about the preview marker instruction, and storing the user-focused segment.

[0011] In one embodiment, the trigger type is non-event-triggered, and the wake-up request is a preview request from the user terminal. The method further includes: acquiring a video stream at a third frame rate to obtain a preview stream, and pushing the preview stream to the user terminal, wherein the third frame rate is greater than the first frame rate; the preview stream and the storage stream of the recording device are obtained by independently encoding them using a multi-stream encoder; or, the preview stream and the storage stream of the recording device are obtained by frame filtering of a video stream at a fourth frame rate generated using a single-stream encoder; wherein the storage stream includes a video stream acquired and stored by the recording device at a first frame rate in sleep mode, a video stream acquired and stored at a second frame rate during the event wake-up period, and a video stream acquired and stored at a frame rate within a preset frame rate range during the non-event wake-up period.

[0012] To solve the above-mentioned technical problems, another technical solution adopted in this application is: to provide a video recording device, including a memory and a processor coupled to each other, wherein the memory stores program instructions; and the processor is used to execute the program instructions stored in the memory to implement the above-mentioned video recording method.

[0013] To solve the above-mentioned technical problems, another technical solution adopted in this application is to provide a computer-readable storage medium for storing program instructions that can be executed by a processor to implement the above-mentioned recording method.

[0014] In the above scheme, the recording device acquires and stores the video stream at a first frame rate in sleep mode. When a wake-up request is received in sleep mode, it switches to wake-up mode and determines the trigger type of the wake-up request. When the trigger type is event-triggered, it means an event has been detected in the video stream, and the video stream is acquired and stored at a higher second frame rate, which is higher than the first frame rate. When the trigger type is non-event-triggered, the video stream is acquired and stored at a frame rate within a preset frame rate range. Since the upper limit of the preset frame rate range is less than the second frame rate, when the recording device is woken up due to a non-event, it can record video at a lower frame rate, thereby reducing storage space usage. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating an embodiment of the video recording method provided in this application; Figure 2 This is a schematic diagram of the frame of an embodiment of the video recording device provided in this application; Figure 3 This is a schematic diagram of the framework of an embodiment of the video recording device provided in this application; Figure 4 This is a schematic diagram of a framework of an embodiment of the computer-readable storage medium provided in this application. Detailed Implementation

[0016] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0017] It should be noted that the term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The terms "first" and "second" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one of those features. The term "multiple" in this application means at least two, such as two, three, etc. The term "several" in this application means at least two. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0018] The recording method in this application is performed by a recording device, which is an AOV camera or a camera with a similar working mode to an AOV camera.

[0019] The recording device in this application includes an image acquisition module, a detection module, an encoder, a storage management module, a communication module, and a frame rate control module. The image acquisition module can be a CMOS sensor used to acquire raw video frames. The detection module runs a lightweight AI detection algorithm to analyze the video footage in real time and detect events (such as people, vehicles, animals, etc.). The bitstream encoder encodes the raw video frames acquired by the image acquisition module. The bitstream encoder can be a single-stream encoder or a multi-stream encoder. A single-stream encoder supports outputting a single video stream, while a multi-stream encoder supports simultaneously outputting two or more video streams with different frame rates. The storage management module stores the acquired video stream in a buffer. Once the buffer is full, the video stream in the buffer is written to a storage unit (such as a local SD card) to obtain the recorded video. The communication module establishes a communication connection with the user terminal to receive instructions or requests from the user terminal and to push a preview stream to the user terminal when a preview request is received. The frame rate control module controls the frame rate during recording.

[0020] Please see Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the video recording method provided in this application. Figure 1 As shown, the method includes the following steps: S11: In response to receiving a wake-up request in sleep mode, switch to wake-up mode and determine the trigger type of the wake-up request.

[0021] The recording device acquires and stores the video stream at a lower first frame rate in sleep mode. For example, the first frame rate ranges from 0.1fps to 0.5fps. For instance, the first frame rate can be set to 0.1fps, 0.3fps, 0.5fps, etc.

[0022] Furthermore, the recording device synchronously detects whether a wake-up request has been received in real time while in sleep mode. When a wake-up request is received, it switches from sleep mode to wake-up mode. The recording device then determines the trigger type of the wake-up request and executes different frame rate control strategies based on that trigger type.

[0023] In this embodiment, the trigger type is either event-triggered or non-event-triggered.

[0024] Event-triggered indicates that an event is detected in the video stream. When an event is detected in the video stream, a wake-up request is generated, and the trigger type is event-triggered.

[0025] Non-event-triggered events can be further divided into user-triggered events and device service-triggered events.

[0026] When a preview request is received from the user, the wake-up request is the preview request, and the trigger type is user-triggered.

[0027] When a business request is received from the recording device itself, the wake-up request becomes a business request, and the trigger type is device business-triggered. A business request can be generated by the recording device when it detects that a business task needs to be performed. In some examples, the business task might be writing the stored stream from the recording device's cache to its storage unit. When the recording device's cache is full, the stored stream needs to be written to the recording device's local storage unit. A business task could be reporting status to a target node; the recording device needs to periodically send heartbeat data to the target node to report its status. The target node could be the cloud or a user terminal, etc. A business task could also be network reconnection; the recording device reconnects to the network when it detects poor or unavailable network conditions. A business task could also be an OTA (Over-The-Air) task, such as firmware version checks or upgrades.

[0028] Further, if the trigger type is determined to be event-triggered, proceed to step S12. If the trigger type is determined to be non-event-triggered, proceed to step S13.

[0029] S12: In response to an event-triggered trigger, acquire and store the video stream at the second frame rate.

[0030] The second frame rate is a higher frame rate than the first frame rate. For example, the second frame rate can range from 15fps to 30fps. For instance, the second frame rate could be 20fps, 30fps, etc.

[0031] S13: In response to a non-event triggered trigger type, acquire and store the video stream at a frame rate within the preset frame rate range.

[0032] The frame rates within the preset frame rate range are lower frame rates, and the upper limit of the preset frame rate range is less than the second frame rate. The lower limit of the preset frame rate range can be greater than or equal to the first frame rate. For example, the preset frame rate range is 0.1fps to 1fps.

[0033] In step S13, when the recording device is woken up due to a non-event, the video stream is no longer acquired and stored at a higher second frame rate, but at a lower frame rate within the preset frame rate range, so as to reduce the storage space occupied by AOV recordings generated during non-event wake-up periods.

[0034] In some implementations, the video stream is acquired and stored at a fixed frame rate within a preset frame rate range, such as acquiring and storing the video stream at the aforementioned first frame rate, or acquiring and storing the video stream at a frame rate within a preset frame rate range that changes dynamically.

[0035] Furthermore, when the recording device detects the end of an event or the end of a non-event behavior, the recording device will re-enter sleep mode.

[0036] In this embodiment, the recording device acquires and stores the video stream at a first frame rate in sleep mode. When a wake-up request is received in sleep mode, it switches to wake-up mode and determines the trigger type of the wake-up request. When the trigger type is event-triggered, it means an event has been detected in the video stream, and the video stream is acquired and stored at a higher second frame rate, which is higher than the first frame rate. When the trigger type is non-event-triggered, the video stream is acquired and stored at a frame rate within a preset frame rate range. Since the upper limit of the preset frame rate range is less than the second frame rate, when the recording device is woken up due to a non-event, it can record video at a lower frame rate, thereby reducing storage space usage.

[0037] In one embodiment, the recording device acquires and stores a video stream at a lower first frame rate in sleep mode. Upon receiving a wake-up request, the recording device determines the trigger type of the wake-up request. When the trigger type is event-triggered, i.e., the recording device wakes up due to an event, it acquires and stores the video stream at a higher second frame rate. When the trigger type is non-event-triggered, i.e., the recording device wakes up due to a non-event, it acquires and stores the video stream at a lower first frame rate in sleep mode. In this embodiment, the stored stream of the recording device includes the video stream acquired and stored by the recording device in sleep mode and during non-event wake-up periods at a lower first frame rate (i.e., ordinary AOV recording), and the video stream acquired and stored during event wake-up periods at a higher second frame rate (i.e., event recording). Ordinary AOV recording and event recording share the same recording timeline.

[0038] The above embodiments can avoid meaningless high-frame-rate recordings caused by non-event wake-ups, reduce storage space usage, and maximize storage space utilization. Furthermore, switching to high-frame-rate event recording only when an event is detected ensures that the recording timeline of the device contains only two types of clean content: ordinary AOV recordings (recording changes in the environmental background) and event recordings (recording key events).

[0039] In one embodiment, when the wake-up request received by the recording device is a preview request from the user, the recording device acquires the video stream at a higher third frame rate during the preview period, obtains a preview stream, and pushes the preview stream to the user. The third frame rate is greater than the first frame rate. The third frame rate may be the same as or different from the aforementioned second frame rate. For example, the third frame rate is 20fps.

[0040] In this embodiment, the preview stream at the third frame rate during the preview period and the storage stream of the recording device are separate. The storage stream of the recording device includes the video stream acquired and stored by the recording device in sleep mode at the first frame rate, the video stream acquired and stored at the second frame rate during the event wake-up period, and the video stream acquired and stored at a frame rate within a preset frame rate range during non-event wake-up periods.

[0041] In one scenario, the recording device's bitstream encoder is a multi-stream encoder, and the preview stream and the recording device's stored stream are independently encoded using the multi-stream encoder. The multi-stream encoder involves two bitstream encoding paths: one for generating a preview stream at a third frame rate during the preview period, and the other for acquiring and storing the video stream throughout the entire recording process to obtain the stored stream. Furthermore, in this scenario, when it's necessary to adjust the frame rate of the stored stream (e.g., upon detecting an event or adjusting the frame rate of the stored stream during the preview period), this is achieved by adjusting the multi-stream encoder's acquisition frame rate for the stored stream.

[0042] In another scenario, the recording device's bitrate encoder is a single-stream encoder that continuously generates a video stream at a fourth frame rate. The fourth frame rate is a higher frame rate value, such as a fourth frame rate greater than or equal to the third frame rate, or a fourth frame rate greater than or equal to the second frame rate. The preview stream and the recording device's storage stream are obtained by filtering the frames of the video stream generated using the fourth frame rate from the single-stream encoder. Furthermore, in this scenario, when the frame rate of the storage stream needs to be adjusted, this is achieved by adjusting the filtering frame rate of the frame filter.

[0043] In this embodiment, the recording device acquires and stores the video stream at a first frame rate in sleep mode, and upon receiving a wake-up request, it can execute a differentiated recording strategy based on the trigger type of the wake-up request.

[0044] (1) The recording device is in sleep mode.

[0045] In sleep mode, the recording device acquires and stores the video stream at the first frame rate, resulting in ordinary AOV recording.

[0046] In one example, during a sleep period, the steps of acquiring and storing a video stream at a first frame rate include: adjusting the acquisition frame rate of the multi-stream encoder with respect to the storage stream to the first frame rate, acquiring and storing the video stream at the first frame rate using the multi-stream encoder.

[0047] In another example, during the sleep period, the steps of acquiring and storing the video stream at a first frame rate include: adjusting the filtering frame rate of the frame filter to the first frame rate, filtering video frames from the video stream at a fourth frame rate generated by the single-stream encoder according to the first frame rate, and storing them.

[0048] (2) The recording device receives a wake-up request, and the wake-up request is triggered by an event.

[0049] When the recording device is awakened by an event, it acquires and stores the video stream at a second frame rate, thus obtaining a recorded event video. Furthermore, when the event ends, it re-enters sleep mode.

[0050] In one example, during an event wake-up period, the steps of acquiring and storing a video stream at a second frame rate include: adjusting the acquisition frame rate of the multi-stream encoder with respect to the storage stream to the second frame rate, acquiring and storing the video stream at the second frame rate using the multi-stream encoder.

[0051] In another example, during the event wake-up period, the steps of acquiring and storing the video stream at the second frame rate include: when the second frame rate is equal to the fourth frame rate, setting the filtering frame rate of the frame filter to the fourth frame rate, filtering all video frames from the video stream at the fourth frame rate generated by the single-stream encoder, and storing them; or, when the second frame rate is less than the fourth frame rate, setting the filtering frame rate of the frame filter to the second frame rate, filtering video frames from the video stream at the fourth frame rate generated by the single-stream encoder according to the second frame rate, and storing them.

[0052] (3) The trigger type is the device service trigger type in the non-event trigger type (the recording device itself generates service requests).

[0053] Recording devices may be periodically or conditionally woken up due to internal business logic, such as cache fullness, periodic status synchronization with the server, and OTA upgrade checks. Acquiring and storing video streams at a high frame rate during these wake-up periods would result in unnecessary storage waste and recording timeline contamination. Considering that the primary purpose of wake-up periods is to complete related business tasks rather than record video, when a recording device is woken up by its own business requests, it acquires and stores video streams at a lower initial frame rate during these wake-up periods. Once the recording device silently completes its business tasks in the background and does not receive other wake-up requests (such as detected events or preview requests from the user), it automatically returns to sleep mode. Recordings generated during wake-up periods are essentially still part of ordinary AOV recordings and do not introduce business noise. The specific content of acquiring and storing video streams at the first frame rate during wake-up periods can be found in the previous section on sleep mode, and will not be repeated here.

[0054] Taking the recording device's buffer (or AOV buffer, which can store 1000 low frame rate video frames) as an example, and assuming no event interference: At 3:00 AM, the equipment had been running continuously for some time, and the AOV cache was almost full (998 frames already stored). The recording device was automatically woken up to prepare to write the cache to its storage unit (such as a local SD card). During the device's wake-up period, no events occurred in the monitoring screen, and there were no user preview requests. According to the policy, the recording device acquired and stored the video stream at the first frame rate (e.g., 0.2fps, 0.33fps) during the wake-up period. Simultaneously, the recording device wrote 1000 video frames from the cache to the storage unit in the background, taking approximately 8 seconds. After writing was completed, the recording device detected no other wake-up sources (no events, no preview requests) and immediately returned to sleep mode. The recordings generated during the wake-up period had the same frame rate as the recordings during the sleep period, both at 0.2fps or 0.33fps. On the final recording timeline, these 8 seconds of recording seamlessly connected with the AOV recordings of the preceding and following periods, with no visual differences and no recordings with any business noise.

[0055] Furthermore, if an event is detected during the device's service wake-up period, the recording device will switch to the second frame rate to acquire and store the video stream until the event ends.

[0056] Optionally, to prevent the recording device from remaining in a wake-up state for an extended period due to abnormal business tasks, a maximum wake-up time can be set. If the business task is not completed within this maximum wake-up time, the recording device will be forced into sleep mode. Furthermore, unfinished business tasks can be marked as pending, allowing the recording device to continue executing them the next time it is woken up.

[0057] Optionally, a recording background label can be added to ordinary AOV recordings generated during the device's wake-up period. This background label indicates that the AOV recording was generated during the device's wake-up period and that no events occurred during that time. For example, the recording background label could be "No events during wake-up." Furthermore, this background label can be added to the corresponding recording metadata for the AOV recording to facilitate subsequent statistical analysis or special display on the cloud or client side. For example, when playing back recordings, users can choose to hide AOV recordings generated purely during the device's wake-up period on the user's display interface, i.e., not displaying unimportant AOV recordings from that period.

[0058] (4) The trigger type is user-triggered (user sends preview request) in the non-event-triggered type.

[0059] In one embodiment, on the one hand, the recording device does not acquire and store the video stream at a higher second frame rate during the preview period on the user's end. Instead, it acquires and stores the video stream at a lower frame rate within a preset frame rate range. That is, the user's preview behavior will not trigger the high frame rate recording mode of the recording device, reducing the generation of meaningless high frame rate recordings during the preview period, thereby reducing the storage space occupied by the recording device. On the other hand, the recording device also acquires the video stream at a higher third frame rate during the preview period on the user's end, obtaining a preview stream, and sends the preview stream to the user's end in real time. This ensures that the user can see a smooth, high frame rate video on the user's end, thereby improving the user's preview experience.

[0060] In one example, the steps of acquiring a video stream at a third frame rate during the preview period include: adjusting the acquisition frame rate of the preview stream by the multi-stream encoder to the third frame rate, acquiring and storing the video stream at the third frame rate using the multi-stream encoder, thereby obtaining the preview stream.

[0061] In another example, during the preview period, the steps of acquiring the video stream at the third frame rate include: when the third frame rate is equal to the fourth frame rate, setting the filtering frame rate of the frame filter to the fourth frame rate, filtering all video frames from the video stream at the fourth frame rate generated by the single-stream encoder, and storing them; or, when the third frame rate is less than the fourth frame rate, setting the filtering frame rate of the frame filter to the third frame rate, filtering video frames from the video stream at the fourth frame rate generated by the single-stream encoder according to the third frame rate, and storing them.

[0062] In one implementation, when a preview close command is received from the user, or when the user submits a preview request but does not perform any action within a set time, the user's preview behavior is determined to have ended, and the recording device stops acquiring the preview stream and stops pushing the preview stream to the user's device. Furthermore, if the recording device does not detect any event at this time, it will enter sleep mode and continue acquiring and storing the video stream at the first frame rate.

[0063] In one embodiment, considering that the AOV recordings stored by the recording device during the preview period and the AOV recordings stored during the sleep period both have the first frame rate (i.e., the frame rate is the same), it is difficult for users to distinguish which periods of recording they have actively previewed when playing back the stored stream of the recording device. To enable users to intuitively distinguish between the AOV recordings during the sleep period and the AOV recordings during the preview period, the recording device acquires and stores the video stream at a frame rate varying within a preset frame rate range during the preview period, thus obtaining the AOV recordings for the preview period. The frame rate variation of the AOV recordings during the preview period is perceptible to the user, achieving the effect of embedding perceptible visual markers in the AOV recordings during the preview period, thereby allowing users to visually distinguish the AOV recordings during the preview period.

[0064] Specifically, the preview period can be divided into at least one sub-period during recording. Within the preview period, the step of the recording device acquiring and storing the video stream at a frame rate within a preset frame rate range further includes: acquiring and storing the video stream at a frame rate within the preset frame rate range within each sub-period corresponding to the preview period. The frame rate corresponding to each sub-period is within the preset frame rate range.

[0065] In one example, for each sub-period of the preview period, the video stream is acquired and stored at a frame rate within a preset frame rate range, including: adjusting the acquisition frame rate of the storage stream by the multi-stream encoder to the frame rate corresponding to the sub-period, and acquiring and storing the video stream with the corresponding frame rate of the sub-period using the multi-stream encoder.

[0066] In another example, for each sub-period of the preview period, the video stream is acquired and stored at a frame rate within a preset frame rate range, including: adjusting the frame rate of the frame filtering to the frame rate corresponding to the sub-period, and filtering and storing video frames from the video stream with the fourth frame rate generated by the single-stream encoder according to the frame rate corresponding to the sub-period.

[0067] At least one sub-segment contains a target sub-segment, and the frame rate corresponding to the target sub-segment is greater than the first frame rate. Based on the foregoing, the upper limit of the preset frame rate range is less than the second frame rate; therefore, the frame rate corresponding to the target sub-segment is greater than the first frame rate and less than the second frame rate. For example, the frame rate corresponding to the target sub-segment is 0.5fps, 1fps, etc.

[0068] The duration of each target sub-period can be designed according to actual needs. For example, the duration of each target sub-period is 3 seconds.

[0069] At least one sub-time period, excluding the target sub-time period, corresponds to a frame rate equal to the first frame rate. This minimizes the storage space occupied by AOV recordings during the preview period.

[0070] In one specific embodiment, the number of at least one sub-time period is multiple, and the target sub-time period includes at least one of the start sub-time period and the end sub-time period.

[0071] For example, the time when the recording device receives the preview end instruction is the start time of the end sub-period. At this time, a countdown of a preset duration (such as 3 seconds) begins, and the time when the countdown ends is the end time of the end sub-period.

[0072] The following example illustrates the situation with a frame rate of 1fps corresponding to the target sub-time period and a first frame rate of 0.33fps.

[0073] In one example, at least one sub-period includes two sub-periods: a start sub-period and an end sub-period, while the target sub-period includes only the start sub-period. The start sub-period has a frame rate of 1 fps, and the end sub-period has a frame rate of 0.33 fps.

[0074] In another example, at least one sub-period includes two sub-periods: a start sub-period and an end sub-period, while the target sub-period includes only the end sub-period. The start sub-period has a frame rate of 0.33 fps, and the end sub-period has a frame rate of 1 fps.

[0075] In another example, at least one sub-time period comprises three sub-time periods: a start sub-time period, a middle sub-time period, and an end sub-time period. The target sub-time period includes a start sub-time period and an end sub-time period. The frame rate for the start and end sub-time periods is 1 fps, and the frame rate for the middle sub-time period is 0.33 fps.

[0076] In this example, by varying the frame rate in three segments—fast at both ends and slow in the middle—the generated AOV recording within the preview period will exhibit a unique visual rhythm: the initial frame transitions are fast, the middle frame transitions are slow, and the final frame transitions are fast again. When users play back the AOV recording within this preview period, they can intuitively identify that the AOV recording within this preview period is one they have previously previewed by observing the speed of the frame transitions.

[0077] Taking a family courtyard scene as an example: The frame rate for the start and end sub-periods is set to 1fps (1 frame per second), and the frame rate for the middle sub-period (R_base) is set to 0.33fps (1 frame per 3 seconds). The recording device's battery is set to 80% (high-performance mode). At 10:00:00 AM, the user initiates a live preview via the user's app, continuously viewing the courtyard for 60 seconds. No events occur during the preview period, and the user does not perform any active operations. The recording device receives the preview request at 10:00:00 AM and is activated. Simultaneously, the recording device pushes a 20fps preview stream to the user's device. Furthermore, the recording device executes a three-stage flagging mechanism in high-performance mode during the preview period. Specifically, from 10:00:00 to 10:00:03 (the beginning of the sub-period), the video stream is acquired and stored at 1fps; from 10:00:03 to 10:00:57 (the middle sub-period), the video stream is acquired and stored at 0.33fps; and from 10:00:57 to 10:01:00 (the end of the sub-period), the video stream is again acquired and stored at 1fps. At 10:01:00, it is confirmed that the user has turned off the preview, the recording device has no other tasks, and returns to sleep mode. When the user plays back the recording the next day, they will see that the 10:00:00-10:00:03 and 10:00:57-10:01:00 segments switch quickly (updating every 1 second), while the middle segment switches slowly (updating every 3 seconds). Through this visual rhythm, the user can intuitively identify that this is the time period they previewed yesterday.

[0078] In another specific implementation, at least one sub-time period includes only one sub-time period, that is, the target sub-time period includes only that one sub-time period, and the target sub-time period corresponds to the entire preview time period.

[0079] Take, for example, a scenario where a user performs a very short preview: Users can quickly view the monitoring footage; the preview lasts only 5 seconds, during which the video stream is continuously acquired and stored at 1fps. During playback, users see a 5-second fast-paced sequence (one frame per second), clearly marked as the user's preview period.

[0080] Optionally, in this embodiment, to avoid the visual abruptness that may be caused by sudden changes in frame rate during the target sub-period, the frame rate of the target sub-period can also adopt a gradual change pattern. For example, within the target sub-period, the frame rate is linearly or non-linearly increased from a first frame rate (e.g., 0.33fps) to 1fps, and then linearly or non-linearly decreased back to the first frame rate (e.g., 0.33fps). This gradual change pattern is more natural in visual presentation and is equally recognizable.

[0081] In one implementation, the frame rate and duration of the target sub-segment are not fixed but can be dynamically adjusted according to actual needs. Adjusting the frame rate of the target sub-segment can be achieved by adjusting the acquisition frame rate of the storage stream by the multi-stream encoder or by adjusting the aforementioned filtering frame rate, which will not be explained further here.

[0082] In this embodiment, at least one of the frame rate corresponding to the target sub-segment and the duration of the target sub-segment is used as the target labeling parameter of the target sub-segment. Determining the target labeling parameter of the target sub-segment includes the following steps: determining at least one evaluation factor; and combining the at least one evaluation factor to determine the target labeling parameter of the target sub-segment. The at least one evaluation factor includes at least one of the following: the current battery level of the recording device, the current remaining storage space of the recording device, the current network quality of the recording device, and the frequency at which the user initiates previews.

[0083] For example, at least one evaluation factor includes the current battery level of the recording device. The higher the current battery level of the recording device, the larger the target marker parameter for the target sub-period; the lower the current battery level of the recording device, the smaller the target marker parameter for the target sub-period, in order to reduce power consumption.

[0084] For example, at least one evaluation factor includes the current remaining storage space of the recording device. The more remaining storage space the recording device has, the larger the target marker parameter for the target sub-period; the less remaining storage space the recording device has, the smaller the target marker parameter for the target sub-period, in order to reduce storage space usage.

[0085] For example, at least one evaluation factor includes the current network quality of the recording device. The better the current network quality of the recording device, the larger the target label parameter for the target sub-period; the worse the current network quality of the recording device, the smaller the target label parameter for the target sub-period.

[0086] For example, at least one evaluation factor includes the frequency of user-initiated previews. The lower the frequency of user-initiated previews, the larger the target marker parameter for the target sub-period; the higher the frequency of user-initiated previews, the smaller the target marker parameter for the target sub-period, in order to minimize the storage space occupied by AOV recordings generated during the preview period.

[0087] In this embodiment, by comprehensively considering various evaluation factors to determine the target marker parameters for the target sub-time period, the target marker parameters for the target sub-time period can be made more consistent with the actual state of the recording device, thereby achieving a balance between user experience and the power consumption and storage usage of the recording device.

[0088] In one specific implementation, determining the target labeling parameter by integrating at least one evaluation factor further includes the following sub-steps: Sub-step one: Determine the evaluation score for each evaluation factor.

[0089] For each evaluation factor, the corresponding evaluation score can be determined according to the scoring rules for that factor.

[0090] The current battery level of the recording device is directly proportional to its evaluation score. The higher the current battery level, the higher the evaluation score; the lower the current battery level, the lower the evaluation score.

[0091] The remaining storage space of a recording device is directly proportional to its evaluation score. The more remaining storage space a recording device has, the higher its evaluation score; conversely, the less remaining storage space a recording device has, the lower its evaluation score.

[0092] The current network quality of a recording device is directly proportional to its evaluation score; the better the current network quality, the higher the evaluation score; the worse the current network quality, the lower the evaluation score.

[0093] The frequency with which users initiate previews is inversely proportional to their evaluation scores. The more frequently users initiate previews, the higher their evaluation scores; conversely, the less frequently users initiate previews, the lower their evaluation scores.

[0094] Sub-step two involves combining the evaluation scores of each evaluation factor to obtain the overall score.

[0095] For example, the sum of the evaluation scores of each evaluation factor is obtained as the comprehensive score.

[0096] For example, the average score of the evaluation scores of each evaluation factor can be obtained as the comprehensive score.

[0097] For example, the scores of each evaluation factor can be weighted and summed, and the resulting weighted sum can be used as the overall score. The weighting coefficients for each evaluation factor can be set according to the importance of that factor. For instance, the weighting coefficients for the current battery level and the remaining storage space of the recording device can be set to higher values, while the weighting coefficients for the other evaluation factors can be set to lower values.

[0098] Sub-step three: Determine the target score range corresponding to the overall score.

[0099] The target score interval is one of several preset score intervals. The preset score interval to which it belongs can be determined based on the value of the comprehensive score, and it serves as the target score interval.

[0100] For example, if several preset score ranges include [0,30), [30,60), [60,80), and [80,100], and the determined comprehensive score is 75 points, then the target score range corresponding to this comprehensive score is [60,80].

[0101] Sub-step four: Select the labeling parameters corresponding to the target score interval from the first mapping relationship, and use them as the target labeling parameters.

[0102] The first mapping relationship includes the aforementioned preset score intervals and the preset label parameters corresponding to each preset score interval. The preset score intervals and the preset label parameters corresponding to each preset score interval in the first mapping relationship can be designed according to specific needs.

[0103] In another specific embodiment, at least one evaluation factor includes the current battery level of the recording device and the current remaining storage space of the recording device. Combining at least one evaluation factor to determine the target marker parameter further includes the following sub-steps: Sub-step one: Using the current battery level and remaining storage space of the recording device, determine the target operating mode of the recording device.

[0104] The target operating mode is one of several preset operating modes. Different preset operating modes correspond to different power and storage space ranges. Therefore, the current power level and remaining storage space of the recording device can be used to determine the corresponding preset operating mode, which can then be used as the target operating mode.

[0105] Step 2: Select the marker parameter corresponding to the target working mode from the second mapping relationship and use it as the target marker parameter.

[0106] The second mapping relationship includes the aforementioned preset working modes and the preset marker parameters corresponding to each preset working mode.

[0107] For example, several preset operating modes include high-performance mode, balanced mode, power-saving mode, and emergency mode. The high-performance mode corresponds to a battery level greater than 50% (representing sufficient battery power) and a storage space range greater than a first storage threshold (representing sufficient storage space). The balanced mode corresponds to a battery level greater than or equal to 20% and less than 50%. The power-saving mode corresponds to a battery level greater than or equal to 5% and less than 20% and a storage space range greater than a second storage threshold and less than a third storage threshold (representing limited storage space). The emergency mode corresponds to a battery level less than 5%. The first, second, and third storage thresholds can be set according to actual needs.

[0108] For example, the preset flag parameters corresponding to the preset working mode include the frame rate R_start of the start sub-segment and the frame rate R_end of the end sub-segment, as well as the duration ΔT_start of the start sub-segment and the duration ΔT_end of the end sub-segment. In this example, the second mapping relationship can be shown in the following table:

[0109] In this case, R_start and R_end not being marked indicates that the frame rate remains low for the first frame rate.

[0110] Taking outdoor surveillance scenarios as an example: The recording equipment is solar-powered, with 18% battery remaining at dusk. A user, noticing an anomaly while reviewing the footage, initiated a preview request, previewing for 40 seconds. The recording equipment detected the 18% battery level and determined it was in power-saving mode. It then pushed a 20fps preview stream to the user. Furthermore, the recording equipment implemented a marking strategy specific to power-saving mode during the preview period. Specifically, in the initial sub-period (1 second after the preview started), the recording equipment acquired and stored the video stream at 0.5fps; and in the final sub-period (the remaining 39 seconds of the preview), it maintained a 0.33fps acquisition and storage rate. When the user's preview ended (e.g., the recording equipment received a preview end command and waited 3 seconds to confirm the end), the recording equipment returned to sleep mode. During playback, the user observed slightly faster frame transitions in the first second of the preview period, followed by slower transitions. Although the markings were less pronounced than in high-performance mode, the user could still perceive that a preview period had been completed. Compared to high-performance mode, this preview significantly reduced additional power consumption, ensuring the recording equipment's long-term battery life under low power conditions.

[0111] In some implementations, when the evaluation factors of the recording device (such as current battery level, current remaining storage space, etc.) change, a new target marker parameter for the target sub-period can be determined based on the evaluation factors, and the target marker parameter for the target sub-period in the current preview can be switched to the new target marker parameter, or the new target marker parameter can be switched to the next preview after the current preview ends.

[0112] In one implementation, if an event is detected during the preview period, the recording device enters event recording mode. At this time, the frame rate of the target sub-period is no longer marked; that is, the frame rate marking mode is automatically paused to ensure the integrity and purity of the event recording. If the event ends but the preview period has already elapsed (e.g., the event occurs in the middle of the preview), the frame rate marking mode can be resumed or re-executed.

[0113] Take, for example, a scenario where events occur during the preview period: The user initiated a preview at 14:00:00, planning to watch it continuously. At the start of the preview, the battery was at 60%, and the recording device was marked for high-performance mode. At 14:00:20 (20 seconds into the preview), an intrusion occurred, and the recording device immediately switched to event recording mode. The event lasted 15 seconds until 14:00:35. During this period, the device's battery level dropped from 60% to 48% (the threshold for entering balanced mode). After the event ended, the user continued previewing until 14:01:00. The recording device's execution flow includes: From 14:00:00 to 14:00:05 (the start of the sub-period): recording a 5-second video stream at 1fps; from 14:00:05 to 14:00:20: recording a video stream at 0.33fps; at 14:00:20, an event is detected, and event recording begins at 20fps; at 14:00:35, the event ends, the current battery level is detected as 48% (already in balanced mode), and it is still within the preview period (25 seconds remaining); from 14:00:35 to 14:00:57: resuming video streaming at 0.33fps; from 14:00:57 to 14:01:00: executing the balanced mode's ΔT_end flag, recording a 3-second video stream at 0.5fps. After the preview ends, the recording device enters sleep mode. When users replay the recording of this period, they see: a fast-paced sequence at the beginning of the preview (marked at 1fps, 5 seconds), followed by a slow-motion sequence (0.33fps), then a sudden switch to smooth event recording (20fps, 15 seconds), clearly recording the intrusion. After the event ends, the slow-motion sequence resumes, followed by another fast-paced sequence (0.5fps, 3 seconds) before the preview ends. Users don't need to view any recording metadata; they can fully understand what happened and whether they previewed the recording solely based on the embedded visual markers.

[0114] Optionally, the duration of each target sub-period can be determined based on the user's recent historical preview behavior. Specifically, the duration of each target sub-period can be determined based on the average historical preview duration corresponding to multiple historical previews within a preset historical period. For example, the preset historical period could be the previous 3 days, the previous 5 days, etc. The duration of the target sub-period can be proportional to the average historical preview duration. The longer the average historical preview duration, the longer the duration of the target sub-period; the shorter the average historical preview duration, the shorter the duration of the target sub-period.

[0115] In one implementation, when a user discovers a scene of interest during the preview period and actively marks it (e.g., by clicking the "Mark this segment" button (for marking a specific time period of recording), "Screenshot," "Enable recording of key focus areas," or "Mark for attention" button on the user's interface), the user's terminal sends a preview marking command to the recording device. Upon receiving the preview marking command, the recording device automatically generates a user-focused segment related to the preview marking command. This user-focused segment provides context for the user's active focus, thus providing a complete cause and effect. This process may further include the following steps: Step 1: In response to receiving a preview marker instruction sent by the user during the preview period, obtain the trigger time corresponding to the preview marker instruction.

[0116] The user can send the trigger time corresponding to the preview marker command to the recording device along with the preview marker command.

[0117] Step 2: Using the first video stream within a first duration before the trigger time and the second video stream within a second duration after the trigger time, generate a user-focused segment about the preview marker instruction.

[0118] The recording device maintains a buffer in its memory, which stores the most recent N seconds of low frame rate (first frame rate, frame rate within a preset frame rate range) video stream output by a multi-stream encoder, or the most recent N seconds of fourth frame rate (high frame rate) video stream output by a single-stream encoder. It is understood that the N seconds of video stream stored in this buffer are continuously updated during the recording process. For details regarding multi-stream encoders and single-stream encoders, please refer to the previous embodiments; they will not be repeated here.

[0119] For example, the cache is a circular cache.

[0120] For example, N seconds is 30 seconds.

[0121] Upon receiving a preview marker command, the recording device retrieves the first video stream from the buffer, which is the first duration preceding the trigger time. Assuming the trigger time corresponding to the preview marker command is denoted as T_mark, and the first duration as M, the recording device will retrieve video frames from the buffer between (T_mark-M) and T_mark, i.e., the first video stream. For example, the first duration is 15 seconds. The specific first duration can be configured according to actual needs.

[0122] In one example, after receiving a preview marker instruction within the preview period, low frame rate recording is no longer used. Instead, high frame rate recording is switched to use the aforementioned second or third frame rate to acquire and store the video stream, and the video stream acquired at the second or third frame rate within the second duration after the trigger time is acquired as the second video stream.

[0123] In another example, upon receiving a preview marker instruction within the preview period, the video stream output by the single-stream encoder at the fourth frame rate (high frame rate) within the second duration after the trigger time is obtained as the second video stream. Alternatively, upon receiving a preview marker instruction within the preview period, the video stream output by the single-stream encoder at the fourth frame rate within the second duration after the trigger time is further frame-filtered to obtain the second video stream.

[0124] For example, the second duration is 30 seconds. The specific duration can be configured according to actual needs.

[0125] Furthermore, after acquiring the first video stream and the second video stream, the user-focused segment regarding the preview marker instruction is generated using the first video stream and the second video stream.

[0126] In one example, the extracted first video stream is spliced ​​with the second video stream to obtain the merged user-focused segment.

[0127] In another example, the first and second video streams are directly used as the segments of interest to the user, and the first and second video streams are associated in the corresponding recording metadata so that the user knows that the first and second video streams are related to the same preview markup instruction.

[0128] Step 3: Store the segments that users are interested in.

[0129] In one example, a video background label is generated for the segment the user is following; this label can be "User-Followed Segment". Furthermore, the start time, end time, and trigger time of the segment can be obtained. Further, the video background label, start time, end time, and trigger time of the segment can be added to the corresponding video metadata for that segment.

[0130] Furthermore, when a user plays back a recording via the client, a special icon corresponding to the user-focused segment can be highlighted. This icon can be a star or other bookmarks. When the user clicks this icon, the client can directly start playback from the beginning of the user-focused segment, thus fully reproducing the sequence of events following the preview marker command and further improving the user experience.

[0131] Taking a shop surveillance scenario as an example: At 19:30:00, the user began previewing the store's interior via their client. At 19:30:20 (20 seconds into the preview), a suspicious person was observed loitering in front of the shelves. The user immediately clicked the "Mark for Attention" button on the client's display. The recording device received the user's preview marker command at 19:30:20, determined the trigger time T_mark to be 19:30:20, and extracted 15 seconds of low-frame-rate AOV recording (approximately 0.2 fps, about 3 frames) from the circular buffer. The recording device then switched to a high-frame-rate of 20 fps and recorded a high-definition recording of the "attention" segment starting at 19:30:20, lasting 30 seconds. Afterward, the recording device merged the two recordings into a single file named "User Attention Segment_20260315_193005". Furthermore, the recording device records the following information in the video metadata of the user-focused segment: Segment type: User-initiated focus; Start time: 19:30:05; Trigger time: 19:30:20. The user continues to preview until closing the preview. During playback, the user sees a special file with a special icon. After clicking the icon, the user-focused segment begins playing from 19:30:05: the first 15 seconds are slowly switching low frame rate footage, showing the suspicious person entering the frame and approaching the shelf; after 15 seconds, it automatically switches to a high frame rate smooth video, clearly recording the details of their stay and departure.

[0132] Optionally, the recording device can also upload the captured user-interested segments to cloud storage. When uploading user-interested segments, the recording device can employ a segmented upload mechanism, dividing the user-interested segments into multiple sub-segments and uploading them to the cloud separately. If a network interruption occurs during the upload process, the recording device can record the breakpoint and resume the upload once the network is restored.

[0133] Furthermore, the cloud can also perform integrity checks on the received user-focused segments to ensure that no user-focused segments are lost.

[0134] In one example, the cloud receives the entire user-focused segment sent by the recording device, along with a first checksum of that segment (e.g., obtained by hashing the user-focused segment). The cloud can then calculate a second checksum for the received user-focused segment and compare it with the first checksum. If the second checksum matches the first checksum, the integrity check is considered successful; otherwise, the integrity check is considered unsuccessful.

[0135] In another example, the cloud receives each sub-segment of the user-focused segment sent by the recording device, along with the calculated third checksum for each sub-segment. For each sub-segment: the cloud calculates a fourth checksum for the sub-segment and compares it with the third checksum; if the fourth checksum matches the third checksum, the sub-segment's integrity check is considered passed; if the fourth checksum does not match the third checksum, the sub-segment's integrity check is considered failed.

[0136] Optionally, when a user actively performs a marking operation during the preview period, even in power-saving mode, the target marking parameters of the target sub-period can be increased for a short time, such as setting the frame rate of the target sub-period to 1fps and the duration of the target sub-period to 0.3 seconds, in order to ensure the clarity of the generated user-focused segments.

[0137] Please see Figure 2 , Figure 2 This is a schematic diagram of a framework of an embodiment of the recording device provided in this application. In this embodiment, the recording device 20 includes a wake-up module 21, a type determination module 22, and a storage stream acquisition module 23. The wake-up module 21 is used to switch to wake-up mode in response to receiving a wake-up request in sleep mode. The type determination module 22 is used to determine the trigger type of the wake-up request. The storage stream acquisition module 23 is used to acquire and store the video stream at a first frame rate in sleep mode. Furthermore, the storage stream acquisition module 23 is used to acquire and store the video stream at a second frame rate in response to an event-triggered trigger type, where the event-triggered type indicates that an event has been detected in the video stream, and the second frame rate is greater than the first frame rate; and to acquire and store the video stream at a frame rate within a preset frame rate range in response to a non-event-triggered trigger type, where the upper limit of the preset frame rate range is less than the second frame rate.

[0138] In one embodiment, the trigger type is non-event-triggered, and the wake-up request is either a preview request from the user or a service request from the recording device. The storage stream acquisition module 23 is used to acquire and store the video stream at a first frame rate.

[0139] In one embodiment, the trigger type is non-event triggered, the wake-up request is a preview request from the user terminal, and the preview period of the user terminal is divided into at least one sub-period during the recording process. The storage stream acquisition module 23 is used to acquire and store the video stream at a frame rate within a preset frame rate range in each sub-period corresponding to the preview period; wherein, in at least one sub-period, there exists a target sub-period with a frame rate greater than a first frame rate.

[0140] In one embodiment, the target sub-period includes a start sub-period and an end sub-period in at least one sub-period; and / or, the frame rate corresponding to each sub-period other than the target sub-period in at least one sub-period is equal to the first frame rate.

[0141] In one embodiment, at least one of the frame rate corresponding to the target sub-period and the duration of the target sub-period is used as the target labeling parameter for the target sub-period. The storage stream acquisition module 23 is used to determine at least one evaluation factor; wherein, the at least one evaluation factor includes at least one of the current battery level of the recording device, the current remaining storage space of the recording device, the current network quality of the recording device, and the frequency of user-initiated previews; the target labeling parameter is determined by combining the at least one evaluation factor.

[0142] In one embodiment, the storage stream acquisition module 23 is used to determine the evaluation score of each evaluation factor; combine the evaluation scores of each evaluation factor to obtain a comprehensive score; determine the target score interval corresponding to the comprehensive score; and select the marker parameter corresponding to the target score interval from a first mapping relationship as the target marker parameter; wherein the first mapping relationship includes several preset score intervals and preset marker parameters corresponding to each preset score interval. Alternatively, at least one evaluation factor includes the current battery level and the current remaining storage space, and the storage stream acquisition module 23 is used to determine the target operating mode using the current battery level and the current remaining storage space; and select the marker parameter corresponding to the target operating mode from a second mapping relationship as the target marker parameter; wherein the second mapping relationship includes several preset operating modes and preset marker parameters corresponding to each preset operating mode.

[0143] In one embodiment, the trigger type is non-event triggered, and the wake-up request is a preview request from the user. The storage stream acquisition module 23 is further configured to, in response to receiving a preview marker instruction sent by the user during the preview period, acquire the trigger time corresponding to the preview marker instruction; generate a user-focused segment about the preview marker instruction using a first video stream within a first duration before the trigger time and a second video stream within a second duration after the trigger time; and store the user-focused segment.

[0144] In one embodiment, the trigger type is non-event-triggered, and the wake-up request is a preview request from the user terminal. The recording device further includes a preview stream acquisition module 24, which is used to acquire a video stream at a third frame rate to obtain a preview stream and push the preview stream to the user terminal. The third frame rate is greater than the first frame rate. The preview stream and the storage stream of the recording device are obtained by independently encoding using a multi-stream encoder; or, the preview stream and the storage stream of the recording device are obtained by frame filtering of a video stream at a fourth frame rate generated using a single-stream encoder. The storage stream includes a video stream acquired and stored by the recording device in sleep mode at a first frame rate, a video stream acquired and stored at a second frame rate during an event wake-up period, and a video stream acquired and stored at a frame rate within a preset frame rate range during non-event wake-up periods.

[0145] Please see Figure 3 , Figure 3 This is a schematic diagram of a frame of an embodiment of the video recording device provided in this application. In this embodiment, the video recording device 30 includes a memory 31 and a processor 33.

[0146] Processor 33 can also be referred to as CPU (Central Processing Unit). Processor 33 may be an integrated circuit chip with signal processing capabilities. Processor 33 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. A general-purpose processor can be a microprocessor, or processor 33 can be any conventional processor 33, etc.

[0147] The memory 31 in the recording device 30 is used to store the program instructions required for the processor 33 to run.

[0148] The processor 33 is used to execute program instructions to implement the recording method in this application.

[0149] Please see Figure 4 , Figure 4This is a schematic diagram of a framework of an embodiment of the computer-readable storage medium provided in this application. The computer-readable storage medium 40 of this application embodiment stores program instructions 41, which, when executed, implement the recording method provided in this application. The program instructions 41 can form a program file and be stored in the aforementioned computer-readable storage medium 40 in the form of a software product, so that a computer device (which may be a personal computer, server, or network device, etc.) can execute all or part of the steps of the methods of various embodiments of this application. The aforementioned computer-readable storage medium 40 includes various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or terminal devices such as computers, servers, mobile phones, and tablets.

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

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

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

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

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

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

[0156] It should be noted that if the technical solution of this application involves personal information, the product using this technical solution has clearly informed the user of the personal information processing rules and obtained the user's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using this technical solution has obtained the user's separate consent before processing the sensitive personal information, and also meets the requirement of "express consent". For example, at personal information collection devices such as cameras, clear and prominent signs are set up to inform users that they have entered the scope of personal information collection and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed that they have agreed to the collection of their personal information; or on the personal information processing device, the personal information processing rules are clearly informed through signs / information, and authorization is obtained through pop-up information or by asking the individual to upload their personal information. The personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

[0157] This application provides only the technology. The specific data required for the application shall be subject to the actual situation. However, users are advised that when using this technology, the collection and processing of data should comply with laws and regulations related to data and personal information protection.

[0158] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A video recording method, characterized by, Applied to a video recording device, the method includes: In response to receiving a wake-up request in sleep mode, the device switches to wake-up mode and determines the trigger type of the wake-up request, wherein the recording device acquires and stores a video stream at a first frame rate in sleep mode; In response to the trigger type being event-triggered, a video stream is acquired and stored at a second frame rate, wherein the event-triggered type indicates that an event is detected from the video stream, and the second frame rate is greater than the first frame rate; In response to the triggering type being non-event triggered, the video stream is acquired and stored at a frame rate within a preset frame rate range, wherein the upper limit of the preset frame rate range is less than the second frame rate.

2. The method of claim 1, wherein, The trigger type is the non-event triggered type, and the wake-up request is either a preview request from the user or a service request from the recording device; The process of acquiring and storing the video stream at a frame rate within a preset frame rate range includes: The video stream is acquired and stored at the first frame rate.

3. The method of claim 1, wherein, The trigger type is the non-event triggered type, the wake-up request is the preview request from the user terminal, and the preview time period of the user terminal is divided into at least one sub-time period during the recording process; The process of acquiring and storing the video stream at a frame rate within a preset frame rate range includes: In each of the sub-time periods corresponding to the preview time period, the video stream is acquired and stored at a frame rate within the preset frame rate range; Wherein, in at least one sub-time period, there exists a target sub-time period whose frame rate is greater than the first frame rate.

4. The method according to claim 3, characterized in that, The target sub-time period includes the start sub-time period and the end sub-time period of the at least one sub-time period; And / or, the frame rate corresponding to each of the at least one sub-time period other than the target sub-time period is equal to the first frame rate.

5. The method of claim 3, wherein, At least one of the frame rate corresponding to the target sub-segment and the duration of the target sub-segment is used as the target marker parameter of the target sub-segment; The steps for determining the target marker parameters include: Determine at least one evaluation factor; wherein the at least one evaluation factor includes at least one of the following: the current battery level of the recording device, the current remaining storage space of the recording device, the current network quality of the recording device, and the frequency of user-initiated previews; The target labeling parameters are determined by combining the at least one evaluation factor.

6. The method according to claim 5, characterized in that, The determination of the target label parameter by integrating the at least one evaluation factor includes: Determine the evaluation score for each of the evaluation factors; The overall score is obtained by combining the evaluation scores of each evaluation factor. Determine the target score range corresponding to the comprehensive score; The labeling parameter corresponding to the target score interval is selected from the first mapping relationship and used as the target labeling parameter; wherein, the first mapping relationship includes a plurality of preset score intervals and preset labeling parameters corresponding to each preset score interval; Alternatively, the at least one evaluation factor includes the current battery level and the current remaining storage space, and the step of combining the at least one evaluation factor to determine the target marker parameter includes: The target operating mode is determined using the current battery level and the current remaining storage space. The target working mode is selected from the second mapping relationship as the target label parameter; wherein, the second mapping relationship includes a number of preset working modes and preset label parameters corresponding to each preset working mode.

7. The method of claim 1, wherein, The trigger type is the non-event-triggered type, and the wake-up request is a preview request from the user's client. The method further includes: In response to receiving a preview marker instruction sent by the user during the preview period, the trigger time corresponding to the preview marker instruction is obtained; Using a first video stream within a first duration prior to the trigger time and a second video stream within a second duration after the trigger time, a user-focused segment related to the preview marker instruction is generated, and the user-focused segment is stored.

8. The method of claim 1, wherein, The trigger type is the non-event-triggered type, and the wake-up request is a preview request from the user's client. The method further includes: A preview stream is obtained by acquiring a video stream at a third frame rate, and the preview stream is pushed to the user terminal, wherein the third frame rate is greater than the first frame rate; The preview stream and the storage stream of the recording device are obtained by independently encoding each using a multi-stream encoder; or, the preview stream and the storage stream of the recording device are obtained by frame filtering of a video stream with a fourth frame rate generated using a single-stream encoder. The storage stream includes a video stream acquired and stored by the recording device in the sleep mode at the first frame rate, a video stream acquired and stored in the event wake-up period at the second frame rate, and a video stream acquired and stored in the non-event wake-up period at a frame rate within the preset frame rate range.

9. A video recording device, characterized in that, Including interconnected memory and processor, The memory stores program instructions; The processor is used to execute program instructions stored in the memory to implement the method according to any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store program instructions that can be executed by a processor to implement the method of any one of claims 1-8.

Images