Mobile Data Segmentation via Alternate Extension Bit Interpretation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communications systems, particularly in Unacknowledged Mode (UM), the existing data segmentation methods waste system resources and lower transmission efficiency due to unnecessary padding and Length Indicator fields when handling Voice over Internet Protocol (VoIP) services, which require instant and continuous packet transmission.
Innovation Solution
The method involves configuring an Alternate Extension-bit Interpretation to set the first extension bit of a Protocol Data Unit (PDU) to a specified value, indicating whether the next field contains a complete Service Data Unit (SDU) that is not segmented, concatenated, or padded, thereby eliminating the need for additional Length Indicator fields and optimizing PDU composition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If Length Indicator fields and extension bits are added to each PDU to indicate SDU boundaries, then data segmentation accuracy is improved, but transmission efficiency deteriorates due to increased overhead
Solution Approach 1:
The patent extracts the Length Indicator field from the standard PDU structure when the alternate extension-bit interpretation is configured. By removing this redundant field and using the extension bit to implicitly indicate SDU boundaries, the overhead is reduced while segmentation accuracy is maintained through the alternative interpretation mechanism.
Solution Approach 2:
The patent changes the interpretation parameter of the extension bit from its conventional meaning to a new meaning that indicates SDU boundary information. This parameter change allows the same bit to convey different information depending on the configuration, eliminating the need for separate Length Indicator fields and improving transmission efficiency.
2Stability of the object's composition
If padding fields are added to PDUs to maintain fixed packet sizes, then packet structure stability is improved, but bandwidth utilization deteriorates due to wasted transmission resources
Solution Approach 1:
The patent introduces dynamic packet sizing by allowing PDUs to have variable lengths based on the actual data content. When the alternate extension-bit interpretation is used, the PDU structure becomes flexible rather than fixed, eliminating the need for padding fields and improving bandwidth utilization while maintaining structural integrity through the alternative boundary indication mechanism.
Solution Approach 2:
The patent discards the padding field mechanism in favor of a more efficient approach. By using the alternate extension-bit interpretation to indicate SDU boundaries, the system recovers the wasted bandwidth that would have been used for padding, while still maintaining packet structure stability through the alternative boundary detection method.
3Productivity
If the first extension bit is used as a flag to indicate complete SDU, then transmission overhead is reduced, but compatibility with existing systems deteriorates
Solution Approach 1:
The patent applies preliminary action by configuring the alternate extension-bit interpretation mode before data transmission begins. This pre-configuration establishes a new operational mode that reduces overhead while maintaining compatibility through a configured parameter that can be set in advance, allowing the system to operate in this optimized mode without requiring real-time negotiation or breaking existing protocols.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of data segmentation in a transmitter of a mobile communications system includes initiating alternate extension bit interpretation, a last data segment of a Service Data Unit exactly ending at an end of a Protocol Data Unit, no Length Indicator in the Protocol Data Unit indicating the end of the Service Data Unit, a length of a next Service Data Unit following the Service Data Unit exactly equaling to a length of a data field of a next Protocol Data Unit following the Protocol Data Unit, and setting a first extension bit of the next Protocol Data Unit to be a specified value for indicating that the next Protocol Data Unit comprises a complete Service Data Unit, which is not segmented, concatenated or padded, and indicating that a Service Data Unit exactly ended in the Protocol Data Unit.