Dynamic PUCCH repeat indicator

Abstract

The aspects presented herein relate to methods and apparatus for wireless communication including devices (e.g., UEs and / or base stations). The apparatus may receive from a base station a Radio Resource Control (RRC) message including an indication of the number of repetitions of a Physical Uplink Control Channel (PUCCH). The apparatus may also receive from the base station Downlink Control Information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH Resource Indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions. The apparatus may also transmit PUCCHs to the base station via the PUCCH resources in the one or more PUCCH resource sets, the transmitted PUCCHs corresponding to the number of PUCCH repetitions.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of International Application No. PCT / CN2020 / 117624, filed on September 25, 2020, entitled “METHODS AND APPARATUS FOR DYNAMICPUCCH REPETITION”, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to communication systems, and more particularly to the Physical Uplink Control Channel (PUCCH) reporting in wireless communication systems.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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.

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband, promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced (pc) mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them.

[0007] Brief Overview

[0008] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify the key or decisive elements of all aspects, nor to define 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 an introduction to the more detailed description that follows.

[0009] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may receive from a base station a radio resource control (RRC) message including an indication of the number of repetitions of a Physical Uplink Control Channel (PUCCH). The apparatus may also receive from the base station downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions. Furthermore, the apparatus may select one PUCCH resource set from the one or more PUCCH resource sets based on the uplink control information (UCI) size. The apparatus may also transmit a PUCCH to the base station via the PUCCH resources in the one or more PUCCH resource sets, the transmitted PUCCH corresponding to the number of PUCCH repetitions.

[0010] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a base station. The apparatus may transmit to a user equipment (UE) a radio resource control (RRC) message including an indication of the number of repetitions of a physical uplink control channel (PUCCH). The apparatus may also transmit to the UE downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions. The apparatus may also receive PUCCHs from the UE via the PUCCH resources in the one or more PUCCH resource sets, the received PUCCHs corresponding to the number of PUCCH repetitions.

[0011] To achieve the foregoing and related objectives, these one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of these one or more aspects are set forth in detail in the following description and drawings. However, these features merely indicate a few of the various ways in which the principles of these various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Brief description of the attached diagram

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

[0014] Figure 2A This is an example illustration of the first frame explaining various aspects of this disclosure.

[0015] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0016] Figure 2C This is an example illustration of the second frame explaining various aspects of this disclosure.

[0017] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0018] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0019] Figure 4 It is a diagram explaining the PUCCH format, configuring IE with the PUCCH format, and providing IE with PUCCH resources.

[0020] Figure 5 This is a diagram illustrating the example of PUCCH resource allocation.

[0021] Figure 6A This is a diagram illustrating the repetition of the PUCCH example.

[0022] Figure 6B This is a diagram illustrating the repetition of the PUCCH example.

[0023] Figure 6C This is a diagram illustrating the repetition of the PUCCH example.

[0024] Figure 7 This is a diagram illustrating an example of communication between the UE and the base station.

[0025] Figure 8 This is a flowchart of a wireless communication method.

[0026] Figure 9 This is a flowchart of a wireless communication method.

[0027] Figure 10 This is a flowchart of a wireless communication method.

[0028] Figure 11 This is a diagram illustrating an example of the hardware implementation of the example device.

[0029] Figure 12 This is a diagram illustrating an example of the hardware implementation of the example device.

[0030] Detailed description

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

[0032] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and explained in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element, or any part of an element, or any combination of elements, may 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0034] Accordingly, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of being used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0035] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0036] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptography decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment 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), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0037] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. Overlapping geographical coverage areas 110 may exist. For example, small cell 102' may have coverage areas 110' that overlap with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB) that can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may use one or more carriers. For each carrier allocated in a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). These 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 to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0038] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

[0040] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.

[0041] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0042] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

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

[0044] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.

[0045] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0046] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0047] Base stations may include and / or be referred to as gNB, B-node, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0048] Refer again Figure 1 In some aspects, UE 104 may include a receiving component 198 configured to receive from a base station a radio resource control (RRC) message including an indication of the number of physical uplink control channel (PUCCH) repetitions. The receiving component 198 may also be configured to receive from the base station downlink control information (DCI) indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number. The receiving component 198 may also be configured to select a PUCCH resource set from the one or more PUCCH resource sets based on the uplink control information (UCI) size. The receiving component 198 may also be configured to transmit a PUCCH to the base station via the PUCCH resources in the one or more PUCCH resource sets, the transmitted PUCCH corresponding to the PUCCH repetition number.

[0049] Refer again Figure 1In some aspects, base station 180 may include transmission component 199 configured to transmit to user equipment (UE) a radio resource control (RRC) message including an indication of the number of physical uplink control channel (PUCCH) repetitions. Transmission component 199 may also be configured to transmit to the UE downlink control information (DCI) indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number. Transmission component 199 may also be configured to receive PUCCHs from the UE via the PUCCH resources in the one or more PUCCH resource sets, the received PUCCHs corresponding to the PUCCH repetition number.

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

[0051] Figure 2A This is a diagram 200 illustrating an example of the first subframe within the 5G NR frame structure. Figure 2B Figure 230 is an example illustrating the DL channel within a 5G NR subframe. Figure 2C This is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of the UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL; or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2CIn the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 1 (all UL), where D is DL, U is UL, and F is for flexible use between DL and 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 all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures for TDD.

[0052] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 symbols per subframe. μ Each time slot. The subcarrier spacing and symbol length / duration vary depending on the design parameters. The subcarrier spacing can be equal to 2. μ *15kHz, where μ is the parameter design from 0 to 4. Thus, parameter design μ = 0 has a subcarrier spacing of 15kHz, while parameter design μ = 4 has a subcarrier spacing of 240kHz. Symbol length / duration is inversely correlated with subcarrier spacing. Figures 2A to 2DAn example is provided with a slot configuration of 0 (14 symbols per slot) and a parameter design of μ=2 (4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have specific parameter designs.

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

[0054] like Figure 2A As explained in the text, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0055] Figure 2BExamples of various DL channels within a subframe of a frame are explained. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs). Each CCE includes 6 RE Groups (REGs), and each REG includes 12 coherent REs in the OFDM symbols of the RB. A 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 shared search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where 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 located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and 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 aforementioned 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 known 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 not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0056] As in Figure 2C As explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and on the specific PUCCH format used. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0057] Figure 2DExamples of various UL channels within a subframe of the explanatory frame. The PUCCH can be located 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) ACK / NACK feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0058] Figure 3 This is a block diagram showing the communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting 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 of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0059] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. 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 decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier with the corresponding spatial stream for transmission.

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

[0061] The controller / processor 359 may be associated with a memory 360 that stores program code 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, cipher decoding, 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 ACK and / or NACK protocols to support HARQ operation.

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

[0063] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0064] UL transmissions are processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0065] The controller / processor 375 may be associated with a memory 376 that stores program code 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, cipher decoding, header decompression, and control signal processing to recover IP packets from the UE 350. 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 operation.

[0066] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The 198 combines various aspects.

[0067] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The 199 combines various aspects.

[0068] Figure 4 This is a diagram 400 illustrating PUCCH format 402, PUCCH format configuration information element (IE) 404, and PUCCH resource IE 406. Some aspects of wireless communication (e.g., New Radio (NR)) can define 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.

[0069] PUCCH resources can be configured via RRC signaling through PUCCH resource IE 406. In some aspects, up to 128 PUCCH resources can be configured. The PUCCH format of each PUCCH resource can be part of the RRC configuration. That is, PUCCH resource IE 406 may include a format field defining the PUCCH format of that PUCCH resource (e.g., one of five formats). In addition, spatial relationships (e.g., beamforming) can be activated for each PUCCH resource via MAC-CE. To multiplex HARQ-ACK in a PUCCH resource, a DCI (e.g., the DCI format for scheduling PDSCH and the corresponding HARQ-ACK information) can indicate a PUCCH resource indicator (PRI). The PUCCH resource can be indicated by the PRI within the DCI. Accordingly, PUCCH resources can be dynamically selected (i.e., dynamically configured for the UE) for HARQ-ACK transmission.

[0070] For certain PUCCH formats, such as PUCCH formats 1, 3, and 4, PUCCH repetition in different time slots is supported. The number of PUCCH repetitions can be configured for a given PUCCH format RRC via the "Number of Slots" (nrofSlots) field (e.g., 2, 4, or 8 slots) within the PUCCH format configuration IE 404. The format field nrofSlots can be referred to as PUCCH format repetition configuration 404a. Since PUCCH format configuration IE 404 configures formats with the same PUCCH format repetition configuration 404a, all PUCCH resources with that format can have the same PUCCH format repetition configuration 404a (i.e., the same number of PUCCH repetitions). Similarly, inter-slot frequency hopping configuration for PUCCH can be configured for a given PUCCH format RRC via the "interslotFrequencyHopping" field within the PUCCH format configuration IE 404. The format field interslotFrequencyHopping can be referred to as PUCCH format inter-slot frequency hopping configuration 404b. Because the PUCCH format configuration IE 404 configuration has the same format as the inter-slot frequency hopping configuration 404b, all PUCCH resources with this format can have the same inter-slot frequency hopping configuration 404b (i.e., inter-slot frequency hopping is disabled / enabled). The same PUCCH resource can be reused across different time slots. In one example, a PUCCH-SpatialRelationInfo (e.g., beam) can be used. Furthermore, the same symbols can be used in each time slot.

[0071] As previously mentioned, the format field `interslotFrequencyHopping` can be referred to as PUCCH format inter-slot frequency hopping configuration 404b. If `interslotFrequencyHopping` is enabled for a PUCCH format, the UE can transmit a PUCCH of that format starting from a first Physical Resource Block (PRB) (provided by the starting PRB in even-numbered time slots) and starting from a second PRB (provided by the second Hop PRB in odd-numbered time slots). The time slot indicated to the UE for the first PUCCH transmission may have the number 0. Furthermore, the UE may not wish to be configured to perform frequency hopping for PUCCH transmissions within a time slot.

[0072] For PUCCH repetition, the number of PUCCH repetitions can be configured semi-statically via RRC signaling. This may limit the flexibility in controlling the number of PUCCH repetitions. As previously mentioned, PUCCH repetition can be configured per PUCCH format. Thus, all PUCCH transmissions with that PUCCH format can have the same number of PUCCH repetitions. For example, it might be impossible for a first PUCCH transmission with PUCCH format 1 to have no PUCCH repetitions (e.g., one PUCCH repetition) while a second PUCCH transmission with PUCCH format 1 might have two PUCCH repetitions unless the RRC reconfigures the number of PUCCH repetitions for PUCCH format 1. There may not be options available for dynamically indicating the number of PUCCH repetitions for PUCCH resources, such as via MAC-CE or DCI.

[0073] In the first configuration, the number of PUCCH repetitions and / or the inter-slot (or inter-repetition) frequency hopping can be configured by an RRC per PUCCH resource configuration (e.g., rather than per PUCCH format, or overriding the configuration for each PUCCH format). For example, PUCCH resource IE 406 can provide the PUCCH resource configuration associated with the PUCCH resource. The PUCCH resource configuration of the PUCCH resource can be configured via, for example, the nrofSlots field (in... Figure 4 (in bold) to indicate PUCCH resource reconfiguration 406a, and / or via, for example, the interslotFrequencyHopping field (in) Figure 4 The PUCCH resource inter-slot frequency hopping configuration 406b is indicated by bold text. Both the PUCCH resource repetition configuration 406a and the PUCCH resource inter-slot frequency hopping configuration 406b can be dedicated to PUCCH resources and can be independent of the PUCCH format.

[0074] For HARQ-ACK transmissions, DCI may include a PRI field indicating the PUCCH resource with a PUCCH repetition number. Accordingly, dynamic indication of the PUCCH repetition number can be achieved through dynamic indication of the PUCCH resource. For periodic CSI / Schedule Request (SR) (e.g., PUCCH resources are configured by RRC without DCI signaling) and HARQ-ACK, configuring PUCCH repetition and inter-slot frequency hopping for PUCCH resources can enable the use of the same PUCCH format with different PUCCH repetition numbers by using different PUCCH resources. Accordingly, PUCCH repetition and inter-slot frequency hopping can be configured more flexibly.

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

[0076] Regarding the conflict resolution between the legacy RRC configuration via PUCCH format configuration IE 404 and the aforementioned RRC configuration via PUCCH resource IE 406, if PUCCH repetition count / PUCCH inter-slot hopping is configured for the PUCCH format (i.e., enabled or disabled), the UE can determine whether to use PUCCH format repetition configuration 404a or PUCCH resource repetition configuration 406a, and whether to use PUCCH format inter-slot hopping configuration 404b or PUCCH resource inter-slot hopping configuration 406b. If the PUCCH resource configured with this PUCCH format is configured (e.g., via RRC signaling) or activated (e.g., via MAC-CE) with a different PUCCH repetition count or a different PUCCH inter-slot hopping configuration, the UE can override PUCCH format repetition configuration 404a with PUCCH resource repetition configuration 406a and override PUCCH format inter-slot hopping configuration 404b with PUCCH resource inter-slot hopping configuration 406b. That is, PUCCH resource parameters can overwrite / overwrite PUCCH format parameters. If a PUCCH resource configured with this PUCCH format is not configured or activated using the PUCCH repetition count or PUCCH inter-slot hopping configuration, then in the first configuration, when transmitting PUCCH using this PUCCH resource, the RRC configuration of the PUCCH format (for PUCCH repetition and / or PUCCH inter-slot hopping) can be assumed. In the second configuration, when transmitting PUCCH using this PUCCH resource, it can be assumed that there is no PUCCH repetition and / or no PUCCH inter-slot hopping.

[0077] In some aspects of wireless communication, the number of PUCCH repetitions based on time slots can be configured by higher layers for each PUCCH format. Considering the mixed traffic types of the UE and the fact that different traffic types may have different reliability and latency, different repetition numbers (e.g., based on time slots or sub-time slots) can be utilized for PUCCHs associated with different traffic types and / or UCI types (e.g., HARQ ACK, Scheduling Request (SR), CSI). Furthermore, since channel conditions can change dynamically, a PUCCH repetition number indicated by a semi-static indicator may lead to unnecessary resource waste or lower transmission reliability. Therefore, the PUCCH repetition number can be dynamically indicated by the DCI.

[0078] The PUCCH repetition number can be configured on a per-PUCCH format or per-PUCCH resource basis. When scheduling PUCCHs, the PUCCH repetition number configured for the PUCCH can be applied. However, PUCCH resources can be scheduled for various types of transmissions. For example, a PUCCH resource can be scheduled for periodic or semi-persistent transmissions for CSI reporting, which may be referred to as periodic (P) or semi-persistent (SP) PUCCH transmissions, and a PUCCH can also be scheduled for non-periodic transmissions for non-periodic CSI reporting, which may be referred to as non-periodic (AP) PUCCH transmissions. Therefore, if the repetition number is configured on a per-PUCCH format or per-PUCCH resource basis, all periodic, semi-persistent, or non-periodic transmissions associated with the same PUCCH resource may be affected and use the same repetition number. For example, when the same PUCCH resource is used for different types of transmissions (e.g., one type for periodic CSI reporting and another type for ACK / NACK transmissions), both periodic CSI and ACK / NACK transmissions can use the same PUCCH repetition number associated with the PUCCH resource or PUCCH format. Based on the above, dynamically indicating the PUCCH repetition count may be beneficial. For example, including RRC messages and / or DCI messages with dynamic PUCCH repetition counts may be advantageous.

[0079] Various aspects of this disclosure may include a PUCCH via a DCI having a dynamic PUCCH repetition number. For example, when enabling the UE to be indicated to have a dynamic PUCCH repetition number, the repetition number may be indicated by an enhanced existing DCI field. Various aspects of this disclosure may include a PUCCH resource indicator (PRI), wherein each PRI code point is associated with a repetition number. Additionally, various aspects of this disclosure may include a PDSCH to HARQ feedback timing indicator (which indicates the slot offset K1 from the PDSCH to the HARQ feedback transmission received), wherein each K1 code point is associated with a repetition number.

[0080]

[0081] Table 1

[0082] Table 1 above shows the PRI or K1 code points in the DCI field, and the number of repetitions. As shown in Table 1, ResourceList-v17xy or Dl-DataToUL-ACK-v17 can have a list of values ​​for the number of PUCCH repetitions. For example, ResourceList-v17xy can be configured as above with a list of repetition numbers PUCCH-ResourceandNumR-v17xy, which provides the number of PUCCH repetitions: 2 repetitions (n2), 4 repetitions (n4), 8 repetitions (n8), or 16 repetitions (n16). For example, ResourceList-v17xy::= PUCCH-ResourceandNumR-v17xy SEQUENCE(SIZE(1…maxNrofPUCCH-ResourcesPerSet)). In some instances, PUCCH-ResourceandNumR-v17xy::=SEQUENCE{repetitionNumber-r17ENUME RATED{n2,n4,n8,n16}}.

[0083] In another example, Dl-DataToUL-ACK-v17 can be configured as above with a list of repetition numbers Dl-DataToUL-ACKandNumR, which provides the number of PUCCH repetitions: 2 repetitions (n2), 4 repetitions (n4), 8 repetitions (n8), or 16 repetitions (n16). Furthermore, Dl-DataToUL-ACK-v17::=SEQUENCE(SIZE(1…I))OF Dl-DataToUL-ACKandNumR, and Dl-DataToUL-ACKandNumR::=SEQUENCE{repetitionNumber-r17 ENUMERATED{n2,n4,n6,n8,n16}}.

[0084] Figure 5 This is diagram 500 illustrating the example of PUCCH resource allocation. Figure 5 This includes the second and third PUCCH resource sets. Furthermore, Figure 5 This shows the PUCCH resources in each PUCCH resource set associated with PRI 0, PRI 1, PRI 2, and PRI 3, as well as the number of repeats (rep#) (e.g., two or four repeats). Figure 5 As shown, the PUCCH resource set can be determined first based on the UCI size, and then the PUCCH resources and the number of repetitions can be determined based on the enhanced PRI indication in the DCI.

[0085] Tables 2 and 3 below depict the different codepoints in the DCI field. More specifically, Table 2 shows the K1 codepoints in the DCI field, along with the number of repetitions. Furthermore, Table 3 shows the PRI codepoints in the DCI field, along with the number of repetitions. By using enhanced PRI or K1 codepoints to indicate the PUCCH repetition number, two different DCI codepoints can have the same PRI or K1 value for the indicated PUCCH resource, but the PUCCH repetition numbers can differ. For example, in Table 2, both the first and second K1 codepoints indicate a K1 value of 2, while the PUCCH repetition numbers (Rep) are 2 and 4, respectively.

[0086]

[0087]

[0088] Table 2

[0089]

[0090] Table 3

[0091] In some respects, when the dynamic number of PUCCH repetitions is indicated by the DCI, the dynamic number of PUCCH repetitions can override the PUCCH repetition number of the semi-static configuration used for PUCCH transmissions scheduled by the DCI. For example, in Figure 5 If the PUCCH resource is used for periodic (P)CSI reporting and also for ACK / NACK feedback, then when transmitting PUCCH for P-CSI reporting, a first number of PUCCH repetitions (which are semi-statically configured to the PUCCH format or PUCCH resource) can be used, and when transmitting PUCCH for ACK / NACK feedback, a second number of PUCCH repetitions indicated by DCI can be used, instead of the first number of PUCCH repetitions.

[0092] The number of PUCCH repetitions indicated from the DCI can be associated with multiple options. For example, the indicated number of PUCCH repetitions can be the total number of repetitions. In this case, the number can be counted for two PUCCH repetitions with different beam information. For example, if the indicated number of PUCCH repetitions is 4, and two types of beam information (ULTCI1 and ULTCI2, or spatial relationship information 1 and spatial relationship information 2) are indicated for the PUCCH, then the number of PUCCH repetitions can be 2 for each type of beam information.

[0093] Furthermore, the indicated number of PUCCH repetitions can be either the actual number of repetitions or the number indicated by the beam. In this case, the same number can be applied to PUCCH repetitions for different beam information. For example, if the indicated number of PUCCH repetitions is 2, and two types of beam information (UL TCI1 and UL TCI2, or spatial relationship information 1 and spatial relationship information 2) are indicated for the PUCCH, then the number of PUCCH repetitions can be 2 for each type of beam information.

[0094] Furthermore, the indicated number of PUCCH repetitions can be a proportion of the number of PUCCH repetitions configured per PUCCH format or per PUCCH resource. For example, if the number of PUCCH repetitions configured for a PUCCH format is 4, the indicated number can be 0.5 or 2. Additionally, if the indicated dynamic number of PUCCH repetitions is 0.5, there can be 2 PUCCH repetitions, while if the indicated dynamic number of PUCCH repetitions is 2, there can be 8 PUCCH repetitions.

[0095] Figure 6A , Figure 6B and Figure 6C These are the explanatory examples PUCCH repeated in Figures 600, 610, and 620. Figure 6A The indicated number of PUCCH repetitions can be the total number of repetitions, for example, 4. Figure 6A As shown, the indicated number of PUCCH repetitions can include PUCCH repetitions for different types of beam information. For example, when the indicated number of PUCCH repetitions is 4, and two types of beam information (spatial relationship information 1 and spatial relationship information 2) are indicated for the PUCCH, the number of PUCCH repetitions can be 2 for each type of beam information.

[0096] Figure 6B The indicated number of PUCCH repetitions can be either the actual number of repetitions or the number indicated by the beam, for example, 2. Figure 6B As shown, the same number of PUCCH repetitions can be applied to PUCCH repetitions with different beam information. For example, when the indicated number of PUCCH repetitions is 2, and the PUCCH indicates two types of beam information (spatial relationship information 1 and spatial relationship information 2), the number of PUCCH repetitions can be 2 for each type of beam information.

[0097] Figure 6C The indicated number of PUCCH repetitions can be displayed as a percentage of the total number of PUCCH repetitions, such as 0.5 or 2 times. Figure 6CAs shown, the indicated number of PUCCH repetitions can be a proportion of the number of PUCCH repetitions configured per PUCCH format or per PUCCH resource. For example, if the PUCCH repetitions configured for a PUCCH format are 4, then the indicated number could be 0.5 or 2. Figure 6C As shown, there are two PUCCH repetitions because the indicated dynamic PUCCH repetition count is 0.5. Furthermore, if the indicated dynamic PUCCH repetition count is 2, then there can be 8 PUCCH repetitions.

[0098] Figure 7 This is a diagram 700 illustrating example communication between UE 702 and base station 704.

[0099] At 710, base station 704 may transmit to UE 702 a radio resource control (RRC) message, such as message 712, which includes an indication of the number of repetitions of the physical uplink control channel (PUCCH).

[0100] At 720, UE 702 may receive from base station 704 a Radio Resource Control (RRC) message, such as message 712, that includes an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH). This indication may correspond to a resource list.

[0101] In some respects, the PUCCH repetition number can be at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number, configured based on the PUCCH format or the PUCCH resource. If the PUCCH repetition number is the total repetition number, the total repetition number can correspond to the PUCCH repetition number of spatial relationship information 1 and the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is the actual repetition number, the actual repetition number can be applied to the PUCCH repetition number of spatial relationship information 1 or the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is a scaled value of the PUCCH repetition number, the scaled value of the PUCCH repetition number can be half or twice the PUCCH repetition number.

[0102] At 730, base station 704 may transmit downlink control information (DCI) (e.g., DCI 732) to UE 702, indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions.

[0103] At 740, UE 702 may receive from base station 704 downlink control information (DCI) (e.g., DCI 732) indicating a code point associated with the PUCCH repetition number. This code point includes at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number. The code point of the DCI may include at least one K1 value, and the at least one K1 value may correspond to the PUCCH repetition number. Furthermore, the at least one K1 value may further correspond to a timing offset. The code point of the DCI may include the PUCCH repetition number such that the PUCCH repetition number overwrites a previous PUCCH repetition number.

[0104] At 750, UE 702 can select one of the one or more PUCCH resource sets based on the Uplink Control Information (UCI) size. In some instances, the DCI can indicate the UCI size. The at least one PRI can correspond to a selected PUCCH resource set.

[0105] At 760, UE 702 may transmit PUCCH (e.g., PUCCH 762) to base station 704 via the PUCCH resources in one or more PUCCH resource sets, and the transmitted PUCCH corresponds to the number of PUCCH repetitions.

[0106] At 770, base station 704 can receive PUCCH (e.g., PUCCH 762) from UE 702 via the PUCCH resource in the one or more PUCCH resource sets, and the received PUCCH corresponds to the number of PUCCH repetitions.

[0107] Figure 8 This is a flowchart 800 of a wireless communication method. The method can be performed by a UE or a component of a UE (e.g., UE 104, 350, 702; device 1102; processing system, which may include memory 360 and may be the entire UE or a component of a UE (such as TX processor 368, controller / processor 359, TX processor 354, antennas 352, etc.)). The method described herein can provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0108] In 802, the UE can receive from the base station a Radio Resource Control (RRC) message including an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH), such as in combination with... Figure 4 , 5As described in the examples in 6A, 6B, 6C, and 7. For example, UE 702 may receive from the base station a Radio Resource Control (RRC) message including an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH), as combined with Figure 7 As described in 720. Furthermore, 802 can be... Figure 11 The specified component 1140 is executed. This instruction may correspond to a resource list.

[0109] In some respects, the PUCCH repetition number can be at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number, configured based on the PUCCH format or the PUCCH resource. If the PUCCH repetition number is the total repetition number, the total repetition number can correspond to the PUCCH repetition number of spatial relationship information 1 and the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is the actual repetition number, the actual repetition number can be applied to the PUCCH repetition number of spatial relationship information 1 or the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is a scaled value of the PUCCH repetition number, the scaled value of the PUCCH repetition number can be half or twice the PUCCH repetition number.

[0110] At 804, the UE can receive downlink control information (DCI) from base station 704 indicating a code point associated with the PUCCH repetition number. This code point includes at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as combined with... Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, UE 702 may receive downlink control information (DCI) from base station 704 indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as in combination with... Figure 7 As described in 740. Furthermore, 804 can be... Figure 11 The determining component 1140 in the DCI is executed. The code point of the DCI may include at least one K1 value, and the at least one K1 value may correspond to the number of PUCCH repetitions. Moreover, the at least one K1 value may further correspond to a timing offset. The code point of the DCI may include the number of PUCCH repetitions, such that the number of PUCCH repetitions overwrites the previous number of PUCCH repetitions.

[0111] In 808, the UE can transmit PUCCH to the base station via the PUCCH resources in one or more PUCCH resource sets. The transmitted PUCCH corresponds to the number of PUCCH repetitions, such as in combination. Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, UE 702 may transmit a PUCCH to the base station via the PUCCH resource in one or more PUCCH resource sets, the transmitted PUCCH corresponding to the number of PUCCH repetitions, as in combination with... Figure 7 As described in 760. Furthermore, 808 can be... Figure 11 The determined component 1140 is executed.

[0112] Figure 9 This is a flowchart 900 of a wireless communication method. The method can be performed by a UE or a component of a UE (e.g., UE 104, 350, 702; device 1102; processing system, which may include memory 360 and may be the entire UE or a component of a UE (such as TX processor 368, controller / processor 359, TX processor 354, antennas 352, etc.)). The method described herein can provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0113] In 902, the UE can receive from the base station a Radio Resource Control (RRC) message including an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH), such as in combination with... Figure 4 , 5 As described in the examples in 6A, 6B, 6C, and 7. For example, UE 702 may receive from the base station a Radio Resource Control (RRC) message including an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH), as combined with Figure 7 As described in 720. Furthermore, 902 can be... Figure 11 The specified component 1140 is executed. This instruction may correspond to a resource list.

[0114] In some respects, the PUCCH repetition number can be at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number, configured based on the PUCCH format or the PUCCH resource. If the PUCCH repetition number is the total repetition number, the total repetition number can correspond to the PUCCH repetition number of spatial relationship information 1 and the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is the actual repetition number, the actual repetition number can be applied to the PUCCH repetition number of spatial relationship information 1 or the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is a scaled value of the PUCCH repetition number, the scaled value of the PUCCH repetition number can be half or twice the PUCCH repetition number.

[0115] In 904, the UE can receive downlink control information (DCI) from the base station indicating a code point associated with the PUCCH repetition number. This code point includes at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as combined with... Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, UE 702 may receive downlink control information (DCI) from base station 704 indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as in combination with... Figure 7 As described in 740. Furthermore, 904 can be... Figure 11 The determining component 1140 in the DCI is executed. The code point of the DCI may include at least one K1 value, and the at least one K1 value may correspond to the number of PUCCH repetitions. Moreover, the at least one K1 value may further correspond to a timing offset. The code point of the DCI may include the number of PUCCH repetitions, such that the number of PUCCH repetitions overwrites the previous number of PUCCH repetitions.

[0116] In 906, the UE can select one PUCCH resource set from one or more PUCCH resource sets based on the uplink control information (UCI) size, such as combining... Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, UE 702 may select one of the PUCCH resource sets from the one or more PUCCH resource sets based on the uplink control information (UCI) size, such as in combination with Figure 7 As described in 750. Furthermore, 906 can be derived from... Figure 11 The determination component 1140 in the process is executed. In some instances, the DCI may indicate the UCI size. The at least one PRI may correspond to a selected PUCCH resource set.

[0117] In 908, the UE can transmit PUCCH to the base station via the PUCCH resources in one or more PUCCH resource sets. The transmitted PUCCH corresponds to the number of PUCCH repetitions, such as in combination. Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, UE 702 may transmit a PUCCH to the base station via the PUCCH resource in one or more PUCCH resource sets, the transmitted PUCCH corresponding to the number of PUCCH repetitions, as in combination with... Figure 7 As described in 760. Furthermore, 908 can be... Figure 11 The determined component 1140 is executed.

[0118] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by a base station or components of a base station (e.g., base stations 102, 180, 310, 704; device 1202; processing system, which may include memory 376 and may be the entire base station or components of a base station (such as antennas 320, RX receiver 318, RX processor 370, controller / processor 375, etc.)). The method described herein can provide several benefits, such as improved communication signaling, resource utilization, and / or power savings.

[0119] In 1002, the base station can transmit a Radio Resource Control (RRC) message to the UE, including an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH), such as in combination with Figure 4 , 5 As described in the examples in 6A, 6B, 6C, and 7. For example, base station 704 may transmit a radio resource control (RRC) message to the UE including an indication of the number of repetitions of the physical uplink control channel (PUCCH), as combined with Figure 7 As described in 710. Furthermore, 1002 can be derived from... Figure 12 The specified component 1240 is executed. This instruction may correspond to a resource list.

[0120] In some respects, the PUCCH repetition number can be at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number, configured based on the PUCCH format or the PUCCH resource. If the PUCCH repetition number is the total repetition number, the total repetition number can correspond to the PUCCH repetition number of spatial relationship information 1 and the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is the actual repetition number, the actual repetition number can be applied to the PUCCH repetition number of spatial relationship information 1 or the PUCCH repetition number of spatial relationship information 2. If the PUCCH repetition number is a scaled value of the PUCCH repetition number, the scaled value of the PUCCH repetition number can be half or twice the PUCCH repetition number.

[0121] In step 1004, the base station may transmit downlink control information (DCI) to the UE indicating a code point associated with the PUCCH repetition number. This code point includes at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as combined with... Figure 4 , 5 As described in the examples in 6A, 6B, 6C, and 7. For example, base station 704 may transmit downlink control information (DCI) to the UE indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number, as in combination with... Figure 7 As described in 730. Furthermore, 1004 can be derived from... Figure 12 The determining component 1240 in the DCI is executed. The code point of the DCI may include at least one K1 value, and the at least one K1 value may correspond to the number of PUCCH repetitions. Moreover, the at least one K1 value may further correspond to a timing offset. The code point of the DCI may include the number of PUCCH repetitions, such that the number of PUCCH repetitions overwrites the previous number of PUCCH repetitions.

[0122] In some instances, one of the PUCCH resource sets in the one or more PUCCH resource sets may be based on the Uplink Control Information (UCI) size. The DCI may indicate the UCI size. Furthermore, the at least one PRI may correspond to a selected PUCCH resource set.

[0123] In 1006, the base station can receive PUCCH from the UE via the PUCCH resources in one or more PUCCH resource sets, and the received PUCCH corresponds to the number of PUCCH repetitions, such as in combination. Figure 4 , 5 As described in examples 6A, 6B, 6C, and 7. For example, base station 704 may receive a PUCCH from the UE via the PUCCH resources in one or more PUCCH resource sets, the received PUCCH corresponding to the number of PUCCH repetitions, as in combination with... Figure 7 As described in 740. Furthermore, 1006 can be derived from... Figure 12 The determined component 1240 is executed.

[0124] Figure 11 Figure 1100 illustrates an example of the hardware implementation of device 1102. Device 1102 is a UE and includes a cellular baseband processor 1104 (also referred to as a modem) coupled to a cellular RF transceiver 1122 and one or more Subscriber Identity Module (SIM) cards 1120, an application processor 1106 coupled to a Secure Digital Card (SD) card 1108 and a screen 1110, a Bluetooth module 1112, a Wireless Local Area Network (WLAN) module 1114, a Global Positioning System (GPS) module 1116, and a power supply 1118. The cellular baseband processor 1104 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include computer-readable media / memory. The computer-readable media / memory may be non-transient. The cellular baseband processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1104, the software causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1104 during software execution. The cellular baseband processor 1104 further includes a receiving component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes the one or more of the described components. The components within the communication manager 1132 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1104. The cellular baseband processor 1104 may be a component of the UE 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1102 may be a modem chip and include only the baseband processor 1104, and in another configuration, the device 1102 may be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional modules of device 1102.

[0125] The communication manager 1132 includes a determining component 1140 configured to receive from the base station a Radio Resource Control (RRC) message including an indication of the number of Physical Uplink Control Channel (PUCCH) repetitions, for example, as described above in conjunction with step 902. The determining component 1140 may also be configured to receive from the base station Downlink Control Information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH Resource Indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions, for example, as described above in conjunction with step 904. The determining component 1140 may also be configured to select a PUCCH resource set from the one or more PUCCH resource sets based on the size of the Uplink Control Information (UCI), for example, as described above in conjunction with step 906. The determining component 1140 can also be configured to transmit a PUCCH to the base station via the PUCCH resources in the one or more PUCCH resource sets, wherein the transmitted PUCCH corresponds to the number of PUCCH repetitions, for example, as described above in conjunction with step 908.

[0126] The equipment may include execution Figure 7 , 8 And the additional components of each block of the algorithm in the aforementioned flowchart of section 9. Therefore, Figure 7 , 8 Each block in the aforementioned flowchart of section 9 can be executed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0127] In one configuration, device 1102 (and specifically cellular baseband processor 1104) includes means for receiving from a base station a Radio Resource Control (RRC) message including an indication of the number of Physical Uplink Control Channel (PUCCH) repetitions; means for receiving from the base station downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH Resource Indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions; means for selecting one of the one or more PUCCH resource sets based on the uplink control information (UCI) size; and means for transmitting a PUCCH to the base station via the PUCCH resources in the one or more PUCCH resource sets, the transmitted PUCCH corresponding to the number of PUCCH repetitions. The aforementioned means may be one or more of the aforementioned components in device 1102 configured to perform the functions described by the aforementioned means. As described above, device 1102 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned device may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described herein.

[0128] Figure 12 Figure 1200 illustrates an example of the hardware implementation of device 1202. Device 1202 is a base station and includes a baseband unit 1204. The baseband unit 1204 can communicate with UE 104 via a cellular RF transceiver. The baseband unit 1204 may include computer-readable media / memory. The baseband unit 1204 is responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the baseband unit 1204, the software causes the baseband unit 1204 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the baseband unit 1204 during software execution. The baseband unit 1204 further includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes the one or more of the illustrated components. The components within the communication manager 1232 may be stored in the computer-readable media / memory and / or configured as hardware within the baseband unit 1204. The baseband unit 1204 may be a component of the BS 310 and may include memory 376 and / or at least one of the following: TX processor 316, RX processor 370, and controller / processor 375.

[0129] The communication manager 1232 includes a determining component 1240 configured to transmit a Radio Resource Control (RRC) message to a User Equipment (UE) including an indication of the number of Physical Uplink Control Channel (PUCCH) repetitions, for example, as described above in conjunction with step 1002. The determining component 1240 may also be configured to transmit to the UE Downlink Control Information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH Resource Indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions, for example, as described above in conjunction with step 1004. The determining component 1240 may also be configured to receive a PUCCH from the UE via the PUCCH resource in the one or more PUCCH resource sets, the received PUCCH corresponding to the number of PUCCH repetitions, for example, as described above in conjunction with step 1006.

[0130] The equipment may include execution Figure 7 and Figure 10 The additional components of each block of the algorithm in the aforementioned flowchart. Therefore, Figure 7 and Figure 10 Each box in the aforementioned flowchart can be executed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0131] In one configuration, device 1202 (and specifically baseband unit 1204) includes means for transmitting to user equipment (UE) a radio resource control (RRC) message including an indication of the number of physical uplink control channel (PUCCH) repetitions; means for transmitting to the UE downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with PUCCH resources in one or more PUCCH resource sets, the at least one PRI corresponding to the number of PUCCH repetitions; and means for receiving a PUCCH from the UE via the PUCCH resources in the one or more PUCCH resource sets, the received PUCCH corresponding to the number of PUCCH repetitions. The aforementioned means may be one or more of the aforementioned components in device 1202 configured to perform the functions described by the aforementioned means. As described above, device 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned apparatus may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions described by the aforementioned apparatus.

[0132] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is an explanation of exemplary methods. It should be understood that the specific order or hierarchy of the boxes in these process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to be limited to the specific order or hierarchy presented.

[0133] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element, unless specifically stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” The word “exemplary” is used herein to mean “example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term “some / a” 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 multiple A, multiple B, or multiple 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" can 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. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is expressly stated in the claims. The terms "module," "mechanism," "element," "device," etc., may not be a substitute for the term "apparatus." Thus, no claim element should be interpreted as an apparatus plus a function unless the element is expressly stated using the phrase "apparatus for..."

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

[0135] Aspect 1 is an apparatus for performing wireless communication at a UE, comprising at least one processor coupled to a memory, and the at least one processor being configured to: receive from a base station a radio resource control (RRC) message including an indication of a physical uplink control channel (PUCCH) repetition number; receive from the base station downlink control information (DCI) indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number; and transmit a PUCCH to the base station via the PUCCH resource in the one or more PUCCH resource sets, the transmitted PUCCH corresponding to the PUCCH repetition number.

[0136] Aspect 2 is an apparatus of aspect 1, wherein the code point of the DCI includes at least one K1 value, and the at least one K1 value corresponds to the number of PUCCH repetitions.

[0137] Aspect 3 is an apparatus of either aspect 1 or 2, wherein the at least one K1 value further corresponds to a timing offset.

[0138] Aspect 4 is an apparatus of any of Aspects 1 to 3, wherein the code point of the DCI includes the number of PUCCH repetitions such that the number of PUCCH repetitions overwrites the previous number of PUCCH repetitions.

[0139] Aspect 5 is an apparatus of any of Aspects 1 to 4, wherein the PUCCH repetition number is at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number configured based on the PUCCH format or the PUCCH resource.

[0140] Aspect 6 is an apparatus of any of Aspects 1 to 5, wherein the number of PUCCH repetitions is the total number of repetitions, and the total number of repetitions corresponds to the number of PUCCH repetitions of spatial relation information 1 and the number of PUCCH repetitions of spatial relation information 2.

[0141] Aspect 7 is an apparatus of any of Aspects 1 to 6, wherein the number of PUCCH repetitions is the actual number of repetitions, and the actual number of repetitions applies to the number of PUCCH repetitions of spatial relation information 1 or the number of PUCCH repetitions of spatial relation information 2.

[0142] Aspect 8 is an apparatus of any of Aspects 1 to 7, wherein the number of PUCCH repetitions is a scaled value of the number of PUCCH repetitions, and the scaled value of the number of PUCCH repetitions is half or twice the number of PUCCH repetitions.

[0143] Aspect 9 is an apparatus of any of Aspects 1 to 8, wherein the at least one processor is further configured to select a PUCCH resource set from the one or more PUCCH resource sets based on the uplink control information (UCI) size.

[0144] Aspect 10 is a device of any of aspects 1 to 9, wherein the DCI indicates the size of the UCI.

[0145] Aspect 11 is an apparatus of any of aspects 1 to 10, wherein the at least one PRI corresponds to a selected set of PUCCH resources.

[0146] Aspect 12 is an apparatus of any of aspects 1 to 11, wherein the instruction corresponds to a resource list.

[0147] Aspect 13 is an apparatus of any of aspects 1 to 12, further comprising a transceiver or antenna coupled to the at least one processor.

[0148] Aspect 14 is a wireless communication method for implementing any of Aspects 1 to 13.

[0149] Aspect 15 is an apparatus for wireless communication, including means for implementing any of aspects 1 to 13.

[0150] Aspect 16 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the processor enables the processor to implement any of aspects 1 to 13.

[0151] Aspect 17 is an apparatus for wireless communication at a base station, comprising at least one processor coupled to a memory, and the at least one processor being configured to: transmit to a user equipment (UE) a radio resource control (RRC) message including an indication of a physical uplink control channel (PUCCH) repetition number; transmit to the UE downlink control information (DCI) indicating a code point associated with the PUCCH repetition number, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, the at least one PRI corresponding to the PUCCH repetition number; and receive a PUCCH from the UE via the PUCCH resource in the one or more PUCCH resource sets, the received PUCCH corresponding to the PUCCH repetition number.

[0152] Aspect 18 is an apparatus of aspect 17, wherein the code point of the DCI includes at least one K1 value, and the at least one K1 value corresponds to the number of PUCCH repetitions.

[0153] Aspect 19 is an apparatus of either Aspect 17 or 18, wherein the code point of the DCI includes at least one K1 value, and the at least one K1 value corresponds to the number of PUCCH repetitions.

[0154] Aspect 20 is an apparatus of any of aspects 17 to 19, wherein the code point of the DCI includes the number of PUCCH repetitions such that the number of PUCCH repetitions overwrites the previous number of PUCCH repetitions.

[0155] Aspect 21 is an apparatus of any of Aspects 17 to 20, wherein the PUCCH repetition number is at least one of the total repetition number, the actual repetition number, or a scaled value of the PUCCH repetition number configured based on the PUCCH format or the PUCCH resource.

[0156] Aspect 22 is an apparatus of any of aspects 17 to 21, wherein the number of PUCCH repetitions is the total number of repetitions, and the total number of repetitions corresponds to the number of PUCCH repetitions of spatial relation information 1 and the number of PUCCH repetitions of spatial relation information 2.

[0157] Aspect 23 is an apparatus of any of aspects 17 to 22, wherein the number of PUCCH repetitions is an actual number of repetitions, and the actual number of repetitions applies to the number of PUCCH repetitions of spatial relation information 1 or the number of PUCCH repetitions of spatial relation information 2.

[0158] Aspect 24 is an apparatus of any of aspects 17 to 23, wherein the number of PUCCH repetitions is a scaled value of the number of PUCCH repetitions, and the scaled value of the number of PUCCH repetitions is half or twice the number of PUCCH repetitions.

[0159] Aspect 25 is an apparatus of any of Aspects 17 to 24, wherein one of the PUCCH resource sets in the one or more PUCCH resource sets is based on the uplink control information (UCI) size.

[0160] Aspect 26 is a device of any of aspects 17 to 25, wherein the DCI indicates the size of the UCI.

[0161] Aspect 27 is an apparatus of any of aspects 17 to 26, wherein the at least one PRI corresponds to the one PUCCH resource set.

[0162] Aspect 28 is an apparatus of any of aspects 17 to 27, wherein the instruction corresponds to a resource list.

[0163] Aspect 29 is an apparatus of any of aspects 17 to 28, further comprising a transceiver or antenna coupled to the at least one processor.

[0164] Aspect 30 is a wireless communication method for implementing any of Aspects 17 to 29.

[0165] Aspect 31 is an apparatus for wireless communication, including means for implementing any of aspects 17 to 29.

[0166] Aspect 32 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the processor enables the processor to implement any of aspects 17 to 29.

Claims

1. An apparatus for performing wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor, the at least one processor being coupled to the memory and configured to: Receive a Radio Resource Control (RRC) message from the network node, which includes an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH). The network node receives downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, wherein the code point of the DCI includes at least one K1 value, and the at least one K1 value corresponds to the number of PUCCH repetitions. Select one PUCCH resource set from the one or more PUCCH resource sets based on the uplink control information UCI size; as well as PUCCHs are transmitted to the network node via the PUCCH resources in one or more PUCCH resource sets, and the transmitted PUCCHs correspond to the number of PUCCH repetitions.

2. The apparatus of claim 1, wherein the at least one K1 value further corresponds to a timing offset.

3. The apparatus of claim 1, wherein the code point of the DCI includes the number of PUCCH repetitions such that the number of PUCCH repetitions overwrites a previous number of PUCCH repetitions.

4. The apparatus of claim 1, wherein the PUCCH repeat number is at least one of a total repeat number, an actual repeat number, or a scaled value of the PUCCH repeat number configured based on the PUCCH format or the PUCCH resource.

5. The apparatus of claim 4, wherein the number of PUCCH repetitions is the total number of repetitions, and the total number of repetitions corresponds to the number of PUCCH repetitions in spatial relationship information 1 and the number of PUCCH repetitions in spatial relationship information 2.

6. The apparatus of claim 4, wherein the number of PUCCH repetitions is the actual number of repetitions, and the actual number of repetitions applies to the number of PUCCH repetitions in spatial relationship information 1 or the number of PUCCH repetitions in spatial relationship information 2.

7. The apparatus of claim 4, wherein the number of PUCCH repetitions is a scaled value of the number of PUCCH repetitions, and the scaled value of the number of PUCCH repetitions is half or twice the number of PUCCH repetitions.

8. The apparatus of claim 1, wherein the DCI indicates the size of the UCI.

9. The apparatus of claim 1, wherein the at least one PRI corresponds to a selected set of PUCCH resources.

10. The apparatus of claim 1, wherein the instruction corresponds to a resource list.

11. The apparatus of claim 1, further comprising a transceiver or antenna coupled to the at least one processor.

12. A method for conducting wireless communication at a user equipment (UE), comprising: Receive a Radio Resource Control (RRC) message from the network node, which includes an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH). The network node receives downlink control information (DCI) indicating a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, wherein the code point of the DCI includes at least one K1 value, and the at least one K1 value corresponds to the number of PUCCH repetitions. Select one PUCCH resource set from the one or more PUCCH resource sets based on the uplink control information UCI size; as well as PUCCHs are transmitted to the network node via the PUCCH resources in one or more PUCCH resource sets, and the transmitted PUCCHs correspond to the number of PUCCH repetitions.

13. The method of claim 12, wherein the PUCCH repeat number is at least one of the total repeat number, the actual repeat number, or a scaled value of the PUCCH repeat number configured based on the PUCCH format or the PUCCH resource.

14. An apparatus for wireless communication at a network node, comprising: Memory; as well as At least one processor, the at least one processor being coupled to the memory and configured to: Transmits a Radio Resource Control (RRC) message that includes an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH); Downlink control information (DCI) is transmitted that indicates a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, wherein the code point of the DCI includes at least one K1 value and the at least one K1 value corresponds to the number of PUCCH repetitions. as well as A PUCCH is received via one or more PUCCH resource sets, the received PUCCH corresponding to the number of PUCCH repetitions, wherein one of the one or more PUCCH resource sets is based on the uplink control information (UCI) size.

15. The apparatus of claim 14, wherein the at least one K1 value further corresponds to a timing offset.

16. The apparatus of claim 14, wherein the code point of the DCI includes the number of PUCCH repetitions such that the number of PUCCH repetitions overwrites a previous number of PUCCH repetitions.

17. The apparatus of claim 14, wherein the PUCCH repeat number is at least one of a total repeat number, an actual repeat number, or a scaled value of the PUCCH repeat number configured based on the PUCCH format or the PUCCH resource.

18. The apparatus of claim 17, wherein the number of PUCCH repetitions is the total number of repetitions, and the total number of repetitions corresponds to the number of PUCCH repetitions in spatial relation information 1 and the number of PUCCH repetitions in spatial relation information 2.

19. The apparatus of claim 17, wherein the number of PUCCH repetitions is the actual number of repetitions, and the actual number of repetitions applies to the number of PUCCH repetitions in spatial relation information 1 or the number of PUCCH repetitions in spatial relation information 2.

20. The apparatus of claim 17, wherein the number of PUCCH repetitions is a scaled value of the number of PUCCH repetitions, and the scaled value of the number of PUCCH repetitions is half or twice the number of PUCCH repetitions.

21. The apparatus of claim 14, wherein the DCI indicates the size of the UCI.

22. The apparatus of claim 14, wherein the at least one PRI corresponds to the one PUCCH resource set.

23. The apparatus of claim 14, wherein the instruction corresponds to a resource list.

24. The apparatus of claim 14, further comprising a transceiver or antenna coupled to the at least one processor.

25. A method for wireless communication at a network node, comprising: Transmits a Radio Resource Control (RRC) message that includes an indication of the number of repetitions of the Physical Uplink Control Channel (PUCCH); Downlink control information (DCI) is transmitted that indicates a code point associated with the number of PUCCH repetitions, the code point including at least one PUCCH resource indicator (PRI) associated with a PUCCH resource in one or more PUCCH resource sets, wherein the code point of the DCI includes at least one K1 value and the at least one K1 value corresponds to the number of PUCCH repetitions. as well as A PUCCH is received via one or more PUCCH resource sets, the received PUCCH corresponding to the number of PUCCH repetitions, wherein one of the one or more PUCCH resource sets is based on the uplink control information (UCI) size.

Images