Wrapper API for Cloud Native Hardware Accelerator Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud Native applications written in languages like Golang and Rust face challenges in integrating hardware-based accelerators due to limited high-level language support and complex communication overhead, restricting the adoption of hardware accelerators like Intel QuickAssist Technology and ARM-based accelerators.

Innovation Solution

A lightweight wrapper API is provided to enable hardware accelerators in high-level programming languages such as Rust, allowing direct access to accelerators through low-level and high-level API interfaces, reducing complexity and communication overhead, and enabling efficient use of accelerators in cloud native applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If hardware-based accelerators are integrated using traditional low-level programming interfaces, then accelerator functionality can be accessed, but the complexity of integration and communication overhead increases significantly

Engineering Contradiction:
Improveease of integrationVSAvoidintegration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (wrapper API or translation layer) that sits between high-level cloud native applications and hardware-based accelerators. This intermediary translates high-level language calls into low-level accelerator commands, enabling seamless integration without requiring developers to directly manage complex hardware interfaces. The intermediary handles communication protocols, data format conversions, and resource management automatically.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If direct integration methods are used between high-level language applications and hardware accelerators, then performance can be improved, but the difficulty of implementation and maintenance increases

Engineering Contradiction:
Improveapplication performanceVSAvoidimplementation ease
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The patent segments the integration architecture into distinct layers: a high-level application interface layer, a translation/wrapper layer, and a hardware accelerator layer. Each layer has specific responsibilities and can be independently developed, tested, and maintained. This segmentation allows high-level applications to achieve near-direct performance while the complex translation logic is isolated in the intermediate layer, making the system easier to implement and maintain.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If cloud native applications use traditional programming interfaces for hardware accelerators, then accelerator functionality is available, but adoption is restricted due to limited high-level language support

Engineering Contradiction:
Improvelanguage compatibilityVSAvoidadoption reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a universal wrapper API layer that provides consistent interfaces for multiple high-level programming languages (such as Python, Java, Go) to access hardware-based accelerators. This universal interface translates language-specific calls into standardized accelerator commands, enabling broad language compatibility while maintaining reliable and consistent accelerator functionality across different programming environments.

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

Data Source

PatentUS20230259412A1Hardware-based accelerators in cloud native applications written in high level programming languages
Publication Date: 2023.08.17 INTEL CORP
  • US20230259412A1 patent drawing
  • US20230259412A1 patent drawing
  • US20230259412A1 patent drawing

AI summary

Various methods, systems, and use cases for providing a wrapper application programming interface (API). The wrapper API can invoke hardware accelerator libraries based on function calls from cloud native applications.