UCI transmission method, UCI reception method, communication device, storage medium, and computer program product

Abstract

The present application relates to the technical field of wireless communications, and discloses a UCI transmission method, a UCI reception method, a communication device, a storage medium, and a computer program product. The UCI reception method comprises: a base station transmitting downlink control information (DCI) in a DCI format for scheduling a physical downlink shared channel (PDSCH), wherein the DCI triggers a target PUSCH; and the base station receiving the target PUSCH from a target slot, wherein a HARQ-ACK triggered by the DCI is carried on the target PUSCH.

Description

Uci sending and receiving method, communication device, storage medium and computer program product

[0001] Cross-reference

[0002] The present application claims priority to the Chinese patent application No. 202410779904.2, filed on June 17, 2024, and entitled "Uci sending and receiving method, communication device, storage medium and computer program product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] Embodiments of the present application relate to the technical field of cloud terminal, in particular to a UCI sending and receiving method, communication device, storage medium and computer program product. BACKGROUND

[0004] In the related art, the Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) is carried through the Physical Uplink Control CHannel (PUCCH).

[0005] However, in some cases, the channel carrying the HARQ-ACK will be changed by the multi-channel multiplexing rule.

[0006] For example, if the PUCCH carrying the HARQ-ACK overlaps in time domain with a Physical Uplink Shared CHannel (PUSCH) carrying uplink data, the HARQ-ACK is multiplexed in the PUSCH by performing multiplexing between the PUCCH and the PUSCH. That is, the HARQ-ACK is transmitted in part of the resources of the PUSCH, and part of the resources originally allocated for uplink data is used to carry the HARQ-ACK. Finally, the PUCCH is not transmitted, and the PUSCH is transmitted.

[0007] If the PUCCH carrying the HARQ-ACK overlaps in time domain with another PUCCH carrying Uplink Control Information (UCI), the two PUCCHs are multiplexed, and finally their UCI is transmitted in a multiplexed PUCCH. The multiplexed PUCCH is transmitted. The original PUCCH can not be transmitted.

[0008] If the PUCCH carrying HARQ-ACK does not overlap in time domain with the PUSCH carrying uplink data or with another PUCCH carrying UCI, the PUCCH carrying HARQ-ACK is transmitted.

[0009] Therefore, the above-mentioned multi-channel multiplexing process occurs between PUCCHs and between PUCCHs and PUSCHs. These multiplexing needs to comply with some predefined timelines, and the multiplexing rules are relatively complex. For example, due to the number of overlapping channels, the number and position of overlapping symbols, the type of UCI carried by the overlapping channels, and whether the overlapping channels have repeated transmission, these factors will affect the specific multiplexing rules.

[0010] Therefore, in the related art, the uplink channel multiplexing rule is too complex, and how to avoid or simplify the multiplexing rule is a technical problem to be solved in the related art. SUMMARY

[0011] Embodiments of the present application provide a UCI sending and receiving method, a communication device, a storage medium and a computer program product.

[0012] In a first aspect, a UCI receiving method is provided, including: a base station sending a DCI (Downlink Control Information) in a DCI (Downlink Control Information) format for scheduling a PDSCH (Physical Downlink Shared Channel), wherein the DCI triggers a target PUSCH; and the base station receiving the target PUSCH from a target slot, wherein the HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0013] In a second aspect, an uplink control information sending method is provided, including: a terminal receiving a DCI in a DCI format for scheduling a PDSCH, wherein the DCI triggers a target PUSCH; and the terminal sending the target PUSCH in a target slot, wherein the HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0014] In a third aspect, a communication device is provided, including a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0015] In a fourth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0016] In a fifth aspect, a computer program product is provided, and the computer program product comprises a computer program stored on a non-transitory computer readable storage medium, and the computer program comprises program instructions, and the program instructions, when executed by a computer, cause the computer to perform the method according to the first aspect or the method according to the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0018] FIG. 1 shows a time domain diagram according to an example embodiment of the present application;

[0019] FIG. 2 shows a time domain diagram according to another example embodiment of the present application;

[0020] FIG. 3 shows a flow diagram of a method for receiving uplink control information according to an example embodiment of the present application;

[0021] FIG. 4 shows a flow diagram of a method for sending uplink control information according to an example embodiment of the present application;

[0022] FIG. 5 shows a structure diagram of a communication device according to an example embodiment of the present application;

[0023] FIG. 6 shows a structure diagram of a terminal according to an example embodiment of the present application;

[0024] FIG. 7 shows a structure diagram of a base station according to an example embodiment of the present application. DETAILED DESCRIPTION

[0025] The example embodiments will be described in detail herein with reference to the attached drawings. The following description is made with reference to the accompanying drawings, in which like reference numerals refer to like elements, and by way of non-limiting example. The following description of example embodiments does not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0026] In the related art, the PUCCH resource set carrying UCI can be configured with at least 2 sets and at most 4 sets, and each set is configured with a corresponding bit range. One set contains multiple PUCCH resources. Among them, the first PUCCH resource set corresponds to 1-2 bits. The bit number of the remaining PUCCH resource set is configured and is greater than 2 bits.

[0027] If one or more downlink control information (DCI) respectively schedules multiple physical downlink shared channels (PDSCH), and the corresponding hybrid automatic repeat request acknowledgement (HARQ-ACK) is indicated to be sent in the same slot, then according to the PUCCH resource indicator (PRI) in the last DCI in the DCI, a PUCCH resource is determined from the determined PUCCH resource set for the HARQ-ACK of the multiple PDSCH. Among them, the HARQ-ACK in the same slot is transmitted as a HARQ-ACK codebook in the determined PUCCH resource.

[0028] However, in the related art, in this scenario, the PUCCH carrying HARQ-ACK may overlap in the time domain with the PUSCH carrying uplink data or with another PUCCH carrying UCI, so that uplink channel multiplexing needs to be performed according to the multiplexing rule, and the multiplexing rule in the related art is relatively complex. Therefore, the embodiments of the present application provide an improved design method to avoid or simplify the multiplexing rule.

[0029] In the embodiments of the present application, the base station and the UE agree in advance:

[0030] If the base station sends a DCI in the PDCCH, the DCI schedules a PDSCH (for example, contains the time-frequency resource of the PDSCH, etc.), and at the same time, the DCI triggers (for example, schedules or indicates) a PUSCH, then the base station receives the HARQ-ACK of the PDSCH in the PUSCH in slot n. Referring to FIG. 1. Among them, the DCI is a DCI of the DCI format scheduling the PDSCH, that is, the DCI is defined as a DCI format scheduling the PDSCH.

[0031] In one implementation, the DCI can also indicate the above-mentioned one slot n.

[0032] That is, if a UE receives a DCI in a PDCCH, the DCI schedules a PDSCH (e.g., the DCI contains time-frequency resources of the PDSCH, etc.), while the DCI also indicates a slot n, while the DCI also schedules / indicates a PUSCH, then the UE receives the PDSCH according to the time-frequency resources, and transmits the HARQ-ACK of the PDSCH in the PUSCH in the slot n.

[0033] wherein the PUSCH is transmitted by the UE in the slot n, and the HARQ-ACK of the PDSCH is carried in the PUSCH. The PUSCH is used to carry UCI (not carrying uplink data), or the PUSCH is a PUSCH that does not transmit uplink data but transmits UCI.

[0034] In addition, for some DCI that does not schedule data is received, the UE is required to provide the HARQ-ACK of the DCI, also included in the technical solutions provided by the embodiments of the present application.

[0035] Referring to FIG. 2, a base station sends a DCI in a PDCCH, and at the same time the DCI indicates a slot n, and at the same time the DCI schedules / indicates a PUSCH, and the DCI is required to provide HARQ-ACK. The HARQ-ACK can indicate that the DCI is correctly received. In this case, the HARQ-ACK does not correspond to a PDSCH, but it corresponds to the DCI in the PDCCH. That is, the DCI does not schedule data (PDSCH), but requires to provide HARQ-ACK for the DCI. That is, if the DCI is correctly received by the UE, the UE is required to provide HARQ-ACK (the HARQ-ACK is ACK). Wherein the DCI is also a DCI of a DCI format that schedules a PDSCH, that is, the DCI is defined as a DCI format that schedules a PDSCH.

[0036] For example, the DCI includes but is not limited to at least one of the following: a DCI used to indicate SCell dormancy and not scheduling PDSCH, a DCI used to release Semi-Persistent Scheduling (SPS) configuration (not scheduling PDSCH either), a DCI used to indicate Transmission Configuration Indicator (TCI) update. For the DCI requiring HARQ-ACK as described above, the base station and the UE agree that: the base station sends the DCI to inform the UE to perform the above-mentioned SCell dormancy or release SPS configuration, and at the same time indicates a slot n in the DCI, and the DCI schedules / indicates a PUSCH. The base station receives the HARQ-ACK of the DCI in the PUSCH in slot n. Correspondingly, the UE receives the DCI, the UE performs the above-mentioned SCell dormancy or release SPS configuration, and transmits the HARQ-ACK of the DCI in the PUSCH in slot n.

[0037] In this case, the DCI no longer needs to indicate slot n.

[0038] In this case, the DCI schedules / indicates a PUSCH, including: scheduling a PUSCH in slot n by including the time domain resource and / or frequency domain resource of the PUSCH in the DCI, or determining a PUSCH resource from a determined set of PUSCH resources by including a PUSCH resource indication information in the DCI. That is, the DCI schedules / indicates a PUSCH can be that the DCI schedules a PUSCH in slot n through the time domain resource and / or frequency domain resource of the PUSCH, or the DCI schedules / indicates a PUSCH can be that the DCI indicates a PUSCH resource in a determined set of PUSCH resources through a PUSCH resource indication information in the DCI. Wherein, the way of carrying UCI by the PUSCH includes: carrying UCI as a MAC CE through the PUSCH, or carrying UCI as UL data.

[0039] In this case, the DCI can be achieved by adding a parameter in the DCI format scheduling PDSCH to schedule / indicate the resource of PUSCH. The DCI format can include but is not limited to at least one of the following: a DCI format defined for scheduling PDSCH, a DCI format defined for scheduling PUSCH, a DCI format defined as a new type of joint scheduling of PDSCH and PUSCH.

[0040] Wherein, about the slot n, it can be further defined as follows:

[0041] (1) If the DCI schedules PDSCH:

[0042] • slot n is the slot obtained by counting n slots backward from the slot where the PDSCH is located. The n slot counting is for DL slots, UL slots, flexible slots, that is, for all slots. Or,

[0043] • slot n is the slot obtained by counting n slots backward from the slot where the PDSCH is located, and from the first flexible slot or UL slot. The n slot counting is only for UL slots and / or flexible slots.

[0044] (2) If the DCI does not schedule PDSCH:

[0045] • slot n is the slot obtained by counting n slots backward from the slot where the PDCCH is located. The n slot counting is for DL slots, UL slots, flexible slots, that is, for all slots. Or,

[0046] • slot n is the slot obtained by counting n slots backward from the slot where the PDCCH is located, and from the first flexible slot or UL slot. The n slot counting is only for UL slots and / or flexible slots.

[0047] The technical solutions provided by the embodiments of the present application will be described below from the perspective of the base station and the terminal respectively.

[0048] FIG. 3 shows a flowchart of a UCI receiving method provided by an exemplary embodiment of the present application, which can be executed by a base station. As shown in FIG. 3, the method mainly includes the following steps:

[0049] Step S310, the base station sends a DCI of DCI format for scheduling PDSCH, wherein the DCI triggers a target PUSCH.

[0050] The format of the DCI sent by the base station is a DCI format for scheduling a PDSCH. In the related art, in a typical case, the DCI for scheduling downlink data (for example, a PDSCH) and the DCI for scheduling uplink data (for example, a PUSCH) are respectively independently designed DCI, and the related information carried by them also has a large difference, so in the related art, they have independent DCI formats. That is, the base station wants to schedule a PDSCH, and the base station sends a DCI of a DCI format associated with downlink data. The base station wants to schedule uplink data, and the base station sends a DCI of a DCI format associated with uplink data. In the embodiment of the application, although the DCI sent by the base station adopts the DCI format for scheduling a PDSCH, the DCI simultaneously triggers a target PUSCH.

[0051] In the embodiment of the application, the DCI can schedule a PDSCH, or the DCI can also not schedule a PDSCH, but requires the terminal to provide HARQ-ACK of the DCI.

[0052] In step S312, the base station receives the target PUSCH from a target slot, wherein the HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0053] In the embodiment of the application, the base station receives the target PUSCH carrying the HARQ-ACK triggered by the DCI from a target slot.

[0054] In the embodiment of the application, the target slot can be indicated in the DCI or can be agreed by the protocol. Therefore, in one implementation, the DCI further includes a target slot indication field, and the target slot indication field is used to indicate a slot as the target slot, wherein the HARQ-ACK is transmitted in the target slot. That is, the target slot indication field is used to indicate a slot as the target slot, and the terminal transmits the HARQ-ACK triggered by the DCI in the target slot.

[0055] In one implementation, the target slot indication field can indicate an n value, n is an integer greater than or equal to 0.

[0056] In one implementation, in response to the DCI scheduling a PDSCH, the target slot is determined by one of the following:

[0057] 1) The target slot is a slot after the slot where the PDSCH is located, and is spaced n slots from the last slot where the PDSCH is located.

[0058] 2) the target slot is a slot which is n slots away from the first slot available for uplink transmission after the slot where the PDSCH is located, and the slot available for uplink transmission includes at least one of a flexible slot and an uplink slot.

[0059] In another embodiment, in response to the DCI not scheduling a PDSCH, the target slot is determined by one of the following:

[0060] 1) the target slot is a slot which is n slots away from the last slot where the DCI is located after the slot where the DCI is located.

[0061] 2) the target slot is a slot which is n slots away from the first slot available for uplink transmission after the slot where the DCI is located, and the slot available for uplink transmission includes at least one of a flexible slot and an uplink slot.

[0062] By the technical scheme provided by the embodiments of the present application, the base station triggers a target PUSCH by a DCI format of a DCI scheduling a PDSCH, and then receives the target PUSCH from a target slot, and the target PUSCH carries the HARQ-ACK triggered by the DCI, so that the HARQ-ACK can be carried on the PUSCH, and the PUCCH carrying the HARQ-ACK and the PUSCH are multiplexed in the time domain to avoid overlapping.

[0063] In an implementation manner, the DCI can also schedule a PDSCH; in response to the DCI also scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the PDSCH. That is, the HARQ-ACK received by the base station in the target slot is the HARQ-ACK of the PDSCH.

[0064] In another implementation manner, the DCI can not schedule a PDSCH; in response to the DCI not scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the DCI.

[0065] In an implementation manner, in response to the DCI not scheduling a PDSCH, the DCI can be used for at least one of the following:

[0066] 1) indicating that a secondary cell is dormant and no downlink data is scheduled; for example, the DCI does not schedule a PDSCH, but the DCI contains information indicating that the SCell is dormant and resource information of the PUSCH (including time domain resource information of the PUSCH and / or frequency domain resource information of the PUSCH).

[0067] 2) indicating a Transmission Configuration Indicator (TCI) update; for example, the DCI does not schedule a PDSCH, but the DCI contains TCI information and resource information of a PUSCH (including time domain resource information of the PUSCH and / or frequency domain resource information of the PUSCH) at the same time.

[0068] 3) indicating a release of a semi-persistent scheduling configuration. For example, the DCI does not schedule a PDSCH, but the DCI contains information of a release of an SPS configuration and resource information of a PUSCH (including time domain resource information of the PUSCH and / or frequency domain resource information of the PUSCH) at the same time.

[0069] Through the above implementation manner, in the case that the DCI does not schedule a PDSCH but is required to provide a HARQ-ACK, a target PUSCH can be triggered by the DCI, and the HARQ-ACK is carried by the target PUSCH, without scheduling a PUCCH to carry the HARQ-ACK, so that the case that the PUCCH carrying the HARQ-ACK and the PUSCH overlap in the time domain and cause uplink channel multiplexing can be avoided.

[0070] In one implementation manner, the DCI triggering a target PUSCH can include that the DCI contains a PUSCH time domain resource field and / or a PUSCH frequency domain resource field for allocating a PUSCH resource, and the base station transmits the target PUSCH by allocating a PUSCH resource (for example, the PUSCH resource is allocated from a frequency domain bandwidth configured by the base station for UL transmission) through the PUSCH time domain resource field and / or the PUSCH frequency domain resource field. That is, in this implementation manner, the DCI can schedule the target PUSCH, and the DCI contains information for indicating a time domain resource and / or a frequency domain resource of the target PUSCH.

[0071] In another implementation manner, the DCI triggering a target PUSCH includes that the DCI contains a PUSCH resource indication field and the PUSCH resource indication field is used to indicate a PUSCH resource from a PUSCH resource set, and the base station transmits the target PUSCH by indicating a PUSCH resource from the determined PUSCH resource set through the PUSCH resource indication field. That is, in this implementation manner, the DCI can contain indication information for indicating a PUSCH resource in a PUSCH resource set, and the PUSCH resource indicated by the indication information is a PUSCH resource in the determined PUSCH resource set.

[0072] In the foregoing implementation manner, the method can further include: the base station configuring the terminal with at least one PUSCH resource set, each PUSCH resource set being associated with a bit quantity range of UCI, wherein the determined PUSCH resource set is determined based on the bit quantity of UCI from the at least one PUSCH resource set. That is, the base station can configure the terminal with at least one PUSCH resource set, each PUSCH resource set being associated with a bit quantity range of UCI, the base station can determine a PUSCH resource set from the at least one PUSCH resource set based on the bit quantity of the HARQ-ACK to be transmitted, indicate one PUSCH resource in the determined PUSCH resource set through the DCI for transmitting the target PUSCH, and the terminal can determine a PUSCH resource set from the at least one PUSCH resource set based on the bit quantity of the HARQ-ACK to be transmitted, and determine one PUSCH resource from the determined PUSCH resource set according to the indication of the DCI, and transmit the target PUSCH through the PUSCH resource.

[0073] wherein one of the PUSCH resource sets contains at least one PUSCH resource for UCI, and the one PUSCH resource includes at least one of the following information: a starting symbol, a number of consecutive symbols, a PUSCH frequency hopping enabling parameter, a number of repetitions, a PUSCH format, a starting resource block (RB), a starting RB of a second frequency hop, a number of RBs, a code word length of an orthogonal convolutional code (OCC), an OCC index, code rate information, a modulation and coding scheme (MCS) level, modulation information, MCS table information, demodulation reference signal (DMRS) related information, beta offset (βOffset) information, a starting resource element (RE) group, a number of resource element groups (REGs), and a starting REG of a second frequency hop.

[0074] In one implementation manner, the DCI can be multiple, and the multiple DCIs indicate the same target slot, and the HARQ-ACKs triggered by the multiple DCIs are carried on the target PUSCH, for example, multiple HARQ-ACKs triggered by multiple DCIs are concatenated, encoded, and then transmitted by the UE in the target PUSCH in slot n.

[0075] In the above implementation manner, the target PUSCH is determined by one of the following manners:

[0076] 1) based on a PUSCH resource indication field in a last DCI of the plurality of DCIs;

[0077] 2) based on a PUSCH time domain resource field and / or a PUSCH frequency domain resource field in the last DCI of the plurality of DCIs.

[0078] In the above implementation manner, the plurality of DCIs comprises at least one of the following:

[0079] 1) a DCI scheduling a PDSCH.

[0080] 2) a DCI not scheduling a PDSCH but being indicated to transmit HARQ-ACK information in the target slot.

[0081] Through the above technical solution provided by the embodiments of the present application, the base station triggers a target PUSCH through a DCI of a DCI format scheduling a PDSCH, and then receives the target PUSCH from the target slot, and the target PUSCH carries the HARQ-ACK triggered by the DCI, so that the HARQ-ACK can be carried on the PUSCH, and the multiplexing channel caused by the PUCCH carrying the HARQ-ACK and the PUSCH overlapping in the time domain can be avoided.

[0082] FIG. 4 shows a flowchart of an uplink control information sending method according to an example embodiment of the present application, which can be executed by a terminal. The method is the operation of the terminal corresponding to the method shown in FIG. 3, has the same or corresponding implementation manners as the method shown in FIG. 3, and the following mainly describes the operation of the terminal, and the details can be referred to the above description.

[0083] As shown in FIG. 4, the uplink control information sending method mainly comprises the following steps.

[0084] Step S410, the terminal receives a DCI of a DCI format scheduling a PDSCH, wherein the DCI triggers a target PUSCH.

[0085] The DCI can be the DCI sent by the base station according to the method shown in FIG. 3.

[0086] In one implementation manner, the DCI also schedules a PDSCH; in response to the DCI also scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the PDSCH.

[0087] In an implementation, the DCI does not schedule a PDSCH; and in response to the DCI not scheduling a PDSCH, the DCI-triggered HARQ-ACK is a HARQ-ACK of the DCI.

[0088] In an implementation, the DCI not scheduling a PDSCH can be used for at least one of the following:

[0089] 1) indicating a secondary cell dormancy and not scheduling downlink data.

[0090] 2) indicating a TCI update.

[0091] 3) indicating a release of a semi-persistent scheduling configuration.

[0092] S412, the terminal transmits the target PUSCH in a target slot, wherein the DCI-triggered HARQ-ACK is carried on the target PUSCH.

[0093] After receiving the DCI, the terminal transmits the target PUSCH carrying the DCI-triggered HARQ-ACK in a target slot. Instead of carrying the HARQ-ACK through a PUCCH, uplink channel multiplexing caused by the PUCCH carrying the HARQ-ACK and the PUSCH overlapping in the time domain can be avoided.

[0094] In the embodiments of the present application, the target slot can be indicated by the DCI or agreed by a protocol. In an implementation, the DCI further includes a target slot indication field, and the target slot indication field is used to indicate a slot as the target slot, wherein the HARQ-ACK is transmitted in the target slot. That is, an indication information for indicating the target slot is included in the DCI, and through the indication of the indication information, the terminal can determine the target slot.

[0095] In an implementation, the target slot indication field indicates an n value, n being an integer greater than or equal to 0; and in response to the DCI scheduling a PDSCH, the target slot is determined to include one of the following:

[0096] 1) the target slot is a slot after the slot where the PDSCH is located and spaced n slots from the last slot where the PDSCH is located.

[0097] 2) the target slot is a slot spaced n slots from the first slot after the slot where the PDSCH is located and available for uplink transmission, the slot available for uplink transmission including at least one of a flexible slot and an uplink slot.

[0098] In another implementation, the target slot indication field indicates an n value, n being an integer greater than or equal to 0; and in response to the DCI not scheduling a PDSCH, the target slot is determined by one of:

[0099] 1) the target slot is a slot after the slot where the DCI is located and spaced n slots from the last slot where the DCI is located;

[0100] 2) the target slot is a slot spaced n slots from the first slot after the slot where the DCI is located that can be used for uplink transmission, the slot that can be used for uplink transmission including at least one of a flexible slot and an uplink slot.

[0101] In one implementation, the DCI triggers a target PUSCH, including that the DCI contains a PUSCH time domain resource field and / or a PUSCH frequency domain resource field for allocating PUSCH resources, wherein the terminal determines a PUSCH resource through the PUSCH time domain resource field and / or the PUSCH frequency domain resource field to transmit the target PUSCH. That is, the indication information indicating the time domain resource and / or the frequency domain resource of the PUSCH is included in the DCI, and the terminal determines a PUSCH resource based on the indication information, and transmits the target PUSCH through the PUSCH resource, that is, the DCI schedules a target PUSCH, and the terminal transmits the target PUSCH on the PUSCH resource indicated by the DCI based on the scheduling of the DCI, and the target PUSCH can carry the HARQ-ACK triggered by the DCI.

[0102] In another implementation, the DCI triggers a target PUSCH, including that the DCI contains a PUSCH resource indication field and the PUSCH resource indication field is used to indicate a PUSCH resource from a PUSCH resource set, wherein the terminal determines a PUSCH resource from the determined PUSCH resource set through the PUSCH resource indication field to transmit the target PUSCH.

[0103] In one implementation, the method can further include that the terminal is configured at least one PUSCH resource set, and each PUSCH resource set is associated with a bit quantity range of UCI.

[0104] In one implementation, the method can further include that the terminal determines a PUSCH resource set from the at least one PUSCH resource set based on the bit quantity of UCI (i.e. the HARQ-ACK triggered by the DCI).

[0105] By the above implementation manner, the terminal can determine one PUSCH resource from the one PUSCH resource set according to the indication of the DCI, and transmit the HARQ-ACK triggered by the DCI through the PUSCH resource.

[0106] In one implementation manner, the one PUSCH resource set includes at least one PUSCH resource for UCI, and the one PUSCH resource includes at least one of the following information: a starting symbol, a number of consecutive symbols, a PUSCH frequency hopping enabling parameter, a number of repetitions, a PUSCH format, a starting RB, a starting RB of a second frequency hopping, a number of RBs, a code word length of OCC, an OCC index, code rate information, an MCS level, modulation information, MCS table information, DMRS related information, beta offset information, a starting RE group, a number of REGs, and a starting RE group of a second frequency hopping.

[0107] In one implementation manner, the DCI is multiple, and the multiple DCIs indicate the same target slot; the method can further include that the terminal carries the HARQ-ACK triggered by the multiple DCIs on the target PUSCH. For example, the terminal can carry the multiple HARQ-ACKs triggered by the multiple DCIs in the target PUSCH after serially encoding the multiple HARQ-ACKs.

[0108] In the above implementation manner, the target PUSCH is determined by one of the following manners:

[0109] 1) based on a PUSCH resource indication field in the last DCI of the multiple DCIs.

[0110] 2) based on a PUSCH time domain resource field and / or a PUSCH frequency domain resource field in the last DCI of the multiple DCIs.

[0111] In one implementation manner, the multiple DCIs include at least one of the following:

[0112] 1) a DCI scheduling a PDSCH.

[0113] 2) a DCI not scheduling a PDSCH but indicating to transmit HARQ-ACK information in the target slot.

[0114] By the technical scheme provided in the embodiments of the present application, the HARQ-ACK information triggered by the DCI can be carried and transmitted on the target PUSCH triggered by the DCI, so that the PUSCH carrying the HARQ-ACK and other uplink channels can be avoided from overlapping in the time domain, and uplink channel multiplexing can be avoided.

[0115] The specific implementation manners of the technical scheme provided in the embodiments of the present application are further described below.

[0116] In the related art, typically, the DCI for scheduling downlink data (e.g. PDSCH) and the DCI for scheduling uplink data (e.g. PUSCH) are respectively independently designed DCI, and the related information carried by them also has great difference, so in the current communication standard, they have independent DCI formats. That is, if the base station wants to schedule a PDSCH, the base station sends a DCI format associated with the downlink data. If the base station wants to schedule uplink data, the base station sends a DCI format associated with the uplink data.

[0117] In the embodiment of the present application, the DCI sent by the base station adopts the DCI format for scheduling PDSCH, and at the same time, the DCI also triggers a target PUSCH, so the HARQ-ACK triggered by the DCI can be carried on the target PUSCH for transmission.

[0118] In the embodiment of the present application, the DCI triggering a target PUSCH can have two implementation manners, the first one is that the DCI schedules a target PUSCH, that is, the DCI can indicate the time domain and / or frequency domain resources of the PUSCH resource of the target PUSCH. The second one is that the DCI indicates a PUSCH resource, which is a PUSCH resource in a PUSCH resource set in at least one PUSCH resource set configured by the base station for the terminal, and the terminal or the base station can determine the PUSCH resource set from the at least one PUSCH resource set based on the bit number of the HARQ-ACK triggered by the DCI.

[0119] The two implementation manners are described respectively as follows.

[0120] Implementation manner one: the DCI schedules a target PUSCH

[0121] In this implementation manner, the DCI contains PUSCH time domain resource field and / or PUSCH frequency domain resource field for allocating PUSCH resource.

[0122] This implementation manner can further include the following three instances, which are described respectively as follows.

[0123] Instance 1: the DCI schedules PDSCH, requires to provide the HARQ-ACK of the PDSCH, and does not require to provide the HARQ-ACK of the DCI.

[0124] Base station side

[0125] In this example, the base station can send one DCI for the UE through the PDCCH, and the DCI contains the time-frequency resource information of one or more PDSCHs, and the DCI also contains the resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) information of one or more PUSCHs. That is, the time domain resource of the PDSCH, the frequency domain resource of the PDSCH, and the resource of the PUSCH are contained in one DCI. That is, in a DCI format for scheduling the PDSCH, in addition to containing the time domain resource information of the PDSCH and the frequency domain resource information of the PDSCH, the PUSCH resource information for scheduling the PUSCH is also contained.

[0126] In one implementation, the DCI can also directly indicate or implicitly indicate a slot n. The base station and the UE agree that the base station receives a PUSCH in the slot n, where the PUSCH is determined to be in the slot n according to the time-frequency resource of the PUSCH, that is, the PUSCH can be determined in the slot n according to the time-frequency resource of the PUSCH.

[0127] In one implementation, the DCI can also directly indicate or implicitly indicate a slot m, and the base station and the UE agree that the base station transmits a PDSCH in the slot m, where the PDSCH is determined to be in the slot m according to the time-frequency resource of the PDSCH.

[0128] In one implementation, the base station and the UE agree that the HARQ-ACK of the PDSCH is carried in the PUSCH.

[0129] Generally, the slot m is earlier than the slot n. The PUSCH is used to carry the UCI (not to carry the uplink data), or the PUSCH is a PUSCH that does not transmit the uplink data but transmits the UCI.

[0130] The base station and the UE agree that if multiple DCIs described above are transmitted from the base station, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the PDSCHs scheduled by the multiple DCIs described above are all indicated to be transmitted in the slot n, then the base station expects to receive these HARQ-ACKs in one PUSCH. Where the one PUSCH is determined to be in the slot n based on the resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) of the PUSCH in the last DCI of the multiple DCIs described above. For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in the slot n.

[0131] UE side

[0132] In this example, the UE receives a DCI in PDCCH, and the DCI indicates time-frequency resources of one or more PDSCHs, and the DCI also contains resources of one or more PUSCHs (here, the resources of the PUSCHs include PUSCH time-domain resources and / or PUSCH frequency-domain resources). That is, the UE receives a DCI, which contains PDSCH time-domain resources, PDSCH frequency-domain resources, and resources of PUSCHs. That is, the UE receives a DCI, which is a DCI format scheduling PDSCHs, but in addition to containing PDSCH time-domain resources and PDSCH frequency-domain resources, the DCI also contains PUSCH resources scheduling PUSCHs.

[0133] In the above case, the UE performs the following processing: the UE receives one or more PDSCHs according to the PDSCH time-domain resources and PDSCH frequency-domain resources, and carries HARQ-ACK of the one or more PDSCHs in a PUSCH obtained according to the resources of the PUSCHs, and transmits the PUSCH. That is, the UE receives one or more PDSCHs according to PDSCH time-domain resources and PDSCH frequency-domain resources in the DCI, and carries HARQ-ACK of the one or more PDSCHs on a PUSCH, which is obtained according to PUSCH resource information contained in the DCI scheduling PUSCHs.

[0134] In an implementation manner, the DCI can also directly indicate or implicitly indicate a slot n. The base station and the UE agree that the UE transmits a PUSCH in the slot n, where the PUSCH is determined to be in the slot n according to the time-frequency resources of the PUSCH.

[0135] In an implementation manner, the DCI can also directly indicate or implicitly indicate a slot m, and the base station and the UE agree that the UE receives a PDSCH in the slot m, where the PDSCH is determined to be in the slot m according to the time-frequency resources of the PDSCH.

[0136] In an implementation manner, the base station and the UE agree that the UE carries HARQ-ACK of the PDSCH in the PUSCH.

[0137] Generally, the slot m is earlier than the slot n. The PUSCH is used to carry UCI (not to carry uplink data), or the PUSCH is a PUSCH that does not transmit uplink data but transmits UCI.

[0138] The base station and the UE agree that if multiple above-mentioned DCIs are received by the UE, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the PDSCHs scheduled by the multiple above-mentioned DCIs are all indicated to be transmitted in the slot n, then the UE transmits these HARQ-ACKs in one PUSCH. Wherein, the one PUSCH is determined in the slot n based on the resource of the PUSCH in the last DCI of the multiple above-mentioned DCIs (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH). For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in the slot n.

[0139] Example 2: The DCI does not schedule downlink data, but requires to provide HARQ-ACK of the DCI.

[0140] Base station side

[0141] In this example, the base station sends one DCI for the UE in the PDCCH, and contains one or more PUSCH resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) information in the DCI. The DCI does not schedule PDSCH, but the DCI is used to release SPS configuration, or is used to indicate SCell dormancy, or is used to indicate TCI, and is required to provide HARQ-ACK. It can also be described as: the DCI does not schedule PDSCH, but is required to provide HARQ-ACK. That is, the information of releasing SPS configuration and the PUSCH resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) information are contained in one DCI at the same time. Or, the information of indicating SCell dormancy and the PUSCH resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) information are contained in one DCI at the same time. Or, the TCI and the PUSCH resource (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH) information are contained in one DCI at the same time.

[0142] In one implementation, the DCI can also directly indicate or implicitly indicate a slot n, and the base station and the UE agree that the base station receives one PUSCH in the slot n, wherein the one PUSCH is determined in the slot n according to the resource of the PUSCH.

[0143] The HARQ-ACK of the DCI is carried in the PUSCH.

[0144] Since the DCI does not schedule a PDSCH, some fields in the DCI that are related to a PDSCH do not have an effect, and they can be used to indicate the above-mentioned PUSCH resource (e.g., PUSCH time domain resource and / or PUSCH frequency domain resource) information. The PUSCH is used to carry UCI (not to carry uplink data), or the PUSCH is a PUSCH that does not transmit uplink data but transmits UCI.

[0145] The base station and the UE agree that if multiple above-mentioned DCIs are transmitted from the base station, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the multiple above-mentioned DCIs are all indicated to be transmitted in slot n, then the base station expects to receive these HARQ-ACKs in one PUSCH. Wherein the one PUSCH is determined in slot n based on the PUSCH resource (here, the PUSCH resource includes the PUSCH time domain resource and / or the PUSCH frequency domain resource) in the last DCI of the multiple above-mentioned DCIs. For example, these HARQ-ACKs are concatenated and then encoded, and the transmission in the PUSCH is performed by the UE in slot n.

[0146] UE side

[0147] In this example, the UE receives a DCI in PDCCH, and the DCI contains one or more PUSCH resources (here, the PUSCH resources include PUSCH time domain resources and / or PUSCH frequency domain resources), and the DCI does not schedule PDSCH, but the DCI is used to indicate releasing SPS configuration, or is used to indicate SCell dormancy, or is used to indicate TCI, and the DCI is required to provide HARQ-ACK. It can also be that the DCI does not schedule PDSCH, but is required to provide HARQ-ACK. That is, the UE receives a DCI, and in the DCI, both the information of releasing SPS configuration and the PUSCH resources (here, the PUSCH resources include PUSCH time domain resources and / or PUSCH frequency domain resources) are contained. Or, the UE receives a DCI, and in the DCI, both the information of indicating SCell dormancy and the PUSCH resources (here, the PUSCH resources include PUSCH time domain resources and / or PUSCH frequency domain resources) are contained. Or, the UE receives a DCI, and in the DCI, both the information of TCI and the PUSCH resources (here, the PUSCH resources include PUSCH time domain resources and / or PUSCH frequency domain resources) are contained. In the above cases, the UE performs the following processing: the UE releases the corresponding SPS configuration, or dormancy of the corresponding SCell, or receives TCI according to the DCI, and carries the HARQ-ACK (i.e. ACK) corresponding to the DCI in the PUSCH obtained according to the PUSCH resources, and transmits the PUSCH.

[0148] In one implementation, the DCI can also directly indicate or implicitly indicate a slot n, and the base station and the UE agree that the UE transmits a PUSCH in the slot n, where the PUSCH is determined to be in the slot n according to the PUSCH resources.

[0149] The UE carries the HARQ-ACK of the DCI in the PUSCH.

[0150] Since the DCI does not schedule PDSCH, some fields related to PDSCH in the DCI do not work, and they can be used as the information of the PUSCH resources (e.g. PUSCH time domain resources and / or PUSCH frequency domain resources) described above. The PUSCH is used to carry UCI (not to carry uplink data), or the PUSCH is a PUSCH that does not transmit uplink data but transmits UCI.

[0151] The base station and the UE can agree that if multiple DCIs described above are received by the UE, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the multiple DCIs described above are all indicated to be transmitted in slot n, then the UE transmits these HARQ-ACKs in one PUSCH. The one PUSCH is determined in slot n based on the resource of the PUSCH in the last DCI of the multiple DCIs described above (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH). For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in slot n.

[0152] Example 3: Example 3 is a mixture of Example 1 and Example 2 below, that is, in Example 3, there are multiple DCIs, some of the multiple DCIs schedule PDSCH, and some of the multiple DCIs do not schedule PDSCH.

[0153] Base station side

[0154] In this example, the base station and the UE can agree that if multiple DCIs described above are transmitted from the base station, and the multiple DCIs all indicate the same slot n, then the base station receives the HARQ-ACKs triggered by the multiple DCIs in one PUSCH in slot n. The one PUSCH is determined in slot n based on the resource of the PUSCH in the last DCI of the multiple DCIs described above (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH). The multiple DCIs and the HARQ-ACKs triggered by the multiple DCIs include: some DCIs are used to schedule PDSCH, and the HARQ-ACK of the PDSCH is required to be received in slot n; some DCIs do not schedule PDSCH, but the HARQ-ACK of the DCI is required to be received in slot n. For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in slot n.

[0155] UE side

[0156] In this example, the base station and the UE agree that if multiple above-mentioned DCIs are received from the base station, and the multiple DCIs all indicate the same slot n, then the UE transmits the HARQ-ACKs triggered by the multiple DCIs in one PUSCH in slot n. Wherein, the one PUSCH is determined in slot n based on the resource of the PUSCH in the last DCI of the multiple DCIs (here, the resource of the PUSCH includes the time domain resource of the PUSCH and / or the frequency domain resource of the PUSCH). Wherein, the multiple DCIs and the multiple HARQ-ACKs triggered by the multiple DCIs include: some DCIs are used to schedule PDSCHs, then the HARQ-ACKs of the PDSCHs are required to be received in slot n, and some DCIs do not schedule PDSCHs, but the HARQ-ACKs of the DCIs are required to be received in slot n. For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in slot n.

[0157] Implementation manner two: DCI indicates one target PUSCH

[0158] In this implementation manner, a PUSCH resource indication field is included in the DCI, and the PUSCH resource indication field is used to indicate one PUSCH resource from a PUSCH resource set, i.e., the PUSCH resource indication field is used to indicate one PUSCH resource in a PUSCH resource set, and the PUSCH resource is used to transmit the target PUSCH.

[0159] In one implementation manner, the implementation manner can include the following three examples, which are described below respectively.

[0160] Example 1, the DCI schedules a PDSCH, and requires to provide the HARQ-ACK of the PDSCH, and does not require to provide the HARQ-ACK of the DCI.

[0161] Base station side

[0162] In this example, the base station configures the UE with at least one PUSCH resource set, and one PUSCH resource set includes one or more PUSCH resources for carrying UCI. At most Q PUSCH resource sets are configured. Q is a positive integer greater than or equal to 1. The value of Q can be configured by the base station, or the value of Q is predefined between the base station and the UE.

[0163] The UCI includes at least one of: HARQ-ACK, Scheduling Request (SR), and Channel State Information (CSI). The CSI includes at least one of CSI-1 and CSI-2. The number of bits of the CSI-2 is determined based on related information in the CSI-1. The set of PUSCH resources is used for transmission of the UCI.

[0164] The base station transmits a DCI for the UE via a PDCCH, and the DCI includes time-frequency resources of one or more PDSCHs, and the DCI includes one or more PUSCH resource indication information. That is, the DCI includes time-domain resources of a PDSCH, frequency-domain resources of the PDSCH, and the PUSCH resource indication information. That is, the DCI scheduling the PDSCH includes time-domain resources and frequency-domain resources of the PDSCH, and further includes the PUSCH resource indication information for determining a PUSCH. The PUSCH resource indication information is used to indicate a PUSCH from a determined set of PUSCH resources, and the determined set of PUSCH resources is one of the at least one set of configured PUSCH resources. The PUSCH is used to carry UCI (not used to carry uplink data), or the PUSCH is a PUSCH without uplink data but with UCI.

[0165] In an implementation, the DCI can directly or implicitly indicate a slot n, and the base station and the UE agree that the base station receives a PUSCH in the slot n, and the PUSCH is determined from a determined set of PUSCH resources in the slot n according to the PUSCH resource indication information.

[0166] In an implementation, the DCI can directly or implicitly indicate a slot m, and the base station transmits a PDSCH in the slot m, and the PDSCH is determined in the slot m according to the time-frequency resources of the PDSCH.

[0167] The HARQ-ACK of the PDSCH is carried in the PUSCH.

[0168] Generally, the slot m is earlier than the slot n.

[0169] In one implementation, the base station and the UE agree that if multiple DCIs described above are transmitted from the base station, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the PDSCHs scheduled by the multiple DCIs described above are all indicated to be transmitted in slot n, then the base station receives these HARQ-ACKs in one PUSCH in slot n. Wherein, the one PUSCH is determined from a determined PUSCH resource set, and is determined based on the PUSCH resource indication information in the last DCI of the multiple DCIs described above. The method of determining a PUSCH resource set is described later.

[0170] The base station and the UE agree that the PUSCH resource indication information can determine a PUSCH from a determined PUSCH resource set. For example, the PUSCH resource indication information can be an index information. Assume that a PUSCH resource set contains 4 PUSCHs. The PUSCH resource indication information can be 2 bits, which is used to indicate a PUSCH from the PUSCH resource set containing 4 PUSCHs based on the order of the PUSCH in the PUSCH resource set.

[0171] UE side

[0172] In this example, the UE is configured one or more PUSCH resource sets, which contains one or more PUSCH resources for carrying UCI. At most Q PUSCH resource sets are configured. Q is a positive integer greater than or equal to 1. The value of Q can be configured by the base station, or the value of Q is predefined between the base station and the UE. Wherein, the UCI contains at least one of the following: HARQ-ACK, SR and CSI. The CSI includes at least one of CSI-1 and CSI-2. Wherein, the number of bits of CSI-2 is determined based on the related information in CSI-1. The PUSCH resource set is used to transmit UCI.

[0173] A UE receives a DCI in a PDCCH, and the DCI contains time-frequency resources of one or more PDSCHs, and the DCI also contains one or more PUSCH resource indication information. That is, a DCI contains PDSCH time domain resource, PDSCH frequency domain resource, and PUSCH resource indication information. That is, a DCI that schedules a PDSCH contains PDSCH time domain resource and frequency domain resource, and also contains PUSCH resource indication information that is used to determine a PUSCH. The PUSCH is used to carry UCI (not used to carry uplink data), or the PUSCH is a PUSCH that does not carry uplink data but carries UCI.

[0174] In an implementation, the DCI also directly indicates or implicitly indicates a slot n, and the base station and the UE agree that the UE transmits a PUSCH in slot n, where the PUSCH is determined from a determined PUSCH resource set in slot n according to the PUSCH resource indication information.

[0175] In an implementation, the DCI also directly indicates or implicitly indicates a slot m, and the UE receives a PDSCH in slot m, where the PDSCH is determined in slot m according to the time-frequency resources of the PDSCH.

[0176] The HARQ-ACK of the PDSCH is carried in the PUSCH.

[0177] Generally, slot m is earlier than slot n.

[0178] In an implementation, the base station and the UE agree that, if multiple DCIs described above are received by the UE, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the PDSCHs scheduled by the multiple DCIs described above are all indicated to be transmitted in slot n, then the UE transmits these HARQ-ACKs in a PUSCH in slot n. Where the one PUSCH is determined from a determined PUSCH resource set, and is determined based on the PUSCH resource indication information in the last DCI of the multiple DCIs described above. The method of determining a PUSCH resource set is described later.

[0179] The base station and the UE agree that the PUSCH resource indication information can determine a PUSCH from a determined set of PUSCH resources. For example, the PUSCH resource indication information can be an index information. Assume that a set of PUSCH resources contains 4 PUSCHs. The PUSCH resource indication information can be 2 bits, which is used to indicate a PUSCH from the set of PUSCH resources containing 4 PUSCHs based on the order of the PUSCHs in the set of PUSCH resources.

[0180] Example 2, the DCI does not schedule downlink data, but requires to provide HARQ-ACK for the DCI.

[0181] The base station side

[0182] In this embodiment, the base station configures a set of PUSCH resources for the UE, and a set of PUSCH resources contains one or more PUSCH resources for carrying UCI. At most Q sets of PUSCH resources are configured. Q is a positive integer greater than or equal to 1. The value of Q can be configured by the base station, or the value of Q is predefined between the base station and the UE. The UCI contains at least one of the following: HARQ-ACK, SR and CSI. The CSI includes at least one of CSI-1 and CSI-2. The number of bits of CSI-2 is determined based on the related information in CSI-1. The set of PUSCH resources is used to transmit the UCI.

[0183] The base station sends a DCI for the UE in the PDCCH, and the DCI contains one or more PUSCH resource indication information. The DCI does not schedule PDSCH, but the DCI is used to release SPS configuration, or is used to indicate SCell dormancy, or is used to indicate TCI, and is required to provide HARQ-ACK. It can also be described as: the DCI does not schedule PDSCH, but is required to provide HARQ-ACK. That is, the DCI contains the information of releasing SPS configuration and the PUSCH resource indication information at the same time. Or, the DCI contains the information of indicating SCell dormancy and the PUSCH resource indication information at the same time. Or, the DCI contains the TCI information and the PUSCH resource indication information at the same time. The PUSCH resource indication information is used to determine a PUSCH from a determined set of PUSCH resources.

[0184] In one implementation, the DCI should also directly indicate or implicitly indicate a slot n, and the base station and the UE agree that the base station receives a PUSCH in the slot n, wherein the PUSCH is determined from the determined set of PUSCH resources in the slot n according to the PUSCH resource indication information.

[0185] In one implementation, the base station and the UE agree that the base station considers the UE will release the corresponding SPS configuration or dormancy the corresponding SCell according to the corresponding indication in the DCI.

[0186] The HARQ-ACK of the DCI is carried in the PUSCH.

[0187] Since the DCI does not schedule PDSCH, some fields in the DCI related to PDSCH do not have effect, which can be used as the PUSCH resource indication information. The PUSCH is used to carry UCI (not carrying uplink data), or the PUSCH is a PUSCH without transmitting uplink data but transmitting UCI.

[0188] In one implementation, the base station and the UE agree that if multiple DCIs are transmitted from the base station, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the multiple DCIs are all indicated to be received in slot n, then the base station receives the HARQ-ACKs in a PUSCH in slot n. Wherein, the one PUSCH is determined from a determined PUSCH resource set, and is determined based on the PUSCH resource indication information in the last DCI of the multiple DCIs. The method of determining a PUSCH resource set is described later.

[0189] The base station and the UE agree that the PUSCH resource indication information can determine a PUSCH from a determined PUSCH resource set. For example, the PUSCH resource indication information can be an index information. Assuming that a PUSCH resource set contains 4 PUSCHs. The PUSCH resource indication information can be 2 bits, which is used to indicate a PUSCH from the PUSCH resource set containing 4 PUSCHs based on the order of the PUSCH in the PUSCH resource set.

[0190] UE side

[0191] In the example, the UE is configured with a PUSCH resource set, which contains one or more PUSCH resources for carrying UCI. At most Q PUSCH resource sets are configured. Q is a positive integer greater than or equal to 1. The value of Q can be configured by the base station, or the value of Q is predefined between the base station and the UE. Wherein, the UCI contains at least one of the following: HARQ-ACK, SR and CSI. The CSI includes at least one of CSI-1 and CSI-2. Wherein, the number of bits of CSI-2 is determined based on the related information in CSI-1. The PUSCH resource set is used to transmit UCI.

[0192] A UE receives a DCI in a PDCCH, and the DCI contains one or more PUSCH resource indication information. The DCI does not schedule a PDSCH, but the DCI is used to release a SPS configuration, or is used to indicate a SCell dormancy, or is used to indicate a TCI, and is required to provide a HARQ-ACK. It can also be described as: the DCI does not schedule a PDSCH, but is required to provide a HARQ-ACK. That is, the DCI contains both the information of releasing a SPS configuration and the PUSCH resource indication information in one DCI. Or, the DCI contains both the information of indicating a SCell dormancy and the PUSCH resource indication information in one DCI. Or, the DCI contains both the information of indicating a TCI and the PUSCH resource indication information in one DCI. The PUSCH resource indication information is used to determine a PUSCH from a determined PUSCH resource set.

[0193] In an implementation, the DCI should also directly or implicitly indicate a slot n, and the base station and the UE agree that the UE transmits a PUSCH in the slot n, where the PUSCH is determined from the determined PUSCH resource set in the slot n according to the PUSCH resource indication information.

[0194] In an implementation, the base station and the UE agree that the UE releases a corresponding SPS configuration or dormancy corresponding SCell according to the corresponding indication in the DCI.

[0195] The HARQ-ACK of the DCI is carried in the PUSCH.

[0196] Since the DCI does not schedule a PDSCH, some fields related to PDSCH in the DCI do not work, and they can be used as the PUSCH resource indication information described above. The PUSCH is used to carry UCI (not to carry uplink data), or the PUSCH is a PUSCH that does not transmit uplink data but transmits UCI.

[0197] In an implementation, the base station and the UE agree that if multiple DCIs described above are received by the UE, and the multiple DCIs all indicate the same slot n, that is, the HARQ-ACKs of the multiple DCIs described above are all indicated to be received in the slot n, then the UE transmits these HARQ-ACKs in a PUSCH in the slot n. Wherein, the one PUSCH is determined from a determined PUSCH resource set, and is determined based on the PUSCH resource indication information in the last DCI of the multiple DCIs described above. The method of determining a PUSCH resource set is described in detail later.

[0198] The base station and the UE agree that the PUSCH resource indication information can determine a PUSCH from a determined set of PUSCH resources. For example, the PUSCH resource indication information can be an index information. Assume that a set of PUSCH resources contains 4 PUSCHs. The PUSCH resource indication information can be 2 bits, which is used to indicate a PUSCH from the set of PUSCH resources containing 4 PUSCHs based on the order of the PUSCHs in the set of PUSCH resources.

[0199] Example 3: Example 3 is a mix of Example 1 and Example 2 below implementation, that is, in Example 3, there are multiple DCIs, some of the multiple DCIs schedule PDSCH, and some of the multiple DCIs do not schedule PDSCH.

[0200] Base station side

[0201] In this example, the base station and the UE agree that if multiple above-mentioned DCIs are transmitted from the base station, and the multiple DCIs all indicate the same slot n, then the base station receives the HARQ-ACKs triggered by the multiple DCIs in one PUSCH in slot n. Wherein, the one PUSCH is determined in slot n based on the PUSCH resource indication information in the last DCI of the multiple above-mentioned DCIs. Wherein, the multiple DCIs and the HARQ-ACKs triggered by the multiple DCIs include: some DCIs are used to schedule PDSCH, then the HARQ-ACK of the PDSCH is required to be received in slot n, some DCIs do not schedule PDSCH, but the HARQ-ACK of the DCI is required to be received in slot n. For example, these HARQ-ACKs are concatenated and encoded, and then transmitted in the PUSCH by the UE in slot n.

[0202] UE side

[0203] In this example, the base station and the UE agree that if multiple above-mentioned DCIs are received from the base station, and the multiple DCIs all indicate the same slot n, then the UE transmits the HARQ-ACKs triggered by the multiple DCIs in one PUSCH in slot n. Wherein, the one PUSCH is determined in slot n based on the resource indication information of the PUSCH in the last DCI of the multiple above-mentioned DCIs. Wherein, the multiple DCIs and the multiple DCIs triggered HARQ-ACKs include: some DCIs are used to schedule PDSCH, then the HARQ-ACK of the PDSCH is required to be received in slot n, some DCIs do not schedule PDSCH, but the HARQ-ACK of the DCI is required to be received in slot n. For example, these HARQ-ACKs are concatenated and then encoded, and then transmitted in the PUSCH by the UE in slot n.

[0204] In the embodiments of the present application, the base station and the UE can agree that the above-mentioned implementation mode one and implementation mode two cannot be configured for the same UE at the same time. That is, the above-mentioned implementation mode one and implementation mode two cannot be configured for one UE at the same time.

[0205] In one implementation mode, for the PUSCH resource set in implementation mode two, the base station and the UE agree that the index ID of the maximum Q PUSCH resource sets is configured from 0 to Q-1. The base station configures the index ID of different PUSCH resource sets in ascending order according to the number of bits of UCI associated with each PUSCH resource set.

[0206] In one implementation mode, the base station and the UE agree to configure the number of UCI bits associated with the UCI resource set according to the following rules:

[0207] If multiple PUSCH resource sets are configured, the PUSCH resource set with index ID 0 is configured to be associated with 1-2 bits of UCI, and the PUSCH resource set with index ID greater than 0 is configured to be associated with more than 2 bits of UCI.

[0208] For example, the base station configures 4 PUSCH resource sets for the UE to carry UCI. The first UCI resource set is a PUCCH resource set, the index ID is configured as 0, and is configured to carry 1~2 bits of UCI. The second UCI resource set is a PUSCH resource set, the index ID is configured as 1, and is configured to carry 3~20 bits of UCI. The third UCI resource set is a PUSCH resource set, the index ID is configured as 2, and is configured to carry 21~60 bits of UCI. The fourth UCI resource set is a PUSCH resource set, the index ID is configured as 3, and is configured to carry 61~M bits of UCI. M is the maximum number of UCI bits that can be carried using the PUSCH resource set.

[0209] For example, the base station configures 4 PUSCH resource sets for the UE to carry UCI. The first UCI resource set is a PUCCH resource set, the index ID is configured as 0, and is configured to carry 1~2 bits of UCI. The second UCI resource set is a PUSCH resource set, the index ID is configured as 1, and is configured to carry 3~20 bits of UCI. The third UCI resource set is a PUSCH resource set, the index ID is configured as 2, and is configured to carry 21~60 bits of UCI. The fourth UCI resource set is a PUSCH resource set, the index ID is configured as 3, and is configured to carry 61~M bits of UCI. M is the maximum number of UCI bits that can be carried using the PUSCH resource set.

[0210] In one implementation, the base station and the UE agree that the UE determines a PUSCH resource set according to the number of bits of UCI to be transmitted. For example, assume the UCI resource sets are configured as in the example above. If the UE wants to transmit 2 bits of HARQ-ACK, the UE determines the first PUSCH resource set to transmit the 2 bits of HARQ-ACK according to the number of bits of HARQ-ACK, which is 2. If the UE wants to transmit 10 bits of UCI (including at least one of HARQ-ACK, SR, and CSI), the UE determines the second PUSCH resource set to transmit the 10 bits of HARQ-ACK according to the number of bits of UCI, which is 10.

[0211] For the transmission of HARQ-ACKs for SPS PDSCH, the base station independently configures up to Q sets of PUSCH resources for a UE, and each set of PUSCH resources is associated with a corresponding range of UCI bits. In one implementation, each set of PUSCH resources contains only one PUSCH for carrying UCI.

[0212] For the up to Q sets of PUSCH resources, the first set of PUSCH resources, i.e., the set of PUSCH resources with index 0, can be configured to contain a maximum number of PUSCH resources that is larger than the number of PUSCH resources in the other sets of PUSCH resources (i.e., the second and subsequent sets of PUSCH resources). The maximum number of PUSCH resources in the first set of PUSCH resources is up to twice or four times the maximum number of PUSCH resources in the other sets of PUSCH resources. The maximum number of PUSCH resources in the other sets of PUSCH resources should be kept equal.

[0213] A PUSCH resource in a set of PUSCH resources can be configured based on resource blocks (RBs) or resource elements (REs). A PUSCH is configured to contain at least one of the following parameters: a starting symbol, a number of consecutive symbols, a PUSCH frequency hopping enable parameter, a number of repetitions, a PUSCH format, a starting RB, a starting RB for a second hop, a number of RBs, an orthogonal covering code (OCC) code word length, an OCC index, a code rate information, a MCS level, a modulation information, a MCS table information, a DMRS related information, a betaoffset information, a starting RE group, a number of RE groups, a starting RE group for a second hop.

[0214] The starting RB is used to determine the starting RB of the PUSCH.

[0215] The number of RBs is used to determine the number of consecutive RBs starting from the indicated starting RB.

[0216] The starting RE group is used to determine the starting RE of the PUSCH.

[0217] The number of RE groups is used to determine the number of consecutive RE groups starting from the indicated starting RE group.

[0218] The frequency hopping enable parameter is used to determine whether the PUSCH frequency hops.

[0219] The starting RE group for a second hop is used to determine the starting RE group for a second hop, and the number of RE groups for the second hop is also determined based on the number of RE groups.

[0220] Second frequency hopping start RB is used to determine the start RB of the second frequency hopping, and the number of RBs corresponding to the second frequency hopping is also determined based on the number of RBs.

[0221] OCC code word length is used to determine the information corresponding to the PUSCH, that is, the OCC code word used when the PUSCH is transmitted in the allocated RE group, so that the PUSCHs of different UEs carrying UCI can be transmitted in the same RE group.

[0222] OCC index is used to determine which group of OCC code words is used. For example, an OCC code word with a length of 2 contains 2 groups of OCC code words, and the OCC index describes which group of the 2 groups of OCC code words is used. For example, an OCC code word with a length of 4 contains 4 groups of OCC code words, and the OCC index describes which group of the 4 groups of OCC code words is used.

[0223] Starting symbol is used to determine the starting symbol of the PUSCH.

[0224] Symbol number is used to determine the number of consecutive symbols of the PUSCH starting from the determined starting symbol.

[0225] DMRS configuration information is used to determine which symbols of the symbols of the PUSCH are DMRS symbols, or the type of DMRS.

[0226] The number of repetitions is used to determine the number of repetitions of the PUSCH.

[0227] PUSCH format is used to determine the transmission mode of the PUSCH.

[0228] Code rate information is used to determine the code rate used by the PUSCH resource.

[0229] MCS level is used to determine the MCS used by the PUSCH.

[0230] Modulation information is used to determine the modulation mode of the PUSCH.

[0231] MCS table information is used to determine which MCS table the MCS level of the PUSCH comes from.

[0232] Beta offset information is used to determine the number of resources in the PUSCH carrying UCI.

[0233] Also, in a case that one PUSCH resource is configured to contain at least one of the following parameters, and different PUSCH resources in the set of PUSCH resources are consistent: starting symbol, number of consecutive symbols, PUSCH frequency hopping enabling parameter, number of repetitions, PUSCH format, starting RB, starting RB of the second frequency hopping, number of RBs, OCC code word length, OCC index, code rate information, MCS level, modulation information, MCS table information, DMRS related information, betaoffset information, starting RE group, number of RE groups, starting RE group of the second frequency hopping.

[0234] Through the technical scheme provided by the embodiments of the present application, the HARQ-ACK triggered by the DCI format of the DCI scheduling the PDSCH can be carried in the PUSCH triggered by the DCI, so that the problem of uplink channel multiplexing caused by the overlap of the PUSCH and the PUCCH in the time domain can be avoided.

[0235] As shown in FIG. 5, the embodiments of the present application further provide a communication device 500, which comprises a processor 5301 and a memory 502, and the memory 5302 stores programs or instructions executable on the processor 501. For example, when the communication device 500 is a terminal, the programs or instructions are executed by the processor 501 to implement each step of the above-mentioned uplink control information sending method embodiments, and the same technical effects can be achieved. When the communication device 500 is a network side device, for example, a base station, the programs or instructions are executed by the processor 501 to implement each step of the above-mentioned uplink control information receiving method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.

[0236] As shown in FIG. 6, the embodiments of the present application further provide a terminal, which comprises a transceiver 630, a memory 620, a processor 600, and programs stored in the memory and executable on the processor. When the processor executes the programs, the following steps are implemented:

[0237] receiving a DCI of a DCI format scheduling a PDSCH, wherein the DCI triggers a target PUSCH; and transmitting the target PUSCH in a target slot, wherein HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0238] In FIG. 6, the bus architecture can include any number of interconnected buses and bridges, specifically, various circuitry of the one or more processors represented by the processor 600 and the memory represented by the memory 620 are linked together. The bus architecture can also link various other circuitry such as peripheral devices, voltage regulators, and power management circuitry, which are well known in the art, and thus, the embodiments of the present application will not be further described. The bus interface provides an interface. The transceiver 610 can be a plurality of elements, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The user interface 630 can also be an interface capable of externally connecting the required devices for different user equipment, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0239] The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1100 in performing operations.

[0240] In one implementation, the processor 1100 is further configured to read a program in the memory 1120, and perform the following steps:

[0241] receiving a DCI of a DCI format for scheduling a PDSCH, wherein the DCI triggers a target PUSCH; and transmitting the target PUSCH in a target slot, wherein HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0242] Those skilled in the art can understand that the structure shown in FIG. 6 does not constitute a limitation on the terminal, and can include more or fewer components than the illustration, or combine certain components, or use different component arrangements.

[0243] As shown in FIG. 7, the embodiments of the present application also provide a base station, which includes a memory 720, a processor 700, a transceiver 710, a bus interface, and a program stored in the memory 720 and executable on the processor 700, the processor 700 is configured to read the program in the memory 720, and perform the following processes:

[0244] receiving a DCI of a DCI format for scheduling a PDSCH, wherein the DCI triggers a target PUSCH; and transmitting the target PUSCH in a target slot, wherein HARQ-ACK triggered by the DCI is carried on the target PUSCH.

[0245] In Figure 7, the bus architecture can include any number of interconnected buses and bridges, specifically, various circuit links between the processor(s) 700 and the memory represented by the memory 720. The bus architecture can also link various other circuits such as peripheral devices, voltage stabilizers, and power management circuits, which are well known in the art, and thus, are not further described in the embodiments of the present application. The bus interface provides an interface. The transceiver 710 can be a plurality of elements, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 in performing operations.

[0246] Those skilled in the art can understand that the structure shown in Figure 7 does not constitute a limitation on the base station, and can include more or fewer components than illustrated, or combine certain components, or adopt a different arrangement of components.

[0247] In an exemplary embodiment, a readable storage medium is also provided, in which a program or instructions are stored, the storage program or instructions are executed by a processor to implement all or part of the steps of the above-mentioned uplink control information receiving method, or implement all or part of the steps of the above-mentioned uplink control information sending method. For example, the readable storage medium can be a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a read-only compact disc (Compact Disc Read-Only Memory, CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0248] In an exemplary embodiment, a computer program product is also provided, the computer program product includes a computer program stored on a non-transitory readable storage medium, the computer program includes program instructions, when the program instructions are executed by a computer, the computer executes all or part of the steps of the above-mentioned uplink control information receiving method, or executes all or part of the steps of the above-mentioned uplink control information sending method.

[0249] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0250] It is to be understood that the application is not limited to the precise construction already described above and shown in the drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application should only be limited by the claims appended hereto.

Claims

1. A method for receiving uplink control information (UCI), wherein, include: The base station sends a DCI in DCI format for scheduling the Physical Downlink Shared Channel (PDSCH), wherein the DCI triggers a Target Physical Uplink Shared Channel (PUSCH). The base station receives the target PUSCH from the target time slot, wherein the DCI-triggered Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) is carried on the target PUSCH.

2. The method according to claim 1, wherein, The DCI also schedules a PDSCH; In response to the DCI, a PDSCH is also scheduled, and the HARQ-ACK triggered by the DCI is the HARQ-ACK of the PDSCH.

3. The method according to claim 1, wherein, The DCI triggers a target PUSCH, including one of the following: The DCI includes a PUSCH time-domain resource field and / or a PUSCH frequency-domain resource field for allocating PUSCH resources, wherein the base station allocates a PUSCH resource through the PUSCH time-domain resource field and / or the PUSCH frequency-domain resource field to transmit the target PUSCH. The DCI includes a PUSCH resource indication field, and the PUSCH resource indication field is used to indicate a PUSCH resource from a set of PUSCH resources, wherein the base station indicates a PUSCH resource from a determined set of PUSCH resources to transmit the target PUSCH through the PUSCH resource indication field.

4. The method according to any one of claims 1 to 3, wherein, The method further includes: The base station configures at least one PUSCH resource set for the terminal. Each PUSCH resource set is associated with a range of uplink control information (UCI) bits. The determined PUSCH resource set is determined from the at least one PUSCH resource set based on the number of UCI bits. A PUSCH resource set contains at least one PUSCH resource for UCI, and the PUSCH resource includes at least one of the following information: start symbol, number of consecutive symbols, PUSCH hopping enable parameters, number of repetitions, PUSCH format, start resource block (RB), start RB for the second hopping, number of RBs, codeword length of orthogonal convolutional code (OCC), OCC index, code rate information, modulation and coding scheme (MCS) level, modulation information, MCS table information, demodulation reference signal (DMRS) related information, beta offset information, start resource unit (RE) group, number of RE groups, and start RE group for the second hopping.

5. The method according to any one of claims 1 to 4, wherein, The DCI also includes a target timeslot indication field, which is used to indicate a timeslot as the target timeslot, wherein the HARQ-ACK is transmitted in the target timeslot.

6. The method according to claim 5, wherein, The target time slot indication field indicates a value n, where n is an integer greater than or equal to 0; In response to the DCI scheduling a PDSCH, the target time slot is determined by one of the following: The target time slot is the time slot after the time slot where the PDSCH is located, and n time slots apart from the last time slot where the PDSCH is located; The target time slot is a time slot that is n time slots apart from the first time slot available for uplink transmission after the time slot where the PDSCH is located. The time slot available for uplink transmission includes at least one of flexible time slots and uplink time slots.

7. The method according to claim 5, wherein, The target time slot indication field indicates a value n, where n is an integer greater than or equal to 0; In response to the DCI not scheduling a PDSCH, the target time slot is determined by one of the following: The target time slot is the time slot after the time slot where the DCI is located, and n time slots apart from the last time slot where the DCI is located; The target time slot is a time slot n time slots apart from the first time slot available for uplink transmission after the time slot where the DCI is located. The time slot available for uplink transmission includes at least one of flexible time slots and uplink time slots.

8. The method according to claim 1, wherein, The DCI did not schedule a PDSCH; In response to the DCI not scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the DCI.

9. The method according to claim 8, wherein, The DCI is used for at least one of the following: Instruct the secondary cell to go into hibernation and not schedule downlink data; Indicates that the transmission configuration indicates a TCI update; Indicates the release of the semi-persistent scheduling configuration.

10. The method according to any one of claims 1 to 9, wherein, There are multiple DCIs, and the multiple DCIs indicate the same target time slot; the HARQ-ACK triggered by the multiple DCIs is carried on the target PUSCH.

11. The method according to claim 10, wherein, The target PUSCH is determined by one of the following: Determined based on the PUSCH resource indicator field in the last of the multiple DCIs; It is determined based on the PUSCH time-domain resource field and / or PUSCH frequency-domain resource field in the last of the multiple DCIs.

12. The method according to claim 10, wherein, The plurality of said DCIs includes at least one of the following: DCI for scheduling PDSCH; A DCI that is not scheduled for PDSCH but is instructed to transmit HARQ-ACK information in the target time slot.

13. A method for transmitting uplink control information, wherein, include: The terminal receives a DCI in DCI format for scheduling PDSCH, wherein the DCI triggers a target PUSCH; The terminal sends the target PUSCH in a target time slot, wherein the DCI-triggered HARQ-ACK is carried on the target PUSCH.

14. The method according to claim 13, wherein, The DCI also schedules a PDSCH; in response to the DCI scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the PDSCH.

15. The method according to claim 13, wherein, The DCI triggers a target PUSCH, including one of the following: The DCI includes a PUSCH time-domain resource field and / or a PUSCH frequency-domain resource field for allocating PUSCH resources, wherein the terminal determines a PUSCH resource through the PUSCH time-domain resource field and / or the PUSCH frequency-domain resource field to transmit the target PUSCH. The DCI includes a PUSCH resource indication field, and the PUSCH resource indication field is used to indicate a PUSCH resource from a set of PUSCH resources, wherein the terminal determines a PUSCH resource from the determined set of PUSCH resources through the PUSCH resource indication field to transmit the target PUSCH.

16. The method according to any one of claims 13 to 15, wherein, The method further includes: the terminal is configured with at least one PUSCH resource set, and each PUSCH resource set is associated with a range of bits of uplink control information (UCI); It also includes: the terminal determining a PUSCH resource set from the at least one PUSCH resource set based on the number of bits of UCI.

17. The method according to claim 16, wherein, A PUSCH resource set contains at least one PUSCH resource for UCI, and the PUSCH resource includes at least one of the following information: start symbol, number of consecutive symbols, PUSCH hopping enable parameters, number of repetitions, PUSCH format, start RB, start resource block RB for the second hopping, number of RBs, codeword length of orthogonal convolutional code (OCC), OCC index, code rate information, modulation and coding scheme (MCS) level, modulation information, MCS table information, demodulation reference signal (DMRS) related information, beta offset information, start resource unit (RE) group, number of RE groups, and start RE group for the second hopping.

18. The method according to any one of claims 13 to 15, wherein, The DCI also includes a target timeslot indication field, which is used to indicate a timeslot as the target timeslot, wherein the HARQ-ACK is transmitted in the target timeslot.

19. The method according to claim 18, wherein, The target time slot indication field indicates a value n, where n is an integer greater than or equal to 0; In response to the DCI scheduling a PDSCH, the target time slot is determined to include one of the following: The target time slot is the time slot after the time slot where the PDSCH is located, and n time slots apart from the last time slot where the PDSCH is located; The target time slot is a time slot that is n time slots apart from the first time slot available for uplink transmission after the time slot where the PDSCH is located. The time slot available for uplink transmission includes at least one of flexible time slots and uplink time slots.

20. The method according to claim 18, wherein, The target time slot indication field indicates a value n, where n is an integer greater than or equal to 0; In response to the DCI not scheduling a PDSCH, the target time slot is determined by one of the following: The target time slot is the time slot after the time slot where the DCI is located, and n time slots apart from the last time slot where the DCI is located; The target time slot is a time slot n time slots apart from the first time slot available for uplink transmission after the time slot where the DCI is located. The time slot available for uplink transmission includes at least one of flexible time slots and uplink time slots.

21. The method according to claim 13, wherein, The DCI did not schedule a PDSCH; in response to the DCI not scheduling a PDSCH, the HARQ-ACK triggered by the DCI is the HARQ-ACK of the DCI.

22. The method according to claim 21, wherein, The DCI is used for at least one of the following: Instruct the secondary cell to go into hibernation and not schedule downlink data; Indicates that the transmission configuration indicates a TCI update; Indicates the release of the semi-persistent scheduling configuration.

23. The method according to any one of claims 13 to 22, wherein, The DCI is multiple, and the multiple DCIs indicate the same target time slot; it also includes: The terminal carries multiple DCI-triggered HARQ-ACKs on the target PUSCH.

24. The method according to claim 23, wherein, The target PUSCH is determined by one of the following: Determined based on the PUSCH resource indicator field in the last of the multiple DCIs; It is determined based on the PUSCH time-domain resource field and / or PUSCH frequency-domain resource field in the last of the multiple DCIs.

25. The method according to claim 23, wherein, The plurality of said DCIs includes at least one of the following: DCI for scheduling PDSCH; A DCI that is not scheduled for PDSCH but is instructed to transmit HARQ-ACK information in the target time slot.

26. A communication device, wherein, The communication device includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the uplink control information receiving method as described in any one of claims 1 to 14, or to implement the steps of the uplink control information transmitting method as described in any one of claims 15 to 25.

27. A readable storage medium, wherein, A program or instructions are stored on the readable storage medium, which, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 25.

28. A computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the steps of the method as described in any one of claims 1 to 25.

Images