Dynamic indication of pucch repetition factor

Abstract

Methods and apparatuses for providing an indication of a PUCCH repetition factor within DCI. The apparatus allocates a downlink resource for at least one UE. The downlink resource includes an indication of a PUCCH repetition factor within DCI. The apparatus transmits the downlink resource to the at least one UE. The indication of the PUCCH repetition factor can include a dynamic indication or an implicit indication of the PUCCH repetition factor. The dynamic indication of the PUCCH repetition factor can be indicated in a separate bit field within the DCI. The implicit indication of the PUCCH repetition factor can be based on a time domain resource allocation of an associated PDSCH.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application No. 63 / 138189, filed January 15, 2021, entitled “Dynamic Indication of PUCCH Repetition Factor,” and U.S. Patent Application No. 17 / 451385, filed October 19, 2021, entitled “Dynamic Indication of PUCCH Repetition Factor,” which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically, to the configuration of providing an indication of the repetition factor of the Physical Uplink Control Channel (PUCCH) within a downlink control indicator (DCI). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of communication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of these multiple access technologies include: Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables 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 Mobile Broadband Evolution program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. 5G NR technology requires further improvement. These improvements may also apply to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of them. This overview is not a comprehensive overview of all conceived aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a base station. The device may be a processor and / or modem at the base station or the base station itself. The apparatus allocates downlink resources to at least one user equipment (UE). The downlink resources include an indication of the physical uplink control channel (PUCCH) repetition factor within a downlink control indicator (DCI). The apparatus transmits the downlink resources to the at least one UE.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The device may be a processor and / or modem at the UE or the UE itself. The apparatus receives an allocation of downlink resources from a base station, the downlink resources including an indication of a Physical Uplink Control Channel (PUCCH) repetition factor within a downlink control indicator (DCI). The apparatus communicates with the base station based on the downlink resources.

[0009] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

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

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

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

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

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

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

[0016] Figure 4 This is a diagram illustrating an example of DCI format.

[0017] Figure 5 This is a diagram illustrating an example of DCI format.

[0018] Figure 6 This is a call flow diagram of signaling between a UE and a base station according to certain aspects of this disclosure.

[0019] Figure 7 This is a flowchart of a wireless communication method.

[0020] Figure 8 This is a diagram illustrating an example of the hardware implementation of the illustrated device.

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

[0022] Figure 10 This is a diagram illustrating an example of the hardware implementation of the illustrated device. Detailed Implementation

[0023] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing 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 cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0024] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0025] For 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 functions described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, functions, etc.

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

[0027] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations and / or uses may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, artificial intelligence (AI) based devices, etc.). While some examples may or may not specifically point to a use case or application, broad applicability to the described innovations can emerge. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors(multiple), interleavers, adders / summers, etc.). The innovations described herein are expected to be implemented in a wide range of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and structures.

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

[0029] 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 perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, 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 device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via 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.

[0030] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including small cells and macro cells can be considered a heterogeneous network. The heterogeneous network may also include Home Evolved Node B (eNB) (HeNB), which can provide services to restricted groups, which can be considered closed subscriber groups (CSGs). 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 (downlink) (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 techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. 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, etc. MHz) for transmission on each of the carriers allocated in a total of Yx MHz (e.g., for x component carriers) of carrier aggregation. The carriers may be adjacent to each other or not. The allocation of carriers with respect to DL and UL may be asymmetric (e.g., more or fewer carriers may be allocated to DL than 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).

[0031] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0032] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 (e.g., in unlicensed spectrum such as 5 GHz). When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0033] 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.) as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0034] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range designations FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and literature, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes arise regarding FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and literature, although FR2 is different from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0035] The frequencies between FR1 and FR2 are often referred to as intermediate frequency (IF) frequencies. Recent 5G NR studies have designated the operating bands of these IF frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). Frequency bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to IF frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating bands have been designated as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0036] In light of the foregoing, unless otherwise specified, it should be understood that the terms "below 6 GHz" and the like (if used herein) can broadly indicate frequencies below 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specified, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly indicate frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may include EHF band frequencies.

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

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

[0039] 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. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides IP address allocation and other functions to the UE. 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 act as an entry point for content provider MBMS transmission, 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 services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0040] 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 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted via 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, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0041] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable terminology. 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, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electrical meters, air pumps, large or small kitchen appliances, medical 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, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 can also be referred to as 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, mobile phone, user agent, mobile client, client, or some other suitable terms. In some scenarios, the term UE can also be applied to one or more accompanying devices, such as in a device constellation arrangement. One or more of these devices can access the network jointly and / or individually.

[0042] Refer again Figure 1 In some aspects, UE 104 can be configured to receive an indication of the PUCCH repetition factor within the DCI. For example, UE 104 may include a resource component 198 configured to receive the allocation of downlink resources, which include an indication of the PUCCH repetition factor. UE 104 may receive the allocation of downlink resources from base station 180. The downlink resources include an indication of the PUCCH repetition factor within the DCI. UE 104 may communicate with the base station based on these downlink resources.

[0043] Refer again Figure 1 In some aspects, base station 180 may be configured to provide the UE with an indication of the PUCCH repetition factor within the DCI. For example, base station 180 may include allocation component 199 configured to allocate downlink resources for UE 104, the downlink resources including the indication of the PUCCH repetition factor. Base station 180 may allocate downlink resources for UE 104. The downlink resources include the indication of the PUCCH repetition factor within the DCI.

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

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

[0046] Figure 2A-2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is regular or extended. For regular CP, each time slot may include 14 symbols, while for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may 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 CP and the numberology. The numberology defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0047] μ <![CDATA[SCS Δf=2 μ ·15[kHz]]> Cyclic prefix 0 15 conventional 1 30 conventional 2 60 Regular, Extended 3 120 conventional 4 240 conventional

[0048] For a standard CP (14 symbols / slot), different mathematical sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, mathematical set 2 allows 4 slots per subframe. Therefore, for both the standard CP and mathematical set μ, there are 14 symbols / slot per slot and 2μ slots / subframe. The subcarrier spacing can be equal to 2. μ *15kHz, where μ is the mathematical set 0 to 4. Therefore, the mathematical set μ = 0 has a subcarrier spacing of 15kHz, and the mathematical set μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2D Examples are provided for a standard frequency division multiplexing (CP) with 14 symbols per slot and a mathematical set μ=2 with 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, one or more different bandwidth portions (BWPs) of frequency division multiplexing can exist (see...). Figure 2B Each BWP can have a specific set of mathematical parameters and a CP (regular or extended).

[0049] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) that extends 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.

[0050] like Figure 2A As shown, some of the 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).

[0051] Figure 2B The illustration shows examples of various DL channels within a subframe of a frame. 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 comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. UE 104 uses the PSS to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The UE uses the SSS 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 DM-RS. The Physical Broadcast Channel (PBCH) (which carries 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 multiple RBs and System Frame Numbers (SFNs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0052] like Figure 2CAs illustrated, 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 second symbol of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted, and depending on the specific PUCCH format used. The UE can transmit a Sounding 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.

[0053] Figure 2D The diagram illustrates examples of various UL channels within a subframe of a frame. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQACK bits indicating one or more ACKs and / or negative ACKs (NACK)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0054] Figure 3This is a block diagram of base station 310 communicating with 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 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service 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 functions 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 for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) transmission, error correction via ARQ, RLC service data unit (SDU) connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions associated with mapping between logical channels and transmit channels, multiplexing MAC SDUs to transmit blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0055] 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 transmit channel, forward error correction (FEC) encoding / decoding of the transmit 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 cluster 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 encoded and modulated symbols can then be segmented into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived from a reference signal 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 use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0056] At UE 350, each receiver 354RX receives signals through its corresponding 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 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on this 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 and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal clustering point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision then performs decoding and deinterleaving to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0057] 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, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels 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.

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

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

[0060] The UL transmission is processed at base station 310 in a manner similar to that described in the receiver function description at UE 350. Each receiver 318RX receives the signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

[0061] 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, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover recovered 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.

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

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

[0064] The aspects presented herein provide a configuration for dynamically indicating the repetition factor of the PUCCH. For example, a base station can allocate downlink resources to a UE, wherein the downlink resources include an indication of the PUCCH repetition factor within the DCI. The DCI can be the PDSCH associated with the UE's scheduling.

[0065] Figure 4 Figure 400 illustrates an example of a DCI format. A DCI format includes uplink grants (e.g., format 0_0, format 0_1) and downlink distributions (e.g., format 1_0, format 1_1). Formats 0_0 and 1_0 are fallback DCIs with the fewest required fields. Formats 1_1 and 0_1 have more fields than formats 0_0 and 1_0. Figure 5 Figure 500 is an example of the available fields for downlink-related DCI (e.g., format 1_0). Figure 5 Figure 500 indicates which fields can be configurable and the bit width of each field. A configurable field indicates whether the field exists only when a certain function is configured or always exists. For example, if a field is configured to exist, the bit width of the field may or may not depend on that configuration. Figure 500 also indicates whether the field is included in the fallback DCI or a comment. Figure 500 also indicates the bit width of the non-fallback DCI. When the field is indicated to exist in the fallback DCI, the bit width of the field within the fallback DCI may be the same as or smaller than the bit width of the non-fallback DCI.

[0066] Figure 6 This is a call flowchart 600 showing the signaling between UE 602 and base station 604. Base station 604 can be configured to provide at least one cell. UE 602 can be configured to communicate with base station 604. For example, in Figure 1 In the context of this, base station 604 may correspond to base station 102 / 180, and accordingly, the cell may include a geographical coverage area 110 in which communication coverage is provided and / or a small cell 102' having coverage area 110'. Furthermore, UE 602 may correspond to at least UE 104. In another example, in Figure 3In the context of UE 604, UE 604 can correspond to UE 310, and UE 602 can correspond to UE 350.

[0067] As illustrated at 606, base station 604 can allocate downlink resources for at least one UE (e.g., UE 602). Downlink resources may include an indication of the PUCCH repetition factor within the DCI. The DCI can schedule associated PDSCHs for UE 602. In some aspects, the indication of the PUCCH repetition factor may include a dynamic or implicit indication of the PUCCH repetition factor.

[0068] In aspects of indicating the PUCCH repeat factor, including dynamic indication, the dynamic indication of the PUCCH repeat factor can be indicated in a separate bit field within the DCI. For example, the separate bit field can be within a non-back-off DCI. The dynamic indication of the PUCCH repeat factor can apply only to PUCCHs carrying an acknowledgment (ACK) or non-acknowledgment (NACK) for the corresponding scheduled PDSCH. In some aspects, the dynamic indication of the PUCCH repeat factor can be valid for all PUCCHs carrying an ACK or NACK for any future scheduled PDSCH. For example, the dynamic indication of the PUCCH repeat factor can be valid for future scheduled PDSCHs until it is overwritten or canceled by a second dynamic indication of the second PUCCH repeat factor. For example, for a PUCCH carrying an ACK / NACK for a PDSCH scheduled by a back-off DCI, the previous non-back-off DCI indication of the PUCCH repeat factor can be applied. In some respects, a dynamic indication of a PUCCH repeat factor can also be applied to other PUCCHs (e.g., PUCCHs carrying CSI reports, or other PUCCHs not associated with a PDCCH) until it is overridden or canceled by another dynamic indication of a repeat factor for another PUCCH.

[0069] In aspects where the indication of the PUCCH repetition factor includes implicit indication of the PUCCH repetition factor, the implicit indication of the PUCCH repetition factor can be based on the time-domain resource allocation of the associated PDSCH. For example, the implicit indication of the PUCCH repetition factor can be based on a new column in the time-domain resource allocation table of the associated PDSCH. This can be applied to both rollback and non-rollback DCI formats. The new column in the time-domain resource allocation table (e.g., a newly added interpretation of the time-domain resource allocation bit field) can be configured via RRC signaling. In some aspects, the time-domain resource allocation table of the time-domain resource allocation can include additional interpretations of the time-domain resource allocation bit field. The additional interpretations of the time-domain resource allocation bit field can be configured via RRC signaling. In some aspects, the additional interpretations of the time-domain resource allocation bit field can be applied to both rollback and non-rollback DCI formats. The implicit indication of the PUCCH repetition factor can be based on additional interpretations of the transmit power control (TPC) command for the PUCCH. For example, the TPC command can be network-configurable such that the bits constituting the bit field can implicitly indicate the PUCCH repeat factor. In some aspects, the implicit indication of the PUCCH repeat factor can be based on an additional interpretation of the Virtual Resource Block (VRB) to Physical Resource Block (PRB) mapping. For example, the value or bit field of the VRB to PRB mapping can implicitly indicate the PUCCH repeat factor. In some cases, such as Figure 5 As shown in Figure 500, one or more fields in the DCI format can be configured to implicitly indicate the PUCCH repeat factor. These fields can be configured to implicitly indicate the PUCCH repeat factor based on bit fields or based on a new interpretation of the commands associated with the fields.

[0070] As illustrated at 608, base station 604 can send downlink resources to UE 602. UE 602 can receive downlink resource allocation from base station 604.

[0071] As illustrated at 610, UE 602 can communicate with base station 604 based on the allocated downlink resources received from base station 604.

[0072] Figure 7 This is a flowchart 700 of a wireless communication method. The method can be performed by a base station or components of a base station (e.g., base station 102 / 180; device 802; baseband unit 804, which may include memory 376 and may be the entire base station 310 or components of base station 310, such as TX processor 316, RX processor 370, and / or controller / processor 375). One or more of the operations illustrated can be omitted, interchanged, or performed simultaneously. This method can allow the base station to provide an indication of the PUCCH repetition factor within the DCI.

[0073] At 702, the base station can allocate downlink resources for at least one UE. For example, 702 can be performed by the allocation component 840 of apparatus 802. Downlink resources may include an indication of the PUCCH repetition factor in the DCI. The DCI may schedule associated PDSCHs for at least one UE. In some aspects, the indication of the PUCCH repetition factor may include a dynamic indication or an implicit indication of the PUCCH repetition factor. In aspects where the indication of the PUCCH repetition factor includes a dynamic indication, the dynamic indication of the PUCCH repetition factor may be indicated in a separate bit field within the DCI. The DCI may include a non-backoff DCI. The dynamic indication of the PUCCH repetition factor may correspond to a PUCCH carrying an ACK or NACK for the corresponding scheduled PDSCH. In some aspects, the dynamic indication of the PUCCH repetition factor corresponds to all PUCCHs carrying an ACK or NACK for any future scheduled PDSCH. The dynamic indication of the PUCCH repetition factor may be valid for future scheduled PDSCHs until overwritten or canceled by a second dynamic indication of the second PUCCH repetition factor. In some aspects, a dynamic indication of the PUCCH repetition factor can correspond to other PUCCHs until it is overridden or canceled by another dynamic indication of the repetition factor of another PUCCH. In aspects where the indication of the PUCCH repetition factor includes an implicit indication, the implicit indication of the PUCCH repetition factor can be based on the time-domain resource allocation of the associated PDSCH. In some aspects, the time-domain resource allocation table of the time-domain resource allocation can include additional interpretations of the time-domain resource allocation bit fields. The additional interpretations of the time-domain resource allocation bit fields can be configured via RRC signaling. In some aspects, the additional interpretations of the time-domain resource allocation bit fields can be applied to both rollback and non-rollback DCI formats. The implicit indication of the PUCCH repetition factor can be based on an additional interpretation of the TPC commands used for the PUCCH. In some aspects, the implicit indication of the PUCCH repetition factor can be based on an additional interpretation of the VRB-to-PRB mapping.

[0074] At point 704, the base station can send downlink resources to at least one UE. For example, 704 can be performed by resource component 842 of apparatus 802. The base station and the at least one UE can communicate with each other based at least on downlink resources or PUCCH repetition factor.

[0075] Figure 8Figure 800 illustrates an example of a hardware implementation of device 802. Device 802 may be a base station, a component of a base station, or may implement base station functions. In some aspects, device 802 may include a baseband unit 804. Baseband unit 804 may communicate with UE 104 via cellular RF transceiver 822. Baseband unit 804 may include computer-readable medium / memory. Baseband unit 804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by baseband unit 804, the software causes baseband unit 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 804 during software execution. Baseband unit 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. Communication manager 832 includes one or more of the illustrated components. Components within communication manager 832 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 804. The baseband unit 804 may be a component of the base station 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0076] Communication manager 832 includes allocation component 840, which can allocate downlink resources for at least one UE, for example, as in combination with Figure 7 As described in 702. The communication manager 832 also includes a resource component 842, which can send downlink resources to at least one UE, for example, as in combination with Figure 7 As described in 704.

[0077] The apparatus may include execution Figure 7 The additional components of each box in the flowchart of the algorithm. Thus, Figure 7 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to perform the stated processing / algorithm, implemented by a processor configured to perform the stated processing / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0078] As shown in the figure, apparatus 802 may include various components configured for various functions. In one configuration, apparatus 802, particularly baseband unit 804, includes components for allocating downlink resources to at least one UE, the downlink resources including an indication of a PUCCH repetition factor within the DCI. The apparatus includes components for transmitting downlink resources to at least one UE. This component may be one or more of the components of apparatus 802 configured to perform the functions listed therein. As described above, apparatus 802 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the component may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions listed therein.

[0079] 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; device 1002; cellular baseband processor 1004, which may include memory 360 and may be the entire UE 350 or components of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. The method can allow the UE to receive an indication of the PUCCH repetition factor within the DCI.

[0080] At 902, the UE can receive downlink resource allocation from the base station. For example, 902 can be performed by resource component 1040 of apparatus 1002. Downlink resources may include an indication of the PUCCH repetition factor within the DCI. The DCI may be a PDSCH associated with at least one UE scheduling. In some aspects, the indication of the PUCCH repetition factor may include a dynamic indication or an implicit indication of the PUCCH repetition factor. In aspects where the indication of the PUCCH repetition factor includes a dynamic indication, the dynamic indication of the PUCCH repetition factor may be indicated in a separate bit field within the DCI. The DCI may include a non-backoff DCI. The dynamic indication of the PUCCH repetition factor may correspond to a PUCCH carrying an ACK or NACK for the corresponding scheduled PDSCH. In some aspects, the dynamic indication of the PUCCH repetition factor corresponds to all PUCCHs carrying an ACK or NACK for any future scheduled PDSCH. A dynamic indication of the PUCCH repetition factor can be valid for future scheduled PDSCHs until overridden or canceled by a second dynamic indication of the second PUCCH repetition factor. In some aspects, a dynamic indication of the PUCCH repetition factor can correspond to other PUCCHs until overridden or canceled by another dynamic indication of another PUCCH repetition factor. In aspects where the indication of the PUCCH repetition factor includes an implicit indication of the PUCCH repetition factor, the implicit indication of the PUCCH repetition factor can be based on the time-domain resource allocation of the associated PDSCH. In some aspects, the time-domain resource allocation table of the time-domain resource allocation can include additional interpretation of the time-domain resource allocation bit field. The additional interpretation of the time-domain resource allocation bit field can be configured via RRC signaling. In some aspects, the additional interpretation of the time-domain resource allocation bit field can be applied to both rollback and non-rollback DCI formats. The implicit indication of the PUCCH repetition factor can be based on an additional interpretation of the TPC command used for the PUCCH. In some respects, the implicit indication of the PUCCH repeat factor can be based on an additional interpretation of the VRB to PRB mapping.

[0081] At point 904, the UE can communicate with the base station at least based on downlink resources. For example, 904 can be performed by the communication component 1042 of device 1002. The base station and the UE can communicate with each other based on downlink resources or PUCCH repetition factor.

[0082] Figure 10Figure 1000 illustrates an example of a hardware implementation of device 1002. Device 1002 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 1002 may include a cellular baseband processor 1004 (also referred to as a modem) coupled to a cellular RF transceiver 1022. In some aspects, device 1002 may also include one or more Subscriber Identity Module (SIM) cards 1020, an application processor 1006 coupled to a Secure Digital Card (SD) card 1008 and a screen 1010, a Bluetooth module 1012, a Wireless Local Area Network (WLAN) module 1014, a Global Positioning System (GPS) module 1016, or a power supply 1018. The cellular baseband processor 1004 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1022. The cellular baseband processor 1004 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. Cellular baseband processor 1004 is responsible for general processing, including the execution of software stored on a computer-readable medium / memory. When executed by cellular baseband processor 1004, this software causes cellular baseband processor 1004 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by cellular baseband processor 1004 during software execution. Cellular baseband processor 1004 also includes a receiving component 1030, a communication manager 1032, and a transmitting component 1034. Communication manager 1032 includes one or more of the illustrated components. Components within communication manager 1032 can be stored in computer-readable medium / memory and / or configured as hardware within cellular baseband processor 1004. Cellular baseband processor 1004 can be a component of UE 350 and can include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1002 may be a modem chip and may only include baseband processor 1004, while in another configuration, device 1002 may be the entire UE (e.g., see [link to relevant documentation]). Figure 3 (350), and includes an additional module of device 1002.

[0083] Communication manager 1032 includes resource component 1040, which is configured to receive downlink resource allocations from the base station, for example, as in combination with Figure 9 As described in 902. The communication manager 1032 also includes a communication component 1042 configured to communicate with the base station at least based on downlink resources, for example, as in conjunction with... Figure 9 As described in 904.

[0084] The device may include execution Figure 9 The additional components of each box in the flowchart of the algorithm. Thus, Figure 9 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to execute the stated processing / algorithm, implemented by a processor configured to implement the stated processing / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0085] As shown in the figure, device 1002 may include various components configured for various functions. In one configuration, device 1002, particularly cellular baseband processor 1004, includes components for receiving downlink resource allocations from a base station, the downlink resources including an indication of PUCCH repetition factors within the DCI. The device includes components for communicating with the base station based on the downlink resources. These components may be one or more of the components of device 1002 configured to perform the functions listed therein. As described above, device 1002 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the components may be the TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions listed therein.

[0086] It should be understood that the specific order or hierarchy of boxes in the disclosed process / flowchart is illustrative of the method. It is understood that the specific order or hierarchy of boxes in the process / flowchart can be rearranged according to design preferences. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of the individual boxes in a sample order and are not intended to limit one to the specific order or hierarchy presented.

[0087] The preceding description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but rather to encompass the full scope consistent with the language of the claims, wherein references to elements in the singular form are not intended to mean “one and only one,” but rather “one or more” unless specifically stated. Terms such as “if,” “when,” and “while” should be interpreted as “under the condition”, rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply a response to the occurrence of an action or a direct action during the occurrence of an action, but simply imply that an action will occur if the condition is met, without requiring a specific or direct time limit for the occurrence of that action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior or better than other aspects. Unless specifically stated, the term “some” means 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 combinations thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or combinations thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are known to or will be known hereafter by 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 to be made public, whether or not such disclosure is expressly enumerated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” may not replace the term “component.” Therefore, unless the element is explicitly listed using the phrase “component for…,” no element in any claim may be interpreted as a component plus a function.

[0088] The following aspects are illustrative only and may be combined with, but not limited to, other aspects or teachings described herein.

[0089] Aspect 1 is an apparatus for wireless communication at a base station, comprising at least one processor, the at least one processor being coupled to a memory and configured to: allocate downlink resources to at least one UE, the downlink resources including an indication of a PUCCH repetition factor within a DCI; and transmit the downlink resources to the at least one UE.

[0090] Aspect 2 is the apparatus as described in aspect 1, further comprising: a transceiver coupled to the at least one processor.

[0091] Aspect 3 is the apparatus as described in either aspect 1 or 2, and further includes: a PDSCH associated with UE scheduling by DCI.

[0092] Aspect 4 is the apparatus as described in any one of aspects 1-3, further comprising: the indication of the PUCCH repeat factor includes a dynamic indication or an implicit indication of the PUCCH repeat factor.

[0093] Aspect 5 is an apparatus as described in any of aspects 1-4, further comprising: a dynamic indication of the PUCCH repetition factor is indicated in a separate bit field within the DCI, wherein the DCI includes a non-back-off DCI.

[0094] Aspect 6 is an apparatus as described in any one of aspects 1-5, further comprising: a dynamic indication of the PUCCH repetition factor corresponding to a PUCCH carrying an ACK or NACK for the corresponding scheduled PDSCH.

[0095] Aspect 7 is the apparatus as described in any of aspects 1-6, further comprising: a dynamic indication of the PUCCH repetition factor corresponding to all PUCCHs carrying an ACK or NACK for any future scheduled PDSCH.

[0096] Aspect 8 is an apparatus as described in any one of aspects 1-7, further comprising: a dynamic indication of the PUCCH repetition factor is valid for future scheduled PDSCHs until it is canceled by overwriting a second dynamic indication of the second PUCCH repetition factor.

[0097] Aspect 9 is the apparatus as described in any one of aspects 1-8, further comprising: a dynamic indication of a PUCCH repetition factor corresponding to another PUCCH until overwritten or canceled by another dynamic indication of a PUCCH repetition factor.

[0098] Aspect 10 is an apparatus as described in any of aspects 1-9, further comprising: an implicit indication of the PUCCH repetition factor based on the temporal resource allocation of the associated PDSCH.

[0099] Aspect 11 is an apparatus as described in any one of aspects 1-10, further comprising: a time-domain resource allocation table for time-domain resource allocation including additional interpretation of the time-domain resource allocation bit field.

[0100] Aspect 12 is an apparatus as described in any of aspects 1-11, further comprising: additional interpretation of the time-domain resource allocation bit field is configured via RRC signaling.

[0101] Aspect 13 is an apparatus as described in any of aspects 1-12, further comprising: additional interpretation of the time-domain resource allocation bit field being applied to both rollback and non-rollback DCI formats.

[0102] Aspect 14 is an apparatus as described in any of aspects 1-13, further comprising: an implicit indication of the PUCCH repetition factor based on an additional interpretation of the TPC command used for PUCCH.

[0103] Aspect 15 is an apparatus as described in any of aspects 1-14, further comprising: the implicit indication of the PUCCH repeat factor is based on an additional interpretation of the VRB-to-PRB mapping.

[0104] Aspect 16 is used to implement the wireless communication method of any of aspects 1 to 15.

[0105] Aspect 17 is a device for wireless communication, including components for implementing any one of aspects 1 to 15.

[0106] Aspect 18 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 15.

[0107] Aspect 19 is an apparatus for wireless communication at a UE, comprising at least one processor coupled to a memory and configured to: receive an allocation of downlink resources from a base station, the downlink resources including an indication of a PUCCH repetition factor within a DCI; and communicate with the base station based on the downlink resources.

[0108] Aspect 20 is the apparatus as described in aspect 19, further comprising: a transceiver coupled to the at least one processor.

[0109] Aspect 21 is an apparatus as described in either aspect 19 or 20, further comprising: a PDSCH associated with UE scheduling by the DCI.

[0110] Aspect 22 is an apparatus as described in any of aspects 19-21, further comprising: the indication of the PUCCH repeat factor includes a dynamic indication or an implicit indication of the PUCCH repeat factor.

[0111] Aspect 23 is an apparatus as described in any of aspects 19-22, further comprising: a dynamic indication of the PUCCH repetition factor is indicated in a separate bit field within the DCI, wherein the DCI includes a non-back-off DCI.

[0112] Aspect 24 is an apparatus as described in any of aspects 19-23, further comprising: a dynamic indication of the PUCCH repetition factor corresponding to a PUCCH carrying an ACK or NACK for the corresponding scheduled PDSCH.

[0113] Aspect 25 is an apparatus as described in any of aspects 19-24, further comprising: a dynamic indication of the PUCCH repetition factor corresponding to all PUCCHs carrying an ACK or NACK for any future scheduled PDSCH.

[0114] Aspect 26 is an apparatus as described in any of aspects 19-25, further comprising: a dynamic indication of the PUCCH repetition factor being valid for future scheduled PDSCHs until overwritten or canceled by a second dynamic indication of the second PUCCH repetition factor.

[0115] Aspect 27 is an apparatus as described in any of aspects 19-26, further comprising: a dynamic indication of a PUCCH repetition factor corresponding to another PUCCH until overwritten or canceled by another dynamic indication of a PUCCH repetition factor.

[0116] Aspect 28 is an apparatus as described in any of aspects 19-27, further comprising: an implicit indication of the PUCCH repetition factor based on the temporal resource allocation of the associated PDSCH.

[0117] Aspect 29 is an apparatus as described in any of aspects 19-28, further comprising: a time-domain resource allocation table for time-domain resource allocation including additional interpretation of the time-domain resource allocation bit field.

[0118] Aspect 30 is an apparatus as described in any of aspects 19-29, further comprising: additional interpretation of the time-domain resource allocation bit field being configured via RRC signaling or being applied to rollback and non-rollback DCI formats.

[0119] Aspect 31 is an apparatus as described in any of aspects 19-30, further comprising: an implicit indication of the PUCCH repetition factor based on an additional interpretation of the TPC command or VRB-to-PRB mapping used for the PUCCH.

[0120] Aspect 32 is a method for implementing wireless communication in any of aspects 19-31.

[0121] Aspect 33 is a device for wireless communication, including components for implementing any of aspects 19-31.

[0122] Aspect 34 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the processor causes the processor to implement any one of aspects 19-31.

Claims

1. An apparatus for wireless communication at a base station, comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the device to: A downlink resource is allocated to at least one user equipment (UE), the downlink resource being associated with an indication of a physical uplink control channel (PUCCH) repetition factor within a first downlink control indicator (DCI), wherein the PUCCH repetition factor is applied to all subsequent PUCCHs until overridden or canceled by a second indication of a different PUCCH repetition factor within a second DCI, the subsequent PUCCHs including at least one PUCCH including an ACK or NACK for any scheduled physical downlink shared channel (PDSCH); and The first DCI is sent to the at least one UE.

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

3. The apparatus of claim 1, wherein, The first DCI is the Physical Downlink Shared Channel (PDSCH) associated with the UE scheduling.

4. The apparatus of claim 1, wherein, The indication of the PUCCH repeat factor includes a dynamic indication or an implicit indication of the PUCCH repeat factor.

5. The apparatus of claim 4, wherein, The dynamic indication of the PUCCH repetition factor is indicated in a separate bit field within the first DCI, wherein the first DCI includes a non-backoff DCI.

6. The apparatus of claim 4, wherein, The indication of the PUCCH repetition factor includes the dynamic indication of the PUCCH repetition factor, and the subsequent PUCCH includes a PUCCH carrying a first acknowledgment (ACK) or a first non-acknowledgment (NACK) for the PDSCH scheduled by the first DCI.

7. The apparatus of claim 4, wherein, The scheduled PDSCH includes one or more future PDSCHs scheduled by the rollback DCI.

8. The apparatus of claim 7, wherein, The indication of the PUCCH repetition factor is valid for future scheduled PDSCHs until it is overwritten or canceled by the second indication.

9. The apparatus of claim 4, wherein, The subsequent PUCCH includes at least one PUCCH that does not include an ACK or NACK for the scheduled PDSCH.

10. The apparatus of claim 4, wherein, The indication of the PUCCH repetition factor includes the implicit indication of the PUCCH repetition factor, and the implicit indication of the PUCCH repetition factor is based on the time-domain resource allocation of the associated Physical Downlink Shared Channel (PDSCH).

11. The apparatus of claim 10, wherein, The time-domain resource allocation table includes additional explanations of the time-domain resource allocation bit fields.

12. The apparatus of claim 11, wherein, The additional interpretation of the time-domain resource allocation bit field is configured via Radio Resource Control (RRC) signaling.

13. The apparatus of claim 11, wherein, The additional interpretation of the time-domain resource allocation bit field is applied to both rollback and non-rollback DCI formats.

14. The apparatus of claim 4, wherein, The indication of the PUCCH repetition factor includes the implicit indication of the PUCCH repetition factor, and the implicit indication of the PUCCH repetition factor is based on an additional interpretation of the transmit power control (TPC) command for the PUCCH.

15. The apparatus of claim 4, wherein, The indication of the PUCCH repetition factor includes the implicit indication of the PUCCH repetition factor and the implicit indication of the PUCCH repetition factor is based on an additional interpretation of the virtual resource block (VRB) to physical resource block (PRB) mapping.

16. A method for conducting wireless communication at a base station, comprising: Downlink resources are allocated to at least one User Equipment (UE), the downlink resources being associated with an indication of a Physical Uplink Control Channel (PUCCH) repetition factor within a first Downlink Control Indicator (DCI), wherein the PUCCH repetition factor applies to all subsequent PUCCHs until overridden or canceled by a second indication of a different PUCCH repetition factor within a second DCI, the subsequent PUCCHs including at least one PUCCH comprising an ACK or NACK for any scheduled Physical Downlink Shared Channel (PDSCH); and The first DCI is sent to the at least one UE.

17. An apparatus for performing wireless communication at a user equipment (UE), comprising: At least one memory containing instructions; as well as At least one processor is configured to execute the instructions to cause the device to: The allocation of downlink resources is received from the base station, the downlink resources being associated with an indication of a physical uplink control channel (PUCCH) repetition factor within a first downlink control indicator (DCI), wherein the PUCCH repetition factor is applied to all subsequent PUCCHs until overridden or canceled by a second indication of a different PUCCH repetition factor within a second DCI, the subsequent PUCCHs including at least one PUCCH including an ACK or NACK for any scheduled physical downlink shared channel (PDSCH); and Based on the allocation of downlink resources, communication is conducted with the base station.

18. The apparatus of claim 17, further comprising a transceiver coupled to the at least one processor.

19. The apparatus of claim 17, wherein, The first DCI is the Physical Downlink Shared Channel (PDSCH) associated with the UE scheduling.

20. The apparatus of claim 17, wherein, The indication of the PUCCH repeat factor includes a dynamic indication or an implicit indication of the PUCCH repeat factor.

21. The apparatus of claim 20, wherein, The dynamic indication of the PUCCH repetition factor is indicated in a separate bit field within the first DCI, wherein the first DCI includes a non-backoff DCI.

22. The apparatus of claim 20, wherein, The indication of the PUCCH repetition factor includes the dynamic indication of the PUCCH repetition factor, and the subsequent PUCCH includes a PUCCH carrying a first acknowledgment (ACK) or a first non-acknowledgment (NACK) for the PDSCH scheduled by the first DCI.

23. The apparatus of claim 20, wherein, The scheduled PDSCH includes one or more future PDSCHs scheduled by the rollback DCI.

24. The apparatus of claim 23, wherein, The indication of the PUCCH repetition factor is valid for future scheduled PDSCHs until it is overwritten or canceled by the second indication.

25. The apparatus of claim 20, wherein, The subsequent PUCCH includes at least one PUCCH that does not include an ACK or NACK for the scheduled PDSCH.

26. The apparatus of claim 20, wherein, The indication of the PUCCH repetition factor includes the implicit indication of the PUCCH repetition factor, and the implicit indication of the PUCCH repetition factor is based on the time-domain resource allocation of the associated Physical Downlink Shared Channel (PDSCH).

27. The apparatus of claim 26, wherein, The time-domain resource allocation table includes additional explanations of the time-domain resource allocation bit fields.

28. The apparatus of claim 27, wherein, The additional interpretation of the time-domain resource allocation bit field is configured via Radio Resource Control (RRC) signaling or applied to both rollback and non-rollback DCI formats.

29. The apparatus of claim 20, wherein, The indication of the PUCCH repetition factor includes the implicit indication of the PUCCH repetition factor and the implicit indication of the PUCCH repetition factor is based on an additional interpretation of the transmit power control (TPC) command or the virtual resource block (VRB) to physical resource block (PRB) mapping for the PUCCH.

30. A method for performing wireless communication at a user equipment (UE), comprising: The allocation of downlink resources is received from the base station, the downlink resources being associated with an indication of a Physical Uplink Control Channel (PUCCH) repetition factor within a first downlink control indicator (DCI), wherein the PUCCH repetition factor applies to all subsequent PUCCHs until overridden or canceled by a second indication of a different PUCCH repetition factor within a second DCI, the subsequent PUCCHs including at least one PUCCH comprising an ACK or NACK for any scheduled Physical Downlink Shared Channel (PDSCH); and Based on the allocation of downlink resources, communication is conducted with the base station.

31. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a device to cause the processor to perform the method as described in any one of claims 16 and 30.

32. An apparatus for performing wireless communication at a base station, the apparatus comprising components for performing the method of claim 16.

33. An apparatus for performing wireless communication at a user equipment (UE), the apparatus comprising components for performing the method of claim 30.

Images