Method and system for completing forms on wide area networks such as the internet

• US 20020062342A1
• Filed: 10/16/2001
• Published: 05/23/2002
• Est. Priority Date: 11/22/2000
• Status: Abandoned Application

• Current Assignee: Faspay Technologies Incorporated
• Original Assignee: Faspay Technologies Incorporated
• Inventors: Sidles, Charles S.
• Application Number:
  US09/978,563
• Publication Number:
  US 20020062342A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

A system automatically intercepts and responds to most requests for personal information that are received from a network and directed to a user. Such requests are intercepted, and the sources of the requests, as well as the user, are validated. The system attempts to complete each request, using information obtained from a wallet database where information is kept secure and is associated with non-personal identifiers. The system attempts to complete requests by searching a dictionary database for request-type-specific rules that indicate, by non-personal identifiers, what personal information is to be entered into which fields of each request or form. The system may also attempt to complete requests or forms using rules for other types of requests that are applied to a new type of request using the principles of fuzzy logic or artificial intelligence. The system also includes a history database where previously user-validated requests are kept with personal information replaced with non-personal field identifiers, and it may attempt to complete requests by reference to requests in this history database. After a form is completed either by the system with user validation, or by the user, it may be kept in the history database, and new rules may be derived either through the use of fuzzy logic or artificial intelligence or study of the requests in the history database. These new rules may be added to the dictionary database. The fuzzy logic or artificial intelligence system may also be given positive or negative feedback.

Claims

1. A system for complying with requests for information received from a network and directed to a user, said system comprising:

a data flow monitor interposed between the network and the user that intercepts such requests;

a wallet database where personal information of one or more users is kept in a secure manner and is associated with non-personal identifiers;

a history database containing at least some previously-completed and user-validated requests in which at least some of the personal information is replaced by the non-personal identifiers to at least partly depersonalize the requests;

a request completion system coupled directly or indirectly to the above elements that accepts such requests, that attempts to fulfill such requests using information obtained from the wallet database through the use of history database records of one or more previously completed, validated copies of the same type of request, and also through asking the user to complete all or those portions of requests not automatically completed and to validate all or those portions of requests automatically completed;

said request completion system further including a completed request analysis engine that can add completed, user verified, and at least partly depersonalized requests to the history database.

2. A system in accordance with claim 1 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in particular types of requests;

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database specifically applicable to a particular type of request.

3. A system in accordance with claim 2

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through history database request analysis and user validation with respect to a particular type of request, thereby developing from the history database new rules for inclusion in the dictionary database.

4. A system in accordance with claim 3

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic or artificial intelligence techniques.

5. A system in accordance with claim 4

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic or artificial intelligence analysis of existing rules, and this engine also can give positive or negative training feedback to the fuzzy logic or artificial intelligence system in accordance with its performance as accepted or corrected by users.

6. A system in accordance with claim 5 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

7. A system in accordance with claim 6

wherein the validation program also determines and validates the user'"'"'s identification.

8. A system in accordance with claim 1 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in requests;

and wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic or artificial intelligence techniques.

9. A system in accordance with claim 8

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic or artificial intelligence analysis of existing rules and history database request analysis, and this engine also can give positive or negative training feedback to the fuzzy logic or artificial intelligence system in accordance with its performance as accepted or corrected by users.

10. A system in accordance with claim 9 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

11. A system in accordance with claim 10

wherein the validation program also determines and validates the user'"'"'s identification.

13. A method in accordance with claim 12 additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within specific types of requests;

and

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applicable to a particular type of request.

14. A method in accordance with claim 13, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through history database record analysis techniques and adding them to the dictionary database.

15. A method in accordance with claim 14, additionally comprising the step of

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic or artificial intelligence techniques.

16. A method in accordance with claim 15, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through fuzzy logic or artificial intelligence techniques and adding them to the dictionary database, and to give positive or negative feedback to the fuzzy logic or artificial intelligence system in accordance with its performance.

17. A method in accordance with claim 16, additionally comprising the step of

validating the source of the request.

18. a method in accordance with claim 17, additionally comprising the step of

validating the user'"'"'s identification.

19. A method in accordance with claim 12, additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within requests;

and

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic or artificial intelligence techniques.

20. A method in accordance with claim 19, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through fuzzy logic or artificial intelligence techniques and adding them to the dictionary database, and to give positive or negative feedback to the fuzzy logic system in accordance with its performance.

21. A method in accordance with claim 20, additionally comprising the step of

validating the source of the request.

22. a method in accordance with claim 21, additionally comprising the step of

validating the user'"'"'s identification.

24. A system in accordance with claim 23 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in particular types of requests;

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database specifically applicable to a particular type of request.

25. A system in accordance with claim 24

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through history database request analysis with respect to a particular type of request, thereby developing from the history database new rules for inclusion in the dictionary database.

26. A system in accordance with claim 25

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

27. A system in accordance with claim 26

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic analysis of existing rules, and this engine also can give positive or negative training feedback to the fuzzy logic system in accordance with its performance.

28. A system in accordance with claim 27 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

29. A system in accordance with claim 28

wherein the validation program also determines and validates the user'"'"'s identification.

30. A system in accordance with claim 23 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in requests;

and wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

31. A system in accordance with claim 30

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic analysis of existing rules and history database request analysis, and this engine also can give positive or negative training feedback to the fuzzy logic system in accordance with its performance.

32. A system in accordance with claim 31 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

33. A system in accordance with claim 32

wherein the validation program also determines and validates the user'"'"'s identification.

35. A method in accordance with claim 34 additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within specific types of requests;

and

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applicable to a particular type of request.

36. A method in accordance with claim 35, additionally comprising the step of

adding new rules developed through history database record analysis techniques to the dictionary database.

37. A method in accordance with claim 36, additionally comprising the step of

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

38. A method in accordance with claim 37, additionally comprising the step of

adding any new rules developed through fuzzy logic techniques to the dictionary database, and giving positive or negative feedback to the fuzzy logic system in accordance with its performance.

39. A method in accordance with claim 38, additionally comprising the step of

validating the source of the request.

40. a method in accordance with claim 39, additionally comprising the step of

validating the user'"'"'s identification.

41. A method in accordance with claim 34, additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within requests;

and

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

42. A method in accordance with claim 41, additionally comprising the step of

adding any new rules developed through fuzzy logic techniques to the dictionary database, and giving positive or negative feedback to the fuzzy logic system in accordance with its performance.

43. A method in accordance with claim 42, additionally comprising the step of

validating the source of the request.

44. a method in accordance with claim 43, additionally comprising the step of

validating the user'"'"'s identification.

46. A system in accordance with claim 45 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in particular types of requests;

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet system through the use of rules obtained from the dictionary database specifically applicable to a particular type of request.

47. A system in accordance with claim 46

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through history database request analysis and user validation with respect to a particular type of request, thereby developing from the history database new rules for inclusion in the dictionary database.

48. A system in accordance with claim 47

wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet system through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

49. A system in accordance with claim 48

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic analysis of existing rules, and this engine also can give positive or negative training feedback to the fuzzy logic system in accordance with its performance as accepted or corrected by users.

50. A system in accordance with claim 49 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

51. A system in accordance with claim 50

wherein the validation program also determines and validates the user'"'"'s identification.

52. A system in accordance with claim 45 to which is added

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in requests;

and wherein the request completion system also attempts to fulfill such requests using information obtained from the wallet system through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

53. A system in accordance with claim 52

wherein the request completion system'"'"'s completed request analysis engine also validates new sets of rules developed through fuzzy logic analysis of existing rules and history database request analysis, and this engine also can give positive or negative training feedback to the fuzzy logic system in accordance with its performance as accepted or corrected by users.

54. A system in accordance with claim 53 which further includes

a validation program coupled to the data flow monitor that determines and validates the source of the request.

55. A system in accordance with claim 54

wherein the validation program also determines and validates the user'"'"'s identification.

57. A method in accordance with claim 56 additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within specific types of requests;

and

attempting to complete such requests using the personal information through the use of rules obtained from the dictionary database applicable to a particular type of request.

58. A method in accordance with claim 57, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through history database record analysis techniques and adding them to the dictionary database.

59. A method in accordance with claim 58, additionally comprising the step of

attempting to complete such requests using the personal information through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

60. A method in accordance with claim 59, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through fuzzy logic techniques and adding them to the dictionary database, and to give positive or negative feedback to the fuzzy logic system in accordance with its performance.

61. A method in accordance with claim 60, additionally comprising the step of

validating the source of the request.

62. a method in accordance with claim 61, additionally comprising the step of

validating the user'"'"'s identification.

63. A method in accordance with claim 56, additionally comprising the steps of

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within requests;

and

attempting to complete such requests using the personal information through the use of rules obtained from the dictionary database applied using fuzzy logic techniques.

64. A method in accordance with claim 63, additionally comprising the step of

following user review and validation or completion or correction of a request, analyzing any changes made by the user to validate any new rules developed through fuzzy logic techniques and adding them to the dictionary database, and to give positive or negative feedback to the fuzzy logic system in accordance with its performance.

65. A method in accordance with claim 64, additionally comprising the step of

validating the source of the request.

66. a method in accordance with claim 65, additionally comprising the step of

validating the user'"'"'s identification.

70. A system in accordance with claim 69 to which is added

a dictionary database containing field names associated with certain form components that are used to populate the forms;

and wherein the request completion system also attempts to complete such through the use of field names found in the dictionary database that match field names in the form.

71. A system in accordance with claim 70

wherein the form fill system extracts rules from previously completed forms in the history database, thereby developing from the history database rules for filling in forms.

72. A system in accordance with claim 71

wherein the form fill system also attempts to fill in forms using personal information through the use of information in the dictionary database and fuzzy logic techniques.

73. A system in accordance with claim 72 to which is added

a dictionary database containing field names associated with certain form components that are used to populate the forms;

and wherein the form fill system also attempts to complete such forms through the use of field names found in the dictionary database applied using fuzzy logic techniques.

74. A system in accordance with claim 73

wherein the form fill system extracts rules from previously completed forms in the history database, thereby developing from the history database rules for filling in forms.

12. A method for automatically complying with requests for information received from a network and directed to a user comprising the steps of:

establishing a wallet database where user information can be kept secure and can be associated with non-personal identifiers;

establishing a history database where user validated, completed requests may be kept with at least some personal information replaced by non-personal identifiers to at least partly depersonalize the requests;

monitoring the flow of data between the network and the user and intercepting such requests for information;

attempting to complete such requests using information obtained from the wallet database through the use of history database records of one or more completed, validated copies of the same type of request, and through asking the user to complete all or those portions of a request not automatically completed and to validate all or those portions of a request automatically completed; and

following user review and validation or completion or correction of a completed request, analyzing any changes made by the user to add completed, user verified, and depersonalized requests to the history data base.

23. A system for complying with requests for information received from a network and directed to a user, said system comprising:

a data flow monitor interposed between the network and the user that intercepts such requests;

a wallet database where personal information of one or more users is kept in a secure manner and is associated with non-personal identifiers;

a history database containing at least some previously-completed and user-validated requests in which at least some of the personal information is replaced by the non-personal identifiers to at least partly depersonalize the requests;

a request completion system coupled directly or indirectly to the above elements that accepts such requests, and that attempts to fulfill such requests using information obtained from the wallet database through the use of history database records of one or more previously completed, validated copies of the same type of request;

said request completion system further including a completed request analysis engine that can add completed and at least partly depersonalized requests to the history database.

34. A method for automatically complying with requests for information received from a network and directed to a user comprising the steps of:

establishing a wallet database where user information can be kept secure and can be associated with non-personal identifiers;

establishing a history database where user validated, completed requests may be kept with at least some personal information replaced by non-personal identifiers to at least partly depersonalize the requests;

monitoring the flow of data between the network and the user and intercepting such requests for information;

attempting to complete such requests using information obtained from the wallet database through the use of history database records of one or more completed, validated copies of the same type of request; and

adding completed and depersonalized requests to the history data base.

45. A system for complying with requests for information received from a network and directed to a user using personal information obtained from a suitable source, said system comprising:

a data flow monitor interposed between the network and the user that intercepts such requests;

a wallet system that, on receipt of a non-personal identifier, can obtain corresponding personal information of one or more users;

a history database containing at least some previously-completed and user-validated requests in which at least some of the personal information is replaced by the non-personal identifiers to at least partly depersonalize the requests;

a request completion system coupled directly or indirectly to the above elements that accepts such requests, that attempts to fulfill such requests using information obtained from the wallet system through the use of history database records of one or more previously completed, validated copies of the same type of request, and also through asking the user to complete all or those portions of requests not automatically completed and to validate all or those portions of requests automatically completed;

said request completion system further including a completed request analysis engine that can add completed, user verified, and at least partly depersonalized requests to the history database.

56. A method for automatically complying with requests for information received from a network and directed to a user using personal information comprising the steps of:

establishing a history database where user validated, completed requests may be kept with at least some personal information replaced by non-personal identifiers to at least partly depersonalize the requests;

monitoring the flow of data between the network and the user and intercepting such requests for information;

attempting to complete such requests using the personal information through the use of history database records of one or more completed, validated copies of the same type of request, and through asking the user to complete all or those portions of a request not automatically completed and to validate all or those portions of a request automatically completed; and

following user review and validation or completion or correction of a completed request, analyzing any changes made by the user to add completed, user verified, and depersonalized requests to the history data base.

67. A system for automatically complying with requests for information received from a network and directed to a user'"'"'s browser, comprising:

a data flow monitor interposed between the network and the user'"'"'s browser that intercepts such requests;

a validation program coupled to the data flow monitor that determines and validates the user'"'"'s identification and that validates the source of the request;

a wallet database where personal information of one or more users is kept in a secure manner and is associated with non-personal identifiers;

a dictionary database containing rules governing what information, identified by non-personal identifiers, goes where in particular types of requests;

a history database containing at least some previously-completed and user-validated requests in which at least some personal information is replaced by the non-personal identifiers to at least partly depersonalize the requests;

a request completion system coupled directly or indirectly to the above elements that accepts such requests, that attempts to fulfill such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database specifically applicable to that particular type of request, through the use of other rules obtained from the dictionary database applied using fuzzy logic techniques, through the use of history database records of one or more previously completed, validated copies of the same type of request, and through asking the user to complete all or those portions of a request not automatically completed and to validate all or those portions of a request automatically completed;

said request completion system further including a completed request analysis engine that validates new sets of rules developed through fuzzy logic analysis of existing rules or through history database request analysis and through user validation with respect to a particular type of request, that gives positive or negative training feedback to the fuzzy logic system in accordance with its performance as accepted or corrected by users, and that can add completed, user verified, and at least partly depersonalized requests to the history database.

68. A method for automatically complying with requests for information received from a network and directed to a user comprising the steps of:

establishing a wallet database where user information can be kept secure and can be associated with non-personal identifiers;

establishing a history database where at least some previously-completed and user-validated requests may be kept with at least some personal information replaced by non-personal identifiers to at least partly depersonalize the requests;

establishing a dictionary database containing rules associating non-personal identifiers with specific data fields within specific types of requests;

monitoring the flow of all data flowing between the network and the user and intercepting such requests for information;

validating the user'"'"'s identification, and validating the source of the request;

attempting to complete such requests using information obtained from the wallet database through the use of rules obtained from the dictionary database specifically applicable to a particular type of request, through the use of rules obtained from the dictionary database applied using fuzzy logic techniques, through the analysis of history database records of one or more completed, validated copies of the same type of request, and through asking the user to complete all or those portions of a request not automatically completed and to validate all or those portions of a request automatically completed; and

following user review and validation or completion or correction of a completed request, analyzing any changes made by the user to validate any new rules developed through fuzzy logic or history database analysis techniques and adding them to the dictionary database, also to give positive or negative feedback to the fuzzy logic system in accordance with its performance, and also to add completed, user verified, and depersonalized requests to the history database.

69. A system for completing forms requesting personal information received from a network and directed to a user, said system comprising:

a data flow monitor interposed between the network and the user that intercepts such forms;

a history database containing at least some previously-completed forms;

a form fill system coupled directly or indirectly to the above elements that accepts such forms, that attempts to complete such forms using personal information through the use of history database records of one or more previously completed copies of the same form and also through asking the user to complete at least portions of forms not automatically completed;

said data flow monitor intercepting what the user fills in and sending it to the form fill system which writes it to the history database.

75. A method for automatically filling in forms received from a network and directed to a user with personal information, comprising the steps of:

establishing a history database where at least some previously completed forms may be kept;

monitoring the flow of data between the network and the user and intercepting such forms requesting information;

attempting to complete such forms with personal information through the use of history database records of one or more completed copies of the same form, and through asking the user to complete at least some portions of forms not automatically completed;

and intercepting what the user fills in and writing it to the history data base for future use.

76. A method in accordance with claim 75 additionally comprising the steps of

establishing a dictionary incorporating a series of names associated with certain form components that may be used to populate forms;

and

attempting to complete such forms with personal information through the use the dictionary information applicable to a particular form.

77. A method in accordance with claim 76, additionally comprising the step of

intercepting what the user fills in to a form and adding it to the history database for future use.

78. A method in accordance with claim 77, additionally comprising the step of

attempting to fill in forms with personal information through the use fuzzy logic techniques applied to information obtained from the dictionary.

79. A method in accordance with claim 75, additionally comprising the steps of

establishing a dictionary incorporating a series of names associated with certain form components that may be used to populate forms;

and

attempting to complete forms with personal information through the use of information obtained from the dictionary applied using fuzzy logic techniques.

80. A method in accordance with claim 79, additionally comprising the step of intercepting what the user fills in and adding it to the history database for future use.