Sun Microsystems is focusing heavily on the open source DRM (digital rights management) market, with a completely new vision of how DRM should work and a bid to provide the standard for the content rich handset market, where it can ride on the success of Java.
Sun seems to be running at least six months ahead of schedule with its DReaM (DRM Everywhere Available) open source DRM, which was not due to be completed until mid-2007, having already signed up Korean IPTV company Alticast. Sun says it is still between nine and 15 months away from a product, but since this is based on an open source process, code exists already for most of the system.
Last week the vendor released the source code for two components of DReaM, the DReaM-CAS (Conditional Access System), which currently works only with the MPEG-2 format, and DReaM-MMI (Mother May I) the underlying mechanism for always asking a central resource for permission to access content.
Sun plans to create a royalty-free, interoperable DRM technology, independent of any specific hardware or operating systems, and focusing on the concept of a user being given access to content, rather than one specific device being authenticated. This is something that may come more easily to Sun, since it can rely on the Liberty Alliance initiative in which it is a key player (as is Nokia), and which provides the means for a single copy of a person’s identity to act as a trust source for other services, without ever having to reveal that identity to other services.
Sun will have version 1.0 of its DReaM MMI software out by the summer and will then launch straight into building a compliance organization under the Common Development and Distribution License (CDDL) that came out of the Mozilla development process. And next month at its Java One conference in San Francisco Sun will demonstrate using the next generation Java SIM smartcard, the upgrade to the one that is used in most mobile handsets phones today, as a basis for identity in an IPTV set-up.
The one big innovation that Sun has brought to this system is the use of the Liberty Alliance ideas on identity, allowing a single copy of a person’s true identity to reside securely on a network and supporting communication between servers to track this identity and offer services to multiple devices the identity owns or uses. At Java One Sun will show a phone being used to prove its proximity to a set-top, and authorize the delivery of content to the owner of a phone, over a separate TV network.
What Sun hopes to end up with is an architecture which separately delivers authentication, licensing, rights management, and protection technologies under the same framework by disintermediating each of those functions. Usage rights will be defined as a separate license management system, allowing the unmodified use of players and DRM clients which are already installed on devices. In this way Sun hopes to retrofit onto existing systems a whole variety of new usage models, that were not previously possible.
Analysts from Wireless Watch’s sister service, Faultline, which focus on broadband digital media and the triple play, talked last week to Tom Jacobs, director of engineering at the Sun Labs, Open Media Commons project on DReaM, who agreed that perhaps Sun had missed an earlier opportunity to get the message out there on its approach to DReaM.
But will this be another technology that Sun fails to dominate, despite creating the opportunity, as it largely has in Java? ‘We understand just how important DRM is going forwards. We were brought into this debate by the cellular community that is worried that it will end up with a huge royalty bill for DRM,’ said Jacobs.’We’ve had the codec wars, and the network protocol wars, and every other technology in pay TV is free and standard except for conditional access.’
Sun has contributed a lot of work towards the Java-based standard OCAP/MHP set-top environment, which is only just rolling out onto cable and other TV networks.
‘There has been a smear campaign by traditional conditional access suppliers to try to put fear, uncertainty and doubt into AES-based DRM systems, suggesting they are not as secure as those already in place, but funnily enough conditional access specialist NDS was one of the first companies to download the source code,’ said Jacobs.
Does that mean that NDS might contribute to the open source process for a royalty free DRM system? ‘Anything that NDS contributes will become royalty free, so we don’t expect any of its core technology to be offered up. Maybe they are just interested in seeing what they may be up against in the future.’
So how do you go about navigating the CDDL process in a world that is full of patents and litigation over patent infringements?
Jacobs explained: ‘The DCAS technology is already pretty well cleared legally. Many of the lawyers that worked on the Digital Cinema Initiative also joined up to work on this, doing both a claims analysis and a technical analysis. Some of the technology in here was patented back in the 1970s for the first round of pay TV and has since expired. There is pre-existing IP such as PKI (Public Key Infrastructure) and AES has always been offered royalty free and was mandated as such by the National Institute of Standards and Technology when it was developed.
‘We don’t want to develop technology that is wholly different, we just want it to be simple, sufficient, and to make sure we can cite all the prior art. Some of the new technology comes from Sun, but we are committing that to be royalty free as well, which is one of the conditions for contributions made under the CDDL. It’s a form of patents commons, where each contributor agrees to pool intellectual property. A company can’t both include their contribution in code and also charge a license for it.’
The CDDL allows for commercial implementations and for companies to benefit commercially and improve upon the code, both with changes to the code and additional segments of code which they add to it.
First talked about in October, DReaM was not supposed to be ready for implementation until the second quarter of 2007, and as such was likely to miss out on being a candidate for mobile handset DRM standards, but at its current pace of development, and with Java dominant on high end phones, the lure of zero royalty payouts for protection of handset content is likely to be too tempting for many mobile operators around the world.