1 Multicast A-A-MAP Symbols Mapping Scheme in m systems ( ) Document Number: C80216m_10/0218 Date Submitted: Source: Yu-Hao Chang, Yih-Shen Chen, Pei-Kai Chih-Yuan Lin, Paul Cheng MediaTek Venue: IEEE Session #66, Orlando, USA. Re: Base Contribution: N/A Purpose: To be discussed and adopted by TGm Notice: This document does not represent the agreed views of the IEEE 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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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 Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Further information is located at and.

2 Background and Motivation (1/2) Different A-A-MAP-IEs encoded by the same modulation and coding scheme are grouped together and form an A-A-MAP group AMS can perform blind decoding in the resource unit (RU) region reserved for the corresponding group to find its A-A-MAP-IE The group size information is broadcasted so that the search space of blind decoding is reduced Multicast A-A-MAP-IE, e.g., group resource allocation (GRA) and composite persistent allocation (composite PA), may occupy more resource than the individual A-A-MAP-IE in the same group The size of multicast A-A-MAP-IE is not fixed, but depends on the information carried

3 Background and Motivation (2/2) Since AMS does not know the exact number of MLRUs used in its multicast-A-AMAP-IE, it needs to check all possible MLRU sizes with different shifts to find its A-A-MAP-IE This operation demands huge computational complexity for blind decoding, especially when more than one multicast A-A-MAP-IE are there in the same group The location and size information of multicast A-A-MAP-IE should be effectively delivered to AMS to save the blind decoding complexity

4 Summary of the proposed scheme The multicast A-A-MAP-IE is divided into two segments, namely, segment 1 and segment 2 multicast A-A-MAP-IEs. Both of them are individually encoded and mapped onto contiguous MLRUs The size of segment 2 is flexible and depends on the information carried while that of segment 1 is fixed and is known to AMS Segment 2 symbol size in terms of MLRUs is also indicated in the corresponding segment 1 symbol so that there is no size ambiguity for segment 2 decoding after AMS decodes segment 1 symbol successfully Note that, the partition between segment-1 and segment-2 is logically –if the required bit number can be filled into a single basic unit A-MAP- IE, e.g., DL/UL basic A-A-MAP-IE, segment 1 and segment 2 can be composed into a single GRA-A-MAP IE –Otherwise, segment-1 and segment-2 are sent in separate but contiguous MLRUs

5 The proposed multicast A-A-MAP-IE mapping scheme Separate the multicast A-A-MAP-IE into two segments, i.e., –multicast A-A-MAP-IE segment 1 (fixed size) –multicast A-A-MAP-IE segment 2 (variable size) Multicast A-A-MAP-IE segment 1 and 2 are called segment 1 and 2, respectively, in the following slides Additional one-bit type field IE is inserted in segment 1 and segment 2 to differentiate these two segments The size of segment 2 symbol in terms of MLRUs is indicated in segment 1 The size of information bits in segment 1 is upper bounded by a fixed number so that the data size after channel encoder is known –For example, the number of information bits in segment 1 is bounded by 40 bits. This corresponds to one MLRU when 16-bit CRC and QPSK ½ are applied MCRC is independently generated and inserted in both segment 1 and segment 2 Both segment 1 and segment 2 are separately encoded by the same MCS after MCRC insertion After channel coding, segment 1 and segment 2 symbols are mapped onto contiguous MLRUs while segment 1 symbol occupies a lower MLRU index than segment 2

6 Decoding of the proposed multicast A-A-MAP mapping Since the size of segment 1 symbol is fixed and known to AMS, AMS can first perform blind decoding for the segment 1 symbol without size ambiguity After decoding segment symbol 1 successfully, AMS learns how many MLRUs right after segment 1 symbol are reserved for segment 2 symbol. Therefore, it can decode the segment 2 symbol immediately without further searching process

7 Information Element in segment 1 segment 1 can contain the following IEs –A-MAP IE type –Type field –segment 2 size –User bit map size –User bit map –Re-arrange Indicator –[Segment 2 indicator] –Optional fields: Long TTI Length Resource offset ACK Channel Offset N_deallocated_AMS De-allocated AMS index Re-arrange Bitmap if Re-arrange Indicator == 1 MIMO Bitmap if Group MIMO mode set == 0b01 or 0b11 PSI Bitmap if Group MIMO mode set == 0b11 Pairing Bitmap if Group MIMO mode set == 0b11 Resource assignment bitmap Padding The idea of having user bit map in segment 1 is to save the computational power of inactive AMS for segment 2 symbol decoding in the corresponding multicast A- A-MAP-IE Note that, the optional fields exists when segment-1 and segment-2 information are composed into a single A-A-MAP IE

8 Information Element in segment 2 Segment 2 can contain the following IEs –A-MAP IE type –Type field –Long TTI Length –Resource offset –ACK Channel Offset –N_deallocated_AMS De-allocated AMS index –Re-arrange Bitmap if Re-arrange Indicator == 1 –MIMO Bitmap if Group MIMO mode set == 0b01 or 0b11 –PSI Bitmap if Group MIMO mode set == 0b11 –Pairing Bitmap if Group MIMO mode set == 0b11 –Resource assignment bitmap –Padding

9 Example of multicast A-A-MAP decoding based on the proposed scheme AMS searches for the segment 1 of its multicast A-A-MAP-IE first –There is no MLRU size ambiguity in segment 1 decoding –Only location of segment 1 symbol is unknown Segment 1 symbol carries information necessary for segment 2 decoding. For example, –MLRUs reserved for the corresponding segment 2 symbol Location of segment 2 is now known to AMS after segment 1 decoding

10 Example of Proposed GRA A-MAP IE SyntaxSize Description A-MAP IE Type4 Group Resource Allocation A- MAP IE Format type1 0: Fixed part (segment-1) 1: extension part (segment-2) If(Format type == 0) { GRA control information // information given in page 6 } else { GRA allocation information // information given in page 7 }

11 Text Proposal (1/2)

12 Text Proposal (2/2)