As everyone who carries a mobile phone has no doubt already learned the hard way, even the most sophisticated devices can be hobbled by a lack of power. And those power issues are especially problematic when it comes to the Internet of Things (IoT), where many IoT devices exist in hard-to-reach locations with little access to external power sources.
Whether implanted in a cardiac patient’s heart or a climate-monitoring installation in a remote rain forest, many IoT devices must rely on internal batteries for a long, long time.
That means IoT devices need two things:
- High-capacity batteries that hold sufficient power to run the device in a small space, and with a long shelf life so they don’t lose that power over time
- Power-efficiency improvements so they consume less of that precious battery juice
IoT batteries getting a lot of attention
To a large extent, the IoT’s ability to work in difficult-to-reach locations will depend on how well those two requirements are met in the coming years. Fortunately, this issue is finally getting the attention it deserves, with researchers around the world working hard to address both sides of the problem. In fact, according to IoT For All, software and hardware engineers, designers, CTOs and product managers are beginning to take an interdisciplinary approach: asking, “Why is it that batteries still suck despite our dependence on them?”
The idea is that approaching the issue across the full technology stack, from prototyping through deployment, will help answer what turns out to be a very complicated question, incorporating the environment and the application as well as the battery itself. For example, even determining battery life — much less extending it — can be surprisingly complex: Individual IoT devices often have multiple functions, each with wildly different power-consumption rates. Think “sleep mode” vs. “active mode.”
Imagining the perfect IoT battery
Given these issues, here are my 10 things IoT battery technologies must do:
- Pack a lot of power into a small space
- Efficiently deliver that power quickly, and/or incrementally, as needed for a particular application, without degrading battery capacity
- Be easily recharged in a variety of ways, including wirelessly, such as over Wi-Fi networks
- Make it simple to remotely monitor battery output, remaining battery life, as well as overall battery health
- Avoid self-discharge to hold their charge for extend time periods, even under adverse environmental conditions
- Be able to be recharged many times, in a variety of ways, without affecting battery capacity
- Avoid emitting waste heat that could cause problems
- Last a long time to avoid the need for premature disposal, and be environmentally friendly when finally retired
- Be inexpensive enough to allow for widespread deployment in many kinds of IoT devices
- Use a flexible design that makes it easy for IoT device makers to incorporate in a wide variety of products
Obviously, creating real-world battery products that satisfy this entire wish list won’t be easy. And not every IoT device or application will need to leverage all 10 factors.
IoT device makers also have work to do
The flip side of this process is that IoT device builders need to do everything they can to ensure their products use the least amount of battery power possible, and even be able to take advantage of alternative power sources when available. That means thinking about optimizing power consumption from the very beginning of the design process, not at the end when everything else has already been worked out.
In addition, it’s critical to “think about the [power requirements of the] entire system, not just the main processing elements.” (The Holy Grail? IoT devices with power requirements so low they don’t need batteries at all!)
That kind of thinking will be critical to powering the IoT, whether it comes from traditional chemical batteries (lithium-ion, alkaline, nickel-cadmium, lead acid, zinc-air, and many others), capacitors, kinetic-or-ambient energy harvesting, or other exotic power technologies.
Thanks to Fredric Paul (see source)