REQUEST ORCHESTRATION USING PREDICTIVE SERVICE CONGESTION CONTROL

• US 20190327324A1
• Filed: 04/19/2019
• Published: 10/24/2019
• Est. Priority Date: 04/23/2018
• Status: Active Grant

• Current Assignee: Yottaa, Inc.
• Original Assignee: Yottaa, Inc.
• Inventors: Buffone, Robert
• Granted Patent: US 10,986,202 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

This disclosure is directed to methods and systems for managing client-side services. An intermediary may receive from an agent incorporated into a web application or client-side application and executing on the client device, a request for a configuration to manage loading of services from the at least one server onto the web application or client-side application. The intermediary can determine an expected temporal pattern of use for at least some of the services at the client device. The intermediary can generate the configuration. The configuration can specify for each of the services, an expected amount of bandwidth to be utilized for loading the corresponding service from the at least one server onto the web application or client-side application, and a loading priority according to the expected temporal pattern of use. The intermediary can send the configuration to the agent.

Claims

1. A method for managing client-side services, the method comprising:

receiving, by an intermediary between a client device and at least one server, from an agent incorporated into a web application or client application and executing on the client device, a request for a configuration to manage loading of services from the at least one server onto the web application or client application;

determining, by the intermediary, an expected temporal pattern of use for at least some of the services at the client device;

generating, by the intermediary, the configuration, the configuration specifying, for each of the services, an expected amount of bandwidth to be utilized for loading the corresponding service from the at least one server onto the web application or client application, and a loading priority according to the expected temporal pattern of use; and

sending, by the intermediary, the configuration to the agent executing on the client device, to cause the web application or client application to request the services from the at least one server in a sequence according to the configuration and to bandwidth available to the client device determined by the agent.

2. The method of claim 1, comprising causing the web application or client application to request the services in a sequence according to hardware resources available on the client device, to the configuration, and to the bandwidth available to the client device determined by the agent.

3. The method of claim 1, comprising determining, by the intermediary for a first service of the services, according to historical data, at least one of:

a number of requests expected from the web application or client-side application to the at least one server to load the first service, an expected response time of the at least one server to a request from the web application or client-side application to load the first service, an expected speed for loading the first service from the at least one server to the web application or client-side application, or an expected loading progression pattern for the first service.

4. The method of claim 3, comprising generating, by the intermediary, the configuration, the configuration specifying for the first service at least one of:

the number of requests expected from the web application or client-side application to the at least one server to load the first service, the expected response time of the at least one server to a request from the web application or client-side application to load the first service, the expected speed for loading the first service from the at least one server to the web application or client-side application, or the expected loading progression pattern for the first service.

5. The method of claim 1, comprising generating a loading priority for a first service of the services, according to at least one of:

a number of requests expected from the web application or client-side application to the at least one server to load the first service, an expected response time of the at least one server to a request from the web application or client-side application to load the first service, an expected speed for loading the first service from the at least one server to the web application or client-side application, an expected loading progression pattern for the first service, a user interface location of the first service on the web application or client-side application, an expected temporal pattern of use of the first service, or an expected amount of bandwidth to be utilized for loading the first service from the at least one server onto the web application or client-side application.

6. The method of claim 1, wherein the configuration further specifies to load the services onto the web application or client-side application according to a sequence established by weighting the loading priorities of the services with corresponding amounts of bandwidth expected to be utilized for loading the corresponding services.

7. The method of claim 1, comprising generating the configuration automatically or via user input, wherein the configuration further specifies to load the services onto the web application or client-side application according to the loading priorities of the services.

8. The method of claim 1, comprising prioritizing the loading of the services within a specified time constraint or a specified bandwidth.

9. The method of claim 1, further comprising tracking user interaction with a first service of the services, wherein the configuration specifies a loading priority for the first service according to the user interaction.

10. The method of claim 1, comprising:

receiving or monitoring, by the intermediary, runtime characteristics of the services; and

maintaining, by the intermediary, the received runtime characteristics in a storage device.

11. A system for managing client-side services, the system comprising:

one or more processors for implementing an intermediary between a client device and at least one server, the intermediary including a configuration engine configured to;

receive from an agent incorporated into a web application or client application and executing on the client device, a request for a configuration to manage loading of services from the at least one server onto the web application or client application;

determine an expected temporal pattern of use for at least some of the services at the client device;

generate the configuration, the configuration specifying, for each of the services, an expected amount of bandwidth to be utilized for loading the corresponding service from the at least one server onto the web application or client application, and a loading priority according to the expected temporal pattern of use; and

send the configuration to the agent executing on the client device, to cause the web application or client application to request the services from the at least one server in a sequence according to the configuration and to bandwidth available to the client device determined by the agent.

12. The system of claim 11, wherein the configuration engine is configured to cause the web application or client application to request the services in a sequence according to hardware resources available on the client device, to the configuration, and to the bandwidth available to the client device determined by the agent.

13. The system of claim 11, wherein the configuration engine is configured to determine, for a first service of the services, according to historical data, at least one of:

a number of requests expected from the web application or client-side application to the at least one server to load the first service, an expected response time of the at least one server to a request from the web application or client-side application to load the first service, an expected speed for loading the first service from the at least one server to the web application or client-side application, or an expected loading progression pattern for the first service.

14. The system of claim 13, wherein the configuration engine is configured to generate the configuration, the configuration specifying for the first service at least one of:

the number of requests expected from the web application or client-side application to the at least one server to load the first service, the expected response time of the at least one server to a request from the web application or client-side application to load the first service, the expected speed for loading the first service from the at least one server to the web application or client-side application, or the expected loading progression pattern for the first service.

15. The system of claim 11, wherein the configuration engine is configured to generate a loading priority for a first service of the services, according to at least one of:

a number of requests expected from the web application or client-side application to the at least one server to load the first service, an expected response time of the at least one server to a request from the web application or client-side application to load the first service, an expected speed for loading the first service from the at least one server to the web application or client-side application, an expected loading progression pattern for the first service, a user interface location of the first service on the web application or client-side application, an expected temporal pattern of use of the first service, or an expected amount of bandwidth to be utilized for loading the first service from the at least one server onto the web application or client-side application.

16. The system of claim 11, wherein the configuration further specifies to load the services onto the web application or client-side application according to a sequence established by weighting the loading priorities of the services with corresponding amounts of bandwidth expected to be utilized for loading the corresponding services.

17. The system of claim 11, wherein the configuration engine is configured to generate the configuration automatically or via user input, wherein the configuration further specifies to load the services onto the web application or client-side application according to the loading priorities of the services.

18. The system of claim 11, comprising prioritizing the loading of the services within a specified time constraint or a specified bandwidth.

19. The system of claim 11, further comprising a metadata engine configured to track user interaction with a first service of the services, wherein the configuration specifies a loading priority for the first service according to the user interaction.

20. The system of claim 11, further comprising a metadata engine of the intermediary, configured to:

receive or monitor runtime characteristics of the services; and

maintain the received runtime characteristics in a storage device.