Technical Specification of the WIM TV trial at Beijing Olympics

1          Purpose and general description of the DMP WIM TV trial

The DMP Web, IP and Mobile (WIM) TV trial at Beijing Olympics intends to provide an Information and Communication (ICT) platform for publication and delivery of User Generated Content (UGC) produced by Beijing citizens, residents living in Beijing (students of selected universities, foreigners living there etc.).

The content eligible to publication on the WIM TV trial platform (“WIM TV trial content”) is any video (“Resource”) for which the Creator holds rights (hence no Olympic Games content, in general). Therefore the recommended type of content can be described as “discover Beijing during the Olympic Games, but outside of the Olympic Games”.

Creators of WIM TV trial content will be provided with a Content Creation Device (CCD), an application that will allow them to make a DMP Content Information (DCI) with Metadata related to the Resource and a Creative Common (CC) like Licence that digitally expresses the selected CC licence using the Rights Expression Language (REL) Open Access Content (OAC) Profile.

Creators will upload their WIM TV trial content (DCI + Resource) to a Content Provider Device (CPD) located in Beijing and accessible to users in China. If there will be interest, mirror CPDs may be set up in other countries (or other locations in China) to serve local users. Different CPDs may have different delivery capabilities.

Those interested to view the WIM TV trial content will be able to download an End User Device (EUD), a PC application that will allow them to browse the CPD and get selected content streamed to their EUD.

Every time an End User performs an action (play, store etc.) specified in an Event Report Request (ERR) placed in the DCI by the Creator, the EUD generates an Event Report (ER) and sends it to the Event Collection Device (ECD). The entity operating the EUD will be able to extract statistical information from the ECD.

CCDs and EUDs are signed applications identified by the Device Identification Device. This gives knowledge of who is actually uploading content to the Main CPD and makes the collected Event Reports reliable.

2          Reference diagram of the WIM TV trial

Figure 1 – Reference diagram of the WIM TV trial depicts the planned arrangement

Figure  SEQ Figure \* ARABIC 1 – Reference diagram of the WIM TV trial

The WIM TV devices have the following functionalities:

3          A walkthrough

3.1        Content Creation

Pota is a participant in the WIM TV trial as a Creator.

1.      Pota downloads the CCD and installs it on his PC

2.      CCD authenticates with the DID

3.      Pota starts the CCD

4.      Pota begins the creation of a Content Item

5.      Pota selects a video taken the day before.

6.      CCD gets an identifier for the video

7.      Pota adds the metadata of the video

a.       Author

b.      Title

c.       Description

d.      Genre

e.       A representative frame of the video

f.        Unstructured text

8.      Pota adds a licence

a.       Pota select one among available CC licences

b.      CCD digitally expresses the selected CC licence using the Rights Expression Language (REL) Open Access Content (OAC) Profile

9.      CCD gets an identifier for the licence

10.  Pota creates presentation information

a.       (a set of Laser templates will be created once and for all for the WIM TV trial)

b.      CCD displays a set of static templates

c.       Pota selects one of the templates

d.      Pota fills in any additional data needed (exclusively) by the template

                                                   i.       

e.       CCD presents the DCI as it will be seen by End User (preview of Laser object or entire End User experience?)

f.        CCD displays a set of static templates indicating the size of the video and the position in the screen at which ads will appear (at specified times)

11.  CCD describes how the Content Item is broken down for transmission using the Bitstream Binding Language (BBL) – the exact nature of this will depend on the actual Digital Item Streaming (DIS) creation functionality

12.  CCD gets an identifier for the Content Item

13.  Pota uploads the Content Item (including the resource) to the Main CPD

3.2        Content Provision

M-CPD is the Main CPD in Beijing

1.      M-CPD sends the DCI to the EUD when an End User right clicks a Content Item in the list

2.      M-CPD receives a request to stream Pota’s Content Item

3.      M-CPD streams the requested Content Item without further checks unless Zhiming does not accept the CC licence terms

3.3        Content Consumption

Zhiming is a participant in the WIM TV trial as an End User.

1.      Zhiming downloads the EUD and installs it on his PC

2.      EUD authenticates with the DID

3.      Zhiming browses a CPD and finds Pota’s Content Item

4.      Zhiming right clicks and downloads the DCI

5.      EUD displays the figure below

6.      Zhiming accepts the CC licence

7.      EUD requests Pota’s Content Item via the Access Content Protocol

8.      CPD starts streaming Pota’s Content Item (AV and ads)

9.      EUD executes as authored by Pota

a.       display resources

b.      present metadata

c.       generate event reports

10.  EUD displays ads received via RTP packets

Figure  SEQ Figure \* ARABIC 2 – Screen for accepting Event Report issuing and CC Licence

3.4        Event Collection

ECD will collect and store in a data base all events generated by all EUDs. The entity managing the ECD will be able to make such queries as “what is the video most watched today?”, e.g. for the purpose of awarding the most successful creators.

3.5        Content Mirroring

Content uploaded to the Main CPD will be mirrored by all CPDs participating in the WIM TV trial.

4          System analysis

In the following Figure 3 – Schematics of the WIM TV trial will be used to progress the specification.

Figure  SEQ Figure \* ARABIC 3 – Schematics of the WIM TV trial

4.1        Content Identification Device

Status:

·        The CID has been developed

·        The Content Registration Protocol has been developed

·        The CCD part of the Protocol has not been integrated in the CCD, so no testing has been carried out

Actions:

·        Integrate the Content Registration Protocol in the CCD

·        Carry out tests with CCD

4.2        Content Creation Device

Status:

·        The CCD has been developed

·        It is possible to create DCI containing

o       DCI Identifier

o       Resources

o       Metadata

o       Licences

o       DRM Tools

·        Store DCI and Resources to CPD

Actions:

·        Add Laser objects to DCI

·        Describe of metadata for DIS with BBL

·        Insert Event Report Request

·        Integrate the Content Registration Protocol in the CCD

·        Carry out tests with CID

·        Request Identifier to CID at the end of DCI buildup

·        Integrate device identification

·        Test device identification with DID

·        Implement DID-CCD protocol over SSL

4.3        Content Provider Device

Status:

·        Store DCI and Resources sent by CCD

·        Send DCF to requesting EUD

Actions:

·        Offer CCD the possibility to store DCI/DCF in personal directory

·        Add Digital Item Streaming

·        Provide robust video streaming

4.4        End-User Device

Status

·        Obtain DCF from CPD

·        Parse DCF/DCI

·        Parse Licence

·        Play video in dowload

Actions

·        Add DIS receiver

·        Choose media framework (for streaming)

o       AVC decoder

o       AVS decoder

·        Parse DCI Presentation Information

·        Present Laser objects

·        Event Report Request receiver

·        Event Report generator

·        Integrate device identification

·        Test device identification with DID

·        Implement DID-EUD protocol over SSL

4.5        Event Collection Device

Status

·        Device not developed

Actions

·        Collection ERs

·        Query DB of ERs

4.6        Device Identification Device

Status

·        DID developed

Action

·        Integrate CCD Identification

·        Integrate EUD Identification

·        Implement DID-CCD protocol over SSL

·        Implement DID-EUD protocol over SSL

4.7        Media framework

1.      The file format of audio-video can be any of (check FF supported by Feng)

a.       ISO FF

2.      The audio encoding can be any of

a.       MPEG Audio (MPEG-1/2 Layer I/II/III) (rfc2250)

b.      Vorbis (draft)

c.       AAC (MPEG-4 Part 3) (rfc3640)

3.      The video encoding can be any of

a.       MPEG Video (MPEG-1/2) (rfc2250)

b.      MPEG 4 Visual (MPEG-4 Part 2) (rfc3016)

c.       AVC (H.264|MPEG-4 Part 10) (rfc3984)

d.      H.263 / H.263+ (rfc4629)

e.       Theora (draft)

f.        AVS

5          What is needed to carry out the WIM TV trial

In the following we list all Devices, what is needed to have them usable for the trial and who is working to make them.

The following application software also needs to be developed

6          Timeline

1^st milestone: 08/05/30

The DID identifies CCD and EUD: 08/05/16

·        User identification:

§         New message required

§         add address (unstructured), email address

§         Protocol between DID and CCD/EUD

The CCD produces a DCI containing

·        Metadata

·        CC Licence

·        Video

·        Laser presentation with metadata, licence etc. (no ads yet)

§         From 1 template: 08/05/09

·        Upload DCI + Resources to CPD: 08/05/16

§         Storage of resources and linking between DCI and resource file name

·        DID-CCD: 08/05/16

From this milestone encourage Creators/End Users to upload/play content for test purposes

The EUD

·        Browsing capability: 08/05/16

·        Plays the DCI showing:

§         The Laser presentation including

·        Metadata

·        Licence

·        Static ad

·        Rendering: 08/05/16

§         Video after acceptance of licence

·        Renders streaming resources

·        DID-EUD: 08/05/16

First version of web site including

·        User management: 08/05/30

o       Shared relevant CPD and DID data (UN/PW, Device certificate, …)

·        Download CCD: 08/05/30

o       Installer

·        Download EUD: 08/05/30

o       Installer

2^nd milestone: 08/06/28

The CCD produces a DCI containing as 1^st milestone

·        Laser presentation with metadata, licence etc. : 08/06/13

o       From 4 (?) templates + ads

o       Select the template

o       Move the ads object in the template

o       View the result

The CPD has streaming capability

·        Installation package for the Feng streaming server (Linux): 08/06/28

3^rd milestone: 08/07/18

The CPD has streaming capability

·        DIS streaming capability

The EUD

·        Receive ad data from RTP packets

·        Display ad data in the scene

·        Issue: connect Laser player with DIS receiver

7          Acronyms