Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/166—Editing, e.g. inserting or deleting
  • G06F40/174—Form filling; Merging

Definitions

• the present invention relates generally to computer software for filling out form documents over a computer network. More particularly, the present invention provides a method and system for automatically filling out fields in an electronic form document on a browser program using a remote server.
• a browser program capable of running; one or more windows may utilize a simple process for communicating information among computers over the Internet, as illustrated in FIG. 1.
• an independent Internet user 106 from a pool of random independent Internet users 101-106, opens a browser window 131 in an Internet browser program, depicted by arrow 161.
• User 106 then enters a request for an Internet Web page 144 (i.e. an HTML page) to be downloaded into browser window 131 belonging to user 106.
• User 106's request is processed by the browser program, and a connection, depicted by arrow 162, is made with the appropriate remote Internet resource 112, typically an Interne Web server, selected from a pool of random remote Internet resources 110-112.
• Remote Internet resource 1 12 returns an HTML document 143, depicted by arrow 163.
• HTML document 143 contains substantially the entire content needed to display completed Web page 144.
• Web page 144 is then displayed back to user 106 in browser window 131, depicted by arrow 164.
• Ad server A model known in the art as the "ad server” model advances this simple browser program method for communicating information over the Internet.
• Many Internet Web pages are composite pages, requiring information in the form of images, text, and/or code to be pulled from several different remote Internet resources.
• Ad servers are generally used to integrate directed electronic material, such as banner advertisements, into such composite Internet Web pages.
• banner advertisements are one example of a remote Internet resource that separately contributes material to a composite Web page.
• FIG. 1 A computer network communication process utilizing an ad server is also depicted in FIG. 1.
• Independent Internet user 102 opens a browser window 130 in his or her Internet browser program, depicted by arrow 151. User 102 then enters a request for an Internet Web page 142 to be downloaded into browser window 130. This request is processed by the browser program, and a connection, depicted by arrow 152, is made with the appropriate remote Internet resource 110, typically an Internet Web server. Remote Internet resource 110 returns a core HTML document 140, depicted by arrow 153. Core document 140 contains some displayable content and an additional link to another -J-
• image 141 in this case a banner advertisement, stored at a separate remote Internet resource 120, in this case an ad server.
• the browser program parses core document 140 to find and use this link to retrieve image 141.
• the browser program then makes a connection, depicted by arrow 154, with remote Internet resource 120 to retrieve image 141.
• Remote Internet resource 120 returns image 141 to the browser program, depicted by arrow 155.
• Image 141 is then merged with the displayable content of core document 140 to comprise completed Web page 142.
• Web page 142 is then displayed back to user 102 in browser window 130, depicted by arrow 156. It should be appreciated that this process may be repeated many times for many separate portions of a particular Web page. In fact, many Web pages contain links to dozens of separate remote Internet resources, requiring this process to be repeated for each separate link.
• Cookies a specific user identifier containing state information, referred to as a session identifier or "cookie", to each particular user whenever a user connects to the resource, for example to retrieve an Internet Web page.
• This cookie is deposited into the user's browser program, which is instructed to show the cookie to the resource upon subsequent visits so that the resource can identify the user.
• the cookie conveys to the resource who the user is and what document or component thereof that the user wants.
• Use of these cookies is vital when components are assembled from various remote Internet resources into one integrated Web page, as a resource for a core HTML document may require several visits or communications from a Web browser while a page is assembled. Without such cookies, use of composite Web pages would be substantially hindered.
• cookies are assigned for longer durations for identification purposes beyond one Internet session.
• One such purpose identifies users, through long-term or persistent cookies, to specific user history and preferences, such that information, for example content specific banner advertisements related to such user history and preferences, may be directed at identified users in the future.
• Proxy systems generally group many individual computers and computer users into a single network. This network is typically served by a single proxy server, which serves as a conduit for all communications among individual network users and between any individual network user and any outside remote electronic resource or user.
• a proxy server may provide several useful functions, such as faster communication between network users, firewall protection for all network computers, and large and efficient storage.
• One example of efficient storage by a proxy server occurs when one network user requests a Web page from a remote resource that has recently been retrieved by another network user. Rather than retrieve the same Web page from the same remote resource again, the proxy server may simply deliver the Web page that has been stored on it from the previous request.
• proxy servers alters the path through which information and communication may travel, such use does not substantially alter the basic functions of the methods and systems described herein.
• many methods may be used to assist a user in filling out an electronic form document.
• One such method is referred to as the "wallet” method, which may be found, for example, at "eWallet” located at http://www.ewallet.com.
• This method requires a user to download a software application and install it onto his or her computer. The user is then required to input personal information items into the application, including the user's name, address, and credit card information, which is stored on the user's computer for future use.
• the user is then able to use this "eWallet” application and inputted personal information items to automatically fill out electronic form documents that are affiliated with the "eWallet” application.
• the user opens the "eWallet” application and clicks and drags a virtual credit card from the virtual wallet onto the form document.
• the "eWallet” application then automatically inserts the inputted personal information items into the document.
• the click and drag step must be repeated for each page of the electronic form document.
• the user is then able to review and approve the form document before transmitting it as complete.
• Transactor Another method for assisting a user in filling out an electronic form document is referred to as the "transactor” method, which may be found, for example, at "Transactor Networks" located at http://www.transactor.net.
• This method differs from the wallet method in that the user is not required to download or install any software onto his or her computer. Instead, personal information items are input and stored in a database on a remote server, which is then accessed every time an electronic form document is to be filled. This remote server containing the personal information items is accessed through a browser window separate from the browser window containing the electronic form document to be filled. This method thus requires communication between separate browser windows.
• FIG. 2 A method for filling; out an electronic form document using this transactor method is illustrated in FIG. 2.
• Independent Internet user 202 from a pool of random independent Internet users 201-206, opens a browser window 230 in his or her Internet browser program, depicted by arrow 251. User 202 then enters a request for a Web page containing an electronic form document 240 to be downloaded into browser window 230. This request is processed by the browser program, and a connection, depicted by arrow 252. is made with the appropriate remote Internet resource 210, typically an Internet Web server, selected from a pool of random remote Internet resources 210-212. Remote Internet resource 210 returns an HTML Web page containing electronic form document 240, depicted by arrow 253. This process may include the retrieval of other portions of the Web page from separate remote electronic resources, as described above in the ad server model.
• User 202 also opens another separate browser window 231 to activate the "transactor" process, typically done through a bookmark.
• the browser program then makes a connection, depicted by arrow 255, with transactor server 220 to retrieve the user's personal information items 241.
• Transactor server 220 returns personal information items 241 to the browser program in browser window 231, depicted by arrow 256.
• window 231 initiates communication with window 230 to begin the automated fill of electronic form document 240 in window 230.
• the windows communicate as necessary until form 240 is filled, depicted by double arrow 257.
• Filled electronic form document 242 is then displayed back to user 202 in browser window 230, depicted by arrow 258.
• User 202 is then able to review and approve filled electronic form document 242 before transmitting it as complete.
• both the “wallet” and “transactor” methods require a substantial initial time investment in requiring a user to input all of his or her personal information items.
• the wallet method requires the user to download and install software to his or her computer. This is problematic in that the user has no access to this method when he or she uses any computer that does not have the wallet program installed and the user's personal information items inputted. It is not only inconvenient to re-install and re-input items on every computer for which the user has access, but it is practically impossible for a computer being used by a user for the first time to have the user's personal information items.
• SUMMARY OF THE INVENTION According to the present invention, methods, systems, and computer program products are disclosed for automatically filling in an electronic form on a user computer having a program capable of performing as a browser.
• the present invention alleviates the problem of burdening the user with manually inputting data into an electronic form without requiring the user to have any programs or data stored on a user's computer and without compromising the user's security by having window cross-communication. This is done through the use of a remote personal information server that registers and stores user data and then delivers this user data in an executable code module to any browser where the user may be located.
• the present invention provides a method for automatically filling in an electronic form document.
• This method utilizes a browser to access the electronic form, execute a link to a personal information server, receive a personal information module transmitted from the personal information server, and execute the personal information module to fill in fields in the electronic form with data contained in the module.
• this permits the user to automatically fill in the electronic form without requiring any program or data to be stored on the user's computer and without using window to window communication.
• the electronic form is downloaded from a remote Web server that has already registered the form with the personal information server. Connections between the remote Web server, the user computer, and the personal information server are all made via the Internet.
• execution of the link includes transmitting a session identifier, for example a user cookie, and an electronic form identifier, for example a Uniform Resource Locator, from the browser to the personal information server.
• transmitting the personal information module includes examining negotiation history modules derived for the electronic form and the user. These negotiation history modules preferably include a form mapping corresponding to the electronic form and a raw data profile corresponding to the user. Another embodiment includes transmitting the electronic form after some or all of the fields have been filled in.
• the present invention provides a system for automatically filling in an electronic form.
• This system includes an information server with personal information for multiple registered users and form mappings, a Web server with an electronic form registered with the information server and having an input button, and a user computer having a browser that can download the electronic form and a user that is registered with the information server.
• the information server and user computer communicate over a network to transmit the electronic form, which is then partially or completely filled in when the input button is activated.
• the present invention provides for a computer program product for automatically filling in an electronic form on a user computer having a browser.
• This computer program product contains a computer readable medium which stores computer codes for performing various functions. These functions include accessing the electronic form, executing a link to a personal information server, transmitting a personal information module from the personal information server to the user computer, and executing the personal information module at the user computer to fill in multiple fields in the electronic form.
• FIGURE 1 is a diagrammatical representation of an "ad server” model in accordance with the prior art.
• FIG. 2 is a diagrammatical representation of a transactor model in accordance with the prior art.
• FIG. 3A is a diagrammatical representation of a system for automatically filling in electronic form documents in accordance with one embodiment of the present invention.
• FIG. 3B is a block diagram showing components of a server enabling the automatic insertion of data in to an electronic form on a remote computer in accordance with one embodiment of the present invention.
• FIG. 4 is a flow diagram of a process for automatically filling in an electronic form document in accordance with one embodiment of the present invention.
• FIG. 5 is a flow diagram of a process for an initial user session using the service for automatic electronic form completion in accordance with one embodiment of the present invention.
• FIG. 6 is a flow diagram of a process for constructing and transmitting a shippable code segment from a server to a user computer in accordance with one embodiment of the present invention.
• FIG. 7 is a flow diagram of a process for mapping through which form names are mapped to a user's raw data values in accordance with one embodiment of the present invention.
• FIGS. 8A. 8B, and 8C are table diagrams showing the field names and format of registered user data in accordance with one embodiment of the present invention.
• FIG. 9 is a block diagram of a typical computer system suitable for implementing an embodiment of the present invention.
• a method and system for automatically filling; in electronic forms on a computer and not requiring a user to download or install any resident software on the computer is described in the various figures.
• electronic commerce or e-commerce will grow. More and more consumers will resort to the Internet, for example, to purchase goods and services. This will typically require the consumer/user to provide at least some data to the merchant typically through filling out an electronic form having various fields, most commonly names, addresses, credit card numbers, phone numbers, etc.
• manually filling in these forms repeatedly can become tedious and inefficient.
• the present invention seeks to alleviate the burden of filling in electronic forms, while informing the consumer/user of privacy precautions taken by a particular merchant site, and not require the user to download any resident software.
• Inherent in the latter feature is allowing the consumer to use the processes of the present invention from any computer connected to the network, the Internet in particular.
• the present invention uses a remote server or "privacy bank,” a novel electronic resource that responds to requests for data by preparing and transmitting a specialized document in the form of a JavaScript.
• This JavaScript is formed dynamically by the privacy bank upon receipt of the request for data.
• the JavaScript created by the privacy bank is a "profile" or mapping between field names in a particular form the user needs to fill in at a particular merchant site (e.g. "www.fishermanstore.com”) and standardized field names stored in the privacy bank server. Once the user's browser program is served this profile from privacy bank, most of the fields in the fishermanstore form are automatically filled in.
• the user becomes a member of the privacy bank resource by providing personal information, also referred to as the raw data, to privacy bank once.
• This raw data can be updated from time to time by the user if desired.
• the user can enter privacy rules or requirements once when initially becoming a member. The user does not need to download any software from privacy bank or any other resource.
• the merchant e.g. The Fisherman Store
• the merchant becomes an affiliate member of the privacy bank network by providing a sample document of its form or forms. Privacy bank can then build a mapping between fields in the merchant's form and the standardized fields in its own database.
• FIG. 3A is a block diagram of a system for automatically filling out electronic form documents in accordance with one embodiment of the present invention.
• a number of end-user computers are shown on the right side of the diagram. These computers can be client computers in a network with access to the Internet or be part of an intranet.
• an end user computer 302 is a stand alone computer with access to the Internet and contains an Internet browser program, a browser window for which is shown at 304.
• a particular Web server 306 is a server for a merchant Web site, such as www.fishermanstore.com to which users or consumers can visit to purchase goods online over the Internet.
• a privacy bank server computer 308 On the left side of the diagram is a specialized electronic resource referred to in the described embodiment as a privacy bank server computer 308, also connected to the Internet.
• the process of automatic electronic form completion begins with a user downloading the form from a Web site such as fishermanstore site.
• a process of a user becoming a member and logging into the privacy bank server is described in greater detail in FIG. 5.
• a user/consumer on computer 302 (“user 302") opens a browser window 304 in an Internet browser program such as Netscape Navigator or Internet Explorer, depicted by arrow 310.
• User 302 then goes to www, fishermanstore .com shown by arrow 312 via the browser and decides to purchase goods.
• a purchasing form 316 typically an HTML document, is returned and downloaded into and displayed in browser window 304.
• user 302 would normally have to "manually" fill in each field in purchasing form 316.
• Much of this information is typically standard: name, address, phone number, payment method, user email address, etc.
• user 302 can "click" on a privacy bank icon or button in form 316 and have the form automatically filled in.
• www.fishermanstorc.com is registered with and thus an affiliate member of the privacy bank service assessable from privacy bank server 308.
• purchasing form 316 contains a privacy bank icon or button 318.
• privacy bank icon 318 By clicking on privacy bank icon 318, user 302 essentially completes a process for automatically filling in form 316 by transparently transmitting a completed form to the privacy bank service on server 308, depicted by an arrow 320.
• the information needed for filling in the form is transmitted to user 302 once form 316 (an HTML document) is parsed, which occurs when form 316 is downloaded. This process is described in greater detail in FIG. 4.
• User 302 informs privacy bank server 308 of the identity of the user and of which Web site and which form on that Web site (if more than one) the user wishes to have filled in. This information is transmitted to privacy bank server 308, unbeknownst to user 302.
• privacy bank server 308 receives a request from registered user 302 (by virtue of an external link in form 316 executed when the form is parsed by user 302), it begins preparing information needed to fill in form 316 on user computer 302.
• the information sent to user computer 302 is a JavaScript program 324 referred to as a "profile.”
• this profile contains a mapping of privacy bank standardized fields and fields in purchasing form 316 and "raw,” generally personal, data associated with user 302.
• the filled out purchasing form 316 is displayed to user 302 as depicted by arrow 326. This occurs when user 302 presses or clicks on privacy bank icon 318.
• the information needed to complete form 316 is already resident in the browser program.
• user 302 can decide whether to proceed with submitting the form (typically after filling out a few more fields such as which items to purchase, quantity, etc.) or declining to submit the form, perhaps after reviewing the fishermanstore's Web site privacy safeguards or for any other reason.
• FIG. 3B is a block diagram showing components of a privacy bank server enabling the automatic filling in of electronic forms on a remote user computer.
• a privacy bank server such as server 308 in FIG. 3A, contains several functional and storage components needed for compiling the data needed for filing in a form, such as form 316. Shown in FIG. 3B are four major components of a privacy bank server in the described embodiment. These components and storage areas include a raw data profile storage area 328, a form mapping storage area 330, a negotiation history module 332, and a shippable code constructor 334.
• Raw data profile storage area 328 contains sets of data relating to registered users of the privacy bank service, one set or profile shown in area 336.
• a registered user has a unique account number that can be used as an identifier and a password, shown in an area 338.
• the standard field names set by the privacy bank service discussed in greater detail in FIGS. 8A, 8B, and 8C, are paired with a user entered data string (such as first name or home street address), followed by a use-preference condition.
• the use-preference condition is used in negotiation history module 332 and is discussed in greater detail in FIG. 7 below. This data is contained in an area 340.
• Another profile for another registered user is shown in an area 342. Each registered user has a similar raw data profile.
• Form mapping area 330 includes multiple form mappings, an example of which is shown in an area 344.
• Each electronic form that is registered with the privacy bank service by an online merchant or seller (i.e. an affiliate member) has a form mapping.
• a privacy bank standard field name as discussed below in FIGS. 8A, 8B, and 8C, and as mentioned above in area 340, is matched or mapped with a "non-standard" field name from the electronic form registered with the service.
• a non-standard field name for a person's last name could be "Last Name,” "Surname” or simply "Last.”
• Different forms use different variations of names for this field and for other fields.
• mapping 348 having the same format for another registered form follows area 344.
• negotiation history module 332 is used to determine which fields in the electronic form will be automatically filled in by the privacy bank server.
• a process associated with negotiation history module 332 is described in greater detail in FIG. 7.
• Module 332 includes multiple negotiation objects, an example of which is shown in an area 350.
• each negotiation object corresponds to one "non-standard" field in the form.
• negotiation object 350 contains information as to whether the field in the form should be filled in based on privacy and use preferences set by the user (as conveyed in use-preference condition in area 340) and compared to intended practices (as conveyed by practice-preference condition in area 346). This comparison is performed in the negotiation history module, which includes a negotiator or comparator for comparing these conditions.
• FIG. 4 is a flow diagram of a process for automatically filling in electronic forms in a computer network in accordance with one embodiment of the present invention. The process described below can be performed in a configuration of servers and computers as described in FIG. 3A above.
• an online user/consumer desiring to purchase certain goods on the Internet downloads an electronic form for making a purchase into the user's browser program.
• the browser parses the electronic form content, typically an HTML document, to identify all external links.
• the HTML contains links to other external Web sites from which content or other types of data is retrieved.
• a Web page is a composite of different components from various sites embedded in a core HTML document.
• An example is an external link to an ad server to retrieve a banner ad component of a core HTML document.
• the electronic form can be seen as a core HTML document. This parsing is done automatically by the browser and is a well known feature.
• the browser identifies an external link to the privacy bank server.
• this link will necessarily be present since the Web site is an affiliated site of the privacy bank service network of registered sites. A description of what "registered” implies in this context is described in greater detail below.
• the browser executes the external link to connect the browser to the privacy bank server.
• the external link is referred to in the described embodiment as a shippable code link to the privacy bank server.
• the shippable code in this context is a JavaScript program that is transmitted from the privacy bank server to the user computer and browser.
• shippable code enables the electronic form to be filled in automatically in a process that is described in greater detail below.
• the privacy bank server determines whether the user computer or browser has a valid state identifier, referred to as a "cookie", previously assigned to it by the privacy bank server.
• a cookie is an identifier assigned by a Web site, whether a Web server or a server such as the privacy bank server, to a user/visitor when the user visits the Web site for the first time in a given session (the time from which a user logs onto the Web and the time he or she exits the Web by exiting the browser).
• the cookie, assigned by a Web site belongs to a particular user.
• the user keeps this cookie during its session (a temporary cookie) and if the user goes back to that Web site during that session, it shows the Web site that cookie from which the Web site can identify the user and retrieve characteristics of that user from its data repository.
• cookies can also be permanent in that they subsist with a user after the user has logged off the browser and can be used again in a new session.
• the concept and implementation of cookies themselves are well known in the field of Internet and, more generally, computer network programming. If the privacy bank server determines that the user computer or browser does not have a valid cookie, it implies that the user has not yet logged into the privacy bank service. If so, control goes to step 412 where the privacy bank server retrieves a login sequence code.
• This code will trigger a login sequence and enable the user to log in to or register with the privacy bank service at a later step in the process, as described in greater detail below.
• the privacy bank server forms a completed package of shippable code containing the retrieved login sequence code, such that the login sequence will be triggered at a later step in the process.
• the browser retrieves this completed package of shippable code from the privacy bank server. The shippable code is then stored in the browser residing on the user's computer, and is executable upon a user trigger, which is described in greater detail below.
• step 416 the privacy bank server gets and reads the user's cookie.
• the privacy bank server gets and reads the user's cookie.
• having a valid cookie indicates that the user has already gone through the login sequence recently, for example during the existing Internet session, and thus it is not necessary for the user to go through the login sequence again.
• the privacy bank server can determine who the user is and thus can retrieve the user's raw data stored by privacy bank. The contents and format of this raw personal data is described in greater detail in FIGS. 8A, 8B, and 8C below.
• the privacy bank server retrieves the user data for the user identified by the valid cookie.
• the privacy bank server couples this user data and an identifier, such as a URL (uniform resource locator), to determine how the electronic form document should be filled.
• the privacy bank server forms a completed package of shippable code (item 324 in FIG. 3A) containing the user data that will be used to fill out the form document.
• this shippable code referred to as a profile
• This shippable code is formed from information in the privacy bank memory that will enable the form document to be filled out automatically at a step later in the process.
• the browser receives the shippable code, or profile, from the privacy bank server, and now has access to it on the user computer, if desired by the user.
• This profile is stored in the browser residing on the user's computer, and is executable upon a user trigger.
• this trigger occurs when the user clicks on an "autofill" button contained in the form and associated with privacy bank at step 424. By clicking on the autofill button, the user allows the browser to execute the shippable code or profile stored thereon.
• the shippable code determines whether it contains user data which would permit it to fill out the form document. If user data is contained within the shippable code residing on the browser, control goes to step 434 where the browser utilizes the shippable code and user data to fill out the electronic form document.
• user data being present in the shippable code is dependent upon the browser having a pre-existing valid cookie when the form document was initially retrieved, as described above.
• step 428 the login sequence is initiated in order to identify the presently unknown user.
• the shippable code utilized by the browser in this step contains the login sequence code, which is a result of the browser not having a pre-existing valid cookie when the form document was initially retrieved, as described above.
• the login process of step 428 is described in greater detail in portions of FIG. 5.
• the privacy bank server retrieves the user data for the identified user, couples this user data and an identifier, such as a URL (uniform resource locator), to determine how the electronic form document should be filled, and forms a completed package of shippable code containing the user data that will be used to fill out the form document.
• a URL uniform resource locator
• the browser receives the shippable code, or profile, from the privacy bank server, and now has access to it on the user computer. This shippable code now contains user data that allows the form document to be filled out automatically.
• control proceeds to step 434, where the browser utilizes the shippable code and user data to fill out the electronic form document.
• the user visually examines the filled out form and the privacy features offered by the Web site and decides whether the form is acceptable. If the user finds that the form needs further adjustment, the user adjusts the document at step 438. This may be done manually, or through any supplemental automated process, such as a client-based macro. This can involve filling in fields that could not be filled in by the profile sent by the privacy bank server (in other words, fields that could not be filled out from the raw data). Such fields can include, for example, which items being purchased and the quantity of items. It can also include updated personal information such as a new address or credit card number. In this case, the user simply types over the information already in the fields. Control then returns to step 436, which is satisfied presumably after going through step 438 once.
• the browser submits the filled out electronic form eventually sending it to the merchant's Web server once the user clicks on a Submit form button in the browser window.
• the filled out form is first sent to the privacy bank server unbeknownst to the user or at least transparent to the user.
• the completed form is received and examined by the privacy bank server which updates its raw data repository to reflect any changes the user may have made to his or her personal information.
• the privacy bank server then posts a message back to the user computer (according to HTTP protocol the server must send a message back to the user computer when it receives an HTML document from it).
• the message it sends back or posts to the user's browser is similar to a "Click Here To Continue" type screen to the user.
• Hidden behind this message is the completed form that was sent to the privacy bank server. Presumably, the user will click to continue and by doing so transmits the hidden completed form to the merchant's Web server.
• the completed form is sent to both the privacy bank server and the merchant's Web server at the same time.
• the completed form is posted automatically from the privacy bank server directly to the merchant's site without any additional input from the user. At this stage the automatic form filling process is complete.
• FIG. 5 is a flow diagram of a process for entering new users into the privacy bank service or logging in existing members thereby allowing them to use the service in accordance with one embodiment of the present invention. Portions of FIG. 5 show in greater detail step 428 of FIG. 4 where the login sequence is initiated to identify the user.
• the server determines that the user does not have a valid cookie
• the server inserts a login process for the user into the shippable code, whereby an account may be created if the user does not already have one. This is done because it is assumed that if the user has not yet been assigned a cookie from privacy bank for the user's current session, he or she has not yet logged onto the privacy bank service or is possibly not a registered member.
• the first event that occurs in the login sequence is the privacy bank server displaying a login screen in the user's browser window, as depicted in step 502.
• the user decides whether or not he or she is a privacy bank member, and proceeds to utilize the appropriate section of the login screen.
• One section of the login screen requires the user to input a user identification and password for an existing account, while another section permits the user to select an icon that routes the session to an account creation screen.
• the user selects a "New Account" icon on the login screen, as depicted in step 506.
• a privacy bank account creation screen is then displayed.
• the user enters his or her user identification, a password, name, other information, and high-level privacy preferences into the account creation screen. Essentially the user is configuring the account and personal information items that will be stored for him or her in the privacy bank repository. The information inputted into this newly created account is then posted back to the privacy bank server, as depicted in step 512.
• the privacy bank server accepts the new account information and establishes a location for the new user in the privacy bank repository. The newly inputted information is then recorded in this repository location.
• the privacy bank server sets a cookie for the current user session, as depicted in step 522, and the process ends.
• the user enters his or her existing user identification and password, as depicted in step 516.
• this login information is posted back to the privacy bank server, which then proceeds to evaluate the information.
• the privacy bank server determines whether or not the posted information is correct, that is, whether or not it corresponds to a valid user identification with the proper password. If the posted information does not correspond to a valid user identification and password, then the attempted login fails, and the process reverts to step 502, where a new login screen is displayed. If the posted information is correct, then the login is successful, and the process proceeds to step 522.
• the privacy bank server then sets a cookie for the current user session, as depicted in step 522, and the process ends.
• FIG. 6 is a flow diagram of a process for deriving the parts needed in constructing a shippable code segment or profile to be posted to the user in accordance with one embodiment of the present invention. It describes a process leading up to step 416 of FIG. 4 in which the browser retrieves the shippable code posted from privacy bank in greater detail. Recall that the user's browser parses the electronic form to identify and then execute any links to external resources to obtain external components to the core HTML document. In the case of the privacy bank server (assuming the merchant Web site from which the electronic form is being downloaded is an affiliate member of privacy bank), the server receives and begins to perform operations pursuant to the link from the user.
• the privacy bank server assuming the merchant Web site from which the electronic form is being downloaded is an affiliate member of privacy bank
• the user retrieves two items: the user cookie and the identifier of the electronic form the user presumably wants to fill out.
• the user cookie (assigned to the user by the privacy bank server from when the user logged onto the service) informs the privacy bank server of the identity of the user.
• the identifier of the electronic form contains an identifier of the merchant's Web site, and the specific form on the site that has been downloaded by the user, also in the form of a URL in the described embodiment. In many instances there may only be one form on the Web site.
• the privacy bank server uses the user cookie to retrieve the user's raw data from the privacy bank memory. The configuration and content of the raw data is described in greater detail in FIGS. 8A, 8B, and 8C below.
• the raw data is a set of data items very likely needed to fill out common electronic purchasing forms. As is described in greater detail below, each raw data item corresponds to a particular privacy bank standard label or name.
• the privacy bank server uses the URL or other identifier for the specific form to be filled out to retrieve a mapping of each field name in the electronic forms (i.e. the legacy names) to privacy bank standardized names. This mapping or field name matching is performed when a merchant becomes an affiliate member of the privacy bank service. At that juncture the merchant submits one or more forms to privacy bank which then examines each field name in the forms and matches it with a privacy bank field name.
• the privacy bank user raw data configuration can be updated if it is believed that the particular legacy field name may begin appearing on other forms. Otherwise, it is left for the user to manually fill in as described in step 424 of FIG. 4.
• the server merges the retrieved name map and the user's raw data through a join type operation.
• the merger between two tuples: the legacy name/privacy bank name tuple and the privacy bank name/raw data value tuple is described in greater detail below.
• the outcome of this merger is a series of tuples matching a legacy name with a raw data value associated with the user. In other preferred embodiments this merger can be performed using other data constructs and operations. However, the outcome is a pairing of a legacy field name and a raw data value.
• the series of tuples from the merger is converted to a shippable code.
• the shippable code is in the form of a JavaScript program which is posted to the browser on the user computer.
• FIG. 7 is a flow diagram of a process for mapping through which form names are mapped to a user's raw data values in accordance with one embodiment of the present invention.
• the privacy bank server uses the form URL or other identifier to retrieve a mapping for the form that maps a legacy name with a privacy bank standardized name.
• the mapping also contains one or more practices for each field name, described in greater detail below.
• This mapping is created when a merchant or service provider decides to become an affiliate member of the privacy bank service.
• the merchant tells privacy bank which forms it wants to register and the field names in those forms, which are then paired with privacy bank standardized names.
• the user cookie is used to obtain the user's raw data, which includes actual data values and preferences associated with each data value.
• the practices mentioned above associated with legacy names and the preferences associated with user raw data values are stated in terms of conditions. In the described embodiment, there are various conditions, such as marketing (targeted), system administration, personalization, research and development, and completion of activity (i.e. ordering). Other embodiments can more or fewer conditions.
• a merchant When a merchant registers with the privacy bank service, it must state what conditions for which it will use each legacy field. For example, for the field "Last Name” it may state that its practice will be to use this field for “personalization” and “completion of activity,” and nothing else. For a “Method of Payment” field, it may state that its practice will be to use this field for “completion of activity,” “research and development,” and “administration” only. In this manner, the merchant will build a list of (legacy field name, practice) pairs stored in the privacy bank server. Similarly, when a user becomes a member of the privacy bank service, he or she is required to provide the raw data values (specific fields for the raw data are described below) and corresponding preferences, also stated in terms of conditions.
• preferences because from the user's point of view they indicate a privacy or use threshold. For example, a user can require that her last name can only be used for "personalization,” “completion of activity,” and “system administration,” thereby excluding its use for targeted "marketing” for example. In the described embodiment, if a user does not specify a preference condition, the data item is not to be released, such as a social security number or a mother's maiden name.
• the privacy bank server retrieves a single (legacy name, practice) pair and its corresponding standardized privacy bank name from the form mapping retrieved at step 702. In the described embodiment, this pair can be the first form field in the merchant's online form.
• the server retrieves a corresponding (standardized privacy bank name, preference) pair from the user's raw data "file.” The privacy bank name in this pair should match the privacy bank name in the pair retrieved at step 706: [(legacy name, practice), PB NamelJ: [PB Namel, preference]
• the privacy bank server compares the merchant's practice conditions on the left with the user's preference conditions on the right.
• the merchant has specified that its practice is to use this data item for the conditions “personalization” and “completion of activity.”
• the user has specified she will only allow her last came to be used for the conditions “personalization,” “completion of activity,” and “system administration.”
• the merchant's conditions and the user's conditions are compared.
• the privacy bank server determines whether the merchant's form field should be filled in taking into account the user's privacy threshold for that field. In the described embodiment this is done by determining whether the user's preference conditions is a superset of the merchant's practice conditions. That is. does the merchant intend to use the user's last name for anything other than what the user has specified.
• the user's preferences is a superset of the merchant's practices: "personalization,” “completion of activity,” and “system administration” includes at least all of "personalization” and "completion of activity.”
• a message is displayed to the user indicating that the field will not be automatically filled in because the merchant may use that information in ways the user has not authorized.
• the user has the option to fill in the field manually and have the privacy bank service proceed with the remaining fields.
• Steps 710 and 712 can be seen as a two-step negotiation process.
• the merchant form seen as an "information buyer,” makes a proposal to the user, the "information seller.”
• the proposal is essentially in the form of what data item the information buyer wants and what he intends to use it for.
• the user gets the proposal and checks whether the merchant's conditions exceed what the user's preferences. In other words, the user checks whether the merchant intends to use the data item for purposes not specifically allowed by the user.
• step 712 If the merchant's practice conditions are acceptable (by performing the superset test in step 712), the user sends an acceptance to the merchant, at which point the raw data value is retrieved and associated with the legacy field. If the merchant's conditions are not acceptable, the user essentially sends a "not accepted" message to the merchant through the negotiator without a raw data value. This completes the second step in the negotiation process.
• Each two-step negotiation is viewed as an object which is later used to construct a JavaScript program (the shippable code) using standard Java programming techniques.
• the server checks whether there are any other (legacy name, practice) pairs in the merchant's form. If there are more legacy fields, control returns to step 706 and the process repeats.
• the process is complete.
• a series of objects or a history of negotiations that has been derived from the mapping process.
• These series of objects are then used to construct a JavaScript program.
• all the objects will have an acceptance from the user and thus a raw data value attached which is included in the JavaScript profile sent over to the browser/user.
• some of the objects can have a "not accepted” or declined message indicating that a particular field in the form will not be filled in and thus will not have a raw data value.
• the shippable code or profile sent to the user represents a series of (legacy field name, raw data value) pairs without any reference to preferences or practices, all the negotiations for the data values having been performed on the privacy bank server.
• FIG. 8 is a high-level table diagram showing how fields containing the raw data and preferences for a user are organized on the privacy bank server in accordance with one embodiment of the present invention.
• a top-level User table 802 has four columns: User 804, Category 806, Type 808, and Short display name 810.
• User Table 802 has four areas of data under column User 804 represented by four rows: Home 812, Work 814, Billing 816, and Shipping 818.
• the user is presented with these four areas of data when registering with the privacy bank service and enters information by going through each of these data areas.
• Skipping Category 806 for the moment, column Type 808 takes the raw data tree down one level from the top level represented by table 802. For example, the Type for data area Home 812 is Info.
• the first column 822 of table 820 is labeled Info but the other three columns are the same as shown in table 802; that is, Category 806, Type 808, and Short display name 810.
• the user begins entering data that will be used for her home information and for Shipping since data area 818 for Shipping in table 802 also has an Info in its Type column 808.
• a Name row 822 has in its Type column 808 a reference to yet another table PersonName, shown as table 824. Similar to table 802 and 820, PersonName table 824 has a first column labeled PersonName and the same three columns as the other tables.
• Text represents a data string that is the actual data item stored in the privacy bank server.
• Type column 808 of each of the data areas a user enters all the raw personal data. An actual data item is entered at each Type box containing Text, indicating a primitive type, or a leaf node when viewed as a tree structure. If the Type column does not contain "Text," another table exists that refines the data area further.
• Type 808 indicates Billlnfo and not Text.
• a table Billlnfo has six further data areas, none of which have a Text Type, so no actual data values can be found at this level.
• CreditCard shown in FIG. 8C, has four data areas: Type, Number, ExpMonth, and ExpYear. all of which are of Type Text, which contain actual data values.
• Short display name column 810 contains a string that is displayed to the user through a user registration graphical user interface of the described embodiment. The user follows the data tree via a user interface using the Short display name strings as field names or guides to entering the data.
• the data areas that have primitive Types, which in the described embodiment is Text are the privacy bank field names that are mapped with the legacy field names in the electronic forms registered with the service.
• the privacy bank names include (in abbreviated form):
• Category column 806 is related to privacy settings set by the user and are tied to the preferences set by a user and defined in terms of the conditions as described above, specifically in FIG. 7.
• the conditions or use thresholds in the described embodiment are marketing (targeted), system administration, personalization, research and development, and completion of activity (i.e. ordering).
• the Categories available in the described embodiment and as shown in the tables of FIGS. 8A, 8B, and 8C, are Physical Contact Information, Online Contact Information, Demographic Data, and Financial Data.
• the relationship between the Categories and the conditions of the described embodiment can be described as a table five-row, four-column table (a 20 cell table) where each condition is one row in the table and each Category is one column in the table.
• the present invention employs various computer-implemented operations involving data stored in computer systems. These operations include, but are not limited to, those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated.
• the operations described herein that form part of the invention are useful machine operations.
• the manipulations performed are often referred to in terms, such as, producing, identifying, running, determining, comparing, executing, downloading, or detecting. It is sometimes convenient, principally for reasons of common usage, to refer to these electrical or magnetic signals as bits, values, elements, variables, characters, data, or the like. It should remembered, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
• the present invention also relates to a device, system or apparatus for performing the aforementioned operations.
• the system may be specially constructed for the required purposes, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer.
• the processes presented above are not inherently related to any particular computer or other computing apparatus.
• various general purpose computers may be used with programs written in accordance with the teachings herein, or, alternatively, it may be more convenient to construct a more specialized computer system to perform the required operations.
• FIG. 9 is a block diagram of a general purpose computer system 900 suitable for carrying out the processing in accordance with one embodiment of the present invention.
• FIG. 9 illustrates one embodiment of a general purpose computer system such as user computer 302 of FIG. 3 A and also describes many components found in privacy bank server 308.
• Computer system 900 made up of various subsystems described below, includes at least one microprocessor subsystem (also referred to as a central processing unit, or CPU) 902. That is, CPU 902 can be implemented by a single-chip processor or by multiple processors.
• CPU 902 is a general purpose digital processor which controls the operation of the computer system 900. Using instructions retrieved from memory, the CPU 902 controls the reception and manipulation of input data, and the output and display of data on output devices.
• CPU 902 is coupled bi-directionally with a first primary storage 904, typically a random access memory (RAM), and uni-directionally with a second primary storage area 906, typically a read-only memory (ROM), via a memory bus 908.
• primary storage 904 can be used as a general storage area and as scratch-pad memory, and can also he used to store input data and processed data. It can also store programming instructions and data, in the form of data objects or JavaScript programs, for example, in addition to other data and instructions for processes operating on CPU 902, and is used typically used for fast transfer of data and instructions in a bi-directional manner over the memory bus 908.
• primary storage 906 typically includes basic operating instructions, program code, data and objects used by the CPU 902 to perform its functions.
• Primary storage devices 904 and 906 may include any suitable computer-readable storage media, described below, depending on whether, for example, data access needs to be bi-directional or uni-directional.
• CPU 902 can also directly and very rapidly retrieve and store frequently needed data in a cache memory 910.
• a removable mass storage device 912 provides additional data storage capacity for the computer system 900, and is coupled either bi-directionally or uni-directionally to CPU 902 via a peripheral bus 914.
• a specific removable mass storage device commonly known as a CD-ROM typically passes data uni-directionally to the CPU 902, whereas a floppy disk can pass data bi-directionally to the CPU 902.
• Storage 912 may also include computer-readable media such as magnetic tape, flash memory, signals embodied on a carrier wave, PC-CARDS, portable mass storage devices, holographic storage devices, and other storage devices.
• a fixed mass storage 916 also provides additional data storage capacity and is coupled bi-directionally to CPU 902 via peripheral bus 914.
• the most common example of mass storage 916 is a hard disk drive. Generally, access to these media is slower than access to primary storages 904 and 906.
• Mass storage 912 and 916 generally store additional programming instructions, data, and the like that typically are not in active use by the CPU 902. It will be appreciated that the information retained within mass storage 912 and 916 may be incorporated, if needed, in standard fashion as part of primary storage 904 (e.g. RAM) as virtual memory.
• primary storage 904 e.g. RAM
• peripheral bus 914 is used to provide access other subsystems and devices as well.
• these include a display monitor 918 and adapter 920, a printer device 922, a network interface 924, an auxiliary input/output device interface 926, a sound card 928 and speakers 930, and other subsystems as needed.
• the network interface 924 allows CPU 902 to be coupled to another computer, computer network, or telecommunications network using a network connection as shown. Through the network interface 924, it is contemplated that the CPU 902 might receive information, e.g., data objects or program instructions, from another network, or might output information to another network in the course of performing the above-described method steps. Information, often represented as a sequence of instructions to be executed on a CPU, may be received from and outputted to another network, for example, in the form of a computer data signal embodied in a carrier wave. An interface card or similar device and appropriate software implemented by CPU 902 can be used to connect the computer system 900 to an external network and transfer data according to standard protocols.
• method embodiments of the present invention may execute solely upon CPU 902, or may be performed across a network such as the Internet, intranet networks; or local area networks, in conjunction with a remote CPU that shares a portion of the processing.
• Additional mass storage devices may also be connected to CPU 902 through network interface 924.
• Auxiliary I/O device interface 926 represents general and customized interfaces that allow the CPU 902 to send and, more typically, receive data from other devices such as microphones, touch-sensitive displays, transducer card readers, tape readers, voice or handwriting recognizers, biometrics readers, cameras, portable mass storage devices, and other computers.
• a keyboard controller 932 is Also coupled to the CPU 902 is a keyboard controller 932 via a local bus 934 for receiving input from a keyboard 936 or a pointer device 938, and sending decoded symbols from the keyboard 936 or pointer device 938 to the CPU 902.
• the pointer device may be a mouse, stylus, track ball, or tablet, and is useful for interacting with a graphical user interface.
• embodiments of the present invention further relate to computer storage products with a computer readable medium that contain program code for performing various computer-implemented operations.
• the computer-readable medium is any data storage device that can store data which can thereafter be read by a computer system.
• the media and program code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known to those of ordinary skill in the computer software arts.
• Examples of computer-readable media include, but are not limited to, all the media mentioned above: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and specialty configured hardware devices such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs), and ROM and RAM devices.
• the computer-readable medium can also be distributed as a data signal embodied in a carrier wave over a network of coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion.
• Examples of program code include both machine code, as produced, for example, by a compiler, or files containing higher level code that may be executed using an interpreter.
• FIG. 9 is but an example of a computer system suitable for use with the invention. Other computer architectures having different configurations of subsystems may also be utilized.
• the raw data can contain more or few fields than those described as needed, and there can be additional privacy or use threshold conditions than the five described.
• the filled out electronic form can be sent automatically to the merchant's Web server after the privacy bank server updates its raw data without additional input from the user.
• the raw data and legacy fields can be bundled and coded in a software module other than as a JavaScript module. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Business, Economics & Management (AREA)
• Physics & Mathematics (AREA)
• Accounting & Taxation (AREA)
• Finance (AREA)
• Databases & Information Systems (AREA)
• General Engineering & Computer Science (AREA)
• Strategic Management (AREA)
• General Health & Medical Sciences (AREA)
• Marketing (AREA)
• Health & Medical Sciences (AREA)
• Artificial Intelligence (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Computational Linguistics (AREA)
• General Business, Economics & Management (AREA)
• Economics (AREA)
• Development Economics (AREA)
• Data Mining & Analysis (AREA)
• Information Transfer Between Computers (AREA)
• Computer And Data Communications (AREA)
• Stored Programmes (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (2)

Family

ID=22868420

Family Applications (1)

Country Status (5)

Cited By (12)

Citations (1)

• 2000
  • 2000-01-14 JP JP2000594047A patent/JP2002535754A/ja active Pending
  • 2000-01-14 EP EP00902426A patent/EP1159695A2/en not_active Withdrawn
  • 2000-01-14 WO PCT/US2000/001031 patent/WO2000042540A2/en not_active Application Discontinuation
  • 2000-01-14 BR BR0007517-5A patent/BR0007517A/pt not_active Application Discontinuation
  • 2000-01-14 AU AU24145/00A patent/AU2414500A/en not_active Abandoned

Patent Citations (1)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events