Geopartitioned data caching

• US 10,432,737 B2
• Filed: 10/12/2017
• Issued: 10/01/2019
• Est. Priority Date: 10/12/2017
• Status: Active Grant

• Current Assignee: Cadent LLC
• Original Assignee: Engine Media, LLC
• Inventors: Ashner, Louis Clayton, Roach, John Patrick, Schwab, Mickey Alexander, Zacharski, Michael
• Primary Examiner(s): Bekerman, Michael
• Assistant Examiner(s): Snider, Scott
• Application Number:
  US15/782,569
• Publication Number:
  US 20190116230A1
• Time in Patent Office: 719 Days
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 12/0848 Partitioned cache, e.g. separate instruction and operand caches
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 9/00 Arrangements for program control, e.g. control units program control for peripheral devices G06F13/10
• CPC Class Codes: G06Q 30/0261 based on user location
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/21 for social networking applications

Abstract

Geopartitioned data caching is disclosed. For example, a data source is connected over a network to a geographically remote data cache in communication with a load balancer service. A processor on the data cache executes to receive, from the data source, a plurality of data entries in the data cache, where the plurality of data entries is selected based on a geographical region of the data cache. A data request for a data entry of the plurality of data entries is received from the load balancer service, where a requestor of the data request is in a second geographical region proximately located with the data cache. The data entry is sent to the load balancer service, where the load balancer service forwards the data entry to a receiver.

Claims

1. A system of geopartitioned data caching, the system comprising:

a data source connected over a network to a first data cache of a plurality of data caches, wherein the first data cache is geographically remote from the data source, and the first data cache stores a first plurality of data entries selected based on a first geographical region of the first data cache; and

a host node with one or more processors and a memory, the host node hosting;

the first data cache; and

a first load balancer service configured to communicate with a nearest data cache among the plurality of data caches, and the first data cache is the nearest data cache to the first load balancer service, wherein the first load balancer service is configured to send advertisement bid requests to advertisers based on receiving advertisement requests;

wherein the one or more processors on the host of the first data cache execute to;

receive, from the first load balancer service, a first data request for a first data entry associated with a first advertisement bid request, wherein the first data entry is available in the data source, and a first requestor of the first data request is in a second geographical region proximately located with the first data cache;

query, based on the first data request, the first data cache to determine whether the first data cache includes the first data entry;

responsive to determining that the first data cache lacks the first data entry, reject, by the first data cache, the first data request, and after rejecting the first data request, retrieve by the first data cache, the first data entry from the data source; and

responsive to the first data cache rejecting the first data request, cancel, by the first load balancer service, the first advertisement bid request to a first advertiser.

2. The system of claim 1, wherein the data source stores a second plurality of data entries, and the first plurality of data entries is a subset of the second plurality of data entries.

3. The system of claim 1, wherein the first data entry includes a first profile of the first requestor, and a second data entry includes a second profile of the second requestor.

4. The system of claim 3, wherein the one or more processors execute further to:

receive, from the first load balancer service, a second data request for the second data entry, wherein a second requestor of the second data request is located in the second geographical region and the second data entry is stored in the first data cache; and

send the second data entry to the first load balancer service, wherein the first load balancer service incorporates the second data entry into at least one advertisement bid request to at least one advertiser.

5. The system of claim 1, wherein the first data cache sends the first data entry to the first load balancer service upon receiving a second data request for the first data entry from the first requestor.

6. The system of claim 5, wherein the first load balancer service incorporates the first data entry in a plurality of advertisement bid requests associated with the second data request, sent to a respective plurality of advertisers.

7. The system of claim 6, wherein the plurality of advertisement bid requests is generated based on a web content retrieved by the first requestor through a network accessible device.

8. The system of claim 7, wherein a second advertiser of the plurality of advertisers is selected to receive a second advertisement bid request of the plurality of advertisement bid requests based on the second advertiser being located in a third geographical region proximately located with the first data cache.

9. The system of claim 1, wherein a previous connection by the first requestor to a second load balancer service was from a third geographical region proximately located with a second data cache which stored the first data entry, and the second data cache is geographically separated from the first data cache.

10. The system of claim 1, wherein the first load balancer service cancels a plurality of advertisement bid requests based on the data cache rejecting the first data request.

11. The system of claim 1, wherein a second load balancer service is collocated with a second data cache.

12. The system of claim 1, wherein the data source is associated with an alerting service and the alerting service is at least one of a detection device of geographically impacting events and a reporting service of geographically impacting events.

13. The system of claim 12, wherein the alerting service reports an imminent geographically impacting event affecting the first geographical region, and the first load balancer service disables requests to the first data cache.

14. The system of claim 13, wherein a second data cache in a third geographical region remote from the first geographical region, a third data cache in a fourth geographical region remote from the first geographical region, and a fourth data cache in a fifth geographical region remote from the first geographical region are sent the first plurality of data entries by the data source.

15. The system of claim 14, wherein a second data request for the first data entry is fulfilled by one of the second data cache, the third data cache, and the fourth data cache.

16. The system of claim 15, wherein the second data request originates from the first load balancer service in the first geographical region.

17. The system of claim 15, wherein the second data request originates from a sixth geographical region separate from the first geographical region, the third geographical region, the fourth geographical region, and the fifth geographical region.

18. The system of claim 14, wherein the first data entry includes a first profile of the first requestor, and the first profile is loaded to at least one of the second data cache, the third data cache, and the fourth data cache.

19. The system of claim 18, wherein the first profile is sent with a second advertisement bid request from at least one of the third geographical region, the fourth geographical region, and the fifth geographical region to a plurality of advertisers, and the first requestor receives an advertisement.

20. The system of claim 1, wherein the first requestor previously accessed a second load balancer service associated with a second data cache and a first copy of the first data entry in the second data cache was updated with a first change, the first data cache retrieves a second copy of the first data entry from the data source prior to the data source being updated with the first change, and the first load balancer service incorporates the non-updated second copy of the first data entry into a second advertisement bid request.

21. The system of claim 20, wherein the first requestor responds to an advertisement displayed to the first requestor based on the second advertisement bid request, resulting in a second change being recorded to the second copy of the first data entry.

22. The system of claim 21, wherein the first data entry in the data source is updated with both the first change and the second change after both changes are made.

23. A method of geopartitioned data caching, the method comprising:

receiving, from a data source, a first plurality of data entries in a first data cache, wherein the first plurality of data entries is selected based on a first geographical region of the first data cache and the first data cache is geographically remote from the data source, and wherein a load balancer service hosted on a same host node as the first data cache is configured to communicate with a nearest data cache among the plurality of data caches, and the first data cache is the nearest data cache to the load balancer service;

receiving, from the load balancer service, a first data request for a first data entry associated with a first advertisement bid request, wherein the load balancer service is configured to send advertisement bid requests to advertisers based on receiving advertisement requests, wherein the first data entry is available in the data source, and a first requestor of the first data request is in a second geographical region proximately located with the first data cache;

querying, based on the first data request, the first data cache to determine whether the first data cache includes the first data entry;

responsive to determining that the first data cache lacks the first data entry, canceling, by the load balancer service, the first advertisement bid request to a first advertiser and retrieving, by the first data cache, the first data entry from the data source.

24. The method of claim 23, wherein the first data entry includes a first profile of the first requestor, and a second data entry includes a second profile of a second requestor, the method further comprising:

receiving, from the load balancer service, a second data request for a second data entry, wherein the second requestor of the second data request is located in the second geographical region and the second data entry is stored in the first data cache;

sending the second data entry to the load balancer service, wherein the load balancer service incorporates the second data entry into at least one advertisement bid request to at least one advertiser.

25. The method of claim 24, wherein the first data cache sends the first data entry to the load balancer service upon receiving a third data request for the first data entry from the first requestor.

26. The method of claim 24, wherein a previous connection by the first requestor to the load balancer service was from a third geographical region proximately located with a second data cache, and the second data cache is geographically separated from the first data cache.

27. The method of claim 25, wherein the load balancer service includes the first profile in a plurality of advertisement bid requests sent to a respective plurality of advertisers and a second advertiser of the plurality of advertisers is selected to receive a second advertisement bid request of the plurality of advertisement bid requests based on the second advertiser being located in a third geographical region proximately located with the first data cache.

28. The method of claim 23 further comprising:

receiving, from an alerting service associated with the data source, a report of an imminent geographically impacting event affecting the first geographical region; and

disabling requests to the first data cache.

29. The method of claim 23 further comprising:

sending, by the data source, the first plurality of data entries to a second data cache in a third geographical region remote from the first geographical region, a third data cache in a fourth geographical region remote from the first geographical region, and a fourth data cache in a fifth geographical region remote from the first geographical region.

30. The method of claim 29 further comprising:

fulfilling, by one of the second data cache, the third data cache, and the fourth data cache, a second data request for the first data entry.

31. The method of claim 29, wherein the first data entry includes a first profile of the first requestor, the first profile is loaded to at least one of the second data cache, the third data cache, and the fourth data cache, and wherein the first profile is sent with a second advertisement bid request from at least one of the third geographical region, the fourth geographical region, and the fifth geographical region to a plurality of advertisers resulting in the first requestor receiving an advertisement.

32. A computer-readable non-transitory storage medium storing executable instructions of geopartitioned data caching, which when executed by a computer system, cause the computer system to:

receive, from a data source, a first plurality of data entries in a first data cache, wherein the first plurality of data entries is selected based on a first geographical region of the first data cache and the first data cache is geographically remote from the data source, and wherein a load balancer service hosted on a same host node as the first data cache is configured to communicate with a nearest data cache among the plurality of data caches, and the first data cache is the nearest data cache to the load balancer service;

receive, from the load balancer service hosted on a same host node as the first data cache, a first data request for a first data entry associated with a first advertisement bid request, wherein the load balancer service is configured to send advertisement bid requests to advertisers based on receiving advertisement requests, wherein the first data entry is available in the data source, and a first requestor of the first data request is in a second geographical region proximately located with the first data cache;

query, based on the first data request, the first data cache to determine whether the first data cache includes the first data entry;

responsive to determining that the first data cache lacks the first data entry, cancel, by the load balancer service, the first advertisement bid request to a first advertiser and retrieve, by the first data cache the first data entry from the data source.