WEIGHTED REQUEST RATE LIMITING FOR RESOURCES

• US 20110238838A1
• Filed: 11/17/2010
• Published: 09/29/2011
• Est. Priority Date: 03/23/2010
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Zhao, Ping, Avalani, Bhaven, Kumar, Abhinav, Murphy, Ronald Francis
• Granted Patent: US 9,058,210 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 16/3331 Query processing
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 2209/504 Resource capping
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Methods and systems to automatically respond to consider the weight of a request when responding to requests associated with resources are described. In one embodiment, an interface module may be configured to receive a request associated with consumer identifier and a resource. A calculator module may be configured to determine a weight of the request and a usage module configured to calculate, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier. An enforcer module may also be configured to respond to the request based on the usage level and the weight of the request. In one embodiment, the usage module may also be configured to update the usage level associated with the consumer identifier based on the weight of the request.

Claims

1. A method, comprising:

receiving a request associated with a consumer identifier and a resource;

determining a weight of the request;

calculating, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier; and

responding to the request based on the usage level and the weight of the request.

2. The method of claim 1, wherein the weight of the request is determined based on at least one of a type of the request and parameters associated with the request.

3. The method of claim 1, wherein the responding to the request is in accordance with a usage policy based on at least one of a weight per time period, an absolute weight limit, and a change in response time over a time period.

4. The method of claim 1, wherein responding to the request comprises rejecting the request.

5. The method of claim 1, further comprising updating the usage level associated with the consumer identifier based on the weight of the request.

6. The method of claim 1, wherein the calculating the usage level comprises identifying a pattern in the usage history associated with the consumer identifier.

7. The method of claim 1, wherein the request comprises the consumer identifier and a resource identifier.

8. A system, comprising:

an interface module configured to receive a request associated with consumer identifier and a resource;

a calculator module configured to determine a weight of the request;

a usage module configured to calculate, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier; and

an enforcer module configured to respond to the request based on the usage level and the weight of the request.

9. The system of claim 8, wherein the calculator module is configured to determine the weight of the request based on at least one of a type of the request and parameters associated with the request.

10. The system of claim 8, wherein the enforcer module is configured to respond to the request in accordance with a usage policy based on at least one of a weight per time period, an absolute weight limit, and a change in response time over a time period.

11. The system of claim 8, wherein the enforcer module is further configured to reject the request.

12. The system of claim 8, wherein the usage module is further configured to update the usage level associated with the consumer identifier based on the weight of the request.

13. The system of claim 8, wherein the usage module is further configured to identify a pattern in the usage history associated with the consumer identifier.

14. The system of claim 8, wherein the request comprises the consumer identifier and a resource identifier.

15. A non-transitory machine-readable medium comprising stored instructions, wherein the instructions, when executed, cause a machine to perform operations, comprising:

receiving a request associated with consumer identifier and a resource;

calculating a usage level associated with the consumer identifier, the usage level based on a weight of the request and a usage history associated with the consumer identifier; and

responding to the request based on the usage level.

16. The non-transitory machine-readable medium of claim 15, wherein the weight of the request is determined based on an estimate of the weight of the request.

17. The non-transitory machine-readable medium of claim 16, wherein the estimate of the weight of the request is based on responding to a plurality of previous requests.

18. The non-transitory machine-readable medium of claim 15, the machine-readable medium further comprising stored instructions, wherein the instructions, when executed, cause a machine to update the usage history associated with the consumer identifier based on the request.

19. A system, comprising:

means for receiving a request associated with consumer identifier and a resource;

means for determining a weight of the request;

means for calculating, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier; and

means for responding to the request based on the weight of the request and the usage level.

20. The system of claim 19, further comprising:

means for updating the usage history associated with the consumer identifier based on the request.