1. Bandwidth Request Channel Physical Layer Design IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE S802.16m-09/0222 Date Submitted: 2009-1-7 Source: Zheng Yan-Xiu, Yu-Chuan Fang, Chang-Lan Tsai, Chung-Lien Ho, Hsi-Min Hsiao, Ren-Jr Chen, Richard Li, E-mail: zhengyanxiu@itri.org.tw.zhengyanxiu@itri.org.tw ITRI Venue: IEEE Session #59, San Diego. Base Contribution: N/A Re: IEEE 802.16m-08/053r1, “Call for Comments and Contributions on Project 802.16m Amendment Working Document”. Target topic: “11.9.2.5.2 PHY Structure”. Purpose: To be discussed and approval by IEEE 802.16m TG Notice: This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2. Motivation Three step bandwidth request channel includes two parts –Preamble: user identification –Data: information for requested bandwidth and user identification Non-coherent detection is preferred for preamble part. As the preamble is detected, channel estimation is performed as referent phase for coherent detection on data part However, two users collide if two users apply identical preamble and the number of preamble sequences determines the collision probability.

3. Proposed Sequence Design for Bandwidth Request Channel Three distributed 6x6 tiles Non-coherent detection for preamble Interleaved structure for better channel estimation to data part Design 32 preambles comparing to ZC code with 19 sequences Code rate (5,19)

4. Sequences for Bandwidth Request Channel #sequence 10 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 20 0 0 0 0 1 1 0 0 1 0 1 0 0 0 1 1 0 0 30 0 0 0 1 0 1 0 1 1 0 0 0 0 1 0 0 0 0 40 0 0 0 1 1 1 0 1 0 1 0 0 1 1 0 0 1 1 50 0 0 1 0 0 1 1 0 0 0 0 1 0 0 1 1 0 0 60 0 0 1 0 1 1 0 1 0 1 1 1 0 0 0 0 1 1 70 0 0 1 1 0 1 0 0 1 0 1 1 1 0 0 0 1 1 80 0 0 1 1 1 1 0 0 0 1 0 1 1 0 0 0 1 0 90 0 1 0 0 0 1 0 1 0 0 1 1 1 1 0 1 1 1 100 0 1 0 0 1 1 0 0 1 0 0 1 1 1 0 0 0 0 110 0 1 0 1 0 1 0 0 0 0 0 0 0 1 0 1 1 1 120 0 1 0 1 1 1 0 1 0 0 0 1 1 1 1 1 0 0 130 0 1 1 0 0 1 0 0 1 0 0 0 1 0 0 0 1 1 140 0 1 1 0 1 0 1 1 1 1 1 1 0 0 1 1 0 0 150 0 1 1 1 0 0 1 1 0 0 1 1 0 1 1 0 1 1 160 0 1 1 1 1 0 1 0 1 0 0 1 1 0 0 0 1 1 #sequence 170 1 0 0 0 0 0 1 1 1 0 1 1 1 0 1 1 0 0 180 1 0 0 0 1 0 1 1 0 0 0 1 1 1 0 1 1 1 190 1 0 0 1 0 0 1 0 0 0 0 0 0 0 1 0 1 1 200 1 0 0 1 1 0 1 1 1 1 0 1 0 0 0 1 1 1 210 1 0 1 0 0 0 1 1 0 0 0 0 1 0 1 1 1 1 220 1 0 1 1 0 0 0 0 1 0 0 1 1 1 1 1 0 0 230 1 0 1 1 1 0 0 1 1 1 1 0 1 0 1 1 1 1 240 1 1 0 0 0 0 0 1 1 0 1 1 0 1 0 0 0 0 250 1 1 0 0 1 0 0 0 1 0 0 0 1 1 0 1 1 1 260 1 1 0 0 1 1 1 1 1 1 1 0 0 0 1 0 1 0 270 1 1 0 1 1 0 0 1 0 0 0 1 0 0 0 0 1 1 280 1 1 1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 0 290 1 1 1 0 0 1 1 1 1 1 0 0 1 0 1 0 1 1 300 1 1 1 0 1 1 1 1 0 0 1 0 1 1 0 0 1 1 310 1 1 1 1 0 1 1 0 1 0 0 0 1 0 1 1 1 1 32320 1 1 1 1 1 1 1 1 0 0 1 0 1 0 0 0 1 0

5. Recommended Separate Decoding for High Mobility When mobility is high, channel varies significantly on time domain Time-varying channel deteriorates detection performance of codes Separate detecting sequences on time domain improves the detection performance Partition received samples into multiple parts on time domain and each part are separately matched and summed

6. Performance comparison for bandwidth request channel Intel’s proposal applies ZC code with19 sequences Our design provides 32 sequences with only at most 1dB performance degradation for the (5,19) code for low and medium mobility Extra codes provide more successful transmission opportunities For high mobility, separate detection provides extra detection performance gain Channel Bandwidth10MHz Over-sampling Factor28/25 FFT Size1024 Cyclic prefix (CP) ratio1/8 Channel conditionPB3, VA120, VA350 The number of antennasTx:1, Rx:2 ModulationBPSK FMT size6x2 Block size6x6 ReceiverPreamble: non-coherent detection, MLD

7. Conclusion Bandwidth request channels are carried in UL Control DRU Bandwidth request coding block size: three distributed 6x6 resource tiles (108 tones total) with diversity order = 3 for frequency diversity Bandwidth Request Preamble: 32 sequences on 19 subcarriers Text proposal is in C802.16m-09/0225