Abstract

With the development of energy-harvesting technology, various applications have been developed that can be operated only with harvested energy, thereby making energy-harvesting technology suitable for edge devices in poor environments where battery replacement is difficult. However, devices with energy-harvesting technology have limitations: an application can operate intermittently in an energy-harvesting device, and the device’s energy is greatly affected by the environment and the state of the device. Intermittent computing causes abnormal progress or affords incorrect results. The factors affecting the energy of the device can change the operation of the device. To solve these problems, we propose the “Intermittent Computing Environment based on a run-time module” (ICEr), which dynamically controls and manages an application for normal operation in intermittent computing. ICEr comprises an energy checker and a controller. The energy checker measures the energy state of a device at run-time, and the controller controls and manages an application through Backup, Restore, Sleep, and Wakeup. The controller optimizes those operations by considering the energy state and memory state together to minimize time and energy overhead. In this study, two kinds of experiments were conducted. In the first experiment, Embench was selected as the target application to validate ICEr and measure its performance. This experiment validated that ICEr behaves dynamically in various environments. Moreover, it showed a reduction in relative execution time overhead of up to 50% and a reduction in energy overhead of up to 49.5% against Hibernus, depending on the environment. In the second experiment, ICEr was applied to the Temperature Measurement Application, and the improvement of the energy efficiency for the real Internet-of-Things (IoT) application was confirmed.

Highlights

  • Energy-harvesting technology is advancing [1,2]. These advances enable the development of various applications that operate only with harvested energy [3,4,5]; energy-harvesting technology is suitable for devices in environments where battery replacement is difficult

  • In E1 and E4, wherein power failure did not occur, ICEr’s relative execution time overhead was about 0.03, which is 0.03 shorter than that of Hibernus. This is a reduction of about 50% in the relative execution time overhead, which is the largest reduction in the intermittent computing environments

  • We proposed ICEr, a low-power intermittent computing environment that dynamically controls and manages an application

Read more

Summary

Introduction

Energy-harvesting technology is advancing [1,2]. These advances enable the development of various applications that operate only with harvested energy [3,4,5]; energy-harvesting technology is suitable for devices in environments where battery replacement is difficult. While designing an application using the programming tools, developers consider the operational environment of the energy-harvesting device. The JIT model measures the energy state of an energy-harvesting device and executes an application based on the energy state. Numerous checkpoints need to be inserted in it to ensure forward progress because the model does not know the environments in which an application will run. Since ICEr is based on the JIT model, it dynamically controls and manages an application in intermittent computing. When ICEr is operational, the controller dynamically controls and manages an application by considering the energy state, and the memory state, which is the most important state of the device. ICEr executes the application normally in intermittent computing and that it can increase energy efficiency in a real IoT environment.

Energy Harvesting and Intermittent Computing
Non-Volatile Random Access Memory
Programming Model
Compiler-Based Model
JIT Model
Our Proposed Approach
System Structure
Energy Checker
Controller
State Diagram of ICEr
Forward Progress and Data Consistency
Energy Efficiency
Programmability and Portability
Experimental Results and Discussion
Experimental Environment
Benchmarks
Execution Time
Number of ICEr Operations
Energy Consumption
Memory Usage
Application
Conclusions
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.