Uplink control information transmission method, device and related equipment

Abstract

This application discloses an uplink control information transmission method, apparatus, and related equipment, belonging to the field of communication technology. The method includes: a terminal determining at least one Physical Uplink Control Channel (PUCCH) cell corresponding to at least two uplink control information (UCIs) based on at least two UCIs; the terminal transmitting a first target UCI through a target PUCCH cell in the at least one PUCCH cell, wherein the first target UCI is determined based on the at least two UCIs.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an uplink control information transmission method, apparatus and related equipment. Background Technology

[0002] Regarding PUCCH carrier handover, current discussions primarily focus on HARQ-ACK feedback when using dynamic indication, with less attention paid to other UCI information types. When applying PUCCH carrier handover to HARQ-ACK feedback and involving the transmission of other UCI information types, there is currently no corresponding solution for the multiplexing operation between UCI information types. This results in limited transmission conditions or poor transmission performance when transmitting different types of UCI information. Summary of the Invention

[0003] This application provides an uplink control information transmission method, apparatus, and related equipment, which can solve the problem of limited transmission or poor transmission performance when transmitting different types of UCI information.

[0004] Firstly, an uplink control information transmission method is provided, including:

[0005] The terminal determines at least one Physical Uplink Control Channel (PUCCH) cell corresponding to at least two UCIs based on at least two UCIs.

[0006] The terminal transmits a first target UCI through a target PUCCH cell in at least one of the PUCCH cells, the first target UCI being determined based on the at least two UCIs.

[0007] Secondly, an uplink control information transmission method is provided, including:

[0008] The network-side equipment receives the first target UCI transmitted by the target physical uplink control channel (PUCCH) cell;

[0009] The target PUCCH cell is a cell among at least one PUCCH cells, and the at least one PUCCH cell is determined based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs.

[0010] Thirdly, an uplink control information transmission device is provided, comprising:

[0011] The determination module is used to determine at least one Physical Uplink Control Channel (PUCCH) cell corresponding to at least two UCIs based on at least two UCIs.

[0012] A transmission module is configured to transmit a first target UCI through a target PUCCH cell in the at least one PUCCH cell, the first target UCI being determined based on the at least two UCIs.

[0013] Fourthly, an uplink control information transmission device is provided, comprising:

[0014] The receiving module is used to receive the first target UCI transmitted by the terminal through the target physical uplink control channel (PUCCH) cell;

[0015] The target PUCCH cell is a cell among at least one PUCCH cells, and the at least one PUCCH cell is determined based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs.

[0016] Fifthly, a terminal is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the uplink control information transmission method as described in the first aspect.

[0017] In a sixth aspect, a network-side device is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the uplink control information transmission method as described in the second aspect.

[0018] In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the uplink control information transmission method as described in the first or second aspect.

[0019] Eighthly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network-side device programs or instructions to implement the uplink control information transmission method as described in the first or second aspect.

[0020] In this embodiment, the terminal determines at least one Physical Uplink Control Channel (PUCCH) cell corresponding to at least two UCIs based on at least two UCIs; the terminal transmits a first target UCI through a target PUCCH cell among the at least one PUCCH cells, the first target UCI being determined based on the at least two UCIs. Transmitting the first target UCI through the target PUCCH cell can improve the transmission performance of the at least two UCIs. Attached Figure Description

[0021] Figure 1This is a structural diagram of a network system provided in an embodiment of this application;

[0022] Figure 2 This is a flowchart of an uplink control information transmission method provided in an embodiment of this application;

[0023] Figures 3a-3c This is a flowchart of the fusion information acquisition process provided in the embodiments of this application;

[0024] Figure 4 This is another flowchart of the uplink control information transmission method provided in the embodiments of this application;

[0025] Figure 5 This is a structural diagram of the uplink control information transmission device provided in the embodiments of this application;

[0026] Figure 6 This is another structural diagram of the uplink control information transmission device provided in the embodiments of this application;

[0027] Figure 7 This is a structural diagram of the communication device provided in the embodiments of this application;

[0028] Figure 8 This is a structural diagram of the terminal provided in the embodiments of this application;

[0029] Figure 9 This is a structural diagram of the network-side device provided in the embodiments of this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0031] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship. In this application, "transmission" refers to the transmission of a signal, not signal sending in the narrow sense.

[0032] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0033] Figure 1This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this embodiment of the application, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0034] The uplink control information transmission method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0035] Please see Figure 2 , Figure 2 This is a flowchart of an uplink control information transmission method provided in an embodiment of this application. The uplink control information transmission method includes:

[0036] Step 201: The terminal determines at least one Physical Uplink Control Channel (PUCCH) cell corresponding to the at least two UCIs based on at least one Uplink control information (UCI).

[0037] The at least two UCIs may include two or more UCIs. The terminal determines the PUCCH cell (hereinafter, the PUCCH cell is also referred to as PUCCH cell) for transmitting each UCI based on each UCI.

[0038] Step 202: The terminal transmits a first target UCI through the target PUCCH cell in the at least one PUCCH cell, and the first target UCI is determined based on the at least two UCIs.

[0039] After determining at least one PUCCH cell, the terminal selects a target PUCCH cell from the at least one PUCCH cell to transmit a first target UCI. The first target UCI is determined based on the at least two UCIs; for example, the first target UCI may include some or all of the at least two UCIs.

[0040] In this embodiment, the terminal determines at least one PUCCH cell corresponding to at least two uplink control information (UCIs) based on at least two UCIs. The terminal transmits a first target UCI through a target PUCCH cell among the at least two PUCCH cells, and the first target UCI is determined based on the at least two UCIs. Transmitting the first target UCI through the target PUCCH cell can improve the transmission performance of the at least two UCIs.

[0041] In the above, the UCI includes at least one of the following:

[0042] Hybrid automatic repeat request acknowledgement (HARQ-ACK);

[0043] Scheduling request (SR);

[0044] Channel State Information (CSI).

[0045] This can also be understood as the UCI information type including at least one of HARQ-ACK, SR, and CSI. For example, if UCI1 includes HARQ-ACK1 and SR1, and UCI2 includes HARQ-ACK2, then both UCI1 and UCI2 include the HARQ-ACK information type.

[0046] Specifically, the HARQ-ACK type can include at least one of dynamic scheduling HARQ-ACK and semi-static scheduling (SPS) HARQ-ACK. Dynamic scheduling HARQ-ACK includes HARQ-ACK corresponding to fallback DCI and HARQ-ACK corresponding to non-fallback downlink control information (DCI). Fallback DCI-related HARQ-ACKs include, for example, HARQ-ACK feedback corresponding to PDSCH transmissions scheduled in DCI format 1_0 or indicated SPS releases. Non-fallback DCI-related HARQ-ACKs include, for example, HARQ-ACK feedback corresponding to PDSCH transmissions scheduled in DCI format 1_1 or DCI format 1_2 or indicated SPS releases.

[0047] For SR types, it can include at least one of SR and Link Recovery Request (LRR).

[0048] For CSI types, at least one of Periodic CSI, Semi-persistent CSI, and Aperiodic CSI may be included.

[0049] For each of the at least two UCIs, the UCI information type included in the UCI may include at least one of HARQ-ACK, SR, and CSI. Different UCIs may include different UCI information types.

[0050] When determining at least one PUCCH cell based on the at least two UCIs, the determination can be based on the type of UCI information included in the UCI. For example, the PUCCH cell corresponding to a certain UCI information type can be understood as the PUCCH cell where the corresponding PUCCH resource / transmission is located when this type of UCI information is transmitted alone.

[0051] The PUCCH cell corresponding to each UCI information type is determined as follows:

[0052] HARQ-ACK Type: For dynamically scheduled HARQ-ACK, when using Non-fallback DCI, the dynamically scheduled DCI can indicate the PUCCH cell corresponding to the dynamically scheduled HARQ-ACK; when using Fallback DCI, if the corresponding dynamically scheduled HARQ-ACK and the dynamically scheduled HARQ-ACK corresponding to the Non-fallback DCI are multiplexed (i.e., contained in the same HARQ-ACK codebook), then the PUCCH cell indicated by one of the Non-fallback DCIs can be used (it can be further assumed that one or more Non-fallback DCIs corresponding to this HARQ-ACK codebook typically indicate the same PUCCH cell, then the aforementioned Non-fallback DCI can be any of these one or more Non-fallback DCIs); optionally, when these one or more Non-fallback DCIs indicate different PUCCH cells, the PUCCH cell indicated by the last Non-fallback DCI can be used, that is, the HARQ-ACK codebook in the last Non-fallback DCI... Transmitted on the PUCCH cell indicated by the DCI), when the corresponding dynamic scheduling HARQ-ACK and the dynamic scheduling HARQ-ACK corresponding to the Non-fallback DCI are not multiplexed (i.e., all DCIs corresponding to the HARQ-ACK codebook corresponding to a certain Fallback DCI are Fallback DCIs), the PUCCH cell corresponding to the corresponding dynamic scheduling HARQ-ACK (or the HARQ-ACK codebook in which it is located) can be determined using the SPS HARQ-ACK carrier mode 2 described below.

[0053] For SPS HARQ-ACK, the corresponding PUCCH cell can be determined using any of the following methods:

[0054] SPS HARQ-ACK carrier mode 1: Dynamic indication of DCI activated / reactivated by SPS.

[0055] SPS HARQ-ACK carrier mode 2: Feedback is fixed on a certain PUCCH cell, such as PCell / PSCell / PUCCH SCell, which can be specified by the protocol or configured based on higher layer signaling.

[0056] When an SPS HARQ-ACK is multiplexed with another SPS HARQ-ACK or a dynamically scheduled HARQ-ACK, the selection / determination of the PUCCH cell corresponding to the multiplexed HARQ-ACK bit sequence can be determined according to predefined rules.

[0057] SR type: When an SR configuration (Config) is triggered, the PUCCH cell corresponding to the PUCCH transmission of a scheduling request resource configuration (scheduling request resource configuration) associated with this SR configuration is the PUCCH cell where the scheduling request resource configuration is located (or the corresponding PUCCH cell) (i.e., this PUCCH configuration is configured under a certain UL BWP of the Serving cell corresponding to this PUCCH cell).

[0058] CSI type: The PUCCH cell corresponding to the CSI report is the PUCCH cell where the CSI reporting configuration (Report Config) corresponding to periodic CSI or semi-persistent CSI on PUCCH is located (i.e., this CSI reporting configuration is configured under the serving cell corresponding to this PUCCH cell).

[0059] In other words, the at least one PUCCH cell corresponding to the at least two UCIs can be determined as follows:

[0060] In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI.

[0061] In the case where the at least two UCIs include a second dynamic scheduling HARQ-ACK and at least one third dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes the PUCCH cell corresponding to the second dynamic scheduling HARQ-ACK, the second dynamic scheduling HARQ-ACK is indicated by a second type DCI, the third dynamic scheduling HARQ-ACK is indicated by a first type DCI, and the second dynamic scheduling HARQ-ACK and the at least one third dynamic scheduling HARQ-ACK are transmitted in the same HARQ-ACK codebook.

[0062] In the case where the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, the at least one PUCCH cell includes a PUCCH cell as specified in the protocol or configured based on higher-layer signaling.

[0063] In the case where at least two UCIs include SPS HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell dynamically indicated by SPS activation or reactivation DCI.

[0064] In the case where the at least two UCIs include an SR corresponding to an SR configuration, the at least one PUCCH cell includes the PUCCH cell corresponding to the first PUCCH transmission, wherein the first PUCCH transmission is a PUCCH transmission corresponding to a scheduling request resource configuration associated with an SR configuration.

[0065] In the case where the at least two UCIs include periodic CSIs, the at least one PUCCH cell includes a PUCCH cell configured with a first CSI reporting configuration, wherein the first CSI reporting configuration is the CSI reporting configuration corresponding to the periodic CSI carried by the PUCCH.

[0066] In the case where at least two UCIs include semi-persistent CSI, the at least one PUCCH cell includes a PUCCH cell configured with a second CSI reporting configuration, wherein the second CSI reporting configuration is the CSI reporting configuration corresponding to the semi-persistent CSI carried by the PUCCH.

[0067] In the above, in the first type of DCI, the indicator field can explicitly indicate the PUCCH cell corresponding to the dynamic scheduling HARQ-ACK (i.e., the PUCCH cell carrying this dynamic scheduling HARQ-ACK), such as Non-fallback DCI.

[0068] In the second type of DCI, there is no indication field to explicitly indicate the PUCCH cell corresponding to its dynamic scheduling HARQ-ACK (i.e., the PUCCH cell carrying this dynamic scheduling HARQ-ACK), such as in Fallback DCI.

[0069] For a PUCCH cell group configured for a UE, assuming that there is at least one serving cell that can be used to transmit PUCCH to respond with HARQ-ACK, it can be called a PUCCH cell.

[0070] The following explains the various scenarios of UCI transmission.

[0071] In the first case, only HARQ-ACK type is transmitted. For dynamically scheduled HARQ-ACK, at most a single PUCCH cell will transmit the codebook corresponding to the dynamically scheduled HARQ-ACK at any given time (e.g., within a time slot or sub-time slot).

[0072] For Non-fallback DCI, the aforementioned single PUCCH cell can be directly indicated by DCI. When indicating or understanding K1, refer to the K1 Set configured / applied for the aforementioned single PUCCH cell (e.g., the PUCCH-Config->dl-DataToUL-ACK parameter).

[0073] For Fallback DCI, the determination of the above single PUCCH cell can be as follows: when multiplexing with HARQ-ACK not corresponding to Non-fallback DCI, it is determined based on SPS HARQ-ACK carrier mode 2; when multiplexing, it is determined based on the PUCCH cell indicated by Non-fallback DCI. The K1 Set used can still follow the preset rules, for example, {1,2,3,4,5,6,7,8}.

[0074] To avoid missed detections in DCI and the impact of different K1 Sets in different PUCCH cell configurations or applications, it is required that the PUCCH cells indicated in the dynamically scheduled DCIs (which can be understood as Non-fallback DCIs) pointing to the same time (e.g., pointing to the same Slot / Sub-slot) be consistent. For Fallback DCIs, to avoid changes in the corresponding PUCCH cells (and the corresponding changes in the temporal feedback position when the SCS / Numerology of the PUCCH cell is different), the network can handle / solve this based on its implementation. For example, for a certain HARQ-ACK codebook, one or more Non-fallback DCIs are first used to determine its corresponding PUCCH cells, and then Fallback DCIs are used as needed to indicate the HARQ-ACKs that need to be further reused on this HARQ-ACK codebook. Alternatively, all scheduling can be done using Fallback DCIs (in which case the corresponding PUCCH cells do not depend on the indication of the Non-fallback DCIs).

[0075] For SPS HARQ-ACK, when multiplexing does not occur, SPS HARQ-ACK can be transmitted on its corresponding PUCCH cell.

[0076] When an SPS HARQ-ACK is multiplexed with another SPS HARQ-ACK or a dynamically scheduled HARQ-ACK, the selection / determination of the PUCCH cell corresponding to the multiplexed HARQ-ACK bit sequence can be based on predefined rules.

[0077] In the second case, reuse between two or more UCI information types (including or excluding HARQ-ACK).

[0078] When PUCCH resources carrying different UCI information types are located on the same or different PUCCH cells and have temporal overlap, multiplexing of these UCI information types can be considered. It is important to note that these PUCCH resources may be located in different PUCCH cells, and their corresponding subcarrier spacing (SCS) or parameter sets (Numerology) may also be different. Temporal overlap can be determined based on absolute time; that is, whether temporal overlap exists between two PUCCH resources (or transmissions) can be determined based on whether there is an overlap between the corresponding time periods of these two PUCCH resources (or transmissions). If the time periods overlap, it can be determined that temporal overlap exists. The above method of determining temporal overlap based on absolute time can be applied to determining temporal overlap between PUCCH resources located in different PUCCH cells, as well as between PUCCH resources located in the same PUCCH cell.

[0079] When the reuse of different UCI information types involves HARQ-ACK information, after determining the HARQ-ACK (including the HARQ-ACK codebook / bit sequence to be transmitted, as well as the corresponding PUCCH cell and PUCCH resources, etc.), further consideration can be given to whether and how to reuse it with other UCI information types.

[0080] When PUCCH resources that need to be reused due to time-domain overlap (each corresponding to different UCI information or UCI information type) are all located (or correspond to) the same PUCCH cell, a preset rule, such as the first preset rule, is used to determine the transmission method.

[0081] When at least one PUCCH resource (corresponding to different UCI information or UCI information types) that needs to be reused based on temporal overlap is located in (or corresponds to) different PUCCH cells, any of the following methods can be used:

[0082] At any given time, only a single PUCCH cell can transmit, or multiple PUCCH cells can transmit in parallel.

[0083] The two methods described above will be explained below.

[0084] The first method involves a maximum of only one PUCCH cell transmitting at any given time. In this case, the terminal transmits the first target UCI through the target PUCCH cell in the at least one PUCCH cell, including:

[0085] The terminal transmits the first target UCI through a target PUCCH cell among the at least two PUCCH cells. The target PUCCH cell is one of the at least two PUCCH cells, and the first target UCI is determined based on the at least two UCIs. The PUCCH resources carrying the at least two UCIs overlap in the time domain, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

[0086] In one scenario, the first target UCI is determined based on the attributes and temporal overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule; the target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

[0087] For two or more PUCCH resources (or transmissions) that overlap in the time domain and carry their own UCIs, they can be located on different PUCCH cells within the same PUCCH cell group, as long as the time domain overlap condition is met. Once the first preset rule determines which PUCCH resource to use and which UCIs to transmit, the finally determined PUCCH resource can be used directly to perform the corresponding PUCCH transmissions on its corresponding PUCCH cell and within its Slot / Sub-slot.

[0088] The first preset rule is illustrated with the following example.

[0089] The following situations can be distinguished:

[0090] Scenario 1: In PUCCH, multiplex HARQ-ACK and SR, or CSI and SR.

[0091] Specifically, for a single Positive / Negative SR (regardless of PUCCH format) and Format0 HARQ-ACK (N<=2), HARQ-ACK is fed back on the Format0 HARQ-ACK resource: when it is a Positive SR, CS (Cyclic Shift) is adjusted; otherwise (when it is a Negative SR), CS is not adjusted.

[0092] For Format0 Positive / Negative SR and Format1 HARQ-ACK (N<=2),

[0093] HARQ-ACK is transmitted normally on Format1 HARQ-ACK resources, and SR is ignored.

[0094] For Format1 Positive / Negative SR and Format1 HARQ-ACK (N<=2), when it is a Positive SR, HARQ-ACK is fed back on the SR resource; otherwise (when it is a Negative SR), HARQ-ACK is fed back on the HARQ-ACK resource.

[0095] For Format2 / 3 / 4 HARQ-ACK and K SR resources, the SR indicator bit is appended to the tail of the HARQ-ACK bit, and the HARQ-ACK PUCCH resource is dynamically scheduled using the Last DCI indicator.

[0096] For Format2 / 3 / 4CSI and K SR resources, the SR indicator bit is placed before the CSI bit, and the PUCCH resource reported by CSI is used.

[0097] Scenario 2: Multiplexing HARQ-ACK, SR, and CSI in PUCCH.

[0098] If there is no HARQ-ACK, or only SPS HARQ-ACK (1 bit), and CSI (wideband or subband report) is transmitted, then the transmission is multiplexed on the CSI PUCCH resource.

[0099] There is a HARQ-ACK for the DCI response (i.e., there is a dynamically scheduled HARQ-ACK), and the transmission is multiplexed on the HARQ-ACK PUCCH resource indicated by the Last DCI.

[0100] Scenario 3: Two physical layer priorities can be configured. For each UCI information type and each PUCCH / PUSCH transmission, the corresponding physical layer priority can be specified, configured, or dynamically indicated. CSI reporting always belongs to the lower physical layer priority.

[0101] When there is temporal overlap between PUCCH / PUSCH transmissions of different physical layer priorities, only the PUCCH / PUSCH transmissions corresponding to the higher physical layer priority are transmitted, while the PUCCH / PUSCH transmissions corresponding to the lower physical layer priority are discarded. Within the same physical layer priority, the preset rules are followed, such as performing the corresponding operations according to Case 1 or Case 2 above.

[0102] In another case, the first target UCI includes one of the following:

[0103] The fusion information obtained by fusing the UCIs from the at least two UCIs;

[0104] A portion of the UCIs selected from the at least two UCIs.

[0105] In the above, the fusion information is determined according to any of the following methods:

[0106] Method 1: For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information.

[0107] Specifically, for each of the at least two PUCCH cells, if the number of UCIs corresponding to the PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell; if the number of UCIs corresponding to the PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

[0108] For example, for each PUCCH cell (i.e., the PUCCH cell in the at least two PUCCH cells), the bit sequence of UCIs to be transmitted and the PUCCH resources are first determined based on a first preset rule. Then, the bit sequences of UCIs corresponding to each PUCCH cell are concatenated end-to-end based on a second preset rule to obtain fusion information. The second preset rule can be ascending or descending order of the index values ​​corresponding to the PUCCH cells.

[0109] The index value corresponding to the PUCCH cell can be understood as the cell index value corresponding to the PUCCH cell, or the uplink serving cell index value corresponding to the PUCCH cell, or the local index value of the PUCCH cell in the set of cells that are allowed to transmit PUCCH. It can be numbered starting from 0. The index value corresponding to the PUCCH cell mentioned in this article follows the description here.

[0110] Optionally, the bit sequence of the UCI to be transmitted for each PUCCH cell can be directly obtained by concatenating the bit sequences of various UCIs to be transmitted on the PUCCH cell according to a first preset rule. That is, the bit sequences of all information types of UCIs existing in the PUCCH cell are concatenated according to the first preset rule. If a certain type of UCI does not exist in the PUCCH cell, then this type of UCI information is ignored or skipped during concatenation. For example, the bit sequences corresponding to HARQ-ACK, SR, CSI part 1, and CSI part 2 are concatenated sequentially. Figure 3a As shown, the bit sequence of the UCI to be transmitted corresponding to each PUCCH cell is directly obtained by concatenating the first and last bit sequences corresponding to each UCI.

[0111] Method 2: Based on the at least two UCIs, determine the M UCI categories that need to be transmitted. For the first UCI category among the M UCI categories, concatenate the second UCIs corresponding to each first PUCCH cell according to the second preset rule to obtain the third UCI corresponding to the first UCI category. Then, concatenate the third UCIs corresponding to each UCI category according to the third preset rule to obtain the fusion information.

[0112] The UCI category includes a UCI information type or a UCI transmission requirement, where M is an integer greater than or equal to 1. The first UCI category is any one of the M UCI categories. The first PUCCH cell is any one of the at least two PUCCH cells that has at least one UCI corresponding to the first UCI category. The second UCI corresponding to the first PUCCH cell is determined based on the second target UCI corresponding to the first PUCCH cell. The second target UCI includes at least one UCI corresponding to the first UCI category. The first UCI category may include one information type or two or more information types. For example, the first UCI category may include HARQ-ACK, or it may include HARQ-ACK and SR.

[0113] For example, if there are three types of UCI information: HARQ-ACK, SR, and CSI, for HARQ-ACK, the UCIs corresponding to each PUCCH cell are filtered to select the PUCCH cell containing the HARQ-ACK UCI. The selected PUCCH cell is called the first PUCCH cell. For the HARQ-ACKs on each first PUCCH cell, the first and second parts are concatenated according to the second preset rule to obtain the third UCI. The second preset rule is the concatenation rule across cells.

[0114] For SR, the UCI corresponding to each PUCCH cell is filtered, and the PUCCH cell containing the UCI of the SR is selected. The selected PUCCH cell is called the first PUCCH cell. For the SR on each first PUCCH cell, the first and second positions are concatenated according to the second preset rule to obtain the third UCI.

[0115] For CSI, the UCI corresponding to each PUCCH cell is filtered, and the PUCCH cell containing the UCI including CSI is selected. The selected PUCCH cell is called the first PUCCH cell. For the CSI on each first PUCCH cell, the first and second positions are concatenated according to the second preset rule to obtain the third UCI.

[0116] The three third UCIs obtained under the above three types are concatenated end-to-end based on the third preset rule to obtain the fused information.

[0117] In the above, when the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; when the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the fourth preset rule based on the UCI corresponding to the first PUCCH cell.

[0118] For example, bit sequences of UCIs of the same type or with the same transmission requirements from the at least two UCIs can be concatenated across PUCCH cells according to a second preset rule. Then, the concatenated output bit sequences of different types or transmission requirements (i.e., the output of the first concatenation operation) can be concatenated again according to a third preset rule to obtain fused information. Before processing based on the second preset rule, if the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the UCI corresponding to the first PUCCH cell according to a fourth preset rule.

[0119] For example, Figure 3b In this process, various UCI information types are first concatenated across the PUCCH cell, and then the concatenated output bit sequences corresponding to each UCI information type are concatenated. For example... Figure 3bAs shown, firstly, the HARQ-ACK, SR, CSI part 1, and CSI part 2 corresponding to each PUCCH cell are concatenated end-to-end based on the PUCCH cell index in ascending or descending order. For a certain UCI information type, if there is no corresponding UCI information to be transmitted on a certain PUCCH cell, this PUCCH cell is ignored (or skipped). Then, the concatenated output bit sequences corresponding to HARQ-ACK, SR, CSI part 1, and CSI part 2 are concatenated end-to-end according to a third preset rule. That is, the concatenated output bit sequences of all information types of UCI with concatenated output bit sequences are concatenated end-to-end according to the third preset rule. If a certain information type of UCI does not have a concatenated output bit sequence, this UCI information type is ignored or skipped during concatenation. For example, the concatenated output bit sequences corresponding to HARQ-ACK, SR, CSI part 1, and CSI part 2 are concatenated end-to-end sequentially. Optionally, only the concatenated output bit sequences corresponding to HARQ-ACK, SR, and CSI part 1 can be concatenated to form a single bit sequence, while CSI part 2 corresponds to another bit sequence on its own.

[0120] For example, Figure 3c In this process, first, UCI information types with the same transmission requirements corresponding to each PUCCH cell are concatenated end-to-end. Then, UCI bit sequences with different transmission requirements are concatenated end-to-end across PUCCH cells. For example... Figure 3cAs shown, for each PUCCH cell, its corresponding HARQ-ACK, SR, and CSI part 1 are concatenated end-to-end according to the fourth preset rule (assuming that the transmission requirements of these UCI information types are the same and can be jointly encoded). For example, assuming that the UCI transmission requirements of these information types HARQ-ACK, SR, and CSI part 1 are the same, the bit sequences corresponding to HARQ-ACK, SR, and CSI part 1 are concatenated end-to-end in sequence to obtain the joint bit sequence corresponding to each PUCCH cell. That is, the bit sequences of UCIs with bit sequences in these information types HARQ-ACK, SR, and CSI part 1 are concatenated end-to-end according to the fourth preset rule. If a certain information type does not have a bit sequence, this UCI information type is ignored or skipped during concatenation. Then, the joint bit sequences corresponding to each PUCCH cell are concatenated end-to-end according to the PUCCH cell index in ascending or descending order to obtain the first UCI bit sequence. The CSI part 2 corresponding to each PUCCH cell can also be concatenated end-to-end according to the PUCCH cell index in ascending or descending order to obtain the second UCI bit sequence. Optionally, the first UCI bit sequence and the second UCI bit sequence can be further concatenated end to end to form a single UCI bit sequence.

[0121] The first target UCI may include a subset of UCIs selected from the at least two UCIs. The subset of UCIs includes any one of the following:

[0122] The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells;

[0123] The UCI of the corresponding target type in at least two UCIs;

[0124] The UCI among the at least two UCIs has the target transmission requirement.

[0125] Specifically, the UCIs corresponding to the second PUCCH cell in the at least two PUCCH cells are selected, meaning all UCIs to be transmitted corresponding to a single PUCCH cell are chosen, and the UCIs to be transmitted corresponding to other PUCCH cells are discarded and not transmitted. For the UCIs corresponding to the selected single PUCCH cell, the actual transmitted UCI bit sequence can be determined based on a first preset rule, or the UCIs to be transmitted can be concatenated end-to-end based on a predefined order / rule.

[0126] The selection of a single PUCCH cell can be done in any of the following ways:

[0127] Based on the PUCCH cell index. For example, from the at least two PUCCH cells, the PUCCH cell with the largest corresponding index value, or the PUCCH cell with the smallest corresponding index value, or the PUCCH cell with a preset index value, is selected to transmit its corresponding UCI to be transmitted. The preset index value can be specified by the protocol or based on higher-layer signaling configuration. For example, when there is time-domain overlap in UCI transmissions on more than one PUCCH cell, the PUCCH cell and / or PUCCH resources are selected by higher-layer signaling configuration.

[0128] The selection of a PUCCH cell is based on physical layer priority, meaning it is chosen from at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs. For example, a PUCCH cell with a higher physical layer priority or the highest physical layer priority can be selected. This involves first determining the physical layer priority or the highest physical layer priority corresponding to the UCI to be transmitted for each PUCCH cell, and then selecting the PUCCH cell with the higher physical layer priority or the highest physical layer priority from these multiple PUCCH cells. If multiple PUCCH cells are still selected, the selection can be further based on the PUCCH cell index or on a separately configured cell priority.

[0129] When the selected PUCCH cell corresponds to two physical layer priorities for the UCI to be transmitted, it is possible to transmit the UCI information corresponding to both physical layer priorities simultaneously (considering the multiplexing across physical layer priorities), or only transmit the UCI information corresponding to the higher physical layer priority.

[0130] The PUCCH cell is selected based on a separately configured cell priority, that is, according to the cell priority configured for each of the at least two PUCCH cells. For example, a cell priority can be configured for each PUCCH cell. A PUCCH cell is selected from the at least two PUCCH cells based on the cell priority, such as selecting the PUCCH cell with the highest, lowest, or a specified cell priority value.

[0131] The selection is based on the resource availability of each PUCCH cell, specifically, the PUCCH cell selected according to the resource availability information of each of the at least two PUCCH cells. For example, a PUCCH cell whose time-domain feedback position contains an uplink symbol, or whose corresponding PUCCH resources are actually available for transmission, is selected. If multiple PUCCH cells are still selected based on resource availability, a further selection can be made based on the PUCCH cell index or a separately configured cell priority.

[0132] Alternatively, only the UCIs corresponding to certain UCI information types in the UCIs to be transmitted for the second PUCCH cell can be transmitted, and the remaining UCIs can be discarded. For example, only HARQ-ACK and SR can be transmitted, and CSI can be discarded, or only HARQ-ACK, SR and CSI part 1 can be transmitted, and CSI part 2 can be discarded.

[0133] The target PUCCH cell described above can be determined based on any of the following methods:

[0134] The selection is based on the PUCCH cell index, meaning the target PUCCH cell can be a PUCCH cell selected from at least two PUCCH cells according to its index value. For example, the PUCCH cell with the smallest, largest, or specified PUCCH cell index can be selected from these multiple PUCCH cells.

[0135] The selection is based on physical layer priority. The target PUCCH cell can be selected from at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs. For example, a PUCCH cell with a higher physical layer priority or the highest physical layer priority can be selected. This involves first determining the physical layer priority or the highest physical layer priority corresponding to the UCI to be transmitted for each PUCCH cell, and then selecting the PUCCH cell with the higher physical layer priority or the highest physical layer priority from these multiple PUCCH cells. If multiple PUCCH cells are still selected, the PUCCH cell can be further selected based on the PUCCH cell index or based on a separately configured cell priority.

[0136] When the selected PUCCH cell corresponds to two physical layer priorities for the UCI to be transmitted, it is possible to transmit the UCI information corresponding to both physical layer priorities simultaneously (considering the multiplexing across physical layer priorities), or only transmit the UCI information corresponding to the higher physical layer priority.

[0137] The selection is based on individually configured cell priorities, meaning the target PUCCH cell can be selected from at least two PUCCH cells according to the cell priorities configured for each PUCCH cell. For example, a cell priority can be configured for each PUCCH cell. A PUCCH cell is selected from the at least two PUCCH cells based on the cell priority, such as selecting the PUCCH cell with the highest, lowest, or a specified cell priority value.

[0138] The selection is based on resource availability, meaning the target PUCCH cell can be selected from at least two PUCCH cells based on their resource availability information. For example, a PUCCH cell whose time-domain feedback location contains an uplink symbol, or whose corresponding PUCCH resources are actually available for transmission, can be selected. If multiple PUCCH cells are still selected based on resource availability, a further selection can be made based on the PUCCH cell index or a separately configured cell priority.

[0139] Select the second PUCCH cell from the at least two PUCCH cells, where the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell. If the first target UCI includes some UCIs, directly select the PUCCH cell corresponding to those partial UCIs.

[0140] Select the third PUCCH cell from the at least two PUCCH cells. The third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK. When the codebook corresponding to the dynamically scheduled HARQ-ACK is transmitted on a certain PUCCH cell, this PUCCH cell is directly selected.

[0141] The second approach involves multiple PUCCH cells transmitting in parallel. In this case, the terminal transmits the first target UCI through a target PUCCH cell in the at least one PUCCH cell, including:

[0142] During the time-domain overlap period, the terminal transmits the at least two UCIs in parallel through the at least two PUCCH cells. Specifically, the PUCCH resources carrying the at least two UCIs have time-domain overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

[0143] For each PUCCH cell with a UCI to be transmitted, the bit sequence of the UCI and the PUCCH resources to be transmitted can be determined based on a first preset rule. When the PUCCH resources corresponding to each PUCCH cell overlap in the time domain, parallel PUCCH transmission with partial or complete overlap in the time domain is allowed for these PUCCH cells.

[0144] In one embodiment of this application, before the terminal determines at least one PUCCH cell corresponding to the at least two UCIs based on the at least two UCIs, the method further includes:

[0145] Receive resource configuration information from UCI.

[0146] The resource configuration information includes at least one of the following:

[0147] The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell;

[0148] The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1;

[0149] The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

[0150] The following sections explain the configuration of SR resources and CSI resources respectively.

[0151] For SR resource configurations, an SR configuration can be associated with one or more (single) scheduling request resource configurations configured on one or more BWPs of one or more PUCCH cells.

[0152] PUCCH carrier switching includes dynamic mode (Alt.1) and semi-static mode (Alt.2C).

[0153] When using the PUCCH carrier switching dynamic mode, a single SR configuration can be associated with the scheduling request resource configuration configured on one or more BWPs of a single PUCCH cell. This scheduling request resource configuration can be a single scheduling request resource configuration.

[0154] When using a semi-static PUCCH carrier switching method, a single SR configuration can be associated with scheduling request resource configurations configured on one or more BWPs of multiple PUCCH cells. For example, it can be associated with N PUCCH cells, where N is the number of PUCCH cells contained in the union of PUCCH cells that are active or available in different time periods based on a time domain pattern. The N PUCCH cells are those contained in the aforementioned union. The time domain pattern can be configured uniformly for M PUCCH cells within the current PUCCH cell group, or it can be configured separately for each PUCCH cell.

[0155] When using PUCCH carrier switching Alt.2C, when the SR transmission corresponding to this SR configuration is triggered (for example, when one or more logical channels associated with this SR configuration trigger Regular BSR and no suitable UL-SCH resources are available, the PUCCH cell corresponding to the PUCCH transmission carrying the SR (hereinafter referred to as SR PUCCH) can be determined based on the Time domain pattern (optionally, it can also be unconstrained by the Time domain pattern).

[0156] Specifically, when a scheduling request resource configuration associated with an SR configuration is configured on the active BWP of a PUCCH cell that is determined to be active or available based on the time domain pattern, the SR PUCCH is transmitted based on the period and offset configured for this scheduling request resource configuration and the PUCCH resource. During multiple consecutive transmissions of the SR PUCCH, if the active / available PUCCH cell changes based on the time domain pattern, the SR PUCCH transmission is switched / transferred from at least one PUCCH cell (i.e., the PUCCH cell that was active / available before the change) to at least another PUCCH cell (i.e., the PUCCH cell that is active / available after the change). When no scheduling request resource configuration associated with this SR configuration is configured on the active BWP of any PUCCH cell after the change, the SR transmission is interrupted or suspended.

[0157] For each scheduling request resource configuration associated with the same SR configuration, the period and offset configuration can be done in any of the following ways (applicable when using PUCCH carrier switching Alt.1 or Alt.2C; for operations that only apply to one case, the corresponding explanation will be given below):

[0158] Configuration Method 1: Period and offset are configured uniformly, based on a reference SCS or reference parameter set. That is, when the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations: the period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are configured uniformly based on the reference subcarrier interval or reference parameter set.

[0159] This is mainly to ensure the strict periodicity of SR transmission. When PUCCH cell switching and / or BWP switching occur during multiple consecutive SR PUCCH transmissions, it can be guaranteed that the time interval between adjacent SR PUCCH transmissions is equal or substantially equal (the time interval of the SR PUCCH Resource configured on each PUCCH cell and / or BWP is equal).

[0160] Optionally, when a single time unit determined based on the reference subcarrier spacing or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration. The fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations. The time unit may include a slot or a sub-slot.

[0161] For example, when a reference slot (i.e., a single slot determined based on Reference SCS / Numerology) corresponds to multiple uplink slots / sub-slots on a valid PUCCH cell (on which SR PUCCH resources are configured), and SR PUCCH needs to be transmitted on this PUCCH cell:

[0162] For any SR PERIODICITY Configuration,

[0163] To determine which uplink slot / sub-slot among these multiple uplink slots / sub-slots to select for transmitting the SR PUCCH, any of the following methods can be used:

[0164] Select a slot / sub-slot that meets predefined conditions. If multiple slots / sub-slots meet the predefined conditions, the earliest slot / sub-slot among them can be selected. For example, select the first / last / specified index slot / sub-slot among these multiple upstream slots / sub-slots. In other words, the target time unit includes the following:

[0165] The time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0166] The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0167] The first time unit among the plurality of time units;

[0168] The last time unit among the plurality of time units;

[0169] The time unit corresponding to the first specified index among the plurality of time units.

[0170] The predefined condition can be: sufficient to accommodate the SR PUCCH resources to be transmitted. The determination of these PUCCH resources requires ensuring that the corresponding PUCCH transmission can actually be executed; for example, the PUCCH resources do not overlap or conflict with Semi-static DL symbols / SSB / CORESET#0.

[0171] Optionally, when SR PERIODICITY When using sym2 or sym6or7, any of the following methods can be used:

[0172] Configuration method 1-1: This periodic configuration is not allowed to avoid corresponding processing;

[0173] Configuration method 1-2: Requires the start time or absolute start time of the SR PUCCH resources on each PUCCH cell associated with the same SR configuration to be aligned, and the interval between the start times of adjacent PUCCH resources or transmission occupancy is SR. PERIODICITY The corresponding absolute duration (which can be determined based on Reference SCS or parameter set) ensures the periodicity between temporally adjacent SR PUCCH Resources during PUCCH cell switching and / or BWP switching.

[0174] Configuration methods 1-3: Following the above principle of "for any SR" PERIODICITYThe configuration applies to the operation of selecting a single uplink slot / sub-slot from multiple uplink slots / sub-slots, and applies SR to this selected single uplink slot / sub-slot. PERIODICITY .

[0175] Configuration Method 2: Each scheduling request resource configuration is configured with its corresponding period and offset, based on the SCS or parameter set corresponding to its PUCCH cell and UL BWP. That is, when the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations, the first scheduling request resource configuration among the at least two scheduling request resource configurations is configured based on target information. Here, the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink UL BWP.

[0176] For CSI resource configuration: The CSI-ReportConfig corresponding to periodic CSI or semi-persistent CSI reporting is configured on the PUCCH cell that transmits the PUCCH carrying periodic CSI or semi-persistent CSI. Each PUCCH cell can be configured independently with the corresponding CSI-ReportConfig for periodic CSI or semi-persistent CSI reporting.

[0177] For periodic CSI on PUCCH, a cell is considered active if its (or its corresponding) active BWP is the uplink BWP configured for this periodic CSI report; otherwise, it is suspended. Optionally, when using PUCCH carrier switching Alt.2C, for periodic CSI on PUCCH, a cell is considered active if its (or its corresponding) PUCCH cell is active or available based on the time-domain mode, and the active BWP of this PUCCH cell is the uplink BWP configured for this periodic CSI report; otherwise, it is suspended.

[0178] For semi-persistent CSI on PUCCH, after activation based on MAC CE, if it is not deactivated by MAC CE, it is considered active if the Active BWP of its (or corresponding) PUCCH cell is the uplink BWP configured for semi-persistent CSI reporting; otherwise, it is suspended. Optionally, when using PUCCH carrier switching Alt.2C, for semi-persistent CSI on PUCCH, after activation based on MAC CE, if it is not deactivated by MAC CE, it is considered active if its (or corresponding) PUCCH cell is active / available based on time-domain mode, and the Active BWP of this PUCCH cell is the uplink BWP configured for semi-persistent CSI reporting; otherwise, it is suspended.

[0179] When using PUCCH carrier switching Alt.2C, it can generally be assumed that at a certain moment only a single PUCCH cell is actually effective or active based on the time-domain mode. Then, UCI multiplexing or prioritization operations can be performed on this PUCCH cell according to certain protocol rules.

[0180] For PUCCH carrier switching, when using the dynamic indication method Alt.1, the HARQ-ACK feedback delay can be shortened for multiplexing and transmission between different UCI information types, and the transmission performance of other UCI information types can be further guaranteed. Other UCI information types can synchronously switch PUCCH cells based on DG HARQ-ACK PUCCH cell switching and corresponding multiplexing rules to ensure their transmission.

[0181] Please see Figure 4 , Figure 4 This is a flowchart of an uplink control information transmission method provided in an embodiment of this application, such as... Figure 4 As shown, the uplink control information transmission method provided in this application includes:

[0182] Step 401: The network-side equipment receives the first target UCI transmitted by the terminal through the target physical uplink control channel (PUCCH) cell;

[0183] The target PUCCH cell is a cell among at least one PUCCH cells, and the at least one PUCCH cell is determined based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs.

[0184] In this embodiment, the network-side device receives a first target UCI transmitted by the terminal through a target Physical Uplink Control Channel (PUCCH) cell; wherein, the target PUCCH cell is a cell among at least one PUCCH cell, the at least one PUCCH cell is determined based on at least two uplink control information (UCIs), and the first target UCI is determined based on the at least two UCIs. Transmitting the first target UCI through the target PUCCH cell can improve the transmission performance of the at least two UCIs.

[0185] Optionally, the UCI includes at least one of the following:

[0186] HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment)

[0187] Scheduling Request (SR);

[0188] Channel State Information (CSI).

[0189] Optionally, the at least one PUCCH cell includes at least one of the following:

[0190] In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI.

[0191] In the case where the at least two UCIs include a second dynamic scheduling HARQ-ACK and at least one third dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes the PUCCH cell corresponding to the second dynamic scheduling HARQ-ACK, the second dynamic scheduling HARQ-ACK is indicated by a second type DCI, the third dynamic scheduling HARQ-ACK is indicated by a first type DCI, and the second dynamic scheduling HARQ-ACK and the at least one third dynamic scheduling HARQ-ACK are transmitted in the same HARQ-ACK codebook.

[0192] In the case where the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, the at least one PUCCH cell includes a PUCCH cell as specified in the protocol or configured based on higher-layer signaling.

[0193] In the case where at least two UCIs include SPS HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell dynamically indicated by SPS activation or reactivation DCI.

[0194] In the case where the at least two UCIs include an SR corresponding to an SR configuration, the at least one PUCCH cell includes the PUCCH cell corresponding to the first PUCCH transmission, wherein the first PUCCH transmission is a PUCCH transmission corresponding to a scheduling request resource configuration associated with an SR configuration.

[0195] In the case where the at least two UCIs include periodic CSIs, the at least one PUCCH cell includes a PUCCH cell configured with a first CSI reporting configuration, wherein the first CSI reporting configuration is the CSI reporting configuration corresponding to the periodic CSI carried by the PUCCH.

[0196] In the case where at least two UCIs include semi-persistent CSI, the at least one PUCCH cell includes a PUCCH cell configured with a second CSI reporting configuration, wherein the second CSI reporting configuration is the CSI reporting configuration corresponding to the semi-persistent CSI carried by the PUCCH.

[0197] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0198] The target PUCCH cell is one of the at least two PUCCH cells, and the first target UCI is determined based on the at least two UCIs.

[0199] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0200] The target PUCCH cell includes the at least two PUCCH cells, and the first target UCI includes the at least two UCIs.

[0201] Optionally, the first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule.

[0202] The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

[0203] Optionally, the first target UCI includes one of the following:

[0204] The fusion information obtained by fusing the UCIs from the at least two UCIs;

[0205] A portion of the UCIs selected from the at least two UCIs.

[0206] Optionally, the fusion information is determined according to any of the following methods:

[0207] For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information.

[0208] Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

[0209] Optionally, the first UCI corresponding to the PUCCH cell is determined as follows:

[0210] When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell.

[0211] If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

[0212] Optionally, if the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; if the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the UCI corresponding to the first PUCCH cell according to the fourth preset rule.

[0213] Optionally, the portion of the UCI includes any one of the following:

[0214] The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells;

[0215] The UCI of the corresponding target type in at least two UCIs;

[0216] The UCI among the at least two UCIs has the target transmission requirement.

[0217] Optionally, the second PUCCH cell includes any one of the following:

[0218] The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells;

[0219] The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells;

[0220] The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells.

[0221] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0222] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0223] The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

[0224] Optionally, the target PUCCH cell includes any one of the following:

[0225] PUCCH cell selected from the at least two PUCCH cells based on the index value;

[0226] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0227] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0228] The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells;

[0229] The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell;

[0230] The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

[0231] Optionally, the method further includes sending UCI resource configuration information.

[0232] Optionally, the resource configuration information includes at least one of the following:

[0233] The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell;

[0234] The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1;

[0235] The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

[0236] Optionally, if the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations:

[0237] The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set;

[0238] or,

[0239] The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink ULBWP.

[0240] Optionally, the fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations;

[0241] In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

[0242] Optionally, the target time unit includes one of the following:

[0243] The time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0244] The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0245] The first time unit among the plurality of time units;

[0246] The last time unit among the plurality of time units;

[0247] The time unit corresponding to the first specified index among the plurality of time units.

[0248] The above information can be found at [link to relevant document]. Figure 2 The descriptions in the terminal-side embodiments are not repeated here.

[0249] Please see Figure 5 , Figure 5 This is a structural diagram of an uplink control information transmission device provided in an embodiment of this application. The first uplink control information transmission device 500 includes:

[0250] The determination module 501 is used to determine at least one physical uplink control channel (PUCCH) cell corresponding to at least two uplink control information (UCIs) based on at least two uplink control information (UCIs).

[0251] The transmission module 502 is configured to transmit a first target UCI through a target PUCCH cell in the at least one PUCCH cell, wherein the first target UCI is determined based on the at least two UCIs.

[0252] Optionally, the UCI includes at least one of the following:

[0253] HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment)

[0254] Scheduling Request (SR);

[0255] Channel State Information (CSI).

[0256] Optionally, if the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI.

[0257] In the case where the at least two UCIs include a second dynamic scheduling HARQ-ACK and at least one third dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes the PUCCH cell corresponding to the second dynamic scheduling HARQ-ACK, the second dynamic scheduling HARQ-ACK is indicated by a second type DCI, the third dynamic scheduling HARQ-ACK is indicated by a first type DCI, and the second dynamic scheduling HARQ-ACK and the at least one third dynamic scheduling HARQ-ACK are transmitted in the same HARQ-ACK codebook.

[0258] In the case where the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, the at least one PUCCH cell includes a PUCCH cell as specified in the protocol or configured based on higher-layer signaling.

[0259] In the case where at least two UCIs include SPS HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell dynamically indicated by SPS activation or reactivation DCI.

[0260] In the case where the at least two UCIs include an SR corresponding to an SR configuration, the at least one PUCCH cell includes the PUCCH cell corresponding to the first PUCCH transmission, wherein the first PUCCH transmission is a PUCCH transmission corresponding to a scheduling request resource configuration associated with an SR configuration.

[0261] In the case where the at least two UCIs include periodic CSIs, the at least one PUCCH cell includes a PUCCH cell configured with a first CSI reporting configuration, wherein the first CSI reporting configuration is the CSI reporting configuration corresponding to the periodic CSI carried by the PUCCH.

[0262] In the case where at least two UCIs include semi-persistent CSI, the at least one PUCCH cell includes a PUCCH cell configured with a second CSI reporting configuration, wherein the second CSI reporting configuration is the CSI reporting configuration corresponding to the semi-persistent CSI carried by the PUCCH.

[0263] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0264] The transmission module 502 is used to transmit the at least two UCIs in parallel through the at least two PUCCH cells during the time-domain overlap period.

[0265] Optionally, the first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule.

[0266] The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

[0267] Optionally, the first target UCI includes one of the following:

[0268] The fusion information obtained by fusing the UCIs from the at least two UCIs;

[0269] A portion of the UCIs selected from the at least two UCIs.

[0270] Optionally, the fusion information is determined according to any of the following methods:

[0271] For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information.

[0272] Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

[0273] Optionally, the first UCI corresponding to the PUCCH cell is determined as follows:

[0274] When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell.

[0275] If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

[0276] Optionally, if the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; if the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the UCI corresponding to the first PUCCH cell according to the fourth preset rule.

[0277] Optionally, the portion of the UCI includes any one of the following:

[0278] The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells;

[0279] The UCI of the corresponding target type in at least two UCIs;

[0280] The UCI among the at least two UCIs has the target transmission requirement.

[0281] Optionally, the second PUCCH cell includes any one of the following:

[0282] The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells;

[0283] The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells;

[0284] The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells.

[0285] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0286] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0287] The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

[0288] Optionally, the target PUCCH cell includes any one of the following:

[0289] PUCCH cell selected from the at least two PUCCH cells based on the index value;

[0290] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0291] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0292] The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells;

[0293] The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell;

[0294] The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

[0295] Optionally, the device further includes a receiving module for receiving resource configuration information from the UCI.

[0296] Optionally, the resource configuration information includes at least one of the following:

[0297] The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell;

[0298] The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1;

[0299] The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

[0300] Optionally, if the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations:

[0301] The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set;

[0302] or,

[0303] The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink ULBWP.

[0304] Optionally, the fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations;

[0305] In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

[0306] Optionally, the target time unit includes one of the following:

[0307] The time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0308] The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0309] The first time unit among the plurality of time units;

[0310] The last time unit among the plurality of time units;

[0311] The time unit corresponding to the first specified index among the plurality of time units.

[0312] The first uplink control information transmission device 500 in the embodiments of this application may be a device, or it may be a component, integrated circuit, or chip in a terminal.

[0313] The first uplink control information transmission device 500 in this embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this embodiment does not specifically limit its use.

[0314] The first uplink control information transmission device 500 provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0315] Please see Figure 6 , Figure 6 This is a structural diagram of an uplink control information transmission device provided in an embodiment of this application. The second uplink control information transmission device 600 includes:

[0316] Receiver module 601 is used by network-side equipment to receive the first target UCI transmitted by the terminal through the target physical uplink control channel (PUCCH) cell;

[0317] The target PUCCH cell is a cell among at least one PUCCH cells, and the at least one PUCCH cell is determined based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs.

[0318] Optionally, the UCI includes at least one of the following:

[0319] HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment)

[0320] Scheduling Request (SR);

[0321] Channel State Information (CSI).

[0322] Optionally, if the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI.

[0323] In the case where the at least two UCIs include a second dynamic scheduling HARQ-ACK and at least one third dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes the PUCCH cell corresponding to the second dynamic scheduling HARQ-ACK, the second dynamic scheduling HARQ-ACK is indicated by a second type DCI, the third dynamic scheduling HARQ-ACK is indicated by a first type DCI, and the second dynamic scheduling HARQ-ACK and the at least one third dynamic scheduling HARQ-ACK are transmitted in the same HARQ-ACK codebook.

[0324] In the case where the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, the at least one PUCCH cell includes a PUCCH cell as specified in the protocol or configured based on higher-layer signaling.

[0325] In the case where at least two UCIs include SPS HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell dynamically indicated by SPS activation or reactivation DCI.

[0326] In the case where the at least two UCIs include an SR corresponding to an SR configuration, the at least one PUCCH cell includes the PUCCH cell corresponding to the first PUCCH transmission, wherein the first PUCCH transmission is a PUCCH transmission corresponding to a scheduling request resource configuration associated with an SR configuration.

[0327] In the case where the at least two UCIs include periodic CSIs, the at least one PUCCH cell includes a PUCCH cell configured with a first CSI reporting configuration, wherein the first CSI reporting configuration is the CSI reporting configuration corresponding to the periodic CSI carried by the PUCCH.

[0328] In the case where at least two UCIs include semi-persistent CSI, the at least one PUCCH cell includes a PUCCH cell configured with a second CSI reporting configuration, wherein the second CSI reporting configuration is the CSI reporting configuration corresponding to the semi-persistent CSI carried by the PUCCH.

[0329] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0330] The target PUCCH cell is one of the at least two PUCCH cells, and the first target UCI is determined based on the at least two UCIs.

[0331] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0332] The target PUCCH cell includes the at least two PUCCH cells, and the first target UCI includes the at least two UCIs.

[0333] Optionally, the first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule.

[0334] The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

[0335] Optionally, the first target UCI includes one of the following:

[0336] The fusion information obtained by fusing the UCIs from the at least two UCIs;

[0337] A portion of the UCIs selected from the at least two UCIs.

[0338] Optionally, the fusion information is determined according to any of the following methods:

[0339] For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information.

[0340] Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

[0341] Optionally, the first UCI corresponding to the PUCCH cell is determined as follows:

[0342] When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell.

[0343] If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

[0344] Optionally, if the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; if the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the UCI corresponding to the first PUCCH cell according to the fourth preset rule.

[0345] Optionally, the portion of the UCI includes any one of the following:

[0346] The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells;

[0347] The UCI of the corresponding target type in at least two UCIs;

[0348] The UCI among the at least two UCIs has the target transmission requirement.

[0349] Optionally, the second PUCCH cell includes any one of the following:

[0350] The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells;

[0351] The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells;

[0352] The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells.

[0353] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0354] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0355] The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

[0356] Optionally, the target PUCCH cell includes any one of the following:

[0357] PUCCH cell selected from the at least two PUCCH cells based on the index value;

[0358] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0359] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0360] The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells;

[0361] The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell;

[0362] The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

[0363] Optionally, the device further includes a sending module for sending UCI resource configuration information.

[0364] Optionally, the resource configuration information includes at least one of the following:

[0365] The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell;

[0366] The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1;

[0367] The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

[0368] Optionally, if the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations:

[0369] The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set;

[0370] or,

[0371] The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink ULBWP.

[0372] Optionally, the fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations;

[0373] In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

[0374] Optionally, the target time unit includes one of the following:

[0375] The time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0376] The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0377] The first time unit among the plurality of time units;

[0378] The last time unit among the plurality of time units;

[0379] The time unit corresponding to the first specified index among the plurality of time units.

[0380] The second uplink control information transmission device 600 provided in this application embodiment can achieve... Figure 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0381] Optional, such as Figure 7 As shown, this application embodiment also provides a communication device 70, including a processor 71, a memory 72, and a program or instructions stored in the memory 72 and executable on the processor 71. For example, when the communication device 70 is a terminal, the program or instructions executed by the processor 71 implement the above-mentioned... Figure 2 The various processes of the uplink control information transmission method embodiment shown can achieve the same technical effect. When the communication device 70 is a network-side device, the program or instruction executed by the processor 71 implements the above. Figure 4 The various processes of the uplink control information transmission method embodiment shown can achieve the same technical effect.

[0382] Figure 8 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0383] The terminal 1000 includes, but is not limited to, the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0384] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0385] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0386] In this embodiment, the radio frequency unit 1001 receives downlink data from the network-side device and processes it for the processor 1010; additionally, it sends uplink data to the base station. Typically, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0387] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0388] Processor 1010 may include one or more processing units; optionally, processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1010.

[0389] The processor 1010 is configured to determine at least one physical uplink control channel (PUCCH) cell corresponding to at least two uplink control information (UCIs) based on at least two uplink control information (UCIs).

[0390] Radio frequency unit 1001 is used to transmit a first target UCI through a target PUCCH cell in the at least one PUCCH cell, the first target UCI being determined based on the at least two UCIs.

[0391] Optionally, the UCI includes at least one of the following:

[0392] HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment)

[0393] Scheduling Request (SR);

[0394] Channel State Information (CSI).

[0395] Optionally, if the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI.

[0396] In the case where the at least two UCIs include a second dynamic scheduling HARQ-ACK and at least one third dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes the PUCCH cell corresponding to the second dynamic scheduling HARQ-ACK, the second dynamic scheduling HARQ-ACK is indicated by a second type DCI, the third dynamic scheduling HARQ-ACK is indicated by a first type DCI, and the second dynamic scheduling HARQ-ACK and the at least one third dynamic scheduling HARQ-ACK are transmitted in the same HARQ-ACK codebook.

[0397] In the case where the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, the at least one PUCCH cell includes a PUCCH cell as specified in the protocol or configured based on higher-layer signaling.

[0398] In the case where at least two UCIs include SPS HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell dynamically indicated by SPS activation or reactivation DCI.

[0399] In the case where the at least two UCIs include an SR corresponding to an SR configuration, the at least one PUCCH cell includes the PUCCH cell corresponding to the first PUCCH transmission, wherein the first PUCCH transmission is a PUCCH transmission corresponding to a scheduling request resource configuration associated with an SR configuration.

[0400] In the case where the at least two UCIs include periodic CSIs, the at least one PUCCH cell includes a PUCCH cell configured with a first CSI reporting configuration, wherein the first CSI reporting configuration is the CSI reporting configuration corresponding to the periodic CSI carried by the PUCCH.

[0401] In the case where at least two UCIs include semi-persistent CSI, the at least one PUCCH cell includes a PUCCH cell configured with a second CSI reporting configuration, wherein the second CSI reporting configuration is the CSI reporting configuration corresponding to the semi-persistent CSI carried by the PUCCH.

[0402] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0403] The target PUCCH cell is one of the at least two PUCCH cells, and the first target UCI is determined based on the at least two UCIs.

[0404] Optionally, the PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells;

[0405] The radio frequency unit 1001 is also configured to, during the time-domain overlap period, transmit the at least two UCIs in parallel through the at least two PUCCH cells.

[0406] Optionally, the first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule.

[0407] The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

[0408] Optionally, the first target UCI includes one of the following:

[0409] The fusion information obtained by fusing the UCIs from the at least two UCIs;

[0410] A portion of the UCIs selected from the at least two UCIs.

[0411] Optionally, the fusion information is determined according to any of the following methods:

[0412] For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information.

[0413] Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

[0414] Optionally, the first UCI corresponding to the PUCCH cell is determined as follows:

[0415] When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell.

[0416] If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

[0417] Optionally, if the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; if the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the UCI corresponding to the first PUCCH cell according to the fourth preset rule.

[0418] Optionally, the portion of the UCI includes any one of the following:

[0419] The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells;

[0420] The UCI of the corresponding target type in at least two UCIs;

[0421] The UCI among the at least two UCIs has the target transmission requirement.

[0422] Optionally, the second PUCCH cell includes any one of the following:

[0423] The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells;

[0424] The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells;

[0425] The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells.

[0426] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0427] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0428] The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

[0429] Optionally, the target PUCCH cell includes any one of the following:

[0430] PUCCH cell selected from the at least two PUCCH cells based on the index value;

[0431] PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs;

[0432] The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells;

[0433] The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells;

[0434] The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell;

[0435] The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

[0436] Optionally, the radio frequency unit 1001 is also used to receive UCI resource configuration information.

[0437] Optionally, the resource configuration information includes at least one of the following:

[0438] The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell;

[0439] The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1;

[0440] The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

[0441] Optionally, if the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations:

[0442] The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set;

[0443] or,

[0444] The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink ULBWP.

[0445] Optionally, the fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations;

[0446] In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

[0447] Optionally, the target time unit includes one of the following:

[0448] The time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0449] The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource;

[0450] The first time unit among the plurality of time units;

[0451] The last time unit among the plurality of time units;

[0452] The time unit corresponding to the first specified index among the plurality of time units.

[0453] The terminal 1000 provided in the above embodiments can achieve Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0454] Specifically, embodiments of this application also provide a network-side device. For example... Figure 9 As shown, the network device 900 includes an antenna 91, a radio frequency (RF) device 92, and a baseband device 93. The antenna 91 is connected to the RF device 92. In the uplink direction, the RF device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be transmitted and sends it to the RF device 92. The RF device 92 processes the received information and then transmits it through the antenna 91.

[0455] The aforementioned frequency band processing device can be located in the baseband device 93. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 93, which includes a processor 94 and a memory 95.

[0456] Baseband device 93 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 9 As shown, one of the chips, for example, is a processor 94, which is connected to a memory 95 to call the program in the memory 95 and execute the network device operation shown in the above method embodiment.

[0457] The baseband device 93 may also include a network interface 96 for exchanging information with the radio frequency device 92, such as a common public radio interface (CPRI).

[0458] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 95 and executable on processor 94, wherein processor 94 calls the instructions or programs in memory 95 to execute. Figure 6 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0459] This application embodiment also provides a readable storage medium storing a program or instructions that are executed by a processor. Figure 2 or Figure 4 The various processes in the method embodiments described herein can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0460] The processor mentioned above is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0461] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network-side device programs or instructions to achieve the above-mentioned... Figure 2 or Figure 4 The various processes in the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0462] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0463] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0464] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network, etc.) to execute the methods described in the various embodiments of this application.

[0465] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for transmitting uplink control information, characterized in that, include: When the Physical Uplink Control Channel (PUCCH) cell group configured for the terminal includes multiple PUCCH cells, the terminal determines at least one PUCCH cell corresponding to the at least two UCIs among the multiple PUCCH cells based on at least two uplink control information (UCIs). The terminal transmits a first target UCI through a target PUCCH cell in the at least one PUCCH cell, and the first target UCI is determined based on the at least two UCIs; In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI. If the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or if the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, then the at least one PUCCH cell includes a PUCCH cell configured according to the protocol or based on higher-layer signaling.

2. The method according to claim 1, characterized in that, The UCI includes at least one of the following: HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment) Scheduling Request (SR); Channel State Information (CSI).

3. The method according to claim 1, characterized in that, The PUCCH cells of the first type of DCI pointing to the same time slot or sub-time slot are consistent.

4. The method according to claim 1, characterized in that, The PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

5. The method according to claim 4, characterized in that, The target PUCCH cell is one of the at least two PUCCH cells.

6. The method according to claim 4, characterized in that, The terminal transmits the first target UCI through the target PUCCH cell in the at least one PUCCH cell, including: During the time-domain overlap period, the terminal transmits the at least two UCIs in parallel through the at least two PUCCH cells.

7. The method according to claim 5, characterized in that, The first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule. The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

8. The method according to claim 5, characterized in that, The first target UCI includes the following: The fusion information obtained by fusing the UCIs from the at least two UCIs; Selected UCIs from the at least two UCIs.

9. The method according to claim 8, characterized in that, The fused information is determined according to any of the following methods: For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information. Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

10. The method according to claim 9, characterized in that, The first UCI corresponding to the PUCCH cell is determined as follows: When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell. If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

11. The method according to claim 9, characterized in that, When the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; when the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the fourth preset rule based on the UCI corresponding to the first PUCCH cell.

12. The method according to claim 8, characterized in that, The UCI portion includes any one of the following: The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells; The UCI of the corresponding target type in at least two UCIs; The UCI among the at least two UCIs has the target transmission requirement.

13. The method according to claim 12, characterized in that, The second PUCCH cell includes any one of the following: The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells; The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells; The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells. PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs; The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells; The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

14. The method according to claim 5, characterized in that, The target PUCCH cell includes any one of the following: PUCCH cell selected from the at least two PUCCH cells based on the index value; PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs; The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells; The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells; The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell; The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

15. The method according to claim 1, characterized in that, Before the terminal determines at least one PUCCH cell corresponding to the at least two UCIs based on the at least two UCIs, the method further includes: Receive resource configuration information from UCI.

16. The method according to claim 15, characterized in that, The resource configuration information includes at least one of the following: The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell; The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1; The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

17. The method according to claim 15, characterized in that, When the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations: The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set; or, The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink UL BWP.

18. The method according to claim 17, characterized in that, The fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations; In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

19. The method according to claim 18, characterized in that, The target time unit includes the following: The time unit among the plurality of time units that can accommodate the SR PUCCH resource; The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource; The first time unit among the plurality of time units; The last time unit among the plurality of time units; The time unit corresponding to the first specified index among the plurality of time units.

20. The method according to claim 1, characterized in that, In the case of PUCCH carrier handover using a semi-static method, at any given time, only a single PUCCH cell is valid or active based on the time-domain mode.

21. A method for transmitting uplink control information, characterized in that, include: The network-side equipment receives the first target UCI transmitted by the target physical uplink control channel (PUCCH) cell; The terminal is configured with a PUCCH cell group that includes multiple PUCCH cells. The target PUCCH cell is a cell in at least one PUCCH cell. The at least one PUCCH cell is determined from the multiple PUCCH cells based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs. In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI. If the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or if the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, then the at least one PUCCH cell includes a PUCCH cell configured according to the protocol or based on higher-layer signaling.

22. The method according to claim 21, characterized in that, The UCI includes at least one of the following: HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment) Scheduling Request (SR); Channel State Information (CSI).

23. The method according to claim 21, characterized in that, The PUCCH cells of the first type of DCI pointing to the same time slot or sub-time slot are consistent.

24. The method according to claim 21, characterized in that, The PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

25. The method according to claim 24, characterized in that, The target PUCCH cell is one of the at least two PUCCH cells.

26. The method according to claim 24, characterized in that, The target PUCCH cell includes the at least two PUCCH cells.

27. The method according to claim 25, characterized in that, The first target UCI is determined based on the attributes and time domain overlap of the PUCCH resources corresponding to each of the at least two UCIs, according to a first preset rule. The target PUCCH cell is the PUCCH cell corresponding to the PUCCH resources carrying the first target UCI.

28. The method according to claim 25, characterized in that, The first target UCI includes the following: The fusion information obtained by fusing the UCIs from the at least two UCIs; Selected UCIs from the at least two UCIs.

29. The method according to claim 28, characterized in that, The fused information is determined according to any of the following methods: For each PUCCH cell in the at least two PUCCH cells, determine the first UCI corresponding to each PUCCH cell, and concatenate the first UCI corresponding to each PUCCH cell based on the second preset rule to obtain the fusion information. Based on the at least two UCIs, M UCI categories to be transmitted are determined. For the first UCI category among the M UCI categories, the second UCIs corresponding to each first PUCCH cell are concatenated end-to-end according to a second preset rule to obtain the third UCI corresponding to the first UCI category. The third UCIs corresponding to each UCI category are then concatenated end-to-end according to a third preset rule to obtain the fusion information. Here, the UCI category includes UCI information type or UCI transmission requirement, M is an integer greater than or equal to 1, the first UCI category is any UCI category among the M UCI categories, the first PUCCH cell is any PUCCH cell among the at least two PUCCH cells that has a second target UCI, the second target UCI includes at least one UCI corresponding to the first UCI category, and the second UCI corresponding to the first PUCCH cell is determined according to the first target UCI corresponding to the first PUCCH cell.

30. The method according to claim 29, characterized in that, The first UCI corresponding to the PUCCH cell is determined as follows: When the number of UCIs corresponding to a PUCCH cell is equal to 1, the first UCI corresponding to the PUCCH cell is determined as the UCI corresponding to the PUCCH cell. If the number of UCIs corresponding to a PUCCH cell is greater than 1, the first UCI corresponding to the PUCCH cell is determined according to the first preset rule based on the UCI corresponding to the PUCCH cell.

31. The method according to claim 29, characterized in that, When the number of UCIs corresponding to the first PUCCH cell is equal to 1, the second UCI corresponding to the first PUCCH cell is the UCI corresponding to the first PUCCH cell; when the number of UCIs corresponding to the first PUCCH cell is greater than 1, the second UCI corresponding to the first PUCCH cell is obtained according to the fourth preset rule based on the UCI corresponding to the first PUCCH cell.

32. The method according to claim 28, characterized in that, The UCI portion includes any one of the following: The UCI that corresponds to the second PUCCH cell in the at least two PUCCH cells; The UCI of the corresponding target type in at least two UCIs; The UCI among the at least two UCIs has the target transmission requirement.

33. The method according to claim 32, characterized in that, The second PUCCH cell includes any one of the following: The PUCCH cell with the largest corresponding index value among the at least two PUCCH cells; The PUCCH cell with the smallest corresponding index value among the at least two PUCCH cells; The at least two PUCCH cells whose corresponding index values ​​are preset index values ​​are PUCCH cells. PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs; The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells; The PUCCH cell is selected based on the resource availability information of each of the at least two PUCCH cells.

34. The method according to claim 25, characterized in that, The target PUCCH cell includes any one of the following: PUCCH cell selected from the at least two PUCCH cells based on the index value; PUCCH cell selected from the at least two PUCCH cells according to the physical layer priority corresponding to each of the at least two UCIs; The PUCCH cell is selected based on the cell priority configured in each of the at least two PUCCH cells; The PUCCH cell selected based on the resource availability information of each of the at least two PUCCH cells; The second PUCCH cell in the at least two PUCCH cells, the first target UCI includes some or all of the UCIs corresponding to the second PUCCH cell; The third PUCCH cell among the at least two PUCCH cells, wherein the third PUCCH cell is the PUCCH cell that needs to transmit the codebook corresponding to the dynamically scheduled HARQ-ACK.

35. The method according to claim 21, characterized in that, The method further includes: Send UCI resource configuration information.

36. The method according to claim 35, characterized in that, The resource configuration information includes at least one of the following: The association information between an SR configuration and a scheduling request resource configuration configured on at least one bandwidth portion BWP of a PUCCH cell; The association information between an SR configuration and a scheduling request resource configuration configured on at least one BWP of N PUCCH cells, where N is an integer greater than 1; The CSI reporting configuration is configured on the PUCCH cell that transmits CSI.

37. The method according to claim 35, characterized in that, When the same SR configuration included in the resource configuration information is associated with at least two scheduling request resource configurations: The period and offset of each scheduling request resource configuration in the at least two scheduling request resource configurations are uniformly configured based on the reference subcarrier interval or reference parameter set; or, The first scheduling request resource configuration in the at least two scheduling request resource configurations is configured based on target information, wherein the first scheduling request resource configuration is any one of the at least two scheduling request resource configurations, and the target information is the PUCCH cell where the first scheduling request resource configuration is located and the subcarrier spacing or parameter set corresponding to the uplink UL BWP.

38. The method according to claim 37, characterized in that, The fourth PUCCH cell is the PUCCH cell corresponding to the second scheduling request resource configuration, and the second scheduling request resource configuration is any one of the at least two scheduling request resource configurations; In the case where a single time unit determined based on the reference subcarrier interval or reference parameter set corresponds to multiple time units on the fourth PUCCH cell, a target time unit is selected from the multiple time units based on a fifth preset rule to determine the SR PUCCH resource corresponding to the second scheduling request resource configuration.

39. The method according to claim 38, characterized in that, The target time unit includes the following: The time unit among the plurality of time units that can accommodate the SR PUCCH resource; The earliest time unit among the plurality of time units that can accommodate the SR PUCCH resource; The first time unit among the plurality of time units; The last time unit among the plurality of time units; The time unit corresponding to the first specified index among the plurality of time units.

40. The method according to claim 21, characterized in that, In the case of PUCCH carrier handover using a semi-static method, at any given time, only a single PUCCH cell is valid or active based on the time-domain mode.

41. An uplink control information transmission device, characterized in that, include: The determination module is used to determine at least one PUCCH cell corresponding to at least two uplink control information (UCIs) in the plurality of PUCCH cells when the PUCCH cell group configured for the terminal includes multiple PUCCH cells. The transmission module is configured to transmit a first target UCI through a target PUCCH cell in the at least one PUCCH cell, wherein the first target UCI is determined based on the at least two UCIs; In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI. If the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or if the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, then the at least one PUCCH cell includes a PUCCH cell configured according to the protocol or based on higher-layer signaling.

42. The apparatus according to claim 41, characterized in that, The PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

43. An uplink control information transmission device, characterized in that, include: The receiving module is used to receive the first target UCI transmitted by the terminal through the target physical uplink control channel (PUCCH) cell; The terminal is configured with a PUCCH cell group that includes multiple PUCCH cells. The target PUCCH cell is a cell in at least one PUCCH cell. The at least one PUCCH cell is determined from the multiple PUCCH cells based on at least two uplink control information (UCIs). The first target UCI is determined based on the at least two UCIs. In the case where the at least two UCIs include a first dynamic scheduling HARQ-ACK, the at least one PUCCH cell includes a PUCCH cell corresponding to the first dynamic scheduling HARQ-ACK, wherein the first dynamic scheduling HARQ-ACK is indicated by a first type of DCI. If the at least two UCIs include semi-static scheduling (SPS) HARQ-ACK, or if the at least two UCIs include dynamic scheduling HARQ-ACK indicated by a second type DCI, and the dynamic scheduling HARQ-ACK indicated by the second type DCI is not transmitted in the same HARQ-ACK codebook as any dynamic scheduling HARQ-ACK indicated by a first type DCI, then the at least one PUCCH cell includes a PUCCH cell configured according to the protocol or based on higher-layer signaling.

44. The apparatus according to claim 43, characterized in that, The PUCCH resources carrying the at least two UCIs have temporal overlap, and the PUCCH resources carrying the at least two UCIs are located in at least two PUCCH cells.

45. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the uplink control information transmission method as described in any one of claims 1 to 20.

46. ​​A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the uplink control information transmission method as described in any one of claims 21 to 40.

47. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the uplink control information transmission method as described in any one of claims 1 to 20, or, when executed by a processor, implement the steps of the uplink control information transmission method as described in any one of claims 1 to 40.

Images