US2005278651A1PendingUtilityA1

Method and system of launching applications from a button of a browser

44
Assignee: COE BRIANPriority: Aug 12, 2003Filed: May 25, 2005Published: Dec 15, 2005
Est. expiryAug 12, 2023(expired)· nominal 20-yr term from priority
G06F 3/0482G06F 3/0481G06F 16/957
44
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system and method of launching an application from a button of a browser is disclosed, and includes providing one or more buttons, used with a downloadable toolbar for an Internet browser, which are configured to launch an external application. The method comprises associating the application to be launched with an identification code, pre-configuring the client with the identification code and information necessary to launch the application, and transmitting a plurality of button characteristics which define button behavior. In the case of launching an external application, button characteristics comprise at least the application identification code.

Claims

exact text as granted — not AI-modified
1 . A method of providing a button of a graphical user interface with the ability to launch an external application, comprising: 
 associating the external application to be launched with an identification code;    pre-configuring a client side module with the identification code and information necessary to launch the external application; and    communicating the identification code to the client side module for association with the button.    
   
   
       2 . The method of  claim 1  further comprising transmitting a fallback URL such that if the external application is not installed, the user is redirected to a site where the application can be installed.  
   
   
       3 . The method of  claim 1  further comprising transmitting the latest available version number of the external application such that the user is notified if there is a newer version available.  
   
   
       4 . The method of  claim 1  wherein the information necessary to launch the external application is a file path.  
   
   
       5 . The method of  claim 1  wherein the information necessary to launch the external application is a registry location.  
   
   
       6 . The method of  claim 1  wherein the information necessary to launch the external application is pre-configured in a secure manner.  
   
   
       7 . The method of  claim 1  wherein the graphical user interface is a portion of an internet browser.  
   
   
       8 . The method of  claim 1  wherein the client side module is a downloadable toolbar.  
   
   
       9 . The method of  claim 1  wherein the button is part of a downloadable toolbar.  
   
   
       10 . The method of  claim 1  wherein the button is implemented using ActiveX control.  
   
   
       11 . The method of  claim 1  wherein a plurality of identification codes are pre-configured into the client side module.  
   
   
       12 . The method of  claim 1  wherein the client side module is automatically updated to include the identification code and information necessary to launch the external application if not present.  
   
   
       13 . A method of launching an application through a button of an internet browser comprising: 
 receiving button characteristics at a client side module and associating the button characteristics with the button, the button characteristics comprising at least an identification code, the identification code being representative of the application to be launched;    recognizing when the button has been activated by the user;    querying the client side module in communication with the button for information regarding the application matching the identification code in response to the button being activated by the user;    querying the client side module for information regarding the version of the application to compare with the version number; and    calling a function to launch the application having the associated identification code.    
   
   
       14 . The method of  claim 13  wherein the client side module is pre-configured with the identification code.  
   
   
       15 . The method of  claim 13  wherein the button characteristics are determined by a content provider.  
   
   
       16 . The method of  claim 13  wherein the button characteristics are requested by the user.  
   
   
       17 . The method of  claim 14  wherein the client side module is further pre-configured with information necessary to launch the application.  
   
   
       18 . The method of  claim 15  wherein the information necessary to launch the application comprises a file path.  
   
   
       19 . The method of  claim 1  wherein the information necessary to launch the external application is a registry location.  
   
   
       20 . The method of  claim 18  wherein the file path of the application to be launched is hidden from the user.  
   
   
       21 . The method of  claim 13  further comprising transmitting a fallback URL such that if the identification code is not recognized, the user is redirected to a site where the application can be installed.  
   
   
       22 . The method of  claim 13  wherein the client side module is a downloadable toolbar.  
   
   
       23 . The method of  claim 13  wherein the button is part of a downloadable toolbar.  
   
   
       24 . The method of  claim 13  wherein the button is implemented using ActiveX control.  
   
   
       25 . A user interface comprising a button with the ability to launch an external application, the button associated with software executable to perform steps comprising: 
 recognizing an association of the external application to be launched with an identification code;    utilizing a first software module that is pre-configured with the identification code and information necessary to launch the external application; and    communicating the identification code to the first software module for association with the button.    
   
   
       26 . The method of  claim 25  further comprising receiving a fallback URL such that if the application is not installed, the user is redirected to a site where the application can be installed.  
   
   
       27 . The method of  claim 25  further comprising receiving the latest available version number of the external application such that the user is notified if there is a newer version available.  
   
   
       28 . The method of  claim 25  wherein the information necessary to launch the external application is a file path.  
   
   
       29 . The method of  claim 1  wherein the information necessary to launch the external application is a registry location.  
   
   
       30 . The method of  claim 25  wherein the information necessary to launch the external application is pre-configured in a secure manner.  
   
   
       31 . The method of  claim 25  wherein the graphical user interface is a portion of an internet browser.  
   
   
       32 . The method of  claim 25  wherein the client side module is a downloadable toolbar.  
   
   
       33 . The method of  claim 25  wherein the button is part of a downloadable toolbar.  
   
   
       34 . The method of  claim 25  wherein the button is implemented using ActiveX control.  
   
   
       35 . The method of  claim 25  wherein a plurality of identification codes are pre-configured into the client side module.  
   
   
       36 . The method of  claim 25  wherein the client side module is automatically updated to include the identification code and information necessary to launch the external application if not present.  
   
   
       37 . A user interface for a browser comprising a button implemented by software code provided by a provider other than a provider of the browser, the button having the ability to launch an external application, the button associated with software executable to perform steps in a computer, comprising: 
 recognizing an association of the external application to be launched with an identification code;    utilizing a first software module that is pre-configured with the identification code and information necessary to launch the external application; and    communicating the identification code to the first software module for association with the button.    
   
   
       38 . The method of  claim 37  further comprising receiving a fallback URL such that if the external application is not installed, the user is redirected to a site where the application can be installed.  
   
   
       39 . The method of  claim 37  further comprising receiving the latest available version number of the external application such that the user is notified if there is a newer version available.  
   
   
       40 . The method of  claim 37  wherein the information necessary to launch the external application is a registry location.  
   
   
       41 . The method of  claim 40  wherein the registry location is pre-configured in a secure manner.  
   
   
       42 . The method of  claim 37  wherein the button is part of a downloadable toolbar.  
   
   
       43 . The method of  claim 37  wherein the button is implemented using ActiveX control.  
   
   
       44 . The method of  claim 37  wherein the first software module is automatically updated to include the identification code and information necessary to launch the external application if not present.  
   
   
       45 . A server configured to communicate to a client computer an application, the application operative to execute functions in a computer, comprising: 
 instantiating in a user interface a button with the ability to launch an external application, the button associated with software executable to perform steps comprising:    recognizing an association of the external application to be launched with an identification code;    utilizing a first software module that is pre-configured with the identification code and information necessary to launch the external application; and    communicating the identification code to the first software module for association with the button.    
   
   
       46 . The method of  claim 45  further comprising receiving a fallback URL such that if the external application is not installed, the user is redirected to a site where the application can be installed.  
   
   
       47 . The method of  claim 45  further comprising receiving the latest available version number of the external application such that the user is notified if there is a newer version available.  
   
   
       48 . The method of  claim 45  wherein the information necessary to launch the external application is a registry location.  
   
   
       49 . The method of  claim 48  wherein the registry location is pre-configured in a secure manner.  
   
   
       50 . The method of  claim 45  wherein the button is part of a downloadable toolbar.  
   
   
       51 . The method of  claim 45  wherein the button is implemented using ActiveX control.  
   
   
       52 . The method of  claim 45  wherein the first software module is automatically updated to include the identification code and information necessary to launch the external application if not present.  
   
   
       53 . The method of  claim 13  wherein button characteristics further comprise a digital signature.  
   
   
       54 . The method of  claim 53  wherein the digital signature is used to compare with the digital signature of the application to be launched in order to verify its authenticity.  
   
   
       55 . A method of launching an application through a button of an internet browser comprising: 
 associating an identification code with the application to be launched;    assigning button characteristics to the button, the button characteristics comprising the identification code, a fallback URL, and a current version number;    recognizing when the button has been activated by the user;    querying a client side module in communication with the button for information regarding the location of the application matching the identification code;    comparing the version of the application with the current version number;    redirecting the user to a site where the application can be updated if the current version number is greater than the version of the application; and    calling the function to launch the application having the associated identification code.    
   
   
       56 . The method of  claim 1  wherein the client side module signs into an account with a content provider.  
   
   
       57 . The method of  claim 56  wherein the identification code is stored at a central location and associated with the account.  
   
   
       58 . The method of  claim 57  wherein the identification code can be configured by a user of the account.  
   
   
       59 . The method of  claim 15  wherein the user has an account with the content provider, and the button characteristics are associated with the account.  
   
   
       60 . The method of  claim 59  wherein the button characteristics are dependent on the level of the account.  
   
   
       61 . The method of  claim 59  wherein the button characteristics are configurable by the user of the account.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.