Connectionless Burst Synchronization via Final PDU Indication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In connectionless transmissions, maintaining synchronization between user equipment (UE) and the network is challenging, particularly in burst transmissions, leading to potential out-of-sync conditions that result in incorrect decryption and delivery of garbage data due to lost acknowledgments and lack of explicit connection maintenance signaling.
Innovation Solution
The solution involves adding additional information to protocol data units (PDUs) to maintain state information, such as a transmission identifier (T_ID) that is updated and stored, allowing devices to recognize new and old transmissions, and establishing and releasing radio link control (RLC) resources accordingly, ensuring proper synchronization and preventing out-of-sync conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If connectionless burst transmissions are used to reduce overhead, then device complexity and signaling overhead are reduced, but synchronization reliability deteriorates due to lost acknowledgments and lack of explicit connection maintenance
Solution Approach 1:
The transmitting device sends a final PDU indication in advance to notify the receiving device that no further PDUs will follow. This preliminary action allows the receiving device to prepare for resource release and prevents synchronization issues that would arise from waiting for an acknowledgment that may be lost.
Solution Approach 2:
The receiving device sends an acknowledgment for the final PDU to confirm receipt and trigger resource release at the transmitting device. This feedback mechanism ensures both devices know when to release RLC resources, maintaining synchronization without requiring persistent connections.
2Productivity
If RLC resources are released after burst transmission to free up resources, then resource efficiency is improved, but synchronization is lost leading to incorrect decryption of retransmissions
Solution Approach 1:
The final PDU indication is sent before the acknowledgment, allowing the receiving device to know in advance when resources can be safely released. This preliminary notification prevents the receiving device from releasing resources too early, which would cause synchronization loss when retransmissions occur.
Solution Approach 2:
The acknowledgment sent by the receiving device serves as feedback to the transmitting device, confirming that the final PDU was received and resources can now be released. This ensures both devices release resources at the appropriate time, maintaining synchronization while improving resource efficiency.
3Reliability
If acknowledgments are sent to confirm receipt of PDUs, then transmission reliability is improved, but the system becomes vulnerable to out-of-sync conditions when acknowledgments are lost
Solution Approach 1:
The final PDU indication is sent in advance, allowing the receiving device to prepare for resource release without waiting for the acknowledgment. This preliminary action reduces the vulnerability to lost acknowledgments, as the receiving device can determine when to release resources based on the final PDU indication rather than waiting for potentially lost feedback.
Data Source
AI summary
A method for operating a receiving device includes receiving a first protocol data unit (PDU) of a first burst transmission, the first PDU includes a first transmission identifier (T_ID) associated with the first burst transmission, and the first PDU further includes a final PDU indication indicating that the first PDU is a final PDU of the first burst transmission, and releasing a first radio link control (RLC) resource associated with the first T_ID when the first RLC resource associated with the first T_ID exists.