Granted Patent B2

US 12,568,156 · App. 18/770,234 · Granted Mar 3, 2026

Inventors: Matthew Johnson (Littleton, CO); Thomas Durdin (Longmont, CO); Jeff Scheufele (Lafayette, CO); John T. Pugaczewski (Hugo, MN)

Assignee: Level 3 Communications, LLC

H04L67/63H04L43/062H04L63/102

Abstract

Claims (76)

1 . A method for using an application programming interface (API) gateway orchestration layer, the method comprising:

identifying, by at least one processor of the API gateway orchestration layer, a first API request, received by an API gateway API, to access a first microservice of a first API gateway;

identifying, by the at least one processor, a second API request, received by the API gateway API, to access a second microservice of a second API gateway;

determining, by the at least one processor, based on the first API request, a first route to the first API gateway;

determining, by the at least one processor, based on the second API request, a second route to the second API gateway;

routing, by the at least one processor, the first API request to the first microservice based on the first route; and

routing, by the at least one processor, the second API request to the second microservice based on the second route.

2 . The method of claim 1 , wherein the API gateway orchestration layer is a management layer of an API gateway orchestration system.

3 . The method of claim 1 , wherein the first API request is received from a first API gateway client, and wherein the second API request is received from a second API gateway client different than the first API gateway client.

4 . The method of claim 1 , further comprising:

identifying, based on the first API request, a first configuration associated with the first API gateway; and

identifying, based on the second API request, a second configuration associated with the second API gateway, the second configuration different than the first configuration,

wherein routing the first API request is further based on the first configuration, and

wherein routing the second API request is further based on the second configuration.

5 . The method of claim 4 , further comprising:

identifying a first API response received from the first API gateway based on the first API request;

identifying a second API response received from the second API gateway based on the second API request;

determining that the first API response uses the first configuration;

determining that the second API responses uses the second configuration;

routing, based on the determination that the first API response uses the first configuration, the first API response to a first API gateway client from which the first API request was received, and

routing, based on the determination that the second API response uses the second configuration, the second API response to a second API gateway client from which the second API request was received.

6 . The method of claim 1 , further comprising:

sending, to an API gateway client, syslog message logging data, telemetry data, and instruction trace data.

7 . The method of claim 1 , further comprising:

sending, to an API gateway client, analytics data comprising a number of API calls detected, error rates associated with API calls, API gateway security data, and latency associated with API calls.

8 . The method of claim 1 , further comprising:

authenticating a first API gateway client from which the first API request was received, wherein routing the first API request is further based on authenticating the first API gateway client; and

authenticating a second API gateway client from which the second API request was received, wherein routing the second API request is further based on authenticating the second API gateway request.

9 . An application programming interface (API) gateway orchestration system, the API gateway orchestration system comprising memory coupled to at least one processor, the at least one processor configured to:

identify a first API request, received by an API gateway API, to access a first microservice of a first API gateway;

identify a second API request, received by the API gateway API, to access a second microservice of a second API gateway;

determine, based on the first API request, a first route to the first API gateway;

determine, based on the second API request, a second route to the second API gateway;

route the first API request to the first microservice based on the first route; and

route the second API request to the second microservice based on the second route.

10 . The API gateway orchestration system of claim 9 , wherein the first API request is received from a first API gateway client, and wherein the second API request is received from a second API gateway client different than the first API gateway client.

11 . The API gateway orchestration system of claim 9 , wherein the at least one processor is further configured to:

identify, based on the first API request, a first configuration associated with the first API gateway; and

identify, based on the second API request, a second configuration associated with the second API gateway, the second configuration different than the first configuration,

wherein to route the first API request is further based on the first configuration, and

wherein to route the second API request is further based on the second configuration.

12 . The API gateway orchestration system of claim 11 , wherein the at least one processor is further configured to:

identify a first API response received from the first API gateway based on the first API request;

identify a second API response received from the second API gateway based on the second API request;

determine that the first API response uses the first configuration;

determine that the second API responses uses the second configuration;

route, based on the determination that the first API response uses the first configuration, the first API response to a first API gateway client from which the first API request was received, and

route, based on the determination that the second API response uses the second configuration, the second API response to a second API gateway client from which the second API request was received.

13 . The API gateway orchestration system of claim 9 , wherein the at least one processor is further configured to:

sending, to an API gateway client, syslog message logging data, telemetry data, and instruction trace data.

14 . The API gateway orchestration system of claim 9 , wherein the at least one processor is further configured to:

send, to an API gateway client, analytics data comprising a number of API calls detected, error rates associated with API calls, API gateway security data, and latency associated with API calls.

15 . The API gateway orchestration system of claim 9 , wherein the at least one processor is further configured to:

authenticate a first API gateway client from which the first API request was received, wherein to route the first API request is further based on authenticating the first API gateway client; and

authenticate a second API gateway client from which the second API request was received, wherein to route the second API request is further based on authenticating the second API gateway request.

16 . A non-transitory storage medium comprising instructions to cause processing circuitry of a device for using an application programming interface (API) gateway orchestration layer, upon execution of the instructions by the processing circuitry, to:

identify a first API request, received by an API gateway API, to access a first microservice of a first API gateway;

identify a second API request, received by the API gateway API, to access a second microservice of a second API gateway;

determine, based on the first API request, a first route to the first API gateway;

determine, based on the second API request, a second route to the second API gateway;

route the first API request to the first microservice based on the first route; and

route the second API request to the second microservice based on the second route.

17 . The non-transitory storage medium of claim 16 , wherein the API gateway orchestration layer is a management layer of an API gateway orchestration system.

18 . The non-transitory storage medium of claim 16 , wherein execution of the instructions further causes the processing circuitry to:

identify, based on the first API request, a first configuration associated with the first API gateway; and

identify, based on the second API request, a second configuration associated with the second API gateway, the second configuration different than the first configuration,

wherein to route the first API request is further based on the first configuration, and

wherein to route the second API request is further based on the second configuration.

19 . The non-transitory storage medium of claim 18 , wherein execution of the instructions further causes the processing circuitry to:

identify a first API response received from the first API gateway based on the first API request;

identify a second API response received from the second API gateway based on the second API request;

determine that the first API response uses the first configuration;

determine that the second API responses uses the second configuration;

route, based on the determination that the first API response uses the first configuration, the first API response to a first API gateway client from which the first API request was received, and

route, based on the determination that the second API response uses the second configuration, the second API response to a second API gateway client from which the second API request was received.

20 . The non-transitory storage medium of claim 16 , wherein execution of the instructions 20 . further causes the processing circuitry to: sending, to an API gateway client, syslog message logging data, telemetry data, and instruction trace data.

Assignments (3)

Continuity (3)

References Cited (23)