Low-power camera event push method, electronic device, and readable storage medium

Abstract

The application discloses a low-power-consumption camera event pushing method, an electronic device and a readable storage medium. The method comprises the following steps: in response to the camera being woken up, all unpushed events are acquired, and at least part of the events are cached based on the remaining power of the camera and the priority of the events; the historical pushing duration of the events when the events are pushed by different types of transmission protocols is acquired, the delay sleep duration is determined based on the remaining power of the camera and the historical pushing duration of all types of transmission protocols; in response to any type of transmission protocol being online on the camera and the platform corresponding to the camera within the delay sleep duration, the at least part of the cached events are pushed to the platform according to the priority of the events by using the online transmission protocol; and in response to the delay sleep duration being reached, the camera is controlled to sleep. Through the above method, the application can guarantee that the probability of event omission is reduced under the condition that the power consumption of the camera is low.

Description

Technical Field

[0001] This application relates to the field of device communication technology, and in particular to a low-power camera event push method, electronic device, and readable storage medium. Background Technology

[0002] In areas with limited power supply, low-power cameras capable of hibernation during normal operation and continuous recording upon waking have become widely used. However, events detected by these cameras are prone to being missed. Conventional methods to reduce this omission significantly increase the camera's operating time, which greatly increases power consumption. Therefore, minimizing event omissions while maintaining low power consumption has become a pressing issue. Summary of the Invention

[0003] The main technical problem addressed by this application is to provide a low-power camera event push method, electronic device, and readable storage medium that can reduce the probability of event omission while ensuring low camera power consumption.

[0004] To address the aforementioned technical problems, this application provides a low-power camera event push method, comprising: in response to the camera being woken up, acquiring all unpushable events and caching at least a portion of the events based on the camera's remaining battery power and the event priorities; acquiring the historical push duration of events pushed using different types of transmission protocols, and determining a delayed sleep duration based on the camera's remaining battery power and the historical push duration of all types of transmission protocols; in response to any type of transmission protocol being launched on the camera and its corresponding platform within the delayed sleep duration, pushing at least a portion of the cached events to the platform according to the event priorities using the launched transmission protocols; and in response to reaching the delayed sleep duration, controlling the camera to go into sleep mode.

[0005] To address the aforementioned technical problems, a second aspect of this application provides an electronic device comprising: a memory and a processor coupled to each other, wherein the memory stores program data, and the processor invokes the program data to execute the method described in the first aspect.

[0006] To address the aforementioned technical problems, a third aspect of this application provides a computer-readable storage medium storing program data thereon, wherein the program data, when executed by a processor, implements the method described in the first aspect.

[0007] The beneficial effects of this application are as follows: Unlike existing technologies, when the camera is woken up, this application acquires all unpushable events. Based on the camera's current remaining battery power and the event matching priority, at least a portion of the unpushable events are cached, ensuring that events detected before wake-up can be cached according to priority, preventing event loss before camera wake-up. The application also acquires the historical push duration required for different types of transmission protocols to push events, and determines the corresponding delayed sleep duration based on the camera's current remaining battery power and the historical push duration of all types of transmission protocols. When any type of transmission protocol goes online on the camera and its corresponding platform during the delayed sleep duration, at least a portion of the cached events are pushed to the camera's corresponding platform according to the event priority using the online transmission protocol. Thus, for each transmission protocol that goes online during the delayed sleep duration, the corresponding protocol is used for event transmission, reducing the probability of event loss. When the camera reaches the delayed sleep duration, it controls the camera to sleep, ensuring that the camera maintains low power consumption and avoids prolonged operation, thus reducing the probability of event loss while ensuring low camera power consumption. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein: Figure 1 This is a flowchart illustrating one implementation of the low-power camera event push method of this application; Figure 2 This is a schematic diagram illustrating an application scenario of one embodiment of the low-power camera communication link of this application; Figure 3 This is a flowchart illustrating another implementation of the low-power camera event push method of this application; Figure 4 This is a schematic diagram illustrating an application scenario of one implementation method of the preset storage format of this application; Figure 5 This is a schematic diagram illustrating an application scenario of one embodiment of the low-power camera event push method of this application; Figure 6 This is a schematic diagram of the structure of one embodiment of the electronic device of this application; Figure 7 This is a schematic diagram of one embodiment of the computer-readable storage medium of this application. Detailed Implementation

[0009] 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 some embodiments of this application, not all embodiments, and different implementation methods can be adaptively combined. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0010] In this paper, the terms "system" and "network" are often used interchangeably. The term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this paper means two or more.

[0011] The low-power camera event push method provided in this application is used to push events detected by a low-power camera, and its corresponding execution subject is a processing unit capable of data processing.

[0012] Please see Figure 1 , Figure 1 This is a flowchart illustrating one embodiment of the low-power camera event push method of this application. The method includes: S101: In response to the camera being woken up, retrieve all unpushed events and cache at least some events based on the camera's remaining battery power and the event priority.

[0013] Specifically, when the camera is woken up, all unpushed events are retrieved. Based on the camera's current remaining battery power and the priority of the events, at least some of the unpushed events are cached, thereby ensuring that events detected before the camera is woken up can be cached according to priority and avoiding the loss of events before the camera is woken up.

[0014] It's important to note that common low-power cameras include AOV (Always On Video) low-power cameras. Currently, the entire connection system between AOV low-power cameras and the cloud platform and client uses dual links due to hardware limitations. When the low-power camera is woken up, the main controller and platform establish a primary communication link. When the low-power camera is in sleep mode, the cellular or WiFi module establishes a separate sleep link with the platform. The primary link is used for device interaction and low-power camera wake-up scenarios, such as streaming, event push notifications, and software application (APP) operation of the device. The sleep link is mainly used for sending keep-alive heartbeats when the device is in sleep mode, and the platform can wake up the device through the sleep link. In sleep mode, the camera captures and analyzes images at longer time intervals to determine if a target or scene change has been detected, and / or detects a target using a passive infrared sensor. After being woken up, the camera continuously records video at a preset frame rate and pushes events.

[0015] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating an application scenario of one embodiment of the low-power camera communication link of this application. Figure 2 The low-power camera shown includes a dual-core system-on-chip (SOC), a sensor, a passive infrared sensor (PIR), a microcontroller, and a cellular / WiFi module. The main link is established between the SOC and the platform, while the sleep link is established between the cellular / WiFi module and the platform. App operations can be transmitted to the platform via an access network. Specifically, the sensor communicates with the main controller via a Mobile Industry Processor Interface (MIPI); the PIR communicates with the microcontroller, and the microcontroller communicates with the cellular / WiFi module via General Purpose Input Output (GPIO); the microcontroller communicates with the main controller via a Universal Asynchronous Receiver Transmitter (UART); the cellular / WiFi module is connected to the main controller via a Universal Serial Bus (USB); and the app communicates with the access network via Long Term Evolution (LTE) standards.

[0016] In one implementation, in response to the camera being woken up, all unpushed events on the camera are acquired, the remaining battery level of the camera is determined to be within a certain range, the allowed caching priority for that range is determined, and the events corresponding to the allowed caching priority are cached.

[0017] In one implementation, in response to the camera being woken up, all events detected before and during the wake-up process are acquired, the number of push notifications allowed by the camera's remaining battery power is determined, and events not exceeding the number of push notifications are cached from the highest priority to the lowest priority based on the priority of the events and the number of push notifications allowed by the remaining battery power.

[0018] It should be noted that the events detected by the camera have different priorities based on their event types.

[0019] Optionally, events related to the camera itself have the highest priority, events matching a target of a preset type detected by the camera have the second highest priority, and image-related events detected after the camera is woken up have the lowest priority.

[0020] In some implementation scenarios, the camera's remaining battery power is divided into multiple battery ranges from 0% to 100%. The larger the battery range, the more priority events can be cached. The battery range with the smallest value can only cache the highest priority events, while the battery range with the largest value can cache events of all priorities.

[0021] In some implementation scenarios, the camera's remaining battery power is converted into the number of push notifications based on a quantity conversion function. The number of push notifications is positively correlated with the remaining battery power, thus allowing more events to be cached when the battery is more abundant.

[0022] In a specific implementation scenario, event types include system events, wake-up events, and post-wake-up events. System events have the highest priority and include events directly related to the camera, such as anti-tampering and battery malfunctions. Wake-up events have the second highest priority and include Smart Motion Detection (SMD) events triggered during sleep mode. Post-wake-up events have the lowest priority and include all ordinary motion detection (MD) events detected after the camera wakes up but before the transmission protocol goes online. SMD events correspond to preset target changes, while MD events correspond to pixel changes between different frames.

[0023] S102: Obtain the historical push duration for push events of different types of transmission protocols, and determine the delayed sleep duration based on the camera's remaining battery power and the historical push duration of all types of transmission protocols.

[0024] Specifically, the historical push duration required for pushing events in different types of transmission protocols is obtained, and the corresponding delayed sleep duration of the camera is determined based on the camera's current remaining battery power and the historical push duration of all types of transmission protocols.

[0025] In one embodiment, the average duration required to push events within a preset period for different types of transmission protocols is obtained as the historical push duration. Based on the battery range of the camera's remaining battery power, a reference delay duration matching the corresponding battery range is determined. One of the durations, the reference delay duration and the historical push duration of each transmission protocol, is selected as the delayed sleep duration.

[0026] In one implementation, the historical push duration required for the last push event of different types of transmission protocols is obtained, a reference delay duration positively correlated with the remaining battery power is determined based on the remaining battery power of the camera, and a delay sleep duration that allows at least one protocol to push events is determined based on the reference delay duration and the historical push duration of each transmission protocol.

[0027] In some implementation scenarios, the remaining battery power of the camera is divided into multiple battery ranges from 0% to 100%. The larger the value of the battery range, the larger the reference delay duration is. The historical push duration of each transmission protocol is compared with the reference delay duration, and the duration with the largest value among the historical push durations that are less than the reference delay duration is selected as the delay sleep duration.

[0028] In some implementation scenarios, the remaining power is converted into a reference delay duration based on a duration conversion function. The reference delay duration is positively correlated with the remaining power. From the reference delay duration and the historical push duration of all transmission protocols, a delay sleep duration that allows at least one protocol to push events is selected.

[0029] S103: In response to any type of transmission protocol going online on the camera and its corresponding platform during the delayed sleep period, push at least a portion of the cached events to the platform according to the priority of the events using the online transmission protocol.

[0030] Specifically, when any type of transmission protocol is launched on the camera and its corresponding platform during the camera's delayed sleep period, at least a portion of the cached events are pushed to the camera's corresponding platform according to the priority of the events using the launched transmission protocol.

[0031] Understandably, during the delay sleep period, if a transmission protocol comes online, the corresponding protocol will be used for event transmission to reduce the probability of event omission.

[0032] It should be noted that the camera will connect to the network before the transmission protocol goes online. The transmission protocol for external access goes online relatively slowly, but wake-up and various detection events occur earlier than the protocol goes online. Therefore, the events detected before the protocol goes online are cached and then pushed after the protocol goes online, thus realizing wake-up caching and push as soon as the network and protocol are ready.

[0033] In one implementation, when any type of transmission protocol is launched on the camera and its corresponding platform during the camera's delayed sleep period, all cached events are pushed to the camera's corresponding platform according to the priority of the events using the launched transmission protocol.

[0034] In one implementation, when any type of transmission protocol goes online on the camera and the platform corresponding to the camera during the camera's delayed sleep period, the subscription information corresponding to the online transmission protocol is determined, and the cached subscribed events are pushed to the platform corresponding to the camera according to the priority of the events based on the subscription information.

[0035] It should be noted that different types of transmission protocols include at least Hyper Text Transfer Protocol (HTTP), Message Queuing Telemetry Transport (MQTT), and Open Network Video Interface Forum (ONVIF). This application does not impose specific restrictions on any particular transmission protocol. Once any type of transmission protocol goes online within the delay sleep period, an event will be pushed to the platform based on the corresponding transmission protocol.

[0036] S104: In response to reaching the delayed sleep duration, control the camera to go into sleep mode.

[0037] Specifically, once the camera reaches the timeout period, it is put into sleep mode to ensure that the camera can always maintain low power consumption and avoid working for a long time, so as to reduce the probability of missing events while ensuring low power consumption.

[0038] In one embodiment, once the delay sleep duration is reached, the camera is immediately put into sleep mode to ensure that the camera's working time does not exceed the delay sleep duration.

[0039] In one implementation, after the delay sleep duration is reached, it is determined whether the online transmission protocol is still being used to push events. If so, no other protocols are added, and the camera is immediately put into sleep mode after the event is pushed. If not, the camera is immediately put into sleep mode to ensure that the online protocols can push events completely.

[0040] The above scheme, upon camera wake-up, acquires all unpushable events. Based on the camera's remaining battery power and event priority, at least a portion of the unpushable events are cached, ensuring that events detected before wake-up are cached according to priority, preventing event loss before camera wake-up. The scheme also retrieves the historical push duration required for different types of transmission protocols to push events, determining the corresponding delayed sleep duration based on the camera's remaining battery power and the historical push durations of all transmission protocols. When any type of transmission protocol goes online on the camera and its corresponding platform during the delayed sleep duration, at least a portion of the cached events are pushed to the platform according to event priority using the online transmission protocol. This ensures that for each transmission protocol that goes online during the delayed sleep duration, the corresponding protocol is used for event transmission, reducing the probability of event loss. Once the camera reaches the delayed sleep duration, it is put into sleep mode to ensure the camera maintains low power consumption, avoiding prolonged operation and minimizing event loss while maintaining low power consumption.

[0041] Please see Figure 3 , Figure 3 This is a flowchart illustrating another embodiment of the low-power camera event push method of this application, the method including: S201: In response to the camera being woken up, retrieve all unpushed events and cache at least some events based on the camera's remaining battery power and the event priority.

[0042] Specifically, the camera wake-up conditions include at least one of the following: the camera detects an event of a preset type, or the sleep link between the camera and the platform receives a wake-up signal. After the camera wakes up, it switches from the sleep link to the main link between the camera and the platform. Once the camera is woken up, it acquires events that were not pushed before the camera was woken up and continuously monitors events after the wake-up. Based on the camera's current remaining battery power and the priority of event matching, at least a portion of the unpushed events are cached. Therefore, upon waking the camera under any condition, event caching is immediately performed, and the camera switches from the sleep link to the main link to facilitate event pushing.

[0043] It should be noted that when the camera detects a preset type of event, i.e., after the camera is awakened from sleep mode by an event triggered by hardware, it is cached immediately. Alternatively, when the sleep link between the camera and the platform receives a wake-up signal, i.e., after a network connection is established between the device and the platform, it is awakened by software and cached immediately. The wake-up signal can be a periodic signal or a signal actively sent by the user as needed. Therefore, this dual-condition caching mechanism caches events at the initial stage of system wake-up, ensuring that even if the underlying hardware or network stack is not fully initialized, triggered events can be reliably stored, providing buffer time for subsequent pushes and improving system reliability.

[0044] In one embodiment, acquiring all unpushable events and caching at least some events based on the camera's remaining battery power and the event priority includes: acquiring all unpushable events and determining the priority corresponding to each event based on its type; determining the battery range in which the camera's remaining battery power is located, acquiring a target priority that matches the battery range, and caching events that match the target priority to a preset memory space.

[0045] Specifically, all unpushed events are retrieved, and the event type of each event is determined to obtain a priority that matches the event type.

[0046] Furthermore, the remaining battery level of the camera is determined to be within a certain range. Each range has a target priority that can be cached, and the higher the value of the range, the more target priorities can be cached. Events that match the target priorities are cached in a preset memory space, thereby pre-allocating and managing a dedicated memory area for caching events and ensuring the reliability of the cache.

[0047] For ease of understanding, we will still use three priority levels as an example. Events related to the camera itself have the highest priority, events matching a preset type of target detected by the camera have the second highest priority, and image-related events detected after the camera is woken up have the lowest priority. When the remaining battery is less than 5%, only the highest priority event is cached after waking up; when the remaining battery is between 5% and 20%, only the highest and second highest priority events are cached after waking up; when the battery exceeds 20%, events of all priorities are cached after waking up. The specific priority levels and battery ranges can be set according to actual needs and specific scenarios. This application is merely illustrative and does not impose any specific limitations.

[0048] It should be noted that caching events matching the target priority to a preset memory space includes: obtaining events matching the target priority and deduplicating them, converting the deduplicated events into a preset storage format; wherein, the preset storage format includes event information corresponding to the event and protocol information corresponding to the transmission protocol matching the event type; and caching the events in the preset storage format to the preset memory space.

[0049] Specifically, events matching the target priority are retrieved, and all events are deduplicated. The deduplicated events are then format-converted, thus unifying the format of all events into a preset storage format before caching. This preset storage format includes event information corresponding to the event and protocol information corresponding to the transmission protocol matching the event type, thereby clarifying the event, the protocol, and the relationship between them.

[0050] It is understandable that caching events in a preset storage format into a preset memory space can effectively reduce power consumption during the caching phase. Furthermore, during the push phase, the transmission protocol that can be pushed can be determined based on the information included in the preset storage format, and the event is finally converted from the preset storage format into the format required by the transmission protocol and pushed.

[0051] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating an application scenario of one embodiment of the preset storage format of this application. The preset storage format includes event information such as... Figure 4 The various types of information corresponding to cached events, and the protocol information included in the access protocol, such as... Figure 4 This includes various types of information corresponding to the transmission protocol. Furthermore, the transmission protocol is matched with user-related information; a mapping relationship exists between event information and protocol information, which can be stored in an association table. Figure 4 The number 1 indicated on the horizontal line represents a one-to-one relationship, and the letter N represents a one-to-N relationship. Figure 4 The preset storage format shown is merely a specific illustration. It can be customized according to requirements in different implementation scenarios, and this application does not impose any specific restrictions on it.

[0052] S202: Obtain the historical push duration for at least one push event of different types of transport protocols, and determine the reference push duration for the corresponding type of transport protocol based on all historical push durations for each type of transport protocol.

[0053] Specifically, the historical push duration of at least one previous push event for different types of transport protocols is obtained. For each type of transport protocol, the most recent historical push duration can be selected, or the total historical push duration of each type of transport protocol when pushing events within a preset time period, or the historical push duration of each type of transport protocol when pushing events a preset number of times.

[0054] Understandably, a reference push duration for each type of transport protocol is determined based on all historical push durations for each type of transport protocol. Typically, the average of all historical push durations for the corresponding type of transport protocol can be chosen as the reference push duration.

[0055] S203: Determine the battery range of the camera's remaining battery and obtain the reference delay duration for matching the battery range.

[0056] Specifically, the battery range in which the camera's current remaining battery power is located is determined. The full battery power is divided into multiple consecutive battery ranges, each with its own reference delay duration. The reference delay duration matching the current battery range is obtained.

[0057] For ease of understanding, let's continue with the three battery levels mentioned earlier as examples. When the remaining battery level is less than 5%, the reference delay time is 5 seconds; when the remaining battery level is between 5% and 20%, the reference delay time is 30 seconds; and when the battery level exceeds 20%, the reference delay time is 60 seconds. This application does not impose specific restrictions on the specific battery level settings or the corresponding reference delay time values.

[0058] Optionally, the reference delay duration corresponding to the smallest power range is set with reference to the transmission protocol with the shortest transmission duration. The reference delay duration corresponding to the smallest power range is greater than the shortest reference push duration among all transmission protocols, thereby ensuring that the highest priority event of a transmission protocol can be retained when the power is extremely low.

[0059] S204: Determine the delay sleep duration based on the reference delay duration for matching power ranges and the reference push duration for each type of transmission protocol.

[0060] Specifically, different durations are filtered from the reference delay duration for matching the power range and the reference push duration for each type of transmission protocol to determine the delay sleep duration.

[0061] It should be noted that cameras typically have a base sleep duration after being woken up. The delayed sleep duration is used to add to the base sleep duration to determine the complete working time after the camera is woken up, so as to ensure the success rate of event push and provide a time node for when the camera should go into sleep mode.

[0062] In one embodiment, determining the delayed sleep duration based on the reference delay duration for matching power ranges and the reference push duration for each type of transmission protocol includes: comparing the reference push duration for each type of transmission protocol with the reference delay duration for matching power ranges, determining a candidate reference push duration with the largest value and a duration less than the reference delay duration; and determining the delayed sleep duration based on the reference delay duration and the candidate reference push duration.

[0063] Specifically, the reference push duration for each type of transmission protocol is compared with the reference delay duration matching the power range. A reference push duration shorter than the reference delay duration is determined, and the reference push duration with the largest value is selected as the candidate reference push duration.

[0064] Furthermore, the time duration is selected from the reference delay duration and the candidate reference push duration to obtain the delayed sleep duration, thereby ensuring that the delayed sleep duration matches the remaining power, minimizing camera power consumption while ensuring that as many transmission protocols as possible can be used for event push.

[0065] In some implementation scenarios, the delayed sleep duration is determined based on the reference delay duration and the candidate reference push duration. This includes: obtaining a preset margin coefficient, adjusting the candidate reference push duration using the margin coefficient to obtain the target reference push duration; wherein the target reference push duration is greater than the candidate reference push duration, and the reference push duration is increased by adjusting the margin coefficient and then compared with the reference delay duration; the minimum value between the reference delay duration and the target reference push duration is taken as the delayed sleep duration.

[0066] Specifically, a preset margin coefficient is obtained, and the candidate reference push duration is adjusted using this margin coefficient to obtain the target reference push duration. This is done so that the adjusted target reference push duration is greater than the candidate reference push duration, thereby increasing the probability of successful push when the target reference push duration is selected. The margin coefficient is also used to adjust the reference push duration, increasing its value before comparing it with the reference delay duration, ensuring consistency in the comparison and selection process.

[0067] Furthermore, the minimum value between the reference delay duration and the target reference push duration is obtained as the delay sleep duration, thus achieving an optimal solution that balances power consumption and event push success rate. The above process is expressed by the following formula: (1) in, The delay sleep duration is indicated by B, the camera's battery level (0%-100%) is indicated by B, and the set of all transmission protocols supported by the camera is indicated by P. This indicates the reference delay duration for matching the power range. This is the residual coefficient. This indicates the reference push duration for different types of transport protocols. The range of values ​​is This application does not impose specific restrictions on this.

[0068] Understandable, This indicates the recommended push duration for the selected candidates. Indicates the target reference push duration.

[0069] Understandably, when comparing the reference push duration of each type of transmission protocol with the reference delay duration that matches the power range, a margin coefficient is used to adjust each reference delay duration, thereby filtering out values ​​whose adjusted duration is less than the reference delay duration.

[0070] To facilitate understanding, this application provides an example scenario where the remaining battery power is 15%. Supported transport protocols Including {Protocol A (online + push event 3s), Protocol B (online + push event 15s), Protocol C (online + push event 35s)}; The value is 0.1. Based on the above formula (1), it can be seen that in this scenario, the selected delayed sleep duration is... The camera wake-up delay is 16.5 seconds; this ensures that events are pushed via Protocol A and Protocol B within 16.5 seconds; under this battery life requirement, the slow Protocol C is discontinued and will no longer push events.

[0071] S205: In response to any type of transmission protocol going online on the camera and its corresponding platform during the delayed sleep period, push at least a portion of the cached events to the platform according to the priority of the events using the online transmission protocol.

[0072] Specifically, when any type of transmission protocol is launched on the camera and its corresponding platform during the camera's delayed sleep period, at least a portion of the cached events are pushed to the camera's corresponding platform according to the priority of the events using the launched transmission protocol.

[0073] In one embodiment, pushing at least a portion of cached events to the platform using an online transport protocol according to event priority includes: in response to the online transport protocol being subscription-based, determining the events subscribed to by the corresponding transport protocol, and pushing the subscribed events to the platform using the corresponding transport protocol according to event priority; in response to the online transport protocol being non-subscription-based, pushing all cached events to the platform using the online transport protocol according to event priority.

[0074] Specifically, the push mechanism of the online transmission protocol is determined. If the online transmission protocol is subscription-based, the events subscribed to by the corresponding transmission protocol are identified, and the subscribed events are pushed to the platform from the cached events according to the event priority using the corresponding transmission protocol. If the online transmission protocol is non-subscription-based, all cached events are pushed to the platform from the cached events according to the event priority using the online transmission protocol.

[0075] Understandably, when multiple types of transport protocols are logged in simultaneously, if any type of transport protocol is based on a subscription model, the subscribed events will be pushed according to the subscription information; if it is not based on a subscription model, all cached events will be pushed directly.

[0076] S206: In response to reaching the delayed sleep duration, control the camera to go into sleep mode.

[0077] Specifically, once the camera reaches the timeout period, it is put into sleep mode to ensure that the camera can always maintain low power consumption and avoid working for a long time, so as to reduce the probability of missing events while ensuring low power consumption.

[0078] Please see Figure 5 , Figure 5 This is a schematic diagram of an application scenario for one embodiment of the low-power camera event push method of this application. After the event center detects any event that needs to wake up the camera, it performs deduplication and priority sorting on the events, unifies the events into a preset storage format and caches them in memory, calculates the delay sleep duration, and within the delay sleep duration, after any type of transmission protocol comes online, the push adapter converts the events in the preset storage format into a format that matches the transmission protocol, and then pushes the cached events to the corresponding protocol system, thereby reducing the probability of event omission while ensuring low camera power consumption.

[0079] Please see Figure 6 , Figure 6 This is a schematic diagram of an embodiment of the electronic device of this application. The electronic device 30 includes a memory 301 and a processor 302 coupled to each other. The memory 301 stores program data (not shown in the figure). The processor 302 calls the program data to implement the method in any of the above embodiments. For the description of the relevant content, please refer to the detailed description of the above method embodiments, which will not be repeated here.

[0080] Please see Figure 7 , Figure 7 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 40 stores program data 400. When the program data 400 is executed by a processor, it implements the method in any of the above embodiments. For a detailed description of the relevant content, please refer to the detailed description of the above method embodiments, which will not be repeated here.

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

[0082] 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.

[0083] 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.

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

Claims

1. A low-power camera event push method, characterized in that, include: In response to the camera being woken up, retrieve all unpushed events and cache at least a portion of the events based on the camera's remaining battery power and the event priority; The historical push duration for push events of different types of transmission protocols is obtained, and the delayed sleep duration is determined based on the remaining battery power of the camera and the historical push duration of all types of the transmission protocols. In response to any type of transmission protocol being launched on the camera and its corresponding platform during the aforementioned delay sleep duration, at least a portion of the cached events are pushed to the platform according to the priority of the events using the launched transmission protocol; In response to reaching the specified delay sleep duration, the camera is controlled to go into sleep mode.

2. The low-power camera event push method according to claim 1, characterized in that, The process of acquiring all unpushed events and caching at least a portion of the events based on the camera's remaining battery power and event priority includes: Retrieve all unpushed events and determine the priority of each event based on its type; Determine the remaining battery level range of the camera, obtain the target priority matching the battery level range, and cache the events matching the target priority in a preset memory space.

3. The low-power camera event push method according to claim 2, characterized in that, The step of caching events matching the target priority to a preset memory space includes: The event matching the target priority is acquired and deduplicated, and the deduplicated event is converted into a preset storage format; wherein, the preset storage format includes event information corresponding to the event and protocol information corresponding to the transmission protocol matching the event type; Cache events with a preset storage format to a preset memory space.

4. The low-power camera event push method according to claim 1, characterized in that, The camera wake-up conditions include at least one of the following: the camera detects an event of a preset type, and the sleep link between the camera and the platform receives a wake-up signal; wherein, after the camera wakes up, it switches from the sleep link to the main link between the camera and the platform.

5. The low-power camera event push method according to claim 1, characterized in that, The process of obtaining historical push durations for different types of transmission protocol push events, and determining the delayed sleep duration based on the camera's remaining battery power and the historical push durations for all types of transmission protocols, includes: Obtain the historical push duration for at least one push event for different types of transport protocols, and determine the reference push duration for the corresponding type of transport protocol based on all historical push durations for each type of transport protocol. Determine the battery range in which the camera's remaining battery power falls, and obtain the reference delay duration matching the battery range; The delay sleep duration is determined based on the reference delay duration matched by the power range and the reference push duration for each type of transmission protocol.

6. The low-power camera event push method according to claim 5, characterized in that, The determination of the delay sleep duration based on the reference delay duration matched by the power range and the reference push duration for each type of transmission protocol includes: The reference push duration for each type of transmission protocol is compared with the reference delay duration matching the power range to determine the candidate reference push duration that is smaller than the reference delay duration and has the largest value. The delay sleep duration is determined based on the reference delay duration and the candidate reference push duration.

7. The low-power camera event push method according to claim 6, characterized in that, The step of determining the delayed sleep duration based on the reference delay duration and the candidate reference push duration includes: Obtain a preset margin coefficient, and use the margin coefficient to adjust the candidate reference push duration to obtain a target reference push duration; wherein, the target reference push duration is greater than the candidate reference push duration, and the reference push duration is increased by adjusting the margin coefficient and then compared with the reference delay duration; The minimum value between the reference delay duration and the target reference push duration shall be used as the delay sleep duration.

8. The low-power camera event push method according to claim 1, characterized in that, The step of using an existing transport protocol to push at least a portion of the cached events to the platform according to event priority includes: In response to the fact that the online transmission protocol is subscription-based, the corresponding transmission protocol subscription events are determined, and the subscribed events are pushed to the platform according to the priority of the events using the corresponding transmission protocol. In response to the fact that the online transmission protocol is non-subscription based, all cached events are pushed to the platform according to the priority of the events using the online transmission protocol.

9. An electronic device, characterized in that, include: A memory and a processor are coupled to each other, wherein the memory stores program data, and the processor invokes the program data to perform the method as described in any one of claims 1-8.

10. A computer-readable storage medium storing program data thereon, characterized in that, When the program data is executed by the processor, it implements the method as described in any one of claims 1-8.

Images