WIRELESS COMMUNICATION METHOD AND USER EQUIPMENT FOR TRANSMISSION IN PARTS OF DIFFERENT BANDWIDTH

Abstract

A wireless communication method, implemented by a user team, for transmission in different Bandwidth Parts (BWPs) includes receiving a Radio Resource Control (RRC) message that configures a first physical uplink control channel configuration (PUCCH-Config) for an uplink bandwidth (UL) part of a first cell and a second PUCCH configuration for a BWP UL of a second cell; receiving, from the first cell, Downlink Control Information (DCI) that includes fields to indicate a duration and a switch indication; and transmitting a PUCCH in the BWP UL of the second cell after receiving the DCI if the switch indication points to the second cell.

Description

WIRELESS COMMUNICATION METHOD AND USER EQUIPMENT FOR TRANSMISSION IN PARTS OF DIFFERENT BANDWIDTH i1 «enn / eznz / E / YiAi Field of Invention The present description is generally related to wireless communications, and specifically, to a wireless communication method and user equipment for transmission in different Bandwidth Parts (BWP). Background of the Invention With the tremendous growth in the number of connected devices and the rapid increase in user / network (NW) traffic volume, various efforts have been made to improve different aspects of wireless communication for the next generation wireless communication system, such as fifth generation (5G) New Radio (NR), by improving data speed, latency, reliability, and mobility. The NR 5G system is designed to offer flexibility and configurability in order to optimize services and NW types, accommodating various use cases such as Enhanced Mobile Broadband (eMBB), Mass Machine-Type Communication (mMTC), and Ultra Reliable Low Latency Communication (URLLC). Ref. 341691 However, as the demand for radio access increases, the need arises in the technique to perform transmissions in different Bandwidth Parts (BWP). Brief Description of the Invention This description is directed to user methods and equipment (UE) for transmission in Different Bandwidth Parts (BWP). In the first aspect of this description, a method implemented by a user team (UE) for transmission across different Bandwidth Parts (BWPs) is provided. The method includes receiving a Radio Resource Control (RRC) message that configures a First Physical Uplink Control Channel (PUCCH-Config) for the uplink BWP (UL) of a first cell and a second PUCCH-Config for the UL BWP of a second cell; receiving, from the first cell, Downlink Control Information (DCI) that includes fields to indicate a duration and a switchover indication; and transmitting a PUCCH on the UL BWP of a second cell after receiving the DCI if the switchover indication points to the second cell. In another implementation of the first aspect, the duration is based on at least one Subcarrier Spacing (SCS) configuration of the BWP UL of a second cell and indicates an offset value between a DCI-scheduled Physical Downlink Shared Channel (PDSCH) and the PUCCH transmission in the time domain. Another implementation of the first aspect also involves transmitting a UE capability message to indicate whether the UE supports transmitting the PUCCH in the BWP UL of a second cell after receiving the DCI. In another implementation of the first aspect, one of the DCI fields also indicates an index (ID) of the second cell as a switching indication. 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 within the same PUCCH cell group. In a second aspect of the present description, a user equipment (UE) is provided in a wireless communication system for transmission in different Bandwidth Parts (BWP). The UE includes a processor and a memory coupled to the processor, wherein the memory stores a computer executable program which, when executed by the processor, causes the processor to receive a Radio Resource Control (RRC) message that configures a first physical uplink control channel (PUCCH i1 «enn / eznz / E / YiAi). Config) for an Uplink (UL) BWP of a first cell and a second PUCCH-Config for a second BWP UL of a second cell; receive, from the first cell, Downlink Control Information (DCI) which includes fields to indicate a duration and a switching indication; and transmit a PUCCH on the BWP UL of a second cell after receiving the DCI if the switching indication points to the second cell. Brief Description of the Figures The aspects of this description are best understood when read in conjunction with the accompanying figures. Several features are not drawn to scale. The dimensions of various features may be arbitrarily enlarged or reduced for clarity of discussion. Figure 1 illustrates a schematic diagram for different carriers with different UL / DL patterns according to an implementation of the present description. Figure 2 illustrates a schematic diagram of the parameter K1 based on the reference carrier according to one modality of the present description. Figure 3 illustrates a schematic diagram for the parameter K1 based on the first carrier according to one modality of the present description. Figure 4 illustrates a schematic diagram for the parameter K1 based on the second carrier according to an i1 «enn / eznz / E / YiAi modality of the present description. Figure 5 illustrates a schematic diagram of the K1 parameter based on different SCS configurations according to one modality of the present description. Figure 6 illustrates a procedure for transmitting in different BWPs performed by a UE according to an implementation of the present description. Figure 7 illustrates a block diagram of a node for wireless communication according to an implementation of the present description. Detailed Description of the Invention The acronyms in this description are defined as follows. Unless otherwise specified, the acronyms have the following meanings. i1 fienn / eznz / E / YiAi Acronym Full Name 3GPP 3rd Generation Partnership Project 5G 5th Generation ACK Acknowledgement AR Augmented Reality BS Base Station BWP Part of Bandwidth CA Carrier Aggregation CC Carrier Component CE Control Element CN Core Network C-RNTI Cellular Radio Network Temporary Identifier DAT Downlink Assignment Index CC Dual Connectivity DCI Downlink Control Information DL Downlink FR1 / 2 Frequency Range 1 / 2 GC-PDCCH Common Physical Downlink Control Channel 1'enn / eznz / E / YiAi group gNB g Node B HARQ Hybrid Auto-Repeat Request ID Index IE Information Element IIoT Industrial Internet of Things LSB Least Significant Bit LTE Long-Term Evolution L1 Layer 1 MAC Media Access Control MCG Master Cell Group MCS-C-RNTI Modulation Coding Scheme-Identifier Temporary MIMO radio network Multi-input Multi-output MSB Most significant bit NACK Negative acknowledgment IDN New data indicator NR New Radio NW Network PCell Primary Cell PSCell Secondary Primary Cell PBCH Physical Broadcast Channel 5 PDCCH Physical Downlink Control Channel PDSCH Physical Shared Downlink Channel PUCCH Physical Uplink Control Channel PUSCH Physical Shared Uplink Channel PDU Protocol Data Unit 10 PHY Physical PTAG Primary Synchronization Advance Group RAN Radio Access Network Rei Release RMSI Minimum Remaining System Information 15 RNTI Radio Network Temporary Identifier RRC Radio Resource Control RV Redundancy Version SCell Secondary Cell SCG Secondary Cell Group 20 SCS Subcarrier Spacing SFI Slot Format Indicator SI System Information SpCell Special Cell SLIV Start Indicator Value and Length 25 SPS Semi-Persistent Scheduling i1 βρηη / ρζηζ / Ε / γίΛΐ SR Scheduling Request SRS Reference Beep SSB Synchronization Signal Block STAG Secondary Synchronization Lead Group SUL Supplementary Uplink TAG Synchronization Lead Group TB Transport Block TBS Transport Block Size TCI Transmission Configuration Indicator TDD Time Division Duplex TR Technical Report TS Technical Specification TTI Transmission Time Interval TX Transmission UCI Uplink Control Information UE User Equipment UL Uplink UL-SCH Uplink Shared Channel URLLC Ultra Reliable Low Latency Communication USS UE GT Specific Search Space Workgroup WI Work Element QCL Quasi-Location The following contains implementation-specific information for this description. «enn / eznz / E / YiAi The figures and accompanying detailed information refer to illustrative implementations only. However, this description is not limited to these illustrative implementations. Skilled workers may find other variations and implementations of this description. Unless otherwise indicated, similar or corresponding elements among the figures may be indicated by similar or corresponding reference numbers. Furthermore, the figures and illustrations in this description are generally not to scale and are not intended to correspond to actual relative dimensions. For consistency and ease of understanding, similar features are identified (although not illustrated in some examples) by numbers in the example figures. However, the features of different implementations may differ in other aspects and are therefore not strictly limited to what is illustrated in the figures. References to "1 implementation," "an implementation," "example implementation," "several implementations," "some implementations," "implementations of this description," etc., may indicate that the implementation(s) of this description may include a particular feature, structure, or characteristic, but not all possible implementations of this description necessarily include that particular feature, structure, or characteristic. Furthermore, repeated use of the phrases "in 1 implementation," "in an example implementation," or "an implementation" does not necessarily refer to the same implementation, although it may.Furthermore, any use of phrases such as implementations in relation to this description is not intended to characterize that all implementations of this description must include the particular feature, structure, or characteristic, and should instead be understood to mean that at least some implementations of this description include the indicated feature, structure, or characteristic. The term "coupled" is defined as connected, either directly or indirectly through intermediate components, and is not necessarily limited to physical connections. The term "comprising," when used, means that it includes, but is not necessarily limited to; it specifically indicates open inclusion of, or membership in, the combination, group, series, and equivalents described. The term "and / or" is simply an association relation used to describe associated objects, and it represents that three relationships can exist. For example, A and / or B can represent that: A exists alone, A and B exist simultaneously, and B exists alone. A and / or B and / or C can represent that at least one of A, B, and C exists. Furthermore, the character / generally indicates that the first and second associated objects are in an "or" relationship. Furthermore, by way of non-exhaustive explanation, specific details such as functional entities, techniques, protocols, standards, and the like are provided to facilitate understanding of the described technology. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, and the like are omitted to avoid obscuring the present description with unnecessary details. Those skilled in the field will immediately recognize that any function or algorithm described herein can be implemented using hardware, software, or a combination of both. The functions described may correspond to modules that can be software, hardware, firmware, or any combination thereof. The software implementation may comprise computer-executable instructions stored on computer-readable media, such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communications processing capabilities can be programmed with the corresponding executable instructions and perform the described NW function(s) or algorithm(s). The microprocessors or general-purpose computers can consist of application-specific integrated circuits (ASICs), programmable logic arrays, and / or use one or more digital signal processors (DSPs). Although some of the example implementations in this description are directed to software installed and running on computer hardware, alternative example implementations implemented as firmware or as hardware or a combination of hardware and software are within the scope of this description. Computer-readable media includes, but is 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 cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions. A radio communication NW architecture (for example, an LTE system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system) typically includes at least one BS, minus one UE, and one or more optional NW elements that provide a connection to a NW. The UE communicates with the NW (for example, a CN, an Evolved Packet Core (EPC) NW, an Evolved Universal Terrestrial Radio Access (E-UTRAN) NW, a Next Generation Core (NGC), a 5G Core Network (5GC), or the Internet) via a RAN established by the BS. It should be noted that, in this description, a UE may include, among other things, a mobile station, terminal, or mobile device, or a user communication radio terminal. For example, a UE may be a portable radio, including, but not limited to, a mobile phone, tablet, wearable device, sensor, or personal digital assistant (PDA) with wireless communication capabilities. The UE is configured to receive and transmit signals over an air interface to one or more cells in a RAN. A BS may include, among others, a Node B (NB) as in the Universal Mobile Telecommunications System (UMTS), an evolved Node B (en) as in LTE-A, a Radio NW Controller (RNC) as in UMTS, a Base Station Controller (BSC) as in the Global System for Mobile Communications (GSM) / Enhanced Data Rate Radio Access NW for GSM Evolution Network (EDGE) (GERAN), a Next Generation eNB (ng-eNB) as in an E-UTRA BS connected to 5GC, a gNB as in the 5G Access NW (5G-AN), and any other device capable of controlling radiocommunication and managing the Radio resources within a cell. The BS can connect to serve one or more UEs via a radio interface with the NW. A base station (BS) can be configured to provide communication services in accordance with at least one of the following Radio Access Technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (often referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS (often referred to as 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, Enhanced LTE (eLTE), NR (often referred to as 5G), and LTE-A Pro. However, the scope of this description should not be limited to the protocols described above. The base station (BS) can be operational to provide i1 radio coverage to a specific geographic area using a plurality of cells included in the regional area network (RAN). The BS can support cell operations. Each cell can serve at least one unit within its radio coverage. More specifically, each cell (often referred to as a service cell) can provide services to one or more units within its radio coverage (for example, each cell schedules downlink (DL) and optionally uplink (UL) resources to at least one unit within its radio coverage for DL ​​and optionally UL packet transmissions). The BS can communicate with one or more units in the radio system across the plurality of cells. A cell can allocate sidelink (SL) resources to support proximity service (ProSe). Each cell can have coverage areas that overlap with other cells. In Multi-RAT Dual Connectivity (MR-DC), the primary cell of an MCG or SCG may be referred to as a SpCell. A PCell may refer to the SpCell of an MCG. A PSCell may refer to the SpCell of an SCG. MCG refers to a group of server cells associated with the Master Node (MN), comprising the SpCell and, optionally, one or more SCells. SCG refers to a group of server cells associated with the Secondary Node (SN), comprising the SpCell and, optionally, one or more SCells. i1 «enn / eznz / E / YiAi In some implementations, the UE may not have RRC (LTE / NR) connections with the corresponding server cells of the associated services. In other words, the UE may not have UE-specific RRC signaling exchange with the server cell. Instead, the user equipment can only monitor DL ​​synchronization signals (e.g., DL synchronization burst sets) and / or SI broadcasting related to the corresponding services from such server cells. Additionally, the UE may have at least one service cell on one or more target SL frequency carriers for the associated services. In some other implementations, the UE may consider the RAN that configures one or more of the service cells as a service RAN. As described above, the NR framework supports flexible configurations to accommodate various next-generation communication requirements (e.g., 5G), such as eMBB, mMTC, and URLLC, while meeting requirements for high reliability, high data rates, and low latency. OFDM technology, as described in 3GPP, can serve as the basis for an NR waveform. Scalable OFDM numerology, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. Furthermore, two coding schemes are considered for NR: (1) Low-Density Parity Check (LDPC) code and (2) polar code. The coding scheme can be adapted based on channel conditions and / or service applications. It is also considered that a single NR frame's transmission time interval must include at least DL transmission data, a guard period, and UL transmission data. The corresponding portions of the DL transmission data, guard period, and UL transmission data must also be configurable, for example, based on NR's dynamic NW. Furthermore, SL resources can also be provided within an NR frame to support ProSe services. The following are some technical terms: HARQ: A functionality can guarantee delivery between peer entities at Layer 1 (i.e., the PHY Layer). A single HARQ process can support one TB when the PHY Layer is not configured for DL / UL spatial multiplexing. When the PHY Layer is configured for DL / UL spatial multiplexing, a single HARQ process can support one or multiple TBs. There can be one HARQ entity per service cell. Each HARQ entity can simultaneously support (number) HARQ DL and UL processes. PUCCH: In the 3GPP NR Rel-15 and Rel-16 specification, the NW can configure a PUCCH-Config parameter in at least one non-initial BWP for a SpCell and a PUCCH SCell, where i1 «enn / eznz / E / YiAi PUCCH SCell refers to a cell group configured with a PUCCH. If supported by the UE, the NW can configure at most one additional SCell from a cell group using PUCCH-Config, where a PUCCH configuration can be set up for a BWP of the normal UL or SUL of a server cell. If the UE is configured with the SUL, the NW can only configure one PUCCH in the BWPs of one of the ULs (e.g., normal UL or SUL). In other words, the PUCCH can be transmitted in a service cell of a PUCCH cell group. If the UE is configured with a PUCCH cell, the UE can apply the corresponding PUCCH transmission to both a primary and a secondary PUCCH group. Additionally, the NW can configure a server cell ID from the same cell group to be used for the PUCCH using a pucch-Cell field in PDSCHServingCellConfig.If the field is missing, the UE can send HARQ feedback in the PUCCH of the SpCell of this cell group, or in this server cell if it is a PUCCH SCell. URLLC: The 3GPP Rel-15 specification introduces basic support for URLLC with TTI structures for low latency, as well as methods to improve reliability. Other use cases with more stringent requirements have been identified as important for the evolution of NR, in addition to the need to improve the use cases enabled by Rel-15. In some implementations, the following use cases may be considered: - Rel-15 enabled improvements in use cases, such as the entertainment industry (e.g., AR and / or VR). - New Rel-16 use cases with higher requirements, such as factory automation, the transport industry (e.g., remote driving use case) and electric power distribution. The following are some problems with solutions. Reduction of HARQ latency with AC in unpaired spectrum Since only a few UL symbols are available to transmit HARQ-ACK information in a heavy-DL TDD configuration, meeting the low-latency requirement of a URLLC scenario can be challenging. Although different server cells may have different UL / DL patterns, only one PUCCH can be transmitted in a server cell configured within a PUCCH cell group. In other words, PUCCH transmission can be configured semi-statically in a specific service cell, and its latency can be highly dependent on the UL / DL patterns of the service cell, as the associated dynamic PUCCH carrier switching is not yet available. Therefore, achieving dynamic PUCCH carrier switching with appropriate solutions is crucial. In one implementation, the server cell lists for use with a PUCCH can be configured by a higher layer, and a DCI field can be used to indicate in which server cell the PUCCH is transmitted. In another implementation, the server cell lists for use with a PUCCH can be configured by a higher layer, and a CE MAC can be used to indicate in which server cell the PUCCH is transmitted. In another implementation, a UE capability can be advertised to support dynamic PUCCH carrier switching, and a DCI field can be used to indicate in which service cell the PUCCH is transmitted. In another implementation, a UE capability can be advertised to support dynamic PUCCH carrier switching, and a CE MAC can be used to indicate in which service cell the PUCCH is transmitted. In another implementation, a CE MAC can be used to indicate the activation / deactivation of a PUCCH carrier in each service cell.In another implementation, a MAC CE can be used to indicate the PUCCH carrier for PUCCH transmission. In another implementation, if a slot indicated by a HARQ timing indicator has no available PUCCH resource(s), dynamic PUCCH carrier switching can be applied. In yet another implementation, two types of PUCCH cells can be provided, one of which can be semi-static and the other dynamic. HARQ-ACK Timing A duration parameter K1 between a given PDSCH and HARQ-ACK can be indicated by dl-DataToUL-ACK or dii1 «enn / eznz / E / YiAi DataToUL-ACK-DCI-l-2-rl6 or a PDSCH-to-HARQ timing indicator field in a corresponding DCI format, and the field can be assigned values ​​for a set of a number of slots / subslots. Furthermore, an SCS configuration parameter K1 is based on the SCS configuration of the server cell in which a PUCCH is configured. Therefore, if PUCCH dynamic carrier switching is applied, a reference SCS configuration for the K1 duration may not be clear. In one implementation, the duration between a given PDSCH transmission and an associated PUCCH transmission can be based on a reference carrier with SCS configuration μ. In another implementation, the duration between a given PDSCH transmission and an associated PUCCH transmission can be based on the PUCCH carrier with SCS configuration μA before dynamic PUCCH carrier switching. In yet another implementation, the duration between a given PDSCH transmission and an associated PUCCH transmission can be based on the PUCCH carrier with SCS configuration μ2 after dynamic PUCCH carrier switching. In another implementation, the duration between a given PDSCH transmission and an associated PUCCH transmission can be based on an active BWP in the server cell with a smaller SCS configuration. In another implementation, the duration between a given PDSCH transmission and an associated PUCCH transmission can be based on an active BWP in the service cell with a larger SCS configuration. jt «enn / eznz / E / YiAi PUCCH Carrier Switching Procedure Dynamic PUCCH carrier switching can impact a PUCCH multiplexing procedure if the definition of a switching point is unclear. For example, if a UE transmits overlapping UL channels in a time domain, the switched PUCCH may no longer overlap with other channels, and consequently, the PUCCH multiplexing procedure may need to be adjusted. In one implementation, if a UE detects a DCI format scheduling a PUCCH on a first PUCCH carrier that may overlap with another PUCCH / PUSCH, the UE may not wait to switch the PUCCH carrier. More specifically, whenever a PUCCH carrier switch indication is received, the UE may ignore it if the overlapping PUCCH is scheduled. In another implementation, when a UE determines to resolve the overlap for PUCCH and / or PUSCH transmissions, the UE may check the availability of PUCCH carrier switching in advance. More specifically, the UE may wait to switch a PUCCH carrier before resolving the overlapping UL transmissions. In another implementation, when a UE receives a PUCCH carrier switch indication, it may represent a definitive and exact switching point. In yet another implementation, when a UE receives a PUCCH carrier switch indication, it may represent a switching duration. i1 «enn / eznz / E / YiAi For more detailed descriptions, PUCCH dynamic carrier switching is introduced below. In one implementation, the server cell lists for use with a PUCCH can be configured by an upper layer, and / or a DCI field can be used to indicate on which server cell the PUCCH is transmitted. In one example, the list can correspond to different groups. More specifically, a first list can correspond to a primary PUCCH cell group, and a second list can correspond to a secondary PUCCH cell group. In one example, a list can correspond to a new RRC parameter, for example, primary PUCCH group list and / or secondary PUCCH group list. In one example, the lists can include server cell IDs. More specifically, list 1 can include server cell ID {#0, #2, #4}, and list 2 can include server cell ID {#0, #2, #4}. and list 2 may include the server cell ID {#1, #3, #5}.In one example, the list might correspond to an assignment table. More specifically, the first row (e.g., ID 0) of the table might correspond to server cell ID 1, and the second row (e.g., ID1) might correspond to server cell ID 3. In one example, the server cell IDs in each list might be independent. More specifically, the server cell ID included in the first list and the server cell ID in the second list might not be the same. For example, list 1 / group 1 might include server cell ID {#0, #1, #3} and list 2 / group 2 might include server cell ID {#2, #4}. In other words, server cell IDs #0, #1, and #3 from list 1 may not be configured or included in list 2. For example, the server cell IDs in each list may be dependent.More specifically, the server cell ID in the first list and the server cell ID in the second list can be the same. For example, list 1 / group 1 might include server cell IDs {#0, #1, #3}, and list 2 / group 2 might include server cell IDs {#1, #4}. In other words, service cell ID #1 can be configured or included in both list 1 and list 2. In one example, the DCI field used to indicate the switched PUCCH carrier can be a new field in an existing DCI format or a new DCI format. Alternatively, the DCI field used to indicate the switched PUCCH carrier can reuse an existing field in an existing DCI. In one implementation, the lists of server cells for use with a PUCCH can be configured by the upper layer and / or a MAC CE can be used to indicate on which server cell the PUCCH is transmitted. For example, the MAC CE might include bit fields for a list ID, a group ID, a server cell ID, and / or the enable / disable mode for each server cell. More specifically, a bitmap of 0 can indicate disable, and a bitmap of 1 can indicate enable. Alternatively, a bitmap of 1 can indicate disable, and a bitmap of 0 can indicate enable. In an implementation, a UE capability to support dynamic PUCCH carrier switching can be reported, a parameter related to a PUCCH carrier can be configured, and / or a DCI field can be used to indicate in which service cell the PUCCH is transmitted. For example, a parameter (e.g., `dynamicPUCCHswitchingenable`) can be used to enable dynamic switching. Furthermore, if the parameter is configured, the DCI can be used to indicate the specific service cell in which the PUCCH can be transmitted. For example, the bit field of the DCI field might correspond to the service cell ID. More specifically, a bit field of 10 might indicate that a PUCCH carrier switches to PUCCH cell #2. Alternatively, the bit field of the DCI field might correspond to the row ID of an allocation table for the list. More specifically, a bit field of 10 might indicate that a PUCCH carrier switches to a service cell corresponding to ID 10.In one example, whether or not the parameter related to PUCCH carrier switching is configured can be determined based on the UE's capacity. More specifically, the parameter can refer to a list, a PUCCH cell ID, or a PUCCH group ID. jt «enn / eznz / E / YiAi In an implementation, the UE's ability to support dynamic PUCCH carrier switching can be reported, a parameter related to a PUCCH carrier can be configured, and / or a MAC CE can be used to indicate which service cell transmits the PUCCH. For example, a parameter (e.g., `dynamicPUCCHswitchingenable`) can be used to enable dynamic switching. Furthermore, if the parameter is enabled, the MAC CE can be used to further indicate the PUCCH carrier. The MAC CE can include the server cell ID and / or the enable / disable mode for each server cell. More specifically, a bitmap of 0 can indicate disable, and a bitmap of 1 can indicate enable. Alternatively, a bitmap of 1 can indicate disable, and a bitmap of 0 can indicate enable. In an implementation, a MAC CE can be used to indicate the activation / deactivation of a PUCCH carrier. More specifically, the activated carrier can be the carrier on which the PUCCH can be transmitted, and the deactivated carrier can be the carrier that does not transmit any PUCCH (e.g., PUCCH transmission). In an example, a deactivated PUCCH carrier might not be scheduled for a PUCCH transmission. In an example, the MAC CE might include fields such as server cell ID, BWP ID, and / or activation / deactivation indication field(s). In an example, the PUCCH carrier(s) included in the MAC CE might be the configured candidate PUCCH carrier(s). More specifically, at least one activation / deactivation bit might correspond to each candidate PUCCH carrier. In one implementation, a MAC CE can be used to indicate a PUCCH carrier for transmitting the PUCCH transmission. For example, the MAC CE might include fields such as the target(s) for the PUCCH switching, cell ID, and / or BWP ID. In one implementation, if a slot indicated by a HARQ timing indicator has no available resource for PUCCH transmission, dynamic PUCCH carrier switching can be applied. More specifically, if the indicator shows that the PUCCH transmission must be transmitted in a slot without an available resource, a first PUCCH carrier can switch to a second PUCCH carrier with an available PUCCH resource. Note that a resource available for PUCCH transmission can be UL symbols, collision-free flexible symbols, and / or appropriate PUCCH formats. In one example, dynamic PUCCH carrier switching can only be applied when the PUCCH resource for the initial PUCCH transmission is unavailable. In one example, a first PUCCH carrier can be switched to a second PUCCH carrier within the same PUCCH group with the smallest service cell ID.Specifically, if a PUCCH group includes a server cell ID {#0, #1, #3}, a first PUCCH bearer is server cell ID #0 and a second PUCCH bearer can be server cell ID #1 when dynamic switching begins. In other words, the selection order of candidate PUCCH bearers can depend on the server cell ID and the PUCCH group. For example, a first PUCCH bearer can be switched to a second PUCCH bearer corresponding to the smallest service cell ID, regardless of whether the two bearers are within the same PUCCH group. More specifically, if a first PUCCH group includes service cell IDs {#0, #2, #3} and a second PUCCH group includes service cell IDs {#1, #4}, the second PUCCH bearer can be serving cell ID #1 in the second PUCCH group. In other words, the selection order of candidate PUCCH carriers may depend on the service cell ID. In one example, the second PUCCH carrier can be determined based on the carrier with the earliest available resource for PUCCH transmission. See Figure 1, which illustrates a schematic diagram for different carriers with different UL / DL patterns according to one implementation of the present description. In Figure 1, D represents that one or more DL resources are available, U represents that one or more UL resources are available, and F represents flexible resources that can be used for either UL transmission or DL ​​reception. As shown in Figure 1 with such exemplary UL / DL patterns of different carriers, if a first PUCCH carrier is carrier #0, then a second PUCCH carrier can be carrier #2 since the UL symbol on carrier #2 is the earliest available UL resource among all carriers. In one example, the second PUCCH carrier can depend on whether a subslot configuration is in place. More specifically, if a subslotLengthForPUCCH-rl6 parameter is configured in an active BWP for carrier #2 instead of carrier #1, the second PUCCH carrier can be carrier #2. In one example, the second PUCCH carrier can be determined based on a carrier with the earliest available resource to transmit the PUCCH, and subslotLengthForPUCCHrl6 in PUCCH-Config of the active BWP UL of the carrier is the same as subslotLengthForPUCCH-rl6 in PUCCH-Config of the active BWP UL of the SpCell or as PUCCH-SCell in the same cell group. In one example, the second PUCCH carrier might depend on whether more than one PUCCH configuration is set as PUCCH-Config. More specifically, if an active BWP on the second carrier with PUCCH-ConfigurationList indicates that more than one PUCCH-Config is present, the first PUCCH carrier might switch to the second carrier. jt «enn / eznz / E / YiAi In one example, a first PUCCH carrier can be switched to a second PUCCH carrier with the highest number of UL symbols in each period. As shown in Figure 1 with such exemplary UL / DL patterns from different carriers, a second PUCCH carrier can be carrier#! since carrier#! has the highest number of UL symbols in a slot. In one example, the period can be a slot, a plurality of symbols, a plurality of slots, an SFI periodicity, a predefined duration, and / or the duration of TDD-UL-DL-Config. In one implementation, two types of indicator PUCCH cells can be provided, one of which can correspond to the semi-static type and the other to the dynamic type. More specifically, a parameter can indicate which type the UE can be applied to. If the parameter is set to {semi-static}, the UE can transmit the PUCCH on the specific PUCCH cell configured by the upper layer; alternatively, if the parameter is set to {dynamic}, the user equipment can apply dynamic PUCCH carrier switching (for example, using at least one DCI). In one example, the dynamic type can only be configured if the UE's ability to support dynamic PUCCH carrier switching is reported. In another example, the dynamic type can be programmed by specific DCI format(s), such as DCI format 0-1, DCI format 0-2, a new DCI format i1 "enn / eznz / E / YiAi", and / or a DCI format encoded by a new RNTI. In another example, if the semi-static type is configured, the UE can configure a PUCCH switching configuration, and the configuration can include parameters such as a PUCCH cell ID, a PUCCH cell group, a PUCCH cell list, a switching timing indication, and / or an enable for dynamic PUCCH carrier switching. In another example, if the dynamic type is configured, the UE can follow a MAC CE indication and / or a DCI indication. Specifically, the switching time indication may refer to the corresponding PUCCH carrier for each slot. In an implementation, after switching from a first PUCCH carrier to a second PUCCH carrier, more than one UCI that is programmed or configured to transmit using the PUCCH resources of the first PUCCH carrier is transmitted on the PUCCH resources of the second carrier for a period of time until switching back from the second PUCCH carrier to the first PUCCH carrier. In one example, after switching from the first PUCCH carrier to the second PUCCH carrier, a HARQ-ACK that is scheduled to be transmitted on a PUCCH resource of the first PUCCH carrier is transmitted on a PUCCH resource of the second carrier. Once the HARQ-ACK has been transmitted, the UE can switch back from the second PUCCH carrier to the first PUCCH carrier. i1 «enn / eznz / E / YiAi For more detailed descriptions, dynamic PUCCH carrier switching is introduced below. In one implementation, the duration between a given PDSCH and an associated PUCCH transmission (e.g., parameter K1) can be based on a reference carrier with an SCS configuration of μ. More specifically, regardless of the programmed PUCCH carrier, a specified K1 value can be based on the reference carrier with SCS configuration μ. See Figure 2, which illustrates a schematic diagram for the reference carrier-based parameter K1 according to one implementation of this description. As shown in Figure 2, if the reference carrier is carrier #0, then K1 can be 2 to indicate the corresponding PUCCH transmission, even if a PUCCH is being transmitted on the other carrier with a different SCS configuration. In one example, the reference carrier can be configured by a higher layer. More specifically, a parameter and / or configuration can be used to designate a service cell ID as the reference carrier. In another example, the reference carrier can be indicated by a DCI format corresponding to a PUCCH transmission. More specifically, a field in the DCI can designate a server cell ID as the reference carrier, or the server cell where the DCI is detected can be considered the reference carrier. In another example, the reference carrier can be indicated by a MAC CE; more specifically, a field in the MAC CE can designate a server cell ID as the reference carrier. Alternatively, a specific field can be used to indicate whether the reference cell is present. If this field has a value of 1, the reference carrier ID is present. If this field is 0, the reference carrier is not present.In one example, the SpCell and the PUCCH-SCell (i.e., the service cell configured by PUCCH-cell) can always be considered as the reference cell. In one implementation, a first PUCCH carrier can be switched to a second PUCCH carrier. The first PUCCH carrier has an SCS configuration of μA, and the second PUCCH carrier has an SCS configuration of μ2. The time between a given PDSCH transmission and its associated PUCCH transmission can be based on the SCS configuration of μA. See Figure 3, which illustrates a schematic diagram for the parameter K1 based on the first carrier according to one implementation of the present description. As shown in Figure 3, if the first carrier is carrier #0, then K1 can be 2 to indicate the corresponding PUCCH transmission, even if a PUCCH is transmitted on the second carrier with a different SCS configuration. In one implementation, a first PUCCH carrier can be switched to a second PUCCH carrier. The first carrier i1 «enn / eznz / E / YiAi If the first PUCCH carrier uses the SCS configuration μA, and the second PUCCH carrier uses the SCS configuration μ2, the duration K1 between a given PDSCH transmission and its associated PUCCH transmission can be based on the SCS configuration μ2. More specifically, the SCS of the destination carrier (e.g., the PUCCH carrier after switching) can be used to interpret K1. As shown in Figure 3, if the first carrier is carrier #0 and the second carrier is carrier #!, then K1 can be 3 to indicate the corresponding PUCCH transmission. In another implementation, see Figure 4, which illustrates a schematic diagram for the parameter K1 based on the second carrier according to one implementation of the present description. As shown in Figure 4, if the second carrier is carrier #!, then the value of K1 can be 4 to indicate the corresponding PUCCH transmission, even if a PUCCH is transmitted on the first carrier with a different SCS configuration. In one implementation, the duration K1 between a given PDSCH transmission and an associated PUCCH transmission can be based on an active BWP in the server cell with the smallest SCS configuration. See Figure 5, which illustrates a schematic diagram for the K1 parameter based on a different SCS configuration according to one implementation of the present description. As shown in Figure 5, K1 can be 5 to indicate the transmission of i1 «enn / eznz / E / YiAi corresponding PUCCH, even if a PUCCH is transmitted on the second carrier with a higher SCS configuration. In one implementation, the duration K1 between a given PDSCH transmission and an associated PUCCH transmission can be based on an active BMP in the server cell with the higher SCS configuration. As shown in Figure 5, K1 can be 2 to indicate the corresponding PUCCH transmission, even if a PUCCH is transmitted on the second carrier with the lower SCS configuration. In one implementation, the duration K1 between a given PDSCH transmission and an associated PUCCH transmission may be based on the SCS of the active BWP on the PUCCH carrier before the switchover. When the SCS of the active BWP on the PUCCH carrier after the switchover is greater than the SCS of the active BWP on the PUCCH carrier before the switchover, a PUCCH resource located in a first UL slot on the PUCCH carrier after the switchover and overlapping with the UL slot indicated by K1 on the PUCCH carrier before the switchover may be used, provided that the PUCCH resource does not conflict with semi-static DL symbols or symbols used for SSB, and the PUCCH resource transmission begins after a duration Tproc, 1 from the end of the PDSCH, where Tproc, 1 is a parameter defined in TS 38.214 section 5.3 (of 3GPP).Otherwise, a PUCCH resource located in a second UL slot on the PUCCH carrier after the jt «enn / eznz / E / YiAi switch and overlapping with the UL slot indicated by K1 on the PUCCH carrier before the switch may be used. In an implementation, any of the above implementations can be configured and / or indicated dynamically. For more detailed descriptions, the PUCCH dynamic carrier switching procedure is presented below. In one implementation, if a UE detects a DCI format scheduling a PUCCH on a first PUCCH carrier that overlaps with another PUCCH or a PUSCH, the UE may not expect to switch the PUCCH carrier. More specifically, whenever a PUCCH carrier switching indication is received, the UE may ignore it if the overlapping PUCCH or PUSCH carriers are scheduled, even though the overlapping UL transmissions should be multiplexed together. In other words, the UE may not expect to perform UCI multiplexing when a PUCCH carrier switch is indicated. In one implementation, when the UE determines that there are overlapping PUCCH transmissions and / or overlapping PUSCH transmissions, the UE can check in advance for the availability of the switched PUCCH carrier. More specifically, the UE can wait to switch the PUCCH carrier before determining the overlapping UL transmission(s). In one implementation, before determining whether to perform a PUCCH carrier switch, the UE can resolve overlapping PUCCH transmissions by performing a UCI multiplexing procedure in advance. If it is determined that the PUCCH resource carries multiplexed UCIs that conflict with semi-static DL symbols, the UE can perform a PUCCH carrier switch to transmit all or some of the multiplexed UCIs. After the PUCCH carrier switch, the UE can determine which PUCCH resource to use with the PUCCH carrier based on the payload size of all or some of the multiplexed UCIs. In one implementation, when the UE receives a PUCCH carrier switching indication, a switching point can be formed / exist. Consequently, the multiplexing procedure can be determined by the switching point. For example, the switching point definition can begin from the end symbol of a last PDSCH reception, for instance, the last candidate PDSCH reception for which the UE can transmit the corresponding HARQ-ACK information. Alternatively, the switching point definition can begin from the end symbol of the DCI indicating dynamic PUCCH carrier switching. Another example is that the switching point definition can begin from the start symbol of the DCI indicating dynamic PUCCH carrier switching. Finally, the switching point definition i1 “enn / eznz / E / YiAi” can begin from the start symbol of the PUCCH transmission.In one example, the UE might expect the switchover point not to begin before Tproc, 2 + d, a parameter defined in TS 38,214 Section 6.4 (of 3GPP), and after the last DCI symbol indicating dynamic PUCCH carrier switching, where d can be 0, a single symbol, multiple symbols, or an absolute duration. In another example, the UE might expect the switchover to begin before Tproc, 2 + d after the last DCI symbol indicating dynamic PUCCH carrier switching, where d can be 0, a single symbol, multiple symbols, or an absolute duration. In another example, the UE might expect to resolve overlapping UL transmissions before the switchover point. In yet another example, the UE might not expect overlapping PUCCH transmissions to be scheduled after receiving a switchover indication. In an implementation, whether the UE performs PUCCH carrier switching may depend on whether more than one UCI with different priorities is multiplexed into a single PUCCH. Specifically, if more than one multiplexed UCI with different priorities is permitted / specified, PUCCH carrier switching may not be scheduled. Conversely, if more than one multiplexed UCI with different priorities is permitted / specified, carrier switching may be scheduled. PUCCH. In one implementation, when the UE receives the PUCCH carrier switching indication, a switching duration may exist (or be formed) for the switching indication's operating delay. During this same switching duration, the UE may not expect scheduled PDCCH receives or UL transmits. See Figure 6, which illustrates a procedure 60 for transmitting in different BWPs performed by a UE according to an implementation of this description. As shown in Figure 6, the procedure 60 for the UE includes the following actions: Action 600: Start. Action 602: Receive an RRC message that configures a first PUCCH-Config for a BWP UL of a first cell and a second PUCCH-Config for a BWP UL of a second cell. Action 604: Receive, from the first cell, DCI that includes fields to indicate a duration and a switching indication. Action 606: Transmit a PUCCH on the BWP UL of the second cell after receiving the DCI if the switching indication points to the second cell. Action 608: The End. Preferably, steps 602 to 606 of procedure 60 can be performed by the UE. In some implementations, the UE can receive the RRC message, which is used to configure the first PUCCH-Config and the second PUCCH-Config in step 602. The first PUCCH-Config is used for the BWP UL (e.g., a first BWP UL) of the first cell, and the second PUCCH-Config is used for the BWP UL (e.g., a second BWP UL) of the second cell. In step 604, the UE can receive the DCI of the first cell. The DCI can include fields to indicate the duration and the switching indication. The switching indication refers to the second cell, and the UE is able to transmit the PUCCH transmission on the BWP UL (e.g., a second BWP UL) of a second cell after receiving the DCI.In step 606, if the switching indication points to the second cell, the UE can transmit the PUCCH in the BWP UL (e.g., a second BWP UL) of a second cell after receiving the DCI. Certain detailed mechanisms and / or operations (e.g., actions 602, 604, and 606) of procedure 60 are described in previous paragraphs and are omitted hereafter for brevity. In some implementations, the duration indicates a trade-off between a DCI-scheduled PDSCH and PUCCH transmission in a time domain, and the duration is based on at least one SCS configuration for the BWP UL (e.g., a second BWP UL) of a second cell. In some implementations, one of the DCI fields also indicates a second cell ID as a switching indication. In some implementations, the first cell is a PCell and the second cell is an SCell, and the first and second cells are within the same PUCCH cell group. In some implementations, procedure 60 can further configure the UE to transmit a UE capability message to a BS / gNB of the first cell, in order to indicate whether the UE supports PUCCH transmission on the BWP UL (for example, a second BWP UL) of a second cell. Refer to Figure 7, which illustrates a block diagram of a Node 700 for wireless communication according to one implementation of the present description. As illustrated in Figure 7, 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 communications module, an NW communications module, and a system communications management module, input / output (I / O) ports, I / O components, and a power supply (not explicitly illustrated in Figure 7). Each of these components can be in communication with each other, directly or indirectly, through one or more 724 buses. The 700 node can be a user device or a base station that performs various functions described in this document, for example, with reference to Figure 6. i1 «enn / eznz / E / YiAi The 706 transceiver includes a 716 transmitter (e.g., transmit circuits) and a 718 receiver (e.g., receive circuits) and can be configured to transmit and / or receive time and / or frequency resource partitioning information. The 706 transceiver can be configured to transmit in different types of subframes and slots, including, but not limited to, usable, non-usable, and flexibly usable slot formats. The 706 transceiver can be configured to receive data and control channels. Node 700 can include a variety of computer-readable media. Computer-readable media can be any available medium that Node 700 can access and includes both volatile (and non-volatile) and removable (and non-removable) media. By way of example, and not as a limitation, computer-readable media can include computer storage media and communication media. Computer storage media can include both volatile (and non-volatile) and removable (and non-removable) media implemented using any information storage method or technology that is computer-readable. Computer storage media include RAM, ROM, EEPROM, flash memory (or other memory technology), CD-ROM, digital versatile discs (DVDs) (or other optical disc storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer storage media do not include a propagated data signal. Communication media can typically incorporate computer-readable instructions, data structures, program modules, or other data into a modulated data signal, such as a carrier wave or other transport mechanism, and include any means of delivering information. The term modulated data signal can refer to a signal that has one or more of its characteristics adjusted or changed in such a way that information is encoded into the signal. By way of example, and not as a limitation, communication media can include wired media, such as a wired NW connection or a direct wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above descriptions should also be included within the scope of computer-readable media. Memory 702 can include computer storage media in the form of volatile and / or non-volatile memory. Memory 702 can be removable, non-removable, or a combination of both. For example, memory 702 can include solid-state memory, hard drives, optical discs, 1¡ «enn / eznz / E / YiAi etc. As illustrated in Figure 7, memory 702 can store a computer-executable (or readable) program 714 (e.g., software code) that is configured to, when executed, cause the processor 708 to perform various functions described herein, e.g., with reference to Figure 6. Alternatively, the computer-executable program 714 may not be directly executable by the processor 208, but may be configured to cause the node 700 (e.g., when compiled and executed) to perform various functions described herein. The processor 708 (for example, having processing circuitry) may include an intelligent hardware device, a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 708 may include memory. The processor 708 can process the data 712 and the computer executable program 714 received from memory 702, and the information received through transceiver 706, the baseband communications module, and / or the NW communications module. The processor 708 can also process the information to be sent to transceiver 706 for transmission via antenna 710 to the NW communications module for subsequent transmission to a CN. i1 «enn / eznz / E / YiAi One or more 704 presentation components can present data to a person or another device. Examples of 704 presentation components include a display device, a speaker, a printing component, a vibrating component, etc. It is clear from this description that various techniques can be used to apply the concepts described without departing from their scope. Furthermore, although the concepts have been described with specific reference to concrete implementations, a person with ordinary knowledge of the subject would recognize that changes can be made to the form and details without departing from the scope of these concepts. As such, the implementations described should be considered in all respects as illustrative and not restrictive. It should also be understood that this description is not limited to the particular implementations described. Many rearrangements, modifications, and substitutions are possible without departing from the scope of this description. It is hereby stated that, as of this date, the best method known to the applicant for putting the aforementioned invention into practice is the one that is clear from the present description of the invention.

Claims

1. A method implemented by a user equipment (UE) for transmission in different Bandwidth Parts (BWPs) characterized in that it comprises: receiving a Radio Resource Control (RRC) message that configures a First Physical Uplink Control Channel (PUCCH-Config) for an uplink BWP (UL) of a first cell and a second PUCCH-Config for a second BWP UL of a second cell; receiving, from the first cell, Downlink Control Information (DCI) that includes fields for indicating a duration and a switching indication; and transmitting a PUCCH in the BWP UL of the second cell after receiving the DCI if the switching indication points to the second cell.

2. The method according to claim 1, characterized in that the duration is based on at least one Subcarrier Spacing Configuration (SCS) of the BWP UL of the second cell and indicates an offset value between a Physical Downlink Shared Channel (PDSCH) i1 «enn / eznz / E / YiAi programmed by the DCI and the PUCCH transmission in a time domain.

3. The method according to claim 1, characterized in that it further comprises: transmitting a UE capability message to indicate whether the UE supports transmitting the PUCCH in the BWP UL of the second cell after receiving the DCI.

4. The method according to claim 1, characterized in that one of the IDC fields further indicates an index (ID) of the second cell as a switching indication.

5. The method according to claim 1, characterized in that: 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 within the same group of PUCCH cells.

6. A user equipment (UE) in a wireless communication system for Different Bandwidth Parts (BWP) transmission, characterized in that it comprises: 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 link control channel (PUCCH-Config) for an uplink (UL) BWP of a first cell and a second PUCCH-Config for a BWP UL of a second cell; receive, from the first cell, Downlink Control Information (DCI) including fields for indicating a duration and a switch indication; and transmit a PUCCH on the BWP UL of a second cell after receiving the DCI if the switch indication points to the second cell.

7. The UE according to claim 6, characterized in that the duration is based on at least one Subcarrier Spacing Configuration (SCS) of the BWP UL of a second cell and indicates an offset value between a DCI-programmed Physical Downlink Shared Channel (PDSCH) and the PUCCH transmission in a time domain.

8. The UE according to claim 6, characterized in that the computer executable program, when executed by the processor, further causes the processor to: transmit a UE capability message to indicate whether the UE supports PUCCH transmission in the BWP UL of a second cell after receiving the DCI.

9. The UE according to claim 6, i1 «enn / eznz / E / YiAi» characterized in that one of the IDC fields further indicates an index (ID) of the second cell as a switching indication.

10. The UE according to claim 6, characterized in that: the first cell is a primary cell (PCell), the second cell is a secondary cell (SCell), the first cell and the second cell are within the same group of PUCCH cells.

Images