The Digital Media Project
Date	2013/02/23
No.	1334
Source	L. Chiariglione
Title	The OCTV implementation

The OCTV implementation

1        Introduction

“Connected TV” is seen by many as the means to provide the much sought-after convergence between traditional broadcast television and various new forms of video delivery. However, the largely proprietary implementations of Connected TV are a major impediment to the development of a promising new market of content, products, services and applications.

The Digital Media Project (DMP) has developed a Specification of Connected TV (dmp1317) called Open Connected TV (OCTV) and commissioned a Software Implementation of (OCTV) made available to DMP members subject to the OCTV implementation software licence (dmp1331).

2        Walkthrough

The OCTV implementation refers to the following usage scenario.

Fig. 1 – OCTV Devices of the usage scenario

where

1. OCTV Devices are devices built according to the subset of OCTV technologies employed in the OCTV Specification (dmp1317).
2. Creator operates Source to upload video and metadata to an OCTV Device called Server
3. Server prepares video for DASH streaming and presents all videos and corresponding metadata to a web page
4.     End User operates Sink to view information on videos and eventually request DASH streaming of a specific video.

Source is an OCTV Device by means of which a Creator can

1.     Create MP21 files (Content) with
   1. Audio-visual sequence
   2. Metadata
   3. Licence
2.     Store Content to Server

Server is an OCTV Device performing the following functions

1.     Prepare audiovisual sequences for DASH streaming
2.     Post Content
3.     Receive Content requests
4.     Stream audiovisual sequences according to the DASH standard as requested by Sink

Sink is an OCTV Device by means of which an End User can

1.     Request DI of a given audio-visual sequence from Server
2.     Present metadata and licence information to the user
3.     Verify licence
4.     Request Server to DASH-stream audio-visual sequence

Table 1 is the walkthrough where

1.     the 1^st column represents the entities (humans and Devices) involved
2.     the 2^nd column represents the functions performed by an entity
3.     the 3^rd column represents the technologies involved.

Table 1 – Walkthrough and technologies

3        Architecture

The 3 OCTV Devices in Fig. 1 conform to the 3-layer architecture of ISO/IEC 23006-1 MPEG-M Architecture.

Fig. 2 – OCTV Device Architecture

Currently the “Security” functionality is not implemented.

4        Engines

The OCTV Implementation provides the list of MXM Engines supporting the walkthrough described in Chapter 2.

Table 1 – Protocol and Technology Engines required

Source code of Protocol and Technology Engines can be found at http://wg11.sc29.org/mxmsvn/repos/java.

5        OCTV Devices

The following Applications, Protocol Engines and Technology Engines are used in the 3 OCTV Devices, as follows

Table 1: Applications, Functionalities and Engines

The table shows that total of 4 Applications, 3 Protocol Engines and 5 Technology Engines.

The following table gives a technology walkthrough.

Table 2: Source-Server-Sink walkthrough

Fig. 2 represents the architecture of the 3 OCTV Devices.

Figure 2: MXM Engines for Source, Server and Sink

Wherever possible Open Source Software (OSS) packages have been employed. Table 3 gives a list of all OSS packages in the OCTV implementation.

Table 3: Open Source environments used in the Work