Selective VRB-to-PRB Bundle Mapping for Consistent Resource Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing VRB-to-PRB mapping methods can result in inconsistent sizes between VRB and PRB bundles, preventing successful mapping.
Innovation Solution
The method involves determining M VRB bundles with lower frequency and/or J VRB bundles with higher frequency, fixedly mapping them to PRB bundles with the same indexes, and using interleaved mapping to determine PRB bundle indexes for remaining VRB bundles, with specific formulas (M = N − ⌊N / P⌋ × P and J = N − ⌊N / P⌋ × P) to ensure consistent sizes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If interleaved mapping is applied to all VRB bundles, then resource distribution is improved, but mapping consistency deteriorates when VRB bundle size and PRB bundle size become inconsistent
Solution Approach 1:
The patent applies different mapping strategies to different parts of the VRB bundles. Specifically, some VRB bundles are mapped using interleaved mapping while others use non-interleaved mapping, depending on their position and size characteristics. This local differentiation ensures that each bundle is mapped appropriately, maintaining both resource distribution benefits and mapping consistency.
Solution Approach 2:
The patent segments the VRB bundles into different groups based on their indexing position. By dividing the bundles and applying different mapping rules to different segments (interleaved for some, non-interleaved for others), the system resolves the contradiction between achieving good resource distribution through interleaving and maintaining mapping consistency when size mismatches occur.
2Reliability
If non-interleaved mapping is used, then mapping consistency is maintained, but resource distribution becomes poor
Solution Approach 1:
Instead of uniformly applying non-interleaved mapping to all bundles, the patent selectively applies interleaved mapping to specific VRB bundles (those with indexes less than N-D) while using non-interleaved mapping for others. This localized approach to interleaving maintains mapping consistency for bundles where it would cause issues while still achieving resource distribution benefits where applicable.
Solution Approach 2:
The patent introduces dynamic selection of mapping strategies based on bundle index and system parameters. The mapping approach changes dynamically depending on the specific VRB bundle being processed, allowing the system to adapt between interleaved and non-interleaved mapping to maintain consistency while improving resource distribution where possible.
3Device complexity
If VRB bundles are fixedly mapped to PRB bundles with same indexes, then mapping complexity is reduced, but resource allocation flexibility is limited
Solution Approach 1:
The patent segments the mapping process into two distinct phases: a fixed mapping phase for certain VRB bundles (where VRB bundle index equals PRB bundle index) and an interleaved mapping phase for others. This segmentation reduces overall mapping complexity by providing a simple baseline while maintaining allocation flexibility through the interleaved portion.
Solution Approach 2:
The system dynamically determines which VRB bundles undergo fixed mapping and which undergo interleaved mapping based on bundle index and system parameters. This dynamic approach allows the system to maintain low complexity for the fixed mapping portions while preserving resource allocation flexibility through the conditional interleaved mapping for specific bundles.
Data Source
Figure 1~2
Figure 3~5
Figure 6~8
AI summary
Disclosed by the present application are a resource mapping method and apparatus and device, comprising: determining to-be-sent data hosted on a data-channel physical downlink shared channel (PDSCH)/physical uplink shared channel (PUSCH); mapping said to-be-sent data to a virtual resource block (VRB); mapping the virtual resource block to a physical resource block (PRB) in resource block (RB) bundle units. Using the present application, it is possible to prevent the problem of the size of a virtual resource block bundle being inconsistent with the size of a physical resource block bundle, thus causing it to be impossible to map the virtual resource block to the physical resource block.