User information coordination across multiple domains
First Claim
1. A method comprising:
- employing a first web server in a first DNS domain, and a second web server in a second DNS domain, wherein the first web server uses a first user tracking mechanism to collect client information and stores the client information as a client record in a database;
the first web server directing a client to access a resource at the second Web-Server;
said resource encapsulating information about a location of the client record in the database;
the second web server decapsulating the location and retrieving the client record from the database; and
the second web server using the client record in conjunction with a second user tracking mechanism.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods and apparatus for sharing user information across the Internet, trackers and servers, in multiple domains. User-tracking mechanism deploy cookies placed in web-browser to track an user preference, or use URL rewriting techniques. In an embodiment, a first web site desiring to coordinate cookie information with a second web site creates a cookie in the browser, and stores information related to the information in the cookie in a cookie coordinator database. It directs the client to access a resource at the second web site. The URL of the resource on the second web site encapsulates the information about the location of the client record in a cookie coordinator database. The second web site places its own cookie on the client browser, and coordinates its information with the information in the cookie of the first web-browser by accessing the client record in the cookie coordinator database.
309 Citations
22 Claims
-
1. A method comprising:
-
employing a first web server in a first DNS domain, and a second web server in a second DNS domain, wherein the first web server uses a first user tracking mechanism to collect client information and stores the client information as a client record in a database;
the first web server directing a client to access a resource at the second Web-Server;
said resource encapsulating information about a location of the client record in the database;
the second web server decapsulating the location and retrieving the client record from the database; and
the second web server using the client record in conjunction with a second user tracking mechanism. - View Dependent Claims (12, 15)
-
-
2. A method as recited in 1, wherein the first and the second user tracking mechanisms use cookies for storing the user client information.
-
3. A method as recited in 1, wherein the first web server authenticates the client, and the client record includes user authentication data enabling the second web server to use a common sign-on with the sign-on of the first web server.
-
4. A method as recited in 1, wherein the first web server stores within the client record at least one parameter which determines at least one characteristic of at least one page to be sent to the client by the second web server.
-
5. A method as recited in 1, wherein said at least one parameter includes at least one user preference.
-
6. A method as recited in 5, wherein said at least one user preference is related to at least one detected purchasing habit.
-
7. A method comprising:
-
employing a first web server in a first DNS domain, and a second web server in a second DNS domain, enabling said first and second web servers to share cookie information; and
coordinating cookies across said first and second domains. - View Dependent Claims (8, 9, 10, 13, 16)
-
-
11. An apparatus comprising:
-
means for employing a first web server in a first DNS domain, and a second web server in a second DNS domain, wherein the first web server uses a first user tracking mechanism to collect client information and stores the client information as a client record in a database;
means for the first web server directing a client to access a resource at the second web server;
means for said resource encapsulating information about a location of the client record in the database;
means for the second web server decapsulating the location and retrieving the client record from the database; and
means for the second web server using the client record in conjunction with a second user tracking mechanism. - View Dependent Claims (17)
-
-
14. A method comprising:
-
employing a first user tracker in a first domain, and a second user tracker in a second domain, wherein the first user tracker uses a first user tracking mechanism to collect client information and stores the client information as a client record in a database;
the first user tracker directing a client to access a resource at the second user tracker;
said resource encapsulating information about a location of the client record in the database;
the second user tracker decapsulating the location and retrieving the client record from the database; and
the second user tracker using the client record in conjunction with a second user tracking mechanism.
-
-
18. A method comprising:
-
employing a first web server in a first DNS domain, and a second web server in a second DNS domain, wherein the first web server maintains a first private cookie at a browser and the second web server maintains a second private cookie at the browser;
accessing a cookie coordinator when the first private cookie is received by the first web-server,; and
mapping a first identity in the first private cookie and a second identity in the second private cookie to a single identity common across the multiple domains. - View Dependent Claims (19, 20)
-
-
21. An apparatus comprising:
-
a web server interface to interface with a first web server in a first DNS domain and to interface a second web server in a second DNS domain;
said first web server having;
a first user tracker to collect client information and stores client information as a client record in a cookie coordinator database;
a redirector for the first web server to direct a client to access a resource at the second web server;
an encapsulator for said resource to encapsulate information about a location of the client record in the database; and
said second web server having;
a second user tracker for the second web server to use the client record in conjunction with a second user tracking mechanism; and
a decapsulator for the second web server to decapsulate a location and retrieving the client record from the database. - View Dependent Claims (22)
-
Specification