HARQ and ARQ Interactions Document Number: IEEE C802.16m-08/1068r1 Date Submitted: 2008-09-05 Source: Hua Xu Voice: +1-847-632-2176 Motorola Inc. E-mail: hua.xu@motorola.com Venue: MAC: HARQ; in response to the TGm Call for Contributions and Comments 802.16m-08/003r4 for Session 57 Base Contribution: Purpose: For review and adapt. 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 >.

Current ARQ Functionalities and Issues ARQ is redundant to HARQ except retransmission after HARQ tries. Currently, HARQ and ARQ are loosely coexists without much of coordination, which makes ARQ inefficient. HARQ re-ordering (PDU SN) is per basic, primary, secondary CIDs not per flow. It is impossible to manage the reordering process based on the specific requirements of each individual flow. HARQ State Transfer

Propose Text to SDD 10.2.3 HARQ and ARQ Interaction The entire transmission and retransmission process is handled by HARQ without ARQ to avoid complicated ACK/NACK communication between the two. The flexibility of being able to start a second HARQ series after the first HARQ series, such as “4-HARQ” tries, failed will be supported by HARQ. The second HARQ series can choose different MCS and segmentation. Guideline of QoS support for each MAC PDU is communicated with the HARQ. This guideline can be in the form of number of HARQ tries per series and maximum number of HARQ series. The HARQ state transfer will be supported during the HO.