Dynamic TDD HARQ Feedback Resource Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In dynamic Time Division Duplex (TDD) configurations, existing systems face challenges in efficiently mapping Physical Uplink Control Channel (PUCCH) resources for Hybrid Automatic Repeat Request (HARQ) acknowledgement (ACK)/non-acknowledgement (NACK) feedback, leading to conflicts between legacy and dynamic-TDD-enabled User Equipments (UEs) due to asymmetry between UpLink (UL) and DownLink (DL) subframes.
Innovation Solution
The method involves dividing DL subframes into subsets based on UL and DL reference TDD configurations, assigning distinct PUCCH resource indices for each subset, and using these indices for reporting HARQ ACK/NACK, while also utilizing Downlink Control Information (DCI) and Radio Resource Control (RRC) signaling to ensure proper resource allocation and conflict avoidance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dynamic TDD configurations are used to adapt to varying traffic conditions, then adaptability is improved, but resource conflicts occur between legacy and dynamic-TDD-enabled UEs due to asymmetry between UL and DL subframes
Solution Approach 1:
The patent segments the DL subframes into two distinct subsets: a first subset indicated by a UL reference TDD configuration and a second subset indicated by a DL reference TDD configuration. This segmentation allows different reference configurations to be applied to different subframe sets, resolving the conflict between legacy UEs (using UL reference) and dynamic-TDD-enabled UEs (using DL reference), while maintaining adaptability to varying traffic conditions.
2Productivity
If PUCCH resource indices are assigned based on asymmetric UL-DL subframe configurations, then resource utilization efficiency is improved, but conflicts arise in HARQ feedback transmission
Solution Approach 1:
The patent applies different PUCCH resource index assignment rules to different subsets of DL subframes. For the first subset (indicated by UL reference TDD configuration), PUCCH resources are assigned based on UL reference configuration. For the second subset (indicated by DL reference TDD configuration), PUCCH resources are assigned based on DL reference configuration. This local differentiation ensures efficient resource utilization for each subset while preventing conflicts in HARQ feedback transmission.
Data Source
AI summary
The present disclosure relates to a method used in a User Equipment (UE) for reporting Hybrid Automatic Repeat Request (HARQ) acknowledgement (ACK)/non-acknowledgement (NACK) for Physical Downlink Shared Channels (PDSCHs) in dynamic time division duplex (TDD) configurations. In the method, a plurality of PDSCHs are received in DownLink (DL) subframes associated with an UpLink (UL) subframe and indicated by a DL reference TDD configuration. The DL subframes are divided into a first subset of DL subframes and a second subset of DL subframes. The first subset of DL subframes is also indicated by an UL reference TDD configuration. A first set of Physical Uplink Control Channel (PUCCH) resource indices are assigned based on resources used in transmission of Physical Downlink Control Channels (PDCCHs) corresponding to the PDSCHs received in the DL subframes of the first subset of DL subframes. A second set of PUCCH resource indices are assigned based on resources used in transmission of PDCCHs corresponding to the PDSCHs received in the DL subframes of the second subset of DL subframes. For each of the received PDSCHs, HARQ ACK/NACK is reported by using PUCCH resources in an order of the assigned first set of PUCCH resource indices for PDSCHs received in the DL subframes of the first subset of DL subframes and in an order of the assigned second set of PUCCH resource indices for PDSCHs received in the DL subframes of the second subset of DL subframes. The present disclosure also relates to a UE and BS for respectively reporting and receiving HARQ ACK/NACK for PDSCHs in TDD configuration.