Rights management system and method integrated with email transmission of documents
US-2015149774-A1 · May 28, 2015 · US
US9716693B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9716693-B2 |
| Application number | US-201414543871-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 17, 2014 |
| Priority date | Nov 17, 2014 |
| Publication date | Jul 25, 2017 |
| Grant date | Jul 25, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A digital rights management (DRM) method for protecting emails can apply different protection policies to different components of an email such as the message body and the attached digital files. While an email application of the client encrypts the entire email document including both the message and the attachments, a plugin module on the client obtains user input regarding the DRM policies to be applied to individual attachments and then transmits the encrypted email along with the information about the DRM policies for the individual attachments to a digital rights management server. The server first decrypts the entire email document, then applies the user-specified DRM policies to the attachments individually. The server re-composes an email and attaches the individually protected attachments, and transmits the email to the exchange server.
Opening claim text (preview).
What is claimed is: 1. A digital rights management method implemented in a system including a client computer and a digital rights management server (RMS server) for protecting electronic mails (emails), comprising: by the client computer: (a) receiving encrypted data representing an email, the email including a message and one or more attachments, the data having been encrypted by an email application of the client computer based on an original digital rights management (DRM) policy selected by a user; (b) obtaining from the user one or more DRM policies to be applied to the attachments of the email, each attachment corresponding to one specified DRM policy; and (c) transmitting the encrypted data representing the email, along with data specifying the DRM policy to be applied to each attachment and data specifying the original DRM policy, to the RMS server; by the RMS server: (d) receiving, from the client computer, the encrypted data representing the email, along with the data specifying the DRM policy to be applied to each attachment and the data specifying the original DRM policy; (e) decrypting the encrypted data representing the email, including the message and the one or more attachments, which has been received from the client computer in step (d); (f) applying digital rights management protection to each attachment which has been decrypted in step (e), based on the specified DRM policy for the attachment as specified in the data received from the client computer in step (d), to generate a protected document for each attachment; (g) re-composing an email document which includes as attachments the protected documents generated in step (f) to generate a re-composed email document; (h) applying digital rights management protection to the re-composed email document generated by step (g) based on the original DRM policy received from the client computer in step (d); and (i) transmitting the re-composed email document to an email exchange server. 2. The method of claim 1 , wherein step (a) includes a plugin module on the client computer receiving the encrypted data representing the email from an email application on the client computer, wherein steps (b) and (c) are performed by the plugin module. 3. The method of claim 2 , wherein in step (b), the plugin module obtains the one or more DRM policies from the user via a user interface generated by the plugin module. 4. The method of claim 1 , wherein the data representing the email that has been decrypted in in step (e) includes recipients, a subject, a message body and the one or more attachments, and wherein step (g) includes: re-composing the new email document using the recipients, the subject and the message body; and attaching the protected documents, or links to the protected documents stored in a storage medium, to the new email. 5. The method of claim 4 , wherein step (g) further comprises appending a notification to the message to indicate that the attachments and the message are protected by different DRM policies. 6. The method of claim 4 , wherein the re-composed email document complies with Multi-Purpose Internet Mail Extensions (MIME) standard. 7. The method of claim 1 , wherein step (f) includes, for each attachment: generating a unique document ID and an encryption key; encrypting the attachment using the encryption key; embedding metadata including the document ID in the encrypted attachment to generate the protected document; and storing the document ID in association with the DRM policy ID and the encryption key in a protected document database. 8. A computer program product comprising a first computer usable non-transitory medium having a first computer readable program code embedded therein for controlling a client computer, and a second computer usable non-transitory medium having a second computer readable program code embedded therein for controlling a digital rights management server (RMS server) computer, wherein the first computer readable program code is configured to cause the client computer to execute a process comprising: (a) receiving encrypted data representing an email, the email including a message and one or more attachments, the data having been encrypted by an email application of the client computer based on an original digital rights management (DRM) policy selected by a user; (b) obtaining from the user one or more DRM policies to be applied to the attachments of the email, each attachment corresponding to one specified DRM policy; and (c) transmitting the encrypted data representing the email, along with data specifying the DRM policy to be applied to each attachment and data specifying the original DRM policy, to the RMS server; wherein the second computer readable program code is configured to cause the RMS server to execute a process comprising: (d) receiving, from the client computer, the encrypted data representing the email, along with the data specifying the DRM policy to be applied to each attachment and the data specifying the original DRM policy; (e) decrypting the encrypted data representing the email, including the message and the one or more attachments, which has been received from the client computer in step (d); (f) applying digital rights management protection to each attachment which has been decrypted in step (e), based on the specified DRM policy for the attachment as specified in the data received from the client computer in step (d), to generate a protected document for each attachment; (g) re-composing an email document which includes as attachments the protected documents generated in step (f) to generate a re-composed email document; (h) applying digital rights management protection to the re-composed email document generated by step (g) based on the original DRM policy received from the client computer in step (d); and (i) transmitting the re-composed email document to an email exchange server. 9. The computer program product of claim 8 , wherein step (a) includes a plugin module on the client computer receiving the encrypted data representing the email from an email application on the client computer, wherein steps (b) and (c) are performed by the plugin module. 10. The computer program product of claim 9 , wherein in step (b), the plugin module obtains the one or more DRM policies from the user via a user interface generated by the plugin module. 11. The computer program product of claim 8 , wherein the data representing the email that has been decrypted in in step (e) includes recipients, a subject, a message body and the one or more attachments, and wherein step (g) includes: re-composing the new email document using the recipients, the subject and the message body; and attaching the protected documents, or links to the protected documents stored in a storage medium, to the new email. 12. The computer program product of claim 11 , wherein step (g) further comprises appending a notification to the message to indicate that the attachments and the message are protected by different DRM policies. 13. The computer program product of claim 11 , wherein the re-composed email document complies with Multi-Purpose Internet Mail Extensions (MIME) standard. 14. The computer program product of claim 8 , wherein step (f) includes, for each attachment: generating a unique document ID and an encryption key; encrypting the attachment using the encryption key; embedding metadata including the document ID in the encrypted attachment to generate the protected document; and storing the document ID in association with the DRM policy ID and the encryption key in a protected docum
Protecting distributed programs or content, e.g. vending or licensing of copyrighted material (protection in video systems or pay television H04N7/16) {; Digital rights management [DRM]} · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title
applying security measures for digital rights management · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.