System and method for message handling

• US 20050131811A1
• Filed: 01/29/2004
• Published: 06/16/2005
• Est. Priority Date: 02/10/2000
• Status: Abandoned Application

• Current Assignee: JOVE Enterprise Limited
• Original Assignee: JOVE Enterprise Limited
• Inventors: Weideman, Chris, Ranzini, Stephen Lange
• Application Number:
  US10/769,084
• Publication Number:
  US 20050131811A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/023 the neutral party being a clearing house
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/06 Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]

Abstract

Systems and methods employable, for example, in the handling of various electronically-dispatched messages, fiber-optic or light based messages, wireless based messages, and/or the like. According to various such systems and methods, in the case where a dispatched message is, for instance, found to be inadequate, undesirable, and/or not wanted or the like in some way, an entity receiving the message and/or one or more entities associated with the recipient entity may, for example, come to possess all or some of funds required by network rules, database rules, file based rules, message based rules, in memory based rules, computer program based rules and/or the like to be made available for possession by the sender (either directly or indirectly) of the message in association with the message.

Claims

1. A method for message handling, comprising:

determining if funds made available in association with a received message represent a sufficient amount of funds; and

determining if said finds made available in association with said received message should be possessed,

wherein said funds are possessed in the case where said message is found to be an undesirable message.

2. The method of claim 1, wherein said undesirable message is a spam email message.

3. The method of claim 1, wherein said undesirable message is an enterprise resource planning message possessing one or more inadequacies.

4. The method of claim 1, wherein said undesirable message is a web services message possessing one or more inadequacies.

5. The method of claim 1, wherein said sufficient amount is an established amount for all received messages.

6. The method of claim 1, wherein said sufficient amount is an established amount for all received messages of a particular type.

7. The method of claim 1, wherein said sufficient amount is dependent upon one or more properties of said message.

8. The method of claim 1, wherein said sufficient amount is a user defined amount.

9. The method of claim 7, wherein said properties suggest said message is a spam email message.

10. The method of claim 7, wherein said properties suggest said message would require an undue amount of processing by a recipient of said message.

11. The method of claim 1, wherein said message is an email message.

12. The method of claim 1, wherein said message is an enterprise resource planning message.

13. The method of claim 1, wherein said message is a web services message.

14. The method of claim 1, further comprising providing to an originator of said message an indication that insufficient finds were made available in association with said message.

15. The method of claim 14, wherein said indication is provided as an email message.

16. The method of claim 14, wherein said indication is provided as an enterprise resource planning message.

17. The method of claim 14, wherein said indication is provided via a bounce of said message.

18. The method of claim 1, wherein a digital rights management container containing a digital representation of money is employed.

19. The method of claim 1, wherein micropayments are employed.

20. The method of claim 1, wherein Financial Services Technology Consortium'"'"'s universal value exchange standard is employed.

21. A method for message handling, comprising:

determining, for a message to be dispatched, an amount of funds to be made available in association with said message;

receiving an indication that insufficient finds were made available in association with said message; and

making a sufficient amount of funds available in association with said message.

22. The method of claim 21, wherein said sufficient amount is an established amount for all dispatched messages.

23. The method of claim 21, wherein said sufficient amount is an established amount for all dispatched messages of a particular type.

24. The method of claim 21, wherein said sufficient amount is dependent upon one or more properties of said message.

25. The method of claim 21, wherein said sufficient amount is a user defined amount.

26. The method of claim 24, wherein said properties suggest said message is a spam email message.

27. The method of claim 24, wherein said properties suggest said message would require an undue amount of processing by a recipient of said message.

28. The method of claim 21, wherein said message is an email message.

29. The method of claim 21, wherein said message is an enterprise resource planning message.

30. The method of claim 21, wherein said message is a web services message.

31. The method of claim 21, wherein a digital rights management container containing a digital representation of money is employed.

32. The method of claim 21, wherein said indication is received as an email message.

33. The method of claim 21, wherein said indication is received as an enterprise resource planning message.

34. The method of claim 21, wherein said indication is received as a web services message.

35. The method of claim 21, wherein said indication is received via a bounce of said message.

36. The method of claim 21, wherein micropayments are employed.

37. The method of claim 21, wherein universal value exchange is employed.

38. The method of claim 21, wherein determination comprises receiving an indication from a user.

39. The method of claim 21, wherein making said sufficient amount of funds available comprises making replacement funds available.

40. The method of claim 21, wherein making said sufficient amount of funds available comprises making supplemental funds available.

41. A system for message handling, comprising:

a memory having program code stored therein; and

a processor operatively connected to said memory for carrying out instructions in accordance with said stored program code;

wherein said program code, when executed by said processor, causes said processor to perform;

determining if funds made available in association with a received message represent a sufficient amount of finds; and

determining if said funds made available in association with said received message should be possessed,

wherein said funds are possessed in the case where said message is found to be an undesirable message.

42. The system of claim 41, wherein said undesirable message is a spam email message.

43. The system of claim 41, wherein said undesirable message is an enterprise resource planning message possessing one or more inadequacies.

44. The system of claim 41, wherein said undesirable message is a web services message possessing one or more inadequacies.

45. The system of claim 41, wherein said sufficient amount is an established amount for all received messages.

46. The system of claim 41, wherein said sufficient amount is an established amount for all received messages of a particular type.

47. The system of claim 41, wherein said sufficient amount is a user defined amount.

48. The system of claim 41, wherein said sufficient amount is dependent upon one or more properties of said message.

49. The system of claim 48, wherein said properties suggest said message is a spam email message.

50. The system of claim 48, wherein said properties suggest said message would require an undue amount of processing by a recipient of said message.

51. The system of claim 41, wherein said message is an email message.

52. The system of claim 41, wherein said message is an enterprise resource planning message.

53. The system of claim 41, wherein said message is a web services message.

54. The system of claim 41, wherein said processor further performs providing to an originator of said message an indication that insufficient funds were made available in association with said message.

55. The system of claim 54, wherein said indication is provided as an email message.

56. The system of claim 54, wherein said indication is provided as an enterprise resource planning message.

57. The system of claim 54, wherein said indication is provided as a web services message.

58. The system of claim 54, wherein said indication is provided via a bounce of said message.

59. The system of claim 41, wherein a digital rights management container containing a digital representation of money is employed.

60. The system of claim 41, wherein micropayments are employed.

61. The system of claim 41, wherein universal value exchange is employed.

62. A system for message handling, comprising:

a memory having program code stored therein; and

a processor operatively connected to said memory for carrying out instructions in accordance with said stored program code;

wherein said program code, when executed by said processor, causes said processor to perform;

determining, for a message to be dispatched, an amount of funds to be made available in association with said message;

receiving an indication that insufficient funds were made available in association with said message; and

making a sufficient amount of funds available in association with said message.

63. The system of claim 62, wherein said sufficient amount is an established amount for all dispatched messages.

64. The system of claim 62, wherein said sufficient amount is an established amount for all dispatched messages of a particular type.

65. The system of claim 62, wherein said sufficient amount is dependent upon one or more properties of said message.

66. The system of claim 62, wherein said sufficient amount is a user defined amount.

67. The system of claim 65, wherein said properties suggest said message is a spam email message.

68. The system of claim 65, wherein said properties suggest said message would require an undue amount of processing by a recipient of said message.

69. The system of claim 62, wherein said message is an email message.

70. The system of claim 62, wherein said message is an enterprise resource planning message.

71. The system of claim 62, wherein said message is a web services message.

72. The system of claim 62, wherein a digital rights management container containing a digital representation of money is employed.

73. The system of claim 62, wherein said indication is received as an email message.

74. The system of claim 62, wherein said indication is received as an enterprise resource planning message.

75. The system of claim 62, wherein said indication is received as a web services message.

76. The system of claim 62, wherein said indication is received via a bounce of said message.

77. The system of claim 62, wherein micropayments are employed.

78. The system of claim 62, wherein universal value exchange is employed.

79. The system of claim 62, wherein determination comprises receiving an indication from a user.

80. The system of claim 62, wherein making said sufficient amount of funds available comprises making replacement funds available.

81. The system of claim 62, wherein making said sufficient amount of funds available comprises making supplemental finds available.