US 9,324,080 B2Grant
Method and system of facilitating on-line shopping using a downloadable toolbar
Issue Date:2016-04-26
•15 Claims
•19 Drawing Sheets
Abstract
A method of modifying an Internet browser interface to provide shopping assistant functionality facilitating on-line shopping at a supported merchant Internet site. A wallet created in accordance with the present invention comprises a database having various user data stored therein under certain predetermined field names. A supported merchant data file identifies a plurality of supported merchants and enables the modified browser interface to determine when a shopper has navigated to a supported merchant web site. For each supported merchant, a rules and mapping file is created that may be used in connection with the wallet to map user-provided information in the wallet to corresponding fields in the merchant's check-out web page. When a user navigates to a supported merchant web site and desires to purchase merchandise and/or services from that merchant, the wallet automatically fills out the merchant's check-out web page(s), thereby simplifying on-line shopping and particularly, the check-out process.
Metadata
Assignee
- YAHOO! INC.
Inventors
- Thomas Joshua Shafron
- Qi Lu
- Ashish Baldua
Application Information
Application Number:US 11/322,529
Filing Date:2005-12-30
Priority Date:1999-10-28
Art Unit:2141
Classifications
IPC:
G06Q30/02G06F3/0481G06Q20/12G06Q30/06
Field of Search:
G06F 3/0481G06F 9/00G06F 15/00G06Q 30/0601G06Q 30/06G06Q 30/02
Patent Drawings (19 sheets)
Description
Cross-Reference to Related Application
[0001] This application is a Divisional of U.S. patent application Ser. No. 10/015,816, which is a Continuation-In-Part of U.S. patent application Ser. No. 09/429,585, filed on Oct. 28, 1999, currently pending.
Field of the Invention
[0002] The present invention is directed to a method and system of facilitating on-line shopping using an Internet browser.
Background of the Invention
[0003] When accessing the Internet (i.e., the worldwide web, the web, etc.), an Internet user typically launches or activates, via a computer, a browser software program such as, for example, Netscape Navigator™ or Microsoft Internet Explorer™. The browser program (also referred to herein as a browser) establishes a physical link to the Internet (via a modem and an Internet Service Provider (ISP), for example) and also provides a textual and graphical user interface, i.e., a browser interface, having a predetermined look and functionality, neither of which can currently be significantly changed by the Internet user. Thus, the browser interface remains relatively static as the Internet user navigates the Internet, moving from web site to web site, application to application, or HTML (Hyper-text Mark-up Language) page to HTML page.
[0004] Limited control of the browser interface is currently available via an executable software program that may, for example, add functional buttons to the browser interface. However, the additional functionality is added to the browser interface when the browser is initially activated and remains static thereafter. Thus, it is not possible for a browser displaying a browser interface modified as just-described to dynamically download information from an Internet site and customize itself, either when the browser is initiated or as the users navigates the Internet. Such a modified browser interface also does not provide access to the various browser Application Programming Interfaces (APIs) for Plug-ins and interfaces. It is thus desirable to provide a method for modifying a browser interface, and to provide a browser interface, that overcomes the above-described shortcomings of the prior art.
[0005] The proliferation of Internet sites makes it increasingly difficult for content providers (i.e., owners of Internet sites) to maximize the time an Internet user spends at a particular Internet site. It is, of course, desirable for a content provider to be able to maximize the time an Internet user spends at that provider's Internet site, or to ensure that an Internet user returns to the content provider's site; this being generally referred to in the art as stickiness. Many business models for companies providing Internet sites are based, at least in part, on revenue derived from advertising. The more likely a user is to remain at or return to an Internet site, the more likely that user is to see ads displayed at that site. Consequently, the company providing that Internet site may be able to charge more for ads on its web pages.
[0006] It is also desirable to maximize the number of Internet users accessing a content provider's site. Briefly stated, an Internet content provider wants to attract a maximum number of Internet users to that provider's Internet site, and to maximize the amount of time those Internet users remain at that site; neither of which is possible using current Internet browsers.
[0007] Of the many benefits of the Internet, on-line shopping provides distinct advantages over traditional shopping. Obviously, the ability to easily visit a multitude of merchant web sites, browse their respective merchandise, compare prices, and place orders, from home or office and in a relatively short period of time, saves the on-line shopper time and money. In addition, shoppers who may find it difficult to visit a number of stores (due to weather, lack of proximately located stores, or for whatever reason), now have an almost unlimited number of stores and merchandise available at their fingertips.
[0008] The on-line shopping experience is relatively quick. A shopper may navigate from merchant-site to merchant-site, browse merchandise, and select and place items in an electronic shopping cart, all with a few mouse clicks. However, the check-out process remains relatively time consuming and labor intensive. Once a shopper has finished shopping, the check-out process may be initiated by selecting a “Check Out” option on the merchant's web site. The shopper is then typically required to fill in various personal data, including name, billing and shipping address, credit card number, etc. The shopper has to repeatedly provide that information to each merchant to complete an on-line shopping transaction, which increases the likelihood of error (by the shopper in providing the information) and slows the on-line shopping process.
Summary of the Invention
[0009] The present invention is directed to a method of dynamically controlling an Internet browser interface and to a dynamically controllable browser interface. In an embodiment of the present invention, a shopping assistant button and shopping assistant functionality is added to the browser interface and available to a user (e.g., an on-line shopper) to provide a faster and more accurate on-line shopping process.
[0010] The present invention is also directed to a method of increasing the number of times an Internet user accesses a predetermined Internet site, and to a method of increasing the amount of time an Internet user spends at a predetermined Internet site.
[0011] As used herein, the term controlling and controllable refer to, by way of non-limiting example, adding to, removing from, and modifying an Internet browser interface. An Internet browser interface, as referred to herein, means the visual or aural presentation presented to a browser user, and via which a user interacts with the browser. The term customize (and variations thereof) may also, be used herein to describe the controllability provided in accordance with the present invention. As used herein, the term dynamically controlling (and variations thereof) refers to a method by which a part of an Internet browser interface (i.e., an interface object) may be displayed and periodically changed or updated while a browser displaying the interface object is activated.
[0012] A browser, as used herein, is given its general, art recognized meaning, and generally refers to a software program that provides an interface to the World Wide Web or Internet. The browser enables an Internet user to navigate the Internet and establish a connection to various Internet sites and view the web page(s) provided at the various Internet sites by content providers. A browser is specifically capable of calling an ActiveX control or Plug-in via an Internet site. The browser also enables an Internet user to navigate between and among Internet sites, i.e., to surf the web. The browser provides a browser interface to the Internet user that is formatted by the provider of the browser software program. The browser interface typically defines the layout (e.g., color, size, number and location) and functionality provided by the browser to the Internet user. The browser interface may comprise a first parent window that typically defines the general size, color, and layout of the browser interface and includes window control buttons (e.g., minimize, close, etc.). The browser interface may also comprise a second parent window (a child to the first parent window), and one or more windows dependent from the second parent (i.e., children). The second parent and its dependent windows may provide, for example, various information (e.g., advertisements, coupons, news, HTML links, etc.) and functionality (i.e., toolbars, pull-down menus, Plug-ins, applications, etc.) to the Internet user.
[0013] An ActiveX control, as used herein, refers to a tool for linking desktop applications for the Internet and is based on art recognized, Microsoft-developed specifications. A Plug-in, as used herein, refers to a type of program developed for use with Netscape browsers and that integrates with a larger application (e.g., a browser software program) to add a specific functionality or capability to that larger program. An ActiveX control and a Plug-in as described above and as referred to herein may be used with any Internet browser.
[0014] As used herein, the term Internet site refers to a location (i.e., node) on the Internet defined by an Internet address or URL (uniform or universal resource locator). As used herein, the term Internet web page refers to a collection of hypertext markup language (HTML) commands provided at an Internet site and that provide formatting information for the text, graphics, and functionality to create a hypertext document that may be displayed on an Internet user's computer display via a browser. For example, an Internet user enters a URL to establish a connection to an Internet site, and that Internet site provides HTML commands to the user's browser to enable display of that Internet site's web page on the user's computer display. The browser interprets hypertext markup language (HTML) commands embedded in a web page and uses the HTML commands to format the text and graphics for that web page.
[0015] The present invention provides advantages to an Internet user, an Internet content provider, and to an Internet Service Provider (ISP). For an Internet user, the present invention provides a method of dynamically controlling or customizing that user's Internet browser interface. The Internet user may now customize the browser interface so that each time the user accesses the Internet using a browser, user-defined information and/or functionality (also collectively referred to herein as information) will be displayed with the browser interface. For example, the user may include bookmarks, address and phone books, personal financial information, personalized news, and various functionality such as is available via ActiveX control and Plug-ins.
[0016] In addition, if an Internet user has an account with a content provider, that user's specific account information (e.g., investment portfolio, news headlines, bookmarks, address book, etc.) may now be dynamically displayed with the browser interface by the browser. Currently, an Internet user can only access that user's specific account information while connected to the content provider's Internet site. The user must return to the content provider's site to receive updated account information. The account information is not displayed with the browser interface once user leaves that Internet site. The present invention provides a method of dynamically controlling and a dynamically controllable browser interface that enables an Internet user to display with the browser interface and continuously update information and/or functionality specific to that user.
[0017] For a content provider, the present invention ensures that an Internet user (via a browser) automatically establishes a connection to that content provider's Internet site every time that user accesses the Internet using a browser. Thus, as soon as an Internet user causes a browser to execute (by selecting a browser icon, for example), the browser automatically establishes a connection to the content provider's Internet site to load that user's customized browser interface information. The present invention may also periodically and automatically cause the user's browser to connect to the content provider's Internet site while the browser is active, i.e. while the user surfs the web. In one embodiment, the content provider may provide an Internet user with access to a program for controlling the browser interface. Once the Internet user has accessed that controlling program to customize that user's browser interface, a connection to that content provider may be automatically established by that user's browser every time that user accesses the Internet. Thus, and in contrast to currently available browsers which establish a connection to an Internet site only when the user enters a URL (or otherwise positively acts to cause a connection to be established such as, for example, by selecting a link or banner advertisement), the present invention automatically establishes a connection to the content provider when the browser is initiated, independent of any home web page selection pre-programmed into the browser, whether by the Internet user or browser vendor. Once that initial connection is established, the content provider may load user-specific information and/or functionality to the Internet user's computer for display with that user's browser interface.
[0018] In addition, the content provider can also periodically cause the browser to automatically reconnect to that content provider's Internet site to update, download new, or otherwise communicate information and/or functionality for the Internet user's browser interface. For example, if an Internet user subscribes to an email service of the content provider, email messages for that Internet user received by the content provide may be automatically communicated to the Internet user even though the user is “surfing” elsewhere. When the user's browser initially establishes a connection to the content provider's Internet site upon execution of that user's browser, the information communicated by the content provider to the Internet user includes instructions for the browser to periodically reconnect to the content provider's Internet site. Thus, regardless of the number of Internet sites the user accesses, and regardless of the particular Internet site currently accessed by a user, a connection back to the content provider's Internet site will be automatically established at intervals determined by the content provider; those reconnections being transparent to the Internet user except when the user receives a notification from the content provider (i.e., new mail has arrived). Thus, the browser interface may be dynamically controlled as the Internet user surfs the web. For an ISP, the benefits are at least as great as for a content provider.
[0019] Initially, the browser interface for an Internet user must be customized using a software program that may be provided by the content provider or ISP, or that may be available on the user's computer. The software program, referred to hereinafter as a controlling program or a program for controlling (and other variations thereof), changes the manner in which the user's browser functions. More specifically, the controlling program downloads or creates a library file on the Internet user's computer. The library file may be, for example, a Dynamic Link Library (DLL) (for a Windows operating system) that creates a shell (or plurality of shells) within the browser and within which various information and/or functionality may be loaded as an ActiveX control or Plug-in. The library file includes ActiveX control or Plug-in functionality that defines an interface object added to the browser interface in accordance with the present invention. When an Internet user launches or activates a browser, the library file is opened and the ActiveX control or Plug-in code contained within that file is made available to the browser and incorporated into the browser interface, thus causing the interface object to be displayed with the browser interface. The library file, and consequently, the shell (or shells), remain open as long as the browser is activated, generally as long as the user is surfing the web. Thus, the information and/or functionality for customizing the browser interface and loaded in the shell remain active even as the user moves from Internet site to Internet site. When used in this context herein, the terms information and functionality refer to any information, data, and/or software-driven functionality that can be contained in or part of the library file.
[0020] The library file also causes the browser to establish a connection to the content provider's Internet site when the browser is initially activated by the user. The content provider's Internet site will load information and/or functionality for the interface object to the user's computer for use in the browser and for display in the browser interface. The information and/or functionality loaded by the content provider may be specific to an Internet user if, for example, that user has an account with the content provider. Alternatively, the content provider may load general information and/or functionality if, for example, the Internet user does not have an account with the content provider (i.e., is a guest).
[0021] The present invention uses an object linking and embedding (OLE) in-process server to control the information and/or functionality of a browser interface. Using an ActiveX control or a browser Plug-in (each being referred to herein as a browser interface overlay (BIO) Library) contained in a library file, virtually any information and/or functionality available with an ActiveX control or Plug-in may be added to a browser interface using the present invention. The library file (via the BIO Library) thus includes the code required to customize, i.e., add, remove and/or modify, the browser interface.
[0022] Once an Internet user has accessed the controlling program and customized the operation of that user's browser, the customized browser interface is displayed when the browser is activated. In contrast to prior art browser modification methods, the present invention provides a method and browser interface that may be dynamically controlled. Updated or changed information and/or functionality may be communicated to the browser and displayed in the browser interface as the Internet user surfs the web and while maintaining the customized information and/or functionality of the browser interface. Thus, an Internet user may automatically receive up-to-date information such as, for example, stock quotes, email, new headlines, at that user's browser interface, at any Internet site and as long as the user is surfing the web using the browser.
[0023] The present invention also provides a method and system of facilitating on-line shopping by modifying a browser interface to provide a shopping assistant button and functionality. The modified browser interface provided in accordance with this embodiment of the present invention simplifies on-line shopping by creating a wallet for each shopper or user. The wallet is stored in a database on a secure server and may be accessed, used, or modified only by the user and only in connection with a user-provided security key. The wallet contains user-supplied information that may be directly ported to a supported merchant check-out web page. Thus, when a user is shopping on-line at a supported merchant's web site, and desired to purchase certain merchandise and/or services from that merchant, the present invention provides the user with access to his/her wallet and facilitates porting of the data contained in the wallet to quickly and effortlessly fill out the merchant's order forms provided at the merchant's check-out web pages.
[0024] Other objects and features of the present invention will become apparent from the following detailed description, considered in conjunction with the accompanying drawing figures. It is to be understood, however, that the drawings are designed solely for the purpose of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims.
Brief Description of the Drawings
[0025] In the drawing figures, which are merely illustrative, and wherein like reference characters denote similar elements throughout the several views:
[0026] FIG. 1 depicts a view of a prior art Internet browser interface;
[0027] FIG. 2 depicts a view of an Internet browser interface including an interface object in the browser toolbar in accordance with an embodiment of the present invention;
[0028] FIG. 3 depicts a view of an Internet browser interface having an interface toolbar including interface object in accordance with an embodiment of the present invention;
[0029] FIG. 4 depicts a view of an Internet browser interface having an interface toolbar including a plurality of interface objects in accordance with an embodiment of the present invention;
[0030] FIG. 5 is a flow diagram of a method of controlling an Internet browser interface in accordance with the present invention;
[0031] FIGS. 6-9 are a flow diagrams of a method of controlling and displaying an Internet browser interface in accordance with various embodiments of the present invention;
[0032] FIG. 10 is a schematic block diagram of a computer connected to the Internet and upon which the present invention may be implemented;
[0033] FIG. 11 is an exemplary screen shot of an Internet browser interface having a shopping assistant button in accordance with an embodiment of the present invention;
[0034] FIG. 12 is an exemplary screen shot of a wallet set-up web page in accordance with an embodiment of the present invention;
[0035] FIG. 13 is an exemplary screen shot of a wallet data entry web page in accordance with an embodiment of the present invention;
[0036] FIG. 14 is an exemplary screen shot of a wallet summary web page in accordance with an embodiment of the present invention;
[0037] FIG. 15 is an exemplary screen shot of a security key window in accordance with an embodiment of the present invention;
[0038] FIG. 16 is an exemplary screen shot of a wallet information window in accordance with an embodiment of the present invention; and
[0039] FIG. 17 is an exemplary screen shot of supported merchant check-out web page in accordance with an embodiment of the present invention.
Detailed Description of the Presently Preferred Embodiments
[0040] The present invention is directed to a method of controlling and displaying an Internet browser interface, and to a controllable Internet browser interface. In accordance with the present invention, a browser interface may be customized using a controlling software program that may be provided by an Internet content provider, an ISP, or that may reside on an Internet user's computer. The controlling software program enables the Internet user, the content provider, or the ISP to customize and control the information and/or functionality of a user's browser and browser interface.
[0041] The present invention also provides a method and system of facilitating on-line shopping by modifying a browser interface to provide a shopping assistant button and functionality. The modified browser interface provided in accordance with this embodiment of the present invention simplifies on-line shopping by creating a wallet for each shopper or user. The wallet is stored in a database on a secure server and may be accessed, used, or modified only by the user and only in connection with a user-provided security key. The wallet contains user-supplied information that may be directly ported to a supported merchant check-out web page. Thus, when a user is shopping on-line at a supported merchant's web site, and desired to purchase certain merchandise and/or services from that merchant, the present invention provides the user with access to his/her wallet and facilitates porting of the data contained in the wallet to quickly and effortlessly fill out the merchant's order forms provided at the merchant's check-out web pages.
[0042] Referring now to the drawings in detail, FIG. 10 is a block diagram of a computer 50 connected to the Internet 90 and upon which the present invention may be implemented. Computer 50 includes an internal bus 64 that facilitates communication of information (i.e., digital data) between and among the various devices of the computer 50 and that also facilitates communication between the computer and external devices and systems via a communication interface 68. A processor 66 coupled to the bus 64 process information within the computer 50. The computer 50 also includes a main memory 60 such as, for example, Random Access Memory (RAM) or other equivalent dynamic memory storage device, coupled to bus 64 for receiving and storing instructions communicated from the processor 66. Main memory 60 may also be used to temporarily store variable or other intermediate information while the processor 66 executes instructions. Read-Only-Memory (ROM) 62 is also coupled to the bus 64 for storing static data and instructions for use by the processor 66. Various input and output devices are provided as part of the computer 50, including, by way of non-limiting example, a display 54 (e.g., cathode ray tube (CRT), liquid crystal display (LCD), etc.), an input device 56 such as a keyboard, and a cursor control device 58 such as a mouse, or trackball, for example. A data storage device 52 such as, for example, a magnetic disk drive and magnetic disk, a CD-ROM drive and CD-ROM, or other equivalent devices and data storage mediums, is coupled to the bus 64 for communication with the processor 66, main memory 60, and communication interface 68. The storage device 52 preferably has an operating system 70 and an Internet browser software program 72 (i.e., a browser) stored thereon. As will be discussed in greater detail below, a library file 74 may also be stored on the data storage device 52.
[0043] The computer 50 may connect to the Internet 90 via the communication interface 68 over a transmission media including, but not limited to, coaxial cable, copper wires, and fiber optical cables. Communication between the computer 50 and the Internet 90 may also be via a wireless or cellular interface. The communication interface 68 facilitates two-way communication between the computer 50 and another electronic device or system, e.g., a server computer (not shown) provided by a content provider 100, 200.
[0044] An Internet user (not shown) using the computer 50 may gain access to the Internet 90 by causing the browser 72 to execute, thereby opening a communication link between the communication interface 68 of the computer 50 and an Internet site 130 of a content provider 100, via an Internet Service Provider (ISP) 80. The browser 72 provides, to the computer display 54, a browser interface 20 (see, e.g., FIG. 1 ) having a layout (e.g., color, size, number, location) and functionality of windows 30 that is predetermined in the browser 72 by the browser vendor. Internet content is communicated by the content provider 100 to the computer 50 for display in a content window 32 of the browser interface 20.
[0045] In accordance with an embodiment of the present invention, a first Internet content provider 100 may provide an Internet user with access to a program 120 for controlling the browser 72 and browser interface 20. When executed by the user, the controlling program 120 downloads or creates a library file 74 such as, for example, a Dynamic Link Library (DLL), on the data storage device 52 of the Internet user's computer 50. The library file 74 preferably includes ActiveX control or Plug-in functionality. Thereafter, when the Internet user accesses the Internet using the browser 72, the browser 72 opens the library file 74 and preferably automatically establishes a connection to the content provider's Internet site 130. The content provider, in response to the connection established by the browser 72, loads information and/or functional data into a shell operating within the browser and created by the library file 74. For example, if the user has an account with the content provider 100, customized information and/or functionality may be loaded into the library file 74. If the user does not have an account, more generalized (i.e., guest) information and/or functionality may be loaded.
[0046] In accordance with the various embodiments of the present invention, as described in more detail herein, data may be communicated between computers (e.g., between a server and a user or client computer). The present invention contemplates that such data communication (or transmission/reception, download/upload, etc.) may be carried out in any manner using any medium, using any now known or hereafter developed medium or method.
[0047] The library file 74 essentially opens a shell (or a plurality of shells) within the browser 72 that contains the ActiveX control or Plug-in code that may control, i.e., add, remove, and/or modify, the Internet browser 72 and the browser interface 20. When loaded with the ActiveX control or Plug-in, the library file 74 preferably contains functions, objects, data, and other software, referred to generally herein as information, that may be used to control the browser 74 and browser interface 20. The present invention ensures that the library file 74 (and shell) does not close when the Internet user moves from Internet site 130 to Internet site 230. Thus, the information and/or functionality provided via the ActiveX control or Plug-in is not lost when the Internet user disconnects from the Internet site that loaded the ActiveX control or Plug-in, and connects to another Internet site.
[0048] Referring next to FIG. 1 , a prior art Internet browser interface 20 having a plurality of windows, each providing various functionality to the Internet user, is there depicted. The browser interface 20 may comprise a first parent window 30 that typically defines the general size, color, and layout of the browser interface and includes window control buttons 28 (e.g., minimize, close, etc.) for that window 30. The browser interface 20 may also comprise a second parent window 36 (a child to the first parent window) within the first parent window 30, and one or more child windows 38 dependent from the second parent. The second parent window 36 and child windows 38 typically define information and/or functionality that will assist an Internet user when accessing and navigating the Internet. For example, the second parent 36 and its dependent windows 38 may provide toolbars, pull-down menus, Plug-ins, applications, etc.
[0049] For example, three windows 38 provided at the top (in the drawing) of the interface 20 define three toolbars 22, which may include a variety of interface controls 24 such as, for example, pull-down menus, functional buttons (e.g., stop, back, forward, home, etc.), and a combination of functional buttons and windows (e.g., a search button and window). The uppermost toolbar 22 provides a plurality of pull-down menus 24; the middle toolbar 22 provides a plurality of functional buttons 24; and the lowermost toolbar 22 provides a pull-down menu and a window 26 (a URL address window). A content window 32 is also provided as part of the interface 20 within which content from an Internet content provider 100 (see, e.g., FIG. 10 ) may be displayed. The Internet user may toggle any of the lower three (in the drawing) toolbars 22 on and off using a View toolbar object 24 (pull-down menu) provided in the second toolbar 22. However, the Internet user currently may not add, remove, or otherwise modify the browser interface 20.
[0050] An Internet browser 20 configured in accordance with various embodiments of the present invention is depicted in FIGS. 2-4 . In FIG. 2 , the browser interface 20 includes an interface object 40 that is defined by the ActiveX control or Plug-in loaded in the library file 74 by the content provider 100. The interface object 40 comprises a pull-down menu 44 and is displayed in the browser toolbar 22 with the interface controls (i.e., browser toolbar objects) 24 provided by the browser 72. In FIG. 3 , an interface object 40 comprises an interface object toolbar 42 and a pull-down menu 44 displayed as a separate window 48 within the browser interface 20. In FIG. 4 , an interface object 40 comprises an interface toolbar 42 including a plurality of pull-down menus 44 and a search window 46 displayed within a separate 48 within the browser interface 20. An interface object 40, in accordance with the various embodiments of the present invention, may comprise virtually any type of information and/or functionality available via a browser. Thus, by way of non-limiting example, an interface object 40 may comprise a pull-down menu, a toolbar and a pull-down menu, textual information (e.g., advertisements, coupons, etc.), textual and/or aural information (e.g., a textual advertisement with accompanying sound), textual, aural, and/or graphical (animated or not) information, video, video and audio, audio, etc.
[0051] The various embodiments of the inventive Internet browser interface 20 depicted by FIGS. 2-4 are merely illustrative, non-limiting examples of the present invention. Variations to the depicted browser interfaces 20 may be possible in accordance with the teachings provided herein.
[0052] Referring next to FIG. 5 , a method of controlling an Internet browser interface 20 is there depicted in accordance with an embodiment of the present invention, and designated generally as 500. At step 510, an Internet user accesses a controlling program 120 via an Internet web site 130, an ISP 80, or the user's computer 50. The controlling program 120, when executed by an Internet user, provides that user with the ability to thereafter control that user's Internet browser interface 20, as discussed in more detail below. The controlling program 120, at step 520, downloads or creates a library file 74 on the Internet user's computer 50 that includes ActiveX control or Plug-in code that define an interface object. Each time the Internet user launches or activates the browser 72, the library file 74 is opened and a connection is automatically established to a predetermined Internet web site 10, one that is preferably configured to communicate to the Internet user's computer 50, ActiveX control or Plug-in code for the interface object, as indicated at steps 530 and 540. The open library file 74 essentially provides a shell within the browser 70 within which the functionality provided by the ActiveX control or Plug-in may be added to the browser interface 20. Neither the library file 74 nor the shell close until the browser 72 is closed. At step 550, an interface object 40 is created that will be displayed in the browser interface 20; the information and/or functionality of the interface object 40 is defined by the ActiveX control or Plug-in. In accordance with the various embodiments of the present invention, the interface object 40 remains displayed by the browser 72 with the browser interface 20, as indicated at step 560, for as long as the user continues to surf the web, i.e., as long as the browser 72 is activated. Thus, the functionality added to the browser 72 and browser interface 20 in accordance with the present invention is not lost as the Internet user surfs the web.
[0053] The present invention provides various embodiments for controlling the browser 72 and browser interface 20, described generally above with reference to FIG. 5 , each of which will now be described in detail.
[0054] Referring next to FIG. 6 and with continued reference to FIG. 10 , a description of an embodiment of a method of controlling and displaying a browser 72 and browser interface 20 in accordance with the present invention, designated generally as 600, will now be provided. For purposes of FIG. 6 and for the following discussion directed thereto, a library file 74 has already been downloaded or created on the Internet user's computer 50, as discussed herein. At step 610, an Internet user launches or activates a browser 72 to initiate access to the Internet 90. At step 620, the library file 74 is opened and a connection automatically established to a predetermined content provider, as indicated at step 630. The functionality defined by the ActiveX control or Plug-in code of the BIO Library is communicated by the content provides to the user's computer 50, (i.e., to the library file 74) to create an interface object 40 which may be added to the browser interface 20. The interface object 40 is displayed with the Internet browser interface 20, as indicated in step 640. The functionality of the interface object 40, as defined by the ActiveX control or Plug-in code, remains with the Internet browser interface 20 as the Internet user traverses the Internet 90, regardless of the number or type of Internet sites the user visits, and as long as user is accessing the Internet 90 using the browser software program 72. When the Internet user moves from one Internet site to another, as indicated at step 650, the present invention determines whether the interface object 40 has survived that move; whether it is still displayed by the browser 72 in the browser interface 20, as indicated at step 652. If the interface object 40 is not displayed in the browser interface 20 (i.e., if it has been removed from the browser interface 20 or otherwise terminated), the interface object 40 is redrawn, as indicated in step 660. If the interface object 40 has survived a user move from one Internet site to another and remains displayed in the browser interface 20, the present invention also determines, at step 654, if the browser 72 is active; since the interface object 40 is only displayed in the browser interface 20 when the browser 72 is operational. If the browser 72 is not activated (if the user is no longer surfing the web), the interface object 40 is terminated and the library file 74 is closed, as indicated at step 670. If the browser 72 remains active, the present invention continues, at step 652, to ensure that the interface object 40 is displayed with the browser interface 20. As the Internet user moves between and among Internet sites, the present invention monitors the status of the interface object 40 and ensures that it is displayed by the browser 72 with the browser interface 20 as long as the user is traversing the Internet 90.
[0055] According to the embodiment depicted in FIG. 6 , the present invention ensures that the interface object 40 is displayed by the browser 72 with the browser interface 20 when the Internet user leaves the Internet web site 130 at which the BIO Library initially was called and loaded to the user's computer 50. For example, when the user launches or activates the browser 72, a connection is automatically established to a first, predetermined Internet site 130 that is maintained by a first content provider 100 and the BIO Library is loaded onto the user's computer 50. The functionality provided by the BIO Library is then available to the browser 72 via a shell created by the library file 74. When the Internet user connects to a second Internet site 230 maintained by a second content provider 200, the functionality for the interface object 40 will continue to be present in the browser interface 20. In this embodiment, the present invention prevents the browser 72 or operating system 70 of the computer 50 from disabling the functionality of the BIO Library by unloading the library file 74 when the link to the first Internet site 130 is terminated.
[0056] For example, when the browser 72 initially connects to the first Internet site 130, that site 130 communicates functional information in the form of ActiveX control software code to the Internet user's computer 50 as a BIO Library, which is loaded into the library file 74. If the library file 74 is not explicitly instructed by the operating system 70 or the browser 72 to close or unload when the connection to the first Internet site 130 is terminated, the library file 74 will remain loaded, providing the desired functionality for the interface object 40 in the browser interface 20, even after the connection to the first Internet site 130 is closed. Keeping the library file 74 loaded while the Internet user moves between and among various Internet sites enables the loading of data, functions and objects outside of the ActiveX control (which is only communicated to the Internet user 50 by the first Internet site 130) but inside of the library file 74. As long as the library file 74 remains loaded, any data or objects created in the library file 74 and outside of the ActiveX control will stay loaded and continue to function in the browser interface 20.
[0057] To keep the library file 74 open during surfing, after the browser 72 has connected to the first Internet site 130, and before that connection is terminated, a global object, object A, is created in the program heap of the Internet user's computer 50, not the calling function heap. Thus, the global object survives the completion of the calling function. The global object may be created using the C++ new operator, or by declaring a global object in the global declarations. In either case, the global object will survive termination of the connection between the browser 72 and the first Internet site 130.
[0058] A global object thus defined remains functional after the ActiveX control provided by the first Internet site 130 closes, i.e. after the initial connection to the first Internet site 130 is terminated. Once the global object has been created, an interface is created using the global object. That interface will serve to, for example, remove, replace and/or add functionality to the browser 72 and browser interface 20. The interface may be created as part of the global object, or by the global object allocating a new interface object 40. For example, the interface object 40 may be created by creating, for example, an interface object window 48 within a browser window 38 (see, e.g., FIGS. 3 and 4 ), and adding it to the browser interface 20 as a child window Alternatively, the browser interface 20 may be directly modified such as, for example, by adding or modifying a browser toolbar 22 or a browser toolbar object 24 in the browser interface 20. Yet another alternative is to create an object interface toolbar 42 that is separate from the browser interface 20, as depicted in FIG. 4 .
[0059] Additionally, a pointer is required that is used to control the browser 72 and to instruct the browser 72 to establish a connection to a predetermined Internet site 130, for example. That pointer is preferably stored globally so that it is accessible by any function or object in the library file 74 that sends commands to the browser 72. In Microsoft Internet Explorer, for example, the IWebBrowser, IWebBrowser2, or IWebBrowserApp object linking and embedding (OLE) interface commands may be used to create the pointer. Using Microsoft Foundation Class (MFC), for example, the pointer may be created using the GetClientSite member of the COleControl class to retrieve a pointer from the first Internet site 130, i.e., the Internet site which loaded the BIO Library. The GetClientSite serves as the entry point for the browser 72 to communicate with the BIO Library. A GetContainer member of the IOleClientSite class returned by the previous step may be used to get a pointer to a container for the BIO Library. The BIO Library's container is a container within which an ActiveX control is loaded. An Internet browser interface 20 generally consists of several parts, including the browser toolbars 22 and the content window 32. A document object is created by the browser 72 for every web page an Internet user accesses and contains all of the data that appears in a particular web page. The document object is also the container for the BIO Library. Thus, a document object may also be referred to as a BIO Library's container.
[0060] A QueryInterface member of the IOleContainer class returned by the previous step may be used to get a pointer to the IServiceProvider interface, which may be used to locate any of the other interfaces that are presented by the browser 72. Finally, a QueryService member of the IServiceProvider class returned by the previous step may be used to get a pointer to the IWebBrowserApp, IWebBrowser, or IWebBrowser2 interface, depending on the specific interfaces provided by the browser 72 that called the BIO Library.
[0061] In an alternative embodiment, the present invention may be used to modify the entire browser window 30. If the entire browser window 30 is modified, as opposed to integrating an interface object 40 into an existing browser window 38, the entire class for the modified browser window 30 may be subclassed or, alternatively, the specific browser window 38 may be subclassed. As used herein, the term subclassing a window, also referred to as hooking a window, refers to the replacement of an original browser window message handling procedure for handling all messages sent to a window, with a user-defined window message handling procedure. For example, a window may be subclassed using the Microsoft Foundation Class (MFC) CWnd:SubclassWindow( ) function. Alternatively, a window may be subclassed using the call the SetWindowLong function (a Microsoft Windows function), with the GWL_WNDPROC argument (a Microsoft Windows constant). The pointer returned by the SetWindowLong function call may be stored to the original browser window message handling procedure for the subclassed window. This enables the BIO Library to intercept all messages passed to a window 30 or 38, and the BIO Library may interpret commands from interface controls 24 including buttons, menus, etc., provided by the browser 72 or from interface objects 40 that have been added by the BIO Library in accordance with the present invention.
[0062] The user-defined window message handling procedure that the BIO Library provides and that replaces the original browser window message handling procedure is referred to herein as the BIO Procedure. Using the BIO Procedure for the browser 72, messages (e.g., commands) intended for the browser 72 may be intercepted and modified, or replacement or new messages (e.g., message handlers for the interface object 40) may be communicated to the browser 72 by the BIO Procedure.
[0063] The present invention also ensures that the interface object 40 has not been removed from the browser interface 20. For example, some Internet browsers 72 redraw the entire browser interface 20 when an Internet user accesses a new web site. While the global object may still be functional following such Internet movement by the user, the interface object 40 will be removed from the browser interface 20 and thus, will not be displayed with the browser interface 20. To prevent this from occurring, messages (e.g., commands) from the browser 72 to repaint the browser interface 20 may be intercepted by the BIO Procedure and the interface object 40 may be redrawn immediately after the browser interface 20 is redrawn. Alternatively, the presence of the interface object 40 in the browser interface 20 may be periodically tested and if not present in the browser interface 20, the interface object 40 may be redrawn. Such periodic testing should preferably occur at intervals of less than approximately one second.
[0064] As an example of the above-described embodiment (depicted in FIG. 6 ), an ActiveX control is loaded as a BIO Library and adds menu items (and functionality) to the browser interface 20. The present invention creates an ActiveX control that dynamically creates a new global object, object A, which creates a new menu object (which may be an interface object 40) with a desired functionality to be added to the browser interface 20. The menu object 40 may be added to the browser interface 20 using, for example, the instructions: AfxGetMainWnd( )→GetMenu( )→AppendMenu( ), where the appended menu of the browser interface 20 would include a popup menu that points to the menu object 40. The browser interface window would then be subclassed and handle the messages for the menu object 40 handled by the BIO Procedure and the messages for the browser interface 20 being passed to the message handler for the browser 72. When the Internet user disconnects from the first Internet site 130 (e.g., leaves the web page containing the ActiveX control), the ActiveX control will close, but the global object, i.e., object A, will remain in the program heap and continue to provide the desired functionality to the browser interface 20.
[0065] Instead of subclassing the browser window within which the interface object 40 is added, object A, or one of its descendants, may retain ownership of the interface object 40. Then, a message handler for the interface object 40 may be created. For example, an interface object 40 may be added to a browser toolbar 22 in accordance with the above-described embodiment of the present invention, except that ownership of the interface object 40 is set using the Microsoft Foundation Class SetOwner function to be object A or one of it's descendants.
[0066] With reference next to FIG. 7 and continued reference to FIG. 10 , a description of an alternate embodiment of a method of controlling and displaying a browser interface 20 in accordance with the present invention, designated generally as 700, will now be provided. For purposes of FIG. 7 and for the following discussion directed thereto, a library file 74 has already been created on the Internet user's computer 50, as described herein. At step 710, an Internet user launches or activates a browser 72 to access the Internet 90. At step 720, the library file 74 is opened on the user's computer 50, and a connection is automatically established to a predetermined Internet site 130, as indicated at step 730. At step 740, the functionality defined by the ActiveX control or Plug-in code of the BIO Library is communicated by the content provider to the user's computer 50 (i.e., to the library file 74) to create an interface object 40 which may be displayed in the browser interface 20 using a continuous loop to control the display of the interface object 40. The interface object 40 may only be removed (i.e., its functionality terminated) upon termination of the continuous loop. The functionality of the interface object 40, as defined by the ActiveX control or Plug-in code, remains with the Internet browser interface 20 as the Internet user traverses the Internet 90, regardless of the number or type of Internet web sites the user visits, and as long as the browser 72 remains activated and as long as the Internet user is accessing the Internet using that browser software program. When the Internet user moves from one web site to another, as indicated at step 750, the present invention determines whether the interface object 40 has survived that move, i.e., whether it is still displayed in the browser interface 20, as indicated at step 752. If the interface object 40 is not displayed by the browser 72 in the browser interface 20 (i.e., it has been removed from the browser interface 20 or otherwise terminated), the interface object 40 is redrawn, as indicated in step 760. If the interface object 40 has survived a user move from one web site to another and remains displayed in the browser interface 20, the present invention also determines, at step 754, if the browser 72 is active; since the interface object 40 is only displayed by the browser 72 in the browser interface 20 when the browser 72 is operational. If the browser 72 is not activated, the interface object 40 is terminated and the library file 74 is closed, as indicated at step 770. If the browser 72 remains active, the present invention determined, at step 756, whether the continuous loop has been terminated. If the loop has been terminated, the interface object 40 is also terminated, as indicated at step 770. If the loop is still executing, the present invention determines whether the interface object 40 is still displayed in the browser interface 20, as indicated at step 752.
[0067] The embodiment of the present invention depicted in FIG. 7 prevents an ActiveX control from unloading by freezing the operation of the library file 74 (within which the ActiveX control code is loaded), even if the operating system 70 or browser 72 generate an instruction to unload or terminate the library file 74. Because the library file 74 is frozen and never finishes unloading, all of the data, functions and objects created inside of the library file 74 by the ActiveX control will continue to exist and function after the library file 74 has been instructed to unload.
[0068] In some operating systems 70 and/or browsers 72, the BIO Library will be closed when the ActiveX control is no longer present at an Internet site. This can also occur when the Internet user moves from an Internet site having the ActiveX control, e.g., Internet site 130 in FIG. 10 , to another Internet site that does not, e.g., Internet site 230 in FIG. 10 . To enable the interface object 40 to continue to operate in the absence of the ActiveX control, the BIO Library (and the library file 74) must be prevented from closing.
[0069] To accomplish this, a pointer is created that is used to control the browser 72. That pointer is preferably stored globally so that it is accessible by any function or object in the library file 74 that may need to send commands to the browser 72. In Microsoft Internet Explorer, for example, the IWebBrowser, IWebBrowser2, or IWebBrowserApp OLE Interface commands may be used to create the pointer. To do this using Microsoft Foundation Class, the GetClientSite member of the COleControl class (which may be used to communicate with the BIO Library) may be used to retrieve a pointer to the BIO Library's Internet site, i.e. that Internet site that provides the ActiveX control. A GetContainer member of the IOleClientSite class returned by the previous step may be used to get a pointer to the BIO Library's container. A QueryInterface member of the IOleContainer class returned by the previous step may be used to get a pointer to the IServiceProvider interface. The IServiceProvider interface is used to easily find any of the other interfaces that are presented by the browser 72. A QueryService member of the IServiceProvider class returned by the previous step may be used to get a pointer to the IWebBrowserApp, IWebBrowser, or IWebBrowser2 interface depending on the interfaces presented by the version of the browser 72 that called the BIO Library.
[0070] To prevent the library file 74 from closing, its operation is halted before it is able to terminate. To freeze or halt the operation of the library file 74, a continuous program loop may be created and executed that terminates only when the BIO Library is to be unloaded, at which time, the program loop also pumps the message queue The program loop is referred to herein as a message pump, and may be created using for example, the PeekMessage, GetMessage, TranslateMessage and DispatchMessage commands in a loop. Exemplary C++ code to carry out the message pump is provided below:
[0071]
where m_Continue is a Boolean variable that is used to instruct the loop when to stop, and PeekMessage, GetMessage, TranslateMessage, and DispatchMessage are all Windows functions. If m_Continue equals false, the loop will end, thus ending the message pump. The msg argument is a reference to a Windows MSG structure.
| while (m_Continue) |
| { |
| if (PeekMessage (&msg, NULL, 0, 0, PM_NOREMOVE) != 0) |
| { |
| GetMessage( &msg, NULL, 0, 0 ); |
| TranslateMessage( &msg ); |
| DispatchMessage( &msg ); |
| } |
| } |
where m_Continue is a Boolean variable that is used to instruct the loop when to stop, and PeekMessage, GetMessage, TranslateMessage, and DispatchMessage are all Windows functions. If m_Continue equals false, the loop will end, thus ending the message pump. The msg argument is a reference to a Windows MSG structure.
[0072] The way the message pump preferably operates is that it checks to see if there are any messages waiting in the message queue using the PeekMessage function. If there is a message, the message pump grabs the message from the message queue using the GetMessage function and translates it from a virtual-key message into a character message using the TranslateMessage function. Finally, the message pump sends the message to the original window message handling procedure that is due to receive the message using the DispatchMessage function.
[0073] The built in capabilities of an operating system 70 may be also used to construct a message pump to pump the message queue. For example, a modal dialog box or message box, using a command such as the MFC command CWnd::MessageBox(“my modal”, MB_OK), serves this purpose well and may be used to provided the desired freezing or halting of the operation of the library file 74.
[0074] As long as the message pump is executing a continuous loop, the ActiveX control will not terminate, even when the Internet user accesses other Internet sites.
[0075] The embodiment of the present invention depicted by FIG. 7 performs in the same manner (e.g., subclassing, message handling, etc.) as the above-described embodiment of FIG. 6 .
[0076] For both of the above-described embodiments (of FIGS. 6 and 7 ), it is preferable, although not necessary, to provide an exit function for the interface object 40 so that object A and all of its descendants will be closed. Possible exemplary scenarios for calling an exit function include intercepting the message to close the browser window in the BIO Procedure, or periodically looking for the browser window and, if it is not found, terminating the ActiveX control.
[0077] Referring next to FIG. 8 , yet another embodiment of the method of the present invention is depicted and designated generally as 800. For purposes of FIG. 8 and for the following discussion directed thereto, a library file 74 has already been created on the Internet user's computer 50, as described herein. At step 810, an Internet user launches or activates a browser 72 to access the Internet 90. At step 820, the library file 74 is opened on the user's computer 50 and a connection is automatically established to a predetermined Internet site 130 (see, e.g., FIG. 10 ), as indicated at step 830. At step 832, a new browser interface is created that is a duplicate of the initial browser interface provided by the browser 72. At step 840, a Function Window is created that represents the original browser interface within which the functionality of the Plug-in was initially loaded.
[0078] The steps for creating a Function Window in accordance with this embodiment of the present invention are depicted in FIG. 8A and designated generally as 840. At step 842, the handle for the initial browser interface window is identified. The initial browser interface window, now the Function Window, is hidden and/or disabled at step 844 so that it cannot be closed, which would cause the BIO Library to crash. At step 846, a pointer is created that is used to control the browser 72. Finally, a new browser interface window is created at step 848 that may be used by the Internet user to continue traversing the Internet.
[0079] With reference again to FIG. 8 , and beginning at step 850, the browser interface may now be controlled by first subclassing any browser windows, or any windows used by the browser, that are to be controlled, and then adding, deleting, and/or modifying the window(s) as described in more detail below. The original browser window message handling procedure is replaced with a BIO Procedure (as defined above). At step 860, the present invention determines whether any new browser windows have been opened, i.e., windows that may not already be subclassed or that may not have been controlled in accordance with the present invention. If new windows have been opened, the present invention determines, at step 870, whether the interface object 40 is to be added to those new windows. If not, the invention determines whether the Internet user desires to close the browser 72, as indicated at step 880. If so, the invention closes, at step 890, all browser windows, including the Function Window. If the user does not desire to close the browser 72, as determined at step 880, the invention returns to step 860 and again determines if new browser windows have been opened.
[0080] With continued reference to FIGS. 8, 8A and 10 , the above-described embodiment of the present invention will now be discussed in more detail. When an ActiveX control is loaded by a content provider 100 via an Internet site 130, typically in response to a browser 72 establishing a connection to that web site 130 and calling an ActiveX control, a library file 74 located on the user's computer is caused to open creating a shell within the browser 72 within which the code for the ActiveX control may be loaded. If the library file 74 that contains the ActiveX control is explicitly instructed, by the operating system 70 or the browser 72, to unload or close when the ActiveX control is closed (when the user terminates the connection to the Internet site 130), any data, functions or objects that have been created outside of the ActiveX control but in the library file 74 will be destroyed when the library file is 74 unloaded. To prevent the library file 74 from unloading, the browser 72 is prevented from closing the ActiveX control until instructed. If the ActiveX control is never instructed to close, the library file 74 is never unloaded.
[0081] A preferred method of accomplishing this is to hide and/or disable the initial browser interface window that loaded the ActiveX control and to create a new copy of that same window within which the Internet user may continue to work and traverse the Internet. Because the initial browser interface is preferably hidden and/or disabled, the ActiveX control cannot be closed until the library file 74 shows, enables or closes the initial browser interface window, i.e. the window that loaded the library file 74.
[0082] The above-described method of FIG. 8 preferably loads the BIO Library as a standard ActiveX control in a browser 74, using, for example, the <Object> tag typically contained in a web page 130 or as a Band Object, and as described in the Microsoft Internet Explorer 4.x Software Development Kit. This instructs the browser 72 to initialize and run the library file 74 that contains the code for BIO Library.
[0083] The first time the BIO Library is initialized and called, a Function Window is created that keeps the BIO Library open by keeping a session with the ActiveX control itself open while the Internet user visits other Internet web sites 210, i.e., other web pages. The Function Window also makes it possible for browser windows that do not have a copy of the BIO Library open to access the OLE interfaces to the browser 72.
[0084] To create the Function Window, the initial browser interface window (i.e., that window which loaded the BIO Library) is preferably hidden and/or disabled. This may be accomplished by identifying the handle of the initial browser interface window, beginning with the handle of the BIO Library. To retrieve the initial browser interface window handle from the handle of the BIO Library, the GetParent function (a Windows Function) is continuously called until the present value for that function call represents one level below the desktop window. For example, a statement such as “m_Handle=GetParent(m_Handle)” executed in a loop may provide the desired functionality and result, where the value of m_Handle is initially equal to the value for the handle of the BIO Library, and will eventually return the handle to the initial browser interface window.
[0085] The next step is to hide and/or disable the initial browser interface window, now referred to as the Function Window, so that the Internet user cannot close the Function Window (by closing the browser 72, for example), thereby causing the BIO Library to unload and removing the functionality provided by the BIO Library from the browser interface 20. To hide the initial browser interface window from the user and/or disable that browser window from user-driven events, WM_SHOWWINDOW and/or WM_ENABLE messages (both Windows constants) may be sent to the initial browser interface window with values to hide and/or disable the browser window. For example, the PostMessage or SendMessage function (existing Windows functions) may be used to send a message to the initial browser interface window with the browser window handle. Alternatively, the ShowWindow and EnableWindow functions (existing Windows functions) may be used to achieve the same result.
[0086] A pointer is created to control the browser 72. This pointer is preferably stored globally so that it is accessible by any function or object in the library file 74 that sends commands to the browser 72. In Microsoft Internet Explorer for example, the IWebBrowser, IWebBrowser2, or IWebBrowserApp OLE interface may be used to create the pointer. To do this using Microsoft Foundation Class for example, the GetClientSite member of the COlecontrol class that serves as the entry point for the browser 72 may be used to communicate with the BIO Library, and to retrieve a pointer to the BIO Library's Internet site, i.e., that Internet site 130 that loaded the ActiveX control. A GetContainer member of the IOleClientSite class returned by the previous step may be used to get a pointer to the BIO Library's container. A QueryInterface member of the IOleContainer class returned by the previous step may be used to get a pointer to the IServiceProvider interface; with the IServiceProvider interface preferably being used to find any of the other interfaces that are presented by the browser 72. A QueryService member of the IServiceProvider class by in the previous step may be used to get a pointer to the IWebBrowserApp, IWebBrowser, or IWebBrowser2 interface depending on the interfaces presented by the version of the browser 72 that called the BIO Library.
[0087] Finally, a new browser window is created that the Internet user may use to continue surfing the web, i.e., to continue accessing various different Internet sites, since the browser window previously used to create the Function Window has been hidden and/or disabled. Preferably, any of the IWebBrowser, IWebBrowser2, or IWebBrowserApp OLE interface is used to create a new browser window, for example, using the Navigate or Navigate2 members of that OLE interface. Alternatively, a WM_COMMAND message that corresponds to any command the browser 72 might use to open a new browser window such as a New Window command or Open In New Window command, etc., may be sent to the browser 72. A new window may also be opened using the Dynamic Data Exchange (DDE) support provided by the browser 72.
[0088] The BIO Library must now add/delete/modify, i.e., control, various browser interface features and functionality. The first step is to subclass any of the browser windows or any of the windows the browser uses (i.e., children) that are to be controlled in accordance with the present invention. A BIO window message handling procedure is used to replace the original window message handling procedure, and is hereinafter referred to as the BIO Procedure.
[0089] Once the browser window, or any of it's children, have been subclassed, it is possible to add menus to a subclass by retrieving a pointer to the browser window menu using the GetMenu function. Once the pointer to the menu's handle is obtained, the menu functions such as ModifyMenu, AppendMenu, InsertMenu, etc., may be used to add any desired menus to the browser window. Any commands assigned to a menu must be handled by the BIO Procedure used to subclass the BIO window. The same command identifier must not be used in creating a menu as any that are included in the browser.
[0090] An interface object toolbar 42 may be added to the browser interface 20 by retrieving the handle of the window to which the toolbar 42 is to be added to (hereinafter referred to as the Frame Handle) using standard Windows functions. Typically, the window will be the BIO window or a frame window that is a child of the BIO window. A window is then created using the Frame Handle as its parent. For example, to add a dialog bar (which is a form of a toolbar) as an interface object 40, an object derived from or of a type CDialogBar (a Microsoft Foundation Class) is created and it's Create method called using Frame Handle. If resources such as, for example, images, toolbars, dialogs, etc., are being used and the browser 72 does not share the same resources as the BIO Library, the browser's resources are temporarily replaced with the BIO Library resources before any data may be loaded from the BIO Library resource. The BIO Library resources may then be replaced with the browser's original resources.
[0091] As new browser windows are opened, it may be desirable to add interface object(s) 40 to those new windows. A timer may be created using SetTimer Windows function that would call a user-defined function and that function would use the FindWindowEx function (a Windows function) to check every child of the desktop window for a window with the same class name as the Function Window. For those browser windows that have not already been modified, i.e., that do not have the interface object 40, the necessary handles may be retrieved and the same changes made as were made for the original BIO Window.
[0092] Finally, when the Internet user desires to close the browser 72, it must be determined if all of the browser windows are closed, except the Function Window, and the Function Window must also be closed if all other browser windows are closed. This may be accomplished by listening for a WM_CLOSE message (a Windows constant) in the BIO message handling procedure or by setting a timer that periodically determines how many browser windows are open. To close the original Function Window, a WM_CLOSE message may be sent to that window.
[0093] Referring next to FIG. 9 , another alternative embodiment of a method of controlling and displaying an Internet browser interface 20 in accordance with the present invention is depicted and generally designated as 900.
[0094] Steps 910, 920, and 930 are essentially the same as described above for the embodiments of FIGS. 6-8 . At step 940, a new browser interface window is created and the initial browser interface window is hidden and/or disabled, and referred to as a Function Window. The Plug-in identifies the handle for the initial browser interface window, hides and/or disables that window, and creates a new browser interface window that may be used by the Internet user. At step 950, all the browser windows are subclassed, and then the browser interface may be controlled, as indicated at step 960, for all open windows. At step 962, the present invention determines if any new browser windows have been opened, in which case the invention returns to step 960. In no new browser interface windows have been opened, step 962 proceeds to step 964 to determine if the Internet user desires to close the browser. All windows must be closed prior to closing the Function Window, and that is determined at step 966. If all windows are closed, the Function Window is closed, as indicated at step 970. Otherwise, step 966 returns to step 964.
[0095] In yet another alternative embodiment of the present invention, the present invention provides a method of controlling an Internet browser interface using a browser Plug-in to control (i.e., add, remove and/or modify) the functionality of the calling browser 72 and to retain the Plug-in functionality after the user leaves the Internet site 130 that loaded the Plug-in.
[0096] When a browser Plug-in is loaded to an Internet user's computer 50 in response to a browser 72 establishing a connection to an Internet site 130 and calling the Plug-in, a library file 74 establishes a shell within the browser 72 and within which the code for the Plug-in may be loaded. If the library file 74 is explicitly instructed by the operating system 70 or the browser 72 to unload when the Plug-in is closed, any data, functions or objects that have been created outside of the Plug-in but in the library file 74, will be destroyed when the library file 74 is unloaded. To prevent the library file 74 from unloading, the browser 72 is prevented from closing the Plug-in until the browser 72 receives an instruction to close the Plug-in. If the Plug-in is never instructed to close, the library file 74 also is never instructed to unload. This may be accomplished by hiding and/or disabling the initial browser window that loaded the Plug-in and by creating a new copy of that same window for the Internet user to continue to use to access and traverse the Internet. Because the initial browser window is preferably hidden and/or disabled, the Plug-in can not be closed until the library file 74 chooses to show, enable or close the initial browser window that loaded the Plug-in.
[0097] For example, a browser Plug-in is loaded as a standard Plug-in in a browser 72, preferably by using the <Embed> tag in a web page 110 (see e.g., FIG. 10 ), which instructs the browser 72 to initialize and load the library file 74 that contains the code for the Plug-in (i.e., the BIO Library).
[0098] The first time the BIO Library is initialized and called, a Function Window is created by hiding and/or disabling the original browser window, thus preventing the BIO Library from unloading by keeping a session with the Plug-in itself open. The Function Window also makes it possible for browser windows that do not have a copy of the BIO Library open to access built-in Application Programming Interfaces (APIs) for Plug-ins (i.e., functionality made available to the Internet user through the browser interface 20 and via the Plug-in functionality), such as those provided with Netscape Navigator and Microsoft Internet Explorer.
[0099] A Function Window is preferably created by disabling or hiding the initial browser window (in which the Plug-in resides) the first time the Plug-in is called by the browser 72. To do this the Plug-in must first identify the handle of the initial browser window. A window member of the NPWindow structure is passed to the BIO Library from the browser 72 as a second argument to the NPP_SetWindow Function and is the handle to the Plug-in window (NPWindow and NPP_SetWindow are part of the Netscape and Internet Explorer API for Plug-Ins). To retrieve the initial browser window handle from this window member, the GetParent function (a Windows function) is continuously called until the present value for that function call represents one level below the desktop window. For example, a statement such as “m_Handle=GetParent(m_Handle)” executed in a loop may provide the desired functionality and result, where the value of m_Handle is initially equal to the value for the handle of the NPWindow structure, and will eventually return the handle for the initial browser window.
[0100] The initial browser window is then hidden and/or disabled so that the Internet user cannot close the Function Window and cause the BIO Library to crash. To hide the initial browser window from the user and/or disable that window from user-driven events, WM_SHOWWINDOW and/or WM_ENABLE messages (both Windows constants) may be sent to the initial browser window with values to hide and/or disable that browser window. This can be accomplished by, for example, using the PostMessage or SendMessage function (Windows functions) to send a message to the initial browser window using the browser window handle. Alternatively, the ShowWindow and EnableWindow functions (Windows functions) may be used to achieve the same results.
[0101] The final step is to create a new browser window that the Internet user can use to continue surfing the web after the initial browser window has been hidden and/or disabled. This may be accomplished, for example, by calling any of the following Netscape and Internet Explorer Plug-in API functions: NPN_GetURL, NPN_PostURL, NPN_GetURLNotify, NPN_PostURLNotify, with the target parameter set to _new, _blank, or any window name that does not already exist. The NPP argument of the above functions is the NPP structure that was provided by the browser 72 to the Plug-in for the Function Window. Another way of doing this is to send a WM_COMMAND message to the browser 72 that corresponds to any command the browser 72 might use to open a new window such as a New Window command or Open In New Window command, for example. A new window may also be opened using the Dynamic Data Exchange (DDE) Support provided by the browser. NPN_GetURL, NPN_PostURL, NPN_GetURLNotify, NPN_PostURLNotify and the NPP structure are part of the Netscape and Internet Explorer API for Plug-Ins and the WM_COMMAND is a Windows constant.
[0102] The BIO Plug-in may now control, i.e., add/delete/modify, features and functionality of the browser 72. The first step is to subclass any of the browser windows or any of the windows the browser uses (collectively, BIO windows) that are to be controlled in accordance with the present invention.
[0103] After the browser window or any of it's children has been subclassed, menus may be added to the browser interface 20 by retrieving a pointer to the browser window menu using the GetMenu function (a Windows function). Once the pointer to the menu's handle is obtained, the menu functions such as ModifyMenu, AppendMenu, InsertMenu, etc. (Windows functions), may be used to add any desired menus to the browser window. Any commands assigned to a menu must be handled by the BIO message handling procedure used to subclass the BIO window, taking care not to use the same command identifier in creating a menu as any included in the browser 72.
[0104] Alternatively or additionally, an interface object toolbar 42 may be added to the browser interface 20 by retrieving the handle of the window to which the toolbar 42 is to be added (hereinafter referred to as the Frame Handle) using standard windows functions—typically the window will be the BIO window or a frame window that is a child of the BIO window. A window is then created using the Frame Handle as its parent. For example, to add a dialog bar (which is a form of a toolbar) as an interface object 40, an object derived from or of type CDialogBar (a Microsoft Foundation Class) may be created and it's Create method called using the Frame Handle. If resources such as, for example, images, toolbars, dialogs, etc., are being used and the browser 72 does not share the same resources as the BIO Library, the browser's resources are temporarily replaced with the BIO Library resources before any data from the BIO Library resource may be loaded. The BIO Library resources may then be replaced with the browser's original resources.
[0105] As new browser windows are opened, the interface object 40 may be added to those new windows. This may be accomplished by creating a timer using SetTimer (a Windows function) that would call a user-defined function that would use the FindWindowEx function (a Windows function) to check every child of the desktop window for a window with the same class name as the Function Window. For those new windows that do not already have the modified interface, i.e., that do not include the interface object 40, the necessary handles are retrieved and the same changes made to those windows as were made to the original BIO window.
[0106] Finally, when the Internet user wishes to close the browser 72, it must be determined if all of the browser windows are closed except the Function Window, and if they are, the Function Window may be closed. This may be accomplished, for example, by listening for a WM_CLOSE message (a Windows constant) in the BIO window message handling procedure or by setting a timer that periodically checks the number of open browser windows. The original Function Window may be closed by sending it a WM_CLOSE message.
[0107] In accordance with the present invention, a BIO Library (i.e., a Plug-in) may be loaded and its functionality provided in the browser interface 20, automatically, i.e., without requiring the user to positively access a particular Internet site, i.e., to surf to a web page that calls the Plug-in. For example, Netscape has a key in its windows registry identified as Automation Startup. Upon activation, Netscape loads all of the OLE controls that are listed in the Automation Startup key. By placing a reference or a call to the library file 74 (and thus to BIO Library and Plug-in that defines an interface object 40) in the Automation Startup key, the library file may be loaded every time a user launches or activates a Netscape browser. Included in that library file 74 may be instructions to create an instance of the interface object 40 in the browser interface 20 and an instruction for the browser 72 to establish a connection to a predetermined Internet site 130. Using this technique, a user does not have to choose to visit a specific Internet site 130 to load a BIO Library. The library file 74 needs to be kept open at least until the Plug-in may be loaded in the browser 72 for display and access via the browser interface 20. One way to do this is to increment a reference counter associated with the library file 74 so that when Netscape unload the OLE controls listed in the Automation Startup key, the library file 74 will not be unloaded because it has a higher reference number.
[0108] The library file 74 may be loaded as a Plug-in using DDE to periodically look for a Netscape DDE Server using a timer or a loop. When a return is received by the browser 72 from the Netscape DDE server, Netscape is ready to receive commands and may be loaded with the Plug-in. DDE may then be used to send a command, such as WWW_OPENURL, to the browser 72, which will cause the Plug-in to load as discussed herein.
[0109] Another method for hiding the Netscape Plug-in window that is used for BIO Library is to remove it from the task bar (i.e., where the Windows “Start” button is located) and place it off of the visible screen. One way to remove it from the Task Bar is to call SetWindowLong and change the window style of the Plug-in window to a toolbox window. Toolbox window's do not appear in the task bar. The Netscape Plug-in window may be placed off screen by calling MoveWindow and providing coordinates that are not in the visible range for the users desktop.
[0110] The BIO window message handling procedure that is used to replace the original browser message handling procedure must know which window a message is intended to reach and what to do with a message once the BIO window message handling procedure receives that message. A preferred way to do this is to create a map that links one piece of information to another. For the present invention, a map that links window handles to structures that contain important information to that window is preferably used. For example when the BIO Library adds the interface object 40 to a new browser window, a new entry in the map is created that links the BIO window's handle to a structure that contains information useful for that BIO window. One of the pieces of information contained in the structure would preferably be the browser's original window message handling procedure for the BIO window. It is necessary to maintain the browser's original window message handling procedure so that if the BIO window message handling procedure does not know how to handle a message, it can pass the message to the browser's original window message handling procedure.
[0111] When a message is received by the BIO window message handling procedure, the first argument that is passed to the procedure is the handle of the window that received the message. To retrieve the structure that contains all of the data specific to that window, a lookup in the map is performed using the window handle as a key. The returned structure will contain all of the stored window specific information, such as the original window message handling procedure.
[0112] When controlling the browser interface 20, i.e., adding to, removing from or modifying the browser interface, the present invention changes how the browser 72 works. Almost anything an Internet user can do with a browser works by sending a message to a browser's window or child window. Objects or windows that send messages include the menus, buttons, combo boxes and almost anything else with which the Internet user can directly interact, i.e., interface controls. Messages for example can be broken up into four components: 1) the handle of the window intended to receive the message; 2) the msg value of the message; 3) a wParam, whose use is usually dependent on the msg value; and 4) an Param, whose value is also usually dependent on the value of the msg value.
[0113] For example, clicking on a button in a browser's window might send a message that contains the WM_COMMAND, which is a Windows constant, msg value to a browser window's window message handling procedure. The lower two bytes of the wParam variable in that message would then be a number that is used to identify which button was pressed.
[0114] By subclassing a browser's window or child window, as described above, any messages that are sent when a user interacts with any of the interface controls may be intercepted. Once a message is intercepted, the BIO window message handling procedure can interpret it and react to it. If the functionality of the interface control is to remain the same (i.e., not added to, deleted from, or modified by the present invention), the message may be passed back to the original window message handling procedure. In this way, virtually all of the interface controls that exist in the browser 72 may be controlled. In addition, interface controls may be added to the browser interface 20 and assigned command identifiers (which are passed in the wParam). The BIO window message handling procedure can then interpret the wParam and provide the functionality of the Interface control that is to be added. In addition, functionality may be removed by simply having the inventive window procedure do nothing if it receives a command identifier associated with an interface control that is to be removed from the browser. That command may thus be prevented from passing to the browser window's original message handling procedure.
[0115] Using the various embodiment of the present invention, as discussed in detail above, an Internet user may create a browser interface 20 having user-defined interface controls. Then, by setting the parent of the window for that browser interface 20 to a window that has been subclassed, any message from the new (i.e., controlled) window will be handled in the BIO window message handling procedure. This can be used to add any interface object 40 such as a toolbar, dialogbar, floating dialog etc., to the browser interface 20.
[0116] The following illustrative, non-limiting application examples are provided to further describe the present invention. A Plug-in or ActiveX control that stays persistent as an Internet user traverses the Internet may add an interface object 40 to the browser interface 20 that enables a user to download their “bookmarks” or “favorites” from a database located on the Internet. The interface will be added directly into the browser interface and will allow the user to visit the “bookmarks” or “favorites” links that they downloaded, using the interface object 40 provided by the Plug-in or ActiveX control. This interface object 40 will serve a similar function to the current “favorites” or “bookmarks” menu items and toolbars on existing browsers. The beneficial difference is that since the bookmarks will be downloaded from a database on the Internet, users have access to their bookmarks on any computer's browser that is capable of loading the Plug-in or ActiveX control.
[0117] The present invention may also be used to generate revenue based on placing advertising “links” included in the “favorites” or “bookmarks” on the browser interface 20 via the Plug-in or ActiveX control. Consumer targeting could be based on, for example, information stored in databases, such as name, age, sex, income, race, education and geographic location, and preferences such as favorites and bookmarks or other preferences that are stored on the database or exist on the browser 72.
[0118] A Plug-in or ActiveX control that stays persistent as the user traverses the Internet may be used to add an interface object 40 to the browser interface 20 that permits a user to download their “address book” from of a database located on the Internet. Such an interface object 40 may be added directly into the interface of the browser interface 20 and will allow the user to send e-mail as well as retrieve stored information for contacts listed in their “address book”.
[0119] The present invention may also be used to earn revenue based on placing advertising “links” included in the “address book” on an interface object 40 of the Plug-in or ActiveX control. Consumer targeting could be based for example on information stored in databases, such as name, age, sex, income, race, education and geographic location, and preferences such as favorites and bookmarks or other preferences that are stored on the database or exist on the browser.
[0120] The present invention may use a Plug-in or ActiveX control to add an edit box on the browser interface 20 that allows a user to type a search directly into the browser instead of having to visit a web page that allows the user to search.
[0121] Additionally, the Plug-in or ActiveX control that stays persistent may poll, or periodically seek—at user, web site or program selected intervals—information from a preferred web site, even though the user is surfing a different web site. As the preferred web site is polled, the preferred web site can send updated information to the interface object on the user's browser, such as near real-time notification of the receipt of mail, continuous updating of stock prices, or other time sensitive information, such as, for example, news feed headlines, sports scores for selected favorite sports teams, and the like. The preferred web site can control, if desired, the timing of the polling, so as to control the traffic at the preferred web site during peak usage periods by extending the time interval between polls.
[0122] Since the shell created by the library file, as described herein, is an environment within which applications can be run, or information displayed, any information or program can be added to the interface of the browser using the present invention. The shell is independent of the browser interface, the content of the browser, and even the content of the shell itself. In short, the shell is an adaptable piece of functionality that does not, in the extreme, even need to be visible to the user. Thus, in use, the shell can be empty and receive its contents from a web site, or the shell could get Plug-ins, or the shell could even get new library files and learn to parse new information “on the fly” as the shell receives new contents from a web site or user. Thus the present invention provides significant opportunities to direct desired information from a preferred site to the user even as the user visits other sites. Of course, the more user-specific functionality provided by a web site via the customizable interface of the present invention, the greater user loyalty that web site can engender.
[0123] In another embodiment of the present invention, and with reference now to FIGS. 11-17 , a shopping assistant button may be added to a toolbar of the Internet browser interface to facilitate on-line shopping at a supported merchant web site. Functionality of this embodiment, including defining the shopping assistant button, is provided by computer code transmitted from a server and stored on the user's computer. The computer code monitors the Internet navigation of the Internet browser to determine if the browser is at a supported merchant web site, provides an indicator for the shopping assistant button when the Internet browser is at a supported merchant web site, and fills out a supported merchant check-out web page.
[0124] As user herein, the term “on-line shopping” refers to the process by which a user of an Internet browser my purchase merchandise and/or services over the Internet using a computer. An on-line merchant (e.g., a seller of merchandise and/or services over the Internet) may provide a web site hosted by a merchant server via which a user may access one or more web pages using an Internet browser. Various merchandise and/or services may be offered for sale by the merchant via the one or more web pages. A shopper may view the merchandise, description of the services, select various merchandise and/or services for placement into an electronic shopping cart, view the contents of the shopping cart, and check-out (as described in more detail below).
[0125] The browser interface 20 depicted in FIG. 11 includes an interface object 40 comprising an interface object toolbar 42 and a shopping assistant button 144 that provides various functionality to the browser interface 20, including, by way of non-limiting example, the ability for a user (the terms user and shopper being used interchangeably herein) of the browser interface 20 to create and edit an electronic wallet (discussed in more detail below), disable the shopping assistant button 144 (and shopping functionality from the browser interface 20), list supported merchants, query about the shopping assistant button 144, pull-down menu 44, and functionality provided by the shopping assistant button 144, and query for help about use of the shopping assistant button 144 and the functionality provided thereby. Shopping assistant computer code or software (e.g., a .dll or .exe. file, javascript, etc.) is provided by a server and stored on the user's computer 50 and operable in connection with the browser and browser interface 20 to define and provide the shopping assistant button 144 and other functionality provided in accordance with the present invention, and as described in more detail below.
[0126] In a preferred embodiment, the shopping assistant button 144 and functionality provided thereby is provided when the interface object 40 is added to the browser interface 20, as described in detail above with regard to the various embodiments of the present invention. That is, when the interface object 40 (i.e., toolbar) is added to the browser interface 20, the shopping assistant button 144 and associated computer code are transmitted or downloaded to the user's computer 50. Alternatively, the shopping assistant button 144 and functionality may be selectively added to the browser interface 20 upon request by the user, i.e., before or after the interface object 40 is added.
[0127] The shopping assistant functionality provided in accordance with this embodiment of the present invention is provided, at least in the first instance, by a server 102 (which may comprise one or more computers, located physically proximate each other, or physically separate from each other) (see, e.g., FIG. 10 ) that may be accessed when the user provides a predetermined Internet address or URL in the URL address window 26 of the browser interface 20. The server 102 is preferably a secure server (i.e., one that is only accessible via a Secure Socket Layer (SSL) connection). At that predetermined Internet address, the user may access one or more web pages, at least one of which enables a user to set up a wallet in accordance with this embodiment of the present invention. Exemplary wallet set-up web pages are depicted in FIGS. 12-14 and discussed in more detail below.
[0128] The shopping assistant functionality is also provided by shopping assistant computer code or software downloaded by the server 102 to the user's computer 50 and operable in connection with the browser interface 20 and shopping assistant button 144. The shopping assistant code may be a .dll or .exe file, for example, javascript, or other known types of computer code or software files. The shopping assistant code monitors the Internet navigation of the Internet browser by intercepting the Internet address (or domain or URL) each time the user causes the browser to navigate to a different Internet address. The shopping assistant code also compares the intercepted Internet address with the Internet addresses of supported merchants by comparing the intercepted address with a supported merchant file containing Internet addresses of supported merchants. The supported merchant file is preferably downloaded by the server 102 and stored on the user's computer 50. Each time a user logs into the server 102, the server 102 compares its version of the supported merchant file with the version stored on the user's computer 50 (that version information may me transmitted by the user during the login process, for example). The server 102 downloads to the user's computer an updated version of the supported merchant file, if necessary. The shopping assistant code also intercepts each web page received by the browser and determines the type of web page (e.g., billing web page, merchant home page, merchandise page, etc.) by the HTML code and http request headers.
[0129] The shopping assistant code also defines the shopping assistant button 144 and pull-down menu 44, and controls the communication between the browser, the server 102 and the merchant server for on-line shopping.
[0130] The shopping assistant button 144 may be provided as part of the interface object 40 in accordance with the various embodiments of the present invention. However, for a user to utilize and access the shopping assistant functionality, the user must first set up a wallet. As used herein, the term “wallet” refers to a file (that may be encoded or encrypted) particular to a user and comprised of information (also referred to herein as data) specific to that user, provided by that user, and stored in a wallet database 104 provided on a data storage device 106 (e.g., hard drive, optical disk, etc.) of the server 102 (see, e.g., FIG. 10 ). The wallet database 106 is structured so that the information provided by the user when setting up the wallet is stored in predefined fields or field names. Similarly, a supported merchant data file is structured using the same fields or field names, to the extent that the merchant check-out web page(s) require the same information as was provided during the wallet set-up process.
[0131] To set up a wallet, the user must provide certain information in response to certain wallet set-up web pages provided by the server 102. It is known to persons skilled in the art that an Internet browser receives data from a server, typically HTML data, for display by the browser interface 20. Thus, reference herein to web pages being provided by a server refers to the download or transmission of data from the server for display by an Internet browser.
[0132] An exemplary wallet set-up web page is depicted in FIG. 12 and generally designated as 1000. That web page 1000 may be accessed, for example, via the “edit wallet” option on the pull-down menu 44 of the shopping assistant button 144. By selecting a predetermined link on the wallet set-up web page 1000, such as, for example, a “Set up your Wallet” link 1002, a wallet data entry web page 1010, such as is depicted in FIG. 13 , is downloaded by the server 102. At the wallet data entry web page 1010, the user enters certain information in a plurality of fields 1012 (either pull-down menu or alpha-numeric entry). The information may be, by way of non-limiting example, credit card type, number, expiration date, user's first and last name, billing address, phone number, user ID, user password, and various other information particular to the user. When setting up a wallet, each user is also required to enter a security key (see, e.g., FIG. 16 ) which is necessary, in addition to the user's ID and password, to access and use the user's wallet. When the user has completely filled out all required fields 1012 in the wallet data entry web page 1010, the user may select a “Finished” button (not shown), which transmits the user-entered information to the server 102. In response, the server 102 downloads a wallet summary web page 1020 that includes a summary 1022 of the user's newly entered account information for review by the user prior to finally setting up the user's wallet, as depicted in FIG. 14 . If the user information is correct, the user may select a link on the wallet summary web page 1020 such as, for example, a “Click here to continue . . . ” link 1024, that causes the user information (data) to be transmitted to the server 102 and stored in the wallet database 104 on the data storage device 106. During the wallet set-up procedure just described, data is being transmitted between the server 102 and the user's computer 50 (see, e.g., FIG. 10 ). For example, web pages 1000 (FIG. 12 ) and 1010 (FIG. 11 ) may both be transmitted by the server 102 for display by the user's browser interface 20 when the user selects the “Set up your wallet” link 1002. When the user has completed the information required on the wallet data entry web page 1010 and selects the “Finished” button (not shown), the user information or data may be transmitted to the server 102. Upon receipt of the user information from the user's computer 50, the server 102 may transmit the wallet summary web page 1020. Alternatively, each of the above-described web pages may be transmitted separately by the server 102 and in response to a user-initiated action (e.g., upon selection by the user of a link or button).
[0133] The server 102 may be that of a content provider 100 or other Internet service provider such as, for example, a search engine provider or ISP, collectively referred to herein as the provider 100. On-line merchants are selected by the provider 100 in connection with which the shopping functionality of the present invention may be used. A supported merchant file contains a list of all supported merchants, including their respective Internet addresses. That file may be used by the shopping assistant computer code to determine if a user has navigated to a supported merchant web site by comparing the URL entered into the URL address window 26 (or provided in a link) with the urls contained in the supported merchant file.
[0134] Once a merchant (a merchant is generally designated 200 in FIG. 10 ) has been selected, the provider 100 determines the merchants' check-out process, including the layout of check-out web page(s) (see, e.g., FIG. 17 ), and information required to complete the merchant's check-out process and check-out web page(s). The provider 100 creates a supported merchant rules and mapping file for each selected merchant (also referred to herein as a supported merchant) that defines a plurality of merchant field names that correspond to the user data required by the merchant during its check-out processes and its check-out web page(s). For example, and with reference to FIG. 17 , a supported merchant check-out web page 2100 requires that a shopper provide billing information including, for example, payment method, credit card number, expiration date, and personal information for the shopper (e.g., name, address and telephone number). The merchant field names correspond to wallet field names defined in the user's wallet. Each supported merchant rules and mapping file may contain different merchant field names, as each merchant may require different information during its check-out process. However, all merchant field names correspond to wallet field names.
[0135] The supported merchant rules and mapping file maps the wallet data (i.e., wallet field names) to the required merchant data (i.e., merchant field names). For example, an entry in the merchant rules and mapping file defining a first name field and last name field may be structured as follows:
[0136] rmi_pageFields[1]=new rmi_fieldMap(“contactFirstName”, “text”, “wallet_b_fname_first”);
- [0137] rmi_pageFields[2]=new rmi_fieldMap(“contactLastName”, “text”, “wallet_b_fname_last”);
- [0138] where “wallet_b_fname_first” is the wallet database field name for the user's first name. However, in the supported merchant file, the user's first name is identified as “contactFirstName”. Thus, the present invention maps the fields in the wallet database to the fields in the supported merchant file so that each merchants order form may be automatically filled out when a user shops at a supported merchant web site.
[0139] With reference now to FIGS. 15-17 , an exemplary check-out process will now be described. As different merchants may have different check-out processes and provide different check-out web pages, the following description is merely illustrative and not intended to limit the scope of or otherwise define the present invention. In addition, the following description does not track the entire on-line shopping process (which may also vary from merchant to merchant), but only the check-out process, which generally begins after the user has selected a “Check Out” or other similar button on a merchant web page.
[0140] When a user launches their Internet browser, the interface object 40 automatically establishes a connection between the user's computer 50 and the server 102. Various user data is downloaded by the server 102 to the user's computer 50. The user may cause the Internet browser to navigate to any Internet address by typing the address in the URL address window 26 (see, e.g., FIG. 11 ), or by selecting a link on a web page. Regardless of how the browser is caused to navigate the Internet (move from web site to web site), the shopping assistant code intercepts the URL for each Internet site navigated to by the user, and compares that URL with the supported merchant data file. If a match is found, the shopping assistant code provides a user perceptible indicator on the shopping assistant button 144 such as, for example, a yellow circle, that indicates that the user has navigated to a supported merchant web site. The shopping assistant code also makes a request to the server 102 for a download of a file containing rules and mapping data for that merchant and that provides details on that merchant's check-out process.
[0141] The shopping assistant code also intercepts each web page received by the browser to determine the type of web page, e.g., a billing page, e-mail address request, credit card information request, etc., by looking at the HTML code and the http request headers. That information was obtained during the provider's selection of merchants and creation of the supported merchant data files. Using the merchant's rules and mapping file, the shopping assistant code can determine the specific page being served and how the user's information should be provided in that page.
[0142] If the shopping assistant code determines that the user's wallet is required for a particular page, it opens a security key window 3000 in the user's browser interface 20 asking the user to enter a security key (SK) in a data entry window 3020, as depicted in FIG. 15 . Once the user has entered a SK and selected a “Continue” button 3030, that security key is securely transmitted, preferably using https, by the user's computer 50 to the server 102. The server 102 compares the user data (e.g., ID and SK) with data previously stored in that user's wallet on the wallet database 106. If the data matches, the SK is verified and an authorization is transmitted by the server 102 to the shopping assistant code; a rejection is transmitted if the data does not match. The authorization may be provided as a wallet information window 3100, such as is depicted in FIG. 16 . When a SK is successfully verified by the server 102, a “secure cookie” is transmitted over SSL to the secure server, and the user's on-line shopping session using his/her wallet begins when the “secure cookie” is set. The “secure cookie” is aggressively timed out, and is preferably valid for up to one (1) hour.
[0143] If the user desires to continue the check-out process using the shopping assistant functionality of the present invention, the user may select a “Continue” button 3130. If the user desires to check-out using the merchant's check-out process, the user may select a “Cancel” button 3140. When the user selects the Continue button 3130, the shopping assistant code retrieves the user's wallet from the wallet database 104 on the server 102, and automatically fills in the merchant's check-out web page 2100, depicted in FIG. 17 . The user's wallet is securely transmitted by the server 102, preferably using https. The user's wallet, and thus the user's personal data, need not be stored on the user's data storage device 52, but only in temporary memory (also referred to herein as main memory or RAM) 60, and used by and in connection with the shopping assistant code and functionality of this embodiment of the present invention. The user's data may automatically expire (e.g., after a predetermined time), or it may be flushed from memory 60 when the user closes the browser.
[0144] Depending upon the type of web page displayed by the browser, the shopping assistant code provides the appropriate user data from the user's wallet (temporarily data in RAM) to the web page. For example, if the shopping assistant code determines the web page is a “billing address” web page, the user's billing address data will be copied from RAM to populate the fields in the billing address web page, and ultimately communicated to the merchant's server. During the check-out process, the shopping assistant code operates in connection with the merchant rules and mapping file and with the user's wallet to automatically provide user data required by the various merchant check-out web pages.
[0145] The wallet database 106 may contain only wallet data or alternatively, the wallet data may be located in a database with other data. While the wallet is preferably used by and in connection with the shopping assistant button 144 and functionality, the wallet may also be used by applications other than shopping assistant such as, for example, bill paying, shopping without shopping assistant, and in connection with virtually any on-line transaction that requires that the user enter personal data. The wallet provides secure transmission and handling of the user's data and makes that data available for use by the user in connection with various on-line transactions without unnecessarily compromising the security of that data.
[0146] Once a user has set up a wallet, the functionality provided in accordance with this embodiment of the present invention is now available to the user as the user shops on-line. Preferably, the on-line shopping functionality is available for use in connection with a supported merchant regardless of the Internet site to which the user is connected (via the Internet browser). Thus, the user need not be connected to the provider's Internet site, or even to a supported merchant's web site. The shopping assistant code handles all communication between the user (the user's computer 50), the server 102, the wallet database 104, and the merchant's Internet site and check-out web page(s).
[0147] In accordance with another embodiment of the present invention, a button 44 (i.e., interface object) may be added to a browser interface toolbar, such as an interface object toolbar 42 (see, e.g., FIG. 4 ) by a party other than the provider 102. For example, a link may be provided on a corporate web site that enables visitors to that web site to add a button 44 to their interface object toolbar 42 that would provide a one-click link to that corporate web site from the browser interface 20. Corporations, or any entity hosting a web site, may sponsor the provider 100 because the addition of the corporate button to the interface object toolbar 42 enables a user to return to that corporate web site from any other web site with a single mouse click. The addition of the corporate button to the browser interface (i.e., the toolbar 42) thus establishes an affinity between a user and the corporate web site. The corporate sponsor designs the button (e.g., look (one-click button or pull-down menus), icon, etc.), and provides the button design and URL data to the provider 100 for incorporation in a database maintained by the provider and associated with browser interface. Thus, a corporate sponsor may have a button defined in the provider database.
[0148] If a visitor to the corporate web site wants to install the corporate button in their browser interface 20, but does not have a browser interface toolbar 42 installed, the present invention also enables installation of the browser interface toolbar 42 and corporate button 44 in the browser interface 20. On the other hand, the corporate button 44 may be added to a toolbar 22 of the browser interface 20, or may be added as a button 44 of an interface object toolbar 42.
[0149] The present invention may also be used as a teaching tool. For example, the interface object toolbar 42 may include a plurality of buttons 44 which may be caused to change color, blink, highlight, etc., to direct a user's attention to that button or to the functionality provided by that button.
[0150] The present invention may also enable a provider or corporate sponsor to notify a user of certain properties of the provider or corporate sponsor when that user visits a competing website. For example, when a user visits an automotive website, the corresponding provider property (e.g., provider Autos) would be highlighted to alert the user of the availability of that feature at the provider website. Software may be provided on the user's computer to intercept the URL each time the user causes the browser to navigate to a web site. That intercepted URL may be compared with a file containing a plurality of urls for the provider properties.
[0151] Importantly, determining the web site to which the user has navigated at any particular instant is determined by the user's computer alone. Thus, no information regarding the user's activity on the Internet is communicated to any server.
[0152] It will be obvious to persons skilled in the art and from the disclosure provided herein that the various embodiments of the present invention may be carried out using software provided on the user's computer and on the various servers.
[0153] It is to be understood that the present invention may be implemented utilizing any number of computer technologies. For example, although the present embodiments are disclosed as operable in connection with the Internet, the present invention may be utilized over any computer network, including, for example, a wide area network. Similarly, the user computer 50 may be any device that may be coupled to the network, including, for example, personal digital assistants, web-enabled cellular telephones, hard-wired telephones that dial into the network, mobile computers, personal computers, Internet appliances and the like. Furthermore, the servers described herein may be of any type, running any software, and the software modules, objects and plug-ins described herein may be written in any programming language. Lastly, the database and storage devices described herein may utilize any storage technology, including, for example, local computer memory, network attached storage, and any known storage medium, such as magnetic or optical.
[0154] Thus, while there have been shown and described and pointed out fundamental novel features of the invention as applied to preferred embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the disclosed invention may be made by those skilled in the art without departing from the spirit of the invention. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.
Claims
What is claimed is:
1. A method comprising:
facilitating control of an Internet browser interface displayable by an Internet browser on a display of a computer, the Internet browser enabling a user of the computer and Internet browser to access and navigate the Internet and to receive and display on the computer display one or more web pages from one or more Internet sites, including the display of a web page from a predetermined Internet site, the Internet browser having at least one downloaded Internet browser toolbar having at least one toolbar button providing a predetermined functionality to the user of the computer and Internet browser, said control comprising:
(a) providing, at the predetermined Internet site, access to a program for controlling the Internet browser interface; and
(b) making available for downloading by the predetermined Internet site, a file for displaying a user toolbar and a shopping assistant interface object as part of the Internet browser interface while the Internet browser is activated regardless of a subsequent Internet site to which the Internet browser is caused to navigate,
wherein the shopping assistant interface object is a toolbar button displayed as part of the downloaded user toolbar and that facilitates at least payment for goods or services while shopping,
wherein the file contains computer code for providing a displayed indicator in a first state on the toolbar button that visibly changes to a second state to indicate available portability of data associated with the shopping assistant interface object into a supported merchant website when the Internet browser is caused to navigate to the supported merchant web site, the file further mapping fields of the data associated with the shopping assistant interface object to fields in a supported merchant file associated with the supported merchant website, and
wherein the shopping assistant interface object intercepts the supported merchant web site when the Internet browser is caused to navigate to the supported merchant web site, the shopping assistant interface object intercepting the supported merchant web site to determine the type of web page navigated to from the HTML code of the web page and the HTTP request headers, the type of web page comprising one or more of a billing page, an e-mail address request, and a credit card information request, and further wherein the shopping assistant interface object uses the type of the web page to determine the mapping of the fields of the data associated with the shopping assistant interface object to fields in the supported merchant file associated with the supported merchant website.
2. The method as recited by claim 1, wherein the file comprises an ActiveX control.
3. The method as recited by claim 1, wherein the file comprises a Plug-in.
4. The method as recited by claim 1, wherein said file contains computer code for intercepting an Internet address for each Internet site to which the Internet browser is caused to navigate, determining if a web site to which the Internet browser is caused to navigate is the supported merchant web site, and if the web site is the supported merchant web site, automatically filling out a check-out web page of the supported merchant web site using a wallet and a supported merchant rules and mapping file.
5. The method as recited by claim 1, wherein said file contains computer code for adding a shopping assistant button and a toolbar of the Internet browser.
6. The method as recited by claim 1, wherein said files contains computer code for determining if a web site to which the Internet browser is caused to navigate is the supported merchant web site by comparing the supported merchant file with an Internet address for each Internet site to which the Internet browser is caused to navigate.
7. The method of claim 1 further comprising providing software to intercept the URL of the Internet site to which the Internet browser is caused to navigate.
8. The method of claim 7 further comprising notifying a user of the Internet browser of a feature of a sponsoring entity when the Internet site to which the Internet browser is caused to navigate is a competitor in an area associated with the sponsoring entity.
9. The method of claim 7 further comprising notifying a user of the Internet browser of a feature of a content provider when the Internet site to which the Internet browser is caused to navigate is a competitor in an area associated with the content provider.
10. A system comprising:
a server, said server including a processor to execute a program accessible over the Internet by a user of a computer for controlling an Internet browser interface, the Internet browser interface displayable by an Internet browser on a display of the computer; and
a file downloadable by said server to the computer for controlling the Internet browser interface, wherein said downloadable file causes a user toolbar and a shopping assistant interface object to be added to the browser interface and to be displayed on the display of the computer as part of the Internet browser interface while the Internet browser is activated regardless of the Internet site to which the computer is connected via the Internet browser,
wherein the shopping assistant interface object is a toolbar button displayed as part of the downloaded user toolbar and that facilitates at least payment for goods or services while shopping,
wherein the file contains computer code for providing a displayed indicator in a first state on the toolbar button that visibly changes to a second state to indicate available portability of data associated with the shopping assistant interface object into a supported merchant website when the Internet browser is caused to navigate to the supported merchant web site, the file further mapping fields of the data associated with the shopping assistant interface object to fields in a supported merchant file associated with the supported merchant website, and
wherein the shopping assistant interface object intercepts the supported merchant web site when the Internet browser is caused to navigate to the supported merchant web site, the shopping assistant interface object intercepting the supported merchant web site to determine the type of web page navigated to from the HTML code of the web page and the HTTP request headers, the type of web page comprising one or more of a billing page, an e-mail address request, and a credit card information request, and further wherein the shopping assistant interface object uses the type of the web page to determine the mapping of the fields of the data associated with the shopping assistant interface object to fields in the supported merchant file associated with the supported merchant website.
11. The system as recited by claim 10, wherein said shopping assistant interface object comprises an ActiveX control.
12. The system as recited by claim 10, wherein said shopping assistant interface object comprises a Plug-in.
13. The system as recited by claim 10, wherein said file contains computer code for intercepting an Internet address for each Internet site to which the Internet browser is caused to navigate, determining if a web site to which the Internet browser is caused to navigate is the supported merchant web site, and if the web site is the supported merchant web site, automatically filling out a check-out web page of the supported merchant web site using a wallet and a supported merchant rules and mapping file.
14. The system as recited by claim 10, wherein said file contains computer code for adding a shopping assistant button and a toolbar of the Internet browser.
15. The system as recited by claim 10, wherein said files contains computer code for determining if a web site to which the Internet browser is caused to navigate is the supported merchant web site by comparing the supported merchant file with an Internet address for each Internet site to which the Internet browser is caused to navigate.
Patent Citations (172)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5241594(A) | 1993-08-01 | Kung | Applicant |
| US5499335(A) | 1996-03-01 | Silver et al. | Applicant |
| US5537596(A) | 1996-07-01 | Yu et al. | Applicant |
| US5630042(A) | 1997-05-01 | McIntosh et al. | Applicant |
| US5644739(A) | 1997-07-01 | Moursund | Applicant |
| US5744787(A) | 1998-04-01 | Teicher | Applicant |
| US5745115(A) | 1998-04-01 | Purple et al. | Applicant |
| US5781724(A) | 1998-07-01 | Nevarez et al. | Applicant |
| US5784058(A) | 1998-07-01 | LaStrange et al. | Applicant |
| US5796393(A) | 1998-08-01 | MacNaughton et al. | Applicant |
| US5802530(A) | 1998-09-01 | Van Hoff | Applicant |
| US5805803(A) | 1998-09-01 | Birrell et al. | Applicant |
| US5808894(A) | 1998-09-01 | Wiens et al. | Applicant |
| US5813007(A) | 1998-09-01 | Nielsen | Applicant |
| US5848424(A) | 1998-12-01 | Scheinkman et al. | Applicant |
| US5875296(A) | 1999-02-01 | Shi et al. | Applicant |
| US5877759(A) | 1999-03-01 | Bauer | Applicant |
| US5883626(A) | 1999-03-01 | Glaser et al. | Applicant |
| US5883810(A) | 1999-03-01 | Franklin et al. | Applicant |
| US5890172(A) | 1999-03-01 | Borman et al. | Applicant |
| US5914714(A) | 1999-06-01 | Brown | Applicant |
| US5917491(A) | 1999-06-01 | Bauersfeld | Applicant |
| US5923326(A) | 1999-07-01 | Bittinger et al. | Applicant |
| US5933142(A) | 1999-08-01 | LaStrange et al. | Applicant |
| US5949419(A) | 1999-09-01 | Domine et al. | Applicant |
| US5963952(A) | 1999-10-01 | Smith | Applicant |
| US5964836(A) | 1999-10-01 | Rowe | Applicant |
| US5974446(A) | 1999-10-01 | Sonnenreich et al. | Applicant |
| US5974549(A) | 1999-10-01 | Golan | Examiner |
| US5999179(A) | 1999-12-01 | Kekic et al. | Applicant |
| US5999972(A) | 1999-12-01 | Gish | Applicant |
| US5999973(A) | 1999-12-01 | Glitho et al. | Applicant |
| US6000832(A) | 1999-12-01 | Franklin et al. | Applicant |
| US6006034(A) | 1999-12-01 | Heath et al. | Applicant |
| US6009459(A) | 1999-12-01 | Belfiore et al. | Applicant |
| US6020884(A) | 2000-02-01 | MacNaughton et al. | Applicant |
| US6025836(A) | 2000-02-01 | McBride | Applicant |
| US6026435(A) | 2000-02-01 | Enomoto et al. | Applicant |
| US6034683(A) | 2000-03-01 | Mansour et al. | Applicant |
| US6041360(A) | 2000-03-01 | Himmel et al. | Applicant |
| US6057836(A) | 2000-05-01 | Kavalam et al. | Applicant |
| US6061695(A) | 2000-05-01 | Slivka et al. | Applicant |
| US6072486(A) | 2000-06-01 | Sheldon et al. | Applicant |
| US6092196(A) | 2000-07-01 | Reiche | Applicant |
| US6101486(A) | 2000-08-01 | Roberts et al. | Applicant |
| US6112240(A) | 2000-08-01 | Pogue et al. | Applicant |
| US6119098(A) | 2000-09-01 | Guyot et al. | Applicant |
| US6125352(A) | 2000-09-01 | Franklin et al. | Applicant |
| US6141010(A) | 2000-10-01 | Hoyle | Applicant |
| US6175869(B1) | 2001-01-01 | Ahuja et al. | Applicant |
| US6185600(B1) | 2001-02-01 | Spence et al. | Applicant |
| US6188995(B1) | 2001-02-01 | Garst et al. | Applicant |
| US6208995(B1) | 2001-03-01 | Himmel et al. | Applicant |
| US6216153(B1) | 2001-04-01 | Vortriede | Applicant |
| US6226655(B1) | 2001-05-01 | Borman et al. | Applicant |
| US6226752(B1) | 2001-05-01 | Gupta et al. | Applicant |
| US6232972(B1) | 2001-05-01 | Arcuri et al. | Applicant |
| US6236400(B1) | 2001-05-01 | Guerrero | Applicant |
| US6256668(B1) | 2001-07-01 | Slivka et al. | Applicant |
| US6262731(B1) | 2001-07-01 | Hasegawa | Applicant |
| US6266058(B1) | 2001-07-01 | Meyer | Applicant |
| US6278450(B1) | 2001-08-01 | Arcuri et al. | Applicant |
| US6282548(B1) | 2001-08-01 | Burner et al. | Applicant |
| US6286001(B1) | 2001-09-01 | Walker et al. | Applicant |
| US6292185(B1) | 2001-09-01 | Ko et al. | Applicant |
| US6314451(B1) | 2001-11-01 | Landsman | Applicant |
| US6356909(B1) | 2002-03-01 | Spencer | Applicant |
| US6360255(B1) | 2002-03-01 | McCormack et al. | Applicant |
| US6373507(B1) | 2002-04-01 | Camara et al. | Applicant |
| US6385619(B1) | 2002-05-01 | Eichstaedt et al. | Applicant |
| US6407754(B1) | 2002-06-01 | Hetherington et al. | Applicant |
| US6433800(B1) | 2002-08-01 | Holtz | Applicant |
| US6434563(B1) | 2002-08-01 | Pasquali et al. | Applicant |
| US6460038(B1) | 2002-10-01 | Khan et al. | Applicant |
| US6460058(B2) | 2002-10-01 | Kopulu et al. | Applicant |
| US6469713(B2) | 2002-10-01 | Hetherington et al. | Applicant |
| US6476833(B1) | 2002-11-01 | Moshfeghi | Applicant |
| US6483525(B1) | 2002-11-01 | Tange | Applicant |
| US6486892(B1) | 2002-11-01 | Stern | Applicant |
| US6490601(B1) | 2002-12-01 | Markus et al. | Applicant |
| US6490602(B1) | 2002-12-01 | Kraemer | Applicant |
| US6493000(B1) | 2002-12-01 | Wynn et al. | Applicant |
| US6496203(B1) | 2002-12-01 | Beaumont et al. | Applicant |
| US6496936(B1) | 2002-12-01 | French et al. | Applicant |
| US6505238(B1) | 2003-01-01 | Tran | Applicant |
| US6542897(B2) | 2003-04-01 | Lee | Applicant |
| US6549217(B1) | 2003-04-01 | De Greef et al. | Applicant |
| US6584505(B1) | 2003-06-01 | Howard et al. | Applicant |
| US6621532(B1) | 2003-09-01 | Mandt | Applicant |
| US6624831(B1) | 2003-09-01 | Shahine et al. | Applicant |
| US6651217(B1) | 2003-11-01 | Kennedy et al. | Applicant |
| US6657702(B1) | 2003-12-01 | Chui et al. | Applicant |
| US6686938(B1) | 2004-02-01 | Jobs et al. | Applicant |
| US6704031(B1) | 2004-03-01 | Kimball et al. | Applicant |
| US6748367(B1) | 2004-06-01 | Lee | Applicant |
| US6757716(B1) | 2004-06-01 | Blegen et al. | Applicant |
| US6784900(B1) | 2004-08-01 | Dobronsky | Applicant |
| US6789201(B2) | 2004-09-01 | Barton et al. | Applicant |
| US6819343(B1) | 2004-11-01 | Sobeski et al. | Applicant |
| US6851060(B1) | 2005-02-01 | Shrader | Applicant |
| US6865680(B1) | 2005-03-01 | Wu et al. | Applicant |
| US6868394(B1) | 2005-03-01 | Mele | Applicant |
| US6873974(B1) | 2005-03-01 | Schutzer | Applicant |
| US6904408(B1) | 2005-06-01 | McCarthy et al. | Examiner |
| US6948125(B2) | 2005-09-01 | Detweiler et al. | Applicant |
| US6976077(B1) | 2005-12-01 | Lehew et al. | Applicant |
| US6981215(B1) | 2005-12-01 | Lindhorst et al. | Applicant |
| US7343351(B1) | 2008-03-01 | Bishop et al. | Examiner |
| US2001/0001147(A1) | 2001-05-01 | Hutchison et al. | Applicant |
| US2001/0035885(A1) | 2001-11-01 | Iron et al. | Applicant |
| US2002/0016769(A1) | 2002-02-01 | Barbara et al. | Applicant |
| US2002/0018078(A1) | 2002-02-01 | Khan et al. | Applicant |
| US2002/0057299(A1) | 2002-05-01 | Oren et al. | Applicant |
| US2002/0062342(A1) | 2002-05-01 | Sidles | Examiner |
| US2002/0070963(A1) | 2002-06-01 | Odero et al. | Applicant |
| US2002/0070969(A1) | 2002-06-01 | Barksdale et al. | Applicant |
| US2002/0075326(A1) | 2002-06-01 | Allen | Applicant |
| US2002/0077978(A1) | 2002-06-01 | O'Leary et al. | Examiner |
| US2002/0078095(A1) | 2002-06-01 | Culham | Applicant |
| US2002/0089549(A1) | 2002-07-01 | Munro et al. | Applicant |
| US2002/0097277(A1) | 2002-07-01 | Pitroda | Applicant |
| US2002/0111814(A1) | 2002-08-01 | Barnett et al. | Applicant |
| US2002/0149615(A1) | 2002-10-01 | Rajarajan et al. | Applicant |
| US2002/0149618(A1) | 2002-10-01 | Estrada et al. | Applicant |
| US2002/0154159(A1) | 2002-10-01 | Day et al. | Applicant |
| US2002/0158912(A1) | 2002-10-01 | O'Rourke | Applicant |
| US2002/0163544(A1) | 2002-11-01 | Baker et al. | Applicant |
| US2002/0163545(A1) | 2002-11-01 | Hii | Applicant |
| US2002/0186239(A1) | 2002-12-01 | Komuro | Applicant |
| US2002/0186249(A1) | 2002-12-01 | Lu et al. | Applicant |
| US2002/0186255(A1) | 2002-12-01 | Shafron et al. | Applicant |
| US2002/0186256(A1) | 2002-12-01 | Hong | Applicant |
| US2003/0009768(A1) | 2003-01-01 | Moir | Applicant |
| US2003/0011641(A1) | 2003-01-01 | Totman et al. | Applicant |
| US2003/0028764(A1) | 2003-02-01 | Campbell | Applicant |
| US2003/0041240(A1) | 2003-02-01 | Roskind et al. | Applicant |
| US2003/0046589(A1) | 2003-03-01 | Gregg | Applicant |
| US2003/0067481(A1) | 2003-04-01 | Chedgey et al. | Applicant |
| US2003/0080995(A1) | 2003-05-01 | Tenenbaum et al. | Applicant |
| US2003/0085916(A1) | 2003-05-01 | Thiry et al. | Applicant |
| US2003/0085927(A1) | 2003-05-01 | Muller | Applicant |
| US2003/0112271(A1) | 2003-06-01 | Batalden et al. | Applicant |
| US2003/0112280(A1) | 2003-06-01 | Driskell | Applicant |
| US2003/0128233(A1) | 2003-07-01 | Kasriel | Applicant |
| US2003/0131106(A1) | 2003-07-01 | Kasriel | Applicant |
| US2003/0140312(A1) | 2003-07-01 | Mohan et al. | Applicant |
| US2003/0202009(A1) | 2003-10-01 | Kasriel | Applicant |
| US2003/0233425(A1) | 2003-12-01 | Lyons et al. | Examiner |
| US2004/0061720(A1) | 2004-04-01 | Weber | Applicant |
| US2004/0125130(A1) | 2004-07-01 | Flamini et al. | Applicant |
| US2004/0174396(A1) | 2004-09-01 | Jobs et al. | Applicant |
| US2004/0186775(A1) | 2004-09-01 | Margiloff et al. | Applicant |
| US2004/0243520(A1) | 2004-12-01 | Bishop et al. | Applicant |
| US2005/0039141(A1) | 2005-02-01 | Burke et al. | Applicant |
| US2005/0039144(A1) | 2005-02-01 | Wada et al. | Applicant |
| US2005/0198220(A1) | 2005-09-01 | Wada et al. | Applicant |
| US2006/0106681(A1) | 2006-05-01 | Shafron et al. | Applicant |
| US2006/0107217(A1) | 2006-05-01 | Lu et al. | Applicant |
| US2006/0122904(A1) | 2006-06-01 | Shafron et al. | Applicant |
| JP2000259566 | 2000-09-01 | Applicant | |
| WO/25239 | 2000-05-01 | Applicant | |
| WO/31657(A2) | 2000-06-01 | Applicant | |
| WO116900 | 2001-03-01 | Applicant | |
| WO1/39046(A1) | 2001-05-01 | Applicant | |
| WO1/52023(A) | 2001-07-01 | Applicant | |
| WO1/67285(A2) | 2001-09-01 | Applicant | |
| WO1/95104 | 2001-12-01 | Applicant | |
| WO3/038554 | 2003-05-01 | Applicant | |
| WO3/038640 | 2003-05-01 | Applicant | |
| WO2005/017670(A2) | 2005-02-01 | Applicant | |
| WO2005/019983(A2) | 2005-03-01 | Applicant | |
| WO2005/043355(A2) | 2005-05-01 | Applicant |
Non-Patent Literature (81)
- “Band Objects”, Microsoft Corporation, Copyright 1997.Examiner
- Supplementary European Search Report (EP 02 77 6336).Applicant
- Alexa Internet Website. Archived Feb. 9, 1998 at http://web.archive.org.Applicant
- Eric Ladd and Jim O'Donnell, Using Microsoft Internet Explorer 4 Que Corporation. 1997 pp. 42-43.Applicant
- Trupin, “The Visual Programmer puts Active X Document Objects Through Their Paces”, Microsoft Systems Journal, Jun. 1996, v11, n6, p. 55(16).Applicant
- “Client/Server and Host Application Development Tools”, DBMS, Jun. 15, 1996, v9, n6 p. 27(10).Applicant
- Childers, “Delphi Client/Server Suite”, Sep. 10, 1996, PC Magazine, vol. 15, N1, p. 207 (3).Applicant
- Persky, “HTML goes WYS/WYG: Two Mac-based Editors”, Mar. 1997, LAN Magazine, v12, n3, p. 121(5).Applicant
- Evans, “Extend Client/Server Apps to the Web”, Mar. 1997, Databased Advisor, v15, n3, p. 52 (5).Applicant
- Finn, “Add Control to your Intranet”, Aug. 1997, Databased Web Advisor, v15, n8, p. 56(3).Applicant
- Wong, “Meeting on the Internet in 10 Minutes”, Nov. 1997, Network, v12, n12, p. 131(4).Applicant
- Faison, “The New HTML Help System Extends Online Help From the Desktop to the Web”, Jan. 1998, Microsoft Systems Journal, v13, n1, p. 55 (14).Applicant
- Alwang “Meeting of the Minds”, Feb. 24, 1998, PC Magazine, v17, n4, p. 179(10).Applicant
- Walter, “Acrobat 4: Adobe's Bid to Make it More that Just a Viewer”, Mar. 1999, Seybold Report on Internet Publishing, 3, 7, NA(1).Applicant
- Alex Lash, “Alexa Accessorizes Browsers”, Sep. 22, 1997, CNET News.com. 2 pages.Applicant
- “As Go Surfers, So Goes Alexa”. Jul. 24, 1997, Wired News, 2 pages.Applicant
- Bart Eisenberg, “Alexa Archives the Internet”, Copyright 1997, 5 pages.Applicant
- Jesse Berst, “A Must-See Browser Add-On”.Sep. 16, 1998, ZDNet AncorDesk, 3 pages.Applicant
- International Search Report for International Application No. PCT/US99/25332, Feb. 2, 2000.Applicant
- International Search Report for International Application No. PCT/US02/34509, Oct. 28, 2003.Applicant
- International Search Report for International Application No. PCT/US02/34510, Jan. 31, 2003.Applicant
- Written Opinion for International Application No. PCT/US02/34510, Sep. 26, 2003.Applicant
- International Search Report for International Application No. PCT/US01/16993, Oct. 25, 2001.Applicant
- International Preliminary Examination Report for International Application No. PCT/US01/16993, Mar. 5, 2003.Applicant
- International Preliminary Examination Report for International Application No. PCT/US99/25332, Jul. 29, 2002.Applicant
- Mace, Thomas, “PowerBrowser”, Mar. 12, 1996, PC Magazine, vol. 15, No. 5, p. 132(1).Applicant
- Mendelson, Edward, “Wake Up Your Web Site”, Jun. 9, 1998, PC Magazine, vol. 17, No. 11 p. 60(2).Applicant
- “Band Objects”, Microsoft Corporation, Copyright 1997, pp. 1-6.Applicant
- “Browser Extensions”, MSDN, Copyright 2004, pp. 1-2.Applicant
- Creating Custom Explorer Bars, Tool Bands, and Desk Bands, MSDN, Copyright 2004, pp. 1-11.Applicant
- “Developers Get Early IE 5”, Jun. 11, 1998, Wired News, pp. 1-2.Applicant
- “Introduction”,XUL Programmer's Reference Manual, Last Updated: Apr. 5, 2001, pp. 1-3.Applicant
- “Netscape 6 Preview Release 1”, NT Compatible, Apr. 5, 2000, pp. 1-3.Applicant
- “Plug-in-Guide”, DevEdge Oline Documentation, Chapter 1, pp. 1-4 and 1-15.Applicant
- “Subject: Add toolbar to IE4-taskbar”, Google Groups, Jan. 26, 1999, p. 1.Applicant
- “Subject: Adding Toolbar (Plugin) in Netscape Communicator”, Google Groups, May 18, 2000, pp. 1-4.Applicant
- “Subject: Custom Toolbar for Netscape Browser”, Google Groups, May 15, 2001, p. 1.Applicant
- “Subject: How the Hell????”, Google Groups, Jun. 6, 2000, pp. 1-3.Applicant
- “Subject: How to add toolbar like Yahoo companion in IE”, Google Groups, Sep. 30, 1999, Messages 1-10.Applicant
- “Subject: How to add toolbar like Yahoo companion in IE”, Google Groups, Sep. 30, 1999, Messages 11-14.Applicant
- “Subject: IE4 Band Objects”, Google Groups, Mar. 22, 1998, pp. 1-3.Applicant
- “Subject: Plugins for IE”, Google Groups, Sep. 30, 2000, p. 1.Applicant
- “Subject: Toolbar like IE4”, Google Groups, Apr. 23, 1998, pp. 1-2.Applicant
- “Subject: What's the deal with Yahoo Companion? Standard plugin API or not?”, Google Groups, Jan. 12, 2000, pp. 1-6.Applicant
- Flanagan David, “Netscape 6.0 Released”, O'Reilly, Nov. 16, 2000, pp. 1-3.Applicant
- Galli Marcio, “The DevEdge RSS-News Ticker Toolbar”, Netscape DevEdge, Jul. 14, 2003, pp. 1-3.Applicant
- Jimmy, “Netscape 6.0 Preview Release 2 Review—Good Software, Bad Timing”, Jimmy's World, Aug. 9, 2000, 3 pages.Applicant
- Mann Alex and Hecht Kevin, “DevEdge Newsgroup FAQ: Client Technical”, DevEdge Online Archive, Last Updated: Dec. 15, 1998, pp. 1-12.Applicant
- Roberts Scott, “Programming Microsoft Internet Explorer 5”, Jul. 1999, pp. 3-16,383-423, 461-475, Microsoft Press, USA.Applicant
- Summers Jason, “Plug-ins Newsgroup FAQ: Plug-ins”, DevEdge Online Archive, Last Updated: May 26, 1999, pp. 1-16.Applicant
- Alexa, Alexa Toolbar Version 1.4.1, Copyright 1998[Note: Setup File Available on Enclosed CD Entitled “Alexa Setup”.Applicant
- International Preliminary Examination Report for International Application No. PCT/US02/34509, May 11, 2004.Applicant
- International Preliminary Examination Report for International Application No. PCT/US02/34510, Aug. 12, 2004.Applicant
- International Search Report for International Application No. PCT/US04/24397, Oct. 31, 2005.Applicant
- Written Opinion for International Application No. PCT/US04/24397, Oct. 31, 2005.Applicant
- International Preliminary Report on Patentability for International Application No. PCT/US2004/24397, Feb. 13, 2006.Applicant
- Hauser, “Generic Extensions of WWW Browsers”, First USENIX Workshop on Electronic Commerce, p. 147-154, Aug. 10, 1995.Applicant
- R.L. Rivest, H.H. Cormen, C.E. Leiserson, “Introduction to Algorithms”, MIT Press, McGraw-Hill, Cambridge Massachusetts, 1997. 6 pages.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,469 dated Mar. 10, 2009.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,469 dated Sep. 16, 2008.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,469 dated Apr. 10, 2008.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,469 dated Nov. 15, 2007.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,533 dated Mar. 31, 2009.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,533 dated Jan. 6, 2009.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,533 dated Aug. 6, 2008.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/015,816 dated Nov. 8, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/015,816 dated Jun. 22, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/015,816 dated Aug. 10, 2005.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/177,501 dated Aug. 27, 2007.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/177,501 dated May 7, 2007.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/177,501 dated Dec. 27, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/177,501 dated Jul. 5, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/177,501 dated Jan. 12, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 10/015,816 dated Jan. 19, 2006.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/322,469 dated Aug. 14, 2009.Applicant
- Official Action from the United States Patent and Trademark Office for U.S. Appl. No. 11/323,094 dated Aug. 18, 2009.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/322,533, dated Oct. 28, 2009.Applicant
- Final Office Action for U.S. Appl. No. 11/322,533, dated Apr. 8, 2010.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/322,533, dated Jul. 12, 2010.Applicant
- Final Office Action for U.S. Appl. No. 11/322,533, dated Dec. 23, 2010.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/322,533, dated Aug. 30, 2012.Applicant