SeNB Release Request Message with Cause IE for Signaling Overhead Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems, especially in dual connectivity scenarios, there is a challenge in efficiently notifying radio resource control (RRC) connection errors and service releases due to incorrect RRC configuration, leading to signaling waste and inability to modify or add secondary eNBs.
Innovation Solution
A method and apparatus for transmitting a secondary eNB (SeNB) Release Request message with a cause, such as 'Radio Connection With UE Lost' or 'Failure in the Radio Interface Procedure', from the master eNB to the SeNB, including data forwarding addresses, to initiate the release of all SCG or split bearers, thereby reducing signaling waste and facilitating proper resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If the MeNB transmits the SeNB Release Request message with the cause to the SeNB, then the signaling overhead is reduced and resource management is improved, but the system complexity increases due to additional message modifications
Solution Approach 1:
The cause information is segmented into a dedicated cause information element (IE) within the SeNB Release Request message structure, separating the error cause indication from other message components. This allows the cause to be transmitted efficiently without requiring complete message redesign, reducing overall signaling overhead while maintaining structured organization.
Solution Approach 2:
The SeNB Release Request message is enhanced to serve multiple functions: it not only requests SeNB release but also conveys the specific cause of release through the included cause IE. This multi-functionality reduces the need for separate signaling messages, thereby reducing signaling overhead while the message structure adapts to handle multiple purposes.
2Productivity
If the cause information is included in the SeNB Release Request message, then the error notification efficiency is improved, but the message processing complexity increases
Solution Approach 1:
The cause information is prepared and included in advance within the SeNB Release Request message before transmission to the SeNB. This preliminary inclusion ensures that the SeNB receives complete error notification information immediately, improving error notification efficiency without requiring additional follow-up signaling exchanges.
Solution Approach 2:
The cause information element acts as an intermediary carrier that conveys the specific error cause from the MeNB to the SeNB within the existing message framework. This intermediary structure allows efficient error notification while maintaining compatibility with the existing message processing architecture, minimizing the increase in processing complexity.
3Reliability
If the SeNB Release Request message includes data forwarding address, then the resource release completeness is improved, but the signaling message size increases
Solution Approach 1:
The data forwarding address information is merged with the SeNB Release Request message, combining the release request function with the data forwarding configuration function in a single message transmission. This merging ensures complete resource release information is conveyed together, improving resource release completeness while avoiding the overhead of separate signaling messages.
Solution Approach 2:
The message includes only the necessary data forwarding address information required for complete resource release, rather than transmitting all possible configuration parameters. This partial inclusion of only essential elements ensures resource release completeness while keeping the message size optimized and avoiding unnecessary data transmission.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and apparatus for transmitting a secondary eNB (SeNB) release request message in a wireless communication system is provided. A master evolved NodeB (MeNB) of dual connectivity receives a message including a cause, which indicates that a user equipment (UE) has not successfully applied a secondary cell group (SCG) configuration, from the UE, and transmit the SeNB Release Request message including the cause to a SeNB.