90 likes | 204 Views
RTP Payload for MPEG-4 with Scaleable and Flexible Error Resiliency draft-guillemot-genrtp-01.txt. IETF AVT WG, Washington D.C. November 11, 1999. Christine Guillemot, Paul Christ , Stefan Wesner , Anders Klemets. MPEG-4/RTP recent history.
E N D
RTP Payload for MPEG-4with Scaleable and Flexible Error Resiliencydraft-guillemot-genrtp-01.txt IETF AVT WG, Washington D.C. November 11, 1999 Christine Guillemot, Paul Christ, Stefan Wesner, Anders Klemets
MPEG-4/RTP recent history • “No non-SL- and non-Systems ES RTP-mapping needed”:draft-ietf-avt-mpeg4- • 12/98 Orlando, 04/99 NY, 07/99 Oslo joint IETF/MEG(phone) meetings => “2 experimental RFCs ...” • 10/99 ISO Melbourne • JNB non-System AV ES-mapping proposed • draft-ietf-guillemot- disappeared/obscured • N3021 to extend draft-ietf-avt-mpeg4... <= Liaison statement N2987 • 12/99 Washington • draft-jnb-mpeg4av-rtp-00.txt „the normative way on how MPEG-4 Audio/Visual streams ... mapped ... to RTP“
Dimensions of MPEG-4/RTP • Network Characteristics - Packet loss versus BER • Application Scenario • Terminal - Server - now (draft-avt-..., draft-guillemot-...) • p-to-p realtime conversational (JNB) • (Multi) Peer-to-Peer - when? • Mixed - when? • RT, Live versus Pre-Encoded Media • Supporting the Systems (OD) Framework • SL draft-ietf-avt- , draft-ietf-guillemot- • non-SL draft-ietf-guillemot • Outside the Systems (without OD) Framework • MPEG-4 Audio EP-Mode, JNB proposal - e.g. use within H.323 • MPEG-4 Video • non-SL draft-ietf-guillemot
Motivations and Rationale 1 • Unified solution for the transport of MPEG-4 • MPEG-4 SL packet streams - and for • MPEG-4 ES • Common media-aware solution for error protection • adaptive to varying network conditions • both live and pre- recorded content
Motivations and Rationale 2 • Packet Loss - generic/flexible protection mechanisms • Assuming a media and network aware adaptation layer • Abstracting media idiosyncrasies • Full and partial AUs as Typed Segments (“ESI”, hint track) • Towards UEP based on typed segments • (high number of streams applications)
Implementation status • Mapping/de-mapping completed and under test • Adaptivity under development • Integrating into IM1 is ongoing • SL-PDU mapping + protection at packet level • Improvement of FEC under development R-S, Convolutional Codes • UEP under development
Information - Distribution • current code documentation • http://www-ks.rus.uni-stuttgart.de/PROJ/GP • code from wesner@rus.uni-stuttgart.de • ACTS COMIQS project • http://www.ccett.fr/comiqs/welcome.htm • Distributed to 4 Companies outside COMIQS • Used in 1 National Project (F) • Candidate for 2 forthcoming European Projects
Conclusion • Complexity of (future) MPEG-4 usage unknown and not obviously bounded • The concept of hiding media idiosyncrasies hasthe potential to efficiently cope with that complexity both in the case of MEPEG-4 and possibly others • ... otherwise we will see a dozen+ specific MPEG-4 media payloads on top of RTP • Experiments will show the value the concept
Why Not Simply ... • VOS hrd • VO hdr • VOL hdr • GVOP hdr • FBA object • Mesh Object • video packet • setupdata (LAM) • audio payload mux element (LATM) • CelpSpecificConfig() • CelpBWSenhHeader() • CelpBaseFrame(), • CelpBRSenhFrame(), • CelpBWSenhFrame() • .. Same for T/F coder • .. Same fro parametric coder • Audio class for UEP SEGMENT TYPES COMPRESSION LAYER ES Descriptor ESI Segment Type RAP Flag SLConfigDescriptor NETWORK ADAPTATION LAYER Redundancy, FEC mechanism QoS Monitor “SL“| Media Ext. Data = protect RTPHdr (RTCP)