[AVT] Re: Question about "PayloadSize" field in MPEG-4 RTP payload format

philippe.gentric@philips.com Wed, 22 August 2001 12:58 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04696; Wed, 22 Aug 2001 08:58:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA10495; Wed, 22 Aug 2001 08:53:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA10444 for <avt@ns.ietf.org>; Wed, 22 Aug 2001 08:52:11 -0400 (EDT)
Received: from gw-nl4.philips.com (gw-nl4.philips.com [212.153.190.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04256 for <avt@ietf.org>; Wed, 22 Aug 2001 08:50:50 -0400 (EDT)
From: philippe.gentric@philips.com
Received: from smtpscan-nl3.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id OAA20741; Wed, 22 Aug 2001 14:52:04 +0200 (MEST) (envelope-from philippe.gentric@philips.com)
Received: from smtpscan-nl3.philips.com(130.139.36.23) by gw-nl4.philips.com via mwrap (4.0a) id xma020739; Wed, 22 Aug 01 14:52:04 +0200
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) by smtpscan-nl3.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id OAA07764; Wed, 22 Aug 2001 14:52:02 +0200 (MET DST)
Received: from notessmtp-nl1.philips.com (notessmtp-nl1.philips.com [130.139.36.10]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id OAA11516; Wed, 22 Aug 2001 14:51:59 +0200 (MET DST)
Received: from EMAUO01.diamond.philips.com (emauo01sv1.diamond.philips.com [130.143.165.215]) by notessmtp-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id OAA19014; Wed, 22 Aug 2001 14:51:58 +0200 (MET DST)
To: young@techway.co.kr
Cc: 4on2andIP-sys@advent.ee.columbia.edu, avt@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001
Message-ID: <OFD7A28E9E.AA18F78C-ONC1256AB0.00449B4F@diamond.philips.com>
Date: Wed, 22 Aug 2001 14:50:49 +0200
X-MIMETrack: Serialize by Router on EMAUO01/H/SERVER/PHILIPS(Release 5.0.5 |September 22, 2000) at 22/08/2001 15:07:12
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Subject: [AVT] Re: Question about "PayloadSize" field in MPEG-4 RTP payload format
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org



it is not a singleSL *MODE* issue,

the absolute rule is that the presence of PayloadSize
(SizeLength != 0) is a total equivalence
(mathematical symbol <=> ;-)
with multipleSL mode

i.e.
Single SL mode == NO PayloadSize field (never)
Multiple SL mode == PayloadSize field (always)

HOWEVER

it may happen that in the multipleSL mode
you have an Access Unit so large that
it is actually larger than the MTU,
then you will split this large AU in
several SL packet and therefore
transport each of these SL packets
in one RTP packet.

***********
so this is a "single SL packet" but the MODE
REMAINS multipleSL (the mode cannot change
inside a session anyway)
***********

in that case since the mode is multiple
you HAVE the PayloadSize field.

It would be stupid to waste this field by putting
in this field the (single) SL packet size
since UDP already gives you that !

moreover it is very helpfull to give (repeat)
the *complete AU size* in this PayloadSIze field.
it helps a receuver finding out if
a complete AU has arrived or not in
case of packet losses .

*******
NOTE:

Actually in case this "single" SL packet
in the RTP packet is actually a
complete Access Unit the
packet structure is
exactly the same as previoulsly !

NOTE (2)

of course if you have such a stream
(1 AU >= 1 RTP packet)
you have NOW a choice:

(1) use the SingleSL (default) mode because
it saves SizeLength bits per packet !

(2) use the MultipleSL mode because
it makes AU reconstrcution easier !

but for best efficiency
of AU reconstruction strategy
I would recommend the usage
of AUstartFalg and AUendFlag:
only 2 bits per packet ...
you have to be a Synch Layer
fan to do that though ;-)


*****
in conclusion it is not a mode issue
it is a "smart" exception for
single SL transport in the MultilpleSL mode


is that more clear ?

Regards,

Philippe Gentric
Software architect
Philips Digital Networks - MP4Net
51 rue Carnot B.P. 301
92156 Suresnes FRANCE
tel: +33(0)147283740
fax: +33(0)147283725
philippe.gentric@philips.com
http://www.mpeg-4.philips.com





"Lim, Young-Kwon" <young@techway.co.kr> on 21-08-2001 16:23:08

Please respond to "Lim, Young-Kwon" <young@techway.co.kr>

To:     Philippe Gentric/LIM/CE/PHILIPS@EMEA1
cc:     <4on2andIP-sys@advent.ee.columbia.edu>
Subject:  Question about "PayloadSize" field
Classification:


Dear Phillipe and all,

In the latest draft, "PayloadSize" field is defined to contain the entire size of AU in single SL case. But the parameter "SizeLength" will set to zero in default and it indicates the single SL case. This means that the length of "PayloadSize" field will
be zero in single SL case and conflict with the definition of "PayoadSize" field. Did I missed something in between?

Sincerely,
Young.











_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
http://www1.ietf.org/mailman/listinfo/avt