Edge Orchestration Mesh for Dynamic Service Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of edge computing environments, particularly in mobile network settings, faces challenges in orchestration, functional coordination, and resource management due to the involvement of multiple participants with different operators, policies, and structures, leading to difficulties in coordinating activities across complex mobility scenarios and heterogeneous computing infrastructures.

Innovation Solution

The implementation of an orchestrator apparatus and method that forms an orchestration mesh, allowing dynamic organization and transfer of orchestration functions across multiple edge computing nodes, enabling coordinated management and execution of services across a multi-edge architecture while maintaining security and trust.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple edge computing nodes with different operators and policies are integrated into a unified orchestration system, then service delivery efficiency and resource utilization are improved, but system complexity and coordination difficulty increase

Engineering Contradiction:
Improveservice delivery efficiencyVSAvoidorchestration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the orchestration system into multiple independent orchestrator nodes that can operate autonomously within their own management domains. Each orchestrator handles local service deployment and coordination, while a mesh connectivity layer enables selective inter-orchestrator communication. This segmentation reduces overall system complexity by distributing orchestration responsibilities rather than requiring a centralized complex control structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a mesh dimension to the traditional hierarchical orchestration architecture. Instead of only vertical hierarchy (cloud-to-edge), the mesh layer adds horizontal connectivity between orchestrators at the same level. This dimensional addition enables parallel coordination paths and reduces bottlenecks, improving service delivery efficiency without proportionally increasing complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If orchestration functions are dynamically transferred across multiple edge nodes, then service execution reliability and trust are improved, but coordination overhead and communication latency increase

Engineering Contradiction:
Improveservice execution reliabilityVSAvoidcoordination overhead time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing trust relationships and security credentials between orchestrators during system initialization. Trust anchors and cryptographic credentials are configured in advance, enabling secure orchestration function transfers without real-time trust negotiation. This preliminary setup reduces coordination overhead time during actual service execution while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mesh connectivity layer acts as an intermediary that facilitates efficient communication and coordination between orchestrators. The intermediary manages message routing, authentication, and state synchronization, reducing direct coordination overhead between distant orchestrators. This intermediary layer improves reliability by providing controlled access and verification while minimizing communication latency through optimized routing.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If a mesh architecture is implemented to enable dynamic orchestration transfer, then adaptability and service flexibility are improved, but system configuration and maintenance difficulty increase

Engineering Contradiction:
Improveorchestration flexibilityVSAvoidsystem configuration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where orchestrators automatically discover available services and resources across the mesh, dynamically register themselves, and adapt to topology changes without manual intervention. The system performs self-configuration, health checking, and failover automatically. This self-service capability provides high adaptability while maintaining ease of operation by eliminating complex manual configuration requirements.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The mesh architecture employs dynamic service discovery and orchestration function transfer mechanisms. Orchestrators can dynamically assume or relinquish orchestration responsibilities based on service requirements, resource availability, and operational conditions. This dynamic behavior enhances adaptability while the automated nature of these changes maintains operational simplicity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3985511B1Orchestration of meshes
Publication Date: 2026.03.18 INTEL CORP
  • EP3985511B1 patent drawingFigure 1
  • EP3985511B1 patent drawingFigure 2
  • EP3985511B1 patent drawingFigure 3

AI summary

Methods, apparatus, systems, and articles of manufacture to orchestrate execution of services in a mesh of orchestrators of an edge cloud computing environment are disclosed. An example orchestrator apparatus includes an interface to receive a service to be executed and to monitor execution of the service. The example apparatus includes an orchestration delegate to select resources and orchestrate deployment of the service to execute using the selected resources. The example apparatus includes a delegated orchestration manager to manage the orchestration delegate based on information from the interface and the orchestration delegate regarding execution of the service.