CN117999760A - Sets of Physical Uplink Control Channel (PUCCH) resources with or without parameters per PUCCH resource - Google Patents

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) may receive a Physical Uplink Control Channel (PUCCH) resource set configuration including a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource. The UE may identify parameters to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration. The UE may transmit one or more repetitions of PUCCH communication based at least in part on the parameter. Numerous other aspects are described.

Description

Sets of Physical Uplink Control Channel (PUCCH) resources with or without parameters per PUCCH resource

Cross Reference to Related Applications

This patent application claims priority to the following applications: U.S. provisional patent application Ser. No.63/261,928, entitled "PHYSICAL UPLINK CONTROL CHANNEL(PUCCH)RESOURCE SET WITH OR WITHOUT A REPETITION FACTOR PER PUCCH RESOURCE", filed on 9 and 30 of 2021, and assigned to the assignee of the present application; and U.S. provisional patent application Ser. No.63/261,925 entitled "MIXED PHYSICAL UPLINK CONTROL CHANNEL RESOURCE SET" filed on 9 and 30 of 2021 and assigned to the assignee of the present application; and U.S. non-provisional patent application No.17/933,536 entitled "PHYSICAL UPLINK CONTROL CHANNEL (PUCCH) RESOURCE SET WITH OR WITHOUT APARAMETER PUCCH PER RESOURCE" filed on 9 and 20 of 2022 and assigned to the assignee of the present application. The disclosure of the previous application is considered to be part of the present patent application and is incorporated by reference.

Technical Field

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for a set of Physical Uplink Control Channel (PUCCH) resources with or without parameters per PUCCH resource.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques 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 an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP).

A wireless network may include one or more base stations that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink and uplink communications. "downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

The multiple access techniques described above have been employed in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional and/or global level. A New Radio (NR), which may be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better support mobile broadband internet access by: improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to integrate better with other open standards, as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR and other radio access technologies remain useful.

Disclosure of Invention

Some aspects described herein relate to a method of wireless communication performed by a User Equipment (UE). The method may include: a Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received, wherein PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH resource parameters, and wherein PUCCH resources in the second PUCCH resource subset do not include per-PUCCH resource parameters. The method may include: parameters to be used for transmitting PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The method may include: one or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

Some aspects described herein relate to a method of wireless communication performed by a base station. The method may include: and transmitting a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein the PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH-resource parameters, and wherein the PUCCH resources in the second PUCCH resource subset do not include per-PUCCH-resource parameters. The method may include: parameters to be used for receiving PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The method may include: one or more repetitions of the PUCCH communication are received based at least in part on the parameter.

Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received. The one or more processors may be configured to: parameters to be used for transmitting PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The one or more processors may be configured to: one or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

Some aspects described herein relate to a base station for wireless communications. The base station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is transmitted. The one or more processors may be configured to: parameters to be used for receiving PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The one or more processors may be configured to: one or more repetitions of the PUCCH communication are received based at least in part on the parameter.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to: parameters to be used for transmitting PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to: one or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a base station. The set of instructions, when executed by the one or more processors of the base station, may cause the base station to: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is transmitted. The set of instructions, when executed by the one or more processors of the base station, may cause the base station to: parameters to be used for receiving PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The set of instructions, when executed by the one or more processors of the base station, may cause the base station to: one or more repetitions of the PUCCH communication are received based at least in part on the parameter.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received, wherein PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH-resource parameters, and wherein PUCCH resources in the second PUCCH resource subset do not comprise per-PUCCH-resource parameters. The apparatus may include means for: parameters to be used for transmitting PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The apparatus may include means for: one or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for: and transmitting a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein the PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH-resource parameters, and wherein the PUCCH resources in the second PUCCH resource subset do not include per-PUCCH-resource parameters. The apparatus may include means for: parameters to be used for receiving PUCCH communications are identified based at least in part on the PUCCH resource set configuration. The apparatus may include means for: one or more repetitions of the PUCCH communication are received based at least in part on the parameter.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user device, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as substantially shown in the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with the associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.

While aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that aspects may be implemented in many different arrangements and scenarios. The techniques described herein may 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 non-module component based devices (e.g., end user devices, vehicles, communications devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating the described aspects and features may include additional components and features for achieving and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or adders). Aspects described herein are intended to be practiced in devices, components, systems, distributed arrangements, and/or end user devices of various sizes, shapes, and configurations.

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example in which a User Equipment (UE) communicates with a base station in a wireless network according to the present disclosure.

Fig. 3 is a diagram illustrating an example associated with a set of Physical Uplink Control Channel (PUCCH) resources with or without a repetition factor per PUCCH resource in accordance with the present disclosure.

Fig. 4 and 5 are diagrams illustrating example processes associated with PUCCH resource sets with or without repetition factors per PUCCH resource according to the present disclosure.

Fig. 6 and 7 are diagrams of example apparatuses for wireless communication according to this disclosure.

Fig. 8 is a diagram illustrating an example associated with hybrid Physical Uplink Control Channel (PUCCH) resource set usage in accordance with the present disclosure.

Fig. 9 and 10 are diagrams illustrating example processes associated with hybrid PUCCH resource set usage according to this disclosure.

Fig. 11 and 12 are diagrams of example apparatuses for wireless communication according to this disclosure.

Detailed Description

Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. In addition, the scope of the present disclosure is intended to cover such an apparatus or method that is practiced using other structure, function, or both in addition to and different from the aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

Several aspects of the telecommunications system will now be presented with reference to various apparatus and techniques. 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 referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

Although aspects may be described herein using terms commonly associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, etc., or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, etc. Wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, ue_c, ue_d, and ue_e), and/or other network entities. Base station 110 is the entity in communication with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or transmit-receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a base station 110 and/or a base station subsystem serving the coverage area, depending on the context in which the term is used.

The base station 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs 120 having an association with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or an in-home base station. In the example shown in fig. 1, BS110a may be a macro base station for macro cell 102a, BS110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells.

In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the moving base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected with each other and/or to one or more other base stations 110 or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transmission network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from an upstream station (e.g., base station 110 or UE 120) and send data transmissions to a downstream station (e.g., UE 120 or base station 110). The relay station may be a UE 120 that may relay transmissions for other UEs 120. In the example shown in fig. 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE 120d in order to facilitate communications between BS110a and UE 120 d. The base station 110 relaying communications may be referred to as a relay station, a relay base station, a repeater, etc.

The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, and the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different effects on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmit power level (e.g., 0.1 to 2 watts).

The network controller 130 may be coupled to a set of base stations 110 or in communication with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. Base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.

UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), 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, a camera, a gaming device, a netbook, a smartbook, a super-book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device configured to communicate via a wireless medium.

Some UEs 120 may be considered Machine Type Communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and/or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequencies may be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographical area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120 e) may communicate directly using one or more side-uplink channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by base station 110.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., by frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is commonly (interchangeably) referred to as the "Sub-6 GHz" band in various documents and articles. Similar naming problems sometimes occur with respect to FR2, although FR2 is commonly (interchangeably) referred to in the literature and articles as the "millimeter wave" band, unlike the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and may therefore effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

In view of the above examples, unless explicitly stated otherwise, it should be understood that the term "sub-6GHz" or the like (if used herein) may broadly represent frequencies that may be less than 6GHz, frequencies that may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it should be understood that the term "millimeter wave" or the like (if used herein) may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4-a or FR4-1 and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4-a, FR4-1, and/or FR 5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receiving a Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource; identifying parameters to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration; and transmitting one or more repetitions of PUCCH communication based at least in part on the parameter. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

In some aspects, the base station 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: transmitting a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource; identifying parameters to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration; and receive one or more repetitions of PUCCH communications based at least in part on the parameter. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, fig. 1 is provided as an example. Other examples may differ from that described with respect to fig. 1.

Fig. 2 is a diagram illustrating an example 200 of a base station 110 in a wireless network 100 in communication with a UE 120 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234T, such as T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, such as R antennas (r≡1).

At base station 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may 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. The transmit processor 220 may 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 Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232T). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232a through 232T may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234T).

At UE 120, antenna set 252 (shown as antennas 252a through 252R) may receive downlink signals from base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254R). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal using a corresponding demodulator component to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to controller/processor 280. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter, etc. In some examples, one or more components of UE 120 may be included in housing 284.

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

The one or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, etc. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements (within a single housing or multiple housings), a coplanar antenna element set, a non-coplanar antenna element set, and/or one or more antenna elements coupled to one or more transmit and/or receive components (such as one or more components of fig. 2).

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ and/or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 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., with reference to fig. 3-12).

At base station 110, uplink signals from UE 120 and/or other UEs may be received by antennas 234, processed by modems 232 (e.g., demodulator components of modems 232, shown as DEMODs), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 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., with reference to fig. 3-12).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component of fig. 2 may perform one or more techniques associated with a set of PUCCH resources with or without parameters per PUCCH resource, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations such as process 400 of fig. 4, process 500 of fig. 5, process 900 of fig. 9, process 1000 of fig. 10, and/or other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, 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, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly or after compiling, converting, and/or interpreting), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 400 of fig. 4, process 500 of fig. 5, and/or other processes as described herein. In some examples, the execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions, among others.

In some aspects, UE 120 includes: means for receiving a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH-resource parameters, and wherein PUCCH resources in the second PUCCH resource subset do not include per-PUCCH-resource parameters; means for identifying parameters to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration; and/or means for transmitting one or more repetitions of PUCCH communication based at least in part on the parameter. The means for the UE to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller/processor 280, or the memory 282.

In some aspects, the base station 110 includes: means for transmitting a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with per-PUCCH-resource parameters, and wherein PUCCH resources in the second PUCCH resource subset do not include per-PUCCH-resource parameters; means for identifying parameters to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration; and/or means for receiving one or more repetitions of PUCCH communications based at least in part on the parameter. The means for a base station to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Although the blocks in fig. 2 are shown as distinct components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and/or TX MIMO processor 266 may be performed by controller/processor 280 or under the control of controller/processor 280.

As indicated above, fig. 2 is provided as an example. Other examples may differ from that described with respect to fig. 2.

In some wireless communication systems, PUCCH repetition may be used to improve PUCCH reliability and coverage, such as for ultra-reliable low latency communications (URLLC) or for UEs 120 located in geographic areas with poor channel conditions (e.g., cell edges). When repetition is used, the transmitter repeats the transmission of the communication a plurality of times. For example, UE 120 may transmit an initial PUCCH communication and may repeat the transmission of the PUCCH communication one or more times (e.g., may retransmit). In some aspects, the repeated transmission (sometimes referred to as a retransmission) may include the same encoded bits (e.g., information bits and parity bits) as the initial transmission and/or another repeated transmission (e.g., where the same redundancy version is used across the repetitions). Alternatively, the repeated transmission may include different encoded bits (e.g., different combinations of information bits and/or parity bits) than the initial transmission and/or another repeated transmission (e.g., where different redundancy versions are used across the repetitions).

As used herein, the term "repetition" is used to refer to an initial communication, and is also used to refer to the transmission of repetitions of the initial communication. For example, if UE 120 is configured to send four repetitions, UE 120 may send an initial transmission and may send a transmission of three repetitions of the initial transmission. Thus, each transmission (whether the transmission is an initial transmission or a retransmission) is counted as a repetition. Further, the term "repetition factor" is used to refer to an indication of the number of repetitions of a communication to be transmitted by UE 120. For example, if UE 120 identifies a repetition factor of four for a given uplink communication, UE 120 may determine that UE 120 is to transmit four repetitions of the given uplink communication. The repetition may be sent in a transmission opportunity (sometimes referred to as a transmission instance).

In some wireless communication systems, a repetition factor (referred to herein as a PUCCH repetition factor) to be used for PUCCH communication may be dynamically indicated. For example, UE 120 may be configured to identify PUCCH resources to be used for PUCCH communication from a pool of 16 PUCCH resources configured for UE 120 using a combination of PUCCH Resource Indicators (PRIs) and allocated Control Channel Elements (CCEs). PRI is a three-bit field carried in a Physical Downlink Control Channel (PDCCH) in Downlink Control Information (DCI) for allocating a Physical Downlink Shared Channel (PDSCH). The allocated CCE may be, for example, the first CCE location of the PDCCH. The index of the allocated CCE is used to calculate single bit information. The combined set of 4 bits (three bits from PRI and one bit from allocated CCE) is used to identify PUCCH resources from the pool of 16 PUCCH resources. Here, the repetition factor may be configured for each PUCCH resource in the pool of 16 PUCCH resources, which means that the PUCCH repetition factor may be dynamically indicated by the PRI in the DCI.

But the maximum number of PUCCH resources that can be indicated in this way is limited. For example, the size of the PUCCH resource pool (e.g., 16 PUCCH resources) may not be sufficient to enable partitioning of PUCCH resources based on different possible repetition factors (e.g., 1, 2, 4, 8, etc.) without significantly reducing the flexibility of the base station 110 in selecting PUCCH resources. What is needed is a technique that enables dynamic indication of PUCCH repetition factors without increasing the length of PRI or reducing the flexibility of PUCCH resource selection (i.e., avoiding too few PUCCH resources associated with each repetition factor due to dividing all PUCCH resources among the possible repetition factor options).

Some techniques and apparatuses described herein implement PUCCH resource sets with or without repetition factors per PUCCH resource. In some aspects, UE 120 may receive a PUCCH resource set configuration including a first PUCCH resource subset and a second PUCCH resource subset. Here, the PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and the PUCCH resources in the second PUCCH resource subset do not include a repetition factor per PUCCH resource. UE 120 may identify a repetition factor to use for PUCCH communications based at least in part on the PUCCH resource set configuration and may transmit one or more repetitions of PUCCH communications based at least in part on the repetition factor. Additional details are provided below. In this way, PUCCH repetition factors may be dynamically indicated without the need to increase the length of PRI or significantly reduce the flexibility of PUCCH resource selection, which means that improved reliability and coverage achieved by dynamic indication of PUCCH repetition factors may be provided without significantly affecting overhead or flexibility.

Fig. 3 is a diagram illustrating an example 300 associated with a PUCCH resource set with or without a repetition factor per PUCCH resource in accordance with the present disclosure. As shown in fig. 3, example 300 includes communication between base station 110 and UE 120. In some aspects, base station 110 and UE 120 may be included in a wireless network, such as wireless network 100. Base station 110 and UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

As shown in fig. 3, with reference numeral 305, the base station 110 may transmit and the UE 120 may receive a PUCCH resource set configuration including a first PUCCH resource subset and a second PUCCH resource subset. The PUCCH resource set configuration is a configuration indicating a PUCCH resource set that may be used by UE 120 in order to transmit PUCCH communications. That is, the PUCCH resource set configuration includes information associated with the PUCCH resource set, where a given PUCCH communication may be transmitted by UE 120 using PUCCH resources from the PUCCH resource set. In some aspects, the PUCCH resource configuration includes a first PUCCH resource subset and a second PUCCH resource subset.

In some aspects, PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource. That is, the first subset of PUCCH resources includes one or more PUCCH resources, wherein each PUCCH resource in the first subset of PUCCH resources is configured with a respective repetition factor (e.g. 1,2, 4, 8, etc.). In some aspects, PUCCH resources in the second PUCCH resource subset are not configured with (i.e. do not include) a repetition factor per PUCCH resource. That is, the second subset of PUCCH resources includes one or more PUCCH resources for which a repetition factor is not configured.

As an example, the PUCCH resource set configuration may indicate eight PUCCH resources corresponding to indexes 0 to 7. Here, the first PUCCH resource subset may include PUCCH resources corresponding to indexes 5 to 7, and the second PUCCH resource subset may include PUCCH resources corresponding to indexes 0 to 4. In this example, PUCCH resources associated with index 5 may be configured with repetition factor 2, PUCCH resources associated with index 6 may be configured with repetition factor 4, and PUCCH resources associated with index 7 may be configured with repetition factor 8. Further, PUCCH resources corresponding to index 0, index 1, index 2, index 3, and index 4 may not be configured with an associated repetition factor.

As indicated by reference numeral 310, UE 120 may identify a repetition factor to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration. For example, UE 120 may identify PUCCH resources to be used for transmitting PUCCH communications. In some aspects, UE 120 may identify PUCCH resources to use for transmitting PUCCH communications based on, for example, PRI (e.g., received in DCI), a location of CCEs, a dynamic indication, or some combination thereof. Here, the PUCCH resource identified for transmitting PUCCH communication may be a PUCCH resource included in a PUCCH resource set configured by PUCCH resource set configuration. Next, UE 120 may identify whether PUCCH resources are configured with a repetition factor in the PUCCH resource set configuration (i.e., whether the identified PUCCH resources are in the first PUCCH resource subset or the second PUCCH resource subset).

In some aspects, if PUCCH resources to be used for transmitting PUCCH communications are included in the first PUCCH resource subset, UE 120 may identify the repetition factor based at least in part on a repetition factor associated with the PUCCH resources as configured in the PUCCH resource set configuration. That is, UE 120 may identify that PUCCH resources in the first subset of PUCCH resources are to be used for transmitting PUCCH communications, and when identifying a repetition factor, UE 120 may identify the repetition factor as a repetition factor associated with PUCCH resources in the PUCCH resource set configuration. As a particular example, and continuing with the above example, UE 120 may receive a PRI indicating that PUCCH resources associated with index 7 are to be used for PUCCH communications. Here, UE 120 may determine that the PUCCH resource associated with index 7 has a repetition factor (e.g., repetition factor 8) configured in the PUCCH resource set configuration, and thus may identify the repetition factor for PUCCH communication as 8.

Conversely, in some aspects, if PUCCH resources to be used for transmitting PUCCH communications are included in the second subset of PUCCH resources, UE 120 may identify the repetition factor in another manner, such as based at least in part on the repetition factor configured for the PUCCH format to be used for PUCCH communications. That is, UE 120 may identify that PUCCH resources in the second subset of PUCCH resources are to be used for transmitting PUCCH communications, and when identifying repetition factors, may identify the repetition factors based at least in part on information not associated with the PUCCH resource set configuration (e.g., repetition factors configured for PUCCH formats to be used for PUCCH communications). As a particular example, and continuing with the above example, UE 120 may receive a PRI indicating that PUCCH resources associated with index 3 are to be used for PUCCH communications. Here, UE 120 may determine that the PUCCH resource associated with index 3 is not configured with the repetition factor in the PUCCH resource set configuration, and thus may identify the repetition factor for PUCCH communication as a (default) repetition factor configured for the PUCCH format to be used for transmitting PUCCH communication.

In some aspects, the PUCCH communication includes acknowledgement information associated with the scheduled PDSCH communication. That is, in some aspects, the PUCCH communication may be a PUCCH communication associated with an Acknowledgement (ACK) or Negative ACK (NACK) that carries a data packet for a scheduled PDSCH (e.g., a PDSCH scheduled by a PDCCH carrying DCI including PRI).

In some aspects, the PUCCH communication includes acknowledgement information associated with a semi-persistent scheduling (SPS) communication. That is, in some aspects, the PUCCH communication may be a PUCCH communication associated with carrying an ACK or NACK for SPS communication.

In some aspects, the PUCCH communication includes a Scheduling Request (SR). That is, in some aspects, the PUCCH communication may be an SR.

In some aspects, the PUCCH communication includes Channel State Information (CSI). That is, in some aspects, the PUCCH communication may be a PUCCH communication associated with carrying CSI.

As indicated by reference numeral 315, the base station 110 can identify a repetition factor to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration. For example, base station 110 may select PUCCH resources to be used by UE 120 to transmit PUCCH communications, and may indicate the PUCCH resources to UE 120 as described above. In some aspects, base station 110 may select PUCCH resources based at least in part on a repetition factor to be used for PUCCH communications (e.g., base station 110 may select PUCCH resources such that UE 120 uses the repetition factor desired by base station 110). Next, in association with receiving the PUCCH communication, the base station 110 may identify a repetition factor associated with the PUCCH communication. In some aspects, base station 110 may identify the repetition factor based at least in part on a PUCCH resource set configuration associated with UE 120 (e.g., in a manner similar to that of UE 120 described above). For example, in association with receiving PUCCH communications, base station 110 may determine whether PUCCH resources to be used by UE 120 for transmitting PUCCH communications are in the first PUCCH resource subset or the second PUCCH resource subset, and may identify the repetition factor accordingly (e.g., in a manner similar to that of UE 120). Base station 110 may then receive one or more repetitions of PUCCH communications according to the identified repetition factor.

As indicated by reference numeral 320, UE 120 may transmit based at least in part on the repetition factor and base station 110 may receive one or more repetitions of PUCCH communications. For example, UE 120 may transmit one or more repetitions of PUCCH communications in PUCCH resources and according to the identified repetition factor, and base station 110 may receive the one or more repetitions of PUCCH communications accordingly.

As described above, fig. 3 is provided as an example. Other examples may differ from that described with respect to fig. 3.

Fig. 4 is a diagram illustrating an example process 400 performed, for example, by a UE, in accordance with the present disclosure. Example process 400 is an example in which a UE (e.g., UE 120) performs operations associated with a set of PUCCH resources with or without a repetition factor per PUCCH resource.

As shown in fig. 4, in some aspects, process 400 may include: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not comprise a repetition factor per PUCCH resource (block 410). For example, the UE (e.g., using the communication manager 140 and/or the receiving component 602 depicted in fig. 6) may receive a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include a repetition factor per PUCCH resource, as described above.

As further shown in fig. 4, in some aspects, process 400 may include: a repetition factor to be used for transmitting PUCCH communications is identified based at least in part on the PUCCH resource set configuration (block 420). For example, the UE (e.g., using the communication manager 140 and/or the identifying component 608 depicted in diagram 608) may identify a repetition factor to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration, as described above.

As further shown in fig. 4, in some aspects, process 400 may include: one or more repetitions of PUCCH communications are transmitted based at least in part on the repetition factor (block 430). For example, the UE (e.g., using the communication manager 140 and/or the transmitting component 604 depicted in fig. 6) may transmit one or more repetitions of PUCCH communication based at least in part on the repetition factor, as described above.

Process 400 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the process 400 includes: identifying PUCCH resources in the first subset of PUCCH resources to be used for transmitting PUCCH communications, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on the repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration.

In a second aspect, alone or in combination with the first aspect, the process 400 includes: identifying PUCCH resources in the second subset of PUCCH resources to be used for transmitting PUCCH communications, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for PUCCH communications.

In a third aspect, alone or in combination with one or more of the first and second aspects, the process 400 includes: PUCCH resources to be used for transmitting PUCCH communications are identified based at least in part on at least one of PRI, a location of CCE, or a dynamic indication.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PUCCH communication includes acknowledgement information associated with the scheduled PDSCH communication.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PUCCH communication includes acknowledgement information associated with the SPS communication.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the PUCCH communication comprises an SR.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the PUCCH communication includes CSI.

While fig. 4 shows example blocks of the process 400, in some aspects, the process 400 may include more blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 4. Additionally or alternatively, two or more of the blocks of process 400 may be performed in parallel.

Fig. 5 is a diagram illustrating an example process 500 performed, for example, by a base station, in accordance with the present disclosure. Example process 500 is an example in which a base station (e.g., base station 110) performs operations associated with a set of PUCCH resources with or without a repetition factor per PUCCH resource.

As shown in fig. 5, in some aspects, process 500 may include: a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is transmitted, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not comprise a repetition factor per PUCCH resource (block 510). For example, the base station (e.g., using the communication manager 150 and/or the transmitting component 704 depicted in fig. 7) may transmit a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include a repetition factor per PUCCH resource, as described above.

As further shown in fig. 5, in some aspects, process 500 may include: a repetition factor to be used for receiving PUCCH communications is identified based at least in part on the PUCCH resource set configuration (block 520). For example, the base station (e.g., using the communication manager 150 and/or the identifying component 708 depicted in fig. 7) can identify a repetition factor to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration, as described above.

As further shown in fig. 5, in some aspects, process 500 may include: one or more repetitions of PUCCH communications are received based at least in part on the repetition factor (block 530). For example, a base station (e.g., using the communication manager 150 and/or the receiving component 702 depicted in fig. 7) can receive one or more repetitions of PUCCH communication based at least in part on the repetition factor, as described above.

Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the process 500 includes: identifying PUCCH resources in the first subset of PUCCH resources to be used for transmitting PUCCH communications, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on the repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration.

In a second aspect, alone or in combination with the first aspect, the process 500 includes: identifying PUCCH resources in the second subset of PUCCH resources to be used for transmitting PUCCH communications, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for PUCCH communications.

In a third aspect, alone or in combination with one or more of the first and second aspects, the PUCCH communication includes acknowledgement information associated with the scheduled PDSCH communication.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PUCCH communication includes acknowledgement information associated with the SPS communication.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PUCCH communication comprises an SR.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the PUCCH communication includes CSI.

While fig. 5 shows example blocks of the process 500, in some aspects, the process 500 may include more blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

Fig. 6 is a diagram of an example apparatus 600 for wireless communications. The apparatus 600 may be a UE, or the UE may include the apparatus 600. In some aspects, the apparatus 600 includes a receiving component 602 and a transmitting component 604 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 600 may communicate with another apparatus 606 (such as a UE, a base station, or another wireless communication device) using a receiving component 602 and a transmitting component 604. As further shown, the apparatus 600 may include a communication manager 140. The communications manager 140 can include an identification component 608 or the like.

In some aspects, the apparatus 600 may be configured to perform one or more operations described herein in connection with fig. 3. Additionally or alternatively, the apparatus 600 may be configured to perform one or more processes described herein, such as process 400 of fig. 4. In some aspects, the apparatus 600 and/or one or more components illustrated in fig. 6 may include one or more components of the UE described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 6 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented 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 executable by a controller or processor to perform functions or operations of the component.

The receiving component 602 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 606. The receiving component 602 may provide the received communication to one or more other components of the apparatus 600. In some aspects, the receiving component 602 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 600. In some aspects, the receive component 602 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a UE described in connection with fig. 2.

The transmitting component 604 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 606. In some aspects, one or more other components of apparatus 600 may generate a communication and may provide the generated communication to sending component 604 for transmission to apparatus 606. In some aspects, the transmitting component 604 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, or the like) on the generated communication and can transmit the processed signal to the device 606. In some aspects, the transmitting component 604 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the UE described in connection with fig. 2. In some aspects, the transmitting component 604 can be co-located with the receiving component 602 in a transceiver.

The receiving component 602 may receive a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not comprise a repetition factor per PUCCH resource. The identifying component 608 can identify a repetition factor to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration. The transmitting component 604 can transmit one or more repetitions of PUCCH communications based at least in part on the repetition factor.

The identifying component 608 can identify that PUCCH resources in the first subset of PUCCH resources are to be used for transmitting PUCCH communications.

The identifying component 608 can identify PUCCH resources in the second PUCCH resource subset to be used for transmitting PUCCH communications.

The identifying component 608 can identify PUCCH resources to be utilized for transmitting PUCCH communications based at least in part on at least one of PRI, location of CCE, or dynamic indication.

The number and arrangement of components shown in fig. 6 are provided as examples. In practice, there may be more components, fewer components, different components, or differently arranged components than those shown in fig. 6. Further, two or more components shown in fig. 6 may be implemented within a single component, or a single component shown in fig. 6 may be implemented as multiple distributed components. Additionally or alternatively, one set (one or more) of components shown in fig. 6 may perform one or more functions described as being performed by another set of components shown in fig. 6.

Fig. 7 is a diagram of an example apparatus 700 for wireless communication. The apparatus 700 may be a base station or the base station may include the apparatus 700. In some aspects, the apparatus 700 includes a receiving component 702 and a transmitting component 704 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 700 may communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using a receiving component 702 and a transmitting component 704. As further shown, the apparatus 700 may include a communication manager 150. The communications manager 150 can include an identification component 708 or the like.

In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with fig. 3. Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as the process 500 of fig. 5. In some aspects, the apparatus 700 and/or one or more components illustrated in fig. 7 may include one or more components of a base station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 7 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented 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 executable by a controller or processor to perform functions or operations of the component.

The receiving component 702 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 706. The receiving component 702 can provide the received communication to one or more other components of the apparatus 700. In some aspects, the receiving component 702 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 700. In some aspects, the receiving component 702 can include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a base station described in connection with fig. 2.

The transmitting component 704 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 706. In some aspects, one or more other components of apparatus 700 may generate a communication, and may provide the generated communication to sending component 704 for transmission to apparatus 706. In some aspects, the transmitting component 704 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, or the like) on the generated communication and can transmit the processed signal to the device 706. In some aspects, the transmit component 704 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the base station described in connection with fig. 2. In some aspects, the transmitting component 704 can be co-located with the receiving component 702 in a transceiver.

The transmitting component 704 may transmit a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with repetition factors per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not comprise repetition factors per PUCCH resource. The identifying component 708 can identify a repetition factor to be used for receiving the PUCCH communication based at least in part on the PUCCH resource set configuration. The receiving component 702 can receive one or more repetitions of PUCCH communications based at least in part on the repetition factor.

The identifying component 708 can identify that PUCCH resources in the first subset of PUCCH resources are to be used for transmitting PUCCH communications.

The identifying component 708 can identify that PUCCH resources in the second subset of PUCCH resources are to be used for transmitting PUCCH communications.

The number and arrangement of components shown in fig. 7 are provided as examples. In practice, there may be more components, fewer components, different components, or differently arranged components than those shown in fig. 7. Further, two or more components shown in fig. 7 may be implemented within a single component, or a single component shown in fig. 7 may be implemented as multiple distributed components. Additionally or alternatively, one set (one or more) of components shown in fig. 7 may perform one or more functions described as being performed by another set of components shown in fig. 7.

The base station may dynamically change the PUCCH repetition factor by configuring repetition on a per PUCCH resource set basis. Similarly, the base station may dynamically change DMRS bundling for PUCCH repetition. Maintaining the same frequency hopping configuration may cause communication problems between the base station and the UE when frequency hopping is enabled and the base station changes DMRS bundling for PUCCH repetition. For example, an inter-slot frequency hopping pattern that alternates based on even slots and odd slots may not be suitable for some DMRS bundling configurations. One problem may be that the maximum number of PUCCH resources that may be identified by PRI may not be sufficient to accommodate all available PUCCH resources with different repetition factors. Increasing the size of the PRI may allow for additional PUCCH resources to be indicated, but result in excessive use of network resources to transmit larger PRIs.

Some aspects described herein enable dynamic indication of frequency hopping by enabling a base station to configure a set of hybrid PUCCH resources with and without inter-slot frequency hopping configured on a per PUCCH resource basis. For example, the base station may configure a PUCCH resource set comprising a first PUCCH resource subset configured for inter-slot frequency hopping per PUCCH resource and a second PUCCH resource subset not configured with an associated configuration for frequency hopping on a per PUCCH resource basis. In this case, the base station may use an indicator (e.g., PRI, CCE location, or other dynamic indication) to identify PUCCH resources in the PUCCH resource set as being configured for inter-slot hopping per PUCCH resource (e.g., in the first PUCCH resource subset), or not being configured with an associated configuration for hopping on a per PUCCH resource basis. Based at least in part on whether the PUCCH resources are in the first PUCCH resource subset or the second PUCCH resource subset, the UE may determine whether to perform inter-slot frequency hopping for transmission of one or more PUCCH repetitions. In this way, the UE and base station enable dynamic indication of frequency hopping without increasing the length of PRI or other indicators and without limiting the flexibility of PUCCH resource selection. In this way, the UE and base station improve communications relative to not allowing dynamic indication of frequency hopping, extending PRI or other indicators, or limiting flexibility in PUCCH resource selection, etc.

Fig. 8 is a diagram illustrating an example 800 associated with hybrid PUCCH resource set usage in accordance with the present disclosure. As shown in fig. 8, example 800 includes communication between base station 110 and UE 120. In some aspects, base station 110 and UE 120 may be included in a wireless network, such as wireless network 100. Base station 110 and UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

As shown in fig. 8 and further by reference numeral 810, base station 110 may configure a PUCCH resource set. For example, base station 110 may send signaling to UE 120 identifying the set of PUCCH resources. In this case, the PUCCH resource set may include a first PUCCH resource subset and a second PUCCH resource subset. The first PUCCH resource subset may include one or more PUCCH resources configured with a configuration for inter-slot frequency hopping per PUCCH resource. In contrast, the second set of PUCCH resources is not configured with an associated configuration for inter-slot frequency hopping of each PUCCH resource. In some aspects, the first PUCCH resource subset may be associated with a configuration of one or more parameters related to frequency hopping and/or frequency hopping performed at frequency hopping. For example, UE 120 may receive signaling identifying: a starting resource block (e.g., startingPRB parameters) for the first PUCCH resource subset and/or the corresponding PUCCH resource for the first PUCCH resource subset, a second resource block (e.g., secondHopPRB parameters) for the first PUCCH resource subset and/or the corresponding PUCCH resource for the first PUCCH resource subset (e.g., in a different symbol or resource position than the starting resource block), or a frequency offset between frequency hops, etc.

Additionally or alternatively, UE 120 may receive signaling identifying a frequency hopping pattern for the first PUCCH resource subset and/or the respective PUCCH resource for the first PUCCH resource subset. Examples of frequency hopping patterns may include ABAB type (i.e., alternating) frequency hopping patterns (where a represents using a first resource block position within a slot and B represents using a second resource block position within a slot), AABB type (i.e., consecutive block) frequency hopping patterns, slot index-based frequency hopping patterns (where a resource block position corresponds to whether the index of a slot is odd or even, or corresponds to the size of the index of a slot), or any other type of pattern. Although described herein in terms of two hops, any other number of hops (e.g., three hops or more) is possible for the hopping pattern.

In some aspects, UE 120 may determine a hopping pattern for the first subset of PUCCH resources (e.g., hopping for each PUCCH resource) based at least in part on the other configured parameter. For example, UE 120 may use a first frequency hopping pattern when DMRS bundling is activated or enabled for PUCCH resource groups and a second frequency hopping pattern when DMRS bundling is not activated or enabled for PUCCH resource groups. In this case, when UE 120 receives a PRI indicating deactivation or activation of DMRS bundling, UE 120 may change the associated frequency hopping pattern (e.g., from the first frequency hopping pattern to the second frequency hopping pattern). Additionally or alternatively, UE 120 may deactivate frequency hopping based at least in part on the PRI indicating activation of DMRS bundling. Additionally or alternatively, UE 120 may receive another type of signaling (e.g., layer 1 (L1) or layer 2 (L2) signaling, such as DCI or downlink MAC-CE) configuring or activating/deactivating DMRS bundling, and may change the interpretation of the hopping configuration (e.g., by changing the hopping pattern, the hopping parameters, whether to perform hopping based at least in part on PUCCH format, as described above, etc.).

In some aspects, UE 120 may determine to enable frequency hopping based at least in part on the indication received from base station 110. For example, UE 120 may determine that frequency hopping is enabled for the first PUCCH resource subset and/or the respective PUCCH resource of the first PUCCH resource subset based at least in part on the configuration of the first PUCCH resource subset and/or the configuration of the respective PUCCH resource for the first PUCCH resource subset. Additionally or alternatively, UE 120 may determine that frequency hopping is enabled for one or more PUCCH resources in the second PUCCH resource subset. For example, when the indication (e.g., PRI or CCE location) indicates that the particular PUCCH resource does not have a configuration for frequency hopping per PUCCH resource, UE 120 may determine that frequency hopping is enabled for the PUCCH format of the particular PUCCH resource in the second PUCCH resource subset based at least in part on other factors. For example, UE 120 may determine to enable frequency hopping for a particular PUCCH resource based at least in part on a format of the particular PUCCH resource, although the particular PUCCH resource does not have an associated configuration for frequency hopping per PUCCH resource. In this case, UE 120 may use the received configuration information associated with configuring frequency hopping for different PUCCH formats and may determine whether frequency hopping is enabled for a particular PUCCH resource based at least in part on the PUCCH format of the particular PUCCH resource. In other words, if PUCCH resources are not configured with an associated frequency hopping configuration on a per PUCCH resource basis (e.g., resources in the second PUCCH resource subset), whether frequency hopping is enabled for the PUCCH resources may be based at least in part on the PUCCH format associated with the PUCCH resources. For example, frequency hopping for PUCCH resources may be enabled for a first PUCCH format and frequency hopping for PUCCH resources may be disabled for a second PUCCH format.

In some aspects, UE 120 may determine to disable frequency hopping based at least in part on the indication received from base station 110. For example, PUCCH resources may be configured to be disabled for frequency hopping (e.g., based on PRI, based on each PUCCH resource). The PUCCH resources may be disabled for frequency hopping regardless of or independent of the PUCCH format of the PUCCH resources. For example, if the PUCCH resource is configured with a repetition factor to be used without frequency hopping, the PUCCH resource will be disabled from frequency hopping even if the PUCCH format of the PUCCH resource defaults to frequency hopping.

As shown in fig. 8 and further by reference numeral 820, UE 120 may transmit using one or more PUCCH resources. For example, UE 120 may transmit repetitions of PUCCH communications using frequency hopping in the first PUCCH resource subset or transmit repetitions of PUCCH communications using frequency hopping in the first PUCCH resource subset and the second PUCCH resource subset. Additionally or alternatively, UE 120 may use frequency hopping to transmit repetitions of PUCCH communications in the following PUCCH resources: the PUCCH resources do not have a configuration for frequency hopping on a per PUCCH resource basis (e.g. a second PUCCH resource subset), but are associated with a particular PUCCH format for which frequency hopping is configured. Additionally or alternatively, UE 120 may transmit one or more repetitions of PUCCH communication without frequency hopping (e.g., in PUCCH resources for which frequency hopping is not configured or when frequency hopping is to be disabled, such as when DMRS bundling is enabled).

As an illustrative example, UE 120 may be configured with a set of PUCCH resources, which may include 8 PUCCH resources, where resources 0 and 1,2, and 3 are not configured with associated repetition factors, resources 4 and 5 are configured with repetition factors 2 and 4, respectively (no configuration for frequency hopping), resource 6 is configured with repetition factor 4 with frequency hopping enabled, and resource 7 is configured with repetition factor 4 with frequency hopping disabled. In this case, UE 120 may receive the PRI indicating resource 7, and UE 120 may transmit using repetition factor 4 (e.g., 4 PUCCH repetitions) without frequency hopping (e.g., as a result of frequency hopping being configured but disabled, regardless of PUCCH format configuration). In contrast, UE 120 may receive a PRI indicating resource 6, and UE 120 may transmit with a frequency hopping usage repetition factor of 4 (e.g., with parameters indicated in the configuration for PUCCH resource 6). Also in contrast, UE 120 may receive a PRI indicating resource 5 and may transmit using repetition factor 4, where frequency hopping depends on PUCCH format configuration (e.g., since resource 5 is not configured with a configuration for frequency hopping).

In some aspects, UE 120 may transmit a PUCCH of a particular format conveying a particular type of information. For example, UE 120 may transmit a PUCCH conveying a hybrid automatic repeat request (HARQ) Acknowledgement (ACK) or a Negative Acknowledgement (NACK) for the scheduled PDSCH. Additionally or alternatively, UE 120 may transmit a PUCCH conveying HARQ ACK/NACK feedback for semi-persistent scheduling (SPS) communications. Additionally or alternatively, UE 120 may send a PUCCH conveying a Scheduling Request (SR) or CSI report.

As described above, fig. 8 is provided as an example. Other examples may differ from that described with respect to fig. 8.

Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE, in accordance with the present disclosure. Example process 900 is an example in which a UE (e.g., UE 120) performs operations associated with a set of hybrid physical uplink control channel resources.

As shown in fig. 9, in some aspects, process 900 may include: information identifying a PUCCH resource set is received, wherein the PUCCH resource set includes a first PUCCH resource subset configured for frequency hopping per PUCCH resource and a second PUCCH resource subset not configured with an associated configuration for frequency hopping per PUCCH resource (block 910). For example, the UE (e.g., using the communication manager 140 and/or the receiving component 1102 depicted in fig. 11) may receive information identifying a set of PUCCH resources, wherein the set of PUCCH resources includes a first subset of PUCCH resources configured for frequency hopping per PUCCH resource and a second subset of PUCCH resources not configured with an associated configuration for frequency hopping per PUCCH resource, as described above.

As further shown in fig. 9, in some aspects, process 900 may include: one or more PUCCH communications are transmitted using one or more PUCCH resources in a set of PUCCH resources with frequency hopping (block 920). For example, the UE (e.g., using communication manager 140 and/or transmission component 1104 depicted in fig. 11) may transmit one or more PUCCH communications using one or more PUCCH resources in the set of PUCCH resources using frequency hopping, as described above.

Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the frequency hopping is inter-slot frequency hopping.

In a second aspect, alone or in combination with the first aspect, the first PUCCH resource subset is associated with a set of configuration parameters for frequency hopping, wherein the set of configuration parameters includes information identifying at least one of a starting resource block, a frequency offset, or a frequency hopping pattern.

In a third aspect, alone or in combination with one or more of the first and second aspects, the indication associated with transmitting the one or more PUCCH communications identifies an associated configured PUCCH resource in the second PUCCH resource subset that is not configured with frequency hopping for each PUCCH resource, and wherein whether a PUCCH resource is associated with frequency hopping is based at least in part on a PUCCH format of the one or more PUCCH resources.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first PUCCH resource subset is associated with a configuration for at least one of: a starting physical resource block, a physical resource block for frequency hopping, a frequency offset, a single frequency hopping, multiple frequency hopping, or a pattern for frequency hopping.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the pattern of frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on an index of a slot in which one or more PUCCH communications are transmitted.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the pattern for frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on whether demodulation reference signal bundling is in an active state.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, one or more PUCCH resources are associated with conveying at least one of: hybrid automatic repeat request feedback messages for scheduled physical downlink shared channels, hybrid automatic repeat request feedback messages for semi-persistently scheduled communications, scheduling requests, or channel state information messages.

While fig. 9 shows example blocks of process 900, in some aspects process 900 may include more blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

Fig. 10 is a diagram illustrating an example process 1000 performed, for example, by a base station in accordance with the present disclosure. Example process 1000 is an example in which a base station (e.g., base station 110) performs operations associated with a hybrid PUCCH resource set.

As shown in fig. 10, in some aspects, process 1000 may include: information identifying a PUCCH resource set is transmitted, wherein the PUCCH resource set includes a first PUCCH resource subset configured for frequency hopping per PUCCH resource and a second PUCCH resource subset not configured with an associated configuration for frequency hopping per PUCCH resource (block 1010). For example, the base station (e.g., using the communication manager 150 and/or the transmission component 1204 depicted in fig. 12) may transmit information identifying a set of PUCCH resources, wherein the set of PUCCH resources includes a first subset of PUCCH resources configured for frequency hopping per PUCCH resource and a second subset of PUCCH resources not configured with an associated configuration for frequency hopping per PUCCH resource, as described above.

As further shown in fig. 10, in some aspects, process 1000 may include: one or more PUCCH communications transmitted using one or more PUCCH resources in a set of frequency hopped PUCCH resources are received (block 1020). For example, a base station (e.g., using communication manager 150 and/or receiving component 1202 depicted in fig. 12) may receive one or more PUCCH communications transmitted using one or more PUCCH resources in a set of frequency hopping-using PUCCH resources, as described above.

Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the frequency hopping is inter-slot frequency hopping.

In a second aspect, alone or in combination with the first aspect, the first PUCCH resource subset is associated with a set of configuration parameters for frequency hopping, wherein the set of configuration parameters includes information identifying at least one of a starting resource block, a frequency offset, or a frequency hopping pattern.

In a third aspect, alone or in combination with one or more of the first and second aspects, the indication associated with transmitting the one or more PUCCH communications identifies an associated configured PUCCH resource in the second PUCCH resource subset that is not configured with frequency hopping for each PUCCH resource, and wherein whether a PUCCH resource is associated with frequency hopping is based at least in part on a PUCCH format of the one or more PUCCH resources.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first PUCCH resource subset is associated with a configuration for at least one of: a starting physical resource block, a physical resource block for frequency hopping, a frequency offset, a single frequency hopping, multiple frequency hopping, or a pattern for frequency hopping.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the pattern of frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on an index of a slot in which one or more PUCCH communications are transmitted.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the pattern for frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on whether demodulation reference signal bundling is in an active state.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, one or more PUCCH resources are associated with conveying at least one of: hybrid automatic repeat request feedback messages for scheduled physical downlink shared channels, hybrid automatic repeat request feedback messages for semi-persistently scheduled communications, scheduling requests, or channel state information messages.

While fig. 10 shows example blocks of process 1000, in some aspects process 1000 may include more blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

Fig. 11 is a diagram of an example apparatus 1100 for wireless communications. The apparatus 1100 may be a UE, or the UE may include the apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106, such as a UE, a base station, or another wireless communication device, using a receiving component 1102 and a transmitting component 1104. As further shown, the apparatus 1100 may include a communication manager 140. The communication manager 140 may include a frequency hopping component 1108 or the like.

In some aspects, apparatus 1100 may be configured to perform one or more operations described herein in connection with fig. 8. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of fig. 9. In some aspects, the apparatus 1100 and/or one or more components illustrated in fig. 11 may include one or more components of the UE described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 11 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented 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 executable by a controller or processor to perform functions or operations of the component.

The receiving component 1102 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 1106. The receiving component 1102 can provide the received communication to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a UE described in connection with fig. 2.

The transmission component 1104 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 1106. In some aspects, one or more other components of apparatus 1100 may generate a communication, and the generated communication may be provided to send component 1104 for transmission to apparatus 1106. In some aspects, the transmission component 1104 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, or the like) on the generated communication and can transmit the processed signal to the device 1106. In some aspects, the transmit component 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or combinations thereof of the UE described in connection with fig. 2. In some aspects, the sending component 1104 may be co-located with the receiving component 1102 in a transceiver.

The receiving component 1102 may receive information identifying a PUCCH resource set, wherein the PUCCH resource set includes a first PUCCH resource subset configured for frequency hopping per PUCCH resource and a second PUCCH resource subset not configured with an associated configuration for frequency hopping per PUCCH resource. The transmitting component 1104 may transmit one or more PUCCH communications using one or more PUCCH resources in the set of PUCCH resources using frequency hopping. Frequency hopping component 1108 can perform frequency hopping on one or more PUCCH resources based at least in part on an indication to communicate using PUCCH resources configured for resource hopping per PUCCH resource.

The number and arrangement of components shown in fig. 11 are provided as examples. In practice, there may be more components, fewer components, different components, or differently arranged components than those shown in FIG. 11. Further, two or more components shown in fig. 11 may be implemented within a single component, or a single component shown in fig. 11 may be implemented as multiple distributed components. Additionally or alternatively, one set (one or more) of components shown in fig. 11 may perform one or more functions described as being performed by another set of components shown in fig. 11.

Fig. 12 is a diagram of an example apparatus 1200 for wireless communications. The apparatus 1200 may be a base station or the base station may include the apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using a receiving component 1202 and a transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 150. The communications manager 150 may include a configuration component 1208 or the like.

In some aspects, apparatus 1200 may be configured to perform one or more operations described herein in connection with fig. 8. Additionally or alternatively, apparatus 1200 may be configured to perform one or more processes described herein, such as process 1000 of fig. 10. In some aspects, the apparatus 1200 and/or one or more components shown in fig. 12 may include one or more components of a base station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 12 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be at least partially implemented 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 executable by a controller or processor to perform functions or operations of the component.

The receiving component 1202 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206. The receiving component 1202 may provide the received communication to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 can include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a base station described in connection with fig. 2.

The transmitting component 1204 can transmit a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 1206. In some aspects, one or more other components of apparatus 1200 may generate a communication and may provide the generated communication to send component 1204 for transmission to apparatus 1206. In some aspects, the transmitting component 1204 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, or the like) on the generated communication and can transmit the processed signal to the device 1206. In some aspects, the transmitting component 1204 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the base station described in connection with fig. 2. In some aspects, the sending component 1204 may be co-located with the receiving component 1202 in a transceiver.

The transmitting component 1204 may transmit information identifying a set of PUCCH resources, wherein the set of PUCCH resources includes a first subset of PUCCH resources configured for frequency hopping per PUCCH resource and a second subset of PUCCH resources not configured with an associated configuration for frequency hopping per PUCCH resource. The receiving component 1202 may receive one or more PUCCH communications transmitted using one or more PUCCH resources in a set of PUCCH resources with frequency hopping. Configuration component 1208 can configure the PUCCH resource set to have a PUCCH resource subset configured for frequency hopping per PUCCH resource and an associated configured PUCCH resource subset not configured with frequency hopping per PUCCH resource.

The number and arrangement of components shown in fig. 12 are provided as examples. In practice, there may be more components, fewer components, different components, or differently arranged components than those shown in fig. 12. Further, two or more components shown in fig. 12 may be implemented within a single component, or a single component shown in fig. 12 may be implemented as multiple distributed components. Additionally or alternatively, one set (one or more) of components shown in fig. 12 may perform one or more functions described as being performed by another set of components shown in fig. 12.

The following provides an overview of some aspects of the disclosure:

aspect 1: a method of wireless communication performed by a UE, comprising: receiving a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include a repetition factor per PUCCH resource; identifying a repetition factor to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration; and transmitting one or more repetitions of the PUCCH communication based at least in part on the repetition factor.

Aspect 2: the method according to aspect 1, further comprising: identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration. Wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration.

Aspect 3: the method of aspect 1, further comprising: identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for the PUCCH communication. Wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for the PUCCH communication.

Aspect 4: the method of any one of aspects 1-3, further comprising: PUCCH resources to be used for transmitting the PUCCH communication are identified based at least in part on at least one of a PRI, a location of a CCE, or a dynamic indication.

Aspect 5: the method of aspect 1, wherein the PUCCH communication includes acknowledgement information associated with the scheduled PDSCH communication.

Aspect 6: the method of any of aspects 1-5, wherein the PUCCH communication comprises acknowledgement information associated with SPS communication.

Aspect 7: the method of any of aspects 1-6, wherein the PUCCH communication comprises an SR.

Aspect 8: the method of any of aspects 1-7, wherein the PUCCH communication comprises CSI.

Aspect 9: a method of wireless communication performed by a base station, comprising: transmitting a PUCCH resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset, wherein PUCCH resources in the first PUCCH resource subset are configured with a repetition factor per PUCCH resource, and wherein PUCCH resources in the second PUCCH resource subset do not include a repetition factor per PUCCH resource; identifying a repetition factor to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration; and receive one or more repetitions of the PUCCH communication based at least in part on the repetition factor.

Aspect 10: the method according to aspect 9, further comprising: identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration. Wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor associated with the PUCCH resource as configured in the PUCCH resource set configuration.

Aspect 11: the method of aspect 9, further comprising: identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication, wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for the PUCCH communication. Wherein identifying the repetition factor comprises: the repetition factor is identified based at least in part on a repetition factor configured for a PUCCH format to be used for the PUCCH communication.

Aspect 12: the method of any of claims 9-11, wherein the PUCCH communication includes acknowledgement information associated with a scheduled PDSCH communication.

Aspect 13: the method of any of aspects 9-12, wherein the PUCCH communication includes acknowledgement information associated with SPS communication.

Aspect 14: the method according to any of the claims 9-13, wherein the PUCCH communication comprises an SR.

Aspect 15: the method according to any of the claims 9-14, wherein the PUCCH communication comprises CSI.

Aspect 16: 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 the method according to one or more of aspects 1-8.

Aspect 17: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-8.

Aspect 18: an apparatus for wireless communication, comprising at least one unit for performing the method of one or more of aspects 1-8.

Aspect 19: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-8.

Aspect 20: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-8.

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 the method according to one or more of aspects 9-15.

Aspect 22: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 9-15.

Aspect 23: an apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 9-15.

Aspect 24: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 9-15.

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 that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 9-15.

Aspect 26: a method of wireless communication performed by a UE, comprising: receiving information identifying a set of PUCCH resources, wherein the set of PUCCH resources includes a first subset of PUCCH resources configured for frequency hopping per PUCCH resource and a second subset of PUCCH resources not configured with an associated configuration for frequency hopping per PUCCH resource; and transmitting one or more PUCCH communications using one or more PUCCH resources in the set of PUCCH resources using frequency hopping.

Aspect 27: the method of aspect 26, wherein the frequency hopping is inter-slot frequency hopping.

Aspect 28: the method of any of claims 26-27, wherein the first PUCCH resource subset is associated with a set of configuration parameters for frequency hopping, wherein the set of configuration parameters includes information identifying at least one of: a starting resource block, a frequency offset, or a frequency hopping pattern.

Aspect 29: the method of any of aspects 26-28, wherein the indication associated with transmitting the one or more PUCCH communications identifies an associated configured PUCCH resource in the second subset of PUCCH resources that is not configured with frequency hopping for each PUCCH resource, and wherein whether a PUCCH resource is associated with frequency hopping is based at least in part on a PUCCH format of the one or more PUCCH resources.

Aspect 30: the method of any of claims 26-29, wherein the first PUCCH resource subset is associated with a configuration for at least one of: a starting physical resource block, a physical resource block for frequency hopping, a frequency offset, a single frequency hopping, multiple frequency hopping, or a pattern for frequency hopping.

Aspect 31: the method of any of aspects 26-30, wherein the pattern of frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on an index of a slot in which one or more PUCCH communications are transmitted.

Aspect 32: the method of any of aspects 26-31, wherein a pattern for frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on whether demodulation reference signal bundling is in an active state.

Aspect 33: the method of any of claims 26-32, wherein the one or more PUCCH resources are associated with transmitting at least one of: hybrid automatic repeat request feedback messages for scheduled physical downlink shared channels, hybrid automatic repeat request feedback messages for semi-persistently scheduled communications, scheduling requests, or channel state information messages.

Aspect 34: a method of wireless communication performed by a base station, comprising: transmitting information identifying a Physical Uplink Control Channel (PUCCH) resource set, wherein the PUCCH resource set includes a first PUCCH resource subset configured for frequency hopping per PUCCH resource and a second PUCCH resource subset not configured with an associated configuration for frequency hopping per PUCCH resource; and receiving one or more PUCCH communications transmitted using one or more PUCCH resources in the set of frequency hopped utilized PUCCH resources.

Aspect 35: the method of aspect 34, wherein the frequency hopping is inter-slot frequency hopping.

Aspect 36: the method of any of claims 34-35, wherein the first PUCCH resource subset is associated with a set of configuration parameters for frequency hopping, wherein the set of configuration parameters includes information identifying at least one of: a starting resource block, a frequency offset, or a frequency hopping pattern.

Aspect 37: the method of any of aspects 34-36, wherein the indication associated with transmitting the one or more PUCCH communications identifies an associated configured PUCCH resource in the second subset of PUCCH resources that is not configured with frequency hopping for each PUCCH resource, and wherein whether a PUCCH resource is associated with frequency hopping is based at least in part on a PUCCH format of the one or more PUCCH resources.

Aspect 38: the method of any of aspects 34-37, wherein the first PUCCH resource subset is associated with a configuration for at least one of: a starting physical resource block, a physical resource block for frequency hopping, a frequency offset, a single frequency hopping, multiple frequency hopping, or a pattern for frequency hopping.

Aspect 39: the method of any of aspects 34-38, wherein the pattern of frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on an index of a slot in which one or more PUCCH communications are transmitted.

Aspect 40: the method of any of aspects 34-39, wherein the pattern for frequency hopping for PUCCH resource configuration in the first PUCCH resource subset is based at least in part on whether demodulation reference signal bundling is in an active state.

Aspect 41: the method of any one of aspects 34 to 40, wherein the one or more PUCCH resources are associated with transmitting at least one of: hybrid automatic repeat request feedback messages for scheduled physical downlink shared channels, hybrid automatic repeat request feedback messages for semi-persistently scheduled communications, scheduling requests, or channel state information messages.

Aspect 42: 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 the method according to one or more of aspects 26-33.

Aspect 43: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 26-33.

Aspect 44: an apparatus for wireless communication, comprising at least one unit to perform the method of one or more of aspects 26-33.

Aspect 45: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 26-33.

Aspect 46: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 26-33.

Aspect 47: 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 the method according to one or more of aspects 34-41.

Aspect 48: an apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 34-41.

Aspect 49: an apparatus for wireless communication, comprising at least one unit for performing the method of one or more of aspects 34-41.

Aspect 50: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 34-41.

Aspect 51: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 34-41.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terminology, should be broadly interpreted to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and/or functions, and the like. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It is apparent that the systems and/or methods described herein may be implemented in different forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of these aspects. Thus, the operation and behavior of the systems and/or methods were described without reference to the specific software code because one of ordinary skill in the art would understand that software and hardware could be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, a "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Even if specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, a phrase referring to "at least one" in a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combinations with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items recited in conjunction with the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items, and may be used interchangeably with "one or more". Where only one item is intended, the phrase "only one" or similar language is used. Further, as used herein, the terms "have", "contain", and the like are intended to be open-ended terms that do not limit the elements that they modify (e.g., "have" an element may also have B). Furthermore, unless explicitly stated otherwise, the phrase "based on" is intended to mean "based, at least in part, on". Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and, unless otherwise specified (e.g., if used in combination with "any" or "only one of" s), may be used interchangeably with "and/or.

Claims (30)

1. A User Equipment (UE) for wireless communication, comprising:

A memory; and

One or more processors coupled to the memory configured to:

a Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received,

Wherein the PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, an

Wherein the PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource;

Identifying parameters to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration; and

One or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

2. The UE of claim 1, wherein the one or more processors are further configured to:

Identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein, to identify the parameter, the one or more processors are configured to:

The parameters are identified based at least in part on parameters configured for a PUCCH format to be used for the PUCCH communication.

3. The UE of claim 1, wherein the one or more processors are further configured to:

identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein, to identify the parameter, the one or more processors are configured to:

the parameters associated with the PUCCH resources are identified based at least in part on the parameters as configured in the PUCCH resource set configuration.

4. The UE of claim 1, wherein the one or more processors are further configured to: PUCCH resources to be used for transmitting the PUCCH communication are identified based at least in part on at least one of a PUCCH Resource Indicator (PRI), a location of a Control Channel Element (CCE), or a dynamic indication.

5. The UE of claim 1, wherein the PUCCH communication comprises acknowledgement information associated with a scheduled Physical Downlink Shared Channel (PDSCH) communication.

6. The UE of claim 1, wherein the PUCCH communication comprises acknowledgement information associated with a semi-persistent scheduling (SPS) communication.

7. The UE of claim 1, wherein the PUCCH communication comprises a Scheduling Request (SR).

8. The UE of claim 1, wherein the PUCCH communication comprises Channel State Information (CSI).

9. The UE of claim 1, wherein the parameter is a repetition factor.

10. The UE of claim 1, wherein the parameter is a configuration for frequency hopping.

11. A base station for wireless communication, comprising:

A memory; and

One or more processors coupled to the memory configured to:

A Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is transmitted,

Wherein the PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, an

Wherein the PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource;

Identifying parameters to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration; and receive one or more repetitions of the PUCCH communication based at least in part on the parameter.

12. The base station of claim 11, wherein the one or more processors are further configured to:

Identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein, to identify the parameter, the one or more processors are configured to:

The parameters are identified based at least in part on parameters configured for a PUCCH format to be used for the PUCCH communication.

13. The base station of claim 11, wherein the one or more processors are further configured to:

identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein, to identify the parameter, the one or more processors are configured to:

the parameters associated with the PUCCH resources are identified based at least in part on the parameters as configured in the PUCCH resource set configuration.

14. The base station of claim 11, wherein the PUCCH communication comprises acknowledgement information associated with a scheduled Physical Downlink Shared Channel (PDSCH) communication.

15. The base station of claim 11, wherein the PUCCH communication comprises acknowledgement information associated with a semi-persistent scheduling (SPS) communication.

16. The base station of claim 11, wherein the PUCCH communication comprises a Scheduling Request (SR).

17. The base station of claim 11, wherein the PUCCH communication comprises Channel State Information (CSI).

18. The base station of claim 11, wherein the parameter is a repetition factor.

19. The base station of claim 11, wherein the parameter is a configuration for frequency hopping.

20. A method of wireless communication performed by a User Equipment (UE), comprising:

a Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is received,

Wherein the PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, an

Wherein the PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource;

Identifying parameters to be used for transmitting PUCCH communications based at least in part on the PUCCH resource set configuration; and

One or more repetitions of the PUCCH communication are transmitted based at least in part on the parameter.

21. The method of claim 20, further comprising:

Identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein identifying the parameter comprises:

The parameters are identified based at least in part on parameters configured for a PUCCH format to be used for the PUCCH communication.

22. The method of claim 20, further comprising:

identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein identifying the parameter comprises:

the parameters associated with the PUCCH resources are identified based at least in part on the parameters as configured in the PUCCH resource set configuration.

23. The method of claim 20, further comprising: PUCCH resources to be used for transmitting the PUCCH communication are identified based at least in part on at least one of a PUCCH Resource Indicator (PRI), a location of a Control Channel Element (CCE), or a dynamic indication.

24. The method of claim 20, wherein the PUCCH communication comprises acknowledgement information associated with a scheduled Physical Downlink Shared Channel (PDSCH) communication.

25. The method of claim 20, wherein the PUCCH communication comprises acknowledgement information associated with a semi-persistent scheduling (SPS) communication.

26. A wireless communication method performed by a base station, comprising:

A Physical Uplink Control Channel (PUCCH) resource set configuration comprising a first PUCCH resource subset and a second PUCCH resource subset is transmitted,

Wherein the PUCCH resources in the first PUCCH resource subset are configured with parameters per PUCCH resource, an

Wherein the PUCCH resources in the second PUCCH resource subset do not include parameters per PUCCH resource;

Identifying parameters to be used for receiving PUCCH communications based at least in part on the PUCCH resource set configuration; and

One or more repetitions of the PUCCH communication are received based at least in part on the parameter.

27. The method of claim 26, further comprising:

Identifying PUCCH resources in the second PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein identifying the parameter comprises:

The parameters are identified based at least in part on parameters configured for a PUCCH format to be used for the PUCCH communication.

28. The method of claim 26, further comprising:

identifying PUCCH resources in the first PUCCH resource subset to be used for transmitting the PUCCH communication,

Wherein identifying the parameter comprises:

the parameters associated with the PUCCH resources are identified based at least in part on the parameters as configured in the PUCCH resource set configuration.

29. The method of claim 26, wherein the PUCCH communication comprises acknowledgement information associated with a scheduled Physical Downlink Shared Channel (PDSCH) communication.

30. The method of claim 26, wherein the PUCCH communication comprises acknowledgement information associated with a semi-persistent scheduling (SPS) communication.