System and method for facilitating load reduction at a landing zone

• US 9,942,312 B1
• Filed: 12/16/2016
• Issued: 04/10/2018
• Est. Priority Date: 12/16/2016
• Status: Active Grant

• Current Assignee: Zoomdata, Inc. (Global Software, Inc.)
• Original Assignee: Zoomdata, Inc. (Global Software, Inc.)
• Inventors: Langseth, Justin, Farchtchi, Ruhollah, Luu, Quan Cat, Barrett, Matthew Robert, Rathore, Punit
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US15/382,534
• Time in Patent Office: 480 Days
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/32 with visual or acoustical indication of the functioning of the machine
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/101 based on network conditions

Abstract

In certain embodiments, load reduction at a landing zone may be facilitated. In some embodiments, a request related to a client-initiated query may be predicted. A second landing zone may be assigned to handle responding to the query-related request, where the second landing zone is different from a first landing zone at which the query-related request is subsequently obtained. Responsive to obtaining the query-related request at the first landing zone from a client device, cause, based on the assignment to the second landing zone, the client device to redirect the query-related request to the second landing zone. The client device may be caused to redirect the query-related request such that the client device transmits the query-related request and subsequent requests for an update related to the client-initiated query to the second landing zone without first transmitting the subsequent requests to the first landing zone.

Claims

1. A method of facilitating load reduction at a landing zone, the method being implemented by a computer system that comprises one or more processors executing computer program instructions that, when executed, perform the method, the method comprising:

predicting a request related to a client-initiated query, the predicted request comprising one or more predicted search parameters;

assigning a second landing zone to handle responding to the predicted request, the second landing zone being different from a first landing zone at which a first request is subsequently obtained;

obtaining, at the first landing zone, the first request from a client device, the first request being obtained subsequent to the assignment to the second landing zone, the first request comprising one or more first search parameters;

determining whether the first request matches the predicted request based on whether the one or more first search parameters matches the one or more predicted search parameters; and

instructing, by the first landing zone, based on the assignment to the second landing zone and based on the first request matching the predicted request, the client device to redirect the first request to the second landing zone such that the client device transmits the first request and subsequent requests for an update related to the client-initiated query to the second landing zone without first transmitting the subsequent requests to the first landing zone.

2. The method of claim 1, wherein instructing the client device to redirect the first request to the second landing zone comprises providing, to the client device, a redirection instruction and an address associated with the second landing zone such that the client device transmits, based on the redirection instruction and the second landing zone address, the first request and the subsequent requests to the second landing zone without first transmitting the subsequent requests to the first landing zone.

3. The method of claim 1, further comprising:

determining request history information indicating one or more queries initiated prior to the client-initiated query or a frequency of requests related to queries matching the client-initiated query,

wherein predicting the request comprises predicting the request based on the request hi story information.

4. The method of claim 1, further comprising:

predicting another request related to another client-initiated query;

assigning a third landing zone to handle responding to the other predicted request, the third landing zone being different from the first landing zone and the second landing zone;

obtaining, at the first landing zone, a second request from the client device;

determining whether the second request matches the other predicted request; and

instructing, by the first landing zone, based on the assignment to the third landing zone and based on the second request matching the other predicted request, the client device to redirect the second request to the third landing zone such that the client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the third landing zone without first transmitting the other subsequent requests to the first landing zone.

5. The method of claim 1, further comprising:

predicting another request related to another client-initiated query;

assigning a third landing zone to handle responding to the other predicted request, the third landing zone being different from the first landing zone and the second landing zone;

obtaining, at the first landing zone, a second request from another client device;

determining whether the second request matches the other predicted request; and

instructing, by the first landing zone, based on the assignment to the third landing zone and based on the second request matching the other predicted request, the other client device to redirect the second request to the third landing zone such that the other client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the third landing zone without first transmitting the other subsequent requests to the first landing zone.

6. The method of claim 1, further comprising:

obtaining, at the first landing zone, from another client device, a second request related to another client-initiated query;

determining whether the other client-initiated query of the second request matches the client-initiated query of the predicted request; and

instructing, by the first landing zone, based on the assignment to the second landing zone and based on the other client-initiated request matching the client-initiated query, the other client device to redirect the second request to the second landing zone such that the other client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the second landing zone without first transmitting the other subsequent requests to the first landing zone.

7. The method of claim 1, wherein the first landing zone is a default landing zone, and the second landing zone is a query-specific landing zone.

8. The method of claim 1, wherein the first request comprises a query submission or an update request related to the client-initiated query.

9. The method of claim 1, wherein the first landing zone corresponds to a first server, and the second landing zone corresponds to a second server different from the first server.

10. The method of claim 1, wherein the first landing zone is a first server or a component hosted at the first server, and the second landing zone is a second server or a component hosted at the second server.

11. A system for facilitating load reduction at a landing zone, the system comprising:

a computer system comprising one or more processors executing computer program instructions that, when executed, cause the computer system to;

predict a request related to a client-initiated query, the predicted request comprising one or more predicted search parameters;

assign a second landing zone to handle responding to the predicted request, the second landing zone being different from a first landing zone at which a first request is subsequently obtained;

obtain, at the first landing zone, the first request from a client device, the first request being obtained subsequent to the assignment to the second landing zone, the first request comprising one or more first search parameters;

determine whether the first request matches the predicted request based on whether the one or more first search parameters matches the one or more predicted search parameters; and

instruct, by the first landing zone, based on the assignment to the second landing zone and based on the first request matching the predicted request, the client device to redirect the first request to the second landing zone such that the client device transmits the first request and subsequent requests for an update related to the client-initiated query to the second landing zone without first transmitting the subsequent requests to the first landing zone.

12. The system of claim 11, wherein instructing the client device to redirect the first request to the second landing zone comprises providing, to the client device, a redirection instruction and an address associated with the second landing zone such that the client device transmits, based on the redirection instruction and the second landing zone address, the first request and the subsequent requests to the second landing zone without first transmitting the subsequent requests to the first landing zone.

13. The system of claim 11, wherein the computer system is further caused to:

determine request history information indicating one or more queries initiated prior to the client-initiated query or a frequency of requests related to queries matching the client-initiated query,

wherein predicting the request comprises predicting the request based on the request history information.

14. The system of claim 11, wherein the computer system is further caused to:

predict another request related to another client-initiated query;

assign a third landing zone to handle responding to the other predicted request, the third landing zone being different from the first landing zone and the second landing zone;

obtain, at the first landing zone, a second request from the client device;

determine whether the second request matches the other predicted request; and

instruct, by the first landing zone, based on the assignment to the third landing zone and based on the second request matching the other predicted request, the client device to redirect the second request to the third landing zone such that the client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the third landing zone without first transmitting the other subsequent requests to the first landing zone.

15. The system of claim 11, wherein the computer system is further caused to:

predict another request related to another client-initiated query;

assign a third landing zone to handle responding to the other predicted request, the third landing zone being different from the first landing zone and the second landing zone;

obtain, at the first landing zone, a second request from another client device;

determine whether the second request matches the other predicted request; and

instruct, by the first landing zone, based on the assignment to the third landing zone and based on the second request matching the other predicted request, the other client device to redirect the second request to the third landing zone such that the other client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the third landing zone without first transmitting the other subsequent requests to the first landing zone.

16. The system of claim 11, wherein the computer system is further caused to:

obtain, at the first landing zone, from another client device, a second request related to another client-initiated query matching the client-initiated query;

determine whether the other client-initiated query of the second request matches the client-initiated query of the predicted request; and

instruct, by the first landing zone, based on the assignment to the second landing zone and based on the other client-initiated request matching the client-initiated query, the other client device to redirect the second request to the second landing zone such that the other client device transmits the second request and other subsequent requests for an update related to the other client-initiated query to the second landing zone without first transmitting the other subsequent requests to the first landing zone.

17. The system of claim 11, wherein the first landing zone is a default landing zone, and the second landing zone is a query-specific landing zone, and wherein the first request comprises a query submission or an update request related to the client-initiated query.

18. The system of claim 11, wherein

the first landing zone is a first server or a component hosted at the first server, and the second landing zone is a second server or a component hosted at the second server.

19. A method of facilitating load reduction at a landing zone, the method being implemented by a computer system that comprises one or more processors executing computer program instructions that, when executed, perform the method, the method comprising:

assigning a second landing zone to handle responding to a first request related to a client-initiated query, the second landing zone being different from a first landing zone at which a second request is subsequently obtained;

obtaining, at the first landing zone, the second request from a client device, the second request being obtained subsequent to the assignment to the second landing zone;

determining whether the second request matches the first request; and

instructing, by the first landing zone, based on the assignment to the second landing zone and based on the second request matching the first request, the client device to redirect the second request to the second landing zone such that the client device transmits the second request and subsequent requests for an update related to the client-initiated query to the second landing zone without first transmitting the subsequent requests to the first landing zone.

20. The method of claim 19, further comprising:

obtaining, at the first landing zone, from another client device, a third request related to another client-initiated query;

determining whether the other client-initiated query of the third request matches the client-initiated query of the first request; and

instructing, by the first landing zone, based on the assignment of the second landing zone and based on the other client-initiated query matching the client-initiated query, the other client device to redirect the third request to the second landing zone such that the other client device transmits the third request and other subsequent requests for an update related to the other client-initiated query to the second landing zone without first transmitting the other subsequent requests to the first landing zone.