# US 8,752,191 B2 · Generic digital rights management framework, and applications thereof > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,752,191 B2 - Document ID: US8752191B2 - Status: Granted - Kind: B2 - Application number: 12/121,636 - Filed: 2008-05-15 - Published: 2009-03-26 - Granted: 2014-06-10 - Earliest claimed: 2007-05-16 - Assignees: Broadcom Corporation - Applicants: Scott Krig - Inventors: Scott Krig - Web page: https://patentgrep.com/patent/US8752191B2 ## CPC - G06F 15/16: Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs {(coordinating program control therefor G06F9/52; in regulating and control system G05B)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Methods, systems and computer program products to implement generic Digital Rights Management (DRM) are provided herein. The methods include opening a session between an initiator and a responder, exchanging one or more of device and system information and sending one of an operation or event based on DRM capabilities, DRM partner, DRM authority, DRM characteristics, DRM Trust and CCEVS profiles. The operation includes one or more of a dataset, response code, operation parameter and response parameter. These extensions may be in the form of one or more of an operation, an event, a dataset or property code. ## Claims ### Claim 1 A method to exchange data on capabilities of a Digital Rights Management (DRM) system between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting capabilities of a DRM system deployed on the responder; and receiving, from the responder, in response to the operation, a dataset with the capabilities of the DRM system deployed on the responder, wherein the dataset indicates whether the DRM system deployed on the responder has a secure path for playing media content. ### Claim 2 (depends on 1) The method of claim 1, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 3 (depends on 1) The method of claim 1, wherein the dataset includes one or more of a DRM system identification, a DRM capability vendor, a DRM capability version, DRM capability features, DRM capability permissions and a DRM capability status. ### Claim 4 (depends on 1) The method of claim 1, wherein the dataset indicates whether the DRM system deployed on the responder is enabled to play media content. ### Claim 5 (depends on 4) The method of claim 4, wherein the media content includes at least one of a video, a resolution of the video, audio, e-books, images, and slides. ### Claim 6 (depends on 1) The method of claim 1, wherein the dataset indicates whether the DRM system deployed on the responder is allowed to render media content. ### Claim 7 (depends on 6) The method of claim 6, wherein the media content includes at least one of a video, a resolution of the video, audio, e-books, images, and slides. ### Claim 8 (depends on 1) The method of claim 1, further comprising: exchanging one or more of device and system information between the initiator and the responder. ### Claim 9 (depends on 1) The method of claim 1, wherein said operation includes one or more of a second dataset, a response code, an operation parameter, and a response parameter. ### Claim 10 A method to exchange data on capabilities of multiple Digital Rights Management (DRM) systems between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting capabilities of multiple DRM systems deployed on the responder; receiving, from the responder, in response to the operation, a dataset with a list of the capabilities of the multiple DRM systems deployed on the responder, wherein the dataset indicates whether the DRM systems deployed on the responder have a secure path for playing media content. ### Claim 11 (depends on 10) The method of claim 10 wherein the list includes capabilities of each of the multiple DRM systems deployed on the responder. ### Claim 12 (depends on 10) The method of claim 10, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 13 (depends on 10) The method of claim 10, wherein the list includes one or more DRM system capability datasets. ### Claim 14 (depends on 13) The method of claim 13, wherein each of the DRM system capability datasets includes one or more of a DRM system identification, a DRM capability vendor, a DRM capability version, DRM capability features, DRM capability permissions and a DRM capability status. ### Claim 15 (depends on 10) The method of claim 10, further comprising: exchanging one or more of device and system information between the initiator and the responder. ### Claim 16 (depends on 10) The method of claim 10, wherein said operation includes one or more of a second dataset, a response code, an operation parameter, and a response parameter. ### Claim 17 A method to exchange information on devices that share a Digital Rights Management (DRM) system between a first device and a second device operating under a data transfer protocol, comprising: opening a session between the first device and the second device; sending an operation from the first device to the second device requesting a list of devices that operate under a management of a common DRM management entity that supports DRM content sharing between the devices; and receiving, from the second device, in response to the operation, a dataset including the list of devices that operate under the management of the common DRM management entity; wherein the common DRM management entity resisters, authenticates, and manages each device's capability to share DRM protected content between the devices. ### Claim 18 (depends on 17) The method of claim 17, wherein the devices are computational devices in a home or office network and share the DRM system. ### Claim 19 (depends on 17) The method of claim 17, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 20 (depends on 17) The method of claim 17, wherein the dataset includes one or more of a partner link type, a partner link address, a partner alias name, a partner device type and partner sharing rights. ### Claim 21 (depends on 17) The method of claim 17, further comprising: exchanging one or more of device and system information between the initiator and the responder. ### Claim 22 (depends on 17) The method of claim 17, wherein said operation includes one or more of a second dataset, a response code, an operation parameter, and a response parameter. ### Claim 23 A method to exchange Digital Rights Management (DRM) authority characteristics between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting data on a DRM authority that registers, authenticates, and manages a capability of DRM partner devices to share DRM protected content between the DRM partner devices; and receiving, from the responder, in response to the operation, a DRM system identification and a dataset including characteristics of the DRM authority that indicate the capability of the DRM partner devices to share the DRM protected content between the DRM partner devices. ### Claim 24 (depends on 23) The method of claim 23, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 25 (depends on 23) The method of claim 23, wherein the dataset includes one or more of an authority link type, an authority link address, an authority alias name, an authority device type and authority rights granted. ### Claim 26 (depends on 23) The method of claim 23, further comprising: exchanging one or more of device and system information between the initiator and the responder. ### Claim 27 (depends on 23) The method of claim 23, wherein said operation includes one or more of a second dataset, a response code, an operation parameter, and a response parameter. ### Claim 28 A method to exchange Digital Rights Management (DRM) security level information between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting data on DRM security level information; and receiving, from the responder, in response to the operation, a dataset including data on DRM security level information of a DRM system implemented on the responder. ### Claim 29 (depends on 28) The method of claim 28, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 30 (depends on 28) The method of claim 28, wherein the dataset includes one or more of secure boot data, trusted clock data, device class data, cryptography hardware capabilities, secure components data, orange book level, device public key data, trusted authority address data and device address data. ### Claim 31 A method to exchange Common Criteria Evaluation and Validation Scheme (CCEVS) data between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting CCEVS data for a CCEVS system deployed on the responder; and receiving, from the responder, in response to the operation, a dataset with the CCEVS data for the CCEVS system deployed on the responder and whether a Digital Rights Management (DRM) system deployed on the responder is allowed to render media content. ### Claim 32 (depends on 31) The method of claim 31, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 33 (depends on 31) The method of claim 31, wherein the dataset includes one or more of a technology type, a profile name, a conformance claim, a protection profile version, an abbreviation sponsor and dates. ### Claim 34 (depends on 31) The method of claim 31, further comprising: exchanging one or more of device and system information between the initiator and the responder. ### Claim 35 (depends on 31) The method of claim 31, wherein said operation includes one or more of a second dataset, a response code, an operation parameter, and a response parameter. ### Claim 36 A method to exchange data on multiple Common Criteria Evaluation and Validation Scheme (CCEVS) systems between an initiator and a responder operating under a data transfer protocol, comprising: opening a session between the initiator and the responder; sending an operation from the initiator to the responder requesting a list of multiple CCEVS systems deployed on the responder; and receiving, from the responder, in response to the operation, a dataset with the list of the multiple CCEVS systems deployed on the responder and whether a Digital Rights Management (DRM) system deployed on the responder is allowed to render media content. ### Claim 37 (depends on 36) The method of claim 36, wherein, the list includes datasets for each of the multiple CCEVS systems deployed on a responder. ### Claim 38 (depends on 36) The method of claim 36, wherein the data transfer protocol is one of a Media Transport Protocol (MTP) or a Picture Transfer Protocol (PTP). ### Claim 39 (depends on 36) The method of claim 36, wherein the list includes CCEVS protection profiles for each CCEVS system deployed on the responder. ### Claim 40 (depends on 39) The method of claim 39, wherein each of the CCEVS protection profiles includes one or more of a technology type, a profile name, a conformance claim, a protection profile version, an abbreviation sponsor and dates.