Deciphering Parameter Synchronization in Wireless Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communications systems, the synchronization of ciphering parameters between sender and receiver is often disrupted due to incorrect settings of sliding window types and sizes, leading to out-of-sync HFN values and resulting in packet discard or window stall issues.

Innovation Solution

The method involves setting the receiving window of a first entity as a Push Type window with a size greater than or equal to that of a second entity when the second entity operates in acknowledged mode, and as a Pull Type window when it operates in unacknowledged or transparent mode, to maintain synchronization and prevent unnecessary packet discard and window stalling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a Pull Type window is used for the receiving window of the deciphering entity, then the window can be advanced when packets with SN outside the window are received, but HFN becomes out of synchronization when packets are retransmitted after being discarded

Engineering Contradiction:
Improvepacket processing efficiencyVSAvoidHFN synchronization
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent dynamically adjusts the receiving window type based on the delivery mode of the lower layer. When the lower layer supports out-of-sequence delivery, a Pull Type window is used to advance the window proactively. When out-of-sequence delivery is not supported, a Push Type window is used to advance the window conservatively only when packets are successfully received or discarded, thereby maintaining HFN synchronization under different network conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of window type (Push Type vs. Pull Type) and window size based on the capabilities of the lower layer. By adjusting these parameters according to whether out-of-sequence delivery is supported, the system optimizes both packet processing efficiency and HFN synchronization reliability for different operational scenarios.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a Push Type window is used for the receiving window of the deciphering entity, then HFN synchronization is maintained, but packets with SN outside the window are discarded unnecessarily causing window stall

Engineering Contradiction:
ImproveHFN synchronizationVSAvoidpacket processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent dynamically selects between Push Type and Pull Type windows based on lower layer capabilities. When out-of-sequence delivery is supported, the Pull Type window allows proactive advancement to prevent unnecessary discards and window stalls. When out-of-sequence delivery is not supported, the Push Type window ensures HFN synchronization is maintained, thus adapting to different network conditions to optimize both reliability and productivity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent adjusts the window type parameter according to the delivery mode of the lower layer. This parameter change enables the system to switch between conservative (Push Type) and proactive (Pull Type) window management strategies, optimizing packet processing efficiency while maintaining HFN synchronization under varying network conditions.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If the receiving window size of the deciphering entity is smaller than the window size of the lower layer entity, then processing overhead is reduced, but packets with SN outside the deciphering window are discarded causing synchronization loss

Engineering Contradiction:
Improveprocessing overheadVSAvoidHFN synchronization
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent performs preliminary action by setting the receiving window size of the deciphering entity to be equal to or larger than the window size of the lower layer entity. This ensures that the deciphering window is sufficiently large to accommodate packets that may arrive out of sequence, preventing unnecessary discards and maintaining HFN synchronization while managing processing overhead.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the receiving window size of the deciphering entity is larger than the window size of the lower layer entity, then packet discard is avoided, but processing complexity and resource consumption increase

Engineering Contradiction:
Improvepacket delivery completenessVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by configuring the receiving window size of the deciphering entity to be equal to or larger than the window size of the lower layer entity before operation begins. This preliminary configuration ensures that the window is sufficiently large to handle out-of-sequence packet delivery, preventing packet discard and maintaining synchronization, while the actual processing overhead is managed through efficient window management algorithms.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8081619B2Method and apparatus of deciphering parameter synchronization in a wireless communications device
Publication Date: 2011.12.20 INNOVATIVE SONIC LTD
  • US8081619B2 patent drawing
  • US8081619B2 patent drawing
  • US8081619B2 patent drawing

AI summary

A method of deciphering parameter synchronization in a reception end of a wireless communications system includes setting a receiving window of a first entity as a Push Type window with a window size greater than or equal to a window size of a receiving window of a second entity when the second entity operates in an acknowledged mode.