2. July 27,1999 DMIF Overview DMIF-1 MPEG-4 표준화 : 멀티미디어 전송 (DMIF) 서울시립대학교 전자전기공학부 최성종 chois@uoscc.uos.ac.kr http://jungmin.uos.ac.kr

3. July 27,1999 DMIF Overview DMIF-2 Explain the DMIF concepts and tools Identify relationship to MPEG-4 Give practical hints on how to use DMIF The Purpose of this Presentation

4. July 27,1999 DMIF Overview DMIF-3 What is DMIF?

5. July 27,1999 DMIF Overview DMIF-4 What is MPEG DMIF? Transparent control interface and procedures for the delivery of MPEG streams irrespective of the source site being a remote interactive terminal on a network, broadcast or file system. DMIFDMIF elivery ultmedia ntegration ramework Delivery of Multimedia Contents + Integration Framework: 단순한 file 전송 (cf. FTP) 이 아닌 Multimedia 자료 전송 : QoS Management 기존의 전송기술을 통합 하여 사용할 수 있는 방법 제시

6. July 27,1999 DMIF Overview DMIF-5 The DMIF Integration Framework

7. July 27,1999 DMIF Overview DMIF-6 Main Objectives of DMIF to hide the delivery technology details from the DMIF User to ensure interoperability between end-systems to manage real time, QoS sensitive channels to allow service providers to log resources per session for usage accounting In achieving above DMIF adopts an Integration Framework to make use of existing standards

8. July 27,1999 DMIF Overview DMIF-7 DMIF & MPEG-4

9. July 27,1999 DMIF Overview DMIF-8 14496-1Systems 14496-2Visual 14496-3Audio 14496-4Conformance Testing 14496-5Reference Software 14496-6Delivery Multimedia Integration Framework (DMIF) MPEG-4 Parts and Versions

10. July 27,1999 DMIF Overview DMIF-9 Compression Layer Streams from as low as bps to Mbps media aware delivery unaware 14496-2Visual 14496-3Audio Elementary Stream Interface (ESI) Systems Layer Manages Elementary Streams, their synchronization and hierarchical relations media and delivery unaware 14496-1Systems Delivery Layer Provides transparent access and delivery of content irrespective of delivery technologies DMIF Application Interface (DAI) delivery aware media unaware 14496-6 DMIF Generic MPEG-4 terminal architecture

11. July 27,1999 DMIF Overview DMIF-10 NetworkNetwork... Elementary Streams DMIF DAI... Decoding Audiovisual Interactive Scene Composition and Rendering Primitive AV Objects Scene Description Information Object Descriptor Display and Local User Interaction... Elementary Streams ESI MPEG-4 Systems DMIF Relationship to MPEG-4

12. July 27,1999 DMIF Overview DMIF-11 The MPEG-4 System User Plane Model

13. July 27,1999 DMIF Overview DMIF-12 DMIF Models

14. July 27,1999 DMIF Overview DMIF-13 The DMIF Computational Model 1- A Service Session is requested at the originating DMIF 2- A Network Session is created between the DMIF peers 3- The target DMIF identifies the Target Application and creates a Service Session 4- Thru the path 1, 2, and 3, the applications create channels in the user plane Originating terminal Target terminal App DMIF App1 1 2 3 4 App2 특정 서비스를 요청 특정 서비스를 제공 Channel: 사용자가 멀티미디어 자료를 전송하는 전송로

15. July 27,1999 DMIF Overview DMIF-14 Important Definitions User plane Control plane Originating terminal Target terminal DMIF user = Application Session

16. July 27,1999 DMIF Overview DMIF-15 DMIF V1 DMIF V1 addresses the following scenarios: –multicast/broadcast –local storage –remote interactive Broadcast source Local Storage Network

17. July 27,1999 DMIF Overview DMIF-16 DMIF Reference Architecture Target App DAI Origin. App DAI Network Broadcast source Local Storage DMIF V1 defines the reference architecture

18. July 27,1999 DMIF Overview DMIF-17 DMIF Reference Architecture DMIF V1 defines the signalling tools for remote interactive scenarios Target App DAI Origin. App DAI Network Broadcast source Local Storage

19. July 27,1999 DMIF Overview DMIF-18 DMIF Reference Architecture - DMIF Instance

20. July 27,1999 DMIF Overview DMIF-19 DMIF Application Interface DAI

21. July 27,1999 DMIF Overview DMIF-20 DMIF Application Interface (DAI) 멀티미디어 서비스 전송를 위해 DAI 는 특정 전송기술에 관계없이 응용프로그램을 개발할 수 있도록 기능을 정의한다. Originating DMIFTarget DMIF App DMIF App1 1 2 3 4 App2 DAI

22. July 27,1999 DMIF Overview DMIF-21 A comparison: DAI vs. Socket

23. July 27,1999 DMIF Overview DMIF-22 Characteristics of DAI For development of applications involving media content delivery, irrespective of delivery technology So far, define semantics (not syntax, nor programming language) –depends on programming language –lack of interoperability Only syntax specified is the URL, for locating services. Define minimal semantics: more functions, and more parameters may be defined for real implementation. Designed for generic use: none MPEG-4 application can use DAI. Comprised of the following classes of primitives: –Service primitives establish a session between peers –Channel primitives negotiate resource parameters for QOS –Data primitives sending & receiving data over the channel

24. July 27,1999 DMIF Overview DMIF-23 DAI primitives - Semantic Definition DA_ServiceAttach (IN: URL, uuDataInBuffer, uuDataInLen; OUT: response, serviceSessionId, uuDataOutBuffer, uuDataOutLen) DA_ServiceAttachCallback (IN: serviceSessionId, serviceName, uuDataInBuffer, uuDataInLen; OUT: response, uuDataOutBuffer, uuDataOutLen) DA_ServiceDetach (IN: serviceSessionId, reason; OUT: response) DA_ServiceDetachCallback (IN: serviceSessionId, reason; OUT: response) DA_ChannelAdd (IN: serviceSessionId, loop(qosDescriptor, direction, uuDataInBuffer, uuDataInLen); OUT: loop(response, channelHandle, uuDataOutBuffer, uuDataOutLen )) DA_ChannelAddCallback (IN: serviceSessionId, loop(channelHandle, qosDescriptor, direction, uuDataInBuffer, uuDataInLen); OUT: loop(response, uuDataOutBuffer, uuDataOutLen)) DA_ChannelDelete (IN: loop(channelHandle, reason); OUT: loop(response)) DA_ChannelDeleteCallback (IN: loop(channelHandle, reason); OUT: loop(response)) DA_UserCommand (IN: loop(channelHandle, uuDataInBuffer, uuDataInLen)) DA_UserCommandCallback (IN: loop(channelHandle, uuDataInBuffer, uuDataInLen)) DA_Data (IN: channelHandle, streamDataBuffer, streamDataLen) DA_DataCallback (IN: channelHandle, streamDataBuffer, streamDataLen, errorFlag)

25. July 27,1999 DMIF Overview DMIF-24 DAI Semantics Originating Application initiates Target DMIF initiates

26. July 27,1999 DMIF Overview DMIF-25 DAI Semantics

27. July 27,1999 DMIF Overview DMIF-26 Structure of the DAI Primitives (without Callback) DA_ServiceAttach (IN: URL,...; OUT:..., serviceSessionId...) Name of the primitive for originating terminal Request Parameters from Application to DMIF layer Confirm Parameters from DMIF layer to Application

28. July 27,1999 DMIF Overview DMIF-27 Structure of the DAI Primitives (with Callback) DA_ServiceAttachCallback (IN: serviceSessionId,... ; OUT: response,... ) Name of the primitive for target terminal Indication Parameters from DMIF layer to Application Response Parameters from Application to DMIF layer

29. July 27,1999 DMIF Overview DMIF-28 DAI Semantics - uu Prefix Prefix uu: The parameter is transparently transported between DMIF users through DMIF, i.e, opaque data structure. Therefore, uuData exist as a pair in the primitive and callback primitive Example: DA_ServiceAttach (IN:..., uuDataInBuffer,...; OUT:..., uuDataOutBuffer,...) DA_ServiceAttachCallback (IN:..., uuDataInBuffer,...; OUT:..., uuDataOutBuffer,...)

30. July 27,1999 DMIF Overview DMIF-29 DAI Primitive Sequence (two different representations)

31. July 27,1999 DMIF Overview DMIF-30 DAI Primitive Sequence

32. July 27,1999 DMIF Overview DMIF-31 DAI Semantics - review DA_ServiceAttach (IN: URL, uuDataInBuffer, uuDataInLen; OUT: response, serviceSessionId, uuDataOutBuffer, uuDataOutLen) DA_ServiceAttachCallback (IN: serviceSessionId, serviceName, uuDataInBuffer, uuDataInLen; OUT: response, uuDataOutBuffer, uuDataOutLen) DA_ServiceDetach (IN: serviceSessionId, reason; OUT: response) DA_ServiceDetachCallback (IN: serviceSessionId, reason; OUT: response) DA_ChannelAdd (IN: serviceSessionId, loop(qosDescriptor, direction, uuDataInBuffer, uuDataInLen); OUT: loop(response, channelHandle, uuDataOutBuffer, uuDataOutLen )) DA_ChannelAddCallback (IN: serviceSessionId, loop(channelHandle, qosDescriptor, direction, uuDataInBuffer, uuDataInLen); OUT: loop(response, uuDataOutBuffer, uuDataOutLen)) DA_ChannelDelete (IN: loop(channelHandle, reason); OUT: loop(response)) DA_ChannelDeleteCallback (IN: loop(channelHandle, reason); OUT: loop(response)) DA_UserCommand (IN: loop(channelHandle, uuDataInBuffer, uuDataInLen)) DA_UserCommandCallback (IN: loop(channelHandle, uuDataInBuffer, uuDataInLen)) DA_Data (IN: channelHandle, streamDataBuffer, streamDataLen) DA_DataCallback (IN: channelHandle, streamDataBuffer, streamDataLen, errorFlag)

33. July 27,1999 DMIF Overview DMIF-32 DMIF Network Interface DNI

34. July 27,1999 DMIF Overview DMIF-33 DNI - Where??

35. July 27,1999 DMIF Overview DMIF-34 DMIF Network Interface (DNI) Only for interactive network scenario a semantic API that abstracts the signalling between DMIF peers irrespectively of the delivery support. The DNI is informative, and is introduced in support to the description of the DMIF Signalling Protocol Defined to support DAI for various network protocols DNI primitives are translated into the native network signaling mechanism Comprised of the following classes of primitives: –Session primitives: session management (setup & release) –Service primitives: service management (attach & detach) –Transmux primitives: transmux management (setup, release, & config) –Channel primitives: channel management (add& delete) –UserCommand primitives

36. July 27,1999 DMIF Overview DMIF-35 Scenarios for Multimedia delivery using DAI & DNI

37. July 27,1999 DMIF Overview DMIF-36 Information flows for Remote Interactive DMIF

38. July 27,1999 DMIF Overview DMIF-37 Addition of Channel in a Remote Interactive DMIF by Target DMIF

39. July 27,1999 DMIF Overview DMIF-38 Addition of Channel in a Remote Interactive DMIF by Originating DMIF

40. July 27,1999 DMIF Overview DMIF-39 Deletion of Channels in a Remote Interactive DMIF

41. July 27,1999 DMIF Overview DMIF-40 Termination of a Service in a Remote Interactive DMIF

42. July 27,1999 DMIF Overview DMIF-41 More Tools: DMIF V2

43. July 27,1999 DMIF Overview DMIF-42 DMIF V2 QoS Monitoring Multicast Signalling Tools DAI Syntax Mobile Support

44. July 27,1999 DMIF Overview DMIF-43 Delivery of MPEG-4 Contents over... MPEG-2 TS MP4 IP MOBILE ATM DAB

45. July 27,1999 DMIF Overview DMIF-44 Delivery Technologies

46. July 27,1999 DMIF Overview DMIF-45 Summary

47. July 27,1999 DMIF Overview DMIF-46 Advantages for Developers The application is written once (DAI); then, by simply plugging in more DMIF instances and by using different URLs, the application would run on more delivery technologies. Investments in commercial multimedia applications would not depend on guesses on the network technology of tomorrow.

48. July 27,1999 DMIF Overview DMIF-47 Advantages for Network Operators The model allows for flexible charging policies in presence of QoS. it also enables the effective exploitation of Intelligent Networks, by plugging in an appropriate and proprietary DMIF instance

49. July 27,1999 DMIF Overview DMIF-48 Conclusion The DMIF model would benefit many players of the multimedia industry, and provides a framework to find solutions for issues like: –advanced charging policies –QoS management. Moreover, it guarantees permanence of multimedia application in presence of new delivery technologies

50. July 27,1999 DMIF Overview DMIF-49 Question and Answer

51. July 27,1999 DMIF Overview DMIF-50 Terminology Session: A related set of communications transactions between two or more network devices. Signaling: The process of sending a transmission signal over a physical medium for purposes of communication.

52. July 27,1999 DMIF Overview DMIF-51 The DMIF Tools at Originating and Target End-Systems Application e.g., Browser DAI (DSI) Session Mgr FlexMuxTransMux Control Stream/Data DAI = DMIF-Application Interface (control) (DSI) = DMIF Signaling Interface (hidden control primitives) H.310, H.323 & DMIF Signaling Standards DSM-CC U-U Carousel File Control DMIF End-System

53. July 27,1999 DMIF Overview DMIF-52 A DMIF Model TRANSPORT NETWORKS (Note 1) Application (MPEG-4) DMIF DMIF Receiver Peer role (Client ) Application (MPEG-4) DMIF DMIF Sender Peer role (Server, Broadcast, Local Storage ) DMIF SRM = Not present in case of pure broadcast SRM= Session and Resource Management function Note 1: Includes I/O bus and drivers for local terminal storage = Invoked on demand DMIF-Application Interface (Note 2) DMIF-Application Interface (Note 2) Note 2: DMIF-Application Interface is designed for generic use and not just for MPEG-4 applications