Your browser does not support JavaScript!

Which battery model to use?

Which battery model to use?

For access to this article, please select a purchase option:

Buy article PDF
(plus tax if applicable)
Buy Knowledge Pack
10 articles for $120.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Your details
Why are you recommending this title?
Select reason:
IET Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

The use of mobile devices like cell phones, navigation systems or laptop computers is limited by the lifetime of the included batteries. This lifetime depends naturally on the rate at which energy is consumed; however, it also depends on the usage pattern of the battery. Continuous drawing of a high current results in an excessive drop of residual capacity. However, during intervals with no or very small currents, batteries do recover to a certain extent. The usage pattern of a device can be well modelled with stochastic workload models. However, one still needs a battery model to describe the effects of the power consumption on the state of the battery. Over the years many different types of battery models have been developed for different application areas. In this study we give a detailed analysis of two well-known analytical models, the kinetic battery model (KiBaM) and the so-called diffusion model. We show that the KiBaM is actually an approximation of the more complex diffusion model; this was not known previously. Furthermore, we tested the suitability of these models for performance evaluation purposes, and found that both models are well suited for doing battery lifetime predictions. However, one should not draw conclusions on what is the best usage pattern based on only a few workload traces.

Related content

This is a required field
Please enter a valid email address