SCALABLE CLOUD - ASSIGNING SCORES TO REQUESTERS AND TREATING REQUESTS DIFFERENTLY BASED ON THOSE SCORES

• US 20190102252A1
• Filed: 09/29/2017
• Published: 04/04/2019
• Est. Priority Date: 09/29/2017
• Status: Active Grant

• Current Assignee: Edison Vault, LLC
• Original Assignee: International Business Machines Corporation
• Inventors: Baptist, Andrew D., Cilfone, Bart R., Dhuse, Greg R., Hegde, Harsha, Leggette, Wesley B., Motwani, Manish, Resch, Jason K., Volvovski, Ilya, Wozniak, Ethan S.
• Granted Patent: US 10,585,748 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/9017 using directory or table look-up use of a directory or look-up table in file systems G06F16/13
• CPC Class Codes: G06F 2211/1007 Addressing errors, i.e. silent errors in RAID, e.g. sector slipping and addressing errors
• CPC Class Codes: G06F 2211/104 Metadata, i.e. metadata associated with RAID systems with parity
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A method begins by a computing device of a dispersed storage network (DSN) maintaining a queue of pending requests to access the DSN while new requests are added to the queue and executed requests are deleted from the queue. The method continues by the computing device determining, for each pending request in the queue, a prioritization score to produce a plurality of prioritization scores. The prioritization score is determined by determining an identity of a requestor associated with a pending request, obtaining a trust score based on the requestor'"'"'s identity, and obtaining a compliance score based on the requestor'"'"'s identity. The trust score indicates the requestor'"'"'s level of legitimate use of the DSN and the compliance score indicates the requestor'"'"'s level of compliance with DSN system requests. The method continues by the computing device executing pending requests of the queue in accordance with the plurality of prioritization scores.

Claims

1. A method comprises:

maintaining, by a computing device of a dispersed storage network (DSN), a queue of pending requests to access the DSN, wherein new requests are added to the queue and executed requests are deleted from the queue;

for each pending request in the queue, determining, by the computing device, a prioritization score to produce a plurality of prioritization scores, wherein the prioritization score is determined by;

determining a requestor'"'"' s identity of a requestor associated with a pending request of the pending requests;

obtaining a trust score based on the requestor'"'"' s identity, wherein the trust score indicates the requestor'"'"'s level of legitimate use of the DSN;

obtaining a compliance score based on the requestor'"'"'s identity, wherein the compliance score indicates the requestor'"'"'s level of compliance with DSN system requests; and

generating the prioritization score based on the trust score and the compliance score; and

executing, by the computing device, the pending requests of the queue in accordance with the plurality of prioritization scores.

2. The method of claim 1, wherein the determining the prioritization score further comprises:

obtaining a billing score based on the requestor'"'"' s identity, wherein the billing score indicates the requestor'"'"' s level of bill payment compliance; and

generating the prioritization score based on the trust score, the compliance score, and the billing score.

3. The method of claim 1, wherein the determining a requestor'"'"'s identity further comprises:

determining the requestor is a registered user device based on a registered user identifier; and

determining the requestor is an anonymous user device based on one or more of a generated unique identifier, a cookie, a network address, a session identifier, and an anonymous authentication.

4. The method of claim 1, wherein the obtaining the trust score comprises:

determining whether the pending request of the requestor is a first request to the DSN;

when the pending request of the requestor is the first request to the DSN, utilizing a default trust score as the trust score; and

when the pending request of the requestor is not the first request to the DSN, retrieving the trust score for the requestor.

5. The method of claim 1, wherein the obtaining the compliance score comprises:

determining whether the pending request of the requestor is a first request to the DSN;

when the pending request of the requestor is the first request to the DSN, utilizing a default compliance score as the compliance score; and

when the pending request of the requestor is not the first request to the DSN, retrieving the compliance score for the requestor.

6. The method of claim 1 further comprises:

after execution of the pending request, updating the compliance score based on the computer device and requestor system level interaction.

7. The method of claim 1 further comprises:

after execution of the pending request, updating the trust score based on the computer device processing of the pending request.

8. The method of claim 1, wherein executing the pending request comprises one of:

rejecting the pending request as a not allowed error;

rejecting the pending request as a payment required error;

rejecting the pending request as a system busy error;

throttling rate of processing the pending request;

delaying processing of the pending request;

routing the pending request to another computing device of the DSN;

processing the pending request; and

accelerated processing of the pending request.

9. The method of claim 1, wherein the determining the prioritization score further comprises:

obtaining a level of use score based on the requestor'"'"'s identity, wherein the level of use score indicates the requestor'"'"' s volume of requests, thrashing of data, and repeating of requests; and

generating the prioritization score based on the trust score, the compliance score, and the level of use score.

10. A computing device comprises:

an interface;

memory; and

a processing module, wherein the processing module is operable coupled to the memory and the interface, and wherein the processing module is operable to;

maintain a queue of pending requests to access a dispersed storage network (DSN), wherein new requests are added to the queue and executed requests are deleted from the queue;

for each pending request in the queue, determine a prioritization score to produce a plurality of prioritization scores, wherein the prioritization score is determined by;

determining a requestor'"'"'s identity of a requestor associated with a pending request of the pending requests;

obtaining a trust score based on the requestor'"'"'s identity, wherein the trust score indicates the requestor'"'"'s level of legitimate use of the DSN;

obtaining a compliance score based on the requestor'"'"'s identity, wherein the compliance score indicates the requestor'"'"'s level of compliance with DSN system requests; and

generating the prioritization score based on the trust score and the compliance score; and

execute the pending requests of the queue in accordance with the plurality of prioritization scores.

11. The computing device of claim 10, wherein the processing module is further operable to determine the prioritization score by:

obtaining a billing score based on the requestor'"'"'s identity, wherein the billing score indicates the requestor'"'"'s level of bill payment compliance; and

generating the prioritization score based on the trust score, the compliance score, and the billing score.

12. The computing device of claim 10, wherein the processing module is further operable to determine a requestor'"'"'s identity further by:

determining the requestor is a registered user device based on a registered user identifier; and

determining the requestor is an anonymous user device based on one or more of a generated unique identifier, a cookie, a network address, a session identifier, and an anonymous authentication.

13. The computing device of claim 10, wherein the processing module is further operable to obtain the trust score by:

determining whether the pending request of the requestor is a first request to the DSN;

when the pending request of the requestor is the first request to the DSN, utilizing a default trust score as the trust score; and

when the pending request of the requestor is not the first request to the DSN, retrieving the trust score for the requestor.

14. The computing device of claim 10, wherein the processing module is further operable to obtain the compliance score by:

determining whether the pending request of the requestor is a first request to the DSN;

when the pending request of the requestor is the first request to the DSN, utilizing a default compliance score as the compliance score; and

when the pending request of the requestor is not the first request to the DSN, retrieving the compliance score for the requestor.

15. The computing device of claim 10, wherein the processing module is further operable to:

after execution of the pending request, updating the compliance score based on the computer device and requestor system level interaction.

16. The computing device of claim 10, wherein the processing module is further operable to:

after execution of the pending request, updating the trust score based on the computer device processing of the pending request.

17. The computing device of claim 10, wherein the processing module is operable to execute the pending request by one of:

rejecting the pending request as a not allowed error;

rejecting the pending request as a payment required error;

rejecting the pending request as a system busy error;

throttling rate of processing the pending request;

delaying processing of the pending request;

routing the pending request to another computing device of the DSN;

processing the pending request; and

accelerated processing of the pending request.

18. The computing device of claim 10, wherein the processing module is operable to determine the prioritization score by:

obtaining a level of use score based on the requestor'"'"'s identity, wherein the level of use score indicates the requestor'"'"' s volume of requests, thrashing of data, and repeating of requests; and

generating the prioritization score based on the trust score, the compliance score, and the level of use score.