Wireless communication method and user equipment for transmitting on different bandwidth parts

Abstract

A wireless communication method for transmission on different bandwidth parts (BWPs) performed by a user equipment includes receiving a radio resource control (RRC) message configuring a first physical uplink control channel configuration (PUCCH-Config) for an uplink (UL) bandwidth part (BWP) of a first cell and a second PUCCH-Config for a UL BWP of a second cell; receiving downlink control information (DCI) including fields indicating a duration and a handover indication from the first cell; and if the handover indication indicates the second cell, sending a PUCCH on the UL BWP of the second cell after receiving the DCI.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims the benefit of and priority to provisional U.S. patent application Ser. No. 63 / 105,170, filed on Oct. 23, 2020 (“‘170 Provisional”), entitled “METHOD AND APPARATUS FOR SCHEDULING PUCCH AMONG DIFFERENT COMPONENT CARRIERS.” The contents of the ’170 Provisional are hereby incorporated by reference in their entirety for all purposes. Technical Field

[0003] The present disclosure relates generally to wireless communications, and in particular, to a wireless communication method and user equipment for transmitting on different bandwidth parts (BandWidthPart, BWP). Background Art

[0004] With the huge growth in the number of connected devices and the rapid increase in user / network (NW) traffic, various efforts have been made to improve different aspects of wireless communications in the next-generation wireless communication systems, such as fifth-generation (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility.

[0005] The 5G NR system is designed to provide flexibility and configurability to optimize NW services and types to suit various use cases, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0006] However, as the demand for radio access continues to increase, there is a need in the art to perform transmissions on different bandwidth parts (BWPs). Summary of the Invention

[0007] The present disclosure is directed to methods and user equipment (UE) for transmitting on different bandwidth parts (BWPs).

[0008] In a first aspect of the present disclosure, a method for transmitting on different bandwidth parts (BWPs) performed by a user equipment (UE) is provided. The method includes receiving a radio resource control (RRC) message configuring a first physical uplink control channel configuration (PUCCH-Config) for an uplink (UL) BWP of a first cell and a second PUCCH-Config for an UL BWP of a second cell; receiving downlink control information (DCI) from the first cell including fields indicating a duration and a handover indication; and if the handover indication indicates the second cell, sending a PUCCH on the UL BWP of the second cell after receiving the DCI.

[0009] In another embodiment of the first aspect, the duration is based at least on the sub-carrier spacing (SCS) configuration of the UL BWP of the second cell and indicates an offset value transmitted between the physical downlink shared channel (PDSCH) and the PUCCH scheduled by the DCI in the time domain.

[0010] Another implementation of the first aspect further includes sending a UE capability message to indicate whether the UE supports sending PUCCH on the UL BWP of the second cell after receiving the DCI.

[0011] In another implementation of the first aspect, a field of the DCI further indicates an index (ID) of the second cell as a handover indication.

[0012] In another implementation of the first aspect, the first cell is a primary cell (PCell), the second cell is a secondary cell (SCell), and the first cell and the second cell are in the same PUCCH cell group.

[0013] In a second aspect of the present disclosure, a user equipment (UE) for transmitting on different bandwidth parts (BWPs) in a wireless communication system is provided. The UE includes a processor; and a memory coupled to the processor, wherein the memory stores a computer-executable program that, when executed by the processor, causes the processor to receive a radio resource control (RRC) message configuring a first physical uplink control channel configuration (PUCCH-Config) for an uplink (UL) BWP of a first cell and a second PUCCH-Config for a UL BWP of a second cell; receive downlink control information (DCI) including a field indicating a duration and a handover indication from the first cell; and, if the handover indication indicates the second cell, transmit a PUCCH on the UL BWP of the second cell after receiving the DCI. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] When with Figure 1 Various aspects of the present disclosure are best understood from the following when read together. Various features are not drawn to scale. The dimensions of various features may be arbitrarily increased or decreased for clarity of discussion.

[0015] Figure 1 FIG. 1 is a schematic diagram illustrating different carriers with different UL / DL modes according to an embodiment of the present disclosure.

[0016] Figure 2 is a schematic diagram illustrating a parameter K1 based on a reference carrier according to an embodiment of the present disclosure.

[0017] Figure 3 is a schematic diagram illustrating a parameter K1 based on a first carrier according to an embodiment of the present disclosure.

[0018] Figure 4 is a schematic diagram illustrating a parameter K1 based on a second carrier according to an embodiment of the present disclosure.

[0019] Figure 5 is a schematic diagram illustrating parameter K1 based on different SCS configurations according to an embodiment of the present disclosure.

[0020] Figure 6 FIG. 1 is a schematic diagram illustrating a process performed by a UE for sending on different BWPs according to an embodiment of the present disclosure.

[0021] Figure 7 FIG. 4 is a block diagram illustrating a node for wireless communication according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] The acronyms used in this disclosure are defined as follows. Unless otherwise indicated, the acronyms have the following meanings.

[0023] Full acronym

[0024] 3GPP (3rd Generation Partnership Project)

[0025] 5G 5th generation

[0026] ACK (Acknowledgement)

[0027] AR (Augmented Reality)

[0028] BS Base Station

[0029] BWP Bandwidth Part

[0030] Carrier Aggregation (CA)

[0031] CC Component Carrier

[0032] CE Control Element

[0033] CN Core Network

[0034] C-RNTI Cell Radio Network Temporary Identifier

[0035] Identifier

[0036] DAI Downlink Assignment Index

[0037] DC Dual Connectivity

[0038] DCI Downlink Control Information

[0039] DL Downlink

[0040] FR1 / 2 Frequency Range 1 / 2

[0041] GC-PDCCH Group Common-Physical Downlink Control Channel

[0042] gNB gNode B

[0043] HARQ Hybrid Automatic Repeat Request (HARQ) ID Index

[0044] IE Information Element

[0045] IIoT (Industrial Internet of Things)

[0046] LSB Least Significant Bit

[0047] LTE Long Term Evolution

[0048] L1 Layer 1

[0049] MAC Medium Access Control

[0050] MCG Master Cell Group

[0051] MCS-C-RNTI Modulation Coding Scheme-Cell-Radio Network Temporary Identity (Modulation

[0052] Coding Scheme-Cell-Radio Network Temporary Identifier)MIMO Multi-Input Multi-Output

[0053] MSB Most Significant Bit

[0054] NACK Negative Acknowledgement

[0055] NDI New Data Indicator

[0056] NR New Radio

[0057] NW Network

[0058] PCell Primary Cell

[0059] PSCell Primary Secondary Cell

[0060] PBCH Physical Broadcast Channel

[0061] PDCCH Physical Downlink Control Channel

[0062] Channel)

[0063] PDSCH Physical Downlink Shared Channel

[0064] Channel)

[0065] PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel PDU Protocol Data Unit

[0066] PHYPhysical

[0067] PTAG Primary Timing Advance Group

[0068] RAN Radio Access Network

[0069] RelRelease

[0070] RMSI Remaining Minimum System Information

[0071] Information)

[0072] RNTI Radio Network Temporary Identifier

[0073] Identifier

[0074] RRC Radio Resource Control

[0075] RV Redundancy Version

[0076] SCell (Secondary Cell)

[0077] SCG Secondary Cell Group

[0078] SCS Subcarrier Spacing

[0079] SFI Slot Format Indicator

[0080] SI System Information

[0081] SpCell Special Cell

[0082] SLIV Start and Length Indicator Value SPS Semi-Persistent Scheduling

[0083] SR Scheduling Request

[0084] SRS Sounding Reference Signal

[0085] SSB Synchronization Signal Block

[0086] STAG Secondary Timing Advance Group

[0087] SUL Supplementary Uplink

[0088] TAG Timing Advance Group

[0089] TB Transport Block

[0090] TBS Transport Block Size

[0091] TCI Transmission Configuration Indicator

[0092] TDD Time Division Duplex

[0093] TR Technical Report

[0094] TS Technical Specification

[0095] TTI Transmission Time Interval

[0096] TX transmission

[0097] UCI Uplink Control Information

[0098] UE (User Equipment)

[0099] UL Uplink

[0100] UL-SCH Uplink Shared Channel

[0101] URLLC Ultra Reliable Low Latency Communication

[0102] Communication

[0103] USS UE-Specific Search Space

[0104] WG Working Group

[0105] WI Working Item

[0106] QCL Quasi Co-Location

[0107] The following contains specific information related to embodiments of the present disclosure. The drawings and the detailed disclosure accompanying them are directed to exemplary embodiments only. However, the present disclosure is not limited to these exemplary embodiments. Those skilled in the art will recognize other variations and embodiments of the present disclosure. Unless otherwise indicated, identical or corresponding elements in the drawings may be represented by identical or corresponding reference numerals. In addition, the drawings and illustrations in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0108] For consistency and ease of understanding, similar features are identified by numbers in the example figures (although not shown in some examples). However, features in different embodiments may differ in other aspects and should not be narrowly limited to what is shown in the figures.

[0109] References to "one embodiment," "an embodiment," "example embodiment," "various embodiments," "some embodiments," "embodiments of the present disclosure," etc. may indicate that embodiments of the present disclosure may include a particular feature, structure, or characteristic, but not every possible embodiment of the present disclosure must include the particular feature, structure, or characteristic. Furthermore, repeated use of the phrases "in one embodiment," "in an example embodiment," or "an embodiment" does not necessarily refer to the same embodiment, although they may. Moreover, use of a phrase such as "embodiments" in conjunction with "the present disclosure" does not mean that all embodiments characterizing the present disclosure must include the particular feature, structure, or characteristic, but rather should be understood to mean that "at least some embodiments of the present disclosure" include the particular feature, structure, or characteristic.

[0110] The term "coupled" is defined as connected, whether directly or indirectly through intermediate components, and is not necessarily limited to physical connections. The term "comprising" when used means "including, but not necessarily limited to," and it specifically indicates open inclusion or membership in the disclosed combinations, groups, series, and equivalents.

[0111] The term "and / or" simply describes the relationship between associated objects, indicating three possible relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists. Additionally, the character " / " generally indicates an "or" relationship between the associated objects.

[0112] In addition, for the purpose of non-limiting explanation, specific details such as functional entities, technologies, protocols, standards, etc. are set forth to provide an understanding of the disclosed technology. In other instances, detailed disclosure of well-known methods, technologies, systems, architectures, etc. is omitted to avoid obscuring the present disclosure with unnecessary details.

[0113] Those skilled in the art will immediately recognize that any NW function or algorithm in this disclosure can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions may correspond to modules that can be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device.

[0114] For example, one or more microprocessors or general-purpose computers with communication processing capabilities can be programmed with corresponding executable instructions and execute the disclosed NW functions or algorithms. The microprocessor or general-purpose computer can be formed by an application-specific integrated circuit (ASIC), a programmable logic array, and / or using one or more digital signal processors (DSP). Although some example embodiments of the present disclosure are directed to software installed and executed on computer hardware, alternative example embodiments implemented as firmware or hardware or a combination of hardware and software are fully within the scope of the present disclosure.

[0115] Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic tape, magnetic tape, disk storage, or any other equivalent medium that can store computer-readable instructions.

[0116] A radio communication NW architecture (e.g., an LTE system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system) typically includes at least one base station (BS), at least one user equipment (UE), and one or more optional NW elements providing connectivity to the NW. The UE connects to the NW (e.g., a CN, an Evolved Packet Core (EPC) NW, an Evolved Universal Terrestrial Radio Access NW (E-UTRAN), a Next-Generation Core (NGC), a 5G Core Network (5GC), or the Internet) through a RAN established by the BS.

[0117] It should be noted that in this disclosure, a UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. For example, a UE may be a portable radio device, including, but not limited to, a mobile phone, a tablet computer, a wearable device, a sensor, or a personal digital assistant (PDA) with wireless communication capabilities. A UE is configured to receive and transmit signals to one or more cells in the RAN over an air interface.

[0118] The BS may include, but is not limited to, a Node B (NB) such as in the Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) such as in LTE-A, a Radio NW Controller (RNC) such as in UMTS, a Base Station Controller (BSC) such as in the Radio Access NW (GERAN) of the Global System for Mobile communication (GSM) / GSM Enhanced Data rates for GSM Evolution (EDGE), a Next Generation eNB (ng-eNB) such as the E-UTRA BS associated with 5GC, a gNB in ​​the 5G Access Network (5G-AN), and any other device capable of controlling radio communications within a cell and managing radio resources. The BS may be connected to the NW via a radio interface to serve one or more UEs.

[0119] The BS may be configured to provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS based on basic Wideband-Code Division Multiple Access (W-CDMA) (commonly referred to as 3G), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, Enhanced LTE (eLTE), NR (commonly referred to as 5G), and LTE-A Pro. However, the scope of the present disclosure should not be limited to the previously disclosed protocols.

[0120] The BS can be used to provide radio coverage to a specific geographical area using multiple cells included in the RAN. The BS can support the operation of cells. Each cell is operable to provide services to at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) can provide services to serve one or more UEs within its radio coverage (for example, each cell schedules DL and optional UL resources to at least one UE within its radio coverage for DL ​​and optional UL packet transmission). The BS can communicate with one or more UEs in the radio communication system through multiple cells. The cell can allocate sidelink (SL) resources for supporting proximity services (ProSe). Each cell may have a coverage area that overlaps with other cells.

[0121] In Multi-RAT Dual Connectivity (MR-DC), the primary cell of an MCG or SCG may be referred to as an SpCell. A PCell may refer to the SpCell of an MCG. A PSCell may refer to the SpCell of an SCG. An MCG refers to a set of serving cells associated with a Master Node (MN), including an SpCell and optionally one or more SCells. An SCG refers to a set of serving cells associated with a Secondary Node (SN), including an SpCell and optionally one or more SCells.

[0122] In some embodiments, the UE may not have an (LTE / NR) RRC connection with the corresponding serving cell for the relevant service. In other words, the UE may not perform UE-specific RRC signaling exchanges with the serving cell. Instead, the UE may only monitor DL ​​synchronization signals (e.g., DL synchronization burst sets) and / or broadcast SI related to the corresponding services from these serving cells. In addition, the UE may have at least one serving cell on one or more target SL frequency carriers for the relevant service. In some other embodiments, the UE may regard the RAN that configures one or more serving cells as the serving RAN.

[0123] As mentioned earlier, the frame structure of NR supports flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while meeting high reliability, high data rate, and low latency requirements. As disclosed in 3GPP, OFDM technology can be used as the baseline for the NR waveform. Scalable OFDM parameters such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used. In addition, NR considers two coding schemes: (1) low-density parity-check (LDPC) codes and (2) polar codes. The coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0124] It is also considered that the transmission time interval of a single NR frame should include at least DL transmission data, guard period, and UL transmission data. The corresponding parts of DL transmission data, guard period, and UL transmission data should also be configurable, for example, based on the dynamic network width of NR. In addition, SL resources can also be provided in NR frames to support ProSe services.

[0125] Here are some technical terms:

[0126] HARQ: A function that ensures data delivery between peer entities at Layer 1 (i.e., the PHY layer). When the PHY layer is not configured for DL / UL spatial multiplexing, a single HARQ process can support 1 TB. When the PHY layer is configured for DL / UL spatial multiplexing, a single HARQ process can support one or more TBs. There may be one HARQ entity per serving cell. Each HARQ entity can support multiple DL and UL HARQ processes in parallel.

[0127] PUCCH: In the 3GPP NR Rel-15 and Rel-16 specifications, the NW can configure the parameter PUCCH-Config on at least one non-initial BWP of one SpCell and one PUCCHSCell, where PUCCH SCell refers to the SCell configured with one PUCCH. If supported by the UE, the NW can configure up to one PUCCH-Config for the additional SCell of one cell group, where one PUCCH configuration can be one BWP configuration of the normal UL or SUL of one serving cell. If the UE is configured with SUL, the NW can configure only one PUCCH on the BWP of one of the ULs (e.g., normal UL or SUL). In other words, PUCCH can be sent on one serving cell in the PUCCH cell group. If the UE is configured with one PUCCH SCell, the UE can apply the corresponding PUCCH transmission to both the primary PUCCH group and the secondary PUCCH group. In addition, the NW can configure the ID of the serving cell of the same cell group for PUCCH through the pucch-Cell field in the PDSCH serving cell configuration. If this field does not exist, the UE can send HARQ feedback on the PUCCH of the SpCell of the cell group, and if it is a PUCCH SCell, send HARQ feedback on the serving cell.

[0128] URLLC: In the 3GPP Rel-15 specification, basic support for URLLC introduces a low-latency TTI structure and methods to improve reliability. In addition to the use cases that require enhancements to enable Rel-15, other use cases with more stringent requirements have been identified as important for NR evolution. In some implementations, the following use cases can be considered:

[0129] Rel-15 supports use case improvements, such as in the entertainment industry (e.g., AR and / or VR).

[0130] New Rel-16 use cases with higher requirements, such as factory automation, transportation (e.g., remote driving use cases), and power distribution.

[0131] Here are some solutions to the problems.

[0132] Providing HARQ latency reduction using CA in unpaired spectrum

[0133] Since only a few UL symbols can be used to transmit HARQ-ACK information in a heavy DL TDD configuration, it may be difficult to meet the low latency requirements of URLLC scenarios. Although different serving cells may have different UL / DL modes, only one PUCCH can be transmitted on the configured serving cell in a PUCCH cell group. In other words, PUCCH transmission can be semi-statically configured in a specific serving cell, and its latency may be highly dependent on the UL / DL mode of the serving cell because the related dynamic PUCCH carrier switching is not yet available. Therefore, it is very important to implement dynamic PUCCH carrier switching through an appropriate solution.

[0134] In one embodiment, the list of serving cells used with a PUCCH may be configured by higher layers, and a DCI field may be used to indicate which serving cell the PUCCH is transmitted on. In another embodiment, the list of serving cells used with a PUCCH may be configured by higher layers, and a MAC CE may be used to indicate which serving cell the PUCCH is transmitted on. In another embodiment, the UE capability of supporting dynamic PUCCH carrier switching may be reported, and a DCI field may be used to indicate which serving cell the PUCCH is transmitted on. In another embodiment, the UE capability of supporting dynamic PUCCH carrier switching may be reported, and a MAC CE may be used to indicate which serving cell the PUCCH is transmitted on. In another embodiment, a MAC CE may be used to indicate the activation / deactivation of one PUCCH carrier per serving cell. In another embodiment, a MAC CE may be used to indicate the PUCCH carrier to be used for PUCCH transmission. In another embodiment, dynamic PUCCH carrier switching may be applied if there are no available PUCCH resources in the timeslot indicated by the HARQ timing indicator. In another embodiment, two types of PUCCH cells may be provided, one of which may be a semi-static type and the other may be a dynamic type.

[0135] HARQ-ACK timing

[0136] The parameter duration K1 between a given PDSCH and HARQ-ACK can be indicated by the PDSCH-to-HARQ timing indicator field in dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2-r16 or the corresponding DCI format, and this field can be mapped to a set of timeslot / subslot values. In addition, the parameter SCS configuration K1 is based on the SCS configuration of the serving cell in which a PUCCH is configured. Therefore, if dynamic PUCCH carrier switching is applied, the reference SCS configuration for the duration K1 may not be clear.

[0137] In one embodiment, the duration between a given PDSCH and the associated PUCCH transmission may apply a reference carrier with SCS configuration μ. In another embodiment, the duration between a given PDSCH and the associated PUCCH transmission may apply a PUCCH carrier with SCS configuration μ1 before dynamic PUCCH carrier switching. In another embodiment, the duration between a given PDSCH and the associated PUCCH transmission may apply a PUCCH carrier with SCS configuration μ2 after dynamic PUCCH carrier switching. In another embodiment, the duration between a given PDSCH and the associated PUCCH transmission may be based on the active BWP in the serving cell with the smallest SCS configuration. In another embodiment, the duration between a given PDSCH and the associated PUCCH transmission may be based on the active BWP in the serving cell with the largest SCS configuration.

[0138] PUCCH carrier switching process

[0139] If the switching point is not clearly defined, dynamic PUCCH carrier switching may have some impact on the PUCCH multiplexing process. For example, if the UE transmits overlapping UL channels in the time domain, the switched PUCCH may become non-overlapping with other channels, so the PUCCH multiplexing process may need to be adjusted.

[0140] In one embodiment, if the UE detects a DCI format that schedules a PUCCH in a first PUCCH carrier that may overlap with another PUCCH / PUSCH, the UE may not expect to switch PUCCH carriers. More specifically, whenever a PUCCH carrier switching indication is received, if an overlapping PUCCH is scheduled, the UE may ignore the PUCCH carrier switching indication. In another embodiment, when the UE decides to resolve the overlap of PUCCH and / or PUSCH transmissions, the UE may check the availability of PUCCH carrier switching in advance. More specifically, the UE may expect to switch PUCCH carriers before resolving the overlapping UL transmissions. In another embodiment, when the UE receives the PUCCH carrier switching indication, it may be a certain and accurate switching point. In another embodiment, when the UE receives the PUCCH carrier switching indication, it may be a switching duration.

[0141] For a more detailed description, dynamic PUCCH carrier switching is introduced below. In one embodiment, the list of serving cells that can be used for transmitting PUCCH can be configured by a higher layer, or / and the DCI field can be used to indicate on which serving cell to send PUCCH. In one example, the lists can correspond to different groups. More specifically, the first list can correspond to the primary PUCCH cell group, and the second list can correspond to the secondary PUCCH cell group. In one example, the list can correspond to a new RRC parameter, for example, a primary PUCCH group list and / or a secondary PUCCH group list. In one example, the list can include the ID of the serving cell. More specifically, list 1 can include serving cell IDs {#0, #2, #4}, and list 2 can include serving cell IDs {#1, #3, #5}. In one example, the list can correspond to a mapping table. More specifically, the first row in the list (e.g., ID 0) can correspond to serving cell ID 1, and the second row (e.g., ID1) can correspond to serving cell ID 3. In one example, the serving cell IDs in each list may be independent. More specifically, the serving cell IDs included in the first list and the serving cell IDs in the second list may be different. For example, List 1 / Group 1 may include serving cell IDs {#0, #1, #3}, and List 2 / Group 2 may include serving cell IDs {#2, #4}. In other words, serving cell IDs #0, #1, and #3 in List 1 may not be configured or included in List 2. In one example, the serving cell IDs in each list may be related. More specifically, the serving cell IDs in the first list and the serving cell IDs in the second list may be the same. For example, List 1 / Group 1 may include serving cell IDs {#0, #1, #3}, and List 2 / Group 2 may include serving cell IDs {#1, #4}. In other words, serving cell ID #1 may be configured or included in both List 1 and List 2. In one example, the DCI field for indicating the switched PUCCH carrier may be a new field in an existing DCI format or a new DCI format. In one example, the DCI field for indicating the switched PUCCH carrier may reuse an existing field in an existing DCI.

[0142] In one embodiment, a list of serving cells that can be used to transmit the PUCCH can be configured by a higher layer and / or a MAC CE can be used to indicate on which serving cell the PUCCH is to be sent. In one example, the MAC CE can include a bit field for the list ID, the group ID, the serving cell ID, and / or the activation / deactivation mode of each serving cell. More specifically, a bitmap of "0" can indicate deactivation, while a bitmap of "1" can indicate activation. Alternatively, a bitmap of "1" can indicate deactivation, while a bitmap of "0" can indicate activation.

[0143] In one embodiment, the UE capability of supporting dynamic PUCCH carrier switching may be reported, parameters related to one PUCCH carrier may be configured, and / or a DCI field may be used to indicate on which serving cell the PUCCH is sent. In one example, a parameter (e.g., dynamicPUCCHswitching-enable) may be used to enable dynamic switching. In addition, if the parameter is configured, a DCI may be used to indicate a specific serving cell on which the PUCCH may be transmitted. In one example, a bit field of the DCI field may correspond to a serving cell ID. More specifically, a bit field of "10" may indicate that one PUCCH carrier is switched to PUCCH cell #2. In one example, a bit field of the DCI field may correspond to a column ID of a mapping table of a list. Further, a bit field of "10" may indicate that one PUCCH carrier is switched to a serving cell corresponding to ID "10". In one example, whether to configure parameters related to PUCCH carrier switching may be determined based on the UE capability. More specifically, the parameter may refer to a list, a PUCCH cell ID, or / and a PUCCH group ID.

[0144] In one embodiment, the UE's ability to support dynamic PUCCH carrier switching can be reported, parameters related to one PUCCH carrier can be configured, and / or a MAC CE can be used to indicate on which serving cell the PUCCH is sent. In one example, a parameter (e.g., dynamicPUCCHswitching-enable) can be used to enable dynamic switching. In addition, if this parameter is enabled, the MAC CE can also be used to further indicate the PUCCH carrier. The MAC CE may include the ID of the serving cell, and / or the activation / deactivation mode of each serving cell. More specifically, bitmap "0" may indicate deactivation, while bitmap "1" may indicate activation. Alternatively, bitmap "1" may indicate deactivation, while bitmap "0" may indicate activation.

[0145] In one embodiment, a MAC CE may be used to indicate the activation / deactivation of a PUCCH carrier. More specifically, an activated carrier may be a carrier on which a PUCCH may be transmitted, and a deactivated carrier may be a carrier that does not transmit any PUCCH (e.g., a PUCCH transmission). In one example, a deactivated PUCCH carrier may not be expected to be scheduled for PUCCH transmission. In one example, a MAC CE may include fields such as a serving cell ID, a BWP ID, and / or an indication of an activation / deactivation field. In one example, a PUCCH carrier included in a MAC CE may be a configured candidate PUCCH carrier. More specifically, at least one activation / deactivation bit may correspond to each candidate PUCCH carrier.

[0146] In one embodiment, the MAC CE may be used to indicate a PUCCH carrier for sending PUCCH transmissions. In one example, the MAC CE may include fields such as a target for switching PUCCH cell ID and / or BWP ID.

[0147] In one embodiment, if the time slot indicated by the HARQ timing indicator has no available resources for PUCCH transmission, dynamic PUCCH carrier switching may be applied. More specifically, if the indicator indicates that PUCCH transmission is to be sent in a time slot without available resources, the first PUCCH carrier may be switched to a second PUCCH carrier with available PUCCH resources. Note that the available resources for PUCCH transmission may be UL symbols, non-collision-free flexible symbols, and / or an appropriate PUCCH format. In one example, dynamic PUCCH carrier switching may be applied only when PUCCH resources for the initial transmission of PUCCH are unavailable. In one example, the first PUCCH carrier may be switched to a second PUCCH carrier within the same PUCCH group with the smallest serving cell ID. More specifically, if the PUCCH group includes serving cell IDs {#0, #1, #3}, then when dynamic switching is initiated, the first PUCCH carrier is serving cell ID #0 and the second PUCCH carrier may be serving cell ID #1. In other words, the order in which PUCCH carrier candidates are selected may depend on the serving cell ID and the PUCCH group. In one example, the first PUCCH carrier can be switched to the second PUCCH carrier corresponding to the smallest serving cell ID, regardless of whether the two carriers are in the same PUCCH group. More specifically, if the first PUCCH group includes serving cell IDs {#0, #2, #3} and the second PUCCH group includes serving cell IDs {#1, #4}, the second PUCCH carrier can be serving cell ID #1 in the second PUCCH group. In other words, the order in which PUCCH carrier candidates are selected may depend on the serving cell ID.

[0148] In one example, the second PUCCH carrier may be determined based on the carrier with the earliest available resources for PUCCH transmission. Figure 1 , which is a schematic diagram showing different carriers with different UL / DL modes according to an embodiment of the present disclosure. Figure 1 In the table, “D” indicates that there are available DL resources, “U” indicates that there are available UL resources, and “F” indicates flexible resources that can be used for UL transmission or DL ​​reception. Figure 1As shown in this exemplary UL / DL pattern with different carriers, if the first PUCCH carrier is carrier #0, the second PUCCH carrier may be carrier #2, because the UL symbols provided in carrier #2 are the earliest available UL resources in all carriers.

[0149] In one example, the second PUCCH carrier may depend on whether subslot configuration is configured. More specifically, if the parameter subslotLengthForPUCCH-r16 is configured in the active BWP for carrier #2 but not carrier #1, the second PUCCH carrier may be carrier #2.

[0150] In one example, the second PUCCH carrier can be determined based on the carrier with the earliest resources available for transmitting PUCCH, and the subslotLengthForPUCCH-r16 in the PUCCH-Config of the active UL BWP of the carrier is the same as the PUCCH-Config of the active UL BWP of the SpCell or the subslotLengthForPUCCH-r16 in the PUCCH-SCell in the same cell group.

[0151] In one example, the second PUCCH carrier may depend on whether more than one PUCCH configuration is configured as PUCCH-Config. More specifically, if the active BWP in the second carrier with PUCCH-ConfigurationList indicates that more than one PUCCH-Config is present, the first PUCCH carrier may be switched to the second carrier.

[0152] In one example, the first PUCCH carrier may be switched to the second PUCCH carrier having the most UL symbols in each cycle. Figure 1 As shown in this exemplary UL / DL pattern with different carriers, the second PUCCH carrier can be carrier #2 because carrier #2 has the most UL symbols in a time slot. In one example, the period can be a time slot, a number of symbols, a number of time slots, an SFI period, a predefined duration, and / or the duration of the TDD-UL-DL-Config.

[0153] In one embodiment, two types of indicated PUCCH cells may be provided, one corresponding to a semi-static type and the other corresponding to a dynamic type. More specifically, a parameter may indicate which type the UE may apply to. If the parameter is set to {semi-static}, the UE may transmit PUCCH on a specific PUCCH cell configured by a higher layer; or, if the parameter is set to {dynamic}, the UE may apply dynamic PUCCH carrier switching (e.g., using at least one DCI).

[0154] In one example, the dynamic type can be configured only when the capability of the UE to support dynamic PUCCH carrier switching is reported. In one example, the dynamic type can be scheduled by a specific DCI format, for example, DCI format 0-1, DCI format 0-2, a new DCI format and / or a DCI format scrambled by a new RNTI. In one example, if the semi-static type is configured, the UE can configure the PUCCH switching configuration, which may include parameters such as PUCCH cell ID, PUCCH cell group, PUCCH cell list, switching timing indication, and / or the enabling of dynamic PUCCH carrier switching. In one example, if the dynamic type is configured, the UE may follow the MAC CE indication and / or DCI indication. Specifically, the switching timing indication may refer to the PUCCH carrier corresponding to each time slot.

[0155] In one embodiment, after switching from a first PUCCH carrier to a second PUCCH carrier, more than one UCI scheduled or configured to be transmitted together with the PUCCH resources of the first PUCCH carrier is transmitted in the PUCCH resources of the second carrier for a period of time until switching from the second PUCCH carrier back to the first PUCCH carrier.

[0156] In one example, after switching from a first PUCCH carrier to a second PUCCH carrier, a HARQ-ACK scheduled for transmission in a PUCCH resource of the first PUCCH carrier is transmitted in a PUCCH resource of the second carrier. After sending the HARQ-ACK, the UE may switch from the second PUCCH carrier back to the first PUCCH carrier.

[0157] For a more detailed description, dynamic PUCCH carrier switching is described below. In one embodiment, the duration between a given PDSCH and the associated PUCCH transmission (e.g., parameter K1) may be based on a reference carrier with SCS configuration μ. More specifically, regardless of which PUCCH carrier is scheduled, the indicated K1 value may be based on a reference carrier with SCS configuration μ. See Figure 2 , is a schematic diagram showing a parameter K1 based on a reference carrier according to an embodiment of the present disclosure. Figure 2 As shown, if the reference carrier is carrier #0, K1 can be "2" to indicate the corresponding PUCCH transmission, even if one PUCCH is transmitted on another carrier with a different SCS configuration.

[0158] In one example, the reference carrier may be configured by a higher layer. More specifically, parameters or / and configuration may be used to indicate the serving cell ID as a reference carrier. In one example, the reference carrier may be indicated by a DCI format corresponding to one PUCCH transmission. More specifically, a field in the DCI may indicate the serving cell ID as a reference carrier, or the serving cell in which the DCI is detected may be used as a reference carrier. In one example, the reference carrier may be indicated by a MAC CE. More specifically, a field in the MAC CE may indicate the serving cell ID as a reference carrier. Alternatively, a dedicated field may be used to indicate whether a reference carrier exists. If this field is set to "1", a reference carrier exists. If this field is set to "0", a reference carrier does not exist. In one example, SpCell and PUCCH-SCell (i.e., the serving cell configured by PUCCH-cell) may always be considered as reference carriers.

[0159] In one embodiment, the first PUCCH carrier may be switched to the second PUCCH carrier. The first PUCCH carrier has an SCS configuration μ1, and the second PUCCH carrier has an SCS configuration μ2. The duration between a given PDSCH and the associated PUCCH transmission may be based on the SCS configuration μ1. Figure 3 , Figure 3 FIG1 is a schematic diagram showing a parameter K1 based on the first carrier according to an embodiment of the present disclosure. Figure 3 As shown, if the first carrier is carrier #0, K1 may be "2" to indicate the corresponding PUCCH transmission, even if one PUCCH is transmitted on a second carrier with a different SCS configuration.

[0160] In one embodiment, a first PUCCH carrier may be switched to a second PUCCH carrier. The first PUCCH carrier uses an SCS configuration μ1, and the second PUCCH carrier uses an SCS configuration μ2. The duration K1 between a given PDSCH and an associated PUCCH transmission may be based on the SCS configuration μ2. More specifically, K1 may be interpreted using the SCS of the target carrier (e.g., the PUCCH carrier after the switch). Figure 3 As shown, if the first carrier is carrier#0 and the second carrier is carrier#1, K1 can be "3" to indicate the corresponding PUCCH transmission. In another embodiment, see Figure 4 , Figure 4FIG1 is a schematic diagram showing a parameter K1 based on the second carrier according to an embodiment of the present disclosure. Figure 4 As shown, if the second carrier is carrier #1, the K1 value can be "4" to indicate the corresponding PUCCH transmission, even if one PUCCH is transmitted on the first carrier with a different SCS configuration.

[0161] In one embodiment, the duration K1 between a given PDSCH and the associated PUCCH transmission may be based on the active BWP in the serving cell with the minimum SCS configuration. Figure 5 , Figure 5 FIG1 is a schematic diagram showing a parameter K1 based on different SCS configurations according to an embodiment of the present disclosure. Figure 5 As shown, K1 may be "5" to indicate the corresponding PUCCH transmission, even if one PUCCH is transmitted on a second carrier with a larger SCS configuration.

[0162] In one embodiment, the duration K1 between a given PDSCH and the associated PUCCH transmission may be based on the active BWP in the serving cell with the maximum SCS configuration. Figure 5 As shown, K1 may be "2" to indicate the corresponding PUCCH transmission, even if one PUCCH is transmitted on a second carrier with a smaller SCS configuration.

[0163] In one embodiment, the duration K1 between a given PDSCH and the associated PUCCH transmission may be based on the SCS of the active BWP in the PUCCH carrier before the handover. When the SCS of the active BWP in the PUCCH carrier after the handover is greater than the SCS of the active BWP in the PUCCH carrier before the handover, if the PUCCH resources do not collide with semi-static DL symbols or symbols used for SSBs, and the PUCCH resource transmission begins after the end of the PDSCH after the duration Tproc,1, then the PUCCH resources of the first UL slot in the PUCCH carrier after the handover and the overlapping UL slot in the PUCCH carrier before the handover indicated by K1 may be used, where Tproc,1 is a parameter defined in TS 38.214 Section 5.3 (in 3GPP). Otherwise, the PUCCH resources of the second UL slot in the PUCCH carrier after the handover and the overlapping UL slot in the PUCCH carrier before the handover indicated by K1 may be used.

[0164] In one embodiment, any of the above embodiments may be configurable and / or dynamically indicated.

[0165] For a more detailed description, the dynamic PUCCH carrier switching process is described below. In one embodiment, if a UE detects a DCI format that schedules a PUCCH in a first PUCCH carrier that overlaps with another PUCCH or PUSCH, the UE may not want to switch PUCCH carriers. More specifically, whenever a switch PUCCH carrier indication is received, if overlapping PUCCH or PUSCH is scheduled, the UE may ignore the switch PUCCH carrier indication even if overlapping UL transmissions should be multiplexed together. In other words, when a PUCCH carrier switch is indicated, the UE may not want to perform UCI multiplexing.

[0166] In one embodiment, when the UE determines that there are overlapping PUCCH transmissions and / or overlapping PUSCH transmissions, the UE may pre-check the availability of switching PUCCH carriers. More specifically, the UE may desire to switch PUCCH carriers before determining overlapping UL transmissions.

[0167] In one embodiment, before determining whether to perform PUCCH carrier switching, the UE may pre-process the UCI multiplexing process to resolve overlapping PUCCH transmissions. If it is determined that a PUCCH resource carries multiplexed UCI that collides with semi-static DL symbols, the UE may perform PUCCH carrier switching to transmit all or part of the multiplexed UCI. After the PUCCH carrier switch, the UE may determine the PUCCH resource to use with the PUCCH carrier based on the payload size of all or part of the multiplexed UCI.

[0168] In one embodiment, a switching point may be formed / exist when the UE receives a PUCCH carrier switching indication. Thus, the multiplexing procedure may be determined by the switching point. In one example, the definition of the switching point may start from the end symbol of the last PDSCH reception, for example, the last candidate PDSCH reception for which the UE may send corresponding HARQ-ACK information. In one example, the definition of the switching point may start from the end symbol of the DCI indicating dynamic PUCCH carrier switching. In one example, the definition of the switching point may start from the start symbol of the DCI indicating dynamic PUCCH carrier switching. In one example, the definition of the switching point may start from the start symbol of the PUCCH transmission. In one example, the UE may expect that the switching point will not start before Tproc,2+d (which is a parameter defined in TS38.214 Section 6.4 (in 3GPP)) after the last symbol of the DCI indicating dynamic PUCCH carrier switching, where "d" may be "0", one symbol, multiple symbols, or an absolute duration. In one example, the UE may expect the switch to begin before Tproc,2+d after the last symbol of the DCI indicating the dynamic PUCCH carrier switch, where "d" can be "0", one symbol, multiple symbols, or an absolute duration. In one example, the UE may expect to resolve overlapping UL transmissions before the switch point. In one example, the UE may not expect to be scheduled for overlapping PUCCH transmissions after receiving a switch indication.

[0169] In one embodiment, whether the UE performs PUCCH carrier switching may depend on whether multiple UCIs with different priorities are multiplexed into a single PUCCH. More specifically, if more than one multiplexed UCI with different priorities is allowed / indicated, PUCCH carrier switching may not be scheduled. Alternatively, if more than one multiplexed UCI with different priorities is allowed / indicated, PUCCH carrier switching may be scheduled.

[0170] In one embodiment, when the UE receives a PUCCH carrier switching indication, a switching duration may exist (or be formed) to delay the operation of the switching indication. During such a switching duration, the UE may not expect scheduled PDCCH reception or UL transmission.

[0171] Please refer to Figure 6 , Figure 6 FIG. 6 is a process 60 performed by a UE for sending on different BWPs according to an embodiment of the present disclosure. Figure 6 As shown, the UE process 60 includes the following actions:

[0172] Action 600: Start.

[0173] Action 602: Receive an RRC message configuring a first PUCCH-Config for a UL BWP of a first cell and a second PUCCH-Config for a UL BWP of a second cell.

[0174] Action 604: Receive a DCI including fields indicating a duration and a handover indication from the first cell.

[0175] Action 606: If the handover indication indicates the second cell, send the PUCCH on the UL BWP of the second cell after receiving the DCI.

[0176] Action 608: End.

[0177] Preferably, actions 602 to 606 of process 60 may be performed by the UE. In some embodiments, the UE may receive an RRC message for configuring a first PUCCH-Config and a second PUCCH-Config in action 602, wherein the first PUCCH-Config is for a UL BWP of a first cell (e.g., a first UL BWP) and the second PUCCH-Config is for a UL BWP of a second cell (e.g., a second UL BWP). In action 604, the UE may receive DCI from the first cell, wherein the DCI may include fields indicating a duration and a handover indication, the handover indication indicating the second cell and enabling the UE to transmit a PUCCH transmission on the UL BWP of the second cell (e.g., the second UL BWP) after receiving the DCI. In action 606, if the handover indication indicates the second cell, the UE may transmit a PUCCH on the UL BWP of the second cell (e.g., the second UL BWP) after receiving the DCI. Certain detailed mechanisms and / or operations of process 60 (e.g., actions 602, 604, and 606) are described in the above paragraphs and are omitted below for brevity.

[0178] In some embodiments, the duration indicates an offset in the time domain between PDSCH and PUCCH transmissions scheduled by the DCI, and the duration is based at least on the SCS configuration for the UL BWP of the second cell (e.g., the second UL BWP). In some embodiments, one of the fields in the DCI further indicates the ID of the second cell as a handover indication. In some embodiments, the first cell is a PCell, the second cell is an SCell, and the first and second cells are in the same PUCCH cell group.

[0179] In some embodiments, process 60 may further configure the UE to transmit a UE capability message to the BS / gNB of the first cell to indicate whether the UE supports sending PUCCH transmissions on the UL BWP of the second cell (e.g., the second UL BWP).

[0180] Please refer to Figure 7 , Figure 7 FIG. 7 is a block diagram showing a node 700 for wireless communication according to an embodiment of the present disclosure. Figure 7 As shown, the node 700 includes a transceiver 706, a processor 708, a memory 702, one or more presentation components 704, and at least one antenna 710. The node 700 may also include a radio frequency (RF) spectrum band module, a BS communication module, a NW communication module, a system communication management module, an input / output (I / O) port, an I / O component, and a power supply ( Figure 7 Each of these components can communicate with each other directly or indirectly via one or more buses 724. The node 700 can be a UE or a BS that performs various functions disclosed herein, for example, Figure 6 .

[0181] The transceiver 706 includes a transmitter 716 (e.g., a transmit / transmit circuit) and a receiver 718 (e.g., a receive / receive circuit) and can be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 706 can be configured to transmit in different types of subframes and time slots, including but not limited to available, unavailable, and flexibly available subframe and time slot formats. The transceiver 706 can be configured to receive data and control channels.

[0182] Node 700 may include a variety of computer-readable media. Computer-readable media may be any available media that node 700 can access, and include volatile (and non-volatile) media and removable (and non-removable) media. By way of example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media may include volatile (and non-volatile) and removable (and non-removable) media implemented according to any method or technology for storing information such as computer-readable information.

[0183] Computer storage media include RAM, ROM, EEPROM, flash memory (or other storage technology), CD-ROM, Digital Versatile Disk (DVD) (or other optical disk storage), magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer storage media does not include propagated data signals. Communication media can generally embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media.

[0184] The term "modulated data signal" may refer to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Any combination of the foregoing disclosures should also be included within the scope of computer-readable media.

[0185] The memory 702 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 702 may be removable, non-removable, or a combination thereof. For example, the memory 702 may include solid-state memory, a hard drive, an optical drive, etc.

[0186] like Figure 7 As shown, the memory 702 may store a computer executable (or readable) program 714 (e.g., software code) that is configured to cause the processor 708 to perform various functions disclosed herein when executed, for example, using reference Figure 6 Alternatively, computer-executable program 714 may not be directly executable by processor 208, but may be configured to cause node 700 (eg, when compiled and executed) to perform the various functions disclosed herein.

[0187] The processor 708 (e.g., having processing circuitry) may include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 708 may include a memory. The processor 708 may process data 712 and computer executable programs 714 received from the memory 702, as well as information received via the transceiver 706, the baseband communication module, and / or the NW communication module. The processor 708 may also process information to be sent to the transceiver 706 for transmission to the NW communication module via the antenna 710 for subsequent transmission to the CN.

[0188] One or more presentation components 704 can present data to a person or other device. Examples of presentation components 704 can include a display device, a speaker, a printing component, a vibration component, and the like.

[0189] In light of the present disclosure, it will be apparent that various techniques may be used to implement the disclosed concepts without departing from the scope of those concepts. Furthermore, although these concepts have been disclosed with specific reference to specific embodiments, those skilled in the art will recognize that changes may be made in form and detail without departing from the scope of these concepts. Therefore, the disclosed embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the specific disclosed embodiments. Many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A method, performed by a user equipment (UE), for performing PUCCH transmission on different bandwidth parts (BWPs) of different physical uplink control channel (PUCCH) cells, the method comprising: receiving a radio resource control (RRC) message configuring a first physical uplink control channel configuration (PUCCH-Config) for a first uplink (UL) BWP of a primary PUCCH cell and a second PUCCH-Config for a second UL BWP of a secondary PUCCH cell; receiving downlink control information (DCI) from the primary PUCCH cell, the DCI comprising a plurality of fields for indicating a duration and indicating switching of PUCCH transmission between the primary PUCCH cell and the secondary PUCCH cell, wherein the duration indicates an offset value between transmission of a physical downlink shared channel (PDSCH) and a hybrid automatic repeat request (HARQ)-ACK on a PUCCH scheduled by the DCI in the time domain; as well as When the multiple fields indicate that the PUCCH transmission is switched from the primary PUCCH cell to the secondary PUCCH cell, sending the PUCCH including the HARQ-ACK on the second UL BWP of the secondary PUCCH cell after receiving the DCI, The primary PUCCH cell and the secondary PUCCH cell are in the same PUCCH cell group.

2. The method according to claim 1, wherein The duration is based at least on a subcarrier spacing (SCS) configuration of the second UL BWP.

3. The method according to claim 1, wherein The method further comprises: A UE capability message is sent to indicate whether the UE supports sending the PUCCH on the second UL BWP after receiving the DCI.

4. The method according to claim 1, wherein One of the multiple fields of the DCI further indicates an index ID of the secondary PUCCH cell as a handover indication.

5. A user equipment (UE) for performing PUCCH transmission on different bandwidth parts (BWPs) of different physical uplink control channel (PUCCH) cells in a wireless communication system, the UE comprising: processor; and a memory coupled to the processor, wherein the memory stores a computer-executable program that, when executed by the processor, causes the processor to: receiving a radio resource control (RRC) message configuring a first physical uplink control channel configuration (PUCCH-Config) for a first uplink (UL) BWP of a primary PUCCH cell and a second PUCCH-Config for a second UL BWP of a secondary PUCCH cell; receiving downlink control information (DCI) from the primary PUCCH cell, the DCI comprising a plurality of fields for indicating a duration and indicating switching of the PUCCH transmission between the primary PUCCH cell and the secondary PUCCH cell, wherein the duration indicates an offset value between transmission of a physical downlink shared channel (PDSCH) and a hybrid automatic repeat request (HARQ)-ACK on the PUCCH scheduled by the DCI in the time domain; and When the multiple fields indicate that the PUCCH transmission is switched from the primary PUCCH cell to the secondary PUCCH cell, sending the PUCCH including the HARQ-ACK on the second UL BWP of the secondary PUCCH cell after receiving the DCI, The primary PUCCH cell and the secondary PUCCH cell are in the same PUCCH cell group.

6. The UE according to claim 5, wherein The duration is based at least on a subcarrier spacing (SCS) configuration of the second UL BWP.

7. The UE according to claim 5, wherein: When executed by the processor, the computer executable program further causes the processor to: A UE capability message is sent to indicate whether the UE supports sending the PUCCH on the second UL BWP after receiving the DCI.

8. The UE according to claim 5, wherein: One of the multiple fields of the DCI further indicates an index ID of the secondary PUCCH cell as a handover indication.

Images