HARQ timing for multi-pdsch grant

Abstract

In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may receive from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple Physical Downlink Shared Channel (PDSCH) resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value may be associated with at least one Physical Uplink Control Channel (PUCCH) resource and indicate the PDSCH to Hybrid Automatic Repeat Request (HARQ) timing. The apparatus may send to the base station via at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 127,870, filed on December 18, 2020, entitled “HARQ TIMING FOR MULTI-PDSCH GRANT,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] In summary, this disclosure relates to communication systems, and more specifically, to Hybrid Automatic Repeat Request (HARQ) management under multiple PDSCH permissible conditions. Background Technology

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

[0005] These multiple access technologies have been adopted in various 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 released by the 3rd 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 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. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to depict 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] A single downlink control information (DCI) message that schedules multiple Physical Downlink Shared Channel (PDSCH) transmissions can help reduce control overhead. The timing of acknowledgment / negative acknowledgment (ACK / NACK) indications for correctly handling multiple PDSCH transmissions scheduled within the same DCI message is desirable.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a user equipment (UE). The apparatus may receive from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value may be associated with at least one Physical Uplink Control Channel (PUCCH) resource and indicate PDSCH to HARQ timing. The apparatus may send to the base station via at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions.

[0009] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a base station. The apparatus may send an indication to a UE via a DCI message for at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value may be associated with at least one PUCCH resource and indicate PDSCH to HARQ timing. The apparatus may receive from the UE via at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions.

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

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

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

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

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

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

[0016] Figure 3 This is a diagram illustrating an example of a base station and a UE in an access network.

[0017] Figure 4 This is a communication flow example of a wireless communication method.

[0018] Figure 5 This is a block diagram illustrating the PDSCH to HARQ timing delay based on some aspects.

[0019] Figure 6 This is a block diagram illustrating the PDSCH to HARQ timing delay based on some aspects.

[0020] Figure 7 This is a block diagram illustrating the PDSCH to HARQ timing delay based on some aspects.

[0021] Figure 8 This is a block diagram illustrating the PDSCH to HARQ timing delay based on some aspects.

[0022] Figure 9 It is a diagram of a table that includes the RRC configuration entries related to K1.

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

[0024] Figure 11 This is a flowchart of a wireless communication method.

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

[0026] Figure 13 This is a diagram illustrating an example of the hardware implementation used for the example device. Detailed Implementation

[0027] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing only the configurations 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 the form of block diagrams in order to avoid obscuring such concepts.

[0028] 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 illustrated in the accompanying drawings by way of various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0029] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, 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 a 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 files, threads of execution, procedures, functions, etc.

[0030] 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. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible by 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 media of the types described above, or any other medium that can be used to store computer-executable code accessible by a computer in the form of instructions or data structures.

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

[0032] 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: 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), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate directly or indirectly with each other (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.

[0033] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. 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 that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which 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 referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to 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. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for up to a total of Yx MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation 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).

[0034] 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 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.

[0035] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an 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.

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

[0037] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the extremely 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 documents and articles.

[0038] In light of the foregoing, unless otherwise specifically stated, it should be understood that the terms "below 6 GHz" and the like (if used herein) can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0039] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (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 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.

[0040] 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 for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0041] 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 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 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for MBMS transmissions to content providers, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to areas of a Multicast-Broadcast Single Frequency Network (MBSFN) that broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0042] 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 processes signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS streaming 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.

[0043] 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 Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, 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 similarly functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0044] Refer again Figure 1In some aspects, UE 104 may include a multi-PDSCH permission management component 198. The multi-PDSCH permission management component 198 may be configured to receive from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value may be associated with at least one PUCCH resource and indicate PDSCH to HARQ timing. The multi-PDSCH permission management component 198 may also be configured to send to the base station via at least one PUCCH resource at least one ACK / NACK indication associated with at least one K1 value and corresponding to the multiple PDSCH transmissions. In some aspects, base station 180 may include a multi-PDSCH permission management component 199. The multi-PDSCH permission management component 199 may be configured to send from the UE via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. At least one K1 value can be associated with at least one PUCCH resource and indicate the PDSCH-to-HARQ timing. The multi-PDSCH permission management component 199 can also be configured to receive from the UE via at least one PUCCH resource at least one ACK / NACK indication associated with at least one K1 value and corresponding to multiple PDSCH transmissions. Although the following description may focus on 5G NR, the concepts described herein are applicable to other similar domains such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0045] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 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 Frequency Division Duplex (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL), or Time Division Duplex (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL). In the process of... Figure 2A , Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are 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 of which are 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 with 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 the 5G NR frame structure as TDD.

[0046] Other wireless communication technologies may have different frame structures 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 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) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum 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 can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2DExamples are provided for slot configuration 0 (14 symbols per slot) and digital scheme μ=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 a frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing can exist (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme.

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

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

[0049] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of an 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 a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring on a CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can span the channel bandwidth at larger and / or lower frequencies. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier 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 PDSCH carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0050] like Figure 2C As shown, some REs in the 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 PUCCH and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols before 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.

[0051] Figure 2DExamples of various UL channels within a subframe of a frame are shown. 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 HARQ acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK) feedback. The PUSCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0052] Figure 3 This is a block diagram illustrating 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 functions. Layer 3 includes the 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 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: transmission of upper-layer packet data units (PDUs), 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 functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0053] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) encoding / 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), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided 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 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 transmitted by UE 350 and / or channel condition feedback. 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 an RF carrier for transmission.

[0054] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the 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 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 a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved 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.

[0055] 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 transport 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.

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

[0057] 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 appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0058] UL transmission at base station 310 is handled in a manner similar to that described for the receiver functions integrated 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 the information to the RX processor 370.

[0059] 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 transport channel and the logical channel 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.

[0060] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The 198 was used to implement various aspects.

[0061] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 The 199 was used to implement various aspects.

[0062] In some aspects of wireless communication, the multiple PUSCH (multi-PUSCH) grant feature can help reduce control overhead. Multiple consecutive PUSCH transmissions can be scheduled within a single multi-PUSCH uplink grant. For multiple PUSCH resources scheduled within a multi-PUSCH grant, the same Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), Modulation and Coding Scheme (MCS), rank, and some other transmission parameters can be shared. The TDRA can be used to provide the start and end positions of a transmission, with multiple start and length indicator values ​​(SLIVs) included in the TDRA entry. A multi-PUSCH uplink grant can indicate the first HARQ process identifier (ID), and subsequent transmissions can use incremental HARQ process IDs. A separate New Data Indicator (NDI) and a separate Redundancy Version Identifier (RVID) (which can be compressed) can be associated with each of the multiple scheduled PUSCH resources. These features help strike a balance between scheduling flexibility and DCI message length.

[0063] In some respects, the multiple PDSCH (multiple PDSCH) permission feature can help reduce control overhead. It should be understood that for mmW channels, time slots can be shorter, especially when using higher subcarrier spacing (SCS) parameters.

[0064] In one aspect, common MCS, rank, precoding matrix, FDRA, and TDRA can be used to schedule multiple PDSCH transmissions in a multi-PDSCH grant. Multi-PDSCH grants can help schedule longer downlink bursts. Many design goals between multi-PDSCH grants and multi-PUSCH grants may be the same. Therefore, many design styles can be directly utilized. However, some downlink-specific issues may also exist, which may need to be considered separately. A multi-PDSCH downlink grant can indicate the first HARQ process ID, and subsequent transmissions can use incremental HARQ process IDs. Individual NDIs and individual RVIDs (which can be compressed) can be associated with each of the multiple scheduled PDSCH transmissions.

[0065] In one aspect, SLIV can be selected to provide sufficiently long gaps between consecutive PDSCH transmissions that utilize multi-PDSCH permitted scheduling. The gaps may have several functions. For example, a gap can allow uplink feedback in the middle of multiple PDSCH transmissions for the served UE and other UEs. As another example, a gap can allow downlink monitoring of the served UE and downlink control transmissions to the served UE and other UEs.

[0066] It may be expected that the timing of ACK / NACK indications for transmissions using multiple PDSCH transmissions scheduled with multi-PDSCH permission should be handled correctly. It may also be expected that the PUCCH resource indicator (PRI) and downlink assignment index (DAI) with multi-PDSCH permission should be handled correctly.

[0067] Figure 4This is a communication flow 400 of an example method for wireless communication. At 406, UE 402 can receive RRC signaling from base station (BS) 404, and BS 404 can send RRC signaling to UE 402. At 408, UE 402 can receive a DCI message (e.g., multiple PDSCH permission) from BS 404, and BS 404 can send a DCI message to UE 402 that schedules multiple PDSCH transmissions on multiple PDSCH resources for downlink transmission and includes at least one K1 value associated with the multiple PDSCH transmissions. The K1 value may be a PDSCH-to-HARQ timing indicator and may indicate the timing delay (in terms of the number of slots) between the last PDSCH resource in a PDSCH resource or PDSCH resource group and the associated PUCCH resource carrying an ACK / NACK indicator for the PDSCH resource or PDSCH resource group. At 410a, BS 404 can send a PDSCH transmission to UE 402, and UE 402 can receive a PDSCH transmission from BS 404. This PDSCH transmission can be one of multiple scheduled PDSCH transmissions. At 412a, UE 402 can send an ACK / NACK indication to BS 404 in a PUCCH resource, and BS 404 can receive an ACK / NACK indication from UE 402 in a PUCCH resource. This ACK / NACK indication corresponds to the PDSCH transmission at 410a. The timing delay between the PDSCH transmission at 410a and the transmission of the PUCCH resource carrying the corresponding ACK / NACK indication at 412a can be indicated by the associated K1 value.

[0068] Similarly, at 410b, BS 404 can send another PDSCH transmission to UE 402, and UE 402 can receive another PDSCH transmission from BS 404, which may be one of a plurality of scheduled PDSCH transmissions. At 412b, UE 402 can send an ACK / NACK indication to BS 404 in a PUCCH resource, and BS 404 can receive an ACK / NACK indication from UE 402 in a PUCCH resource, corresponding to the PDSCH transmission at 410b. The timing delay between the PDSCH transmission at 410b and the transmission of the PUCCH resource carrying the corresponding ACK / NACK indication at 412b can be indicated by the associated K1 value. In different aspects, the K1 value may be the same or may be different, as will be apparent from the following description. It should be understood that... Figure 4The exact positions of the PUCCHs carrying ACK / NACK indicators (e.g., 412a, 412b, ..., etc.) are illustrative and do not limit the scope of this disclosure. For example, in aspects not shown here, 412a may occur after 410b, and 412b may occur before 410b, etc. Optionally, additional PDSCH transmissions / receives and the transmission / receive of ACK / NACK indicators on the PUCCH (e.g., 410c, 412c, etc.) may occur based on multiple PDSCH permissions.

[0069] Figure 5 This is a block diagram 500 illustrating the PDSCH to HARQ timing delay based on some aspects. For example... Figure 5 As shown, DCI messages (e.g., in) Figure 4 The DCI message sent at position 408 in the PUCCH resource 504 can schedule several PDSCH transmissions (e.g., six (6) PDSCH transmissions on six PDSCH resources (502a-f)) for downlink transmission. The DCI message can also include an indication of a single K1 value for all scheduled PDSCH resources. Therefore, for all PDSCH transmissions in a single PUCCH resource 504 (e.g., PDSCH transmissions on PDSCH resources 502a-f), transmissions can be sent from the UE to the BS (e.g., Figure 4 UE 402 sends one or more ACK / NACK indications to BS 404. In one aspect, an ACK / NACK indication can be sent for each PDSCH transmission. In another aspect, a single group ACK / NACK indication can be sent for all associated PDSCH transmissions. The K1 value can indicate the timing delay (in slots) between the last PDSCH resource (i.e., PDSCH resource 502f) and PUCCH resource 504 among all scheduled PDSCH resources. Using a single K1 value and a single PUCCH resource to carry ACK / NACK indications for all PDSCH resources scheduled in a multi-PDSCH grant can represent a simple solution with low control overhead. It is similar to the solution used with multi-PUSCH grants, where a single K2 value is provided to indicate the timing offset from multi-PUSCH grant to the first PUSCH transmission. However, using a single K1 value and a single PUCCH resource can be associated with long feedback delays, especially for earlier PDSCH transmissions scheduled in a multi-PDSCH grant.

[0070] Figure 6 This is a block diagram 600 illustrating the PDSCH to HARQ timing delay based on some aspects. For example... Figure 6 As shown in each example in the examples, DCI messages (e.g., multiple PDSCH permission) (e.g., in...) Figure 4The DCI message sent at position 408 in the DCI message can schedule several PDSCH transmissions, for example, three (3) PDSCH transmissions on three PDSCH resources (602a-c and 602d-f, respectively). The DCI message can also include an indication of a single K1 value, which can be applied individually to each of the multiple scheduled PDSCH transmissions. Therefore, a PUCCH resource is provided to carry a corresponding ACK / NACK indication for each of the multiple PDSCH transmissions. For example, PUCCH resource 604a is provided for PDSCH transmissions on PDSCH resource 602a, PUCCH resource 604b is provided for PDSCH transmissions on PDSCH resource 602b, PUCCH resources 604c-f are provided for PDSCH transmissions on PDSCH resources 602c-f, and so on. A single K1 value can indicate the timing delay (in slots) between each PDSCH resource in the scheduled PDSCH resources and the corresponding PUCCH resource (e.g., between PDSCH resource 602a and PUCCH resource 604a). In one example shown, a single K1 value can indicate a timing delay of one (1) slot. Therefore, the transmission and reception of the PUCCH resource can occur one slot after the corresponding PDSCH resource. For example, PUCCH resource 604a may lag behind PDSCH resource 602a by one slot. In another example shown, a single K1 value can indicate a timing delay of 0 slots, which can indicate that the PUCCH resource can be in the same slot as the corresponding PDSCH resource. For example, PUCCH resource 604d and the corresponding PDSCH resource 602d can be in the same slot. BS (e.g., Figure 4 BS 404 in the context of multiple PDSCH permission can provide appropriate gaps between consecutive PDSCH transmissions scheduled in a multi-PDSCH permission to allow UEs (e.g., Figure 4 The UE 402 sends an ACK / NACK indication.

[0071] Figure 7 This is a block diagram 700 illustrating the PDSCH to HARQ timing delay based on some aspects. For example... Figure 7As shown in the two examples, a DCI message (e.g., a multi-PDSCH permission) (e.g., a DCI message sent at 408) can be scheduled as three (3) PDSCH transmissions on three PDSCH resources (702a-c) and four (4) PDSCH transmissions on four PDSCH resources (702d-g), respectively. Multiple scheduled PDSCH transmissions can be organized into one or more groups based on a PDSCH transmission group size parameter (e.g., “NumOfPdschPerK1”), which specifies the number of consecutive PDSCH transmissions in each group. In the two examples shown, the “NumOfPdschPerK1” parameter specifies that each PDSCH transmission group includes three (3) consecutive PDSCH transmissions. Therefore, in one example, PDSCH transmissions on PDSCH resources 702a-c can form a group. In another example, PDSCH transmissions on PDSCH resource 702d-f can form one group, and PDSCH transmissions on PDSCH resource 702g can form a separate group. It should be understood that in some scenarios, a PDSCH group within a PDSCH group (e.g., the last PDSCH group) may contain fewer PDSCH transmissions per group than specified by the "NumOfPdschPerK1" parameter, because the total number of PDSCH transmissions scheduled in a multi-PDSCH permission may not be divisible by the number of PDSCH transmissions per group specified by the "NumOfPdschPerK1" parameter. The DCI message may also include an indication of one or more K1 values. Each PDSCH group can be associated with a K1 value. For example, a PDSCH group including PDSCH transmissions on PDSCH resource 702d-f can be associated with a K1 value, a PDSCH group including PDSCH transmissions on PDSCH resource 702g can be associated with a K1 value, and so on. The K1 value can indicate the timing delay (in slots) between the last PDSCH resource in an associated PDSCH resource group and the corresponding PUCCH resource in that PDSCH resource group (e.g., between PDSCH resource 702c and PUCCH resource 704a, between PDSCH resource 702f and PUCCH resource 704b, between PDSCH resource 702g and PUCCH resource 704c, etc.). Therefore, one or more PUCCH resources can be present to carry ACK / NACK indications. In one aspect, the same K1 value can be provided in the DCI message and used for each PDSCH group within the PDSCH group. In another aspect, different K1 values ​​(which can form a vector of K1 values) can be provided and used for different PDSCH groups; for example, each PDSCH group in multiple PDSCH groups can use a single K1 value from multiple K1 values.It should be understood that when the total number of PDSCH transmissions scheduled in a multi-PDSCH grant is less than the number of PDSCH transmissions per group specified by this parameter, all PDSCH transmissions can be collected in the same group, and one or more ACK / NACK indications can be sent and received for all PDSCH transmissions in a single PUCCH resource. Figure 7 Example 1 illustrates this scenario, which is similar to... Figure 5 The scenario is illustrated. In one aspect, an ACK / NACK indication can be sent for each PDSCH transmission. In another aspect, a single group ACK / NACK indication can be sent for all associated PDSCH transmissions.

[0072] Figure 8 This is a block diagram 800 illustrating the PDSCH to HARQ timing delay based on some aspects. For example... Figure 8 As shown, DCI messages (e.g., multiple PDSCH permission) (e.g., in...) Figure 4 The DCI message sent at position 408 in the example can be scheduled as three (3) PDSCH transmissions on three PDSCH resources (802a-c and 802d-f, respectively), as shown in each of the two examples illustrated. The DCI message can also include indications of multiple K1 values. Each PDSCH transmission can be associated with a corresponding K1 value. For example, in... Figure 8 In Example 1 shown, each PDSCH transmission in the PDSCH transmissions on PDSCH resources 802a-c is associated with one of the K1 values ​​K1_0, K1_1, and K1_2. The K1 value can indicate the timing delay (in units of time slots) between the PDSCH resource and the corresponding PUCCH resource (e.g., between PDSCH resources 802a-c and PUCCH resources 804a-c, between PDSCH resources 802d and PUCCH resources 804d, between PDSCH resources 802e and PUCCH resources 804d, between PDSCH resources 802f and PUCCH resources 804e, etc.). Therefore, one or more PUCCH resources can be provided to carry ACK / NACK indications. In one aspect, a vector of K1 values, including multiple K1 values ​​for multiple PDSCH transmissions, can be pre-configured with RRC signaling (e.g., ...). Figure 4 RRC signaling 406 in the RRC configuration entry (e.g., "multi-pdsch-DataToUL-ACK" entry). DCI message (e.g., in Figure 4The DCI message sent at position 408 in the DCI message (e.g., in the DCI message) can include a K1 value index pointing to a pre-configured RRC configuration entry. This approach can be associated with flexibility and a good trade-off between overhead and latency. Alternatively, a vector of K1 values ​​including multiple K1 values ​​can be used in the DCI message (e.g., in the DCI message). Figure 4 The DCI message sent at position 408 in the document explicitly indicates this. In this respect, the DCI message may include multiple K1 value fields to accommodate multiple K1 values, for example, one K1 value per PDSCH. However, this approach may result in the DCI message having a variable length. BS (e.g., Figure 4 BS 404 in the context of multiple PDSCH permission can provide appropriate gaps between consecutive PDSCH transmissions scheduled in a multi-PDSCH permission to allow UEs (e.g., Figure 4 The UE (402) sends an ACK / NACK indication. It should be understood that... Figure 8 The aspects shown can be considered as Figure 7 Special cases of some of the aspects shown, where the number of PDSCH transmissions per group is specified as a certain number, such as one (1).

[0073] In one aspect, BS (e.g., Figure 4 BS 404 in the document can specify the maximum allowed number of PUCCH resources (e.g., “MaxNumofPucch”) for ACK / NACK indications of multiple PDSCH transmissions scheduled in a multi-PDSCH permission. The maximum allowed number of feedback PUCCH resources can be indicated via RRC signaling (e.g., RRC signaling 406). In one aspect, BS (e.g., Figure 4BS 404 in the DCI message can determine the total number of PDSCH transmissions scheduled in a multi-PDSCH allowance based on the maximum allowed number of PUCCH resources. In other words, the DCI used for multi-PDSCH allowance can be adjusted based on the maximum allowed number of PUCCH resources. Therefore, in one aspect, when receiving and / or decoding a DCI message that includes multi-PDSCH allowance (e.g., the DCI message at 408), the UE (e.g., UE 402) can determine the number of PDSCH groups (i.e., the corresponding number of PUCCH resources) (e.g., “NumofPucchgroup”) for the PDSCH transmissions scheduled in a multi-PDSCH allowance. In one aspect, if a single K1 value is indicated in the DCI message, the UE (e.g., UE 402) can determine NumofPucchgroup as either MaxNumofPucch or the number of PDSCH transmissions scheduled in a multi-PDSCH allowance, whichever is smaller. In one aspect, the BS (e.g., BS404) may include a dynamically specified number of PDSCH groups (e.g., “NumofPucchgroup”) in a DCI message (e.g., a DCI message sent at 408), which may be less than or equal to the maximum allowed number of PUCCH resources (e.g., “MaxNumofPucch”), and the UE (e.g., UE 402) may use the dynamically specified number of PDSCH groups when organizing PDSCH transmissions into groups.

[0074] It should be understood that, except for the last PUCCH resource, the number of PDSCH transmissions corresponding to each PUCCH resource (i.e., the PDSCH group size) can be calculated as floor(number of PDSCH transmissions scheduled in a multi-PDSCH grant / NumofPucchgroup) (where floor(x) is a rounding function that gives the largest integer less than or equal to x as the output), and the number of PDSCH transmissions corresponding to the last PUCCH resource can be calculated as (number of PDSCH transmissions scheduled in a multi-PDSCH grant) - (NumofPucchgroup-1) * floor(number of PDSCH transmissions scheduled in a multi-PDSCH grant / NumofPucchgroup). In one aspect, the DCI message may also include indications of multiple K1 values. Each PDSCH transmission may be associated with a corresponding K1 value. In other words, the length of the vector of K1 values ​​may be equal to the number of PDSCH transmissions scheduled in a multi-PDSCH grant. The K1 value may indicate the timing delay (in units of time slots) between the associated PDSCH resource and the corresponding PUCCH resource. A BS (e.g., BS 404) can ensure that the implied number of PUCCH resources, as indicated in a DCI message (e.g., a DCI message sent at 408), does not exceed the maximum allowed number of PUCCH resources.

[0075] Figure 9 Figure 900 shows a table that includes RRC configuration entries related to K1. Figure 9 The table shown may include the above information about Figure 8 The described "multi-pdsch-DataToUL-ACK" entry can be pre-configured with RRC signaling at 406. Each entry includes a PDSCH group size (e.g., "NumOfPdschPerK1") and one or more K1 values ​​(more than one K1 value within an entry can form a vector of K1 values). Therefore, a DCI message (e.g., a DCI message sent at 408) can include a K1 value index pointing to one of the pre-configured RRC configuration entries. If an entry contains a vector of K1 values ​​(including multiple K1 values), each K1 value in the vector can correspond to a PDSCH transport group (it should be understood that, in some respects, the group size can be 1). The last PDSCH transport in a PDSCH transport group can be used as a reference for counting the PDSCH-to-HARQ timing delay.

[0076] The PDSCH group size can be specified in different ways depending on the aspect (e.g., the "NumOfPdschPerK1" parameter). In one aspect, the DCI message (e.g., in...) Figure 4The DCI message sent at position 408 in the DCI message may include a PDSCH group size index pointing to one of the at least one pre-configured RRC configuration entries (e.g., the "multi-pdsch-DataToUL-ACK" entry described above), from which the PDSCH group size can be obtained. Alternatively, the DCI message (e.g., in...) may include... Figure 4 The PDSCH group size is explicitly indicated in the DCI message sent at position 408. Alternatively, the PDSCH group size can be pre-configured via RRC signaling (e.g., RRC signaling 406).

[0077] In one approach, all PUCCH resources can be associated with the same PRI. This may have the benefit of lower overhead, but flexibility may be limited. In another approach, individual PRIs can be associated with each PUCCH resource. In one approach, PRIs can be included in the DCI message. However, this may be associated with high overhead. In another approach, a table containing vectors of PRIs can be pre-configured, each vector including multiple PRIs, and an index pointing to an entry in the pre-configured table can be included in the DCI message.

[0078] Figure 10 This is a flowchart 1000 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 402, device 1202). At 1002, the UE can receive from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value can be associated with at least one PUCCH resource and indicate the PDSCH-to-HARQ timing. For example, 1002 can be performed by... Figure 12 The downlink control component 1240 is executed via the receiving component 1230 and the transmitting component 1234.

[0079] At point 1004, the UE can send at least one ACK / NACK indication to the base station via at least one PUCCH resource, which is associated with at least one K1 value and corresponds to multiple PDSCH transmissions. For example, point 1004 can be... Figure 12 The confirmation component 1242 in the middle is used to execute.

[0080] In one aspect, at least one K1 value may indicate a timing delay, in timeslots, between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource.

[0081] In one aspect, returning to the reference Figure 6 At least one K1 value may include a single K1 value applicable to each PDSCH transmission in multiple PDSCH transmissions. At least one PUCCH resource may include multiple PUCCH resources. Each PDSCH transmission in multiple PDSCH transmissions may correspond to one of the multiple PUCCH resources. At least one ACK / NACK indication may include multiple ACK / NACK indications. The UE may also send multiple ACK / NACK indications to the base station via multiple PUCCH resources. Each PDSCH transmission in multiple PDSCH transmissions may be associated with one of the multiple ACK / NACK indications. Each PUCCH resource in multiple PUCCH resources may carry one of the multiple ACK / NACK indications.

[0082] In one aspect, returning to the reference Figure 7 Multiple PDSCH transmissions can be organized into at least one PDSCH transmission group. At least one K1 value may include a single K1 value applicable to each PDSCH transmission group within the at least one PDSCH transmission group. Each group within the at least one PDSCH transmission group may be associated via a single K1 value with one or more ACK / NACK indications from at least one PUCCH resource and at least one ACK / NACK indication carried in an associated PUCCH resource. In one aspect, each PDSCH transmission group within the at least one PDSCH transmission group, or all PDSCH transmission groups other than one PDSCH transmission group within the at least one PDSCH transmission group, may include an equal number of consecutive PDSCH transmissions.

[0083] In one aspect, multiple PDSCH transmissions can be organized into multiple PDSCH transmission groups. At least one K1 value may include multiple K1 values. Each of the multiple K1 values ​​may be applicable to a corresponding PDSCH transmission group within the multiple PDSCH transmission groups. Each group within the multiple PDSCH transmission groups may be associated with one of at least one PUCCH resources via a corresponding K1 value. At least one ACK / NACK indication may include multiple ACK / NACK indications. The UE may also send multiple ACK / NACK indications to the base station via at least one PUCCH resource. Each group within the multiple PDSCH transmission groups may be associated with one or more ACK / NACK indications among the multiple ACK / NACK indications. In one aspect, each PDSCH transmission group within the multiple PDSCH transmission groups, or all PDSCH transmission groups except for one of the multiple PDSCH transmission groups, may include an equal number of consecutive PDSCH transmissions.

[0084] In one aspect, the UE may also receive from the base station via RRC signaling a first limit (e.g., the "MaxNumofPucch" limit described above) regarding the number of at least one PUCCH resource. The UE may organize multiple PDSCH transmissions into multiple PDSCH transmission groups based on the first limit. The number of PDSCH transmission groups may be less than or equal to the first limit.

[0085] In one aspect, the UE may also receive a second constraint (e.g., the "NumPucchgroup" parameter described above) from the base station in the DCI message regarding the number of at least one PUCCH resource. The second constraint may be less than or equal to the first constraint. The UE may organize multiple PDSCH transmissions into multiple PDSCH transmission groups based on the second constraint. The number of groups in the multiple PDSCH transmission groups may be less than or equal to the second constraint.

[0086] In one aspect, returning to the reference Figure 8 At least one K1 value may include multiple K1 values. Each of the multiple K1 values ​​may be applicable to a corresponding PDSCH transmission among multiple PDSCH transmissions. Each PDSCH transmission among multiple PDSCH transmissions may be associated with one of the at least one PUCCH resources via the corresponding K1 value. At least one ACK / NACK indication may include multiple ACK / NACK indications. The UE may also send multiple ACK / NACK indications to the base station via at least one PUCCH resource. Each PDSCH transmission among multiple PDSCH transmissions may be associated with one of the multiple ACK / NACK indications.

[0087] In one aspect, an indication of at least one K1 value received via a DCI message may be associated with an RRC signaling entry that includes multiple K1 values. In another aspect, an indication of at least one K1 value received via a DCI message may include multiple K1 values ​​in the DCI message.

[0088] In one aspect, multiple PDSCH transmissions can be organized into at least one PDSCH transmission group, and each group in the at least one PDSCH transmission group can be associated with one of at least one K1 value. Each group in the at least one PDSCH transmission group can correspond to one or more ACK / NACK indicators in at least one PUCCH resource and at least one ACK / NACK indicator via the associated K1 value. The indication of at least one K1 value received via DCI message can be associated with a first table (e.g., received via RRC signaling) Figure 9 The first table may be associated with at least one entry that associates the PDSCH transport group size with at least one K1 value.

[0089] In one aspect, the DCI message may further include an indication of the size of a PDSCH transport group associated with multiple PDSCH transports. The indication of the PDSCH transport group size may correspond to an entry in at least one entry of a first table. In one aspect, the UE may receive the indication of the size of a PDSCH transport group associated with multiple PDSCH transports from the base station via RRC signaling.

[0090] Figure 11 This is a flowchart 1100 of a wireless communication method. This method can be performed by a base station (e.g., base station 102 / 180; base station 404; device 1302). At 1102, the base station can send an indication to the UE via a DCI message of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value can be associated with at least one PUCCH resource and indicate the PDSCH-to-HARQ timing. For example, 1102 can be performed by… Figure 13 The downlink control component 1340 is executed via the transmission component 1334.

[0091] At point 1104, the base station can receive from the UE at least one ACK / NACK indication associated with at least one K1 value and corresponding to multiple PDSCH transmissions via at least one PUCCH resource. For example, 1104 can be... Figure 13 The confirmation component 1342 is executed via the receiving component 1330.

[0092] In one aspect, at least one K1 value may indicate a timing delay, in timeslots, between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource.

[0093] In one aspect, returning to the reference Figure 6 At least one K1 value may include a single K1 value applicable to each PDSCH transmission in the multiple PDSCH transmissions. At least one PUCCH resource may include multiple PUCCH resources. Each PDSCH transmission in the multiple PDSCH transmissions may correspond to one of the multiple PUCCH resources. At least one ACK / NACK indication may include multiple ACK / NACK indications. The base station may also receive multiple ACK / NACK indications from the UE via multiple PUCCH resources. Each PDSCH transmission in the multiple PDSCH transmissions may be associated with one of the multiple ACK / NACK indications. Each PUCCH resource in the multiple PUCCH resources may carry one of the multiple ACK / NACK indications.

[0094] In one aspect, returning to the reference Figure 7 Multiple PDSCH transmissions can be organized into at least one PDSCH transmission group. At least one K1 value may include a single K1 value applicable to each PDSCH transmission group within the at least one PDSCH transmission group. Each group within the at least one PDSCH transmission group may be associated via a single K1 value with one or more ACK / NACK indications from at least one PUCCH resource and at least one ACK / NACK indication carried in an associated PUCCH resource. In one aspect, each PDSCH transmission group within the at least one PDSCH transmission group, or all PDSCH transmission groups other than one PDSCH transmission group within the at least one PDSCH transmission group, may include an equal number of consecutive PDSCH transmissions.

[0095] In one aspect, multiple PDSCH transmissions can be organized into multiple PDSCH transmission groups. At least one K1 value may include multiple K1 values. Each of the multiple K1 values ​​may be applicable to a corresponding PDSCH transmission group within the multiple PDSCH transmission groups. Each of the multiple PDSCH transmission groups may be associated with a PUCCH resource (at least one PUCCH resource) via a corresponding K1 value. At least one ACK / NACK indication may include multiple ACK / NACK indications. The base station may also receive multiple ACK / NACK indications from the UE via at least one PUCCH resource. Each of the multiple PDSCH transmission groups may be associated with one or more ACK / NACK indications among the multiple ACK / NACK indications. In one aspect, each PDSCH transmission group within the multiple PDSCH transmission groups, or all PDSCH transmission groups except for one of the multiple PDSCH transmission groups, may include an equal number of consecutive PDSCH transmissions.

[0096] In one aspect, the base station may also send a first limit (e.g., the "MaxNumofPucch" limit described above) to the UE via RRC signaling regarding the number of at least one PUCCH resource. The number of multiple PDSCH transmission groups may be less than or equal to the first limit.

[0097] In one aspect, the base station may also send a second limit (e.g., the "NumPucchgroup" parameter described above) to the UE in the DCI message regarding the number of at least one PUCCH resource. The second limit may be less than or equal to the first limit. The number of groups in multiple PDSCH transmission groups may be less than or equal to the second limit.

[0098] In one aspect, returning to the reference Figure 8 At least one K1 value may include multiple K1 values. Each of the multiple K1 values ​​may be applicable to a corresponding PDSCH transmission among the multiple PDSCH transmissions. Each PDSCH transmission among the multiple PDSCH transmissions may be associated with one of the at least one PUCCH resources via the corresponding K1 value. At least one ACK / NACK indication may include multiple ACK / NACK indications. The base station may also receive multiple ACK / NACK indications from the UE via at least one PUCCH resource. Each PDSCH transmission among the multiple PDSCH transmissions is associated with one of the multiple ACK / NACK indications.

[0099] In one aspect, an indication of at least one K1 value sent via a DCI message may be associated with an RRC signaling entry that includes multiple K1 values. In another aspect, an indication of at least one K1 value sent via a DCI message may include multiple K1 values ​​in the DCI message.

[0100] In one aspect, multiple PDSCH transmissions can be organized into at least one PDSCH transmission group, and each group in the at least one PDSCH transmission group can be associated with one of at least one K1 value. Each group in the at least one PDSCH transmission group can correspond to one or more ACK / NACK indicators in at least one PUCCH resource and at least one ACK / NACK indicator via the associated K1 value. The indication of at least one K1 value sent via DCI message can be associated with a first table (e.g., sent via RRC signaling) Figure 9 The first table may be associated with at least one entry that associates the PDSCH transport group size with at least one K1 value.

[0101] In one aspect, the DCI message may further include an indication of the size of a PDSCH transport group associated with multiple PDSCH transports. The indication of the PDSCH transport group size may correspond to an entry in at least one entry of a first table. In one aspect, the base station may send the indication of the size of a PDSCH transport group associated with multiple PDSCH transports to the UE via RRC signaling.

[0102] Figure 12Figure 1200 illustrates an example of a hardware implementation for device 1202. Device 1202 is a UE and includes: a cellular baseband processor 1204 (also referred to as a modem) coupled to a cellular RF transceiver 1222 and one or more Subscriber Identity Module (SIM) cards 1220; an application processor 1206 coupled to a Secure Digital (SD) card 1208 and a screen 1210; a Bluetooth module 1212; a Wireless Local Area Network (WLAN) module 1214; a Global Positioning System (GPS) module 1216; and a power supply 1218. The cellular baseband processor 1204 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1222. The cellular baseband processor 1204 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1204 is responsible for general processing, which includes executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1204, the software causes the cellular baseband processor 1204 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1204 during software execution. The cellular baseband processor 1204 also includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes one or more of the components shown. The components within the communication manager 1232 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1204. The cellular baseband processor 1204 can be a component of the UE 350 and can include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1202 can be a modem chip and only include the baseband processor 1204; in another configuration, the device 1202 can be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1202.

[0103] Communication manager 1232 includes downlink control component 1240, configured to receive from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message includes scheduling information for the multiple PDSCH transmissions, and the at least one K1 value is associated with at least one PUCCH resource and indicates PDSCH-to-HARQ timing, for example, as in combination with... Figure 10 As described in 1002. The communication manager 1232 also includes an acknowledgment component 1242 configured to send at least one ACK / NACK indication to the base station via at least one PUCCH resource, associated with at least one K1 value and corresponding to multiple PDSCH transmissions, for example, as in combination with... Figure 10 The 1004 in the text describes this.

[0104] The device may include the ability to perform the above-described actions. Figure 10 The flowchart shows the algorithm's additional components in each box. Therefore, Figure 10 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of these components. These components can 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.

[0105] In one configuration, apparatus 1202 (and specifically, cellular baseband processor 1204) includes: a unit for receiving from a base station via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources, the DCI message including scheduling information for the multiple PDSCH transmissions, the at least one K1 value being associated with at least one PUCCH resource and indicating PDSCH to HARQ timing; and a unit for sending to the base station via the at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions. The aforementioned unit may be one or more of the components of apparatus 1202 configured to perform the functions described therein. As described above, apparatus 1202 may include TX processor 368, RX processor 356, and controller / processor 359. Therefore, in one configuration, the aforementioned unit may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described therein.

[0106] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1302. Device 1302 is a BS and includes a baseband unit 1304. Baseband unit 1304 can communicate with UE 104 via cellular RF transceiver 1322. Baseband unit 1304 may include computer-readable medium / memory. Baseband unit 1304 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory. When executed by baseband unit 1304, the software causes baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1304 during software execution. Baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. Communication manager 1332 includes one or more of the components shown. Components within communication manager 1332 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1304. The baseband unit 1304 may be a component of the BS 310 and may include at least one of the TX processor 316, the RX processor 370 and the controller / processor 375 and / or the memory 376.

[0107] Communication manager 1332 includes downlink control component 1340, configured to send to the UE via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources. The DCI message includes scheduling information for the multiple PDSCH transmissions, and the at least one K1 value is associated with at least one PUCCH resource and indicates the PDSCH to HARQ timing, for example, as combined with... Figure 11 As described in 1102. The communication manager 1332 also includes an acknowledgment component 1342 configured to receive from the UE via at least one PUCCH resource at least one ACK / NACK indication associated with at least one K1 value and corresponding to multiple PDSCH transmissions, for example, as in combination with... Figure 11 As described in 1104.

[0108] The device may include functions that perform Figure 11 The additional components of each box in the algorithm's flowchart above. Therefore, Figure 11 Each block in the flowchart above can be executed by a component, and the apparatus can include one or more of these components. These components can 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.

[0109] In one configuration, apparatus 1302 (and specifically, baseband unit 1304) includes: a unit for sending to the UE via a DCI message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple PDSCH resources, the DCI message including scheduling information for the multiple PDSCH transmissions, the at least one K1 value being associated with at least one PUCCH resource and indicating PDSCH to HARQ timing; and a unit for receiving from the UE via at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions. The aforementioned unit may be one or more of the components of apparatus 1302 configured to perform the functions described therein. As described above, apparatus 1302 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, the aforementioned unit may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described therein.

[0110] To provide an indication of the timing delay of multiple PDSCH transmissions scheduled in a multi-PDSCH permission, an indication of at least one K1 value corresponding to the multiple PDSCH transmissions on multiple PDSCH resources can be sent from the base station to the UE via a DCI message. The DCI message may include scheduling information for the multiple PDSCH transmissions. The at least one K1 value may be associated with at least one PUCCH resource and indicate the PDSCH-to-HARQ timing. The device may send at least one ACK / NACK indication associated with at least one K1 value and corresponding to the multiple PDSCH transmissions to the base station via at least one PUCCH resource.

[0111] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of the various boxes in the example order, but are not intended to limit one to the specific order or hierarchy given.

[0112] The foregoing description is provided to enable any person skilled in the art to implement 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 are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, references to the singular element are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the same time as” should be interpreted as meaning “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The term “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 preferred over or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure that are known to or will be known later by one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “unit.” Therefore, no claim can be made that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

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

[0114] Aspect 1 is a method for wireless communication at a user equipment (UE), comprising: receiving from a base station via a downlink control information (DCI) message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple physical downlink shared channel (PDSCH) resources, the DCI message including scheduling information for the multiple PDSCH transmissions, the at least one K1 value being associated with at least one physical uplink control channel (PUCCH) resource and indicating PDSCH timing to Hybrid Automatic Repeat Request (HARQ); and transmitting to the base station via the at least one PUCCH resource at least one acknowledgment / negative acknowledgment (ACK / NACK) indication associated with the at least one K1 value and corresponding to the multiple PDSCH transmissions.

[0115] Aspect 2 is the method according to aspect 1, wherein the at least one K1 value indicates a timing delay, in timeslots, between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource.

[0116] Aspect 3 is the method according to any one of Aspects 1 and 2, wherein the at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transmissions, the at least one PUCCH resource includes a plurality of PUCCH resources, each of the plurality of PDSCH transmissions corresponds to one of the plurality of PUCCH resources, the at least one ACK / NACK indication includes a plurality of ACK / NACK indications, and the method further includes: sending the plurality of ACK / NACK indications to the base station via the plurality of PUCCH resources, wherein each of the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications, and each of the plurality of PUCCH resources carries one of the plurality of ACK / NACK indications.

[0117] Aspect 4 is the method according to any one of Aspects 1 and 2, wherein the plurality of PDSCH transmissions are organized into at least one PDSCH transmission group, the at least one K1 value includes a single K1 value applicable to each of the at least one PDSCH transmission groups, and each of the at least one PDSCH transmission groups is associated via the single K1 value with one or more ACK / NACK indications of the at least one ACK / NACK indication carried in an associated PUCCH resource and a PUCCH resource.

[0118] Aspect 5 is the method according to aspect 4, wherein each PDSCH transmission group in the at least one PDSCH transmission group or all PDSCH transmission groups other than one of the at least one PDSCH transmission groups comprises an equal number of consecutive PDSCH transmissions.

[0119] Aspect 6 is a method according to any one of Aspects 1 and 2, wherein the plurality of PDSCH transmissions are organized into a plurality of PDSCH transmission groups, the at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​is applicable to a corresponding PDSCH transmission group in the plurality of PDSCH transmission groups, each of the plurality of PDSCH transmission groups is associated with a PUCCH resource in the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication includes a plurality of ACK / NACK indications, and the method further includes: sending the plurality of ACK / NACK indications to the base station via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmission groups is associated with one or more ACK / NACK indications in the plurality of ACK / NACK indications.

[0120] Aspect 7 is the method according to aspect 6, wherein each of the plurality of PDSCH transmission groups or all PDSCH transmission groups other than one of the plurality of PDSCH transmission groups comprises an equal number of consecutive PDSCH transmissions.

[0121] Aspect 8 is the method according to aspect 6, further comprising: receiving from the base station via radio resource control (RRC) signaling a first limit on the number of the at least one PUCCH resource; and organizing the plurality of PDSCH transmissions into the plurality of PDSCH transmission groups based on the first limit, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the first limit.

[0122] Aspect 9 is the method according to aspect 8, further comprising: receiving from the base station in the DCI message a second limit on the number of the at least one PUCCH resource, the second limit being less than or equal to the first limit; and organizing the plurality of PDSCH transmissions into the plurality of PDSCH transmission groups based on the second limit, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the second limit.

[0123] Aspect 10 is a method according to any one of Aspects 1 and 2, wherein the at least one K1 value comprises a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission among the plurality of PDSCH transmissions, each of the plurality of PDSCH transmissions being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication comprising a plurality of ACK / NACK indications, and the method further comprising: sending the plurality of ACK / NACK indications to the base station via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmissions is associated with an ACK / NACK indication among the plurality of ACK / NACK indications.

[0124] Aspect 11 is the method according to aspect 10, wherein the indication of the at least one K1 value received via the DCI message is associated with a Radio Resource Control (RRC) signaling entry including the plurality of K1 values.

[0125] Aspect 12 is the method according to aspect 10, wherein the indication of the at least one K1 value received via the DCI message includes the plurality of K1 values ​​in the DCI message.

[0126] Aspect 13 is a method according to any one of Aspects 1 to 12, wherein the plurality of PDSCH transmissions are organized into at least one PDSCH transmission group, each of the at least one PDSCH transmission group being associated with one of the at least one K1 values, and each of the at least one PDSCH transmission group corresponding via an associated K1 value to one of the at least one PUCCH resources and one or more ACK / NACK indications of the at least one ACK / NACK indication, wherein the indication of the at least one K1 value received via the DCI message is associated with a first table received via Radio Resource Control (RRC) signaling, the first table including at least one entry associating the PDSCH transmission group size with at least one K1 value.

[0127] Aspect 14 is the method according to aspect 13, wherein the DCI message further includes an indication of the size of a PDSCH transport group associated with the plurality of PDSCH transports, the indication of the PDSCH transport group size corresponding to an entry in the at least one entry of the first table.

[0128] Aspect 15 is the method according to aspect 13, further comprising: receiving from the base station via RRC signaling an indication of the size of a PDSCH transmission group associated with the plurality of PDSCH transmissions.

[0129] Aspect 16 is an apparatus for wireless communication, including at least one processor coupled to a memory and configured to implement the methods of any one of aspects 1 to 15.

[0130] Aspect 17 is an apparatus for wireless communication, including units for implementing the methods of any one of aspects 1 to 15.

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

[0132] Aspect 19 is a method of wireless communication at a base station, comprising: sending to a user equipment (UE) via a downlink control information (DCI) message an indication of at least one K1 value corresponding to a plurality of PDSCH transmissions on a plurality of physical downlink shared channel (PDSCH) resources, the at least one K1 value being associated with at least one physical uplink control channel (PUCCH) resource and indicating PDSCH to Hybrid Automatic Repeat Request (HARQ) timing; and receiving from the UE via the at least one PUCCH resource at least one acknowledgment / negative acknowledgment (ACK / NACK) indication associated with the at least one K1 value and corresponding to the plurality of PDSCH transmissions.

[0133] Aspect 20 is the method according to aspect 19, wherein the at least one K1 value indicates a timing delay, in timeslots, between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource.

[0134] Aspect 21 is a method according to any one of Aspects 19 and 20, wherein the at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transmissions, the at least one PUCCH resource includes a plurality of PUCCH resources, each of the plurality of PDSCH transmissions corresponds to one of the plurality of PUCCH resources, the at least one ACK / NACK indication includes a plurality of ACK / NACK indications, and the method further includes: receiving the plurality of ACK / NACK indications from the UE via the plurality of PUCCH resources, wherein each of the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications, and each of the plurality of PUCCH resources carries one of the plurality of ACK / NACK indications.

[0135] Aspect 22 is the method according to any one of Aspects 19 and 20, wherein the plurality of PDSCH transmissions are organized into at least one PDSCH transmission group, the at least one K1 value includes a single K1 value applicable to each of the at least one PDSCH transmission groups, and each of the at least one PDSCH transmission groups is associated via the single K1 value with one or more ACK / NACK indications of the at least one ACK / NACK indication carried in an associated PUCCH resource and a PUCCH resource.

[0136] Aspect 23 is the method according to aspect 22, wherein each of the at least one PDSCH transmission groups or all PDSCH transmission groups other than one of the at least one PDSCH transmission groups comprises an equal number of consecutive PDSCH transmissions.

[0137] Aspect 24 is a method according to any one of Aspects 19 and 20, wherein the plurality of PDSCH transmissions are organized into a plurality of PDSCH transmission groups, the at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission group in the plurality of PDSCH transmission groups, each of the plurality of PDSCH transmission groups being associated with a PUCCH resource in the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication including a plurality of ACK / NACK indications, and the method further includes: receiving the plurality of ACK / NACK indications from the UE via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmission groups is associated with one or more ACK / NACK indications in the plurality of ACK / NACK indications.

[0138] Aspect 25 is the method according to aspect 24, wherein each of the plurality of PDSCH transmission groups or all PDSCH transmission groups other than one of the plurality of PDSCH transmission groups comprises an equal number of consecutive PDSCH transmissions.

[0139] Aspect 26 is the method according to aspect 24, further comprising: sending a first limit to the UE via radio resource control (RRC) signaling regarding the number of the at least one PUCCH resource, wherein the number of groups of the plurality of PDSCH transmission groups is less than or equal to the first limit.

[0140] Aspect 27 is the method according to aspect 26, further comprising: sending a second limit to the UE in the DCI message regarding the number of the at least one PUCCH resource, the second limit being less than or equal to the first limit, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the second limit.

[0141] Aspect 28 is a method according to any one of Aspects 19 and 20, wherein the at least one K1 value comprises a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission among the plurality of PDSCH transmissions, each of the plurality of PDSCH transmissions being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication comprising a plurality of ACK / NACK indications, and the method further comprising: receiving the plurality of ACK / NACK indications from the UE via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmissions is associated with an ACK / NACK indication among the plurality of ACK / NACK indications.

[0142] Aspect 29 is the method according to aspect 28, wherein the indication of the at least one K1 value sent via the DCI message is associated with a Radio Resource Control (RRC) signaling entry including the plurality of K1 values.

[0143] Aspect 30 is the method according to aspect 28, wherein the indication of the at least one K1 value sent via the DCI message includes the plurality of K1 values ​​in the DCI message.

[0144] Aspect 31 is a method according to any one of aspects 19 to 30, wherein the plurality of PDSCH transmissions are organized into at least one PDSCH transmission group, each of the at least one PDSCH transmission group being associated with one of the at least one K1 values, and each of the at least one PDSCH transmission group corresponding via an associated K1 value to one of the at least one PUCCH resources and one or more ACK / NACK indications of the at least one ACK / NACK indication, wherein the indication of the at least one K1 value sent via the DCI message is associated with a first table sent via Radio Resource Control (RRC) signaling, the first table including at least one entry associating the PDSCH transmission group size with at least one K1 value.

[0145] Aspect 32 is the method according to aspect 31, wherein the DCI message further includes an indication of the size of a PDSCH transport group associated with the plurality of PDSCH transports, the indication of the PDSCH transport group size corresponding to an entry in the at least one entry of the first table.

[0146] Aspect 33 is the method according to aspect 31, further comprising: sending an indication to the UE via RRC signaling of the size of a PDSCH transmission group associated with the plurality of PDSCH transmissions.

[0147] Aspect 34 is an apparatus for wireless communication, including at least one processor coupled to a memory and configured to implement the methods of any one of aspects 19 to 33.

[0148] Aspect 35 is an apparatus for wireless communication, including units for implementing the methods of any one of aspects 19 to 33.

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

Claims

1. A method for wireless communication at a user equipment (UE), comprising: The system receives from the base station via a downlink control information (DCI) message an indication of at least one K1 value corresponding to multiple PDSCH transmissions on multiple physical downlink shared channel (PDSCH) resources, the DCI message including scheduling information for the multiple PDSCH transmissions, the at least one K1 value being associated with at least one physical uplink control channel (PUCCH) resource and indicating the PDSCH to Hybrid Automatic Repeat Request (HARQ) timing. A first limit on the number of the at least one PUCCH resource is received from the base station via Radio Resource Control (RRC) signaling; Based on the first limitation, the plurality of PDSCH transmissions are organized into a plurality of PDSCH transmission groups, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the first limitation; as well as At least one acknowledgment / negative acknowledgment (ACK / NACK) indication associated with the at least one K1 value and corresponding to the plurality of PDSCH transmissions is sent to the base station via the at least one PUCCH resource.

2. The method of claim 1, wherein, The at least one K1 value indicates the timing delay between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource, in time slots.

3. The method according to claim 2, wherein, The at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transmissions, the at least one PUCCH resource includes a plurality of PUCCH resources, each of the plurality of PDSCH transmissions corresponds to one of the plurality of PUCCH resources, the at least one ACK / NACK indication includes a plurality of ACK / NACK indications, and the method further includes: The plurality of ACK / NACK indications are sent to the base station via the plurality of PUCCH resources, wherein each PDSCH transmission in the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications, and each PUCCH resource in the plurality of PUCCH resources carries one of the plurality of ACK / NACK indications.

4. The method according to claim 2, wherein, The at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transport groups, and each of the plurality of PDSCH transport groups is associated via the single K1 value with one or more ACK / NACK indications of the at least one ACK / NACK indication carried in an associated PUCCH resource and a PUCCH resource.

5. The method according to claim 4, wherein, Each of the plurality of PDSCH transport groups, or all PDSCH transport groups except for one of the plurality of PDSCH transport groups, comprises an equal number of consecutive PDSCH transports.

6. The method according to claim 2, wherein, The at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding group among the plurality of PDSCH transport groups, each of the plurality of PDSCH transport groups being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication including a plurality of ACK / NACK indications, and the method further includes: The plurality of ACK / NACK indications are sent to the base station via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmission groups is associated with one or more of the plurality of ACK / NACK indications.

7. The method according to claim 6, wherein, Each of the plurality of PDSCH transport groups, or all PDSCH transport groups except for one of the plurality of PDSCH transport groups, comprises an equal number of consecutive PDSCH transports.

8. The method according to claim 6, further comprising: The DCI message receives a second limit from the base station regarding the number of the at least one PUCCH resource, the second limit being less than or equal to the first limit; as well as The plurality of PDSCH transmissions are organized into the plurality of PDSCH transmission groups based on the second limitation, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the second limitation.

9. The method according to claim 2, wherein, The at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission among the plurality of PDSCH transmissions, each of the plurality of PDSCH transmissions being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication including a plurality of ACK / NACK indications, and the method further includes: The plurality of ACK / NACK indications are sent to the base station via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications.

10. The method according to claim 9, wherein, The indication of at least one K1 value received via the DCI message is associated with a Radio Resource Control (RRC) signaling entry that includes the plurality of K1 values.

11. The method according to claim 9, wherein, The indication of the at least one K1 value received via the DCI message includes the plurality of K1 values ​​in the DCI message.

12. The method according to claim 2, wherein, Each of the plurality of PDSCH transport groups is associated with one of the at least one K1 values, and each of the plurality of PDSCH transport groups corresponds via an associated K1 value to one of the at least one PUCCH resources and one or more ACK / NACK indications of the at least one ACK / NACK indication. The indication of the at least one K1 value received via the DCI message is associated with a first table received via Radio Resource Control (RRC) signaling, the first table including at least one entry that associates the PDSCH transport group size with at least one K1 value.

13. The method according to claim 12, wherein, The DCI message also includes an indication of the size of the PDSCH transport group associated with the plurality of PDSCH transports, the indication of the PDSCH transport group size corresponding to one of the at least one entries in the first table.

14. The method of claim 12, further comprising: The system receives an indication from the base station via RRC signaling of the size of the PDSCH transmission group associated with the plurality of PDSCH transmissions.

15. An apparatus for wireless communication, the apparatus being a user equipment (UE), comprising: Memory; as well as At least one processor coupled to the memory and configured to perform the method according to any one of claims 1 to 14.

16. A method for wireless communication at a base station, comprising: The system sends an indication to the user equipment (UE) via a downlink control information (DCI) message for at least one K1 value corresponding to multiple PDSCH transmissions on multiple physical downlink shared channel (PDSCH) resources. The DCI message includes scheduling information for the multiple PDSCH transmissions. The at least one K1 value is associated with at least one physical uplink control channel (PUCCH) resource and indicates the PDSCH timing to Hybrid Automatic Repeat Request (HARQ). A first limit regarding the number of the at least one PUCCH resource is sent to the UE via Radio Resource Control (RRC) signaling, wherein the plurality of PDSCH transmissions are organized into a plurality of PDSCH transmission groups, and the number of the plurality of PDSCH transmission groups is less than or equal to the first limit; as well as Receive from the UE via the at least one PUCCH resource at least one ACK / NACK indication associated with the at least one K1 value and corresponding to the plurality of PDSCH transmissions.

17. The method according to claim 16, wherein, The at least one K1 value indicates the timing delay between the last PDSCH resource in the corresponding PDSCH resource or the corresponding PDSCH resource group and an associated PUCCH resource in the at least one PUCCH resource, in time slots.

18. The method according to claim 17, wherein, The at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transmissions, the at least one PUCCH resource includes a plurality of PUCCH resources, each of the plurality of PDSCH transmissions corresponds to one of the plurality of PUCCH resources, the at least one ACK / NACK indication includes a plurality of ACK / NACK indications, and the method further includes: The UE receives the plurality of ACK / NACK indications via the plurality of PUCCH resources, wherein each of the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications, and each of the plurality of PUCCH resources carries one of the plurality of ACK / NACK indications.

19. The method of claim 17, wherein, The at least one K1 value includes a single K1 value applicable to each of the plurality of PDSCH transport groups, and each of the plurality of PDSCH transport groups is associated via the single K1 value with one or more ACK / NACK indications of the at least one ACK / NACK indication carried in an associated PUCCH resource and a PUCCH resource.

20. The method according to claim 19, wherein, Each of the plurality of PDSCH transport groups, or all PDSCH transport groups except for one of the plurality of PDSCH transport groups, comprises an equal number of consecutive PDSCH transports.

21. The method according to claim 17, wherein, The at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission group among the plurality of PDSCH transmission groups, each of the plurality of PDSCH transmission groups being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication including a plurality of ACK / NACK indications, and the method further includes: The plurality of ACK / NACK indications are received from the UE via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmission groups is associated with one or more of the plurality of ACK / NACK indications.

22. The method according to claim 21, wherein, Each of the plurality of PDSCH transport groups, or all PDSCH transport groups except for one of the plurality of PDSCH transport groups, comprises an equal number of consecutive PDSCH transports.

23. The method of claim 21, further comprising: The DCI message sends a second limit to the UE regarding the number of the at least one PUCCH resource, the second limit being less than or equal to the first limit, wherein the number of the plurality of PDSCH transmission groups is less than or equal to the second limit.

24. The method of claim 17, wherein, The at least one K1 value includes a plurality of K1 values, each of the plurality of K1 values ​​being applicable to a corresponding PDSCH transmission among the plurality of PDSCH transmissions, each of the plurality of PDSCH transmissions being associated with a PUCCH resource among the at least one PUCCH resource via a corresponding K1 value, the at least one ACK / NACK indication including a plurality of ACK / NACK indications, and the method further includes: The plurality of ACK / NACK indications are received from the UE via the at least one PUCCH resource, wherein each of the plurality of PDSCH transmissions is associated with one of the plurality of ACK / NACK indications.

25. The method according to claim 24, wherein, The indication of at least one K1 value sent via the DCI message is associated with a Radio Resource Control (RRC) signaling entry that includes the plurality of K1 values.

26. The method according to claim 24, wherein, The indication of at least one K1 value sent via the DCI message includes the plurality of K1 values ​​in the DCI message.

27. The method according to claim 17, wherein, Each of the plurality of PDSCH transport groups is associated with one of the at least one K1 values, and each of the plurality of PDSCH transport groups corresponds via an associated K1 value to one of the at least one PUCCH resources and one or more ACK / NACK indications of the at least one ACK / NACK indication. The indication of the at least one K1 value sent via the DCI message is associated with a first table sent via Radio Resource Control (RRC) signaling, the first table including at least one entry that associates the PDSCH transport group size with at least one K1 value.

28. An apparatus for wireless communication at a base station, comprising: Memory; as well as At least one processor coupled to the memory and configured to perform the method according to any one of claims 16 to 27.

Images