JP2000076189A - System and method for controlling transmission of stored information to internet web site - Google Patents

Abstract

PROBLEM TO BE SOLVED: To protect the privacy of information included in a recording area of a user's personal computer by generating a decision regarding a response to a request and automatically implementing the decision regarding the response to the request. SOLUTION: A user's browser 8 stores data in a user's electronic wallet 12 instead of writing the data to the hard disk of a user's personal computer where the browser is installed. The user 6 accesses a web site, whose web site server 2 makes a request to write the data to the storage device on the user's personal computer 4 and inquires the request of the user 6 to determine whether or not the data is received. According to the decision, the transfer of the data to the web site server 2 is automatically performed as a decision regarding the response to the request according to the decision.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[Cross Reference with Related Applications]
Co-pending US Provisional Patent Application No.
60 / 081,748; issued on November 12, 1998
Co-pending U.S. Patent Application Serial No. 09 / 190,99
No.3: The title of the invention is "Store electronic data safely.
Systems and methods " Year Month Date application
U.S. Patent Application No. Issue; and the title of the invention
Graphic signature system " Year Month
U.S. Patent Application No. Partial continuation of
Applications, which are incorporated herein by reference.
You.

[0002]

FIELD OF THE INVENTION The present invention relates generally to Internet web-based client / server applications, and more particularly, to the storage of electronically stored information on electronic media at Internet websites accessed by consumers. A system and method for controlling transmission.

[0003]

BACKGROUND OF THE INVENTION As the Internet evolves,
The purpose of maintaining a website has also changed. Currently, websites not only entertain visitors, but in some cases, in exchange for fees,
It is also used as a medium for providing services and information. Thus, many website owners now use the website as a virtual point-of-sale show window or service counter. The exchanges that take place in traditional service counters and traditional stores are
If the store owner or employee is not a name,
It involves personal contact that can identify the customer by eye. Ideally, after a consumer interacts a lot with the owner, the owner will know the consumer's preferences and can link those preferences to the consumer's identity. Linking customer preferences to customer identities allows store owners and service providers to respond more quickly to customer needs, so that they can remain competitive it can.

[0004] Because website owners do not have personal contact with the person accessing the website, the website owner needs some means other than visual identification to identify the virtual customer. One mechanism that has been developed to help website owners identify who visits the site is cookies (co
okie). A cookie is a piece of software, usually a few lines of text or less, stored on the hard drive of a personal computer (PC) that accesses a website. PCs use the Hyper Text Transfer Protocol (H) to access websites on the World Wide Web portion of the Internet.
TTP). HTTP transactions include requests from individual PCs attempting to access the website and responses issued by the website server.

[0005] Generally, a software application residing on a PC, usually called a browser, sends a request to a server, which issues a response in which the hypertext description language (HTM) is described.
L) Return the document to the PC browser. Cookie transmission is
Occurs as part of the HTTP transaction process. The web site server transmits the cookie along with the rest of the requested HTML document (ie, the accessed web page) to the browser on the PC. Next, the browser places the cookie on the hard disk of each PC.
Accumulate on drive. Therefore, the transmission of the cookie is H
Less obvious than downloading a TML file. In fact, cookies are obscured and are a way for website owners to gather information without bothering website visitors.

[0006] Cookies are a common mechanism that allows a server to store information on the hard drive of the PC accessing the website. The server only looks for cookies sent by itself, and therefore can only use them. Normally, servers cannot access cookies set by other servers. Thus, the information in the cookie is typically stored in a uniform resource locator (UR) that has access to the cookie.
L) or a description of a range of website addresses. Future HTTP U from the PC where the cookie resides that falls within the URL identified in the cookie
The RL request includes transmission of a cookie from the PC to the server. When the server retrieves a previously stored cookie, the server updates the information received and
The updated cookie can be sent back to the PC.

[0007] The type of information stored in a cookie can vary widely. For example, cookies are used by website owners to obtain various useful arrangement information regarding visitors to their website. In its simplest form, cookies can be used as a type of non-personal identification badge. For example, the cookie may return to the server only reports that the user identified by the number periodically views a particular page on the website. The cookie can keep a record of the pages that have been visited most and how much time has been spent on those pages. The types of things that are usually written in cookies are, for example, visitor IDs in website databases,
Includes pages that have been visited most frequently previously, or any other kind of thing that is useful to website owners.
For example, cookies indicate the last time a user visited a site, how often the user visited the site, what pages the user viewed, and what the user was interested in.

[0008] Cookies allow website owners to react quickly and effectively to serve a large number of users of the website. For example, one user visits many pages of a website in page order,
If the user stays on page 25 of the 45 pages and visits the website the next time, the cookie will indicate where the user has stayed and may ask the user if they want to continue where they left off. Cookies, just like traditional store service counters, allow website owners to recognize a customer and return a level of custom or personalized service when the customer returns to the store. To provide to customers.

[0009] Cookies are similar to reminders to website owners. Cookies allow website owners to write their own notes and give them to their customers. Whenever a customer returns to the website, the memo is brought and the website owner can read it and determine from the memo what to remember about the customer. Website owners can change what is stored in the memo over time, or give each customer many different memos,
Website owners can also remember many different things about each customer.

[0010] Cookies can also be used to provide a more personalized world wide web to look through the experience. For example, a website may request that the user fill in a form listing the types of information that the user prefers to search each time the user visits a particular website. The user preferences are stored in a file maintained on the website server and linked to a specific cookie that is transmitted to the user's PC. The next time that particular PC visits the website,
The cookies transmitted to the web site provide only the information specified by the user as being of interest by identifying the file containing the user's preferences. By using cookies in this manner, during a subsequent connection, the user is relieved of having to re-enter the user ID. Where possible, the website stores user preferences in cookies. Then, the web site can obtain the user's preference every time the user accesses the web site.

[0011] Websites that provide shopping carts to Internet shoppers may use cookies to store information about the items that are placed in the shopping cart. Cookies are
Enables virtual customers to put items in their shopping basket, finish their online session, and then see the basket they left behind when returning to the site. Cookies also determine how users navigate around websites, what pages they visit most often, how they enter those pages, and
You can track which one you can navigate more efficiently. For example, if a user has visited a website with a large number of pages, use cookies to remember which page in the page order the user stopped, and from where he ended in the next online session. You can ask the user if you want to continue. Cookies can track this type of information on an individual user basis.

[0012] Well-designed cookies allow a website owner to direct a user to somewhere else on the web, whether or not a particular page is the user's starting point. Make it possible to determine whether or not it is Even simple tasks such as counting visitors can be enhanced by cookies. Without the information contained in the cookie, typical counters cannot determine how many individual users have visited the site and how many of the total hits are repeat visitors. In a sense, cookies allow website owners to write down their own notes and pass them on to their visitors. And
Each time the user returns to the website, the owner can search the memorandum to identify the visitor and his preferences.

At present, users can only control whether or not to accept cookies from websites, and cannot control the distribution of cookies residing on their PC's hard drive. The Internet browser can be configured to request consumer permission to accept the provided cookie. By default, the browser is configured to accept cookies from websites without asking the consumer for permission. Many consumers are unaware of their ability to do so, so they do not configure their browsers to ask if the user accepts the cookies provided. As many websites constantly attempt to send dozens of cookies during the transmission of a single HTML document, it is becoming too cumbersome to see the experience. So nobody else has their own browser.

[0014] Even if the consumer configures the browser to request permission before accepting the cookie, once the cookie is accepted, the consumer can now disseminate the information stored in the cookie on the PC's hard drive. Can not control. The client side of the browser initially allows the visitor to decide whether or not they want a cookie, but once the cookie is there, nothing prevents the cookie from being retrieved.

[0015]

SUMMARY OF THE INVENTION The features and advantages of the present invention reside in the user's PC.
In order to protect the privacy of the information contained in the recording area, the PC user is provided with the ability to manage the flow and content of information in the cookie.

A further feature and advantage of the present invention is that it provides online customers with the ability to control where cookies will be stored, especially protecting the privacy of the information contained within the cookies. To provide the ability to consumers.

[0017] Another feature and advantage of the present invention is to provide consumers with the ability to control the spread of cookies residing on electronic storage media.

An additional feature and advantage of the present invention is that it allows consumers to assign different levels of privacy levels to the information contained in the cookie, and the assigned privacy value allows the consumer to control the spread of the cookie. Is to be able to do it.

Yet another additional feature and advantage of the present invention is that it allows consumers to monitor and weigh the information that a merchant or website captures in the form of cookies and leaves.

A still further feature and advantage of the present invention is that the value of the information contained in a cookie in an electronic wallet or on a hard drive of a PC, for example, to request compensation for access to the information contained in the cookie By doing so, the consumer can be realized.

To achieve the above and other features, advantages, and objects of the present invention, embodiments of the present invention provide a "cookie jar (c) in an electronic or virtual wallet.
ookie jar) ", and a system and method for controlling stored data transmission to an Internet website server. In an embodiment of the present invention, when a user accesses a website, the system accumulates data for a website server. Thereafter, when the user accesses the website again, the system of the present invention receives a request from the web server for stored data transmission to the website server. The system of the present invention generates or forms a decision regarding a response to a request,
Automatically make decisions about responding to requests.

In an embodiment of the invention, storing the data includes accessing the website server by a user at a terminal such as a PC having a browser application. When the website server is accessed by the user through the Internet,
The website server sends the data to the browser application, and the browser sends the user's virtual
Transfer data to the wallet application. A server-based virtual wallet application requests a user's permission to store data by automatically prompting the user for permission at the terminal. The user enters into the terminal a decision to either reserve the permission or accept the permission.
If the user accepts permission to store the data, the data is automatically stored by the virtual wallet application.

When the user accesses the same website server again, the website server sends a request for transmission of the stored data received by the user's virtual wallet application. The virtual wallet application automatically generates or forms the decision by prompting the user at the terminal for the user's decision regarding the response to the request from the website server. The user
A decision is made at the terminal to either reject the request or accept the request at the terminal.

In an embodiment of the present invention, alternatively, the user may pre-configure the virtual wallet application with at least one predefined parameter in determining a response to a request. The predefined parameters are, for example, parameters relating to information contained in the stored data, such as the user's name and / or address, or, for example, the identity of a website server requesting transmission of the stored data. This is a parameter related to proof. The pre-configured virtual wallet application automatically generates or forms a user's decision based at least in part on one or both of the predefined parameters. In other words, the virtual wallet application determines whether to reserve the stored data or send it to the website server based at least in part on one or both of the parameters.
Automatically generate or shape decisions for users.

This decision on the response may be based on either automatically rejecting the request and retaining the stored data, or by accepting the request and sending the stored data to the website server to automatically send the response to the website server. The user's virtual wallet application runs automatically. The system comprises a terminal, such as a user's PC with a browser application, used to access a website server, and a server-based electronic device that communicates with the user's PC over a network, such as the Internet. Or a virtual wallet application.

[0026] Additional objects, advantages and novel features of the invention will be set forth in part in the description which follows, and in part by reviewing the following, or by learning to practice the invention. It will be more apparent to those familiar with.

[0027]

DETAILED DESCRIPTION Reference is made in detail to an embodiment of the present invention, an example of which is illustrated in the accompanying drawings, in which the present invention provides information stored on electronic media to an Internet website accessed by a consumer. System and method for controlling transmission of data. The invention is PC
The user is provided with a certain degree of control over, for example, the manner in which the cookies stored on the hard drive of the PC are distributed. In addition, embodiments of the present invention provide P
C Allows a user to incorporate a certain level of intelligence into the user's browser.

As used herein, a cookie is a piece of information that a server can store on a device that accesses the server. For example, a website server may store cookies on the PC of a browser user accessing the website. A cookie contains information that a user has provided to a website, such as information in a form written to access the site. Normally, only the server that stores the cookie can access the information on the cookie. The systems and methods of the present invention, referred to herein as cookie jars, provide PC users / owners with the ability to protect the privacy of information in cookies and / or realize the value of information.

The systems and methods of embodiments of the present invention also manage the flow and content of information in cookies. For example, if the system of the present invention allows a PC user to read and approve data stored on a hard drive,
Cookies can be added at will. Similarly, this feature of the system of the present invention advantageously
The information contained in the cookie can be excluded, provided that the PC
Certain conditions, such as user approval.

In addition, the PC user can establish policies for different levels of information such that certain information may be removed without prompting the PC user. Furthermore, since the information in the cookie has a certain value,
The C user may request some form of compensation for the removal of information in the cookie. Thus, the system and method of the present invention monitors and weighs the information in the cookies captured and left by the merchant.

The system for an embodiment of the present invention can utilize application software such as an electronic or virtual wallet and utilizes a cookie jar residing within the electronic or virtual wallet of an embodiment of the present invention. it can. An electronic wallet is an embodiment of the software, the owner of which, for example, a payment mechanism,
Serves as a container for identity authentication mechanisms, personal information, and electronic artifacts. The electronic wallet can reside, for example, on a consumer PC, server, or smart card.

Currently, many electronic wallets focus on payment mechanisms. However, electronic wallets are: ID information; credit card account information; customer loyalty program information; personal information manager; site profile repository; telephone card; agent profile; and other payment mechanisms (eg, debit card information). Used to preserve
For a detailed discussion of electronic wallets, see, for example, co-pending and commonly-owned provisional application No. 60/08, filed Apr. 14, 1998, which is hereby incorporated by reference.
See 1,748. The information stored in the electronic wallet can be transmitted and received by the owner of the electronic wallet in the form of cookies, for example, over the Internet or other types of networks.

The system and method of embodiments of the present invention can receive any cookie provided by a particular entity's website, such as the user's bank, and the particular entity's website requests the cookie. Whenever you do, allow the PC user to specify that a cookie can be returned to the entity at any time. On the other hand, for a website of an entity for which the PC user does not wish to exchange much information, the user specifies that the user's permission must first be requested for any cookies provided by that particular website. be able to.

Further, the system and method of the present invention may require that a user's permission be requested, for example, if a cookie provided by a particular website has the user's ID thereon. If the cookie does not have the user's ID on it, allow the PC user to specify that no authorization is required. The system and method of the present invention provide value-added services to PC users in terms of privacy and data protection,
Help users decide what level of data protection they want.

At present, cookies are stored on a hard disk of a user PC on which browser software is installed.
It is stored as a simple text file on the drive. Typically, a browser can be configured by a PC user, for example, to request permission from the user before accepting a cookie. FIG. 1 shows an overview of the main components and the flow of information between the main components of a prior art interaction between a PC and a website server with a browser. A typical cookie interaction includes a web server 2 of a website and a user computer or PC 4. When user 6 on his PC 4 goes to a website, if web server 2 wants to write a cookie, it contacts browser 8 on the user PC and sends the cookie to the browser. If the browser 8 is not configured by the user 6, the cookie is automatically stored on the user PC 4 by the web server 2. If the browser 8 is configured, the configured browser on the user PC 4 asks the user 6 whether or not to accept the cookie, but the user replies yes or no. If the user answers yes,
Data is written to the user PC 4 by the web server 2.

FIG. 2 is a flow chart showing, in an enlarged manner, the flow of information shown in FIG. 1 in the prior art interaction between the website server 2 and the user PC 4 having the unconfigured browser 8. Provide more details. In S1, a user 6 surfing the Internet accesses a website. In S2, the accessed website server 2 loads the web page to the user's PC 4 and loads the user's PC.
Place the cookie in the folder specified by the browser 8 on the hard drive. Later, in S3, when the user 6 returns to the website, the website server 2 sends the information included in the cookie to the user's PC.
Search from 4. In S4, the website server 2 sends the web page to the user's PC4.
And send a new or updated cookie to the user's PC4.

FIG. 3 is a flow chart showing a prior art interaction between a website server 2 and a user's PC 4 having a browser 8 configured by a user 6 to seek permission before accepting cookies. The information flow shown in FIG. 1 is expanded to provide further details. In S11, the user 6 accesses the website. At S12, the accessed website server 2 requests permission to load the cookie in the hard drive of the user's PC4. S13
If the user 6 does not accept the cookie, the accessed website server 2
No cookies on hard drive 4 and S14
Then, the website server loads the web page into the user's PC4. When the user 6 returns to the same website, the user is treated by the website server 2 as an initial visitor and the process is repeated.

Still referring to FIG. 3, instead, if the user 6 accepts the cookie in S15, the accessed website server 2 loads the cookie and the web page in the user's PC 4 in S16. afterwards,
When the user 2 returns to the website at S17, the website server 2 wants to know what cookies are stored on the user's PC4. The web server 2 requests the browser 8 on the user's PC 4 to send the cookie back. Web server 2
Ask for the name of the cookie you want returned, and in S18,
The cookie is automatically sent back by the browser 8 on the user's PC 4 and, at S19, the website server 2
Loads a web page on the user's PC4.
In this way, the PC user 6 can configure the browser so that it cannot accept cookies without asking the user for permission, but after accepting, the user cannot control the cookies.

FIG. 4 shows a website server 2 and a cookie server for the method and system of an embodiment of the present invention.
1 shows an overview of the main components and the flow of information between the main components in an interaction with a user PC having a jar 10. According to the present invention, instead of writing a cookie on the hard disk of the user PC 4 on which the user's browser 8 is installed, for example, the cookie is stored in the user's electronic wallet 12.
Thus, the PC user 6 goes to the website, the website server 2 asks if the user may be given a cookie, and when the user accepts, the cookie is sent by the web server to the browser 8 on the user's PC 4.
, But is transferred to the user's electronic wallet 12.

The system and method of the present invention store cookies in the secure data storage of the electronic or virtual wallet 12, along with all other electronic information that is also stored in the electronic wallet. Since the electronic wallet 12 is, for example, a server-based wallet, cookies can be used wherever an electronic wallet is available. In this way, the cookie is sent to the PC user's electronic wallet 12 and stored, rather than being written on the hard drive of the user's PC 4 where the user's browser 8 is installed.

FIG. 5 is a flow chart showing a website server 2, a user PC 4 having a cookie jar 10 in a browser 8 and an electronic wallet 12.
FIG. 4 expands the information flow shown in FIG. 4 for interaction between and provides further details. In S21, the user 6 accesses the website, and in S22, the website server requests permission to write data to the cookie storage device on the user's PC4. S
At 23, a request is made from the browser 8 to the cookie jar 10 residing in an electronic or virtual wallet 12.
The virtual wallet asks the user 6 if a particular website server may store the cookie (OK). User 6 determines whether to accept the cookie and, at S25, if user 6 refuses permission, website server 2 simply loads the web page onto user's PC4. When user 6 returns to the same website, website server 2 treats the user as an initial visitor and the process is repeated.

Still referring to FIG. 5, instead of S26
When the user 6 accepts the cookie, the data of the cookie is transmitted by the web server 2 to the user's PC.
4 to the browser 8. In S27, the browser
Virtual or electronic wallet 12
Transfer to Cookie Jar 1 living in an electronic wallet
Cookie data is stored in 0. At S28, when the user 6 returns to the website, at S29, the web
Server 2 requests to return its cookie. However, cookies are not automatically returned. Instead, the user 6 controls whether to return the cookie to the website server 2. The manner in which the decision is made is determined by cookies in the electronic or virtual wallet 12 in the system of the present invention. The user's control over the cookie is enforced by the user either approving or rejecting permission to return the cookie.

Referring again to FIG. 5, if the cookie jar 10 is not pre-configured by the user 6 at S41, the cookie jar asks the user if it is OK to send the cookie. Depending on whether the user 6 accepts or rejects the permission, the cookie may or may not be returned to the website server 2. On the other hand, the user 6 can pre-configure the cookie jar 10 to allow all access to the cookie jar from a particular website server, such as the user's bank, in which case the user may even be queried. Instead, cookies are automatically sent to a particular website server by a cookie jar. However, the user 6 can also pre-configure the cookie jar 10 so as to never allow access to the cookie jar from a particular website server, in which case the user is not even queried. , The request will simply be rejected flat.

Alternatively, when a particular website server requests a return of a cookie containing information of a predefined nature, it informs the user and asks the user if they want to issue a cookie. The user 6 can pre-configure the cookie jar 10. User 6 may also answer yes or no to accept or reject the request to return cookies on the website. Depending on how the user 6 configures and behaves his or her electronic wallet 12 and the cookie jar 10 in the electronic wallet, there are many other possible ways of returning and sending cookie information. There are options.

Embodiments of the system and method of the present invention involve a set of intelligence leading to a yes or no answer. Depending on the particular website, and depending on the nature of the information being exchanged, individual users may have different preferences as to how often they actually want to be asked to issue cookies. . For example, if the information in the cookie happens to include the user's name and address, the user 6 may be very nervous about where his name and address information is sent. On the other hand, if the information in the cookie is only the user ID number for a particular website,
User 6 may not be too nervous.

The system and method of embodiments of the present invention ensure that certain information, such as the user's name and address, is never issued without asking the user.
Has the ability built in during the interaction of the user 6 to configure the cookie jar 10. Similarly, the user 6 can configure the cookie jar 10 so that, for example, when logging to the user's bank website, the cookie jar does not need to request permission from the user to issue information.

In an embodiment of the present invention, the system comprises:
For example, two sets of controls are provided to pre-configure the cookie jar 10. One control set allows the user 6 to pre-configure the cookie jar 10 based on, for example, data present in the cookie. Thus, when the website server 2 requests a return of the cookie, the cookie jar 10 reads all the data in the cookie and determines whether to issue the cookie based on the data. The other set of controls allows the user 6 to pre-configure the cookie jar 10 based on, for example, who is asking for the data in the cookie. Thus, the cookie jar's decision to issue or not issue a cookie need not be based on what is in the data, but simply on where the information is being sent. The cookie jar 10 manages the magnitude of the importance of both controls.

Referring again to FIG. 5, based on the data in the cookie or the identity of the website requesting the cookie, the decision to issue or not issue the cookie without an interaction between the user and the cookie jar. When the cookie jar 10 is configured in advance by the user 6 so as to perform
The cookie jar reads the data in the cookie and / or identifies the website and decides not to issue a cookie. In S32, the cookie jar 10 rejects the request to issue a cookie.
The page loads. Alternatively, at S34, upon reading the data in the cookie and / or identifying the requesting website, the cookie jar determines to issue the cookie. In S35, cookie jar 1
0 sends a cookie to website server 2 and S3
At 6, the web page is similarly loaded.

In an embodiment of the present invention, when the user 6 returns to a website that was previously allowed to store cookies in the user's cookie jar 10, a decision is made not to issue cookies. ,Web Site·
The server 2 assumes that the user is a new user and, for example, displays a new user screen on the user's PC.
4 is displayed. As described above, the user 6 can select whether or not to issue a cookie, and can set cookie issuing conditions. For example, the user 6 can set the issuance of cookies stored in the user's cookie jar 10 as immediate authorization, and if there is an unusually long cookie with the user's name, You will be presented with a dialog box stating that the cookie containing will be sent to the particular website. User 6 responds with a yes or no answer to allow or deny permission to send the cookie to the website.

Various preferred embodiments of the present invention have been described in terms of achieving the various objects of the present invention. It should be recognized that these embodiments are illustrative of the principles of the present invention. Numerous variations and adaptations will be readily apparent to those skilled in the art without departing from the spirit and scope of the invention. Accordingly, the invention is limited only by the following claims.

[Brief description of the drawings]

 In the drawing:

FIG. 1 has a web site and a browser,
Provides an overview of the key components and the flow of information between the key components in a typical prior art interaction with a PC;

FIG. 2 is a flow chart of the information shown in FIG. 1 for a prior art interaction between a website server and a PC having an unconfigured (unbuilt) browser. Enlarge the flow and provide more details;

FIG. 3 is a flow chart of a prior art interaction between a web site server and a PC having a browser configured (constructed) to seek user permission before accepting cookies. , Expanding the flow of information shown in FIG. 1 and providing further details;

FIG. 4 shows an overview of the key components and the flow of information between the key components for an embodiment of the present invention; and

FIG. 5 is a flow chart illustrating the process of interaction between a website server and a PC having a cookie jar in an electronic or virtual wallet, according to an embodiment of the present invention. The information flow shown in Figure 4 is expanded to provide further details.

────────────────────────────────────────────────── ─── Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) H04L 29/06 H04L 13/00 305C (71) Applicant 598156527 12731 Jefferson Boulevard, Los Angeles, California 90066, U.S.A. SA (72) Inventor Christy. Parthenge, USA 91326, North Ridge, Entrade A Venue 11718, California (72) Inventor Lisa Ezroll United States 10021, New York, New York, East Seventy Second Street, Apartment 42A, 525

Claims (56)

[Claims] 1. A method for controlling stored data transmission to an Internet website server, comprising:
Storing the data for the web site server; receiving a request for the stored data transmission to the web site server; forming a decision regarding a response to the request; and Making said decision on the response automatically. 2. The method according to claim 1, further comprising the step of storing the data.
The method of claim 1, comprising accessing the website server by a user at a terminal. 3. The method of claim 2, wherein said terminal further comprises a PC having a browser application. 4. The method of claim 2, wherein accessing the website server further comprises accessing the website server over a network. 5. The method of claim 4, wherein said network further comprises the Internet. 6. The method of claim 3, wherein accessing the website server further comprises sending the data by the website server. 7. The method of claim 3, wherein sending the data by the website server further comprises sending the data to the browser application. 8. The method of claim 7, wherein sending the data to the browser application further comprises transferring the data by the browser application to the user's virtual wallet application. 9. The method of claim 8, wherein said virtual wallet application further comprises a server-based virtual wallet application. 10. The virtual wallet application further comprising: transferring the data to the virtual wallet application further comprising requesting the user's permission to store the data. Item 8. The method according to Item 8. 11. The method of claim 10, wherein requesting the permission of the user further comprises automatically prompting the user at the terminal for the permission by the virtual wallet application. 12. The step of prompting the user for permission includes:
The method of claim 11, further comprising entering a decision by the user at the terminal regarding the request for permission to store the data. 13. The method of claim 1, wherein entering the decision by the user further comprises entering the decision by the user accepting the permission.
Method 2. 14. The method of claim 13, wherein entering the decision to accept the permission further comprises storing the data with the virtual wallet application. 15. The method of claim 1, wherein receiving the request for the stored data transmission further comprises a user accessing a website server at a terminal. 16. The method of claim 15, wherein accessing the website server further comprises accessing the website server over a network. 17. The method of claim 16, wherein said network further comprises the Internet. 18. The method of claim 15, wherein accessing the website server by the user further comprises sending the request for transmission by the website server. 19. The method of claim 18, wherein sending the request by the website server further comprises receiving the request by the user's virtual wallet application. 20. The method of claim 1, wherein forming the decision regarding the response to the request further comprises receiving the request by a user's virtual wallet application. 21. The step of receiving the request by the virtual wallet application further comprising the step of automatically prompting the user at the terminal by the virtual wallet application for the decision on the response to the request. The method of claim 20. 22. The method of claim 21, wherein said terminal further comprises a PC. 23. The method of claim 21, wherein automatically prompting the user for the response further comprises entering the decision by the user at the terminal. 24. The step of inputting the decision further comprises:
3. The method of claim 2, further comprising the step of rejecting the request at the terminal and entering the decision by the user.
Method 3. 25. The step of inputting the decision further comprises:
3. Entering the decision by the user at the terminal to accept the request.
Method 4. 26. The step of forming a decision further comprises:
At least one predefined parameter for the decision regarding the response to the request,
3. The method of claim 2, further comprising pre-configuring the virtual wallet application by the user.
0 method. 27. The step of pre-configuring said virtual wallet application further comprises a group consisting of parameters relating to said stored data and parameters relating to said website server requesting said stored data transmission. At least one selected
27. The method of claim 26, comprising pre-configuring the virtual wallet application with two predefined parameters. 28. The step of forming a decision further comprises:
28. The method of claim 27, comprising automatically generating the decision by the virtual wallet application of the user based at least in part on at least one predefined parameter. 29. The step of automatically generating the decision further comprises rejecting the request by the user's virtual wallet application based at least in part on the parameter relating to the stored data. 29. The method of claim 28, comprising automatically generating 30. The step of automatically generating said decision further comprises: based at least in part on said parameters relating to said website server requesting said stored data transmission, said virtual wallet of said user. 29. The method of claim 28, comprising automatically generating the decision to reject the request by an application. 31. The step of automatically generating the decision further comprises the step of accepting the request by the user's virtual wallet application based at least in part on the parameter relating to the stored data. 29. The method of claim 28, comprising automatically generating 32. The step of automatically generating the decision further comprises: based at least in part on the parameters associated with a website server requesting transmission of the data, the virtual wallet application of the user. 29. The method of claim 28, comprising automatically generating the decision to grant the request by: 33. The step of automatically making the determination regarding the response further comprises automatically sending the response to the website server by a user's virtual wallet application. the method of. 34. The method of claim 33, wherein automatically sending the response further comprises automatically prompting the user at the terminal by the virtual wallet application to make the decision regarding the response. . 35. The method of claim 34, wherein said terminal further comprises a PC. 36. The method of claim 34, wherein automatically sending the response further comprises entering the decision by the user at a terminal. 37. Entering the decision by the user further comprises entering a decision of one of the following: rejecting the request by the user and accepting the request by the user. 37. The method of claim 36. 38. The step of entering the decision to reject the request by the user further comprising automatically reserving the stored data from the website server by the user's virtual wallet application. 38. The method of claim 37, comprising steps. 39. Accepting the request and entering the decision by the user further comprises automatically sending the stored data to the website server by the user's virtual wallet application. 38. The method of claim 37, comprising: 40. The step of automatically sending the response further comprising: storing the response by the virtual wallet application based on at least one predefined parameter pre-configured in the virtual wallet application. 34. The method of claim 33, comprising automatically generating the decision of one of a response to reserve data and a response to send the stored data to the website server. 41. The at least one predefined parameter is further selected from a group consisting of parameters relating to the stored data and parameters relating to the website server requesting the stored data. 41. The method of claim 40, comprising at least one predefined parameter. 42. The step of automatically sending the response further comprises automatically retrieving the stored data from the website server by the virtual wallet application based at least in part on parameters related to the stored data. 42. The method of claim 41, further comprising the step of dynamically retaining. 43. The method of automatically sending the response further comprising: at least in part based on parameters associated with the web site server requesting the stored data, the virtual wallet application providing the web site server. 42. The method of claim 41, comprising automatically reserving said stored data from a server. 44. The method of automatically sending the response further comprising automatically sending the stored data to the website server based at least in part on parameters related to the stored data. Item 41. The method of Item 41. 45. The step of automatically sending the response further comprises automatically sending the stored data to the website server based at least in part on parameters associated with the website server requesting the stored data. 42. The method of claim 41, further comprising the step of sending. 46. A system for controlling stored data transmission to an Internet Web site server, comprising: means for storing the data for the Web site server; and transmitting the stored data to the Web site server. Means associated with the storage means for receiving a request for the request; means associated with the transmission means for forming a decision regarding the response to the request; and the decision regarding the response to the request. Means associated with the decision making means for performing automatically. 47. The system of claim 46, wherein said means for storing said data further comprises a virtual wallet application. 48. The system of claim 47, wherein said virtual wallet application further comprises a server-based virtual wallet application. 49. The system of claim 46, wherein said means for receiving said request for stored data transmission further comprises a virtual wallet application. 50. The system of claim 49, wherein said virtual wallet application further comprises a server-based virtual wallet application. 51. The system of claim 50, wherein said means for receiving said request further comprises a terminal in communication with said virtual wallet application. 52. The system of claim 51, wherein said means for receiving said request further comprises said terminal in communication with said website server. 53. The system of claim 46, wherein said means for forming said decision regarding said response to said request further comprises a virtual wallet application. 54. The system of claim 53, wherein said virtual wallet application further comprises a server-based virtual wallet application. 55. The system of claim 46, wherein said means for automatically making said determination regarding said response to said request further comprises a virtual wallet application. 56. The system of claim 55, wherein said virtual wallet application further comprises a server-based virtual wallet application.