Server architecture and methods for storing and serving event data
First Claim
Patent Images
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;
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.
0 Assignments
0 Petitions
Accused Products
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.
-
Citations
35 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; 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. 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; wherein the physical server is operative to make the event data available to the applications via said query interface substantially in real time, and 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. - View Dependent Claims (16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27)
-
-
28. 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 substantially in real time 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. - View Dependent Claims (29, 30, 31, 32, 33, 34, 35)
-
Specification