1. Support of Dynamic Load-balancing between 16m and 16e in Uplink System - (16.3.8.3.5.3) IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16m-09/2845r1 Date Submitted: 2010-01-12 Source: Jeongho Park, Jaeweon Cho, Hokyu Choi Voice:+82-31-279-7528 Samsung Electronics Co., Ltd. E-mail:jeongho.jh.park@samsung.com Mark Cudak Motorola E-mail:mark.cudak@motorola.com Venue: IEEE 802.16-09/0073, “IEEE 802.16 Working Group Letter Ballot Recirc #30b: Announcement” Base Contribution: None Purpose: To be discussed and adopted by TGm 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. Support of Dynamic Load-balancing between 16m and 16e - Uplink System - Jeongho Park, Jaeweon Cho, Hokyu Choi Samsung Electronics Co., Ltd. Mark Cudak Motorola January 2010

3. About This Contribution Goal and scope of this contribution - Provide a proposal for dynamic load balancing in uplink systems between 16e and 16m Full flexibility for load balancing WITHOUT any additional signaling Maximum commonality in protocol between mixed and 16m only mode Proposal in this contribution - The required operation for dynamic load balancing BS side : Need to separate resources for 16e and 16m in scheduler MS side : Nothing different from normal operation (MS transparent) - The required change in the 16m draft spec Remove a step of referring subchannel bitmap signaling Add a renumbering step into subchannelization of 16m PUSC zone support 2

4. Initial Entry in Mixed Mode In Addition to Following information, - RNG channel resource location for initial ranging(S-SFH SP1) - TX power for initial ranging (S-SFH SP1 & 2) - Uplink subchannelization for RNG-REQ MSG(S-SFH SP1 & 2) AMS in Mixed Mode Need to know - What PUSC subchannels are assigned to 16m Before uplink subchannelization This brings high signaling overhead or initial entry latency Proposal can remove this necessity while still providing dynamic load balancing - Also can maximize protocol commonality btw mixed & 16m only mode 3

5. Proposal Renumbering index in reverse order in 16m - Control channel signaling format/protocol in 16m only mode can be applied to mixed mode - Dynamic load balancing could be done without any reference of signaling Resource Usage - Use of continuous PUSC index within each 16e and 16m Since PUSC subchannel provides full frequency diversity, it is okay - Assign from lowest index to 16e while highest index to 16m BS scheduling can change load balancing with full dynamics 4

6. Comparison in Concept 16m only 5 Mixed in D3Mixed Proposed Data HFBCH BW REQ CH FFBCH Logical resource index From 16m AMS perspective Data RNG CQI/ ACK RNG Logical resource index From 16e MS perspective Logical resource index From 16m AMS perspective Signaling required RNG CQI/ ACK Logical resource index From 16e MS perspective Logical resource index From 16m AMS perspective HFBCH BW REQ CH FFBCH Signaling NOT required & BS can change breakpoint Dynamically by scheduling 16e 16m 16e 16m RNG Data BW REQ CH FFBCH HFBCH Data

7. Required Text Change in D3 (1/8) When supporting FDM based UL PUSC zone, UL subchannelization shall conform the following rules: 1) For the WirelessMAN-OFDMA system bandwidth, all usable subcarriers given in Table 878, Table 879, and Table 880 are divided into PUSC tiles. 2) UL PUSC subchannelization is performed as described in section >. 3) Available subchannels for Advanced Air Interface AMS shall be specified through subchannel bitmap broadcasted by [system descriptor, TBD]. 43) All PUSC tiles of specified subchannels from step 3 are extended in time domain from 3 OFDM symbols to Nsym OFDM symbols, where Nsym is dependent of AAI subframe type. 54) Based on specified subchannels of step 3 with symbol extension tiles of step 4, DRUs for Advanced Air Interface are made up. 65) Repeat step 4 and step 5 for remained OFDMA symbols of every uplink AAI subframe 6) Renumber the DLRU index in reverse order of PUSC subchannel index 6 Remedy 1: Change text from line 19 to 37 in page 510

8. Required Text Change in D3 (2/8) 7 Remedy 2: Change Figure 536 in page 510 as follows:

9. Required Text Change in D3 (3/8) 8 UCAS_SB05/4/3See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 5 bits For 10 MHz, 4 bits For 5 MHz, 3 bits UCAS_MB05/4/3See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 5 bits For 10 MHz, 4 bits For 5 MHz, 3 bits UCAS_i3/2/1See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 3 bits For 10 MHz, 2 bits For 5 MHz, 1 bits Remedy 3: Change text from line 51 to 64 in page 377

10. Required Text Change in D3 (4/8) 9 Remedy 4: Change text from line 13 to 23 in page 378 : If ( FDM-based UL PUSC zone support ) { Frame configuration index 6Indicates the WirelessMAN-OFDMA support in the UL with FDM mode, when the Frame Configuration Index in S-SFH SP21 is equal to - 5 or 7 or 9 for 5/10/20 MHz channel bandwidth according to Table 771 - 4or 6 or 8 for 8.75 MHz channel bandwidth according to Table 772 - 3 (with CP=1/8) for 7 MHz channel bandwidth according to Table 773 The mapping between value of this index and frame configuration is listed in Table Table 771, Table 772,and Table 773 WirelessMAN-OFDMA support1Indicates whether frame configuration supports WirelessMAN-OFDMA systems or not 0b0 : No support of WirelessMAN- OFDMA 0b1 : Support of WirelessMAN-OFDMA If (WirelessMAN-OFDMA support == 0b1){

11. Required Text Change in D3 (4/8) 10 Remedy 5: Change text from line 33 to 36 in page 378 Ranging channel location in the frequency domain 3Indicate the start distributed LRU index for ranging channel. } else { UL_Permbase7Indicate UL_Permbase used in WirelessMAN-OFDMA system } else if (WirelessMAN-OFDMA support == 0b0) {

12. Required Text Change in D3 (5/8) 11 Remedy 6: Change text from line 55 to 59 in page 378 Ranging channel formats for non-synchronized AMSs 1Indicates the ranging channel formats number of Table 883 } UCAS_SB05/4/3See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 5 bits For 10 MHz, 4 bits For 5 MHz, 3 bits UCAS_MB05/4/3See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 5 bits For 10 MHz, 4 bits For 5 MHz, 3 bits UCAS_i3/2/1See 16.3.8.3.1UL CRU/DRU allocation For 20 MHz, 3 bits For 10 MHz, 2 bits For 5 MHz, 1 bits }

13. Required Text Change in D3 (6/8) 12 Remedy 7: Change text from line 30 to 32 in page 379 Frame configuration index6The mapping between value of this index and frame configuration is listed in Table Table 771, Table 772,and Table 773

14. Required Text Change in D3 (7/8) applied. For the UL FDM mode, the default number of UL subchannels dedicated to WirelessMAN- OFDMA is X = max(8, ceil(35 x the number of DL AAI subframes dedicated to WirelessMAN-OFDMA / (total number of DL AAI subframes in a frame))), and the number of UL subchannels dedicated to Advanced Air Interface operations is Y = 35 - X. 13 Remedy 9: Change text from line 41 to 45 in page 312 group for operation of the Advanced Air Interface. The UL subchannels group for operation of the WirelessMAN-OFDMA shall be indicated by the UL allocated subchannels bitmap TLV or the UL AMC Allocated physical bands bitmap TLV, defined in Table TBD, in the UCD message. Remedy 10: Change text from line 34 to 37 in page 305

15. Required Text Change in D3 (8/8) 14 channels, UL fast feedback channels, UL bandwidth request channels, and UL data channels as Figure 542 534. If frame configuration supports FDM-based uplink PUSC-zone support, ranging channel is located in the lowest DLRU index which is followed by UL HARQ feedback channels, UL fast feedback channels, UL bandwidth request channels, and UL data channels as Figure XXX. Remedy 11: Change text from line 39 to 40 in page 506 Remedy 12: Insert the following Figure XXX in line 41, page 510 as follows: