The technology described in this patent document relates generally to systems and devices that utilize a rechargeable battery. More particularly, systems and methods are provided for monitoring the deterioration of a rechargeable battery.
The deterioration of a rechargeable battery relates to the amount that one or more performance characteristics of the battery have degraded over time. The battery performance characteristics that are subject to deterioration include, for example, the charge capacity of the battery and the battery's equivalent series resistance (ESR). The charge capacity of the battery is a measure of the amount of energy that may be stored in the battery when fully charged. The ESR of the battery is relevant to determining the amount of current that the battery is capable of delivering. It is desirable in many systems and devices to monitor the deterioration of one or more battery performance characteristics, for instance, to determine when the rechargeable battery should be replaced.
The battery monitoring system 12 may include one or more processing devices, such as a microprocessor or DSP, and may also include one or more sensor devices for detecting operating parameters of the battery 14. For example, the battery monitoring system 12 may include sensor devices to detect the ambient temperature of the battery, the charge or discharge current of the battery, the battery voltage, and/or other operating parameters. In one example, the battery monitoring system 12 may be incorporated into the charging subsystem of a mobile device (see, e.g.,
The data store 16 may be any type of non-volatile data storage device, such as a flash memory or other memory device. The dotted line between the rechargeable battery 14 and the data store 16 indicates that the data store 16 is associated with the battery 14. In one embodiment, for example, the data store 16 may be physically attached or internal to the rechargeable battery 14. In this manner, the stored information relating to the rechargeable battery 14 may be maintained even if the rechargeable battery 14 is moved from one system or device to another.
In operation, data relating to the deterioration of the rechargeable battery 14 is monitored by the battery monitoring system 12 and stored in the data store 16. The battery monitoring system 12 may also cause information relating to the battery deterioration to be shown on the display 18. Battery deterioration relates to the amount by which one or more battery performance characteristics, such as the rechargeable battery's ability to store and/or deliver a charge, have diminished over time. Battery deterioration may be caused by one or more factors that are monitored by the battery monitoring system 12 to determine the present deterioration of a battery performance characteristic. As illustrated, the battery performance characteristics may include the battery's charge capacity and/or equivalent series resistance (ESR). Both of these battery performance characteristics (capacity and ESR) are subject to deterioration over time.
The deterioration of a rechargeable battery over time is caused by the combination of numerous environmental and operational factors. An exact calculation relating to the percent deterioration of a battery performance characteristic should take all of these factors into account, and is therefore not feasible (if even possible) for most applications. However, a close approximation of the percent deterioration of a battery performance characteristic may be achieved by monitoring the factors that most dramatically affect its deterioration. As illustrated in
In one example, the battery monitoring system 12 may determine an amount of deterioration of a battery performance characteristic based, at least in part, on the number of charge cycles incurred by the battery 14 and the degree to which each of the charge cycles are full charge cycles or partial charge cycles. For instance, each time the battery 14 is charged, the battery monitoring system 12 may increment a count of the number of charge cycles stored in the data store 16. In addition, the battery monitoring system 12 may monitor whether the battery is fully or partially charged and include this information in the data store 16 along with the charge cycle count. The stored information relating to the number of full and partial charge cycles may then be used by the battery monitoring system 12 to determine the percent deterioration of a battery performance characteristic, for example by using a stored deterioration look-up table or algorithm that is specific to the type of battery 14.
For instance, the battery monitoring system 12 may utilize an algorithm or look-up table that associates a certain percentage of battery deterioration to every charge or discharge cycle incurred by the battery 14. The percentage of battery deterioration associated with a charge or discharge cycle may then be weighted by a predetermined amount depending on whether the charge or discharge cycle was full or partial. Even further, different weighting factors may be applied to the deterioration calculation depending on the degree to which the battery is charged or discharged during a cycle (e.g., weight A for a quarter charge, weight B for a half charge, weight C for a three-quarter charge, and weight D for a full charge).
The accuracy of the battery deterioration calculated by the battery monitoring system 12 may be improved by adding further dimensions to the look-up table or algorithm that take into consideration additional environmental or operational factors. For example,
In addition to monitoring operational and environmental factors during charge and discharge cycles, the battery monitoring system 12 may also account for battery deterioration during periods when the battery is not in use. With reference again to
In another example, the battery monitoring system 12 may also monitor and record the charge level at which the battery is stored (i.e., the charge level when the battery is not being charged or discharged). For example, it is known that a LiIon battery that is stored with a partial charge deteriorates more slowly than a battery that is stored with a full charge. Therefore, storage charge level information may be used along with the battery age and storage temperature information to determine an even closer approximation of battery deterioration.
When a battery deterioration event is detected, the method 30 accesses a data store at step 34 to determine the last calculated deterioration value for one or more battery performance characteristics, such as battery capacity or ESR. For example, a stored deterioration value relating to battery capacity may indicate that the maximum available storage capacity of the battery has deteriorated to a certain percentage of its original value when last calculated.
In step 36, the method identifies one or more environmental or operational factors affecting the amount of deterioration caused by the battery deterioration event. For example, if the detected battery deterioration event is a charge cycle, then the method may determine whether the charge cycle is full or partial, the rate at which the battery is charged during the charge cycle, the age of the battery during the charge cycle, and/or other factors relevant to the amount of battery deterioration incurred during a charge cycle.
In step 38, the method accesses an algorithm or look-up table from memory for use in determining the amount of deterioration caused by the event. For instance, the method may select an algorithm or look-up table that is specific to the type of battery (e.g., the battery's chemical composition) and/or the type of deterioration event. In addition, different algorithms or look-up tables may be selected depending on one or more of the detected deterioration factors, such as the age of the battery, the temperature during the deterioration event and/or other factors. It should be understood that the number of stored algorithms or look-up tables and the number of dimensions in each algorithm or look-up table is a design choice that may be modified depending on the processing capabilities of the system and/or other design criteria. For instance, in one example all of the available battery deterioration events and battery deterioration factors could be incorporated into a single multi-dimensional look-up table. In other examples, however, multiple look-up tables or algorithms could be used to reduce the number of dimensions in each.
The selected algorithm or look-up table is applied in step 40, and the updated deterioration value is stored to memory in step 42 and displayed in step 44. For example, the selected algorithm or look-up table may be used to determine that the event resulted in a certain percentage of additional deterioration to the relevant battery performance characteristics. This amount may then be added to the previously stored percent deterioration and displayed on the device.
Example displays relating to the deterioration of a battery performance characteristic are illustrated in
Another example of a display 60 showing the deterioration of a battery performance characteristic is illustrated in
In addition to monitoring battery deterioration, the charging subsystem 202 charges the rechargeable battery 204 and provides power to the mobile device 200, either from the rechargeable battery 204 or from a USB host connected to the USB interface 220. The USB controller 222 monitors the USB data lines, and controls data communication between the processing device 206 and a USB host.
The processing device 206 controls the overall operation of the mobile device 200. Operating system software executed by the processing device 206 is preferably stored in a persistent store such as a flash memory 218, but may also be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element. In addition, operating system software, specific device applications, or parts thereof, may be temporarily loaded into a volatile store, such as a random access memory (RAM) 216. Communication signals received by the mobile device 200 may also be stored to RAM 216.
The processing device 206, in addition to its operating system functions, enables execution of software applications on the device 200. A predetermined set of applications that control basic device operations, such as data and voice communications, may be installed on the device 200 during manufacture. In addition, a personal information manager (PIM) application may be installed during manufacture. The PIM is preferably capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items. The PIM application is also preferably capable of sending and receiving data items via the wireless network 226. Preferably, the PIM data items are seamlessly integrated, synchronized and updated via the wireless network 226 with the device user's corresponding data items stored or associated with a host computer system.
Communication functions, including data and voice communications, are performed through the communication subsystem 208, and possibly through the short-range communications subsystem 210. If the mobile device 200 is enabled for two-way communications, then the communication subsystem 200 includes a receiver 228, a transmitter 230, and a processing module 232, such as a digital signal processor (DSP). In addition, the communication subsystem 208, configured as a two-way communications device, includes one or more, preferably embedded or internal, antenna elements 234, 236, and local oscillators (LOs) 238. The specific design and implementation of the communication subsystem 208 is dependent upon the communication network 226 in which the mobile device 200 is intended to operate. Network access requirements vary depending upon the type of communication system 226.
When required network registration or activation procedures have been completed, the mobile device 200 may send and receive communication signals over the communication network 226. Signals received by the antenna 234 through the communication network 226 are input to the receiver 228, which may perform such common receiver functions as signal amplification, frequency down-conversion, filtering, channel selection, and analog-to-digital conversion. Analog-to-digital conversion of the received signal allows the DSP to perform more complex communication functions, such as demodulation and decoding. In a similar manner, signals to be transmitted are processed by the DSP 232, and are then input to the transmitter 230 for digital-to-analog conversion, frequency up-conversion, filtering, amplification and transmission over the communication network 208 via the antenna 236.
In addition to processing communication signals, the DSP 232 provides for receiver 228 and transmitter 230 control. For example, gains applied to communication signals in the receiver 228 and transmitter 230 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 232.
In a data communication mode, a received signal, such as a text message or web page download, is processed by the communication subsystem 208 and input to the processing device 206. The received signal is then further processed by the processing device 206 for output to a display 212 (which may serve the function of the battery deterioration display 18 of
In a voice communication mode, overall operation of the device 200 is substantially similar to data communication mode, except that received signals are output to a speaker 214, and signals for transmission are generated by a microphone 215. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the device 200. In addition, the display 212 may also be utilized in voice communication mode, for example to display the identity of a calling party, the duration of a voice call, or other voice call related information.
The short-range communications subsystem 210 enables communication between the mobile device 200 and other proximate systems or devices, which need not necessarily be similar devices. For example, the short-range communications subsystem 210 may include an infrared device and associated circuits and components, or a Bluetooth™ communication module to provide for communication with similarly-enabled systems and devices.
This written description uses examples to disclose the invention, including the best mode, and also to enable a person skilled in the art to make and use the invention. The invention described herein may provide certain advantages, such as a more accurate approximation of battery deterioration, an enhanced information display for the benefit of the user, and/or other advantages. The patentable scope of the invention may include other examples that occur to those skilled in the art. For example,
This is a continuation of U.S. application Ser. No. 13/567,163, filed Aug. 6, 2012, which is a division of U.S. application Ser. No. 12/536,659, filed Aug. 6, 2009 (now U.S. Pat. No. 8,255,176), which claims priority from U.S. Provisional Application No. 61/086,985, filed Aug. 7, 2008, all the above applications hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5557188 | Piercey | Sep 1996 | A |
5690685 | Kroll et al. | Nov 1997 | A |
5862515 | Kobayashi et al. | Jan 1999 | A |
5904705 | Kroll et al. | May 1999 | A |
6337560 | Kalogeropoulos et al. | Jan 2002 | B1 |
6400123 | Bean et al. | Jun 2002 | B1 |
6420851 | Schoofs et al. | Jul 2002 | B1 |
6424123 | Odaohhara et al. | Jul 2002 | B1 |
6522101 | Malackowski | Feb 2003 | B2 |
6545448 | Stanley et al. | Apr 2003 | B1 |
6563318 | Kawakami et al. | May 2003 | B2 |
6577104 | Sakakibara | Jun 2003 | B2 |
6617829 | Smith | Sep 2003 | B1 |
6630814 | Ptasinski et al. | Oct 2003 | B2 |
6683440 | Kawakami et al. | Jan 2004 | B2 |
6760625 | Kroll | Jul 2004 | B1 |
6794849 | Mori et al. | Sep 2004 | B2 |
6932174 | Hirata et al. | Aug 2005 | B2 |
6982544 | Tran | Jan 2006 | B2 |
7078907 | Uesaka et al. | Jul 2006 | B2 |
7091693 | Grunert et al. | Aug 2006 | B2 |
7091698 | Yamazaki et al. | Aug 2006 | B2 |
7107160 | Bean | Sep 2006 | B2 |
7123155 | Schinner | Oct 2006 | B2 |
7190171 | Kawakami et al. | Mar 2007 | B2 |
7191077 | Mese et al. | Mar 2007 | B2 |
7211987 | Aoki et al | May 2007 | B2 |
7227335 | Sakakibara et al. | Jun 2007 | B2 |
7301305 | Tran | Nov 2007 | B2 |
7388383 | Kawakami et al. | Jun 2008 | B2 |
7420374 | Chen | Sep 2008 | B2 |
7466105 | Inui et al. | Dec 2008 | B2 |
7671566 | Du | Mar 2010 | B2 |
7688075 | Kelley et al. | Mar 2010 | B2 |
7737659 | Morioka | Jun 2010 | B2 |
7825631 | Chen et al. | Nov 2010 | B2 |
7898263 | Ishida et al. | Mar 2011 | B2 |
8040107 | Ishii | Oct 2011 | B2 |
8045316 | Nerheim | Oct 2011 | B2 |
8204552 | Hong et al. | Jun 2012 | B2 |
8255176 | Plestid | Aug 2012 | B2 |
8473231 | Plestid | Jun 2013 | B2 |
20020012830 | Uemura et al. | Jan 2002 | A1 |
20020060554 | Odaohhara et al. | May 2002 | A1 |
20020101218 | Koenck et al. | Aug 2002 | A1 |
20020109506 | Kawakami et al. | Aug 2002 | A1 |
20020132653 | Okamoto et al. | Sep 2002 | A1 |
20020167293 | Ptasinski et al. | Nov 2002 | A1 |
20030006735 | Kawakami et al. | Jan 2003 | A1 |
20030057918 | Aoki et al. | Mar 2003 | A1 |
20030069704 | Bean | Apr 2003 | A1 |
20030189418 | Schinner | Oct 2003 | A1 |
20030222867 | Bean et al. | Dec 2003 | A1 |
20050001625 | Ashtiani et al. | Jan 2005 | A1 |
20050017686 | Sakakibara et al. | Jan 2005 | A1 |
20050035743 | Kawakami et al. | Feb 2005 | A1 |
20050156570 | Inui et al. | Jul 2005 | A1 |
20050174093 | Chen | Aug 2005 | A1 |
20060049805 | Tran | Mar 2006 | A1 |
20060238168 | Matsuo et al. | Oct 2006 | A1 |
20070075678 | Ng et al. | Apr 2007 | A1 |
20070120554 | Kawakami et al. | May 2007 | A1 |
20070182373 | Sakakibara et al. | Aug 2007 | A1 |
20070188141 | Hamaguchi et al. | Aug 2007 | A1 |
20070188148 | Kawasumi et al. | Aug 2007 | A1 |
20070260975 | Nordenhake | Nov 2007 | A1 |
20070285059 | Zettel et al. | Dec 2007 | A1 |
20080007223 | Morioka | Jan 2008 | A1 |
20080116853 | Du | May 2008 | A1 |
20100156351 | Ugaji et al. | Jun 2010 | A1 |
20110187329 | Majima et al. | Aug 2011 | A1 |
20110238344 | Jin et al. | Sep 2011 | A1 |
20120303302 | Plestid | Nov 2012 | A1 |
Number | Date | Country |
---|---|---|
102005026583 | Dec 2006 | DE |
0628833 | Dec 1994 | EP |
1450173 | Aug 2004 | EP |
1482318 | Dec 2004 | EP |
1500945 | Jan 2005 | EP |
1990859 | Nov 2008 | EP |
2068161 | Jun 2009 | EP |
09115554 | May 1997 | JP |
WO 02097456 | Dec 2002 | WO |
WO 2007048367 | May 2007 | WO |
WO 2007099898 | Sep 2007 | WO |
Entry |
---|
EPO Extended European Search Report for Application No. 12195344.2-1560 dated Jun. 10, 2013 (18 pages). |
Buchmann, Isidor: “How to prolong lithium-based batteries,” Battery University.com http://www.batteryuniversity.com/parttwo-34. htm, created Feb. 2003, last edited Sep. 2006, printed Feb. 8, 2008, 5 pages. |
CIPO: Office Action issued for corresponding Canadian Patent Application No. 2674996 dated Aug. 28, 2012 (5 pages). |
EPO: {Partial European Search Report for Application No. 12195344.2-2216 dated Feb. 4, 2013 (9 pages). |
EPO: Communication Pursuant to Article 94(3) EPC for Application No. 09167470.5-2216 dated Nov. 23, 2010 (6 pages). |
EPO: Extended European Search Report for Application No. 0916740.5-2216 dated Jun. 15, 2010 (16 pages). |
Office Action dated Nov. 8, 2011; U.S. Appl. No. 12/536,659, filed Aug. 6, 2009; 6 pages. |
Office Action dated Dec. 30, 2011; U.S. Appl. No. 12/536,659, filed Aug. 6, 2009; 11 pages. |
Notice of Allowance dated Apr. 25, 2012; U.S. Appl. No. 12/536,659, filed Aug. 6, 2009; 11 pages. |
Office Action dated Nov. 9, 2012; U.S. Appl. No. 13/567,163, filed Aug. 6, 2012; 16 pages. |
Notice of Allowance dated Mar. 5, 2013; U.S. Appl. No. 13/567,163, filed Aug. 6, 2012; 13 pages. |
European Summons to Attend Oral Proceedings; Application No. 09167470.5; May 8, 2012; 8 pages. |
Number | Date | Country | |
---|---|---|---|
20130268223 A1 | Oct 2013 | US |
Number | Date | Country | |
---|---|---|---|
61086985 | Aug 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12536659 | Aug 2009 | US |
Child | 13567163 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13567163 | Aug 2012 | US |
Child | 13892360 | US |