Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. An application heartbeat period adjusting method, comprising: acquiring a heartbeat type and a first heartbeat period of a first application in response to determining that the first application is not in an application whitelist; determining, in response to the heartbeat type of the first application being a heartbeat type that needs an adjustment, and further in response to determining, according to the first heartbeat period of the first application, that a number of times the first application wakes up a system within a preset period is greater than a preset times threshold, that the first heartbeat period of the first application needs to be adjusted; obtaining, according to an identifier of the first application, the first heartbeat period of the first application, wherein the acquiring the heartbeat type and the first heartbeat period and the determining that the first heartbeat period needs to be adjusted are performed before the obtaining the first heartbeat period of the first application; adjusting the first heartbeat period of the first application to a second heartbeat period according to a preset trigger heartbeat period, wherein the first heartbeat period is an original heartbeat period of the first application, the second heartbeat period is a heartbeat period, which is adjusted according to the preset trigger heartbeat period, of the first application; obtaining, according to an identifier of a second application, a third heartbeat period of the second application; and adjusting the third heartbeat period of the second application to a fourth heartbeat period according to the preset trigger heartbeat period, wherein the third heartbeat period is an original heartbeat period of the second application, the fourth heartbeat period is a heartbeat period, which is adjusted according to the preset trigger heartbeat period, of the second application, the preset trigger heartbeat period is an adjustment period according to which the first or third heartbeat period is adjusted, and the fourth heartbeat period is a multiple of the second heartbeat period.
This invention relates to a method for dynamically adjusting application heartbeat periods in a computing system to reduce unnecessary system wake-ups and improve energy efficiency. The method addresses the problem of applications frequently waking up the system with heartbeat signals, which can drain power and degrade performance, especially in battery-powered devices. The method first identifies a first application not in a predefined whitelist and acquires its heartbeat type and original heartbeat period. If the heartbeat type requires adjustment and the application's wake-up frequency exceeds a preset threshold within a given timeframe, the method determines that the heartbeat period needs modification. The original heartbeat period is then adjusted to a new period based on a predefined trigger heartbeat period. Additionally, the method retrieves the heartbeat period of a second application and adjusts it similarly, ensuring the new period is a multiple of the first application's adjusted period. This synchronization helps maintain system stability while minimizing wake-up events. The approach ensures that only applications with excessive wake-up activity are adjusted, preserving system responsiveness while conserving energy.
4. The method according to claim 1 , wherein before it is determined that the first application is not in the application whitelist, the method comprises presetting the application whitelist, wherein the application whitelist comprises an identifier of an application on which it is determined, according to an application attribute, that the heartbeat period adjustment does not need to be performed.
This invention relates to a method for managing application heartbeat periods in a computing system, specifically addressing the problem of unnecessary or inefficient heartbeat adjustments that can degrade system performance. The method involves dynamically adjusting the heartbeat period of applications based on whether they are listed in a predefined application whitelist. The whitelist contains identifiers of applications that do not require heartbeat period adjustments, as determined by their attributes. Before checking if an application is on the whitelist, the system presets this whitelist, ensuring that only applications not listed undergo heartbeat period adjustments. This selective approach optimizes system resources by avoiding unnecessary adjustments for whitelisted applications, thereby improving overall efficiency and performance. The method ensures that heartbeat monitoring remains effective while minimizing computational overhead. The whitelist is populated based on application attributes, allowing for flexible and adaptive management of heartbeat intervals. This solution is particularly useful in environments where multiple applications operate, and frequent heartbeat adjustments could lead to inefficiencies. By presetting the whitelist, the system can quickly determine which applications require adjustments, streamlining the process and reducing unnecessary processing. The method enhances system stability and responsiveness by focusing adjustments only on applications that need them.
5. The method according to claim 1 , wherein acquiring the heartbeat type and the first heartbeat period of the first application comprises acquiring the heartbeat type and the first heartbeat period of the first application according to an alarm configuration file of the first application.
This invention relates to monitoring and managing application heartbeats in a computing system. The problem addressed is the need to efficiently track and configure heartbeat signals from applications to ensure system health and performance. Heartbeats are periodic signals sent by applications to indicate they are running correctly, but managing these signals can be resource-intensive if not properly configured. The invention provides a method for acquiring and processing heartbeat information from applications. Specifically, it involves determining the type and period of a heartbeat signal from a first application by referencing an alarm configuration file associated with that application. The alarm configuration file contains predefined settings that specify the heartbeat type (e.g., periodic, event-based) and the interval (first heartbeat period) at which the heartbeat should be sent. This allows the system to dynamically adjust monitoring parameters based on the application's requirements, reducing unnecessary overhead and improving efficiency. The method ensures that heartbeat monitoring is tailored to each application's needs, optimizing system resources while maintaining reliable health checks. By using the alarm configuration file, the system avoids hardcoding heartbeat parameters, making it more flexible and adaptable to different applications. This approach is particularly useful in large-scale systems where multiple applications with varying heartbeat requirements must be monitored.
7. A terminal, comprising: a processor; and a computer-readable storage medium storing a program to be executed by the processor, the program including instructions for: acquiring a heartbeat type and a first heartbeat period of a first application in response to determining that the first application is not in an application whitelist; determining, in response to the heartbeat type of the first application being a heartbeat type that needs an adjustment, and further in response to determining, according to the first heartbeat period of the first application, that a number of times the first application wakes up a system within a preset period is greater than a preset times threshold, that the first heartbeat period of the first application needs to be adjusted; obtaining, according to an identifier of the first application, the first heartbeat period of the first application, wherein the instructions for acquiring the heartbeat type and the first heartbeat period and instructions for determining that the first heartbeat period needs to be adjusted are executed before the instructions for obtaining the first heartbeat period of the first application; adjusting the first heartbeat period of the first application to a second heartbeat period according to a preset trigger heartbeat period, wherein the first heartbeat period is an original heartbeat period of the first application, the second heartbeat period is a heartbeat period, which is adjusted according to the preset trigger heartbeat period, of the first application; obtaining, according to an identifier of a second application, a third heartbeat period of the second application; and adjusting the third heartbeat period of the second application to a fourth heartbeat period according to the preset trigger heartbeat period, wherein the third heartbeat period is an original heartbeat period of the second application, the fourth heartbeat period is a heartbeat period, which is adjusted according to the preset trigger heartbeat period, of the second application, the preset trigger heartbeat period is an adjustment period according to which the first or third heartbeat period is adjusted, and the fourth heartbeat period is a multiple of the second heartbeat period.
This invention relates to power management in mobile devices, specifically optimizing application heartbeat intervals to reduce unnecessary system wake-ups. The problem addressed is excessive battery drain caused by applications frequently waking the system for periodic tasks (heartbeats) without user interaction. The solution involves dynamically adjusting heartbeat periods for non-whitelisted applications based on their wake-up frequency. The system includes a processor and storage medium with instructions to monitor applications not in a trusted whitelist. For each monitored application, it acquires the heartbeat type and original period. If the heartbeat type requires adjustment and the application wakes the system too frequently (exceeding a preset threshold within a given time), the system modifies the heartbeat period. The adjustment uses a preset trigger period, extending the original period to a longer, optimized interval. This adjustment applies to multiple applications, with each new period being a multiple of the trigger period. The process ensures only necessary wake-ups occur, conserving battery life while maintaining application functionality. The system first analyzes heartbeat patterns before applying adjustments, ensuring only problematic applications are modified.
10. The terminal according to claim 7 , wherein before it is determined that the first application is not in the application whitelist, the program further includes instructions for: presetting the application whitelist, wherein the application whitelist comprises an identifier of an application on which it is determined, according to an application attribute, that the heartbeat period adjustment does not need to be performed.
This invention relates to a terminal device configured to manage application heartbeat periods to optimize power consumption and network efficiency. The problem addressed is the unnecessary power and bandwidth usage caused by frequent heartbeat transmissions from applications that do not require real-time synchronization. The solution involves dynamically adjusting heartbeat intervals based on whether an application is listed in a predefined whitelist, which contains applications that do not need heartbeat period adjustments. The terminal includes a processor and memory storing executable instructions. The instructions enable the terminal to monitor applications running on the device and determine whether each application should have its heartbeat period adjusted. Before making this determination, the terminal presets an application whitelist containing identifiers of applications that, based on their attributes, do not require heartbeat period adjustments. The whitelist ensures that only non-whitelisted applications undergo heartbeat interval modifications, reducing unnecessary processing and communication overhead. The terminal checks if an application is in the whitelist before deciding whether to adjust its heartbeat period, thereby optimizing resource usage while maintaining functionality for critical applications. This approach improves battery life and network efficiency by minimizing redundant transmissions.
11. The terminal according to claim 7 , wherein the program further includes instructions for: acquiring the heartbeat type and the first heartbeat period of the first application according to an alarm configuration file of the first application.
A system and method for managing application heartbeat monitoring in a terminal device addresses the challenge of efficiently tracking application health and performance. The invention provides a terminal device with a program that monitors application heartbeat signals to detect and respond to application malfunctions or failures. The program includes instructions for acquiring the heartbeat type and the first heartbeat period of a first application based on an alarm configuration file specific to that application. This configuration file defines the expected heartbeat behavior, including the type of heartbeat signal (e.g., periodic, event-based) and the interval at which the heartbeat should occur. The terminal device uses this information to verify the application's operational status, ensuring timely detection of anomalies. The system may also include additional features such as generating alerts, restarting the application, or logging errors when heartbeat signals deviate from the expected pattern. By dynamically adjusting monitoring parameters based on application-specific configurations, the invention improves reliability and reduces unnecessary resource consumption. The solution is particularly useful in environments where multiple applications with varying heartbeat requirements must be monitored simultaneously.
Unknown
February 4, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.