DRAFT OCTV TESTBED

1        Introduction

This document provides information on how to use the Core OCTV testbed and to contribute an OCTV module. Please make reference to the OCTV specification (dmp1317) for further details.

2        The OCTV test bed

The OCTV test bed has the following features

  1. It has client-server configuration
  2. The client is implemented in C++
  3. The server is implemented in Java
  4. The client supports the following subset of OCTV functionalities
    1. The player is a stand alone application
    2. The middleware is populated with the following engines
      1. Media Framework Technology Engine
      2. LASeR Parser Technology Engine
      3. Rendering Technology Engine
      4. Orchestrator
  5. The server supports the follwing subset of OCTV functionalities
    1. LASeR creator TE
    2. Request Content PE
    3. Orchestrator
  6. The engines are available as object code

The overall architecture of the set up is given by Fig. 1

Fig. 1 – End-to-end architecture of the OCTV testbed

The architecture of the player is depicted by Fig. 2

Fig. 2 – LASeR player architecture

The Media Framework and LASeR Parser Engines implement the architecture depicted in Fig. 3

Fig. 3 – Internal architecture of Media Framework and LASeR Parser Engine

3        Process to add a new module to the platform

OCTV adopts a test bed, whose initial configuration is described in Annex C, with the following features

  1. The testbed is composed of a client and a server
  2. Each of the client and server supports a significant subset of OCTV functionalities implemented as C++ Engines (client) and Java Engines (server)
  3. The Engines are available in object code.

A proposal to test an OCTV module for acceptance may fall into one of three categories

  1. It implements a functionality that is already present in the testbed
  2. It implements a functionality that is not present in the testbed
  3. It implements a functionality that is partly present in the testbed

In case the functionality is already present in the testbed

  1. The existing module(s) is(are) replaced by the new one(s) and
  2. The new set up is tested against the old one
  3. If the test is successful the new module(s) replace(s) the old module(s) in the testbed

In case the functionality is not yet present in the testbed

  1. The new module(s) is(are) added to the set up
  2. New applications designed to test the new set up are developed
  3. The new set up is tested
  4. If the test is successful the new module(s) is(are) added to the testbed

In case the functionality that is partly present in the testbed a mix of the two preceding cases.

  1. The existing module(s) is(are) replaced by the new one(s) and
  2. The new module(s) is(are) added to the set up
  3. New applications designed to test the new set up are developed
  4. The new set up is tested
  5. If the test is successful the new module(s) is(are) added to the testbed

In case the proposed engine(s) pass the above tests, they become part of the OCTV platform and the proponent becomes an OCTV member as defined by the OCTV project rules.

4        How to use the OCTV testbed

Please do the following

  1. Send an email to the DMP Secretariat (secretariat@dmpf.org) to join the analysis.p212@dmpf.org mailing list
  2. Request access to the LASeR player (currently the installer is only for Linux/Windows)
  3. Download the installer and install the player
  4. Launch the player
  5. Communicate to the DMP Secretariat (secretariat@dmpf.org) your readiness to contribute a module to the OCTV project