WO2011150340A2 - Procédé et système d'enrichissement de résultats de recherche par des informations de traitement de paiement - Google Patents

Procédé et système d'enrichissement de résultats de recherche par des informations de traitement de paiement Download PDF

Info

Publication number
WO2011150340A2
WO2011150340A2 PCT/US2011/038355 US2011038355W WO2011150340A2 WO 2011150340 A2 WO2011150340 A2 WO 2011150340A2 US 2011038355 W US2011038355 W US 2011038355W WO 2011150340 A2 WO2011150340 A2 WO 2011150340A2
Authority
WO
WIPO (PCT)
Prior art keywords
payment processing
urls
merchant
marketplace
search results
Prior art date
Application number
PCT/US2011/038355
Other languages
English (en)
Other versions
WO2011150340A3 (fr
Inventor
Audian H. Paxson
Scott A. Sachtjen
Original Assignee
Iconix, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Iconix, Inc. filed Critical Iconix, Inc.
Publication of WO2011150340A2 publication Critical patent/WO2011150340A2/fr
Publication of WO2011150340A3 publication Critical patent/WO2011150340A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising

Definitions

  • the present disclosure generally relates to data processing systems. More specifically, the present disclosure relates to methods and systems for enhancing search results by presenting relevant payment processing information with one or more search results displayed in a search results page.
  • a search engine is an application that processes user-provided queries to search for information on the World Wide Web.
  • a search engine's output is typically a web page, referred to as a search results page (SRP), showing a list of items satisfying the user-provided query.
  • SRP search results page
  • each search result shown in a search results page consists of a user-selectable (e.g., hyperlink) heading, or title, and some additional text (sometimes referred to as a page snippet) that provides some context for why the search result satisfied the user's search query.
  • Figure 1 illustrates an example of a conventional search results page.
  • a user has performed a search with the search terms "64 GB iPad" by entering the terms into the search bar 10, and selecting the search button 12.
  • the first search result has the title or heading, "eStore.com: 64 GB iPad (New)".
  • the heading or title 14 is a hyperlink directed to the actual web page satisfying the user's query. Accordingly, if selected, the user's web browser will request the relevant web page hosted at the eStore.com website.
  • the search result shows some additional text 16 that provides the user with some context for why the web page satisfied the search query.
  • the exact algorithm used in selecting the text to be displayed in the header or title, and the additional text (sometimes referred to as a page snippet), varies from one search engine to the next.
  • a user may be performing a search for a specific purpose. For instance, in the example shown in Figure 1, the user may be searching for a website of an online merchant or marketplace where the user can purchase a 64 GB iPad.
  • certain information if displayed in the search results, might enhance the usefulness of the search results to the end- user.
  • useful information about a particular merchant is not readily accessible to a search engine's crawler and therefore such information cannot simply be added by the search engine to the various search results.
  • Figure 1 is a prior art view of an example search results page
  • Figure 2 is an example of a search results page showing payment processing information, consistent with an embodiment of the invention
  • Figure 3 illustrates a network environment showing several of the various computing components involved in a system for enhancing search results with payment processing information, consistent with some embodiments of the invention
  • Figure 4 illustrates a network environment showing several of the various computing components involved in a system for enhancing search results with payment processing information, consistent with some alternative embodiments of the invention
  • Figure 5 illustrates a method, according to an embodiment of the invention, for enhancing search results by displaying with the search results payment processing information indicating, for example, which search results are associated with merchants who accept payments from a particular online payment processing entity;
  • Figure 6 is a block diagram of a machine in the form of a computer within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • search results when search results are displayed by a web browser application, the search results are enhanced by displaying payment processing information next to, or near, some of the individual search results. For instance, the payment processing
  • information may be some text, a graphic, or some other indicia, indicating that an on-line merchant or marketplace associated with a particular search result accepts payments from a particular payment processing entity.
  • the text, graphic or indicia is displayed in proximity with each search result that is associated with an address, or Uniform Resource Locator (URL), of an on-line merchant or marketplace known to accept and process payments from the particular payment processor.
  • URL Uniform Resource Locator
  • the graphic or icon element with reference number 18 indicates that the merchant, "eStore.com", associated with the first search result, accepts payments from a payment processing entity arbitrarily referred to herein as "PayUS.”
  • a payment processing entity e.g., PayUS in Figure 2
  • a search results page may include payment processing information for any number of payment processing entities, such that a single search result may be shown with multiple payment processing entities.
  • the search results page is modified to display payment processing information after the search results page has been communicated from a search engine to the web browser application residing and executing at an end-user's client computer.
  • the logic for identifying the search results with which the payment processing information is to be displayed, and for modifying the search results page to actually display the payment processing information is embodied, at least in part, in a web browser plug-in.
  • a web browser plug-in which may also be referred to as a browser extension, browser helper object, browser add- in, or add-on, is an ancillary computer program that operates in conjunction with a web browser application to perform some specific function.
  • the browser plug-in is invoked to analyze a search results page for the purpose of identifying which search results are known to be associated with a particular payment processing entity, and to modify those search results to display payment processing information (e.g., text, graphic or other indicia) with the relevant search results.
  • payment processing information e.g., text, graphic or other indicia
  • the logic for identifying the search results with which the payment processing information is to be displayed, and for modifying the search results page to actually display the payment processing information is natively provided by the browser application.
  • a web browser application may include logic for indentifying when a search results page has been requested and received.
  • the browser detects when it has received a search results page by analyzing the URL of the document or web page received. Accordingly, the browser application may analyze the source document representing the search results page and modify a portion of the source document to show payment processing information along with one or more of the individual search results.
  • the analysis for identifying the search results with which the payment processing information is to be displayed involves parsing and extracting text from the source document that represents the search results page, and then comparing certain textual elements (e.g., extracted URLs, or portions thereof) from the source document with URLs from a list of URLs known to be associated with merchants and/or marketplaces that have partnered with and accept payments from any one of several payment processing entities. Accordingly, the list of URLs that are known to be associated with merchants that accept payments from the particular payment processor may, in some embodiments, be downloaded to the client computer and then periodically updated.
  • certain textual elements e.g., extracted URLs, or portions thereof
  • the comparison of URLs extracted from a search results page with a list of URLs known to be associated with any one of several payment processing entities occurs at the client computer system.
  • the comparison may be performed by a browser plug-in, or by the browser itself.
  • the appropriate portion of the search results page is modified, for example, by inserting the relevant text or code to cause payment processing information to be displayed in conjunction with the search result.
  • the list of URLs may be maintained at a server of a third party, such as an entity that offers the browser enhancement as a service.
  • the list of URLs may be accessed via an application programming interface (API) on a real-time, or substantially real-time, basis in order to process requests on an on-demand basis.
  • API application programming interface
  • the browser application (or browser plug-in) communicates the URLs extracted from the search results page to the server operated by the third party.
  • the extracted URLs may be communicated to the server as part of an application programming interface (API) request associated with a service offered by the server.
  • API application programming interface
  • the server processes the request to identify any extracted URLs that match or otherwise correspond with a URL in a list of URLs known to be associated with merchants and/or marketplaces that accept payments from certain payment processing entities.
  • the server then provides a response to the client computer system with any relevant payment processing information that corresponds with a search result.
  • the server may include payment processing information for any number of payment processing entities, such that the search results page can be modified to show payment processing information for any number of payment processing entities. For instance, a single search result on the search results page may be modified to show multiple payment processing entities - each payment processing entity capable of processing a payment for the merchant or marketplace associated with the search result.
  • the list of URLs may be maintained by a particular payment processing entity.
  • the browser application or plug-in communicates the extracted URLs directly to a server operated by the payment processing entity.
  • the server of the payment processing entity will then analyze the URLs and reply with payment processing information for those search results having URLs that match or otherwise correspond with a URL in a list of URLs known to the server to be associated with merchants or
  • the enhanced search results page can be displayed independently of the search engine that is utilized to generate the search results.
  • the payment processing information for individual merchants may not be detectable by a search engine's automated crawler, or bot, and may not otherwise be publicly available for use by a search engine.
  • the use of a browser plug-in to enhance search results provides flexibility in that the plug-in may be configured to support any number and type of search engines, as well as any number and variety of browser applications or even non-browser based applications.
  • FIG. 3 illustrates a network environment showing several of the various computing components involved in a system 30 for enhancing search results with payment processing information, according to one embodiment of the invention.
  • the system 30 includes a client computer system 32, and a first server computer 32 executing a search engine 36.
  • the client computer system 32 is shown to include a web browser application 38.
  • the browser application may be enhanced with functionality that facilitates the modification of search results to show payment processing information.
  • the web browser application 38 may operate in conjunction with a plug-in or browser helper object (not shown in Figure 3), which facilitates the enhanced functionality described herein.
  • the browser application 38 downloads and stores a list of URLs 40 known to be associated with merchants or marketplaces that have partnered with one or more payment processing entities that are operating payment processing applications.
  • This list 40 may be automatically, periodically updated.
  • the online merchant information including the list of URLs 40 is downloaded in the background periodically from a server that offers a payment information service for one or more payment processing entities.
  • the merchant URL list may be downloaded directly from a particular payment processing entity.
  • the list of URLs is stored at the client computer system 32, such that the analysis of URLs extracted from a search results page occurs at the client computer system 32.
  • an end-user utilizes the web browser application 38 to invoke the address (e.g., URL) of a search engine, such as search engine 36, and then performs a search by providing one or more keywords or phrases.
  • the search engine 36 responds by serving a search results page to the client computer system 32. Because the logic for identifying URLs and modifying the search results is located at the client, the process is not dependent on any particular search engine, and works equally well with all varieties of search engines, including general purpose search engines as well as subject matter specific search engines.
  • the search engine 36 communicates the resulting source document to the requesting web browser application 38, the browser 38 analyzes the source document by parsing its contents and extracting from the contents the URLs that correspond with each individual search result.
  • this analysis may involve normalizing the URL, for example, by extracting from the URL the hostname, the domain name, or some other subset of the URL that may be recognizable in a comparison with URLs known to be associated with merchants or marketplaces that accept payments from certain payment processing entities.
  • some payment provider information such as some text, a graphic or icon, or some other indicia is displayed with the search result to indicate that the merchant or marketplace associated with the search result accepts payments from the payment processing entity.
  • the list of URLs is maintained at a server and is accessible to the browser or browser plug-in via an API call.
  • Figure 4 shows an alternative network environment 40, including various computing devices with which an embodiment of the invention might be deployed.
  • the client computer system 42 is shown to include a browser application 44 and a browser plug-in, or helper object 46.
  • the online merchant information 52 and particularly the list of URLs that are known to correspond with merchants and/or
  • the browser plug-in 46 after receiving a source document representing a search results page from a server 54 of a search engine 56, the browser plug-in 46 communicates URLs extracted from the source document (e.g., representing a search results page) to the server 48 hosting the payment information service 50.
  • the payment information service 50 responds by identifying the URLs that are known to the payment information service 50 to be associated with merchants or marketplaces that utilize the services of certain payment processing entities.
  • the payment information service 50 embodies an application programming interface (API) by which the browser plug-in can request information for use in enhancing a search results page with payment processing information.
  • API application programming interface
  • the browser plug-in communicates API requests to the payment information service 50, and the service responds with the relevant payment information that is to be included in the search results page.
  • the payment information service 50 may obtain and aggregate merchant information and corresponding payment processing information for a variety of payment processing entities.
  • the search results pages may be modified to show several different payment processing options available for a particular individual merchant associated with a single search result.
  • the payment information service 50 may be hosted by a particular payment processing entity.
  • the payment information service 50 may only provide payment information for merchants or marketplaces that utilize the payment application associated with the particular payment processing entity.
  • a search results page may only be modified to show payment options for the particular payment processing entity.
  • Figure 5 illustrates a method for enhancing search results by displaying with the search results payment processing information indicating, for example, which search results are associated with merchants who accept payments from a particular online payment processing entity.
  • an end-user has already caused to be downloaded and installed on a client computer system an appropriate browser or browser plug-in for implementing portions of the process illustrated in Figure 5.
  • the process begins at method operation 60 when, after entering an address (e.g., URL) corresponding with a search engine and providing one or more keywords to be searched, a search engine communicates to the client computer system, and the client computer system receives, a source document representing a search results page for the search executed by the search engine.
  • the browser or in some embodiments, browser plug-in
  • the browser compares the identified URLs with URLs from a list of URLs known to be associated with merchants or marketplaces that have partnered with and accept payments from one or more payment processing entities.
  • the comparison is performed at the client computer system, using a list of URLs that is stored at the client computer system.
  • the URL comparison is performed at a server, after the extracted URLs are communicated to the server.
  • the server may host a payment information service that provides payment information for multiple payment processing entities.
  • the server may be associated with a particular payment processing entity, and as such, may provide information only about merchants known to utilize the payment processing applications of the particular payment processing entity.
  • the portion of the source document corresponding with the relevant search result is modified so that the search result, when rendered by the browser application, will display some text, a graphic, an icon, or some other indicia indicating that the merchant or marketplace associated with the search result accepts payments processed by a particular payment processing entity.
  • the source document is rendered and displayed to the end-user in a window of the web browser application.
  • a pop-up user interface (UI) element may be displayed.
  • This pop-up UI element may, for example, present additional information about the merchant associated with the particular search result with which the payment processing information is displayed.
  • the pop-up UI element may display additional information about the particular payment processing entity, and/or the particular payment services provided by the merchant corresponding with the individual search result.
  • the browser or browser plug-in may have a user interface component that enables an end-user to configure various settings for the payment information service. For example, in some embodiments, via the configuration user interface, an end-user may be able to specify various payment processing entities for which the end-user would like to view payment processing information. Accordingly, the search results may only be modified to show payment processing options for the payment processing entities selected by the end-user.
  • processors may be temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions.
  • the modules or logical components referred to herein may, in some example embodiments, comprise processor-implemented modules or logic.
  • the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
  • the one or more processors may also operate to support performance of the relevant operations in a "cloud computing" environment or as a service implemented in software, "software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., Application Program Interfaces (APIs).
  • APIs Application Program Interfaces
  • Figure 6 is a block diagram of a machine in the form of a computer within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine may operate in the capacity of a server or a client machine in server-client network environments, or as a peer machine in peer-to-peer (or distributed) network environments.
  • the machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA Personal Digital Assistant
  • STB set-top box
  • PDA Personal Digital Assistant
  • mobile telephone a web appliance
  • network router switch or bridge
  • the example computer system 1500 includes a processor 1502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 1501 and a static memory 1506, which communicate with each other via a bus 1508.
  • the computer system 1500 may further include a display unit 1510, an alphanumeric input device 1517 (e.g., a keyboard), and a user interface (UI) navigation device 1511 (e.g., a mouse).
  • the display, input device and cursor control device are a touch screen display.
  • the computer system 1500 may additionally include a storage device (e.g., drive unit 1516), a signal generation device 1518 (e.g., a speaker), a network interface device 1520, and one or more sensors 1521, such as a global positioning system sensor, compass, accelerometer, or other sensor.
  • a storage device e.g., drive unit 1516
  • a signal generation device 1518 e.g., a speaker
  • a network interface device 1520 e.g., a Global positioning system sensor, compass, accelerometer, or other sensor.
  • sensors 1521 such as a global positioning system sensor, compass, accelerometer, or other sensor.
  • the drive unit 1516 includes a machine-readable medium 1522 on which is stored one or more sets of instructions and data structures (e.g., software 1523) embodying or utilized by any one or more of the methodologies or functions described herein.
  • the software 1523 may also reside, completely or at least partially, within the main memory 1501 and/or within the processor 1502 during execution thereof by the computer system 1500, the main memory 1501 and the processor 1502 also constituting machine-readable media.
  • machine-readable medium 1522 is illustrated in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions.
  • the term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions.
  • the term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
  • machine-readable media include nonvolatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPPvOM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPPvOM, and flash memory devices
  • magnetic disks such as internal hard disks and removable disks
  • magneto-optical disks and CD-ROM and DVD-ROM disks.
  • the software 1523 may further be transmitted or received over a communications network 1526 using a transmission medium via the network interface device 1520 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).
  • Examples of communication networks include a local area network ("LAN”), a wide area network (“WAN”), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Wi-Fi® and WiMax® networks).
  • POTS Plain Old Telephone
  • Wi-Fi® and WiMax® networks wireless data networks.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

Abstract

L'invention porte sur des procédés et des systèmes d'enrichissement d'une page de résultats de recherche par des informations de traitement de paiement. Conformément à certains modes de réalisation du sujet de l'invention, un module d'extension de navigateur est appelé afin d'analyser un document source correspondant à une page de résultats de recherche générée par un moteur de recherche. Le module d'extension analyse et extrait des adresses URL correspondant aux résultats de recherche individuels, et compare ensuite les adresses URL à des adresses URL issues d'une liste d'adresses URL connues comme étant associées à des marchands ou des places de marché qui acceptent des paiements provenant d'une entité de traitement de paiement particulière. Pour les résultats de recherche qui ont des adresses URL correspondantes, la partie du document source correspondant au résultat de recherche est modifiée de telle manière que le résultat de recherche soit affiché avec du texte supplémentaire, un graphique, une icône ou certains autres indices qui indiquent que le résultat de recherche est associé à un marchand qui accepte des paiements provenant de l'entité de traitement de paiement particulière.
PCT/US2011/038355 2010-05-27 2011-05-27 Procédé et système d'enrichissement de résultats de recherche par des informations de traitement de paiement WO2011150340A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US34897510P 2010-05-27 2010-05-27
US61/348,975 2010-05-27

Publications (2)

Publication Number Publication Date
WO2011150340A2 true WO2011150340A2 (fr) 2011-12-01
WO2011150340A3 WO2011150340A3 (fr) 2014-03-20

Family

ID=45004864

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/038355 WO2011150340A2 (fr) 2010-05-27 2011-05-27 Procédé et système d'enrichissement de résultats de recherche par des informations de traitement de paiement

Country Status (1)

Country Link
WO (1) WO2011150340A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017177872A1 (fr) * 2016-04-11 2017-10-19 中兴通讯股份有限公司 Procédé et appareil de collecte de données, et support de stockage

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050027822A1 (en) * 2003-07-30 2005-02-03 Plaza Manuel Eslick Method and system for providing secondary internet access features by intercepting primary browser window locators
US7318047B1 (en) * 1999-12-29 2008-01-08 Pitney Bowes Inc. Method and apparatus for providing electronic refunds in an online payment system
US20080195492A1 (en) * 1999-06-23 2008-08-14 Signature Systems Llc Method and system for implementing a search engine with reward components and payment components
US20090171809A1 (en) * 2007-12-27 2009-07-02 Martina Rothley Efficient purchase order creation
US20090210392A1 (en) * 2008-02-19 2009-08-20 Brian Keith Agranoff System and method for providing search engine-based rewards
US20100037317A1 (en) * 2008-08-06 2010-02-11 Jeong Wook Oh Mehtod and system for security monitoring of the interface between a browser and an external browser module
US20100094891A1 (en) * 2008-10-13 2010-04-15 Bid Solve, Inc. Client-Server System for Multi-Resource Searching

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080195492A1 (en) * 1999-06-23 2008-08-14 Signature Systems Llc Method and system for implementing a search engine with reward components and payment components
US7318047B1 (en) * 1999-12-29 2008-01-08 Pitney Bowes Inc. Method and apparatus for providing electronic refunds in an online payment system
US20050027822A1 (en) * 2003-07-30 2005-02-03 Plaza Manuel Eslick Method and system for providing secondary internet access features by intercepting primary browser window locators
US20090171809A1 (en) * 2007-12-27 2009-07-02 Martina Rothley Efficient purchase order creation
US20090210392A1 (en) * 2008-02-19 2009-08-20 Brian Keith Agranoff System and method for providing search engine-based rewards
US20100037317A1 (en) * 2008-08-06 2010-02-11 Jeong Wook Oh Mehtod and system for security monitoring of the interface between a browser and an external browser module
US20100094891A1 (en) * 2008-10-13 2010-04-15 Bid Solve, Inc. Client-Server System for Multi-Resource Searching

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017177872A1 (fr) * 2016-04-11 2017-10-19 中兴通讯股份有限公司 Procédé et appareil de collecte de données, et support de stockage

Also Published As

Publication number Publication date
WO2011150340A3 (fr) 2014-03-20

Similar Documents

Publication Publication Date Title
US10667101B2 (en) Contextual deep linking of applications
US9483388B2 (en) Discovery of application states
EP3161678B1 (fr) Liens profonds pour applications natives
KR102006396B1 (ko) 브라우징 액티비티에 기초하여 정합 애플리케이션을 식별하는 기법
US8762360B2 (en) Integrating applications within search results
US8612418B2 (en) Mobile web browser for pre-loading web pages
US9977790B2 (en) Automatically obtaining real-time, geographically-relevant product information from heterogeneus sources
US10713324B2 (en) Search results for native applications
US9727354B2 (en) System and methods for loading an application and its modules in a client device
US20160188737A1 (en) Native application search results
US8725715B2 (en) Enhanced content and searching features provided by a linked-to website
US20230106266A1 (en) Indexing Access Limited Native Applications
US9679081B2 (en) Navigation control for network clients
JP2017507376A (ja) 商品情報を通信および提示するための方法、装置、および、システム
CN103793495B (zh) 应用信息检索方法及系统和应用信息获取方法及系统
US10339195B2 (en) Navigation control for network clients
WO2011150340A2 (fr) Procédé et système d'enrichissement de résultats de recherche par des informations de traitement de paiement
US20130110912A1 (en) System and method for providing anonymous internet browsing
US20130339487A1 (en) Method and Apparatus for URL Handling
WO2016077379A1 (fr) Liaison contextuelle approfondie d'applications

Legal Events

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

Ref document number: 11787502

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 11787502

Country of ref document: EP

Kind code of ref document: A2