Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Integrating DRM


At its simplest level, digital rights management (DRM) technology is all about controlling access to information. Customers want convenient access to their purchased products, while companies seek to protect their intellectual property from unauthorized use or duplication. DRM sits squarely between these two parties, trying to present an amicable compromise between the customers and the vendor.

You could argue that hardware keys, software licenses, and serial numbers all fall under the DRM umbrella. However, the term more commonly refers to any of several advanced architectures for producing, providing, and protecting digital media. Although DRM infrastructures are sophisticated, they frequently employ familiar technologies like public key infrastructure (PKI), encryption, distributed architectures, Web storefronts, and various media formats.

Although there are several approaches to providing digital rights management, the most common one is outlined in the diagram, "Anatomy of a DRM Transaction." (See below.) Key aspects of an effective DRM system include:

  • data protection, so files aren't easily viewed without proper privileges;
  • unique identification of each customer to ensure that rights are applied appropriately;
  • central management of rights to allow for free distribution, anti-fraud measures, and revocation;
  • flexibility, so the system can be tailored to various business models (rental, ownership, and read-only, for example).

DRM has several advantages over traditional digital media protection schemes like passwords and watermarks. The path from the author to the customer can be very short, allowing individuals to publish their works online at a low cost. The media is usually well protected using encryption or some other means (but you would be hard-pressed to demonstrate that any given DRM protection scheme is impossible to crack). Furthermore, permissions for the protected media can be tailored to either restrict or allow various privileges, such as partial or preview viewing, printing, duplication, or time-limited rentals.

On the other hand, the DRM approach introduces some concerns and disadvantages that you must also consider. Because rights are generally managed on a central server, authorization often (but not always) requires access to a license management server via the Internet. In such a scenario, the server is a pivotal component of the key infrastructure.

The unique identification requirement poses problems as well. Customers will be concerned about their privacy, and will want to know if and how you're tracking their usage. DRM also often requires running specific proprietary software on the client machine to unlock protected media, like Windows Media Player, or another product compatible with Microsoft Windows Media Rights Manager framework.

Anatomy of a DRM Transaction: At its most basic, a DRM transaction starts with the content creator (a), who generates a piece of media (b), be it audio, video, text, or some other format. Once in digital form, the media file is encrypted to protect it from unauthorized use and stored on a server. Access to the file is managed by the license server, possibly in conjunction with a pay management system (c). Decrypted media might be delivered directly to a browser (d), or it could be decoded by the appropriate DRM-enabled software application (e). Either way, the result is fully licensed, digital-quality media file or stream reaching the customer (f).


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.