Fog Network Code Offloading via Container Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Resource-constrained IoT devices in fog networks face challenges with computation-intensive applications due to limited computing power and energy resources, requiring efficient methods to offload software code for real-time response.

Innovation Solution

The use of container technology for code offloading between fog nodes, where annotated and rewritten code is executed in a proximal container node, utilizing stub and skeleton communication mechanisms, and a token-based binding scheme to manage resource utilization and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Power

If code offloading is implemented to reduce computation burden on resource-constrained devices, then computing capability is improved, but system complexity increases due to container technology and communication mechanisms

Engineering Contradiction:
Improvecomputing capabilityVSAvoidsystem complexity
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The system segments code execution by separating computation-intensive tasks from resource-constrained devices and placing them in container nodes. The code is divided into executable units that can be independently offloaded and executed in containers, enabling distributed computation while managing complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Container nodes serve as intermediary elements between client devices and the execution environment. These intermediaries manage the complexity of code compilation, execution, and communication through standardized stub-skeleton mechanisms, shielding client devices from the complexity of the offloading infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If code is offloaded to proximal nodes for execution, then latency is reduced, but resource utilization must be carefully managed to avoid node overload

Engineering Contradiction:
ImprovelatencyVSAvoidresource utilization
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system dynamically assigns code to container nodes based on real-time resource availability and latency requirements. The dynamic nature of the fog network allows flexible allocation that adapts to changing conditions, ensuring low latency while preventing node overload through continuous resource monitoring and adaptive scheduling.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes execution parameters by selecting different container nodes based on resource state and latency constraints. When resources are abundant, more aggressive offloading occurs; when constrained, the system adjusts execution parameters to balance performance and resource utilization, preventing node overload while maintaining low latency.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If computation-intensive tasks are executed on resource-constrained IoT devices, then device autonomy is maintained, but energy consumption increases

Engineering Contradiction:
Improvedevice autonomyVSAvoidenergy consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The system extracts computation-intensive operations from resource-constrained devices and places them in dedicated container nodes. By taking out heavy computational tasks, the patent enables device autonomy for simpler operations while offloading energy-intensive processing to nodes with adequate resources, thereby reducing energy consumption on IoT devices.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements self-service through automated code selection and execution decisions. The framework autonomously determines which code to offload and to which node, eliminating the need for manual intervention while optimizing energy consumption. Device autonomy is maintained for high-level control decisions while low-level execution is automated.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10693973B2System and method for work distribution in a fog network via code offloading
Publication Date: 2020.06.23 WISTRON CORP
  • US10693973B2 patent drawing
  • US10693973B2 patent drawing
  • US10693973B2 patent drawing

AI summary

A fog network includes a first fog network node configured to execute an application program, and a second fog network node configured to host a container. The first fog network node is configured to determine a need to offload at least a portion of the application program for execution in the second fog network node, access a registry to identify and locate a container image created from executable code of the application program stored in the fog network, and load the identified container image in the second fog network node. The second fog network node is configured to start the container in response to the container image being loaded, execute the executable code of the application program, and return a result from executing the executable code of the application program to the first fog network node.