RLC Reset Synchronization for PDU Size Adaptation

The patent applies preliminary action by checking whether an RLC reset procedure is currently pending before performing single-sided RLC re-establishment. If a reset is pending, the re-establishment is delayed until the reset completes. This prevents the HFN synchronization problem by ensuring that PDU size changes do not interfere with ongoing reset procedures that are critical for maintaining data integrity.

The patent implements feedback mechanisms through timer monitoring and state checking. The UE checks the status of RLC reset procedures and uses timers to track pending operations. This feedback loop ensures that single-sided re-establishment is only performed when it is safe to do so, preventing HFN mismatches while still allowing efficient PDU size changes when appropriate.

The patent performs a preliminary check to determine whether an RLC reset procedure is pending before initiating a PDU size change via single-sided re-establishment. By checking the reset state in advance and delaying re-establishment if necessary, the patent ensures that PDU size changes occur only when HFN synchronization is not at risk, thus maintaining both adaptability and reliability.

The patent applies preliminary anti-action by preventing single-sided RLC re-establishment when an RLC reset procedure is detected as pending. This counter-measure blocks the potentially harmful action (re-establishment during reset) before it can cause HFN desynchronization, thereby protecting data integrity while still allowing PDU size changes under safe conditions.

The patent segments the RLC entity into independent uplink and downlink sides, enabling single-sided re-establishment. This segmentation allows the downlink side to be re-established for PDU size changes without affecting uplink data transmission. By isolating the impact of re-establishment to only the downlink side, the patent avoids the need for full RLC resets that would cause bidirectional data loss.

The patent introduces dynamic behavior by allowing selective re-establishment of RLC entities based on current operational conditions. Instead of static full resets, the system dynamically determines whether single-sided re-establishment is appropriate by checking reset procedure status. This dynamic approach maintains data integrity through targeted interventions rather than blanket resets.