Your browser is not supported. Please update it.

30 November 2005

DVB passes ‘major milestone’ in comprehensive TV protection

An enormously comprehensive model for protecting content has been laid down by the Digital Video Broadcasting project (DVB) encompassing every instance conceivable for delivering broadcast content and subsequently protecting it, including after it has been received, stored and copied to other devices.

The 103 page document published this week completely divorces the model for content protection and copy management (CPCM) from any specific technology and will produce technology guidelines later. This is the first standard effort focused on incorporating both mobile and portable devices and fixed broadcast devices like set tops, and to cover data translation between the two. DVB has standards for satellite, cable, terrestrial broadcast and mobile TV datacasting, and these new protection standards will apply to them all.

The publication of the DVB Bluebook A094 Content Protection & Copy Management (DVB-CPCM) is described by its authors as a major milestone towards a specification for persistent protection for commercial content in consumer digital products and home networks.

The model defines five content management operations (Acquisition, Storage, Processing, Consumption and Export) as abstract CPCM functions and goes on to say how they are controlled in a smart card based conditional access system or a digital rights management system and how each of them can be communicated across a home network.

The two core concepts are ‘authorized domains’ and ‘local environment’ and restrictions to copying or playing content can be put into either or both.

Copying can be restricted based on devices being too far away to be within a local environment or can be pre-registered to be part of a family grouping of devices in an authorized domain. By combining these two concepts and using proximity testing, DVB hopes to create a system where content can be shared by devices that occupy a local environment and also be shared by more remote devices such as mobile phones, PDAs or TVs at a family’s country home, of in-car devices, because they are part of an authorized domain.

This will be maintained by a series of complex key management functions which take in both embedded keys (access keys contained within the original piece of acquired content) or Out of Band content licenses, where the content license is securely stored in secret on a particular devices.

And yet all the time content can be scrambled and impossible to pirate without breaking an encryption key. Even the infamous analog hole gets some copy protection treatment within the document.

A wide variety of usage rules will be maintained by an intelligent Authorized Domain Manager, which looks like it will be in a set top or some such device, with rules like ‘Restrict playing to the Authorized Domain which acquired it ‘, or ‘Copy No More’ or ‘Copy Once,’ or the ability to tell storage devices not to retain a copy.

This Authorized Domain Manager looks like the real software platform here and will have access to metadata covering all usage state information including versioning for content licenses, a content identifier, a way of creating its own licenses, a record of how the content has been used so far, an identifier for each domain and descrambling keys.

Some devices are expected to be made aware enough to use device discovery to signal to each other and determine the presence of any authorized devices present in a home to make the creation of an authorized domain much easier.

The proximity testing will likely be linked to something like how long it takes to ‘ping’ an internet attached device, and will be defined in a later document, and is envisaged to be run either before any content exchange happens, or on a periodic or irregular basis.

If the other form of authorization is used, an Authorized Domain, then only CPCM compliant devices that are controlled by members of a single household can be attached and each attachment must happen manually, probably when the device is bought, and this makes no assumptions about the physical locations of the devices.

There are two consumption models anticipated under these far ranging protection services, one where content is consumed on a time based rental system and includes a ‘view from first playback’ 16-bit field which defines the number of 15-minute intervals up to as long as 1.87 years. So setting content to expire after 30 days or 2 hours is simply a single field setting.

The other consumption model allows for putting limits on the number of viewings or the number of times a piece of content can be copied.

There is even a setting for content that is allowed to leave the protection space entirely which is expected to be used on Creative Commons licenses or promotional clips.

An encryption toolbox will be specified in a future CPCM specification and will take in keys that are held on either each individual device or shared across an authorized domain, and there will be a specified revocation process to eliminate devices or entire domains from the key passing chain Again this has not yet been specified in detail, and neither has the key certification process, of the method of authorizing key exchanges.

The system allows for encryption keys to sit either entirely or partially within a smart card, or live solely on a piece of storage.

The document can be downloaded now from the CPCM page in the Technology section of the DVB website (www.dvb.org) and contains the first three elements of the CPCM specification: DVBCPCM Reference Model, DVB-CPCM Usage State Information, and DVB-CPCM Abbreviations, Definitions and Terms.

When completed, the full DVB-CPCM specification will be submitted to ETSI for standardization.

The Digital Video Broadcasting Project (DVB) is an industry-led consortium of over 250 broadcasters, manufacturers, network operators, software developers and regulatory bodies in over 35 countries.