DEVICE, METHOD AND PROGRAM PRODUCT FOR PLANNING BATTERY CONSUMPTION

Abstract

A method comprising the following steps: - Determining (602), using a processor, a respective expected battery consumption rate for each application of a plurality of applications; - Determining (604), for each application of the plurality of applications, a respective estimated duration for which the battery will power a device if the respective application is executed, wherein the respective estimated duration for which the battery will power the device is based on the respective expected battery consumption rate of the respective application and the current remaining battery energy; - Displaying (606), for each application of the plurality of applications, the respective estimated duration together with a visual representation of the respective application; - Obtaining a user selection as to how long a selected application of the plurality of applications should be used;and update, based on the user selection, the displayed respective estimated durations of the other applications from the multitude of applications.;

Description

AREA

[0001] The subject matter disclosed here concerns batteries, and more precisely, the planning of battery consumption. BACKGROUND GENERAL STATE OF THE TECHNOLOGY

[0002] Information handling devices, such as desktop computers, laptop computers, tablet computers, smartphones, optical head-mounted display units, smartwatches, etc., are ubiquitous in society. These information handling devices can use batteries. The time that the battery powers an information handling device can depend on how the device is used. SUMMARY

[0003] A device for planning battery consumption is disclosed. A method and a computer program product also perform the functions of the device. In one embodiment, the device comprises a display device, a processor, and memory that stores code executable by the processor. In various embodiments, the code is executable by the processor to determine an expected battery consumption rate of an application. In another embodiment, the code is executable by the processor to determine an estimated duration for which the battery will power the device if the application is running. The estimated duration for which the battery will power the device can be based on the expected battery consumption rate of the application and the current remaining battery power.In some embodiments, the code is executable by the processor to display the estimated time duration on a display device along with a visual representation of the application.

[0004] In another embodiment, the code executable by the processor to determine the expected battery consumption rate of the application also includes code executable by the processor to analyze the application's past battery consumption data. In some embodiments, the code executable by the processor to analyze the application's past battery consumption data also includes code executable by the processor to access memory. The memory may contain the past battery consumption data.

[0005] In another embodiment, the memory further includes code executable by the processor to determine the expected battery consumption rate for each of several applications. In such an embodiment, the memory further includes code executable by the processor to determine the estimated duration for which the battery will power the device for each of the several applications, if that application is running. In some embodiments, the memory further includes code executable by the processor to display each estimated duration along with a visual representation of each of the several applications.In certain embodiments, the code executable by the processor to determine the estimated duration for which the battery will power the device if the application is running further comprises code executable by the processor to add the expected battery consumption rate of the application to a current battery consumption rate to yield a combined battery consumption rate, and to divide the current remaining battery energy by the combined battery consumption rate.

[0006] In one embodiment, the code executable by the processor to determine the estimated duration for which the battery will power the device if the application is executed further comprises code executable by the processor to determine a combined estimated duration for which the battery will power the device for multiple applications selected to run together, and to display the combined estimated duration along with a respective visual representation of each of the multiple applications selected to run together.

[0007] In one embodiment, a method for planning battery consumption includes determining, using a processor, an expected battery consumption rate of an application. In some embodiments, the method includes determining an estimated duration for which the battery will power a device if the application is running. The estimated duration for which the battery will power the device can be based on the expected battery consumption rate of the application and the current remaining battery power. In another embodiment, the method includes displaying the estimated duration along with a visual representation of the application.

[0008] In some embodiments, determining the expected battery consumption rate of the application involves analyzing the application's past battery consumption data. In these embodiments, analyzing the application's past battery consumption data may involve accessing a memory location on the device that contains the past battery consumption data. In some embodiments, analyzing the application's past battery consumption data may involve accessing a remote storage device that contains the past battery consumption data. In some embodiments, determining the expected battery consumption rate of the application includes determining the expected battery consumption rate of the application when the application is not running.

[0009] In some embodiments, the method includes determining the expected battery consumption rate for each of several applications. In these embodiments, the method may include determining the estimated duration for which the battery will power the device for each of the multiple applications, if that application is executed. In certain embodiments, the method includes displaying each estimated duration along with a visual representation of each of the multiple applications.

[0010] In certain embodiments, determining the estimated duration for which the battery will power the device if the application is running involves adding the application's expected battery consumption rate to a current battery consumption rate to obtain a combined battery consumption rate, and dividing the current remaining battery energy by the combined battery consumption rate.

[0011] In one embodiment, a program product comprises a computer-readable storage medium that stores code executable by a processor. In certain embodiments, the executable code includes code to determine the expected battery consumption rate of an application. In another embodiment, the code includes code to determine an estimated duration for which the battery will power a device if the application is running. The estimated duration for which the battery will power the device can be based on the expected battery consumption rate of the application and the current remaining battery power. In some embodiments, the executable code includes code to display the estimated duration along with a visual representation of the application.

[0012] In certain embodiments, the code further includes code for executing the determination of a respective expected battery consumption rate for each of several applications. In some embodiments, the code further includes code for executing the determination of a respective estimated duration for which the battery will power the device for each of the several applications, if the respective application is executed. In other embodiments, the code further includes code for executing the display of each estimated duration along with a respective visual representation of each of the several applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] A more detailed description of the embodiments briefly described above is given with reference to specific embodiments illustrated in the accompanying drawings. It is understood that these drawings depict only some embodiments and should therefore not be considered exhaustive. The embodiments are described and explained with additional specificity and detail by means of the accompanying drawings. These show:

[0014] Fig. 1 a schematic block diagram illustrating an embodiment of a system for planning battery consumption;

[0015] Fig. 2 a schematic block diagram illustrating an embodiment of a device comprising an information handling device;

[0016] Fig. 3 a schematic block diagram illustrating an embodiment of a device comprising a battery consumption module of an application;

[0017] Fig. 4 a schematic block diagram illustrating another embodiment of a device comprising a battery consumption module of an application;

[0018] Fig. 5 a schematic block diagram illustrating another embodiment of a device comprising a battery consumption module of an application;

[0019] Fig. 6. A flowchart illustrating one embodiment of a method for planning battery consumption; and

[0020] Fig. 7 a flowchart illustrating one embodiment of another method for planning battery consumption. DETAILED DESCRIPTION

[0021] As a person skilled in the art will understand, the aspects of the embodiments can be configured as a system, device, method, or program product. Accordingly, the embodiments can take the form of one embodiment entirely as hardware, one embodiment entirely as software (including firmware, resident software, microcode, etc.), or one embodiment that combines software and hardware aspects, all of which may herein be generally referred to as a "circuit," "module," or "system." Furthermore, the embodiments can take the form of a program product configured in one or more computer-readable storage devices embodying machine-readable code, computer-readable code, and / or program code, which herein is referred to as "code." The storage devices can be physical, non-transient, and / or non-transmitting. The storage devices can be configured as non-signals.In one particular embodiment, the storage devices use only signals to access code.

[0022] Some of the functional units described in this description have been designated as modules to emphasize their implementation independence. A module can be implemented, for example, as a hardware circuit comprising specific VLSI (very high integration level) circuits or gate arrays, commercially available semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable logic devices, or the like.

[0023] Modules can also be implemented as code and / or software for execution by various types of processors. An identified code module can, for example, comprise one or more physical or logical blocks of executable code, which may be organized as an object, procedure, or function. However, the executable elements of an identified module do not need to be spatially contiguous; they can consist of disparate instructions stored in different locations. When logically combined, these instructions form the module and fulfill its stated purpose.

[0024] Indeed, a code module can correspond to a single instruction or many instructions and can even be distributed across several different code segments, across different programs, and across multiple storage devices. Similarly, operational data can be identified and represented within modules and can be in any suitable form and organized within any suitable type of data structure. The operational data can be aggregated into a single data record or distributed across various locations, including different computer-readable storage devices. When a module or parts of a module are implemented as software, the software components are stored on one or more computer-readable storage devices.

[0025] Any combination of one or more computer-readable media can be used. The computer-readable medium can be a computer-readable storage medium. The computer-readable storage medium can be a storage device that stores the code. The storage device can be, for example, without limitation, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination thereof.

[0026] More specific examples (a non-exhaustive list) of storage devices would include: an electrical connection having one or more wires, a portable computer disk, a hard disk, working memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the context of this publication, a computer-readable storage medium can be any physical medium capable of containing or storing a program for use by a system, device, or apparatus for carrying out instructions or in connection therewith.

[0027] Code for executing operations for implementations can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, or the like, and traditional procedural programming languages ​​such as C or the like, and / or machine languages ​​such as assembly language. The code can run entirely on the user's computer, partially on the user's computer as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (e.g., a server).via the Internet using an Internet service provider).

[0028] Throughout this description, any reference to "an embodiment" or similar expressions means that a particular feature, structure, or distinguishing characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrase "in an embodiment" and similar expressions throughout this description may all refer to the same embodiment, but mean "one or more, but not all, embodiments," unless expressly stated otherwise. The terms "comprising," "having," and their variants mean "comprising but without limitation," unless expressly stated otherwise. A listed set of elements does not imply that one or all of the elements are mutually exclusive, unless expressly stated otherwise.The terms “ein”, “eine” and “der, die, das” also refer to “one or more”, unless explicitly stated otherwise.

[0029] Furthermore, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner. Numerous specific details are provided in the following description, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a comprehensive understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be implemented in practice without one or more of the specific details or with different methods, components, materials, and so on. In other cases, well-known structures, materials, or processes are not shown or described in detail to avoid obscuring the aspects of an embodiment.

[0030] The following describes aspects of the embodiments with reference to schematic flowcharts and / or schematic block diagrams of processes, devices, systems, and program products according to the embodiments. It is understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code.This code can be provided to a processor of a general-purpose computer, a specific computer, or another programmable data processing device to produce a machine such that the instructions executed through the processor of the computer or other programmable data processing device create means to implement the functions / actions specified in the block or blocks of the flowcharts and / or schematic block diagrams.

[0031] The code can also be stored in a storage device that can direct a computer, other programmable data processing device, or other equipment to function in a particular way, such that the instructions stored in the storage device result in a product comprising instructions that implement the function / action specified in the block or blocks of the flowcharts and / or schematic block diagrams.

[0032] The code can also be loaded onto a computer, other programmable data processing device, or other equipment to cause a series of operational steps to be performed on the computer, other programmable device, or other equipment to produce a computer-implemented process, so that the code executed on the computer or other programmable device provides processes to implement the functions / actions specified in the block or blocks of the flowchart and / or block diagram.

[0033] The flowcharts and / or schematic block diagrams in the figures depict the architecture, functionality, and operation of possible implementations of devices, systems, processes, and program products according to various embodiments. In this respect, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, a segment, or a code section that comprises one or more executable instructions of the code for implementing the specified logical function(s).

[0034] It should also be noted that in some alternative implementations, the functions mentioned in the block may occur in a different order than shown in the figures. For example, two blocks shown sequentially may actually be executed essentially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functionality in question. Other steps and processes may be devised whose function, logic, or effect is equivalent to one or more blocks, or parts thereof, of the depicted figures.

[0035] Although various arrow and line types may be used in the flowchart and / or block diagrams, it is understood that these do not limit the scope of the corresponding embodiments. Some arrows or other connecting elements may be used simply to indicate the logical sequence of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of indefinite duration between the enumerated steps of the depicted embodiment. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks within the block diagrams and / or flowcharts, can be implemented using specific hardware-based systems that execute the specified functions or actions, or using combinations of specific hardware and code.

[0036] The description of elements in each figure may refer to elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0037] Fig. 1 represents an embodiment of a system 100 for planning battery consumption. In one embodiment, the system includes 100 Information handling devices 102 , battery consumption modules 104 of applications, data networks 106 and server 108 Although a specific number of information handling devices 102 , battery consumption modules 104 of applications, data networks 106 and servers 108 in Fig. Figure 1 shows that any number of information handling devices 102 , battery consumption modules 104of applications, data networks 106 and servers 108 in the system 100 may contain.

[0038] In one embodiment, the information handling devices include 102 Computer devices, such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smartphones, smart televisions (e.g., televisions connected to the internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the information handling devices include 102 Wearable devices, such as smartwatches, fitness trackers, optical head-mounted displays, or the like. Information handling devices 102 can access the data network directly using a network connection 106 access.

[0039] The information handling devices 102 and / or the servers 108 One embodiment of the battery consumption module 104 an application. In certain embodiments, the battery consumption module can 104 Determine the expected battery consumption rate of an application. The battery consumption module 104 An application can determine an estimated duration during which a battery will power a device (e.g., an information handling device). 102 ) will supply power if the application is running. The estimated duration for which the battery will power the device can be based on the expected battery consumption rate of the application and the current remaining battery power. The battery consumption module 104An application can also display the estimated time duration on a display device along with a visual representation of the application. Thus, the battery consumption module can 104 It can be used in an application to show how long an application can function when run based on the current available battery power.

[0040] The data network 106 In one embodiment, it comprises a digital communication network that transmits digital communications. The data network 106 Can a wireless network, such as a wireless mobile network, a local wireless network, such as a WiFi network, or a Bluetooth network be used? ® -network, a near-field communication (“NFC”) network, an ad-hoc network, and / or the like. The data network 106It can include a WAN, a storage area network (SAN), a LAN, a fiber optic network, the internet, or another digital communications network. The data network 106 The data network can comprise two or more networks. 106 It can include one or more servers, routers, switches, and / or other network equipment. The data network 106 This may also include computer-readable storage media, such as a hard drive, an optical drive, non-volatile memory, RAM, or the like.

[0041] In one embodiment, the servers include 108 Computer equipment, such as desktop computers, laptop computers, mainframes, cloud servers, virtual servers, and / or the like. In some configurations, the servers 108They are referred to as application servers, email servers, database servers, file servers, game servers, home servers, media servers, web servers, and / or the like. In certain configurations, the servers store 108 Data and can be accessed by one or more information handling devices 102 via the network 106 be designed. In certain configurations, the servers can 108 at least part of the battery consumption module 104 an application and can include one or more processes of the battery consumption module. 104 run an application.

[0042] Fig. 2 represents an embodiment of a device 200 from, which can be used to plan battery consumption. The device 200 includes one embodiment of the information handling device 102 Furthermore, the information handling device can 102 the battery consumption module104 an application, a processor 202 , a storage 204 , an input device 206 , a communication hardware 208 and a display device 210 include. In some embodiments, the input device 206 and the display device 210 combined in a single device, such as a touchscreen.

[0043] The processor 202 In one embodiment, it can comprise any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor can be 202 It may be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field-programmable gate array (FPGA), or a similar programmable controller. In some embodiments, the processor performs 202Instructions that are stored in the memory 204 are stored to execute the procedures and routines described here. The processor 202 is with the memory 204 , the battery consumption module 104 an application, the input device 206 , the communication hardware 208 and the display device 210 linked in terms of communication.

[0044] The storage 204 In one embodiment, it is a computer-readable storage medium. In some embodiments, the storage includes 204 volatile computer storage media. For example, the storage 204 The RAM may include dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), and / or static RAM (SRAM). In some embodiments, the memory includes 204 Non-volatile computer storage media. For example, the storage 204a hard disk, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the storage includes 204 both volatile and non-volatile computer storage media.

[0045] In some designs, the memory stores 204 Data on the battery consumption history of applications. In some designs, the memory stores 204 also program code and related data, such as an operating system or other controller algorithms, that run on the information handling device 102 function.

[0046] The information handling device 102 Can the battery consumption module 104 Use an application to determine the battery consumption of applications. It is understood that the battery consumption module 104An application can include computer hardware, computer software, or a combination of both. For example, the battery consumption module 104 An application may include circuits or a processor used to determine an application's expected battery consumption rate. In certain embodiments, the application's expected battery consumption rate can be determined when the application is not running. Another example is the battery consumption module. 104 an application computer program code that determines an estimated duration during which a battery will power the information handling device 102 will supply energy if the application is executed.

[0047] The input device 206In one embodiment, the input device may comprise any known computer input device, including a touchpad, button, keyboard, stylus, or the like. In some embodiments, the input device may be... 206 into the display device 210 It may be integrated, for example as a touchscreen or a similar touch-sensitive display. In some embodiments, the input device includes 206 a touchscreen so that text can be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, the input device includes 206 Two or more different devices, such as a keyboard and a touch panel. The communication hardware 208 It can enable communication with other devices. For example, the communication hardware can 208communication via Bluetooth ® , activate WiFi and so on.

[0048] The display device 210 In one embodiment, the display device may comprise any known electronically controllable display or display device. 210 It can be designed to output visual, audible, and / or tactile signals. In some embodiments, the display device includes 210 An electronic device capable of outputting visual data to a user. For example, a display device 210 Without restriction, this includes an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, or the like to a user. Another non-restrictive example of a display device is... 210This includes a wearable device, such as a smartwatch, smart glasses, a heads-up display, or the like. Furthermore, the display device can... 210 a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a PC, a vehicle dashboard or the like.

[0049] In certain embodiments, the display device includes 210 one or more speakers to produce sound. For example, the display device 210 generate an audible alarm or notification (e.g., a beep or ring) when determining an expected battery consumption rate of an application. In some embodiments, the display device includes 210 One or more haptic devices for generating vibrations, movement, or other haptic feedback. For example, the display device 210generate haptic feedback when initializing the data restriction.

[0050] In some designs, the display device 210 wholly or partially into the input device 206 be integrated. For example, the input device 206 and the display device 210 a touchscreen or similar touch-sensitive display. In other embodiments, the display device may be 210 near the input device 206 are located. In certain designs, the display device 210 Instructions and / or data for output from the processor 202 and / or the battery consumption module 104 received from an application.

[0051] Fig. Figure 3 shows a schematic block diagram illustrating an embodiment of a device 300 depicts a battery consumption module 104an application. Furthermore, the battery consumption module includes 104 an application a battery consumption monitoring module 302 , a time determination module 304 an application and a display module 306 .

[0052] The battery consumption determination module 302 It can be used to determine the expected battery consumption rate of an application that is not running. In some embodiments, the battery consumption determination module can 302 It can be used to determine the expected battery consumption rate of a running application. In certain embodiments, the battery consumption determination module can 302 This can be used to determine the expected battery consumption rate of more than one application. The more than one application can have a status of running, not running, or a combination thereof.

[0053] In one embodiment, the battery consumption determination module 302 Determine the expected battery consumption rate of an application by analyzing the application's historical battery consumption data. This historical data can include information such as the application's name, the duration of its use, the amount of battery power consumed, the amount of processor resources used, the amount of network data sent and / or received, and so on. Such historical battery consumption data can correspond to a single execution of the application, a combination of executions during the lifetime of a battery, lifetime use of the application on a device, aggregated data corresponding to application use on multiple devices, and so forth.

[0054] Previous battery usage data can be stored in the memory. 204 an information handling device 102 be stored, which the battery consumption module 104 an application, and / or the previous battery consumption data may be stored on a remote storage device (e.g., remote storage), such as an information handling device. 102 , which is the battery consumption module 104 not included in an application.

[0055] In certain embodiments, the expected battery consumption rate can be expressed as a percentage of the device's battery energy used per second, minute, hour, etc. In some embodiments, the expected battery consumption rate can be expressed as the amount of battery energy consumed per second, minute, hour, etc.

[0056] In some embodiments, the time determination module304 An application can use this to determine an estimated duration for which the battery will power the device if the application is running. The estimated duration can be based on the application's expected battery consumption rate and the current remaining battery power. Accordingly, the timing module can 304 An application can determine the current remaining battery energy. It is understood that determining the current remaining battery energy of a battery can be done using any suitable technique. For example, an information handling device can 102 , which contains a battery, measure an amount of energy supplied by the information handling device 102 is consumed after the battery has been fully charged, and the amount of energy supplied by the information handling device102 Subtract the amount of energy consumed from the total energy capacity of the battery to determine the current remaining battery energy.

[0057] In one embodiment, the estimated duration during which the battery powers the information handling device can be 102The estimated time the battery will power the information handling device can be calculated by adding an application's expected battery consumption rate to its current battery consumption rate to obtain a combined battery consumption rate, and then dividing the current remaining battery energy by the combined battery consumption rate. For example, if an expected battery consumption rate is 5% of the battery capacity per hour and a current battery consumption rate is 8% of the battery capacity per hour, the combined battery consumption rate would be 13% of the battery capacity per hour. If the current remaining battery energy is then 52%, the estimated time the battery will power the information handling device would be... 102The battery life, if the application were running, would be 4 hours (e.g., 52% remaining energy / 13% energy consumption per hour = 4 hours). It is understood that the current battery consumption rate can be determined by measuring the amount of energy consumed over time or by any other suitable method. In certain embodiments, an estimated duration for which the battery would power the information handling device may be provided. 102 will supply energy for multiple applications.

[0058] In one embodiment, the display module 306 The estimated time duration is displayed along with a representation of the application. In some versions, the display module can... 306 Display the estimated time duration for multiple applications, showing a representation of each application. The display module 306 can the display device 210Use this to display the estimated runtime for an application along with its representation. The application's representation can be any suitable representation, such as an icon, an image, a label, and so on.

[0059] By displaying the estimated duration for which an application will run (e.g., based on the battery capacity consumed by the application), a user can determine whether they have sufficient battery power to use a desired application. For example, a user who needs to make a long phone call can determine whether they have enough battery power to make such a call. Similarly, a user who wants to play a game application can determine whether they have enough battery power to play the desired game. Finally, a user who wants to use mapping or navigation software can determine whether they have enough battery power to travel between one or more locations.

[0060] In certain configurations, a user may be able to specify which applications they wish to use and for how long. The battery consumption module 104 An application can combine all the information entered by the user and determine whether the user has sufficient battery power to operate all their desired applications for the desired duration. Furthermore, the battery consumption module provides information on battery usage. 104 an application indicates how long additional applications will run based on user input for the planned application usage.

[0061] Fig. Figure 4 is a schematic block diagram showing another embodiment of a device. 400 depicts a battery consumption module 104 an application includes. As shown, the device includes 400 an embodiment of the information handling device 102Furthermore, the information handling device includes 102 one embodiment of the display device 210 to display various elements.

[0062] The display device 210 can display any suitable elements. In the illustrated embodiment, the display device shows 210 a representation of a game application 404 , a representation of a mapping application 406 , a representation of a browser application 408 , a representation of a telephone application 410 , a representation of a video application 412 , and a representation of a messaging application 414Each representation of an application can include one or more of an application label, an icon corresponding to the application, an image corresponding to the application, and any other representation of the application. In certain embodiments, the selection of the application's representation can execute the application.

[0063] The information handling device 102 the device 400 includes a battery setting 416 an application that can be used to display an estimated time duration during which any application that displays the applications 404 , 406 , 408 , 410 , 412 and 414 This corresponds to having sufficient battery power to function if it is executed as described in Fig. Section 5 is explained in more detail. In one embodiment, the battery setting can be adjusted. 416An application should include an option that can be selected by a user and, when selected, displays the estimated time that each application will have sufficient battery power to function if it is running.

[0064] Fig. Figure 5 is a schematic block diagram showing another embodiment of a device 500 depicts a battery consumption module 104 an application. In the illustrated embodiment, the battery setting 416 an application set to display the estimated time that each application will have sufficient battery power to function if it is running.

[0065] As shown, in particular, an initial estimated time is given. 502 displayed, indicating that the battery of the information handling device is low. 102All currently running programs, in addition to the game application (e.g., one that is not currently running), can be used for 4 hours and 10 minutes. Furthermore, a second estimated time is given. 504 displayed, indicating that the battery of the information handling device is low. 102 All currently running programs, in addition to the map application (e.g., one that is not currently running), can be used for 1 hour and 30 minutes. Furthermore, a third estimated time is calculated. 506 displayed, indicating that the battery of the information handling device is low. 102 All currently running programs in addition to the browser application (e.g., which is not currently running) can be used for 6 hours and 35 minutes.

[0066] In addition, a fourth estimated time is provided. 508 displayed, indicating that the battery of the information handling device is low. 102All currently running programs, in addition to the phone application (e.g., one that is not currently running), can be used for 8 hours and 30 minutes. Furthermore, a fifth estimated time is also available. 510 displayed, indicating that the battery of the information handling device is low. 102 All currently running programs, in addition to the video application (e.g., one that is not currently running), can be used for 6 hours and 20 minutes. Furthermore, a sixth estimated time is calculated. 512 displayed, indicating that the battery of the information handling device is low. 102 All currently running programs in addition to the messaging service application (e.g., which is not currently running) can be used for 7 hours and 40 minutes.

[0067] In certain implementations, a user can select how long an application should be used, such as via the battery settings. 416from applications or by selecting one of the estimated times. After a user has selected how long to use an application, other time estimates can be updated to provide an estimate of how long they will run if run in addition to any user-defined activity times. For example, a user can specify that they intend to use the map application. 1 to use for an hour. Accordingly, in such an example, the fourth estimated time can be 508 , which corresponds to the phone application, will be updated to specify an activity time of 2 hours (e.g., which may or may not overlap with the operation of the map application), taking into account the use of the map application during 1 hour.

[0068] Fig. 6 is a flowchart that represents an embodiment of a process 600for planning battery consumption. In some embodiments, the method is 600 by a device, such as the information handling device 102 , executed. In other embodiments, the method can 600 through a module, such as the battery consumption module 104 an application. In certain embodiments, the method can be carried out. 600 executed by a processor that runs program code, for example by a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or the like.

[0069] The procedure 600 can determine 602 This includes an expected battery consumption rate of an application. In certain embodiments, the battery consumption determination module may include 302Determine the expected battery consumption rate of an application. In some embodiments, determining this includes 602 Determining the expected battery consumption rate of the application involves analyzing the application's past battery consumption data. In various embodiments, analyzing the application's past battery consumption data includes accessing a memory location on the device that contains the past battery consumption data. In certain embodiments, analyzing the application's past battery consumption data may involve accessing a remote storage device that contains the past battery consumption data. Furthermore, in some embodiments, an expected battery consumption rate can be determined for multiple applications. In some embodiments, determining the expected battery consumption rate includes... 602Determining the expected battery consumption rate of the application when the application is not running.

[0070] The procedure 600 can also determine 604 The estimated duration for which the battery will power a device if the application is running may include an estimated duration for which the battery will power the device. This estimated duration may be based on the expected battery consumption rate of the application and the current remaining battery energy. In certain embodiments, the timing module may include 304 Determine the estimated duration of an application 604 , during which the battery will power the device if the application is executed. In one embodiment, determining includes 604The estimated duration for which the battery will power the device if the application is running is calculated by adding the application's expected battery consumption rate to the current battery consumption rate to obtain a combined battery consumption rate, and dividing the current remaining battery energy by the combined battery consumption rate. For various embodiments, an estimated duration can be determined for several different applications.

[0071] The procedure 600 can display the estimated duration along with a representation of the application 606 , and the procedure 600 can be terminated. In one embodiment, the display module can 306 Display the estimated duration along with the application's presentation. 606In some versions, several estimated times can be displayed along with corresponding representations of the applications.

[0072] Fig. 7 is a flowchart that represents an embodiment of another method 700 for planning battery consumption. In some embodiments, the method is 700 by a device, such as the information handling device 102 , executed. In other embodiments, the method can 700 through a module, such as the battery consumption module 104 an application. In certain embodiments, the method can be carried out. 700 executed by a processor that runs program code, for example by a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA or the like.

[0073] As shown, determined 702 the procedure700 a basic battery consumption for a current system. For example, the procedure can 700 Determine a battery consumption rate for applications 702 , which are currently running on a system (e.g., on an information handling device) 102The battery consumption rate can be the amount of battery life consumed from the remaining battery life over a period of time. For example, the battery consumption rate can be a percentage of the remaining battery life consumed per second, minute, hour, etc. In one example, a battery consumption rate could be 0.1% of the remaining battery life consumed per minute. In another example, the battery consumption rate could be the amount of energy consumed from the remaining battery energy over a period of time. The period can be any suitable time, such as one second, one minute, one hour, etc.

[0074] The procedure 700 receives 704A user selection of applications that the user wants to run simultaneously. For example, the user can select any number of applications to run at the same time (e.g., a game, a phone, a map, video footage, a browser, a messaging service, etc.). As shown, the procedure can 700 Determine a battery consumption rate for an application A 706 , determine a battery consumption rate for application B 708 , determine a battery consumption rate for an application C 710 and / or determine a battery consumption rate for any number of applications up to a number of N applications 712 The battery consumption rates that are determined depend on the applications selected by the user.

[0075] In the illustrated embodiment, the user has selected applications B and C. For example, application B may have a battery consumption rate of 0.05% of the remaining battery life consumed per minute, and application C may have a battery consumption rate of 0.08% of the remaining battery life consumed per minute.

[0076] The procedure 700 summed up 714 The consumption rates of the selected applications B and C and the base battery. In one example, the sum can be... 714 The consumption rates are 0.1% (e.g., the base battery consumption rate) plus 0.05% (e.g., the battery consumption rate of application B) plus 0.08% (e.g., the battery consumption rate of application C) to yield 0.23% (e.g., the expected battery consumption rate if applications B and C are both running in addition to the applications currently running).

[0077] The procedure 700 certainly 716 then an estimated time during which the system and applications B and C will run, based on the remaining battery life. In one embodiment, the estimated time can be determined by dividing the remaining battery life by the sum of the consumption rates of the selected applications and the base battery. For example, the remaining battery life could be 50%, and the sum of the consumption rates of the selected applications and the base battery could be 0.23%, so the estimated time could be approximately 217 minutes, or 3 hours and 37 minutes (e.g., 50% / 0.23%).

[0078] Furthermore, the procedure can 700 Display the estimated time for the system along with the selected applications. 718 , and then the procedure can begin 700 be completed. For example, the procedure may be completed. 700display with applications B and C 718 that they have 3 hours and 37 minutes of remaining time if they are run together with all other applications currently running on the system.

[0079] The embodiments can be implemented in other specific forms. The described embodiments are to be regarded in every respect as merely exemplary and not as limiting. The scope of the invention is therefore specified by the accompanying claims instead of by the foregoing description. All modifications that fall within the scope and meaning of the equivalence of the claims are to be included within their scope.

Claims

[1] Device comprising: – a display device; – a processor; a memory that stores code executable by the processor, for: – Determining the expected battery consumption rate of an application; – Determining an estimated duration for which the battery will power the device if the application is running, wherein the estimated duration for which the battery will power the device is based on the expected battery consumption rate of the application and the current remaining battery energy; and – Displaying the estimated time duration on the display device along with a visual representation of the application. [2] Device according to claim 1, wherein the code executable by the processor to determine the expected battery consumption rate of the application further comprises code executable by the processor to analyze the application's previous battery consumption data. [3] Device according to claim 2, wherein the code executable by the processor to analyze the application's previous battery consumption data further comprises code executable by the processor to access the memory, wherein the memory comprises the previous battery consumption data. [4] Device according to claim 1, wherein the memory further comprises code that can be executed by the processor to determine a respective expected battery consumption rate for each application of a plurality of applications. [5] Device according to claim 4, wherein the memory further comprises code that can be executed by the processor to determine a respective estimated time period during which the battery will supply power to the device for each application of the plurality of applications, if the respective application is executed. [6] Device according to claim 5, wherein the memory further comprises code that can be executed by the processor to display each estimated time duration together with a respective visual representation of a respective application of the plurality of applications. [7] Device according to claim 1, wherein the code executable by the processor to determine the estimated duration for which the battery will power the device if the application is executed further comprises code executable by the processor to add the expected battery consumption rate of the application to an actual battery consumption rate to obtain a combined battery consumption rate, and to divide the actual remaining battery energy by the combined battery consumption rate. [8] Device according to claim 1, wherein the code executable by the processor to determine the estimated time that the battery will power the device if the application is executed further comprises code executable by the processor to determine a combined estimated time that the battery will power the device for a plurality of applications selected to be executed together, and to display the combined estimated time together with a respective visual representation of each of the multiple applications selected to be executed together. [9] Procedure comprising the following steps: – Determine, using a processor, an expected battery consumption rate of an application; – Determining an estimated duration for which the battery will power a device if the application is running, wherein the estimated duration for which the battery will power the device is based on the expected battery consumption rate of the application and the current remaining battery energy; and – Displaying the estimated time duration along with a visual representation of the application. [10] Method according to claim 9, wherein determining the expected battery consumption rate of the application comprises analyzing the application's previous battery consumption data. [11] Method according to claim 10, wherein analyzing the application's previous battery consumption data comprises at least one of accessing a memory of the device containing the previous battery consumption data and accessing a remote storage device containing the previous battery consumption data. [12] Method according to claim 9, wherein determining the expected battery consumption rate of the application comprises determining the expected battery consumption rate of the application when the application is not running. [13] The method of claim 9, further comprising determining a respective expected battery consumption rate for each application of a plurality of applications. [14] The method of claim 13, further comprising determining a respective estimated time period during which the battery will supply energy to the device for each application of the plurality of applications, if the respective application is carried out. [15] The method of claim 14, further comprising displaying each estimated time duration together with a respective visual representation of each application of the plurality of applications. [16] Method according to claim 9, wherein determining the estimated time for which the battery will power the device if the application is executed comprises adding the expected battery consumption rate of the application to a current battery consumption rate to obtain a combined battery consumption rate, and dividing the current remaining battery energy by the combined battery consumption rate. [17] Program product comprising a computer-readable storage medium that stores code executable by a processor, wherein the executable code comprises code to perform: – Determining the expected battery consumption rate of an application; – Determining an estimated duration for which the battery will power a device if the application is running, wherein the estimated duration for which the battery will power the device is based on the expected battery consumption rate of the application and the current remaining battery energy; and – Displaying the estimated time duration along with a visual representation of the application. [18] Program product according to claim 17, wherein the code further comprises code for performing the determination of a respective expected battery consumption rate for each application and a plurality of applications. [19] Program product according to claim 18, wherein the code further comprises code for performing the determination of a respective estimated time period during which the battery will supply power to the device for each application of the plurality of applications, if the respective application is performed. [20] Program product according to claim 19, wherein the code further comprises code for performing the display of each estimated time duration together with a respective visual representation of a respective application of the plurality of applications.

Images