Multiple Tb Configuration in Multi-Pdsch Grant

This application is a Continuation of U.S. Non-provisional application Ser. No. 17/818,941, entitled “MULTIPLE TB CONFIGURATION IN MULTI-PDSCH GRANT” and filed on Aug. 10, 2022, which claims the benefit of and priority to U.S. Provisional Application Ser. No. 63/238,090, entitled “MULTIPLE TB CONFIGURATION IN MULTI-PDSCH GRANT” and filed on Aug. 27, 2021, which are expressly incorporated by reference herein in their entirety.

The present disclosure relates generally to communication systems, and more particularly, to a method for wireless communication including multiple transport block (TB) configuration in a multi-physical downlink shared channel (PDSCH) grant.

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

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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 may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates 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 description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a user equipment (UE), and the UE may be configured to receive a parameter indicating that two codeword transmission for physical downlink shared channel (PDSCH) transmissions is enabled by a network node, receive a multi-PDSCH grant in a single downlink control information (DCI) comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant from the network node; and receive each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block from the network node

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a network node, and the network node may be configured to transmit a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, transmit a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and transmit each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

A network node may provide a user equipment (UE) with a single downlink control information (DCI) to schedule multiple physical downlink shared channel (PDSCH) transmissions to the UE (e.g., multiple downlink (DL) TBs) or multiple physical uplink shared channel (PUSCH) transmissions from the UE (e.g., multiple uplink (UL) TBs). In some aspects, the resource allocation may be across multiple slots. The single DCI may reduce the control signaling overhead and/or may reduce monitoring and processing of scheduling physical downlink control channel (PDCCH) at the UE. As an example, a UE may avoid monitoring for and/or processing scheduling PDCCH in each slot if the network node provides the UE with a single DCI that allocates resources in multiple slots. As well, the network node may reduce control signaling overhead by reducing the number of DCI transmitted to the UE. A PDSCH may include multiple codewords in a single PDSCH transmission. For example, the PDSCH may have a higher layer parameter that enables a maximum number of codewords scheduled by DCI that allows for 2, or possibly more, codewords. If a maximum number of 2 codewords is enabled, there may be times when the network node does not transmit multiple codewords in a PDSCH transmission. In such aspects, a second transport block (TB) may be disabled for the PDSCH transmission. The network node may indicate that the TB is disabled through a particular combination of a modulation and coding scheme (MCS) and redundancy version (RV) indicated in the DCI for the PDSCH.

Aspects presented herein enable a network node to indicate to a UE that a second TB is disabled for multiple PDSCH scheduled through a single DCI. In contrast to a single PDSCH transmission, a DCI scheduling resources for multiple PDSCH transmissions indicates a MCS and an individual RV for each PDSCH. In some aspects, a combination of a particular value of the MCS and at least one of the RVs in the single DCI may indicate that the second TB is disabled for each of the PDSCHs scheduled by the DCI. In some aspects, a combination of a particular value of the MCS together with a particular pattern of RVs values may indicate to the UE that the second TB is disabled for each of the PDSCHs scheduled by the DCI. The use of the pattern of RV values with the particular MCS value may provide the network node with added flexibility in scheduling combinations of MCS and RV for the various PDSCHs while continuing to enable the second TB, e.g., without indicating that the second TB is disabled.

The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), 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 functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

1 FIG. 100 102 104 160 190 102 is a diagram illustrating an example of a wireless communications system and an access network. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations, UEs, an Evolved Packet Core (EPC), and another core network(e.g., a 5G Core (5GC)). The base stationsmay include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

102 160 132 102 190 184 102 102 160 190 134 132 184 134 The base stationsconfigured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPCthrough first backhaul links(e.g., S1 interface). The base stationsconfigured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core networkthrough second backhaul links. In addition to other functions, the base stationsmay perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stationsmay communicate directly or indirectly (e.g., through the EPCor core network) with each other over third backhaul links(e.g., X2 interface). The first backhaul links, the second backhaul links, and the third backhaul linksmay be wired or wireless.

102 104 102 110 110 102 110 110 102 120 102 104 104 102 102 104 120 102 104 The base stationsmay wirelessly communicate with the UEs. Each of the base stationsmay provide communication coverage for a respective geographic coverage area. There may be overlapping geographic coverage areas. For example, the small cell′ may have a coverage area′ that overlaps the coverage areaof one or more macro base stations. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication linksbetween the base stationsand the UEsmay include uplink (UL) (also referred to as reverse link) transmissions from a UEto a base stationand/or downlink (DL) (also referred to as forward link) transmissions from a base stationto a UE. The communication linksmay use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations/UEsmay use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

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

150 152 154 152 150 The wireless communications system may further include a Wi-Fi access point (AP)in communication with Wi-Fi stations (STAs)via communication links, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs/APmay perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

102 102 150 102 The small cell′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell′ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHZ, or the like) as used by the Wi-Fi AP. The small cell′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

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

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

With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.

102 102 180 104 180 180 180 182 104 180 104 A base station, whether a small cell′ or a large cell (e.g., 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 gNBmay operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE. When the gNBoperates in millimeter wave or near millimeter wave frequencies, the gNBmay be referred to as a millimeter wave base station. The millimeter wave base stationmay utilize beamformingwith the UEto compensate for the path loss and short range. The base stationand the UEmay each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

180 104 182 104 180 182 104 180 180 104 180 104 180 104 180 104 The base stationmay transmit a beamformed signal to the UEin one or more transmit directions′. The UEmay receive the beamformed signal from the base stationin one or more receive directions″. The UEmay also transmit a beamformed signal to the base stationin one or more transmit directions. The base stationmay receive the beamformed signal from the UEin one or more receive directions. The base station/UEmay perform beam training to determine the best receive and transmit directions for each of the base station/UE. The transmit and receive directions for the base stationmay or may not be the same. The transmit and receive directions for the UEmay or may not be the same.

160 162 164 166 168 170 172 162 174 162 104 160 162 166 172 172 172 170 176 176 170 170 168 102 190 192 193 194 195 192 196 192 104 190 192 195 195 195 197 197 The EPCmay include a Mobility Management Entity (MME), other MMEs, a Serving Gateway, a Multimedia Broadcast Multicast Service (MBMS) Gateway, a Broadcast Multicast Service Center (BM-SC), and a Packet Data Network (PDN) Gateway. The MMEmay be in communication with a Home Subscriber Server (HSS). The MMEis the control node that processes the signaling between the UEsand the EPC. Generally, the MMEprovides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway, which itself is connected to the PDN Gateway. The PDN Gatewayprovides UE IP address allocation as well as other functions. The PDN Gatewayand the BM-SCare connected to the IP Services. The IP Servicesmay include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SCmay provide functions for MBMS user service provisioning and delivery. The BM-SCmay serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gatewaymay be used to distribute MBMS traffic to the base stationsbelonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information. The core networkmay include an Access and Mobility Management Function (AMF), other AMFs, a Session Management Function (SMF), and a User Plane Function (UPF). The AMFmay be in communication with a Unified Data Management (UDM). The AMFis the control node that processes the signaling between the UEsand the core network. Generally, the AMFprovides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF. The UPFprovides UE IP address allocation as well as other functions. The UPFis connected to the IP Services. The IP Servicesmay include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

102 160 190 104 104 104 104 The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base stationprovides an access point to the EPCor core networkfor a UE. Examples of UEsinclude a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEsmay be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UEmay also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

1 FIG. 104 198 180 199 Referring again to, in certain aspects, the UEmay include a multi-PDSCH grant configuration componentconfigured to receive, from a base station, a parameter enabling two codeword transmission for PDSCH transmissions, receive, from the base station, a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant, and receive, from the base station, each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block. In certain aspects, the base stationmay include a multi-PDSCH grant configuration componentconfigured to transmit, to a UE, a parameter enabling two codeword transmission for PDSCH transmissions, transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant, and transmit each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

2 FIG.A 2 FIG.B 2 FIG.C 2 FIG.D 2 2 FIGS.A,C 200 230 250 280 4 28 3 1 3 4 1 28 0 61 0 1 2 61 is a diagramillustrating an example of a first subframe within a 5G NR frame structure.is a diagramillustrating an example of DL channels within a 5G NR subframe.is a diagramillustrating an example of a second subframe within a 5G NR frame structure.is a diagramillustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by, the 5G NR frame structure is assumed to be TDD, with subframebeing configured with slot format(with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframebeing configured with slot format(with all UL). While subframes,are shown with slot formats,, respectively, any particular subframe may be configured with any of the various available slot formats-. Slot formats,are all DL, UL, respectively. Other slot formats-include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

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

TABLE A numerology, SCS, and cyclic prefix SCS μ μ Δf = 2· 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

μ μ 2 2 FIGS.A-D 2 FIG.B For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2slots/subframe. The subcarrier spacing may be equal to 2*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 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.

2 FIG.A As illustrated in, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

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

2 FIG.C As illustrated in, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

2 FIG.D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

3 FIG. 310 350 375 375 375 is a block diagram of a base stationin communication with a UEin an access network. In the DL, Internet protocol (IP) packets may be provided to a controller/processor. The controller/processorimplements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processorprovides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), 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 functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

316 370 316 374 350 320 318 318 The transmit (TX) processorand the receive (RX) processorimplement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processorhandles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together 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 produce multiple spatial streams. Channel estimates from a channel estimatormay be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE. Each spatial stream may then be provided to a different antennavia a separate transmitterTx. Each transmitterTx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

350 354 352 354 356 368 356 356 350 350 356 356 310 358 310 359 At the UE, each receiverRx receives a signal through its respective antenna. Each receiverRx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor. The TX processorand the RX processorimplement layer 1 functionality associated with various signal processing functions. The RX processormay perform spatial processing on the information to recover any spatial streams destined for the UE. If multiple spatial streams are destined for the UE, they may be combined by the RX processorinto a single OFDM symbol stream. The RX processorthen converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station. These soft decisions may be based on channel estimates computed by the channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base stationon the physical channel. The data and control signals are then provided to the controller/processor, which implements layer 3 and layer 2 functionality.

359 360 360 359 359 The controller/processorcan be associated with a memorythat stores program codes and data. The memorymay be referred to as a computer-readable medium. In the UL, the controller/processorprovides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processoris also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

310 359 Similar to the functionality described in connection with the DL transmission by the base station, the controller/processorprovides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

358 310 368 368 352 354 354 Channel estimates derived by a channel estimatorfrom a reference signal or feedback transmitted by the base stationmay be used by the TX processorto select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processormay be provided to different antennavia separate transmittersTx. Each transmitterTx may modulate an RF carrier with a respective spatial stream for transmission.

310 350 318 320 318 370 The UL transmission is processed at the base stationin a manner similar to that described in connection with the receiver function at the UE. Each receiverRx receives a signal through its respective antenna. Each receiverRx recovers information modulated onto an RF carrier and provides the information to a RX processor.

375 376 376 375 375 The controller/processorcan be associated with a memorythat stores program codes and data. The memorymay be referred to as a computer-readable medium. In the UL, the controller/processorprovides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processoris also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

368 356 359 198 316 370 375 199 1 FIG. 1 FIG. At least one of the TX processor, the RX processor, and the controller/processormay be configured to perform aspects in connection with the multi-PDSCH grant configuration componentof. At least one of the TX processor, the RX processor, and the controller/processormay be configured to perform aspects in connection with the multi-PDSCH grant configuring componentof.

A network node may provide a UE with a single downlink control information (DCI) to schedule multiple PDSCH transmissions to the UE (e.g., multiple downlink (DL) TBs) or multiple PUSCH transmissions from the UE (e.g., multiple uplink (UL) TBs). In some aspects, the resource allocation may be across multiple slots. The single DCI may reduce the control signaling overhead and/or may reduce monitoring and processing of scheduling PDCCH at the UE. As an example, a UE may avoid monitoring for and/or processing scheduling PDCCH in each slot if the network node provides the UE with a single DCI that allocates resources in multiple slots. As used herein, a “single DCI” refers to one DCI message, e.g., one control message within a PDCCH transmission, that may include multiple parameters relating to control information to the UE.

In some aspects, the multi-PDSCH/PUSCH DCI may indicate the allocated resources based on a time domain resource allocation (TDRA) table. Table B illustrates an example TDRA table. Table B is merely an example of a TDRA table to illustrate the concept, and a DCI grant may be based on any of various TDRA tables.

For a single DCI that schedules multiple PUSCHs, the TDRA table may include entries such that each row indicates multiple PUSCHs (that may be non-continuous in time-domain). Each PUSCH may have a separate start and length indicator value (SLIV) and mapping type. The number of scheduled PUSCHs may be implicitly indicated by the number of indicated valid SLIVs in the row of the TDRA table signalled in DCI. For a DCI that can schedule multiple PDSCHs, the TDRA may include entries such that each row indicates multiple PDSCHs. Each PDSCH may have a separate SLIV and mapping type. The number of scheduled PDSCHs may be implicitly indicated by the number of indicated valid SLIVs in the row of the TDRA table signalled in DCI. The DCI may indicate multiple PUSCH/PDSCH grants that are continuous resource in a time-domain or that are non-continuous in the time domain. The multiple SLIVs for a particular index of the TDRA table may be indicated in various ways. For example, each row may use S, L columns or may use SLIV values. Regardless of the way in which the multiple SLIVs are indicated, one row index may correspond to multiple SLIVs.

TABLE B TDRA table row PUSCH index mapping type K2 SLIV 0 Type A (0 . . . 32) (0 .127), (0 .127) 1 Type B (0 . . . 32) (0 .127), ., (0 .127)

2 2 0 As illustrated, each row of the TDRA table may row indicate resource allocations for multiple PUSCHs or for multiple PDSCHs, e.g., two to eight PUSCHs/PDSCHs. For PUSCH, each row of the TDRA table may indicate a corresponding Kparameter that indicates the slot where UE is to transmit the first PUSCH of the multiple PUSCHs. For example, Kmay indicate a time period between the DCI and the slot for the transmission of the first PUSCH. For PDSCH, each row of the TDRA table may indicate a corresponding Kparameter that indicates the slot where UE is to receive the first PDSCH of the multiple PDSCHs. Each PUSCH/PDSCH may have a separate SLIV and mapping type. The number of scheduled PUSCHs/PDSCHs may be indicated by the number of indicated valid SLIVs in the row indicated by an index indicated in the scheduling DCI. As an example, a TDRA for continuous multi-PUSCH may be signalled to the UE for multi-PUSCH DCI in pusch-TimeDomainAllocationListForMultiPUSCH.

The DCI scheduling multiple PUSCHs may indicate one or transmission parameters that are the same for each scheduled PUSCHs and may be referred to as common to each of the scheduled PUSCHs. In some aspects, the DCI may indicate a common frequency domain resource allocation (FDRA) parameter, a modulation and coding scheme (MCS) parameter, or a common rank parameter that are shared by each of the PUSCHs scheduled by the DCI. In one aspect, the starting and/or ending positions of the multiple PUSCHs may be provided by a time domain resource allocation TDRA parameter, e.g., as described in connection with Table B. For example, the TDRA parameter may include multiple SLIVs, associated with the starting and/or ending positions of the multiple PUSCH.

In one aspect, the UL grant may indicate the first hybrid automatic repeat request (HARQ) process ID, and the later transmissions may use incremental HARQ process IDs. In another aspect, each PUSCH of the multiple PUSCHs may be associated with separate parameters, e.g., separate new data indicator (NDI), or separate redundancy version (RV) identifier (ID) (RVID).

A multiple PDSCH (multi-PUSCH) grant feature may be provided to similarly reduce control overhead for scheduling downlink transmissions. The multi-PDSCH grant may refer to one DL grant, e.g., a single DCI message, that schedules multiple PDSCH transmissions. That is, a network node may transmit one DL grant scheduling resources for multiple PDSCH transmissions.

4 4 FIGS.A andB 4 FIG.A 4 FIG.B 4 4 FIGS.A andB 4 FIG.B 4 FIG.A 400 450 400 1 2 3 4 1 2 3 4 450 1 1 2 3 4 1 1 2 3 4 are diagramsand, respectively, of single PDSCH scheduling and multiple PDSCH (multi-PDSCH) scheduling. As shown in, diagramincludes single PDSCH scheduling with multiple downlink (DL) grants, e.g., DL grant, DL grant, DL grant, and DL grant, as well as multiple PDSCHs, e.g., PDSCH, PDSCH, PDSCH, and PDSCH. As shown in, diagramincludes multi-PDSCH scheduling with one DL grant, e.g., DL grant, as well as multiple PDSCHs, e.g., PDSCH, PDSCH, PDSCH, and PDSCH.show multi-PDSCH scheduling () can reduce the signaling overhead by including one DL grant, e.g., DL grant, compared to single PDSCH scheduling () which utilizes multiple DL grant, e.g., DL grant, DL grant, DL grant, and DL grant.

4 FIG.B As shown in, multiple PDSCH scheduling or multi-PDSCH scheduling may also be beneficial for reducing power consumption.

In higher frequency bands, such as a frequency band above 52.6 GHz, there may be a wider available bandwidth for wireless communication. A higher SCS may be used for the wireless communication to reduce phase noise and/or to utilize the wider available bandwidth. A higher SCS corresponds to shorter symbol and slot durations. In some aspects, the single DCI scheduling multiple PDSCH transmissions or multiple PUSCH transmissions may reduce overhead and/or may improve scheduling for shorter slot durations associated with a higher SCS. For example, the multi-PDSCH grant may help the network node to schedule longer downlink bursts.

0 1 In some instances, a time domain resource allocation (TDRA) in DCI, e.g., DCI_, may indicate a combination of multiple PDSCHs, where candidate combinations may be configured by radio resource control (RRC) signaling. Moreover, multi-PDSCH scheduling may support a certain number of PDSCHs, e.g., up to 8 PDSCHs, that are continuous or intermittent in time domain.

The DCI scheduling multiple PDSCHs may indicate one or more common parameters that are shared for each of the PDSCH. For example, the DCI may indicate a MCS that is shared by each of the TBs of the multiple PDSCHs. As described in connection with the DCI for multiple PUSCH scheduling, the common parameters may include FDRA, rank, or other parameters that are shared by each of the multiple PDSCHs being scheduled by the DCI. An individual RV and/or NDI may be indicated for each of the multiple PDSCHs.

The PDSCHs of the multi-PDSCH, may include more than one transport block (TB) and corresponding more than one codeword. That is, each PDSCH of the multi-PDSCH may be configured to carry one or more TBs, and each TB may carry at least one codeword. The network node may transmit an indication or a parameter to enable the multiple TB.

The network node may enable the inclusion of multiple codeword transmission, e.g., in 2 TBs of a PDSCH transmission through a configuration of a higher layer parameter that indicates a maximum number of codewords scheduled by DCI (e.g., which may be referred to as “maxNrofCodeWordsScheduledByDCI”) with a value of 2, e.g., in RRC signaling to the UE. If the maximum number is configured, or otherwise indicated, as “2”, the network node may transmit PDSCH comprising two codewords, e.g., in 2 TBs, to a UE. If the maximum number is configured, or otherwise indicated, as “1”, the network node may send a single codeword in a single TB of a PDSCH transmission.

0 1 For example, two TBs may be configured for each PDSCH, and two codewords may be scheduled on downlink transmission. In one aspect, both TBs may be enabled, and the first TB and the second TB may be mapped to a first codeword (codeword) and a second codeword (codeword), respectively.

1 2 0 1 If the transmission of multiple codewords, e.g., in multiple TBs, is enabled by the higher layer indication, there may be times when the network node does not transmit a second TB in the PDSCH. The network node may indicate in DCI to the UE that the network node will not transmit multiple TBs (and therefore is not going to transmit multiple codewords) in a PDSCH transmission so that the UE accurately receives the PDSCH transmission. For example, if both TBs are enabled, and the higher layer parameter indicates that two codeword transmission is enabled, the TBandmay be mapped to codewordand codeword, respectively. If only 1 TB is enabled (e.g., the second TB is disabled in the DCI), then the enabled TB may be mapped to the first codeword. Here, some aspects provide the two codeword transmission as an example of the multiple codeword transmission, but the current disclosure is not limited thereto. The maximum number of the multiple codeword transmission may be greater than or equal to two (2).

For a DCI scheduling a single PDSCH, the network node may indicate that the second TB is disabled, or will not be transmitted even though the higher layer parameter enables a maxNrofCodeWordsScheduledByDCI of 2, through a combination of an MCS of 26 and an RVID of 1. The UE may interpret the DCI to determine that the enabled TB, e.g., first TB, is mapped to the first codeword of the single PDSCH.

As noted above, the DCI scheduling multiple PDSCH may indicate a same MCS for the TBs of the PDSCHs. That is, a single MCS value indicated in the DCI may be commonly applied to each of the PDSCHs, which may include one or more TBs. Each TB may be configured with an individual RV and/or NDI. In some aspects, the RV or the NDI may be indicated per TB. That is, each TB of the more than one TB of the PDSCH may be scheduled with a separate RV and NDI.

Aspects presented herein enable a network node to indicate to a UE that a second TB is disabled for multiple PDSCH scheduled through a single DCI. In contrast to a single PDSCH transmission, a DCI scheduling resources for multiple PDSCH transmissions indicates a MCS (e.g., a common MCS) and an individual RV for each PDSCH, and individual RV is a single-bit field. In some aspects, a combination of a particular value of the common MCS and at least one of the RVs in the single DCI may indicate that the second TB is disabled for each of the PDSCHs scheduled by the DCI.

In some aspects, the DCI (e.g., multi-PDSCH grant) scheduling the multiple PDSCHs may use a combination of MCS and RV vector (or RVID) value to indicate that the second TB is disabled for each of the multiple PDSCHs. For example, if the combination of MCS=y and RV ID=x indicates that the second TB is disabled, the DCI may include the common MCS=y and the RV ID=x for each of the multiple PDSCHs scheduled by the DCI in order to indicate that the second TB is disabled.

26 In one aspect, a combination of the MCSand the RV=1 for all PDSCHs may indicate to the wireless devices, e.g., the network node or the UE, that the associated at least one PB is disabled.

For example, the higher layer parameter maxNrofCodeWordsScheduledByDCI may be configured to enable 2 codewords to be transmitted in each PDSCH of the multiple PDSCHs, and the network node may disable the second TB of each of the multiple PDSCHs by transmitting the DCI including that the combination of the common MCS of 26 and the individual RVID of each of the multiple PDSCHs of 1.

4 As an example in which the DCI schedulesPDSCH transmissions, the DCI may provide that the MCS=26 and the RVID of the multiple PDSCHs is “1111” to indicate that the second TB of the multiple PDSCHs is disabled. The UE may receive the DCI including the multi-PDSCH grant scheduling the multiple PDSCHs indicating that the MCS=26 and the RVID is “1111,” and understand that the second TB of the multiple PDSCHs are disabled for the multiple PDSCHs scheduled by the DCI. The example of four PDSCH is used merely to illustrate the concept, and the concept may be applied to a multi-PDSCH grant for any number of 2 or more PDSCH.

In some aspects, a combination of a particular value of the common MCS together with a particular pattern of RVs values may indicate to the UE that the second TB is disabled for each of the PDSCHs scheduled by the DCI. The use of the pattern of RV values with the particular common MCS value may provide the network node with added flexibility in scheduling combinations of MCS and RV for the various PDSCHs while continuing to enable the second TB, e.g., without indicating that the second TB is disabled. As an example, a form of an RV vector (or RVID) may be configured to indicate that the second TB is disabled for the multiple PDSCHs scheduled by the DCI. That is, the DCI including the multi-PDSCH grant scheduling the multiple PDSCHs may include a pattern of the RVID of the PDSCH that may indicate that the multiple PDSCHs may be disabled for the multiple PDSCHs scheduled by the DCI.

In some aspects, the pattern of RVID may include two RV indications of any two adjacent PDSCHs being different from each other to indicate that at least one TB is disabled for the multiple PDSCHs. In one aspect, the pattern of RV indications may include an alternating pattern of RV indications.

In one example, two TBs may be configured for the PDSCH, and the multi-PDSCH grant may schedule two (2) PDSCHs. The DCI including the multi-PDSCH grant may include the pattern of the RVID may be value of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs.

In another example, two TBs may be configured for the PDSCH, and the multi-PDSCH grant may schedule eight (8) PDSCHs. The DCI including the multi-PDSCH grant may include the pattern of the RVID may be value of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCHs. The examples of two PDSCHs or eight PDSCHs are used merely to illustrate the concept, and the concept may be applied for any number of two or more PDSCHs.

26 By using a pattern of the RVID of the PDSCH to indicate that the multiple PDSCHs may be disabled for the multiple PDSCHs scheduled by the DCI, the network node and the UE may improve the scheduling flexibility without increasing the data bit of the RVID by reserving the RVID for indicating the redundancy version of the PDSCH. For example, if a first transmission of a first codeword that was communicated via a first PDSCH with RV=0 and MCSfails, the network node may determine to communicate the retransmission of the first codeword via a second PDSCH with RV=1, indicating that the second PDSCH includes a retransmission of the data that was previously transmitted with RV=0. As multiple PDSCH transmissions scheduled by a single DCI may experience similar channel conditions and may each need a retransmission, it may be helpful for the network node to indicate an RV=1 for each of the PDSCHs. The use of a particular pattern of RV IDs to indicate that a second TB is disabled enables the network node to retransmit 2 TB transmissions for each of the PDSCHs with RV=1 and without indicating that the second TB is disabled.

In some aspects, the use of the pattern of RV IDs along with the particular MCS may enabled the network node to indicate that the second TB is disabled without an increased number of bits in the DCI.

5 FIG.A 500 500 502 504 504 502 502 504 502 is a communication diagramof a method of wireless communication. The communication diagrammay include a UEand a network node. The network nodemay configure the UEwith more than one codeword transmission for each PDSCH and transmit DCI including multi-PDSCH grant scheduling multiple PDSCHs. The DCI may include an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. The UEmay receive the DCI including multi-PDSCH grant scheduling multiple PDSCHs, the DCI including the indication that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant, and understand that the multiple PDSCHs scheduled by the multi-PDSCH grant. The network nodemay transmit each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, and the UEmay receive each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block.

506 504 502 502 504 At, the network nodemay transmit, to the UE, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. The UEmay receive, from the network node, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. The parameter enabling two codeword transmission for PDSCH transmissions may be configured using the higher layer parameter of an RRC message.

508 504 502 502 504 At, the network nodemay transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. The UEmay receive, from the network node, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Here, the multi-PDSCH grant may include a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant.

In one aspect, the indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may correspond to a combination of an MCS and a pattern of RV indications included in the single DCI. In one example, the MCS in the combination may be 26. In another example, each RV indication in the pattern of RV indications may correspond to a 1. For example, the DCI including the multi-PDSCH grant associated with the multiple PDSCHs may provide that the MCS of the multiple PDSCHs is 26 and the RVID of the multiple PDSCHs is 1 to indicate that the second TB of the multiple PDSCHs may be disabled.

In another aspect, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. That is, the pattern of RV indications that may indicate that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may include two RV indications of any two adjacent PDSCHs being different from each other. The pattern of RV indications may include an alternating pattern of RV indications.

For example, two TBs may be configured for the PDSCH. In one example, the multi-PDSCH grant may schedule two (2) PDSCHs, and the multi-PDSCH grant may include the pattern of the RVID of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs. In another example, the multi-PDSCH grant may schedule eight (8) PDSCHs, and The DCI including the multi-PDSCH grant may include the pattern of the RVID of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCH grant.

510 504 502 504 512 504 510 512 504 502 510 512 508 550 502 504 514 502 5 FIG.B At, the network nodemay transmit a PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. The UEmay receive, from the network node, the PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. At, the network nodemay transmit another PDSCH indicated by the multi-PDSCH grant based on the disablement of the second TB. Atand, the network nodemay transmit a single TB mapped to a first codeword for each PDSCH indicated in the multi-PDSCH grant. The UEmay receive each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second TB by receiving a single TB mapped to a first codeword for each PDSCH indicated in the multi-PDSCH grant. Although this example is illustrated for an example of two PDSCHs atandscheduled by the DCI at, the concept may be applied for any number of two or more PDSCHs scheduled by a single DCI.shows a communication flowbetween the UEand the network nodein which the network node indicates that the second TB is disabled using a pattern of alternating RV ID values. At, the UEmay receive the RRC message signaling that the maxNrofCodeWordsScheduledByDCI=2, indicating that the maximum number of codewords is 2.

516 502 502 At, the UEmay receive a DCI scheduling multiple PDSCH and indicating an MCS=26 and a pattern of alternating RV ID values (e.g., “010 . . . ” or “101 . . . ”. The UEmay interpret the MCS=26 and alternating RV ID values to mean that the second TB is disabled for each PDSCH scheduled by the DCI.

518 520 522 502 516 516 516 Then, at,, at, the UEmay receive each of the PDSCH, having a single TB mapped to a single codeword. Although this example is illustrated for an example of three PDSCHs scheduled by the DCI, the concept may be applied for any number of two or more PDSCHs scheduled by a single DCI. As an example, for two PDSCHs, the alternating RV ID pattern atmay be “01” or “10”. For four PDSCHs, the alternating RV ID pattern atmay be “1010” or “0101”. For a larger number of PDSCHs, the pattern may be extended.

6 FIG. 600 104 502 1304 1004 is a flowchartof a method of wireless communication. The method may be performed by a UE (e.g., the UE//; the apparatus). The UE may be configured by the network node with more than one codeword transmission for each PDSCH. The UE may receive DCI including multi-PDSCH grant scheduling multiple PDSCHs, the DCI including the indication that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant, and understand that the multiple PDSCHs scheduled by the multi-PDSCH grant. The UE may receive each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block.

602 506 514 504 602 198 At, the UE may receive, from a network node, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. The parameter indicating the enablement of the two codeword transmission for PDSCH transmissions may be configured using the higher layer parameter of an RRC message. For the example, parameter may include maxNrofCodeWordsScheduledByDCI=2, indicating that the maximum number of codewords is 2. For example, atand, the UE may receive, from the network node, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. Furthermore,may be performed by a multi-PDSCH grant configuration component.

604 508 516 502 504 604 198 At, the UE may receive, from the network node, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Here, the multi-PDSCH grant may include a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. For example, atand, the UEmay receive, from the network node, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Furthermore,may be performed by the multi-PDSCH grant configuration component.

In one aspect, the indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may correspond to a combination of an MCS and a pattern of RV indications included in the single DCI. In one example, the MCS in the combination may be 26. In another example, each RV indication in the pattern of RV indications may correspond to a 1. For example, the DCI including the multi-PDSCH grant associated with the multiple PDSCHs may provide that the MCS of the multiple PDSCHs is 26 and the RVID of the multiple PDSCHs is 1 to indicate that the second TB of the multiple PDSCHs may be disabled.

In another aspect, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. That is, the pattern of RV indications that may indicate that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may include two RV indications of any two adjacent PDSCHs being different from each other. The pattern of RV indications may include an alternating pattern of RV indications.

For example, two TBs may be configured for the PDSCH. In one example, the multi-PDSCH grant may schedule two (2) PDSCHs, and the multi-PDSCH grant may include the pattern of the RVID of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs. In another example, the multi-PDSCH grant may schedule eight (8) PDSCHs, and The DCI including the multi-PDSCH grant may include the pattern of the RVID of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCH grant.

606 608 510 512 518 520 522 502 504 606 608 198 At, the UE may receive, from the network node, the PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. In one aspect, the UE may receive each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second TB by receiving a single TB mapped to a first codeword for each PDSCH indicated in the multi-PDSCH grant (). For example, at,,,, and, the UEmay receive, from the network node, the PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. Furthermore,andmay be performed by the multi-PDSCH grant configuration component.

7 FIG. 700 104 502 1304 1004 is a flowchartof a method of wireless communication. The method may be performed by a UE (e.g., the UE//; the apparatus). The UE may be configured by the network node with more than one codeword transmission for each PDSCH. The UE may receive DCI including multi-PDSCH grant scheduling multiple PDSCHs, the DCI including the indication that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant, and understand that the multiple PDSCHs scheduled by the multi-PDSCH grant. The UE may receive each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block.

702 506 514 504 702 198 At, the UE may receive, from a network node, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. The parameter indicating the enablement of the two codeword transmission for PDSCH transmissions may be configured using the higher layer parameter of an RRC message. For example, the parameter may include maxNrofCodeWordsScheduledByDCI=2, indicating that the maximum number of codewords is 2. For example, atand, the UE may receive, from the network node, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. Furthermore,may be performed by a multi-PDSCH grant configuration component.

704 508 516 502 504 704 198 At, the UE may receive, from the network node, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Here, the multi-PDSCH grant may include a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. For example, atand, the UEmay receive, from the network node, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Furthermore,may be performed by the multi-PDSCH grant configuration component.

In one aspect, the indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may correspond to a combination of an MCS and a pattern of RV indications included in the single DCI. In one example, the MCS in the combination may be 26. In another example, each RV indication in the pattern of RV indications may correspond to a 1. For example, the DCI including the multi-PDSCH grant associated with the multiple PDSCHs may provide that the MCS of the multiple PDSCHs is 26 and the RVID of the multiple PDSCHs is 1 to indicate that the second TB of the multiple PDSCHs may be disabled.

In another aspect, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. That is, the pattern of RV indications that may indicate that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may include two RV indications of any two adjacent PDSCHs being different from each other. The pattern of RV indications may include an alternating pattern of RV indications.

For example, two TBs may be configured for the PDSCH. In one example, the multi-PDSCH grant may schedule two (2) PDSCHs, and the multi-PDSCH grant may include the pattern of the RVID of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs. In another example, the multi-PDSCH grant may schedule eight (8) PDSCHs, and The DCI including the multi-PDSCH grant may include the pattern of the RVID of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCH grant.

706 510 512 518 520 522 502 504 706 708 198 At, the UE may receive, from the network node, the PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. For example, at,,,, and, the UEmay receive, from the network node, the PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. Furthermore,andmay be performed by the multi-PDSCH grant configuration component.

8 FIG. 800 102 180 504 1302 1102 1206 is a flowchartof a method of wireless communication. The method may be performed by a network node (e.g., the base station///; the network entity/). The network node may configure the UE with more than one codeword transmission for each PDSCH and transmit DCI including multi-PDSCH grant scheduling multiple PDSCHs. The DCI may include an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. The network node may transmit each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block.

802 506 514 504 502 802 199 At, the network node may transmit, to the UE, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. The parameter indicating the enablement of the two codeword transmission for PDSCH transmissions may be configured using the higher layer parameter of an RRC message. For example, the parameter may include maxNrofCodeWordsScheduledByDCI=2, indicating that the maximum number of codewords is 2. For example, atand, the network nodemay transmit, to the UE, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. Furthermore,may be performed by a multi-PDSCH grant configuring component.

804 508 516 504 502 804 199 At, the network node may transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Here, the multi-PDSCH grant may include a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. For example, atand, the network nodemay transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Furthermore,may be performed by the multi-PDSCH grant configuring component.

In one aspect, the indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may correspond to a combination of an MCS and a pattern of RV indications included in the single DCI. In one example, the MCS in the combination may be 26. In another example, each RV indication in the pattern of RV indications may correspond to a 1. For example, the DCI including the multi-PDSCH grant associated with the multiple PDSCHs may provide that the MCS of the multiple PDSCHs is 26 and the RVID of the multiple PDSCHs is 1 to indicate that the second TB of the multiple PDSCHs may be disabled.

In another aspect, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. That is, the pattern of RV indications that may indicate that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may include two RV indications of any two adjacent PDSCHs being different from each other. The pattern of RV indications may include an alternating pattern of RV indications.

For example, two TBs may be configured for the PDSCH. In one example, the multi-PDSCH grant may schedule two (2) PDSCHs, and the multi-PDSCH grant may include the pattern of the RVID of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs. In another example, the multi-PDSCH grant may schedule eight (8) PDSCHs, and The DCI including the multi-PDSCH grant may include the pattern of the RVID of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCH grant.

806 808 510 512 518 520 522 504 806 808 199 At, the network node may transmit a PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. In one aspect, the network node may transmit each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block by transmitting a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant (). For example, at,,,, and, the network nodemay transmit a PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. Furthermore,andmay be performed by the multi-PDSCH grant configuring component.

9 FIG. 900 102 180 504 1302 1102 1206 is a flowchartof a method of wireless communication. The method may be performed by a network node (e.g., the base station///; the network entity/). The network node may configure the UE with more than one codeword transmission for each PDSCH and transmit DCI including multi-PDSCH grant scheduling multiple PDSCHs. The DCI may include an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. The network node may transmit each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block.

902 506 514 504 502 902 199 At, the network node may transmit, to the UE, a parameter indicating the two codeword transmission for PDSCH transmissions is enabled. The parameter indicating the enablement of the two codeword transmission for PDSCH transmissions may be configured using the higher layer parameter of an RRC message. For example, the parameter may include maxNrofCodeWordsScheduledByDCI=2, indicating that the maximum number of codewords is 2. For example, atand, the network nodemay transmit, to the UE, a parameter indicating that two codeword transmission for PDSCH transmissions is enabled. Furthermore,may be performed by a multi-PDSCH grant configuring component.

904 508 516 504 502 904 199 At, the network node may transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Here, the multi-PDSCH grant may include a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. For example, atand, the network nodemay transmit, to the UE, a multi-PDSCH grant in a single DCI including an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. Furthermore,may be performed by the multi-PDSCH grant configuring component.

In one aspect, the indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may correspond to a combination of an MCS and a pattern of RV indications included in the single DCI. In one example, the MCS in the combination may be 26. In another example, each RV indication in the pattern of RV indications may correspond to a 1. For example, the DCI including the multi-PDSCH grant associated with the multiple PDSCHs may provide that the MCS of the multiple PDSCHs is 26 and the RVID of the multiple PDSCHs is 1 to indicate that the second TB of the multiple PDSCHs may be disabled.

In another aspect, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. That is, the pattern of RV indications that may indicate that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant may include two RV indications of any two adjacent PDSCHs being different from each other. The pattern of RV indications may include an alternating pattern of RV indications.

For example, two TBs may be configured for the PDSCH. In one example, the multi-PDSCH grant may schedule two (2) PDSCHs, and the multi-PDSCH grant may include the pattern of the RVID of 10 or 01 for the two PDSCHs to indicate that the second TB may be disabled for the two PDSCHs scheduled by the multi-PDSCHs. In another example, the multi-PDSCH grant may schedule eight (8) PDSCHs, and The DCI including the multi-PDSCH grant may include the pattern of the RVID of 10101010 or 01010101 for the eight PDSCHs to indicate that the second TB may be disabled for the eight PDSCHs scheduled by the multi-PDSCH grant.

906 510 512 518 520 522 504 906 908 199 At, the network node may transmit a PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. For example, at,,,, and, the network nodemay transmit a PDSCH indicated by the multi-PDSCH grant based on a disablement of the second TB. Furthermore,andmay be performed by the multi-PDSCH grant configuring component.

10 FIG. 3 FIG. 1000 1004 1004 1004 1024 1022 1024 1024 1004 1020 1006 1008 1010 1006 1006 1004 1012 1014 1016 1018 1026 1030 1032 1012 1014 1016 1012 1014 1016 1080 1024 1022 1080 104 1002 1024 1006 1024 1006 1026 1024 1006 1026 1024 1006 1024 1006 1024 1006 1024 1006 1024 1006 350 360 368 356 359 1004 1024 1006 1004 350 1004 is a diagramillustrating an example of a hardware implementation for an apparatus. The apparatusmay be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatusmay include a cellular baseband processor(also referred to as a modem) coupled to one or more transceivers(e.g., cellular RF transceiver). The cellular baseband processormay include on-chip memory′. In some aspects, the apparatusmay further include one or more subscriber identity modules (SIM) cardsand an application processorcoupled to a secure digital (SD) cardand a screen. The application processormay include on-chip memory′. In some aspects, the apparatusmay further include a Bluetooth module, a WLAN module, an SPS module(e.g., GNSS module), one or more sensor modules(e.g., barometric pressure sensor/altimeter; motion sensor such as inertial management unit (IMU), gyroscope, and/or accelerometer(s); light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio and/or other technologies used for positioning), additional memory modules, a power supply, and/or a camera. The Bluetooth module, the WLAN module, and the SPS modulemay include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module, the WLAN module, and the SPS modulemay include their own dedicated antennas and/or utilize the antennasfor communication. The cellular baseband processorcommunicates through the transceiver(s)via one or more antennaswith the UEand/or with an RU associated with a network entity. The cellular baseband processorand the application processormay each include a computer-readable medium/memory′,′, respectively. The additional memory modulesmay also be considered a computer-readable medium/memory. Each computer-readable medium/memory′,′,may be non-transitory. The cellular baseband processorand the application processorare each responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor/application processor, causes the cellular baseband processor/application processorto perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor/application processorwhen executing software. The cellular baseband processor/application processormay be a component of the UEand may include the memoryand/or at least one of the TX processor, the RX processor, and the controller/processor. In one configuration, the apparatusmay be a processor chip (modem and/or application) and include just the cellular baseband processorand/or the application processor, and in another configuration, the apparatusmay be the entire UE (e.g., seeof) and include the additional modules of the apparatus.

198 198 1024 1006 1024 1006 198 1004 1004 1024 1006 198 1004 1004 368 356 359 368 356 359 As discussed supra, the multi-PDSCH grant configuration componentis configured to receive a parameter indicating that two codeword transmission for PDSCH transmissions is enabled by a network node, receive a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant from the network node; and receive each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block from the network node. The multi-PDSCH grant configuration componentmay be within the cellular baseband processor, the application processor, or both the cellular baseband processorand the application processor. The multi-PDSCH grant configuration componentmay be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatusmay include a variety of components configured for various functions. In one configuration, the apparatus, and in particular the cellular baseband processorand/or the application processor, includes means for receiving a parameter indicating that two codeword transmission for PDSCH transmissions is enabled by a network node, means for receiving a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant from the network node, and means for receiving each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block from the network node. In one configuration, the multi-PDSCH grant includes a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. In one configuration, the indication corresponds to a combination of the MCS and a pattern of RV indications included in the single DCI. In one configuration, each RV indication in the pattern of RV indications corresponds to a value of 1. In one configuration, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. In one configuration, the pattern of RV indications includes an alternating pattern of RV indications. In one configuration, the MCS in the combination is 26. In one configuration, the means for receiving each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, the at least one processor is further configured to receive a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant. The means may be the multi-PDSCH grant configuration componentof the apparatusconfigured to perform the functions recited by the means. As described supra, the apparatusmay include the TX processor, the RX processor, and the controller/processor. As such, in one configuration, the means may be the TX processor, the RX processor, and/or the controller/processorconfigured to perform the functions recited by the means.

11 FIG. 1100 1102 1102 1102 1110 1130 1140 199 1102 1110 1110 1130 1110 1130 1140 1130 1130 1140 1140 1110 1112 1112 1112 1110 1114 1118 1110 1130 1130 1132 1132 1132 1130 1134 1138 1130 1140 1140 1142 1142 1142 1140 1144 1146 1180 1148 1140 104 1112 1132 1142 1114 1134 1144 1112 1132 1142 is a diagramillustrating an example of a hardware implementation for a network entity. The network entitymay be a BS, a component of a BS, or may implement BS functionality. The network entitymay include at least one of a CU, a DU, or an RU. For example, depending on the layer functionality handled by the multi-PDSCH grant configuring component, the network entitymay include the CU; both the CUand the DU; each of the CU, the DU, and the RU; the DU; both the DUand the RU; or the RU. The CUmay include a CU processor. The CU processormay include on-chip memory′. In some aspects, the CUmay further include additional memory modulesand a communications interface. The CUcommunicates with the DUthrough a midhaul link, such as an F1 interface. The DUmay include a DU processor. The DU processormay include on-chip memory′. In some aspects, the DUmay further include additional memory modulesand a communications interface. The DUcommunicates with the RUthrough a fronthaul link. The RUmay include an RU processor. The RU processormay include on-chip memory′. In some aspects, the RUmay further include additional memory modules, one or more transceivers, antennas, and a communications interface. The RUcommunicates with the UE. The on-chip memory′,′,′ and the additional memory modules,,may each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. Each of the processors,,is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

199 199 1110 1130 1140 199 1102 1102 199 1102 1102 316 370 375 316 370 375 As discussed supra, the multi-PDSCH grant configuring componentis configured to transmit a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, transmit a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and transmit each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. The multi-PDSCH grant configuring componentmay be within one or more processors of one or more of the CU, DU, and the RU. The multi-PDSCH grant configuring componentmay be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entitymay include a variety of components configured for various functions. In one configuration, the network entityincludes means for transmitting a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, means for transmitting a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and means for transmitting each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. In one configuration, the multi-PDSCH grant includes a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. In one configuration, the indication corresponds to a combination of the MCS and a pattern of RV indications included in the single DCI. In one configuration, each RV indication in the pattern of RV indications corresponds to a value of 1. In one configuration, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. In one configuration, the pattern of RV indications includes an alternating pattern of RV indications. In one configuration, the MCS in the combination is 26. In one configuration, the means for transmitting each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, the at least one processor is further configured to transmit a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant for the UE. The means may be the multi-PDSCH grant configuring componentof the network entityconfigured to perform the functions recited by the means. As described supra, the network entitymay include the TX processor, the RX processor, and the controller/processor. As such, in one configuration, the means may be the TX processor, the RX processor, and/or the controller/processorconfigured to perform the functions recited by the means.

12 FIG. 1200 1260 1260 190 1260 1212 1212 1212 1260 1214 1260 1280 1202 1212 1214 1212 is a diagramillustrating an example of a hardware implementation for a network entity. In one example, the network entitymay be within the core network. The network entitymay include a network processor. The network processormay include on-chip memory′. In some aspects, the network entitymay further include additional memory modules. The network entitycommunicates via the network interfacedirectly (e.g., backhaul link) or indirectly (e.g., through a RIC) with the CU. The on-chip memory′ and the additional memory modulesmay each be considered a computer-readable medium/memory. Each computer-readable medium/memory may be non-transitory. The processoris responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the corresponding processor(s) causes the processor(s) to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the processor(s) when executing software.

199 199 1212 199 1260 1260 199 1260 As discussed supra, the multi-PDSCH grant configuring componentis configured to transmit a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, transmit a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and transmit each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. The multi-PDSCH grant configuring componentmay be within the processor. The multi-PDSCH grant configuring componentmay be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entitymay include a variety of components configured for various functions. In one configuration, the network entityincludes means for transmitting a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, means for transmitting a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and means for transmitting each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. In one configuration, the multi-PDSCH grant includes a MCS (e.g., a common MCS) that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. In one configuration, the indication corresponds to a combination of the MCS and a pattern of RV indications included in the single DCI. In one configuration, each RV indication in the pattern of RV indications corresponds to a value of 1. In one configuration, the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. In one configuration, the pattern of RV indications includes an alternating pattern of RV indications. In one configuration, the MCS in the combination is 26. In one configuration, the means for transmitting each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, the at least one processor is further configured to transmit a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant for the UE. The means may be the multi-PDSCH grant configuring componentof the network entityconfigured to perform the functions recited by the means.

13 FIG. 1300 1310 1320 1320 1325 1315 1305 1310 1330 1330 1340 1340 1304 1304 1340 is a diagramillustrating another example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUsthat can communicate directly with a core networkvia a backhaul link, or indirectly with the core networkthrough one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC)via an E2 link, or a Non-Real Time (Non-RT) RICassociated with a Service Management and Orchestration (SMO) Framework, or both). A CUmay communicate with one or more DUsvia respective midhaul links, such as an F1 interface. The DUsmay communicate with one or more RUsvia respective fronthaul links. The RUsmay communicate with respective UEsvia one or more radio frequency (RF) access links. In some implementations, the UEmay be simultaneously served by multiple RUs.

1310 1330 1340 1325 1315 1305 Each of the units, i.e., the CUS, the DUs, the RUs, as well as the Near-RT RICs, the Non-RT RICs, and the SMO Framework, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

1310 1310 1310 1310 1310 1330 In some aspects, the CUmay host one or more higher layer control functions. Such control functions can include RRC, PDCP, SDAP, or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU. The CUmay be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CUcan be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CUcan be implemented to communicate with the DU, as necessary, for network control and signaling.

1330 1340 1330 1330 1330 1310 The DUmay correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs. In some aspects, the DUmay host one or more of an RLC layer, a MAC layer, and one or more high PHY layers (such as modules for FEC encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DUmay further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU, or with the control functions hosted by the CU.

1340 1340 1330 1340 1304 1340 1330 1330 1310 Lower-layer functionality can be implemented by one or more RUs. In some deployments, an RU, controlled by a DU, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing FFT, iFFT, digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s)can be implemented to handle over the air (OTA) communication with one or more UEs. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)can be controlled by the corresponding DU. In some scenarios, this configuration can enable the DU(s)and the CUto be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

1305 1305 1305 1390 1310 1330 1340 1325 1305 1311 1305 1340 1305 1315 1305 The SMO Frameworkmay be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Frameworkmay be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Frameworkmay be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud)) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs, DUs, RUsand Near-RT RICs. In some implementations, the SMO Frameworkcan communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB), via an O1 interface. Additionally, in some implementations, the SMO Frameworkcan communicate directly with one or more RUsvia an O1 interface. The SMO Frameworkalso may include a Non-RT RICconfigured to support functionality of the SMO Framework.

1315 1325 1315 1325 1325 1310 1330 1325 The Non-RT RICmay be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI)/machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC. The Non-RT RICmay be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC. The Near-RT RICmay be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs, one or more DUs, or both, as well as an O-eNB, with the Near-RT RIC.

1325 1315 1325 1305 1315 1315 1325 1315 1305 1 In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC, the Non-RT RICmay receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RICand may be received at the SMO Frameworkor the Non-RT RICfrom non-network data sources or from network functions. In some examples, the Non-RT RICor the Near-RT RICmay be configured to tune RAN behavior or performance. For example, the Non-RT RICmay monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework(such as reconfiguration via) or via creation of RAN management policies (such as A1 policies).

1310 1330 1340 1302 1302 1310 1330 1340 1302 1302 1320 1304 1302 1340 1304 1304 1340 1340 1304 1302 1304 At least one of the CU, the DU, and the RUmay be referred to as a base station. Accordingly, a base stationmay include one or more of the CU, the DU, and the RU(each component indicated with dotted lines to signify that each component may or may not be included in the base station). The base stationprovides an access point to the core networkfor a UE. The base stationsmay include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include HeNBs, which may provide service to a restricted group known as a CSG. The communication links between the RUsand the UEsmay include UL (also referred to as reverse link) transmissions from a UEto an RUand/or DL (also referred to as forward link) transmissions from an RUto a UE. The communication links may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations/UEsmay use spectrum up to Y MHz (e.g., 5, 130, 135, 20, 1300, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a PCell and a secondary component carrier may be referred to as a SCell.

1304 1358 1358 1358 Certain UEsmay communicate with each other using device-to-device (D2D) communication link. The D2D communication linkmay use the DL/UL WWAN spectrum. The D2D communication linkmay use one or more sidelink channels, such as a PSBCH, a PSDCH, a PSSCH, and a PSCCH. D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

1350 1304 1354 1304 1350 The wireless communications system may further include a Wi-Fi APin communication with UEs(also referred to as Wi-Fi stations (STAs)) via communication link, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs/APmay perform a CCA prior to communicating in order to determine whether the channel is available.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHZ) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the ITU as a “millimeter wave” band.

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

With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

1302 1304 1302 1382 1304 1304 1302 1304 1384 1302 1302 1304 1302 1304 1302 1304 1302 1304 The base stationand the UEmay each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base stationmay transmit a beamformed signalto the UEin one or more transmit directions. The UEmay receive the beamformed signal from the base stationin one or more receive directions. The UEmay also transmit a beamformed signalto the base stationin one or more transmit directions. The base stationmay receive the beamformed signal from the UEin one or more receive directions. The base station/UEmay perform beam training to determine the best receive and transmit directions for each of the base station/UE. The transmit and receive directions for the base stationmay or may not be the same. The transmit and receive directions for the UEmay or may not be the same.

1302 1302 The base stationmay include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a BSS, an ESS, a TRP, network node, network entity, network equipment, or some other suitable terminology. The base stationcan be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).

1320 1361 1362 1363 1364 1368 1361 1304 1320 1361 1362 1363 1364 1368 1365 1366 1368 1365 1366 1365 1366 1365 1366 1304 1361 1304 1304 1304 1304 1302 1370 The core networkmay include an AMF, a SMF, a UPF, a UDM, one or more location servers, and other functional entities. The AMFis the control node that processes the signaling between the UEsand the core network. The AMFsupports registration management, connection management, mobility management, and other functions. The SMFsupports session management and other functions. The UPFsupports packet routing, packet forwarding, and other functions. The UDMsupports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location serversare illustrated as including a Gateway Mobile Location Center (GMLC)and a Location Management Function (LMF). However, generally, the one or more location serversmay include one or more location/positioning servers, which may include one or more of the GMLC, the LMF, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLCand the LMFsupport UE location services. The GMLCprovides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMFreceives measurements and assistance information from the NG-RAN and the UEvia the AMFto compute the position of the UE. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE. Positioning the UEmay involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UEand/or the serving base station. The signals measured may be based on one or more of a satellite positioning system (SPS)(e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.

1304 1304 1304 Examples of UEsinclude a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEsmay be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UEmay also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

13 FIG. 1304 198 1302 199 Referring again to, in certain aspects, the UEmay include a multi-PDSCH grant configuration componentconfigured to receive a parameter indicating that two codeword transmission for PDSCH transmissions is enabled by a network node, receive a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant from the network node; and receive each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block from the network node. In certain aspects, the base stationmay include a multi-PDSCH grant configuring componentconfigured to transmit a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, transmit a multi-PDSCH grant in a single DCI comprising an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant for the UE, and transmit each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

According to the aspects of the current disclosure, the network node may configure the UE with more than one codeword transmission for each PDSCH and transmit DCI including multi-PDSCH grant scheduling multiple PDSCHs. The DCI may include an indication that a second TB is disabled for each PDSCH indicated by the multi-PDSCH grant. The UE may receive the DCI including multi-PDSCH grant scheduling multiple PDSCHs, the DCI including the indication that the second TB is disabled for each PDSCH indicated by the multi-PDSCH grant, and understand that the multiple PDSCHs scheduled by the multi-PDSCH grant. In one aspect, the indication may include a combination of the MCS and the RV vector (or RVID) value of the associated multiple PDSCHs. In another aspect, the indication may include a pattern of the RV vector (or RVID) values of associated multiple PDSCHs.

It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically 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 A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

Aspect 1 is a method of wireless communication at a UE, including receiving a parameter indicating that two codeword transmission for PDSCH transmissions is enabled by a network node, receiving a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH indicated by the multi-PDSCH grant from the network node, and receiving each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block from the network node. Aspect 2 is the method of aspect 1, where the multi-PDSCH grant includes a MCS that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. Aspect 3 is the method of aspect 2, where the indication corresponds to a combination of the MCS and a pattern of RV indications included in the single DCI. Aspect 4 is the method of aspect 3, where each RV indication in the pattern of RV indications corresponds to a value of 1. Aspect 5 is the method of any of aspects 3 to 4, where the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. Aspect 6 is the method of any of aspects 3 to 5, where the pattern of RV indications includes an alternating pattern of RV indications. Aspect 7 is the method of any of aspects 3 to 6, where the MCS in the combination is 26. Aspect 8 is the method of any of aspects 1 to 7, where, receiving each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, the at least one processor further includes receiving a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant. Aspect 9 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to implement any of aspects 1 to 8, further including a transceiver coupled to the at least one processor. Aspect 10 is an apparatus for wireless communication including means for implementing any of aspects 1 to 8. Aspect 11 is a non-transitory computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 8. Aspect 12 is a method of wireless communication at a network node, including transmitting a parameter indicating that two codeword transmission for PDSCH transmissions is enabled for a UE, transmitting a multi-PDSCH grant in a single DCI including an indication that a second transport block is disabled for each PDSCH in the multi-PDSCH grant for the UE, and transmitting each PDSCH indicated by the multi-PDSCH grant based on a disablement of the second transport block for the UE. Aspect 13 is the method of aspect 12, where the multi-PDSCH grant includes a MCS that is common to each PDSCH indicated by the multi-PDSCH grant and an individual RV indication for each PDSCH indicated by the multi-PDSCH grant. Aspect 14 is the method of aspect 13, where the indication corresponds to a combination of the MCS and a pattern of RV indications included in the single DCI. Aspect 15 is the method of aspect 14, where each RV indication in the pattern of RV indications corresponds to a value of 1. Aspect 16 is the method of any of aspects 14 and 15, where the pattern of RV indications includes two RV indications of any two adjacent PDSCHs being different from each other. Aspect 17 is the method of any of aspects 14 to 16, where the pattern of RV indications includes an alternating pattern of RV indications. Aspect 18 is the method of any of aspects 14 to 17, where the MCS in the combination is 26. Aspect 19 is the method of any of aspects 12 to 18, where, transmitting each PDSCH indicated by the multi-PDSCH grant based on the disablement of the second transport block, the at least one processor further includes transmitting a single transport block mapped to a first codeword of each PDSCH indicated in the multi-PDSCH grant for the UE. Aspect 20 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to implement any of aspects 12 to 19, further including a transceiver coupled to the at least one processor. Aspect 21 is an apparatus for wireless communication including means for implementing any of aspects 12 to 19. Aspect 22 is a non-transitory computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 12 to 19. The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.