Intent-Driven E2E Orchestration With Reactive SLA Correction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current orchestration solutions for edge computing and IoT networks face challenges such as vendor-lock, incorrect resource provisioning, and sub-optimal performance due to lack of contextual information, especially in heterogeneous hardware environments, leading to overprovisioning and increased costs.

Innovation Solution

Implementing a reactive intent-driven end-to-end orchestration system that maps service level objectives across systems and resources using a meta-language to express key performance indicators and allow for auto-corrective actions, enabling nested and graduated Service Level Agreements (SLAs) to adapt to bursts and optimize resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional orchestration solutions are used in edge computing and IoT networks, then service deployment is simplified, but vendor-lock occurs and resource provisioning becomes incorrect leading to overprovisioning and increased costs

Engineering Contradiction:

Improveservice deploymentVSAvoidvendor independence

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary layer (orchestration system with meta-language) between service deployment and hardware resources. This intermediary translates high-level service requirements into hardware-specific configurations without exposing vendor details to users, thereby achieving vendor independence while maintaining ease of service deployment.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The orchestration system implements a universal meta-language that can describe service requirements independently of specific hardware vendors. This universal interface allows the same service description to be deployed across heterogeneous hardware platforms from different vendors, eliminating vendor-lock while simplifying service deployment.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If traditional orchestration solutions are used, then service deployment is simplified, but resource provisioning becomes incorrect leading to sub-optimal performance

Engineering Contradiction:

Improveservice deploymentVSAvoidresource utilization efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The orchestration system implements feedback mechanisms that continuously monitor resource utilization and service performance. Based on this feedback, the system automatically adjusts resource provisioning to match actual service requirements, preventing both overprovisioning and underprovisioning while maintaining simplified service deployment.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system transitions from static resource provisioning to dynamic resource allocation. Service requirements and resource provisioning are continuously adapted based on changing conditions, allowing the system to optimize resource utilization efficiency while maintaining ease of service deployment through automated adjustments.

Inventive Principle:

Principle #15Dynamics

3Manufacturing precision

If hardware-specific configurations are used directly, then resource provisioning precision is improved, but device complexity increases and users must understand hardware details

Engineering Contradiction:

Improveresource provisioning precisionVSAvoidorchestration complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the orchestration process into distinct layers: a high-level service description layer using meta-language, and a hardware-specific configuration layer. This segmentation allows users to work with simple service descriptions while the system handles complex hardware-specific configurations automatically, achieving resource provisioning precision without increasing user-facing complexity.

Inventive Principle:

Principle #1Segmentation

4Reliability

If context-aware orchestration is implemented, then service level objectives are met more accurately, but information processing requirements increase

Engineering Contradiction:

Improveservice level agreement complianceVSAvoidcomputational overhead

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary analysis and context extraction to identify only the most relevant information for service level objective compliance. By pre-processing and filtering context information before detailed analysis, the system achieves accurate service level agreement compliance while minimizing computational overhead through selective processing.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12536293B2Systems and methods for reactive intent-driven end-to-end orchestration

Publication Date: 2026.01.27 INTEL CORP

AI summary

Various systems and methods for reactive intent-driven end-to-end (E2E) orchestration are described herein. An orchestrator system, includes a processor; and memory to store instructions, which when executed by the processor, cause the system to: receive, at the orchestrator system, an intent-based service level agreement (SLA) for execution of a series of tasks on a plurality of compute nodes; calculate, based on the intent-based SLA, intermediate latency thresholds corresponding to each task of the series of tasks; calculate slack estimates based on the latency thresholds and real-time telemetry of the plurality of compute nodes or real-time telemetry of connections between the plurality of compute nodes; monitor execution of the series of tasks on the plurality of compute nodes; and perform a corrective action in response to determining that the execution of the series of tasks is predicted to exceed one of the intermediate latency thresholds.