System and method for preserving consumer choice

• US 9,313,279 B2
• Filed: 02/20/2014
• Issued: 04/12/2016
• Est. Priority Date: 09/19/2006
• Status: Active Grant

• Current Assignee: Mercury Kingdom Assets Limited
• Original Assignee: Mercury Kingdom Assets Limited
• Inventors: Wilson, Joseph G.
• Primary Examiner(s): Patel, Parth
• Assistant Examiner(s): Chang, Kai
• Application Number:
  US14/185,338
• Publication Number:
  US 20140172963A1
• Time in Patent Office: 782 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/306 User profiles

Abstract

Methods and systems for preserving user attribute data by way of managing and synchronizing redundant storage locations.

Claims

1. A method comprising:

accessing stored first user attribute data associated with an internet browser at a first data location on a client and stored second user attribute data associated with the internet browser at a second data location on a server, the first user attribute data having a first recency date indicating a time at which the first user attribute data was last updated and the second user attribute data having a second recency date indicating a time at which the second user attribute data was last updated;

receiving a request to view a webpage associated with the first user attribute data and the second user attribute data from the client at the server to access a web page associated with the server, said webpage calling a third party service;

determining that the first user attribute data, the second user attribute data or both are out of date based at least in part on the first recency date and the second recency date; and

synchronizing, via the third party service, the first user attribute data at the first data location and the second user attribute data at the second data location, in response to receiving the request to view the webpage and determining the first user attribute data, the second user attribute data or both are out of date.

2. The method of claim 1, further comprising determining synchronization of the first user attribute data and the second user attribute data responsive to receipt of an if-modified-since call.

3. The method of claim 2, wherein the determination that the first user attribute data is out of date is based at least in part a determination that the first user attribute data differs from the second user attribute data.

4. The method of claim 1, wherein the first user attribute data and the second user attribute data pertains to an identity of the client.

5. The method of claim 1, wherein the first user attribute data and the second user attribute data pertains to client-side opt out choices with respect to communicating with a network associated with the server.

6. The method of claim 1, wherein the first user attribute data is stored as at least one of the following:

a browser cookie;

a Java Applet;

or

a Flash Shared Object.

7. The method of claim 1, wherein the first user attribute data is stored in at least one of the following:

a browser cache;

or

a random-access-memory.

8. The method of claim 1, further comprising updating the first recency date, the second recency date or both.

9. A non-transitory computer readable program code stored on a computer useable medium readable by a digital processing apparatus to perform steps comprising:

maintaining user attribute data associated with an internet browser at a first data location associated with a client and at a second data location associated with the client;

receiving, at the client, a first transmission containing instruction code from a third party operatively configured to cause the client to determine synchronicity between the user attribute data stored on the client, the user attribute data stored on the server, and user attribute data associated with the internet browser; and

synchronizing the user attribute data stored at the first data location and at the second data location with the user attribute data associated with the internet browser.

10. The non-transitory computer readable program code of claim 9, wherein the user attribute data stored at the client is stored as at least one of the following:

a browser cookie;

a Java Applet;

or

a Flash Shared Object.

11. The non-transitory computer readable program code of claim 9, wherein the user attribute data stored at the client is stored in at least one of the following:

a browser cache;

or

a random-access-memory.

12. The non-transitory computer readable program code of claim 9, wherein the user attribute data pertains to client-side opt out choices associated with a network.

13. The non-transitory computer readable program code of claim 9, wherein the user attribute data pertains to an identity of the client.

14. A method comprising:

receiving a request from a client at a server to view a webpage;

determining that cache data exists on the client, the cache data having an associated cache recency date;

determining that first party cookies exist, the first party cookies having an associated first party recency date;

determining that third party cookies exist associated with the webpage, the third party cookies having an associated third party recency date;

determining that the third party recency date is greater than the first party recency date;

determining that the third party recency date is greater than the cache recency date; and

providing data associated with the third party cookies to the client.

15. The method of claim 14, further comprising identifying the third party cookies as an authoritative storage location, in response to determining that the third party recency date is greater than the cache recency date.

16. The method of claim 14, further comprising synchronizing the cache data with the data associated with the third party cookies.

17. The method of claim 14, wherein the third party cookies include at least one user attribute.

18. The method of claim 14, wherein the third party cookies are associated with at least one advertisement.

19. The method of claim 14, wherein the data associated with the third party cookies pertains to a client-side opt out choice.