Remote GPU Middleware for Confidential Disaggregated Computing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing disaggregated computing systems face security challenges in distributed environments, particularly in multi-tenant scenarios where data confidentiality and integrity are compromised due to untrusted software accessing accelerator devices like FPGAs.

Innovation Solution

Implementing a trusted execution environment (TEE) and secure data transfer mechanisms using memory-mapped I/O (MMIO) and direct memory access (DMA) transactions, along with cryptographic operations and authentication tags, to secure data exchange between processors and accelerators, thereby isolating untrusted software from sensitive operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If disaggregated computing is implemented to improve resource utilization and performance, then productivity and resource efficiency are improved, but security and data confidentiality are compromised due to untrusted software accessing accelerator devices

Engineering Contradiction:
Improveresource utilizationVSAvoiddata confidentiality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system segments the computing environment into trusted and untrusted zones by implementing virtualization layers and secure enclaves. Accelerator devices are divided into isolated instances, each with controlled access permissions, allowing multiple tenants to share hardware resources while maintaining security boundaries through virtual machine monitors and trusted execution environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A trusted intermediary layer (virtualization platform, driver stack, or secure runtime environment) is introduced between untrusted software and accelerator devices. This intermediary enforces access policies, validates operations, and protects sensitive data, enabling secure sharing of accelerators across multiple tenants without direct software-hardware access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If direct hardware access is allowed for high-performance computing, then processing speed and performance are improved, but security control and data integrity are reduced

Engineering Contradiction:
Improveprocessing speedVSAvoidsecurity risks
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

Security validations and access authorizations are performed in advance before software can access accelerator devices. The system pre-configures secure contexts, establishes trust relationships, and validates operation codes before execution, ensuring that high-speed processing occurs only within approved security boundaries without runtime security checks that would slow performance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces physical direct-access mechanisms with software-based security abstractions. Instead of allowing direct hardware access through physical or electrical connections, the system uses virtualized access paths, encrypted communication channels, and software-enforced security policies that maintain performance while eliminating security vulnerabilities associated with direct access.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12405838B2Disaggregated computing for distributed confidential computing environment
Publication Date: 2025.09.02 INTEL CORP
  • US12405838B2 patent drawing
  • US12405838B2 patent drawing
  • US12405838B2 patent drawing

AI summary

An apparatus to facilitate disaggregated computing for a distributed confidential computing environment is disclosed. The apparatus includes one or more processors to: provide a remote GPU middleware layer to act as a proxy for an application stack on a client platform that is separate from the remote server platform, wherein the remote GPU middleware layer comprises is to expose an abstraction of the remote GPU to userspace components of a remote GPU stack, the userspace components running on the client machine; communicate with a kernel mode driver of the one or more processors to cause the host memory to be allocated for data structures used to communicate commands between the client and the remote GPU; and invoke the kernel mode driver to submit a workload generated by the application stack, the workload submitted for processing by the remote GPU using the data structures allocated in the host memory.