1 RUS Projects Communication Systems BeWü Development RTP Payload for MPEG-4 Payload for MPEG-4 with Flexible Error with Flexible Error Resiliency Resiliency draft-ietf-avt-mpeg4streams- 00.txt proposed experimental RFC formerly draft-guillemot-avt- genrtp-03.txt ne Guillemot, Paul Christ , Stefan Wesner [, Anders
24
Embed
Christine Guillemot, Paul Christ , Stefan Wesner [, Anders Klemets]
RTP Payload for MPEG-4 with Flexible Error Resiliency draft-ietf-avt-mpeg4streams-00.txt proposed experimental RFC formerly draft-guillemot-avt-genrtp-03.txt. IETF AVT WG, Adelaide. March, 2000. Christine Guillemot, Paul Christ , Stefan Wesner [, Anders Klemets]. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
RUSProjects Communication Systems
BeWü Development
RTP Payload for MPEG-4 Payload for MPEG-4
with Flexible Error Resiliencywith Flexible Error Resiliency draft-ietf-avt-mpeg4streams-00.txt
proposed experimental RFC
formerly draft-guillemot-avt-genrtp-03.txt
RTP Payload for MPEG-4 Payload for MPEG-4
with Flexible Error Resiliencywith Flexible Error Resiliency draft-ietf-avt-mpeg4streams-00.txt
proposed experimental RFC
formerly draft-guillemot-avt-genrtp-03.txt Christine Guillemot, Paul Christ, Stefan Wesner [, Anders Klemets]
2
RUSProjects Communication Systems
BeWü Development
draft-guillemot-avt-genrtp-03.txt => new title Flexmux section added in discussion with authors - (see draft-
rgcc-flexmuxmpeg4-00.txt);
Payload Type (PT): Different payload types should be assigned for MPEG4 ES, MPEG4 SL-PDU MPEG-4 FlexMux streams. A payload type in the dynamic range should be chosen.
Same format, same interface ES, SL, Flexmux
TSOFFSET removed, Ebits included
draft-guillemot-avt-genrtp-03.txt => new title Flexmux section added in discussion with authors - (see draft-
rgcc-flexmuxmpeg4-00.txt);
Payload Type (PT): Different payload types should be assigned for MPEG4 ES, MPEG4 SL-PDU MPEG-4 FlexMux streams. A payload type in the dynamic range should be chosen.
Same format, same interface ES, SL, Flexmux
TSOFFSET removed, Ebits included
Modifications since WashingtonModifications since Washington
3
RUSProjects Communication Systems
BeWü Development
Multiple Dimensions of MPEG-4/RTPMultiple Dimensions of MPEG-4/RTP
Systems (OD) or non-systems (non-OD) framework
Various types of streams with different QoS requirements (MPEG-4 A/V, OD, BIFS, IPMP, other compressed AV
Unified solution for the transport of MPEG-4 MPEG-4 SL packet streams - and for MPEG-4 ES
Common solution for both live and pre- encoded content
Applicable to the transport of FlexMux PD (submitted draft-rgcc-avt-mpeg4flexmux-00.txt)
Unified solution for the transport of MPEG-4 MPEG-4 SL packet streams - and for MPEG-4 ES
Common solution for both live and pre- encoded content
Applicable to the transport of FlexMux PD (submitted draft-rgcc-avt-mpeg4flexmux-00.txt)
Summary Summary
5
RUSProjects Communication Systems
BeWü Development
SummarySummary Abstraction of
QoS monitoring and Congestion Contro “intelligence” unique interface architectural simplicity and consistent stream “adaptation” in high number of streams applications (mixing real-time & pre-encoded content)
Packet Loss flexible protection mechanisms Full and partial AUs Segments with types or priority
Abstract media idiosyncrasies Assuming a media and network aware adaptation layer Towards UEP and/or Diffserv marking based on AUs
Abstraction of QoS monitoring and Congestion Contro “intelligence” unique interface architectural simplicity and consistent stream “adaptation” in high number of streams applications (mixing real-time & pre-encoded content)
Packet Loss flexible protection mechanisms Full and partial AUs Segments with types or priority
Abstract media idiosyncrasies Assuming a media and network aware adaptation layer Towards UEP and/or Diffserv marking based on AUs
6
RUSProjects Communication Systems
BeWü Development
Sample RTP packet for MPEG-4 ESsSample RTP packet for MPEG-4 ESs
- One byte difference with draft-ietf-avt-mpeg4-es-00.txt,Byte offering additional flexibility in terms of protection- The packet would be of this form if protection supported by compression layer in the case of real-time
7
RUSProjects Communication Systems
BeWü Development
Sample RTP packet for MPEG-4 ESsSample RTP packet for MPEG-4 ESs
If additional data-based protection needed (eg. duplicatedheaders), (no fragmentation used).
Usage of the format for MPEG-4 Flexmux-PDUs in draft-rgcc-avt-mpeg4flexmux-00.txt
Usage of the format for MPEG-4 Flexmux-PDUs in draft-rgcc-avt-mpeg4flexmux-00.txt« What is suggested here is to define objects in the RTP payload, asit is proposed in draft-ietf-avt-mpeg4streams-01.txt. The RTP payload being a succession of ob-jects. Each object is byte aligned. Each object starting with its length. »
« A payload object is either a protection data object, or a completeFlexMux packet. Each payload object follows an identification byte,its object type byte. The RTP payload starts with one object typebyte. »
« The object type byte syntax: 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+ |G|E| XT | +-+-+-+-+-+-+-+ »
11
RUSProjects Communication Systems
BeWü Development
MPEG-4/RTP recent historyMPEG-4/RTP recent history 12/98 Orlando,
draft-ietf-avt-rtp-mpeg4-00.txt, SL-packetized streams draft-guillemot-avt-genrtp-00.txt, ES streams + flexible additional
protection (if needed, eg. for streamed content)
04/99 NY + 07/99 Oslo joint IETF/MPEG (phone) meetings “No non-SL- and non-Systems ES RTP-mapping needed”: “2 experimental RFCs ...”
10/99 ISO Melbourne JNB non-System AV ES-mapping proposed
12/99 Washington draft-jnb-mpeg4av-rtp-00.txt „the normative way on how MPEG-4 Audio/Visual streams ... mapped ... to RTP“
Mapping/de-mapping completed Integrating into IM1 as a DMIF plug-in (with
CSELT) is ongoing FEC implemented: duplicated headers, parity codes Adaptivity for QoS monitoring under development R-S under development
Mapping/de-mapping completed Integrating into IM1 as a DMIF plug-in (with
CSELT) is ongoing FEC implemented: duplicated headers, parity codes Adaptivity for QoS monitoring under development R-S under development
14
RUSProjects Communication Systems
BeWü Development
Information - DistributionInformation - Distribution current code documentation
http://www-ks.rus.uni-stuttgart.de/PROJ/GP ACTS COMIQS project ended february 2000
http://www.ccett.fr/comiqs/welcome.htm Used in 1 National Project (F, RNRT-VISI) Continue in 2 European Projects (IST-SONG, IST-
OPENISE) Distributed to 4 Companies outside the above
projects
current code documentation http://www-ks.rus.uni-stuttgart.de/PROJ/GP
ACTS COMIQS project ended february 2000 http://www.ccett.fr/comiqs/welcome.htm
Used in 1 National Project (F, RNRT-VISI) Continue in 2 European Projects (IST-SONG, IST-
OPENISE) Distributed to 4 Companies outside the above
projects
15
RUSProjects Communication Systems
BeWü Development
ConclusionConclusion Complexity of (future) MPEG-4 usage
Multiple streams (live and pre-encoded) with different QoS requirements so far, multiple ways for handling protection in the different ESs (HEC specific to visual)
Stresses the need, for the sake of architectural « simplicity »,
simple, single interface, avoiding parsers of the ESs
draft-ietf-avt-mpeg4streams-01.txt has the potential for an homogeneous way of handling efficient transport of the different types of MPEG-4 streams
Complexity of (future) MPEG-4 usage Multiple streams (live and pre-encoded) with different QoS requirements so far, multiple ways for handling protection in the different ESs (HEC specific to visual)
Stresses the need, for the sake of architectural « simplicity »,
simple, single interface, avoiding parsers of the ESs
draft-ietf-avt-mpeg4streams-01.txt has the potential for an homogeneous way of handling efficient transport of the different types of MPEG-4 streams
16
RUSProjects Communication Systems
BeWü Development
Application Case of
draft-ietf-avt-mpeg4streams-01.txt
to MPEG-4 Visual streams
in draft-gc-avt-mpeg4visual-00.txt
Application Case of
draft-ietf-avt-mpeg4streams-01.txt
to MPEG-4 Visual streams
in draft-gc-avt-mpeg4visual-00.txt
Christine Guillemot, Paul Christ, Stefan Wesner
17
RUSProjects Communication Systems
BeWü Development
Application of drat-ietf-avt-mpeg4streams-01.txt to the transport of MPEG-4 visual streams
Common solution for both live and pre- encoded content
Common solution for the different profiles
Application of drat-ietf-avt-mpeg4streams-01.txt to the transport of MPEG-4 visual streams
Common solution for both live and pre- encoded content
Common solution for the different profiles
Summary Summary
18
RUSProjects Communication Systems
BeWü Development
Simple Visual Profile: efficient, error resilient coding of rectangular
video objects, suitable for applications on mobile networks.
Simple Scalable Profile: adds support for coding of temporal and spatial scalable objects, useful for applications which provide services at more than one level of quality due to bit-rate or decoder resource limitations.
Core Visual Profile: adds support for coding of arbitrary-shaped and temporally scalable objects, useful for applications such as those providing content-interactivity (Internet multimedia applications).
Simple Visual Profile: efficient, error resilient coding of rectangular
video objects, suitable for applications on mobile networks.
Simple Scalable Profile: adds support for coding of temporal and spatial scalable objects, useful for applications which provide services at more than one level of quality due to bit-rate or decoder resource limitations.
Core Visual Profile: adds support for coding of arbitrary-shaped and temporally scalable objects, useful for applications such as those providing content-interactivity (Internet multimedia applications).
Visual Profiles Visual Profiles
19
RUSProjects Communication Systems
BeWü Development
Main Visual Profile: adds support for coding of interlaced, semi-
transparent, and sprite objects to the Core Visual Profile; useful for
interactive and entertainment-quality broadcast and DVD applications.
N-Bit Visual Profile: adds support for coding video objects having
pixel-depths ranging from 4 to 12 bits to the Core Visual Profile.
…. More for synthetic and for natural/synthetic hybrid visual content
Main Visual Profile: adds support for coding of interlaced, semi-
transparent, and sprite objects to the Core Visual Profile; useful for
interactive and entertainment-quality broadcast and DVD applications.
N-Bit Visual Profile: adds support for coding video objects having
pixel-depths ranging from 4 to 12 bits to the Core Visual Profile.
…. More for synthetic and for natural/synthetic hybrid visual content