Power consumption calling method and system, electronic equipment and storage medium

Abstract

The invention relates to a power consumption calling method and system, electronic equipment and a storage medium, and relates to the technical field of terminals. Determining a power consumption calling strategy corresponding to the target component according to the real-time scene where the target component is located in combination with white list data stored in the cloud; or, based on a power consumption calling instruction sent by the third-party software, determining a power consumption calling strategy corresponding to the target component; and executing the power consumption calling strategy on the target component. The power consumption calling strategy corresponding to the target component is determined through the real-time scene where the target component is located in combination with the white list data stored in the cloud, unnecessary power consumption calling can be avoided, and therefore the overall energy consumption of equipment is reduced, and the power consumption calling strategy corresponding to the target component is determined based on the power consumption calling instruction sent by the third-party software, so that the power consumption calling efficiency is improved. The power consumption of the target component can be pointedly reduced, so that the user experience is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of terminal technology, and in particular to a power consumption calling method, system, electronic device and storage medium. Background Art

[0002] The power consumption of mobile devices is one of the important factors affecting user experience and battery life. In order to improve the battery life of mobile devices, it is necessary to effectively manage and control the power consumption of mobile devices. In mobile devices, power consumption mainly comes from multiple aspects such as processors, screens, and network connections. In order to effectively manage the power consumption of mobile devices, it is necessary to call the power consumption of mobile devices based on the operating status of each component to extend battery life. How to call the power consumption of mobile devices has become an urgent problem to be solved. Summary of the invention

[0003] The present disclosure provides a power consumption calling method, system, electronic device and storage medium to at least solve the problem of how to call power consumption of mobile devices. The technical solution of the present disclosure is as follows:

[0004] According to the first aspect of the embodiments of the present disclosure, a power consumption call method is provided, including: determining a target component on a target device to be power-consumption called; determining a power consumption call strategy corresponding to the target component according to the real-time scenario in which the target component is located and in combination with whitelist data stored in the cloud; or, determining a power consumption call strategy corresponding to the target component based on a power consumption call instruction sent by third-party software; and executing the power consumption call strategy on the target component. In some embodiments, determining a target component on a target device to be power-consumption called includes: monitoring multiple candidate components on the target device; in response to monitoring a state change of any one or more candidate components, using the candidate component with a state change as a target component.

[0005] In some embodiments, the power consumption calling strategy corresponding to the target component is determined according to the real-time scenario in which the target component is located and in combination with the whitelist data stored in the cloud, including: obtaining the whitelist data stored in the cloud, the whitelist data including the whitelist scenarios with power consumption calling authority, the candidate components with power consumption calling authority in each whitelist scenario, and the mapping relationship between the candidate components and the candidate power consumption calling strategy in each whitelist scenario; obtaining the current real-time scenario of the target component, and determining whether the real-time scenario belongs to the whitelist scenario; in response to the real-time scenario belonging to the whitelist scenario, determining whether the target component belongs to the candidate component with power consumption calling authority in the real-time scenario; if the target component belongs to the candidate component with power consumption calling authority in the real-time scenario, querying the mapping relationship corresponding to the real-time scenario to determine the power consumption calling strategy corresponding to the target component.

[0006] In some embodiments, determining a target component on a target device for power consumption call includes: obtaining a power consumption call instruction sent by third-party software based on a power consumption management interface, wherein the third-party software is software that is granted power consumption call permission; and determining the target component on which power consumption call is to be performed based on the power consumption call instruction.

[0007] In some embodiments, determining the power consumption calling strategy corresponding to the target component includes: based on the power consumption calling instruction, obtaining the strategy identification information corresponding to each target component carried by the power consumption calling instruction; and determining the power consumption calling strategy corresponding to each target component according to the strategy identification information.

[0008] In some embodiments, after executing the power consumption calling strategy on the target component, the method further includes: updating a strategy execution log corresponding to the power consumption calling strategy.

[0009] In some embodiments, after determining the power consumption call policy corresponding to the target component, it also includes: judging whether to execute the power consumption call policy based on the status parameters of the target device, wherein the status parameters include real-time user status, real-time system status, and real-time target component status; in response to the judgment result that the power consumption call policy is not executed, the processing program corresponding to the target component is controlled not to execute the power consumption call policy.

[0010] In some embodiments, the target component is at least one of a process component, an activity component, and a window component.

[0011] According to the second aspect of the embodiment of the present disclosure, a power consumption calling system is provided, including: a power consumption service module, which is used to determine the target component on the target device to be power-consumption called; a power consumption policy determination module, which is used to determine the power consumption calling policy corresponding to the target component according to the real-time scenario in which the target component is located and in combination with the whitelist data stored in the cloud; or, based on the power consumption calling instruction sent by the third-party software, determine the power consumption calling policy corresponding to the target component; an agent execution module, which is used to execute the power consumption calling policy on the target component. In some embodiments, the power consumption service module is also used to: monitor multiple candidate components on the target device; in response to monitoring a state change of any one or more candidate components, use the candidate component with the state change as the target component.

[0012] In some embodiments, the power consumption policy determination module is also used to: obtain whitelist data stored in the cloud, the whitelist data including whitelist scenarios with power consumption call permission, candidate components with power consumption call permission in each whitelist scenario, and a mapping relationship between candidate components and candidate power consumption call policies in each whitelist scenario; obtain the current real-time scenario of the target component, and determine whether the real-time scenario belongs to the whitelist scenario; in response to the real-time scenario belonging to the whitelist scenario, determine whether the target component belongs to a candidate component with power consumption call permission in the real-time scenario; if the target component belongs to a candidate component with power consumption call permission in the real-time scenario, query the mapping relationship corresponding to the real-time scenario to determine the power consumption call policy corresponding to the target component.

[0013] In some embodiments, the power consumption service module is further used to: obtain power consumption call instructions sent by third-party software based on the power consumption management interface, wherein the third-party software is software that is granted power consumption call authority; and determine the target component to be called for power consumption based on the power consumption call instructions.

[0014] In some embodiments, the power consumption policy determination module is further used to: based on the power consumption call instruction, obtain the policy identification information corresponding to each target component carried by the power consumption call instruction; and determine the power consumption call policy corresponding to each target component according to the policy identification information.

[0015] In some embodiments, the power consumption calling system further includes: a log updating module, configured to update a policy execution log corresponding to the power consumption calling policy.

[0016] In some embodiments, the power consumption calling system also includes: a power consumption control module, used to determine whether to execute the power consumption calling strategy based on the status parameters of the target device, wherein the status parameters include real-time user status, real-time system status and real-time target component status; an agent execution module, further used to: in response to the judgment result that the power consumption calling strategy is not executed, control the processing program corresponding to the target component not to execute the power consumption calling strategy.

[0017] In some embodiments, the target component is at least one of a process component, an activity component, and a window component.

[0018] According to the third aspect of an embodiment of the present disclosure, an electronic device is proposed, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to implement a power consumption calling method as described in the embodiment of the first aspect of the present application.

[0019] According to a fourth aspect of an embodiment of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is proposed, wherein the computer instructions are used to implement a power consumption calling method as described in the embodiment of the first aspect of the present application.

[0020] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is proposed, including a computer program, and when the computer program is executed by a processor, the computer program implements a power consumption calling method as described in the embodiment of the first aspect of the present application.

[0021] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0022] This application determines the power consumption call strategy corresponding to the target component through the real-time scenario of the target component and combines it with the whitelist data stored in the cloud, which can avoid unnecessary power consumption calls and thus reduce the overall energy consumption of the device. By determining the power consumption call strategy corresponding to the target component based on the power consumption call instructions sent by third-party software, the power consumption of the target component can be reduced in a targeted manner to improve user experience.

[0023] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0025] Figure 1 It is a schematic diagram of an exemplary implementation of a power consumption calling method shown in the present application.

[0026] Figure 2 It is a schematic diagram of an exemplary implementation of another power consumption calling method shown in the present application.

[0027] Figure 3 It is a schematic diagram of an exemplary implementation of another power consumption calling method shown in the present application.

[0028] Figure 4 This is a schematic diagram of the relationship between a target component, policy identification information and a power consumption calling policy shown in the present application.

[0029] Figure 5 It is a schematic diagram of a power consumption calling system shown in the present application.

[0030] Figure 6 It is a framework diagram of a power consumption calling system shown in the present application.

[0031] Figure 7 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0032] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0034] Figure 1 is a schematic diagram of an exemplary implementation of a power consumption calling method shown in the present application, such as Figure 1 As shown, the power consumption calling method includes the following steps:

[0035] S101, determining a target component on a target device to be invoked for power consumption.

[0036] As a feasible method, the target device may monitor the components contained in the target device in real time. If at a certain moment, it is detected that one or more components have state changes, these components with state changes may be used as target components.

[0037] As another achievable manner, the target component may be directly specified by the third-party software. For example, if it is detected that the user adjusts the refresh rate of the third-party video software from 120 Hz to 60 Hz, the component corresponding to the refresh rate is used as the target component.

[0038] Optionally, the target component is at least one of a process component, an activity component, and a window component. It is not difficult to understand that the target component may also be other types of components.

[0039] S102, determining the power consumption calling strategy corresponding to the target component according to the real-time scenario of the target component and in combination with the whitelist data stored in the cloud; or determining the power consumption calling strategy corresponding to the target component based on the power consumption calling instruction sent by the third-party software.

[0040] In this application, the corresponding power consumption calling strategy of the target component is selected according to different scenarios and requirements. For example, for long-running processes or activities, low power consumption mode can be used; for frequently switched windows, methods such as dynamic adjustment of screen brightness can be used to reduce power consumption; for call interfaces that have not detected user operations for a long time, the screen can be kept off.

[0041] As a feasible method, the power consumption call strategy corresponding to the target component is determined according to the real-time scenario of the target component and compared with the whitelist data stored in the cloud. The whitelist data includes whitelist scenarios with power consumption call permissions, candidate components with power consumption call permissions in each whitelist scenario, and the mapping relationship between candidate components and candidate power consumption call strategies in each whitelist scenario.

[0042] As another achievable manner, the power consumption calling instruction sent by the third-party software is parsed to determine the power consumption calling strategy corresponding to the target component carried by the power consumption calling instruction.

[0043] S103, executing the power consumption calling strategy on the target component.

[0044] Control the corresponding handler of the target component to execute the power consumption call strategy. For example, if you need to reduce the screen brightness to save power, you can call the setBrightness method in the android.app.Activity class to achieve it.

[0045] An embodiment of the present application proposes a power consumption calling method, including: determining a target component on a target device to be power-consumption called; determining a power consumption calling strategy corresponding to the target component according to the real-time scenario in which the target component is located and in combination with whitelist data stored in the cloud; or, determining a power consumption calling strategy corresponding to the target component based on a power consumption calling instruction sent by third-party software; executing the power consumption calling strategy on the target component. The present application determines the power consumption calling strategy corresponding to the target component through the real-time scenario in which the target component is located and in combination with whitelist data stored in the cloud, thereby avoiding unnecessary power consumption calls and reducing the overall energy consumption of the device, and determining the power consumption calling strategy corresponding to the target component based on the power consumption calling instruction sent by the third-party software can reduce the power consumption of the target component in a targeted manner to improve the user experience. Furthermore, after controlling the handler corresponding to the target component to execute the power consumption calling strategy, it also includes: updating the policy execution log corresponding to the power consumption calling strategy to facilitate subsequent energy consumption analysis.

[0046] Figure 2 is a schematic diagram of an exemplary implementation of another power consumption calling method shown in the present application, such as Figure 2 As shown, the power consumption calling method includes the following steps:

[0047] S201, monitoring multiple candidate components on a target device.

[0048] Optionally, the target component is at least one of a process component, an activity component, and a window component.

[0049] S202: In response to monitoring that any one or more candidate components have a state change, the candidate components having a state change are used as target components.

[0050] S203, obtaining whitelist data stored in the cloud, the whitelist data including whitelist scenarios with power consumption call permission, candidate components with power consumption call permission in each whitelist scenario, and a mapping relationship between the candidate components and the candidate power consumption call strategy in each whitelist scenario.

[0051] Among them, the whitelist scenarios with power consumption call permission specify which scenarios are considered to be scenarios that allow power consumption calls. These scenarios may be defined according to different requirements and conditions, such as a specific time period, specific software, etc.

[0052] The candidate components with power consumption call permission in each whitelist scenario specify which candidate components are granted the power consumption call permission in each whitelist scenario. These candidate components may be process components, activity components or window components of the device.

[0053] The mapping relationship between the candidate components and the candidate power consumption invocation strategies specifies the power consumption invocation strategy corresponding to each candidate component. These strategies can be formulated according to specific components and requirements, such as limiting their invocation frequency, limiting their occupied resources, etc.

[0054] By storing whitelist data in the cloud, it is easy to manage and update the whitelist data and ensure that each component executes the corresponding power consumption call strategy in a specific scenario. This can better control the power consumption behavior of the device, improve energy utilization efficiency and extend the use time of the device.

[0055] S204, obtaining the current real-time scene of the target component, and determining whether the real-time scene belongs to the whitelist scene.

[0056] Exemplarily, if software A is located in a whitelist scenario stored in the cloud, and the current target component is in the running state of software A, it is determined that the real-time scenario belongs to the whitelist scenario.

[0057] S205 , in response to the real-time scenario belonging to the whitelist scenario, determining whether the target component is a candidate component having power consumption calling authority in the real-time scenario.

[0058] Since the components with power consumption calling permissions corresponding to different whitelist scenarios are not necessarily the same, in this application, after determining that the real-time scenario belongs to the whitelist scenario, it is necessary to determine whether the target component is a candidate component with power consumption calling permissions in the real-time scenario.

[0059] For example, the components with power consumption call permission corresponding to whitelist scenario software A include component 1, component 2 and component 4, while the components with power consumption call permission corresponding to whitelist scenario software B include component 1, component 3 and component 5, that is, the components with power consumption call permission corresponding to different whitelist scenarios are not necessarily the same. The specific setting can be made according to the actual situation.

[0060] S206: If the target component is a candidate component with power consumption calling authority in the real-time scenario, query the mapping relationship corresponding to the real-time scenario to determine the power consumption calling strategy corresponding to the target component.

[0061] In this application, the power consumption calling strategy corresponding to the target component is determined by querying the mapping relationship corresponding to the real-time scenario. For example, if component 1 is a process refresh rate component, in the mapping relationship corresponding to the whitelist scenario software A, the refresh rate corresponding to component 1 is 120HZ, then the power consumption calling strategy corresponding to component 1 in the software A scenario is to adjust the refresh rate to 120HZ; and in the mapping relationship corresponding to the whitelist scenario software B, the refresh rate corresponding to component 1 is 60HZ, then the power consumption calling strategy corresponding to component 1 in the software B scenario is to adjust the refresh rate to 60HZ.

[0062] S207 , judging whether to execute the power consumption calling strategy based on the state parameters of the target device, wherein the state parameters include real-time user state, real-time system state, and real-time target component state.

[0063] The real-time user status refers to the user's operation status, for example, whether the user frequently clicks the screen during a call.

[0064] The real-time system status is the current device status of the target device, such as the current battery capacity status, network connection status, memory usage, running applications, whether it is in energy saving mode, etc. of the target device.

[0065] The target component status refers to the status of various components on the target device, such as screen brightness, volume, network connection, etc.

[0066] In this application, the real-time user status, real-time system status, and real-time target component status can be obtained by obtaining the device's sensor information, application usage, etc., and then judging whether it is necessary to execute the power consumption call strategy based on this information, so as to dynamically adjust the power consumption call strategy to achieve better energy saving effects. For example, if the user is performing a long task or playing a game, the screen brightness can be reduced or the power saving mode can be turned on to reduce energy consumption.

[0067] S208 , in response to the judgment result that the power consumption calling strategy is to be executed, controlling the processing program corresponding to the target component to execute the power consumption calling strategy.

[0068] If the above judgment result is to execute the power consumption calling strategy, then the processing program corresponding to the target component is controlled to execute the power consumption calling strategy.

[0069] Furthermore, if the judgment result is that the power consumption calling strategy is not executed, the processing program corresponding to the control target component does not execute the power consumption calling strategy.

[0070] In an embodiment of the present application, the target device automatically turns on component status monitoring. By determining the target component to be called for power consumption and the corresponding power consumption calling strategy, the power consumption of the target component can be reduced in a targeted manner. By judging the user status, system status and target component status in real time, unnecessary power consumption calls can be avoided, thereby reducing the overall energy consumption of the device and improving battery life and user experience.

[0071] Figure 3 is a schematic diagram of an exemplary implementation of another power consumption calling method shown in the present application, such as Figure 3 As shown, the power consumption calling method includes the following steps:

[0072] S301, acquiring a power consumption calling instruction sent by third-party software based on a power consumption management interface, wherein the third-party software is software that is granted with power consumption calling authority.

[0073] Different from the above-mentioned embodiments, the embodiments of the present application no longer realize power consumption call based on the status monitoring of the components automatically started by the target device, but directly obtains the power consumption call instruction sent by the third-party software based on the power consumption management interface to make subsequent power consumption calls according to the power consumption call instruction.

[0074] Among them, the power consumption call instruction sent by the third-party software can be generated based on the user operation. For example, if the user adjusts the refresh rate of the third-party video software from 120HZ to 60HZ through operation, a power consumption call instruction for adjusting the refresh rate of the third-party video software from 120HZ to 60HZ is generated.

[0075] S302: Determine a target component for which power consumption is to be called based on the power consumption calling instruction.

[0076] According to the structure and specification of the power consumption call instruction, the field information related to the target component is extracted. When parsing the field information in the power consumption call instruction, the identification or identifier representing the target component is searched, which may be a component name, ID, address, etc., which is used to uniquely identify the target component. The identification of the target component is matched with the known components in the system, and the target component is determined according to the matching result.

[0077] S303: Based on the power consumption calling instruction, obtain the policy identification information corresponding to each target component carried by the power consumption calling instruction.

[0078] The power consumption call instruction is further parsed using the parsed target component identifier to obtain the policy identifier information corresponding to each target component carried by the power consumption call instruction.

[0079] S304: Determine the power consumption calling strategy corresponding to each target component according to the strategy identification information.

[0080] Figure 4 This is a schematic diagram of the relationship between a target component, policy identification information and power consumption calling policy shown in the present application, such as Figure 4 As shown, the strategy identification information takes a binary identification as an example. After the target component is determined, the power consumption calling strategy corresponding to the target component can be determined according to the binary identification.

[0081] S305 , judging whether to execute the power consumption calling strategy based on the real-time user state, the real-time system state and the real-time target component state of the target device.

[0082] S306 , in response to the judgment result that the power consumption calling strategy is to be executed, controlling the processing program corresponding to the target component to execute the power consumption calling strategy.

[0083] Regarding the specific implementation of steps S307 to S308, reference may be made to the specific introduction of the relevant parts in the above embodiments, which will not be elaborated here.

[0084] Furthermore, if the judgment result is that the power consumption calling strategy is not executed, the processing program corresponding to the control target component does not execute the power consumption calling strategy.

[0085] In an embodiment of the present application, the power consumption call instruction sent by the third-party software is directly obtained based on the power consumption management interface, and the target component to be power consumed and the corresponding power consumption call strategy are determined through the power consumption call instruction. The power consumption of the target component can be reduced in a targeted manner. By judging the user status, system status and target component status in real time, unnecessary power consumption calls can be avoided, thereby reducing the overall energy consumption of the device and improving battery life and user experience.

[0086] Figure 5is a schematic diagram of a power consumption calling system shown in the present application, such as Figure 5 As shown, the power consumption calling system 500 includes a power consumption service module 501, a power consumption strategy determination module 502, a power consumption control module 503 and an agent execution module 504, wherein:

[0087] The power consumption service module 501 is used to determine a target component on a target device to be invoked for power consumption.

[0088] The power consumption strategy determination module 502 is used to determine the power consumption calling strategy corresponding to the target component according to the real-time scenario of the target component and in combination with the whitelist data stored in the cloud; or, based on the power consumption calling instruction sent by the third-party software, determine the power consumption calling strategy corresponding to the target component.

[0089] The proxy execution module 503 is used to execute the power consumption calling strategy on the target component.

[0090] The power consumption calling system proposed in the present application can reduce the power consumption of the target component in a targeted manner by determining the target component to be power consumed and the corresponding power consumption calling strategy, and can avoid unnecessary power consumption calls, thereby reducing the overall energy consumption of the device and improving battery life and user experience.

[0091] In some embodiments, the power consumption service module 501 is further used to: monitor multiple candidate components on the target device; in response to monitoring a state change of any one or more candidate components, use the candidate component with the state change as the target component.

[0092] In some embodiments, the power consumption policy determination module 502 is also used to: obtain whitelist data stored in the cloud, the whitelist data including whitelist scenarios with power consumption call permissions, candidate components with power consumption call permissions in each whitelist scenario, and a mapping relationship between candidate components and candidate power consumption call policies in each whitelist scenario; obtain the current real-time scenario of the target component, and determine whether the real-time scenario belongs to the whitelist scenario; in response to the real-time scenario belonging to the whitelist scenario, determine whether the target component belongs to a candidate component with power consumption call permissions in the real-time scenario; if the target component belongs to a candidate component with power consumption call permissions in the real-time scenario, query the mapping relationship corresponding to the real-time scenario to determine the power consumption call policy corresponding to the target component.

[0093] In some embodiments, the power consumption service module 501 is also used to: obtain power consumption call instructions sent by third-party software based on the power consumption management interface, wherein the third-party software is software that is granted power consumption call authority; and determine the target component to be called for power consumption based on the power consumption call instructions.

[0094] In some embodiments, the power consumption policy determination module 502 is further used to: based on the power consumption call instruction, obtain the policy identification information corresponding to each target component carried by the power consumption call instruction; and determine the power consumption call policy corresponding to each target component according to the policy identification information.

[0095] In some embodiments, the power consumption calling system 500 further includes: a log updating module 504, which is used to update a policy execution log corresponding to the power consumption calling policy.

[0096] In some embodiments, the power consumption calling system 500 also includes: a power consumption control module 504, which is used to determine whether to execute the power consumption calling strategy based on the status parameters of the target device, wherein the status parameters include real-time user status, real-time system status, and real-time target component status; an agent execution module 503, which is also used to: in response to the judgment result that the power consumption calling strategy is not executed, control the handler corresponding to the target component not to execute the power consumption calling strategy.

[0097] In some embodiments, the target component is at least one of a process component, an activity component, and a window component.

[0098] Figure 6 This is an overall framework diagram of a power consumption calling system shown in the present application, such as Figure 6 As shown in the figure, the power consumption calling system consists of four layers of architecture, namely, interface layer, strategy layer, execution layer and interaction layer. Among them:

[0099] The interface layer includes power management interface, activity management service, power service module and cloud.

[0100] The function of the power consumption management interface is: the third-party software sends a power consumption call instruction to the power consumption service module through the power consumption management interface.

[0101] The cloud stores whitelist data.

[0102] The power consumption service module is used to determine the target component on the target device to be called for power consumption. Optionally, the power consumption service module can also receive the target component and target component status information sent by the activity management service.

[0103] The policy layer includes a power consumption policy determination module, a power consumption control module, a power consumption window, a power consumption activity, a power consumption process, a user status acquisition unit, and a system status acquisition unit.

[0104] Among them, the power consumption strategy determination module is used to determine the power consumption calling strategy corresponding to the target component.

[0105] The user status acquisition unit is used to send the real-time user status to the power consumption control module.

[0106] The system status acquisition unit is used to send the real-time system status to the power consumption control module.

[0107] The power consumption window, the power consumption activity and / or the power consumption process are used to send the real-time target component status to the power consumption control module.

[0108] The power consumption control module is used to determine whether to execute the power consumption calling strategy based on the real-time user status, real-time system status and real-time target component status of the target device.

[0109] The execution layer includes an agent execution module, which is used to control the processing program corresponding to the target component to execute the power consumption calling strategy in response to the judgment result that the power consumption calling strategy is executed.

[0110] The interaction layer includes the display composition system and the open graphics interface, which is used to interact with processes below the application framework layer.

[0111] Figure 7 is a block diagram of an electronic device 700 according to an exemplary embodiment.

[0112] like Figure 7 As shown, the electronic device 700 includes:

[0113] The memory 701 and the processor 702, a bus 703 connecting different components (including the memory 701 and the processor 702), the memory 701 stores a computer program, and when the processor 702 executes the program, a power consumption calling method of an embodiment of the present disclosure is implemented.

[0114] Bus 703 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0115] The electronic device 700 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 700, including volatile and non-volatile media, removable and non-removable media.

[0116] The memory 701 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 704 and / or cache memory 705. The electronic device 700 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 706 may be used to read and write non-removable, non-volatile magnetic media ( Figure 7 not shown, usually called a "hard drive"). Although Figure 7 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical medium) may be provided. In these cases, each drive may be connected to bus 703 via one or more data medium interfaces. Memory 701 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0117] A program / utility 708 having a set (at least one) of program modules 707 may be stored, for example, in the memory 701. Such program modules 707 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 707 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0118] The electronic device 700 may also communicate with one or more external devices 709 (e.g., keyboard, pointing device, display 710, etc.), one or more devices that enable a user to interact with the electronic device 700, and / or any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 711. Furthermore, the electronic device 700 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 712. Figure 7 As shown, the network adapter 712 communicates with other modules of the electronic device 700 via the bus 703. It should be understood that although Figure 7 Not shown, other hardware and / or software modules may be used in conjunction with electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0119] The processor 702 executes various functional applications and data processing by running the programs stored in the memory 701 .

[0120] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of a power consumption calling method of an embodiment of the present disclosure, and will not be repeated here.

[0121] In order to implement the above embodiment, the embodiment of the present application also proposes a non-transient computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to implement a power consumption calling method as shown in the above embodiment. Optionally, the non-transient computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0122] In order to implement the above embodiment, the embodiment of the present application also proposes a computer program product, including a computer program, and when the computer program is executed by a processor, it implements a power consumption calling method as shown in the above embodiment.

[0123] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0124] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A power consumption calling method, characterized in that: include: Determine a target component on a target device to which a power consumption call is to be made; According to the real-time scenario of the target component and in combination with the whitelist data stored in the cloud, determine the power consumption calling strategy corresponding to the target component; or, Determine a power consumption calling strategy corresponding to the target component based on the power consumption calling instruction sent by the third-party software; The power consumption invocation strategy is executed on the target component.

2. The method according to claim 1, characterized in that The step of determining a target component on a target device to be called for power consumption includes: Monitoring multiple candidate components on the target device; In response to monitoring that a state change occurs in any one or more of the candidate components, the candidate component whose state change occurs is used as the target component.

3. The method according to claim 2, characterized in that The step of determining the power consumption calling strategy corresponding to the target component according to the real-time scenario of the target component and in combination with the whitelist data stored in the cloud includes: Obtaining whitelist data stored in the cloud, the whitelist data including whitelist scenarios with power consumption call authority, candidate components with power consumption call authority in each whitelist scenario, and a mapping relationship between the candidate components and the candidate power consumption call strategy in each whitelist scenario; Obtaining the current real-time scene of the target component, and determining whether the real-time scene belongs to the whitelist scene; In response to the real-time scenario belonging to the whitelist scenario, determining whether the target component is a candidate component having power consumption calling authority in the real-time scenario; If the target component is a candidate component with power consumption calling authority in the real-time scenario, the mapping relationship corresponding to the real-time scenario is queried to determine the power consumption calling strategy corresponding to the target component.

4. The method according to claim 1, characterized in that The step of determining a target component on a target device to be called for power consumption includes: Acquiring a power consumption calling instruction sent by third-party software based on a power consumption management interface, wherein the third-party software is software that is granted with a power consumption calling authority; Based on the power consumption call instruction, the target component to be called for power consumption is determined.

5. The method according to claim 4, characterized in that The determining the power consumption calling strategy corresponding to the target component based on the power consumption calling instruction sent by the third-party software includes: Based on the power consumption calling instruction, obtaining the policy identification information corresponding to each target component carried by the power consumption calling instruction; The power consumption calling strategy corresponding to each of the target components is determined according to the strategy identification information.

6. The method according to any one of claims 1 to 5, characterized in that After executing the power consumption calling strategy on the target component, the method further includes: Update the policy execution log corresponding to the power consumption call policy.

7. The method according to any one of claims 1 to 5, characterized in that After determining the power consumption calling strategy corresponding to the target component, the method further includes: Determining whether to execute the power consumption calling strategy based on the state parameters of the target device, wherein the state parameters include real-time user state, real-time system state, and real-time target component state; In response to the judgment result that the power consumption calling strategy is not executed, the processing program corresponding to the target component is controlled not to execute the power consumption calling strategy.

8. The method according to any one of claims 1 to 5, characterized in that The target component is at least one of a process component, an activity component, and a window component.

9. A power consumption calling system, characterized in that: include: A power consumption service module, used to determine a target component on a target device to be subjected to a power consumption call; A power consumption strategy determination module, used to determine the power consumption calling strategy corresponding to the target component according to the real-time scenario in which the target component is located and in combination with the whitelist data stored in the cloud; Alternatively, based on the power consumption calling instruction sent by the third-party software, determining the power consumption calling strategy corresponding to the target component; The proxy execution module is used to execute the power consumption calling strategy on the target component.

10. The system according to claim 9, characterized in that The power consumption service module is further used for: Monitoring multiple candidate components on the target device; In response to monitoring that a state change occurs in any one or more of the candidate components, the candidate component whose state change occurs is used as the target component.

11. The system according to claim 10, characterized in that The power consumption strategy determination module is further used for: Obtaining whitelist data stored in the cloud, the whitelist data including whitelist scenarios with power consumption call authority, candidate components with power consumption call authority in each whitelist scenario, and a mapping relationship between the candidate components and the candidate power consumption call strategy in each whitelist scenario; Obtaining the current real-time scene of the target component, and determining whether the real-time scene belongs to the whitelist scene; In response to the real-time scenario belonging to the whitelist scenario, determining whether the target component is a candidate component having power consumption calling authority in the real-time scenario; If the target component is a candidate component with power consumption calling authority in the real-time scenario, the mapping relationship corresponding to the real-time scenario is queried to determine the power consumption calling strategy corresponding to the target component.

12. The system according to claim 9, characterized in that The power consumption service module is further used for: Acquiring a power consumption calling instruction sent by third-party software based on a power consumption management interface, wherein the third-party software is software that is granted with a power consumption calling authority; Based on the power consumption call instruction, the target component to be called for power consumption is determined.

13. The system according to claim 10, characterized in that The power consumption strategy determination module is further used for: Based on the power consumption calling instruction, obtaining the policy identification information corresponding to each target component carried by the power consumption calling instruction; The power consumption calling strategy corresponding to each of the target components is determined according to the strategy identification information.

14. The system according to any one of claims 9 to 13, characterized in that: The system further comprises: The log update module is used to update the policy execution log corresponding to the power consumption call policy.

15. The system according to any one of claims 9 to 13, characterized in that: The system further comprises: A power consumption control module, used for determining whether to execute the power consumption calling strategy based on the state parameters of the target device, wherein the state parameters include real-time user state, real-time system state and real-time target component state; The proxy execution module is further used to: in response to the judgment result that the power consumption calling strategy is not to be executed, control the processing program corresponding to the target component not to execute the power consumption calling strategy.

16. The system according to any one of claims 9 to 13, characterized in that: The target component is at least one of a process component, an activity component, and a window component.

17. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 8.

18. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-8.

19. A computer program product, comprising a computer program, which, when executed by a processor, implements the steps according to any one of claims 1 to 8.

Images