File vault and cloud based document notary service

• US 9,886,684 B2
• Filed: 04/26/2016
• Issued: 02/06/2018
• Est. Priority Date: 01/11/2012
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Baron, Casey L.
• Primary Examiner(s): Chen, Eric
• Application Number:
  US15/138,372
• Publication Number:
  US 20170024711A1
• Time in Patent Office: 651 Days
• Field of Search: None
• 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 notarized 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 at least one security credential from a third party;

receiving 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;

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

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

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

receiving 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

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

2. The method of claim 1, 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 and the second party is not related to the first party.

3. 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.

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

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

6. The method of claim 1 wherein receiving a first request to access the first document comprises receiving the first request from a fourth party.

7. The method of claim 1, 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.

8. At least one non-transitory machine-readable medium having stored thereon data which, if used by at least one machine, causes the at least one machine to perform operations comprising:

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 machine 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 store 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 machine via the network; and

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

9. The at least one medium of claim 8, 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 and the second party is not related to the first party.

10. The at least one medium of claim 8 comprising instructions to, before granting the first request, encrypt the first document with a private key that corresponds with a publically available public key.

11. The at least one medium of claim 8 comprising instructions to digitally sign the first document before granting the first request.

12. The at least one medium of claim 11 comprising instructions to provide date information, which concerns a date the first document was received from the first node, coupled to the digitally signed first document.

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

14. The at least one medium of claim 8, 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.

15. A system comprising:

at least one memory; and

at least one processor, coupled to the memory, to perform operations comprising;

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 store 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.

16. The system of claim 15, 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 and the second party is not related to the first party.

17. The system of claim 15, wherein the operations comprise, before granting the first request, encrypt the first document with a private key that corresponds with a publically available public key.

18. The system of claim 15 wherein the operations comprise digitally sign the first document before granting the first request.

19. The system of claim 18 wherein the operations comprise provide date information, which concerns a date the first document was received from the first node, coupled to the digitally signed first document.

20. The system of claim 15 wherein:

receiving a first request to access the first document comprises receiving the first request from a fourth party; and

periodically receiving the additional documents comprises periodically automatically pulling the additional documents from the first node based on the at least one security credential.