UL codebook adaptation for PUSCH

Abstract

An apparatus, a method, and a computer program product for wireless communication are provided. An example method may include transmitting, for a second network entity, information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended one of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. The example method may also include receiving, from the second network entity in the uplink grant, information indicating a selected codebook of the recommended subset of codebooks. The example method may also include transmitting a PUSCH transmission based on the selected codebook and the uplink grant.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems with codebook based transmissions. Background Art

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

[0003] 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). 5GNR 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. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5GNR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] 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 at least one processor may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective predecoder. The at least one processor may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. The at least one processor may be configured to send a physical uplink shared channel (PUSCH) transmission based on the selected codebook and the uplink grant. The at least one processor may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets from the second network entity, wherein each respective codebook in the codebook set corresponds to a respective predecoder. The at least one processor may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant.The at least one processor may be configured to send a PUSCH transmission based on the selected codebook and the uplink grant.

[0006] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a first network entity, such as a network node (e.g., a network node such as a base station), are provided. The apparatus may include a memory and at least one processor, the at least one processor being coupled to the memory. The at least one processor may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective precoder. The at least one processor may be configured to send, in an uplink grant for the second network entity, information indicating the recommended codebook subset. The at least one processor may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant. The at least one processor may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. The at least one processor may be configured to send information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity. The at least one processor may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant.

[0007] 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 indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0014] Figure 4 is a diagram illustrating example communications between network entities and a UE.

[0015] Figure 5A is a diagram illustrating an example uniform linear array (ULA) antenna.

[0016] Figure 5B is a diagram illustrating an example uniform planar array (UPA) antenna.

[0017] Figure 6 is a diagram illustrating an example evaluation of different codebook candidates.

[0018] Figure 7 is a diagram illustrating an example evaluation of different codebook candidates.

[0019] Figure 8 is a diagram illustrating example communications between network entities and a UE.

[0020] Fig. 9 is a diagram illustrating example communications between network entities and a UE.

[0021] Fig.10 is a flow chart of a wireless communication method.

[0022] Fig.11 is a flow chart of a wireless communication method.

[0023] Fig.12 is a flow chart of a wireless communication method.

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

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

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

[0027] Fig.16 is a flow chart of a wireless communication method.

[0028] Fig.17 is a flow chart of a wireless communication method.

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

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

[0031] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in 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 cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

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

[0033] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which 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, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other 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, processes, functions, or any combination thereof.

[0034] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality 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 media that can be accessed by a computer. As an 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 media that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0035] 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, various 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 devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various 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 actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0036] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. 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 network equipment (such as a base station (BS)) or one or more units (or one or more components) performing 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 NRBS, 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.

[0037] 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 throughout 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).

[0038] 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. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0039] Figure 1 1 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.

[0040] Each of these units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired transmission medium or a 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 that is configured to receive a signal or send a signal to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive a signal on a wireless transmission medium, or to send a signal to one or more of the other units on a wireless transmission medium, or both.

[0041] 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), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 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 physically split 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.

[0042] 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 or demodulation, etc.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may also 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.

[0043] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the 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 functional splitting (such as lower layer functional splitting). 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 specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0044] 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 to instantiate 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 .

[0045] 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 communicate 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 the O-eNB with the near-RT RIC 125.

[0046] 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 creation of RAN management policies (such as A1 policies).

[0047] 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. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include 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).

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

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

[0050] 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, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0051] 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, so 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.

[0052] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, 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 herein, 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.

[0053] 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 the best transmit direction for each of the base station 102 / UE 104. The transmit direction and the receive direction of the base station 102 may be the same or may not be the same. The transmit direction and the receive direction of the UE 104 may be the same or may not be the same.

[0054] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a 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 and 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.

[0055] 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 the 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) or mobile positioning center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the 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.

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

[0057] Reference again Figure 1 , in some aspects, the UE 104 may include a codebook component 198. In some aspects, the codebook component 198 may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset in the one or more codebook subsets to a second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 198 may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. In some aspects, the codebook component 198 may be configured to send a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the codebook component 198 may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets from the second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, codebook component 198 may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. In some aspects, codebook component 198 may be configured to send a PUSCH transmission based on the selected codebook and the uplink grant.

[0058] In certain aspects, the base station 102 may include a codebook component 199. In some aspects, the codebook component 199 may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset in the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 199 may be configured to send information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, the codebook component 199 may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the codebook component 199 may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and a recommended codebook subset in the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, codebook component 199 may be configured to send information indicating the selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, codebook component 199 may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant.

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

[0060] 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, a first base station, a first device, a first device, a first computing system, a first set of one or more components, or a first processing entity, etc. configured to receive information; 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, or a second processing entity, etc.

[0061] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information or 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.

[0062] 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 can be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or time division duplex (TDD) (wherein 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-61. Slot formats 0 and 1 are full DL and full 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).

[0063] 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 equally sized subframes (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 normal or extended. For a normal 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.

[0064]

[0065]

[0066] Table 1: Parameter set, SCS and CP

[0067] 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. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / 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).

[0068] A resource grid may be used to represent a 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.

[0069] 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).

[0070] 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 identity. 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 not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0071] 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 teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

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

[0073] Figure 3370 is a block diagram of a base station 310 in an access network communicating with a UE 350. 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.

[0074] The transmit (TX) 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 separated into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined 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. The channel estimate from the channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition 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 for transmission using a corresponding spatial stream.

[0075] 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 combined 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 and reference signals on each subcarrier 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 base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0077] 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 delivery 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.

[0078] Channel estimates derived by the channel estimator 358 based on 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 facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0079] 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 respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0081] 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 codebook component 198 is used to perform various aspects.

[0082] 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 codebook component 199 is used to perform various aspects.

[0083] A set of time-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 (i.e., the purpose of an SRS resource set) for an SRS resource set may be configured (such as in an SRS-ResourceSet parameter) by a higher layer parameter (such as a "purpose" associated with the SRS resource set). For example, the purpose may be configured as one of beam management, codebook (e.g., for codebook-based transmissions), non-codebook (e.g., for non-codebook-based transmissions), or antenna switching. Each SRS resource set may be configured with one or more (such as up to 16) SRS resources. Each SRS resource set may be non-periodic, semi-persistent, or periodic.

[0084] In some wireless communication systems, two types of PUSCH transmissions may be supported: codebook-based transmissions and non-codebook-based transmissions. For non-codebook-based transmissions, the UE may be configured with an 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., the number of layers) used for the scheduled PUSCH. The PUSCH may be transmitted using the same pre-decoder as the indicated SRS resource and the same spatial domain filter (i.e., beam).

[0085] 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 that schedules the 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 the PUSCH. The 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". The TPMI may be used to indicate a precoding matrix. In some aspects, one TPMI may correspond to one precoding matrix. By sending the TPMI, the network may communicate with the UE regarding the selection of a particular precoding matrix for uplink transmissions. For example, for each PUSCH, in an UL grant, the network may signal the precoder to be used in the codebook based on the TPMI. In some aspects, for each PUSCH slot, in an UL grant, the network may signal the precoder to be used in the codebook based on the TPMI. In some aspects, the precoder may be different for each PUSCH slot.

[0086] In the codebook-based uplink shared channel transmission, the network selects the transmission rank and the corresponding precoding matrix, and notifies the device through the uplink scheduling grant. The term "configured codebook set" may refer to a set of configured precoding matrices (which may each correspond to a precoder) for precoding at the UE and the network (for example, it may also be referred to as "all codebooks", "entire codebooks" or "codebooks"). The configured codebook set may be configured without signaling between the UE and the network. Based on the various aspects provided herein, the configured codebook set may be divided into different codebook subsets. As used herein, the term "codebook subset" may refer to a subset of a "configured codebook set", which may be configured based on a division determined by the UE or the network, and is facilitated by signaling between the UE and the network. For example, the UE may determine how the configured codebook set may be divided into different subsets and the precoding matrices included in each subset, and then send information to the network indicating how the configured codebook set may be divided into different subsets and the precoding matrices included in each subset. As another example, the network may determine how the configured codebook set may be divided into different subsets and the precoding matrices included in each subset, and then send information to the UE indicating how the configured codebook set may be divided into different subsets and the precoding matrices included in each subset. As used herein, information indicating how the configured codebook set may be divided into different subsets and the precoding matrices included in each subset may be referred to as "division". As used herein, the term "recommended codebook subset" may refer to a specific codebook subset that may be recommended or selected (e.g., by a UE or a network) to be suitable for use by a UE. As used herein, the term "local antenna blocking" may refer to antenna blocking at a wireless location caused by humans, such as antenna blocking caused by hands, fingers, heads, or other parts of the human body. Local antenna blocking may depend on the way a human may be interacting with a wireless device. Precoding is a process of preprocessing a transmitted signal based on a precoder. Based on the precoder, the wireless device may apply weights to antenna elements, the weights including the amplitude and phase of each antenna element. The term "pre-decoder" may correspond to a "pre-decoding matrix" and may refer to a parameter used in the pre-decoding process and may be indicated as a "codebook candidate" or "codebook" in a configured codebook set. With the help of weights, the antenna can be electronically guided to radiate in the intended direction by suppressing power in other directions. In some wireless communication systems, the UE may support eight-transmission channel (8Tx) UL operation to support 4 layers and more per UE. To support such operations, a configured codebook set configured for the UE may include a large number of pre-decoders. As used herein, the term "uplink grant" may refer to information sent from a network node to a UE associated with an uplink transmission. An uplink grant may trigger an uplink transmission and may be associated with time-frequency resources used for the uplink transmission.

[0087] Figure 4 4 is a diagram 400 illustrating an example communication between a network entity 404 and a UE 402. The network entity 404 may be a network node. The network node may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (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 disaggregated 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.

[0088] like Figure 4 As illustrated, UE 402 may send one or more SRS 416 to network entity 404. Based on the one or more SRS 416, network entity 404 may perform channel estimation at 418. For example, network entity 404 may use one or more SRS 416 to estimate the quality of an uplink channel for a large bandwidth outside of a span assigned to UE 402. One or more SRS 416 may be generated using a basis sequence that may have small power variations in time and frequency, which may result in high power amplifier efficiency and comparable channel estimation quality for all frequency components. In some aspects, the one or more SRS 416 may be used to generate the one or more SRS 416. Represents an uplink channel. In some aspects, the uplink channel may be estimated based on Rx and Tx (e.g., Rx×Tx) associated with one or more SRS 416. After performing channel estimation at 418, in some aspects, at 420, the network entity 404 may select a precoding matrix and a corresponding TPMI from a configured codebook set.

[0089] After selecting the precoding matrix and corresponding TPMI at 420, the network entity 404 may send control information 422 to indicate the TPMI and rank information associated with the precoding matrix selected at 420 to the UE 402. In some aspects, the control information 422 may be included in an uplink grant associated with (e.g., triggering) a PUSCH transmission 424. Based on the TPMI and rank information, the UE 402 may identify the precoding matrix selected at 420 and use the selected precoding matrix to send the PUSCH transmission 424 to the network entity 404. In some aspects, the precoding matrix selected at 420 may be different for each PUSCH transmission or for each time slot.

[0090] Figure 5A 5 is a diagram illustrating an example uniform linear array (ULA) antenna. Figure 5A As illustrated, the ULA antenna may include antennas spaced apart (eg, equally spaced apart) along a straight line. Figure 5B 5 is a diagram 550 illustrating an example uniform planar array (UPA) antenna. Figure 5BAs illustrated, a UPA antenna may include individual antennas positioned along a rectangular grid to form a planar array.

[0091] Some example codebooks that may be configured at the UE and the network for UL are provided in Table 2 below:

[0092]

[0093]

[0094] Table 2

[0095] Parameters M, N, and P can be used to indicate different antenna layouts. Parameters O1 and O2 may correspond to the configuration of the sampling factor. Parameters i1 and i2 may correspond to feedback report values. As illustrated in Table 2, for a fully coherent structure, different antenna layouts may correspond to different codebooks. A UE with a fully coherent structure (e.g., a UE with the capability of a fully coherent structure) may be able to control and maintain the phase offset between antennas for PUSCH transmission to be the same as the phase offset between antennas for previous SRS transmission. In order to cover all potential types of UE antenna layouts, the signaling overhead for the TPMI indication sent for PUSCH may be large. The various aspects provided herein can reduce the signaling overhead for the TPMI indication sent for PUSCH by dividing the configured codebook set into codebook subsets. After the configured codebook set is divided into codebook subsets, the UE or network may recommend or select a recommended codebook subset and indicate the recommended codebook subset to other entities (network or UE). Therefore, the signaling overhead of TPMI indication can be reduced because the bits used to indicate the TPMI in the recommended codebook subset can be smaller than the bits used to indicate the TPMI in the configured codebook set. By reducing the signaling overhead of TPMI indication, the overall efficiency and data rate of the communication system can be improved.

[0096] Figure 6600 is a diagram illustrating an example evaluation of different codebook candidates. The Alt2-a predecoder can be a 2TX / 4TX codebook and / or an 8×1 antenna selection vector (as a starting point for a codebook designed for fully coherent / partially coherent / incoherent UEs). The Alt1-b predecoder can be a UL 2TX / 4TX codebook and / or an 8×1 antenna selection vector (as a starting point for a codebook designed for partially coherent / incoherent UEs) and a Type I codebook (as a starting point for a codebook designed for fully coherent UEs). The Type 1 codebook can be based on a defined codebook table, which may include entries with different antenna layouts, different numbers of antennas, or different sampling factors, etc. The Type 2 codebook can be based on one or more formulas. "TPUT" can be throughput, and "FWA" can be fixed wireless access. Edge TPUT can be the throughput at the edge of coverage. Center TPUT can be the throughput at the center of coverage. Figure 7 is a diagram 700 illustrating an example evaluation of different codebook candidates.

[0097] As described herein, for a certain UE, based on its antenna layout, it may be sufficient to use a specific codebook subset (e.g., a recommended codebook subset) from the entire configured codebook set. The configured codebook set may be divided into subsets based on a partition determined by the UE or the network. The number of bits used to signal a pre-decoder (e.g., by indicating a TPMI associated with the pre-decoder) may be reduced accordingly.

[0098] In some aspects, the UE may determine a partitioning of a configured codebook set. Figure 8 is a diagram 800 illustrating example communications between a network entity 804 and a UE 802 .

[0099] The network entity 804 may be a network node. The network node may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (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 disaggregated 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.

[0100] like Figure 8As illustrated, the UE 802 may determine the codebook partition and the recommended codebook subset based on the antenna layout of the UE at 804. In some aspects, the UE 802 may further determine the codebook partition and the recommended codebook subset based on the local antenna blocking of the UE, the power consumption of the UE, or the DL channel measurement of the UE (assuming DL / UL channel reciprocity) at 804. In some aspects, the UE 802 may determine the codebook partition and the recommended codebook subset based on other parameters at 804. In some aspects, the codebook partition determined at 804 may be an initial codebook partition that may be updated later by the network entity 804 or the UE 802. In some aspects, the initial codebook partition may be determined based on the antenna layout of the UE. In some aspects, the initial codebook partition may be reported to the network entity 804 as part of the capability information associated with the UE 802, which may also include a coherence report (reporting whether the UE 802 is fully coherent, partially coherent, or incoherent), and may be reported via radio resource control (RRC) signaling.

[0101] In some aspects, after determining the codebook partition and the recommended codebook subset at 804, the UE 802 may send information indicating the codebook partition 806 and information indicating the recommended codebook subset 808 to the network entity 804 (e.g., via a medium access control (MAC) control element (MAC-CE), RRC signaling, or control information). In some aspects, Figure 8 As illustrated, based on the codebook partition 806, the configured codebook set 840 may be divided into a first subset 840A, a second subset 840B, a third subset 840C, and a fourth subset 840D. For example, the recommended codebook subset 808 may be the subset 840A.

[0102] like Figure 8 As illustrated, UE 802 may send one or more SRS 816 to network entity 804. Based on the one or more SRS 816, network entity 804 may perform channel estimation at 818. For example, network entity 804 may use one or more SRS 816 to estimate the quality of an uplink channel for a large bandwidth outside of a span assigned to UE 802. One or more SRS 816 may be generated using a basis sequence that may have small power variations in time and frequency, which may result in high power amplifier efficiency and comparable channel estimation quality for all frequency components. In some aspects, the one or more SRS 816 may be used to generate the one or more SRS 816. Represents an uplink channel. In some aspects, the uplink channel may be estimated based on Rx and Tx (e.g., Rx×Tx) associated with one or more SRS 816. After performing channel estimation at 818, in some aspects, at 820, the network entity 804 may select a precoding matrix and a corresponding TPMI from the recommended codebook subset 808. In some aspects, the precoding matrix selected at 820 may be different for each PUSCH transmission or for each time slot.

[0103] After selecting the precoding matrix and the corresponding TPMI from the recommended codebook subset 808 at 820, the network entity 804 may send control information 822 to indicate the TPMI and rank information associated with the precoding matrix selected at 820 to the UE 802. In some aspects, the control information 822 may be included in an uplink grant associated with (e.g., triggering) a PUSCH transmission 824. Based on the TPMI and rank information, the UE 802 may identify the precoding matrix selected at 820 and send a PUSCH transmission 824 to the network entity 804 using the selected precoding matrix.

[0104] In some aspects, the partitioning of the configured codebook set may be periodically updated. For example, the partitioning of the configured codebook set may be periodically updated to adapt to changes in power consumption, local antenna obstruction, or channel estimation associated with the UE 802. In some aspects, the partitioning of the configured codebook set may be aperiodically updated based on changes in power consumption, local antenna obstruction, or channel estimation associated with the UE 802. Figure 8 As illustrated, to update the partitioning of the configured codebook set, the UE 802 may determine the codebook partitioning at 826 to update the codebook partitioning. In some aspects, the UE 802 may determine the codebook partitioning and the recommended codebook subset at 826 based on the local antenna blocking of the UE, the power consumption of the UE, or the DL channel measurement of the UE. After determining the codebook partitioning at 826, the UE 802 may send information indicating the updated codebook partitioning 830 to the network entity 804 (e.g., via MAC-CE, RRC signaling, or control information). In some aspects, as Figure 8 As illustrated, subset 840A, subset 840B, subset 840C, or subset 840D may be changed based on the updated codebook partition 830. In some aspects, the recommended subset may still be subset 840A.

[0105] In some aspects, the network entity 804 may determine the codebook partition and the recommended codebook subset at 828. In some aspects, the network entity 804 may determine the codebook partition and the recommended codebook subset at 828 based on PUSCH decoding results (e.g., including PUSCH decoding results associated with the PUSCH transmission 824 and one or more other PUSCH decoding results). In some aspects, as an example, based on a machine learning model, the network entity 804 may learn which pre-decoders may be suitable for the UE 802. In some aspects, the network entity 804 may determine the codebook partition and the recommended codebook subset based on one or more other parameters at 826. In some aspects, after determining the codebook partition and the recommended codebook subset at 828, the network entity 804 may send information indicating the updated codebook partition 832 to the UE 802 (e.g., via MAC-CE, RRC signaling, or control information). In some aspects, as Figure 8 As illustrated, subset 840A, subset 840B, subset 840C, or subset 840D may be changed based on codebook partition 832. In some aspects, the recommended subset may still be subset 840A.

[0106] In some aspects, the network entity 804 may further select a precoding matrix within the recommended subset based on the updated partition. In some aspects, the network entity 804 may send control information to indicate to the UE 802 the TPMI and rank information associated with the precoding matrix selected based on the updated partition. In some aspects, the control information may be included in an uplink grant associated with (e.g., triggering) a second PUSCH transmission. Based on the TPMI and rank information, the UE 802 may identify the selected precoding matrix and use the selected precoding matrix to send a second PUSCH transmission to the network entity.

[0107] Fig. 9 900 is a diagram illustrating an example communication between a network entity 904 and a UE 902. The network entity 904 may be a network node. The network node may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (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 disaggregated 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.

[0108] like Fig. 9As illustrated, the UE 902 may send one or more SRS 916 to the network entity 904. Based on the one or more SRS 916, the network entity 904 may perform channel estimation at 918. For example, the network entity 904 may use the one or more SRS 916 to estimate the quality of the uplink channel for a large bandwidth outside the span assigned to the UE 902. The one or more SRS 916 may be generated using a basis sequence that may have small power variations in time and frequency, which may result in high power amplifier efficiency and comparable channel estimation quality for all frequency components. In some aspects, the one or more SRS 916 may be used to generate the one or more SRS 916. Represents an uplink channel. In some aspects, the uplink channel may be estimated based on Rx and Tx (e.g., Rx×Tx) associated with one or more SRS 916. After performing channel estimation at 918, in some aspects, at 920, the network entity 904 may select a precoding matrix and a corresponding TPMI from a configured codebook set. In some aspects, the precoding matrix selected at 920 may be different for each PUSCH transmission or for each time slot.

[0109] After selecting the precoding matrix and the corresponding TPMI at 920, the network entity 904 may send control information 922 to indicate the TPMI and rank information associated with the precoding matrix selected at 920 to the UE 902. In some aspects, the control information 922 may be included in an uplink grant associated with (e.g., triggering) a PUSCH transmission 924. Based on the TPMI and the rank information, the UE 902 may identify the precoding matrix selected at 920 and send the PUSCH transmission 924 to the network entity 904 using the selected precoding matrix.

[0110] In some aspects, the network entity 904 may determine the codebook partition and the recommended codebook subset at 928. In some aspects, the network entity 904 may determine the codebook partition and the recommended codebook subset at 928 based on PUSCH decoding results (e.g., including PUSCH decoding results associated with the PUSCH transmission 924 and one or more other PUSCH decoding results). In some aspects, as an example, based on a machine learning model, the network entity 904 may learn which precoders may be suitable for the UE 902. In some aspects, the network entity 904 may determine the codebook partition and the recommended codebook subset at 928 based on one or more other parameters. In some aspects, after determining the codebook partition and the recommended codebook subset at 928, the network entity 904 may send information indicating the codebook partition 930 and information indicating the recommended codebook subset to the UE 802 (e.g., via MAC-CE, RRC signaling, or control information).

[0111] In some aspects, such as Fig. 9As illustrated, based on the codebook partition 930, the configured codebook set 940 may be divided into a first subset 940A, a second subset 940B, a third subset 940C, and a fourth subset 940D. For example, the recommended codebook subset may be the subset 940A.

[0112] In some aspects, at 932, the network entity 904 may select a precoding matrix and a corresponding TPMI from the recommended codebook subset based on the codebook partitioning 930. In some aspects, the precoding matrix selected at 932 may be different for each PUSCH transmission or for each slot.

[0113] After selecting a precoding matrix and a corresponding TPMI from the recommended codebook subset based on the codebook partition 930 at 932, the network entity 904 may send control information 934 to indicate to the UE 902 the TPMI and rank information associated with the precoding matrix selected at 820. In some aspects, the control information 934 may be included in an uplink grant associated with (e.g., triggering) a PUSCH transmission 936. Based on the TPMI and rank information, the UE 002 may identify the precoding matrix selected at 932 and use the selected precoding matrix to send the PUSCH transmission 936 to the network entity 904. In some aspects, the codebook partition may be updated periodically or aperiodically by the network entity 904. In some aspects, the network entity 904 may further select a precoding matrix within the recommended subset based on the updated partition. In some aspects, the network entity 904 may send control information to indicate to the UE 902 the TPMI and rank information associated with the precoding matrix selected based on the updated partition. In some aspects, the control information may be included in an uplink grant associated with (eg, triggering) the second PUSCH transmission.Based on the TPMI and the rank information, the UE 902 may identify the selected precoding matrix and use the selected precoding matrix to send the second PUSCH transmission to the network entity.

[0114] Fig.10 1000 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, UE 802; device 1804).

[0115] At 1010, the first network entity may send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset of the one or more codebook subsets to a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, UE 802 may send information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 806) and information indicating a recommended codebook subset of the one or more codebook subsets (e.g., 808) to a second network entity 804, wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1010 may be performed by codebook component 198.

[0116] At 1020, the first network entity may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant. For example, UE 802 may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant (e.g., 822). In some aspects, 1020 may be performed by codebook component 198.

[0117] At 1030, the first network entity may send a PUSCH transmission based on the selected codebook and the uplink grant. For example, UE 802 may send a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 824). In some aspects, 1030 may be performed by codebook component 198.

[0118] Fig.11 11 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, UE 802; device 1804).

[0119] At 1102, the first network entity may determine a partition of one or more codebook subsets and a recommended codebook subset. For example, UE 802 may determine the partition of the one or more codebook subsets and the recommended codebook subset at 804. In some aspects, 1102 may be performed by codebook component 198. In some aspects, the first network entity may determine the partition of the one or more codebook subsets and the recommended codebook subset based on an antenna layout associated with the first network entity. In some aspects, to determine the partition of the one or more codebook subsets and the recommended codebook subset, the at least one processor is configured to determine the partition of the one or more codebook subsets and the recommended codebook subset based on at least one of the following: local antenna blocking associated with the first network entity, power consumption associated with the first network entity, or channel measurement associated with the first network entity.

[0120] At 1110, the first network entity may send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset in the one or more codebook subsets to the second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, UE 802 may send information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 806) and information indicating a recommended codebook subset in the one or more codebook subsets (e.g., 808) to the second network entity 804, wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1110 may be performed by codebook component 198. In some aspects, to send the information indicating the partition, the first network entity may send uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the partition, wherein the RRC signaling also includes capability information associated with the first network entity. In some aspects, to send the information indicating the partition, the first network entity may send an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

[0121] At 1120, the first network entity may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant. For example, UE 802 may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant (e.g., 822). In some aspects, 1120 may be performed by codebook component 198.

[0122] At 1130, the first network entity may send a PUSCH transmission based on the selected codebook and the uplink grant. For example, UE 802 may send a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 824). In some aspects, 1130 may be performed by codebook component 198.

[0123] At 1132, the first network entity may determine a second partitioning of the one or more codebook subsets. For example, UE 802 may determine a second partitioning of the one or more codebook subsets at 826. In some aspects, 1132 may be performed by codebook component 198. In some aspects, the first network entity may determine the second partitioning of the one or more codebook subsets based on at least one of: a local antenna blockage associated with the first network entity, a power consumption associated with the first network entity, or a channel measurement associated with the first network entity.

[0124] At 1134, the first network entity may send information indicating the second partition to the second network entity. For example, UE 802 may send information indicating the second partition (e.g., 830) to the second network entity. In some aspects, 1134 may be performed by codebook component 198.

[0125] At 1142, the first network entity may receive information indicating a second partitioning of the one or more codebook subsets from the second network entity. For example, UE 802 may receive information indicating a second partitioning (e.g., 832) of the one or more codebook subsets from the second network entity. In some aspects, 1142 may be performed by codebook component 198. In some aspects, the second partitioning is based at least on a decoding result associated with the first PUSCH transmission.

[0126] At 1144, the first network entity may receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets from the second network entity based on the second partitioning. For example, UE 802 may receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets from the second network entity based on the second partitioning. In some aspects, 1144 may be performed by codebook component 198.

[0127] At 1150, the first network entity may send a second PUSCH transmission based on the second selected codebook. For example, UE 802 may send a second PUSCH transmission based on the second selected codebook. In some aspects, 1150 may be performed by codebook component 198.

[0128] Fig.12 1200 is a flow chart of a wireless communication method. The method may be performed by a network entity (eg, base station 102, network entity 804, network entity 1802, network entity 1902).

[0129] At 1210, the first network entity may receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity (e.g., UE 802) and information indicating a recommended codebook subset in the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, network entity 804 may receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity (e.g., 806) and information indicating a recommended codebook subset in the one or more codebook subsets (e.g., 808), wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1210 may be performed by codebook component 199.

[0130] At 1220, the first network entity may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity (e.g., 822). For example, network entity 804 may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity. In some aspects, 1220 may be performed by codebook component 199.

[0131] At 1230, the first network entity may receive a PUSCH transmission based on the selected codebook and the uplink grant. For example, the network entity 804 may receive a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 824). In some aspects, 1230 may be performed by the codebook component 199.

[0132] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a network entity (eg, base station 102, network entity 804, network entity 1802, network entity 1902).

[0133] At 1310, the first network entity may receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, network entity 804 may receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity (e.g., UE 804) (e.g., 806) and information indicating a recommended codebook subset of the one or more codebook subsets (e.g., 808), wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1310 may be performed by codebook component 199. In some aspects, the partition of the one or more codebook subsets and the recommended codebook subset are based on an antenna layout associated with the second network entity. In some aspects, the partitioning of the one or more codebook subsets and the recommended codebook subset are based on at least one of: local antenna blocking associated with the second network entity, power consumption associated with the second network entity, or channel measurements associated with the second network entity. In some aspects, to receive the information indicating the partitioning, the first network entity may receive an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partitioning. In some aspects, to receive the information indicating the partitioning, the first network entity may receive uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the partitioning, wherein the RRC signaling also includes capability information associated with the second network entity.

[0134] At 1320, the first network entity may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity (e.g., 822). For example, network entity 804 may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity. In some aspects, 1320 may be performed by codebook component 199.

[0135] At 1330, the first network entity may receive a PUSCH transmission based on the selected codebook and the uplink grant. For example, the network entity 804 may receive a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 824). In some aspects, 1330 may be performed by the codebook component 199.

[0136] At 1332, the first network entity may determine a second partitioning of the one or more codebook subsets. For example, the network entity 804 may determine (e.g., at 828) a second partitioning of the one or more codebook subsets. In some aspects, 1332 may be performed by the codebook component 199. In some aspects, to determine the second partitioning, the first network entity may determine the second partitioning based at least on a decoding result associated with the first PUSCH transmission and a machine learning model.

[0137] At 1334, the first network entity may send information indicating the second partitioning of the one or more codebook subsets. For example, the network entity 804 may send information indicating the second partitioning (e.g., 832) of the one or more codebook subsets. In some aspects, 1334 may be performed by the codebook component 199.

[0138] At 1342, the first network entity may receive information of a second partitioning of the one or more codebook subsets. For example, the network entity 804 may receive information indicating a second partitioning (e.g., 830) of the one or more codebook subsets. In some aspects, 1342 may be performed by the codebook component 199. In some aspects, the second partitioning is based on at least one of: a local antenna blockage associated with the second network entity, a power consumption associated with the second network entity, or a channel measurement associated with the second network entity.

[0139] At 1344, the first network entity may send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets to the second network entity based on the second partition. For example, network entity 804 may send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets to the second network entity based on the second partition. In some aspects, 1344 may be performed by codebook component 199.

[0140] At 1350, the first network entity may receive a second PUSCH transmission based on the second selected codebook. For example, network entity 804 may receive a second PUSCH transmission based on the second selected codebook. In some aspects, 1350 may be performed by codebook component 199.

[0141] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, UE 902; device 1804).

[0142] At 1410, the first network entity may receive information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets from a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, UE 902 may receive information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 930) and a recommended codebook subset in the one or more codebook subsets from a second network entity 904, wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1410 may be performed by codebook component 198.

[0143] At 1420, the first network entity may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant. For example, UE 902 may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant (e.g., 934). In some aspects, 1420 may be performed by codebook component 198.

[0144] At 1430, the first network entity may send a PUSCH transmission based on the selected codebook and the uplink grant. For example, UE 902 may send a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 936). In some aspects, 1430 may be performed by codebook component 198.

[0145] Fig.15 1500 is a flow chart of a wireless communication method. The method may be performed by a first network entity (eg, UE 104, UE 902; device 1804).

[0146] At 1510, the first network entity may receive information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets from a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, UE 902 may receive information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 930) and a recommended codebook subset in the one or more codebook subsets from a second network entity 904, wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1510 may be performed by codebook component 198. In some aspects, to receive the information indicating the partition, the first network entity may receive a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition. In some aspects, to receive the information indicating the partition, the first network entity may receive downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

[0147] At 1520, the first network entity may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant. For example, UE 902 may receive information indicating the selected codebook in the recommended codebook subset from the second network entity in an uplink grant (e.g., 934). In some aspects, 1520 may be performed by codebook component 198.

[0148] At 1530, the first network entity may send a PUSCH transmission based on the selected codebook and the uplink grant. For example, UE 902 may send a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 936). In some aspects, 1530 may be performed by codebook component 198.

[0149] At 1542, the first network entity may receive information of a second partitioning of the one or more codebook subsets. For example, the UE 902 may receive information indicating a second partitioning of the one or more codebook subsets. In some aspects, 1542 may be performed by the codebook component 198.

[0150] At 1544, the first network entity may receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning. For example, the UE 902 may receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning. In some aspects, 1544 may be performed by the codebook component 198.

[0151] At 1546, the first network entity may send a second PUSCH transmission based on the second selected codebook. For example, UE 902 may send a second PUSCH transmission based on the second selected codebook. In some aspects, 1546 may be performed by codebook component 198.

[0152] Fig.16 1600 is a flow chart of a wireless communication method. The method may be performed by a network entity (eg, base station 102, network entity 904, network entity 1802, network entity 1902).

[0153] At 1610, the first network entity may send information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, network entity 904 may send information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 930) and a recommended codebook subset in the one or more codebook subsets for a second network entity (e.g., UE 902), wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1610 may be performed by codebook component 199.

[0154] At 1620, the first network entity may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity. For example, network entity 904 may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity (e.g., 934). In some aspects, 1620 may be performed by codebook component 199.

[0155] At 1630, the first network entity may receive a PUSCH transmission based on the selected codebook and the uplink grant. For example, the network entity 904 may receive a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 936). In some aspects, 1630 may be performed by the codebook component 199.

[0156] Fig.17 1700 is a flow chart of a wireless communication method. The method may be performed by a network entity (eg, base station 102, network entity 904, network entity 1802, network entity 1902).

[0157] At 1702, the first network entity may determine the partition of the one or more codebook subsets. For example, the network entity 904 may determine (e.g., at 928) the partition of the one or more codebook subsets. In some aspects, 1702 may be performed by the codebook component 199.

[0158] At 1710, the first network entity may send information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. For example, network entity 904 may send information indicating a partition of one or more codebook subsets in a configured codebook set (e.g., 930) and a recommended codebook subset in the one or more codebook subsets for a second network entity (e.g., UE 902), wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, 1710 may be performed by codebook component 199. In some aspects, to send the information indicating the partition, the first network entity may send a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition. In some aspects, to send the information indicating the partition, the first network entity may send downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

[0159] At 1720, the first network entity may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity. For example, network entity 904 may send information indicating the selected codebook in the recommended codebook subset in an uplink grant to the second network entity (e.g., 934). In some aspects, 1720 may be performed by codebook component 199.

[0160] At 1730, the first network entity may receive a PUSCH transmission based on the selected codebook and the uplink grant. For example, the network entity 904 may receive a PUSCH transmission based on the selected codebook and the uplink grant (e.g., 936). In some aspects, 1730 may be performed by the codebook component 199.

[0161] At 1740, the first network entity may determine a second partitioning of the one or more codebook subsets. For example, the network entity 904 may determine a second partitioning of the one or more codebook subsets. In some aspects, 1740 may be performed by the codebook component 199. In some aspects, to determine the second partitioning, the first network entity may determine the second partitioning based at least on a PUSCH decoding result set, the PUSCH decoding result set including PUSCH decoding results associated with the PUSCH transmission.

[0162] At 1742, the first network entity may send information of a second partitioning of the one or more codebook subsets. For example, the network entity 904 may send information indicating a second partitioning of the one or more codebook subsets. In some aspects, 1742 may be performed by the codebook component 199.

[0163] At 1744, the first network entity may send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning. For example, the network entity 904 may send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning. In some aspects, 1744 may be performed by the codebook component 199.

[0164] At 1746, the first network entity may receive a second PUSCH transmission based on the second selected codebook. For example, the network entity 904 may receive a second PUSCH transmission based on the second selected codebook. In some aspects, 1746 may be performed by the codebook component 199.

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

[0166] In some aspects, the codebook component 198 may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset of the one or more codebook subsets to a second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 198 may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. In some aspects, the codebook component 198 may be configured to send a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the codebook component 198 may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset of the one or more codebook subsets from the second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 198 may be configured to receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. In some aspects, the codebook component 198 may be configured to send a PUSCH transmission based on the selected codebook and the uplink grant. The codebook component 198 may be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The codebook component 198 may be one or more hardware components that are 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. As shown, the device 1804 may include a variety of components configured for various functions. In one configuration, the apparatus 1804 (and specifically, the cellular baseband processor 1824 and / or the application processor 1806) includes means for sending, for a second network entity, information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset in the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the apparatus 1804 may include means for receiving, in an uplink grant, from the second network entity, information indicating a selected codebook in the recommended codebook subset. In some aspects, the apparatus 1804 may also include means for sending a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the apparatus 1804 may include means for determining the partition of the one or more codebook subsets and the recommended codebook subset based on an antenna layout associated with the first network entity.In some aspects, the apparatus 1804 may include means for determining the partitioning of the one or more codebook subsets and the recommended codebook subset based on at least one of the following: local antenna blocking associated with the first network entity, power consumption associated with the first network entity, or channel measurements associated with the first network entity. In some aspects, the apparatus 1804 may include means for determining a second partitioning of the one or more codebook subsets based on at least one of the following: local antenna blocking associated with the first network entity, power consumption associated with the first network entity, or channel measurements associated with the first network entity. In some aspects, the apparatus 1804 may include means for sending information indicating the second partitioning to the second network entity. In some aspects, the apparatus 1804 may include means for receiving information indicating the second partitioning of the one or more codebook subsets from the second network entity. In some aspects, the apparatus 1804 may include means for receiving information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets from the second network entity based on the second partitioning. In some aspects, the apparatus 1804 may include means for sending a second PUSCH transmission based on the second selected codebook. In some aspects, the apparatus 1804 may include means for receiving information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets from a second network entity, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the apparatus 1804 may include means for receiving information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant. In some aspects, the apparatus 1804 may include means for sending a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the apparatus 1804 may include means for receiving information indicating a second partition of the one or more codebook subsets. In some aspects, the apparatus 1804 may include means for receiving information indicating a second selected codebook in the recommended codebook subset in the one or more codebook subsets based on the second partition. In some aspects, the apparatus 1804 may include means for transmitting a second PUSCH transmission based on the second selected codebook. The means may be the codebook component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described herein, the apparatus 1804 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.

[0167] Fig.191900 is a diagram illustrating an example of a hardware implementation for a network entity 1902. The network entity 1902 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1902 may include at least one of a CU 1910, a DU 1930, or a RU 1940. For example, depending on the layer functionality handled by the component 199, the network entity 1902 may include a CU 1910; both a CU 1910 and a DU 1930; each of the CU 1910, the DU 1930, and the RU 1940; the DU 1930; both a DU 1930 and a RU 1940; or a RU 1940. The CU 1910 may include a CU processor 1912. The CU processor 1912 may include an on-chip memory 1912'. In some aspects, the CU 1910 may also include an additional memory module 1914 and a communication interface 1918. CU 1910 communicates with DU 1930 via a midhaul link, such as an F1 interface. DU 1930 may include a DU processor 1932. DU processor 1932 may include on-chip memory 1932'. In some aspects, DU 1930 may also include an additional memory module 1934 and a communication interface 1938. DU 1930 communicates with RU 1940 via a fronthaul link. RU 1940 may include a RU processor 1942. RU processor 1942 may include on-chip memory 1942'. In some aspects, RU 1940 may also include an additional memory module 1944, one or more transceivers 1946, an antenna 1980, and a communication interface 1948. RU 1940 communicates with UE 104. On-chip memory 1912', 1932', 1942' and additional memory modules 1914, 1934, 1944 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1912, 1932, 1942 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.

[0168] In some aspects, the codebook component 199 may be configured to receive information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 199 may be configured to send information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, the codebook component 199 may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the codebook component 199 may be configured to send information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and a recommended codebook subset of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the codebook component 199 may be configured to send information indicating the selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, the codebook component 199 may be configured to receive a PUSCH transmission based on the selected codebook and the uplink grant. The codebook component 199 may be within one or more processors of one or more of the CU 1910, DU 1930, and RU 1940. The codebook component 199 may be one or more hardware components that are 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. The network entity 1902 may include a variety of components configured for various functions. In one configuration, the network entity 1902 includes means for receiving information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset in the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective pre-decoder. In some aspects, the network entity 1902 may include means for sending information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, the network entity 1902 may include means for receiving a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the network entity 1902 may include means for receiving information indicating a second partition of the one or more codebook subsets. In some aspects, the network entity 1902 may include means for determining a second partition of the one or more codebook subsets. In some aspects, the network entity 1902 may include means for sending information indicating the second partition of the one or more codebook subsets.In some aspects, the network entity 1902 may include means for sending information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets for the second network entity based on the second partitioning. In some aspects, the network entity 1902 may also include means for receiving a second PUSCH transmission based on the second selected codebook. In some aspects, the network entity 1902 may include means for sending information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for the second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder. In some aspects, the network entity 1902 may include means for sending information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity. In some aspects, the network entity 1902 may include means for receiving a PUSCH transmission based on the selected codebook and the uplink grant. In some aspects, the network entity 1902 may include means for determining the partition of the one or more codebook subsets. In some aspects, the network entity 1902 may include means for determining a second partition of the one or more codebook subsets. In some aspects, the network entity 1902 may include means for sending information indicating a second partition of the one or more codebook subsets. In some aspects, the network entity 1902 may include means for sending information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partition. In some aspects, the network entity 1902 may also include means for receiving a second PUSCH transmission based on the second selected codebook. The means may be a codebook component 199 of the network entity 1902 configured to perform the functions recited by the means. As described herein, the network entity 1902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

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

[0170] The foregoing 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 may 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 "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages 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, which 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, the data may be directly received / sent between the first device and the second device, or 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 later be known to a person 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", etc. 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..."

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

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

[0173] 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 coupled to the memory, wherein the at least one processor is configured to: send information indicating a partition of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset among the one or more codebook subsets to a second network entity, wherein each respective codebook in the codebook set corresponds to a respective predecoder; receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant; and send a physical uplink shared channel (PUSCH) transmission based on the selected codebook and the uplink grant.

[0174] Aspect 2 is a first network according to aspect 1, wherein the at least one processor is configured to: determine the partitioning of the one or more codebook subsets and the recommended codebook subset based on an antenna layout associated with the first network entity.

[0175] Aspect 3 is a first network according to Aspect 2, wherein in order to determine the partition of the one or more codebook subsets and the recommended codebook subset, the at least one processor is configured to determine the partition of the one or more codebook subsets and the recommended codebook subset based on at least one of the following items: local antenna blocking associated with the first network entity, power consumption associated with the first network entity, or channel measurement associated with the first network entity.

[0176] Aspect 4 is a first network according to any one of Aspects 2 to 3, wherein the at least one processor is configured to: determine a second partition of the one or more codebook subsets based on at least one of the following: local antenna blocking associated with the first network entity, power consumption associated with the first network entity, or channel measurement associated with the first network entity; and send information indicating the second partition to the second network entity.

[0177] Aspect 5 is a first network entity according to any one of aspects 2 to 3, wherein the at least one processor is configured to: receive information indicating a second partitioning of the one or more codebook subsets from the second network entity.

[0178] Aspect 6 is a first network according to any one of aspects 4 to 5, wherein the at least one processor is configured to: receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets from the second network entity based on the second partitioning; and send a second PUSCH transmission based on the second selected codebook.

[0179] Aspect 7 is a first network according to any one of Aspect 6, wherein the second partitioning is based at least on a decoding result associated with the first PUSCH transmission.

[0180] Aspect 8 is a first network according to any one of Aspects 1 to 7, wherein in order to send the information indicating the partition, the at least one processor is configured to send an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

[0181] Aspect 9 is a first network according to any one of Aspects 1 to 8, wherein in order to send the information indicating the division, the at least one processor is configured to send uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the division, wherein the RRC signaling also includes capability information associated with the first network entity.

[0182] Aspect 10 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 information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset among the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective predecoder; send information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity; and receive a physical uplink shared channel (PUSCH) transmission based on the selected codebook and the uplink grant.

[0183] Aspect 11 is the first network according to aspect 10, wherein the partitioning of the one or more codebook subsets and the recommended codebook subset are based on an antenna layout associated with the second network entity.

[0184] Aspect 12 is a first network according to any one of Aspects 10 to 11, wherein the partitioning of the one or more codebook subsets and the recommended codebook subset are based on at least one of the following: local antenna blocking associated with the second network entity, power consumption associated with the second network entity, or channel measurement associated with the second network entity.

[0185] Aspect 13 is a first network according to any one of Aspects 10 to 12, wherein the at least one processor is configured to: receive information indicating a second partitioning of the one or more codebook subsets, wherein the second partitioning is based on at least one of the following: local antenna blocking associated with the second network entity, power consumption associated with the second network entity, or channel measurement associated with the second network entity.

[0186] Aspect 14 is a first network entity according to any one of aspects 10 to 12, wherein the at least one processor is configured to: determine a second partitioning of the one or more codebook subsets; and send information indicating the second partitioning of the one or more codebook subsets.

[0187] Aspect 15 is a first network according to aspect 14, wherein the at least one processor is configured to: send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets to the second network entity based on the second partition; and receive a second PUSCH transmission based on the second selected codebook.

[0188] Aspect 16 is a first network according to Aspect 15, wherein in order to determine the second partition, the at least one processor is configured to determine the second partition based at least on a decoding result associated with the first PUSCH transmission and a machine learning model.

[0189] Aspect 17 is a first network according to any one of Aspects 10 to 16, wherein in order to receive the information indicating the partition, the at least one processor is configured to receive an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

[0190] Aspect 18 is a first network according to any one of Aspects 10 to 17, wherein in order to receive the information indicating the division, the at least one processor is configured to receive uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the division, wherein the RRC signaling also includes capability information associated with the second network entity.

[0191] Aspect 19 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 information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset among the one or more codebook subsets from a second network entity, wherein each respective codebook in the codebook set corresponds to a respective predecoder; receive information indicating a selected codebook in the recommended codebook subset from the second network entity in an uplink grant; and send a physical uplink shared channel (PUSCH) transmission based on the selected codebook and the uplink grant.

[0192] Aspect 20 is the first network entity according to aspect 19, wherein the at least one processor is configured to: receive information indicating a second partitioning of the one or more codebook subsets.

[0193] Aspect 21 is a first network according to any one of aspects 19 to 20, wherein the at least one processor is configured to: receive information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partition; and send a second PUSCH transmission based on the second selected codebook.

[0194] Aspect 22 is a first network according to any one of aspects 19 to 21, wherein in order to receive the information indicating the partition, the at least one processor is configured to receive a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

[0195] Aspect 23 is a first network according to any one of Aspects 19 to 22, wherein in order to receive the information indicating the partition, the at least one processor is configured to receive downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

[0196] Aspect 24 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 information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective predecoder; send information indicating a selected codebook in the recommended codebook subset in an uplink grant for the second network entity; and receive a physical uplink shared channel (PUSCH) transmission based on the selected codebook and the uplink grant.

[0197] Aspect 25 is the first network according to aspect 24, wherein the at least one processor is configured to determine the partitioning of the one or more codebook subsets.

[0198] Aspect 26 is a first network entity according to any one of aspects 24 to 25, wherein the at least one processor is configured to: determine a second partitioning of the one or more codebook subsets; and send information indicating the second partitioning of the one or more codebook subsets.

[0199] Aspect 27 is a first network according to any one of aspects 24 to 26, wherein the at least one processor is configured to: send information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partition; and receive a second PUSCH transmission based on the second selected codebook.

[0200] Aspect 28 is a first network according to any one of Aspects 24 to 27, wherein in order to determine the second partition, the at least one processor is configured to: determine the second partition based at least on a PUSCH decoding result set, the PUSCH decoding result set including a PUSCH decoding result associated with the PUSCH transmission.

[0201] Aspect 29 is a first network according to any one of aspects 24 to 28, wherein in order to send the information indicating the partition, the at least one processor is configured to send a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

[0202] Aspect 30 is a first network according to any one of Aspects 24 to 29, wherein in order to send the information indicating the partition, the at least one processor is configured to send downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

[0203] Aspect 31 is a wireless communication method for implementing any one of aspects 1 to 9 and aspects 19 to 23.

[0204] Aspect 32 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 9 and aspects 19 to 23.

[0205] Aspect 33 is a computer-readable medium (e.g., a non-transitory computer-readable storage medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of Aspects 1 to 9 and Aspects 19 to 23.

[0206] Aspect 34 is a wireless communication method for implementing any one of aspects 10 to 18 and aspects 24 to 30.

[0207] Aspect 35 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 10 to 18 and aspects 24 to 30.

[0208] Aspect 36 is a computer-readable medium (eg, a non-transitory computer-readable storage medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 10 to 18 and aspects 24 to 30.

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: Sending, to a second network entity, information indicating a division of one or more codebook subsets in a configured codebook set and information indicating a recommended codebook subset among the one or more codebook subsets, wherein each corresponding codebook in the codebook set corresponds to a corresponding precoder; receiving, in an uplink grant from the second network entity, information indicating a selected codebook from the recommended codebook subset; as well as A physical uplink shared channel (PUSCH) transmission is sent based on the selected codebook and the uplink grant.

2. The first network entity according to claim 1, wherein the at least one processor is configured to: The partitioning of the one or more codebook subsets and the recommended codebook subset are determined based on an antenna layout associated with the first network entity.

3. The first network entity of claim 2, wherein to determine the partition of the one or more codebook subsets and the recommended codebook subset, the at least one processor is configured to determine the partition of the one or more codebook subsets and the recommended codebook subset based on at least one of the following: a local antenna blockage associated with the first network entity, a power consumption associated with the first network entity, or Channel measurements associated with the first network entity.

4. The first network entity according to claim 2, wherein the at least one processor is configured to: The second partitioning of the one or more codebook subsets is determined based on at least one of the following: a local antenna blockage associated with the first network entity, a power consumption associated with the first network entity, or channel measurements associated with the first network entity; and Information indicating the second division is sent to the second network entity.

5. The first network entity of claim 2, wherein the at least one processor is configured to: Information indicating a second partitioning of the one or more codebook subsets is received from the second network entity.

6. The first network entity according to claim 5, wherein the at least one processor is configured to: receiving, from the second network entity, information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning; and A second PUSCH transmission is sent based on the second selected codebook.

7. The first network entity of claim 6, wherein the second partitioning is based at least on a decoding result associated with the first PUSCH transmission.

8. The first network entity of claim 1, wherein to send the information indicating the partition, the at least one processor is configured to send an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

9. The first network entity of claim 1 , wherein in order to send the information indicating the partition, the at least one processor is configured to send uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the partition, wherein the RRC signaling also includes capability information associated with the first network entity.

10. 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 information indicating a partition of one or more codebook subsets in a configured codebook set for a second network entity and information indicating a recommended codebook subset of the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective precoder; sending, in an uplink grant to the second network entity, information indicating a selected codebook from the recommended codebook subset; as well as A physical uplink shared channel (PUSCH) transmission is received based on the selected codebook and the uplink grant.

11. The first network entity of claim 10, wherein the partitioning of the one or more codebook subsets and the recommended codebook subset are based on an antenna configuration associated with the second network entity.

12. The first network entity of claim 11, wherein the partitioning of the one or more codebook subsets and the recommended codebook subset are based on at least one of the following: a local antenna blockage associated with the second network entity, a power consumption associated with the second network entity, or Channel measurements associated with the second network entity.

13. The first network entity of claim 11, wherein the at least one processor is configured to: Receiving information indicating a second partitioning of the one or more codebook subsets, wherein the second partitioning is based on at least one of: a local antenna blockage associated with the second network entity, a power consumption associated with the second network entity, or Channel measurements associated with the second network entity.

14. The first network entity of claim 11, wherein the at least one processor is configured to: determining a second partitioning of the one or more codebook subsets; and Information indicating the second partitioning of the one or more codebook subsets is transmitted.

15. The first network entity of claim 14, wherein the at least one processor is configured to: sending, to the second network entity, information indicating a second selected codebook in the recommended codebook subset among the one or more codebook subsets based on the second partitioning; and A second PUSCH transmission is received based on the second selected codebook.

16. The first network entity of claim 15, wherein to determine the second partition, the at least one processor is configured to determine the second partition based at least on a decoding result associated with the first PUSCH transmission and a machine learning model.

17. The first network entity of claim 10, wherein to receive the information indicating the partition, the at least one processor is configured to receive an uplink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

18. The first network entity of claim 10, wherein in order to receive the information indicating the partition, the at least one processor is configured to receive uplink control information (UCI) or radio resource control (RRC) signaling including the information indicating the partition, wherein the RRC signaling also includes capability information associated with the second network entity.

19. 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, from a second network entity, information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset among the one or more codebook subsets, wherein each respective codebook in the codebook set corresponds to a respective precoder; receiving, in an uplink grant from the second network entity, information indicating a selected codebook from the recommended codebook subset; as well as A physical uplink shared channel (PUSCH) transmission is sent based on the selected codebook and the uplink grant.

20. The first network entity of claim 19, wherein the at least one processor is configured to: Information indicating a second partitioning of the one or more codebook subsets is received.

21. The first network entity of claim 20, wherein the at least one processor is configured to: receiving information indicating a second selected codebook in the recommended codebook subset of the one or more codebook subsets based on the second partitioning; and A second PUSCH transmission is sent based on the second selected codebook.

22. The first network entity of claim 19, wherein to receive the information indicating the partition, the at least one processor is configured to receive a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

23. The first network entity of claim 19, wherein to receive the information indicating the partition, the at least one processor is configured to receive downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

24. 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 information indicating a partition of one or more codebook subsets in a configured codebook set and a recommended codebook subset in the one or more codebook subsets for a second network entity, wherein each respective codebook in the codebook set corresponds to a respective precoder; sending, in an uplink grant to the second network entity, information indicating a selected codebook from the recommended codebook subset; as well as A physical uplink shared channel (PUSCH) transmission is received based on the selected codebook and the uplink grant.

25. The first network entity of claim 24, wherein the at least one processor is configured to: The partitioning of the one or more codebook subsets is determined.

26. The first network entity of claim 24, wherein the at least one processor is configured to: determining a second partitioning of the one or more codebook subsets; and Information indicating the second partitioning of the one or more codebook subsets is transmitted.

27. The first network entity of claim 26, wherein the at least one processor is configured to: transmitting information indicating a second selected codebook in the recommended codebook subset among the one or more codebook subsets based on the second partitioning; and A second PUSCH transmission is received based on the second selected codebook.

28. The first network entity of claim 26, wherein, in order to determine the second partition, the at least one processor is configured to: determine the second partition based at least on a PUSCH decoding result set, the PUSCH decoding result set comprising PUSCH decoding results associated with the PUSCH transmission.

29. The first network entity of claim 24, wherein to send the information indicating the partition, the at least one processor is configured to send a downlink medium access control (MAC) control element (MAC-CE) including the information indicating the partition.

30. The first network entity of claim 24, wherein to send the information indicating the partition, the at least one processor is configured to send downlink control information (DCI) or radio resource control (RRC) signaling including the information indicating the partition.

Images