Channel State Information Determination via Worst-Case Code Block Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mobile communication networks like LTE, existing feedback reporting methods are too optimistic due to uneven interference levels among code blocks, leading to increased block error rates and suboptimum throughput, especially in heterogeneous networks where some code blocks face higher interference.

Innovation Solution

The method determines channel state information based on a worst-case code block, grouping resource elements by interference levels and using weighted metric combining to calculate feedback metrics, which considers the impact of uneven interference levels among sub-blocks, providing more accurate feedback reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If feedback reporting methods consider overall TB signal quality, then the feedback is simpler to compute, but the feedback becomes too optimistic leading to increased block error rates

Engineering Contradiction:
Improvefeedback computation simplicityVSAvoidblock error rate
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The transport block is divided into multiple code blocks, and the feedback computation is segmented to evaluate each code block's interference level separately. This allows identification of the worst-case code block without computing overall TB quality, maintaining simplicity while improving accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of evaluating overall TB signal quality uniformly, the method applies local quality assessment by examining interference levels at specific code block level. This local evaluation identifies the worst-case code block and provides more accurate feedback for heterogeneous interference scenarios.

Inventive Principle:
Principle #3Local quality

2Reliability

If feedback reporting methods account for uneven interference levels among code blocks, then block error rates are reduced, but the computation complexity increases

Engineering Contradiction:
Improveblock error rateVSAvoidfeedback computation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The method performs partial action by evaluating only the necessary code blocks to identify the worst-case scenario, rather than computing detailed metrics for all code blocks. This reduces computation complexity while still capturing the essential interference variation among code blocks.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The method performs preliminary action by identifying the worst-case code block before final feedback computation. This preliminary identification simplifies subsequent feedback generation, as the system only needs to compute detailed metrics for the identified worst-case code block rather than all code blocks.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the system uses worst-case code block based feedback, then throughput is improved through accurate feedback, but the processing requirements increase

Engineering Contradiction:
ImprovethroughputVSAvoidprocessing power
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The method applies partial action by computing detailed interference metrics only for the worst-case code block identified through preliminary screening, rather than processing all code blocks equally. This reduces processing power requirements while maintaining the accuracy benefits of code-block-level analysis.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The method extracts and focuses computational resources on the critical worst-case code block that determines overall TB performance. By taking out this specific code block for detailed analysis and using its characteristics for feedback generation, the system achieves accurate throughput optimization without processing the entire transport block in detail.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10567059B2Method and device for determining channel state information
Publication Date: 2020.02.18 INTEL CORP
  • US10567059B2 patent drawing
  • US10567059B2 patent drawing
  • US10567059B2 patent drawing

AI summary

A method (300) for determining channel state information includes: receiving (301) a downlink signal, wherein the downlink signal comprises a transport block comprising a plurality of code blocks, each code block of the plurality of code blocks comprising a plurality of resource elements; determining (302) a worst case code block of the plurality of code blocks based on at least one of noise or interference experienced by the plurality of resource elements of the respective code blocks; and determining (303) a metric indicative of a channel state information based on the worst case code block.