Secondary RB Release in Dual Connectivity RRC
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems with dual connectivity, existing methods fail to efficiently manage radio bearer release without affecting data transmission, particularly when no secondary RB with an SCG bearer type is configured, and all downlink data is transmitted or buffers are empty, with no uplink grant requests.
Innovation Solution
A network node with a communication interfacing unit and processor that releases an RRC connection and corresponding RBs when specific conditions are met, including successful transmission of downlink data and absence of uplink grant requests, allowing for the release of secondary RBs without disrupting communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the network node releases the RRC connection and secondary RBs when downlink data is successfully transmitted and buffers are empty, then resource management efficiency is improved and unnecessary network activity is reduced, but the complexity of managing multiple conditions and coordination between master and auxiliary node increases
Solution Approach 1:
The patent segments the bearer management into MCG bearers (managed by master node) and SCG bearers (managed by auxiliary node), allowing independent release decisions for each type. The master node can release secondary RBs independently after verifying downlink data completion, without requiring coordinated action from the auxiliary node, thus simplifying the overall management complexity while improving efficiency.
Solution Approach 2:
The master node performs preliminary verification of release conditions (downlink data transmission completion, buffer status, uplink grant requests) before initiating the RB release process. This preliminary action ensures that all necessary conditions are met before releasing resources, preventing premature release that could affect ongoing communications, thereby improving resource management efficiency without increasing operational complexity.
2Reliability
If the network node waits for all downlink data to be transmitted and buffers to be empty before releasing secondary RBs, then data transmission reliability is improved, but the time delay in resource release increases
Solution Approach 1:
The master node continuously monitors feedback information including downlink data transmission status, buffer status, and uplink grant requests from the UE. Based on this real-time feedback, the master node determines when all downlink data has been successfully transmitted and buffers are empty, allowing timely release of secondary RBs while ensuring data transmission reliability is maintained.
Solution Approach 2:
The system uses self-service mechanisms where the master node autonomously determines the appropriate time to release secondary RBs based on monitored conditions (downlink data completion, buffer status, uplink grant requests). This self-service approach eliminates the need for explicit coordination with the auxiliary node for release timing, reducing release delay while maintaining reliability through condition-based decision making.
3Speed
If the network node releases secondary RBs independently without coordinating with the auxiliary node, then the speed of resource release is improved, but the risk of communication inconsistency between master and auxiliary node increases
Solution Approach 1:
The patent segments bearer management responsibilities between master and auxiliary nodes, with the master node having independent authority to release MCG bearers and the auxiliary node managing SCG bearers. This segmentation allows the master node to release secondary RBs independently and quickly without coordination delays, while communication consistency is maintained through the defined functional split and condition verification mechanisms.
Solution Approach 2:
The master node performs preliminary verification of release conditions (downlink data transmission completion, buffer status, uplink grant requests) before initiating the release process. This preliminary action ensures that releasing RBs independently will not create communication inconsistencies, as all necessary conditions are confirmed to be satisfied before the release takes effect.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network node includes a communication interfacing unit and a processor. The processor operable to perform operations includes controlling the communication interfacing unit to establish at least one second RB with a secondary cell group (SCG) bearer type between the communication device and an auxiliary network node; and releasing one of the at least one second RB under a condition that, for a first time period, all of downlink data in at least one downlink buffer corresponding to the one of the at least one second RB is successfully transmitted or the at least one downlink buffer corresponding to the one of the at least one second RB is empty, and the auxiliary network node does not receive any request for an uplink grant allocation.