← Latest papers
🤖 AI

Adaptive DNN Partitioning and Offloading in Heterogeneous Edge-Cloud Continuum

This paper proposes and validates a framework for adaptive DNN partitioning and offloading across a heterogeneous edge-cloud continuum that dynamically adjusts to runtime conditions, demonstrating significant reductions in energy consumption and latency compared to static baselines on a physical testbed.

Original authors: Akuen Akoi Deng, Eimantas Butkus, Alfreds Lapkovskis, Praveen Kumar Donta

Published 2026-05-12
📖 4 min read☕ Coffee break read

Original authors: Akuen Akoi Deng, Eimantas Butkus, Alfreds Lapkovskis, Praveen Kumar Donta

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have a very smart but tired robot (your IoT device, like a smart camera or a drone) that needs to solve a complex puzzle. This puzzle is a Deep Neural Network (DNN), which is essentially a massive, multi-step recipe for making decisions, like recognizing a face or identifying a car.

In the past, this robot had two bad options:

  1. Do it all itself: It tries to solve the whole puzzle alone. It gets exhausted (uses too much battery) and takes a long time.
  2. Send it all to the cloud: It emails the whole puzzle to a super-fast computer in a distant data center. This is fast for the computer, but the robot spends a lot of time waiting for the email to arrive and leave, and the internet connection might be slow or spotty.

The Problem: The "Static" Plan

Most current solutions use a static plan. It's like a chef who decides, "I will chop the vegetables here, cook the sauce in the middle kitchen, and plate the dish in the final kitchen," and then never changes that plan, even if the internet slows down, the middle kitchen gets busy, or the robot's battery is running low. This rigid approach often leads to wasted energy or slow results.

The Solution: The "Adaptive" Chef

The authors of this paper built a smart, adaptive framework. Think of it as a dynamic project manager that constantly watches the team and changes the plan in real-time.

Here is how their system works, using a three-kitchen restaurant analogy:

  1. The Three Kitchens (The Continuum):

    • The Edge (Raspberry Pi): A tiny, battery-powered food truck. It's close to the customer but has a small stove and limited fuel.
    • The Fog (Laptop): A mid-sized local kitchen. It has a better stove but isn't as powerful as the big one.
    • The Cloud (Desktop PC): A massive, industrial factory with a super-fast oven and unlimited power, but it's far away.
  2. The Dynamic Splitting:
    Instead of a fixed recipe, this system breaks the puzzle (the neural network) into layers. It asks: "Should the food truck chop the onions, or should it send them to the local kitchen?"

    • It profiles the puzzle first to know how big each step is.
    • It measures the roads (network links) between the kitchens to see if traffic is heavy.
    • It calculates the cost of fuel (energy) and time (latency) for every possible way to split the work.
  3. The Constant Re-evaluation:
    This is the magic part. The system doesn't just pick a plan once. Every few minutes, it checks:

    • "Is the road to the factory getting clogged?"
    • "Is the food truck running low on battery?"
    • "Is the local kitchen getting too hot?"
      If conditions change, it instantly reassigns the work. Maybe today the food truck does the chopping, but tomorrow, because the road is clear, it sends the chopping to the factory to save the truck's battery.

The Real-World Test

The authors didn't just simulate this on a computer; they built a physical testbed (a real-life lab):

  • Edge: A Raspberry Pi (the food truck).
  • Fog: A Laptop (the local kitchen).
  • Cloud: A powerful PC with a high-end graphics card (the industrial factory).

They tested this with three famous "puzzles" (AI models): VGG16 (a very complex one), AlexNet (medium complexity), and MobileNetV2 (a lightweight one designed for small devices).

The Results: Saving Fuel and Time

When they compared their "Adaptive" manager against the old "Static" plan, the results were impressive:

  • Energy Savings: The adaptive system saved 27% to 36% more energy. It was like the food truck running on a single tank of gas for much longer because it only did the heavy lifting when it was absolutely necessary and the roads were clear.
  • Speed Improvements: It also made the process 6% to 23% faster. By avoiding traffic jams and sending work to the right kitchen at the right time, the final dish was served sooner.

The Bottom Line

The paper proves that being flexible is better than being rigid. By constantly watching the environment and shifting the workload between the small device, the local computer, and the big cloud, you can save a massive amount of battery life and get answers faster. This is a big deal for the future of smart devices that need to run on batteries while making quick, smart decisions.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →