PUSCH Resource Block Mapping Across UL Allocation Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for mapping PUSCH signals are limited to UL resource allocation type 1, which can result in blind detection by the network side when UEs are in different RRC states, and switching to UL resource allocation type 2 leads to undetectable signals due to unknown intra-cell guard bands.
Innovation Solution
A method and apparatus for determining target resource blocks and mapping modes based on frequency domain resource allocation types and scheduling modes, allowing UEs to map PUSCH signals effectively across different types, ensuring detection by the network side.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If UL resource allocation type 1 is used for PUSCH mapping, then the mapping can be performed within the initial BWP, but the network side cannot detect PUSCH signals when UEs have different intra-cell guard bands
Solution Approach 1:
The patent introduces dynamic adaptability by enabling the terminal to select different mapping modes (first mapping mode for allocation type 1, second mapping mode for allocation type 2) based on the configured frequency domain resource allocation type. This dynamic selection resolves the contradiction by making the system adaptable to different allocation types while maintaining reliable signal detection through appropriate mode selection.
Solution Approach 2:
The patent changes the mapping parameter (mapping mode) based on the frequency domain resource allocation type parameter. When allocation type 1 is configured, the first mapping mode is used; when allocation type 2 is configured, the second mapping mode is used. This parameter-based adaptation resolves the contradiction between detection reliability and allocation type versatility.
2Adaptability or versatility
If UL resource allocation type 2 is used for PUSCH mapping, then the terminal can map signals according to different frequency domain resource allocation types, but the network side cannot detect the signals due to unknown intra-cell guard bands
Solution Approach 1:
The patent makes the mapping process dynamic by selecting the second mapping mode specifically when allocation type 2 is configured. This dynamic adaptation allows the system to handle different allocation types appropriately, resolving the contradiction by ensuring the network side can detect signals even with different intra-cell guard bands through the appropriate mapping mode selection.
Solution Approach 2:
The patent changes the mapping behavior based on the allocation type parameter. For allocation type 2, the second mapping mode is employed which properly handles the intra-cell guard band variations, thereby maintaining detection reliability while supporting allocation type versatility.
3Device complexity
If the terminal maps all PUSCHs to the initial UL BWP to avoid blind detection, then the mapping is simplified, but the network side may still fail to detect signals when UEs are in different RRC states
Solution Approach 1:
The patent introduces dynamic mapping mode selection based on the UE's RRC state and the configured allocation type. In the idle state, the terminal uses the first mapping mode; in the connected state, it uses the second mapping mode. This dynamic adaptation resolves the contradiction by maintaining relatively simple mapping processes while ensuring reliable signal detection across different RRC states.
Solution Approach 2:
The patent changes the mapping mode parameter according to the RRC state parameter. This parameter-based adaptation allows the system to maintain simplicity in the mapping process while ensuring reliable signal detection by selecting the appropriate mode for each state.
Data Source
AI summary
This application discloses a method for mapping a PUSCH signal, a terminal, and a network-side device. The method for mapping a PUSCH signal includes: determining, according to a frequency domain resource allocation type for the terminal and frequency domain resource allocation information for the terminal, a target resource block allocated to a PUSCH, where the target resource block includes a first target VRB or a first target PRB; determining, according to the frequency domain resource allocation type and/or a scheduling mode of the PUSCH, a mapping mode of mapping a PUSCH signal to a second target PRB, where the second target PRB is the first target PRB or a PRB corresponding to the first target VRB; and mapping the PUSCH signal to the second target PRB by using the mapping mode.