Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
  • G06F21/107—License processing; Key processing
  • G06F21/1073—Conversion
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
  • H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
  • H04N21/4623—Processing of entitlement messages, e.g. ECM [Entitlement Control Message] or EMM [Entitlement Management Message]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
  • H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
  • H04N21/4627—Rights management associated to the content

Definitions

• DRM Digital rights management
• a mapping layer is provided to translate DRM system requirements from one DRM system, such as a source DRM system, to another DRM system, such as a target DRM system.
• DRM system requirement translation is performed using a signed data structure that maps DRM system requirements from one DRM system to one or more other DRM systems.
• FIG. 1 illustrates an operating environment in accordance with one or more embodiments.
• FIG. 2 illustrates an example data structure in accordance with one or more embodiments.
• FIG. 3 illustrates a system in accordance with one or more embodiments.
• Fig. 4 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
• Fig. 5 is a block diagram of an example system that can be utilized to implement one or more embodiments.
• a mapping layer is provided to translate DRM system requirements from one DRM system, such as a source DRM system, to another DRM system, such as a target DRM system.
• DRM system requirement translation is performed using a signed data structure that maps DRM system requirements from one DRM system to one or more other DRM systems.
• Example Data Structure describes an example data structure in accordance with one or more embodiments.
• Example Method describes an example method in accordance with one or more embodiments.
• Example System describes an example system that can be utilized to implement one or more embodiments.
• Fig. 1 illustrates an operating environment in accordance with one or more embodiments, generally at 100.
• Operating environment 100 includes multiple different computing devices, examples of which are shown at 102, 104, 106, and 108.
• Individual computing devices or components associated therewith can typically include one or more processors 110, one or more computer-readable media 112, an operating system 114 and one or more applications 116 that reside on the computer-readable media and which are executable by the processor(s).
• Such applications can include, by way of example and not limitation, a media playing application or any other type of application that can enable distributed content to be consumed by a user.
• the computing devices can also include a digital rights management (DRM) system 117 that includes a DRM agent.
• DRM digital rights management
• the DRM agent is typically responsible for enforcing policy that is described in a particular license associated with content that can be received and consumed by the computing device.
• the computer-readable media can include, by way of example and not limitation, all forms of volatile and non- volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like.
• environment 100 includes a network 118, such as a local network or the Internet. The network can be utilized to receive DRM-protected content and associated licenses.
• Operating environment 100 also includes, in at least some embodiments, an entity that provides a data structure that can be utilized to map DRM system requirements.
• entity takes the form of a trusted DRM service or server 120 that can generate and provide a data structure that can be utilized by the various computing devices to translate DRM system requirements from one DRM system to another, as will become apparent below.
• the computing devices can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer (such as computing device 106), a portable computer (such as computing device 104), a handheld computer such as a personal digital assistant (such as computing device 102), a television that may or may not include a set-top box (such as computing device 108), and the like.
• a computing device is shown and described below in relation to Fig. 5.
• Fig. 2 illustrates an example data structure in accordance with one or more embodiments generally at 200.
• data structure 200 is referred to as a Revocation Information Structure or "Revlnfo Structure”.
• Revocation information version refers to a number included in DRM policy that identifies a particular version of revocation data.
• Revocation data refers to version numbers, certificate revocation lists, system renewability messages or other data utilized to execute revocation, as will be appreciated by the skilled artisan.
• Data structure 200 includes, in one or more embodiments, a revocation information version 202 and associations between various DRM systems and corresponding system version numbers.
• association 204 defines an association between "DRM system 1" and “Version 1.0”
• association 206 defines an association between “DRM system 2” and “Version 3.0”
• association 208 defines an association between "DRM system 3” and "Version 2.0”.
• “DRM system 1” might correspond to Microsoft's PlayReady DRM system
• “DRM system 2” might correspond to RealNetworks' Helix DRM system and so on.
• the version numbers described in the associations 204, 206 and 208 are seen to comply with or otherwise satisfy system requirements associated with the revocation information version number.
• the structure 200 provides a mapping layer that can translate DRM system requirements from one DRM system to another, such as a DRM system that might be present on a source DRM system and a DRM system that might be present on a target transferee, such as a different target DRM system.
• data structure 200 can be signed and issued to a client computing device by a DRM service, such as DRM service 120 in Fig. 1. Once issued, the client computing device can utilize data structure 200 to ensure that computing devices or target transferees to which DRM- protected content and licenses may be transferred have DRM systems that are compliant with requirements established by the DRM service.
• FIG. 3 illustrates a system in accordance with one or more embodiments generally at 300.
• System 300 includes, in this example, a DRM service 302, a first client computing device 304 having a first DRM system, designated "DRM System 1", and a target transferee in the form of a second client computing device 306 having a second different DRM system, designated "DRM System 2".
• DRM service 302 In operation, in at least some embodiments, DRM service 302 generates, signs and issues a Revlnfo structure 308.
• Structure 308 includes a RIV number and various associations between DRM systems and system version numbers as described above.
• client computing device 304 receives Revlnfo structure 308.
• the Revlnfo structure 308 is processed by a DRM agent executing on client computing device 304. Part of this processing can include validating the signature on the Revlnfo structure. If the signature validates, then the DRM agent can assume that the various associations described in the Revlnfo structure are valid.
• license 310 can include various policies associated with the DRM -protected content, a RIV number for DRM system 1, and a content key.
• the DRM agent evaluates the license by ascertaining the license's RIV number and checking the license's RIV number against the RIV number contained in Revlnfo structure 308. If the license contains a valid RIV number, and DRM System 1 has a version that is the same as or newer than one described in an association appearing in Revlnfo structure 308, client computing device 304 can use the license to consume the associated DRM-protected content.
• client computing device 304 wishes to transfer the DRM-protected content to client computing device 306.
• the DRM agent executing on client computing device 304 queries the DRM system on client computing device 306 to ascertain its version number. If client computing device 306' s DRM version number is contained in an association described in Revlnfo structure 308 (or, in at least some embodiments, newer than the one described in the
• the license can be transferred to client computing device 306. If, on the other hand, the DRM version number of the DRM system executing on client device 306 does not match or otherwise favorably compare with a version number described in Revlnfo structure 308, the license is not transferred. [0028] In this manner, DRM licenses can be transferred from one system to another in situations where the systems are executing different DRM systems. License transfer is made possible, in this example, through the use of the signed Revlnfo structure 308 that was received by client computing device 304. [0029] Having considered an example use of a data structure in accordance with one or more embodiments, consider now a method that can be implemented using the systems described above.
• Fig. 4 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
• the method can be implemented in connection with any suitable hardware, software, firmware, or combination thereof.
• aspects of the method can be implemented by a suitably- configured DRM service. As such, those aspects are designated "DRM Service”.
• aspects of the method can be implemented by a suitably-configured client computing device. As such, those aspects are designated "Client Computing Device”.
• Step 400 generates an Revlnfo structure. Examples of a suitable Revlnfo structure are provided above.
• Step 402 signs the Revlnfo structure. This step can be accomplished by signing the structure with a private key associated with the DRM service.
• Step 404 sends the Revlnfo structure to a client computing device.
• Step 406 receives the Revlnfo structure. After receiving the Revlnfo structure, the client computing device or, more accurately, a suitably-configured DRM agent executing on the client computing device can verify the authenticity of the Revlnfo structure. This can be done, for example, by using a public key associated with the private key that was used to sign the Revlnfo structure.
• Step 408 receives a request to transfer a license associated with DRM-protected content.
• This step can be performed in any suitable way. For example, a user operating the client computing device may wish to transfer DRM-protected content to another computing device or to another application executing on the current client computing device.
• Step 410 ascertains a version number of a DRM system on a target transferee.
• a target transferee can include by way of example and not limitation, another computing device or an application executing on the current computing device.
• Step 412 ascertains whether the version number of the target transferee is equal to or newer than a version number contained in the Revlnfo structure. The step can be performed by comparing the version number of the target transferee with a version number contained in an association or mapping described in the Revlnfo structure. If the version number of the target transferee is equal to or newer than a version number in the Revlnfo structure, then step 414 transfers the license to the target transferee.
• step 416 does not transfer the license.
• licenses can be transferred between systems that employ different DRM systems.
• the license generated for the target transferee states its version number as mapped using the data structure for the source DRM system. By using mappings that are described in the Revlnfo structure, DRM system requirements can be confirmed to meet with requirements promulgated by the DRM service.
• FIG. 5 illustrates an example computing device 500 that can implement the various embodiments described above.
• Computing device 500 can be, for example, various computing devices or servers, such as those illustrated in Fig. 1 or any other suitable computing device.
• Computing device 500 includes one or more processors or processing units 502, one or more memory and/or storage components 504, one or more input/output (I/O) devices 506, and a bus 508 that allows the various components and devices to communicate with one another.
• Bus 508 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
• Bus 508 can include wired and/or wireless buses.
• Memory/storage component 504 represents one or more computer storage media.
• Component 504 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth).
• Component 504 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).
• One or more input/output devices 506 allow a user to enter commands and information to computing device 500, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth.
• output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.
• a display device e.g., a monitor or projector
• speakers e.g., a speaker
• printer e.g., a printer
• network card e.g., a network card
• output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.
• Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media.
• Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise "computer storage media".
• Computer storage media include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.
• Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
• a mapping layer is provided to translate DRM system requirements from one DRM system, such as a source system, to another DRM system, such as a target system.
• DRM system requirement translation is performed using a signed data structure that maps DRM system requirements from one DRM system to one or more other DRM systems.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Multimedia (AREA)
• Computer Security & Cryptography (AREA)
• Databases & Information Systems (AREA)
• Technology Law (AREA)
• Computer Hardware Design (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Signal Processing (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Storage Device Security (AREA)
• Machine Translation (AREA)
• Document Processing Apparatus (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (2)

Family

ID=41398794

Family Applications (1)

Country Status (7)

Cited By (2)

Families Citing this family (3)

Citations (1)

Family Cites Families (31)

• 2008
  • 2008-06-04 US US12/133,354 patent/US8095518B2/en active Active
• 2009
  • 2009-05-29 EP EP09759118A patent/EP2308001A4/en not_active Ceased
  • 2009-05-29 RU RU2010149878/08A patent/RU2010149878A/ru unknown
  • 2009-05-29 WO PCT/US2009/045670 patent/WO2009148957A2/en not_active Ceased
  • 2009-05-29 JP JP2011512546A patent/JP5497017B2/ja not_active Expired - Fee Related
  • 2009-05-29 KR KR1020107027039A patent/KR101618385B1/ko active Active
  • 2009-05-29 CN CN200980121351.5A patent/CN102057380B/zh active Active

Patent Citations (1)

Also Published As

Similar Documents

Legal Events