Towards a software architecture for DRM

ABSTRACT

The domain of digital rights management (DRM) is currently lacking a generic architecture that supports interoperability and reuse of specific DRM technologies. This lack of architectural support is a serious drawback in light of the rapid evolution of a complex domain like DRM. It is highly unlikely that a single DRM technology or standard will be able to support the diversity of devices, users, platforms, and media, or the wide variety of system requirements concerning security, flexibility, and efficiency. This paper analyses state-of-the-art DRM technologies and extracts from them high level usage scenarios according to content consumers, producers, and publishers. In addition, the key services are identified both from a functional and security perspective. Identifying key DRM services and locating them in an overall structure brings us one step closer to a software architecture for DRM. Having available a software architecture should help the DRM community in reasoning about DRM systems, and in achieving reuse and interoperability of multiple domain-specific DRM technologies and standards.

REFERENCES

• 1: Aegis DRM. http://www.aegisdrm.com/.
• 2: Ross Anderson, Cryptography and competition policy: issues with 'trusted computing', Proceedings of the twenty-second annual symposium on Principles of distributed computing, p.3-10, July 13-16, 2003, Boston, Massachusetts [doi>10.1145/872035.872036]
• 3: Len Bass , Paul Clements , Rick Kazman, Software architecture in practice, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 4: S. Chow, P. A. Eisen, H. Johnson, and P. C. van Oorschot. A White-Box DES Implementation for DRM Applications. In Proceedings of ACM Workshop on Digital Rights Management (DRM2002), pages 1--15, Washington DC, USA, Nov 2002.
• 5: D. Clark, The design philosophy of the DARPA internet protocols, ACM SIGCOMM Computer Communication Review, v.18 n.4, p.106-114, August 1988
• 6: K. Coyle. Rights expression languages. Technical report, A Report for the Library of Congress, Feb. 2004. http://www.loc.gov/standards/.
• 7: John S. Erickson, Fair use, DRM, and trusted computing, Communications of the ACM, v.46 n.4, April 2003 [doi>10.1145/641205.641228]
• 8: Fraunhofer Institute. Light Weight DRM (LWDRM). http://www.lwdrm.com/.
• 9: S. Guth. Rights Expression Languages. In E. Becker, W. Buhse, D. Günnewig, and N. Rump, editors, Digital Rights Management: Technological, Economic, Legal and Political Aspects, volume 2770 of LNCS, pages 101--112. Springer, Nov. 2003.
• 10: Bill Horne , Lesley R. Matheson , Casey Sheehan , Robert Endre Tarjan, Dynamic Self-Checking Techniques for Improved Tamper Resistance, Revised Papers from the ACM CCS-8 Workshop on Security and Privacy in Digital Rights Management, p.141-159, November 05, 2001
• 11: IBM. IBM Electronic Media Management System (EMMS). http://www-306.ibm.com/software/data/emms.
• 12: Pramod A. Jamkhedkar , Gregory L. Heileman, DRM as a layered system, Proceedings of the 4th ACM workshop on Digital rights management, October 25-25, 2004, Washington DC, USA [doi>10.1145/1029146.1029151]
• 13: Gregor Kiczales , John Lamping , Christina Videira Lopes , Chris Maeda , Anurag Mendhekar , Gail Murphy, Open implementation design guidelines, Proceedings of the 19th international conference on Software engineering, p.481-490, May 17-23, 1997, Boston, Massachusetts, United States [doi>10.1145/253228.253431]
• 14: Wenbo Mao, Modern Cryptography: Theory and Practice, Prentice Hall Professional Technical Reference, 2003
• 15: S. Michiels. Component Framework Technology for Adaptable and Manageable Protocol Stacks. PhD thesis, K.U.Leuven, Dept. of Computer Science, Leuven, Belgium, Nov. 2003.
• 16: Microsoft Corporation. Windows Media DRM (WMDRM), 2005.
• 17: Deirdre K. Mulligan, Introduction, Communications of the ACM, v.46 n.4, April 2003 [doi>10.1145/641205.641227]
• 18: OMA. Open mobile alliance. http://www.openmobilealliance.org.
• 19: Real Networks. Helix DRM. http://www.realnetworks.com/products/drm.
• 20: M. Reed, P. Syverson, and D. Goldschlag. Anonymous connections and onion routing. IEEE Journal on Selected Areas in Communication Special Issue on Copyright and Privacy Protection, 16(4):482--494, May 1998.
• 21: Clemens Szyperski, Component software: beyond object-oriented programming, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1998
• 22: The International DOI Foundation. The Digital Object Identifier (DOI). http://www.doi.org/, June 2005.
• 23: Matt Welsh , David Culler, Virtualization Considered Harmful: OS Design Directions for Well-Conditioned Services, Proceedings of the Eighth Workshop on Hot Topics in Operating Systems, p.139, May 20-22, 2001
• 24: G. Wroblewsky. General Method of Program Code Obfuscation. PhD thesis, Wroclaw University of Technology, Feb. 2002.

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.5 LEGAL ASPECTS OF COMPUTING
      K.5.1 Hardware/Software Protection
          Subjects: Licensing

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Domain-specific architectures
        D.2.13 Reusable Software
            Subjects: Domain engineering

  K. Computing Milieux
  K.5 LEGAL ASPECTS OF COMPUTING
      K.5.1 Hardware/Software Protection
          Subjects: Proprietary rights

General Terms:
Design, Security, Standardization

Keywords:
DRM, software architecture