1. doc.: IEEE 802.11-12/0104r1 SubmissionLiwen Chu Etc.Slide 1 Fragmentation with A-MPDU Date: 2012-01-16 Authors: Date: Jan, 2012

2. doc.: IEEE 802.11-12/0104r1 Submission Fragmentation in the 802.11 Baseline Specification Fragmentation creates MPDUs smaller than the original MSDU or MMPDU length to increase reliability, by increasing the probability of successful transmission of the MSDU or MMPDU in cases where channel characteristics limit reception reliability for longer frames. An MSDU transmitted under an HT-immediate or HT-delayed Block Ack agreement shall not be fragmented even if its length exceeds dot11FragmentationThreshold. An MSDU transmitted within an A-MPDU shall not be fragmented even if its length exceeds dot11FragmentationThreshold. Group addressed MSDUs or MMPDUs shall not be fragmented even if their length exceeds dot11FragmentationThreshold. Slide 2 Date: Jan, 2012

3. doc.: IEEE 802.11-12/0104r1 Submission Why Narrower Channel needs Fragmentation with A- MPDU Sub1GHz 802.11ah has comparably narrow operating channels (1Mhz, 2MHz, 4MHz, 8MHz, 16MHz) than legacy bands. 802.11af will also have narrow channels (e.g. 6MHz). Fragmentation without A-MPDU increases the reliability: –When collision occurs, the unsuccessful transmission is shorter. –The CRC can provide higher protection to the shorter frame. Fragmentation without A-MPDU creates more overhead. –Each fragmentation needs an acknowledge frame. –More IFSs and PHY headers are required for a MSDU/MMPDU. Fragment2 SIFS PHY HeaderMPDU MSDU Fragment1Fragment2Fragment3Fragment4Fragment0 PHY HeaderACK Fragment1Fragment0Fragment3Fragment4 Slide 3 Date: Jan, 2012

4. doc.: IEEE 802.11-12/0104r1 Submission Why Narrower Channel needs Fragmentation with A-MPDU (Contd) Fragmentation with A-MPDU increases the reliability without increasing overhead. –When a collision occurs, the unsuccessful transmission is shorter. Each A-MPDU subframe is identified by an MPDU Delimiter. –The CRC can provide higher protection to the shorter frame. –Aggregated fragments plus a BlockAck decrease the IFS and PHY overhead. SIFS PHY HeaderA-MPDU Subframe MSDU Fragment1Fragment2Fragment3Fragment4Fragment0 BlockAck MPDU 4 bytes MPDU Delimiter Pad (0 - 3bytes) A-MPDU Subframe Fragment0Fragment1Fragment2Fragment3Fragment4 Slide 4 Date: Jan, 2012

5. doc.: IEEE 802.11-12/0104r1 Submission Solution: Allow Fragmentation with A-MPDU In a narrow-channel band (e.g. Sub 1GHz TGah), a STA or an AP can combine Fragmentation with A-MPDU: –An MSDU transmitted within an A-MPDU may be fragmented if its length exceeds dot11FragmentationThreshold. SIFS PHY HeaderA-MPDU Subframe MSDU Fragment1Fragment2Fragment3Fragment4Fragment0 BlockAck MPDU 4 bytes MPDU Delimiter Pad (0 - 3bytes) A-MPDU Subframe Fragment0Fragment1Fragment2Fragment3Fragment4 Slide 5 Date: Jan, 2012

6. doc.: IEEE 802.11-12/0104r1 Submission Issue and Solution with Fragmentation BlockAck Issue with fragmentation blockAck: –The BA Information field is a long field 128 +2 = 130 bytes. This may not be good to low PHY rate. Solution: –Compress the fragmentation BA Information field to shorter length (e.g. 10 Octets, 4 MSDUs can be acknowledged by this shorter fragmentation BA Information field ). –A reserved bit in BA Control field can used as shorter fragmentation BA Information indication. Or A compressed basic blockAck Req can be defined for the shorter fragmentation BA. Block Ack Starting Sequence ControlBlock Ack Bitmap 28Octets Slide 6 Date: Jan, 2012

7. doc.: IEEE 802.11-12/0104r1 Submission Straw Poll Do you support fragmentation with A-MPDU defined in slide 5 and slide 6? –Y –N –A Slide 7 Date: Jan, 2012