Uplink Control Information Transmission via Service-Specific PUSCH Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for transmitting uplink control information (UCI) in wireless communication technologies fail to meet the different reliability requirements of Ultra Reliable Low Latency Communication (URLLC) and Enhance Mobile Broadband (eMBB) services, as they use the same UCI piggyback rules for both services.

Innovation Solution

The method involves configuring different Physical Uplink Shared Channel (PUSCH) parameters for different types of UCI, allowing the terminal to transmit UCI based on specific PUSCH configuration parameters that match the reliability requirements of each service type, including setting state parameters, scaling parameters, and beta-offsets to manage Resource Elements (REs) and code rate adjustments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the same UCI piggyback rules are used for both URLLC and eMBB services, then the device complexity is reduced, but the reliability requirement of URLLC service cannot be met

Engineering Contradiction:
Improvereliability requirementVSAvoidUCI piggyback configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by configuring different PUSCH parameters (such as beta-offset, scaling factor, and resource element allocation) specifically for URLLC service UCI transmissions. This allows the system to provide enhanced reliability for critical URLLC control information while maintaining simpler configuration for eMBB service, thus resolving the contradiction between reliability requirements and device complexity.

Inventive Principle:
Principle #3Local quality

2Reliability

If different PUSCH configuration parameters are configured for different service types, then the reliability requirement of URLLC service is met, but the device complexity increases

Engineering Contradiction:
Improvereliability requirementVSAvoidPUSCH configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the PUSCH configuration into service-type-specific parameters, allowing independent optimization for URLLC and eMBB services. By dividing the configuration into distinct segments (URLLC-specific parameters vs. eMBB parameters), the system can meet the high reliability requirements of URLLC without unnecessarily complicating the entire UCI transmission system.

Inventive Principle:
Principle #1Segmentation

3Reliability

If UCI is transmitted on PUSCH with standard piggyback rules, then the ease of operation is maintained, but the loss of information occurs for URLLC service

Engineering Contradiction:
Improveinformation transmission reliabilityVSAvoidUCI transmission operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent changes key transmission parameters (beta-offset value, scaling factor, resource element mapping) when transmitting UCI for URLLC service on PUSCH. These parameter modifications ensure that critical URLLC control information receives enhanced protection and prioritization, preventing information loss while maintaining the overall simplicity of the piggyback transmission mechanism.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3820220B1Transmission method and device for uplink control information and computer storage medium
Publication Date: 2023.09.27 CHINA MOBILE COMM GRP CO LTD
  • EP3820220B1 patent drawingFigure 1~3
  • EP3820220B1 patent drawingFigure 4~5
  • EP3820220B1 patent drawing

AI summary

Disclosed are a transmission method and device for uplink control information and a computer storage medium. The method comprises: a terminal, according to the type of physical uplink shared channel (PUSCH) and/or the type of uplink control information, selecting a corresponding first PUSCH configuration parameter, and the terminal transmitting the uplink control information on the basis of the first PUSCH configuration parameter, wherein different PUSCH configuration parameters correspond to PUSCH of different types and/or uplink control information of different types.