WO2025008053A1

WO2025008053A1 - Power management in a battery-powered device

Info

Publication number: WO2025008053A1
Application number: PCT/EP2023/068376
Authority: WO
Inventors: Rickard Ljung
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-07-04
Filing date: 2023-07-04
Publication date: 2025-01-09
Anticipated expiration: 2026-01-04

Abstract

Power consumption by a first device (201, 401, 501, 503, 505) is controlled by predicting (103, 307, 601), at a present time, whether an energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at a later time, wherein performance of the energy consuming activity requires a first amount of energy. When it is predicted, at the present time, that the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, then an energy preserving device operational mode (107, 111, 309, 311, 605) is activated. The energy preserving device operational mode (107, 111, 309, 311, 605) acts 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

POWER MANAGEMENT IN A BATTERY-POWERED DEVICE

BACKGROUND

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

Some or all of the following abbreviations are used in this specification:

Abbreviation Explanation

AR Augmented Reality

CPU Central Processing Unit

DVFS Dynamic Voltage and Frequency Scaling

GPS Global Positioning System

GPU Graphics Processing Unit

SOC State of Charge

VR Virtual Reality

Wireless consumer electronic devices such as smartphones, AR/VR headsets, wireless gaming remote controllers, and the like may be battery powered and thereby have a limited battery lifetime. As used herein, the term “battery lifetime” refers to the time it takes for a device to change from a state in which it has a fully charged battery to a state in which it has a fully drained battery. Also as used herein, the term “remaining battery lifetime” is the time it takes for a device having any current state of charge to a state in which it has a fully drained battery.

The battery lifetime of a device may vary a great deal, depending on how it is implemented. Relevant factors include properties of the device’s energy-consuming hardware components (e.g., CPUs, GPUs, Memories, sensors, power amplifiers, etc.) and the software implementations that determine how the hardware is utilized.

For such consumer electronic devices, the consumer’s usage habits may heavily impact the battery lifetime. As an example, a smartphone having no or only a few installed and activated applications by a first consumer may consume less energy compared to the same smartphone when a large number of applications are installed and activated. Similarly, a smartphone that is not interacted with (e.g., by a user touching buttons, screens, etc.), and thereby in a less active usage pattern, will likely consume less energy than the same smartphone when it is interacted with a lot using the available user interfaces.

A consumer may use the consumer electronic device in different use cases, depending on the device type, and some of these may be more important to the user than others. For example, using a smartphone or smartwatch for contactless payment (e.g., in a grocery store or at the bus on the way home from work), or for unlocking the user’s home entrance door when coming home may not require a large amount of battery energy but may, nonetheless, be very critical to the user in terms of the service being provided, so any disruption of that service should be avoided. By contrast, other uses of the device (e.g., supporting a casual 10 minutes of web browsing while waiting to catch a bus) may not be as important if full (or any) functionality cannot be provided. Thus, various use cases to which a device can be put have a wide range of possible importance levels, for example, with respect to how seriously a user is affected if a particular use case functionality cannot be provided when the user calls for it.

In a battery powered device, the ability to perform one or more applications associated with any given use case is heavily dependent on having sufficient energy stored in the battery when the use case is called into play. Energy conservation is therefore of great interest. Conventional technology exists for saving energy in battery powered devices, such as DVFS, hardware and software module deactivations (e.g., application deactivations), and settings adjustment (e.g., screen brightness settings). Different energy modes (e.g., power save modes) may be deployed to control one or more of such energy saving settings. Such battery lifetime optimizations may be directed at specific parameters such as setting a device screen brightness level to a fixed value, or setting a CPU clock rate. Optimizations may also be on a more general level, such as a user-activated energy saving mode in which more than one software setting may be configured for energy saving in an attempt to prolong battery life.

Besides approaches that require an express action by a user, battery stamina modes may be activated by software in a device, which activation being based on pre-defined activation rules (e.g., when reaching a certain remaining battery level threshold).

Battery lifetime estimation functionalities are also known in the art, in which a device may estimate the current SOC and a 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.

The document CN113220106A is understood to disclose battery lifetime estimation being coupled with a user preset target battery endurance time. A power saving mode to reach the target battery lifetime is set. The device in this way may dynamically adjust the power-saving mode level of a target application according to the historical operation information of the target application in order to meet a certain battery endurance time.

Conventional technology is inadequate for addressing the problem of ensuring that a device will have sufficient energy stored in its battery when a very important use case is to be activated. Such technology provides for battery lifetime estimations and battery lifetime optimizations. Activation of energy saving mode functionality is conventionally based on measured parameters, pre-set end user configurations, or on a set target battery lifetime. But none of these approaches ensure that sufficient power for a particular use case will be available in the future when that use case is called into play.

There is therefore a need for technology that addresses these and/or related problems regarding battery lifetime optimization when one or more particularly important use cases may potentially be required to be performed sometime in the future.

SUMMARY

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 the use of these terms does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

Moreover, reference letters may be provided in some instances (e.g., in the claims and summary) to facilitate identification of various steps and/or elements. However, the use of reference letters is not intended to impute or suggest that the so-referenced steps and/or elements are to be performed or operated in any particular order.

In accordance with one aspect of the present invention, the foregoing and other objects are achieved in technology (e.g., methods, apparatuses, nontransitory computer readable storage media, program means) that controls power consumption by a first device.

In an aspect of some but not necessarily all embodiments consistent with the invention, power control includes predicting, at a present time, whether an energy consuming activity will be performed by the 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 present time, that the energy consuming activity will be performed by the first device at the later time, then the device activates an energy preserving device operational mode that acts 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.

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

In yet another aspect of some but not necessarily all embodiments consistent with the invention, the state information includes the present location of the first device. Prediction can then include comparing the present location of the first device to a geographical area within which the energy consuming activity is historically performed.

In still another aspect of some but not necessarily all embodiments consistent with the invention, the energy preserving device operational mode comprises, in response to a determination that at least the first amount of energy will not be stored in the battery of the first device when the energy consuming activity is initiated at the later time, deactivating one or more currently active device activities.

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

In yet another aspect of some but not necessarily all embodiments consistent with the invention, deactivating the one or more currently active device activities comprises reducing a 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.

In still another aspect of some but not necessarily all embodiments consistent with the invention, the energy preserving device operational mode comprises using, via a wireless link between the first device and a second device, a second user interface of the second device instead of the first user interface of the first device when performing input and/or output operations of the first device. In some but not necessarily all embodiments, the second device is one of: a smartwatch; a smartphone; a tablet; and an extended reality headset. In another aspect of some but not necessarily all embodiments consistent with the invention, deactivating the one or more currently active device activities comprises reducing or deactivating execution of one or more application programs currently being executed by the first device.

In yet another aspect of some but not necessarily all embodiments consistent with the invention, deactivating the one or more currently active device activities comprises shutting down device operation for a period of time, and resuming device operation after expiration of the period of time.

In still another aspect of some but not necessarily all embodiments consistent with the invention, deactivating one or more currently active device activities comprises continuing to accept receipt of an input to the first device that cancels the energy preserving device operational mode; and leaving the energy preserving device operation mode in response to receipt of the input to the first device that cancels the energy preserving device operational mode.

In another aspect of some but not necessarily all embodiments consistent with the invention, predicting, at the present time, whether the energy consuming activity will be performed by the first device at the later time comprises communicating, to a server via a telecommunications network, a request for a prediction regarding whether the energy consuming activity will be performed by the first device at the later time.

In yet another aspect of some but not necessarily all embodiments consistent with the invention, power control of the first device comprises, when the first device is operating in the energy preserving device operation mode, making a second prediction whether at least the first amount of energy will be stored in the battery of the first device when the energy consuming activity is initiated at the later time; and 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 consuming activity is initiated at the later time, then further limiting performance by the first device of functions that consume power.

In still another aspect of some but not necessarily all embodiments consistent with the invention, power control of the first device comprises determining the first amount of energy based on data collected from historical energy usage of the first device.

In another aspect of some but not necessarily all embodiments consistent with the invention, power control of the first device comprises receiving, from a user input, information that relates to the first amount of energy; and determining the first amount of energy based on the user input. In yet another aspect of some but not necessarily all embodiments consistent with the invention, power control of the first device comprises outputting, to an output device, a notification that the device is taking an energy saving action.

In still another aspect of some but not necessarily all embodiments consistent with the invention, the first device is one of a user equipment; an electronic tablet device; a smartwatch; a sensor device; and a machine type communication device.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the invention will be understood by reading the following detailed description in conjunction with the drawings in which:

Figure l is a state transition diagram that describes actions of a device in accordance with some but not necessarily all inventive embodiments.

Figure 2 is a block diagram of a device configured to operate in accordance with exemplary embodiments consistent with the invention.

Figure 3 is, in one respect, a flowchart of actions performed by device for ensuring that there will be sufficient energy for a defined one or more use cases in accordance with some but not necessarily all inventive embodiments.

Figure 4 illustrates aspects of some inventive embodiments in which a device communicates with one or more (e.g., wirelessly) connected devices to inform a user about the power saving actions being taken by the device, and in some embodiments, to accept input supplied to the connected device(s).

Figure 5 is a schematic diagram illustrating embodiments in which the energy-preserving functionality within the device is supported by a network server 507 or other external information exchange entities that provide information to the device and receive data from the device.

Figure 6 is, in one respect, a flowchart of actions performed by device for ensuring that there will be sufficient energy for a defined one or more use cases in accordance with some but not necessarily all inventive embodiments.

Figure 7 shows an exemplary controller that may be included in a device to cause any and/or all of the herein-described and illustrated actions associated with that device to be performed. DETAILED DESCRIPTION

The various features of the invention will now be described with reference to the figures, in which like parts are identified with the same reference characters.

The various aspects of the invention will now be described in greater detail in connection with a number of exemplary embodiments. To facilitate an understanding of the invention, many aspects of the invention 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 suitable 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 alone, one or more programmed processors, or any combination of these). Moreover, the invention can additionally be considered to be embodied entirely within any form of non- transitory computer readable carrier, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein. Thus, the various aspects of the invention may be embodied in many different forms, and all such forms are contemplated to be within the scope of the invention. For each of the various aspects of the invention, any such form of embodiments as described above may be referred to herein as “logic configured to” perform a described action, or alternatively as “logic that” performs a described action.

An aspect of inventive embodiments includes predicting whether it will be called on to perform a particular energy consuming activity at a later time, wherein the energy consuming activity requires a first amount of energy.

In another aspect of some inventive embodiments, a prediction that the particular energy consuming activity will be performed at the later time causes present activation of one or more battery 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.

In another aspect of some but not necessarily all embodiments, state information is used to predict, at the present time, whether the energy consuming activity will be performed by the device at the later time. The state information comprises one or more of: a present day of the week; a present time of day; and a present location of the first device. A technical effect brought about by embodiments consistent with the invention is the control of one or more energy consuming activities within a device to reduce their 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 available when a future target use case is to be executed. To illustrate this point, consider a use case in which an end user determines that the very most important task for their wireless device is to be fully working as a public transport ticket verification when that user goes home from work in the evening.

Embodiments consistent with the invention are informed of this use case, and act to adapt energy consumption by the device during the day to ensure that sufficient energy remains stored in the device’s battery to run the public transport application at the expected time of traveling home. This could, among other things, mean for example that enough energy needs to be preserved in the device’s battery at the time the use case is expected to be activated to be able to run the device’s display at a very high brightness level to display a ticket code to a QR reader associated with the public transportation.

There are many such use cases, and a complete list of them is well beyond the scope of this description. Some non-limiting examples are:

• Given a smartwatch that is capable of performing things such as activity tracking, showing the time, GPS location tracking, logging mobile payments, mobile key, and the like, such a device can be configured with a critical use case that can be characterized as “unlock the car after my outdoor exercise”.

In such scenario, an end user can take their car to travel to a place for running and use the smartwatch during the exercise activity while still being assured that they will be able to come back to the car after finishing exercise to unlock the car with the smartwatch without risk that the battery will have run out due to high energy consumption from for example, GPS based activity tracking during the previously conducted exercise. This is because the device is configured to limit the activity tracking performance during the exercise activity to avoid draining the battery fully, so that at the end of the activity the end user will still be able to unlock the car.

• Smartphones can typically be used for a wide variety of functionalities including mobile payment. The user of such a device, using the inventive technology described herein, can set a critical use case that can be characterized as “Ensure that I can use my phone to make my grocery store payment before coming home from work”. The inventive technology described herein would then ensure that the device preserves sufficient energy throughout the user’s workday to allow the payment application to run after shopping at end of the day before coming home.

• Smartphones may be used as a modem and/or computer support for local data aggregation and data offloading or in similar use cases that the user considers to be critically important. If such use cases are anticipated to occur at some future time, the inventive technology takes actions to presently control other applications, screen usage, and the like to - if required to ensure a sufficient amount of stored energy at the future time -put these other uses into a power save mode or even disabling them in order to perform the critical use case when the future time arrives.

Aspects of embodiments consistent with the invention will now be described with reference to Figure 1, which is a state transition diagram that describes actions of a device in accordance with some but not necessarily all inventive embodiments. In initial states 101, 103, the device is configured with a use case definition and its requirements. As illustrated by examples set out above and also in the following, it is particularly advantageous for the use case to involve some device activity that is especially important to the user of the device. Identification 101 of one or more use cases can be conducted by a user via an end user interface. Alternatively (or in addition), identification of use cases can be configured from an external network server function or similar.

Along with the definition of device actions associated with a given use case, the device estimates requirements for the use case 103. This includes obtaining an expected energy level that will be required to carry out the use case. Such information can be obtained from historical usage statistics. Other methods, such as receiving estimation information from external sources (end user or configuration server data) may also be used.

Estimating requirements also includes estimating a future time of use for each of the identified use cases.

Following this initial phase of operation, the device predicts whether any of the given use cases will be performed at a future time within the current battery lifetime. For example, if a use case relates to a user using the device to pay for public transportation after a day at work, the device will predict that the use case will not be run if it is not a workday (e.g., a Saturday or Sunday). When such a prediction is made, the device transitions into a non-power preservation state 105, in which the device is fully functional in its usual way, without needing to perform any further special activities to preserve energy for the use case.

But if current state information, such as and without limitation, day of the week, time of day, and location of the device lead to a prediction that the use case will be performed at a future time within the current battery lifetime, the device transitions into a regular usage state 107. During the regular usage state 107, the device is fully functional. However, in addition to performing whatever functions the user might require, the device also regularly enters a state in which it makes battery level predictions 109. This can include updating an estimation regarding if and when the use case may occur. It also involves comparing the anticipated required amount of energy for the use case with an estimate of remaining battery life to determine a probability of supporting the use case requirement at the time when it is expected to be performed.

So long as the device concludes that an expected amount of energy usage between a current time and the predicted future time of the use case will not deplete the battery below the amount that will be needed to support the use case, the device can continue to operate in the regular usage state 107, still with regular checks of battery level prediction 109 being performed.

If it is not yet time to activate the use case but the battery level prediction estimates that a current battery SOC (and possibly also, rate of energy usage between a current time and the future time of the use case) will not leave the battery with a sufficient amount of stored energy to carry out the use case, then the device transitions to a power saving mode 111. The particular actions taken in power saving mode 111 can vary from one embodiment to the next, but in all instances the actions have the goal of reducing power consumption sufficiently to ensure that the battery will retain a sufficient amount of stored energy to carry out the use case at the estimated future time. Such actions include but are not limited to operating system power management switching off or reducing hardware components’ supply voltage and reducing clock frequency. In some but not necessarily all embodiments, energy consumption is reduced by deactivating some or nearly all of a device’s user interface hardware (e.g., screen, buttons) with user interface functionality being delegated 113 to one or more secondary devices 115. Data and control signaling can be exchanged 117 between the main and secondary devices 115 by means of, for example, short-range wireless signaling.

In another aspect of at least some embodiments consistent with the invention, power saving mode I l l is not a set of one-time power reducing actions. To the contrary, even after power saving steps have been activated 111, the device regularly performs battery level prediction 119. As discussed before, this can include updating an estimation regarding if and when the use case may occur. It also involves comparing the anticipated required amount of energy for the use case with an estimate of remaining battery life to determine a probability of supporting the use case requirement at the time when it is expected to be performed.

So long as it is not yet time to activate the use case, the device can remain in a loop between the power saving mode 111 and battery level prediction 119. In some alternative embodiments, it is possible for the device to revert back to regular usage state 107 if the battery’s SOC becomes acceptable and it is anticipated that no further power saving steps need be taken.

At some point, it is time to run the critical use case(s), so the device transitions to the critical use state 121 from whichever one of the present states (regular usage state 107 or power saving mode 111) it is in at that time.

Further aspects of inventive embodiments are now discussed with reference to Figure 2, which is a block diagram of a device 200 having a number of components that can be implemented in hardware, in software (alone or running on one or more processors), or a combination of both.

The device 201 includes a battery 203 and a dynamic power saving activation function 205 that coordinates the actions performed by other components that include:

A use case identification component 207 (Responsible for defining and storing a use case definition and its related required energy level)

A component 209 responsible for battery level measurements and estimating remaining battery lifetime

A component 211 for managing energy used by the device (e.g., controlling power saving modes)

In further 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 may encompass operating system software active within the device, controlling the hardware and software usage. The components and functions 205, 207, 209, and 211 may be separate functional entities, or two or more of them may be combined, for example, operating as one common software functionality.

Aspects such as battery lifetime estimation and power saving features are known individually in conventional devices and therefore need not be described here in greater detail. Any such implementations are usable in combination with inventive aspects described herein. Still further aspects of some but not necessarily all inventive embodiments will now be described with reference to Figure 3, which in one respect is a flowchart of actions performed by a device that ensures sufficient energy for a defined one or more use cases in accordance with some but not necessarily all inventive embodiments. In other respects, the blocks depicted in Figure 3 can also be considered to represent means 300 (e.g., hardwired or programmable circuitry or other processing means) for carrying out the described actions.

As shown beginning in Figure 3, the process includes identifying (step 301) one or more use cases that are considered (e.g., by a user of the device 201) critically important in the sense that the user wants to guarantee that the battery 203 of the device will have sufficient stored energy at the time that the use case is to be activated at some future time. Step 301 may include end user interaction (e.g., via a user interface) with the device to configure an application (associated with the identified use case) to be executed, and at what time it should be run.

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

The remaining battery life is estimated (step 305). From this, it is possible to estimate 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 regarding whether optimization is required (decision block 307). The estimations made in this step can use conventional battery lifetime estimation methods, such as those that are typically available in wireless battery powered devices today. The estimation can be repeated multiple times, in order to keep the estimated battery life up to date, based on possible variations in battery drain over time.

If the estimated amount of energy that will be stored in the battery at a future time when the critical use case is expected to be run is less than the amount of energy associated with that critical use case, then battery lifetime optimization is required (“Yes” path out of decision block 307). That device then determines a level of energy preservation that is required to ensure that the amount of energy to support the use case will be present when the use case is activated (step

309).

Based on the ascertained level of energy preservation that is required, the device takes one or more energy saving actions (step 311). Several types of actions may be taken using, for example, legacy battery saving mechanisms available to reduce battery drain from wireless battery powered devices. The actions are typically done within this step without needing any further end user interaction, and for this reason the energy saving activation to meet the future critical use case needs is performed automatically. Information to an end user may however be provided, for example, by presenting information about the energy saving action on a display of the device or by sending such information to one or more (e.g., wirelessly) connected devices.

As a result of the energy saving actions taken in step 311, one or more functionalities or capabilities of the device may be reduced or inactivated in order to reduce the device’s energy consumption. As a special case, the device may be shut down during a period of time in order to save battery energy, and then started again at the time or closer in time prior to the estimated usage.

The device 201 also regularly checks to see if the moment has arrived with the critical use case to be activated (decision block 313). This can follow step 311 if energy preservation is activated, or can follow in other instances when battery lifetime optimization is not required (“No” path out of decision block 307). If the critical use case is not to be performed at this time (“No” path out of decision block 313) then the above identified process repeats, beginning with battery lifetime estimation (step 305).

Otherwise, the critical use case is activated (step 315) and energy saving activity is discontinued (assuming that there is no continuing need to preserve energy for still further use cases).

Additional aspects of some but not necessarily all inventive embodiments will now be described with reference to Figure 4. In this class of embodiments, the power saving actions include communicating with one or more (e.g., wirelessly) connected devices to inform a user about the power saving actions being taken. As an example, a smartphone or other device 401 may be connected to an AR/VR headset 403 or smartwatch 405, and in order to save energy in the smartphone 401 the screen of the smartphone may be switched off. To take its place, user interaction such as presenting information to the end user can be made via the headset 403 and/or the smartwatch 405. As one example of such information, the headset 403 display may receive a message from the smartphone 401 that the smartphone 401 is temporarily switched into energy 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 together with instructions on how to override the energy saving mode (i.e., to revert back to ordinary smartphone operation).

Enlisting one or more secondary devices 115, 403, 405 is an effective way of reducing energy consumption in the primary device because, for example, a shortrange wireless low energy link (e.g., a BLUETOOTH low energy link) can very easily be maintained (e.g., via a duty cycled connection to “maintain” link) with very low energy consumption, somewhere on the order of less than 0.1 mW on average. By comparison, activating a display/screen of a typical smartphone will consume (depending on brightness level, among other things) a few hundreds of mW or more. With such a large disparity, the primary device can maintain a low energy link for quite some time before it will have consumed as many Wh of power as a screen would when active for only about 30 seconds or so.

In yet another aspect of some but not necessarily all embodiments consistent with the invention, a probability of critical use case occurrence can be determined by the device. Such probability estimation may be utilized in order to determine whether or not to trigger activation of the power saving mechanism. One example of probability estimation could be done via geographical activity tracking, meaning that the device such as in step 303 of Figure 3 also maintains, as part of use case activity statistics, a log of location information associated with the use case activity. If, for example, the determined critical use case is always performed within a certain geographical area, it is likely that the critical use case will not be performed if the device is located in a significantly different area far away (especially if the device is not typically located in the far away area in a period of time preceding activation of the use case). Hence, the function may not activate any extra energy saving features to meet the use case requirements based on the location of the device.

In yet another aspect of some but not necessarily all embodiments consistent with the invention, and with reference to Figure 5, the energy-preserving functionality within the device 501, 503, 505 is supported by a network server 507 or other external information exchange entities that provide information to the device and receive data from the device.

The network server 507 may, for example, support by supplying information for determining what constitutes a critical use case. This is helpful especially when, for example, the device 501, 503, 505 is a sensor device (e.g., an Internet of Things sensor), and there may be specific time periods when the sensor data is critical to be retrieved from the device. Such information may be controlled and determined centrally via a network server 507, and information for defining the use case can be transmitted to the device 501, 503, 505 from the network server 507.

The network server 507 may, in some further alternative embodiments, support with information for making energy estimations. In a similar scenario concerning sensor devices or other machine type communication devices, statistics on device characteristics such as energy consumption may be captured and stored for multiple devices in a network server, and relevant information can therefore be provided from the central source via a network server 507. Information for making energy estimations can therefore be transmitted to the device 501, 503, 505 from the network server.

In further alternative features, the network server 507 may be used in general to control the device software for the energy preserving functionality (e.g., for the determination of which energy saving features should be activated in order to preserve battery life). Such functionality can be supported by the device 501, 503, 505 by providing information and statistics from the device 501, 503, 505 to the server 507 for use in future determination steps.

Still further aspects of some but not necessarily all inventive embodiments will now be described with reference to Figure 6, which in one respect is a flowchart of actions performed by a device that ensures sufficient energy for a defined one or more use cases in accordance with some but not necessarily all inventive embodiments. In other respects, the blocks depicted in Figure 6 can also be considered to represent means 600 (e.g., hardwired or programmable circuitry or other processing means) for carrying out the described actions.

As shown beginning in Figure 6 the illustrated process is for controlling power consumption by a first device and includes predicting (step 601), at a present time, whether an energy consuming activity will be performed by the first device at a later time, wherein performance of the energy consuming activity requires a first amount of energy. As mentioned earlier, any given use case may or may not be invoked during a current battery lifetime, and the parameters for making the prediction can vary from one use case/application to the next. For example, some but not all use cases are dependent on state information, such as what day of the week it is. Another factor that may or may not be relevant for a given use case is time of day. And still another factor that may or may not be relevant for a given use case is geographic location. In this last instance, for example, the device’s state information can include the present location of the first device. Prediction then includes, among other possible considerations, comparing the present location of the first device to a geographical area within which the energy consuming activity is historically performed. These factors are intended only for purposes of illustration, and do not represent all possible factors that can be considered by the device when making the prediction.

The prediction is then assessed 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 actions need be taken, and processing reverts back to step 601.

If, on the other hand, it is predicted at the present time that the energy consuming activity will be performed by the first device at the later time (“Yes” path out of decision block 603), then the device activates an energy preserving device operational mode that acts 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 (Step 605).

Sometime later, the energy consuming activity is performed (step 607).

Looking at some aspects in further detail, the energy preserving device operational mode (e.g., step 605) can, in some embodiments, comprise determining whether there is a need to reduce the first device’s rate of energy consumption (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 consuming activity is initiated at the later time. If there is not (“No” path out of decision block 609), then no special actions need be taken at this time. But otherwise (“Yes” path out of decision block 609), one possible response is deactivating one or more currently active device activities (step 611). In some but not necessarily all embodiments, deactivation is done selectively, with selection of the one or more currently active device activities being based on a prediction of how much energy will be saved when the one or more currently active device activities are deactivated.

Further aspects are contemplated to be within the scope of some but not necessarily all inventive embodiments. For example, some embodiments may provide the end user with a way to override an activated energy saving functionality. In such case, a user interface such as button, touchscreen interaction, or voice command may be used to revert the device back to its ordinary mode of operation, not targeting to preserve energy for a future critical use case.

In another aspect of some embodiments, when an action is to be taken to preserve battery life in order to meet the future energy needs of one or more critical use cases, one or more information elements informing about the action may be provided to connected devices. For example, a message can be sent wirelessly to a companion product informing about the action taken. Such information may, for example, inform a user by presenting information on a display of the companion product, for example: “This device is currently in energy saving mode to support an expected use of a key functionality ‘XYZ’. Click button to override.” Here “XYZ” refers to one or more use cases such as unlocking the car door, payment service, and the like. In this example, there are two aspects, one being to inform the user, via a second device, about the power saving actions being taken in the first device; and another aspect in which an end user is given the ability to override the power saving, causing the device to revert to ordinary operation.

In another aspect of some but not necessarily all embodiments, at the stage of estimating a future usage, the device may perform an estimation of the likelihood that the use case will be performed during the specific battery cycle. In other words, the device may determine whether the energy preservation typically performed during battery cycles actually will be performed within this particular battery cycle. As an example the device may couple the expected use case to location information, to determine likelihood of the action to be performed based on current location information. For example, if the future usage is expected to be performed at a certain geographical location but the device is a large distance away from such location, the likelihood of performing the critical use case is very low. Hence, the energy management may not consider this use case as being likely to occur during this battery cycle.

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

Further aspects of embodiments consistent with the invention will now be described with reference to Figure 7, which shows an exemplary controller 701 that may be included in a device to cause any and/or all of the herein-described and illustrated actions associated with that device to be performed. In particular, the controller 701 includes circuitry configured to carry out any one or any combination of the various functions described herein. Such circuitry could, for example, be entirely hard-wired circuitry (e.g., one or more Application Specific Integrated Circuits - “ASICs”). Depicted in the exemplary embodiment of Figure 7, however, is programmable circuitry, comprising a processor 703 coupled to one or more memory devices 705 (e.g., Random Access Memory, Magnetic Disc Drives, Optical Disk Drives, Read Only Memory, etc.) and to an interface 707 that enables bidirectional communication with other elements of a device as described above. A complete list of possible other elements is beyond the scope of this description. The memory device(s) 705 store program means 709 (e.g., a set of processor instructions) configured to cause the processor 703 to control other device elements so as to carry out any of the aspects described herein. The memory device(s) 705 may also store data (not shown) representing various constant and variable parameters as may be needed by the processor 703 and/or as may be generated when carrying out its functions such as those specified by the program means 709.

Embodiments consistent with aspects of the invention provide a number of advantages over conventional technology. Such advantages include, without limitation:

A device is provided an ability to control energy/power consumption by the device specifically tailored to meet the energy needs of a specific targeted use case

A device is provided an ability to predict not only a possible timing of a future use case, but also whether the use case is likely to occur within a current battery lifetime, and in this way avoid unnecessarily disabling or degrading device functionality if the future use case is not likely to occur.

The invention has been described with reference to particular embodiments. However, it will be readily apparent to those skilled in the art that it is possible to embody the invention in specific forms other than those of the embodiment described above. Thus, the described embodiments are merely illustrative and should not be considered restrictive in any way. The scope of the invention is further illustrated by the appended claims, rather than only by the preceding description, and all variations and equivalents which fall within the range of the claims are intended to be embraced therein.

Claims

CLAIMS:

1. A method of controlling power consumption by a first device (201, 401, 501, 503, 505), the method comprising: predicting (103, 307, 601), at a present time, whether an energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at a later time, wherein performance of the energy consuming activity requires a first amount of energy; and when it is predicted, at the present time, that the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, then activating an energy preserving device operational mode (107, 111, 309, 311, 605) that acts 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.

2. The method of claim 1, wherein predicting (103, 307, 601), at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: using state information to predict, at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, wherein the state information comprises one or more of: a present day of the week; a present time of day; and a present location of the first device (201, 401, 501, 503, 505).

3. The method of claim 2, wherein the state information includes the present location of the first device (201, 401, 501, 503, 505), and wherein using the state information to predict, at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: comparing the present location of the first device (201, 401, 501, 503, 505) to a geographical area within which the energy consuming activity is historically performed.

4. The method of any one of the previous claims, wherein the energy preserving device operational mode (107, 111, 309, 311, 605) comprises: in response to a determination (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, deactivating one or more currently active device activities (6H).

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

6. The method of any one of claims 4 through 5, wherein deactivating the one or more currently active device activities (611) comprises: reducing a functionality of a first user interface of the first device (201, 401, 501, 503, 505).

7. The method of claim 6, wherein the functionality of the first user interface includes a brightness level of an output display of the first user interface.

8. The method of any one of claims 6 through 7, wherein the energy preserving device operational mode (107, 111, 309, 311, 605) comprises: using, via a wireless link (117) between the first device (201, 401, 501, 503, 505) and a second device (405, 403), a second user interface of the second device (405, 403) instead of the first user interface of the first device (201, 401, 501, 503, 505) when performing input and/or output operations of the first device (201, 401, 501, 503, 505).

9. The method of claim 8, wherein the second device (405, 403) is one of: a smartwatch; a smartphone; a tablet; and an extended reality headset.

10. The method of any one of claims 4 through 9, wherein deactivating the one or more currently active device activities (611) comprises: reducing or deactivating execution of one or more application programs currently being executed by the first device (201, 401, 501, 503, 505).

11. The method of any one of claims 4 through 10, wherein deactivating the one or more currently active device activities (611) comprises: shutting down device operation for a period of time, and resuming device operation after expiration of the period of time.

12. The method of any one of claims 4 through 11, wherein deactivating one or more currently active device activities (611) comprises: continuing to accept receipt of an input to the first device (201, 401, 501, 503, 505) that cancels the energy preserving device operational mode (107, 111, 309, 311, 605); and leaving the energy preserving device operation mode in response to receipt of the input to the first device (201, 401, 501, 503, 505) that cancels the energy preserving device operational mode (107, 111, 309, 311, 605).

13. The method of any one of the previous claims, wherein predicting (103, 307, 601), at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: communicating, to a server (507) via a telecommunications network, a request for a prediction regarding whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time.

14. The method of any one of the previous claims, comprising: when the first device (201, 401, 501, 503, 505) is operating in the energy preserving device operation mode, making a second prediction (119) 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 consuming activity is initiated at the later time; and 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 initiated at the later time, then further limiting performance by the first device (201, 401, 501, 503, 505) of functions that consume power.

15. The method of any one of the previous claims, comprising: determining the first amount of energy based on data collected from historical energy usage of the first device (201, 401, 501, 503, 505).

16. The method of any one of claims 1 through 14, comprising; receiving, from a user input, information that relates to the first amount of energy; and determining the first amount of energy based on the user input.

17. The method of any one of the previous claims, comprising: outputting, to an output device, a notification that the device is taking an energy saving action.

18. The method of any one of the previous claims, wherein the first device (201, 401, 501, 503, 505) is one of: a user equipment; an electronic tablet device; a smartwatch; a sensor device; and a machine type communication device.

19. A computer program (709) comprising instructions that, when executed by at least one processor (703), causes the at least one processor (703) to carry out the method according to any one of claims 1 through 18.

20. A carrier comprising the computer program (709) of claim 19, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a non-transitory computer readable storage medium (705).

21. An apparatus (300, 600, 701) for controlling power consumption by a first device (201, 401, 501, 503, 505), the apparatus (300, 600, 701) comprising circuitry configured to cause the first device (201, 401, 501, 503, 505) to perform: predicting (103, 307, 601), at a present time, whether an energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at a later time, wherein performance of the energy consuming activity requires a first amount of energy; and when it is predicted, at the present time, that the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, then activating an energy preserving device operational mode (107, 111, 309, 311, 605) that acts 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.

22. The apparatus (300, 600, 701) of claim 21, wherein predicting (103, 307, 601), at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: using state information to predict, at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time, wherein the state information comprises one or more of: a present day of the week; a present time of day; and a present location of the first device (201, 401, 501, 503, 505).

23. The apparatus (300, 600, 701) of claim 22, wherein the state information includes the present location of the first device (201, 401, 501, 503, 505), and wherein using the state information to predict, at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: comparing the present location of the first device (201, 401, 501, 503, 505) to a geographical area within which the energy consuming activity is historically performed.

24. The apparatus (300, 600, 701) of any one of claims 21 through 23, wherein the energy preserving device operational mode (107, 111, 309, 311, 605) comprises: in response to a determination (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, deactivating one or more currently active device activities (6H).

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

26. The apparatus (300, 600, 701) of any one of claims 24 through 25, wherein deactivating the one or more currently active device activities (611) comprises: reducing a functionality of a first user interface of the first device (201, 401, 501, 503, 505).

27. The apparatus (300, 600, 701) of claim 26, wherein the functionality of the first user interface includes a brightness level of an output display of the first user interface.

28. The apparatus (300, 600, 701) of any one of claims 26 through 27, wherein the energy preserving device operational mode (107, 111, 309, 311, 605) comprises: using, via a wireless link (117) between the first device (201, 401, 501, 503, 505) and a second device (405, 403), a second user interface of the second device (405, 403) instead of the first user interface of the first device (201, 401, 501, 503, 505) when performing input and/or output operations of the first device (201, 401, 501, 503, 505).

29. The apparatus (300, 600, 701) of claim 28, wherein the second device (405, 403) is one of: a smartwatch; a smartphone; a tablet; and an extended reality headset.

30. The apparatus (300, 600, 701) of any one of claims 24 through 29, wherein deactivating the one or more currently active device activities (611) comprises: reducing or deactivating execution of one or more application programs currently being executed by the first device (201, 401, 501, 503, 505).

31. The apparatus (300, 600, 701) of any one of claims 24 through 30, wherein deactivating the one or more currently active device activities (611) comprises: shutting down device operation for a period of time, and resuming device operation after expiration of the period of time.

32. The apparatus (300, 600, 701) of any one of claims 24 through 31, wherein deactivating one or more currently active device activities (611) comprises: continuing to accept receipt of an input to the first device (201, 401, 501, 503, 505) that cancels the energy preserving device operational mode (107, 111, 309, 311, 605); and leaving the energy preserving device operation mode in response to receipt of the input to the first device (201, 401, 501, 503, 505) that cancels the energy preserving device operational mode (107, 111, 309, 311, 605).

33. The apparatus (300, 600, 701) of any one of claims 21 through 32, wherein predicting (103, 307, 601), at the present time, whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time comprises: communicating, to a server (507) via a telecommunications network, a request for a prediction regarding whether the energy consuming activity will be performed by the first device (201, 401, 501, 503, 505) at the later time.

34. The apparatus (300, 600, 701) of any one of claims 21 through 33, wherein the circuitry 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 preserving device operation mode, making a second prediction (119) 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 consuming activity is initiated at the later time; and 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 initiated at the later time, then further limiting performance by the first device (201, 401, 501, 503, 505) of functions that consume power.

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

36. The apparatus (300, 600, 701) of any one of claims 21 through 34, wherein the circuitry is further configured to cause the first device (201, 401, 501, 503, 505) to perform: receiving, from a user input, information that relates to the first amount of energy; and determining the first amount of energy based on the user input.

37. The apparatus (300, 600, 701) of any one of claims 21 through 36, wherein the circuitry is further configured to cause the first device (201, 401, 501, 503, 505) to perform: outputting, to an output device, a notification that the device is taking an energy saving action.

38. The apparatus (300, 600, 701) of any one of claims 21 through 37, wherein the first device (201, 401, 501, 503, 505) is one of: a user equipment; an electronic tablet device; a smartwatch; a sensor device; and a machine type communication device.