1. (Marvell Semiconductor, Inc.)
July 2001
doc.: IEEE /399r0
July 2001
Some Thoughts on IEEE g
Weishi Feng
(Marvell Semiconductor, Inc.)
Weishi Feng, Marvell Semiconductor Inc.
Wei Lih Lim, Matsushita Electric Ind.

2. July 2001
doc.: IEEE /399r0
July 2001
Where are we going?
It seems to me that none of the existing proposals (CCK-OFDM/PBCC/MBCK/DQPSK) will be able to get 75% of the votes.
Weishi Feng, Marvell Semiconductor Inc.
Wei Lih Lim, Matsushita Electric Ind.

3. Another possibility DQPSK + Reed-Solomon code
July 2001
Another possibility
DQPSK + Reed-Solomon code
The PHY insert 2 redundancy bytes for every 20B
Provides 20 Mbps data rate and much higher reliability than that of the DQPSK proposal.
Decoding is extremely simple.
No IP issues.
If the PHY buffers 20 bytes and transfer the data to MAC after correction, this RS decoding add only 4 us delay if the data transfer rate between PHY and MAC is 44Mbps.
Weishi Feng, Marvell Semiconductor Inc.

4. July 2001
doc.: IEEE /399r0
July 2001
As an example
22 bytes
Another 22 bytes
20 bytes to
MAC
8 us at 22Mbps
Less than 4 us
at 44 Mbps
Other options: if the data can be transferred to the MAC at 88Mbps, stronger code can be used. For example, add 4 redundancy bytes for every 40 bytes.
Then we will talk about Delay-Ack with duplication history in order to recover the loss of previous delay-ack information due to error
Then follow by improvement of TXOP
Weishi Feng, Marvell Semiconductor Inc.
Wei Lih Lim, Matsushita Electric Ind.