Entitled Data Cache Management

• US 20110093925A1
• Filed: 10/20/2009
• Published: 04/21/2011
• Est. Priority Date: 10/20/2009
• Status: Active Grant

• Current Assignee: Refinitiv US Organization, LLC (Refinitiv US Holdings, Inc.)
• Original Assignee: Thomson Reuters LLC (The Woodbridge Co. Ltd.)
• Inventors: Jornitski, Vladimir, Varadrajan, Srinivasan, Krishnamoorthy, Venkatanarayanan, Zucknovich, Stephen, Leisy, Jacques
• Granted Patent: US 8,397,066 B2
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices

Abstract

Systems and methods are disclosed for managing an entitled data cache. A data server may generate and send entitled data to a data cache server. The data cache server, a server that may be located nearer to the user within a data provider'"'"'s computer network, may receive and cache the entitled data. A permission server may store user'"'"'s permissions and transmit the user'"'"'s permissions to the data server and the data cache server. Upon receiving a request for data, the data cache server may retrieve the requested data from the cache and send a subset of the cached data which matches the user'"'"'s permissions to the user, without the need to request the data from the data server.

Claims

1. A computer server, comprising:

a memory; and

a processor configured to control the operation of the computer server, the processor configured to cause the computer server to;

receive entitled data from a data server, the entitled data having associated data permissions corresponding to at least one user authorized to access the computer server;

cache the entitled data, wherein caching the entitled data comprises storing the entitled data and a related identifier corresponding to the associated data permissions of the entitled data;

receive a first data request for at least a portion of the entitled data from a first user of the computer server;

retrieve user permissions corresponding to the first user of the computer server; and

determine if the first user'"'"'s permissions intersect with the associated data permissions of the cached entitled data, wherein said determining is based on the first user'"'"'s permissions and the related identifier corresponding to the associated data permissions of the entitled data,

wherein if the first user'"'"'s permissions intersect with the associated data permissions of the entitled data, the computer server is further configured to transmit at least a subset of the cached entitled data to the first user.

2. The apparatus of claim 1, wherein the computer server is further configured to determine if the cached entitled data is expired before transmitting the cached entitled data to the first user.

3. The apparatus of claim 1, wherein the computer server is further configured to:

receive a second data request from a second user of the computer server, wherein the second data request requests the same entitled data as the first data request received from the first user;

retrieve user permissions corresponding to the second user of the computer server, wherein the second user'"'"'s permissions with respect to the requested entitled data are different from the first user'"'"'s permissions; and

transmit a different subset of the cached entitled data to the second user in response to the second user request.

4. The apparatus of claim 1, wherein the computer server is further configured to subscribe to a publish server to receive updates to the cached entitled data, when the cached entitled data changes.

5. The apparatus of claim 4, wherein the computer server is configured to receive updated data from the publish server prior to the expiration of the cached data.

6. The apparatus of claim 1, wherein the computer server is further configured to:

receive a second data request from the first user of the computer server, wherein the second data request requests the same entitled data as the first data request;

determine that the first user'"'"'s permissions have changed subsequent to receiving the first data request; and

transmit a different subset of the cached entitled data to the first user.

7. A method comprising:

receiving entitled data from a data server, the entitled data having associated data permissions corresponding to at least one user authorized to access the computer server;

caching the entitled data, wherein caching the entitled data comprises storing the entitled data and a related identifier corresponding to associated data permissions of the entitled data;

receiving a first request for at least a portion of the entitled data from a first user;

determining if the first user'"'"'s permissions intersect with the associated data permissions of the cached entitled data, wherein said determining is based on the first user'"'"'s permissions and the related identifier corresponding to the associated data permissions of the entitled data,

if the first user'"'"'s permissions intersect with the associated data permissions of the entitled data, transmitting at least a subset of the cached entitled data to the first user.

8. The method of claim 7, further comprising:

determining if the cached entitled data is expired before transmitting the cached entitled data to the first user.

9. The method of claim 7, wherein caching the entitled data comprises storing the entitled data with a cache signature corresponding to the associated data permissions of the entitled data.

10. The method of claim 9, wherein the cache signature includes information corresponding to the user request.

11. The method of claim 7, further comprising:

subscribing to a publish server to receive updated data;

receiving asynchronous data updates for the entitled data from the publish server; and

replacing the cached entitled data with the updated entitled data.

12. The method of claim 8, further comprising:

generating a cache signature by hashing the first request.

13. The method of claim 7, wherein determining if a user'"'"'s permissions intersect with the data permissions includes requesting and receiving the user'"'"'s permissions from a permission server.

21. The method of claim 9, wherein caching the entitled data comprises storing the entitled data with an Entitlement Token corresponding to the associated data permissions of the entitled data.

22. The method of claim 21, wherein Entitlement Token allows grouping of users with similar permissions to access the same cached entitled data.

23. The method of claim 11, wherein notification of updates of the cache can update multiple caches arranged in a hierarchy and stored on the data cache server.

14. A method comprising:

receiving a first data request, the first data request corresponding to a first user having first user permissions on a computer system;

determining if a first response data corresponding to the first data request and corresponding to the first user permissions is stored in a local data cache;

if the first response data is stored in the local data cache, sending the first user the response data;

receiving a second data request corresponding to a second user having second user permissions on the computer system, the second data request being the same as the first data request, wherein the second user permissions are different from the first user permissions;

determining if a second response data corresponding to the second user request and corresponding second user permissions is stored in a local data cache;

if the second response data is stored in the local data cache, sending the second user the second response data, wherein the second response data is different than the first response data.

15. The method of claim 14, further comprising:

if the data is not cached, requesting data corresponding to either the first user'"'"'s request or the second user'"'"'s request from a data and caching the data received from the data server.

16. The method of claim 14, further comprising:

verifying the expiration of the cached data is prior to sending the subset of the cached data, and sending the subset of cached data to one of the first or second users only if the cached data is not expired.

17. One or more computer readable media storing computer readable instructions that, when executed, cause a processor to perform a method comprising:

receiving a first data request, the first data request corresponding to a first user having first user permissions on a computer system;

determining if a first response data corresponding to the first data request and corresponding to the first user permissions is stored in a local data cache;

if the first response data is stored in the local data cache, sending the first user the response data;

receiving a second data request corresponding to a second user having second user permissions on the computer system, the second data request being the same as the first data request, wherein the second user permissions are different from the first user permissions;

determining if a second response data corresponding to the second user request and corresponding second user permissions is stored in a local data cache;

if the second response data is stored in the local data cache, sending the second user the second response data, wherein the second response data is different than the first response data.

18. The method of claim 17, further comprising:

if the data is not cached, requesting data corresponding to either the first user'"'"'s request or the second user'"'"'s request from a data and caching the data received from the data server.

19. The method of claim 17, further comprising:

verifying the expiration of the cached data is prior to sending the subset of the cached data, and sending the subset of cached data to one of the first or second users only if the cached data is not expired.

20. The method of claim 17, further comprising:

receiving a third data request corresponding to the first user, the third data request requesting the same data as the first data request;

determining the first user'"'"'s permissions have changed subsequent to receiving the first data request;

sending the first user response data different from the response data sent to the first user in response to the first data request.