Listen-Before-Talk Channel Access Priority Class Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Listen-Before-Talk (LBT) procedures in wireless communication networks often result in unnecessary, inconsistent, and incompatible delays due to defaulting to a lowest priority Channel Access Priority Class (CAPC) for transmissions that do not include User Plane data payloads, leading to unfavorable mismatches between CAPC and payload priority.

Innovation Solution

Implementing a method that selects a channel access priority class (CAPC) based on the type of transmission payload, using a mapping that associates different types of payloads with respective CAPCs, ensuring that the selected CAPC is higher than the lowest priority CAPC, thereby optimizing channel access procedures for various types of transmissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a lowest priority Channel Access Priority Class (CAPC) is defaulted for transmissions without User Plane data payloads, then the LBT procedure is simplified and consistent, but unnecessary delays occur and channel access efficiency deteriorates

Engineering Contradiction:
ImproveLBT procedure consistencyVSAvoidchannel access delay
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies local quality by assigning different CAPC values to different transmission payload types. Instead of using a uniform lowest priority CAPC for all transmissions, the system selectively assigns appropriate priority levels based on the specific payload characteristics, thereby optimizing channel access delay for each transmission type while maintaining procedural consistency through defined mapping rules.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the CAPC parameter dynamically based on the transmission payload type. By establishing a mapping relationship between payload types and corresponding CAPC values, the system adjusts the channel access priority parameter to match the actual transmission requirements, reducing unnecessary delays while maintaining operational consistency through standardized mapping procedures.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If a lowest priority CAPC is used for all transmissions including control plane messages and random access preambles, then the channel access procedure is standardized, but the priority mismatch between CAPC and payload importance increases

Engineering Contradiction:
Improvechannel access procedure standardizationVSAvoidpriority alignment accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements local quality by tailoring the CAPC assignment to the specific characteristics of each transmission payload type. Control plane messages, random access preambles, and other non-user plane transmissions are assigned appropriate priority levels through a defined mapping relationship, ensuring that the channel access priority reflects the actual importance and urgency of each transmission type.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces dynamics into the previously static CAPC assignment by making the priority level adaptive to the transmission payload type. The mapping mechanism enables the system to dynamically select appropriate CAPC values based on the specific transmission requirements, thereby improving priority alignment accuracy while maintaining procedural standardization through consistent mapping rules.

Inventive Principle:
Principle #15Dynamics

3Productivity

If different CAPCs are selected based on transmission payload types, then channel access efficiency and priority alignment improve, but the complexity of CAPC selection and mapping increases

Engineering Contradiction:
Improvechannel access efficiencyVSAvoidCAPC selection complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing a mapping relationship between transmission payload types and corresponding CAPC values. This mapping table or configuration is prepared in advance, allowing the system to quickly determine the appropriate CAPC based on the payload type without requiring complex real-time decision-making, thereby improving channel access efficiency while minimizing selection complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that bridges the gap between transmission payload types and CAPC values. This mapping layer acts as a simplified interface that translates payload characteristics into appropriate priority levels, reducing the complexity of direct CAPC selection while improving overall channel access efficiency through systematic priority assignment.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12185374B2Enhanced listen-before-talk
Publication Date: 2024.12.31 GOOGLE LLC
  • US12185374B2 patent drawing
  • US12185374B2 patent drawing
  • US12185374B2 patent drawing

AI summary

An enhanced LBT procedure (200) mitigates unnecessary delays in delivering transmissions between User Equipment and base stations over unlicensed spectrum. A UE or base station selects a particular CAPC corresponding to an intended transmission (225) based on an intelligent mapping of different types of transmission payload (e.g., transmission payload other than or in in addition to pre-defined, QoS-related UP message data payload) to different CAPCs. Most (if not all) of the mapped CAPCs corresponding to the different types of transmission payload are of a higher priority than a lowest priority CAPC (212-222), resulting in channel access procedures that are more commensurate with respective transmission payloads. The intelligent mapping may indicate different priorities among different types of transmission payload and/or different types of messages, and/or may indicate which type of transmission is to govern selection of a CAPC when multiple types of transmission payload are included in a single, intended transmission.