US20090271374A1 - Social network powered query refinement and recommendations - Google Patents

Social network powered query refinement and recommendations Download PDF

Info

Publication number
US20090271374A1
US20090271374A1 US12111309 US11130908A US2009271374A1 US 20090271374 A1 US20090271374 A1 US 20090271374A1 US 12111309 US12111309 US 12111309 US 11130908 A US11130908 A US 11130908A US 2009271374 A1 US2009271374 A1 US 2009271374A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
search
query
buddies
buddy
user
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
US12111309
Inventor
David S. Korn
Donald E. Bradford
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.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30943Information retrieval; Database structures therefor ; File system structures therefor details of database functions independent of the retrieved data type
    • G06F17/30964Querying
    • G06F17/30991Presentation or visualization of query results
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30861Retrieval from the Internet, e.g. browsers
    • G06F17/30864Retrieval from the Internet, e.g. browsers by querying, e.g. search engines or meta-search engines, crawling techniques, push systems
    • G06F17/30867Retrieval from the Internet, e.g. browsers by querying, e.g. search engines or meta-search engines, crawling techniques, push systems with filtering and personalisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30943Information retrieval; Database structures therefor ; File system structures therefor details of database functions independent of the retrieved data type
    • G06F17/30964Querying
    • G06F17/30979Query processing

Abstract

Embodiments of the present invention enhance the search experience of a user by looking at the search history of one or more buddies to provide search enhancements to the user. Examples of search enhancements include an annotation or graphic adjacent to a search result indicating the search result has been visited by one of the user's buddies. In another embodiment, the relevance score assigned to a search result is increased if the search result has been visited by a buddy. In another aspect, alternative queries from the buddies' search history may be suggested to the user during the search session.

Description

    BACKGROUND
  • Computer users enter search terms into search engines to find information about various items (e.g., people, sports teams, cities, and companies) or in some case to locate specific objects (e.g. documents, emails, and web pages). The goal of the search engines is to provide the computer users with relevant search results. Internet search engines are a common example of search engines that receive search terms and return search results.
  • SUMMARY
  • This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
  • Embodiments of the present invention relate to using search histories from one or more buddies to provide more relevant search results and search enhancements that improve the searching experience for the user. In one embodiment, a user submits a search query and is presented with search results and a search enhancement. A search enhancement may be presented adjacent to individual search results and indicate that the search result has been visited by buddies in response to queries similar to the one submitted by the user. In another embodiment, search results visited by buddies are given more weight by the search engine when ranking results or are presented in a separate section of the search results. Buddy search history information may also be used to suggest alternative queries that are related to a query submitted by the user.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention is described in detail below with reference to the attached drawing figures, wherein:
  • FIG. 1 is a block diagram of an exemplary computing environment suitable for use in implementing the present invention;
  • FIG. 2 is an illustration showing an exemplary computing system architecture suitable for utilizing search information from buddies to enhance a users search experience, in accordance with an embodiment of the present invention;
  • FIG. 3 illustrates a manner in which relationships between the current query and buddies' queries are analyzed to determine whether search results are related to a query, in accordance with embodiments of the present invention;
  • FIG. 4 illustrates a method of determining whether a buddy query is related to a current query by categorizing the buddy query and current query, in accordance with embodiments of the present invention;
  • FIG. 5 illustrates a method of determining whether a buddy query is related to a current query, in accordance with embodiments of the present invention;
  • FIG. 6 illustrates an additional method of determining whether the current query is related to buddy queries within the buddies' search history, in accordance with embodiments of the present invention;
  • FIG. 7 illustrates a method of determining whether a current query is related to a search result within the search history by category, in accordance with embodiments of the present invention;
  • FIG. 8 illustrates a method of determining whether a search result within the search histories of buddies is related to a current query using keywords, in accordance with embodiments of the present invention;
  • FIG. 9 includes a flow diagram showing an exemplary method for providing search enhancements based in part on buddy search histories, in accordance with embodiments of the present invention;
  • FIG. 10 includes a flow diagram showing an exemplary method for improving search results using search history from one or more buddies, in accordance with embodiments of the present invention;
  • FIG. 11 includes an exemplary screen display showing a search input interface, in accordance with embodiments of the present invention; and
  • FIGS. 12-14 include an exemplary screen display showing search enhancements, in accordance with embodiments of the present invention.
  • DETAILED DESCRIPTION
  • The subject matter of the present invention is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different elements of methods employed, the terms should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.
  • Overview
  • Embodiments of the present invention provide a system and method of using search histories from a group of buddies to provide an improved search experience for the user. A buddy is a person designated by a user. A user may designate a single buddy or a group of buddies whose search history will be used to improve the users search experience. The search histories of these buddies, including related queries and sites visited in response to the related queries, may be used to provide more relevant search results, search enhancements, or suggest alternative search queries drawn from the buddy search histories. In one embodiment, in response to submitting a current query, a user is presented with search results and a search enhancement. A search enhancement may be presented adjacent to individual search results and indicate that the search result has been visited by a buddy. In another embodiment, a search enhancement provides a list of search results that have been visited by buddies and are related to the current query. In another embodiment, related search queries drawn from the buddy search histories are suggested to the user.
  • Accordingly, in one embodiment of the invention, a computerized system containing a processor and a computer-storage media for enhancing a search session using buddy search history information is provided. The system includes a search engine that receives a query from a user and generates a plurality of search results that are responsive to the query. The system also includes a search enhancement component that receives information identifying one or more buddies, wherein a buddy is a person designated by the user. The search enhancement component also generates one or more search enhancements that are based on a plurality of buddy search histories associated with the one or more buddies, wherein the plurality of buddy search histories includes at least queries associated with the one or more buddies that submitted the queries and search results associated with the one or more buddies that interacted with the search results. The search enhancement component also causes the one or more search enhancements to be displayed with the plurality of search results.
  • In another aspect, an embodiment of the invention is one or more computer-storage media having computer-executable instructions embodied thereon for performing a method of providing search enhancements based in part on buddy search histories. The method includes receiving a search query from a user, retrieving a search history for one or more buddies designated by the user, and presenting one or more search enhancements to the user based on the search query and the search history.
  • A further embodiment of the present invention is directed to one or more computer-storage media having computer-executable instructions embodied thereon for performing a method of improving search results using search history information from one or more buddies. The method includes storing search history information associated with individual users, wherein the individual users may designate a privacy level for the search history information associated with the individual user. The method further includes receiving a search query from a user and receiving information indicating one or more search buddies associated with the user. The method also include displaying one or more additional search queries related to the search query and drawn from a subset of the search history information that is associated with the one or more search buddies, wherein the one or more additional search queries are selectable by the user. The method also includes displaying search results in conjunction with a search enhancement.
  • Exemplary Operating Environment
  • Having briefly described an overview of the present invention, an exemplary operating environment in which various aspects of the present invention may be implemented is described below in order to provide a general context for various aspects of the present invention. Referring initially to FIG. 1 in particular, an exemplary operating environment for implementing embodiments of the present invention is shown and designated generally as computing device 100. Computing device 100 is but one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing device 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated.
  • The invention may be described in the general context of computer code or machine-useable instructions, including computer-executable instructions such as program modules, being executed by a computer or other machine, such as a personal data assistant or other handheld device. Generally, program modules including routines, programs, objects, components, data structures, etc., refer to code that perform particular tasks or implement particular abstract data types. The invention may be practiced in a variety of system configurations, including hand-held devices, consumer electronics, general-purpose computers, more specialty computing devices, etc. The invention may also be practiced in distributed computing environments where tasks are performed by remote-processing devices that are linked through a communications network.
  • With reference to FIG. 1, computing device 100 includes a bus 110 that directly or indirectly couples the following devices: memory 112, one or more processors 114, one or more presentation components 116, input/output ports 118, input/output components 120, and an illustrative power supply 122. Bus 110 represents what may be one or more busses (such as an address bus, data bus, or combination thereof). Although the various blocks of FIG. 1 are shown with lines for the sake of clarity, in reality, delineating various components is not so clear, and metaphorically, the lines would more accurately be grey and fuzzy. For example, one may consider a presentation component such as a display device to be an I/O component. Also, processors have memory. We recognize that such is the nature of the art, and reiterate that the diagram of FIG. 1 is merely illustrative of an exemplary computing device that can be used in connection with one or more embodiments of the present invention. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “hand-held device,” etc., as all are contemplated within the scope of FIG. 1 and reference to “computing device.”
  • Computing device 100 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computing device 100 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.
  • Memory 112 includes computer-storage media in the form of volatile and/or nonvolatile memory. The memory may be removable, nonremovable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical-disc drives, etc. Computing device 100 includes one or more processors that read data from various entities such as memory 112 or I/O components 120. Presentation component(s) 116 present data indications to a user or other device. Exemplary presentation components include a display device, speaker, printing component, vibrating component, etc.
  • I/O ports 118 allow computing device 100 to be logically coupled to other devices including I/O components 120, some of which may be built in. Illustrative components include a microphone, joystick, game pad, satellite dish, scanner, printer, wireless device, etc.
  • Exemplary System Architecture
  • Turning now to FIG. 2, a block diagram is illustrated that shows a system architecture suitable for providing an enhanced search experience that utilizes search history information from one or more buddies. It will be understood and appreciated by those of ordinary skill in the art that the computing system architecture 200 shown in FIG. 2 is merely an example of one suitable computing system and is not intended to suggest any limitation as to the scope of the use or functionality of the present invention. Neither should the computing system architecture 200 be interpreted as having any dependency or requirement related to any single component/module or combination of component/modules illustrated therein.
  • Computing system architecture 200 includes a search engine component 210, a buddy list management component 220, a search history tracking component 230, a search history privacy component 240, a search enhancement component 250, a query suggestion component 260, and a data store 270. Computing system architecture 200 may reside on a single computing device, such as computing device 100 shown in FIG. 1. In the alternative, computing system architecture 200 may reside in a distributed computing environment that includes multiple computing devices coupled with one another via one or more networks. Such networks may include, without limitation, one or more local area networks (LANs) and/or one or more wide area networks (WANs). Such network environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. Accordingly, the network, or combination of networks, is not further described herein.
  • The search engine component 210 receives a search query and returns search results. In one embodiment, the search query is received over the Internet and the search results are web pages connected to the Internet. The search engine component 210 may include a web crawler that indexes web pages or other documents to aide in the process of quickly finding and presenting relevant search results. The search engine component 210 may apply an algorithm to determine which search results are the most relevant. The list of results produced or returned in response to a search query may be called the search engine results page or SERP.
  • Buddy list management component 220 performs several functions related to buddy lists, including creating, deleting, and storing buddy lists. A buddy list is a group of people designated by an individual user as buddies. A buddy list could be a user's contact list or a user's social network. In one embodiment, the individual users and people on the user's buddy list must all subscribe to or sign up for a search service. In one embodiment, the buddy list may be unilaterally established by a user. In other words, the people placed on the buddy list do not need to give consent to be added to a user's buddy list. In another embodiment, the buddy relationship is bilateral meaning that a person must consent to being placed on a user's buddy list.
  • The buddy list management component 220 may facilitate the creation of buddy lists. The buddy list management component 220 may allow users to edit the buddy list by adding buddies to and/or subtracting buddies from the list. The buddy list management component 220 may provide an interface to allow the user to input identification information (e.g. name, email address, user ID) for buddies. The buddy list management component 220 may also suggest buddies from a list for selection by the user. In a case where consent of a potential buddy is required to add them to a buddy list, the buddy list management component 220 may contact the potential buddy to obtain the necessary consent from the buddy.
  • The search history tracking component 230 facilitates the collection of search history information for individual users. The search history tracking component 230 may store search history by search contexts. A search context may include a query submitted by a user, the search results presented to the user in response to the query and those search results selected and viewed by the user in response to the query. The search results selected and viewed by the user may include more than just search results returned in the search engine result page (SERP). The search context information may include all content browsed from a search query. In addition, privacy information may be included in the search context that grants different levels of access to different users or buddies (as will be described in more detail below with reference to the search history privacy component 240). All of the information in an individual search context is associated with the user who submitted the search query. Several methods of identifying a user exist that allow the search history tracking component 230 to attribute the search context to the proper user. For example, an individual user may be identified by asking the user to login, enter an email address or entering some other identification information. In another embodiment, the user is identified by an IP address or through a cookie on the user's computer. In another embodiment, the search history information is collected by a client device that is used by the user during a search session. Thus, the client device may identify the user and send the search history information along with information identifying the user to a central data store. Other methods of identifying the user are also possible. In one embodiment, search history for a user is retrieved from a browser and used to populate the search history for the user. The retrieval of search history information from a browser may occur the first time the search history tracking component 230 interacts with a user, or as an ongoing way to collect search history information from the user.
  • An individual user may generate several search contexts during a search session. A search session starts when a user enters the search engine and stops when the user exits the search engine. A new search context may be generated every time a new query is submitted by the user. In one embodiment, the search history tracking component 230 facilitates storing search history information in data store 270.
  • The search history privacy component 240 collects privacy preferences and associates them with search contexts. In one embodiment, the search history privacy component 240 allows a user to designate a privacy level for each search context generated during a search session. In another embodiment, the user may designate a privacy level that is assigned to all search contexts generated during a search session. In another embodiment, a user selects a default privacy level that is assigned to all search contexts generated until the default privacy level is changed, or an individual privacy level is selected for a search session or a search context. The search history privacy component 240 may allow a user to designate a privacy level as a search query if submitted. The search history privacy component 240 may also allow a user to view their search history and assign or change the designated privacy level at any level of granularity. For example, the user could change the privacy level on a search context basis, a session context basis, or the entire search history.
  • The search history privacy component 240 may assign one of several privacy levels to a search history, or part of a search history. Different privacy levels may be designated for different parts of a user search history. In one embodiment, one of five different privacy levels are assigned to a user's search history or parts of the search history. The five privacy levels include a private designation, an individual buddies designation, an all buddies designation, a buddy group designation, and a public designation. The private designation indicates that the search context should not be shared with others or used in any way to enhance search results. The individual buddies designation indicates individual buddies that can use the search context to enhance a search. The all buddies designation indicates that all of the buddies on the users buddy list may use the search context to enhance a search. The buddy group designation indicates that one or more groups of buddies may use the search context to enhance a search. A public designation indicates that all users and buddies on a system may use the search context to enhance a search. The search history privacy component 240 may provide any number of interfaces to facilitate the collection of privacy level information.
  • The search enhancement component 250 provides search enhancements in response to a search query submitted by a user. The search enhancement utilizes search history information from one or more buddies of the user submitting the search query. In some embodiments, search history from all buddies included in the user's buddy list is used to provide search enhancements. An interface may be provided for the user to select an individual buddy, a group of buddies, a predefined group of buddies, or all buddies to provide a search enhancement. For example, a user could predefine a group of buddies consisting of hunting enthusiasts. When submitting a search query related to hunting, the user may wish to designate this predefined group to provide a search enhancement. The purpose of the search enhancement is to leverage the buddies' search experience to provide information regarding the relevance of search results presented to the user.
  • Many different kinds of search enhancements may be presented to a user. In one embodiment, the normal search results are presented in conjunction with a search enhancement that indicates an individual search result has been visited by a buddy. Normal search results are the search results returned by the search engine without taking the buddy search histories into account. The indication may list a specific buddy who selected and viewed a search result, the number of buddies that selected and viewed a search result, or just that at least one buddy selected and viewed a search result. In one embodiment, the search enhancement is a graphic that is displayed adjacent to an individual search result that is described by the graphic. FIGS. 11-14 illustrate various embodiments of a search enhancement. These embodiments are shown for the sake of example and are not meant to be limiting.
  • FIG. 11 depicts an illustrative screen display showing a search input interface 1100 that may be provided, for instance, via a search engine web page. The search input interface 1100 allows a user to input a current search query 1102. A user may select one or more buddies by selecting the select buddies link 1104. A user may update their buddy list by adding buddies to their buddy list and/or deleting buddies from their buddy list through the update buddies list link 1106. The user may solicit alternative queries that are related to the current query by selecting the suggest query link 1108. As described previously, the suggested queries could be taken from the search history of one or more buddies.
  • FIG. 12 depicts an illustrative screen display 1200 showing a search enhancement that indicates how many buddies have visited a particular search results. The search results section 1212 includes search result 1202, search result 1204, and search result 1206. In one embodiment, each of these search results is returned by the search engine without taking the buddy search history information into account. Search enhancement 1208 is displayed adjacent to search result 1202 and indicates that search result 1202 has been visited by 10 buddies. Search enhancement 1210 is displayed adjacent to search result 1204 and indicates that search result 1204 has been visited by two buddies. Notice that a search enhancement is not provided for search result 1206 illustrating that search results can be presented without a search enhancement.
  • In one embodiment, the normal search results (i.e. those returned without taking the buddies' search history into account) are re-ordered based on information from the search history, such as the number of times a search result has been selected and viewed by buddies. The re-ordered search results may be presented with or without other search enhancements. FIG. 12 shows search results 1202, 1204, and 1206 ordered according to the number of times they have been visited by one or more buddies. Search result 1202 is listed first because it has been visited by 10 buddies. Search result 1204 is listed second because it has been visited by two buddies. Search result 1206 is listed third because it has not been visited by any buddies. Search results, such as search result 1206, that have not been viewed by buddies may be ranked according to typical ranking mechanism used by the search engine.
  • FIG. 13 depicts an illustrative screen display 1300 showing a search enhancement that indicates which buddies have visited a particular search result. The search results section 1312 includes search result 1302, search result 1304, and search result 1306. In one embodiment, each of these search results is returned by the search engine without taking the buddy search history information into account. Search enhancement 1308 is displayed adjacent to search result 1302 and indicates that search result 1302 has been visited by buddy 1 and buddy 5. Search enhancement 1310 is displayed adjacent to search result 1304 and indicates that search result 1304 has been visited by buddy 2. Notice that a search enhancement is not provided for search result 1206 illustrating that search results can be presented without a search enhancement.
  • FIG. 14 depicts an illustrative screen display 1400 showing a search enhancement that provides a separate section of search results that include results selected and visited by buddies. The search results section 1414 includes search result 1402, search result 1404, and search result 1406. In one embodiment, each of these search results is returned by the search engine without taking the buddy search history information into account. The buddy search results section 1416 displays one or more search results that are have been visited and selected by one or more buddies and are related to the current search query. The buddy search results section 1416 includes search result 1402, search result 1410, and search result 1412. Search result 1402 is listed in both sections indicating that a search result may appear in both sections if it meets the respective criteria for inclusion in each search result section.
  • When providing the search enhancement, the privacy level of search context information submitted by the buddies will be honored. For example, if a buddy has been designated by a first user, but does not have any search history available to the first user because of privacy levels assigned to the search history information then that buddy's search history information will not be used to provide a search enhancement. In some instances, the privacy level assigned to search information that appears in multiple contexts may be in conflict. A conflict in the search history information can occur when the same search result is viewed in response to two different queries because each query is part of a different search context and each search context may be assigned a different privacy level. For example, a search result visited in one context in response to a first query may be designated private, whereas the same search results visited in a second context in response to a second query may be designated as public. In one embodiment, the conflict is resolved by utilizing the search history information at the lowest privacy level. The lowest privacy level is the level that allows the most information to be used. In another embodiment, the conflict is resolved by ascribing the highest privacy level to the conflicting search history information. In the embodiment where the lowest privacy level is used, the search result will be used to enhance the buddies' search. For example, if in response to a query regarding cars, a buddy visits a consumer advocacy site and designates that search context containing the query and the consumer advocacy site as public and then visits the consumer advocacy site in response to a second query that is designated private, the consumer advocacy site would nevertheless be utilized by the search enhancement component 250 to generate a search enhancement. On the other hand, the opposite result will occur if the highest privacy level governs the conflict in privacy levels. In that case, the consumer advocacy site would not be utilized by the search enhancement component 250 to generate a search enhancement because it is part of a search context designed as private.
  • The search enhancement component 250 may provide other search enhancements such as reordering the search results based on giving more weight to search results viewed by one or more buddies. In another embodiment, a separate group of search results that have been visited by buddies and that are related to the submitted query are presented in a separate section. In yet another embodiment, the search enhancement includes interacting with the search engine to adjust the relevant weight given to search results visited by buddies.
  • An important aspect of providing a search enhancement includes determining which search results and queries within a buddies' search history are related to the current query submitted by the user. FIG. 3 and FIGS. 7-8 illustrate determining whether a search result within the search history is related to the current query. FIGS. 4-6 illustrate determining whether a buddy query is related to the current query. The examples shown in FIGS. 3-8 are for the sake of illustration only, and are not meant to be limiting. Other methods of determining whether a relation ship exists between the current query and a buddy query or the current query and a buddy search result are possible.
  • FIG. 3 illustrates a manner in which relationships between the current query and buddies' queries from the search history are analyzed to determine whether search results are related to the current query in accordance with embodiments of the present invention. The analysis illustrated in FIG. 3 determines that a search result is related to a current query if the search result was selected and viewed by a designed buddy when the search result was presented in response to a buddy query that is related to the current query. FIG. 3 shows a current query 310 submitted by the user. FIG. 3 also shows a buddy query group 320 including a group of queries submitted by buddies, and buddy result group 330 including search results visited by the buddies in response to the various buddy queries. Buddy query group 320 and buddy search result group 330 are taken from the search histories for the user's buddies. Buddy query group 320 includes buddy query 322, buddy query 324, buddy query 326, and buddy query 328. Only four buddy queries are shown for the sake of illustration, but many more buddy queries could be includes. Buddy search result group 330 includes search result 332, search result 334, search result 336, search result 338, and search result 339. As with the buddy queries, the search results are taken from the buddies' search histories and could include many more search results than the five shown. Current query 310 is related to buddy query 322 through relationship 360. Buddy query 326 is related to current query 310 through relationship 362. The various methods of determining whether a relationship between the current query 310 and a buddy query are described subsequently. In one embodiment, search result 332 and search result 336 would be related to the current query 310 because they were visited by a buddy in response to buddy query 322 which is related to the current query 310. The search results visited only in response to buddy query 324 and buddy query 328 may not to be related to current query 310 since buddy query 324 and buddy query 328 are not related to the current query. Thus, in this embodiment, only search result 332 and search result 336 would be determined to be related to current query 310.
  • Turning now to FIG. 4, a block diagram illustrates determining whether a buddy query is related to a current query by categorizing the query, in accordance with embodiments of the present invention. In this embodiment, a buddy query is related to the current query 310 if it falls within one or more of the same categories. A category may be a designation assigned to a search result or query based on the subject matter of the search result or query. Both search results and queries may be assigned categories to help present relevant search results in response to a query. FIG. 4 includes current query 310 category 420, category 422, category 424, and category 426. The lines between the current query 310 and category 420, category 422 and category 426 indicate that the current query 310 is categorized into these three categories. The current query 310 does not fall into query category 424, as indicated by the lack of a connection. FIG. 4 also includes buddy query 432, buddy query 434, buddy query 436, and buddy query 438. Buddy query 432 is related to current query 310 because they have at least one category in common. In this case, they are both in category 420 and category 422. Buddy query 434 is not related to current query 310 because it is not related to category 420, category 422, or category 426. Buddy category 436 is related to current query 310 because they are both in category 426. In one embodiment, the fact that buddy query 436 is also categorized in category 424 which is not related to the current query 310 does not prevent it from being related to the current query 310. Buddy search query 438 is not related to the current query 310 because it is not related to one of the categories to which current query 310 is related.
  • Turning now to FIG. 5, a block diagram illustrates determining whether a buddy query is related to a current query, in accordance with embodiments of the present invention. In this embodiment, buddy queries are determined to be related to the current query 310 if the buddy query produces at least one search result that is in the same category as the current query 310 and that was visited by at least one buddy in response to a buddy query. FIG. 5 includes current query 310. FIG. 5 also includes category 520, category 522, category 524, and category 526. FIG. 5 also shows search result 530, search result 532, and search result 534. In one embodiment, all search results within the search histories of buddies that fall within categories assigned to the current query 310 may be included in the evaluation. FIG. 5 also includes buddy query 540, buddy query 542, buddy query 544, and buddy query 546. The lines between the current query 310 and categories indicate that the current query 310 is categorized into the category to which it is connected. Thus, the current query 310 is categorized into categories 520, 522, and 526, but not category 524. The lines between search results and categories indicate that the search result is in the category or categories to which it is connected. Thus, search result 530 is in category 524, search result 532 is in category 520 and 522, and search result 534 is in category 526. The lines between search results and buddy queries indicate that the search result was visited by a buddy in response to the query to which the search result is connected. Thus, search result 530 was visited in response to buddy query 542, search result 532 was visited in response to buddy query 540, and search result 534 was visited in response to buddy query 544.
  • Continuing with FIG. 5, buddy queries are determined to be related to the current query 310 if the search results visited in response to the buddy query are in the same category as the current query 310. For example, buddy query 540 is related to the current query 310 because search result 532, which shares category 520 with current query 310, was visited in response to buddy query 540. Similarly, buddy query 544 is related to current query 310 because search result 534, which shares category 526 with current query 310, was visited in response to buddy query 544. Conversely, buddy query 542 is not related to current query 310 because search result 530 is only in category 524, which is not shared with current query 310. Buddy query 546 is unrelated to any of the search results and, thus, is not related to current query 310.
  • Turning now to FIG. 6, a block diagram illustrates determining whether the current query is related to buddy queries within the buddy search history, in accordance with an embodiment of the present invention. In this embodiment, buddies' queries are related to the current query 310 if they returned one or more search results that are also within the search engine results page (“SERP”) 610 for the current query 310. The SERP 610 includes search results returned by the current query 310 without use of the buddy search history information. FIG. 6 includes current query 310 and a group of search results within the SERP 610. The search results within SERP 610 include search result 612, search result 614, search result 616, and search result 618. Search result 620 and search result 622 are also shown but they are not within SERP 610. FIG. 6 also includes buddy query 632, buddy query 634, buddy query 636, and buddy query 638. The lines between buddy search query 632 and search results 612 and 614 indicate that search results 612 and 614 selected by a buddy in response to buddy query 632. The line between buddy search query 634 and search result 622 indicates that search result 622 was selected by a buddy in response to buddy query 634. The line between buddy search query 636 and search result 618 indicates that search result 618 was selected in response to buddy query 636. The line between buddy search query 638 and search result 620 indicates that search result 620 was selected in response to buddy query 638.
  • Continuing with FIG. 6, buddy query 632 is related to current query 310 because it resulted in the selection of search results 612 and 614, both of which are in the SERP 610. Similarly, buddy query 636 is related to current query 310 because it resulted in the selection of search result 618, which is in the SERP 610. Buddy query 634 and buddy query 638 are not related to current query 310 because search results within SERP 610 were not visited in response to either buddy query 634 or buddy query 638.
  • Turning now to FIG. 7, a block diagram illustrates determining whether a current query is related to a search result within the buddies' search history using categories, in accordance with an embodiment of the present invention. In FIG. 7, a buddy search result is related to the current query 310 if they have a category in common. FIG. 7 includes current query 310. Current query 310 falls into category 710, category 712 and category 716 as indicated by connecting lines. Current query 310 does not fall into category 714. Search result 720, search result 722, search result 724, and search result 726 are all found within the search histories of the user's buddies. Search result 720, search result 722, and search result 726 all fall into a category in common with the current query 310. Search result 724 falls under category 714, which is not related to current query 310. Accordingly, search result 724 is not related to the current query 310. Thus, only search result 720, search result 722, and search result 726 are related to the current query 310.
  • Turning now to FIG. 8, a block diagram illustrates determining whether a search result within the search histories of buddies are related to a current query using keywords, in accordance with embodiments of the present invention. Examples of keywords include a single word, multiple words, a clause, a sentence, numbers, and combinations of letters and numbers. In FIG. 8, the current query 310 is related to a buddy search result if they have a keyword in common. A keyword may be assigned to, or found within, a search result or query based on the subject matter of search result or query. In one embodiment, a list of keywords is assembled and assigned to a query or search result if the keyword occurs in the search result or query. FIG. 8 shows that current query 310 includes keyword 810, keyword 812, and keyword 816. Keyword 814 is shown for the sake of illustration but is not contained in current query 310. Search result 820, search result 822, search result 824, and search result 826 are all found within the search histories of buddies designated by the current user. Search result 820 is related to current query 310 because it also contains keyword 816. Search result 822 is related to the current query 310 because it contains keyword 810, and keyword 812. Search result 824 is not related to current query 310 because it is only related to keyword 814, which is not related to current query 310. Search result 826 is related to current query 310 because it contains keyword 816.
  • Returning now to FIG. 2, the search enhancement component 250 may utilize the methods of FIGS. 3-8, or other methods to determine that a search result within the buddy search history is related to the current query. In one embodiment, a search result from the search history information must also be in the SERP for the current query to be considered related. In other embodiments, the search result from the search history information does not need to be in the SERP for the current query. Having made this determination, search enhancements may be presented in association with the related search results as described previously.
  • The query suggestion component 260 identifies related queries within the buddy search histories and presents the related queries to the user as alternative query suggestions to allow the user to refine the search. The query suggestion component 260 may use the approaches described with reference to FIG. 3, FIG. 4, FIG. 5, FIG. 6, or another approach to determine whether a query within the buddy search history is related to the current query. Variations on the described methods as well as other methods not explicitly described may also be used. The query suggestions may be presented prior to presenting search results. The alternative query suggestions may also be presented after search results are presented.
  • Data store 270, may store information for the search engine, search histories, buddy lists, and any other information necessary to enable the functions of computer system architecture 200. In one embodiment, data store 270 organizes the information in a relational data base. Data store 270 may be centrally located and communicatively connected to other components operating on different computing devices.
  • Referring next to FIG. 9, a flow diagram showing an exemplary method for providing search enhancements based in part on buddy search histories is shown and designated generally as reference numeral 900. At step 910, a search query is received from a user. In one embodiment, a search query is submitted over the Internet through a user interface intended to receive search queries. For example, a search query may be submitted in the query field present on an Internet web page. The query may be a single word, or a series of words. The query may also contain Boolean operators. Embodiments of the present invention are not intended to be limited by the type of query received or the manner in which the query is received.
  • At step 920, a search history for one or more buddies designated by the user is retrieved. In one embodiment, the buddies are designated through a user interface displayed to the user. In one embodiment, a single buddy is designated. In another embodiment, two or more buddies are designated. In another embodiment, a predetermined group of buddies is designated by the user. The buddies may be selected from a list of buddies that was previously created by the user. In another embodiment, the buddies may be entered in conjunction with the search query. In yet another embodiment, all buddies on a user's list may be used. A search history may be stored in a data store that is communicatively connected to the computing device retrieving the search history. As explained above, the search history may be stored in terms of search contexts that each includes a search query, search results visited by the buddy submitting the search query, and a privacy level. Other information may also be stored in a search context. Each individual search context should be associated with a single user making it possible to retrieve search histories for only one or more designated buddies.
  • At step 930, one or more search enhancements are presented to the user. The search enhancements are generated based in part on the search query and the retrieved search history. In one embodiment, a search enhancement includes an annotation displayed adjacent to an individual search result. As illustrated in FIG. 12, the annotation may communicate the number of buddies that have viewed the individual search result. As illustrated in FIG. 13, the annotation may identify one or more buddies that have actually viewed the search result. In yet another embodiment, the annotation may simply indicate that at least one buddy has viewed the individual search result. As illustrated in FIG. 14, the search enhancement may include a separate section of search results that have been viewed by one or more buddies and are related to the search query. Some methods of determining whether a search result is related to a current query have been described previously. In another embodiment, the search enhancement includes reordering the search results returned from the query by giving additional weight to search results with the SERP that were visited by a buddy. This ensures that search results visited by buddies will be considered more relevant than search results that have not been visited by buddies.
  • In one embodiment, one or more additional search queries related to the current search query may be presented to the user for selection as a query suggestion to refine the user's search. The additional queries may be drawn from the search histories of the one or more designated buddies if it is determined to be related to the originally submitted search query. Some methods of determining whether a query within the search histories of designated buddies is related to the current query have been described previously.
  • A privacy input interface may be presented to the user in conjunction with the search engine results page or any other time during a search session. The privacy input interface allows the user to select a privacy level for each search context associated with the user. As described previously, a search context may include an individual query, search results viewed by the user submitting the individual query, and privacy information. In one embodiment, privacy level information is received through the privacy input interface presented to the user. The privacy level information may then be stored in association with the search context in a data store that is used to store the search context information. Various privacy levels that may be used have been described previously.
  • Turning now to FIG. 10, a flow diagram showing an exemplary method for improving search results using search history information from one or more buddies is shown and designated generally with reference to numeral 1000. At step 1010, search history information associated with individual users is stored. The individual users may designate a privacy level for the search history information associated with the individual user. Methods of assigning privacy levels to various parts of a user's search history have been described previously as have various privacy levels.
  • At step 1020, a search query is received from a user. Various embodiments of receiving a search query for a user have been described previously with reference to FIG. 9. At step 1030, identification information for one or more search buddies associated with the user is received. At step 1040, one or more additional search queries related to the search query and drawn from a subset of the search history information that is associated with the buddies are displayed to the user. As described previously, the one or more search queries may be selected by the user. Upon selection of a related search query, results associated with that search query will be presented to the user. At step 1050, the search results normally returned from the original search query are presented in association with one or more search enhancements. Examples of possible search enhancements have been described previously with reference to FIGS. 11-14 and elsewhere.
  • CONCLUSION
  • As can be understood, embodiments of the present invention provide an enhanced search experience using search history information from a group of one or more buddies. The present invention has been described in relation to particular embodiments, which are intended in all respects to be illustrative rather than restrictive. Alternative embodiments will become apparent to those of ordinary skill in the art to which the present invention pertains without departing from its scope.
  • From the foregoing, it will be seen that this invention is one well adapted to attain all the ends and objects set forth above, together with other advantages which are obvious and inherent to the system and method. It will be understood that certain features and subcombinations are of utility and may be employed without reference to other features and subcombinations. This is contemplated by and is within the scope of the claims.

Claims (20)

  1. 1. A computerized system containing a processor and a computer-storage media for enhancing a search session using buddy search history information, the system comprising:
    a search engine that receives a query from a user and generates a plurality of search results that are responsive to the query; and
    a search enhancement component that:
    (1) receives identification information for one or more buddies, wherein a buddy is a person designated by the user,
    (2) generates one or more search enhancements that are based on a plurality of buddy search histories associated with the one or more buddies, wherein the plurality of buddy search histories includes at least queries associated with the one or more buddies that submitted the queries and search results associated with the one or more buddies that interacted with the search results, and
    (3) causes the one or more search enhancements to be displayed with the plurality of search results.
  2. 2. The computerized system of claim 1, wherein the one or more buddies includes one or more of a single buddy, a predefined group of buddies, all buddies on a buddy list, and a plurality of buddies individually selected during a search session, wherein the search session starts when the user accesses the search engine and ends when the user exits the search engine.
  3. 3. The computerized system of claim 1, wherein the one or more search enhancements includes an annotation displayed adjacent to an individual search result within the plurality of search results, wherein the annotation communicates information derived from the plurality of buddy search histories.
  4. 4. The computerized system of claim 3, wherein the annotation communicates one or more of: a number of buddies that have viewed the individual search result within the plurality of search results; an identification of individual buddies that have viewed the individual search result; and an indication that at least one buddy has viewed the individual search result.
  5. 5. The computerized system of claim 1, wherein the one or more search enhancements are displayed with the plurality of search results as a separate section of search results that are related to the query and that have been viewed by the one or more buddies.
  6. 6. The computerized system of claim 1, wherein the one or more search enhancements include reordering the search results to give more importance to individual search results that have been viewed by the one or more buddies.
  7. 7. The computerized system of claim 1, further comprising a query suggestion component that suggests a new query related to the query, wherein the new query is taken from the plurality of buddy search histories and determined to be related to the query.
  8. 8. The computerized system of claim 1, wherein the system further comprises a search history privacy component and a search history tracking component, wherein the search history privacy component allows the user and buddies to assign a privacy level to their search histories, and wherein the search history tracking component causes search history information to be stored.
  9. 9. One or more computer-storage media having computer-executable instructions embodied thereon for performing a method of providing search enhancements based in part on buddy search histories, the method comprising:
    receiving a search query from a user;
    retrieving a search history for one or more buddies designated by the user; and
    presenting one or more search enhancements to the user based on the search query and the search history.
  10. 10. The one or more computer-storage media of claim 9, wherein the one or more search enhancements includes an annotation displayed adjacent to an individual search result, wherein the annotation communicates one or more of: a number of buddies that have viewed the individual search result; an identification of the one or more buddies that have viewed the individual search result; and an indication that at least one buddy has viewed the individual search result.
  11. 11. The one or more computer-storage media of claim 9, wherein the one or more search enhancements includes a separate section of results that have been viewed by the one or more buddies and are related to the search query.
  12. 12. The one or more computer-storage media of claim 9, wherein the one or more search enhancements include reordering the search results by giving additional weight to search results within the search history.
  13. 13. The one or more computer-storage media of claim 9, further comprising suggesting a new search query related to the search query based on the search history for the one or more buddies, wherein the new search query was submitted by one or more of the one or more buddies and determined to be related to the search query.
  14. 14. The one or more computer-storage media of claim 13, wherein the new search query is determined to be related to the search query if the search query and the new search query have above a threshold number of search results in common.
  15. 15. The one or more computer-storage media of claim 13, wherein the new search query is determined to be related to the search query if the search query and the new search query have a common search query category.
  16. 16. The one or more computer-storage media of claim 9, wherein the method further comprises:
    presenting a privacy input interface to the user that allows the user to select a privacy level for a search context associated with the user, wherein the search context includes an individual query, search results returned in response the individual query, and search results viewed by a person submitting the individual query; and
    receiving the privacy level designated by the user.
  17. 17. The media of claim 16, wherein the privacy level includes one or more of the following privacy level designations:
    a private designation that indicates the search context should not be shared with others or used to refine suggestions for other buddies;
    an individual buddies designation that indicates individual buddies that can use and view the search context;
    an all buddies designation that indicates that all of the buddies may use and view the search context;
    a buddy group designation that indicates one or more groups of buddies that may use and view the search context; and
    a public designation indicating that all users on a system may use and view the search context.
  18. 18. One or more computer-storage media having computer-executable instructions embodied thereon for performing a method of improving search results using search history information from one or more buddies, the method comprising:
    storing search history information associated with individual users, wherein the individual users may designate a privacy level for the search history information associated with the individual user;
    receiving a search query from a user;
    receiving information indicating one or more search buddies associated with the user;
    displaying one or more additional search queries related to the search query and drawn from a subset of the search history information that is associated with the one or more search buddies, wherein the one or more additional search queries are selectable by the user; and
    displaying search results in conjunction with a search enhancement.
  19. 19. The one or more computer-storage media of claim 18, wherein the search enhancement includes an annotation displayed adjacent to an individual search result within the subset of the plurality of normal search results, wherein the annotation communicates one or more of: a number of buddies that have viewed the individual search result; an identification of the one or more buddies that have viewed the individual search result; and an indication that at least one buddy has viewed the individual search result.
  20. 20. One or more computer-storage media of claim 18, wherein the search enhancement includes a separate section of results that have been viewed by the one or more buddies.
US12111309 2008-04-29 2008-04-29 Social network powered query refinement and recommendations Abandoned US20090271374A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12111309 US20090271374A1 (en) 2008-04-29 2008-04-29 Social network powered query refinement and recommendations

Applications Claiming Priority (15)

Application Number Priority Date Filing Date Title
US12111309 US20090271374A1 (en) 2008-04-29 2008-04-29 Social network powered query refinement and recommendations
JP2011507497A JP5328896B2 (en) 2008-04-29 2009-02-25 Proposal and narrowing down of queries that take advantage of the social network
MX2010011407A MX339056B (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations.
AU2009241626A AU2009241626B2 (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
SG2013031471A SG190584A1 (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
KR20107024202A KR20110018300A (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
PCT/US2009/035061 WO2009134522A1 (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
BRPI0909089A2 BRPI0909089A2 (en) 2008-04-29 2009-02-25 refinement and recommendations for on search by social network
EP20090739324 EP2272013A4 (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
CA 2718621 CA2718621A1 (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
CN 200980115934 CN102016845B (en) 2008-04-29 2009-02-25 Social network powered query refinement and recommendations
RU2010144263A RU2010144263A (en) 2008-04-29 2009-02-25 request improvement with the use of the network and community recommendations
TW98108090A TWI529543B (en) 2008-04-29 2009-03-12 Computerized system and computer-storage media for social network powered query refinement and recommendations
ZA201006416A ZA201006416B (en) 2008-04-29 2010-09-07 Social network powered query refinement and recommendations
US13407947 US20120158720A1 (en) 2008-04-29 2012-02-29 Social network powered search enhancements

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13407947 Continuation-In-Part US20120158720A1 (en) 2008-04-29 2012-02-29 Social network powered search enhancements

Publications (1)

Publication Number Publication Date
US20090271374A1 true true US20090271374A1 (en) 2009-10-29

Family

ID=41216001

Family Applications (1)

Application Number Title Priority Date Filing Date
US12111309 Abandoned US20090271374A1 (en) 2008-04-29 2008-04-29 Social network powered query refinement and recommendations

Country Status (8)

Country Link
US (1) US20090271374A1 (en)
EP (1) EP2272013A4 (en)
JP (1) JP5328896B2 (en)
KR (1) KR20110018300A (en)
CN (1) CN102016845B (en)
CA (1) CA2718621A1 (en)
RU (1) RU2010144263A (en)
WO (1) WO2009134522A1 (en)

Cited By (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090070299A1 (en) * 2007-09-12 2009-03-12 Nishith Parikh Inference of query relationships based on retrieved attributes
US20100257171A1 (en) * 2009-04-03 2010-10-07 Yahoo! Inc. Techniques for categorizing search queries
US20110191371A1 (en) * 2010-02-01 2011-08-04 Microsoft Corporation Social network search
US20110202522A1 (en) * 2010-02-18 2011-08-18 David Ciemiewicz Automated user behavior feedback system for whole page search success optimization
US20110258232A1 (en) * 2010-04-14 2011-10-20 The Dun & Bradstreet Corporation Ascribing actionable attributes to data that describes a personal identity
US20120078870A1 (en) * 2010-09-28 2012-03-29 Bazaz Gaurav Apparatus and method for collaborative social search
WO2012087418A1 (en) * 2010-12-22 2012-06-28 Thomson Licensing Realtime search grid updates
US20120197987A1 (en) * 2011-02-02 2012-08-02 Research In Motion Limited Method, device and system for social media communications across a plurality of computing devices
EP2485159A1 (en) * 2011-02-02 2012-08-08 Research in Motion Corporation Method, device and system for social media communications across a plurality of computing devices
US20120265756A1 (en) * 2010-12-08 2012-10-18 S.L.I. Systems, Inc. Method for determining relevant search results
US20130031106A1 (en) * 2011-07-29 2013-01-31 Microsoft Corporation Social network powered query suggestions
US20130041876A1 (en) * 2011-08-08 2013-02-14 Paul Alexander Dow Link recommendation and densification
WO2013012767A3 (en) * 2011-07-15 2013-03-21 Microsoft Corporation Ensuring variety in a feed
US20130080460A1 (en) * 2011-09-22 2013-03-28 Microsoft Corporation Providing topic based search guidance
US20130106682A1 (en) * 2011-10-31 2013-05-02 Elwha LLC, a limited liability company of the State of Delaware Context-sensitive query enrichment
WO2012166885A3 (en) * 2011-06-03 2013-05-16 Facebook, Inc. Context-based ranking of search results
US20130144868A1 (en) * 2011-12-01 2013-06-06 Microsoft Corporation Post Building and Search Creation
CN103294967A (en) * 2013-05-10 2013-09-11 中国地质大学(武汉) Method and system for protecting privacy of users in big data mining environments
US8538978B2 (en) * 2010-11-22 2013-09-17 International Business Machines Corporation Presenting a search suggestion with a social comments icon
US20140040271A1 (en) * 2012-08-01 2014-02-06 Google Inc. Categorizing search terms
CN103678326A (en) * 2012-09-03 2014-03-26 百度在线网络技术(北京)有限公司 Method and device for providing browsing information based on search result
JP2014059865A (en) * 2012-09-14 2014-04-03 Hon Hai Precision Industry Co Ltd Retrieval system and method thereof
US8712991B2 (en) 2011-07-07 2014-04-29 Microsoft Corporation Document-related representative information
US20140136518A1 (en) * 2012-11-12 2014-05-15 Microsoft Corporation Multi-pane presentation of multidimensional search results
WO2014096137A1 (en) * 2012-12-21 2014-06-26 Quentral S.R.L. Interest matching techniques using internet searches
JP2014522046A (en) * 2011-08-02 2014-08-28 ▲騰▼▲訊▼科技(深▲セン▼)有限公司 Search methods, systems, and devices
WO2014137590A1 (en) * 2013-03-08 2014-09-12 Google Inc. Social annotations for enhanced search results
JP2014529114A (en) * 2011-07-20 2014-10-30 マイクロソフト コーポレーション Modeling search of the social graph
US20150081686A1 (en) * 2010-04-19 2015-03-19 Facebook, Inc. Default Structured Search Queries on Online Social Networks
CN104462278A (en) * 2014-11-26 2015-03-25 百度在线网络技术(北京)有限公司 Page content display control method and system
WO2015073759A1 (en) * 2013-11-18 2015-05-21 Microsoft Technology Licensing, Llc Techniques for managing writable search results
US20150169771A1 (en) * 2012-06-04 2015-06-18 Google Inc. Applying social annotations to search results
US9104751B2 (en) 2011-10-12 2015-08-11 Microsoft Technology Licensing, Llc Supplemental search results having social connection endorsement data on a SERP
US9104765B2 (en) 2011-06-17 2015-08-11 Robert Osann, Jr. Automatic webpage characterization and search results annotation
US9110992B2 (en) 2011-06-03 2015-08-18 Facebook, Inc. Context-based selection of calls-to-action associated with search results
CN105051722A (en) * 2012-12-20 2015-11-11 微软技术许可有限责任公司 Auto-complete with persisted atomically linked entities
US9244985B1 (en) * 2011-09-06 2016-01-26 Google Inc. Generating search results for people
US9268857B2 (en) 2011-06-03 2016-02-23 Facebook, Inc. Suggesting search results to users before receiving any search query from the users
CN105354259A (en) * 2015-10-22 2016-02-24 百度在线网络技术(北京)有限公司 Mobile search method and apparatus
US20160070762A1 (en) * 2014-09-04 2016-03-10 Salesforce.Com, Inc. Topic Profile Query Creation
US20160103894A1 (en) * 2010-04-19 2016-04-14 Facebook, Inc. Search Queries with Previews of Search Results on Online Social Networks
US20160103893A1 (en) * 2010-04-19 2016-04-14 Facebook, Inc. Generating Default Search Queries on Online Social Networks
US9569439B2 (en) 2011-10-31 2017-02-14 Elwha Llc Context-sensitive query enrichment
US9715596B2 (en) 2013-05-08 2017-07-25 Facebook, Inc. Approximate privacy indexing for search queries on online social networks
US9852444B2 (en) * 2010-04-19 2017-12-26 Facebook, Inc. Sponsored search queries on online social networks
US10013493B1 (en) * 2011-07-13 2018-07-03 Google Llc Customized search engines
US10102245B2 (en) 2013-04-25 2018-10-16 Facebook, Inc. Variable search query vertical access
US10108676B2 (en) 2013-05-08 2018-10-23 Facebook, Inc. Filtering suggested queries on online social networks
US10129705B1 (en) 2017-12-11 2018-11-13 Facebook, Inc. Location prediction using wireless signals on online social networks
US10133878B2 (en) 2014-07-30 2018-11-20 Microsoft Technology Licensing, Llc Stochastic privacy
US10140338B2 (en) 2010-04-19 2018-11-27 Facebook, Inc. Filtering structured search queries based on privacy settings

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8478700B2 (en) * 2010-08-11 2013-07-02 Brightedge Technologies, Inc. Opportunity identification and forecasting for search engine optimization
CN102375844A (en) * 2010-08-20 2012-03-14 腾讯数码(天津)有限公司 Information providing method and system
CN102810104B (en) * 2011-06-03 2015-05-20 阿里巴巴集团控股有限公司 Information adjusting method and device
CN103425703B (en) * 2012-05-25 2018-07-27 深圳市腾讯计算机系统有限公司 Method and apparatus for processing information such networks
US8972399B2 (en) * 2012-06-22 2015-03-03 Microsoft Technology Licensing, Llc Ranking based on social activity data
CN103678397B (en) * 2012-09-20 2017-05-17 富士通株式会社 Application search means search method and electronic device applications
WO2014050002A1 (en) * 2012-09-28 2014-04-03 日本電気株式会社 Query degree-of-similarity evaluation system, evaluation method, and program
CN103207904B (en) * 2013-03-28 2017-03-15 百度在线网络技术(北京)有限公司 Method of providing search results and search engine
US9785661B2 (en) * 2014-02-07 2017-10-10 Microsoft Technology Licensing, Llc Trend response management

Citations (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732088B1 (en) * 1999-12-14 2004-05-04 Xerox Corporation Collaborative searching by query induction
US20040143661A1 (en) * 2003-01-14 2004-07-22 Akio Higashi Content history log collecting system
US20050120003A1 (en) * 2003-10-08 2005-06-02 Drury William J. Method for maintaining a record of searches and results
US20050131716A1 (en) * 2003-12-15 2005-06-16 Hanan Martin D. Method for determining compatibility
US20050266835A1 (en) * 2004-04-09 2005-12-01 Anuraag Agrawal Sharing content on mobile devices
US20060004892A1 (en) * 2004-06-14 2006-01-05 Christopher Lunt Visual tags for search results generated from social network information
US20060106762A1 (en) * 2004-11-01 2006-05-18 Sap Aktiengesellschaft Information retrieval method with efficient similarity search capability
US20060129533A1 (en) * 2004-12-15 2006-06-15 Xerox Corporation Personalized web search method
US20060195442A1 (en) * 2005-02-03 2006-08-31 Cone Julian M Network promotional system and method
US20060206460A1 (en) * 2005-03-14 2006-09-14 Sanjay Gadkari Biasing search results
US20060218225A1 (en) * 2005-03-28 2006-09-28 Hee Voon George H Device for sharing social network information among users over a network
US20060235873A1 (en) * 2003-10-22 2006-10-19 Jookster Networks, Inc. Social network-based internet search engine
US20060248061A1 (en) * 2005-04-13 2006-11-02 Kulakow Arthur J Web page with tabbed display regions for displaying search results
US20060259479A1 (en) * 2005-05-12 2006-11-16 Microsoft Corporation System and method for automatic generation of suggested inline search terms
US20060282856A1 (en) * 2005-03-04 2006-12-14 Sharp Laboratories Of America, Inc. Collaborative recommendation system
US20060288000A1 (en) * 2005-06-20 2006-12-21 Raghav Gupta System to generate related search queries
US20070061332A1 (en) * 2005-09-14 2007-03-15 Jorey Ramer User history influenced search results
US20070150368A1 (en) * 2005-09-06 2007-06-28 Samir Arora On-line personalized content and merchandising environment
US20070150496A1 (en) * 2004-02-18 2007-06-28 Feinsmith Jason B Machine-implemented activity management system using asynchronously shared activity data objects and journal data items
US20070156636A1 (en) * 2006-01-03 2007-07-05 Yahoo! Inc. Apparatus and method for controlling content access based on shared annotations for annotated users in a folksonomy scheme
US20070162422A1 (en) * 2005-12-30 2007-07-12 George Djabarov Dynamic search box for web browser
US7266546B2 (en) * 2001-09-05 2007-09-04 Fuji Xerox Co., Ltd. Content/information search system
US20070226183A1 (en) * 2006-03-22 2007-09-27 Hart Matt E Method and apparatus for performing collaborative searches
US20070266019A1 (en) * 2004-06-24 2007-11-15 Lavi Amir System for facilitating search over a network
US20070266097A1 (en) * 2006-04-25 2007-11-15 Pagebites, Inc. Method for information gathering and dissemination in a social network
US20080005072A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Search engine that identifies and uses social networks in communications, retrieval, and electronic commerce
US20080005073A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Data management in social networks
US20080005064A1 (en) * 2005-06-28 2008-01-03 Yahoo! Inc. Apparatus and method for content annotation and conditional annotation retrieval in a search context
US20080059455A1 (en) * 2006-08-31 2008-03-06 Canoy Michael-David N Method and apparatus of obtaining or providing search results using user-based biases
US20080082512A1 (en) * 2003-12-30 2008-04-03 Aol Llc Enhanced Search Results
US20080228745A1 (en) * 2004-09-15 2008-09-18 Markus Michael J Collections of linked databases
US20080255946A1 (en) * 2007-04-10 2008-10-16 Utbk, Inc. Systems and Methods to Facilitate Real Time Communications and Commerce via a Social Network
US20080301112A1 (en) * 2007-05-29 2008-12-04 Yahoo! Inc. Enabling searching of user ratings and reviews using user profile location, and social networks
US20080319943A1 (en) * 2007-06-19 2008-12-25 Fischer Donald F Delegated search of content in accounts linked to social overlay system
US20090063304A1 (en) * 2007-08-29 2009-03-05 Anthony Meggs System and method for searching, identifying, and ranking merchants based upon preselected criteria such as social values
US20090125511A1 (en) * 2007-11-13 2009-05-14 Ankesh Kumar Page ranking system employing user sharing data
US20090204601A1 (en) * 2008-02-13 2009-08-13 Yahoo! Inc. Social network search
US20090216859A1 (en) * 2008-02-22 2009-08-27 Anthony James Dolling Method and apparatus for sharing content among multiple users
US20090282002A1 (en) * 2008-03-10 2009-11-12 Travis Reeder Methods and systems for integrating data from social networks
US20090287682A1 (en) * 2008-03-17 2009-11-19 Robb Fujioka Social based search engine, system and method
US7827176B2 (en) * 2004-06-30 2010-11-02 Google Inc. Methods and systems for endorsing local search results
US8005823B1 (en) * 2007-03-28 2011-08-23 Amazon Technologies, Inc. Community search optimization
US8055673B2 (en) * 2008-06-05 2011-11-08 Yahoo! Inc. Friendly search and socially augmented search query assistance layer
US8086605B2 (en) * 2005-06-28 2011-12-27 Yahoo! Inc. Search engine with augmented relevance ranking by community participation
US20140196157A1 (en) * 2007-09-07 2014-07-10 Facebook, Inc. Dynamically updating privacy settings in a social network

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10207906A (en) * 1997-01-27 1998-08-07 Fuji Xerox Co Ltd Retrieval history managing device
JP2004178070A (en) * 2002-11-25 2004-06-24 Nippon Telegr & Teleph Corp <Ntt> Information retrieval method, information retrieval device and program
JP2005071002A (en) * 2003-08-22 2005-03-17 Ricoh Co Ltd Common search system, program, and recording medium
US7165119B2 (en) * 2003-10-14 2007-01-16 America Online, Inc. Search enhancement system and method having rankings, explicitly specified by the user, based upon applicability and validity of search parameters in regard to a subject matter
CN101124576B (en) * 2004-03-15 2010-06-16 雅虎公司 Search system and methods with integration of user annotations from a trust network
WO2006011819A1 (en) * 2004-07-30 2006-02-02 Eurekster, Inc. Adaptive search engine
JP2010503081A (en) * 2006-08-31 2010-01-28 クゥアルコム・インコーポレイテッドQualcomm Incorporated Using the user-based bias results for obtaining or providing a method and apparatus

Patent Citations (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732088B1 (en) * 1999-12-14 2004-05-04 Xerox Corporation Collaborative searching by query induction
US7266546B2 (en) * 2001-09-05 2007-09-04 Fuji Xerox Co., Ltd. Content/information search system
US20040143661A1 (en) * 2003-01-14 2004-07-22 Akio Higashi Content history log collecting system
US20050120003A1 (en) * 2003-10-08 2005-06-02 Drury William J. Method for maintaining a record of searches and results
US20060235873A1 (en) * 2003-10-22 2006-10-19 Jookster Networks, Inc. Social network-based internet search engine
US20050131716A1 (en) * 2003-12-15 2005-06-16 Hanan Martin D. Method for determining compatibility
US20080082512A1 (en) * 2003-12-30 2008-04-03 Aol Llc Enhanced Search Results
US20070150496A1 (en) * 2004-02-18 2007-06-28 Feinsmith Jason B Machine-implemented activity management system using asynchronously shared activity data objects and journal data items
US20050266835A1 (en) * 2004-04-09 2005-12-01 Anuraag Agrawal Sharing content on mobile devices
US20110087658A1 (en) * 2004-06-14 2011-04-14 Facebook, Inc. Ranking Search Results Based on the Frequency of Access on the Search Results by Users of a Social-Networking System
US7788260B2 (en) * 2004-06-14 2010-08-31 Facebook, Inc. Ranking search results based on the frequency of clicks on the search results by members of a social network who are within a predetermined degree of separation
US20060004892A1 (en) * 2004-06-14 2006-01-05 Christopher Lunt Visual tags for search results generated from social network information
US20070266019A1 (en) * 2004-06-24 2007-11-15 Lavi Amir System for facilitating search over a network
US7827176B2 (en) * 2004-06-30 2010-11-02 Google Inc. Methods and systems for endorsing local search results
US20080228745A1 (en) * 2004-09-15 2008-09-18 Markus Michael J Collections of linked databases
US20060106762A1 (en) * 2004-11-01 2006-05-18 Sap Aktiengesellschaft Information retrieval method with efficient similarity search capability
US20060129533A1 (en) * 2004-12-15 2006-06-15 Xerox Corporation Personalized web search method
US20060195442A1 (en) * 2005-02-03 2006-08-31 Cone Julian M Network promotional system and method
US20060282856A1 (en) * 2005-03-04 2006-12-14 Sharp Laboratories Of America, Inc. Collaborative recommendation system
US20060206460A1 (en) * 2005-03-14 2006-09-14 Sanjay Gadkari Biasing search results
US20060218225A1 (en) * 2005-03-28 2006-09-28 Hee Voon George H Device for sharing social network information among users over a network
US20060248061A1 (en) * 2005-04-13 2006-11-02 Kulakow Arthur J Web page with tabbed display regions for displaying search results
US20060259479A1 (en) * 2005-05-12 2006-11-16 Microsoft Corporation System and method for automatic generation of suggested inline search terms
US20060288000A1 (en) * 2005-06-20 2006-12-21 Raghav Gupta System to generate related search queries
US8086605B2 (en) * 2005-06-28 2011-12-27 Yahoo! Inc. Search engine with augmented relevance ranking by community participation
US8521734B2 (en) * 2005-06-28 2013-08-27 Yahoo! Inc. Search engine with augmented relevance ranking by community participation
US20080005064A1 (en) * 2005-06-28 2008-01-03 Yahoo! Inc. Apparatus and method for content annotation and conditional annotation retrieval in a search context
US20070150368A1 (en) * 2005-09-06 2007-06-28 Samir Arora On-line personalized content and merchandising environment
US20070061332A1 (en) * 2005-09-14 2007-03-15 Jorey Ramer User history influenced search results
US20070162422A1 (en) * 2005-12-30 2007-07-12 George Djabarov Dynamic search box for web browser
US20070156636A1 (en) * 2006-01-03 2007-07-05 Yahoo! Inc. Apparatus and method for controlling content access based on shared annotations for annotated users in a folksonomy scheme
US20070226183A1 (en) * 2006-03-22 2007-09-27 Hart Matt E Method and apparatus for performing collaborative searches
US20070266097A1 (en) * 2006-04-25 2007-11-15 Pagebites, Inc. Method for information gathering and dissemination in a social network
US20080005072A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Search engine that identifies and uses social networks in communications, retrieval, and electronic commerce
US20080005073A1 (en) * 2006-06-28 2008-01-03 Microsoft Corporation Data management in social networks
US20080059455A1 (en) * 2006-08-31 2008-03-06 Canoy Michael-David N Method and apparatus of obtaining or providing search results using user-based biases
US8005823B1 (en) * 2007-03-28 2011-08-23 Amazon Technologies, Inc. Community search optimization
US20080255946A1 (en) * 2007-04-10 2008-10-16 Utbk, Inc. Systems and Methods to Facilitate Real Time Communications and Commerce via a Social Network
US7895177B2 (en) * 2007-05-29 2011-02-22 Yahoo! Inc. Enabling searching of user ratings and reviews using user profile location, and social networks
US20080301112A1 (en) * 2007-05-29 2008-12-04 Yahoo! Inc. Enabling searching of user ratings and reviews using user profile location, and social networks
US20080319943A1 (en) * 2007-06-19 2008-12-25 Fischer Donald F Delegated search of content in accounts linked to social overlay system
US20090063304A1 (en) * 2007-08-29 2009-03-05 Anthony Meggs System and method for searching, identifying, and ranking merchants based upon preselected criteria such as social values
US20140196157A1 (en) * 2007-09-07 2014-07-10 Facebook, Inc. Dynamically updating privacy settings in a social network
US20090125511A1 (en) * 2007-11-13 2009-05-14 Ankesh Kumar Page ranking system employing user sharing data
US20090204601A1 (en) * 2008-02-13 2009-08-13 Yahoo! Inc. Social network search
US20090216859A1 (en) * 2008-02-22 2009-08-27 Anthony James Dolling Method and apparatus for sharing content among multiple users
US20090282002A1 (en) * 2008-03-10 2009-11-12 Travis Reeder Methods and systems for integrating data from social networks
US20090287682A1 (en) * 2008-03-17 2009-11-19 Robb Fujioka Social based search engine, system and method
US8055673B2 (en) * 2008-06-05 2011-11-08 Yahoo! Inc. Friendly search and socially augmented search query assistance layer

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Lau, Tessa, Oren Etzioni, and Daniel S. Weld. "Privacy interfaces for information management." Communications of the ACM 42, no. 10 (1999): 88-94. *

Cited By (86)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8655868B2 (en) * 2007-09-12 2014-02-18 Ebay Inc. Inference of query relationships based on retrieved attributes
US10055484B2 (en) 2007-09-12 2018-08-21 Ebay Inc. Inference of query relationships based on retrieved attributes
US9330201B2 (en) 2007-09-12 2016-05-03 Ebay Inc. Inference of query relationships based on retrieved attributes
US20090070299A1 (en) * 2007-09-12 2009-03-12 Nishith Parikh Inference of query relationships based on retrieved attributes
US20100257171A1 (en) * 2009-04-03 2010-10-07 Yahoo! Inc. Techniques for categorizing search queries
WO2011094036A3 (en) * 2010-02-01 2011-10-27 Microsoft Corporation Social network search
US20110191371A1 (en) * 2010-02-01 2011-08-04 Microsoft Corporation Social network search
US8832101B2 (en) * 2010-02-18 2014-09-09 Yahoo! Inc. Automated user behavior feedback system for whole page search success optimization
US20110202522A1 (en) * 2010-02-18 2011-08-18 David Ciemiewicz Automated user behavior feedback system for whole page search success optimization
US9442991B2 (en) 2010-04-14 2016-09-13 The Dun & Bradstreet Corporation Ascribing actionable attributes to data that describes a personal identity
US20110258232A1 (en) * 2010-04-14 2011-10-20 The Dun & Bradstreet Corporation Ascribing actionable attributes to data that describes a personal identity
US8438183B2 (en) * 2010-04-14 2013-05-07 The Dun & Bradstreet Corporation Ascribing actionable attributes to data that describes a personal identity
US20160103893A1 (en) * 2010-04-19 2016-04-14 Facebook, Inc. Generating Default Search Queries on Online Social Networks
US10140338B2 (en) 2010-04-19 2018-11-27 Facebook, Inc. Filtering structured search queries based on privacy settings
US20150081686A1 (en) * 2010-04-19 2015-03-19 Facebook, Inc. Default Structured Search Queries on Online Social Networks
US9946772B2 (en) * 2010-04-19 2018-04-17 Facebook, Inc. Search queries with previews of search results on online social networks
US9852444B2 (en) * 2010-04-19 2017-12-26 Facebook, Inc. Sponsored search queries on online social networks
US9753995B2 (en) * 2010-04-19 2017-09-05 Facebook, Inc. Generating default search queries on online social networks
US9959318B2 (en) * 2010-04-19 2018-05-01 Facebook, Inc. Default structured search queries on online social networks
US20160103894A1 (en) * 2010-04-19 2016-04-14 Facebook, Inc. Search Queries with Previews of Search Results on Online Social Networks
US20120078870A1 (en) * 2010-09-28 2012-03-29 Bazaz Gaurav Apparatus and method for collaborative social search
US8538978B2 (en) * 2010-11-22 2013-09-17 International Business Machines Corporation Presenting a search suggestion with a social comments icon
US9460161B2 (en) 2010-12-08 2016-10-04 S.L.I. Systems, Inc. Method for determining relevant search results
US20120265756A1 (en) * 2010-12-08 2012-10-18 S.L.I. Systems, Inc. Method for determining relevant search results
US9990442B2 (en) 2010-12-08 2018-06-05 S.L.I. Systems, Inc. Method for determining relevant search results
WO2012087418A1 (en) * 2010-12-22 2012-06-28 Thomson Licensing Realtime search grid updates
CN103270749A (en) * 2010-12-22 2013-08-28 汤姆逊许可公司 Realtime search grid updates
US20120197987A1 (en) * 2011-02-02 2012-08-02 Research In Motion Limited Method, device and system for social media communications across a plurality of computing devices
EP2485159A1 (en) * 2011-02-02 2012-08-08 Research in Motion Corporation Method, device and system for social media communications across a plurality of computing devices
WO2012106136A1 (en) * 2011-02-02 2012-08-09 Research In Motion Corporation Device and system for social media communications across a plurality of computing devices
US9934284B2 (en) 2011-06-03 2018-04-03 Facebook, Inc. Context-based selection of calls-to-action associated with search results
US9805126B2 (en) 2011-06-03 2017-10-31 Facebook, Inc. Context-based ranking of search results
US9268857B2 (en) 2011-06-03 2016-02-23 Facebook, Inc. Suggesting search results to users before receiving any search query from the users
KR20140041574A (en) * 2011-06-03 2014-04-04 페이스북, 인크. Context-based ranking of search results
KR101576939B1 (en) 2011-06-03 2015-12-21 페이스북, 인크. Method and system for context-based ranking of search results
US10002168B2 (en) 2011-06-03 2018-06-19 Facebook, Inc. Suggesting search results to users before receiving any search query from the users
US9110992B2 (en) 2011-06-03 2015-08-18 Facebook, Inc. Context-based selection of calls-to-action associated with search results
US8909637B2 (en) 2011-06-03 2014-12-09 Facebook, Inc. Context-based ranking of search results
WO2012166885A3 (en) * 2011-06-03 2013-05-16 Facebook, Inc. Context-based ranking of search results
CN107451284A (en) * 2011-06-03 2017-12-08 脸谱公司 Method, System And Storage Medium Used For Processing Search Query
KR101850848B1 (en) 2011-06-03 2018-04-20 페이스북, 인크. Method and system for context-based ranking of search results
US9104765B2 (en) 2011-06-17 2015-08-11 Robert Osann, Jr. Automatic webpage characterization and search results annotation
US8712991B2 (en) 2011-07-07 2014-04-29 Microsoft Corporation Document-related representative information
US10013493B1 (en) * 2011-07-13 2018-07-03 Google Llc Customized search engines
WO2013012767A3 (en) * 2011-07-15 2013-03-21 Microsoft Corporation Ensuring variety in a feed
JP2014529114A (en) * 2011-07-20 2014-10-30 マイクロソフト コーポレーション Modeling search of the social graph
EP2737422A4 (en) * 2011-07-29 2015-09-30 Microsoft Technology Licensing Llc Social network powered query suggestions
US20130031106A1 (en) * 2011-07-29 2013-01-31 Microsoft Corporation Social network powered query suggestions
WO2013019688A3 (en) * 2011-07-29 2013-06-06 Microsoft Corporation Social network powered query suggestions
US9477765B2 (en) 2011-08-02 2016-10-25 Tencent Technology (Shenzhen) Company Limited Search method, system and device
JP2014522046A (en) * 2011-08-02 2014-08-28 ▲騰▼▲訊▼科技(深▲セン▼)有限公司 Search methods, systems, and devices
US20130041876A1 (en) * 2011-08-08 2013-02-14 Paul Alexander Dow Link recommendation and densification
US9244985B1 (en) * 2011-09-06 2016-01-26 Google Inc. Generating search results for people
US10019589B1 (en) * 2011-09-06 2018-07-10 Google Llc Generating search results for people
US20130080460A1 (en) * 2011-09-22 2013-03-28 Microsoft Corporation Providing topic based search guidance
US9043350B2 (en) * 2011-09-22 2015-05-26 Microsoft Technology Licensing, Llc Providing topic based search guidance
US9104751B2 (en) 2011-10-12 2015-08-11 Microsoft Technology Licensing, Llc Supplemental search results having social connection endorsement data on a SERP
US9569439B2 (en) 2011-10-31 2017-02-14 Elwha Llc Context-sensitive query enrichment
US20130106682A1 (en) * 2011-10-31 2013-05-02 Elwha LLC, a limited liability company of the State of Delaware Context-sensitive query enrichment
US20130144868A1 (en) * 2011-12-01 2013-06-06 Microsoft Corporation Post Building and Search Creation
US9959348B2 (en) * 2012-06-04 2018-05-01 Google Llc Applying social annotations to search results
US20150169771A1 (en) * 2012-06-04 2015-06-18 Google Inc. Applying social annotations to search results
WO2014022715A1 (en) * 2012-08-01 2014-02-06 Google Inc. Categorizing search terms
US9576042B2 (en) * 2012-08-01 2017-02-21 Google Inc. Categorizing search terms
US20140040271A1 (en) * 2012-08-01 2014-02-06 Google Inc. Categorizing search terms
CN103678326A (en) * 2012-09-03 2014-03-26 百度在线网络技术(北京)有限公司 Method and device for providing browsing information based on search result
JP2014059865A (en) * 2012-09-14 2014-04-03 Hon Hai Precision Industry Co Ltd Retrieval system and method thereof
US20140136518A1 (en) * 2012-11-12 2014-05-15 Microsoft Corporation Multi-pane presentation of multidimensional search results
US9836179B2 (en) 2012-12-20 2017-12-05 Microsoft Technology Licensing, Llc Auto-complete with persisted atomically linked entities
CN105051722A (en) * 2012-12-20 2015-11-11 微软技术许可有限责任公司 Auto-complete with persisted atomically linked entities
WO2014096137A1 (en) * 2012-12-21 2014-06-26 Quentral S.R.L. Interest matching techniques using internet searches
WO2014137590A1 (en) * 2013-03-08 2014-09-12 Google Inc. Social annotations for enhanced search results
US9934283B2 (en) 2013-03-08 2018-04-03 Google Llc Social annotations for enhanced search results
US10102245B2 (en) 2013-04-25 2018-10-16 Facebook, Inc. Variable search query vertical access
US9715596B2 (en) 2013-05-08 2017-07-25 Facebook, Inc. Approximate privacy indexing for search queries on online social networks
US10108676B2 (en) 2013-05-08 2018-10-23 Facebook, Inc. Filtering suggested queries on online social networks
CN103294967A (en) * 2013-05-10 2013-09-11 中国地质大学(武汉) Method and system for protecting privacy of users in big data mining environments
WO2015073759A1 (en) * 2013-11-18 2015-05-21 Microsoft Technology Licensing, Llc Techniques for managing writable search results
US10102288B2 (en) 2013-11-18 2018-10-16 Microsoft Technology Licensing, Llc Techniques for managing writable search results
CN105745651A (en) * 2013-11-18 2016-07-06 微软技术许可有限责任公司 Techniques for managing writable search results
US10133878B2 (en) 2014-07-30 2018-11-20 Microsoft Technology Licensing, Llc Stochastic privacy
US20160070762A1 (en) * 2014-09-04 2016-03-10 Salesforce.Com, Inc. Topic Profile Query Creation
US9710468B2 (en) * 2014-09-04 2017-07-18 Salesforce.Com, Inc. Topic profile query creation
CN104462278A (en) * 2014-11-26 2015-03-25 百度在线网络技术(北京)有限公司 Page content display control method and system
CN105354259A (en) * 2015-10-22 2016-02-24 百度在线网络技术(北京)有限公司 Mobile search method and apparatus
US10129705B1 (en) 2017-12-11 2018-11-13 Facebook, Inc. Location prediction using wireless signals on online social networks

Also Published As

Publication number Publication date Type
CA2718621A1 (en) 2009-11-05 application
WO2009134522A1 (en) 2009-11-05 application
JP5328896B2 (en) 2013-10-30 grant
EP2272013A1 (en) 2011-01-12 application
EP2272013A4 (en) 2012-10-10 application
JP2011521329A (en) 2011-07-21 application
CN102016845B (en) 2015-04-22 grant
KR20110018300A (en) 2011-02-23 application
RU2010144263A (en) 2012-05-10 application
CN102016845A (en) 2011-04-13 application

Similar Documents

Publication Publication Date Title
US7599950B2 (en) Systems and methods for collecting user annotations
Balog et al. Formal models for expert finding in enterprise corpora
US7216121B2 (en) Search engine facility with automated knowledge retrieval, generation and maintenance
US8255386B1 (en) Selection of documents to place in search index
US20090024595A1 (en) Automatic expanded language search
US20060112081A1 (en) Storing searches in an e-mail folder
US20070203887A1 (en) Methods and systems for endorsing search results
US8055673B2 (en) Friendly search and socially augmented search query assistance layer
US20050027704A1 (en) Method and system for assessing relevant properties of work contexts for use by information services
US20050222989A1 (en) Results based personalization of advertisements in a search engine
US8122016B1 (en) Determining concepts associated with a query
US6944609B2 (en) Search results using editor feedback
US20100250578A1 (en) System and method for conducting a profile based search
US7809714B1 (en) Process for enhancing queries for information retrieval
US20070073708A1 (en) Generation of topical subjects from alert search terms
US20060122978A1 (en) Entity-specific tuned searching
US20100005061A1 (en) Information processing with integrated semantic contexts
US20080313247A1 (en) Page Ranking Based on a Behavioral WEB Graph
US20080016218A1 (en) Method and system for sharing and accessing resources
US7885918B2 (en) Creating a taxonomy from business-oriented metadata content
US20090132516A1 (en) Enhancing and optimizing enterprise search
US20070266017A1 (en) Search Query Formulation
US20080140348A1 (en) Systems and methods for predictive models using geographic text search
US7899818B2 (en) Method and system for providing focused search results by excluding categories
US20090292696A1 (en) Computer-implemented search using result matching

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KORN, DAVID S;BRADFORD, DONALD E;REEL/FRAME:020871/0303

Effective date: 20080428

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034564/0001

Effective date: 20141014