US20110208711A1 - Search annotation and personalization services - Google Patents

Search annotation and personalization services Download PDF

Info

Publication number
US20110208711A1
US20110208711A1 US13/098,191 US201113098191A US2011208711A1 US 20110208711 A1 US20110208711 A1 US 20110208711A1 US 201113098191 A US201113098191 A US 201113098191A US 2011208711 A1 US2011208711 A1 US 2011208711A1
Authority
US
United States
Prior art keywords
user
event
search
users
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/098,191
Inventor
Taylor N. Van Vleet
Yu-Shan Fung
Ruben Ortega
Udi Manber
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US13/098,191 priority Critical patent/US20110208711A1/en
Publication of US20110208711A1 publication Critical patent/US20110208711A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/953Querying, e.g. by the use of web search engines
    • G06F16/9535Search customisation based on user profiles and personalisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Definitions

  • the present disclosure relates to computer-based systems for capturing, persistently storing, and serving event data reflective of user-generated events, including search-related events.
  • Web site systems commonly include one or more mechanisms for capturing and storing information about the browsing activities or “clickstreams” of users.
  • the captured clickstream data is commonly used to personalize web pages for recognized users.
  • the captured clickstream data either provides only very limited information about each user's browsing history, or is captured in a format that is of only limited use for personalization.
  • some web sites maintain a real time record of each item selection, browse node selection, and search query submission performed by each user during browsing of an electronic catalog.
  • Such browse histories are useful, for example, for generating personalized item recommendations, and for displaying navigation histories to assist users in returning to previously accessed content.
  • these types of records typically lack the level of detail and structure desired for flexibly building new types of real-time personalization applications.
  • Some systems also maintain web server access logs (“web logs”) that contain a chronological record of every HTTP request received by the web site, together with associated timestamp and user ID information.
  • web query logs may also record the identities of items presented to users within such pages (commonly referred to as item “impressions”). While these logs typically contain more detailed browse history information, they are maintained in a format that is poorly suited for the real-time extraction and analysis of users' clickstream histories.
  • web logs can be mined for information useful to various personalization functions, the task of mining a large web log can take many hours or days, potentially rendering the extracted data stale by the time it is available for use. Further, much of the detailed information contained in a web log is disregarded during the mining process, and is thus effectively lost for purposes of personalization.
  • An event history server system persistently stores event data descriptive of events that occur during browsing sessions of web site users.
  • the event data is stored in association with the IDs of the corresponding users, and is made available in real time to web site applications that may use the event data to personalize web pages for specific users.
  • the event history server records event data descriptive of substantially every selection event (e.g., mouse click) of every user of a web site.
  • the event history server may also record event data descriptive of other types of browsing events, such as impressions (i.e., items presented to users on dynamically generated web pages) and mouse-over events.
  • the event data stored for each recorded event is preferably stored within a database as an event object.
  • Each event object may, for example, include identifiers of the general event type (e.g., mouse click, impression, etc.) and type of display element involved (e.g., catalog item, browse node, search result item, etc.), an event value (e.g., the text of a selected URL), a timestamp indicating of the event's date and time of occurrence, and associated context information.
  • a query interface of the event history server enables applications, such as personalization applications, to retrieve a particular user's event data by general event type, type of display element involved, time of occurrence, and possibly other criteria.
  • the query interface also preferably supports queries with the semantics of “has user X accessed URL Y before?” and “when did user X access URL Y?”
  • the query interface may more generally support queries with the semantics of “does an event of type T and value V exist within the event history of user X?”
  • users are provided an option to annotate particular search results, and to publish the annotations to other users.
  • the annotations may be stored as events that can be retrieved via the query interface.
  • the system may also provide functionality for users to organize and search their respective event histories.
  • FIG. 1 illustrates a web site system that includes an event history server system according to one embodiment of the invention.
  • FIG. 2 illustrates a set of software components that may be executed by the cache layer servers and storage layer servers of FIG. 1 .
  • FIG. 3 illustrates an example web search results page in which search results are annotated to indicate the user's prior browsing history with respect to such items.
  • FIG. 4 illustrates a process for identifying search result items that have previously been accessed by the user.
  • FIG. 5 illustrates a process for determining whether the user previously submitted the same search query, and if so, whether any new search result items have been located in the current search.
  • FIG. 7 illustrates how the event history server may be used to collect event data reported by a browser component, such as a browser toolbar.
  • FIG. 1 illustrates a web site system 30 that includes an event history server system 32 (“event history server”) according to one embodiment of the invention.
  • the event history server 32 provides a service for persistently recording, and providing real-time access to, event data indicative of events that occur during browsing sessions of users.
  • the event data preferably describes the clickstreams of the users, and may also describe other types of events such as mouse-over and impression events.
  • the event history server 32 also provides an API (application program interface) through which applications and services can flexibly retrieve, and request information about, the event data of specific users.
  • API application program interface
  • the web site system 30 includes one or more web server machines 34 that receive and process requests from user computers 36 and/or other types of devices (PDAs, mobile phones, etc.). Processes running on the web server machines 34 communicate with various web applications 38 , which may be implemented as web services. These applications 38 may run on the web server machines 34 , but more typically run on separate server machines (not shown). The types of web applications provided within a given system will typically depend upon the nature and purpose of the system. For example, an Internet search engine site may include one or more search applications 38 for enabling users to conduct keyword searches of an index of web pages.
  • An electronic commerce site may include web applications for performing such tasks as conducting searches of an electronic catalog, browsing an electronic catalog via a browse tree, generating personalized recommendations, placing orders, and managing personal account data.
  • web applications 38 supply personalized web page content based on user-specific event data stored by the event history server 32 .
  • APIs are also provided for allowing applications 38 to submit queries to the event history server 32 .
  • browsing events may additionally or alternatively be reported to the event history server 32 by a browser-based event reporting component ( FIG. 7 ) that runs on the user computers 36 .
  • the set of data stored by the event history server 32 for a particular event is preferably stored as an “event object.”
  • the event history server 32 persistently stores event objects describing substantially every selection action or “mouse click” of every recognized user of the web site system 30 .
  • This information may include, for example, the URL accessed, the time/date of the access, and associated context information.
  • the event history server may also record impression events reflective of specific items presented to users within dynamically generated web pages. For example, when a user views a dynamically-generated web page that includes a personalized list of items selected from a database, the event history server may store an event object for each such item, or may store a single event object that contains the list of items.
  • the event objects are preferably stored and indexed within the event history server 32 to permit retrieval based on time-of-occurrence, general event type (e.g., mouse click versus impression), type of display element involved (e.g., catalog item, browse node, or Web search result URL), user ID, and other object properties.
  • general event type e.g., mouse click versus impression
  • type of display element involved e.g., catalog item, browse node, or Web search result URL
  • user ID e.g., and other object properties.
  • the event data captured by the event history server 32 reflects actions performed by users during browsing of a particular web site or set of web sites hosted by the web site system 30 .
  • This captured data may, in some embodiments, also reflect actions performed by users during browsing of external, independent web sites. For example, users may be permitted or required to download to their computers 36 a browser plug-in, such as a browser toolbar, that reports all URL accesses (and possibly other types of events) to the event history server 32 (see FIG. 7 , discussed below).
  • Some or all of the web applications 38 preferably act as clients of the event history server 32 .
  • the web applications interact with the event history server 32 primarily by sending event queries to the event history server 32 in order to retrieve or obtain information about specific events.
  • Theses queries preferably include requests for fixed-size blocks of event data, such as “recall last N events of type T for user Y,” or “recall next N events of type T for user Y.”
  • a web application 38 may request the event objects for the last fifty search queries submitted by a particular user, or may request the event objects for the last fifty browse nodes viewed by a particular user.
  • the retrieved event objects may be used by the web applications 38 for any suitable purpose, such as generating personalized item recommendations or displaying browse history data to users to facilitate navigation.
  • the event history server 32 also preferably supports queries of the semantic form “does an event of type T and value V exist within the event history of user Y?” and “when did an event of type T and value V occur within the event history of user Y?”
  • a web application can query the event history server 32 to find out whether a particular user has accessed a particular URL before, and if so, when.
  • one application of this feature involves generating a personalized web search results page (see FIG. 3 ) that highlights the search results/URLs that have already been accessed by the particular user, and indicates when the viewed URLs were last accessed. Additional examples of the types of queries that may be supported by the event history server 32 , and of applications which make use of the captured event data, are provided below.
  • the event history server 32 may also respond to event queries (and possibly updates) from other types of components.
  • a data mining application may retrieve and analyze event data of users for purposes of enhancing browsing of the web site; and a security application or administrator may retrieve clickstream data to analyze a security breach.
  • Application components and services that send updates and/or queries to the event history server 32 are referred to herein as “clients,” and are depicted in FIG. 1 as being part of a client layer 39 .
  • the event history server 32 consists of two layers: a cache layer 40 and a persistent storage layer 44 .
  • the cache layer 40 is made up of a set of physical cache layer servers 42 , each of which runs service-level software 70 ( FIG. 2 ) for responding to updates and queries from clients.
  • Each cache layer server 42 includes a cache 43 that temporarily stores event data in the form of event objects.
  • the cache 43 may be implemented using non-volatile disk storage, random access memory, or a combination thereof. As described below, the cache 43 may also store user-specific Bloom filters for responding to certain types of queries. Communications between the client layer 39 , the cache layer 40 and the persistent storage layer preferably occur over a local area network.
  • the cache layer servers 42 are preferably partitioned by browsing session ID, meaning that each such server 42 only stores event data (event objects) associated with its respective range or group of session IDs. Thus, for example, when a user starts a new browsing session, that session is assigned to a particular cache layer server 42 which thereafter services all updates and event queries corresponding to that browsing session. In one implementation, a total of nine dual-CPU cache layer servers 42 are provided within the cache layer 40 , one of which is used as a hot spare.
  • the caches 43 are preferably implemented as stateless, write-through caches, facilitating the addition, removal, backup, and rebooting of the machines 42 .
  • the cache layer 40 acts essentially as an intermediary between the client layer 39 and the persistent storage layer 44 , allowing the system to operate at higher throughput levels.
  • the event history server 32 may alternatively be implemented without a cache layer. Further, where the cache layer 40 is provided, it may be bypassed where caching would not be beneficial, such that some requests are serviced directly by the persistent storage layer 44 .
  • the persistent storage layer 44 is made up of a set of physical storage layer servers 46 .
  • two storage layer servers 46 are provided, although a greater or lesser number may be used.
  • Each storage layer server 46 is responsible of maintaining a complete copy of the event data persistently stored by the system 32 .
  • the storage layer servers 46 are mirrors of each other when two or more are provided. Because the storage layer servers 46 are mirrored, a single storage layer server 46 can go down or be taken off line without affecting the overall functionality of the event history service.
  • Each storage layer server 46 may, for example, include several terabytes of disk drive storage. If approximately 100M events are recorded per day, and an average of thirty bytes of data are stored for each recorded event, each storage layer server 46 will store approximately 3 GB (gigabytes) of event data per day, or about one terabyte per year. Under such a usage scenario, each storage layer server 46 is capable of storing and serving several years worth of event data. When the storage capacity of a storage layer server 46 is reached, new disk drives may be added to the storage layer to increase its capacity, and/or old event data may be purged or archived.
  • each storage layer server 46 runs database software 62 for storing and managing the event data, and runs service-level code 60 for processing updates and queries received from the cache layer 40 .
  • the storage layer servers 46 may be implemented using low cost commodity hardware, and may use Berkeley databases, or another type of relatively low cost database, to store the event data.
  • the event history server 32 responds to updates generally as follows.
  • the cache layer server 42 assigned to the corresponding session ID updates its respective cache 43 to include the event object specified by the update. If the event is for a recognized user, the cache layer server 42 also sends the update to each of the storage layer servers 46 (preferably using a publish-subscribe protocol), and each such server 46 stores the associated event object within its persistent storage 64 in association with the corresponding user ID.
  • Each cache layer server 42 preferably aggregates multiple events/updates for sending to the storage layer servers 46 , so that these servers 46 receive updates from the cache layer in batches.
  • the event objects are stored in the cache 43 in association with the corresponding session ID and/or user ID.
  • the cache layer server 42 stores the event object in its cache 43 (in association with the corresponding session ID), but does not send the update to the persistent storage layer 44 .
  • the user may be unrecognized if, for example, the user (1) is new to the web site, (2) is accessing the web site from a particular computer 36 for the first time and has not logged in, or (3) is accessing the web site from a computer 36 that is configured to block cookies and has not logged in. Throughout a session, the cache layer will thus collect event data for an unrecognized user.
  • the associated cache layer server 42 associates collected event data for that user with the user's ID.
  • the cache layer server 42 sends a series of updates to the storage layer servers 44 to persistently store this collected event data in association with the user ID. The system thus allows a user's events to be persistently captured even though the user may not be recognized at the time such events occur. Further, during the period in which the user is unrecognized, clients of the event history server 32 can retrieve and request information about the cached event data of the unrecognized user based on the user's session ID.
  • the event history server 32 responds to event queries from clients generally as follows.
  • a cache layer server 46 receives an event query from a client, it initially checks its respective cache 43 to determine whether the relevant event data resides therein, and responds to the query if the data is present. If the relevant event data does not reside in the cache 43 , the query is passed to one of the storage layer servers 46 .
  • a load balancing algorithm may be used to select between the storage layer servers 46 for this purpose.
  • the selected storage layer server 46 responds to the query by generating a response (which may include requested event objects), and returning this response to the cache layer server 42 from which the query was received.
  • the cache layer server 42 then passes this response to the requesting client.
  • the cache layer server 42 stores this event data in its respective cache 43 by default.
  • an event query may indicate that the retrieved event data should not be cached; this feature may be used, for example, to inhibit caching when a large quantity of event data is read from persistent storage for purposes of off-line data mining.
  • the illustrated embodiment of the event history server 32 captures data descriptive of browsing events as such events occur, and makes such event data available to personalization applications 38 in real time (i.e., substantially immediately).
  • the event data is made available in a form that allows applications 38 to limit their queries to the specific types and items of event data needed to perform specific personalization tasks.
  • the applications 38 have access to the “raw” event data itself, as opposed to merely a summary of such data.
  • Users of the event history server may, in some embodiments, be given the option to control whether their respective browsing histories are to be recorded by the event history server (e.g., an opt-in or opt-out option may be provided). Additional features and benefits of the disclosed architecture are discussed below.
  • each event object includes the following components: Subject, Value, Tag, and Time. Each of these components is described below. In one embodiment, these components are used to capture data regarding three general types of events: mouse clicks, impressions, and mouse-over events.
  • the Subject of the event object is a code that indicates, for mouse click, mouse over, and impression events, the type of display element involved (e.g., an item, a browse node, an external URL, or link for submitting a search query).
  • One or more subject codes may also be defined for describing search query submissions from users.
  • Table 1 below provides examples of some of the event subjects that may be supported, and indicates the data stored in the Value field for each such event subject. These examples assume that the web site system 30 hosts an electronic catalog that may be browsed and searched by users to locate items (products, new articles, etc.), and also assumes that the web site system 30 implements a search engine for locating external web sites and pages. As will be recognized, the types of events recorded within a particular web site system 30 will depend largely on the nature and purpose of that system, and may vary significantly from those listed in Table 1.
  • an “annotation” event type is defined for purposes of storing annotations entered by users.
  • An “annotation” event type is defined for purposes of storing annotations entered by users.
  • One application for annotation events involves allowing users to annotate their respective search results, and to later recall and review such annotations. Users may also be given the ability to publish their annotations to other users. Unlike mouse clicks, impressions, and mouse over events, annotation events represent explicit requests by users to store event data for later retrieval.
  • This information may be captured, for stored, one which contains example, by initially directing the user's the text of the URL, and the browser to an internal URL used for tracking other of which contains the purposes, and then redirecting the browser to page's display title. Strings the external URL/web site selected by the user. that exceed a particular length are truncated.
  • Feature User access to a particular web site feature Feature ID such as an item recommendations service Other URL URL access event that does not fall within one Text of URL and associated of the above categories display title
  • the Tag may be implemented as a set of flags indicating some or all of the following: (1) the general type of the event (e.g., mouse click, impression, or mouse-over), (2) whether the Value portion of the event has been truncated (e.g., because of the excessive length of a particular text string), (3) whether the event is “undisplayable,” meaning that it cannot be viewed by the user, and (4) whether the event is transient versus persistent.
  • a Tag's “undisplayable” flag may be used, for example, to allow users to effectively remove events from their viewable event histories.
  • the web site system 30 may provide an application 38 and associated user interface through which users can view and search their respective event histories, and “delete” selected events from such histories.
  • the corresponding event object is marked by the event history server 32 as “undisplayable” to prevent the user from viewing the associated event, but remains accessible to clients of the event history server 32 .
  • the “transient/persistent” flag may be used to mark those events that can be permanently deleted from persistent storage at a certain point of time. This feature may be used to purge event objects that are of little or no value after a certain time period, so that the associated persistent storage is made available for storing other data.
  • the Time component is a numerical value indicating the time of occurrence of the event, and may be expressed, for example, in seconds since 1970.
  • an additional value may be included specifying the time of expiration of the event object.
  • Expired event objects may be deleted from persistent storage periodically by a background task, or using any other appropriate method.
  • the query set implemented by the event history server 32 preferably allows clients to retrieve the event objects for a given user or session based on event Subject, Value, Tag, and Time. For example, a client can request the event objects for all impressions (or all mouse click events) of a particular type of display element, or for all impressions (or all mouse click events) of a particular display element type and value.
  • the query set preferably allows clients to specify an event time range (e.g., “last 10 days,” or “since Feb. 10, of 2003”).
  • the query set also supports queries of the following form: “does an event of type T and value V exist within history of user X?”
  • the type of the event may be specified in the query in terms of the general event type (e.g., mouse click or impression), the type of display element involved, or both.
  • the query set supports queries of the type “when did event of type T and value V occur in the history of user X?”
  • FIG. 2 illustrates the primary software components that run on the cache layer and storage layer servers 42 , 46 in one embodiment.
  • each storage layer server 46 runs service code 60 for processing queries and updates from the cache layer 40 .
  • the service code communicates with database software 62 , such as software used to implement Berkeley databases.
  • the database software 62 manages one or more databases of event data in disk drive storage 64 .
  • each storage layer server 46 runs multiple pub-sub type service processes, each of which corresponds to a respective set or range of user IDs and exclusively accesses its own Berkeley database; this architecture greatly simplifies the management of the databases.
  • Each storage layer server 46 additionally runs synchronization service code 68 that is responsible for maintaining the storage layer servers in synchronization. The synchronization service is used, for example, to synchronize the persistent databases after one storage layer server is temporarily taken off line.
  • Each cache layer server 42 runs cache layer service code 70 that accesses its respective cache 43 of event data.
  • Event data is preferably stored in the cache 43 both by user ID (if the user is recognized) and session ID.
  • the cache layer service code 70 includes components 72 , 74 for processing updates and queries received from clients.
  • both types of servers 42 , 46 also preferably include software components for generating and processing Bloom filters.
  • each Bloom filter is a condensed representation of some portion of a user's event data, and may be used to evaluate whether the user has performed a particular action without having to retrieve the associated event objects.
  • Bloom filters are used to reduce the processing and data retrieval needed to determine whether a given user has accessed a given URL.
  • one application of the event history server 32 involves generating a personalized search results page identifying any search result items that were previously accessed by the particular user.
  • the search results page may further indicate the time each such item was accessed. This feature may be applied both to internal catalog searches (in which case the search results page may, for example, indicate those catalog items for which the user has viewed an item detail page), and to web searches (in which case the search results page may indicate which of the external web pages has been viewed).
  • FIG. 3 illustrates an example web search results page according to one embodiment of this feature.
  • the web search query “lord of the rings” has produced a search results listing in which each search result item (three shown) is an external web page or site having a corresponding URL.
  • the links contained within the search result listings are internal links (i.e., they point back to the web server system 30 ) that are used to immediately redirect the user's browser to the external page of interest; this allows the event history server 32 to record event objects describing the search results (external URLs) selected by the user for viewing.
  • the user's selections of external URLs are logged by firing a JavaScript component that detects and reports the user's selections.
  • the first item 100 in the list of FIG. 3 includes the annotation “viewed,” indicating that the user previously accessed this particular URL.
  • the user can thus readily identify those web pages that have already been viewed. Because the user's event history is stored on the server side (rather than merely on the user's computer 36 ), the “viewed” status may be properly indicated even if the user only viewed the particular web page from a different computer 36 .
  • the user By hovering the mouse cursor over this item 100 , the user can also view the date he/she last accessed this URL, as shown by the mouse-over text “previously viewed on February 14.”
  • the date-of-access text may alternatively be displayed in-line with the search results text 100 .
  • Various other types of information can be incorporated into the annotations based on the user's event history, such as the number of times the user has accessed the particular URL, and the text of a prior search query that uncovered this URL (if different from the current search query).
  • FIG. 4 illustrates the general process by which a search application 38 may interact with the event history server 32 to generate search results pages of the type shown in FIG. 3 .
  • the search application initially receives a search query, and executes the search to generate a set of search results. If the search is a general web search, each search result item will be in the form of a URL of a web page that is responsive to the search, and may be displayed together with textual excerpts extracted from such web pages (as in FIG. 3 ).
  • the execution of such searches typically involves comparing the search query to an index generated by a web crawler program.
  • each search result item may be in the form of an item description that may be clicked on to access a corresponding item detail page.
  • the search results returned in a given search may include both external web pages and items selected from an internally-hosted electronic catalog.
  • the search application then sends a separate query to the event history server 32 for each search result item—or at least those that are to be displayed on the current search result page—to determine whether the user previously accessed that item.
  • the event history server 32 preferably uses Bloom filters to efficiently process these types of queries, although the use of Bloom filters may alternatively be omitted.
  • search results page is generated with embedded viewed-item annotations of the type shown in FIG. 3 .
  • the search application may also take the viewed/not-viewed status of each search result item into consideration in ranking/ordering the search result items for display.
  • the process depicted by FIG. 4 can be varied such that the event history server 32 is not actually accessed in response to the search queries.
  • the event data indicative of specific search result URLs selected by specific users can be periodically retrieved from the event history server 32 and stored on a separate “search personalization” server. This separate server can then be assigned to the task of responding to requests of the type “has user X accessed external URL Y?” The same is true for the process of FIG. 5 , described below.
  • the search application's user interface may also provide an option for the user to restrict the scope of the search to items previously viewed, items not previously viewed, or items viewed within a particular time period (e.g., the last seven days). This feature may be implemented using the same process flow as in FIG. 4 , except that the query results returned by the event history server 32 will be used to determine which search result items are to be displayed.
  • the foregoing search results personalization features may also be applied to searches for other types of items.
  • the results of an auction search may be annotated to indicate which of the located auctions have been viewed by the user, when each auction was viewed, and possibly whether the user has submitted a bid on each such auction.
  • the results of a search of bulletin board postings or blog (web log) postings may be annotated to indicate if/when specific postings were viewed by the user.
  • the second search result item 120 illustrates another feature that may be implemented using the event history server 32 .
  • This feature involves determining whether the user previously submitted the same search query, and if so, whether any new search result items (i.e., items not present in the prior search results set) have been found.
  • the search results page reveals that the user previously conducted the same search on February 14, and that the item corresponding to the URL “lordotrings.com” is a new item that did not come up in the prior search.
  • FIG. 5 illustrates the general process by which a search application 38 may interact with the event history server 32 to implement this “new-item annotations” feature. This process may be combined with that of FIG. 4 to generate annotated search results pages of the type shown in FIG. 3 .
  • the search application initially receives and executes the search query (block 130 ), and queries the event history server 32 to determine whether the user has previously submitted the same query (block 132 ). If the user has not submitted this query, the search results page is generated (block 140 ) without adding any “new item” annotations.
  • the event history server 32 is again queried for the time of the last submission (block 134 ).
  • the event history server 32 is queried to determine which of the current search result items, if any, have not been displayed to the user (i.e., have not been the subject of an impression event); this query may optionally be limited in scope to impressions occurring at the time of or shortly after the prior search.
  • any new search result items exist in the current search result set they are annotated as shown in FIG. 3 (item 120 ).
  • the relevance rankings of the new items may also be augmented to increase the likelihood that the new items will be displayed.
  • One variation of the method shown in FIG. 5 is to allow the user to explicitly limit the (repeat) search to items that did not come up in a prior execution of the same search query.
  • This option may, for example, be provided as a check box on the web site's search page.
  • Bloom filters may be used by the event history server 32 to reduce the need for persistent data retrieval when responding to a query of the form “does event of type T and value V exist in history of user X?” For example, Bloom filters may be used to determine whether a particular user has viewed or selected a particular URL.
  • a Bloom filter is a bit sequence or array generated according to a set of hash functions. Bloom filters are used to quickly test whether a particular item is a member of a large set of items.
  • One common application for Bloom filters is to test whether a given object (as identified by the object's URL) is currently stored in a cache of web pages. Specifically, when an object is added to the cache, the hash functions are applied to the object's URL to determine which of the bits in the Bloom filter are to be turned ON. When an object is requested, these hash functions are again applied to the requested object's URL, and a test is then performed to determine whether all of the corresponding bits in the Bloom filter are turned ON. If one or more of the bits are not ON, the object is not stored in the cache.
  • one or more Bloom filters are generated for a given user to describe some aspect or segment of that user's event history.
  • the Bloom filters are preferably generated and stored by the persistent storage layer 44 ( FIG. 1 ), and are passed to the cache layer 40 for purposes of responding to queries.
  • Different Bloom filters may be generated for a given user for responding to different types of queries.
  • different types of Bloom filters may be generated for different types of activity (e.g., URL accesses, URL impressions, URL accesses plus impressions, catalog item accesses, mouse over events, etc.).
  • different Bloom filters may be generated for different time periods.
  • FIG. 6 illustrates the general process by which a Bloom filter may be used to test for URL accesses by a recognized user, User X.
  • a storage layer server 46 generates one or more Bloom filters for User X. This step may, for example, be performed in response to receiving an associated query or update for User X.
  • the storage layer service code FIG. 2 ) initially retrieves URL access events for User X, applies a set of hash functions to each accessed URL, and sets the associated Bloom filter bits.
  • the size of the Bloom filter may be selected to enable storage of a desired number of events while maintaining a false-positive rate below a desired threshold.
  • Bloom filters generated by one storage layer server 46 may be passed to the other storage layer server(s) by the synchronization service.
  • the bloom filters may additionally or alternatively be generated by the cache layer servers 42 .
  • a cache layer server receives a query of the form “has User X accessed URL Y?” In the context of the search results annotation features described above, many such queries may be received for a given user for purposes of generating a single search results page.
  • the cache layer server 42 retrieves the relevant Bloom filter from one of the storage layer servers 46 if the Bloom filter is not already stored in the cache 43 .
  • the cache layer server 42 tests the relevant Bloom filter to see if the corresponding bits for the URL are ON. If one or more of the bits are OFF (meaning that no accesses to URL Y exist in the relevant event history of User X), the cache layer server 42 returns an answer of NO (step 5 ), without passing the query to the persistent storage layer. If, on the other hand, all of the bits are ON (meaning that the URL access very likely exists within User X's event history), the query is passed to one of the storage layer servers 46 (step 6 ) to check User X's actual event data for the URL access. In step 7 , the storage layer server 46 returns a response to the query via the cache layer server 42 . As an alternative to querying the storage layer server (step 6 ), the cache layer server can be designed to simply return a YES response when the Bloom filter test is positive, although this approach may cause in accurate results to be presented to users on rare occasions.
  • the cache layer server 42 (but preferably not the storage layer server 46 ) updates its copy of the associated Bloom filter to reflect these updates. For example, if User X selects a search result item (URL) from a web search results page of the type shown in FIG. 3 , the associated Bloom filter will be updated within the cache 43 to set the bits associated with the selected URL. Thus, the Bloom filter used by the cache layer to respond to queries reflects the most recent browsing activities of the relevant user. At some point, the Bloom filter may be purged from the cache 43 due to inactivity, at which time the updated Bloom filter is written to the persistent storage layer (in place of the original version) for further use.
  • the Bloom filter may be purged from the cache 43 due to inactivity, at which time the updated Bloom filter is written to the persistent storage layer (in place of the original version) for further use.
  • a given Bloom filter may reach its capacity, meaning that it cannot store additional events without exceeding a desired average false positive rate.
  • the Bloom filter may be replaced with a larger Bloom filter (e.g., 8 Kilobytes rather than 4 Kilobytes) in order to provide greater event capacity.
  • FIG. 7 illustrates an embodiment in which the event history server 32 records event data reported by a browser-based event reporting component 160 .
  • the event reporting component 160 runs as a component of a web browser 162 on some or all of the computers 36 of users of the event history server 32 .
  • the event reporting component 160 is preferably implemented as part of a browser toolbar component 164 .
  • the toolbar component 164 may, for example, be provided as an optional browser plug-in that can be downloaded and installed by users.
  • the event reporting component 160 may alternatively be implemented as a standalone browser plug-in, as part of a plug-in other than a toolbar, or as part of the native code of the web browser 162 .
  • the browser-based event reporting component 160 preferably reports event data for all web sites and pages accessed by the user. For example, the event reporting component 160 may report every mouse click or other selection event on every web page accessed by the user. The event reporting component 160 may also report other types of browsing events, such as mouse-over events, impressions, selections of the “back” button on the web browser 162 , etc.
  • the browser-based event reporting component 160 may take the place of the server-based event reporting component 35 of FIG. 1 .
  • both types of event reporting components 35 , 160 may be used within a given system.
  • the event history server 32 may only capture data reported by the server-based event reporting component 35 , in which case the event data may only reflect events that occur during browsing of one or more specific web sites.
  • the captured event data may also extend to other web sites.
  • personalized toolbar content may be generated by a server-side toolbar personalization application 170 .
  • This application 170 may use event data retrieved from the event history server 32 to generate context-sensitive toolbar messages for display to users. For example, when a user accesses a particular web site, the toolbar personalization application 170 may retrieve and display a history of transactions performed by the user on that web site. Further, the toolbar may be personalized with real time information about all of the web sites or pages visited during the current browsing session.

Abstract

Various features are disclosed for storing and providing access to event data reflective of user-generated events, including events associated with search query submission of users. One such feature enables users to annotate search results, to later recall and view these annotations, and to publish the annotations to other users. Another feature involves recording event data reflective of search result viewing events of users, and using this event data to personalize search results pages for particular users.

Description

    PRIORITY CLAIM
  • This application is a continuation of U.S. application Ser. No. 11/325,009, filed Jan. 4, 2006, which is a division of U.S. patent application Ser. No. 10/612,395, filed Jul. 2, 2003, the disclosure of which is hereby incorporated by reference.
  • BACKGROUND
  • 1. Field
  • The present disclosure relates to computer-based systems for capturing, persistently storing, and serving event data reflective of user-generated events, including search-related events.
  • 2. Description of the Related Art
  • Web site systems commonly include one or more mechanisms for capturing and storing information about the browsing activities or “clickstreams” of users. The captured clickstream data is commonly used to personalize web pages for recognized users. Typically, however, the captured clickstream data either provides only very limited information about each user's browsing history, or is captured in a format that is of only limited use for personalization.
  • For example, some web sites maintain a real time record of each item selection, browse node selection, and search query submission performed by each user during browsing of an electronic catalog. Such browse histories are useful, for example, for generating personalized item recommendations, and for displaying navigation histories to assist users in returning to previously accessed content. However, these types of records typically lack the level of detail and structure desired for flexibly building new types of real-time personalization applications.
  • Some systems also maintain web server access logs (“web logs”) that contain a chronological record of every HTTP request received by the web site, together with associated timestamp and user ID information. For web pages that are generated dynamically, the web query logs may also record the identities of items presented to users within such pages (commonly referred to as item “impressions”). While these logs typically contain more detailed browse history information, they are maintained in a format that is poorly suited for the real-time extraction and analysis of users' clickstream histories. Although web logs can be mined for information useful to various personalization functions, the task of mining a large web log can take many hours or days, potentially rendering the extracted data stale by the time it is available for use. Further, much of the detailed information contained in a web log is disregarded during the mining process, and is thus effectively lost for purposes of personalization.
  • SUMMARY
  • An event history server system is disclosed that persistently stores event data descriptive of events that occur during browsing sessions of web site users. The event data is stored in association with the IDs of the corresponding users, and is made available in real time to web site applications that may use the event data to personalize web pages for specific users. In one embodiment, the event history server records event data descriptive of substantially every selection event (e.g., mouse click) of every user of a web site. The event history server may also record event data descriptive of other types of browsing events, such as impressions (i.e., items presented to users on dynamically generated web pages) and mouse-over events.
  • The event data stored for each recorded event is preferably stored within a database as an event object. Each event object may, for example, include identifiers of the general event type (e.g., mouse click, impression, etc.) and type of display element involved (e.g., catalog item, browse node, search result item, etc.), an event value (e.g., the text of a selected URL), a timestamp indicating of the event's date and time of occurrence, and associated context information. A query interface of the event history server enables applications, such as personalization applications, to retrieve a particular user's event data by general event type, type of display element involved, time of occurrence, and possibly other criteria. The query interface also preferably supports queries with the semantics of “has user X accessed URL Y before?” and “when did user X access URL Y?” The query interface may more generally support queries with the semantics of “does an event of type T and value V exist within the event history of user X?”
  • In one embodiment, users are provided an option to annotate particular search results, and to publish the annotations to other users. The annotations may be stored as events that can be retrieved via the query interface. The system may also provide functionality for users to organize and search their respective event histories.
  • Neither this summary nor the following detailed description purports to define the invention. The invention is defined by the claims.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates a web site system that includes an event history server system according to one embodiment of the invention.
  • FIG. 2 illustrates a set of software components that may be executed by the cache layer servers and storage layer servers of FIG. 1.
  • FIG. 3 illustrates an example web search results page in which search results are annotated to indicate the user's prior browsing history with respect to such items.
  • FIG. 4 illustrates a process for identifying search result items that have previously been accessed by the user.
  • FIG. 5 illustrates a process for determining whether the user previously submitted the same search query, and if so, whether any new search result items have been located in the current search.
  • FIG. 6 illustrates the use of a Bloom filter to efficiently determine whether a user has accessed a particular object.
  • FIG. 7 illustrates how the event history server may be used to collect event data reported by a browser component, such as a browser toolbar.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • A preferred embodiment of a web site system that includes an event history server system will now be described with reference to the drawings. As will be recognized, many of the inventive features embodied within the disclosed system may be implemented or used without others. Numerous implementation details will be set forth in the following description in order to illustrate, but not limit, the invention.
  • I. Overview
  • FIG. 1 illustrates a web site system 30 that includes an event history server system 32 (“event history server”) according to one embodiment of the invention. The event history server 32 provides a service for persistently recording, and providing real-time access to, event data indicative of events that occur during browsing sessions of users. The event data preferably describes the clickstreams of the users, and may also describe other types of events such as mouse-over and impression events. As described below, the event history server 32 also provides an API (application program interface) through which applications and services can flexibly retrieve, and request information about, the event data of specific users.
  • As illustrated in FIG. 1, the web site system 30 includes one or more web server machines 34 that receive and process requests from user computers 36 and/or other types of devices (PDAs, mobile phones, etc.). Processes running on the web server machines 34 communicate with various web applications 38, which may be implemented as web services. These applications 38 may run on the web server machines 34, but more typically run on separate server machines (not shown). The types of web applications provided within a given system will typically depend upon the nature and purpose of the system. For example, an Internet search engine site may include one or more search applications 38 for enabling users to conduct keyword searches of an index of web pages. An electronic commerce site may include web applications for performing such tasks as conducting searches of an electronic catalog, browsing an electronic catalog via a browse tree, generating personalized recommendations, placing orders, and managing personal account data. For purposes of this description, it may be assumed that at least some of the web applications 38 supply personalized web page content based on user-specific event data stored by the event history server 32.
  • As depicted in FIG. 1, each web server machine 34 preferably runs an event reporting component 35 that sends updates to the event history server 32 in response to actions performed by online users. (A given user need not be an individual, but may, for example, be a group of individuals that share a user computer 36 or a user account). Each such update contains or otherwise specifies event data descriptive of a particular event that has occurred during a browsing session of a user, such as a mouse click, a search query submission, or an impression. The event reporting component 35 may include a set of APIs (application program interfaces) for making calls to the event history server 32, and may include configuration parameters specifying the types of actions for which events/updates are to be generated. APIs are also provided for allowing applications 38 to submit queries to the event history server 32. As described in section V below, browsing events may additionally or alternatively be reported to the event history server 32 by a browser-based event reporting component (FIG. 7) that runs on the user computers 36.
  • The set of data stored by the event history server 32 for a particular event is preferably stored as an “event object.” In one embodiment, for example, the event history server 32 persistently stores event objects describing substantially every selection action or “mouse click” of every recognized user of the web site system 30. This information may include, for example, the URL accessed, the time/date of the access, and associated context information. The event history server may also record impression events reflective of specific items presented to users within dynamically generated web pages. For example, when a user views a dynamically-generated web page that includes a personalized list of items selected from a database, the event history server may store an event object for each such item, or may store a single event object that contains the list of items. Additional examples of the types of events that may be recorded, and of the event data that may be recorded for such events, are provided below. The event objects are preferably stored and indexed within the event history server 32 to permit retrieval based on time-of-occurrence, general event type (e.g., mouse click versus impression), type of display element involved (e.g., catalog item, browse node, or Web search result URL), user ID, and other object properties.
  • The event data captured by the event history server 32 reflects actions performed by users during browsing of a particular web site or set of web sites hosted by the web site system 30. This captured data may, in some embodiments, also reflect actions performed by users during browsing of external, independent web sites. For example, users may be permitted or required to download to their computers 36 a browser plug-in, such as a browser toolbar, that reports all URL accesses (and possibly other types of events) to the event history server 32 (see FIG. 7, discussed below).
  • Some or all of the web applications 38 preferably act as clients of the event history server 32. As depicted in FIG. 1, the web applications interact with the event history server 32 primarily by sending event queries to the event history server 32 in order to retrieve or obtain information about specific events. Theses queries preferably include requests for fixed-size blocks of event data, such as “recall last N events of type T for user Y,” or “recall next N events of type T for user Y.” For example, a web application 38 may request the event objects for the last fifty search queries submitted by a particular user, or may request the event objects for the last fifty browse nodes viewed by a particular user. The retrieved event objects may be used by the web applications 38 for any suitable purpose, such as generating personalized item recommendations or displaying browse history data to users to facilitate navigation.
  • The event history server 32 also preferably supports queries of the semantic form “does an event of type T and value V exist within the event history of user Y?” and “when did an event of type T and value V occur within the event history of user Y?” For example, a web application can query the event history server 32 to find out whether a particular user has accessed a particular URL before, and if so, when. As described below, one application of this feature involves generating a personalized web search results page (see FIG. 3) that highlights the search results/URLs that have already been accessed by the particular user, and indicates when the viewed URLs were last accessed. Additional examples of the types of queries that may be supported by the event history server 32, and of applications which make use of the captured event data, are provided below.
  • Although the event queries are depicted in FIG. 1 as emanating from the web applications 38, the event history server 32 may also respond to event queries (and possibly updates) from other types of components. For example, a data mining application may retrieve and analyze event data of users for purposes of enhancing browsing of the web site; and a security application or administrator may retrieve clickstream data to analyze a security breach. Application components and services that send updates and/or queries to the event history server 32 are referred to herein as “clients,” and are depicted in FIG. 1 as being part of a client layer 39.
  • As illustrated in FIG. 1, the event history server 32 consists of two layers: a cache layer 40 and a persistent storage layer 44. The cache layer 40 is made up of a set of physical cache layer servers 42, each of which runs service-level software 70 (FIG. 2) for responding to updates and queries from clients. Each cache layer server 42 includes a cache 43 that temporarily stores event data in the form of event objects. The cache 43 may be implemented using non-volatile disk storage, random access memory, or a combination thereof. As described below, the cache 43 may also store user-specific Bloom filters for responding to certain types of queries. Communications between the client layer 39, the cache layer 40 and the persistent storage layer preferably occur over a local area network.
  • The cache layer servers 42 are preferably partitioned by browsing session ID, meaning that each such server 42 only stores event data (event objects) associated with its respective range or group of session IDs. Thus, for example, when a user starts a new browsing session, that session is assigned to a particular cache layer server 42 which thereafter services all updates and event queries corresponding to that browsing session. In one implementation, a total of nine dual-CPU cache layer servers 42 are provided within the cache layer 40, one of which is used as a hot spare. The caches 43 are preferably implemented as stateless, write-through caches, facilitating the addition, removal, backup, and rebooting of the machines 42.
  • As described below, the cache layer 40 acts essentially as an intermediary between the client layer 39 and the persistent storage layer 44, allowing the system to operate at higher throughput levels. Although the use of a cache layer 40 is preferred, the event history server 32 may alternatively be implemented without a cache layer. Further, where the cache layer 40 is provided, it may be bypassed where caching would not be beneficial, such that some requests are serviced directly by the persistent storage layer 44.
  • With further reference to FIG. 1, the persistent storage layer 44 is made up of a set of physical storage layer servers 46. In the illustrated embodiment, two storage layer servers 46 are provided, although a greater or lesser number may be used. Each storage layer server 46 is responsible of maintaining a complete copy of the event data persistently stored by the system 32. Thus, the storage layer servers 46 are mirrors of each other when two or more are provided. Because the storage layer servers 46 are mirrored, a single storage layer server 46 can go down or be taken off line without affecting the overall functionality of the event history service.
  • Each storage layer server 46 may, for example, include several terabytes of disk drive storage. If approximately 100M events are recorded per day, and an average of thirty bytes of data are stored for each recorded event, each storage layer server 46 will store approximately 3 GB (gigabytes) of event data per day, or about one terabyte per year. Under such a usage scenario, each storage layer server 46 is capable of storing and serving several years worth of event data. When the storage capacity of a storage layer server 46 is reached, new disk drives may be added to the storage layer to increase its capacity, and/or old event data may be purged or archived.
  • As described below and depicted in FIG. 2, each storage layer server 46 runs database software 62 for storing and managing the event data, and runs service-level code 60 for processing updates and queries received from the cache layer 40. The storage layer servers 46 may be implemented using low cost commodity hardware, and may use Berkeley databases, or another type of relatively low cost database, to store the event data.
  • The event history server 32 responds to updates generally as follows. When an update is sent to the cache layer 40 by a web server machine 34, the cache layer server 42 assigned to the corresponding session ID updates its respective cache 43 to include the event object specified by the update. If the event is for a recognized user, the cache layer server 42 also sends the update to each of the storage layer servers 46 (preferably using a publish-subscribe protocol), and each such server 46 stores the associated event object within its persistent storage 64 in association with the corresponding user ID. Each cache layer server 42 preferably aggregates multiple events/updates for sending to the storage layer servers 46, so that these servers 46 receive updates from the cache layer in batches. The event objects are stored in the cache 43 in association with the corresponding session ID and/or user ID.
  • If the event data specified within an update is for an unrecognized user, the cache layer server 42 stores the event object in its cache 43 (in association with the corresponding session ID), but does not send the update to the persistent storage layer 44. The user may be unrecognized if, for example, the user (1) is new to the web site, (2) is accessing the web site from a particular computer 36 for the first time and has not logged in, or (3) is accessing the web site from a computer 36 that is configured to block cookies and has not logged in. Throughout a session, the cache layer will thus collect event data for an unrecognized user.
  • If an unrecognized user logs in, creates an account, or otherwise becomes recognized during the browsing session, the associated cache layer server 42 associates collected event data for that user with the user's ID. In addition, the cache layer server 42 sends a series of updates to the storage layer servers 44 to persistently store this collected event data in association with the user ID. The system thus allows a user's events to be persistently captured even though the user may not be recognized at the time such events occur. Further, during the period in which the user is unrecognized, clients of the event history server 32 can retrieve and request information about the cached event data of the unrecognized user based on the user's session ID.
  • The event history server 32 responds to event queries from clients generally as follows. When a cache layer server 46 receives an event query from a client, it initially checks its respective cache 43 to determine whether the relevant event data resides therein, and responds to the query if the data is present. If the relevant event data does not reside in the cache 43, the query is passed to one of the storage layer servers 46. A load balancing algorithm may be used to select between the storage layer servers 46 for this purpose. The selected storage layer server 46 responds to the query by generating a response (which may include requested event objects), and returning this response to the cache layer server 42 from which the query was received. The cache layer server 42 then passes this response to the requesting client.
  • If the response includes event data retrieved from persistent storage, the cache layer server 42 stores this event data in its respective cache 43 by default. In the preferred embodiment, an event query may indicate that the retrieved event data should not be cached; this feature may be used, for example, to inhibit caching when a large quantity of event data is read from persistent storage for purposes of off-line data mining.
  • As indicated by the foregoing, the illustrated embodiment of the event history server 32 captures data descriptive of browsing events as such events occur, and makes such event data available to personalization applications 38 in real time (i.e., substantially immediately). In addition, the event data is made available in a form that allows applications 38 to limit their queries to the specific types and items of event data needed to perform specific personalization tasks. Further, unlike systems that rely on the results of an off-line data mining analysis, the applications 38 have access to the “raw” event data itself, as opposed to merely a summary of such data. Users of the event history server may, in some embodiments, be given the option to control whether their respective browsing histories are to be recorded by the event history server (e.g., an opt-in or opt-out option may be provided). Additional features and benefits of the disclosed architecture are discussed below.
  • II. Event Object Content and Retrieval
  • As indicated above, the set of data stored for a given event is stored by the event history server 32 as an event object. In one embodiment, each event object includes the following components: Subject, Value, Tag, and Time. Each of these components is described below. In one embodiment, these components are used to capture data regarding three general types of events: mouse clicks, impressions, and mouse-over events.
  • The Subject of the event object is a code that indicates, for mouse click, mouse over, and impression events, the type of display element involved (e.g., an item, a browse node, an external URL, or link for submitting a search query). One or more subject codes may also be defined for describing search query submissions from users. The Subject of an event, together with the event's Tag (described below), fully specify the type of the event (e.g., mouse click of browse node, impression of catalog item, etc.).
  • Table 1 below provides examples of some of the event subjects that may be supported, and indicates the data stored in the Value field for each such event subject. These examples assume that the web site system 30 hosts an electronic catalog that may be browsed and searched by users to locate items (products, new articles, etc.), and also assumes that the web site system 30 implements a search engine for locating external web sites and pages. As will be recognized, the types of events recorded within a particular web site system 30 will depend largely on the nature and purpose of that system, and may vary significantly from those listed in Table 1.
  • Further, the event types may be varied or extended in order to support additional application features. For example, in one embodiment which is not represented in Table 1, an “annotation” event type is defined for purposes of storing annotations entered by users. One application for annotation events involves allowing users to annotate their respective search results, and to later recall and review such annotations. Users may also be given the ability to publish their annotations to other users. Unlike mouse clicks, impressions, and mouse over events, annotation events represent explicit requests by users to store event data for later retrieval.
  • TABLE 1
    Event
    Subject Description Value
    Catalog User selection, impression, or mouse-over of a Item ID
    item catalog item
    Browse User selection, impression, or mouse-over of a Browse node ID
    node browse node (item category)
    Internal Search query submission for conducting an Text of search term(s)
    Search internal search, such as a search for items in an entered by user
    query electronic catalog
    Web search Search query submission for conducting a Text of search term(s)
    query general Web/Internet search that is not limited entered by user
    in scope to any particular set of Web sites
    Web search URL selected by user from web search results Two separate strings are
    URL page. This information may be captured, for stored, one which contains
    example, by initially directing the user's the text of the URL, and the
    browser to an internal URL used for tracking other of which contains the
    purposes, and then redirecting the browser to page's display title. Strings
    the external URL/web site selected by the user. that exceed a particular
    length are truncated.
    Feature User access to a particular web site feature, Feature ID
    such as an item recommendations service
    Other URL URL access event that does not fall within one Text of URL and associated
    of the above categories display title
  • The Tag may be implemented as a set of flags indicating some or all of the following: (1) the general type of the event (e.g., mouse click, impression, or mouse-over), (2) whether the Value portion of the event has been truncated (e.g., because of the excessive length of a particular text string), (3) whether the event is “undisplayable,” meaning that it cannot be viewed by the user, and (4) whether the event is transient versus persistent.
  • A Tag's “undisplayable” flag may be used, for example, to allow users to effectively remove events from their viewable event histories. For example, the web site system 30 may provide an application 38 and associated user interface through which users can view and search their respective event histories, and “delete” selected events from such histories. When a user deletes a particular event (such as particular search query submission or browse node access), the corresponding event object is marked by the event history server 32 as “undisplayable” to prevent the user from viewing the associated event, but remains accessible to clients of the event history server 32.
  • The “transient/persistent” flag may be used to mark those events that can be permanently deleted from persistent storage at a certain point of time. This feature may be used to purge event objects that are of little or no value after a certain time period, so that the associated persistent storage is made available for storing other data.
  • The Time component is a numerical value indicating the time of occurrence of the event, and may be expressed, for example, in seconds since 1970. When the persistent/transient flag is set to “transient,” an additional value may be included specifying the time of expiration of the event object. Expired event objects may be deleted from persistent storage periodically by a background task, or using any other appropriate method.
  • The query set implemented by the event history server 32 preferably allows clients to retrieve the event objects for a given user or session based on event Subject, Value, Tag, and Time. For example, a client can request the event objects for all impressions (or all mouse click events) of a particular type of display element, or for all impressions (or all mouse click events) of a particular display element type and value. In addition, the query set preferably allows clients to specify an event time range (e.g., “last 10 days,” or “since Feb. 10, of 2003”).
  • As mentioned above, the query set also supports queries of the following form: “does an event of type T and value V exist within history of user X?” The type of the event may be specified in the query in terms of the general event type (e.g., mouse click or impression), the type of display element involved, or both. For example, a query of the form “does event of type=Web search query and Value=comet Halley exist in history of user X?” would reveal whether user X has conducted a general Web search using the query “comet Halley.” Further, the query set supports queries of the type “when did event of type T and value V occur in the history of user X?”
  • III. Software Architecture
  • FIG. 2 illustrates the primary software components that run on the cache layer and storage layer servers 42, 46 in one embodiment. As illustrated, each storage layer server 46 runs service code 60 for processing queries and updates from the cache layer 40. The service code communicates with database software 62, such as software used to implement Berkeley databases. The database software 62 manages one or more databases of event data in disk drive storage 64. In one embodiment, each storage layer server 46 runs multiple pub-sub type service processes, each of which corresponds to a respective set or range of user IDs and exclusively accesses its own Berkeley database; this architecture greatly simplifies the management of the databases. Each storage layer server 46 additionally runs synchronization service code 68 that is responsible for maintaining the storage layer servers in synchronization. The synchronization service is used, for example, to synchronize the persistent databases after one storage layer server is temporarily taken off line.
  • Each cache layer server 42 runs cache layer service code 70 that accesses its respective cache 43 of event data. Event data is preferably stored in the cache 43 both by user ID (if the user is recognized) and session ID. As illustrated in FIG. 2, the cache layer service code 70 includes components 72, 74 for processing updates and queries received from clients.
  • As further depicted in FIG. 2, both types of servers 42, 46 also preferably include software components for generating and processing Bloom filters. As described below, each Bloom filter is a condensed representation of some portion of a user's event data, and may be used to evaluate whether the user has performed a particular action without having to retrieve the associated event objects. For example, in one embodiment, Bloom filters are used to reduce the processing and data retrieval needed to determine whether a given user has accessed a given URL.
  • IV. Example Search Personalization Applications
  • As indicated above, one application of the event history server 32 involves generating a personalized search results page identifying any search result items that were previously accessed by the particular user. The search results page may further indicate the time each such item was accessed. This feature may be applied both to internal catalog searches (in which case the search results page may, for example, indicate those catalog items for which the user has viewed an item detail page), and to web searches (in which case the search results page may indicate which of the external web pages has been viewed).
  • FIG. 3 illustrates an example web search results page according to one embodiment of this feature. In this example, the web search query “lord of the rings” has produced a search results listing in which each search result item (three shown) is an external web page or site having a corresponding URL. In one embodiment, the links contained within the search result listings are internal links (i.e., they point back to the web server system 30) that are used to immediately redirect the user's browser to the external page of interest; this allows the event history server 32 to record event objects describing the search results (external URLs) selected by the user for viewing. In another embodiment, the user's selections of external URLs are logged by firing a JavaScript component that detects and reports the user's selections.
  • The first item 100 in the list of FIG. 3 includes the annotation “viewed,” indicating that the user previously accessed this particular URL. The user can thus readily identify those web pages that have already been viewed. Because the user's event history is stored on the server side (rather than merely on the user's computer 36), the “viewed” status may be properly indicated even if the user only viewed the particular web page from a different computer 36. By hovering the mouse cursor over this item 100, the user can also view the date he/she last accessed this URL, as shown by the mouse-over text “previously viewed on February 14.” The date-of-access text may alternatively be displayed in-line with the search results text 100. Various other types of information can be incorporated into the annotations based on the user's event history, such as the number of times the user has accessed the particular URL, and the text of a prior search query that uncovered this URL (if different from the current search query).
  • FIG. 4 illustrates the general process by which a search application 38 may interact with the event history server 32 to generate search results pages of the type shown in FIG. 3. It is assumed in this example that the user is recognized by the web site system 30. As depicted by block 110, the search application initially receives a search query, and executes the search to generate a set of search results. If the search is a general web search, each search result item will be in the form of a URL of a web page that is responsive to the search, and may be displayed together with textual excerpts extracted from such web pages (as in FIG. 3). As is known in the art, the execution of such searches typically involves comparing the search query to an index generated by a web crawler program. If the search is directed to an electronic catalog hosted by the web site system 30, each search result item may be in the form of an item description that may be clicked on to access a corresponding item detail page. In some embodiments, the search results returned in a given search may include both external web pages and items selected from an internally-hosted electronic catalog.
  • As depicted by block 112, the search application then sends a separate query to the event history server 32 for each search result item—or at least those that are to be displayed on the current search result page—to determine whether the user previously accessed that item. For general web searches, each such query may be in the form of “has user X selected URL=<URL value> before?” For catalog searches, each query may be in the form of “has user X selected catalog item=<item ID> before?” As described below, the event history server 32 preferably uses Bloom filters to efficiently process these types of queries, although the use of Bloom filters may alternatively be omitted.
  • As depicted by block 114, for each search result item found to have been previously accessed by the user (if any), an additional query is preferably sent to the event history server 32 to request the date (time) of the last user's last access to that item. Finally, as depicted in block 116, a search results page is generated with embedded viewed-item annotations of the type shown in FIG. 3. The search application may also take the viewed/not-viewed status of each search result item into consideration in ranking/ordering the search result items for display.
  • As will be apparent, the process depicted by FIG. 4 can be varied such that the event history server 32 is not actually accessed in response to the search queries. For example, to reduce the load on the event history server 32, the event data indicative of specific search result URLs selected by specific users can be periodically retrieved from the event history server 32 and stored on a separate “search personalization” server. This separate server can then be assigned to the task of responding to requests of the type “has user X accessed external URL Y?” The same is true for the process of FIG. 5, described below.
  • The search application's user interface may also provide an option for the user to restrict the scope of the search to items previously viewed, items not previously viewed, or items viewed within a particular time period (e.g., the last seven days). This feature may be implemented using the same process flow as in FIG. 4, except that the query results returned by the event history server 32 will be used to determine which search result items are to be displayed.
  • As will be apparent, the foregoing search results personalization features, as well as those described below with reference to FIG. 5, may also be applied to searches for other types of items. For example, in the context of an online auction site, the results of an auction search may be annotated to indicate which of the located auctions have been viewed by the user, when each auction was viewed, and possibly whether the user has submitted a bid on each such auction. Similarly, the results of a search of bulletin board postings or blog (web log) postings may be annotated to indicate if/when specific postings were viewed by the user.
  • Referring again to FIG. 3, the second search result item 120 illustrates another feature that may be implemented using the event history server 32. This feature involves determining whether the user previously submitted the same search query, and if so, whether any new search result items (i.e., items not present in the prior search results set) have been found. In this particular example, the search results page reveals that the user previously conducted the same search on February 14, and that the item corresponding to the URL “lordotrings.com” is a new item that did not come up in the prior search.
  • FIG. 5 illustrates the general process by which a search application 38 may interact with the event history server 32 to implement this “new-item annotations” feature. This process may be combined with that of FIG. 4 to generate annotated search results pages of the type shown in FIG. 3. As illustrated in FIG. 5, the search application initially receives and executes the search query (block 130), and queries the event history server 32 to determine whether the user has previously submitted the same query (block 132). If the user has not submitted this query, the search results page is generated (block 140) without adding any “new item” annotations.
  • If the same search query was previously submitted, the event history server 32 is again queried for the time of the last submission (block 134). In addition, as depicted in block 136, the event history server 32 is queried to determine which of the current search result items, if any, have not been displayed to the user (i.e., have not been the subject of an impression event); this query may optionally be limited in scope to impressions occurring at the time of or shortly after the prior search. As depicted by block 138, if any new search result items exist in the current search result set, they are annotated as shown in FIG. 3 (item 120). The relevance rankings of the new items may also be augmented to increase the likelihood that the new items will be displayed.
  • One variation of the method shown in FIG. 5 is to allow the user to explicitly limit the (repeat) search to items that did not come up in a prior execution of the same search query. This option may, for example, be provided as a check box on the web site's search page.
  • IV. Use of Bloom Filters to Determine Whether User Previously Viewed or Accessed a Given Element
  • As mentioned above, Bloom filters may be used by the event history server 32 to reduce the need for persistent data retrieval when responding to a query of the form “does event of type T and value V exist in history of user X?” For example, Bloom filters may be used to determine whether a particular user has viewed or selected a particular URL.
  • By way of background, a Bloom filter is a bit sequence or array generated according to a set of hash functions. Bloom filters are used to quickly test whether a particular item is a member of a large set of items. One common application for Bloom filters is to test whether a given object (as identified by the object's URL) is currently stored in a cache of web pages. Specifically, when an object is added to the cache, the hash functions are applied to the object's URL to determine which of the bits in the Bloom filter are to be turned ON. When an object is requested, these hash functions are again applied to the requested object's URL, and a test is then performed to determine whether all of the corresponding bits in the Bloom filter are turned ON. If one or more of the bits are not ON, the object is not stored in the cache. If, on the other hand, all of the bits are ON, there is a very high likelihood that the requested object is in the cache. Thus, “false positives” or “false hits” are possible, but “false negatives” or “false misses” generally are not.
  • According to one aspect of the invention, one or more Bloom filters are generated for a given user to describe some aspect or segment of that user's event history. The Bloom filters are preferably generated and stored by the persistent storage layer 44 (FIG. 1), and are passed to the cache layer 40 for purposes of responding to queries. Different Bloom filters may be generated for a given user for responding to different types of queries. For example, different types of Bloom filters may be generated for different types of activity (e.g., URL accesses, URL impressions, URL accesses plus impressions, catalog item accesses, mouse over events, etc.). In addition, different Bloom filters may be generated for different time periods.
  • FIG. 6 illustrates the general process by which a Bloom filter may be used to test for URL accesses by a recognized user, User X. Although this diagram is specific to URL accesses, the illustrated process flow also applies to other types of event activity. In step 1 of FIG. 6, a storage layer server 46 generates one or more Bloom filters for User X. This step may, for example, be performed in response to receiving an associated query or update for User X. To generate a Bloom filter specifically for URL accesses, the storage layer service code (FIG. 2) initially retrieves URL access events for User X, applies a set of hash functions to each accessed URL, and sets the associated Bloom filter bits. As discussed below, the size of the Bloom filter may be selected to enable storage of a desired number of events while maintaining a false-positive rate below a desired threshold. Bloom filters generated by one storage layer server 46 may be passed to the other storage layer server(s) by the synchronization service. The bloom filters may additionally or alternatively be generated by the cache layer servers 42.
  • In step 2 of FIG. 6, a cache layer server receives a query of the form “has User X accessed URL Y?” In the context of the search results annotation features described above, many such queries may be received for a given user for purposes of generating a single search results page. In step 3, the cache layer server 42 retrieves the relevant Bloom filter from one of the storage layer servers 46 if the Bloom filter is not already stored in the cache 43.
  • In step 4, the cache layer server 42 tests the relevant Bloom filter to see if the corresponding bits for the URL are ON. If one or more of the bits are OFF (meaning that no accesses to URL Y exist in the relevant event history of User X), the cache layer server 42 returns an answer of NO (step 5), without passing the query to the persistent storage layer. If, on the other hand, all of the bits are ON (meaning that the URL access very likely exists within User X's event history), the query is passed to one of the storage layer servers 46 (step 6) to check User X's actual event data for the URL access. In step 7, the storage layer server 46 returns a response to the query via the cache layer server 42. As an alternative to querying the storage layer server (step 6), the cache layer server can be designed to simply return a YES response when the Bloom filter test is positive, although this approach may cause in accurate results to be presented to users on rare occasions.
  • As updates reflective of URL accesses are thereafter received for User X, the cache layer server 42 (but preferably not the storage layer server 46) updates its copy of the associated Bloom filter to reflect these updates. For example, if User X selects a search result item (URL) from a web search results page of the type shown in FIG. 3, the associated Bloom filter will be updated within the cache 43 to set the bits associated with the selected URL. Thus, the Bloom filter used by the cache layer to respond to queries reflects the most recent browsing activities of the relevant user. At some point, the Bloom filter may be purged from the cache 43 due to inactivity, at which time the updated Bloom filter is written to the persistent storage layer (in place of the original version) for further use.
  • At some point, a given Bloom filter may reach its capacity, meaning that it cannot store additional events without exceeding a desired average false positive rate. At this point, the Bloom filter may be replaced with a larger Bloom filter (e.g., 8 Kilobytes rather than 4 Kilobytes) in order to provide greater event capacity.
  • The foregoing description focuses on the generation and use of Bloom filters for recognized users. Bloom filters may also be generated for unrecognized users by the cache layer servers 42. For example, at the outset of a browsing session, the assigned cache layer server 42 may generate a Bloom filter for a user, and may thereafter update the Bloom filter with new events for that user. This “session-specific” Bloom filter may be used to respond to queries in the same way as described above.
  • V. Browser-Based Reporting of Event Data
  • FIG. 7 illustrates an embodiment in which the event history server 32 records event data reported by a browser-based event reporting component 160. The event reporting component 160 runs as a component of a web browser 162 on some or all of the computers 36 of users of the event history server 32. As illustrated, the event reporting component 160 is preferably implemented as part of a browser toolbar component 164. The toolbar component 164 may, for example, be provided as an optional browser plug-in that can be downloaded and installed by users. The event reporting component 160 may alternatively be implemented as a standalone browser plug-in, as part of a plug-in other than a toolbar, or as part of the native code of the web browser 162.
  • The browser-based event reporting component 160 preferably reports event data for all web sites and pages accessed by the user. For example, the event reporting component 160 may report every mouse click or other selection event on every web page accessed by the user. The event reporting component 160 may also report other types of browsing events, such as mouse-over events, impressions, selections of the “back” button on the web browser 162, etc.
  • The browser-based event reporting component 160 may take the place of the server-based event reporting component 35 of FIG. 1. Alternatively, both types of event reporting components 35, 160 may be used within a given system. For example, for users that do not have the toolbar 164 installed, the event history server 32 may only capture data reported by the server-based event reporting component 35, in which case the event data may only reflect events that occur during browsing of one or more specific web sites. For users that have the toolbar 164 installed on their respective computers 36, the captured event data may also extend to other web sites.
  • The event data collected from the browser-based event reporting component 160 may be used to provide a variety of different personalization services to users. For example, a service may be provided for allowing users to view a listing of all web sites they have respectively accessed that satisfy some user-specified criteria. Using this service, users may, for example, view listings of all payment transactions they have respectively made on the web, or view a history of all travel-related web sites they have accessed. The data fields included within the event objects may be supplemented as needed to implement such a service.
  • As depicted in FIG. 7, personalized toolbar content may be generated by a server-side toolbar personalization application 170. This application 170 may use event data retrieved from the event history server 32 to generate context-sensitive toolbar messages for display to users. For example, when a user accesses a particular web site, the toolbar personalization application 170 may retrieve and display a history of transactions performed by the user on that web site. Further, the toolbar may be personalized with real time information about all of the web sites or pages visited during the current browsing session.
  • VI. Other Personalization Applications
  • As will be recognized, numerous other types of personalization applications and features are made possible by the event history server 32. As mentioned above, one such application involves allowing users to view, organize, and possibly annotate their respective event histories. This may be accomplished in part by providing a user interface, such as a set of web pages, through which users can create event history folders, and select events to add to such folders. An event search engine may also be provided through which users can search their respective event histories by event type, event value, event time-of-occurrence, and various other criteria. As mentioned above, users may also be permitted to “delete” specific events from their respective event histories.
  • Although this invention has been described in terms of certain preferred embodiments and applications, other embodiments and applications that are apparent to those of ordinary skill in the art, including embodiments which do not provide all of the features and advantages set forth herein, are also within the scope of this invention. Accordingly, the scope of the present invention is intended to be defined only by reference to the appended claims

Claims (19)

1. A system that provides functionality for conducting searches, the system comprising:
a search engine system that is responsive to search queries received over a network from user computing devices of users by generating and returning search results pages listing corresponding search results, said search results including uniform resource locators of responsive resources, said search engine system providing functionality, including a user interface, that enables users to annotate particular search results, and to subsequently recall such annotations for viewing; and
a server that persistently stores event data in association with particular users of the search engine system, said event data comprising search result annotations created by particular users, said server including a query interface that enables the search engine system to selectively retrieve the persistently stored event data associated with particular users.
2. The system of claim 1, wherein the search engine system additionally provides functionality for the users to publish their respective search result annotations to other users.
3. The system of claim 1, wherein the user interface includes functionality for users to view and organize their respective event histories.
4. The system of claim 1, wherein the server is configured to store a search result annotation submitted by a user as an event object that is separately retrievable via the query interface.
5. The system of claim 4, wherein the event object includes an event type identifier and an event timestamp.
6. The system of claim 1, wherein the server is additionally configured to store event data descriptive of search result viewing events, and the search engine system is configured to personalize search results page for a user with annotations indicative of when the user previously viewed particular search results, said annotations based on the event data descriptive of search result viewing events.
7. The system of claim 1, wherein the server stores event data for each of a plurality of defined event types, including an annotation event type.
8. The system of claim 7, wherein the query interface provides functionality for selectively retrieving the event data based on at least user ID, event type, and event time-of-occurrence.
9. The system of claim 1, wherein the server comprises at least one persistent storage layer machine that persistently stores the event data, and comprises a plurality of cache layer machines that cache event data of particular users during browsing sessions of such users, wherein the search engine system is configured to send queries to the cache layer machines to request event data.
10. A method, comprising:
receiving a search query submission from a user computing device associated with a user;
executing the search query to identify a plurality of search results that are responsive to the search query;
outputting a representation of the search results to the user computing device for presentation to the user;
providing an option for the user to annotate the search results, and receiving a resulting search result annotation submitted by the user;
persistently storing the search result annotation in association with the user;
subsequently retrieving the persistently stored search result annotation by execution of a query; and
outputting the search result annotation for display to the user;
said method performed in its entirety by a computer-implemented system that comprises a plurality of server machines.
11. The method of claim 10, further comprising, by said computer-implemented system, providing an option for the user to publish the search result annotation to other users.
12. The method of claim 10, further comprising, by said computer-implemented system, publishing the search query annotation to other users.
13. The method of claim 10, wherein persistently storing the search result annotation comprises persistently storing, on a server, an event object that includes at least the search result annotation and an event timestamp.
14. The method of claim 13, wherein retrieving the search result annotation comprises receiving said query from an application, and, in response to the query, returning the event object to the application.
15. The method of claim 10, further comprising recording, in association with the user, event data that identifies specific search result URLs selected by the user for viewing, and using said event data to personalize search results pages for the user.
16. The method of claim 10, wherein the computer-implemented system is a web site system that hosts a web site that provides functionality for conducting Internet searches.
17. A system, comprising
a computer system comprising a plurality of servers, said computer system configured to perform a process that comprises:
receiving a search query submission from a user computing device associated with a user;
executing the search query to identify a plurality of search results that are responsive to the search query;
outputting a representation of the search results to the user computing device for presentation to the user;
providing an option for the user to annotate the search results, and receiving a resulting search result annotation submitted by the user;
persistently storing the search result annotation in association with the user;
subsequently retrieving the persistently stored search result annotation; and
outputting the search result annotation for display to the user.
18. The system of claim 17, wherein the computer system is additionally configured to provide an option for the user to publish the search result annotation to other users.
19. The system of claim 17, wherein the computer system is additionally configured to publish the search query annotation to other users.
US13/098,191 2003-07-02 2011-04-29 Search annotation and personalization services Abandoned US20110208711A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/098,191 US20110208711A1 (en) 2003-07-02 2011-04-29 Search annotation and personalization services

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/612,395 US7565425B2 (en) 2003-07-02 2003-07-02 Server architecture and methods for persistently storing and serving event data
US11/325,009 US7945637B2 (en) 2003-07-02 2006-01-04 Server architecture and methods for persistently storing and serving event data
US13/098,191 US20110208711A1 (en) 2003-07-02 2011-04-29 Search annotation and personalization services

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/325,009 Continuation US7945637B2 (en) 2003-07-02 2006-01-04 Server architecture and methods for persistently storing and serving event data

Publications (1)

Publication Number Publication Date
US20110208711A1 true US20110208711A1 (en) 2011-08-25

Family

ID=34062354

Family Applications (4)

Application Number Title Priority Date Filing Date
US10/612,395 Active 2026-06-11 US7565425B2 (en) 2003-07-02 2003-07-02 Server architecture and methods for persistently storing and serving event data
US11/325,009 Expired - Fee Related US7945637B2 (en) 2003-07-02 2006-01-04 Server architecture and methods for persistently storing and serving event data
US12/502,165 Expired - Lifetime US7895325B2 (en) 2003-07-02 2009-07-13 Server architecture and methods for storing and serving event data
US13/098,191 Abandoned US20110208711A1 (en) 2003-07-02 2011-04-29 Search annotation and personalization services

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US10/612,395 Active 2026-06-11 US7565425B2 (en) 2003-07-02 2003-07-02 Server architecture and methods for persistently storing and serving event data
US11/325,009 Expired - Fee Related US7945637B2 (en) 2003-07-02 2006-01-04 Server architecture and methods for persistently storing and serving event data
US12/502,165 Expired - Lifetime US7895325B2 (en) 2003-07-02 2009-07-13 Server architecture and methods for storing and serving event data

Country Status (5)

Country Link
US (4) US7565425B2 (en)
EP (1) EP1652027A4 (en)
JP (1) JP2007526537A (en)
CA (1) CA2530565C (en)
WO (1) WO2005006129A2 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110213805A1 (en) * 2004-03-15 2011-09-01 Yahoo! Inc. Search systems and methods with integration of user annotations
US20130024431A1 (en) * 2011-07-22 2013-01-24 Microsoft Corporation Event database for event search and ticket retrieval
US8510287B1 (en) 2012-04-08 2013-08-13 Microsoft Corporation Annotating personalized recommendations
US20130254642A1 (en) * 2012-03-20 2013-09-26 Samsung Electronics Co., Ltd. System and method for managing browsing histories of web browser
US20140025684A1 (en) * 2012-07-20 2014-01-23 Apple Inc. Indexing and searching a data collection
US20140280905A1 (en) * 2013-03-15 2014-09-18 One Source Virtual Hr, Inc. System and method for service provision in a multi-tenant environment
US10956481B2 (en) 2016-07-29 2021-03-23 Splunk Inc. Event-based correlation of non-text machine data
US11227208B2 (en) 2016-07-29 2022-01-18 Splunk Inc. Automated data-generation for event-based system
US11314799B2 (en) 2016-07-29 2022-04-26 Splunk Inc. Event-based data intake and query system employing non-text machine data
US11636311B2 (en) 2016-07-29 2023-04-25 Splunk Inc. Anomaly detection based on predicted textual characters

Families Citing this family (288)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7801905B1 (en) * 2003-11-25 2010-09-21 Prabhdeep Singh Knowledge archival and recollection systems and methods
US10296919B2 (en) 2002-03-07 2019-05-21 Comscore, Inc. System and method of a click event data collection platform
US8095589B2 (en) 2002-03-07 2012-01-10 Compete, Inc. Clickstream analysis methods and systems
US20080189408A1 (en) 2002-10-09 2008-08-07 David Cancel Presenting web site analytics
US7885974B2 (en) * 2002-11-18 2011-02-08 Aol Inc. Method and apparatus providing omnibus view of online and offline content of various file types and sources
US7567979B2 (en) * 2003-08-15 2009-07-28 Microsoft Corporation Expression-based web logger for usage and navigational behavior tracking
US7756750B2 (en) 2003-09-02 2010-07-13 Vinimaya, Inc. Method and system for providing online procurement between a buyer and suppliers over a network
US7505964B2 (en) 2003-09-12 2009-03-17 Google Inc. Methods and systems for improving a search ranking using related queries
US7454417B2 (en) 2003-09-12 2008-11-18 Google Inc. Methods and systems for improving a search ranking using population information
US7386791B2 (en) 2003-09-24 2008-06-10 Format Dynamics, Llc Method and systems for creating a digital document altered in response to at least one event
US20050097089A1 (en) * 2003-11-05 2005-05-05 Tom Nielsen Persistent user interface for providing navigational functionality
US8521725B1 (en) 2003-12-03 2013-08-27 Google Inc. Systems and methods for improved searching
US20060230040A1 (en) * 2003-12-08 2006-10-12 Andy Curtis Methods and systems for providing a response to a query
US7451131B2 (en) * 2003-12-08 2008-11-11 Iac Search & Media, Inc. Methods and systems for providing a response to a query
US7181447B2 (en) * 2003-12-08 2007-02-20 Iac Search And Media, Inc. Methods and systems for conceptually organizing and presenting information
US7984175B2 (en) 2003-12-10 2011-07-19 Mcafee, Inc. Method and apparatus for data capture and analysis system
US8656039B2 (en) * 2003-12-10 2014-02-18 Mcafee, Inc. Rule parser
US20050131876A1 (en) * 2003-12-10 2005-06-16 Ahuja Ratinder Paul S. Graphical user interface for capture system
US7899828B2 (en) * 2003-12-10 2011-03-01 Mcafee, Inc. Tag data structure for maintaining relational data over captured objects
US7774604B2 (en) * 2003-12-10 2010-08-10 Mcafee, Inc. Verifying captured objects before presentation
US8548170B2 (en) * 2003-12-10 2013-10-01 Mcafee, Inc. Document de-registration
US7814327B2 (en) 2003-12-10 2010-10-12 Mcafee, Inc. Document registration
US7774721B2 (en) * 2003-12-15 2010-08-10 Microsoft Corporation Intelligent backward resource navigation
US7890526B1 (en) 2003-12-30 2011-02-15 Microsoft Corporation Incremental query refinement
US7281008B1 (en) * 2003-12-31 2007-10-09 Google Inc. Systems and methods for constructing a query result set
US8954420B1 (en) 2003-12-31 2015-02-10 Google Inc. Methods and systems for improving a search ranking using article information
US20050149498A1 (en) * 2003-12-31 2005-07-07 Stephen Lawrence Methods and systems for improving a search ranking using article information
US7930540B2 (en) * 2004-01-22 2011-04-19 Mcafee, Inc. Cryptographic policy enforcement
US7925657B1 (en) 2004-03-17 2011-04-12 Google Inc. Methods and systems for adjusting a scoring measure based on query breadth
US8386728B1 (en) 2004-03-31 2013-02-26 Google Inc. Methods and systems for prioritizing a crawl
US8099407B2 (en) 2004-03-31 2012-01-17 Google Inc. Methods and systems for processing media files
US8346777B1 (en) * 2004-03-31 2013-01-01 Google Inc. Systems and methods for selectively storing event data
US8631076B1 (en) 2004-03-31 2014-01-14 Google Inc. Methods and systems for associating instant messenger events
US7941439B1 (en) 2004-03-31 2011-05-10 Google Inc. Methods and systems for information capture
US20050234929A1 (en) * 2004-03-31 2005-10-20 Ionescu Mihai F Methods and systems for interfacing applications with a search engine
US7412708B1 (en) 2004-03-31 2008-08-12 Google Inc. Methods and systems for capturing information
US7333976B1 (en) * 2004-03-31 2008-02-19 Google Inc. Methods and systems for processing contact information
US7725508B2 (en) 2004-03-31 2010-05-25 Google Inc. Methods and systems for information capture and retrieval
US8161053B1 (en) 2004-03-31 2012-04-17 Google Inc. Methods and systems for eliminating duplicate events
US7680888B1 (en) 2004-03-31 2010-03-16 Google Inc. Methods and systems for processing instant messenger messages
US8275839B2 (en) * 2004-03-31 2012-09-25 Google Inc. Methods and systems for processing email messages
US7499958B1 (en) * 2004-03-31 2009-03-03 Google Inc. Systems and methods of replicating all or part of a data store
US20050223027A1 (en) * 2004-03-31 2005-10-06 Lawrence Stephen R Methods and systems for structuring event data in a database for location and retrieval
US7581227B1 (en) * 2004-03-31 2009-08-25 Google Inc. Systems and methods of synchronizing indexes
US8219531B2 (en) * 2004-04-05 2012-07-10 George Eagan Knowledge archival and recollection systems and methods
GB0409582D0 (en) * 2004-04-29 2004-06-02 British Telecomm Event notification network
US7962591B2 (en) * 2004-06-23 2011-06-14 Mcafee, Inc. Object classification in a capture system
US7761439B1 (en) 2004-06-30 2010-07-20 Google Inc. Systems and methods for performing a directory search
US8676922B1 (en) 2004-06-30 2014-03-18 Google Inc. Automatic proxy setting modification
US7437364B1 (en) * 2004-06-30 2008-10-14 Google Inc. System and method of accessing a document efficiently through multi-tier web caching
US8224964B1 (en) 2004-06-30 2012-07-17 Google Inc. System and method of accessing a document efficiently through multi-tier web caching
US8560534B2 (en) * 2004-08-23 2013-10-15 Mcafee, Inc. Database for a capture system
US7483916B2 (en) * 2004-08-23 2009-01-27 Mcafee, Inc. Database for a capture system
US7949849B2 (en) * 2004-08-24 2011-05-24 Mcafee, Inc. File system for a capture system
US8341143B1 (en) 2004-09-02 2012-12-25 A9.Com, Inc. Multi-category searching
US7873622B1 (en) 2004-09-02 2011-01-18 A9.Com, Inc. Multi-column search results interface
US7440968B1 (en) 2004-11-30 2008-10-21 Google Inc. Query boosting based on classification
US8874570B1 (en) 2004-11-30 2014-10-28 Google Inc. Search boost vector based on co-visitation information
US8364670B2 (en) * 2004-12-28 2013-01-29 Dt Labs, Llc System, method and apparatus for electronically searching for an item
US8302011B2 (en) 2005-01-24 2012-10-30 A9.Com, Inc. Technique for modifying presentation of information displayed to end users of a computer system
US7861154B2 (en) * 2005-02-28 2010-12-28 Microsoft Corporation Integration of annotations to dynamic data sets
US8131736B1 (en) * 2005-03-01 2012-03-06 Google Inc. System and method for navigating documents
US8060463B1 (en) 2005-03-30 2011-11-15 Amazon Technologies, Inc. Mining of user event data to identify users with common interests
US20060224583A1 (en) * 2005-03-31 2006-10-05 Google, Inc. Systems and methods for analyzing a user's web history
US7587387B2 (en) 2005-03-31 2009-09-08 Google Inc. User interface for facts query engine with snippets from information sources that include query terms and answer terms
US8239394B1 (en) * 2005-03-31 2012-08-07 Google Inc. Bloom filters for query simulation
US7783631B2 (en) * 2005-03-31 2010-08-24 Google Inc. Systems and methods for managing multiple user accounts
US20060224608A1 (en) * 2005-03-31 2006-10-05 Google, Inc. Systems and methods for combining sets of favorites
US7747632B2 (en) * 2005-03-31 2010-06-29 Google Inc. Systems and methods for providing subscription-based personalization
US7953720B1 (en) 2005-03-31 2011-05-31 Google Inc. Selecting the best answer to a fact query from among a set of potential answers
US9256685B2 (en) * 2005-03-31 2016-02-09 Google Inc. Systems and methods for modifying search results based on a user's history
US7962462B1 (en) 2005-05-31 2011-06-14 Google Inc. Deriving and using document and site quality signals from search query streams
US7512850B2 (en) * 2005-07-15 2009-03-31 Tabula, Inc. Checkpointing user design states in a configurable IC
US7831913B2 (en) * 2005-07-29 2010-11-09 Microsoft Corporation Selection-based item tagging
US9105028B2 (en) 2005-08-10 2015-08-11 Compete, Inc. Monitoring clickstream behavior of viewers of online advertisements and search results
US7907608B2 (en) * 2005-08-12 2011-03-15 Mcafee, Inc. High speed packet capture
US7966395B1 (en) * 2005-08-23 2011-06-21 Amazon Technologies, Inc. System and method for indicating interest of online content
US7818326B2 (en) * 2005-08-31 2010-10-19 Mcafee, Inc. System and method for word indexing in a capture system and querying thereof
US7496557B2 (en) * 2005-09-30 2009-02-24 International Business Machines Corporation Microhubs and its applications
US7730011B1 (en) 2005-10-19 2010-06-01 Mcafee, Inc. Attributes of captured objects in a capture system
US9697231B2 (en) * 2005-11-09 2017-07-04 Cxense Asa Methods and apparatus for providing virtual media channels based on media search
US7657104B2 (en) * 2005-11-21 2010-02-02 Mcafee, Inc. Identifying image type in a capture system
US7716353B2 (en) * 2005-12-21 2010-05-11 Bmc Software, Inc. Web services availability cache
US9262446B1 (en) 2005-12-29 2016-02-16 Google Inc. Dynamically ranking entries in a personal data book
US7925649B2 (en) 2005-12-30 2011-04-12 Google Inc. Method, system, and graphical user interface for alerting a computer user to new results for a prior search
US7904759B2 (en) * 2006-01-11 2011-03-08 Amazon Technologies, Inc. System and method for service availability management
US20070185870A1 (en) 2006-01-27 2007-08-09 Hogue Andrew W Data object visualization using graphs
US8954426B2 (en) * 2006-02-17 2015-02-10 Google Inc. Query language
US7925676B2 (en) 2006-01-27 2011-04-12 Google Inc. Data object visualization using maps
US8055674B2 (en) * 2006-02-17 2011-11-08 Google Inc. Annotation framework
US7953730B1 (en) * 2006-03-02 2011-05-31 A9.Com, Inc. System and method for presenting a search history
US9037698B1 (en) 2006-03-14 2015-05-19 Amazon Technologies, Inc. Method and system for collecting and analyzing time-series data
US8601112B1 (en) 2006-03-14 2013-12-03 Amazon Technologies, Inc. Method and system for collecting and analyzing time-series data
US7979439B1 (en) 2006-03-14 2011-07-12 Amazon Technologies, Inc. Method and system for collecting and analyzing time-series data
US20070226504A1 (en) * 2006-03-24 2007-09-27 Reconnex Corporation Signature match processing in a document registration system
US8832247B2 (en) * 2006-03-24 2014-09-09 Blue Coat Systems, Inc. Methods and systems for caching content at multiple levels
US8504537B2 (en) 2006-03-24 2013-08-06 Mcafee, Inc. Signature distribution in a document registration system
US7747749B1 (en) 2006-05-05 2010-06-29 Google Inc. Systems and methods of efficiently preloading documents to client devices
US7689614B2 (en) * 2006-05-22 2010-03-30 Mcafee, Inc. Query generation for a capture system
US7958227B2 (en) * 2006-05-22 2011-06-07 Mcafee, Inc. Attributes of captured objects in a capture system
US8010689B2 (en) * 2006-05-22 2011-08-30 Mcafee, Inc. Locational tagging in a capture system
US9443022B2 (en) 2006-06-05 2016-09-13 Google Inc. Method, system, and graphical user interface for providing personalized recommendations of popular search queries
US7574310B2 (en) * 2006-06-12 2009-08-11 Kennedy Robert A Network-enabled electrical power distribution equipment with improved storage system
US8868533B2 (en) 2006-06-30 2014-10-21 International Business Machines Corporation Method and apparatus for intelligent capture of document object model events
US8949406B2 (en) * 2008-08-14 2015-02-03 International Business Machines Corporation Method and system for communication between a client system and a server system
US8583772B2 (en) * 2008-08-14 2013-11-12 International Business Machines Corporation Dynamically configurable session agent
US20080011819A1 (en) * 2006-07-11 2008-01-17 Microsoft Corporation Microsoft Patent Group Verification of hit testing
US20080015878A1 (en) * 2006-07-17 2008-01-17 Yahoo! Inc. Real-time user profile platform for targeted online advertisement and personalization
WO2008091387A2 (en) * 2006-08-07 2008-07-31 Chacha Search, Inc. Electronic previous search results log
US8260910B2 (en) * 2006-09-19 2012-09-04 Oracle America, Inc. Method and apparatus for monitoring a data stream to detect a pattern of data elements using bloom filters
US8260909B2 (en) * 2006-09-19 2012-09-04 Oracle America, Inc. Method and apparatus for monitoring a data stream
US8954412B1 (en) 2006-09-28 2015-02-10 Google Inc. Corroborating facts in electronic documents
US10409849B2 (en) 2006-09-29 2019-09-10 A9.Com, Inc. System and method for displaying columns of search results
US8037060B1 (en) 2006-09-29 2011-10-11 A9.Com, Inc. System and method for displaying columns of search results
US8112425B2 (en) 2006-10-05 2012-02-07 Splunk Inc. Time series search engine
US9824107B2 (en) 2006-10-25 2017-11-21 Entit Software Llc Tracking changing state data to assist in computer network security
US8661029B1 (en) 2006-11-02 2014-02-25 Google Inc. Modifying search result ranking based on implicit user feedback
US8255873B2 (en) * 2006-11-20 2012-08-28 Microsoft Corporation Handling external content in web applications
US7937428B2 (en) * 2006-12-21 2011-05-03 International Business Machines Corporation System and method for generating and using a dynamic bloom filter
US7925678B2 (en) * 2007-01-12 2011-04-12 Loglogic, Inc. Customized reporting and mining of event data
US20080209009A1 (en) * 2007-01-18 2008-08-28 Niraj Katwala Methods and systems for synchronizing cached search results
JP2008181189A (en) * 2007-01-23 2008-08-07 Global Techno:Kk Trail data extracting method
US8271891B1 (en) * 2007-02-02 2012-09-18 Sandia Corporation Computing environment logbook
US9189561B2 (en) 2007-02-10 2015-11-17 Adobe Systems Incorporated Bridge event analytics tools and techniques
US8065275B2 (en) * 2007-02-15 2011-11-22 Google Inc. Systems and methods for cache optimization
US8812651B1 (en) * 2007-02-15 2014-08-19 Google Inc. Systems and methods for client cache awareness
US8938463B1 (en) 2007-03-12 2015-01-20 Google Inc. Modifying search result ranking based on implicit user feedback and a model of presentation bias
US7827170B1 (en) 2007-03-13 2010-11-02 Google Inc. Systems and methods for demoting personalized search results based on personal information
US8347202B1 (en) 2007-03-14 2013-01-01 Google Inc. Determining geographic locations for place names in a fact repository
US8694374B1 (en) 2007-03-14 2014-04-08 Google Inc. Detecting click spam
US20080244428A1 (en) * 2007-03-30 2008-10-02 Yahoo! Inc. Visually Emphasizing Query Results Based on Relevance Feedback
US7881984B2 (en) * 2007-03-30 2011-02-01 Amazon Technologies, Inc. Service for providing item recommendations
US20080244442A1 (en) * 2007-03-30 2008-10-02 Microsoft Corporation Techniques to share information between application programs
US7974888B2 (en) 2007-03-30 2011-07-05 Amazon Technologies, Inc. Services for providing item association data
US7921073B2 (en) * 2007-04-05 2011-04-05 Yahoo! Inc. System and method for determining impression volumes of content items in a taxonomy hierarchy
US9092510B1 (en) 2007-04-30 2015-07-28 Google Inc. Modifying search result ranking based on a temporal element of user feedback
US20080270761A1 (en) * 2007-04-30 2008-10-30 Microsoft Corporation Techniques to generate event contexts for recurring events
US7899815B2 (en) * 2007-05-02 2011-03-01 Yahoo! Inc. Apparatus and methods for providing search benchmarks
US8239751B1 (en) 2007-05-16 2012-08-07 Google Inc. Data from web documents in a spreadsheet
US20090006322A1 (en) * 2007-06-27 2009-01-01 Chang Shannon H Method for Handling Web Search Results to Be Displayed on a Browser
US8122360B2 (en) 2007-06-27 2012-02-21 Kosmix Corporation Automatic selection of user-oriented web content
WO2009003514A1 (en) * 2007-06-29 2009-01-08 Telefonaktiebolaget Lm Ericsson (Publ) Method of processing event notifications and event subscriptions
US8694511B1 (en) 2007-08-20 2014-04-08 Google Inc. Modifying search result ranking based on populations
US20090063590A1 (en) * 2007-08-30 2009-03-05 Microsoft Corporation Operating System Support of Graceful Degradation for Web Applications
US8042055B2 (en) 2007-08-31 2011-10-18 Tealeaf Technology, Inc. Replaying captured network interactions
US8191081B2 (en) * 2007-09-06 2012-05-29 Sap Ag Condition-based event filtering
US7428522B1 (en) 2007-09-27 2008-09-23 Yahoo! Inc. Real-time search term popularity determination, by search origin geographic location
US8909655B1 (en) 2007-10-11 2014-12-09 Google Inc. Time based ranking
US8090740B2 (en) * 2007-10-16 2012-01-03 Microsoft Corp. Search-centric hierarchichal browser history
US8954430B1 (en) * 2007-12-13 2015-02-10 Amazon Technologies, Inc. Persistent searches
US8271878B2 (en) * 2007-12-28 2012-09-18 Amazon Technologies, Inc. Behavior-based selection of items to present on affiliate sites
US20090172021A1 (en) * 2007-12-28 2009-07-02 Kane Francis J Recommendations based on actions performed on multiple remote servers
US7984056B1 (en) 2007-12-28 2011-07-19 Amazon Technologies, Inc. System for facilitating discovery and management of feeds
US20090171968A1 (en) * 2007-12-28 2009-07-02 Kane Francis J Widget-assisted content personalization based on user behaviors tracked across multiple web sites
US20090171754A1 (en) * 2007-12-28 2009-07-02 Kane Francis J Widget-assisted detection and exposure of cross-site behavioral associations
US20090171755A1 (en) * 2007-12-28 2009-07-02 Kane Francis J Behavior-based generation of site-to-site referrals
US8250080B1 (en) 2008-01-11 2012-08-21 Google Inc. Filtering in search engines
US8849838B2 (en) 2008-01-15 2014-09-30 Google Inc. Bloom filter for storing file access history
US20090248612A1 (en) * 2008-03-31 2009-10-01 Morris Robert P Methods, Systems, And Computer Program Products For Providing Prior Values Of A Tuple Element In A Publish/Subscribe System
US8346791B1 (en) 2008-05-16 2013-01-01 Google Inc. Search augmentation
JP2010008601A (en) * 2008-06-25 2010-01-14 Fujitsu Ltd Guide information display device, guide information display method, and program
US9086775B1 (en) 2008-07-10 2015-07-21 Google Inc. Minimizing software based keyboard
US8205242B2 (en) * 2008-07-10 2012-06-19 Mcafee, Inc. System and method for data mining and security policy management
US8180771B2 (en) * 2008-07-18 2012-05-15 Iac Search & Media, Inc. Search activity eraser
US9276747B2 (en) 2008-08-04 2016-03-01 Technology Policy Associates, Llc Remote profile security system
US9253154B2 (en) 2008-08-12 2016-02-02 Mcafee, Inc. Configuration management for a capture/registration system
US8452769B2 (en) * 2008-09-19 2013-05-28 International Business Machines Corporation Context aware search document
US8396865B1 (en) 2008-12-10 2013-03-12 Google Inc. Sharing search engine relevance data between corpora
US8214350B1 (en) * 2009-01-02 2012-07-03 Google Inc. Pre-computed impression lists
US8850591B2 (en) 2009-01-13 2014-09-30 Mcafee, Inc. System and method for concept building
US8706709B2 (en) 2009-01-15 2014-04-22 Mcafee, Inc. System and method for intelligent term grouping
US20100185644A1 (en) * 2009-01-21 2010-07-22 Microsoft Corporatoin Automatic search suggestions from client-side, browser, history cache
US10191982B1 (en) 2009-01-23 2019-01-29 Zakata, LLC Topical search portal
US9607324B1 (en) 2009-01-23 2017-03-28 Zakta, LLC Topical trust network
US10007729B1 (en) 2009-01-23 2018-06-26 Zakta, LLC Collaboratively finding, organizing and/or accessing information
US8473442B1 (en) 2009-02-25 2013-06-25 Mcafee, Inc. System and method for intelligent state management
US9477763B2 (en) * 2009-03-02 2016-10-25 Excalibur IP, LC Personalized search results utilizing previously navigated web sites
US20100229100A1 (en) * 2009-03-03 2010-09-09 Sprint Spectrum L.P. Methods and Systems for Storing and Accessing Application History
US20100227682A1 (en) * 2009-03-04 2010-09-09 Microsoft Corporation Awarding of avatar items in video game environment
US20100228701A1 (en) * 2009-03-06 2010-09-09 Microsoft Corporation Updating bloom filters
US8447722B1 (en) 2009-03-25 2013-05-21 Mcafee, Inc. System and method for data mining and security policy management
US8667121B2 (en) 2009-03-25 2014-03-04 Mcafee, Inc. System and method for managing data and policies
KR20100107801A (en) * 2009-03-26 2010-10-06 삼성전자주식회사 Apparatus and method for antenna selection in wireless communication system
US9934320B2 (en) 2009-03-31 2018-04-03 International Business Machines Corporation Method and apparatus for using proxy objects on webpage overlays to provide alternative webpage actions
US8930818B2 (en) * 2009-03-31 2015-01-06 International Business Machines Corporation Visualization of website analytics
US20100257403A1 (en) * 2009-04-03 2010-10-07 Microsoft Corporation Restoration of a system from a set of full and partial delta system snapshots across a distributed system
US8261126B2 (en) 2009-04-03 2012-09-04 Microsoft Corporation Bare metal machine recovery from the cloud
US9009146B1 (en) 2009-04-08 2015-04-14 Google Inc. Ranking search results based on similar queries
US8862574B2 (en) * 2009-04-30 2014-10-14 Microsoft Corporation Providing a search-result filters toolbar
US8447760B1 (en) 2009-07-20 2013-05-21 Google Inc. Generating a related set of documents for an initial set of documents
US9135277B2 (en) 2009-08-07 2015-09-15 Google Inc. Architecture for responding to a visual query
US9087059B2 (en) * 2009-08-07 2015-07-21 Google Inc. User interface for presenting search results for multiple regions of a visual query
US20110035367A1 (en) * 2009-08-07 2011-02-10 Gupta Ankur K Methods And System For Efficient Crawling Of Advertiser Landing Page URLs
US8498974B1 (en) 2009-08-31 2013-07-30 Google Inc. Refining search results
US8386731B2 (en) * 2009-09-14 2013-02-26 Vmware, Inc. Method and system for optimizing live migration of persistent data of virtual machine using disk I/O heuristics
US9770654B1 (en) 2009-09-30 2017-09-26 Amazon Technologies, Inc. Cross device operation of games
US8414390B1 (en) 2009-09-30 2013-04-09 Amazon Technologies, Inc. Systems and methods for the electronic distribution of games
US8972391B1 (en) 2009-10-02 2015-03-03 Google Inc. Recent interest based relevance scoring
US8874555B1 (en) 2009-11-20 2014-10-28 Google Inc. Modifying scoring data based on historical changes
US8615514B1 (en) 2010-02-03 2013-12-24 Google Inc. Evaluating website properties by partitioning user feedback
US20110208840A1 (en) * 2010-02-22 2011-08-25 Lee Blackman Cookie alert
US8924379B1 (en) 2010-03-05 2014-12-30 Google Inc. Temporal-based score adjustments
US8959093B1 (en) 2010-03-15 2015-02-17 Google Inc. Ranking search results based on anchors
US20110231482A1 (en) * 2010-03-22 2011-09-22 Strangeloop Networks Inc. Automated Optimization Based On Determination Of Website Usage Scenario
US8347021B1 (en) 2010-04-09 2013-01-01 Google Inc. Storing application messages
US8589228B2 (en) * 2010-06-07 2013-11-19 Microsoft Corporation Click modeling for URL placements in query response pages
US8533532B2 (en) * 2010-06-23 2013-09-10 International Business Machines Corporation System identifying and inferring web session events
US9623119B1 (en) 2010-06-29 2017-04-18 Google Inc. Accentuating search results
US8832083B1 (en) 2010-07-23 2014-09-09 Google Inc. Combining user feedback
US8578049B2 (en) 2010-10-04 2013-11-05 Futurewei Technologies, Inc. Content router forwarding plane architecture
US8806615B2 (en) 2010-11-04 2014-08-12 Mcafee, Inc. System and method for protecting specified data combinations
US8346792B1 (en) 2010-11-09 2013-01-01 Google Inc. Query generation using structural similarity between documents
US10068266B2 (en) 2010-12-02 2018-09-04 Vinimaya Inc. Methods and systems to maintain, check, report, and audit contract and historical pricing in electronic procurement
US20120143725A1 (en) * 2010-12-02 2012-06-07 Vinimaya Inc. Methods and systems for influencing search and shopping decisions in electronic procurement
US9697050B2 (en) * 2010-12-22 2017-07-04 Sap Se System and method for scaling for a large number of concurrent users
US9002867B1 (en) 2010-12-30 2015-04-07 Google Inc. Modifying ranking data based on document changes
WO2012115981A1 (en) 2011-02-22 2012-08-30 Tealeaf Technology, Inc. On-page manipulation and real-time replacement of content
US20120240019A1 (en) * 2011-03-17 2012-09-20 Ebay Inc. Method and system for tracking web link usage
US9667713B2 (en) * 2011-03-21 2017-05-30 Apple Inc. Apparatus and method for managing peer-to-peer connections between different service providers
US8498995B1 (en) * 2011-03-24 2013-07-30 Emc Corporation Optimizing data retrieval during event data query processing
US9760414B2 (en) 2011-05-18 2017-09-12 International Business Machines Corporation Preserving event data for lazily-loaded macro components in a publish/subscribe system
US10268656B1 (en) * 2011-05-19 2019-04-23 Palo Alto Networks, Inc. Using cache and bloom filters for URL lookups
US8725730B2 (en) * 2011-05-23 2014-05-13 Hewlett-Packard Development Company, L.P. Responding to a query in a data processing system
US9037696B2 (en) 2011-08-16 2015-05-19 Amazon Technologies, Inc. Managing information associated with network resources
US8832028B2 (en) * 2011-08-25 2014-09-09 Oracle International Corporation Database cloning
US8504906B1 (en) * 2011-09-08 2013-08-06 Amazon Technologies, Inc. Sending selected text and corresponding media content
US8949371B1 (en) * 2011-09-29 2015-02-03 Symantec Corporation Time and space efficient method and system for detecting structured data in free text
WO2013067462A1 (en) * 2011-11-03 2013-05-10 Rockmelt, Inc. Social web browsing
US9313100B1 (en) 2011-11-14 2016-04-12 Amazon Technologies, Inc. Remote browsing session management
US9330188B1 (en) 2011-12-22 2016-05-03 Amazon Technologies, Inc. Shared browsing sessions
US8700561B2 (en) 2011-12-27 2014-04-15 Mcafee, Inc. System and method for providing data protection workflows in a network environment
US9336321B1 (en) 2012-01-26 2016-05-10 Amazon Technologies, Inc. Remote browsing and searching
US8839087B1 (en) 2012-01-26 2014-09-16 Amazon Technologies, Inc. Remote browsing and searching
US8954580B2 (en) 2012-01-27 2015-02-10 Compete, Inc. Hybrid internet traffic measurement using site-centric and panel data
US9900395B2 (en) 2012-01-27 2018-02-20 Comscore, Inc. Dynamic normalization of internet traffic
US10185822B2 (en) * 2012-03-14 2019-01-22 Carbon Black, Inc. Systems and methods for tracking and recording events in a network of computing systems
US20130262445A1 (en) * 2012-04-02 2013-10-03 Pomian & Corella, Llc Browsing real-time search results reliably on a mobile computing device
US10210480B2 (en) * 2012-05-31 2019-02-19 Apple Inc. Avoiding a redundant display of a notification on multiple user devices
US9348936B2 (en) * 2012-07-25 2016-05-24 Oracle International Corporation Heuristic caching to personalize applications
US8631034B1 (en) * 2012-08-13 2014-01-14 Aria Solutions Inc. High performance real-time relational database system and methods for using same
US8943197B1 (en) 2012-08-16 2015-01-27 Amazon Technologies, Inc. Automated content update notification
US10261938B1 (en) 2012-08-31 2019-04-16 Amazon Technologies, Inc. Content preloading using predictive models
US9349123B1 (en) 2012-10-04 2016-05-24 Amazon Technologies, Inc. Hybrid native networked application
US9635094B2 (en) 2012-10-15 2017-04-25 International Business Machines Corporation Capturing and replaying application sessions using resource files
US9536108B2 (en) 2012-10-23 2017-01-03 International Business Machines Corporation Method and apparatus for generating privacy profiles
US9535720B2 (en) 2012-11-13 2017-01-03 International Business Machines Corporation System for capturing and replaying screen gestures
US10474735B2 (en) 2012-11-19 2019-11-12 Acoustic, L.P. Dynamic zooming of content with overlays
US20140149392A1 (en) * 2012-11-28 2014-05-29 Microsoft Corporation Unified search result service and cache update
US9183499B1 (en) 2013-04-19 2015-11-10 Google Inc. Evaluating quality based on neighbor features
US10353957B2 (en) 2013-04-30 2019-07-16 Splunk Inc. Processing of performance data and raw log data from an information technology environment
US10318541B2 (en) 2013-04-30 2019-06-11 Splunk Inc. Correlating log data with performance measurements having a specified relationship to a threshold value
US10997191B2 (en) 2013-04-30 2021-05-04 Splunk Inc. Query-triggered processing of performance data and log data from an information technology environment
US10614132B2 (en) 2013-04-30 2020-04-07 Splunk Inc. GUI-triggered processing of performance data and log data from an information technology environment
US10225136B2 (en) 2013-04-30 2019-03-05 Splunk Inc. Processing of log data and performance data obtained via an application programming interface (API)
US10019496B2 (en) 2013-04-30 2018-07-10 Splunk Inc. Processing of performance data and log data from an information technology environment by using diverse data stores
US10346357B2 (en) 2013-04-30 2019-07-09 Splunk Inc. Processing of performance data and structure data from an information technology environment
US9860143B2 (en) * 2013-06-26 2018-01-02 Nicolas Bissantz System for providing information on the traffic on a group of websites
JP6517468B2 (en) * 2014-01-10 2019-05-22 日本電気株式会社 INFORMATION PROCESSING SYSTEM, INFORMATION PROCESSING APPARATUS, MONITORING APPARATUS, MONITORING METHOD, AND PROGRAM
RU2608668C2 (en) * 2014-07-30 2017-01-23 Общество С Ограниченной Ответственностью "Яндекс" System and method for control and organisation of web-browser cache for offline browsing
US9075812B1 (en) * 2014-09-05 2015-07-07 WhisperText, Inc. System and method for automatically selecting images to accompany text
US10002361B2 (en) 2015-02-27 2018-06-19 Esquify, Inc. Remote supervision of client device activity
US9634992B1 (en) * 2015-02-28 2017-04-25 Palo Alto Networks, Inc. Probabilistic duplicate detection
US10785310B1 (en) * 2015-09-30 2020-09-22 Open Text Corporation Method and system implementing dynamic and/or adaptive user interfaces
US10304082B1 (en) 2015-11-12 2019-05-28 Amazon Technologies, Inc. Personalized network content generation and redirection according to repeat behavior
US9672487B1 (en) 2016-01-15 2017-06-06 FinLocker LLC Systems and/or methods for providing enhanced control over and visibility into workflows where potentially sensitive data is processed by different operators, regardless of current workflow task owner
US9904957B2 (en) * 2016-01-15 2018-02-27 FinLocker LLC Systems and/or methods for maintaining control over, and access to, sensitive data inclusive digital vaults and hierarchically-arranged information elements thereof
US10019588B2 (en) 2016-01-15 2018-07-10 FinLocker LLC Systems and/or methods for enabling cooperatively-completed rules-based data analytics of potentially sensitive data
US20170352034A1 (en) * 2016-06-02 2017-12-07 Samsung Electronics Company, Ltd. Transaction-Record Verification for Mobile-Payment System
CN109155749B (en) 2016-06-21 2021-11-19 甲骨文国际公司 Method and system for associating messages with a conversation
WO2017222617A1 (en) 2016-06-21 2017-12-28 Oracle International Corporation Internet cloud-hosted natural language interactive messaging system server collaboration
JP6952060B2 (en) 2016-06-21 2021-10-20 オラクル・インターナショナル・コーポレイション User Resolver, an interactive messaging system in natural language hosted in the Internet cloud
US11477302B2 (en) 2016-07-06 2022-10-18 Palo Alto Research Center Incorporated Computer-implemented system and method for distributed activity detection
US10832279B2 (en) 2016-08-17 2020-11-10 International Business Machines Corporation Aggregation of unique user invocations in an online environment
JP6883650B2 (en) 2016-09-16 2021-06-09 オラクル・インターナショナル・コーポレイション A natural language interactive messaging system hosted by the Internet cloud with a virtual database
US10740803B2 (en) 2016-11-30 2020-08-11 Facebook, Inc. Scheduling events for a dynamic audience platform
US10536550B2 (en) * 2016-11-30 2020-01-14 Facebook, Inc. Storage of events for a dynamic audience platform
US10970629B1 (en) * 2017-02-24 2021-04-06 Amazon Technologies, Inc. Encodings for reversible sparse dimensionality reduction
US10825064B1 (en) 2017-03-13 2020-11-03 Amazon Technologies, Inc. Preventing duplicate content selection for digital presentation
US11657407B1 (en) * 2017-03-13 2023-05-23 Amazon Technologies, Inc. Filtering data with probabilistic filters for content selection
US20180262404A1 (en) * 2017-03-13 2018-09-13 Microsoft Technology Licensing, Llc Hypermedia-driven record and playback test framework
US10891678B1 (en) 2017-04-18 2021-01-12 Amazon Technologies, Inc. Personalized network content generation and redirection according to time intervals between repeated instances of behavior based on entity size
US10643178B1 (en) 2017-06-16 2020-05-05 Coupa Software Incorporated Asynchronous real-time procurement system
CN109542339B (en) * 2018-10-23 2021-09-03 拉扎斯网络科技(上海)有限公司 Data layered access method and device, multilayer storage equipment and storage medium
CN109361778A (en) * 2018-12-18 2019-02-19 厦门商集网络科技有限责任公司 A kind of method and terminal managing session
US10477287B1 (en) 2019-06-18 2019-11-12 Neal C. Fairbanks Method for providing additional information associated with an object visually present in media content
US11418571B1 (en) 2021-07-29 2022-08-16 Servicenow, Inc. Server-side workflow improvement based on client-side data mining
US11809378B2 (en) 2021-10-15 2023-11-07 Morgan Stanley Services Group Inc. Network file deduplication using decaying bloom filters
CN116389444B (en) * 2023-04-10 2023-09-15 北京智享嘉网络信息技术有限公司 Traffic scheduling method and system based on user web application

Citations (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774123A (en) * 1995-12-15 1998-06-30 Ncr Corporation Apparatus and method for enhancing navigation of an on-line multiple-resource information service
US6310630B1 (en) * 1997-12-12 2001-10-30 International Business Machines Corporation Data processing system and method for internet browser history generation
US20020010625A1 (en) * 1998-09-18 2002-01-24 Smith Brent R. Content personalization based on actions performed during a current browsing session
US20020013834A1 (en) * 1998-04-20 2002-01-31 Jeffrey Esakov Tracking and graphical display of user activity on an information network
US20020032689A1 (en) * 1999-12-15 2002-03-14 Abbott Kenneth H. Storing and recalling information to augment human memories
US20020063735A1 (en) * 2000-11-30 2002-05-30 Mediacom.Net, Llc Method and apparatus for providing dynamic information to a user via a visual display
US20020069407A1 (en) * 2000-11-28 2002-06-06 Navic Systems, Incorporated System and method for reporting counted impressions
US20020103789A1 (en) * 2001-01-26 2002-08-01 Turnbull Donald R. Interface and system for providing persistent contextual relevance for commerce activities in a networked environment
US6448980B1 (en) * 1998-10-09 2002-09-10 International Business Machines Corporation Personalizing rich media presentations based on user response to the presentation
US6453342B1 (en) * 1998-12-03 2002-09-17 International Business Machines Corporation Method and apparatus for selective caching and cleaning of history pages for web browsers
US6460060B1 (en) * 1999-01-26 2002-10-01 International Business Machines Corporation Method and system for searching web browser history
US20020143925A1 (en) * 2000-12-29 2002-10-03 Ncr Corporation Identifying web-log data representing a single user session
US20020143933A1 (en) * 2001-04-03 2002-10-03 International Business Machines Corporation Clickstream data collection technique
US20020147732A1 (en) * 2001-04-04 2002-10-10 Alorica Inc. Method, system, and program for customer service and support management
US6466970B1 (en) * 1999-01-27 2002-10-15 International Business Machines Corporation System and method for collecting and analyzing information about content requested in a network (World Wide Web) environment
US20020178169A1 (en) * 2001-05-23 2002-11-28 Nair Sandeep R. System and method for efficient and adaptive web accesses filtering
US20020198882A1 (en) * 2001-03-29 2002-12-26 Linden Gregory D. Content personalization based on actions performed during a current browsing session
US20030110296A1 (en) * 2001-12-07 2003-06-12 Kirsch Steven T. Method and system for reducing network latency in data communication
US20030188263A1 (en) * 1998-10-19 2003-10-02 Cary Lee Bates Multi-target links for navigating between hypertext documents and the like
US20030229537A1 (en) * 2000-05-03 2003-12-11 Dunning Ted E. Relationship discovery engine
US6667751B1 (en) * 2000-07-13 2003-12-23 International Business Machines Corporation Linear web browser history viewer
US6768994B1 (en) * 2001-02-23 2004-07-27 Trimble Navigation Limited Web based data mining and location data reporting and system
US6785671B1 (en) * 1999-12-08 2004-08-31 Amazon.Com, Inc. System and method for locating web-based product offerings
US20040172595A1 (en) * 2000-03-07 2004-09-02 Microsoft Corporation System and method for annotating web-based document
US20040267700A1 (en) * 2003-06-26 2004-12-30 Dumais Susan T. Systems and methods for personal ubiquitous information retrieval and reuse
US6877007B1 (en) * 2001-10-16 2005-04-05 Anna M. Hentzel Method and apparatus for tracking a user's interaction with a resource supplied by a server computer
US6877077B2 (en) * 2001-12-07 2005-04-05 Sun Microsystems, Inc. Memory controller and method using read and write queues and an ordering queue for dispatching read and write memory requests out of order to reduce memory latency
US20050086188A1 (en) * 2001-04-11 2005-04-21 Hillis Daniel W. Knowledge web
US20050102274A1 (en) * 2002-12-12 2005-05-12 Chen Jay C. Hyperlink Park and Search
US20050128304A1 (en) * 2002-02-06 2005-06-16 Manasseh Frederick M. System and method for traveler interactions management
US6917922B1 (en) * 2001-07-06 2005-07-12 Amazon.Com, Inc. Contextual presentation of information about related orders during browsing of an electronic catalog
US20060004607A1 (en) * 2000-02-24 2006-01-05 Philip Marshall Personalized health history system with accommodation for consumer health terminology
US20070185850A1 (en) * 1999-11-10 2007-08-09 Walters Edward J Apparatus and Method for Displaying Records Responsive to a Database Query
US7295996B2 (en) * 2001-11-30 2007-11-13 Skinner Christopher J Automated web ranking bid management account system
US20080177994A1 (en) * 2003-01-12 2008-07-24 Yaron Mayer System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows
US20110153599A1 (en) * 2002-12-13 2011-06-23 Google Inc. Meta-Web

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7197547B1 (en) * 1999-05-11 2007-03-27 Andrew Karl Miller Load balancing technique implemented in a data network device utilizing a data cache
US6571259B1 (en) * 2000-09-26 2003-05-27 Emc Corporation Preallocation of file system cache blocks in a data storage system
JP3770874B2 (en) * 2000-11-21 2006-04-26 サムスン エレクトロニクス カンパニー リミテッド Regional tunnel management method in mobile communication system using mobile IP

Patent Citations (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774123A (en) * 1995-12-15 1998-06-30 Ncr Corporation Apparatus and method for enhancing navigation of an on-line multiple-resource information service
US6310630B1 (en) * 1997-12-12 2001-10-30 International Business Machines Corporation Data processing system and method for internet browser history generation
US20020013834A1 (en) * 1998-04-20 2002-01-31 Jeffrey Esakov Tracking and graphical display of user activity on an information network
US20020010625A1 (en) * 1998-09-18 2002-01-24 Smith Brent R. Content personalization based on actions performed during a current browsing session
US6448980B1 (en) * 1998-10-09 2002-09-10 International Business Machines Corporation Personalizing rich media presentations based on user response to the presentation
US20030188263A1 (en) * 1998-10-19 2003-10-02 Cary Lee Bates Multi-target links for navigating between hypertext documents and the like
US6453342B1 (en) * 1998-12-03 2002-09-17 International Business Machines Corporation Method and apparatus for selective caching and cleaning of history pages for web browsers
US6460060B1 (en) * 1999-01-26 2002-10-01 International Business Machines Corporation Method and system for searching web browser history
US6466970B1 (en) * 1999-01-27 2002-10-15 International Business Machines Corporation System and method for collecting and analyzing information about content requested in a network (World Wide Web) environment
US20070185850A1 (en) * 1999-11-10 2007-08-09 Walters Edward J Apparatus and Method for Displaying Records Responsive to a Database Query
US6785671B1 (en) * 1999-12-08 2004-08-31 Amazon.Com, Inc. System and method for locating web-based product offerings
US20020032689A1 (en) * 1999-12-15 2002-03-14 Abbott Kenneth H. Storing and recalling information to augment human memories
US20060004607A1 (en) * 2000-02-24 2006-01-05 Philip Marshall Personalized health history system with accommodation for consumer health terminology
US20040172595A1 (en) * 2000-03-07 2004-09-02 Microsoft Corporation System and method for annotating web-based document
US20030229537A1 (en) * 2000-05-03 2003-12-11 Dunning Ted E. Relationship discovery engine
US6667751B1 (en) * 2000-07-13 2003-12-23 International Business Machines Corporation Linear web browser history viewer
US20020069407A1 (en) * 2000-11-28 2002-06-06 Navic Systems, Incorporated System and method for reporting counted impressions
US20020063735A1 (en) * 2000-11-30 2002-05-30 Mediacom.Net, Llc Method and apparatus for providing dynamic information to a user via a visual display
US20020143925A1 (en) * 2000-12-29 2002-10-03 Ncr Corporation Identifying web-log data representing a single user session
US20020103789A1 (en) * 2001-01-26 2002-08-01 Turnbull Donald R. Interface and system for providing persistent contextual relevance for commerce activities in a networked environment
US6768994B1 (en) * 2001-02-23 2004-07-27 Trimble Navigation Limited Web based data mining and location data reporting and system
US20020198882A1 (en) * 2001-03-29 2002-12-26 Linden Gregory D. Content personalization based on actions performed during a current browsing session
US20020143933A1 (en) * 2001-04-03 2002-10-03 International Business Machines Corporation Clickstream data collection technique
US20020147732A1 (en) * 2001-04-04 2002-10-10 Alorica Inc. Method, system, and program for customer service and support management
US20050086188A1 (en) * 2001-04-11 2005-04-21 Hillis Daniel W. Knowledge web
US20020178169A1 (en) * 2001-05-23 2002-11-28 Nair Sandeep R. System and method for efficient and adaptive web accesses filtering
US6917922B1 (en) * 2001-07-06 2005-07-12 Amazon.Com, Inc. Contextual presentation of information about related orders during browsing of an electronic catalog
US6877007B1 (en) * 2001-10-16 2005-04-05 Anna M. Hentzel Method and apparatus for tracking a user's interaction with a resource supplied by a server computer
US7295996B2 (en) * 2001-11-30 2007-11-13 Skinner Christopher J Automated web ranking bid management account system
US6877077B2 (en) * 2001-12-07 2005-04-05 Sun Microsystems, Inc. Memory controller and method using read and write queues and an ordering queue for dispatching read and write memory requests out of order to reduce memory latency
US20030110296A1 (en) * 2001-12-07 2003-06-12 Kirsch Steven T. Method and system for reducing network latency in data communication
US20050128304A1 (en) * 2002-02-06 2005-06-16 Manasseh Frederick M. System and method for traveler interactions management
US20050102274A1 (en) * 2002-12-12 2005-05-12 Chen Jay C. Hyperlink Park and Search
US20110153599A1 (en) * 2002-12-13 2011-06-23 Google Inc. Meta-Web
US20080177994A1 (en) * 2003-01-12 2008-07-24 Yaron Mayer System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows
US20040267700A1 (en) * 2003-06-26 2004-12-30 Dumais Susan T. Systems and methods for personal ubiquitous information retrieval and reuse

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9489463B2 (en) 2004-03-15 2016-11-08 Excalibur Ip, Llc Search systems and methods with integration of user annotations
US20120233154A1 (en) * 2004-03-15 2012-09-13 Yahoo! Inc. Search systems and methods with integration of aggregate user annotations
US9984164B2 (en) * 2004-03-15 2018-05-29 Excalibur Ip, Llc Search systems and methods with integration of aggregate user annotations
US20110213805A1 (en) * 2004-03-15 2011-09-01 Yahoo! Inc. Search systems and methods with integration of user annotations
US20130024431A1 (en) * 2011-07-22 2013-01-24 Microsoft Corporation Event database for event search and ticket retrieval
US20130254642A1 (en) * 2012-03-20 2013-09-26 Samsung Electronics Co., Ltd. System and method for managing browsing histories of web browser
US8510287B1 (en) 2012-04-08 2013-08-13 Microsoft Corporation Annotating personalized recommendations
US20140025684A1 (en) * 2012-07-20 2014-01-23 Apple Inc. Indexing and searching a data collection
US8977626B2 (en) * 2012-07-20 2015-03-10 Apple Inc. Indexing and searching a data collection
US9965339B2 (en) * 2013-03-15 2018-05-08 One Source Virtual Hr, Inc. System and method for service provision in a multi-tenant environment
WO2014149430A1 (en) * 2013-03-15 2014-09-25 One Source Virtual Hr, Inc. System and method for service provision in a multi-tenant environment
US20140280905A1 (en) * 2013-03-15 2014-09-18 One Source Virtual Hr, Inc. System and method for service provision in a multi-tenant environment
US10853151B2 (en) 2013-03-15 2020-12-01 Onesource Virtual, Inc. System and method for service provision in a multi-tenant environment
US10956481B2 (en) 2016-07-29 2021-03-23 Splunk Inc. Event-based correlation of non-text machine data
US11227208B2 (en) 2016-07-29 2022-01-18 Splunk Inc. Automated data-generation for event-based system
US11232146B2 (en) * 2016-07-29 2022-01-25 Splunk Inc. Searching non-text machine data
US11314799B2 (en) 2016-07-29 2022-04-26 Splunk Inc. Event-based data intake and query system employing non-text machine data
US11636311B2 (en) 2016-07-29 2023-04-25 Splunk Inc. Anomaly detection based on predicted textual characters
US11789993B2 (en) 2016-07-29 2023-10-17 Splunk Inc. Correlating non-text machine data using event fields
US11816140B1 (en) 2016-07-29 2023-11-14 Splunk Inc. Non-text machine data processing

Also Published As

Publication number Publication date
US20090276407A1 (en) 2009-11-05
US20060112178A1 (en) 2006-05-25
CA2530565C (en) 2012-07-31
JP2007526537A (en) 2007-09-13
CA2530565A1 (en) 2005-01-20
US7565425B2 (en) 2009-07-21
EP1652027A2 (en) 2006-05-03
US20050033803A1 (en) 2005-02-10
EP1652027A4 (en) 2008-06-04
WO2005006129A2 (en) 2005-01-20
US7895325B2 (en) 2011-02-22
US7945637B2 (en) 2011-05-17
WO2005006129A3 (en) 2006-12-21

Similar Documents

Publication Publication Date Title
US7565425B2 (en) Server architecture and methods for persistently storing and serving event data
US11809504B2 (en) Auto-refinement of search results based on monitored search activities of users
US9443022B2 (en) Method, system, and graphical user interface for providing personalized recommendations of popular search queries
US10394908B1 (en) Systems and methods for modifying search results based on a user&#39;s history
Tanasa et al. Advanced data preprocessing for intersites web usage mining
US7747632B2 (en) Systems and methods for providing subscription-based personalization
US7783631B2 (en) Systems and methods for managing multiple user accounts
US7694212B2 (en) Systems and methods for providing a graphical display of search activity
CA2603087C (en) Systems and methods for analyzing a user&#39;s web history
US8849818B1 (en) Searching via user-specified ratings
US20060224608A1 (en) Systems and methods for combining sets of favorites
US9529861B2 (en) Method, system, and graphical user interface for improved search result displays via user-specified annotations
US8589391B1 (en) Method and system for generating web site ratings for a user
Sathiyamoorthi et al. Data Pre-Processing Techniques for Pre-Fetching and Caching of Web Data through Proxy Server

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION