Power management in battery powered devices

Abstract

Power consumption by a first device (201, 401, 501, 503, 505) is controlled by predicting (103, 307, 601) at a current time whether an energy consumption activity is to be performed by the first device (201, 401, 501, 503, 505) at a later time, where performance of the energy consumption activity requires a first amount of energy. When at the current time it is predicted that the energy consumption activity is to be performed by the first device (201, 401, 501, 503, 505) at the later time, then an energy conservation device operating mode (107, 111, 309, 311, 605) is activated. The energy conservation device operating mode (107, 111, 309, 311, 605) performs an action to ensure that at least the first amount of energy will be stored in a battery of the first device (201, 401, 501, 503, 505) when the energy consuming activity is initiated at the later time.

Description

BACKGROUND

[0001] The present invention relates to power management in battery-powered devices, and more particularly, to management of energy usage by a battery-powered device that ensures that sufficient power will be stored in the device's battery for the device to perform an identified energy-consuming activity at a later time.

[0002] The following acronyms are used in this specification, in part or in whole:

[0003] Abbreviations Explanation

[0004] AR augmented reality

[0005] CPU central processor

[0006] DVFS dynamic voltage and frequency scaling

[0007] GPS global positioning system

[0008] GPU graphics processing unit

[0009] SOC state of charge

[0010] VR virtual reality

[0011] Wireless consumer electronic devices, such as smartphones, AR / VR headsets, wireless game controllers, and the like, can be powered by a battery and, therefore, have a limited battery life. As used herein, the term "battery life" refers to the time it takes for a device to go from a state in which it has a fully-charged battery to a state in which it has a fully-depleted battery. Further, as used herein, the term "remaining battery life" refers to the time it takes for a device to go from any current state of charge to a state in which it has a fully-depleted battery.

[0012] A device's battery life can vary greatly, depending on how it is implemented. Relevant factors include the properties of the device's energy-consuming hardware components (e.g., CPU, GPU, memory, sensors, power amplifiers, etc.) and the software implementation that determines how to utilize the hardware.

[0013] For such consumer electronic devices, a consumer's usage habits can significantly impact the battery life. For example, a first consumer's smartphone that does not have applications installed and activated or has only a small number of applications installed and activated can consume less energy than the same smartphone when a large number of applications are installed and activated. Similarly, a smartphone that is not being interacted with (e.g., by a user touching buttons, the screen, etc.), and is, therefore, in a less active usage mode, can consume less energy than the same smartphone when it is being interacted with using the available user interface.

[0014] Consumers can use consumer electronic devices in different use cases depending on the type of device, some of which can be more important to the user than others. For example, using a smartphone or smartwatch for contactless payment (e.g., at a grocery store or on a bus ride home), or unlocking the entry door to the user’s home when arriving home, can not require a lot of battery energy, but can be very critical to the user in terms of the service provided, and therefore any interruption to this service should be avoided. By contrast, other uses of the device (e.g., supporting casual web browsing for 10 minutes while waiting for a bus) can be less important if full (or any) functionality cannot be provided. Thus, the various use cases in which a device can be placed have a wide range of possible levels of importance, e.g., how severely the user is impacted if the functionality for a particular use case cannot be provided when the user invokes it.

[0015] In battery-powered devices, the ability to execute one or more applications associated with any given use case depends largely on sufficient energy being stored in the battery at the time the use case is invoked. Thus, energy conservation is of great interest. There are conventional techniques for conserving energy in battery-powered devices, such as DVFS, hardware and software module deactivation (e.g., application deactivation), and setting adjustments (e.g., screen brightness settings). Different energy modes (e.g., power save modes) can be deployed to control one or more such energy conservation settings. Such battery life optimization can be for specific parameters, such as setting the device screen brightness level to a fixed value, or setting the CPU clock rate. Optimization can also be done at a more general level, such as a user-activated energy conservation mode in which more than one software setting can be configured to attempt energy conservation in order to extend battery life.

[0016] In addition to methods that require explicit action by the user, battery endurance modes can also be activated by software in the device, based on predefined activation rules (e.g., when a particular remaining battery level threshold is reached).

[0017] Battery life estimation functionality is also known in the art, in which a device can estimate the current SOC and current energy consumption rate in order to predict how much longer the battery will be able to provide power until the device can no longer operate.

[0018] Document CN113220106A is understood to disclose battery life estimation in combination with a user-preset target battery endurance time. A power saving mode is set for reaching the target battery life. In this way, the device can dynamically adjust the power saving mode level of a target application according to historical operation information of the target application in order to meet a particular battery endurance time.

[0019] Conventional techniques are insufficient to address the problem of ensuring that a device will have sufficient energy stored in its battery at the time a very important use case is to be activated. Such techniques provide battery life estimation and battery life optimization. Activation of power saving mode functionality is typically based on measured parameters, pre-set end user configuration, or a set target battery life. However, none of these approaches can ensure that the use case will have sufficient power available at a future time when the use case is invoked.

[0020] Therefore, there is a need for a technique to address these problems and / or related problems regarding battery life optimization when one or more particularly important use cases can need to be performed at some future time. SUMMARY

[0021] It should be emphasized that the terms "comprises" and "comprising", when used in this specification, are taken to specify the presence of stated features, integers, steps or components; but do not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof.

[0022] Furthermore, reference letters can be provided in some instances (e.g., in the claims and summary) to facilitate identification of various steps and / or elements. However, use of reference letters is not intended to imply or suggest that the referenced steps and / or elements are to be performed or operated in any particular order.

[0023] According to one aspect of the present application, the foregoing and other objects are achieved in a technique (e.g., method, apparatus, non-transitory computer-readable storage medium, program apparatus) that controls power consumption of a first device.

[0024] In one aspect of some, but not necessarily all embodiments consistent with the present application, the power control includes predicting, at a current time, whether an energy consuming activity will be performed by a first device at a later time, wherein performance of the energy consuming activity requires a first amount of energy. When the device predicts at the current time that the energy consuming activity will be performed by the first device at the later time, then the device activates an energy conservation device operating mode that implements actions to ensure that at least the first amount of energy will be stored in a battery of the first device when the energy consuming activity is initiated at the later time.

[0025] In another aspect of some, but not necessarily all embodiments consistent with the present application, predicting, at a current time, whether an energy consuming activity will be performed by a first device at a later time includes using state information to predict, at the current time, whether the energy consuming activity will be performed by the first device at the later time. The state information includes one or more of: a day of the week; a current time of day; and a current location of the first device.

[0026] In another aspect of some, but not necessarily all embodiments consistent with the application, the state information includes the current location of the first device. The predicting can then include comparing the current location of the first device to a geographic region in which historically the energy consumption activity was performed.

[0027] In another aspect of some, but not necessarily all embodiments consistent with the application, the energy conservation device operating mode includes deactivating one or more currently active device activities in response to determining that at least the first amount of energy will not be stored in the battery of the first device when the energy consumption activity is initiated at the later time.

[0028] In another aspect of some, but not necessarily all embodiments consistent with the application, deactivating the one or more currently active device activities includes selecting the one or more currently active device activities based on a prediction of how much energy will be conserved when the one or more currently active device activities are deactivated.

[0029] In another aspect of some, but not necessarily all embodiments consistent with the application, deactivating the one or more currently active device activities includes reducing functionality of a first user interface of the first device. In some, but not necessarily all embodiments, the functionality of the first user interface includes a brightness level of an output display of the first user interface.

[0030] In another aspect of some, but not necessarily all embodiments consistent with the application, the energy conservation device operating mode includes using a second user interface of a second device instead of the first user interface of the first device via a wireless link between the first device and the second device in performing input and / or output operations of the first device. In some, but not necessarily all embodiments, the second device is one of: a smart watch; a smart phone; a tablet computer; and an extended reality headset.

[0031] In another aspect of some, but not necessarily all embodiments consistent with the application, deactivating the one or more currently active device activities includes reducing or deactivating execution of one or more applications that are currently being executed by the first device.

[0032] In another aspect of some, but not necessarily all embodiments consistent with the application, deactivating the one or more currently active device activities includes shutting down device operations for a period of time, and resuming device operations after the period of time expires.

[0033] In another aspect of some, but not necessarily all embodiments consistent with the application, deactivating one or more currently active device activities includes: continuing to accept receipt of input to the first device that cancels the energy saving device operating mode; and in response to receiving the input to the first device that cancels the energy saving device operating mode, exiting the energy saving device operating mode.

[0034] In another aspect of some, but not necessarily all embodiments consistent with the application, predicting at the current time whether the energy consumption activity will be performed by the first device at the later time includes transmitting, via a telecommunications network, a request to a server for a prediction as to whether the energy consumption activity will be performed by the first device at the later time.

[0035] In another aspect of some, but not necessarily all embodiments consistent with the application, power control of the first device includes making a second prediction of whether at least the first amount of energy will be stored in the battery of the first device when the energy consumption activity is initiated at the later time while the first device is operating in the energy saving device operating mode; and further limiting execution of energy consuming functions by the first device if the second prediction is that the first amount of energy will not be stored in the battery of the first device when the energy consumption activity is initiated at the later time.

[0036] In another aspect of some, but not necessarily all embodiments consistent with the application, power control of the first device includes determining the first amount of energy based on data collected from historical energy usage of the first device.

[0037] In another aspect of some, but not necessarily all embodiments consistent with the application, power control of the first device includes receiving information related to the first amount of energy from a user input; and determining the first amount of energy based on the user input.

[0038] In another aspect of some, but not necessarily all embodiments consistent with the application, power control of the first device includes outputting a notification to an output device that the device is taking energy saving action.

[0039] In another aspect of some, but not necessarily all embodiments consistent with the application, the first device is one of: a user device; an electronic tablet device; a smart watch; a sensor device; and a machine type communication device. BRIEF DESCRIPTION OF DRAWINGS

[0040] Objects and advantages of the application will be understood by reading the following detailed description in conjunction with the drawings, in which:

[0041] Figure 1 is a state transition diagram describing actions of a device according to some, but not necessarily all, embodiments of the invention.

[0042] Figure 2 is a block diagram of a device configured to operate according to exemplary embodiments consistent with the invention.

[0043] Figure 3 is a flowchart of actions performed by a device to ensure that there will be sufficient energy for defined one or more use cases according to some, but not necessarily all, embodiments of the invention, in one aspect.

[0044] Figure 4 illustrates aspects of some embodiments of the invention in which a device communicates with one or more (e.g., wirelessly) connected devices to inform a user that the device is taking power saving actions, and in some embodiments, accepts input provided to the connected devices.

[0045] Figure 5 is a schematic diagram illustrating embodiments in which energy saving functionality within a device is supported by a network server 507 or other external information exchange entity that provides information to and receives data from the device.

[0046] Figure 6 is a flowchart of actions performed by a device to ensure that there will be sufficient energy for defined one or more use cases according to some, but not necessarily all, embodiments of the invention, in one aspect.

[0047] Figure 7 illustrates an exemplary controller that can be included in a device to cause any and / or all of the actions described and illustrated herein associated with the device to be performed. DETAILED DESCRIPTION

[0048] Various features of the invention will now be described with reference to the drawings, wherein like parts are identified with the same reference symbols.

[0049] Various aspects of the application will now be described in greater detail in connection with a number of exemplary embodiments. To facilitate an understanding of the application, many aspects of the application are described in terms of sequences of actions to be performed by elements of a computer system or other hardware capable of executing programmed instructions. It will be recognized that in each of the embodiments, the various actions could be performed by specialized circuits (e.g., analog and / or discrete logic gates interconnected to perform a specialized function), by one or more processors programmed with a set of instructions, or by a combination of both. The term "circuitry configured to" perform one or more described actions is used herein to refer to any such embodiment (i.e., one or more specialized circuits, one or more programmed processors, or any combination of these). Additionally, the application can also be embodied in a computer program product that includes a non-transitory computer readable medium having stored thereon instructions that, when executed by a processor, cause the processor to perform the techniques described herein. Thus, the various aspects of the application can be embodied in many different forms, and all such forms are contemplated to be within the scope of the application. For each of the aspects of the application, the embodiments described above and any of their equivalents can be referred to herein as "logic configured to" perform an action, or alternatively as "logic" that performs the action.

[0050] One aspect of embodiments of the application includes predicting whether a particular energy consuming activity will be required to be performed at a later time, wherein the energy consuming activity requires a first amount of energy.

[0051] In another aspect of some, but not necessarily all, embodiments of the application, the prediction that a particular energy consuming activity will be performed at a later time results in a current activation of one or more power saving functions that ensure that at least the first amount of energy will be stored in the battery when the particular energy consuming activity is initiated at the later time.

[0052] In another aspect of some, but not necessarily all, embodiments, the state information is used to predict at a current time whether an energy consuming activity will be performed by the device at a later time. The state information includes one or more of: a day of the week; a current time of day; and a current location of the first device.

[0053] The technical effect brought about by embodiments consistent with the present invention is to control one or more energy consuming activities within a device to reduce its energy consumption (e.g., by reducing the amount of activity or even stopping such activity) in order to ensure that a sufficient amount of energy will be stored and will be available when a future target use case is to be executed. To illustrate this, consider a use case in which an end user determines that the most important task for their wireless device is to be in full operation as a public transportation ticket validation when the user comes home from work in the evening. Embodiments consistent with the present invention are notified of this use case and take action to adjust the device's energy consumption during the day to ensure that sufficient energy remains in the device's battery in order to run the public transportation application at the expected time of coming home. This can mean, among other things, that, for example, enough energy needs to be saved in the device's battery in order to be able to run the device's display at a very high level of brightness in order to display a ticket code to a QR reader associated with public transportation at the expected time of the use case being activated.

[0054] There are many such use cases, the full list of which is far beyond the scope of this specification. Some non-limiting examples include:

[0055] • Given a smart watch capable of performing things such as activity tracking, display time, GPS location tracking, recording mobile payments, mobile key, etc., such a device can be configured a critical use case which can feature "unlock my car after I exercise outdoors."

[0056] In this scenario, an end user can drive their car to a place where they go for a run and use the smart watch during the exercise activity while still being able to guarantee that they will be able to use the smart watch to unlock the car at the car when they are done exercising without the risk of the battery running out of power due to high energy consumption based on GPS-based activity tracking during the exercise performed earlier. This is because the device is configured to limit activity tracking execution during the exercise activity to avoid completely draining the battery so that at the end of the activity, the end user will still be able to unlock the car.

[0057] • A smart phone can typically be used for a wide variety of functions, including mobile payments. Using the inventive techniques described herein, a user of such a device can set a critical use case which features "make sure I can use my phone to make my payment at the grocery store before I come home from work." The inventive techniques described herein will then ensure that the device saves sufficient energy during the user's entire workday to allow the payment application to run after shopping at the end of the day before coming home.

[0058] • A smartphone can be used as a modem and / or computer support for local data aggregation and data offloading, or similar use cases that the user considers vital. If such a use case is expected to occur at some time in the future, the present technology takes action to control other applications, screen use, etc. at the present time, in order to put these other uses in power saving mode, or even disable them, in order to perform the critical use case when the time in the future comes (if necessary to ensure that there is a sufficient amount of stored energy at the time in the future).

[0059] Reference will now be made to Figure 1 Aspects of embodiments consistent with the present invention will now be described, Figure 1 is a state transition diagram describing the actions of a device according to some, but not necessarily all, embodiments of the invention. In the initial state 101, 103, the device is configured with a use case definition and its requirements. As shown in the examples presented above, as well as below, some device activities that are of particular importance to the user of the device are particularly advantageous for the use case. The identification 101 of one or more use cases can be made by the user via an end user interface. Optionally (or additionally), the identification of the use case can be configured from an external network server function or similar.

[0060] In addition to the definition of the device activities associated with a given use case, the device also estimates the requirements for the use case 103. This includes obtaining the expected energy level that will be required to perform the use case. Such information can be obtained from historical usage statistics. Other methods can also be used, such as receiving estimation information from an external source (end user or configuration server data).

[0061] Estimating the requirements also includes estimating the time of future use for each identified use case.

[0062] Following this initial phase of operation, the device predicts whether any given use case will be performed at a time in the future within the current battery lifetime. For example, if the use case involves the user using the device to pay for public transportation after a day at work, the device will predict that the use case will not run if it is not a weekday (e.g. Saturday or Sunday). When such a prediction is made, the device transitions to the non-power saving state 105, in which the device works completely normally in its usual manner, without the need to perform any further special activities to save energy for the use case.

[0063] However, if the current state information (such as, but not limited to, the day of the week, the time of day, and the location of the device) leads to a prediction that the use case will be executed at a future time within the current battery lifetime, the device transitions to a regular use state 107. During the regular use state 107, the device functions completely normally. However, in addition to performing any functions that the user can require, the device also periodically enters a state 109 in which it performs battery level predictions. This can include updating estimates about whether and when the use case is likely to occur. It also involves comparing the expected required amount of energy for the use case to the estimate of the remaining battery lifetime to determine the probability that the use case demands will be supported at the time when the use case is expected to be executed.

[0064] As long as the device concludes that the expected energy usage between the current time and the future time of the predicted use case will not deplete the battery below the amount of energy that will be required to support the use case, the device can continue to operate in the normal use state 107, with periodic checks of the battery level predictions still being performed 109.

[0065] If it is not yet time to activate the use case, but the battery level predictions estimate that the current battery SOC (and possibly also the energy usage rate between the current time and the future time of the use case) will not leave the battery with a sufficient amount of stored energy to perform the use case, the device transitions to a power saving mode 111. The specific actions taken in the power saving mode 111 can vary from embodiment to embodiment, but in all instances the goal of the actions is to reduce power consumption sufficiently to ensure that the battery will retain a sufficient amount of stored energy to perform the use case at the estimated future time. Such actions include, but are not limited to, operating system power management, turning off or reducing power supply voltages to hardware components, and reducing clock frequencies. In some, but not necessarily all embodiments, energy consumption is reduced by deactivating some or almost all of the user interface hardware of the device (such as the screen, buttons), with user interface functions being delegated 113 to one or more secondary devices 115. Data and control signaling can be exchanged 117 between the primary device and the secondary devices 115 through, for example, short-range wireless signaling.

[0066] In another aspect of at least some embodiments consistent with the present invention, the power saving mode 111 is not a one-time set of power saving actions. Rather, even after the power saving step 111 has been activated, the device periodically performs battery level predictions 119. As before, this can include updating estimates about whether and when the use case is likely to occur. It also involves comparing the expected required amount of energy for the use case to the estimate of the remaining battery lifetime to determine the probability that the use case demands will be supported at the time when the use case is expected to be executed.

[0067] The device can remain in the cycle between power saving mode 111 and battery level prediction 119 as long as it is not yet time to activate the use case. In some alternative embodiments, if the SOC of the battery becomes acceptable and it is not expected that further energy saving steps need to be taken, the device can resume to normal use state 107.

[0068] At some point, it is time to run the critical use case, so the device transitions from one of the current states it is in (normal use state 107 or power saving mode 111) to critical use state 121.

[0069] Reference will now be made to Figure 2 Further aspects of embodiments of the invention are discussed, Figure 2 is a block diagram of a device 200 having a plurality of components that can be implemented in hardware, in software (either alone or running on one or more processors), or in a combination of both.

[0070] The device 201 comprises a battery 203 and a dynamic power saving activation function 205 that coordinates actions performed by other components, including:

[0071] - a use case identification component 207 (responsible for defining and storing use case definitions and their associated required energy levels)

[0072] - a component 209 responsible for battery level measurements and estimation of remaining battery life

[0073] - a component 211 for managing energy used by the device (e.g., controlling power saving modes)

[0074] In other aspects of some but not necessarily all embodiments, one or more of the dynamic power saving activation function 205, the use case identification component 207, the battery level measurement component 209, and the energy management component 211 reside within an application entity of the device. The application entity in the device can comprise operating system software active within the device that controls hardware and software usage. The components and function 205, 207, 209, and 211 can be separate functional entities, or two or more of them can be combined together, e.g., as one general purpose software function.

[0075] Aspects such as battery life estimation and energy saving features are individually known in conventional devices, and therefore need not be described in more detail here. Any such implementation can be used in conjunction with the aspects of the invention described herein.

[0076] Reference will now be made to Figure 3 Further aspects of some but not necessarily all embodiments of the invention are described, Figure 3is a flowchart of actions performed by a device in accordance with some, but not necessarily all, embodiments of the invention in an aspect that ensures sufficient energy for defined use case(s). In other aspects, Figure 3 The blocks shown in the middle can also be seen as representing an apparatus 300 (e.g. hard-wired or programmable circuitry or other processing means) for performing the actions described.

[0077] As indicated in the beginning of Figure 3 The process comprises identifying (step 301) one or more use cases that are considered (e.g. by a user of the device 201) to be critical in the sense that the user wants to guarantee that the battery 203 of the device will have sufficient stored energy when the use case is activated at some future time. Step 301 can comprise end-user interaction with the device (e.g. via a user interface) to configure an application (associated with the identified use case) that is to be executed and at what time it should be run.

[0078] The energy required to perform the critical use case at the estimated time is estimated (step 303). This estimation can be performed by one or more calculations based on data collected from the history of energy usage of the device. In other words, the device can comprise software and / or hardware functionality that stores a history of application usage over time and energy consumption experienced over time. Such energy usage statistics can be used to determine a typical amount of energy required to perform the identified use case. Alternatively, or in combination, end-user interaction can be utilized to determine the amount of energy required to support the use case. The user interaction can be, for example, via a user interface that enables a controlling user to set a target battery SOC or similar that should be available when the critical use case is to be activated.

[0079] The remaining battery life is estimated (step 305). Thereby, it can be estimated how much energy will still be stored in the battery when the critical use case is to be activated. Based on this, a decision is made as to whether optimization is needed (decision block 307). The estimation made in this step can use conventional battery life estimation methods, such as those commonly available in wireless battery-powered devices today. The estimation can be repeated several times in order to keep the estimated battery life up-to-date based on possible changes in battery consumption over time.

[0080] If the amount of energy that will be stored in the battery at the future time when the critical use case is expected to be run is less than the amount of energy associated with the critical use case, battery life optimization is needed (the "yes" path out of decision block 307). The device then determines the required level of energy conservation to ensure that the amount of energy for supporting the use case will be present when the use case is activated (step 309).

[0081] Based on the determined required energy conservation level, the device takes one or more energy saving actions (step 311). Several types of actions can be taken, for example, using conventional power saving mechanisms that are available to reduce the battery consumption of the wirelessly powered device. These actions are typically done in this step without any further end user interaction and thus, the energy saving activation is performed automatically to meet future critical use case requirements. However, information to the end user can be provided, for example, by presenting information about the energy saving actions on the device's display, or by sending such information to one or more (e.g., wirelessly) connected devices.

[0082] As a result of the energy saving actions taken in step 311, one or more functions or capabilities of the device can be reduced or disabled in order to reduce the energy consumption of the device. As a special case, the device can be turned off for a period of time to conserve battery energy and then be started again at or near the time of the estimated use.

[0083] The device 201 also periodically checks to see if the time has arrived when the critical use case is to be activated (decision block 313). If energy conservation is activated, this can follow step 311, or other instances can follow if battery life optimization is not required (the "No" path out of decision block 307). If the critical use case is not executed at this time (the "No" path out of decision block 313), the above-identified process is repeated, starting with the battery life estimation (step 305).

[0084] Otherwise, the critical use case is activated (step 315), and the energy saving activities are stopped (assuming that energy conservation is not required to continue for other use cases).

[0085] Reference will now be made to Figure 4 Additional aspects of some, but not necessarily all, embodiments of the invention will now be described. In such embodiments, the power saving actions include communicating with one or more (e.g., wirelessly) connected devices to inform the user of the power saving actions being taken. For example, a smart phone or other device 401 can be connected to an AR / VR headset 403 or a smart watch 405, and to conserve energy in the smart phone 401, the screen of the smart phone can be turned off. Instead, user interaction can be conducted via the headset 403 and / or the smart watch 405, such as presenting information to the end user. As one example of such information, the headset display can receive a message from the smart phone 401 that the smart phone 401 is temporarily switching to a power saving mode. Such message can then be presented to the end user via the headset display. In one or more examples, such message can be presented with instructions on how to override the power saving mode (i.e., to return to normal smart phone operation).

[0086] Enlisting one or more secondary devices 115, 403, 405 is an effective method of reducing energy consumption in the primary device, since, for example, a short-range wireless low-energy link (e.g. a Bluetooth Low Energy link) can be very easily maintained (e.g. "maintain" the link via a duty cycled connection) with very low energy consumption (on the order of approximately less than 0.1 mW on average). In contrast, activating a display / screen of a typical smartphone will consume (among other things, depending on the brightness level, etc.) several hundred mW or more. With such a large disparity, the primary device can maintain the low-energy link for a considerable amount of time before it will have consumed as much power as the screen would have consumed if it had been active for only about 30 seconds or so.

[0087] In another aspect of some, but not necessarily all embodiments consistent with the application, the probability of a critical use case occurring can be determined by the device. This probability estimate can be utilized in order to determine whether to trigger activation of the power saving mechanism. One example of a probability estimate can be done via geofence tracking, meaning that, for example, if a device is frequently entering a certain geofenced area, it is likely that a critical use case will be performed. If the device is not entering the geofenced area, it is likely that the critical use case will not be performed. Figure 3 The device in step 303 also maintains a log of location information associated with use case activity as part of the use case activity statistics. For example, if a determined critical use case is always performed within a certain geographic area, then if the device is located in a significantly different, remote area (especially if the device is not typically located in that remote area for a period of time prior to activation of the use case), it is likely that the critical use case will not be performed. Thus, based on the location of the device, the function can not activate any additional power saving features to meet the use case requirements.

[0088] In another aspect of some, but not necessarily all embodiments consistent with the application, and with reference to Figure 5 The energy saving function within the device 501, 503, 505 is supported by a network server 507 or other external information exchange entity that provides information to the device and receives data from the device.

[0089] For example, the network server 507 can support by providing information for determining what constitutes a critical use case. This is especially useful, for example, when the device 501, 503, 505 is a sensor device (e.g. an Internet of Things sensor) and there can be a specific time period in which it is critical to retrieve sensor data from the device. Such information can be centrally controlled and determined via the network server 507, and information for defining use cases can be sent from the network server 507 to the device 501, 503, 505.

[0090] In some further alternative embodiments, the network server 507 can support information for making energy estimates. In similar scenarios involving sensor devices or other machine type communication devices, statistics about device characteristics such as energy consumption can be captured and stored for multiple devices in the network server, and thus the relevant information can be provided from a central source via the network server 507. Thus, information for making energy estimates can be sent from the network server to the devices 501, 503, 505.

[0091] In further alternative features, the network server 507 can generally be used to control device software for energy saving functions (e.g., for determining which power saving features should be activated in order to save battery life). Such functions can be supported by the devices 501, 503, 505 by providing information and statistics from the devices 501, 503, 505 to the server 507 for future determination steps.

[0092] Reference will now be made to Figure 6 Some, but not necessarily all, aspects of this application will now be described with reference to the following figures: Figure 6 is a flowchart of actions performed by a device in accordance with some, but not necessarily all, embodiments of the application, in one aspect, that ensures sufficient energy for defined use case or use cases. In other aspects, Figure 6 The blocks shown in FIG. 6 can also be viewed as representing a device 600 (e.g., a hardwired or programmable circuit or other processing means) for performing the actions described.

[0093] As indicated at the outset in Figure 6 The illustrated process is for controlling power consumption of a first device, and includes predicting (step 601) at a current time whether an energy consuming activity will be performed by the first device at a later time, where performance of the energy consuming activity requires a first amount of energy. As previously noted, any given use case can or can not be invoked during a current battery life, and the parameters used for making the prediction can vary from use case to use case. For example, some, but not all, use cases depend on state information such as the day of the week. For a given use case, another factor that can or can not be relevant is the time of day. For a given use case, another factor that can or can not be relevant is a geographic location. For example, in this last instance, the state information for the device can include a current location of the first device. The prediction then includes, among other possible considerations, comparing the current location of the first device to historical geographic regions within which the energy consuming activity has been performed.

[0094] These factors are intended only for illustrative purposes, and are not meant to represent all possible factors that can be considered by the device in making the prediction.

[0095] The prediction is then evaluated by the device (decision block 603). If the use case is not predicted to occur (NO path out of decision block 603), then no special action needs to be taken, and processing returns to step 601.

[0096] On the other hand, if the energy consumption activity is predicted to be performed by the first device at a later time at the current time (YES path out of decision block 603), then the device activates an energy saving device operational mode that implements actions to ensure that at least a first amount of energy will be stored in the battery of the first device when the energy consumption activity is initiated at the later time (step 605).

[0097] At a later time, the energy consumption activity is performed (step 607).

[0098] In some embodiments, the energy saving device operational mode (e.g., step 605) can include determining whether the energy consumption rate of the first device needs to be reduced (decision block 609) (i.e., determining whether at least the first amount of energy will not be stored in the battery of the first device when the energy consumption activity is initiated at the later time). If no (NO path out of decision block 608), then no special action needs to be taken at this time. But in addition to this (YES path out of decision block 609), one possible response is to deactivate one or more currently active device activities (step 611). In some but not necessarily all embodiments, the deactivation is selectively performed, and the one or more currently active device activities are selected based on a prediction of how much energy will be saved when the one or more currently active device activities are deactivated.

[0099] Other aspects are considered to be within the scope of some but not necessarily all embodiments of the invention. For example, some embodiments can provide a way for an end user to override the energy saving functionality that is activated. In this case, a user interface (such as a button, touch screen interaction, or voice command) can be used to restore the device back to its normal operational mode, rather than targeting energy saving for future critical use cases.

[0100] In another aspect of some embodiments, when an action is to be taken to preserve battery life in order to meet future energy needs for one or more critical use cases, one or more information elements informing the action can be provided to the connected device. For example, a message can be sent wirelessly to the companion product informing the action taken. For example, such information can inform the user by presenting information on the display of the companion product, e.g., "This device is currently in power saving mode to support expected use of critical function 'XYZ'. Click button to override." Here "XYZ" refers to one or more use cases, such as unlocking a car door, a payment service, etc. In this example, there are two aspects, one aspect being informing the user via the second device that a power saving action is being taken in the first device; and another aspect in which the end user is given the ability to override the power saving, causing the device to revert to normal operation.

[0101] In another aspect of some but not necessarily all embodiments, in the phase of estimating future use, the device can perform an estimation of the likelihood that a use case will be performed during a particular battery cycle. In other words, the device can determine whether energy preservation that is normally performed during a battery cycle will actually be performed within that particular battery cycle. For example, the device can couple the anticipated use case with location information to determine the likelihood that the action is to be performed based on the current location information. For example, if the anticipated future use is to be performed at a certain geographic location, but the device is far away from that location, the likelihood of performing the critical use case is very low. Thus, the energy management can not consider that use case as likely to occur during that battery cycle.

[0102] In another aspect of some but not necessarily all embodiments, in the phase of taking action towards the device to preserve battery life in order to meet future energy needs, one or more power saving options can be identified, but only executed if explicitly selected. The selection can be made by input provided from an external source, such as but not limited to end user interaction.

[0103] Reference will now be made to Figure 7 Further aspects of embodiments consistent with the present invention are described, Figure 7 An exemplary controller 701 is shown, which can be included in a device to cause any and / or all of the actions described and shown herein to be performed in association with the device. In particular, the controller 701 includes circuitry configured to perform any one or any combination of the various functions described herein. For example, such circuitry can be a fully hardwired circuit (e.g., one or more application specific integrated circuits - "ASICs"). However, in Figure 7Depicted in the exemplary embodiment of FIG. 7 is a programmable circuit, which includes a processor 703 coupled to one or more memory devices 705 (e.g., random access memory, disk drive, optical drive, read-only memory, etc.) and an interface 707 that enables bidirectional communication with other elements of the device as described above. A complete list of possible other elements is beyond the scope of this specification.

[0104] The memory device 705 stores program means 709 (e.g., a set of processor instructions) configured to cause the processor 703 to control the other device elements in order to perform any of the aspects described herein. The memory device 705 can also store data (not shown) representing various constants and variables that processor 703 can utilize and / or generate while performing its functions, such as the functions specified by program means 709.

[0105] Embodiments consistent with aspects of the present invention provide numerous advantages over conventional techniques. Such advantages include, but are not limited to:

[0106] - providing the device with the ability to control the energy / power consumption of the device that is specifically tailored to meet the energy needs of a particular target use case

[0107] - providing the device with the ability to not only predict the likely timing of a future use case, but also to predict whether that use case is likely to occur within the current battery life, and in this way avoid unnecessarily disabling or reducing device functionality in cases where a future use case is unlikely to occur.

[0108] The present invention has been described with reference to particular embodiments. However, the person of ordinary skill in the art will readily appreciate that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The described embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Claims

1. A method for controlling the power consumption of a first device (201, 401, 501, 503, 505), the method comprising: Predict at the current time whether the energy consumption activity (103, 307, 601) will be performed by the first device (201, 401, 501, 503, 505) at a later time, wherein the execution of the energy consumption activity requires a first amount of energy; and When it is predicted at the current time that the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, an energy storage device operation mode (107, 111, 309, 311, 605) is activated. This energy storage device operation mode performs actions to ensure that at least the first amount of energy will be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy consumption activity is initiated at the later time.

2. The method according to claim 1, wherein, The prediction at the current time (103, 307, 601) of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: Using status information to predict at the current time whether the energy-consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, wherein the status information includes one or more of the following: One day of the week; The current time of day; and The current location of the first device (201, 401, 501, 503, 505).

3. The method according to claim 2, wherein, The status information includes the current position of the first device (201, 401, 501, 503, 505), and wherein using the status information to predict at the current time whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: The current location of the first device (201, 401, 501, 503, 505) is compared with the geographical area within which the energy-consuming activities were historically performed.

4. The method according to any one of the preceding claims, wherein, The operating modes (107, 111, 309, 311, 605) of the energy storage device include: In response to determining (609) that at least the first amount of energy will not be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy-consuming activity is initiated at the later time, deactivate one or more currently active device activities (611).

5. The method according to claim 4, wherein, Deactivating one or more currently active device activities (611) includes: The one or more currently active device activities are selected based on a prediction of how much energy will be saved when the one or more currently active device activities are deactivated (611).

6. The method according to any one of claims 4 to 5, wherein, Deactivating one or more currently active device activities (611) includes: Reduce the functionality of the first user interface of the first device (201, 401, 501, 503, 505).

7. The method according to claim 6, wherein, The functions of the first user interface include the brightness level of the output display of the first user interface.

8. The method according to any one of claims 6 to 7, wherein, The operating modes (107, 111, 309, 311, 605) of the energy storage device include: When performing input and / or output operations of the first device (201, 401, 501, 503, 505), the second user interface of the second device (405, 403) is used instead of the first user interface of the first device (201, 401, 501, 503, 505) via the wireless link (117) between the first device (201, 401, 501, 503, 505) and the second device (405, 403).

9. The method according to claim 8, wherein, The second device (405, 403) is one of the following: Smartwatch; Smartphone; Tablet computers; and Augmented Reality Headphones.

10. The method according to any one of claims 4 to 9, wherein, Deactivating one or more currently active device activities (611) includes: Reduce or deactivate the execution of one or more applications currently being executed by the first device (201, 401, 501, 503, 505).

11. The method according to any one of claims 4 to 10, wherein, Deactivating one or more currently active device activities (611) includes: The device is shut down for a period of time and then restored to operation after the period has expired.

12. The method according to any one of claims 4 to 11, wherein, Deactivating one or more currently active device activities (611) includes: Continue to receive input to the first device (201, 401, 501, 503, 505) to cancel the operation mode (107, 111, 309, 311, 605) of the energy storage device; and In response to receiving the input to the first device (201, 401, 501, 503, 505) to cancel the energy storage device operation mode (107, 111, 309, 311, 605), the device exits the energy storage device operation mode.

13. The method according to any one of the preceding claims, wherein, The prediction at the current time (103, 307, 601) of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: A request is sent to the server (507) via a telecommunications network for a prediction of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time.

14. The method according to any one of the preceding claims, comprising: When the first device (201, 401, 501, 503, 505) is operating in the energy storage device operation mode, a second prediction (119) is made as to whether at least the first amount of energy will be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy consumption activity is initiated at the later time. as well as If the second prediction (119) is that the first amount of energy will not be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy-consuming activity is started at the later time, then the execution of the power-consuming function by the first device (201, 401, 501, 503, 505) is further restricted.

15. The method according to any one of the preceding claims, comprising: The first amount of energy is determined based on data collected from the historical energy usage of the first devices (201, 401, 501, 503, 505).

16. The method according to any one of claims 1 to 14, comprising: ； Receive information related to the first quantity of energy from user input; as well as The first quantity of energy is determined based on the user input.

17. The method according to any one of the preceding claims, comprising: Output a notification to the output device that the device is taking energy-saving actions.

18. The method according to any one of the preceding claims, wherein, The first device (201, 401, 501, 503, 505) is one of the following: User equipment; Electronic tablet computer equipment; Smartwatch; Sensor devices; and Machine-type communication equipment.

19. A computer program (709) comprising instructions which, when executed by at least one processor (703), cause the at least one processor (703) to perform the method according to any one of claims 1 to 18.

20. A carrier comprising the computer program (709) according to claim 19, wherein, The carrier is one of electronic signals, optical signals, radio signals, and non-transient computer-readable storage media (705).

21. A device (300, 600, 701) for controlling the power consumption of a first device (201, 401, 501, 503, 505), the device (300, 600, 701) comprising circuitry configured to cause the first device (201, 401, 501, 503, 505) to perform: Predict at the current time whether the energy consumption activity (103, 307, 601) will be performed by the first device (201, 401, 501, 503, 505) at a later time, where, The execution of the energy-consuming activity requires a first amount of energy; as well as When it is predicted at the current time that the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, an energy storage device operation mode (107, 111, 309, 311, 605) is activated. This energy storage device operation mode performs actions to ensure that at least the first amount of energy will be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy consumption activity is initiated at the later time.

22. The apparatus (300, 600, 701) according to claim 21, wherein, The prediction at the current time (103, 307, 601) of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: Using status information to predict at the current time whether the energy-consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, wherein the status information includes one or more of the following: One day of the week; The current time of day; and The current location of the first device (201, 401, 501, 503, 505).

23. The apparatus (300, 600, 701) according to claim 22, wherein, The status information includes the current position of the first device (201, 401, 501, 503, 505), and wherein using the status information to predict at the current time whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: The current location of the first device (201, 401, 501, 503, 505) is compared with the geographical area within which the energy-consuming activities were historically performed.

24. The apparatus (300, 600, 701) according to any one of claims 21 to 23, wherein, The operating modes (107, 111, 309, 311, 605) of the energy storage device include: In response to determining (609) that at least the first amount of energy will not be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy-consuming activity is initiated at the later time, deactivate one or more currently active device activities (611).

25. The apparatus (300, 600, 701) according to claim 24, wherein, Deactivating one or more currently active device activities (611) includes: The one or more currently active device activities are selected based on a prediction of how much energy will be saved when the one or more currently active device activities are deactivated (611).

26. The apparatus (300, 600, 701) according to any one of claims 24 to 25, wherein, Deactivating one or more currently active device activities (611) includes: Reduce the functionality of the first user interface of the first device (201, 401, 501, 503, 505).

27. The apparatus (300, 600, 701) according to claim 26, wherein, The functions of the first user interface include the brightness level of the output display of the first user interface.

28. The apparatus (300, 600, 701) according to any one of claims 26 to 27, wherein, The operating modes (107, 111, 309, 311, 605) of the energy storage device include: When performing input and / or output operations of the first device (201, 401, 501, 503, 505), the second user interface of the second device (405, 403) is used instead of the first user interface of the first device (201, 401, 501, 503, 505) via the wireless link (117) between the first device (201, 401, 501, 503, 505) and the second device (405, 403).

29. The apparatus (300, 600, 701) according to claim 28, wherein, The second device (405, 403) is one of the following: Smartwatch; Smartphone; Tablet computers; and Augmented Reality Headphones.

30. The apparatus (300, 600, 701) according to any one of claims 24 to 29, wherein, Deactivating one or more currently active device activities (611) includes: Reduce or deactivate the execution of one or more applications currently being executed by the first device (201, 401, 501, 503, 505).

31. The apparatus (300, 600, 701) according to any one of claims 24 to 30, wherein, Deactivating one or more currently active device activities (611) includes: The device is shut down for a period of time and then restored to operation after the period has expired.

32. The apparatus (300, 600, 701) according to any one of claims 24 to 31, wherein, Deactivating one or more currently active device activities (611) includes: Continue to receive input to the first device (201, 401, 501, 503, 505) to cancel the operation mode (107, 111, 309, 311, 605) of the energy storage device; and In response to receiving the input to the first device (201, 401, 501, 503, 505) to cancel the energy storage device operation mode (107, 111, 309, 311, 605), the device exits the energy storage device operation mode.

33. The apparatus (300, 600, 701) according to any one of claims 21 to 32, wherein, The prediction at the current time (103, 307, 601) of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time includes: A request is sent to the server (507) via a telecommunications network for a prediction of whether the energy consumption activity will be performed by the first device (201, 401, 501, 503, 505) at the later time.

34. The apparatus (300, 600, 701) according to any one of claims 21 to 33, wherein, The circuit is further configured to cause the first device (201, 401, 501, 503, 505) to perform: When the first device (201, 401, 501, 503, 505) is operating in the energy storage device operation mode, a second prediction (119) is made as to whether at least the first amount of energy will be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy consumption activity is initiated at the later time. as well as If the second prediction (119) is that the first amount of energy will not be stored in the battery of the first device (201, 401, 501, 503, 505) when the energy-consuming activity is started at the later time, then the execution of the power-consuming function by the first device (201, 401, 501, 503, 505) is further restricted.

35. The apparatus (300, 600, 701) according to any one of claims 21 to 34, wherein, The circuit is further configured to cause the first device (201, 401, 501, 503, 505) to perform: The first amount of energy is determined based on data collected from the historical energy usage of the first devices (201, 401, 501, 503, 505).

36. The apparatus (300, 600, 701) according to any one of claims 21 to 34, wherein, The circuit is further configured to cause the first device (201, 401, 501, 503, 505) to perform: Receive information related to the first quantity of energy from user input; as well as The first quantity of energy is determined based on the user input.

37. The apparatus (300, 600, 701) according to any one of claims 21 to 36, wherein, The circuit is further configured to cause the first device (201, 401, 501, 503, 505) to perform: Output a notification to the output device that the device is taking energy-saving actions.

38. The apparatus (300, 600, 701) according to any one of claims 21 to 37, wherein, The first device (201, 401, 501, 503, 505) is one of the following: User equipment; Electronic tablet computer equipment; Smartwatch; Sensor devices; and Machine-type communication equipment.

Images