Primary-Path UL Grant Allocation for Faster MR-DC Uplink Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Multi-Radio Dual Connectivity (MR-DC) architectures do not provide primary path configuration information to the gNB-DU, leading to non-optimized packet scheduling and delays in uplink data transmission.
Innovation Solution
Implementing a method where a gNB-CU sends a UE context modification request to a gNB-DU with parameters indicating the need for pre-configured uplink scheduling grants and primary path configuration, allowing the gNB-DU to allocate grants on the primary path before the UE sends a scheduling request.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If existing MR-DC architecture is used without primary path configuration information, then device complexity is reduced, but uplink data transmission speed deteriorates due to non-optimized packet scheduling
Solution Approach 1:
The gNB-CU performs preliminary configuration by providing primary path configuration information to the gNB-DU before uplink data transmission. This allows the gNB-DU to pre-allocate uplink grants and optimize packet scheduling in advance, eliminating the need for UE to send scheduling requests and improving transmission speed without significant additional complexity
Solution Approach 2:
The patent introduces an intermediary mechanism where the gNB-CU acts as a mediator between the core network and gNB-DU, transferring primary path configuration information through F1 interface messages (UE Context Setup Request, UE Context Modification Request). This intermediary approach enables optimized scheduling at gNB-DU without requiring direct complex configuration at each node
2Loss of time
If pre-configured grants are allocated on primary path, then uplink data transmission delay is reduced, but network node processing complexity increases
Solution Approach 1:
Uplink grants are pre-configured and allocated to the UE on the primary path before data transmission occurs. The gNB-DU receives primary path configuration information and proactively allocates grants, eliminating the time delay associated with scheduling requests and grant allocation during active transmission
Solution Approach 2:
The system implements self-service through automated grant allocation based on pre-configured parameters. Once the gNB-DU receives the primary path configuration, it autonomously manages grant allocation without requiring continuous manual intervention or complex real-time decision-making, reducing processing complexity while maintaining low delay
3Productivity
If primary path configuration information is provided to gNB-DU, then packet scheduling optimization is achieved, but network interface complexity increases
Solution Approach 1:
The patent utilizes existing multi-functional F1 interface messages (UE Context Setup Request, UE Context Modification Request, UE Context Release Request) to carry primary path configuration information. These messages already serve multiple purposes in the gNB-CU to gNB-DU communication, and the patent extends their functionality to include scheduling optimization parameters without requiring new dedicated interface protocols
Solution Approach 2:
The primary path configuration information is merged into existing F1 interface message structures. Rather than creating separate dedicated signaling messages, the patent combines the scheduling optimization parameters with routine context management messages, reducing network interface complexity while achieving packet scheduling optimization
Data Source
AI summary
A first network node comprises program code including: first receiving code configured to cause at least one of said at least one processor to receive, from a second network node, a UE context modification request; first transmitting code configured to cause at least one of said at least one processor to transmit, to the second network node in response to receiving the context modification request, a context modification response; allocating code configured to cause at least one of said at least one processor to, in response to the UE context modification request, allocate one or more pre-configured grants to the UE, and second receiving code configured to cause at least one of said at least one processor to receive, from the UE in response to the one or more pre-configured grants, first uplink data, before sending a scheduling request to the base station and receiving corresponding UL scheduling grants.