Adaptive low-battery warnings for battery-powered electronic devices

The disclosed embodiments provide a system that facilitates the use of an electronic device. The electronic device may be a keyboard, a mouse, a trackpad, a remote control, a mobile phone, a wireless phone, a toy, a portable media player, a game controller, and/or a camera. During operation, the system monitors a state-of-charge of a battery used to power the electronic device. Next, the system calculates a charge threshold associated with a low-battery warning for the battery based on the monitored state-of-charge. If the state-of-charge of the battery reaches the charge threshold, the system generates the low-battery warning.

BACKGROUND

The present embodiments relate to battery-powered electronic devices. More specifically, the present embodiments relate to techniques for adaptively generating low-battery warnings based on charge-consumption patterns associated with batteries used to power the electronic devices.

2. Related Art

Batteries may be used to power a variety of electronic devices. For example, AA and/or AAA batteries may be used in devices such as cameras, toys, flashlights, peripheral devices, game controllers, and/or remote controls. On the other hand, lithium-ion and/or lithium-polymer batteries may be used to power mobile phones, portable media players, laptop computers, and/or tablet computers.

In addition, battery-powered electronic devices may include functionality to generate “low-battery warnings” that notify users of reduced states-of-charge in the batteries that may subsequently disrupt use of the electronic devices. For example, a mobile phone may generate a pop-up containing a low-battery warning after the state-of-charge of the battery in the mobile phone drops below 10%. The pop-up may thus allow a user of the mobile phone to plug in the mobile phone and/or reduce the power consumption of the mobile phone before the battery fully depletes and causes the mobile phone to power off.

However, the same types of electronic devices may consume battery power at different rates based on usage patterns associated with the electronic devices. For example, a wireless keyboard may be used by a first user for an average of two hours a day, while the same model of wireless keyboard may be used by a second user for an average of six hours a day. The second user may thus replace and/or recharge the batteries in his/her wireless keyboard about three times as frequently as the first user.

Different battery depletion rates may also cause low-battery warnings to be generated at different times prior to full battery depletion. In turn, such variance in the timing of low-battery warnings may adversely affect the use of battery-powered electronic devices. For example, a low-battery warning for a wireless keyboard may be displayed after the battery for the wireless keyboard falls below 10% capacity. As a result, an infrequent user of the wireless keyboard may find the low-battery warning to be a nuisance because the low-battery warning may be displayed for several weeks before the battery in the wireless keyboard is fully depleted. On the other hand, the low-battery warning may not provide enough notice to a frequent user of the wireless keyboard if the low-battery warning is shown to the user only a few days before the battery in the wireless keyboard runs out of power.

Hence, use of battery-powered electronic devices may be facilitated by mechanisms that generate low-battery warnings for the electronic devices in a consistent and/or timely manner.

SUMMARY

The disclosed embodiments provide a system that facilitates the use of an electronic device. The electronic device may be a keyboard, a mouse, a trackpad, a remote control, a mobile phone, a wireless phone, a toy, a portable media player, a game controller, and/or a camera. During operation, the system monitors a state-of-charge of a battery used to power the electronic device. To monitor the state-of-charge of the battery, the system periodically measures a voltage of the battery, determines the state-of-charge of the battery based on the measured voltage, and records the state-of-charge and a timestamp associated with the measured voltage.

Next, the system calculates a charge threshold associated with a low-battery warning for the battery based on the monitored state-of-charge. To calculate the charge threshold, the system calculates an average charge consumption associated with the battery using the monitored state-of-charge and multiplies the average charge consumption by a trigger period associated with the low-battery warning. The trigger period may correspond to a pre-specified period of time before the battery is fully depleted. In addition, the system may calculate the average charge consumption by calculating a total charge consumption associated with a monitoring window of the monitored state-of-charge and dividing the total charge consumption by a monitoring period spanned by the monitoring window.

If the state-of-charge of the battery reaches the charge threshold, the system generates the low-battery warning. For example, the system may generate the low-battery warning by displaying the low-battery warning to a user of the electronic device. On the other hand, if the state-of-charge of the battery has not reached the charge threshold, the system recalculates the charge threshold based on the monitored state-of-charge. By recalculating the charge threshold until the state-of-charge reaches the charge threshold, the system may facilitate the timely and/or consistent generation of the low-battery warning, independently of changes to the powering and/or use of the electronic device.

DETAILED DESCRIPTION

FIG. 1shows an electronic device102in accordance with an embodiment. Electronic device102may correspond to a keyboard, a mouse, a trackpad, a remote control, a wireless and/or mobile phone, a toy, a camera, a game controller, a portable media player, and/or other device that is powered by one or more batteries104-106. For example, electronic device102may be used with standard-sized batteries such as AAA batteries, AA batteries, C batteries, D batteries, and/or nine-volt batteries. On the other hand, batteries104-106may correspond to lithium-ion and/or lithium-polymer batteries that are designed to fit within the enclosure of electronic device102.

As electronic device102is used, chemical energy stored in batteries104-106may be converted into electrical energy that is used to operate one or more electrical components in electronic device102. For example, batteries104-106may power a processor, memory, storage, touchscreen, microphone, speaker, and/or radio transceiver in a mobile phone, allowing a user of the mobile phone to make and receive calls, send and receive emails, and/or browse the web on the mobile phone. Because the energy stored in batteries104-106is limited, batteries104-106may be recharged and/or replaced to enable continued use of electronic device102. Conversely, full depletion of batteries104-106during use of electronic device102may cause electronic device102to power off, and in turn, disrupt use of electronic device102by a user.

Electronic device102may also be configured for use with other electronic devices. As shown inFIG. 2, a set of electronic devices202-206may include functionality to communicate with one another. For example, electronic device202may correspond to a wireless keyboard, electronic device204may correspond to a wireless mouse, and electronic device206may be a laptop and/or desktop computer for which electronic devices202-204operate as input devices. As a result, a user may interact with the computer system represented by electronic device206by providing input to electronic devices202-204and receiving output from a display in electronic device206.

To facilitate use of electronic devices202-206, low-battery warnings may be generated to notify a user that limited battery life in one or more electronic devices202-204may disrupt operation of the electronic device(s) in the near future. For example, electronic devices202-204may provide battery “gas gauges” that convert voltage and/or current measurements from batteries used to power electronic devices202-204into state-of-charge values for the batteries. The state-of-charge values may be obtained by electronic device206and compared with a predefined threshold (e.g., 10%) for low-battery states in electronic devices202-204. Electronic device206may then display low-battery warnings for electronic devices202-204if the state-of-charge values have reached or dropped below the threshold.

However, batteries may be fully depleted at different rates based on the devices (e.g., electronic devices202-206) powered by the batteries, the types of batteries used within the devices, and/or the usage patterns associated with the devices. First, the same types of batteries may be associated with different depletion rates for different electronic devices (e.g., electronic devices202-206). For example, two AA batteries may power a first type of game controller for 36 hours and a second type of game controller for 55 hours. Next, different depletion rates may result from the use of different types of batteries to power the same electronic device. For example, a set of alkaline AA batteries may power a digital camera for 1-3 times as long as a set of nickel-cadmium (NiCd) AA batteries. Finally, the period of time over which an electronic device is powered by a battery may vary based on the amount of use associated with the electronic device. For example, frequent use of a wireless keyboard may fully deplete the batteries in the wireless keyboard after one month, while occasional use of the wireless keyboard may allow the same types of batteries to power the wireless keyboard for over two months.

Such differences in battery depletion rates may additionally cause low-battery warnings to be displayed at different times prior to full battery depletion. For example, low-battery warnings for a wireless mouse may be triggered after the state-of-charge of the battery in the wireless mouse drops below 10%. A user who infrequently uses the wireless mouse may be shown a low-battery warning for over a month before the battery is fully depleted, while a user who constantly uses the wireless mouse may be notified of a low battery only a few days before the battery runs out of power. As a result, low-battery warnings may irritate some users if the low-battery warnings are displayed for long periods of time before the batteries associated with the low-battery warnings run out of power. On the other hand, the same low-battery warnings may not provide enough notice for other users if the low-battery warnings are displayed only a few hours or a few days before the batteries are fully depleted.

Furthermore, low-battery warnings may be generated at different times prior to full battery depletion in different devices (e.g., electronic devices202-206). For example, a user may receive a low-battery warning for a wireless mouse two weeks before the wireless mouse powers off and a low-battery warning for a wireless keyboard two days before the battery for the wireless keyboard runs out of power. Such device-based inconsistencies in the timing of low-battery warnings may cause confusion for users by preventing the users from using the same time scale to manage low-battery states in different devices.

In one or more embodiments, electronic devices202-206include functionality to generate low-battery warnings in a consistent and/or timely manner. For example, electronic devices202-206may be configured to generate low-battery warnings approximately two weeks before the batteries in electronic devices202-206are fully depleted, regardless of the types of devices used, the types of batteries used to power the devices, and/or the usage patterns associated with each device.

More specifically, monitoring apparatuses212-214in each battery-powered electronic device (e.g., electronic devices202-204) may monitor the state-of-charge of a battery used to power the electronic device. Each monitoring apparatus212-214may periodically (e.g., once a minute, once every five minutes, etc.) measure a voltage of the corresponding battery, determine the state-of-charge of the battery based on the measured voltage, and record the state-of-charge and a timestamp associated with the measured voltage.

Next, an analysis apparatus208in electronic device206and/or electronic devices202-204may calculate a charge threshold associated with a low-battery warning for the battery based on the monitored state-of-charge. The charge threshold may represent a state-of-charge of the battery at which a low-battery warning should be generated to provide a certain amount of notice to the user before the battery is fully depleted. In other words, the charge threshold may allow the low-battery warning to be generated at a pre-specified period before the battery is fully depleted.

If the state-of-charge reaches or falls below the charge threshold, a notification apparatus210in electronic device206and/or electronic devices202-204may generate a low-battery warning. For example, notification apparatus210may display the low-battery warning to the user through a graphical user interface (GUI) in electronic device206and/or electronic devices202-204.

On the other hand, if the state-of-charge has not reached the charge threshold, notification apparatus210may recalculate the charge threshold based on the monitored state-of-charge (e.g., from monitoring apparatuses212-214). For example, notification apparatus210may recalculate the charge threshold after obtaining a new state-of-charge from monitoring apparatus214every five minutes to maintain an up-to-date charge threshold that reflects the usage patterns associated with electronic device204. Calculation and use of charge thresholds associated with low-battery warnings is discussed in further detail below with respect toFIG. 3.

FIG. 3shows a system for facilitating use of an electronic device302in accordance with an embodiment. Electronic device302may correspond to a keyboard, a mouse, a trackpad, a remote control, a phone, a toy, a camera, a game controller, a portable media player, and/or other device that is powered by a battery306. In addition, electronic device302may be configured to communicate with a different electronic device. For example, electronic device302may function as a wireless input device (e.g., keyboard, mouse, trackpad, remote control, webcam, game controller) that obtains input from a user and transmits data associated with the input to another electronic device (e.g., laptop computer, desktop computer, game console, television) with which the user is interacting.

As mentioned above, the system ofFIG. 3may be used to generate a low-battery warning330for a battery306that supplies power to electronic device302. First, a monitoring apparatus308in electronic device302may periodically measure a voltage304of battery306and determine a state-of-charge314of battery306based on the measured voltage304. For example, monitoring apparatus308may be implemented by a microcontroller unit (MCU) in electronic device302that converts measurements of voltage304into state-of-charge314values using one or more discharge curves for battery306.

Next, monitoring apparatus308may record state-of-charge314and a timestamp316associated with the measured voltage304. For example, monitoring apparatus308may maintain a log file containing a state-of-charge314calculated from a measurement of voltage304and a value for timestamp316representing the time at which the measurement was made. Alternatively, monitoring apparatus308may transmit voltage304, state-of-charge314, and/or timestamp316to another electronic device (e.g., computer system) for processing and/or recording of voltage304, state-of-charge314, and/or timestamp316.

An analysis apparatus310may then calculate a charge threshold328using the monitored state-of-charge314and timestamp316. In one or more embodiments, charge threshold328is used to generate low-battery warning330at a time that represents a pre-specified period before battery306is fully depleted. For example, charge threshold328may correspond to a value for state-of-charge314that represents a full depletion of battery306in ten days.

As a result, charge threshold328may vary based on the type of battery306used to power electronic device302, the type of electronic device302powered by battery306, and/or the usage patterns associated with electronic device302. For example, charge threshold328may be lower if battery306is associated with a higher capacity, electronic device302consumes less power, and/or electronic device302is infrequently used. Conversely, charge threshold328may be higher if battery306is associated with a lower capacity, electronic device302consumes more power, and/or electronic device302is frequently used.

To calculate charge threshold328, analysis apparatus310may first calculate a total charge consumption320associated with a monitoring window318of the monitored state-of-charge314. Monitoring window318may represent an adjustable, sliding window of time from which values for state-of-charge314and/or timestamp316are obtained to calculate charge threshold328. For example, monitoring window318may correspond to a ten-day window that ends at the most recent value of timestamp316obtained from monitoring apparatus308and begins ten days prior to the date represented by the most recent value of timestamp316. Total charge consumption320may thus be calculated by subtracting the most recent and/or lowest value for state-of-charge314within monitoring window318from the oldest and/or highest value for state-of-charge314within monitoring window318. Continuing with the previous example, total charge consumption320for a ten-day monitoring window318may be calculated by subtracting the newest value for state-of-charge314from a value for state-of-charge314that was obtained ten days prior to the newest value.

Next, analysis apparatus310may calculate an average charge consumption324by dividing total charge consumption320by a monitoring period322spanned by monitoring window318. For example, a daily average charge consumption324may be calculated by dividing total charge consumption320by the number of days spanned by monitoring window318.

Finally, analysis apparatus310may calculate charge threshold328based on average charge consumption324and a trigger period326associated with low-battery warning330. Trigger period326may represent the pre-specified period of time before battery306is fully depleted at which low-battery warning330is to be generated. As a result, charge threshold328may be obtained by multiplying average charge consumption324by trigger period326. For example, charge threshold328may be calculated by multiplying a daily average charge consumption324by the number of days in trigger period326.

Charge threshold328may then be used to generate low-battery warning330within a notification apparatus312. In particular, notification apparatus312may generate low-battery warning330if the current value of state-of-charge314reaches charge threshold328. For example, notification apparatus312may generate low-battery warning330by displaying a pop-up window containing low-battery warning330within a display associated with electronic device302and/or another electronic device.

On the other hand, if the current value of state-of-charge314has not reached charge threshold328, analysis apparatus310may recalculate charge threshold328based on monitored values of state-of-charge314. For example, analysis apparatus310may recalculate total charge consumption320using a new monitoring window318that includes the current value of state-of-charge314, obtain a new value for average charge consumption324from total charge consumption320, and multiply the new average charge consumption324by trigger period326to obtain a new value of charge threshold328.

Consequently, the system ofFIG. 3may facilitate timeliness and/or consistency in the generation of low-battery warning330, regardless of the usage patterns and/or types of batteries associated with electronic device302. First, the depletion rate of battery306within electronic device302may be identified by continuous monitoring of state-of-charge314. Next, a sliding monitoring window318may ensure that total charge consumption320and average charge consumption324reflect the most recent usage patterns for electronic device302. The calculation of charge threshold328using trigger period326may additionally facilitate the generation of low-battery warning330at a time that is neither too early nor too late for a user of electronic device302. Finally, the continuous update of charge threshold328may ensure that changes to the powering and/or use of electronic device302do not affect the generation of low-battery warning330at the pre-specified period before battery306is fully depleted.

Those skilled in the art will appreciate that the system ofFIG. 3may be implemented in a variety of ways. First, monitoring apparatus308, analysis apparatus310, and notification apparatus312may be implemented by electronic device302. For example, a mobile phone and/or tablet computer may include functionality to monitor state-of-charge314, calculate charge threshold328, and display low-battery warning330to a user. Alternatively, some or all of monitoring apparatus308, analysis apparatus310, and/or notification apparatus312may reside on a different electronic device that includes functionality to communicate with electronic device302. For example, a wireless keyboard may transmit values for voltage304, state-of-charge314, and/or timestamp316to a device driver in a computer system for which the wireless keyboard is an input device. The device driver may process the transmitted values to calculate charge threshold328, and an operating system in the computer system may display low-battery warning330in a pop-up window to the user once state-of-charge314reaches charge threshold328.

FIG. 4shows a flowchart illustrating the process of facilitating use of an electronic device in accordance with an embodiment. In one or more embodiments, one or more of the steps may be omitted, repeated, and/or performed in a different order. Accordingly, the specific arrangement of steps shown inFIG. 4should not be construed as limiting the scope of the embodiments.

Initially, a state-of-charge of a battery used to power the electronic device is monitored (operation402). Monitoring of a battery's state-of-charge is discussed in further detail below with respect toFIG. 5. Next, a charge threshold associated with a low-battery warning for the battery is calculated based on the monitored state-of-charge (operation404). Calculation of a charge threshold associated with a low-battery warning is discussed in further detail below with respect toFIG. 6.

The state-of-charge may reach the charge threshold (operation406) as the battery is used to power the electronic device. For example, the state-of-charge may gradually drop as the battery supplies power to the electronic device and eventually reach the charge threshold if the battery is not recharged and/or replaced. If the charge threshold has not been reached, the charge threshold is recalculated based on the monitored state-of-charge (operation404). In other words, the charge threshold may be continuously recalculated as long as the state-of-charge has not reached the charge threshold.

If the battery's state-of-charge has reached the charge threshold, a low-battery warning is generated (operation408). For example, the low-battery warning may correspond to a visual and/or audio notification that alerts a user of the need to replace and/or recharge the battery before the battery fully depletes and disrupts use of the electronic device.

FIG. 5shows a flowchart illustrating the process of monitoring the state-of-charge of a battery in accordance with an embodiment. In one or more embodiments, one or more of the steps may be omitted, repeated, and/or performed in a different order. Accordingly, the specific arrangement of steps shown inFIG. 5should not be construed as limiting the scope of the embodiments.

To monitor the state-of-charge, a voltage of the battery is periodically measured (operation502). Next, the state-of-charge of the battery is determined based on the measured voltage (operation504). For example, the measured voltage may be converted into the state-of-charge using one or more discharge curves for the battery. Finally, the state-of-charge and a timestamp associated with the measured voltage are recorded (operation506). For example, the measured voltage, state-of-charge, and/or timestamp may be stored in a log file for subsequent processing and/or retrieval.

FIG. 6shows a flowchart illustrating the process of calculating a charge threshold associated with a low-battery warning for a battery in accordance with an embodiment. In one or more embodiments, one or more of the steps may be omitted, repeated, and/or performed in a different order. Accordingly, the specific arrangement of steps shown inFIG. 6should not be construed as limiting the scope of the embodiments.

First, a total charge consumption associated with a monitoring window of a monitored state-of-charge of the battery is calculated (operation602). The total charge consumption may be calculated by subtracting the newest and/or lowest value for the state-of-charge within the monitoring window from the oldest and/or highest value for the state-of-charge within the monitoring window.

Next, an average charge consumption associated with the battery is calculated by dividing the total charge consumption by a monitoring period spanned by the monitoring window (operation604). For example, a daily average charge consumption may be obtained by dividing the total charge consumption by the number of days in the monitoring window. Alternatively, the average charge consumption for a different unit of time (e.g., one hour, 12 hours, one week) may be calculated by dividing the total charge consumption by the number of units of time in the monitoring window.

Finally, the charge threshold is calculated based on the monitored state-of-charge by multiplying the average charge consumption by a trigger period associated with the low-battery warning (operation606). The trigger period may correspond to a pre-specified period of time before the battery is fully depleted. For example, the charge threshold may be calculated by multiplying a daily average charge consumption by the number of days in the trigger period.

In other words, the charge threshold may be calculated using the following equation:

T⁢⁢%=n⁢⁢%Dwindow×DTrigger
Within the equation, T % may represent the charge threshold, n % may represent the total charge consumption, Dwindowmay represent the monitoring window, and DTriggermay represent the trigger period.

FIG. 7shows a computer system700in accordance with an embodiment. Computer system700includes a processor702, memory704, storage706, and/or other components found in peripheral devices, portable electronic devices, and/or consumer electronic devices. Processor702may support parallel processing and/or multi-threaded operation with other processors in computer system700. Computer system700may also include input/output (I/O) devices such as a keyboard708, a mouse710, and a display712.

Computer system700may include functionality to execute various components of the present embodiments. In particular, computer system700may include an operating system (not shown) that coordinates the use of hardware and software resources on computer system700, as well as one or more applications that perform specialized tasks for the user. To perform tasks for the user, applications may obtain the use of hardware resources on computer system700from the operating system, as well as interact with the user through a hardware and/or software framework provided by the operating system.

In one or more embodiments, computer system700provides a system for facilitating use of an electronic device. The system may include a monitoring apparatus that monitors a state-of-charge of a battery used to power the electronic device. The system may also include an analysis apparatus that calculates a charge threshold associated with a low-battery warning for the battery based on the monitored state-of-charge. Finally, the system may include a notification apparatus that generates the low-battery warning if the state-of-charge of the battery reaches the charge threshold.

In addition, one or more components of computer system700may be remotely located and connected to the other components over a network. Portions of the present embodiments (e.g., monitoring apparatus, analysis apparatus, notification apparatus, etc.) may also be located on different nodes of a distributed system that implements the embodiments. For example, the present embodiments may be implemented using a cloud computing system that monitors and manages the use of batteries in remote electronic devices.