28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

On receiv<strong>in</strong>g the <strong>in</strong><strong>format</strong>ion that an event has occurred, the LE checks active L<strong>in</strong>ks of all active<br />

Application and Scene objects to determ<strong>in</strong>e whether some L<strong>in</strong>k must be fired or not. When a L<strong>in</strong>k is fired,<br />

the LE uses the primitive Process-Action() to <strong>in</strong>form the OP which Action object should be processed.<br />

3. Overview of DSM-CC<br />

The DSM-CC is a set of protocol specifications for manag<strong>in</strong>g and controll<strong>in</strong>g MPEG-1 and MPEG-2 bit<br />

streams. These protocols are <strong>in</strong>tended for general applications, MHEG applications, and script<strong>in</strong>g<br />

language application to setup or teardown a network connection us<strong>in</strong>g User-Network (U-N) primitives and<br />

for communication between a client and a server across a network us<strong>in</strong>g User-User (U-U) primitives. U-N<br />

primitives are def<strong>in</strong>ed as a series of messages to be exchanged among the client, network and server. U-U<br />

primitives may use a Remote Procedure Call (RPC) protocol and may <strong>in</strong>volve U-N messag<strong>in</strong>g. DSM-CC<br />

may be carried as a stream with<strong>in</strong> an MPEG 1 System Stream, an MPEG 2 Transport Stream, or an<br />

MPEG 2 Program Stream. Alternatively, DSM-CC may be carried over other delivery mechanisms, such<br />

as TCP or UDP.<br />

4. Overview of DAVIC<br />

The DAVIC is a consortium whose purpose is to favor and nurture emerg<strong>in</strong>g audio-visual standards and<br />

services. These goals are achieved open <strong>in</strong>ternational collaboration of all members of the DAVIC<br />

consortium. As of today, there are more than 200 companies from 20 different countries who participate<br />

<strong>in</strong> DAVIC activities. The DAVIC specification is <strong>in</strong>tended to be open and to specify tools, protocols for<br />

handl<strong>in</strong>g <strong>in</strong><strong>format</strong>ion flows and not systems. Thus different vendors can make their systems <strong>in</strong>teroperable<br />

if they conform to the DAVIC specification. DAVIC specifies m<strong>in</strong>imum requirements only and it is up to<br />

the vendor to add more functionality.<br />

4.1 DAVIC Architecture<br />

The DAVIC system specification is aimed at provid<strong>in</strong>g <strong>in</strong>teroperability. It is based on an abstract<br />

reference model and is made up of 5 subsystems (see [Fig. 2]). A11, A10, A9 and A1 denote reference<br />

po<strong>in</strong>ts with<strong>in</strong> the system and <strong>in</strong>dicate the <strong>in</strong><strong>format</strong>ion flow between modules. A reference po<strong>in</strong>t comprises<br />

of one or more logical <strong>in</strong><strong>format</strong>ion-transfer <strong>in</strong>terface and one or more physical <strong>in</strong><strong>format</strong>ion transfer<br />

<strong>in</strong>terface. DAVIC 1.0 system typically addresses the service provider system (SPS), service consumer<br />

system (SCS) and the delivery between the two. The DAVIC system uses a four-layer service model,<br />

namely, pr<strong>in</strong>ciple service model(SL1), application service layer (SL1), session and transport service layer<br />

(SL2) and network service layer (SL3).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!