Protected Interoperable File Format (PIFF) The Athens Project - - PowerPoint PPT Presentation

Protected Interoperable File Format (PIFF)

The “Athens” Project

Microsoft Corporation September 23, 2009

• J. Simmons, M. Jeffrey

TM4299 rev1

Agenda

• A vision of the future
• The digital rights management dilemma
• Protected interoperable file format (PIFF)
• PIFF supported scenarios
• PIFF feature summary
• Protection System Specific Header box
• Track Encryption box
• Sample Encryption box
• References

A Vision of the Future

Portable, protected online video content

• Will be accessible on all endpoints
• Will enable all key consumption scenarios

Ubiquitous content protection

• Will meet requirements of content providers
• Will support interoperability between manufacturers
• Will support extensibility for new manufacturers

Supply chain optimised

• The key to online video market expansion
• Will prevent a hodgepodge of walled gardens

Hi Def.

PlayRead y Marlin OMA DRM Other

Std Def.

PlayRead y Marlin OMA DRM Other

Low Def.

PlayRead y Marlin OMA DRM Other

Mobil e

PlayRead y Marlin OMA DRM Other

Cost of Encoding a TV Episode

Containe r & Encrypti

• n

DRM Interoperability is achieved by standardising the container & encryption.

The Digital Rights Management Dilemma

Implementations are always proprietary, so how to make interoperable? 23/9/2009 Microsoft Corporation 5

Containe r & Encrypti

• n

Rights Expressi

• n

Languag e Licensin g Regime Key Mgt System

Ease of Standardisation

Difficult Easy Nearly standardised

• today. Easy.

Always present & proprietary. Tied to compliance rules

• f licensing

regime Tied to authentication of licensing regime.

Protected Interoperable File Format (PIFF)

23/9/2009 Microsoft Corporation 6

• Standardisation of the encryption

algorithm (AES-128, CTR or CBC mode)

• Generalisation of the ISO Base Media File

Format “Scheme Signaling” mechanism to cover multiple DRM systems

• Support for all key use scenarios to

address the supply chain optimisation problem.

Hi Def.

PIF F

Std Def.

PIF F

Low Def.

PIF F

Mobile

PIF F

Optimising the Supply Chain

• Also, the same format can be used for both

streaming and download (e.g. rental or download to own)

• Studios can afford to encode more titles
• Ecosystem becomes richer, more interoperable,

and much more convenient for consumers

PIFF Supported Scenarios

23/9/2009 Microsoft Corporation 8

• Adaptive bit rate streaming
• Second session or digital copy
• Internet download
• Progressive download and playback
• Side loading onto portable devices
• DRM interoperability and extensibility
• Late binding/muxing of alternate tracks
• Client targeted advertising

PIFF Feature Summary

23/9/2009 Microsoft Corporation 9

• Seamless adaptive bit rate streaming using

fragmented form of ISO Base Media File Format

• Multiple DRM support using a standard

encryption method and addition of three “uuid” boxes

– Protection System Specific Header Box – Track Encryption Box – Sample Encryption Box

Protection System Specific Header Box

23/9/2009 Microsoft Corporation 10

File Type ('ftyp')

Movie ('moov')

Movie Header ('mvhd') Protectio n System Specific Header ('uuid') Track ('trak') x [# tracks] ... Movie Extends ('mvex') Movie Extends Header ('mehd') Track Extends ('trex') Fragment x [# fragments] Movie Fragment Random Access ('mfra') Track Fragment Random Access ('tfra') x [# tracks] Movie Fragment Random Access Offset ('mfro')

The Protection System Specific Header Box contains the data needed by a Content Protection System to play back the content. There can be any number of these boxes, added at any time.

Track Encryption Box

23/9/2009 Microsoft Corporation 11

Original Sample Entry with protected type Protection Scheme Info ('sinf')

Original Format Box ('frma') Scheme Type Box ('schm') Scheme Information Box ('schi') Track Encryption Box The Track Encryption box contains default values for the AlgorithmID, IV_size, and KID for the entire track. All Content Protection Systems use the same encryption algorithm. There is no DRM-Specific metadata at the track or sample level.

Movie Fragment ('moof')

Movie Fragment Header ('mfhd') Track Fragment ('traf')

Track Fragment Header ('tfhd') Track Fragment Run ('trun')

Independent and Disposable Samples ('sdtp')

Sample Encryptio n

Media Data ('mdat' )

Sample Encryption Box

The Sample Encryption Box contains the sample specific encryption data, including whether the sample is encrypted or not.

References

• Smooth Streaming Transport Protocol,

http://learn.iis.net/page.aspx/684/smooth-streaming- transport-protocol/

• Protected Interoperable File Format (PIFF),

http://learn.iis.net/page.aspx/685/protected- interoperable-file-format/

• Microsoft Community Promise,

http://www.microsoft.com/interop/cp/default.mspx

Standardisation Plans

• PIFF was announced at IBC, and is available on the web
• License is open to all and royalty-free

– See the Microsoft Community Promise for details

• Microsoft intends to work with others to seek formal standardisation of

both PIFF and the associated Smooth Streaming protocols

• Exactly where these standards would be developed is not yet decided;

however DVB is one possibility

• Companies interested in taking these ideas forward should contact

mark.jeffrey@microsoft.com

Thank You

M

23/9/2009 Microsoft Corporation 15