Physical uplink control channel communication for carrier aggregation

Abstract

Aspects of the disclosure relate generally to wireless communication. In some aspects, a user equipment (UE) can receive a downlink communication associated with a physical uplink control channel (PUCCH) communication. The UE can transmit the PUCCH communication via a secondary component carrier based at least in part on, for example, a primary component carrier not having sufficient uplink resources for transmitting the PUCCH communication. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 143,636, filed January 29, 2021, entitled “PHYSICAL UPLINK CONTROL CHANNEL COMMUNICATION FOR CARRIER AGGREGATION”, and U.S. Non-Provisional Patent Application No. 17 / 649,185, filed January 27, 2022, entitled “PHYSICAL UPLINK CONTROL CHANNEL COMMUNICATION FOR CARRIER AGGREGATION”, which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to technologies and apparatuses for wireless communication and physical uplink control channel communication for carrier aggregation. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies, which enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs) capable of supporting communication for multiple user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, while an "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As will be described in detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, and so on.

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, regional, and even global levels. NR (which can also be referred to as 5G) is a collection of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] In some aspects, a wireless communication method performed by a user equipment (UE) includes receiving downlink communication associated with physical uplink control channel (PUCCH) communication; and transmitting PUCCH communication via a secondary component carrier.

[0008] In some aspects, a wireless communication method performed by a base station includes transmitting downlink communications associated with PUCCH communications; and receiving PUCCH communications via a secondary component carrier associated with a UE.

[0009] In some aspects, a UE for wireless communication includes a memory; and one or more processors coupled to the memory, the one or more processors being configured to: receive downlink communications associated with PUCCH communications; and transmit PUCCH communications via secondary component carriers.

[0010] In some aspects, a base station for wireless communication includes a memory; and one or more processors coupled to the memory, the one or more processors being configured to: transmit downlink communications associated with PUCCH communications; and receive PUCCH communications via a secondary component carrier associated with a UE.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive downlink communications associated with PUCCH communications; and transmit PUCCH communications via a secondary component carrier.

[0012] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: transmit downlink communications associated with PUCCH communications; and receive PUCCH communications via a secondary component carrier associated with a UE.

[0013] In some aspects, an apparatus for wireless communication includes components for receiving downlink communications associated with PUCCH communications; and components for transmitting PUCCH communications via a secondary component carrier.

[0014] In some aspects, an apparatus for wireless communication includes components for transmitting downlink communications associated with PUCCH communications; and means for receiving PUCCH communications via a secondary component carrier associated with a UE.

[0015] The general categories include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, and processing systems, as basically described with reference to the accompanying drawings and illustrated in the drawings and description.

[0016] The foregoing has provided a fairly broad overview of the features and technical advantages of the examples according to this disclosure in order to better understand the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifications or the design of other structures for achieving the same purpose as this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features, organization, and operation of the concepts disclosed herein, as well as their associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to limit the definitions of the claims.

[0017] While aspects have been described in this disclosure by way of example, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / procurement equipment, medical devices, or devices enabling artificial intelligence). Aspects may be implemented as chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features to implement and practice the claimed and described aspects. For example, the transmission and reception of wireless signals may include components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or accumulators). The aspects described in this article can be practiced in a wide variety of devices, components, systems, distributed arrangements, or end-user devices of different sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a more detailed understanding of the features of this disclosure, a more specific description of the above-brief overview can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should therefore not be considered as limiting its scope, as the description may allow for other equivalent aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a schematic diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 This is a schematic diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 and Figure 4 This is a schematic diagram illustrating an example of communication associated with transmitting physical uplink control channel communication according to this disclosure.

[0022] Figure 5 This is a schematic diagram illustrating an example of communication associated with a physical uplink control channel for carrier aggregation according to this disclosure.

[0023] Figure 6 and Figure 7This is a schematic diagram illustrating an example process associated with physical uplink control channel communication for carrier aggregation according to this disclosure.

[0024] Figure 8 and Figure 9 This is a block diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0025] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be presented in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method that uses a structure, function, or structure-plus-function practice other than or different from the aspects described herein. It should be understood that any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

[0026] Various devices and techniques will now be referenced to illustrate several aspects of a telecommunications system. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of both. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the entire system.

[0027] It should be noted that although the terms commonly associated with 5G or NR radio access technology (RAT) may be used to describe the aspects herein, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0028] Figure 1This is a schematic diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. The wireless network 100 may include multiple base stations 110 (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the coverage area of ​​a BS subsystem serving that coverage area, depending on the context in which the term is used.

[0029] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or other cell types. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells can be referred to as a macro BS. A BS used for picocells can be referred to as a pico BS. A BS used for femtocells can be referred to as a femtocell BS or a home BS. Figure 1 In the example shown, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “Node B”, “5G NB”, and “cell” are used interchangeably in this document.

[0030] In some respects, the cell is not necessarily fixed, and the geographical area of ​​the cell can move depending on the location of the mobile base station. In some respects, the BS can interconnect with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connection or virtual network, using any suitable transport network).

[0031] Wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and transmit the data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can forward transmissions for other UEs. Figure 1 In the example shown, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay unit, etc.

[0032] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0033] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0034] UEs 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite broadcasting), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0035] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or from a network (e.g., a wide area network such as the Internet or cellular networks) via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120 (e.g., processor components and / or memory components). In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0036] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, air interface, etc. A frequency can be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0037] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication with each other). For example, UE 120 may communicate using point-to-point (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0038] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc., based on frequency or wavelength. For example, devices of wireless network 100 can communicate using an operating band with a first frequency range (FR1), which can range from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2), which can range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz” band. Similarly, although FR2 is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) which the International Telecommunication Union (ITU) identifies as the “millimeter wave” band, it is also frequently referred to as the “millimeter wave” band. Therefore, unless specifically stated otherwise, terms such as “sub-6 GHz” should be understood to broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz) when used herein. Similarly, unless specifically stated otherwise, the terms “millimeter wave” and similar terms, when used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to these modified frequency ranges.

[0039] As mentioned above, Figure 1 This is provided as an example. Other examples may be provided. Figure 1 The descriptions differ.

[0040] Figure 2 This is a schematic diagram illustrating an example 200 of communication between base station 110 and UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, wherein generally, T≥1 and R≥1.

[0041] At base station 110, transmitting processor 220 can receive data from one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process (e.g., code and modulate) the data for each UE based at least in part on the selected MCS(one or more) for the UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). If appropriate, the transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t respectively.

[0042] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if appropriate, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), and / or CQI. In some respects, one or more components of the UE 120 may be included in the housing 284.

[0043] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include, for example, one or more devices in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0044] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may be included, or may be included, in one or more antenna panels, antenna groups, antenna element groups, and / or antenna arrays. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as... Figure 2 One or more components.

[0045] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262, and receive and process control information (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-coded (if applicable) by TX MIMO processor 266, then further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of UE 120 can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as referenced). Figure 5-7 (As described).

[0046] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 if applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule UE 120 for downlink and / or uplink communication. In some aspects, modulators and demodulators (e.g., MOD / DEMOD 232) of base station 110 may be included in the modulator of base station 110. In some aspects, base station 110 includes transceivers. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as referenced). Figure 5-7 (As described).

[0047] As described in more detail elsewhere in this document, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with PUCCH communication used for carrier aggregation. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 6 Processing 600 Figure 7 The processing 700 and / or other processing described herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), the one or more instructions may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 6 Processing 600 Figure 7 The operations of processing 700 and / or other processing described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0048] In some aspects, the UE includes components for receiving downlink communications associated with PUCCH communications; or components for transmitting PUCCH communications via a secondary component carrier (e.g., at least in part because the primary component carrier does not have sufficient uplink resources for transmitting PUCCH communications). Components of the UE performing the operations described herein may include, for example, one or more of the following: antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0049] In some respects, the UE includes a component for receiving an indication that the UE intends to transmit PUCCH communication via a secondary component carrier (e.g., if the primary component carrier does not have sufficient uplink resources to transmit PUCCH communication).

[0050] In some respects, the UE includes components for receiving instructions via radio resource control signaling.

[0051] In some respects, the UE includes components for transmitting PUCCH communications via secondary component carriers at times based at least in part on a set of parameters (numerology) of the primary component carrier.

[0052] In some aspects, the UE includes components for determining the time slots of the secondary component carrier for transmitting PUCCH communications based at least in part on one or more of the following:

[0053] In some aspects, the UE includes components for determining the time slots of the secondary component carrier for transmitting PUCCH communications based at least in part on one or more of the following:

[0054] In some aspects, the UE includes components for receiving priority indications among a set of candidate secondary component carriers.

[0055] In some aspects, the base station includes components for transmitting downlink communications associated with PUCCH communications; or components for receiving PUCCH communications at least in part based on a primary component carrier associated with the UE via a secondary component carrier associated with the UE, the primary component carrier having uplink resources insufficient for the UE to transmit PUCCH signals. Components for the base station to perform the operations described herein may include one or more of, for example, a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0056] In some aspects, the base station includes components for transmitting an indication that the UE wants to transmit PUCCH communication via a secondary component carrier (e.g., if the primary component carrier does not have sufficient uplink resources for the UE to transmit PUCCH communication).

[0057] In some respects, the base station includes components for transmitting instructions based on radio resource control signaling.

[0058] In some respects, the base station includes components for receiving PUCCH communications via a secondary component carrier at a time based at least in part on a parameter set of the primary component carrier.

[0059] In some aspects, the base station includes components for determining the time slot of the secondary component carrier to receive PUCCH communications based at least in part on one or more of the following:

[0060] In some aspects, the base station includes components for determining the time slot of the secondary component carrier to receive PUCCH communications based at least in part on one or more of the following:

[0061] In some aspects, the base station includes components for transmitting priority indications for a set of candidate secondary component carriers.

[0062] Although Figure 2 The blocks are shown as different components, but the functions of the blocks described above can be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be performed by the controller / processor 280 or under the control of the controller / processor 280.

[0063] As mentioned above, providing Figure 2 As an example. Other examples may be related to... Figure 2 The descriptions are different.

[0064] Figure 3 This is a schematic diagram illustrating example 300 associated with transmitting physical uplink control channel communication according to this disclosure. Figure 3 As shown, the UE can communicate with the base station. In some aspects, the UE can be configured to provide PUCCH communication, at least in part, based on receiving Physical Downlink Shared Channel (PDSCH) communication.

[0065] As shown by reference numeral 305 in the attached figure, the UE can receive and the base station can transmit downlink control information (DCI) messages that schedule the PDSCH on one or more component carriers (CCs) and / or the PUCCH associated with the PDSCH. For example, the DCI message can indicate one or more communication resources that the base station wants to transmit and the UE wants to receive downlink data. The DCI message can indicate (e.g., using a PDSCH-to-Hybrid Automatic Repeat Request (HARQ) feedback timing indicator) the timing of the PUCCH relative to the received PDSCH. For example, the DCI message can indicate the number of time slots (e.g., via the K1 value field of the DCI) after the received PDSCH, during which the PUCCH is scheduled for the UE to transmit HARQ feedback.

[0066] As shown by reference numeral 310 in the attached figure, the UE can receive PDSCH communications. For example, the UE can receive application data, file downloads, and / or a portion of the data stream within a PDSCH communication. The UE can receive PDSCH communications via one or more CCs in a PUCCH group, such as the primary CC (PCC) and / or one or more secondary CCs (SCCs).

[0067] As shown by reference numeral 315 in the attached figure, the UE can determine the HARQ acknowledgment (HARQ-ACK) feedback associated with the PDSCH. For example, the UE can attempt to decode the PDSCH communication and / or can generate HARQ-ACK feedback based at least in part on the attempt to decode the PDSCH communication. The HARQ-ACK feedback can indicate ACK or NACK.

[0068] As shown by reference numeral 320 in the attached figure, the UE can transmit PUCCH communication via the PCC. The UE can transmit PUCCH communication via the PCC at least in part based on the PDSCH being scheduled by any group of CCs (e.g., PCC and / or one or more SCCs) in the PUCCH group.

[0069] As mentioned above, providing Figure 3 As an example. Other examples may be related to... Figure 3 The descriptions are different.

[0070] Figure 4 This is a schematic diagram illustrating Example 400 associated with transmitting a PUCCH according to this disclosure. Figure 4 As shown, the UE can communicate with the base station in one or more time slots and / or based on one or more CCs of a PUCCH group. For example, the UE can communicate with the base station via a set of CCs of a PUCCH group, such as PCC, first SCC, and / or second SCC.

[0071] As shown in the figure, one or more CCs in this group can include time-division multiplexing of uplink and downlink communication. The PCC can be configured with downlink time slots in time slots 0, 1, 4, and 5; uplink time slots in time slots 3 and 7; and special time slots (e.g., including uplink resources, downlink resources, and / or handover gaps) in time slots 2 and 6. The first SCC can be configured with downlink time slots in time slots 2, 3, 6, and 7; uplink time slots in time slots 1 and 5; and special time slots (e.g., including uplink resources, downlink resources, and / or handover gaps) in time slots 0 and 4.

[0072] One or more CCs in this group can include frequency division multiplexing for uplink and downlink communication. For example, the second SCC can include uplink resources of time slots 0-8 in a first frequency range and downlink resources of time slots 0-8 in a second frequency range.

[0073] As shown by reference numeral 405 in the attached figure, the UE can receive, and the base station can transmit, a DCI that schedules the PDSCH. The DCI may include a PDSCH-to-HARQ feedback timing indicator that indicates the timing (e.g., time slot) relative to the time slot in which the PDSCH communication is received via the PDSCH for sending HARQ-ACK feedback for the communication.

[0074] As shown by reference numeral 410 in the attached figure, the UE can receive via PDSCH, and the base station can transmit PDSCH communication via PDSCH. The UE can receive PDSCH communication via one or more time slots, at least in part based on DCI. The UE can receive PDSCH communication ending in time slot n. The PDSCH-to-HARQ feedback timing indicator (e.g., the K1 field of DCI) can have a value k.

[0075] As shown in Figure 415, the UE can transmit via PCC in time slot n+k, and the base station can receive PUCCH communication via PCC in time slot n+k. The UE can determine time slot n+k based at least in part on the last time slot in which the UE receives the PDSCH and the PDSCH-to-HARQ feedback timing indicator of the DCI. PUCCH communication can be based at least in part on the decoding indication HARQ-ACK feedback (e.g., ACK or NACK) of the PDSCH.

[0076] In some component carrier configurations, PCC can be configured using time-division multiplexing of uplink and downlink communications. In these configurations, the base station can indicate the value of the PDSCH-to-HARQ feedback timing indicator to indicate that the UE has sufficient uplink resources for transmitting PUCCH communications in the specified time slots. This can force a delay between PDSCH reception and PUCCH transmission, which is at least partially based on the timing that the UE has sufficient uplink resources for transmitting subsequent PUCCH communications. The UE and / or base station can consume power, computation, network, and / or communication resources, at least partially based on the delay in receiving PUCCH communications caused by the delay. Additionally, or alternatively, the base station can consume computational resources to determine the value of the PDSCH-to-HARQ feedback timing indicator to indicate that the UE has sufficient uplink resources in the PCC for transmitting PUCCH communications in the specified time slots.

[0077] As mentioned above, providing Figure 4 As an example. Other examples may be related to... Figure 4 The descriptions are different.

[0078] In some aspects described herein, the UE can be configured to transmit PUCCH communication via the PCC and one or more SCCs. In some aspects, the UE can be configured to transmit PUCCH communication via an SCC configured to transmit PUCCH communication, at least partially based on the PCC not having sufficient uplink resources for PUCCH communication. For example, the PCC may not have sufficient uplink resources for PUCCH communication in a reference time slot indicated at least partially by a PDSCH-to-HARQ feedback timing indicator (e.g., time slot n+k). In some aspects, one or more SCCs can be configured to have priorities such that the UE can transmit PUCCH communication via a first SCC, at least partially based on the PCC not having sufficient uplink resources, via a second SCC, or at least partially based on the second SCC not having sufficient uplink resources, via a third SCC.

[0079] In some respects, the UE can transmit PUCCH communication via the SCC time slot, at least in part based on the PCC parameter set. For example, the UE can transmit PUCCH communication during the earliest time slot of the SCC, which overlaps in time with the PCC time slot indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

[0080] In some respects, PDSCH can be associated with configured grants and / or semi-permanent scheduling resources. The UE can transmit PUCCH communication during the earliest available time slot on the PCC or SCC, which overlaps in time with or follows the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

[0081] Based at least in part on the UE being configured to transmit PUCCH communication via SCC, the UE can transmit PUCCH communication with a delay not constrained by the PCC having sufficient resources for PUCCH communication. In some aspects, relative to a configuration where the UE is configured to transmit PUCCH communication only on the PCC, the PCC and one or more SCCs can be configured to increase the number of time slots during the period when the UE is configured to transmit PUCCH communication. For example, the base station can configure uplink time slots and / or special time slots for the PCC and one or more SCCs such that at least one of the PCC and one or more SCCs has sufficient uplink resources for PUCCH communication. Based at least in part on the UE transmitting PUCCH communication with a delay not constrained by the PCC having sufficient resources for PUCCH communication, the UE and / or base station can save power, computing, network, and / or communication resources that would otherwise be consumed at least in part due to delays in receiving PUCCH communication caused by the delay.

[0082] Additionally, or alternatively, the base station can conserve computational resources that might otherwise be used to determine the value of the PDSCH-to-HARQ feedback timing indicator to indicate to the UE that it has sufficient uplink resources in the PCC for transmitting PUCCH communications during the time slots. In some aspects, the base station can use the PDSCH-to-HARQ feedback timing indicator for multiple PDSCH communications, at least in part based on the UE being configured to have sufficient uplink resources to transmit PUCCH communications in each time slot or an increasing number of time slots. For example, the UE can use Radio Resource Control (RRC) signaling to indicate the PDSCH-to-HARQ feedback timing indicator for a set of PDSCH communications. In this way, the UE and / or the base station can reduce the overhead associated with scheduling PUCCH communications related to a set of PDSCH communications.

[0083] Figure 5 This is a schematic diagram illustrating example 500 associated with transmitting physical uplink control channel communication according to this disclosure. Figure 5 As shown, a UE (e.g., UE 120) can communicate with a base station (e.g., base station 110). The UE and the base station can be part of a wireless network (e.g., wireless network 100). The UE can communicate with the base station on one or more time slots and / or on one or more CCs in a PUCCH group. For example, the UE can communicate with the base station via a set of CCs in a PUCCH group (e.g., PCC and one or more SCCs).

[0084] As shown by reference numeral 505 in the accompanying drawings, the UE may receive configuration information (e.g., from a base station, another base station, etc.) and / or may determine the configuration information at least in part based on a communication protocol. In some aspects, the UE may receive the configuration information via one or more of RRC signaling, a Media Access Control (MAC) control element (CE), etc. In some aspects, the configuration information may include indications of one or more configuration parameters (e.g., those already known to the UE) for the UE to select, and / or explicit configuration information for the UE to use to configure the UE, etc.

[0085] In some aspects, configuration information may instruct the UE to communicate with the base station via the PCC of a PUCCH group and one or more SCCs within that group. In some aspects, configuration information may instruct the configuration of the PCC and the SCCs within that group. For example, configuration information may instruct the time slot allocation of the PCC and / or the SCCs within that group (e.g., as uplink, downlink, or special time slots, etc.). In some aspects, configuration information may instruct the UE to transmit PUCCH communication based at least in part on receiving PDSCH communication via the PCC and / or the SCCs within that group. In some aspects, configuration information may instruct the UE to transmit PUCCH communication via the PCC or via the SCCs within that group. In some aspects, configuration information may instruct the UE how to transmit PUCCH communication and / or how the UE determines the CC used to transmit PUCCH communication.

[0086] As shown by reference numeral 510 in the accompanying drawings, the UE can be configured to communicate with a base station. In some aspects, the UE can be configured at least partially based on configuration information. In some aspects, the UE can be configured to perform one or more operations described herein.

[0087] As shown by reference numeral 515 in the attached figure, the UE can receive, and the base station can send, an indication that the UE should send PUCCH communication via the SCC when the PCC does not have sufficient uplink resources. In some aspects, the UE can receive an indication that the UE should send PUCCH communication via the SCC when the PCC does not have sufficient uplink resources via RRC signaling.

[0088] As shown by reference numeral 520 in the attached figure, the UE can receive a priority indication for one or more SCCs in the same group. In some aspects, the UE can receive the priority indication for one or more SCCs in the same message, or together with an indication that the UE will transmit PUCCH communication via the SCCs when the PCC does not have sufficient uplink resources. In some aspects, the UE is configured to transmit PUCCH via one or more SCCs in a group of one or more SCCs, at least in part based on the SCC having the highest priority among the SCCs, which are configured to transmit PUCCH and have sufficient resources for transmitting PUCCH.

[0089] As shown by reference numeral 525 in the attached figure, the UE can receive, and the base station can send, a scheduling grant that schedules the PDSCH on one or more CCs and / or PDSCHs associated with the PDSCH in a PUCCH group. In some aspects, the scheduling grant may include DCI messages or RRC signaling (e.g., a grant of scheduling configuration), etc.

[0090] As shown by reference numeral 530 in the attached figure, the UE can receive PDSCH communication via one or more CCs in a PUCCH group, and the base station can transmit PDSCH communication via one or more CCs in a PUCCH group. In some aspects, PDSCH communication may include application data, file downloads, and / or a portion of a data stream. In some aspects, the UE can receive PDSCH communication in one or more time slots ending in time slot n.

[0091] As shown by reference numeral 535 in the attached figure, the UE can determine the CC to use and / or the time slot to be used for transmitting PUCCH communication associated with the PDSCH. In some aspects, the UE can determine a reference time slot for transmitting PUCCH communication. For example, the reference time slot can be time slot n+k, where n is the last time slot in which the UE receives the PDSCH, and k is the value of the PDSCH-to-HARQ feedback timing indicator. In some aspects, time slot n+k can be at least partially based on the parameter set of the PCC (e.g., the time slot length configured for the PCC). The UE can determine whether the PCC has sufficient uplink resources for transmitting PUCCH communication during the reference time slot. If the PCC does not have sufficient uplink resources, the UE can determine to transmit PUCCH communication via the SCC during the reference time slot. If the SCC has multiple time slots within the reference time slot (e.g., time slots shorter than the PCC's time slots are defined at least partially based on the parameter set of the SCC), the UE can be configured to transmit PUCCH communication via one or more of the multiple time slots. For example, a UE can be configured to transmit PUCCH communication via the earliest slot of a secondary component carrier that has sufficient uplink resources for transmitting PUCCH communication and overlaps at least partially with the slot of the primary component carrier indicated by a PDSCH-to-HARQ feedback timing indicator (e.g., a reference slot).

[0092] In some aspects, the PCC and / or SCC can be configured such that only one of the PCCs and / or one or more SCCs configured to transmit PUCCH has uplink resources during a time slot that can be scheduled to transmit PUCCH. For example, the PCC and / or SCC can be configured such that only one CC of the PCCs and / or one or more SCCs configured to transmit PUCCH has uplink resources during each time slot. Based at least in part on the PCC and / or SCC being configured such that only one CC of the PCC and / or one or more SCCs configured to transmit PUCCH has uplink resources during a time slot that can be scheduled to transmit PUCC, the UE can determine to transmit PUCCH via a CC that has uplink resources configured in the reference time slot.

[0093] In some respects (e.g., where PDSCH is associated with the granting of a configuration), the UE may determine the time slot of the SCC or PCC to transmit PUCCH communication based at least in part on a reference time slot indicated by the PDSCH-to-HARQ feedback timing indicator or at least in part on the time slot indicated by the PDSCH-to-HARQ feedback timing indicator. Additionally, or alternatively, the UE may determine the time slot of the SCC or PCC to transmit PUCCH communication based at least in part on the earliest time slot of the PCC or SCC that has sufficient uplink resources for transmitting PUCCH communication, which overlaps in time with or follows the reference time slot.

[0094] As indicated by reference numeral 540, the UE can transmit via PCC or SCC, and the base station can receive the PUCCH associated with the PDSCH via PCC or SCC. In some aspects, the UE can transmit PUCCH communication via SCC, at least in part, based on the fact that PCC does not have sufficient uplink resources for transmitting PUCCH communication. In some aspects, the UE can transmit PUCCH communication via PCC or SCC at a determined time (e.g., within a time slot), at least in part, based on one or more parameters (e.g., as described by reference numeral 535). For example, the UE can transmit PUCCH communication via PCC or SCC during a time slot based at least in part on a set of parameters of the primary component carrier. Additionally, or alternatively, the UE can transmit PUCCH communication via PCC or SCC during a reference time slot or during the earliest time slot that has sufficient uplink resources for transmitting PUCCH communication and overlaps with the reference time slot.

[0095] Based at least in part on the UE being configured to transmit PUCCH communication via SCC, the UE can transmit PUCCH communication with a delay not constrained by the PCC having sufficient resources for PUCCH communication. In some aspects, relative to a configuration where the UE is configured to transmit PUCCH communication only on the PCC, the PCC and one or more SCCs can be configured to increase the number of time slots the UE is configured to transmit PUCCH communication. For example, the base station can configure uplink time slots and / or special time slots for the PCC and one or more SCCs such that at least one of the PCC and one or more SCCs has sufficient uplink resources for PUCCH communication. Based at least in part on the UE transmitting PUCCH communication with a delay not constrained by the PCC having sufficient resources for PUCCH communication, the UE and / or base station can save power, computing, network, and / or communication resources that would otherwise be consumed at least in part due to the delay in receiving PUCCH communication caused by the delay.

[0096] As mentioned above, providing Figure 5 As an example. Other examples can be used with... Figure 5The descriptions differ.

[0097] Figure 6 This is a schematic diagram illustrating, for example, an example process 600 performed by a UE in accordance with this disclosure. Example process 600 is an example of an operation performed by a UE (e.g., UE 120) associated with physical uplink control channel communication for carrier aggregation.

[0098] like Figure 6 As shown, in some aspects, processing 600 may include receiving downlink communication associated with PUCCH communication (block 610). For example, the UE (e.g., using...) Figure 8 The receiving component 802 depicted can receive downlink communications associated with PUCCH communications, as described above.

[0099] like Figure 6 As further shown, in some aspects, processing 600 may include transmitting PUCCH communication via a secondary component carrier (block 620). For example, the UE (e.g., using...) Figure 8 The transmitting component 804 described herein can transmit PUCCH communication via a secondary component carrier. In some respects, the UE may transmit PUCCH communication via a secondary component carrier, at least in part, because the primary component carrier does not have sufficient uplink resources for transmitting PUCCH communication, as described above.

[0100] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or aspects relating to one or more other processes described elsewhere herein.

[0101] In the first aspect, processing 600 includes receiving an indication that the UE wants to transmit PUCCH communication via a secondary component carrier (e.g., if the primary component carrier does not have sufficient uplink resources for transmitting PUCCH communication).

[0102] In the second aspect, alone or in combination with the first aspect, receiving an indication that the UE wants to transmit PUCCH communication via a secondary component carrier includes receiving the indication via radio resource control signaling.

[0103] In the third aspect, either alone or in combination with one or more of the first and second aspects, the primary component carrier and the secondary component carrier are component carriers of the PUCCH group.

[0104] In the fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting PUCCH communication via a secondary component carrier includes transmitting PUCCH communication via a secondary component carrier at a time based at least partially on a parameter set of the primary component carrier.

[0105] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, processing 600 includes determining the time slot of the secondary component carrier for transmitting PUCCH communication based on one or more of the time slots of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier that overlaps in time with the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

[0106] In the sixth aspect, downlink communication is associated with the granting of configuration, either alone or in combination with one or more of the first to fifth aspects.

[0107] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, processing 600 includes determining the time slot of the secondary component carrier for transmitting PUCCH communication based at least in part on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for transmitting PUCCH communication, which time slot overlaps in time with or follows the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0108] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, processing 600 includes receiving a priority indication of a set of candidate secondary component carriers, wherein transmitting PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier having the highest priority among the candidate secondary component carriers in the set, which has sufficient uplink resources for transmitting PUCCH communication.

[0109] although Figure 6 The example block for processing 600 is shown, but in some respects, processing 600 can include additional blocks, fewer blocks, different blocks, or blocks similar to... Figure 6 The different arrangements of blocks are depicted in the diagram. Additionally, or alternatively, processing two or more blocks of 600 can be performed in parallel.

[0110] Figure 7 This is a schematic diagram illustrating, for example, an example process 700 performed by a base station in accordance with this disclosure. Example process 700 is an example of an operation performed by a base station (e.g., base station 110) associated with physical uplink control channel communication for carrier aggregation.

[0111] like Figure 7As shown, in some aspects, processing 700 may include sending downlink communication associated with PUCCH communication (block 710). For example, a base station (e.g., using...) Figure 9 The transmitting component 904 depicted can transmit downlink communications associated with PUCCH communications, as described above.

[0112] like Figure 7 As further shown, in some aspects, processing 700 may include receiving PUCCH communication via a secondary component carrier associated with the UE (block 720). For example, a base station (e.g., using...) Figure 9 The receiving component 902 described herein can receive PUCCH communication via a secondary component carrier associated with the UE. In some aspects, the UE can transmit PUCCH communication via a secondary component carrier, at least in part, because the primary component carrier associated with the UE does not have sufficient uplink resources for the UE to transmit PUCCH communication, as described above.

[0113] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or aspects relating to one or more other processes described elsewhere herein.

[0114] In the first aspect, processing 700 includes sending an indication that the UE wants to send PUCCH communication via a secondary component carrier (e.g., if the primary component carrier does not have sufficient uplink resources for the UE to send PUCCH communication).

[0115] In the second aspect, either alone or in combination with the first aspect, the instruction to transmit a UE to transmit PUCCH communication via a secondary component carrier includes transmitting the instruction via radio resource control signaling.

[0116] In the third aspect, either alone or in combination with one or more of the first and second aspects, the primary component carrier and the secondary component carrier are component carriers of the PUCCH group.

[0117] In the fourth aspect, receiving PUCCH communication via a secondary component carrier, alone or in combination with one or more of the first to third aspects, includes receiving PUCCH communication via a secondary component carrier at a time based at least partially on a parameter set of the primary component carrier.

[0118] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, processing 700 includes determining the time slot of the secondary component carrier for receiving PUCCH communication based at least in part on one or more of the following: the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator; the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for the UE to transmit PUCCH communication; and the time slot of the secondary component carrier overlapping in time with the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0119] In the sixth aspect, downlink communication is associated with the granting of configuration, either alone or in combination with one or more of the first to fifth aspects.

[0120] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, processing 700 includes determining the time slot of the secondary component carrier for receiving PUCCH communication based at least partially on the PDSCH-to-HARQ feedback timing indicator, the time slot of the primary component carrier indicated at least partially on the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for the UE to transmit PUCCH communication, the earliest time slot overlapping with or following one or more of the time slot of the primary component carrier indicated at least partially on the PDSCH-to-HARQ feedback timing indicator.

[0121] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, processing 700 includes transmitting a priority indication of a set of candidate secondary component carriers, wherein receiving PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier having the highest priority among the candidate secondary component carriers in the set, which has sufficient uplink resources for the UE to transmit PUCCH communication.

[0122] although Figure 7 Example blocks for processing 700 are shown, but in some respects, processing 700 can include additional blocks, fewer blocks, different blocks, or blocks similar to those in other applications. Figure 7 The different arrangements of blocks are depicted in the diagram. Additionally, or alternatively, processing two or more blocks of 700 can be performed in parallel.

[0123] Figure 8This is a block diagram of an example device 800 for wireless communication. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802 and a transmitting component 804, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 800 can use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 800 may include a communication manager 808.

[0124] In some respects, device 800 can be configured to perform the actions described herein. Figure 4 One or more related operations. Additionally, or alternatively, the device 800 may be configured to perform one or more processes described herein, such as... Figure 6 The processing 600. In some aspects, the device 800 and / or Figure 8 One or more components shown may include the above and Figure 2 One or more components of the relevant UE. Additionally, or alternatively, Figure 8 One or more components shown can be used in conjunction with the above. Figure 2 Implemented within one or more of the relevant components. Additionally, or alternatively, one or more of the components in the group may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0125] Receiver 802 may receive communications from device 806, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 800. In some aspects, receiver 802 may include the aforementioned... Figure 2 One or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the relevant UE.

[0126] Transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 806. In some aspects, one or more other components of device 800 can generate communications and provide the generated communications to transmitting component 804 for transmission to device 806. In some aspects, transmitting component 804 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and the processed signals can be transmitted to device 806. In some aspects, transmitting component 804 may include the aforementioned components... Figure 2 The relevant UE may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may coexist with the receive component 802 in a transceiver.

[0127] The receiving component 802 can receive downlink communications associated with PUCCH communications. The transmitting component 804 can transmit PUCCH communications via a secondary component carrier. In some aspects, the transmitting component 804 can transmit PUCCH communications via a secondary component carrier, at least in part, because the primary component carrier does not have sufficient uplink resources for transmitting PUCCH communications.

[0128] The receiving component 802 can receive an indication that the UE wants to transmit PUCCH communication via the secondary component carrier (e.g., if the primary component carrier does not have enough uplink resources to transmit PUCCH communication).

[0129] The communication manager 808 may determine the time slot of the secondary component carrier for transmitting PUCCH communication based at least in part on one or more of the following: the timing of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources to transmit PUCCH communication, and overlapping in time with the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0130] The communication manager 808 may determine the time slot of the secondary component carrier for transmitting PUCCH communication based at least in part on one or more of the timing of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for transmitting PUCCH communication, which overlaps in time with or follows the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0131] The receiving component 802 can receive a priority indication of a set of candidate secondary component carriers, wherein the transmission of PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier with the highest priority among the candidate secondary component carriers in the set, which has sufficient uplink resources for transmitting PUCCH communication.

[0132] supply Figure 8 The number and arrangement of components shown are for illustrative purposes only. In practice, additional components, fewer components, different components, or components may exist. Figure 8 The different component arrangements are shown. Furthermore... Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally, or alternatively, Figure 8 The set (one or more) components shown can perform actions described by Figure 8 The other set of components shown performs one or more functions.

[0133] Figure 9 This is a block diagram of an example device 900 for wireless communication. Device 900 may be a base station, or a base station may include device 900. In some aspects, device 900 includes a receiving component 902 and a transmitting component 904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 can use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 900 may include a communication manager 908.

[0134] In some respects, device 900 can be configured to perform the actions described herein. Figure 4 One or more related operations. Additionally, or alternatively, device 900 may be configured to perform one or more processes described herein, such as... Figure 7 The processing 700. In some aspects, the device 900 and / or Figure 9 One or more components shown may include the above and Figure 2 One or more components of the relevant base station. Additionally, or alternatively, Figure 9 One or more components shown can be used in conjunction with the above. Figure 2 Implemented within one or more of the relevant components. Additionally, or alternatively, one or more of the components in the group may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of that component.

[0135] Receiver 902 can receive communications from device 906, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 can provide the received communications to one or more other components of device 900. In some aspects, receiver 902 can perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and can provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include the aforementioned... Figure 2 One or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the relevant base station.

[0136] Transmitting component 904 can transmit communications (e.g., reference signals, control information, data communications, or combinations thereof) to device 906. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 906. In some aspects, transmitting component 904 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) and can transmit the processed signals to device 906. In some aspects, transmitting component 904 may include the aforementioned... Figure 2 The base station may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may coexist with the receive component 902 in a transceiver.

[0137] Transmitting component 904 can transmit downlink communications associated with PUCCH communications. Receiving component 902 can receive PUCCH communications via secondary component carriers associated with the UE, at least in part, based on the fact that there are insufficient uplink resources on the primary component carrier associated with the UE for the UE to transmit PUCCH communications.

[0138] The transmitting component 904 can transmit an indication that the UE wants to transmit PUCCH communication via the secondary component carrier (e.g., if the primary component carrier does not have enough uplink resources for the UE to transmit PUCCH communication).

[0139] The communication manager 908 may determine the time slot of the secondary component carrier for receiving PUCCH communication based at least in part on one or more of the following: the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator; the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for the UE to transmit PUCCH communication; and the time slot overlapping in time with the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0140] The communication manager 908 may determine the time slot of the secondary component carrier for receiving PUCCH communication based at least in part on one or more of the following: the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator; the earliest time slot of the secondary component carrier that has sufficient uplink resources for the UE to transmit PUCCH communication; or the time slot of the secondary component carrier that overlaps with or follows the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator.

[0141] The transmitting component 904 can transmit a set of priority indications for a group of candidate secondary component carriers, wherein receiving PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier with the highest priority among the candidate secondary component carriers in the set, which has sufficient uplink resources for the UE to transmit PUCCH communication.

[0142] supply Figure 9 The number and arrangement of components shown are for illustrative purposes only. In practice, there may be additional components, fewer components, different components, or components with... Figure 9 The different component arrangements are shown. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally, or alternatively, Figure 9 The set (one or more) components shown can perform one or more actions described by [the specified method]. Figure 9 The other set of components shown performs the function.

[0143] The following is an overview of some aspects of this disclosure:

[0144] Aspect 1: A wireless communication method performed by a user equipment (UE), comprising: receiving downlink communication associated with physical uplink control channel (PUCCH) communication; and transmitting the PUCCH communication via a secondary component carrier.

[0145] Aspect 2: The method of Aspect 1, wherein transmitting PUCCH communication via a secondary component carrier is at least in part based on the fact that the primary component carrier does not have sufficient uplink resources for transmitting PUCCH communication.

[0146] Aspect 3: The method of aspect 1 further includes: receiving an indication from the UE that it wants to transmit PUCCH communication via a secondary component carrier.

[0147] Aspect 4: The method of aspect 3, wherein receiving an indication that the UE wants to transmit PUCCH communication via a secondary component carrier includes receiving the indication via radio resource control signaling.

[0148] Aspect 5: The method of Aspect 1, wherein the primary component carrier and the secondary component carrier are component carriers of the PUCCH group.

[0149] Aspect 6: The method of Aspect 1, wherein transmitting PUCCH communication via a secondary component carrier includes: transmitting PUCCH communication via a secondary component carrier at a time at least partially based on a parameter set of the primary component carrier.

[0150] Aspect 7: The method of Aspect 6 further includes: determining the time slot for transmitting PUCCH communication of the secondary component carrier based at least in part on one or more of the following: the physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier that overlaps in time with the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator.

[0151] Aspect 8: The method of Aspect 1, wherein downlink communication is associated with the granting of configuration.

[0152] Aspect 9: The method of Aspect 8 further includes: determining the time slot for transmitting PUCCH communication of the secondary component carrier based at least in part on one or more of the following: the physical downlink shared channel to the hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for transmitting PUCCH communication, which overlaps in time with or follows the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator.

[0153] Aspect 10: The method of Aspect 1 further includes: receiving a priority indication of a set of candidate secondary component carriers, wherein the transmission of PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier having the highest priority among the candidate secondary component carriers in the set of candidate secondary component carriers, which has sufficient uplink resources for transmitting PUCCH communication.

[0154] Aspect 11: A wireless communication method performed by a base station, comprising: transmitting downlink communication associated with physical uplink control channel (PUCCH) communication; and receiving PUCCH communication via a secondary component carrier associated with a user equipment (UE).

[0155] Aspect 12: The method of Aspect 11, wherein receiving PUCCH communication via a secondary component carrier is at least partially based on a primary component carrier associated with a UE that has sufficient uplink resources for the UE to transmit PUCCH communication.

[0156] Aspect 13: The method of aspect 11 further includes: sending an indication that the UE wants to send PUCCH communication via a secondary component carrier.

[0157] Aspect 14: The method of aspect 13, wherein the transmitting UE is to transmit an indication of PUCCH communication via a secondary component carrier.

[0158] Aspect 15: The method of Aspect 11, wherein the primary component carrier and the secondary component carrier are component carriers of the PUCCH group.

[0159] Aspect 16: The method of aspect 11, wherein receiving PUCCH communication via a secondary component carrier includes: receiving PUCCH communication via a secondary component carrier at a time at least partially based on a parameter set of the primary component carrier.

[0160] Aspect 17: The method of Aspect 16 further includes: determining the time slot for receiving PUCCH communications of the secondary component carrier based at least in part on one or more of the following: the Physical Downlink Shared Channel to Hybrid Automatic Repeat Request (PDSCH-to-HARQ) feedback timing indicator, the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier is the earliest time slot of the secondary component carrier with sufficient uplink resources for the UE to transmit PUCCH communications and overlaps in time with the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator.

[0161] Aspect 18: The method of Aspect 11, wherein downlink communication is associated with the granting of configuration.

[0162] Aspect 19: The method of Aspect 18 further includes: determining the time slot for receiving PUCCH communications of the secondary component carrier based at least in part on one or more of the following: the Physical Downlink Shared Channel to Hybrid Automatic Repeat Request (PDSCH-to-HARQ) feedback timing indicator, the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator, or the time slot of the secondary component carrier being the earliest time slot of the secondary component carrier with sufficient uplink resources for the UE to transmit PUCCH communications, which overlaps in time with or follows the time slot of the primary component carrier indicated at least in part on the PDSCH-to-HARQ feedback timing indicator.

[0163] Aspect 20: The method of Aspect 11 further includes: transmitting a priority indication of a set of candidate secondary component carriers, wherein receiving PUCCH communication via the secondary component carriers is based at least in part on the secondary component carrier having the highest priority among the candidate secondary component carriers in the set of candidate secondary component carriers, which has sufficient uplink resources for the UE to transmit PUCCH communication.

[0164] Aspect 21: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more methods of aspects 1-20.

[0165] Aspect 22: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform one or more methods of aspects 1-20.

[0166] Aspect 23: A device for wireless communication, comprising at least one component for performing one or more methods of aspects 1-20.

[0167] Aspect 24: A non-transitory computer-readable medium storing wireless communication code, said code comprising instructions executable by a processor to perform one or more methods of aspects 1-20.

[0168] Aspect 25: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions, which, when executed by one or more processors of the device, cause the device to perform one or more methods of aspects 1-20.

[0169] The foregoing disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or can be derived from practice in the various aspects.

[0170] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. "Software" should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, programs and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or others. As used herein, processors are implemented in hardware and / or a combination of hardware and software. Clearly, the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation in any respect. Therefore, this document describes the operation and behavior of systems and / or methods without mentioning specific software code—it is understood that software and hardware can be designed to implement these systems and / or methods, at least in part, based on the descriptions herein.

[0171] As used in this article, the threshold can be determined by context, meaning the value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0172] Even if specific combinations of features are disclosed in the claims and / or specification, these combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically described in the claims and / or specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of aspects includes combinations of each dependent claim with every other claim in the claim set. As used herein, the phrase referring to the list of “at least one” items means any combination of these items, including a single member. As an example, “at least one: a, b, or” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0173] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as essential or necessary. Furthermore, the terms “a” and “one” as used herein include one or more items and are used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items in relation to the article “the” and is used interchangeably with “the one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are used interchangeably with “one or more.” If only one item is intended to be used, the phrase “only one” or similar language is used. Additionally, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” means “at least partially based on” unless explicitly stated otherwise. Additionally, as used herein, the term “or” is intended to be included when used in a series and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, are configured to: Receive downlink communications associated with Physical Uplink Control Channel (PUCCH) communications, wherein the downlink communications are associated with the granting of a configuration; The PUCCH communication is transmitted via a secondary component carrier. as well as The time slot for transmitting the PUCCH communication is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for transmitting the PUCCH communication, and the earliest time slot of the secondary component carrier overlaps in time with or follows the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

2. The UE of claim 1, wherein transmitting the PUCCH communication via the secondary component carrier is at least in part based on the primary component carrier not having sufficient uplink resources for transmitting the PUCCH communication.

3. The UE according to claim 1, wherein the one or more processors are further configured to: The UE receives an indication that it wants to transmit the PUCCH communication via the secondary component carrier.

4. The UE of claim 3, wherein, in order to receive an indication that the UE intends to transmit the PUCCH communication via the secondary component carrier, the one or more processors are configured to: The instruction is received via radio resource control signaling.

5. The UE according to claim 1, wherein the primary component carrier and the secondary component carrier are component carriers of a PUCCH group.

6. The UE of claim 1, wherein, in order to transmit PUCCH communication via the secondary component carrier, the one or more processors are configured to: The PUCCH communication is transmitted via the secondary component carrier at a time based at least in part on the parameter set of the primary component carrier.

7. The UE of claim 6, wherein the one or more processors are further configured to: The time slot for transmitting the PUCCH communication is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier, and the earliest time slot of the secondary component carrier overlaps in time with the time slot of the primary component carrier, which is indicated at least partially based on the PDSCH-to-HARQ feedback timing indicator.

8. The UE of claim 1, wherein the one or more processors are further configured to: receive a priority indication of a set of candidate secondary component carriers, The transmission of PUCCH communication via the secondary component carrier is based at least in part on the secondary component carrier with the highest priority among a set of candidate secondary component carriers, which has sufficient uplink resources for transmitting the PUCCH communication.

9. A network node for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, are configured to: Send downlink communications associated with Physical Uplink Control Channel (PUCCH) communications, wherein the downlink communications are associated with the granting of a configuration; The PUCCH communication is received via a secondary component carrier associated with the user equipment (UE); and The time slot for receiving the PUCCH communication of the secondary component carrier is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for the UE to transmit the PUCCH communication, and it overlaps in time with or follows the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

10. The network node of claim 9, wherein receiving PUCCH communication via the secondary component carrier is at least in part based on a primary component carrier associated with the UE having sufficient uplink resources for the UE to transmit the PUCCH communication.

11. The network node of claim 9, wherein the one or more processors are further configured to: The UE sends an indication that it wants to transmit the PUCCH communication via the secondary component carrier.

12. The network node of claim 11, wherein, in order to transmit an indication that the UE will transmit the PUCCH communication via the secondary component carrier, the one or more processors are configured to: The instruction is sent via radio resource control signaling.

13. The network node according to claim 9, wherein the primary component carrier and the secondary component carrier are component carriers of a PUCCH group.

14. The network node of claim 9, wherein, in order to receive the PUCCH communication via the secondary component carrier, the one or more processors are configured to: The PUCCH communication is received via the secondary component carrier at a time based at least in part on the parameter set of the primary component carrier.

15. The network node of claim 14, wherein the one or more processors are further configured to: The time slot for receiving the PUCCH communication of the secondary component carrier is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for the UE to transmit the PUCCH communication, and it overlaps in time with the time slot of the primary component carrier that is at least partially based on the PDSCH-to-HARQ feedback timing indicator.

16. The network node of claim 9, wherein the one or more processors are further configured to: Send a priority indication of a set of candidate secondary component carriers. The PUCCH communication received via the secondary component carrier is at least partially based on the secondary component carrier with the highest priority among a set of candidate secondary component carriers, which has sufficient uplink resources for the UE to transmit the PUCCH communication.

17. A wireless communication method performed by a user equipment (UE), comprising: Receive downlink communications associated with Physical Uplink Control Channel (PUCCH) communications, wherein the downlink communications are associated with the granting of a configuration; The PUCCH communication is transmitted via a secondary component carrier. as well as The time slot for transmitting the PUCCH communication is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for transmitting the PUCCH communication, and the earliest time slot of the secondary component carrier overlaps in time with or follows the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

18. The method of claim 17, wherein transmitting the PUCCH communication via the secondary component carrier is at least in part based on the primary component carrier not having sufficient uplink resources for transmitting the PUCCH communication.

19. The method of claim 17, wherein transmitting the PUCCH communication via the secondary component carrier comprises: The PUCCH communication is transmitted via the secondary component carrier at a time based at least in part on the parameter set of the primary component carrier.

20. The method of claim 19, further comprising: The time slot for transmitting the PUCCH communication is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for transmitting the PUCCH communication, and it overlaps in time with the time slot of the primary component carrier that is at least partially based on the PDSCH-to-HARQ feedback timing indicator.

21. The method of claim 17, further comprising: Receive priority indications for a set of candidate secondary component carriers. The transmission of PUCCH communication via the secondary component carrier is based at least in part on the secondary component carrier with the highest priority among a set of candidate secondary component carriers, which has sufficient uplink resources for transmitting the PUCCH communication.

22. A wireless communication method performed by a network node, comprising: Send downlink communications associated with Physical Uplink Control Channel (PUCCH) communications, wherein the downlink communications are associated with the granting of a configuration; The PUCCH communication is received via a secondary component carrier associated with the user equipment (UE); and The time slot for receiving the PUCCH communication of the secondary component carrier is determined based at least in part on one or more of the following: Physical downlink shared channel to hybrid automatic repeat request (PDSCH-to-HARQ) feedback timing indicator, At least in part based on the time slot of the primary component carrier indicated by the PDSCH-to-HARQ feedback timing indicator, or The time slot of the secondary component carrier is the earliest time slot of the secondary component carrier that has sufficient uplink resources for the UE to transmit the PUCCH communication, and it overlaps in time with or follows the time slot of the primary component carrier indicated at least in part by the PDSCH-to-HARQ feedback timing indicator.

23. The method of claim 22, wherein receiving PUCCH communication via the secondary component carrier is at least in part based on a primary component carrier associated with the UE having sufficient uplink resources for the UE to transmit the PUCCH communication.

24. A user equipment (UE) for wireless communication, comprising components for performing the method according to any one of claims 17-21.

25. A network node for wireless communication, comprising components for performing the method according to any one of claims 22-23.

26. A computer-readable medium having computer instructions recorded thereon, which, when executed by a processor of a user equipment (UE), cause the processor to perform the method according to any one of claims 17-21.

27. A computer-readable medium having computer instructions recorded thereon, which, when executed by a processor of a network node, cause the processor to perform the method according to any one of claims 22-23.

28. A computer program product comprising computer instructions that, when executed by a processor of a user equipment (UE), cause the processor to perform the method according to any one of claims 17-21.

29. A computer program product comprising computer instructions that, when executed by a processor of a network node, cause the processor to perform the method according to any one of claims 22-23.

Images