Oracle video server content model, Content layers – Oracle A55979-02 User Manual

Page 16

Advertising
background image

Oracle Video Server Content Model

1-6

Getting Started with Oracle Video Server Manager

Oracle Video Server Content Model

Oracle Video Server (OVS) offers both physical and logical control of all content
that is stored in the Oracle Video Server system. To harness the flexibility and
control that this content model offers, you must understand the different layers of
content that are available in the OVS environment.

Content Layers

The OVS content model consists of the following layers:

Content Files:

files that OVS stores and delivers to clients. Content files can

contain video and/or audio and are created through a process called encoding.

For more information on the types of content files that OVS supports, refer to

“Codecs, Containers, and Frameworks”

in Chapter 3.

Tag Files:

a physical file that stores metadata and header information about a

given piece of content, such as the file’s name, format, bit rate, and size. Tag
files also store information about individual video frames, which is not stored
in the database. Tag files must have an .mpi extension.

Physical Content:

a database object that contains the same header and

metadata information found in a tag file.

Clips:

a logical excerpt from a content file. Each clip corresponds to only one

content file. Clips map to a specific start and stop position (in seconds) within a
content file.

Logical content:

a collection of video clips that are played in a pre-defined

sequence.

Logical content, clips, and physical content are all objects that are stored
persistently in the Oracle database. Video Server Manager enables you to create,
edit, and remove these objects, thereby protecting the physical data that is stored in
the Oracle Media Data Store (MDS).

In contrast, tag files and content files are physical data files which are stored in the
MDS. For each content file that you load into the MDS, you must create a tag file
and store it in the MDS with the content file.

Figure 1–3

illustrates the relationship between the different OVS content layers.

Advertising