Video lingering recording control method and device, chip, monitoring equipment, system and medium

Abstract

The application provides a loitering video recording control method, device, chip, monitoring equipment, system and medium. The method comprises the following steps: acquiring a recording number of loitering video recording by a monitoring equipment in a first time interval, wherein the monitoring equipment takes a loitering video once in the case that a person loiters in an image acquisition range of the monitoring equipment and a loitering duration reaches a set loitering duration; in the case that a set first condition is established, outputting a first reminder message corresponding to the first condition or modifying the loitering duration; wherein the first condition comprises that the recording number is greater than or equal to a set first number threshold, or the first condition comprises that the recording number is less than or equal to a set second number threshold. The application helps to avoid frequent / insufficient loitering video recording of the monitoring equipment, so as to improve the loitering perception effect of the monitoring equipment.

Description

Technical Field

[0001] This application relates to the field of surveillance technology, and in particular to a method, device, chip, surveillance equipment, system and medium for controlling lingering recording. Background Technology

[0002] Surveillance equipment can achieve its monitoring purpose through included cameras. For example, a door lock (or smart door lock) can include a doorbell (or smart peephole) that incorporates multimedia services, and this multimedia doorbell can include a camera. When someone lingers near the door (such as the doorway area), the camera can record a video of that lingering. This video can then be sent to the user for viewing, thus achieving the monitoring purpose and ensuring home security. Therefore, it is necessary to provide a method for controlling lingering video recording. Summary of the Invention

[0003] This application provides a method, apparatus, chip, monitoring equipment, system, and medium for controlling lingering recording, which helps to avoid monitoring equipment from frequently or infrequently recording lingering footage, thereby improving the lingering perception effect of the monitoring equipment.

[0004] In a first aspect, embodiments of this application provide a method for controlling loitering recording, comprising: acquiring the number of times a monitoring device records a loitering recording within a first time interval, wherein the monitoring device records a loitering recording once when a person loites within the image acquisition range of the monitoring device and the duration of the loitering reaches a set loitering duration; and outputting a first reminder message corresponding to the first condition or modifying the loitering duration when a set first condition is met; wherein the first condition includes the number of recordings being greater than or equal to a set first number threshold, or the first condition includes the number of recordings being less than or equal to a set second number threshold.

[0005] In scenarios with frequent dwell times, users have relatively low sensitivity to dwell time. However, inappropriate dwell time settings can lead to frequent recording of dwell time, resulting in frequent recording pushes and rapid power loss of monitoring equipment (such as door locks), negatively impacting user experience. This application's embodiment determines whether a condition for modifying the dwell time is met based on the frequency of dwell time recording. If met, the dwell time can be modified or the user can be reminded to modify it, thereby avoiding frequent recording and improving the dwell time perception effect of the monitoring equipment. This avoids frequent recording pushes and rapid power loss of monitoring equipment in scenarios with frequent dwell times, resulting in a better user experience.

[0006] In scenarios with insufficient dwell time, users are relatively sensitive to dwell time fluctuations. However, inappropriate dwell time settings can lead to insufficient recording of dwell time footage, causing monitoring devices to become insensitive to dwell time fluctuations and push too few recordings, resulting in poor user security and a bad user experience. This application's embodiment determines whether the conditions for modifying the dwell time to address insufficient recording of dwell time footage are met based on whether insufficient dwell time recording occurs. If met, the dwell time can be modified or the user can be reminded to modify the dwell time, thereby avoiding insufficient recording of dwell time footage and improving the dwell time perception effect of the monitoring device. This improves the monitoring device's sensitivity to dwell time fluctuations and user security in scenarios with insufficient dwell time fluctuations, resulting in a better user experience.

[0007] Automatically adjusting the dwell time allows for optimization without user intervention, preventing monitoring devices from pushing too many or too few dwell time recordings. By reminding users to adjust the dwell time, users can increase, decrease, or leave it unchanged as needed, thus meeting their specific requirements.

[0008] Optionally, the stay recording control method further includes: when the set second condition is met, outputting a second reminder message corresponding to the second condition or modifying the current stay duration; wherein, one of the first and second conditions includes the number of records being greater than or equal to the first number threshold, and the other of the first and second conditions includes the number of records being less than or equal to the second number threshold, and the first number threshold being greater than the second number threshold.

[0009] By setting separate conditions for modifying the dwell time trigger to address both frequent and infrequent recording scenarios, we can avoid both excessive pushes of dwell time recordings and rapid power loss of monitoring equipment in scenarios with frequent dwell times. This also improves the sensitivity of monitoring equipment to dwell times and enhances user security in scenarios with infrequent dwell times. Furthermore, it can prevent the monitoring equipment from pushing too many or too few dwell time recordings due to inappropriate changes in dwell time or a mismatch between the modified dwell time and changes in the scenario.

[0010] Optionally, a first reminder message is output if the first condition is met; if the first condition includes that the number of records is greater than or equal to the threshold for the first time, the first condition also includes that the first time interval is not within the prohibited reminder time interval.

[0011] To avoid frequently reminding users to modify their stay duration in scenarios with frequent stays, which would negatively impact user experience, the trigger conditions for modifying the stay duration in cases of frequent stay recording include not only the monitoring device frequently pushing stay recordings, but also that the current time period must meet the reminder interval requirement. No stay duration modification reminders will be made during time periods that do not meet the reminder interval requirement.

[0012] Optionally, the time interval for prohibiting reminders is obtained based on the operation of increasing, decreasing, or maintaining the dwell time. By determining the time interval for prohibiting reminders based on whether and how the user modifies the dwell time, the frequency of reminders for users in frequent dwell scenarios can meet the user's personalized needs, avoiding frequent or untimely reminders that would negatively impact the user experience.

[0013] Optionally, the lingering recording control method further includes: if, after the first reminder message is output on the monitoring device, there is an operation that does not match the first reminder message, then the first time interval is determined to be within the prohibited reminder time interval.

[0014] If, after reminding a user in a scenario involving frequent stays, the user performs an action that is opposite to or inconsistent with the initial reminder, it can be assumed that the user is not sensitive to the frequent push notifications of stay recordings and the rapid power loss of the monitoring equipment, but rather focuses more on the security of the monitoring. Therefore, it is not necessary to remind the user again, which can meet the user's personalized needs and provide a better user experience.

[0015] Optionally, a first reminder message is output when the first condition is met; if the first condition includes that the number of records is less than or equal to the second threshold, the first condition also includes that the number of times the monitoring device takes a stay video in the second time interval is less than the third threshold; wherein, the second time interval includes the first time interval and the time interval before the first time interval, and the third threshold is greater than the second threshold.

[0016] To avoid accidentally disturbing users by sending unnecessary reminders to modify the stay duration in scenarios where the stay is too short, the trigger conditions for modifying the stay duration in cases of insufficient stay recording include not only the current number of stay recordings that are too short, but also the number of stay recordings that are too short over a longer period of time. If the conditions are not met, no reminder to modify the stay duration will be sent.

[0017] Optionally, the second threshold is obtained based on the number of lingering videos viewed within the second time interval.

[0018] Based on the different levels of attention paid to lingering by different users, a second threshold can be obtained by combining the user's viewing history of lingering recordings over a previous period. Based on this, it is possible to more effectively judge whether the monitoring device is pushing too few lingering recordings to meet the user's needs.

[0019] Secondly, embodiments of this application provide a loitering recording control device, comprising: an acquisition module, configured to acquire the number of times a monitoring device records a loitering video within a first time interval, wherein the monitoring device records a loitering video once when a person loites within the image acquisition range of the monitoring device and the duration of the loitering reaches a set loitering duration; and a processing module, configured to output a first reminder message corresponding to the first condition or modify the loitering duration when a set first condition is met; wherein the first condition includes the number of records being greater than or equal to a set first number threshold, or the first condition includes the number of records being less than or equal to a set second number threshold.

[0020] Thirdly, embodiments of this application provide an electronic chip, including: a processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to perform the method as described in any of the first aspects.

[0021] Fourthly, embodiments of this application provide a monitoring device, including: an image acquisition module for capturing loitering videos, and a loitering video control device as described in the second aspect or an electronic chip as described in the third aspect.

[0022] Fifthly, embodiments of this application provide a monitoring device, which includes one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by one or more processors, the monitoring device is triggered to execute the method as described in any of the first aspects.

[0023] In a sixth aspect, embodiments of this application provide a loitering video recording control system, including: a user terminal and a monitoring device as described in the fourth or fifth aspect; the monitoring device is configured to output a first reminder message corresponding to the first condition to the user terminal when the first condition is met; the user terminal is configured to display the first reminder message.

[0024] If the monitoring equipment frequently records recordings of the stay in scenarios with frequent stays, or if it records too few recordings in scenarios with infrequent stays, it can remind the user that the current frequency of recordings is too high or too low. This allows the user to adjust the stay duration to address the issue of frequent or infrequent recordings. Furthermore, the user can increase, decrease, or leave the stay duration unchanged as needed to meet their specific requirements.

[0025] Optionally, the user terminal is configured to display a configuration page when a triggering operation on the first reminder message is detected, the configuration page including controls for configuring the stay duration; and to modify the stay duration via the controls when an operation for modifying the stay duration is detected.

[0026] If a user needs to modify their dwell time after being reminded, the user's terminal can display a configuration page triggered by the user's response to the reminder message, allowing the user to quickly modify the dwell time as needed, thus providing a better user experience.

[0027] Optionally, the user terminal is used to update the modified stay duration to the monitoring equipment.

[0028] After the user modifies the stay duration as needed, the user terminal can also update the modified stay duration to the monitoring equipment, so that the monitoring equipment can record stay videos on demand according to the user's real-time stay duration requirements. This ensures that the number of stay video pushes meets the user's current needs.

[0029] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method as described in any of the first aspects.

[0030] Eighthly, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method as described in any of the first aspects.

[0031] The technical effects of the aforementioned aspects can be referenced from each other, and will not be elaborated further here. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below.

[0033] Figure 1 This is a schematic diagram of the structure of a monitoring device provided in an embodiment of this application;

[0034] Figure 2 A schematic diagram illustrating motion detection using a PIR sensor provided in an embodiment of this application;

[0035] Figure 3 This is a schematic diagram illustrating the interaction between the monitoring device provided in this application embodiment and the user's terminal device;

[0036] Figure 4 A flowchart illustrating a method for controlling lingering recording provided in an embodiment of this application;

[0037] Figure 5 A schematic diagram of a cat's eye stay configuration page provided in an embodiment of this application;

[0038] Figure 6 This is a flowchart illustrating another method for controlling lingering recording provided in an embodiment of this application. Detailed Implementation

[0039] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0040] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0041] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0042] It should be understood that the term "at least one" as used in this document refers to one or more, and "more than one" refers to two or more. The term "and / or" as used in this document 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 alone, A and B simultaneously, and B alone. A and B can be singular or plural. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0043] It should be understood that although the terms "first," "second," etc., may be used to describe the set thresholds in the embodiments of this application, these set thresholds should not be limited to these terms. These terms are only used to distinguish the set thresholds from each other. For example, without departing from the scope of the embodiments of this application, the first set threshold may also be referred to as the second set threshold, and similarly, the second set threshold may also be referred to as the first set threshold.

[0044] The loitering recording control method provided in any embodiment of this application can be applied to... Figure 1 The monitoring device 100 shown. Figure 1 A schematic diagram of the monitoring device 100 is shown.

[0045] The monitoring device 100 may include a processor 110, internal memory 121, power management module 141, battery 142, antenna 2, wireless communication module 160, audio module 170, speaker 170A, microphone 170C, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, etc. The sensor module 180 may include a fingerprint sensor, touch sensor, etc.

[0046] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the monitoring device 100. In other embodiments of this application, the monitoring device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0047] For example, if the monitoring device is a door lock, the door lock can include, in addition to, Figure 1 The components shown may include some or all of the door lock body. For example, if the monitoring device 100 is not a door lock, it may not include... Figure 1 The components shown include button 190 and display screen 194.

[0048] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0049] In some embodiments, the processor 110 may be a system-on-chip (SoC), which may include a central processing unit (CPU), and may further include other types of processors. In some embodiments, the processor 110 may be a PWM control chip.

[0050] The processor 110 may also include necessary hardware accelerators or logic processing hardware circuitry, such as an ASIC, or one or more integrated circuits for controlling the execution of the program. Furthermore, the processor 110 may have the capability to operate one or more software programs, which may be stored in a storage medium.

[0051] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0052] In some embodiments, the memory of the monitoring device 100 may be a read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), or other types of dynamic storage devices capable of storing information and instructions. It may also be an electrically erasable programmable read-only memory (EEPROM), or any computer-readable medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer.

[0053] In some embodiments, the processor 110 and the memory can be combined into a single processing device, or they can be separate components. The processor 110 can be used to execute program code stored in the memory. In specific implementations, the memory can be integrated into the processor 110, or it can be independent of the processor 110.

[0054] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0055] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the monitoring device 100. In other embodiments of this application, the monitoring device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0056] The power management module 141 is used to connect the battery 142 and the processor 110 to supply power to the processor 110.

[0057] The wireless communication function of the monitoring device 100 can be implemented through the antenna 2, the wireless communication module 160, the modem processor, and the baseband processor. The monitoring device 100 can use its wireless communication function to push captured recordings of the activity to the user's terminal device and to output reminder messages to the user's terminal device.

[0058] Antenna 2 is used to transmit and receive electromagnetic wave signals. Each antenna in the monitoring device 100 can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0059] The modem processor may include a modulator and a demodulator. The modulator modulates a low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to speaker 170A, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a separate device.

[0060] The wireless communication module 160 can provide solutions for wireless communication applications on the monitoring device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0061] In some embodiments, the antenna 2 and the wireless communication module 160 are coupled, enabling the monitoring device 100 to communicate with the network and other devices via wireless communication technology.

[0062] The monitoring device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0063] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the monitoring device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0064] The monitoring device 100 can perform its shooting function through an ISP, camera 193, video codec, GPU, display screen 194, and application processor. Based on the images captured by the camera 193, the monitoring device 100 can process the images to detect the duration of loitering and push the recorded loitering footage to the user's terminal device. When the monitoring device 100 is used as a door lock, it can display the outside view on the display screen 194, allowing users to check the loitering status of people outside the door, thus meeting the user's security monitoring needs.

[0065] The ISP is used to process data fed back by camera 193. Camera 193 is used to capture still images or videos. An object passes through the lens to generate an optical image that is projected onto the photosensitive element.

[0066] Video codecs are used to compress or decompress digital video. Monitoring device 100 may support one or more video codecs. Thus, monitoring device 100 can play or record video in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0067] Internal memory 121 can be used to store executable program code, including instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the monitoring device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of the monitoring device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located within the processor.

[0068] The monitoring device 100 can implement audio functions through an audio module 170, a speaker 170A, a microphone 170C, and an application processor to support the implementation of the intercom function of the monitoring device 100.

[0069] A fingerprint sensor is used to collect fingerprints. The monitoring device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, etc.

[0070] A touch sensor, also known as a "touch device," can be located on the display screen 194. The touch sensor and the display screen 194 together form a touchscreen, also called a "touchscreen." The touch sensor detects touch operations applied to or near it. The touch sensor can then transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In some embodiments, the touch sensor may also be located on the surface of the monitoring device 100, in a different position than the display screen 194.

[0071] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Motor 191 can generate vibration feedback. Motor 191 can be used for tactile vibration feedback. Indicator 192 can be an indicator light, used to indicate changes in battery level, etc.

[0072] The software system of the monitoring equipment 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture.

[0073] Monitoring devices can achieve their monitoring objectives through included cameras. For example, a door lock (or smart door lock) monitoring device may include a doorbell (or smart peephole) that involves multimedia services, and this doorbell may include a camera. The following description uses a door lock as an example to illustrate the technical implementation of this application. The relevant technical descriptions are also applicable to non-door lock monitoring devices, and the embodiments of this application will not be repeated here.

[0074] Door locks can be powered by batteries (such as lithium batteries / dry cell batteries).

[0075] The video function of a smart doorbell allows users to view the situation outside the door at any time as needed. However, due to factors such as limited user attention and limited power consumption of the door lock, it is not possible to achieve 24-hour monitoring. In monitoring scenarios, users are usually only interested in abnormal situations (mainly people lingering outside the door). Therefore, the door lock can record a video of people lingering outside the door (such as the doorway area that can usually be captured by a camera).

[0076] When someone passes by or lingers outside the door, the motion detection function of the smart peephole is triggered. The camera on the smart peephole can then record video of the lingering person, capturing the image. This video can be sent to the user for review, thus achieving the purpose of monitoring and ensuring home security. For example, by reviewing the video, the user can see if a stranger is loitering or lingering at the door.

[0077] There are many types of motion detection technologies, and these technologies are constantly evolving. PIR (Passive Infrared) sensors are widely used in the surveillance field due to their non-radiation, good concealment, low power consumption, and ability to detect motion.

[0078] PIR sensors operate on the principle of pyroelectric infrared sensing, detecting the temperature difference between moving objects (such as people or animals) and background objects. They detect the infrared radiation emitted by the moving object and convert it into an electrical signal. For example, the human body, typically at 36-37 degrees Celsius, emits infrared radiation of a specific wavelength of about 10µm. When a warm object (such as a human) passes through the first detector window in front of the PIR detector, a positive pulse is generated; when the object passes through the second detector window, a negative pulse is generated. This indicates that a warm object is detected moving nearby. The signal indicating the presence of a moving warm object can be generated using a relatively simple analog electronic device with a pair of operational amplifiers.

[0079] In one related technology 1, the door lock can use a PIR sensor to detect motion and use a camera to record a video of a person lingering when a warm object (such as a person) is detected passing by the door, thereby achieving the purpose of monitoring.

[0080] Please refer to Figure 2 The PIR sensor used in the door lock can be a dual infrared sensor 202, and the infrared light emitted by the dual infrared sensor 202 is emitted through the Fresnel lens 203. Figure 2 The arrow shown indicates the direction of movement in which the dual-element infrared sensor 202 is most sensitive to detection. If user 201 moves along... Figure 2 Moving in the direction indicated by the arrow will allow the dual-element infrared sensor 202 to detect the passing of a moving object. When the dual-element infrared sensor 202 detects the passing of a moving object, the door lock can record a video of the object's presence via a camera.

[0081] Please refer to Figure 3 The door lock may include a camera 301, a display screen 302, and a door handle 303, as shown. When someone presses the doorbell, the doorbell rings, the camera 301 captures an image of the outside, and the display screen 302 displays the image captured by the camera 301, allowing the user to view the situation outside the door. When the door lock's PIR sensor detects someone passing by the door, the camera 301 captures an image of the outside to record a video of the person's presence. The door lock can then send the video recording captured by the camera 301 to the user's mobile terminal 304, allowing the user to view the received video recording as needed through the corresponding door lock app installed on the mobile terminal 304.

[0082] However, the working principle of PIR technology means that PIR sensors have inherent defects, such as low sensitivity and great susceptibility to temperature. Therefore, when PIR sensors are used in the scenario of recording the stay of a door lock, problems such as insensitive stay and false stay recognition (for abnormal scenarios) will occur, resulting in poor stay perception and affecting the user experience.

[0083] For example, in scenarios with frequent lingering, people often pass quickly through the doorway. In such cases, the PIR sensor can frequently detect people passing by, and the door lock will typically record lingering videos frequently. However, in these scenarios, people outside usually pass quickly rather than lingering at the door as the user might expect. Therefore, the door lock, based on the PIR sensor, may experience problems with its insensitivity to lingering, leading to frequent recordings and push of lingering videos, resulting in poor lingering detection.

[0084] The frequent stay scenarios can be further divided into frequent stay normal scenarios and frequent stay abnormal scenarios. Frequent stay normal scenarios include scenarios such as store entrances, first-floor user entrances, and elevator entrances, while frequent stay abnormal scenarios include scenarios such as neighbors moving / renovating / getting married.

[0085] For example, in an abnormal scenario, some door curtains are warm in summer, and external forces (such as wind) can cause them to sway back and forth. In this case, the PIR sensor can frequently detect warm objects passing by the door, and the door lock will usually take frequent recordings of such lingering objects. However, in this abnormal scenario, there is no situation where someone is lingering at the door for an extended period, which is of interest to the user. Therefore, there is a problem of false lingering identification in this abnormal scenario.

[0086] Furthermore, when the door lock is battery powered, the smart peephole, which involves multimedia functions, has a significant impact on battery consumption. For example, the average power consumption of a smart peephole can account for about 60% of the overall power consumption of the door lock, while lingering recording, as an important function of the smart peephole, can account for about 70% of its overall power consumption. Because the lingering recording function has a significant impact on the door lock's power consumption, frequent use of this function will result in high power consumption and rapid battery depletion. If left unchecked, this could lead to a rapid battery drain, rendering the door unusable and resulting in a poor user experience.

[0087] To improve the lingering detection effect of door locks and avoid excessive power consumption caused by frequent lingering recording, a related technology 2 allows setting a fixed lingering duration (e.g., 9 seconds). The specific value of the lingering duration can be determined by combining the device's factory settings and user configuration. Taking a lingering duration of 9 seconds as an example, when the door lock detects someone passing by the door, it can check whether someone has been lingering at the door for 9 seconds. If so, it will record a lingering video for a certain duration and push the recorded video to the user's mobile phone so that the user can view the lingering video as needed.

[0088] However, a fixed dwell time is not suitable for specific scenarios with frequent or infrequent dwell times. Furthermore, the environment in which the door lock is located can change (e.g., neighbor renovations), making the fixed dwell time inapplicable to changed scenarios. Additionally, users typically don't modify the system's default dwell time setting, and may not even be aware of changes in the door lock's environment. This makes the door lock prone to frequently triggering dwell time recording while missing some recordings. Frequent dwell time recording not only negatively impacts user experience due to excessive push notifications, but also causes the door lock's battery to drain quickly. Missed dwell time recordings reduce the door lock's sensitivity to people's presence, which is detrimental to user security.

[0089] For example, frequent loitering scenarios can include normal scenarios such as store entrances, first-floor user entrances, and elevator entrances, as well as abnormal scenarios such as neighbors moving, renovating, or getting married. Fixed loitering durations are not suitable for these frequent loitering scenarios, which can lead to door locks frequently pushing loitering videos to users and the door locks draining the battery quickly due to frequent loitering video recording.

[0090] Scenarios with very few stays may include single-elevator single-family, detached buildings, and top-floor units. However, fixed stay durations are not always applicable to these scenarios, which may lead to the door lock missing some stay recordings, resulting in insufficient security awareness.

[0091] like Figure 4 As shown in the figure, this application provides a method for controlling lingering recording, which may include steps 401 to 402. This method can solve the problem of door locks frequently / rarely implementing lingering recording function under two extreme abnormal lingering scenarios: abnormally frequent lingering and extremely infrequent lingering.

[0092] In one embodiment, the method can be executed by a door lock. In another embodiment, the method can also be executed by a user-used terminal device.

[0093] In one embodiment, Figure 4 The illustrated embodiment can be applied to the field of security monitoring with camera surveillance.

[0094] Step 401: Obtain the number of times the door lock records the stay video within the first time interval. Specifically, a stay video is recorded when someone stays within the door lock's image acquisition range and the stay duration reaches the set stay duration.

[0095] The first time interval can be a period of time preceding the current moment.

[0096] In one embodiment, the number of times a stay video is recorded within a period of time before the current moment can be obtained periodically. For example, the number of records can be obtained every day. In this case, the first time interval can be 24 hours of the current day, or a certain moment of the previous day to the same moment of the current day.

[0097] In one embodiment, the image acquisition area of ​​the door lock can be the image acquisition area of ​​a camera included in the door lock for capturing lingering video, and the image acquisition area can include a monitoring area of ​​interest to the user outside the door.

[0098] In one embodiment, when the door lock detects someone passing by using motion detection technology, it can detect whether someone is lingering within the door lock's image capture range and whether the duration of lingering reaches a preset lingering duration. If both are true, the door lock can record a lingering video using a camera. After each lingering video is recorded, the door lock can push the recorded lingering video to the user's terminal device in real time.

[0099] In one feasible implementation, the door lock can detect whether someone is passing by using a PIR sensor.

[0100] Considering that if someone lingers outside the door for an extended period and remains stationary or makes only slight movements, the PIR sensor may not detect their presence, and the door lock typically will not record any footage during this time. In this scenario, the door lock suffers from insensitive lingering detection, leading to missed detections and recordings, resulting in poor lingering detection performance. To address this issue, another feasible implementation involves the door lock periodically capturing images via a camera and performing human recognition on these images to determine the presence of someone.

[0101] In one feasible implementation, when the door lock detects someone passing by, it can use images captured by a camera to detect whether someone is lingering there continuously. In one embodiment, the continuous lingering of someone is not limited to the same person lingering there continuously.

[0102] In another feasible implementation, when the door lock detects someone passing by, it can use a PIR sensor to detect whether someone is continuously passing by.

[0103] In one embodiment, a page that allows users to set the duration of their stay can be as follows: Figure 5 As shown. Figure 5 The page shows a UX (User Experience) style for setting up peephole lingering recording. "Llingering Duration" indicates whether someone is lingering outside the door for more than a specified time (e.g., ...). Figure 5 The lingering recording will be triggered after 9 seconds (as shown). After the lingering recording is triggered, the door lock can record for a specified duration (e.g., 9 seconds). Figure 5 The 6-second video footage shown is used as a recording of the stay.

[0104] Please refer to Figure 5 If the "Stay Recording" control is enabled, the stay recording control process can be executed. If the "Stay Recording" control is disabled, the stay recording control process will not be executed. Users can enable or disable the stay recording function of the door lock as needed.

[0105] If the set stay duration does not match the scene where the door lock is located, there may be problems such as frequent take-up recordings or missed take-up recordings. Therefore, to solve this problem, we can first obtain the number of times the door lock takes stay recordings within the first time interval, so as to determine whether the stay duration does not match the scene where the door lock is located.

[0106] Step 402: If the set first condition is met, output the first reminder message corresponding to the first condition or modify the stay time; wherein, the first condition includes the number of records being greater than or equal to the set first number threshold, or the first condition includes the number of records being less than or equal to the set second number threshold.

[0107] In scenarios with frequent stays, users are relatively less sensitive to the duration of their stay. However, inappropriate stay duration settings can lead to frequent recordings of the stay, resulting in frequent push notifications for these recordings and rapid power loss from the door lock due to high power consumption, thus negatively impacting the user experience. To address this issue, the first condition could be modifying the stay duration trigger condition to handle frequent recordings, specifically including a record count exceeding a threshold (i.e., the number of stay recordings is too high). In other words, addressing frequent recordings could involve modifying part or all of the stay duration trigger condition.

[0108] For example, in one embodiment, the stay duration can be automatically modified as long as the number of records exceeds the threshold for the first record.

[0109] In another embodiment, for example, when the number of records exceeds the threshold for the first record and the current time meets the reminder time interval requirement, the first reminder message can be output.

[0110] In one embodiment, the first reminder message may be a message reminding the user to increase the dwell time to reduce the number of dwell time recordings pushed. In another embodiment, the first reminder message may be a message reminding the user that if the door lock is currently frequently recording dwell time videos, the user can modify the dwell time as needed. In yet another embodiment, the first reminder message may be a message reminding the user of the door lock's battery power consumption.

[0111] As can be seen, this application embodiment can determine whether the trigger condition for modifying the stay duration to cope with frequent stay recording is met based on whether the stay recording occurs frequently. If the condition is met, the stay duration can be modified or the user can be reminded to modify the stay duration. This aims to avoid frequent stay recording by modifying the stay duration, thereby improving the stay perception effect of the door lock. This can avoid the door lock frequently pushing stay recordings in frequent stay scenarios and avoid the door lock losing power quickly, thus providing a better user experience.

[0112] When the first condition is to modify the dwell time trigger condition to deal with frequent dwell time recording, by setting and modifying the dwell time as needed, frequent dwell time recording can be avoided, as well as the problem of dwell time misidentification in abnormal scenarios. Therefore, it can solve the problems of poor dwell time perception effect and fast battery drain of the door lock in the above-mentioned related technology 1, and can solve the problems of frequent push of dwell time recording and fast battery drain of the door lock in the above-mentioned related technology 2.

[0113] In scenarios with insufficient dwell time, users are relatively sensitive to dwell time, but inappropriate dwell time settings may result in insufficient dwell time recordings. This can lead to door locks becoming insensitive to dwell time and sending out too few dwell time recordings, resulting in poor user security and a bad user experience. To solve this problem, the first condition could be modifying the dwell time trigger condition to address insufficient dwell time recordings, and this first condition includes the number of recordings being less than a second threshold (i.e., the number of dwell time recordings is too low). In other words, addressing insufficient dwell time recordings can involve modifying part or all of the corresponding dwell time trigger condition.

[0114] For example, in one embodiment, the stay duration can be automatically modified as long as the number of records is less than the threshold for the second count.

[0115] In another embodiment, a second reminder message can be output when the number of recordings is less than the second threshold and the overall number of recordings taken over several consecutive days is relatively small.

[0116] In one embodiment, the second reminder message may be information reminding the user to reduce the duration of their stay to avoid missing recordings. In another embodiment, the second reminder message may be information reminding the user that if the door lock is not currently recording enough footage of their stay, they can adjust the duration as needed. In yet another embodiment, the second reminder message may be information reminding the user of the level of security.

[0117] As can be seen, this application embodiment can determine whether the trigger condition for modifying the stay duration to address the situation of insufficient stay recording is met based on whether insufficient stay recording occurs. If the condition is met, the stay duration can be modified or the user can be reminded to modify the stay duration. This aims to avoid insufficient stay recording by modifying the stay duration, thereby improving the door lock's stay perception effect. This can improve the door lock's sensitivity to stay and user security in scenarios with insufficient stay, thus resulting in a better user experience.

[0118] When the first condition is to modify the dwell time trigger condition to deal with insufficient dwell time recording, the problem of missed dwell time recording can be avoided by setting and modifying the dwell time as needed. Therefore, it can solve the problem of low dwell sensitivity and low user security of the door lock in the scenario of insufficient dwell time in the above-mentioned related technology 2.

[0119] Whether it's a scenario with frequent stays or a scenario with infrequent stays, as long as the first condition is met, it can be considered that the currently set stay duration does not match the current scenario of the door lock. Therefore, the stay duration can be automatically modified or the user can be reminded to modify the stay duration.

[0120] If the primary condition for automatically modifying the dwell time is to address frequent dwell time recording, then the dwell time can be increased by modifying the dwell time itself. Increasing the dwell time reduces the number of times the door lock records dwell time, avoids frequent push notifications of dwell time recordings, and reduces the door lock's power consumption.

[0121] If the primary condition for automatically adjusting the dwell time is to address insufficient dwell time recording, then the dwell time can be reduced by modifying the dwell time itself. Reducing the dwell time increases the number of times the door lock records dwell time, preventing missed recordings and ensuring user security.

[0122] By automatically adjusting the dwell time, the dwell time can be optimized without the user's awareness or intervention, thus avoiding excessive or insufficient push of dwell time recordings to the door lock.

[0123] All other things being equal, an increase in the duration of stay will result in a decrease in the number of times the stay video is recorded, resulting in less frequent video feeds and slower battery drain for the door lock, but it will also lead to a decrease in security. Conversely, an increase in the duration of stay will result in an increase in the number of times the stay video is recorded, which will increase security, but it will also lead to more frequent video feeds and faster battery drain for the door lock.

[0124] For security reasons, the dwell time can be set to remain unchanged rather than automatically adjusted; instead, users can be prompted to adjust it manually as needed. Furthermore, different users may have varying perceptions and needs regarding door lock power consumption and the frequency of dwell time recording notifications. By prompting users to adjust the dwell time instead of automatically adjusting it, the dwell time recording control can be tailored to individual user requirements.

[0125] When prompting users to modify the dwell time, if the primary condition is to trigger the modification of the dwell time to address frequent dwell time recordings, users can choose to increase, decrease, or not modify the dwell time as needed after being prompted. Increasing the dwell time can reduce the number of times the door lock records dwell time, avoid frequent push notifications of dwell time recordings, and reduce the door lock's power consumption.

[0126] When prompting users to modify their dwell time, if the primary condition for modifying the dwell time is to address insufficient dwell time recording, users can choose to increase, decrease, or not modify the dwell time as needed after being prompted. If the user reduces the dwell time, the door lock will record more dwell time footage, avoiding missed recordings and ensuring user security.

[0127] By reminding users to modify their stay duration, users can increase, decrease, or not modify their stay duration as needed, thus meeting their needs.

[0128] In one embodiment of this application, the stay recording control method may further include: when a set second condition is met, outputting a second reminder message corresponding to the second condition or modifying the current stay duration; wherein, one of the first and second conditions includes the number of records being greater than or equal to a first count threshold, and the other of the first and second conditions includes the number of records being less than or equal to a second count threshold, and the first count threshold being greater than the second count threshold.

[0129] By setting both the first and second conditions, the trigger conditions for modifying the stay duration include not only the condition for modifying the stay duration in response to frequent recording of stay videos, but also the condition for modifying the stay duration in response to infrequent recording of stay videos. This ensures that, regardless of whether the stay is frequent or infrequent, as long as either of the stay duration modification trigger conditions is met, the stay duration can be automatically modified or a modification reminder can be provided.

[0130] In situations where the scene surrounding the door lock undergoes a temporary change (such as a neighbor renovating their house), the temporary change may trigger a condition for modifying the dwell time, leading to a change in the dwell time. However, once the scene returns to normal after the temporary change, the modified dwell time may not match the restored scene. This could trigger another condition for modifying the dwell time, resulting in a further modification. Therefore, based on the complementary effect of these two dwell time modification trigger conditions, the user doesn't need to manually monitor when the temporary scene disappears and promptly revert the modified dwell time afterward. The dwell time setting can always adapt to the scene surrounding the door lock and any changes to that scene.

[0131] To achieve a complementary effect between the two conditions for modifying the dwell time trigger, the threshold for the first count can be set to be greater than the threshold for the second count. That is, the threshold for the first count is the upper limit of the number of times, and the threshold for the second count is the lower limit of the number of times. If the number of recorded times is greater than or equal to the upper limit, it can be considered that the door lock is currently recording dwell time videos frequently. If the number of recorded times is less than or equal to the lower limit, it can be considered that the door lock is currently recording dwell time videos too infrequently.

[0132] It is evident that by setting separate trigger conditions for modifying the dwell time to address both frequent dwell time recording and infrequent dwell time recording, we can not only avoid frequent push notifications of dwell time recordings and rapid power loss of the door lock in frequent dwell time scenarios, but also improve the door lock's sensitivity to dwell time and user security in scenarios with infrequent dwell time. Furthermore, we can prevent the door lock from pushing too many or too few dwell time recordings due to inappropriate changes in dwell time or changes in the dwell time not matching the scenario.

[0133] The following sections will explain the specific implementation of the stay recording control method, specifically addressing the modification of the stay duration trigger condition for the first condition (to address frequent recording of stay duration) or the modification of the stay duration trigger condition for the first condition (to address infrequent recording of stay duration).

[0134] In one embodiment of this application, when reminding users to modify their stay duration in scenarios with frequent stays, a first reminder message is output when a first condition is met; the first condition includes cases where the number of records is greater than or equal to the threshold of the first count, and the first condition also includes cases where the first time interval is not within the prohibited reminder time interval.

[0135] To avoid frequently reminding users to modify their stay duration in scenarios with frequent stays, which would negatively impact user experience, the trigger conditions for modifying the stay duration in cases of frequent stay recording include not only the door lock frequently pushing stay recordings, but also that the current time period must meet the reminder interval requirement. No stay duration modification reminders will be made during time periods that do not meet the reminder interval requirement.

[0136] Based on the varying perceptions of different users regarding the frequency of push notifications for recording sessions, the rate of battery drain on door locks, and the perceived level of security, after receiving a notification, users can modify or not modify the duration of the recording session (i.e., maintain the original duration), or increase or decrease it as needed. In this way, user actions can influence the time range for disabling notifications, ensuring that the disabling time range aligns with the user's personalized needs.

[0137] Thus, in one embodiment of this application, the time interval for prohibiting reminders is obtained based on operations that increase, decrease, or maintain the dwell time. In one feasible implementation, the user's operation to maintain the dwell time can be an operation where the user does not modify the dwell time (or no operation).

[0138] By determining the time range for prohibiting reminders based on whether and how the user modifies the stay duration, the frequency of reminders for users in frequent stay scenarios can meet the user's personalized needs, avoiding frequent or untimely reminders that would negatively impact the user experience.

[0139] In one feasible implementation, the number of reminders can be recorded, where the recorded number of reminders represents the number of times the first reminder message was output, and the time interval for prohibiting reminders is obtained based on the recorded number of reminders.

[0140] In one embodiment, the number of recorded reminders may be consistent with the number of times the first reminder message is actually output.

[0141] In another embodiment, the recorded number of reminders is affected not only by the actual number of times the first reminder message is output, but also by whether the user modifies the dwell time in response to the door lock reminder. Therefore, the recorded number of reminders may not be the same as the actual number of times the first reminder message is output. Thus, the recorded number of reminders can be obtained based on the operation of increasing, decreasing, or maintaining the dwell time; that is, the recorded number of reminders is affected by whether and how the user modifies the dwell time.

[0142] For example, if a user is reminded due to frequent push notifications of lingering video recordings, and the user increases their lingering time due to the door lock reminder, it can be assumed that the user accepts the frequent push notifications. In this case, the interval between prohibiting the next reminder can be relatively short.

[0143] For example, if a user is reminded after frequent push notifications of a dwell time recording, but the user does not change the dwell time due to the door lock reminder, it can be assumed that the user has no obvious awareness of the frequency of the push notifications. In this case, the interval between the next reminder and the prohibition of reminders can be relatively long.

[0144] For example, if a user is reminded after frequent push notifications of lingering recordings, but the user reduces the lingering time due to the door lock reminder, it can be assumed that the user is more concerned about monitoring security and less accepting of missed recordings, and is not concerned about the frequent push notifications of lingering recordings and the high power consumption of the door lock. In this case, no further reminders can be given (which is equivalent to making the interval between prohibiting reminders for the next reminder infinitely long).

[0145] Thus, in one embodiment of this application, a first reminder message is output when a first condition is met; the first condition includes: the number of records is greater than the first count threshold, and the first time interval is not within the prohibited reminder time interval corresponding to the number of recorded reminders; wherein, the number of recorded reminders represents the number of times the first reminder message is output.

[0146] In one embodiment, it can be directly determined whether the first time interval is within the prohibited reminder time interval. In another embodiment, it can be determined whether the first time interval is within the prohibited reminder time interval by judging whether the current time is within the prohibited reminder time interval. If the current time is within the prohibited reminder time interval, the first time interval can be considered to be within the prohibited reminder time interval; if the current time is not within the prohibited reminder time interval, the first time interval can be considered not to be within the prohibited reminder time interval.

[0147] In one embodiment of this application, after outputting the first reminder message, the recorded reminder count can be incremented by one. If the user increases their stay time after outputting the first reminder message, the recorded reminder count can be reset to zero; if the user decreases their stay time after outputting the first reminder message, the recorded reminder count can be set to specific information indicating that no further reminders will be given.

[0148] In one embodiment, if the user increases their stay time after the door lock outputs the first reminder message, the recorded reminder count can be reset to zero in real time after the user increases their stay time. If the first condition is met again after resetting, the first reminder message can be output again, and the recorded reminder count can be incremented by one (i.e., the recorded reminder count is now 1). By resetting the recorded reminder count in real time based on the user's increased stay time, the timely execution of the next reminder can be achieved.

[0149] In another embodiment, after determining that the first condition is met, the current dwell time can be compared with the dwell time when the first reminder message was last output (i.e., it can be determined whether and how the user modified the dwell time between the current reminder and the previous reminder), and the recorded number of reminders can be updated based on the comparison result.

[0150] If the comparison result indicates that the current dwell time is the same as the dwell time when the first reminder message was output, meaning the user did not modify the dwell time, then the recorded reminder count can be incremented by one.

[0151] If the comparison result indicates that the current dwell time is greater than the dwell time when the first reminder message was last output, meaning the user has increased their dwell time, then the recorded reminder count can be updated to one (equivalent to resetting to zero and then adding one).

[0152] If the comparison result indicates that the current dwell time is less than the dwell time when the first reminder message was output, meaning the user has reduced the dwell time, then the recorded reminder count can be updated with specific information indicating that no further reminders will be sent.

[0153] In one embodiment of this application, the first condition further includes the following for cases where the user increases or does not modify the dwell time after the reminder: if the first reminder message has been output, the dwell time at the time the first reminder message was output is not greater than the current dwell time (i.e., the user increases or does not modify the dwell time after the last reminder).

[0154] Based on this, the lingering recording control method further includes: if the lingering duration when the first reminder message was last output is equal to the current lingering duration (i.e., the user did not modify the lingering duration after the last reminder), the recorded reminder count will be incremented by one after the current reminder message is output (i.e., the reminder count will be incremented by one); if the lingering duration when the first reminder message was last output is less than the current lingering duration (i.e., the user increased the lingering duration after the last reminder), the recorded reminder count will be modified to one after the current reminder message is output (i.e., the reminder count will be reset to zero and then incremented by one).

[0155] If the user increased / did not modify their dwell time after the last reminder, but dwell time recordings are still frequently pushed during the first time period, then a second reminder is required. Conversely, if the user decreased their dwell time after the last reminder, even if dwell time recordings are still frequently pushed during the first time period, a second reminder is not necessary.

[0156] In one embodiment, if no first reminder information has been output, that is, if the current reminder is the first reminder (equivalent to the recorded number of reminders being zero), then the first time interval is not within the prohibited reminder time interval corresponding to the recorded number of reminders (for example, the duration of the corresponding prohibited reminder time interval can be 0). After the first reminder, the recorded number of reminders can be modified to one.

[0157] By combining the number of reminders already completed with the specific actions the user takes based on the reminder messages—whether to modify them and how to change the dwell time—the time interval for which no reminders are given can be determined. This ensures that the length of the time interval is related not only to the number of reminders but also to the user's need for reminders. This allows for accurate determination of the time interval, enabling reminder intervals that better meet user needs and avoiding unnecessary frequent or untimely reminders that negatively impact the user experience.

[0158] In one embodiment of this application, for cases where the user reduces the dwell time after being reminded, the dwell recording control method further includes: if there is an operation that does not match the first reminder message after the first reminder message is output on the door lock, then the first time interval is determined to be within the prohibited reminder time interval.

[0159] If, after reminding a user in a scenario involving frequent lingering, the user performs an action that is opposite to or inconsistent with the initial reminder, it can be assumed that the user is not sensitive to the frequent push notifications of lingering recordings and the rapid power loss of the door lock, but rather focuses more on the security of the monitoring. Therefore, it is not necessary to remind the user again, which can meet the user's personalized needs and provide a better user experience.

[0160] In one embodiment of this application, the first condition is not met if a first reminder message has already been output and the dwell time at the time the first reminder message was last output was greater than the current dwell time (i.e., the user reduced the dwell time after the last reminder). Based on this, the dwell recording control method further includes: if the dwell time at the time the first reminder message was last output was greater than the current dwell time, modifying the recorded reminder count to target information; wherein, when the recorded reminder count is target information, the first time interval is within the prohibited reminder time interval corresponding to the recorded reminder count.

[0161] If the user reduced their dwell time after the last reminder, even if dwell time recordings are still frequently pushed during the first time period, the trigger condition for modifying the dwell time will not be met, and there is no need to remind them again.

[0162] In scenarios involving frequent stays, shorter stay durations can lead to frequent recording of the stay video. In such cases, users can be prompted to adjust their stay duration to potentially address the issues of frequent video recording notifications and rapid power loss from the door lock caused by longer stay durations. However, if users reduce their stay duration based on the prompt, this would exacerbate the problem of frequent video recording notifications and rapid power loss from the door lock. In this case, it can be assumed that users are not sensitive to this issue and therefore no further prompts are needed. In such situations, subsequent prompts can be discontinued to align with users' actual needs.

[0163] Considering that the greater the number of recorded reminders, the longer the time interval between the user's last increased dwell time, meaning the user did not modify the dwell time more often during that period, and thus the user was more unaware of the frequent push notifications, the corresponding time interval for prohibiting reminders can be larger.

[0164] For example, if the recorded number of reminders is 0 / 1 / 2 / 3 (meaning the current reminder to be executed is the 1st / 2nd / 3rd / 4th reminder), then the corresponding reminder-disabled time ranges can be 0 days / 7 days / 30 days / 90 days respectively. This allows for reminders that meet user needs and avoids excessively frequent reminders that could negatively impact user experience.

[0165] Thus, in one embodiment of this application, the number of recorded reminders and the duration of the time interval during which reminders are prohibited are positively correlated.

[0166] By establishing a positive correlation between the number of recorded reminders and the duration of the corresponding time interval during which no reminders are given, the time interval can be accurately determined, thus avoiding negative impacts on user experience due to frequent reminders.

[0167] Please refer to Figure 6 One embodiment of this application provides a method for controlling the recording of a stay, which may include the following steps 601 to 606. This method is applied to a door lock with a camera.

[0168] Step 601: Read the number of reminders recorded in the flash memory. Flash memory is a type of non-volatile memory.

[0169] In one embodiment, the door lock can read the number of reminders recorded in the flash memory after power-on and temporarily store the read reminder count in memory. While the door lock is powered on, if the recorded reminder count is updated, both the flash memory and the temporarily stored reminder count can be updated simultaneously, ensuring consistency between the two. The temporarily stored reminder count is then used during power-on to determine whether the trigger condition for modifying the dwell time is met. By initially reading the reminder count recorded in the flash memory after power-on and then using the temporarily stored reminder count during power-on, the flash memory's erase / write lifespan can be improved.

[0170] Step 602: Record a sojourn video when the sojourn conditions are met. The sojourn conditions include that someone is sojourning within the image capture range of the door lock and the duration of sojourn reaches the set sojourn duration.

[0171] Once the conditions for triggering a stay are detected, a stay video can be recorded. Multiple stay videos can be recorded within a certain period, such as within a day. The number of stay videos recorded within a certain period is consistent with the number of times the conditions for triggering a stay are detected within that period.

[0172] Step 603: Determine whether the number of times the stay video is recorded within the day meets the upper limit corresponding to the working mode of the door lock. If yes, proceed to step 604; otherwise, proceed to step 602.

[0173] If the number of records meets the upper limit, it can be further determined whether the reminder time interval requirement is met at the current moment.

[0174] If the number of recordings does not meet the upper limit, meaning there are no frequent pushes of loitering videos on that day, step 602 can be executed to perform on-demand shooting of loitering videos for the next day.

[0175] In one embodiment, different operating modes can be set for the door lock, with different maximum number of recordings per day for each mode. For example, the door lock's operating modes may include an extreme mode and an energy-saving mode. In one feasible implementation, the maximum number of recordings per day for the extreme mode is ≥80, and the maximum number of recordings per day for the energy-saving mode is ≥40.

[0176] like Figure 5 As shown, the door lock's operating mode can be set to energy-saving mode.

[0177] Step 604: Determine whether the current time meets the reminder time interval requirements. If yes, proceed to step 605; otherwise, proceed to step 602. The reminder time interval requirements include: if no reminder information has been output, the current time meets the reminder time interval requirements; if the number of recorded reminders is 1 (i.e., the next reminder is the 2nd recorded reminder), the current time is more than 7 days since the last reminder; if the number of recorded reminders is 2 (i.e., the next reminder is the 3rd recorded reminder), the current time is more than 30 days since the last reminder; if the number of recorded reminders is 3 (i.e., the next reminder is the 4th recorded reminder), the current time is more than 90 days since the last reminder.

[0178] After determining that the daily recording limit has been met, the system can determine whether the daily reminder interval requirement is met by checking if the current moment meets the requirement. If the current moment meets the requirement, then the reminder interval requirement is met for the day, and the user will be reminded if the daily recording limit is exceeded. If the current moment does not meet the requirement, then the reminder interval requirement is not met for the day, and the user will not be reminded even if the daily recording limit is exceeded. This avoids reminding the user again within the corresponding prohibited reminder time interval after the last reminder.

[0179] By increasing the reminder interval as the number of recorded reminders increases, the problem of frequent reminders that repeatedly disturb the user can be avoided.

[0180] Step 605: Compare the current dwell time with the dwell time at the time of the last reminder (i.e., determine whether the user has modified the dwell time between the last reminder and the current time). If yes, output a reminder message to the user's terminal device, increment the recorded reminder count by one, and synchronously update the recorded reminder count in the flash memory. Then execute step 602. Otherwise, execute step 606.

[0181] In one embodiment, the output reminder message may be a message reminding the user to linger outside the door frequently.

[0182] In one embodiment, the system can determine whether the user modified the dwell time between the last reminder and the current time by comparing the current dwell time configuration with a snapshot of the dwell time configuration at the time of the last reminder. If no modification was made, it indicates that the user is not sensitive to frequent push notifications, so the recorded reminder count can be incremented by one to avoid reminding the user again in a short period of time.

[0183] Figure 6 In this embodiment, after determining that the video recording of the stay is frequently pushed on the same day, it can be determined whether the current time meets the reminder time interval requirement. If the reminder time interval requirement is met, the current stay duration can be further compared with the stay duration at the time of the last reminder to see if they are consistent.

[0184] In another embodiment, the corresponding interval time range can be determined first based on the number of recorded reminders, and it can be determined whether the stay video is frequently pushed on the same day outside the interval time range. If so, the current stay time can be further compared with the stay time at the last reminder to see if they are consistent.

[0185] Step 606: Determine whether the current dwell time is less than the dwell time at the last reminder (i.e., determine how the user modified the dwell time between the last reminder and the current time). If yes, set the recorded reminder count to indicate no more reminders and update the recorded reminder count in the flash memory synchronously. Otherwise, output a reminder message to the user's terminal device, set the recorded reminder count to 1 (i.e., treat this reminder as the first reminder), and update the recorded reminder count in the flash memory synchronously. Then, proceed to step 602.

[0186] Determining whether the current dwell time is less than the dwell time at the time of the last alert is equivalent to determining whether the current dwell sensitivity is greater than the dwell sensitivity at the time of the last alert. The shorter the dwell time, the higher the door lock's dwell sensitivity, the easier it is to detect people staying, and thus more frequent dwell video notifications. Conversely, the longer the dwell time, the lower the door lock's dwell sensitivity, the less likely it is to detect people staying, and thus fewer dwell video notifications.

[0187] If the current dwell time is less than the dwell time at the time of the last reminder, it means that the user has reduced the dwell time between the last reminder and the current time. This can be interpreted as the user wanting to stay in the monitoring for a longer period of time to ensure the corresponding monitoring security, and being unaware of the frequent push notifications of the dwell recording. Therefore, no further reminders are needed.

[0188] If the current dwell time is longer than the dwell time at the time of the last reminder, it means that the user has increased the dwell time between the last reminder and the current time. In this case, it can be assumed that the user does not need to stay for monitoring to a greater extent to ensure the corresponding monitoring security, and is not very accepting of the frequent push of dwell recording and the problem of rapid battery drain of the door lock. Therefore, if the user increases the dwell time, and the dwell recording is pushed frequently again in the future, the user can be reminded again in a short time.

[0189] In one embodiment, the terminal device can display a reminder message output by the door lock to alert the user to frequent lingering outside the door. If the user clicks on the reminder message, the terminal device can automatically redirect to the peephole lingering configuration page of the door lock APP, allowing the user to modify the lingering duration as needed. In one embodiment, the content displayed on the peephole lingering configuration page can be as follows: Figure 5 As shown.

[0190] Figure 6In the embodiment shown, it is possible to determine whether and how the user modified the stay duration between the last reminder and the current time if the stay recording is frequently pushed on the same day and the reminder time interval requirement is met. (That is, the reminder count used in step 604 does not take into account the user's modification of the stay duration.) This eliminates the need to monitor the user's modification of the stay duration in real time.

[0191] In another embodiment, the recorded reminder count can be updated in real time based on the user's modification of the stay duration. For example, when the user increases the stay duration, the recorded reminder count can be reset to zero; when the user decreases the stay duration, the recorded reminder count can be set to indicate that reminders will no longer be sent. This makes the determination of whether the reminder time interval requirement is met more aligned with user needs, ensuring timely reminders.

[0192] Figure 6 The embodiment shown updates the record of reminders based on the number of times the user modifies the stay duration. It determines whether the triggering condition for modifying the stay duration is met by judging whether the door lock frequently pushes stay videos on the same day and whether the current time meets the reminder time interval corresponding to the number of reminders. If the condition is met, the user is reminded to increase the stay duration. This can avoid the door lock frequently pushing stay videos in frequent stay scenarios, the battery drains quickly, and repeated reminders to the user.

[0193] For example, in one test case, compared to not reminding the user to modify the dwell time, the dwell recording control scheme provided in this application reminds the user when the dwell time modification trigger condition is met, and the user increases the dwell time (or recording detection time), which can reduce the number of times the door lock performs the dwell recording function by 60%, and can significantly reduce the door lock battery power consumption. The total time for the door lock to complete one dwell recording function can include system startup time, dwell recording time, and dwell recording upload time (upload time is affected by network conditions, with an average upload speed of 400kbps).

[0194] In a scenario where the user is reminded to modify the stay duration due to insufficient stay, in one embodiment of this application, a first reminder message is output when a first condition is met; the first condition includes the number of records being less than the second threshold, and further includes the number of times the door lock takes stay videos within a second time interval being less than or equal to the third threshold; wherein, the second time interval includes the first time interval and the time interval before the first time interval, and the third threshold is greater than the second threshold.

[0195] To avoid accidentally disturbing users by sending unnecessary reminders to modify the stay duration in scenarios where the stay is too short, the trigger conditions for modifying the stay duration in cases of insufficient stay recording include not only the current number of stay recordings that are too short, but also the number of stay recordings that are too short over a longer period of time. If the conditions are not met, no reminder to modify the stay duration will be sent.

[0196] In one embodiment of this application, the second threshold is obtained based on the number of lingering videos viewed within a second time interval. Based on the varying levels of attention different users pay to lingering, a second threshold can be obtained for each user by combining their viewing history of lingering videos over a previous period. This allows for a more targeted assessment of whether the monitoring device is pushing too few lingering videos, thus meeting user needs.

[0197] In one embodiment of this application, the duration of the first time interval is a unit duration, and the duration of the second time interval is multiple unit durations. Based on this, the lingering recording control method further includes: obtaining a lingering perception level based on the number of times the door lock takes lingering recordings within each unit duration of the second time interval, and the number of lingering recordings viewed within each unit duration of the second time interval; obtaining an average number of lingering recordings taken within each unit duration based on the number of times the door lock takes lingering recordings within the second time interval; and obtaining a second threshold based on the obtained lingering perception level and the average number of lingering recordings taken.

[0198] Since different users may have different levels of attention to their stay, and the location of the door lock may vary in different scenarios (such as different apartment layouts), the lower limit of the number of stays can be determined by combining the user's perception of their stay. This allows for accurate determination of the lower limit of the number of stays and makes the service more targeted to the user.

[0199] In one embodiment, the unit duration can be a full 24 hours, and the second time interval can be a series of consecutive days before the current moment.

[0200] In one embodiment, the second threshold number can be calculated using the following formulas (1) to (3). The more attention a user pays to their stay, the greater their perceived stay level, and thus the larger the second threshold number obtained.

[0201] N = MeanTarry × f(x) (1)

[0202]

[0203]

[0204] Where N represents the second threshold, MeanTarry represents the average number of times a recording of a user's dwell time is taken within a unit of time, f(x) represents the user's perceived dwell time, m represents the number of unit periods included in the second time interval, and Total... n This represents the total number of times the lingering video is pushed within the nth unit of time (i.e., the number of times the door lock takes lingering video recordings within the nth unit of time). View n This represents the number of times a user views a lingering video within the nth unit of time (i.e., the number of lingering videos viewed within the nth unit of time), where 'a' is an empirical value used for correction coefficients.

[0205] Considering that users' attention to lingering can vary in different environments, and that different users in the same environment can also have different levels of attention to lingering, in order to meet user needs, we can combine the user's attention to lingering over a previous period of time to specifically judge whether the door lock pushes too few lingering video recordings, that is, whether the door lock is not sensitive to lingering. This makes the lingering video recording control effect meet user needs and improve user experience.

[0206] In one embodiment of this application, the duration of the first time interval is a unit duration, the duration of the second time interval is multiple unit durations, and the third number threshold is the product of the second number threshold and the number of unit durations included in the second time interval.

[0207] Taking a first time interval of one day, a second time interval of m days, and a second counting threshold of N times as an example, the third counting threshold can be N×m times.

[0208] By making the duration of the second time interval multiple times that of the first time interval, and by making the third threshold the same multiple of the second threshold, it is helpful to accurately assess whether there are too few overall dwell time recordings pushed over a longer period of time. This enables precise reminders to modify the dwell time in scenarios where dwell time is too short.

[0209] This application embodiment also provides a loitering recording control device, including: an acquisition module, used to acquire the number of times a monitoring device records a loitering video within a first time interval, wherein the monitoring device records a loitering video once when someone loites within the image acquisition range of the monitoring device and the duration of the loitering reaches a set loitering duration; and a processing module, used to output a first reminder message corresponding to the first condition or modify the loitering duration when a set first condition is met; wherein the first condition includes the number of records being greater than a set first number threshold, or the first condition includes the number of records being less than a set second number threshold.

[0210] This application also provides a monitoring device, which includes an image acquisition module for capturing loitering videos and the aforementioned loitering video control device. In one embodiment, the monitoring device can be a door lock.

[0211] This application also provides an electronic chip, which includes a processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to execute the method steps provided in any method embodiment of this application.

[0212] This application also provides a monitoring device, which includes an image acquisition module for capturing video recordings of a stay, and the aforementioned electronic chip. In one embodiment, the monitoring device can be a door lock.

[0213] This application also provides a monitoring device, which includes one or more memories for storing computer program instructions and one or more processors. When the computer program instructions are executed by the one or more processors, the monitoring device is triggered to execute the method steps provided in any method embodiment of this application. In one embodiment, the monitoring device may be a door lock.

[0214] This application also provides a loitering video recording control system, including: a user terminal and a monitoring device provided in any embodiment of this application. The monitoring device is used to output a first reminder message corresponding to the first condition to the user terminal when the first condition is met. The user terminal is used to display the first reminder message.

[0215] If the monitoring equipment frequently records recordings of the stay in scenarios with frequent stays, or if it records too few recordings in scenarios with infrequent stays, it can remind the user that the current frequency of recordings is too high or too low. This allows the user to adjust the stay duration to address the issue of frequent or infrequent recordings. Furthermore, the user can increase, decrease, or leave the stay duration unchanged as needed to meet their specific requirements.

[0216] In one embodiment, the user terminal is configured to display a configuration page upon detecting a triggering operation on a first reminder message. The configuration page includes controls for configuring the dwell time. Upon detecting an operation to modify the dwell time, the user terminal modifies the dwell time via the controls. If the user needs to modify the dwell time after being reminded, the user terminal can display the configuration page upon the user's triggering of the reminder message, allowing the user to quickly modify the dwell time as needed, resulting in a better user experience.

[0217] In one embodiment, the user terminal is used to update the modified stay duration to the monitoring device. After the user modifies the stay duration as needed, the user terminal can also update the modified stay duration to the monitoring device, so that the monitoring device can record stay videos on demand according to the user's real-time required stay duration, thus ensuring that the number of stay video pushes matches the user's current needs.

[0218] The specific technical implementation of the stay recording control system can be found in the relevant technical descriptions of other embodiments of this application, and will not be repeated here.

[0219] An embodiment of this application also proposes a terminal device, which includes a communication module, a memory for storing computer program instructions, and a processor for executing the program instructions. When the computer program instructions are executed by the processor, the terminal device is triggered to execute the method steps provided in any method embodiment of this application.

[0220] An embodiment of this application also proposes a server device, which includes a communication module, a memory for storing computer program instructions, and a processor for executing the program instructions. When the computer program instructions are executed by the processor, the server device is triggered to execute the method steps provided in any method embodiment of this application.

[0221] One embodiment of this application also provides an electronic device, which includes multiple antennas, a memory for storing computer program instructions, a processor for executing the computer program instructions, and a communication device (such as a communication module that can implement 5G communication based on the NR protocol). When the computer program instructions are executed by the processor, the electronic device is triggered to execute the method steps provided in any method embodiment of this application.

[0222] Specifically, in one embodiment of this application, one or more computer programs are stored in the aforementioned memory, and the one or more computer programs include instructions that, when executed by the aforementioned device, cause the aforementioned device to perform the method steps described in the embodiments of this application.

[0223] Furthermore, the devices, apparatuses, and modules described in the embodiments of this application may be implemented by computer chips or physical entities, or by products with certain functions.

[0224] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0225] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, 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 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, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0226] Specifically, one embodiment of this application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to execute the method steps provided in the embodiment of this application.

[0227] An embodiment of this application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the method steps provided in the embodiments of this application.

[0228] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of 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 indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be electrical, mechanical, or other forms.

[0229] 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 according to actual needs.

[0230] 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 in a combination of hardware and software functional units.

[0231] An integrated unit implemented as a software functional unit can be stored in a computer-readable storage medium. This software functional unit, stored in a storage medium, includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0232] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0233] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0234] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments of this application can be implemented using electronic hardware, computer software, or a combination of electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0235] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the same or similar parts between the various embodiments of this application can be referred to mutually. For example, the specific working processes of the systems, devices, and units described in the embodiments of this application can be referred to the corresponding processes in the method embodiments of this application, and will not be repeated here.

[0236] The above description is merely a specific embodiment of this application and is not intended to limit this application. The scope of protection of this application shall be determined by the claims.

Claims

1. A method for controlling lingering video recording, characterized in that, include: The number of times the monitoring device records a stay video within a first time interval is obtained. The first time interval is a period of time before the current moment. The monitoring device records a stay video once when someone stays within the image acquisition range of the monitoring device and the duration of the stay reaches the set stay duration. If the first condition is met, output a first reminder message corresponding to the first condition or modify the stay duration; The first condition is a condition for modifying the stay duration to deal with frequent recording of stay videos, and the first condition includes the number of records being greater than or equal to a set first number threshold. Alternatively, the first condition is a condition for modifying the stay duration to deal with insufficient recording of stay videos, and the first condition includes the number of records being less than or equal to a set second number threshold.

2. The method according to claim 1, characterized in that, The method further includes: If the second condition is met, output the second reminder message corresponding to the second condition or modify the current stay duration; Wherein, one of the first condition and the second condition includes the number of records being greater than or equal to the first number threshold, and the other of the first condition and the second condition includes the number of records being less than or equal to the second number threshold, and the first number threshold being greater than the second number threshold.

3. The method according to claim 1 or 2, characterized in that, If the first condition is met, output the first reminder message; If the first condition includes the number of records being greater than or equal to the first number threshold, the first condition further includes: the first time interval is not within the prohibited reminder time interval.

4. The method according to claim 3, characterized in that, The prohibited reminder time interval is obtained by increasing, decreasing or maintaining the dwell time.

5. The method according to claim 3, characterized in that, The method further includes: If, after the first reminder message is output on the monitoring device, there is an operation that does not match the first reminder message, then the first time interval is determined to be within the prohibited reminder time interval.

6. The method according to claim 1 or 2, characterized in that, If the first condition is met, output the first reminder message; If the first condition includes the number of recordings being less than or equal to the second number threshold, the first condition further includes: the number of times the monitoring device records the stay video within the second time interval being less than or equal to the third number threshold; The second time interval includes the first time interval and the time interval preceding the first time interval, and the third number threshold is greater than the second number threshold.

7. The method according to claim 6, characterized in that, The second threshold number is obtained based on the number of lingering videos viewed within the second time interval.

8. A device for controlling recording of loitering, characterized in that, include: The acquisition module is used to acquire the number of times the monitoring device captures a sojourn video within a first time interval, wherein the first time interval is a period of time before the current moment, and the monitoring device captures a sojourn video once when someone lingers within the image acquisition range of the monitoring device and the duration of the sojourn reaches the set sojourn duration. The processing module is used to output a first reminder message corresponding to the first condition or modify the stay duration when the first condition is met. The first condition is a condition for modifying the stay duration to deal with frequent recording of stay videos, and the first condition includes the number of records being greater than or equal to a set first number threshold. Alternatively, the first condition is a condition for modifying the stay duration to deal with insufficient recording of stay videos, and the first condition includes the number of records being less than or equal to a set second number threshold.

9. An electronic chip, characterized in that, include: A processor for executing computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to perform the method of any one of claims 1-7.

10. A monitoring device, characterized in that, include: An image acquisition module for capturing a sojourn video, and a sojourn video recording control device as described in claim 8 or an electronic chip as described in claim 9.

11. A monitoring device, characterized in that, The monitoring device includes one or more memories for storing computer program instructions and one or more processors, wherein when the computer program instructions are executed by the one or more processors, the monitoring device is triggered to perform the method as described in any one of claims 1-7.

12. A loitering video recording control system, characterized in that, include: User terminal, and monitoring equipment as described in claim 10 or 11; The monitoring device is used to output a first reminder message corresponding to the first condition to the user terminal when the first condition is met. The user terminal is used to display the first reminder message.

13. The loitering video recording control system according to claim 12, characterized in that, The user terminal is configured to display a configuration page when a trigger operation on the first reminder message is detected, the configuration page including a control for configuring the stay duration; and to modify the stay duration through the control when an operation for modifying the stay duration is detected.

14. The loitering video recording control system according to claim 13, characterized in that, The user terminal is used to update the modified stay duration to the monitoring device.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-7.

16. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-7.

Images