Method and apparatus for in-browser related searches - Patents.com

Abstract

In response to a selection of a search area included in a web page displayed within the display area of ​​the browser, the device can request a search on content of the search area, receive a searched query, a search result page for the searched query, and a related search request, and display a first search request indicator and a second search request indicator within a search results area outside the display area and within the browser. The device can receive a selection of the first search request indicator. In response to a selection of the first search request indicator, the device can display content for the first search request indicator within a navigation area of ​​the search results area.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 266,294, entitled "METHOD AND APPARATUS FOR RELATED SEARCH WITHIN A BROWSER," filed December 31, 2021, the disclosure of which is incorporated by reference in its entirety herein.

[0002] A web browser can be used to display content searched for by a search engine, and in response to a user selecting one or more of the search results, the content can be displayed within the web browser. Summary of the Invention

[0003] A method in one general aspect can include triggering a search query for a search area and displaying a search results area that overlaps a display area of ​​the browser (e.g., a content window, a tab content window). The search results area is a window (area) outside the display area but still within the browser. In response to a selection of a search area included in a web page displayed within the display area of ​​the browser, a search request area can be generated that includes one or more related searches that are displayed as search request indicators. The search results area can include a determined query (for the performed search) for the search area. The search results area can include one or more related search requests (i.e., related queries) for the determined query. In some implementations, the search results area can include text identifying the determined query for the search area. The one or more related search requests can be represented within the search results area by search request indicators (e.g., a first search request indicator and a second search request indicator within the search results area). In some implementations, the determined query can be represented by one of the search request indicators. The search results area can include a navigation area in which a search results page is displayed and in which the search results page can be interacted with. Interaction with (selection of) the search request indicator can change the content of the navigation area without changing the search request indicator. [Brief description of the drawings]

[0004] [Fig. 1A and B] FIG. 2 illustrates the rendering of content within a browser's display area, search results area, and navigation area according to one embodiment. [Figure 1C] FIG. 2 illustrates the rendering of content within a browser's display area, search results area, and navigation area according to one embodiment. [Figure 1D] FIG. 2 illustrates the rendering of content within a browser's display area, search results area, and navigation area according to one embodiment. [Figure 1E] FIG. 2 illustrates the rendering of content within a browser's display area, search results area, and navigation area according to one embodiment. [Figure 2A.B] FIG. 2 illustrates another embodiment for rendering content within the display area, search results area, and navigation area of ​​a browser according to one embodiment. [Figure 2C] FIG. 2 illustrates another embodiment for rendering content within a display area, a search results area, and a navigation area of ​​a browser according to one embodiment. [Figure 3A and B] FIG. 2 illustrates another embodiment for rendering content within the display area, search results area, and navigation area of ​​a browser according to one embodiment. [Figure 3C] FIG. 2 illustrates another embodiment for rendering content within the display area, search results area, and navigation area of ​​a browser according to one embodiment. [Figure 3D] FIG. 2 illustrates another embodiment for rendering content within the display area, search results area, and navigation area of ​​a browser according to one embodiment. [Figure 4] FIG. 1 illustrates a computing system and search server for implementing concepts described herein. [Figure 5A] 5 is a flowchart illustrating an exemplary process for rendering content within a browser's display area, search results area, and navigation area according to one implementation. [Figure 5B] 5 is a flowchart illustrating an exemplary process for rendering content within a browser's display area, search results area, and navigation area according to one implementation. [Figure 6] 5 is a flowchart illustrating an example process for determining related search requests for searching selected content within a display area according to one implementation. [Figure 7]FIG. 1 illustrates an example of a general purpose computing device and a general purpose mobile computing device that can be used with the techniques described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] The present disclosure relates to navigation of content related to search results (or indicators thereof) obtained in response to a selected search area. More specifically, the present disclosure relates to providing a search area with a searched (main) query and one or more additional related search queries (related search requests). The search area represents the content of a web page selected by a user of a browser. The search area may represent text that is not an anchor, i.e., text that is not part of a link. In some embodiments, the searched query and one or more related search requests may be represented as operable search request indicators in the search results area. In some embodiments, the one or more related search requests may be represented as operable search request indicators, but the searched query is not represented as an operable search request indicator in the search results area. The search results area may overlap (may cover, may replace) the web page from which the search area was selected. Upon selection of a search area, the browser may initiate a request for a search of the selected text. As part of the request for the selected text, the browser may also provide an identifier of the web page (e.g., location, URL, URI, etc.) to include in a response to the request, the context of the selected text, and / or an amount of related queries (related search queries). The search server may determine the queries for the search space. This query selected by the search server is called the searched query or main query. The search server may also provide a number of related queries (e.g., one, two, etc.). Related queries are other queries that were not searched but are also related to the search space. In some embodiments, the search server may use the web page identifiers and the number (amount) of related queries to rank and select the related queries. In some embodiments, no more than the requested amount of related queries are returned. In some embodiments, the ranking prioritizes related queries with fewer characters. In response to the request provided to the browser, the search server may provide the searched query, a search result page for the searched query, and one or more related queries.

[0006] Thus, the response provided by the search server to the browser is related to the selected search area from content within the webpage. The content can include all of the text visible to the user and can extend beyond what is visible. The text selection from the user may be prioritized in light of relevant related searches. The response may include a search results page. The response may include related search requests. The related search requests may be displayed within the search results area of ​​the browser such that the content of the webpage is maintained (e.g., persists) within the browser while the search results page and the related search requests are displayed. The related search requests may also be provided as interactive indicators (e.g., buttons, links, selectable areas / images, etc.), which are maintained (e.g., persists) within the search results area. At least one of the search requests (the search request indicator) may be selected and content related to the selected search request (i.e., a search results page) may be displayed within the search results area while maintaining the webpage within the browser display area. In some implementations, the content related to the search request (e.g., the search results page) may be presented in a new tab. The search request indicator may continue to be displayed (e.g., maintained or persisted) even while the content of the navigation area of ​​the search results area changes. Thus, the search request indicator allows navigation of the content without losing the context of the searched query. When associated with an operating system (OS) window, a browser may be referred to as a browser window.

[0007] A technical problem associated with content within a web page is that once content to search within a web page is identified, the content within the web page cannot be maintained during the search unless a separate browser, tab, or application is used. When a user selects an area of ​​content, it may become unclear what the user's intended search (query) is, and some disambiguation is required. For example, content within a web page may be copied for searching, the web page may be replaced with a search engine interface, or another browser or tab may be used to search for the content. Computing resources such as memory, bandwidth, and battery are consumed when a user submits multiple queries or when a user needs to open a new tab to perform a search.

[0008] At least one solution to the above technical problem is that search results can be displayed together with related search requests in a search result area of ​​a browser, and thus web page content is maintained (e.g., persisted) in the browser in a separate display area while the search results and related search requests are displayed. At least one technical effect of this technical solution is that the original web page content is not lost while using the search results. Another technical effect of the technical solution is that the original web page content is maintained, and the user can submit additional queries to obtain additional search results while maintaining the original search context (e.g., searched query / main query). When related search requests are selected, the limited display area of ​​the mobile device (e.g., smartphone, tablet, glasses, smartwatch, etc.) may be optimized such that keystrokes and gestures for performing multiple searches are minimized. In this way, search results in the search result area and web page content in the display area can be displayed simultaneously in the browser (e.g., in a browser tab), and multiple searches can be performed with minimal input from the user.

[0009] In some implementations, the search results area may be integrated as part of the browser, which may prevent the search results area from being spoofed (e.g., mimicked) by a third party or a web page content owner. This may be implemented as a security feature, allowing a user to distinguish between legitimate search results obtained by a search query and search results that may be inserted by a third party or a web page provider. Thus, the technical problem of search result spoofing may be avoided by the technical solution of integrating the search results area in the browser as described above. The technical effect of integrating the search results area in the browser is to prevent spoofing.

[0010] As mentioned above, in some implementations, the search results may continue to be displayed (e.g., may be maintained or persisted) in the search results area while the content of the search results is displayed. The content associated with the search results may be simultaneously displayed within a navigation area within the browser (e.g., within a browser tab). Thus, the technical problem of being able to simultaneously navigate the content associated with the search results while viewing the search results in the search results area is solved by the above technical solutions and technical effects.

[0011] The embodiments described herein enable improved guided human-machine interaction, where a webpage is viewed on one side while another query is executed on the viewed webpage and the respective search results are displayed on the other side. The browsing of the webpage and the execution of the query together with the viewing of the results are performed simultaneously using only one user interface. This saves processing resources for maintaining and managing the various user interfaces required for browsing the webpage and for executing queries on the webpage and viewing the results of the respective queries. This reduces the user's interaction with the user interface. Furthermore, various queries can be executed with respect to the selected search area of ​​the webpage and their results can be easily retrieved and viewed using only one user interface. Furthermore, the embodiments described herein require less communication between the browser and the server, because when requesting a search on the content of the search area of ​​the webpage, various variants of the request are taken into account by the server, and the server provides browser data related not only to the searched (main) query but also to (possible) related search requests. The browser can process the related search requests without requiring more extensive communication with the server. A user can easily switch between different requests and their results to view a web page simultaneously in the same interface, thereby improving the user's interaction with the web page.

[0012] The browsers described herein may be executed within a computing device. For example, the browser may be executed within a laptop device. In some implementations, the browser may be executed within a mobile device. Although many of the implementations shown and described herein are shown in portrait mode, any of the implementations described herein may be rendered in landscape mode.

[0013] 1A is a diagram illustrating a web page W1 displayed in a display area 120 of a browser 110. In some embodiments, the display area 120 may be in a tab of the browser 110. As shown in FIG 1A, the web page includes content C1. The content C1 may include image content, text content, and / or the like.

[0014] As shown in FIGS. 1A-1E, browser 110 includes address bar area 114. An address (e.g., a uniform resource locator (URL)) of web page W1 may be shown in address bar area 114 (e.g., input address area 113). Other controls, icons, and / or the like may also be included in address bar area 114. Address bar area 114 may be controlled by and / or associated with browser 110 (e.g., a browser application). Address bar area 114 may be controlled by browser 110 on behalf of web page W1 and / or a provider of web page W1.

[0015] FIG. 1B illustrates a search results area 150 including a search request area 130 (shown as a dashed box) triggered for display within the browser 110. The search results area 150 may also be referred to as an overlay area or overlay window. The search results area 150 (overlay window) may include the search request area 130 and the navigation area 140. The search results area 150 of FIG. 1B may be triggered in response to receiving a search area SA (e.g., text, image) of the content C1. The search area SA may also be referred to as a search area SA of the web page W1. The search area SA of FIG. 1 may be received in response to being selected (e.g., interacted with). In some embodiments, the interaction may include a selection. In some embodiments, the interaction (selection) may occur in a portion of the search area.

[0016] In some embodiments, the interaction and / or selection (or a display thereof) may be used to trigger an action or result. For example, in this embodiment shown in the figure, a search result SA may be selected in FIG. 1A. In response to the selection of the search area SA in FIG. 1A, the browser may initiate a search request for the search area SA in FIG. 1A while the web page W1 is displayed in the display area 120 in FIG. 1B. In some embodiments, the search request is triggered when the search area SA is text or includes text. In some embodiments, the search request is triggered when the search area SA is an image or includes an image. In some embodiments, the search request is triggered when the selection area SA is not identified as operable by the web page W1. The content of a web page is operable when the web page includes markup tags that combine the selection of content with an event. Anchor tags, tags with on-click mouse events, etc. are examples of content that is operable by the web page W1. That is, text or images already actionable in webpage W1 (e.g., actionable text, actionable images) may be selectable to perform that action (e.g., navigate to another webpage W1 or initiate an action defined by webpage W1). Content identified as actionable by a webpage may perform an action when selected and / or cause the display of a pop-up menu when selected / interacted with, including the action specified by webpage W1 and / or other actions to perform (e.g., a pop-up window confirming whether to open the content associated with the link in a new tab, a new browser window, copy the link to the clipboard, open the link in an incognito window, etc.). When content is identified as actionable by webpage W1, the browser may not automatically override that action by automatically sending a search request for the search area.In some embodiments, the request for a search may be an option in a pop-up menu. If the content is not identified as operable and is interacted with (e.g., selected) by the user, the browser may automatically (i.e., without further interaction from the user) send a request to search for the content represented by the search area SA. The search request may be triggered, for example, by a user of a mobile device via a search of the content within the search area SA (e.g., a text search, an image search, and / or other). In some embodiments, the request for a search may be triggered in response to a selection of the search area SA being completed. In some embodiments, the request for a search (based on the search area SA) may be triggered in response to a long press selection of the search area SA (e.g., selecting the search area for a threshold period). In some embodiments, a user interface for triggering a search query based on the search area SA may be used.

[0017] The search request includes the content of the search area. The content of the search area may include at least one of text or one or more images. The search request may include an identifier of the web page W1 (e.g., an address such as a URL or URI). The search request may include a context from the content C1 of the web page W1. The context may include text located near the search area SA (e.g., within a few words, pixels, DOM nodes, etc. before and / or after the search area). The search request may include an amount (number) of related queries to return. That is, the browser may convey as part of the request to the server the number of related queries to provide in the response. The browser may send the search request to a server, e.g., a search server.

[0018] The search server receives a search request from the browser and determines a query for the contents of the search area. The search server may determine the query using conventional techniques (e.g., natural language processing, entity identification, etc.). In some implementations, the search server may use context, if provided, in determining the query. In some implementations, the search server may determine the query using a web page identifier. The query may include text, such as, for example, words, phrases, acronyms, etc. The text may include text identified within (the contents of) the search area. The text may include text identified using context. The text may include text using entity identification. The query may include an entity identifier. If the search area includes images, the query may include images. The search server may generate a search result page for the query. Thus, a query identified by the search server for a search area may be referred to as a searched query or a main query. A search result page is a web page generated by the search server in response to the query. A search result page includes multiple search results. A search result may be associated with an identifier of a resource deemed responsive to the query. Thus, a search result may represent a resource. A resource may be any content accessible via the Internet, e.g., a web page, a PDF file, an audio file, an image, a video file, a document, etc. A resource may be accessible via an identifier, such as a URL, a URI, etc. A search result may include a link to the resource, the link using the resource identifier. A search result may include text from the linked resource, e.g., a web page title, a snippet (text extracted from the content of the resource), etc. A search result may include an image from the linked resource. A search result may be rich answers, such as knowledge panels, short answers (e.g., definitions, answers provided by a third party application and triggered by a query that matches a particular type of query), etc.A search result page may contain other elements such as advertisements, "people also asked" short answers, interactive rich answers, links to refine queries, etc., as is known.

[0019] The search server may also determine related queries for the searched query. In some embodiments, the related queries may be generated based on the search area SA, i.e., the content of the search area. In some embodiments, the related queries may include queries that were considered for the searched query but were not selected as the searched query. That is, the related queries may be low-ranked queries that are considered as searched queries but were not selected as the searched query. For example, if the content of the search area includes references to ambiguous entities, the related queries may include the second entity when the first entity was selected as the searched (main) query. In some embodiments, the related queries may be queries that are frequently issued (e.g., as determined by statistical analysis) after the searched (main) query. In some embodiments, the related queries may be generated based on identifiers (e.g., URLs) of web pages associated with the search area SA. For example, in some embodiments, the related queries may include queries when the web pages are top-ranked resources. As another example, the related queries may include queries that are frequently issued before the user navigates to the web page. As another example, the identifier may be used to identify queries that have response documents (including the document identified by the identifier) ​​that share a clause.

[0020] Related queries may also be referred to as related search requests. Potential (or candidate) related queries may be generated using conventional techniques. The search server may select some of the potential related queries to provide as part of the response to the search request. The search server may rank the potential (candidate) queries to identify the selected related queries. If a certain amount of related queries is provided to the search server as part of the search request, the search server may select the top ranked related queries of that amount to return as part of the response to the search request. The search server may rank the related queries using conventional ranking factors. The search server may also rank the related queries using the position of the web page W1. The position of the web page is not a conventional ranking factor for related queries because the web page is not associated with the search engine query. Ranking factors include, for example, the semantic proximity of the suggestion to the highlighted text and the number of times the suggestion follows the highlighted text.

[0021] In some embodiments, the search server may use the length (in characters) of the related queries as a ranking factor. For example, if a related query is too long, it may be ranked lower because it takes up too much space on the client's display. Thus, the search system may prioritize shorter related search requests (shorter related queries) over longer related search requests (longer related queries). The search server may send a response to the search request back to the browser. The response may include the searched query, a search result page for the searched query, and at least one related search request (related query). In some embodiments, no more than the requested amount of related search queries is provided as part of the response to the search request.

[0022] In response to receiving the search request response, search result region 150 is rendered within browser 110 of FIG. 1B. Search result region 150 includes search request region 130. In some embodiments, search result region 150 overlays display region 120. In some embodiments, rendering search result region 150 reduces the size of display region 120. In either embodiment, in response to selection of search region SA of FIG. 1A, web page W1 is displayed (i.e., within display region 120) and search result region 150 is rendered within browser 110 of FIG. 1B. Thus, while both the results of search result region 150 and web page W1 are visible, rendering search result region 150 may reduce the amount of content of web page W1 visible within display region 120.

[0023] As shown in FIG. 1B, the search result area 150 may include a search request area 130. The search request area 130 includes search request indicators 135, labeled SR1′-SR3′ in FIG. 1B. Thus, the search request indicators SR1′-SR3′ may be collectively referred to as search request indicators 135. The search request indicators SR1′-SR3′ may represent at least some of the related queries (related search requests) provided in the response from the server (other related queries provided may be associated with the search request indicators that are not displayed in the search result area 150 but can be accessed by scrolling). The search request indicator 135 may be interacted with to request a search related to the search area SA. Thus, the search request indicator 135 is an operable user interface element. The operable user interface element may be interacted with by a user to perform a programmed operation. The operation performed by the search request indicator 135 may be, for example, sending a search request in the form of a query to a search server. Thus, one search request indicator can be associated (generated) with one of the related search requests provided by the server. In some embodiments, one of the search request indicators can be associated (generated) with the searched query (main query). The related search request (e.g., related query) can include a word (keyword), a phrase, and / or multiple words or phrases, such that, for example, interaction with the search request indicator requests a search for the word, phrase, etc. The related search request can be or include an image, such that, for example, interaction with the search request indicator for the related search request requests a search for the image. The related search request is provided by the search server as part of a response to a request to search the selected area SA.In some embodiments, the first search request, e.g., the search request issued in response to interaction with SR1', is a searched query (main query), and the second search request, e.g., the search request issued in response to interaction with SR2', is a related search request (related query) provided by the server. In some embodiments, the searched query is not represented (associated) by a search request indicator. In such an embodiment, the searched query may be represented in a query text area of ​​the search results area 150 (e.g., as described with respect to FIGS. 3A-3D), and the first search request, e.g., the search request issued in response to interaction with SR1', and the second search request are each for another related search request provided by the server.

[0024] In some embodiments, one or more of the search request indicators 135 may include text. In some embodiments, one or more of the search request indicators 135 may include an image. The search request indicators 135 may be or may include a keyword or keywords that can be selected to obtain additional content (e.g., additional search result pages). Thus, additional search results may be navigated through the search request indicators SR1'-SR3'. That is, the search request indicators SR1'-SR3' may be interacted with to provide additional search results (e.g., through different search result pages), allowing the user to navigate to different search result content (different search result pages) without navigating away from the search result area 150 or the web page W1.

[0025] In some embodiments, the search request indicators SR1'-SR3' may represent a subset of related queries displayed in response to a search request of the search domain. In some embodiments, the search request indicators SR1'-SR3' may be a ranked (e.g., highest ranked) subset of related queries displayed in response to a search request of the search domain. In some embodiments, one or more of the search request indicators SR1'-SR3' may be ranked such that the most important related searches (or a subset thereof) are rendered in the search request domain 130. The ranking is based on a ranking order determined by the server. In some embodiments, the searched queries represent the highest ranked searches of the search domain.

[0026] In some embodiments, although not shown in FIG. 1B , additional search request indicators 135 may be displayed in response to a search request in search area SA. The additional search request indicators 135 may be viewed by scrolling or otherwise navigating through search request area 130. For example, search request area 130 may include a carousel of search request indicators 135. In this manner, additional related search requests may be viewed within search request area 130. For example, in some embodiments, the additional search request indicators 135 may be viewed by scrolling left or right within search request area 130.

[0027] As shown in FIG. 1B, in response to rendering the search result region 150, the size (e.g., the visible area) of the display region 120 is reduced. That is, in response to the search result region 150 being displayed, the size of the visible portion of the display region 120 is reduced. In some embodiments, the search result region 150 is an overlay, e.g., appears on top of the display region 120. Thus, in some embodiments, the search result region 150 may overlap (e.g., partially overlap) the web page W1 without changing the scale of the web page W1. In some embodiments, the web page W1 may be re-layed out (e.g., scaled) to fit (e.g., suitable for display) in the display region 120. In some embodiments, the display region 120 shown in FIG. 1A may be divided into the display region 120 and the search result region 150 as shown in FIG. 1B. The combined area of ​​the display region 120 and the search result region 150 shown in FIG. 1B may be the same as the area of ​​the display region 120 shown in FIG. 1A. In some implementations, the combined area of ​​display area 120 and search results area 150 may be different (eg, smaller, larger) than the area of ​​display area 120.

[0028] In some implementations, any background or theme applied to the address bar area 114 may blend in (and be continuous with) the search results area 150. A continuous background is more difficult to mimic by a third party (e.g., the provider of web page W1) within the browser 110 application. Additionally, a continuous background or theme can be implemented as a security feature, allowing a user to distinguish between legitimate search results resulting from a search query and search results that may be inserted by a third party or the provider of the web page.

[0029] FIG. 1C shows content C2 (e.g., a search result web page) rendered in navigation area 140 within search result area 150. Content C2 may be rendered in navigation area 140 in response to an interaction (e.g., a user interaction) with search request indicator SR1′ of search request area 130. In this embodiment, navigation area 140 does not replace display area 120. Content C2 displayed in navigation area 140 is visible even while web page W1 (and content C1) is at least partially displayed in display area 120 in this embodiment. Search request area 130 with search request indicator 135 is disposed between navigation area 140 and display area 120. In some embodiments, content C2 is loaded without interaction with search request indicator SR1′. For example, if search request indicator SR1′ represents a searched query, the browser may load (preload, prerender) in navigation area 140 a search result page returned in response to a request to search the search area. In such an embodiment, the content C2 can be viewed without selection of the search request indicator SR1′. For example, the user can drag an upper portion of the search result region 150 toward the display region 120 to view at least a portion of the content C2. The content C2 can also be viewed by maximizing the search result region 150. Maximizing the search result region 150 can be performed, for example, by dragging an upper portion of the search result region 150 toward the display region 120. Maximizing the search result region 150 can also be performed, for example, in response to selection of one of the search request indicators 135. When the search result region 150 is in a maximized state, the search result region 150 occupies a larger area than the display region 120, but does not completely cover / overlap the display region 120.

[0030] The navigation area 140 can be used to utilize (e.g., search) search results for a currently selected search request (i.e., a related search request represented by a most recently selected one of the search request indicators 135). A searched query is considered a currently selected search request before any of the search request indicators 135 is selected. For example, in response to a first search request indicator being selected from the search request area 130, a first content may be rendered in the navigation area 140. In response to a second search request indicator being selected from the search request area 130, a second content may be rendered in the navigation area 140 instead of or in addition to the first content. Content may be navigated while the search results (e.g., the search request indicator SR1′) are maintained in the search request area 130.

[0031] 1C, in some embodiments, the search request indicator SR1' is not displayed in the search request area 130 because content C2 corresponding to the search request indicator SR1' is already displayed. Thus, the search request indicator SR1' associated with content already displayed in the navigation area 140 may not be included in the search request area 130. In some such embodiments, text (or an image) corresponding to the search request indicator SR1' may be shown in a query title area of ​​the search results area 150, as described with respect to FIG.

[0032] Although not shown in FIG. 1C, in some embodiments, interaction with (e.g., selection of) at least a portion (e.g., a link) of the content C2 while the search request area 130 is shown may cause the search request area 130 to close and a new browser tab to open. For example, selection of a link in the content C2 may open a resource (e.g., a web page, a file) associated with the link in a new tab in the browser. As another example, in response to selection of a link in the content C2, the display area 120 may be removed and the resource associated with the link may be expanded within the current tab (e.g., the entire display area 120 of the browser 110). This may cause the search results area 150 to close. As another example, selection of a link in the content C2 may further display a menu (e.g., a pop-up menu) including an option to open the resource associated with the link. In some embodiments, although not shown in FIG. 1C, interaction outside the search results area 150 may cause the search results area 150 to close.

[0033] FIG. 1D shows content C3 (e.g., content of a search result page) rendered in navigation area 140 in search result area 150 of browser 110. Content C3 is rendered in navigation area 140 in response to an interaction (e.g., user interaction) with search request indicator SR3′ in search request area 130. Navigation area 140 replaces content C2 in navigation area 140 in this embodiment. In this embodiment, content C3 displayed in display area 140 replaces content C2 displayed in navigation area 140. As shown in FIG. 1D, search request indicator 135 is shifted so that search request indicator SR3′ corresponding to content C3 is more centrally located in search request area 130. Also shown in FIG. 1D is search request indicator SR4′. This is because search request indicator SR3′ has been shifted. The search request indicator SR4' may have been visible via a scroll input (eg, a right-to-left swipe or drag) within the search request area 130 before the search request indicator SR3' was selected.

[0034] 1A-1D, in some embodiments, after search request region 130 and navigation region 140 are presented, a new web address may be entered into input address region 113 of address bar region 114. In response to the new web address field, web page W1 (or other content) in navigation region 140 may be replaced with another web page (not shown) while maintaining search request indicator 135 in search request region 130. That is, search request indicator 135 may be maintained while navigating within navigation region 140 or using a different web address in address bar region 114 of browser 110.

[0035] FIGURE 1E illustrates that the size of navigation area 140 can be changed (e.g., enlarged, reduced). In FIGURE 1E, the size of navigation area 140 is enlarged from the size of navigation area 140 shown in FIGURE 1D, for example. In some implementations, a handle (not shown) or other icon associated with or included in navigation area 140 can be used to pull or push navigation area 140 to change its size. For example, a handle can be selected and dragged to change the size of navigation area 140. Exemplary handles 132 are shown in at least FIGURES 2B and 2C.

[0036] In some embodiments, user interface elements (e.g., a "back" button, a "back" arrow) can be used to remove (e.g., clear, navigate elsewhere) content rendered in navigation region 140 (e.g., web page W2). In some embodiments, user interface elements can be used to remove (e.g., clear) search request region 130 and / or navigation region 140. In some embodiments, user interface elements can be used to navigate (e.g., go back) from a web page (e.g., web page W2), search request indicator 135, and / or search results region 150.

[0037] 2A-2C show alternative display implementations relating to the display area 120 and the search result area 150 (search request area 130 and navigation area 140). In some implementations, content C2 associated with the search request indicator SR1' is shown in response to the navigation area 140 being enlarged in size. For example, the search request indicators SR1'-SR3' may be rendered in the search request area 130 of FIG. 2B in response to selection of the search area SA of FIG. 2A. A handle 132 (represented by a line) associated with the search request area 130 may be selected and used to move (e.g., drag) the search request area 130 in an upward direction (shown in direction A) to cause (e.g., generate) the navigation area 140 to appear as shown in FIG. 2C. In some implementations, in response to the movement of the search request area 130, the navigation area 140 may be caused to appear and content C2 associated with the search request indicator SR1' (which is the first search request indicator) may be rendered. In some embodiments, content associated with at least one of the focused search request indicators 135 (e.g., the one centered within the search request area 130 (also referred to as the currently selected search request)) may be rendered within the navigation area 140 in response to movement of the search request area 130 (e.g., movement of the handle 132).

[0038] The location and / or shape of the search result region 150 (search request region 130 and / or associated navigation region 140) may be different than shown here. In some embodiments, the search request region 130 and / or associated navigation region 140 may be smaller in size than shown. In some embodiments, the search request region 130 and / or associated navigation region 140 may be included along different sides of the browser 110 (e.g., along the bottom, along the top, along the left side, and / or along the other). In some embodiments, the search request region 130 (and / or navigation region 140) may float above the display region 120 (e.g., may be rendered in an upper window), in which case the size of the display region 120 in FIG. 1A is not reduced to the area of ​​the display region 120 shown in FIG. 1B. In some embodiments, the search request region 130 may be another shape (e.g., circular) instead of square or rectangular.

[0039] As shown (e.g., FIG. 2C), the SR1'-SR3' search request indicators 135 are arranged horizontally within the search request area 130 and can be navigated along the horizontal direction. In some implementations, the search request indicators SR1'-SR3' can be positioned in different orientations (e.g., vertically) within the search request area 130.

[0040] 3A-3D show alternative display implementations relating to the display region 120 and the search results region 150 (search request region 130 and navigation region 140). In the example of FIG. 3A-3D, the search results region 150 includes a query text region 332. The query text region 332 corresponds to the currently selected search request, i.e., the focused search request. The focused search request corresponds to the searched query when the search results region 150 is first displayed (rendered). The focused search request can change based on an interaction with the search request indicator 135. The search results page currently displayed in the navigation region 140 corresponds to the focused search request. In the example of FIG. 3B, the search request indicator SR1′ corresponds to the searched query, and thus the query text region 332 includes the text for the searched query. In the example of FIG. 3B, when the user resizes the search results region 150, e.g., as described for FIG. 2C, the content of the navigation region 140 becomes the search results page received for the searched query.

[0041] In some embodiments, the display area of ​​the query text area 332 may include an image related to the search request in focus. In some embodiments, the search server transmits an image for the searched query in response to a request to search the search area. The image may be small (sized to occupy an area similar to a few lines of text in the search results area 150) and may be displayed with the text in the query text area 332 above the search request area 130. In some embodiments, the image, if provided, is removed from the query text area 332 when the search results area 150 is maximized to free up display area for additional content to be displayed in the navigation area 140. In some embodiments, the text in the query text area 332 corresponds to the related search request / searched query.

[0042] FIG. 3C illustrates changes to the search results region 150 in response to an interaction 305 with the search request indicator SR3′. As shown, interaction with (e.g., selection of) the search request indicator SR3′ can change the size of the search results region 150. Thus, for example, the search results region 150 may be maximized or in a maximized state in response to selection of the search request indicator SR3′. Furthermore, when the search request indicator SR3′ is selected, the related search request associated with SR3′ becomes the currently selected search request, i.e., the search request in focus. Thus, the content of the query text region 332 is changed to correspond to the related search request associated with the search request indicator SR3′. In some embodiments, when the search results region 150 is in a maximized state, a control 337 may be displayed. Selection of the control 337 may cause the browser to open a search results page for the search request in focus in a new tab or new browser window. In some embodiments, when the search results region 150 is maximized, the appearance of the display region 120 may be changed. For example, as shown in FIG. 3C, display area 120 may be shaded. In addition to maximizing search results area 150, selection of SR3′ may cause a search request to be submitted to a search server. The search request is a query represented by the related search request corresponding to SR3′. Thus, the search server may return a search results page corresponding to SR3′ and display the search results page (e.g., content C3) in navigation area 140.

[0043] In the example of FIG. 3C, the user may reduce the size of the search results region 150 by, for example, interacting with the handle 132. For example, the user may drag the handle 132 toward the navigation region 140, for example, in direction B of FIG. 3C. In some implementations, when the handle 132 reaches a minimize threshold 338, for example, represented by a dashed line in FIG. 3C, the browser may automatically change the currently selected search request, i.e., the search request in focus, to the searched query. Thus, for example, when the handle 132 reaches the minimize threshold 338, the browser may change the query text region 332 to the text for the searched query and may change the content of the navigation region 140 to a search results page for the searched query, as shown in FIG. 3D. The minimize threshold 338 may be a screen coordinate, for example, a y-coordinate or an x-coordinate, which is between the position of the handle 132 when the search results region 150 is in a maximized state and the position of the handle 132 when the search results region 150 is in a minimized state. The minimization threshold 338 may be closer to the position of the handle 132 when the search results region 150 is in a minimized state than the position of the handle 132 when the search results region 150 is in a maximized state. When the search results region 150 is in a minimized state, the search results region 150 may display only the search request region 130 and the query text region 332 (in embodiments that include it). That is, when the search results region 150 is in a minimized state, the navigation region 140 is not visible or is only slightly visible. Thus, for example, the search results region 150 of Figures 3B and 3D shows the search results region 150 in a minimized state, and Figure 3C shows the search results region 150 in a maximized state.

[0044] FIG. 4 illustrates a system 400 including a computing system 402 and a search server 440 configured to implement the concepts and various embodiments shown and described herein. As illustrated in FIG. 4, the computing system 402 is configured to communicate with the search server 440 and / or a web page provider 410 (e.g., a web server) over a network 450. The computing system 402 includes at least a browser manager 420 and a search result manager 423. In some embodiments, the browser manager 420 is configured to manage content, such as web page content, provided by the web page provider 410 (e.g., also referred to as a web server). In some embodiments, the browser manager 420 is configured to operate as one of several applications 428 executed via an operating system (O / S) 429. The browser manager 420 can be configured to implement major portions of a user interface, search results, windows, and / or the like, as described in connection with the embodiments described herein.

[0045] 4, computing system 402 includes several hardware components, including a communications module 461, one or more cameras 462, memory 463, a central processing unit (CPU) and graphics processing unit (GPU) 464, one or more input devices 467, and one or more output devices 468. The hardware components may be used to facilitate the operation of browser manager 420, search result manager 423, and / or other components of computing system 402.

[0046] Browser manager 420 includes a user interface (UI) generator 421 configured to generate and / or manage various user interface elements of a browser, such as browser 110 shown and described herein. For example, UI generator 421 may generate UI elements including various windows of browser 110. Such various windows may be, for example, at least display area 120, search results area 150 (including search request area 130), navigation area 140, and / or query text area 332 shown in Figures 1A-1C and other figures.

[0047] Browser manager 420 includes tab manager 422 configured to generate and / or manage various tabs of a browser, such as browser 110. Browser manager 420 may be configured to open new tabs in response to, among other things, a user's interaction with a link in a search results page displayed in a navigation area (e.g., navigation area 140) of a search results area (e.g., search results area 150). Browser manager 420 may be configured to open new tabs in response to, among other things, a user's interaction with a control (e.g., control 337 of FIG. 3C) of search results area 150. In some implementations, the control may be displayed when the search results area is displayed in a maximized state, as described herein.

[0048] The browser manager 420 includes a search results manager 423 configured to generate and / or manage the rendering of content (e.g., content in the search results region 150 including the search request indicator, content in the navigation region, content in the query text region 332, etc.) (shown in at least FIGS. 1B, 1C, 3B, 3C, and other figures). The browser manager 420 includes a display area manager 424 configured to generate and / or manage the rendering of content associated with a web page W1 in the display area 120 (shown in FIG. 1B and other figures). The content of the web page W1 can be provided to the computing system 402 by a web page provider 410.

[0049] 4, session data 427, which may be stored in memory 463 (not shown), may be managed as or by one of applications 428. Session data 427 may include data related to one or more browser sessions. Application information 426 may include information related to various applications that may run within and / or be executed by O / S 429.

[0050] The search result manager 423 may also be configured to manage one or more elements selected for searching, e.g., search area SA in FIG. 1A and other figures. The search result manager 423 may trigger one or more search requests, e.g., generate a search request for the selected search area and send the request to the search server 440. The search result manager 423 may include an area detector 432 that may detect one or more areas selected for searching (e.g., search area SA shown in FIG. 1B and other figures). The search result manager 423 may also include a capture manager 431 that may manage the content of the search request, e.g., package the content of the search area, a web page identifier, a context for the search area, and / or a number of related searches to be returned to a format required by the search suggestion generator 442 of the search server 440. The selection of one or more areas for searching may be triggered by one or more input devices 467 (e.g., a mouse, a gesture, etc.) and communicated to the search result manager 423 (and area detector 432). The search results manager 423 can be configured to implement the process described with respect to Figures 5A and 5B.

[0051] 4, the communication module 461 can be configured to facilitate communication with the web page provider 410 and / or the search server 440 over the network 450 via one or more communication protocols. The camera 462 can be used to capture one or more images, the memory 463 can be used to store information associated with the browser manager 420 and / or the search result manager 423, and the CPU / GPU 464 can be used to process the information and / or images associated with the browser manager 420 and / or the search result manager 423. The computing system 402 further includes one or more output devices 468, such as a communication port, a speaker, a display, and / or the like. The functionality described herein can be implemented based on one or more policies 465 and / or preferences 466 (e.g., the number of relevant search requests returned) stored in the memory 463.

[0052] FIG. 4 illustrates some aspects of the search server 440. For example, the search server 440 includes one or more processors 446 and one or more memory devices 448. The search server 440 includes a search suggestion generator 442 configured to receive a search request for a search space from the computing system 402. A search request for a search space differs from a normal search query because the query is not known in advance. The search suggestion generator 442 is configured to determine a query searched from the search space (optionally using a context provided with the request and / or the content of a web page identified in the request to search the search space). The search suggestion generator 442 is also configured to identify related candidate queries for the search space, rank the related candidate queries, and select related candidate queries for inclusion in a response to the request. The search suggestion generator 442 may communicate with a search engine 444 of the search server 440 (or a search engine 444 accessible to the search server 440). The search engine 444 can be used to provide a search result page for the query. For example, once the search suggestion generator 442 determines a searched query for a search domain, the search suggestion generator 442 may send the searched query to the search engine 444, which may provide a search result page for the searched query. The search result page typically includes multiple search results, each of which represents a resource that may be responsive to the query. The search result page may also include rich results, such as short answers and / or knowledge panels. The search result page may also include advertisements or sponsored results. The search suggestion generator 442 may be configured to implement the process described with respect to FIG. 6.

[0053] 5A and 5B are a flow chart illustrating a method 500 for implementing at least some of the concepts described herein in various figures. Many elements of the method 500 may be implemented by at least the components illustrated in FIG. 4. In particular, the method 500 may be performed by a browser (e.g., browser manager 420) of the computing system 402. At step 502, the system may display a web page within a display area of ​​the browser. At step 504, the system may receive a selection of an area of ​​the web page content (e.g., search area SA of FIG. 1A). In response to the selection of a search area contained in the web page (506), the system may request a search of the content of the search area at step 508. The request may include the content of the search area, an identifier of the web page, and context for the search area from the web page. In some implementations, the request may include the number (i.e., amount) of related queries to be returned. The system may provide this request to search the search area to a server (e.g., a search server). The search server may provide a response to the search request. The response may include the searched query, a search result page for the searched query, and at least one related search request. The related search request(s) are additional queries (related queries) that a user can submit from a search result interface (e.g., search result area 150 in FIG. 1B and other figures) without navigating away from the web page.

[0054] At step 510, the system receives the response, and at step 512, the system causes a first search request indicator and a second search request indicator to be displayed outside the display area and within the search results area in the browser. In some embodiments, the first search request indicator can represent the searched query and the second search request indicator can represent a related search request. In some embodiments, for example, if two or more related search requests are provided in the response, the first search result indicator can represent one of the related search requests and the second search result indicator can represent another of the related search requests. At step 514, the system receives a selection of the first search request indicator. At step 516, the system causes content for the first search request indicator to be displayed within the navigation area of ​​the search results area in response to the selection of the first search request indicator. In embodiments in which the searched query is represented by the first search request indicator, the content is a search results page received in the response. In such embodiments, displaying the content may include automatically maximizing the size of the search results area (e.g., displaying the search results area in a maximized state), such that at least a portion of the search results page for the searched query is visible. In an embodiment in which the first search request indicator represents a related query, displaying the content may include sending the related query to a search server, receiving a search results page for the related query, and displaying the search results page for the related query.

[0055] Once the system renders the search results region, the system may be configured to respond to one or more different inputs associated with the search results region. For example, in step 550, the system may receive an interaction (such as a selection, tap, click, etc.) outside the search results region. In response to receiving this interaction, in step 552, the search results region may be closed, i.e., removed from the display area of ​​the browser. As another example, in step 530, the system may receive a selection of a link in the navigation region (e.g., a selection of a link from a search results page currently displayed in the navigation region of the search results region). Or, in step 530, the system may receive a selection of a control in the search results region configured to open a search results page currently displayed in the navigation region in a new tab. In response to receiving the selection of the link or control, in step 534, the system may create a new tab and display the contents of the navigation region (the search results page for the search request in focus) in the new tab.

[0056] As another example, in step 540, the system may receive an interaction with a handle of the search results area. The interaction may be a drag of the handle, which changes the size of the search results area displayed in the browser. The system may monitor the position (coordinates) of the handle during the drag and may determine in step 542 whether the coordinates meet a minimization threshold (e.g., minimization threshold 338 of FIG. 3C). In response to determining that the coordinates of the handle meet the minimization threshold, and if the content in the navigation area is not content from the search results for the searched query, in step 544, the system may replace the content in the navigation area with content from a search results page (e.g., as shown in FIG. 3D) for the searched query.

[0057] As another example, in step 520, the system may receive an interaction for a selection of a particular search request indicator. The particular search request indicator may be any of the search request indicators displayed in the search results area. In response to receiving the selection (522), the system may send a query corresponding to the particular search request indicator to a search server in step 524. In step 526, the system receives a search results page for the query in response to the request. In step 528, the system causes content from the search results page for the query to be displayed within the navigation area of ​​the search results area. And the query associated with the particular search request indicator may be considered a current search request or a search request in focus.

[0058] FIG. 6 is a flow chart illustrating a method 600 for implementing at least some of the concepts described herein in the various figures. Many elements of the method 600 may be implemented by at least the components illustrated in FIG. 4. In particular, the method 600 may be performed by a server system (e.g., search server 440). At step 602, the system may receive a request to search a selected search area from a browser executing on a client device. The request includes the selected search area and an identifier of a web page displayed by the browser. The request may include a context for the search area. The request may include an amount of related search requests (related queries) to be returned. In the request, the selected search area and the context are content from the web page identified in the request.

[0059] In step 604, the system may determine a query for the selected search area. This query may be referred to as a searched query. In determining the searched query, the system may identify several candidate queries for the search area and select the top queries as the searched queries. The system may use known or later developed techniques to select the searched queries. The system may obtain a search result page for the searched query in step 606. In step 608, the system may determine one or more related search requests for the search area. These related search queries may be referred to as related candidate queries. The system may rank the related candidate queries in step 610. The ranking may depend on several factors, including the identifier of the web page. The ranking may also or instead use the length of the related candidate queries as a ranking factor. As part of step 610, the system may select the highest ranked related candidate queries. The number of selected candidate queries (related search requests) may be based on the amount received with the request to search the search area. In step 612, the system provides the query, the selected related search request(s), and a search results page for the query to the browser in response to the request.

[0060] 7 illustrates an example of a general purpose computing device 2000 and a general purpose mobile computing device 2050 that can be used with the techniques described herein. The computing device 2000 is intended to represent various types of digital computers, such as laptops, desktops, tablets, workstations, personal digital assistants, televisions, servers, blade servers, mainframes, and other suitable computing devices. The computing device 2050 is intended to represent various types of mobile devices, such as personal digital assistants, mobile phones, smartphones, and other similar computing devices. The components illustrated here, their connections and relationships, and their functions are intended to be exemplary only and are not intended to limit the implementation of the embodiments described and / or claimed herein.

[0061] The computing device 2000 includes a processor 2002, a memory 2004, a storage device 2006, a high-speed controller 2008 that connects to the memory 2004 and a high-speed expansion port 2010, and a low-speed controller 2012 that connects to a low-speed expansion port 2014 and the storage device 2006. The processor 2002 may be a semiconductor-based processor. The memory 2004 may be a semiconductor-based memory. Each of the components 2002, 2004, 2006, 2008, 2010, and 2012 are interconnected using various buses and may be mounted on a common motherboard or may be mounted in other manners as desired. The processor 2002 may process instructions for execution within the computing device 2000, including instructions stored in the memory 2004 or the storage device 2006, to display graphical information of a GUI on an external input / output device, such as a display 2016 connected to the high-speed interface 2008. In other embodiments, multiple processors and / or multiple buses may be used as desired, along with multiple memories and types of memories. Also, multiple computing devices 2000 may be connected, with each device performing some of the required operations (eg, as a bank of servers, a group of blade servers, or a multi-processor system).

[0062] The memory 2004 stores information within the computing device 2000. In one embodiment, the memory 2004 is a volatile memory unit(s). In another embodiment, the memory 2004 is a non-volatile memory unit(s). The memory 2004 may also be another form of computer-readable medium, such as a magnetic disk or an optical disk.

[0063] The storage device 2006 can provide mass storage for the computing device 2000. In one embodiment, the storage device 2006 can be or include a computer-readable medium. The computer-readable medium can be, for example, a floppy disk device, a hard disk device, an optical disk device, or an array of devices including a tape device, a flash memory or other similar solid-state memory device, or a storage area network or other configuration of devices. A computer program product can be tangibly embodied in an information carrier. The computer program product can also include instructions that, when executed, perform one or more methods as described above. The information carrier is a computer-readable medium or machine-readable medium, such as the memory 2004, the storage device 2006, or the memory of the processor 2002.

[0064] The high-speed controller 2008 manages the more bandwidth-intensive operations of the computing device 2000, and the low-speed controller 2012 manages the less bandwidth-intensive operations. Such allocation of functions is merely an example. In one embodiment, the high-speed controller 2008 is connected to the memory 2004, the display 2016 (e.g., via a graphics processor or accelerator), and the high-speed expansion port 2010. The high-speed expansion port 2010 may accept various expansion cards (not shown). In this embodiment, the low-speed controller 2012 is connected to the storage device 2006 and the low-speed expansion port 2014. The low-speed expansion port may include various communication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet) and may be connected to one or more input / output devices (e.g., a keyboard, a pointing device, a scanner, or a network device such as a switch or a router) via a network adapter or the like.

[0065] The computing device 2000 may be implemented in many different forms, as shown in the figure. For example, it may be implemented as a standard server 2020, or multiple times in a group of such servers. It may also be implemented as part of a rack server system 2024. It may also be implemented in a personal computer, such as a laptop computer 2022. Alternatively, the components of the computing device 2000 may be combined with other components in a mobile device (not shown), such as device 2050. Each such device may include one or more of the computing devices 2000, 2050, and the overall system may be made up of multiple computing devices 2000, 2050 in communication with each other.

[0066] Computing device 2050 includes components such as a processor 2052, memory 2064, input / output devices such as a display 2054, a communication interface 2066, and a transceiver 2068, among other components. Device 2050 may also be provided with a storage device, such as a microdrive or other device, to provide additional storage. Each of components 2052, 2064, 2054, 2066, and 2068 are interconnected using various buses, and some of these components may be mounted on a common motherboard or in other manners as desired.

[0067] The processor 2052 can execute instructions within the computing device 2050, including instructions stored in the memory 2064. The processor can be implemented as a chipset of chips including individual analog and digital processors. The processor can be provided for coordination of other components of the device 2050, such as control of a user interface, applications executed by the device 2050, and wireless communications by the device 2050.

[0068] The processor 2052 may communicate with a user via a display interface 2056 and a control interface 2058 connected to a display 2054. The display 2054 may be, for example, a TFT LCD (thin film transistor liquid crystal display) or an OLED (organic light emitting diode) display, or other suitable display technology. The display interface 2056 may include suitable circuitry for driving the display 2054 to present graphical and other information to the user. The control interface 2058 may receive and convert commands from the user for transmission to the processor 2052. Additionally, an external interface 2062 may be provided in communication with the processor 2052, thereby enabling short-range communication between the device 2050 and other devices. The external interface 2062 may, for example, enable wired communication in some embodiments and wireless communication in other embodiments, and multiple interfaces may also be used.

[0069] The memory 2064 stores information within the computing device 2050. The memory 2064 can be implemented as one or more of one or more computer readable media, one or more volatile memory units, or one or more non-volatile memory units. An expansion memory 2074 may also be provided and connected to the device 2050 via an expansion interface 2072, which may include, for example, a SIMM (Single In-Line Memory Module) card interface. Such expansion memory 2074 may provide additional storage space for the device 2050 or may store applications or other information of the device 2050. In particular, the expansion memory 2074 may include instructions for performing or supplementing the above processes and may also include secure information. Thus, for example, the expansion memory 2074 may be provided as a security module of the device 2050 and may be programmed with instructions that enable secure use of the device 2050. Furthermore, secure applications may be provided via the SIMM card, along with additional information such as identification information that is placed on the SIMM card in an unhackable manner.

[0070] The memory may include, for example, flash memory and / or NVRAM memory, as described below. In one embodiment, a computer program product may be tangibly embodied in an information carrier. The computer program product includes instructions that, when executed, perform one or more methods, such as those described above. The information carrier may be a computer-readable or machine-readable medium, such as memory 2064, expansion memory 2074, or memory of processor 2052, and may be received, for example, via transceiver 2068 or external interface 2062.

[0071] The device 2050 may communicate wirelessly via a communication interface 2066, which may include digital signal processing circuitry if necessary. The communication interface 2066 may enable communication in various modes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Such communication may occur, for example, via a transceiver 2068. Additionally, short-range communication may occur using Bluetooth, WiFi, or other such transceivers (not shown). Additionally, a GPS (Global Positioning System) receiver module 2070 may provide the device 2050 with additional wireless data related to navigation and position, which may be used as needed by applications executing on the device 2050.

[0072] Device 2050 can also perform voice communications using an audio codec 2060, which can receive voice information from a user and convert it into usable digital information. The audio codec 2060 can likewise generate sounds that are heard by the user, such as through a speaker in a handset of device 2050. Such sounds can include voice telephone calls, recorded sounds (e.g., voice messages, music files, etc.), and sounds generated by applications running on device 2050.

[0073] The computing device 2050 may be implemented in many different forms, as shown in the figure, for example, it may be implemented as a mobile phone 2080, or it may be implemented as part of a smartphone 2082, a tablet, glasses, a smartwatch, a personal digital assistant, or other similar mobile device.

[0074] Various implementations of the systems and techniques described herein may be realized in digital electronic circuitry, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementation in one or more computer programs executable and / or interpretable by a programmable system including at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from the storage system and to transmit data and instructions to the storage system, at least one input device, and at least one output device.

[0075] These computer programs (also known as programs, software, software applications, or code) contain machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., magnetic disks, optical disks, memory, programmable logic circuits (PLDs)) used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium that receives the machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0076] To provide for interaction with a user, the systems and techniques described herein can be implemented on 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 pointing device (e.g., a mouse or trackball) by which the user can provide input to the computer. Other types of devices may also be provided to enable interaction with the user, for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user may be received in any form, including acoustic, spoken language, or tactile input.

[0077] The systems and techniques described herein can be implemented in a computing system that includes a back-end component (e.g., as a data server), or includes a middleware component (e.g., an application server), or includes a front-end component (e.g., a client computer having a graphical user interface or web browser through which a user can interact with an implementation of the systems and techniques described herein), or includes any combination of 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 communications network). Examples of communications networks include a local area network ("LAN"), a wide area network ("WAN"), and the Internet.

[0078] A computing system may include clients and servers. Clients and servers 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.

[0079] Several embodiments have been described. However, it will be understood that various modifications can be made without departing from the spirit and scope of the disclosed embodiments.

[0080] Additionally, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desired results. Additionally, other steps may be provided or certain steps may be removed from the illustrated flows, and additional components may be added to or removed from the illustrated systems.

Claims

1. 1. A method comprising: in response to a selection of a search area included in a web page displayed within the browser display area; requesting a search on the contents of said search area; receiving a searched query, a search result page for the searched query, and a related search request; and displaying a first search request indicator and a second search request indicator within a search results area outside the display area and within the browser; receiving a selection of the first search request indicator; and in response to the selection of the first search request indicator, displaying content for the first search request indicator within a navigation area of ​​the search results area; A method comprising:

2. the request for the search includes an identifier for the content of the search area and the web page; The method of claim 1 , wherein the related search requests are selected based at least in part on the identifier of the web page.

3. the first search request indicator represents the searched query; The method of claim 1 or 2, wherein the content for the first search request indicator is content from the search result page.

4. The method of claim 3 , wherein displaying the content for the first search request indicator includes maximizing the search results area to display the navigation area.

5. The method of claim 4 , wherein the search result area, when maximized, occupies an area larger than the display area.

6. The related search request is a first related search request, a second related search request is received along with the first related search request, the first search request indicator represents the second related search request, and the method further includes, in response to a selection of the first search request indicator: requesting a search for the second related search request; receiving a second search result page for the second related search request; and The method of claim 1 or 2, further comprising: displaying second content within the navigation area, the second content being content from the second search results page.

7. The content for the first search request indicator is a first content, and the method further comprises: receiving a selection of the second search request indicator; and in response to receiving the selection of the second search request indicator, requesting a search for said related search queries; receiving a second search result page for the related search request; and 2. The method of claim 1, further comprising: displaying second content in the navigation area, the second content being content from the second search results page, the second content replacing the first content in the navigation area.

8. The search results area includes a handle configured to resize the navigation area, and the method further comprises: receiving an interaction with the handle to change the size of the navigation area displayed in the search results area; determining when the coordinates of the handle reach a minimization threshold; and 8. The method of claim 7, further comprising: in response to determining that the coordinates have reached the minimization threshold, causing the navigation area to display the first content, wherein the first content replaces the second content in the navigation area.

9. The method of claim 8 , further comprising resizing the navigation area in response to an interaction with the navigation area.

10. the search result area further includes a query text area; 2. A method according to any one of the preceding claims, wherein the query text area displays text related to the content displayed in the navigation area.

11. receiving a selection of a link within the content displayed in the navigation area; and creating a new browser tab from said content; 2. The method of any one of the preceding claims, further comprising:

12. the search result area includes a search request area disposed between a query text area and the navigation area; 2. A method according to any one of the preceding claims, wherein the first search request indicator and the second search request indicator are located in the search request area.

13. In response to the selection of the search area, determining whether the search region is text that is not operational text; performing the requesting a search in response to determining that the search region is text that is not operational text; and in response to determining that the search region is not text or determining that the text is actionable text, displaying a pop-up menu including operations for the actionable text; 2. The method of any one of the preceding claims, further comprising:

14. 2. A method according to any one of the preceding claims, wherein the searched query is a query generated using the content of the search area and provided to a search engine for generating the search results page.

15. 2. A method according to any one of the preceding claims, wherein the related search requests are queries that are generated using the content of the search space different from the searched query.

16. At least one processor; a memory for storing instructions, The instructions, when executed by the at least one processor, cause the computing device to perform operations, including: in response to a selection of a search area included in a web page displayed within the browser display area; requesting a search on the contents of said search area; receiving a searched query, a search result page for the searched query, and a related search request; and displaying a first search request indicator and a second search request indicator within a search results area outside the display area and within the browser; receiving a selection of the first search request indicator; and in response to the selection of the first search request indicator, displaying content for the first search request indicator within a navigation area of ​​the search results area; a computing device comprising:

17. the first search request indicator represents the searched query; The computing device of claim 16 , wherein the content for the first search request indicator is content from the search results page.

18. 20. The computing device of claim 17, wherein causing the content to be displayed for the first search request indicator includes maximizing the search results region to display the navigation region.

19. The computing device of claim 18 , wherein the search results area, when maximized, occupies an area larger than the display area.

20. The related search request is a first related search request, a second related search request is received along with the first related search request, the first search request indicator represents the second related search request, and the operation further comprises, in response to a selection of the first search request indicator: requesting a search for the second related search request; receiving a second search result page for the second related search request; and 20. The computing device of claim 16, further comprising: displaying second content within the navigation area, the second content being content from the second search results page.

21. 1. A method comprising: receiving a request from a browser executing on a client device to search for content for a selected search area, the request including the content for the selected search area and an identifier of a web page displayed by the browser, the selected search area being content contained in the web page; determining a query for the selected search space; using the identifier of the web page to determine relevant search queries for the selected search area; obtaining a search result page for said query; and providing the query, the related search requests, and the search result page in response to the request; A method comprising:

22. 22. The method of claim 21, as part of determining the related search requests, the method further comprises: prioritizing shorter related search requests over longer related search requests.

23. 1. A method comprising: receiving a search area of ​​a web page to be displayed within a display area of ​​a browser, the browser comprising: requesting a search on the contents of said search area; receiving a response to the request including at least two related search requests; and displaying a first search request indicator and a second search request indicator within the search result area; and the method further comprises: receiving a selection of the first search request indicator; and in response to a selection of the first search request indicator, displaying content for the first search request indicator within a navigation area of ​​the search results area; A method comprising:

Images