RUS Projects Communication Systems BeWü Development 1 Payload for MPEG-4 with Scaleable and Flexible Error Resiliency RTP Payload for MPEG-4 with Scaleable and Flexible Error Resiliency draft-guillemot-genrtp-01.txt Christine Guillemot, Paul Christ, Stefan Wesner, Anders Klemets

RUS Projects Communication Systems BeWü Development 2 MPEG-4/RTP recent history l “No non-SL- and non-Systems ES RTP-mapping needed”: draft-ietf-avt-mpeg4- l 12/98 Orlando, 04/99 NY, 07/99 Oslo joint IETF/MEG (phone) meetings => “ 2 experimental RFCs...” l 10/99 ISO Melbourne n JNB non-System AV ES-mapping proposed n draft-ietf-guillemot- disappeared/obscured n N3021 to extend draft-ietf-avt-mpeg4... <= Liaison statement N2987 l 12/99 Washington draft-jnb-mpeg4av-rtp-00.txt „ the normative way on how MPEG-4 Audio/Visual streams... mapped... to RTP“ l “No non-SL- and non-Systems ES RTP-mapping needed”: draft-ietf-avt-mpeg4- l 12/98 Orlando, 04/99 NY, 07/99 Oslo joint IETF/MEG (phone) meetings => “ 2 experimental RFCs...” l 10/99 ISO Melbourne n JNB non-System AV ES-mapping proposed n draft-ietf-guillemot- disappeared/obscured n N3021 to extend draft-ietf-avt-mpeg4... <= Liaison statement N2987 l 12/99 Washington draft-jnb-mpeg4av-rtp-00.txt „ the normative way on how MPEG-4 Audio/Visual streams... mapped... to RTP“

RUS Projects Communication Systems BeWü Development 3 Dimensions of MPEG-4/RTP l Network Characteristics - Packet loss versus BER l Application Scenario n Terminal - Server - now (draft-avt-..., draft-guillemot-...) n p-to-p realtime conversational (JNB) n (Multi) Peer-to-Peer - when? n Mixed - when? l RT, Live versus Pre-Encoded Media l Supporting the Systems (OD) Framework n SLdraft-ietf-avt-, draft-ietf-guillemot- n non-SLdraft-ietf-guillemot l Outside the Systems (without OD) Framework n MPEG-4 Audio EP-Mode, JNB proposal - e.g. use within H.323 n MPEG-4 Video n non-SLdraft-ietf-guillemot l Network Characteristics - Packet loss versus BER l Application Scenario n Terminal - Server - now (draft-avt-..., draft-guillemot-...) n p-to-p realtime conversational (JNB) n (Multi) Peer-to-Peer - when? n Mixed - when? l RT, Live versus Pre-Encoded Media l Supporting the Systems (OD) Framework n SLdraft-ietf-avt-, draft-ietf-guillemot- n non-SLdraft-ietf-guillemot l Outside the Systems (without OD) Framework n MPEG-4 Audio EP-Mode, JNB proposal - e.g. use within H.323 n MPEG-4 Video n non-SLdraft-ietf-guillemot

RUS Projects Communication Systems BeWü Development 4 l Unified solution for the transport of MPEG-4 n MPEG-4 SL packet streams - and for n MPEG-4 ES l Common media-aware solution for error protection n adaptive to varying network conditions n both live and pre- recorded content l Unified solution for the transport of MPEG-4 n MPEG-4 SL packet streams - and for n MPEG-4 ES l Common media-aware solution for error protection n adaptive to varying network conditions n both live and pre- recorded content Motivations and Rationale 1

RUS Projects Communication Systems BeWü Development 5 Motivations and Rationale 2 l Packet Loss - generic/flexible protection mechanisms n Assuming a media and network aware adaptation layer n Abstracting media idiosyncrasies n Full and partial AUs as Typed Segments (“ESI”, hint track) n Towards UEP based on typed segments l (high number of streams applications) l Packet Loss - generic/flexible protection mechanisms n Assuming a media and network aware adaptation layer n Abstracting media idiosyncrasies n Full and partial AUs as Typed Segments (“ESI”, hint track) n Towards UEP based on typed segments l (high number of streams applications)

RUS Projects Communication Systems BeWü Development 6 Implementation status l Mapping/de-mapping completed and under test l Adaptivity under development l Integrating into IM1 is ongoing n SL-PDU mapping + protection at packet level l Improvement of FEC under development R-S, Convolutional Codes l UEP under development l Mapping/de-mapping completed and under test l Adaptivity under development l Integrating into IM1 is ongoing n SL-PDU mapping + protection at packet level l Improvement of FEC under development R-S, Convolutional Codes l UEP under development

RUS Projects Communication Systems BeWü Development 7 Information - Distribution l current code documentation n l code from l ACTS COMIQS project n l Distributed to 4 Companies outside COMIQS l Used in 1 National Project (F) l Candidate for 2 forthcoming European Projects l current code documentation n l code from l ACTS COMIQS project n l Distributed to 4 Companies outside COMIQS l Used in 1 National Project (F) l Candidate for 2 forthcoming European Projects

RUS Projects Communication Systems BeWü Development 8 Conclusion l Complexity of (future) MPEG-4 usage unknown and not obviously bounded l The concept of hiding media idiosyncrasies has the potential to efficiently cope with that complexity both in the case of MEPEG-4 and possibly others l... otherwise we will see a dozen+ specific MPEG-4 media payloads on top of RTP l Experiments will show the value the concept l Complexity of (future) MPEG-4 usage unknown and not obviously bounded l The concept of hiding media idiosyncrasies has the potential to efficiently cope with that complexity both in the case of MEPEG-4 and possibly others l... otherwise we will see a dozen+ specific MPEG-4 media payloads on top of RTP l Experiments will show the value the concept

RUS Projects Communication Systems BeWü Development 9 Why Not Simply... COMPRESSION LAYER NETWORK ADAPTATION LAYER Redundancy, FEC mechanism ESI RAP Flag Segment Type ES Descriptor RTP Hdr Media Ext. Data = pro tect “SL“| QoS Monitor SLConfigDescriptor (RTCP) 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