PUSCH Time-Domain Scheduling on Unlicensed Bands
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The time domain resource allocation for physical uplink shared channels (PUSCH) on an unlicensed band is unclear, particularly for configured grant (CG) PUSCHs carrying semi-persistent channel state information (SP-CSI) and retransmissions, and the use of non-fallback DCI formats like DCI format 0_1 is not well-defined in existing technologies.
Innovation Solution
A method and apparatus for determining time domain resource allocation lists for PUSCHs on an unlicensed band, using non-fallback DCI formats, where the allocation is based on whether the transmission is first or retransmission and the scrambling identifier, such as CS-RNTI or SP-CSI-RNTI, to ensure consistent and flexible scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-fallback DCI format is used to schedule PUSCH transmission on unlicensed band, then scheduling flexibility is improved, but time domain resource allocation becomes unclear
Solution Approach 1:
The patent applies parameter changes by differentiating resource allocation based on DCI format type (fallback vs non-fallback) and transmission type (first transmission vs retransmission). The time domain resource allocation list is selected dynamically according to these parameter changes, resolving the ambiguity in resource allocation information while maintaining scheduling flexibility.
Solution Approach 2:
The patent implements dynamics by making the time domain resource allocation list selection adaptive rather than fixed. The terminal dynamically determines which allocation list to use based on the received DCI format and transmission type, allowing the system to adapt to different scheduling scenarios on unlicensed bands.
2Device complexity
If time domain resource allocation list is not clearly defined, then device complexity is reduced, but communication reliability deteriorates
Solution Approach 1:
The patent applies universality by defining a unified set of time domain resource allocation lists that serve multiple purposes: first transmissions, retransmissions, and different DCI formats all reference the same allocation lists. This multi-functional approach ensures clear and reliable resource allocation without requiring separate complex configurations for each scenario.
Solution Approach 2:
The patent implements feedback mechanisms where the terminal reports its interpretation of the time domain resource allocation list back to the network. This feedback loop ensures that both sides have consistent understanding of the resource allocation, thereby improving communication reliability while maintaining manageable device complexity.
3Productivity
If multiple PUSCHs are scheduled with different time domain resources, then productivity is improved, but measurement precision of resource allocation requirements deteriorates
Solution Approach 1:
The patent applies segmentation by dividing the time domain resource allocation into distinct lists for different transmission scenarios (first transmission list and retransmission list). Each list contains specific time domain resource allocations tailored to its purpose, allowing multiple PUSCHs to be scheduled efficiently while maintaining precise control over resource allocation requirements.
Solution Approach 2:
The patent uses parameter changes to differentiate between first transmissions and retransmissions, assigning different time domain resource allocation lists to each. This parameter-based differentiation enables the system to schedule multiple PUSCHs with different time domain resources while maintaining precise measurement and control of allocation requirements for each type of transmission.
Data Source
AI summary
A resource determining method and apparatus, and a terminal are disclosed. The solution includes: receiving first DCI, where the first DCI is in a non-fallback DCI format, and at least one row index in a time domain resource allocation list associated with the non-fallback DCI format indicates time domain transmission resources of a plurality of physical uplink shared channels PUSCHs; and the first DCI is used for scheduling transmission of the PUSCHs on an unlicensed band; and determining a time domain resource allocation list used for transmitting the PUSCHs according to the following content: whether the transmission scheduled by the first DCI is first transmission or retransmission and a scrambling identifier of the first DCI.


