Serverless Function Deployment Across Edge Nodes by Resource Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Selecting the best device for executing serverless functions in edge computing environments is challenging due to varying device capabilities, leading to potential overloading or underloading and suboptimal system performance.

Innovation Solution

A system that decomposes serverless functions into executable files based on resource requirements and node capabilities, distributing them across multiple nodes for efficient resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If serverless functions are deployed to edge devices with varying capabilities, then system flexibility and responsiveness are improved, but device selection complexity increases leading to potential overloading or underloading

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddevice selection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system employs self-service mechanisms where the deployment platform automatically assesses device capabilities and makes intelligent placement decisions without manual intervention. The platform autonomously matches serverless functions to appropriate edge devices based on real-time capability assessments, resource availability, and workload characteristics, thereby resolving the complexity of device selection while maintaining system flexibility

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically adjusts deployment parameters based on changing device capabilities and workload requirements. It continuously monitors device states and modifies placement decisions in response to parameter changes such as resource availability, network conditions, and function performance metrics, enabling adaptive deployment that avoids both overloading and underloading scenarios

Inventive Principle:
Principle #35Parameter changes

2Productivity

If serverless functions are deployed independently by different developers, then scalability and robustness are improved, but coordination and resource allocation become challenging

Engineering Contradiction:
Improvedevelopment scalabilityVSAvoidresource allocation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements a universal deployment platform that handles multiple functions and services across diverse edge devices through a common interface and resource management layer. This multi-functional approach allows independent developers to deploy their serverless functions without needing to manage underlying resource allocation, as the platform provides unified orchestration and coordination

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The deployment platform acts as an intermediary between independent developers and the edge device infrastructure. It mediates resource allocation by receiving deployment requests from various developers, assessing device capabilities, and automatically assigning functions to appropriate devices, thereby eliminating the need for developers to directly coordinate resource management while maintaining system-wide optimization

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260079720A1Deployment of configuration files generated from serverless functions
Publication Date: 2026.03.19 RED HAT INC
  • US20260079720A1 patent drawing
  • US20260079720A1 patent drawing
  • US20260079720A1 patent drawing

AI summary

Some examples of the present disclosure relate to deploying configuration files generated from serverless functions. In one particular example, a system can receive a serverless function including a set of software elements. The system can determine resource requirements associated with executing the serverless function. The system can also determine a set of capabilities for a plurality of nodes. The system can generate a set of executable files corresponding to the set of software elements and the resource requirements. The system can assign a first executable file to a first configuration file based on the set of capabilities. The first configuration file is associated with a first node of the plurality of nodes. The system can execute the first configuration file having the first executable file using the first node.