Dynamic Compute Orchestration in Information Centric Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current ICN technologies lack the ability for clients to selectively choose a server for computation based on compute constraints, security, and efficiency, especially in multi-server scenarios, leading to potential security concerns and inefficient resource utilization.

Innovation Solution

The proposed solution involves a client sending a discovery interest packet with relevant details to network nodes, which respond with computation time data, allowing the client to select a suitable server for computation, and enabling seamless result retrieval even if the client moves to a different network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single compute server is used in ICN, then routing simplicity is improved, but resource utilization efficiency and adaptability deteriorate

Engineering Contradiction:
Improverouting complexityVSAvoidresource utilization efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the compute resource into multiple distributed servers instead of using a single centralized server. Each server can independently process compute requests, allowing the system to scale horizontally and improve resource utilization while maintaining routing simplicity through interest packet-based naming.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal compute orchestration mechanism that works across multiple servers with different capabilities. The interest packet framework provides a unified interface for clients to request compute services from any available server, making the system adaptable to various server configurations and improving overall resource utilization.

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

2Device complexity

If clients cannot select compute servers, then system simplicity is improved, but security and efficiency deteriorate

Engineering Contradiction:
Improvesystem complexityVSAvoidsecurity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where clients receive information about available compute servers and their capabilities, then make informed selection decisions. The system provides feedback about server status, performance metrics, and security credentials, enabling clients to select appropriate servers while maintaining system simplicity through automated orchestration.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If clients cannot select compute servers, then ease of operation is improved, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improveclient operation simplicityVSAvoidresource utilization efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent enables clients to self-select compute servers based on their specific requirements and the available options. The interest packet mechanism allows clients to autonomously discover and choose appropriate compute resources without complex manual configuration, improving both ease of operation and resource utilization efficiency through demand-driven resource allocation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11792113B2Information centric network dynamic compute orchestration
Publication Date: 2023.10.17 INTEL CORP
  • US11792113B2 patent drawing
  • US11792113B2 patent drawing
  • US11792113B2 patent drawing

AI summary

Systems and methods for dynamic compute orchestration include receiving, at a network node of an information centric network, a first interest packet comprising a name field indicating a named function and one or more constraints specifying compute requirements for a computing node to execute the named function, the first interest packet received from a client node. A plurality of computing nodes are identified that satisfy the compute requirements for executing the named function. The first interest packet is forwarded to at least some of the plurality of computing nodes. Data packets are received from at least some of the plurality of computing nodes in response to the first interest packet. One of the plurality of computing nodes is selected based on the received data packets, and a second interest packet is sent to the selected one of the plurality of computing nodes instructing the selected one of the plurality of compute nodes to execute the named function.