Power consumption control method and device, terminal equipment and storage medium

Abstract

Embodiments of the present application disclose a power consumption control method and device, a terminal device and a storage medium, which are used for performing power consumption control on a foreground application according to a low-power mode when target data of the terminal device meets a preset trigger condition, so as to reduce power consumption of the foreground application, and thus low-power control of the foreground application can be implemented. The method comprises the following steps: monitoring target data of a terminal device, wherein the target data comprises at least one of current system state data and usage scenario data of a foreground application; and performing power consumption control on the foreground application according to a low-power mode when the target data meets a preset trigger condition, so as to reduce power consumption of the foreground application.

Description

Technical Field

[0001] This application relates to the field of terminal devices, and more particularly to a power consumption control method, apparatus, terminal device, and storage medium. Background Technology

[0002] When a device enters a low-battery state or when the user wants the device to enter a power-saving state, power saving mode / ultra-power saving mode can be activated to save power and achieve a longer battery life. However, the current mode can only adjust and optimize general power consumption items for all scenarios of the device, and cannot perform targeted power control. Summary of the Invention

[0003] This application provides a power consumption control method, apparatus, terminal device, and storage medium, which are used to control the power consumption of the foreground application according to a low power consumption mode when the target data of the terminal device meets the preset trigger conditions, so as to reduce the power consumption of the foreground application and thus achieve low power consumption control of the foreground application.

[0004] The first aspect of this application provides a power consumption control method, which may include:

[0005] The target data of the monitoring terminal device includes at least one of the current system status data and the usage scenario data of the foreground application.

[0006] When the target data meets the preset triggering conditions, power consumption control is performed on the foreground application according to the low power mode to reduce the power consumption of the foreground application.

[0007] A second aspect of this application provides a power consumption control device, which may include:

[0008] The monitoring module is used to monitor target data of the terminal device, wherein the target data includes at least one of the current system status data and the usage scenario data of the foreground application;

[0009] The processing module is used to control the power consumption of the foreground application according to a low-power mode when the target data meets the preset trigger conditions, so as to reduce the power consumption of the foreground application.

[0010] A third aspect of this application provides a terminal device that may include a memory, a processor, and a transceiver. The memory stores a computer program that can run on the processor, and the terminal device executes the program to implement the method described in the first aspect of this application.

[0011] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the method described in the first aspect of this application.

[0012] Another aspect of this application discloses a computer program product that, when run on a computer, causes the computer to execute the method described in the first aspect of this application.

[0013] Another aspect of this application discloses an application publishing platform for publishing computer program products, wherein when the computer program product is run on a computer, the computer executes the method described in the first aspect of this application.

[0014] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0015] In this embodiment, target data of the terminal device can be monitored. The target data includes at least one of current system status data and usage scenario data of the foreground application. When the target data meets a preset trigger condition, power consumption control is performed on the foreground application according to a low-power mode to reduce its power consumption. This allows for low-power control of the foreground application. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments and the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application, and other drawings can be obtained based on these drawings.

[0017] Figure 1 This is a schematic diagram of one embodiment of the power consumption control method in this application;

[0018] Figure 2 This is a schematic diagram illustrating the activation of the long video playback mode in an embodiment of this application;

[0019] Figure 3A This is a schematic diagram illustrating the display of the prompt information via a floating window in an embodiment of this application;

[0020] Figure 3B This is a schematic diagram illustrating the display of the notification information via the notification bar in an embodiment of this application;

[0021] Figure 3C This is a schematic diagram of the overall process of the power consumption control method in the embodiments of this application;

[0022] Figure 4 This is a schematic diagram of one embodiment of the power consumption control device in this application.

[0023] Figure 5 This is a schematic diagram of one embodiment of the terminal device in this application;

[0024] Figure 6 This is a schematic diagram of another embodiment of the terminal device in this application. Detailed Implementation

[0025] This application provides a power consumption control method, apparatus, terminal device, and storage medium, which are used to control the power consumption of the foreground application according to a low power consumption mode when the target data of the terminal device meets the preset trigger conditions, so as to reduce the power consumption of the foreground application and thus achieve low power consumption control of the foreground application.

[0026] To enable those skilled in the art to better understand the present application, the technical solutions of the embodiments of the present application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. All embodiments based on the present application should fall within the scope of protection of the present application.

[0027] The following is a brief explanation of some of the terms used in this application:

[0028] Universal optimization across all scenarios: Universal optimization across all scenarios refers to unified power management for all usage scenarios of mobile devices. This may include measures such as reducing screen brightness, turning off unnecessary sensors, and reducing the operating frequency of the central processing unit (CPU). These optimizations apply to all usage scenarios of the device, but may not be optimized for specific applications or specific user behaviors.

[0029] Application-level optimization: Application-level optimization refers to power consumption optimization for specific applications. For example, for a video playback application, the decoding process can be optimized, the resolution reduced, or the buffering strategy adjusted to reduce power consumption. This type of optimization is more refined because it takes into account the specific needs and behaviors of the application.

[0030] Activity-level optimization: Activity-level optimization refers to power consumption optimization for specific user interface activities in Android application development. For example, when a user is watching a video, the system can automatically turn off the screen or reduce CPU performance to reduce energy consumption. This optimization requires a deep understanding of the application's specific use cases and the ability to dynamically adjust power consumption strategies based on user behavior.

[0031] Power Saving Mode: Power saving mode is an operating mode that reduces battery consumption by adjusting the settings and functions of a terminal device. When power saving mode is enabled, the terminal device will typically reduce screen brightness, limit background application activity, and disable unnecessary functions, thereby effectively extending battery life. This mode is suitable for use when the battery is low but the terminal device still needs to be used, as it can reduce battery consumption without significantly affecting the user experience.

[0032] Ultra Power Saving Mode: Also known as Extreme Power Saving Mode or Ultra Power Saving Mode, this is a feature on mobile devices designed to minimize battery consumption. Users can enable this mode when their phone's battery level drops below a certain point to extend device usage time. This mode limits background app activity, reduces screen brightness, disables unnecessary features such as Wi-Fi, Bluetooth, and GPS, and may only allow a few critical apps to run. In Ultra Power Saving Mode, the phone may switch to a simplified interface, reducing visual effects and animations to further reduce battery consumption.

[0033] "Long-lasting playback mode" or "video playback extended battery life mode" refers to a mode on mobile devices, especially smartphones, that optimizes video playback to extend battery life. This mode extends device usage time by reducing power consumption during video playback, but may sacrifice some video quality or playback experience.

[0034] In some implementations, when a terminal device enters a low-battery state or when the user wants the device to enter a power-saving state, power saving mode / ultra-power saving mode can be activated to save power and achieve a longer battery life. However, the current mode can only adjust and optimize general power consumption items for all scenarios of the terminal device, and cannot achieve fine-grained power consumption adjustment at the application level or even the activity scene level. Moreover, the power consumption control items in the current mode require manual activation or confirmation by the user to adjust and optimize, which cannot achieve intelligent and seamless operation, thus affecting the user experience.

[0035] In this technical solution, when the target data of the terminal device (including at least one of the current system status data and the usage scenario data of the foreground application) meets the preset triggering conditions, the power consumption of the foreground application is controlled according to the low power mode. Since the power consumption of the low power mode is less than that of the non-low power mode, the low power consumption of the foreground application can be controlled.

[0036] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0037] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0038] The technical solution of this application will be further described below by way of embodiments, such as... Figure 1 The diagram shown is a schematic representation of an embodiment of the power consumption control method in this application, which may include:

[0039] 101. Monitor target data of terminal devices, including at least one of the following: current system status data and usage scenario data of foreground applications.

[0040] Optionally, in some possible implementations, the current system status data includes at least one of the following: the charging status of the terminal device, the current remaining battery power, the current temperature, the foreground application, the on / off status of the first power-saving mode, and the on / off status of the second power-saving mode, wherein the power-saving degree of the second power-saving mode is greater than that of the first power-saving mode.

[0041] Optionally, in some possible implementations, the usage scenario data of the foreground application includes: the usage duration of the foreground application, the screen usage status of the foreground application, and the on / off status of the low-power mode of the foreground application.

[0042] For example, the terminal device can monitor the current system status data and the usage scenario data of the foreground application in real time. The usage scenario data of the target application can also be referred to as user usage scenario data. Combined with the current system status data, the device can intelligently identify the degree of demand for low-power mode under the current user's usage habits, thereby triggering different levels of low-power strategy conditions. Low-power strategy conditions can also be referred to as preset trigger conditions.

[0043] Terminal devices can monitor current system status data in real time, including: the terminal device can monitor the charging status, that is, whether the terminal device is currently charging or not; it can also monitor the current remaining battery power, foreground applications, current temperature and other system status; it can also monitor the on / off status of low power saving modes such as the first power saving mode and the second power saving mode (also known as the super power saving mode).

[0044] The terminal device can monitor the usage scenario data of the foreground application in real time. This data can include: recording the user's usage time for the foreground application, which can be understood as the user's usage time within a given day. For example, "day" could be from midnight of the current day to midnight of the next day, or from 6 AM of the current day to 6 AM of the next day, etc. After 24 hours, the user's usage time is reset to zero, and the monitoring starts again. It can also include the screen usage status of the foreground application, such as full-screen, floating window, or split-screen states. Furthermore, it can include the on / off status of the foreground application's low-power mode. For example, it can read whether the user has enabled the low-power mode switch (e.g., long refresh mode, or video long battery life mode) for the foreground application. If it is enabled, the low-power mode is on; if not, it is off. Another example: if the video long battery life mode switch is on, it can check whether the foreground application is a specific application for which the video long battery life mode is active. If so, the video long battery life mode is enabled for the foreground application.

[0045] Optionally, the target data for monitoring the terminal device may include: the terminal device monitoring the current system status data through the system monitoring module; and / or, monitoring the usage scenario data of the foreground application through the scenario monitoring module.

[0046] This technical solution provides further explanation of the current system status data and the usage scenario data of the target application, thereby providing a more accurate understanding of the current system status data and the usage scenario data of the target application and improving the feasibility of the solution.

[0047] Optionally, in some possible implementations, the method may further include: displaying a first settings interface, the first settings interface including a first switch control for a first power-saving mode; when the first power-saving mode is in a closed state, responding to an open operation of the first switch control to enable the first power-saving mode; when the first power-saving mode is in a closed state, responding to a close operation of the first switch control to disable the first power-saving mode.

[0048] Optionally, in some possible implementations, the method may further include: displaying a second settings interface, the second settings interface including a second switch control for the second power-saving mode; when the second power-saving mode is in a closed state, responding to an open operation of the second switch control to enable the second power-saving mode; when the second power-saving mode is in a closed state, responding to a close operation of the second switch control to disable the second power-saving mode.

[0049] Optionally, in some possible implementations, the method may further include: displaying a third settings interface, the third settings interface including a third switch control for low power mode; when low power mode is in the off state, responding to an open operation of the third switch control to enable low power mode; when low power mode is in the on state, responding to a close operation of the third switch control to disable low power mode.

[0050] For example, the first power-saving mode can be a power-saving mode, the second power-saving mode can be a super power-saving mode, and the low-power mode can be a video long-lasting mode, a long-refreshing mode, or other low-power modes; this application does not make any specific limitations. The first and second power-saving modes are mainly applied to the power-saving modes of the entire system on the terminal device. The low-power mode, on the other hand, is mainly applied to the power consumption mode of the foreground application.

[0051] For example, in the System Settings—Battery—Power Saving Settings interface, there are toggle options for Power Saving Mode, Ultra Power Saving Mode, and Video Long Battery Life Mode, allowing users to turn these modes on and off. Alternatively, these toggle options can also be found in the drop-down menu.

[0052] For example, in the System Settings—Battery—Power Saving Settings interface, a toggle option for a video long battery life mode is provided, along with a text prompt informing the user that this function aims to save power and may result in a slight loss of video quality. Figure 2 The image shown is a schematic diagram illustrating the activation of the long video playback mode in an embodiment of this application.

[0053] In this technical solution, an interactive implementation scheme is provided for enabling and disabling the first power-saving mode, the second power-saving mode, and the low-power mode, thereby improving the feasibility of the solution.

[0054] Optionally, in some possible implementations, the screen usage state of the target application may include full-screen usage state, split-screen usage state, or floating window usage state.

[0055] Full-screen mode refers to an application occupying the entire display screen, preventing the user from seeing or interacting with other applications. In full-screen mode, the video or application fills the entire screen, providing an immersive experience. For example, in a video application, a user can enter full-screen mode by clicking the full-screen button on the video playback screen to gain a larger field of view and a better viewing experience.

[0056] Split-screen mode allows users to use two or more applications simultaneously, each occupying a portion of the screen. This mode is suitable for multitasking, allowing users to view and operate multiple applications on one screen at a time. For example, some mobile operating systems offer split-screen functionality, allowing users to enable split-screen multitasking in settings and then activate split-screen mode via specific gestures or buttons.

[0057] Floating window usage, also known as floating window playback, refers to an application displaying itself as a small window on the screen, allowing users to operate other applications while watching videos or making video calls. This mode provides flexibility, allowing users to freely switch to other tasks while keeping the video playing. For example, in a video application, a user can launch floating window playback by clicking the small window play icon on the video playback interface. The video will then float on the screen as a small window, allowing the user to continue using other functions of the phone.

[0058] In this technical solution, full-screen mode provides an immersive experience, split-screen mode allows for multitasking, and floating window mode offers flexibility, allowing users to perform other operations while viewing content. These different screen usage modes can be selected and switched according to the user's needs and preferences.

[0059] Optionally, in some possible implementations, the foreground application includes the target application, and monitoring the target data of the terminal device may include: monitoring the target data of the terminal device when the target application is detected to be launched, wherein the target application belongs to an application in a preset whitelist.

[0060] For example, the target application is an application in a preset whitelist. Generally speaking, applications in the preset whitelist are applications with high power consumption, such as applications mainly used to play multimedia resources.

[0061] In this technical solution, target data of the terminal device will only be monitored if the target application is in the preset whitelist and the target application is detected to be running. Since the target application is a high-power application, monitoring the target data of the terminal device facilitates low-power control, thereby improving the battery life of the terminal device.

[0062] 102. When the target data meets the preset trigger conditions, power consumption control is performed on the foreground application according to the low power mode to reduce the power consumption of the foreground application.

[0063] Optionally, in some possible implementations, the preset triggering conditions include at least one of the following: the current remaining battery power is less than the battery power threshold, the current temperature is greater than the temperature threshold, the foreground application is an application in a preset whitelist, the first power saving mode is enabled, the second power saving mode is enabled, the current temperature of the terminal device is greater than the temperature threshold, the usage time is greater than the duration threshold, and the low power mode of the foreground application is enabled, and / or the terminal device is in a non-charging state.

[0064] For example, if the terminal device is not charging, there is a need to conserve power and extend its battery life because the terminal device is not charging. If the terminal device is charging, there is no worry about running out of power. And / or, if the terminal device meets at least one of the following conditions, the target data can be considered to meet the preset trigger conditions: the current remaining power is less than the power threshold, the current temperature is greater than the temperature threshold, the foreground application is in a preset whitelist, the power saving mode is enabled, the super power saving mode is enabled, the current temperature of the terminal device is greater than the temperature threshold, the usage time is greater than the duration threshold, and the low power mode of the foreground application is enabled.

[0065] In this technical solution, the preset triggering conditions for the target data are specifically explained, which improves the feasibility of the solution.

[0066] Optionally, in some possible implementations, the preset trigger condition is obtained from the server, or it is preset in the terminal device.

[0067] In this technical solution, the preset trigger conditions can be obtained from the server or preset in the terminal device. If preset in the terminal device, the local storage space requirement of the terminal device will be higher. In this case, the target data can be directly compared with the preset trigger conditions to see if they are met. If obtained from the server, the communication requirements between the terminal device and the server are higher. The preset trigger conditions need to be obtained from the server first, and then the target data needs to be compared with the preset trigger conditions to see if they are met. Providing a detailed explanation of the different methods of obtaining the preset trigger conditions improves the feasibility of the solution.

[0068] Optionally, in some possible implementations, power control of the foreground application based on the low-power mode may include: power control of the interface activity scenarios of the foreground application based on the low-power mode.

[0069] For example, at least one of the current system status data and the usage scenario data of the foreground application can be judged. If at least one of the current system status data and the usage scenario data of the foreground application meets the preset triggering conditions, power consumption control can be performed on the interface activity scenario in the foreground application according to the low power mode to improve the battery life of the terminal device.

[0070] In this technical solution, when the target data of the terminal device meets the preset triggering conditions, power consumption control is performed on the interface activity scene of the foreground application according to the low power mode to reduce the power consumption of the foreground application. Therefore, low power consumption control of the interface activity scene of the foreground application can be achieved, thereby improving the battery life of the terminal device.

[0071] Optionally, in some possible implementations, power control of the foreground application based on the low-power mode may include: power control of the foreground application based on the low-power mode and the target power optimization policy, with preset trigger conditions corresponding to the target power optimization policy.

[0072] Optionally, in some possible implementations, the target optimization strategy is obtained from the server or pre-configured in the terminal device. The target power consumption optimization strategy can be obtained from the server or pre-configured in the terminal device; this application does not specifically limit this. The target power consumption optimization strategy is an optimization strategy set by the terminal device or server according to the product definition.

[0073] If the target power optimization policy is obtained from the server, and the target data meets the preset trigger conditions, the power optimization policy is obtained from the server. Based on the target power optimization policy and the low power mode, the power consumption of the foreground application is controlled to reduce the power consumption of the foreground application, thus achieving low power control of the foreground application.

[0074] If the target power consumption optimization policy is preset in the terminal device, and the target data meets the preset trigger conditions, it is not necessary to obtain the target power consumption optimization policy from the server. The power consumption of the foreground application can be controlled directly according to the preset target power consumption optimization policy and low power mode in the terminal device to reduce the power consumption of the foreground application, thus achieving low power consumption control of the foreground application.

[0075] In this technical solution, when the target data meets the preset trigger conditions, since the preset trigger conditions correspond to the target power consumption optimization strategy, the corresponding target power consumption optimization strategy can be matched according to the preset trigger conditions. Based on the low power mode and the target power consumption optimization strategy, the power consumption of the foreground application is controlled to reduce the power consumption of the foreground application. This can achieve low power consumption control of the foreground application, thereby improving the battery life of the terminal device.

[0076] Optionally, in some possible implementations, the method may also include: sending target data to the server; receiving the target power optimization policy from the server in response to the sending of the target data.

[0077] For example, after monitoring and obtaining target data, the terminal device can send the target data to the server. This target data can be used by the server to determine the target power consumption optimization strategy, and then the server sends the target power consumption optimization strategy to the terminal device. For instance, the terminal device can upload data points related to enabling low-power mode to the server for big data monitoring and analysis.

[0078] In this technical solution, target data is sent to the server. This target data is used by the server to determine the target power consumption optimization strategy. Therefore, the server can obtain the target power consumption optimization strategy in real time based on the reported target data, and then send the target power consumption optimization strategy to the terminal device. The terminal device controls the power consumption of the foreground application according to the low power mode and the specific target power consumption optimization strategy to reduce the power consumption of the foreground application. This can achieve low power consumption control of the foreground application, thereby improving the battery life of the terminal device.

[0079] Optionally, in some possible implementations, power control of the foreground application based on the low-power mode and the target power optimization strategy may include: power control of the interface activity scenarios of the foreground application based on the low-power mode and the target power optimization strategy.

[0080] In this technical solution, when the target data of the terminal device meets the preset triggering conditions, power consumption control is performed on the interface activity scene of the foreground application according to the low power mode and target power consumption optimization strategy to reduce the power consumption of the foreground application. Therefore, low power consumption control of the interface activity scene of the foreground application can be achieved, thereby improving the battery life of the terminal device.

[0081] Optionally, in some possible implementations, the foreground application includes the target application. Power consumption control for the interface activities of the foreground application may include: controlling the playback parameters of multimedia resources when playing multimedia resources through the target application, and / or performing system power consumption control.

[0082] For example, when playing multimedia resources through a target application, if the target data meets a preset trigger condition, the playback parameters of the multimedia resources are controlled according to a low-power mode, and / or system power consumption is controlled. Alternatively, when playing multimedia resources through a target application, if the target data meets a preset trigger condition, the playback parameters of the multimedia resources are controlled according to a low-power mode and a target power consumption optimization strategy, and / or system power consumption is controlled.

[0083] In this technical solution, when playing multimedia resources through a target application, if the target data meets preset trigger conditions, the playback parameters of the multimedia resources are controlled according to a low-power mode, or according to a low-power mode and a target power optimization strategy; or system power consumption is controlled; or both the playback parameters of the multimedia resources and system power consumption are controlled. A specific implementation method for power consumption control is provided to reduce the power consumption of the foreground application, thus improving the feasibility of the solution.

[0084] Optionally, in some possible implementations, the playback parameters include at least one of the following: screen brightness, volume, audio, sound effects, Bluetooth transmission rate, picture quality, video color, True Color Vision brightening curve, and Frame Rate Target Control (FRTC).

[0085] Optionally, in some possible implementations, system power consumption control is performed when playing multimedia resources through the target application, including at least one of the following:

[0086] The system suppresses dual-channel wireless fidelity networks, switches between GPS and network positioning, disables background data synchronization, closes background applications, and disables system haptic feedback.

[0087] For example, the terminal device controls the playback parameters of the target application's multimedia resources based on the low-power mode and target power optimization strategy. These parameters include: screen brightness adjustment, volume adjustment, audio adjustment (which can be holographic audio adjustment or spatial audio adjustment), sound effect adjustment (which can be understood as device sound effect adjustment), Bluetooth transmission rate adjustment (which can be understood as bitrate adjustment during Bluetooth connection), picture adjustment (which can be understood as adaptive picture enhancement adjustment), picture quality adjustment (which can be understood as ultra-high definition picture enhancement adjustment), video color adjustment (which can be understood as video color enhancement adjustment), True Color Vision brightening curve adjustment, and frame rate target control adjustment (which can be understood as frame rate target control FRTC frame compression adjustment).

[0088] Terminal devices control system power consumption based on low-power modes and target power optimization strategies, such as: dual-channel suppression of Wi-Fi networks, GPS positioning switching network positioning adjustment, disabling automatic background synchronization, freezing background applications (i.e., closing background applications), and disabling system touch sensing.

[0089] FRTC (Frame Rate Target Control) is a frame rate control technology that allows users to set a target maximum frame rate when running 3D applications in full-screen mode. This optimizes the performance and power consumption of the graphics processing unit (GPU) while ensuring a smooth and optimized gaming experience. With proper configuration, users can achieve better performance in different games and application scenarios.

[0090] This technical solution provides a detailed explanation of the playback parameters for controlling multimedia resources and the system power consumption control, and offers a specific implementation method for power consumption control, thereby improving the feasibility of the solution.

[0091] Optionally, in some possible implementations, the method may also include: notifying the foreground application to enter a low-power mode.

[0092] For example, depending on the foreground application, the foreground application is notified to enter a low-power mode via Cosa and Hyperboost.

[0093] In this technical solution, Cosa and Hyperboost can be used to notify the foreground application to enter low-power mode based on the low-power mode, thereby saving power consumption within the foreground application process.

[0094] Optionally, in some possible implementations, when the target data meets the preset trigger conditions, power control of the foreground application according to the low-power mode may include: when the target data meets the preset trigger conditions and the low-power mode is not activated, activating the low-power mode to obtain the low-power mode; and controlling the power consumption of the foreground application according to the low-power mode.

[0095] For example, when the target data meets preset trigger conditions, the terminal device can enter the low-power mode activation phase, i.e., the low-power mode activation stage. Before activating the low-power mode, the activation status of the low-power mode needs to be determined to avoid resource waste and system logic chaos caused by secondary activation. If the low-power mode is active, then power consumption control of the foreground application is performed directly according to the low-power mode; if the low-power mode is inactive, then the low-power mode is activated, and then power consumption control of the foreground application is performed according to the low-power mode.

[0096] In this technical solution, when the target data meets the preset triggering conditions, the activation status of the low-power mode needs to be determined before the terminal device activates the low-power mode to avoid resource waste and system logic chaos caused by secondary activation. If the low-power mode is not activated, it is then activated; power consumption of the foreground application is controlled according to the low-power mode to reduce the power consumption of the foreground application, thereby improving the battery life of the terminal device.

[0097] Optionally, in some possible implementations, when the target data meets the preset trigger conditions, power control of the foreground application based on the low-power mode may include: activating the low-power mode when the target data meets the preset trigger conditions and the low-power mode is not activated; and controlling power consumption for the interface activity scenarios of the foreground application based on the low-power mode.

[0098] For example, when the target data meets preset triggering conditions, the terminal device can enter the low-power mode activation phase, i.e., the low-power mode activation stage. Before activating the low-power mode, the activation status of the low-power mode needs to be determined to avoid resource waste and system logic chaos caused by secondary activation. If the low-power mode is in an active state, then power consumption control is performed directly on the interface activities of the foreground application based on the low-power mode; if the low-power mode is in an inactive state, then the low-power mode is activated, and then power consumption control is performed on the interface activities of the foreground application based on the low-power mode.

[0099] In this technical solution, when the target data meets the preset triggering conditions, before the terminal device activates the low-power mode, it is necessary to first determine the activation status of the low-power mode to avoid resource waste and system logic chaos caused by secondary activation. If the low-power mode is not activated, it is then activated; based on the interface activity scenario of the foreground application in the low-power mode, power consumption is controlled to reduce the power consumption of the foreground application, thereby improving the battery life of the terminal device.

[0100] Optionally, in some possible implementations, after activating the low-power mode, the method may also include: displaying a prompt message to inform the user that the low-power mode has been enabled.

[0101] For example, after low-power mode is enabled, a prompt message can be displayed on the screen to inform the user that low-power mode has been activated. For instance, this low-power mode could be a video long-lasting mode.

[0102] In this technical solution, if the low-power mode is enabled, a prompt message can be sent to the user to indicate that the low-power mode is enabled.

[0103] Optionally, in some possible implementations, displaying a prompt message may include:

[0104] Display a notification message via a floating window; and / or,

[0105] A notification message will be displayed in the notification bar.

[0106] For example, after low-power mode is enabled, a notification message can be displayed via a floating window; and / or via the notification bar. Figure 3A The image shown is a schematic diagram illustrating the display of prompt information via a floating window in an embodiment of this application. For example... Figure 3B The image shown is a schematic diagram illustrating the display of prompt information via a notification bar in an embodiment of this application.

[0107] For example: Utilize the system's Toast feature to display a 5-second floating window informing the user that low-power mode is enabled and power-saving optimizations are in progress. And / or, continuously display the notification in the notification bar pull-down menu, indicating that the system's low-power mode is currently enabled and power-saving optimizations are in progress.

[0108] In Android systems, using the system's Toast feature is a common operation to display a brief notification message on the screen. Here are the detailed steps on how to use the system's Toast feature:

[0109] (1) Import the Toast class: In the Java file, you first need to import the android.widget.Toast class.

[0110] (2) Create a Toast object: Use the Toast.makeText() method to create a Toast object and set the text content to be displayed and the display duration.

[0111] (3) Set the position of the Toast (optional): You can use the setGravity() method to set the position of the Toast display. By default, the Toast will be displayed in the center at the bottom of the screen. For example, you can set the Toast to be displayed at the top of the screen.

[0112] (4) Custom Toast: If you need a more complex custom Toast, you can use LayoutInflater to load a custom layout Toast.

[0113] The steps above demonstrate how to invoke the system's Toast feature in an Android application to display a notification message. Toast is a lightweight message notification method, suitable for displaying short messages, but not for complex interactions or content displayed for extended periods.

[0114] In this technical solution, the terminal device can display the prompt information separately through a floating window, or separately through the notification bar, or simultaneously through a floating window and the notification bar, to notify the user that the foreground application has entered a low-power mode.

[0115] Optionally, in some possible implementations, the number of foreground applications is at least one.

[0116] For example, a terminal device can simultaneously support the operation of multiple applications in the foreground, and multiple clients can manage each foreground application to achieve fine-grained power consumption control in complex scenarios, such as full-screen usage, floating window usage, or split-screen usage.

[0117] In this technical solution, the number of foreground applications is limited. The terminal device can support the operation of at least one application in the foreground. Regardless of the number of foreground applications, power consumption can be controlled to improve the battery life of the terminal device.

[0118] Optionally, in some possible implementations, the method also includes power consumption control through communication with the local service layer.

[0119] In Android, the Native layer is a layer in the system architecture located between the Java application layer and the operating system kernel. It is primarily responsible for interacting with hardware and providing efficient low-level services. The Native layer is based on the Linux kernel, which provides low-level hardware driver support and manages resources, including device drivers, memory management, network management, and power management. Optimizations in the Native layer include avoiding unnecessary memory allocation, using multithreading, optimizing algorithms, and optimizing system service calls to improve application performance and stability.

[0120] In this technical solution, the terminal device can establish a communication mechanism with the native service layer, enabling more layers of customization and optimization.

[0121] Optionally, in some possible implementations, when the target data meets the preset trigger conditions, power control of the foreground application according to the low-power mode may include: when the target data meets the preset trigger conditions, power control of the foreground application according to the low-power mode through a third-party platform.

[0122] In this technical solution, the terminal device can access the custom tuning capabilities provided by some third-party platforms and other systems, and provide them to third-party applications to build custom tuning capabilities exclusive to the third-party applications, thereby enabling power consumption control.

[0123] Optionally, in some possible implementations, when the target data meets the preset trigger conditions, power control of the foreground application according to the low-power mode may include: when the target data meets the preset trigger conditions, the controller performs power control of the foreground application according to the low-power mode.

[0124] In this technical solution, the terminal device can control the power consumption of the foreground application according to the low-power mode through a controller (also known as a low-power controller). The low-power controller in this application can provide a large number of scene detection mechanisms and system low-power control capabilities, which can be used to expand different applications and build new projects with different power control strategies.

[0125] Power consumption has always been a challenge for terminal devices. It's difficult to make large-scale modifications and optimizations to existing mature solutions in typical scenarios to achieve power savings. This application designs a low-power control method for terminal devices, enabling real-time fine-tuning of system functions for specific applications or scenarios. It monitors target data from the terminal device, including at least one of the following: current system status data and foreground application usage scenario data. Specifically, it determines the terminal device's system status and the user's usage scenario, and then controls the power consumption of each system module through a controller. Optionally, the target power consumption options and strategies can be adjusted and controlled in real-time via a server, i.e., cloud configuration.

[0126] For example, such as Figure 3C The diagram shows a general flowchart of the power consumption control method in this embodiment. When a target application is detected to be running in the whitelisted applications, the Play Control Engine (PCE) module is activated via Cosa to manage and control the playback of multimedia resources. Simultaneously, the target application registers a low-power service (client) to receive low-power optimization instructions or data when needed. When the target application's low-power service (client) is activated, the low-power controller corresponding to the target application is started. For example, MediaTurbo can be used to start the low-power controller corresponding to the target application. This low-power controller is responsible for managing the power consumption of the target application, ensuring that energy consumption is minimized while maintaining the application's operation. The low-power controller initializes, including reading some system settings of the terminal device, such as power management policies and Bluetooth connection parameters, and storing these settings internally. This is done to optimize power consumption based on the actual situation of the device in subsequent power management. Finally, the low-power controller completes the initialization process and is ready to manage the power consumption of the target application based on the stored system settings and application requirements. MediaTurbo is a technology designed to optimize multimedia experiences, especially in scenarios such as video playback and gaming.

[0127] The multimedia playback control engine module can also be used to launch the system monitoring module and the scene monitoring module to monitor target data, namely at least one of the current system status data and the usage scene data of the foreground application (including data on changes in usage scenes and usage habits); it can also launch the cloud configuration module to obtain cloud configuration strategies, namely target optimization strategies.

[0128] Then, it checks whether the target data meets the preset trigger conditions. If so, it checks whether low-power mode is enabled. If enabled (or enabled if not), it retrieves the target optimization strategy through the cloud configuration module and adjusts the power consumption of each module in the system according to the low-power mode and the target optimization strategy. Optionally, a Toast message indicating that low-power mode is enabled can be displayed through the notification module.

[0129] In this embodiment, target data of the terminal device can be monitored. The target data includes at least one of current system status data and usage scenario data of the foreground application. When the target data meets a preset trigger condition, power consumption control of the foreground application is performed according to a low-power mode to reduce the power consumption of the foreground application. This allows for low-power control of the foreground application.

[0130] This application aims to save power consumption in multimedia usage scenarios, especially for foreground applications and whitelisted applications. By disassembling and analyzing the various modules of the terminal device, it provides a low-power control method that allows for flexible switching of strategies and fine-tuning of the capabilities of each module. While avoiding any loss of user experience, it significantly reduces or adjusts the power consumption of unnecessary system capabilities, achieving the goal of seamless power saving.

[0131] like Figure 4 The diagram shown is a schematic representation of one embodiment of the power consumption control device in this application, which may include:

[0132] Monitoring module 401 is used to monitor target data of terminal devices, wherein the target data includes at least one of current system status data and usage scenario data of foreground applications;

[0133] The processing module 402 is used to control the power consumption of the foreground application according to a low-power mode when the target data meets the preset trigger conditions, so as to reduce the power consumption of the foreground application.

[0134] Optionally, in some possible implementations, the processing module 402 is specifically used to control power consumption for the interface activity scenarios of the foreground application according to the low-power mode.

[0135] Optionally, in some possible implementations, the processing module 402 is specifically used to perform power control on the foreground application according to the low power mode and the target power optimization policy, wherein the preset triggering condition corresponds to the target power optimization policy.

[0136] Optionally, in some possible implementations, the processing module 402 is specifically used to perform power consumption control on the interface activity scenarios of the foreground application according to the low power mode and the target power consumption optimization strategy.

[0137] Optionally, in some possible implementations, the processing module 402 is specifically used to control the playback parameters of the multimedia resources and / or to perform system power consumption control when playing multimedia resources through the target application.

[0138] Optionally, in some possible implementations, the playback parameters include at least one of the following: screen brightness, volume, audio, sound effects, Bluetooth transmission rate, picture quality, video color, True Color Vision brightening curve, and Frame Rate Target Control (FRTC).

[0139] Optionally, in some possible implementations, the processing module 402 is specifically used to perform at least one of the following when playing multimedia resources through the target application: wireless fidelity network dual-channel suppression, GPS positioning switching network positioning, disabling background data synchronization, closing background applications, and disabling system haptic feedback function.

[0140] Optionally, in some possible implementations, the target optimization strategy is obtained from a server, or it is preset in the terminal device.

[0141] Optionally, in some possible implementations, the power consumption control device further includes:

[0142] The transceiver module 403 is used to send the target data to the server and receive the target power consumption optimization strategy from the server in response to the sending of the target data.

[0143] Optionally, in some possible implementations, the foreground application includes a target application, and the monitoring module 401 is specifically used to monitor the target data of the terminal device when the target application is detected to be launched, wherein the target application belongs to an application in a preset whitelist.

[0144] Optionally, in some possible implementations, the current system status data includes at least one of the following: the charging status of the terminal device, the current remaining battery power, the current temperature, the foreground application, the on / off status of the first power-saving mode, and the on / off status of the second power-saving mode, wherein the power-saving effect of the second power-saving mode is greater than that of the first power-saving mode; or,

[0145] The usage scenario data of the foreground application includes: the usage duration of the foreground application, the screen usage status of the foreground application, and the on / off status of the low-power mode of the foreground application; or,

[0146] The preset triggering conditions include at least one of the following: the current remaining battery power is less than the battery power threshold, the current temperature is greater than the temperature threshold, the foreground application is an application in a preset whitelist, the first mode is enabled, the second power saving mode is enabled, the current temperature of the terminal device is greater than the temperature threshold, the usage time is greater than the duration threshold, and the low power mode of the foreground application is enabled, and / or the terminal device is in a non-charging state.

[0147] Optionally, in some possible implementations, the preset triggering condition is obtained from a server, or is preset in the terminal device.

[0148] Optionally, in some possible implementations, the processing module 402 is specifically used to activate the low-power mode when the target data meets the preset triggering conditions and the low-power mode is not activated; and to perform power control on the foreground application according to the low-power mode.

[0149] Optionally, in some possible implementations, after the low-power mode is activated, the power control device further includes a display module 404 for displaying a prompt message, the prompt message being used to notify the user that the low-power mode has been enabled.

[0150] Optionally, in some possible implementations, the display module 404 is specifically used to display the prompt information via a floating window; and / or,

[0151] Display module 404 is specifically used to display the prompt information through the notification bar.

[0152] like Figure 5 The diagram shown is a schematic representation of an embodiment of the terminal device described in this application, which may include, for example: Figure 4 The power consumption control device shown.

[0153] like Figure 6 The diagram shown is a schematic diagram of another embodiment of the terminal device in this application. The following is in conjunction with... Figure 6 A detailed introduction to the various components of a mobile phone in a terminal device:

[0154] RF circuit 610 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with processor 680; additionally, it transmits uplink data to the base station. Typically, RF circuit 610 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc. Furthermore, RF circuit 610 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0155] The memory 620 can be used to store software programs and modules. The processor 680 executes various functions and data processing of the mobile phone by running the software programs and modules stored in the memory 620. The memory 620 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 620 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0156] The input unit 630 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the mobile phone. Specifically, the input unit 630 may include a touch panel 631 and other input devices 632. The touch panel 631, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 631), and drive the corresponding connection devices according to a pre-set program. Optionally, the touch panel 631 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 680, and can receive and execute commands sent by the processor 680. In addition, the touch panel 631 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 631, the input unit 630 may also include other input devices 632. Specifically, other input devices 632 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0157] The display unit 640 can be used to display information input by the user or information provided to the user, as well as various menus of the mobile phone. The display unit 640 may include a display panel 641, which may optionally be configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar display. Furthermore, a touch panel 631 may cover the display panel 641. When the touch panel 631 detects a touch operation on or near it, it transmits the information to the processor 680 to determine the type of touch event. Subsequently, the processor 680 provides corresponding visual output on the display panel 641 based on the type of touch event. Although in Figure 6 In this embodiment, the touch panel 631 and the display panel 641 are two separate components to realize the input and output functions of the mobile phone. However, in some embodiments, the touch panel 631 and the display panel 641 can be integrated to realize the input and output functions of the mobile phone.

[0158] The mobile phone may also include at least one sensor 650, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 641 according to the ambient light level, and the proximity sensor can turn off the display panel 641 and / or backlight when the phone is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity, and can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, taps), etc. Other sensors that may be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0159] Audio circuit 660, speaker 661, and microphone 662 provide an audio interface between the user and the mobile phone. Audio circuit 660 converts received audio data into electrical signals and transmits them to speaker 661, where speaker 661 converts them into sound signals for output. On the other hand, microphone 662 converts collected sound signals into electrical signals, which are received by audio circuit 660, converted into audio data, and then output to processor 680 for processing. The audio data is then transmitted via RF circuit 610 to, for example, another mobile phone, or output to memory 620 for further processing.

[0160] Wi-Fi is a short-range wireless transmission technology. Through the Wi-Fi module 670, mobile phones can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 6 Wi-Fi module 670 is shown, but it is understood that it is not an essential component of a mobile phone and can be omitted as needed without changing the essence of the invention.

[0161] The processor 680 is the control center of the mobile phone, connecting various parts of the phone through various interfaces and lines. It executes software programs and / or modules stored in the memory 620, and calls data stored in the memory 620 to perform various functions and process data, thereby providing overall monitoring of the phone. Optionally, the processor 680 may include one or more processing units; preferably, the processor 680 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 680.

[0162] The mobile phone also includes a power supply 690 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 680 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0163] Although not shown, mobile phones may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0164] In this embodiment of the application, the processor 680 is used to monitor target data of the terminal device, the target data including at least one of current system status data and usage scenario data of the foreground application; when the target data meets a preset trigger condition, the processor controls the power consumption of the foreground application according to a low power mode to reduce the power consumption of the foreground application.

[0165] Optionally, in some possible implementations, the processor 680 is specifically configured to control power consumption for the interface activity scenarios of the foreground application according to the low-power mode.

[0166] Optionally, in some possible implementations, the processor 680 is specifically used to perform power control on the foreground application according to the low-power mode and the target power optimization policy, wherein the preset triggering condition corresponds to the target power optimization policy.

[0167] Optionally, in some possible implementations, the processor 680 is specifically used to control power consumption for the interface activity scenarios of the foreground application based on the low-power mode and the target power optimization strategy.

[0168] Optionally, in some possible implementations, the processor 680 is specifically configured to control playback parameters of the multimedia resources being played through the target application, and / or to perform system power consumption control.

[0169] Optionally, in some possible implementations, the playback parameters include at least one of the following: screen brightness, volume, audio, sound effects, Bluetooth transmission rate, picture quality, video color, True Color Vision brightening curve, and Frame Rate Target Control (FRTC).

[0170] Optionally, in some possible implementations, the processor 680 is specifically configured to, when playing multimedia resources through the target application, suppress dual-channel Wi-Fi network, switch between GPS positioning and network positioning, disable background data synchronization, close background applications, and disable system haptic feedback function.

[0171] Optionally, in some possible implementations, the target optimization strategy is obtained from a server, or it is preset in the terminal device.

[0172] Optionally, in some possible implementations, the RF circuit 610 is used to send the target data to the server and receive the target power consumption optimization strategy from the server in response to the sending of the target data.

[0173] Optionally, in some possible implementations, the foreground application includes a target application, and the processor 680 is specifically used to monitor target data of the terminal device when the target application is detected to be launched, wherein the target application belongs to an application in a preset whitelist.

[0174] Optionally, in some possible implementations, the current system status data includes at least one of the following: the charging status of the terminal device, the current remaining battery power, the current temperature, the foreground application, the on / off status of the first power-saving mode, and the on / off status of the second power-saving mode, wherein the power-saving effect of the second power-saving mode is greater than that of the first power-saving mode; or,

[0175] The usage scenario data of the foreground application includes: the usage duration of the foreground application, the screen usage status of the foreground application, and the on / off status of the low-power mode of the foreground application; or,

[0176] The preset trigger conditions include at least one of the following: the current remaining battery power is less than the battery power threshold, the current temperature is greater than the temperature threshold, the foreground application is an application in a preset whitelist, the first power saving mode is enabled, the second power saving mode is enabled, the current temperature of the terminal device is greater than the temperature threshold, the usage time is greater than the duration threshold, and the low power mode of the foreground application is enabled, and / or the terminal device is in a non-charging state.

[0177] Optionally, in some possible implementations, the preset triggering condition is obtained from a server, or is preset in the terminal device.

[0178] Optionally, in some possible implementations, the processor 680 is specifically configured to activate the low-power mode when the target data meets a preset trigger condition and the low-power mode is not activated; and to perform power control on the foreground application according to the low-power mode.

[0179] Optionally, in some possible implementations, after the low-power mode is activated, the display unit 640 is used to display a prompt message to inform the user that the low-power mode has been enabled.

[0180] Optionally, in some possible implementations, the display unit 640 is specifically used to display the prompt information via a floating window; and / or,

[0181] Display unit 640 is specifically used to display the prompt information through the notification bar.

[0182] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0183] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

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

[0187] 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.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0188] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A power consumption control method, characterized in that, include: The target data of the monitoring terminal device includes at least one of the current system status data and the usage scenario data of the foreground application. When the target data meets the preset triggering conditions, power consumption control is performed on the foreground application according to the low power mode to reduce the power consumption of the foreground application.

2. The method according to claim 1, characterized in that, The step of controlling the power consumption of the foreground application according to the low-power mode includes: Based on the low-power mode, power consumption is controlled for the interface activities of the foreground application.

3. The method according to claim 1, characterized in that, The step of controlling the power consumption of the foreground application according to the low-power mode includes: The power consumption of the foreground application is controlled according to the low power mode and the target power optimization strategy, and the preset triggering condition corresponds to the target power optimization strategy.

4. The method according to claim 3, characterized in that, The step of controlling the power consumption of the foreground application based on the low-power mode and the target power optimization strategy includes: Based on the low-power mode and the target power optimization strategy, power consumption is controlled for the interface activity scenarios of the foreground application.

5. The method according to claim 2 or 4, characterized in that, The foreground application includes a target application, and the power consumption control for the interface activity scenarios of the foreground application includes: When playing multimedia resources through the target application, control the playback parameters of the multimedia resources and / or perform system power consumption control.

6. The method according to claim 5, characterized in that, The playback parameters include at least one of the following: screen brightness, volume, audio, sound effects, Bluetooth transmission rate, picture quality, video color, True Color Vision brightening curve, and Frame Rate Target Control (FRTC).

7. The method according to claim 5, characterized in that, When playing multimedia resources through the target application, system power consumption control includes at least one of the following: Dual-channel suppression of wireless fidelity networks; Global Positioning System (GPS) positioning and network positioning; Disable background data synchronization; Close background applications; Turn off the system's haptic feedback function.

8. The method according to claim 3 or 4, characterized in that, The target optimization strategy is obtained from the server or is preset in the terminal device.

9. The method according to claim 8, characterized in that, The method further includes: Send the target data to the server; Receive the target power consumption optimization strategy from the server in response to the target data transmission.

10. The method according to any one of claims 1-4, characterized in that, The foreground application includes a target application, and the target data of the monitoring terminal device includes: If the target application is detected to be launched, the target data of the terminal device is monitored, and the target application belongs to an application in a preset whitelist.

11. The method according to any one of claims 1-4, characterized in that, The current system status data includes at least one of the following: the charging status of the terminal device, the current remaining battery power, the current temperature, the foreground application, the on / off status of the first power-saving mode, and the on / off status of the second power-saving mode, wherein the power-saving effect of the second power-saving mode is greater than that of the first power-saving mode; or, The usage scenario data of the foreground application includes: the usage duration of the foreground application, the screen usage status of the foreground application, and the on / off status of the low-power mode of the foreground application; or, The preset trigger conditions include at least one of the following: the current remaining battery power is less than the battery power threshold, the current temperature is greater than the temperature threshold, the foreground application is an application in a preset whitelist, the first power saving mode is enabled, the second power saving mode is enabled, the current temperature of the terminal device is greater than the temperature threshold, the usage time is greater than the duration threshold, and the low power mode of the foreground application is enabled, and / or the terminal device is in a non-charging state.

12. The method according to claim 11, characterized in that, The preset triggering conditions are obtained from the server or preset in the terminal device.

13. A power consumption control device, characterized in that, include: The monitoring module is used to monitor target data of the terminal device, wherein the target data includes at least one of the current system status data and the usage scenario data of the foreground application; The processing module is used to control the power consumption of the foreground application according to a low-power mode when the target data meets the preset trigger conditions, so as to reduce the power consumption of the foreground application.

14. A terminal device, characterized in that, include: A memory and a processor, and a transceiver, wherein the memory stores a computer program executable on the processor, and the terminal device executes the program to implement the method of any one of claims 1-12.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-12.

Images