HK1216788B - Enhanced search results associated with a modular search object framework - Google Patents

Description

Enhanced search results associated with the modular search object framework

Technical Field

The present application relates to the presentation of entity-based content (eg, entity search results and graphical user interfaces) and modular search objects, a framework for supporting entity-based content and modular search objects, and user interaction therewith.

Background Art

It is common for users to enter a query containing one or more keywords and perform a search on a web page. Typically, the search results are provided on a results page that lists links, where the links have titles and some description of the linked content. In many cases, the results list is accompanied by one or more sponsored results (i.e., search ads).

Users are increasingly searching on mobile devices such as smartphones or tablets. Conventional techniques for providing result lists are not well adapted to the specific limitations of mobile devices. Consequently, there are a number of unresolved engineering problems to provide users with search results that are well adapted to mobile devices or mobile device interfaces to other devices (e.g., televisions).

Summary of the Invention

Provided herein are novel systems, methods, and circuits for presenting entity-based content (e.g., entity search results and graphical user interfaces), modular search objects, frameworks for supporting entity-based content and modular search objects, and user interactions therewith. Entity-based content can be monetized. Entity search results are search results based on (e.g., solely based on) an entity (e.g., a specific person, place, or thing). Entity search results or other forms of entity-based content delivery (such as an entity graphical user interface (e.g., an entity tray)) can be distinguished from non-entity content in the following manner: in a system (such as a content provider's system), content for a particular entity is delivered via a single root object consisting of one or more child objects. For non-entity search results, the result is not necessarily associated with a root object for a particular entity; there may be many root search results for a particular entity. Additionally, in a non-entity-based system, there may be multiple root graphical user interfaces (GUIs), such as multiple root web pages, for a single entity. In an entity-based content system, each entity has a root object. In an example entity-based system, each entity may have only one web page. For example, for Tom Cruze actor (Actor), in such an entity-based system, there is only one root object for Tom Cruze actor (for example, one root webpage for Tom Cruze actor). However, in a non-entity-based content system, there may be many root objects for Tom Cruze. For example, for a non-entity content delivery system, there may be many different root webpages and websites for Tom Cruze actor. For an entity-based content delivery system, there is only one root object. In the case where each entity in the framework has only one root object, there may be many entity child objects under the entity root object. WIKIPEDIA can be regarded as a system based on entity content delivery. The framework described in this article attempts to remove the ambiguity of entities, which WIKIPEDIA may have experienced. In the example of the framework, entities in the system that may cause ambiguity can be denied entry into the system.

In the framework, the display of aggregated search results can be dynamic and interactive. Furthermore, in the framework, entity search results (even search suggestions and non-entity search results) can attempt to match the searcher's content (e.g., based on the search query entered by the searcher). Furthermore, the user or group profile associated with the searcher can be used to determine user intent. The display of the included search results on multiple interactive objects can include links and other visual information attached to the interactive objects. This information can include a summary of the entity and more. Information about such objects can include detailed information about the entity and links to related entities. This information can be provided via a root graphical user interface (GUI) object for each entity and its child GUI objects, such as through an entity tray and cards within the tray. The entity root GUI object and each child GUI object can include various information about the entity and entities related to it. For example, a tray can be displayed for a particular actor (e.g., tray 201a for actor Tom Cruze), and a child GUI (e.g., card) of the tray can display a map to the actor's restaurants. The specific restaurant location of the restaurant owned by the actor may even be a "place" entity in the frame, and restaurants generally may be a "thing" entity in the frame. In one example, the search results provided by the frame may appear in the form of a list that appears in the form of a stack of cards on a display device.

In examples where the frame presents a stack of card search results or any other two- or three-dimensional form for a list of search results, such results can be graphically enhanced (e.g., photographically enhanced). Additionally, these frame results can be merged with search suggestions in a list. Additionally, such a list can be interactive in that the individual objects in the list can be moved, expanded, shrunk, minimized, or even hidden by the user interacting with the list. Entity search results (as opposed to non-entity search results and/or search suggestions) in the list provided by the frame can be emphasized, for example, through graphical enhancement. The enhancement can even be tactile or through audio output or some other form of perceptible output.

Additionally or alternatively, search results and other GUIs of the framework can organize results and information based on user intent. In an example, user intent can be predicted from an input search query. In such an example, the corresponding search results can be listed in an order that reflects the information that the framework predicted the user intended to receive when entering the search query. In addition, user intent can be reflected in the layout and format of the entity GUI and sub-GUIs displayed to the user. In addition, information within the entity GUI can be arranged and formatted based on the predicted user intent.

BRIEF DESCRIPTION OF THE DRAWINGS

The systems and methods may be better understood with reference to the accompanying drawings and description. Non-limiting and non-exhaustive examples are described with reference to the following figures. The components in the figures are not necessarily drawn to scale; emphasis is instead placed on illustrating the principles of the system. In the figures, like reference numerals designate corresponding parts throughout the different views.

1 illustrates a block diagram of an example information system including example devices of a network that can provide aspects of a modular search object framework.

2a illustrates entity and non-entity search result objects and search suggestion objects displayed on an example page view rendered by an example client application, such as a mobile web browser. The example client application can be executed on any client device shown in FIG.

Figure 2b illustrates an example expanded displayed entity search result object associated with a person on the page view rendered by the example client application of Figure 2a. Specifically, the depiction of the expanded object includes an example summary portion rendered by the example summary circuitry of the modular search object framework.

Figure 3a illustrates the example expanded displayed entity search result object of Figure 2b. Specifically, the depiction of the expanded object includes multiple interactive parts rendered by corresponding circuitry of the modular search object framework.

3b illustrates the example expanded displayed entity search result object of FIG. 2b, overlaid with an example image-based search result portion and an example web-based search result portion overlaid by corresponding circuitry of the modular search object framework.

4a illustrates the example expanded displayed entity search result object of FIG. 2b, overlaid with an exemplary image-based search result portion rendered by corresponding circuitry of the modular search object framework.

4b illustrates the example expanded displayed entity search result object of FIG. 2b, overlaid with an example map-based search result portion rendered by corresponding circuitry of the modular search object framework.

FIG5 a illustrates example displayed entity and non-entity search result objects on an example page view rendered by a client application.

FIG5 b illustrates an example displayed and partially expanded entity search result object on an example page view rendered by a client application.

6a illustrates an example expanded displayed entity search result object on an example page view rendered by a client application. Specifically, the depiction of the expanded object includes an example summary portion rendered by an example summary circuit of the modular search object framework.

Figure 6b shows an example expanded displayed entity search result object on an example page view rendered by a client application. Specifically, the depiction of the expanded object includes an example summary portion and an example predicted answer portion rendered by corresponding circuitry of the modular search object framework.

7a illustrates an example expanded displayed entity search result object associated with a place. Specifically, the depiction of the expanded object associated with the place includes a plurality of interactive portions rendered by corresponding circuitry of the modular search object framework.

7b illustrates an example expanded displayed entity search result object associated with a thing. Specifically, the depiction of the expanded object associated with the thing includes multiple interactive parts rendered by corresponding circuitry of the modular search object framework.

FIG8 a illustrates example displayed entity and non-entity search result objects and search suggestion objects on an example page view rendered by an example client application, such as a web browser. Such a client application can be executed on any client device shown in FIG1 . FIG8 a also illustrates an example expanded displayed entity search result object.

Figure 8b shows an example expanded displayed search suggestion object associated with an example suggested search term on an example page view rendered by the client application of Figure 8a. Specifically, the depiction of the expanded object includes a search result portion based on an example web page rendered by corresponding circuitry of the modular search object framework.

FIG9 illustrates a block diagram of example circuitry for a server of an example system that can provide aspects of a modular search object framework, such as the modular search framework server 116 shown in FIG1 .

10 illustrates a block diagram of example circuitry for a client device of an example system that can provide aspects of a module search object framework, such as any client device of the system shown in FIG. 1 .

11a illustrates example operations of example circuitry of an example system that can provide aspects of a module search object framework. In one example, the operations can be performed by circuitry of a client device, such as any client device of the system shown in FIG.

11 b illustrates example operations of example circuitry of an example system that can provide aspects of a modular search object framework. In one example, the operations can be performed by circuitry of a server, such as the modular framework server 116 shown in FIG.

12 illustrates example operations of example circuitry of an example system that can provide aspects of a module search object framework. In one example, the operations can be performed by circuitry of a client device, such as any client device of the system shown in FIG.

Figures 13 and 14 are block diagrams of example electronic devices that can implement aspects of and are related to example systems that can provide a modular search object framework. For example, Figure 13 shows an example of a client device such as audience client device 124 of Figure 1; and Figure 14 shows an example of a server such as modular search framework server 116.

DETAILED DESCRIPTION

The subject matter will now be described more fully below with reference to the accompanying drawings, which form a part hereof and show specific examples by way of illustration. However, the subject matter may be embodied in a variety of different forms, and thus covered or claimed subject matter should be construed as not being limited to the examples set forth herein; the examples are provided for illustrative purposes only. Likewise, the claimed or covered subject matter should have a reasonable scope. For example, the subject matter may be embodied as a method, apparatus, component, or system, or otherwise. Therefore, the following detailed description is not intended to limit the scope of what is claimed.

Overview

Provided herein are novel systems, methods, and circuits for presenting entity-based content (e.g., entity search results and graphical user interfaces), modular search objects, frameworks for supporting entity-based content and modular search objects, and user interactions therewith. Entity-based content can be monetized. Entity search results are search results based on (e.g., solely based on) an entity (e.g., a specific person, place, or thing). Entity search results or other forms of entity-based content delivery (such as an entity graphical user interface (e.g., an entity tray)) can be distinguished from non-entity content in the following manner: in a system (such as a content provider's system), content for a particular entity is delivered via a single root object consisting of one or more child objects. For non-entity search results, the result is not necessarily associated with a root object for a particular entity; there may be many root search results for a particular entity. Additionally, in a non-entity-based system, there may be multiple root graphical user interfaces (GUIs), such as multiple root web pages, for a single entity. In an entity-based content system, each entity has a root object. In an example entity-based system, each entity may have only one web page. For example, for Tom Cruze actor (Actor), in such an entity-based system, there is only one root object for Tom Cruze actor (for example, one root webpage for Tom Cruze actor). However, in a non-entity-based content system, there may be many root objects for Tom Cruze. For example, for a non-entity content delivery system, there may be many different root webpages and websites for Tom Cruze actor. For an entity-based content delivery system, there is only one root object. In the case where each entity in the framework has only one root object, there may be many entity child objects under the entity root object. WIKIPEDIA can be regarded as a system based on entity content delivery. The framework described in this article attempts to remove the ambiguity of entities, which WIKIPEDIA may have experienced. In the example of the framework, entities in the system that may cause ambiguity can be denied entry into the system.

In the framework, the display of aggregated search results can be dynamic and interactive. Furthermore, in the framework, entity search results (even search suggestions and non-entity search results) can attempt to match the searcher's content (e.g., based on the search query entered by the searcher). Furthermore, the user or group profile associated with the searcher can be used to determine user intent. The display of the included search results on multiple interactive objects can include links and other visual information attached to the interactive objects. This information can include a summary of the entity and more. Information about such objects can include detailed information about the entity and links to related entities. This information can be provided via a root graphical user interface (GUI) object for each entity and its child GUI objects, such as through an entity tray and cards within the tray. The entity root GUI object and each child GUI object can include various information about the entity and entities related to it. For example, a tray can be displayed for a particular actor (e.g., tray 201a for actor Tom Cruze), and a child GUI (e.g., card) of the tray can display a map to the actor's restaurants. The specific restaurant location of the restaurant owned by the actor may even be a "place" entity in the frame, and restaurants generally may be a "thing" entity in the frame. In one example, the search results provided by the frame may appear in the form of a list that appears in the form of a stack of cards on a display device.

In examples where the frame presents a stack of card search results or any other two- or three-dimensional form for a list of search results, such results can be graphically enhanced (e.g., photographically enhanced). Additionally, these frame results can be merged with search suggestions in a list. Additionally, such a list can be interactive in that the individual objects in the list can be moved, expanded, shrunk, minimized, or even hidden by the user interacting with the list. Entity search results (as opposed to non-entity search results and/or search suggestions) in the list provided by the frame can be emphasized, for example, through graphical enhancement. The enhancement can even be tactile or through audio output or some other form of perceptible output.

Additionally or alternatively, search results and other GUIs of the framework can organize results and information based on user intent. In an example, user intent can be predicted from an input search query. In such an example, the corresponding search results can be listed in an order that reflects the information that the framework predicted the user intended to receive when entering the search query. In addition, user intent can be reflected in the layout and format of the entity GUI and sub-GUIs displayed to the user. In addition, information within the entity GUI can be arranged and formatted based on the predicted user intent.

Description of the drawings

FIG1 shows a block diagram of an example information system including example devices that can provide a network of modular search object frameworks. The information system 100 in the example of FIG1 includes an account server 102, an account database 104, a search engine server 106, an advertisement server 108, an advertisement database 110, a content database 114, a content server 112, a modular search framework server 116 (which can also be communicatively coupled to corresponding databases), an analytics server 118, and an analytics database 119. The aforementioned servers and databases can be communicatively coupled over a network 120.

The information system 100 is accessible over a network 120 by advertiser devices, such as advertiser client devices 122, and audience devices, such as audience client devices 124. An audience device may be a client device that displays online content, such as physical and non-physical search results, search suggestions, content, and advertisements, to a user. In various examples of such an online information system, a user may search for and obtain content from sources on the network 120, such as a search engine server 106, an ad server 108, an ad database 110, a content server 112, a content database 114, and a modular search framework server 116. Advertisers may provide advertisements for placement on electronic properties (e.g., web pages) and other communications over the network to audience devices, such as audience client devices 124. The online information system may be employed and operated by an online service provider, such as Yahoo! Inc.

The account server 102 stores account information for advertisers. The account server 102 communicates data with the account database 104. The account information may include database records associated with each corresponding advertiser. Appropriate information may be stored, maintained, updated, and read from the account database 104 by the account server 102. Examples include advertiser identification information, advertiser security information such as passwords and other security credentials, account balance information, and information related to content associated with their ads and user interactions associated with their ads and associated content. In addition, examples include analytical data related to their ads and associated content and user interactions with them. In one example, the analytical data may be in the form of one or more schematic diagrams, for example, in the form of schematic diagrams for at least a portion of each audience segment, segment combination, or campaign. The account information may include advertising reservation information. This reservation information may be used as input to determine the availability of advertising impressions.

The account server 102 can be implemented using appropriate equipment. The account server 102 can be implemented as a single server, multiple servers, or other types of computing devices known in the art. Access to the account server 102 can be accomplished through a firewall that protects the account management program and account information from external tampering. Additional security can be provided via enhancements to standard communication protocols, such as secure HTTP (HTTPS) or secure sockets layer (SSL). For example, such security can be applied to any of the servers in FIG. 1 .

The account server 102 may provide an advertiser front end to simplify the process of accessing an advertiser's account information (e.g., a client application). The advertiser front end may be a software routine, program, or application that constitutes a user interface. In a specific example, the advertiser front end may be accessed as a website with an electronic item, which the visiting advertiser may view on an advertiser device such as the advertiser client device 122. The advertiser may use the advertiser front end to view and edit account data and advertising data, such as subscription data. After editing the advertising data, the account data may then be saved to the account database 104.

In addition, audience analytics, delivered effects, effect availability, and segments can be viewed in real time using the advertiser front end. The advertiser front end can be a client application, such as a client application running on an advertiser client device. Scripts and/or applets (e.g., scripts and/or applets) can be part of the front end and can render access points for retrieving audience analytics, delivered effects, effect availability, and segments. In one example, the front end can include a graphical display of fields for selecting at least a portion of an audience segment, segment combination, or campaign. The front end, via the script and/or applet, can request audience analytics, delivered effects, and effect availability for at least a portion of an audience segment, segment combination, or campaign. This information can then be displayed, for example, according to the script and/or applet.

The search engine server 106 and/or the modular search framework server 116 can be one or more servers. Alternatively, the search engine server 106 and/or the modular search framework server 116 can be a computer program, instruction, or software code stored on a computer-readable storage medium and executed on one or more processors of one or more servers. The search engine server 106 and/or the modular search framework server 116 can be accessed by audience devices (such as audience client devices 124 operated by audience members) over the network 120. Access can be through graphical access points. For example, a query input box (e.g., the query input box 212 shown in Figures 2a-3a and 4a-7b and the query input box 820 shown in Figures 8a and 8b) can be an access point for users to submit search queries to the search engine server 106 and/or the modular search framework server 116 from the audience client device 124. Submitted search queries or other user interactions with the search engine server 106 and/or the modular search framework server 116 can be recorded in a data log, and such logs can be transmitted to the analysis server 118 for processing. After processing, the analysis server 118 can output corresponding analysis data to the search engine server 106 and/or the modular search framework server 116 for use in determining the effectiveness of entity and non-entity non-sponsored search results, entity and non-entity sponsored search results, and other types of content and advertising. Analysis circuitry can be used to determine the analysis data, and such circuitry can be embodied in any of the servers and client devices shown in FIG1.

In addition to the search query, the audience client device 124 can transmit interactions with the search results and/or search suggestions (e.g., interactions with the sub-GUI associated with the search results that appear on the same page view as the search results). For example, such interactions can be transmitted to the search engine server 106, the modular search framework server 116, and/or the analysis server 118. The search engine server 106 and/or the modular search framework server 116 locates matching information using appropriate protocols or algorithms and returns the information to the audience client device 124, for example, in the form of search suggestions, entity search results, and non-entity search results. Examples of non-entity search results can include a list of web page search results. The web page search results can include a link to the corresponding web page and a short corresponding description and/or text mined from the web page. The search engine server 106 and/or the modular search framework server 116 can receive user interaction information (which may include search queries) from the audience device and send the corresponding information to the ad server 108 and/or the content server 112, and the ad server 108 and/or the content server 112 can serve the corresponding advertisements and/or search results, but with more in-depth details or accompanying GUIs and sub-GUIs for interacting with topics associated with the advertisements, entity search results, and/or non-entity search results. Information input and/or output by these devices can be recorded in data logs and can be transmitted over the network 120 to the analysis server 118 for processing. The analysis server 118 can provide analytical feedback for influencing future delivery of content. For example, the analysis server 118 can provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs (e.g., entity trays 201a-201d shown in Figures 2b-7b, respectively, and entity tray 801 shown in Figures 8a-8b) and sub-GUIs (e.g., the "Summary" sub-GUI shown in Figures 2b, 6a, 6b, and 8a and the mini-trays 318a-318c shown in Figure 3a) that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

The search engine server 106 and/or the modular search framework server 116 can be designed to help users and potential audience members find information located on the Internet or an intranet. In one example, the search engine server 106 and/or the modular search framework server 116 can also provide electronic objects, such as web pages and/or physical trays, with content (including search results, information that matches the context of the user's query, links to other network destinations, or files of information of interest to the user operating the audience client device 124, as well as streams or web pages of content items and advertising items selected for display to the user) to the audience client device 124 on the network 120. The information provided by the search engine server 106 and/or the modular search framework server 116 can also be logged, and such logs can be transmitted to the analysis server 118 on the network 120 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback for influencing future delivery of content. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

The search engine server 106 and/or the modular search framework server 116 can enable devices such as advertiser client devices 122, audience client devices 124, or another type of client device to search for files of interest, such as files associated with an entity tray, using a search query. Typically, the search engine server 106 and/or the modular search framework server 116 can be accessed by client devices via a server or directly over a network 120. The search engine server 106 and/or the modular search framework server 116 can include a crawler component, an indexer component, an index storage component, a search component, a ranking component, a cache, a user or group profile storage component, an entity storage component, a login component, a user or group profile builder, an entity builder, and an API such as an application program interface (API) corresponding to the modular search framework. For example, the search engine server 106 and/or the modular search framework server 116 can be deployed in a distributed manner, such as via a group of distributed servers. Components can be duplicated within the network, such as for redundancy or better access.

Server 108 operates to deliver advertisements to audience devices, such as audience client devices 124. Advertisements may include text data, graphic data, image data, video data, or audio data. Advertisements may also include data defining advertising information that may be of interest to users of the audience devices. Advertisements may also include corresponding audience targeting information or advertising campaign information, such as information about audience segments and segment combinations. Advertisements may also include data defining links to other online objects accessible via network 120, such as physical trays and other types of objects related to physical trays. In addition, physical GUIs and other types of objects (e.g., physical trays and sub-GUIs related to physical trays) may be advertisements or may include advertisements. The aforementioned audience targeting information and other data associated with the advertisements may be recorded in a data log, and such logs may be transmitted to analysis server 118 for processing. Once processed into corresponding analytical data, analysis server 118 may provide analytical feedback to influence future content delivery. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

For online service providers, advertisements can be displayed on electronic items resulting from user-defined searches based at least in part on search terms. If the displayed advertisement is relevant to at least a portion of an audience segment, segment combination, or campaign, advertising may be beneficial to the user, advertiser, or portal. Therefore, various techniques have been developed to determine corresponding audience segments or subsequently target relevant advertisements to audience members within these segments. For example, user interests, user intentions, and targeting data related to a segment or campaign can be recorded in data logs and such logs can be transmitted to analysis server 118 for processing. Once processed into corresponding analytical data, analysis server 118 can provide analytical feedback to influence future delivery of content. For example, analysis server 118 can provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include advertisements, search suggestions, entity search results, and non-entity search results and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

One method of displaying targeted advertisements includes using demographic characteristics (e.g., age, income, gender, occupation, etc.) to predict user behavior, such as by grouping. Advertisements can be displayed to users in a target audience based at least in part on the predicted user behavior. The above-mentioned target data (such as demographic data and psychographic data) can be recorded in data logs and such logs can be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback for influencing future delivery of content. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs including advertisements, search suggestions, entity search results, and non-entity search results and/or associated with advertisements, search suggestions, entity search results, and non-entity search results.

Another method includes profile-type ad targeting. In this method, user or group profiles for corresponding users or groups can be generated to model user behavior, for example, by tracking the user's path through a network of websites or sites, and compiling the profile based at least in part on the physical GUI (e.g., physical tray), web page, and advertisement that are ultimately delivered. For example, relevance can be identified, such as for user purchases. The identified relevance can be used to target potential buyers by targeting content or ads to specific users. The profile-type targeting data mentioned above can be recorded in a data log and such log can be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback for influencing future delivery of content. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include advertisements, search suggestions, entity search results, and non-entity search results and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

Another approach involves targeting based on the content of a user-requested electronic object, such as the content of a physical GUI (e.g., a physical tray) or web page requested by the user. Advertisements can be placed on the electronic object or associated with other content related to the subject of the advertisement. The relationship between the content and the advertisement can be determined in an appropriate manner. The overall subject of a particular electronic object can be determined, for example, by analyzing the content displayed therein. Furthermore, techniques have been developed for displaying advertisements tailored to the specific portion of the article currently being viewed by the user. Thus, advertisements can be selected by matching keywords and/or phrases within the advertisement and the electronic object. The aforementioned targeting data can be recorded in a data log, and such log can be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback to influence future content delivery. For example, the analysis server 118 can provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

Ad server 108 includes logic and data operable to format ad data for delivery to user devices, such as audience member devices. Ad server 108 is in data communication with ad database 110. Ad database 110 stores information, including data defining ads, for delivery to user devices. This ad data may be stored in ad database 110 by another data processing device or by an advertiser. Ad data may include data defining ad creatives and bid amounts for corresponding ads and/or audience segments. This ad formatting and pricing data may be recorded in a data log, and such log may be transmitted to analytics server 118 for processing. Once processed into corresponding analytical data, analytics server 118 may provide analytical feedback to influence future delivery of content. For example, analytics server 118 may provide feedback to influence the delivery of ads, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include ads, search suggestions, entity search results, non-entity search results, and/or are associated with ads, search suggestions, entity search results, and non-entity search results.

Advertisement data can be formatted into advertisement items, which can be included in a stream of content items and advertisement items provided to an audience device. The formatted advertisement items can be described by appearance, size, shape, text formatting, graphic formatting, and included information, which can be standardized to provide a consistent look and feel for advertisement items in the stream. Such a stream can be included within or integrated with an entity GUI (e.g., an entity tray). Furthermore, related entity GUIs can include similar appearance, size, shape, text formatting, graphic formatting, and included information to provide a consistent look and feel between the entity GUIs and the stream. Furthermore, the formatted data can be recorded in a data log, and such log can be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback to influence future delivery of content. For example, the analysis server 118 can provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

Additionally, the ad server 108 is in data communication with the network 120. The ad server 108 transmits ad data and other information to devices over the network 120. This information may include ad data transmitted to audience devices. This information may also include ad data and other information communicated with advertiser devices, such as advertiser client devices 122. Advertisers operating advertiser devices can access the ad server 108 over the network to access information including ad data. This access may include developing ad creatives, editing ad data, deleting ad data, setting and adjusting bid amounts, and other activities. This access may also include a portal for interacting with an entity GUI (e.g., an entity tray) at least partially controlled or owned by the advertiser, viewing analytics associated with the entity GUI, and editing portions of the entity GUI (e.g., an entity tray). The ad server 108 then provides the ad items and/or entity GUIs to other network devices (e.g., the modular search framework server 116, the analytics server 118, and/or the account server 102) for classification (e.g., associating the ad items and/or entity GUIs with at least a portion of an audience segment, segment combination, or campaign). This information can be used to provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include advertisements, search suggestions, entity search results, and non-entity search results and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

The ad server 108 can provide an advertiser front-end to simplify accessing an advertiser's ad data. The advertiser front-end can be a software routine, program, or application that constitutes a user interface. In a specific example, the advertiser front-end can be accessed as a website with an electronic device, which the advertiser can view on the advertiser's device. Advertisers can use the advertiser front-end to view and edit ad data. After editing the ad data, the ad data can then be saved to the ad database 110 for subsequent transmission to the audience's device in an advertisement.

Ad server 108, content server 112, or any other server described herein may be one or more servers. Alternatively, ad server 108, content server 112, or any other server described herein may be a computer program, instructions, and/or software code stored on a computer-readable storage medium and running on one or more processors of one or more servers. Ad server 108 may access information about advertising items from ad database 110 or from other locations accessible via network 120. Ad server 108 transmits data defining advertising items and other information to a device over network 120. Content server 112 may access information about content items from content database 114 or from other locations accessible via network 120. Content server 112 transmits data defining content items and other information to a device over network 120. Content items and advertising items may include any form of content included in advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

The information about the content item can also include content data and other information transmitted by the content provider operating the content provider device, such as corresponding audience segment information and possible links to entity search results, trays, and other types of entity GUIs. The content provider operating the content provider device can access the content server 112 on the network 120 to access information, including corresponding segment information, entity search result information, and entity GUI information. This access can be used to develop content items, edit content items, delete content items, set and adjust bid amounts, and other activities, such as associating content items with at least a portion of an audience segment, segment combination, or activity. The content provider operating the content provider device can also access the analysis server 118 on the network 120 to access analytical data. Such analysis can help focus on developing content items, editing content items, deleting content items, setting and adjusting bid amounts, and activities related to the distribution of content, such as the distribution of content via entity search results and GUIs (e.g., entity trays).

The content server 112 can provide the content provider front end to simplify the process of the content data of the access content provider.The content provider front end can be a software routine, program or the application that constitutes the user interface.In a specific example, the content provider front end can be accessed as the website with electronic objects, and the access content provider can view this website on the content provider device.The content provider can use the content provider front end to view and edit content data.After (for example at content server 112 or another content source) editing content data, the content data can be saved to content database 114 then and be used to be transferred to other equipment in the network 120 subsequently, such as the equipment of management entity search result and GUI.

The content provider front end can be a client application, such as a client application running on an advertiser client device or an audience client device, respectively. A script and/or applet (e.g., a script and/or applet) can be part of the front end and can render an access point for retrieving effect availability data (e.g., effect availability data), and the script and/or applet can manage the retrieval of effect availability data. In one example, the front end can include a graphical display of fields for selecting at least a portion of an audience segment, segment combination, or campaign. The front end can then request effect availability for at least a portion of an audience segment, segment combination, or campaign via the script and/or applet. The analysis can then be displayed, for example, according to the script and/or applet. Such analysis can also be used to provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include advertisements, search suggestions, entity search results, and non-entity search results and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

The content server 112 includes logic and data operable to format content data for delivery to an audience device. The content server 112 can accordingly provide content items or links to such items to the analysis server 118 and/or the modular search framework server 116 for analysis or association with entities. For example, content items and links can be matched to data and circuits, such as entity data and circuits, or even such as module circuits and data (e.g., module circuits 910 in FIG9 ). Matching can be complex and can be based on historical information related to audience segments and effect availability.

Content data can be formatted so that content items can be included in a stream of content items and advertising items provided to an audience device. Formatted content items can be described by appearance, size, shape, text formatting, graphic formatting, and included information, which can be standardized to provide a consistent look and feel for content items in the stream. Such a stream can be included within or integrated with an entity GUI (e.g., an entity tray). Furthermore, related entity GUIs can include similar appearance, size, shape, text formatting, graphic formatting, and included information to provide a consistent look and feel between the entity GUIs and the stream. Furthermore, the formatted data can be recorded in a data log, and such log can be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback to influence future delivery of content. For example, the analysis server 118 can provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

In one example, a content item can have a bid amount that can be associated, and this bid amount is used to the content item in the stream of the item being shown to the audience device is ranked or positioned. In other examples, the content item does not include a bid amount, or the bid amount is not used to rank the content item. Such a content item can be considered as a non-revenue-generating item. The bid amount and other relevant information can be recorded with a data log and such a log can be transferred to analysis server 118 for processing. Once processed as corresponding analytical data, analysis server 118 can provide feedback for influencing the future delivery of content. For example, analysis server 118 can provide feedback for influencing advertisement, search suggestion, entity search result, non-entity search result and include advertisement, search suggestion, entity search result and non-entity search result and/or the delivery of the corresponding GUI and sub-GUI associated with advertisement, search suggestion, entity search result and non-entity search result.

The above-mentioned servers and databases can be implemented by computing devices. Computing devices are capable of sending or receiving signals, for example, over a wired or wireless network, or of processing or storing signals (e.g., as a physical storage state in a memory), and thus can operate as a server. Thus, devices capable of operating as a server can include, for example, dedicated rack-mounted servers, desktop computers, laptop computers, set-top boxes, integrated devices combining various features (e.g., two or more features of the aforementioned devices), and the like.

Servers can vary widely in configuration or performance, but typically a server may include a central processing unit and memory. A server may also include mass storage devices, a power supply, wired and wireless network interfaces, input/output interfaces, and/or an operating system such as Windows Server, Mac OS X, UNIX, Linux, FreeBSD, etc.

The above-mentioned server and database can be implemented as an online server system or can communicate with an online server system. The online server system can include a device that includes a configuration to respond to a request for receiving content delivery for page views, entity search results and GUI (e.g., entity tray) or other forms to provide data to another device via a network. The online server system can, for example, host sites such as social networking sites or personal user websites (e.g., blogs, video blogs (vlogs), online dating sites, etc.), and the example of a social networking site can include but is not limited to Flicker, Twitter, Facebook, LinkedIn. Such sites can be integrated with the framework via a modular search framework server 116. The online server system can also host various other websites, including but not limited to business websites, educational websites, dictionary websites, encyclopedia websites, Wikipedia, financial websites, government websites, etc. These sites can also be integrated with the framework via a modular search framework server 116.

The online server system can also provide various services, which may include network services, third-party services, audio services, video services, email services, instant messaging (IM) services, SMS services, MMS services, FTP services, IP voice (VOIP) services, calendar services, photo services, etc. Examples of content may include text, images, audio, video, etc., which may be processed in the form of physical signals such as electronic signals, or may be stored in a memory as a physical state, for example. Examples of devices that can operate as online server systems include desktop computers, multi-processor systems, microprocessor types, or programmable consumer electronics, etc. The online server system may (or may not) be under the common ownership or control of the servers and databases described herein.

The network 120 may include a data communication network or a combination of networks. A network may couple devices so that communications may be exchanged, for example, between a server and a client device or other types of devices (e.g., including between wireless devices coupled via a wireless network). A network may also include mass storage, such as a network attached storage (NAS), a storage area network (SAN), or other forms of computer or machine-readable media. A network may include the Internet, a local area network (LAN), a wide area network (WAN), a wired type connection, a wireless type connection, or any combination thereof. Similarly, subnetworks may employ different architectures or may be compatible with different protocols and may interoperate within a larger network such as the network 120.

Various types of devices can be made available to provide interoperability for different architectures or protocols. For example, a router can provide a link between otherwise separate and independent LANs. The communication link or channel can include, for example, an analog telephone line such as a twisted pair, a coaxial cable, a complete or partial digital line including a T1, T2, T3, or T4 type line, an integrated services digital network (ISDN), a digital subscription line (DSL), a wireless link including a satellite link, or other communication links or channels known to those skilled in the art. In addition, a computing device or other related electronic device can be remotely coupled to the network, for example, via a telephone line or link.

Advertiser client device 122 comprises a data processing device that can access information system 100 over network 120. Advertiser client device 122 is operable to interact with any of the servers or databases described herein over network 120. Advertiser client device 122 may implement a client application for viewing electronic items and submitting user requests. Advertiser client device 122 may transmit data (including data defining electronic items and other information) to information system 100. Advertiser client device 122 may receive communications from information system 100 including data defining electronic items and advertising creatives. The aforementioned interactions and information may be recorded in a data log, and such log may be transmitted to analytics server 118 for processing. Once processed into corresponding analytical data, analytics server 118 may provide analytical feedback to influence future delivery of content. For example, analytics server 118 may provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

In one example, a content provider can access the information system 100 using a content provider device that is generally similar in structure and function to an advertiser device. For example, the content provider device provides access to content data in the content database 114.

Audience client devices 124 comprise data processing devices that can access information system 100 over network 120. Audience client devices 124 are operable to interact with search engine server 106, ad server 108, content server 112, analytics server 118, and modular search framework server 116 over network 120. Audience client devices 124 can implement client applications for viewing electronic content and submitting user requests. A user operating audience client device 124 can enter a search request and transmit the search request to information system 100. The search request is processed by the search engine and search results are returned to audience client device 124. The above interactions and information are recorded in data logs and such logs can be transmitted to analytics server 118 for processing. Once processed into corresponding analytical data, analytics server 118 can provide analytical feedback to influence future content delivery. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

In other examples, a user of an audience client device 124 may request data, such as a page of information, from the online information system 100. Alternatively, the data may be provided in another environment, such as a native mobile application, a TV application, or an audio application. The online information system 100 may provide the data or redirect the browser to another source of data. Additionally, the ad server may select advertisements from the advertisement database 110 and include data defining the advertisements in the data provided to the audience client device 124. The aforementioned interactions and information may be recorded in a data log, and such logs may be transmitted to the analysis server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 may provide analytical feedback to influence future delivery of content. For example, the analysis server 118 may provide feedback to influence the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

When accessing information on the information system 100, the advertiser client device 122 and the audience client device 124 operate as client devices. Client devices (such as the advertiser client device 122 and the audience client device 124) can include computing devices capable of sending or receiving signals, for example, via a wired or wireless network. Client devices can include, for example, desktop computers or portable devices such as cellular phones, smartphones, display pagers, radio frequency (RF) devices, infrared (IR) devices, personal digital assistants (PDAs), handheld computers, tablet computers, laptop computers, set-top boxes, wearable computers, integrated devices that combine various features (e.g., features of the aforementioned devices), etc. In the example of FIG1 , both the laptop computer 126 and the smartphone 128, which can be client devices, can be operated as advertiser devices or audience devices.

Client devices can be diverse in terms of performance or features. The claimed subject matter is intended to cover a wide range of possible variations. For example, a cell phone may include a numeric keypad or a limited-function display, such as a monochrome liquid crystal display (LCD) for displaying text. However, in contrast, as another example, a client device capable of accessing the Internet may include a physical or virtual keyboard, mass storage, an accelerometer, a gyroscope, a global positioning system (GPS) or other location identification type capability, or a highly functional display such as a touch-sensitive color 2D or 3D display.

Client devices such as advertiser client device 122 and audience client device 124 may include or execute various operating systems, including personal computer operating systems such as Windows, iOS, or Linux, or mobile operating systems such as iOS, Android, or Windows Mobile. Client devices may include or execute various possible applications, such as client software applications, that enable communication with other devices (e.g., via email, short message service (SMS), or multimedia message service (MMS), including via networks such as social networks, such as Facebook, LinkedIn, Twitter, Flickr, or Google+, to provide just a few possible examples). Client devices may also include or execute applications for communicating content, such as text content, multimedia content, and the like. Client devices may also include or execute applications for performing various possible tasks, such as browsing, searching, and playing various forms of content, including locally or remotely stored or streamed videos, or video games. The foregoing is provided to illustrate the claimed subject matter and is intended to encompass a broad range of possible features or capabilities. At least some of the features, capabilities, and interactions mentioned above may be recorded in data logs, and such logs may be transmitted to analytics server 118 for processing. Once processed into corresponding analytical data, the analysis server 118 can provide analytical feedback for influencing future delivery of content. For example, the analysis server 118 can provide feedback for influencing the delivery of advertisements, search suggestions, entity search results, non-entity search results, and corresponding GUIs and sub-GUIs that include and/or are associated with advertisements, search suggestions, entity search results, and non-entity search results.

Additionally, the disclosed methods and systems can be implemented at least partially in a cloud computing environment, at least partially in a server, at least partially in a client device, or in any combination thereof.

Figures 2a-8b illustrate screen representations that can be provided by the modular search object framework. In Figures 2a-7b, the screen representations are depicted as being displayed on a display 202 of a client mobile device 200. In Figures 8a and 8b, the screen representations are depicted as being displayed on a display 802 of a client device or coupled to a client device (such as a display associated with a personal computer or smart TV). Displays 202 and 802 can each include a touch screen configured to receive user input, such as touch gestures.

Within the screen representations, illustrated are graphical user interfaces (GUIs) provided by the framework and GUIs provided by a local operating system and/or a local client application, such as a web browser. For example, portion 204a and touchscreen keyboard 204b in FIG. 2a of the screen representation are portions of the GUI provided by the local operating system of the client mobile device 200. Portion 804 in FIG. 8a and FIG. 8b is a portion of the GUI provided by the local operating system of the client device associated with display 802. Additionally, for example, portion 206a in FIG. 2a-3a and FIG. 5a-7b of the screen representations is a portion of the GUI provided by the framework and/or a service provider associated with the framework, and portions 206b-206m in FIG. 2a-7b are portions of the GUI provided by the framework. Additionally, for example, portion 208a in FIG. 2b, FIG. 3a, and FIG. 6a-7b is a portion of the GUI provided by a local client application executing on the client mobile device 200. In FIG. 8a and FIG. 8b, web browser 808 is a GUI provided by a local web browser application executing on the client device associated with display 802. Portion 806a is a GUI portion provided by the framework, and portions 806b and 806c are GUI portions provided by the framework and/or a service provider associated with the framework.

In one example, GUI parts such as 204b, 206a and 208a can be hidden by local operating system, local client application, framework or any combination thereof, so that the GUI parts provided by framework such as part 206b-206m can be displayed on the larger space of display 202. Even GUI part 204a can be hidden. For the example result of such function, see Fig. 3b. When the finger of the user such as finger 306 in Fig. 3b interacts with the GUI parts in the part provided by framework such as part 206e, the function of hiding GUI parts can appear. In one example, this function and other object movement are enhanced, and this movement and hiding occur seamlessly under the situation that there is no unwanted visual illusion, because local operating system, local client application and framework are tightly coupled. For example, the circuit controlling such function can be a circuit combination of local operating system, local client application and framework, which is present in host device (such as mobile client device 200 or client device associated with display 802).

In one example, the GUI portion provided by the framework can interact with the GUI portion provided by the local client application and the local operating system. Due to the presence of associated circuitry (local to the client device displaying the GUI portion), these interactions occur seamlessly. Due to the tight coupling between the circuitry of the local operating system, local client application, and the framework, the conversion between the display changes of the various page views and parts shown in Figures 2a-7b and 8a-8b can occur without unwanted visual artifacts. For example, a part of the circuitry can include client-side code such as AJAX, JavaScript, or any combination thereof.

Alternatively or additionally, the framework can provide animations, including deliberate visual effects, to provide visually pleasing transitions when switching from one displayed feature to another. For example, a theme for the visual presentation of a GUI portion of the framework (optionally, a GUI portion that interacts with or is displayed simultaneously with the GUI portion of the framework) can include a card theme. For example, a card theme can include GUI portions having borders with curved corners, and GUI portions that can overlap each other (to give the appearance that each portion is a card with curved corners). The framework's transitions between various visual displays can include animations, including rearrangements of cards, such as shuffling. Alternatively or additionally, animations can include moving cards into or out of a set of cards. A deck of cards can include partial expansion in linear and/or rotational directions in three-dimensional graphical space. Animations for the transitions can include expanding the cards in the deck horizontally along the x-axis, vertically along the y-axis, along the z-axis in a direction entering or leaving the screen, rotationally around any one of the x-axis, y-axis, and z-axis, or a combination of the x-axis, y-axis, and z-axis, or any combination thereof.

For example, FIG2a shows cards being vertically expanded along the y-axis relative to display 202. FIG2b shows a card being pulled out of a partially vertically expanded deck 210. During a transition between display portion 206b and display portion 206c, the expanded cards of portion 206b can be vertically retracted into the deck 210 displayed in portion 206c. When transitioning from one card to another, the cards labeled "Summary" and "More" of portions 206c and 206d, respectively, in FIG2b and FIG3a, can simply flash from one card to the other. Alternatively, such card transitions can include animations that include cards moving in and/or out of deck 210. The animation can also include shuffling of deck 210. An animation of shuffling deck 210 can also appear when a search query is presented (such as when a query is entered into search query box 212). For example, when the framework switches from providing information about Tom Cruze in Figures 2a-5b to providing information about Katie Bolmes in Figures 6a-6b, the deck of cards 210 can be shuffled to give the appearance that the deck is being shuffled to find cards about Katie Bolmes. Such animations can also occur when a link or button is clicked (causing a transition from one entity to another). In addition, when a query is entered or at least partially entered, such an action can cause a transition from one entity to another.

In one example, transitions within an entity can occur with relatively simple animations (such as flashing between cards, scrolling through related cards arranged side by side in a tray of cards in a single direction, or at least partially moving one or more cards into or out of a deck) in accordance with user interaction with the corresponding entity GUI. Transitions from one entity to another can include relatively more complex animations, such as shuffling a deck of cards. In some examples, shuffling can occur in transitions within an entity or in transitions from one entity to another; however, in such examples, shuffling for transitions within an entity can occur in a significantly shorter amount of time than shuffling between entity changes. For example, shuffling due to transitions within an entity can take less than one second, while shuffling due to transitions between entities can take more than two seconds.

Figures 2a-8b illustrate example screens for navigating content (such as online content), highlighting the various features provided by the framework. Figure 2a shows the text "tom" being entered into a search query box 212 via keyboard 204b. Alternatively, the text can be entered via voice commands or some other form of user input. When "tom" is entered into the box, or when "tom" is entered and the search execution button 214 is clicked, search suggestions and/or search results may appear within portion 206b on display 202. For example, when "tom" is entered into box 212 but before the search execution button 214 is clicked, search topic suggestions such as search suggestions 216 and 218 in Figure 2a may appear. The user can select one of these suggestions, which will cause the query to be executed using the corresponding text displayed for the suggestion. In this example, the suggestions appear as cards. These suggestion cards may have similar color and texture schemes, and the schemes may be simple, such as a solid color or a spectrum of colors within the full spectrum of colors. For example, the suggestion cards may each be various shades of blue. Additionally, when "tom" is entered into box 212, actual search results may appear, for example, search results associated with a specific entity (such as a specific person, place, or thing). In this example, the entity search results include search results 220, 222, and 224 in Figure 2a. These results appear as cards. These search result cards can have different color and texture schemes and can include themes associated with photos (such as photos bleed into the card). This visual feature helps users distinguish between search result cards (such as entity search result cards) and search suggestion cards (optionally, non-entity search result cards). When the search is actually performed and the search results are displayed (for example, in section 206h of Figure 5a and 206i of Figure 5b), the entity search results can be visually distinguished from a set of non-entity search results (such as a set of web search results) by the color and texture scheme of the cards representing the results. For example, a simple, single-color range theme can represent a set of web search results, while a more complex theme (such as a bleed-in photo) can represent entity search results. In FIG. 5 a , entity search results 502 a - 502 f are visually distinguishable from web-based search results 504 a - 504 c .

In the example shown in Figures 2a and 2b, a user can select one of the search results shown in Figure 2a (entity search results 220, 222, or 224), which causes the page view to transition from displaying expanded search results and suggestions to a full-sized card that includes information about the selected entity, such as shown in Figure 2b. For example, the user may have selected the entity search result 220 labeled "Tom Cruze - Actor," which would result in a full-sized card being displayed for that entity (Tom Cruze - Actor). A full-sized card is a card that includes the graphical functionality of the entity tray. In other words, the full-sized card can be the initial GUI of the entity tray.

Full-size entity cards (such as the card displayed for Tom Cruze, e.g., the cards within sections 206c-206g) provide information specific to that entity or entities related to that entity. In addition to specific people (real people or fictional characters), entities can also include any specific places or things. For example, section 206i in FIG7a depicts a place entity card for the entity Green Can Coffee. Section 206m in FIG7b depicts a thing entity (more specifically, a product entity) for the entity ZBOX.

The various versions of ZBOX can have their own full-sized cards and entity trays. In this sense, there is a broad hierarchy and network of entities. Within this broad hierarchy and network, people, places, and things can have various types of relationships. For example, these relationships can include object relationships, such as from the perspective of an object hierarchy (including the relationship between general items and specific items (for example, the relationship between a general ZBOX and a specific version of a ZBOX)). This object hierarchy also applies to "places". For example, Green Can Coffee can be a thing (a company) in general, but each location of Green Can Coffee is a specific place. Generic things can be related to these specific places, and such relationships can be output for the user to navigate through associated links.

Referring back to Figure 2b, a full-size card 226 is shown for the actor Tom Cruzer. Within the full-size card 226, there are many visible and hidden parts. Overlapping the full-size card are two sub-cards 228a and 228b, namely a card marked with "Summary" and a card marked with "More" (hereinafter referred to as the Summary card and the "More" card). The full-size card 226 and the two sub-cards 228a and 228b are extended from the card deck 210. Part 206c (including the card deck 210 and any cards extended from the card deck) can be called a physical tray. The part 206b overlapped by the keyboard 204b can also include a tray 203 for at least cards 216-224. The tray can be associated with at least a portion of the search query (even an unexecuted search query). For example, parts 206b, 206h, and 206i include a tray associated with the search term "tom." Sections 206c-206g contain tray 201a associated with the entity being searched for (Tom Cruzer, actor). Sections 206j-206k contain tray 201b associated with the entity being searched for (Katie Bolmes, actress). Section 206l contains tray 201c associated with the entity being searched for (Green Can Coffee, place entity). Section 206m contains tray 201d associated with the entity being searched for (ZBOX, thing entity). In Figures 8a-8b, section 806a includes tray 801 associated with Tom Cruzer, actor. Additionally, in Figures 8a-8b, section 806a contains tray 803 associated with the search term "tom."

Along with the full-size card, a display associated with at least one module circuit may appear. Each module has corresponding circuits configured to perform various aspects of the module. In Figure 2b, a GUI rendered by the entity summary module is shown. The summary GUI includes summary information about the selected entity. In Figure 2b, the selected entity is Tom Cruze. The information that appears in the summary GUI can be mined information, information from a content database, information selected by the entity responsible for editing the information, information selected by machine learning, or any combination thereof. Such information may include the most searched information for the selected entity. The most searched information can be collected from online search logs and other logs about web browsing. This information can be updated at various intervals. The length of time between each update can be based on the number of requests for the entity summary for the selected entity. The information within the entity summary can be plain text or hypertext (which, when selected, links to other entities or launches hypertext related to the search).

In addition, as shown in Figure 2b, a theme can be rendered by the entity theme module circuit. The entity theme module circuit can include visual and instrumental settings for the tray associated with the selected entity. For example, the tray can look, feel, and operate differently. Such settings can include a background for the tray. The background can include a photo associated with the entity, such as a photo of the entity sized to include a portion of the tray. Figures 2b-4b show at least a portion of a background 230 for the entity Tom Cruze. The background 230 includes a label 232a for the entity Tom Cruze actor and a photo image 232b of Tom Cruze. In addition to the tray for Tom Cruze actor, the search result card for Tom Cruze also includes a portion of the background 230 (see Figures 2a and 5a). In addition, the background can be modified by the background module circuit, such as by being modified according to the format of the search results (see the portion of the modified background 234 in Figure 5b).

At the screen in Figure 2b, the user can select the tab associated with the "More" card 228b. This can cause the tray for actor Tom Cruze to switch from summary card 228a to "More" card 228b. The display of "More" card 228b is shown in Figure 3a. "More" card 228b includes a GUI rendered by the "More" module circuit. This "More" GUI includes information about the selected entity. As shown, the information in the "More" GUI can be displayed via sub-GUIs associated with different categories and module circuits associated with different categories. Each sub-GUI can be rendered by one or more related module circuits. The "More" module circuit can include configuration information, such as display configuration information for modules and sub-modules within the modules. For example, in Figure 3a, some sub-modules are displayed as scrollable mini-trays 318a-318c with corresponding mini-cards displayed side by side. For example, in a touchscreen environment, the mini-cards within the mini-tray can be cycled through by sliding the tray in the corresponding direction.

The "More" module circuit may also include GUI configuration information regarding which sub-modules are to be included in the "More" module GUI. For example, in FIG3a, for the actor Tom Cruze, at least the sub-module circuits for related movies, romantically related people, and generally related people are selected for inclusion in the "More" module circuit. The "More" module circuit for the actor Tom Cruze is a combination of the "More" module circuit for Tom Cruze and the entity circuit, which communicate with each other. The selection of sub-module circuits for each module circuit can be a global selection across all entities, a specific selection for each entity type, a specific selection for each entity, or any combination thereof. For example, in the "More" module circuit, the person entity can include the "people also searched" circuit module, but the place and thing entities cannot. However, for example, the "Image" module sub-GUI (as shown as sub-GUI 308 in FIG3b) can be universally selected for all types of entities. For Tom Cruze only, or any other person with multiple known relationships and/or ex-spouses, an instance of the "More" module may include a "Relationships" module sub-GUI.

The selection of sub-module GUIs can be based on various sources, such as information mined from partner websites and information from a content database (e.g., a database storing search logs with information related to the most common categories searched for in conjunction with queries for a particular entity). For example, search logs may indicate that a user's query for information about Tom Cruze likely also intends to seek information about movies in which Tom Cruze appears. Alternatively, an owner (e.g., an owner advertiser) associated with the Tom Cruze entity tray can manually select sub-module GUIs to include in a particular module GUI, such as the "More" module GUI. Using machine learning to predict the intent of a user querying for an entity and using this prediction to select sub-modules for the module circuitry has advantages. Indeed, various aspects of an entity tray can be determined based on this predicted intent of a user searching for an entity associated with the entity tray. For example, machine learning can be used to determine predicted information and information that a user desires to be displayed anywhere on the entity GUI. Such information can be determined based on historical online user interaction data, which can include data related to clicks, searches, dwell time, or any combination thereof.

In Figure 3a, the selected entity is still Tom Cruze. The information that appears in the "More" GUI can be mined information, information from a content database, information selected by the entity responsible for compiling the information, information selected by machine learning, or any combination thereof. Such information can include the most searched information for the selected entity for each category associated with the displayed sub-GUI. The most searched information and detailed information related to each category for the entity can be collected from online search logs and other logs related to web browsing. The classification information and detailed information can be updated at various intervals. The length of time between updates to each sub-GUI can be based on the number of sub-GUI requests for the selected entity. The information within the entity can be images and/or text and can include hyperlinks to other entities or initiate related searches. For example, a user can select one of the movie images in the movie sub-GUI 301, which can initiate a search for that movie or navigate to the entity tray for that movie (if such an entity tray is available within the framework). Additionally, as shown, the user may select one of the person images in the "Relationships" sub-GUI 303 or the "People Also Searched For" sub-GUI 305, and this may initiate a search for the selected person or navigation to a physical tray for that person.

As shown, the user can select one of the images associated with one of Tom Cruze's romances, such as image 302 labeled "Katie Bolmes." This can cause the framework's GUI to replace tray 201a for Tom Cruze, the actor, with tray 201b for Katie Bolmes, the actress, in Figures 6a and 6b. The display of tray 201b for Katie Bolmes, the actress, is shown in Figures 6a and 6b. Figure 6a includes a summary card for Katie Bolmes, the actress, rendered on the tray. In one example, the default landing page or child card of the tray is a summary card. Additionally, Figure 6a shows a change in the label of the deck to "All search results for Katie Bolmes" instead of "All search results for Tom Cruze." Additionally, the text in the search box 212 can be automatically changed to text associated with the destination entity. In this case, navigation from the Tom Cruze tray 201a to the Katie Bolmes tray 201b causes a change in the labels on the deck and the text in the search box to change to include text that says Katie Bolmes instead of Tom Cruze.

In Figure 6b, the text string "favorite color" has been entered into the search box along with "Katie Bolmes." This additional text can be predicted to be a question associated with the entity predicted for the search text. In this case, the framework, through the question prediction module, predicts that the user is interested in actress Katie Bolmes' favorite color. The question prediction module circuitry can be coupled to a question answering module circuitry configured to search for an answer to the predicted question. Figure 6b shows the question answering module circuitry configured to output an answer 602 at the top of the summary card for Katie Bolmes in an answer location 604.

Referring back to FIG. 3a , a user can select card deck 210 by, for example, swiping upward from the text "All Search Results for Tom Cruze" or clicking on the text. This can cause tray 201a for the actor Tom Cruze to transition from the "More" card 228b to the "All Search Results" card 304 in FIG. The display of "All Search Results" card 304 is shown in FIG. "All Search Results" card 304 includes a GUI rendered by the "All Search Results" module. The "All Search Results" GUI includes information about the selected entity. As shown, the information in the "All Search Results" GUI can be displayed via sub-GUIs associated with different categories and module circuits associated with different categories. Each sub-GUI can be rendered by one or more related module circuits. The "All Search Results" module circuit can include configuration information, such as display configuration information for the module circuit and sub-modules within the module circuit. For example, in FIG. 3b , the image sub-GUI is displayed as a scrollable mini-tray with corresponding mini-cards displayed side by side, each card including an image of an entity associated with tray 201a for the actor Tom Cruze. The "Web Results" submodule is presented as a scrollable miniature tray with a list of web-based search results. These search results are clickable to navigate to the corresponding web page or another card associated with the physical tray. In FIG3 b , a user's finger 306 is shown gesturing over the web search results provided by the web results submodule circuitry. When such a gesture is made, portions 208 a and 206 b are hidden to allow more screen space to display the web search results.

The "all search results" module may also include configuration information regarding which submodules are to be included in the "all search results" module. For example, in Figure 3b, at least the submodules for web search results and image search results are selected to be included in the "all search results" module for Tom Cruze the actor. As mentioned, the selection of submodules for each module may be a global selection across all entities, a specific selection for each entity type, a specific selection for each entity, or any combination thereof. For example, in the "all search results" module, both people and things entities may include an "image" module, but places entities may not. However, for example, for the "all search results" module, the "web results" module (as shown in Figure 3b as sub-GUI 310) may be a universal selection for all types of entities. Only for Tom Cruze or any other person with multiple known close relationships and/or ex-spouses, an instance of the "all search results" module may include a display of the "relationships" module (not shown in Figure 3b). For the "All Search Results" module circuit, as well as other module circuits having the GUI depicted herein, it should be noted that the associated sub-GUI may be hidden from the shown view, but may become visible when scrolling through the corresponding section.

In FIG3b , the selected entity is still Tom Cruze, and the user can select a link such as image link 312 or text link 314, or a sub-link such as sub-link 316. Selecting a link such as image link 312 can cause the client application to navigate to a webpage associated with the website hosting the corresponding image. Alternatively, it can cause the client application to navigate to a card within the entity's tray, such as card 402 for an image slideshow module (as shown in FIG4a ). Selecting a text link such as text link 314 can cause the client application to navigate to the webpage corresponding to the link. Selecting a sub-link such as sub-link 316 labeled “map” can cause the client application to navigate to a card such as map card 404 within the entity's tray (as shown in FIG4b ). Alternatively, selecting a sub-link such as sub-link 316 labeled “map” can cause the client application to navigate to another webpage associated with the link, such as a webpage on the same website associated with a link having a map associated with the entity (e.g., see FIG4b ). The information within the frame's GUI may be images and/or text, and may include hyperlinks to other cards within the entity tray, other entities, or may initiate a related search.

The information that appears in the "All Search Results" GUI can be mined information, information from a content database, an advertising database, or a search engine database, or any combination thereof, information selected by the entity responsible for editing the information, information selected by machine learning, or any combination thereof. The search results displayed by the "All Search Results" GUI can be determined by various search engine algorithms. The search results can include the most searched information for the selected entity for each category associated with the displayed sub-GUI. The most searched information and detailed information related to each category for the entity can be collected from online search logs and other logs about web browsing and searching. The classification information and search results can be updated at various intervals. The length of time between updates to each search result sub-GUI can be based on the number of sub-GUIs requested for the selected entity.

To navigate back from card 402 in Figure 4a or card 404 in Figure 4b, the user can perform a specific gesture toward portion 206f or 206g, respectively. In one example, the user can begin swiping downward at the top of a card to move the card downward, revealing the portion of tray 201a that was already covered by the card. For example, using a gesture to move card 402 downward can cause the display shown in Figures 2b or 3a or any other previously displayed card for that entity, such as the last card displayed for that entity before the card was moved downward. In other words, this function can function similarly to a back button. To navigate to a new entity, the user can select a link to another entity or, along with other actions, enter a new query in search box 212. For example, when entering text in search box 212, the framework can cause client device 200 to display search suggestions and/or search results (similar to those shown in portion 206 in Figure 2a, except for suggestions and/or results related to the newly entered text). The user can then select another entity from the list.

FIG9 illustrates an example block diagram of example circuitry for a server of an example system that can provide aspects of a modular search object framework, such as the modular search framework server 116 shown in FIG1 . FIG9 also illustrates a client device 901 (e.g., any of the client devices 124-128 of FIG1 , or the device 1007 of FIG10 and the device 1300 of FIG13 ) communicatively coupled to the server 900 over the network 120. The server 900 can include one or more servers, such as the modular search framework server 116 and/or the search engine server 106.

The server 900 includes a processor circuit 902 (eg, central processing unit 1402 of FIG. 14 ) and a system executable by the processor circuit and stored in a non-transitory medium 904 (eg, memory 1410 ). The system is configured to provide several aspects of the framework.

The system includes network communication circuitry 906 (e.g., circuitry included in network interface 1430) and framework circuitry 908 (e.g., circuitry included in modular search object framework 1426). Network communication circuitry 906 and framework circuitry are communicatively coupled via circuitry. In the present disclosure, circuitry may include circuitry that is wirelessly connected and circuitry that is connected via hardware such as wires. Network communication circuitry 906 may be configured to communicatively couple the system to client device 901 over network 120. This allows, for example, a portion of an entity provided by server 900 to be displayed via a client application installed on client device 901.

The framework circuitry 908 includes module circuitry 910 (e.g., module circuitry 1427a), entity circuitry 912 (e.g., entity circuitry 1427b), inter-module interface circuitry 914, inter-entity interface circuitry 916, and inter-frame interface circuitry 918. The inter-module interface circuitry 914 may be configured to communicatively couple any module circuitry in the module circuitry 910. For example, the inter-module interface circuitry 914 may communicatively couple at least an entity GUI module circuitry, such as the tray module circuitry 920, to one or more other circuits in the module circuitry 910.

The inter-frame interface circuit 918 can be configured to communicatively couple at least one entity circuit in the entity circuit 912 to any one of the multiple module circuits in the module circuit 910, such as coupling any one of the entity circuits to the tray module circuit 920. For the example entity portions shown in Figures 2a-8b, the tray module circuit can be configured to interact with at least one entity circuit to output the interactive entity portion to a page view for the corresponding entity. In addition, in such an example, the interactive portion can include multiple movable visual objects having information related to the corresponding entity. In addition, in such an example, the multiple movable visual objects are movable within the interactive entity portion. These functions can be implemented via the interoperation of the sub-circuits of the module circuit 910 and the entity circuit 912.

In addition, these movable objects and associated functions can be provided by any type of module circuit and entity circuit interoperation through coupling provided by the inter-frame interface circuit 918. In one example, the movable visual object can be a card. In addition, the card can have rounded corners as shown in Figures 2a-8b. As shown in Figure 3a, such a card can include a miniature tray of miniature cards within the card, and the miniature cards can include information about the entity. In addition, the movable object can include links for navigating between entities, and such objects can be overlapping, for example, where a first overlapping object is movable to view at least a portion of a second object under the first object. In addition, the movable visual object can be adjacent to or adjacent to another object in the movable object. These functions can be implemented via the interoperation of the subcircuits of the module circuit 910 and the entity circuit 912.

In addition, advantageous functionality such as seamless movement of objects among multiple movable objects without unintended visual effects can be attributed to the tight coupling of the circuitry of the framework circuitry 908. In addition, the tight coupling between the client circuitry of the framework circuitry installed on the client device 901 and the local operating system circuitry of the client device, and the circuitry of the client application installed on the client device, can also improve such advantageous functionality. Code can be sent from the server 900 to the client device 901, which can add and configure the client circuitry of the framework circuitry for the client device. For example, circuitry within the client device 1007 of Figure 10 can be added or changed based on such code transmitted from the server 900. The code may include an object representing a portion of the framework circuitry 908.

Inter-entity interface circuitry 916 may be configured to communicatively couple at least one of the plurality of entity circuits to one or more other entity circuits of the plurality of entity circuits of entity circuitry 912. Inter-entity interface circuitry 916 is communicatively coupled to inter-module interface circuitry 914 via inter-framework interface circuitry 918. These interconnections may provide a basis for linking between the entities and corresponding text shown in Figures 2a-8b and associating a particular module GUI with a particular entity.

The module circuit 910 may include at least one module circuit, such as a tray module circuit 920. Other examples of module circuits within the module circuit 910 may include an entity search result circuit, a search suggestion circuit, a non-entity search result circuit (e.g., a web search result circuit), a map circuit, and more. Such circuits may provide the various structures and operations shown in Figures 2a-8b and Figures 10-12. As shown by Figure 9, the hierarchy of module circuits within the circuit 910 may be extensive. For example, as shown, a module circuit such as the tray module circuit 920 may include sub-module circuits, and the sub-module circuits may each have their own sub-module circuits. For example, most of the module circuits of the circuit 910 (whether or not they are sub-module circuits) may each include at least a sub-module circuit that configures the circuit and configures one or more GUIs provided by the circuit. The example organization of the circuit of the module circuit 910 is consistent with the arrangement of the GUI and sub-GUIs shown in Figures 2a-8b. However, other steps may also be consistent with the GUI shown.

For example, tray circuit 920 may include a summary circuit, a tray configuration circuit that may include a tray GUI configuration circuit, and a "more" circuit associated with the "more" GUI shown in Figure 3a. In addition, as shown in Figure 9, tray circuit 920 includes other sub-circuits for other functions imagined by the framework regarding the tray object. In Figure 9, a summary circuit such as the corresponding circuit that provides the summary GUI in Figure 2b includes a configuration circuit such as a circuit for the configuration of the summary GUI, and an analysis circuit. The analysis circuit may provide at least a portion of the information that may be intended to be viewed by the user. Some GUIs of the framework may be associated with the analysis circuit of the summary circuit or other analysis circuits of the module circuit 910. Such a GUI is likely to incorporate information needed for prediction of audience members of the framework.

Entity search results circuitry 922 may provide various functions and structures associated with retrieving and displaying entity search results (such as the entity search results shown in Figures 2a, 5a, 5b, 8a, and 8b). Search suggestion circuitry may provide various functions and structures associated with retrieving and displaying search suggestions (such as the search suggestions shown in Figures 2a, 5a, 8a, and 8b). Web search results circuitry 926 may provide various functions and structures associated with retrieving and displaying web search results (such as the web search results shown in Figures 3b, 4b, and 8b). For the purposes of this disclosure, web search results are examples of non-entity search results. Other exemplary non-entity search results are image search results that vaguely associate an image with the search query. Entity search results are results that include information objects for specific entities (such as a specific person, place, or thing). For places and things, there are sub-entities. Entities will be explained in more detail in another section of this disclosure. Map circuitry 928 may provide various functions and structures associated with retrieving and displaying map-based search results, such as the map search result shown in Figure 4b. Circuit map 928 may include or be associated with navigation circuitry of module circuitry 910 (e.g., circuitry including circuitry for discovering routes and device geographic location). As mentioned, each module circuitry may include sub-module circuitry, such as corresponding user interface circuitry, configuration circuitry, analysis circuitry, data processing circuitry, data storage circuitry, data retrieval circuitry, navigation circuitry, or any combination thereof. The examples of module circuitry described herein and shown in FIG9 are merely illustrative of the breadth of the framework.

Entity circuit 912 includes various types of entity circuits, including person circuit 930, place circuit 932, and thing circuit 934. Person circuit 930 includes a circuit for each specific person that can be identified as an entity by the framework. The specific person can be a real living person or a deceased person. Well-known people who are frequently searched online, such as celebrities, can be automatically entered into the framework and circuits can be automatically generated for those people. Less well-known people (such as ordinary people who run small businesses) can submit applications to generate circuits for themselves, their businesses, and/or the products they hope to sell through the framework. Specific people can also include characters in fictional work. For fictional characters, multiple entities can be created for known characters. For example, the character "Supermom" can have an entity circuit for each Supermom character entered into the framework (e.g., multiple Supermoms from different Supermom movies and TV series, and multiple Supermoms from different versions of the Supermom comic book). When the corresponding entity is submitted and accepted by the framework, the person entity becomes identifiable. At that time, a circuit can be generated for that person entity. A front end for the modular search framework server 116 and/or the account server 102 may facilitate input of entities, such as human entities.

Place circuits 932 include a circuit for each specific location that can be identified as an entity through the framework. A specific location can be an address, a global location, a physical location without an address, or any combination thereof. A physical location without an address (e.g., an obscure park) can be submitted through an application process. Locations without addresses but commonly searched for (e.g., national parks) can be automatically entered into the system as circuits. In other words, well-known places that are frequently searched online, such as landmarks, government-managed parks, cities, countries, and even well-known bodies of water, can be automatically entered into the framework and circuits automatically generated for those locations. Less well-known locations (such as ordinary parking lots without addresses) can be submitted via an application for a circuit to be generated for that location. For example, businesses and products can be marketed through place entities. A place can be any geographic entity, whether fictional, non-fictional, still existing, historical, or some combination thereof. For fictional locations, multiple entities can be created for known fictional locations. For example, each description of Atlantis used in a work of fiction can have its own entity circuit. When the corresponding entity is submitted and accepted by the framework, the place entity becomes identifiable. At that time, a circuit can be generated for the place entity. The front end for the modular search framework server 116 and/or the account server 102 can facilitate the input of entities, such as place entities.

Thing circuits 934 include circuits for each specific thing that can be identified as an entity through the framework. Specific organizations, products, services, and named creatures (e.g., pets or famous circus animals) can be thing entities. Thing entities can overlap with place entities and fictional character entities; for example, a geographical location like the dark side of the moon can also be a thing. Alternatively, for example, "Wizard of Oy" can be a thing entity (e.g., a movie entity) and a character entity, such as the Wizard of Oy character from the original film production. Additionally, there can be iterations of some things. To continue the Wizard of Oy theme, there can be some well-known productions of the movie in live theater format. Well-known things that are frequently searched online (such as movies, mass-produced products, and large companies) can be automatically entered into the framework and circuits can be automatically generated for those things. Less well-known things (such as new products developed by ordinary people) can be submitted via applications for circuits to be generated for those things. For example, services and products can be marketed through thing entities. A thing can be almost any clear thing that can be claimed. A thing can be fictional, non-fictional, still existing, historical, or some combination thereof. A thing entity becomes identifiable when a corresponding entity is submitted and accepted by the framework. At that time, a circuit can be generated for the thing entity. A front end for the modular search framework server 116 and/or the account server 102 can facilitate inputting entities, such as thing entities.

Each specific person, place, or thing circuit of entity circuit 912 can include and provide a corresponding data model for collecting, maintaining, and inputting information about the corresponding entity. These data models can also serve as an interface for data requested through various operations provided by module circuit 910. Each specific entity circuit can also include logic for facilitating operations between module circuits of circuit 910 and a database for storing information about the entity. In other words, such an entity circuit can act as middleware between the functionality of the framework and the data. In view of this middleware function, module circuits such as summary module circuits do not need to include sub-circuits for every entity in the system. When a module circuit is called for an entity, the module circuit can be integrated into each module via communication rather than actual circuits per entity circuit.

With respect to the example entity screen in FIG2 b , various functions provided by module circuitry 910 are invoked, such as the functions of the summary module circuitry. The functions of the summary module circuitry for retrieving information about the actor Tom Cruze communicate with a specific entity circuitry for the actor Tom Cruze. The specific entity circuitry may have information about Tom Cruze cached or permanently stored within its circuitry or may request information from a database, such as a database dedicated to the modular search framework server 116 (not shown in FIG1 ) and/or the content database 114 or the advertisement database 110.

Figure 10 shows a block diagram of example circuitry of a client device of an example system, such as any client device of the systems shown in Figures 1 and 13, that can provide various aspects of a modular search object framework. For example, Figure 10 shows a block diagram of example circuitry of a client device 1007 that can provide entity search results, non-entity search results, and search suggestions within a portion of a page view provided at least in part by the client side aspects of the framework. The circuitry within the client device 1007 can be part of and/or associated with a non-transitory medium that can be executed by a processor of the client device. The circuitry can include an input/output interface 1009 (e.g., input/output interface 1340 of Figure 13). The circuitry can also include client application circuitry 1001 (e.g., circuitry of client application 1326 of Figure 13). The circuitry can also include network communication circuitry 1011 (e.g., network interface 1330 of Figure 13).

The client application circuit 1001 may include a first circuit 1004 configured to receive a search query from a search query input field 1003 of a page view. In addition, the client application may include a circuit 1002 configured to display a search query input field. The search query may be input by a user via the search query input field 1003 and a user input device (e.g., a user input device of an input/output interface). For example, the input and output may be received via a touch screen 1005. The search query may include text, an image, a voice command, a gesture (e.g., a gesture from the user's eyes, head, torso, arm, hand, finger, or any combination thereof), or any combination thereof. Receipt of the search query may occur at a placeholder within a non-transitory computer-readable medium, such as a reserved memory location for a placeholder in a memory device of the client device 1007. The search query may be evidenced in the computer-readable medium by a change in the physical state of the placeholder within the medium.

The client application circuitry 1001 may also include a second circuitry 1006 configured to transmit the search query to a search server (e.g., the search engine server 106, the sponsored search server, and/or the modular search framework server 116 of FIG. 1 ) over a network (e.g., the network 120 ). Transmission of the search query may occur via a communication interface (e.g., the communication interface of the network communication circuitry 1011 ) embedded in or connected to the client device. The communication interface may transform the changing physical state of the medium representing the search query into any type of electromagnetic signal for communication across a computer network link. The communication interface may be communicatively coupled to the non-transitory computer-readable medium and the search server. The search server and the client device 1007 may be one or more computers connected over the network 120 . The aforementioned communicative couplings and other such couplings described herein may be implemented via various types of wired and wireless connections. Communication across the coupling may be via any form of electromagnetic signal, such as electrical signals, optical signals, or any combination thereof. Furthermore, in one example, the search server may be the search engine server 106, the sponsored search server, the modular search framework server 116, or any combination thereof.

The search query may be communicated with user information, wherein the user information includes demographic information associated with the user, psychographic information associated with the user, the user's real-time geographic location, or any combination thereof. The search query may be transmitted over a network that is part of a cloud computing environment. The search server may also be part of the cloud computing environment. The search server may be communicatively coupled to a content server, an advertising server, an analytics server, an account server, a sponsored search server, or any combination thereof (e.g., any one or more of the servers in FIG. 1 ). Any of these components may be part of the cloud computing environment.

The client application circuitry 1001 may also include a third circuitry 1008 configured to receive entity and non-entity search results, such as entity and non-entity sponsored search results, from a search server based on a search query. The circuitry may also receive search suggestions from the server. Additionally or alternatively, search suggestions may be generated by client circuitry (such as circuitry associated with the script and/or applet 1328). Receipt of search results may occur via a communication interface embedded in or connected to the client device (e.g., a communication interface of the network communication circuitry 1011). The communication interface may transform the electromagnetic signal representing the sponsored search into a changed physical state of a non-transitory computer-readable medium representing the search results.

Search results can be determined at the search server based on the search query. This determination can be accomplished by non-entity or entity sponsored search result determination factor circuitry and/or non-entity or entity non-sponsored search result determination factor circuitry hosted by the search server. Search results can also be determined based on user information. Search results can also be determined from data from a content server, an advertising server, an analytics server, an account server, a sponsored search server, or any combination thereof (e.g., any one or more of the servers of FIG. 1 ). Search results can include instructions associated with sub-GUIs that can extend from, overlap with, or both extend and overlap a set of corresponding search results, such as those shown in FIG. 2a, 2b, 8a, and 8b. The instructions associated with the sub-GUIs are hidden from the user's view, for example, in the form of web browser-readable and/or executable code.

The client application circuitry 1001 may also include fourth circuitry 1010 configured to display entity and/or non-entity search results (e.g., search results 502a-502f and 504a-504c in FIG. 5a ) on the page view. Where the search results are sponsored search results, the sponsored search results may be displayed within a portion of the page view dedicated to sponsored search results (e.g., advertisement portions 806b and 806c in FIG. 8a and FIG. 8b ). In examples where the results are sponsored results, the sponsored search results may also be displayed within a search result list that includes sponsored search results and non-sponsored search results (e.g., search result 502e in FIG. 5a ). In such examples, regardless of whether the results are sponsored or non-sponsored (not shown), the sponsored search results may be displayed first in the list of displayed search results. Additionally, the sponsored search results may be displayed adjacent to the non-sponsored search results.

The display of the search results on the page view can appear on the display device of the touch screen 1005 that has displayed the page view, wherein the display device is embedded in or connected to the client device 1007. For examples of the results of this function, see the results 502a-502f, 504a-504c and 254a-254d of Figures 5a and 5b, respectively. A graphics card or any other type of graphics processing device can convert the portion of the computer-readable medium representing the search results into an electromagnetic signal representing the sponsored search that can be transmitted to the display device. At this time, the signal is rendered into a visual display by the display device. Any of these technical functions can be implanted via the output device of the touch screen 1005 (e.g., the output device of the input/output interface 1009).

The client application circuit 1001 may also include a fifth circuit 1012 configured to receive a selection of a portion of the search results. When the selection is for an entity search result, such a selection may cause the display of the entity GUI and the sub-GUI. The receipt of the selection may occur at a placeholder within a non-transitory computer-readable medium, such as a reserved memory for a placeholder in a memory device of the client device 1007. The selection may be demonstrated in the computer-readable medium by a change in the physical state of the placeholder within the medium. The selection may be input by the user via an icon selection input field and a user input device (e.g., a user input device of the input/output interface 1009). The selection may occur by the user clicking, moving, or touching the search result. The selection may occur by tactile input, voice command, gesture (e.g., gesture from the user's eyes, head, torso, arm, hand, finger, or any combination thereof), or any combination thereof.

The client application circuit 1001 may also include a sixth circuit 1016 configured to display a GUI and/or sub-GUI associated with the search results (or search suggestions). The display of the sub-GUI may appear in the same page view. The user interface may be close to the selected search result icon. The user interface may be in the same part of the search results. The user interface may be adjacent to the search results. The user interface may be immediately below the search results. The user interface may be immediately above the search results. The user interface may be immediately to the side of the search results. The user interface may be immediately diagonally opposite the search results. The user interface may be within the list of search results so that the user interface appears below or above and above or below the search results, with the search results initially being below or above the search results. Search results that are initially below or above the search results may be immediately below or above the search results. The display of the GUI or sub-GUI may enable a search result that is immediately above or below another search result to move up or down according to the position of the GUI or sub-GUI.

The GUI or sub-GUI can present audio content, video content, text content, graphic content, tactile content or any other type of human-perceivable content, web page forms, video games, links to the second page view or any combination thereof. The GUI or sub-GUI can be displayed on all page views or on all page views. The GUI or sub-GUI can be displayed on most page views or on most page views. The sub-GUI can be displayed on most or all of the page portions containing search results or on most or all of the page portions containing search results. In some examples, the GUI and sub-GUI are displayed on a portion of the page view, and at least a portion of the GUI or sub-GUI is at least partially transparent. In other examples, when the GUI or sub-GUI is displayed, one or more portions except the user interface can be visually suppressed. Visual suppression can include blurring, reducing size, reducing brightness, reducing sharpness, mosaicing, filtering one or more colors, or any combination thereof.

Examples of GUIs and sub-GUIs and their transitions are shown in Figures 2a-8b. A graphics card or any other type of image processing device can convert portions of a computer-readable medium representing a GUI or sub-GUI into electromagnetic signals representing the GUI or sub-GUI that can be transmitted to a display device. At this point, the signals are rendered into a visual display by the display device. Any of these technical functions can be implemented via an output device (e.g., an output device of input/output interface 1009).

The client segment application circuit 1001 may also include a seventh circuit 1018 configured to receive user input from a user input field of the GUI or sub-GUI. The receipt of user input from the user input field of the GUI or sub-GUI may occur at a placeholder within the non-transitory computer-readable medium. In addition, the receipt of user input or any other receipt of user input herein may occur via various known ways of receiving user input (e.g., the ways described herein). For example, user input to the GUI or sub-GUI may be received and processed via a user input device (e.g., a user input device of the input/output interface 1009). The user input may include text, images, voice commands, gestures (e.g., gestures from the user's eyes, head, torso, arms, hands, fingers, or any combination thereof), or any combination thereof.

The user input field may include a text box having one or more lines for entering text, a check box, a radio button, a file selection control for uploading a file, a reset button, a submit button, a drop-down list, a scrollable list, or any combination thereof. The user input field may also include a selectable image, an animated image, a fixed image, or any combination thereof. The user input field may be displayed, based on the search query, demographic information associated with the user, psychographic information associated with the user, the user's real-time geographic location, or any combination thereof.

The client application circuit 1001 may further include an eighth circuit 1014 configured to initiate an action based on user input received from a user input field of the GUI or sub-GUI. The action may be performed by one or more computer components described herein, network components described herein, any other known computer hardware, any other known computer software, or any combination thereof. For example, an action that would typically occur on a client may be performed by a portion of the client device 1007. An action that would typically occur on a server may be performed by a portion of one of the servers described herein (e.g., the server described with respect to FIG. 1 ).

This action can comprise showing one or more GUIs or sub-GUIs, and it can comprise the following and be associated with the following: audio content, video content, text content, graphic content, tactile content or the human perceptible content of any other type, web page form, video game, user input field, to another GUI such as another entity or sub-GUI's link, the state of user input field (for example, the position of field, the size of field, the color of field, the brightness of field, the shape of field, or another type of the graphic composition of field or their any combination) change or their any other combination.This action can comprise submitting user input to server.Such submission can be used for business.Submission can be stored in database.In addition, this submission can be used to determine at least a portion of the display of GUI and sub-GUI (in other words, submission can be used as feedback).

Figure 11a illustrates example operations 1100a of example circuitry of an example system providing various aspects of a modular search object framework. In one example, the operations may be performed by circuitry of a client device, such as any of the client devices of the system shown in Figure 1. At 1102, operation 1100a may include receiving a search query from a search field displayed on a page view on a client device (e.g., any of the client devices shown in Figures 1, 10, and 13). The receiving at 1102 may occur at a user interface circuit (e.g., interface circuitry of a user input interface of input/output interface 1109 in Figure 10 or input/output interface 1340 in Figure 13). At 1104, operation 1100a may also include transmitting the search query to a framework server (e.g., modular search framework server 116). The transmission at 1104 may occur over a network link (e.g., a network link in network 120). The communication at 1104 may be initiated by network communication circuitry (e.g., network communication circuitry 1011 or network interface 1330) that is communicatively coupled to the user interface circuitry. At 1106, operation 1100a may further include receiving entity search results, non-entity search results, search suggestions, or any combination thereof from the framework server based on the search query. The receiving at 1106 may occur at the network communication circuit. At 1108, operation 1100a may further include outputting the entity search results, non-entity search results, search suggestions, or any combination thereof on the page view.

In one example, the output at 1108 may include providing a graphical distinction between entity and non-entity search results. Additionally, the output at 1108 may include providing a graphical distinction between entity search results and search suggestions. The distinction may also occur between any type of search results and search suggestions. The distinction may also occur through differences in audio input or some other form of perceptible input. The distinction between entity search results, non-entity search results, and search suggestions may occur through a specific order of these items when displayed in a list. For example, entity search results may appear first in the list, followed by non-entity search results, and then search suggestions. The distinction may occur by displaying a different background for one type of item than for other types of listed items. The difference in background may be color. Additionally, for example, the background for one type of item may be derived from a photograph or description associated with the corresponding entity and may appear in multiple colors, while the background for other types of listed items may appear as a single color or a range of single colors. In other words, the distinction may occur by displaying different graphical parameters for one type of item than for other types of listed items.

Additionally, at 1110, operation 110a may include receiving a selection of an entity search result, a non-entity search result, a search suggestion, or any combination thereof. Upon receiving a selection at 1110, circuitry of the client device and/or server may determine at 1111 whether the selection is on an entity search result. When an entity search result is selected, operation 1100a may continue outputting an interactive entity portion of the page view via the user interface circuitry. The portion may then be displayed on the page view. The interactive portion may include a plurality of movable visual objects that are movable within the interactive entity portion. When a non-entity search result is selected or a search suggestion is selected, operation 1100b continues outputting the corresponding non-entity search result on the page view at 1112. In one example, outputting a result after a user selects a search suggestion may also result in an entity search result.

FIG11 b illustrates example operations 1100 b of example circuitry of an example system that can provide various aspects of a modular search object framework. In one example, the operations can be performed by circuitry of a server, such as the modular framework server 116 shown in FIG1 . At 1122 , operation 1100 b can include receiving a search query from a client device (e.g., any of the client devices of FIG1 , FIG10 , and FIG13 ). Receiving the search query at 1122 can occur over a network communication circuit (e.g., the network communication circuitry in the network interface 1430 shown in FIG14 ). Additionally, the transmitted query received at 1122 can occur over a network, such as the network 120 in FIG1 .

At 1124, operation 1100b may also include executing the search query on the entity search database. The execution at 1124 may occur via search engine circuitry (e.g., via circuitry included within framework circuitry 908 of FIG. 9 and/or circuitry included within search engine server 106 and/or modular search framework server 116). The entity search database may be communicatively coupled to such circuitry and may include at least a portion of an advertisement database, a content database, an account database, an analytics database 119, a database tightly coupled to modular search framework server 116, or any combination thereof. The search engine circuitry may also be communicatively coupled to network communication circuitry.

At 1126, operation 1100b may further include identifying an entity indicator in the search query based on the execution of the search query on the entity search database. The identification at 1126 may be performed by search engine circuitry and may also be part of the execution of the query on the entity search database. When the entity indicator is identified, the search engine circuitry may identify entity search results based on the entity indicator. At 1128, operation 1100b may further include identifying additional query parts in addition to the entity indicator in the search query. The identification of the additional query parts may be based on the execution of the search query on the entity search database. The identification at 1128 may be performed by search engine circuitry and may also be part of the execution of the query on the entity search database.

When an additional query portion is identified at 1128, operation 1100b may further include executing the additional query portion on an entity search database, a non-entity search database, or both, related to the entity search results at 1130. The non-entity search may be communicatively coupled to the search engine circuitry and may include at least a portion of an advertising database, a content database, an account database, an analytics database 119, a database tightly coupled to the modular search framework server 116, or any combination thereof. In one example, when an additional query portion is identified at 1128, the search engine circuitry may further be configured to interpret the search query as a question. When the query is interpreted as a question, one or more additional search results may be provided as one or more answers to the question. For example, in FIG6b , the query input at query box 212 is "Katie Bolmes Favorite Color." This may be interpreted as a question such as "What is Katie Bolmes' favorite color?" As shown in FIG6b , the answer to the question has been displayed along with the entity search results.

At 1132, operation 1100b may also include identifying one or more additional search results in the entity search results. The identification of the one or more additional search results in the entity search results may be based on executing an additional query portion on an entity search database, a non-entity search database, or both. The identification at 1132 may be performed by search engine circuitry and may also be part of executing a query on the entity search database, the non-entity search database, or both. The identification of the one or more additional search results at 1132 may occur by the search engine circuitry predicting that the one or more search results, or the search query that the user submitted, are most likely intended to be submitted and received. In such an example, the search engine circuitry may include, or may be communicatively coupled to, for example, analysis circuitry of analysis server 118, circuitry for analyzing data 119, circuitry of modular search framework server 116 (e.g., analysis circuitry of framework circuitry 908 or 1426), circuitry of a framework database, client-side analysis circuitry (e.g., circuitry of script and/or applet 1328), or any combination thereof. In other words, the search engine circuitry may also be configured to determine whether the one or more additional search results are present in the entity search results and may then act accordingly.

When one or more additional search results are identified in the entity search results at 1132, operation 1100b may further include highlighting the one or more additional search results in the entity search results at 1134. Otherwise, when one or more additional search results are not identified in the entity search results at 1132, operation 1100b may further include adding the one or more additional search results to the entity search results at 1136 and then performing the highlighting at 1134.

Emphasizing the one or more additional search results in the entity search results can be accomplished by adding a visual representation of the one or more additional search results at a predetermined location in a first graphical user interface (GUI) to appear after a user selects the entity search result on a client device. The predetermined location can be a variable location in the first GUI relative to other visual information. Alternatively, the predetermined location can be fixed. As shown in FIG6 b , the predetermined location 604 can be above entity-specific text in the first GUI in addition to the displayed title of the first GUI.

Alternatively or additionally, emphasis can be placed on one or more additional search results within the entity search results by including a visual representation of the one or more additional search results in a foremost portion of the first GUI so as to appear after a user selects the entity search result on a client device. The foremost portion can be provided by causing the foremost portion to appear closer to a user viewing the first GUI than other portions. Furthermore, the foremost portion can cover at least one other portion of the first GUI in addition to covering a background portion and can be uncovered by any portion of the first GUI. The foremost portion can also be sharper than at least most other portions of the first GUI.

Additionally, emphasizing the one or more additional search results to cause the entity search result to appear can be accomplished by visually displaying the one or more additional search results in a manner that contrasts more with background elements of the first GUI than at least most other visual objects of the first GUI. In one such example, the first GUI can be an initial GUI that appears after a user selects the entity search result on a client device.

Emphasizing one or more additional search results within the entity search results can also be accomplished by enlarging the visual presentation of the one or more additional search results relative to all other visual objects in the first GUI, such that they appear after a user selects the entity search result on the client device. Additionally, emphasizing one or more additional search results within the entity search results can be accomplished by reducing the size of at least a majority of visual objects in the first GUI, such that they appear after a user selects the entity search result on the client device. At least a majority of the visual objects can exclude background objects of the first GUI and the visual presentation of the one or more additional search results.

Additionally, highlighting one or more additional search results in the entity search results can be accomplished by audio output of the one or more additional search results after the user selects the entity search result on the client device. In one example, the audio output can occur when a first GUI that appears after the user selects the entity search result on the client device is output.

Operation 1100b may also include transmitting the entity search results to the client device over the network at 1138. Transmission of the entity search results to the client device may be initiated via the network communication circuitry. When it is determined at 1128 that there are no additional query parts beyond the entity indicator, the network communication circuitry may transmit the entity search results to the client device without highlighting one or more additional results.

Returning to the identification at 1126 of the reference entity indicator, when the entity is not identified, operation 1100b may further include executing a query on a non-entity search database at 1140 and transmitting one or more non-entity search results over a network to a client device at 1142. Execution of the search query at 1140 may be performed by search engine circuitry and communication of the one or more non-entity search results at 1142 may be initiated by network communication circuitry. Additionally, in one example, execution of the search query at 1140 and communication of the one or more non-entity search results at 1142 may occur regardless of whether the entity is identified.

Figure 12 illustrates example operations 1200 of example circuitry of an example system that can provide aspects of a modular search object framework. In one example, the operations can be performed by circuitry of a client device, such as any client device of the system shown in Figure 1. At 1202, operation 1200 can include operations 1102-1110 of Figure 11a. Operation 1200 can also include, for example, identifying entity indicators in a search query based on execution of a search query on an entity search database. At 1204, this can be performed by operations similar to the operations at 1126 of Figure 11b. Additionally or alternatively, at least a portion of this identification can occur at the client circuitry of the client device. Operation 1200 can also include identifying additional query portions in addition to the entity indicators in the search query, for example, at 1206 by operations similar to the operations at 1128 of Figure 11b. Additionally, at least a portion of this identification can occur at the client circuitry of the client device.

When an entity indicator is identified at 1204, operation 1200 may also include performing operations similar to operation 1130 of Figure 11b at 1208. However, when an additional query portion is identified at 1206, operation 1100b may also include performing operations similar to operation 1130 of Figure 11b at 1208. In addition, at least a portion of these operations may occur at the client circuitry of the client device. Alternatively, and as shown in Figure 12, when an entity in the query is identified at 1204 and an additional query portion is identified at 1206, the circuitry of the client device and/or server may predict the user intent behind the query using the additional query portion at 1208. At operation 1210, the client circuitry may proceed to output the corresponding interactive entity portion on the page view based on the user's predicted intent related to the user's search. In the event that the entity cannot be identified, operation 1200 may continue with operation 1112 of FIG. 11 a at 1205 ; and in the event that the entity is identified but the additional query portion is not identified, operation 1200 may continue with operation 1114 at 1207 .

Figures 13 and 14 are block diagrams of example electronic devices that can implement aspects of and are related to example systems that can provide a modular search object framework. For example, Figure 13 illustrates an example of the audience client device 124 of Figure 1; and Figure 14 illustrates an example of the search engine server 106 of Figure 1, the modular search framework server 116, or an example server that combines features of both servers.

FIG13 is a block diagram of an example electronic device 1300 that can implement client aspects of the framework and is associated with various aspects of the framework. For example, electronic device 1300 can be any client device described with respect to FIG1 and FIG10 , such as audience client device 124. Electronic device 1300 can include a central processing unit (CPU) 1302, memory 1310, a power supply 1306, and input/output components such as a network interface 1330 and an input/output interface 1340, as well as a communication bus 1304 that connects the aforementioned elements of the electronic device. Network interface 1330 can include a receiver and a transmitter (or transceiver), as well as an antenna for wireless communication. CPU 1302 can be any type of data processing device, such as a central processing unit (CPU). Furthermore, for example, CPU 1302 can be central processing logic; central processing logic can include hardware (e.g., circuitry and/or a microprocessor), firmware, software, and/or a combination of each to perform functions or actions, and/or to cause functions or actions from another component. In addition, the central processing logic may include a software controlled microprocessor, discrete logic such as an application specific integrated circuit (ASIC), a programmable/programmed logic device, a memory device containing instructions, etc., or combinational logic embedded in hardware. In addition, the logic may also be fully embodied as software.

Memory 1310, which may include random access memory (RAM) 1312 or read-only memory (ROM) 1314, may be enabled by memory devices such as primary (directly accessible by the CPU) and/or secondary (indirectly accessible by the CPU) storage devices (e.g., flash memory, magnetic disks, optical disks).

RAM 1312 may store data and instructions defining an operating system 1321, data storage 1324, and applications 1322, including client applications 1326 and scripts and/or applets 1328 (e.g., scripts and/or applets suitable for framework client functionality). Applications 1322 may include hardware (e.g., circuitry and/or microprocessors), firmware, software, or any combination thereof. Example content provided by applications such as client application 1326 may include text, images, audio, video, etc., which may be processed in the form of physical signals such as electrical signals or may be stored in memory as physical states, for example.

ROM 1314 may include a basic input/output system (BIOS) 1315 for electronic device 1300. Power supply 1306 contains power supply components and facilitates the supply and management of power to electronic device 1300. Input/output components may include various types of interfaces for facilitating communication between components of electronic device 1300, components of external devices (e.g., components of other devices of information system 100), and end users. For example, such components may include a network card, which is an integrated receiver, transmitter, and I/O interface such as input/output interface 1340. For example, a network card may facilitate wired or wireless communication with other devices on a network. In the case of wireless communication, an antenna may facilitate such communication. I/O components such as I/O interface 1340 may include user interfaces such as a monitor, keyboard, touch screen, microphone, and speaker. In addition, some I/O components such as I/O interface 1340 and bus 1304 may facilitate communication between components of electronic device 1300 and facilitate processing performed by CPU 1302.

Figure 14 is a block diagram of an example electronic device 1400 that can implement the server-side aspects of the framework and is related to the example aspects of the framework. For example, the electronic device 1400 can be a device that can implement the modular search framework server 116 of Figure 1. The electronic device 1400 can include a CPU 1402, a memory 1410, a power supply 1406, and input/output components such as a network interface 1430 and an input/output interface 1440, as well as a communication bus 1404 connecting the above-mentioned elements of the electronic device. The network interface 1430 can include a receiver and a transmitter (or transceiver), as well as an antenna for wireless communication. The CPU 1402 can be any type of data processing device such as a central processing unit (CPU). In addition, for example, the CPU 1402 can be a central processing logic.

Memory 1410, which may include random access memory (RAM) 1412 or read-only memory (ROM) 1414, may be enabled by a memory device. RAM 1412 may store data and instructions defining an operating system 1421, data storage 1424, and applications 1422. Applications 1422 may include a modular search object framework 1426 (e.g., framework circuit 908 shown in FIG. 9 ), which may include module circuits 1427a (e.g., module circuit 910) and entity circuits 1427b (e.g., entity circuit 912). Applications 1422 may include hardware (e.g., circuits and/or microprocessors), firmware, software, or any combination thereof. ROM 1414 may include a basic input/output system (BIOS) 1415 for electronic device 1400.

The power supply 1406 includes a power supply assembly and facilitates the supply and management of power to the electronic device 1400. The input/output assembly may include interfaces for facilitating communication between components of the electronic device 1400, components of external devices (e.g., components of other devices of the information system 100), and end users. For example, such an assembly may include a network card that is an integration of a receiver, a transmitter, and an I/O interface such as the input/output interface 1440. I/O assemblies such as the I/O interface 1440 may include user interfaces such as a monitor, a keyboard, a touch screen, a microphone, and a speaker. Additionally, some I/O assemblies such as the I/O interface 1440 and the bus 1404 may facilitate communication between components of the electronic device 1400 and may facilitate processing performed by the CPU 1402.

Claims (15)

1. A system executable by processor circuitry and stored in a non-transitory medium, comprising: The network communication circuit is configured as follows: The search query is transmitted to the framework server, the transmission occurring over a network link; and Receive entity search results from the framework server according to the search query; and User interface circuitry, communicatively coupled to the network communication circuitry, wherein the user interface circuitry is configured to: Receive the search query from the search field on the page view; Receive search suggestions based on the search query; Receive non-entity search results based on the search query; The entity search results are output as a list on the page view, or as cards in the entity tray. The search suggestions will be output to the list; and The non-entity search results are output in the list as cards in the entity tray, wherein the output of the non-entity search results is graphically distinguishable from the output of the entity search results. 2. The system of claim 1, wherein the user interface circuitry is further configured to receive a selection of the entity search result. 3. The system of claim 2, wherein the user interface circuit is further configured to: output an interactive entity portion on the page view based on the entity search result, wherein the interactive portion includes a plurality of movable visual objects movable within the interactive entity portion. 4. The system of claim 1, wherein the user interface circuitry is further configured to receive a selection of the search suggestion. 5. The system of claim 4, wherein the user interface circuit is further configured to output at least non-entity search results based on the search suggestions. 6. The system of claim 1, wherein the output of the search suggestions and the output of the entity search results are graphically distinguishable. 7. A method for searching, comprising: The user interface circuit receives the search query from the search field on the page view. The search query is transmitted to the framework server via a network communication circuit that is communicatively coupled to the user interface circuit, the transmission occurring on a network link; Based on the search query, entity search results are received from the framework server via the network communication circuit; Based on the search query, search suggestions and non-entity search results are received through the user interface circuit; The entity search results are output to a list on the page view via the user interface circuit, as cards in the entity tray. The search suggestions are output to the list via the user interface circuit; and The non-physical search results are output to the list via the user interface circuit as cards in the physical tray, wherein the output of the non-physical search results is graphically distinguishable from the output of the physical search results. 8. The method of claim 7, wherein the output of the search suggestions and the output of the entity search results are graphically distinguishable. 9. The method of claim 8, wherein the output of the search suggestions is graphically distinguishable from the output of the entity search results by means of the ranking of the search suggestions relative to the entity search results. 10. The method of claim 8, wherein the output of the search suggestion is graphically distinguishable from the output of the entity search result by displaying a background different from that of the entity search result. 11. The method of claim 10, wherein the difference in the background is color. 12. The method of claim 10, wherein the background of the entity search result is derived from a photograph or illustration related to the corresponding entity and appears to have multiple colors, and wherein the background of the search suggestion appears to be monochrome. 13. The method of claim 7, wherein the output of the non-entity search results is graphically distinguishable from the output of the entity search results by the sorting of the non-entity search results relative to the entity search results. 14. The method of claim 7, wherein the background of the entity search result is derived from a photograph or illustration associated with the corresponding entity and appears to have multiple colors, and wherein the background of the non-entity search result appears to be a single color. 15. A system for searching, comprising: A device for receiving search queries from a search field on a page view; A means for transmitting the search query to the framework server; A means for receiving entity search results from the framework server based on the search query; A means for receiving search suggestions and non-entity search results based on the search query; A means for outputting the entity search results to a list on the page view as cards in an entity tray; A means for outputting the search suggestions to the list; and A means for outputting the non-entity search results to the list as cards in the entity tray, wherein the output of the non-entity search results is graphically distinguishable from the output of the entity search results.