Embodiments of the present invention relate generally to wireless network communications and, more specifically, to battery control for safeguarding lower voltage integrated circuits.
A conventional wireless mesh network includes a plurality of nodes configured to communicate with one another. In certain types of heterogeneous wireless mesh networks, both continuously-powered nodes and battery-powered nodes communicate and interact with one another within the mesh network. Typically, continuously-powered nodes are coupled to a power grid and have continuous access to power (except during power outages). Battery-powered nodes, on the other hand, have only a finite supply of battery power. To conserve power, battery-powered nodes may deactivate for long periods of time, during which little power is consumed, and then reactivate for short periods of time, during which very brief network communications are performed.
In many cases, battery-powered nodes are deployed in locations where replacing depleted batteries is difficult or impossible. For this reason, battery-powered nodes are preferably equipped with batteries having an extended lifetime. One example of a battery with an extended lifetime is a lithium thionyl chloride (LTC) battery. LTC batteries, however, typically cannot be used to power battery-powered nodes for at least two reasons.
First, LTC batteries usually deliver a voltage level that is higher than the maximum operating voltage of the integrated circuitry within a conventional battery-powered node. Consequently, powering a conventional battery-powered node using an LTC battery may damage or destroy the integrated circuitry. Second, LTC batteries oftentimes cannot deliver a sufficiently high current level quickly enough for the battery-powered node to perform network communications during the short reactivation periods. In fact, LTC batteries can be damaged by large current draws, such as those typically needed during the short reactivation periods.
As the foregoing illustrates, what is needed in the art is a more effective way to power battery-powered nodes using batteries that operate at high voltages.
One embodiment of the present invention sets forth a computer-implemented method for powering a battery-powered node residing within a wireless mesh network, including storing first electrical energy in a storage element, wherein a primary cell transmits the first electrical energy to the storage element at a first voltage level, determining that a second voltage level associated with the storage element exceeds a third voltage level associated with a secondary cell, and storing second electrical energy that is derived from the first electrical energy in the secondary cell, wherein the battery-powered node communicates with one or more other nodes residing within the wireless mesh network using at least a portion of the second electrical energy.
At least one advantage of the techniques described herein is that a higher voltage battery (including an LTC battery) can safely power a battery-powered node that has a lower maximum operating voltage. Accordingly, the battery-powered node may operate for an extended period of time compared to conventional battery-powered nodes powered only by lower voltage batteries.
So that the manner in which the above-recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
In the following description, numerous specific details are set forth to provide a more thorough understanding of the present invention. However, it will be apparent to one of skill in the art that the present invention may be practiced without one or more of these specific details. In other instances, well-known features have not been described in order to avoid obscuring the present invention.
As discussed above, battery-powered nodes included in conventional mesh networks may be deployed in locations where replacing depleted batteries is difficult or impossible. Accordingly, battery-powered nodes are preferably equipped with batteries having an extended lifetime, such as LTC batteries. LTC batteries, however, typically deliver a voltage level that exceeds the maximum voltage level associated with most conventional battery-powered nodes. Further, LTC batteries cannot quickly provide the high current level that is needed when a conventional battery-powered node reactivates to perform network communications.
To address these issues, embodiments of the invention include a battery controller that buffers a higher voltage provided by a primary cell in order to charge a secondary cell. The secondary cell provides a low voltage that can safely power a battery-powered node with limited risk of damage. The secondary cell may also have a low impedance and therefore be capable of providing the elevated current level needed during reactivation of the battery-powered node.
One advantage of the techniques described herein is that a higher voltage battery (including an LTC battery) can safely power a battery-powered node that has a lower maximum operating voltage. Accordingly, the battery-powered node may operate for an extended period of time compared to conventional battery-powered nodes powered only by lower voltage batteries. Extending the operational life of battery-powered nodes that participate in wireless mesh networks is critical to the ongoing operation of those networks. Another advantage of the techniques described herein is that the primary cell is not required to quickly provide an elevated current level when the battery-powered node reactivates because the secondary cell provides this current level. Thus, the battery-powered node can very briefly reactivate to perform network communications, thereby conserving power. For these reasons, the techniques described herein represent a technological advancement over previous approaches.
A discovery protocol may be implemented to determine node adjacency to one or more adjacent nodes. For example, intermediate node 130-2 may execute the discovery protocol to determine that nodes 110, 130-1, 130-3, and 130-5 are adjacent to node 130-2. Furthermore, this node adjacency indicates that communication links 132-2, 134-2, 134-4 and 134-3 may be established between the nodes 110, 130-1, 130-3, and 130-5, respectively. Any technically feasible discovery protocol may be implemented without departing from the scope and spirit of embodiments of the present invention.
The discovery protocol may also be implemented to determine the hopping sequences of adjacent nodes, i.e. the sequence of channels across which nodes periodically receive payload data. As is known in the art, a “channel” may correspond to a particular range of frequencies. Once adjacency is established between the source node 110 and at least one intermediate node 130, the source node 110 may generate payload data for delivery to the destination node 112, assuming a path is available. The payload data may comprise an Internet protocol (IP) packet, or any other technically feasible unit of data. Similarly, any technically feasible addressing and forwarding techniques may be implemented to facilitate delivery of the payload data from the source node 110 to the destination node 112. For example, the payload data may include a header field configured to include a destination address, such as an IP address or media access control (MAC) address.
Each intermediate node 130 may be configured to forward the payload data based on the destination address. Alternatively, the payload data may include a header field configured to include at least one switch label to define a predetermined path from the source node 110 to the destination node 112. A forwarding database may be maintained by each intermediate node 130 that indicates which communication link 132, 134, 136 should be used and in what priority to transmit the payload data for delivery to the destination node 112. The forwarding database may represent multiple routes to the destination address, and each of the multiple routes may include one or more cost values. Any technically feasible type of cost value may characterize a link or a route within the network system 100, although one specific approach is discussed in greater detail below in conjunction with
In network system 100, the access point 150 is configured to communicate with at least one node within the wireless mesh network 102, such as intermediate node 130-4. Communication may include transmission of payload data, timing data, or any other technically relevant data between the access point 150 and the at least one node within the wireless mesh network 102. For example, communications link 140 may be established between the access point 150 and intermediate node 130-4 to facilitate transmission of payload data between wireless mesh network 102 and network 152. The network 152 is coupled to the server 154 via communications link 142. The access point 150 is coupled to the network 152, which may comprise any wired, optical, wireless, or hybrid network configured to transmit payload data between the access point 150 and the server 154.
In one embodiment, the server 154 represents a destination for payload data originating within the wireless mesh network 102 and a source of payload data destined for one or more nodes within the wireless mesh network 102. In one embodiment, the server 154 is a computing device, including a processor and memory, and executes an application for interacting with nodes within the wireless mesh network 102. For example, nodes within the wireless mesh network 102 may perform measurements to generate measurement data, such as power consumption data. The server 154 may execute an application to collect the measurement data and report the measurement data. In one embodiment, the server 154 queries nodes within the wireless mesh network 102 for certain data. Each queried node replies with requested data, such as consumption data, system status and health data, and so forth. In an alternative embodiment, each node within the wireless mesh network 102 autonomously reports certain data, which is collected by the server 154 as the data becomes available via autonomous reporting.
The techniques described herein are sufficiently flexible to be utilized within any technically feasible network environment including, without limitation, a wide-area network (WAN) or a local-area network (LAN). Moreover, multiple network types may exist within a given network system 100. For example, communications between two nodes 130 or between a node 130 and the corresponding access point 150 may be via a radio-frequency local-area network (RF LAN), while communications between access points 150 and the network may be via a WAN such as a general packet radio service (GPRS). As mentioned above, each node within wireless mesh network 102 includes a network interface that enables the node to communicate wirelessly with other nodes. Each node 130 may implement any and all embodiments of the invention by operation of the network interface. An exemplary network interface is described below in conjunction with
A memory 212 may be coupled to the MPU 210 for local program and data storage. Similarly, a memory 216 may be coupled to the DSP 214 for local program and data storage. Memory 212 and/or memory 216 may be used to buffer incoming data as well as store data structures such as, e.g., a forwarding database, and/or routing tables that include primary and secondary path information, path cost values, and so forth.
In one embodiment, the MPU 210 implements procedures for processing IP packets transmitted or received as payload data by the network interface 200. The procedures for processing the IP packets may include, without limitation, wireless routing, encryption, authentication, protocol translation, and routing between and among different wireless and wired network ports. In one embodiment, MPU 210 implements the techniques performed by the node when MPU 210 executes a firmware program stored in memory within network interface 200.
The MPU 214 is coupled to DAC 220 and DAC 221. Each DAC 220, 221 is configured to convert a stream of outbound digital values into a corresponding analog signal. The outbound digital values are computed by the signal processing procedures for modulating one or more channels. The DSP 214 is also coupled to ADC 222 and ADC 223. Each ADC 222, 223 is configured to sample and quantize an analog signal to generate a stream of inbound digital values. The inbound digital values are processed by the signal processing procedures to demodulate and extract payload data from the inbound digital values.
In one embodiment, MPU 210 and/or DSP 214 are configured to buffer incoming data within memory 212 and/or memory 216. The incoming data may be buffered in any technically feasible format, including, for example, raw soft bits from individual channels, demodulated bits, raw ADC samples, and so forth. MPU 210 and/or DSP 214 may buffer within memory 212 and/or memory 216 any portion of data received across the set of channels from which antenna 246 receives data, including all such data. MPU 210 and/or DSP 214 may then perform various operations with the buffered data, including demodulation operations, decoding operations, and so forth.
MPU 210, DSP 214, and potentially other elements included in network interface 200 are powered by power system 250. Power system 250 includes a higher voltage primary cell, such as a Lithium Thionyl Chloride (LTC) battery, and a lower voltage secondary cell, such as a Lithium Ion (Li-ion) battery. Power system 250 also includes a battery controller that buffers charge provided by the primary cell in order to charge the secondary cell. The secondary cell then delivers low voltage power that can safely power MPU 210, DSP 214, and other elements of network interface 200. Power system 250 is described in greater detail below in conjunction with
Persons having ordinary skill in the art will recognize that network interface 200 represents just one possible network interface that may be implemented within wireless mesh network 102 shown in
Battery controller 300 includes switches 302 and 306, current limiters 304 and 308, storage element 310, inverter 312, and comparator 314, coupled together in the manner shown. Current limiters 304 and 308 may protect primary cell 320 and secondary cell 330 from current spikes by preventing inrush current to and from storage element 310. Storage element 310 may be a capacitor. Comparator 314 monitors a voltage level associated with storage element 310. Comparator 314 may have hysteresis and may operate relative to a reference.
In operation, primary cell 320 powers storage element 310 via switch 302, which initially may be closed. Comparator 314 monitors voltage associated with storage element 310. When storage element 310 reaches a voltage level that is higher than a target operating voltage of secondary cell 330, comparator 314 transmits a signal to open switch 302. Inverter 312 inverts that signal and closes switch 306. Configured in this manner, primary cell 320 is isolated from secondary cell 330.
With switch 306 closed, storage element 310 conducts stored charge through switch 306 and into secondary cell 330, thereby charging secondary cell 330. Storage element 310 continues to conduct stored charge in this manner, thereby causing the voltage level associated with storage element 310 to decrease. Comparator 314 continues to monitor this voltage level. When the voltage level of storage element 310 is less than (or equal to) the target operating voltage of secondary cell 330, comparator 314 transmits a signal to close switch 302. Inverter 312 inverts this signal, thereby opening switch 306. Primary cell 320 may then again charge storage element 310.
This process may repeat continuously, and during this process secondary cell 330 provides power to load 340. When the voltage of secondary cell 330 reaches the operating voltage of load 340, comparator 314 keeps switch 302 closed until the voltage of secondary cell 330 falls beneath the target operating voltage of secondary cell 330. Then, comparator 314 opens switch 302, causing inverter 312 to close switch 306 and allow secondary cell 330 to recharge via storage cell 310.
Battery controller 300 described above advantageously allows a higher voltage battery to safely power a load that demands a lower voltage. Because higher voltage batteries may have an extended lifetime compared to other lower batteries, a battery-powered node that implements battery controller 300 may have a longer operational lifetime compared to other devices that can only be powered by lower voltage batteries. In addition, battery controller 300 may mitigate voltage variations in higher voltage batteries that can occur due to temperature fluctuations. In particular, certain types of LTC batteries provide a voltage level that decreases with increasing temperature. The buffering approach implemented by battery controller 300 reduces the effects of these voltage changes. Further, battery controller 300 may be especially advantageous when implemented in wireless mesh networks where battery-powered nodes power on periodically and need an elevated current level over a short time span. Because higher voltage batteries often have high impedance levels, such batteries usually cannot quickly provide an elevated current level. However, battery controller 300 allows a high current level to be provided to load 340 via secondary cell 330 independent of the impedance level of primary cell 320. Finally, battery controller 300 described thus far operates with low quiescent current and can be constructed at low cost. For these reasons, battery controller 300 represents a significant technological improvement.
As shown, a method 400 begins at step 402, where battery controller 300 conducts charge from primary cell 320 into storage element 310 via switch 302, thereby storing electrical energy in storage element 310. At step 404, comparator 314 within battery controller 300 determines whether the voltage of storage element 310 is greater than a threshold. The threshold generally corresponds to the target operating voltage of secondary cell 330. The method 400 returns to step 402 until the voltage of storage element 310 exceeds the threshold.
When the voltage of storage element 310 exceeds the threshold, the method 400 proceeds to step 406. At step 406, comparator 314 opens switch 302 and inverter 312 closes switch 306. At step 408, storage element 310 conducts charge into secondary cell 330 via switch 306, thereby storing electrical energy in secondary cell 330. At step 410, secondary cell 330 conducts electrical energy to load 340. As mentioned, load 340 may include various elements of network interface 200 of
At step 412, comparator 314 within battery controller 300 determines whether the voltage of storage element 310 is less than the threshold. Again, the threshold generally corresponds to the target operating voltage of secondary cell 330. The method 400 returns to step 408 until the voltage of storage element 310 falls beneath the threshold. When the voltage of storage element 310 falls beneath the threshold, the method 400 proceeds to step 414. At step 414, comparator 314 opens switch 306 and inverter 312 closes switch 302. Battery controller 300 repeat the method 400 continuously in order buffer charge between primary cell 320 and secondary cell 330.
In sum, a battery controller buffers a higher voltage provided by a primary cell in order to charge a secondary cell. The secondary cell provides a low voltage that can safely power integrated circuitry within a battery powered node with limited risk of damage. The battery controller includes a storage device that is charged by the primary cell. When the voltage of the storage device reaches a threshold, the battery controller conducts the stored charge into the secondary cell while isolating the secondary cell from the primary cell. The secondary cell, when charged, powers the battery powered node at the low voltage.
One advantage of the techniques described herein is that a higher voltage LTC battery can safely provide power to a node that has a low maximum operating voltage. Accordingly, the node may operate for extended periods of time compared to conventional nodes powered only by lower voltage batteries. Extending the operational life of battery-powered nodes that participate in wireless mesh networks is critical to the ongoing operation of those networks. Another advantage of the techniques described herein is that the primary cell is not required to quickly provide an elevated current level when the node reactivates because the secondary cell provides this current level. Thus, the node can very briefly reactivate to perform network communications, thereby conserving power. For at least these reasons, the techniques described herein represent a technological advancement over previous approaches.
1. A computer-implemented method for powering a battery-powered node residing within a wireless mesh network, the method comprising: storing first electrical energy in a storage element, wherein a primary cell transmits the first electrical energy to the storage element at a first voltage level, determining that a second voltage level associated with the storage element exceeds a third voltage level associated with a secondary cell, and storing second electrical energy that is derived from the first electrical energy in the secondary cell, wherein the battery-powered node communicates with one or more other nodes residing within the wireless mesh network using at least a portion of the second electrical energy.
2. The computer-implemented method of clause 1, wherein storing the first electrical energy comprises causing one or more switches to switch into a first configuration, and wherein, in the first configuration, the primary cell is electrically coupled to the storage element and electrically isolated from the secondary cell.
3. The computer-implemented method of any of clauses 1 and 2, wherein the one or more switches includes a first switch and a second switch, and wherein, in the first configuration, the first switch is closed and the second switch is open.
4. The computer-implemented method of any of clauses 1, 2, and 3, wherein storing the second electrical energy comprises causing one or more switches to switch into a second configuration, and wherein, in the second configuration, the secondary cell is electrically coupled to the storage element and electrically isolated from the primary cell.
5. The computer-implemented method of any of clauses 1, 2, 3, and 4, wherein the one or more switches includes a first switch and a second switch, and wherein, in the second configuration, the first switch is open and the second switch is closed.
6. The computer-implemented method of any of clauses 1, 2, 3, 4, and 5, wherein the first voltage level is greater than a maximum voltage level associated with the battery-powered node, and the second voltage level is less than or equal to the maximum voltage level associated with the battery-powered node.
7. The computer-implemented method of any of clauses 1, 2, 3, 4, 5, and 6, wherein the primary cell comprises a lithium thionyl chloride battery, and the first voltage level is greater than 3.6 volts.
8. The computer-implemented method of any of clauses 1, 2, 3, 4, 5, 6, and 7, wherein the secondary cell comprises a lithium ion battery, and the third voltage level is less than or equal to 3.6 volts.
9. The computer-implemented method of any of clauses 1, 2, 3, 4, 5, 6, 7, and 8, wherein the storage element comprises a capacitor.
10. The computer-implemented method of any of clauses 1, 2, 3, 4, 5, 6, 7, 8, and 9, wherein the node draws the second electrical energy from the secondary cell when performing the wireless communications with a current level that is independent of an impedance level associated with the primary cell.
11. A system for powering a battery-powered node residing within a wireless mesh network, comprising: a storage element that stores first electrical energy, a primary cell that transmits the first electrical energy to the storage element at a first voltage level, a comparator that determines that a second voltage level associated with the storage element exceeds a third voltage level, and a secondary cell that operate at the first voltage level and stores second electrical energy that is derived from the first electrical energy, wherein the battery-powered node communicates with one or more other nodes residing within the wireless mesh network using at least a portion of the second electrical energy.
12. The system of clause 11, wherein the storage element stores the first electrical energy when the comparator causes one or more switches to switch into a first configuration, and wherein, in the first configuration, the primary cell is electrically coupled to the storage element and electrically isolated from the secondary cell.
13. The system of any of clauses 11 and 12, wherein the one or more switches includes a first switch and a second switch, and wherein, in the first configuration, the first switch is closed and the second switch is open.
14. The system of any of clauses 11, 12, and 13, wherein the secondary cell stores the second electrical energy when the comparator causes one or more switches to switch into a second configuration, and wherein, in the second configuration, the secondary cell is electrically coupled to the storage element and electrically isolated from the primary cell.
15. The system of any of clauses 11, 12, 13, and 14, wherein the one or more switches includes a first switch and a second switch, and wherein, in the second configuration, the first switch is open and the second switch is closed.
16. The system of any of clauses 11, 12, 13, 14, and 15, wherein the first voltage level is greater than a maximum voltage level associated with the battery-powered node, and the second voltage level is less than or equal to the maximum voltage level associated with the battery-powered node.
17. The system of any of clauses 11, 12, 13, 14, 15, and 16, wherein the primary cell comprises a lithium thionyl chloride battery and the first voltage level is greater than 3.6 volts, and wherein the secondary cell comprises a lithium ion battery and the third voltage level is less than or equal to 3.6 volts.
18. The system of any of clauses 11, 12, 13, 14, 15, 16, and 17, wherein the battery powered node deactivates during a first recurring time period and reactivates during a second recurring time period to communicate with the one or more other nodes.
19. The system of any of clauses 11, 12, 13, 14, 15, 16, 17, and 18, wherein the first time period exceeds the second time period.
20. The system of any of clauses 11, 12, 13, 14, 15, 16, 17, 18, and 19, wherein the battery-powered node draws the second electrical energy from the secondary cell when communicating with the one or more other nodes at a current level that is independent of an impedance level associated with the primary cell.
Any and all combinations of any of the claim elements recited in any of the claims and/or any elements described in this application, in any fashion, fall within the contemplated scope of the present invention and protection
The descriptions of the various embodiments have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments.
Aspects of the present embodiments may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “module” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such processors may be, without limitation, general purpose processors, special-purpose processors, application-specific processors, or field-programmable processors.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
While the preceding is directed to embodiments of the present disclosure, other and further embodiments of the disclosure may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
This application claims the benefit of United States provisional patent application titled, “Battery Voltage Management,” filed on Feb. 6, 2017 and having Ser. No. 62/455,134. The subject matter of this related application is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3594627 | Lesher | Jul 1971 | A |
3683256 | Mas | Aug 1972 | A |
3787704 | Dennewitz | Jan 1974 | A |
3963976 | Clark | Jun 1976 | A |
4039898 | Iwata | Aug 1977 | A |
4187536 | Govaert | Feb 1980 | A |
4477764 | Pollard | Oct 1984 | A |
4672293 | Crampton | Jun 1987 | A |
5383907 | Kroll | Jan 1995 | A |
5407444 | Kroll | Apr 1995 | A |
5440179 | Severinsky | Aug 1995 | A |
5447522 | Chang | Sep 1995 | A |
5488283 | Dougherty | Jan 1996 | A |
5592067 | Peter | Jan 1997 | A |
5620464 | Kroll | Apr 1997 | A |
6064176 | Odaka | May 2000 | A |
6153947 | Rockow | Nov 2000 | A |
6271642 | Dougherty | Aug 2001 | B1 |
6310789 | Nebrigic | Oct 2001 | B1 |
6320351 | Ng | Nov 2001 | B1 |
6713894 | Reimer | Mar 2004 | B1 |
6737830 | Bean | May 2004 | B2 |
6777916 | Yang | Aug 2004 | B2 |
6864664 | Clift | Mar 2005 | B2 |
6873133 | Kavounas | Mar 2005 | B1 |
6909915 | Greatbatch | Jun 2005 | B2 |
7020519 | Greatbatch | Mar 2006 | B2 |
7030591 | Stellberger | Apr 2006 | B2 |
7079893 | Greatbatch | Jul 2006 | B2 |
7109684 | Takaoka | Sep 2006 | B2 |
7136701 | Greatbatch | Nov 2006 | B2 |
7193390 | Nagai | Mar 2007 | B2 |
7199488 | Baker | Apr 2007 | B1 |
7200357 | Janik | Apr 2007 | B2 |
7277417 | Palm | Oct 2007 | B2 |
7298113 | Orikasa | Nov 2007 | B2 |
7550943 | Spartano | Jun 2009 | B2 |
7573154 | Tsui | Aug 2009 | B2 |
7660601 | Janik | Feb 2010 | B2 |
7977923 | Pelrine | Jul 2011 | B2 |
7994756 | Rowland | Aug 2011 | B2 |
8004237 | Manor | Aug 2011 | B2 |
8228645 | English | Jul 2012 | B2 |
8243701 | Palm | Aug 2012 | B2 |
8259221 | Kaplan | Sep 2012 | B1 |
8525520 | Edwards | Sep 2013 | B2 |
8553666 | Palm | Oct 2013 | B2 |
8749213 | Chen | Jun 2014 | B2 |
8803683 | Schnitz | Aug 2014 | B2 |
8970388 | Track | Mar 2015 | B2 |
9025582 | Palm | May 2015 | B2 |
9048669 | Lim | Jun 2015 | B2 |
9217765 | Lazar, II | Dec 2015 | B2 |
9244474 | Smith | Jan 2016 | B2 |
9380531 | Subramanian | Jun 2016 | B1 |
9490653 | Shevde | Nov 2016 | B2 |
9529076 | Subramanian | Dec 2016 | B2 |
9612602 | Smith | Apr 2017 | B2 |
9692260 | Walsh | Jun 2017 | B2 |
9694192 | Vansickle | Jul 2017 | B2 |
9706489 | Subramanian | Jul 2017 | B2 |
9710001 | Smith | Jul 2017 | B2 |
9731610 | Reichow | Aug 2017 | B2 |
9809126 | Nakazawa | Nov 2017 | B2 |
9955456 | Hui | Apr 2018 | B2 |
9958885 | Smith | May 2018 | B2 |
9964973 | Smith | May 2018 | B2 |
10028220 | Subramanian | Jul 2018 | B2 |
10075007 | Langlinais | Sep 2018 | B2 |
10236554 | Ackley | Mar 2019 | B2 |
10320290 | Peker | Jun 2019 | B2 |
10382080 | Turnbull | Aug 2019 | B2 |
10476382 | Wu | Nov 2019 | B2 |
10485537 | Yates | Nov 2019 | B2 |
10541541 | Zhang | Jan 2020 | B2 |
10554057 | Wang | Feb 2020 | B1 |
10608962 | Edwards | Mar 2020 | B2 |
20010028571 | Hanada | Oct 2001 | A1 |
20030001544 | Nakanishi | Jan 2003 | A1 |
20030099121 | Yang | May 2003 | A1 |
20040004462 | Bean | Jan 2004 | A1 |
20040147971 | Greatbatch | Jul 2004 | A1 |
20040147972 | Greatbatch | Jul 2004 | A1 |
20040158296 | Greatbatch | Aug 2004 | A1 |
20040218620 | Palm | Nov 2004 | A1 |
20040225333 | Greatbatch | Nov 2004 | A1 |
20040257039 | Clift | Dec 2004 | A1 |
20040257043 | Takaoka | Dec 2004 | A1 |
20050017688 | Stellberger | Jan 2005 | A1 |
20050052154 | Kavounas | Mar 2005 | A1 |
20050088138 | Sasaki | Apr 2005 | A1 |
20050127871 | Orikasa | Jun 2005 | A1 |
20050151518 | Schneiker | Jul 2005 | A1 |
20050250449 | Janik | Nov 2005 | A1 |
20080019344 | Palm | Jan 2008 | A1 |
20080079393 | Spartano | Apr 2008 | A1 |
20080111517 | Pfeifer | May 2008 | A1 |
20080197801 | Manor | Aug 2008 | A1 |
20080278221 | Rowland | Nov 2008 | A1 |
20100060231 | Trainor | Mar 2010 | A1 |
20100114235 | Jiang | May 2010 | A1 |
20100127658 | Fazakas | May 2010 | A1 |
20100226049 | English | Sep 2010 | A1 |
20100308654 | Chen | Dec 2010 | A1 |
20110298414 | Manor | Dec 2011 | A1 |
20120086390 | Lim | Apr 2012 | A1 |
20120269107 | Palm | Oct 2012 | A1 |
20120297104 | Thottuvelil | Nov 2012 | A1 |
20130181829 | Schnitz | Jul 2013 | A1 |
20130286914 | Palm | Oct 2013 | A1 |
20130297082 | Ensworth | Nov 2013 | A1 |
20130320767 | Huang | Dec 2013 | A1 |
20140046534 | Lazar, II | Feb 2014 | A1 |
20140103734 | Walsh | Apr 2014 | A1 |
20140232190 | Chen | Aug 2014 | A1 |
20140252866 | Walsh | Sep 2014 | A1 |
20140268945 | Low | Sep 2014 | A1 |
20140347194 | Schnitz | Nov 2014 | A1 |
20140368160 | Reichow | Dec 2014 | A1 |
20150008867 | Smychkovich | Jan 2015 | A1 |
20150021993 | Smith | Jan 2015 | A1 |
20150021997 | Smith | Jan 2015 | A1 |
20150022026 | Smith | Jan 2015 | A1 |
20150022349 | Smith | Jan 2015 | A1 |
20150022368 | Smith | Jan 2015 | A1 |
20160043762 | Turnbull | Feb 2016 | A1 |
20160104374 | Ypma | Apr 2016 | A1 |
20160111907 | Lynds | Apr 2016 | A1 |
20160150501 | Hui | May 2016 | A1 |
20160216362 | Subramanian | Jul 2016 | A1 |
20160219505 | Subramanian | Jul 2016 | A1 |
20160219516 | Subramanian | Jul 2016 | A1 |
20170257023 | Wu | Sep 2017 | A1 |
20170279275 | Yamamoto | Sep 2017 | A1 |
20180226697 | Edwards | Aug 2018 | A1 |
20180324696 | Subramanian | Nov 2018 | A1 |
20190214845 | Hausman, Jr. | Jul 2019 | A1 |
20200120513 | Cahill-O'Brien | Apr 2020 | A1 |
20200120575 | Cahill-O'Brien | Apr 2020 | A1 |
Entry |
---|
“Internal resistance of D Cell Alkaline versus vs AA—NiMH ?”, lineijbaldj, CandlePowerForums, Published online Aug. 17, 2007 to Sep. 4, 2007, Seen Online Feb. 23, 2021, https://www.candlepowerforums.com/vb/showthread.php?172428-Internal-resistance-of-D-Cell-Alkaline-versus-vs-AA-NiMH (Year: 2007). |
“Nickel Metal Hydride (NiMH): Handbook and Application Manual”, Energizer Brands LLC, pp. 2 & 6, Published 2018, Seen online Feb. 23, 2021 data.energizer.com/pdfs/nickelmetalhydride_appman.pdf (Year: 2018). |
“Alkaline Manganese Dioxide: Handbook and Application Manual”, Energizer Brands, pp. 6-10 esp.8, published 2018, seen online Feb. 23, 2021 data.energizer.com/pdfs/alkaline_appman.pdf (Year: 2018). |
Number | Date | Country | |
---|---|---|---|
20180227849 A1 | Aug 2018 | US |
Number | Date | Country | |
---|---|---|---|
62455134 | Feb 2017 | US |