A method and apparatus for transmitting uplink control information

By adjusting the temporal position relationship between PUCCH and PUSCH, uplink control information is transmitted through PUSCH, which solves the problem of high uplink transmission power consumption in 5G terminal devices and achieves power optimization and improved transmission efficiency.

CN114828238BActive Publication Date: 2025-10-17HUAWEI TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202110281553.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-01-19
Filing Date
2021-03-16
Publication Date
2025-10-17
Estimated Expiration
2041-03-16

AI Technical Summary

Technical Problem

Existing 5G terminal devices consume a lot of power during uplink transmission and have not been effectively optimized.

Method used

By adjusting the temporal positional relationship between the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH), the transmission of uplink control information is optimized, including transmitting uplink control information through the PUSCH, thereby reducing the number of transmissions and power consumption.

Benefits of technology

This reduces the power consumption of terminal devices, decreases the number of uplink transmissions, and improves transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114828238B_ABST
    Figure CN114828238B_ABST
Patent Text Reader

Abstract

A method and device for transmitting uplink control information are provided for a communication system, such as V2X, LTE-V, V2V, Internet of Vehicles, MTC, IoT, LTE-M, M2M, Internet of Things, etc. When the time domain length between the time domain position of DCI and the time domain position of PUSCH is greater than or equal to a first time domain length; or the time domain length between the time domain position of PUSCH and the time domain position of PDSCH corresponding to the uplink control information is greater than or equal to the first time domain length; or the time domain length between the time domain position of PUSCH and the time domain position of CSI-RS corresponding to the uplink control information is greater than or equal to a second time domain length; or the time domain length between the time domain position of PUCCH and the time domain position of PUSCH is less than or equal to a third time domain length, the terminal device transmits the uplink control information to the network device through the PUSCH.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority from the Chinese patent application No. 202110069446.X filed on January 19, 2021 and entitled "A method of new single carrier / cell configuration", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a method and apparatus for transmitting uplink control information. BACKGROUND

[0003] A terminal device supporting the 5th Generation new radio access technology (5G NR) generally needs to support a larger bandwidth (for example, 100 megahertz (MHz) or the like), a larger number of antennas (for example, 4 reception (RX) antennas and 2 transmission (TX) antennas or the like), and a more complex baseband processing procedure (for example, polar code or the like), which will result in higher power consumption of the terminal device. At present, in order to reduce the power consumption of the terminal device, more and more researches on power consumption saving of the terminal device are carried out. However, in the current research, the downlink transmission of the terminal device is mainly optimized, and the uplink transmission is not optimized. SUMMARY

[0004] The present application provides a method and apparatus for transmitting uplink control information, which is used to optimize the transmission of uplink control information to save the power consumption of the terminal device.

[0005] In a first aspect, the present application provides a method for transmitting uplink control information, which can include: when the relationship between the time domain position of a physical uplink control channel (PUCCH) containing uplink control information and the time domain position of a physical uplink shared channel (PUSCH) can satisfy:

[0006] The first condition can include that a time domain position of the PUCCH is between a time domain position of a downlink control information (DCI) and a time domain position of the PUSCH, wherein the DCI is used for scheduling transmission of the PUSCH, and the uplink control information includes one or more of a hybrid automatic repeat request (HARQ) feedback, a periodic channel state information (P-CSI) report, or a semi-persistent CSI (SP-CSI) report; or

[0007] The time domain position of the PUSCH is before the time domain position of the PUCCH, and a time domain length between a time domain position of a physical downlink shared channel (PDSCH) corresponding to the uplink control information and the time domain position of the PUSCH is greater than or equal to a first time domain length, wherein the uplink control information includes the HARQ feedback; or

[0008] The time domain position of the PUSCH is before the time domain position of the PUCCH, and a time domain length between a time domain position of a CSI reference signal (RS) (CSI-RS) corresponding to the uplink control information and the time domain position of the PUSCH is greater than or equal to a second time domain length, wherein the uplink control information includes the P-CSI report or the SP-CSI report; or

[0009] The time domain position of the PUCCH is before the time domain position of the PUSCH, and a time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to a third time domain length, wherein the uplink control information includes one or more of the HARQ feedback, the P-CSI report, or the SP-CSI report.

[0010] Afterwards, the terminal device can transmit the uplink control information to the network device through the PUSCH.

[0011] Through the above method, by transmitting the uplink control information through the PUSCH, the number of uplink transmissions can be reduced, and thus the power consumption of the terminal device can be reduced.

[0012] In one possible design, the first condition can further include that a time domain length between the time domain position of the DCI and the time domain position of the PUCCH can be greater than or equal to a fourth time domain length. In this way, it can be ensured that the terminal device has sufficient time to complete DCI decoding, so that the terminal device knows whether there is a subsequent PUSCH scheduling.

[0013] In one possible design, the fourth time-domain length can be a current minimum scheduling time interval.

[0014] In one possible design, the first condition can further include that a time-domain length between a time-domain location of the PUCCH and a time-domain location of the PUSCH can be less than or equal to a fifth time-domain length. This can reduce a transmission latency of the uplink control information.

[0015] In one possible design, the first condition can further include that, when the uplink control information contains a P-CSI report or an SP-CSI report, and the DCI triggers an aperiodic channel state information (AP-CSI) report, a report content of the P-CSI report or the SP-CSI report contained in the uplink control information can be different from a report content of the AP-CSI report contained in the PUSCH. This can avoid repeated transmission of CSI reports with the same effect.

[0016] In one possible design, when the uplink control information contains a P-CSI report or an SP-CSI report, and the DCI triggers an aperiodic channel state information (AP-CSI) report, and a report content of the P-CSI report or the SP-CSI report contained in the uplink control information is partially or totally the same as a report content of the AP-CSI report contained in the PUSCH, the terminal device discards the uplink control information, i.e., does not transmit the uplink control information. This can avoid repeated transmission of CSI reports with the same effect.

[0017] In one possible design, the report content (reportQuantity) is configured by the network device for the terminal device, and the report content is used to identify a type of channel state information included in a current CSI report.

[0018] In one possible design, the terminal device transmits the uplink control information to the network device through the PUSCH, which can specifically include: the terminal device concatenates the uplink control information and information contained in the PUSCH at a bit level to obtain first information; and then the terminal device transmits the first information to the network device through the PUSCH. This can successfully transmit the uplink control information to the network device through the PUSCH, and can reduce a number of times of uplink transmission and reduce power consumption of the terminal device.

[0019] In a possible design, the terminal device transmits the uplink control information to the network device through the PUSCH, which can be implemented as follows: the terminal device punctures the PUSCH, maps the uplink control information to a position where the PUSCH is punctured, to obtain second information; and then the terminal device transmits the second information to the network device through the PUSCH. In this way, the terminal device can successfully transmit the uplink control information to the network device through the PUSCH, and the number of uplink transmissions can be reduced, and the power consumption of the terminal device can be reduced.

[0020] In a possible design, the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to a sixth time domain length, or the terminal device transmits the uplink control information through the information bit concatenation method in a case where the number of information bits of the uplink control information is greater than or equal to a first value. In this way, the terminal device can successfully transmit the uplink control information to the network device through the PUSCH.

[0021] In a possible design, the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than the sixth time domain length, or the terminal device transmits the uplink control information through the puncturing method in a case where the number of information bits of the uplink control information is less than the first value. In this way, the terminal device can successfully transmit the uplink control information to the network device through the PUSCH.

[0022] In a possible design, when the relationship between the time domain position of the PUCCH containing the uplink control information and the time domain position of the PUSCH satisfies the first condition or the time domain position of the PUCCH is before the time domain position of the PUSCH, and the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to a third time domain length, the terminal device can determine whether to transmit the uplink control information through the information bit concatenation method or through the puncturing method according to the size relationship between the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH and the sixth time domain length.

[0023] In a possible design, the terminal device receives a first message from the network device, where the first message is used to configure or enable the function of transmitting the uplink control information through the PUSCH. In this way, the terminal device can transmit the uplink control information to the network device through the PUSCH.

[0024] In one possible design, the terminal device sends a second message to the network device, where the second message is used to request enabling the function of transmitting the uplink control information via the PUSCH. This can enable the terminal device to transmit the uplink control information to the network device via the PUSCH.

[0025] In one possible design, the terminal device receives a third message from the network device, where the third message is used to instruct the terminal device to transmit the uplink control information via the PUSCH. This can enable the terminal device to transmit the uplink control information to the network device via the PUSCH.

[0026] In one possible design, before the terminal device transmits the uplink control information to the network device via the PUSCH, the terminal device determines that a reference signal received power (RSRP) sent to the network device after receiving a reference signal from the network device can be greater than an RSRP threshold, where the RSRP is determined by the terminal device based on the reference signal. This can ensure the transmission performance of the terminal device.

[0027] In one possible design, the terminal device transmits the uplink control information to the network device via the PUSCH, which can include that the terminal device transmits the uplink control information to the network device via the PUSCH with a first transmit power, where the first transmit power is greater than an original transmit power of the PUSCH, or the first transmit power is determined based on the original transmit power of the PUSCH and an original transmit power of the PUCCH. This can improve the energy allocated to each bit on average, thereby ensuring the transmission performance of the terminal device.

[0028] In one possible design, the number of information bits of the uplink control information can be less than or equal to a second value. The second value can be predefined or configured by the network device. This can ensure that the terminal device successfully transmits the uplink control information to the network device via the PUSCH.

[0029] In one possible design, the terminal device transmits the uplink control information to the network device via the PUSCH, which can include that the terminal device determines K bits in the uplink control information in a descending order of priority, where the number of information bits of the uplink control information is greater than M, and K is less than or equal to M; and the terminal device transmits the K bits to the network device via the PUSCH. This can ensure that the terminal device successfully transmits the uplink control information to the network device via the PUSCH.

[0030] In a possible design, the first time domain length can satisfy the following formula:

[0031] First time domain length = (N1+d 1,1 +d2)(2048+144)·κ2 -μ ·T C

[0032] where N1 is the processing capability reported by the terminal device, and is related to a subcarrier spacing (SCS) or a system parameter; d 1,1 and d2 are related to a PDSCH mapping type and a length of symbols occupied by the PDSCH; μ is a system parameter; T c =1 / (Δf max ·N f ), where Δf max =480·10 3 Hz, N f =4096; κ = T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), and Δf ref =15·10 3 Hz.

[0033] In a possible design, the second time domain length can satisfy the following formula:

[0034] Second time domain length = (Z)(2048+144)·κ2 -μ ·T C

[0035] where Z is a predefined value; T c =1 / (Δf max ·N f ), where Δf max =480·103Hz, N f =4096; κ = T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), and Δf ref =15·10 3 Hz.

[0036] In a second aspect, the present application provides a method for transmitting uplink control information, which can include: when a relationship between a time domain position of a PUCCH containing uplink control information and a time domain position of a PUSCH can satisfy:

[0037] a first condition, the first condition can comprise that a time domain position of the PUCCH is between a time domain position of a downlink control information (DCI) and a time domain position of the PUSCH, wherein the DCI is used for scheduling transmission of the PUSCH, wherein the uplink control information comprises one or more of a HARQ feedback, a P-CSI report, or a SP-CSI report; or,

[0038] the time domain position of the PUSCH is before the time domain position of the PUCCH, and a time domain length between a time domain position of a PDSCH corresponding to the uplink control information and the time domain position of the PUSCH is greater than or equal to a first time domain length, wherein the uplink control information comprises the HARQ feedback; or,

[0039] the time domain position of the PUSCH is before the time domain position of the PUCCH, and a time domain length between a time domain position of a CSI-RS corresponding to the uplink control information and the time domain position of the PUSCH is greater than or equal to a second time domain length, wherein the uplink control information comprises the P-CSI report and / or the SP-CSI report; or,

[0040] the time domain position of the PUCCH is before the time domain position of the PUSCH, and a time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to a third time domain length, wherein the uplink control information comprises one or more of a HARQ feedback, a P-CSI report, or a SP-CSI report;

[0041] Afterwards, the network device can receive the uplink control information transmitted by the terminal device through the PUSCH.

[0042] By the above method, by transmitting the uplink control information through the PUSCH, the number of uplink transmissions can be reduced, and thus the power consumption of the terminal device can be reduced.

[0043] In one possible design, the first condition can further comprise that a time domain length between the time domain position of the DCI and the time domain position of the PUCCH can be greater than or equal to a fourth time domain length. In this way, it can be ensured that the terminal device has enough time to complete DCI decoding, so that the terminal device knows whether there is a subsequent PUSCH scheduling.

[0044] In one possible design, the fourth time domain length is a current minimum scheduling slot interval.

[0045] In one possible design, the first condition can further include that a time domain length between a time domain location of the PUCCH and a time domain location of the PUSCH can be less than or equal to a fifth time domain length. This can reduce a transmission latency of the uplink control information.

[0046] In one possible design, the first condition can further include that when the UCI contains a P-CSI report or an SP-CSI report and the DCI triggers an AP-CSI report, a report content of the P-CSI report or the SP-CSI report contained by the UCI can be different from a report content of the AP-CSI report contained by the PUSCH. This can avoid repeated transmission of CSI reports of the same effect.

[0047] In one possible design, when the uplink control information contains a P-CSI report or an SP-CSI report, the DCI triggers an aperiodic channel state information AP-CSI report, and a report content of the P-CSI report or the SP-CSI report contained by the uplink control information is partially or totally the same as a report content of the AP-CSI report contained by the PUSCH, the network device does not receive the uplink control information. This can avoid repeated transmission of CSI reports of the same effect.

[0048] In one possible design, the report content (reportQuantity) is configured by the network device for the terminal device, and the report content is used to identify a type of channel state information included in a current CSI report.

[0049] In one possible design, the network device receives the uplink control information transmitted by the terminal device through the PUSCH, and specifically, the network device can receive first information transmitted by the terminal device through the PUSCH, where the first information is obtained by performing bit concatenation on the uplink control information and information contained in the PUSCH by the terminal device. In this way, the network device can successfully receive the uplink control information transmitted by the terminal device through the PUSCH, and the number of uplink transmissions can be reduced, and the power consumption of the terminal device can be reduced.

[0050] In one possible design, the network device receives the uplink control information transmitted by the terminal device through the PUSCH, and specifically, the network device can receive second information transmitted by the terminal device through the PUSCH, where the second information is obtained by puncturing the PUSCH by the terminal device and mapping the uplink control information to a position of the PUSCH that is punctured. In this way, the network device can successfully receive the uplink control information transmitted by the terminal device through the PUSCH, and the number of uplink transmissions can be reduced, and the power consumption of the terminal device can be reduced.

[0051] In one possible design, a time domain length between a time domain location of the PUCCH and a time domain location of the PUSCH is greater than or equal to a sixth time domain length; or, in a case where a number of information bits of the uplink control information is greater than or equal to a first value, the uplink control information is transmitted by an information bit concatenation method. This can enable the network device to successfully receive the uplink control information transmitted by the PUSCH.

[0052] In one possible design, a time domain length between a time domain location of the PUCCH and a time domain location of the PUSCH is less than the sixth time domain length; or, in a case where a number of information bits of the uplink control information is less than the first value, the uplink control information is transmitted by a puncturing method. This can enable the network device to successfully receive the uplink control information transmitted by the PUSCH.

[0053] In one possible design, when a relationship between a time domain location of a PUCCH containing uplink control information and a time domain location of a PUSCH satisfies: the first condition or the time domain location of the PUCCH is before the time domain location of the PUSCH, and a time domain length between the time domain location of the PUCCH and the time domain location of the PUSCH is less than or equal to a third time domain length, the network device can determine, according to a size relationship between the time domain length between the time domain location of the PUCCH and the time domain location of the PUSCH and a sixth time domain length, whether the terminal device transmits the uplink control information by the information bit concatenation method or by the puncturing method.

[0054] In one possible design, the network device sends a first message to the terminal device, where the first message is used to configure or enable a function of the terminal device to transmit the uplink control information by the PUSCH. This can enable the network device to receive the uplink control information transmitted by the PUSCH.

[0055] In one possible design, the network device receives a second message from the terminal device, where the second message is used to request to enable the function of transmitting the uplink control information by the PUSCH. This can enable the network device to receive the uplink control information transmitted by the PUSCH.

[0056] In one possible design, the network device sends a third message to the terminal device, where the third message is used to instruct the terminal device to transmit the uplink control information by the PUSCH. This can enable the network device to receive the uplink control information transmitted by the PUSCH.

[0057] In a possible design, before the network device receives the uplink control information transmitted by the terminal device through the PUSCH, the network device determines that the RSRP from the terminal device is greater than an RSRP threshold, where the RSRP is sent by the terminal device after receiving a reference signal from the network device, and the RSRP is determined by the terminal device based on the reference signal. This can guarantee transmission performance.

[0058] In a possible design, the number of information bits of the uplink control information is less than or equal to a second value. The second value can be predefined or configured by the network device. This can guarantee that the network device can receive the uplink control information transmitted through the PUSCH.

[0059] In a possible design, the network device receives the uplink control information transmitted by the terminal device through the PUSCH, specifically, the network device receives K bits in the uplink control information transmitted by the terminal device through the PUSCH, where the K bits are the first K bits determined by the terminal device in descending order of priority of bits in the uplink control information; and the number of information bits of the uplink control information is greater than M, and K is less than or equal to M. This can guarantee that the network device successfully receives the uplink control information transmitted through the PUSCH.

[0060] In a possible design, the first time domain length can satisfy the following formula:

[0061] First time domain length = (N1+d 1,1 +d2)(2048+144)·κ2 -μ ·T C

[0062] where N1 is a processing capability reported by the terminal device, and the value is related to a subcarrier spacing (SCS) or a system parameter; d 1,1 and d2 are related to a PDSCH mapping type and a symbol length occupied by the PDSCH; μ is a system parameter; T c =1 / (Δf max ·N f ), where Δf max =480·10 3 Hz, N f =4096; κ = T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz.

[0063] In one possible design, the second time-domain length can satisfy the following equation:

[0064] Second time-domain length = (Z)(2048+144)·κ2 -μ ·T C

[0065] where Z is a predefined value; T c = 1 / (Δf max ·N f ), where Δf max = 480·10 3 Hz, N f = 4096; κ = T s / T c = 64, where T s = 1 / (Δf ref ·N f,ref ), Δf ref = 15·10 3 Hz.

[0066] In a third aspect, a communication apparatus is provided. The communication apparatus can be a terminal device. The communication apparatus has the functions of the terminal device in the above first aspect or various possible implementation forms of the first aspect. The functions can be implemented by hardware, or by hardware executing software. The hardware or software includes one or more modules corresponding to the functions.

[0067] In one possible design, the communication apparatus can include a transceiver and a processing unit. The transceiver and the processing unit can perform the functions of the terminal device in the above first aspect or various possible implementation forms of the first aspect. Details can be referred to the description of the method examples, which are not repeated here.

[0068] In one possible design, the communication apparatus can include a transceiver and a processing unit. The transceiver and the processing unit can perform the functions of the terminal device in the above first aspect or various possible implementation forms of the first aspect. Details can be referred to the description of the method examples, which are not repeated here.

[0069] In a fourth aspect, the present application provides a communication apparatus, which can be a network device. The communication apparatus has the functions of the network device in the second aspect or various possible implementation forms of the second aspect. The functions can be implemented by hardware, or by hardware in cooperation with software. The hardware or software includes one or more modules corresponding to the functions as described above.

[0070] In a possible design, the communication apparatus can include a transceiver and a processing unit. The transceiver and the processing unit can perform the corresponding functions of the network device in the second aspect or various possible implementation forms of the second aspect. For details, refer to the description of the method examples, which are not repeated here.

[0071] In a possible design, the communication apparatus can include a transceiver and a processor, and optionally a memory. The transceiver can be configured to receive and send data or information, and to perform communication interaction with other devices in a communication system. The processor can be configured to support the communication apparatus to perform the corresponding functions of the network device in the second aspect or various possible implementation forms of the second aspect. The memory is coupled to the processor, and stores program instructions and data necessary for the communication apparatus.

[0072] In a fifth aspect, the embodiments of the present application provide a communication system, which can include the terminal device and the network device as described above.

[0073] In a sixth aspect, the embodiments of the present application provide a computer-readable storage medium, which stores program instructions. When the program instructions are run on a computer, the computer is enabled to perform the method in the first aspect or various possible implementation forms of the first aspect, or the method in the second aspect or various possible implementation forms of the second aspect. Exemplarily, the computer-readable storage medium can be any available medium that can be accessed by a computer. For example, but not limited to: the computer-readable medium can include a non-transitory computer-readable medium, a random-access memory (RAM), a read-only memory (ROM), an electrically EPROM (EEPROM), a CD-ROM or other optical disk storage, a magnetic disk storage medium or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0074] In a seventh aspect, an embodiment of the present application provides a computer program product including computer program code or instructions, which, when executed on a computer, cause the computer to implement the method of the above first aspect or each possible design example of the first aspect or the above second aspect or each possible design example of the second aspect.

[0075] In an eighth aspect, the present application also provides a chip coupled with a memory, for reading and executing program instructions stored in the memory to implement the method of the above first aspect or each possible design example of the first aspect or the above second aspect or each possible design example of the second aspect.

[0076] The above-mentioned various aspects of the third aspect to the eighth aspect and the technical effects that can be achieved by the various aspects are described above in the technical effects that can be achieved by the various possible schemes of the first aspect or the second aspect, and will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0077] Figure 1 A schematic diagram of a communication system architecture is provided for the present application;

[0078] Figure 2 A flowchart of an uplink control information transmission method is provided for the present application;

[0079] Figure 3 A schematic diagram of uplink control information transmission is provided for the present application;

[0080] Figure 4 Another schematic diagram of uplink control information transmission is provided for the present application;

[0081] Figure 5 Another schematic diagram of uplink control information transmission is provided for the present application;

[0082] Figure 6 Another schematic diagram of uplink control information transmission is provided for the present application;

[0083] Figure 7 Another schematic diagram of uplink control information transmission is provided for the present application;

[0084] Figure 8 Another schematic diagram of uplink control information transmission is provided for the present application;

[0085] Figure 9 Another schematic diagram of uplink control information transmission is provided for the present application;

[0086] Figure 10 A flowchart of uplink control information transmission is provided for the present application;

[0087] Figure 11 Another flow diagram of uplink control information transmission provided for the present application;

[0088] Figure 12 Another flow diagram of uplink control information transmission provided for the present application;

[0089] Figure 13 Another flow diagram of uplink control information transmission provided for the present application;

[0090] Figure 14 Another flow diagram of uplink control information transmission provided for the present application;

[0091] Figure 15 Another flow diagram of uplink control information transmission provided for the present application;

[0092] Figure 16 Another flow diagram of uplink control information transmission provided for the present application;

[0093] Figure 17 Another flow diagram of uplink control information transmission provided for the present application;

[0094] Figure 18 Another flow diagram of uplink control information transmission provided for the present application;

[0095] Figure 19 Another flow diagram of uplink control information transmission provided for the present application;

[0096] Figure 20 Another flow diagram of uplink control information transmission provided for the present application;

[0097] Figure 21 Another flow diagram of uplink control information transmission provided for the present application;

[0098] Figure 22 Another flow diagram of uplink control information transmission provided for the present application;

[0099] Figure 23 Another flow diagram of uplink control information transmission provided for the present application;

[0100] Figure 24 Another flow diagram of uplink control information transmission provided for the present application;

[0101] Figure 25 Another flow diagram of uplink control information transmission provided for the present application;

[0102] Figure 26 Another flow diagram of uplink control information transmission provided for the present application;

[0103] Figure 27Another UCI transmission diagram provided by the present application;

[0104] Figure 28 A UCI transmission flow diagram provided by the present application;

[0105] Figure 29 Another UCI transmission flow diagram provided by the present application;

[0106] Figure 30 Another UCI transmission flow diagram provided by the present application;

[0107] Figure 31 Another UCI transmission flow diagram provided by the present application;

[0108] Figure 32 A communication device structure diagram provided by the present application;

[0109] Figure 33 A communication device structure diagram provided by the present application. DETAILED DESCRIPTION

[0110] The present application will be further described in detail below with reference to the accompanying drawings.

[0111] The present application provides a kind of transmission method and device of uplink control information, to propose how to optimize the transmission of uplink control information, to save the power consumption of terminal equipment.Therein, the method and device described in the present application are based on the same technical concept, since the principle of method and device to solve problem is similar, therefore the implementation of device and method can be mutually referred to, and the place of repetition is not described repeatedly.

[0112] In the description of the present application, "first", "second", "third" and the like are only used for distinguishing the purpose of description, and cannot be understood as indicating or implying relative importance, and also cannot be understood as indicating or implying order. That is, first, second, third, …, N (N is one, two, three, four, …, etc.) in the present application is only used for distinguishing description, without the limitation of order, can not appear in order, that is, fourth, fifth, etc. can appear first, etc., and the present application does not limit this.

[0113] In the description of the present application, "at least one" refers to one or more, and more refers to two or more.

[0114] In order to more clearly describe the technical scheme of the embodiments of the present application, the transmission method and device of uplink control information provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0115] Figure 1 An architecture of a communication system to which embodiments of the present application are applicable is shown, which includes a network device and a terminal device.

[0116] The network device is a device with wireless transceiving function or a chip that can be disposed in the network device, and includes but is not limited to: a base station (generation node B, gNB), a radio network controller (RNC), a node B (Node B, NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB, or a home Node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (Wi-Fi) system, a wireless relay node, a wireless backhaul node, a transmission and reception point (TRP or transmission point, TP), etc., and can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0117] In some deployments, a gNB can include a centralized unit (CU) and a DU. A gNB can also include a radio unit (RU). The CU implements part of the functions of the gNB, and the DU implements part of the functions of the gNB, for example, the CU implements the functions of the radio resource control (RRC), the packet data convergence protocol (PDCP) layer, and the DU implements the functions of the radio link control (RLC), the media access control (MAC), and the physical (PHY) layer. Since the information of the RRC layer eventually becomes the information of the PHY layer, or is transformed from the information of the PHY layer, under this architecture, high-layer signaling, such as RRC layer signaling or PDCP layer signaling, can also be considered as being sent by the DU, or by the DU+RU. It can be understood that the network device can be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the core network CN, and no limitation is made in this regard.

[0118] The terminal device can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a smart wearable device (smart glasses, smart watch, smart earphone, etc.), a wireless terminal in smart home, etc., and can also be a chip or chip module (or chip system) that can be arranged in the above devices. The embodiments of the present application do not limit the application scenarios. The terminal device with wireless transceiver function and the chip that can be arranged in the terminal device are collectively referred to as a terminal device in the present application.

[0119] It should be noted that, Figure 1 The communication system shown can be but is not limited to a fourth generation (4th Generation, 4G) system, a fifth generation (5th Generation, 5G) system such as a new radio access technology (new radio access technology, NR), and optionally, the method of the embodiments of the present application is also applicable to various future communication systems, such as a sixth generation (6th Generation, 6G) system or other communication networks, etc.

[0120] The uplink transmission of NR and related processes can be as follows:

[0121] 1. Uplink data: transmitted in a physical uplink shared channel (physical uplink shared channel, PUSCH).

[0122] (1) The time-domain location of PUSCH transmission is usually indicated by the downlink control information (DCI) sent by the network device to the terminal device. Specifically, if the network device sends a DCI at slot n, the DCI indicates a K2 value, and the terminal device transmits PUSCH at slot n+K2. This PUSCH scheduled by DCI is generally referred to as dynamic data scheduling.

[0123] (2) Another transmission mode of PUSCH exists in the standard, which is the transmission mode of configured grant (CG). CG can be divided into two cases: in one case, the transmission parameters of PUSCH are configured to the terminal device by the radio resource control (RRC) signaling of the network device, and when the terminal device has uplink data to send, it is transmitted through the pre-configured PUSCH. In another case, part of the transmission parameters of PUSCH are configured by the RRC signaling of the network device, and the remaining transmission parameters are indicated by DCI. When the network device sends DCI to activate the transmission of PUSCH, the terminal device will perform periodic transmission according to the configured periodicity until the network device sends another DCI to stop the PUSCH transmission of the terminal device. Therefore, in the transmission mode of CG, there may be a case of "PUSCH without DCI".

[0124] 2. Hybrid automatic repeat request (HARQ) feedback: HARQ feedback is usually carried in PUCCH transmission, and the time-domain location of PUCCH carrying HARQ feedback can be indicated by DCI sent by the network device to the terminal device. Specifically, if the network device sends a DCI to schedule the transmission of downlink data at slot n, the DCI indicates a K0 value and a K1 value, and the terminal device receives the physical downlink shared channel (PDSCH) at slot n+K0, wherein the PDSCH contains downlink data, and the terminal device transmits the HARQ feedback corresponding to the PDSCH at slot n+K0+K1.

[0125] 3. Channel state information (CSI) report: After receiving the CSI reference signal (RS) (CSI-RS) sent by the network device, the terminal device sends a CSI report to the network device. CSI report can be divided into the following three categories:

[0126] (1) Periodic CSI report (P-CSI report): usually transmitted in PUCCH, once the network device configures the periodic CSI report for the terminal device, the terminal device will send the CSI report according to the configured period. That is, the time domain position of the periodic CSI report is semi-statically configured by RRC signaling.

[0127] (2) Semi-persistent CSI report (SP-CSI report): like the periodic CSI report, it is usually transmitted in PUCCH. But the difference from the periodic CSI report is that the semi-persistent CSI report needs to be activated again after being configured by the network device for the terminal device. After activation, its time domain position can be considered to be semi-statically configured by RRC signaling.

[0128] (3) Aperiodic CSI report (AP-CSI report): transmitted in PUSCH, triggered by DCI. Specifically, if the network device sends a DCI in slot n, the DCI can contain an aperiodic CSI trigger information in addition to the indication of K2 value. If the DCI contains the aperiodic CSI trigger information, the terminal device will carry the aperiodic CSI report in the scheduled PUSCH.

[0129] In order to save the power consumption of the terminal device in the present application, it is proposed that the above uplink transmission can be optimized for transmission. Specifically, the transmission method of uplink control information is described in detail in the present application. It should be noted that the uplink control information in 5G can be uplink control information (UCI); in future communication systems or networks, such as 6G, it can still be UCI, or it can have other names, which are not limited in the present application. In the present application, the uplink control information can contain one or more of HARQ feedback, P-CSI or SP-CSI.

[0130] It should be noted that the operations of the terminal device in the following embodiments can also be implemented by a processor in the terminal device, or a chip or chip system, or a functional module, etc. The operations of the network device can also be implemented by a processor in the network device, or a chip or chip system, or a functional module, etc.

[0131] Based on the above description, the transmission method of uplink control information provided by the embodiments of the present application is suitable for Figure 1 The communication system shown in FIG. 1. Referring to Figure 2As shown, the specific flow of the method can include:

[0132] Step 201: The terminal device determines that the time domain position of the PUCCH containing the uplink control information is between the time domain position of the DCI and the time domain position of the PUSCH, wherein the DCI is used for scheduling the transmission of the PUSCH.

[0133] The uplink control information can include one or more of HARQ feedback, P-CSI reporting, or SP-CSI reporting.

[0134] Step 202: The terminal device transmits the uplink control information to the network device through the PUSCH, that is, the network device receives the uplink control information transmitted by the terminal device through the PUSCH.

[0135] Specifically, the terminal device transmits the uplink control information to the network device through the PUSCH, that is, the terminal device transmits the uplink control information to the network device through the PUSCH together with the information in the PUSCH.

[0136] When the network device receives the uplink control information transmitted by the terminal device through the PUSCH, the network device also needs to determine that the time domain position of the PUCCH containing the uplink control information is between the time domain position of the DCI and the time domain position of the PUSCH.

[0137] Specifically, when the terminal device transmits the uplink control information to the network device through the PUSCH, the terminal device will not send the PUCCH again.

[0138] For example, when the method shown in Figure 2 is adopted, the transmission schematic of the uplink control information can be as shown in Figure 3 .

[0139] In the above method, the terminal device transmits the uplink control information to the network device through the PUSCH, which can only send the PUSCH without sending the PUCCH, that is, reducing two uplink transmissions to one uplink transmission, thereby reducing the power consumption of the terminal device.

[0140] Since the PUSCH is dynamically scheduled by the DCI, in order to ensure that the uplink control information can be combined into the PUSCH (i.e., to ensure that the uplink control information is transmitted through the PUSCH), the terminal device needs to be able to determine that there is a transmission of the PUSCH near the PUCCH, i.e., the terminal device determines that the time domain position of the PUCCH and the time domain position of the PUSCH satisfy step 201. If the time domain position of the DCI is located after the time domain position of the PUCCH, the terminal device cannot predict that there is a transmission of the PUSCH near the PUCCH. In order to ensure that the terminal device can send the uplink control information to the network device, the terminal device can only choose to send the uplink control information through the PUSCH. Therefore, the time domain position of the DCI needs to be located before the time domain position of the PUCCH.

[0141] In addition, if the time domain position of the DCI and the time domain position of the PUSCH scheduled by the DCI are both before the time domain position of the PUCCH, it means that the time domain position of the uplink control information transmission needs to be advanced from the time domain position of the PUCCH to the time domain position of the PUSCH, as shown in FIG. 2B. Figure 4 The terminal device needs a certain time to generate the uplink control information. For example, when the terminal device generates the HARQ feedback, the terminal device needs to decode and verify the downlink data, so as to determine whether the data is correctly transmitted to decide whether to generate an ACK or a NACK. For another example, when the terminal device generates the CSI report, the terminal device needs to receive the CSI-RS and process the received signal to generate the report. Therefore, if the uplink control information is transmitted in advance as shown in FIG. 2B, it may not be able to ensure that the terminal device has sufficient processing time to generate the uplink control information. Therefore, in general, the time domain position of the PUSCH needs to be located after the time domain position of the PUCCH. Figure 4

[0142] In an optional embodiment, the time domain length between the time domain position of the DCI and the time domain position of the PUCCH can be greater than or equal to a fourth time domain length.

[0143] Specifically, the time domain length between the end position of the time domain position of the DCI and the start position of the time domain position of the PUCCH can be greater than or equal to the fourth time domain length. For example, the fourth time domain length can be as shown in the uplink control information transmission schematic diagram shown in FIG. 2C. Figure 5

[0144] For example, the end position can be an end symbol, and the start position can be a start symbol, and the present application does not limit this. It should be noted that the end position and the start position mentioned in the following description are the same, and the following will not be described in detail.

[0145] ​​The fourth time domain length is to ensure that the terminal device has enough time to complete DCI decoding, so that the terminal device knows whether there is a PUSCH scheduling afterwards. If the time domain position of the DCI is close to the time domain position of the PUCCH, the terminal device may not have completed the DCI decoding and cannot know whether there is a PUSCH transmission near the PUCCH. In order to ensure that the uplink control information can be sent to the network device, the uplink control information can only be transmitted through the PUCCH. Therefore, in order to realize that the uplink control information can be transmitted through the PUSCH, the time domain position interval between the DCI and the PUCCH is ensured to satisfy the fourth time domain length limit.

[0146] In an example, the fourth time domain length can be one or more symbols, or one or more slots.

[0147] In another example, when the network device configures or indicates a minimum scheduling slot interval (minimum scheduling offset) for the terminal device, the fourth time domain length can be equal to the current effective K0 minimum value (K0min).

[0148] In a specific embodiment, the fourth time domain length can be predefined in the standard, can be configured by the network device to the terminal device, or can be determined by the terminal device and then reported to the network device.

[0149] In another optional implementation, the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH can be less than or equal to a fifth time domain length.

[0150] Specifically, the time domain length between the end position of the time domain position of the PUCCH and the start position of the time domain position of the PUSCH can be less than or equal to the fifth time domain length. For example, the fifth time domain length can be as shown in the transmission schematic diagram of the uplink control information as shown in the following figure. Figure 6

[0151] The fifth time domain length is to control the transmission delay of the uplink control information when the uplink control information is transmitted through the PUSCH. For example, the fifth time domain length can be the maximum value of the additional transmission delay of the uplink control information transmission when the uplink control information is transmitted through the PUSCH. The purpose of the fifth time domain length is to avoid large uplink control information transmission delay. Because when the uplink control information is sent through the subsequent PUSCH, the sending time of the uplink control information will be delayed, which will cause the increase of the whole communication delay. In order to control the range of the communication delay, the fifth time domain length can be used to limit the time domain range in which the uplink control information can be delayed to send.

[0152] ​In an example, the fifth time domain length can also be one or more symbols, or one or more slots.

[0153] Similarly, the fifth time domain length can also be predefined in the standard, configured by the network device to the terminal device, or determined by the terminal device and then reported to the network device.

[0154] In an exemplary embodiment, when there is at least one other PUCCH containing uplink control information between the time domain position of the current PUCCH and the time domain position of the PUSCH, the terminal device can transmit the uplink control information in the current PUCCH and the at least one other uplink control information to the network device through the PUSCH.

[0155] In an optional embodiment, the time domain length between the time domain position of the DCI and the time domain position of the PUCCH is greater than or equal to the fourth time domain length, and the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to the fifth time domain length. For example Figure 7 as shown.

[0156] In an optional embodiment, when the uplink control information contains P-CSI reporting or SP-CSI reporting, and the DCI triggers AP-CSI reporting, the terminal device performs step 202 only when the reporting content of the P-CSI reporting or SP-CSI reporting contained in the uplink control information is different from the reporting content of the AP-CSI reporting contained in the PUSCH. Wherein, the reporting content is different can be that the reporting content is completely different, or the reporting content is not completely the same. It should be noted that this embodiment can be used in combination with the above method involving the fourth time domain length and / or the fifth time domain length.

[0157] Specifically, when the network device configures the terminal device with the related configuration information of the CSI report, it will configure the parameter report content (reportQuantity), which is used to indicate which type of channel state information will be carried in the current CSI report. In some embodiments, the value of reportQuantity can be as follows:

[0158]

[0159] Since the P-CSI report or the SP-CSI report and the AP-CSI report are all CSI reports sent by the terminal device, the functions may overlap to a certain extent, and if the terminal device sends the CSI report twice, the performance improvement may not be obvious, but the power consumption of the terminal device will be consumed. Therefore, in order to avoid the repeated transmission of the CSI report with the same function (that is, transmitting once through the PUCCH carrying the P-CSI report or the SP-CSI report, and transmitting once through the PUSCH carrying the AP-CSI report), the transmission of one of them can be cancelled. In order to avoid the impact on the performance as much as possible, in the present application, the terminal device only performs step 202 when the report content (reportQuantity) of the P-CSI report or the SP-CSI report contained in the uplink control information is different from the report content of the AP-CSI report contained in the PUSCH.

[0160] In an optional embodiment, when the report content of the P-CSI report or the SP-CSI report is partially or completely the same as the report content of the AP-CSI report, the terminal device discards the information in the PUCCH, that is, the terminal device cancels the transmission of the PUCCH, that is, the terminal device no longer sends the information (that is, the uplink control information) in the PUCCH.

[0161] In another optional embodiment, when the uplink control information contains the P-CSI report or the SP-CSI report, and the DCI triggers the AP-CSI report, the terminal device can not judge whether the report content of the P-CSI report or the SP-CSI report is the same as the report content of the AP-CSI report, and the terminal device can directly discard the information in the PUCCH, that is, no longer send the P-CSI report or the SP-CSI report in the PUCCH, for example Figure 8 as shown.

[0162] In a specific embodiment, the terminal device transmits the uplink control information to the network device through the PUSCH, which can specifically include the following two methods:

[0163] Method a1, the terminal device concatenates the uplink control information and the information contained in the PUSCH at the bit level to obtain first information, and transmits the first information to the network device through the PUSCH.

[0164] Specifically, in method a1, the terminal device can multiplex the uplink control information into the PUSCH, that is, concatenate the uplink control information and the information contained in the PUSCH at the bit level, and then modulate and map them together to the physical resource of the PUSCH, that is, obtain the first information.

[0165] Method a2: The terminal device punctures the PUSCH, maps the uplink control information to the position where the PUSCH is punctured, obtains the second information, and transmits the second information to the network device through the PUSCH. The second information is the uplink control information mapped to the position where the PUSCH is punctured and the information at the position where the PUSCH is not punctured.

[0166] Specifically, in the above method a2, the terminal device separately modulates the uplink control information, and after puncturing the PUSCH, replaces the modulated symbol on some resource elements (REs) occupied by the punctured PUSCH with the modulated symbol after modulation of the uplink control information, that is, obtains the second information.

[0167] Optionally, when puncturing the PUSCH, the position where the PUSCH is punctured can be predefined. For example, in the time domain, the terminal device can start puncturing from the first symbol occupied by the PUSCH, or the terminal device can start puncturing from the first symbol in the PUSCH except the demodulation reference symbol (DMRS); in the frequency domain, the terminal device can start puncturing from the starting RE occupied by the PUSCH, and the two punctured REs can be separated by h REs, where h can be a predefined value. Of course, the position where the PUSCH is punctured can also have other possibilities, as long as the information at the position where the PUSCH is punctured has little effect on data transmission, which is not limited in the present application.

[0168] It should be noted that in addition to the above method a1 and method a2, there can be other methods, which are not listed here.

[0169] The above method a1 and method a2 can be predefined in the standard, or can be configured by the network device to the terminal device, or the terminal device can also adopt method a1, method a2 or other methods through conditional judgment. Specifically, the following three methods can be included:

[0170] Method b1: When the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to the sixth time domain length, the above method a1 is adopted; otherwise, the above method a2 is adopted.

[0171] Specifically, whether the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to the sixth time domain length can be represented by whether the time domain length between the end position of the time domain position of the PUCCH and the start position of the time domain position of the PUSCH is greater than or equal to the sixth time domain length.

[0172] The sixth time domain length is used to ensure that the terminal device has enough processing time when the terminal device needs to jointly modulate the uplink control information and the uplink data.

[0173] In an example, the sixth time domain length can also be one or more symbols or one or more slots.

[0174] For example, a schematic diagram in which the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to the sixth time domain length can be as shown in FIG. 3. Figure 9

[0175] If the above method a1 is used, the uplink control information needs to be jointly modulated with the uplink data, and therefore, enough time needs to be reserved for the terminal device. When the above method a2 is used, the uplink control information is modulated separately from the uplink data, and even if the time domain position of the PUCCH is close to the time domain position of the PUSCH, the processing of the uplink control information will not affect the generation of the PUSCH itself, but only needs to replace part of the RE when the information contained in the PUSCH is transmitted. Therefore, the above method a2 requires less time. Therefore, it can be determined by the method b1 whether to use the method a1 or the method a2.

[0176] Similarly, the sixth time domain length can also be predefined in the standard, can be configured by the network device to the terminal device, or can also be determined by the terminal device and then reported to the network device.

[0177] Method b2: when the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to a seventh time domain length, the above method a1 is used; otherwise, the method in step 202 is not performed, that is, the uplink control information is not transmitted through the PUSCH, but is directly transmitted through the PUCCH according to the existing method.

[0178] The seventh time domain length is used to ensure that the terminal device has enough processing time when the terminal device needs to jointly modulate the uplink control information and the uplink data.

[0179] In an example, the seventh time domain length can be the same as the sixth time domain length.

[0180] Method b3: when the number of information bits of the uplink control information is greater than or equal to a first value, the above method a1 is used; when the number of information bits of the uplink control information is less than the first value, the above method a2 is used.

[0181] ​Specifically, when the method a2 is used, part of the REs in the PUSCH is directly replaced by the modulated symbols of the uplink control information, which is equivalent to destroying part of the uplink data. After the uplink data is channel encoded, a part of the redundant information will be introduced. The addition of the redundant information can make the coded and modulated PUSCH still be able to recover all the original information even if part of the PUSCH is destroyed, as long as the proportion of the destroyed part is small. Therefore, when the number of information bits of the uplink control information is small, even if the uplink control information is sent together with the uplink data by using the above method a2, both of them can be correctly transmitted. However, when the number of information bits of the uplink control information is large, the above method a2 can cause the transmission of the uplink data to fail. Therefore, the first value is introduced, and when the number of information bits of the uplink control information is less than the first value, the method a2 is used again, which can reduce the probability of transmission failure.

[0182] The first value can be predefined or configured by the network device to the terminal device. The value of the first value can be any value that can be successfully transmitted when the uplink information is transmitted through the PUSCH.

[0183] In a specific embodiment, the above method b1 and the above method b3 can be combined to determine whether the method a1 or the method a2 is used.

[0184] Currently, when the uplink control information is transmitted through the PUCCH and the information is transmitted through the PUSCH, the terminal device needs to send two signals. Although the transmission power consumption of the terminal device is large, the energy per bit of the two signals is also high, which can resist strong noise and has a large coverage range. When the uplink control information is transmitted through the PUSCH by using the method of the present application, whether it is the uplink control information or the data or the AP-CSI report in the PUSCH, the energy per bit is relatively low, the coverage range of the signal can be limited, and the signal transmission reliability can be reduced. In order to solve the problem of signal transmission reliability, the present application can ensure the reliability of signal transmission by the following methods:

[0185] Method c1: the terminal device only performs step 202 when the reference signal received power (RSRP) sent by the terminal device to the network device is greater than an RSRP threshold.

[0186] The terminal device calculates an RSRP value according to the power of a reference signal (such as a synchronization signal block (SSB) and a physical broadcast channel (PBCH) block, or a CSI-RS, etc.) received from the network device. The greater the RSRP value, the closer the terminal device is to the network device. The RSRP threshold value is equivalent to an equivalent network device-to-terminal device distance threshold value. When the RSRP corresponding to the reference signal received by the terminal device is greater than the RSRP threshold value, it means that the terminal device is close enough to the network device. At this time, even if the terminal device transmits the uplink control information through the PUSCH, it can ensure that the signal can be correctly transmitted. When the terminal device reports the RSRP to the network device, if the RSRP is greater than the RSRP threshold value, it can be considered that the coverage of the terminal device is not limited, and at this time, the uplink control information can be transmitted in the manner of step 202.

[0187] For example, when the RSRP does not satisfy the condition in method c1, the uplink control information can be transmitted in the conventional manner, that is, the uplink control information is transmitted alone.

[0188] It should be noted that the uplink control information is transmitted in step 202 only when both the terminal device and the network device determine that the RSRP is greater than the RSRP threshold value. Therefore, the comparison between the RSRP reported by the terminal device to the network device and the RSRP threshold value can determine whether the terminal device and the network device both determine whether the condition is satisfied.

[0189] Method c2: When the terminal device transmits the uplink control information to the network device through the PUSCH, the terminal device transmits the uplink control information to the network device through the PUSCH by using a first transmission power.

[0190] The first transmission power can be determined in the following two ways:

[0191] The first way: The first transmission power can be the original transmission power of the PUSCH plus X decibels (dB), where the value of X can be standard predefined, or preconfigured by the network device to the terminal device, or indicated by the network device through signaling (such as DCI), which is not limited in the present application.

[0192] The first transmission power can be determined based on the original transmission power of the PUSCH and the original transmission power of the PUCCH. For example, the first transmission power can be obtained by adding the original transmission power of the PUSCH and the original transmission power of the PUCCH, or the first transmission power can be obtained by multiplying the sum of the original transmission power of the PUSCH and the original transmission power of the PUCCH by a coefficient. For example, if the original transmission power of the PUCCH is 16 decibels-milliwatts (dBm) and the original transmission power of the PUSCH is 16 dBm, the first transmission power can be the sum of the two, i.e., 19 dBm, or the sum of the two multiplied by a coefficient, i.e., 18 dBm, and the like. Of course, there can be other methods to obtain the first transmission power, which are not limited in the present application.

[0193] It should be understood that the above two methods are to increase the transmission power. In some embodiments, the transmission power of the PUSCH can be determined according to the path loss value estimated by the terminal device, the transmission parameter configured by the network device, and the transmit power control (TPC) command indicated by the network device in the DCI. In order to improve the transmission reliability of the uplink control information and the uplink data or the AP-CSI report, the method in the above method c2 can be used to increase the transmission power of the PUSCH, thereby increasing the energy allocated to each bit on average.

[0194] Method c3: the terminal device performs step 202 only when the number of bits of the uplink control information is less than or equal to a second value. This method c3 controls the degree of decrease in the energy allocated to each bit on average, and only when the transmission can be guaranteed, the uplink control information is transmitted by the method in step 202.

[0195] The second value can be predefined or configured by the network device to the terminal device. The value of the second value can be determined as long as the uplink control information can be transmitted when the uplink control information is transmitted by the PUSCH.

[0196] Method c4: when the terminal device transmits the PUSCH of the uplink control information to the network device, the terminal device can determine the first K bits in the uplink control information from high to low according to the priority of the bits in the uplink control information when the number of bits of the uplink control information is greater than M; the terminal device transmits the K bits to the network device by the PUSCH; wherein the K is less than or equal to M.

[0197] For example, M is the second value in method c3.

[0198] Specifically, the terminal device transmits the uplink control information to the network device through the PUSCH, and when the network device receives the uplink control information transmitted by the terminal device through the PUSCH, the two parties need to negotiate and jointly enable or not enable the function. Exemplarily, the enabling of the function can be configured in the following four ways:

[0199] Mode d1: the terminal device receives a first message from the network device, and the first message is used to configure or enable the function of transmitting the uplink control information by the terminal device through the PUSCH.

[0200] The first message is also the configuration information sent by the network device to the terminal device, for example, the first message can be sent through radio resource control (RRC) signaling or medium access control (MAC) control elements (CE) (MAC CE).

[0201] Through the above method, when the time domain position of the PUCCH and the time domain position of the PUSCH meet step 201, the terminal device can transmit the uplink control information through the PUSCH, and the network device can receive the uplink control information through the PUSCH, for example, the specific process can be as shown in Figure 10 .

[0202] Mode d2: the terminal device sends a second message to the network device, and the second message is used to request to enable the function of transmitting the uplink control information through the PUSCH. Then, the terminal device receives a first message from the network device, and the first message is used to configure or enable the function of transmitting the uplink control information by the terminal device through the PUSCH. After that, when the time domain position of the PUCCH and the time domain position of the PUSCH meet step 201, the terminal device can transmit the uplink control information through the PUSCH, and the network device can receive the uplink control information through the PUSCH, for example, the specific process can be as shown in Figure 11 .

[0203] Mode d3: the terminal device receives a first message from the network device, and the first message is used to configure or enable the function of transmitting the uplink control information by the terminal device through the PUSCH; then the terminal device receives a third message from the network device, and the third message is used to instruct the terminal device to transmit the uplink control information through the PUSCH. After that, when the time domain position of the PUCCH and the time domain position of the PUSCH meet step 201, the terminal device can transmit the uplink control information through the PUSCH, and the network device can receive the uplink control information through the PUSCH, for example, the specific process can be as shown in Figure 12 .

[0204] In mode d3, after the network device sends configuration information (i.e., the first message) to the terminal device, it also needs to send dynamic indication information, i.e., a third message (e.g., DCI), to the terminal device, indicating whether the terminal device can transmit uplink control information via the PUSCH. For example, the third message can be added to the DCI of the PUSCH scheduled by the network device to indicate whether uplink control information in other PUCCHs can be transmitted via the current PUSCH.

[0205] Method d4: The terminal device sends a second message to the network device, and the second message is used to request to enable the function of transmitting uplink control information through PUSCH. Then, the terminal device receives a first message from the network device, and the first message is used to configure or enable the function of the terminal device to transmit uplink control information through PUSCH. After that, the terminal device receives a third message from the network device, and the third message is used to instruct the terminal device to transmit uplink control information through PUSCH. Finally, when the time domain position of PUCCH and the time domain position of PUSCH meet step 201, the terminal device can send the uplink control information through PUSCH, and the network device can receive the uplink control information through PUSCH. For example, the specific process can be as follows. Figure 13 shown.

[0206] That is, mode d4 is a combination of the above three modes. For specific message descriptions, please refer to the relevant descriptions in the above modes.

[0207] By adopting the uplink control information transmission method provided in the present application and transmitting the uplink control information through PUSCH, the number of uplink transmissions can be reduced, thereby reducing the power consumption of the terminal device.

[0208] Based on the above description, the embodiment of the present application also provides another method for transmitting uplink control information, which is suitable for Figure 1 The communication system shown. Figure 14 As shown, the specific process of the method may include:

[0209] Step 1401: The terminal device determines that the time domain position of PUSCH is before the time domain position of PUCCH containing uplink control information, and the time domain length between the time domain position of PDSCH corresponding to the uplink control information and the time domain position of PUSCH is greater than or equal to the first time domain length.

[0210] The uplink control information may include the HARQ feedback.

[0211] Step 1402: The terminal device transmits the uplink control information to the network device via the PUSCH, that is, the network device receives the uplink control information transmitted by the terminal device via the PUSCH.

[0212] andFigure 2 The embodiment shown is similar, when the terminal device transmits uplink control information to the network device through PUSCH, the terminal device will not send information in PUCCH again.

[0213] This embodiment can ensure that the terminal device has enough time to decode PDSCH and generate HARQ feedback information through the limitation of the first time domain length. For example, the transmission diagram of uplink control information limited by the first time domain length can be as shown in the figure. Figure 15

[0214] In a specific implementation, the first time domain length can be represented by T proc,1 , wherein T proc,1 can conform to the following formula one:

[0215] T proc,1 = (N1+d 1,1 +d2)(2048+144)·κ2 -μ ·T C formula one;

[0216] Wherein, the value of N1 in the above formula one is related to the subcarrier spacing (SCS) or system parameter numerology. N1 is a processing capability reported by the terminal device, and the terminal device can report "capability one" or "capability two". The value of N1 can refer to the following table 1 or table 2:

[0217] Table 1 capability one

[0218]

[0219] Table 2 capability two

[0220]

[0221] Wherein, in the above table 1 and table 2, the parameter dmrs-AdditionalPosition is used to configure the time domain position of the demodulation reference symbol (DMRS); pos0 is a value of this parameter, which can be explained as "position 0";

[0222] d 1,1 and d2 are related to PDSCH mapping type and the symbol length occupied by PDSCH. μ is numerology, T c =1 / (Δf max ·N f ), wherein Δf max =480·10​3 Hz, N f = 4096; K = T s / T c = 64, where T s = 1 / (Af ref · N f,ref ), Af ref = 15·10 3 Hz, N f,ref = 2048.

[0223] Specifically, the method for the terminal device to transmit the uplink control information to the network device via the PUSCH is similar to the method for the terminal device to transmit the uplink control information to the network device via the PUSCH in the embodiment shown in Figure 2 , and specific reference can be made to the related descriptions in the methods a1-a3, b1-b3 and c1-c4 described above, which will not be repeated here.

[0224] Optionally, in this embodiment, since the time domain position of the PUSCH is before the time domain position of the PUCCH containing the uplink control information, when the terminal device transmits the uplink control information to the network device via the PUSCH, the above methods b1-b2 can not be used, that is, in this embodiment, both the bit concatenation (i.e., the above method a1) or the puncturing (i.e., the above method a2) can be used, and are not limited by the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH (i.e., without considering the size relationship between the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH and the sixth time domain length or the seventh time domain length).

[0225] Specifically, the specific method for the network device to configure the capability information of the terminal device to transmit the uplink control information via the PUSCH can also be understood with reference to the related descriptions in the methods d1-d4 in the embodiment shown in Figure 2 , which will not be repeated here.

[0226] By using the method for transmitting the uplink control information provided in the present application, the number of uplink transmissions can be reduced by transmitting the uplink control information via the PUSCH, thereby reducing the power consumption of the terminal device.

[0227] Based on the above description, another method for transmitting uplink control information is also provided in the embodiments of the present application, which is applicable to the communication system shown in Figure 1 . Referring to Figure 16 , the specific process of the method can include:

[0228] Step 1601: The terminal device determines that the time domain position of the PUSCH is before the time domain position of the PUCCH containing the uplink control information, and the time domain length between the time domain position of the CSI-RS corresponding to the uplink control information and the time domain position of the PUSCH is greater than or equal to the second time domain length.

[0229] The uplink control information can include P-CSI reporting and / or SP-CSI reporting.

[0230] Step 1602: The terminal device transmits the uplink control information to the network device through the PUSCH, i.e., the network device receives the uplink control information transmitted by the terminal device through the PUSCH.

[0231] As shown in the embodiment of Figure 2 , when the terminal device transmits the uplink control information to the network device through the PUSCH, the terminal device will not send the information in the PUCCH any more.

[0232] This embodiment can ensure that the terminal device has enough time to decode the PDSCH and generate the P-CSI reporting and / or SP-CSI reporting through the limitation of the second time domain length. For example, the transmission schematic diagram of the uplink control information limited by the second time domain length can be as shown in Figure 17 .

[0233] In a specific implementation, the second time domain length can be represented by T proc,CSI , wherein T proc,CSI can conform to the following formula two:

[0234] T proc,CSI = (Z) (2048 + 144) · κ2 -μ · T C , formula two.

[0235] Wherein, Z is a predefined value; κ can be greater than or equal to 1, and T C can be greater than or equal to 0. See the related description of formula one in the embodiment of Figure 14 , which will not be described in detail here.

[0236] Specifically, the method for the terminal device to transmit the uplink control information to the network device through the PUSCH is similar to the method for the terminal device to transmit the uplink control information to the network device through the PUSCH involved in the embodiment of Figure 2 , and specific reference can be made to the related description in the above methods a1-a3, b1-b3 and c1-c4, which will not be repeated here.

[0237] Optionally, in this embodiment, when the terminal device transmits the uplink control information to the network device through the PUSCH, the terminal device can not use the restrictions of the above methods b1-b2, that is, in this embodiment, both the bit concatenation (that is, the above method a1) or the puncturing (that is, the above method a2) can be used, and the terminal device is not limited by the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH (that is, the terminal device does not need to consider the size relationship between the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH and the sixth time domain length or the seventh time domain length).

[0238] Specifically, the specific manner in which the network device configures the capability information of the terminal device for transmitting the uplink control information through the PUSCH can also be understood with reference to the related descriptions of the methods d1-d4 in the above-described embodiments, and details are not described herein again. Figure 2

[0239] By using the method for transmitting the uplink control information provided in the present application, the number of uplink transmissions can be reduced, and the power consumption of the terminal device can be reduced.

[0240] Based on the above description, another method for transmitting uplink control information is also provided in the embodiments of the present application, which is applicable to the communication system as shown in Figure 1 Figure 18 The specific process of the method can include the following steps.

[0241] In step 1801, the terminal device determines that the time domain position of the PUCCH containing the uplink control information is before the time domain position of the PUSCH, and the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to the third time domain length.

[0242] In step 1802, the terminal device transmits the uplink control information to the network device through the PUSCH, that is, the network device receives the uplink control information transmitted by the terminal device through the PUSCH.

[0243] The embodiments can be applicable to a scenario of configured grant (CG)-PUSCH transmission (for a specific description, reference can be made to the description of the transmission manner of the CG in the above description of the uplink transmission of the NR, and details are not described herein again), and in the scenario, there can be no DCI.

[0244] Similar to the embodiments shown in Figure 2 When the terminal device transmits the uplink control information to the network device through the PUSCH, the terminal device will not send the information in the PUCCH.

[0245] ​​Exemplarily, the transmission diagram of the uplink control information with the third time domain length limited can be as follows: Figure 19 shown.

[0246] Optionally, the third time domain length may be one or more symbols, or one or more time slots.

[0247] The third time domain length may be predefined in the standard, or may be configured by the network device to the terminal device, or the terminal device may determine and then report the sixth time domain length to the network device.

[0248] Specifically, the method in which the terminal device transmits uplink control information to the network device via PUSCH is similar to Figure 2 The method in which the terminal device in the illustrated embodiment transmits uplink control information to the network device via PUSCH is similar. For details, please refer to the relevant descriptions in the above methods a1 to a3, b1 to b3 and c1 to c4, which will not be repeated here.

[0249] Specifically, the network device configures the terminal device with the capability information of transmitting uplink control information through PUSCH, which can also be seen in the above Figure 2 The relevant descriptions of methods d1 to d4 in the illustrated embodiment will not be repeated here.

[0250] By adopting the uplink control information transmission method provided in the present application and transmitting the uplink control information through PUSCH, the number of uplink transmissions can be reduced, thereby reducing the power consumption of the terminal device.

[0251] It should be noted that when the relationship between the PUCCH containing uplink control information and multiple PUSCHs satisfies Figure 2 or Figure 18 The embodiment shown in FIG. Figure 14 or Figure 16 In the case of the embodiment shown, the terminal device can select a PUSCH from multiple PUSCHs to transmit current uplink control information.

[0252] It should be noted that the “…greater than or equal to…” and “…less than…” involved in the above embodiments are merely examples. It should be understood that “greater than” is one situation and “less than” is another situation. Among them, “equal to” can be classified as the greater than situation as mentioned above, and of course it can also be classified as the less than situation. This application does not limit this.

[0253] It should be noted that the time domain position of XX involved in the above embodiments may also be referred to as XX occasion. For example, the time domain position of PUCCH may be referred to as PUCCH occasion.

[0254] The following is a practical example of how the method described in the above embodiment can be used to reduce the number of uplink transmissions and thus reduce the power consumption of the terminal device. Specifically, when the terminal device is a mobile phone, in a scenario where a mobile phone user uses a mobile phone to send and receive WeChat messages, the user receives a downlink data packet (contained in the PDSCH) when receiving a WeChat message through the mobile phone, and sends HARQ feedback to the network device. When a user sends a WeChat message through a mobile phone, an uplink data packet (contained in the PUSCH) is sent. If the current method is used, if the time domain position for sending the HARQ feedback determined by the mobile phone according to the configuration / instruction of the network device does not overlap with the time domain position for sending the PUSCH, the mobile phone will send the HARQ feedback and PUSCH respectively at the two time domain positions, that is, it will send two uplink signals. If the solution of the present invention is used, if the conditions are met, the mobile phone can merge the HARQ feedback into the PUSCH and send it, and the mobile phone only sends one uplink signal. This achieves the effect of energy saving for the mobile phone.

[0255] Based on the above embodiments, the method for transmitting uplink control information is described in detail with some specific examples. In the following examples, the terminal device is a UE, the network device is a base station, and the uplink control information is UCI.

[0256] In the following example, this solution is used to reduce the number of UE uplink transmissions, thereby reducing the UE's uplink transmission power consumption.

[0257] Specifically, in the following example, to reduce the number of UE uplink transmissions, the UE can "predict" that there is a PUSCH near the PUCCH containing UCI (HARQ-ACK or P-CSI / SP-CSI) and then transmit the UCI in the PUSCH. Furthermore, this solution can be described through the following four aspects: first, how to use this feature, that is, how to use the feature of transmitting UCI in the PUSCH; second, how to define "near the PUCCH"; third, how to merge the UCI into the PUSCH for transmission; and fourth, how to avoid affecting transmission performance.

[0258] The first aspect is how to use this feature, that is, how to use the feature of carrying UCI in the PUSCH for transmission:

[0259] Method 1: The standard defines conditions for combined transmission. When PUCCH and PUSCH meet the conditions, both the base station and the UE can determine that the two (i.e., the information in UCI and PUSCH) can be combined for transmission.

[0260] Method two: the base station dynamically indicates in the DCI scheduling PUSCH whether it can be combined, and the range and conditions of the combination can be the same as method one. This method two can be understood as a dynamic switch of whether to "enable the feature".

[0261] Second aspect, how to define "PUCCH vicinity":

[0262] Scenario one: when the PUSCH is a DCI dynamically scheduled PUSCH, and the PUCCH is located between the DCI and the PUSCH, the PUSCH can be considered to be in the vicinity of the PUCCH.

[0263] Specifically, a gap1 (also referred to as the fourth time domain length in the above embodiments) is required between the DCI and the PUCCH, so as to give the UE sufficient time for DCI blind detection. If the DCI is detected, it is determined that the UCI is combined into the PUSCH for transmission; if the DCI is not detected, it is determined that the UCI is transmitted in the PUCCH.

[0264] The distance (also referred to as the distance in the time domain position) between the PUCCH and the PUSCH is less than or equal to a gap2 (also referred to as the fifth time domain length in the above embodiments), so as to avoid excessive latency caused by delayed transmission of the UCI.

[0265] Scenario two: when the PUSCH is a semi-persistent PUSCH, the distance between the PUCCH and the PUSCH is less than or equal to a gap3 (also referred to as the third time domain length in the above embodiments).

[0266] Third aspect, how to combine the UCI into the PUSCH for transmission:

[0267] Method one: the UCI can be multiplexed into the PUSCH, that is, the UCI information bits and the uplink data bits are concatenated, and then modulated and mapped to the physical resources of the PUSCH.

[0268] Method two: the UCI can puncture the PUSCH.

[0269] Only method one can be used; or only method two can be used; or the base station configures whether to use method one or method two; or method one or method two is used according to the conditions.

[0270] For example, when the distance between PUCCH and PUSCH is greater than or equal to gap4 (i.e. the sixth time domain length in the above embodiment), multiplexing is used, otherwise puncturing is used.

[0271] For another example, when the distance between PUCCH and PUSCH is greater than or equal to gap5 (i.e. the seventh time domain length in the above embodiment), multiplexing is used, otherwise legacy transmission is used without merging.

[0272] For another example, a UCI information bit threshold N is introduced, when the number of UCI information bits to be merged is greater than or equal to N, multiplexing is used, otherwise puncturing is used.

[0273] In one scenario, if PUCCH carries P-CSI report / SP-CSI report and PUSCH carries AP-CSI report, the P-CSI report / SP-CSI report is dropped.

[0274] Optionally, when the CSI report sent on PUCCH and the CSI-report sent on PUSCH are partially or completely the same in report content (reportQuantity), the PUCCH is dropped, otherwise the CSI report in PUCCH is merged into PUSCH.

[0275] Fourthly, how to avoid the impact on transmission performance:

[0276] Possible impact one: after UCI is merged into PUSCH for transmission, the energy per bit is reduced, and the coverage performance is affected.

[0277] Solution one: introduce an RSRP threshold, when the RSRP reported by the UE to the base station is higher than the RSRP threshold, it is considered that the coverage of the UE is not limited, at this time the merging transmission method in the present application can be used, otherwise the commonly used method is used.

[0278] Solution two: enhance PUSCH power control.

[0279] For example, when UCI is merged into PUSCH for transmission, the transmission power of PUSCH is increased by X dB, the value of X can be predefined, or configured by the base station, or indicated by DCI.

[0280] For example, when UCI is combined into PUSCH for transmission, the final transmit power of PUSCH can be determined by the original PUCCH transmit power and the original PUSCH transmit power, for example, power addition, or power addition multiplied by a coefficient, etc.

[0281] Possible impact 2: If the number of UCI information bits is large, UCI combined into PUSCH for transmission can cause UCI transmission failure.

[0282] Solution: Introduce a UCI information bit threshold M, when the number of UCI information bits to be combined is less than or equal to M, then combine, otherwise use the current common way of transmission.

[0283] In the first specific example, when the PUCCH carrying UCI (including HARQ-ACK and / or P-CSI / SP-CSI) is located between DCI and PUSCH, the UE combines UCI into the latter PUSCH for transmission (i.e., the terminal device of the above embodiment transmits the uplink control information through the PUSCH). An example can be as shown in Figure 20 The leftmost part is DCI, the rightmost part is the PUSCH scheduled by DCI, and the middle part is the PUCCH carrying UCI. In the scheme of this example, the middle PUCCH will not be transmitted, and UCI will be combined into the right PUSCH for transmission.

[0284] Specifically, on the one hand, in order to reduce the uplink transmission power consumption, UCI is combined into PUSCH for transmission in this scheme. Since PUSCH is dynamically scheduled by DCI, in order to ensure that UCI can be combined into PUSCH, the UE needs to be able to determine that there is PUSCH transmission near PUCCH. If DCI is located after PUCCH, the UE cannot predict that there is PUSCH transmission near PUCCH, in order to ensure that UCI can be transmitted to the base station, it can only choose to use PUCCH to carry UCI. Therefore, DCI needs to be located before PUCCH.

[0285] On the other hand, if DCI and the PUSCH scheduled by DCI are both before PUCCH, it means that the time (i.e., time domain position) of UCI transmission needs to be advanced from PUCCH to the position of PUSCH (such as Figure 21The UCI needs a certain time to be generated by the UE, for example, when the UE generates the HARQ-ACK, the UE needs to decode and check the downlink data to determine whether the data is correctly transmitted to decide whether to generate the ACK or the NACK; when the UE generates the CSI report, the UE needs to receive the CSI-RS and process the received signal to generate the report. Therefore, if the UCI is transmitted in advance, it is possible that the UE does not have enough processing time to generate the UCI. Therefore, preferably, the PUSCH needs to be located after the PUCCH.

[0286] In this first specific example, the UCI can be combined into the PUSCH, reducing the number of uplink transmissions and reducing the power consumption of the UE.

[0287] In the second specific example, the explanation of "why the PUSCH needs to be after the PUCCH" is given as in the first specific example. However, combining the UCI into the PUSCH after the PUCCH will delay the transmission time of the UCI, i.e. increase the communication delay. In this example, by adding some restrictions, it is ensured that the PUSCH can be before the PUCCH, thereby shortening the communication delay.

[0288] When the UCI is the HARQ-ACK, if the interval between the PDSCH corresponding to the HARQ-ACK and the PUSCH is greater than or equal to a predefined interval (i.e. the first time domain length involved in the above embodiments), it is considered that the UCI can be combined into the PUSCH for transmission. As shown in Figure 22 The interval can be T proc,1 . Specifically, the related explanation of T proc,1 can be found in the above Figure 14 The formula one and the related description of each parameter in the formula one in the embodiment shown in

[0289] Similarly, when the UCI is the CSI report, if the interval between the PDSCH corresponding to the CSI report and the PUSCH is greater than or equal to a predefined interval (i.e. the second time domain length involved in the above embodiments), it is considered that the UCI can be combined into the PUSCH for transmission. As shown in Figure 23 The interval can be T proc,CSI . Wherein, T proc,CSI can be found in the related description of the formula two in the embodiment shown in Figure 16 The formula two and the related description of each parameter in the formula two in the embodiment shown in

[0290] Similarly, similar to the first specific embodiment, the function (i.e. the UCI is combined into the PUSCH for transmission) can be used after the base station configures the function for the UE, or the base station configures the function and then dynamically indicates whether the function is used.

[0291] By adopting the second specific example, uplink transmissions can be combined and UCI can be transmitted in advance, thereby saving UE power consumption and reducing transmission delay. Compared with the first specific example, transmission delay can be reduced.

[0292] In the third specific example, this example is a further supplement to the first or second specific example, and provides a clearer description of "there is a PUSCH near the PUCCH".

[0293] On the one hand, it is necessary to consider the interval between PUCCH and DCI (that is, the time domain length between the time domain positions of PUCCH and DCI). At this time, the rule can be described as follows: When the PUCCH carrying UCI (including HARQ-ACK and / or P-CSI report / SP-CSI report) is located between DCI and PUSCH, and the length between the end symbol of DCI (that is, the end position of the time domain position) and the start symbol of PUCCH (that is, the start position of the time domain position, the same description appears below) is greater than or equal to gap 1 (gap1) (that is, the fourth time domain length involved above, the same description appears below), the UCI is merged into the subsequent PUSCH and sent together. For example Figure 24 shown.

[0294] The purpose of gap 1 is to ensure that the UE has enough time to complete DCI decoding and thus determine whether there will be subsequent PUSCH scheduling. If the DCI is too close to the PUCCH, the UE may not have completed DCI decoding and will not be able to determine whether there is a PUSCH transmission near the PUCCH. To ensure that the UCI can be sent to the base station, the PUCCH must be used to carry the UCI.

[0295] Typically, the gap1 may be one or more symbols, or one or more slots. The value of the gap1 may be predefined in the standard, configured by the base station to the UE, or reported by the UE.

[0296] When the base station configures or indicates a minimum scheduling timeslot interval for the UE, the value of gap1 may be equal to the currently effective K0min (minimum value of K0).

[0297] On the other hand, the interval between PUCCH and PUSCH also needs to be considered. The rule can be described as follows: when the PUCCH carrying UCI (including HARQ-ACK and / or P-CSI report / SP-CSI report) is located between the DCI and the PUSCH, and the length between the end symbol of the PUCCH and the start symbol of the PUSCH is less than or equal to gap2 (i.e., the fifth time domain length involved in the above embodiment), the UCI is merged into the subsequent PUSCH for transmission. For example, Figure 25 As shown.

[0298] The purpose of the gap2 is to avoid excessive delay. Because when the UCI is merged into the subsequent PUSCH for transmission, the transmission time of the UCI will be delayed, which will cause the increase of the overall communication delay. In order to avoid the influence of the present application scheme on the communication delay, the "range of delay of UCI transmission" can be limited, i.e., the gap2 is introduced.

[0299] Of course, gap1 and gap2 can also be used together, as Figure 26 As shown.

[0300] It should be noted that gap1 can be used in combination with the first specific example and the second specific example, but gap2 can only be used in combination with the first specific example, and cannot be used in combination with the second specific example, because the UCI is sent in advance in the second specific example.

[0301] With the third specific example, gap1 can ensure that the UE can "predict" whether there is a PUSCH transmission near the PUCCH before the PUCCH, so as to merge the UCI into the PUSCH for transmission; gap2 can ensure that the transmission delay will not be too large. Compared with the first specific example, gap1 further defines the positional relationship between the DCI and the PUCCH, thereby ensuring the feasibility of the scheme; gap2 avoids the excessive influence of the scheme on the delay.

[0302] In the fourth specific example, the present application scheme is further improved. In the first to third specific examples, only the DCI dynamically scheduled PUSCH is considered, and the CG-PUSCH is not considered. When the CG-PUSCH is considered, there can be no DCI, so the "conditions" defined in the first to third specific examples (i.e., the relationship between the time domain positions of the defined DCI, PUCCH, or PUSCH) are no longer applicable.

[0303] For CG-PUSCH, the condition for combining transmission can be defined as: when the PUCCH carrying UCI (including HARQ-ACK and / or P-CSI report / SP-CSI report) is located before the PUSCH, and the length between the end symbol of the PUCCH and the start symbol of the PUSCH is less than or equal to gap3 (i.e. the third time domain length involved in the above embodiments), the UCI is combined into the later PUSCH for transmission.

[0304] Alternatively, in one way, in the case of CG-PUSCH, UCI cannot be combined into CG-PUSCH for transmission.

[0305] The fourth specific example is a supplement to the case of CG-PUSCH, which perfects the scheme.

[0306] In the fifth specific example, it is a further improvement of the scheme in the first to fourth specific examples. This example describes in detail how to combine UCI into the specific scheme of transmitting PUSCH.

[0307] Specifically, UCI can be combined into PUSCH for transmission (i.e. the above-mentioned UCI transmission through PUSCH), which can be done in the following two ways:

[0308] Method one: UCI can be multiplexed into PUSCH, i.e. UE concatenates UCI information bits with uplink data bits, and then modulates and maps them to the physical resources of PUSCH;

[0309] Method two: UCI can puncture PUSCH, i.e. UE modulates UCI separately, and after generating PUSCH, replaces the modulation symbols of some REs occupied by PUSCH with the modulation symbols of UCI.

[0310] In the scheme of the first to fourth specific examples, method one can be combined, method two can be combined, or the base station can send configuration information to the UE to determine whether to use method one or method two.

[0311] In another case, the way to determine how UCI is combined into PUSCH for transmission can be:

[0312] Method one: introduce a gap4 (i.e. the sixth time domain length involved in the above embodiments), for example Figure 27As shown, multiplexing is used when the distance between PUCCH and PUSCH is greater than or equal to gap4, otherwise puncturing is used. The principle is that if multiplexing is used for combination, UCI needs to be jointly modulated with uplink data, so sufficient time needs to be reserved for the UE. When puncturing is used, UCI and uplink data are modulated separately, so even if PUCCH is close to PUSCH, the processing of UCI will not affect the generation of the PUSCH itself, but only needs to replace part of the RE when PUSCH is transmitted. Therefore, the puncturing method requires less time.

[0313] Method two: introduce a gap5 (i.e. the seventh time domain length involved in the above embodiment), when the distance between PUCCH and PUSCH is greater than or equal to gap5, multiplexing is used, otherwise legacy transmission is used without combination. In this way, there is only one multiplexing combination method, and this condition can be used to determine whether to combine.

[0314] Method three: introduce a UCI information bit threshold N (i.e. the first value involved in the above embodiment), when the number of UCI information bits to be combined is greater than or equal to N, multiplexing is used, otherwise puncturing is used. The principle is that when puncturing is used, part of the RE in PUSCH is replaced by the modulated symbol after UCI modulation, which is equivalent to destroying part of the uplink data information. After channel coding, a part of the redundant information is introduced. The addition of redundant information can make the coded and modulated PUSCH still be able to recover all the original information even if part of it is destroyed, as long as the destroyed part does not account for a large proportion. Therefore, when the number of UCI information bits is small, even if UCI uses puncturing to send with uplink data, both can be transmitted correctly. However, when the number of UCI information bits is large, puncturing may cause uplink data transmission failure. Therefore, by introducing this information bit threshold, puncturing is used only when the condition is met, which can reduce the probability of transmission failure. It should be noted that method three can be combined with method one, i.e. jointly determining whether to use multiplexing or puncturing according to the two conditions in method one and method three.

[0315] In the above description, the PUSCH mentioned can be the PUSCH carrying uplink data. Next, consider the following question: if the UCI is a P-CSI report / SP-CSI report, and the AP-CSI report is also scheduled to be sent in the PUSCH, how can the UE do it?

[0316] In some embodiments, when the PUCCH carrying the P-CSI report / SP-CSI report and the PUSCH carrying the AP-CSI report do not overlap, they are sent without affecting each other. However, since both the P-CSI report / SP-CSI report and the AP-CSI report are sending CSI reports, there may be some overlap in function, and sending the CSI report twice may not significantly improve performance, but it will cause the UE to consume power. Therefore, in this example, the following scheme can be considered: when the PUCCH carrying the P-CSI report / SP-CSI report is located between the DCI and the PUSCH, and the DCI triggers the AP-CSI report, drop (i.e., do not send) the PUCCH. A schematic diagram can be as shown in the above Figure 8 .

[0317] Further, when the base station configures the UE with the relevant configuration information of the CSI report, it will configure a parameter called reportQuantity, which is used to indicate which type of channel state information will be carried in the current CSI report. In the existing standard, the values that reportQuantity can take can be seen in the implementation shown in Figure 2 .

[0318] This example is to avoid the repeated transmission of CSI reports with the same effect (i.e., transmitted once through the P-CSI report / SP-CSI report PUCCH, and once through the AP-CSI report PUSCH), and cancel the transmission of one of them. In order to minimize the impact on performance, the "CSI report with the same effect" can be clearly defined: the reportQuantity is partially or completely the same. At this time, the scheme can be further refined as follows: when the CSI report sent on the PUCCH and the CSI-report sent on the PUSCH have the same reportQuantity, partially or completely, drop the PUCCH, otherwise merge the CSI report in the PUCCH into the PUSCH for transmission.

[0319] This fifth specific example explicitly defines how to merge the UCI into the PUSCH for transmission, further complementing the scheme.

[0320] In a sixth specific example, the above specific examples are further supplemented.

[0321] Specifically, the base station can send configuration information (e.g. through RRC signaling (or message) or MAC CE) to the UE (i.e. the first message involved in the above embodiments), which is used to enable (i.e. turn on) the function (i.e. the function of UCI being transmitted in PUSCH, i.e. the function of UCI being transmitted through PUSCH involved in the above embodiments). After the UE is configured with the function, when the relative time-domain positions of PUCCH and PUSCH meet the condition, both the base station and the UE can determine that the two (i.e. UCI and the information in PUSCH) can be transmitted in combination. An example flow can be as shown in Figure 28 .

[0322] On the other hand, the UE can send auxiliary information (i.e. the second message involved in the above embodiments) to request or trigger the turning on or off of the function. An example flow can be as shown in Figure 29 .

[0323] In another case, after the base station sends the configuration information to the UE, it also needs to send dynamic indication information (e.g. DCI) to the UE (i.e. the third message involved in the above embodiments), indicating whether the UE can transmit in combination (i.e. whether to enable or enable the function). For example, add indication information in the DCI scheduling PUSCH, which is used to indicate whether the UCI in other PUCCH can be transmitted in combination with the current PUSCH. An example flow can be as shown in Figure 30 .

[0324] Further, the request or trigger for turning on or off the function can be combined with the request of the UE in the above cases. An example flow can be as shown in Figure 31 .

[0325] In a seventh specific example, this example is used to avoid the impact on transmission performance. When the PUCCH of UCI is transmitted separately from the PUSCH, the UE needs to send two signals, although the transmission power consumption of the UE is large, but the energy per information bit in the two signals is also higher, which can resist stronger noise, and the coverage of the signal is larger. When UCI is transmitted in combination with PUSCH, whether it is UCI or data or AP-CSI report in PUSCH, the energy per information bit is lower, the coverage of the signal may be limited, and the signal transmission reliability is reduced. In order to solve the problem of signal transmission reliability, the following several enhanced methods are proposed in this example.

[0326] Method one: introduce a RSRP threshold, when the RSRP reported by UE to base station is higher than the RSRP threshold, it can be considered that the coverage of UE is not limited, at this time the merging transmission method in the present application can be adopted (i.e. UCI is merged with PUSCH for transmission), otherwise the commonly used method is adopted. The principle is that UE will calculate a RSRP value according to the received power of the reference signal sent by the base station, when the RSRP value is larger, it means that the UE is closer to the base station. A RSRP threshold is equivalent to an equivalent base station to UE distance threshold. When the RSRP received by the UE is higher than the RSRP threshold, it means that the UE is close enough to the base station. At this time, even if the UCI is merged with PUSCH for transmission, the signal can also be transmitted correctly. It should be noted that in the present method, the condition is "RSRP reported by UE to base station", because both UE and base station must know whether UCI is merged with PUSCH, in order to correctly transmit. Therefore, both UE and base station must know whether the RSRP condition is met.

[0327] Method two: enhance the power control method of PUSCH. In some current embodiments, the transmission power of PUSCH can be determined according to the path loss value estimated by UE, the transmission parameters configured by base station, and the TPC command indicated by base station in DCI. If no enhancement is made, UE will determine the transmission power of PUSCH according to the method in the current embodiment. If it is desired to improve the transmission reliability of UCI and uplink data or AP-CSI report, the transmission power of PUSCH can be increased when UCI is merged with PUSCH for transmission, so as to increase the average energy per information bit. Specifically, the following several possible ways can be included:

[0328] Method one: when UCI is merged with PUSCH for transmission, the transmission power of PUSCH is increased by X dB, the value of X can be predefined, or configured by base station, or indicated by base station through DCI.

[0329] Method two: when UCI is merged with PUSCH for transmission, the final transmission power of PUSCH can be determined by the original PUCCH transmission power (i.e. the original transmission power of PUCCH) and the original PUSCH transmission power (i.e. the original transmission power of PUSCH), for example, the two powers are added, or the sum of the two powers is multiplied by a coefficient, etc. For example, if the original transmission power of PUCCH is 16 dBm and the original transmission power of PUSCH is 16 dBm, the transmission power of PUSCH after UCI is merged with PUSCH can be the sum of the two, i.e. 19 dBm, or the sum multiplied by a coefficient, i.e. 18 dBm, etc.

[0330] Method three: introduce a threshold M of the number of UCI information bits (i.e. the second value involved in the above embodiments), when the number of UCI information bits to be combined is less than or equal to M, then combine, otherwise use the current common way. This method can control the degree of energy reduction per information bit, only when it can be guaranteed to transmit, then combine, otherwise do not combine.

[0331] In another case, the transmission content can also be determined according to the priority of UCI. For example, when the number of UCI information bits to be combined is greater than M, the UE selects K bits from the UCI to be combined in order of priority from high to low, where K <= M. Then the UE combines the K bits into the PUSCH for transmission, and the remaining bits are not transmitted.

[0332] The seventh specific example further considers the feasibility of UCI and PUSCH combined transmission, and tries to minimize the impact of combined transmission on transmission performance.

[0333] In the above embodiments, the transmission method of uplink control information in 5G or future communication systems such as 6G is described. In other scenarios, such as device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication or vehicle-to-everything (V2X) communication, and other scenarios based on sidelink (SL) transmission, SL control information (such as HARQ feedback information, CSI feedback information, etc.) can also be combined into a sidelink shared channel (PSSCH) for transmission. The SL control information is originally carried by a sidelink control channel (PSCCH) or a sidelink feedback channel (PSFCH). For example, if a terminal device determines that the time domain position of the PSFCH carrying the SL control information (such as HARQ feedback information) is between the time domain position of the sidelink control information (SCI) and the time domain position of the PSSCH scheduled by the SCI, the terminal device can not transmit the PSFCH, but can combine the HARQ feedback information (i.e. SL control information) into the PSSCH for transmission. Optionally, similar to the examples of Figure 7 In the scenario based on SL transmission, a fourth time domain length and / or a fifth time domain length can also be defined, and the beneficial effects are similar to Figure 7The beneficial effects of the illustrated manner are similar and will not be described in detail here.

[0334] Based on the above embodiments, the embodiments of the present application further provide a communication device, which can be referred to as Figure 32 As shown, the device 3200 can include a transceiver unit 3201 and a processing unit 3202. The transceiver unit 3201 is configured to transmit information (messages or data) of the communication device 3200, i.e., receive information (messages or data) or send information (messages or data), and the processing unit 3202 is configured to control and manage the actions of the communication device 3200. The processing unit 3202 can also control the steps performed by the transceiver unit 3201.

[0335] For example, the communication device 3200 can be a terminal device, a processor in the terminal device, a chip or a chip system, or a functional module, etc. in the above embodiments; or the communication device 3200 can be a network device, a processor in the network device, a chip or a chip system, or a functional module, etc. in the above embodiments.

[0336] In one embodiment, the communication device 3200 is configured to implement the functions of the terminal device in the above Figure 2 , Figure 14 , the figures or Figure 18 The transceiver unit 3201 can implement the transceiving operations (or transmission operations) performed by the terminal device in the above Figure 2 , Figure 14 , Figure 16 or Figure 18 embodiments; the processing unit 3202 can implement other operations performed by the terminal device in the above Figure 2 , Figure 14 , Figure 16 or Figure 18 embodiments, except for the transceiving operations. For specific details, please refer to the related descriptions in the above Figure 2 , Figure 14 , Figure 16 or Figure 18 embodiments, which will not be described in detail here.

[0337] In another embodiment, the communication device 3200 is configured to implement the functions of the network device in the above Figure 2 , Figure 14 , the figures or Figure 16 The transceiver unit 3201 can implement the transceiving operations (or transmission operations) performed by the terminal device in the above Figure 18 , Figure 2 , Figure 14 or Figure 16The transceiving operations performed by the network device in the illustrated embodiments; the processing unit 3202 can implement Figure 18 、 Figure 2 、 Figure 14 or Figure 16 other operations performed by the network device in the embodiments illustrated in Figure 18 、 Figure 2 、 Figure 14 or Figure 16 the embodiments described above. For details, please refer to the related description in the above embodiments, which will not be described in detail here.

[0338] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical functional division. In actual implementation, there can be another division manner. The functional units in the embodiments of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0339] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application, essentially or the part that makes a contribution to the prior art, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0340] Based on the above embodiments, the embodiments of the present application also provide a communication device. As shown in Figure 18 , the communication device 3300 can include a transceiver 3301 and a processor 3302. Optionally, the communication device 3300 can also include a memory 3303. The memory 3303 can be arranged inside the communication device 3300, or arranged outside the communication device 3300. The processor 3302 can control the transceiver 3301 to receive and send data (information or message).

[0341] Specifically, the processor 3302 can be a central processing unit (CPU), a network processor (NP), or a combination thereof. The processor 3302 can further include a hardware chip. The hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0342] The transceiver 3301, the processor 3302, and the memory 3303 are connected to each other. Optionally, the transceiver 3301, the processor 3302, and the memory 3303 are connected to each other through a bus 3304. The bus 3304 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 Only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0343] In an optional embodiment, the memory 3303 is configured to store programs, etc. Specifically, the programs can include program codes including computer operation instructions. The memory 3303 can include a RAM, and can also include a non-volatile memory such as one or more disk memories. The processor 3302 executes the application programs stored in the memory 3303 to implement the above functions, thereby implementing the functions of the communication apparatus 3300.

[0344] For example, the communication apparatus 3300 can be the terminal device in the above embodiments; and can also be the network device in the above embodiments.

[0345] In an embodiment, the communication apparatus 3300 implements the above functions by executing the programs stored in the memory 3303. Figure 14 ,Figure 16 、 Figure 18 or Figure 2 the terminal device, the transceiver 3301 can implement the transceiving operation (or transmission operation) performed by the terminal device in the embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 ; the processor 3302 can implement other operations performed by the terminal device in the embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 other than the transceiving operation. For specific descriptions, refer to the related descriptions in the above embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 , which are not described in detail here.

[0346] In an embodiment, when the communication apparatus 3300 implements the function of the network device in the embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 , the transceiver 3301 can implement the transceiving operation performed by the network device in the embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 ; the processor 3302 can implement other operations performed by the network device in the embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 other than the transceiving operation. For specific descriptions, refer to the related descriptions in the above embodiments of Figure 14 、 Figure 16 、 Figure 18 or Figure 2 , which are not described in detail here.

[0347] Based on the above embodiments, the embodiments of the present application further provide a communication system, which can include a terminal device and a network device, etc.

[0348] The embodiments of the present application further provide a computer readable storage medium for storing a computer program, which, when executed by a computer, can implement the uplink control information transmission method provided by the above method embodiments.

[0349] The embodiment of the present application further provides a computer program product for storing a computer program, which, when executed by a computer, can realize the transmission method of uplink control information provided by the method embodiment.

[0350] The embodiment of the present application further provides a chip comprising a processor coupled with a memory, for invoking a program in the memory to make the chip realize the transmission method of uplink control information provided by the method embodiment.

[0351] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) containing computer-usable program code.

[0352] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system) and computer program product according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device implemented in the flowcharts and / or block diagrams. Figure 14 one or more flows and / or blocks Figure 16 means for performing the function specified by the flow or flows and / or block or blocks.

[0353] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction means, which realizes the flowcharts and / or block diagrams. Figure 18 one or more flows and / or blocks Figure 2 means for performing the function specified by the flow or flows and / or block or blocks.

[0354] These computer program instructions can also be loaded into a computer or other programmable data processing apparatus, so that a series of operation steps are performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing apparatus provide a process for realizing the flowcharts and / or block diagrams. Figure 14 one or more flows and / or blocks Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figure 2 Figure 14 Figure 16 Figure 18 Figuresteps of the functions specified in the one or more blocks.

[0355] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the application. Thus, it is intended that the present application cover the modifications and variations of this application provided they come within the scope of the appended claims and their equivalents.

Claims

1. A method for transmitting uplink control information, characterized in that: include: When the relationship between the time domain position of the physical uplink control channel PUCCH containing uplink control information and the time domain position of the physical uplink shared channel PUSCH satisfies: The first condition, wherein the first condition includes the time domain position of the PUCCH being used for modulation The time domain position of the downlink control information DCI of the PUSCH is the same as the time domain position of the PUSCH Between, wherein the uplink control information includes hybrid automatic repeat request HARQ feedback, periodic One or more of the following: Channel State Information P-CSI report or Semi-Persistent Channel State Information SP-CSI report item; or, The time domain position of the PUSCH is before the time domain position of the PUCCH, and the uplink The time domain position of the physical downlink shared channel PDSCH corresponding to the control information is consistent with the time domain position of the PUSCH The time domain length between the domain positions is greater than or equal to the first time domain length, wherein the uplink control signal The information includes HARQ feedback; or, The time domain position of the PUSCH is before the time domain position of the PUCCH, and the uplink The time domain length between the time domain position of the channel state information reference signal CSI-RS corresponding to the control information and the time domain position of the PUSCH is greater than or equal to the second time domain length, wherein the uplink control The information includes a P-CSI report or a SP-CSI report; or, The time domain position of the PUCCH is before the time domain position of the PUSCH, and the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to the third time domain length. Field length, wherein the uplink control information includes HARQ feedback, P-CSI report or SP-CSI report one or more items in the report; The time domain position of the PUCCH and the time domain position of the PUSCH do not overlap; The terminal device transmits the uplink control information to the network device through the PUSCH.

2. The method according to claim 1, wherein The first condition also includes one or more of the following: The time domain length between the time domain position of the DCI and the time domain position of the PUCCH is greater than or equal to a fourth time domain length; or A time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to a fifth time domain length; or When the uplink control information includes a P-CSI report or an SP-CSI report, and the DCI triggers an aperiodic channel state information AP-CSI report, the report content of the P-CSI report or SP-CSI report included in the uplink control information is different from the report content of the AP-CSI report included in the PUSCH.

3. The method according to claim 2, wherein The fourth time domain length is the current minimum scheduling time slot interval.

4. The method according to any one of claims 1 to 3, wherein The terminal device transmitting the uplink control information to the network device through the PUSCH, including: The terminal device performs bit concatenation on the uplink control information and the information included in the PUSCH, and transmits the concatenation to the network device via the PUSCH; or The terminal device punctures the PUSCH, maps the uplink control information to the punctured position of the PUSCH, and transmits the uplink control information to the network device through the PUSCH.

5. The method according to claim 4, wherein The terminal device bit-concatenates the uplink control information and the information contained in the PUSCH, and transmits the bit-concatenated information to the network device through the PUSCH; wherein the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to a sixth time domain length; or the number of information bits of the uplink control information is greater than or equal to a first value; or The terminal device punctures the PUSCH, maps the uplink control information to the punctured position of the PUSCH, and transmits it to the network device through the PUSCH; wherein, the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than the sixth time domain length; or, the number of information bits of the uplink control information is less than the first value.

6. The method according to any one of claims 1 to 3, wherein: Before the terminal device transmits the uplink control information to the network device through the PUSCH, the method further includes: The terminal device determines that after receiving the reference signal from the network device, the reference signal received power RSRP sent to the network device is greater than the RSRP threshold, wherein the RSRP is determined by the terminal device based on the reference signal.

7. The method according to any one of claims 1 to 3, wherein: The terminal device transmitting the uplink control information to the network device through the PUSCH, including: The terminal device transmits the uplink control information to the network device through the PUSCH using a first transmission power; wherein the first transmission power is greater than the original transmission power of the PUSCH; or the first transmission power is determined based on the original transmission power of the PUSCH and the original transmission power of the PUCCH.

8. The method according to any one of claims 1 to 3, wherein: The terminal device transmitting the uplink control information to the network device through the PUSCH, including: The terminal device determines the first K bits according to the priority of the bits in the uplink control information from high to low; wherein the number of information bits of the uplink control information is greater than or equal to M, and K is less than or equal to M; The terminal device transmits the K bits to the network device through the PUSCH.

9. The method according to any one of claims 1 to 3, wherein: The method further comprises: When the uplink control information includes a P-CSI report or an SP-CSI report, and the DCI triggers a non-periodic channel state information AP-CSI report, and the report content of the P-CSI report or SP-CSI report included in the uplink control information is partially or completely identical to the report content of the AP-CSI report included in the PUSCH, the terminal device discards the uplink control information.

10. The method according to any one of claims 1 to 3, wherein The first time domain length conforms to the following formula: First time domain length = (N1 + d 1,1 +d2)(2048+144)·κ·2 -μ ·T C Wherein, N1 is the processing capability reported by the terminal device, and its value is related to the subcarrier spacing (SCS) or system parameters; 1,1 and d2 are related to the PDSCH mapping type and the symbol length occupied by PDSCH; μ is a system parameter; T c =1 / (Δf max ·N f ), where Δf max =480·103Hz, N f =4096;κ=T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz, N f,ref =2048.

11. The method according to any one of claims 1 to 3, wherein: The second time domain length conforms to the following formula: Second time domain length = (Z)(2048+144)·κ·2 -μ ·T C Where Z is a predefined value; T c =1 / (Δf max ·N f ), where Δf max =480·103Hz, N f =4096;κ=T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz, N f,ref =2048.

12. A method for transmitting uplink control information, characterized in that: include: When the relationship between the time domain position of the physical uplink control channel PUCCH containing uplink control information and the time domain position of the physical uplink shared channel PUSCH satisfies: The first condition includes that the time domain position of the PUCCH is used to schedule the The time domain position of the downlink control information DCI of PUSCH is between the time domain position of the PUSCH. The uplink control information includes hybrid automatic repeat request HARQ feedback, periodic channel status One or more items in a P-CSI report or a semi-persistent channel state information SP-CSI report; or The time domain position of the PUSCH is before the time domain position of the PUCCH, and the uplink The time domain position of the physical downlink shared channel PDSCH corresponding to the control information is consistent with the time domain position of the PUSCH The time domain length between the domain positions is greater than or equal to the first time domain length, wherein the uplink control signal The information includes the HARQ feedback; or, The time domain position of the PUSCH is before the time domain position of the PUCCH, and the uplink The time domain length between the time domain position of the channel state information reference signal CSI-RS corresponding to the control information and the time domain position of the PUSCH is greater than or equal to the second time domain length, wherein the uplink control The information includes the P-CSI report and / or the SP-CSI report; or, The time domain position of the PUCCH is before the time domain position of the PUSCH, and the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to the third time domain length. Field length, wherein the uplink control information includes HARQ feedback, P-CSI report or SP-CSI report one or more items in the report; The time domain position of the PUCCH and the time domain position of the PUSCH do not overlap; The network device receives the uplink control information transmitted by the terminal device through the PUSCH.

13. The method according to claim 12, wherein: The first condition also includes one or more of the following: The time domain length between the time domain position of the DCI and the time domain position of the PUCCH is greater than or equal to a fourth time domain length; or A time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than or equal to a fifth time domain length; or When the uplink control information includes a P-CSI report or an SP-CSI report, and the DCI triggers an aperiodic channel state information AP-CSI report, the report content of the P-CSI report or SP-CSI report included in the uplink control information is different from the report content of the AP-CSI report included in the PUSCH.

14. The method according to claim 13, wherein The fourth time domain length is the current minimum scheduling time slot interval.

15. The method according to any one of claims 12 to 14, wherein: The network device receiving the uplink control information transmitted by the terminal device through the PUSCH includes: The network device receives, through the PUSCH, information obtained by the terminal device performing bit concatenation on the uplink control information and information included in the PUSCH; or The network device receives, through the PUSCH, information obtained by the terminal device performing puncturing on the PUSCH and mapping the uplink control information to the position where the PUSCH is punctured.

16. The method according to claim 15, wherein The network device receives, through the PUSCH, information obtained by the terminal device performing bit concatenation on the uplink control information and the information contained in the PUSCH; wherein a time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is greater than or equal to a sixth time domain length; or, the number of information bits of the uplink control information is greater than or equal to a first value; or The network device receives, through the PUSCH, information obtained by the terminal device by puncturing the PUSCH and mapping the uplink control information to the position where the PUSCH is punctured; wherein the time domain length between the time domain position of the PUCCH and the time domain position of the PUSCH is less than the sixth time domain length; or, the number of information bits of the uplink control information is less than the first value.

17. The method according to any one of claims 12 to 14, wherein: Before the network device receives the uplink control information transmitted by the terminal device through the PUSCH, the method further includes: The network device determines that the reference signal received power RSRP from the terminal device is greater than an RSRP threshold, wherein the RSRP is sent by the terminal device after receiving the reference signal from the network device, and the RSRP is determined by the terminal device based on the reference signal.

18. The method according to any one of claims 12 to 14, wherein: The network device receiving the uplink control information transmitted by the terminal device through the PUSCH includes: The network device receives K bits of the uplink control information transmitted by the terminal device through the PUSCH, where the K bits are the first K bits determined by the terminal device according to the priority of the bits in the uplink control information from high to low; wherein the number of information bits of the uplink control information is greater than M, and K is less than or equal to M.

19. The method according to any one of claims 12 to 14, wherein: The method further comprises: When the uplink control information includes a P-CSI report or an SP-CSI report, and the DCI triggers an aperiodic channel state information AP-CSI report, and the report content of the P-CSI report or SP-CSI report included in the uplink control information is partially or completely identical to the report content of the AP-CSI report included in the PUSCH, the network device does not receive the uplink control information.

20. The method according to any one of claims 12 to 14, wherein: The first time domain length conforms to the following formula: First time domain length = (N1 + d 1,1 +d2)(2048+144)·κ·2 -μ ·T C Wherein, N1 is the processing capability reported by the terminal device, and its value is related to the subcarrier spacing (SCS) or system parameters; 1,1 and d2 are related to the PDSCH mapping type and the symbol length occupied by PDSCH; μ is a system parameter; T c =1 / (Δf max ·N f ), where Δf max =480·103Hz, N f =4096;κ=T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz, N f,ref =2048.

21. The method according to any one of claims 12 to 14, wherein: The second time domain length conforms to the following formula: Second time domain length = (Z)(2048+144)·κ·2 -μ ·T C Where Z is a predefined value; T c =1 / (Δf max ·N f ), where Δf max =480·103Hz, N f =4096;κ=T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz, N f,ref =2048.

22. A terminal device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store computer instructions; The processor is coupled to the memory and is configured to call computer instructions in the memory so that the terminal device executes the method according to any one of claims 1 to 11.

23. A network device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store computer instructions; The processor is coupled to the memory and is configured to call computer instructions in the memory to enable the network device to execute the method according to any one of claims 12 to 21.

24. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when called by the computer, are used to enable the computer to execute the method according to any one of claims 1 to 21.

Citation Information

Patent Citations

  • Method, device and system for sending uplink control information

    CN110798892A

  • Multiplexing method of Uplink Control Information (UCI)

    CN111726206A

  • Method, user equipment, device, and storage medium for performing uplink transmission, and method and base station for performing uplink reception

    WO2020197338A1