Systems and methods for third-party interoperability in secure network transactions using tokenized data
US-2024348616-A1 · Oct 17, 2024 · US
US9836702B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9836702-B2 |
| Application number | US-25240408-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 16, 2008 |
| Priority date | Oct 16, 2008 |
| Publication date | Dec 5, 2017 |
| Grant date | Dec 5, 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 method operative at an identity provider enforces a digital rights management (DRM) scheme associated with a piece of content. The identity provider is an entity that participates in a “federation” with one or more other entities including, for example, an service provider (e.g., a content provider), a DRM privileges provider, and a DRM policy provider. In one embodiment, the method begins by having the identity provider obtain and evaluate against a DRM policy a set of DRM privileges associated with the end user requesting access to the piece of content. Based on the evaluation, the identity provider generates a single sign on (SSO) message that includes a reference to the set of DRM privileges. The message is then forward to the service provider entity, which provides the end user a response.
Opening claim text (preview).
I claim: 1. A method for enforcing a digital rights management (DRM) scheme associated with a piece of content, wherein an identity provider entity together with a service provider entity participate in a federation, comprising: at an identity provider entity that includes a hardware element: upon authentication of the end user to the identity provider entity, receiving a request to single sign-on to the service provider entity to attempt to obtain the piece of content; during processing of the request to single sign-on to the service provider entity, determining a DRM policy that is enforced at the service provider entity, determining a set of one or more DRM privileges associated with the end user requesting access to the piece of content, and based on the DRM policy and the set of one or more DRM privileges so determined, evaluating against the DRM policy the set of one or more DRM privileges, wherein the evaluating step is carried out using the hardware element; during processing of the request to single sign-on to the service provider entity, based on the authentication of the end user and a result of the evaluation, generating a single sign-on message that includes a reference to the set of one or more DRM privileges associated with the end user requesting access to the piece of content, wherein the single sign-on message is generated using the hardware element; and forwarding to the service provider entity the single sign-on message that includes the reference to the set of one or more DRM privileges to complete the processing of the request to single sign-on to the service provider entity, wherein the single sign-on message is forwarded from the identity provider entity to the service provider entity via a redirection mechanism; wherein evaluating DRM policy based on the determined DRM privileges during the single sign-on request processing flow provides an improved identity provider entity. 2. The method as described in claim 1 wherein the DRM policy is available locally at the identity provider entity. 3. The method as described in claim 1 wherein, when the DRM policy is not available locally at the identity provider entity, the method further includes the steps of: generating a DRM policy evaluation request that includes the set of one or more DRM privileges; forwarding the DRM policy evaluation request to an entity in the federation; and receiving a response to the DRM policy evaluation request. 4. The method as described in claim 3 wherein the response to DRM policy evaluation request indicates that access to the given piece of content is permitted. 5. The method as described in claim 1 wherein the set of one or more DRM privileges are available locally at the identity provider entity. 6. The method as described in claim 1 wherein, when the set of one or more DRM privileges are not available locally at the identity provider entity, the method further includes obtaining the set of one or more DRM privileges from an entity in the federation. 7. The method as described in claim 1 wherein, when the set of one or more DRM privileges are not available locally at the identity provider entity, the method further includes obtaining the set of one or more DRM privileges from the user. 8. The method as described in claim 7 wherein the set of one of more DRM privileges are obtained from the user directly. 9. The method as described in claim 7 wherein the set of one or more DRM privileges are obtained by having user cause a third entity to provide the set of one or more DRM privileges to the identity provider. 10. The method as described in claim 1 further including: receiving the set of one or more DRM privileges from a third entity in the federation; generating a DRM policy evaluation request that includes the set of one or more DRM privileges; forwarding the DRM policy evaluation request to a fourth entity in the federation; and receiving a response to the DRM policy evaluation request from the fourth entity. 11. The method as described in claim 10 wherein the third entity provides a service of managing the set of one or more DRM privileges on behalf of users within the federation. 12. The method as described in claim 10 wherein the fourth entity provides a service of managing DRM policy within the federation. 13. The method as described in claim 10 wherein the third and fourth entity are a single entity within the federation that manages the set of one or more DRM privileges on behalf of users and also manages DRM policy within the federation. 14. The method as described in claim 1 wherein the message includes a pointer to an assertion containing the set of one or more DRM privileges associated with the end user, and wherein the identity provider requests an exchange of the pointer for the assertion to obtain the set of one or more DRM privileges. 15. The method as described in claim 1 wherein the piece of content has an associated DRM license, distinct from the DRM privileges, the DRM license comprising a decryption key, a set of rights, and an identifier of a device associated with the end user and upon which the piece of content is permitted to be rendered.
using certificates · 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
where a single sign-on provides access to a plurality of computers · CPC title
Administration; Management · CPC title
including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.