DYNAMICALLY RESOLVING RECIPIENTS TO RETRIEVE PUBLIC KEYS DURING SEND/RECEIVE

• US 20100229051A1
• Filed: 05/07/2010
• Published: 09/09/2010
• Est. Priority Date: 06/03/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Counts, Eian D., Gupta, Anoop, Kroman, Paul K., Hall, Gary W., Vargas, Garrett R., Nalliah, Selvaraj
• Granted Patent: US 8,151,106 B2
• Time in Patent Office: Days
• US Class Current: 714/57
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• 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/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 9/12 Transmitting and receiving encryption devices synchronised or initially set up in a particular manner
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy

Abstract

Systems and methods are disclosed that facilitate identifying messages generated on a mobile device while the device is offline as requiring encryption, storing the messages in a message outbox with a flag indicating that encryption is required, and identifying recipients of the flagged messages to generate a recipient list. The recipient list can be piggybacked on a server synchronization request when the mobile device enters a period of online activity, and a server can return public keys associated with identified recipients to permit an encryption component, such as a secure/multipurpose Internet mail extension protocol (S/MIME) encryption component, in the mobile device to encrypt the messages.

Claims

1. A method for processing a message on a mobile device, comprising:

storing a message on the mobile device during a period that the mobile device is unable to communicate with a server; and

upon the mobile device becoming able to communicate with the server, generating a synchronization request for synchronizing between the mobile device and the server, the synchronization request comprising a request for a public key associated with an identified recipient of the stored message.

2. The method of claim 1, wherein storing a message comprises associating the message with an identifier that indicates the message requires a public key.

3. The method of claim 1, wherein generating a synchronization request comprises identifying a recipient associated with the stored message.

4. The method of claim 3, wherein identifying a recipient associated with the stored message comprises identifying an email alias.

5. The method of claim 1, wherein the synchronization request comprising a request for a public key associated with an identified recipient comprises a synchronization request identifying at least one of an email alias or a device identifier.

6. The method of claim 5, wherein the synchronization request comprises a request to resolve at least one of an email alias or a device identifier against the server.

7. The method of claim 1, further comprising:

transmitting the synchronization request to the server; and

receiving a public key from the server.

8. The method of claim 7, further comprising:

encrypting the stored message using the received public key; and

transmitting the encrypted message to the recipient.

9. The method of claim 8, wherein encrypting the stored message comprises employing an S/MIME encryption technique.

10. The method of claim 1, further comprising generating an error message upon receipt of an indication a public key cannot be determined for the identified recipient.

11. The method of claim 10, further comprising storing the error message in an inbox data store for the mobile device and storing the stored message in a data store comprising drafts.

12. A tangible computer readable medium having instructions stored thereon that, if executed by a computing device, cause the computing device to perform operations comprising:

storing messages on the mobile device during a period that the mobile device is unable to communicate with a server;

upon the mobile device becoming able to communicate with the server, generating a synchronization request for synchronizing between the mobile device and the server, the synchronization request comprising a request for public keys associated with identified recipients of a plurality of the stored messages.

13. The method of claim 12, wherein storing messages comprises associating an indicator with each stored message that is to be encrypted when transmitted.

14. The method of claim 13, wherein generating a synchronization request comprises:

assessing the stored messages and compiling recipient information for messages having an associated indicator.

15. The method of claim 14, wherein compiling recipient information for messages having an associated indicator comprises compiling a list of recipients.

16. The method of claim 15, wherein the synchronization request comprising a request for public keys associated with identified recipients comprises the list of recipients.

17. The method of claim 16, wherein the list of recipients comprises email aliases.

18. A mobile device, comprising:

a computing processor; and

memory communicatively coupled with the computing processor, the memory comprising instructions executable on the computing processor to perform the following;

storing a message on the mobile device during a period that the mobile device is unable to communicate with a server;

associating the message with an identifier that indicates the message requires use of an encryption technique when transmitting;

upon the mobile device becoming able to communicate with the server;

identifying a recipient for the message;

generating a synchronization request for synchronizing between the mobile device and the server, the synchronization request comprising a request for a certificate associated with the identified recipient;

transmitting the synchronization request; and

receiving the certificate.

19. The method of claim 18, further comprising:

encrypting data using the received certificate; and

transmitting the encrypted data.

20. The method of claim 19, wherein encrypting data using the received certificate comprises employing an S/MIME encryption technique.