NR Resource Block Mapping for Consistent VRB-PRB Bundle Sizes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Next Generation Radio (NR) technology, the existing VRB-to-PRB mapping methods often result in inconsistent sizes between VRB and PRB bundles, leading to incomplete mapping processes.
Innovation Solution
The proposed method involves determining M VRB bundles with lower frequency and/or L VRB bundles with higher frequency, fixedly mapping these to PRB bundles, and using interleaved mapping to determine corresponding PRB bundle numbers, while inserting nulls in the interleaver to ensure consistent mapping, avoiding size inconsistencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If interleaved VRB-to-PRB mapping is used, then resource allocation flexibility is improved, but VRB bundle and PRB bundle size consistency deteriorates causing mapping failure
Solution Approach 1:
The patent segments the VRB-to-PRB mapping process into two distinct parts: (1) direct mapping for the first and/or last VRB bundles, and (2) interleaved mapping for the remaining VRB bundles. This segmentation allows the system to maintain bundle size consistency through direct mapping while still achieving resource allocation flexibility through interleaved mapping for the remaining bundles, thereby resolving the contradiction between adaptability and reliability.
Solution Approach 2:
The patent applies different mapping strategies to different parts of the resource blocks: direct mapping is applied to the first and/or last VRB bundles where size consistency is critical, while interleaved mapping is applied to the remaining VRB bundles where flexibility is prioritized. This local differentiation of mapping quality ensures that each region serves its specific function, resolving the contradiction between overall flexibility and local consistency.
2Device complexity
If direct VRB-to-PRB mapping is used, then mapping simplicity is improved, but resource allocation flexibility deteriorates
Solution Approach 1:
The mapping process is segmented into simple direct mapping for boundary bundles and more complex interleaved mapping for intermediate bundles. This segmentation allows the system to maintain overall manageable complexity while achieving the flexibility benefits of interleaved mapping where needed, resolving the contradiction between simplicity and adaptability.
Solution Approach 2:
Different mapping complexities are applied locally: simple direct mapping for first/last bundles and complex interleaved mapping for remaining bundles. This local quality approach ensures that the mapping process remains simple where flexibility is less critical while achieving flexibility where required, balancing complexity and adaptability.
3Reliability
If VRB bundles are fixedly mapped to PRB bundles, then mapping reliability is improved, but resource distribution uniformity deteriorates
Solution Approach 1:
The patent segments the mapping approach: fixed direct mapping for first/last VRB bundles ensures reliability, while interleaved mapping for remaining bundles achieves uniform resource distribution. This segmentation allows the system to satisfy both requirements by applying the appropriate mapping strategy to the appropriate bundles.
Solution Approach 2:
Different mapping strategies are applied to different regions: fixed mapping provides reliability for boundary bundles, while interleaved mapping provides uniform distribution for intermediate bundles. This local differentiation resolves the contradiction between reliability and uniformity by optimizing each region for its primary requirement.
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.