Sidelink Fallback Retransmission Feedback Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems, particularly in sidelink communications, face challenges in efficiently managing retransmissions in scenarios where transmissions from base stations (BS) or programmable logic controllers (PLC) are not successfully decoded by user equipment (UE), leading to potential service disruptions and reduced reliability in industrial internet-of-things (IIOT) and other applications.

Innovation Solution

Implementing a system where UE monitors transmissions, determines decoding success, and sends feedback messages indicating whether the BS or PLC should retransmit, with options to configure thresholds for determining retransmission based on decoding information such as SINR and LLR values, allowing for proactive or reactive retransmission strategies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If fallback retransmission is implemented in sidelink communications, then reliability of data transmission is improved, but device complexity and protocol overhead increase

Engineering Contradiction:
Improvetransmission reliabilityVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the receiving UE sends acknowledgment information to the transmitting UE, enabling the transmitter to determine whether retransmission is needed. This feedback loop is central to the fallback retransmission process and resolves the reliability issue by ensuring successful data delivery.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies preliminary action through advance resource allocation and pre-configured retransmission parameters. The gNB schedules resources in advance and configures fallback retransmission behavior before actual transmission occurs, allowing the system to handle failures efficiently without increasing operational complexity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If retransmission strategies with thresholds are implemented, then data integrity is improved, but latency increases due to additional processing and waiting

Engineering Contradiction:
Improvedata integrityVSAvoidtransmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent utilizes parameter changes by configuring thresholds (such as BLER thresholds) that determine when retransmission should occur. By dynamically adjusting these parameters based on channel conditions and transmission history, the system optimizes the balance between data integrity and latency, avoiding unnecessary retransmissions while ensuring reliable delivery when needed.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent applies partial action by implementing retransmission only when necessary, based on threshold violations or feedback indications. Rather than always attempting retransmission, the system uses partial retransmission strategies that activate only when data integrity is compromised, thereby minimizing latency while maintaining reliability.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If proactive retransmission configuration is implemented, then service disruption is reduced, but system overhead and processing requirements increase

Engineering Contradiction:
Improveservice continuityVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action through advance resource allocation and pre-configured retransmission parameters. The gNB schedules resources in advance and configures fallback retransmission behavior before actual transmission occurs, allowing the system to handle failures efficiently without increasing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies self-service by enabling UEs to autonomously determine when retransmission is needed based on received feedback and configured thresholds. The receiving UE independently evaluates transmission success and sends appropriate acknowledgment signals, reducing the processing burden on the network while maintaining service continuity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11876628B2Fallback retransmission in sidelink
Publication Date: 2024.01.16 QUALCOMM INC
  • US11876628B2 patent drawing
  • US11876628B2 patent drawing
  • US11876628B2 patent drawing

AI summary

Certain aspects of the present disclosure provide techniques for a fallback retransmission for a sidelink. A method that may be performed by a user equipment (UE) includes monitoring a transmission from a node. The UE can determine that the transmission was not successfully decoded. The UE can send a feedback message to the node indicating that the transmission was not successfully decoded. The feedback message can also include an indication of whether the node or a base station (BS) retransmits the transmission. The node retransmits the transmission or indicates to the BS to retransmit based on the feedback message. The BS can configure the node, the UE, or both with one or more thresholds for determining whether the node or the BS retransmits the transmission.