OPERA Eurescom Project 1207 Interoperability of Digital Rights

OPERA Eurescom Project 1207 Interoperability of Digital Rights Management (DRM) Technologies Partner: • Sun Microsystems, Inc. • DMDSecure. • Exavio, Inc. • Matáv Hungarian Telecommunications. Company Limited. • T-Systems Nova Gmb. H, Berkom. EURESCOM 1

OPERA Overview. 1. Introduction 2. System Overview 3. Architecture 4. Demonstrator 5. Discussion EURESCOM 2

OPERA Content owner / Provider Domain MPEG 21 / ODRL Licence eb. XML Management Business Commercial DRM Content owners Orchestration Systems like view MS-DRM License Content Real DRM Management Encryption /. . . (Destributors Enfrocement view) Licence Management end users OMA / view Part of ODRL Enduser Domain EURESCOM 3

OPERA Content owner / Provider Domain 21 / Make it as MPEG flexible (Complicated)as possible ODRL Licence Business Orchestration eb. XML Management Content owners view License Management (Destributors view) OMA / Part of ODRL Commercial DRM Systems like MS-DRM Content Real DRM Encryption /. . . Enfrocement Licence Management end users view Make it as simple as possible Enduser Domain EURESCOM 4

OPERA 1. Introduction History. • Started with gathering requirements from the operators. DRM-Systems should be able to handle: • Different content types • A multi-client and multi-system infrastructure (Contentsyndication) • different access methods, services and devices • Flexible business Models • Performance and Availability EURESCOM 5

OPERA 1. Introduction History. • Requirements of the Content Owners • Open Systems • Secure Decode & Decryption • Scaleable Protection: More valuable content = more protection • DRM should working on discontinued mode for wireless devices. • Multiplatform • Flexible business models EURESCOM 6

OPERA 1. Introduction History. • User Requirements • Ease of use • Transparent and Visible • Protection of Privacy • Simple business models • Fast and reliable • Should run on standard hardware EURESCOM 7

OPERA 1. Introduction The Problem: no DRM fulfills all requirements • No global License Management available • DRM-Systems are only compatible to itself (some times even not that) • The handling is not transparent for the user • No open systems • One DRM is not available for all Content types • Different systems with complete different approaches • Strongly altering market. EURESCOM 8

OPERA 1. Introduction OPERA Mission. The objective of the project was the specification of an open DRM architecture that addresses the needs of: • Content Providers: Addresses the needs of content providers to get a powerful and independent platform. • Operators: Able to handle content of different media types, rights models and business models. • Users: Addresses the needs of customers, to get an easy to handle, device and location independent service. EURESCOM 9

OPERA 1. Introduction Different solutions for the Licence bounding • Microsoft, Real etc. : The License is “stored” in the player and is bound to the hardware by a generated hardware key • OMA: License is stored in a secured part of the end device. The Hardware have to ensure that no copy of the license can be done (secure storage and handling part of the OS). • OPERA: A new single license is delivered for every usage. EURESCOM 10

OPERA 1. Introduction Why OPERA? DRM 1 Player 1 DRM 2 Player 2 DRM 3 Player. . . DRM. . . Player x PC-Based Limitations of current systems Every DRM System works separately i. e. specialized in content types, players, end devices, system environments. EURESCOM 11

OPERA 1. Introduction OPERA framework. DRM 1 Player 1 on a PC DRM 2 Player 2 in a car radio OPERA DRM 3 Player. . . in a settop box DRM. . . Player x in device. . . OPERA provides the framework to handle various DRM systems in a common environment. EURESCOM 12

OPERA 2. System Overview. Concepts, Features, General Overview, 3 rd Party Domain. EURESCOM 13

OPERA 2. Overview Concepts. The main value of the OPERA framework is based on two conceptual approaches: • The usage license is independent of the underlying DRM system. • The usage license is bound to an user instead of (as is common) to a device. To achieve these functionalities Opera directly integrates major DRM systems and uses the already available DRM frameworks. EURESCOM 14

OPERA 2. Overview Features. # Feature Description Benefit 1 User bound licenses Usage rules are independent of the end devices. Instead they are explicitly bound to a user. Secure for content provider, ease of use for the user, “subscriber control” for operator. 2 Separation of rights from content Rights management is completely separated from the DRM process and allows every content type that the underlying DRM system is able to support. Content Providers and end users are able to use arbitrary DRM systems. The OPERA framework supports different DRM systems. 3 Support for multiple devices Support for different end devices: (a) PC (b) Set Ease of use for the user, more revenue for -top Box (c) PDA. operators and content providers. EURESCOM 15

OPERA 2. Overview General Overview. Client Domain Opera Proxy Access Domain UMTS WLAN Presentation Layer Service Layer • Web Portale • User Registration • User Verification • Licence Generation • Rights Registration • Content Registration Shop DRM – Framework Supporting Services PC STB (Payment, CMS Content Delivery) ISDN EURESCOM 3 rd Party Domain Opera Server Mobile Phone PDA Service Domain Content Providers 16

OPERA 2. Overview 3 rd Party Domain. Presentation Layer Shop Server Service Layer Play out Server Content Management Accounting/ Billing Other Auth. Services SMS-Gateway editorialservice Content Data Content Meta Data Reports EURESCOM Accounting Data User Data 17

OPERA 3. Architecture. Component Overview, Client Components, Server Components, Additional Components. EURESCOM 18

OPERA 3. Architecture Component Overview. EURESCOM 19

OPERA 3. Architecture Client Components. • Opera Proxy: The Opera Proxy is responsible for connecting the user to the Opera Server and adds the users Authentication information to the incoming license request from the Player. • DRM Player (or Viewer) application: The media player or viewer allows users to consume the content they bought. This component is dependent on the particular used DRM system. EURESCOM 20

OPERA 3. Architecture Server Components. • The license management layer (Opera Server) is responsible for management of the rights the users have obtained. They are described through an Opera license and stored in a database on a per-user basis. • The license delivery layer is responsible for delivering licenses of the underlying proprietary DRM-systems to the user’s machines. Examples for such systems are DMDfusion and the DWS (Digital World Services) system. EURESCOM 21

OPERA 3. Architecture Server Components. • The enforcement layer is realized by one of the proprietary DRM-systems available on the market. Enforcement layer - enforces the compliance of usage rules (more exactly: those of the delivered license) by using mechanisms like encryption. • Content management layer – This layer represents the content utility interface and a media asset management system. For the Opera project the focus is the additional possibility to specify usage rules for the Opera Server. EURESCOM 22

OPERA 3. Architecture Additional Components. • Shop Application: The shop application is used to buy content over a web based application. The Opera management layer uses the shop also to verify that the content was bought by the user who request the license. • Payment Application: The payment application is often part of the shop application but may also be a separate application e. g. T-Pay or First. Gate. • Content delivery system: – architecturally both download and streaming capability shall be supported. But for the demonstrator only download will be supported. EURESCOM 23

OPERA 4. Demonstrator. Components in demonstrator, flow for Obtaining Licenses EURESCOM Work 24

OPERA 4. Demonstrator Components. • License Delivery Layer (DRM Frameworks) • DMD Secure • License Enforcement Layer (DRM Systems) • Digicont DRM from SDC AG. • Microsoft DRM • Devices • PDA • Personal Computer • Set Top Box • (Mobile phone) EURESCOM 25

OPERA 4. Demonstrator Workflow. Components in Opera DRM solution EURESCOM 26

OPERA 4. Demonstrator Workflow. EURESCOM 27

OPERA 4. Demonstrator Workflow. EURESCOM 28

OPERA 4. Demonstrator Workflow. EURESCOM 29

OPERA 4. Demonstrator Workflow. EURESCOM 30

OPERA 4. Demonstrator Workflow. EURESCOM 31

OPERA 4. Demonstrator Workflow. EURESCOM 32

OPERA 4. Demonstrator Workflow. EURESCOM 33

OPERA 5. Questions ? • Thank you for your interest. Please feel free to ask your questions. • More informations are available at the Eurescom Webside: www. eurescom. de EURESCOM 34