RNTI-Based Resource Allocation for 5G NR Scheduling Flexibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G New Radio (NR) system's resource allocation methods for Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) are limited, leading to inflexibility and inefficiency in scheduling, particularly for Ultra Reliable & Low Latency Communication (URLLC) services due to restricted parameter options and high DCI overhead.
Innovation Solution
A resource allocation method that uses multiple resource collections, each corresponding to a unique Radio Network Temporary Identity (RNTI), allowing for dynamic allocation of time-frequency domain resources based on different types of services without increasing DCI overhead, by configuring different resource collections for DCI scrambled with different RNTIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single resource allocation table with limited SLIV values (16 entries) is used for PDSCH/PUSCH time domain resource allocation, then DCI overhead is controlled, but scheduling flexibility and resource allocation efficiency are greatly limited
Solution Approach 1:
The patent divides the resource allocation mechanism into multiple resource tables (first resource table and second resource table), each associated with different RNTIs. This segmentation allows different tables to serve different service types (eMBB and URLLC) with appropriate resource configurations, resolving the contradiction between limited table size and scheduling flexibility needs.
Solution Approach 2:
The patent changes the parameter of resource table selection by introducing RNTI-based differentiation. Different RNTIs (e.g., C-RNTI for eMBB, MCS-C-RNTI for URLLC) are associated with different resource tables that have different SLIV configurations. This parameter change enables the system to adapt resource allocation characteristics to different service requirements while maintaining controlled DCI overhead.
2Quantity of substance
If a PDSCH/PUSCH time domain resource table contains only 16 SLIV values to control DCI overhead, then DCI size is limited, but the ability to support multiple dimensional parameters (starting symbol, quantity of symbols, mapping types) is restricted
Solution Approach 1:
The patent segments the resource configuration space into multiple tables, where each table can be optimized for specific parameter combinations. The first resource table can be configured with SLIV values suitable for eMBB services, while the second resource table can contain SLIV values optimized for URLLC services. This segmentation allows each table to provide adequate parameter options for its target service type without requiring a single excessively large table.
Solution Approach 2:
The patent creates a universal resource allocation framework where multiple resource tables serve different service types through RNTI-based selection. Each table functions specifically for its associated service type, yet collectively they provide universal coverage for both eMBB and URLLC services, enabling the system to support diverse parameter requirements across different service types.
3Device complexity
If a PUSCH resource set contains only 32 PUSCH resources to control DCI overhead, then DCI complexity is managed, but resource allocation efficiency and flexibility for URLLC services are compromised
Solution Approach 1:
The patent segments the PUSCH resource allocation into separate tables for different service types. The second resource table can be specifically optimized for URLLC services with resource configurations that prioritize low latency and high reliability. This segmentation allows URLLC-specific optimizations without requiring all PUSCH resources to be included in a single large table, thus maintaining DCI complexity management while improving resource allocation efficiency for URLLC.
4Quantity of substance
If limited optional values are provided in each resource dimension to control DCI overhead, then DCI size is constrained, but flexibility for supporting both eMBB and URLLC services simultaneously is greatly limited
Solution Approach 1:
The patent segments resource allocation into service-specific tables associated with different RNTIs. The first resource table can provide parameter options optimized for eMBB services, while the second resource table provides parameter options optimized for URLLC services. This segmentation enables the system to support both service types simultaneously with appropriate parameter options for each, without requiring a single large table that would increase DCI overhead.
Solution Approach 2:
The patent uses RNTI-based parameter changes to select between different resource tables with different SLIV configurations. When URLLC service is detected (via specific RNTI), the system switches to the second resource table with URLLC-optimized parameters. This parameter change mechanism enables dynamic adaptation to different service types while maintaining controlled DCI overhead through table-specific parameter sets.
Data Source
AI summary
Implementations of the present disclosure relate to a resource allocation method, a terminal device, and a network device. The method comprises: receiving first configuration information transmitted by a network device, wherein the first configuration information comprises multiple resource collections, the multiple resource collections are in one-to-one correspondence with multiple RNTIs, each of the multiple resource collections is used for indicating an available resource of a target channel, and the available resources indicated by the multiple resource collections are different; receiving target downlink control information (DCI) transmitted by the network device; and if the target DCI is scrambled according to a first RNTI among the multiple RNTIs, determining a resource used by the target channel in a first resource collection corresponding to the first RNTI.