Application Resource Reservation for Deterministic Precision Networking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional networking methods fail to provide strict Quality of Service (QoS) reservations within the operating system and platform, leading to non-deterministic processing delays and resource overprovisioning in mission-critical precision networking systems.

Innovation Solution

Implementing a framework for application-to-application resource reservation schemes that dynamically reserve OS/Hypervisor and platform resources, including cross-interconnect reservations, to achieve deterministic processing delays and QoS.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional NIC to NIC network reservations are used, then network path QoS can be provided, but reservations within the OS and platform are not addressed leading to non-deterministic processing delays

Engineering Contradiction:
ImproveQoS guaranteeVSAvoidprocessing delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the end-to-end network path into multiple reservation domains: network path (NIC to NIC), OS/Hypervisor, and platform resources. Each domain has its own reservation mechanism, allowing deterministic processing at each stage rather than relying solely on network path reservations. This segmentation addresses the technical contradiction by extending QoS guarantees from just the network path to include system processing stages.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary resource reservation before data transmission occurs. The application-to-application reservation mechanism pre-allocates resources across the network path, OS, and platform before actual data flow begins. This preliminary action eliminates non-deterministic processing delays by ensuring resources are reserved in advance, rather than competing for resources during transmission.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If resources are overprovisioned to avoid compromising QoS, then deterministic networking can be achieved, but resource efficiency decreases

Engineering Contradiction:
ImproveQoS guaranteeVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic resource reservation that adapts to actual application requirements. The application-to-application reservation mechanism allows resources to be allocated precisely based on measured or declared application needs, rather than statically overprovisioning. This dynamic approach maintains QoS guarantees while improving resource efficiency by allocating only what is necessary.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the reservation parameter from network-only to application-to-application across multiple domains. By extending reservations to include OS and platform resources with specific performance parameters (processing delays, bandwidth), the system achieves deterministic networking without overprovisioning, as resources are reserved with precise parameter specifications rather than excessive capacity.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If application-to-application resource reservation is implemented, then deterministic processing delays are achieved, but system complexity increases

Engineering Contradiction:
Improveprocessing delayVSAvoidreservation framework
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent creates a universal reservation framework that handles multiple domains (network path, OS, platform) through a single application-to-application interface. This multi-functional reservation mechanism consolidates what would otherwise require separate reservation systems for each domain, achieving deterministic processing delays while managing complexity through unification rather than proliferation of separate mechanisms.

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

Solution Approach 2:

The patent introduces an intermediary reservation management layer that coordinates between application requirements and system resources. This intermediary handles the complexity of cross-domain reservations by providing a standardized interface and translation layer, reducing the overall system complexity compared to direct peer-to-peer reservations across multiple domains.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If cross-interconnect reservations are implemented, then platform resource determinism is improved, but implementation complexity increases

Engineering Contradiction:
Improveplatform resource determinismVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent merges cross-interconnect reservations with the overall application-to-application reservation framework. Rather than implementing separate complex reservation systems for each interconnect, the patent combines them into a unified reservation mechanism that handles platform resources collectively. This merging reduces implementation complexity while maintaining platform resource determinism.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12483515B2Application-to-application resource reservation schemes for precision networking
Publication Date: 2025.11.25 INTEL CORP
  • US12483515B2 patent drawing
  • US12483515B2 patent drawing
  • US12483515B2 patent drawing

AI summary

Methods and apparatus for application-to-application resource reservation schemes for precision networking. Hardware resources, such as interconnects and processing resources, are reserved for forwarding and processing data along flow paths for end-to-end delivery of data between applications running on respective platforms communicating over a network. Operating system and/or hypervisor resources are also reserved. The reservations may be based per application, per virtual machine (VM), or per container, and reservations for multiple applications/VMs/containers are supported. The interconnects include chip-to-chip, socket-to-socket (for multi-socket platforms), and die-to-die interconnects. Reservations for on-chip fabrics are also supported. Under one approach, an orchestrator is used to manage resources reservations by sending resources reservation requests to a platform's operating system or hypervisor, with the operating system/hypervisor configuring the platform hardware resources to effect based on the reserved resources. The method and apparatus may be used to implement flow paths having deterministic latencies and/or meet SLA QoS requirements.