120 likes | 142 Views
Efficient Error Control Using Network Coding for Multicast Transmission. Date: 2009-03-19. Authors:. Contents. Overview of Network Coding Issues for Network Coding Our Proposal System Block Diagram Example of Network Coding Error Control Frame Conclusion. Overview of Network Coding.
E N D
Efficient Error Control Using Network Coding for Multicast Transmission Date: 2009-03-19 Authors: J.-K. Kevin Rhee, et. al, KAIST
Contents • Overview of Network Coding • Issues for Network Coding • Our Proposal • System Block Diagram • Example of Network Coding Error Control Frame • Conclusion J.-K. Kevin Rhee, et. al, KAIST
Overview of Network Coding • Problems of existing error control scheme in 802.11 • Itinvolves error control frame storming. • Multicast Error Rate (# of Receiving station X Unicast error rate) • MER = 1, if # of Receiving station X Unicast error rate > 1 • MER = # of Receiving station X Unicast error rate • If MER = 1, it required more than 100% of overhead. • How network coding benefits to multicast error control Network coding requires 3 times less overhead comparing with the existing error control scheme. J.-K. Kevin Rhee, et. al, KAIST
Issues for Network Coding • Handling variable length of frames • The size of error control frames coined by XOR operations are same as the largest frames among a set. • The way notifying receiving nodes of actual payload size ofa missing frame is required. • XOR payload design concept • We should clarify which information should be XORed and which information should not. J.-K. Kevin Rhee, et. al, KAIST
OurProposal -50- • Handling variable length of frames • Padding a special ending bit sequence at the end of payload. • • Actual data payload is retrieved by matching ending bit sequence. Payload EoS Frame 1 Payload EoS Padding(0x0000….) Frame 2 Payload EoS Padding(0x0000….) Frame 3 = XORed Payload Error control frame J.-K. Kevin Rhee, et. al, KAIST
Our Proposal -60- • Handling variable length of frames • Retrieve XORed Payload Error control frame Payload EoS Frame 1 Payload EoS Padding(0x0000….) Frame 3 = Payload EoS Padding(0x0000….) Retrieved frame Payload of Frame 2 J.-K. Kevin Rhee, et. al, KAIST
Our Proposal -70- • Handling variable length of frames • Introducing a length field XORing. • • Actual data payload is retrieved by matching ending bit sequence. • • This scheme does not require Length Payload Frame 1 Length Payload Padding(0x0000….) Frame 2 Payload Length Padding(0x0000….) Frame 3 = XORed Length XORed Payload Error control frame J.-K. Kevin Rhee, et. al, KAIST
Our Proposal -80- • Handling variable length of frames • Retrieve XORed Payload XORed Length Error control frame Length Payload Frame 1 Padding(0x0000….) Length Payload Frame 3 = Length Payload Padding(0x0000….) Retrieved frame Payload of Frame 2 J.-K. Kevin Rhee, et. al, KAIST
System Block Diagram -90- • System Blocks J.-K. Kevin Rhee, et. al, KAIST
Example of Network Coding Error Control Frame -100- • Block ACK Network Coding Error Control Frame. • It takes Block ACK Control Path. • In BAR Control field, we define an additional type field distinguishing error control frames from others. • Start Seq and End Seq fields notify receiving stations of encoded frames. • Maximum size of XOR frame body is 2425 (2423 bytes-Data + 2 bytes-Length Filed or EoS) J.-K. Kevin Rhee, et. al, KAIST
Conclusion -110- • We propose two ways of supporting variable length of frames for network coding. • Introducing a Length Field • Padding EoS bit sequence at the end of payload. • Both scheme can allow receiving stations to retrieve actual data payload out of XORed payload. • We also proposed system block diagram for network coding multicast error control and example format of error control frame compliant with Block ACK. J.-K. Kevin Rhee, et. al, KAIST
Thank You! J.-K. Kevin Rhee, et. al, KAIST