Method and apparatus for data recipient storage and retrieval of data using a network communication device

• US 7,146,341 B1
• Filed: 04/19/2000
• Issued: 12/05/2006
• Est. Priority Date: 10/07/1998
• Status: Expired due to Term

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: VeriSign, Inc.
• Inventors: Light, Elliott D., Lum, James C. P.
• Primary Examiner(s): ELISCA, PIERRE E
• Application Number:
  US09/552,088
• Time in Patent Office: 2,421 Days
• Field of Search: 370/352, 713/171, 713/176, 713/200, 713/156, 713/201, 713/153, 713/202, 713/159, 380/202, 380/203, 380/204, 709/229, 705/42, 705/64, 705/39, 705/40, 705/27, 705/26, 705/67, 705/75, 379/93.12
• US Class Current: 705/64
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/0855 involving a third party
• 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/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0222 During e-commerce, i.e. online transactions
• CPC Class Codes: G06Q 30/0277 Online advertisement
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A system and method for data recipient invoked electronic commerce allowing data subjects to provide information over a network and data recipients to receive such information relating to the needs of data subject such as purchases, distribution of application information and the like. The system includes a server having software which gathers the information from a data subject to complete a transaction over a network. The system has a data subject data structure that stores information for registered data subjects. The software is able to access the data subject data structure and enter the data subject'"'"'s information during subsequent transactions. Having the software obtain and enter the data subject'"'"'s purchasing information, the data subject does not have to enter the same information every time the data subject desires to effect a transaction over the network. In alternate embodiments, the same technology can be applied to other arenas where a user may have to enter the same repetitive information.

Claims

1. A system for data recipient invoked electronic transactions, comprising:

a first network;

a second network;

at least one data recipient computer associated with at least one data recipient and connected to the first network, the at least one data recipient computer having web server software for hosting a web page and client software for allowing the at least one data recipient to send and receive information over the first network;

at least one gateway computer connected to the first network and the second network, the at least one gateway computer having gateway software for allowing the file exchange between the first and second networks;

at least one data subject network communication device (NCD) associated with the at least one data subject and connected to the second network, the at least one data subject NCD having software for accessing, and communicating with, the gateway computer to send and receive information over the first network;

at least one data repository connected to the first network, the at least one data repository having data repository software including instructions for gathering information to complete a transaction; and

the client software includes instructions for forwarding a data recipient'"'"'s offer to the at least one data repository via the gateway computer, the second network, and the NCD software.

2. The system in accordance with claim 1, wherein the data repository further comprises instructions to send the purchasing information to the at least one data recipient computer.

3. The system in accordance with claim 1, wherein the first network is selected from group consisting of the Internet, intranet, local area networks (LANS), and wide area networks (WANS), wireless, wireless local loops and cable networks.

4. The system in accordance with claim 1, wherein the second network is selected from group consisting of the Internet, intranet, local area networks (LANS), and wide area networks (WANS), wireless, wireless local loops, and cable networks.

5. The system in accordance with claim 1, wherein the second network is a wireless network and the gateway computer software comprises a wireless application protocol interface.

6. The system in accordance with claim 1, wherein the client software and the NCD software send and receive files in a common computer language.

7. The system in accordance with claim 6, wherein the common computer language is selected from a group consisting of HTML, XML, and WML.

8. The system in accordance with claim 1, wherein the NCD software further comprises a translator for reading and writing files in the native language of the NCD software, and read and write files in the native language of the client software.

9. The system in accordance with claim 1, wherein the gateway software further comprises a translator for reading and writing files in the native language of the NCD software and read and write files in the native language of the client software.

10. The system in accordance with claim 1, wherein the client software further comprises a translator for reading and writing files in the native language of the client software, and for reading and writing files in the native language of the NCD software.

11. The system in accordance with claim 1 wherein the data repository is connected to the gateway computer via the first network.

12. The system in accordance with claim 1 wherein the data repository is co-located with and directly connected to the gateway computer.

13. The system in accordance with claim 1, wherein the client software further comprises instructions for instructing the data subject NCD software to forward the data recipient'"'"'s offer to the data repository and to send a message to the data repository indicating whether a NCD software identifier is present in the data subject'"'"'s NCD software, and wherein the presence of a NCD software identifier indicates whether the data subject'"'"'s NCD software was previously used in conjunction with the system.

14. The system in accordance with claim 13, wherein the NCD software identifier is a cookie.

15. The system in accordance with claim 13, further comprising a data subject data structure which further comprises information pertaining to previous transactions by at least one registered data subject, and wherein a registered data subject is a data subject who has previously registered with the system.

16. The system in accordance with claim 15, wherein the data repository further comprises storage for storing the data subject data structure.

17. The system in accordance with claim 15, further comprising at least one server for storing the data subject data structure.

18. The system in accordance with claim 13, further comprising a data recipient data structure which further comprises label-value pairs which represent data recipient information that is necessary to identify the data recipient and the data recipient computer.

19. The system in accordance with claim 18, wherein the data recipient information further comprises contact information, data recipient identification number, at least one network location for the data recipient computer, accepted payment card types, accepted currencies, and accepted payment methods.

20. The system in accordance with claim 18, wherein the data repository further comprises storage for storing the data recipient data structure.

21. The system in accordance with claim 18, further comprising at least one server for storing the data recipient data structure.

22. The system in accordance with claim 13, further comprising:

a data subject data structure which further comprises information pertaining to previous purchasing transactions by at least one registered data subject, wherein a registered data subject is a data subject who has previously registered with the system; and

a data recipient data structure which further comprises label-value pairs which represent data recipient information that identifies the data recipient and the data recipient computer.

23. The system in accordance with claim 22, wherein the data repository software further comprises instructions for selecting a data subject if the NCD software identifier identifies one or more registered data subjects who have used the data subject'"'"'s NCD software in conjunction with the system.

24. The system in accordance with claim 23, wherein the data repository software further comprises instructions for gathering the transaction information pertaining to the selected registered data subject from the data subject data structure to complete a transaction.

25. The system in accordance with claim 24, wherein the data repository software further comprises instructions for selecting the transaction information for a selected registered data subject that is acceptable to the data recipient based on the data recipient information in the data recipient data structure.

26. The system in accordance with claim 25, wherein the data repository software further comprises instructions for gathering the transaction information to complete the transaction by prompting the registered data subject for additional information to complete the transaction if the data subject data structure is missing information to complete the transaction.

27. The system in accordance with claim 23, wherein the data repository software further comprises instructions for allowing a registered data subject to enter information to identify the registered data subject thereby allowing the data repository software to access the registered data subject'"'"'s information stored in the data subject data structure if the registered data subject was not associated with the data subject'"'"'s web browser.

28. The system in accordance with claim 23, wherein the data repository software further comprises instructions to allow a registered data subject to enter information to identify the registered data subject thereby allowing the data repository software to access the registered data subject'"'"'s information stored in the data subject data structure if the data repository software did not select the correct registered data subject.

29. The system in accordance with claim 28, wherein the information which can be entered to identify the registered data subject comprises a data subject identification number, email address, and a passphrase.

30. The system in accordance with claim 27, wherein the information which can be entered to identify the registered data subject comprises a data subject identification number, email address, and a passphrase.

31. The system in accordance with claim 23, wherein the data repository software further comprises instructions for prompting the selected data subject for the data subject'"'"'s identification number and passphrase if the registered data subject was selected by the data repository software.

32. The system in accordance with claim 22, wherein the data repository software further comprises instructions for gathering the information to complete the transaction by prompting the data subject for the information when the data subject is a non-registered data subject.

33. The system in accordance with claim 32, further comprising a temporary data structure for storing for a limited amount of time information pertaining to a transaction.

34. The system in accordance with claim 32, wherein the data repository software further comprises instructions to set a flag if a non-registered data subject elects to become a registered data subject.

35. The system in accordance with claim 34, wherein the data repository software further comprises instructions to prompt a non-registered data subject for registration information if the flag is set indicating that a non-registered data subject elected to become a registered data subject.

36. The system in accordance with claim 35, wherein the data repository software further comprises instructions to transfer the information stored in the temporary data structure to the data subject data structure when a non-registered data subject elects to become a registered data subject.

37. The system in accordance with claim 1, wherein the data recipient'"'"'s offer comprises at least a data recipient identifier, a price for the item, a digital signature of the data recipient, and a transaction number.

38. The system in accordance with claim 37, wherein the data recipient'"'"'s offer further comprises a final price indicator which indicates that the price for an item is not final.

39. The system in accordance with claim 38, wherein the data repository software further comprises instructions which communicate the data subject'"'"'s shipping address information to the data recipient computer for calculating the final price for the item if the final price indicator indicates that the price for an item is not final.

40. The system in accordance with claim 39, wherein the data subject'"'"'s shipping address information communicated to the data recipient further comprises the city, state, country and mail code of the data subject'"'"'s shipping address.

41. The system in accordance with claim 39, wherein the data recipient computer further comprises instructions for calculating the final price for the item being purchased based on the data subject'"'"'s shipping address information.

42. The system in accordance with claim 39, wherein the data subject'"'"'s shipping address information communicated to the data recipient further comprises the shipping means.

43. The system in accordance with claim 42, wherein the data recipient computer further comprises instructions for calculating the final price for the item being purchased based on the data subject'"'"'s shipping address information.

44. The system in accordance with claim 39, wherein the data subject'"'"'s shipping address is the email address where the item is being sent for items which can be delivered over the network.

45. The system in accordance with claim 1, wherein the system further comprises a data subject transaction log for recording information relating to a registered data subject'"'"'s purchasing transactions, and wherein a registered data subject is a data subject who has previously registered with the system.

46. The system in accordance with claim 45, wherein the data repository further comprises storage for storing the data subject transaction log.

47. The system in accordance with claim 45, further comprising at least one server to store the data subject transaction log.

48. The system in accordance with claim 1, further comprising a data recipient transaction log which stores label-value pairs relating to transactions performed by the at least one data recipient.

49. The system in accordance with claim 48, wherein the data repository further comprises storage for storing the data recipient transaction log.

50. The system in accordance with claim 48, further comprising at least one server for storing the data recipient transaction log.

51. A method for purchasing an item over a first network coupled to a second network by a gateway, comprising:

at a data recipient computer connected to the first network;

receiving a request for an offer from a data subject network communications device connected to the second network, and

in response to the request, sending the offer and a data file from the data recipient computer to the data subject network communications device; and

at a data repository connected to the first network;

receiving the offer and a message from the data subject network communications device,

in response to the offer, determining an identity of a data subject based on the message,

gathering payment data associated with the data subject based on the identity,

presenting the offer to the data subject network communications device,

receiving a purchase decision from the data subject network communications device, and

sending payment data to the data recipient computer.

52. The method of claim 51 further comprising:

at the data subject network communications device;

receiving the offer and the data file from the data recipient computer;

processing the data file;

creating the message; and

sending the offer and the message to the data repository.

53. The method of claim 52 further comprising:

at the data subject network communications device;

receiving the offer from the data repository; and

sending the purchase decision to the data repository.

54. The method of claim 53, wherein said presenting includes displaying the offer on the data subject network communication device in an area reserved for a wallet.

55. The method of claim 51, further comprising:

at the data repository;

prompting the data subject for identification;

in response, receiving identifying information from the data subject network communication device; and

authenticating the data subject based on the identifying information.

56. The method of claim 55, wherein the identifying information includes an identification number, an email address and a passphrase.

57. The method of claim 55, further comprising:

at the data repository;

prompting the data subject for purchasing information; and

receiving the purchasing information from the data subject network communication device.

58. The method of claim 51, wherein the offer includes a data recipient identifier, a price, a data recipient digital signature, and a transaction number.

59. The method of claim 58, further comprising:

at the data repository;

determining whether to adjust the price based on a data subject address;

sending the price and the data subject address to the data recipient computer; and

receiving a revised price from the data recipient computer.

60. The method of claim 51, wherein the message includes a network communication device software identifier.

61. The method of claim 60, wherein the message is a cookie.

62. A system for conducting electronic transactions, comprising:

a first network;

a gateway coupled to the first network;

a second network coupled to the gateway;

a data recipient computer, coupled to the first network, adaptively configured to;

receive an offer request from a data subject network communication device, coupled to the second network, via the gateway,

send an offer and a data file to the data subject network communication device via the gateway; and

a data repository, coupled to the first network, adaptively configured to;

receive the offer and a message from the data subject network communication device via the gateway,

determine an identity of a data subject based on the message,

gather payment data associated with the data subject based on the identity,

present the offer to the data subject network communications device via the gateway,

receive a purchase decision from the data subject network communications device via the gateway, and

send payment data to the data recipient computer.

63. The system of claim 62, wherein:

the first network is a wide area network;

the second network is a wireless network; and

the gateway is a wireless application protocol-enabled gateway.

64. The system of claim 62, wherein the first network is a wide area network and the second network is a cable network.

65. The system of claim 62, wherein the data subject network communication device includes a web browser.

66. The system of claim 62, wherein the gateway is adaptively configured to translate between a data subject network communication device file format and at least one of a data recipient computer file format and a data repository file format.

67. The system of claim 62, wherein the data repository includes a database having a plurality of data structures.

68. The system of claim 67, wherein the plurality of data structures includes a data subject data structure, a data recipient data structure, a data subject transaction log, and a data recipient transaction log.

69. The system of claim 62, further comprising an encrypted communication link between the data repository, the data recipient computer, and the data subject network communication device.

70. The system of claim 62, further comprising a direct communication link between the data repository and the data recipient computer.