Doppler basis selection for multiple transmit-receive points

Abstract

Methods, systems, and devices for wireless communication are described. The method may include: receiving one or more reference signals from a set of a plurality of transmit-receive points; generating a coherent joint transmit precoding matrix indicator (PMI) associated with a set of the plurality of transmit-receive points based on receiving the one or more reference signals, wherein the coherent joint transmit PMI includes one or more Doppler domain components for each transmit-receive point in the set of the plurality of transmit-receive points; and transmitting a report including the indication of the coherent joint transmission PMI.

Description

Technical Field

[0001] The following discussion relates to wireless communication, including Doppler selection for multiple transmitting and receiving points. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses supporting Doppler selection for multiple transmit / receive points. For example, the described technology provides: receiving one or more reference signals from a set of multiple transmit / receive points; generating a coherent joint transmit pre-decoding matrix indicator (PMI) associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmit PMI may include one or more Doppler domain components for each of the multiple transmit / receive points in the set; and transmitting a report including an indication of the coherent joint transmit PMI.

[0004] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the memories. The one or more processors may be able to operate individually or jointly to execute the code, thereby enabling the UE to: receive one or more reference signals from a set of multiple transmit / receive points; generate a coherent joint transmission (PMI) associated with the set of multiple transmit / receive points based on the received reference signals, wherein the PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set; and transmit a report including an indication of the PMI.

[0005] Another UE for wireless communication is described. The UE may include: components for receiving one or more reference signals from a set of multiple transmit / receive points; components for generating a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set; and components for transmitting a report including an indication of the coherent joint transmission PMI.

[0006] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive one or more reference signals from a set of multiple transmit / receive points; generate a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set; and transmit a report including an instruction to the coherent joint transmission PMI.

[0007] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending a common Doppler selection for all transmit and receive points in the set of multiple transmit and receive points.

[0008] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending the Doppler offset value of each of the multiple transmit and receive points in the set.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Doppler offset value includes a non-oversampled Doppler offset value, and the number of samples of the non-oversampled Doppler offset value may be an integer value corresponding to the length of the Doppler basis.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Doppler offset value includes an oversampled Doppler offset value, and the number of samples of the oversampled Doppler offset value may be a multiple of the Doppler base length.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the number of Doppler offset values ​​for each of the multiple transmit and receive points in the set of multiple transmit and receive points may be less than the total number of transmit and receive points in the set of multiple transmit and receive points, and the number of Doppler offset values ​​represents the relative offset with respect to a reference transmit and receive point in the set of multiple transmit and receive points.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Doppler offset value for each of the multiple transmit and receive points in the set may be shared for both polarizations of one or more transmit antennas in the set of multiple transmit and receive points.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Doppler offset value of each of the multiple transmit and receive points in the set can be shared across all layers in the set of multiple layers associated with the PMI.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the Doppler offset value of each of the multiple transmit and receive points in the set of transmit and receive points may be layer-specific for the set of multiple layers associated with the PMI.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending an independent Doppler selection for each of the multiple transmit / receive points in the set.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending an oversampled group index for each of the multiple transmit / receive points in the set.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for the following actions: sending an oversampled group index that may be less than the total number of transmit / receive points in the set of multiple transmit / receive points, wherein the oversampled group index may be relative to an oversampled group index corresponding to a reference transmit / receive point in the set of multiple transmit / receive points.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the oversampling group index for each of the multiple transmit and receive points in the set may be shared for both polarizations of one or more transmit antennas of the multiple transmit and receive points in the set.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the independent Doppler selection for each of the multiple transmit / receive points in the set, the oversampling group index for each of the multiple transmit / receive points in the set, or both may be layer-specific for the set of multiple layers associated with the PMI.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for the following actions: sending a strongest coefficient indicator for each of a set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently co-transmitted PMI, wherein the strongest coefficient indicator may be defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the report may include operations, features, components, or instructions for the following actions: transmitting a strongest coefficient indicator for each of a set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator may be aligned with the zero Doppler basis associated with the one or more Doppler domain components.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for sending a non-zero coefficient bitmap, wherein the frequency domain components and time domain components associated with the non-zero coefficient bitmap may be reported as paired coefficients.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the report may include operations, features, components, or instructions for: transmitting a first-stage bitmap having a size that may be based on the number of sets of multiple transmit / receive points and the number of layers associated with the PMI; and transmitting a second-stage bitmap having non-zero coefficients for a component subset of the first-stage bitmap, the subset being indicated as non-zero by the first-stage bitmap.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more reference signals received from the set of multiple transmit and receive points may be configured using the same transmit periodicity, and the timing offset difference between the transmissions of the reference signals may be configured to be less than or equal to an offset threshold duration.

[0025] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more reference signals received from the set of multiple transmit and receive points may be configured using a transmit trigger having a trigger offset difference that may be less than or equal to a trigger threshold duration.

[0026] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the coherently co-transmitted PMI includes a Type II channel state information PMI.

[0027] A method for wireless communication by a network entity is described. The method may include: transmitting one or more reference signals to a UE; receiving a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points; and scheduling one or more resources for communicating with the UE based on the received report.

[0028] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code, thereby enabling the network entity to: transmit one or more reference signals to a UE; receive a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points; and schedule one or more resources for communicating with the UE based on the received report.

[0029] Another network entity for wireless communication is described. This network entity may include: components for transmitting one or more reference signals to a UE; components for receiving a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points; and components for scheduling one or more resources for communicating with the UE based on the received report.

[0030] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit one or more reference signals to a UE; receive a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points; and schedule one or more resources for communicating with the UE based on the received report.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving a common Doppler selection for all transmit and receive points in the set of multiple transmit and receive points.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving the Doppler offset value of each of the multiple transmit and receive points in the set.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Doppler offset includes a non-oversampled Doppler offset, and the number of samples of the non-oversampled Doppler offset can be an integer value corresponding to the length of the Doppler basis.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Doppler offset includes an oversampled Doppler offset, and the number of samples for the oversampled Doppler offset can be a multiple of the Doppler base length.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the number of Doppler offset values ​​for each of the multiple transmit and receive points in the set of multiple transmit and receive points may be less than the total number of transmit and receive points in the set of multiple transmit and receive points, and the number of Doppler offset values ​​represents the relative offset with respect to a reference transmit and receive point in the set of multiple transmit and receive points.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Doppler offset value for each of the multiple transmit and receive points in the set may be shared for both polarizations of one or more transmit antennas in the set of multiple transmit and receive points.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Doppler offset value of each of the multiple transmit and receive points in the set can be shared across all layers in the set of multiple layers associated with the PMI.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the Doppler offset value of each of the multiple transmit and receive points in the set of multiple transmit and receive points may be layer-specific for the set of multiple layers associated with the PMI.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving an independent Doppler selection for each of the multiple transmit / receive points in the set.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving an oversampled group index for each of the multiple transmit / receive points in the set.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving an oversampled group index that may be less than the total number of transmit / receive points in the set of multiple transmit / receive points, wherein the oversampled group index may be relative to an oversampled group index corresponding to a reference transmit / receive point in the set of multiple transmit / receive points.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the oversampling group index for each of the multiple transmit and receive points in the set may be shared for both polarizations of one or more transmit antennas of the multiple transmit and receive points in the set.

[0043] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the independent Doppler selection for each of the multiple transmit and receive points in the set, the oversampled group index for each of the multiple transmit and receive points in the set, or both may be layer-specific for the set of multiple layers associated with the PMI.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for the following actions: receiving a strongest coefficient indicator for each of a set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator may be defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0045] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for the following actions: receiving a strongest coefficient indicator for each of a set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator may be aligned with the zero Doppler basis associated with the one or more Doppler domain components.

[0046] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for receiving a non-zero coefficient bitmap, wherein the frequency domain components and time domain components associated with the non-zero coefficient bitmap may be reported as paired coefficients.

[0047] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for: receiving a first-stage bitmap having a size that may be based on the number of sets of multiple transmit / receive points and the number of layers associated with the PMI; and receiving a second-stage bitmap having non-zero coefficients for a component subset of the first-stage bitmap, the subset being indicated as non-zero by the first-stage bitmap.

[0048] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more reference signals may be configured using the same transmission periodicity, and the timing offset difference between the transmissions of the reference signals may be configured to be less than or equal to an offset threshold duration.

[0049] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more reference signals may be configured using a transmit trigger with a trigger offset difference that may be less than or equal to the duration of a trigger threshold.

[0050] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the coherent joint transmission PMI includes Type II channel state information PMI. Attached Figure Description

[0051] Figure 1 and Figure 2 An example of a wireless communication system supporting Doppler selection for multiple transmitting and receiving points is shown, according to one or more aspects of this disclosure.

[0052] Figure 3 An example of a process flow supporting Doppler selection for multiple transmitting and receiving points is shown, according to one or more aspects of this disclosure.

[0053] Figure 4 and Figure 5 A block diagram of a device supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown.

[0054] Figure 6 A block diagram is shown of a communication manager that supports Doppler selection for multiple transmitting and receiving points, according to one or more aspects of this disclosure.

[0055] Figure 7 A diagram of a system including a device supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown.

[0056] Figure 8 and Figure 9 A block diagram of a device supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown.

[0057] Figure 10 A block diagram is shown of a communication manager that supports Doppler selection for multiple transmitting and receiving points, according to one or more aspects of this disclosure.

[0058] Figure 11 A diagram of a system including a device supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown.

[0059] Figure 12 and Figure 13 A flowchart illustrating a method for supporting Doppler selection for multiple transmitting and receiving points according to one or more aspects of this disclosure is shown. Detailed Implementation

[0060] User equipment (UE) can establish communication with multiple TRPs (such as a first TRP and a second TRP) in a wireless communication system (e.g., a multiple transmit-receive-point (TRP) environment). Communication between the UE and TRPs may include reference signaling (e.g., Channel State Information Reference Signal (CSI-RS)) to support channel state information measurement and reporting. In the case of communication associated with multiple-input multiple-output (MIMO) transmission techniques, highly accurate CSI-RS can be beneficial for signal pre-decoding and other processes associated with communication between the TRPs and the UE. For example, the UE can measure one or more CSI-RS transmitted by the TRPs, use the measurement to determine the pre-decoding matrix associated with the codebook, and can transmit the associated pre-decoding matrix indicator (PMI) to these TRPs. However, in some examples, the UE may move relative to the TRPs. Therefore, one or more Doppler shifts may be associated with communication between the UE and the TRPs, which may affect the accuracy of the CSI-RS measurements and thus prevent the UE from transmitting accurate PMIs. Although various techniques have been employed to attempt to account for Doppler shift in communication between a mobile UE and a single TRP, these techniques may not be suitable for situations where the UE communicates with multiple TRPs and moves relative to those multiple TRPs.

[0061] To account for Doppler shifts in communication between the UE and multiple TRPs, the UE can determine the Doppler shift (or some other Doppler domain components) associated with each of these TRPs. It can utilize the determined Doppler shifts to generate one or more Doppler-based Component Interchanges (PMIs) and transmit these PMIs to one or more of these TRPs to improve future transmission effectiveness and efficiency. For example, the UE can receive one or more reference signals (e.g., CSI-RS) from a first TRP and from a second TRP. Based on the received reference signals, the UE can estimate aspects of the channel associated with the Doppler shifts (e.g., Doppler spread or other Doppler domain components) between the UE and each of these TRPs. For example, the UE can estimate a first Doppler shift associated with the first TRP based on the reference signal from the first TRP, and can estimate a second Doppler shift associated with the second TRP based on the reference signal from the second TRP. The UE can use these estimated Doppler shifts to determine a Doppler-based PMI and can send the PMI to one or more of these TRPs (or another network entity). In some examples, the UE can send a common Doppler base selection for all TRPs in these TRPs, while in other examples, the UE can send a TRP-specific Doppler base selection for each TRP. Additionally or alternatively, the UE can also send TRP-specific information (e.g., Doppler offset, group index) associated with the determined PMI.

[0062] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described by way of process flow. The aspects of this disclosure are further illustrated and described by way of device diagrams, system diagrams, and flowcharts relating to Doppler selection for multiple transmitting and receiving points.

[0063] Figure 1 An example of a wireless communication system 100 supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0064] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0065] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

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

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

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

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

[0070] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

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

[0072] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support per-TRP oversampled Doppler selection as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0074] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

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

[0076] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be made by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

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

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

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

[0080] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

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

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

[0083] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

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

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

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

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

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

[0089] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0090] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

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

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

[0093] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0094] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

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

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

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

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

[0099] UE 115 can establish communication with multiple TRPs 170 (such as a first TRP and a second TRP) in a wireless communication system (e.g., a multi-TRP environment). Communication between UE 115 and TRPs 170 may include reference signaling (e.g., CSI-RS), which can be used to support channel state information measurement and reporting. In cases where communication is associated with MIMO transmission techniques, highly accurate CSI-RS can be beneficial for signal pre-decoding and other processes associated with communication between TRPs 170 and UE 115. For example, UE 115 may measure one or more CSI-RS transmitted by TRPs 170, use this measurement to determine the pre-decoding matrix associated with the codebook, and may (e.g., via CSI reporting or similar signaling) transmit the associated PMI to TRPs 170. In some examples, UE 115 may be mobile relative to TRPs 170. Therefore, one or more Doppler frequency shifts can be associated with communication between UE 115 and TRP 170, which may affect the accuracy of CSI-RS measurements and thus prevent UE 115 from determining and reporting an accurate PMI. While various techniques have been employed to account for Doppler frequency shifts in communication between a mobile UE and a single TRP, these techniques may not be suitable for situations where the UE communicates with multiple TRPs and moves relative to those TRPs. Furthermore, existing techniques may not account for hardware variations at the TRPs (e.g., oscillator drift variations), which can cause relative frequency drift between TRPs.

[0100] To account for Doppler frequency shift (and / or hardware variations between TRPs) in communication between UE 115 and multiple TRPs 170, UE 115 may determine the Doppler-based components (e.g., Doppler basis selection, Doppler offset, etc.) associated with each TRP in TRP 170. These determined Doppler-based components may be used to generate one or more Doppler-based multi-TRP PMIs, and these PMIs may be transmitted to one or more TRPs in TRP 170 (e.g., via uplink reporting, such as CSI reporting). For example, UE 115 may receive and measure one or more reference signals (e.g., CSI-RS) from (e.g., a first TRP and a second TRP in TRP 170). Based on the received reference signals, UE 115 may estimate aspects of the channel between UE 115 and each TRP in TRP 170, including the Doppler-based components of the channel and the relative Doppler difference between TRPs 170. UE 115 may utilize these estimated Doppler-based components to determine a Doppler-based PMI, which takes into account the Doppler components of the channel for each TRP 170. UE 115 may report a TRP-specific Doppler domain to network entities (e.g., one or more TRPs in TRP 170) via CSI reporting. In some examples, UE 115 may report a common Doppler base selection for all TRPs 170. Additionally or alternatively, UE 115 may report a TRP-specific Doppler base selection for each TRP 170. In addition to the Doppler base selection, UE 115 may also report one or more Doppler offsets (which may be oversampled or non-oversampled Doppler offsets).

[0101] Figure 2 An example of a wireless communication system 200 supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include UE 115-a, TRP 170-a, and TRP 170-b, which may be as described in reference... Figure 1 Examples of the corresponding devices described.

[0102] Wireless communication system 200 may be associated with Doppler-based effects such as Doppler shift, Doppler spread, etc. For example, UE 115-a may communicate with both TRP 170-a and TRP 170-b (and / or an additional TRP not shown) while moving at a speed relative to TRP 170, which may result in Doppler effects on communication between UE 115-a and TRP 170. In some examples (e.g., when UE 115-a moves at a speed relative to TRP 170-a different from its speed relative to TRP 170-b), the Doppler effect on communication between UE 115-a and TRP 170-a may differ from the Doppler effect on communication between UE 115-a and TRP 170-b. In some examples, the Doppler effect on communication may lead to degraded, inaccurate, or inefficient communication between UE 115-a and TRP 170.

[0103] Some techniques for considering the Doppler effect in communication between a single TRP 170 and UE 115 may include a pre-decoder matrix using Doppler notification. For example, to consider the Doppler effect in communication between a single TRP 170 and UE 115, UE 115 may provide feedback for beam selection in the form of PMI or codebook-based feedback (e.g., a Doppler codebook for a single TRP). For example, UE 115 may measure CSI-RS (or other reference signaling) over a period of time and may use these measurements to prepare a pre-decoder matrix that considers the selected spatial domain (SD) basis, the selected frequency domain (FD) basis, and the coefficient matrix. To consider the velocity of UE 115, the UE may use the measured CSI-RS information over a period of time to predict (e.g., extrapolate) the future pre-decoder. UE 115 may compress the extrapolated coefficient matrix into the Doppler domain (e.g., localize it in time and frequency), while one or more matrices in the remaining matrix may be assumed to be constant over time. Therefore, UE 115 can report a PMI that takes into account the Doppler effect of the channel for a single TRP 170. While these techniques may be useful in considering the Doppler effect in communication between a single TRP and a mobile UE, they may not be suitable for situations involving multiple TRPs.

[0104] In cases where the UE 115 is static (e.g., at speeds below a certain configured threshold) and communicating with multiple TRPs, several other codebook techniques can be used. For example, the UE 115 can measure CSI-RS (or other reference signaling) and use these measurements to generate one or more joint codebooks that take into account the channel measurements associated with the multiple TRPs. However, such joint codebooks may not be suitable for cases where the UE 115 is moving relative to the TRP 170 (e.g., above a certain configured speed threshold) because these techniques may not account for the Doppler effect in communication between the UE 115 and multiple TRPs 170.

[0105] The Doppler effect associated with the wireless communication system 200 may be caused by one or more sources. For example, the Doppler effect may be associated with the movement of UE 115-a relative to TRP 170-a and TRP 170-b. UE 115-a may be associated with a first velocity along the dominant propagation path of TRP 170-a (e.g., the dominant transmission path between UE 115-a and TRP 170-a), and UE 115-a may be associated with a second velocity along the dominant propagation path of TRP 170-b. These two velocities of UE 115-a (e.g., relative to TRP 170) may result in a separate Doppler shift (e.g., per-TRP Doppler difference, relative Doppler difference) for each TRP in TRP 170. Additionally or alternatively, the Doppler shift may be associated with or caused by a frequency drift in one or both TRPs of TRP 170, specifically by an oscillator (referred to herein as "XO") within those TRPs. Thus, TRP 170-a may be associated with a first frequency drift relative to UE 115-a, and TRP 170-b may be associated with a second frequency drift relative to UE 115-a. These two frequency drifts of TRP 170 may result in a separate Doppler shift of TRP 170 relative to UE 115-a. Therefore, it may be beneficial to allow TRP 170 and UE 115-a to account for Doppler shifts (e.g., over time) associated with or caused by movements of UE 115-a relative to more than one of the TRPs in TRP 170 (e.g., to increase the accuracy of channel state information compression in the time domain).

[0106] To accurately account for the Doppler effect in communication, the wireless communication system 200 may consider the velocity of UE 115-a relative to each TRP in TRP 170, as well as the XO drift of TRP 170-a and TRP 170-b. For example, the XO drift of TRP 170-a, the XO drift of TRP 170-b, and the velocity of UE 115-a relative to TRP 170 may result in a linear phase ramp Doppler shift over time, where the XO drift of TRP 170 can be illustrated by an exponential function, and the velocity of UE 115-a can be illustrated as a function of the velocity along the propagation path between UE 115-a and TRP 170-a and between UE 115-a and TRP 170-b. The wireless communication system 200 may also consider the frequency domain, time domain, transmitted data, and attenuation coefficients (e.g., along with XO drift and the relative velocity of UE 115-a) associated with the path between UE 115-a and TRP 170. In some examples, the difference in XO drift of each TRP in TRP 170 may result in a first Doppler drift associated with the propagation path between UE 115-a and TRP 170-a, and a second Doppler drift associated with the propagation path between UE 115-a and TRP 170-b (e.g., TRP-specific Doppler drift). In other examples, the Doppler drift associated with the propagation path between UE 115-a and TRP 170-a and the Doppler drift associated with the propagation path between UE 115-a and TRP 170-b may be the same.

[0107] According to various aspects of this disclosure, UE 115-a may report channel state information (e.g., eType II CJT CSI) to the network entity of wireless communication system 200, including a TRP-specific Doppler domain (e.g., also referred to as a time domain) basis. For example, UE 115-a may report a common Doppler base selection 205 for all TRPs 170. UE 115-a may report the common Doppler base selection 205 via a bit set according to the following equation: in Let represent the Doppler length, and Q represent the total. The selected number of bases in the set. In some examples, base 0 can always be selected.

[0108] UE 115-a may also report one or more Doppler offsets (e.g., as part of a CSI report or separately). In some cases, UE 115-a may report TRP-specific non-oversampled Doppler offsets. (For example, TRP-specific non-oversampled Doppler offset 220, TRP-specific non-oversampled Doppler offset 225). As mentioned herein, specific TRP n The non-oversampled Doppler shift can be expressed as (For example, as an integer), where It is the Doppler length. UE115-a can be accessed via... Individual reports show non-oversampled Doppler offsets of 220 and 225.

[0109] In some cases, UE 115-a can report TRP-specific oversampled Doppler offset. (For example, TRP-specific oversampled Doppler offset 230, TRP-specific oversampled Doppler offset 235). As mentioned in this article, specific TRP n The oversampled Doppler shift can be expressed as (e.g., fractions), where Indicates the Doppler domain oversampling factor (e.g., =4). UE 115-a can be accessed via Individual reports show oversampling Doppler offsets of 230 and 235.

[0110] In either case of reporting a TRP-specific non-oversampled Doppler offset or a TRP-specific oversampled Doppler offset, UE 115-a may report fewer Doppler offsets than the Doppler offset of TRP 170. For example, UE 115-a may report a total of N-1 Doppler offsets, where N represents the total number of TRPs 170 associated with the report. In such cases, one TRP of TRP 170 may be considered as a reference TRP 170 (e.g., the first TRP on a default number or some other configuration), and the Doppler offset of that reference TRP may be assumed to be zero, and other Doppler offsets may be reported and / or interpreted relative to that reference TRP.

[0111] In some examples, UE 115-a may report TRP-specific Doppler selections (e.g., TRP-specific Doppler selection 210, TRP-specific Doppler selection 215). In such examples, the TRP-specific Doppler selection is a completely independent selection for each TRP 170. Similar to the shared Doppler selection example, when reporting TRP-specific Doppler selections, UE 115 may also report TRP-specific non-oversampled Doppler offsets or TRP-specific oversampled Doppler offsets. In such cases, the reported Doppler offset can be interpreted as an offset between the strongest local Doppler bases for each TRP.

[0112] In addition to reporting TRP-specific Doppler base selection, UE 115-a can also report TRP-specific Doppler oversampling group index. (For example, TRP-specific Doppler oversampling group index 240, TRP-specific Doppler oversampling group index 245). For a specific TRP n TRP Specific Doppler Oversampling Group Index It can be represented as And can be accessed via The UE 115-a may report fewer Doppler oversampled group indices than the number of TRPs. For example, the UE 115-a may report a total of N-1 Doppler oversampled group indices, where N is the total number of TRPs 170 associated with the report. In such cases, one of the TRPs 170 can be considered as a reference TRP, and the TRP-specific oversampled group index of that reference TRP can be assumed to be... .

[0113] In some examples, the TRP-specific Doppler offset for each TRP 170, the TRP-specific oversampled group index for each TRP 170, or both may be reported as polarization-shared. For example, the TRP-specific Doppler offset reported for each TRP 170 (e.g., non-oversampled Doppler offset 220, non-oversampled Doppler offset 225, oversampled Doppler offset 230, oversampled Doppler offset 235) or the TRP-specific oversampled group index reported for each TRP (e.g., TRP-specific Doppler oversampled group index 240, TRP-specific Doppler oversampled group index 245) may be shared for both polarizations of one or more transmit antennas of each TRP in TRP 170.

[0114] In some examples, the TRP-specific Doppler offset reported using shared Doppler base selection can be layer-shared or layer-specific. If UE 115-a is a MIMO device, UE 115-a can transmit communications via more than one layer. In some examples, the TRP-specific Doppler offset (e.g., non-oversampled Doppler offset 220, non-oversampled Doppler offset 225, oversampled Doppler offset 230, oversampled Doppler offset 235) can be shared across all layers associated with the PMI transmitted by UE 115-a. If the Doppler offset is layer-shared, UE 115-a can perform TRP-specific time-domain phase rotation on the measurement channel matrix associated with each TRP in TRP 170 before implementing one or more matrix factorization techniques (e.g., singular value decomposition (SVD), eigenvalue decomposition (EVD)).

[0115] In some examples, one or more TRP-specific Doppler offsets (e.g., non-oversampled Doppler offset 220, non-oversampled Doppler offset 225, oversampled Doppler offset 230, oversampled Doppler offset 235) may be specific to each layer associated with the PMI transmitted by UE 115-a. Where the Doppler offset is layer-specific, UE 115-a may implement TRP-specific time-domain phase rotation for the pre-decoder associated with each TRP in TRP 170 after implementing one or more matrix factorization techniques (e.g., SVD, EVD).

[0116] In some examples, when reporting TRP-specific Doppler selection, UE 115-a may perform Doppler selection after implementing one or more matrix factorization techniques (e.g., SVD, EVD).

[0117] In some examples, when reporting a TRP-specific Doppler base selection, the TRP-specific Doppler oversampling group index can be layer-specific. For example, the TRP-specific Doppler oversampling group index selected by UE 115-a (e.g., TRP-specific Doppler oversampling group index 240, TRP-specific Doppler oversampling group index 245) can be specific to a single layer associated with the PMI sent by UE 115-a. When the TRP-specific Doppler oversampling group index is layer-specific, UE 115-a can select the TRP-specific Doppler oversampling group index value after implementing one or more matrix factorization techniques (e.g., SVD, EVD). In some examples, UE 115-a can utilize the TRP 170 associated with the TRP-specific Doppler oversampling group index used for all layers. The reference TRP is the same as the TRP, however UE 115-a may not report the reference TRP.

[0118] In some examples, UE 115-a may also report the strongest coefficient indicator (SCI) associated with the identified Doppler component. For example, UE 115-a may define the SCI across all selected Doppler bases (e.g., TRP-specific bases, common Doppler bases) for each layer, and may report the SCI based on the following payloads: Where L n This indicates that for each TRP n The number of selected beams (e.g., SD bases), where Q represents the number of selected Doppler bases. In some other examples, UE 115-a may align the SCI with a reference Doppler base (e.g., Doppler base 0) and may report the SCI based on the following payload: UE 115-a can take various actions to reduce the size of the non-zero coefficient (NZC) bitmap associated with CSI reports to reduce overhead and improve the efficiency and throughput of the wireless communication system 200. In some examples, UE 115-b can reduce the dimensions associated with the NZC bitmap (e.g., spatial dimension, frequency dimension, time dimension, or Doppler dimension). For example, for each layer, the FD and TD paired (e.g., delay-Doppler paired) bitmap is based on which NZC bitmap is additionally associated with the path selection bits in the SD. Figure 1 The reported results are obtained from this. In some cases, the FD and TD paired (e.g., delayed-Doppler paired) bitmaps are shared by the TRP, resulting in a bitmap size based on M*Q, where Q is the selected number of Doppler bases and M is the selected number of FD bases. The size of the baseline 3D bitmap can be determined according to... To determine, (where L) n This indicates the number of beams (e.g., SD-based) selected for each TRP-n. However, the reduced NZC bitmap size based on FD and TD pairing (e.g., delay-Doppler pairing) can be determined according to... + To determine (where) This can represent the percentage of non-zero FD and TD pairings (e.g., delay-Doppler pairings), which can be configured by control signaling such as RRC. Therefore, UE 115-a can maintain... (For example, making) This reduces the size of the NZC bitmap.

[0119] In some other cases, FD and TD pairing (e.g., delayed-Doppler pairing) bitmaps may be used and reported as TRP-specific. The size of the FD and TD pairing (e.g., delayed-Doppler pairing) bitmap can be determined according to... The unit is determined by N, where N represents the number of TRPs, NMQ represents the size of the bitmap for FD and TD pairings (e.g., delay-Doppler pairings), and where This indicates the size of the path selection bitmap in SD.

[0120] Additionally or alternatively, UE 115-a can achieve TRP / layer size reduction by reporting a subset of the NZC bitmap based on the first-stage bitmap. For example, UE 115-a can report a first-stage bitmap representing a block-by-block coefficient bitmap of size based on N* rank, where layers with TRPs having relatively small coefficients (e.g., close to 0 by a certain threshold amount) are reported as 0 values, and layers with larger coefficients are reported as 1 values. In such schemes, the subsequently transmitted NZC bitmap is reported only for layers / TRPs that report "1" in the first-stage bitmap, thereby reducing the overhead associated with sending NZC bitmap values ​​for layers / TRPs that report "0" in the first-stage bitmap. In some examples, the NZC bitmap size reduction techniques described herein can be combined, such as implementing a two-stage bitmap planned for TRP / layer reduction and FD and TD paired (e.g., delay-Doppler paired) bitmaps.

[0121] Reference signaling (e.g., CSI-RS) sent by TRP 170 can be configured in a coordinated manner such that UE 115-a measures CSI-RS sent simultaneously or close in time. For example, periodic CSI-RS (P-CSI-RS) and semi-persistent CSI-RS (SP-CSI-RS) associated with UE 115-a and TRP 170 can be configured using the same periodicity. Additionally or alternatively, P-CSI-RS and SP-CSI-RS can be associated with a timing offset having a difference of no more than a threshold duration (e.g., 2 consecutive time slots). In some examples, aperiodic CSI-RS (AP-CSI-RS) bursts associated with UE 115-a and TRP 170 can be configured using a trigger offset characterized by a difference of no more than a threshold duration (e.g., 2 consecutive time slots).

[0122] Figure 3 An example of a process flow 300 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure is shown. Process flow 300 may include UE 115-b, TRP 170-c, and TRP 170-d, which may be references Figure 1 and Figure 2 Examples of the corresponding devices described are provided. Although only two TRP 170s are shown, it should be understood that the techniques described herein can be applied to additional TRP 170s. The following alternative examples can be implemented, some of which involve steps performed in a different order than those described, or not performed at all. In some examples, steps may include additional features not mentioned below, or additional steps may be added.

[0123] At 305, UE 115-b may receive one or more reference signals transmitted by TRP 170-d and / or one or more reference signals transmitted by TRP 170-c. The reference signal may be an example of a CSI-RS. The reference signal may be configured as a periodic CSI-RS (P-CSI-RS) or a semi-persistent CSI-RS (SP-CSI-RS) and may be associated with the same periodicity, and may be configured using a timing offset difference (e.g., between transmissions of each reference signal in the reference signals) with a duration less than or equal to a threshold time. In some examples, one or more of the reference signals may be configured as an aperiodic CSI-RS (AP-CSI-RS) and may include a transmission trigger associated with a trigger offset difference less than or equal to a trigger threshold.

[0124] At 310, UE 115-b may generate one or more coherently co-transmitted PMIs associated with TRP 170-c and TRP 170-d. For example, based on the one or more reference signals received from TRP 170-c and TRP 170-d, UE 115-b may generate one or more PMIs, which may include one or more Doppler domain (e.g., Doppler-based) components for both TRP 170-c and TRP 170-d. In some examples, UE 115-b may report a common Doppler base selection associated with both of TRP 170-c (or, if more than two TRPs are included), while in other examples, UE 115-b may report a TRP-specific (e.g., independent Doppler base selection) selection for each of TRP 170-c and TRP 170-d, as per the reference signal. Figure 2 Further description. In some examples, one or more PMIs may include a Type II CSI PMI.

[0125] At 315, UE 115-b may send the one or more PMIs to the network (e.g., one or more network entities, such as one or both of TRP 170-c and TRP170-d). For example, UE 115-b may send a report to TRP 170 including the generated PMI (e.g., a coherently co-transmitted PMI). In some examples, UE 115-b may send a report including a common Doppler base selection for TRP 170 (e.g., the same Doppler base for both TRPs 170). In some examples, the report sent by UE 115-b may also include Doppler offset values ​​for one or more TRPs in TRP 170. Each Doppler offset value may be an example of an oversampled Doppler offset value or a non-oversampled Doppler offset value, and each Doppler offset value may be associated with the length of the common Doppler base. For example, oversampled Doppler offset values ​​can be associated with a multiple of the length of the shared Doppler base, while non-oversampled Doppler offset values ​​can be associated with an integer value of the length of the shared Doppler base. UE 115-b can transmit a total of N-1 Doppler offset values, where N is the total number of TRPs 170, and the number of transmitted Doppler offset values ​​can represent the relative Doppler offset with respect to a reference TRP in the TRP 170. Each transmitted Doppler offset can also be shared with respect to the two polarizations of the transmit antenna of the associated TRP 170. Each transmitted Doppler offset can additionally be shared with all layers associated with the transmission of the PMI, or can be specific to each layer among the layers associated with the transmission of the PMI.

[0126] In some examples, UE 115-b may send a report to TRP 170 that includes an independent Doppler selection (e.g., a TRP-specific Doppler selection) for each TRP in TRP 170. In some examples, the report sent by UE 115-b may also include an oversampled group index for each TRP in TRP 170. UE 115-b may send a total of N-1 oversampled group indices, where N is the total number of TRPs 170, and the sent oversampled group indices may be relative to a reference oversampled group index associated with one of the TRPs in TRP 170. Each sent oversampled group index may also be shared for both polarizations of the transmit antenna of the associated TRP 170. Each sent TRP-specific Doppler selection and each oversampled group index may be specific to each layer in the layer associated with the transmission of PMI.

[0127] In some examples, the report sent by UE 115-b to TRP 170 may include a SCI. This SCI may (e.g., to TRP 170) indicate the strongest coefficient, which may correspond to a coefficient matrix associated with the sent PMI. In some examples, the SCI may be defined across each of a selected Doppler base (e.g., a shared Doppler base, one or more TRP-specific Doppler bases) associated with one or more Doppler offset values ​​or oversampled group indices. In some examples, the SCI may be aligned with a reference (e.g., zero) Doppler base associated with the one or more Doppler offset values ​​or the oversampled group index.

[0128] In some examples, the report transmitted by UE 115-b may also include one or more bitmaps. For example, a report transmitted by UE 115-b to TRP 170 may include a non-zero coefficient bitmap. The non-zero coefficient bitmap may be associated with frequency domain components and time domain components, which may be reported by UE 115-b as delay-Doppler pairs. In some examples, transmitting the report may include UE 115-b transmitting a first-stage bitmap, which may be characterized by the magnitude of the number of TRP 170 and the number of layers associated with the PMI. UE 115-b may also transmit a second-stage bitmap, which may be characterized by one or more non-zero coefficients associated with a non-zero subset of the indications of the components of the first-stage bitmap.

[0129] At 320, one or both of the TRPs 170 can schedule one or more resources for communication with UE 115-b. For example, in response to receiving one or more PMIs sent from UE 115-b, TRP 170 can schedule various PDSCH resources based on the received PMIs. At 325, TRP 170 can send and UE 115-b can receive PDSCH resources.

[0130] Figure 4 A block diagram 400 illustrates a device 405 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0131] Receiver 410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Doppler selection for multiple transmit and receive points). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0132] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Doppler selection for multiple transmit and receive points). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0133] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0134] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0135] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0136] In some examples, the communication manager 420 may be configured to use or otherwise cooperate with the receiver 410, transmitter 415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or be integrated in combination with the receiver 410, transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0137] The communication manager 420 may support wireless communication according to examples disclosed herein. For example, the communication manager 420 may be capable of, configured to, or operable to support components for receiving one or more reference signals from a set of multiple transmit / receive points. The communication manager 420 may be capable of, configured to, or operable to support components for generating a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set. The communication manager 420 may be capable of, configured to, or operable to support components for transmitting a report including an indication of the coherent joint transmission PMI.

[0138] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing and utilizing communication resources more efficiently.

[0139] Figure 5A block diagram 500 of a device 505 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, transmitter 515, and communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Doppler selection for multiple transmit and receive points). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0141] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with Doppler selection for multiple transmit and receive points). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0142] Device 505 or its various components may be examples of parts for performing various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, communication manager 520 may include reference signaling manager 525, PMI manager 530, reporting manager 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use or otherwise cooperate with receiver 510, transmitter 515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0143] Communication manager 520 may support wireless communication according to examples disclosed herein. Reference signaling manager 525 is capable of, configured to, or operable to support components for receiving one or more reference signals from a set of multiple transmit / receive points. PMI manager 530 is capable of, configured to, or operable to support components for generating a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set. Report manager 535 is capable of, configured to, or operable to support components for transmitting a report including an indication of the coherent joint transmission PMI.

[0144] Figure 6 A block diagram 600 is shown of a communication manager 620 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, the communication manager 620 may include a reference signaling manager 625, a PMI manager 630, a report manager 635, a shared Doppler selection manager 640, an independent Doppler selection manager 645, a strongest coefficient indicator manager 650, a bitmap manager 655, a Doppler offset value manager 660, an oversampling group index manager 665, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0145] Communication manager 620 may support wireless communication according to examples disclosed herein. Reference signaling manager 625 is capable of, configured to, or operable to support components for receiving one or more reference signals from a set of multiple transmit / receive points. PMI manager 630 is capable of, configured to, or operable to support components for generating a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set. Report manager 635 is capable of, configured to, or operable to support components for transmitting a report including an indication of the coherent joint transmission PMI.

[0146] In some examples, to support the sending of this report, the common Doppler selection manager 640 is capable of, configured to, or able to operate to support components for sending common Doppler selections for all sender / receiver points in the set of multiple sender / receiver points.

[0147] In some examples, to support the sending of this report, the Doppler offset value manager 660 is capable of, configured to, or able to operate to support components for sending the Doppler offset values ​​of each of the multiple transmit and receive points in the set.

[0148] In some examples, the Doppler offset includes a non-oversampled Doppler offset. In some examples, the number of samples for the non-oversampled Doppler offset is an integer value corresponding to the Doppler basis length.

[0149] In some examples, the Doppler offset includes an oversampled Doppler offset. In some examples, the number of samples in the oversampled Doppler offset is a multiple of the Doppler basis length.

[0150] In some examples, the number of Doppler offset values ​​for each of the multiple transmitters and receivers in the set is less than the total number of transmitters and receivers in the set. In some examples, the number of Doppler offset values ​​represents the relative offset with respect to a reference transmitter or receiver in the set of multiple transmitters and receivers.

[0151] In some examples, the Doppler offset value for each of the multiple transmit and receive points in the set is shared for both polarizations of one or more transmit antennas in the set of multiple transmit and receive points.

[0152] In some examples, the Doppler offset value of each of the multiple transmit and receive points in the set is shared across all layers in the set of multiple layers associated with the PMI.

[0153] In some examples, the Doppler offset value for each of the multiple transmit and receive points in the set is layer-specific for the set of multiple layers associated with the PMI.

[0154] In some examples, to support the sending of the report, the Independent Doppler Selection Manager 645 is capable of, configured to, or operable to support components for sending independent Doppler selections for each of the multiple sender / receiver points in the set.

[0155] In some examples, to support the sending of this report, the oversampled group index manager 665 is capable of, configured to, or able to operate to support components for sending an oversampled group index for each of the multiple sender and receiver points in the set.

[0156] In some examples, to support the sending of the report, the oversampled group index manager 665 is capable of, configured to, or operable to support components for sending a number of oversampled group indices less than the total number of send / receive points in the set of multiple send / receive points, wherein the oversampled group index is relative to an oversampled group index corresponding to a reference send / receive point in the set of multiple send / receive points.

[0157] In some examples, the oversampling group index for each of the multiple transmit / receive points in the set is shared for both polarizations of one or more transmit antennas in the set of multiple transmit / receive points.

[0158] In some examples, the independent Doppler selection for each of the multiple transmit / receive points in the set, the oversampling group index for each of the multiple transmit / receive points in the set, or both are layer-specific for the set of multiple layers associated with the PMI.

[0159] In some examples, to support the transmission of the report, the strongest coefficient indicator manager 650 is capable of, configured to, or operable to support components for transmitting a strongest coefficient indicator for each of the set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator is defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0160] In some examples, to support the transmission of the report, the strongest coefficient indicator manager 650 is capable of, configured to, or operable to support components for transmitting a strongest coefficient indicator for each of the set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently co-transmitted PMI, wherein the strongest coefficient indicator is aligned with the zero Doppler base associated with the one or more Doppler domain components.

[0161] In some examples, to support the sending of this report, the bitmap manager 655 is able to be configured or operated to support components for sending a non-zero coefficient bitmap, wherein the frequency domain components and time domain components associated with the non-zero coefficient bitmap are reported as paired coefficients.

[0162] In some examples, to support the transmission of the report, bitmap manager 655 is capable of, configured to, or operable to support components for transmitting a first-stage bitmap having a size based on the number of sets of multiple transmit / receive points and the number of layers associated with the PMI. In some examples, to support the transmission of the report, bitmap manager 655 is capable of, configured to, or operable to support components for transmitting a second-stage bitmap having non-zero coefficients for a subset of the components of the first-stage bitmap, the subset being indicated as non-zero by the first-stage bitmap.

[0163] In some examples, the one or more reference signals received from this set of multiple transmit and receive points are configured using the same transmission periodicity. In some examples, the timing offset difference between reference signal transmissions is configured to be less than or equal to an offset threshold duration.

[0164] In some examples, the one or more reference signals received from the set of multiple transmit and receive points are configured using a transmit trigger with a trigger offset difference less than or equal to the duration of a trigger threshold.

[0165] In some examples, the coherently co-transmitted PMI includes a Type II channel state information PMI.

[0166] Figure 7 A diagram of a system 700 including device 705 supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0167] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0168] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725, wired or wireless links, as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0169] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may also include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0170] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., supporting various functions or tasks for Doppler selection of multiple transmit and receive points). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 730 or otherwise.

[0171] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving one or more reference signals from a set of multiple transmit / receive points. The communication manager 720 may be capable of, configured to, or operable to support components for generating a coherent joint transmission PMI associated with the set of multiple transmit / receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit / receive points in the set. The communication manager 720 may be capable of, configured to, or operable to support components for transmitting a report including an indication of the coherent joint transmission PMI.

[0172] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improving communication reliability, reducing latency, improving and reducing processing-related user experience, utilizing communication resources more efficiently, and improving coordination between devices.

[0173] In some examples, the communication manager 720 may be configured to use or otherwise coordinate with the transceiver 715, one or more antennas 725, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause the device 705 to perform various aspects of Doppler selection for multiple transmit and receive points as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0174] Figure 8 A block diagram 800 of a device 805 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0177] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0178] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0179] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described herein).

[0180] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with the receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with the receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0181] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for transmitting one or more reference signals to the UE. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit and receive points. The communication manager 820 may be capable of, configured to, or operable to support components for scheduling one or more resources for communicating with the UE based on the received report.

[0182] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing and utilizing communication resources more efficiently.

[0183] Figure 9 A block diagram 900 illustrates a device 905 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0186] Device 905 or its various components may be examples of parts used to perform various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, communication manager 920 may include reference signaling manager 925, PMI indicator 930, downlink resource manager 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0187] Communication Manager 920 may support wireless communication according to examples disclosed herein. Reference Signaling Manager 925 is capable of, configured to, or operable to support components for transmitting one or more reference signals to the UE. PMI Indicator 930 is capable of, configured to, or operable to support components for receiving a report including an indication of a coherently coupled transmission PMI, wherein the coherently coupled transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points. Downlink Resource Manager 935 is capable of, configured to, or operable to support components for scheduling one or more resources for communicating with the UE based on the received report.

[0188] Figure 10A block diagram 1000 of a communication manager 1020 supporting Doppler selection for multiple transmit and receive points according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of Doppler selection for multiple transmit and receive points as described herein. For example, the communication manager 1020 may include a reference signaling manager 1025, a PMI indicator 1030, a downlink resource manager 1035, a shared Doppler selection manager 1040, an independent Doppler selection manager 1045, a strongest coefficient indicator manager 1050, a bitmap manager 1055, a Doppler offset value manager 1060, an oversampling group index manager 1065, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0189] Communication Manager 1020 may support wireless communication according to examples disclosed herein. Reference Signaling Manager 1025 is capable of, configured to, or operable to support components for transmitting one or more reference signals to the UE. PMI Indicator 1030 is capable of, configured to, or operable to support components for receiving a report including an indication of a coherently coupled transmission PMI, wherein the coherently coupled transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit / receive points. Downlink Resource Manager 1035 is capable of, configured to, or operable to support components for scheduling one or more resources for communicating with the UE based on the received report.

[0190] In some examples, to support receiving the report, the common Doppler selection manager 1040 is capable of being configured or operated to support components for receiving common Doppler selections for all transmit / receive points in the set of multiple transmit / receive points.

[0191] In some examples, to support receiving the report, the Doppler offset value manager 1060 is capable of being configured or operated to support components for receiving the Doppler offset values ​​of each of the multiple transmit / receive points in the set.

[0192] In some examples, the Doppler offset includes a non-oversampled Doppler offset. In some examples, the number of samples for the non-oversampled Doppler offset is an integer value corresponding to the Doppler basis length.

[0193] In some examples, the Doppler offset includes an oversampled Doppler offset. In some examples, the number of samples in the oversampled Doppler offset is a multiple of the Doppler basis length.

[0194] In some examples, the number of Doppler offset values ​​for each of the multiple transmitters and receivers in the set is less than the total number of transmitters and receivers in the set. In some examples, the number of Doppler offset values ​​represents the relative offset with respect to a reference transmitter or receiver in the set of multiple transmitters and receivers.

[0195] In some examples, the Doppler offset value for each of the multiple transmit and receive points in the set is shared for both polarizations of one or more transmit antennas in the set of multiple transmit and receive points.

[0196] In some examples, the Doppler offset value of each of the multiple transmit and receive points in the set is shared across all layers in the set of multiple layers associated with the PMI.

[0197] In some examples, the Doppler offset value for each of the multiple transmit and receive points in the set is layer-specific for the set of multiple layers associated with the PMI.

[0198] In some examples, to support receiving the report, the Independent Doppler Selection Manager 1045 is capable of being configured or operated to support components for receiving independent Doppler selections for each of the multiple transmit / receive points in the set.

[0199] In some examples, to support receiving the report, the oversampling group index manager 1065 is capable of, configured to, or able to operate to support components for receiving the oversampling group index for each of the multiple transmit / receive points in the set.

[0200] In some examples, to support receiving the report, the oversampled group index manager 1065 is capable of, configured to, or operable to support components for receiving a number of oversampled group indices less than the total number of transmit / receive points in the set of multiple transmit / receive points, wherein the oversampled group index is relative to an oversampled group index corresponding to a reference transmit / receive point in the set of multiple transmit / receive points.

[0201] In some examples, the oversampling group index for each of the multiple transmit / receive points in the set is shared for both polarizations of one or more transmit antennas in the set of multiple transmit / receive points.

[0202] In some examples, the independent Doppler selection for each of the multiple transmit / receive points in the set, the oversampling group index for each of the multiple transmit / receive points in the set, or both are layer-specific for the set of multiple layers associated with the PMI.

[0203] In some examples, to support receiving the report, the strongest coefficient indicator manager 1050 is capable of, configured to, or operable to support components for receiving the strongest coefficient indicator for each of the set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator is defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0204] In some examples, to support receiving the report, the strongest coefficient indicator manager 1050 is capable of, configured to, or operable to support components for receiving the strongest coefficient indicator for each of the set of multiple layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator is aligned with the zero Doppler basis associated with the one or more Doppler domain components.

[0205] In some examples, in order to support receiving the report, the bitmap manager 1055 is able to be configured or operated to support components for receiving a non-zero coefficient bitmap, wherein the frequency domain components and time domain components associated with the non-zero coefficient bitmap are reported as paired coefficients.

[0206] In some examples, to support receiving the report, the bitmap manager 1055 is capable of, configured to, or operable to support components for receiving a first-stage bitmap having a size based on the number of sets of multiple transmit / receive points and the number of layers associated with the PMI. In some examples, to support receiving the report, the bitmap manager 1055 is capable of, configured to, or operable to support components for receiving a second-stage bitmap having non-zero coefficients for a subset of the components of the first-stage bitmap, the subset being indicated as non-zero by the first-stage bitmap.

[0207] In some examples, the one or more reference signals are configured using the same transmission periodicity. In some examples, the timing offset difference between reference signal transmissions is configured to be less than or equal to an offset threshold duration.

[0208] In some examples, the one or more reference signals are configured using a send trigger with a trigger offset difference that is less than or equal to the duration of the trigger threshold.

[0209] In some examples, the coherently co-transmitted PMI includes a Type II channel state information PMI.

[0210] Figure 11 A diagram of a system 1100 including device 1105 supporting Doppler selection for multiple transmit and receive points, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components that support output and enable communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0211] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0212] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by one of the at least one processor 1135, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may also include a BIOS, etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0213] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., supporting various functions or tasks for Doppler selection of multiple transmit and receive points). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1130) host functions for performing the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories in at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operated to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0214] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

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

[0216] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for transmitting one or more reference signals to the UE. The communication manager 1120 may be capable of, configured to, or operable to support components for receiving a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit and receive points. The communication manager 1120 may be capable of, configured to, or operable to support components for scheduling one or more resources for communicating with the UE based on the received report.

[0217] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for improving communication reliability, reducing latency, improving and reducing processing-related user experience, utilizing communication resources more efficiently, and improving coordination between devices.

[0218] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors of at least one processor 1135 to cause device 1105 to perform various aspects of Doppler selection for multiple transmit and receive points as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0219] Figure 12 A flowchart illustrating a method 1200 for supporting Doppler selection for multiple transmit and receive points according to various aspects of this disclosure is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be implemented by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0220] At 1205, the method may include: receiving one or more reference signals from a set of multiple transmitting and receiving points. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference... Figure 6 The described reference signaling manager 625 is used for execution.

[0221] At 1210, the method may include: generating a coherent joint transmission PMI associated with the set of multiple transmit and receive points based on the received one or more reference signals, wherein the coherent joint transmission PMI includes one or more Doppler domain components for each of the multiple transmit and receive points in the set. The operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be derived from references... Figure 6 The described PMI Manager 630 is used to execute this.

[0222] At 1215, the method may include: sending a report including an indication of the coherent joint transmission of the PMI. The operation of block 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to... Figure 6 The report manager 635 described is used to execute this.

[0223] Figure 13 A flowchart illustrating method 1300 for supporting Doppler selection for multiple transmit and receive points according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by a network entity or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0224] At 1305, the method may include: sending one or more reference signals to the UE. The operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be determined by reference signals as specified in the reference signals. Figure 10 The reference signaling manager 1025 is used to execute this.

[0225] At 1310, the method may include: receiving a report including an indication of a coherent joint transmission PMI, wherein the coherent joint transmission PMI is based on the one or more reference signals and includes one or more Doppler domain components for each of a set of multiple transmit and receive points. Operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to... Figure 10 The described PMI indicator 1030 is used to perform this.

[0226] At 1315, the method may include: scheduling one or more resources for communicating with the UE based on the received report. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to... Figure 10 The described downlink resource manager 1035 is used to execute this.

[0227] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving one or more reference signals from a plurality of transmit / receive points; generating a coherent joint transmit pre-decoding matrix indicator (PMI) associated with the plurality of transmit / receive points, at least in part based on the received one or more reference signals, wherein the coherent joint transmit PMI includes one or more Doppler domain components for each of the plurality of transmit / receive points; and transmitting a report including an indication of the coherent joint transmit PMI.

[0228] Aspect 2: According to the method of aspect 1, sending the report includes: sending a common Doppler selection for all of the plurality of transmit and receive points.

[0229] Aspect 3: According to the method of aspect 2, sending the report includes: sending the Doppler offset value of each of the plurality of transmit and receive points.

[0230] Aspect 4: According to the method of aspect 3, the Doppler offset value includes a non-oversampled Doppler offset value, wherein the number of samples of the non-oversampled Doppler offset value is an integer value corresponding to the length of the Doppler basis.

[0231] Aspect 5: The method according to any one of Aspects 3 to 4, wherein the Doppler offset value includes an oversampled Doppler offset value, the number of samples of the oversampled Doppler offset value being a multiple of the Doppler basis length.

[0232] Aspect 6: The method according to any one of Aspects 3 to 5, wherein the number of Doppler offset values ​​for each of the plurality of transmitting and receiving points is less than the total number of transmitting and receiving points in the plurality of transmitting and receiving points, and the number of Doppler offset values ​​represents a relative offset relative to a reference transmitting and receiving point among the plurality of transmitting and receiving points.

[0233] Aspect 7: The method according to any one of Aspects 3 to 6, wherein the Doppler offset value of each of the plurality of transmit and receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit and receive points.

[0234] Aspect 8: The method according to any one of Aspects 3 to 7, wherein the Doppler offset value of each of the plurality of transmit and receive points is shared for all layers of the plurality of layers associated with the PMI.

[0235] Aspect 9: The method according to any one of Aspects 3 to 8, wherein the Doppler offset value of each of the plurality of transmit and receive points is layer-specific for the plurality of layers associated with the PMI.

[0236] Aspect 10: The method according to any one of Aspects 1 to 9, wherein sending the report comprises: sending an independent Doppler selection for each of the plurality of transmit / receive points.

[0237] Aspect 11: According to the method of aspect 10, sending the report includes: sending an oversampled group index for each of the plurality of transmit / receive points.

[0238] Aspect 12: According to the method of aspect 11, sending the report includes: sending an oversampled group index less than the total number of the plurality of transmit / receive points, wherein the oversampled group index is relative to an oversampled group index corresponding to a reference transmit / receive point among the plurality of transmit / receive points.

[0239] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the oversampling group index of each of the plurality of transmit and receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit and receive points.

[0240] Aspect 14: The method according to any one of Aspects 11 to 13, wherein the independent Doppler selection for each of the plurality of transmit / receive points, the oversampling group index for each of the plurality of transmit / receive points, or both are layer-specific for the plurality of layers associated with the PMI.

[0241] Aspect 15: The method according to any one of Aspects 1 to 14, wherein sending the report comprises: sending a strongest coefficient indicator for each of a plurality of layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently jointly sent PMI, wherein the strongest coefficient indicator is defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0242] Aspect 16: The method according to any one of Aspects 1 to 15, wherein sending the report comprises: sending a strongest coefficient indicator for each of a plurality of layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to a coefficient matrix associated with the coherently jointly transmitted PMI, wherein the strongest coefficient indicator is aligned with a zero Doppler basis associated with the one or more Doppler domain components.

[0243] Aspect 17: The method according to any one of Aspects 1 to 16, wherein sending the report comprises: sending a non-zero coefficient bitmap, wherein the frequency domain component and time domain component associated with the non-zero coefficient bitmap are reported as paired coefficients.

[0244] Aspect 18: The method according to any one of Aspects 1 to 17, wherein sending the report comprises: sending a first stage bitmap having a size based on the number of the plurality of transmit / receive points and the number of layers associated with the PMI; and sending a second stage bitmap having non-zero coefficients for a subset of components of the first stage bitmap, the subset being indicated as non-zero by the first stage bitmap.

[0245] Aspect 19: The method according to any one of aspects 1 to 18, wherein the one or more reference signals received from the plurality of transmit and receive points are configured using the same transmit periodicity, and the timing offset difference between the transmission of the reference signals is configured to be less than or equal to an offset threshold duration.

[0246] Aspect 20: The method according to any one of aspects 1 to 19, wherein the one or more reference signals received from the plurality of transmit and receive points are configured using a transmit trigger having a trigger offset difference less than or equal to a trigger threshold duration.

[0247] Aspect 21: The method according to any one of Aspects 1 to 20, wherein the coherent joint transmission PMI includes Type II channel state information PMI.

[0248] Aspect 22: A method for wireless communication at a network entity, the method comprising: transmitting one or more reference signals to a UE; receiving a report including an indication of a coherent joint transmission pre-decoding matrix indicator (PMI), wherein the coherent joint transmission PMI is at least partially based on the one or more reference signals and includes one or more Doppler domain components for each of a plurality of transmit / receive points; and scheduling one or more resources for communicating with the UE, at least partially based on receiving the report.

[0249] Aspect 23: The method according to aspect 22, wherein receiving the report includes: receiving a common Doppler selection for all of the plurality of transmit / receive points.

[0250] Aspect 24: According to the method of aspect 23, receiving the report includes: receiving the Doppler offset value of each of the plurality of transmit / receive points.

[0251] Aspect 25: According to the method of aspect 24, the Doppler offset values ​​include non-oversampled Doppler offset values, wherein the number of samples of the non-oversampled Doppler offset values ​​is an integer value corresponding to the length of the Doppler basis.

[0252] Aspect 26: The method according to any one of Aspects 24 to 25, wherein the Doppler offset value includes an oversampled Doppler offset value, the number of samples of the oversampled Doppler offset value being a multiple of the Doppler basis length.

[0253] Aspect 27: The method according to any one of aspects 24 to 26, wherein the number of Doppler offset values ​​for each of the plurality of transmit and receive points is less than the total number of transmit and receive points in the plurality of transmit and receive points, and the number of Doppler offset values ​​represents a relative offset relative to a reference transmit and receive point among the plurality of transmit and receive points.

[0254] Aspect 28: The method according to any one of Aspects 24 to 27, wherein the Doppler offset value of each of the plurality of transmit and receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit and receive points.

[0255] Aspect 29: The method according to any one of Aspects 24 to 28, wherein the Doppler offset value of each of the plurality of transmit and receive points is shared for all layers of the plurality of layers associated with the PMI.

[0256] Aspect 30: The method according to any one of aspects 24 to 29, wherein the Doppler offset value of each of the plurality of transmit and receive points is layer-specific for the plurality of layers associated with the PMI.

[0257] Aspect 31: The method according to any one of Aspects 22 to 30, wherein receiving the report comprises: receiving an independent Doppler selection for each of the plurality of transmit / receive points.

[0258] Aspect 32: According to the method of aspect 31, receiving the report includes: receiving an oversampled group index for each of the plurality of transmit / receive points.

[0259] Aspect 33: According to the method of aspect 32, receiving the report includes: receiving an oversampled group index less than the total number of the plurality of transmit / receive points, wherein the oversampled group index is relative to an oversampled group index corresponding to a reference transmit / receive point among the plurality of transmit / receive points.

[0260] Aspect 34: The method according to any one of Aspects 32 to 33, wherein the oversampling group index of each of the plurality of transmit and receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit and receive points.

[0261] Aspect 35: The method according to any one of Aspects 32 to 34, wherein the independent Doppler selection for each of the plurality of transmit and receive points, the oversampling group index for each of the plurality of transmit and receive points, or both are layer-specific for the plurality of layers associated with the PMI.

[0262] Aspect 36: The method according to any one of Aspects 22 to 35, wherein receiving the report comprises: receiving a strongest coefficient indicator for each of a plurality of layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to a coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator is defined across all selected Doppler bases associated with the one or more Doppler domain components.

[0263] Aspect 37: The method according to any one of Aspects 22 to 36, wherein receiving the report comprises: receiving a strongest coefficient indicator for each of a plurality of layers associated with the PMI, the strongest coefficient indicator indicating the strongest coefficient corresponding to a coefficient matrix associated with the coherently transmitted PMI, wherein the strongest coefficient indicator is aligned with a zero Doppler basis associated with the one or more Doppler domain components.

[0264] Aspect 38: The method according to any one of Aspects 22 to 37, wherein receiving the report comprises: receiving a non-zero coefficient bitmap, wherein the frequency domain component and time domain component associated with the non-zero coefficient bitmap are reported as paired coefficients.

[0265] Aspect 39: The method according to any one of Aspects 22 to 38, wherein receiving the report comprises: receiving a first stage bitmap having a size based on the number of the plurality of transmit / receive points and the number of layers associated with the PMI; and receiving a second stage bitmap having non-zero coefficients for a subset of components of the first stage bitmap, the subset being indicated as non-zero by the first stage bitmap.

[0266] Aspect 40: The method according to any one of Aspects 22 to 39, wherein the one or more reference signals are configured using the same transmission periodicity, and the timing offset difference between the transmissions of the reference signals is configured to be less than or equal to an offset threshold duration.

[0267] Aspect 41: The method according to any one of Aspects 22 to 40, wherein the one or more reference signals are configured using a transmission trigger having a trigger offset difference less than or equal to a trigger threshold duration.

[0268] Aspect 42: The method according to any one of Aspects 22 to 41, wherein the coherent joint transmission PMI includes Type II channel state information PMI.

[0269] Aspect 43: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the UE to perform a method according to any one of aspects 1 to 21.

[0270] Aspect 44: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 21.

[0271] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 21.

[0272] Aspect 46: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the network entity to perform a method according to any one of aspects 22 to 42.

[0273] Aspect 47: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 22 to 42.

[0274] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method according to any one of aspects 22 to 42.

[0275] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0276] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0278] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0279] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0280] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0281] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0282] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0283] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0284] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0285] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the UE to: Receive one or more reference signals from multiple transmitting and receiving points; At least in part based on the received one or more reference signals, a coherent joint transmit pre-decoding matrix indicator (PMI) associated with the plurality of transmit and receive points is generated, wherein the coherent joint transmit PMI includes one or more Doppler domain components for each of the plurality of transmit and receive points; and Send a report including instructions for the coherent joint transmission of the PMI.

2. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send a common Doppler selection for all of the plurality of transmit and receive points.

3. The UE according to claim 2, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The Doppler offset value of each of the plurality of transmit and receive points is transmitted.

4. The UE according to claim 3, wherein: The Doppler offset values ​​include non-oversampled Doppler offset values, and The number of samples for the non-oversampled Doppler offset is an integer value corresponding to the length of the Doppler basis.

5. The UE according to claim 3, wherein: The Doppler offset values ​​include oversampled Doppler offset values, and The number of samples for the oversampled Doppler offset is a multiple of the Doppler base length.

6. The UE according to claim 3, wherein: The number of Doppler offset values ​​for each of the plurality of transmitting and receiving points is less than the total number of transmitting and receiving points. The number of Doppler offset values ​​represents the relative offset with respect to a reference transmit / receive point among the plurality of transmit / receive points.

7. The UE of claim 3, wherein the Doppler offset value of each of the plurality of transmit / receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit / receive points.

8. The UE of claim 3, wherein the Doppler offset value of each of the plurality of transmit / receive points is shared for all layers of the plurality of layers associated with the PMI.

9. The UE of claim 3, wherein the Doppler offset value of each of the plurality of transmit / receive points is layer-specific for the plurality of layers associated with the PMI.

10. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send an independent Doppler selection for each of the plurality of transmit / receive points.

11. The UE according to claim 10, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send the oversampling group index for each of the plurality of transmit and receive points.

12. The UE according to claim 11, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send an oversampled group index that is less than the total number of the plurality of transmit and receive points, wherein the oversampled group index is relative to the oversampled group index corresponding to a reference transmit and receive point among the plurality of transmit and receive points.

13. The UE of claim 11, wherein the oversampling group index for each of the plurality of transmit / receive points is shared for both polarizations of one or more transmit antennas of the plurality of transmit / receive points.

14. The UE of claim 11, wherein the independent Doppler selection for each of the plurality of transmit / receive points, the oversampling group index for each of the plurality of transmit / receive points, or both are layer-specific for the plurality of layers associated with the PMI.

15. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: For each of the multiple layers associated with the PMI, a strongest coefficient indicator is sent, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently co-transmitted PMI, wherein the strongest coefficient indicator is defined across all selected Doppler bases associated with the one or more Doppler domain components.

16. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: For each of the multiple layers associated with the PMI, a strongest coefficient indicator is sent, the strongest coefficient indicator indicating the strongest coefficient corresponding to the coefficient matrix associated with the coherently co-transmitted PMI, wherein the strongest coefficient indicator is aligned with the zero Doppler basis associated with the one or more Doppler domain components.

17. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send a non-zero coefficient bitmap, wherein the frequency domain component and time domain component associated with the non-zero coefficient bitmap are reported as paired coefficients.

18. The UE according to claim 1, wherein, In order to send the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: Send a first stage bitmap, the first stage bitmap having a size based on the number of the plurality of transmit / receive points and the number of layers associated with the PMI; as well as Send a second stage bitmap, the second stage bitmap having non-zero coefficients for a subset of the components of the first stage bitmap, the subset being indicated as non-zero by the first stage bitmap.

19. The UE according to claim 1, wherein: The one or more reference signals received from the plurality of transmitting and receiving points are configured using the same transmission periodicity, and The timing offset difference between reference signal transmissions is configured to be less than or equal to the offset threshold duration.

20. The UE of claim 1, wherein the one or more reference signals received from the plurality of transmit / receive points are configured using a transmit trigger having a trigger offset difference less than or equal to a trigger threshold duration.

21. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the network entity to: Send one or more reference signals to the user equipment (UE); Receive a report including an indication of a coherent joint transmit pre-decoding matrix indicator (PMI), wherein the coherent joint transmit PMI is at least partially based on the one or more reference signals and includes one or more Doppler domain components for each of a plurality of transmit-receive points; as well as One or more resources for communicating with the UE are scheduled, at least in part, based on the receipt of the report.

22. The network entity according to claim 21, wherein, In order to receive the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the network entity to: Receive a common Doppler selection for all of the plurality of transmit and receive points.

23. The network entity according to claim 22, wherein, In order to receive the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the network entity to: Receive the Doppler offset value of each of the plurality of transmit and receive points.

24. The network entity according to claim 23, wherein: The Doppler offset values ​​include non-oversampled Doppler offset values, and The number of samples for the non-oversampled Doppler offset is an integer value corresponding to the length of the Doppler basis.

25. The network entity according to claim 23, wherein: The Doppler offset values ​​include oversampled Doppler offset values, and The number of samples for the oversampled Doppler offset is a multiple of the Doppler base length.

26. The network entity according to claim 21, wherein, In order to receive the report, the one or more processors can operate individually or jointly to execute the code, thereby enabling the network entity to: Receive independent Doppler selection for each of the plurality of transmit / receive points.

27. A user equipment (UE), the user equipment (UE) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the UE to: Receive one or more reference signals from multiple transmitting and receiving points; At least in part based on the received one or more reference signals, a coherent joint transmit pre-decoding matrix indicator (PMI) associated with the plurality of transmit and receive points is generated, wherein the coherent joint transmit PMI includes one or more Doppler domain components for each of the plurality of transmit and receive points; and Send a report including instructions for the coherent joint transmission of the PMI.

28. The UE according to claim 27, wherein, In order to send the report, the processing system is configured to cause the UE to: Send a common Doppler selection for all of the plurality of transmit and receive points.

29. The UE according to claim 28, wherein, In order to send the report, the processing system is configured to cause the UE to: The Doppler offset value of each of the plurality of transmit and receive points is transmitted.

30. A network entity, the network entity comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the network entity to: Send one or more reference signals to the user equipment (UE); Receive a report including an indication of a coherent joint transmit pre-decoding matrix indicator (PMI), wherein the coherent joint transmit PMI is at least partially based on the one or more reference signals and includes one or more Doppler domain components for each of a plurality of transmit-receive points; as well as One or more resources for communicating with the UE are scheduled, at least in part, based on the receipt of the report.

Images