DATA CACHING BASED ON SOCIAL CHARACTERISTICS OF USERS

• US 20150220628A1
• Filed: 12/18/2012
• Published: 08/06/2015
• Est. Priority Date: 12/18/2012
• Status: Active Grant

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Li, Qi, Song, Xuefeng, Zhong, Haoqing
• Granted Patent: US 10,235,451 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/35 Clustering; Classification
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

In one example embodiment, a computer-implemented method is provided for caching data from an online resource based on social characteristics of users using the data. The method includes dividing the users into one or more social groups according to the social characteristics, and creating one or more cache databases corresponding to the one or more social groups, wherein data in each of the one or more cache databases are indexed by one or more user attributes identifying social characteristics of user used the data.

Claims

1. A method to cache data from an online resource based on social characteristics of users using the data, comprising:

dividing the users into one or more social groups according to the social characteristics; and

creating one or more cache databases corresponding to the one or more social groups,

wherein data in each of the one or more cache databases are indexed by one or more user attributes identifying social characteristics of users who have used the data.

27. The method of claim 1, wherein various ones of the one or more user attributes are static.

28. The method of claim 1, wherein various ones of the one or more user attributes are dynamic.

2. A method to cache data, comprising:

receiving a request for data from a user of the data, wherein the request is accompanied by one or more user attributes identifying the user'"'"'s relationship with a social group;

identifying a cache database based on the one or more user attributes;

querying the cache database for requested data; and

upon receiving a message indicating the requested data is not stored in the cache database;

querying a database server for the requested data,

receiving the requested data from the database server,

attaching the one or more user attributes with the requested data, and

storing into the cache database the request for data and the requested data attached with the one or more user attributes.

3. The method of claim 2, wherein storing the requested data into the cache database comprises:

associating the requested data with a count of accesses of the requested data by users from a same social group.

4. The method of claim 3, wherein the requested data is ranked in the cache database by the value of the count.

5. The method of claim 4, wherein data with a smallest count value in the cache database is replaced first.

6. The method of claim 2, wherein the cache database executes the query for the requested data by searching for the requested data in the cache database according to the one or more user attributes accompanying the request.

7. The method of claim 2, wherein data in the cache database is refreshed at a refresh frequency that is based on a volume of queries that the cache database receives.

8. The method of claim 7, wherein a threshold is set for the volume of queries that the cache database receives,

wherein further, the refresh frequency decreases when the volume of queries that the cache database receives exceeds the threshold,

wherein further still, the refresh frequency increases when the volume of queries that the cache database receives is below the threshold.

9. The method of claim 2, wherein various ones of the one or more user attributes are static.

10. The method of claim 2, wherein various ones of the one or more user attributes are dynamic.

11. (canceled)

12. (canceled)

13. (canceled)

14. (canceled)

15. (canceled)

16. (canceled)

17. (canceled)

18. A system to retrieve data, comprising:

a database server that is configured to store the data;

one or more cache databases that are each respectively configured to cache at least portions of the data for a group of users of the data,

wherein each of the respective groups of users of the data share one or more characteristics, and

wherein each of the respective portions of the data are tagged with one or more user attributes that are configured to identify the users of the data; and

a web server that is configured to;

receive, from one of the users of the data, a request for data that is accompanied by one or more of the user attributes,

identify one of the one or more cache databases in which at least some of the respective portions of the data cached therein are tagged with the one or more user attributes that accompany the request for data, and

query the one or more identified cache database for the requested data.

19. The system of claim 18, wherein the web server is further configured to receive the requested data from one or more of the identified cache databases for transmission to the user.

20. The system of claim 18, wherein, upon receiving a message indicated that the requested data is not cached in the identified one or more cache databases, the web server is further configured to:

query the database server for the requested data;

receive the requested data from the database server;

attach the one or more user attributes that accompanied the request for data to the requested data; and

cache the requested data in one or more of the cache databases in which respective portions of the data are tagged with the one or more user attributes that accompanied the request for data.

21. The system of claim 18, wherein the portions of data cached in the one or more cache databases is refreshed at a refresh frequency that increases and decreases in accordance with a volume of queries received at the respective cache database.

22. The system of claim 21,

wherein, a threshold is set for the volume of queries,

wherein further, the refresh frequency decreases when the volume of queries exceeds the threshold, and

wherein further, the refresh frequency increases when the volume of queries falls below the threshold.

23. The system of claim 20, wherein the portions of data cached in the one or more cache databases is further associated with a count of accesses.

24. The system of claim 23, wherein replacement of the portions of data starts with those of the portions of data having a lowest count of accesses.

25. The system of claim 18, wherein various ones of the one or more user attributes are static.

26. The system of claim 18, wherein various ones of the one or more user attributes are dynamic.