Configuration of SDM PUSCH and handover between different modes

Abstract

The present disclosure provides an apparatus, a method, and a computer program product for transmitting an SDM PUSCH. An example method can include receiving, from a second network entity, downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH) transmission, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. The example method can also include mapping at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or radio resource control (RRC) configuration. The example method can also include sending the at least one TB or CW to the second network entity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 810,273, filed on June 30, 2022, entitled “CONFIGURATIONS AND SWITCHING BETWEEN DIFFERENT MODES OF SDM PUSCH,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to a wireless communication system with a spatial division multiplexing (SDM) physical uplink shared channel (PUSCH). Background Art

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

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

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus at a first network entity, such as a user equipment (UE), are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a layer set and a second portion associated with a second subset of layers within the layer set. The memory and the at least one processor coupled to the memory may be further configured to map at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or a radio resource control (RRC) configuration. The memory and the at least one processor coupled to the memory may be further configured to send the at least one TB or CW to the second network entity.

[0008] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus at a first network entity, such as a base station, are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to send a DCI scheduling a PUSCH transmission including a first part and a second part to a second network entity, wherein the PUSCH transmission includes a first part associated with a first subset of layers within a layer set and a second part associated with a second subset of layers within the layer set. The memory and the at least one processor coupled to the memory may be further configured to receive at least one TB or CW from the second network entity, wherein the at least one TB or CW is mapped to the first part or the second part based on the DCI or RRC configuration.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0016] Figure 4 is a diagram illustrating an example in which a base station communicates with a UE.

[0017] Figure 5 is a diagram illustrating example communications between a UE and a network entity.

[0018] Figure 6 is a diagram illustrating an example mapping pattern for PUSCH repetition.

[0019] Figure 7 is a diagram illustrating an example mapping pattern for PUSCH repetition.

[0020] Figure 8 is a diagram illustrating an example first mode of processing SDM PUSCH transmission.

[0021] Fig. 9 is a diagram illustrating an example of a second mode of processing SDM PUSCH transmission.

[0022] Fig.10 is a diagram illustrating example communications between a UE and a network entity.

[0023] Fig.11 is a diagram illustrating an example of a third mode of processing SDM PUSCH transmission.

[0024] Fig.12 is a diagram illustrating an example of a fourth mode of processing SDM PUSCH transmission.

[0025] Fig.13 is a flow chart of a wireless communication method.

[0026] Fig.14 is a flow chart of a wireless communication method.

[0027] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0028] Fig.16 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0029] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0030] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0032] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these 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.

[0033] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) The various techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0034] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using 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) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0035] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between 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 in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0036] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0037] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both). The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0039] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU110 may 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 specific implementations, CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0040] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending on a functional split (such as that defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0041] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0042] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0043] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125.

[0044] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0045] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may 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). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified 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 (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0050] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0051] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each base station / UE in the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0052] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (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 a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0053] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement results and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, 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 one or more of other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0055] Reference again Figure 1 , in some aspects, the UE 104 may include a PUSCH component 198. In some aspects, the PUSCH component 198 may be configured to receive a DCI scheduling a PUSCH transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component 198 may be further configured to map at least one TB or CW to the first portion or the second portion based on the DCI or the RRC configuration. In some aspects, the PUSCH component 198 may be further configured to send the at least one TB or CW to the second network entity.

[0056] In certain aspects, the base station 102 may include a PUSCH component 199. In some aspects, the PUSCH component 199 may be configured to send a DCI to a second network entity scheduling a PUSCH transmission including a first portion and a second portion, wherein the PUSCH transmission includes the first portion associated with a first subset of layers within the set of layers and the second portion associated with a second subset of layers within the set of layers. In some aspects, the PUSCH component 199 may be further configured to receive at least one TB or CW from the second network entity, wherein the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI or the RRC configuration.

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

[0058] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0059] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0060] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling).

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

[0062]

[0063] Table 1

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

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

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

[0067] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A 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 a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

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

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

[0070] Figure 3370 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements 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 / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery 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.

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

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

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

[0074] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer 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.

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

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

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

[0078] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The PUSCH component 198 is used to perform various aspects.

[0079] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The PUSCH component 199 is used to perform various aspects.

[0080] Figure 4 4 is a diagram 400 illustrating communication between a base station 402 and a UE 404. Figure 4 , the base station 402 may send a beamformed signal to the UE 404 in one or more directions 402a, 402b, 402c, 402d, 402e, 402f, 402g, 402h. The UE 404 may receive the beamformed signal from the base station 402 in one or more reception directions 404a, 404b, 404c, 404d. The UE 404 may also send a beamformed signal to the base station 402 in one or more directions 404a-404d. The base station 402 may receive the beamformed signal from the UE 404 in one or more reception directions 402a-402h. The base station 402 / UE 404 may perform beam training to determine the best reception direction and transmission direction for each of the base stations 402 / UEs 404. The transmission direction and the reception direction for the base station 402 may be the same or may be different. The transmission direction and the reception direction for the UE 404 may be the same or may be different.

[0081] In response to different conditions, UE 404 may determine to switch beams, for example, between beams 402a-402h. The beam at UE 404 may be used for reception of downlink communications and / or transmission of uplink communications. In some examples, base station 402 may transmit a transmission that triggers beam switching of UE 404. For example, base station 402 may indicate a transmission configuration indication (TCI) state change, and in response, UE 404 may switch to a new beam for a new TCI state of base station 402. In some cases, the UE may receive a signal from a base station that is configured to trigger a transmission configuration indication (TCI) state change via, for example, a MAC control element (CE) command. The TCI state change may enable the UE to find the best UE receive beam corresponding to the TCI state from the base station and switch to such a beam. Switching beams may allow an enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver communicate using the same configured beam set.

[0082] Base station 402 and UE 404 may each include multiple transmit receive points (TRPs). Each TRP may include different RF modules with shared hardware and / or software controllers. Each TRP may perform separate baseband processing. Each TRP may include different antenna panels or different antenna element sets.

[0083] A set of time and frequency resources that can be used for one or more transmissions of an SRS may be referred to as an "SRS resource set". In some communication systems, the applicability of an SRS resource set for an SRS resource set may be configured by a higher layer parameter, such as a "purpose" associated with the SRS resource set, such as in an SRS-ResourceSet parameter. For example, the purpose may be configured as one of beam management, codebook, non-codebook, antenna switching, etc. Each SRS resource set may be configured with one or more (such as up to 16) SRS resources. Each SRS resource set may be aperiodic, semi-persistent, or periodic.

[0084] In some wireless communication systems, two types of PUSCH transmissions may be supported. The first type may be referred to as codebook-based transmission. For codebook-based transmission, the UE may be configured with a set of SRS resources with "Purpose" set to "Codebook". For example, up to 4 SRS resources in the set may be configured for the UE. Each SRS resource may be a radio resource control (RRC) configured with multiple ports (such as one or more ports). The SRS Resource Indicator (SRI) field in the UL DCI for scheduling PUSCH may indicate an SRS resource. The number of ports configured for the indicated SRS resource may determine the number of antenna ports used for PUSCH. PUSCH may be transmitted using the same spatial domain filter (which may be otherwise referred to as a "beam") as the indicated SRS resource. The number of layers (i.e., rank) or the transmitted precoding matrix indicator (TPMI) (e.g., for a predecoder) for the scheduled PUSCH may be determined based on a separate DCI field "precoding information and number of layers".

[0085] For non-codebook based transmissions, the UE may be configured with one SRS resource set with "Purpose" set to "Non-Codebook". For example, up to 4 SRS resources in the set may be configured for the UE. Each SRS resource may be an RRC configured with one port. The SRI field in the UL DCI that schedules the PUSCH may indicate one or more SRS resources. The number of indicated SRS resources may determine the rank (i.e., number of layers) used for the scheduled PUSCH. The PUSCH may be transmitted using the same pre-decoder and the same spatial domain filter (i.e., beam) as the indicated SRS resource.

[0086] In some aspects, multiple TRPs or multiple panels can be used to enhance reliability and robustness for PUSCH. For example, if a link using a first TRP is blocked and one repetition of PUSCH fails to be received, another repetition can be received and decoded by another TRP. Thus, with multiple TRPs, transmit diversity is increased and PUSCH transmissions can be more reliable. Repetitions can also be referred to as transmit opportunities.

[0087] PUSCH transmissions may be sent in one or more repetitions (which may also be referred to herein as "parts") using different types of repetitions. For different PUSCH repetitions corresponding to the same TB, the repetitions are sent in different time slots in type A repetitions, and in different mini-slots in type B repetitions. The number of repetitions may be RRC configured or may be dynamically indicated, such as by utilizing the time domain resource assignment (TDRA) field of the DCI. In some wireless communication systems, all repetitions may be sent using the same beam. For example, the SRI field of the DCI may apply to all repetitions. The SRI may be a field in the UL DCI that determines the beam or power control parameters for the PUSCH by pointing to one or more SRS resources within an SRS resource set.

[0088] In some other wireless communication systems, different PUSCH repetitions are intended to be received at different TRPs, panels or antennas at a base station, and these repetitions can use the same beam or different beams. For example, two repetition sets can be provided, each of which includes its own beam associated with its own power control parameters. Each repetition set may include one or more repetitions. The two repetition sets may correspond to two SRS resource sets, which may include a DCI that can indicate two beams and two power control parameter sets by indicating one or more SRS resources within each of the two SRS resource sets. Various aspects of this document enable the association between two SRS resource sets and two PUSCH repetition sets.

[0089] Figure 5 5 is a diagram 500 illustrating communication between a UE 502 and a network entity 504 (eg, a base station). Figure 5, the network entity 504 may configure the UE 502 with at least two SRS resource sets 506. In some aspects, the network entity 504 may not support dynamic order switching. In some aspects, the SRS resource set 506 may include an SRS resource set identifier (ID) that may be represented by the srs-ResourceSetID field in the SRS-ResourceSet parameter. In some aspects, the SRS resource set 506 may include a parameter representing the order, such as an SRS-ResourceSetOrder parameter. The network entity 504 may be a network node. The network node may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0090] In some aspects, the network entity 504 may send the DCI 508 to the UE 502. In some aspects, a dynamic order may be supported by the network entity 504. In some aspects, the DCI 508 may include one or more bits, such as two bits, to indicate the order of the SRS resource sets used in the SRS resource sets 506.

[0091] UE 502 may send one or more repetitions of a PUSCH to network entity 504, the one or more repetitions such as a first PUSCH repetition 510, a second PUSCH repetition 512, a third PUSCH repetition 514, and a fourth PUSCH repetition 516. In some aspects, within two SRS resource sets in SRS resource sets 506, the SRS resource set with the lowest ID may correspond to a first set of repetitions (the first set of repetitions may be the repetition set that occurs first in time), and the SRS resource set with the second lowest ID corresponds to a second set of repetitions. For example, a first PUSCH repetition set may include a first PUSCH repetition 510 and a second PUSCH repetition 512, and a second PUSCH repetition set may include a third PUSCH repetition 514 and a fourth PUSCH repetition 516. The first PUSCH repetition set may correspond to the SRS resource set with the lowest ID.

[0092] In some aspects, within two SRS resource sets in SRS resource sets 506, the SRS resource set with the highest ID may correspond to the first set of repetitions, and the SRS resource set with the second highest ID may correspond to the second set of repetitions. For example, the first PUSCH repetition set may include the first PUSCH repetition 510 and the second PUSCH repetition 512, and the second PUSCH repetition set may include the third PUSCH repetition 514 and the fourth PUSCH repetition 516. The first PUSCH repetition set may correspond to the SRS resource set with the highest ID. In some aspects, the SRS resource sets associated with the first PUSCH repetition 510, the second PUSCH repetition 512, the third PUSCH repetition 514, and the fourth PUSCH repetition 516 may be determined based on a parameter representing an order.

[0093] In some aspects, if the network entity 504 supports dynamic order switching and the DCI 508 includes one or more bits indicating the order, the one or more bits may represent a DCI code point that may correspond to the order. For example, the DCI code point may be 0, 1, 2, or 3 and may be associated with the order 1, 2, 12, and 21. Table 2 illustrates an example correspondence between a set of DCI code points and a set of correspondences indicating the order of PUSCH transmission.

[0094]

[0095] Table 2

[0096] As illustrated in Table 2, the SRS resource set indicator may be based on whether 2 SRS resource sets corresponding to the DCI format are configured.

[0097] Figure 6 600 is a diagram illustrating an example cyclic mapping pattern for PUSCH repetition. Figure 6 , DCI 602 may schedule four PUSCH repetitions: PUSCH repetition 604, PUSCH repetition 606, PUSCH repetition 608, and PUSCH repetition 610. For cyclic beam mapping, the first PUSCH repetition 604 and the third PUSCH repetition 608 may be associated with the first beam and the first set of power control parameters. The second PUSCH repetition 606 and the fourth PUSCH repetition 610 may be associated with the second beam and the second set of power control parameters. This cyclic mapping pattern may be applicable to both type A repetitions and type B repetitions.

[0098] Figure 7 700 is a diagram illustrating an example mapping pattern for PUSCH repetition. Figure 7As illustrated in , DCI 702 scheduling may schedule four PUSCH repetitions. The four PUSCH repetitions may be arranged differently based on the code point in DCI 702. For example, based on code point 0, the four PUSCH repetitions may be PUSCH repetition 704A, PUSCH repetition 706A, PUSCH repetition 708A, and PUSCH repetition 710A, which may all be based on the first beam and the first set of power control parameters (and for the first TRP). Based on code point 1, the four PUSCH repetitions may be PUSCH repetition 704B, PUSCH repetition 706B, PUSCH repetition 708B, and PUSCH repetition 710B, which may all be based on the second beam and the second set of power control parameters (and for the second TRP). Based on code point 2, the four PUSCH repetitions may be PUSCH repetition 704C, PUSCH repetition 706C, PUSCH repetition 708C, and PUSCH repetition 710C, wherein PUSCH repetition 704C and PUSCH repetition 708C may be based on a first beam and a first set of power control parameters (and for a first TRP), and PUSCH repetition 706C and PUSCH repetition 710C may be based on a second beam and a second set of power control parameters (and for a second TRP). Based on code point 3, the four PUSCH repetitions may be PUSCH repetition 704D, PUSCH repetition 706D, PUSCH repetition 708D, and PUSCH repetition 710D, wherein PUSCH repetition 706D and PUSCH repetition 710D may be based on a first beam and a first set of power control parameters (and for a first TRP), and PUSCH repetition 704D and PUSCH repetition 708D may be based on a second beam and a second set of power control parameters (and for a second TRP).

[0099] In some aspects, a PUSCH transmission may be based on SDM and may be associated with multiple DM-RS port sets, which may in turn be associated with multiple MIMO layer sets in multiple panels at the UE, respectively. PUSCH transmissions may be transmitted based on multiple MIMO layer sets in multiple panels at the UE using different transmit beams, pre-decoders, and power control parameters. For example, a first portion of a PUSCH transmission may be transmitted to a first TRP of a base station via a first panel via a first MIMO layer set associated with a first DM-RS port set using a first transmit beam (and associated TCI state). A second portion of a PUSCH transmission may be transmitted to a second TRP of a base station via a second panel via a second MIMO layer set associated with a second DM-RS port set using a second transmit beam (and associated TCI state). Such a PUSCH transmission may be based on one TB and one CW or based on more than one TB and more than one CW. A TB may be a payload of data transferred between a medium access control (MAC) layer and a PHY layer for transmitting data in a TB. The PHY layer may convert the TB to CW by appending a cyclic redundancy check (CRC) to the TB (which may also be referred to as "scrambling"), segmenting the TB into multiple code blocks of a configured size (e.g., segmenting into code blocks between 40 bits and 6144 bits) or padding to a configured size (e.g., padding to 40 bits with 0s if the TB is less than 40 bits), then processing each code block with a turbo decoder and reassembling the code blocks into CW. Such processing after appending the CRC may also be collectively referred to as coding and modulation.

[0100] As used herein, the term "SDM PUSCH" may refer to a PUSCH transmission including different parts based on SDM.As used herein, the terms "repetition" and "part" may be used interchangeably to refer to repetitions of a PUSCH. Figure 8 8 is a diagram illustrating a first mode (Mode 1) of processing SDM PUSCH transmissions. Figure 8, to send a PUSCH transmission, after encoding, scrambling, and modulation at 804, a single TB 802 may be used to generate a CW 806. The CW 806 may be mapped (at 808) to a first MIMO layer set 810A associated with a first SRI / TPMI associated with a first panel of the UE (e.g., as indicated by the DCI), and may then be sent to a first TRP 820A of a base station 820 using a transmit beam associated with the first MIMO layer set 810A. The CW 806 may also be mapped (at 808) to a second MIMO layer set 810B associated with a second SRI / TPMI associated with a second panel of the UE (e.g., as indicated by the DCI), and may then be sent to a second TRP 820B of the base station 820 using a transmit beam associated with the second MIMO layer set 810B. Transmitting different portions of a PUSCH transmission corresponding to transmissions using different layer sets associated with different panels and beams, respectively, based on the same TB and the same CW may be a first mode of handling SDM PUSCH transmissions.A single NDI, a single RV, and a single MCS may be used for TB 802 and CW 806.

[0101] Fig. 9 900 is a diagram illustrating an example of a second mode of processing SDM PUSCH transmissions. Fig. 9, to send a PUSCH transmission, a first portion of the PUSCH transmission may correspond to a first TB 902A, which may be used to generate a CW 906A after encoding, scrambling, and modulation at 904A. The CW 906A may be mapped (at 908) to a first MIMO layer set 910A associated with a first SRI / TPMI associated with a first panel of the UE (e.g., as indicated by the DCI), and may then be transmitted to a first TRP 920A of a base station 920 using a transmit beam associated with the first MIMO layer set 910A. A second portion of the PUSCH transmission may correspond to a second TB 902B, which may be used to generate a CW 906B after encoding, scrambling, and modulation at 904B. CW 906B may be mapped (at 908) to a second MIMO layer set 910B associated with a second SRI / TPMI associated with a second panel of the UE (e.g., as indicated by the DCI), and may then be transmitted to a second TRP 920B of a base station 920 using a transmit beam associated with the second MIMO layer set 910B. TB 902A may be associated with a first modulation and coding scheme (MCS), a first redundancy version (RV), and a first new data indicator (NDI). TB 902B may be associated with a second MCS, a second RV, and a second NDI. The first MCS, the first RV, and the first NDI may be represented by a DCI in one or more fields separate from one or more fields representing the second MCS, the second RV, and the second NDI. The value of the first MCS may be the same or different from the second MCS. The value of the first NDI may be the same or different from the second NDI. The value of the first RV may be the same or different from the second RV. Sending different portions of the PUSCH transmission based on different TBs and different CWs corresponding to transmissions using different layer sets associated with different panels and beams, respectively, may be a second mode (Mode 2) of processing SDM PUSCH transmissions.

[0102] The first mode for processing SDM PUSCH transmissions and the second mode for processing SDM PUSCH transmissions may provide different advantages, which may be situational. For example, the first mode may be more suitable for reliability / diversity because the TBs are mapped to layers from two sets, which means that if one beam is blocked, the TBs can still be decoded from the layers mapped to the other beam. The second mode may be more suitable for capacity increase because different MCSs can be used to adapt the decoding rate and modulation order to the effective signal to interference and noise ratio (SINR) for each layer set / each beam. The aspects provided herein may enable the UE to distinguish and determine how to process SDM PUSCH transmissions. The aspects provided herein may also enable the UE to use different CWs and TBs associated with different NDIs, RVs, and MCSs, regardless of whether the UE is operating in sTRP or mTRP. The aspects provided herein may also provide additional modes that can more efficiently process SDM PUSCH transmissions.

[0103] Fig.10 1000 is a diagram illustrating an example communication between a UE 1002 and a network entity 1004 (e.g., a base station). The network entity 1004 may be a network node. The network node may be implemented as a converged base station, a decomposed base station, an IAB node, a relay node, a sidelink node, etc. The network entity may be implemented in a converged or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0104] like Fig.101007, the network entity 1004 may configure the UE 1002 with at least two SRS resource sets 1006 that may be configured based on the RRC configuration 1007. In some aspects, each of the SRS resource sets 1006 may include an SRS resource set ID that may be represented by the srs-ResourceSetID field in the SRS-ResourceSet parameter. In some aspects, the network entity 1004 may send a DCI 1008 to the UE 1002. In some aspects, the DCI 1008 may include one or more bits, such as two bits (e.g., the code points illustrated in Table 2), to indicate the order of different parts / transmissions in the PUSCH transmission 1014. The DCI 1008 may schedule the SDM PUSCH. In some aspects, the DCI 1008 may include at least two MIMO layer sets, which may be associated with at least two DM-RS port sets that are respectively associated with at least two transmit beams (and TCI states) or two SRS resource sets. Based on the DCI or RRC configuration 1007, the UE 1002 may determine (at 1012) whether to process the SDM PUSCH based on: 1) one TB and CW are mapped to two MIMO layer sets (a first mode for processing the SDM PUSCH), 2) two corresponding TBs and CWs are mapped to corresponding layer sets (a second mode for processing the SDM PUSCH), or 3) other ways of mapping TBs and CWs to MIMO layers (other modes for processing the SDM PUSCH). In some aspects, after processing the SDM PUSCH, the UE 1002 may send a PUSCH transmission 1014 to the network entity 1004.

[0105] In some aspects, the RRC configuration 1007 may be based on a bandwidth part (BWP) or a serving cell. In some aspects, the RRC configuration 1007 may configure one mode for processing the SDM PUSCH, and the UE 1002 may process the SDM PUSCH accordingly at 1012. In some aspects, the RRC configuration 1007 may configure more than one mode for processing the SDM PUSCH, and the UE 1002 may use additional signaling to determine which mode to use when processing the SDM PUSCH at 1012.

[0106] In some aspects, the DCI 1008 may explicitly or implicitly indicate a first mode of processing the SDM PUSCH or a second mode of processing the SDM PUSCH. In some aspects, the DCI 1008 may include two MCS / NDI / RV fields, the two MCS / NDI / RV fields including a first MCS / RV / NDI field set and a second MCS / RV / NDI field set associated with two TBs including a first TB and a second TB. The DCI may dynamically disable one of the TBs (e.g., in the DCI 1008 or in another DCI) based on the MCS / RV / NDI value for the corresponding TB being set to one or more configuration values. If both the first MCS / RV / NDI field set and the second MCS / RV / NDI field set associated with the TB are not disabled, the UE 1002 may process the SDM PUSCH based on the second mode. If the first MCS / RV / NDI field set and the second MCS / RV / NDI field set are not disabled, the UE 1002 may process the SDM PUSCH based on the first mode.

[0107] In some aspects, an SRS resource set indicator (such as a code point) in the DCI 1008 may be used to indicate a first mode for processing SDM PUSCH and a second mode for processing SDM PUSCH. An example is illustrated in Table 3 below:

[0108]

[0109] Table 3

[0110] As illustrated in Table 3, for mode 2, the SRS resource set indicator may also indicate whether the layer of the first TB or the second TB is mapped to the first SRS resource set or the second SRS resource set. As illustrated in Table 3, code point 0 and code point 1 may indicate that the PUSCH is based on sTRP without SDM. Code point 2 may indicate the use of a first mode of processing SDM PUSCH, in which a single TB is mapped to different parts of the SDM PUSCH based on different MIMO layer sets for different TRPs (and additionally indicates the association between the SRS resource set and the MIMO layer set). Code point 3 may indicate the use of a first mode of processing SDM PUSCH, in which a single TB is mapped to different parts of the SDM PUSCH based on different MIMO layer sets for different TRPs (and additionally indicates the association between the SRS resource set and the MIMO layer set). Code point 4 may indicate the use of a second mode of processing SDM PUSCH, in which different TBs are mapped to different parts of the SDM PUSCH based on different MIMO layer sets for different TRPs (and additionally indicates the association between the SRS resource set and the MIMO layer set). Code point 5 may indicate the use of a second mode of processing SDM PUSCH, where different TBs are mapped to different parts of the SDM PUSCH based on different MIMO layer sets for different TRPs (and additionally indicating the association between SRS resource sets and MIMO layer sets). Similarly, code points may be used to indicate other modes of processing SDM PUSCH.

[0111] In some aspects, the UE 1002 may determine at 1012 whether to use the first mode of processing SDM PUSCH, the second mode of processing SDM PUSCH, or other modes of processing SDM PUSCH based on the number of layers in the first set (which may be indicated by the first SRI field or TPMI field in the DCI 1008 and may be represented by r1) and the number of layers in the second set (which may be indicated by the second SRI field or TPMI field in the DCI 1008 and may be represented by r2). For example, if (r1, r2) = (1, 1), (2, 1), (1, 2), mode 1 may be used. For (r1, r2) = (2, 2), mode 2 may be used.

[0112] In some aspects, if the PUSCH is scheduled using a configured number (such as 4) or fewer layers and the DCI 1008 includes two MCS / RV / NDI field sets, the UE 1002 can determine whether one CW and one TB are mapped to all MIMO layers, or two CWs and two TBs are mapped to two MIMO layer sets based on whether the PUSCH is associated with one SRS resource set or one TCI state or two SRS resource sets or two TCI states. In some aspects, if two to four layers are used for PUSCH, mode 2 can be used (and two TBs or two CWs can be used). There can be two MIMO layer sets (and associated TCI states) associated with two SRS resource sets / two beams. In some aspects, when all MIMO layers used to send PUSCH are associated with one SRS resource set and one TCI state, all MIMO layers can be mapped to one TB and one CW. In such aspects, the DCI 1008 can still include two NDI / RV / MCS field sets. In some aspects, whether the PUSCH is associated with one SRS resource set or one TCI state or two SRS resource sets or two TCI states may be determined based on the SRS resource set indicator in the DCI 1008. If the PUSCH is associated with one SRS resource set or one TCI state, the UE 1002 may ignore the second NDI / RV / MCS field set.

[0113] In some aspects, the UE 1002 may employ a third mode of processing SDM PUSCH transmissions. Fig.11 1100 is a diagram illustrating an example of a third mode of processing SDM PUSCH transmissions. Fig.11, to transmit a PUSCH transmission, a single TB 1102A may be encoded at 1104. After encoding at 1102A, at 1105A, rate matching may be performed based on a first RV; scrambling and modulation may also be performed at 1105A. Based on the processing at 1105A, a CW 1106A may be generated (based on TB 1102A and the first RV). At 1105B, rate matching may be performed based on a second RV; scrambling and modulation may also be performed at 1105B. Based on the processing at 1105B, a CW 1106B may be generated (based on TB 1102A and the second RV). CW 1106A may be mapped (at 1108) to a first MIMO layer set 1110A associated with a first SRI / TPMI associated with a first panel of the UE (e.g., as indicated by the DCI), and may then be transmitted to a first TRP 1120A of a base station 1120 using a transmit beam associated with the first MIMO layer set 1110A. CW 1106B may be mapped (at 1108) to a second MIMO layer set 1110B associated with a second SRI / TPMI associated with a second panel of the UE (e.g., as indicated by the DCI), and may then be transmitted to a second TRP 1120B of the base station 1120 using a transmit beam associated with the second MIMO layer set 1110B.

[0114] In other words, the PUSCH may include one TB that may be encoded and then rate matched using the first RV and the second RV, respectively, to create a first repetition and a second repetition of the TB, respectively. The modulation symbols of the first repetition may be mapped to a first set of MIMO layers (associated with a first SRS resource set / first TCI state / first precoding), and the modulation symbols of the second repetition may be mapped to a second set of MIMO layers (associated with a second SRS resource set / second TCI state / second precoding). Thus, each repetition may be self-decodable because the rate matching is separate, and if one of the beams is blocked, the performance may be better than the first mode.

[0115] In some aspects, CW 1106A and CW 1106B are associated with a single NDI and MCS and may be associated with a first RV and a second RV, respectively. In some aspects, the first RV and the second RV may be indicated by two RV fields in the DCI 1008. In some aspects, one RV field in the DCI 1008 may indicate that the first RV and the second RV may be obtained based on an RV offset that may be independent of the DCI 1008 (such as configured in the RRC configuration 1007 or configured without signaling from the network entity 1004).

[0116] Fig.121200 is a diagram illustrating an example of a fourth mode of processing SDM PUSCH transmissions. Fig.12 , to send a PUSCH transmission, a first portion of the PUSCH transmission may correspond to a first TB 1202A, which may be used to generate a CW 1206A after encoding, scrambling, and modulation at 1204A. The CW 1206A may be mapped (at 1208) to at least one layer in a first MIMO layer set 1210A associated with a first SRI / TPMI associated with a first panel of the UE (e.g., as indicated by the DCI), and at least one layer in a second MIMO layer set 1210B associated with a second SRI / TPMI associated with a second panel of the UE (e.g., as indicated by the DCI). The CW 1206A may then be sent to a first TRP 1220A of a base station 1220 using a transmit beam associated with the first MIMO layer set 1210A, and may be sent to a second TRP 1220B of the base station 1220 using a transmit beam associated with the second MIMO layer set 1210B. The second portion of the PUSCH transmission may correspond to a second TB 1202B, which may be used to generate CW 1206B after encoding, scrambling, and modulation at 1204B. CW 1206B may be mapped (at 1208) to at least one layer in a first MIMO layer set 1210A associated with a first SRI / TPMI associated with a first panel of the UE (e.g., as indicated by the DCI), and at least one layer in a second MIMO layer set 1210B associated with a second SRI / TPMI associated with a second panel of the UE (e.g., as indicated by the DCI). CW 1206B may then be transmitted to a first TRP 1220A of a base station 1220 using a transmit beam associated with the first MIMO layer set 1210A, and may be transmitted to a second TRP 1220B of the base station 1220 using a transmit beam associated with the second MIMO layer set 1210B. This mode can enhance the reliability of each of the two TBs (or at least one of the two TBs) because the layers of the TBs are mapped to layers from two beams, and the two TBs / CWs can be scheduled with different MCSs.

[0117] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, UE 1002; device 1504).

[0118] At 1302, the first network entity may receive DCI scheduling a PUSCH transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. For example, UE 1002 may receive DCI 1008 scheduling a PUSCH transmission from a second network entity (e.g., 1004), wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, 1302 may be performed by PUSCH component 198. In some aspects, the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication may be associated with a first TB or a first CW associated with a first subset of layers, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication may be associated with a second TB or a second CW associated with a second subset of layers.

[0119] At 1304, the first network entity may map at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration. For example, the UE 1002 may map at least one TB or CW to the first portion or the second portion (e.g., at 1012) based on the DCI or RRC configuration 1007. In some aspects, 1304 may be performed by the PUSCH component 198. In some aspects, to map at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration, the first network entity may map at least one TB or CW to the first portion or the second portion based on the RRC configuration, and the RRC configuration may be associated with a bandwidth part (BWP) or a serving cell. In some aspects, to map at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration, the first network entity may map at least one TB or CW to the first portion or the second portion based on the DCI. In some aspects, the DCI includes an SRS resource set indicator, and wherein the first network entity may map at least one TB or CW to the first portion or the second portion based on the SRS resource set indicator. In some aspects, the SRS resource set indicator indicates a first SRS resource set associated with a first subset of layers and a second SRS resource set associated with a second subset of layers. In some aspects, to map at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration, the first network entity may map at least one TB or CW to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers. In some aspects, in order to map at least one TB or CW to the first part or the second part based on a DCI or RRC configuration, the first network entity may map at least one TB or CW to the first part or the second part based on the number of SRS resource sets associated with the PUSCH transmission, and wherein the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, wherein the first indication may be associated with a first TB or a first CW associated with a first subset of layers, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication may be associated with a second TB or a second CW associated with a second subset of layers. In some aspects, the number of SRS resource sets associated with the PUSCH transmission may be one, and wherein the DCI also includes a disabling indication, wherein the disabling indication may be configured to cause the first network entity to avoid using the first MCS, the first NDI, or the first RV associated with the first indication, or to avoid using the second MCS, the second NDI, or the second RV associated with the second indication.In some aspects, the at least one TB or CW includes a TB, a first CW and a second CW, and wherein the first CW may be based on rate matching a TB using a first RV, and the second CW may be based on rate matching a TB using a second RV. In some aspects, the first RV may be indicated by a DCI, and wherein the second RV may be indicated by the DCI or configured based on an RV offset relative to the first RV, and the RV offset may be independent of the DCI. For example, based on the DCI not including a field indicating the RV offset, the RV offset may be independent of the DCI. The DCI may include a field indicating the first RV, without a field indicating the second RV and without a field indicating the RV offset. In some aspects, the RV offset may be configured without base station signaling. In some aspects, the RV offset may be configured based on an RRC configuration (such as RRC configuration 1007 or a different RRC configuration).

[0120] At 1306, the first network entity may send at least one TB or CW to the second network entity. For example, UE 1002 may send at least one TB or CW (e.g., PUSCH transmission 1014) to the second network entity (e.g., 1004). In some aspects, 1306 may be performed by PUSCH component 198. In some aspects, the DCI also includes a disabling indication, wherein the disabling indication may be configured to cause the first network entity to avoid using a second MCS, a second NDI, or a second RV associated with the second indication, and wherein the at least one TB or CW corresponds to a first TB or a first CW based on the disabling indication. In some aspects, the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW may be associated with at least one first layer in a first subset of layers and at least one second layer in a second subset of layers.

[0121] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, base station 102, network entity 1004, network entity 1502, network entity 1602).

[0122] At 1402, the first network entity may send a DCI to the second network entity scheduling a PUSCH transmission including a first portion and a second portion, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. For example, the network entity 1004 may send a DCI 1008 to the second network entity (e.g., UE 1002) scheduling a PUSCH transmission including a first portion and a second portion, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within the set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, 1402 may be performed by the PUSCH component 199. In some aspects, the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, wherein the first indication may be associated with a first TB or a first CW associated with the first subset of layers, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication may be associated with a second TB or a second CW associated with the second subset of layers. In some aspects, the DCI also includes a disabling indication, wherein the disabling indication indicates avoiding the use of a second MCS, a second NDI, or a second RV associated with a second indication, and wherein the at least one TB or CW corresponds to a first TB or a first CW based on the disabling indication. In some aspects, the DCI includes an SRS resource set indicator, and at least one TB or CW may be mapped to a first part or a second part based on the SRS resource set indicator. In some aspects, the SRS resource set indicator indicates a first SRS resource set associated with a first subset of layers and a second SRS resource set associated with a second subset of layers. In some aspects, the first RV may be indicated by the DCI, and wherein the second RV may be indicated by the DCI or configured based on an RV offset relative to the first RV, and the RV offset may be independent of the DCI. For example, based on the DCI not including a field indicating an RV offset, the RV offset may be independent of the DCI. The DCI may include a field indicating the first RV, without a field indicating the second RV and without a field indicating the RV offset. In some aspects, the RV offset may be configured without base station signaling. In some aspects, the RV offset may be configured based on an RRC configuration, such as RRC configuration 1007 or a different RRC configuration.

[0123] At 1404, the first network entity may receive at least one TB or CW from the second network entity, wherein the at least one TB or CW is mapped to the first part or the second part based on a DCI or an RRC configuration. For example, the network entity 1004 may receive at least one TB or CW (e.g., a PUSCH transmission 1014) from the second network entity, wherein the at least one TB or CW is mapped to the first part or the second part based on a DCI or an RRC configuration 1007. In some aspects, 1404 may be performed by the PUSCH component 199. In some aspects, the at least one TB or CW may be mapped to the first part or the second part based on an RRC configuration, and wherein the RRC configuration may be associated with a BWP or a serving cell. In some aspects, the at least one TB or CW may be mapped to the first part or the second part based on a DCI. In some aspects, the at least one TB or CW may be mapped to the first part or the second part based on a first number of layers associated with a first subset of layers and a second number of layers associated with a second subset of layers. In some aspects, at least one TB or CW may be mapped to a first portion or a second portion based on a number of SRS resource sets associated with a PUSCH transmission, and wherein the DCI includes a first indication associated with a first MCS, a first NDI, or a first RV, wherein the first indication may be associated with a first TB or a first CW associated with a first subset of layers, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication may be associated with a second TB or a second CW associated with a second subset of layers. In some aspects, the number of SRS resource sets associated with a PUSCH transmission may be one, and wherein the DCI includes a disabling indication indicating to avoid using a first MCS, a first NDI, or a first RV associated with the first indication, or to avoid using a second MCS, a second NDI, or a second RV associated with the second indication. In some aspects, the at least one TB or CW includes a TB, a first CW, and a second CW, and wherein the first CW may be rate matched to a TB based on using a first RV, and the second CW may be rate matched to a TB based on using a second RV. In some aspects, the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW may be associated with at least one first layer in a first subset of layers and at least one second layer in a second subset of layers.

[0124] Fig.151500 is a diagram illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, a satellite system module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the satellite system module 1516 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1524 / application processor 1506, enables the cellular baseband processor 1524 / application processor 1506 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software. The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 1504 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1524 and / or the application processor 1506, and in another configuration, the device 1504 may be an entire UE (see, e.g., Figure 3 350) and includes additional modules of device 1504.

[0125] As discussed herein, the PUSCH component 198 may be configured to receive a DCI scheduling a PUSCH transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a layer set and a second portion associated with a second subset of layers within a layer set. In some aspects, the PUSCH component 198 may be further configured to map at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration. In some aspects, the PUSCH component 198 may be further configured to send at least one TB or CW to the second network entity. The PUSCH component 198 may be within the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. The PUSCH component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 1504 may include a variety of components configured for various functions. In one configuration, the apparatus 1504 (and specifically, the cellular baseband processor 1524 and / or the application processor 1506) includes a component for receiving a DCI scheduling a PUSCH transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers. In some aspects, the apparatus 1504 may also include a component for mapping at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration. In some aspects, the apparatus 1504 may also include a component for sending at least one TB or CW to the second network entity. In some aspects, the component for mapping at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration may include a component for mapping at least one TB or CW to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers. In some aspects, the means for mapping at least one TB or CW to the first portion or the second portion based on the DCI or RRC configuration may include means for mapping at least one TB or CW to the first portion or the second portion based on a sounding reference signal (SRS) resource set associated with the PUSCH transmission. These means may be the PUSCH component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described herein, the apparatus 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0126] Fig.16 1600 is a diagram illustrating an example of a hardware implementation of a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include a CU 1610; both the CU 1610 and the DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both the DU 1630 and the RU 1640; or the RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612'. In some aspects, the CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU 1610 communicates with DU 1630 via a midhaul link such as an F1 interface. DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include additional memory modules 1634 and communication interfaces 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include additional memory modules 1644, one or more transceivers 1646, antenna 1680, and communication interface 1648. RU 1640 communicates with UE 104. On-chip memory 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each processor in processors 1612, 1632, 1642 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0127] As discussed herein, the PUSCH component 199 may be configured to send a DCI scheduling a PUSCH transmission including a first portion and a second portion to a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a layer set and a second portion associated with a second subset of layers within a layer set. In some aspects, the PUSCH component 199 may be further configured to receive at least one TB or CW from the second network entity, wherein the at least one TB or CW may be mapped to the first portion or the second portion based on the DCI or RRC configuration. The PUSCH component 199 may be within one or more processors of one or more of the CU 1610, DU 1630, and RU 1640. The PUSCH component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above operations. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 includes a component for sending a DCI scheduling a PUSCH transmission including a first part and a second part to a second network entity, wherein the PUSCH transmission includes a first part associated with a first subset of layers within a layer set and a second part associated with a second subset of layers within the layer set. In some aspects, the network entity 1602 may also include a component for receiving at least one TB or CW from the second network entity, wherein the at least one TB or CW may be mapped to the first part or the second part based on the DCI or RRC configuration. These components may be a PUSCH component 199 of the network entity 1602 configured to perform the functions recited by the components. As described herein, the network entity 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the components may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the components.

[0128] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0129] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ... " and "at ... " do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ... ", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, 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 multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0130] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0132] Aspect 1 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: receive downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission from a second network entity, wherein the PUSCH transmission includes a first part associated with a first subset of layers within a layer set and a second part associated with a second subset of layers within the layer set; map at least one transport block (TB) or codeword (CW) to the first part or the second part based on the DCI or radio resource control (RRC) configuration; and send the at least one TB or CW to the second network entity.

[0133] Aspect 2 is a first network entity according to Aspect 1, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the RRC configuration, and wherein the RRC configuration is associated with a bandwidth part (BWP) or a service cell.

[0134] Aspect 3 is a first network entity according to any one of Aspects 1 to 2, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the DCI.

[0135] Aspect 4 is a first network entity according to any one of Aspects 1 to 3, wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

[0136] Aspect 5 is a first network entity according to any one of Aspects 1 to 4, wherein the DCI also includes a disabling indication, wherein the disabling indication is configured to cause the at least one processor to avoid using the second MCS, the second NDI or the second RV associated with the second indication, and wherein the at least one TB or CW corresponds to the first TB or the first CW based on the disabling indication.

[0137] Aspect 6 is a first network entity according to any one of Aspects 1 to 5, wherein the DCI includes a sounding reference signal (SRS) resource set indicator, and wherein the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the SRS resource set indicator.

[0138] Aspect 7 is a first network entity according to any one of aspects 1 to 6, wherein the SRS resource set indicator indicates a first SRS resource set associated with a first subset of the layers and a second SRS resource set associated with a second subset of the layers.

[0139] Aspect 8 is a first network entity according to any one of Aspects 1 to 7, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on a first number of layers associated with the first subset of the layers and a second number of layers associated with the second subset of the layers.

[0140] Aspect 9 is a first network entity according to any one of Aspects 1 to 8, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI) or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

[0141] Aspect 10 is a first network entity according to any one of Aspects 1 to 9, wherein the number of SRS resource sets associated with the PUSCH transmission is one, and wherein the DCI also includes a disabling indication, wherein the disabling indication is configured to cause the at least one processor to avoid using the first MCS, the first NDI or the first RV associated with the first indication, or to avoid using the second MCS, the second NDI or the second RV associated with the second indication.

[0142] Aspect 11 is a first network entity according to any one of Aspects 1 to 10, wherein the at least one TB or CW includes a TB, a first CW, and a second CW, and wherein the first CW is based on rate matching the one TB using a first redundancy version (RV), and the second CW is based on rate matching the one TB using the second RV.

[0143] Aspect 12 is a first network entity according to any one of Aspects 1 to 11, wherein the first RV is indicated by the DCI, and wherein the second RV is indicated by the DCI or is configured based on an RV offset relative to the first RV, and the RV offset is independent of the DCI.

[0144] Aspect 13 is a first network entity according to any one of Aspects 1 to 12, wherein the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW is associated with at least one first layer in the first subset of the layers and at least one second layer in the second subset of the layers.

[0145] Aspect 14 is a first network entity for wireless communication, the first network entity comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, wherein the at least one processor is configured to: send downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission to a second network entity, wherein the PUSCH transmission includes a first part associated with a first subset of layers within a layer set and a second part associated with a second subset of layers within the layer set; and receive at least one transport block (TB) or codeword (CW) from the second network entity, wherein the at least one TB or CW is mapped to the first part or the second part based on the DCI or radio resource control (RRC) configuration.

[0146] Aspect 15 is the first network entity according to aspect 14, wherein the at least one TB or CW is mapped to the first part or the second part based on the RRC configuration, and wherein the RRC configuration is associated with a bandwidth part (BWP) or a serving cell.

[0147] Aspect 16 is the first network entity according to any one of aspects 14 to 15, wherein the at least one TB or CW is mapped to the first part or the second part based on the DCI.

[0148] Aspect 17 is a first network entity according to any one of Aspects 14 to 16, wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

[0149] Aspect 18 is a first network entity according to any one of Aspects 14 to 17, wherein the DCI also includes a disabling indication, wherein the disabling indication indicates avoiding use of the second MCS, the second NDI or the second RV associated with the second indication, and wherein the at least one TB or CW corresponds to the first TB or the first CW based on the disabling indication.

[0150] Aspect 19 is a first network entity according to any one of aspects 14 to 18, wherein the DCI includes a sounding reference signal (SRS) resource set indicator, and the at least one TB or CW is mapped to a first PUSCH transmission or a second PUSCH transmission based on the SRS resource set indicator.

[0151] Aspect 20 is a first network entity according to any one of aspects 14 to 19, wherein the SRS resource set indicator indicates a first SRS resource set associated with a first subset of the layers and a second SRS resource set associated with a second subset of the layers.

[0152] Aspect 21 is a first network entity according to any one of Aspects 14 to 20, wherein the at least one TB or CW is mapped to the first part or the second part based on a first number of layers associated with the first subset of the layers and a second number of layers associated with the second subset of the layers.

[0153] Aspect 22 is a first network entity according to any one of Aspects 14 to 21, wherein the at least one TB or CW is mapped to the first part or the second part based on the number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI) or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

[0154] Aspect 23 is a first network entity according to any one of Aspects 14 to 22, wherein the number of SRS resource sets associated with the PUSCH transmission is one, and wherein the DCI includes a disabling indication, the disabling indication indicating avoiding use of the first MCS, the first NDI or the first RV associated with the first indication, or avoiding use of the second MCS, the second NDI or the second RV associated with the second indication.

[0155] Aspect 24 is a first network entity according to any one of Aspects 14 to 23, wherein the at least one TB or CW includes a TB, a first CW, and a second CW, and wherein the first CW is based on rate matching the one TB using a first redundancy version (RV), and the second CW is based on rate matching the one TB using the second RV.

[0156] Aspect 25 is a first network entity according to any one of Aspects 14 to 24, wherein the first RV is indicated by the DCI, and wherein the second RV is indicated by the DCI or is configured based on an RV offset relative to the first RV, and the RV offset is independent of the DCI.

[0157] Aspect 26 is a first network entity according to any one of Aspects 14 to 25, wherein the at least one TB or CW includes a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW is associated with at least one first layer in the first subset of the layers and at least one second layer in the second subset of the layers.

[0158] Aspect 27 is a wireless communication method for implementing any one of aspects 1 to 13.

[0159] Aspect 28 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 13.

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

[0161] Aspect 30 is a wireless communication method for implementing any one of aspects 14 to 26.

[0162] Aspect 31 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 14 to 26.

[0163] Aspect 32 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 14 to 26.

Claims

1. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; mapping at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or radio resource control (RRC) configuration; as well as The at least one TB or CW is sent to the second network entity.

2. The first network entity according to claim 1, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the RRC configuration, and wherein the RRC configuration is associated with a bandwidth part (BWP) or a serving cell.

3. The first network entity according to claim 1, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the DCI.

4. The first network entity according to claim 3, wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layers, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layers.

5. The first network entity according to claim 4, wherein the DCI also includes a disabling indication, wherein the disabling indication is configured to cause the at least one processor to avoid using the second MCS, the second NDI or the second RV associated with the second indication, and wherein the at least one TB or CW corresponds to the first TB or the first CW based on the disabling indication.

6. The first network entity of claim 3, wherein the DCI comprises a sounding reference signal (SRS) resource set indicator, and wherein the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the SRS resource set indicator. 7 . The first network entity of claim 6 , wherein the SRS resource set indicator indicates a first SRS resource set associated with a first subset of the layers and a second SRS resource set associated with a second subset of the layers.

8. The first network entity of claim 3, wherein, in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers.

9. A first network entity according to claim 1, wherein in order to map the at least one TB or CW to the first part or the second part based on the DCI or the RRC configuration, the at least one processor is configured to map the at least one TB or CW to the first part or the second part based on the number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI) or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

10. The first network entity of claim 9, wherein the number of SRS resource sets associated with the PUSCH transmission is one, and wherein the DCI further comprises a disabling indication, wherein the disabling indication is configured to cause the at least one processor to avoid using the first MCS, the first NDI or the first RV associated with the first indication, or to avoid using the second MCS, the second NDI or the second RV associated with the second indication.

11. The first network entity of claim 1 , wherein the at least one TB or CW comprises a TB, a first CW, and a second CW, and wherein the first CW is rate matched to the one TB based on using a first redundancy version (RV), and the second CW is rate matched to the one TB based on using the second RV.

12. The first network entity according to claim 11, wherein the first RV is indicated by the DCI, and wherein the second RV is indicated by the DCI or is configured based on an RV offset relative to the first RV, the RV offset being independent of the DCI.

13. The first network entity of claim 1 , wherein the at least one TB or CW comprises a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW is associated with at least one first layer in a first subset of the layers and at least one second layer in a second subset of the layers.

14. A first network entity for wireless communication, the first network entity comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: sending downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission to a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; as well as At least one transport block (TB) or codeword (CW) is received from the second network entity, wherein the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or radio resource control (RRC) configuration.

15. The first network entity of claim 14, wherein the at least one TB or CW is mapped to the first part or the second part based on the RRC configuration, and wherein the RRC configuration is associated with a bandwidth part (BWP) or a serving cell.

16. The first network entity of claim 14, wherein the at least one TB or CW is mapped to the first part or the second part based on the DCI.

17. A first network entity according to claim 16, wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

18. The first network entity according to claim 17, wherein the DCI further includes a disabling indication, wherein the disabling indication indicates avoiding use of the second MCS, the second NDI or the second RV associated with the second indication, and wherein the at least one TB or CW corresponds to the first TB or the first CW based on the disabling indication.

19. The first network entity of claim 16, wherein the DCI includes a sounding reference signal (SRS) resource set indicator, and the at least one TB or CW is mapped to the first PUSCH transmission or the second PUSCH transmission based on the SRS resource set indicator.

20. The first network entity of claim 19, wherein the SRS resource set indicator indicates a first SRS resource set associated with a first subset of the layers and a second SRS resource set associated with a second subset of the layers.

21. The first network entity of claim 16, wherein the at least one TB or CW is mapped to the first portion or the second portion based on a first number of layers associated with the first subset of layers and a second number of layers associated with the second subset of layers.

22. A first network entity according to claim 14, wherein the at least one TB or CW is mapped to the first part or the second part based on the number of sounding reference signal (SRS) resource sets associated with the PUSCH transmission, and wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI) or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

23. The first network entity of claim 22, wherein the number of SRS resource sets associated with the PUSCH transmission is one, and wherein the DCI includes a disabling indication indicating avoiding use of the first MCS, the first NDI or the first RV associated with the first indication, or avoiding use of the second MCS, the second NDI or the second RV associated with the second indication.

24. The first network entity of claim 14, wherein the at least one TB or CW comprises a TB, a first CW, and a second CW, and wherein the first CW is rate matched to the one TB based on using a first redundancy version (RV), and the second CW is rate matched to the one TB based on using the second RV.

25. The first network entity of claim 24, wherein the first RV is indicated by the DCI, and wherein the second RV is indicated by the DCI or is configured based on an RV offset relative to the first RV, the RV offset being independent of the DCI.

26. The first network entity of claim 14, wherein the at least one TB or CW comprises a first TB or a first CW and a second TB or a second CW, and wherein at least one of the first CW or the second CW is associated with at least one first layer in a first subset of the layers and at least one second layer in a second subset of the layers.

27. A method for wireless communication at a first network entity, the method comprising: receiving downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission from a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; mapping at least one transport block (TB) or codeword (CW) to the first portion or the second portion based on the DCI or radio resource control (RRC) configuration; as well as The at least one TB or CW is sent to the second network entity.

28. A method according to claim 27, wherein the DCI includes a first indication associated with a first modulation and coding scheme (MCS), a first new data indicator (NDI), or a first redundancy version (RV), wherein the first indication is associated with a first TB or a first CW associated with a first subset of the layer, wherein the DCI includes a second indication associated with a second MCS, a second NDI, or a second RV, wherein the second indication is associated with a second TB or a second CW associated with a second subset of the layer.

29. The method of claim 27, wherein the at least one TB or CW comprises a TB, a first CW, and a second CW, and wherein the first CW is rate matched to the one TB based on using a first redundancy version (RV), and the second CW is rate matched to the one TB based on using the second RV.

30. A method for wireless communication at a first network entity, the method comprising: sending downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) transmission to a second network entity, wherein the PUSCH transmission includes a first portion associated with a first subset of layers within a set of layers and a second portion associated with a second subset of layers within the set of layers; as well as At least one transport block (TB) or codeword (CW) is received from the second network entity, wherein the at least one TB or CW is mapped to the first portion or the second portion based on the DCI or radio resource control (RRC) configuration.

Images