KR20030079927A - Method and system for connecting end users with network location - Google Patents

Abstract

The present invention relates to a plurality of end users remotely accessing a network comprising a hub site and a plurality of provider sites. Information associated with the end user is associated with a non-external identification symbol. Public end user information is shared with the provider without the end user's permission. Personal end user information is shared with the provider only upon permission from the end user. The hub site receives the code from the end user and, based on the code, instructs the end user where it is on the network. The specific location that the end user is facing is based on the category specified by the service provider, the specified purpose of the end user, or the specific information of the end user's session on the network.

Description

System and method for connecting end users to network locations {METHOD AND SYSTEM FOR CONNECTING END USERS WITH NETWORK LOCATION}

Bar-code scanning techniques have been used quite often. These bar codes are found in most items encountered by consumers every day, from grocery to driver's licenses. Other forms of code (e.g., personal code) and methods of capturing the code continue to be developed. Bar codes and other codes help to quickly and easily store the identification, tracking and inventory of items as well as the storage of data associated with the items. As bar-code becomes part of the consumer's usual and familiar experience, it uses Web services and applications. Various forms of web services and applications continue to grow in number and become popular.

Using identification methods that converge these two distinctly different technologies for producing products that provide mobility, simplicity, accuracy, convenience, and efficiency for web applications and services, manufacturers can reduce costs (and do things that have been done in the past) Replaces bar-coding technology), increases revenue (provides bar codeable advertisements for consumers to know about products, prices, store locations, etc.), increases productivity (automates sales tasks such as ordering products) To improve consumer loyalty (provide bar code-related value-added services to consumers).

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

1A shows a preferred embodiment of a system for practicing the method of the present invention,

1B illustrates a preferred embodiment of some operating architecture of the present invention,

2A shows a preferred embodiment of a system for practicing the method of the present invention,

2B shows a paragraph code listing database used in accordance with a preferred embodiment of the present invention,

3 illustrates a structure for end user profile information associated with an end user identifier used in accordance with a preferred embodiment of the present invention;

4A and 4B illustrate a preferred user interface employed by an end user in accordance with a preferred embodiment of the present invention,

4C shows a structure for maintaining related information and an end user code list folder according to a preferred embodiment of the present invention;

5A and 5B show two embodiments of information flow between components of the preferred embodiment of the system of the present invention,

6A-6R show examples in which the method of the present invention is carried out in accordance with a preferred embodiment of the present invention,

6S shows an example of a user interface on a cellular phone that can be used with an access service in accordance with a preferred embodiment of the present invention,

7 shows a preferred embodiment of a system that can be used to practice the method of the present invention,

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

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

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

11 is a flow diagram illustrating a method for transferring information indicative of a scan of machine readable code between sites in accordance with a preferred embodiment of the present invention;

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

The present invention is directed to providing a method and system for the convergence of bar-codes and other coding techniques, web-based applications and services, thereby satisfying the needs of the prior art.

In particular, the present invention relates to methods and systems for selectively storing and sharing end user information. The plurality of end users may remotely access a network having at least one hub site and a plurality of provider sites. The user record corresponding to each end user is stored in the profile database associated with the hub site. Each user record may include public information that the end user expects to share with one or more providers without the end user's permission, presented to the hub site by the end user; Secret information that the end user expects not shared with any provider without the end user's permission, presented to the hub site by the end user; And a non-externally identifying symbol associated with the user record identifying the end user on the network. In response to the first request signal containing the non-external identification symbol, public information associated with the end user is transmitted from the hub site to the provider without the end user's permission. In response to the second request signal containing the non-external identification symbol, a grant request is sent from the hub site to the end user. Secret information associated with the end user is sent from the hub site to the provider only when the end user's permission is received in response to the authorization request.

The invention also relates to a method and system for an end user to identify a provider's location on a network having at least one hub site and a plurality of provider sites and remotely accessed by the end user. Code information corresponding to one or more codes provided by the end user is received at the hub site. In response to the code information, network address information associated with the received code information and corresponding to the provider's location on the network is retrieved from the profile database associated with the hub site. The network address information is used to indicate to the end user the location of the relevant provider on the network. The profile database includes a user record corresponding to each end user. Each user record may include public information that the end user expects to share with one or more providers without the end user's permission, presented to the hub site by the end user; Secret information that the end user expects not shared with any provider without the end user's permission, presented to the hub site by the end user; And a non-external identification symbol associated with the user record identifying the end user on the network.

The present invention also relates to a system and method for transmitting information indicative of machine readable codes scanned between network sites. Information related to the scan of the one or more machine readable codes formed by the end user is received at the first site. Information relating to the scan of the machine readable code is stored in a database associated with the first site in the data record, and includes a unique alphanumeric identifier on the data record. The end user travels from the first site to the second site by a URL comprising two codes identifying the address of the second site on the network and a unique alphanumeric identifier associated with the 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 includes an indication 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 invention also relates to a method and system for an end user to identify a provider's location on the network and to preserve user-annotated code information. The network has one hub site and a plurality of provider sites and is accessed remotely by a plurality of end users. Code information corresponding to 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 provider's network associated with the received code information is retrieved from the profile database associated with the hub site. The network address information is used to indicate to the end user the location on the network of the associated provider. The user addition code information is received from the end user of the hub site. The user addition code information is stored in the hub site.

Ultimately, the present invention relates to a system and method for instructing an end user of a network location using information corresponding to a provider associated with the end user. A database with a plurality of records is provided, each of which is associated with a different machine readable code. One or more records have a plurality of different network addresses associated with them, and these different network addresses are associated with different providers. Scan information associated with the scan of one or more machine readable codes formed by an end user having a remote scan device is received at a network site, and the end user is associated with one of the different providers. In response to the scan information, records associated with machine readable codes scanned by the end user are retrieved from the database. At least one network address is selected for each of the retrieved records. This selection will be based on criteria specified by the provider associated with the end user, ie the explicit purpose of the end user, or the unique information of the end user's session on the network. The selected network address begins to be sent from the network site to the end user.

The foregoing detailed description and the detailed examples set forth below are merely examples of the invention and are intended to provide further explanation of the invention.

BRIEF DESCRIPTION OF DRAWINGS To illustrate the present invention, the accompanying drawings are shown and are incorporated in and constitute a part of this specification, and together with the accompanying description, they explain one or more embodiments of the invention.

Hereinafter, the present invention will be described in detail with reference to preferred embodiments shown in the accompanying drawings. The same reference numerals are used for the same parts throughout the drawings.

1A illustrates a preferred embodiment of a system 1000 that implements the method of the present invention. System 1000 includes a plurality of end users 500, each of which has a device capable of entering or scanning a code (ie, a number) associated with a specified purpose of end user 500. The system 1000 also includes a platform 100 and a plurality of providers 600. The platform 100 includes various components (detailed in greater detail in FIG. 2A) that facilitate interoperability between the service provided by the provider 600 and the end user 500 (and its associated devices). The platform 100 is a launching service that supports the end user 500 in accomplishing a wide range of functions, identification code information, user environment, and specified purposes in addition to basic functions such as switches as described in detail herein. application information needed for services). The platform 100 includes a hub site 101 that can be accessed via the internet 50, thereby allowing the end user 500 and the provider 600 to interact with the platform 100.

End user 500 may use a variety of different types of devices or acquisition techniques to obtain code and communicate with platform 100 or provider 600 with the code. For example, the end user 500 may connect to the platform 100 by phone 5, enter codes by dialing, and pass codes to the handset. This input is sent to the Internet via the voice gateway 2005 and from the platform 100 or provider 600 to the voice response unit. In addition, the end user 500 may use a personal digital assistant (PDA) 10 to transmit a code to the Internet 50 via the wireless application protocol gateway 2010, thereby providing a platform 100 or a provider 600. Can be sent to. Optionally, the end user 500 may use a portable wireless scanner, or a scanner confined to the end user client 15 to scan a personal code or barcode (e.g., public code including EAN, UPC and JAN). This code may then be transmitted over the Internet 50 by the end user 500 using the end user client 15 and uploaded to the platform 100. Means for acquiring and transmitting other code information to the platform 100 or provider 600 are well known in the art and are included in the present invention. The particular device used by the end user 500 specifies the capabilities of the system 1000 that are available. As will be described in detail below, the device and its identifier adjust features for the available functions and access privileges in system 1000.

The end user 500, the platform 100, and the provider 600 may establish connections with each other through various forms of different links to form a network. For example, the end user 500 is connected to the platform 100 via the link 51 and the link 52 directly through the Internet 50, or the link 51, the link via the provider 600. It may be connected to platform 100 via 53 and link 54. In other embodiments, an optional structure of the connection between the end user 500, the platform 100, and the provider 600 is also possible, which is obvious to those skilled in the art and is included in the present invention. In some embodiments, one or more links between these various entities may use radio.

Provider 600, including a service provider and an access provider, hosts a provider site 601 accessible through the Internet 50. The provider 600 is a component that can earn income by manufacturing or selling possible items, materials or products that they deem valuable. The provider 600 provides an application / service that accepts the code as input and can identify the code that operates with their application / service. The provider 600 is responsible for registering and authenticating their shares / applications / services.

The operational relationship between the access provider and the service provider is described with reference to FIG. 1B. The access provider may set up an operational account 1195 in the platform 100 (by using the code listing component 109 shown with reference to FIG. 2A). In a similar manner, the service provider may also set up the computational account 1196 within the platform 100. Each end user 500 residing on a network in system 1000 is supported by at least one access provider. Each access provider “owns” each end user 500 by having exclusive rights to permanently suspend access of the end user 500 that the access provider supports to the network. In a similar manner, the access provider may own the end user 500 and any other device 20. In contrast, a service provider owns a particular form of personal code 1098 in which its service 1097 is computed. The service 1097 also computes with public code 1099. The service provider's service 1097 may be allowed for or limited by a particular type of context 1180, as described in detail in FIG. 2A. In a preferred embodiment, the single structure acts as both a service provider and an access provider.

At least one interface 400 is placed between platform 100 and the rest of system 1000. Access to the platform 100 is coordinated through the interface 400. In particular, for example, interface 400 converts data transmitted from and to platform 100 as well as providing communication security between the rest of system 1000 and platform 100 and Monitor. Thus, interface 400 becomes an outer boundary of platform 100.

2A illustrates in more detail the preferred embodiment of the system 1000 shown in FIG. 1A. 1A and 2A, service / application 650 represents the services and applications provided within system 1000 by provider 600 and provides value to end user 500. Examples of services / applications 650 shown in FIG. 2A include shopping services, publishing and item management services, including grocery shopping services. However, other forms of web services / applications 650 may also be provided through system 1000 without departing from the scope of the present invention. As described above with reference to FIG. 2A, the end user 500 may employ various devices 550 that receive information from and transmit information to the system 1000.

One or more interfaces 400 are represented by envelopes similar to SOAP with XML payload, using HTTP transport of TCP / IP in the present preferred embodiment, wherein the interface 400 Is provided by the provider 600 and the end user 500 accessing the functionality and information of the platform 100. In a preferred embodiment, all interface calls to the platform 100 require credentials and authentication. It is also encrypted in extremely personal cases.

Platform 100 executes a number of services that are not associated with any particular component. For example, platform 100 executes a rendering service 120, which services 120 end user 500 regardless of the class used by end user 500. Enable data output. This is possible through the rendering interface 410, by making adjustments to support a particular protocol, and also allowing the input structure and physical display structure of a particular device. Thus, for example, end user 500 is a system suitable for a particular device (i.e., PC (large device), web-enabled phone (small device), or PDA (medium device)) used by end user 500. May receive an output from 1000. In a preferred embodiment, the service provider is responsible for supporting the appropriate output for each class of device in order to use the rendering service 120 of the platform 100.

The session service 130 of the platform 100 ensures continuous user connectivity and authentication within a single authorized application. The end user 500 using the system 1000 travels through other systems owned and operated by different organizations, so the session service 130 is provided to ensure that the end user 500's experience is continuous. Session service 130 defines parameters that are passed from external service 650 to platform 100 or from platform 100 to external service 650 as end user 500 moves from one side to the other. . These parameters include service identification; End user identifier (eg, GUID, which will be described in detail below); Session echo data (ie, information indicating that when the user returns to platform 100, the external service 650 wants to return from platform 100); External echo data (ie, information indicating that the service 650 wants to return from the platform 100 when the end user returns to the external service 650); A ticket associated with the code listing; Time stamp; And a digest calculated based on the value of the aforementioned parameters.

In addition, in a preferred embodiment, platform 100 includes a decryption service 140. Decryption service 140 allows device-specific decryption code and other application data, if necessary. In other embodiments of the invention, the session, rendering, and decryption functions may be implemented by one or more providers 600 rather than by platform 100.

In addition to the session, rendering, and decryption services executed by platform 100, platform 100 is comprised of a number of different components, in this preferred embodiment. Each component stores specific information and has a specific function. The functions supported by the components of the platform 100 are in this preferred embodiment four main categories: (1) code entry or scanning, including code, device and user authentication; Uploading, retrieval and code encryption / decryption steps; And code mapping to a service / application; (2) code list management steps, including adding, removing, and editing code; And copying, cutting, pasting, and erasing the code list; (3) managing the code and related services / applications, including code retrieval and purchase; Limiting / achieving access to the code; And (4) monitoring events and usage, which includes accessing scan / code entry details for each user and each device and monitoring the event structure.

The provider 600 and the end user 500 use the graphical user interface ("GUIs") 200 to provide the components of the platform 100 via the hub site 101 (which is maintained on the Internet by the platform 100). Use and access. For example, the end user GUI 210 is a generic interface through which the end user 500 passes to access the functionality and information of the platform 500. In some embodiments, the end user GUI 210 is custom made for a particular provider 600. In a preferred embodiment, the end user context component 104, code profile component 108, event / alarm component 103, utilization component 106, scan cache component 107 and directory component 105 are end user GUIs. Can be accessed via 210.

Code manager GUI 220 configures and edits service / application 650; Register and issue a personal code; Create and edit code lists (eg, code lists and their associated data used to link codes for specific URLs of service / application 650 as described); And context 600 (e.g., small cell phone browsers, medium PDA browsers, and large PC browsers) for services such as background-specific display, display language, and output device channels. In a preferred embodiment, code listing component 109, directory component 105, and billing component 102 are accessed by code manager GUI 220.

The account manager GUI 230 allows the provider 600 to establish various business relationships. In the preferred embodiment, the billing component 102 is accessed through the account manager GUI 230.

The following describes the functions and items of each component of platform 100 in a preferred embodiment of the present invention. Additional or reduced information and / or functionality may be included in the components described below in other embodiments without departing from the scope of the present invention.

Billing component 102 of platform 100 facilitates the invoice and payment process. The event / alarm component 103 enables the storage of business events and applications that require active management to ensure business flow and data storage retention. In particular, these components track the end user 500 behavior and provide a structure for initiating innovative behavior based on the profile of the end user 500. For example, event / alarm component 103 is innovatively intervened to identify potential misconduct on behalf of end user 500 within system 1000. The utilization component 106 is for tracking system 1000 usage by the end user 500.

The end user context component 104 manages communication between the platform 100 and the provider 600 as well as communication between the platform 100 and the end user 500. The end user context component 104 acts as a container for current activity and related details that represent between dialogues and between these entities. Information included in the end user context component 104 may include the following general categories of information; That is, marketing information; Prominent disclosures (eg itemized emails); An item of activity (eg, due date, expiry of certificate); An activity log (including feedback to end users 500 activities completed by other people about the end user and completed customer order processing activities); And activities subscribed by end user 500.

Directory component 105 includes device information as well as profile information of end user 500. The device information includes the serial number identification of the device, device type, device status (active or inactive), and identification of the access provider (ie, owner) associated with the device. Referring to FIG. 3, the profile information included in the directory component 105 may include a non-external identification symbol of the end user 500, which may also be referred to herein as a global universally unique identifier (GUID). And end user 500 information in various forms associated therewith. Each end user 500 has at least one GUID 1055 associated with them. Some end users have one or more GUIDs, in other embodiments. In this preferred embodiment, there is general information of four categories of end user 500 associated with GUID 1055. Public information 1051 that the end user also expects that the information in that category will be shared with one or more providers 600 without the end user 500's permission presented by the end user 500 to the hub site 101. ). For example, this public information 1051 includes the common name of the end user 500 as well as their preferred language, background, and preferred connection path. Public information 1051 also includes confidential summary information that provides a reference to a confidential item without revealing the confidential item of information on its own.

Other categories of information related to the GUID 1055 while retained in the directory component 105 will not be shared with any provider 600 without the end user's permission, which the end user 500 has presented to the hub site 101. The secret information 1052 is also expected by the user. For example, the secret information 1052 includes the first and last name, address, telephone number, and marital status of the end user 500. Another category of information is provider preference information 1053. In this preferred embodiment, this information, like the secret information 1052, will not be provided to any provider 600 without the permission of the end user 500. Provider preference information 1053 includes the preferences of end user 500 for each service 650 provided by provider 600. For example, the end user 500 may indicate their preference that some type of food is preferred or that some type of food is allergic with respect to grocery services. As another example, the end user 500 presents the provider with a particular area of interest (eg, food, sports, exercise, etc.). In this preferred embodiment provider preference information 1053 of one provider is not shared with another provider.

The provider 600 accesses the directory component 105 to perform various functions associated with the device and the end user 500 (which is possible by using the code manager 220 described above). In particular, the provider 600 may upload, add or remove end user information or device information.

Again, returning to FIG. 2A, platform 100 also includes a wallet component 110. The wallet component 110 stores financial profile information of the end user 500 to facilitate purchase opportunities. The wallet component 110 includes, along with its associated certificate, a specific profile attachment representing the means of payment of the end user 500. Referring to FIG. 3, wallet component 110 includes financial information 1101 associated with GUID 1055 associated with each end user 500. Financial information 1101 includes a credit card number, payment method, and billing and delivery address. Financial information 1101 also includes an access provider identification, which is associated with a particular end user 500 GUID 1055. In this preferred embodiment, the financial information 1101 is shared with the provider 600 only when receiving authentication information from the provider and when the end user 500 provides permission to share the information.

Again, in FIG. 2A, platform 100 includes a scan cache component 107. The scan cache component 107 is used to store the scan list and other code entered by the end user 500. In particular, this component is a breakdown of the end user 500's list of scanning / code entry activities. The scan cache component 107 supports the functionality provided to the end user 500 via the end user GUI 210. For example, end user 500 employing end user GUI 210 accesses the functionality of scan cache component 107 to adjust the scan list. End user 500 uploads and stores the scan list to scan cache component 107. In addition, the scan list is removed using these components.

4A-4C illustrate an example of one feature of the end user 500 experience employing 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 employs his web browser and is presented with the end user GUI 210 via the hub site 101. Referring to Figure 4A, the user can set the uploaded code list and the folder for the code. The name of the folder appears in the name area 212 and each scan entry is listed in the code description area 214. The date and time for the scanned code or the rest of the input appear in the date / time area 216. Service area 218 allows a user to select and launch a particular application associated with an item listed in code description area 214.

Referring to FIG. 4B, the end user 500 enters the screen 213 by clicking on the code description area 214 of the screen 211 of FIG. 4A. Here, the user provides a description of each scan and a specific folder. Each folder set by the end user 500 is associated with a GUID 1055 of that particular end user. As mentioned above, each folder contains a code group. End user 500 also provides an addition to a particular folder using screen 213 of FIG. 4B in addition area 2130. For example, the addition may be a quantity for a particular item on the food item of the grocery item scanned by the end user. Another example of user addition may be a list of items desired for the end user's birthday.

The end user 500 also employs specific services / applications that transform simple items into useful structures. For example, a user may take a list of items scanned by the user along with their favorite grocery store and provide the user with a passage identification through the passage through which the user can find each item on the list. Adopt sundries shopping service.

Also, in the preferred embodiment, the relevant code group is a binary large object (“BLOB”) for a particular service / application 650 adopted by the end user 500. The BLOB includes information that should be stored by the particular service provider on behalf of the end user 500 and stored with the group code (e.g., the quantity that the user can benefit from a particular predetermined item, promotional product). In a preferred embodiment, in contrast to the user addition information shared between providers and easily viewable, the BLOB is not shared between providers and can only be accessed by the specific provider that established it.

In FIG. 4C, the manner in which folders 217 associated with a particular GUID 1055 include group codes 218 is illustrated, which includes both the BLOB 2181 and user additions 2182 associated with them. This information (ie, group code associated with each GUID, and its associated BLOB 2181 and user additions 2182) is stored in the scan cache component 107. Thus, by listing user additions, the value added by the user (eg, creating a recipe and taking a grocery list by adding quantities associated with each grocery item), or listing the service 650 with a BLOB The value added by the user by applying to is preserved across all interactions for that end user 500 for a particular service provider. This value can then be transferred to another person by the end user 500, for example, by emailing the recipe to another user. Another user may receive the recipe even if it was not previously supported on the network. Thus, another commercial benefit can be obtained.

Returning to Figure 2A and the description of the components of the platform 100, the code profile component 108 stores information about the code and services associated with the code. Typically, the filtering function of the platform 100 takes continuous code (entered by the end user 500 via scanning or other input technology) and uses the code profile component 108 to make the code active. . In particular, the code profile component 108 is a profile of the end user 500 (including the code entered by the end user 500, the services and preferences signed by the end user 500 from the directory component 105). Information; Device profile information of the device used to input code (including usage and ownership information) from the directory component 105; And active operation mapping from contextual information (ie, specific information of the session of the end user 500 on the network) for returning the end user 500 pointer to the particular service / application 650.

Thus, in uploading a list for scan / code input, the code profile component 108 is also referred to as a unique alphanumeric identifier (also referred to herein as a "ticket") for the URL service and list for the ticket that must be sent in order to obtain the service. (As mentioned). Furthermore, in response to the ticket supplied by the end user 500, the code profile component 108 submits a mapping and possible service for each code associated with the ticket.

The code listing component 109 handles information about code, life rhythms, ownership characteristics, services and their respective mappings. In particular, code listing component 109 allows linking of code to service / application 650. Code listing component 109 allows the creation of a new service by providing parameters such as URL, name and description. The provider 600 specifies the service context, changes the size of the returned item, and also changes the starting point of the list for the item returned to the user, similarly to defining and specifying the item displayed to the user based on the particular code. For example, only the end user 500 with a specific context is designated to use a particular service (eg, a user whose code entry via a mobile phone does not have access to services or information containing graphics). In addition, the code listing component 109 allows creation of a compute account, which specifies ownership, listing, context, and private code of the service, as described in connection with FIG. 1B. In addition, the provider 600 uses these components to specify a personal code.

The access provider uses code listing component 109 to represent negative choices when they are associated with a service provided by a competitor. In the preferred embodiment, FIG. 2B illustrates a portion of a database that may be included in code listing component 109. The access provider account table 1091 allows identification of the access provider. End user table 1092 identifies end user 500 owned by the access provider identified in table 1091. By using the block service table 1093, the access provider identified in the table 1091 can prevent or prevent the user identified in the table 1092 from being provided with the particular service identified in the table 1093. In a similar manner, by using the block service provider table 1094, the access provider identified in table 1091 may be combined with any service provided by the service provider identified in table 1094 by the user identified in table 1092. It can be prevented or prevented from being provided. In addition, the ability of an access provider to set up such a block is illustrated in FIG. 1B.

The content list component 111 functions as a storage and loading device for product information. For example, the content listing component 111 may comprise two separate sets of product data: (1) a generic product name, description and category that may be used by the platform 100; And (2) specific product data of the supplier, such as price, ownership description, and URL. The content list component 111 is used to supply product information to the code list component 109 that is highly volatile or large and cannot be stored in the code list component 109. Further, for example, a search may be performed in the content listing component 111 to obtain information relating to the manufacturer of the product associated with a particular code or keyword. In addition, this component accepts input of a specific code or keyword to retrieve a specific list of information associated with the code or keyword. In some embodiments, such searches may be performed only by employees of the access provider, but in other embodiments, end user 500 may be allowed access to such search capabilities.

5A and 5B are two examples of how information flows between end user 500, platform 100, and provider 600 in FIG. 2A. Referring to FIG. 5A, in step (1), the end user 500 uploads a single scan to the platform 100. In step (2), the platform 100 finds the code associated with the scan, and in step (3), sends a direction response to the provider 600 along with the scan data. In step (4), the end user 500 comes to the provider 600 along with the direction designation. In step (5), the provider 600 generates the content based on the scanned data, and in step (6), the content is returned to the end user 500. Referring to FIG. 5B, the end user 500 uploads a scan to the provider 600 in step (1). In step (2), the provider 600 requests scan data from the platform 100, and in step (3), retrieves the scanned data. In step (4), the platform 100 responds to the scan data to the provider 600. In step (5), the provider 600 returns the content to the end user 500. Other information will be known to those skilled in the art without departing from the scope of the present invention.

A more detailed example is described with reference to FIGS. 6A-6R. With reference to FIG. 6A, end user 500 purchases a device from access provider 600. Thus, all scans uploaded by such devices and appendages associated with the access provider 600 are subject to access provider provisions, such that the device and its associated identification number are registered in the platform 100 (eg, the access provider is an end-user). User 500 may be prevented from accessing a service provided by a competitor of an access provider). Also in this example, the access provider 600 functions as a service provider. The end user 500 is registered with the access provider 600 because the access provider 600 is responsible for authentication and registration at that shared group. End user 500 is assigned a user identification number by access provider 600. The end user 500 is then "owned" by the access provider 600 for the purpose of activity of the end user 500 by using the service of the access provider 600. In this preferred embodiment, the end user 500 downloads and installs software to help interact with the platform 100. This software has an application identification number registered with the access provider 600. The access provider 600 may adjust the user experience of the end user 500 by writing the rules on the platform 100 to storage.

By using the device, the end user 500 scans ten items and then uploads the code associated with the scan to the platform 100 using a personal computer. In one embodiment, because the code is an encryptor, platform 100 must encrypt the code. In encryption, the device identification number (from the device) and the application identification number 5000 (from the software) are identified together with the code associated with the scan, as shown with reference to FIG. 6B. This allows identifying the code as an accessory associated with access provider 600 (here XYZ company).

Referring to FIG. 6C, once the code is encrypted, platform 100 may find out what each code represents (in the code listing component of FIG. 2A), as shown in region 5001. In addition, each code corresponds to service specific information and has one or more services associated therewith (e.g., a URL required to identify the same in the service provider's database and launch the service associated with that code). In this example, one UPC code was found in a box of paperclips. The platform 100 identifies a plurality of service providers that provide services related to paperclips.

However, as shown with reference to FIG. 6D, the device identification number and application identification number 5002 are uploaded with the code. This allows the platform 100 to determine (by referring to the contextual information in the code profile component 108) the access provider rules that it conforms to. In this example, the provider 600 provision refers to the end user 500 being presented only with its service, excluding other services that wish to provide a service associated with the paperclip. In a particular example, provider 600 provisions may refer to that the end user 500 does not represent any service provided by a competitor of provider 600.

Referring to FIG. 6E, the platform 100 selects a code applicable to the service provided by the provider 600 and retrieves service specific information associated with the provider. In this example, only three of the ten codes are applicable in this manner. Referring to FIG. 6F, as shown in code region 5001, service information and code listings associated with provider 600 are stored in a temporary location within platform 100. This location is assigned a unique alphanumeric identifier or ticket number. In this example, the ticket number is 12345.

Referring to FIG. 6G, the platform 100 signals an end user 500 instructing the user's personal computer to open a browser window with a URL, the URL indicating the location of the provider 600 and providing ticket information. to provide. Referring to FIG. 6H, the personal computer of the end user 500 opens the browser to the specific URL from the provider 600. The URL includes ticket number information. Referring to FIG. 6I, the provider 600 is responsible for authentication and requires the end user 500 to enter their username and password. As shown with reference to FIG. 6J, upon successful login, provider 600 associates the end user 500 with a ticket number.

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

With reference to FIG. 6O, the end user 500 will click on area 5004 hoping to investigate seven other available scans. Referring to FIG. 6P, the browser of the end user 500 returns to the end user GUI 210 of the platform 100 with information identifying the end user 500 information and the access provider 600 information. Referring to FIG. 6Q, by using the end user 500 information and the access provider 600 information supplied via the URL, the platform 100 may retrieve the scan history profile from the scan cache component 107, and The scan history profile is used to introduce end user GUI 210 to a user 500 branded according to the identified access provider. Referring to FIG. 6R, the platform 100 using the provider-branded end user GUI 210 introduces all services available through the hub site 101 to the end user 500. In such a case, the access provider rules still apply, and the user 500 can be prevented from observing the services provided by the competitors of the provider 600. The user then launches all the services provided.

In the end user 500 experience described with reference to FIGS. 6A-6R, the end user 500 has demonstrated its stated purpose by presenting its purpose to make a purchase, as shown in FIG. 6M. The end user 500 has various different specified purposes, such as thinking, selling, searching, including, transmitting, and the like. For example, FIG. 6S illustrates user interface 6002, which is a preferred example on mobile phone 6001. FIG. Shown in interface 6002 is a bookmark identification service that the user can select. By selecting a particular bookmark, the end user 500 displays its specified request.

7 illustrates a preferred embodiment of a system 7000 used to implement the method of the present invention. Calls made by the end user 500 via the end user GUI 210 (see, eg, FIG. 2A) are satisfied by the consumer zone 711, each of which is a web server 713 and an application. Server 710. Each consumer zone 711 also includes a fire wall 712. This preferred embodiment shows three consumer zones 711, but any number of consumer zones may be employed if desired in accordance with the present invention. Thus, system 7000 is scalable. As described with reference to FIG. 2A, management segment 720 satisfies calls made through account manager 230 and code manager 220. In addition, end-user authentication may be performed through the authentication service 721 of the management segment 720. The state of the record area 730 provides a backup of all the information maintained on the platform 100 (see FIG. 2A), and therefore high security is required. Internet access to system 7000 may be through an internet connection segment 740.

8A and 8B, a method of selectively sharing and storing end users is described, which is a system having a plurality of end users remotely accessing a network having at least one hub site and a plurality of provider sites. Is done in In step 801, a user record corresponding to each end user is stored in a profile database associated with the hub site. Each user record may include public information that the end user expects to share with one or more providers without the end user's permission, presented to the hub site by the end user; Secret information that the end user expects not shared with any provider without the end user's permission, presented to the hub site by the end user; And a non-external identification symbol associated with the user record identifying the end user on the network. In step 802, a first request signal is received that includes a non-external identification symbol corresponding to an end user. In step 803, in response to the first request signal, public information associated with the end user is sent from the hub site to the provider without the end user's permission. In step 804, a second request signal is received that includes a non-external identification symbol corresponding to the end user. In step 805, an authorization request is sent from the hub site to the end user. In step 806, it is determined in response to the permission request whether an end user permission has been received. If so, in step 807, secret information associated with the end user is sent from the hub site to the provider. If not, at step 808, the secret information is not sent.

In some embodiments, each user record further includes financial information associated with the end user. In this embodiment, at step 809, a third request signal is received that includes a non-external identification symbol corresponding to the end user. In step 810, in response to the third request signal, the second grant request is sent from the hub site to the end user. In step 811, it is determined in response to the second permission request whether an end user permission has been received. If not, at step 812, financial information is not sent. If authorization was received as shown in Figure 8B, then in step 813 it is determined whether authentication information has been received from the provider. If so, in step 814, financial information associated with the end user is sent from the hub site to the provider. If not, at step 820, financial information is not sent.

In another embodiment, each user record further includes provider preference information associated with the end user. As shown in FIG. 8A, in this embodiment, at step 815, a fourth request signal is received that includes a non-external identification symbol corresponding to the end user. In step 816, in response to the fourth request signal, a third grant request is sent from the hub site to the end user. In step 817, it is determined in response to the third permission request whether an end user permission has been received. If not, at step 818, the provider preference information is not sent. If so, in step 819, provider preference information associated with the end user is sent from the hub site to the provider.

9, in a system with a plurality of end users remotely accessing a network having at least one hub site and a plurality of provider sites, identifying at least one end user location on the network of at least one provider. The method is shown. In step 901, code information corresponding to one or more codes (eg, machine readable codes) provided by an end user (eg, scanning) is received at the hub site. In step 902, in response to the code information, network address information corresponding to a location on a provider's network associated with the received code information is retrieved from a profile database associated with a hub site. In step 903, the network address information is used to indicate an end user's location on the network of the associated provider. The profile database includes a user record corresponding to each end user. The user record may include public information that the end user expects to share with one or more providers without the end user's permission, presented to the hub site by the end user; Secret information that the end user expects not shared with any provider without the end user's permission, presented to the hub site by the end user; And a non-external identification symbol associated with the user record identifying the end user on the network.

Referring to FIG. 10, 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, preserve user addition code information and at least for at least one end user A method of identifying a location on one provider's network is described. In step 1001, code information corresponding to one or more codes provided by the end user is received at the hub site. In step 1002, in response to the code information, network address information corresponding to a location on a provider's network associated with the received code information is retrieved from a profile database associated with a hub site. In step 1003, the network address information is used to indicate an end user's location on the network of the associated provider. In step 1004, the user addition code information is received from an end user at the hub site. In step 1005, the user addition code information is stored in the hub site.

Referring to FIG. 11, a method of transmitting information indicative of a scan of a device-reading code between network sites is described. At step 1101, information related to the scan of one or more device-readable codes formed by the end user is received at the first site. In step 1102, the information associated with the scan is stored in a database associated with the first site in a data record having the associated unique alphanumeric identifier. In step 1103, the end user indicates the second site by means of a URL at the first site, both a code identifying the address of the second site on the network and a unique alphanumeric identifier associated with the information stored at the first site. Done. In step 1104, a request signal is received at the first site from the second site for the information stored at the first site. The request signal includes a unique alphanumeric identifier indication. In step 1105, the stored information is sent from the first site to the second site in response to the request signal.

12, a method of instructing an end user of a network location using information corresponding to a provider associated with an end user is described. In step 1201, a database is provided. The database includes a plurality of records, each record associated with a different device-readable code, wherein one or more records have a plurality of different network addresses associated therewith, and the different network addresses are different providers. Related to. In step 1202, scan information is received at a network site. The scan information relates to the scanning of one or more device-reading codes formed by the end user with the remote scanning device, wherein the end user is associated with one different provider. In step 1203, in response to the scan information, a record associated with the device-reading code scanned by the end user is retrieved from the database. In step 1204, at least one network address for each retrieved record is selected based on the specified category by the provider associated with the end user. In another embodiment, the network address is selected based on the specified purpose of the end user. In another embodiment, the network address is selected based on the characteristic information of the session of the end user on the network. In step 1205, transmission of at least one selected network address to an end user at a network site begins.

Claims (33)

A system for selectively sharing and storing end user information 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, comprising: a) In the profile database associated with the hub site, public information that the end user expects to be shared with one or more providers without the end user's permission, presented by the end user to the hub site, presented by the end user to the hub site. Each containing a non-externally identifying symbol associated with a user record that identifies the end user on the network, and secret information that the end user expects not to share with any provider without the end user's permission. Storing a user record, corresponding to the end user of the; b) in response to the first request signal comprising a non-external identification symbol corresponding to the end user, sending public information associated with the end user from the hub site to the provider without the end user's permission; And c) in response to the second request signal comprising a non-external identification symbol corresponding to the end user, sending a grant request from the hub site to the end user, and only when the end user's grant is received in response to the grant request. Transmitting secret information associated with the end user from the provider to the provider; Information sharing and storage method comprising a. 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 in which at least one end user identifies a location on the network of at least one provider, the method comprising: Receiving code information corresponding to one or more codes provided by the end user at the hub site; Responsive to the code information, retrieving network address information corresponding to a location on a network of a provider associated with the received code information from a profile database associated with a hub site; And Using network address information to indicate to an end user a location on a network of associated providers; Including; Here, the profile database is public information that the end user expects to be shared with one or more providers without end user's permission, presented by the end user to the hub site, end user presented to the hub site by the end user. A user record corresponding to each end user, including secret information that the end user expects not to be shared with any provider without permission of the user, and a non-external identification symbol associated with the user record identifying the end user on the network. Location identification method on a network, comprising: a network; A method of transmitting information representing scanned machine-readable codes between network sites, a) at a first site, receiving information related to a scan of one or more machine readable codes formed by an end user; b) storing information related to the scan of one or more machine-readable codes in a data record having an associated unique alphanumeric identifier in a database associated with the first site; c) directing the end user from the first site to the second site by a URL comprising a code identifying the address of the second site on the network and a unique alphanumeric identifier associated with the information stored at the first site; d) at the first site, receiving a request signal from the second site for the information stored at the first site, the unique alphanumeric identifier indication; And e) transmitting the stored information from the first site to the second site in response to the request signal; Information transmission method comprising a. A method of instructing a user of a network location using information corresponding to a provider associated with an end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on a category specified by a provider associated with the end user; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. According to claim 1, Each user record further comprises financial information about an end user, d) sending a second grant request from the hub site to the end user in response to a third request signal that includes a non-external identification symbol corresponding to the end user, and permitting the end user in response to the second grant request. And receiving, when received, authentication information from the provider, transmitting financial information associated with the end user from the hub site to the provider. According to claim 1, And wherein said one or more codes comprise one or more machine readable codes. A system for transmitting information indicative of machine readable codes scanned between network sites, A first site to receive information related to scanning of one or more machine readable codes formed by an end user; A database associated with the first site that stores information related to the scan of one or more machine readable codes in a data record having an associated unique alphanumeric identifier; And From a first site, the end user is indicated by a URL comprising a code identifying an address of a second site on a network and a unique alphanumeric identifier associated with information stored at the first site; Including; Wherein a request signal from a second site for information stored at the first site, including a unique alphanumeric identifier indication, is received at the first site, The stored information is transmitted from the first site to the second site in response to the request signal. A method of instructing an end user of a network location using information corresponding to a provider associated with the end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on the specified purpose of the end user; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. According to claim 1, Each user record further comprises provider preference information about an end user, d) in response to the fourth request signal comprising a non-external identification symbol corresponding to the end user, send a third grant request from the hub site to the end user, and the end user's permission is received in response to the third grant request. And, if so, transmitting provider preference information related to the end user from the hub site to the provider. The method of claim 2, And said machine readable code is scanned by an end user. According to claim 1, A method of sharing and storing information, wherein only a support provider supporting an end user on the network has the right to permanently suspend the end user's access to the network. A method of instructing an end user of a network location using information corresponding to a provider associated with the end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on characteristic information of a session of an end user on the network; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. In a system with a plurality of end users remotely accessing a network having at least one hub site and a plurality of provider sites, at least one end user identifies a location on the network of at least one provider and retrieves user additive code information. As a method of preservation, Receiving code information corresponding to one or more codes provided by the end user at the hub site; Responsive to the code information, retrieving network address information corresponding to a location on a network of a provider associated with the received code information from a profile database associated with a hub site; Using network address information to indicate to an end user a location on a network of associated providers; Receiving user addition code information from an end user at the hub site; And Storing the user addition code information in a hub site; Location identification and code information preservation method on a network comprising a. A network remotely accessed by a plurality of end users, the network having at least one hub site and a plurality of provider sites; And Public information that an end user expects to be shared with one or more providers without the end user's permission, presented by the end user to the hub site, or shared with any provider without the end user's permission that the end user presents on the hub site. Secret information that the end user would also expect, and non-external identification symbols associated with the user record identifying the end user on the network, and associated with the hub site for storing the user record, corresponding to each end user. Profile database; Including; Wherein, in response to the first request signal comprising a non-external identification symbol corresponding to the end user, transmitting public information related to the end user from the hub site to the provider without the end user's permission, Here, in response to the second request signal including the non-external identification symbol corresponding to the end user, the hub request is sent from the hub site to the end user, and only when the end user's permission is received in response to the permission request. A system for selectively sharing and storing end user information, the method comprising transmitting secret information associated with an end user from a site to a provider. A network having at least one hub site and a plurality of provider sites from which code information corresponding to one or more codes provided by the end user is received, the plurality of end users accessing remotely; A profile database associated with a hub site from which network address information corresponding to a location on a provider's network associated with code information received in response to the code information is retrieved; Including; Here, the profile database is public information that the end user expects to be shared with one or more providers without end user's permission, presented by the end user to the hub site, end user presented to the hub site by the end user. A user record, corresponding to each end user, containing secret information that the end user expects will not be shared with any provider without permission of the user, and a non-external identification symbol associated with the user record that identifies the end user on the network. Include, Wherein the network address information is used to indicate to an end user a location on the network of a provider associated with the at least one end user. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine-readable code scanned by the end user from the database, and for each retrieved record based on the category specified by the provider associated with the end user. Selecting at least one network address and initiating transmission of the at least one selected network address from a network site to an end user. A system in which at least one end user identifies the location of at least one provider and preserves user addition code information. A network accessed by a plurality of end users remotely, the network having at least one hub site and a plurality of provider sites from which code information corresponding to one or more codes provided by an end user is received; A profile database associated with a hub site from which network address information corresponding to a location on a provider's network associated with code information received in response to the code information is retrieved; Including; Here, the network address information is used to indicate the location on the network of the provider concerned to the end user, Here, the user addition code information is received from the end user at the hub site, Wherein the user addition code information is stored in the hub site. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine readable code scanned by the end user from the database, and based on the specified purpose of the end user, at least one network address for each retrieved record. And initiate transmission of the at least one selected network address from a network site to an end user. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; And A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine-readable code scanned by the end user from a database, and based on at least characteristic information of the session of the end user on the network, at least for each retrieved record. Selecting one network address and initiating transmission of at least one selected network address from a network site to an end user. 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 in which at least one end user identifies a location on the network of at least one provider, the method comprising: Receiving code information corresponding to one or more codes provided by the end user at the hub site; Responsive to the code information, retrieving network address information corresponding to a location on a network of a provider associated with the received code information from a profile database associated with a hub site; And Using network address information to indicate to an end user a location on a network of associated providers; Including; Here, the profile database is public information that the end user expects to be shared with one or more providers without end user's permission, presented by the end user to the hub site, end user presented to the hub site by the end user. A user record corresponding to each end user, including secret information that the end user expects not to be shared with any provider without permission of the user, and a non-external identification symbol associated with the user record identifying the end user on the network. Location identification method on a network, comprising: a network; The method of claim 20, Wherein said one or more codes comprise one or more machine readable codes. The method of claim 21, And said machine readable code is scanned by an end user. In a system with a plurality of end users remotely accessing a network having at least one hub site and a plurality of provider sites, at least one end user identifies a location on the network of at least one provider and retrieves user additive code information. As a method of preservation, Receiving code information corresponding to one or more codes provided by the end user at the hub site; Responsive to the code information, retrieving network address information corresponding to a location on a network of a provider associated with the received code information from a profile database associated with a hub site; Using network address information to indicate to an end user a location on a network of associated providers; Receiving user addition code information from an end user at the hub site; And Storing the user addition code information in a hub site; Location identification and code information preservation method on a network comprising a. A network having at least one hub site and a plurality of provider sites from which code information corresponding to one or more codes provided by the end user is received, the plurality of end users accessing remotely; A profile database associated with a hub site from which network address information corresponding to a location on a provider's network associated with code information received in response to the code information is retrieved; Including; Here, the profile database is public information that the end user expects to be shared with one or more providers without end user's permission, presented by the end user to the hub site, end user presented to the hub site by the end user. A user record, corresponding to each end user, containing secret information that the end user expects will not be shared with any provider without permission of the user, and a non-external identification symbol associated with the user record that identifies the end user on the network. Include, Wherein the network address information is used to indicate to an end user a location on the network of a provider associated with the at least one end user. A system in which at least one end user identifies the location of at least one provider and preserves user addition code information. A network accessed by a plurality of end users remotely, the network having at least one hub site and a plurality of provider sites from which code information corresponding to one or more codes provided by the end user is received; A profile database associated with a hub site from which network address information corresponding to a location on a provider's network associated with code information received in response to the code information is retrieved; Including; Here, the network address information is used to indicate the location on the network of the provider concerned to the end user, Here, the user addition code information is received from the end user at the hub site, Wherein the user addition code information is stored in the hub site. A method of transmitting information representing scanned machine-readable codes between network sites, a) at a first site, receiving information related to a scan of one or more machine readable codes formed by an end user; b) storing information related to the scan of one or more machine-readable codes in a data record having an associated unique alphanumeric identifier in a database associated with the first site; c) directing the end user from the first site to the second site by a URL comprising a code identifying the address of the second site on the network and a unique alphanumeric identifier associated with the information stored at the first site; d) at the first site, receiving a request signal from the second site for the information stored at the first site, the unique alphanumeric identifier indication; And e) transmitting the stored information from the first site to the second site in response to the request signal; Information transmission method comprising a. A system for transmitting information indicative of machine readable codes scanned between network sites, A first site to receive information related to scanning of one or more machine readable codes formed by an end user; A database associated with the first site that stores information related to the scan of one or more machine readable codes in a data record having an associated unique alphanumeric identifier; And From a first site, the end user is indicated by a URL comprising a code identifying an address of a second site on a network and a unique alphanumeric identifier associated with information stored at the first site; Including; Wherein a request signal from a second site for information stored at the first site, including a unique alphanumeric identifier indication, is received at the first site, The stored information is transmitted from the first site to the second site in response to the request signal. A method of instructing a user of a network location using information corresponding to a provider associated with an end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on a category specified by a provider associated with the end user; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. A method of instructing an end user of a network location using information corresponding to a provider associated with the end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on the specified purpose of the end user; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. A method of instructing an end user of a network location using information corresponding to a provider associated with the end user, a) providing a database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; b) receiving scan information at a network site having a remote scanning device and associated with the scan of one or more machine-readable codes formed by an end user associated with one different provider; c) responsive to the scan information, retrieving from the database a record associated with the machine readable code scanned by the end user; d) selecting at least one network address for each retrieved record based on characteristic information of a session of an end user on the network; And e) initiating transmission of at least one selected network address from a network site to an end user; Network location indication method comprising a. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine-readable code scanned by the end user from the database, and for each retrieved record based on the category specified by the provider associated with the end user. Selecting at least one network address and initiating transmission of the at least one selected network address from a network site to an end user. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine-readable code scanned by the end user from the database, and based on the specified purpose of the end user, at least one network address for each retrieved record. And initiate transmission of the at least one selected network address from a network site to an end user. A system for instructing a user of a network location using information corresponding to a provider associated with an end user, A database having a plurality of records, each associated with a different machine readable code and having a network address associated with a different provider; And A network site having a remote scanning device, the network site receiving scan information related to scanning of one or more machine-readable codes formed by end users associated with one different provider; Including; Wherein, in response to the scan information, retrieve a record associated with the machine-readable code scanned by the end user from a database, and based on at least characteristic information of the session of the end user on the network, at least for each retrieved record. Selecting one network address and initiating transmission of at least one selected network address from a network site to an end user.