1 / 0

T he Digital Media Project Goals – Achievements – Future

T he Digital Media Project Goals – Achievements – Future. Leonardo Chiariglione DMP Brainstorming Day San José, CA – 2014/01/11. DMP – goals. Launched as Digital Media Manifesto in Jul 2003 Manifesto published in Sep 2003 http://www.chiariglione.org/manifesto/dmm.htm

rocio
Download Presentation

T he Digital Media Project Goals – Achievements – Future

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Digital Media ProjectGoals – Achievements – Future

    Leonardo Chiariglione DMP Brainstorming Day San José, CA – 2014/01/11
  2. DMP – goals Launched as Digital Media Manifesto in Jul 2003 Manifesto published in Sep 2003 http://www.chiariglione.org/manifesto/dmm.htm The Digital Media Project (DMP) was established on 1st December 2003 with the mission to …promote continuing successful development, deployment and use of digital media that respect Creator and rights holders rights to exploit their works End user wish to fully enjoy the benefits of digital media Various value-chain player interest to provide products and services
  3. Interoperable DRM Platform (IDP) specification v. 3.3
  4. AD #1 – Value Chain Functions and Requirements/2 Contains A list of Value-Chain Users The list of General Requirements The full list of Requirements of Primitive Functions Represents 24 months of work The foundation of other DMP documents “Work in progress” (by definition) Open to more contribution from anybody
  5. AD #2 – Architecture Walkthrough exercising the main elements of Value-Chains enabled by Tools Operating principles of Certification and Registration Authorities/Agencies A series of models Creation Model Distribution Model Delivery Model DRM Tool Model Device Model Domain Model Import/Export Model Data Model
  6. Distribution Model Service Provider Device End- User Device Content Return Channel Content Identification Device Content Provider Device Content Return Channel License Identification Device License Identification Device License Provider Device License Return Channel License Identification Device DRM Tool Identification Device DRM Tool Provider Device DRM Tool Return Channel
  7. AD #3 – Interoperable DRM Platform The specifications of all Tools Organised in four main components Represent Protocols Package IDP Schema
  8. Represent information Content Metadata DCI Signature DCI Hash Identifier Resource DRM Information DRM Tool DRM Tool Body License Key DRM Messages Authentication Messages Device Information Domain Domain Protocol Use Data Binary XML
  9. Overview of DMP IDP-3.1 AD #4 – Use Cases and Value Chains Defines 17 Use Cases Describes Use Cases by means of walk-throughs (possibly > 1 per Use Case) For each use Case and walk-through lists all IDP Tools required to implement it Normative AD
  10. AD #5 – Certification and Registration Authorities Value-Chains rely on the guaranteed Integrity of Entities e.g. Device and DRM Tools Identity of Entities e.g. Content, Device, Domain, DRM Tools and User AD #5 collects roles, qualification requirements, appointment procedures and operation rules of Certification and Registration Authorities Process DMP selects and appoint Authorities Authorities appoint Agencies Agencies Certify or Identify Entities
  11. Authorities and Agencies Authority Agency 1 Agency 2 Agency k Entity 1,2 Entity 1,l Entity k,1 Entity k,2 Entity K,n Entity 1,1 Entity 2,1 Entity 2,m
  12. AD #6 – Terminology 160 terms defined and used in all ADs Some examples Conformance: The status of a Content or Device Entity that has been judged to positively meet the requirements of a Technical Specification Content Interoperability: The capability of a Content Item to be Used by a Device in the way expected by the Device(s) from which the Content has originated Device Interoperability : The capability of a device to exchange data with other devices across standard interfaces, using standard protocols, and to be processed by the devices exchanging the data in a predictable fashion Interoperable DRM System: A set of Devices that manage, possibly protect and Use Content Interoperably
  13. IDP reference software Chillout software Devices RVD LPD CPD TPD CCD EUD DMD DID DoID CID Libraries P2P Auxiliary Core Media Framework OS + Java platform + dependencies
  14. AD #8 – End-to-End Conformance Questions requiring an answer Has an Entity been correctly implemented according to the Technical Specifications? Can an Entity be safely admitted to the Value-Chain? Purpose of AD #8 is to provide Means to test an Entity for Conformance to ADs Methodologies Test suites Software (where possible) General information to be used by Certification Authorities/Agencies
  15. AD #9 – Mapping of TRUs to the digital space Why do we need to support Traditional Rights and Usages? Users could desert offers based on IDP because they find the IDP experience poor compared with The analogue experience The current digital experience Repackaging the TRU experience with IDP technologies may lead to some new Digital Media Business Models Doing this is often possible using the IDP toolkit
  16. DMP responses to consultations
  17. Contributions to MPEG standards
  18. Media Streaming Application Format (MPEG-A Part 5, MSAF) In July 2006 some DMP members submitted the MS-AF proposal to MPEG In October 2007 MPEG approved MS-AF as ISO/IEC FDIS 23000-5 MS-AF is the first (and only) ISO standard for governed audio-visual content streaming Domain Management Device License Provider Device Media Streaming Player Content Provider Device Media Streaming Player Media Streaming Player DRM Tool Provider Device
  19. Multimedia Service Platform Technologies (MPEG-M) MPEG issued a Call for Proposals on MPEG eXtensibleMiddleware (MXM) in May 2008 DMP members Submitted a response to the call in July 2008 Contributed to the development of parts 1-4 on MPEG-M DMP gave MPEG a licence to use the Chillout reference software
  20. Open Media Marketplace DMP developed notion and requirements of OMM: an environment where Users perform actions on Entities using Services provided by Service Providers Some requirements OMM shall enable the provisioning of interoperable Services between OMM Users OMM shall support Basic Services OMM shall enable a Service Provider to combine several Basic Services into one Aggregated Service OMM shall enable different Providers to offer the same Basic Services and the same or partially overlapping Aggregated Services
  21. MPEG-M version 2 In January 2010 MPEG issued a new Call for Proposals that included OMM requirements as proposed to MPEG at the London meeting (June-July 2009) Advanced IPTV Terminals (AIT) proposed by ITU-T DMP members Submitted a response to the call in April 2010 Contributed to the development of new parts 1-5 and part 5 of MPEG-M
  22. The goal of MPEG-M To accelerate and facilitate realisation of the digital dream by providing users with the ability to seamlessly Create Publish Distribute Access Pay/cash Process Re-distribute Consume governed multimedia services
  23. An introduction to Multimedia Service Platform Technologies (MPEG-M) The MPEG-M standard Formally ISO/IEC 23006 5-part standard Part 1 – Architecture Part 2 – MPEG Extensible Middleware (MXM) API Part 3 – Conformance and Reference Software Part 4 – Elementary Services Part 5 – Service Aggregation
  24. MPEG-M architecture Application level App1 App2 Appi Appm MXM API Aggregation and Orchestration Prot Eng1 Prot Eng2 Prot Engi Prot Engp Middleware level NtwkTE Secur. TE Tech Eng1 Tech Engq Network API Security API Resource API Computing Platform level Network Security Local resources
  25. An introduction to VCN-PS Available MPEG-M Engines
  26. An introduction to Multimedia Service Platform Technologies (MPEG-M) Part 4 Elementary Services
  27. An introduction to Multimedia Service Platform Technologies (MPEG-M) Part 5 – Aggregated Services Music "mood" BPMN diagram
  28. An introduction to Multimedia Service Platform Technologies (MPEG-M) Building new Services from Elementary Services
  29. Publish/Subscribe Peer1 6 ER Fractal Subscribe S-VDI Request R-VDI S-VDI 3 4 P-VDI 1 S-VDI P-VDI 7 5 MATCH R-VDI Publish P-VDI ER Store R-VDI Peer2 Conet R-VDI R-VDI 2
  30. Video Centric Networking – Publish/Subscribe (VCN-PS) DASH Segmenter Peer Creator Consumer Peer(segmenter) Peer(hostname) DASH segmenter MXM MXM GStreamer plug-in Green ICN TE Over lay TE Over lay TE Green ICN TE VLC MF TE Overlay GreenICN
  31. Open Connected TV (OCTV) The Open Connected TV (OCTV) has developed a international standards-based technical specification an industry-grade implementation (platform) The goal is to enable creation and development of a broad market of interoperable products, content, services and applications that enrich one-way TV services with multichannel two-way content access and delivery.
  32. The OCTV implementation Segments video Posts relevant data to web site Streams video (DASH) Plays content posted on "Server" according to "Source“-defined use rights Creates file with video, descriptive metadata and use rights Uploads file to "Server"
  33. OCTV software operation - Source
  34. OCTV software operation - Server
  35. OCTV software operation - Sink
  36. - HTTP - JSON - XML - HTML Service Access Via REST API MVC Services Security JSP Pages Validators UIComponents Orche- strator REL T-Engine Metadata T-Engine DI T-Engine Service Modules (MXM MW) Create Con. P-Engine MR T-Engine MP21FF T-Engine Id. Con. P-Engine JVM Servlet Container Relational DB Other Repository
  37. Conclusions DMP has just turned 10  It has a track record of specification development Has successfully contributed to MPEG producing or extending important standards (REL, MVCO, MXM) Has full availability of OCTV implementation software Is well equipped to address new challenges
More Related