Presentation is loading. Please wait.

Presentation is loading. Please wait.

Structure of the “Resource Allocation” field in the A-AMAP IEs – Proposal Summary Document Number: IEEE C80216m-09_1328 Date Submitted: 2009-07-06 Source:

Similar presentations


Presentation on theme: "Structure of the “Resource Allocation” field in the A-AMAP IEs – Proposal Summary Document Number: IEEE C80216m-09_1328 Date Submitted: 2009-07-06 Source:"— Presentation transcript:

1 Structure of the “Resource Allocation” field in the A-AMAP IEs – Proposal Summary Document Number: IEEE C80216m-09_1328 Date Submitted: 2009-07-06 Source: Sudhir Ramakrishna, E-mail:sudhir.r@samsung.com@samsung.com Youngbo Cho, Hyunkyu Yu, Jeongho Park, Heewon Kang, Zhouyue Pi Venue: Re: 802.16m amendment working document Category: AWD Comments Area: Chapter 15.3.6 (DL Control) Base Contribution: IEEE C80216m-09_1328 Purpose: To be discussed and adopted by TGm for the 802.16m AWD 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 IEEE_C80216m-09_1328 Slide #2 Associated AWD Text Proposal Contribution C80216m-09_1331 provides the AWD text defining the structure & interpretation of the “Resource Allocation” field, and the interpretation of the associated IEs, for the 5, 10 and 20 MHz cases This contribution provides a high-level summary of the detailed RA field text in Contribution C80216m- 09_13331, and provides some motivation, background & pointers to some supporting simulation results for the RA field design. Summary of this contribution

3 IEEE_C80216m-09_1328 Slide #3 DRU/Mini-Band CRUs : RA Field Design Goals Should be possible to indicate a 1 LRU assignment No un-assigned LRUs due to assignment indication limitations For VoIP support, need to indicate assignment of 1/2/3/4 & 6 LRUs RA field as small as possible, to keep signaling efficient DRU/Mini-Band CRUs : RA Field Design Summary Use “channel tree” approach  Nodes at bottom level of tree represent LRUs  Each node in tree, indexed by RA, indicates assignment of all nodes at bottom level branching from it Select channel tree such that  1 LRU granularity at lower assignment sizes  to support VoIP  Lower granularity at larger assignment sizes o Leads to reduction in number of nodes in tree  reduction in size of RA field o Granularity less important at larger assignment sizes, will not affect performance in “full buffer” type traffic o In RL, large assignments unlikely due to transmit power limitations

4 IEEE_C80216m-09_1328 Slide #4 Sub-band CRUs : RA Field Design Goals From DL system-level simulation results in [2]  Allocation of smaller (<= 3) number of sub-bands is an important (dominant) use-case o For this use case, using a common MCS for all assigned sub-bands leads to very small performance difference  Ability to indicate non-contiguous sub-band allocations important o Can lead to performance gains (with PF scheduler) over purely contiguous allocations Sub-band CRUs : RA Field Design Summary For allocation of sub-bands with contiguous indices, leverage channel tree indication method In all cases, all possible allocations of sub-bands with contiguous indices can be indicated RA field indexing designed so that Using 1 IE, can indicate most combinations of non-contiguous assignments of small (<= 3) number of sub-bands For allocation of larger # of non-contiguous sub-bands, use 2 IEs, and indicate using concatenated RA fields Do not need more than 2 IEs

5 IEEE_C80216m-09_1328 Slide #5 RA Field Structure For each of the BW cases (5 MHz, 10 MHz & 20 MHz) Use x + 1 bits for the RA Field  x bits for RA itself (x depends on bandwidth and # of LRU combinations to be indicated)  1 distinguisher bit, called RA_Specifier, to distinguish between contiguous and non-contiguous LRU allocations o Non-contiguous indicator used in sub-band allocations

6 SS_RAField_IEEE_C80216m-09_1328 Slide #6 RA Field - Design Summary for 5/10/20 MHz 5 MHz10 MHz20 MHz # of LRUs244896 # of sub-bands61224 # of all possible contiguous LRU allocations 30011764656 # of resource indication bits7 Resource Allocation (RA) bits + 1 specifier bit = 8 bits total 8 RA + 1 specifier10 RA + 1 specifier # of possible contiguous LRU allocations indicable 117/300252/1176981/4656 Highest difference between consecutive contiguous LRU sizes 444 Non-contiguous sub-band allocations using 1 IE All combinationsAll combinations of 2 SBs, almost all (210/220) combinations of 3 SBs All combinations of 2 SBs, some combinations of 3 SBs Max. # of IEs needed for all possible non-contiguous sub- band indication 122

7 SS_RAField_IEEE_C80216m-09_1328 Slide #7 5 MHz

8 SS_RAField_IEEE_C80216m-09_1328 Slide #8 5 MHz - Summary 24 LRUs, 6 sub-bands RA Field = 8 bits Use 7-bits RA + 1 bit RA_Specifier RA_Specifier used to distinguish sub-band-CRU allocations vs DRU/miniband CRU allocations Design summary Full flexibility for sub-band allocation with 1 sub-band granularity For contiguous (DRU/mini-band CRU) allocations – can indicate 117 of the 300 possible combinations Never need more than 1 AAMAP IE for any allocation

9 SS_RAField_IEEE_C80216m-09_1328 Slide #9 5 MHz – Channel tree for contiguous allocations 117 nodes in tree, indexed by 7-bit RA Each node allocates all the nodes at bottom level (Level 10) that it is connected to. Allows indication of 117 of the 300 possible combinations of contiguous LRU indices (24 LRUs = 300 contiguous combinations)

10 SS_RAField_IEEE_C80216m-09_1328 Slide #10 5 MHz DL Flow – 7 bit RA + 1 bit Specifier

11 SS_RAField_IEEE_C80216m-09_1328 Slide #11 5 MHz – Indexing Tables Table_RA_1 : This table maps value of 7-bit RA to a node in the channel tree, and then to a set of contiguous LRU indices.

12 SS_RAField_IEEE_C80216m-09_1328 Slide #12 10 MHz

13 SS_RAField_IEEE_C80216m-09_1328 Slide #13 10 MHz - Summary 48 LRUs, 12 sub-bands RA Field = 9 bits 8-bit RA + 1 bit RA_Specifier Design summary Contiguous allocations – use a channel tree, allowing indication of 252 of the 1176 possible LRU allocations Non-contiguous sub-band allocations With 1 IE, can indicate all 2 and almost all (210/220) 3 non-contiguous sub-band allocations With 2 IEs, concatenate 8 bit RA in each IE, interpret resultant as a 12 bit bitmap to allow arbitrary allocations of the 12 sub-bands Never use more than 2 IEs

14 SS_RAField_IEEE_C80216m-09_1328 Slide #14 10 MHz – Channel tree for contiguous allocations 252 nodes in tree, indexed by 8-bit RA

15 SS_RAField_IEEE_C80216m-09_1328 Slide #15 10 MHz DL Flow – 8 bit RA + 1 bit Specifier

16 SS_RAField_IEEE_C80216m-09_1328 Slide #16 10 MHz – Indexing Tables Table_RA_2 : This table maps value of 8-bit RA to a node in the channel tree, and then to a set of contiguous LRU indices. Table_RA_3 & Table_RA_4: Map 8-bit RA to indices of 2 & 3 non-contiguous sub-bands These tables are specified in the text proposal.

17 SS_RAField_IEEE_C80216m-09_1328 Slide #17 20 MHz

18 SS_RAField_IEEE_C80216m-09_1328 Slide #18 20 MHz - Summary 96 LRUs, 24 sub-bands RA field = 11 bits 10-bit RA + 1 bit RA_Specifier Design summary Contiguous allocations – use a channel tree, allowing indication of 981 of the 4656 possible LRU allocations Non-contiguous sub-band allocations Design very similar to the 10 MHz case With 1 IE, can indicate all 2 non-contiguous sub-band allocations, and some of the 3 sub-band possibilities With 2 IEs, concatenate 10 bit RA, interpret resultant as a 20 bit bitmap to allow arbitrary allocations of up-to 20 sub-bands For allocations larger than 20 sub-bands, use contiguous sub-band indices Never use more than 2 IEs

19 SS_RAField_IEEE_C80216m-09_1328 Slide #19 20 MHz – Channel tree for contiguous allocations

20 SS_RAField_IEEE_C80216m-09_1328 Slide #20 20 MHz DL Flow – 10 bit RA + 1 bit Specifier

21 SS_RAField_IEEE_C80216m-09_1328 Slide #21 20 MHz – Indexing Tables Table_RA_5 : This table maps value of 10-bit RA to a node in the channel tree, and then to a set of contiguous LRU indices. Table_RA_6 & Table_RA_7 : Maps 10-bit RA to indices of 2 or 3 non-contiguous sub-bands  These tables are specified in the text proposal

22 SS_RAField_IEEE_C80216m-09_1328 Slide #22 References [1] C80216m-09_0918r2, “Proposed AWD text specifying the “Resource Allocation” field in the Basic Assignment A-MAP IEs”, presented in IEEE 802.16m Session 61 (in Cairo). [2] C80216m-09_0917r2, “Design of the “Resource Allocation” field in the Basic Assignment A- MAP IE: Simulation results, Insights & Methodology”, presented in IEEE 802.16m Session 61 (Cairo).


Download ppt "Structure of the “Resource Allocation” field in the A-AMAP IEs – Proposal Summary Document Number: IEEE C80216m-09_1328 Date Submitted: 2009-07-06 Source:"

Similar presentations


Ads by Google