accelerating media business developments

Accelerating Media Business Developments

Christian Timmerer

Klagenfurt University (UNI-KLU) Faculty of Technical Sciences (TEWI)

Department of Information Technology (ITEC) Multimedia Communication (MMC)

http://research.timmerer.com http://blog.timmerer.com mailto:[email protected]

MPEG-M: MPEG Extensible Middleware

AcknowledgmentsL. Chiariglione, F. Chiariglione

M. Preda, M. Eberhard, I. Arsov, A. Defino

http://mxm.wg11.sc29.org/[email protected]

http://wg11.sc29.org/mxmsvn/repos

What if …

• … one does not need in-depth knowledge of specific MPEG technologies / standards?

• … one is able to start with application/business development as soon as some (reference) software becomes available?

• … one is able to exchange applications’ underlying (reference) software with optimized one at no cost?

2009/10/31 Christian Timmerer, Klagenfurt University, Austria 2

Outline

• Introduction – Overview

• Architecture

• Application Programming Interface (API)

• Example Instantiations

– Fully Interoperable Streaming

– [Including MPEG-4 3D Graphics

– Sharing Protected Contents]

• [Conclusions – References]


Introduction – Overview

• A set of APIs to access possibly all MPEG technologies

• Simple methods to call complex functionalities inside MXM engines

• “Thin” applications because the complexity is in the MXM engines

• Replacement of MXM engines with better performing ones at no cost

• Creation of a global market of MXM Engines, MXM Applications and MXM Devices


Introduction – Overview (cont’d)

The MXM standard – ISO/IEC 23006 – is subdivided in four parts:• Part 1 - MXM Architecture and Technologies specifies the MXM

architecture and references the technologies that are part of an MXM implementation;

• Part 2 - MXM Application Programming Interfaces (APIs): specifies the MXM APIs;

• Part 3 - MXM Conformance and Reference Software: specifies conformance tests and the software implementation of the standard

• Part 4 – MXM Protocols: specifies a set of protocols enabling distributed applications to exchange information related to content items and parts thereof, including rights and protection information


MXM Application 1 MXM Application 2

MPEG21 File Engine

Digital ItemEngine

REL Engine

IPMPEngine

ContentMetadata

Engine

MediaFramework

Engine

Drivers, Accelerators, Controllers, etc.

OS

MXMEngine

APIs

OtherEngines

HW

SceneEngine

SecurityEngine

MXM Device

72009/10/31 Christian Timmerer, Klagenfurt University, Austria

MXM Application 3 MXM Application 1 MXM Application 2

MPEG21 File Engine

Digital ItemEngine

REL Engine

IPMPEngine

ContentMetadata

Engine

MediaFramework

Engine

Drivers, Accelerators, Controllers, etc.

OS

OrchestratorEngine

MXMOrchestrator

API

OtherEngines

HW

SceneEngine

SecurityEngine

MXM Device


MXM Protocols

ContentCreationDevice

End-UserDevice

ContentIdentific.Device

ContentProviderDevice

LicenseProviderDevice

DRM ToolProviderDevice 92009/10/31 Christian Timmerer, Klagenfurt University, Austria

OSMXM

MXM Application

OSMXM

MXM Application

Computing Platform Computing Platform

Enabling MXM Apps to communicate


An impressive number of standards…

Rights Expression Language

Intellectual Property Management and Protection

Reconfigurable Video Coding Event Reporting

IPMPX

Advanced Audio Coding

Audio Lossless Coding File Format

BIFS

LASeR

Digital Item Declaration

HE AAC

MPEG-7 Visual

MDS

Digital Item Identification

Digital Item Processing

Media Value Chain Ontology

XML IPMP messagesDigital Item Streaming

IPMP Components

Digital Item Adaptation MPQF


Motivation of providing API

• MPEG specifications: huge amount of technology– 157 standards in ISO/IEC 14496 (MPEG-4) family

– 43 standards in ISO/IEC 15938 (MPEG-7) family

– 33 standards in ISO/IEC 21000 (MPEG-21) family

– …

• Around 11 000 pages, 1,5 m high when printed

• However, majority of people developing MPEG related applications do not need to know that is inside the boxes, but only how to use it

2009/10/31 12Christian Timmerer, Klagenfurt University, Austria

http://images.google.com/imgres?imgurl=http://www.financialsforyou.com/man with piles of paper.jpg&imgrefurl=http://patnickandjim.com/corporate-fitness-agreement/&usg=__oixKB3bnPJpnQsoZrpo8syxdk9M=&h=288&w=416&sz=159&hl=fr&start=60&um=1&tbnid=nn39zMr43mZ2LM:&tbnh=87&tbnw=125&prev=/images?q=lot+of+paper&ndsp=20&hl=fr&client=firefox-a&rls=org.mozilla:fr:official&sa=N&start=40&um=1

The MXM Approach

3. Documenting the IN/OUT points in another …MPEG standard: 23006-2 MXM API

- only 37 pages , - around 500 methods

1. Creating wrapping libraries, called engines

2. Opening the engines at ESSENTIAL points only

2009/10/31 13Christian Timmerer, Klagenfurt University, Austria

List of MXM Engines

• ContentProtocolEngine

• ContentSearchEngine

• DIAEngine

• DIDEngine

• DISEngine

• DomainEngine

• EREngine

• IPMPEngine

• IPMPToolProtocolEngine

• LicenseProtocolEngine

• MediaFrameworkEngine

• MetadataEngine

• MPEG21FileEngine

• MVCOEngine

• OrchestratorEngine

• RELEngine

• RenderingEngine

• SecurityEngine


MXM APIs of each engine have been divided into…

• Creation e.g. – Encode a raw audio track– Create an MPEG-7 metadata description

• Access e.g. – Get data from a Digital Item– Decode a video

• Editing e.g. – Add an elementary stream to a multiplexed content

• Engine-specific e.g. – RELEngine: authorise(license, query)– LicenseProtocolEngine: requestLicense(licenseID,

serviceURL)


Fully Interoperable Streaming ofMedia Resources in Heterogeneous Environments


Join the MXM Development Team!

• Why you should join

– Plenty of interesting work still has to be done

– Enough space for student projects, master thesis, PhD thesis, etc.

– You can choose betweenJava, C++ or start a new implementation in another language!

– It gives you visibility on a broad set of MPEG technologies

– Web site, blog, reflector, and soon more utilities

– Friendly and collaborative environment


Thank you for your attention

... questions, comments, etc. are welcome …

Ass.-Prof. Dipl.-Ing. Dr. Christian TimmererKlagenfurt University, Department of Information Technology (ITEC)

Universitätsstrasse 65-67, A-9020 Klagenfurt, [email protected]

http://research.timmerer.com/Tel: +43/463/2700 3621 Fax: +43/463/2700 3699

© Copyright: Christian Timmerer


http://mxm.wg11.sc29.org/[email protected]

http://wg11.sc29.org/mxmsvn/repos