SERVER ARCHITECTURE AND METHODS FOR STORING AND SERVING EVENT DATA

• US 20090276407A1
• Filed: 07/13/2009
• Published: 11/05/2009
• Est. Priority Date: 07/02/2003
• Status: Active Grant

• Current Assignee: Ruben Ortega, Taylor N Van Vleet, Udi Manber, Yu-Shan Fung
• Original Assignee: Ruben Ortega, Taylor N Van Vleet, Udi Manber, Yu-Shan Fung
• Inventors: Manber, Udi, Van Vleet, Taylor N., Ortega, Ruben, Fung, Yu-Shan
• Granted Patent: US 7,895,325 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

An event history server system stores event data descriptive of user-specific events that occur in browsing sessions of users. A query interface of the event history server system enables applications to selectively retrieve the event data based on various event parameters such as event type, event time of occurrence, and user identifier. The applications may, for example, include one or more personalization applications that generate personalized content for users.

Claims

1. A machine-implemented method of recording and providing access to event data regarding events that occur during browsing sessions of users, the method comprising:

receiving event data over a network from one or more machines that service page requests from user computing devices, said event data reflective of user-specific events that occur during browsing sessions of each of a plurality of users;

storing the event data in a database such that each event is represented by a respective event object that is separately retrievable from the database;

receiving queries for event data over a network from applications, said queries generated in accordance with a query interface that enables the applications to selectively retrieve stored event data based on at least event type, event time of occurrence, and user identifier; and

processing the queries via execution of code by a physical server, wherein processing the queries comprises identifying, and retrieving from the database, particular event objects that are responsive to the queries, and returning responsive event data to the applications.

2. The method of claim 1, further comprising, by execution of at least one of said applications by a machine, using the responsive event data to personalize web pages for users.

3. The method of claim 2, wherein using the event data to personalize web pages for users comprises using retrieved event data regarding past search activities of a user to personalize a search results page for a user.

4. The method of claim 1, wherein the method comprises storing the event data in the database, and providing query-based access to the event data via the query interface, substantially in real time.

5. The method of claim 1, wherein receiving event data over a network comprises receiving the event data from each of a plurality of web server machines substantially as corresponding events occur.

6. The method of claim 1, wherein storing the event data comprises, for a particular event, storing an event object that includes at least an event type identifier, an event value, and a time stamp.

7. The method of claim 1, wherein the method is performed by an event history server system that comprises a physical cache layer server and a physical storage layer server, and the method further comprises:

caching the event data associated with particular users on the cache layer server during browsing sessions of said particular users; and

by execution of query processing code by the cache layer server, using the cached event data to service at least some of the queries for event data.

8. The method of claim 7, wherein the event history server system comprises a plurality of physical cache layer servers, and the method comprises partitioning the cache layer servers by browse session identifier, such that each cache layer server caches event data for a respective subset of browse sessions.

9. The method of claim 8, further comprising sending update messages from each of the cache layer servers to the storage layer server to enable the storage layer server to maintain a record of events that occur during said browsing sessions.

10. The method of claim 1, wherein processing the queries for event data comprises processing a query of the form “

has User X accessed URL Y?”

11. The method of claim 1, wherein processing the queries for event data comprises processing a query of the form “

when has User X accessed URL Y?”

12. The method of claim 1, wherein storing the event data comprises, for a particular event associated with a display element on a page accessed by a user, storing a corresponding event object indicating at least:

a type of the display element and a value associated with the display element.

13. The method of claim 1, wherein storing the event data comprises, for a mouse-over event in which a user hovers a mouse over a display element on a page, storing a corresponding event object that (1) identifies the event as a mouse-over event, and (2) includes information about the display element.

14. The method of claim 1, wherein storing the event data comprises, for an impression event in which a particular display element is included in a dynamically generated page served to a user, storing a corresponding event object that (1) identifies the event as an impression event, and (2) includes information about the display element.

15. The method of claim 1, wherein storing the event data comprises, for an event in which a user selects a search result URL, storing an event object that contains text of the URL and an associated display title.

16. An event history server system, comprising:

a physical server comprising a database that stores event objects reflective of user-specific events of a plurality of users, each event object corresponding to, and containing event data associated with, a respective user-specific event occurring during a browsing session of a corresponding user, said user-specific events reported to the event history server system over a network by at least one machine that services page requests from computing devices of said users, each event object being separately retrievable from the database; and

service code that runs on the physical server and processes queries for event data, said queries received by the event history server system over a network from applications, said queries conforming to a query interface embodied in said service code, said query interface enabling the applications to selectively retrieve the event data based on at least event type, event time of occurrence, and user identifier, said service code additionally operative to cause new event objects to be written to the database in response to the at least one machine reporting new user-specific events to the event history server system.

17. The event history server system of claim 16, wherein the query interface additionally enables the applications to retrieve the event data based on types of display elements associated with particular events.

18. The event history server system of claim 16, wherein the physical server is programmed, via said service code, to respond to a query from an application by identifying, and retrieving from said database, particular event objects that are responsive to the query.

19. The event history server system of claim 16, further comprising an application that retrieves event data from the event history server system via the query interface, and uses the retrieved event data to personalize pages for users.

21. The event history server system of claim 16, wherein the event history server system is operative to make the event data available to the applications via said query interface substantially in real time.

22. The event history server system of claim 16, further comprising a plurality of web server machines that report user-specific events to the event history server system substantially in real time for recordation.

23. The event history server system of claim 16, further comprising a physical cache layer server that is programmed to cache the event data associated with particular users during browsing sessions of said particular users;

and is additionally programmed to use the cached event data to service at least some of the queries from the applications.

24. The event history server system of claim 16, wherein the event history server system further comprises a plurality of physical cache layer servers, each of which is operative to cache, and provide query-based access to, event data of a different respective subset of the users.

25. The event history server system of claim 16, wherein the service code is operative to accept and respond to queries of the form “

has User X accessed URL Y?”

26. The event history server system of claim 16, wherein the service code is operative to accept and respond to queries of the form “

when has User X accessed URL Y?”

27. The event history server system of claim 16, wherein the physical server is programmed to store in said database, for a particular event associated with a display element on a page accessed by a user, a corresponding event object indicating at least:

a type of the display element and a value associated with the display element.

28. The event history server system of claim 16, wherein the physical server is programmed to store in said database, for a mouse-over event in which a user hovers a mouse over a display element on a page, a corresponding event object that (1) identifies the event as a mouse-over event, and (2) includes information about the display element.

29. The event history server system of claim 16, wherein the physical server is programmed to store in said database, for an impression event in which a particular display element is included in a dynamically generated page served to a user, a corresponding event object that (1) identifies the event as an impression event, and (2) includes information about the display element.

30. The event history server system of claim 16, wherein the physical server is programmed to store in said database, for an event in which a user selects a search result URL from a search results page, an event object that contains text of the URL and an associated display title.

20. The event history server system of claim 1816, wherein the retrieved event data is descriptive of past search activities of users, and the application is operative to use the retrieved event data to personalize search results pages for the users such that the search results pages reflect the past searching activities of corresponding users.

31. A computer-implemented method of storing and providing access to event data, the method comprising:

recording, on an event history server system that comprises at least one physical server, user-specific events that occur as part of a browsing session of a user such that each event is recorded as a respective event object that is separately retrievable via a query interface, said query interface enabling event objects to be retrieved by at least event type, event time of occurrence, and user identifier; and

during said browsing session;

making said event objects available to a plurality of applications on a network via said query interface, such that the applications can send queries to the event history server system to selectively retrieve event data associated with the user; and

with at least one of said applications, generating personalized page content for the user based on event data retrieved from the event history server system via the query interface.

32. The method of claim 31, wherein recording the user-specific events comprises persistently storing the event objects on a physical storage layer server of said event history server system, and caching said event objects on a physical cache layer server of said event history server system.

33. The method of claim 32, further comprising, by execution of query processing code by the physical cache layer server, responding to at least some of said queries from the applications.

34. The method of claim 31, wherein the user-specific events are recorded on the event history server system in response to said events being reported to the event history server system over a network by at least one web server machine.

35. The method of claim 31, wherein recording the user-specific events comprises, for a particular event associated with a display element on a page accessed by the user, storing a corresponding event object indicating at least:

a type of the display element and a value associated with the display element.

36. The method of claim 31, wherein recording the user-specific events comprises, for a mouse-over event in which a user hovers a mouse over a display element on a page, storing a corresponding event object that (1) identifies the event as a mouse-over event, and (2) includes information about the display element.

37. The method of claim 31, wherein recording the user-specific events comprises, for an impression event in which a particular display element is included in a dynamically generated page served to the user, storing a corresponding event object that (1) identifies the event as an impression event, and (2) includes information about the display element.

38. The method of claim 31, wherein recording the user-specific events comprises, for an event in which the user selects a search result URL on a search results page, storing an event object that contains text of the URL and an associated display title.