SMART NIC / DPU TRANSLATION AGENT FOR VENDOR-SPECIFIC COMMUNICATION
The Smart NIC/DPU translation agent addresses the challenge of non-standardized APIs by translating vendor-neutral methods into vendor-specific ones, enhancing communication efficiency and network performance in data centers.
DE102023120013B4Active Publication Date: 2026-06-18HEWLETT PACKARD ENTERPRISE DEV LP
Patent Information
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- HEWLETT PACKARD ENTERPRISE DEV LP
- Filing Date
- 2023-07-27
- Publication Date
- 2026-06-18
AI Technical Summary
Technical Problem
The integration and management of smart NICs and DPUs in data centers are hindered by proprietary and non-standardized API methods, leading to complexity and inefficiency in configuration and control processes.
Method used
A Smart NIC/DPU translation agent that translates vendor-neutral API methods into vendor-specific ones, enabling seamless communication and management through an industry-standard data model, reducing complexity and freeing up processor resources.
Benefits of technology
Facilitates efficient and standardized communication with smart NICs and DPUs, improving network performance and reducing the complexity of API transactions.
✦ Generated by Eureka AI based on patent content.
Smart Images
Figure 00000000_0000_ABST
Abstract
A device (120) comprising the following: at least one memory (122) in which computer-readable instructions are stored which, when executed by at least one processor (124) coupled to the at least one memory (122), cause the at least one processor (124) to: to receive data from a web service client (150), wherein the data includes at least one operational request associated with a vendor-neutral application programming interface (API) procedure, wherein the at least one operational request includes at least one request to configure a tenant VPC in a Smart NIC (132), and wherein the vendor-neutral API procedure includes a RESTful data model (Representational State Transfer Web API); which modify at least one operational requirement to match a Fabric data model; Decomposing the modified at least one operation requirement into a multitude of operations that act on data associated with a vendor-specific API method, where the vendor-specific API method differs from the vendor-neutral API method; and Performing the multitude of operations that act on the data using the vendor-specific API method for passing to the vendor firmware (160).
Need to check novelty before this filing date? Find Prior Art