Source: http://www.google.com/patents/US20060173818?dq=7,177,838
Timestamp: 2014-07-29 10:47:01
Document Index: 321092196

Matched Legal Cases: ['art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600']

Patent US20060173818 - Systems, methods, and media for utilizing electronic document usage ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsSystems, methods and media for utilizing electronic document usage information are disclosed. More particularly, hardware and/or software utilizing electronic document usage information to respond to user search requests with search engines are disclosed. Embodiments include receiving a search request...http://www.google.com/patents/US20060173818?utm_source=gb-gplus-sharePatent US20060173818 - Systems, methods, and media for utilizing electronic document usage information with search enginesAdvanced Patent SearchPublication numberUS20060173818 A1Publication typeApplicationApplication numberUS 11/032,872Publication dateAug 3, 2006Filing dateJan 11, 2005Priority dateJan 11, 2005Also published asUS7421426, US8005811, US20080275871Publication number032872, 11032872, US 2006/0173818 A1, US 2006/173818 A1, US 20060173818 A1, US 20060173818A1, US 2006173818 A1, US 2006173818A1, US-A1-20060173818, US-A1-2006173818, US2006/0173818A1, US2006/173818A1, US20060173818 A1, US20060173818A1, US2006173818 A1, US2006173818A1InventorsViktors Berstis, Randolph ForlenzaOriginal AssigneeViktors Berstis, Forlenza Randolph MExport CitationBiBTeX, EndNote, RefManReferenced by (10), Classifications (14), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetSystems, methods, and media for utilizing electronic document usage information with search enginesUS 20060173818 A1Abstract Systems, methods and media for utilizing electronic document usage information are disclosed. More particularly, hardware and/or software utilizing electronic document usage information to respond to user search requests with search engines are disclosed. Embodiments include receiving a search request from a requesting user and receiving document utilization information associated with one or more electronic documents, where the document utilization information provides an indication of the usage of the electronic documents by one or more users. Further embodiments include generating search results based at least partially on the search request and the document utilization information and transmitting an indication of the search results to the requesting user. Further embodiments include generating statistical information regarding the search results for electronic documents and transmitting the generated statistical information. Images(7) Claims(20)
DETAILED DESCRIPTION OF EMBODIMENTS The following is a detailed description of example embodiments of the invention depicted in the accompanying drawings. The example embodiments are in such detail as to clearly communicate the invention. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intent is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. The detailed descriptions below are designed to make such embodiments obvious to a person of ordinary skill in the art. Systems, methods, and media for utilizing electronic document utilization information to respond to user search requests with search engines are disclosed. In the disclosed embodiments, the document usage system receives a search request, such as one requesting a search based on particular keywords, from a requesting user. The document usage system receives document utilization information associated with one or more electronic documents, where the document utilization information provides an indication of the usage of the electronic documents by one or more users. The document usage system may then generate search results in response to the search request based at least partially on the received document utilization information, after which it transmits an indication of the search results to the requesting user. The document utilization information supplements the information otherwise available to generate search results by providing information regarding how documents have actually been used. The disclosed embodiments improve the quality of search results provided to users by incorporating document utilization information in determining network sites or electronic documents that satisfy a search request (as well as the relative ranking of the search results), resulting in more meaningful and accurate search results. This may result in identification of the particular portion of an electronic document that is likely to be most relevant to the requesting user, further improving the value of the search results. Improved quality of search results may increase the usage and revenue of a search site, as well as increase access to electronic documents for which document utilization information is available. Keyword spamming would often be ineffective when document utilization information is considered, reducing the misleading results created by keyword spamming. While specific embodiments will be described below with reference to particular configurations of hardware and/or software, those of skill in the art will realize that embodiments of the present invention may advantageously be implemented with other substantially equivalent hardware and/or software systems. Turning now to the drawings, FIG. 1 depicts an environment for a system for utilizing electronic document usage information in a search engine according to one embodiment. In the depicted embodiment, the document usage system 100 includes one or more document computer systems 102 in communication with a network 110. Each document computer system 102 may contain a usage tracking module 112 and a document reader 114. A user may view electronic documents using the document reader 114 while the usage tracking module 112 tracks information relating to the user's access of particular electronic documents. In the depicted embodiment, the document usage system 100 also includes one or more aggregator servers 104 in communication with the document computer systems 102 via network 110 for aggregating document usage information gathered from document computer systems 102. The one or more aggregator servers 104 may be in communication with one or more search engine servers 106 via network 120, while the one or more search engine servers 106 may be in communication with one or more user search computer systems 102 via network 130. A user on a user search computer system 108 may use a browser 118 or other program to request a search from a search engine server 106. A search engine server 106 may then provide search results to a user on a user search computer system 108 based at least partially on document usage information received from an aggregator server 104. Electronic documents may be digitized documents that contain text, graphics, photographs, etc. that may be read by various computer systems. Electronic documents may contain text or graphics and may use any type of file format, such as PNG, JPEG, GIF, TIFF, DOC, HTML, PDF, RTF, TXT, MCW, etc. Electronic documents may include any type of document, such as books, eBooks, articles, journals, World Wide Web (Web) pages, etc. Electronic documents may, in one embodiment, include multiple pages and/or other means of organizing the document, such as chapters, sections, volumes, etc. Networks 110, 120, 130 may be any type of data communications channel, such as the Internet, an intranet, a LAN, a WAN, an Ethernet network, a wireless network, a proprietary network, a broadband cable network, etc. Networks 110, 120, and/or 130 may be the same or different networks. The Internet or other public network may be particularly useful as network 110, 120, and 130 when the search engine server 106 is hosting a publicly-accessible search site. Those skilled in the art will recognize, however, that the invention described herein may be implemented utilizing any type or any combination of data communications channels. Document computer systems 102 may include personal computers, workstations, servers, mainframe computers, notebook or laptop computers, desktop computers, PDAs, tablet or palm PCs, set-top boxes, mobile phones, wireless devices, or the like. The usage tracking module 112 may track the user's usage of an electronic document being viewed. Usage of an electronic document may include opening or closing the electronic document, creating or deleting bookmarks in the electronic document, time spent with the electronic document open, printing the electronic document, e-mailing or otherwise transmitting the electronic document, etc. In one embodiment, the usage of the electronic document is tracked based on the portion of the electronic document being used, such as a page, chapter, section, etc. of the document. A user may utilize a document computer system 102 to view or read electronic documents using a document reader 114, such as a browser (e.g., Microsoft Corporation's Microsoft Explorer�, etc.), dedicated electronic document reader software (e.g., Adobe Systems Inc.'s Adobe Acrobat� or Reader), or other software. The document reader 114 may be any software module that is used to display an electronic document. Examples of currently existing document readers 114 include Adobe Systems Inc.'s Adobe Acrobat� or Reader, Microsoft Corporation's Word� or Reader�, Palm Corporation's Reader�, MobiPocket Reader, etc. Aggregator servers 104 may include one or more PCs, workstations, servers, mainframe computers, notebook or laptop computers, desktop computers, or the like, and are described in more detail in relation to FIG. 2. Each aggregator server 104 may include an aggregator module 116 for collecting and aggregating electronic document usage information received from users on a document computer system 102. For example, the aggregator module 116 may aggregate the amount of time that each user spent on a particular page of an electronic document for all users who viewed the document on a document computer system 102. In this embodiment, the aggregator module 116 determines the pages (or other sections or portions) of the electronic document on which users have spent the most time viewing. Time spent viewing a page or other portion of a document may be used as a proxy for the value, utility, or relevance of the information included on that page. The aggregator module 116 may analyze, collect, or aggregate electronic document usage information for electronic documents in any fashion. In one embodiment, a single aggregator server 104 may be used to determine electronic document usage by receiving indications of electronic document usage from the document computer systems 102 and processing the data. The aggregator server 104 of this embodiment may include local storage, such as a hard drive, or may include other storage, such as a hard drive array, remote storage over a network, a Redundant Array of Independent Disks (RAID) system, etc. In another embodiment, a plurality of aggregator servers 104 may be utilized where one aggregator server 104 is designated as a primary aggregator server 104 so that document computer systems 102 will first attempt to transmit usage information to it. Any of the aggregator servers 104 in this embodiment, however, may receive information from the document computer systems 102. The plurality of aggregator servers 104 may replicate their collected information with each of the other aggregator servers 104 so that if one is temporarily disabled or permanently removed, the usage information will still be available. One or more search engine servers 106 may be in communication with any aggregator modules 104 (via network 120) and with any user search computer systems 108. The one or more search engine servers 106 may include one or more PCs, workstations, servers, mainframe computers, notebook or laptop computers, desktop computers, or the like. A search engine server 106 may receive a search request from a user on a user search computer system 108, where the search request may include keywords or other parameters that define the scope of the user's desired search. A search engine server 106 may transmit search results to a user on a user search computer system 108 once the search has been completed. A search engine server 106 may receive aggregated document usage information from an aggregator server 104 to be used or supplement search results for the user. User search computer systems 108 may include personal computers, workstations, servers, mainframe computers, notebook or laptop computers, desktop computers, PDAs, tablet or palm PCs, set-top boxes, mobile phones, wireless devices, or the like. A user search computer system 108 may include a browser 118 for creating and submitting search requests and for viewing search results. Browser 118 may be a graphical browser application that allows a user to view Internet or intranet content such as Microsoft Corporation's Internet Explorer, Netscape Communication Corporation's Navigator, Mozilla, Apple Corporation's Safari, etc. Using a browser 118, a user may connect to a network site associated with a search engine server 106, create and submit a search, and view the search results when the search is completed. Alternatively, a user may use a type of software other than a browser 118 for creating search requests and viewing search results. A single computer system may serve as both document computer system 102 and user search computer system 108. The document usage system 100 of the disclosed embodiments may advantageously provide improved results from search engines, increasing the value of search results to users and ultimately the number of users using a search engine and the potential revenue from the search engine. The document usage system 100 uses document utilization information created from usage information gathered from a plurality of users to supplement search results provided to users. Document utilization information provides an indication of the valuable or relevant portions of a document based on the amount that a document (or portion of a document) has actually been used or bookmarked. For example, if a document matches the search request and thus appears in the search results, the document usage system 100 may point users to the most heavily used sections (i.e., the most relevant), potentially saving the user's time and improving the results. In another example, documents or sections of documents that have been heavily viewed by users may be moved up in the search result list, possibly improving the quality of search results. Heavily viewed documents often provide more relevant and timely information to users, as users are unlikely to spend large amounts of time with documents that are not useful. Referring now to FIG. 2, there is shown an aggregator server 104 of the document usage system 100 of FIG. 1 according to one embodiment. In the embodiment of FIG. 2, the aggregator server 104 includes an aggregator module 116, a user communications module 202, a search engine communications module 204, a usage analysis module 206, a usage credit module 208, and a memory module 210. The aggregator module 116 is described in relation to FIG. 1. The user communications module 202 may receive information, such as usage information, from the document computer systems 102 via the network 110. The user communications module 202 may also transmit information, such as aggregated document utilization information, to the document user computer systems 102. Aggregator server 104 may also include a search engine communications module 204. The search engine communications module 204 may transmit document utilization information (aggregated usage information) or other information to a search engine server 106 via network 120. The search engine communications module 204 may also receive search result statistics or other information from the search engine server 106. The usage analysis module 206 may provide more sophisticated analysis of the usage information collected and aggregated by the aggregator module 116. For example, the usage analysis module 206 may sort and/or analyze the usage information by type of user, class of user, type of usage (e.g., printing, viewing, bookmarking, etc.), different timeframes (e.g., giving more weight to more recent usage), etc. In one embodiment, an administrator or other user may customize the type of analysis that is performed by the usage analysis module 206. The usage credit module 208 may award credits, called usage credits herein, to users who are using electronic documents and providing usage information as a reward to those users. A user may use usage credits to receive discounted or free usage of electronic documents, exchange usage credits for cash or other items, or any other use. A user may also use usage credits to receive benefits from the search engine server 106, such as premium searches (e.g., more accurate, quicker, etc.), quicker searches, searches with less or no advertisements, etc. The usage credit module 208 may also manage awarded usage credits, facilitate users using their usage credits, etc. By providing usage credits to users who are using electronic documents and providing usage information to an aggregator server 104, the document usage system 100 will encourage users to agree to provide usage information. For many users, the incentive of getting usage credits will likely outweigh their reluctance to provide information about their particular usage. Memory module 210 may store any type of information, such as user preferences, electronic documents, document usage information, document utilization information, etc. Any type of memory may be used, including fixed or removable media, permanent or temporary storage, volatile or non-volatile memory, hard drives, CD-ROMs, etc. In one embodiment, memory module 210 may store document identification information, such as document name or identifier, creation or modification date, edition, publisher, document type (e.g., DOC, PDF, etc.), etc. Memory module 210 may maintain usage information in, for example, a table in the memory module 210 organized by document identification. In one embodiment, when no user has provided data for a particular electronic document, memory module 210 may stored an indication that no data exists. Referring now to FIG. 3, there is shown a search engine server 106 of the document usage system 100 of FIG. 1 according to one embodiment. In the embodiment of FIG. 3, the search engine server 106 includes a user communications module 302, an aggregator server module 304, a spider module 306, a search algorithm module 308, an indexer module 310, a usage credit module 208, a statistics credit module 312, and a memory module 314. The user communications module 302 may receive an indication of a search request or other information from a user search computer systems 108 via the network 130. The user communications module 302 may also transmit an indication of search results or other information to a user search computer system 108. The aggregator server module 304 may receive document utilization information from the aggregator server 104 and may also transmit search result statistics to the aggregator server 104. The spider module 306 may search the content of sites and/or documents on a network (e.g., the Internet), after which the indexer module 310 may analyze the content of the sites and/or documents to create an index for the words contained in each. The index may be stored in the memory module 314. Memory module 314 may store any type of information, such as generated indexes, document usage information, search results, etc., and memory module 312 may utilize any type of memory, including fixed or removable media, permanent or temporary storage, volatile or non-volatile memory, hard drives, CD-ROMs, etc. In response to receiving a search request from a user, the search algorithm module 308 may search the index created by the indexer module 310 to determine the items (and the ranking of items) in the-search result. The search result may include a list of documents (and associated network addresses) where the keywords in the search request were found. The search result may include a ranking of �hits�, or sites and documents satisfying the search, based on their likely interest to the requesting user. The search results may also include a selection of the content in the document containing the keywords. In one embodiment, the indexer module 310 and/or search algorithm module 308 may utilize information received by the aggregator server module 304 in addition to the index of keywords. For example, if the number of users or the time spent by users for a plurality of electronic documents is known, the search algorithm module 308 and/or indexer module 310 may rank those electronic documents in any search requests for which they satisfy the keyword search in descending order of usage. An electronic document that has been read more often, in other words, might be ranked higher than an electronic document that has been read less frequently. In another example, the search result may reference the portion of an electronic document that is most utilized (as identified by the aggregator module 104), either by link or the content itself, in the search results generated by the search algorithm module 308. This allows a user viewing the search results to see the content most likely to meet their needs. Each search engine server 106 may also include a usage credit module 208 and a statistics credit module 312. The usage credit module 208 of the search engine server 106 may be similar to the usage credit module 208 of the aggregator server 104, and either or both may grant and manage usage credits. Statistics credit module 312 may grant statistics credit to document providers in exchange for aggregated document utilization information. A document provider (e.g., aggregator server 104 owner, document author, document copyright owner, etc.) may exchange statistics credits for improved services from a search engine provider, such as higher visibility in search results, document utilization information related to other documents, free or discounted advertisements, cash or other items, etc. By providing statistics credits to document providers in exchange for document utilization information, search engine providers are able to encourage document providers to supply document utilization information to improve the quality and content of their searches. Document providers, on the other hand, may receive significant benefits in exchange for information that they are already gathering. The functions of the various modules of FIGS. 2 and 3 may be combined or distributed in any fashion between the aggregator server 104 and search engine server 106. For example, the functions of the aggregator module 302 and the usage analysis module 304 of the aggregator server 104 may be combined into one module. In another example, all of the functions of the components of the aggregator server 104 may be performed by modules of the search engine server 106 instead, eliminating the need for the aggregator server 104 and network 110 as the search engine server 106 would then communicate directly with any document computer systems 102. Other modifications and combinations are possible. FIG. 4 depicts an example of a flow chart 400 for determining electronic document usage information according to one embodiment. The method of flow chart 400 may be performed, in one embodiment, by a usage tracking module 112 of a document computer system 102. Flow chart 400 begins with element 402, detecting usage of an electronic document, such as usage by a user using a document reader 114 on a document computer system 102 to view an electronic document. In one embodiment, an indication of the usage of the electronic document is the time a user spends viewing a particular page. For example, the usage of an electronic document may be the time a user spends viewing a PDF document in a document reader 114. If a user spends a relatively long period of time viewing a particular page, it is evidence that the user finds value in the information contained on that page. Similarly, if the user quickly moves past a page, it may reflect less value to the content on that page. Quickly skipping over a page may reflect a lower value than never seeing a page at all, as an unseen page may have more potential to have value than one that is quickly reviewed and moved past. In another example, the usage of an electronic document may include printing of a page of a document, as printing a page provides another indication that the user finds that page valuable. Element 402 may include detection of any type of usage, including both active and passive uses. Flow chart 400 continues to decision block 404, where it is determined whether the user is actively viewing the electronic document. Optional decision block 404 may provide more accurate usage information as it excludes misleading information, such as when a user leaves a document open for a period of time without actively viewing the document. If it is determined in decision block 404 that the user is not actively viewing the document, the function continues to element 412 and usage information is not transmitted, as there is no valid usage of the electronic document by the user. If the user is actively viewing the electronic document (or if decision block 404 is not used), the function continues to element 406. Any methodology may be used to determine if a user is actively viewing an electronic document. In one embodiment, the expiration of a set time interval without any activity of a user (e.g., user input, etc.) may indicate that the user is no longer actively viewing the document. For example, if no user input is received for ten minutes, the function may determine that the user is no longer active and accordingly will discount any time after the last user input (or expiration of the interval). In another embodiment, use of another function of the computer system provides an indication that the user is not actively viewing an electronic document. For example, if a user is actively utilizing a spreadsheet program, decision block 404 may determine that the user is not actively viewing an electronic document in a document reader 114. In yet another example, a user is not considered to be actively viewing an electronic document if a screensaver activates on the display of a document computer system 102. In addition to detection of usage, flow chart 400 also optionally detects bookmarks created in the electronic document in element 406. Creation or deletion of bookmarks at a particular location in an electronic document is a type of usage of an electronic document that may provide an even more direct relation to the value a user places on the information at that location. Locations may include a page, section, chapter, paragraph, sentence, word, graph, or any other location or object. A user typically creates a bookmark at a location in an electronic document when they desire to be able to quickly get back to that location. Accordingly, a bookmark is good evidence that the user finds the information at that location of value. Similarly, if a user deletes a bookmark, it is good evidence that the user no longer finds the information at that location of value. After detecting usage information and/or bookmark information, element 408 saves usage and/or bookmark information to any type of storage. Flow chart 400 transmits any usage and/or bookmark information to an aggregator server 104 via network 110 in element 410. Flow chart 400 may also transmit information about the user and/or document computer system 102 along with the usage information. After document utilization information is created or aggregated by an aggregator server, the method of flow chart 400 continues to element 412, receiving document utilization information, which may be received from, in one example, an aggregator server 104 via network 110. After receiving aggregated document information, the method of flow chart 400 continues to optional element 414, analyzing document utilization information and any local document usage information. In this element, flow chart 400 compares the document utilization information, which contains aggregate usage information from a plurality of users, to local usage information, such as from the user using the document computer system 102. In this embodiment, a user might find value in seeing how their usage compares to others. The method of flow chart 400 may perform any type of analysis, such as finding similarities or differences in usage, finding the most used pages, finding the common bookmarks, determining recommended additional sections to read for the user, etc. In element 416, the document utilization information and/or any local usage information, or the results of analysis of the two, may be stored locally or remotely, such as on a local hard drive. For example, element 416 stores document utilization information in a file located in the same directory with the electronic document. In another embodiment, element 416 stores document utilization information in the same file as the electronic document, such as by utilizing empty fields, appending the document utilization information at the end of a file, etc. The method of flow chart 400 continues to element 418, displaying an indication of the document utilization information and/or the local usage information to the user. Flow chart 400 may display the information with a document reader 114 or other program and the information may be displayed in any form, such as visual display, auditory display, etc. After element 418, the method terminates. FIG. 5 depicts an example of a flow chart 500 for aggregating electronic document usage information according to one embodiment. The method of flow chart 500 may be performed, in one embodiment, by an aggregator server 104. Flow chart 500 begins with element 502, receiving usage and/or bookmark information, such as from a plurality of users on document computer systems 102. Flow chart 500 may also receive information about the user and/or computer system that transmitted the information along with the document usage information. After receiving usage and/or bookmark information, the method of flow chart 500 then continues to element 504, aggregating usage and/or bookmark information from multiple users and/or document computer systems 102 for a particular electronic document. Aggregation may occur at the page level (collecting usage of that pages among multiple users), or it may occur at different levels of fidelity, such as higher levels (e.g., chapters, sections, articles, etc.) or lower levels (e.g., paragraphs, sentences, etc.). In one embodiment, flow chart 500 determines the amount of time users cumulatively spent on each page of a particular electronic document in element 504. In another embodiment, flow chart 500 determines the percentage of users who bookmarked each page of an electronic document in element 504. Flow chart 500 continues to element 506, creating document utilization information from the aggregated usage and/or bookmark information for a particular document. In one example, document utilization information for a particular electronic document includes the relative amounts of time spent on each page of an electronic document by aggregated users. For example, the document utilization information could indicate that users spent an average of 30 seconds on page 1, two minutes on page 2, and 13 seconds on page three, and so on. A bar chart or histogram-like display could be created illustrating the time spent on each page. Using this visual representation, a user could see that page 2, in this example, is probably the most valuable of the electronic document pages. In other embodiments, flow chart 500 may use more sophisticated processing. In another example, usage information may be determined based on a class of users. For example, users can be divided based on some sort of classification (e.g., experts, physicists, programmers, Ph.D. candidates, etc.) and document utilization information may be created specifically based on that classification. In another embodiment, flow chart 500 may combine different types of usage and/or bookmark information into document utilization information. In this embodiment, flow chart 500 may contain bookmark information, time spent on a page, which pages were printed out, etc., to provide an indication of the value of a particular page or section. Any type of processing is possible, and particular types of processing might be requested by users or administrators, set up as defaults, may be used in response to particular types of data, etc. After creating document utilization information, flow chart 500 designates keywords based on document utilization information in optional element 508. Traditional algorithms choose keywords based primarily on the frequency of appearance of that keyword in a document. In element 508, flow chart 500 may designate keywords based on other factors, such as the frequency of appearance of the keyword weighted by the utilization of the section containing the keyword, bookmarks of pages or sections containing the keyword, etc. A word appearing five times on the most heavily viewed page of a document, for example, may be more relevant to users (and thus more appropriate for a keyword) than a word appearing ten times throughout the entire document. Flow chart 500 may use any type of algorithm or methodology, and any combination of factors, to designate keywords for an electronic document. Flow chart 500 continues to element 510, transmitting document utilization information and/or keywords, such as to a search engine server 106 via network 120 for use in responding to user search requests. Flow chart 500 may also transmit document utilization information directly to users on document computer systems 102 via network 110 so that the document readers 114 may utilize the information. In optional element 512, the method of flow chart 500 receives statistical information showing search engine results. Flow chart 500 may use the received statistical information in element 514 to modify the document utilization information and/or keywords. For example, flow chart 500 may use the received statistical information to provide additional information in the document utilization information, modify keywords based on search result statistical information, etc. If, in one example, a particular portion of a document often satisfied user search criteria, flow chart 500 could use such information to increase the weight given to that portion of the document when creating document utilization information. After element 514, flow chart 500 terminates. FIG. 6 depicts an example of a flow chart 600 for receiving and utilizing electronic document usage information in a search engine according to one embodiment. The method of flow chart 600 may be performed, in one embodiment, by a search engine server 106. Flow chart 600 begins with element 602, receiving a search request from a user. The received search request may be generated by a user inputting keywords (such as on a network site associated with the search engine) using a browser 118 on a user search computer system 108 and then transmitting the request to the search engine server 106. The method of flow chart 600 then continues to element 604, receiving aggregated document utilization information and/or keywords such as from, for example, an aggregator server 104. The method of flow chart 600 then continues to optional element 606, archiving the received document utilization information and/or keywords. The method of flow chart 600 continues to element 608, where the search engine server 106 may generate search results in response to the user's search request, where the search results are based on the keyword index, document utilization information and/or keywords. Flow chart 600 may used the received information in any fashion, such as by giving the information a particular weight versus the search index, using the document utilization information to identify a particular relevant portion of a document, using the document utilization information as factors in determining the search results, etc. By using document utilization information and/or keywords provided by the aggregator server 104, the quality and usefulness of the search results may be improved. Knowledge of which portions of a document are more used than others allows a search engine algorithm to consider the value of a portion of a document when generating search results. Accordingly, flow chart 600 may move documents in which keywords appear in heavily used portions of a document to a higher priority in the search results. In another example, flow chart 600 may identify the content of the most useful portion of a document (as identified by a higher usage) in the search results. After generating search results, the method of flow chart 600 continues to element 610, transmitting an indication of the search results to the requesting user on a user search computer system 108, such as via network 130. The user may then view an indication of the search results on browser 118. In optional element 612 flow chart 600 may generate statistical information regarding search results for particular documents. Statistical information regarding search results may include the number of times a particular document was included in search results, the document's position in search results, the number of times a user followed the link to the document, etc. After element 612, the method of flow chart 600 continues to optional element 614, transmitting the generated statistical information, after which the method terminates. The search engine server 106 may generate and transmit the statistical information to the aggregator server 104 or users on user search computer systems 108 or document computer systems 102 for eventual display. In general, the routines executed to implement the embodiments of the invention, may be part of an operating system or a specific application, component, program, module, object, or sequence of instructions. The computer program of the present invention typically is comprised of a multitude of instructions that will be translated by the native computer into a machine-readable format and hence executable instructions. Also, programs are comprised of variables and data structures that either reside locally to the program or are found in memory or on storage devices. In addition, various programs described hereinafter may be identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature. It will be apparent to those skilled in the art having the benefit of this disclosure that the present invention contemplates methods, systems, and media for utilizing electronic document usage information in search engines. It is understood that the form of the invention shown and described in the detailed description and the drawings are to be taken merely as examples. It is intended that the following claims be interpreted broadly to embrace all the variations of the example embodiments disclosed. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7885952Dec 20, 2006Feb 8, 2011Microsoft CorporationCloaking detection utilizing popularity and market valueUS7925986Sep 27, 2007Apr 12, 2011Veveo, Inc.Methods and systems for a linear character selection display interface for ambiguous text inputUS7962504 *May 24, 2006Jun 14, 2011Aol Inc.Sourcing terms into a search engineUS8005811Jul 1, 2008Aug 23, 2011Google Inc.Systems and media for utilizing electronic document usage information with search enginesUS8073852 *May 16, 2008Dec 6, 2011Google Inc.Systems and media for awarding credits based on provided usage informationUS8190618 *Dec 4, 2007May 29, 2012Google Inc.Systems, methods, and media for aggregating electronic document usage informationUS8463766Nov 28, 2011Jun 11, 2013Google Inc.Systems and media for awarding credits based on provided usage informationUS8725752 *Mar 7, 2012May 13, 2014Yahoo! Inc.Method, apparatus and computer readable medium for indexing advertisements to combine relevance with consumer click feedbackUS20120166445 *Mar 7, 2012Jun 28, 2012Deepayan ChakrabartiMethod, apparatus and computer readable medium for indexing advertisements to combine relevance with consumer click feedbackWO2008148009A1 *May 23, 2008Dec 4, 2008Veveo IncMethod and system for unified searching across and within multiple documents* Cited by examinerClassifications U.S. Classification1/1, 707/E17.108, 705/52, 705/51, 707/999.003International ClassificationG06F7/00, G06F17/30, G06Q99/00, H04K1/00, H04L9/00Cooperative ClassificationG06F17/30864, Y10S707/99945, Y10S707/99933European ClassificationG06F17/30W1Legal EventsDateCodeEventDescriptionSep 23, 2011FPAYFee paymentYear of fee payment: 4Apr 14, 2011ASAssignmentOwner name: GOOGLE INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:026131/0161Effective date: 20110328Feb 22, 2005ASAssignmentOwner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BERSTIS, VIKTORS;FORLENZA, RANDOLPH MICHAEL;REEL/FRAME:015753/0772Effective date: 20041209RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google