Document event notifications based on document access control lists
US-2015229647-A1 · Aug 13, 2015 · US
US9813452B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9813452-B2 |
| Application number | US-201514951066-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 24, 2015 |
| Priority date | Nov 24, 2015 |
| Publication date | Nov 7, 2017 |
| Grant date | Nov 7, 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.
In a digital rights management system, a rights management server sends event notifications to certain users when other users perform certain actions (read, print, copy, etc.) on documents managed by the system. For each document, a notification rule defines which users will receive what event notifications for that document. The notification rule is determined based on document access permissions possessed by the users, so that only users who have permission to perform an action on the document will receive notifications when other users perform that action on the document, while users with no permission to perform an action will not receive notifications when other users perform that action. The server also allows the users who have permission to perform an action to opt out of the notifications. The server monitors events that occur on the documents, and sends event notifications to appropriate users according to the notification rules.
Opening claim text (preview).
What is claimed is: 1. A digital rights management method implemented in a server of a digital right management (DRM) system, comprising: (a) obtaining a permission policy that is associated with a digital document managed by the DRM system, wherein the permission policy defines, for each of a plurality of users of the DRM system, whether or not the user has permission to take each of a plurality of actions on the document; (b) generating a notification rule for the document based on the permission policy obtained in step (a), wherein the notification rule defines, for each of the plurality of users, a plurality of notification settings each corresponding to one of the plurality of actions, wherein for each one of the plurality of actions, the corresponding notification setting is always set to Off if the user does not have permission to take the corresponding action under the permission policy, and the corresponding notification setting is initially set to On if the user has permission to take the corresponding action under the permission policy; (c) continuously monitoring actions taken by any of the plurality of users on the document; and (d) when an action by a user on the document is detected in step (c), sending event notifications to some or all of the plurality of users whose notification settings corresponding to the detected action are set to On, without sending event notifications to any of the plurality of users whose notification settings corresponding to the detected action are set to Off; wherein in step (d), when the detected action is a publication of the document or a change of permission policy associated with the document, the event notification sent to each receiving user include a list of one or more other users, and for each one of the plurality of actions that the receiving user has permission to take under the permission policy, the event notification contains an indication of whether or not each of the other users in the list has permission to take that action, and for each one of the plurality of actions that the receiving user does not have permission to take under the permission policy, the event notification contains an indication of the action but no indication of whether or not each of the other users in the list has permission to take that action. 2. The method of claim 1 , wherein the plurality of actions include at least one of read, print and copy. 3. The method of claim 1 , further comprising: (e) obtaining user information that associates each user with a group, wherein in step (d), the event notifications are sent only to users whose notification settings corresponding to the detected action are set to On and who belong to the same group as the user who took the detected action. 4. The method of claim 1 , further comprising: (f) obtaining user information that associates each user with a role, wherein in step (d), the event notifications are sent only to users whose notification settings corresponding to the detected action are set to On and who have an equal role as or a higher role than the user who took the detected action. 5. The method of claim 1 , wherein the event notifications include an identity of the user who took the detected action on the document. 6. The method of claim 1 , wherein the detected action on the document is a print action, and wherein the event notification includes an identity of a printer used to print the document and a number of copies of the document that was printed. 7. The method of claim 1 , wherein the detected action on the document is a read action, and wherein the event notification includes an identity of a device used to read the document. 8. The method of claim 1 , wherein each event notification sent in step (d) includes an opt-out request for the user who receives the event notification to select or deselect one or more actions from a list of actions, wherein the list of actions excludes any actions which that user does not have permission to take under the permission policy; wherein the method further comprises: (g) receiving input from a user in response to the opt-out request; (h) changing the notification rule for the document, by changing the notification settings for that user based on the user input received in step (g). 9. The method of claim 1 , wherein each event notification sent in step (d) includes a request for the user who receives the event notification to select a notification method for receiving further event notifications, the notification method being selected from among at least one of email, short message service (SMS), messenger and social network; wherein the method further comprises repeating steps (c) and (d), wherein in repeated step (d), the event notifications are sent using the notification methods selected by the users. 10. A computer program product comprising a computer usable non-transitory medium having a computer readable program code embedded therein for controlling a server of a digital right management (DRM) system, the computer readable program code configured to cause the server to execute a digital rights management process, the process comprising: (a) obtaining a permission policy that is associated with a digital document managed by the DRM system, wherein the permission policy defines, for each of a plurality of users of the DRM system, whether or not the user has permission to take each of a plurality of actions on the document; (b) generating a notification rule for the document based on the permission policy obtained in step (a), wherein the notification rule defines, for each of the plurality of users, a plurality of notification settings each corresponding to one of the plurality of actions, wherein for each one of the plurality of actions, the corresponding notification setting is always set to Off if the user does not have permission to take the corresponding action under the permission policy, and the corresponding notification setting is initially set to On if the user has permission to take the corresponding action under the permission policy; (c) continuously monitoring actions taken by any of the plurality of users on the document; and (d) when an action by a user on the document is detected in step (c), sending event notifications to some or all of the plurality of users whose notification settings corresponding to the detected action are set to On, without sending event notifications to any of the plurality of users whose notification settings corresponding to the detected action are set to Off; wherein in step (d), when the detected action is a publication of the document or a change of permission policy associated with the document, the event notification sent to each receiving user include a list of one or more other users, and for each one of the plurality of actions that the receiving user has permission to take under the permission policy, the event notification contains an indication of whether or not each of the other users in the list has permission to take that action, and for each one of the plurality of actions that the receiving user does not have permission to take under the permission policy, the event notification contains an indication of the action but no indication of whether or not each of the other users in the list has permission to take that action. 11. The computer program product of claim 10 , wherein the plurality of actions include at least one of read, print and copy. 12. The computer program product of claim 10 , wherein the process further comprises: (e) obtaining user information that associates each user with a group, wherein in step (d), the event notifications are sent only to users whose no
for controlling access to devices or network resources · CPC title
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
for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title
Tools and structures for managing or administering access control systems · CPC title
Entity profiles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.