Lease-Based Orchestration for Edge Serverless Resource Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Edge computing faces challenges in efficient resource orchestration and management, particularly in stateful serverless clusters, due to limited resource elasticity, infrastructure capacity constraints, and high latency requirements, especially in multi-tenancy and dynamic mobility scenarios.

Innovation Solution

A lease-based orchestration platform that uses smart contracts for formalized resource leasing, enabling transparent fine-grained usage metering and rapid scaling through scheduler bridging between borrower and lender domains, with auction-based mechanisms for resource procurement and local assignment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If resources are allocated statically in edge computing clusters, then infrastructure capacity constraints are respected, but resource utilization efficiency deteriorates due to limited resource elasticity

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidresource elasticity
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic resource allocation through lease-based orchestration where resource leases are granted for specific time periods and can be renewed or revoked based on demand. The system transitions from static allocation to dynamic allocation by introducing time-bound leases and auction mechanisms that allow resources to be reallocated efficiently as workloads change, directly resolving the contradiction between utilization efficiency and adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the allocation parameter from permanent/static to temporary/time-bound through the introduction of lease durations. Resources are allocated with specific lease terms that can be adjusted based on demand, allowing the system to optimize utilization during high-demand periods while maintaining control during low-demand periods, thus improving both efficiency and elasticity.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If centralized orchestration is used for resource management, then coordination is simplified, but latency increases due to communication overhead with central controllers

Engineering Contradiction:
Improveorchestration coordination complexityVSAvoidorchestration latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent introduces a hierarchical orchestration model where local edge cluster controllers manage resources within their own clusters autonomously, making decisions locally without constant communication with a central controller. This local autonomy reduces communication latency while maintaining coordination through standardized lease interfaces, resolving the contradiction between simplified coordination and reduced latency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The centralized orchestration system is segmented into multiple independent edge cluster controllers that each manage their own resources. This segmentation distributes the orchestration burden, reducing the communication overhead to a single central controller and thereby reducing latency while maintaining coordination through the standardized lease-based interface.

Inventive Principle:
Principle #1Segmentation

3Reliability

If resources are over-provisioned to handle peak demand, then service latency requirements are met, but infrastructure cost increases

Engineering Contradiction:
Improveservice latency guaranteeVSAvoidinfrastructure resource quantity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system ensures continuous useful action by maintaining a pool of pre-provisioned resources that can be quickly allocated through the auction mechanism when demand arises. Rather than keeping all resources idle or risking service degradation, the continuous availability of resources through leases ensures latency requirements are met while allowing efficient utilization during non-peak periods.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

Resources are pre-provisioned and made available through lease arrangements before demand occurs. The auction mechanism allows resources to be allocated in advance or quickly when needed, ensuring that latency requirements are met without permanently over-provisioning. The preliminary setup of resource pools with lease capabilities enables rapid response to demand spikes.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If fine-grained resource allocation is implemented, then resource utilization efficiency improves, but measurement and monitoring complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidusage metering complexity
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements feedback mechanisms through the lease-based orchestration system that automatically track resource usage, billing, and allocation. The system provides continuous feedback on resource consumption to both the orchestration platform and users, enabling fine-grained allocation while simplifying measurement through automated tracking and reporting built into the lease management infrastructure.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20230119552A1Resource management mechanisms for stateful serverless clusters in edge computing
Publication Date: 2023.04.20 INTEL CORP
  • US20230119552A1 patent drawing
  • US20230119552A1 patent drawing
  • US20230119552A1 patent drawing

AI summary

Systems and methods for managing distributed compute resources are described herein. A system is configured to receive, from an agent operating at a first compute domain of a plurality of compute domains, a request for compute resources; broadcast the request for compute resources to respective agents at the plurality of compute domains; receive a plurality of offers for available compute resources from at least a portion of the plurality of compute domains; transmit, to a selected agent at a selected compute domain of the plurality of compute domains, a commit message to reserve compute resources of the selected compute domain associated with a selected offer of the plurality of offers; and transmit an indication of the commit message to the agent at the first compute domain, wherein the first compute domain is to use the compute resources reserved at the selected compute domain for workloads of the first compute domain.