Abstract
To ensure secure content delivery, the Motion Picture Experts Group (MPEG) has dedicated significant effort to the digital rights management (DRM) issues. MPEG is now moving from defining only hooks to proprietary systems (e.g., in MPEG-2, MPEG-4 Version 1) to specifying a more encompassing standard in intellectual property management and protection (IPMP). MPEG feels that this is necessary in order to achieve MPEG's most important goal: interoperability. The design of the IPMP Extension framework also considers the complexity of the MPEG-4 standard and the diversity of its applications. This architecture leaves the details of the design of IPMP tools in the hands of applications developers, while ensuring the maximum flexibility and security. This paper first briefly describes the background of the development of the MPEG-4 IPMP Extension. It then presents an overview of the MPEG-4 IPMP Extension, including its architecture, the flexible protection signaling, and the secure messaging framework for the communication between the terminal and the tools. Two sample usage scenarios are also provided to illustrate how an MPEG-4 IPMP Extension compliant system works.
Highlights
If the encryption used to protect the video content is different from one intellectual property management and protection (IPMP) system to another, the consumer electronics (CE) manufacturers would have to build multiple versions of the Motion Picture Experts Group (MPEG)-4 terminal to deal with different protection systems used by different content providers
This paper introduces MPEG-4 IPMP Extension, the breakthrough technology standardized by MPEG for interoperable Digital rights management (DRM)
MPEG-4 IPMP Extension can be used in combination with proprietary tools, which enables the implementation of various degrees of security for different business models while maintaining the interoperability
Summary
With the advent of digital technologies, many new market opportunities have emerged for content owners, content distributors, and consumer electronics/information technology industries. When they are in their tent in the middle of the Gobi desert, Mr MPEG starts listening to his MIEP He finds a new hit that he feels is great and would like to share it by transferring that song to his wife’s MIEP (and, being a rule-abiding guy, he has acquired the rights to do so). Being the dictator of MPEG, Mr MPEG has the power to demand that IPMP Extension support transferring IPMP tools intended for one device to a device of a different make This would save the trip because otherwise his wife will start asking why he has spent all those years in MPEG if such a simple thing like moving a song from one MIEP to another is not possible and the discussion is likely to degenerate. We will show how these considerations have been addressed in MPEG-4 IPMP Extension
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call