File vault and cloud based document notary service

• US 9,344,416 B2
• Filed: 01/11/2012
• Issued: 05/17/2016
• Est. Priority Date: 01/11/2012
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Baron, Charles
• Primary Examiner(s): CHEN, SHIN HON
• Application Number:
  US13/993,341
• Publication Number:
  US 20130269006A1
• Time in Patent Office: 1,588 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 50/18 Legal services
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

In one embodiment, a trusted cloud service such as an “electronic vault” may store records of a consumer'"'"'s electronic data file history. These documents may come from disparate providers and include financial statements and the like. The trusted vault cloud may act as an online notary to certify documents are legitimate and may be trusted. For example, a retailer may dispute whether the consumer paid a debt. To resolve the issue the retailer may access the cloud vault to retrieve a bank statement for the consumer, whereby the bank statement is electronically notorized by the vault cloud and is thus credible to the retailer. The retailer may then see proof the consumer had indeed paid a past debt to the retailer. Other embodiments are described herein.

Claims

1. A method executed by at least one processor comprising:

receiving (a) a first document from a first node associated with a first party during a first transfer transaction, (b) a second document from a second node associated with a second party, and (c) a third document from the first node during the first transfer transaction, the first and second nodes remotely coupled to the at least one processor via a network;

storing the first and second documents in at least one non-volatile machine accessible medium coupled to the at least one processor, the first and second documents respectively assigned to first and second document identifiers;

receiving a first request to access the first document from a fourth party, the first request corresponding to the first document identifier;

after receiving the first request, receiving a first authorization, including at least one digital security credential, from a third party associated with a third node that is remotely coupled to the at least one processor via the network; and

granting the first request based on the first authorization and the first document identifier;

wherein the first document corresponds to a first user account and the third document corresponds to an additional user account that is different from the first user account.

2. The method of claim 1, wherein the first document corresponds to a first account statement between the first and third parties.

3. The method of claim 2, wherein (a) the third party has an active account with the first party when the first document is received from the first node, (b) the third party has closed the account with the first party after the first document is received but before the first request is received, and (c) the third party has no additional account open with the first party when the first request is received.

4. The method of claim 1 comprising, before granting the first request, encrypting the first document with a private key that corresponds with a publically available public key.

5. The method of claim 1 comprising digitally signing the first document before granting the first request.

6. The method of claim 5 comprising providing date information, which concerns the date the first document was received from the first node, coupled to a digitally signed first document.

7. The method of claim 1, wherein the first document identifier includes a globally unique identifier.

8. The method of claim 1 comprising:

establishing a guest account for the fourth party;

receiving at least one security credential associated with the guest account; and

granting the first request based on the guest account and the at least one security credential.

9. The method of claim 1 wherein receiving the first document from the first node comprises receiving a first digital signature from the first node, the method further comprising:

digitally signing the first document with a second digital signature before granting the first request; and

coupling the first document to a first watermark that is based on both of the first and second digital signatures.

10. An apparatus comprising:

at least one processor;

control logic, coupled to the at least one processor, to;

receive at least one security credential from a third party;

receive a first document from a first node associated with a first party, based on the at least one security credential, and a second document from a second node associated with a second party, the first and second nodes remotely coupled to the at least one processor via a network;

store the first and second documents, the first and second documents respectively assigned to first and second document identifiers;

periodically receive additional documents from the first node based on the at least one security credential and storing the additional documents;

receive a first request to access the first document, the first request corresponding to the first document identifier;

receive a first authorization from a third node, associated with the third party, that is remotely coupled to the at least one processor via the network; and

grant the first request based on the first authorization and the first document identifier.

11. The apparatus of claim 10, wherein (a) the first document corresponds to a first account statement between the first and third parties, (b) the third party has an active account with the first party when the first document is received from the first node, (c) the third party has closed the account with the first party after the first document is received but before the first request is received, (d) the third party has no additional account open with the first party when the first request is received and (e) the second node is associated with the second party not related to the first party.

12. The apparatus of claim 10, wherein the control logic is to, before granting the first request, encrypt the first document with a private key that corresponds with a publically available public key.

13. The apparatus of claim 10 wherein the control logic is to digitally sign the first document before granting the first request.

14. The apparatus of claim 13 wherein the control logic is to provide date information, which concerns a date the first document was received from the first node, within the digitally signed first document.

15. The apparatus of claim 10 wherein receiving a first request to access the first document comprises receiving the first request from a fourth party.

16. The apparatus of claim 10, wherein periodically receiving the additional documents comprises periodically automatically pulling the additional documents from the first node based on the at least one security credential.

17. At least one non-transitory machine-accessible medium having instructions stored thereon, the instructions when executed on a machine cause the machine to:

receive a first document from a first node associated with a first party and a second document from a second node associated with a second party, wherein receiving the first document comprises receiving a first digital signature from the first node;

store the first and second documents, the first and second documents respectively assigned to first and second document identifiers;

receive a first request to access the first document, the first request corresponding to the first document identifier;

digitally sign the first document, which already includes the first digital signature, with a second digital signature before granting the first request;

couple the first document to a first watermark that is based on both of the first and second digital signatures;

receive a first authorization from a third node associated with a third party; and

grant the first request based on the first authorization and the first document identifier.

18. The at least one medium of claim 17 including instructions that enable the machine to, before granting the first request, encrypt the first document with a private key that corresponds with a publically available public key.

19. The at least one medium of claim 17, wherein receiving a first request to access the first document comprises receiving the first request from a fourth party.

20. The at least one medium of claim 17 including instructions that enable the machine to:

receive at least one security credential from the third party;

receive the first document from the first node based on the at least one security credential; and

periodically receive additional documents from the first node based on the at least one security credential and store the additional documents.