EP1982275A1 - Plate-forme de recherche - Google Patents

Plate-forme de recherche

Info

Publication number
EP1982275A1
EP1982275A1 EP07700378A EP07700378A EP1982275A1 EP 1982275 A1 EP1982275 A1 EP 1982275A1 EP 07700378 A EP07700378 A EP 07700378A EP 07700378 A EP07700378 A EP 07700378A EP 1982275 A1 EP1982275 A1 EP 1982275A1
Authority
EP
European Patent Office
Prior art keywords
search
content
user
results
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP07700378A
Other languages
German (de)
English (en)
Inventor
Jiazhen Wu
Fred Bierhaus
Massimo Vitali
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vodafone Group PLC
Original Assignee
Vodafone Group PLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vodafone Group PLC filed Critical Vodafone Group PLC
Publication of EP1982275A1 publication Critical patent/EP1982275A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/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
    • 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/903—Querying
    • G06F16/9038—Presentation of query results

Definitions

  • the invention relates to a search platform for mobile devices.
  • the invention relates to a search platform adapted to tailor the results of a search to the particular subscriber, mobile device and/or search context (date, time, location, profile etc.)
  • Search engines have become central to a rich experience of the content stored in computing networks. Along with directory portals, search engines facilitate effective use of the internet (especially the Web).
  • Search engines do however present their own challenges. Often, a search request will give rise to many more search "hits" in the search results than can reasonably be assessed. The majority of search engines limit the number of browsable results to a more manageable figure and attempt to identify the most relevant hits and rank those hits ahead of otherwise similar hits. This problem is often compounded in the mobile environment, where there is generally far less browsable screen area and where charging models can mean that the download of each byte of data represents a monetary cost to the user as well as a corresponding download delay.
  • One conventional way of managing the vast body of potential search hits is to filter results before rendering the search results, thereby reducing the number of hits presented to the terminal user. This technique is not unique to the mobile environment.
  • WAP wireless access protocol
  • WML wireless markup language
  • WML documents are stored on a web server in much the same way as HTML (Hyper Text Markup Language) documents.
  • Mobile terminals access WML decks via a WAP gateway.
  • WAP gateways provide an interface with WML content, and increasingly with the World Wide Web.
  • a known first step in the provision of mobile search functionality is to filter content based on whether the device supports WML or XHTML before presenting the results of a search to a user.
  • a method for generating search results from an index of a content store containing a plurality of content items over a wireless telecommunications connection, each content item having corresponding meta information associated therewith, the meta information comprising at least one of device, subscriber and context specific information comprising: receiving a search request message from a user using a mobile device, the search request message including user search terms; obtaining contextual data representative of the mobile device, user subscription and network capability; initiating a search of the content store index in accordance with the user search terms; determining, for at least one of the user search terms, whether there exists one or more correlated index entry in the content index; and where a correlation exists, generating search results, the results of the search including respective links to correlated content items ranked in accordance with the contextual data.
  • the method may include a step of filtering based upon contextual criteria, for example: network capability (e.g. is the bearer technology GPRS, EDGE, UMTS/3G, or HSDPA etc.? what is the current network load status?) and user profile (whether automatically and dynamically generated or manually provided by the user).
  • network capability e.g. is the bearer technology GPRS, EDGE, UMTS/3G, or HSDPA etc.? what is the current network load status
  • user profile whether automatically and dynamically generated or manually provided by the user.
  • the user profile may include an indication of location.
  • This location information may be manually entered by the subscriber or alternatively acquired through an automatic location mechanism: for instance using Cell ID or global positioning satellite (GPS) information. Bothe GPS and Cell ID techniques are well know in the field and will not be detailed in the present context.
  • GPS global positioning satellite
  • the invention thus provides a deep link device-specific search with categorised result display.
  • Mobile search as described here improves on the user experience from search engines such as Google and Yahoo by returning search results that are based on a detailed context profile of the device, user, and network capability.
  • search engines such as Google and Yahoo by returning search results that are based on a detailed context profile of the device, user, and network capability.
  • the mobile user is no longer presented with content, often chargeable, downloadable digital content, which is generally not optimal for his/her specific device and circumstances.
  • Search results are conveniently tailored to reflect whether a user is in the right mobile network coverage area (e.g. 3G) to receive the content.
  • a user is in the right mobile network coverage area (e.g. 3G) to receive the content.
  • Content "on net” is required to carry additional metatags that indicate deep information about the content: e.g. whether the content is for a specific device, for colour displays only, for subscribers to a paid for channel only or indeed for "adults only”.
  • crawler agents When the crawler agents generate their indexed database (a content store index), they provide a richer database for a corresponding "intelligent" search engine to take advantage of. The results are then ranked in such a way that the most relevant content/results are given higher weighting.
  • Figure 1 shows the architecture of a typical mobile portal including a mobile search platform in accordance with the present invention
  • FIG. 2 shows the operation of the mobile search platform of Figure 1 in more detail
  • Figure 3 shows the hierarchical structure of crawler functionality; and Figure 4 shows the general MVC (Model/View/Controller) architecture of the content assembly engine (CAE) portion of the mobile search portal.
  • MVC Model/View/Controller
  • FIG. 1 shows the architecture of a typical mobile portal system including a mobile search platform 100,110,120. The operation of the components of the platform is now described:
  • Content is stored in one or more content stores 150.
  • Each content item has associated meta information which describes a range of attributes of the content item.
  • Meta information describes a range of attributes of the content item.
  • RDF Resource Descriptor Framework metadata.
  • RDF is a W3C standard that is defined as a language to describe the information of the World Wide Web resources and their specific metadata (e.g. title, author, creation date, date of last modify, copyright, licensing and others) and "objects" that can be identified on the network.
  • the W3C Metadata Activity webpage describes RDF as follows: Resource Description Framework (RDF) "provides a more general treatment of metadata”.
  • RDF is a declarative language and provides a standard way for using XML to represent metadata in the form of statements about properties and relationships of items on the Web. Such items, known as resources, can be almost anything, provided it has a Web address. This means that you can associate metadata with a Web page, a graphic, an audio file, a movie clip, and so on.
  • RDF provides a framework in which independent communities can develop vocabularies that suit their specific needs and share vocabularies with other communities. In order to share vocabularies, the meaning of the terms must be spelled out in detail. The descriptions of these vocabulary sets are called RDF Schemas.
  • a schema defines the meaning, characteristics, and relationships of a set of properties, and this may include constraints on potential values and the inheritance of properties from other schemas.
  • the RDF language allows each document containing metadata to clarify which vocabulary is being used by assigning each vocabulary a Web address. In short, RDF is extensible.
  • RDF schema are defined to describe meta information about mobile content, such as ringtone, game, picture and music.
  • the meta information may include indications of whether a particular content item is suitable for a given class of mobile device.
  • the search index used in Fig 1 is hosted by a remote external partner. Rather than populating the search index 120 by crawling the content store 150 from the remote site of the search index 120, the Applicant has developed an "internal search crawler" 160, based on a user agent that provides:
  • the internal search crawler 160 delivers improved quality and number of relevant search results.
  • the internal crawler 160 is arranged to parse multi-entry RDF files, where they appear, giving content providers 140 the opportunity to modify their RDF creation logic to take advantage of this.
  • Logic is introduced in the internal search crawler user agent 160 to ensure that if the URL of the referring page matches the URL embedded within the RDF file, results will be merged to single search index entry, thereby improving the content finding capability.
  • the user agent may be arranged to use relative links in meta-refs to RDF, and in the RDF files themselves.
  • the internal crawler 160 requests a page, which is specified as an entry point in the configuration file, to the web server after identifying itself. Once the page is obtained, it reads and processes the content of the RDF meta information about the content, along with 3rd party supplied pages, extracting title, text, links and all other relevant information. The product follows new links found in the current page while keeping an account of the list of links that have already been followed.
  • the configuration file also has a configurable filter that allows limited sites navigation using a pattern (i.e. a string). Each time the product crawls a page the valid information obtained is stored in a local database (210 in Figure 2).
  • Each operating company may choose to install a local version of the software stack for handling the provision of content via a terminal application.
  • a bespoke internal crawler can be implemented in each operating company's service delivery platform (or "core stack").
  • each internal crawler system can be arranged to run within software stacks appropriate to each operating company, there is an immediate speed advantage over conventional externally provided crawler systems: • the crawl happens at the assembly layer, meaning that there is no requirement to render content for the internal crawler 160 • the incoming crawl requests are immune to Internet latency
  • crawler 160 By having the internal crawler 160 under the control of the network service provider (or operating company) rather than a third party, multiple crawler tasks can be set running at different times and frequencies, allowing each local operator to see in real-time what is happening. As a result: frequently changing content (for example - news stories) can be crawled more frequently than relatively static content (for example - ringtones); new or modified existing crawler start points can be added very much quicker in response to requests from content providers; and the facility for monitoring and debugging crawler progress can be enhanced to identify and fix problems that stop content items being indexed.
  • frequently changing content for example - news stories
  • relatively static content for example - ringtones
  • new or modified existing crawler start points can be added very much quicker in response to requests from content providers
  • the facility for monitoring and debugging crawler progress can be enhanced to identify and fix problems that stop content items being indexed.
  • Figure 3 illustrates the software hierarchy of the internal crawler application 160, whereby the frequency and timing of crawling tasks can be scheduled.
  • a varying number of individual instances of the agents (“threads") can operate upon any given task.
  • Each crawling session can in turn mandate a plurality of different tasks.
  • the internal crawler 160 has been designed to work not only with multiple small RDF meta-data files that reference a single piece of content (an arrangement known from the conventional FAST-SEARCH crawler from FAST[RTM]), but also with large RDF meta-data files that reference multiple items of content ("multi-entry RDF files"). Consequently, for content providers 140 who store details of their content in a database 150, if large RDF files are created (or programmed to be created on-the-fly by server-side logic) with details of all content within it, then the information in those large RDF files will be inserted directly into the index 120, with no need to crawl furtfier pages from that provider. Furthermore, content from third party content providers 140 will become much more visible in the search results, driving increased user traffic and revenue.
  • the operation of the search platform and particularly of the Search Content Push Engine (SCPS) 180 is illustrated in Figure 2.
  • the SCP Engine 180 has a number of execution functionalities, including: XMLwriter, Uploader and cleaner functionalities. These functionalities are described below.
  • Each single crawling task populates a local database 210 (e.g. an Oracle [RTM] database) with crawling information. These need to be transformed into XML data in order to be uploaded onto the remote search index 120 hosted by the external search engine 110.
  • the XMLwriter retrieves task data (i.e. crawling information) that are stored in the database and converts them into customized XML files accordingly to specifics of the remote index database 120.
  • the XML files generated by the XMLwriter are uploaded into the remote search index 120 as documents either replacing old versions of the same documents, or inserting new documents if no old ones exist.
  • the data can then be viewed through the mobile interface 130.
  • the Cleaner establishes a connection to the remote search index and removes a set of documents having specific features defined by the settings that appear in the apposite configuration file. Several different cleaning types are supported, starting from the removal of the obsolete documents and ending with the removal of all the documents having a specific field value.
  • the operation of the mobile search portal 100 is perhaps best understood when one considers the illustrative use case of a subscriber choosing to search for content via the portal 100.
  • the portal 100 presents a search interface 130 to the subscriber's mobile device, which allows the subscriber to specify search criteria. Let us assume that in this case the subscriber enters a word or phrase.
  • the search interface 130 may further provide further options.
  • the content type limitation option is not taken, it may be assumed that the subscriber wishes to 5 search all available content. If however the subscriber chooses a content type, the portal 100 allows the subscriber to initiate a search.
  • the system receives the search request from the subscriber and processes the portal request. Firstly, the subscriber is authenticated. Provided the subscriber is 0 authenticated, the request is authorized.
  • contextual information is obtained.
  • This contextual information includes information relating to the subscriber profile of the user (e.g. language preference, safe-search criterion, credit level etc) and information 5 delivered by the mobile terminal in the authentication process (e.g. subscriber's device type).
  • the portal system 100 then checks the submitted search criteria to ensure that the search is valid (e.g. it contains at least two recognised characters).
  • the system ZO then sends the search criteria along with the contextual information and content type (if selected) to the search engine 110.
  • the search engine 110 processes valid search criteria and generates ranked, device-specific search results. >5
  • the core stack of the portal system 132 then receives the device specific search results from the search engine 110 and renders them for presentation on the subscriber's display.
  • the core stack (or service delivery platform) 132 includes a third party integration component (3PI), 230 a content (or common) assembly engine (CAE) 240 and a content rendering engine (CRE) 250. These components are shown in both Fig 1 and Fig 2, but only given reference numbers in Fig 2.
  • the 3PI 230 receives RDF tag information in partner markup rig (PML) files provided by content providers 220, 222, 224 in addition to the content itself.
  • the 3PI 230 extracts the RDF tag information corresponding to the content items and supplies the extracted information as "fragments" of operator mark-up language (in the present applicant's case: Vodafone Content Markup Language or VCML).
  • the operator markup language fragments are then assembled at the assembly layer for delivery to a higher level, rendering layer.
  • the functionality of the assembly layer is provided by the CAE 240, a software component that interprets incoming requests from users, obtains information from content sources (i.e. the extracted RDF tag information in the VCML fragments), and assembles the pieces that will make up the response into a single content document (in this instance, a VCML "page"). It then sends the assembled content to the rendering layer.
  • the general architecture of the CAE 240 is shown in Figure 4.
  • MVC Model/View/Controller
  • business logic classes and beans comprise the Model
  • JSP files and custom tags comprise the View
  • Actions comprise the Controller.
  • the business logic can be further separated into several layers: Service objects and Manager objects.
  • the Service objects are the core of the business logic and sit on top of Manager objects, which encapsulate lower level functionality, such as persistence, or, in the case of the Search Portal, connections to the external search servers.
  • a key example of an Action is the SubmitSearchAction, which is responsible for extracting the user's query from the request, validating it, and calling the business logic to perform the search. To complement this Action, the present CAE provides SearchService and SearchManager.
  • SearchService is responsible for search engine implementation independent business logic, allowing such things as the boosting of internal results.
  • SearchManager is responsible for business logic which is specific to the implemented search engine, such as generating a syntactically correct query and transforming search engine result objects into generic value objects for consumption by the higher layers.
  • the content rendering layer receives search result objects, parses the markup language and delivers the result object in a format suitable for display.
  • the CRE 250 recognises an end-user's device, and uses the attributes of the device to convert resources such as images and text coming from the CAE 240 to a size and format appropriate for the particular device. It also manages the connection between the user device and the rest of the Service Delivery Platform: in particular the provision of the search interface 130 for extracting user requests.
  • the core stack 132 may be provided with a spelling inference engine (not shown) for generating an alternative spelling response along with the search results. This addresses the common experience of misspelling, suggesting a "most likely" alternative search term.
  • the portal 100 can filter out results corresponding to age-classified and/or age- restricted content.
  • the portal 100 is arranged to detect a Service ID tag (i.e. a charging tag) within the links to content items returned. If a Service ID is contained within an item returned by the search engine 110 and the subscriber chooses to download that content, a charge will be deducted from their account.
  • a Service ID tag i.e. a charging tag
  • the portal displays the item in a search results deck.
  • the deck shows the entered search criteria, the total number of results matching the search criteria to be displayed, and each search result as a hyperlink, with a teaser description for each search result.
  • the search results may be displayed grouped by content type.
  • the search results may distinguish between content that is hosted by the service provider ("on net") and content hosted on web servers not controlled by the provider ("off net").
  • the results deck may show this separation by displaying the total number of results for each group as a distinct item.
  • the search results are displayed within each group ordered according to relevancy.
  • the system can be configured to display results with a relevancy ranking equal to or greater than a predetermined threshold.
  • "On net” search results may be "boosted” individually above similar “off net” results or they may be presented as an "on net” group above a corresponding "off net” group.
  • the search result deck may indicate the fact visually, for example with an icon.
  • search tips facility, whereby the subscriber may request guidance about suitable search terms, wildcard symbols.
  • the subscriber may qualify a word search with a content type limitation. More generally he may be taken through a search process based on the context of the search request, a so-called contextual search.
  • the subscriber chooses to search for content from a contextual search hyperlink.
  • the system returns a search dialogue page with the context (e.g. content type) pre-selected. Examples of content types are ringtones, games, pictures & music.
  • the system may also allow the subscriber to specify further contextual search criteria.
  • the subscriber Using the pre-filled search dialogue page, the subscriber enters a word or phrase for their contextual search.
  • the system handles this contextual search by initiating a search within the defined context (content type).
  • the subscriber may search within distinct "content channels" (such as a news broadcast feed or a chart music/video content channel).
  • the subscriber chooses the channel search option from a 3 rd party brokered partner page.
  • the system allows the subscriber to specify the channel search criteria and returns a pre-filled search dialogue page: pre-filled on this occasion with a predetermined channel selected.
  • the subscriber uses the pre-filled search dialogue page to enter a word or phrase for a channel search and the system responds to the entry of search terms in this dialogue page by initiating a corresponding search within the selected channel for the subscriber.
  • Service ID information can be used to refine further the results of a search task.
  • the raw results of a search task include service ID information.
  • the system may send a request for service related information, such as pricing data, to an appropriate service application (e.g. a charging and pricing application), not shown.
  • the request is arranged to contain the service ID information for the content item.
  • the system receives a corresponding response from the service application.
  • the information displayed by the system can then be tailored to reflect the service related information corresponding to the content item in the search results.
  • selecting the link to the content item would lead to a content subscription request page instead of a direct link to the actual content.
  • the system may be arranged to return a suitable error message when it determines that the search criteria entered are invalid.
  • the system may be arranged to display a message advising the subscriber that no results were found when it receives a "no results found" response from the search engine.
  • the cause of a null result may be misspelling.
  • the occurrence of a "no results” response may be the trigger for an update handling mechanism. Whenever the "no results" response is received the mechanism is capable of checking the context of the request and in certain circumstances (e.g. the device or firmware being used by the subscriber is unrecognised) may suggest or trigger an update check. As a result the occurrence of such "no results" responses can be reduced.
  • the system may be provided with a spelling engine, so that if the "no results found" response contains an alternative spelling, the system displays an alternative spelling message with the alternative spelling displayed as a search hyperlink.
  • the spelling engine may equally well be used, when results are found.
  • the system may display a message advising the Subscriber that an alternative spelling has been found and the alternative spelling may be displayed as a search hyperlink.
  • the user may actively request the application of the spelling engine to verify their typed search criteria.
  • the system logs a communication failure event and displays an error message.
  • a determination that search engine is unavailable is met with a similar result. Again the system logs a communication failure event and displays an appropriate error message.
  • the mobile search platform thus filters search results intelligently, taking account of:
  • device features e.g. full track music capable phone
  • device type e.g. Advanced phone with wide screen
  • device name e.g. firmware installed on device
  • the intelligent crawling solution described above provides crawling of the mobile content using both a proprietary content format (in the case of the Applicant - Vodafone Content Markup Language, VCML) and mobile RDF (Resource Description Framework) tagging scheme.
  • the intelligent crawler automatically associates content with their meta-information such as device specific features, network suitability, user profile suitability, subscriptions, categories of the content, ranking boosting value of the content etc. This makes rendering search results simple yet relevant to the personal context of the user.

Abstract

L'invention concerne une plate-forme de recherche pour dispositifs mobiles, cette plate-forme pouvant être conçue pour adapter les résultats d'une recherche à un abonné particulier, un dispositif mobile et/ou un contexte de recherche (date, temps, localisation, profil, etc.). La demande d'accompagnement de ce contenu par des méta-informations associées et la mise à disposition d'un agent utilisateur local qui comprend le formatage de ces méta-informations, permettent à un moteur de recherche d'assembler une base de données de contenus indexés en profondeur. En conséquence, les résultats de recherche représentant les articles de contenu les plus appropriés pour l'abonné peuvent être présentés tout en réduisant au minimum les éventualités de distribution de contenu indésirable.
EP07700378A 2006-01-13 2007-01-12 Plate-forme de recherche Ceased EP1982275A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GBGB0600678.7A GB0600678D0 (en) 2006-01-13 2006-01-13 Search platform
PCT/GB2007/000091 WO2007080413A1 (fr) 2006-01-13 2007-01-12 Plate-forme de recherche

Publications (1)

Publication Number Publication Date
EP1982275A1 true EP1982275A1 (fr) 2008-10-22

Family

ID=35997995

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07700378A Ceased EP1982275A1 (fr) 2006-01-13 2007-01-12 Plate-forme de recherche

Country Status (5)

Country Link
EP (1) EP1982275A1 (fr)
JP (1) JP2009523284A (fr)
CN (1) CN101401099A (fr)
GB (2) GB0600678D0 (fr)
WO (1) WO2007080413A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4220943B2 (ja) 2004-07-15 2009-02-04 ソフトバンクモバイル株式会社 電子機器
US8565733B2 (en) * 2008-05-08 2013-10-22 Clear Channel Management Services, Inc. Computer-based method and system for processing a file request in response to a message received from a user mobile device
EP2128776A1 (fr) 2008-05-26 2009-12-02 Vodafone Holding GmbH Procédé, plate-forme de recherche et dispositif d'utilisateur pour générer des résultats de recherche
US10812937B2 (en) * 2008-12-11 2020-10-20 Qualcomm Incorporated Method and apparatus for obtaining contextually relevant content
US20120191686A1 (en) * 2009-10-07 2012-07-26 Telefonaktiebolaget L M Ericsson (Publ) System and Method for Assisting a User with Searching Multimedia Objects
US8762374B1 (en) 2010-03-08 2014-06-24 Emc Corporation Task driven context-aware search
US9031958B2 (en) * 2011-04-18 2015-05-12 International Business Machines Corporation File searching on mobile devices
US20140143244A1 (en) * 2011-06-16 2014-05-22 Nokia Corporation Method and apparatus for searching for content within a channel based on contextual characteristics
US8959087B2 (en) * 2011-09-21 2015-02-17 Oracle International Corporation Search-based universal navigation
US10666997B2 (en) * 2012-01-05 2020-05-26 Disney Enterprises, Inc. Cloud based content assembly method and system
KR102019975B1 (ko) * 2012-08-29 2019-11-04 삼성전자주식회사 디아비스 및 그의 컨텐츠 검색 방법
US10007731B2 (en) * 2012-09-12 2018-06-26 Google Llc Deduplication in search results
WO2014072989A1 (fr) 2012-11-09 2014-05-15 P M Bijin Procédé et système de localisation d'industrie commerciale et de service d'une coordonnée géographique spécifique par le biais de dispositif de communication sans fil
WO2016137114A1 (fr) * 2015-02-23 2016-09-01 건국대학교 산학협력단 Procédé et dispositif d'établissement de base de données de métaconnaissances et de traitement d'interrogation
US9773040B2 (en) 2015-05-04 2017-09-26 Alan Weisman Search token mnemonic replacement
US9311168B1 (en) * 2015-09-30 2016-04-12 Google Inc. Deeplinking to multiple native applications
US10534780B2 (en) 2015-10-28 2020-01-14 Microsoft Technology Licensing, Llc Single unified ranker

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10269246A (ja) * 1997-03-21 1998-10-09 Tsushin Hoso Kiko 検索情報配信方法
US6182066B1 (en) * 1997-11-26 2001-01-30 International Business Machines Corp. Category processing of query topics and electronic document content topics
US6968333B2 (en) * 2000-04-02 2005-11-22 Tangis Corporation Soliciting information based on a computer user's context
AU2001241000A1 (en) * 2000-03-07 2001-09-17 Tzunami Inc. System and method for computer searching
EP1337940B1 (fr) * 2000-11-20 2004-04-28 BRITISH TELECOMMUNICATIONS public limited company Procede de gestion des ressources
US7200801B2 (en) * 2002-05-17 2007-04-03 Sap Aktiengesellschaft Rich media information portals
US7356332B2 (en) * 2003-06-09 2008-04-08 Microsoft Corporation Mobile information system for presenting information to mobile devices
US20050071328A1 (en) * 2003-09-30 2005-03-31 Lawrence Stephen R. Personalization of web search
US7716158B2 (en) * 2004-01-09 2010-05-11 Microsoft Corporation System and method for context sensitive searching

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2007080413A1 *

Also Published As

Publication number Publication date
GB0600678D0 (en) 2006-02-22
CN101401099A (zh) 2009-04-01
WO2007080413A1 (fr) 2007-07-19
GB0700662D0 (en) 2007-02-21
GB2434230A (en) 2007-07-18
JP2009523284A (ja) 2009-06-18

Similar Documents

Publication Publication Date Title
WO2007080413A1 (fr) Plate-forme de recherche
CN101601033B (zh) 响应于模式化查询而生成专业的搜索结果
US8280879B2 (en) System and method for quantifying visibility within search engines
RU2522103C2 (ru) Способ и браузер для уведомления об обновлении
US20090006338A1 (en) User created mobile content
US8756228B2 (en) Method and apparatus for creating contextualized feeds
US20050131889A1 (en) Intelligent data query builder
US20110029541A1 (en) System and method for intent-driven search result presentation
EP2151981A1 (fr) Procédé, système et appareil pour implanter une annonce publicitaire
US8204956B2 (en) Computer-implemented voice application indexing web site
KR20070034458A (ko) 개인용 포털과 웹 컨텐츠 신디케이션의 통합 방법
WO2011127427A2 (fr) Optimisation de contenu dynamique basée sur un abonnement
US20040205651A1 (en) Transferring information over a network related to the content of user's focus
WO2010094927A1 (fr) Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes
US7590681B1 (en) Method and system for managing and delivering web content to internet appliances
US20090024702A1 (en) Method for Selection and Display of at Least One Piece of Additional Information
JP2006139470A (ja) 情報提供装置および情報提供方法ならびにそのプログラム
US20030120779A1 (en) Method for performing a search, and computer program product and user interface for same
US8103649B2 (en) Search system and search method
US9727650B2 (en) Method for delivering query responses
JP2010165155A (ja) コンテンツ提供装置
GB2445394A (en) Database query method
JP2003288342A (ja) 情報処理装置
EP2089822B1 (fr) Système et procédé pour identifier des adresses dans un réseau de données distribué
KR20110003994A (ko) 검색 결과 내 추가 검색 모듈 및 그를 이용한 검색 결과 내 추가 검색 방법

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080801

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20081114

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20101214