Method, apparatus and non-transitory computer readable medium for wireless communication

Abstract

The invention relates to a method, an apparatus and a non-transitory computer readable medium for wireless communication. The method comprises: a network node configuring one or more physical uplink control channel (PUCCH) resource sets for a terminal, the PUCCH resource sets comprising N PUCCH resources, the N PUCCH resources comprising a PUCCH resource from a first frequency domain resource and a PUCCH resource from a second frequency domain resource, the first frequency domain resource comprising a first carrier or a first partial bandwidth (BWP), and the second frequency domain resource comprising a second carrier or a second partial bandwidth (BWP); the second frequency domain resource comprises a second carrier or a second BWP; and transmitting, by the network node to the terminal, downlink control information (DCI) comprising an indicator of the PUCCH resource, in which: in the event that the PUCCH resource indicated by the indicator is from the first frequency domain resource, the terminal is to transmit a PUCCH transmission using the PUCCH resource on the first frequency domain resource; and in the case that the PUCCH resource indicated by the indicator is from the second frequency domain resource, the terminal will use the PUCCH resource on the second frequency domain resource to transmit the PUCCH transmission.

Description

[0001] This application is a divisional application of Chinese patent application No. 202080106279.5, filed on October 15, 2020, entitled "Determining a carrier for control channel transmission". Technical Field

[0002] This patent application generally pertains to wireless communication. Background Technology

[0003] Mobile communication technology is propelling the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in mobile communications have led to greater demands for capacity and connectivity. Other factors, such as energy consumption, equipment cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Various technologies, including new methods for providing higher quality of service, are currently under discussion. Summary of the Invention

[0004] This application discloses methods, systems, and apparatuses related to digital wireless communication, and more specifically, discloses methods, systems, and apparatuses related to techniques for determining whether to switch the carrier of the control channel transmission from a terminal to a network node.

[0005] In one exemplary aspect, a method for wireless communication is disclosed. The method includes: a network node sending a carrier indication message to a terminal, the carrier indication message indicating a carrier via a predefined bit field in a control indication field. The method may further include: the network node receiving a second message from the terminal via the carrier indicated in the carrier indication message.

[0006] In another exemplary aspect, a method for wireless communication includes: receiving a carrier indication message from a network node by a terminal, the carrier indication message indicating a carrier via a predefined bit field in a control indication field. The method may further include: sending a second message from the terminal to the network node via the carrier indicated in the carrier indication message.

[0007] In another exemplary aspect, a wireless communication device including a processor is disclosed. The processor is configured to implement the methods described herein.

[0008] In yet another exemplary aspect, the various techniques described herein may be embodied in processor-executable code and stored on a computer-readable program medium.

[0009] Details of one or more embodiments are set forth in the accompanying appendices, drawings, and the description below. Other features will become apparent from the description, drawings, and terms. Attached Figure Description

[0010] Figure 1This is an example block diagram representing multiple carriers.

[0011] Figure 2 This is an example block diagram of a carrier used for transmission switching of the physical uplink control channel (PUCCH).

[0012] Figure 3 This is a block diagram of an example method for determining whether to switch carriers for PUCCH resources.

[0013] Figure 4 An example of a wireless communication system to which one or more embodiments of the present technology can be applied is shown.

[0014] Figure 5 It is a block diagram representation of a part of a hardware platform. Detailed Implementation

[0015] The use of section headings in this application is merely for ease of understanding and does not limit the scope of the embodiments to the sections in which they are described. Furthermore, while embodiments are described with reference to 5G examples, the disclosed techniques can be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0016] The development of next-generation wireless communication (5G New Radio, NR) is part of the continuous evolution of mobile broadband to meet the growing network demands. NR can provide greater throughput, allowing more users to connect simultaneously. Other aspects such as energy consumption, equipment complexity, spectrum efficiency, and latency are also important for meeting the needs of various communication scenarios. In current technologies, if carrier aggregation is used for a terminal or user equipment (UE), the corresponding physical uplink control channel carrying the hybrid automatic repeat request acknowledgment (HARQ-ACK PUCCH) can always be transmitted on the uplink primary carrier (Pcell).

[0017] Figure 1 This is an example block diagram 100 representing multiple carriers. However, in some cases, such as... Figure 1 As shown, CC0 and CC1 are aggregated, where CC0 is the primary carrier and CC1 is the secondary carrier. The time slot configuration of CC0 and CC1 is as follows: Figure 1As shown, D indicates the downlink time slot, S indicates the flexible time slot, and U indicates the uplink time slot. When the Physical Downlink Shared Channel (PDSCH) in the first downlink time slot of CC0 is scheduled and required to send a HARQ-ACK in the third time slot, but the third time slot is the DL time slot in CC0, the HARQ-ACK PUCCH may not be transmitted. However, transmission of Ultra Reliable Low Latency Communication (URLLC) services may not be delayed.

[0018] Therefore, since a HARQ-ACK PUCCH can correspond to a UL time slot in CC1, a HARQ-ACK PUCCH can be modified / switched to CC1 for transmission. This method can also be used for other PUCCHs such as CSI PUCCH and / or SR PUCCH.

[0019] Example 1

[0020] In Example 1, the gNodeB can indicate the carrier for PUCCH transmission to the UE through a predefined bit field in the DCI of the physical downlink control channel (PDCCH). Here, PUCCH can include any one of HARQ-ACK PUCCH, SR PUCCH and CSI PUCCH, negative acknowledgment (NACK) PUCCH, ACK-only PUCCH and / or beam failure recovery (BFR) PUCCH.

[0021] Taking HARQ-ACK PUCCH as an example, when the gNodeB schedules PDSCH through the DCI in the PDCCH, the predefined bit fields in the DCI can instruct the carrier to transmit the HARQ-ACK PUCCH corresponding to the PDSCH. In this way, after receiving the DCI, the UE can receive the PDSCH according to the scheduling information in the DCI, decode the PDSCH, and transmit the corresponding HARQ-ACK PUCCH on the carrier indicated by the DCI.

[0022] When the PDSCH is scheduled and the CSI PUCCH (e.g., an A-CSI report) is triggered via the DCI in the PDCCH, the gNodeB can also transmit the CSI PUCCH carrier via a predefined bit field in the DCI. In this way, after receiving the DCI, the UE can transmit the CSI PUCCH on the carrier indicated by the DCI.

[0023] When a release DCI or a sleep DCI is transmitted in the PDCCH, the gNodeB can indicate the carrier transmission of a HARQ-ACK PUCCH through a predefined bit field. This predefined bit field is included in the release DCI or the sleep DCI, and the HARQ-ACK PUCCH corresponds to the release DCI or the sleep DCI.

[0024] The predefined bit field can be a new bit field in the DCI, or an existing bit field in the DCI that is reinterpreted as a predefined bit field. For example, an existing bit field can include at least: a time slot between the PDSCH and the corresponding HARQ-ACK feedback indication field (timing indication, recorded as k1), used to describe the number of time slots between the time slot where the PDSCH is located and the time slot where the corresponding HARQ-ACK PUCCH is located. Optionally, this field may include a PUCCH resource indication field (PUCCH resource indication, recorded as PRI), used to describe the PUCCH resources in the PUCCH resource set.

[0025] To reduce the overhead of predefined bit fields in the DCI, the gNodeB can configure multiple carriers for the UE and allow PUCCH handover / conversion between multiple carriers. For example, the gNodeB can configure multiple carriers via radio resource control (RRC) or medium access control (MAC) control element (MAC CE) signaling, and indicate one carrier in the multiple carriers to transmit the PUCCH via a predefined bit field in the DCI. The same subcarrier spacing (SCS) can be maintained for multiple carriers to simplify operation. In some cases, different SCSs can be allowed for multiple carriers.

[0026] To achieve low UE cost, a new signaling 1 can be introduced to inform the gNodeB whether the UE has the capability to switch / transfer carriers supporting PUCCH transmission. For example, new signaling 1 informs the gNodeB that the UE can support the switching / transfer of carriers for PUCCH transmission. If the gNodeB receives this new signaling 1, it can instruct the UE to switch carriers transmitted on the PUCCH. Otherwise, it cannot instruct the UE to switch carriers for PUCCH transmission (meaning the PUCCH is transmitted in the Pcell). As another example, new signaling 1 informs the gNodeB that the UE cannot support the switching / transfer of carriers for PUCCH transmission. If the gNodeB receives this new signaling 1, it cannot instruct the UE to switch carriers for PUCCH transmission. Otherwise, it can instruct the UE to switch carriers for PUCCH transmission.

[0027] To reduce the complexity of gNodeB scheduling, a new signaling 2 can be introduced to inform the UE whether gNodeB allows (or disallows) the UE to switch the carrier for PUCCH transmission. For example, new signaling 2 informs the UE that gNodeB allows the UE to switch the carrier for PUCCH transmission. If the UE receives this new signaling 2, it receives the DCI and determines the carrier for PUCCH transmission based on the predefined bit fields in the DCI. Otherwise, after receiving the DCI, the UE ignores the predefined bit fields in the DCI and does not determine the carrier for PUCCH transmission based on the predefined bit fields (meaning the PUCCH is transmitted in the Pcell). As another example, new signaling 2 informs the UE that gNodeB does not allow the UE to switch the carrier for PUCCH transmission. If the UE receives this new signaling 2, after receiving the DCI, the UE ignores the predefined bit fields in the DCI and does not determine the carrier for PUCCH transmission based on the predefined bit fields (meaning the PUCCH is transmitted in the Pcell). Otherwise, after receiving the DCI, the UE determines the carrier for PUCCH transmission based on the predefined bit fields in the DCI. The new signaling 2 can be configured by the gNodeB to the UE via RRC or MAC CE signaling.

[0028] If the predefined bit field in the DCI is a new bit field, and if the predefined bit field exists in the DCI (i.e., is configured in the DCI), it can instruct the UE to determine the carrier to which the PUCCH is transmitted based on the predefined bit field. If the predefined bit field does not exist (i.e., is not configured in the DCI), the UE defaults to the PUCCH being transmitted in the Pcell and does not need to switch the carrier to which the PUCCH is transmitted.

[0029] If the UE determines from predefined bit fields in the DCI that it needs to switch PUCCH transmission to another carrier, the PUCCH power indication field (transmit power control (TPC) command for the scheduled PUCCH, also known as the TPC) in the DCI can be applied to the power control of PUCCH transmission on the other carrier. In fact, all PUCCH-related parameters in the DCI can be applied to PUCCH transmission on another carrier. For example, if it indicates that the PUCCH will be transmitted in CC1, the values ​​of PUCCH-related parameters in the DCI (such as k1, PRI, SCS, and TPC) are determined based on the k1 set configured for CC1, the PUCCH resource set, SCS, and TPC.

[0030] As a further extension, for other fields in the existing DCI, such as the TPC field, the BWP indicator field (also known as BWP), or the SRS request field (SRS request), the high bits of these fields can be interpreted as predefined bit fields, or these fields can be interpreted as predefined bit fields.

[0031] If multiple carriers are configured for the UE to switch PUCCH transmissions among these carriers, the number of bits in the PUCCH-related parameter fields (such as k1, PRI, TPC) in the DCI can be determined based on the configuration information of one of the multiple carriers, and that one carrier results in the maximum number of bits.

[0032] Example 2

[0033] In some cases, the high-order bits of the existing k1 field in the DCI are reinterpreted as a predefined bit field to indicate the carrier used for PUCCH transmission. In the current specification, the k1 field in the DCI can indicate the number of slot intervals between the slots of the PDSCH scheduled by the DCI and the corresponding HARQ-ACK PUCCH slots. Typically, 3 bits are used for the k1 field, but in some cases, through RRC configuration, 0, 1, or 2 bits are used for the k1 field.

[0034] As an example, the UE reports to the gNodeB that it supports the handover / switching of the PUCCH transmission carrier and is configured to allow the handover / switching of the PUCCH transmission carrier. For example, the UE is configured to allow the handover of the PUCCH transmission carrier between CC0 and CC1 via RRC signaling. Assume the k1 field is configured as 3 bits. Here, CC0 is a UL Pcell, and CC1 is a UL Scell. The high-order bit (most significant bit) of the k1 field in this DCI is 1, indicating the carrier used for PUCCH transmission. For example, when the high-order bit of k1 is 0, it means the PUCCH is transmitted in CC0; when the high-order bit of k1 is 1, it means the PUCCH is transmitted in CC1 (or, for example, when the high-order bit of k1 is 0, it means the PUCCH is transmitted in a Pcell; when the high-order bit of k1 is 1, it means the PUCCH is transmitted in an Scell ​​(or a non-Pcell)). Figure 1 Through DCI, the gNodeB can schedule PDSCH in the first time slot of CC0. The gNodeB can set the high-order bit of the k1 field to 1, and the low-order bits of the k1 field (excluding predefined bit fields) indicate that the HARQ-ACK PUCCH of this PDSCH will be transmitted in the third time slot. After receiving the DCI, the UE can identify that the HARQ-ACK PUCCH will be transmitted in CC1 and determine that the HARQ-ACK PUCCH will be transmitted in the third time slot of CC1. In some cases, the number of time slot intervals is determined based on the low-order bit value of the k1 field in the k1 set configured for CC1.

[0035] Since only the least significant bit in the k1 field is used to indicate the number of time slot intervals (i.e., 2 bits), the number of k1 values ​​in the k1 set can be configured as follows: Case 1: (maximum) 2 3 There are k1 values, case 2: (maximum) 2 2 There are k1 values. For case 1, gNodeB and UE agree beforehand that the lower bits of the k1 field correspond to (at most) 22 k1 values ​​in the k1 set; for example, the (at most) first 2 k1 values ​​in the k1 set. 2 There are k1 values.

[0036] If the k1 field is configured with 2 bits, it can be similar to a k1 field configured with 3 bits. If the k1 field is configured with 1 bit, and the UE is allowed to switch / transfer the PUCCH transmission carrier (or if the UE is configured to switch / transfer the PUCCH transmission carrier), then the 1 bit of the k1 field is used to indicate the carrier used for PUCCH transmission. The number of time slot intervals uses k1 values ​​defined in the k1 set. The k1 set includes (maximum) 2 1 There are k1 values.

[0037] If the k1 field is configured to bit 0, it can indicate that switching / conversion of the PUCCH transmission carrier is not supported, i.e., the PUCCH is transmitted in the UL Pcell. The k1 set can include (up to) 2 0 The method specifies a set of K1 values, and the number of time slot intervals uses the default k1 values ​​from the k1 set. This method is applicable to DCI 1-0, DCI 1-1, and DCI 1-2.

[0038] This may reduce the number of k1 values ​​in the k1 set, but it may not increase the number of bits in the DCI and will not introduce a new DCI format.

[0039] If a UE is configured with multiple carriers to switch PUCCH transmissions between these carriers, the number of bits in the PUCCH-related parameter fields (such as k1, PRI, TPC) in the DCI is determined based on the configuration information of one of the multiple carriers, and that one carrier results in the maximum number of bits.

[0040] Example 3

[0041] The high bits of the existing PRI field in DCI can be reinterpreted as a predefined bit field to indicate the carrier of the PUCCH transmission.

[0042] In the current specification, the PRI field in DCI can indicate a PUCCH resource in the PUCCH resource set. Typically, 3 bits can be used for the PRI field, but in some cases, through RRC configuration, 0, 1, or 2 bits can be used for the PRI field.

[0043] As an example, the UE reports to the gNodeB that it supports the handover / switching of the PUCCH transmission carrier and is configured to allow the handover / switching of the PUCCH transmission carrier. For example, the UE is configured to allow the handover of the PUCCH transmission carrier between CC0 and CC1 via RRC signaling. Assume the PRI field is configured with 3 bits. Here, CC0 is a UL Pcell, and CC1 is a ULScell. The high-order bit (most significant bit) of the PRI field in this DCI indicates the carrier used for PUCCH transmission. For example, when the high-order bit of PRI is 0, it means the PUCCH is transmitted in CC0; when the high-order bit of PRI is 1, it means the PUCCH is transmitted in CC1 (or, for example, when the high-order bit of PRI is 0, it means the PUCCH is transmitted in a Pcell; when the high-order bit of PRI is 1, it means the PUCCH is transmitted in an Scell ​​(or a non-Pcell)). Figure 1Through DCI, the gNodeB can schedule PDSCH in the first time slot of CC0. The gNodeB can set the high bit of the PRI field to 1, and the low bit of the PRI field (other than the predefined bit fields) indicates that the HARQ-ACK PUCCH of this PDSCH will be transmitted in the third time slot. After receiving the DCI, the UE can identify that the HARQ-ACK PUCCH will be transmitted in CC1 and determine that the HARQ-ACK PUCCH will be transmitted in the third time slot of CC1. In some cases, PUCCH resources are determined based on the low bit value of the PRI field from the PUCCH dataset configured for CC1.

[0044] Since only the low-order bits (i.e., 2 bits) of the PRI field are used to indicate the PUCCH resources in the PUCCH resource set, the number of PUCCH resources in the PUCCH resource set can be configured as follows: Case 1: (Maximum) 2 3 One PUCCH resource, Case 2: (Maximum) 2 2 There are 2 PUCCH resources. For case 1, the gNodeB and UE agree beforehand that the lower bits of the PRI field correspond to (at most) 2 PUCCH resources in the set. 2 A PUCCH resource, for example, the (maximum) top 2 in the PUCCH resource set. 2 One PUCCH resource.

[0045] If the PRI field is configured with 2 bits, it can be configured similarly to a PRI field configured with 3 bits. If the PRI field is configured with 1 bit, and the UE is allowed to switch / transfer the PUCCH transmission carrier (or if the UE is configured to switch / transfer the PUCCH transmission carrier), then bit 1 of the PRI field can be used to indicate the carrier of the PUCCH transmission. PUCCH resources use the defined PUCCH resources in the PUCCH resource set. The PUCCH resource set can include (up to) 2 1 One PUCCH resource.

[0046] If the PRI field is configured to bit 0, it can indicate that switching / conversion of the PUCCH transmission carrier is not supported, meaning that the PUCCH can be transmitted in the UL Pcell. The PUCCH resource set can include (up to) 2 0 There is one PUCCH resource, and the PUCCH resource uses the default PUCCH resource in the PUCCH resource.

[0047] The above method is applicable to DCI 1-0, DCI 1-1, and DCI 1-2. This mechanism can reduce the number of PUCCH resources in the PUCCH resource set, but it may not increase the number of bits in the DCI and will not introduce a new DCI format.

[0048] If a UE is configured with multiple carriers to switch PUCCH transmissions among these carriers, the number of bits in the PUCCH-related parameter fields (such as k1, PRI, TPC) in the DCI is determined based on the configuration information of one of the multiple carriers, and that one carrier results in the maximum number of bits.

[0049] Example 4

[0050] Based on Examples 1-3, the method in Example 4 can be provided to indicate the carrier used for PUCCH transmission. The demodulation reference signal (DMRS) sequence of the PDSCH can be used to indicate the carrier used for PUCCH transmission. For example, the gNodeB configures multiple candidate DMRS sequences for PDSCH transmission. For example, two DMRS sequences are configured and recorded as Sequence 1 and Sequence 2, respectively. When transmitting the PDSCH, the gNodeB can transmit the DMRS sequence to indicate the carrier of the HARQ-ACK PUCCH used for transmitting the PDSCH.

[0051] For example, see Figure 1 Assume DMRS sequence 1 corresponds to CC0 for PUCCH transmission, and DMRS sequence 2 corresponds to CC1 for PUCCH transmission. When the gNodeB transmits PDSCH in the first time slot of CC0, the gNodeB may expect the HARQ-ACK PUCCH of the PDSCH to be transmitted in CC1. The gNodeB can transmit DMRS sequence 2 for decoding the PDSCH. When the PDSCH is received, the UE can detect the corresponding DMRS sequence. The UE can detect that DMRS sequence 2 has been transmitted, and then the UE assumes that the HARQ-ACK PUCCH of the PDSCH will be transmitted in CC1.

[0052] This mechanism may not incur signaling overhead, but it increases the complexity of DMRS sequence detection. In many cases, for a UE, the PUCCH resource set is configured per BWP (bandwidth portion), meaning all PUCCH resources in the PUCCH resource set come from the BWP of a single carrier. A novel method for constructing the PUCCH resource set is described below. Using this new PUCCH resource set, existing PUCCH resource indications can be used for dynamic handover or conversion of PUCCH transport carriers.

[0053] This embodiment may include a PUCCH resource set, configured to contain PUCCH resources from different carriers (or BWPs) of the UE. Then, the PRI (PUCCH Resource Indicator) in the DCI of the PDCCH can be used to indicate the index of the PUCCH resource in the PUCCH resource set. As agreed upon by the gNodeB and the UE, the carrier containing the indicated PUCCH resource is the PUCCH transport carrier (or BWP). In this way, the UE can indirectly obtain the PUCCH transport carrier (or BWP) from the PRI. The following uses a carrier as an example.

[0054] On the gNodeB side, the gNodeB configures one or more PUCCH resource sets for the UE. A PUCCH resource set can include N PUCCH resources, some from carrier 0 (CC0) and others from carrier 1 (CC1). The gNodeB then indicates the PUCCH resources via PRI in the DCI. If the PUCCH resource indicated by PRI comes from CC0, it indicates that the PUCCH needs to be transmitted in CC0. If the PUCCH resource indicated by PRI comes from CC1, it means that the PUCCH needs to be transmitted in CC1.

[0055] On the UE side, a PUCCH resource set containing PUCCH resources from different carriers (or BWPs) is configured for the UE. The UE receives the DCI in the PDCCH, obtains the PUCCH resources from the PRI in the DCI, and determines that the carrier (or BWP) where the PUCCH resources are located is the PUCCH transmission carrier (or BWP).

[0056] For example, the gNodeB configures one or more PUCCH resource sets for the UE, which contain PUCCH resources from multiple carriers. For instance, the PUCCH resource set contains PUCCHs from CC0 and CC1. According to existing technology, the gNodeB can configure eight PUCCH resources for the UE in CC0, with IDs 0-7. It also configures eight PUCCH resources for the UE in CC1, with IDs 0-7. The gNodeB can configure the PUCCH resources identified as 0-3 in CC0 and CC1 as 0-3 into the PUCCH resource set. In this way, a PUCCH resource set containing PUCCH resources from multiple carriers can be constructed for the UE. Therefore, the PUCCH resource set can include eight PUCCH resources from CC0 and CC1 respectively. In this PUCCH resource set, the eight PUCCH resources are configured with indexes. For example, PUCCH resources from CC0, identified as 0~3, are indexed sequentially as 0~3, while PUCCH resources from CC1, identified as 0~3, are indexed sequentially as 4~7. Therefore, in this set of PUCCH resources, each PUCCH can have a unique index.

[0057] The gNodeB can indicate PUCCH resources in the PUCCH resource set to the UE via the PRI indicator in the DCI of the PDCCH. If the gNodeB wants the UE to transmit PUCCH resources via CC0, it can set the PRI value to 0-3 (e.g., setting PRI=1), thus requiring the PUCCH resource with index 1 in the PUCCH resource set to be transmitted via CC0 (because the PUCCH resource with index 1 is in CC0). Similarly, if the gNodeB wants the UE to transmit PUCCH resources via CC1, it can set the PRI value to 4-7 (e.g., setting PRI=4). Therefore, it requires the PUCCH resource with index 4 in the PUCCH resource set to be transmitted via CC1 (because the PUCCH resource with index 4 is in CC1).

[0058] On the UE side, a PUCCH resource set containing PUCCH resources from multiple carriers can be configured for the UE. Each PUCCH resource is configured with a unique index in the PUCCH data set. Then, the UE receives the DCI in the PDCCH and obtains the PUCCH resource from the PRI in the DCI. In this way, the UE can determine that the carrier containing the PUCCH resource is the PUCCH transmission carrier.

[0059] In this way, the carrier can be dynamically indicated for each PUCCH transmission, thus solving the problems raised in the background art. It is only necessary to define that the PUCCH resources in the PUCCH resource set come from multiple carriers. Then, the PRI in the DCI can indicate the PUCCH resources from the PUCCH resource set and indirectly indicate the carrier used for PUCCH transmission.

[0060] The gNodeB can configure multiple carriers for the UE to switch PUCCH transmission carriers via RRC or MAC CE. The same subcarrier spacing (SCS) can be maintained for multiple carriers to simplify operation (different SCS are also possible).

[0061] A PUCCH resource set containing PUCCH resources from multiple carriers can at least include PUCCH resources in the UL Pcell. If the UE is configured with this PUCCH resource set, but the PRI field in the DCI is configured to bit 0, then the gNodeB and the UE can assume that the PUCCH will be determined according to the UL Pcell and transmitted in the UL Pcell. PUCCH includes HARQ-ACK PUCCH, SRPUCCH, and CSI PUCCH, NACK-only PUCCH, ACK-only PUCCH, and BFR PUCCH.

[0062] To achieve low UE cost, a new signaling 1 can be introduced to notify the gNodeB that the UE has / or does not have the capability to switch / transfer carriers supporting PUCCH transmission. Several descriptions can be given here. For example, the new signaling 1 informs the gNodeB that the UE is capable of supporting the switching / transfer of carriers for PUCCH transmission. If the gNodeB receives this new signaling 1, it can instruct the UE to switch the carrier transmitted on the PUCCH. Otherwise, it cannot instruct the UE to switch the carrier for PUCCH transmission (meaning the PUCCH is transmitted in the Pcell). Or, for example, the new signaling 1 informs the gNodeB that the UE is not capable of supporting the switching / transfer of carriers for PUCCH transmission. If the gNodeB receives this new signaling 1, it cannot instruct the UE to switch the carrier for PUCCH transmission. Otherwise, it can instruct the UE to switch the carrier for PUCCH transmission.

[0063] To reduce the complexity of gNodeB scheduling, a new signaling 2 can be introduced to inform the UE that gNodeB allows (or disallows) the UE to switch the carrier of PUCCH transmission.

[0064] If the PRI in the DCI indicates that the PUCCH needs to be transmitted in CC1, then all parameters related to the PUCCH in the DCI can be applied to carrier 1. For example, the actual values ​​of the parameters related to the PUCCH are determined based on the parameters in carrier 1. For example, if the PUCCH is indicated to be transmitted in carrier 1, then k1, PRI, subcarrier spacing (SCS), and transmit power control (TPC) in the DCI correspond to the configuration in CC1.

[0065] Example 5

[0066] Example embodiment 5 can be provided to indicate the carrier used for PUCCH transmission. The DMRS sequence of PDSCH can be used to indicate the carrier used for PUCCH transmission. For example, the gNodeB configures multiple candidate DMRS sequences for PDSCH transmission. For example, two DMRS sequences are configured and recorded as Sequence 1 and Sequence 2, respectively. When transmitting PDSCH, the gNodeB can transmit the DMRS sequence to indicate the carrier of the HARQ-ACK PUCCH for transmitting PDSCH.

[0067] For example, see Figure 1 Assume DMRS sequence 1 corresponds to CC0 for PUCCH transmission, and DMRS sequence 2 corresponds to CC1 for PUCCH transmission. When the gNodeB transmits PDSCH in the first time slot of CC0, the gNodeB expects the HARQ-ACK PUCCH of the PDSCH to be transmitted in CC1. Then, the gNodeB can transmit DMRS sequence 2 for decoding the PDSCH. When the PDSCH is received, the UE detects the corresponding DMRS sequence. The UE finds that DMRS sequence 2 has been transmitted, and then the UE assumes that the HARQ-ACK PUCCH of the PDSCH will be transmitted in CC1. This mechanism may not incur signaling overhead, but it increases the complexity of DMRS sequence detection.

[0068] Example 6

[0069] In many cases, the earliest allowed transmission position of the HARQ-ACK PUCCH corresponding to PDSCH is via T proc，1 To be defined. Here, T proc，1 The definition can be considered as the SCS of PDCCH, the SCS of PDSCH, and the SCS of PUCCH. Therefore, it is possible to choose T. proc，1 Maximize the SCS, and then determine the corresponding parameters (e.g., the value of N1) based on the SCS to calculate T. proc，1 .

[0070] Considering that the dynamic switching / transition of the PUCCH transmission carrier may affect the earliest position of PUCCH transmission, the following describes how to define the switching / transition duration of the PUCCH transmission carrier to better determine the earliest position of PUCCH transmission.

[0071] For simplicity, let's assume the duration required for the UE to complete the PUCCH transmission carrier handover (including corresponding preparations) is denoted as S1. S1 can be defined by the number of symbols, the number of time slots, absolute time, or the number of sampling points. If the S1 duration is defined by the number of symbols, then the number of different symbols is defined as the S1 duration for each type of subcarrier spacing (SCS). The start of the S1 duration is defined as the end of the last symbol of the PDCCH used to change the PUCCH transmission carrier. The duration is then S1. The PUCCH transmission handover to another carrier should not occur earlier than the end of S1. Of course, T, as defined by existing specifications... proc，1 This should also be satisfied. That is, if the carrier of the PUCCH transmission is switched / changed, the first symbol of the PUCCH transmission should not be earlier than T. proc，1 Or the end of S1.

[0072] Figure 2 An example is shown in the figure. Figure 2 This is an example block diagram 200 for a carrier used for PUCCH transmission switching. A PDCCH schedules a PDSCH and indicates the location of the HARQ-ACK PUCCH for the PDSCH. proc，1 The start position of S1 is the end of the PDCCH scheduled by the PDCCH, and the start position of S1 is the end of the PDCCH. The PRI in the DCI of the PDCCH indicates that the PUCCH is switching from CC0 to CC1. Therefore, the first symbol of the PUCCH should not be earlier than T. proc，1 And the end of S1.

[0073] The duration of S1 can be obtained through actual testing, or a more flexible S1 can be defined. Table 1 defines the possible durations of S1.

[0074]

[0075] Figure 3 This is a block diagram of an example method 300 for determining whether to switch a carrier for a PUCCH resource. The method may include: a network node sending a carrier indication message to a terminal, the carrier indication message indicating a carrier via predefined bit fields in a control indication field (block 302). The carrier may include, for example, a reference... Figure 1 The described transport resource is CC0 or CC1. The control indication field may include DCI.

[0076] The method may further include: the network node receiving a second message from the terminal via a carrier indicated in the carrier indication message (box 304). This second message may include an uplink message (PUCCH message) sent from the UE to the gNB, such as... Figure 2 As described in [the text].

[0077] In some embodiments, a carrier indication message is transmitted in a physical downlink control channel (PDCCH) message, and a second message is transmitted in a physical uplink control channel (PUCCH) message.

[0078] In some embodiments, the control indication field includes a downlink control information (DCI) field.

[0079] In some embodiments, the second message includes any one of the following messages: Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) PUCCH (HARQ-ACK PUCCH) message, Scheduling Request (SR) PUCCH message, Channel State Information (CSI) PUCCH message, Negative Acknowledgment Only (NACK) PUCCH message, Acknowledgment Only PUCCH message, and Beam Failure Recovery (BFR) PUCCH message.

[0080] In some embodiments, the carrier indication message instructs the carrier to transmit a HARQ-ACK PUCCH message, which corresponds to a Physical Downlink Shared Channel (PDSCH) message.

[0081] In some embodiments, the terminal is configured to receive a PDSCH according to scheduling information included in the DCI of the carrier indication message, and wherein the terminal is configured to transmit a HARQ-ACK PUCCH on a carrier indicated by the DCI of the channel indication message.

[0082] In some embodiments, when the PDSCH message is scheduled by the DCI of the carrier indication message and the CSI PUCCH is triggered by the DCI of the carrier indication message in the PDCCH message, the carrier indication message includes a carrier that transmits the CSI PUCCH via a predefined bit field in the DCI of the carrier indication message.

[0083] In some embodiments, the carrier indication message indicates carrier transmission of HARQ-ACK PUCCH in a predefined bit field, which is included in the release DCI or the sleep DCI, and the HARQ-ACK PUCCH corresponds to the release DCI or the sleep DCI.

[0084] In some embodiments, the carrier indication message indicates one of the multiple carriers configured for the terminal to allow PUCCH handover between the multiple carriers.

[0085] In some embodiments, the method includes: receiving a first signaling message from a terminal by a network node, the first signaling message indicating that the terminal may perform a carrier switch for PUCCH transmission, wherein the network node is permitted to instruct the terminal to switch carriers in a carrier indication message in response to receiving the first signaling message.

[0086] In some embodiments, the method includes: a network node sending a second signaling message to a terminal, the second signaling message instructing the network node to allow the terminal to switch the carrier used for PUCCH transmission, wherein the terminal is configured to use a carrier indication message to determine the carrier used for PUCCH transmission.

[0087] In some embodiments, when configuring multiple carriers for a terminal to switch PUCCH transmission, the number of bits in the PUCCH-related parameter fields in the control indication field is determined based on the configuration information of one of the multiple carriers, and that one carrier results in a maximum number of bits.

[0088] In some embodiments, a set of high-order bits of the k1 field of the DCI is interpreted as a predefined bit field to indicate the carrier used for PUCCH transmission.

[0089] In some embodiments, network nodes are configured to schedule the Physical Downlink Shared Channel (PDSCH) in a first time slot, wherein the high bit of the k1 field is set to 1, and wherein the low bit of the k1 field indicates that the HARQ-ACK PUCCH of the PDSCH is transmitted in a third time slot.

[0090] In some embodiments, the k1 field corresponding to the DCI is configured as bit 1, and the k1 field of the DCI indicates the carrier used for PUCCH transmission.

[0091] In some embodiments, the k1 field corresponding to the DCI is configured as bit 0, and the k1 field of the DCI indicates that switching of the PUCCH transmission carrier is not supported.

[0092] In some embodiments, a set of high-order bits of the PRI field in the DCI is reinterpreted as a predefined bit field to indicate the carrier used for PUCCH transmission.

[0093] In some embodiments, network nodes are configured to allow terminals to switch carriers among multiple carriers via Radio Resource Control (RRC) signaling.

[0094] In some embodiments, the PRI field corresponding to the DCI is configured as bit 1, and the PRI field of the DCI indicates the carrier used for PUCCH transmission.

[0095] In some embodiments, the PRI field corresponding to the DCI is configured to bit 0, and the PRI field of the DCI indicates that switching of the PUCCH transmission carrier is not supported.

[0096] In some embodiments, the PUCCH resource set is configured to include PUCCH resources for the terminal from the multicarrier or bandwidth portion (BWP).

[0097] In some embodiments, the carrier indication message is a PRI field in the DCI and indicates PUCCH resources in a PUCCH resource set, which includes PUCCH resources for the terminal from multiple carriers or BWP.

[0098] In some embodiments, the PRI field in the DCI of the carrier indication message indicates the index of the PUCCH resource in the PUCCH resource set.

[0099] In some embodiments, the terminal is configured to determine, based on the PUCCH resource set, whether the carrier containing the PUCCH resource indicated by the PRI or the BWP is the PUCCH transmission carrier.

[0100] In another example embodiment, a method for wireless communication includes: receiving a carrier indication message from a network node by a terminal, the carrier indication message indicating a carrier via a predefined bit field in a control indication field. The method may further include: sending a second message from the terminal to the network node via the carrier indicated in the carrier indication message.

[0101] In some embodiments, the carrier indication message is transmitted in a physical downlink control channel (PDCCH) message, while the second message is transmitted in a physical uplink control channel (PUCCH) message.

[0102] In some embodiments, the control indication field includes a downlink control information (DCI) field.

[0103] In some embodiments, the second message includes any one of the following messages: Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) PUCCH (HARQ-ACK PUCCH) message, Scheduling Request (SR) PUCCH message, Channel State Information (CSI) PUCCH message, Negative Acknowledgment Only (NACK) PUCCH message, Acknowledgment Only PUCCH message, and Beam Failure Recovery (BFR) PUCCH message.

[0104] In some embodiments, the carrier indication message instructs the carrier to transmit a HARQ-ACK PUCCH message, which corresponds to a Physical Downlink Shared Channel (PDSCH) message.

[0105] In some embodiments, the terminal is configured to receive a PDSCH based on scheduling information included in the DCI of the carrier indication message, and wherein the terminal is configured to transmit a HARQ-ACK PUCCH on the carrier indicated by the DCI of the channel indication message.

[0106] In some embodiments, the carrier indication message includes a carrier for transmitting the CSI PUCCH via a predefined bit field in the carrier indication message's DCI when the PDSCH message is scheduled by the carrier indication message's DCI, and the CSI PUCCH is triggered by the carrier indication message's DCI in the PDCCH message.

[0107] In some embodiments, the carrier indication message indicates carrier transmission of HARQ-ACK PUCCH in a predefined bit field, which is included in the release DCI or the sleep DCI, and the HARQ-ACK PUCCH corresponds to the release DCI or the sleep DCI.

[0108] In some embodiments, the carrier indication message indicates one of the multiple carriers configured for the terminal to allow PUCCH switching between the multiple carriers.

[0109] In some embodiments, the method includes: receiving a first signaling message from a terminal by a network node, the first signaling message instructing the terminal to perform a carrier switch for PUCCH transmission, wherein the network node is permitted to instruct the terminal to switch carriers in a carrier indication message in response to receiving the first signaling message.

[0110] In some embodiments, the method includes: a network node sending a second signaling message to a terminal, the second signaling message instructing the network node to allow the terminal to switch the carrier used for PUCCH transmission, wherein the terminal is configured to use a carrier indication message to determine the carrier used for PUCCH transmission.

[0111] In some embodiments, when configuring multiple carriers for a terminal to switch PUCCH transmission, the number of bits in the PUCCH-related parameter fields in the control indication field is determined based on the configuration information of one of the multiple carriers, and that one carrier results in a maximum number of bits.

[0112] In some embodiments, a set of high-order bits of the k1 field of the DCI is interpreted as a predefined bit field to indicate the carrier used for PUCCH transmission.

[0113] In some embodiments, the k1 field corresponding to the DCI is configured as bit 1, and the k1 field of the DCI indicates the carrier used for PUCCH transmission.

[0114] In some embodiments, the k1 field corresponding to the DCI is configured as bit 0, and the k1 field of the DCI indicates that switching of the PUCCH transmission carrier is not supported.

[0115] In some embodiments, a set of high-order bits of the PRI field in the DCI is reinterpreted as a predefined bit field to indicate the carrier used for PUCCH transmission.

[0116] In some embodiments, network nodes are configured to allow terminals to switch carriers among multiple carriers via Radio Resource Control (RRC) signaling.

[0117] In some embodiments, the PRI field corresponding to the DCI is configured as bit 1, and the PRI field of the DCI indicates the carrier used for PUCCH transmission.

[0118] In some embodiments, the PRI field corresponding to the DCI is configured to bit 0, and the PRI field of the DCI indicates that switching of the PUCCH transmission carrier is not supported.

[0119] In some embodiments, the PUCCH resource set is configured to include PUCCH resources for the terminal from the multicarrier or bandwidth portion (BWP).

[0120] In some embodiments, the carrier indication message is a PRI field in the DCI and indicates PUCCH resources in a PUCCH resource set, which includes PUCCH resources for the terminal from multiple carriers or BWP.

[0121] In some embodiments, the PRI field in the DCI of the carrier indication message indicates the index of the PUCCH resource in the PUCCH resource set.

[0122] In some embodiments, the terminal is configured to determine, based on the PUCCH resource set, whether the carrier containing the PUCCH resource indicated by the PRI or the BWP is the PUCCH transmission carrier.

[0123] Example wireless system

[0124] Figure 4An example of a wireless communication system to which one or more embodiments of the present technology can be applied is shown. The wireless communication system 400 may include one or more base stations (BS) 405a, 405b, one or more wireless devices or terminals 410a, 410b, 410c, 410d, and a core network 425. Base stations 405a, 405b may provide wireless services to wireless devices 410a, 410b, 410c, and 410d in one or more wireless sectors. In some embodiments, base stations 405a, 405b include directional antennas that generate two or more directional beams to provide wireless coverage in different sectors. The base stations may implement cell scheduling or candidate cell functionality, as described in this application.

[0125] The core network 425 can communicate with one or more base stations 405a and 405b. The core network 425 provides connectivity with other wireless and wired communication systems. The core network may include one or more service subscription databases for storing information related to subscribed wireless devices 410a, 410b, 410c, and 410d. The first base station 405a can provide wireless services based on a first wireless access technology, while the second base station 405b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 405a and 405b can be located in the same location or can be installed separately in the field. Wireless devices 410a, 410b, 410c, and 410d can support multiple different wireless access technologies.

[0126] In some implementations, a wireless communication system may include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices include two or more wireless technologies that can be used to connect to different wireless networks.

[0127] Figure 5 This is a block diagram representation of a hardware platform. Hardware platform 505, such as a network node, base station, terminal, or wireless device (or UE), may include processor electronics 510, such as a microprocessor implementing one or more technologies presented in this application. Hardware platform 505 may include transceiver electronics 515 for transmitting and / or receiving wired or wireless signals via one or more communication interfaces, such as antenna 520 or a wired interface. Hardware platform 505 may implement other communication interfaces having defined protocols for transmitting and receiving data. Hardware platform 505 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, processor electronics 510 may include at least a portion of transceiver electronics 515. In some embodiments, hardware platform 505 is used to implement at least some of the disclosed technologies, modules, or functions.

[0128] in conclusion

[0129] The disclosed and other embodiments, modules, and functional operations described in this application can be implemented in digital electronic circuits, or in computer software, firmware, or hardware (including the structures disclosed in this application and their equivalents), or in a combination of one or more of these. The disclosed and other embodiments can be implemented as one or more computer program products (i.e., one or more modules of computer program instructions encoded on a computer-readable medium) for execution by or control of the operation of a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition of substances influencing machine-readable propagation signals, or one or more of these. The term "data processing apparatus" encompasses all means, devices, and machines for processing data, including, for example, a programmable processor, a computer, or a plurality of processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these. The propagation signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0130] Computer programs (also referred to as programs, software, software applications, scripts, or code) can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units suited to a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple co-located files (e.g., a file storing one or more modules, subroutines, or code sections). A computer program can be deployed to execute on a single computer, or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communication network.

[0131] The processes and logic flows described in this application can be executed by one or more programmable processors that execute one or more computer programs to perform functions by manipulating input data and generating outputs. The processes and logic flows can also be executed by dedicated logic circuitry, and the apparatus can also be implemented as dedicated logic circuitry, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit).

[0132] Processors suitable for executing computer programs include, for example, general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Typically, a computer will also include, or be operatively coupled to, one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, to receive data from or transfer data to, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM optical disks. The processor and memory may be supplemented or incorporated therein by dedicated logic circuitry.

[0133] Although this patent application contains numerous details, these details should not be construed as limiting the scope of any invention or what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of a particular invention. Certain features described in the context of individual embodiments in this patent application may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as functioning in a particular combination, and even initially claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0134] Similarly, although the operations are described in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order or sequence shown, or requiring all illustrated operations to achieve the desired result. Furthermore, the separation of various system components in the embodiments described in this patent application should not be construed as requiring such separation in all embodiments.

[0135] Only some implementation methods and examples have been described. Other implementation methods, improvements and variations can be made based on the content described and illustrated in this patent application.

Claims

1. A method for wireless communication, comprising: The network node configures one or more Physical Uplink Control Channel (PUCCH) resource sets for the terminal. The PUCCH resource set includes N PUCCH resources, which include PUCCH resources from a first frequency domain resource and PUCCH resources from a second frequency domain resource. The first frequency domain resource includes a first carrier or a first partial bandwidth (BWP), and the second frequency domain resource includes a second carrier or a second BWP. The network node sends downlink control information (DCI) including an indicator of PUCCH resources to the terminal, wherein: When the PUCCH resource indicated by the indicator comes from the first frequency domain resource, the terminal will use the PUCCH resource on the first frequency domain resource to send a PUCCH transmission; and If the PUCCH resource indicated by the indicator comes from the second frequency domain resource, the terminal will use the PUCCH resource on the second frequency domain resource to send PUCCH transmission.

2. The method according to claim 1, wherein, The PUCCH resource is indicated via a predefined bit field in the DCI.

3. The method according to claim 2, wherein, The predefined bit field is the PUCCH resource indicator PRI field, and The PRI field indicates an index of a PUCCH resource from the one or more PUCCH resource sets.

4. The method according to claim 2, wherein, The predefined bit field is the PUCCH resource indicator PRI field, and The location of the PUCCH resource indicated by the PRI field in one or more PUCCH resource sets determines the carrier or bandwidth portion (BWP) used for PUCCH transmission.

5. The method according to claim 1 or 2, wherein, The DCI refers to a DCI that releases, sleeps, or schedules the Physical Downlink Shared Channel (PDSCH). The PUCCH resource indicates a carrier used to transmit a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ARC) PUCCH corresponding to the Release DCI, the Sleep DCI, or the PDSCH.

6. The method according to any one of claims 1-4, further comprising: The network node receives the second message from the PUCCH from the terminal on the carrier corresponding to the PUCCH resource. The second message includes at least one of the following: a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ARC) (HARQ-ACK) message, a Negative Acknowledgment Only (NACK) message, or an Acknowledgment Only (ACK) message.

7. The method according to any one of claims 1-4, further comprising: The network node receives a first signaling message from the terminal, the first signaling message indicating that the terminal has the capability to transmit a switching carrier for PUCCH.

8. The method according to any one of claims 1-4, further comprising: The network node sends a signaling message to the terminal via Radio Resource Control (RRC) signaling, the signaling message indicating that the terminal is permitted to switch carriers for PUCCH transmission among multiple carriers based on the PUCCH resources.

9. The method according to any one of claims 1-4, wherein, The values ​​of the parameters associated with the PUCCH transmission are determined based on the corresponding parameters or parameter set configured for the carrier where the PUCCH resource indicated by the indicator resides, and The parameters include at least one of the following: k1, PUCCH resource indicator PRI, transmit power control (TPC) for the PUCCH, and subcarrier spacing (SCS); wherein k1 is the number of time slots between the time slot where the Physical Downlink Shared Channel (PDSCH) is located and the time slot where the HARQ-ACK PUCCH corresponding to the PDSCH is located.

10. A method for wireless communication, comprising: The terminal receives configuration information, which is used to configure one or more Physical Uplink Control Channel (PUCCH) resource sets for the terminal. The PUCCH resource set includes N PUCCH resources, which include PUCCH resources from a first frequency domain resource and PUCCH resources from a second frequency domain resource. The first frequency domain resource includes a first carrier or a first partial bandwidth (BWP), and the second frequency domain resource includes a second carrier or a second BWP. The terminal receives downlink control information (DCI) including an indicator of PUCCH resources from the network node, wherein: When the PUCCH resource indicated by the indicator comes from the first frequency domain resource, the terminal will use the PUCCH resource on the first frequency domain resource to send a PUCCH transmission; and If the PUCCH resource indicated by the indicator comes from the second frequency domain resource, the terminal will use the PUCCH resource on the second frequency domain resource to send PUCCH transmission.

11. The method according to claim 10, wherein, The PUCCH resource is indicated via a predefined bit field in the DCI.

12. The method according to claim 11, wherein, The predefined bit field is the PUCCH resource indicator PRI field, and The PRI field indicates an index of a PUCCH resource from the one or more PUCCH resource sets.

13. The method according to claim 11, wherein, The predefined bit field is the PUCCH resource indicator PRI field, and The location of the PUCCH resource indicated by the PRI field in one or more PUCCH resource sets determines the carrier or bandwidth portion (BWP) used for PUCCH transmission.

14. The method according to claim 10 or 11, wherein, The DCI refers to a DCI that releases, sleeps, or schedules the Physical Downlink Shared Channel (PDSCH). The PUCCH resource indicates a carrier used to transmit a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ARC) PUCCH corresponding to the Release DCI, the Sleep DCI, or the PDSCH.

15. The method according to any one of claims 10-13, further comprising: The terminal sends a second message from the PUCCH on the carrier corresponding to the PUCCH resource to the network node. The second message includes at least one of the following: a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ARC) (HARQ-ACK) message, a Negative Acknowledgment Only (NACK) message, or an Acknowledgment Only (ACK) message.

16. The method according to any one of claims 10-13, further comprising: The terminal sends a first signaling message to the network node, the first signaling message indicating that the terminal has the capability to transmit a switching carrier for PUCCH.

17. The method according to any one of claims 10-13, further comprising: The terminal receives a signaling message from the network node via Radio Resource Control (RRC) signaling, the signaling message indicating that the terminal is permitted to switch carriers for PUCCH transmission among multiple carriers based on the PUCCH resources.

18. The method according to any one of claims 10-13, wherein, The values ​​of the parameters associated with the PUCCH transmission are determined based on the corresponding parameters or parameter set configured for the carrier where the PUCCH resource indicated by the indicator resides, and The parameters include at least one of the following: k1, PUCCH resource indicator PRI, transmit power control (TPC) for the PUCCH, and subcarrier spacing (SCS); wherein k1 is the number of time slots between the time slot where the Physical Downlink Shared Channel (PDSCH) is located and the time slot where the HARQ-ACK PUCCH corresponding to the PDSCH is located.

19. An apparatus for wireless communication, the apparatus comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the apparatus to perform the following operations: Configure one or more Physical Uplink Control Channel (PUCCH) resource sets for the terminal. in, The PUCCH resource set includes N PUCCH resources, which include PUCCH resources from a first frequency domain resource and PUCCH resources from a second frequency domain resource. The first frequency domain resource includes a first carrier or a first partial bandwidth (BWP), and the second frequency domain resource includes a second carrier or a second BWP. Send downlink control information (DCI) including an indicator of PUCCH resources to the terminal, wherein: When the PUCCH resource indicated by the indicator comes from the first frequency domain resource, the terminal will use the PUCCH resource on the first frequency domain resource to send a PUCCH transmission; and If the PUCCH resource indicated by the indicator comes from the second frequency domain resource, the terminal will use the PUCCH resource on the second frequency domain resource to send PUCCH transmission.

20. An apparatus for wireless communication, the apparatus comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the apparatus to perform the following operations: Receive configuration information, among which, The configuration information is used to configure one or more Physical Uplink Control Channel (PUCCH) resource sets. The PUCCH resource set includes N PUCCH resources, which include PUCCH resources from a first frequency domain resource and PUCCH resources from a second frequency domain resource. The first frequency domain resource includes a first carrier or a first partial bandwidth (BWP), and the second frequency domain resource includes a second carrier or a second BWP. Receive downlink control information (DCI) from the network node, including indicators of PUCCH resources, where: When the PUCCH resource indicated by the indicator comes from the first frequency domain resource, the terminal will use the PUCCH resource on the first frequency domain resource to send a PUCCH transmission; and If the PUCCH resource indicated by the indicator comes from the second frequency domain resource, the terminal will use the PUCCH resource on the second frequency domain resource to send PUCCH transmission.

21. A non-transitory computer-readable medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 18.

Images