UE MAC LBT Failure Detection for Reliable Uplink Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for an improved mechanism for a UE to handle Listen-Before-Talk (LBT) failures in the physical layer of next-generation wireless communication networks, particularly in unlicensed spectra, to ensure efficient channel access and transmission.

Innovation Solution

A UE is equipped with a Medium Access Control (MAC) entity that receives LBT failure indications, increments an LBT failure counter, determines an LBT failure event when the counter reaches a threshold, and resets the counter after a time period, indicating the failure to upper layers for appropriate action.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If LBT failure detection mechanism is implemented, then reliability of uplink transmission is improved, but device complexity increases

Engineering Contradiction:
Improveuplink transmission reliabilityVSAvoidMAC entity complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The LBT failure detection mechanism is segmented into distinct functional components: an LBT failure counter for tracking failures, a threshold comparison unit for determining failure events, and a reset mechanism for recovery. This segmentation allows each component to perform its specific function independently, improving reliability without overwhelming the MAC entity with monolithic complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by maintaining a failure counter and comparing it against a threshold before declaring an LBT failure event. This preliminary detection mechanism enables early identification of transmission issues, allowing the system to take preventive actions or switch to alternative transmission methods before complete failure occurs, thereby improving uplink transmission reliability.

Inventive Principle:
Principle #10Preliminary action

2Speed

If LBT failure counter threshold is set low, then responsiveness to failures is improved, but false alarm rate increases

Engineering Contradiction:
Improvefailure detection speedVSAvoiddetection accuracy
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system allows dynamic adjustment of the threshold parameter based on network conditions and service requirements. By changing the threshold parameter, the system can optimize between rapid failure detection (lower threshold) and reduced false alarms (higher threshold), enabling flexible adaptation to different operational scenarios while maintaining both responsiveness and accuracy.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If LBT failure counter is reset frequently, then system recovery is improved, but loss of failure information occurs

Engineering Contradiction:
Improvesystem recovery speedVSAvoidfailure history information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The reset mechanism incorporates feedback by monitoring the failure counter and resetting it only when specific recovery conditions are met. This feedback-based approach ensures that the counter is reset at appropriate moments when the system has actually recovered from failures, rather than arbitrarily. The feedback loop maintains productivity by enabling timely recovery while preserving failure information until genuine recovery occurs, preventing premature loss of diagnostic data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12408193B2Method and apparatus for LBT failure detection
Publication Date: 2025.09.02 HANNIBAL IP LLC
  • US12408193B2 patent drawing
  • US12408193B2 patent drawing
  • US12408193B2 patent drawing

AI summary

A method for LBT failure detection performed by a UE is provided. The method includes: receiving, by a MAC entity of the UE, an LBT failure indication from a lower layer for all UL transmissions; increasing an LBT failure counter when the MAC entity receives the LBT failure indication; determining an LBT failure event occurs when the LBT failure counter is greater than or equal to a threshold; and resetting the LBT failure counter after the MAC entity has not received the LBT failure indication for a time period.