Codebook selection

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may generate a recommendation for a first codebook for a single transmit receive point (TRP) and not including a time domain (TD) base or a Doppler domain (DD) base, or a second codebook for multiple TRPs or including a TD base or a DD base. The UE may send the recommendation. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 162,626, filed on January 31, 2023, entitled “CODEBOOK SELECTION,” and assigned to the assignee of the present application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for codebook selection. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include generating a recommendation for a first codebook for a single transmit receive point (TRP) and not including a time domain (TD) basis or a Doppler domain (DD) basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. The method may include transmitting the recommendation.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. The method may include sending a codebook configuration based at least in part on the recommendation.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The method may include selecting the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include generating a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The method may include transmitting the codebook structure.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the UE to generate a recommendation for a first codebook or a second codebook, the first codebook being for a single TRP and not including a TD basis or a DD basis, and the second codebook being for multiple TRPs or including a TD basis or a DD basis. The instructions may be executable by the one or more processors to cause the UE to send the recommendation.

[0012] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the network entity to receive a recommendation for a first codebook or a second codebook, the first codebook being for a single TRP and not including a TD basis or a DD basis, and the second codebook being for multiple TRPs or including a TD basis or a DD basis. The instructions may be executable by the one or more processors to cause the network entity to send a codebook configuration based at least in part on the recommendation.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the UE to receive a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The instructions may be executable by the one or more processors to cause the UE to select the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions.

[0014] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the network entity to generate a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The instructions may be executable by the one or more processors to cause the network entity to transmit the codebook structure.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a UE. When executed by one or more processors of the UE, the one or more instructions may cause the UE to generate a recommendation for a first codebook for a single TRP and not including a TD or DD basis, or a second codebook for multiple TRPs or including a TD or DD basis. When executed by the one or more processors of the UE, the one or more instructions may cause the UE to transmit the recommendation.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a network entity. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to receive a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. The one or more instructions, when executed by the one or more processors of the network entity, may cause the network entity to send a codebook configuration based at least in part on the recommendation.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a UE. The one or more instructions, when executed by one or more processors of the UE, may cause the UE to receive a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The one or more instructions, when executed by the one or more processors of the UE, may cause the UE to select the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a network entity. The one or more instructions, when executed by one or more processors of the network entity, may cause the network entity to generate a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. The one or more instructions, when executed by the one or more processors of the network entity, may cause the network entity to transmit the codebook structure.

[0019] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0020] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0021] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order that the above-described features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of a network entity (eg, a base station) communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0026] Figure 4 An example logical architecture of a distributed random access network according to the present disclosure is illustrated.

[0027] Figure 5 is a diagram illustrating an example of multi-transmission reception point (TRP) communication (sometimes referred to as multi-panel communication) according to the present disclosure.

[0028] Figure 6 is a diagram illustrating an example of a channel state information reference signal beam management process according to the present disclosure.

[0029] Figure 7 is a diagram illustrating examples of coherent joint transmission and non-coherent joint transmission for multiple TRPs according to the present disclosure.

[0030] Figure 8 is a diagram illustrating an example of selecting a codebook according to the present disclosure.

[0031] Figure 9 is a diagram illustrating an example of codebook basis selection according to the present disclosure.

[0032] Figure 10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0033] Figure 11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0034] Figure 12 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0035] Figure 13 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0036] Figure 14 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0037] Figure 15 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0038] The coverage of a user equipment (UE) may be limited to a single transmit receive point (TRP), and the mobility of the UE may be restricted so that legacy channel state information (CSI) can ensure reliable communication. Legacy codebooks (e.g., the 3rd Generation Partnership Project (3GPP) standard Release 17 codebook or earlier versions) can be characterized as codebooks for a single TRP and not including a time domain (TD) basis or a Doppler domain (DD) basis. Release 18 codebooks (non-legacy codebooks) can be characterized as codebooks for multiple TRPs, including a TD basis or a DD basis, or both. In addition to higher measurement and reporting resource overhead, Release 18 codebook enhancements may also involve higher computation and processing at the UE side. The benefits of Release 18 optimizations can be found primarily in high Doppler scenarios and multi-TRP (mTRP) coherent joint transmission (CJT) operations, where the UE is in the coverage area of ​​multiple TRPs. If the UE does not need to use the Release 18 codebook (e.g., single TRP, low mobility), using the Release 18 codebook is a waste of power, processing resources, and signaling resources.

[0039] According to various aspects described herein, a UE may request a network entity to dynamically switch between a first codebook (e.g., a Release 17 codebook for a single TRP and not including a TD basis or a DD basis) and a second codebook (e.g., a Release 18 codebook for multiple TRPs, including a TD basis or a DD basis, or both). The network entity may use these codebooks for downlink transmissions. For example, the UE may generate a recommendation by selecting the first codebook or the second codebook. The UE may send the recommendation. The network entity may send a codebook configuration based at least in part on the recommendation. The network entity may accept the recommendation, or reject the recommendation and select a different codebook than the recommendation. By providing a recommendation, the UE may have greater flexibility to select a codebook (e.g., a Release 17 codebook or a Release 18 codebook) that is appropriate for the conditions or UE state.

[0040] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0041] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0042] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0043] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0044] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a TRP, a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0045] In some examples, network node 110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0046] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0047] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0048] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0049] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0050] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0051] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0052] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0054] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that 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 it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0056] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0057] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may generate a recommendation for a first codebook for a single TRP that does not include a TD basis or a DD basis, or a second codebook for multiple TRPs or that includes a TD basis or a DD basis. The communication manager 140 may send the recommendation.

[0058] In some aspects, the communication manager 140 may receive a codebook structure for selecting a TD basis or a DD basis for the codebook based at least in part on one or more configuration conditions. The communication manager 140 may select the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0059] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. The communication manager 150 may send a codebook configuration based at least in part on the recommendation.

[0060] In some aspects, the communication manager 150 may generate a codebook structure for selecting a TD basis or a DD basis for the codebook based at least in part on one or more configuration conditions. The communication manager 150 may transmit the codebook structure. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0061] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0062] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0063] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0064] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0065] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0066] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0067] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 4 to 15 ) any aspects of any method described in the method.

[0068] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 4 to 15 ) any aspects of any method described in the method.

[0069] As described in greater detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of network node 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the network node 110 may perform one or more techniques associated with codebook selection. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 10 The process of 1000 Figure 11 Process 1100, Figure 12 The process of 1200 Figure 13 1300 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause the one or more processors, UE 120, and / or the network entity to perform or direct, for example, Figure 10 The process of 1000 Figure 11 Process 1100, Figure 12 The process of 1200 Figure 13 The operations of process 1300 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0070] In some aspects, a UE (e.g., UE 120) includes means for generating a recommendation for a first codebook or a second codebook, the first codebook being for a single TRP and not including a TD basis or a DD basis, and the second codebook being for multiple TRPs or including a TD basis or a DD basis; and / or means for transmitting the recommendation. Means for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0071] In some aspects, a network entity (e.g., network node 110) includes means for receiving a recommendation for a first codebook or a second codebook, the first codebook being for a single TRP and not including a TD basis or a DD basis, the second codebook being for multiple TRPs or including a TD basis or a DD basis; and / or means for transmitting a codebook configuration based at least in part on the recommendation. In some aspects, means for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0072] In some aspects, a UE (e.g., UE 120) includes means for receiving a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions; and / or means for selecting the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions. Means for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0073] In some aspects, a network entity (e.g., network node 110) includes means for generating a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions; and / or means for transmitting the codebook structure. In some aspects, means for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0074] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0075] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0076] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element or network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality) can be implemented in a converged or decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell) can be implemented as a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0077] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more 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 across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0079] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with the service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as the F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)," respectively. A network entity may include a CU, DU, RU, or any combination of CUs, DUs, and RUs. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CUs, DUs, and RUs. A network entity may also include one or more of the following: a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that can provide a network interface or service for a UE, mobile station, sensor / actuator, or other wireless device.

[0080] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, to one or more of the other units over the wireless transmission medium.

[0081] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 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, the CU 310 may be logically 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, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0082] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the following, at least in part according to a functional split (such as that defined by 3GPP): a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 330 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0083] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, both real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0084] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0085] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0087] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0088] Figure 4 An example logical architecture of a distributed RAN 400 according to the present disclosure is illustrated.

[0089] The 5G access node 405 may include an access node controller 410. The access node controller 410 may be a CU of the distributed RAN 400. In some aspects, a backhaul interface to the 5G core network 415 may terminate at the access node controller 410. The 5G core network 415 may include a 5G control plane component 420 and a 5G user plane component 425 (e.g., a 5G gateway), and the backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 410. Additionally or alternatively, a backhaul interface to one or more neighboring access nodes 430 (e.g., another 5G access node 405 and / or an LTE access node) may terminate at the access node controller 410.

[0090] The access node controller 410 may include one or more TRPs 435 and / or may communicate with one or more TRPs (e.g., via an F1 control (F1-C) interface and / or an F1 user (F1-U) interface). The TRP 435 may be a DU of the distributed RAN 400. In some aspects, the TRP 435 may correspond to the above combined Figure 110. For example, different TRPs 435 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 435 may be included in a single network node 110. In some aspects, the network node 110 may include a CU (e.g., an access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 may be referred to as a cell, a panel, an antenna array, or an array.

[0091] The TRP 435 may be connected to a single access node controller 410 or to multiple access node controllers 410. In some aspects, there may be dynamic configuration of split logical functions within the architecture of the distributed RAN 400. For example, the PDCP layer, RLC layer, and / or MAC layer may be configured to terminate at the access node controller 410 or the TRP 435.

[0092] In some aspects, multiple TRPs 435 may transmit communications (e.g., the same communication or different communications) in the same transmit time interval (TTI) (e.g., a slot, mini-slot, subframe, or symbol) or in different TTIs using different quasi-co-location (QCL) relationships (e.g., different spatial parameters, different transmit configuration indicator (TCI) states, different precoding parameters, and / or different beamforming parameters). In some aspects, the TCI state may be used to indicate one or more QCL relationships. A TRP 435 may be configured to provide traffic to a UE 120 individually (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 435).

[0093] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0094] Figure 5 5 is a diagram illustrating an example 500 of multiple TRP (multi-TRP) communication (sometimes referred to as multi-panel communication) according to the present disclosure. Figure 5 As shown, multiple TRPs 505 can communicate with the same UE 120. TRP 505 can correspond to the above-mentioned Figure 4 TRP 435 as described.

[0095] Multiple TRPs 505 (shown as TRP A and TRP B) can communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and / or increase throughput. The TRPs 505 can coordinate such communications via an interface between the TRPs 505 (e.g., a backhaul interface and / or an access node controller 410). When the TRPs 505 are co-located at the same network node 110 (e.g., when the TRPs 505 are different antenna arrays or panels of the same network node 110), the interface can have lower latency and / or higher capacity, and when the TRPs 505 are located at different base stations 110, the interface can have higher latency and / or lower capacity (compared to co-location). Different TRPs 505 can communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., different layers in a multi-layer communication).

[0096] In a first multi-TRP transmission mode (e.g., Mode 1), a single physical downlink control channel (PDCCH) may be used to schedule downlink data communications for a single physical downlink shared channel (PDSCH). In this case, multiple TRPs 505 (e.g., TRP A and TRP B) may send communications to UE 120 on the same PDSCH. For example, communications may be sent using a single codeword with different spatial layers for different TRPs 505 (e.g., where one codeword is mapped to a first set of layers sent by a first TRP 505 and to a second set of layers sent by a second TRP 505). As another example, communications may be sent using multiple codewords, where different codewords are sent by different TRPs 505 (e.g., using different sets of layers). In either case, different TRPs 505 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 505 may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first set of layers, and the second TRP 505 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) set of layers. In some aspects, the TCI state in the downlink control information (DCI) (e.g., sent on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Generally speaking, in the multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0097] In a second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCHs (e.g., one PDCCH for each PDSCH). In this case, a first PDCCH may schedule a first codeword to be transmitted by the first TRP 505, and a second PDCCH may schedule a second codeword to be transmitted by the second TRP 505. In addition, a first DCI (e.g., transmitted by the first TRP 505) may schedule a first PDSCH communication associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 505, and a second DCI (e.g., transmitted by the second TRP 505) may schedule a second PDSCH communication associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 505. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state corresponding to the DCI for the TRP 505. The TCI field of the DCI indicates the corresponding TCI state (e.g., the TCI field of the first DCI indicates a first TCI state and the TCI field of the second DCI indicates a second TCI state).

[0098] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0099] Figure 6 600, 610, and 620 are diagrams illustrating examples of a CSI reference signal (CSI-RS) beam management process according to the present disclosure. Figure 6 As shown, examples 600, 610, and 620 include a UE 120 communicating with a network entity (e.g., network node 110) in a wireless network (e.g., wireless network 100). Figure 6 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and network node 110 or TRP, between mobile terminal nodes and control nodes, between IAB child nodes and IAB parent nodes, and / or between scheduled nodes and scheduling nodes). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., an RRC connected state).

[0100] like Figure 6As shown, example 600 may include a network node (NN) 110 and a UE 120 communicating to perform beam management using CSI-RS. Example 600 depicts a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam scanning procedure, a cell search procedure, and / or a beam search procedure. Figure 6 As shown in example 600, CSI-RS may be configured to be sent from network node 110 to UE 120. CSI-RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling), and / or aperiodic (e.g., using DCI).

[0101] The first beam management process may include network node 110 performing beam scanning on multiple transmit (Tx) beams. Network node 110 may use each transmit beam used for beam management to transmit a CSI-RS. To enable UE 120 to perform receive (Rx) beam scanning, the base station may transmit each CSI-RS multiple times (e.g., using repetition) within the same reference signal (RS) resource set using the transmit beam, so that UE 120 can scan the receive beam in multiple transmission instances. For example, if network node 110 has a set of N transmit beams and UE 120 has a set of M receive beams, CSI-RS may be transmitted M times on each of the N transmit beams, so that UE 120 can receive M instances of CSI-RS per transmit beam. In other words, for each transmit beam of network node 110, UE 120 may perform beam scanning on its receive beam. Thus, the first beam management procedure may enable UE 120 to use different receive beams to measure CSI-RS on different transmit beams to support selection of a network node 110 transmit beam / UE 120 receive beam pair. UE 120 may report the measurement results to network node 110 to enable network node 110 to select one or more beam pairs for communication between network node 110 and UE 120. Although example 600 has been described in conjunction with CSI-RS, the first beam management procedure may also use synchronization signal blocks (SSBs) to perform beam management in a similar manner as described above.

[0102] like Figure 6 As shown, example 610 may include network node 110 and UE 120 communicating to perform beam management using CSI-RS. Example 610 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure may be referred to as a beam refinement procedure, a base station beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 6As shown in example 610, a CSI-RS may be configured to be transmitted from network node 110 to UE 120. The CSI-RS may be configured to be aperiodic (e.g., using DCI). The second beam management procedure may include network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with network node 110 (e.g., determined based at least in part on measurements reported by UE 120 in conjunction with the first beam management procedure). Network node 110 may transmit a CSI-RS using each of the one or more transmit beams used for beam management. UE 120 may measure each CSI-RS using a single (e.g., identical) receive beam (e.g., determined based at least in part on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable network node 110 to select an optimal transmit beam based at least in part on the CSI-RS measurements reported by UE 120 (e.g., measured by UE 120 using a single receive beam).

[0103] like Figure 6 As shown, example 620 depicts a third beam management process (e.g., P3 CSI-RS beam management). The third beam management process may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. Figure 6 As shown in example 620, one or more CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RS may be configured to be aperiodic (e.g., using DCI). The third beam management procedure may include the network node 110 transmitting the one or more CSI-RSs using a single transmit beam (e.g., determined at least in part based on measurement results reported by the UE 120 in conjunction with the first beam management procedure and / or the second beam management procedure). To enable the UE 120 to perform receive beam scanning, the base station may transmit the CSI-RS multiple times (e.g., using repetition) within the same RS resource set using the transmit beam, so that the UE 120 can scan through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (e.g., determined at least in part based on measurement results performed in conjunction with the first beam management procedure and / or the second beam management procedure). The third beam management process may enable the network node 110 and / or the UE 120 to select the best receive beam based at least in part on reported measurement results received from the UE 120 (e.g., reported measurement results of the CSI-RS of the transmit beam using the one or more receive beams).

[0104] As indicated above, Figure 6is provided as an example of a beam management process. Other examples of beam management processes can be found in the Figure 6 For example, the UE 120 and the network node 110 may perform the third beam management procedure before performing the second beam management procedure, and / or the UE 120 and the network node 110 may perform a similar beam management procedure to select a UE transmit beam.

[0105] Figure 7 is a diagram illustrating example 700 of CJT and non-coherent joint transmission (NCJT) for multiple TRPs according to the present disclosure.

[0106] CJT involves multiple transmitters, each transmitting a message with a phase that constructively combines at the receiver. CJT may include beamforming using antennas that are not co-located and correspond to different TRPs. CJT can improve signal power and spatial diversity in communications in NR networks.

[0107] UE 120 may measure the CSI-RS and send a CSI report indicating the CSI, such as a precoding matrix indicator (PMI). The PMI is a matrix that indicates how data is transformed to the antenna ports. The CSI report may include a codebook, which is a set of precoders or one or more PMIs. A Type I codebook may include a predefined matrix. A Type II codebook may include a more detailed CSI report for multi-user MIMO and may include beam groups. CSI acquisition may be enhanced for CJT of multiple TRPs (e.g., up to 4 TRPs). An enhanced Type II codebook (eType-II codebook) may be an eType-II codebook structure, which may be generalized as where the pre-decoder for a specific layer on N3 subbands is written as where c i,m,l is the combination coefficient for the i-th spatial basis (beam) and the m-th frequency basis, and is a 2L×M matrix containing all coefficients, such as N t ×1 spatial domain (SD) basis, W1 is N containing all SD bases t ×2L matrix, and is a 1×N3FD basis; is an M×N3 matrix containing all FD bases. L can be a spatial domain basis, such as a beam configuration or TRP. M can be a frequency domain basis. The eType-II extension to CJT can be applied to TRPs individually and then combined by common phase: where W(1) and W(2) are the associated eType-II pre-decoders for TRP1 and TRP2, and is a scaler for common phase (or vector for different subbands). The eType-II pre-decoder can be applied jointly across TRPs, where And the difference here is that W(1) and W(2) are calculated jointly.

[0108] For eType-IICSI, the parameters may include SD radix configuration represented as #SD:L={2,4,6}. The frequency domain radix may be represented as #FD: and The coefficients may include an amplitude scaling factor (p) and a beta shift factor (β). The non-zero coefficients (NZC) may be expressed as #NZC: The network entity may configure a combination (1 out of 8) of (L, p1, p3, β) using RRC messaging.

[0109] For eType-II with respect to CJT, further design considerations may be necessary for multiple TRPs. If multiple TRPs are supported (such as up to 4 TRPs), the UE may report the PMI for all TRPs jointly, and the UE may be expected to indicate the selection hypothesis. In order to indicate the channel conditions of different TRPs while balancing the feedback overhead (e.g., bitmaps for coefficient indication, coefficient feedback), different TRPs may have different numbering for the spatial domain basis (L) or the frequency domain basis (M). It may be necessary to support different codebooks based on, for example, a common phase across different TRPs (where the coefficients of the TRPs are calculated independently). The codebooks may be jointly calculated and reported across TRPs.

[0110] For NCJT based on spatial domain multiplexing (SDM), data is pre-decoded separately on different TRPs. For example, pre-decoder A is pre-decoded for one TRP, and pre-decoder B is pre-decoded for a separate TRP. This can be expressed as: The non-bold letters are used for data of pre-decoder A and the first TRP, and the bold letters are used for data of pre-decoder B and the second TRP. V A :4×1、V B :4×2 may indicate a precoder for a specific TRP and rank (indicated by the rank indicator (RI)). Data (RI TRP ×1)X A :1×1、X B :2×1 can indicate data through TRP and RI.

[0111] For CJT, data is pre-decoded jointly at different TRPs. For example, this can be expressed as: Predecoder V A :4×2、V B :4×2 and data(RICJT ×1)X:2×1. Reference numeral 702 shows joint precoding for multiple TRPs, rather than separate precoding as shown for NCJT. Reference numeral 704 shows two layers that are jointly precoded. Reference numeral 706 shows a precoder for one layer of the eType-II codebook structure, which is generalized as

[0112] For 3GPP standard Release 18 Type II codebook optimization for high or medium UE mobility speeds, the UE may support a codebook structure in which N4 (codebook size in the time domain) is configured by the network entity via higher layer signaling. For N4=1, the DD basis is identical (no DD compression), which reuses the old W1, and W f (For example, At higher UE speeds, channel variations in the time domain are significant. Without accounting for such variations in UE mobility scenarios, the codebook may become inaccurate. Inaccurate feedback may degrade communications, wasting power, processing resources, and signaling resources.

[0113] For N4>1, the DD orthogonal DFT basis usually selected for all space domain (SD) basis and frequency domain (FD) basis can reuse the old W1 and W f , where the codebook is represented as W1 represents the space aspect, represents the codebook coefficient, W f represents FD, and now W d In this scenario, only Q (the number of selected DD basis vectors) > 1 is allowed.

[0114] In typical UE operation, coverage may be limited to a single TRP and mobility may be restricted so that legacy CSI can ensure reliable communication. Legacy codebooks (e.g., Release 17 codebooks, codebooks earlier than Release 17) can be characterized as codebooks for a single TRP and not including a TD basis or a DD basis. Release 18 codebooks (non-legacy codebooks) can be characterized as codebooks for multiple TRPs, including a TD basis or a DD basis, or both. In addition to higher measurement and reporting resource overhead, Release 18 codebook enhancements may also involve higher computation and processing at the UE side. The benefits of Release 18 optimizations can be found primarily in high Doppler scenarios and mTRP CJT operations, where the UE is in the coverage area of ​​multiple TRPs. If the UE does not need to use the Release 18 codebook (e.g., single TRP, low mobility), using the Release 18 codebook is a waste of power, processing resources, and signaling resources.

[0115] In addition, for DD group or TD group (W dDifferent alternatives to the sparse matrix have different advantages and disadvantages. Non-identity bases (e.g., DFT, discrete cosine transform (DCT)) offer lower overhead due to better compression (but higher complexity). Identity bases are suitable when channel variations are abrupt and less predictable. Basis functions can be customized for different operating scenarios to exploit a higher accuracy and overhead trade-off.

[0116] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0117] Figure 8 8 is a diagram illustrating an example 800 of selecting a codebook according to the present disclosure. Example 800 shows a network entity 810 (e.g., network node 110) and a UE 820 (e.g., UE 120) that can communicate with each other via a wireless network (e.g., wireless network 100). Network entity 810 can control or operate with one or more TRPs.

[0118] According to various aspects described herein, a UE 820 may dynamically switch between a first codebook (e.g., a Release-17 codebook for a single TRP that does not include a TD or DD basis) and a second codebook (e.g., a Release-18 codebook for multiple TRPs that includes a TD or DD basis, or both). For example, the UE 820 may generate a recommendation by selecting the first codebook or the second codebook, as shown by reference numeral 825. As shown by reference numeral 830, the UE 820 may send the recommendation. As shown by reference numeral 835, the network entity 810 may send a codebook configuration based at least in part on the recommendation. The network entity 810 may accept the recommendation or reject the recommendation and select a different codebook than the recommendation. By providing the recommendation, the UE 820 may have greater flexibility in selecting a codebook (e.g., a Release-17 codebook or a Release-18 codebook) that is appropriate for the conditions or UE state. As a result, if a Release-18 codebook is not required, the UE 820 may save power, processing resources, and signaling resources. The UE 820 may use the Release 18 codebook to improve CSI feedback and improve communications, which also saves power, processing resources, and signaling resources that would otherwise be wasted with degraded communications and retransmissions.

[0119] For example, UE 820 may request network entity 810 to switch between a Release 18 codebook and a Release 17 codebook based at least in part on UE-side conditions or conditions at UE 820. The UE-side conditions may include channel time-related measurements, such as measurements of downlink reference signals (e.g., CSI-RS or tracking reference signals (TRS)). The measurements may indicate time differences or time variations in the channel. The side conditions may include Doppler measurements, which may include time differences or variations based at least in part on UE mobility or other sensors (e.g., proximity, radar, lidar) of UE 820. The side conditions may include RSRP measurements or signal-to-interference-plus-noise ratio (SINR) measurements from multiple TRPs.

[0120] In some aspects, the UE 820 may select a Release 18 codebook based at least in part on a determination that use of the existing Release 17 codebook will result in a loss of throughput or fail to meet a block error rate (BLER) threshold (e.g., a maximum BLER). After communication fails to improve through such corrections, the UE 820 may request a switch to the Release 18 codebook instead of performing hybrid automatic repeat request (HARQ) or CQI adjustment.

[0121] In some aspects, the UE 820 may select a Release 17 codebook or a Release 18 codebook based at least in part on UE battery status or data application quality of service (QoS) requirements. For example, the UE 820 may switch from a Release 18 codebook to a legacy codebook (e.g., a Release 17 codebook or earlier). In some aspects, the UE 820 may send a recommendation indicating the codebook selection in an explicit message, such as in a physical uplink channel message.

[0122] Alternatively, in some aspects, the recommendation may be an implicit message. UE 820 may adjust signaling or one or more parameters in existing signaling used by UE 820 so that network entity 810 interprets the adjustment as an indication of a recommendation to switch codebooks. For example, UE 820 may indicate a recommendation by sending multiple negative acknowledgments (NACKs), which are interpreted by network entity 810 as an indication to switch codebooks. In some aspects, UE 820 may send an indication of a preferred codebook that is different from the codebook configured by network entity 810. Other parameter adjustments may include a pattern of NACKs. For example, UE 810 may send a NACK at time slots / times n1, n2, n3, ... nK. In some aspects, UE 820 may send an ACK or NACK in designated or configured resources. UE 802 may also reuse additional information fields in existing ACK / NACK messages.

[0123] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0124] Figure 9 is a diagram illustrating an example 900 of codebook basis selection according to the present disclosure.

[0125] In some aspects, the network entity 810 may configure an adaptive codebook structure, wherein the UE 820 may be able to select a TD basis or a DD basis (or a set of TD basis or DD basis) for a codebook (e.g., a selected codebook) based at least in part on satisfying certain configuration conditions. The conditions may be configured via radio resource control (RRC) messaging.

[0126] Example 900 illustrates the use of a codebook structure for TD basis selection or DD basis selection. As indicated by reference numeral 905, the network entity 810 may generate a codebook structure for selecting a TD basis or a DD basis for the codebook. The codebook structure may indicate a codebook and / or conditions for selecting the TD basis or the DD basis for the codebook. The UE 820 may select the TD basis or the DD basis based at least in part on one or more configured conditions.

[0127] In some aspects, the configuration conditions may include an offset between the CSI measurement or reporting instance and the codebook application time slot (when the codebook is applied). The configuration conditions may include the codebook size (e.g., N4) in TD / DD. The configuration conditions may include the channel correlation time. The configuration conditions may include the Doppler profile perceived by the UE. The configuration conditions may include reporting overhead or resource configuration. The configuration conditions may include QoS requirements.

[0128] In some aspects, the configuration may include a network entity 810 preference order or a UE 820 preference order for TD or DD base selection. For example, the preference order may include a list of TD or DD bases from which the UE 820 may select in order. In some aspects, the order may be based at least in part on the preferences of the corresponding nodes. For example, the UE 820 may prefer a certain set of bases at a given time based at least in part on its available resources (e.g., hardware, software, computing, memory, power). Preferences may change over time as resource availability changes. Similarly, the network entity 810 may have preferences based at least in part on its load and / or traffic.

[0129] As shown at reference numeral 910, network entity 810 may transmit a codebook structure. As shown at reference numeral 915, UE 820 may select a TD basis or a DD basis for the codebook based at least in part on one or more configured conditions. This may include comparing current conditions (e.g., traffic, channel, UE state) with the configured conditions. UE 820 may select one or more TD basis or DD basis (W) based at least in part on the results of the comparison. dIn some aspects, the UE 820 may transmit a selected TD-based or DD-based report, as indicated by reference numeral 920.

[0130] By enabling UE 820 to select a TD basis or a DD basis for the codebook, UE 820 can select a TD basis or a DD basis for the codebook that utilizes the advantages of the other TD basis or DD basis or avoids its disadvantages. As a result, the codebook can be more accurate and / or more efficient. This improves communication and saves power, processing resources, and signaling resources.

[0131] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0132] Figure 10 1 is a diagram illustrating an example process 1000, performed, for example, by a UE, according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120, UE 820) performs operations associated with codebook selection.

[0133] like Figure 10 As shown, in some aspects, process 1000 may include generating a recommendation for a first codebook (e.g., a Release 17 codebook) for a single TRP and not including a TD basis or a DD basis, or a second codebook (e.g., a Release 18 codebook) for multiple TRPs or including a TD basis or a DD basis (or both) (block 1010). Figure 14 The communication manager 1406 depicted in FIG) may generate a recommendation for a first codebook that is used for a single TRP and does not include a TD basis or a DD basis, or a second codebook that is used for multiple TRPs or includes a TD basis or a DD basis (or both), as described above.

[0134] like Figure 10 As further shown, in some aspects, process 1000 may include sending the recommendation (block 1020). For example, a UE (e.g., using Figure 14 The sending component 1404 and / or the communication manager 1406 depicted in can send the recommendation, as described above.

[0135] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0136] In a first aspect, generating the recommendation includes selecting the first codebook or the second codebook based at least in part on channel time-correlated measurements.

[0137] In a second aspect, alone or in combination with the first aspect, generating the recommendation includes selecting the first codebook or the second codebook based at least in part on Doppler measurements.

[0138] In a third aspect, alone or in combination with one or more of the first and second aspects, the Doppler measurement is based at least in part on sensor information from one or more sensors of the UE.

[0139] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on reference signal received power measurements from a plurality of TRPs.

[0140] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, generating the recommendation includes: selecting the first codebook or the second codebook based at least in part on SINR measurements from multiple TRPs.

[0141] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, generating the recommendation includes selecting the second codebook based at least in part on a BLER of the first codebook satisfying a BLER threshold.

[0142] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, generating the recommendation includes selecting the second codebook based at least in part on a throughput loss of the first codebook satisfying a loss threshold.

[0143] In a seventh aspect, alone or in combination with one or more of the first to seventh aspects, generating the recommendation includes: selecting the first codebook or the second codebook based at least in part on a power state of the UE or a processing state of the UE.

[0144] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on a quality of service requirement.

[0145] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the recommendation is an explicit message indicating selection of the first codebook or the second codebook.

[0146] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, sending the recommendation includes sending a threshold number of NACKs.

[0147] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, sending the recommendation includes sending a preferred codebook that is different from the codebook configuration.

[0148] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, sending the recommendation includes adjusting signaling indicating a request for codebook switching.

[0149] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 1000. In some embodiments, the process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be executed in parallel.

[0150] Figure 11 is a diagram illustrating an example process 1100, for example, performed by a network entity, in accordance with the present disclosure. The example process 1100 is an example in which a network entity (eg, network node 110, network entity 810) performs operations associated with codebook selection.

[0151] like Figure 11 As shown, in some aspects, process 1100 may include receiving a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis (block 1110). For example, a network entity (e.g., using Figure 14 The receiving component 1402 and / or the communication manager 1406 depicted in the figure may receive a recommendation for a first codebook or a second codebook, wherein the first codebook is used for a single TRP and does not include a TD basis or a DD basis, and the second codebook is used for multiple TRPs or includes a TD basis or a DD basis, as described above.

[0152] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include sending a codebook configuration based at least in part on the recommendation (block 1120). For example, a network entity (e.g., using Figure 14 The transmitting component 1404 and / or the communication manager 1406 depicted in FIG may transmit a codebook configuration based at least in part on the recommendation, as described above.

[0153] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0154] In a first aspect, the recommendation comprises an explicit physical uplink control channel message indicating selection of the first codebook or the second codebook.

[0155] In a second aspect, alone or in combination with the first aspect, receiving the recommendation includes receiving a threshold number of NACKs.

[0156] In a third aspect, alone or in combination with one or both of the first and second aspects, receiving the recommendation includes receiving a preferred codebook that is different from the codebook configuration.

[0157] In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving the recommendation includes receiving signaling adapted to indicate a request for a codebook switch.

[0158] although Figure 11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Figure 11 1100. In some embodiments, the process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be executed in parallel.

[0159] Figure 12 is a diagram illustrating an example process 1200, for example, performed by a UE, according to the present disclosure. Example process 1200 is an example in which a UE (eg, UE 120, UE 820) performs operations associated with TD base selection or DD base selection.

[0160] like Figure 12 As shown, in some aspects, process 1200 may include receiving a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions (block 1210). Figure 14 The receiving component 1402 and / or the communication manager 1406 depicted in FIG may receive a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions, as described above.

[0161] like Figure 12 As further shown in FIG. 1 , in some aspects, process 1200 may include selecting the TD basis or DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configured conditions (block 1220). Figure 14 The communication manager 1406 depicted in FIG) may select the TD basis or DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configured conditions, as described above.

[0162] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0163] In a first aspect, the one or more configuration conditions include an offset between a CSI measurement result or reporting instance and a codebook application time slot.

[0164] In a second aspect, alone or in combination with the first aspect, the one or more configuration conditions include a codebook size in the TD basis or the DD basis.

[0165] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more configuration conditions include a channel correlation time.

[0166] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the one or more configuration conditions include a UE-perceived Doppler profile.

[0167] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more configuration conditions include reporting overhead configuration or resource configuration.

[0168] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more configuration conditions include QoS requirements.

[0169] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the codebook structure indicates a preferred preference order for the TD base or the DD base or a codebook structure preferred by the UE.

[0170] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1200 includes sending a report of the selected TD basis or DD basis for the codebook.

[0171] although Figure 12 Example blocks of process 1200 are shown, but in some aspects, process 1200 may include Figure 12 1200. In some embodiments, the process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be executed in parallel.

[0172] Figure 13 is a diagram illustrating an example process 1300, for example, performed by a network entity, in accordance with the present disclosure. The example process 1300 is an example in which a network entity (eg, network node 110, network entity 810) performs operations associated with codebook selection.

[0173] like Figure 13As shown, in some aspects, process 1300 may include generating a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions (block 1310). Figure 15 The communication manager 1506 depicted in FIG. 15 may generate a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions, as described above.

[0174] like Figure 13 As further shown, in some aspects, process 1300 may include sending the codebook structure (block 1320). For example, a network entity (e.g., using Figure 15 The sending component 1504 and / or the communication manager 1506 depicted in can send the codebook structure, as described above.

[0175] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0176] In one aspect, process 1300 includes receiving a report of a selected TD basis or DD basis associated with the codebook structure.

[0177] although Figure 13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Figure 13 1300. In some embodiments, the process 1300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1300 may be executed in parallel.

[0178] Figure 14 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a UE (e.g., UE 120, UE 820), or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402, a sending component 1404, and / or a communication manager 1406, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is in conjunction with Figure 1 As shown, the device 1400 can utilize a receiving component 1402 and a sending component 1404 to communicate with another device 1408, such as a UE or a network node (such as a CU, DU, RU, or base station).

[0179] In some aspects, the apparatus 1400 may be configured to perform the Figures 1 to 9Additionally or alternatively, the apparatus 1400 may be configured to perform one or more of the processes described herein, such as Figure 10 The process of 1000 Figure 12 In some aspects, Figure 14 The device 1400 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Figure 14 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0180] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1408. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0181] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the apparatus 1408. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1408. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmitting component 1404 can be co-located with the receiving component 1402 in a transceiver.

[0182] The communications manager 1406 can support the operation of the receiving component 1402 and / or the sending component 1404. For example, the communications manager 1406 can receive information associated with configuring the receipt of communications by the receiving component 1402 and / or the sending of communications by the sending component 1404. Additionally or alternatively, the communications manager 1406 can generate and / or provide control information to the receiving component 1402 and / or the sending component 1404 to control the receipt and / or sending of communications.

[0183] In some aspects, the communication manager 1406 can generate a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. The sending component 1404 can send the recommendation.

[0184] In some aspects, receiving component 1402 may receive a codebook structure for selecting a TD basis or a DD basis for a codebook based at least in part on one or more configuration conditions. Communication manager 1406 may select the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions. Transmitting component 1404 may transmit a report of the selected TD basis or the DD basis for the codebook.

[0185] Figure 14 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 14 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 14 Two or more components shown may be implemented in a single component, or Figure 14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The illustrated set of components (one or more) may be described as being executable by Figure 14 Another group of components is shown performing one or more functions.

[0186] Figure 15 1 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a network entity (e.g., network node 110, network entity 810), or a network entity may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502, a sending component 1504, and / or a communication manager 1506, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1506 is a communication manager that is configured to communicate with one another. Figure 1As shown, the apparatus 1500 can utilize a receiving component 1502 and a sending component 1504 to communicate with another apparatus 1508, such as a UE or a network node (such as a CU, DU, RU, or base station).

[0187] In some aspects, the apparatus 1500 may be configured to perform the Figures 1 to 9 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more of the processes described herein, such as Figure 11 Process 1100, Figure 13 In some aspects, Figure 15 The illustrated apparatus 1500 and / or one or more components may include a combination of Figure 2 Additionally or alternatively, Figure 15 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0188] Receive component 1502 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from device 1508. Receive component 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receive component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of device 1500. In some aspects, receive component 1502 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0189] The transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1508. In some aspects, one or more other components of the apparatus 1500 may generate communications and may provide the generated communications to the transmitting component 1504 for transmission to the apparatus 1508. In some aspects, the transmitting component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1508. In some aspects, the transmitting component 1504 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmitting component 1504 can be co-located with the receiving component 1502 in a transceiver.

[0190] The communications manager 1506 can support the operation of the receiving component 1502 and / or the sending component 1504. For example, the communications manager 1506 can receive information associated with configuring the receipt of communications by the receiving component 1502 and / or the sending of communications by the sending component 1504. Additionally or alternatively, the communications manager 1506 can generate and / or provide control information to the receiving component 1502 and / or the sending component 1504 to control the receipt and / or sending of communications.

[0191] In some aspects, receiving component 1502 may receive a recommendation for a first codebook for a single TRP and not including a TD basis or a DD basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis. Transmitting component 1504 may transmit a codebook configuration based at least in part on the recommendation.

[0192] In some aspects, the communication manager 1506 can generate a codebook structure for selecting a TD basis or a DD basis for the codebook based at least in part on one or more configuration conditions. The transmitting component 1504 can transmit the codebook structure. The receiving component 1502 can receive a report of the selected TD basis or DD basis associated with the codebook structure.

[0193] Figure 15 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 15 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 15 Two or more components shown may be implemented in a single component, or Figure 15 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 15The illustrated set of components (one or more) may be described as being executable by Figure 15 Another group of components is shown performing one or more functions.

[0194] The following provides an overview of some aspects of the disclosure:

[0195] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: generating a recommendation for a first codebook or a second codebook, wherein the first codebook is used for a single transmit receive point (TRP) and does not include a time domain (TD) basis or a Doppler domain (DD) basis, and the second codebook is used for multiple TRPs or includes a TD basis or a DD basis; and sending the recommendation.

[0196] Aspect 2: The method of aspect 1, wherein generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on channel time-correlated measurement results.

[0197] Aspect 3: The method according to any one of aspects 1 to 2, wherein generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on Doppler measurements.

[0198] Aspect 4: The method of aspect 3, wherein the Doppler measurement result is based at least in part on sensor information from one or more sensors of the UE.

[0199] Aspect 5: The method according to any one of aspects 1 to 4, wherein generating the recommendation includes: selecting the first codebook or the second codebook based at least in part on reference signal received power measurement results from multiple TRPs.

[0200] Aspect 6: The method according to any one of aspects 1 to 5, wherein generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on signal to interference plus noise ratio measurements from multiple TRPs.

[0201] Aspect 7: The method according to any one of aspects 1 to 6, wherein generating the recommendation comprises: selecting the second codebook based at least in part on a block error rate (BLER) of the first codebook satisfying a BLER threshold.

[0202] Aspect 8: The method according to any one of aspects 1 to 7, wherein generating the recommendation comprises selecting the second codebook based at least in part on a throughput loss of the first codebook satisfying a loss threshold.

[0203] Aspect 9: The method according to any one of aspects 1 to 8, wherein generating the recommendation comprises: selecting the first codebook or the second codebook based at least in part on a power state of the UE or a processing state of the UE.

[0204] Aspect 10: The method according to any one of aspects 1 to 9, wherein generating the recommendation comprises selecting the first codebook or the second codebook based at least in part on a quality of service requirement.

[0205] Aspect 11: The method according to any one of aspects 1 to 10, wherein the recommendation is an explicit message indicating the selection of the first codebook or the second codebook.

[0206] Aspect 12: The method according to any one of aspects 1 to 11, wherein sending the recommendation comprises sending a threshold number of negative acknowledgements.

[0207] Aspect 13: The method according to any one of aspects 1 to 12, wherein sending the recommendation comprises: sending a preferred codebook that is different from the codebook configuration.

[0208] Aspect 14: The method according to any one of aspects 1 to 13, wherein sending the recommendation comprises: adjusting signaling for indicating a request for codebook switching.

[0209] Aspect 15: A method of wireless communication performed by a network entity, the method comprising: receiving a recommendation for a first codebook or a second codebook, wherein the first codebook is used for a single transmit receive point (TRP) and does not include a time domain (TD) basis or a Doppler domain (DD) basis, and the second codebook is used for multiple TRPs or includes a TD basis or a DD basis; and sending a codebook configuration based at least in part on the recommendation.

[0210] Aspect 16: The method of aspect 15, wherein the recommendation comprises an explicit physical uplink control channel message indicating selection of the first codebook or the second codebook.

[0211] Aspect 17: The method according to any one of aspects 15 to 16, wherein receiving the recommendation comprises: receiving a threshold number of negative acknowledgements.

[0212] Aspect 18: The method according to any one of aspects 15 to 17, wherein receiving the recommendation comprises: receiving a preferred codebook different from the codebook configuration.

[0213] Aspect 19: The method according to any one of aspects 15 to 18, wherein receiving the recommendation comprises receiving signaling adapted to indicate a request for a codebook switch.

[0214] Aspect 20: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a codebook structure for selecting a time domain (TD) basis or a Doppler domain (DD) basis for a codebook based at least in part on one or more configuration conditions; and selecting the TD basis or the DD basis for the codebook based at least in part on a comparison of one or more current conditions with the one or more configuration conditions.

[0215] Aspect 21: The method according to aspect 20, wherein the one or more configuration conditions include an offset between a channel state information measurement result or reporting instance and a codebook application time slot.

[0216] Aspect 22: The method according to any one of aspects 20 to 21, wherein the one or more configuration conditions include a codebook size in the TD basis or the DD basis.

[0217] Aspect 23: The method according to any one of aspects 20 to 22, wherein the one or more configuration conditions include a channel correlation time.

[0218] Aspect 24: The method according to any one of aspects 20 to 23, wherein the one or more configuration conditions include a Doppler profile perceived by the UE.

[0219] Aspect 25: The method according to any one of aspects 20 to 24, wherein the one or more configuration conditions include reporting overhead configuration or resource configuration.

[0220] Aspect 26: The method according to any one of aspects 20 to 25, wherein the one or more configuration conditions include quality of service requirements.

[0221] Aspect 27: The method according to any one of aspects 20 to 26, wherein the codebook structure indicates a preferred preference order for the TD basis or the DD basis or a codebook structure preferred by the UE.

[0222] Aspect 28: The method according to any one of aspects 20 to 27, further comprising: sending a report of the selected TD basis or DD basis for the codebook.

[0223] Aspect 29: A method of wireless communication performed by a network entity, the method comprising: generating a codebook structure for selecting a time domain (TD) basis or a Doppler domain (DD) basis for a codebook based at least in part on one or more configuration conditions; and transmitting the codebook structure.

[0224] Aspect 30: The method according to aspect 29, the method comprising: receiving a report of the selected TD basis or DD basis associated with the codebook structure.

[0225] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.

[0226] Aspect 32: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 30.

[0227] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0228] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

[0229] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.

[0230] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0231] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0232] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0233] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0234] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: generating a recommendation for a first codebook for a single transmit receive point (TRP) and not including a time domain (TD) basis or a Doppler domain (DD) basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis; and The recommendation is sent.

2. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: when generating the recommendation, select the first codebook or the second codebook based at least in part on a channel time-correlated measurement result.

3. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: select the first codebook or the second codebook based at least in part on Doppler measurements when generating the recommendation. 4 . The UE of claim 3 , wherein the Doppler measurement result is based at least in part on sensor information from one or more sensors of the UE.

5. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: select the first codebook or the second codebook based at least in part on reference signal received power measurements from a plurality of TRPs when generating the recommendation.

6. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: select the first codebook or the second codebook based at least in part on signal to interference plus noise ratio measurements from a plurality of TRPs when generating the recommendation.

7. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: when generating the recommendation, select the second codebook based at least in part on a block error rate (BLER) of the first codebook satisfying a BLER threshold.

8. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to: when generating the recommendation, select the second codebook based at least in part on a throughput loss of the first codebook satisfying a loss threshold.

9. The UE of claim 1 , wherein the memory comprises instructions executable by the one or more processors to cause the UE to, when generating the recommendation, select the first codebook or the second codebook based at least in part on a power state of the UE or a processing state of the UE.

10. The UE of claim 1, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: select the first codebook or the second codebook based at least in part on a quality of service requirement when generating the recommendation. The UE of claim 1 , wherein the recommendation is an explicit message indicating selection of the first codebook or the second codebook.

12. The UE of claim 1, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: send a threshold number of negative acknowledgements when sending the recommendation.

13. The UE of claim 1, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: send a preferred codebook different from a codebook configuration when sending the recommendation.

14. The UE of claim 1, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: adjust signaling indicating a request for a codebook switch when sending the recommendation.

15. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network entity to: receiving a recommendation for a first codebook for a single transmit receive point (TRP) and not including a time domain (TD) basis or a Doppler domain (DD) basis, or a second codebook for multiple TRPs or including a TD basis or a DD basis; and The sending is based at least in part on the recommended codebook configuration.

16. The network entity of claim 15, wherein the recommendation comprises an explicit physical uplink control channel message indicating selection of the first codebook or the second codebook.

17. The network entity of claim 15, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: receive a threshold number of negative acknowledgements upon receiving the recommendation.

18. The network entity of claim 15, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: upon receiving the recommendation, receive a preferred codebook that is different from a codebook configuration.

19. The network entity of claim 15, wherein the memory comprises instructions executable by the one or more processors to cause the UE to: upon receiving the recommendation, receive signaling adapted to indicate a request for a codebook switch.

20. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the UE to: receiving a codebook structure for selecting a time domain (TD) basis or a Doppler domain (DD) basis for the codebook based at least in part on one or more configuration conditions; as well as The TD basis or the DD basis for the codebook is selected based at least in part on a comparison of one or more current conditions and the one or more configured conditions.

21. The UE of claim 20, wherein the one or more configuration conditions include an offset between a channel state information measurement result or reporting instance and a codebook application time slot.

22. The UE of claim 20, wherein the one or more configuration conditions include a codebook size in the TD basis or the DD basis.

23. The UE of claim 20, wherein the one or more configuration conditions include a channel correlation time.

24. The UE of claim 20, wherein the one or more configuration conditions include a UE-perceived Doppler profile.

25. The UE of claim 20, wherein the one or more configuration conditions include reporting overhead configuration or resource configuration.

26. The UE of claim 20, wherein the one or more configuration conditions include a quality of service requirement. 27 . The UE according to claim 20 , wherein the codebook structure indicates a preferred preference order for the TD basis or the DD basis or a codebook structure preferred by the UE.

28. The UE of claim 20, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to: transmit a report of the selected TD basis or DD basis for the codebook.

29. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network entity to: generating a codebook structure for selecting a time domain (TD) basis or a Doppler domain (DD) basis for the codebook based at least in part on one or more configuration conditions; as well as The codebook structure is sent.

30. The network entity of claim 29, wherein the memory further comprises instructions executable by the one or more processors to cause the network entity to: receive a report of the selected TD basis or DD basis associated with the codebook structure.

Images