WO2011071990A2 - Opérations de recherche de ressources - Google Patents

Opérations de recherche de ressources Download PDF

Info

Publication number
WO2011071990A2
WO2011071990A2 PCT/US2010/059415 US2010059415W WO2011071990A2 WO 2011071990 A2 WO2011071990 A2 WO 2011071990A2 US 2010059415 W US2010059415 W US 2010059415W WO 2011071990 A2 WO2011071990 A2 WO 2011071990A2
Authority
WO
WIPO (PCT)
Prior art keywords
resource
search
query
tidbit
text
Prior art date
Application number
PCT/US2010/059415
Other languages
English (en)
Other versions
WO2011071990A3 (fr
Inventor
Matias Pelenur
Christopher Rohrs
Samarth Keshava
Jeremy Silber
Original Assignee
Google Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Google Inc. filed Critical Google Inc.
Priority to CA2783344A priority Critical patent/CA2783344C/fr
Priority to AU2010328181A priority patent/AU2010328181B2/en
Priority to EP10795516A priority patent/EP2510463A2/fr
Publication of WO2011071990A2 publication Critical patent/WO2011071990A2/fr
Publication of WO2011071990A3 publication Critical patent/WO2011071990A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/248—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G06F16/338—Presentation of query results

Definitions

  • This specification relates to digital information retrieval, and particularly to processing search results to facilitate search operations.
  • the Internet provides access to a wide variety of resources, for example, video files, image files, audio files, or Web pages including content for particular subjects, book articles, or news articles.
  • a search system can select one or more resources in response to receiving a search query.
  • a search query is data that a user submits to a search engine to satisfy the user's informational needs.
  • the search system selects and scores resources based on their relevance to the search query and on their importance relative to other resources to provide search results that link to the selected resources.
  • the search results are typically ordered according to the scores, and provided in a search results page.
  • the search results page displays a list of search results, and each search result includes several lines of text (a "snippet") that are intended to show how the page is relevant to the query.
  • a search result When a user clicks on a search result, the user's client device requests the resource - typically a web page - that the search result references.
  • the user may have to manually search the page to find the relevant content, even if the snippet included the exact content they want. The users often must either scroll through the page to find the relevant content, or perform a manual word search operation by use of a browser word search tool.
  • one innovative aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving a query, the query including one or more query terms; receiving, for each of a plurality of resources identified as being relevant to the query, one or more tidbits, each tidbit being query-relevant text extracted from the resource; for each tidbit extracted from each resource: determining whether the tidbit is eligible for a resource search operation that occurs in response to the resource being rendered on a client device, and in response to determining that the tidbit is eligible for a resource search operation, marking the tidbit as being a resource search tidbit; and providing, for each of the plurality of resources, a corresponding search result responsive to the query, each search result including a resource locator that specifies the location of the resource, and wherein at least one search result includes a resource search tidbit.
  • Other embodiments of this aspect include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods
  • Another aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving, in response to a query including one or more query terms, a search results page including search results responsive to the query, each search result including a resource locator that specifies the location of a resource identified as being relevant to the query, and wherein at least one search result includes a resource search tidbit, the resource search tidbit being query-relevant text extracted from the resource and eligible for a research search operation in response to the resource specified by the resource locator of the at least one search result being rendered on the client device; receiving a selection of the at least one search result at the client device; receiving, in response to the selection, the resource specified by the resource locator of the at least one search result; rendering the resource at the client device; identifying a portion of text in the resource that matches the query-relevant text of the resource search tidbit; and performing the resource search operation only if the identified portion of the text matching the query-relevant text of the resource search tidbit meets a search
  • Fig. 1 is a block diagram of a search system that facilitates resource search operations on a client device.
  • Fig. 2 is a block diagram of an example process flow for identifying resource search tidbits in a tidbit processor.
  • Figs. 3A - 3C are Venn diagrams illustrating an example eligibility rule for determining whether a tidbit is eligible for a resource search operation.
  • Fig. 4 is a flow diagram of an example process for identifying resource search tidbits.
  • Fig. 5 is a flow diagram of an example process for determining whether a tidbit for a resource is eligible for a resource search operation.
  • Fig. 6 is a block diagram of an example process for associating resource search tidbits with resource locators from a search results page.
  • Fig. 7A is an illustration of an example rendering of a resource for which a portion of text matching the query-relevant text of the resource search tidbit does not meet a search operation threshold condition.
  • Fig. 7B is an illustration of an example rendering of a resource for which a portion of text matching the query-relevant text of the resource search tidbit does meet a search operation threshold condition.
  • Fig. 8 is a flow diagram of an example process for performing a resource search operation.
  • Fig. 9 is a flow diagram of an example process for determining whether a portion of text in a resource matches the query-relevant text of a resource search tidbit.
  • Fig. 10 is a flow diagram of an example process for navigating to a portion of a resource in response to selecting a resource search tidbit.
  • Fig. 1 1 is a flow diagram of performing a resource search operation using an association of resource locators and resource search tidbits.
  • Fig. 1 is a block diagram of a search environment 100 that facilitates resource search operations on a client device.
  • the example environment 100 includes a network 102, e.g., a local area network (LAN), wide area network (WAN), the Internet, or a combination of them.
  • the network 102 connects Websites 104, client devices 106, and the search system 1 10.
  • the environment 100 may include many thousands of publishers 104 and client devices 106.
  • a Website 104 is one or more resources 105 associated with a domain name and hosted by one or more servers.
  • An example Website is a collection of Web pages formatted in hypertext markup language (HTML) that can contain text, images, multimedia content, and programming elements, e.g., scripts.
  • HTML hypertext markup language
  • Each Website 104 is maintained by a publisher, e.g., an entity that manages and/or owns the Website.
  • a resource 105 is any data that can be provided by a Website 104 over the network 102 and that is associated with a resource address.
  • Resources 105 include HTML pages, word processing documents, and portable document format (PDF) documents, images, video, and feed sources, to name just a few.
  • the resources 105 can include content, e.g., words, phrases, images and sounds and may include embedded information (e.g., meta information and hyperlinks) and/or embedded instructions (e.g., JavaScript scripts).
  • a client device 106 is an electronic device that is under control of a user and is capable of requesting and receiving resources 105 over the network 102.
  • Example client devices 106 include personal computers, mobile communication devices, and other devices that can send and receive data over the network 102.
  • a client device 106 typically includes a user application, e.g., a web browser, to facilitate the sending and receiving of data over the network 102.
  • the search system 1 10 identifies the resources 105 by crawling and indexing the resources 105 provided on Websites 104. Data about the resources 105 can be indexed based on the resource to which the data corresponds. The indexed and, optionally, cached copies of the resources 105 are stored in an indexed cache 1 12.
  • the client devices 106 submit search queries 109 to the search system 1 10.
  • any particular search query 109 can include one or more terms consisting of words, numbers or other characters.
  • the search query 109 entered by the user can be "pachinko 1975 Japan" to search online for information regarding the Japanese upright pinball games.
  • the search system 1 10 accesses (e.g., using a search engine) the indexed cache 112 to identify resources 105 that are relevant to the search query 109.
  • the search system 1 10 identifies the resources 105, generates search results 1 11 that identify the resources 105, and returns the search results 11 1 to the client devices 106.
  • the search results 1 11 can include resources 105 corresponding to Web hits related to "1975 Japanese pachinkos" in response to the user's search query 109.
  • a search result 1 11 is data generated by the search system 110 that identifies a resource 105 that is responsive to a particular search query, and includes a link to the resource 105.
  • An example search result 11 1 can include a Web page title, a snippet of text or a portion of an image extracted from the Web page, and the URL of the Web page.
  • the search results are ranked based on scores related to the resources 105 identified by the search results 1 11, such as information retrieval ("IR") scores, and optionally a quality score of each resource relative to other resources.
  • IR scores are computed from dot products of feature vectors corresponding to a search query 109 and a resource 105, and the ranking of the search results is based on initial relevance scores that are a combination of the IR scores and page quality scores.
  • the search results 1 11 are ordered according to these initial relevance scores and provided to the client device 106 according to the order.
  • the client devices 106 receive the search results 1 11, e.g., in the form of one or more search result pages 126, and render the search results 1 11 for presentation to users.
  • the client device 106 requests the resource 105 identified by the link.
  • the Website 104 hosting the resource 105 receives the request for the resource 105 from the client device 106 and provides the resource 105 to the requesting client device 106.
  • the search results 11 1 include the identification of resources 105 that are relevant to the user's search, such as a set of query terms entered by the user into a Web browser on the client device 106.
  • the search system 110 identifies one or more tidbits and selects a subset of the tidbits for potential inclusion as a snippet.
  • a "tidbit” is query-relevant text that can be included in a snippet.
  • a "snippet" can include one or more tidbits.
  • Each snippet can include query-relevant text extracted from the resource 105 specified by the resource locator (e.g., the resource's URL) of the search result.
  • Snippets can be rendered on the client device 106 as part of the search result.
  • a tidbit is a portion of contiguous text in the resource, such as a group of adjacent words in the search result 11 1 displayed on the user's client device 106.
  • the search results 11 1 can also include one or more snippets, each including one or more tidbits.
  • the search system 110 can provide the query, the resources (or data identifying the resources) and the tidbits for each of the resources to a tidbit processor 113.
  • the tidbit processor 1 13 which is described in more detail in Fig. 2, determines for each tidbit whether the tidbit is eligible for a resource search operation that occurs in response to the resource being rendered on a client device 106.
  • the tidbit processor 113 marks the tidbit as a resource search tidbit (RST).
  • RST resource search tidbit
  • the use of resource search tidbits is described in more detail below.
  • the tidbit processor 113 informs the search system 1 10 of the identified resource search tidbits, if any.
  • a search results page 126 is presented to the user, displaying the search results 1 11, the user can make a selection. For example, the user can review the search results 1 11, including examining the snippets displayed for each resource 105 corresponding to each individual search result 1 11. Upon seeing a particular search result of interest, for example, the user can click the URL or other resource locator for the resource 105 to display a page 128 corresponding to the resource 105.
  • the page 128 can be, for example, the rendered resource 105 corresponding to the news story, product review, home page, advertisement, or any other Web page selected by the user from the search results 11 1.
  • one or more scroll bars 130 within the user interface of the client device 106 can be used to manage the display of the page 128.
  • the scroll bar 130 is scrolled to the top.
  • Sections of the Web site of most interest to the user may not appear in the top, or immediately viewable, portion of the Web page.
  • the information does not fit entirely within the viewport of the client device 106, or is difficult for the user to find on the screen.
  • a selection environment 132 is displayed.
  • the selection environment displays resource search tidbits 134 for the resource, each containing a portion of the query-relevant text of the resource.
  • the selection environment 132 can include one or more resource search tidbits 134 corresponding to text in the resource that matches the user's search terms (e.g., "pachinko 1975 Japan").
  • the sections of text of most closely matching the user's search terms may be embedded in a portion of the resource 105 that is not initially displayed on the client device 106.
  • the user can quickly identify and navigate to those corresponding passages of the resource 105.
  • the selection environment 132 includes three user-selectable lines, each a resource search tidbit, the second of which is highlighted to indicate selection by the user.
  • One advantage of the selection environment 132 is to overcome the problem of limited viewports, such as the viewport on the client device 106.
  • the resource 105 may not be visible to a user of the device because the resource 105 contains too much information to fit entirely within the device's viewport.
  • the zoom level of the viewport e.g., the viewport is zoomed- in
  • the size of the viewport and/or the dimensions of the web page not all of the web page's contents can be displayed in the viewport at the same time.
  • displaying a web page such a scenario is a common occurrence because of the mobile device's relatively small viewport.
  • the query-relevant text of a resource search tidbit included in the search result can be, in some implementations, a subset of the query-relevant text of the snippet included in the search result.
  • the resource search tidbits are tidbits that need not necessarily be part of the snippet of the search result, meaning that they are not rendered on the client device 106 as part of the search results 11 1.
  • the state of information displayed in the page 128 can change, as indicated by the arrow 136.
  • the resource 105 has scrolled to the section of page that corresponds to the resource search tidbit selected by the user.
  • the query-relevant text 138 associated with the user-selected resource search tidbit 134 is shown highlighted (e.g., highlighted in Fig. 1 by using a box around the text). For example, while the resource
  • the query-relevant text that is of interest to the user can be embedded much further down in the document and made more easily
  • Highlighting of query-relevant text can be accomplished using colored highlighting behind the text.
  • "highlighting" can be accomplished by bolding the text, using a different font family, using a different text o color, or by various combinations thereof.
  • Fig. 2 is a block diagram of an example process flow 200 for identifying resource search tidbits 202 in the tidbit processor 1 14.
  • the tidbit processor 113 can be implemented as a component of the search system 1 10, or can be a separate system in data communication with the search system 110.
  • the resource search tidbits 2025 identified by the tidbit processor 1 13 are called "resource search tidbits.”
  • Resource search tidbits are tidbits that are eligible to be used on a client device 106 to search a resource for query-relevant text corresponding to the tidbits as part of a resource search operation.
  • the resource search operations which is described in more detail below, occurs in response to selecting a search result that identifies the resource.
  • the tidbit processor 113 receives as input the query 109, a resource URL 206 for each resource identified as being relevant to the query 109, one or more tidbits 208 (e.g., tidbiti through tidbit n ) extracted that the search system 1 10 has identified as including query-relevant text, and a resource 105 identified by the URL 206 and from which the tidbits 208 are extracted.
  • tidbits 208 e.g., tidbiti through tidbit n
  • the tidbit processor 113 can identify resource search tidbits (RSTs) 202 in addition to the URLs provided to the client device
  • the query 109 can include the one or more user-defined query terms, such as0 words, numbers, etc. that are input into the search query field of a Web browser
  • the search system 110 can generate one or more tidbits 208 that correspond to each resource 105 identified as being responsive to the query 109. Based on the other inputs it receives, the tidbit processor 113 can reduce the list of candidate tidbits 208 to just those tidbits 208 that are appropriate for use as resource search tidbits (RSTs) 202.
  • RSTs resource search tidbits
  • tidbits related to 1975 Japanese pachinkos can be identified by the search system 110 in response to the query "pachinko 1975 Japan" and provided to the tidbit processor 1 13, only a handful (e.g., one to ten) may ultimately end up being used to generate resource search tidbits (RSTs) 202.
  • the candidate tidbits not used for resource search tidbits (RSTs) 202 can be those eliminated from consideration (e.g., using eligibility rules) by the tidbit processor 113 when comparing the tidbits 208 to the query 109, the URL 206, and the resource 105.
  • Figs. 3A - 3C are Venn diagrams illustrating an example eligibility rule for determining whether a tidbit is eligible for a resource search operation.
  • the example Venn regions include a resource region and a tidbit region.
  • the resource region is representative of one or more features associated with a resource and the terms that are included in those features.
  • Example features associated with the resource include the URL of the resource, the title of the resource, and even the resource itself.
  • the tidbit region is representative of the terms in the tidbit.
  • tidbit eligibility rules if a particular tidbit includes at least one query term that is not included in the title of the resource, then the tidbit can be used as a resource search tidbit (RST). In other implementations, if a particular tidbit includes at least one query term that is not included in the title of the resource or in the resource locator (e.g., URL) of the resource, then the tidbit can be used as a resource search tidbit (RST).
  • Other eligibility rules can also be used, such as rules that take into account the display formatting of query terms in the resource, etc.
  • rules can also be based on the use of word variants, synonyms, or edit distances.
  • word variants or words based on word stems
  • semantic matching when used in tidbit eligibility rules, can include synonym pairs such as "Eisenhower” and “Ike,” “Bill Clinton” and “President Clinton,” or "green” and “environmental.”
  • synonym matching can depend on the context (e.g., other text in the resource), such as to avoid false matches, for example, of the color green versus the "green” (environmental) movement.
  • Venn diagram 300 illustrates the use of an example eligibility rule that results in the selection of a resource search tidbit j (RST j ) 302.
  • a resource region 304 within the Venn diagram includes query terms 1, 2 and 3, meaning that the query terms 1, 2 and 3 are included in the one or more features represented by the region 304, e.g., the resource's title, URL or both.
  • a tidbit j region 306 includes query terms 3 and 4, meaning that the query terms 3 and 4 are included in the tidbit j .
  • the overlap of the regions 304 and 306 is indicated by the intersection 308 that includes the query term 3 that occurs both in the resource feature(s) (e.g., the title and/or URL) and in the tidbit j .
  • the tidbit is deemed eligible for being a resource search tidbit (e.g., the RST j 302).
  • Venn diagram 310 illustrates the use of an example eligibility rule that results in the selection of a resource search tidbit k (RST k ) 312.
  • a resource region 314 within the Venn diagram includes query terms 1 and 2, meaning that the query terms 1 and 2 are included in the one or more features represented by the region 304, e.g., the resource's title, URL or both.
  • a tidbit k region 316 includes query term 3, meaning that the query term 3 is included in the tidbit k .
  • the overlap of the regions 314 and 316 is the region 314 itself, as query terms 1 and 2 occur both in the resource feature(s) (e.g., the resource's title and/or URL) and in the tidbitk.
  • the tidbit is deemed eligible for being a resource search tidbit (e.g., the RST k 312).
  • Venn diagram 320 illustrates the use of an example eligibility rule that results in not selecting a resource search tidbit m (RST m ) 322.
  • a resource region 324 within the Venn diagram includes query terms 1, 2, 3 and 4, meaning that the query terms 1, 2, 3 and 4 are included in the features represented by the region 304, e.g., the resource's title, URL or both.
  • a tidbit m region 326 includes query terms 3 and 4, meaning that the query terms 3 and 4 are included in the tidbit m .
  • the overlap of the regions 314 and 316 is the region 314 itself, as query terms 3 and 4 occur both in the resource feature(s) (e.g., the title and/or URL) and in the tidbit m .
  • the tidbit is not eligible for being a resource search tidbit (e.g., the RST m 322).
  • the tidbit fails to meet eligibility requirements, for example, for being included in the selection environment 132 described with reference to Fig. 1.
  • determining whether a tidbit is eligible for a resource search operation can result when all of the query terms are included in the tidbit.
  • Fig. 4 is a flow diagram of an example process 400 for identifying resource search tidbits.
  • the tidbit processor 113 for example, can perform the steps of the process 400.
  • a query that includes one or more query terms is received (402).
  • the tidbit processor 113 can receive the query 109, which can originate from the client device 106.
  • a user can enter the query terms (e.g., "pachinko 1975 Japan") of the query 109 in a search box of a Web browser or other user application.
  • each tidbit being query-relevant text extracted from the resource (404).
  • the tidbit processor 113 can receive the tidbits 208 from the search system 1 10, which can automatically send one or more tidbits with any resource that is responsive to the query processed by the search system 110. If the query 109, for example, is "pachinko 1975 Japan," then the tidbits 208 can be query- relevant text extracted from resources 105 (e.g., Web pages) that correspond to the query 109 entered by the user on the client device 106. For instance, example tidbits 208 can include "in 1975, tens of thousands of Japanese pachinkos were replaced" or "Japan sent boatloads of reconditioned pachinkos to the US in 1975," to name a few examples.
  • the tidbit from the resource is examined (406). Examination can include, for example, text in the tidbit 208 to determine if query terms within the tidbit 208 are contained in the title of the resource 105 and/or embedded within the resource's resource locator (e.g., the resource's URL).
  • the tidbit is marked as being a resource search tidbit (410).
  • the tidbit 208 e.g., "in 1975, tens of thousands of Japanese pachinkos were replaced."
  • the "marking" can occur when the tidbit processor 1 13 outputs or otherwise identifies the tidbit 208 as a resource search tidbit (RST) 202.
  • the tidbits 208 provided by the search system 1 10 can be limited initially to only those tidbits 208 that correspond to a subset of the resources, such as only those resources on the first page of search results. Later, if the user begins reviewing search results on a subsequent page, the search system 110 can provide tidbits 208 for additional resources 105, as needed.
  • a corresponding search result responsive to the query is provided, with at least one search result including a resource search tidbit (414).
  • At least one search result includes a resource search tidbit when at least one resource search tidbit is identified as being eligible for a resource search operation.
  • the search system 110 can provide a search result 109. If the resource search tidbit 202 is, for example, part of the snippet of the search result, the resource search tidbit can be marked by use of HTML ⁇ span> tags. Other ways of marking a resource search tidbit can also be used.
  • Fig. 5 is a flow diagram of an example process 500 for determining whether a tidbit for a resource is eligible for a resource search operation.
  • the tidbit processor 113 can perform the steps of the process 500.
  • Query terms in a resource region are identified (502).
  • the resource region can include the resource itself, and/or specific portions of the resource, and/or the URL of the resource, and/or other features of the resource.
  • a resource 105 related to pachinkos can include one or more titles and subtitles within the text of the resource, and can be identified by a corresponding URL.
  • Individual query terms from the user's query 109 can be identified in the title section, and/or the URL of the resource.
  • Query terms in the tidbit are identified (504).
  • the query terms identified in the tidbit e.g., one of the tidbits 208 can already have been tagged by the search system 1 10. If not, the query terms in the tidbit can be identified with reference to those query terms in the query 109.
  • Query terms in the tidbit are compared to query terms in the resource region (506).
  • synonyms can be used to match query terms to the title section, such as "Ike” (e.g., as a query term) for "Eisenhower” (e.g., as a word in the title section) to name one example.
  • query terms can also be compared to the resource locator (e.g., URL).
  • RSTs resource search tidbits
  • "including” can include query term matching using synonyms, word stemming and edit distances.
  • the tidbit processor 113 After comparing one of the tidbits 208 with the title section of the resource 105, can output the tidbit 208 as a resource search tidbit (RST) 202.
  • RST resource search tidbit
  • Generation of the RST 208 can include the tidbit itself plus any additional information needed to place the RST 208 in the selection environment 132 and to enable ultimate selection of the RST 208 by the user and navigation to the
  • a resource 105 can have more than one tidbit 208 provided for it, and the tidbit processor 113 can process all of the tidbits for the resource to determine which tidbits 208, if any, are candidates for becoming eligible for becoming resource search tidbits (RSTs) 202.
  • RSTs resource search tidbits
  • the tidbit processor 113 can stop processing tidbits 208 for a resource 105 when a threshold number (e.g., five RSTs 202) have been identified, so as not to overwhelm the user with too many RSTs 202 in a selection environment of a resource search operation.
  • a threshold number e.g., five RSTs 202
  • all tidbits 208 for a resource 105 can be processed by the tidbit processor 1 13, and the best RSTs 202 can be provided to the user, discarding, for example, RSTs 202 of lower quality as determined by a ranking algorithm.
  • the tidbit processor 113 can generate at least one RST 1 13 even if not all of the query terms are exact matches to query-relevant text within the resource 105 in order to have at least one RST 113 that the user can use.
  • next tidbit is obtained (514). Processing the next tidbit can resume at step (504) of the process 500. For example, query terms in the tidbit are identified (504), and so on for the next tidbit and for each tidbit processed.
  • next resource is obtained (518), and processing the next resource can resume at step (502) of the process 500.
  • the process 500 ends (520).
  • Fig. 6 is a block diagram of an example process for associating resource search tidbits with resource locators from a search results page.
  • An example search results page 602 lists search results 608a-608c that correspond to a search query 604.
  • a user running a Web browser on the client device 106 can enter the search query 604 (e.g., "new widget features") in order to access Internet information related to widgets having new features.
  • the client device 106 can send the query 109 (e.g., including query terms from the user's search query 604) over the network 102, where it can be handled by a search system 110.
  • the search system 110 can return the search results 1 11.
  • the search results 11 1 can be displayed as the individual search results 608a-608c.
  • These search results 608a-608c correspond to the resources 105 described with reference to Fig. 1.
  • a resource title 610a e.g., "Product Review for Widget”
  • the resource title 610a also includes one of the query terms of the search query 604, namely "Widget.”
  • the search result 608a also includes a snippet 612a of "Our new widget has new features...If you desire a new full-featured widget." in which the query terms, or likenesses thereof, are bolded.
  • the likenesses of the query terms of the search query 604 can include synonyms, word stems or variants (e.g., "full-featured"), and words within a threshold edit distance.
  • the user can click on the URL to navigate to the web page associated with the resource locator 614a.
  • the other search results on the search results page 602 namely the search results 608b and 608c each have their respective titles 610b and 610c, snippets 612b and 612c, and resource locators 614b and 614c.
  • terms in the snippets that "match" the query terms of the search query 604 are also bolded.
  • words in titles, snippets and resource locators can be highlighted in various ways, such as with different colors of highlighting (e.g., a different color for each query term), shading, different font colors, different font families, bolding, italics, or any other mechanism for providing a different visible look to the user.
  • hovering over, or clicking on, a query term can cause all instances of that query term to be highlighted in some way.
  • Resource search tidbit information 622 which identifies resource search tidbits for each search result 608, is also provided with the search results page.
  • the resource search tidbit information 622 need not be displayed as part of the page; instead, the information can be of the form of marked resource search tidbits for each search result.
  • a resource search tidbit can be query-relevant text that is independent of the query-relevant text of a snippet for a search result, i.e., the resource search tidbit may be a block of text that is not part of the snippet.
  • the resource search tidbit information 622 can include, for each search result (e.g., search results 608a -608c), the search result's resource locator (e.g., URL) and associated resource search tidbit.
  • search result 608a the Web browser executing on the client device 106 can process, in response to a selection of the search result 608a, the two resource search tidbit (as indicated by "URLi: RSTn, RST12") to determine whether a resource search operation is to be performed.
  • the associations between resource search tidbits and resource locators can be stored, for example, by processing a document object model (DOM) representation of the search results page.
  • DOM document object model
  • Web browser applications can use various internal representations of the document, such as a document object model (DOM) representation, for managing and rendering documents to be displayed to the user.
  • DOM document object model
  • Any of the representations can be used, for example, to associate resource locators (e.g., URLs) with resource search tidbits (RSTs), such as will be described with respect to the process flow diagram Fig. 1 1.
  • resource locators e.g., URLs
  • RSTs resource search tidbits
  • the Web browser's rendering module (e.g., part of the Web browser executing on the user's client device 106) can translate a displayed markup language document using some type of translation, such as to a DOM representation.
  • the translation can analyze the internal representation of the current document, extract text from the text nodes of the representation, and send the text to a browser translation module for translation.
  • the page translator module can receive the translated text from the browser translator module and updates the internal representation.
  • the rendering component of the browser can then render the updated internal representation.
  • the term "web browser” when used herein can refer to any web browser application, any browser extension, or any other program running on the client (or server) that facilitates browsing online content.
  • the DOM representation of a document is in the form a tree of node objects. Each node corresponds to a part of the document. Nodes can be various types including, for example, root nodes, element nodes, attribute nodes, text nodes and script nodes.
  • a text node is a node corresponding to text in the document, and includes text stored in the node.
  • An element node is a node corresponding to an annotation in the document such as ⁇ html> tags or ⁇ title> tags.
  • An attribute node is a node
  • a script node includes an executable script.
  • a DOM representation can also include other types of nodes.
  • the browser By traversing the DOM of the search results page, the browser identifies the resource search tidbits that have been marked for each URL and stores the association in memory. The association is then accessed each time a page is requested by a selection of a search result, and the web browser uses the association to determine which resource search tidbits to search for in a given page. Using the resource search tidbits for the page, the web browser determines whether the resource search tidbits meet a resource search operation threshold condition.
  • Fig. 7A is an illustration of an example rendering of a resource for which a portion of text matching the query-relevant text of the resource search tidbit does not meet a search operation threshold condition.
  • the rendering shows an example page 702.
  • the page 702 displayed represents an example Web Page that can be rendered if the user selects the search result 608a, as described with reference to Fig. 6.
  • communication by the client device 106 across the network 102 e.g., an HTTP get
  • the page 702 can be rendered, for example, by a Web browser executing on the user's client device 106.
  • the Web page content 708 is displayed, including any graphics and text associated with the resource.
  • the Web browser on the client device 106 can have the ability to highlight the query-relevant text associated with the resource search tidbits if, for example, the associations between the resource locator (e.g., the resource's URL) and the resource search tidbits are accessible from document object models (DOMs) from the previous search results page stored in computer memory.
  • the associations between the resource locator e.g., the resource's URL
  • the resource search tidbits are accessible from document object models (DOMs) from the previous search results page stored in computer memory.
  • the page 702 does not include a selection environment 132 because, in this example, the query-relevant text associated with resource search tidbits (e.g., "RSTn and RST12") are near enough to the "top" of the Web page content 708 (e.g., above the "fold") so as not to warrant displaying a control that allows the user to quickly navigate significantly "lower" on the Web page.
  • the query-relevant text associated with resource search tidbits e.g., "RSTn and RST12”
  • Fig. 7B is an illustration of an example rendering of a resource for which a portion of text matching the query-relevant text of the resource search tidbit does meet a search operation threshold condition.
  • the rendering is of an example page 722.
  • the page 722 displayed represents an example Web Page that can be rendered if the user selects the search result 608c, as described with reference to Fig. 6.
  • both the Web page title 724 and the address 726 match the resource locator 614c (e.g., "www.examplel435.com/business/classicgadgets.html").
  • the client device 106 across the network 102 e.g., "Get URL 3 " involves requesting the resource associated with the resource locator 614c.
  • the page 722 can be rendered, for example, by a Web browser executing on the user's client device 106.
  • the Web page content 728 is displayed, including any graphics and text associated with the resource.
  • the text corresponding to the resource search tidbits associated with the resource are positioned sufficiently lower within the content of the Web page so as not to be displayed when the Web page appears. Essentially, the text of the resource search tidbits are scrolled off the page.
  • the browser executing on the client device 106 can recognize the rendered location of the query- relevant text and automatically display a selection environment 730.
  • a best matches message 732 included in the selection environment 730 can echo the query terms (e.g., "new widget features") that are included in the user's original search query 604, as described with reference to Fig. 6.
  • the selection environment 730 can further include the resource search tidbits (e.g., "RST31 and RST32") associated with the query-relevant text passages, in this case selection environment options 734 and 736.
  • the option 734 can be selected by the user to navigate to the portion of the web content containing the text 738 matching the resource search tidbit RST 31 , and the option 736 to navigate to the text 740 matching the resource search tidbit RST 32 .
  • the option 734 is depicted in Fig. 7B as containing the text "RST 32 " in order to make clear the mapping of the RST to its corresponding query-relevant text in the resource.
  • the option 736 includes the tidbit "several of our new-featured widgets" which matches the query-relevant passage 740.
  • query terms that appear in tidbits and query-relevant text can be highlighted in any way (e.g., shown here using bolding).
  • the query-relevant passages 738 and 740 are displayed in a phantom region 742 used here to indicate and extension of the web page 722 beyond the active viewport.
  • the Web browser on the client device 106 has accesses associations between the resource locator (e.g., the resource's URL) and the resource search tidbits are accessible from data gathered from document object model (DOM) and stored in computer memory.
  • DOM document object model
  • Fig. 8 is a flow diagram of an example process 800 for performing a resource search operation.
  • the client device 106 (described with reference to Fig. 1) can perform the steps of the process 800. More specifically, the process 800 can be executed, for example, by computer applications that are part of, our in
  • Web browser applications or other Web search and content rendering applications running on a user's client device 106.
  • a search results page including search results responsive to the query is received (802).
  • Each search result includes a resource locator that specifies the location of a resource identified as being relevant to the query.
  • At least one search result includes a resource search tidbit.
  • the resource search tidbit is query-relevant text extracted from the resource.
  • the resource search tidbit is eligible for a research search operation in response to the resource specified by the resource locator of the at least one search result being rendered on the client device.
  • the search results page can be the web page 126 that displays the search results 11 1 provided by the search system 110.
  • the search results 11 1 can include snippets from and links to resources 105 that the search system 110 identifies as responsive to the user's query 109.
  • the search results 1 11 can be displayed or rendered within a graphical user interface on the screen of the user's client device 106. For example, if the user's query 109 is "pachinko 1975 Japan," then the search results page displayed as the web page 126 can include Web or Internet "hits" related to the query. As result, the user can see, within each of the search results 11 1, resource locators (e.g., links or URLs) for each resource 105, and snippets that can contain some or all of the individual query terms from the query 109.
  • resource locators e.g., links or URLs
  • a selection of the at least one search result is received at the client device (804). For example, from the search results 11 1 displayed on the user's client device 106, the user can select one of the individual search results 1 11. Continuing with the current example, the user can select a particular search result, such as a search result 1 11 corresponding to the history of pachinko games in Japan. The user's selection of the particular search result 1 11, for example, can cause the Web browser application to obtain the URL (or other resource locator) that is associated with or embedded within the search result 11 1.
  • the resource specified by the resource locator of the at least one search result is received (806).
  • the Web browser application can access the corresponding resource 105. Access can occur, for example, over the network 102, using the URL of the resource 105.
  • the resource is rendered at the client device (808).
  • the resource 105 can be displayed within the user's Web browser, such as to display the Web page that provides a history of pachinko games in Japan.
  • a portion of text in the resource that matches the query-relevant text of the resource search tidbit is identified (810).
  • an application on the client device 106 identifies query-relevant text 138 corresponding to the specific resource search tidbit 134.
  • the resource search operation is performed only if the identified portion of the text matching the query-relevant text of the resource search tidbit meets a search operation threshold condition (812). For example, in some implementations, certain threshold conditions must exist before the resource search operation is performed. Specifically, unless the query-relevant text 138 corresponding to a specific resource search tidbit 134 appears below the "fold" (e.g., a pre-determined number of pixels from the top of the display or outside of the current view port), the selection environment 132 is not displayed.
  • a search operation threshold condition e.g., a pre-determined number of pixels from the top of the display or outside of the current view port
  • the selection environment 132 can display all resource search tidbits 134 no matter how many of the resource search tidbits' corresponding query-relevant text passages appear above or below the fold. In other implementations, the selection environment 132 displays only the resource search tidbits for which corresponding text passages are below the fold.
  • Fig. 9 is a flow diagram of an example process 900 for determining whether a portion of text in a resource matches the query-relevant text of a resource search tidbit.
  • the client device 106 (described with reference to Fig. 1) can perform the steps of the process 900. More specifically, the process 900 can be executed, for example, by computer applications that are part of, or in communication with, Web browser applications or other Web search and content rendering applications running on a user's client device 106.
  • the resources that are processed by the search system 110 are cached resources, and the resources may have been updated by administrators or users after the resource is stored in a cache of the search system 1 10. Accordingly, the copy of the resource stored in the cache of the search system 1 10 may not exactly match the copy of the resource that is provided by the website hosting the resource. Accordingly, the client device, in some implementations, is configured to search for matching text based on an exact match and a closest match criteria.
  • a portion of text in the resource that exactly matches the query-relevant text of the resource search tidbit is searched for (902).
  • a Web browser application running on the client device 106 can search for query-relevant text in a resource 105 that matches all of the text in the resource search tidbit.
  • the query-relevant text 138 in this case can contain all of the query terms (e.g., all of the terms in "pachinko 1975 Japan").
  • the portion of text in the resource that most closely matches the text of the resource search tidbit is identified (908).
  • the text identified in the resource 105 can include exact matches to most of the terms in the query 109 and close matches to the remaining terms.
  • a portion of text with a minimum edit distance from the query- relevant text of the resource search tidbit relative to other portions of the text in the resource is identified as being the closest match.
  • prefix matching can be used, such as to identify terms in the query-relevant text having the longest prefix match to terms in the resource search tidbit.
  • postfix matching can be used, such as to identify terms in the query-relevant text having the longest postfix match to terms in the resource search tidbit.
  • Other types of matching can also be used, e.g., longest string matching, etc.
  • Fig. 10 is a flow diagram of an example process 1000 for navigating to a portion of a resource in response to selecting a resource search tidbit.
  • the client device 106 (described with reference to Fig. 1) can perform the steps of the process 1000. More specifically, the process 1000 can be executed, for example, by computer applications that are part of, our in communication with, Web browser applications or other Web search and content rendering applications running on a user's client device 106.
  • a selection environment is displayed with the rendered resource, the selection environment displaying the portion of text in the resource that matches the query- relevant text of the resource search tidbit (1002).
  • the selection environment 132 can also be displayed.
  • the page 128 can be a web page related to pachinko games
  • the selection environment 132 can include one or more resource search tidbits 134 corresponding to query-relevant text portions in the resource 105 that are related to the query terms of the query 109 (e.g. "pachinko 1975 Japan").
  • navigation occurs to the portion of the resource that includes the portion of text in the resource that matches the query-relevant text of the resource search tidbit (1004). For example, if the user selects a particular resource search tidbit 134, such as one containing the tidbit "Japan sent boatloads of reconditioned pachinkos to the US in 1975," then the user's Web browser can navigate to that portion of the resource 105 that contains that text. Specifically, the Web page can automatically scroll to the passage of interest as shown in Fig. l and indicated by an updated display of the page 128 and a new position of the scroll bars 130.
  • a particular resource search tidbit 134 such as one containing the tidbit "Japan sent boatloads of reconditioned pachinkos to the US in 1975”
  • Fig. 1 1 is a flow diagram of an example process 1100 for performing a resource search operation using an associating of resource locators and resource search tidbits.
  • the client device 106 (described with reference to Fig. 1) can perform the steps of the process 1 100. More specifically, the process 1 100 can be executed, for example, by computer applications that are part of, our in communication with, Web browser applications or other Web search and content rendering applications running on a user's client device 106.
  • the resource search tidbit of the at least one search result is associated with the resource locator of the at least one search result (1 102).
  • the nodes of the tree can include the association of the resource search tidbit to a resource locator in a search result.
  • the association is stored in a computer memory (1 104), and the association is accessed in the computer memory in response to a selection of a search result from the search results page (1106). For example, when the user selects one of the search results 11 1 from the Web page 126, the Web browser executing on the user's client device 106 can access the association of the resource search tidbits and the URL corresponding to the selected search result.
  • the portion of text in the resource that matches the query-relevant text of the resource search tidbit associated with the resource locator of the at least one search result that matches the resource locator of the resource is identified (1 108).
  • some of the processing described above as occurring at the client device 106 can instead occur at the server.
  • the search system 110 can perform most or all of the processing needed to determine eligibility of resource search tidbits.
  • the selection environment 132 can always be displayed regardless of whether the query-relevant text of the resource 105 already appears on the screen.
  • a scroll bar in order to manage large numbers of (e.g., more than 1 to 5) resource search tidbits (RSTs) in the selection environment 132, a scroll bar can be added to allow the user to position to an RST of interest, such as one further down the list.
  • RSTs resource search tidbits
  • additional tools can be added to the selection environment 132, such as a tool to check off passages that have already been read.
  • the user can be provided with options to hide selected RSTs, such a RSTs most associated with a specific query term in which the user is no longer interested in seeing associated RSTs.
  • user options can be provided to allow the RSTs to be sorted in specific ways (e.g., by one or more query terms).
  • a search feature can be added to the selection environment 132 that allows the user, for example, to search for specific text strings within the collection of RSTs.
  • automatic highlighting can occur on the portions of text in a resource that match the text of the resource search tidbit, regardless of whether the resource search tidbit meets a search operation threshold condition. For example, the text can be highlighted in light yellow upon initial display of the resource. If a selection environment is displayed, and if the user then selects the RST associated with the query-relevant text, the highlighting can be changed, for example, to a strong yellow.
  • highlighting can be changed to an off color, such as by changing the initially-highlighted in yellow text to violet or some other non-yellow highlighting color. In this way, the user can be informed of where he or she has already been on the Web page.
  • the server system 110 can provide a byte offset and byte length tuple that identifies the distance from the start of the resource, in bytes, of a tidbit that is of a size equal to the byte length.
  • offset references can also be used, e.g., a paragraph number and/or sentence number.
  • the matching operations at the client side can be changed accordingly.
  • the client device can request resource search tidbits for a resource from the search system 110 asynchronously, e.g., in response to selecting a resource from a search result.
  • the search system 1 10 can then perform the resource search tidbit operations described above for only that resource, and provide the identified resource search tidbits to the client device for processing.
  • implementation reduces processing load on the search system 1 10.
  • the browser application can treat the snippet as a default resource search tidbit, and can perform the eligibility operations, matching operations, highlighting operations, and search environment related operations described above using the snippet as input.
  • Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
  • Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.
  • the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus.
  • a computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them.
  • a computer storage medium is not a propagated signal
  • a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal.
  • the computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).
  • the operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer- readable storage devices or received from other sources.
  • data processing apparatus encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a
  • the apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC
  • the apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
  • the apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
  • a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment.
  • a computer program may, but need not, correspond to a file in a file system.
  • a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
  • a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output.
  • the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • the essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data.
  • a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • a computer need not have such devices.
  • a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.
  • Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
  • a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • keyboard and a pointing device e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a
  • Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.
  • the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network.
  • Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
  • LAN local area network
  • WAN wide area network
  • inter-network e.g., the Internet
  • peer-to-peer networks e.g., ad hoc peer-to-peer networks.
  • the computing system can include clients and servers.
  • a client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
  • a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device).
  • client device e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device.
  • Data generated at the client device e.g., a result of the user interaction

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne des procédés, des systèmes et un appareil, qui comprennent des programmes informatiques codés sur un moyen de stockage sur ordinateur, afin d'identifier un contenu pertinent pour une requête dans une ressource identifiée par un résultat de recherche en réponse à la requête. Dans un aspect, un procédé inclut l'identification de morceaux choisis de recherche de ressources pour une ressource, chaque morceau choisi de recherche de ressources étant éligible pour une opération de recherche de ressources pour la ressource. Les morceaux choisis de recherche de ressources sont munis de résultats de recherche vers un dispositif client. En réponse à la sélection par un utilisateur d'une ressource identifiée par un résultat de recherche, le dispositif client identifie du texte dans la ressource correspondant au texte pertinent pour la requête du morceau choisi de recherche de ressources et réalise une opération de recherche de ressources sur la ressource si le texte identifié satisfait une condition de seuil d'opération de recherche.
PCT/US2010/059415 2009-12-08 2010-12-08 Opérations de recherche de ressources WO2011071990A2 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CA2783344A CA2783344C (fr) 2009-12-08 2010-12-08 Operations de recherche de ressources
AU2010328181A AU2010328181B2 (en) 2009-12-08 2010-12-08 Resource search operations
EP10795516A EP2510463A2 (fr) 2009-12-08 2010-12-08 Opérations de recherche de ressources

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US26768109P 2009-12-08 2009-12-08
US61/267,681 2009-12-08
US12/839,721 2010-07-20
US12/839,721 US8392449B2 (en) 2009-12-08 2010-07-20 Resource search operations

Publications (2)

Publication Number Publication Date
WO2011071990A2 true WO2011071990A2 (fr) 2011-06-16
WO2011071990A3 WO2011071990A3 (fr) 2011-08-04

Family

ID=44083043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/059415 WO2011071990A2 (fr) 2009-12-08 2010-12-08 Opérations de recherche de ressources

Country Status (5)

Country Link
US (2) US8392449B2 (fr)
EP (1) EP2510463A2 (fr)
AU (1) AU2010328181B2 (fr)
CA (1) CA2783344C (fr)
WO (1) WO2011071990A2 (fr)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9552422B2 (en) 2010-06-11 2017-01-24 Doat Media Ltd. System and method for detecting a search intent
US9372885B2 (en) 2010-06-11 2016-06-21 Doat Media Ltd. System and methods thereof for dynamically updating the contents of a folder on a device
US9529918B2 (en) 2010-06-11 2016-12-27 Doat Media Ltd. System and methods thereof for downloading applications via a communication network
US20120226676A1 (en) * 2010-06-11 2012-09-06 Doat Media Ltd. System and methods thereof for adaptation of a free text query to a customized query set
US10713312B2 (en) 2010-06-11 2020-07-14 Doat Media Ltd. System and method for context-launching of applications
US9069443B2 (en) 2010-06-11 2015-06-30 Doat Media Ltd. Method for dynamically displaying a personalized home screen on a user device
US9141702B2 (en) 2010-06-11 2015-09-22 Doat Media Ltd. Method for dynamically displaying a personalized home screen on a device
US9323844B2 (en) 2010-06-11 2016-04-26 Doat Media Ltd. System and methods thereof for enhancing a user's search experience
KR101741698B1 (ko) * 2010-10-18 2017-05-31 삼성전자주식회사 검색 서비스 제공방법 및 이를 적용한 디스플레이 장치
KR101842457B1 (ko) * 2011-03-09 2018-03-27 엘지전자 주식회사 이동 단말기 및 그의 텍스트 커서 운용방법
US8655913B1 (en) * 2012-03-26 2014-02-18 Google Inc. Method for locating web elements comprising of fuzzy matching on attributes and relative location/position of element
US11157570B2 (en) * 2012-05-24 2021-10-26 Evernote Corporation Related notes and multi-layer search in personal and shared content
US9348846B2 (en) 2012-07-02 2016-05-24 Google Inc. User-navigable resource representations
US9235858B1 (en) * 2012-07-25 2016-01-12 Amazon Technologies, Inc. Local search of network content
US8965880B2 (en) * 2012-10-05 2015-02-24 Google Inc. Transcoding and serving resources
US20150169701A1 (en) * 2013-01-25 2015-06-18 Google Inc. Providing customized content in knowledge panels
US9300760B2 (en) * 2013-01-28 2016-03-29 Google Inc. Machine-specific instruction set translation
WO2014146230A1 (fr) * 2013-03-18 2014-09-25 Nokia Corporation Procédé et appareil pour interroger des ressources par un champ de recherche
US9230023B2 (en) * 2013-04-16 2016-01-05 Google Inc. Search suggestion and display environment
US20170132314A1 (en) * 2014-06-02 2017-05-11 Hewlett-Packard Development Company, L.P. Identifying relevant topics for recommending a resource
CN105138697B (zh) * 2015-09-25 2018-11-13 百度在线网络技术（北京）有限公司 一种搜索结果的展现方法、装置及系统
US11157493B2 (en) * 2015-12-30 2021-10-26 Facebook, Inc. Optimistic data fetching and rendering
US10621237B1 (en) * 2016-08-01 2020-04-14 Amazon Technologies, Inc. Contextual overlay for documents
US11816135B2 (en) * 2019-02-26 2023-11-14 Greyb Research Private Limited Method, system, and computer program product for retrieving relevant documents

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5946678A (en) * 1995-01-11 1999-08-31 Philips Electronics North America Corporation User interface for document retrieval
US6895430B1 (en) * 1999-10-01 2005-05-17 Eric Schneider Method and apparatus for integrating resolution services, registration services, and search services
US5991739A (en) * 1997-11-24 1999-11-23 Food.Com Internet online order method and apparatus
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6772139B1 (en) * 1998-10-05 2004-08-03 Smith, Iii Julius O. Method and apparatus for facilitating use of hypertext links on the world wide web
US6763496B1 (en) * 1999-03-31 2004-07-13 Microsoft Corporation Method for promoting contextual information to display pages containing hyperlinks
US6785671B1 (en) * 1999-12-08 2004-08-31 Amazon.Com, Inc. System and method for locating web-based product offerings
US7325201B2 (en) * 2000-05-18 2008-01-29 Endeca Technologies, Inc. System and method for manipulating content in a hierarchical data-driven search and navigation system
US6704024B2 (en) * 2000-08-07 2004-03-09 Zframe, Inc. Visual content browsing using rasterized representations
US20020103920A1 (en) * 2000-11-21 2002-08-01 Berkun Ken Alan Interpretive stream metadata extraction
US6701311B2 (en) * 2001-02-07 2004-03-02 International Business Machines Corporation Customer self service system for resource search and selection
US7404142B1 (en) * 2001-06-29 2008-07-22 At&T Delaware Intellectual Property, Inc. Systems and method for rapid presentation of structured digital content items
US20030055812A1 (en) * 2001-09-14 2003-03-20 Xccelerator Technologies, Inc. Vehicle parts monitoring system and associated method
US7143362B2 (en) * 2001-12-28 2006-11-28 International Business Machines Corporation System and method for visualizing and navigating content in a graphical user interface
US20030154221A1 (en) * 2002-02-13 2003-08-14 Sun Microsystems, Inc. System and method for accessing file system entities
US7333991B2 (en) * 2002-08-05 2008-02-19 Todd E. Vander Hill Digital design and maintenance system and method
GB0316806D0 (en) * 2003-07-17 2003-08-20 Ivis Group Ltd Improved search engine
US8150824B2 (en) * 2003-12-31 2012-04-03 Google Inc. Systems and methods for direct navigation to specific portion of target document
US8370342B1 (en) * 2005-09-27 2013-02-05 Google Inc. Display of relevant results
US8380721B2 (en) * 2006-01-18 2013-02-19 Netseer, Inc. System and method for context-based knowledge search, tagging, collaboration, management, and advertisement
US20080235209A1 (en) * 2007-03-20 2008-09-25 Samsung Electronics Co., Ltd. Method and apparatus for search result snippet analysis for query expansion and result filtering
US7805432B2 (en) * 2006-06-15 2010-09-28 University College Dublin National University Of Ireland, Dublin Meta search engine
US7698344B2 (en) * 2007-04-02 2010-04-13 Microsoft Corporation Search macro suggestions relevant to search queries
US7672938B2 (en) * 2007-10-05 2010-03-02 Microsoft Corporation Creating search enabled web pages
US8364694B2 (en) * 2007-10-26 2013-01-29 Apple Inc. Search assistant for digital media assets
US7853587B2 (en) * 2008-01-31 2010-12-14 Microsoft Corporation Generating search result summaries
US20090204602A1 (en) * 2008-02-13 2009-08-13 Yahoo! Inc. Apparatus and methods for presenting linking abstracts for search results
US7937395B2 (en) * 2008-02-22 2011-05-03 Tigerlogic Corporation Systems and methods of displaying and re-using document chunks in a document development application
US9195754B2 (en) * 2008-06-13 2015-11-24 International Business Machines Corporation Expansion of search result information
TWI393018B (zh) * 2009-02-06 2013-04-11 Inst Information Industry 關鍵詞彙即時擴展方法與系統以及儲存關鍵詞彙即時擴展程式的電腦可讀寫記錄媒體
US8250053B2 (en) * 2009-02-24 2012-08-21 Microsoft Corporation Intelligent enhancement of a search result snippet
US8214357B2 (en) * 2009-02-27 2012-07-03 Research In Motion Limited System and method for linking ad tagged words
US8316039B2 (en) * 2009-05-18 2012-11-20 Microsoft Corporation Identifying conceptually related terms in search query results
US8694505B2 (en) * 2009-09-04 2014-04-08 Microsoft Corporation Table of contents for search query refinement
US8725717B2 (en) * 2009-12-23 2014-05-13 Palo Alto Research Center Incorporated System and method for identifying topics for short text communications
US20120030013A1 (en) * 2010-07-27 2012-02-02 Caroline Tsay Slideshows in search
US8639680B1 (en) * 2012-05-07 2014-01-28 Google Inc. Hidden text detection for search result scoring

Also Published As

Publication number Publication date
WO2011071990A3 (fr) 2011-08-04
AU2010328181A1 (en) 2012-06-28
EP2510463A2 (fr) 2012-10-17
US20130179437A1 (en) 2013-07-11
CA2783344A1 (fr) 2011-06-16
AU2010328181B2 (en) 2015-04-09
CA2783344C (fr) 2018-01-16
US8392449B2 (en) 2013-03-05
US20110137933A1 (en) 2011-06-09

Similar Documents

Publication Publication Date Title
CA2783344C (fr) Operations de recherche de ressources
US8538989B1 (en) Assigning weights to parts of a document
US9355185B2 (en) Infinite browse
US9323808B1 (en) Predictive query suggestion caching
US8898583B2 (en) Systems and methods for providing information regarding semantic entities included in a page of content
US7783644B1 (en) Query-independent entity importance in books
US9104772B2 (en) System and method for providing tag-based relevance recommendations of bookmarks in a bookmark and tag database
US7895595B2 (en) Automatic method and system for formulating and transforming representations of context used by information services
TWI471737B (zh) 具搜尋結果之蹤跡識別系統與方法
KR101060594B1 (ko) 문서 데이터의 키워드 추출 및 연관어 네트워크 구성 장치 및 방법
US20090144240A1 (en) Method and systems for using community bookmark data to supplement internet search results
US9798820B1 (en) Classification of keywords
RU2696305C2 (ru) Браузинг изображений через интеллектуально проанализированные связанные гиперссылкой фрагменты текста
US20140032529A1 (en) Information resource identification system
US20140372873A1 (en) Detecting Main Page Content
US20130254189A1 (en) Using Anchor Text to Provide Context
US9116992B2 (en) Providing time series information with search results
EP3053063B1 (fr) Transition d'un premier environnement de résultats de recherche à un second environnement de résultats de recherche
AU2009322821A1 (en) Previewing search results for suggested refinement terms and vertical searches
JP2011154668A (ja) ウェブページの主意，およびユーザの嗜好を適切に把握して，最善の情報をリアルタイムに推奨する方法
JP2007334502A (ja) 検索装置、方法およびプログラム
US20150161279A1 (en) Displaying Local Site Name Information with Search Results
US9697281B1 (en) Autocomplete search methods
JP2008112310A (ja) 検索装置、情報検索システム、検索方法、検索プログラム、及び記録媒体
KR101421819B1 (ko) 온라인 환경에서의 벌룬을 이용한 키워드 검색 결과 제공 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10795516

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010328181

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2783344

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2010795516

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010795516

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2010328181

Country of ref document: AU

Date of ref document: 20101208

Kind code of ref document: A