UOD RAPTORQ FEC SCHEME draft-luby-uod-raptoq-00 IETF PRAGUE MARCH 27 – APRIL 1, 2011 Mike Luby & Thomas Stockhammer.

Slides:



Advertisements
Similar presentations
RTP Payload Format for Reed Solomon FEC of Multiple Flows
Advertisements

TOPIC : MIME (Multipurpose Internet Mail Extensions ) By: Cecilia Gomes COSC 541,DATA COMMUNICATION SYSTEMS & NETWORKS Instructor: Prof. Anvari (SEU)
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
Draft-roux-fecframe-repacketization-00..txt, CEA LIST, 77th IETF Meeting, March 23d Benefits of re-packetization for FEC based protection of multimedia.
n-bit comparator using 1-bit comparator
RTP Payload Format for Reed-Solomon FEC draft-galanos-fecframe-rtp-reedsolomon-00 Sarit Galanos, RADVISION IETF 76 – November 2009.
1 Wireless Sensor Networks Akyildiz/Vuran Administration Issues  Take home Mid-term Exam  Assign April 2, Due April 7  Individual work is required 
Draft-ospf-non-compatible Mike Dubrovsky. The draft addresses the following problem: Problem: How to introduce non-backward compatible functionality into.
IP: The Internet Protocol
Fountain Codes Amin Shokrollahi EPFL and Digital Fountain, Inc.
+======-========-========-========-========-========-========-========-========+ | Bit| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |Byte | | | | | | | | | |======+=======================================================================|
IPv4 over IP CS draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00 Soohong Daniel Park Syam Madanapalli 68 – Prague, Czech Republic March 18-23,
1 RTP Payload Format for DV Format Video draft-kobayashi-dv-video-00.txt Akimichi Ogawa Keio University.
1 Lot 3 - Développements MNGT to FAC-CM Interface Version 5 Baris DEMIRAY / Michelle WETTERWALD
INRIA Rhône-Alpes - Planète research group Reed-Solomon FEC I-D LDPC-* FEC I-D TESLA I-D Simple-auth I-D IETF 70 th – Vancouver meeting, November 2007.
MPEG-4 Design Team Report. 2 Proposals draft-ietf-avt-rtp-mpeg4-02.txt draft-guillemot-genrtp-01.txt draft-jnb-mpeg4av-rtp-00.txt FlexMux packetization.
Application of Finite Geometry LDPC code on the Internet Data Transport Wu Yuchun Oct 2006 Huawei Hisi Company Ltd.
1 RaptorG Forward Error Correction Scheme for Object Delivery draft-luby-rmt-bb-fec-raptorg-object-00 (update to this to be officially submitted soon)
Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.
EOVSA STATE FRAME ASSEMBLY, DISTRIBUTION, AND SYNCHRONIZATION Gelu Nita NJIT MARCH 2012 EOVSA PDR MEETING 1.
1 Raptor codes for reliable multicast object delivery Michael Luby Digital Fountain.
INRIA Rhône-Alpes - V. Roca - 1 FCAST: Scalable Object Delivery on top of the ALC Protocol IETF 68 th – Prague meeting, March 2007 Vincent Roca (INRIA)
1 VCID Notification over ATM Link N. SonyCSL K. Toshiba L. Ericsson Ennovate Networks H. Toshiba G.Swallow.
Forward Error Correction vs. Active Retransmit Requests in Wireless Networks Robbert Haarman.
RTP Payload Format for Reed-Solomon FEC draft-galanos-fecframe-rtp-reedsolomon-01 Sarit Galanos, RADVISION IETF 77 – March 2010 Orly.
Mapping IP Addresses to Hardware Addresses Chapter 5.
© NOKIAMSF Paris drieft-ietf-grmp-04.PPT / 28 March, 2000/ ADo page: 1 Review of draft-ietf-gsmp-04 Avri Doria, Nokia Fiffi Hellstrand, Nortel Networks.
Protocol Layering Chapter 11.
Simple Reed-Solomon FEC Scheme for FECFRAME draft-roca-fecframe-simple-rs-01 IETF 79 – Beijing, November 2010 V. Roca – M. Cunche (INRIA) J. Lacan – A.
1 Extend FEC BB to RTP streaming? Michael Luby Digital Fountain.
RTP Profile for RTCP-based Retransmission Request for Unicast session Koichi Yano (Canon) Matthew Podolsky, and Steven McCanne (U.C. Berkeley) (FastForward.
Slide title :32-35pt Color: R153 G0 B0 Corporate Font : FrutigerNext LT Medium Font to be used by customers and partners : Arial Slide text :20-22pt Bullets.
1-D Interleaved Parity FEC draft-begen-fecframe-interleaved-fec-scheme-00 IETF 72 – July 2008 Ali C. Begen
GOE FEC schemes GOE FEC schemes IETF83, March 26 th, 2012, Paris V. Roca, A. Roumy (Inria) B. Sayadi (ALU-BL)
Universal Object Delivery (UOD) & Generalized Object Encoding (GOE) IETF 83 MARCH 25 – 30, 2012 Paris, France Kevin Fall, Mike Luby & Thomas Stockhammer.
draft-jounay-pwe3-dynamic-pw-update-00.txt IETF 70 PWE3 Working Group
Advertising Generic Information in IS-IS
Flow control for EDMG devices
ICN Hop-By-Hop Fragmentation Update: Begin-End Fragmentation (BEF)
Transfer Frame Structures
… General Decoder for a Linear Block Code … …
IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.
M. Luby, Digital Fountain
Transport Layer.
MIMO Coding for SC PHY in 11ay
Flow control for EDMG devices
Net 323 D: Networks Protocols
Data Link Layer What does it do?
Ed Greenberg Greg Kazz 10/17/2012
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Discussion on Suitable Parameters for SCHC]
Extending TLVs Richard Maiden Intel May 2018.
FEC SIMULATION IN NS-2 Zhuo Bin Wu (z ).
Further considerations on WUR frame format
Greg Mirsky Jeff Tantsura Mach Chen Ilya Varlashkin
Net 323 D: Networks Protocols
IETF 100 draft-zheng-xrblock-effective-loss-index-02
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Discussion on Suitable Parameters for SCHC]
doc.: IEEE /457 Mathilde Benveniste AT&T Labs, Research
2/4/2019May 2008 November 2007 doc.: IEEE /2752r1
MIMO Coding for SC PHY in 11ay
William Stallings Data and Computer Communications
CS4470 Computer Networking Protocols
Air Efficiency and Reliability Enhancements for Multicast
doc.: IEEE <doc#>
Ch 17 - Binding Protocol Addresses
Sharp Laboratories USA
Oasis, Hursley, January Andrew Banks
Robert Moskowitz, Verizon
Chapter 3 - Binary Numbering System
draft-liu-pim-mofrr-tilfa-00
Presentation transcript:

UOD RAPTORQ FEC SCHEME draft-luby-uod-raptoq-00 IETF PRAGUE MARCH 27 – APRIL 1, 2011 Mike Luby & Thomas Stockhammer

UOD RaptorQ UOD = Universal Object Delivery Provides simpler file delivery than RaptorQ FEC Scheme No separate limitations on the number of source blocks and on the number of source symbols per source block Simple changes only FEC Payload ID format simplified The same FEC OTI per object – Extended for delivering multiple objects No changes to the RaptorQ FEC code Provides additional file delivery services in a simple way UEP file delivery Bundled file delivery

UOD RaptorQ – FEC Payload ID 0123456789 1 2 3 01 Universal Object Symbol Identifier (UOSI) (32 bits)

UOD RaptorQ shared parameters FEC Encoding ID – 7 (TBD) Number of objects (D) (8 bits) Symbol alignment parameter (Al) (8 bits) For I = 1,…,D, for object I: (10 octets per object) Encoding symbol size (T(I)) (16 bits) Transfer length (F(I)) (40 bits) Number of source blocks (Z(I)) (12 bits) Number of sub-blocks per source block (N(I)) (12 bits)

UOSI  (SBN, ESI) mapping From UOSI value C to (SBN,ESI) values (A,B) for an object with Z source blocks: B = floor(C/Z) A = C – B*Z From (SBN,ESI) values (A,B) for an object with Z source blocks to UOSI value C: C = A + B*Z

Sender parameter generation Applied to each of the D objects independently F(I) is the size of object I T(I) is the size of an encoding symbol for object I Kt(I) = F(I)/T(I) determines the priority of object I Kt(I) the number of source symbols for object I Practically, the number of any packets required to recover object I Applied exactly as described in the RaptorQ FEC Scheme

Sender encoding packet generation For each UOSI value C = 0, 1, 2, 3, ..., generate and send an encoding packet as follows: Set the value of the FEC Payload ID of the encoding packet to the UOSI value C. For I = 1,...,D, Determine the (SBN, ESI) values (A(I), B(I)) for object I that correspond to UOSI value C. Generate the encoding symbol E(I) of size T(I) that corresponds to (SBN, ESI) values (A(I), B(I)) from object I according to the procedures of the RaptorQ FEC Scheme. Add encoding symbol E(I) to the payload of the encoding packet. Send the encoding packet.

Receiver parameter usage Applied to each of the D objects independently F(I) is the size of object I T(I) is the size in each packet for encoding symbols of object I Exactly the same as described in the RaptorQ FEC Scheme

Receiver encoding packet processing When a packet is received with UOSI value C: For I = 1,...,D, Determine the (SBN, ESI) values (A(I), B(I)) for object I that correspond to UOSI value C. Extract the encoding symbol E(I) of size T(I) that corresponds to (SBN, ESI) values (A(I), B(I)) of object I Process the encoding symbol E(I) and the (SBN, ESI) values (A(I),B(I)) according to the procedures of the RaptorQ FEC Scheme applied to the parameters of object I.

UOD RaptorQ – UEP example File size = 1,024 KB – send 2,048 KB of encoded data First part is 32 KB in size – send 128 KB of encoded data Second part is 992 KB in size – send 1,920 KB of encoded data Each encoded packet has a payload of 1 KB for encoded symbols RaptorQ Send two parts separately UOD RaptorQ D = 2 F(1) = 32 KB, T(1) = 64 bytes F(2) = 992 KB, T(2) = 960 bytes Generate and send 2,048 packets 128 KB sent for first part 1,920 KB sent for the second part

UOD RaptorQ and Simple RaptorQ (first part) RaptorQ (first part) RaptorQ & UOD RaptorQ (second part)

UOD RaptorQ – Bundling example 32 files to be transmitted as a bundle Each file is of size 32 KB – send 64 KB of encoded data for each Each encoded packet has a payload of 1 KB for encoded symbols RaptorQ Send each file separately UOD RaptorQ D = 32 F(1) = F(2) = … = F(32) = 32 KB, T(1) = 64 bytes T(1) = T(2) = … = T(32) = 32 bytes Generate and send 2,048 packets

Comparisons RaptorQ All 32 files UOD RaptorQ All 32 files

Request Adopt draft-luby-uod-raptorq-00 as a RMT working group item?