RNC Node-B RLC PDU Size Notification Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communication systems, the current NBAP protocol lacks the ability to notify whether the RLC PDU size has a fixed or variable length, leading to discrepancies between RNC and Node-B, resulting in inefficient data communication and potential failures during flow control.
Innovation Solution
A mobile communication system that includes a control device and a base station capable of communicating using both fixed-length and variable-length data sizes, where the control device transmits information indicating the data size type to the base station, enabling consistent setting states and adaptive flow control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the NBAP protocol is used for communication between RNC and Node-B, then the protocol can be implemented with existing standards, but the protocol lacks the ability to notify whether RLC PDU size has fixed or variable length, leading to setting discrepancies
Solution Approach 1:
The patent applies preliminary action by having the RNC determine the RLC PDU size format (fixed or variable length) before establishing the radio link, and then notifying the Node-B of this determination through the NBAP protocol. This ensures that both RNC and Node-B have consistent understanding of the data size format before communication begins, preventing setting discrepancies.
Solution Approach 2:
The patent introduces a notification mechanism as an intermediary between RNC and Node-B. The RNC sends explicit notification information through the NBAP protocol to convey the RLC PDU size format determination to the Node-B. This intermediary communication ensures that the Node-B receives accurate setting information that it would otherwise lack in the standard NBAP protocol.
2Productivity
If fixed-length data size is used for communication, then the protocol processing is simplified, but the data communication efficiency is reduced due to inability to adapt to varying communication status
Solution Approach 1:
The patent applies dynamics by enabling the system to switch between fixed-length and variable-length RLC PDU sizes based on communication status. The RNC determines the appropriate format and notifies the Node-B, allowing the system to adapt dynamically between different data size modes. This provides flexibility to optimize for either efficiency (variable length) or simplicity (fixed length) as needed.
Solution Approach 2:
The patent changes the parameter of RLC PDU size format from a static configuration to a dynamically selectable parameter. The RNC can determine and switch between fixed-length and variable-length modes based on communication requirements, and this parameter change is communicated to the Node-B through NBAP notification, enabling efficient adaptation to varying traffic conditions.
3Productivity
If variable-length data size is used for communication, then the data communication efficiency is improved through adaptive sizing, but the protocol complexity increases due to need for size negotiation and management
Solution Approach 1:
The patent applies preliminary action by having the RNC determine the RLC PDU size format before radio link establishment and notify the Node-B in advance. This preliminary determination and notification simplifies the overall process by avoiding complex runtime negotiations, as both parties know the data size format before communication begins.
Solution Approach 2:
The patent implements feedback through the NBAP notification mechanism, where the RNC's determination of RLC PDU size format is communicated back to the Node-B. This feedback ensures that the Node-B has the necessary information to properly handle variable-length data transmissions without requiring complex autonomous negotiation protocols.
4Reliability
If the RNC and Node-B have different settings for RLC PDU size format, then each device can operate independently, but flow control failures occur due to incompatible data transmission
Solution Approach 1:
The patent applies preliminary action by having the RNC determine the RLC PDU size format before radio link establishment and notify the Node-B of this determination. This ensures that both devices have synchronized settings before communication begins, preventing flow control failures that would result from incompatible data transmission formats.
Solution Approach 2:
The patent introduces NBAP notification as an intermediary mechanism that transfers the RLC PDU size format setting from the RNC to the Node-B. This intermediary communication ensures reliable setting synchronization between the two devices, eliminating the risk of incompatible configurations while maintaining operational independence.
Data Source
AI summary
A mobile communication system includes a control device and a base station device. Data communication between the control device and the base station device is conducted using a fixed-length data size and a variable-length data size. The control device transmits information indicating whether a data size of the data communication has a fixed length or a variable length. The base station device receives the information from the control device.