WO2001022245A1

WO2001022245A1 - Dynamic navigation tool bar incorporating real-language context addressing

Info

Publication number: WO2001022245A1
Application number: PCT/US2000/025817
Authority: WO
Inventors: Michael Bannen
Original assignee: Clickguide, Inc.
Priority date: 1999-09-20
Filing date: 2000-09-20
Publication date: 2001-03-29
Also published as: GB2371655A; GB0208538D0; GB2371655B; AU7596400A

Abstract

A customizable graphical user interface (100) is provided for accomplishing navigation of global computer networks with a minimum of typing and clicking by a user. A customizable tool bar (102) has an embedded hierarchy (114, 116, 122, 130) wherein the hierarchy corresponds to Internet addresses (144, 146, 148, 150, 152, 154) of selected favored web content providers without reference to specific URL or domain name addresses (144, 146, 148, 150, 152, 154) corresponding thereto. The tool bar (102) can also include a hierarchy corresponding to URL and domain name addresses (144, 146, 148, 150, 152, 154) wherein real language context addresses (104, 106, 108, 110, 112, 118, 120, 124, 126, 128, 132, 134, 136, 138, 140, 142) have been substituted for the URL/domain name (144, 146, 148, 150, 152, 154) so that a user can navigate purely by instinctive context rather than being required to know specific URL or domain names. The tool bar real language aliases (104, 106, 108, 110, 112, 118, 120, 124, 126, 128, 132, 134, 136, 138, 140, 142) are dynamically updated, in conjunction with the underlying URL or domain name (144, 146, 148, 150, 152, 154), as required to reflect changes due to thirdparty web site reorganization, relocation, or removal to prevent the expiration or obsoleting of the embedded URLs (144, 146, 148, 150, 152, 154).

Description

DYNAMIC NAVIGATION TOOL BAR INCORPORATING REAL- LANGUAGE CONTEXT ADDRESSING

This application claims the benefit of U.S. Provisional Application No. 60/154,761, filed September 20, 1999.

BACKGROUND OF THE INVENTION

Field of the Invention

This invention relates to a system for navigating a computer network and includes a local computer, remote computers and a communications link to provide quick and efficient access to pre-selected service providers carrying different types of predetermined content. This invention also relates to a software program for working with a desktop application to serve as a ready navigational tool for user defined, or provider defined, indexed subject matter using real-language substitutes for complicated computer, TCP/IP or domain name addresses. Related Art

The Internet (a subset of which is known as The World Wide Web or WWW) is an interconnected computer network that is generally distributed throughout the world on discrete interconnected computer nodes having software interfaces relying on the Hypertext Transfer Protocol ("HTTP") that is used to generate so-called "web pages." Access to the Internet can be had by various methods, but today the average non-institutional user obtains access time from one of a myriad of Internet Service Providers (ISPs), which themselves have authorized access to the Internet.

The Internet originally presented information in a technical, textual, non- intuitive, and arguably user-hostile manner. It required knowledge of specialized computer language, having idiosyncratic designations and syntax. The Internet now provides the flexibility of allowing material to be presented in a textual or graphic format. Navigation around the WWW still requires some knowledge of the directory structure of the various nodes of the Internet, and specialized knowledge of the syntax required to access that directory structure. The directory structure provides an "address" to each given resource on the Internet. The address is known as the Universal Resource Locator (URL) and includes a domain name (e.g., clickguide.com). A URL typically takes the form of a cryptic text string, a very simple example of which is http://www.clickguide.com.

Some of that requirement for special knowledge has been obviated by the advent of the HyperText Markup Language (HTML), a software system that allows the embedding of codes within a web page which may be activated by the user, and allowing direct access to the page identified by the underlying computer syntax, while presenting a contextual reference in plain language to the user. This system works fine once a user has located the page upon which the link is located. However, the problem still existed in providing a means to locate information when all the user knew was the type of information that was desired. This led to the advent of what have become commonly known as search engines, or indexing tools that continually collect information from the various locations on the Internet and index the information in a manner which can be textually searched by a user.

A common problem with search engines is that they are limited in the contextual manner in which they relate search terms, and they can also carry expired information, for there is limited mechanism to remove expired information from the databases. Also, some "competing" search engines use the same database, and only provide a different look to, or maybe a slightly different handling of the information. Access to the Internet has been made easier through the advent of what has become known as the Internet browser. The original Internet browser product was known as Mosaic, and was developed at the University of Illinois at Champaign- Urbana. That browser evolved into the current market leaders: Netscape's Navigator® and Microsoft Internet Explorer®.

While Internet browsers provide an interface to the Internet, they, in themselves, do not provide a means of locating content providers on the Internet. The Internet browsers typically include a user-configurable, tagged list of addresses, often referred to as "Favorites" for the Internet Explorer Internet browser or "Bookmarks" for the Netscape Navigator, wherein users can save a URL to the tagged list of addresses, enabling the user to quickly access the page designated by that URL, if it is still valid, at a later time while using that Internet browser. FIG. 1 shows an example prior art method for navigating the Internet. A user starts the method, at the initiation point shown as 10 by launching the Internet browser (12) which displays the "home page" for the particular Internet browser (14) which, if the Internet browser has just been launched will show the "home page" assigned by the user of the Internet browser or default to a previously predetermined page. At this point, the user must select a method to navigate the Internet (16). Exemplary methods are listed in FIG. 1 and include manually entering a URL into the Internet browser (18), selecting a previously-saved URL from a tagged list (20), clicking on a hyper link which automatically transports the Internet browser to display the web page embedded in the hyper link (22), using a search engine to display a list of queried web pages and click on a hyper link embedded in the results list from the search engine (24), clicking on the "back" or "forward" buttons to display previous or later displayed web pages (26), or selecting from a "history" of previously-accessed web pages typically saved on a computer's hard drive (28). Once the method of navigation has been selected, the Internet browser views the next web page (30). FIG. 1 also shows a link 32 shown as "A" which leads to the continuation of the process in FIG. 2.

FIG. 2 shows a method by which a user can save a particular URL in a tagged list in the Internet browser (Favorites or Bookmarks) for access in later browsing such as in the method step shown as (20) of FIG. 1. FIG. 2 shows a decision point (34) which, if a user decides to tag or save the URL of the current web page for later access, the user typically displays the web page in the Internet browser window (36) and selects a graphical user interface item such as a menu, tool bar, or other interface to send a command to the Internet browser that the user desires to save the URL in the tagged list (38). The user is then typically prompted to create a real-language nickname for association with the URL to be saved in the tagged list (40).

Alternatively, the user can accept an embedded real-language nickname for the web page sometimes provided by web site content providers within hyper text links or web site page properties. Once the web site address and nickname have been indicated by the user, the user also typically has an opportunity to organize the tagged list into a hierarchy or directory structure wherein particular web site addresses are manually subdivided into user-named folders, subfolders for organization by the user (42). Once the new entry into the tagged list has been saved, the user can return to browsing web site content (44). FIG. 2 shows an exit point of this process (46) which returns the user to browsing and selecting a new navigation menu as shown in FIG. 1.

It should be noted in FIG. 2 that if the user does not desire to tag the current page for later access (34), the user moves directly to (44) to return to FIG. 1 (46).

For a user to index multiple pages, the process of FIG. 2 must be repeated for each web page which the user desires to add to the tagged list (Favorites or Bookmarks).

FIG. 3 shows an example of a personal computer screen display of an Internet browser 50, comprising a content window 52, a menu bar 54, a button tool bar 56 and a URL address entry window 58. In general, a user can operate the Internet browser 50 by entering an address into the URL address entry window 58, wherein the Internet browser 10 displays the content of the page indicated within the URL entry window 58. Further, as shown in FIG. 4, a tagged address list 60, i.e., Favorites or Bookmarks, can be displayed wherein the user has previously saved each of the URL addresses listed therein in which correspond to desired web sites for later visitation. The tagged list 60 may be a single list of randomly distributed URLs, or the user may customize the menu by organizing the menu items alphabetically, or dividing them into categorized "folders" 62, as shown in FIG. 5. The user may accept a default display name selected by the browser, or create their own.

The primary shortcoming of the tagged address systems that the current Internet browsers utilize lies in the dynamic nature of the Internet. Users desire a consistency in results when they execute commands on their browser, as in any other program or system. When the user is accessing information on their own computer, or on a dedicated location within their own network, the process for locating that information is usually well defined and stable. Internet pages, however, are subject to a higher frequency of change, due to reorganization of pages by the owner, expiration of pages, and dynamic updating of information by content providers. Such factors affect the ability of the user to locate information because the pointer that the user has manually created, in the form of a tagged address list, is static. There is no mechanism in place to update the list dynamically, as the destinations referred to in the list are dynamic.

Another of the shortcomings of the browser provided lists is the default manner in which listings are added to the list. By default, new listings are randomly assigned to the overall list, in the order in which assigned or by alphabetical order according to the nickname for the URL assigned by the user, and given a listing name as assigned by the owner of the destination page. This may have no relation to the purpose for which the user has tagged that particular page. Also, if the owner of the page has not named the page, the user, by default, will see the URL of the page as the line item entry in his address list. This is not useful to the user in providing an intuitive listing, which requires no subsequent translation by the user. It requires the user to remember just what that cryptic listing is referencing, it requires the user to look at the page to remind himself what the page contains, or it requires the user to search for the material anew when he can't find the reference on his tagged address list.

Another shortcoming of the tagged address lists of the current browser programs is their uniqueness to that browser. They require development independent of any file structure that may be in place in the user's information environment.

The various interfaces on the typical Internet browsers best serve the most knowledgeable user. The expert frequent user will have spent much time and energy customizing their browser, or in fact doesn't use the graphical browser at all. For the novice or first time user, however, there is always a learning curve, which in many cases is never overcome.

SUMMARY OF THE INVENTION

Therefore, the current invention provides a navigation interface for the Internet, or other digital information environment, that provides the user with direction to context-specific, and context-indexed, information, and dynamically updates links to the information sources, eliminating the problems of expired or moved links. Furthermore, this interface provides the user with flexibility to customize the interface to match the user's own specific preferences. Furthermore, the interface has the flexibility to adapt as a navigation tool to operate in additional environments such as the corporate network, or the user's own computer.

The invention overcomes the limitations of prior art Internet browsers by providing a customizable graphical user interface for accomplishing Internet navigation with a minimum of typing and clicking by a user. In a preferred embodiment, the invention comprises a customizable tool bar having an embedded hierarchy wherein the hierarchy corresponds to Internet addresses of selected favored Internet providers without reference to specific URL or domain name addresses corresponding thereto. Further, in a preferred embodiment, the tool bar includes a hierarchy corresponding to URL and domain name addresses wherein real-language context addresses have been substituted for the URL/domain name so that a user can navigate purely by instinctive context rather than being required to know specific URL or domain names. Further, in an additional preferred embodiment, the tool bar real-language aliases are dynamically updated, in conjunction with the underlying URL or domain name, as required to reflect changes due to third-party web site reorganization, relocation, or removal.

In one aspect, the invention relates to an interface for a client located on a distributed network of clients and servers for selecting desired content on other clients and servers on the network by accessing a database on a remote computer, the database having a list of target navigation addresses of the desired content and an index corresponding thereto.

In one embodiment, the interface comprises at least one user selectable actuator identified by a context-based identifier corresponding to the index of the list on the remote computer, and a first operable link to a browser on the client and a second operable link to the remote computer database, wherein the second operable link returns a target navigation address from the server database when the user selects the at least one actuator and the client browser is redirected to the returned target navigation address via the first operable link. A user thereby need not maintain an updated list of target navigation addresses on the client, but rather need only navigate via the context-based identifier on the at least one actuator of the interface and any changes to the target navigation address can be maintained on the server. The at least one actuator can comprise a series of actuators each with a unique context-based identifier. The series of actuators can be organized into a hierarchy based upon relationships between the context-based identifiers in the series of actuators.The hierarchy can be a menu system. The context-based identifier for the at least one actuator can be preselectable based upon a particular distribution origin for the interface or perhaps a particular affiliate relationship with the remote computer. The remote computer can transmit the content of the context-based identifier for the at least one actuator via the second operable link. The initial configuration of the interface can be received from the remote computer via the second operable link. A client database can be located on the client that receives at least one of context-based identifiers and target navigation addresses from the server database. The client database can be periodically updated with at least one of refreshed context- based identifier information and target navigation address information via the second operable link. The context-based identifiers for the interface can be stored in a form independent of a particular type of client browser or other viewing application. The client software can identify the viewing application and load a menu adapted for that application. The target navigation addresses can be customized to the viewing application to direct the application to destinations adapted to work with that application.

In another aspect of the invention, text selected by a user prior to actuating the at least one actuator can be tagged to a subsequent redirection to a target navigation address to provide the selected text as input for a targeted address.

In another aspect of the invention, the invention relates to a system for managing context-based navigation on a distributed network of servers and clients. The system can comprise a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an index identifying the target navigation address. At least one client located on the distributed network having a client database having at least one row element, the at least one row element containing a context-based identifier, wherein each of the at least one row element context-based identifiers corresponds to the index. An interface located on the client having at least one actuator corresponding to the at least one row element context-based identifier, wherein selection of the at least one actuator returns a target navigation address from the server database corresponding to the selected context-based identifier. A user of the client thereby need not maintain the client database because any changes in the target navigation address can be made in the server database because the client refers only to the index.

A redirector can be provided for directing the client to the returned target navigation address. A maintenance routine can be provided for confirming whether the target navigation address is active. A cached list can be provided on the client containing recently-selected context-based identifiers and the returned target navigation addresses. A comparator can be provided for looking up the context-based identifier in the cached list corresponding to the context-based identifier of subsequently selected actuators and redirecting the navigation of the client to the target navigation address if a match is found in the cached list. A validator can be provided for looking up the context-based identifier of subsequently selected actuators in the server database to confirm that the target navigation address located in the cached list is the same as the target navigation address in the server database corresponding to the context-based identifier. The target navigation address can be a URL or perhaps a domain name. A navigation log can be provided on the server containing at least a client identifier and a selected target navigation address. The client identifier and each selected target navigation address can be appended to the navigation log, whereby profile information can thereby be compiled and reported by at least the client identifier and the target navigation address. The client database can further include a second index corresponding to the context-based identifier, wherein the second index relates to the first index of the server database.

In an additional aspect of the invention, the invention relates to a method for managing context-based navigation on a distributed network of servers and clients comprising the steps of: maintaining a server database on a server located on the distributed network having at least one row element, the at least one row element containing a target navigation address and an index identifying the target navigation address; distributing a client database to at least one client located on the distributed network, the client database having at least one row element, the at least one row element containing a context-based identifier, wherein each of the at least one row element context-based identifiers corresponds to the index; and installing an interface on the client having at least one actuator corresponding to the at least one row element context-based identifier, wherein selection of the at least one actuator returns a target navigation address from the server database corresponding to the selected context- based identifier; whereby a user of the client need not maintain the client database because any changes in the target navigation address can be made in the server database because the client refers only to the index.

The method can also include the steps of: redirecting the client to the returned target navigation address; wherein the maintenance step comprises confirming whether the target navigation address is active; maintaining a cached list on the client containing recently-selected context-based identifiers and the returned target navigation addresses; comparing the context-based identifier in the cached list corresponding to the context-based identifier of subsequently selected actuators and redirecting the navigation of the client to the target navigation address if a match is found in the cached list; validating the context-based identifier of subsequently selected actuators in the server database to confirm that the target navigation address located in the cached list is the same as the target navigation address in the server database corresponding to the context-based identifier; maintaining a navigation log on the server containing at least a client identifier and a selected target navigation address; and appending at least the client identifier and each selected target navigation address to the navigation log, whereby profile information can thereby be compiled and reported by at least the client identifier and the target navigation address. In another aspect, the invention relates to a system for navigation on a distributed network of servers and clients while determining and tabulating the number of clients delivered to particular addresses on the network. In one embodiment of the system, the system comprises a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an affiliate index corresponding to the target navigation address. An affiliate database is located on the distributed network identifying affiliates of the server corresponding to the affiliate index, corresponding target navigation addresses of each affiliate and an affiliate counter for identifying the number of delivered clients from the server to each affiliate. At least one client located on the distributed network and an interface is located on the client having at least one actuator for sending a target navigation address identifier to the server, wherein selection of the at least one actuator directs the client to the server with an indicator corresponding to the target navigation address identifier. A redirector is located on the server, wherein the redirector redirects the client to the selected target navigation address and increments the corresponding affiliate counter if the target navigation address corresponds to an affiliate index. The number of clients delivered to an affiliate can thereby be easily determined by querying the affiliate database and business relationships based upon the volume of clients delivered to an affiliate can be easily formed and maintained.

In other embodiments of the system, the target navigation address identifier on the interface can comprise a context-based identifier and the server database further comprises a corresponding context-based index for each target navigation address. At least one default target navigation address identifier can correspond to an affiliate in the affiliate database. The context-based identifier for the at least one default target navigation address can relate to the subject matter content of the corresponding affiliate. The affiliate corresponding to the at least one default target navigation address can be replaced by another affiliate through a competitive bid process. An affiliate can purchase positioning as a default target navigation address. An affiliate can pay an administrator of the server a fee for delivering clients to the affiliate target navigation address. The fee can be proportional to the number of clients delivered to the affiliate target navigation address. The affiliate database can be located on the server.

In another aspect of the invention, the invention relates to a method for determining and tabulating the number of clients delivered to particular addresses on a distributed network of servers and clients. In one embodiment, the invention comprises the steps of maintaining a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an affiliate index corresponding to the target navigation address; interconnecting the server to an affiliate database located on the distributed network identifying affiliates of the server corresponding to the affiliate index, corresponding target navigation addresses of each affiliate and an affiliate counter for identifying the number of delivered clients from the server to each affiliate; providing an interface to at least one client located on the distributed network, the interface having at least one actuator for sending a target navigation address identifier to the server; redirecting the client to the server upon selection of the at least one actuator with an indicator corresponding to the target navigation address identifier; incrementing the corresponding affiliate counter if the target navigation address corresponds to an affiliate index; and redirecting the client to the selected target navigation address; whereby the number of clients delivered to an affiliate can be easily determined by querying the affiliate database and business relationships based upon the volume of clients delivered to an affiliate can be easily formed and maintained.

In other embodiments, the method can also include the steps and features of: the target navigation address identifier on the interface can comprise a context-based identifier and the server database can further comprise a corresponding context-based index for each target navigation address; the interface can further comprise at least one default target navigation address identifier corresponding to an affiliate in the affiliate database; relating the context-based identifier for the at least one default target navigation address to the subject matter content of the corresponding affiliate; replacing the affiliate corresponding to the at least one default target navigation address with another affiliate through a competitive bid process; selling a position as a default target navigation address to an affiliate; receiving payment from an affiliate for delivering clients to the affiliate target navigation address; the fee can be proportional to the number of clients delivered to the affiliate target navigation address; the affiliate database can be located on the server. In yet an additional aspect of the invention, the invention relates to a system for distributor-specific implementation of a navigation interface on a distributed network of servers and clients. In one embodiment, the invention comprises a server on the distributed network having an uncompiled interface code and a compiler for compiling the interface code into a distributable object upon receipt of a distributor identification code, wherein each distributor identification code is associated with a unique configuration of the interface by the server. At least one distributor is provided having a unique distributor identification code having at least one of a distributable object compiled according to its unique distributor identifcation code, an installation module capable of invoking the compiler with its unique distributor identification code. At least one client on the distributed network that receives the unique configuration of the interface via the at least one distributor. The configuration of the distributable object can thereby be controlled based upon the distribution point and distributor based upon the unique distribution code. The installation module can comprise a link to the compiler with its unique distributor code embedded therein. The installation module can comprise a client- installed application that invokes the compiler with its unique distributor code. The installation module can comprise a client-installed application having a compiler for creating the distributable object with its unique distributor code. The server can have a default distributor code for producing a default configuration of the distributable object. The default distributor code can be used by the compiler when no unique distributor identification code is received.

In another aspect, the invention relates to a method for distributing customized implementations of a navigation interface on a distributed network of servers and clients. In one embodiment, the invention comprises the steps of: maintaining a server on the distributed network having an uncompiled interface code and a compiler for compiling the interface code into a distributable object upon receipt of a distributor identification code, wherein each distributor identification code is associated with a unique configuration of the interface by the server; assigning a unique distributor identification code to at least one distributor, the at least one distributor having at least one of a distributable object compiled according to its unique distributor identifcation code, an installation module capable of invoking the compiler with its unique distributor identification code; and distributing the unique configuration of the interface via the at least one distributor to at least one client on the distributed network; whereby the configuration of the distributable object can be controlled based upon the distribution point and distributor based upon the unique distribution code.

In other embodiments, the method can also include the features and steps of: wherein the installation module comprises a link to the compiler with its unique distributor code embedded therein; invoking the compiler with the unique distributor code via the client; invoking the compiler with the unique distributor code via the distributor and sending the distributable object to the client; wherein the installation module comprises a client-installed application having a compiler for creating the distributable object with its unique distributor code; assigning a default distributor code and producing a default configuration of the distributable object based upon the default distributor code when a unique distributor code is not received by the compiler.

Other objects, features, and advantages of the invention will be apparent from the ensuing description in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart describing a prior art method of Internet navigation with prior art known web browsing software employing a plurality of options to move from one web page to another web page;

FIG. 2 is a continuation of the flowchart of FIG. 1, showing method steps necessary for saving a desired URL address into a tagged list in web browsing software such as the Favorites menu in the Internet Explorer software or the Bookmarks menu in the Netscape Navigator software;

FIG. 3 illustrates a typical Internet web browser as displayed on a conventional computer monitor (not shown); FIG. 4 shows the Internet browser of FIG. 3 with a tagged list menu expanded to show several sublevels of tagged URL addresses; FIG. 5 shows the tagged list of FIG. 4 located in a frame adjacent to a web content window;

FIG. 6 is a schematic diagram of an Internet navigation system and process according to the invention; FIG. 6 A is an enlarged portion of FIG. 6 showing the prior art Internet navigation process;

FIG. 6B is an enlarged portion of FIG. 6 showing a distribution and installation process for the Internet navigation system according to the invention;

FIG. 6C is an enlarged portion of FIG. 6 showing a flow of information between a client and a server in an Internet navigation system according to the invention;

FIG. 6D is an enlarged portion of FIG. 6 showing operation of the Internet navigation system according to the invention between a client, server and content provider; FIG. 7A is a schematic of a further embodiment of a distribution and installation process of an Internet navigation system according to the invention;

FIG. 7B is a further embodiment of a distribution and installation of the Internet navigation system according to the invention;

FIG. 7C is a schematic showing a further embodiment of communication between a client and server using the Internet navigation system according to the invention;

FIG. 7D is a schematic diagram showing a transfer of information between a client and a server in an Intemet navigation system according to the invention;

FIG. 8 shows the Internet browser of FIG. 3 wherein an online customization feature of a navigation toolbar according to the invention has been selected;

FIG. 9 illustrates a process by which the online customization feature of FIG. 8 can be performed enabling the user to select, build and execute the installation of a navigation tool according to the invention;

FIG. 10 illustrates the method step of selecting the content for the navigation tool of FIG. 9 in greater detail; FIG. 11 illustrates a web site page for selecting main level categories shown by example as auctions, sports, search, shopping, tickets and tools;

FIG. 12 illustrates a web site page configured for selection of content provided for a particular main level category (i.e., "shopping") enabling a user to select content providers such as, for example, submenu categories of books and stores;

FIG. 13 shows a web site page configured to enable a user to select a subset of available indexed pages in a web site tree stmcture to allow systematic selection of all or a portion of a particular content provider (as selected in FIG. 12) tree stmcture;

FIG. 14 illustrates a system menu provided on the navigation tool of FIGS. 8-9 according to the invention and showing a customization feature for the local computer on which the web browsing software is run;

FIG. 15 illustrates a dialogue box wherein the menu system of the navigation tool of FIGS. 8-14 can be rearranged by a drag-and-drop method to restructure the main level categories and submenu system relating thereto; FIG. 16 illustrates a navigation flowchart containing a process embodied in an

Internet navigation tool according to the invention;

FIG. 17 shows a web browsing software window including a toolbar embodiment of the navigation tool of FIG.16;

FIG. 18 is a schematic view of the navigation tool of FIGS. 16-17 showing several main level categories and an example sublevel menu system for a particular main level category where the main level category and its associated sublevel menu system are linked to another sublevel menu system or a database record having fields relating to a nickname for a particular URL address and a field containing the URL address, whereby selection of the nickname in the sublevel menu system triggers a command to the Internet browser to navigate to that particular URL address;

FIG. 19 shows a database incorporating the main level categories of FIG. 18 broken down into a database having subrecords corresponding to each main level category and showing an example pointer containing fields relating to a particular sublevel, a nickname for a URL address and a particular URL address; FIG. 20 illustrates the Internet browser containing the navigation tool of FIG.

16 according to the invention, wherein a particular main level category and its associated sublevels have been expanded to select an example real-language context nickname for a URL address;

FIG. 21 shows the Internet browser of FIG. 20 after the instructions to navigate to a particular URL address has been executed by the Internet browser; FIG. 22 illustrates an advanced method of operation of the navigation tool of

FIG. 16 wherein a user has selected text within the web content window (shown in the figure as selectedtext) and thereafter selection of a particular URL address within the main level category menu system sends selectedtext as a parameter to the new web page to immediately perform a desired command; FIG. 23 illustrates the Internet browser of FIG. 16 wherein a particular word has been selected in the web content window and a desired real-language context nickname search has been performed, i.e., the word "register" (selectedtext) has been selected while using the command "search dictionary" using the navigation tool of

FIG. 16; FIG. 24 illustrates the web browsing window of FIG. 20 after selectedtext has been passed to the desired dictionary web page, and wherein the results from the dictionary web page are shown;

FIG. 25 illustrates the Internet browser of FIG. 16 wherein a particular word has been selected in the web content window and a desired real-language context nickname search has been performed, i.e., the word "register" has been selected and the command "news content provider" has been selected while using the navigation tool of FIG. 16;

FIG. 26 illustrates the Internet browser of FIG. 16, wherein a particular word has been selected in the web content window and a desired real-language context nickname search has been performed, i.e., the word "register" has been selected and the command "search thesaurus" has been selected while using the navigation tool of

FIG. 16;

FIG. 27 illustrates the web browsing window of FIG. 26 after the selectedtext has been passed to the desired thesaurus web page wherein the results from the thesaurus have been shown; FIG. 28 illustrates the web browsing window of FIG. 26 after the selectedtext has been passed to the desired news content provider web page, and wherein the results from the news content provider have been shown;

FIG. 29 illustrates an embodiment of a client/server physical and relational configuration according to the invention; and

FIG. 30 illustrates an outline of the interconnections between the PK and FK indices for the fields of Table 1.

DETAILED DESCRIPTION In the Internet navigation system according to the invention, a service provider

("ClickGuide.com) will maintain a database of current navigation instructions for accessing locations (such as content providers) on a distributed network (such as the Intemet). Distributors direct users to the service provider, the users being identified as being referred by a given distributor. Users will be provided with an interface for directly accessing content providers without needing to know their specific domain name or other Internet address, and without running the risk of having a static Favorites or Bookmarks list located on their client computer becoming stale. Content providers (some of which are also distributors) are provided another avenue for directing users to their location. Referring now to FIG. 6, an Internet navigation system and process according to the invention includes a service provider 1000, here ClickGuide.com, a distributor 1010, at least one user 1020, and content providers 1030.

Referring to FIG. 6A, users 1020 access content providers 1030 using the prior art method of Internet navigation 5. Referring to FIG. 6B, the service provider 1000 provides a client interface access module 1102 to distributors 1010. Distributors 1010 can be, by way of example, computer equipment manufacturers 1012, Internet service providers 1014 and participating content providers 1016 having a link on their site to the service provider 1000. The module 1102 can take the form of an installation program for downloading the interface, a compiled executable program including the interface, or a link to the service provider 1000. The module 1102 is configurable to uniquely identify a distributor 1010, so that a user 1020 receives a uniquely identified module 1104 from the distributor 1010. The user obtains module 1104 by purchasing computer equipment with the module 1104 installed, by accessing the web site of a distributor, or receiving removable media containing the module 1104. The user 1020 receives a module 1104 from distributor 1010 and is directed to the service provider 1000 to commence or continue the installation process of the interface. In those cases where the user 1020 receives a module 1104 for installation on the client computer, upon running the software, the software will contact the service provider 1000 with a distribution ID uniquely identified to a distributor 1010. Service provider 1000 responds to the installation program or interface with, at a minimum, a software ID 1108. The service provider 1000 records an association between the distribution ED 1106 and the software ID 1108 for future use in data manipulation including compilation of distributor-related and user-related activity, and can use the association to tailor the information and menu structures of the interface to the distributor 1010 that introduced user 1020 to service provider 1000. In some embodiments, the service provider 1000 will send a menu stmcture for the interface with the software ID 1108.

Referring now to FIG. 6C, as the user 1020 begins using the interface, the interface will query 1110 the service provider 1000. In a preferred embodiment, the query 1110 is in the form of a context-based navigation instruction. The service provider 1000 addresses 1122 a database 1040 that associates the query 1110 with navigation syntax for accessing sites on the Internet. The service provider 1000 then responds 1112 to the user 1020 with the navigation syntax. In a further embodiment, the query 1110 can result in a response 1112 from the service provider 1000 of a menu stmcture containing context-based menu entries for graphical selection by the user 1020. The interface on the client computer can thereby build a menu stmcture of context-based menu entries. The menu entries will, as discussed below, form subsequent queries 1110 to the service provider 1000.

Referring now to FIG. 6D, whereas user 1020 previously accessed content providers 1030 directly through prior art navigation 5, user 1020 can now access the content providers 1030 through a context-based navigation interface that queries 1110 service provider 1000. The user is subsequently redirected 1114 to an appropriate content provider 1030. In a further embodiment, a query 1110 results in navigation syntax 1112 being returned to the user 1020 and stored on the client computer for future use in directing the user 1020 to the content provider 1030. The content provider 1030 that receives the benefit of the redirection 1114 is determined in several ways.

A primary method of determining which content provider 1030 receives redirection 1114 is the development of affiliates 1032. Affiliates 1032 pay the service provider 1000 for premium placement in database 1040 as the content provider 1030 associated with the context-based menu entries of the interface. Redirection 1114 is then primarily redirected 1118 to the affiliate 1032. Another aspect of this arrangement is that the majority of the users 1020 using the interface through service provider 1000 will be redirected 1114, 1118 to affiliate 1032. Other content providers 1030 that are selected for placement in the context-based menu stmcture of the interface, or, more particularly, are associated with the context-based menu entries in the database 1040, will often have a "click through" mechanism in place whereby referrers, in this case service provider 1000, receive a monetary benefit for referring or redirecting users to the content provider 1030. The "click through" benefit can be related to volume of referrals, volume of business of referred user, or other criteria established by the content provider. Database 1040 is then primarily developed with affiliates 1032 placed in a premium position for association with context-based menu entries of the interface; other content providers 1030 that are not affiliates 1032 may or may not receive preferred placement in the database 1040.

Another manner of selection of the content providers 1030 based on a menu stmcture is related to the distribution ID 1106 received by the service provider 1000 during initial installation of the interface. For instance, if the user 1020 was directed to service provider 1000 by a content provider 1016 having a link on its site to the service provider 1000, because the user 1020 (or, more particularly, the software ID 1108) is so identified with the distribution ID 1106, menu stmcture provided user 1020 will provide the content provider 1016 as the primary content provider for that context-based menu entry or entries. The menu stmcture accessed by the user 1020 is further customizable by the user 1020 through the interface and in cooperation with the service provider 1000, wherein the service provider 1000 provides the user 1020 with the option of selecting from content providers 1030 indexed in database 1040. A further customization method is anticipated with regard to content providers

1016 having a link to service provider 1000 on their site. For user 1020 already having the interface installed, the link further serves the purpose of initiating a customization of the interface (e.g. the menu entry associations) to include the content provider 1016. Referring now to FIG. 7 A, a further embodiment of the invention comprises a browser 2020 transferring 2106 a distributor ID to a web server 2000 (herein ClickGuide.com) and receiving 2108 a compiled executable file for execution on the client computer (not shown) running the browser 2020. It is anticipated that the compiled executable file will have the distributor ID embedded therein, or will have a software ID embedded therein. Anther embodiment is disclosed in FIG. 7B, wherein the browser 2020 has a ClickGuide (designated CG) overlay or tool bar transmitting 2106' a distributor ID to a web server 2000 and receiving 2108' in response a software ID for embedding therein. In either of the previous embodiments, the ClickGuide interface installed on the client computer can be installed with an embedded menu stmcture, or an embedded distributor ID, or an embedded software ID. In each instance, the web server 2000 will maintain a database associating the distributor ID with the software ID, and one or the other with any menu stmcture in use on the client computer. FIG. 7C depicts an embodiment wherein the browser 2020 and ClickGuide interface signal 2106" the web server 2000 that the menu tree in the ClickGuide interface is equal to null, or is empty. In response, the web server 2000 can transfer 2108" at least one menu stmcture, in a preferred embodiment an encrypted text file. The menu stmcture can be an empty table requiring filling as the user uses the interface to contact the web server, or can contain sufficient context-based menu entries for the user to initiate contact with the server 2000 to receive Internet navigation instmctions, or be redirected to, content providers on the Intemet (WWW). In a further embodiment shown in FIG. 7D, the browser 2020 and ClickGuide interface transfer a URL ID 2110 to web server 2000 and receive in response an associated URL for use by the browser to access a content provider on the Internet (WWW). In a preferred embodiment, the URL contains an optional query string identifying to the content provider the source of the referral of the user to the content provider. In another embodiment, the browser is redirected by the web server 2000 directly to the content provider upon receipt of the URL ID 2110.

Another way of describing the navigation tool, and its associated use in a network or digital environment, according to the invention, is that there are a number of avenues whereby a user will obtain the navigation tool for installation on his or her computer and affiliation with a browser software or other viewing application, a number of ways to configure the navigation tool, and a number of uses of the tool to benefit the user 1020, the content providers 1030, and the service provider 1000 (see FIGS. 6-7D). A first anticipated source of the navigation tool on a user's computer will be an original equipment computer manufacturer who installs the navigation tool as part of an original installation for the user. A second anticipated method of a user obtaining the navigation tool software is for the user to access the administrator's web site via a hyperlink located on an affiliate content provider's web site. The hyperlink would lead the user to a download area on the administrator's web site, where the user can download the navigation tool software to the user's computer. A third anticipated method of distribution of the navigation tool software is through distribution of removable media (such as a floppy disk or CD), distributed by the navigation tool administrator, an affiliate content provider, or a computer equipment manufacturer. In one embodiment, the method of distribution has anticipated distribution of the navigation tool software itself. Another embodiment of a method of distribution of the navigation tool software anticipates distribution of, or downloading by the user of, an installation program, a device commonly user by Internet software providers, whereby the user only downloads the installation software which is generally a smaller program than the target software, until such time as the user decides to install the software itself. Such a method of installing software requires that the user be connected to the Internet for downloading of the actual software product. In the alternative, the user could download the full software product for installation on the user's computer while not connected to the Internet.

In the first method, the user will mn the installation program while connected to the Internet, with the installation program querying the administrator's web site to initialize downloading of the actual navigation tool software to the user's computer. The installation software will include an embedded distributor identification, whereby the administrator can determine the source of the installation program, whether it was downloaded as a result of a hyperlink from a content provider's web site, was installed by a computer equipment manufacturer, came from a removable media distribution, or was downloaded directly from the administrator's web site directly with no known affiliation to a source outside of the administrator. During the installation of the navigation tool software onto the user's computer from the administrator's web site, a software identification is embedded into the navigation tool software to identify the particular software download. A database in the administrator's web site will affiliate the software identification with the distributor identification and will provide a customized configuration of menus and submenus based on the distribution identification. For example, if the distribution identification indicates that the user was referred to the administrator by an affiliated content provider, the navigation tool will be customized to direct the user to that content provider upon selection of a related submenu entry.

By identifying each installation on a user's computer by a unique software identification, the user can return to the administrator's web site to individualize his or her configuration of menus and the menu entries. The administrator can also dynamically update URLs commonly accessed from each installation of the software when the navigation tool software contacts the administrator's web site with its unique software identification.

In the cases where the navigation tool software has been installed directly on a user's machine while not connected to the Internet, such as when a computer equipment manufacturer has installed the software as part of an original installation, or a user has installed the software from a removable media while not connected to the Internet, there will come a time when the navigation tool software is activated for the first time while connected to the Internet, such as when a user runs software in conjunction with an Internet web browser and attempts to open any of the menus on the navigation tool bar. In one embodiment of the invention, the installed navigation tool software will be a shell, wherein the database 158 (see FIG. 19) is empty until the software first contacts the administrator's web site. In such a case, the communication of the navigation tool software with the administrator's web site will initiate a transfer of the distribution identification to the administrator's web site. In response, the administrator's web site will transfer the software identification to the user's computer as well as the database information for the navigation tool software corresponding to the distribution identification, as discussed supra, wherein the database information is customized based on the identification of the distribution. Where no distribution identification exists beyond the administrator's web site, the administrator will have a standardized configuration.

In a first embodiment of the invention, it is anticipated that the database 158 resident on the user's computer contain all of the actual URLs for the context- identified submenu entries of the navigation tool. However, as discussed in the "Background of the Invention," a common fault of web browsers with their favorites or bookmarks, is the dynamic nature of the Internet and the propensity of web addresses to change over time. The invention anticipates two avenues for dynamically updating URLs contained in the database associating a given submenu entry with a URL. That database associating the URL with the submenu entry can be resident on the user's computer or on the administrator's computer, or both. The first instance, where the database is resident on the user's computer, and only the user's computer, is the prior art implementation of the favorites or bookmarks of the popular Internet web browsers.

A second implementation maintains a copy of the entire database resident on both the user's computer and on the administrator's web site. When a user selects a submenu entry, the navigation tool software will access the database for the associated URL and directs the web browser to access that site. To obviate the problems with the prior art static database (favorites or bookmarks), the database on the user's computer must be periodically updated with any changed information regarding the links contained in the database. The navigation tool software must therefore contact the administrator's web side periodically to compare and replace database entries on the user's computer when necessary. This can be done in the background on a timed, periodic basis, can be initiated when the user connects to the Internet, can be initiated when the user activates the navigation tool, or any other database refreshment scheme as might be well known in the art.

A further embodiment of the invention anticipates the database on the user's computer associating each submenu entry with not a specific URL, but with a unique submenu entry identifier that itself is further associated with a unique URL. When a particular submenu entry is selected by the user, the user's computer contacts the administrator web server with the submenu entry identifier to retrieve the most current URL associated with that submenu entry identifier (as in FIG. 7D). As each URL is retrieved from the administrator's web server, the URL is cached on the user's computer for future use. On each subsequent selection of that submenu entry, the navigation tool software retrieves the URL from the cached database and sends it to the Internet browser, while substantially simultaneously sending the submenu entry identifier to the administrator web server. If the URL associated with that submenu entry identifier has not changed since the last time that URL was accessed by that user, as identified by the software identification, the administrator web server takes no further action. If, however, the URL associated with that unique submenu entry identifier has changed since last accessed by that user, the administrator web server will transfer an updated URL to the navigation tool software on the user's computer for placement in the database and association with that unique submenu entry identifier. In another mode of customization, the web site administrator (244 in FIGS. 9-

10)(through agreement with web content providers for the navigation tool 100) provides a display link on the web pages of those content providers desiring to be added to a user's navigation tool. This display link operates in two modes, dependent upon whether the user which operates the link is a current user of the navigation tool bar: (1) If the user currently has the navigation tool installed on and used on their computer 242, selection of the link would add that particular content provider to the appropriate menu tree as described above; or

(2) If the user does not currently have the navigation tool installed on their computer 242 they are browsing with, selection of the link would transport the user to the web site 244 to enable the user to download the navigation tool, and to include on the menu bar 102 (see FIG. 8) the content provider which directed the user to the download site for the navigation tool bar. For reliability and robustness purposes, a particular user's data file is preferably periodically exchanged and stored on the web site 244 so that, if a catastrophic failure of a user's browser 50 occurred or updates of either the navigation tool 100 or the browser 50 occurred, a user can visit the web site 244 and obtain a backup copy of the user's data file wherein all links created could be immediately recovered.

It is contemplated that "default" status for a particular content provider on the web site 244 is offered periodically in an auction fashion. It is apparent that, for users who do not spend a great deal of time customizing their navigation tool 100, the default status for the content providers for each main-level category is extremely important. As the administrator of the web site 244 builds the index 260 with real- language contextual nicknames 270, the administrator is able to offer the user a choice as to which content providers are primarily listed under each main-level category. However, many users will, rather than actively choose from a list of content providers indexed by the administrator, will passively choose to use default settings entered by the administrator.

It is of great advantage to content providers on the Internet to increase traffic to their web sites and, therefore, it is advantageous to a content provider to be selected as the default provider under a main-level category relating to their business. The administrator can thereby offer the content providers the option of being listed as the default content provider, or being given a higher spot on the selection list available to users. Selection of those content providers that will be higher on the list, or that will serve as the default setting for the various categories, will be decided on an auction basis, those content providers agreeing to pay a higher fee receiving a higher priority, or higher placing, on the listing of content providers in each category.

In summary, the navigation tool 100 described herein contains those categories that are selected by a user from a predetermined list provided by the administrator of the web site 244. Navigation by the user within each main-level category leads the user to subcategories, with links to content providers web page content.

The user continually has the opportunity to customize their selection of content providers and the organization of the interface provided by the navigation tool 100. This customization can be accomplished by accessing the service provider's web site, and doing an online customization, or can be done on the user's own computer 242, doing a local customization. The online customization is effective in providing the user with the opportunity to access the most up to date indexes 260 of content providers created by the administrator. The local customization options are most effective for allowing customized organization of the hierarchy as it is viewed by the user. A further description of these customization methods follows.

Referring to FIGs. 8-18, an inventive feature of a navigation tool 100 is a method for installing and updating the menu bar 102 of the navigation tool 100 to initiate use thereof. In the embodiment described herein, it is contemplated that the creation of a user's initial configuration and subsequent reconfigurations of the navigation tool 100 can be performed on an administering party's web site. In an initial online configuration, a user would be provided with either installation software or a direct URL address to the administering party's web site for configuration of the navigation tool 100. For subsequent reconfigurations, a user can select the system menu 114 and enters the Customize submenu 222 through the Customize menu entry 220 therein as shown in FIG. 8, and selects the Online menu entry 224.

Entering the URL address, running installation software or selecting the Online entry 224 preferably enters the user into the online customization method as outlined in the schematic of FIG. 9. It will be understood that the preferred embodiment of an online configuration and customization is shown in FIG. 9, however, a more standard configuration using installation software distributed on recorded media can also be used without departing from the scope of this invention. FIG. 9 shows the general schematic process for configuring and customizing the navigation tool 100 and downloading the configuration for the navigation tool 100 to a user's computer. FIG. 10 shows a sub-process for the method of FIG. 9 relating to a user's selection of content for the navigation tool. FIGS. 11-13 relate to example web pages for selection of the particular web site content.

Turning to FIG. 9, a user computer 242 has a connection to an administering party's web site 244 having scripting adapted to allow the user to select categories and specifics of content providers (246) for the navigation tool 100. Once the content for the navigation tool 100 has been selected (246), the web site 244 builds a data stream containing the navigation tool 100 including one or both of executable code and a data file for the navigation tool 100 (248). The web site 244 can store the data file for archival purposes and an optional subsequent step of this method can include the recordation of a logon ID and a password for a user (250) to later recover the contents on-line (252). The data stream is then sent to the user's computer 242 (254), (256) wherein a command built into the data stream installs the data file and/or the executable code contained in the data stream into the Internet browser 50 (258).

The step (246) of selecting content for the navigation tool 100 is described in greater detail in FIG. 10. As shown in FIG. 10, the web site 244 contains an index 260 which contains the directory stmcture for all web pages of content providers available for selection by the user cross-referenced with a real-language contextual nickname for the content available on each web page. This index 260 can be as simple as a database 262 having tables of the directory stmcture of various content providers 264. Each table record 266 contains fields relating to a URL or domain name address field 268 and a corresponding nickname field 270 containing a real- language contextual name for the content of the web page identified by the URL field 268. The web site 244 preferably employs a frequent updating routine to the indexer 260 so that a user's settings are current. The user's browser 50 can connect to the web page 244 wherein the user can build and select content providers and arrange selected main level topics and sublevel topics for the navigation tool 100. The first step in building the navigation tool 100 is selecting which main-level category menus (shown by example with reference numerals 104-112) (272). A sample web page is shown in FIG. 11 having an example content window 52 containing with an interface for selecting the main-level category menus (272). The particular content of the categories (Search, Auctions, Tickets, etc.) are shown only by example.

Another step in building the navigation tool 100 is selecting which content providers will be assigned to provide the addressing links for the submenu system of each main-level category selected (274). A sample web page is shown in FIG. 12 having an example content window 52 containing with an interface for selecting the content providers for a main-level category (274). FIG. 12 shows content providers for the "Shopping" menu - selected only by example having selectable sub-categories of "Books" (with http ://www. amazon.com shown by example as a selectable content provider) and "Stores" (with "The Gap" and "Macy's" shown by example as selectable content providers). Each content provider and sub-category of the main-level categories are shown only by example.

Another step in building the navigation tool 100 is selecting either the default directory tree stmcture for each particular content provider (selected in step (274)) or specifying a subset of the directory tree stmcture (276). A sample web page is shown in FIG. 13 having an example content window 52 containing with an interface for selecting a subset of the selected content provider's directory tree stmcture from the index 260 (276). The particular selectable directory tree is shown only by example.

In each of steps (272), (274) and (276) and as portrayed in FIGS. 11-13 in the methods of FIGS. 9-10, the user can then execute the step of building the data stream (248), (254) by instmcting the customization web site 244 to do so. In the web pages shown by example in FIGS. 11-13, a user can press a button 278 (titled "Update Toolbar") to perform these instmctions. This step need only be performed once at the end of the entire customization routine - but can be performed at intervals during the customization of the navigation tool 100 without negative consequence. For example, under any given main-level category, such as Shopping, as depicted in FIG. 11 , the Shopping category may have a subcategory entitled Books as shown in FIG. 12. The subcategory Books, unlike the subcategory Stores, may not have a choice between content providers. A default bookstore may have been selected by the user, or by the service provider, and the bookstore categories are divided by subject matter or area, but the bookstore itself and the language necessary to identify the bookstore is not necessarily displayed in the resulting navigation tool - which, once the content provider has been selected by the user - need only be identified as "Books." The user can, of course, have the menu customized to include that information if the user so desires, or to select another book content provider, of the user's choice - should one be available. In the alternative, as shown above under the Shopping category of FIG. 12, the subcategories can be divided up by the vendor, and then within each vendor, can be divided up by category or subject matter.

It is another inventive feature of the navigation tool that the administrator of the web site 244 can provide updates to identified users of the navigation tool of updates to the index 260, described with respect to FIG. 10 In this form of customization, the administrator of the web site 244 provides requests to the users (such as from the user information stored with respect to the user's logon D and password (250), (252)) when new content becomes available for online customization. For example, the web site 244 sends e-mail requests to users of the navigation tool 100 to request whether the new content added to the index 260 is to be added to their navigation tool 100. A link is provided in the e-mail message which mns a script downloaded from the web site 244 for automatically installing the new content within the menu tree of the navigation software. Thus, the navigation tool 100 is dynamically updated with new content. The same update routines can be run with respect to links in the index 260 which have been changed and these changes must be propagated to a user's navigation tool 100.

Another mode of customization contemplated by this invention is monitoring a user's history of use of the software, specifically the usage history of the various menu items. The usage of these menu items is monitored with respect to those menu items that are not used. Once a predetermined length of time has passed, the user will be offered the option of discarding those menu items that the user has not utilized. In this manner, the navigation tool 100 is kept in an optimized condition, not containing any line items that are superfluous for their lack of use. One way in which this feature is implemented is by providing a counter field for each entry in the database 158 which is incremented each time a user selects the menu entry corresponding to that entry in the database 158. Thus, counter fields which are much lower than other counter fields in the database 158 would prompt the inquiry about removing the menu bar.

Another aspect of this mode of customization is based upon a monitoring of the usage of the navigator tool bar features, web pages accessed, general content of Internet information accessed, browsing history, general browsing habits, and other methods of navigation (e.g. "back" and "forward" buttons on the Internet browser and manual typing of URLs in the address line of the browser screen). The software will present the user the option of adding features to the tool bar to keep the process of Internet navigation as streamlined as possible.

For example, if a user loaded a particular web site address but did not select that menu item for a predetermined extended period of time, a message could be provided to the user of whether to delete that particular menu item to reduce the size of the menu items thereon to a particular useable level. As a further example, if a user frequently visits a particular web site, but that web site is not installed on the navigation tool bar, this notice could be provided to the user. The distinct advantage of the real language context nature of the navigation tool 100 is to remove the sometimes cryptic descriptions on web sites that have been constructed by many different web authors. Different web sites also utilize different indexing systems, or will respond to different types of queries when seeking the same type of information. In order to optimize the navigation tool 100 for the particular user, and ease the user's access to sites which the user more frequently accesses, the software is capable of monitoring the usage patterns of the user, and prompting the user with suggested updates to the hierarchy of the software. For example, if the user never accesses a particular category that is embedded in the hierarchy of the software, the user, after a pre-selected period of time, can be notified of such non-use, and offered the option to remove a particular unused category from the embedded hierarchy. Such a feature can be deactivated by the user. Another example of such dynamic updating would occur for a user that frequently accesses a particular subcategory. The user could be offered the option to move that particular subcategory up in the hierarchy to ease the user's access to that subcategory.

Another embodiment of a dynamically updated hierarchy pertains to a user being prompted by the administrator, upon access to the Internet, with new content providers that the service provider has indexed. The user is offered the option of adding the content provider to the appropriate category and subcategory within their embedded hierarchy.

FIG. 14 shows the Internet browser 50 with the Clickguide System menu 114 selected in the menu bar 102 which includes a Customize menu entry 220 which points to a customize submenu 222 having Online and Local submenu entries 224 and 226, respectively. The following describes the routine for local customization of the navigation tool 100 which is prompted when a user selects the local submenu entry 226 from within the Customize submenu 222. FIG. 15 shows a Customize window 228 which appears when the Local submenu entry 226 is selected from the Customize submenu 222. The Customize window 228 includes a content window 230 having a directory tree stmcture 232 shown in graphical form. The directory tree stmcture 232 shows a typical folder/file expandable tree representing the main-level categories 114 and the subsequent submenu system 115, 122 and 130 (see FIG. 18). Of course, additional or fewer submenu systems can be used without departing from the scope of the invention depending upon the particular configuration of the directory tree employed by the user. The folders and files (web links) shown in the directory tree 232 can be reorganized by the well known drag-and-drop method of directory tree reorganization. Thus, the main-level categories 114 and their associated submenus 115, 122 and 130 can be reorganized as desired by the user. Each drag-and-drop operation repopulates the menu bar 102 with the new directory tree stmcture 232 of the desired main-level categories 114, submenus 115, 122 and 130 and the web links contained therein. Of course, it will be understood that the tables contained in the database 158 are reorganized to reflect the changes in the directory tree stmcture 232. The process described in FIGS. 14-15 relates to a process for re-configuring or customizing the navigation tool 100 after the navigation tool 100 has been used. It is contemplated that the settings, tool bar selections, organization and database can be contained in a data file which is either stored on the user's local computer and/or archived on a administering party's web site. Using the organization and customization features shown in FIGS. 14-15, each user can locally configure a navigation tool 100 unique to their preferences.

The data file can be as simple as a text file to comprise the source of configuration and customization information used in the database 158 for the navigation tool 100. The data file contains the database 158 which is used to correlate the real-language contextual titles displayed in the main-level categories 114 and their associated submenus on the Internet browser 50, and the actual URL or domain name field, or the Java script that is mn in the various functions of the navigation tool 100. Further, a user can create and store multiple data files which can be selectively referenced by the tool bar, such as in a pull-down menu or in successive file open/close operations, to provide multiple configurations for each user. Since the navigation tool 100 is formed as a dynamic menu bar 102 which references a data file, a pointer can be changed from one data file to another so that multiple user settings can be maintained. Further, it is contemplated that users can exchange data files containing the customized configuration of the navigation tool by file exchanges such as ftp, e-mail recordable media, etc. Thus, if a particularly large amount of effort was expended by a user to construct the particular menu bar 102 for the navigation tool 100, one user can transfer the data file to another user wherein the user can merely download the particular data file into its own navigation tool 100. The navigation tool 100 is then dynamically updated and reconfigured based upon the new data file.

Turning now to the operation of the user interface of the navigation tool according to the invention, FIG. 16 shows an inventive system 200 for navigation of the Internet using a navigation tool 100 shown in FIG. 17. The navigation tool 100 is shown as a menu bar 102 deployed above the main menu bar 54 and button bar 56 in the Internet browser 50 as described in the background section. This type of installation of a software subcomponent is typically referred to as a "plug-in" or an applet which is installed as a part of the web browsing software resident on a user's computer. The client software can also be a separate executable application that attaches itself to identified browser or other software applications having a need for a navigation interface. It will also be understood that, although the navigation tool 100 is described with respect to a menu bar 102, any known graphical user interface can be substituted for the menu bar 102 without departing from the scope of this invention. Examples of other graphical user interfaces that could be substituted for the menu bar 102 include a button bar, a separable tool bar, a separate application window, etc. The menu bar 102 of the navigation tool 100 includes several main-level category menus 104, 106, 108, 110 and 112 titled "Search", "Misc.", "Shopping", "Sports", and "Tickets", respectively. It will be understood that the titles for these main-level category menus 104-112 are shown for illustrative purposes only and other main-level categories can be employed without departing from the scope of this invention. The main-level category menus 104-112 each include a resident directory stmcture contained therein whereby a user can select from the main-level category menus 104-112, navigate through the directory stmcture contained within a particular main- level category menu 104-112 and select an item contained within one of the menus. This type of menu navigation is frequently employed in graphical user interfaces and, therefore, the particular methods of pointing and clicking a mouse cursor to select menus, submenus, and entries in the menu and submenus are described further. They will merely be referred to by using the common well-known terms of highlighting, selecting, clicking, etc.

The menu bar 102 of the navigation tool 100 also includes a system menu 114 titled "Clickguide" — a proposed product name used to identify the menu bar 102. The menu bar also includes a system menu 116 entitled "Favorites". The system menu 116 is a drop-down menu (not shown) for selection of alternate main-level category menus that a user may select in lieu of the menus 104-112 shown. By way of example, the list of menus 104-112 could be embedded in the system menu 116, and, upon selection of a menu, say "Shopping" 108, the submenus of "Shopping" 108 would populate menu bar 102. If the user was concentrating on sports, the submenus of "Sports" 110 would repopulate menu bar 102. As a further possibility, access to the Favorites menu 60 located on the main menu bar 54 could be provided to allow a user to conceal the main menu bar 54 if desired and use the menu bar 102 of the navigation tool 100 according to the invention. As shown in FIG. 16, to use system 80 with the navigation tool 100 built into the Internet browser 50, the Internet browser is first launched 82, which, in turn, brings up the "home" page for the Internet browser 84 as is well known in the art. At this point, a user clicks on one of the main-level category menus 104-112 (86 in FIG. 16) and navigates through any sublevel categories and selects an entry in one of the main-level category menus 88. It is an important feature of this invention that the selection made in step 88 corresponds to a hyper text link to a particular web page using a URL or domain address. Rather than the user of the Internet browser 50 being required to build a tagged list (Favorites or Bookmarks) in an entry-by-entry fashion, the navigation tool 100 is pre-loaded with a directory stmcture submenu system corresponding to each of the main-level category menus 104-112. In addition, the user can select a content provider for each of the main-level category menus 104-112 and the software is pre-loaded with real-language context nicknames applied to URL or domain name addresses contained within the web site of the context provider selected by the user. In this fashion, the user is not required to build a Favorites or Bookmarks, i.e., a tagged list, of selected web pages. Rather, a user selects a particular content provider for a particular main- level category menu 104-112 and the menu stmcture of the menu bar 102 is pre-loaded with real-language context entries which correspond to URL to allow real-language selection of information desired by a user of the navigation tool 100. An example menu in submenu stmcture for one of the main-level category menus 104-112 is shown in FIG. 18. A group of main-level categories is shown generally by reference numeral 114 and a sublevel menu 115 is shown for one of the main-level category menus 108. Although the sublevel menu 115 is shown for the "Shopping" main- level category menus 114, it will be understood that each of the main- level category menus can have a similar submenu stmcture with appropriate content and context therefor. The sublevel menu 115 has a pair of sample menu entries 118 and 120, namely, "Books" and "Stores", respectively, which contextually relate to the parent level for the sublevel menu 115, i.e., the "Shopping" menu 108.

A sample second-level submenu 122 stmcture is provided for the first-level submenu 120 as well. This sublevel menu 122 has three sample entries 124, 126, and 128, titled "Home", "All Categories", and "Help", respectively.

The "All Categories" submenu entry 126 relates to a further third-level sublevel menu 130 which has sample entries 132, 134, 136, 138, 140, and a catch-all entry representing an undetermined number of additional entries 142. The entries are entitled "Best Sellers", "Art Architecture", "Audio Books", "Biographies", "Children's Books", and "Etc.", respectively. Additional sublevel menus are also possible (e.g., specific book categories under "Children's Books" as opposed to a URL as illustrated). The menu entries provided in the main-level category menu 114, the first-level submenu 115, the second-level submenu 122, the third-level submenu 130 and the remainder of the menu stmcture for the main-level category menus 114 can relate to both a sublevel directory entry wherein a menu entry in a parent menu leads to a submenu in a sublevel menu or directly to hyper text link. To the extent that a menu entry in one of the main- level or sublevel menus outlined in FIG. 18 relates to a hyper text link, selection of that menu entry sends a command to the Internet browser 50 to insert a URL to which the selected menu entry relates. The Internet browser 50 thereby has the URL or domain name address inserted into the address bar 58 and the Internet browser 50 navigates to the desired web page.

This relation between a real-language context entry denoted by the menu entries 104-112, 118-120, 124-128 and 132-142 permits a user to navigate the main- level category menus 114 and their associated submenus (such as those shown by reference numerals 115, 122 and 130). Further, to the extent that a menu entry relates to a command to navigate to a particular hyper text link, the menu entry title, such as "Best Sellers" or "Biographies", submenu entries 132 and 138 of sublevel menu 130 relate in a database to a corresponding URL. The following table shows an example of the relation between the real- language context menu entries 132-140 and their associated links to particular URL or domain name address-referenced web pages shown in FIG. 18 by reference numerals 144, 146, 148, 150 and 152, respectively:

FIG. 18 also shows that submenu 115 can include both a link 154 to a home page of the "Stores" submenu 115, as well as a further submenu with a contextual entries for pages within that category.

FIG. 19 shows the main-level category menus 114 having example menu entries 104-112. FIG. 19 also shows a process routine 156, wherein a menu selection is received from the main-level category menus 114 that further queries a database 158 including the main-level category menus 104-112. The database contains several subentries 160 for each of the main-level category menus 114 that indicates whether the menu entry for a particular menu contains a link to a submenu or to a URL. A sample record of the database 158 shown by reference numeral 162 in FIG. 19 containing a submenu field 164, a nickname field 166, and a URL field 168. The submenu field 164 contains an address of a particular submenu linked to by the particular menu entry 160. The nickname field contains the real-language context entry for providing a user with a contextual name for a particular submenu or web address. The URL address field 168 contains the URL indexed by the nickname field 166. Of course, it will be understood that the database 158 in FIG. 19 is shown by example only. Many different database structures can be employed to accomplish the function of indexing submenu and URL into a directory tree without departing from the scope of this invention.

FIG. 20 shows the Internet browser with the Shopping main-level category menu 108 selected; the "Books" submenu entry 118 is selected as is further submenu entry of "All Categories" 126 of the second-level submenu 122. Further, "Computers lnternet", sublevel menu entry 170 of the third-level submenu 130 is also selected and a fourth-level submenu 172 has a "New-Releases" entry 174 selected therein. In this context, "New Releases" 174 corresponds to a URL rather than to a furthere submenu.

Once the fourth- level submenu 172 has the "New-Releases" submenu entry 174 selected, the navigation tool 100 looks up the appropriate URL field 168 in the database 158 and sends the contents of the URL field 168 to the address bar 58 in the Internet browser 50. The results of this operation is shown in FIG. 21, wherein the computers and Internet book page of a major book seller is shown within the content window 52 of the Internet browser 50. The navigation was accomplished by the user with a single mouse click which highlights the appropriate main-level category menu 114 and following subsequent navigation through the submenu stmcture of the main- level category menu 114 selected by the user. A release of the mouse button automatically sends the command to the address bar 58 of the Internet browser 50 which, in turn, displays the desired web page in the content window 52 of the Internet browser 50.

It is an important aspect of the navigation tool 100 that the navigation through the submenu stmcture of the menu bar 102 of the navigation tool 100 is performed by the user interpreting real-language nicknames (as contained in nickname field 166 of the database 158) rather than interpreting a URL.

FIG. 22 shows an advanced method of navigation that is another inventive feature of the navigation tool 100 according to the invention. FIG. 22 shows a first web page 176 having a URL of http://www.homepagel .com. The web page 176 has a string of text referred to as selectedtext 178. The process shown in FIG. 22 is appropriate when an entry in the URL field 168 of the database 158 requires that a parameter be entered along with the address or, alternatively, the web page which is the target of the URL does not require a parameter, but a flag can be attached to the command to navigate to the desired web page to automatically enter the parameter into the web page. This is typically done in HTML addressing by appending an "&" onto the address of the string and setting a variable or appending a text string after the "&" which represents a command to perform a particular routine. Once the user has the selectedtext string 178 highlighted as shown at step 180, then the user navigates the tool bar 100 as shown at step 182 to send the command to the destination page. Step 182 illustrates a similar approach to that shown by method steps 86-90 as shown in FIG. 16. In the advanced navigation method shown in FIG. 22, the selectedtext string 178 is appended to the field contents of the URL field 168 in the database 158 as shown by step 184. The selectedtext string 178 thereby becomes a parameter for the newly selected web page 186. The Internet browser 50 then navigates to a second web page 188 having an address of http://www.homepage2.com. In the example shown in FIG. 22, reference numeral 190 shows the command submitted to the Internet browser comprising the address ofhomepage2.com with an "&" and selectedtext 178 appended thereto. FIGS. 23-28 show examples of the advanced navigation feature shown in FIG. 22 of the navigation tool 100.

FIG. 23 shows a Internet browser 50 having the navigation tool 100 embedded therein, wherein the search menu 104 has been highlighted to display a submenu 192 thereof having submenu entries 194 (Movies Showtimes), 196 (Get Stock Quote), 198 (Search News), and 200 (Tools). The tools menu 200 is shown having a submenu 202 with entries Get Weather 204, Date and Time 206, Quick Calculator 208, Search Dictionary 210 and Search Thesaurus 212. As shown in FIG. 23, the Search Dictionary entry 210 of the submenu 202 has been highlighted.

As also noted in FIG. 23, the text "Register" 214 has been highlighted on the page prior to the user navigating through the menu bar 102 of the navigation tool 100. With selectedtext 178 (the highlighted text "Register" 214) highlighted, the user navigates through the menu bar 102 of the navigation tool 100 and selects the Search Dictionary entry 210 within the submenu stmcture of the Search Menu 104. This assumes that the URL field 168 of the database 158 contains a hyper text link to a particular dictionary web site which is capable of receiving a string parameter to look up a particular dictionary word within the dictionary web site.

As the command is performed, the string selectedtext 178 comprising the highlighted term 214 is sent to the dictionary web page which, in turn, returns the contents of a search for the term embodied in the selectedtext string 178 (which in this case happens to "Register"). The results of this search as shown in the content window 52 of the Internet browser 50 is shown in FIG. 24.

FIG. 26 shows Internet browser 50 having the navigation tool 100 embedded therein wherein the Search menu 104 as well as the Tools and Search Thesaurus submenu entries 200 and 212, respectively, have been highlighted. With selectedtext 178 (the highlighted text 214) highlighted, the user navigates through the menu bar 102 of the navigation tool 100 and selects the Search Thesaums entry 210 within the submenu stmcture of the Search menu 104. This assumes that the URL field 168 of the database 158 contains a hypertext link to a particular thesaums web site (i.e., http://www.thesaums.com) which is capable of receiving a string parameter to look up a particular thesaums word within the dictionary web site. As the command is performed, selectedtext 214 is sent to the thesaums web page which, in turn, returns the contents of a search for the term embodied in the selectedtext string 178 ("Register" 214). The results of this search as shown in the content window 52 of the Internet browser 50 is shown in FIG. 27.

FIG. 25 shows Internet browser 50 having the navigation tool 100 embedded therein wherein the Search menu 104 as well as the Search News submenu entry 198 are selected. A "Search (news content provider)" submenu entry 216 is then selected. In FIGS. 25 and 28, submenu entry 216 is labelled as "Search CNN News", with, for example, the web site address for http://www.cnn.com contained in URL field 168. A string of selectedtext 178 ("Register" 214) has been highlighted on the current page being displayed in the content window 52 prior to the user navigating through the menu bar 102 of the navigation tool 100. URL field 168 of the database 158 contains a hypertext link to a web site (e.g., http://www.cnn.com) which is capable of receiving a string parameter to search for occurrences of selectedtext 178 in news stories. As the command is performed, selectedtext 178 is sent to the news content provider's web page which, in turn, returns the contents of a search for the term embodied in the selectedtext 178 ("Register" 214). The results of this search are shown in the content window 52 of the Internet browser 50 shown in FIG. 28. It will be understood that this advanced navigation method employed with the navigation tool 100 can be employed with any web page capable of receiving a parameter or other criteria as a command. A user can thereby obtain weather, movie times, stock quotes, and a great deal of other information by merely selecting text in the content window 52 of the browser 50 and then navigating the menu bar 102 to select the desired target web address. A further embodiment of the navigation tool 100 lies in a dialog box (not shown) for prompting the user for text when a submenu entry requires input of selectedtext 178 and text has not been highlighted in the content window 52.

Unlike the content provider- or web site-driven navigation tools typically used by browsers, the instant invention utilizes a real-language, context-driven, hierarchy. Therefore, the user is given the opportunity to select the context of the subject matter which they are seeking, in a more directed fashion than going to a content provider's site and having to search within that content provider's site for the specific subject matter that they desire. The user can go directly through their embedded hierarchy on their computer 242, and take advantage of the indexing that has already been done by the administrator.

By going through the hierarchy built into the navigation tool 100 at the initial configuration stage, a user need only navigate through the menu stmcture based upon the context provided by the tree stmcture. Rather than needing to know http://www.bookstore.com/books/newreleases/computers (which may require knowledge of the www.bookstore.com web site as well as specific knowledge of the directory stmcture of the web site), a user would merely need to select the "Shopping" menu, "Books" submenu, "New Releases" submenu and select the "Computers" entry in the directory tree 232. The particular web site accessed (once this selection is made) has previously been decided by the selection of the content provider and the pre-loading of the directory stmcture indexed by real-language nickname into the navigation tool 100.

Another way of viewing the invention, or a further embodiment of the invention, is to explore the active interfaces between the Clickguide servers and clients, as shown in the tables to follow. All these interfaces will use the HTTP protocol, which will allow the Client software to work reasonably well behind a firewall. Any interface calls which cannot be executed due to errors will return an error value. This error value will contain a numeric error number and a text description. A sample eπor looks like "101 :User does not exist." The following discussion assumes the Client software has been installed on a user's desktop.

Provided here are the general use cases of the various active interfaces. The first interface to be called by the Client software is the GenerateSoftwareld interface (see also FIGs. 6B and 7B). The very first time Clickguide runs on a new user's desktop the GenerateSoftwareld interface is called to obtain an unique identifier for the Clickguide desktop. This identifier is then passed to all the subsequent calls to the Clickguide servers. The first time the client software starts after a desktop reboot, the

QueryServers interface should be called to determine the IP addresses of the Clickguide application and servers that can best service the user's desktop. For example, users in California will be directed to a different set of servers than users on the East Coast. The Client software will call interface VerifyUser to start a "session". A new session begins every time the software starts after a desktop reboot, or the user's session id expires. If the user sends a valid usemame and password combination, or the user is a guest user, the servers will send back a session id. The session id can be passed to any other server interface to authenticate the user. Sessions can expire, at which time the Client software must obtain another session id.

To obtain the menu files available for the user, the QueryMenuFiles interface can be called (see FIG. 7C). This interface returns a list of all of the user's menu files. Note that the user can access his own menu files from any location having the client software installed. Once the user logs in to the server ("VerifyUser") from any location, QueryMenuFiles has the usemame available through the session_id. The client software can then request menu files through the DownloadMenuFile interface. If the user would like to personalize his or her menu files, the client software can call the CustomizeMenu interface.

All Clickguide interfaces can recommend upgrades. If this happens an upgrade value in the interface response will indicate the version number of an upgrade available. Once this happens, the client should prompt the user to upgrade their software. If the user elects to upgrade the software the client will call the DownloadSoftwareUpdate interface to obtain an upgrade program.

ACTIVE INTERFACES GENERATESOFTWAREID

Input Parameters ammeter Name Type Description distribution id integer Specify which distribution this software should be associated with. version id integer Specify what release of software the client is.

Output Parameters ammeter Name Type Description sofhvare_id integer Server returns the unique software identifier for the client. upgrade integer Server indicates whether the client should upgrade its binaries error" string If an error occurs, describe what occurred.

Since all Client requests as described in the next sections require the transmission of a unique Software ID that identifies a particular Client installation, it is imperative for the freshly installed Client Software to communicate with the Application Server. The client software should obtain a Software ID before being used by the consumer for the first time. In fact the client software should be inoperable with out a Software ID. GenerateSoftwareld is called from Initial Client Usage scenario (FIGS. 6B, 7A, and 7B).

Once the Client is in possession of its SoftwarelD, we have accomplished the de-coupling of an Affiliate (or distributor) from its distributed software, while at the same time we have established the very first steps in providing full logging of Consumer activity, tying it back to the original Affiliate. The Software ED is the minimum amount of information (along with the preexisting, from installation, version ED) that is needed for any Consumer to initiate usage of the system. Client Software will be downloaded with a default menu stmcture, the one available during the creation of the distribution version of the software.

That same Software ED is to be used as part of the User ED (until at least the moment when a user actually registers with Clickguide). For example, all 'defaulted' user Ids will be of the following format: guest_(SoftwareID)

This implies that all manually specified user Ids must 'block' the above pattern. To distinguish between the two, we shall call manually entered user Ids 'user names'. A Consumer who never wishes to customize their menus, will keep using the Guest user ID transparently. No password is needed at this stage. The only functionality Consumers can then use is the menu links of the Clickguide menu associated with a standard installation for an Affiliate (or distributor).

Example Client sends: http://AppServerX//serylet GenerateSoftwareED?version id=&distribution id=

AppServerX replies:

SoftwareED=(uniquely generated ED (numeric) that also becomes the default, 'under the hood' user ED for this 'new' account)

Upgrade=(Returns a 1 if a software upgrade should occur; a 0 otherwise. See DownloadSoftwareUpdate interface.)

DOWNLOADSOFTWAREUPDATE

Input Parameters

¹ 'ammeter Name Type Description software_id integer Identify which client software installation is requesting the

URL redirection.

Output Parameters

Parameter Name Type Description none An encoded (and perhaps) compressed string of bytes containing the requested file error* string If an error occurs, describe what occurred.

Periodically the Client software will be updated. This method will return an upgrade program to update the client software to the latest version.

Example

Client sends: http://AppServerX//serylets/DownloadSoftwareUpdate?software id=10

AppServerX replies: <a set of bytes representing an encoded (and perhaps compressed) f ile >

QUERYMENUFILES

Input Parameters

"ammeter Name Type Description software_id Integer Identify which client software is making the request. version id Integer Identify what version of the software the client is running. session id Integer Identify the user session orginating the requests. (Obsoletes usemame and password) usemame* String The user who is requesting the download. password* String The password of the user

Output Parameters

^Parameter Name Type Description menu_l string ED and Description of the first menu menu_2 string ID and Description of the second menu menu_n string ED and Description of the n-th menu upgrade string Server indicates whether the client should upgrade its binaries. error* string If an error occurs, describe what occurred.

The Client software can query the Clickguide servers for the menus available to the user. However, guest users will only have system default menus available to them. Registered users on the other hand will receive system default menus and any customized menus they may have created.

If the session_id does not match any session data in the database or the session has expired an error will be returned indicating this.

The menus returned to the user will contain three pieces of information menu_id, menu_description, and menu_timestamp. Menu_id is the identifier that can be used to retrieve the menu file with a call to DownloadMenuFile. Menu_description is an English explanation of the contents of the menu file. Menu timestamp is the ei- current timestamp of the file measured in seconds since January 1 , 1970.

Example

Client sends: http://AppServerX//serylet/QueryMenuFiles?software id=10&version id=2&session id=10345

AppServerX replies: menu_l=l :News : 947283651 menu_2=2 : Education: 947283651 menu_3=3 : Finance : 947283651 menu_4=4 : Sports : 947283651 menu_5=5 :Religion: 947283651

QUERYSERVERS

Input Parameters

^Parameter Name Type Description software_id integer Identify which client software is making the request. version_id integer Identify what version of the software the client is running.

Output Parameters

¹ 'ammeter Name Type Description app_server_l string A host name, indicating what primary application server the client should send requests to. redir server 1 string A host name, indicating what primary redirection server the client should send requests to. app_server_2 string A host name, indicating what secondary application server the client should send requests to. redir server 2 string A host name, indicating what secondary redirection server the client should send requests to. upgrade integer Server indicates whether the client should upgrade its binaries. error'¹ string If an error occurs, describe what occurred.

The Clickguide client needs to know which of the Clickguide application or redirection servers the client can obtain its content from. This Interface returns to the client which servers the client should send its requests to. Example

Client sends: http://AppServerX//serylet/QuervServers?software id=10&version_id=l

AppServerX replies : app_server_l=app01 . clickguide . com redir_server_l=redir01 . clickguide . com app_server_2=app02 . clickguide . com redir_server_2=redir02 . clickguide . com

Upgrade= (Returns a 1 if a software upgrade should occur; a 0 otherwise . See DownloadSoftwareUpdate interface . )

DOWNLOADMEN UFILE

Input Parameters ammeter Name Type Description softwarejid integer Identify which client software is making the request. session_id integer Identify the user session orginating the requests.

(Obsoletes usemame and password) usemame* string The user who is requesting the download. password* string The password of the user menu id integer The menu id to download.

Output Parameters

^Parameter Name Type Description none An encoded (and perhaps) compressed string of bytes containing the requested file error ^y string If an error occurs, describe what occurred.

The Clickguide client may request menu files through the DownloadMenuFile interface (see FIG. 7D). This method will request a menu file specified by a menu id. The menu id is obtained on a prior call to the QueryMenuFiles interface. If the menu file specified is a personal menu file, the menu file will only be returned if the user's session_id is valid and the user is the owner of the menu file. Like the QueryMenuFiles interface, guest users may ask for system default menus. The menu files may be sent as a compressed file stream in the future.

Example

Client sends: http://AppServerX//serylet/DownloadMenuFile?software id=l 0&session_id=l 0345& menu id=10

AppServerX replie :

(a set of bytes representing an encoded (and compressed?) file )

CUSTOMIZEMENU

Input Parameters

'ammeter Name Type Description software_id integer Identify which client software is making the request. version id integer Identify what version of the software the client is running. session_id integer Identify the user session orginating the requests.

(Obsoletes usemame and password) usemame^'3' string The user who is requesting the download, password* string The password of the user menu id integer The menu id to customize.

Output Parameters

'ammeter Name Type Description url string The url to redirect the browser to for menu customization. upgrade integer Server indicates whether the client should upgrade its binaries. string If an error occurs, describe what occurred.

The Clickguide client may request menu files to be customized (see FIGS. 8- 13). This interface will return the AppServer URL to perform the customization. The client software should redirect the browser to the URL returned by this interface. The session_id authenticates the user. If the session does not exist or has expired, an error message indicating this will be returned.

Example

Client sends: http://AppServerX /serylet/CustomizeMenu?software id=l 0&version_id=l &session id=10345&menu id=10

AppServerX replies: url=(URL that browser should be redirected to) upgrade= (Returns a 1 if a software upgrade should occur; a 0 otherwise . See DownloadSoftwareUpdate interface . )

VERIFYUSER Input Parameters

'ammeter Name Type Description software_id integer Identify which client software is making the request. version_id integer Identify what version of the software the client is mnning. usemame string The requested user name. password string The UNIX encrypted password

Output Parameters ammeter Name Description success int Indicate whether the new user was created or not. 0=false,l=tme upgrade integer Server indicates whether the client should upgrade its binaries. session id integer Identify the user session orginating the requests. (Obsoletes usemame and password to other interfaces) error" string If an error occurs, describe what occurred.

The VerifyUser interface is used to authenticate users to the Client software. A valid usemame/password combination allows the user to see his or her personalized menus. The interface will return a 0 for authentication failure and a 1 for authentication success. In addition a session_id will be returned for the client to pass to other server interfaces that require user authentication. The password will be encoded using Unix style encryption. The password field is only required for registered users. If the user_id starts with "guest_" a password is not needed.

Sessions are created for registered users and guest users. The session ids can then be passed to any other interface that requires authentication.

The error ouput parameter will contain the description of any errors that occur.

Example

Client sends: http://AppServerX//serylet/VerifVUser?software_id=10&version id=l&username=so viet&password=ksjdl 212**

AppServerX replies: success=0 session_id=0

Upgrade= (Returns a 1 if a software upgrade should occur; a 0 otherwise. An embodiment of a client/server physical and relational configuration according to the invention is shown in FIG. 29. The client computer ("Web Client") communicates with the "Re-direction Server", which maintains a database relevant to the client computer. The re-direction server communicates with the "Admin Server" to periodically synchronize its content. For an embodiment wherein an "Application Server" is established in an enterprise or intranet environment, the "Web Client Intranet" client computer communicates with the "Application Server", which in turn communicates with the "Admin Server". The "Admin Server" serves as a permanent repository for the information generated according to the invention.

A further view of an aspect of the invention, embodied in an example database schema for database 1040, is outlined in the following Table 1. The schema for the database 1040 comprises a table abbreviation (TABLE ABBREV), a field identifier (FIELD), a flag indicating whether the particular field is a primary key index (PK) or a family key index (FK) and to which primary key the particular family key is interconnected to (REF), and the field data type (FEELD TYPE) - whether a number (NUMBER), date (DATE), variable character string (VARCHAR), etc., and whether there is a condition on the field that the corresponding field cannot be null (NULL COND), e.g., NOT_NULL. An outline of the interconnections between the PK and FK indices for the fields of Table 1 for the database 1040 is illustrated in FIG. 30.

It will be understood that the schema for the database 1040 shown in Table 1 and in FIG. 30 is by example only and it is contemplated that any suitable database stmcture accomplishing the results and functions in the appended claims is also contemplated. Variations in the database stmcture shall not be limiting on the concepts in the appended claims.

While the invention has been specifically described in connection with certain specific embodiments thereof, it is to be understood that this is by way of illustration and not of limitation, and the scope of the appended claims should be construed as broadly as the prior art will permit. TABLE 1.

Claims

CLAIMSWhat is claimed is:

1. An interface for a client located on a distributed network of clients and servers for selecting desired content on other clients and servers on the network by accessing a database on a remote computer, the database having a list of target navigation addresses of the desired content and an index corresponding thereto, the interface comprising: at least one user selectable actuator identified by a context-based identifier corresponding to the index of the list on the remote computer; and a first operable link to a browser on the client and a second operable link to the remote computer database, wherein the second operable link returns a target navigation address from the server database when the user selects the at least one actuator and the client browser is redirected to the returned target navigation address via the first operable link; whereby a user need not maintain an updated list of target navigation addresses on the client, but rather need only navigate via the context-based identifier on the at least one actuator of the interface and any changes to the target navigation address can be maintained on the server.

2. The interface of claim 1 wherein the at least one actuator comprises a series of actuators each with a unique context-based identifier.

3. The interface of claim 2 wherein the series of actuators is organized into a hierarchy based upon relationships between the context-based identifiers in the series of actuators.

4. The interface of claim 3 wherein the hierarchy is a menu system.

5. The interface of claims 1-4 wherein the context-based identifier for the at least one actuator is preselectable based upon a particular distribution origin for the interface.

6. The interface of claims 1-5 wherein the context-based identifier for the at least one actuator is preselectable based upon a particular affiliate relationship with the remote computer.

7. The interface of claims 1-6 wherein the remote computer transmits the content of the context-based identifier for the at least one actuator via the second operable link.

8. The interface of claims 1-7 wherein an initial configuration of the interface is received from the remote computer via the second operable link.

9. The interface of claims 1-8 and further comprising a client database located on the client that receives at least one of context-based identifiers and target navigation addresses from the server database.

10. The interface of claims 1-9 wherein the client database is periodically updated with at least one of refreshed context-based identifier information and target navigation address information via the second operable link.

11. The interface of claims 1-10 wherein the context-based identifiers for the interface are stored in a form independent of a particular type of client browser.

12. The interface of claims 1-11 wherein any text selected by a user prior to actuating the at least one actuator is tagged to a subsequent redirection to a target navigation address to provide the selected text as data to the selected content.

13. A system for managing context-based navigation on a distributed network of servers and clients comprising: a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an index identifying the target navigation address; at least one client located on the distributed network having a client database having at least one row element, the at least one row element containing a context- based identifier, wherein each of the at least one row element context-based identifiers corresponds to the index; and an interface located on the client having at least one actuator corresponding to the at least one row element context-based identifier, wherein selection of the at least one actuator returns a target navigation address from the server database corresponding to the selected context-based identifier; whereby a user of the client need not maintain the client database because any changes in the target navigation address can be made in the server database because the client refers only to the index.

14. The system of claim 13 and further comprising a redirector for directing the client to the returned target navigation address.

15. The system of claims 13-14 and further comprising a maintenance routine for confirming whether the target navigation address is active.

16. The system of claims 13-15 and further comprising a cached list on the client containing recently-selected context-based identifiers and the returned target navigation addresses.

17. The system of claims 13-16 and further comprising a comparator for looking up the context-based identifier in the cached list corresponding to the context- based identifier of subsequently selected actuators and redirecting the navigation of the client to the target navigation address if a match is found in the cached list.

18. The system of claims 13-17 and further comprising a validator for looking up the context-based identifier of subsequently selected actuators in the server database to confirm that the target navigation address located in the cached list is the same as the target navigation address in the server database corresponding to the context-based identifier.

19. The system of claims 13-18 wherein the target navigation address is a URL.

20. The system of claims 13-19 wherein the target navigation address is a domain name.

21. The system of claims 13-20 and further comprising a navigation log on the server containing at least a client identifier and a selected target navigation address.

22. The system of claims 13-21 wherein the client identifier and each selected target navigation address are appended to the navigation log, whereby profile information can thereby be compiled and reported by at least the client identifier and the target navigation address.

23. The system of claims 13-22 wherein the client database further includes a second index corresponding to the context-based identifier, wherein the second index relates to the first index of the server database.

24. A method for managing context-based navigation on a distributed network of servers and clients comprising the steps of: maintaining a server database on a server located on the distributed network having at least one row element, the at least one row element containing a target navigation address and an index identifying the target navigation address; distributing a client database to at least one client located on the distributed network, the client database having at least one row element, the at least one row element containing a context-based identifier, wherein each of the at least one row element context-based identifiers corresponds to the index; and installing an interface on the client having at least one actuator corresponding to the at least one row element context-based identifier, wherein selection of the at least one actuator returns a target navigation address from the server database corresponding to the selected context-based identifier; whereby a user of the client need not maintain the client database because any changes in the target navigation address can be made in the server database because the client refers only to the index.

25. The method of claim 24 and further comprising the step of redirecting the client to the returned target navigation address.

26. The method of claims 24-25 wherein the maintenance step comprises confirming whether the target navigation address is active.

27. The method of claims 24-26 and further comprising the step of maintaining a cached list on the client containing recently-selected context-based identifiers and the returned target navigation addresses.

28. The method of claims 24-27 and further comprising the step of comparing the context-based identifier in the cached list corresponding to the context- based identifier of subsequently selected actuators and redirecting the navigation of the client to the target navigation address if a match is found in the cached list.

29. The method of claims 24-28 and further comprising the step of validating the context-based identifier of subsequently selected actuators in the server database to confirm that the target navigation address located in the cached list is the same as the target navigation address in the server database corresponding to the context-based identifier.

30. The method of claims 24-29 and further comprising the step of maintaining a navigation log on the server containing at least a client identifier and a selected target navigation address.

31. The method of claims 24-30 and further comprising the step of appending at least the client identifier and each selected target navigation address to the navigation log, whereby profile information can thereby be compiled and reported by at least the client identifier and the target navigation address.

32. A system for navigation on a distributed network of servers and clients while determining and tabulating the number of clients delivered to particular addresses on the network comprising: a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an affiliate index corresponding to the target navigation address; an affiliate database on the distributed network identifying affiliates of the server corresponding to the affiliate index, corresponding target navigation addresses of each affiliate and an affiliate counter for identifying the number of delivered clients from the server to each affiliate; at least one client located on the distributed network; an interface located on the client having at least one actuator for sending a target navigation address identifier to the server, wherein selection of the at least one actuator directs the client to the server with an indicator corresponding to the target navigation address identifier; and a redirector located on the server, wherein the redirector redirects the client to the selected target navigation address and increments the corresponding affiliate counter if the target navigation address corresponds to an affiliate index; whereby the number of clients delivered to an affiliate can be easily determined by querying the affiliate database and business relationships based upon the volume of clients delivered to an affiliate can be easily formed and maintained.

33. The system of claim 32 wherein the target navigation address identifier on the interface comprises a context-based identifier and the server database further comprises a corresponding context-based index for each target navigation address.

34. The system of claims 32-33 wherein the interface further comprises at least one default target navigation address identifier corresponding to an affiliate in the affiliate database.

35. The system of claims 32-34 wherein the context-based identifier for the at least one default target navigation address relates to the subject matter content of the corresponding affiliate.

36. The system of claims 32-35 wherein the affiliate corresponding to the at least one default target navigation address can be replaced by another affiliate through a competitive bid process.

37. The system of claims 32-36 wherein an affiliate purchases positioning as a default target navigation address.

38. The system of claims 32-37 wherein an affiliate pays an administrator of the server a fee for delivering clients to the affiliate target navigation address.

39. The system of claims 32-38 wherein the fee is proportional to the number of clients delivered to the affiliate target navigation address.

40. The system of claims 32-39 wherein the affiliate database is located on the server.

41. A method for determining and tabulating the number of clients delivered to particular addresses on a distributed network of servers and clients comprising the steps of: maintaining a server located on the distributed network having a server database having at least one row element, the at least one row element containing a target navigation address and an affiliate index corresponding to the target navigation address; interconnecting the server to an affiliate database located on the distributed network identifying affiliates of the server corresponding to the affiliate index, corresponding target navigation addresses of each affiliate and an affiliate counter for identifying the number of delivered clients from the server to each affiliate; providing an interface to at least one client located on the distributed network, the interface having at least one actuator for sending a target navigation address identifier to the server; redirecting the client to the server upon selection of the at least one actuator with an indicator corresponding to the target navigation address identifier; incrementing the corresponding affiliate counter if the target navigation address corresponds to an affiliate index; and redirecting the client to the selected target navigation address; whereby the number of clients delivered to an affiliate can be easily determined by querying the affiliate database and business relationships based upon the volume of clients delivered to an affiliate can be easily formed and maintained.

42. The method of claim 41 wherein the target navigation address identifier on the interface comprises a context-based identifier and the server database further comprises a corresponding context-based index for each target navigation address.

43. The method of claims 41-42 wherein the interface further comprises at least one default target navigation address identifier corresponding to an affiliate in the affiliate database.

44. The method of claims 41-43 and further comprising the step of relating the context-based identifier for the at least one default target navigation address to the subject matter content of the corresponding affiliate.

45. The method of claims 41-44 and further comprising the step of replacing the affiliate corresponding to the at least one default target navigation address with another affiliate through a competitive bid process.

46. The method of claims 41-45 and further comprising the step of selling a position as a default target navigation address to an affiliate.

47. The method of claims 41-46 and further comprising the step of receiving payment from an affiliate for delivering clients to the affiliate target navigation address.

48. The method of claims 41-47 wherein the fee is proportional to the number of clients delivered to the affiliate target navigation address.

49. The method of claims 41-48 wherein the affiliate database is located on the server.

50. A system for distributor-specific implementation of a navigation interface on a distributed network of servers and clients comprising: a server on the distributed network having an uncompiled interface code and a compiler for compiling the interface code into a distributable object upon receipt of a distributor identification code, wherein each distributor identification code is associated with a unique configuration of the interface by the server; at least one distributor having a unique distributor identification code having at least one of a distributable object compiled according to its unique distributor identification code, an installation module capable of invoking the compiler with its unique distributor identification code; at least one client on the distributed network that receives the unique configuration of the interface via the at least one distributor; whereby the configuration of the distributable object can be controlled based upon the distribution point and distributor based upon the unique distribution code.

51. The system of claim 50 wherein the installation module comprises a link to the compiler with its unique distributor code embedded therein.

52. The system of claims 50-51 wherein the installation module comprises a client-installed application that invokes the compiler with its unique distributor code.

53. The system of claims 50-52 wherein the installation module comprises a client-installed application having a compiler for creating the distributable object with its unique distributor code.

54. The system of claims 50-53 wherein the server has a default distributor code for producing a default configuration of the distributable object.

55. The system of claims 50-54 wherein the default distributor code is used by the compiler when no unique distributor identification code is received.

56. A method for distributing customized implementations of a navigation interface on a distributed network of servers and clients comprising the steps of: maintaining a server on the distributed network having an uncompiled interface code and a compiler for compiling the interface code into a distributable object upon receipt of a distributor identification code, wherein each distributor identification code is associated with a unique configuration of the interface by the server; assigning a unique distributor identification code to at least one distributor, the at least one distributor having at least one of a distributable object compiled according to its unique distributor identification code, an installation module capable of invoking the compiler with its unique distributor identification code; and distributing the unique configuration of the interface via the at least one distributor to at least one client on the distributed network; whereby the configuration of the distributable object can be controlled based upon the distribution point and distributor based upon the unique distribution code.

57. The method of claim 56 wherein the installation module comprises a link to the compiler with its unique distributor code embedded therein.

58. The method of claims 56-57 and further comprising the step of invoking the compiler with the unique distributor code via the client.

59. The method of claims 56-58 and further comprising the steps of invoking the compiler with the unique distributor code via the distributor and sending the distributable object to the client.

60. The method of claims 56-59 wherein the installation module comprises a client-installed application having a compiler for creating the distributable object with its unique distributor code.

61. The method of claims 56-60 and further comprising the step of assigning a default distributor code and producing a default configuration of the distributable object based upon the default distributor code when a unique distributor code is not received by the compiler.