IP Library Granted Patent US 11,032,396
Granted Patent B2
US 11,032,396 · App. 16/415,761 · Granted Jun 8, 2021

Systems and methods for managing client requests to access services provided by a data center

Inventor: Rajiv Sinha (Santa Clara, CA)
Assignee: Citrix Systems, Inc.
H04L67/36H04L43/062H04L43/0876H04L43/16H04L67/322H04L67/327
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,032,396
App. No.
16/415,761
Granted
Jun 8, 2021
Kind
B2
Abstract

Described embodiments provide systems and methods for managing client requests to access services provided by a data center. A method can include identifying, by a first device, metrics of client requests to a service communicated from a plurality of clients via one or more Internet service providers (ISPs) to a data center including a plurality of servers providing the service. The method can include identifying metrics of application programming interface (API) requests communicated between a plurality of microservices of the service responsive to the client requests being forwarded to the plurality of servers. The method can include identifying metrics of responses to the client requests. The method can include displaying a service graph generated to identify, via the metrics, an issue with at least one of the one or more ISPs, the plurality of microservices, or one or more WAN links.

Claims (30)

1. A method comprising:

(a) identifying, by a first device, first metrics for a service, the first metrics generated from client requests to the service communicated from a plurality of clients via one or more Internet service providers (ISPs) to a data center comprising a plurality of servers providing the service, the first metrics used to identify issues with the one or more ISPs;

(b) identifying, by the first device, second metrics for the service, the second metrics generated from application programming interface (API) requests communicated between a plurality of microservices of the service responsive to the client requests being forwarded to the plurality of servers, the second metrics used to identify issues with the plurality of microservices;

(c) identifying, by the first device, third metrics for the service, the third metrics generated from responses to the client requests, the responses generated by the plurality of microservices and communicated between a second device and the plurality of clients via one or more wide area network (WAN) links, the second device intermediary between the plurality of servers and the plurality of clients and configured to select the one or more WAN links via which to communicate the responses to the client requests, the third metrics used to identify issues with the one or more WAN links;

(d) generating, by the first device, a service graph to identify issues with at least one of the one or more ISPs, the plurality of microservices, or the one or more WAN links, the issues identified using the first, second, and third metrics; and

(e) displaying, by the first device, on the service graph, one or more graphical indicators, the one or more graphical indicators generated using the first metrics, the second metrics, or the third metrics, and used to identify an issue with at least one of the one or more ISPs, the plurality of microservices, or the one or more WAN links.

2. The method of claim 1 , wherein the client requests are forwarded to the data center by a traffic manager configured to select one of a global traffic manager or the data center based on at least fourth metrics of the one or more ISPs.

3. The method of claim 1 , wherein the first device is intermediary to the one or more ISPs and the data center.

4. The method of claim 1 , wherein d further comprises generating, by the first device, the service graph comprising a plurality of nodes to represent at least each of the one or more ISPs, the second device, and the plurality of microservices of the service.

5. The method of claim 4 , further comprising generating, by the first device, the service graph to comprise arcs between each of the plurality of nodes to identify metrics of network traffic between each of the plurality of nodes.

6. The method of claim 1 , wherein the client requests are forwarded from the plurality of clients via the one or more ISPs to an application delivery controller configured to manage network traffic to the service.

7. The method of claim 6 , further comprising identifying, by the first device, from the application delivery controller, metrics of network traffic of the plurality of clients between the one or more ISPs and the service, and generating, by the first device, the service graph, to identify, via the metrics of network traffic, one or more issues between the one or more ISPs and the service.

8. The method of claim 1 , wherein (e) further comprises displaying, by the first device, the service graph generated to identify metrics of network traffic from the plurality of clients via the one or more ISPs through the data center and to the plurality of clients via the second device.

9. The method of claim 1 , wherein (e) further comprises identifying, by the first device, the issue via the service graph.

10. A system comprising:

a first device comprising one or more processors, coupled to memory and configured to:

identify first metrics for a service, the first metrics generated from client requests communicated between a client of a plurality of clients via an Internet service provider (ISP) to a data center comprising a plurality of servers providing the service, wherein the client requests are to access the service, and wherein the first metrics are used to identify issues with the one or more ISPs; and

wherein the first device is configured to:

identify second metrics for the service, the second metrics generated from application programming interface (API) requests communicated between a plurality of microservices of the service responsive to the client requests being forwarded to the plurality of servers, the second metrics used to identify issues with the plurality of microservices;

identify third metrics for the service, the third metrics generated from responses to the client requests, the responses generated by the plurality of services, communicated between a second device and the client via one or more wide area network (WAN) links, the second device intermediary between the plurality of servers and the plurality of clients and configured to select the one or more WAN links via which to communicate the responses to the client requests, the third metrics used to identify issues with the one or more WAN links;

generate a service graph to identify issues with at least one of the one or more ISPs, the plurality of microservices, or the one or more WAN links, the issues identified using the first, second, and third metrics; and

display on the service graph, one or more graphical indicators, the one or more graphical indicators generated using the first metrics, the second metrics, or the third metrics, and used to identify an issue with at least one of the one or more ISPs, the plurality of microservices, or the one or more WAN links.

11. The system of claim 10 , wherein the client requests are forwarded to the data center by a traffic manager configured to select one of a global traffic manager or the data center based on a least fourth metrics of the one or more ISPs.

12. The system of claim 10 , wherein the first device is intermediary to the one or more ISPs and the data center.

13. The system of claim 10 , wherein the first device is further configured to generate the service graph comprising a plurality of nodes to represent at least each of the one or more ISPs, the second device, and the plurality of microservices of the service.

14. The system of claim 13 , wherein the first device is further configured to generate the service graph to comprise arcs between each of the plurality of nodes to identify metrics on network traffic between each of the plurality of nodes.

15. The system of claim 10 , wherein the client requests are forwarded from the plurality of clients via the one or more ISPs to an application delivery controller configured to manage network traffic to the service.

16. The system of claim 15 , wherein the first device is further configured to identify, from the application delivery controller, metrics of network traffic of the plurality of clients between the one or more ISPs and the service, and to generate the service graph to identify, via the metrics of network traffic, one or more issues between the one or more ISPs and the service.

17. The system of claim 10 , wherein the first device is further configured to display the service graph generated to identify metrics of network traffic from the plurality of clients via the one or more ISPs through the data center and to the plurality of clients via the second device.

18. The system of claim 10 , wherein the first device is further configured to identify the issue via the service graph.

Assignments (9)
PATENT SECURITY AGREEMENT Recorded Aug 15, 2025
From: CLOUD SOFTWARE GROUP, INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 072488/0172 →
SECURITY INTEREST Recorded May 24, 2024
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 067662/0568 →
RELEASE AND REASSIGNMENT OF SECURITY INTEREST IN PATENT (REEL/FRAME 062113/0001) Recorded Apr 14, 2023
From: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
To: CITRIX SYSTEMS, INC.; CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.)
Reel/Frame 063339/0525 →
PATENT SECURITY AGREEMENT Recorded Apr 14, 2023
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 063340/0164 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062112/0262 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 062113/0001 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 062113/0470 →
SECURITY INTEREST Recorded Sep 30, 2022
From: CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 062079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2019
From: SINHA, RAJIV
To: CITRIX SYSTEMS, INC.
Reel/Frame 049518/0476 →
Continuity (1)
Related Publication 20200366759A1 · Nov 19, 2020