Delay compensation for multiple transmit-receive points

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a first channel state information reference signal (CSI-RS) from a first transmit receive point (TRP) and a second CSI-RS from a second TRP. The UE may transmit a timing offset value and a precoding matrix indicator based at least in part on the first CSI-RS and the second CSI-RS measurements. The UE may receive a tracking reference signal (TRS) from the first TRP and the second TRP. The UE may generate a delay profile for channel estimation based at least in part on the TRS for physical downlink shared channel (PDSCH) demodulation. The UE may receive a PDSCH communication jointly transmitted from the first TRP and the second TRP based at least in part on the delay profile. Numerous other aspects are described.

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless communication, and to techniques and apparatuses for compensating for delay for multiple transmission reception points. BACKGROUND

[0002] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0003] A wireless network can include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE can communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to communications from network nodes to UEs, and “uplink” (or “UL”) refers to communications from UEs to network nodes. Some wireless networks can support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among others).

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR), which can be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method can include receiving a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP. The method can include transmitting a timing offset value and a precoding matrix indicator (PMI) measured based at least in part on the first CSI-RS and the second CSI-RS. The method can include receiving a tracking reference signal (TRS) from the first TRP and the second TRP. The method can include generating a delay profile for channel estimation based at least in part on the TRS for physical downlink shared channel (PDSCH) demodulation. The method can include receiving a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method can include transmitting a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The method can include receiving a timing offset value and a PMI. The method can include transmitting a TRS from the first TRP and the second TRP. The method can include transmitting a PDSCH communication jointly from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0007] Some aspects described herein relate to a UE for wireless communication. The UE can include a memory and one or more processors coupled to the memory. The one or more processors can be configured to receive a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The one or more processors can be configured to transmit a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS. The one or more processors can be configured to receive a TRS from the first TRP and the second TRP. The one or more processors can be configured to generate a delay profile for channel estimation based at least in part on the TRS for PDSCH demodulation. The one or more processors can be configured to receive a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity can include a memory and one or more processors coupled to the memory. The one or more processors can be configured to transmit a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The one or more processors can be configured to receive a timing offset value and a PMI. The one or more processors can be configured to transmit a TRS from the first TRP and the second TRP. The one or more processors can be configured to jointly transmit a PDSCH communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to transmit a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to receive a TRS from the first TRP and the second TRP. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to generate a delay profile for channel estimation based at least in part on the TRS for PDSCH demodulation. The set of instructions, when executed by the one or more processors of the UE, can cause the UE to receive a PDSCH communication jointly transmitted from the first TRP and the second TRP based at least in part on the delay profile.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to transmit a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The set of instructions, when executed by the one or more processors of the network entity, can cause the network entity to receive a timing offset value and a PMI. The set of instructions, when executed by the one or more processors of the network entity, can cause the network entity to transmit a TRS from the first TRP and the second TRP. The set of instructions, when executed by the one or more processors of the network entity, can cause the network entity to jointly transmit a PDSCH communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The apparatus can include means for transmitting a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS. The apparatus can include means for receiving a TRS from the first TRP and the second TRP. The apparatus can include means for generating a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS. The apparatus can include means for receiving a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for transmitting a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The apparatus can include means for receiving a timing offset value and a PMI. The apparatus can include means for transmitting a TRS from the first TRP and the second TRP. The apparatus can include means for transmitting a PDSCH communication jointly from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0013] Aspects generally include a method, apparatus, system, computer program product, UE, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

[0014] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions are not to depart from the scope of the appended claims. The present disclosure is to be accorded the widest scope encompassed by the appended claims. The properties of the concepts disclosed herein will be better understood in conjunction with the accompanying drawings and the following description of specific examples. Each of the figures is provided for the purpose of illustration and description, and is not intended as a limitation on the scope of the claims.

[0015] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. Techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS

[0016] To more fully understand the above-described features of the present disclosure, a further description can be had by reference to the various aspects, some of which are illustrated in the appended drawings. It is noted, however, that the appended drawings are not intended to be exhaustive or limiting of the present disclosure and are not intended to limit the scope of the description to the one aspect depicted. The same reference numerals in different drawings can identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a disaggregated base station architecture, in accordance with the present disclosure.

[0020] Figure 4 illustrates an example logical architecture of a distributed random access network, in accordance with the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of multi-transmission reception point (TRP) communications, in accordance with the present disclosure.

[0022] Figure 6is a diagram illustrating an example of multi-TRP operation according to the present disclosure.

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

[0024] Figure 8 is a diagram illustrating an example of a beam management procedure according to the present disclosure.

[0025] Figure 9 is a diagram illustrating an example of using beams for communication between a network entity and a UE according to the present disclosure.

[0026] Figure 10 is a diagram illustrating an example of a delay profile according to the present disclosure.

[0027] Figure 11 is a diagram illustrating an example of a transmission configuration indicator state according to the present disclosure.

[0028] Figure 12 is a diagram illustrating an example of physical downlink shared channel transmission with per-TRP tracking reference signal according to the present disclosure.

[0029] Figure 13 is a diagram illustrating an example associated with delay pre-compensation according to the present disclosure.

[0030] Figure 14 is a diagram illustrating an example of reception timing in a single frequency network (SFN) according to the present disclosure.

[0031] Figure 15 is a diagram illustrating an example of pre-compensation in a SFN according to the present disclosure.

[0032] Figure 16 is a diagram illustrating an example of updating delay compensation according to the present disclosure.

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

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

[0035] Figure 19 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0036] Figure 20 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION

[0037] A user equipment (UE) can measure reference signals and report channel state information (CSI) feedback that provides information of a channel. The UE can report a timing offset value that represents a difference in propagation timing of reference signals from multiple transmission reception points (TRPs). The UE can report the timing offset value with the CSI feedback. A network entity can use the timing offset value for subband precoding determination. However, tracking reference signals (TRSs) and physical downlink shared channel (PDSCH) communications from the TRPs can not be time-aligned and not compensated for by the timing misalignment. Thus, any noise filtering performed by the UE prior to channel estimation can not be as effective. With less effective filtering, channel estimation can not be as accurate and thus communications can be degraded. Degraded communications can waste power and signaling resources if the communications are lost or retransmitted.

[0038] According to various aspects described herein, a network entity can use the timing offset value for both subband precoding determination and PDSCH delay pre-compensation. PDSCH delay pre-compensation can include adjusting a transmission time of a PDSCH communication from a TRP to align a time of arrival of the PDSCH communication at the UE. This can result in a delay profile in which reception from the TRPs are aligned in time. The UE can be expected to be aware of the network entity’s behavior of transmitting PDSCHs with delay pre-compensation in order to make proper channel estimation and demodulation. The UE can use this information to filter received communications to reduce noise in channel estimation.

[0039] By using the timing offset value for PDSCH delay pre-compensation, the time of arrival of PDSCH communications from multiple TRPs can be more time-aligned. Filtering in channel estimation can be more effective for reception from all TRPs and communications can be improved. Improving communications saves power and signaling resources that would otherwise be wasted due to unsuccessful communications.

[0040] In some aspects, the UE can further generate a delay profile based at least in part on an average delay of the anchor TRS. Since the average delay is for only one TRP, the UE can save processing resources.

[0041] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using, in addition to or in place of the aspects set forth herein, other structures, functionalities, or structures and functions disclosed with respect to the various aspects of the present disclosure. It will be understood that any aspect of the disclosure disclosed herein can be implemented by one or more elements of a claim.

[0042] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0043] While aspects can be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

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

[0045] In some examples, the network nodes 110 are or include network nodes that communicate with UEs 120 via radio access links, such as RUs. In some examples, the network nodes 110 are or include network nodes that communicate with other network nodes 110 via a front-haul link or a mid-haul link, such as DUs. In some examples, the network nodes 110 are or include network nodes that communicate with other network nodes 110 via a mid-haul link or with a core network via a backhaul link, such as CUs. In some examples, the network nodes 110 (such as aggregated network nodes 110 or disaggregated network nodes 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 can include, for example, an NR base station, an LTE base station, a NodeB, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 can interconnect with each other and / or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network, such as a direct physical connection, an air interface, or a virtual network.

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

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

[0048] Wireless network 100 can include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station can be a UE 120 that can relay transmissions for other UEs 120. In Figure 1 In the example shown in FIG. 1, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d in order to facilitate communication between network node 110a and UE 120d. A network node 110 that relays

[0049] Wireless network 100 can be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 can have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro network nodes can have a high transmit power level (e.g., 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes can have a lower transmit power level (e.g., 0.1 to 2 watts).

[0050] A network controller 130 can couple to or communicate with a set of network nodes 110 and can provide coordination and control for the network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a metro communication link. The network nodes 110 can also communicate with one another directly via wireless backhaul communication links or indirect via wired backhaul communication links. In some aspects, the network controller 130 can be a CU or a core network device, or can include a CU or a core network device.

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

[0052] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and / or eMTC UEs can include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a network node, another device (e.g., remote device), or some other entity. A

[0053] Generally, any number of wireless networks 100 can be deployed in a given geographic area. Each wireless network 100 can support a particular RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, an air interface, and / or the like. Frequencies can be referred to as carriers, frequency channels, and / or the like. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0054] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., not using network node 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110. Communication between UEs 120 can be through a direct

[0055] Devices of wireless network 100 can use electromagnetic spectrum for communication. The electromagnetic spectrum can be subdivided based on frequency or wavelength into various classes, bands, channels, and / or the like. For example, devices of wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, despite the frequencies being less than 30 GHz, which is the lower limit of the Extremely High Frequency (EHF) band designated by the International Telecommunications Union (ITU). Wireless communication can be performed using different carrier bandwidths within a band. For example, a carrier can be associated with a particular bandwidth part (BWP) within the band. The BWP can include a set of resource blocks (RBs) that can be used for communication between devices of wireless network 100.

[0056] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as Frequency Range designations FR3 (7.125 GHz - 24.25 GHz). Bands that fall within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Moreover, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range designations FR4-a or FR4-l (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands fall within the EHF band.

[0057] With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-l, and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-l, and / or FR5) can be modified, and that the techniques described herein are applicable with those modified frequency ranges.

[0058] In some aspects, a UE (e.g., UE 120) can include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 can receive, from a first TRP, a first channel state information reference signal (CSI-RS) and receive, from a second TRP, a second CSI-RS. The communications manager 140 can transmit a timing offset value and a precoding matrix indicator (PMI) measured based at least in part on the first CSI-RS and the second CSI-RS. The communications manager 140 can receive, from the first TRP and the second TRP, a tracking reference signal (TRS). The communications manager 140 can generate, based at least in part on the TRS, a delay profile for channel estimation for PDSCH demodulation. The communications manager 140 can receive, based at least in part on the delay profile, a PDSCH communication transmitted jointly from the first TRP and the second TRP. Additionally, or alternatively, the communications manager 140 can perform one or more other operations described herein.

[0059] In some aspects, a network entity (e.g., a network node 110) can include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 can transmit a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The communication manager 150 can receive a timing offset value and a PMI. The communication manager 150 can transmit a TRS from the first TRP and the second TRP. The communication manager 150 can jointly transmit a PDSCH communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI. Additionally, or alternatively, the communication manager 150 can perform one or more other operations described herein.

[0060] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to Figure 1 the examples described with respect to

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

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

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

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

[0065] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements (within a single housing or multiple housings), a set of co-planar antenna elements, a set of non-co-planar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as, for example, one or more components in the transceiver 288 and / or the transceiver 254) in a device. Figure 2 ​

[0066] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modems 254 of UE 120 can include modulators and demodulators. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, with reference to Figures 4-20 ) and can operate in a similar manner.

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

[0068] The controller / processor of the network entity (e.g., controller / processor 240 of network node 110), the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more techniques associated with compensation for delays across multiple TRPs, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 17 Process 1700 Figure 18 The operation of process 1800 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation and / or interpretation). Figure 17 Process 1700 Figure 18 The operation of process 1800 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0069] In some aspects, the UE (e.g., UE 120) includes: components for receiving a first CSI-RS from a first TRP and a second CSI-RS from a second TRP; components for transmitting a timing offset value and a PMI measured at least in part based on the first CSI-RS and the second CSI-RS; components for receiving a TRS from the first TRP and the second TRP; components for generating a delay distribution for channel estimation based at least in part on the TRS for PDSCH demodulation; and / or components for receiving PDSCH communications jointly transmitted from the first TRP and the second TRP based at least in part on the delay distribution. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0070] In some aspects, a network entity (e.g., a network node 110) includes means for transmitting a first CSI-RS from a first TRP and a second CSI-RS from a second TRP, means for receiving a timing offset value and a PMI, means for transmitting a TRS from the first TRP and the second TRP, and / or means for jointly transmitting a PDSCH communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI. In some aspects, means for a network entity to perform operations described herein can include, for example, one or more of the communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0071] Although Figure 2 The blocks in FIG. 13 are illustrated as distinct components only for the sake of clarity, and numerous implementations of the functionality described with respect to these blocks can be carried out in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be carried out by or under the control of the controller / processor 280.

[0072] As indicated above, Figure 2 are provided as examples. Other examples can differ from what is described with respect to the examples Figure 2 described with respect to the examples

[0073] Deployments of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, base station, or network equipment can be implemented in an aggregated architecture or a disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station. A “network entity” or “network node” can refer to a disaggregated base station or one or more units of a disaggregated base station, such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof.

[0074] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node (e.g., within a single device or unit). Disaggregated base stations (e.g., disaggregated network nodes) can be configured to utilize protocol stacks that are physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0075] Base station type operations or network designs can take into account the aggregated nature of base station functionality. For example, disaggregated base stations can be utilized in IAB networks, open radio access networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or virtualized radio access networks (vRAN, also referred to as cloud radio access networks (C-RAN)) to facilitate scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. Disaggregated base stations can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0076] Figure 3 FIG. 1 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 can include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 can communicate with one or more DUs 330 via respective fronthaul links, such as over F1 interfaces. Each of the DUs 330 can communicate with one or more RUs 340 via respective front-haul links. Each of the RUs 340 can communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, the UEs 120 can be simultaneously served by multiple RUs 340.

[0077] Each of the units (including CU 310, DU 330, RU 340) and near-RT RIC 325, non-RT RIC 315, and SMO framework 305 can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission media. In some examples, each of the units can include a wired interface configured to receive or transmit signals to one or more of the other units through a wired transmission medium and a wireless interface that can include a receiver, a transmitter, or a transceiver (such as a RF transceiver) configured to receive or transmit signals to one or more of the other units through a wireless transmission medium, or both.

[0078] In some aspects, CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, CU 310 can 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 units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. CU 310 can be implemented to communicate with DU 330 for network control and signaling as needed.

[0079] Each DU 330 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers in accordance with a functional split, such as a functional split defined by 3 GPP. In some aspects, the one or more high PHY layers can be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 can also host one or more low PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which can also be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0080] Each RU 340 can implement lower layer functionality. In some deployments, the RUs 340 controlled by the DUs 330 can correspond to logical nodes that host RF processing functions or low PHY layer functions based on a functional split (e.g., a functional split defined by 3 GPP), such as a lower layer functional split, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 340 can be controlled by the corresponding DUs 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

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

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

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

[0084] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described Figure 3 with respect to the examples described in this regard.

[0085] Figure 4 An example logical architecture of a distributed RAN 400 in accordance with the present disclosure is illustrated.

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

[0087] The access node controller 410 can include and / or can be in communication with one or more TRPs 435 (e.g., via an Fl control (Fl-C) interface and / or an Fl user (Fl-U) interface). The TRPs 435 can include a distributed unit (DU) and / or a radio unit (RU) of the distributed RAN 400. In some aspects, the TRPs 435 can correspond to the above-described access node 105. Figure 1The described network nodes 110. For example, different TRPs 435 can be included in different network nodes 110. Additionally or alternatively, multiple TRPs 435 can be included in a single network node 110. In some aspects, a network node 110 can include a CU (e.g., an access node controller 410) and / or one or more DUs (e.g., one or more TRPs 435). In some cases, a TRP 435 can be referred to as a cell, a panel, an antenna array, or an array.

[0088] A TRP 435 can be connected to a single access node controller 410 or multiple access node controllers 410. In some aspects, there can be a dynamic configuration of split logical functions within the architecture of distributed RAN 400, referred to elsewhere herein as functional split. For example, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and / or the medium access control (MAC) layer can be configured to terminate at the access node controller 410 or at the TRP 435.

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

[0090] As indicated above, Figure 4 are provided as examples. Other examples can differ from what is described with respect to Figure 4 the described examples.

[0091] Figure 5 is a diagram illustrating an example 500 of multi-TRP communications (sometimes referred to as multi-panel communications) in accordance with the present disclosure. As shown, Figure 5 a plurality of TRPs 505 can be in communication with a same UE 120. The TRPs 505 can correspond to the TRPs 435 described above in connection with Figure 4 .

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

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

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

[0095] As indicated above, Figure 5 are provided as examples. Other examples can differ from what is described Figure 5 with respect to the examples described with respect to

[0096] Figure 6 is a diagram illustrating an example 600 of multi-TRP operation according to the present disclosure.

[0097] Example 600 shows that single DCI (sDCI) for multi-TRP PDSCH can include spatial division multiplexing (SDM), frequency division multiplexing (FDM), or time division multiplexing (TDM). Example 600 shows that, in the case of multi-TRP, a TRP can use TDM circular mapping or TDM sequential mapping. Example 600 also shows that multiple DCI (mDCI) for multi-TRP PDSCH can include DMRS for SDM.

[0098] Example 600 shows that TDM can be used for physical uplink control channel (PUCCH) repetition. Example 600 also shows that single frequency network (SFN) can use SDM for physical uplink shared channel (PUSCH) and / or PUCCH.

[0099] As indicated above, Figure 6 are provided as examples. Other examples can differ from what is described Figure 6 with respect to the examples described with respect to

[0100] Figure 7 This is an illustration of example 700 of a CJT and a non-CJT (NCJT) for multiple TRPs according to this disclosure.

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

[0102] For SDM-based NCJT, data is pre-decoded separately on different TRPs. For example, pre-decoder A is pre-decoded for one TRP, and pre-decoder B is pre-decoded for a separate TRP. This can be represented as: The non-bold letters are used for the data of pre-decoder A and the first TRP, and the bold letters are used for the data of pre-decoder B and the second TRP. For example, the pre-decoder ( ) , This can indicate the pre-decoder used for a specific TRP and rank (indicated by the rank indicator (RI)). Data ( ) , Data can be indicated via TRP and RI.

[0103] For CJT, data is pre-decoded jointly on different TRPs. For example, this can be represented as: Pre-decoder ( ) , and data ( ) Reference numeral 702 illustrates joint pre-decoding for multiple TRPs, rather than individual pre-decoding as shown for NCJT. Reference numeral 704 illustrates two layers being jointly pre-decoded.

[0104] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0105] Figure 8 These are illustrations of examples 800, 810, and 820 illustrating beam management processes according to this disclosure. Figure 8 As shown, Examples 800, 810, and 820 include a UE 120 that communicates with network entities (e.g., network node 110) in a wireless network (e.g., wireless network 100). However, Figure 8The illustrated devices are provided as examples, and the wireless network can support communication and beam management between other devices (e.g., between a UE 120 and a network node 110 or TRP, between a mobile terminal node and a control node, between an IAB child node and an IAB parent node, and / or between a scheduled node and a scheduling node). In some aspects, the UE 120 and the network node 110 can be in a connected state (e.g., an RRC connected state).

[0106] As Figure 8 illustrated, example 800 can include a network node (NN) 110 and a UE 120 communicating to perform beam management using CSI-RS. Example 800 depicts a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure can be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam sweeping procedure, a cell search procedure, and / or a beam search procedure. As Figure 8 and illustrated by example 800, CSI-RS can be configured to be transmitted from the network node 110 to the UE 120. The CSI-RS can be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling), and / or aperiodic (e.g., using DCI).

[0107] The first beam management procedure can include the network node 110 performing a beam sweep on a plurality of transmit (Tx) beams. The network node 110 can transmit a CSI-RS using each transmit beam for beam management. To enable the UE 120 to perform a receive (Rx) beam sweep, the base station can transmit each CSI-RS multiple times (e.g., with repetition) within the same set of RS resources using the transmit beams, such that the UE 120 can sweep through receive beams over multiple transmission instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS can be transmitted M times on each of the N transmit beams, such that the UE 120 can receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 can perform a beam sweep of the UE 120’s receive beams. Thus, the first beam management procedure can enable the UE 120 to measure the CSI-RS on different transmit beams using different receive beams to support selection of network node 110 transmit beam / UE 120 receive beam beam pairs. The UE 120 can report the measurements to the network node 110 to enable the network node 110 to select one or more beam pairs for communication between the network node 110 and the UE 120. While example 800 has been described in connection with CSI-RS, the first beam management procedure can also use synchronization signal blocks (SSBs) to perform beam management in a similar manner as described above.

[0108] As shown in Figure 8 Example 810 can include network node 110 and UE 120 communicating to perform beam management using CSI-RS. Example 810 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure can be referred to as a beam refinement procedure, a base station beam refinement procedure, a TRP beam refinement procedure, and / or a transmission beam refinement procedure. As shown in Figure 8 and Example 810, CSI-RS can be configured to be transmitted from network node 110 to UE 120. The CSI-RS can be configured to be aperiodic (e.g., using DCI), or A-CSI. The second beam management procedure can include network node 110 performing a beam sweep on one or more transmission beams. The one or more transmission beams can be a subset of all transmission beams associated with network node 110 (e.g., determined based at least in part on measurements reported by UE 120 in connection with a first beam management procedure). Network node 110 can transmit a CSI-RS using each of the one or more transmission beams used for beam management. UE 120 can measure each CSI-RS using a single (e.g., same) reception beam (e.g., determined based at least in part on measurements performed in connection with the first beam management procedure). The second beam management procedure can enable network node 110 to select a best transmission beam based at least in part on measurements of the CSI-RS reported by UE 120 (e.g., measured by UE 120 using the single reception beam).

[0109] As shown in Figure 8 Example 820 depicts a third beam management procedure (e.g., P3 CSI-RS beam management). The third beam management procedure can be referred to as a beam refinement procedure, a UE beam refinement procedure, and / or a reception beam refinement procedure. As shown in Figure 8As shown in example 820, one or more CSI-RSs can be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs can be configured to be aperiodic (e.g., using DCI). The third beam management procedure can include the network node 110 transmitting the one or more CSI-RSs using a single transmit beam (e.g., determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure and / or the second beam management procedure). To enable the UE 120 to perform receive beam sweeping, the base station can transmit (e.g., with repetition) the CSI-RSs multiple times within the same set of RS resources using the transmit beam, such that the UE 120 can sweep through one or more receive beams in multiple transmission instances. The one or more receive beams can be a subset of all receive beams associated with the UE 120 (e.g., determined based at least in part on measurements performed in connection with the first beam management procedure and / or the second beam management procedure). The third beam management procedure can enable the network node 110 and / or the UE 120 to select a best receive beam based at least in part on reported measurements received from the UE 120 (e.g., reported measurements of the CSI-RSs of the transmit beam using the one or more receive beams).

[0110] As indicated above, Figure 8 are provided as examples of beam management procedures. Other examples of beam management procedures can differ from the examples described with respect to Figure 8 the example 820. For example, the UE 120 and the network node 110 can perform the third beam management procedure prior to performing the second beam management procedure, and / or the UE 120 and the network node 110 can perform similar beam management procedures to select a UE transmit beam.

[0111] Figure 9 is a diagram illustrating an example 900 of using beams for communication between a network entity (e.g., the network node 110) and a UE (e.g., the UE 120) in accordance with the present disclosure. As Figure 9 shown, the network node 110 and the UE 120 can communicate with one another.

[0112] The network node 110 can transmit to the UE 120 located within a coverage area of the network node 110. The network node 110 and the UE 120 can be configured for beamformed communications, where the network node 110 can transmit in the direction of the UE 120 using directional network entity transmit beams (e.g., BS transmit beams), and the UE 120 can receive the transmissions using directional UE receive beams. Each transmit beam can have an associated beam identifier (ID), beam direction, or beam symbol, among other examples. The network node 110 can transmit downlink communications via one or more transmit beams 905.

[0113] The UE 120 can attempt to receive downlink transmissions via one or more UE receive beams 910, which can be configured at the receive circuitry of the UE 120 using different beamforming parameters. The UE 120 can identify a particular transmit beam 905 (shown as transmit beam 905-A) and a particular UE receive beam 910 (shown as UE receive beam 910-A) that provide relatively good performance (e.g., that have the optimal channel quality of the measured different combinations of transmit beams 905 and UE receive beams 910). In some examples, the UE 120 can transmit an indication of which transmit beam 905 the UE 120 identifies as a preferred transmit beam for the network node 110 to use for transmissions to the UE 120. Thus, the UE 120 can obtain and maintain a beam pair link (BPL) (e.g., a combination of transmit beam 905-A and UE receive beam 910-A) with the network node 110 for downlink communications, which can be further refined and maintained in accordance with one or more established beam refinement procedures.

[0114] A downlink beam, such as a transmit beam 905 or a UE receive beam 910, can be associated with a TCI state. A TCI state can indicate a directionality or characteristics of a downlink beam, such as one or more quasi-co-location (QCL) characteristics of a downlink beam. QCL characteristics can include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameter, among other examples. In some examples, each transmit beam 905 can be associated with an SSB, and the UE 120 can indicate a preferred transmit beam 905 by transmitting an uplink transmission in resources of an SSB associated with the preferred transmit beam 905. A particular SSB can have an associated TCI state (e.g., for antenna port or for beamforming). In some examples, the network node 110 can indicate a downlink transmit beam 905 based at least in part on an antenna port QCL characteristic that can be indicated by a TCI state. A TCI state can be associated with one set of downlink reference signals (e.g., SSBs and aperiodic, periodic, or semi-persistent CSI-RS) for different QCL types (e.g., different combinations of QCL types for Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameter, among other examples). Where the QCL type indicates a spatial receive parameter, the QCL type can correspond to an analog receive beamforming parameter of a UE receive beam 910 at the UE 120. Thus, the UE 120 can select a corresponding UE receive beam 910 from a set of BPLs based at least in part on the network node 110 indicating a transmit beam 905 via a TCI indication.

[0115] The network node 110 can maintain a set of activated TCI states for downlink shared channel transmissions and a set of activated TCI states for downlink control channel transmissions. The set of activated TCI states for downlink shared channel transmissions can correspond to beams that the network node 110 uses for downlink transmissions on PDSCH. The set of activated TCI states for downlink control channel communications can correspond to beams that the network node 110 can use for downlink transmissions on PDCCH or in a control resource set (CORESET). The UE 120 can also maintain the set of activated TCI states for receiving downlink shared channel transmissions and CORESET transmissions. In cases where a TCI state is activated for the UE 120, the UE 120 can have one or more antenna configurations based at least in part on the TCI state, and the UE 120 can not need to reconfigure antenna or antenna weighting configurations. In some examples, the set of activated TCI states (e.g., activated PDSCH TCI states and activated CORESET TCI states) for the UE 120 can be configured by a configuration message, such as an RRC message.

[0116] Similarly, for uplink communications, the UE 120 can transmit in the direction of the network node 110 using directional UE transmit beams, and the network node 110 can receive the transmissions using directional receive beams. Each UE transmit beam can have an associated beam ID, beam direction, or beam symbol, etc. The UE 120 can transmit uplink communications via one or more UE transmit beams 915.

[0117] The network node 110 can receive uplink transmissions via one or more receive beams 920 (e.g., BS receive beams). The network node 110 can identify a particular UE transmit beam 915 (shown as UE transmit beam 915-A) and a particular receive beam 920 (shown as receive beam 920-A) that provide relatively good performance (e.g., that have the optimal channel quality of the measured different combinations of UE transmit beams 915 and receive beams 920). In some examples, the network node 110 can transmit an indication of which UE transmit beam 915 the network node 110 identifies as a preferred UE transmit beam from which the network node 110 can select to transmit from the UE 120. Thus, the UE 120 and the network node 110 can obtain and maintain a BPL for uplink communications (e.g., the combination of UE transmit beam 915-A and receive beam 920-A), which can be further refined and maintained in accordance with one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 915 or a BS receive beam 920, can be associated with a spatial relation. The spatial relation can indicate a directionality or characteristic of the uplink beam (similar to one or more QCL characteristics), as described above.

[0118] 3GPP standard Release 17 established a unified TCI state framework in which more than one beam can be indicated using a TCI state. A TCI state can be used to indicate a beam for a downlink channel or reference signal (RS) and / or an uplink channel or RS. There can be multiple types of unified TCI states. For example, a joint TCI state can indicate a common beam for at least one downlink channel or RS and at least one uplink channel or RS. This can be Type 1 and can include at least UE-specific PDCCH, PDSCH, PUCCH, and PUSCH. A downlink TCI state can indicate a common beam for more than one downlink channel or RS. This can be Type 2 and can include at least UE-specific PDCCH and PDSCH. An uplink TCI state can indicate a common beam for more than one uplink channel or RS. This can be Type 3 and can include at least UE-specific PUCCH and PUSCH. Other types of unified TCI states can include a separate downlink single-channel or RS TCI state indicating a beam for a single downlink channel or RS, a separate uplink single-channel or RS TCI state indicating a beam for a single uplink channel or RS, or uplink spatial relation information, such as a spatial relation indicator (SRI), indicating a beam for a single uplink channel or RS.

[0119] A network entity can send a unified TCI state indication indicating a unified TCI state. The unified TCI state indication can provide a downlink or joint TCI state with QCL Type 1 (e.g., for QCL Type A) and QCL Type 2 (e.g., for QCL Type D). The unified TCI state indication can also provide a downlink or joint TCI state with power control parameters, such as a P0 value, an a value, or cross-link interference (CLI) information. For a joint TCI state, the unified TCI state indication can indicate a path loss RS. For an uplink TCI state, the unified TCI state indication can indicate an RS (e.g., for a spatial filter) and / or a power control parameter.

[0120] A UE can be configured for A-CSI, and A-CSI can be triggered by DCI. The configuration for A-CSI trigger states can be included in reporting configuration information, such as CSI- AssociatedReportConfiglnfo of CSI-AperiodicTriggerState. A-CSI can involve A-CSI-RS received using an A-CSI-RS resource set. In the unified TCI framework for sDCI for multi-TRP, there can be no QCL information (e.g., QCL-Info) for an A-CSI resource set configured for CSI feedback and beam management. Without such QCL information, the UE is not clear on which unified TCI states the UE is to use for one or more A-CSI-RS resource sets. This uncertainty can result in suboptimal unified TCI state selection for A-CSI-RS, which will degrade the accuracy of A-CSI and degrade the communication. The degraded communication wastes processing resources and signaling resources.

[0121] As indicated above, Figure 9 are provided as examples. Other examples can differ from what is described with respect to Figure 9 the examples described with respect to

[0122] Figure 10 is a diagram illustrating an example 1000 of a delay profile in accordance with the present disclosure.

[0123] In some scenarios, eType-II CSI feedback can have large timing errors. Example 1000 shows a UE at different distances from two TRPs. Due to inter-TRP time synchronization errors or propagation delay differences between the UE and the two TRPs, the downlink timing of the PDSCH signals received at the UE can have large misalignments between the two TRPs. UE movement can cause time-varying propagation delay differences, with the delay 0 of TRP 0 and the delay 1. The downlink (e.g., PDSCH communication) timing difference between TRPs can also vary over time due to independent clock drift in TRP 0 and TRP 1.

[0124] In the case of CJT precoding, the UE can observe a composite channel with large delay spread on the PDSCH DMRS. The eType-II CSI feedback can have large delay spread. The resolvable delay span D of the eType-II CSI feedback can be determined by the bandwidth of the PMI subbands. In the delay domain, delay taps (received times) larger than the resolvable delay span D are aliased (wrapped around in the channel phase that cannot be distinguished by the receiver). With two PMI subbands per CQI subband, the resolvable delay span D is doubled. With N3 frequency domain (FD) bases, each FD base represents one delay tap with D / N3 granularity.

[0125] Example 1000 also illustrates a power delay profile (PDP) where the UE uses TCI state 0 for beams from TRP 0 and TCI state 1 for beams from TRP 1. The combined PDP can show a time gap or time misalignment of signals from TRP 0 and TRP 1.

[0126] In some examples, the UE can perform per-TRP delay compensation and reporting. Before using singular value decomposition (SVD) to obtain the matrix, the UE can use an algorithm for reporting where the term is used to represent the TRP relative delay (TRP #n to 1). In a first step, the UE can determine such that where is the measured channel of TRP #n without FD phase rotation (delay compensation). At a second step, the UE can compute the PMI based on and based on the following mode 2 (FD joint) codebook (CB): At a third step, the UE can report as the PMI parameter, and a mode 1 (FD independent CB) precoder can be represented as:

[0127] where .

[0128] As indicated above, Figure 10 is provided as an example. Other examples can differ from what is described with respect to the example Figure 10 described with respect to the example

[0129] Figure 11 is a diagram illustrating an example 1100 of a predicted TCI state in accordance with the present disclosure.

[0130] In some scenarios, a UE can be configured with per-TRP TCI states. A network entity can configure and activate TCI states per TRP. The network entity can transmit TRS per TRP. The UE can construct a delay profile for channel estimation by combining per-TRP PDPs. Example 1100 shows the combination of PDPs.

[0131] In some scenarios, a UE can be configured with single frequency network (SFN) TCI states. A network entity can configure TCI states associated with multiple TRPs (shown as TRP 0, TRP 1, and TRP 2). The network entity can transmit TRS from the multiple TRPs in an SFN manner. The UE can obtain a delay profile for channel estimation from the SFN TRS, as shown in example 1102.

[0132] When a UE reports As CSI feedback, the network entity can use the reported for subband MIMO precoding determination. However, the TRS and PDSCH communications can not be time-aligned, and not compensated for timing misalignment. Thus, any noise filtering prior to channel estimation can not be as effective. For example, noise filtering can be performed on signals from TRP 0, but not on misaligned signals from TRP 1. With less effective filtering, channel estimation can not be as accurate, and thus communications can be degraded. Degraded communications can waste power and signaling resources if the communications are lost or retransmitted.

[0133] As indicated above, Figure 11 are provided as examples. Other examples can differ from what is described with respect to Figure 11 the examples described.

[0134] Figure 12 is a diagram illustrating example 1200 of PDSCH transmission with per-TRP TRS, in accordance with the present disclosure.

[0135] According to various aspects described herein, a network entity can use the reported for both subband MIMO precoding determination and PDSCH delay pre-compensation. PDSCH delay pre-compensation includes adjusting the transmission time of PDSCH communications from the TRPs to align the arrival time of the PDSCH communications at the UE. This can result in a delay profile in which reception from the TRPs is aligned in time. The UE can be expected to be aware of the network entity’s behavior of PDSCH transmission with delay pre-compensation in order to make proper channel estimation and demodulation. The UE can use this information to filter received communications to reduce noise in channel estimation. If the network entity applies delay pre-compensation to PDSCH communications, the UE can expect to receive information about the pre-compensation in the TRS transmission.

[0136] For example, a UE can receive and measure CSI-RS from TRP 0 and TRP 1. The UE can transmit a timing offset value such as and a PMI based at least in part on the CSI-RS measurements. The UE can receive TRS from TRP 0 and TRP 1 and generate a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS. The UE can receive a PDSCH communication jointly transmitted from TRP 0 and TRP 1 based at least in part on the delay profile (pre-compensated). By pre-compensating for PDSCH delay, the time of arrival of PDSCH communications from multiple TRPs can be more time-aligned. Filtering can be more efficient for reception from all TRPs, and communications can be improved. Improving communications saves power and signaling resources that would otherwise be wasted due to unsuccessful communications.

[0137] Example 1200 illustrates an example of delay pre-compensation of TRP 1 relative to TRP 0. A UE can receive TRS, CSI-RS, and / or PDSCH communications from TRP 0 with a propagation delay of 0. The UE can receive TRS, CSI-RS, and / or PDSCH communications from TRP 1 at a different distance with a propagation delay of 1.

[0138] As illustrated by timing diagram 1202, the propagation delay can be different due to the different distances of the TRPs from the UE. However, in some aspects, a network entity can use the TRP 0 TRS as an anchor TRS such that other TRSs, such as the TRP 1 TRS, use the average delay of the TRP 0 TRS to align the delay of the TRP 1 with the delay of the TRP 0. The network entity can indicate that the TRP 0 TRS is to be the anchor TRS for the average delay. The TRP 0 TRS can be associated with a QCL reference for the average delay and the delay spread. The TRP 1 TRS can be associated with a QCL reference for only the delay spread (and not the average delay of the TRP 1 TRS). The UE can expect that the TRS 1 PDP can be anchored on the TRS 0 PDP with respect to the average delay. Timing diagram 1202 illustrates the original delay 1 (dashed line) can then be aligned with the delay 0, as illustrated by the arrow and the solid line for 0. Timing diagram 1204 illustrates that a first CSI-RS from TRP 0 and a second CSI-RS from TRP 1 can have different propagation delays.

[0139] Timing diagram 1206 illustrates that PDSCH communication can be pre-compensated for delays in order to align the timing of received PDSCH communications from TRP 0 and TRP 1. In some respects, the transmission of PDSCH communications from TRP 1 can be pre-compensated for delays by adding or subtracting... 1 and Differences between 0, such as 1 + ( 0 - 1) = 0.

[0140] As indicated above, Figure 12 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 12 The examples described are different.

[0141] Figure 13 This is a diagram illustrating Example 1300 associated with delay pre-compensation according to this disclosure. (See diagram for example.) Figure 13 As shown, network entity 1310 (e.g., network node 110) and UE 1320 (e.g., UE 120) can communicate with each other. Network entity 1310 can control TRP 1312 and TRP 1314.

[0142] As shown by reference numeral 1325 in the attached figure, network entity 1310 may transmit a first CSI-RS via TRP 1312 and a second CSI-RS via TRP 1314. The TRPs may be located at different distances from UE 1320. UE 1320 may measure the CSI-RS and determine the timing offset value (e.g., the timing offset of each TRPn in a plurality of TRPs) based at least in part on the different reception times of the CSI-RS. The timing offset value can be the propagation time difference between TRP 1312 and TRP 1314. The timing offset value can also be the received signal timing difference between TRP 1312 and TRP 1314. UE 1320 can generate PMI at least partially based on CSI-RS. PMI can be at least partially based on one or more timing offset values. As shown by reference numeral 1330, UE 1320 can transmit one or more timing offset values ​​and / or PMI (as part of CSI feedback).

[0143] As shown by reference number 1335, TRP 1312 and TRP 1314 can transmit TRSs. In some aspects, TRP 1312 can transmit a first TRS and TRP 1314 can transmit a second TRS. As shown by reference number 1340, network entity 1310 can transmit an indication of whether the first TRS or the second TRS is an anchor TRS. As shown by reference number 1345, UE 1320 can generate a delay profile based at least in part on an average delay of the anchor TRS. In some aspects, UE 1320 can apply the average delay to a QCL reference of the second TRS.

[0144] As shown by reference number 1350, network entity 1310 can transmit a PDSCH communication (or multiple PDSCH communications) from TRP 1312 and TRP 1314. UE 1320 can estimate a channel from a DMRS in the PDSCH communication for PDSCH demodulation based at least in part on the delay profile generated from the TRS.

[0145] As indicated above, Figure 13 are provided as examples. Other examples can differ from what is described with respect to Figure 13 the examples described with respect to

[0146] Figure 14 is a diagram illustrating an example 1400 of reception timing in an SFN, in accordance with the present disclosure.

[0147] In some aspects, TRP 1312 and TRP 1314 can be part of an SFN and can transmit SFN TRSs, as shown by example 1400. UE 1320 can generate a delay profile from the SFN TRSs for demodulation of a PDSCH jointly transmitted from TRP 1312 and TRP 1314. When timing offsets are not compensated for with respect to the TRSs and the PDSCH communication, the timing offsets can be compensated for in a MIMO precoding determination.

[0148] Network entity 1310 can apply only to subband MIMO precoding determinations. Network entity 1310 can transmit a PDSCH communication and SFN TRSs and / or a PDSCH communication without delay precompensation. For example, network entity 1310 can transmit a PDSCH communication from TRP 1314 with MIMO precoding and without timing offset precompensation. The timing diagram in example 1400 shows a delay profile with misaligned timing. The SFN TRSs can be a QCL reference for average delay and delay spread. UE 1320 can derive the average delay and the delay spread from the SFN TRSs.

[0149] As indicated above, Figure 14are provided as examples. Other examples can differ from what is described with regard to Figure 14 the examples described with regard to

[0150] Figure 15 is a diagram illustrating an example 1500 of pre-compensation in SFN according to the present disclosure.

[0151] In some aspects, the network entity 1310 and the UE 1320 can apply delay pre-compensation in SFN based at least in part on the timing offset. For example, the network entity 1310 can apply to PDSCH delay pre-compensation and TRS delay pre-compensation. The SFN TRS can be a QCL reference for average delay and delay spread. The UE 1320 can derive the average delay and delay spread from the SFN TRS. This scheme can be applied when SFN TRS is configured per UE.

[0152] When the timing offset is compensated for TRS and PDSCH pair, the timing offset can be ignored in MIMO precoding determination. Example 1500 shows a timing diagram 1502 within the aligned reception timing after applying delay pre-compensation for SFN TRS (e.g., TRP 1 TRS). Timing diagram 1504 shows timing alignment for PDSCH.

[0153] As indicated above, Figure 15 are provided as examples. Other examples can differ from what is described with regard to Figure 15 the examples described with regard to

[0154] Figure 16 is a diagram illustrating an example 1600 of updating delay compensation according to the present disclosure.

[0155] As shown by reference number 1602, the UE 1320 can report CSI (e.g., PMI) with a new timing offset value. As shown by reference number 1604, the network entity can update subband MIMO precoding based at least in part on the reported CSI (e.g., timing value offset, PMI). In some aspects, as shown by reference number 1606, the network entity 1310 can update the timing offset pre-compensation for TRS transmitted from the TRP 1314 at a next TRS occasion after receiving the new timing offset value.

[0156] As shown by reference number 1608, the UE 1320 can update QCL for channel estimation. The UE 1320 can update the QCL based at least in part on the new timing offset value. In some aspects, as shown by reference number 1610, the network entity 1310 can update the timing offset pre-compensation for PDSCH transmitted from the TRP 1314 after transmission of TRS at a next TRS occasion based at least in part on the new timing offset value.

[0157] As indicated above, Figure 16 are provided as examples. Other examples can differ from what is described with respect to Figure 16 the described examples.

[0158] Figure 17 is a diagram illustrating an example process 1700 performed, for example, by a UE, in accordance with aspects of the present disclosure. Example process 1700 is an example of a process for performing operations associated with delay compensation for multiple TRPs by a UE (e.g., UE 120, UE 1320).

[0159] As Figure 17 further shown, in some aspects, process 1700 can include receiving a first CSI-RS from a first TRP and a second CSI-RS from a second TRP (block 1710). For example, the UE (e.g., using reception component 1902 and / or communication manager 1906, depicted) can receive a first CSI-RS from a first TRP and a second CSI-RS from a second TRP, as described above. Figure 19 As

[0160] further shown, in some aspects, process 1700 can include transmitting a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS (block 1720). For example, the UE (e.g., using transmission component 1904 and / or communication manager 1906, depicted) can transmit a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS, as described above. Figure 17 Figure 19 As further shown, in some aspects, process 1700 can include receiving a TRS from the first TRP and the second TRP (block 1730). For example, the UE (e.g., using reception component 1902 and / or communication manager 1906, depicted) can receive a TRS from the first TRP and the second TRP, as described above.

[0161] Figure 17 As Figure 19 further shown, in some aspects, process 1700 can include generating a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS (block 1740). For example, the UE (e.g., using communication manager 1906, depicted) can generate a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS, as described above.

[0162] As Figure 17 further shown, in some aspects, process 1700 can include generating a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS (block 1740). For example, the UE (e.g., using communication manager 1906, depicted) can generate a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS, as described above. Figure 19 As

[0163] further shown, in some aspects, process 1700 can include generating a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS (block 1740). For example, the UE (e.g., using communication manager 1906, depicted) can generate a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS, as described above. Figure 17 ​Further, in some aspects, process 1700 can include receiving, based at least in part on the delay profile, a PDSCH communication jointly transmitted from the first TRP and the second TRP (block 1750). For example, the UE (e.g., using reception component 1902 and / or communication manager 1906, depicted above) can receive, based at least in part on the delay profile, a PDSCH communication jointly transmitted from the first TRP and the second TRP, as described above. Figure 19 The depicted reception component 1902 and / or communication manager 1906 can receive, based at least in part on the delay profile, a PDSCH communication jointly transmitted from the first TRP and the second TRP, as described above.

[0164] Process 1700 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0165] In a first aspect, process 1700 includes measuring a PMI for joint transmission of PDSCH from the first TRP and the second TRP based at least in part on a timing offset value, where the timing offset value indicates a difference in received signal timing between the first TRP and the second TRP.

[0166] In a second aspect, alone or in combination with the first aspect, receiving the TRS includes receiving a first TRS from the first TRP and a second TRS from the second TRP.

[0167] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1700 includes receiving an indication of whether the first TRS or the second TRS is an anchor TRS, and generating the delay profile includes generating the delay profile further based at least in part on an average delay of the anchor TRS.

[0168] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first TRS is the anchor TRS, and process 1700 includes applying an average delay of the anchor TRS to a QCL reference of the second TRS.

[0169] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, receiving the TRS includes receiving a SFN TRS from the first TRP and the second TRP, and generating the delay profile includes generating the delay profile from the SFN TRS for demodulation of the PDSCH jointly transmitted from the first TRP and the second TRP.

[0170] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 1700 includes estimating a channel from a DMRS in the PDSCH communication based at least in part on the delay profile generated from the TRS for PDSCH demodulation.

[0171] Although Figure 17 Example blocks of process 1700 are illustrated, but in some aspects, process 1700 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 17. In some aspects, process 1700 can include one or more additional processes or methods described elsewhere herein. For example, process 1700 can include one or more processes described with reference to FIGs. 1-16.Figure 17 Compared to the boxes depicted, process 1700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1700 may be executed in parallel.

[0172] Figure 18 This is a diagram illustrating, for example, an example process 1800 performed by a network entity according to this disclosure. Example process 1800 is an example of a network entity (e.g., network node 110, network entity 1310) performing operations associated with delay compensation for multiple TRPs.

[0173] like Figure 18 As shown, in some aspects, process 1800 may include sending a first CSI-RS from a first TRP and sending a second CSI-RS from a second TRP (box 1810). For example, network entities (e.g., using...) Figure 20 The transmission component 2004 and / or communication manager 2006 described above can transmit a first CSI-RS from a first TRP and a second CSI-RS from a second TRP.

[0174] like Figure 18 As further shown, in some aspects, process 1800 may include receiving a timing offset value and a PMI (box 1820). For example, a network entity (e.g., using...) Figure 20 The described receiving component 2002 and / or communication manager 2006 can receive timing offset values ​​and PMIs, as described above.

[0175] like Figure 18 As further shown, in some aspects, process 1800 may include sending a TRS from a first TRP and a second TRP (box 1830). For example, network entities (e.g., using...) Figure 20 The transmission component 2004 and / or communication manager 2006 depicted can transmit TRS from the first TRP and the second TRP, as described above.

[0176] like Figure 18 As further shown, in some aspects, process 1800 may include jointly sending PDSCH communication from a first TRP and a second TRP (box 1840) based at least in part on a timing offset value and PMI. For example, network entities (e.g., using...) Figure 20 The transmission component 2004 and / or communication manager 2006 described herein may transmit PDSCH communications jointly from the first TRP and the second TRP, at least in part, based on the timing offset value and PMI, as described above.

[0177] Process 1800 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0178] In a first aspect, transmitting the TRS includes transmitting the first TRS from the first TRP and transmitting the second TRS from the second TRP.

[0179] In a second aspect, alone or in combination with the first aspect, process 1800 includes transmitting an indication of whether the first TRS or the second TRS is an anchor TRS.

[0180] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1800 includes transmitting the PDSCH communication from the TRP associated with the non-anchor TRS after the timing offset pre-compensation.

[0181] In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the TRS includes transmitting a single frequency network (SFN) TRS from the first TRS and the second TRP.

[0182] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting the SFN TRS and the PDSCH communication includes transmitting the SFN TRS and the PDSCH communication without timing offset pre-compensation.

[0183] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 1800 includes compensating MIMO precoding for a PDSCH transmitted from the second TRP based at least in part on the timing offset value.

[0184] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, transmitting the TRS and the PDSCH communication includes transmitting the TRS and the PDSCH communication from the second TRP after the timing offset pre-compensation.

[0185] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 1800 includes updating timing offset pre-compensation for a TRS transmitted from the second TRP at a next TRS occasion after receiving a new timing offset value from the UE based at least in part on the new timing offset value.

[0186] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 1800 includes updating timing offset pre-compensation for a PDSCH transmitted from the second TRP after transmission of a TRS at a next TRS occasion based at least in part on the new timing offset value.

[0187] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, transmitting the PDSCH communication includes transmitting the PDSCH communication from the second TRP with MIMO precoding and without pre-compensation of a timing offset.

[0188] Although Figure 18 Example blocks of the process 1800 are illustrated, but in some aspects, the process 1800 can include Figure 18 more blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted. Additionally or alternatively, two or more of the blocks of the process 1800 can be performed in parallel.

[0189] Figure 19 is a diagram of an example apparatus 1900 for wireless communication in accordance with the present disclosure. The apparatus 1900 can be a UE (e.g., UE 120, UE 1320), or a UE can include the apparatus 1900. In some aspects, the apparatus 1900 includes a reception component 1902, a transmission component 1904, and / or a communication manager 1906, which can communicate with one another Figure 1 The apparatus 1900 can be used to perform techniques described herein, for example, with reference to FIGs. 1-17. In some aspects, the apparatus 1900 can be configured to perform one or more of the operations described herein in conjunction with

[0190] In some aspects, the apparatus 1900 can be configured to perform one or more operations described herein in conjunction with Figures 1-16 Additionally or alternatively, the apparatus 1900 can be configured to perform one or more processes described herein, such as process 1700 of Figure 17 In some aspects, the apparatus 1900 and / or one or more components shown in Figure 19 may include one or more components of a UE described in connection with Figure 2 Additionally or alternatively, one or more components shown in Figure 19 may be implemented within one or more components described in connection with Figure 2 Additionally or alternatively, one or more components of a set of components can be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0191] The reception component 1902 can receive communications, such as reference signals, control information, data communications, or any combination thereof, from the apparatus 1908. The reception component 1902 can provide received communications to one or more other components of the apparatus 1900. In some aspects, the reception component 1902 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1900. In some aspects, the reception component 1902 can include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE. Figure 2 the described UE.

[0192] The transmission component 1904 can transmit communications, such as reference signals, control information, data communications, or any combination thereof, to the apparatus 1908. In some aspects, one or more other components of the apparatus 1900 can generate communications and can provide the generated communications to the transmission component 1904 for transmission to the apparatus 1908. In some aspects, the transmission component 1904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 1908. In some aspects, the transmission component 1904 can include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or any combination thereof, as described with reference to the UE. In some aspects, the transmission component 1904 can be co-located with the reception component 1902 in a transceiver. Figure 2 the described UE.

[0193] The communication manager 1906 can support the operations of the reception component 1902 and / or the transmission component 1904. For example, the communication manager 1906 can receive information associated with configuring reception of communications by the reception component 1902 and / or transmission of communications by the transmission component 1904. Additionally, or alternatively, the communication manager 1906 can generate control information and / or provide control information to the reception component 1902 and / or the transmission component 1904 to control the reception and / or transmission of communications.

[0194] The reception component 1902 can receive a first CSI-RS from a first TRP and a second CSI-RS from a second TRP. The transmission component 1904 can transmit a timing offset value and a PMI measured based at least in part on the first CSI-RS and the second CSI-RS. The reception component 1902 can receive a TRS from the first TRP and the second TRP. The communication manager 1906 can generate a delay profile for channel estimation for PDSCH demodulation based at least in part on the TRS. The reception component 1902 can receive a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

[0195] The communication manager 1906 can measure a PMI for joint transmission of a PDSCH from a first TRP and a second TRP based at least in part on a timing offset value, where the timing offset value indicates a received signal timing difference between the first TRP and the second TRP.

[0196] The reception component 1902 can receive an indication of whether a first TRS or a second TRS is an anchor TRS, and the communication manager 1906 can generate a delay profile based at least in part on an average delay of the anchor TRS.

[0197] The communication manager 1906 can estimate a channel from a demodulation reference signal (DMRS) in a PDSCH communication for PDSCH demodulation based at least in part on a delay profile generated from a TRS.

[0198] Figure 19 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 19 There can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 19 Two or more components shown can be implemented within a single component, or Figure 19 A single component shown can be implemented as multiple, distributed components. Additionally or alternatively, Figure 19 A set of one or more components shown can be implemented to perform one or more functions described as being performed by another set of one or more components shown. Figure 19 One or more functions described as being performed by one set of components shown can be instead performed by another set of components shown.

[0199] Figure 20 FIGURE 18 is a diagram of an example apparatus 1800 for wireless communication in accordance with aspects of the present disclosure. The apparatus 1800 can be a network entity (e.g., a network node 110, a network entity 1310), or a network entity can include the apparatus 1800. In some aspects, the apparatus 1800 includes means for receiving 1802, means for transmitting 1804, and / or means for communicating 1806, which can be, e.g., the reception component 1202, the transmission component 1204, and / or the communication manager 1206, respectively, of FIGURE 12, and / or can include one or more other components of the network entity.Figure 1 The described communication manager 150. As shown, the device 2000 can communicate with another device 2008 (such as a UE or a network node (such as a CU, DU, RU or base station)) using the receiving component 2002 and the transmitting component 2004.

[0200] In some respects, device 2000 can be configured to perform the functions described herein. Figures 1-16 One or more operations described herein. Additionally or alternatively, the apparatus 2000 may be configured to perform one or more processes described herein, such as Figure 18 The process 1800. In some respects, the apparatus 2000 and / or Figure 20 One or more components shown may include combinations Figure 2 One or more components of the described network entity. Additionally or alternatively, Figure 20 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0201] Receiver 2002 may receive communications from device 2008, such as reference signals, control information, data communications, or combinations thereof. Receiver 2002 may provide the received communications to one or more other components of device 2000. In some aspects, receiver 2002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 2000. In some aspects, receiver 2002 may include combinations of... Figure 2 The network entity described includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

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

[0203] The communication manager 2006 can support operations of the reception component 2002 and / or the transmission component 2004. For example, the communication manager 2006 can receive information associated with configuring reception of communications by the reception component 2002 and / or transmission of communications by the transmission component 2004. Additionally, or alternatively, the communication manager 2006 can generate and / or provide control information to the reception component 2002 and / or the transmission component 2004 to control the reception and / or transmission of communications.

[0204] The transmission component 2004 can transmit the first CSI-RS from the first TRP and the second CSI-RS from the second TRP. The reception component 2002 can receive a timing offset value and a PMI. The transmission component 2004 can transmit the TRS from the first TRP and the second TRP. The transmission component 2004 can jointly transmit a PDSCH communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0205] The transmission component 2004 can transmit an indication of whether the first TRS or the second TRS is an anchor TRS. The transmission component 2004 can transmit a PDSCH communication from a TRP associated with a non-anchor TRS after timing offset pre-compensation. The communication manager 2006 can pre-compensate MIMO precoding for a PDSCH transmitted from the second TRP based at least in part on the timing offset value.

[0206] The communication manager 2006 can update timing offset pre-compensation for a TRS transmitted from the second TRP at a next TRS occasion after receiving a new timing offset value from the UE based at least in part on the new timing offset value. The communication manager 2006 can update timing offset pre-compensation for a PDSCH transmitted from the second TRP after transmission of a TRS at the next TRS occasion based at least in part on the new timing offset value.

[0207] Figure 20 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 20 There can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 20 Two or more of the components shown can be implemented within a single component, or Figure 20 The single component shown can be implemented as multiple, distributed components. Additionally or alternatively,Figure 20 The set of one or more components shown can perform one or more functions described as being performed by Figure 20 another set of components shown.

[0208] SUMMARY

[0209] Aspect 1 : A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; transmitting a timing offset value and a precoding matrix indicator (PMI) measured based at least in part on the first CSI-RS and the second CSI-RS; receiving a tracking reference signal (TRS) from the first TRP and the second TRP; generating a delay profile for channel estimation based at least in part on the TRS for physical downlink shared channel (PDSCH) demodulation; and receiving a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

[0210] Aspect 2: The method of Aspect 1, further comprising: measuring the PMI for joint transmission of PDSCH from the first TRP and the second TRP based at least in part on the timing offset value, wherein the timing offset value indicates a received signal timing difference between the first TRP and the second TRP.

[0211] Aspect 3: The method of any of Aspects 1-2, wherein receiving the TRS comprises: receiving a first TRS from the first TRP and a second TRS from the second TRP.

[0212] Aspect 4: The method of Aspect 3, further comprising: receiving an indication of whether the first TRS or the second TRS is an anchor TRS, and wherein generating the delay profile comprises: generating the delay profile further based at least in part on an average delay of the anchor TRS.

[0213] Aspect 5: The method of Aspect 4, wherein the first TRS is the anchor TRS, and wherein the method further comprises: applying the average delay of the anchor TRS to a quasi co- location (QCL) reference of the second TRS.

[0214] Aspect 6: The method of any of aspects 1 through 5, wherein receiving the TRS comprises: receiving a single frequency network (SFN) TRS from the first TRP and the second TRP, and wherein generating the delay profile comprises: generating the delay profile from the SFN TRS for demodulating a PDSCH transmitted jointly from the first TRP and the second TRP.

[0215] Aspect 7: The method of any of aspects 1 through 6, the method further comprising: estimating a channel from a demodulation reference signal (DMRS) in the PDSCH communication for PDSCH demodulation based at least in part on the delay profile generated from the TRS.

[0216] Aspect 8: A method of wireless communication performed by a network entity, the method comprising: transmitting a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; receiving a timing offset value and a precoding matrix indicator (PMI); transmitting a tracking reference signal (TRS) from the first TRP and the second TRP; and jointly transmitting a physical downlink shared channel (PDSCH) communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

[0217] Aspect 9: The method of aspect 8, wherein transmitting the TRS comprises: transmitting a first tracking reference signal (TRS) from the first TRP and a second TRS from the second TRP.

[0218] Aspect 10: The method of aspect 9, the method further comprising: transmitting an indication of whether the first TRS or the second TRS is an anchor TRS.

[0219] Aspect 11: The method of aspect 9, the method further comprising: transmitting the PDSCH communication from a TRP associated with a non-anchor TRS after timing offset pre-compensation.

[0220] Aspect 12: The method of any of aspects 8 through 11, wherein transmitting the TRS comprises: transmitting a single frequency network (SFN) TRS from the first TRP and the second TRP.

[0221] Aspect 13: The method of aspect 12, wherein transmitting the SFN TRS and the PDSCH communication comprises: transmitting the SFN TRS and the PDSCH communication without timing offset pre-compensation.

[0222] Aspect 14: The method of aspect 13, further comprising pre-compensating, based at least in part on the timing offset value, multiple-input multiple-output (MIMO) precoding for the PDSCH transmitted from the second TRP.

[0223] Aspect 15: The method of aspect 12, wherein transmitting the TRS and the PDSCH communication comprises transmitting the TRS and the PDSCH communication from the second TRP after timing offset pre-compensation.

[0224] Aspect 16: The method of aspect 15, wherein transmitting the PDSCH communication comprises transmitting the PDSCH communication from the second TRP with MIMO precoding and without timing offset pre-compensation.

[0225] Aspect 17: The method of aspect 15, further comprising updating the timing offset pre-compensation for the TRS transmitted from the second TRP at a next TRS occasion after receiving a new timing offset value from a user equipment based at least in part on the new timing offset value.

[0226] Aspect 18: The method of aspect 17, further comprising updating the timing offset pre-compensation for the PDSCH transmitted from the second TRP after transmission of the TRS at the next TRS occasion based at least in part on the new timing offset value.

[0227] Aspect 19: An apparatus for wireless communication at a device, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-18.

[0228] Aspect 20: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-18.

[0229] Aspect 21: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 1-18.

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

[0231] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-18.

[0232] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or from practicing the aspects.

[0233] As used herein, the term “component” is intended to be broadly interpreted to encompass hardware and / or a combination of hardware and software. “Software” shall be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — because software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0234] As used herein, depending on the context, “satisfy a threshold” can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0235] Although specific combinations of features are set out in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of the features described herein can be combined in ways not specifically recited in the claims or described in the specification. The disclosure of various aspects includes each and every combination of the features described herein (and / or in the claims). As used herein, the phrase “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of items from among a, b, and c (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c, or combinations with multiples of the same element, To the extent that any terms are given definitions herein, those definitions are not intended to limit the meanings of those terms unless expressly so defined herein.

[0236] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items unless otherwise indicated by context. Also, as used herein, the terms “has,” “have,” or “having” or variants thereof are intended to be open-ended terms that do not limit the item described by those terms to the item only, but rather, to one or more items. Further, the phrase “based on” is intended to be open-ended, and to not limit the item described by those terms to the item only, but rather, to one or more items. Also, as used herein, the term “or” when used in a list of two or more items, is intended to be an open-ended term that can be interpreted to mean any one item in the list, or any combination of items in the list.

Claims

1. A user equipment (UE) for wireless communication, the UE comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to: receive a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; transmit a timing offset value and a precoding matrix indicator (PMI) measured based at least in part on the first CSI-RS and the second CSI-RS; receive a tracking reference signal (TRS) from the first TRP and the second TRP; generate a delay profile for channel estimation based at least in part on the TRS for physical downlink shared channel (PDSCH) demodulation; and receive a PDSCH communication transmitted jointly from the first TRP and the second TRP based at least in part on the delay profile.

2. The UE of claim 1, wherein the one or more processors are configured to measure the PMI for joint transmission of PDSCH from the first TRP and the second TRP based at least in part on the timing offset value, wherein the timing offset value indicates a received signal timing difference between the first TRP and the second TRP.

3. The UE of claim 1, wherein to receive the TRS, the one or more processors are configured to receive a first TRS from the first TRP and a second TRS from the second TRP.

4. The UE of claim 3, wherein the one or more processors are configured to receive an indication of whether the first TRS or the second TRS is an anchor TRS, and wherein to generate the delay profile, the one or more processors are configured to generate the delay profile further based at least in part on an average delay of the anchor TRS.

5. The UE of claim 4, wherein the first TRS is the anchor TRS, and wherein the one or more processors are configured to apply the average delay of the anchor TRS to a quasi co-location (QCL) reference of the second TRS.

6. The UE of claim 1, wherein to receive the TRS, the one or more processors are configured to receive a single frequency network (SFN) TRS from the first TRP and the second TRP, and wherein to generate the delay profile, the one or more processors are configured to generate the delay profile from the SFN TRS for demodulation of PDSCH transmitted jointly from the first TRP and the second TRP.

7. The UE of claim 1, wherein the one or more processors are configured to estimate a channel from a demodulation reference signal (DMRS) in the PDSCH communication for PDSCH demodulation based at least in part on the delay profile generated from the TRS.

8. A network entity for wireless communication, the network entity comprising: a memory; And one or more processors coupled to the memory, the one or more processors configured to: transmit a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; receive a timing offset value and a precoding matrix indicator (PMI); transmit a tracking reference signal (TRS) from the first TRP and the second TRP; and transmit a physical downlink shared channel (PDSCH) communication from the first TRP and the second TRP jointly based at least in part on the timing offset value and the PMI.

9. The network entity of claim 8, wherein to transmit the TRS, the one or more processors are configured to transmit a first tracking reference signal (TRS) from the first TRP and a second TRS from the second TRP.

10. The network entity of claim 9, wherein the one or more processors are configured to transmit an indication of whether the first TRS or the second TRS is an anchor TRS.

11. The network entity of claim 9, wherein the one or more processors are configured to transmit the PDSCH communication from a TRP associated with a non-anchor TRS after timing offset pre-compensation.

12. The network entity of claim 8, wherein to transmit the TRS, the one or more processors are configured to transmit a single frequency network (SFN) TRS from the first TRS and the second TRP.

13. The network entity of claim 12, wherein to transmit the SFN TRS and the PDSCH communication, the one or more processors are configured to transmit the SFN TRS and the PDSCH communication without timing offset pre-compensation.

14. The network entity of claim 13, wherein the one or more processors are configured to compensate for multiple input multiple output (MIMO) precoding for the PDSCH transmitted from the second TRP based at least in part on the timing offset value.

15. The network entity of claim 12, wherein to transmit the TRS and the PDSCH communication, the one or more processors are configured to transmit the TRS and the PDSCH communication from the second TRP after timing offset pre-compensation.

16. The network entity of claim 15, wherein to transmit the PDSCH communication, the one or more processors are configured to transmit the PDSCH communication from the second TRP without timing offset pre-compensation with MIMO precoding.

17. The network entity of claim 15, wherein the one or more processors are configured to update the timing offset pre-compensation for the TRS transmitted from the second TRP at a next TRS occasion after receiving a new timing offset value from a user equipment based at least in part on the new timing offset value.

18. The network entity of claim 17, wherein the one or more processors are configured to update the timing offset pre-compensation for the PDSCH transmitted from the second TRP after the transmission of the TRS at the next TRS occasion based at least in part on the new timing offset value.

19. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; transmitting a timing offset value and a precoding matrix indicator (PMI) measured based at least in part on the first CSI-RS and the second CSI-RS; receiving a tracking reference signal (TRS) from the first TRP and the second TRP; generating a delay profile for channel estimation based at least in part on the TRS for physical downlink shared channel (PDSCH) demodulation; and receiving a PDSCH communication jointly transmitted from the first TRP and the second TRP based at least in part on the delay profile.

20. The method of claim 19, further comprising: measuring the PMI for joint transmission of a PDSCH from the first TRP and the second TRP based at least in part on the timing offset value, wherein the timing offset value indicates a received signal timing difference between the first TRP and the second TRP.

21. The method of claim 19, wherein receiving the TRS comprises: receiving a first TRS from the first TRP and a second TRS from the second TRP.

22. The method of claim 21, further comprising: receiving an indication of whether the first TRS or the second TRS is an anchor TRS, and wherein generating the delay profile comprises generating the delay profile further based at least in part on an average delay of the anchor TRS.

23. The method of claim 22, wherein the first TRS is the anchor TRS, and wherein the method further comprises: applying the average delay of the anchor TRS to a quasi co-location (QCL) reference of the second TRS.

24. The method of claim 19, wherein receiving the TRS comprises: receiving a single frequency network (SFN) TRS from the first TRP and the second TRP, and wherein generating the delay profile comprises generating the delay profile from the SFN TRS for demodulation of a PDSCH jointly transmitted from the first TRP and the second TRP.

25. A method of wireless communication performed by a network entity, the method comprising: transmitting a first channel state information reference signal (CSI-RS) from a first transmission reception point (TRP) and a second CSI-RS from a second TRP; receiving a timing offset value and a precoding matrix indicator (PMI); transmitting a tracking reference signal (TRS) from the first TRP and the second TRP; and jointly transmitting a physical downlink shared channel (PDSCH) communication from the first TRP and the second TRP based at least in part on the timing offset value and the PMI.

26. The method of claim 25, wherein transmitting the TRS comprises: transmitting a first tracking reference signal (TRS) from the first TRP and a second TRS from the second TRP, and wherein the method further comprises: transmitting an indication of whether the first TRS or the second TRS is an anchor TRS; and transmitting an indication of whether the first TRS or the second TRS is an anchor TRS; and transmit the PDSCH communication from the TRP associated with the non-anchor TRS after timing offset pre-compensation.

27. The method of claim 25, wherein transmitting the TRS comprises: transmit a single frequency network (SFN) TRS from the first TRS and the second TRP.

28. The method of claim 27, wherein transmitting the TRS and the PDSCH communication comprises: transmit the TRS and the PDSCH communication from the second TRP after timing offset pre-compensation.

29. The method of claim 28, further comprising: update the timing offset pre-compensation for the TRS transmitted from the second TRP at a next TRS occasion after receiving a new timing offset value from a user equipment based at least in part on the new timing offset value.

30. The method of claim 29, further comprising: update the timing offset pre-compensation for the PDSCH transmitted from the second TRP after transmission of the TRS at the next TRS occasion based at least in part on the new timing offset value.

Images