190 likes | 316 Views
MPEG-4 Approach to QoS. Reinhard Baier, GMD FOKUS, DT Guido Franceschini, CSELT, IT. What’s MPEG-4?. ISO/IEC 14496 - Information Technology - Generic Coding of Audio-Visual Object. 14496 -1: Systems 14496 -2: Visual 14496 -3: Audio 14496 -4: Conformance 14496 -5: Reference Software
E N D
MPEG-4 Approach to QoS Reinhard Baier, GMD FOKUS, DT Guido Franceschini, CSELT, IT
What’s MPEG-4? • ISO/IEC 14496 - Information Technology - Generic Coding of Audio-Visual Object • 14496-1: Systems • 14496-2: Visual • 14496-3: Audio • 14496-4: Conformance • 14496-5: Reference Software • 14496-6: DMIF
voice AV presentation video object 2D background 3D furniture MPEG-4 - A scene
scene person 2Dbackground furniture audiovisual presentation voice video globe desk MPEG-4 - A scene description
What’s DMIF? • Delivery Multimedia Information Framework • DMIF is part 6 of MPEG-4 • DMIF specifies the Delivery Layer of MPEG-4
Why DMIF? • too many delivery technologies, each with its own peculiarities • no consolidated solution for real time multimedia streaming at certain QoS • different APIs for different environments (Local Files, Broadcast sources, Interactive servers through a variety of transports) • difficulties for network operators in defining meaningful billing policies (e.g. the “flat” Internet)
Favour the development of multimedia application with QoS requirements Hide the delivery technology details to the DMIF User Make optimal usage of network resources, given application QoS constraints Allow Network Operators to monitor resources being consumed in a single session, to allow meaningful billing policies Ensure interoperability between end-systems DMIF goals
The generic MPEG-4 architecture media related Compression Layer ESI Systems Layer DAI delivery related Delivery Layer
Local App Broadcast source Local Storage Network DAI DMIF communication architecture (1) Remote App DAI
Local App Local DMIF for Broadcast Remote App. (emulated) Broadcast source DMIF Filter DAI DMIF communication architecture (2) Remote DMIF (emulated)
Local App Remote App. (emulated) Local Storage DMIF Filter DAI DMIF communication architecture (3) Local DMIF for Local Files Remote DMIF (emulated)
Local App Local DMIF for Broadcast Remote App. (emulated) Remote DMIF (emulated) Broadcast source Remote App. (emulated) Local DMIF for Local Files Remote DMIF (emulated) Local Storage DMIF Filter Local DMIF for Remote srv Sig map Network DAI DNI Remote App Remote DMIF (Real) Sig map DNI DAI DMIF communication architecture (4) PLAY PLAY PLAY PLAY
Still under debate Requirements are: to represent the location of a Service to localize the Service on a variety of delivery technologies, including local files, MPEG-2 broadcast, IP and ATM networks to represent any kind of address to identify the control protocol to be used (including Intelligent Networks ?) DMIF URLs
QoS “media” metrics: used by the application when requesting a channel QoS “transport” metrics: a generic network centric translation of the above QoS “network” (specific) metrics: the final set of metrics used in the native network signaling QoS in DMIF
Advantages for Developers • they may write the application just once; then, by simply plugging in more DMIF instances and by feeding the application with different URLs, the application would run on other delivery technologies. • they can begin to invest in commercial multimedia applications with the assurance that their investment will not be made obsolete by new delivery technologies.
Advantages for Network Operators • the model allows for meaningful and flexible billing policies in presence of QoS • it also enables the effective exploitation of Intelligent Networks, by plugging in an appropriate and proprietary DMIF instance
The DMIF model would benefit many players of the multimedia industry, and provides solutions for yet unsolved issues like: meaningful billing policies permanence of multimedia application in the presence of new delivery technologies QoS management. Conclusion