Parallel ARQ Status Reporting for Low-Latency Packet Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems face challenges in efficiently managing parallel cores for ARQ status reporting, leading to increased latency and decreased performance due to lock acquisition and synchronization issues, particularly in high-throughput scenarios.

Innovation Solution

Implementing a mechanism for parallel status reporting using an alternate Status Report Control PDU Type (CPT) and introducing a START_SN field to enable parallel processing of ARQ status across multiple threads without locks, allowing for efficient preparation and transmission of status reports even in cases of grant insufficiency or loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single thread is used to prepare the Status PDU sequentially, then the processing is simple and lock-free, but the latency increases and throughput decreases

Engineering Contradiction:
ImproveStatus PDU preparation throughputVSAvoidStatus PDU preparation latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The Status PDU preparation process is segmented into multiple independent threads, each responsible for processing specific portions of the receive window. The receive window is divided into segments that can be processed in parallel, with each thread generating partial Status PDU information that is later combined into the complete Status PDU.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-threaded sequential processing model to a multi-threaded parallel processing model by adding the dimension of concurrent execution. Multiple threads operate simultaneously on different portions of the status report generation task, fundamentally changing the time complexity from linear to logarithmic or constant time operations.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If multiple threads are used to prepare the Status PDU in parallel, then the throughput increases and latency decreases, but lock acquisition and synchronization issues arise

Engineering Contradiction:
ImproveStatus PDU preparation throughputVSAvoidSynchronization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the critical section that requires synchronization and replaces it with lock-free data structures and algorithms. By redesigning the status report generation to use atomic operations and thread-local storage where possible, the need for complex locking mechanisms is eliminated or minimized.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces intermediary data structures and communication mechanisms that allow multiple threads to collaborate without direct synchronization. Thread-safe queues, atomic counters, and merge operations serve as intermediaries that coordinate thread execution without requiring locks.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If the Status PDU is truncated due to insufficient grants, then the available resources are utilized efficiently, but the recovery delay increases

Engineering Contradiction:
ImproveResource utilization efficiencyVSAvoidPacket recovery delay
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent prepares the complete Status PDU information in advance using parallel thread processing, storing it in a buffer or memory structure. When grants become available, even if truncated, the pre-computed status information can be quickly transmitted without requiring full re-computation, reducing the impact of truncation on recovery delay.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent dynamically adjusts the Status PDU content based on available grant size. By changing the parameter of status report completeness rather than the processing methodology, the system can efficiently utilize variable grant sizes while maintaining the benefits of parallel processing for status computation.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If the same Status PDU creation process is repeated after Status PDU loss, then the system ensures accurate status reporting, but the processing delay increases further

Engineering Contradiction:
ImproveStatus reporting accuracyVSAvoidRepeated processing delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent maintains pre-computed status information in memory buffers that persist across transmission attempts. When a Status PDU is lost, the receiver can request retransmission of the same pre-computed status information without requiring the transmitter to re-execute the entire parallel processing pipeline, significantly reducing repeated processing delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates copies of the computed status information and stores them for potential retransmission. Instead of regenerating the Status PDU from scratch after loss, the system retrieves and retransmits stored copies, maintaining reliability while minimizing processing overhead.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250350409A1Method and apparatus of reporting automatic repeat request status in a communication system
Publication Date: 2025.11.13 SAMSUNG ELECTRONICS CO LTD
  • US20250350409A1 patent drawing
  • US20250350409A1 patent drawing
  • US20250350409A1 patent drawing

AI summary

The disclosure relates to a method and a system of reporting Automatic Repeat Request (ARQ) status in a communication system by a receiver entity. The method comprising: receiving a bit sequence of an ARQ packet; determining a plurality of threads configured to run in parallel on at least one part of the bit sequence; detecting reception status of one or more bits in the at least one part of the bit sequence by running in parallel the plurality of threads on the at least one part of the bit sequence; compiling the reception status of one or more bits from the plurality of threads; and transmitting, by the receiver entity, a status report prepared based on compilation of the reception status of one or more bits from the plurality of threads to a lower layer.