Latency-Based Energy Storage Device Selection

Abstract

Latency-based selections of energy storage devices are described herein. In implementations, latency behavior of computing tasks performed by a computing device is predicted for a period of time. Based on the predicted latency behavior of the computing device over the period of time, an assessment is made regarding which of multiple heterogeneous energy storage devices are most appropriate to service the system workload. For example, high energy density devices may be favored for latency sensitive tasks whereas high energy density devices may be favored when latency sensitivity is not a concern. A combination of energy storage devices to service the current workload is selected based upon the latency considerations and then power supply settings are adjusted to cause supply of power from the selected combination of energy storage devices during the time period.

Description

BACKGROUND

As technology has advanced, mobile computing devices have become increasingly commonplace. Mobile computing devices provide various functionality to users, allowing the user to interact with the device to check email, surf the web, compose text messages, interact with applications, and so on. One challenge that faces developers of mobile computing devices is efficient power management and extension of battery life. For example, extended processing of tasks by processors at or near capacity may drain the device battery, causing the device to shut down. Various power management strategies may be applied to control processor and battery utilization generally at the expense of overall device performance. If power management implemented for a device fails to strike a good balance between performance and battery life, user dissatisfaction with the device and manufacturer may result.

SUMMARY

In accordance with one or more embodiments, in a computing device having multiple heterogeneous energy storage devices, latency behavior of computing tasks performed by a computing device is predicted for a period of time. Based on the predicted latency behavior of the computing device over the period of time, an assessment is made regarding which of the multiple heterogeneous energy storage devices are most appropriate to service the system workload. For example, high power density devices may be favored for latency sensitive tasks whereas high energy density devices may be favored when latency sensitivity is not a concern. A combination of energy storage devices to service the current workload is selected based upon the latency considerations and then power supply settings are adjusted to cause supply of power from the selected combination of energy storage devices during the time period. This may involve setting a power ratio to control power draw from the multiple heterogeneous energy storage devices as designated for the predicted latency behavior.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an operating environment in accordance with one or more embodiments.

FIG. 2 depicts example details of a computing device having an energy storage device system with heterogeneous energy storage devices in accordance with one or more implementations.

FIG. 3 depicts one illustrative example arrangement of an energy storage device system having multiple energy storage devices that are battery cells.

FIG. 4 depicts example details of a system having heterogeneous energy storage devices in accordance with one or more implementations.

FIG. 5 is a flow diagram that describes details of an example procedure for latency-based energy storage device selection in accordance with one or more implementations

FIG. 6 is a flow diagram that describes details of another example procedure for latency-based energy storage device selection in accordance with one or more implementations.

FIG. 7 illustrates an example system that includes an example computing device that is representative of one or more computing systems and/or devices that may implement the various techniques described herein.

DETAILED DESCRIPTION

Overview

Latency-based energy storage device selection is described for a device having an energy storage device system with heterogeneous energy storage devices, such as heterogeneous battery cells. The heterogeneous energy storage devices include two or more energy storage devices having various different characteristics such as different sizes, capacities, technologies, chemistries, shapes, state of charge (SOC), age, temperature, cycle counts, and so forth. These different characteristics result in different energy storage devices being better suited for different types of operations and scenarios. For example, one energy storage device may be a high power density device more efficient at providing larger amounts of energy over shorter amounts of time (e.g., during latency sensitive tasks such as video processing) and another energy storage device may be a high energy density device more efficient at providing smaller amounts of energy over longer amounts of time (e.g., while a device is in a low-power usage or energy saving mode). Generally, a high power density device charges fast and are capable of supplying a high power output. In contrast, a high energy density device is designed to operate efficiently, but provides lower power output and may be more susceptible to aging and degradation from repeated charge cycles.

The techniques discussed herein use latency behavior information regarding applications, computing tasks, interaction scenarios and/or past usage of a computing device to assess latency sensitivity of a workload and adjust power draws across multiple heterogeneous energy storage devices. Adjusting the combination of storage devices used for different levels of latency sensitivity as discussed in this document improves performance and efficiency of the energy storage device system both in the short term for handling latency sensitive tasks and over time as individual devices age and cycle counts increase.

In the discussion that follows, a section titled “Operating Environment” is provided and describes one example environment in which one or more implementations can be employed. Following this, a section titled “Latency-Based Energy Storage Device Selection System Details” describes example details and procedures in accordance with one or more implementations. Last, a section titled “Example System” describes example computing systems, components, and devices that can be utilized for one or more implementations of latency-based energy storage device selection.

Operating Environment

FIG. 1 illustrates an operating environment in accordance with one or more embodiments, generally at 100. The environment 100 includes a computing device 102 having a processing system 104 with one or more processors and devices (e.g., CPUs, GPUs, microcontrollers, hardware elements, fixed logic devices, etc.), one or more computer-readable media 106, an operating system 108, and one or more applications 110 that reside on the computer-readable media and which are executable by the processing system. The processing system 104 may be configured to include multiple independent processors configured in parallel or in series and one or more multi-core processing units. A multi-core processing unit may have two or more processors (“cores”) included on the same chip or integrated circuit. In one or more implementations, the processing system 104 may include multiple processing cores that provide a range of performance capabilities, processing efficiencies, and power usage characteristics.

The processing system 104 may retrieve and execute computer-program instructions from applications 110 to provide a wide range of functionality to the computing device 102, including but not limited to gaming, office productivity, email, media management, printing, networking, web-browsing, and so forth. A variety of data and program files related to the applications 110 can also be included, examples of which include game files, office documents, multimedia files, emails, data files, web pages, user profile and/or preference data, and so forth.

The computing device 102 can be embodied as any suitable computing system and/or device such as, by way of example and not limitation, a gaming system, a desktop computer, a portable computer, a tablet or slate computer, a handheld computer such as a personal digital assistant (PDA), a cell phone, a set-top box, a wearable device (e.g., watch, band, glasses, etc.), and the like. For example, as shown in FIG. 1 the computing device 102 can be implemented as a television client device 112, a computer 114, and/or a gaming system 116 that is connected to a display device 118 to display media content. Alternatively, the computing device may be any type of portable computer, mobile phone, or portable device 120 that includes an integrated display 122. A computing device may also be configured as a wearable device 124 that is designed to be worn by, attached to, carried by, or otherwise transported by a user. Examples of wearable devices 124 depicted in FIG. 1 include glasses, a smart band or watch, and a pod device such as clip-on fitness device, media player, or tracker. Other examples of wearable devices 124 include but are not limited to badges, a key fob, an access card, and a ring, an article of clothing, a glove, or a bracelet, to name a few examples. Any of the computing devices can be implemented with various components, such as one or more processors and memory devices, as well as with any combination of differing components. One example of a computing system that can represent various systems and/or devices including the computing device 102 is shown and described below in relation to FIG. 7.

The computer-readable media can include, by way of example and not limitation, all forms of volatile and non-volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. Computer-readable media can include both “computer-readable storage media” and “communication media,” examples of which can be found in the discussion of the example computing system of FIG. 7.

The computing device 102 may also include a power manager 126 that includes or makes use of a latency estimator 127, and an energy storage device system 128 having multiple heterogeneous energy storage devices that operate as described above and below. The power manager 126 represents functionality operable to manage power for the computing device in various ways. For example the power manager 126 may assess system-wide power management considerations and manage availability heterogeneous energy storage devices, processors, and/or processing cores based on the assessment. In one or more implementations, the power manager 126 is configured to implement a switching policy established based on power management considerations to control the battery system 128. The switching policy depends at least upon latency considerations as discussed herein.

In this context, the latency estimator 127 represents functionality that the power manager may include, invoke, or otherwise make use of to determine latency behavior for a current workload (also referred to herein as usage behavior) of the computing device 102 and manage heterogeneous energy storage devices of the energy storage device system 128 accordingly. This may involve analyzing factors including but not limited to energy storage device characteristics, latency sensitivity of different tasks, application specific latency considerations, estimated or predicted future usage and latency behavior of the computing device 102, estimated future energy usage of the computing device 102 over a given time period (e.g., a day), and so forth.

The assessment may further involve analyzing other factors including but not limited to, charge levels/states, the device power state, actual and expected workloads, thermal conditions, user presence, processor/core utilization, application context, device context, priority, contextual clues, and other suitable performance metrics that may be used to drive power management decisions at the system level. Different types of applications, tasks, and scenarios may be assigned pre-computed latency sensitivity values that are used by the latency estimator 127 to determine latency behavior for a current workload. Latency estimator 127 may additionally operate to estimate or predict latency sensitivity values “on-demand” using the various factors when pre-computed values are not available.

The power manager 126 is further configured to apply the switching policy to adjust the performance of the battery system 128 based on the assessment of system-wide performance metrics and conditions (e.g., analyzing an operational context for the device), including at least latency sensitivity associated with current workload. Applying the switching policy may involve controlling modes of different energy storage devices (e.g., cells), states of individual energy storage devices and/or availability of heterogeneous energy storage devices included with an energy storage system 128. For example, the power manager 126 is operable to communicate control signals or otherwise interact with the energy storage system 128 to direct operation of switching hardware to switch between heterogeneous battery cells to service the load in accordance with the switching policy and analysis of the operational context.

As mentioned, the energy storage device system 128 is configured to include multiple heterogeneous energy storage devices. Energy storage devices may be configured in various ways and be implemented in various combinations of as discussed in greater detail below. The power manager 126 and energy storage device system 128 may be provided using any suitable combination of hardware, software, firmware, and/or logic devices. As illustrated, the power manager 126 and energy storage device system 128 may be configured as separate, standalone systems. In addition or alternatively, the power manager 126 may also be configured as a system or module that is combined with the operating system 108 or implemented via a controller or other component of the energy storage device system 128. Details regarding these and other aspects of latency-based energy storage device selection are discussed in the following section.

The environment 100 further depicts that the computing device 102 may be communicatively coupled via a network 130 to a service provider 132, which enables the computing device 102 to access and interact with various resources 134 made available by the service provider 132. The resources 134 can include any suitable combination of content and/or services typically made available over a network by one or more service providers. For instance, content can include various combinations of text, video, ads, audio, multi-media streams, applications, animations, images, webpages, and the like. Some examples of services include, but are not limited to, an online computing service (e.g., “cloud” computing), an authentication service, web-based applications, a file storage and collaboration service, a search service, messaging services such as email and/or instant messaging, and a social networking service.

Having described an example operating environment, consider now example details and techniques associated with one or more implementations of latency-based energy storage device selection.

Latency-Based Energy Storage Device Selection System Details

To further illustrate, consider the discussion in this section of example devices, components, procedures, and implementation details that may be utilized to provide latency-based energy storage device selection as described herein. In general, functionality, features, and concepts described in relation to the examples above and below may be employed in the context of the example procedures described in this section. Further, functionality, features, and concepts described in relation to different figures and examples in this document may be interchanged among one another and are not limited to implementation in the context of a particular figure or procedure. Moreover, blocks associated with different representative procedures and corresponding figures herein may be applied together and/or combined in different ways. Thus, individual functionality, features, and concepts described in relation to different example environments, devices, components, figures, and procedures herein may be used in any suitable combinations and are not limited to the particular combinations represented by the enumerated examples in this description.

Example Device

FIG. 2 depicts generally at 200 example details of a computing device 102 having an energy storage device system 128 with heterogeneous energy storage devices in accordance with one or more implementations. Computing device 102 also includes processing system 104, computer readable media 106, operating system 108 and applications 110 as discussed in relation to FIG. 1. In the depicted example, a power manager 126 is also shown as being implemented as a component of the operating system 108.

By way of example and not limitation, the energy storage device system 128 is depicted as having energy storage devices 202 and an energy storage device controller 204. The energy storage devices 202 are representative of various different kinds of energy storage devices that may be included with the computing device 102. These energy storage devices can include, for example, battery cells, supercapacitors, and so forth. It should be noted that these energy storage devices include various devices that store energy as opposed to being an external plug-in AC power source. As mentioned, energy storage devices 202 include energy storage devices having different characteristics such as different sizes/capacities, chemistries, battery technologies, shapes, state of charge (SOC), age, temperature, and so forth (heterogeneous energy storage devices). The different characteristics may include different “properties” of the energy storage devices (e.g., chemistries, sizes, capacities) and different “states” in which the energy storage devices are currently operating (e.g., “SoC”, age, temperature). Thus, in the context of the techniques described herein heterogeneous energy storage devices may include either or both of different types of devices designed with different properties and devices having the same or similar properties by design, but having different state characteristics.

Accordingly, the energy storage device system 128 includes a diverse combination of multiple energy storage devices at least some of which have different characteristics one to another. However, it should be noted that some energy storage devices 202 may be the same and still be part of the energy storage device system 128 (e.g., the energy storage devices 202 may include three battery cells, two of which have the same characteristics and a third of which has one or more characteristics that are different than the first two battery cells). It should also be noted that energy storage devices may be heterogeneous despite sharing one or more characteristics (e.g., two battery cells may have the same capacities but have different battery technologies and different shapes). Various combinations of energy storage devices 202 may be utilized to provide a range of capacities, performance capabilities, efficiencies, and power usage characteristics. In at least some implementations, the energy storage devices 202 include a combination including at least one high energy density device and one high power energy device. This type of combination enables high power delivery in some situations for critical and latency sensitive tasks, and fast charging in other situations to keep the computing device operational and increase overall battery life.

Generally, high power density devices are more efficient at providing larger amounts of energy over shorter amounts of time (e.g., during latency sensitive tasks such as video processing). The high power density devices may charge fast and provide high power output. On the other hand, high energy density devices are designed to operate efficiently and may have larger capacities. However, the high energy density devices supply less power and may not be suitable for latency sensitive tasks. Additionally, the high energy density devices are more susceptible to increases cycle counts, which can accelerate aging and degradation over time. Situationally selecting an appropriate combination of different batteries to use, charge, and drain in accordance with techniques described herein enables increase performance and more efficient use of the energy storage device system 128. Additionally, cycle counts can be controlled and balanced to avoid having some energy storage devices 202 age much faster than other energy storage devices 202. In the context of latency sensitive tasks, a bulk of the power can be supplied via high power density device, which enables support for greater processing performance without adversely affecting the cycle count and lifetime of the high energy density devices.

The energy storage device controller 204 is representative of a control system to control operation of the energy storage device system 128 and delivery of power from the energy storage devices 202 to service a system load of the computing device 102. The system load refers to the energy required by the computing device 102 at any given point in time in order to operate. The energy storage device controller 204 may be configured using various logic, hardware, circuitry, firmware, and/or software suitable to connect the energy storage devices 202 one to another, supply power to the system, switch between the energy storage devices, and so forth. By way of example and not limitation, the energy storage device controller 204 in FIG. 2 is depicted as including switching hardware 206 and control logic 208 that is operable to selectively switch between different designated energy storage devices 202 at different times. Control logic 208 may reflect different switching modes that switch between drawing power from different ones of the energy storage devices 202 so that power is drawn from energy storage devices 202 in accordance with a particular power ratio as determined by the power manager 126. Thus, rather than merely interconnecting energy storage devices in parallel or series, switching hardware 206 can be utilized to set-up a switching scheme to select different energy storage devices based on different factors and workload patterns for the computing device 102. Similarly, control logic 208 may reflect different switching modes that switch between providing power to different energy storage devices 202 to charge energy storage devices 202 in accordance with a particular power ratio as determined by the power manager 126. Thus, charging and discharging modes depend at least in part upon latency considerations as discussed herein.

In one approach, selection of an energy storage device 202 occurs under the influence of the power manager 126. As noted previously, the power manager 126 represents functionality operable to manage the energy storage devices 202 and makes policy decisions regarding how to charge and discharge the device according to various criteria. The selection of an energy storage device 202 refers to selection of a particular one or more of the energy storage devices 202 and an amount of power that is to be drawn from each of the selected one or more energy storage devices. This selection of the amount of power that is to be drawn can be identified by a power ratio of one energy storage device to another. A power ratio of x:y can be used, where x refers to power drawn from a first energy storage device and y refers to power drawn from a second energy storage device. For example, a power ratio of 4:1 indicates that four times the amount of power is to be drawn from the first energy storage device than from the second energy storage device. Similar power ratios can be used in situations in which there are three or more energy storage devices, such as a power ratio x1:x2: . . . :xm, where x1 refers to power drawn from a first energy storage device, x2 refers to power drawn from a second energy storage device, and xm refers to power drawn from an mth energy storage device. For example, a power ratio of 4:2:1:1 indicates that: the amount of power to be drawn from the first energy storage device is twice the amount of power to be drawn from the second energy storage device and four times the amount of power to be drawn from each of the third and fourth energy storage devices, the amount of power to be drawn from the second energy storage device is twice the amount of power to be drawn from each of the third and fourth energy storage devices, and the amount of power to be drawn from the third energy storage device is the same as the amount of power to be drawn from the fourth energy storage device.

As noted, the selection of an energy storage device 202 and setting of power ratio is based at least in part upon latency considerations. Functionality to assess latency behavior for tasks, applications, and workloads is represented by the latency estimator 127, which the power manager 126 may rely upon to inform power management decisions. The latency behavior assessment involves identifying latency sensitive tasks, applications, and workloads that benefit from higher power and processing frequencies (e.g., a high power mode). The assessment may also be based upon the priority assigned to tasks and the current state of the energy storage device system. When latency sensitivity is determined to exceed an established threshold associated with a “high” level of sensitivity, the power manager 126 is configured to favor use of high power density devices over high energy density device to increase performance (e.g., reduce latency). For non-sensitive tasks, the power manager 126 is configured to favor use of high energy density devices over high power density devices to conserve charge and availability of the high power density devices.

In one approach, a table, list, file or other suitable data structure that correlates different tasks, applications, and scenarios to latency sensitivity is compiled and maintained via the latency estimator 127. This latency data is used to assess the latency for a particular workload over a period time (e.g., an epoch) based on the set of tasks, applications, scenarios, etc. corresponding to the workload. Based on the applications that are launched and tasks that are scheduled, latency data can be used to look-up sensitivity for individual applications/tasks listed in the latency data and make an overall determination regarding the degree to which the current workload is latency sensitive. For unknown applications and tasks (e.g., items not available in the compiled list) the latency estimator 127 may operate to predict the latency sensitivity for such items. Information regarding sensitivity that is predicted may be used to update the listed tasks/applications. The predictions may be based on similarity to known items. For example, different applications of the same class (e.g., video players, image editors, desktop productivity apps, email clients, etc.) may be assigned similar values with respect to latency based on similarity. Additionally, the latency estimator 127 may also consider the processing context to predict whether items may benefit from higher processing performance or not. For example, if an application is network bandwidth or I/O bottlenecked then increasing power is unlikely to have a substantial effect. On the other hand, if the computing device is operating with low power and the processing system is at or near the applicable power cap, there may be room to increase performance by favoring high power energy density devices. In addition or alternatively, information regarding latency sensitivity may be available through a service via a service provider 132. In this approach, the data structure that correlates different tasks, applications, and scenarios to latency sensitivity may be obtained and updated through interaction with the service. Various other techniques to assess latency sensitivity are also contemplated.

The power manager 126 operates to make power management decisions based as least in part upon the latency assessments as just described. Although this document focuses on latency-based decisions and selections, power management decisions may also depend upon other factors including but not limited to predicted energy consumption, expected usage of the computing device, availability of charging opportunities, user behavior and schedules, geographic location, and characteristics of the energy storage device systems and individual devices, to name a few examples. Such additional factors may be employed in combination with latency considerations and also in connection with non-latency sensitive workloads to control both charging and discharging of the system of heterogeneous energy storage devices.

The power manager 126 uses predicted latency as determined by the latency estimator 127, alone or in combination with other factors, to select an appropriate combination of energy storage devices to service the current workload and direct changes to switching hardware 206 to use the selected combination. For example, the power manager 126 may communicate control signals or other suitable data that is interpreted and applied by the control logic 208 to operate switching hardware 206 to draw power as specified by the power manager 126 for a given time frame or epoch. In one or more implementations, selection of the combination of energy storage devices involves setting a power ratio for drawing power from the energy storage device 202 to control the division of the power load among the energy storage devices. This power ratio is used by the control logic 208 to determine which energy storage device(s) to draw power from at any given time. The power ratio may reflect decimal or fractional values for the division of the power. The power ratio may also be expressed as amounts of power draw (e.g., number of watts) for each individual device. In another approach, a number of modes corresponding to different ratios may be established and the mode may be selected based upon the latency assessment.

Accordingly, the power manager 126 may include or otherwise make use of a power ratio estimator module 210 and power ratio data 212. The power ratio estimator module 210 represents functionality operable to use the information gathered and generated by power manager 126 to determine the ratios in which power is to be drawn from the various energy storage devices in the energy storage device system 128. At any given time, the power ratio estimator module 210 determines ratios to utilize for a period of time (e.g., epoch) based at least upon predicted latency sensitivity during the period of time. Such determinations can be made by the power ratio estimator module 210 at various regular or irregular intervals. For example, the power ratio estimator module 210 can make this determination every minute or second, after the amount of time in a current epoch elapses (e.g., at the beginning of each epoch), and so forth.

The power ratio data 212 represents data used by the power ratio estimator module 210. The power ratio data 212 can be implemented as any of a variety of different data structures (e.g., a table, list, or other record), or as any of a variety of different formulas, rules, algorithms, and so forth. The power ratio specifies a division of an overall power load between different energy storage devices. This may be expressed in terms of percentage loads, amounts of power draw, time factors, or otherwise. In one or more embodiments, the power ratio data 218 is a table of threshold values for latency and corresponding power ratios. The power ratio estimator module 210 accesses the power ratio data 212, compares the combined estimated latency to the threshold values in the power ratio data 212, and sets the power ratio for the computing device as the power ratio corresponding to the threshold values.

Table I illustrates an example table that can be used as power ratio data 218. It should be noted that the table illustrated in Table I is an example, and that other data structures, formulas, algorithms, and so forth can be used.

TABLE I
Latency Sensitivity Value        Power Ratio
Below threshold 1                Ratio 1
Between threshold 1 and threshold 2 Ratio 2
Above threshold 2                Ratio 3

Thus, as shown in Table I, three different power ratios are available, depending on the combined latency sensitivity. Although only three power ratios and two threshold values (threshold 1 and threshold 2) are shown, any number of power ratios and threshold values can be used. The power manager 126 is thus able to manage heterogeneous energy storage devices to select different combinations of devices and set power draw ratios and/or divisions of power based upon the latency behavior and perceived latency sensitivity of different tasks, applications, workloads, and interaction scenarios.

Example Battery Cell Arrangement

Generally speaking, an energy storage device system 128 having multiple diverse energy storage devices may be configured in various ways and employ a variety of different types of energy storage devices. In one or more implementations, different energy storage devices 202 included with a system have different characteristics, such as differences in one or more of battery chemistry, capacity, voltage, size, shapes and/or state of charge (SOC), to name a few examples. Using different types of energy storage devices provides flexibility for design of the energy storage device system and circuit boards, and consequently enables device developers to make better utilization of internal space to provide devices having increased battery life and efficiency. The different energy storage devices are arranged in a circuit that enables selective switching among the energy storage devices.

In particular, FIG. 3 depicts generally at 300 one illustrative example arrangement of an energy storage device system 128 having multiple energy storage devices 202 that are battery cells. The energy storage devices 202 may be connected in a circuit that includes an energy storage device controller 204 that implements switching hardware 206 and control logic 208 to switch back and forth among the energy storage devices 202.

Each of the energy storage devices 202 may be represented according to a battery model 302 an example of which is depicted in FIG. 3. Each of the battery cells may also be coupled to a capacitor buffer 304, which is provided to smooth out the supplied power when the switching hardware 206 is employed to switch between cells. Although one illustrative example of a battery model 302 is shown in FIG. 3, it is to be appreciated that the concepts described herein are not limited to a particular model and various different models may be utilized, individually or in combination. Generally, multiple energy storage devices 202 are arranged together with switching hardware 206 that enables switching between the energy storage devices. The switching circuit may also include a mechanism to smooth the current draw from different energy storage devices, such as the example capacitor buffer 304 or other smoothing components. Additionally, the switching circuit includes control logic 208 or comparable functionality to designate and control which of the energy storage devices are used to service the load, the mode of operation of the energy storage devices, and the amount of power that is drawn from each energy storage device. The control logic 208 controls the amount of power that is drawn from each energy storage device in accordance with the power ratio determined by the schedule-based energy storage device selection system 126.

The battery controller 204 and switching hardware 206 may be configured to support multiple different modes of operation for energy storage devices 202. In one mode, the switching hardware 206 is controlled to select one energy storage device at a time from which current is drawn to support the load. The particular energy storage device that is selected at any given time is dependent upon the determined power ratio.

In another mode, the switching hardware 206 is controlled to cycle rapidly between two or more different energy storage devices to draw a percentage of the overall load current from each energy storage device. In other words, the switching hardware 206 is cycled at a relatively high frequency to pull current from different energy storage devices according to the determined power ratio. Effectively, the rapid cycling in this mode enables servicing of the load by drawing different portions of load current from different cells at the same time. For example, for an energy storage device system having three cells and a determined power ratio of 7:2:1, seventy percent of the load may be drawn from a first energy storage device, twenty percent from a second energy storage device, and ten percent from a third energy storage device.

In yet another mode, the switching hardware 206 is controlled to cycle rapidly between or connect to two or more different energy storage devices to draw a specified amount of current at substantially the same time (e.g., simultaneously) from two or more energy storage devices being used to support the load. In this mode, the amount of current supplied by each energy storage device is designated as opposed to setting percentages or weight factors. Again, rapid cycling in this mode enables servicing of the load by drawing different portions of load current from different energy storage devices at the same time, but in this case within constraints for the amount of current that is supplied from each cell.

FIG. 3 further depicts an equivalent circuit model 306 for the energy storage device system 128. In particular, the equivalent circuit model 306 represents switching hardware 206 that can be used to provide current I to a load 308 using an arrangement of multiple battery energy storage devices 202. In the depicted example, four different battery cells 310(1)-310(4) are connectable to the load 308 via a switch 312. The switch 312 may be implemented as a solid state switch or other suitable hardware switching device. The example battery cells 310(1)-310(4) represent different heterogeneous batteries configured to provide respective amounts of current I₁, I₂, I₃, and I₄. The load current I may be supplied using one or a combination of the battery cells 310(1)-310(4).

To do so, the switch 312 may be controlled via the control logic 208 to service the load in accordance with a determined power ratio as described previously. The switch 312 is also used to implement the various different switching modes described above and below. For instance the switch 312 may be positioned to select one of the battery cells 310(1)-310(4) and service the load via the selected cell. The switch 312 may also be cycled rapidly to different positions associated with different cells to effectively draw a portion of the overall current I at the same time from each battery. In this approach, the overall current I is supplied by summing the currents I₁, I₂, I₃, and I₄ supplied from each cell. (e.g., I=I₁+I₂, +I₃−I₄). Portions of current obtained from each cell may be specified in various ways such as by associating percentages, weight factors, thresholds, or designated amounts with the cells.

FIG. 4 depicts generally at 400 example details of a system having heterogeneous energy storage devices in accordance with one or more implementations. In particular, the example of FIG. 4 depicts a system having energy storage devices 202 that may be integrated with a computing device 102. Power is supplied via the energy storage devices using the techniques discussed herein, such as via an energy storage device controller 204, which includes switching hardware 206 and control logic 208. In the depicted example, the energy storage device controller 204 is implemented via a power management integrated circuit (PMIC) 402 that is adapted to support heterogeneous energy storage device switching and latency-based energy storage device selection. For instance, in one or more implementations, the PMIC or other energy storage device controller is adapted to include registers 404 to facilitate policy enforcement of a switching policy. The registers 404 may be configured to hold various parameters that the control logic 208 makes use of to control operation of switching hardware 206 and supply power from the energy storage devices accordingly. For example, registers 404 may include registers indicative of the determined power ratio, the switching policy, a selected switching mode, a timing register, and battery cell specific registers indicative of battery states, characteristics, and designated current switching constraints (amounts, weights, percentages, thresholds, etc.). Registers may be assigned default values selected for general usage in typical scenarios. Registers may then be selectively adapted under the influence of the operating system and/or user input to implement policy settings for different use cases.

The registers 404 implemented by the energy storage device controller are exposed to enable operating system 108 and/or application 110 level control over switching. In other words, the registers 404 provide user accessible control over heterogeneous energy storage device switching. By way of example and not limitation parameter values for the registers 404 may be set and updated dynamically via an application programming interface (API) 406 that is exposed via the operating system 108 as represented in FIG. 4. API messages and or other control signals may be exchanged between the energy storage device controller 204 and operating system over a suitable communication bus 408, one example of which is an I²C bus. Information regarding energy storage device states, workload, and characteristics of energy storage devices 202 may also be communicated to the operating system 108 and/or schedule-power manager 126 via the control signals and/or API to facilitate assessments of the operational context and policy decisions based on the operational context.

Thus, as represented in FIG. 4, the operating system 108, by way of a power manager 126 or otherwise, may make policy decisions such as mode selection and energy storage device constraints setting for energy storage device switching. Policy decisions are made based upon performance parameters indicative of an operational context including at least information regarding battery states and characteristics obtained from the battery controller 204. As represented, policy decisions may be made under the influence of a latency estimator 127 that determines and supplies information regarding latency sensitivity of tasks, applications, workloads, and interaction scenarios. The API 406 provides a mechanism by which control signals are communicated to the energy storage device controller 204 to set the registers 404 in accordance with the policy decisions. Thus, the operating system 108 and/or power manager 126 may direct operation of energy storage device controller 204 to implement policy enforcement of a selected policy by setting the registers 404 and causing operation of switching hardware 206 to effectuate the operational modes and energy storage device constraints specified by the policy. Power is then supplied to the system via one or more of the energy storage devices in accordance with the policy decisions.

Example Procedures

Further aspects of latency-based energy storage device selection techniques are discussed in relation to example procedure of FIGS. 5 and 6. The procedures described in this document may be implemented utilizing the environment, system, devices, and components described herein and in connection with any suitable hardware, software, firmware, or combination thereof. The procedures may be represented as a set of blocks that specify operations performed by one or more entities and are not necessarily limited to the orders shown for performing the operations by the respective blocks.

FIG. 5 is a flow diagram that describes details of an example procedure 500 for latency-based energy storage device selection in accordance with one or more implementations. The procedure 500 describes details of drawing power from multiple heterogeneous energy storage devices based upon latency considerations. The procedure 500 can be implemented by way of a suitably configured computing device, such as by way of an operating system 108, power manager 126, latency estimator 127, and/or other functionality described in relation to the examples of FIGS. 1-4.

Latency behavior of computing tasks performed via a computing device having multiple heterogeneous energy storage devices over a period of time is predicted (block 502). The latency behavior of tasks associated with the workload can be predicted in various ways as discussed above. The latency behavior can be determined, for example, based on an assessment of applications, tasks, and interaction scenarios that are currently being performed and/or are expected to be performed during a time period. This may involve analyzing applications that are launched and corresponding tasks associated with the applications. In one or more implementations, a data structure that correlates different items (e.g., applications, tasks, workloads, scenarios, etc.) with latency sensitivity values may be refereed to look-up applicable values. Additionally, predictions can be made based upon a similarity assessment of applications/tasks that are not enumerated in the data structure to items that are enumerated and mapped to latency sensitivity values via the data structure. In this approach, similar items may be assigned the same or similar latency sensitivity values.

A combination of energy storage devices to use for performance of the computing tasks is selected in dependence upon the predicted latency (block 504). For example, batteries or energy devices that are better suited to the particular level of latency sensitivity determined for the tasks may be selected or favored based on the analysis. As noted, higher power density devices may be favored in latency sensitive scenarios and higher energy density devices may be favored in situation that are not deemed latency sensitive. Power draws between available energy storage devices are adjusted according to the latency sensitive levels determined for the time period.

In particular, adjustments are caused to switching hardware to supply power for performance of the computing tasks from the selected combination of energy storage devices during the period of time (block 506). For example, a power manager 126 may operate to direct operation of an energy storage device controller 204 to implement policy decisions as previously discussed. In at least some implementations, this involves communications between the power manager 126 and energy storage device controller 204 effective to control switching hardware to draw levels of power for different energy storage devices as specified by the power manager. For example, different energy storage devices may be activated and deactivated based on determined policy settings. The policy settings are based at least partially upon latency considerations as described herein. In addition or alternatively, policy settings may specify power ratios that are mapped to the predicted latency behavior as described previously. In yet another example, the policy settings may be configured to cause implementation of different pre-established operating modes such as a high power mode, balanced mode, or low power mode. In this approach, power draws for different energy storage devices are specified by the selected mode. Accordingly, adjustments to power draws based on latency considerations may be made in various example ways enumerated as well as using other suitable techniques to change power draws for a set of heterogeneous energy storage devices in dependence upon assessments of latency behavior for computing tasks.

FIG. 6 is a flow diagram that describes details of another example procedure 600 for latency-based energy storage device selection in accordance with one or more implementations. The procedure 600 describes details of adjusting power draw between multiple heterogeneous energy storage device including high power density devices and high energy density device. The procedure 600 can be implemented by way of a suitably configured computing device, such as by way of an operating system 108, power manager 126, and/or other functionality described in relation to the examples of FIGS. 1-4.

A determination is made that latency sensitivity of a workload for a computing device exceeds a threshold. The determination is made in relation to a computing device including an energy storage device system with at least one high power density device and at least one high energy density device (block 602). For instance, latency sensitivity of a workload can be determined in various ways as discussed herein including using preset values or predicting latency sensitivity on demand. In one example, the determination is performed by comparing items associated with the workload to items contained in a data structure that correlates different tasks, applications, and scenarios to levels of latency sensitivity to assess latency sensitivity of the workload. Additionally, different threshold levels of latency sensitivity can be established and related to power management settings, such as power ratios or modes of operation as noted in this description. By way of example and not limitation, threshold levels for latency sensitivity may be correlated to different power ratios as represented and discussed in relation to Table 1 above. Accordingly, different determined levels of latency sensitivity may trigger different corresponding responses to adjust power draws between heterogeneous energy storage devices of an energy storage device system.

In particular, responsive to determining that latency sensitivity exceeds the threshold, a power ratio for the energy storage device system is adjusted to increase a percentage of power to service the workload supplied from the high power density device (block 604). Here, the level of latency sensitivity that is determined indicates that the workload may benefit from increased power supply and/or processing performance. Accordingly, the power ratio is adjusted accordingly to favor the high power density device. In other words, the balance of total power supplied by the energy storage device system may be adjusted to increase power from one or more high power density devices under appropriate circumstance. In some scenarios, a majority or bulk of the overall power is supplied via high power density devices when a corresponding threshold is exceeded. Moreover, in some instances just high power density devices may be employed, in which case other low power density devices (e.g., high energy density devices) may be suspended or shut-off.

Increased power supply favoring the one or more high power density devices may continue for a specified period of time as long as power from the devices remains available (e.g., the devices/battery cells have available charge) and the latency sensitive workload is ongoing. A return to a more balanced or different division of power draw may occur in response to conclusion of the latency sensitive workload and a corresponding change in the level of latency sensitivity.

In particular, conclusion of latency sensitive tasks associated with the workload is recognized (block 606). Here, the system recognizes that the particular tasks and/or interaction with applications that causes the elevated level of latency sensitivity are completed. Because of this, a corresponding drop in the level of latency sensitivity occurs and the system is able to detect this drop.

Responsive to recognizing conclusion of the latency sensitive tasks, the power ratio is readjusted to divide power supply from the energy storage device system according to factors designated for non-latency sensitive workloads. (block 608) In this case, power ratios are generally adjusted to rely more heavily on high energy density devices and preserve charge of the high power density devices for subsequent, higher demand tasks. For example, assuming that the drop in latency sensitivity falls below a lowest applicable threshold, power ratios may be adjusted to increase reliance upon high energy density devices and/or to minimize usage of high power density devices. Naturally, intermediate levels of latency sensitivity may prompt corresponding adjustments to power ratios to balance the division of power between high power density devices and high energy density devices accordingly. A range of such intermediate balances and power ratios between fully using high power devices/modes and fully using lower power devices/modes are contemplated. Generally, when latency sensitivity is determined to be at levels designated as high, action is taken to favor high power density devices to reduce latency. On the other hand, when latency sensitivity is determined to be below levels designated as high, action is taken to favor high energy density devices to conserve power for future computing tasks and workloads that may be latency sensitive.

Having considered the foregoing example details and procedures, consider now a discussion of an example system and components that may be employed for aspects of latency-based energy storage device selection in one or more implementations.

Example System

FIG. 7 illustrates an example system 700 that includes an example computing device 702 that is representative of one or more computing systems and/or devices that may implement the various techniques described herein. The computing device 702 may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and/or any other suitable computing device or computing system.

The example computing device 702 as illustrated includes a processing system 704, one or more computer-readable media 706, and one or more I/O interfaces 708 that are communicatively coupled, one to another. Although not shown, the computing device 702 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.

The processing system 704 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 704 is illustrated as including hardware elements 710 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 710 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.

The computer-readable media 706 is illustrated as including memory/storage 712. The memory/storage 712 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage 712 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage 712 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 706 may be configured in a variety of other ways as further described below.

Input/output interface(s) 708 are representative of functionality to allow a user to enter commands and information to computing device 702, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone for voice operations, a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device 702 may be configured in a variety of ways as further described below to support user interaction.

Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms “module,” “functionality,” and “component” as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 702. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “communication media.”

“Computer-readable storage media” refers to media and/or devices that enable storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Computer-readable storage media does not include signal bearing media, transitory signals, or signals per se. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.

“Communication media” may refer to signal-bearing media that is configured to transmit instructions to the hardware of the computing device 702, such as via a network. Communication media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Communication media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 710 and computer-readable media 706 are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable storage media described previously.

Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules including the operating system 108, applications 110, power manager 126, and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 710. The computing device 702 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device 702 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 710 of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 702 and/or processing systems 704) to implement techniques, modules, and examples described herein.

As further illustrated in FIG. 7, the example system 700 enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.

In the example system 700, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.

In one embodiment, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one embodiment, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.

In various implementations, the computing device 702 may assume a variety of different configurations, such as for computer 714, mobile 716, and television 718 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 702 may be configured according to one or more of the different device classes. For instance, the computing device 702 may be implemented as the computer 714 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.

The computing device 702 may also be implemented as the mobile 716 class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 702 may also be implemented as the television 718 class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.

The techniques described herein may be supported by these various configurations of the computing device 702 and are not limited to the specific examples of the techniques described herein. This is illustrated through inclusion of the power manager 126 and the energy storage device system 128 on the computing device 702. The functionality represented by power manager 126 and other modules/applications may also be implemented all or in part through use of a distributed system, such as over a “cloud” 720 via a platform 722 as described below.

The cloud 720 includes and/or is representative of a platform 722 for resources 724. The platform 722 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 720. The resources 724 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 702. Resources 724 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.

The platform 722 may abstract resources and functions to connect the computing device 702 with other computing devices. The platform 722 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 724 that are implemented via the platform 722. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 700. For example, the functionality may be implemented in part on the computing device 702 as well as via the platform 722 that abstracts the functionality of the cloud 720.

EXAMPLE IMPLEMENTATIONS

Example implementations of techniques described herein include, but are not limited to, one or any combinations of one or more of the following examples:

Example 1

A method implemented by a computing device having multiple heterogeneous energy storage devices, the method comprising: predicting latency behavior of computing tasks performed via the computing device for a period of time; selecting a combination of energy storage devices to use for performance of the computing tasks in dependence upon the predicted latency behavior; and causing adjustments to switching hardware to supply power for performance of the computing tasks from the selected combination of energy storage devices during the period of time.

Example 2

The method as described in any one or more of the examples in this section, wherein predicting the latency behavior includes assessing latency sensitivity of individual computing tasks associated with a workload for the period of time and establishing overall latency sensitivity for the period of time based on the latency sensitivity for the individual computing tasks.

Example 3

The method as described in any one or more of the examples in this section, wherein predicting the latency behavior includes determining latency sensitivity associated with applications executing on the computing device for the period of time.

Example 4

The method as described in any one or more of the examples in this section, wherein predicting the latency behavior comprises referencing a data structure configured to correlate different computing tasks and applications to corresponding levels of latency sensitivity.

Example 5

The method as described in any one or more of the examples in this section, wherein selecting the combination of energy storage devices comprises: comparing predicted latency behavior to one or more defined threshold levels of latency sensitivity; determining a threshold level that corresponds to the predicted latency behavior; and setting a division of an overall power load between the multiple heterogeneous energy storage devices as designated for the threshold level that corresponds to the predicted latency behavior

Example 6

The method as described in any one or more of the examples in this section, wherein causing adjustments to switching hardware comprises setting a power ratio for an energy storage system including the multiple heterogeneous energy storage devices to control power draw from the multiple heterogeneous energy storage devices as designated for the predicted latency behavior.

Example 7

The method as described in any one or more of the examples in this section, wherein the multiple heterogeneous energy storage devices are configured as multiple heterogeneous battery cells.

Example 8

The method as described in any one or more of the examples in this section, wherein: the multiple heterogeneous energy storage devices include at least one high power density device and at least one high energy density device; and selecting the combination comprises balancing a division of power draw between the high power density device and the high energy density device based on the predicted latency behavior.

Example 9

The method as described in any one or more of the examples in this section, wherein causing adjustments to switching hardware comprises communicating control signals to a controller for an energy storage system including the multiple heterogeneous energy storage devices and the switching hardware to direct operation of switching hardware to draw power from the selected combination of energy storage devices.

Example 10

The method as described in any one or more of the examples in this section, wherein the control signals are configured to designate a switching mode for the multiple heterogeneous energy storage devices based on the predicted latency behavior.

Example 11

A computing device comprising: an energy storage device system including multiple heterogeneous energy storage devices; and a power manager configured to direct operations of the energy storage device system to control power draw from the multiple heterogeneous energy storage devices based at least in part upon an assessment of latency sensitivity of a workload performed via the computing device for a period of time, including: causing a division of power draw between the multiple heterogeneous energy storage devices to favor high power density devices included with the multiple heterogeneous energy storage devices to reduce latency when latency sensitivity is at levels designated as high; and causing the division of power draw between the multiple heterogeneous energy storage devices to favor high energy density devices included with the multiple heterogeneous energy storage devices to conserve power for future workloads when latency sensitivity is below the levels designated as high.

Example 12

The computing device as described in any one or more of the examples in this section, wherein causing the division of power comprises: determining a power ratio based upon the assessment of latency sensitivity; and communicating the determined power ratio for use by the energy storage device system, thereby directing operation of switching hardware of the energy storage device system to apply the power ratio to implement the corresponding division of power draw.

Example 13

The computing device as described in any one or more of the examples in this section, wherein the power manager includes a latency estimator configured to perform the assessment of latency sensitivity for the workload including analyzing one or more of energy storage device characteristics, latency sensitivity of different tasks, application-specific latency considerations, estimated device usage, or estimated energy usage to predict latency sensitivity for the workload.

Example 14

The computing device as described in any one or more of the examples in this section, wherein the latency estimator is further configured to select a combination of energy storage devices to use for performance of the workload in dependence upon the predicted latency sensitivity, the division of power draw corresponding to the combination of energy storage devices that is selected.

Example 15

The computing device as described in any one or more of the examples in this section, wherein the power manager includes a power ratio estimator configured to derive a power ratio that specifies the division of power draw based upon the assessment of latency sensitivity.

Example 16

A computing device comprising: an energy storage device system with multiple heterogeneous energy storage devices including at least on high power density device and at least one high energy density device; one or more processors; and one or more computer-readable storage media having stored thereon instructions that, responsive to execution by the one or more processors, cause the one or more processors to perform operations including: determining that latency sensitivity of a workload for the computing device exceeds a threshold associated with high latency sensitivity; and responsive to determining that latency sensitivity exceeds the threshold, adjusting a power ratio for the energy storage device system to increase a percentage of power to service the workload supplied from the high power density device.

Example 17

The computing device as described in any one or more of the examples in this section, wherein the instructions further cause the one or more processors to perform operations including: recognizing conclusion of latency sensitive tasks associated with the work load; and responsive to recognizing conclusion of the latency sensitive tasks, readjusting the power ratio to divide power supply from the energy storage device system according to factors designated for non-latency sensitive workloads.

Example 18

The computing device as described in any one or more of the examples in this section, wherein the factors designated for non-latency sensitive workloads include one or more of predicted energy consumption, expected usage of the computing device, availability of charging opportunities, user behavior and schedules, geographic location, or characteristics of the energy storage device system.

Example 19

The computing device as described in any one or more of the examples in this section, wherein the instructions further cause the one or more processors to perform operations including: determining latency sensitivity of the workload by comparing items associated with the workload to items contained in a data structure that correlates different tasks, applications, and scenarios to levels of latency sensitivity.

Example 20

The computing device as described in any one or more of the examples in this section, the multiple heterogeneous energy storage devices have different characteristics including one or more of different sizes, capacities, technologies, chemistries, shapes, state of charge (SOC), age, temperatures, or cycle counts.

CONCLUSION

Although the example implementations have been described in language specific to structural features and/or methodological acts, it is to be understood that the implementations defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed features.

Claims

1. A method implemented by a computing device having multiple heterogeneous energy storage devices, the method comprising:

predicting latency behavior of computing tasks performed via the computing device for a period of time;

selecting a combination of energy storage devices to use for performance of the computing tasks in dependence upon the predicted latency behavior; and

causing adjustments to switching hardware to supply power for performance of the computing tasks from the selected combination of energy storage devices during the period of time.