Non-zero coefficient selection and strongest coefficient indicator for coherent joint transmission channel state information

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive channel state information (CSI) reference signals (CSI-RSs) from multiple transmit receive points (TRPs) and may perform measurements on the CSI-RSs to identify appropriate configurations for communicating with the TRPs. The UE may also send a CSI report to a network entity such that the network entity may identify an appropriate configuration at the TRP for communicating with the UE. The CSI reporting may include a non-zero coefficient (NZC) bitmap based on measurements of the CSI-RS using a frequency domain (FD) base and a spatial domain (SD) base associated with each of the TRPs. The described techniques provide block-based NZC bitmap reporting that may leverage a partial overlap in the FD bases of the different TRPs to reduce NZC bitmap size.

Description

Technical Field

[0001] The following relates to wireless communications, including non-zero coefficient selection and strongest coefficient indicators for coherent joint transmission of channel state information. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses that support non-zero coefficient selection and strongest coefficient indicators (SCI) for coherent joint transmission of channel state information. A user equipment (UE) may receive channel state information (CSI) reference signals (CSI-RS) from multiple transmit receive points (TRPs) and may perform measurements on these CSI-RS to identify a suitable configuration for communicating with the TRPs. The UE may also send a CSI report to a network entity so that the network entity can identify a suitable configuration at the TRP for communicating with the UE. The CSI report may include a non-zero coefficient (NZC) bitmap based on measurements of the CSI-RS using a frequency domain (FD) basis and a spatial domain (SD) basis associated with each TRP in the TRPs. The described technology provides a block-based NZC bitmap report that can reduce the NZC bitmap size by exploiting overlap in the FD basis of different TRPs. Due to the time delay difference between receiving CSI-RS from the first TRP and the second TRP at the UE (for example, due to the position difference in the TRP), the FD basis selection for the first TRP and the second TRP may be reported separately, thereby reducing the size of the NZC bitmap by utilizing the overlap in the FD basis between the first TRP and the second TRP. In order for the UE and the network entity to identify the NZC bitmap format, both the UE and the network entity should know the number of selected FD basis and SD basis reported per TRP. Therefore, the control signaling indicating the multi-TRP configuration of the UE may indicate the number of FD basis and / or SD basis per TRP, or the UE may indicate the number of FD basis and / or SD basis per TRP in the uplink control information (UCI) conveying the NZC bitmap.

[0004] A method for wireless communication at a UE is described. The method may include: receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with a network entity via a first TRP and a second TRP associated with the network entity; receiving a CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration; and sending a UCI message to the network entity including an NZC bitmap, the NZC bitmap being based on a measurement of the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0005] An apparatus for wireless communication is described. The apparatus may include: a memory; a transceiver; and at least one processor of a UE, the at least one processor being coupled to the memory and the transceiver. The at least one processor may be configured to: receive control signaling indicating a multi-TRP configuration for use by the UE to communicate with a network entity via a first TRP and a second TRP associated with the network entity; receive a CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration; and send a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with a network entity via a first TRP and a second TRP associated with the network entity; a component for receiving a CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration; and a component for sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to perform the following operations: receive control signaling indicating a multi-TRP configuration for the UE to use to communicate with the network entity via a first TRP and a second TRP associated with the network entity; receive a CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration; and send a UCI message to the network entity including an NZC bitmap, the NZC bitmap being based on a measurement of the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including one or more fields indicating a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases may be based on the first number and the second number.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including one or more fields indicating a selection of the first TRP and the second TRP from a set of multiple TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the set of multiple TRPs.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of FD bases per TRP may be inversely correlated to the number of TRPs selected in the UCI message.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of FD bases per TRP may be inversely correlated to the number of layers reported in the UCI message.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including one or more fields indicating a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases may be based on the first number and the second number.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for: receiving an indication of a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases may be based on the first number and the second number.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for: receiving an indication of a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases may be based on the first number and the second number.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including a field set indicating a layer-specific FD basis selection on a per-TRP basis.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for: receiving the control signaling indicating that the first TRP and the second TRP share the same layer-specific FD base selection.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for sending a first incremental amplitude associated with the first TRP and a second incremental amplitude associated with the second TRP, wherein the first incremental amplitude and the second incremental amplitude may exceed the strongest coefficient.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including a field set indicating a layer common SD base selection based on each TRP.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for: receiving the control signaling indicating that the first TRP and the second TRP share the same layer common SD base selection.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first number of FD groups associated with the first TRP may be the same as a second number of FD groups associated with the second TRP.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending the UCI message including a field indicating a selection of one of the first TRP or the second TRP from a set of multiple TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the set of multiple TRPs, and wherein the selection of one of the first TRP or the second TRP includes selection of both the first TRP and the second TRP.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include operations, features, components, or instructions for: sending a single incremental magnitude associated with the first TRP and the second TRP, where the single incremental magnitude may exceed the strongest coefficient.

[0023] A method for wireless communication at a network entity is described. The method may include: outputting control signaling to a UE indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity; outputting a CSI-RS according to the multi-TRP configuration via the first TRP and the second TRP; and obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0024] An apparatus for wireless communication is described. The apparatus may include: a memory; and at least one processor of a network entity, the at least one processor being coupled to the memory. The at least one processor may be configured to: output to a UE control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity; output a CSI-RS according to the multi-TRP configuration via the first TRP and the second TRP; and obtain from the UE and in response to the CSI-RS a UCI message including an NZC bitmap, wherein a size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0025] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for outputting control signaling to a UE indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity; a component for outputting a CSI-RS according to the multi-TRP configuration via the first TRP and the second TRP; and a component for obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to perform the following operations: output control signaling to a UE indicating a multi-TRP configuration for the UE to use to communicate with the network entity via a first TRP and a second TRP associated with the network entity; output a CSI-RS according to the multi-TRP configuration via the first TRP and the second TRP; and obtain a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the UCI message may include operations, features, components, or instructions for: obtaining the UCI message including one or more fields indicating a selection of the first TRP and the second TRP from a set of multiple TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the set of multiple TRPs.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of FD bases per TRP may be inversely correlated to the number of layers reported in the UCI message.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the UCI message may include operations, features, components, or instructions for: obtaining the UCI message including one or more fields indicating a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases may be based on the first number and the second number.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the control signaling may include operations, features, components, or instructions that may include: outputting an indication of a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases may be based on the first number and the second number.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the control signaling may include operations, features, components, or instructions for: outputting an indication of a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of FD bases may be based on the first number and the second number.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the UCI message may include operations, features, components, or instructions for: obtaining the UCI message including a field set indicating a layer-specific FD basis selection on a per-TRP basis.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the UCI message may include operations, features, components, or instructions for: outputting the UCI message including a field set indicating a layer common SD base selection based on each TRP. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 An example of a wireless communication system supporting non-zero coefficient (NZC) selection and strongest coefficient indicator (SCI) for coherent joint transmission (CJT) channel state information (CSI) in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 2 An example of a network architecture supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 3 An example of supporting NZC selection for CJT CSI and non-CJT for SCI according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 4 An example of supporting NZC selection for CJT CSI and non-CJT for SCI according to one or more aspects of the present disclosure is illustrated.

[0038] Figure 5 An example of a precoding matrix indicated in a CSI report for multiple layers supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated.

[0039] Figure 6 Examples of orientations of different antenna panels for supporting NZC selection for CJT CSI and CJT for SCI according to one or more aspects of the present disclosure are illustrated.

[0040] Figure 7 An example of supporting NZC selection for CJT CSI and selection of spatial basis and frequency basis for SCI according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 8 An example of a frequency domain basis selection method supporting NZC selection for CJT CSI and SCI according to one or more aspects of the present disclosure is illustrated.

[0042] Fig. 9 An example of supporting NZC selection for CJT CSI and selection of spatial basis and frequency basis for SCI according to one or more aspects of the present disclosure is illustrated.

[0043] Fig.10 An example of a UCI format supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated.

[0044] Fig.11 An example of a process flow supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated.

[0045] Fig.12 and Fig.13 A block diagram of a device supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown.

[0046] Fig.14 A block diagram of a communication manager supporting NZC selection and SCI for CJT CSI is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.15 A diagram of a system including a device supporting NZC selection and SCI for CJT CSI in accordance with one or more aspects of the present disclosure is shown.

[0048] Fig.16 and Fig.17 A block diagram of a device supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown.

[0049] Fig.18 A block diagram of a communication manager supporting NZC selection and SCI for CJT CSI is shown in accordance with one or more aspects of the present disclosure.

[0050] Fig.19 A diagram of a system including a device supporting NZC selection and SCI for CJT CSI in accordance with one or more aspects of the present disclosure is shown.

[0051] Figure 20 to Figure 23 A flow chart illustrating a method of supporting NZC selection and SCI for CJT CSI is shown. DETAILED DESCRIPTION

[0052] In some wireless communication systems, a user equipment (UE) may communicate with multiple transmit receive points (TRPs) to improve throughput or improve the reliability of communications. For example, when operating in a multi-TRP operating mode, the UE may receive different downlink data from multiple TRPs simultaneously, resulting in improved throughput, or the UE may receive the same downlink data from multiple TRPs, resulting in improved reliability (e.g., a higher chance of the UE receiving the data). The network may implement coherent joint transmission (CJT), which refers to the transmission of data including joint precoding at different TRPs or separate precoding at different TRPs with controlled phases and coefficients, which may reduce the number of layers used for transmission from multiple TRPs. In such systems, the TRP may send a channel state information (CSI) reference signal (CSI-RS) to the UE, and the UE may perform measurements on the CSI-RS to identify a suitable configuration for communicating with the TRP. The UE may also send a CSI report to a network entity so that the network entity can identify a suitable configuration at the TRP for communicating with the UE. The CSI report may include a non-zero coefficient (NZC) bitmap based on the measurement of the CSI-RS using a frequency domain (FD) basis and a spatial domain (SD) basis associated with each TRP in the TRP. Some TRPs may share some FD basis. Reporting the NZC bitmap without considering the overlap in the FD basis may increase communication overhead.

[0053] Various aspects of the present disclosure relate to block-based NZC bitmap reporting that can reduce the NZC bitmap size by exploiting the overlap in FD bases of different TRPs. Due to the time delay difference between receiving CSI-RS from a first TRP and a second TRP at a UE (e.g., due to a position difference in the TRP), the FD base selection for the first TRP and the second TRP can be reported separately, thereby reducing the size of the NZC bitmap by exploiting the overlap in the FD base between the first TRP and the second TRP. In order for the UE and the network entity to identify the NZC bitmap format, both the UE and the network entity should know the number of selected FD bases and SD bases reported per TRP. Therefore, the control signaling indicating the UE's multi-TRP configuration may indicate the number of FD bases and / or SD bases per TRP, or the UE may indicate the number of FD bases and / or SD bases per TRP in the uplink control information (UCI) that conveys the NZC bitmap.

[0054] Various aspects of the present disclosure are first described in the context of a wireless communication system. Examples of processes and signaling exchanges that support NZC selection and the strongest coefficient indicator (SCI) for CJT CSI are then described. Various aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow charts involving NZC selection and SCI for CJT CSI, and various aspects of the present disclosure are described with reference to the apparatus diagrams, system diagrams, and flow charts.

[0055] Figure 1 An example of a wireless communication system 100 that supports NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0056] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0057] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0058] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0059] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0060] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0061] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0062] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0063] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0064] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104, and one or more UEs 115. The IAB host may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB hosts) via an Xn-C interface (which may be an example of part of a backhaul link).

[0065] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB host may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0066] For example, the IAB node 104 may be referred to as a parent node that supports communications for a child IAB node or as a child node associated with the IAB host, or both. The IAB host may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay the transmission to the UE 115 via the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0067] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support NZC selection and SCI for CJT CSI as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0068] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0069] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0070] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive" or "communicate", "output" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0071] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0072] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0073] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0074] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0075] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0076] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0077] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0078] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0079] Carrier multiplexing physical channels may be used for communication according to various techniques. Physical control channels and physical data channels may be multiplexed, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0080] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0081] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0082] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0083] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0084] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0085] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0086] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0087] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0088] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0089] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0090] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0091] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0092] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region that uses a spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may be facilitated using an antenna array within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

[0093] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0094] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0095] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0096] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0097] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0098] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0099] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), CSI reference signals (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0100] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0101] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0102] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0103] In the wireless communication system 100, the UE 115 may communicate with multiple TRPs to improve throughput or improve the reliability of communication. For example, when operating in a multi-TRP operating mode, the UE 115 may receive different downlink data from multiple TRPs simultaneously, resulting in improved throughput, or the UE 115 may receive the same downlink data from multiple TRPs, resulting in improved reliability (e.g., a higher chance of the UE 115 receiving the data). The network may implement coherent joint transmission (CJT), which refers to the transmission of data including joint precoding at different TRPs or separate precoding at different TRPs with controlled phases and coefficients, which can reduce the number of layers used for transmission from multiple TRPs. CJT-enhanced Type II CSI for CJT can enable a larger number of ports using distributed TRPs or antenna panels in low frequency bands. For example, in some cases, for a single TRP or antenna panel with 32 ports, the antenna size may be too large for practical deployment.

[0104] In a system implementing CJT, the TRP may send a CSI-RS to the UE 115, and the UE 115 may perform measurements on the CSI-RS to identify a suitable configuration for communicating with the TRP. The UE 115 may also send a CSI report to the network entity 105 so that the network entity 105 may identify a suitable configuration at the TRP for communicating with the UE 115. The CSI report may include an NZC bitmap based on measurements of the CSI-RS using an FD basis and an SD basis associated with each TRP in the TRP. Some TRPs may share some FD basis. Reporting the NZC bitmap without considering overlaps in the FD basis may increase communication overhead.

[0105] Block-based NZC bitmap reporting can reduce the NZC bitmap size by exploiting the overlap in FD bases of different TRPs. Due to the time delay difference between receiving CSI-RS from the first TRP and the second TRP at the UE 115 (for example, due to the position difference in the TRP), the FD base selection for the first TRP and the second TRP can be reported separately, thereby reducing the size of the NZC bitmap by exploiting the overlap in the FD base between the first TRP and the second TRP. In order for the UE 115 and the network entity 105 to identify the NZC bitmap format, both the UE 115 and the network entity 105 should know the number of selected FD bases and SD bases reported per TRP. Therefore, the control signaling indicating the multi-TRP configuration of the UE 115 may indicate the number of FD bases and / or SD bases per TRP, or the UE 115 may indicate the number of FD bases and / or SD bases per TRP in the UCI that conveys the NZC bitmap.

[0106] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with the core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0107] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0108] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a 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, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0109] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional splits, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0110] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., 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 functional splitting (such as lower layer functional splitting). In such an architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by corresponding DU 165-a. In some examples, such a configuration may enable DU 165-a and CU160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0111] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) to perform network entity lifecycle management (e.g., instantiating virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate (e.g., via an O1 interface) with components configured according to a 4G RAN. Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0112] The non-RT RIC 175-a may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b.

[0113] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (e.g., an A1 policy).

[0114] Figure 3 An example of a non-CJT 300 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated. Non-coherent joint transmission may be based on spatial division multiplexing (SDM), and data may be pre-coded separately at different TRPs. The first TRP 305 may use a pre-decoder V A For data X A Pre-decoding is performed, and the second TRP 310 can use the pre-decoder V B For data X B Pre-decoder for pre-decoding data sent at TRP The rank of data transmission (e.g., V A :4×1,V B :4×2). In addition, the rank of data transmission (e.g., X A :1×1,X B :2×1) sends the data X(RI) to be pre-decoded for the data from TRP TRP ×1) are mapped to different layers. Therefore, the pre-decoded data sent from the first TRP 205 and the second TRP 305 can be given by Formula 1.

[0115]

[0116] Figure 4 An example of a CJT 400 supporting NZC selection and SCI for CJT CSI in accordance with one or more aspects of the present disclosure is illustrated. Coherent joint transmission may refer to transmission including data precoded jointly at different TRPs or separately precoded at different TRPs with controlled phases and coefficients.

[0117] In the example of CJT 400, data may be jointly pre-coded at different TRPs (eg, pre-coded in a fully joint manner). The first TRP 405 may use a pre-coder V A The data X is pre-decoded, and the second TRP 410 can use the pre-decoder V B Pre-decode data X. Pre-decoder for pre-decoding data sent at TRP The rank of data transmission (e.g., V A :4×2,V b :4×2). In addition, the rank of data transmission (e.g., X A :2×1) sends the pre-decoded data X(RI) to be sent for the data from the first TRP 405 and the second TRP 410 joint ×1) is mapped to different layers. Therefore, the pre-decoded data sent from the first TRP 305 and the second TRP 310 can be given by Formula 2.

[0118]

[0119] Figure 5 An example of a precoding matrix indicated in a CSI report for multiple layers 500 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated. The UE 115 may indicate a precoding matrix for each of the multiple layers in the CSI report, and the CSI report may support up to a rank of four (i.e., four layers). For each layer, the precoder across the number of n3 precoding matrix indicator (PMI) subbands may be N t ×N3 matrix W (e.g.,

[0120] The number of PMI subbands N3 may be determined by the number of channel quality indicator (CQI) subbands and the number of PMI subbands per CQI subband (e.g., R={1, 2}). In some cases, the number of CQI subbands may be determined by a higher layer parameter (e.g., csi-ReportingBand), and the number of PMI subbands per CQI subband may also be configured (e.g., configured by the parameter numberOfPMISubbandsPerCQISubband). For R=1, N3 may be equal to the number of CQI subbands (e.g., with possible values ​​{1, 2, ..., 19}). For R=2, possible values ​​of N3 may be {1, 2, ..., 37}. In some cases, the PMI subband size may be finer (e.g., half) than the CQI subband size, which is better than the PMI subband size equal to the CQI subband size. For edge CQI subbands, the UE 115 may report one PMI if the number of resource blocks is less than or equal to the nominal CQI subband size divided by 2. Alternatively, for edge CQI subbands, the UE 115 may report two PMIs if the number of resource blocks is greater than the CQI subband size divided by 2. For other CQI subbands, the UE 115 may report two PMIs.

[0121] The SD basis W1 in the matrix (eg, a discrete Fourier transform (DFT) basis) may be N t ×2L matrix, where N t W1 may be common to all layers, N t It can be RRC configured (for example, N t =2N1O1N2o2, where o1 and O2 are oversampled), and L can be RRC configured (e.g., L={2,4,6}).

[0122] FD base W f (e.g., DFT basis) can be an M×N3 matrix, where M can refer to the number of FD bases, can be layer-specific, and M can be rank-pair specific (e.g., M1=M2, for rank={1,2}, and M3=M4, for rank={3,4}, where M1 or M3 is RRC configured).

[0123] coefficient It can be a 2L×M matrix and can be layer specific. For each layer, the UE 115 can report up to K0 non-zero coefficients (NZC), where K0 is RRC configured. Across all layers, the UE 115 can report up to 2K0 non-zero coefficients. Unreported coefficients can be set to zero, and the UE 115 can perform The coefficients are quantized.

[0124] For layer 1, UE 115 may The NZC of the transmission from the TRP can be quantized (e.g., layer-independent quantization). The NZC can be reported for two different polarizations of the transmission from the TRP. Formula 3 shows the coefficients An example of a matrix (e.g., for type IICSI quantification of ).

[0125]

[0126] At the first step, the UE 115 may report the index of the strongest coefficient (e.g., NZC), and the strongest coefficient may be used as a reference for the stronger polarization. The stronger polarization may refer to the polarization associated with the strongest coefficient, while the weaker polarization may be another polarization. If the strongest coefficient is one, the UE 115 may not quantize the coefficient. For example, the strongest coefficient in Formula 3 is the "1" in the first column. The strongest coefficient may be used as a reference for the stronger polarization. The UE 115 may also report the reference power of the weaker polarization. At the second step, the UE 115 may quantize the reference power of the weaker polarization with four bits from 0 dB in steps of -1.5 dB (in power). The UE 115 may also report the differential amplitude of each coefficient. The UE 115 may quantize the differential amplitude with three bits from 0 dB in steps of -3 dB (in power). The UE 115 may also report the phase quantization of each coefficient. The UE 115 may utilize a 16-phase shift keying (PSK) alphabet to quantize the phase.

[0127] The number of SD basis, FD basis and NZC to be reported by UE 115 can be given by Table 1.

[0128] Table 1: Number of SD bases, FD bases and NZC

[0129]

[0130] For the number of space domain bases, L = {2, 4, 6}. For the number of FD bases, and For the number of NZC, UE 115 may receive RRC signaling to configure a combination of K, p1, p3, β (eg, 1 out of 8).

[0131] As the number of TRPs that UE 115 may be configured to communicate with increases, the overhead of CSI reporting also increases (e.g., because UE 115 may report the SD basis, FD basis, and precoding coefficients for each TRP). That is, the CSI reporting overhead may increase with the number of TRPs (e.g., N TRP). However, in some cases, it may be appropriate to enable communication with a large number of TRPs or a large number of ports (e.g., for low frequency bands with distributed TRPs or panels). For example, for a single TRP or panel with, for example, 32 ports, the antenna array size may be too large for practical deployment. Therefore, the wireless communication system 100 can support efficient techniques for supporting communication with multiple TRPs while minimizing CSI reporting overhead.

[0132] Figure 6 An example of an orientation of different antenna panels of a CJT 600 for supporting NZC selection for CJT CSI and SCI according to one or more aspects of the present disclosure is illustrated. One or more TRPs can support coherent joint transmission with backhaul communications and synchronization between TRPs. In one aspect, a co-located TRP or antenna panel (e.g., within a site) can be used for coherent joint transmission. In example 600-a, the TRP can use multiple antenna panels with the same orientation for coherent joint transmission. In example 600-b, the TRP can use multiple antenna panels with different orientations (e.g., between sectors) for coherent joint transmission. On the other hand, a distributed TRP (e.g., between sites) can be used for coherent joint transmission. This aspect is described in example 600-c.

[0133] If a co-located TRP or antenna panel is used for CJT, the precoding matrix or predecoder used to precode the data can be selected from a joint codebook. The precoding matrix for example 600-a (where the TRP or antenna panel has a joint FD basis and SD basis) can be given by Equation 4, where the same SD basis selection matrix W_1 can be applied to both TRPs: TRP#A and TRP#B.

[0134]

[0135] The precoding matrix for example 600-b (where the TRP or antenna panel has a joint FD basis and a separate SD basis) is given by Equation 5.

[0136]

[0137] If distributed TRP is used for CJT (e.g., as illustrated in example 600-c), a precoding matrix or precoder for precoding data may be selected from separate codebooks (e.g., separate FD basis and SD basis), and common amplitude or phase coefficients may be added to the precoding matrix or precoder. Such a precoding matrix or precoder may be given by Formula 6.

[0138]

[0139] For Type II codebook refinement of CJT for multiple TRPs, the resulting codebook may be associated with parameters for basis reporting, including the number of basis vectors (e.g., SD and / or FD basis configuration), which may be configured by the network via higher layer signaling. The basis selection indicator (e.g., SD and / or FD basis selection) may also be a port of the CSI report. Quantized combining coefficients The SCI may be indicated as part of the CSI report.

[0140] Type II codebook refinement for CJT for multiple TRPs The coefficient quantization scheme, at least for N=2, may reuse the alphabets for amplitude and phase from the legacy per-coefficient quantization scheme. Additionally or alternatively, quantization of phase and quantization of differential amplitude relative to a reference amplitude (where the SCI determines the location of the reference amplitude), and where a reference is defined for each layer, and each set of coefficients may be reused from the legacy per-coefficient quantization scheme.

[0141] Figure 7 An example of supporting selection of a spatial basis and a frequency basis for CJT CSI 700 that supports selection of NZC and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated.

[0142] For joint codebook CJT, FD basis selection may be reported separately for different TRPs. FD basis selection may be reported separately to TRP A and TRP B by utilizing, for example, a delay difference τ between the reception of signals from TRP A and TRP B. Reporting FD basis selection for TRP A and TRP B separately may reduce overhead in the NZC selection bitmap by using a block-by-block (and in some cases 2-level) indication of NZC selection.

[0143] For example, example 705-a illustrates the case where M=7, and for each of TRP A and TRP B, L=6, and thus 2L=12. Example 705-b illustrates joint codebook FD basis selection for TRP A and TRP B. As illustrated in example 705-b, at least one of the FD bases of TRP A and TRP B may overlap.

[0144] Example 705-c illustrates separate codebook FD basis selection for TRP A and TRP B. In Example 705-c, a separate FD codebook is represented (e.g., where separate FD basis selection may be natural), and the FD basis columns do not overlap. For example, even when two TRPs (e.g., TRP A and TRP B) share the same selected FD basis, the shared FD basis is reported separately.

[0145] For the joint codebook, as shown in example 705-b, the bitmap size can be reduced by exploiting the delay difference τ and reporting the NZC selection on a block-by-block basis. For M=7 and L=6, the bitmap for the joint FD basis selection example 705-b will involve 2L*M=84 bits. For M=7 and L=6. Block-by-block reporting of the bitmap (e.g., reporting blocks 710-a and 710-b) will involve 2L1*M1+2L2*M2=48 bits. Therefore, block-by-block indication of NZC can reduce the bit overhead for reporting the NZC bitmap.

[0146] The difference between example 705-c and a joint codebook (eg, as shown in example 705-b) may be that for a separate codebook, Whether the NZC block in the matrix allows columns to overlap, so that even if two TRPs share the same chosen FD basis, they can still be reported separately.

[0147] For type IICJT CSI with (at least partially) shared FD basis between TRPs (e.g., for a joint codebook), the number of selected SD basis and FD basis (denoted as L for TRP n=1, ..., N, respectively) is n and M n ) can be per TRP configured by the network (e.g., via signaling from the network entity 105) or per TRP reported by the UE. For the case where the number of SD bases or FD bases is per TRP configured by the network, L n or M n The value of can be TRP-common or TRP-specific, for TRP n=1, ..., N. For the case where the number of SD bases or FD bases is reported per TRP by the UE, the configuration can be based on the total number across TRPs (e.g., Where L refers to the total number of SD bases across TRPs (n=1, ..., N) and M refers to the total number of FD bases across TRPs (n=1, .., N). Table 2 below lists the possible cases of whether the FD base or SD base is per TRP configured by the network or per TRP reported by the UE.

[0148] Table 2

[0149]

[0150] For the joint codebook, case 2 may be better than case 1, which may be better than case 4, which may be better than case 4. For SD basis, configuring the total number of SD basis may be better than per-TRP SB basis configuration. For FD basis, the network's per-TRP configuration may be better than the per-TRP reported by the UE situation.

[0151] For UE reported L n Situation, L n The value of may be reported (eg, determined) using CSI Part 1, as described herein with reference to Fig. 9 For example, the L in CSI part 1 may be used by the network entity n to determine the payload size of the SD base selection and NZC selection bitmap in CSI part 2. In some cases, L may be explicitly reported in CSI part 1. n In some cases, the network entity may implicitly determine L based on the TRP selection reported by the UE in CSI Part 1. n For example, where N TRPs are selected and / or reported, the N TRPs are divided equally into two halves: For the first (L mod N) TRP, and For the remaining TRPs, where L is the total number of configurations of the SD basis (eg, indicated by the network entity). For example, in the case of L=8 and N=3, for the first 2 selected TRPs, L1=L2=4, and for the last selected TRP, L3=3.

[0152] For network configuration L n or L reported by UE n In this case, the layer common SD basis selection indication in CSI part 2 may include a first field that indicates the oversampling group with log2 bits for each TRP (n=1, ..., N) separately (thus, a total of N log2O1O2 bits). n or L reported by UE n In this case, the layer common SD base selection indication in CSI part 2 may include a second field, which indicates, for each TRP (n=1, ..., N), from having The L selected in the N1N2 SD base n SD bases (so a total of units).

[0153] For UE reported M n In this case, CSI part 1 can be used to determine M n For example, the M in CSI part 1 may be used by the network entity nto determine the payload size of the FD basis selection and NZC selection bitmaps in CSI part 2. In some cases, M may be explicitly reported in CSI part 1. n In some cases, M may be determined implicitly by the network entity based on the TRP selection reported by the UE in CSI Part 1. n For example, in the case of selecting / reporting N TRPs: For the N TRPs, the common value n=1, ..., N, where M is the total number of configured FD bases, and γ≥1.

[0154] For network configuration M n Or M reported by UE n In order to maintain comparable UCI overhead for different numbers of TRPs selected, M n M may decrease with the number of TRPs (N) selected. To maintain comparable UCI overhead (e.g., number of layers) of rank, M n It can decrease with the rank.

[0155] For network configuration M n Or M reported by UE n In this case, the layer-specific FD basis selection indication may be included in CSI part 2. For each TRP (n=1, ..., N), the first field may indicate the window position of the window-based FD basis selection, respectively. For non-window-based FD basis selection, the first field may not exist. For each TRP (n=1, ..., N), the second field may indicate the selection of the FD basis (directly from the N3 total basis - for non-window-based FD basis selection, or from the indicated window - for window-based FD basis selection).

[0156] Figure 8 An example of a method 800 supporting NZC selection for CJT CSI and FD basis selection for SCI in accordance with one or more aspects of the present disclosure is illustrated.

[0157] FD basis selection (W f ) may be layer specific. And for each layer, the strongest coefficients may be aligned at FD basis 0. For example, FD basis selection method 800 illustrates FD basis index 805-a before index remapping and FD basis index 805-b after index remapping. Index 805-a and index 805-b illustrate an example of N3=37 and M=5 (e.g., window size 2M=10).

[0158] At the first step, for layer l, the FD base index of the strongest coefficient (before index remapping) can be expressed as It may not be reported in the CSI report. In the second step, the FD base index Relative to Remap (from the codebook) to Make m can be Make In the third step, the FR base index (after index remapping) may be reported. Reportable May not be reported with the strongest coefficient.

[0159] For each layer, the FD basis selection can be either direct 1-level or window-based 2-level, depending on the number of PMI subbands (N3). For N3≤19, the UE can (For each layer) directly report M-1 FD bases from N3-1 candidate FD bases. For N3>19, the UE may first The first bit reports the starting index of the intermediate set based on the window (selected from N3 down to 2M) and can then be selected from 2M-1 candidate FD bases The bits (for each layer) report M-1 FD bases. FD base 0 may always be selected (eg, because the strongest coefficients align at FD base 0).

[0160] Fig. 9 An example of supporting NZC selection for CJT CSI and selection of a spatial basis and a frequency basis 900 for SCI in accordance with one or more aspects of the present disclosure is illustrated.

[0161] Three types of TRP groups may be defined. In a first group type (e.g., type 1), TRPs within a group share the same FD basis selection indication in the CSI report. In a second group type (e.g., type 2), TRPs within a group share the same SD basis selection indication in the CSI report. In a third group type (e.g., type 3), TRPs within a group share the same FD and SD basis selection indication in the CSI report. The network may configure (e.g., may indicate in control signaling) the TRP group type of a TRP. TRPs within a type 3 TRP group and a type 2 TRP group may be considered for M n A TRP configured or reported. TRPs within a Type 3 TRP group and a Type 2 TRP group can be considered as a unit of TRP selection. For example, a 3-bit bitmap A, {B, C}, D of a 4-TRP, where {B, C} is configured as a Type 3 or Type 2 TRP group.

[0162] Example 905-a illustrates a case where TRP B and TRP C are included in a type 1 TRP group. Example 905-b illustrates a case where TRP B and TRP C are included in a type 2 or type 3 TRP group. As illustrated, TRPs within a TRP group (e.g., TRP B and TRP C in example 905-a or TRP B and TRP C in example 905-b) may share the same NZC selection bitmap ("Block: In Matrix”). An NZC bitmap can be associated with one or more incremental amplitudes on the SCI per polarization. As shown in example 905-a, a type 1 TRP group can be associated with more than one incremental amplitude (e.g., one incremental amplitude per TRP). As shown in example 905-b, a type 2 or type 3 TRP group can be associated with one incremental amplitude. For the TRP and polarization with the strongest coefficient, incremental amplitude = 0. The incremental amplitude refers to p in Equation 3 ref .

[0163] Fig.10 An example of a UCI format 1000 supporting NZC selection and SCI for CJT CSI in accordance with one or more aspects of the present disclosure is illustrated.

[0164] As described herein, UE 115 may send a CSI report to a network entity via a UCI message, which may use UCI format 1000. UCI format 1000 may include UCI part 1 1010 and UCI part 2 1030.

[0165] UCI part 1 1010 may include a rank indicator (RI) field 1015, a CQI field 1020, and a number of NZCs (NNZC) field 1025. The NNZC field 1025 may indicate the total number of NZCs across all layers. The bit width of the NNZC field 1025 may be log22K0 bits.

[0166] UCI part 2 1030 may include an SD beam selection field 1035, an FD basis selection field 1040, an SCI field 1045, a coefficient selection field 1050, and an NZC quantization field 1055. The SD beam selection field 1035 may indicate L beams out of N1N2O1O2 total beams. The bit width of the SD beam selection field 1035 may be: i 1,1 :log2O1O2, for the beam group; and i 1,2 : For beam indication. The FD basis selection field 1040 may be used to select M from N3 FD bases for each layer. RI FD bases. If N3<19, then Units report 1,6,l, where l = 0, ... RI-1. If N3>19, a two-level window-based selection can be used. i 1,1 ,i 1,2 ,i 1,5 ,i 1,6,l ,i 1,7,l ,i 1,8,l ,i 2,3,l ,i 2,4,l , and i 2,5,l refers to the codebook index. The SCI field 1045 may be used to indicate the location of the strongest coefficient. For RI=1, the bit width of the SCI field 1045 may be For RI>1, the bit width of the SCI field can be The coefficient selection field 1050 may indicate the NZC The bit width of the coefficient selection field 1050 may be given by a 2LM bitmap of RI size, for a total of 2LM×RI bits. The NZC quantization field 1055 may be used to indicate amplitude or phase quantization. 2,3,l , then the NZC quantization field 1055 may include 4 bits to indicate the reference amplitude and the weaker polarization. 2,4,l , then the NZC quantization field 1055 may include The ones digit indicates the magnitude of the difference for each coefficient except the strongest coefficient. 2,5,l , then the NZC quantization field 1055 may include Ones bits indicating the phase of each coefficient except the strongest coefficient.

[0167] Fig.11 An example of a process flow 1100 for supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is illustrated. The process flow 1100 may include a UE 115-b, which may be an example of a UE 115 as described herein. The process flow 1100 may include a network entity 105-a, which may be an example of a network entity 105 as described herein. In the following description of the process flow 1100, operations between the UE 115-b and the network entity 105-a may be sent in a different order than the example order shown, or operations performed by the UE 115-b and the network entity 105-a may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 1100, and other operations may be added to the process flow 1100.

[0168] At 1105, UE 115-b may receive control signaling from network entity 105-a indicating a multi-TRP configuration for UE 115-b to use to communicate with network entity 105-a via a first TRP and a second TRP associated with network entity 105-a.

[0169] At 1110, UE 115-b may receive channel state information reference signals from a first TRP and a second TRP according to a multi-TRP configuration. Network entity 105-a may send CSI-RS via the first TRP and the second TRP.

[0170] At 1115, UE 115-b may send a UCI message including an NZC bitmap to network entity 105-a, the NZC bitmap being based on measurements of a channel state information reference signal. A size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP. The FD basis associated with the first TRP at least partially overlaps the FD basis associated with the second TRP.

[0171] In some examples, sending the UCI includes sending the UCI including one or more fields indicating a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP. The number of FD bases may be based on the first number and the second number.

[0172] In some examples, sending the UCI includes sending the UCI including one or more fields indicating a selection of a first TRP and a second TRP from a set of multiple TRPs. For example, the control signaling received at 1105 may indicate a multi-TRP configuration for use by the UE to communicate with a network entity including a set of multiple TRPs. In some examples, the number of FD bases per TRP is negatively correlated with the number of TRPs selected in the UCI message.

[0173] In some examples, the number of FD bases per TRP is negatively correlated to the number of layers reported in the UCI message.

[0174] In some examples, sending the UCI includes sending the UCI including one or more fields indicating a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP. The number of SD bases may be based on the first number and the second number.

[0175] In some examples, receiving control signaling at 1105 includes receiving an indication of a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP. The number of FD bases may be based on the first number and the second number.

[0176] In some examples, receiving control signaling at 1105 includes receiving an indication of a first number of SD bases associated with a first TRP and a second number of SD bases associated with a second TRP. The number of SD bases may be based on the first number and the second number.

[0177] In some examples, sending the UCI includes sending the UCI including a set of fields indicating a layer-specific FD basis selection on a per-TRP basis.

[0178] In some examples, receiving control signaling at 1105 includes receiving control signaling indicating that the first TRP and the second TRP share the same layer-specific FD basis selection. In some cases, sending UCI also includes sending a first incremental amplitude associated with the first TRP and a second incremental amplitude associated with the second TRP, wherein the first incremental amplitude and the second incremental amplitude exceed the strongest coefficient.

[0179] In some examples, sending the UCI includes sending the UCI including a set of fields indicating a layer common SD base selection on a per-TRP basis.

[0180] In some examples, receiving control signaling at 1105 includes receiving control signaling indicating that the first TRP and the second TRP share the same layer common SD base selection. In some cases, the first number of FD bases associated with the first TRP and the second number of FD bases associated with the second TRP are the same. In some cases, sending UCI includes sending UCI including a field indicating a selection of one of a first TRP or a second TRP from a plurality of TRPs, wherein the control signaling indicates a multi-TRP configuration for use by the UE to communicate with a network entity including a set of a plurality of TRPs, and wherein the selection of one of the first TRP or the second TRP can be a selection of both the first TRP and the second TRP. In some cases, sending UCI also includes sending a single incremental amplitude associated with the first TRP and the second TRP, wherein the single incremental amplitude exceeds the strongest coefficient.

[0181] In some examples, at 1120, network entity 105-a may identify parameters for precoding data sent to UE 115-b based on the CSI report in the UCI, e.g., as described in reference Figure 5As shown. For example, the network entity 105-a may identify a predecoder for precoding data transmission to the UE 115-b based on the SD basis, the FD basis, and the NZC included in the CSI report. The network entity 105-a may then use the predecoder to precode the data for transmission to the UE 115-b. In some examples, at 1125, the network entity 105-a may send data to the UE 115-b. For example, the network entity 105-a may send at least one of the multiple transmissions forming the CJT to the UE 115-b. The phases and amplitudes of the multiple transmissions forming the CJT may be controlled and coordinated by the TRPs participating in the coherent joint transmission. Alternatively, the network entity 105-a may coordinate the CJT of the data to the UE 115-b. The UE 115-b may receive the CJT from multiple TRPs.

[0182] Fig.12 A block diagram 1200 of a device 1205 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the UE 115 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0183] The receiver 1210 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to NZC selection and SCI for CJT CSI), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1205. The receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0184] The transmitter 1215 may provide means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to NZC selection and SCI for CJT CSI), user data, control information, or any combination thereof. In some examples, the transmitter 1215 may be co-located with the receiver 1210 in a transceiver module. The transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0185] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0186] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0187] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0188] In some examples, communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in conjunction with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0189] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The communication manager 1220 may be configured to or otherwise support components for receiving CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration. The communication manager 1220 may be configured to or otherwise support components for sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0190] By including or configuring a communications manager 1220 according to examples as described herein, a device 1205 (e.g., a processor controlling or otherwise coupled to a receiver 1210, a transmitter 1215, the communications manager 1220, or a combination thereof) may support techniques for reducing processing and more efficiently utilizing communications resources.

[0191] Fig.13 A block diagram 1300 of a device 1305 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or UE 115 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0192] The receiver 1310 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to NZC selection and SCI for CJT CSI), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1305. The receiver 1310 may utilize a single antenna or a collection of multiple antennas.

[0193] The transmitter 1315 may provide means for transmitting signals generated by other components of the device 1305. For example, the transmitter 1315 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to NZC selection and SCI for CJT CSI), user data, control information, or any combination thereof. In some examples, the transmitter 1315 may be co-located with the receiver 1310 in a transceiver module. The transmitter 1315 may utilize a single antenna or a collection of multiple antennas.

[0194] The device 1305 or its various components may be examples of components for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1320 may include a multi-TRP manager 1325, a CSI-RS manager 1330, an NZC bitmap manager 1335, or any combination thereof. The communication manager 1320 may be an example of various aspects of the communication manager 1220 as described herein. In some examples, the communication manager 1320 or its various components may be configured to use or otherwise cooperate with the receiver 1310, the transmitter 1315, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0195] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the UE. The multi-TRP manager 1325 may be configured to or otherwise support components for receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The CSI-RS manager 1330 may be configured to or otherwise support components for receiving CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration. The NZC bitmap manager 1335 may be configured to or otherwise support components for sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0196] Fig.14A block diagram 1400 of a communication manager 1420 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1420 may include a multi-TRP manager 1425, a CSI-RS manager 1430, an NZC bitmap manager 1435, an FD base manager 1440, a TRP selection manager 1445, an SD base manager 1455, an FD base selection manager 1460, an SD base selection manager 1465, an incremental amplitude manager 1470, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0197] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at the UE. The multi-TRP manager 1425 may be configured to or otherwise support components for receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The CSI-RS manager 1430 may be configured to or otherwise support components for receiving CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration. The NZC bitmap manager 1435 may be configured to or otherwise support components for sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0198] In some examples, to support sending a UCI message, the FD base manager 1440 may be configured as or otherwise support components for sending a UCI message comprising one or more fields indicating a first number of FD bases associated with a first TRP and a second number of FD bases associated with a second TRP, wherein the number of FD bases is based on the first number and the second number.

[0199] In some examples, to support receiving control signaling, the FD base manager 1440 may be configured as or otherwise support components for receiving indications of a first number of FD bases associated with a first TRP and a second number of FD bases associated with a second TRP, wherein the number of FD bases is based on the first number and the second number.

[0200] In some examples, to support sending a UCI message, the TRP selection manager 1445 may be configured to or otherwise support components for sending a UCI message comprising one or more fields indicating a selection of a first TRP and a second TRP from a set of multiple TRPs, wherein the control signaling indicates a multi-TRP configuration for use by the UE to communicate with a network entity comprising the set of multiple TRPs.

[0201] In some examples, the number of FD bases per TRP is negatively correlated with the number of TRPs selected in the UCI message. In some examples, the number of FD bases per TRP is negatively correlated with the number of layers reported in the UCI message.

[0202] In some examples, to support sending a UCI message, the SD base manager 1455 may be configured to or otherwise support components for sending a UCI message comprising one or more fields indicating a first number of SD bases associated with a first TRP and a second number of SD bases associated with a second TRP, wherein the number of SD bases is based on the first number and the second number.

[0203] In some examples, to support receiving control signaling, the SD base manager 1455 may be configured as or otherwise support components for receiving indications of a first number of SD bases associated with a first TRP and a second number of SD bases associated with a second TRP, wherein the number of SD bases is based on the first number and the second number.

[0204] In some examples, to support sending UCI messages, FD base selection manager 1460 may be configured or otherwise support components for sending a UCI message including a set of fields indicating layer-specific FD base selection on a per-TRP basis.

[0205] In some examples, to support receiving control signaling, the delta amplitude manager 1470 may be configured as or otherwise support components for receiving control signaling indicating that the first TRP and the second TRP share the same layer-specific FD base selection.

[0206] In some examples, to support receiving control signaling, the incremental amplitude manager 1470 may be configured as or otherwise support components for sending a first incremental amplitude associated with a first TRP and a second incremental amplitude associated with a second TRP, where the first incremental amplitude and the second incremental amplitude exceed the strongest coefficient.

[0207] In some examples, to support sending UCI messages, SD base selection manager 1465 may be configured or otherwise support components for sending a UCI message including a field set indicating a layer-common SD base selection on a per-TRP basis.

[0208] In some examples, to support receiving control signaling, the SD base selection manager 1465 may be configured as or otherwise support components for receiving control signaling indicating that the first TRP and the second TRP share the same layer common SD base selection.

[0209] In some examples, a first number of FD groups associated with a first TRP and a second number of FD groups associated with a second TRP are the same.

[0210] In some examples, to support sending a UCI message, the TRP selection manager 1445 may be configured to or otherwise support components for sending a UCI message including a field indicating a selection of a first TRP or one of a second TRP from a set of multiple TRPs, wherein the control signaling indicates a multi-TRP configuration for use by the UE to communicate with a network entity including the set of multiple TRPs, and wherein the selection of one of the first TRP or the second TRP includes selection of both the first TRP and the second TRP.

[0211] In some examples, to support sending a UCI message, the delta magnitude manager 1470 may be configured as or otherwise support components for sending a single delta magnitude associated with a first TRP and a second TRP, where the single delta magnitude exceeds the strongest coefficient.

[0212] Fig.15 A diagram of a system 1500 including a device 1505 that supports NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of a device 1205, a device 1305, or a UE 115 as described herein, or include components thereof. The device 1505 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1520, an input / output (I / O) controller 1510, a transceiver 1515, an antenna 1525, a memory 1530, a code 1535, and a processor 1540. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1545).

[0213] I / O controller 1510 can manage input signals and output signals of device 1505. I / O controller 1510 can also manage peripheral devices that are not integrated into device 1505. In some cases, I / O controller 1510 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1510 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1510 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1510 may be implemented as part of a processor (such as processor 1540). In some cases, a user may interact with device 1505 via I / O controller 1510 or via hardware components controlled by I / O controller 1510.

[0214] In some cases, the device 1505 may include a single antenna 1525. However, in some other cases, the device 1505 may have more than one antenna 1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1515 may communicate bidirectionally via one or more antennas 1525, a wired or wireless link, as described herein. For example, the transceiver 1515 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1515 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1525 for transmission; and demodulating packets received from one or more antennas 1525. The transceiver 1515 or the transceiver 1515 and one or more antennas 1525 may be examples of transmitters 1215, transmitters 1315, receivers 1210, receivers 1310, or any combination thereof or components thereof as described herein.

[0215] Memory 1530 may include random access memory (RAM) and read-only memory (ROM). Memory 1530 may store computer-readable, computer-executable code 1535 including instructions that, when executed by processor 1540, cause device 1505 to perform various functions described herein. Code 1535 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1535 may not be directly executable by processor 1540, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1530 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0216] Processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1540 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to enable device 1505 to perform various functions (e.g., support various functions or tasks of NZC selection and SCI for CJTCSI). For example, device 1505 or a component of device 1505 may include processor 1540 and memory 1530 coupled to or coupled to processor 1540, and processor 1540 and memory 1530 are configured to perform various functions described herein.

[0217] According to the examples disclosed herein, the communication manager 1520 may support wireless communication at the UE. For example, the communication manager 1520 may be configured to or otherwise support components for receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The communication manager 1520 may be configured to or otherwise support components for receiving CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration. The communication manager 1520 may be configured to or otherwise support components for sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0218] By including or configuring a communications manager 1520 according to examples as described herein, the device 1505 can support techniques for improved communications reliability, more efficient utilization of communications resources, improved coordination between devices, and improved utilization of processing power.

[0219] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1515, one or more antennas 1525, or any combination thereof. For example, the communication manager 1520 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1515. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the processor 1540, the memory 1530, the code 1535, or any combination thereof. For example, the code 1535 may include instructions that are executable by the processor 1540 to cause the device 1505 to perform various aspects of NZC selection and SCI for CJT CSI as described herein, or the processor 1540 and the memory 1530 may be otherwise configured to perform or support such operations.

[0220] Fig.16 A block diagram 1600 of a device 1605 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of aspects of the network entity 105 as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communication manager 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0221] Receiver 1610 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1605. In some examples, receiver 1610 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0222] The transmitter 1615 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1605. For example, the transmitter 1615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1615 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1615 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1615 and the receiver 1610 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0223] The communication manager 1620, the receiver 1610, the transmitter 1615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1620, the receiver 1610, the transmitter 1615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0224] In some examples, the communication manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0225] Additionally or alternatively, in some examples, the communication manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0226] In some examples, communication manager 1620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1610, transmitter 1615, or both. For example, communication manager 1620 may receive information from receiver 1610, transmit information to transmitter 1615, or be integrated in conjunction with receiver 1610, transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0227] According to the examples disclosed herein, the communication manager 1620 may support wireless communication at a network entity. For example, the communication manager 1620 may be configured to or otherwise support a component for sending control signaling to a UE indicating a multi-TRP configuration for the UE to use to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The communication manager 1620 may be configured to or otherwise support a component for sending a CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The communication manager 1620 may be configured to or otherwise support a component for obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0228] By including or configuring a communications manager 1620 according to examples as described herein, a device 1605 (e.g., a processor controlling or otherwise coupled to a receiver 1610, a transmitter 1615, a communications manager 1620, or a combination thereof) may support techniques for reducing processing and more efficiently utilizing communications resources.

[0229] Fig.17A block diagram 1700 of a device 1705 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1705 may be an example of aspects of the device 1605 or network entity 105 as described herein. The device 1705 may include a receiver 1710, a transmitter 1715, and a communication manager 1720. The device 1705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0230] Receiver 1710 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1705. In some examples, receiver 1710 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1710 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0231] The transmitter 1715 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1705. For example, the transmitter 1715 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1715 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1715 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1715 and the receiver 1710 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0232] The device 1705 or its various components may be examples of components for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1720 may include a multi-TRP manager 1725, a CSI-RS manager 1730, an NZC bitmap manager 1735, or any combination thereof. The communication manager 1720 may be an example of various aspects of the communication manager 1620 as described herein. In some examples, the communication manager 1720 or its various components may be configured to use or otherwise cooperate with the receiver 1710, the transmitter 1715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1720 may receive information from the receiver 1710, transmit information to the transmitter 1715, or be integrated with the receiver 1710, the transmitter 1715, or both to obtain information, output information, or perform various other operations as described herein.

[0233] According to the examples disclosed herein, the communication manager 1720 may support wireless communication at a network entity. The multi-TRP manager 1725 may be configured to or otherwise support a component for sending control signaling to a UE indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The CSI-RS manager 1730 may be configured to or otherwise support a component for sending a CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The NZC bitmap manager 1735 may be configured to or otherwise support a component for obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0234] Fig.18A block diagram 1800 of a communication manager 1820 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The communication manager 1820 may be an example of aspects of the communication manager 1620, the communication manager 1720, or both as described herein. The communication manager 1820 or its various components may be examples of components for performing various aspects of NZC selection and SCI for CJT CSI as described herein. For example, the communication manager 1820 may include a multi-TRP manager 1825, a CSI-RS manager 1830, an NZC bitmap manager 1835, a TRP selection manager 1840, an SD base manager 1845, an FD base manager 1850, an FD base selection manager 1855, an SD base selection manager 1860, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0235] According to the examples disclosed herein, the communication manager 1820 may support wireless communication at a network entity. The multi-TRP manager 1825 may be configured to or otherwise support a component for sending control signaling to a UE indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The CSI-RS manager 1830 may be configured to or otherwise support a component for sending a CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The NZC bitmap manager 1835 may be configured to or otherwise support a component for obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0236] In some examples, to support receiving a UCI message, the TRP selection manager 1840 may be configured to or otherwise support components for receiving a UCI message comprising one or more fields indicating a selection of a first TRP and a second TRP from a set of multiple TRPs, wherein the control signaling indicates a multi-TRP configuration for use by the UE to communicate with a network entity comprising the set of multiple TRPs.

[0237] In some examples, the number of FD bases per TRP is negatively correlated to the number of layers reported in the UCI message.

[0238] In some examples, to support receiving UCI messages, SD base manager 1845 may be configured as or otherwise support components for receiving UCI messages comprising one or more fields indicating a first number of SD bases associated with a first TRP and a second number of SD bases associated with a second TRP, wherein the number of SD bases is based on the first number and the second number.

[0239] In some examples, to support sending control signaling, the FD base manager 1850 may be configured as or otherwise support components for sending indications of a first number of FD bases associated with a first TRP and a second number of FD bases associated with a second TRP, wherein the number of FD bases is based on the first number and the second number.

[0240] In some examples, to support sending control signaling, the SD base manager 1845 may be configured as or otherwise support components for sending indications of a first number of SD bases associated with a first TRP and a second number of SD bases associated with a second TRP, wherein the number of FD bases is based on the first number and the second number.

[0241] In some examples, to support receiving UCI messages, FD base selection manager 1855 may be configured or otherwise support components for receiving a UCI message including a set of fields indicating layer-specific FD base selection on a per-TRP basis.

[0242] In some examples, to support sending UCI messages, SD base selection manager 1860 may be configured or otherwise support components for sending a UCI message including a field set indicating a layer common SD base selection on a per-TRP basis.

[0243] Fig.19A diagram of a system 1900 including a device 1905 supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The device 1905 may be an example of a device 1605, a device 1705, or a network entity 105 as described herein, or include components thereof. The device 1905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1905 may include components that support output and acquisition of communications, such as a communication manager 1920, a transceiver 1910, an antenna 1915, a memory 1925, a code 1930, and a processor 1935. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1940).

[0244] The transceiver 1910 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1910 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1910 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1905 may include one or more antennas 1915, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1910 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1915, via a wired transmitter); receiving a modulated signal (e.g., from one or more antennas 1915, from a wired receiver); and demodulating a signal. In some implementations, the transceiver 1910 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1915 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1915 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 1910 may include or be configured to be coupled to one or more processors or memory components that are operable to perform the following operations: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1910, or the transceiver 1910 and one or more antennas 1915, or the transceiver 1910 and one or more antennas 1915 and one or more processors or memory components (e.g., processor 1935, or memory 1925, or both) may be included in a chip or chip component installed in the device 1905. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0245] The memory 1925 may include RAM and ROM. The memory 1925 may store computer-readable, computer-executable code 1930 including instructions that, when executed by the processor 1935, cause the device 1905 to perform various functions described herein. The code 1930 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1930 may not be directly executable by the processor 1935, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 1925 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0246] Processor 1935 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1935 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1935. Processor 1935 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1925) to enable device 1905 to perform various functions (e.g., support various functions or tasks of NZC selection and SCI for CJT CSI). For example, device 1905 or a component of device 1905 may include processor 1935 and memory 1925 coupled to processor 1935, and the processor 1935 and memory 1925 are configured to perform various functions described herein. Processor 1935 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing functions of device 1905 (e.g., by executing code 1930). Processor 1935 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1905 (such as in memory 1925). In some specific implementations, processor 1935 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be passed to other systems or, for example, components of device 1905). For example, a processing system of device 1905 may refer to a system including various other components or subcomponents of device 1905, such as processor 1935, or transceiver 1910, or communication manager 1920, or other components or combinations of components of device 1905. The processing system of device 1905 may be docked with other components of device 1905, and may process information (such as input or signal) received from other components, or output information to other components. For example, a chip or modem of device 1905 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1905 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1905 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0247] In some examples, bus 1940 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1940 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1905, or communications performed between different components of device 1905 that may be co-located or may be located in different locations (e.g., where device 1905 may refer to a system in which one or more of communication manager 1920, transceiver 1910, memory 1925, code 1930, and processor 1935 may be located in one of the different components or divided between the different components).

[0248] In some examples, communication manager 1920 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1920 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1920 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1920 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0249] According to the examples disclosed herein, the communication manager 1920 may support wireless communication at a network entity. For example, the communication manager 1920 may be configured to or otherwise support a component for sending control signaling to a UE indicating a multi-TRP configuration for the UE to use to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The communication manager 1920 may be configured to or otherwise support a component for sending a CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The communication manager 1920 may be configured to or otherwise support a component for obtaining a UCI message including an NZC bitmap from the UE and in response to the CSI-RS, wherein the size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0250] By including or configuring a communications manager 1920 according to examples as described herein, the device 1905 can support techniques for improved communications reliability, more efficient utilization of communications resources, improved coordination between devices, and improved utilization of processing power.

[0251] In some examples, the communication manager 1920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1910, one or more antennas 1915 (e.g., where applicable), or any combination thereof. For example, the communication manager 1920 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1910. Although the communication manager 1920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1920 may be supported or performed by the transceiver 1910, the processor 1935, the memory 1925, the code 1930, or any combination thereof. For example, the code 1930 may include instructions that are executable by the processor 1935 to cause the device 1905 to perform various aspects of NZC selection and SCI for CJT CSI as described herein, or the processor 1935 and the memory 1925 may be otherwise configured to perform or support such operations.

[0252] Fig. 20 A flowchart illustrating a method 2000 for supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 15 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0253] At 2005, the method may include receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with a network entity via a first TRP and a second TRP associated with the network entity. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.14 The multi-TRP manager 1425 is used to perform. Additionally or alternatively, the components for performing 2005 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540 and / or a bus 1545.

[0254] At 2010, the method may include receiving CSI-RS from a first TRP and a second TRP according to a multi-TRP configuration. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.14 The CSI-RS manager 1430 is used to perform. Additionally or alternatively, the components for performing 2010 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540 and / or a bus 1545.

[0255] At 2015, the method may include sending a UCI message including an NZC bitmap to a network entity, the NZC bitmap being based on a measurement of a CSI-RS, wherein a size of a number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with a first TRP and a second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.14 The NZC bitmap manager 1435 is used to perform. Additionally or alternatively, the components for performing 2015 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540, and / or a bus 1545.

[0256] Fig.21 A flowchart illustrating a method 2100 for supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 15 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0257] At 2105, the method may include receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.14The multi-TRP manager 1425 is used to perform. Additionally or alternatively, the components for performing 2105 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540 and / or a bus 1545.

[0258] At 2110, the method may include receiving CSI-RS from a first TRP and a second TRP according to a multi-TRP configuration. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference Fig.14 The CSI-RS manager 1430 is used to perform. Additionally or alternatively, the components for performing 2110 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540 and / or a bus 1545.

[0259] At 2115, the method may include sending a UCI message including an NZC bitmap to a network entity, the NZC bitmap being based on a measurement of the CSI-RS, wherein a size of a number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with a first TRP and a second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.14 The NZC bitmap manager 1435 is used to perform. Additionally or alternatively, the components for performing 2115 may, but not necessarily include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540, and / or a bus 1545.

[0260] At 2120, the method may include sending a UCI message including one or more fields indicating a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases is based at least in part on the first number and the second number. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.14 The FD base manager 1440 performs. Additionally or alternatively, the components for performing 2120 may but need not include, for example, an antenna 1525, a transceiver 1515, a communication manager 1520, a memory 1530 (including code 1535), a processor 1540, and / or a bus 1545.

[0261] Fig. 22A flowchart illustrating a method 2200 for supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 as well as Figures 16 to 19 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0262] At 2205, the method may include outputting to the UE control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The operations of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed as described in reference to Fig.18 The multi-TRP manager 1825 is used to perform. Additionally or alternatively, the components for performing 2205 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0263] At 2210, the method may include outputting the CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The operations of 2210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed as described in reference Fig.18 The CSI-RS manager 1830 is used to perform. Additionally or alternatively, the components for performing 2210 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0264] At 2215, the method may include obtaining, from the UE and in response to the CSI-RS, a UCI message including an NZC bitmap, wherein a size of the number of bits of the NZC bitmap is based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP. The operations of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed as described in reference Fig.18The NZC bitmap manager 1835 is used to perform. Additionally or alternatively, the components for performing 2215 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0265] Fig.23 A flowchart illustrating a method 2300 for supporting NZC selection and SCI for CJT CSI according to one or more aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 11 as well as Figures 16 to 19 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0266] At 2305, the method may include outputting to the UE control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Fig.18 The multi-TRP manager 1825 is used to perform. Additionally or alternatively, the components for performing 2305 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0267] At 2310, the method may include outputting the CSI-RS according to a multi-TRP configuration via a first TRP and a second TRP. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed as described in reference Fig.18 The CSI-RS manager 1830 is used to perform. Additionally or alternatively, the components for performing 2310 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0268] At 2315, the method may include obtaining, from the UE and in response to the CSI-RS, a UCI message including an NZC bitmap, wherein a size of the number of bits of the NZC bitmap is based on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Fig.18 The NZC bitmap manager 1835 is used to perform. Additionally or alternatively, the components for performing 2315 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0269] At 2320, the method may include obtaining a UCI message including one or more fields indicating a selection of a first TRP and a second TRP from a set of multiple TRPs, wherein the control signaling indicates a multi-TRP configuration for use by the UE to communicate with a network entity including the set of multiple TRPs. The operations of 2320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2320 may be performed as described in reference to Fig.18 The TRP selection manager 1840 is executed. Additionally or alternatively, the components for executing 2320 may, but not necessarily include, for example, an antenna 1915, a transceiver 1910, a communication manager 1920, a memory 1925 (including code 1930), a processor 1935 and / or a bus 1940.

[0270] The following provides an overview of various aspects of the disclosure:

[0271] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving control signaling indicating a multi-TRP configuration for use by the UE to communicate with a network entity via a first TRP and a second TRP associated with the network entity; receiving a CSI-RS from the first TRP and the second TRP according to the multi-TRP configuration; and sending a UCI message including an NZC bitmap to the network entity, the NZC bitmap being based at least in part on a measurement of the CSI-RS, wherein a size of the number of bits of the NZC bitmap is based at least in part on a number of FD bases and a number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0272] Aspect 2: A method according to Aspect 1, wherein sending the UCI message includes: sending the UCI message including one or more fields, the one or more fields indicating a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases is at least partially based on the first number and the second number.

[0273] Aspect 3: A method according to any one of Aspects 1 to 2, wherein sending the UCI message comprises: sending the UCI message including one or more fields, the one or more fields indicating the selection of the first TRP and the second TRP from multiple TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the multiple TRPs.

[0274] Aspect 4: The method according to Aspect 3, wherein the number of FD bases per TRP is negatively correlated with the number of TRPs selected in the UCI message.

[0275] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the number of FD bases per TRP is negatively correlated with the number of layers reported in the UCI message.

[0276] Aspect 6: A method according to any one of Aspects 1 to 5, wherein sending the UCI message comprises: sending the UCI message including one or more fields, the one or more fields indicating a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases is at least partially based on the first number and the second number.

[0277] Aspect 7: A method according to any one of Aspects 1 to 6, wherein receiving the control signaling includes: receiving an indication of a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases is at least partially based on the first number and the second number.

[0278] Aspect 8: A method according to any one of Aspects 1 to 7, wherein receiving the control signaling includes: receiving an indication of a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases is at least partially based on the first number and the second number.

[0279] Aspect 9: The method according to any one of aspects 1 to 8, wherein sending the UCI message comprises: sending the UCI message including a field set, the field set indicating a layer-specific FD basis selection on a per-TRP basis.

[0280] Aspect 10: The method according to Aspect 9, wherein receiving the control signaling includes: receiving the control signaling indicating that the first TRP and the second TRP share the same layer-specific FD base selection.

[0281] Aspect 11: The method according to Aspect 10, wherein sending the UCI message further comprises: sending a first incremental amplitude associated with the first TRP and a second incremental amplitude associated with the second TRP, wherein the first incremental amplitude and the second incremental amplitude exceed the strongest coefficient.

[0282] Aspect 12: The method according to any one of Aspects 1 to 11, wherein sending the UCI message comprises: sending the UCI message including a field set, the field set indicating a layer common SD base selection on a per-TRP basis.

[0283] Aspect 13: The method according to Aspect 12, wherein receiving the control signaling includes: receiving the control signaling indicating that the first TRP and the second TRP share the same layer common SD base selection.

[0284] Aspect 14: A method according to Aspect 13, wherein a first number of FD groups associated with the first TRP and a second number of FD groups associated with the second TRP are the same.

[0285] Aspect 15: A method according to any one of Aspects 13 to 14, wherein sending the UCI message further comprises: sending the UCI message including a field, the field indicating a selection of one of the first TRP or the second TRP from a plurality of TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the plurality of TRPs, and wherein the selection of one of the first TRP or the second TRP includes a selection of both the first TRP and the second TRP.

[0286] Aspect 16: The method according to any one of Aspects 13 to 15, wherein sending the UCI message further comprises: sending a single incremental amplitude associated with the first TRP and the second TRP, wherein the single incremental amplitude exceeds the strongest coefficient.

[0287] Aspect 17: A method for performing wireless communications at a network entity, the method comprising: outputting to a UE control signaling indicating a multi-TRP configuration for use by the UE to communicate with the network entity via a first TRP and a second TRP associated with the network entity; outputting a CSI-RS according to the multi-TRP configuration via the first TRP and the second TRP; and obtaining from the UE and in response to the CSI-RS a UCI message including an NZC bitmap, wherein a size of the number of bits of the NZC bitmap is at least partially based on the number of FD bases and the number of SD bases associated with the first TRP and the second TRP, wherein the FD base associated with the first TRP at least partially overlaps the FD base associated with the second TRP.

[0288] Aspect 18: A method according to Aspect 17, wherein obtaining the UCI message comprises: obtaining the UCI message including one or more fields, the one or more fields indicating the selection of the first TRP and the second TRP from a plurality of TRPs, wherein the control signaling indicates the multi-TRP configuration for use by the UE to communicate with the network entity including the plurality of TRPs.

[0289] Aspect 19: The method according to any one of Aspects 17 to 18, wherein the number of FD bases per TRP is negatively correlated with the number of layers reported in the UCI message.

[0290] Aspect 20: A method according to any one of Aspects 17 to 19, wherein obtaining the UCI message includes: obtaining the UCI message including one or more fields, the one or more fields indicating a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of SD bases is at least partially based on the first number and the second number.

[0291] Aspect 21: A method according to any one of Aspects 17 to 20, wherein outputting the control signaling includes: outputting an indication of a first number of FD bases associated with the first TRP and a second number of FD bases associated with the second TRP, wherein the number of FD bases is at least partially based on the first number and the second number.

[0292] Aspect 22: A method according to any one of Aspects 17 to 21, wherein outputting the control signaling includes: outputting an indication of a first number of SD bases associated with the first TRP and a second number of SD bases associated with the second TRP, wherein the number of FD bases is at least partially based on the first number and the second number.

[0293] Aspect 23: The method according to any one of Aspects 17 to 22, wherein obtaining the UCI message comprises: obtaining the UCI message including a field set, the field set indicating a layer-specific FD basis selection on a per-TRP basis.

[0294] Aspect 24: The method according to any one of Aspects 17 to 23, wherein outputting the UCI message comprises: outputting the UCI message including a field set, the field set indicating a layer common SD base selection on a per-TRP basis.

[0295] Aspect 25: An apparatus comprising: a memory; a transceiver; and at least one processor, the at least one processor being coupled to the memory and the transceiver, the at least one processor being configured to execute a method according to any one of Aspects 1 to 16.

[0296] Aspect 26: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 16.

[0297] Aspect 27: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0298] Aspect 28: An apparatus, comprising: a memory and at least one processor, the at least one processor being coupled to the memory, the at least one processor being configured to execute the method according to any one of aspects 17 to 24.

[0299] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 17 to 24.

[0300] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 17 to 24.

[0301] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0302] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0303] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0304] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0305] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0306] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0307] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or CAB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0308] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0309] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0310] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0311] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling indicating a multiple transmission and reception point configuration for use by the UE to communicate with the network entity via a first transmission and reception point and a second transmission and reception point associated with the network entity; receiving a channel state information reference signal from the first transmission and reception point and the second transmission and reception point according to the multiple transmission and reception point configuration; as well as An uplink control information message is sent to the network entity, wherein the non-zero coefficient bitmap is based at least in part on the measurement of the channel state information reference signal, wherein the size of the number of bits of the non-zero coefficient bitmap is based at least in part on the number of frequency domain bases and the number of spatial domain bases associated with the first transmission reception point and the second transmission reception point, wherein the frequency domain base associated with the first transmission reception point at least partially overlaps the frequency domain base associated with the second transmission reception point.

2. The method of claim 1 , wherein sending the uplink control information message comprises: Send the uplink control information message comprising one or more fields, wherein the one or more fields indicate a first number of frequency domain bases associated with the first transmitting / receiving point and a second number of frequency domain bases associated with the second transmitting / receiving point, wherein the number of frequency domain bases is at least partially based on the first number and the second number.

3. The method of claim 1 , wherein sending the uplink control information message comprises: Sending the uplink control information message including one or more fields indicating selection of the first transmission reception point and the second transmission reception point from a plurality of transmission reception points, wherein the control signaling indicates the multiple transmission reception point configuration for use by the UE to communicate with the network entity including the plurality of transmission reception points.

4. The method according to claim 3, wherein the number of frequency domain bases per transmission and reception point is negatively correlated with the number of transmission and reception points selected in the uplink control information message.

5. The method of claim 1, wherein the number of frequency domain bases per transmission reception point is negatively correlated with the number of layers reported in the uplink control information message.

6. The method of claim 1, wherein sending the uplink control information message comprises: Send the uplink control information message including one or more fields, wherein the one or more fields indicate a first number of spatial domain bases associated with the first transmitting and receiving point and a second number of spatial domain bases associated with the second transmitting and receiving point, wherein the number of spatial domain bases is at least partially based on the first number and the second number.

7. The method of claim 1 , wherein receiving the control signaling comprises: An indication of a first number of frequency domain bases associated with the first transmit-receive point and a second number of frequency domain bases associated with the second transmit-receive point is received, wherein the number of frequency domain bases is based at least in part on the first number and the second number.

8. The method of claim 1, wherein receiving the control signaling comprises: An indication of a first number of spatial domain bases associated with the first transmit-receive point and a second number of spatial domain bases associated with the second transmit-receive point is received, wherein the number of spatial domain bases is based at least in part on the first number and the second number.

9. The method of claim 1 , wherein sending the uplink control information message comprises: The uplink control information message is transmitted including a set of fields indicating a layer-specific frequency domain basis selection on a per transmission reception point basis.

10. The method of claim 9, wherein receiving the control signaling comprises: Receive the control signaling indicating that the first transmission reception point and the second transmission reception point share the same layer-specific frequency domain basis selection.

11. The method of claim 10, wherein sending the uplink control information message further comprises: A first incremental amplitude associated with the first transmit-receive point and a second incremental amplitude associated with the second transmit-receive point are transmitted, wherein the first incremental amplitude and the second incremental amplitude exceed a strongest coefficient.

12. The method of claim 1 , wherein sending the uplink control information message comprises: The uplink control information message is transmitted including a set of fields indicating a layer common spatial domain basis selection on a per transmission reception point basis.

13. The method of claim 12, wherein receiving the control signaling comprises: The control signaling indicating that the first transmission reception point and the second transmission reception point share the same layer common spatial domain basis selection is received.

14. The method of claim 13, wherein a first number of frequency domain bases associated with the first transmission / reception point and a second number of frequency domain bases associated with the second transmission / reception point are the same.

15. The method of claim 13, wherein sending the uplink control information message further comprises: Sending the uplink control information message including a field, the field indicating a selection of one of the first transmission reception point or the second transmission reception point from a plurality of transmission reception points, wherein the control signaling indicates the multiple transmission reception point configuration for use by the UE to communicate with the network entity including the plurality of transmission reception points, and wherein the selection of one of the first transmission reception point or the second transmission reception point includes a selection of both the first transmission reception point and the second transmission reception point.

16. The method of claim 13, wherein sending the uplink control information message further comprises: A single incremental magnitude associated with the first transmit-receive point and the second transmit-receive point is transmitted, wherein the single incremental magnitude exceeds the strongest coefficient.

17. A method for wireless communication at a network entity, the method comprising: outputting to a user equipment (UE) control signaling indicating a multiple transmission reception point configuration for use by the UE to communicate with the network entity via a first transmission reception point and a second transmission reception point associated with the network entity; Outputting a channel state information reference signal according to the multiple transmission and reception point configuration via the first transmission and reception point and the second transmission and reception point; as well as An uplink control information message including a non-zero coefficient bitmap is obtained from the UE and in response to the channel state information reference signal, wherein a size of the number of bits of the non-zero coefficient bitmap is based at least in part on the number of frequency domain bases and the number of spatial domain bases associated with the first transmission reception point and the second transmission reception point, wherein the frequency domain base associated with the first transmission reception point at least partially overlaps the frequency domain base associated with the second transmission reception point.

18. The method of claim 17, wherein obtaining the uplink control information message comprises: Obtain the uplink control information message comprising one or more fields indicating selection of the first transmission reception point and the second transmission reception point from a plurality of transmission reception points, wherein the control signaling indicates the multiple transmission reception point configuration for use by the UE to communicate with the network entity comprising the plurality of transmission reception points.

19. The method of claim 17, wherein the number of frequency domain bases per transmission reception point is inversely correlated with the number of layers reported in the uplink control information message.

20. The method of claim 17, wherein obtaining the uplink control information message comprises: Obtain the uplink control information message comprising one or more fields, wherein the one or more fields indicate a first number of spatial domain bases associated with the first transmitting / receiving point and a second number of spatial domain bases associated with the second transmitting / receiving point, wherein the number of spatial domain bases is at least partially based on the first number and the second number.

21. The method of claim 17, wherein outputting the control signaling comprises: An indication of a first number of frequency domain bases associated with the first transmit-receive point and a second number of frequency domain bases associated with the second transmit-receive point is output, wherein the number of frequency domain bases is based at least in part on the first number and the second number.

22. The method of claim 17, wherein outputting the control signaling comprises: An indication of a first number of spatial domain bases associated with the first transmit-receive point and a second number of spatial domain bases associated with the second transmit-receive point is output, wherein the number of frequency domain bases is based at least in part on the first number and the second number.

23. The method of claim 17, wherein obtaining the uplink control information message comprises: The uplink control information message comprising a set of fields is obtained, the set of fields indicating a layer-specific frequency domain basis selection on a per-transmission-reception-point basis.

24. The method of claim 17, wherein outputting the uplink control information message comprises: The uplink control information message including a set of fields is output, the set of fields indicating a layer common spatial domain basis selection on a per transmission reception point basis.

25. An apparatus for wireless communication, the apparatus comprising: Memory; Transceiver; and At least one processor of a user equipment (UE), the at least one processor coupled to the memory and the transceiver, and the at least one processor configured to: receiving, via the transceiver, control signaling indicating a multiple transmission and reception point configuration for use by the UE to communicate with a network entity via a first transmission and reception point and a second transmission and reception point associated with the network entity; Receiving, via the transceiver, a channel state information reference signal from the first transmission and reception point and the second transmission and reception point according to the multiple transmission and reception point configuration; as well as An uplink control information message is sent to the network entity and via the transceiver, wherein the non-zero coefficient bitmap is based at least in part on a measurement of the channel state information reference signal, wherein a size of the number of bits of the non-zero coefficient bitmap is based at least in part on a number of frequency domain bases and a number of spatial domain bases associated with the first transmission reception point and the second transmission reception point, wherein the frequency domain base associated with the first transmission reception point at least partially overlaps the frequency domain base associated with the second transmission reception point.

26. The apparatus of claim 25, wherein the at least one processor is further configured to: The uplink control information message including one or more fields is sent via the transceiver, and the one or more fields indicate a first number of frequency domain bases associated with the first transmitting and receiving point and a second number of frequency domain bases associated with the second transmitting and receiving point, wherein the number of frequency domain bases is at least partially based on the first number and the second number.

27. The apparatus of claim 25, wherein to send the uplink control information message, the at least one processor is further configured to: The uplink control information message including one or more fields is sent via the transceiver, and the one or more fields indicate the selection of the first transmission reception point and the second transmission reception point from a plurality of transmission reception points, wherein the control signaling indicates the multiple transmission reception point configuration for use by the UE to communicate with the network entity including the plurality of transmission reception points.

28. The apparatus of claim 27, wherein the number of frequency domain bases per transmission-reception point is negatively correlated with the number of transmission-reception points selected in the uplink control information message.

29. The apparatus of claim 25, wherein the number of frequency domain bases per transmission reception point is inversely correlated with the number of layers reported in the uplink control information message.

30. An apparatus for wireless communication, the apparatus comprising: Memory; and at least one processor of a network entity, the at least one processor being coupled to the memory, and the at least one processor being configured to: outputting to a user equipment (UE) control signaling indicating a multiple transmission reception point configuration for use by the UE to communicate with the network entity via a first transmission reception point and a second transmission reception point associated with the network entity; Outputting a channel state information reference signal according to the multiple transmission and reception point configuration via the first transmission and reception point and the second transmission and reception point; as well as An uplink control information message including a non-zero coefficient bitmap is obtained from the UE and in response to the channel state information reference signal, wherein a size of the number of bits of the non-zero coefficient bitmap is based at least in part on the number of frequency domain bases and the number of spatial domain bases associated with the first transmission reception point and the second transmission reception point, wherein the frequency domain base associated with the first transmission reception point at least partially overlaps the frequency domain base associated with the second transmission reception point.

Images