Systems and methods for conducting transactions and communications using a trusted third party

• US 20070124247A1
• Filed: 10/30/2006
• Published: 05/31/2007
• Est. Priority Date: 04/20/2001
• Status: Active Grant

• Current Assignee: Intertrust Technologies Corporation (Fidelio Acquisition Co LLC)
• Original Assignee: Intertrust Technologies Corporation (Fidelio Acquisition Co LLC)
• Inventors: Sander, Tomas, Pinkas, Binyamin, Horne, William
• Granted Patent: US 7,827,114 B2
• Time in Patent Office: Days
• US Class Current: 705/50
• 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/3829 involving key management
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

Systems and methods are provided for managing the transfer of electronic files. In one embodiment, a sender transfers an encrypted version of a file (such as a digitally encoded audio track, movie, document, or the like) to someone who wishes to receive it. The receiver computes a hash of the encrypted file, and sends it to a trusted third party. The trusted third party compares the hash that was computed by the receiver with another hash computed by the sender. If the two hashes match, the third party sends the file decryption key to the receiver. In some embodiments, the receiver may also send the third party payment information so that the sender, the content owner, and/or the third party can be paid for their role in the transaction. In a preferred embodiment, the payment information is only sent to, and/or used by, the third party once the third party has confirmed to the satisfaction of the receiver that the encrypted file in the receiver'"'"'s possession will decrypt correctly. In some embodiments, the sender computes a hash of the encrypted version of the file and sends it directly to the third party. In other embodiments, the sender encrypts this hash using a key associated with the third party and sends the encrypted hash to the receiver, who then forwards it to the third party.

Claims

1-21. -21. (canceled)

22. A method for providing a first party with data content, the method comprising:

receiving the data content from a second party, wherein the data content has been encrypted by a third party;

computing a first hash of at least a portion of the received encrypted data content;

sending the first hash to a fourth party, wherein the fourth party is operable to compare at least a portion of the first hash to at least a portion of a second hash;

receiving a decryption key from the fourth party; and

decrypting at least the portion of the received encrypted data content with the decryption key.

23. A method as in claim 22, wherein the step of receiving the data content from the second party further includes the second party receiving the data content from the third party.

24. A method as in claim 22, wherein the step of computing a first hash of a portion of the data content includes computing multiple hashes of the data content, wherein each of the multiple hashes is computed using a different portion of the data content.

25. A method as in claim 24, wherein the decryption key comprises a public key of the fourth party.

26. A method as in claim 24, wherein the second hash includes a hash of at least a portion of the encrypted data content, the second hash and the decryption key being sent to the fourth party by the third party.

27. A method as in claim 24, wherein the data content comprises one or more of:

digitally encoded audio content;

digitally encoded video content;

digitally encoded text; and

software.

28. A method as in claim 24, wherein each different portion of the data content comprises a unique, non-overlapping portion of the data content.

29. A method as in claim 24, wherein the step of sending the first hash to the fourth party includes sending the multiple hashes to a plurality of parties, and wherein the step of receiving the decryption key further includes receiving a plurality of decryption keys from the plurality of parties, each of the decryption keys being operable to decrypt a portion of the data content.

30. A method as in claim 29, wherein a first decryption key received from one of the plurality of parties is operable to decrypt at least a first portion of the data content used to compute a hash sent to the one of the plurality of parties.

31. A method as in claim 29, wherein the plurality of decryption keys does not include at least one decryption key corresponding to at least one portion of the data content, and wherein the step of decrypting the data content includes decrypting said at least one portion of the data content.

32. A method as in claim 30, wherein the plurality of decryption keys does not include at least twenty five percent of a set of decryption keys corresponding to each portion of the data content, and wherein the step of decrypting the portion of data content includes decrypting each portion of the data content using the plurality of decryption keys.

33. A method as in claim 24, further comprising:

in response to the step of sending the first hash, receiving an indication from the fourth party that the portion of the encrypted data content is valid.

34. A method as in claim 33, further including:

in response to receiving the indication from the fourth party that the encrypted data content is valid, submitting payment information to the fourth party, the payment information being sufficient to enable the fourth party to cause the first party to be charged for the data content.

35. A method as in claim 34, wherein the payment information is processed so that the fourth party is compensated for supplying the decryption key to the first party.

36. A method as in claim 22, wherein the step of sending the first hash to a fourth party further includes sending payment related information to the fourth party.

37. A method as in claim 22, wherein the step of receiving data content from the second party further includes receiving the data content in multiple data blocks, and wherein each of the multiple data blocks further includes a message authentication code.

38. A method as in claim 37, wherein the message authentication code included in at least one of the multiple blocks is encoded by the fourth party, wherein the fourth party uses a key to encode the message authentication code before sending the message authentication code to the third party.

39. A method as in claim 37, wherein the step of sending the first hash to the fourth party further includes sending the message authentication code.

40. A method as in claim 39, wherein the fourth party is operable to decrypt the message authentication code and compare the decrypted message authentication code with the message authentication code sent by the fourth party to the third party.

41. A method as in claim 40, wherein the fourth party uses the key to decrypt the received message authentication code.