Granted Patent B2

US 12,418,441 · App. 18/181,523 · Granted Sep 16, 2025

Inventors: Phillip Andrew Leech (Houston, TX); Jeffrey R. Hilland (Lago Vista, TX); Clark Thomas Laughlin (Houston, TX)

Assignee: Hewlett Packard Enterprise Development LP

H04L12/4641H04L12/4633H04L41/0806

Abstract

Claims (41)

1. A device comprising:

at least one memory having computer-readable instructions stored thereon which, when executed by at least one processor coupled to the at least one memory, cause the at least one processor to:

receive data from a web service client, the data comprising at least one operation request associated with a vendor-neutral Application Programming Interface (API) method, wherein the at least one operation request comprises at least one request to configure a tenant VPC in a Smart NIC and wherein the vendor-neutral API method comprises a representational state transfer web API (RESTful) data model;

modify the at least one operation request to conform with a fabric data model;

decompose the modified at least one operation request into a plurality of operations that act on data associated with a vendor-specific API method, wherein the vendor-specific API method is different from the vendor-neutral API method; and

perform, the plurality of operations that act on the data using the vendor-specific API method for delivery to vendor firmware.

2. The device of claim 1 , wherein the at least one processor operable to receive data, comprises:

monitoring data traffic associated with internet protocol HTTP/2;

identifying at least one operation request associated with a vendor-neutral API method;

receive the at least one operation request; and

modifying the at least one operation request to conform with the fabric data model.

3. The device of claim 1 , wherein the at least one processor operable to decompose the at least one operation request, comprises:

receiving the modified at least one operation request;

generating the plurality of operations aligning with the vendor-specific API associated with configuration commands for configuring an Operator underlay networking based upon the modified at least one operation request; and

generating the plurality of operations aligning with the vendor-specific API associated with control commands for controlling the Operator underlay networking based upon the modified at least one operation request.

4. The device of claim 1 , wherein the at least one processor operable to perform the plurality of operations, comprises:

receiving the plurality of operations associated with configuration commands and control commands;

executing the plurality of operations associated with the vendor firmware; and

sending resulting data from the executed plurality of operations to the vendor firmware.

5. The device of claim 1 , wherein the vendor-neutral API method comprises a high-performance Remote Procedure Call (RPC) framework.

6. The device of claim 1 , wherein the RESTful data model is used for a transport layer of the high-performance RPC framework.

7. The device of claim 1 , wherein the RESTful data model represents at least one of an operator Virtual Private Cloud (VPC) or a tenant VPC.

8. The device of claim 7 , wherein the RESTful data model comprises at least one zone corresponding to a plurality of networks or subnets.

9. The device of claim 8 , wherein the RESTful data model comprises at least one endpoint having at least one address pool corresponding to a plurality of terminating host interfaces.

10. The device of claim 1 , wherein the at least one operation request comprises at least one configuration request or control function request.

11. The device of claim 10 , wherein the at least one configuration request or control function request comprises at least one request to configure a Data Processing Unit (DPU) for operator underlay networking or tenant Virtual Private Cloud (VPC) overlay networking.

12. The device of claim 1 , wherein the vendor-specific API method comprises a vendor-specific high-performance RPC framework API.

13. The device of claim 1 , wherein the set of operations that act on the data comprises at least one management function.

14. The device of claim 13 , wherein the at least one management function comprises at least one configuration function or control function.

15. The device of claim 14 , wherein the at least one configuration function or control function comprises at least one function to configure at least one of: operator underlay networking or tenant VPC overlay networking.

16. The device of claim 1 , wherein the at least one processor comprises a management interface configured to expose a vendor-specific API.

17. The device of claim 16 , wherein the management interface is configured to expose the vendor-specific API over a high-performance RPC framework.

18. The device of claim 16 , wherein the at least one processor is further caused to obtain, using a telemetry service unit, telemetry data for a vendor-supplied network component via the vendor-specific API.

19. A method comprising:

receiving, using an orchestration service unit, data from an external entity, the data comprising at least one operation request using a vendor-neutral API method;

decomposing, using a configuration service unit, the at least one operation request into a plurality of operations that act on the data using a vendor-specific API method, wherein the vendor-specific API method is different from the vendor-neutral API method; and

implementing, using a proxy service unit, the plurality of operations that act on the data using the vendor-specific API method.

20. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by at least one processor, cause the at least one processor to:

detect, using an orchestration service unit, data from an external entity, the data comprising at least one operation request using a vendor-neutral API method comprising a RESTful data model;

translate, using a configuration service unit, the at least one operation request into a plurality of operations that act on the data using a vendor-specific API method, wherein the vendor-specific API method is different from the vendor-neutral API method; and

execute, using a proxy service unit, the plurality of operations that act on the data using the vendor-specific API method.

Assignments (1)

Continuity (1)

References Cited (9)