CN1511291A - Method and system for connecting an end user to a network location - Google Patents

Abstract

A plurality of end users remotely access a network that includes a hub site and a number of provider sites. Information relating to the end user is associated with a non-externally identifying symbol. Public end-user information is shared with provider without permission from the end user. Private end-user information is shared with providers only upon receiving permission from the end user. The hub site receives codes from the end user and, based on the codes, directs the end user to a location on the network. The particular location to which the end user is directed may be based on criteria specified by a service provider, an expressed goal of the end user or property information of a session of the end user on the network.

Description

Method and system for connecting an end user to a network location

Field of the invention

The present invention relates to identifying a provider network location based on coded information provided by an end user.

Background of the invention

Bar code scanning technology has been used for quite some time. This type of barcode appears on many items that customers encounter every day—from grocery items to driver's licenses. Other types of codes, such as private codes, and methods of obtaining such codes, have been and continue to be developed. Bar codes and other codes allow for quick and easy identification, tracking, and cataloging of items, as well as storage of data related to such items. As barcodes have become a pervasive and familiar part of the consumer experience, there is use of web services and applications. Different types of web services and applications continue to grow in number and popularity.

Converging these two apparently disparate technologies to produce a product identification method that can provide mobility, simplicity, accuracy, convenience, and efficiency to web applications and services will enable companies to reduce costs (by using Bar code technology replaces previous manual tasks), increases revenue (by providing an effective advertising alternative to bar codes, familiarizes consumers with products, prices, storage locations, etc.), increases production (by automating sales force tasks such as product ordering), and improves consumption. customer loyalty (by providing barcode-related value-added services to consumers).

Summary of the invention

The present invention provides systems and methods for converged barcodes and other encoding technologies and web-based applications and services, thereby fulfilling needs arising in the prior art.

In particular, the present invention is directed to a system and method for storing and selectively sharing end user information. Multiple end users remotely access a network with at least one hub site and multiple provider sites. A user record corresponding to each end user is stored in a profile database associated with the hub site. Each user record includes public information, which an end user submits to the Hub site, and which the end user anticipates will be shared by one or more suppliers without the end user's permission, and private information, which the end user submits to the hub The Site, and the end user is not expected to be shared by any provider without the end user's permission; and a non-external identifier associated with the user record, identifying the end user on the network. In response to the first request signal including the non-external identifier, public information related to the end user is sent from the hub site to the provider without the end user's permission. Responses to the second request signal including the non-external identifier allow the request to be sent from the hub site to the end user. Private information pertaining to the end user is sent from the hub site to the provider only when the end user's permission is received in response to a permission request.

The present invention further relates to a system and method for an end user to identify provider locations on a network remotely accessed by the end user and having at least one hub site and a plurality of provider sites. Code information corresponding to the one or more codes provided by the end user is received at the hub site. In response to the code information, network address information corresponding to the provider's location on the network and associated with the received code information is retrieved from a profile database associated with the hub site. This network address information is used to point the end user to the relevant provider's location on the network. The profile database includes a user record corresponding to each end user. Each user record includes public information, which an end user submits to the Hub site, and which the end user anticipates will be shared by one or more suppliers without the end user's permission, and private information, which the end user submits to the hub The Site, and the end user is not expected to be shared by any provider without the end user's permission; and a non-external identifier associated with the user record, identifying the end user on the network.

Furthermore, the present invention relates to a method and system for transmitting information representing scanned machine-readable codes between network sites. Information relating to scans of one or more machine-readable codes formed by an end user is received at a first site. Information related to scanning of the machine-readable code is stored in a database associated with the first site, within a data record having a unique alphanumeric identifier associated therewith. End users are directed from a first site to a second site using a URL that includes both a symbol identifying the address of the second site on the network and a unique alphanumeric identifier associated with information stored at the first site. A request signal from a second site for information stored at the first site is received at the first site. The request signal contains a representation of a unique alphanumeric identifier. The stored information is transmitted from the first site to the second site in response to the request signal.

The present invention further relates to a system and method for identifying a supplier's location on a network for an end user and for retaining user annotation code information. The network has a hub site and multiple provider sites, accessed remotely by multiple end users. Code information corresponding to the one or more codes provided by the end user is received at the hub site. In response to the code information, network address information corresponding to the location on the network of the provider associated with the received code information is retrieved from a profile database associated with the hub site. This network address information is used to direct the end user to the relevant provider's location on the network at which user note code information is received from the end user at the hub site. User note code information is stored at the hub site.

Finally, the invention relates to a method and system for pointing an end user to a network location using information corresponding to a provider associated with the end user. A database is provided with a plurality of records, each record being associated with a different machine readable code. One or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different providers. Scanning information associated with scanning of one or more machine-readable codes formed by an end user using a remote scanning device is received at a network site. In response to the scan information, a record associated with the machine-readable code scanned by the end user is retrieved from the database. At least one network address is selected for each retrieved record. This selection may be based on criteria specified by the provider associated with the end user; goals expressed by the end user; or information about the nature of the end user's conversations on the network. A transmission is initiated from the network site to the end user's selected address.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

Brief description of the drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principle of the invention.

In the attached picture:

Figure 1A shows a preferred embodiment of a system for carrying out the method of the present invention.

Figure 1B shows a preferred embodiment of part of the management architecture of the present invention.

Figure 2A shows a preferred embodiment of a system for performing the method of the present invention.

Figure 2B shows a fragment of a code directory database usable in accordance with a preferred embodiment of the present invention.

Figure 3 illustrates the structure of end user profile information associated with an end user identifier, which may be used in connection with a preferred embodiment of the present invention.

4A and 4B illustrate exemplary user interfaces that may be employed by an end user in accordance with a preferred embodiment of the present invention.

FIG. 4C shows the structure for maintaining the end-user code list folder according to a preferred embodiment of the present invention.

Figures 5A and 5B illustrate two examples of the manner in which information may flow between components of a preferred embodiment of the system of the present invention.

Figures 6A to 6R illustrate an example of the manner in which the method of the present invention may be implemented according to a preferred embodiment of the present invention.

Figure 6S shows an example of a user interface on a cell phone that may be used in connection with accessing services in accordance with a preferred embodiment of the present invention.

Figure 7 shows a preferred embodiment of a system that can be used to implement the method of the present invention.

8A and 8B are flowcharts illustrating a method for storing and selectively sharing end-user information in accordance with a preferred embodiment of the present invention.

FIG. 9 is a flow diagram illustrating a method for an end user to identify a provider's location on a network in accordance with a preferred embodiment of the present invention.

Figure 10 is a flow diagram illustrating a method for an end user to identify a provider's location on the network and for storing user annotated code information in accordance with a preferred embodiment of the present invention.

11 is a flowchart illustrating a method for transferring information representing scanned machine-readable codes between sites in accordance with a preferred embodiment of the present invention.

Figure 12 is a flow diagram illustrating a method for directing an end user to a network location using information corresponding to a provider associated with the end user, in accordance with a preferred embodiment of the present invention.

Detailed Description of the Preferred Embodiment

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. The same reference numbers are used throughout the drawings to refer to the same or like parts.

Figure 1 shows a preferred embodiment of a system 1000 for performing the method of the present invention. The system 1000 includes a plurality of end users 500, each with a device that allows the end users 500 to scan or otherwise receive a code (ie, digit) associated with an end user's 500 expressed goal. The system 1000 also includes a platform 100 and a plurality of providers 600 . Platform 100 includes a number of components (explained more fully with reference to FIG. 2A ) that facilitate interoperation between end users 500 (and their associated devices) and services provided by providers 600 . As described in more detail herein, the functionality of the platform 100 is wide-ranging, but the primary function is as a switch, identifying code information, user context, and applications necessary to run services that help the end user 500 achieve stated goals program information. The platform 100 includes a hub site 101 accessible via the Internet 50 , which allows end users 500 and suppliers 600 to interact with the platform 100 .

The end user 500 can obtain the codes using various types of devices or capture techniques and send these codes to the platform 100 or the provider 600 . For example, an end user 500 may contact the platform 100 via a phone 5 and receive a code by dialing or dictating a code into a handset. This input is transmitted through the voice gateway 2005 to the Internet 50 and then to the voice response unit of the platform 100 or provider 600 . The end user 500 can also use the personal digital assistant 10 and transmit the code through the wireless application protocol gateway 2010 to the Internet 50 and then to the platform 100 or the provider 600 . In addition, the end user 500 can use a portable wireless scanner, or a scanner tethered to the end user client 15, to scan barcodes (eg, common codes including EAN, UPC, and JAN) private codes. These codes can then be transmitted and uploaded to the platform 100 by the end user 500 using the end user client 15 over the Internet 50 . Other means of obtaining the code and transferring it to the platform 100 or provider 600 are well known in the art and are thus within the scope of the present invention. The particular device used by the end user 500 dictates the functionality available to the system 1000 . As discussed in more detail below, devices and their identifiers govern aspects of access privileges and functionality available within system 1000 .

End users 500, platforms 100, and providers 600 can be connected to each other through different types of links to form a network. For example, end user 500 may connect to platform 100 via Internet 50 , directly via links 51 and 52 , or via provider 600 via links 51 , 53 , and 54 . In other embodiments, other possible connection configurations between the end user 500, the platform 100 and the provider 600 are known to those skilled in the art and thus are within the scope of the present invention. In some embodiments, one or more links between these various entities are wireless.

Providers 600 including service providers and access providers each host a provider site 601 accessible via the Internet 50 . Suppliers 600 are organizations that look to earn revenue from selling or making available items, materials or applications that they deem valuable. Providers 600 provide applications/services that accept codes as input and are responsible for identifying codes that can work with their applications/services. Providers 600 are responsible for registering and authenticating their communities/applications/services.

The administrative relationship between access providers and service providers can be described with reference to FIG. 1B. The access provider can establish an operational account 1195 within the platform 100 (using the code component 109 shown in and discussed with reference to FIG. 2A). Similarly, a service provider can establish an operating account within the platform 100 . Each end user 500 present on the network 2000 within the system 1000 is supported by at least one provider. Each access provider "owns" each end user 500 it supports, such that the access provider has unique authority to permanently stop the end user 500 it supports from accessing the network. Similarly, an access provider may provide end users 500 with certain devices 20 as such. On the other hand, an access provider may own a specific type of proprietary code 1098 on which its services 1097 may operate. Its services 1097 also operate on common code 1099 . As discussed in more detail below with reference to FIG. 2A , a service provider's services 1097 may be available for specific types of contexts 1180 , or may be limited by those contexts 1180 . In a preferred embodiment, a single organization may act as both a service provider and an access provider.

At least one interface 400 is configured between the platform 100 and the rest of the system 1000 . Access to platform 100 provides interface 400 control. Specifically, interface 400 monitors and provides security for communications between platform 100 and the rest of system 1000 , and converts data transmitted to and from platform 100 , for example. As such, interface 400 is the outer boundary of platform 100 .

FIG. 2A shows yet another preferred embodiment of the system 1000 shown in FIG. 1A in more detail. Referring to both Figures 1A and 2A, services/applications 650 represent services and applications provided by providers 600 within system 1000, as well as values provided to end users 500. Exemplary services/applications 650 shown in FIG. 2 include shopping services, including grocery purchasing services, and publishing and content management services. However, any type of web service/application 650 may be provided by the system 1000 within the scope of the present invention. As previously described with reference to FIG. 2A , end users 500 may employ various devices 550 to send and receive information to and from system 1000 .

In a preferred embodiment, one or more interfaces are provided through which providers 600 and end users 500 can access information and functionality of platform 100, represented as SOAP-like packets with XML payloads using HTTP transfers over TCP/IP seal up. In a preferred embodiment, all interface calls to the platform 100 require trust credentials and authorization. Also, where privacy is involved, encryption may be employed.

Platform 100 executes several services that cannot be identified with specific components. For example, the platform 100 executes the payment service 120 that enables output of data to the end user 500 regardless of the type of device used by the end user 500 . This is accomplished through the payment interface 410 by being tuned to support specific protocols and allowing for specific device physical display geometries and input mechanisms. In this way, for example, end user 500 will be able to receive output from system 1000 adapted to the particular device used by end user 500 (i.e. PC (large device), web-enabled phone (small device), or PDA (medium device)). In a preferred embodiment, the service provider is responsible for providing the appropriate output for each type of device in order to utilize the payment service 120 of the platform 100 .

The dialogue means 130 of the platform 100 ensures continuous user connection and authorization within a single application subscription. Each user 500 using the system 1000 navigates through a disparate system of ownership and operates through a different mechanism, and then having the dialog service 130 in place ensures that the experience for the end user 500 is continuous. The dialog service 130 specifies parameters that are communicated to/from the platform 100 by the external service 650 as end users communicate to each other. These parameters may include the following: Service Identification; End User Identifier (such as a GUID in more detail below); Dialogue Response Data (i.e., information that Platform 100 has indicated that it wishes to return from External Service 650 when the User returns to Platform 100); Response data (ie, information that the external service 650 has indicated that it wants from the platform 100 when the end user returns to the external service 650); tickets related to code lists; timestamps; and feeds calculated based on the above parameter values.

The platform 100 also includes a decryption service 140 in the preferred embodiment. Decryption service 140 allows device-specific decryption of code and other application data, if desired. In other embodiments of the invention, the dialog, payment and decryption functions may be performed by one or more providers 600 rather than by the platform 100 .

In a preferred embodiment, platform 100 includes several distinct components in addition to the session, payment and decryption services performed by platform 100 . Each component stores specific information and has certain functionality. The functionality supported by the components of the platform 100 can be grouped into four main categories, in a preferred embodiment: (1) processing of scanned or other code entry, this includes authenticating codes, devices and users; uploading, retrieval and encryption /decrypt codes; and map codes to services/applications; (2) manage code lists, which includes adding, removing, and editing codes; and copy, intercept, paste, and clean up code lists; (3) supervise codes and related/applications, This includes purchasing and reclaiming codes; and restricting/winning access to codes; and (4) monitoring events and usage, which includes monitoring event mechanisms and access scan/code entry history per user and per device.

Suppliers 600 and end users 500 may access and use components of platform 100 using graphical user interface ("GUI") 200 through hub site 101 maintained by platform 100 on the Internet. For example, the end user GUI 210 is the general interface through which the end user 500 can gain access to information and functionality of the platform 100. In some embodiments, the end user GUI 210 can be customized for a particular provider 600. In a preferred embodiment, end user context component 104, code profile component 108, event/alert component 103, usage component 106, scan cache component 107 and directory component 105 are accessible through end user GUI 210.

The code manager GUI 220 can be used by the provider 600 to create and edit services/applications 650; register and issue private codes; generate and edit lists of codes (e.g. a list of codes and their associated data such as descriptions, used to link codes to services/applications application 650); and assign context to the service, such as site-specific display, display language, and output device channel (e.g., small for mobile phone browsers, medium for PDA browsers, and large for on PC browsers). In a preferred embodiment, code category component 109, directory component 105, and billing component 102 are accessible through code manager GUI 220.

The account manager GUI 230 allows various business relationships with suppliers 600 to be established. In a preferred embodiment, the billing component 102 is accessible through the account manager GUI 230.

The content and function of each component of platform 100 in the preferred embodiment are described below. In other embodiments within the scope of the invention, more or less information and/or functionality may be included in the components described below.

The billing component 102 of the platform 100 facilitates invoicing and payment processing. The event/alert component 103 allows the storage of application and business events to be managed efficiently to ensure the integrity of data storage and business flow. Specifically, this component tracks the behavior of the end user 500 and provides mechanisms to initiate proactive action based on the end user's 500 profile. For example, event/alert component 103 can identify potential fraudulent activity on behalf of end user 500 within system 1000 and intervene proactively. Usage component 106 is used to track usage of system 1000 by end users 500 .

The end user context component 104 manages the communication between the platform 100 and the end user 500 , and the communication between the platform 100 and the supplier 600 . The end user context component 104 acts as a container for current actions and related history, representing conversations between these entities. The information contained in the end user context component 104 includes the following general categories of information: marketing information; outstanding events (e.g., email tracking items); action items (e.g., payments due, certification termination); Feedback that the action of fulfillment has been completed, and other activities initiated by the end user); and activities initiated by the end user 500).

The directory component 105 contains profile information of the end user 500 as well as device information. Device information may include the serial number identification of the device, the fulfillment of the device, the state of the device (activated or not activated), and the identification of an access provider (ie, owner) associated with the device. 3, the profile information contained in the directory component 105 includes information about various types of end users 500 associated with end users 500 non-external identifiers, also referred to herein as globally uniform unique identifiers ("GUIDs") . Each end user has at least one GUID 1055 associated with him or her. Some end users in some embodiments have more than one GUID. In a preferred embodiment, there are four general categories of end user 500 information associated with GUID 1055. One category of information includes public information 1051 that is submitted to the hub site 101 by an end user 500 and is intended to be shared with one or more suppliers 600 without the end user's 500 permission. This public information 1051 may include, for example, the common name of the end users 500, as well as their preferred language, location, and best channel of contact. Public information 1051 may also include confidential summary information that provides references to confidential information items without requiring the confidential items of the disclosed information itself.

Another class of information, private information 1052, associated with GUID 1055 and maintained in directory optimal component 105, is submitted to hub site 101 by end user 500 and is not expected to be shared with any supplier 600 without end user permission shared. Such private information 1052 may include, for example, the first and last names of end users 500, their addresses, phone numbers, and marital status. Yet another type of information is supplier preference information 1053 . In this embodiment, like private information, this information will not be provided to any provider 600 without the permission of the end user 500 . The provider preference information 1053 includes certain preferences of the end user 500 for each service provided by the provider 600 . For example, an end user 500 may indicate in his preferences related to a grocery shopping service that he is allergic to certain types of food, or prefers certain other types of food. In another example, the end user 500 may indicate the same specific area of interest (eg, cooking, sports, apparel, etc.) to the provider. In a preferred embodiment, supplier preference information 1053 for one supplier is shared with other suppliers.

Supplier 600 may access directory component 105 (using code manager 220 as described in more detail above) to perform various functions related to the device and end user 500 . In particular, provider 600 can update, add or remove end user information or device information.

Returning to FIG. 2A , the platform 100 also includes a wallet component 110 . Wallet component 110 stores financial profile information for end user 500 to facilitate purchase timing. The wallet component 110 includes specified profile attributes representing the end user's 500 payment medium, and authorization credentials associated with them. Referring to FIG. 3 , the wallet component 110 contains financial information 1101 associated with a GUID 1055 for each end user 500. Financial information 1101 includes credit card number, payment medium, and billing and shipping addresses. Financial information 1101 may also include an access provider identification associated with a particular end user 500 GUID 1055. In a preferred embodiment, financial information 1101 may only be shared with the provider 600 if authorization information is received from the provider and only if the end user 500 provides permission to share such information.

Returning again to FIG. 2A , platform 100 includes scan cache component 107 . The scan cache component 107 is used to store scans and other code listings entered by the end user 500 . Specifically, this component is a list-based history of the scanning/code entry activity of the end user 500 . The cache component 107 supports the functionality provided to the end user 500 through the end user GUI 210. For example, an end user 500 employing the end user GUI 210 can access the functionality of the scan cache component 107 to manage a list. The end user 500 uploads and stores the scan list to the scan cache component 107 . Scan lists can also be deleted using this component.

Figures 4A through 4C illustrate an example of one way in which an end user 500 would experience using the end user GUI 210 to access the scan cache component 107, in accordance with a preferred embodiment of the present invention. The end user 500 can take his web browser and navigate to the hub 101 and be presented with the end user GUI 210. Referring to FIG. 4A , the user can create folders for codes and uploaded code lists. The name of the folder is indicated in the name area 212 and each scan item is listed in the code description area 214 . The date and time the code was scanned or otherwise entered by voice is indicated in the date/time field 216 . The service area 218 allows the user to select and issue specific applications associated with the items listed in the code description area 214 .

Referring to Figure 4B, the end user 500 may navigate to screen 213 by clicking on the code description area of screen 211 of Figure 4A. Here, the user can provide a description of each scan and specific folder. Each folder created by an end user 500 is associated with a specific end user's GUID 1055. As mentioned earlier, each folder contains a set of codes. In addition, the end user 500 can provide comments on a particular folder in the comments area 2130 using the screen 213 of FIG. 4B . For example, such a note could be the amount of a particular item on the end user's grocery list of food items for a birthday.

End users 500 also use specific services/applications that convert mere lists into useful structures. For example, a user may use a grocery shopping service with a user's preferred grocery store that has a list of items that the user has scanned, and provide the user with an aisle-by-aisle identification of where the user can find each item on his list.

Also, associated with the code set in the preferred embodiment is a binary large object ("BLOB") for the channel service/application 650 deployed by the end user 500. The BLOB includes information that the particular service provider has indicated on behalf of the end user 500, and should be stored with the code set (eg, the amount of item specifically required, the promotion for which the user has taken advantage). In a preferred embodiment, a BLOB is not shared among providers and is only accessible by the specific provider that created it, as opposed to annotation information that is visible and shared among providers.

FIG. 4C shows the way folders 217 associated with a particular GUID 1055 contain groups of codes 218 with BLOBs 2181 and comments 2182 associated with them. This information (i.e. the set of codes associated with each GUID and its associated BLOB 2181 and annotation 2182) is maintained in the scan cache component 107. In this way, the value added to the list by service 650 is applied by the user when forming an annotation (e.g., taking a grocery list and generating a recipe by adding the quantities associated with each grocery item) or series tables with BLOBs, at the end user 500's specific service All interaction processes of suppliers are retained. This value can then be communicated by the end user 500 all the way to others, for example by emailing the recipe to another user. Other users may not have been previously supported on the network, but may become supported when receiving a recipe. In this way, a further advantage is obtained.

Returning again to FIG. 2A and the description of the platform 100 components, the code profile component 108 stores information about the codes and the services associated with those codes. In general, the filtering functionality of the platform 100 uses the code profile component 108 to take a series of codes (entered by the end user 500 via scanning or other input techniques) and translate the codes into actions. In particular, the code profile component 108 uses the code activity operation map from the input by the end user 500, the profile information of the end user 500 (including preferences and any services the end user has subscribed to) from the directory Device profile information of the device used to enter the code (including ownership information and any restrictions on use); and contextual information (i.e. information on the nature of the session of the end user 500 on the network) to return to the end user 500 a link to the specific service/application 650 pointer.

Thus, when a scan/code entry list is uploaded, the code profile component 108 returns a unique alpha-numeric identifier (also referred to herein as a "ticket") associated with the list, and the service to which the ticket should be sent to obtain the service URL. In turn, in response to a ticket provided by the end user 500, the code profiling component 108 returns the available services and a mapping for each code associated with the ticket.

The code class component 109 handles the information, lifecycle, and ownership properties of code, services, and their respective mappings. In particular, the code category component 109 allows linking of code to services/applications 650 . Code category component 109 allows new services to be generated by providing parameters such as URL, title and description. Provider 600 may specify the service context, and specify and narrow down the items displayed to the user based on a particular code, change the size of the returned content, and/or change the starting point of the list of items returned to the user. For example, it may be stipulated that only end users 500 with a specific context are allowed to use certain services (eg, a user entering a code via a cell phone is not allowed to gain access to information or services including graphics). The code category component 109 also allows the creation of operational accounts that specify ownership of services, lists, contexts, and private codes, as discussed with reference to FIG. 1B . Provider 600 also specifies proprietary code using this component.

A service provider may use the code category component 109 to indicate negative options related to services offered by competitors. Figure 2B shows a portion of a database that may be included in code category component 109 in a preferred embodiment. Access Supplier Account Table 1091 allows access to the identification of the supplier. End user table 1092 identifies end users 500 owned by the access provider identified in table 1091 . Using block service table 1093 , the access provider identified in table 1091 can block or prevent presentation of a particular service identified in table 1093 to a user identified in table 1092 . Similarly, using block service provider table 1094, the access provider identified in table 1091 can block or prevent presentation of any service provided by the service provider identified in table 1094 to the user identified in table 1092. The ability of the access provider to build these blocks is also shown in Figure 1B.

The content category component 111 functions as an archiving repository and loading facility for product information. For example, the content category component 111 may include two separate sets of product data: (1) general product titles, descriptions, and categories available through the platform 100; and (2) vendor-specific product data, such as pricing, ownership descriptions, and URLs. . The content category component 111 is used to provide the code category component 109 with product information that is too variable or too large to be stored in the code category component 109 . For example, a search may also be performed in the content category component 111 to obtain information about product manufacturers associated with a particular code or keyword. This component also accepts input of a specific code or keyword and returns a list of specific information related to that code or keyword. In some embodiments, this search can only be performed by employees of the access provider, while in other embodiments, end users 500 may be allowed to access these search capabilities.

Figures 5A and 5B illustrate two examples of the manner in which information may flow among the end user 500, the platform 100, and the supplier 600 shown in Figure 2A. Referring to FIG. 5A , at step 1 , an end user 500 uploads a single scan to the platform 100 . At step 2, the platform 100 looks up the code associated with the scan, and at step 3, sends a response to the end user 500 redirected to the provider 600 with the scan data. At step 4, the end user 500 follows the redirection to the provider 600 . In step 5, the supplier 600 generates content based on the scanned data, and returns the content to the end user 500 in step 6 . Referring to FIG. 5B , the end user 500 uploads the scan in step 1 to the provider 600 . In step 2, the provider 600 requests scanned data from the platform 100, and the platform 100 looks up the scanned data in step 3. In step 4, the platform 100 responds to the supplier 600 with the scanned data. In step 6, the provider 600 returns the content to the end user 500 . Other information flows are well known to those skilled in the art and are within the scope of the present invention.

More specific examples are shown with reference to FIGS. 6A to 6R. Referring to FIG. 6A , an end user 500 has purchased a device from an access provider 600 . In this way, the device and its associated information number are registered within the platform 100 as belonging to the access provider 600, and all scans uploaded by this device will be subject to the access provider rules (e.g., the access provider may prevent the end user 500 from accessing the access to services offered by competitors of suppliers). In this example, access provider 600 also acts as a service provider. The end user 500 registers with the access provider 600, provided that the access provider 600 is responsible for registration and authorization in its community. The end user 500 is assigned a user identification number by the access provider 600 . The end user 500 is then "owned" by the access provider 600 for the purposes of the end user's 500 activities in using the services of the access provider 600 . In a preferred embodiment, end users 500 can download and install software that facilitates interaction with platform 100 . This software has an application identification number registered with the access provider 600 . The access provider 600 is able to control the experience of the end user 500 through written rules in the platform 100 .

Using this device, the end user 500 is able to scan ten times and then upload the code associated with these scans to the platform 100 using his personal computer. In one embodiment, the code is encrypted, and thus the platform 100 must decrypt the code. Upon decryption, the device identification number (from the device) and the application identification number (from the software) 5000 are identified along with the code associated with the scan, as shown with reference to Figure 6B. This allows the platform 100 to identify that the code belongs to the access provider 600 (here company XYZ).

Referring to FIG. 6C , once the codes have been encrypted, the platform 100 can look up what each code represents (in the code category component 109 of FIG. 2A ), as shown in area 5001. In addition, each code has one or more services associated with it and corresponding service-specific information (eg, the URL required to originate the service associated with the code and identify the service within the service provider database). The platform 100 can identify several service providers that provide paper clip-related services.

However, as shown with reference to FIG. 6D, a device identification number and an application identification number 5002 are uploaded along with the code. This allows the platform 100 to determine (by consulting contextual information in the code profile component 108) the access provider rules that the platform 100 is to follow. In this example, the provider's 600 rules dictate that only its services be presented to end users 500, excluding other services intended to provide paper clip-related services. In a particular example, a provider 600 rule may indicate that end users 500 are not presented with services provided by competitors of the provider 600 .

Referring to Figure 6E, the platform 100 selects a code applicable to the service offered by the provider 600 and retrieves service specific information for that provider. In this example, three codes out of ten are applicable. Referring to FIG. 6F , as indicated in code area 5001 , a list of codes and service information for provider 600 is stored in a temporary location within platform 100 . Assign a unique alpha-numeric identifier or ticket number to this location. In this example, the ticket number is 12345.

Referring to FIG. 6G, the platform 100 sends a signal to the end user 500 directing the user's personal computer to open a browser window to a URL indicating the location of the supplier 600 and also provides ticket information. Referring to FIG. 6H , the personal computer of the end user 500 opens a browser to a specific URL at the provider 600 . URL contains ticket number information. Referring to Figure 6I, the provider 600 is responsible for authorization and then requests the end user 500 to enter his username and password. Upon successful login, the provider 600 associates the end user 500 with a ticket number, as shown with reference to Figure 6J.

Referring to Figure 6K, the supplier 600 uses the ticket to request a list of codes previously uploaded by the platform 100 user 500 and associated with the ticket. At this point, the platform 100 will require the provider 600 to provide its username in order to generate a scan history for the end user 500 . Referring to FIG. 6L , a copy of the code list represented by the ticket number is sent by the platform 100 to the supplier 600 . Included in the code list is provider specific service information for the three codes that provider 600 can use. Referring to FIG. 6M , provider 600 converts the code list to a user interface and displays it to user 500 through its web browser, as shown in exemplary interface 5006 . Interface 5006 indicates that three items are available in area 5003 through supplier 600 and also indicates in area 5004 that there are additional items available to user 500 . Referring to FIG. 6N , the platform 100 saves all ten uploaded codes in the scan company cache component 107 . This particular scan history profile is uniquely identified by provider 600 .

Referring to FIG. 60 , assuming the end user 500 wishes to view the seven other available scans, he will click on area 5004 . Referring to FIG. 6P , the browser of the end user 500 is redirected back to the end user GUI 210 of the platform 100, along with information identifying the access provider 600 information and ten user 500 information. Referring to FIG. 6Q , using the access provider 600 information and end user 500 information provided through the URL, the platform 100 is able to retrieve a scan history profile from the scan cache component 107, which is used to present the user 500 with a service according to the identified service. End user GUI 210 for vendor marking. 6R, the platform 100 presents all available services to the end user 500 through the hub site 101 using the end user GUI 210 marked by the provider. In this case, access provider rules will still apply and will prevent user 500 from viewing services offered by provider 600 competitors. The user can then start all presented services.

In the experience of the end user 500 shown with reference to FIGS. 6A to 6R , as shown in FIG. 6M , the end user 500 demonstrates its expressed goal by indicating that it wishes to make a purchase. End users 500 may have various express goals, such as buying, selling, searching, including, retweeting, and the like. For example, FIG. 6S shows an exemplary user interface 6002 on a cellular phone 6001. Shown on interface 6002 are bookmarks identifying services selectable by the user. By selecting a particular bookmark, the end user 500 has indicated his expressed need.

Figure 7 provides an example of a preferred embodiment of a system 7000 that can be used to implement the methods of the present invention. Invocations made by an end user 500 through the end user GUI 210 (such as described with reference to FIG. Each consumer section 711 also includes a firewall 712 . Although this exemplary embodiment depicts three consumer segments 711, any number of consumer segments may be employed, if desired, in accordance with the present invention. System 7000 is thus scalable. As described with reference to FIG. 2A , management segment 720 fulfills calls made by account manager 230 and code manager 220 . Authentication of the end user may also be performed by the authentication server 721 of the management segment 720 . The statements of logging area 730 provide a backup of all information held on platform 100 (as described with reference to FIG. 2A ), and thus should be highly reliable. Internet access to system 7000 can be achieved through Internet connection segment 740 .

Referring to Figures 8A and 8B, there is shown a method for storing and selectively sharing end user information in a system having multiple end users remotely accessing a network of at least one hub site and multiple provider sites . At step 801, a user record corresponding to each end user is stored in a profile database associated with that hub site. Each User Record includes public information, which is submitted to the Hub Site by the End User, and which the End User is expected to share with one or more Suppliers without the End User's permission, and private information, which is submitted to the Hub Site by the End User, And the end user is expected not to share with any provider without the end user's permission, and the non-external identifier associated with the user record that identifies the end user on the network. At step 802, a first request signal including a non-external identifier corresponding to an end user is received. At step 803, in response to the first request signal, public information related to the end user is sent from the hub site to the provider without the end user's permission. At step 804, a second request signal including a non-external identifier corresponding to the end user is received. At step 805, a permission request is sent to the end user at the hub site. At step 806, it is determined whether the end user's permission has been received in response to the permission request. If yes, then at step 807, private information related to the end user is sent from the hub site to the provider. If not, then at step 808, no private information is sent.

In some embodiments, each user record also includes financial information related to the end user. In this embodiment, at step 809, a third request signal is received that includes a non-external identifier corresponding to the end user. At step 810, a second permission request is sent from the hub site to the end user in response to the third request signal. At step 811, it is determined whether an end user's permission has been received in response to the second permission request. If not, then at step 812, no financial information is sent. As shown in FIG. 8B, if a license is received, then at step 813, it is determined whether authentication information has been received from the supplier. If so, at step 814, financial information related to the end user is sent from the hub site to the provider. If not, at step 820 no financial information is sent.

In another embodiment, each user record also includes provider preference information associated with the last one. As shown in FIG. 8A, in these embodiments, at step 815, a fourth request signal is received that includes a non-external identifier corresponding to the end user. At step 816, a third permission request is sent from the hub site to the end user in response to the fourth request signal. At step 817, it is determined whether an end-user license was received in response to the third license request. If not, at step 815, no provider preference information is sent. If so, at step 819, provider preference information related to the end user is sent from the hub site to the provider.

Referring to Figure 9, in a system having multiple end users who have remote access to a network having at least one hub site and multiple provider sites, a location on the network of at least one provider is shown identifying at least one end user to at least one end user Methods. At step 901, code information (eg, a machine-readable code) corresponding to one or more codes is received at a hub site provided (eg, provided for scanning) by an end user. In step 902, in response to the code information, network address information corresponding to the location on the provider network associated with the received code information is retrieved from a profile database associated with the hub site. At step 903, the network address information is used to direct the end user to the relevant location on the provider's network. The profile database includes a user record corresponding to each end user. This user record includes public information, which series of information is submitted by the end user to the hub site, and the end user expects, without the permission of the end user, that information may be shared by one or more suppliers, including private information, which is submitted by the end user to the hub site. hub site, and the end user expects, that information will not be shared with any provider without the end user's permission, and includes a non-external identifier associated with the end user that identifies the end user on the network.

Referring to Figure 10, in a system having multiple end users who have remote access to a network having at least one hub site and multiple provider sites, a location on the network of at least one provider is shown identifying at least one end user to at least one end user And a way to preserve user-commented code information. At step 1001, code information corresponding to one or more codes provided by an end user is received at a hub site. At step 1002, in response to the code information, network address information corresponding to the location on the provider network associated with the received code information is retrieved from a profile database associated with the hub site. At step 1003, the network address information is used to direct the end user to the relevant location on the provider's network. At step 1004, a user-annotated code message from an end user is received at the hub site. At step 1005, user-annotated code information is stored at the hub site.

Referring to Figure 11, a method is shown for sending information representing scanned machine-readable codes between network sites. At step 1101, information related to one or more scans of a machine-readable code by an end user is received at a first site. At step 1102, information related to the scan is stored in a data record at a database associated with the first site having a unique alphanumeric identifier associated therewith. At step 1103, the end user is directed from the first site to the second site with a URL that includes both a symbol identifying the second site's address on the network and a unique URL associated with information stored at the first site. The alphanumeric identifier for the . At step 1104, a request signal from a second site for information stored at the first site is received at the first site. The request signal includes a representation of a unique alphanumeric identifier. At step 1105, the stored information is transmitted from the first site to the second site in response to the request signal.

Referring to Figure 12, there is shown the use of information corresponding to a provider associated with the end user for directing the end user to a network location. In step 1201, a database is provided. The database includes a plurality of records, each associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers. At step 1202, scan information is received at a website. The scan information is associated with one or more scans of a machine-readable code formed using a remote scanning device by an end user associated with one or more different suppliers. At step 1203, in response to the scan information, a record associated with the machine-readable code scanned by the end user is retrieved from the database. At step 1204, at least one network address for each retrieved record is selected based on criteria specified by the provider associated with the end user. In other embodiments, the network address is selected based on the end user's expressed goals. In other embodiments, the network address is selected based on information about the nature of the end user's session on the network. At step 1205, transmission from the network site to at least one selected network address of the end user is initiated.

Claims (33)

1. In a system having multiple end users remotely accessing a network having at least one hub site and multiple supplier sites, a method for storing and selectively sharing end user information comprising: a) In a profile database associated with the hub site, store a user record corresponding to each end user; each user record includes public information that the end user submits to the hub site and that the end user is not expected to need. Shared by one or more suppliers with the consent of the end user, private information that the end user submits to the hub site and that the end user does not expect to be shared by any supplier without the consent of the end user, and related to user records An associated, non-external identifier that identifies an end user on the network; b) responding to the first request signal containing a non-external identifier corresponding to the end user without the permission of the end user to send public information related to the end user from the hub site to the provider; and c) send a permission request from the hub site to the end user in response to a second request signal containing a non-external identifier corresponding to the end user, and send a permission request from the hub site to the provider only if the end user's permission is received in response to the permission request Providers send private information related to end users. 2. In a system having multiple end users remotely accessing a network having at least one hub site and multiple supplier sites, a method for at least one end user to identify at least one supplier location on the network, comprising: receiving code information at the hub site corresponding to one or more codes provided by the end user; Responsive to the code information, retrieving, from a profile database associated with the hub site, network address information corresponding to a location on the provider network associated with the received code information; and Use this network address information to direct the end user to the relevant supplier's location on the network, wherein the profile database includes a user record corresponding to each end user; each user record includes publicly available information that the end user submits to the hub site and that the end user is expected to use without the end user's permission by one or more Provider-shared, private information that an end user submits to a hub site and that an end user does not expect to be shared by any provider without the end user's permission, and a non-external identifier associated with a user record that identifies the of end users. 3. A method for sending information representing scanned machine-readable codes between network sites, including: a) receiving, at a first site, information relating to a scan of one or more machine-readable codes formed by an end user; b) storing information related to the scanning of the machine-readable code in a data record having a unique alphanumeric identifier associated therewith at a database associated with the first site; c) point the end user from the first site to the second site using a URL that includes both a symbol identifying the address of the second site on the network and a unique alphanumeric identifier associated with information stored at the first site; d) receiving at the first site a request signal from a second site for information stored at the first site, wherein the request signal includes a representation of a unique alphanumeric identifier; and e) transmitting the stored information from the first site to the second site in response to the request signal. 4. A method of pointing the end user to a network location using information corresponding to the provider associated with the end user, including: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on criteria specified by the provider associated with the end user; and e) initiating transmission from the network site to at least one selected network address of the end user. 5. The method of claim 1, wherein each user record further includes financial information related to the end user, further comprising: d) in response to a third request signal containing a non-external identifier corresponding to the end user, a second permission request is sent from the hub site to the end user, and only if authentication information is received from the provider, and if in response to the second permission request Financial information related to the end user is sent from the hub site to the supplier only after receiving the end user's permission. 6. The method of claim 1, wherein the one or more codes comprise one or more machine readable codes. 7. A system for sending information representing scanned machine-readable codes between network sites, comprising: a first site at which information relating to scans of one or more machine-readable codes formed by an end user is received; a database associated with the first site that stores information related to the scanning of the machine-readable code in data records having a unique alphanumeric identifier associated therewith; A second site that directs end users from the first site to the second site using a URL that includes both a symbol identifying the address of the second site on the network and a unique alphanumeric number associated with information stored at the first site identifier; wherein a request signal is received at the first site from a second site for information stored at the first site, wherein the request signal includes a representation of a unique alphanumeric identifier; and Wherein the stored information is transmitted from the first site to the second site in response to the request signal. 8. A method of directing an end user to a network location using information corresponding to a provider associated with the end user, including: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on the goals expressed by the end user; and e) initiating transmission from the network site to at least one selected network address of the end user. 9. The method of claim 1, wherein each end user further includes provider preference information associated with the end user, further comprising: d) sending a third permission request from the hub site to the end user in response to a fourth request signal containing a non-external identifier corresponding to the end user, and only when the end user's permission is received in response to the third permission request, from The hub site sends supplier preference information relevant to the end user to the supplier. 10. The method of claim 2, wherein the machine readable code is scanned by an end user. 11. The method of claim 1, wherein only the support provider supporting the end user on the network has the right to permanently suspend the end user's access to the network. 12. A method of directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on information about the nature of the end-user session on the network; and e) initiating transmission from the network site to at least one selected network address of the end user. 13. In a system with multiple end users remotely accessing a network with at least one hub site and multiple supplier sites, identifying a location on at least one supplier network for at least one end user and retaining user note code information A method comprising: receiving code information at the hub site corresponding to one or more codes provided by the end user; Responsive to the code information, retrieving, from a profile database associated with the hub site, network address information corresponding to a location on the network of the provider associated with the received code information; Use this network address information to direct end users to the relevant provider's location on the network; Receive user-annotated code information from end-users at hub sites; The user note code information is stored at the hub site. 14. A system for storing and selectively sharing end user information comprising: A network with at least one hub site and multiple provider sites, with multiple end users accessing the network remotely; a profile database associated with the hub site for storing a user record corresponding to each end user; each user record includes public information that the end user submits to the hub site and that the end user does not expect to need the end user shared by one or more suppliers, private information that an end user submits to a hub site and that an end user does not expect to be shared by any supplier without that end user's permission, and information associated with a user record Non-external identifiers that identify end users on the network; wherein the response includes a first request signal corresponding to a non-external identifier of an end user without the permission of the end user to send the public information related to the end user from the hub site to the provider; and wherein, in response to a second request signal containing a non-external identifier corresponding to the end user, a permission request is sent from the hub site to the end user, and only when permission is received from the end user in response to the permission request, is sent from the hub site to Supplier sends private information related to end user. 15. A system for at least one end user to identify the location of at least one supplier on a network, comprising: a network comprising at least one Hub Site and a plurality of Provider Sites where a plurality of End Users access the network remotely, wherein code information corresponding to one or more codes provided by the end user is received at the hub site; and a profile database associated with the hub site, responsive to the code information, retrieving from the database network address information corresponding to the location on the provider network associated with the received code information; wherein the profile database includes a user record corresponding to each end user, each user record including publicly available information that the end user submits to the hub site and that the end user is expected to use without the end user's permission by one or more Provider-shared, private information that the end user submits to the hub site and that the end user does not expect to be shared by any provider without the end user's permission, and a non-external identifier associated with the user record, identifying the network end users on ; and Wherein the network address information is used to point the end user to the relevant provider's location on the network. 16. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a network site at which scan information is received relating to scans of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various suppliers; wherein, responsive to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on criteria specified by a provider associated with the end user; And initiate transmission from the network site to at least one selected network address of the end user. 17. A system for at least one end user to identify the location of at least one supplier and for retaining user note code information: a network comprising at least one hub site and a plurality of provider sites, wherein a plurality of end users access the network remotely, wherein code information corresponding to one or more codes provided by the end user is received at the hub site; and a profile database associated with the hub site from which, responsive to the code information, network address information corresponding to the location on the provider network associated with the received code information is retrieved, where the network address information is used to point the end user to a location on the relevant provider's network, where user comment code information is received from end users at the hub site, and Wherein said user note code information is stored at the hub site. 18. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a network site at which scan information is received in connection with scans of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various suppliers; wherein, in response to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on the end user's expressed goals; Transmission of at least one selected network address by the end user. 19. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a web site at which scan information is received in connection with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various suppliers; wherein, in response to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on information about the nature of the end user session; Transmission to at least one selected network address of the end user. 20. In a system having a plurality of end users remotely accessing a network having at least one hub site and a plurality of provider sites, a method for at least one end user to identify at least one provider location on the network, comprising: receiving code information at the hub site corresponding to one or more codes provided by the end user; Responsive to the code information, retrieving, from a profile database associated with the hub site, network address information corresponding to a location on the provider network associated with the received code information; and Use this network address information to direct the end user to the relevant supplier's location on the network, wherein the profile database includes a user record corresponding to each end user; each user record includes publicly available information that the end user submits to the hub site and that the end user is expected to use without the end user's permission by one or more Provider-shared, private information that an end user submits to a hub site and that an end user does not expect to be shared by any provider without the end user's permission, and a non-external identifier associated with a user record that identifies the of end users. 21. The method of claim 20, wherein the one or more codes comprise one or more machine readable codes. 22. The method of claim 21, wherein the machine readable code is scanned by an end user. 23. In a system with multiple end users with remote access to the network, the network has at least one hub site and multiple supplier sites, identifies a location on at least one supplier network for at least one end user and maintains user note code information A method of , including: receiving code information at the hub site corresponding to one or more codes provided by the end user; Responsive to the code information, retrieving, from a profile database associated with the hub site, network address information corresponding to a location on the network of the provider associated with the received code information; Use this network address information to direct the end user to a location on the relevant provider's network; Receive user comment code information from end users at hub sites; The user note code information is stored at the hub site. 24. A system for at least one end user to identify the location of at least one supplier on a network, comprising: a network comprising at least one Hub Site and a plurality of Provider Sites where a plurality of End Users access the network remotely, wherein code information corresponding to one or more codes provided by the end user is received at the hub site; and a profile database associated with the hub site, responsive to the code information, retrieving from the database network address information corresponding to the location on the provider network associated with the received code information; wherein the profile database includes a user record corresponding to each end user; each user record includes publicly available information that the end user submits to the hub site and that the end user is expected to use without the end user's permission by one or more Provider-shared, private information that the end user submits to the hub site and that the end user does not expect to be shared by any provider without the end user's permission, and a non-external identifier associated with the user record, identifying the network end users on ; and Wherein the network address information is used to point the end user to the relevant provider's location on the network. 25. A system that identifies the location of at least one supplier for at least one end user and maintains user note code information: a network comprising at least one Hub Site and a plurality of Provider Sites where a plurality of End Users access the network remotely, wherein code information corresponding to one or more codes provided by the end user is received at the hub site; and a profile database associated with the hub site, responsive to the code information, from which to retrieve network address information corresponding to the location on the network of the provider associated with the received code information; where the network address information is used to point the end user to the location of the relevant provider on the network; where receiving user comment code information from end users at the hub site; Wherein the user note code information is stored at the hub site. 26. A method for sending information representing scanned machine-readable codes between network sites, comprising: a) receiving, at a first site, information relating to a scan of one or more machine-readable codes formed by an end user; b) storing information related to the scanning of the machine-readable code in a data record having a unique alphanumeric identifier associated therewith at a database associated with the first site; c) point the end user from the first site to the second site using a URL that includes both a symbol identifying the address of the second site on the network and a unique alphanumeric identifier associated with information stored at the first site; d) receiving at the first site a request signal from a second site for information stored at the first site, wherein the request signal includes a representation of a unique alphanumeric identifier; and e) transmitting the stored information from the first site to the second site in response to the request signal. 27. A system for sending information representing scanned machine-readable codes between network sites, comprising: a first site at which information relating to scans of one or more machine-readable codes formed by an end user is received; a database associated with the first site, the database storing information related to the scanning of the machine-readable code in data records having a unique alphanumeric identifier associated therewith; A second site to which end users are directed from a first site using a URL that contains both a symbol identifying the address of the second site on the network and a unique alphanumeric identifier associated with information stored at the first site ; wherein a request signal is received at the first site from a second site for information stored at the first site, wherein the request signal includes a representation of a unique alphanumeric identifier; and Wherein the information stored in response to the request signal is sent from the first station to the second station. 28. A method of directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on criteria specified by the provider associated with the end user; and e) initiating transmission from the network site to at least one selected network address of the end user. 29. A method of directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on the goals expressed by the end user; and e) initiating transmission from the network site to at least one selected network address of the end user. 30. A method of directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a) Provide a database with a plurality of records, each of which is associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, which are associated with different suppliers ; b) receiving at a network site scan information associated with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the different providers; c) in response to the scan information, retrieve from the database a record associated with the machine readable code scanned by the end user; d) select at least one network address for each retrieved record based on information about the nature of the end user's conversations on the network; and e) initiating transmission from the network site to at least one selected network address of the end user. 31. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a network site at which scan information is received relating to scans of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various suppliers; wherein, responsive to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on criteria specified by a provider associated with the end user; And initiate transmission from the network site to at least one selected network address of the end user. 32. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a network site at which scan information is received in connection with scans of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various suppliers; wherein, in response to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on the end user's expressed goals; Transmission of at least one selected network address by the end user. 33. A system for directing an end user to a network location using information corresponding to a provider associated with the end user, comprising: a database with a plurality of records, each record associated with a different machine readable code, wherein one or more records have associated therewith a plurality of different network addresses, the different network addresses being associated with different suppliers; a web site at which scan information is received in connection with a scan of one or more machine-readable codes formed by an end user using a remote scanning device, the end user being associated with one of the various providers; wherein, in response to the scan information, retrieving records from the database associated with the machine-readable codes scanned by the end user; selecting at least one network address for each retrieved record based on information about the nature of the end user session; Transmission to at least one selected network address of the end user.

Images