UCI transmission method and device and storage medium

Abstract

The invention provides a UCI (Uplink Control Information) transmission method and device and a storage medium, and the method comprises the steps: if a PUSCH and a PUCCH (Physical Uplink Control Channel) which carries UCI are overlapped in a time domain, excluding a CG PUSCH which carries configuration scheduling uplink control information and does not support UCI multiplexing transmission in the PUSCH; and determining a target channel used for bearing the UCI in the remaining channels, and sending the UCI on the target channel. According to the UCI transmission method and device and the storage medium provided by the invention, if the PUSCH and the PUCCH bearing the UCI are overlapped in the time domain, the CG PUSCH bearing the configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH, the target channel used for bearing the UCI is determined from the remaining channels, and the UCI is transmitted according to the target channel. The terminal implementation complexity is reduced, the reliability of configuring and scheduling the uplink control information is ensured, and the transmission rate is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an uplink control information (UCI) transmission method, device and storage medium. Background Art

[0002] The related technology introduces configuration scheduling information transmitted on the physical uplink shared channel (PUSCH). When the physical uplink shared channel (PUSCH) is configured to be multiplexed, the configuration scheduling information and hybrid automatic repeat request confirmation (HARQ ACK) information of the same priority can be multiplexed on the PUSCH; otherwise, the configuration scheduling information and HARQ-ACK information of the same priority cannot be transmitted at the same time. When the HARQ-ACK information needs to be multiplexed on the PUSCH carrying the configuration scheduling information and the PUSCH does not support multiplexing, the PUSCH needs to be discarded and the HARQ-ACK information is only transmitted on the PUCCH.

[0003] The above-mentioned related technical solutions result in that the configuration scheduling information cannot be transmitted in time, thus affecting the transmission rate. Summary of the invention

[0004] The embodiments of the present application provide a UCI transmission method, device, and storage medium to solve the technical problem of low transmission rate in the related art.

[0005] In a first aspect, an embodiment of the present application provides an uplink control information UCI transmission method, which is applied to a terminal, including:

[0006] If the physical uplink shared channel PUSCH and the physical uplink control channel PUCCH carrying UCI overlap in the time domain, the configuration scheduling CG PUSCH that carries the configuration scheduling uplink control information and does not support UCI multiplexing transmission is excluded from the PUSCH;

[0007] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is sent on the target channel.

[0008] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0009] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0010] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0011] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0012] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0013] The transmission of the CG PUSCH is not performed.

[0014] In some embodiments, the UCI is hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0015] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by the radio resource control RRC parameters.

[0016] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0017] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0018] In a second aspect, an embodiment of the present application provides a UCI transmission method, which is applied to a network device, including:

[0019] If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH;

[0020] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is received on the target channel.

[0021] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0022] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0023] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0024] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0025] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0026] Reception of the CG PUSCH is not performed.

[0027] In some embodiments, the UCI is HARQ-ACK information.

[0028] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0029] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0030] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0031] In a third aspect, an embodiment of the present application provides a terminal, including a memory, a transceiver, and a processor;

[0032] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0033] If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH;

[0034] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is sent on the target channel.

[0035] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0036] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0037] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0038] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0039] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0040] The transmission of the CG PUSCH is not performed.

[0041] In some embodiments, the UCI is HARQ-ACK information.

[0042] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0043] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0044] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0045] In a fourth aspect, an embodiment of the present application provides a network device, including a memory, a transceiver, and a processor;

[0046] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0047] If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH;

[0048] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is received on the target channel.

[0049] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0050] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0051] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0052] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0053] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0054] Reception of the CG PUSCH is not performed.

[0055] In some embodiments, the UCI is HARQ-ACK information.

[0056] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0057] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0058] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0059] In a fifth aspect, an embodiment of the present application provides a UCI transmission device, including:

[0060] A first exclusion module is configured to exclude, if the PUSCH and the PUCCH carrying the UCI overlap in the time domain, the CG PUSCH carrying the configuration scheduling uplink control information and not supporting the UCI multiplexing transmission in the PUSCH;

[0061] The sending module is used to determine a target channel for carrying the UCI from the remaining channels, and send the UCI on the target channel.

[0062] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0063] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0064] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0065] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0066] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0067] The transmission of the CG PUSCH is not performed.

[0068] In some embodiments, the UCI is hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0069] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by the radio resource control RRC parameters.

[0070] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0071] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0072] In a sixth aspect, an embodiment of the present application provides a UCI transmission device, including:

[0073] A second exclusion module is configured to exclude, if the PUSCH and the PUCCH carrying the UCI overlap in the time domain, the CG PUSCH carrying the configuration scheduling uplink control information and not supporting the UCI multiplexing transmission in the PUSCH;

[0074] The receiving module is used to determine a target channel for carrying the UCI from the remaining channels, and receive the UCI on the target channel.

[0075] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0076] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0077] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0078] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0079] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0080] Reception of the CG PUSCH is not performed.

[0081] In some embodiments, the UCI is HARQ-ACK information.

[0082] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0083] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0084] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0085] In a seventh aspect, an embodiment of the present application further provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method described in the first aspect or the second aspect as described above.

[0086] In an eighth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method described in the first aspect or the second aspect as described above.

[0087] In a ninth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the UCI transmission method described in the first aspect or the second aspect as described above.

[0088] In a tenth aspect, an embodiment of the present application further provides a communication device, wherein a computer program is stored in the communication device, and the computer program is used to enable the communication device to execute the UCI transmission method described in the first aspect or the second aspect as described above.

[0089] In an eleventh aspect, an embodiment of the present application further provides a chip product, wherein a computer program is stored in the chip product, and the computer program is used to enable the chip product to execute the UCI transmission method described in the first aspect or the second aspect as described above.

[0090] The UCI transmission method, device and storage medium provided in the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CGPUSCH carrying the configuration scheduling uplink control information and not supporting the UCI multiplexing transmission is excluded from the PUSCH, and the target channel for carrying the UCI is determined from the remaining channels, thereby reducing the complexity of terminal implementation and ensuring the reliability of the configuration scheduling uplink control information, thereby improving the transmission rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0092] Figure 1 It is one of the flowcharts of the UCI transmission method provided in the embodiment of the present application;

[0093] Figure 2 This is the second flow chart of the UCI transmission method provided in the embodiment of the present application;

[0094] Figure 3 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0095] Figure 4 It is a structural diagram of a network device provided in an embodiment of the present application;

[0096] Figure 5 This is one of the structural schematic diagrams of a UCI transmission device provided in an embodiment of the present application;

[0097] Figure 6 This is the second structural schematic diagram of a UCI transmission device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0098] The uplink channel multiplexing method in the 3rd Generation Partnership Project (3GPP) protocol is as follows:

[0099] In the New Radio (NR) communication system, in implementation mode A, for the same terminal, in order to avoid an excessively large peak-to-average power ratio (PAPR), the simultaneous transmission of PUCCH and PUSCH is not supported. Therefore, when the time domain resources of PUCCH and PUSCH overlap, the terminal can multiplex UCI on PUSCH for transmission, thereby eliminating the need to transmit PUCCH.

[0100] When there is overlap in time domain resources between the PUCCH and multiple PUSCHs, the terminal multiplexes the UCI carried by the PUCCH on one of the PUSCHs for transmission in a prescribed manner.

[0101] Among them, the above-mentioned time domain resource overlap or conflict refers to the conflict in the same carrier group. For example, the master cell group (MCG) and the secondary cell group (SCG) in the dual link are each a carrier group. When supporting PUCCH transmission on the secondary component carrier (SCC), a primary physical uplink control channel group (Primary PUCCH Group) and a secondary physical uplink control channel group (SecondaryPUCCH Group) will appear, and each physical uplink control channel group (PUCCH group) is a carrier group.

[0102] In implementation mode B, the uplink channel multiplexing method is as follows:

[0103] A two-level physical layer priority definition is introduced for uplink channels. When the time domain resources of uplink channels with different physical layer priorities overlap, the terminal discards the low-priority channel and only transmits the high-priority physical channel.

[0104] When time domain resources of uplink channels with the same physical layer priority overlap, the terminal performs multiplexing transmission of the channels with the same physical layer priority in accordance with implementation mode A.

[0105] When there are conflicts between channels with the same and different physical layer priorities, the terminal first processes the multiplexing between low-priority channels, then processes the time domain resource overlap between different priorities, then processes the multiplexing between high-priority channels, and finally processes the time domain resource overlap between the multiplexed high-priority channels and low-priority channels.

[0106] Implementation method B introduces the configuration scheduling uplink control information (Configure Grant Uplink Control Information, CG-UCI) transmitted on the CG PUSCH. When the indication information cg-UCI-Multiplexing is configured, the CG-UCI and HARQ-ACK of the same priority can be multiplexed on the CG PUSCH; otherwise, the CG-UCI and HARQ-ACK of the same priority cannot be transmitted at the same time. When HARQ-ACK needs to be multiplexed on the PUSCH carrying the CG-UCI and the indication information cg-UCI-Multiplexing does not support multiplexing, it is necessary to discard the CG PUSCH and transmit HARQ-ACK only on the PUCCH or multiplex the HARQ-ACK on another PUSCH.

[0107] The uplink channel multiplexing method of implementation mode C is as follows:

[0108] Further support the multiplexing of channels with different physical layer priorities. When the multiplexing indication information uci-MuxWithDiffPrio for opening channels with different physical layer priorities is configured, the terminal first processes the time domain resource overlap of channels with the same priority according to the process of implementation mode A, and then processes the time domain resource overlap of uplink channels with different physical layer priorities.

[0109] For the multiplexing of CG-UCI and HARQ-ACK on CG PUSCH, the high-level parameter (indication information) cg-UCI-Multiplexing corresponding to CG PUSCH can be used to indicate whether multiplexing is supported. When HARQ-ACK and multiple CG PUSCHs overlap, if at least one CG PUSCH contains CG-UCI, it is not clear how to perform multiplexing transmission. When HARQ-ACK needs to be multiplexed on the PUSCH carrying CG-UCI and the indication information cg-UCI-Multiplexing does not support multiplexing, it is unclear when to transmit HARQ-ACK on PUCCH, when to multiplex HARQ-ACK on another PUSCH, and when there are multiple PUSCHs, it is unclear on which PUSCH to multiplex HARQ-ACK.

[0110] Based on the above technical problems, the UCI transmission method provided by the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CGPUSCH that carries the configuration scheduling uplink control information and does not support UCI multiplexing transmission is excluded from the PUSCH, and the target channel for carrying UCI is determined from the remaining channels, which reduces the terminal implementation complexity and ensures the reliability of the configuration scheduling uplink control information, thereby improving the transmission rate.

[0111] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0112] Figure 1 is one of the flow charts of the UCI transmission method provided in the embodiment of the present application, such as Figure 1 As shown, an embodiment of the present application provides a UCI transmission method, the execution subject of which may be a terminal, such as a mobile phone. The method includes:

[0113] Step 101: If a physical uplink shared channel PUSCH and a physical uplink control channel PUCCH carrying UCI overlap in the time domain, a configuration scheduling CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission is excluded from the PUSCH.

[0114] Specifically, in the embodiment of the present application, the terminal first determines whether the PUSCH and the PUCCH carrying the UCI overlap / conflict in the time domain.

[0115] The above-mentioned time domain resource overlap / conflict may refer to a conflict in the same carrier group. For example, the MCG and SCG in the dual link are each a carrier group. When supporting PUCCH transmission on the SCC, a Primary PUCCH Group and a Secondary PUCCH Group will appear, and each PUCCH group is a carrier group.

[0116] If the PUSCH and the PUCCH carrying UCI overlap / collide in the time domain, the terminal can exclude the configured scheduled CG PUSCH that carries CG-UCI and does not support UCI multiplexing transmission in the PUSCH. The configured scheduled CG PUSCH that does not support UCI multiplexing transmission refers to the CG PUSCH that is not configured with the high-level parameter cg-UCI-Multiplexing.

[0117] For example, excluding PUSCHs that carry CG-UCI and do not support multiplexing with HARQ-ACK may mean that PUSCHs that carry CG-UCI and do not support multiplexing with HARQ-ACK are not used as candidate PUSCHs for UCI multiplexing, and are not directly discarded. PUSCHs are selected for multiplexing based on predefined rules among the remaining PUSCHs.

[0118] For another example, excluding PUSCHs that carry CG-UCI and do not support multiplexing with HARQ-ACK may mean discarding PUSCHs that carry CG-UCI and do not support multiplexing with HARQ-ACK, and processing the remaining PUCCHs and PUSCHs according to the existing protocol process.

[0119] UCI may be HARQ-ACK information, or HARQ-NACK information, etc.

[0120] Step 102: Determine a target channel for carrying the UCI from the remaining channels, and send the UCI on the target channel.

[0121] Specifically, in an embodiment of the present application, after excluding those PUSCHs that carry CG-UCI and do not support multiplexing with UCI, a target channel for carrying the UCI is determined in the remaining channels, and UCI is sent on the target channel.

[0122] For example, if there is no optional PUSCH after excluding those PUSCHs that carry CG-UCI and do not support multiplexing with UCI, the CG PUSCH is discarded and UCI is sent on the PUCCH.

[0123] For another example, if optional PUSCHs exist after excluding PUSCHs that carry CG-UCI and do not support multiplexing with UCI, a PUSCH is selected from the optional PUSCHs based on predefined rules for multiplexing to send UCI.

[0124] The UCI transmission method provided in the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, excludes the CG PUSCH carrying CG-UCI and not supporting UCI multiplexing transmission in the PUSCH, and determines the target channel for carrying UCI in the remaining channels, thereby reducing the complexity of terminal implementation and ensuring the reliability of configuration and scheduling uplink control information, and improving the transmission rate.

[0125] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0126] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0127] Specifically, in an embodiment of the present application, if there is no optional PUSCH (or there is no overlap between other PUSCHs and PUCCH) after excluding those PUSCHs that carry CG-UCI and do not support multiplexing with UCI, the CG PUSCH is discarded and UCI is sent on the PUCCH.

[0128] The UCI transmission method provided in the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, exclude the CG PUSCH carrying CG-UCI and not supporting UCI multiplexing transmission in the PUSCH, and if there is no PUSCH in the remaining channels, discard the CG PUSCH and send UCI on the PUCCH, thereby reducing the complexity of terminal implementation, ensuring the reliability of the configuration scheduling uplink control information, and improving the transmission rate.

[0129] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0130] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0131] Specifically, in an embodiment of the present application, if there is an optional PUSCH after excluding those PUSCHs that carry CG-UCI and do not support multiplexing with UCI, one of the PUSCHs can be selected based on predefined rules to multiplex and send UCI.

[0132] The predefined rule is a PUSCH selection rule for UCI multiplexing defined in the 3GPP protocol. For example, the selection may be made in the order of priority of the following rules:

[0133] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0134] Rule 2: Select the earliest PUSCH time slot;

[0135] Rule 3: Give priority to dynamically scheduled PUSCH;

[0136] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0137] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0138] Among them, for example, rule one has the highest priority, rule two has the second highest priority, rule three has the third highest priority, rule four has the fourth highest priority, and rule five has the lowest priority.

[0139] In addition, the predefined rules may not include the above rule 2.

[0140] The UCI transmission method provided by the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, exclude the CG PUSCH that carries CG-UCI and does not support UCI multiplexing transmission in the PUSCH, and select one of the PUSCHs in the remaining channels based on predefined rules to multiplex and send UCI, thereby reducing the terminal implementation complexity and ensuring the reliability of the configuration scheduling uplink control information, thereby improving the transmission rate.

[0141] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0142] The transmission of the CG PUSCH is not performed.

[0143] Specifically, in the embodiment of the present application, those PUSCHs that carry CG-UCI and do not support multiplexing with UCI are excluded, which means that the sending of the CG PUSCH is not performed.

[0144] The UCI transmission method provided by the present application, if the PUSCH and the PUCCH carrying UCI overlap in the time domain, excludes the CG PUSCH that carries CG-UCI and does not support UCI multiplexing transmission in the PUSCH, selects one of the PUSCHs in the remaining channels based on predefined rules to multiplex and send UCI, and does not send the CG PUSCH, thereby further improving the reliability of the system.

[0145] In some embodiments, the UCI is hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0146] Specifically, in an embodiment of the present application, UCI is HARQ-ACK information.

[0147] In some embodiments, if the UCI in the PUCCH does not include HARQ-ACK information, the CGPUSCH may be sent, i.e., there is no need to exclude the PUSCH that carries the CG-UCI and does not support multiplexing with HARQ-ACK. If the UCI in the PUCCH includes HARQ-ACK information, UCI multiplexing is performed after excluding the PUSCH that carries the CG-UCI and does not support multiplexing with HARQ-ACK in the PUSCH.

[0148] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by the radio resource control RRC parameters.

[0149] Specifically, in the embodiment of the present application, corresponding to the new UE capability and corresponding to the new RRC configuration parameters, when the terminal has the new UE capability and the function is configured to be turned on, the corresponding process of UCI transmission in the embodiment of the present application is performed. Otherwise, the traditional UCI multiplexing process is also performed.

[0150] In some embodiments, the UCI transmission method in the embodiments of the present application may be directed to multiplexing between PUCCH and PUSCH of the same priority.

[0151] In some embodiments, the UCI transmission method in the embodiments of the present application may also be applicable to conflicts between PUCCH and PUSCH of the same priority or different priorities.

[0152] The method in the above embodiment is further described below with reference to several specific examples.

[0153] Example 1: PUCCH and PUSCH have the same priority, and the UCI type carried by PUCCH is not distinguished.

[0154] When PUSCH and PUCCH of the same priority overlap, all PUSCHs overlapping with PUCCH are selected, excluding PUSCHs that carry CG-UCI and do not support CG-UCI and HARQ-ACK multiplexing (i.e. CG PUSCHs without cg-UCI-Multiplexing). UCI transmission mode is as follows:

[0155] Method 1: If there is no other overlap between PUSCH and PUCCH after excluding the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, then all PUSCHs that carry CG-UCI and do not support multiplexing of CG-UCI and HARQ-ACK are discarded, and only PUCCH is transmitted. Otherwise, the remaining PUSCHs are selected for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined in the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0156] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0157] Rule 2: Select the earliest PUSCH time slot;

[0158] Rule 3: Give priority to dynamically scheduled PUSCH;

[0159] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0160] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0161] In addition, the predefined rules may not include the above rule 2.

[0162] Method 2: Exclude the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, that is, discard the PUSCH that carries CG-UCI and does not support multiplexing with HARQ-ACK, and process the remaining PUCCH and PUSCH according to the existing protocol process; that is, if there is no overlap between PUSCH and PUCCH, only PUCCH is transmitted; if there is at least one overlap between PUSCH and PUCCH, select PUSCH for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined by the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0163] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0164] Rule 2: Select the earliest PUSCH time slot;

[0165] Rule 3: Give priority to dynamically scheduled PUSCH;

[0166] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0167] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0168] In addition, the predefined rules may not include the above rule 2.

[0169] Example 2: PUCCH and PUSCH have the same priority, and the UCI type carried by PUCCH is distinguished.

[0170] When PUSCH and PUCCH of the same priority overlap, the following two situations are distinguished according to the type of UCI carried by PUCCH:

[0171] Case 1: PUCCH contains HARQ-ACK, and UCI is transmitted as follows:

[0172] Method 1: If there is no other overlap between PUSCH and PUCCH after excluding the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, then all PUSCHs that carry CG-UCI and do not support multiplexing of CG-UCI and HARQ-ACK are discarded, and only PUCCH is transmitted. Otherwise, the remaining PUSCHs are selected for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined in the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0173] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0174] Rule 2: Select the earliest PUSCH time slot;

[0175] Rule 3: Give priority to dynamically scheduled PUSCH;

[0176] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0177] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0178] In addition, the predefined rules may not include the above rule 2.

[0179] Method 2: Exclude the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, that is, discard the PUSCH that carries CG-UCI and does not support multiplexing with HARQ-ACK, and process the remaining PUCCH and PUSCH according to the existing protocol process; that is, if there is no overlap between PUSCH and PUCCH, only PUCCH is transmitted; if there is at least one overlap between PUSCH and PUCCH, select PUSCH for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined in the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0180] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0181] Rule 2: Select the earliest PUSCH time slot;

[0182] Rule 3: Give priority to dynamically scheduled PUSCH;

[0183] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0184] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0185] In addition, the predefined rules may not include the above rule 2.

[0186] Case 2: If the PUCCH does not contain HARQ-ACK, the PUSCH is selected for multiplexing transmission according to a predefined rule. The predefined rule is a PUSCH selection rule for UCI multiplexing defined in the 3GPP protocol, for example, the selection may be made according to the priority order of the following rules:

[0187] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0188] Rule 2: Select the earliest PUSCH time slot;

[0189] Rule 3: Give priority to dynamically scheduled PUSCH;

[0190] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0191] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0192] In addition, the predefined rules may not include the above rule 2.

[0193] Example 3: Corresponding to new UE capabilities.

[0194] New UE capabilities are introduced for CG-UCI and HARQ-ACK multiplexing. The following two situations are distinguished based on whether the UE has the corresponding capabilities:

[0195] Case 1: When the UE supports this capability and the base station configures the corresponding function to be enabled, the UCI transmission method is the same as Example 1 or Example 2 and is not described here.

[0196] Case 2: If the UE does not support this capability or the corresponding function is not enabled, the PUSCH is selected for multiplexing transmission according to a predefined rule. The predefined rule is a PUSCH selection rule for UCI multiplexing defined in the 3GPP protocol, for example, the selection may be made according to the priority order of the following rules:

[0197] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0198] Rule 2: Select the earliest PUSCH time slot;

[0199] Rule 3: Give priority to dynamically scheduled PUSCH;

[0200] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0201] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0202] In addition, the predefined rules may not include the above rule 2.

[0203] Example 4: The priorities of PUCCH and PUSCH are different.

[0204] When configuring the multiplexing indication information uci-MuxWithDiffPrio for opening channels with different physical layer priorities, when processing the overlap of PUSCH and PUCCH of different priorities, select all PUSCHs overlapping with PUCCH, excluding the PUSCHs that carry CG-UCI and do not support CG-UCI and HARQ-ACK multiplexing. The UCI transmission method is as follows:

[0205] Method 1: If there is no other overlap between PUSCH and PUCCH after excluding the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, then all PUSCHs that carry CG-UCI and do not support multiplexing of CG-UCI and HARQ-ACK are discarded, and only PUCCH is transmitted. Otherwise, the remaining PUSCHs are selected for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined in the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0206] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0207] Rule 2: Select the earliest PUSCH time slot;

[0208] Rule 3: Give priority to dynamically scheduled PUSCH;

[0209] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0210] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0211] In addition, the predefined rules may not include the above rule 2.

[0212] Method 2: Exclude the PUSCH that carries CG-UCI and does not support multiplexing of CG-UCI and HARQ-ACK, that is, discard the PUSCH that carries CG-UCI and does not support multiplexing with HARQ-ACK, and process the remaining PUCCH and PUSCH according to the existing protocol process; that is, if there is no overlap between PUSCH and PUCCH, only PUCCH is transmitted; if there is at least one overlap between PUSCH and PUCCH, select PUSCH for multiplexing transmission according to predefined rules. The predefined rules are PUSCH selection rules for UCI multiplexing defined in the 3GPP protocol, for example, the selection can be made according to the priority order of the following rules:

[0213] Rule 1: PUSCH carrying A-CSI is preferentially selected for multiplexing;

[0214] Rule 2: Select the earliest PUSCH time slot;

[0215] Rule 3: Give priority to dynamically scheduled PUSCH;

[0216] Rule 4: PUSCH on the serving cell with the smallest serving cell number is selected first;

[0217] Rule 5: Prioritize the PUSCH transmission with the earliest starting position.

[0218] In addition, the predefined rules may not include the above rule 2.

[0219] For Example 4, a processing method similar to that of Example 1 is used for the overlapping of PUCCH and PUSCH of different priorities. In addition, Example 4 can also use a processing method similar to that of Example 2, that is, different processing methods are used to distinguish whether HARQ-ACK is carried in PUCCH, which will not be repeated here.

[0220] The present invention proposes a UCI multiplexing method, and provides specific UCI multiplexing rules for the case where PUSCH and PUCCH overlap, PUSCH carries CG-UCI and does not support multiplexing, thereby reducing UE implementation complexity and ensuring the reliability of CG-UCI.

[0221] Figure 2 This is a second flow chart of the UCI transmission method provided in an embodiment of the present application, such as Figure 2 As shown, an embodiment of the present application provides a UCI transmission method, the execution subject of which may be a network device, such as a base station, etc. The method includes:

[0222] Step 201: If the PUSCH and the PUCCH carrying UCI overlap in the time domain, exclude the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission from the PUSCH;

[0223] Step 202: Determine a target channel for carrying the UCI from the remaining channels, and receive the UCI on the target channel.

[0224] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0225] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0226] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0227] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0228] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0229] Reception of the CG PUSCH is not performed.

[0230] In some embodiments, the UCI is HARQ-ACK information.

[0231] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0232] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0233] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0234] Specifically, the UCI transmission method provided in the embodiment of the present application can refer to the above-mentioned UCI transmission method embodiment in which the execution subject is a terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the above-mentioned corresponding method embodiments will not be described in detail here.

[0235] Figure 3is a schematic diagram of the structure of a terminal provided in an embodiment of the present application, such as Figure 3 As shown, the terminal includes a memory 320, a transceiver 300, and a processor 310, wherein:

[0236] The memory 320 is used to store computer programs; the transceiver 300 is used to send and receive data under the control of the processor 310; the processor 310 is used to read the computer program in the memory 320 and perform the following operations:

[0237] If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH;

[0238] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is sent on the target channel.

[0239] Among them, Figure 3 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 310 and various circuits of memory represented by memory 320 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 300 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and other transmission media. For different user devices, the user interface 330 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0240] The processor 310 is responsible for managing the bus architecture and general processing, and the memory 320 can store data used by the processor 310 when performing operations.

[0241] In some embodiments, the processor 310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0242] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0243] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0244] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0245] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0246] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0247] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0248] The transmission of the CG PUSCH is not performed.

[0249] In some embodiments, the UCI is HARQ-ACK information.

[0250] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0251] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0252] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0253] It should be noted here that the above-mentioned terminal provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the above-mentioned execution subject is the terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0254] Figure 4 is a schematic diagram of the structure of a network device provided in an embodiment of the present application, such as Figure 4 As shown, the network device includes a memory 420, a transceiver 400, and a processor 410, wherein:

[0255] The memory 420 is used to store computer programs; the transceiver 400 is used to send and receive data under the control of the processor 410; the processor 410 is used to read the computer program in the memory 420 and perform the following operations:

[0256] If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH;

[0257] A target channel for carrying the UCI is determined from the remaining channels, and the UCI is received on the target channel.

[0258] Among them, Figure 4 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 410 and memory represented by memory 420. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 400 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 410 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 410 when performing operations.

[0259] The processor 410 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0260] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0261] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0262] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0263] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0264] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0265] Reception of the CG PUSCH is not performed.

[0266] In some embodiments, the UCI is HARQ-ACK information.

[0267] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0268] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0269] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0270] Specifically, the above-mentioned network device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is the network device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0271] Figure 5 is one of the structural diagrams of a UCI transmission device provided in an embodiment of the present application, such as Figure 5 As shown, an embodiment of the present application provides a UCI transmission device, including a first exclusion module 501 and a sending module 502, wherein:

[0272] The first exclusion module 501 is used to exclude the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH if the PUSCH and the PUCCH carrying UCI overlap in the time domain;

[0273] The sending module 502 is configured to determine a target channel for carrying the UCI from the remaining channels, and send the UCI on the target channel.

[0274] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0275] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

[0276] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises:

[0277] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

[0278] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0279] The transmission of the CG PUSCH is not performed.

[0280] In some embodiments, the UCI is hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0281] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by the radio resource control RRC parameters.

[0282] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0283] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0284] Specifically, the above-mentioned UCI transmission device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is a terminal, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0285] Figure 6 This is a second structural diagram of a UCI transmission device provided in an embodiment of the present application, such as Figure 6 As shown, an embodiment of the present application provides a UCI transmission device, including a second exclusion module 601 and a receiving module 602, wherein:

[0286] The second exclusion module 601 is used to exclude the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH if the PUSCH and the PUCCH carrying UCI overlap in the time domain;

[0287] The receiving module 602 is configured to determine a target channel for carrying the UCI from among the remaining channels, and receive the UCI on the target channel.

[0288] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0289] In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

[0290] In some embodiments, determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises:

[0291] In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

[0292] In some embodiments, excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission from the PUSCH includes:

[0293] Reception of the CG PUSCH is not performed.

[0294] In some embodiments, the UCI is HARQ-ACK information.

[0295] In some embodiments, the multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

[0296] In some embodiments, the PUSCH and the PUCCH have the same priority.

[0297] In some embodiments, the PUSCH and the PUCCH have different priorities.

[0298] Specifically, the above-mentioned UCI transmission device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the execution subject is a network device, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0299] It should be noted that the division of units / modules in the above embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0300] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0301] In some embodiments, a non-transitory readable storage medium is further provided, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method provided by the above-mentioned method embodiments.

[0302] Specifically, the above-mentioned non-transitory readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as the method embodiments in this embodiment will not be described in detail here.

[0303] It should be noted that the non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0304] In some embodiments, a processor-readable storage medium is further provided, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method provided by the above-mentioned method embodiments.

[0305] Specifically, the processor-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiments will not be described in detail herein.

[0306] In some embodiments, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the UCI transmission method provided by the above method embodiments.

[0307] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0308] In some embodiments, a communication device is further provided, wherein a computer program is stored in the communication device, and the computer program is used to enable the communication device to execute the UCI transmission method provided by the above-mentioned method embodiments.

[0309] Specifically, the above-mentioned communication device provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as the method embodiments in this embodiment will not be described in detail here.

[0310] In some embodiments, a chip product is further provided, wherein a computer program is stored in the chip product, and the computer program is used to enable the chip product to execute the UCI transmission method provided by the above-mentioned method embodiments.

[0311] Specifically, the above-mentioned chip product provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0312] It should also be noted that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0313] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0314] "Determine B based on A" in the embodiments of the present application means that the factor A should be considered when determining B. It is not limited to "B can be determined based on A alone", but should also include: "Determine B based on A and C", "Determine B based on A, C and E", "Determine C based on A, and further determine B based on C", etc. In addition, it can also include taking A as a condition for determining B, for example, "When A meets the first condition, use the first method to determine B"; for another example, "When A meets the second condition, determine B", etc.; for another example, "When A meets the third condition, determine B based on the first parameter", etc. Of course, it can also be a condition that takes A as a factor for determining B, for example, "When A meets the first condition, use the first method to determine C, and further determine B based on C", etc.

[0315] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0316] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0317] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0318] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0319] Network devices and terminal devices can each use one or more antennas for multi-input multi-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.

[0320] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0321] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0322] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0323] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0324] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for transmitting uplink control information (UCI), characterized in that: Applied to terminals, including: If the physical uplink shared channel PUSCH and the physical uplink control channel PUCCH carrying UCI overlap in the time domain, the configuration scheduling CGPUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH; A target channel for carrying the UCI is determined from the remaining channels, and the UCI is sent on the target channel.

2. The UCI transmission method according to claim 1, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises: In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

3. The UCI transmission method according to claim 1, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises: In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

4. The UCI transmission method according to claim 1, characterized in that: Excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission in the PUSCH, including: The transmission of the CG PUSCH is not performed.

5. The UCI transmission method according to any one of claims 1 to 4, characterized in that: The UCI is hybrid automatic repeat request acknowledgement HARQ-ACK information.

6. The UCI transmission method according to any one of claims 1 to 5, characterized in that: The multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by the radio resource control RRC parameter.

7. The UCI transmission method according to any one of claims 1 to 6, characterized in that: The PUSCH and the PUCCH have the same priority.

8. The UCI transmission method according to any one of claims 1 to 6, characterized in that: The PUSCH and the PUCCH have different priorities.

9. A UCI transmission method, characterized in that: Applied to network equipment, including: If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH; A target channel for carrying the UCI is determined from the remaining channels, and the UCI is received on the target channel.

10. The UCI transmission method according to claim 9, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises: In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

11. The UCI transmission method according to claim 9, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises: In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

12. The UCI transmission method according to claim 9, characterized in that: Excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission in the PUSCH, including: Reception of the CG PUSCH is not performed.

13. The UCI transmission method according to any one of claims 9 to 12, characterized in that: The UCI is HARQ-ACK information.

14. The UCI transmission method according to any one of claims 9 to 13, characterized in that: The multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

15. The UCI transmission method according to any one of claims 9 to 14, characterized in that: The PUSCH and the PUCCH have the same priority.

16. The UCI transmission method according to any one of claims 9 to 14, characterized in that: The PUSCH and the PUCCH have different priorities.

17. A terminal, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH; A target channel for carrying the UCI is determined from the remaining channels, and the UCI is sent on the target channel.

18. The terminal according to claim 17, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises: In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is sent on the PUCCH.

19. The terminal according to claim 17, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and sending the UCI on the target channel, comprises: In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and transmit the UCI.

20. The terminal according to claim 17, characterized in that: Excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission in the PUSCH, including: The transmission of the CG PUSCH is not performed.

21. The terminal according to any one of claims 17 to 20, characterized in that: The UCI is HARQ-ACK information.

22. The terminal according to any one of claims 17 to 21, characterized in that: The multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

23. The terminal according to any one of claims 17 to 22, characterized in that: The PUSCH and the PUCCH have the same priority.

24. The terminal according to any one of claims 17 to 22, characterized in that: The PUSCH and the PUCCH have different priorities.

25. A network device, characterized in that: Including memory, transceiver, processor; A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: If the PUSCH and the PUCCH carrying UCI overlap in the time domain, the CG PUSCH carrying configuration scheduling uplink control information and not supporting UCI multiplexing transmission is excluded from the PUSCH; A target channel for carrying the UCI is determined from the remaining channels, and the UCI is received on the target channel.

26. The network device according to claim 25, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises: In a case where there is no PUSCH in the remaining channels, the CG PUSCH is discarded and the UCI is received on the PUCCH.

27. The network device according to claim 25, characterized in that: The determining a target channel for carrying the UCI from the remaining channels, and receiving the UCI on the target channel, comprises: In the case that there is a PUSCH in the remaining channels, one of the PUSCHs is selected based on a predefined rule to multiplex and receive the UCI.

28. The network device according to claim 25, characterized in that: Excluding the CG PUSCH that carries configuration scheduling uplink control information and does not support UCI multiplexing transmission in the PUSCH, including: Reception of the CG PUSCH is not performed.

29. The network device according to any one of claims 25 to 28, characterized in that: The UCI is HARQ-ACK information.

30. The network device according to any one of claims 25 to 29, characterized in that: The multiplexing transmission of UCI can be performed only when the terminal has the corresponding terminal capability, and whether to perform the multiplexing transmission of UCI is configured by RRC parameters.

31. The network device according to any one of claims 25 to 30, characterized in that: The PUSCH and the PUCCH have the same priority.

32. The network device according to any one of claims 25 to 30, characterized in that: The PUSCH and the PUCCH have different priorities.

33. A UCI transmission device, characterized in that: include: A first exclusion module is configured to exclude, if the PUSCH and the PUCCH carrying the UCI overlap in the time domain, the CG PUSCH carrying the configuration scheduling uplink control information and not supporting the UCI multiplexing transmission in the PUSCH; The sending module is used to determine a target channel for carrying the UCI from the remaining channels, and send the UCI on the target channel.

34. A UCI transmission device, characterized in that: include: A second exclusion module is configured to exclude, if the PUSCH and the PUCCH carrying the UCI overlap in the time domain, the CG PUSCH carrying the configuration scheduling uplink control information and not supporting the UCI multiplexing transmission in the PUSCH; The receiving module is used to determine a target channel for carrying the UCI from the remaining channels, and receive the UCI on the target channel.

35. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method according to any one of claims 1 to 8.

36. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the UCI transmission method according to any one of claims 9 to 16.

Images