The Digital Media Project  

Source

GA20

Date

2009/04/25

Title

Preliminary working draft of Open Media Marketplace

No.

1228/OMM

Preliminary working draft of Open Media Marketplace

1          Introduction

DMP has developed its Interoperable DRM Platform (IDP) specification as a toolkit. AD #2 describes the process

  1. Study how media value chains are built and run
  2. Single out the DRM functions that are required in value chains handling digital media (primitive functions)
  3. Standardise such DRM primitive functions (tools)
  4. Integrate the tools in a specification (toolkit)
  5. Check that the toolkit can actually be used to implement a large number of representative digital media value chains (use cases)
  6. Make a reference software implementation (Chillout)
  7. Repackage the reference software as a middleware (MXM) with specified API for each tool (MXM Engine)

As is well known the last step was triggered by DMP but actually executed in MPEG.

At the last two DMP meetings the idea of Open Media Marketplace has been discussed. The target of OMM is to provide more tools than those provided by the IDP that only are relevant to the DRM aspect of value chains. However, we believe that a similar process as used for IDP can be adopted for OMM.

The purpose is to identify and characterise the primitive functions that are needed by the Content Users and the Service Providers listed above, so that it becomes possible to

  1. Standardise technologies for each of the primitive functions
  2. Develop the OMM toolkit.

2          An initial OMM walkthrough

On a second thought the separation between Content Users and Service Providers appears rather artificial. Therefore in the following we will try to develop a model that only makes reference to Users. This will be achieved by first developing a walkthrough.

User A wants to assume an OMM Role. The initial Open Media Marketplace can be described by the following walkthrough.

Table 1 –Initial OMM walkthrough

Need

Service

User A must/may in general pay/be paid for the services offered by/to OMM Users

Convert Unit (CU) converts real money into accounting units and vice versa

User A must be Identified in OMM

Identify User (IU) Identifies other Users

User A may need to pay IU (or any other User)

Record Transaction (RT) records all Transactions of a subscribed User with other Users

RT may need to check that a User’s virtual account is backed up by real guarantee

Record Default (RD) is notified by RT if a User has insufficient guarantee

User A may need to describe himself in order to do good business in OMM

Manage Metadata (MM) lets User CRUD Metadata

User A may need to Store some Resources

Manage Resource (MR) lets User CRUD Resources

User A may need to describe some Resources in order to be able to offer them to the OMM

MM lets User CRUD Resource Metadata

A User performs a recordable action

Record Event (RE) records the User Event

An Event related to a Content Item happens

RE records the Content Event

User A needs to Identify Resources, Metadata and their combination

Identify Content (IC) Identifies Content and Content Elements

User A may want to Post his Resources on some delivery system (web, mobile, broadcast)

Host Site (HS) lets User Post Content

User A makes searches on Users and Content

MM respond to User’s Search

User A may find Content C of User B and may want to use it with another Content of his (Content D)

Negotiate Rights (NR) lets User Negotiate Rights to Content C of User B

User A may want to make appropriate edits to Content C and D

Edit Resource (ER) lets User CRUD Product

User A may need to move Content C and D to ER in order to edit

Deliver Content (DC) lets User move Content

User A may want to give licence to his Product and may need somebody to promote it

Promote Content (PC) promotes a Product to prospective Users based on guidelines received

User A may want to Consume Content

Render Content presents Content to a User

Summarising Table 1 provides an initial list of OMM Users along with their definition.

Table 1 – Initial list of OMM Users

User

Acr.

Informal definition: A User who

Convert Unit

CU

Converts money↔accounting units

Identify User

IU

Identifies Users

Record Transaction

RT

Records point transactions

Record Default

RD

Records defaulted transactions

Manage Metadata

MM

CRUDs Metadata of Entities in OMM

Manage Resource

MR

CRUDs Resources

Record Event

RE

Records Events related to Entities in OMM

Identify Content

IC

Identifies Content

Host Site

HS

Offers sites for a specific delivery technology

Negotiate Rights

NR

Offers rights negotiation services between two Users

Edit Resource

ER

Offers audio-visual editing services

Deliver Content

DC

Delivers Content via a specific delivery system

Promote Content

PM

Promotes Content of other Users

Render Content

RC

Presents Content for consumption

3          Analysis of User to User interactions

3.1        Introduction

In this chapter we explore all relationships that exist between two interacting Users by identifying the relevant primitive functions for each pair of Users.

3.2        Between any two Users

Primitive Function

Users

Description

Request Initiation of Service

USnUS

US1 requests US2 to initiate Service Contract

Request Termination of Service

USnUS

US1 requests US2 to terminate Service Contract

Request to Purchase

USnUS

US1 requests US2 to purchase a Content Item

Notify Payment Received

USnUS

US1 notifies US2 that payment has been received

3.3        Between a User and a specific User

3.3.1        USnCU

Primitive Function

Users

Description

Request Conversion

USnCU

US requests CU to convert real money into Units or vice versa

3.3.2        USnIU

Primitive Function

Users

Description

Request User Identification

USnIU

US requests IU to be Identified

Request User Authentication

USnIU

US1 requests IU to Authenticate US2

3.3.3        USnRT

Primitive Function

Users

Description

CRUD Account

USnRT

US requests RT to CRUD Account

Request Availability to Cash

USnRT

US1 requests RT to notify US2 that he awaits payment

Request to Pay

RTnUS

RT request US2 to pay US1

Request to Remunerate

USnRT

US1 requests RT to Remunerate US2

Notify Payment Performed

RTnUS

RT notifies US2 that US1 has paid

Request Transaction Log

USnRT

US requests RT to provide a Transaction log

Notify Transaction

RTnUS

RT notifies US that Account has been Credited/Debited

3.3.4        USnRD

Primitive Function

Users

Description

Request Default

USnRD

US1 requests RD defaulted Transactions of US2

3.3.5        USnMM

Primitive Function

Users

Description

CRUD Metadata

USnMM

US requests MM to CRUD Metadata of an Entity

Request Metadata

USnMM

US requests MM Metadata of a given instance of an Entity

CRUD Playlist

USnMM

US requests MM to CRUD a Playlist

Rate Entity

USnMM

US requests MM to Rate an Entity

Search Entity

USnMM

US requests MM to provide a list of Entities satisfying a matching criterion

3.3.6        USnMR

Primitive Function

Users

Description

CRUD Resource

USnMR

US requests MR to CRUD a Resource

Request User Resource

USnMR

US1 requests MR a specific Resource of US2

3.3.7        USnRE

Primitive Function

Users

Description

Request Record Event

USnRE

US requests RE to record a specific event (e.g. page view)

Request Event

USnRE

US requests RE Events of the desired Entity

Request Notification

USnRE

US requests RE to be Notified of specific Events

Notify Event

REnUS

RE Notifies US of the requested specific Events

3.3.8        USnIC

Primitive Function

Users

Description

Request Content Identification

USnIC

US requests IC to Identify a Content Item

Request Content Authentication

USnIC

US requests IC to Authenticate Content Item

3.3.9        USnHS

Primitive Function

Users

Description

CRUD Site

USnHS

US requests HS to CRUD a Site to Post Content

3.3.10    USnNR

Primitive Function

Users

Description

Request Negotiation

USnNR

US1 requests NR to Negotiate Rights to CI2 of US2

3.3.11    USnER

Primitive Function

Users

Description

Request Edit

USnER

US requests ER to Edit Resources

3.3.12    USnDC

Primitive Function

Users

Description

Request Delivery

USnDC

US1 requests DC to Deliver Content Item to/from US2

3.3.13    USnPM

Primitive Function

Users

Description

Request Promotion

USnPM

US requests PM to Promote use of Content Item

3.4        Between two Users of the same type

3.4.1        RTnRT

Primitive Function

Users

Description

Notify Cash Disposition

RTnRT

RT1 notifies RT2 readiness to cash

Authorise Payment

RTnRT

RT2 authorises RT1 to add specified Unit amount to US1

3.4.2        RDnRD

Primitive Function

Users

Description

Request Default

RDnRD

RD1 requests defaulted Transactions of US2 to RD2

3.4.3        MMnMM

Primitive Function

Users

Description

Request Metadata

MMnMM

MM1 requests Metadata of desired Entity MM2

3.4.4        MRnMR

Primitive Function

Users

Description

Request User Resource

MRnMR

MR1 requests Resource to MR2

3.4.5        REnRE

Primitive Function

Users

Description

Request Event

REnRE

RE1 requests Events of desired Entity to RE2

3.4.6        ICnIC

Primitive Function

Users

Description

Request Content Authentication

ICnIC

IC1 requests Authentication of CI2 to IC2

3.4.7        DCnDC

Primitive Function

Users

Description

Request Delivery

DCnDC

DC1 (e.g. web D.) requests DC2 (e.g. mobile D.) to Deliver Content Item to/from US2

3.5        Between CU and some specific User

3.5.1        CUnRT

Primitive Function

Users

Description

Request Credit Unit

CUnRT

CU requests RT to add/subtract a Unit amount to/from US Account

3.6        Between RT and some specific User

3.6.1        RTnCU

Primitive Function

Users

Description

Request Account Status

RTnCU

RT requests CU the status of US real account

3.6.2        RTnRD

Primitive Function

Users

Description

Communicate Default

RTnRD

RT communicates to RD that US has defaulted

4          Terminology

Account

A ledger of Transactions in Units

CRUD

Create, Read, Update, Delete

Default

An event caused by a User who does not have enough Units to cope with his OMM obligations

Delivery

The moving of Content from an OMM User to another OMM User

Entity

Any of

  • Content
  • Event
  • Group
  • Metadata
  • Playlist
  • Resource
  • Site
  • User