DIET: A Dynamic Energy Management Approach for Wearable Health Monitoring Devices
DIET: A Dynamic Energy Management Approach for Wearable Health Monitoring Devices
复制标题
DIET：可穿戴健康监测设备的动态能量管理方法
DOI：
10.23919/date54114.2022.9774553
复制
发表时间：
2022
期刊：
影响因子：
--
通讯作者：
J. Doppa
中科院分区：
文献类型：
--
作者：
Nuzhat Yamin;Ganapati Bhat;J. Doppa
可穿戴设备在健康和活动监测应用中变得越来越流行。这些设备通常包括可充电的小电池，以改善用户舒适性。但是，电池容量较小会导致运营寿命有限，需要频繁地充电。最近的研究提出了使用光和用户运动来提高可穿戴设备的寿命的能量收获。大多数能量收集方法都认为，健康监测所需的能量收集设备和传感器的放置是相同的。但是，此假设不适合多个现实世界应用。例如，使用压电传感器进行运动能量收获仅限于膝盖和肘部，而用于心率监测的传感器必须放在胸部上以获得最佳性能。为了应对这一挑战，我们提出了一种新型的动态能源管理方法，称为饮食，用于由多个传感器和能量收集设备实现的可穿戴健康应用。饮食背后的关键思想是从多个来源收集能量，并使用轻质优化算法将其最佳地分配给每个传感器，以便最大化应用程序的总体实用程序。 30天内，来自四个用户的实际数据实验表明，饮食方法在离线甲骨文的10％以内实现了实用性。
Wearable devices are becoming increasingly popular for health and activity monitoring applications. These devices typically include small rechargeable batteries to improve user comfort. However, the small battery capacity leads to limited operating life, requiring frequent recharging. Recent research has proposed energy harvesting using light and user motion to improve the lifetime of wearable devices. Most energy harvesting approaches assume that the placement of the energy harvesting device and sensors required for health monitoring are the same. However, this assumption does not hold for several real-world applications. For example, motion energy harvesting using piezoelectric sensors is limited to the knees and elbows, while a sensor for heart rate monitoring must be placed on the chest for optimal performance. To address this challenge, we propose a novel dynamic energy management approach referred to as DIET for wearable health applications enabled by multiple sensors and energy harvesting devices. The key idea behind DIET is to harvest energy from multiple sources and optimally allocate it to each sensor using a lightweight optimization algorithm such that the overall utility for applications is maximized. Experiments on real-world data from four users over 30 days show that the DIET approach achieves utility within 10% of an offline Oracle.