Transcript Slides S802.16m-10/0256

Proposed Text for FDM-based UL PUSC Zone Support (16.3.8)
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE C80216m-10_0256
Date Submitted:
2010-03-05
Source:
Jinsoo Choi, Jinyoung Chun, HanGyu Cho, Jin Sam Kwak
{js.choi, jiny.chun, hg.cho, jinsam.kwak}@lge.com
LG Electronics
Re:
Comments on P802.16m/D4 for LB #31
Purpose: To be discussed and adopted into P802.16m/D5
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:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >.
1
Subchannel rotation (SR) issue in FDM-based UL PUSC support
 Without subchannel rotation (SR) – turn off SR
 No impact on both 16e MS and AMS in current structure
 With subchannel rotation (SR) – turn on SR
 A problem in the current UL PUSC zone structure
 16e MS should know the available subchannels for SR by subchannel bitmap in
UCD.
 Because the period of UCD is not small, it is difficult to support dynamic load
balancing.
 Consideration points
 Because AAI system is designed based on subframe structure (pilot pattern, UL
control structure, etc), slot based SR must affect on the performance of AAI
system. Then AMS must not be affected by SR in mixed mode.
 For dynamic load balancing, could we support subframe-level load balancing or
frame-level load balancing?
- Subframe-level load balancing: With current structure, it seems difficult in fact.
- Frame-level load balancing: ABS can utilize some control channel such as MAP to
WirelessMAN-OFDMA system, which have a possibility to support frame-level load
balancing.
 Can AMS be transparent with SR while supporting dynamic load balancing? If
there is some region which is not applied by SR, resources for AMS could be
allocated to that kind of region.
One solution to resolve issues
 Current SR rule in 8.4.6.2.6 is depending on Nsubch value, which is defined
as the number of total subchannels except subchannels defined by some
UIUC cases (details are described in next slides). Then, if ABS set 16m
region into those kind of exceptional subchannels, AMS is transparent
with SR and frame-level load balancing can be supported.
 For example, when ABS transmit MAP with UIUC=13 for safety zone, then
16e MS can apply SR with total subchannel size except subchannels for
safety zone. AMS doesn’t have to know the region information, so there is
no required signaling for AAI operation.
Ref. Subchannel rotation scheme in 16e
Non-SR regions in 16e (cont’d)
 Subchannel rotation is applied except UIUC=0, 11 with 0x8, 12 and 13.
•
•
•
•
UIUC=0: Fast-feedback Allocation IE
UIUC=11 with 0x8: HARQ ACKCH Region Allocation IE
UIUC=12: CDMA BR, Ranging channel allocation
UIUC=13: PAPR reduction allocation, safety zone and sounding zone
 Can we use the channels for the allocation of 16m zone in PUSC FDM
zone?
• UIUC=0,11 with 0x8: At most one region per frame may be defined for TDD
mode. And the indices are allocated by frequency-first. So we can’t use it for 16m
zone.
• UIUC=12: YMS can transmit ranging code in any Ranging channels. So we can’t
restrict that for 16m zone.
• UIUC=13: If it is used for PAPR reduction, YMS can transmit garbage subcarriers
to reduce PAPR of their transmissions. But if it is used for safety zone, it’s empty
region. So 16m zone could be contained in UIUC=13 for PAPR reduction
allocation.
5
Ref. Non-SR regions in 16e
 UIUC=13 (PAPR reduction/Safety zone
/Sounding region)
6
Conclusion
 When subchannel rotation defined in 8.4.6.2.6 is applied to WirelessMANOFDMA system, it is difficult to support dynamic load balancing in fact.
 To support frame-level load balancing at least, ABS can transmit MAP to 16e MS
with UIUC=13 which is set to safety zone, so 16e MS know available subchannels
for SR except those subchannels.
 In order for AMS to be transparent with subchannel rotation, DRUs for Advanced
Air Interface system shall be allocated within these exceptional subchannels and
these subchannels shall not be allocated for the WirelessMAN-OFDMA system.
 If the dynamic load balancing could not be supported, it would not be good to
maintain current UL PUSC zone structure because there exists still ambiguity in
operation without clear separation between 16e and 16m. (e.g., in the case of
dynamic ranging allocation). In addition, we don’t have to maintain unnecessary
operation like reverse ordering.
 Thus we should resolve load balancing issue or make the UL PUSC structure clear
with separation between 16e and 16m region.