Keep-alive control method and system for intelligent device

Abstract

The application discloses a keep-alive control method and system of an intelligent device. The method comprises the following steps: the intelligent device is switched from a low-power mode to a normal mode at a current wake-up time, and is connected to an associated router for communication, wherein the router is used for proxying the intelligent device to perform a keep-alive connection with a cloud platform, and the current wake-up time is determined based on a first period; the intelligent device performs period negotiation with the router to determine a second period of the intelligent device, and the second period is used for determining a next wake-up time of the intelligent device after the intelligent device is switched to the low-power mode. The above scheme can reduce the power consumption of the keep-alive connection of the intelligent device.

Description

Technical Field

[0001] This application relates to the field of intelligent device control technology, and in particular to a keep-alive control method and system for intelligent devices. Background Technology

[0002] With the rapid development of IoT technology, smart devices (such as smart door locks, low-power sensors, smart wearable devices, etc.) have been widely used in various application scenarios.

[0003] These types of smart devices need to maintain a long-term connection to the cloud platform to stay online and enable functions such as remote control, status reporting, and command reception. In related technologies, frequent and prolonged connections and communication between smart devices and the cloud platform increase energy consumption and reduce battery life.

[0004] Therefore, it is urgent to reduce the power consumption of smart devices while keeping them connected online. Summary of the Invention

[0005] The main technical problem addressed by this application is to provide a keep-alive control method and system for smart devices, which can reduce the power consumption of keep-alive connections in smart devices.

[0006] The first aspect of this application provides a keep-alive control method for a smart device, the method comprising: the smart device switching from a low-power mode to a normal mode at the current wake-up time and establishing a communication connection with an associated router, wherein the router is used to proxy the smart device to establish a keep-alive connection with a cloud platform, and the current wake-up time is determined based on a first cycle; the smart device and the router negotiate a cycle to determine a second cycle for the smart device, the second cycle being used to determine the next wake-up time after the smart device switches to the low-power mode.

[0007] The second aspect of this application provides a keep-alive control method for a smart device, the method comprising: a router communicating with the smart device in response to the associated smart device switching from a low-power mode to a normal mode at the current wake-up time, wherein the router acts as an intermediary for the smart device to establish a keep-alive connection with the cloud platform, and the current wake-up time is determined based on a first cycle; the router and the smart device negotiate a cycle to determine a second cycle for the smart device, the second cycle being used to determine the next wake-up time after the smart device switches to a low-power mode.

[0008] A third aspect of this application provides a keep-alive control method for a smart device. The method includes: a cloud platform establishing a keep-alive connection with a router that acts as an agent for the smart device, enabling the smart device and the router to implement the keep-alive control method described above; wherein the smart device switches from a low-power mode to a normal mode at the current wake-up time and establishes a communication connection with the associated router, wherein the current wake-up time is determined based on a first cycle; the smart device and the router negotiate a cycle to determine a second cycle for the smart device, the second cycle being used to determine the next wake-up time after the smart device switches to the low-power mode.

[0009] The fourth aspect of this application provides a keep-alive control system for a smart device, the keep-alive control system for a smart device comprising: a smart device, a router, and a cloud platform, the combination of the smart device, the router, and the cloud platform being used for any of the above-mentioned keep-alive control methods for a smart device.

[0010] The fifth aspect of this application provides a computer device including a memory and a processor coupled to each other, the memory storing program instructions, and the processor executing the program instructions to implement the keep-alive control method for any of the above-described intelligent devices.

[0011] The sixth aspect of this application provides a computer-readable storage medium storing program instructions that, when executed by a processor, implement the keep-alive control method for any of the above-mentioned intelligent devices.

[0012] The above solution involves the smart device determining the current wake-up time based on the first cycle, switching from low-power mode to normal mode at the current wake-up time, and establishing a communication connection with the associated router. Simultaneously, the smart device and the router negotiate the second cycle to determine the next wake-up time after switching to low-power mode. Furthermore, the router acts as a proxy for the smart device to complete the keep-alive connection with the cloud platform. This effectively reduces the power consumption of the smart device, extends its battery life, ensures the stability and reliability of the keep-alive connection between the smart device and the cloud platform, and allows for flexible adaptation of the smart device's wake-up strategy through periodic negotiation, improving overall communication efficiency and device operation rationality. Overall, it reduces the power consumption of the smart device in maintaining the keep-alive connection with the cloud platform.

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

[0014] To more clearly illustrate the technical solutions in this application, the accompanying drawings required in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Among them: Figure 1 This is a flowchart illustrating the first embodiment of the keep-alive control system for the intelligent device of this application; Figure 2 This is a flowchart illustrating the second embodiment of the keep-alive control system for the intelligent device of this application; Figure 3 This is a flowchart illustrating the first embodiment of the keep-alive control method for intelligent devices according to this application; Figure 4 This is a flowchart illustrating the second embodiment of the keep-alive control method for intelligent devices according to this application; Figure 5 This is a flowchart illustrating the third embodiment of the keep-alive control method for intelligent devices in this application; Figure 6 This is a flowchart illustrating the fourth embodiment of the keep-alive control method for intelligent devices in this application; Figure 7 This is a flowchart illustrating the fifth embodiment of the keep-alive control method for intelligent devices in this application; Figure 8 This is a schematic diagram of the structure of an embodiment of the computer device of this application; Figure 9 This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium of this application. Detailed Implementation

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

[0016] The terms "first" and "second" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0017] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

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

[0019] This application provides the following embodiments, and each embodiment is described in detail below.

[0020] Please see Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the keep-alive control system for the intelligent device of this application. The keep-alive control system 100 for the intelligent device includes an intelligent device 110, a router 120, and a cloud platform 130. The router 120 can communicate with both the intelligent device 110 and the cloud platform 130. The router 120 can act as a proxy for the keep-alive connection between the intelligent device 110 and the cloud platform 130, and can maintain a virtual connection between the intelligent device 110 and the cloud platform 130.

[0021] Optionally, the number of smart devices 110 can be at least one. When the smart device keep-alive control system 100 includes multiple smart devices 110, the router 120 can respectively proxy each smart device 110 to maintain a keep-alive connection with the cloud platform 130, and maintain a virtual connection between each smart device 110 and the cloud platform 130.

[0022] The smart device 110 can be a device that requires a keep-alive connection. For example, the smart device 110 can be an IoT device, a device that is not directly powered (such as one that requires battery power or charging), or a low-power smart device. For example, the smart device 110 includes smart locks (such as smart door locks, smart access control systems), smart speakers, low-power sensors, smart wearable devices, etc. The following description uses a smart door lock as an example. This application does not limit the smart device 110.

[0023] Router 120 can be a WiFi (wireless network) access point, for example, an access point that has functions related to the keep-alive control method of the smart device in this embodiment. Router 120 is not limited in this application.

[0024] The server of cloud platform 130 can establish a keep-alive connection with router 120 on behalf of smart device 110. For example, it can receive keep-alive information sent by router 120, which includes connection information and heartbeat information; for example, it can first send operation instructions to smart device 110 to router 120 for temporary storage, and after router 120 establishes a communication connection with smart device 110, it will then send the operation instructions to smart device 110.

[0025] In some implementations, the smart device keep-alive control system 100 also includes a client (not shown), such as a smartphone, tablet, laptop, desktop computer, smartwatch, etc. The client can connect to the cloud platform 130 via a network, and the target object can input remote operation commands for the smart device 110 in the client's application to enable remote operation of the smart device 110.

[0026] In some implementations, please refer to Figure 2 , Figure 2 This is a flowchart illustrating the second embodiment of the keep-alive control system for the intelligent device of this application.

[0027] The smart device 110 includes a main control module, a communication module (such as WiFi), a power management module, and functional modules (such as lock body control and sensors for smart door locks). These modules are not shown in the diagram. The main control module can be a main control MCU (Microcontroller Unit) used to control the various modules of the smart device 110. The communication module is used to communicate with other external devices (such as router 120). The power management module is used to manage the power of the smart device 110. The functional modules are used to implement the corresponding functions of the smart device 110. The above modules can refer to modules in related technologies. This application does not limit the above modules.

[0028] Optionally, the smart device 110 (such as its software layer) also includes a negotiation module and a context-aware module. The negotiation module can be a TWT (Target Wake Time) negotiation module, the coordination module can be used to conduct periodic negotiations with the router 120, and the context-aware module can collect various feature data of the smart device to obtain the influencing factors collected by the smart device.

[0029] Optionally, the router 120 includes a proxy keep-alive module and a coordination management module. The router 120 can serve as an access point for a wireless network and can connect with the smart device 110. The proxy keep-alive module is used to proxy the smart device 110 to maintain a keep-alive connection with the cloud platform 130. The coordination management module can be a TWT coordination management module, used to periodically negotiate with the smart device 110 (such as its coordination module) to determine the wake-up cycle of the smart device 110.

[0030] Optionally, the cloud platform 130 includes a data acquisition module that can collect relevant data of operation instructions, client behavior data, etc., and send them to the router 120 to obtain influencing factors based on this data. This application does not impose any restrictions on this.

[0031] The combination of the above-mentioned smart device 110, router 120 and cloud platform 130 can be used to implement the smart device keep-alive control method of any of the following embodiments, specifically referring to the following embodiments.

[0032] In some embodiments, please refer to Figure 3 , Figure 3 This is a flowchart illustrating the first embodiment of the keep-alive control method for a smart device according to this application. This embodiment is applied to a smart device, and the method may include the following steps: S11: Smart devices establish a connection with the router.

[0033] Initialization and proxy connection establishment can be performed first, and an association connection can be established between the smart device and the router. Optionally, network association and authentication can be performed between the smart device and the router to establish an association connection.

[0034] S12: Perform capability negotiation with the router to confirm whether the router has keep-alive control capability, which includes the ability to keep-alive connections and the ability to periodically negotiate.

[0035] The smart device negotiates capabilities with the router to confirm whether the router has keep-alive control capabilities. These keep-alive control capabilities include the ability to keep the connection alive and the ability to periodically negotiate (such as TWT periodic coordination). For example, the smart device exchanges frames with the router to confirm whether the router has keep-alive control capabilities.

[0036] Optionally, in response to the router having keep-alive control capability, the following step S13 is performed.

[0037] Optionally, if the router has keep-alive control capability, the process ends; or, the smart device wakes up using a preset period, and each wake-up period of the smart device is configured to a preset period.

[0038] S13: In response to the router having keep-alive control capabilities, the authentication information of the smart device is sent to the router so that the router can use the authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform.

[0039] In response to the router's keep-alive control capabilities, the smart device establishes a proxy keep-alive contract with the router. The smart device can send its authentication information to the router, enabling the router to use this authentication information to proxy the smart device's keep-alive connection with the cloud platform. The smart device's authentication information includes information such as a security token and device serial number. The security token can be a security token generated from the smart device's account information; this application does not restrict the authentication information.

[0040] In some implementations, the smart device can encrypt its authentication information to obtain encrypted authentication information, and then send the encrypted authentication information to the router. This method allows for encrypted transmission; for example, the smart device can use TLS (Transport Layer Security) encryption to encrypt the authentication information before transmitting it to the router. The router can establish a connection with the cloud platform using its own information (i.e., from the router's perspective). After establishing the connection, the router can use the encrypted authentication information (i.e., the authentication information) to proxy the smart device to complete registration, periodically maintain a long connection, and maintain a keep-alive connection with the cloud platform according to a preset keep-alive strategy. Afterward, the cloud platform considers the smart device to be online. The preset keep-alive strategy can include policies related to the keep-alive connection, such as preset heartbeat intervals and timeout thresholds. For example, the preset keep-alive strategy could be to send keep-alive information to the cloud platform on behalf of the smart device according to a preset heartbeat interval. If no confirmation information is received from the cloud platform upon reaching the timeout threshold, the proxy keep-alive connection is determined to be abnormal, and a reconnection with the cloud platform can be initiated. This application does not limit the preset keep-alive strategy.

[0041] In some implementations, the following step may be included after step S13: S14: The smart device and the router conduct the first cycle negotiation to determine the initial cycle of the smart device. The initial cycle is used to determine the first wake-up time after the smart device enters the low power mode.

[0042] The smart device and the router conduct an initial period negotiation (such as TWT negotiation) to determine the initial period of the smart device. The initial period is used to determine the first wake-up time after the smart device enters low-power mode. The initial period can be a preset initial period, such as 5 seconds or 8 seconds, or it can be negotiated through frame interaction. The initial period negotiation can utilize reference parameters such as the smart device's performance, the router's performance, and the network environment to determine the initial period of the smart device. This application does not impose any restrictions on the initial period.

[0043] Optionally, after determining the initial cycle of the smart device, the smart device enters a low-power mode and is woken up by the initial cycle. The smart device can be woken up based on the wake-up time determined by the initial cycle to switch from the low-power mode to the normal mode.

[0044] The above solution can shift the application-layer keep-alive connection task from limited terminal devices to more powerful network infrastructure (routers), and includes processes such as authentication information, encrypted transmission, capability negotiation, and registration of authorized agents to improve the security of the router proxy smart device's keep-alive connection with the cloud platform. In addition, the wake-up of the TWT cycle can maximize the sleep cycle and reduce the power consumption of smart devices.

[0045] In some embodiments, please refer to Figure 4 , Figure 4 This is a flowchart illustrating a second embodiment of the keep-alive control method for a smart device according to this application. This embodiment is applied to a smart device, and the method may include the following steps: S21: The smart device switches from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the associated router. The router is used to proxy the smart device to maintain a keep-alive connection with the cloud platform. The current wake-up time is determined based on the first cycle.

[0046] Smart devices can associate with routers and communicate with them. Routers can connect to cloud platforms, allowing them to act as agents for the smart devices in maintaining a keep-alive connection. The router can send keep-alive messages to the cloud platform on behalf of the smart devices, thus ensuring the cloud platform considers the smart devices online and maintains a keep-alive connection. Smart devices can have at least two modes: a low-power mode and a normal mode. The low-power mode can be a sleep state, in which case the smart device disconnects from the router. In normal mode, the smart device maintains communication with the router. After entering low-power mode, the smart device wakes up during a wake-up cycle to switch from low-power mode to normal mode.

[0047] In each wake-up cycle, the smart device determines the current wake-up time based on the first cycle, where the first cycle utilizes the wake-up cycle of the smart device determined by the initial cycle or the previous cycle negotiation. The smart device wakes up at the current wake-up time, switching from low-power mode to normal mode and establishing a communication connection with the associated router. This communication connection can be brief, during which the smart device and router can perform data exchange and other operations.

[0048] In some embodiments, after communicating with the router, the smart device may perform at least one of the following tasks: confirming the proxy keep-alive connection status, periodic negotiation, other data interaction, etc. This application does not impose any limitations on this.

[0049] In some implementations, the smart device verifies the proxy keep-alive connection status between the associated router and the cloud platform: it checks whether the router has any pending forwarding instructions issued by the cloud platform; in response to the presence of such instructions, the router sends the instructions to the smart device, which receives and executes them, and sends a completion message to the router upon completion. After all pending instructions are completed, the router sends a confirmation message (i.e., a confirmation frame) indicating that the proxy keep-alive connection is normal. The smart device receiving this confirmation message indicates that the router's proxy keep-alive connection between the smart device and the cloud platform is normal. Alternatively, in response to the absence of pending forwarding instructions from the cloud platform, the router directly sends a confirmation message indicating that the proxy keep-alive connection is normal to the smart device, which then directly receives it.

[0050] In some application scenarios, a keep-alive connection is established between the router and the cloud platform. In response to an anomaly in the proxy keep-alive connection between the router and the cloud platform, the router can re-establish the keep-alive connection. For example, this can be done in the low-power mode or normal mode of the smart device. Optionally, if re-establishing the keep-alive connection requires the smart device to resend authentication information, the router sends a message indicating a proxy keep-alive connection anomaly to the smart device during communication. In response, the smart device resends authentication information to the router, allowing the router to re-proxy the smart device to establish a keep-alive connection with the cloud platform based on this information. Optionally, if re-establishing the keep-alive connection does not require the smart device to resend authentication information, the router can directly re-proxy the smart device to establish a keep-alive connection with the cloud platform.

[0051] S22: The smart device and the router negotiate the cycle to determine the second cycle of the smart device. The second cycle is used to determine the next wake-up time after the smart device switches to low power mode.

[0052] In some implementations, after the smart device communicates with the router, the smart device and the router perform periodic negotiation (such as TWT periodic renegotiation) to determine the second period of the smart device. The second period is used to determine the next wake-up time after the smart device switches to low power mode, so that it can be used as the new current wake-up time to re-execute the above steps S21 to S22. After each wake-up, a new wake-up period can be dynamically determined.

[0053] In some implementations, the periodic negotiation can agree on the second period for the next wake-up. Specifically, the smart device and the router can determine the second period of the smart device through frame interaction, such as negotiating the service period, period interval, wake-up time, etc. This application does not limit the periodic negotiation.

[0054] In some implementations, after the smart device and the router negotiate the cycle and determine the second cycle of the smart device, the smart device responds to complete the task of the current wake-up. After there are no other tasks to execute, it switches from normal mode to low power mode and can immediately enter the next deep sleep cycle, wait for the next current wake-up time (next wake-up time), and re-execute the above steps. The above steps can be executed cyclically.

[0055] In some embodiments, for step S22 above, the smart device and the router can use influencing factors to conduct periodic negotiation to determine the second period of the smart device; wherein, the influencing factors include at least one of the following: influencing factors collected by the smart device, influencing factors collected by the cloud platform, and influencing factors collected by the router.

[0056] Optionally, after the smart device establishes a communication connection with the router, it can send the influencing factors collected by the smart device to the router, or send the collected data from the smart device, and the router can obtain the corresponding influencing factors based on the collected data from the smart device.

[0057] In some implementations, during the periodic negotiation process, a router (such as a TWT collaborative management module) may be used to determine the second period, or the router and smart device may work together to determine the second period. This application does not impose any restrictions on this.

[0058] Optionally, the router adjusts the base cycle based on influencing factors to obtain the smart device's second cycle, and then sends it to the smart device for cycle confirmation, thereby dynamically determining the wake-up cycle T_next for the next TWT. In this case, the smart device receives the second cycle sent by the router; where the second cycle is obtained by the router adjusting the base cycle based on influencing factors.

[0059] Optionally, the influencing factors collected by the smart device include a first part of influencing factors and a second part of influencing factors. Among them, the first part of influencing factors is sent to the router, and the second part of influencing factors is not sent to the router. The security requirement of the second part of influencing factors is higher than that of the first part of influencing factors. In this case, for the influencing factors with higher security requirements, they can be not sent to the router but only stored by the smart device, and the two cooperate to determine the second period. The router adjusts the base period using the influencing factors in the first case to obtain the second period of the smart device and sends it to the smart device. Among them, the influencing factors in the first case include at least one of the following: the first part of influencing factors collected by the smart device, the influencing factors collected by the cloud platform, and the influencing factors collected by the router; the smart device receives the second period of the smart device sent by the router; then, the smart device adjusts the second period using the influencing factors in the second case to obtain the adjusted second period and sends the adjusted second period to the router, so that the router receives the adjusted second period and performs a period confirmation on the adjusted second period; among them, the influencing factors in the second case include: the second part of influencing factors collected by the smart device.

[0060] Optionally, the base period can be a preset period or an initial period, and this application does not limit the base period.

[0061] In the above solution, the smart device determines the current wake-up time based on the first period, switches from the low-power mode to the normal mode at the current wake-up time, and communicates with the associated router. At the same time, the smart device and the router perform a period negotiation to determine the second period of the smart device to determine the next wake-up time after switching to the low-power mode, and the router is used as an agent for the smart device to complete the keep-alive connection with the cloud platform. This can effectively reduce the power consumption of the smart device and extend the device's battery life, and can also ensure the stability and reliability of the keep-alive connection between the smart device and the cloud platform. It can also achieve flexible adaptation of the smart device's wake-up strategy through period negotiation, improve the overall communication efficiency and device operation rationality, and generally reduce the power consumption of the keep-alive connection between the smart device and the cloud platform.

[0062] In addition, using the router as an agent for the smart device to perform a keep-alive connection with the cloud platform eliminates the high-power consumption link of the smart device communicating with the remote server, and combined with the dynamic adjustment of the TWT period, greatly reduces the number of ineffective wake-ups. Using the router as a local agent, the network environment is more stable, reducing the "false offline" problem of the smart device caused by fluctuations in the wide area network and improving the connection reliability. In addition, the period negotiation is based on the TWT protocol of the wireless network, with little hardware modification to the smart device, mainly relying on software upgrades on the router side, improving compatibility.

[0063] In some embodiments, please refer to Figure 5 , Figure 5This is a flowchart illustrating a third embodiment of the keep-alive control method for smart devices according to this application. This embodiment is applied to a router, and the method may include the following steps: S31: The router responds to the associated smart device switching from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the smart device. The router acts as an intermediary for the smart device to maintain a keep-alive connection with the cloud platform. The current wake-up time is determined based on the first cycle.

[0064] In some embodiments, prior to step S31, the router establishes an association connection with the smart device. Then, the router and the smart device perform capability negotiation to confirm whether the router has keep-alive control capability. This keep-alive control capability includes the ability to maintain a keep-alive connection and the ability to periodically negotiate. In response to the router having keep-alive control capability, the router receives authentication information sent by the smart device and uses this authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform.

[0065] In some implementations, the router receives encrypted authentication information sent by the smart device, wherein the encrypted authentication information is obtained by the smart device encrypting the authentication information; the router establishes a connection with the cloud platform, uses the encrypted authentication information to proxy the smart device to complete the registration, and establishes a keep-alive connection with the cloud platform according to a preset keep-alive policy.

[0066] In some implementations, after the router proxies the smart device to establish a keep-alive connection with the cloud platform, the router and the smart device conduct an initial periodic negotiation to determine the initial period of the smart device. The initial period is used to determine the first wake-up time after the smart device enters a low-power mode.

[0067] After each wake-up cycle of the smart device, the router responds by switching from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the smart device. The router acts as a proxy for the smart device to maintain a keep-alive connection with the cloud platform. The current wake-up time is determined based on the first cycle. This step can be specifically described in the above embodiments, and will not be repeated here.

[0068] S32: The router and the smart device negotiate a periodic period to determine the second period of the smart device. The second period is used to determine the next wake-up time after the smart device switches to low power mode.

[0069] The router can negotiate with the smart device periodically to determine the second period for the smart device to wake up next. The second period is used to determine the next wake-up time after the smart device switches to low-power mode.

[0070] In some implementations, the router and the smart device negotiate a periodicity using influencing factors to determine the second period for the smart device; wherein the influencing factors include at least one of the following: influencing factors collected by the smart device, influencing factors collected by the cloud platform, and influencing factors collected by the router.

[0071] Optionally, the router adjusts the base cycle using influencing factors to obtain the second cycle of the smart device, and sends the second cycle of the smart device to the smart device.

[0072] Optionally, the influencing factors collected by the smart device include a first part of influencing factors and a second part of influencing factors. The first part of influencing factors is sent to the router, while the second part is not. The security requirements for the second part of influencing factors are higher than those for the first part. In this case, the router adjusts the base period using the influencing factors of the first scenario to obtain the second period of the smart device, and then sends the second period of the smart device to the smart device. The influencing factors of the first scenario include at least one of the following: the first part of influencing factors collected by the smart device, the influencing factors collected by the cloud platform, and the influencing factors collected by the router. The router receives the adjusted second period sent by the smart device. The adjusted second period is obtained by the smart device adjusting the second period using the influencing factors of the second scenario. The influencing factors of the second scenario include the second part of influencing factors collected by the smart device.

[0073] The specific implementation process of the above steps can be referred to the specific implementation process of the router in the above embodiments, and will not be repeated here.

[0074] In some embodiments, for the steps related to the periodic negotiation between the smart device and the router, such as adjusting the base period using influencing factors to obtain the second period of the smart device; and / or adjusting the base period using the influencing factors of the first case to obtain the second period of the smart device, the base period can be adjusted using the adjustment coefficients determined by each influencing factor to obtain the final second period.

[0075] Please see Figure 6 , Figure 6 This is a flowchart illustrating the fourth embodiment of the keep-alive control method for smart devices according to this application. This embodiment is applied to a router, and the method may include the following steps: S41: Determine the first adjustment coefficient for each influencing factor.

[0076] The first adjustment coefficient for each influencing factor can be determined by utilizing the various influencing factors.

[0077] In some implementations, each influencing factor may correspond to multiple states. Preset coefficients can be set for each influencing factor and / or each state of each influencing factor. Thus, the first adjustment coefficient of each influencing factor can be determined based on the preset coefficients corresponding to each influencing factor.

[0078] In some implementations, the aforementioned influencing factors include at least one of the following: influencing factors collected by smart devices, influencing factors collected by cloud platforms, and influencing factors collected by routers. Smart devices, cloud platforms, and routers can acquire collected data and obtain the influencing factors of each device based on the collected data. For example, the collected data can be used as an influencing factor, or the influencing factors can be obtained by processing or analyzing the collected data. This application does not limit the influencing factors collected by each device.

[0079] In some implementations, the influencing factors include at least one of the following: proxy status, power information, time context, device usage information, and password validity information. The proxy status represents the keep-alive connection status between the router and the cloud platform, and can be collected by the router and / or the cloud platform. The power information represents the current power level or power range of the smart device. The password validity information can represent the validity period of the password, and both the power information and password validity information are collected by the smart device. For example, the time context can represent the current usage period, and the time context is collected by the smart device and / or the cloud platform. Device usage information can include the predicted usage probability for each time period, device usage habits, etc., and can be obtained by the smart device and / or the cloud platform from relevant information of historical operation commands, such as time series data of historical operations (e.g., unlocking commands) of the smart lock. This information is then sent to the router, which processes the relevant information of the historical operation commands to obtain device usage information. Alternatively, the cloud platform processes the relevant information of the historical operation commands to obtain device usage information before sending it to the router. This application does not limit the device usage information. Corresponding preset coefficients are provided for each of the above influencing factors and / or different states of each influencing factor.

[0080] Optionally, if the device usage information can include the predicted usage probability for each time period, the router or cloud platform performs pre-defined statistics (such as Gaussian distribution fitting) on ​​the relevant information of historical operation commands to predict the probability that the smart device will be operated or receive the issued operation commands in the future time period, that is, to obtain the predicted usage probability. Alternatively, the router or cloud platform uses a time series model (such as a lightweight time series model) to predict the relevant information of historical operation commands to obtain the predicted usage probability of the smart device in the future time.

[0081] In some implementations, a first adjustment coefficient for each influencing factor is determined based on a preset coefficient corresponding to each influencing factor, as follows: Proxy Status: Proxy status can include normal proxy keep-alive connection, abnormal proxy keep-alive connection, and pending instruction forwarding. In response to a normal proxy keep-alive connection status, a first proxy coefficient (e.g., 1) is determined as the first adjustment coefficient. Alternatively, in response to a pending instruction forwarding or abnormal proxy keep-alive connection status, a second proxy coefficient (e.g., 0.1) is determined as the first adjustment coefficient, where the first proxy coefficient is greater than the second proxy coefficient. This method reduces the next wake-up cycle in the case of an abnormal proxy keep-alive connection or pending instruction forwarding, allowing for rapid response or connection reconstruction.

[0082] Battery Information: In response to battery information falling within a preset battery range, a preset coefficient corresponding to the preset battery range is determined as the first adjustment coefficient. Optionally, the preset battery range may include at least two battery ranges, each with a corresponding preset coefficient. The preset coefficient for the higher battery range is less than that for the lower battery range. For example, the preset battery range may be divided into a preset low battery range (e.g., a battery range not exceeding a preset battery threshold) and a non-preset low battery range (e.g., a range exceeding the preset battery threshold). In response to battery information exceeding the preset battery threshold (e.g., exceeding 20%), the corresponding preset coefficient (e.g., 1) is determined as the first adjustment coefficient. Alternatively, in response to battery information not exceeding the preset battery threshold (e.g., not exceeding 20%), the corresponding preset coefficient (e.g., 10) is determined as the first adjustment coefficient. This method can extend the wake-up cycle as much as possible when the battery is low to prolong the battery life of the smart device.

[0083] Time Context: In response to a time context belonging to a preset time period, a preset coefficient corresponding to the preset time period is determined as the first adjustment coefficient. The preset time period may include at least two time periods, and a corresponding preset coefficient can be set for each time period separately. Optionally, the preset time period includes at least a first time period (e.g., 1 AM to 6 AM) and a second time period (e.g., 8 AM to 8 PM). The first time period corresponds to a first time coefficient (e.g., 10), and the second time period corresponds to a second time coefficient (e.g., 1). The first time coefficient is less than the second time coefficient. This application does not limit the time periods and their corresponding preset coefficients.

[0084] Device Usage Information: Responding to the device usage information representing the predicted usage probability for the current time period, a preset coefficient corresponding to the predicted usage probability for the current time period is determined as the first adjustment coefficient. The predicted usage probability for the current time period is obtained by predicting using historical device usage information, and the preset coefficient is inversely proportional to the predicted usage probability. The predicted usage probability can be divided into multiple levels, each with a corresponding preset coefficient. For example, the predicted usage probability can be divided into high usage probability, medium usage probability, and low usage probability. A preset coefficient of 0.5 corresponds to high usage probability, 1 to medium usage probability, and 2 to low usage probability. This method can dynamically adjust the wake-up cycle, improving response speed and reducing power consumption.

[0085] Password validity period information: In response to the password validity period falling within a preset near-expiration range, a first validity period coefficient is determined as the first adjustment coefficient; conversely, in response to the password validity period falling outside the preset near-expiration range, a second validity period coefficient is determined as the first adjustment coefficient, wherein the first validity period coefficient is less than the second validity period coefficient. For example, the preset near-expiration range may include 30 minutes before or after the password takes effect, 30 minutes before or 0 minutes after the password expires, etc. The first validity period coefficient corresponding to falling within the preset near-expiration range is 0.2, and the second validity period coefficient corresponding to falling outside the preset near-expiration range is 1. For instance, if a temporary password is valid from 3-4 PM on the same day, at the current time or 2:50 PM, the next TWT cycle can be proactively shortened to ensure that the smart device can be woken up in time to receive the command issued by the router for the password.

[0086] This application does not impose any restrictions on the above-mentioned influencing factors and their corresponding preset coefficients.

[0087] S42: Adjust the base cycle using the first adjustment coefficient corresponding to each influencing factor to obtain the second cycle of the smart device; or, adjust the base cycle using the first adjustment coefficient corresponding to each influencing factor and the priority corresponding to each influencing factor to obtain the second cycle of the smart device.

[0088] In some implementations, the base period can be adjusted using the first adjustment coefficients corresponding to each influencing factor. For example, the base period can be weighted using each first adjustment coefficient to obtain the second period of the smart device.

[0089] For example, the base period is T_base (e.g., 10 seconds). The base period is adjusted using the first adjustment coefficient corresponding to each influencing factor to obtain the second period of the smart device, as follows: T_next=T_base*F_proxy*F_battery*F_time*F_habit*F_key.

[0090] Where T_next represents the second period, T_base represents the base period, and F_xxx represents the first adjustment coefficient corresponding to each influencing factor. Specifically, F_proxy is the first adjustment coefficient corresponding to the proxy status, F_battery is the first adjustment coefficient corresponding to the battery information, F_time is the first adjustment coefficient corresponding to the time context, F_habit is the first adjustment coefficient corresponding to the device usage information, and F_key is the first adjustment coefficient corresponding to the password validity information.

[0091] In some implementations, the base cycle can be adjusted using the first adjustment coefficient corresponding to each influencing factor and the priority corresponding to each influencing factor to obtain the second cycle of the smart device.

[0092] Optionally, after determining the first adjustment coefficient corresponding to each influencing factor, the priority of each influencing factor can be obtained. Then, based on the priority of each influencing factor, the priority coefficient of the first adjustment coefficient is determined. The priority coefficient is then used to adjust the first adjustment coefficient of the influencing factor to obtain the second adjustment coefficient. The second adjustment coefficient is then used to adjust the base cycle to obtain the second cycle of the smart device.

[0093] Optionally, the priority coefficient indicates whether the first adjustment coefficient is effective. The effectiveness of the first adjustment coefficient can be determined using the priority coefficient corresponding to each first adjustment coefficient. Then, the effective first adjustment coefficients are used to weight the base period to obtain the second period of the smart device. Specifically, the corresponding priority coefficient can be obtained for the first adjustment coefficient corresponding to each priority factor; that is, each priority corresponds to a separate priority coefficient.

[0094] Optionally, in response to the triggering condition being met by the influencing factors of the current priority, the priority coefficient of the first adjustment coefficient corresponding to the lower priority is determined to be a first value (e.g., 0), where lower priority includes priorities lower than the current priority, and the first value indicates that the first adjustment coefficient of the corresponding priority is not effective; otherwise, the priority coefficient of the first adjustment coefficient corresponding to other cases is a second value (e.g., 1), and the second value indicates that the first adjustment coefficient of the corresponding priority is effective. For example, if the influencing factors of the first priority meet the triggering condition, then the first adjustment coefficients corresponding to the second and third priorities are not effective.

[0095] Optionally, for the above-mentioned influencing factors, the priorities include a first priority P_1, a second priority P_2, and a third priority P_3, where the first priority is the highest and the third priority is the lowest. The first priority is the proxy state, and its triggering conditions include the proxy state being a pending instruction or a proxy keep-alive connection abnormality. The second priority is battery information, and its triggering conditions include the battery information being within a preset low battery range. The third priority and its triggering conditions include influencing factors other than the first and second priorities, such as time context, device usage information, and password expiration information. In some application scenarios, the first adjustment coefficient corresponding to the influencing factors of each priority can be used to determine whether the triggering conditions are met. For example, if the first adjustment coefficient F_proxy for the proxy state is not 1, it indicates that the proxy state is a pending instruction or a proxy keep-alive connection abnormality, and the first priority meets the triggering conditions.

[0096] For example, the base cycle is adjusted using the first adjustment coefficient and the priority of each influencing factor to obtain the second cycle of the smart device, as follows: T_next=T_base*(P_1*F_proxy)*(P_2*F_battery)*(P_3*F_time*F_habit*F_key).

[0097] Where T_next represents the second period, T_base represents the base period, F_xxx represents the first adjustment coefficient corresponding to each influencing factor, and P_1, P_2, and P_3 represent the priority coefficients corresponding to the first adjustment coefficients of the first, second, and third priority influencing factors, respectively, indicating whether the corresponding first adjustment coefficients are effective. Specifically, F_proxy is the first adjustment coefficient corresponding to the proxy state, F_battery is the first adjustment coefficient corresponding to the battery information, F_time is the first adjustment coefficient corresponding to the time context, F_habit is the first adjustment coefficient corresponding to the device usage information, and F_key is the first adjustment coefficient corresponding to the password expiration information.

[0098] For example, in response to the first adjustment coefficient F_proxy≠1 of the proxy state, indicating that the first priority proxy state meets the triggering condition, the first adjustment coefficients corresponding to the second and third priorities are not effective and are set to the first value (such as 0). In addition, the priority coefficient of the first adjustment coefficient of the proxy state is the second value (such as 1), that is, the priority coefficient P_1 corresponding to the first priority is 1, the priority coefficient P_2 corresponding to the second priority is 0, and the priority coefficient P_3 corresponding to the third priority is 0.

[0099] For example, in response to the first adjustment coefficient F_proxy = 1 for the proxy state and the first adjustment coefficient F_battery ≠ 1 for the battery information, indicating that the proxy state of the first priority does not meet the triggering condition and the battery information of the second priority meets the triggering condition, then the priority coefficient P_1 corresponding to the first priority is 1, the priority coefficient P_2 corresponding to the second priority is 1, and the priority coefficient P_3 corresponding to the third priority is 0.

[0100] For example, in response to the first adjustment coefficient F_proxy = 1 for the proxy state and the first adjustment coefficient F_battery = 1 for the battery information, indicating that the first priority proxy state does not meet the trigger condition and the second priority battery information does not meet the trigger condition, the priority coefficient P_1 corresponding to the first priority is 1, the priority coefficient P_2 corresponding to the second priority is 1, and the priority coefficient P_3 corresponding to the third priority is 1.

[0101] In some application scenarios, the specific process of adjusting the second period using the influencing factors of the second situation to obtain the adjusted second period for the above-mentioned intelligent device can refer to the process of determining the second period described above. For example, the influencing factors of the second situation can be used as the influencing factors mentioned above, and the second period can be used as the base period mentioned above. Specifically, the adjusted second period can be obtained by adjusting the second period using the influencing factors of the second situation as described above. This application will not elaborate further here.

[0102] The above solution dynamically adjusts the TWT cycle through various influencing factors, increases the wake-up frequency near potential usage times to ensure low latency, and minimizes power consumption during idle periods, thus achieving intelligent energy management.

[0103] In some embodiments, please refer to Figure 7 , Figure 7 This is a flowchart illustrating the fifth embodiment of the keep-alive control method for intelligent devices according to this application. This embodiment is applied to a cloud platform, and the method may include the following steps: S51: The cloud platform establishes a keep-alive connection with the router of the agent smart device, so that the smart device and the router can implement the above-mentioned keep-alive control method for smart devices.

[0104] In this process, the smart device switches from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the associated router. The current wake-up time is determined based on the first cycle. The smart device and the router negotiate the cycle to determine the second cycle of the smart device. The second cycle is used to determine the next wake-up time after the smart device switches to low-power mode.

[0105] This step can be referred to the specific implementation process of the above embodiments, and will not be repeated here.

[0106] In some implementations, after step S51, at least one further step is included: S52: Receives operation instructions sent by the client and forwards them to the router so that the operation instructions are stored in the router as instructions to be forwarded. The operation instructions are the operation instructions of the target object on the smart device by the client.

[0107] Optionally, the cloud platform can connect to the client and receive operation commands sent by the client. These operation commands can be instructions from the target object to operate the smart device on the client. Taking a smart door lock as an example, the operation commands can be unlocking commands, locking commands, password issuance commands, etc. This application does not limit the types of operation commands. The cloud platform can then forward the operation commands to the router. The router stores the operation commands as instructions to be forwarded, so that they can be sent to the smart device for execution after the smart device establishes a communication connection with the router.

[0108] S53: Collects relevant information about the operation commands of smart devices on the client side, obtains the influencing factors collected by the cloud platform, and sends them to the router.

[0109] Optionally, the cloud platform can collect information related to the client's operation commands, such as the operation command itself, the time of the operation command, the number of operation commands, and the target object corresponding to the operation command. This application does not limit the information related to the operation commands. The cloud platform can determine the influencing factors collected by the cloud platform based on the information related to the operation commands and send the collected influencing factors to the router.

[0110] Optionally, information related to the operation instructions can be used as an influencing factor, or the influencing factors can be obtained by analyzing the information related to the operation instructions. This application does not impose any limitations on this.

[0111] It is understood that in the above method of specific implementation, the order in which each step is written does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0112] It is understood that the keep-alive control method for intelligent devices in this application can be executed by a computer device, which can be any device with processing capabilities, such as mobile devices, computers, servers, etc., and this application does not impose any restrictions on this. In some possible implementations, the keep-alive control method for intelligent devices can be implemented by the processor calling program instructions stored in memory.

[0113] Please see Figure 8 , Figure 8This is a schematic diagram of the structure of a computer device according to an embodiment of this application. The computer device 60 includes a memory 61 and a processor 62 coupled to each other. The memory 61 stores program instructions, and the processor 62 executes the program instructions to implement the steps of any of the above-described smart device keep-alive control methods. In a specific implementation scenario, the computer device 60 may include, but is not limited to, a microcomputer or a server. In addition, the computer device 60 may also include mobile devices such as laptops and tablets, which are not limited here.

[0114] In this embodiment, processor 62 can also be referred to as a CPU (Central Processing Unit). Processor 62 may be an integrated circuit chip with signal processing capabilities. Processor 62 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor, or processor 62 can be any conventional processor. Furthermore, processor 62 can be implemented using integrated circuit chips.

[0115] The methods described in the above embodiments can be implemented as computer programs; therefore, this application proposes a computer-readable storage medium. Please refer to [link to relevant documentation]. Figure 9 , Figure 9 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 70 stores program instructions 71 that can be executed by a processor. The program instructions 71 can be executed by the processor to implement the steps of the keep-alive control method for any of the above-described intelligent devices.

[0116] The computer-readable storage medium 70 in this embodiment includes: a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., which can store program instructions 71. Alternatively, it may be a server storing the program instructions 71. The server can send the stored program instructions 71 to other devices for execution, or it can execute the stored program instructions 71 itself.

[0117] This application also provides a computer program product comprising a computer program that, when executed by a processor, can implement the steps of the methods described in any of the foregoing embodiments. Specifically, the computer program product can be a software or program product containing a computer program, capable of running on a computing device or stored on any available medium.

[0118] In some embodiments, the functions or modules of the apparatus provided in this application can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments. For the sake of brevity, this application will not repeat the details here.

[0119] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to. For the sake of brevity, the present application will not repeat them here.

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

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

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

[0123] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application.

[0124] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, and thus stored in a computer-readable storage medium for execution by a computing device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Therefore, this application is not limited to any particular hardware and software combination.

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

Claims

1. A keep-alive control method for an intelligent device, characterized in that, include: The smart device switches from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the associated router. The router is used to proxy the smart device to maintain a keep-alive connection with the cloud platform. The current wake-up time is determined based on the first cycle. The smart device negotiates with the router periodically to determine a second period for the smart device. The second period is used to determine the next wake-up time after the smart device switches to low-power mode.

2. The method according to claim 1, characterized in that, The smart device negotiates periodically with the router to determine the second period of the smart device, including: The smart device and the router negotiate periodically using influencing factors to determine the second period of the smart device; wherein, the influencing factors include at least one of the following: influencing factors collected by the smart device, influencing factors collected by the cloud platform, and influencing factors collected by the router.

3. The method according to claim 2, characterized in that, The smart device and the router conduct periodic negotiations using influencing factors to determine the second period of the smart device, including: The router receives the second cycle of the smart device; wherein the second cycle is obtained by the router adjusting the base cycle using the influencing factors. Alternatively, the influencing factors collected by the smart device include a first part of influencing factors and a second part of influencing factors. The first part of influencing factors is sent to the router, while the second part is not sent to the router. The security requirements for the second part of influencing factors are higher than those for the first part. The smart device and the router use the influencing factors to periodically negotiate and determine the second period for the smart device, including: The router receives the second cycle of the smart device; wherein the second cycle is obtained by the router by adjusting the base cycle using the influencing factors of the first situation, and the influencing factors of the first situation include at least one of the following: the first part of the influencing factors collected by the smart device, the influencing factors collected by the cloud platform, and the influencing factors collected by the router. The second period is adjusted using the influencing factors of the second scenario to obtain the adjusted second period, and the adjusted second period is sent to the router; wherein, the influencing factors of the second scenario include: the second part of influencing factors collected by the smart device.

4. The method according to claim 1, characterized in that, Before the smart device switches from low-power mode to normal mode during the first cycle wake-up and establishes a communication connection with the associated router, the following steps are included: Establish an association connection with the router; Capability negotiation is performed with the router to confirm whether the router has keep-alive control capability, wherein the keep-alive control capability includes the ability to keep-alive connections and the ability to periodically negotiate. In response to the router having keep-alive control capability, the authentication information of the smart device is sent to the router, so that the router can use the authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform.

5. The method according to claim 4, characterized in that, Sending the authentication information of the smart device to the router, so that the router can use the authentication information to proxy the smart device to maintain a keep-alive connection with the cloud platform, includes: The authentication information of the smart device is encrypted to obtain encrypted authentication information; The encrypted authentication information is sent to the router so that after the router establishes a connection with the cloud platform, it uses the encrypted authentication information to proxy the smart device to complete the registration and establishes a keep-alive connection with the cloud platform according to the preset keep-alive strategy. And / or, after sending the authentication information of the smart device to the router so that the router can use the authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform, the following steps are included: The smart device and the router conduct an initial periodic negotiation to determine the initial period of the smart device, wherein the initial period is used to determine the first wake-up time after the smart device enters the low-power mode.

6. The method according to claim 1, characterized in that, After establishing a communication connection with the associated router, the following is included: Confirm the proxy keep-alive connection status between the associated router and the cloud platform: In response to the existence of a pending forwarding instruction issued by the cloud platform, receive and execute the pending forwarding instruction, and receive confirmation information from the router that the proxy keep-alive connection is normal after the pending forwarding instruction is completed; or, in response to the absence of a pending forwarding instruction issued by the cloud platform, receive confirmation information from the router that the proxy keep-alive connection is normal. And / or, after the smart device performs periodic negotiation with the router to determine the second period of the smart device, it includes: In response to completing the current wake-up task, the smart device switches from the normal mode to the low-power mode.

7. A keep-alive control method for an intelligent device, characterized in that, include: The router responds to the associated smart device switching from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the smart device. The router acts as an intermediary for the smart device to maintain a keep-alive connection with the cloud platform. The current wake-up time is determined based on a first cycle. The router and the smart device negotiate periodically to determine the second period of the smart device. The second period is used to determine the next wake-up time after the smart device switches to low power mode.

8. The method according to claim 7, characterized in that, The router and the smart device perform periodic negotiation to determine the second period of the smart device, including: The router and the smart device negotiate periodically using influencing factors to determine the second period of the smart device; wherein, the influencing factors include at least one of the following: influencing factors collected by the smart device, influencing factors collected by the cloud platform, and influencing factors collected by the router.

9. The method according to claim 8, characterized in that, The router and the smart device negotiate periodically using influencing factors to determine the second period of the smart device, including: The base cycle is adjusted using the aforementioned influencing factors to obtain the second cycle of the smart device, and the second cycle of the smart device is then sent to the smart device. Alternatively, the influencing factors collected by the smart device include a first part of influencing factors and a second part of influencing factors. The first part of influencing factors is sent to the router, while the second part is not sent to the router. The security requirements for the second part of influencing factors are higher than those for the first part. The router and the smart device use the influencing factors to periodically negotiate and determine the second period of the smart device, including: The base cycle is adjusted using the influencing factors of the first scenario to obtain the second cycle of the smart device, and the second cycle of the smart device is sent to the smart device; wherein, the influencing factors of the first scenario include at least one of the following: the first part of the influencing factors collected by the smart device, the influencing factors collected by the cloud platform, and the influencing factors collected by the router; The system receives an adjusted second period sent by the smart device; wherein the adjusted second period is obtained by the smart device adjusting the second period using the influencing factors of the second situation; wherein the influencing factors of the second situation include: a second part of influencing factors collected by the smart device.

10. The method according to claim 9, characterized in that, The second cycle of the smart device is obtained by adjusting the base cycle using the aforementioned influencing factors. And / or, adjusting the base cycle using the influencing factors of the first case to obtain the second cycle of the smart device includes: Determine the first adjustment factor for each influencing factor; The second cycle of the smart device is obtained by adjusting the base cycle using the first adjustment coefficient corresponding to each influencing factor; or, the second cycle of the smart device is obtained by adjusting the base cycle using the first adjustment coefficient corresponding to each influencing factor and the priority corresponding to each influencing factor.

11. The method according to claim 10, characterized in that, The determination of the first adjustment coefficient corresponding to each influencing factor includes: Based on the preset coefficients corresponding to each influencing factor, the first adjustment coefficient of each influencing factor is determined. And / or, the step of adjusting the base cycle using the first adjustment coefficient corresponding to each influencing factor and the priority corresponding to each influencing factor to obtain the second cycle of the smart device includes: Prioritize each influencing factor; Based on the priority of each influencing factor, the priority coefficient of the first adjustment coefficient is determined; Using the priority coefficient, the first adjustment coefficient of the influencing factor is adjusted to obtain the second adjustment coefficient; The second adjustment coefficient is used to adjust the base cycle to obtain the second cycle of the smart device.

12. The method according to claim 11, characterized in that, The priority coefficient indicates whether the first adjustment coefficient is effective; And / or, the determination of the priority coefficient of the first adjustment coefficient based on the priority of each influencing factor includes: In response to the current priority influencing factors meeting the triggering condition, the priority coefficient of the first adjustment coefficient corresponding to the low priority is determined as the first value, wherein the low priority includes priorities lower than the current priority, and the first value indicates that the first adjustment coefficient is not effective.

13. The method according to claim 11, characterized in that, The influencing factors include at least one of the following: proxy status, power information, time context, device usage information, and password validity information. The proxy status represents the keep-alive connection status between the router and the cloud platform. Each influencing factor has a preset coefficient. The priorities include a first priority, a second priority, and a third priority. The triggering conditions for the first priority include a proxy status indicating a pending forwarding instruction or an abnormal proxy keep-alive connection. The triggering condition for the second priority includes battery information falling within a preset low battery range. The triggering conditions for the third priority include influencing factors other than the first and second priorities; and / or, The process of determining the first adjustment coefficient for each influencing factor based on the preset coefficients corresponding to each influencing factor includes at least one of the following steps: In response to the proxy status being normal for proxy keep-alive connection, the corresponding first proxy coefficient is determined as the first adjustment coefficient; or, in response to the proxy status being pending forwarding instruction or abnormal proxy keep-alive connection, the corresponding second proxy coefficient is determined as the first adjustment coefficient, wherein the first proxy coefficient is greater than the second proxy coefficient. In response to the fact that the power information belongs to a preset power range, a preset coefficient corresponding to the preset power range is determined as a first adjustment coefficient; In response to the time context belonging to a preset time period, the preset coefficient corresponding to the preset time period is determined to be the first adjustment coefficient, wherein the preset time period includes a first time period and a second time period, the first time period corresponds to the first time coefficient, the second time period corresponds to the second time coefficient, and the first time coefficient is less than the second time coefficient; In response to the device usage information characterizing the predicted usage probability of the current time period, a preset coefficient corresponding to the predicted usage probability of the current time period is determined as the first adjustment coefficient, wherein the predicted usage probability of the current time period is predicted using historical device usage information, and the preset coefficient is inversely proportional to the predicted usage probability; In response to the password expiration information falling within a preset near-expiration range, a corresponding first expiration coefficient is determined as a first adjustment coefficient; or, in response to the password expiration information not falling within a preset near-expiration range, a corresponding second expiration coefficient is determined as a first adjustment coefficient, wherein the first expiration coefficient is less than the second expiration coefficient.

14. The method according to claim 7, characterized in that, Before establishing a communication connection with the smart device, the following steps are included: Establish an association connection with the aforementioned smart device; The router performs capability negotiation with the smart device to confirm whether it has keep-alive control capability, wherein the keep-alive control capability includes the ability to keep-alive connections and the ability to periodically negotiate. In response to the router having keep-alive control capability, it receives authentication information sent by the smart device and uses the authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform.

15. The method according to claim 14, characterized in that, The step of receiving authentication information sent by the smart device and using the authentication information to proxy the smart device to maintain a keep-alive connection with the cloud platform includes: The system receives encrypted authentication information sent by the smart device, wherein the encrypted authentication information is obtained by the smart device encrypting the authentication information. The router establishes a connection with the cloud platform, uses the encrypted authentication information to proxy the smart device to complete the registration, and maintains a connection with the cloud platform according to a preset keep-alive strategy. And / or, after receiving the authentication information sent by the smart device and using the authentication information to proxy the smart device to establish a keep-alive connection with the cloud platform, the following steps are included: The router and the smart device conduct an initial period negotiation to determine the initial period of the smart device, wherein the initial period is used to determine the first wake-up time after the smart device enters low power mode.

16. A keep-alive control method for an intelligent device, characterized in that, include: The cloud platform establishes a keep-alive connection with the router of the agent smart device, so that the smart device and the router can implement the keep-alive control method of the smart device according to any one of claims 1 to 15; The smart device switches from low-power mode to normal mode at the current wake-up time and establishes a communication connection with the associated router. The current wake-up time is determined based on a first cycle. The smart device negotiates with the router to determine a second cycle, which is used to determine the next wake-up time after the smart device switches to low-power mode.

17. The method according to claim 16, characterized in that, It also includes at least one of the following steps: The system receives operation instructions sent by the client and forwards them to the router, so that the operation instructions are stored in the router as instructions to be forwarded, wherein the operation instructions are operation instructions of the target object on the smart device by the client. Information related to the operation commands given to the smart device by the client is collected, and the influencing factors collected by the cloud platform are obtained and sent to the router.

18. A keep-alive control system for an intelligent device, characterized in that, include: A smart device, a router, and a cloud platform, wherein the combination of the smart device, the router, and the cloud platform is used to implement the keep-alive control method for the smart device according to any one of claims 1 to 17.

Images