Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
  • G06F16/33—Querying
  • G06F16/335—Filtering based on additional data, e.g. user or group profiles
  • G06F16/337—Profile generation, learning or modification
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/953—Querying, e.g. by the use of web search engines
  • G06F16/9535—Search customisation based on user profiles and personalisation

Definitions

• the present invention relates generally to search queries over a network and user configuration of feeds and clusters in conjunction with a mobile device.
• screen real estate is at a minimum. Navigation of any presented information may be dependent upon, or subject to the quirks of, the particular mobile device.
• the user is not in an environment conducive to casual exploration of the World Wide Web. In fact, the user may be in a changing environment that itself demands the lion's share of the user's attention. Thus the tailoring of search engine results and content consumption to the mobile experience is of prime importance to the user.
• some mobile device users may desire delivery of content in a more automatic manner, possibly with the content tailored to a unique set of interests, such as hobbies or social network groups. Even if a user has the time, energy, and technical skills necessary to manually configure a mobile device, the user will likely be forced to remain content to receive a narrow set of pre-defined information sources, such as news headlines, weather and sports. Yet other users may desire delivery of particular content depending on the current user environment.
• advertisers desire to provide information that is tailored to each user and enhances the user experience.
• An advertiser can approximate this goal through delivery of advertising material as part of delivery of search engine results, because of the likely correlation between the user search terms and the user's actual interests.
• advertisers typically have limited ability to reach a target audience that is likely on the move and in need of information relevant to the environment they are in or going to.
• FIG. 1 is a system diagram of one embodiment of an environment in which the invention may be practiced
• FIG. 2 illustrates a sample search and clustered search results on a mobile device
• FIG. 3 illustrates the clustering achieved through the use of metadata wrappers applied in a social networking context
• FIG. 4 illustrates the generation of results based on a search yielding no named cluster results
• FIG. 5 illustrates a mobile user search system performing a federated query to multiple data sources in which third parties provide plug in modules to interpret their data into a format usable by the search;
• FIG. 6 illustrates a sample framework for the plug-ins shown in FIG. 5;
• FIG. 7 illustrates a schematic of an Add Anything Engine
• FIG. 8 illustrates a schematic of a Mobile Homepage Targeting Engine
• FIG. 9 illustrates a portion of a sample use of the Add Anything Engine
• FIG. 10 illustrates a portion of a sample use of the Add Anything Engine
• FIG. 11 illustrates a portion of a sample use of the Add Anything Engine
• FIG. 12 illustrates a complete screen shot (with portions omitted) of a mobile device resulting from the performance operations illustrated in FIGS. 9-11;
• FIG. 13 illustrates information associated with the entity "Boston Red Sox"
• FIG. 14 illustrates user configuration screens used in conjunction with various embodiments of the invention
• FIG. 15 illustrates a subset of the oneSearch entity types organized by hierarchical type-subtype relations
• FIG. 16 is a block diagram of a computer system on which embodiments of the invention may be implemented.
• a content object may be any form or format of content that is consumable by users such as, but not limited to, any one or more of the following: text, numerical data, images, animation, audio, video or any combination thereof including content encountered as search results, through browsing or from communications with others through voice, email, text, image, animation, gesture, audio or video.
• Content may come from any data processing source or device.
• contextual information related to the user's current activity is derived from the mobile device or other sources, and passed to a search engine as metadata in order to reorder generic search results into a personalized result set including a system and method for personalizing mobile user content requests, i.e., searches or dynamic page assembly requests by augmenting a mobile user's input with a first set of metadata derived from the context of the input, including location information to match the request and rank or re-rank the results
• one or more content objects are displayed on a mobile device. For each content object selected by a user, one or more entities or entity types are determined to correlate to the selected content object. Based at least in part on the determined entity or entity type, an information feed is created. The user may incorporate the information feed into the user's home page or device and automatically receive updates based on the web page or information corresponding to the content object, entity or associated information sources.
• a set of search results is displayed on a mobile device.
• an entity or entity type is determined for the selected search result.
• an information feed is created. The user may incorporate the information feed into the user's home page or device and automatically receive updates based on the web page or information corresponding to the search result or information resource when users annotate results to cause the future inclusion of that source, result, or search type in their mobile "home page.”
• a set of users are ranked against a selected advertiser or product. From the set of users, candidate targets are predicted for a set of one or more advertisers and conditions, based at least in part on the context of the user, the advertisement copy and a pre-selected time for refining, qualifying and scoring users for an advertiser based upon the actual hierarchical content configurations of the user's mobile home page and the interaction and usage data of the user with the home page over time.
• a user's content consumption and communications on the user's mobile device(s), along with (2) the preferences and activities that the user performs in configuring, consuming, interacting with, and sharing content, as well as (3) the contexts in which and the people with whom the user performs these actions, provide information to advertisers about the user's interests and intentions.
• FIG. 1 illustrates a high-level schematic of a mobile device having a web browser, with the mobile device in communication with a server.
• the server is connected to a network and includes a personalized content engine configured to aggregate and display disparate types and sources of content, a search engine that is configured to perform a search of the network and a user data tracking engine for instrumenting and recording user's behavior.
• a personalized content engine configured to aggregate and display disparate types and sources of content
• search engine that is configured to perform a search of the network
• a user data tracking engine for instrumenting and recording user's behavior.
• networked system 100 includes a mobile device 110 in communication with a server 130 using network 104.
• the network 104 is the Internet, but it could also be a non-public network such as a telecommunications carrier.
• Server 130 includes a set of one or more search and data applications 134.
• Search and data applications 134 include personalized content engine 140, configured to generate and maintain a "home page" of personalized content types and sources in one centralized display, and search engine 150 configured to perform searches of data accessible via the network and the Internet.
• personalized content engine 140 corresponds to is the Yahoo! onePlace mobile home page and search engine 150 is configured to search a private network of user data such as Yahoo! or Google.
• Search and data applications 134 also include one or more of the following modules: User Data Store (UDS) 152, Mobile Search Refine Manager 154, Search Module 156, and Search Clustering Module 158. These particular naming conventions are not necessary from any technical standpoint to understand the methods and systems disclosed herein, but are provided for the convenience of the reader. These modules will not be described in a serial fashion, but will be introduced as certain features and embodiments are illustrated. Although each module is described separately from search engine 150, each module could be incorporated into search engine 150.
• Mobile device 110 may include a mobile telephone, gaming or reading device or another wireless device (such as Wi-Fi or Bluetooth, for example) that provides access to one or more interconnected networks 104.
• Mobile device 110 includes an interactive application 120 that permits browsing of content and data using display 126.
• an interactive application 120 that permits browsing of content and data using display 126.
• a social relations and associations graph may be constructed from nearly any activity, from dating to professional organizations, with some networks not focused on a particular activity, but instead a set of personal or familial relationships.
• a description representing an individual's current activities may include some or all of the factors relating to the "Where,” the “When,” the “Who,” and the “What,” which provide a continuous path/state data stream on the user and provide exact context for any user-originating requests such as search or loading a mobile home page.
• these factors are themselves metadata called for example a user's W4 metadata including one or more of spatial metadata, temporal metadata, social metadata, object metadata and/or topical metadata.
• each of the (1) operating environment, (2) mobile client environment, (3) server environment and (4) operation of mobile search queries in conjunction with location modifiers can be further extended with reference to metadata wrappers, including user W4 metadata, placed around data that is exchanged among mobile clients, servers, and (optionally) administrators or third party service providers.
• User W4 metadata includes contextual metadata which relate to the "Where,” the "When,” the "Who,” and/or the "What" of any given event, e.g., a text message or voice communication.
• W4 metadata may include information which is spatial or geographic in nature (i.e., the "Where"), temporal (i.e., the "When"), social (i.e., the "Who"), and/or related to physical objects or topical interests (i.e., the "What”).
• the relevance of at least some of these aspects may be determined by analyzing the similarity of these aspects among user groups, as well as patterns of these similarities within and among the respective spatial, temporal, social, and topical aspects.
• the context provided by user W4 metadata aids in the disambiguation of mobile search queries, which in turn permits improved clustering of search terms and search results.
• a user enters the query "apple.”
• the term "apple” can be mapped to a number of abstract ideas, real world objects, and digital objects and media. Collectively, these things are referred to herein as "entities.”
• the disambiguation is performed on the string "apple” to determine at least some of the possible entities "apple” might represent, e.g., the company, the fruit, the record label, etc., each of which may then be mapped to one or more result types.
• disambiguation can preference recent real- world or online behavior data to preference certain results. For example, if the user was in the Apple Mac Store yesterday and made a purchase, then the disambiguation might preference local receipts or product information pages the user recently accessed in conjunction with the user's prior purchase or research.
• the different result types might include geographic results (e.g., company or store locations), stock price, news stories (e.g., text and video), as well as conventional web and mobile web links.
• geographic results e.g., company or store locations
• stock price e.g., stock price
• news stories e.g., text and video
• clusters of result types based on the entity or entities identified in the disambiguation phase and their respective mappings to result types may be rendered or manipulated. Additional information regarding disambiguation of search queries can be found in Application Ser. No. 11/651,102, entitled "Clustered Search Processing.”
• FIG. 15 represents a subset of the oneSearch entity types organized by hierarchical type-subtype relations. Additional relations among entities and entity types may include numeric and symbolic relationships, as well as composite entity types such as "events" which link other entity types such as places, times, people, etc. [0049] In FIG. 15, for example, row 1510 references the entity “Apple Computer” (corresponding to the discussion above) and row 1520 references the entity “Pizza Restaurant.”
• Entities may also exist in multiple categories.
• the television series Lost could exist in the TV shows category of Entertainment Information Objects yet also be referenced in the Actor category of Entertainment People.
• Pizza could be Business Listing, Venue, Place as well as a recipe entry in Wikipedia, Reference, or Information Object.
• UDS 152 may include a database, text, spreadsheet, folder, file, or the like, and may be configured to maintain and store social relations and associations information as collected from network 104 as well as associated networks or user data sources. For example, a four dimensional map of a mobile device may be used as a proxy for the user's historical and current location, state and association with other nearby or related users.
• social relations and associations information stored in UDS 152 for a mobile user includes one or more of the following: (1) the user's identification information for social networking websites to which the user belongs, such as MySpace, Facebook, or Linkedln; (2) contact information maintained by the user, such as for voice contact, electronic mail, instant messaging, and text messaging; (3) membership groups to which the user belongs; (4) subscriber information of individuals that subscribe to user- created content, such as subscribers to the user's Flickr account or the user's blog and (5) any other accessible source of data on the user's location, association, actions, interests or transactions.
• social relations and associations information stored in UDS 152 for a mobile user includes one or more of the following: (1) the user's identification information for social networking websites to which the user belongs, such as MySpace, Facebook, or Linkedln; (2) contact information maintained by the user, such as for voice contact, electronic mail, instant messaging, and text messaging; (3) membership groups to which the user belongs; (4) subscriber information of individuals that subscribe to user- created content, such as subscribers to the user's
• social relations and associations information stored in UDS 152 for a mobile user includes electronic communications sent or received by the mobile user, such as electronic mail, instant messaging, and text messaging, while other embodiments combine information from multiple devices, mobile and stationary to include all known data, communications and transactions for the user.
• location information based both on a user's actual and past path data as well as on a user's physical residence(s), account registration information, locations of interests the user has implicitly or explicitly shared with the system, or the like, may also be stored within UDS 152.
• Such information may indicate that the user resides in a particular town, neighborhood, city, or the like, within a particular county, state, country, or the like, or is interested in a given location (e.g. venue, district, city, region, etc.), or the like.
• location information may also be configured and arranged, in one embodiment, in a hierarchical relationship.
• mobile status information that is related to the user may also be stored within UDS 152.
• Such mobile status information may include one or more of following: (1) the name, operating system, and CPU of mobile device 110; (2) the current status, location and/or usage history of mobile device 110, such as when and how long it has been powered on and accessed as well as to which cell towers or network nodes it has been communicatively connected with; (3) status information of applications 242 loaded on or currently operating on mobile device 110, such as information related interactive application 120; (4) contents of data storage of mobile device 110; and (5) information such as coordinate history from GPS of mobile device 110, from which a user's mobile status (such as that the user is located in a slow-moving transportation device on a particular freeway) may be derived.
• Usage history includes both active interaction data created by the user's actions, as well as passive data such as location of the user, proximity to known landmarks or Points of Interest (POI), and association other co-present users, devices, networks, vehicles or appliances.
• POI Points
• social networking information may be obtained once a user has provided account access to the user's social network or electronic mail accounts.
• social relations and associations information may be obtained indirectly through monitoring various movements, actions and interactions of a user. Interactions may be monitored though use of a browser toolbar activated by the user, in which some or all data sent to mobile device 110 is forwarded to UDS 152 as well as any other known method of instrumenting a mobile device to track user interaction including orientation, biometric and motion sensing.
• the implicit social relations and associations data and/or contact information may be extracted based on data from the users' respective devices, environmental sensors or data feeds and/or the content within a message between the user and another user whether or not they are both members of an explicit social network.
• Information such as social networking information, communications information, location information, and mobile path or status information, is stored within UDS 152, and may be passed with other data as a "metadata wrapper". As described below, a metadata wrapper may provide contextual information or content information to the data in which it accompanies.
• MSRM Mobile Search Refine Manager
• MSRM 154 is configured to receive the search query from a user, parse the search query into one or more primary search terms, and provide contextual modifiers based upon information regarding the user stored within UDS 152. Additional features of MSRM 154, including processing of contextual and concept-based searches, are described in Application Ser. No. 11/651,102, entitled “Clustered Search Processing.”
• contextual modifiers are provided in a metadata wrapper passed to MSRM 154 from mobile device 110; for example, the metadata wrapper may comprise data accompanying or part of a search query sent from mobile device 110.
• contextual modifiers are provided to MSRM 154 by UDS 152.
• MSRM 154 identifies any concept-specific data sources to be searched. One embodiment of a method in which third-parties may provide customizable data sources will be described later with respect to FIGS. 5-6. [0065] Using the information stored in UDS 152, MSRM 154 then fashions a modified search query to be processed by Search Module 156, along with an indication of any concept-specific data sources to be searched.
• Search results provided by Search Module 156 may be clustered into groups, and optionally ranked, as disclosed in Application Ser. No. 11/651,102, entitled "Clustered Search Processing.”
• search results from Search Module 156 are then passed to Search Clustering Module 158.
• metadata passed to Search Module 156 is also passed to Search Clustering Module 158.
• search results as determined with respect to mobile user metadata may also be modified based on metadata derived from one or both of concept- specific and content-specific data sources. The corresponding search results may be clustered by source, terms, concept or content.
• Metadata identified by one or both UDS 152 and MSRM 154 may be matched to search results based on a matching concept-specific data source.
• search results are combined with other known data sources to create a "virtual cluster" that may be presented to the user in the same or a similar manner in which actual clustered results are presented to the user.
• concepts identified by Search Clustering Module 158 used to cluster results are attached to the results as metadata.
• the identified concepts are used to determine a result type or relative rank based on the entity or entities identified in the disambiguation phase.
• metadata representing the user's mobile status information may be used to construct the layout of search results appearing on display 126 of mobile device 100.
• FIGS. 2-4 displaying sample searches and search results on a mobile device.
• the mobile user performs a simple search using the term "sushi.”
• Previously obtained metadata such as the user's location has been captured and is displayed below the search box; in this example, the user is located "near
• This location metadata permits the identification and display of nearby businesses, such as restaurants, identified as relevant to the search term.
• the restaurants form a cluster of particular instances of the abstract entity type "restaurant.”
• the metadata wrapper can be employed by other content providers, such as Yelp, Zagat, and OpenTable, and shown under the heading "More business results" in panel 210. These business results could be generated based on a combination of the mobile user's location, the search term, and an abstract entity type such as "restaurant,” and pushed to the user. [0078] In panel 220, the user has selected the result for "Sushi Roku in the Forum
• the mobile device's display is configured to display links to other related information, such as a map, user reviews, and more tools, via the link to "Business details.”
• Panels 231 , 232, and 233 display the links available from the landing page for
• FIG. 3 illustrates the clustering achieved through the use of metadata wrappers applied in a social networking context.
• Panel 310 illustrates a search performed by the user for a person named "Will Decker.” This search may again being performed with reference to the user's current location, as shown in the location information ("near 3000
• the search generates a cluster of profile information using the abstract class "Contact” with regard to three applications,
• each of the instances of the "Contact” class type possess properties that can be used to further refine the results and aid the user in locating the individual named "Will Decker” that he or she actually knows.
• panel 320 the user has selected the profiles found in Facebook and views a summary of the various people named "Will Decker” (or a slight variant thereof) along with additional information, such as a thumbnail photo and an encapsulated summary about the individual, such as "Berkeley Alum • UChicago Alum,” corresponding to the class "Overview.”
• panel 330 the user has navigated to a representation of Facebook photo gallery for a particular instance of "Will Decker.” Metadata wrappers including photograph information may be applied by the API framework, and combined with information regarding the mobile device physical features, to present the various
• FIG. 4 illustrates the generation of results based on a search yielding no named cluster results, in which the user is presented with one or more unnamed, virtual clusters, which themselves may comprise one or more third-party open abstracts.
• a mobile user enters the search term "Audi tt.” While none of the search results yield a named cluster, a virtual cluster entitled "2008 Audi TT" is created using content supplied from MotorTrend and Wikipedia conforming to the open abstracts model.
• the user has selected the MotorTrend Research icon and is presented with a landing page assembled from data and metadata that may be (1) supplied from results obtained from general data sources, or (2) supplied from a MotorTrend API plug-in.
• FIG. 5 illustrates a mobile search system 500 performing a federated query to multiple data sources in which third parties provide plug in modules to interpret their data into a format usable by the search or personalized content processes.
• the search retrieves data (and associated metadata) in data stores 511, 512, 513 that comprise a "Content Index.” Data is passed to the Content Index from content plug-ins 521-524 described below with reference to FIG. 6. Results in mobile search system 500 are also pulled directly from content plug in 526.
• Each of plug-ins 521-525 either pull data from, or are pushed data by, content sources 531-536.
• Content sources may comprise application program interfaces (APIs) and/or content feeds.
• results in mobile search system 500 are also pulled directly by content source 537, which comprises an application program interface (API).
• APIs application program interface
• data may be pulled from an API or content feed from a third party provider to the plug-in; or data may be pushed to the plug via a third party provider's content feed.
• FIG. 6 illustrates a sample framework for a plug-in shown in FIG. 5.
• Plug- in 600 comprises parser 610, an association module 620, and renderer 630.
• Parser 610 may comprise a metadata parser or API Requestor, one or both communicating with one or more of the "Content Sources" shown on FIG. 5. Parsed data, including optional metadata wrappers, are passed from parser 610 to association module 620. Explicit and inferred cluster result mapping is performed by association module 620, with results processed by renderer 630. Results in the renderer may be processed through an XML schema or a template / user interface mapping, providing metadata wrappers (such as clusterlDs, entitylDs, W4 metadata, and content type metadata) that permit the system to determine the appropriate format, rendering, and user actions for the content shown on the mobile device. Results are then sent to one or more data stores that comprise the "Content Index" of FIG. 5.
• metadata wrappers such as clusterlDs, entitylDs, W4 metadata, and content type metadata
• search results may represent various types of content, such as text, numerical data, image, animation, audio or video and formats of content such as an RSS feed, a link to a newspaper article, a Wikipedia entry, or portions of a web page.
• the user may desire to incorporate one or more search results into the user's home page or mobile home page that automatically appears when a browser or application is first invoked, or is invoked when the user activates a "home" command of some type.
• a search result, or portion of a search result may itself be considered an entity or entity type as previously described; for example, a web link or RSS feed may be added to, and treated as, an entity or entity type on the user's home page. Items which may be added include: (1) web links; (2) RSS feeds; (3) web links for which RSS feeds are created based on periodically revisiting the link to check for updates; (4) "entity” or "entity type”; and (5) entities or entity types added through the parsing of a a web link or RSS feed.
• a user may select a search result or any online web page or resource for future inclusion, or the user may also add the entity or entities represented within that content to the user's personalized content engine.
• the personalized content engine may automatically or interactively determine whether the user wishes to add that content, resource, or feed, among one or multiple associated entities.
• FIG. 7 illustrates four components of Add Anything Engine 700 that may be used to permit the user to add search results to the user's home page or other information aggregation location or device. It should be understood that the elements in FIG. 7 may be easily incorporated in server 130 shown in Fig. 1. For example, Add Anything Engine 700
• 700 may be incorporated into search and data applications 134 on server 130. For simplicity, the description below will be made with reference to FIG. 7.
• Add Anything Engine 700 includes Query Manager 704, Display
• Instrumentation Manager 708, Content Analyzer 712, and Registration Manager 716 are included in Instrumentation Manager 708, Content Analyzer 712, and Registration Manager 716.
• Query Manager 704 tracks search query information and related metadata of one or more usage data sets or search histories of the user as well as across any number of devices or networks associated with the user.
• Query Manager 704 receives information from UDS 152 and MSRM 154.
• Information from Query Manager 704 is supplied to Content Analyzer 712 for use in determination of the particular content type or format to be associated with the corresponding search result.
• Content Analyzer 712 parses received web links and RSS feeds for determination of the corresponding entity and entity type.
• Content Analyzer 712 forwards results corresponding to such a static content type to Registration Manager 716.
• Registration Manager 716 may create a recurring information feed out of a non-feed enabled information object so that the user receives updated information from the corresponding link at various intervals. For example, the user may desire to view web page announcements made by government agencies, such as the United States Patent and
• Registration Manager 716 includes instructions to periodically fetch the data source corresponding to the non-feed enabled information object selected by the user, parse the resulting data, and apply metadata wrappers.
• Registration Manager 716 forwards any recurring information feeds to Mobile
• Homepage Manager 720 for display on mobile device 110.
• Display Instrumentation Manager 708 controls both the actual display of the
• Manager 708 forwards selected known information feeds to Mobile Homepage Manager
• Display Instrumentation Manager 708 may also be configured to sense spoken commands and/or user gestures for selecting selected known information feeds to Mobile Homepage Manager 720 and Registration Manager 716 for feed creation.
• FIGS. 9-13 illustrate an illustrative mobile home page environment and one manner in which a user may add an entity to a mobile device home page.
• Panel 910 displays a portion a mobile device screen from which the user may add content to the user's home page, first by activating the entry entitled "Add Anything to Y! onePlace.” After activation, the user is presented with panel 920.
• Panel 920 includes area 921 for the user to input text for a personalized search, with entries at area 921 corresponding to a default set of locations from which to add content.
• the "Add Anything" capability may be applied to search queries entered by the user and/or to preselected or customized sets of content objects (entities, links, RSS feeds, etc.) presented to the user without requiring the user to enter a search query, but which may utilize contextual and other information about the user, the available entities, and the device, to present one or more customized and/or personalized content objects for possible addition to the user's mobile home page.
• content objects entities, links, RSS feeds, etc.
• the user viewing panel 1010 has input the text "Red Sox" at area 1011.
• panel 1020 After activation of the "oneSearch” button in panel 1010 5 the user is presented with panel 1020, offering the user a variety of choices from which to select one or more content objects to add content to the user's mobile home page.
• Some choices, such as area 1022 correspond to an RSS feed that the user may select.
• Other choices correspond to news articles and links to web sites, for example "www.redsox.com.”
• Area 1021 corresponds to the entity “Boston Red Sox,” which may be associated with one or more information owners, publishers or authors clustered together as described in more detail in Ser. No.
• the user in panel 1110 has selected the first entry 1111 corresponding to the entity "Boston Red Sox" to be added to the user's home page.
• a default set of content and sources is automatically generated by default.
• the user may specifically select or unselect content sources or objects from those associated with the user's subscription to the entity "Boston Red Sox” in order to assemble an individualized set of aggregated content and sources associated with both the entity and the user.
• content associated with entities may be free or fee-based, anonymous or registered depending on the topic and standards of practice.
• FIG. 12 A screenshot illustrating the beginning and ending of the user's home page is shown in FIG. 12.
• panel 1210 represents the 'top' of the home page. The page scrolls down until panel 1220, representing the 'bottom' of the home page, is reached.
• an icon representing the entity "Boston Red Sox” has been added to the user's home page, providing the user with an easily accessible manner in which to view the system's latest personalized set of content corresponding to the Boston Red Sox.
• panel 1310 illustrates content assembled by the system corresponding to the entity "Boston Red Sox.”
• FIG. 1210 illustrates content assembled by the system corresponding to the entity "Boston Red Sox."
• the system has added content sources corresponding to score and schedules, upcoming games, news, photos, and a roster. Unlike mere bookmarks, each of these content sources is dynamic, and information from each source may be automatically retrieved and assembled for the user's consumption.
• the selection and presentation of the associated content objects and feeds for a given entity may also be dynamically altered (i.e., removed, reordered, transcoded into different media types, etc.) based on preferences or actions of the system, the content publisher, the user, an advertiser, the network operator, the device manufacturer, or any combination thereof, as well as related to the various aspects of context described above (i.e., spatial, temporal, social, topical, etc.) in which the associated content objects and feeds for a given entity may be accessed by a user.
• FIG 14 illustrates two views in which the user may reconfigure the user's mobile home page, including the relative order in which items appear. Entry 1430 "Boston Red Sox" demonstrates the new entity added to the user's current content ordering of their mobile home page and the associated arrows allow the user to interactively remove, raise or lower the order of any entity or content on the list. In an embodiment, the user may group, name groups, and delete or reorder groups of any entity or content on the list. [0112] Advertisement Personalization
• the dynamic mobile user web browsing interaction and content consumption experience differs greatly from the traditional, static methods of web browsing typically performed on a personal computer tied to home or work. Attempts to squeeze the traditional web browsing interaction and content consumption experience onto a small mobile screen fail to offer the benefits afforded by the methods and systems disclosed above. [0114] Similarly, use of traditional techniques to squeeze advertising material onto the mobile screen lead to a negative user experience. The traditional techniques lead to 'one-size-f ⁇ ts-air advertisements that intrude on user experience rather than accentuate it. [0115] Significant improvements are afforded in which actual mobile user history is used to (a) rank mobile users against brand and/or advertiser, and (b) predict specific users for specific advertisers at a specific campaign and time and/or space combination for delivery. A method and system for matching advertisements with mobile users is described below with reference to FIG. 8.
• FIG. 8 illustrates a Mobile Homepage Targeting Engine (MHTE) 800, a fully customizable personal advertising system for matching specific ad copy or specialized content to specific ad or content delivery opportunities based upon at least the content, format, configuration and interaction data created by users and their mobile home pages, such as Yahoo's onePlace. It should be understood that the elements in FIG. 8 may be easily incorporated in search and data applications on server 130.
• MHTE 800 may include modules for: (a) managing interaction with advertisers and publishers; and (b) configuring a user's mobile home page with ad serving requests generated by one or more of the following: (1) network; (2) users; and (3) third parties.
• MHTE 800 includes Ad Copy Manager 804, Mobile Home Page Manager 808, Matching Manager 812, and Ad Display Manager 816.
• Ad Copy Manager 804 interacts with advertisers or publishers, and may permit advertisers or publishers to perform one or more of the following: (1) register and manage their accounts; (2) submit ad copy or specialized content; and (3) specify desired actions in the form of targeting models.
• Specialized content may be any form of new, updated or exclusive content marketed to the user by an owner, publisher or content retailer.
• a targeting model may be a function of one or more of the following user characteristics: (1) type of mobile access device; (2) access network; (3) demographic; (4) current user activity; (5) location or proximity to one or more known persons, places or things, (6) co-presence of other users, devices or POI, and (7) user history, preferences, or profile, among others.
• Ad Display Manager 816 responds to specific ad requests whether from the user, the network or a third party service, e.g., carrier or ISP to populate Ad copy or specialized content received from the Ad Copy Manager 804 as instructed by the Matching Manager 812 and returns the instrumented copy for display by the requesting party.
• ad request may include information indicating the desired target user criteria, the amount or maximum amount the advertiser is willing to pay, limitations or conditions of display, and the duration of the offer.
• Mobile Homepage Manager 808 instruments and tracks user content, configuration and interaction with the user's mobile home page or other selected web page including spoken, tactile and sensed inputs.
• Matching Manager 812 applies targeting models to user profiles to qualify, score and select ad copy or specialized content for serving in response to ad requests handled by Ad Display Manager 816. Data from Mobile Homepage Manager 808 may be forwarded to Matching Manager 812 for refinement or construction of various ad targeting models.
• MHTE 800 The following non-limiting examples illustrate some of the benefits afforded by MHTE 800.
• the user has added "Pizza Restaurant” as an entity to onePlace, in order to receive updates such as special promotions, recent reviews, grand openings or any other content, feed or source of information relevant to the entity in the vicinity of the potential target user's current location, home, work or other locations of interest, e.g., regularly visited cities, locations designated of interest by the user, etc.
• Such an entity "Pizza Restaurant” appears as row 1520 in the non-limiting sample subset of oneSearch entity types illustrated in FIG. 15.
• the user would be then considered by MHTE 800 as a potential target eligible to receive customized advertising materials or specialized content.
• MHTE 800 Information regarding the same user may arrive into MHTE 800 through additional interactions by the user. For example, the user may have also added "vegetarian recipes" to onePlace which can be combined with the targeting information derived from the user's interactions with the "Pizza Restaurant” entity to develop a targeting profile that the user would likely prefer content, advertisements, or promotions related to "vegetarian pizzas" as opposed to "nonvegetarian pizzas.”
• An illustration of the benefits afforded by MHTE 800 might be as follows: a pizza maker seeks new customers in a particular area. The pizza maker supplies ad copy or specialized content to Ad Copy Manager 804, along with target data supplied to Ad Display Manager 816.
• Matching Manager 812 identifies a set of potential targets, including the user described above.
• Matching Manager 812 is alerted, reviews the placement of entities on the user's home page and considers the level and type of user activity associated with the entities in the determination of targeted advertisements and content for the user.
• Matching Manager 812 configures an advertisement for a meatless pizza special, served by the pizza maker at its nearby establishment. This advertisement is delivered to the user by Mobile Homepage Manager 808.
• Matching Manager 812 reviews the user's metadata and search history and identifies the user as a potential target.
• additional data and metadata may further enhance the user targeting profile, such as the potential target's prior search history including several searches using the term "vegetarian” in Yahoo! oneSearch, and additionally, the target having posted status updates to MySpace from Yahoo! oneConnect regarding vegetarian recipes.
• Matching Manager 812 is alerted, reviews the user's metadata including social relations and associations history, and configures an advertisement for the meatless pizza special, served by the pizza maker at its nearby establishment. This advertisement is delivered to the user by Mobile Homepage Manager 808 along with search results.
• FIG. 14 illustrates two manners in which a user's placement of entities on the user's home page may be used by Matching Manager 812 as part of the advertisement personalization process.
• Panel 1410 illustrates a user setting panel to coordinate the user's various electronic mail accounts, instant messagers, social networks, contacts, and calendar. When listing information of these kinds, it is customary for the user to place the user's favorite entries near the top of each list.
• Matching Manager 812 may use these types of metrics, such as, ranking within group or between groups, as part of the advertisement personalization process increasing the weight of a particular user to an entity or brand based upon a higher order on their mobile home page or strong associations through past, current or predicted activities.
• panel 1420 corresponds to the user selected ordering of entities, such as those illustrated in FIGS. 9-13.
• the entity ordering shown in panel 1420 corresponds to all entities shown in FIG. 12; note the final entity of "Boston Red Sox.”
• Matching Manager 812 may use this ordering, for example, to select a particular advertisement from a pool of eligible advertisements, with the selected advertisement displayed to the user whereby content and entities associated with a mobile home page influence the selection of the advertisement by increasing the rank of potential advertisements related to content or entities to which the user is subscribed.
• a user's deselection of content or advertisers in the past may also be used to influence the ranking.
• the techniques described herein are implemented by one or more special-purpose computing devices.
• the special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination.
• ASICs application-specific integrated circuits
• FPGAs field programmable gate arrays
• Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques.
• FIG. 16 is a block diagram that illustrates a computer system 1600 upon which an embodiment of the invention may be implemented.
• Computer system 1600 includes a bus 1602 or other communication mechanism for communicating information, and a hardware processor 1604 coupled with bus 1602 for processing information.
• Hardware processor 1604 may be, for example, a general purpose microprocessor.
• Computer system 1600 also includes a main memory 1606, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 1602 for storing information and instructions to be executed by processor 1604.
• Main memory 1606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1604.
• Such instructions when stored in storage media accessible to processor 1604, render computer system 1600 into a special-purpose machine that is customized to perform the operations specified in the instructions.
• Computer system 1600 further includes a read only memory (ROM) 1608 or other static storage device coupled to bus 1602 for storing static information and instructions for processor 1604.
• ROM read only memory
• a storage device 1610 such as a magnetic disk or optical disk, is provided and coupled to bus 1602 for storing information and instructions.
• Computer system 1600 may be coupled via bus 1602 to a display 1612, such as a cathode ray tube (CRT), for displaying information to a computer user.
• An input device 1614 is coupled to bus 1602 for communicating information and command selections to processor 1604.
• cursor control 1616 such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 1604 and for controlling cursor movement on display 1612.
• This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
• Input device 1614 may also be a mobile telephone, gaming, reading, browsing or communication device that may include speech and recording (audio), visual (video and image), tactile and gestural input or sensing input capabilities as well as audio, visual and tactile output capabilities and multi-channel communication capabilities that is interactively connected through one or more networks such as to report its state and location in real-time over time and facilitate access to content and users.
• speech and recording audio
• visual video and image
• tactile and gestural input or sensing input capabilities as well as audio, visual and tactile output capabilities and multi-channel communication capabilities that is interactively connected through one or more networks such as to report its state and location in real-time over time and facilitate access to content and users.
• Computer system 1600 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 1600 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 1600 in response to processor 1604 executing one or more sequences of one or more instructions contained in main memory 1606. Such instructions may be read into main memory 1606 from another storage medium, such as storage device 1610. Execution of the sequences of instructions contained in main memory 1606 causes processor 1604 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
• Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1610.
• Volatile media includes dynamic memory, such as main memory 1606.
• Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM 5 a FLASH-EPROM, NVRAM, any other memory chip or cartridge.
• Storage media is distinct from but may be used in conjunction with transmission media.
• Transmission media participates in transferring information between storage media.
• transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 1602.
• transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
• Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 1604 for execution.
• the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer.
• the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
• a modem local to computer system 1600 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal.
• An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 1602.
• Bus 1602 carries the data to main memory 1606, from which processor 1604 retrieves and executes the instructions.
• Computer system 1600 also includes a communication interface 1618 coupled to bus 1602.
• Communication interface 1618 provides a two-way data communication coupling to a network link 1620 that is connected to a local network 1622.
• communication interface 1618 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
• ISDN integrated services digital network
• communication interface 1618 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 1618 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
• LAN local area network
• Network link 1620 typically provides data communication through one or more networks to other data devices.
• network link 1620 may provide a connection through local network 1622 to a host computer 1624 or to data equipment operated by an Internet Service Provider (ISP) 1626.
• ISP 1626 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet" 1628.
• Internet 1628 uses electrical, electromagnetic or optical signals that carry digital data streams.
• the signals through the various networks and the signals on network link 1620 and through communication interface 1618, which carry the digital data to and from computer system 1600, are example forms of transmission media.
• Computer system 1600 can send messages and receive data, including program code, through the network(s), network link 1620 and communication interface 1618.
• a server 1630 might transmit a requested code for an application program through Internet 1628, ISP 1626, local network 1622 and communication interface 1618.
• Embodiments of the invention may also be directed to computer program products comprising software stored on any computer readable medium including mobile telephones or computing devices. Such software, when executed in one or more data processing devices, causes a data processing device(s) to operate as described herein.
• Embodiments of the present invention employ any computer readable medium, known now or in the future. Examples of computer readable mediums include, but are not limited to.
• primary storage devices e.g., any type of random access memory
• secondary storage devices e.g., hard drives, floppy disks, CD ROMS, zip disks, tapes, magnetic storage devices, optical storage devices, MEMs, nanotechnology-based storage device, etc.
• This specification is on a periodic release schedule to improve conformance to industry standard vocabularies and enable common use cases to be accomplished in a consistent manner. It will be refreshed approximately weekly during the alpha and beta periods, while we work closely with partners.
• the searchmonkey-profile vocabulary can be used in DataRSS feeds, and with pages embedded with RDFa and eRDF.
• searchmonkey-profile consists of a number of vocabulary definitions, including industry-standard ones, as well as a simple way to declare all the prefixes.
• DataRSS add the following processing instruction to the beginning of a feed to declare the searchmonkey-profile vocabulary definitions:
• the rel vocabulary defines values to use in the rel attribute of item.
• the naming convention for these properties is to always start with the rel: prefix, followed by a short term representing a person, place, thing, idea, or concept. While these are not RDF classes in a formal sense, in practice they are used much the same way and thus share the convention of starting with an initial capital letter, not counting the prefix.
• rel Resource. All other relationships in this vocabulary directly or indirectly "subclass" from rel : Resource.
• a "Parent Class" column indicates the next-more-general relationship. For example from more specific to more general: a rel .- Image is a rel : Media which is a rel : Resource.
• Task family of rel properties are intentionally defined in a fairly generic way, so pick the closest one that matches. Here are a few of the more commonly used ones;
• rel Edit to edit a wiki page for instance.
• rel Edit property is particularly useful.
• the property attribute contained within a meta tag, associates a literal string value with a resource. Official and unofficial industry standards in wide use make up the bulk of the list. Where no existing vocabulary is in wide use, certain key properties are defined in this profile. The following sections give guidance on which vocabularies to use. All properties are listed in the searchmonkey-profile vocabulary specification.
• the domain specifies which kinds of items the property applies to. For instance, media : width makes sense only on rel : Media items; it makes no sense applied to rel : Person, for example.
• the range specifies what kind of string values to expect in this property.
• the dc date property should accept a date in a certain format, namely YYYY-MM-DD, also known as ISO-8601 format.
• tagspace tags as a space-separated tag list
• tagspace tag for a single tag (which might include spaces)
• media height and media : width for audio/video resources, it is good to specify the size in pixels with these attributes
• geo location for a general, human-readable location like "San Francisco” or "South Bay Area” • geo -.point for a specific latitude/longitude (space-separated)
• Datatype vocabularies have two main uses. Some properties, like dc .- identifier can have many different possible values, say a URL, or an ISBN number. In this case the range of this property is only "string”, however, if you want to specify explicitly that the value you've put in there is more specific than what the range will allow, you can specify a datatype.
• the prefix should be something reasonably short, descriptive, and not likely to used for an unrelated purpose by someone else. As is the case with all CURIEs, the prefix stands for a longer URL, for which you need to define. It should be something underneath a domain name over which you have control.
• the Domain column indicates which types of objects can have the listed property. For example: the media : uri applies to objects of class rel : Media, which includes child classes rel : Image, rel : Thumbnail, and others.
• a blank value in the Domain column indicates that the listed property applies to all objects.
• the Range column indicates what kinds of values are appropriate for the listed property. Integer, float, decimal, and duration all map to the XML Schema datatypes of the same name. Date maps to XML Schema dateTime, which uses ISO 8601 format. URI maps to XML Schema anyURI and must be an absolute URL, not starting with a slash. Email maps to an email address defined by RFC 2822. List maps to a space-separated list.
• a blank value in the Range column indicate that the listed property can accept values in any format.
• Friend-of-a-friend ⁇ http://xmlns.eom/foaf/0. l/> geo a vocabulary for geographic metadata ⁇ http://www.georss.org/georss> media

Landscapes

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

Applications Claiming Priority (2)

Publications (2)

Family

ID=41377484

Family Applications (1)

Country Status (4)

Cited By (1)

Families Citing this family (30)

Citations (1)

Family Cites Families (6)

• 2009
  • 2009-04-01 WO PCT/US2009/039212 patent/WO2009146087A1/en active Application Filing
  • 2009-04-01 KR KR1020107024602A patent/KR101475552B1/ko active IP Right Grant
  • 2009-04-01 EP EP09755449A patent/EP2272015A4/de not_active Withdrawn
  • 2009-04-01 CN CN2009801105281A patent/CN101981570A/zh active Pending

Patent Citations (1)

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events