DNI - DMIF Network Interface

By: Preethi Ramkumar

Meaning of DNI – “DMIF Network Interface”, define the separation between the User Plane and the Control Plane. DMIF is split into two basic planes: the User Plane and the Control Plane. These are separated and encapsulated by the DAI and DNI interfaces. Anything that functions above the DMIF Network Interface is said to be in the User Plane. DMIF User sits here and controls Service Attachments and Channels. The Control Plane lies between the DAI and the DMIF Network Interface (the DNI). The transMux channels and buffer resources are allocated and de-allocated in the Control Plane.

DNI also abstracts the signaling mechanisms used between peers in the network session, irrespective of the delivery technologies. This means that the DNI semantics are mapped to whichever network dependant native signaling is available, keeping the delivery mechanisms hidden from the higher layers. The DNI primitives are the defining elements of the DNI. These include: Session primitives (setup and release) Service primitives (attach and detach) Transmux primitives (setup and release) Channel primitives (add and delete) Session primitives exist in the DNI and not the DAI because it lies within the scope of delivery-related data. Since the DAI is completely hidden from such details, it is not required there. A typical session will begin with a session setup with the remote control plane, then a service attach, to notify the remote peer service and check for its existence. Before channels can be added, the a transmux setup must be performed, to establish at least one transmux stream.

Other Related Definitions:

“…The DMIF specification compares the overall design to FTP. There is a DMIF Application Interface (DAI) and the DMIF Network Interface (DNI). The application uses the DAI to establish a session, and the DMIF layer maps this through to the DNI to signal the appropriate network resources. How this happens is very application pattern dependent. For example, an application for local storage is quite different from one for remote interaction. Network channels are called transmuxes and a general model of mapping elementary MPEG streams onto these channels is defined, together with a specific mapping for low latency, low overhead (i.e. multiple streams per network channel) is offered in the TransMux channel model in the standard.” [ISO MPEG]

“…AAA is a fundamental aspect of IP networking. As mobile IP technology expands to enable a multitude of mobile, Internet-enabled devices, AAA servers will provide the means of administering policy to ensure proper use and management of resources.” [MobileIN.com]

“…Collectively, authentication, authorization, and accounting are sometimes referred to as AAA. Central management of AAA means the information is in a single, centralized, secure database. This is much easier to administer than information distributed across numerous devices.” [Peter J. Welcher - Chesapeake NetCraftsmen]

Related Links:

DMIF network Interface (DNI) - Internet Engineering Task Force
DMIF specification - Cordis

Technical Resources:

Internet Delivery of MPEG-4 Object-Based Multimedia - IEEE Computer Society

Products and Solutions:

Citeseer
Eurescom

Blogs, News, Feeds, Discussion Lists:

The key elements of DMIF
DMIF & System

Books About:

The MPEG-4 Book - by Touradj Ebrahimi, Fernando Pereira

See Also:

Other DNI Related Resources

 

(C) Copyright Birds-Eye.Net, All rights reserved.
It is against the law to reproduce this content or any portion of it in any form without the explicit written permission of Birds-Eye Network Services, LLC. Federal copyright law (17 USC 504) makes it illegal, punishable with fines up to $100,000 per violation plus attorney's fees.