TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

As explained, the Delivery layer is media unaware but delivery technology aware. It provides
transparent access to the delivery of content irrespective of the technologies used (IP, ATM...). The
boundary between the Sync Layer and the Delivery Layer is referred to DMIF Application Interface
(DAI). It offers content location independent procedures for establishing MPEG-4 sessions and
access to transport channels. Also it provides default DMIF signaling protocol which
corresponding to the DMIF Network Interface (DNI).
6.1.2.1 MPEG-4 DMIF Architecture
DMIF framework covers three major technologies: (1) interactive network technology, (2)
broadcast technology and (3) the disk technology. An application accesses data through the DAI
irrespectively whether such data comes from a broadcast source, from local storage or from remote
server. In all scenarios the Local Application only interacts through DAI primitives. Figure 6-4
clarifies the DMIF aim.
Local DMIF
for Broadcast
Remote DMIF
(emulated)
Remote App.
(emulated)
Broadcast
source
Local
App
DMIF Filter
Local DMIF
for Local Files
Remote
DMIF
(emulated)
Remote App.
(emulated)
Local
Storage
Local DMIF
for Remote srv
Sig
map
Network
DAI
DNI
Sig
map
Remote DMIF
(Real)
Remote
App
DNI
DAI
Figure 6-4: MPEG-4 DMIF architecture
6.1.2.2 DMIF Layer
MPEG-4 DMIF allows each delivery technology to be used for its unique characteristics in a
way transparent to application developers. Figure 6-5 shows the composition of DMIF stack in
conjunction with an IP-based underlying networking environment.
MPEG-4 Application
DMIF Application Interface
DMIF Network Interface
}DMIF
TCP/UDP
IP
Figure 6-5: DMIF stack protocols with IP networks
DMIF contains functionality needed to establish sessions and connections between an
application running at server side and an application running at client side over transport networks.
In general, DMIF provides the following functionalities:
144