Enhanced PUCCH transmission for repetition or frequency hopping

Abstract

The device receives a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration indicates at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-slot hopping configuration independent of the PUCCH format for the PUCCH resource. In addition, the device sends PUCCH in the PUCCH resource based on at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot hopping configuration configured in the PUCCH resource configuration. The received PUCCH resource configuration may override the PUCCH format configuration. The device may receive a DCI indicating a PUCCH resource and / or a MAC‑CE associated with the PUCCH resource configuration, and may send a PUCCH based on the received DCI / MAC‑CE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 081,147, filed on September 21, 2020, entitled “Enhanced PUCCH Transmission for Repetition or Frequency Hopping,” and U.S. Patent Application No. 17 / 406,659, filed on August 19, 2021, entitled “Enhanced PUCCH Transmission for Repetition or Frequency Hopping,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003]

[0001] The present disclosure relates generally to communication systems and, more particularly, to enhanced Physical Uplink Control Channel (PUCCH) transmissions for repetition and / or frequency hopping. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., together with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvement of 5GNR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0007] The PUCCH resource repetition configuration and / or PUCCH resource inter-slot hopping configuration for the PUCCH resource may override the PUCCH format repetition configuration and / or PUCCH format inter-slot hopping configuration for the PUCCH format. The device may receive a DCI indicating a PUCCH resource, and / or the device may receive a MAC-CE configuring PUCCH repetition and / or PUCCH resource inter-slot hopping. Thus, via the DCI / MAC-CE, the device may be dynamically configured to be associated with PUCCH repetition and / or PUCCH inter-slot hopping.

[0008] In aspects of the present disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or modem at a UE or the UE itself. The apparatus receives a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration indicates at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-slot hopping configuration independent of a PUCCH format for the PUCCH resource. In addition, the apparatus sends a PUCCH in a PUCCH resource based on at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-slot hopping configuration configured in the PUCCH resource configuration.

[0009] To accomplish the foregoing and related purposes, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a schematic diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a schematic diagram showing an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a schematic diagram showing a PUCCH format, a PUCCH format configuration IE and a PUCCH resource IE.

[0017] Figure 5 is a schematic diagram showing PUCCH resources configured by PUCCH resource IE and DCI including PUCCH repetition indication.

[0018] Figure 6 is a call flow diagram illustrating configuration of PUCCH repetition and / or PUCCH inter-slot hopping for PUCCH resources independent of the PUCCH format.

[0019] Figure 7 is a flow chart of a method of wireless communication.

[0020] Figure 8 is a flow chart of a method of wireless communication.

[0021] Fig. 9 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0022] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be implemented without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0023] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0024] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0025] Therefore, in one or more exemplary embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, or a combination of various types of computer-readable media, or can be used to store any other medium with executable code in the form of instructions or data structures that can be accessed by a computer.

[0026] Although aspects and implementations are described in this application by illustrations of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many other arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and / or uses may be generated via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications or may not be specifically for use cases or applications, various applicability of the innovations may also occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems that merge one or more aspects of the described innovations. In some actual settings, the device incorporating the described aspects and features may also include additional components and features for the implementations and practices of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of different sizes, shapes, and configurations.

[0027] Figure 1 1 is a schematic diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0028] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 via a second backhaul link 184. The base station 102 may perform, among other functions, one or more of the following functions: transmission of user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0029] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. In each carrier allocated in carrier aggregation, the base station 102 / UE 104 can use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth, and up to a total of Yx MHZ (x component carriers) of carrier aggregation for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0030] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelinks, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0031] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in a 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0032] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0033] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often referred to (interchangeably) as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0034] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range names FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore, the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to exceed 52.6GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6GHz-71 GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0035] In view of the above, unless otherwise explicitly stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0036] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (e.g., gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0037] The base station 180 may transmit beamformed signals in one or more transmit directions 182' to the UE 104. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182'. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may be the same, or may not be the same. The transmit and receive directions for the UE 104 may be the same, or may not be the same.

[0038] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts specific services, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0039] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (HSS) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) streaming (PSS) service, and / or other IP services.

[0040] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client or some other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0041] Refer again Figure 1 In certain aspects, the UE 104 may be configured with a PUCCH resource repetition / PUCCH resource inter-slot hopping determination component (198) configured to receive and process a PUCCH resource repetition configuration and / or a PUCCH resource inter-slot hopping configuration for a PUCCH transmission based on the configuration.

[0042] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0043] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a schematic diagram 230 showing an example of DL channels within a 5G NR subframe. Figure 2C is a diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. Figure 2A , 2C In the example provided, it is assumed that the 5G NR frame structure is TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure, i.e., TDD.

[0044] Figures 2A-2D A frame structure is shown, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include microslots that may include 7, 4, or 2 symbols. Depending on whether the cyclic prefix (CP) is normal or extended, each time slot may include 14 or 12 symbols. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-constrained scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the CP and the digital scheme. The digital scheme defines a subcarrier spacing (SCS), and effectively defines a symbol length / duration, which is equal to 1 / SCS.

[0045]

[0046] For normal CP (14 symbols / slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, digital scheme 2 allows 4 slots per subframe. Thus, for normal CP and digital scheme μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for a normal CP with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) multiplexed (see Figure 2B ). Each BWP can have a specific digital scheme and CP (normal or extended).

[0047] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0048] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one specific configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0049] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (e.g., the system information block (SIB)), and paging messages.

[0050] like Figure 2C As shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may send DM-RS for a physical uplink control channel (PUCCH) and DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0051] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0052] Figure 3 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0053] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 including the physical (PHY) layer may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

[0054] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0055] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0056] Similar to the functions described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0057] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0058] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0059] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0060] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform Figure 1 198 related aspects.

[0061] Figure 4 4 is a schematic diagram 400 showing a PUCCH format 402 , a PUCCH format configuration IE 404 , and a PUCCH resource IE 406 . Figure 5 5 is a diagram 500 showing PUCCH resources 502 configured by the PUCCH resource IE 406 and the DCI including the PUCCH repetition indication in the diagram 504. NR defines multiple (e.g., five) PUCCH formats with short / long durations, different payload size ranges, and different multiplexing capabilities. PUCCH format 0 is a short PUCCH format with 1-2 UCI bits, where the waveform is a computer generated sequence (CGS). PUCCH format 1 is a long PUCCH format with 1-2 UCI bits using time division orthogonal cover code (TD-OCC), where the waveform is CGS. PUCCH format 2 is a short PUCCH format with more than 2 UCI bits, where the waveform is OFDM. PUCCH format 3 is a long PUCCH format with more than 2 UCI bits and no multiplexing capability, where the waveform is DFT-s-OFDM. PUCCH format 4 is a long PUCCH format with more than 2 UCI bits and multiplexing capability, where the waveform is DFT-s-OFDM.

[0062] PUCCH resources can be configured via RRC signaling through PUCCH resource IE 406. Up to 128 PUCCH resources can be configured. The PUCCH format used for each PUCCH resource is part of the RRC configuration. That is, PUCCH resource IE 406 includes a format field that defines the PUCCH format (e.g., one of five formats) for the PUCCH resource. The spatial relationship (beam) of each PUCCH resource can be activated by MAC-CE. For multiplexed HARQ-ACK in PUCCH resources, the DCI (DCI format for scheduling PDSCH and corresponding HARQ-ACK information) indicates a PUCCH resource indicator (PRI). The PUCCH resources can be indicated by the PRI within the DCI. Therefore, the PUCCH resources can be dynamically selected (i.e., dynamically configured for the UE) for HARQ-ACK transmission.

[0063] PUCCH repetitions in different time slots can support PUCCH formats 1, 3 and 4. The number of PUCCH repetitions is configured by RRC for a given PUCCH format via the field nrofSlots (2, 4 or 8 time slots) within the PUCCH format configuration IE 404. The format field nrofSlots may be referred to as PUCCH format repetition configuration 404a. Since the PUCCH format configuration IE 404 uses the same PUCCH format repetition configuration 404a to configure the format, all PUCCH resources with the format will have the same PUCCH format repetition configuration 404a (i.e., the same number of PUCCH repetitions). Similarly, the PUCCH inter-slot frequency hopping configuration is configured by RRC for a given PUCCH format via the field interslotFrequencyHopping within the PUCCH format configuration IE 404. The format field interslotFrequencyHopping may be referred to as PUCCH format inter-slot frequency hopping configuration 404b. Since the PUCCH format configuration IE 404 configures the format with the same PUCCH format inter-slot hopping configuration 404b, all PUCCH resources with the format will have the same PUCCH format inter-slot hopping configuration 404b (i.e., inter-slot hopping is enabled / disabled). The same PUCCH resource is used across all repetitions in different slots. In one example, one PUCCH-SpatialRelationInfo (beam) may be used. The same symbol may be used in each slot.

[0064] As discussed above, the format field interslotFrequencyHopping may be referred to as PUCCH format interslot frequency hopping configuration 404b. Referring to the schematic diagram of PUCCH resources 502, if interslotFrequencyHopping is enabled for a PUCCH format, the UE transmits a PUCCH for the PUCCH format starting from a first physical resource block (PRB) provided by a startingPRB in a slot having an even number, and starting from a second PRB provided by a secondHopPRB in a slot having an odd number. The slot indicated to the UE for the first PUCCH transmission may have a number of 0. The UE may not be expected to be configured to perform frequency hopping on PUCCH transmissions within a slot.

[0065] For PUCCH repetitions, the number of PUCCH repetitions is semi-statically configured through RRC signaling. As such, the number of PUCCH repetitions may not be so flexibly controlled. As discussed above, PUCCH repetitions are configured per PUCCH format. As such, all PUCCH transmissions with that PUCCH format may have the same number of PUCCH repetitions. For example, unless the RRC reconfigures the number of PUCCH repetitions for PUCCH format 1, it will not be possible to have no PUCCH repetitions (e.g., one PUCCH repetition) for a first PUCCH transmission with PUCCH format 1 and two PUCCH repetitions for a second PUCCH transmission with PUCCH format 1. There is currently no option available to dynamically indicate the number of PUCCH repetitions for a PUCCH resource (such as, for example, through MAC-CE or DCI).

[0066] In a first configuration, the number of PUCCH repetitions and / or inter-slot (or inter-repetition) frequency hopping may be RRC-configured per PUCCH resource configuration (e.g., rather than per PUCCH format, or overriding the configuration per PUCCH format). For example, the PUCCH resource IE 406 may provide a PUCCH resource configuration associated with a PUCCH resource. The PUCCH resource configuration for a PUCCH resource may indicate a PUCCH resource repetition configuration 406a, for example, via the field nrofSlots (indicated in bold), and / or indicate a PUCCH resource inter-slot frequency hopping configuration 406b, for example, via the field interslotFrequencyHopping (indicated in bold). Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b are specific to PUCCH resources and are independent of the PUCCH format. In one configuration, enhanced RRC signaling may be used to dynamically configure the PUCCH repetition factor per PUCCH resource. For example, a PUCCH resource indication mechanism based on the PRI field of the DCI and the starting CCE index is used to indicate the PUCCH resource and its associated repetition factor.

[0067] For HARQ-ACK transmission, the DCI may include a PRI field that indicates the PUCCH resources using the number of PUCCH repetitions. Therefore, the dynamic indication of the number of PUCCH repetitions may be achieved by the dynamic indication of the PUCCH resources. For periodic CSI / scheduling request (SR) (PUCCH resources are configured via RRC without DCI signaling) and HARQ-ACK, configuring PUCCH repetitions and PUCCH inter-slot hopping for PUCCH resources enables the use of the same PUCCH format with different numbers of PUCCH repetitions by using different PUCCH resources. Therefore, PUCCH repetitions and PUCCH inter-slot hopping may be configured more flexibly.

[0068] Optionally, MAC-CE may update, overwrite or enable the number of PUCCH repetitions per PUCCH resource. MAC-CE may update spatial relationship information (beam) for a given PUCCH resource. The same MAC-CE message may be used for this purpose, for example, by adding a field to MAC-CE. In a first configuration, MAC-CE may indicate the number of PUCCH repetitions. In a second configuration, MAC-CE may activate or deactivate more than one PUCCH repetition. For example, more than one PUCCH repetition may be configured as part of the PUCCH resource configuration, but MAC-CE may include a bit to indicate whether the number is used or no repetition (ie, one repetition) is assumed. If the number of PUCCH repetitions is not configured in RRC, but MAC-CE indicates that PUCCH repetitions are activated, a default number of PUCCH repetitions (e.g., two PUCCH repetitions) may be assumed. MAC-CE may also enable or disable PUCCH inter-slot hopping when PUCCH repetitions are enabled or the number of PUCCH repetitions is indicated as greater than one.

[0069] Regarding the conflict resolution of the legacy RRC configuration through the PUCCH format configuration IE 404 to the RRC configuration through the PUCCH resource IE 406, if the number of PUCCH repetitions / PUCCH inter-slot hopping (enabled or disabled) is configured for the PUCCH format, the UE can determine whether to use the PUCCH format repetition configuration 404a or the PUCCH resource repetition configuration 406a, and whether to use the PUCCH format inter-slot hopping configuration 404b or the PUCCH resource inter-slot hopping configuration 406b. If the PUCCH resource configured with the PUCCH format is configured via RRC or activated via MAC-CE with a different number of PUCCH repetitions or a different configuration of PUCCH inter-slot hopping, the UE can cover the PUCCH format repetition configuration 404a with the PUCCH resource repetition configuration 406a, and cover the PUCCH format inter-slot hopping configuration 404b with the PUCCH resource inter-slot hopping configuration 406b. That is, the PUCCH resource parameters can overwrite / cover the PUCCH format parameters. If the PUCCH resource configured with the PUCCH format is not configured or activated with the number of PUCCH repetitions or the configuration of PUCCH inter-slot hopping, then in the first configuration, when the PUCCH is sent using the PUCCH resource, the RRC configuration of the PUCCH format (for PUCCH repetition and / or PUCCH inter-slot hopping) may be assumed. In the second configuration, when the PUCCH is sent using the PUCCH resource, no PUCCH repetition and / or no PUCCH inter-slot hopping may be assumed.

[0070] Alternatively, referring to schematic diagram 504, a new field in the DCI (e.g., a DCI format for scheduling PDSCH and corresponding HARQ-ACK) may be added to indicate the number of PUCCH repetitions and / or PUCCH inter-slot hopping. In this option, the PRI field may indicate the PUCCH resources used for HARQ-ACK transmission, and the new field may indicate the number of PUCCH repetitions and / or the configuration for PUCCH inter-slot hopping. If more than one DCI indicates the same time slot for HARQ-ACK multiplexing, the number of PUCCH repetitions for transmission of HARQ-ACK and / or the configuration for PUCCH inter-slot hopping may be determined by the UE based on the last DCI (e.g., see 506). The presence of the new field in the DCI may be configured via RRC. For DCI format 1_1 versus DCI format 1_2, the RRC configuration may be separate. As mentioned above, the new field may not be added to the fallback DCI (DCI format 1_0) and may not be configured for both DCI formats 1_1 and 1_2. Thus, some DCIs may include the new field and some DCIs may not include the new field. In a first configuration, if the last DCI is a DCI format that does not include the new field, the UE may assume that the number of PUCCH repetitions is one. In a second configuration, the UE may determine the number of PUCCH repetitions based on the last DCI that includes the new field (which may not be the absolute last DCI) (e.g., see 508).

[0071] Figure 6 600 is a call flow diagram illustrating configuration of PUCCH repetition and / or PUCCH inter-slot hopping for PUCCH resources independent of PUCCH format. A base station 604 may be configured to provide at least one cell. A UE 602 may be configured to communicate with the base station 604. For example, in Figure 1 In the context of , base station 604 may correspond to base station 102 / 180, and accordingly, a cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cell 102' having a coverage area 110'. In addition, UE 602 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 604 may correspond to base station 310 and UE 602 may correspond to UE 350.

[0072] The UE 602 receives a PUCCH resource configuration 406 (in a PUCCH resource IE) associated with a PUCCH resource from a base station 604. The PUCCH resource configuration 406 indicates at least one of a PUCCH resource repetition configuration (e.g., 406a) or a PUCCH resource inter-slot frequency hopping configuration (e.g., 406b) for the PUCCH resource independent of the PUCCH format. Both the PUCCH resource repetition configuration 406a defined by the nrofSlots field within the PUCCH resource IE and the PUCCH resource inter-slot frequency hopping configuration 406b defined by the interslotFrequencyHopping field in the PUCCH resource IE are defined relative to the PUCCH resource IE and are therefore independent of the PUCCH format. Subsequently, the UE 602 sends a PUCCH 608 in the PUCCH resource based on at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot frequency hopping configuration 406b configured in the PUCCH resource configuration.

[0073] As discussed above, the PUCCH resource repetition configuration 406a and / or the PUCCH resource inter-slot hopping configuration 406b are received in the PUCCH resource IE via RRC signaling. As can be clearly seen from the PUCCH resource IE, the PUCCH resource IE also configures the PUCCH resource to be associated with one PUCCH format. The PUCCH format (e.g., the PUCCH format configuration IE 404) has a PUCCH format repetition configuration 404a and a PUCCH format inter-slot hopping configuration 404b, and the PUCCH resource repetition configuration 406a and / or the PUCCH resource inter-slot hopping configuration 406b overwrite the PUCCH format repetition configuration 404a and / or the PUCCH format inter-slot hopping configuration 404b for the PUCCH resource. When the PUCCH resource repetition configuration 406a is not configured for a specific number of PUCCH repetitions, the UE 602 can determine the number of PUCCH repetitions for PUCCH transmission based on the PUCCH format repetition configuration 404a. Alternatively, when the PUCCH resource repetition configuration 406a is not configured for a specific number of PUCCH repetitions, the UE 602 may determine that the number of PUCCH repetitions for PUCCH transmission is one.

[0074] As discussed above, although the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot hopping configuration 406b are semi-statically configured through RRC signaling, multiple different PUCCH resource IEs can define different PUCCH resources using different configurations of PUCCH repetition / PUCCH inter-slot hopping, and the UE 602 can be dynamically configured using PUCCH repetition / PUCCH inter-slot hopping through DCI 606 indicating reception of PUCCH resources and / or MAC-CE 606 configuring PUCCH repetition and / or PUCCH inter-slot hopping.

[0075] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104; apparatus 902; cellular baseband processor 904, which may include memory 360 and which may be the entire UE 350 or a component of the UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). One or more of the operations shown may be omitted, swapped, or performed simultaneously. The method may allow a UE to be dynamically configured to be associated with PUCCH repetition and / or PUCCH inter-slot hopping.

[0076] At 702, the UE receives a PUCCH resource configuration associated with a PUCCH resource. For example, 702 can be performed by a receiving component 930 of the device 902. The PUCCH resource configuration indicates at least one of a PUCCH resource repetition configuration 406a or a PUCCH resource inter-slot hopping configuration 406b for the PUCCH resource independent of the PUCCH format. In one configuration, at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot hopping configuration 406b is received in a PUCCH resource IE 406 via RRC signaling. The PUCCH resource configuration also configures the PUCCH resource to be associated with a PUCCH format in a PUCCH format. The PUCCH format has a PUCCH format repetition configuration 404a and a PUCCH format inter-slot hopping configuration 404b. At least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-time slot hopping configuration 406b covers at least one of the PUCCH format repetition configuration 404a or the PUCCH format inter-time slot hopping configuration 404b for the PUCCH resource. In one configuration, at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-time slot hopping configuration is received in downlink control information (DCI). The DCI is the last received DCI in a set of DCIs indicating the same time slot for transmission of hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information. In one configuration, the DCI includes a first field indicating the PUCCH resource and a second field indicating the number of PUCCH repetitions associated with the PUCCH resource repetition configuration or indicating the PUCCH resource inter-time slot hopping configuration, the first field being a PUCCH resource indicator (PRI) field. In one configuration, the DCI is the last received DCI in a set of DCIs including a second field and indicating the same time slot for transmission of HARQ-ACK information.

[0077] At 704, the UE transmits the PUCCH in the PUCCH resource. For example, 704 may be performed by the transmitting component 934 of the apparatus 902. The UE transmits the PUCCH in the PUCCH resource based on at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot hopping configuration 406b configured in the PUCCH resource configuration.

[0078] Figure 8800 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104; apparatus 902; cellular baseband processor 904, which may include memory 360 and which may be the entire UE 350 or a component of the UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). One or more of the operations shown may be omitted, swapped, or performed simultaneously. The method may allow a UE to be dynamically configured to be associated with PUCCH repetition and / or PUCCH inter-slot hopping.

[0079] At 802, the UE receives a PUCCH resource configuration associated with a PUCCH resource. For example, 802 can be performed by a receiving component 930 of the device 902. The PUCCH resource configuration indicates at least one of a PUCCH resource repetition configuration 406a or a PUCCH resource inter-slot hopping configuration 406b for the PUCCH resource independent of the PUCCH format. In one configuration, at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot hopping configuration 406b is received in a PUCCH resource IE 406 via RRC signaling. The PUCCH resource configuration also configures the PUCCH resource to be associated with a PUCCH format in a PUCCH format. The PUCCH format has a PUCCH format repetition configuration 404a and a PUCCH format inter-slot hopping configuration 404b. At least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-time slot hopping configuration 406b covers at least one of the PUCCH format repetition configuration 404a or the PUCCH format inter-time slot hopping configuration 404b for the PUCCH resource. In one configuration, at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-time slot hopping configuration is received in downlink control information (DCI). The DCI is the last received DCI in a set of DCIs indicating the same time slot for transmission of hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information. In one configuration, the DCI includes a first field indicating the PUCCH resource and a second field indicating the number of PUCCH repetitions associated with the PUCCH resource repetition configuration or indicating the PUCCH resource inter-time slot hopping configuration, the first field being a PUCCH resource indicator (PRI) field. In one configuration, the DCI is the last received DCI in a set of DCIs including a second field and indicating the same time slot for transmission of HARQ-ACK information.

[0080] At 804, the UE receives a DCI or MAC-CE associated with a PUCCH resource configuration. For example, 804 may be performed by a receiving component 930 of the device 902. In one configuration, for example, at 806, the UE may receive a DCI that schedules a PUCCH transmission. The DCI indicates a PUCCH resource associated with a PUCCH resource configuration, the PUCCH resource configuration indicating at least one of a PUCCH resource repetition configuration 406a or a PUCCH resource inter-slot hopping configuration 406b. In one configuration, at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot hopping configuration 406b is received in the DCI. The DCI may be received in the last received DCI in a set of DCIs indicating the same time slot for transmission of HARQ-ACK information. When the DCI indicates the number of PUCCH repetitions, when the last received DCI does not include an indication of the number of PUCCH repetitions, the UE may determine that the number of PUCCH repetitions for the PUCCH resource configuration is one. The DCI may include a first field (PRI field) indicating a PUCCH resource and a second field indicating the number of PUCCH repetitions associated with the PUCCH resource repetition configuration 406a or indicating the PUCCH resource inter-slot hopping configuration 406b. The UE may receive RRC signaling indicating the presence of the second field within the DCI. The DCI may be the last received DCI in a set of DCIs that include the second field and indicate the same time slot for transmission of HARQ-ACK information. In one configuration, for example, at 808, the UE may receive a MAC-CE covering the PUCCH resource repetition configuration 406a. The PUCCH resource repetition configuration specifies the first number of PUCCH repetitions. The MAC-CE may indicate the second number of PUCCH repetitions used for PUCCH transmission. In one configuration, for example, at 810, the UE receives a MAC-CE that activates or deactivates the PUCCH resource repetition configuration. In one configuration, when the number of PUCCH repetitions used for PUCCH transmission is greater than one, the MAC-CE may enable or disable inter-slot hopping associated with the PUCCH resource inter-slot hopping configuration 406b.

[0081] At 812, the UE determines the number of PUCCH repetitions. For example, 812 can be performed by the PUCCH resource repetition / PUCCH resource inter-slot hopping determination component 940 of the device 902. In one configuration, for example, at 814, the UE determines the number of PUCCH repetitions for PUCCH transmission based on the PUCCH format repetition configuration. When the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the UE determines the number of PUCCH repetitions for PUCCH transmission based on the PUCCH format repetition configuration. In one configuration, for example, at 816, the UE determines that the number of PUCCH repetitions for PUCCH transmission is one, a first number of PUCCH repetitions, or a default number of PUCCH repetitions. In one configuration, when the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the UE determines that the number of PUCCH repetitions for PUCCH transmission is one. The PUCCH resource repetition configuration may indicate a first number of PUCCH repetitions. In one configuration, when MAC-CE activates PUCCH resource repetition configuration, the UE determines that the number of PUCCH repetitions for PUCCH transmission is equal to the first number of PUCCH repetitions. In one configuration, when MAC-CE deactivates PUCCH resource repetition configuration, the UE determines that the number of PUCCH repetitions for PUCCH transmission is equal to one. In one configuration, when MAC-CE activates PUCCH resource repetition configuration and the PUCCH resource repetition configuration indicates no repetition, the UE determines that the number of PUCCH repetitions for PUCCH transmission is a default number of PUCCH repetitions. The DCI may indicate the number of PUCCH repetitions. In one configuration, when the last received DCI does not include an indication of the number of PUCCH repetitions, the UE determines that the number of PUCCH repetitions for PUCCH resource configuration is one. In one configuration, when the PUCCH resource repetition configuration 406a indicates a first number of PUCCH repetitions, the UE may determine that the number of PUCCH repetitions for PUCCH transmission is equal to the first number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration 406a, and may determine that the number of PUCCH repetitions for PUCCH transmission is equal to one when the MAC-CE deactivates the PUCCH resource repetition configuration 406a. In addition, in such a configuration, when the PUCCH resource repetition configuration 406a indicates no repetitions, the UE may determine that the number of PUCCH repetitions for PUCCH transmission is a default number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration 406a.

[0082] At 818, the UE receives RRC signaling indicating the presence of the second field within the DCI. For example, 818 can be performed by the receiving component 930 of the apparatus 902.

[0083] At 820, the UE transmits a PUCCH in the PUCCH resource. For example, 820 may be performed by the transmitting component 934 of the apparatus 902. The UE transmits the PUCCH in the PUCCH resource based on at least one of the PUCCH resource repetition configuration 406a or the PUCCH resource inter-slot hopping configuration 406b configured in the PUCCH resource configuration. In one configuration, the PUCCH may be transmitted based on a received MAC-CE indicating a second number of PUCCH repetitions.

[0084] Fig. 9 900 is a schematic diagram showing an example of a hardware implementation for an apparatus 902. The apparatus 902 may be a UE, a component of a UE, or may implement a UE function. In some aspects, the apparatus 902 may include a cellular baseband processor 904 (also referred to as a modem) coupled to a cellular RF transceiver 922. In some aspects, the apparatus 902 may also include one or more subscriber identity modules (SIM) cards 920, an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910, a Bluetooth module 912, a wireless local area network (WLAN) module 914, a global positioning system (GPS) module 916, or a power supply 918. The cellular baseband processor 904 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 922. The cellular baseband processor 904 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-temporary. The cellular baseband processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 904, the software causes the cellular baseband processor 904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 904 when executing the software. The cellular baseband processor 904 also includes a receiving component 930, a communication manager 932, and a transmitting component 934. The communication manager 932 includes one or more of the components shown. The components within the communication manager 932 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 904. The cellular baseband processor 904 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 902 may be a modem chip and include only the baseband processor 904, while in another configuration, the device 902 may be the entire UE (e.g., see Figure 3 350), and includes additional modules of device 902.

[0085] The communication manager 932 includes a PUCCH resource repetition / PUCCH resource inter-slot hopping determination component 940, which is configured to process the received PUCCH resource configuration and determine the PUCCH repetition and / or PUCCH inter-slot hopping configuration (e.g., as combined with Figure 8 The receiving component 830 is configured to receive a PUCCH resource configuration associated with a PUCCH resource (e.g., as described in conjunction with Figure 7 702 or Figure 8 The receiving component 830 may also be configured to receive a DCI or MAC-CE associated with a PUCCH resource configuration (e.g., as described in conjunction with Figure 8 804, 806, 808, or 810 of ). The receiving component 830 may also be configured to receive RRC signaling indicating the presence of a second field within the DCI (e.g., as described in conjunction with Figure 8 The transmitting component 934 is configured to transmit the PUCCH in the PUCCH resource (e.g., as described in conjunction with Figure 7 704 or Figure 8 820 as described).

[0086] The apparatus may include additional components that perform Figure 7 and 8 Each block in the algorithm block in the flowchart. Thus, Figure 7 and 8 Each block in the flowchart of can be performed by a component, and the device may include one or more of these components. The component can be one or more hardware components specifically configured to implement the process / algorithm, one or more hardware components implemented by a processor configured to execute the process / algorithm, one or more hardware components stored in a computer-readable medium for processor implementation, or some combination thereof.

[0087] As shown, the device 902 may include multiple components configured for various functions. In one configuration, the device 902 (and, in particular, the cellular baseband processor 904) includes a unit for receiving a PUCCH resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-slot hopping configuration independent of a PUCCH format for the PUCCH resource. The device includes a unit for sending a PUCCH in the PUCCH resource based on at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot hopping configuration configured in the PUCCH resource configuration. The device also includes a unit for determining the number of PUCCH repetitions for PUCCH transmission based on the PUCCH format repetition configuration when the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions. The device also includes a unit for determining that the number of PUCCH repetitions for PUCCH transmission is one when the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions. The device also includes a unit for receiving a DCI for scheduling PUCCH transmission. The DCI indicates a PUCCH resource associated with a PUCCH resource configuration, and the PUCCH resource configuration indicates at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-time slot hopping configuration. The device also includes a unit for receiving a MAC-CE covering the PUCCH resource repetition configuration. The MAC-CE indicates a second number of PUCCH repetitions for PUCCH transmission. The PUCCH is sent based on a received MAC-CE indicating a second number of PUCCH repetitions. The device also includes a unit for receiving a MAC-CE that activates or deactivates the PUCCH resource repetition configuration. The device also includes a unit for determining that the number of PUCCH repetitions for PUCCH transmission is equal to the first number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration. The device also includes a unit for determining that the number of PUCCH repetitions for PUCCH transmission is equal to one when the MAC-CE deactivates the PUCCH resource repetition configuration. The device also includes a unit for determining that the number of PUCCH repetitions for PUCCH transmission is equal to one when the MAC-CE deactivates the PUCCH resource repetition configuration. The device also includes a unit for determining that the number of PUCCH repetitions for PUCCH transmission is a default number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration and the PUCCH resource repetition configuration indicates no repetition. The apparatus further includes means for determining that the number of PUCCH repetitions for the PUCCH resource configuration is one when the last received DCI does not include an indication of the number of PUCCH repetitions. The apparatus further includes means for receiving radio resource control (RRC) signaling indicating the presence of a second field within the DCI. The means may be one or more of the components of the apparatus 902 configured to perform the functions recited by the means.As described above, the apparatus 902 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the means.

[0088] As discussed above, the UE may receive a PUCCH resource configuration 406 associated with a PUCCH resource, wherein the PUCCH resource configuration indicates a PUCCH resource repetition configuration 406a and / or a PUCCH resource inter-slot hopping configuration 406b for the PUCCH resource. Since the PUCCH resource configuration itself configures the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot hopping configuration 406b for the PUCCH resource, both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot hopping configuration 406b are independent of the PUCCH format. The PUCCH format may configure the PUCCH format repetition configuration 404a and / or the PUCCH format inter-slot hopping configuration 404b, both of which may be covered by the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot hopping configuration 406b. The UE may receive a DCI / MAC-CE associated with the PUCCH resource and / or the PUCCH resource configuration. In this way, PUCCH repetition and / or PUCCH inter-slot hopping can be inherently dynamically configured, providing flexibility in the configuration of the UE using PUCCH repetition and / or PUCCH inter-slot hopping. The UE can then send PUCCH in the PUCCH resource based on the PUCCH resource repetition configuration, PUCCH resource inter-slot hopping configuration, DCI and / or MAC-CE.

[0089] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. Based on design preferences, it is understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. In addition, some blocks can be combined or omitted. The attached method claims present the elements of each block in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0090] The above description is provided so that any technician in the field can implement the various aspects described herein. For those skilled in the art, various modifications to these aspects will be easily apparent, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language claims, wherein, unless specifically stated, the reference to the elements in the singular form is not intended to mean "one and only one", but "one or more". Terms such as "if", "when" and "while" should be interpreted as meaning "under ... conditions", rather than implying a direct time relationship or reaction. That is, these phrases (such as "when") do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if the condition is met, the action will occur, but does not require a specific or immediate time limit for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being superior to or superior to other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. may not be a substitute for the word "unit." Thus, no claim element is to be interpreted as a unit-plus-function unless the element is explicitly recited using the phrase "unit for..."

[0091] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0092] Aspect 1 is an apparatus for wireless communication at a UE, comprising: at least one processor coupled to a memory and configured to perform the following: receive a PUCCH resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating at least one of a PUCCH resource repetition configuration or a PUCCH resource inter-slot hopping configuration for the PUCCH resource independent of a PUCCH format; and send a PUCCH in the PUCCH resource based on the at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot hopping configuration configured in the PUCCH resource configuration.

[0093] Aspect 2 is the apparatus according to aspect 1, further comprising: a transceiver coupled to the at least one processor.

[0094] Aspect 3 is a device according to any one of Aspects 1 and 2, further comprising: at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot hopping configuration is received in the PUCCH resource IE via RRC signaling.

[0095] Aspect 4 is an apparatus according to any one of aspects 1-3, further comprising: the PUCCH resource configuration further configures the PUCCH resource to be associated with a PUCCH format in the PUCCH formats.

[0096] Aspect 5 is an apparatus according to any one of Aspects 1-4, further comprising: the PUCCH format has a PUCCH format repetition configuration and a PUCCH format inter-slot frequency hopping configuration, and at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot frequency hopping configuration covers at least one of the PUCCH format repetition configuration or the PUCCH format inter-slot frequency hopping configuration used for the PUCCH resource.

[0097] Aspect 6 is an apparatus according to any one of Aspects 1-5, further comprising: the at least one processor is also configured to determine the number of PUCCH repetitions for transmission of the PUCCH based on the PUCCH format repetition configuration when the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions.

[0098] Aspect 7 is an apparatus according to any one of Aspects 1-6, further comprising: the at least one processor is also configured to determine that the number of PUCCH repetitions used for the transmission of the PUCCH is one when the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions.

[0099] Aspect 8 is an apparatus according to any one of Aspects 1-7, further comprising: the at least one processor is also configured to receive downlink control information (DCI) for scheduling PUCCH transmission, the DCI indicating the PUCCH resource associated with the PUCCH resource configuration, and the PUCCH resource configuration indicating at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-slot frequency hopping configuration.

[0100] Aspect 9 is an apparatus according to any one of Aspects 1-8, further comprising: the PUCCH resource repetition configuration indicates a first number of PUCCH repetitions; and further comprising: the at least one processor is also configured to receive a MAC-CE covering the PUCCH resource repetition configuration, the MAC-CE indicating a second number of PUCCH repetitions used for PUCCH transmission, and the PUCCH is sent based on the received MAC-CE indicating the second number of PUCCH repetitions.

[0101] Aspect 10 is an apparatus according to any one of aspects 1-9, further comprising: the at least one processor is further configured to receive a MAC-CE activating or deactivating the PUCCH resource repetition configuration.

[0102] Aspect 11 is an apparatus according to any one of Aspects 1-10, further comprising: a PUCCH resource repetition configuration indicating a first number of PUCCH repetitions; and further comprising: the at least one processor is also configured to determine that the number of PUCCH repetitions used for PUCCH transmission is equal to the first number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration, and to determine that the number of PUCCH repetitions used for the PUCCH transmission is equal to one when the MAC-CE deactivates the PUCCH resource repetition configuration.

[0103] Aspect 12 is an apparatus according to any one of Aspects 1-11, further comprising: the at least one processor is also configured to determine that the number of PUCCH repetitions used for PUCCH transmission is a default number of PUCCH repetitions when the MAC-CE activates the PUCCH resource repetition configuration and the PUCCH resource repetition configuration indicates no repetition.

[0104] Aspect 13 is an apparatus according to any one of aspects 1-12, further comprising: when the number of PUCCH repetitions used for PUCCH transmission is greater than one, the MAC-CE enabling or disabling inter-slot hopping associated with the PUCCH resource inter-slot hopping configuration.

[0105] Aspect 14 is an apparatus according to any one of aspects 1-13, further comprising: at least one of the PUCCH resource repetition configuration or the PUCCH resource inter-time slot hopping configuration is received in a DCI.

[0106] Aspect 15 is an apparatus according to any one of aspects 1-14, further comprising: the DCI is the last received DCI in a set of DCIs indicating the same time slot for transmission of HARQ-ACK information.

[0107] Aspect 16 is an apparatus according to any one of Aspects 1-15, further comprising: the DCI indicates the number of PUCCH repetitions; and further comprising: the at least one processor is also configured to determine that the number of PUCCH repetitions used for the PUCCH resource configuration is one when the last received DCI does not include an indication of the number of PUCCH repetitions.

[0108] Aspect 17 is an apparatus according to any one of Aspects 1-16, further comprising: the DCI comprises a first field indicating the PUCCH resource and a second field indicating the number of PUCCH repetitions associated with the PUCCH resource repetition configuration or indicating the inter-time slot hopping configuration of the PUCCH resource, and the first field is a PRI field.

[0109] Aspect 18 is the apparatus according to any one of aspects 1-17, further comprising: the at least one processor is further configured to receive RRC signaling indicating the presence of the second field within the DCI.

[0110] Aspect 19 is an apparatus according to any one of aspects 1-18, further comprising: the DCI is the last received DCI in a set of DCIs including the second field and indicating the same time slot for transmission of HARQ-ACK information.

[0111] Aspect 20 is a method for wireless communication implementing any one of aspects 1-19.

[0112] Aspect 21 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1-19.

[0113] Aspect 22 is a computer-readable medium storing computer-executable codes, wherein when the codes are executed by a processor, the processor is caused to implement any one of aspects 1-19.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving a physical uplink control channel (PUCCH) resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating a PUCCH resource repetition configuration for the PUCCH resource, the PUCCH resource configuration being different from a PUCCH format repetition configuration; and The PUCCH is sent in the PUCCH resource based on the PUCCH resource repetition configuration configured in the PUCCH resource configuration.

2. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

3. The device according to claim 1, wherein: The at least one processor is configured to receive the PUCCH resource repetition configuration in a PUCCH resource information element (IE) via radio resource control (RRC) signaling.

4. The device according to claim 3, wherein: The PUCCH resource configuration further configures the PUCCH resource to be associated with a PUCCH format among a plurality of PUCCH formats.

5. The device according to claim 4, wherein: The PUCCH format is associated with the PUCCH format repetition configuration, and the PUCCH resource repetition configuration covers the PUCCH format repetition configuration for the PUCCH resource.

6. The device according to claim 5, wherein: The at least one processor is further configured to: When the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the number of PUCCH repetitions for transmission of the PUCCH is determined based on the PUCCH format repetition configuration.

7. The device according to claim 5, wherein: The at least one processor is further configured to: When the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the number of PUCCH repetitions determined for transmission of the PUCCH is one.

8. The device according to claim 3, wherein: The at least one processor is further configured to: Downlink control information (DCI) scheduling a PUCCH transmission is received, the DCI indicating the PUCCH resource associated with the PUCCH resource configuration, the PUCCH resource configuration indicating the PUCCH resource repetition configuration.

9. The device according to claim 3, wherein: The PUCCH resource repetition configuration indicates a first number of PUCCH repetitions, wherein the at least one processor is further configured to: A medium access control (MAC) control element (CE) (MAC-CE) is received covering the PUCCH resource repetition configuration, the MAC-CE indicating a second number of PUCCH repetitions for PUCCH transmission, and the PUCCH is sent based on the received MAC-CE indicating the second number of PUCCH repetitions.

10. The device according to claim 3, wherein: The at least one processor is further configured to: A medium access control (MAC) control element (CE) (MAC-CE) is received to activate or deactivate the PUCCH resource repetition configuration.

11. The device according to claim 10, wherein: The PUCCH resource repetition configuration indicates a first number of PUCCH repetitions, wherein the at least one processor is further configured to: When the MAC-CE activates the PUCCH resource repetition configuration, determining that the number of PUCCH repetitions used for PUCCH transmission is equal to the first number of PUCCH repetitions; and When the MAC-CE deactivates the PUCCH resource repetition configuration, the number of PUCCH repetitions used for the PUCCH transmission is determined to be equal to one.

12. The device according to claim 10, wherein: The at least one processor is further configured to: When the MAC-CE activates the PUCCH resource repetition configuration and the PUCCH resource repetition configuration indicates no repetition, determining the number of PUCCH repetitions used for PUCCH transmission is a default number of PUCCH repetitions.

13. The device according to claim 10, wherein: The MAC-CE enables or disables inter-slot hopping associated with the PUCCH resource inter-slot hopping configuration when the number of PUCCH repetitions used for PUCCH transmission is greater than one.

14. The device according to claim 1, wherein: The PUCCH resource repetition configuration is received in downlink control information (DCI).

15. The device according to claim 14, wherein: The DCI is the last received DCI among a set of DCIs of the same slot indicating transmission of hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) information.

16. The device according to claim 15, wherein: The DCI indicates a number of PUCCH repetitions, wherein the at least one processor is further configured to: When the last received DCI does not include an indication of the number of PUCCH repetitions, determining the number of PUCCH repetitions for the PUCCH resource configuration is one.

17. The device according to claim 14, wherein: The DCI includes a first field indicating the PUCCH resource and a second field indicating the number of PUCCH repetitions associated with the PUCCH resource repetition configuration, the first field being a PUCCH Resource Indicator (PRI) field.

18. The device according to claim 17, wherein: The at least one processor is further configured to: Radio resource control (RRC) signaling is received indicating the presence of the second field within the DCI.

19. The device according to claim 17, wherein: The DCI is a last received DCI among a set of DCIs of the same time slot that include the second field and indicate transmission of hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) information.

20. A method for wireless communication of a user equipment (UE), comprising: receiving a physical uplink control channel (PUCCH) resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating a PUCCH resource repetition configuration for the PUCCH resource, the PUCCH resource configuration being different from a PUCCH format repetition configuration; and The PUCCH is sent in the PUCCH resource based on the PUCCH resource repetition configuration configured in the PUCCH resource configuration.

21. The method according to claim 20, wherein: The PUCCH resource repetition configuration is received in a PUCCH resource information element (IE) via radio resource control (RRC) signaling.

22. The method according to claim 21, wherein: The PUCCH resource configuration further configures the PUCCH resource to be associated with a PUCCH format among a plurality of PUCCH formats.

23. The method according to claim 22, wherein: The PUCCH format is associated with the PUCCH format repetition configuration, and the PUCCH resource repetition configuration covers the PUCCH format repetition configuration for the PUCCH resource.

24. The method according to claim 23, further comprising: When the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the number of PUCCH repetitions for transmission of the PUCCH is determined based on the PUCCH format repetition configuration.

25. The method of claim 23, further comprising: When the PUCCH resource repetition configuration is not configured for a specific number of PUCCH repetitions, the number of PUCCH repetitions determined for transmission of the PUCCH is one.

26. The method of claim 21, further comprising: Downlink control information (DCI) scheduling a PUCCH transmission is received, the DCI indicating the PUCCH resource associated with the PUCCH resource configuration, the PUCCH resource configuration indicating the PUCCH resource repetition configuration.

27. The method of claim 21, wherein: The PUCCH resource repetition configuration indicates a first number of PUCCH repetitions, and the method further includes: A medium access control (MAC) control element (CE) (MAC-CE) is received covering the PUCCH resource repetition configuration, the MAC-CE indicating a second number of PUCCH repetitions for PUCCH transmission, and the PUCCH is sent based on the received MAC-CE indicating the second number of PUCCH repetitions.

28. The method of claim 21, further comprising: A medium access control (MAC) control element (CE) (MAC-CE) is received to activate or deactivate the PUCCH resource repetition configuration.

29. An apparatus for wireless communication of a user equipment (UE), comprising: means for receiving a physical uplink control channel (PUCCH) resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating a PUCCH resource repetition configuration for the PUCCH resource, the PUCCH resource configuration being different from a PUCCH format repetition configuration; and means for sending a PUCCH in the PUCCH resource based on the PUCCH resource repetition configuration configured in the PUCCH resource configuration.

30. A computer readable medium storing computer executable code at a user equipment (UE), the code, when executed by a processor, causes the processor to: receiving a physical uplink control channel (PUCCH) resource configuration associated with a PUCCH resource, the PUCCH resource configuration indicating a PUCCH resource repetition configuration for the PUCCH resource, the PUCCH resource configuration being different from a PUCCH format repetition configuration; and The PUCCH is sent in the PUCCH resource based on the PUCCH resource repetition configuration configured in the PUCCH resource configuration.

Images